So configuring the Azure VPN Gateway for point‑to‑site to
support a user‑based connection is similar,
but just slightly different.
So I've removed the configuration from the previous demonstration,
and here I'm just going to walk through this once again.
So I'll click Configure now, and you'll see it remembered my address pool.
So I left that there.
That's fine.
And here we're going to select SSTP because we're going to
use this as a user‑based connection.
Once again, we're going to check our Authentication type,
but this time we're going to uncheck Azure certificate,
and then we'll select RADIUS authentication.
And here we're going to put in our RADIUS server IP address.
Again,
we can't use a name here because the Azure VPN Gateway
doesn't have access to our DNS infrastructure,
so we must put an IP address here.
And the important thing to note here is that this IP
address does not have to be in Azure.
It just needs to be reachable by the Azure VPN Gateway.
Ideally,
it will be in Azure or at least someplace located as close as
possible to the Azure VPN Gateway to perform authentication
promptly and effectively and efficiently,
but at the end of the day,
this NPS server really could reside anywhere as long as it was reachable.
And, of course, you'll enter your your shared secret.
And if you want to have a secondary server, you can do that.
It does only support two.
Not a bad idea to have a backup as well, so we'll enter one here.
And once that's done, go ahead and click Save.
And then once the gateway is finished saving,
just like I did before, click Download VPN client,
open the archive, navigate to the Generic folder,
find that XML file, and grab your VPN Gateway name.
It's the same gateway, so it's the same name that we use previously.
But again, just like I did before with the device‑based connection,
then you would supply that as your VPN Gateway name in the
device configuration profile in Intune, or if you're using XML, you would place that in your XML.