Merge pull request #215355 from cynthn/patch-9

Update migration-classic-resource-manager-overview.md

Author: denrea

articles/virtual-machines/media/migration-classic-resource-manager/validate-storage-account.png

@@ -5,9 +5,8 @@ author: tanmaygore
 manager: vashan
 ms.service: virtual-machines
 ms.subservice: classic-to-arm-migration
-ms.workload: infrastructure-services
 ms.topic: conceptual
-ms.date: 02/06/2020
+ms.date: 10/21/2022
 ms.author: tagore
 
 ---
@@ -90,17 +89,13 @@ If your storage account does not have any associated disks or Virtual Machines d
 
 The following screenshots show how to upgrade a Classic storage account to an Azure Resource Manager storage account using Azure portal:
 1. Sign in to the [Azure portal](https://portal.azure.com).
-2. Navigate to your storage account.
-3. In the **Settings** section, click **Migrate to Azure Resource Manager**.
+2. Navigate to your classic storage account.
+3. In the **Settings** section, click **Migrate to ARM**.
 4. Click on **Validate** to determine migration feasibility.
-5. If validation passes, click on **Prepare** to create a migrated storage account.
-6. Type **yes** to confirm migration and click **Commit** to finish the migration.
+   :::image type="content" source="./media/migration-classic-resource-manager/validate-storage-account.png" alt-text="Screenshot showing the page for migrating your classic storage account to Azure Resource Manager.":::
+1. If validation passes, click on **Prepare** to create a migrated storage account.
+1. Type **yes** to confirm migration and click **Commit** to finish the migration.
 
-    ![Validate Storage Account](../../includes/media/storage-account-upgrade-classic/storage-migrate-resource-manager-1.png)
-    
-    ![Prepare Storage Account](../../includes/media/storage-account-upgrade-classic/storage-migrate-resource-manager-2.png)
-    
-    ![Finalize Storage Account Migration](../../includes/media/storage-account-upgrade-classic/storage-migrate-resource-manager-3.png)
 
 ### Migration of unattached resources
 Storage Accounts with no associated disks or Virtual Machines data may be migrated independently.
@@ -134,11 +129,11 @@ The following configurations are not currently supported.
 | Compute |Virtual machines that have alerts, Autoscale policies |The migration goes through and these settings are dropped. It is highly recommended that you evaluate your environment before you do the migration. Alternatively, you can reconfigure the alert settings after migration is complete. |
 | Compute |XML VM extensions (BGInfo 1.*, Visual Studio Debugger, Web Deploy, and Remote Debugging) |This is not supported. It is recommended that you remove these extensions from the virtual machine to continue migration or they will be dropped automatically during the migration process. |
 | Compute |Boot diagnostics with Premium storage |Disable Boot Diagnostics feature for the VMs before continuing with migration. You can re-enable boot diagnostics in the Resource Manager stack after the migration is complete. Additionally, blobs that are being used for screenshot and serial logs should be deleted so you are no longer charged for those blobs. |
-| Compute | Cloud services that contain more than one availability set or multiple availability sets. |This is currently not supported. Please move the Virtual Machines to the same availability set before migrating. |
+| Compute | Cloud services that contain more than one availability set or multiple availability sets. |This is currently not supported. Move the Virtual Machines to the same availability set before migrating. |
 | Compute | VM with Microsoft Defender for Cloud extension | Microsoft Defender for Cloud automatically installs extensions on your Virtual Machines to monitor their security and raise alerts. These extensions usually get installed automatically if the Microsoft Defender for Cloud policy is enabled on the subscription. To migrate the Virtual Machines, disable the Defender for Cloud policy on the subscription, which will remove the Defender for Cloud monitoring extension from the Virtual Machines. |
 | Compute | VM with backup or snapshot extension | These extensions are installed on a Virtual Machine configured with the Azure Backup service. While the migration of these VMs is not supported, follow the guidance in [Frequently asked questions about classic to Azure Resource Manager migration](./migration-classic-resource-manager-faq.yml) to keep backups that were taken prior to migration.  |
 | Compute | VM with Azure Site Recovery extension | These extensions are installed on a Virtual Machine configured with the Azure Site Recovery service. While the migration of storage used with Site Recovery will work, current replication will be impacted. You need to disable and enable VM replication after storage migration. |
-| Network |Virtual networks that contain virtual machines and web/worker roles |This is currently not supported. Please move the Web/Worker roles to their own Virtual Network before migrating. Once the classic Virtual Network is migrated, the migrated Azure Resource Manager Virtual Network can be peered with the classic Virtual Network to achieve similar configuration as before.|
+| Network |Virtual networks that contain virtual machines and web/worker roles |This is currently not supported. Move the Web/Worker roles to their own Virtual Network before migrating. Once the classic Virtual Network is migrated, the migrated Azure Resource Manager Virtual Network can be peered with the classic Virtual Network to achieve similar configuration as before.|
 | Network | Classic Express Route circuits |This is currently not supported. These circuits need to be migrated to Azure Resource Manager before beginning IaaS migration. To learn more, see [Moving ExpressRoute circuits from the classic to the Resource Manager deployment model](../expressroute/expressroute-move.md).|
 | Azure App Service |Virtual networks that contain App Service environments |This is currently not supported. |
 | Azure HDInsight |Virtual networks that contain HDInsight services |This is currently not supported. |