Azure VPN Gateway (classic) is retiring on August 31st 2024

[azure-deprecation-automation]

Azure VPN Gateway (classic) is retiring on August 31st 2024

Deadline: Aug 31, 2024
Impacted Services:

• Azure Vpn Gateway

More information:

• https://azure.microsoft.com/updates/five-azure-classic-networking-services-will-be-retired-on-31-august-2024/
• https://docs.microsoft.com/azure/vpn-gateway/vpn-gateway-classic-resource-manager-migration
• Azure Cloud Services (classic) deployment model is retiring on 31 August 2024 #167

Notice

Here's the official report from Microsoft:

In August 2021, we announced that Azure Cloud Services (classic) will be retired on 31 August 2024. Because classic Azure Virtual Network, reserved IP addresses, Azure ExpressRoute gateway, Azure Application Gateway, and Azure VPN Gateway are dependent on Azure Cloud Services (classic), they’ll be retired on the same date.

Before that date, you’ll need to migrate any resources that use these classic networking services to the Azure Resource Manager deployment model, which provides the same capabilities as classic plus:

• Simplified resource deployment with a management layer that enables you to create, update, and delete Azure resources.
• Resource grouping, which allows you to deploy, monitor, manage, and apply access control policies to resources as a group.

Timeline

Phase	Date	Description
Announcement	Mar 18, 2022	Deprecation was announced
Deprecation	Aug 31, 2024	Service will no longer work

Impact

Azure VPN Gateway (classic) is retiring on August 31st 2024 and migration to ARM-based Azure VPN Gateway is required.

Required Action

A migration guide is available here.

Here's the official report from Microsoft:

To avoid service disruptions, follow the guidance to migrate your resources that use these classic networking services to Azure Resource Manager by 31 August 2024.

Contact

You can get in touch through the following options:

• Get answers from Microsoft Q&A (link).
• Contact Azure support (link).

[azure-deprecation-automation]

This issue is automatically managed and suggest to use GitHub Discussions to discuss this deprecation.