Merge pull request #287758 from greg-lindsay/appgw-upd

replace 287569

Author: JamesJBarnett

articles/application-gateway/classic-to-resource-manager.md

@@ -1,27 +1,27 @@
 ---
-title: Application Gateway classic to Resource Manager
-description: Learn about moving Application Gateway resources from the classic deployment model to the Resource Manager deployment model.
+title: Azure Application Gateway classic to Resource Manager
+description: Learn about moving Azure Application Gateway resources from the classic deployment model to the Resource Manager deployment model.
 services: application-gateway
 author: greg-lindsay
 ms.service: azure-application-gateway
 ms.topic: how-to
-ms.date: 06/27/2024
+ms.date: 10/02/2024
 ms.author: greglin
 ---
 
-# Application Gateway classic to Resource Manager migration
+# Application gateway classic to Resource Manager migration
 
 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](../azure-resource-manager/management/overview.md).
 
-Application Gateway resources will **not** be 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](/azure/virtual-machines/migration-classic-resource-manager-ps), 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. 
+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](/azure/virtual-machines/migration-classic-resource-manager-ps), 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. 
 
-In order 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.
+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.
 
-## Creating a new Application Gateway resource 
+## Creating a new application gateway resource 
 
-For more information on how to set up an Application Gateway resource after VNet migration, you can refer:
+For more information on how to set up an application gateway resource after VNet migration, you can refer:
 
 * [Deployment via portal](quick-create-portal.md)
 * [Deployment via PowerShell](quick-create-powershell.md)
@@ -43,13 +43,38 @@ Azure Resource Manager is the latest control plane of Azure responsible for crea
 
 ### Where can I find more information regarding classic to Azure Resource Manager migration?
 
-Please refer to [Frequently asked questions about classic to Azure Resource Manager migration](/azure/virtual-machines/migration-classic-resource-manager-faq)
+Refer to [Frequently asked questions about classic to Azure Resource Manager migration](/azure/virtual-machines/migration-classic-resource-manager-faq)
+
+### 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](/powershell/azure/servicemanagement/install-azure-ps)
+
+> [!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](/powershell/module/servicemanagement/azure/remove-azureapplicationgateway)
+
+ ```
+#Login to account and set proper subscription
+  Add-AzureAccount
+  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](/answers/topics/azure-virtual-network.html). 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](/azure/virtual-machines/migration-classic-resource-manager-ps)
+To get started, see: [platform-supported migration of IaaS resources from classic to Resource Manager](/azure/virtual-machines/migration-classic-resource-manager-ps)
 
-For any concerns around migration, you can contact Azure Support. Learn more about [Azure support here](https://azure.microsoft.com/support/options/).
+For any concerns around migration, you can contact Azure Support. Learn more about [Azure support here](https://azure.microsoft.com/support/options/).