For Azure VPN Client with Point-to-Site (P2S):
- A separate VPN server is not required. Azure VPN Gateway provides the P2S VPN gateway service.
- P2S connections require a route-based VPN gateway.
- The client connects by importing the VPN client profile configuration package into Azure VPN Client and then connecting.
About using Azure VPN Client without a Microsoft account:
- If the P2S gateway is configured for Microsoft Entra ID authentication, users authenticate with Microsoft Entra ID credentials.
- Microsoft Entra ID authentication is supported only for the OpenVPN protocol.
- To authenticate and connect with Microsoft Entra ID, clients must use the Azure VPN Client.
- Azure VPN Gateway also supports other authentication methods, including:
- Certificate authentication
- RADIUS / Active Directory Domain Server authentication
If the goal is to avoid Microsoft Entra ID sign-in, use a P2S configuration based on:
- Certificate authentication: each client needs the Azure VPN Client installed and configured, plus the correct client certificates installed locally.
- RADIUS / AD Domain authentication: requires a RADIUS server integrated with Active Directory. The Azure VPN Gateway acts as a pass-through to the RADIUS server. If that RADIUS server is on-premises, a site-to-site VPN connection from Azure to the on-premises site is required for reachability.
For Windows with Microsoft Entra ID authentication, the Azure VPN Client setup is:
- Open Azure VPN Client.
- Select + > Import.
- Open the extracted profile package, then in the AzureVPN folder select azurevpnconfig_aad.xml or azurevpnconfig.xml.
- Save the profile.
- Select the profile and choose Connect.
- Authenticate if prompted.