Everything, Everything

I tried following a couple of guides on how to setup VPN access using Windows Server 2012 R2. The first guide for PPTP was going well until I logged into the new Azure portal and tried to add the necessary endpoints - you can only add TCP and UDP ports; you can't add protocols! I switched to using SSTP, which means exposing HTTPS with IIS, and got a lot further. I temporarily installed the self-signed certificate as a trusted root certificate on my computer, otherwise Windows 10 complains about it (and Windows won't let you ignore any certificate errors). I initially tried using the default DHCP setting for IPv4 assignment but it seemed happier with a static pool.

Then I realised that nothing was being routed. It turns out neither of the two guides I'd looked at covered installing Routing and enabling NAT on a public interface so that I can use the VPN connection to talk to other hosts on the Internet, which was the point of my little exercise. After adding the extra role and following the second step in a TechNet article, things appear to be working. If I try and access Netflix or Yahoo it thinks I'm in another part of Western Europe. Presumably if I spin up another Azure VM in America I could make them think I'm based there (although they release shows like Better Call Saul, House of Cards, and Love at the same time as the UK so I'm not too concerned). Bandwidth isn't too expensive either, with Tier 1 costing about £5 for 100GB of traffic.