Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Resource Manager enables deploying complex applications through templates, configures virtual machines by using VM extensions, and incorporates access management and tagging. Azure Resource Manager includes scalable, parallel deployment for virtual machines into availability sets. The new deployment model also provides lifecycle management of compute, network, and storage independently. You can read more about Azure Resource Manager features and benefits.
Application gateway resources are not migrated automatically as part of VNet migration from classic to Resource Manager. As part of VNet migration process as documented at IaaS resources migration page, if you have an application gateway resource present on the VNet that you're trying to migrate to Resource Manager deployment model, the automatic migration wouldn't be successful.
To migrate your application gateway resource to Resource Manager deployment model, you'll have to remove the Application Resource from the VNet before beginning migration and then recreate the application gateway resource once migration is complete.
For more information on how to set up an application gateway resource after VNet migration, you can refer:
- Deployment via portal
- Deployment via PowerShell
- Deployment via Azure CLI
- Deployment via ARM template
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.
Azure Resource Manager is the latest control plane of Azure responsible for creating, managing, deleting VMs and performing other control plane operations.
Refer to Frequently asked questions about classic to Azure Resource Manager migration
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
#Login 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>
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.
To get started, see: platform-supported migration of IaaS resources from classic to Resource Manager
For any concerns around migration, you can contact Azure Support. Learn more about Azure support here.