Retiring Manually Registered Azure VPN Clients on March 31, 2029
Microsoft will retire manually registered Azure VPN clients for point-to-site connections using Microsoft Entra ID authentication on March 31, 2029, for Azure Government and Microsoft Azure operated by 21Vianet clouds. To avoid disruption, users must migrate to a Microsoft-registered VPN client before the retirement date. This change aims to enhance security by exclusively supporting Microsoft-registered clients post-retirement.
- →Retirement of manually registered Azure VPN clients
- →Recommended action: Migrate to Microsoft-registered VPN clients
Deprecations (1) ›
- Retirement of manually registered Azure VPN clients
Manually registered Azure VPN clients for point-to-site connections with Microsoft Entra ID authentication will be retired on March 31, 2029, for Azure Government and Microsoft Azure operated by 21Vianet clouds.
Notes (1) ›
- Recommended action: Migrate to Microsoft-registered VPN clients
Users are advised to migrate manually registered Azure VPN clients to a Microsoft-registered VPN client before March 31, 2029, to prevent service disruptions. Only Microsoft-registered VPN clients will be supported after this date to improve security.
https://azure.microsoft.com/en-us/updates/?id=557395
Related releases
- Azure Blob Storage SFTP adds Microsoft Entra ID-based access Azure Updates ·
- Microsoft Entra server principals now generally available for Azure SQL Database Azure Updates ·
- Azure Managed Redis adds Entra ID RBAC for data management in preview Azure Updates ·
- Azure Updates discovery enabled by AI Azure Updates ·
- SharePoint indexer supports ASPX pages and Lists in Azure preview Azure Updates ·
- Azure Database for PostgreSQL: Cross-tenant Customer-Managed Keys in Preview Azure Updates ·