Application gateway classic to Resource Manager migration

  • Article
  • 05/18/2025

This article describes benefits of the new Azure Resource Manager (ARM) deployment model and provides guidance on how to migrate Azure Application Gateway from classic deployment to Azure Resource Manager deployment. For more information about deployment models, see Azure Resource Manager vs. classic deployment.

Note

For information about retirement of the classic deployment model, see Azure updates.

Azure Resource Manager has many features and benefits, including:

At a high level, migration of an application gateway from classic to Resource Manager requires three steps:

  1. Remove (delete) the application gateway resource from the VNet.
  2. Migrate your IaaS resources.
  3. Recreate the application gateway resource using Resource Manager.

Important

Application gateway resources are not migrated automatically as part of VNet migration from classic to Resource Manager. If you have an application gateway resource present on the VNet that you're trying to migrate to Resource Manager deployment model, automatic migration fails.

Creating a new application gateway resource

See the following articles for more information on how to set up an application gateway resource after VNet migration:

Common questions

What is Azure Service Manager and what does it mean by classic?

The word "classic" in classic networking service refers to networking resources managed by Azure Service Manager (ASM). Azure Service Manager (ASM) is the old control plane of Azure responsible for creating, managing, deleting VMs and performing other control plane operations.

Note

To view all the classic resources in your subscription, Open the All Resources blade and look for a (Classic) suffix after the resource name.

What is Azure Resource Manager?

Azure Resource Manager is the latest control plane of Azure responsible for creating, managing, deleting VMs and performing other control plane operations.

Where can I find more information regarding classic to Azure Resource Manager migration?

Refer to Frequently asked questions about classic to Azure Resource Manager migration

How can I clean up my classic application gateway deployment?

Step 1: Install the old PowerShell version for managing legacy resources.

Installing the Azure PowerShell Service Management module

Note

The cmdlets referenced in this documentation are for managing legacy Azure resources that use Azure Service Manager (ASM) APIs. This legacy PowerShell module isn't recommended for creating new resources since ASM is scheduled for retirement.

Step 2: Run the following command to remove the application gateway: Remove-AzureApplicationGateway

# Sign in to account and set proper subscription
 Add-AzureAccount -Environment AzureChinaCloud
 Get-AzureSubscription
 Select-AzureSubscription -SubscriptionId <SubscriptionId> -Default

 # Get the list of application gateways in the subscription
 Get-AzureApplicationGateway

 #Remove the desired application gateway
 Remove-AzureApplicationGateway -Name <NameofGateway>

How do I report an issue?

Post your issues and questions about migration to our Microsoft Q&A page. We recommend posting all your questions on this forum. If you have a support contract, you're welcome to log a support ticket as well.

Next steps

To get started, see Platform-supported migration of IaaS resources from classic to Resource Manager

Also see Prepare for Azure classic administrator roles retirement and Azure classic subscription administrators.

For any concerns around migration, you can contact Azure Support. Learn more about Azure support here.