Azure Point to Site VPN Configuration Step by Step | VPN Gateway | Certificates

A Point-to-Site (P2S) VPN gateway connection lets you create a secure connection to your virtual network from an individual client computer. A P2S connection is established by starting it from the client computer. This solution is useful for telecommuters who want to connect to Azure VNets from a remote location, such as from home or a conference. P2S VPN is also a useful solution to use instead of S2S VPN when you have only a few clients that need to connect to a VNet.

Today we are going to learn about Azure VPN Gateway and how to configure a P2S connection to Azure.

00:00 Intro
01:42 Creating Resources + Sample Web Server
02:44 Configuring VPN Gateway
04:23 Certificate Configuration | Root an Client
06:48 Point to Site Configuration
07:48 Device Configuration

Meet Kamal Today
Kamal Rathnayake

[venomq]

Hi mate. Just wanted to say thanks for the upload. I found it quite useful.

[michaelvasilkov]

Thank you brother! I wish I had found this video earlier

[DIegoGrillet]

Hi, thanks for sharing, I ran everything and it worked perfectly, I wanted to consult you, I created a VM with Windows 10, and added a shared folder, which anyone can access, I configured the vpn, everything works fine, the problem occurs when I wanted to access the shared folder, I thought that connected to the VPN and typing in the file explorer \\private-ip-vm I would have access to all shared resources, as usually happens in a local network environment. I was breathing inbound rules, and other things but I did not achieve anything. Ps: I tried to use the OpenVpn client, unfortunately I could not configure it. Thanks for your contribution.

[pantoffelslippers]

Hi. When your VPN connects, what is your IP Address? It’s not on the same range as your 10.0.0.4 server?

[hanyro]

Thank you! Can you create another video by using the Openvpn option?

[wrxryfd]

One think to consider: Basic SKU is no longer available from portal you must create it by command

[bwadley]

Thanks very helpful, it seems Microsoft have removed the Basic VPN SKU, but it can be added via a script. Quite annoying!😊

[roneyr]

Hi Kamal, thank you so much for the video. I have a req where the company doesnt have an on-prem dc. What solution is apt in my scenario.

[ramyalimohamedali]

please explain how non-admin users can connect to the VPN? Thanks!

[bradBueche]

Great video! and it looks like you have bunch of other interesting topics that I need to learn. I just have 1 question so far with the scripting. Isn't this the powershell syntax for declaring variables?
$grp="P2STESTRG"
$location1="southeastasia"
$vnetName1="SEAvnet"
$subnetName="Subnet1"
$vmName="SEA_VM"

Then the rest of the scripting starts with az commands which I thought ran only in bash (or unix shell) so wouldn't the syntax be like this?
export grp="P2STESTRG"
export location1="southeastasia"
export vnetName1="SEAvnet"
export subnetName="Subnet1"
export vmName="SEA_VM"

[Mortenglmz]

Can you use Azure AD VPN Cert + Condtional Access for these deployment, instead of self certificate?