AzureRetirement
Azure VPN Gateway: manually registered VPN clients retirement (Gov, 21Vianet)
Retirement date for manually registered Azure VPN clients in Azure Government and Microsoft Azure operated by 21Vianet: 31 Mar 2029. After that date, only Microsoft-registered VPN clients are supported.
Retires , 31 Mar 2029
What breaks
On 31 Mar 2029, manually registered Azure VPN clients for point-to-site connections with Microsoft Entra ID authentication are retired in the Azure Government and Microsoft Azure operated by 21Vianet clouds. After that date, only Microsoft-registered VPN clients are supported.
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 2029.
Replacement
Microsoft-registered VPN client
Sources
- Official sourceazure.microsoft.comOfficial
- 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 2028Azure VPN Gateway: manually registered Azure VPN clients retirementSource
- , 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