Azure VPN Gateway
An Azure service that enables the connection of on-premises networks to Azure through site-to-site virtual private networks.
Windows Server 2019 cannot connect to Azure site using Azure VPN client(certificate authentication)
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(115.19999999999999, 64%, 21%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAS%3C/text%3E%3C/svg%3E)
Andhika Saputra
20
Reputation points
I'm currently installing a VPN client configuration using Azure VPN Client with certificate authentication for the tunnel type I'm using: IKEv2 and OpenVPN. In the Azure VPN client, I imported the configuration azurevpnconfig.xml, and when connecting, I get an error message: "VPN Platform did not trigger connection."
When connecting to the VPN via VPN settings, I get an error message: "No such interface supported."
I've tried this on Windows Server 2022, and everything worked fine. However, I have a production server running Windows Server 2019 standalone, and the Azure VPN client cannot connect to azure site. I tried it in a Windows Server 2019 dev environment, and it failed again.
I've tried several troubleshooting things
- Repair Azure VPN Client
- Reset Network
- Uninstall Network Adapter from device manager
- Restart the Rasman service
- Background Apps
error log:
10/24/2025 6:01:09 AM: Dialing VPN connection vnetdrc, Status = VPN Platform did not trigger connection.
10/24/2025 6:01:09 AM: Found valid client cert in store
10/24/2025 6:01:09 AM: Dialing VPN connection vnetdrc
Azure VPN Gateway
{count} votes
-
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(124.80000000000001, 83%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ERV%3C/text%3E%3C/svg%3E)
Ravi Varma Mudduluru 1,790 Reputation points Microsoft External Staff Moderator2025-10-24T00:20:33.7766667+00:00 Hello @Andhika Saputra,
Thanks for reaching Microsoft Q&A.I understand that you're encountering some connectivity issues with the Azure VPN Client on your Windows Server 2019 setup. Here are some steps you can take to troubleshoot the problem:
- Ensure that the client certificates are correctly installed in the following locations:
- AzureClient.pfx should be in
Current User\Personal\Certificates. - AzureRoot.cer should be in
Local Computer\Trusted Root Certification Authorities.
- AzureClient.pfx should be in
- Ensure that the VPN Gateway is properly configured for Point-to-Site (P2S) connections with the correct authentication settings. Since configurations can vary by site, verify that the appropriate client packages and profiles have been downloaded and successfully imported.
- Delete/Uninstall all WAN miniport network adapters from Device manager, and then click on Action > Scan for hardware changes or perform a machine restart.
- Check if any 3rd party software and/or firewall blocking these P2S connections from the client-side upstream towards Azure.
- If you haven't already, try uninstalling the Azure VPN Client completely and then reinstalling it. This can fix issues related to corrupted installations.
- The error "No such interface supported" could indicate networking issues. checking your firewall rules to ensure they are not blocking VPN connections.
- You noted that the error log states "Dialing VPN connection vnetdrc." Ensure that the config in
azurevpnconfig.xmlaligns with the intended Azure setup.
You can refer to the below thread:
https://free.blessedness.top/en-us/answers/questions/2276954/dialing-vpn-connection-accessdev-vnet-status-vpn-pOfficial documents:
VPN Platform did not trigger connectionWindows background apps and your privacy
Azure VPN Client "Status = VPN Platform did not trigger connection rm-did-not-trigger-connection
Kindly let us know if the above helps or you need further assistance on this issue.
Please "upvote" if the information helped you. This will help us and others in the community as well.
- Ensure that the client certificates are correctly installed in the following locations:
-
Andhika Saputra 20 Reputation points
2025-10-24T01:17:45.5866667+00:00 I have done that but it still doesn't work, is this because Windows Server 2019 can't? I have tried it on Windows Server 2022 and it runs smoothly, but on Windows Server 2019 this issue can't be solved at all. I have done a lot of troubleshooting but it still doesn't work.
-
Ravi Varma Mudduluru 1,790 Reputation points Microsoft External Staff Moderator
2025-10-25T00:25:27.6066667+00:00 Hello @**Andhika Saputra
**
Could you please check the private message and share us the requested details?
Sign in to comment
Sign in to answer