Hello everyone! We are here, talking a little about Point to site VPN Azure. But when I will need to do this? Imagine if you are far away, without your business' laptop. You need to connect to your environment to change some virtual configs and you need to be in your private address to connect. Good history, but there are some cases that it happens! Believe or not! Point-to-Site (or P2S) VPN is a way your computer connects directally with your azure environment (not just Azure, tipically is called Point-to-Site).Image Source: Google Images Until the moment we are writting this post, the VPN support up to 128 VPN clients at the same time. So, lets start..... since nothing to work (I'll creating the scenario from zero). Some scenario information here: VMName: P2SVPNScenario VMIP: 10.0.1.4 Resource Group: RGP2SVPNScenario RGP2SVPNScenario Address 10.0.0.0/16 Default Subnet range:10.0.1.0/24 Gateway Subnet range: 10.0.2.0/28 Point-tosite configuration address pool: 172.16.0/28
Now, we need to create the Virtual Network Gateway...
Now, lets creating the virtual network gateway. This step will take several minutes.....
zzzzzzzzzzzzzzzzzzz After 23 minutes and 25 seconds to be exact...
Now, we need to configurate it.
Put the Address pool to the VPN address... And then, you need to load the certificate information...
After, the image will be like this:
Save and then Download VPN client....
Accept the message to continue......
Sorry for some parts in portuguese... but I know you can understand!
Our VM internal IP.....
Just to test... I'm trying to ping and timed out.....
Now, lets connect to the VPN..
And yes! Working!
And 2 tricks for you! You need to add the certificate key of your root certificate - The Chain CA Certificate, to do this, you need to export as base 64!!! The certificate that you need to use, must have in the field Enhanced Key Usage the Cient Authentication option!
Enjoy! Reference: https://docs.microsoft.com/en-us/azure/vpn-gateway/point-to-site-about
