The only caveat you need to be aware of in this scenerio, is that RADIUS Point-to-Site authentication is only available on the SKU “VPNGW1” and above. The Azure VPN Gateway is just about as easy as it gets to configure and to managed (sometimes to a fault). The Gateway Subnet will be used automatically, and is required, when you configure the VPN Gateway. One subnet for infrastructure, and one “Gateway Subnet”. You most likely already have a VNET where you will be configuring this setup, but if you don’t you need to create one with two subnets. Virtual Network Gateway Subnet: 10.1.0.16/28ĭomain Controler/NPS Server Static IP: 10.1.0.10
Virtual Network Address Space: 10.1.0.0/24 To start off, here is my environment information I’m using to setup this configuration.
This post is how you impliment said configuration. Thankfully, Microsoft now allows RADIUS backed authentication. It wasn’t bad, but it certainly wasn’t good. Until recently though, Point-to-Site VPNs were a bit clunky because they needed mutual certificate authentication. Posted on JanuUpdated on JanuReading Time: 4 minutesįor the money, it’s hard to beat the Azure VPN Gateway. Azure Point-to-Site VPN with RADIUS Authentication
0 kommentar(er)
