Hello @Ratty ,
Welcome to Microsoft Q&A Platform. Thank you for reaching out & hope you are doing well.
I understand that you would like to know if you need to create certificate when using Azure AD authentication only for P2S VPN connection to an Azure VPN Gateway.
No, you don't need to create any certificate when using Azure AD authentication only for P2S VPN connection to an Azure VPN Gateway.
The certificate that is selected in the certificate information section of the Azure VPN client is a "DigiCert Global Root CA
" certificate which should be auto-filled/auto-selected when you import the Azure VPN profile.
If you are adding a connection manually, you should be able to select "DigiCert Global Root CA
" from the drop down.
Below are the step-by-step instructions to configure Azure AD tenant and P2S VPN gateway & client for Azure VPN:
- Create Azure AD tenant users.
- Authorize the Azure VPN application.
Once the consent is provided, Azure VPN Client shows up under Enterprise Applications within the Azure Active Directory.
- Create a VPN gateway. NOTE: The Basic SKU is not supported for OpenVPN. Azure AD authentication is supported only for OpenVPN® protocol connections and requires the Azure VPN Client.
- Configure Point-to-site authentication for the gateway:
Address pool: client address pool
Tunnel type: OpenVPN (SSL)
Authentication type: Azure Active Directory
Tenant: https://login.microsoftonline.com/{AzureAD TenantID}
Audience: 41b23e61-6c1e-4545-b367-cd054e0ed4b4
Issuer: https://sts.windows.net/{AzureAD TenantID}/
NOTE: Replace the AzureAD TenantID with the tenant ID that corresponds to your configuration.
You can locate the tenant ID of the directory that you want to use for authentication in the properties section of your Active Directory page. For help with finding your tenant ID, see How to find your Azure Active Directory tenant ID.
- Download the Azure VPN Client profile configuration package, extract the downloaded zip file and browse to the AzureVPN folder. Make a note of the location of the “azurevpnconfig.xml” file.
Refer: https://learn.microsoft.com/en-us/azure/vpn-gateway/openvpn-azure-ad-tenant
-
- Download the Azure VPN Client: Download the latest version of the Azure VPN Client install files using one of the following links: Install using Client Install files: https://aka.ms/azvpnclientdownload. Install directly, when signed in on a client computer: Microsoft Store.
- Now, you can either import the VPN client profile configuration files or manually add the profile to the VPN client.
- To Import VPN client profile configuration files:
On the VPN client app, select Import.
- Browse to the profile “azurevpnconfig.xml” file and select it. With the file selected, select Open.
Specify the name of the profile (if you want to change it) or you can leave the default and select Save.
- Select Connect to connect to the VPN.
- To manually add the profile:
- On the VPN client app, select + Add.
- Fill out the connection information. Select Save.
- To fill the information, refer the below doc which shows how to get the required details:
- https://learn.microsoft.com/en-us/azure/vpn-gateway/about-vpn-profile-download
- In the Certificate Information, select "
DigiCert Global Root CA
" from the drop down.
- Select Connect to connect to the VPN.
- Select/type the proper credentials, then select Continue.
Refer: https://learn.microsoft.com/en-us/azure/vpn-gateway/openvpn-azure-ad-client
Additional Information: I've also seen a few customers using DigiCert Global Root G2
certificate in their Azure VPN client on both Windows & Mac.
Refer: https://github.com/MicrosoftDocs/azure-docs/issues/104907
NOTE: These DigiCert Global root certificates should already be available on your machines if they have access to Internet and have windows updates allowed.
Kindly let us know if the above helped or you need further assistance on this issue.
Please "Accept the answer" if the information helped you. This will help us and others in the community as well.
I was able to successfully connect to my Azure VPN Gateway after selecting the Digicert Global Root CA option. In my case, it did not automatically select it when I imported the client VPN configuration xml from azure.
Thank you so much for the assistance!
Thank you for the update, @Ratty . Glad to hear that the provided solution helped in fixing your issue.