AzureRetirement
Azure VPN Gateway: manually registered Azure VPN clients retirement
Retirement date for manually registered Azure VPN clients for point-to-site connections with Microsoft Entra ID authentication: 31 Mar 2028. After that date, only Microsoft-registered VPN clients are supported.
Retires , 31 Mar 2028
What breaks
On 31 Mar 2028, manually registered Azure VPN clients for point-to-site connections with Microsoft Entra ID authentication are retired. After that date, only Microsoft-registered VPN clients are supported. Since 30 December 2025, it is no longer possible to create point-to-site connections with a manually registered client. Subscriptions that use a manually registered Azure VPN client for point-to-site VPN connections are affected.
What to do
Migrate manually registered Azure VPN clients to a Microsoft-registered VPN client for point-to-site connections with Microsoft Entra ID authentication before 31 Mar 2028.
Replacement
Microsoft-registered VPN client
Sources
- Official sourceazure.microsoft.comOfficial
- Additional sourcelearn.microsoft.comOfficial
- Additional sourceaka.msOfficial
- Additional sourcelearn.microsoft.comOfficial
Last checked against the first source in this list on .
Related
- , 31 Aug 2026Azure VPN Gateway: Azure VPN Client for Linux (Preview) retirementSource
- , 30 Sep 2026Azure VPN Gateway: VpnGw1-5 non-AZ SKUs retirementSource
- , 31 Mar 2027Azure VPN Gateway: SSTP protocol support retirementSource
- , 31 Mar 2029Azure VPN Gateway: manually registered VPN clients retirement (Gov, 21Vianet)Source
- , 18 Aug 2026Microsoft Defender for Cloud: retirement in Azure operated by 21VianetSource
- , 14 Sep 2026Azure Functions: runtime version 1.x end of supportSource
Found an error? Report it
The text on this page is drafted with AI assistance from the vendor's text, checked against the official source and approved by a person before it is published. How items are written
Last checked · Added · Changelog for this item