Merge pull request #234270 from divargas-msft/patch-7

[Doc-a-thon] Updating migration-classic-resource-manager-cli.md

Author: v-shils

articles/virtual-machines/migration-classic-resource-manager-cli.md

@@ -7,7 +7,7 @@ ms.service: virtual-machines
 ms.subservice: classic-to-arm-migration
 ms.workload: infrastructure-services
 ms.topic: how-to
-ms.date: 01/23/2023
+ms.date: 04/12/2023
 ms.author: oriwolman 
 ms.custom: devx-track-azurecli compute-evergreen, devx-track-arm-template
 ---
@@ -23,15 +23,16 @@ These steps show you how to use CLI commands to migrate infrastructure as a serv
 
 > [!NOTE]
 > All the operations described here are idempotent. If you have a problem other than an unsupported feature or a configuration error, we recommend that you retry the prepare, abort, or commit operation. The platform will then try the action again.
-> 
-> 
+>
+>
 
 <br>
 Here is a flowchart to identify the order in which steps need to be executed during a migration process
 
 ![Screenshot that shows the migration steps](./media/migration-classic-resource-manager/migration-flow.png)
 
 ## Step 1: Prepare for migration
+
 Here are a few best practices that we recommend as you evaluate migrating IaaS resources from classic to Resource Manager:
 
 * Read through the [list of unsupported configurations or features](migration-classic-resource-manager-overview.md). If you have virtual machines that use unsupported configurations or features, we recommend that you wait for the feature/configuration support to be announced. Alternatively, you can remove that feature or move out of that configuration to enable migration if it suits your needs.
@@ -41,21 +42,21 @@ Here are a few best practices that we recommend as you evaluate migrating IaaS r
 > Application Gateways are not currently supported for migration from classic to Resource Manager. To migrate a classic virtual network with an Application gateway, remove the gateway before running a Prepare operation to move the network. After you complete the migration, reconnect the gateway in Azure Resource Manager. 
 >
 >ExpressRoute gateways connecting to ExpressRoute circuits in another subscription cannot be migrated automatically. In such cases, remove the ExpressRoute gateway, migrate the virtual network and recreate the gateway. Please see [Migrate ExpressRoute circuits and associated virtual networks from the classic to the Resource Manager deployment model](../expressroute/expressroute-migration-classic-resource-manager.md) for more information.
-> 
-> 
+>
+>
 
 ## Step 2: Set your subscription and register the provider
 For migration scenarios, you need to set up your environment for both classic and Resource Manager. [Install the Azure classic CLI](/cli/azure/install-classic-cli) and [select your subscription](/cli/azure/authenticate-azure-cli).
 
 Sign-in to your account.
 
-```azurecli
+```azurecli-interactive
 azure login
 ```
 
 Select the Azure subscription by using the following command.
 
-```azurecli
+```azurecli-interactive
 azure account set "<azure-subscription-name>"
 ```
 
@@ -68,98 +69,100 @@ azure account set "<azure-subscription-name>"
 
 Register with the migration resource provider by using the following command. Note that in some cases, this command times out. However, the registration will be successful.
 
-```azurecli
+```azurecli-interactive
 azure provider register Microsoft.ClassicInfrastructureMigrate
 ```
 
 Please wait five minutes for the registration to finish. You can check the status of the approval by using the following command. Make sure that RegistrationState is `Registered` before you proceed.
 
-```azurecli
+```azurecli-interactive
 azure provider show Microsoft.ClassicInfrastructureMigrate
 ```
 
 Now switch CLI to the `asm` mode.
 
-```azurecli
+```azurecli-interactive
 azure config mode asm
 ```
 
 ## Step 3: Make sure you have enough Azure Resource Manager Virtual Machine vCPUs in the Azure region of your current deployment or VNET
 For this step you'll need to switch to `arm` mode. Do this with the following command.
 
-```azurecli
+```azurecli-interactive
 azure config mode arm
 ```
 
 You can use the following CLI command to check the current number of vCPUs you have in Azure Resource Manager. To learn more about vCPU quotas, see [Limits and the Azure Resource Manager](../azure-resource-manager/management/azure-subscription-service-limits.md#managing-limits).
 
-```azurecli
+```azurecli-interactive
 azure vm list-usage -l "<Your VNET or Deployment's Azure region"
 ```
 
 Once you're done verifying this step, you can switch back to `asm` mode.
 
-```azurecli
+```azurecli-interactive
 azure config mode asm
 ```
 
 ## Step 4: Option 1 - Migrate virtual machines in a cloud service
+
 Get the list of cloud services by using the following command, and then pick the cloud service that you want to migrate. Note that if the VMs in the cloud service are in a virtual network or if they have web/worker roles, you will get an error message.
 
-```azurecli
+```azurecli-interactive
 azure service list
 ```
 
 Run the following command to get the deployment name for the cloud service from the verbose output. In most cases, the deployment name is the same as the cloud service name.
 
-```azurecli
+```azurecli-interactive
 azure service show <serviceName> -vv
 ```
 
 First, validate if you can migrate the cloud service using the following commands:
 
-```shell
+```azurecli-interactive
 azure service deployment validate-migration <serviceName> <deploymentName> new "" "" ""
 ```
 
 Prepare the virtual machines in the cloud service for migration. You have two options to choose from.
 
 If you want to migrate the VMs to a platform-created virtual network, use the following command.
 
-```azurecli
+```azurecli-interactive
 azure service deployment prepare-migration <serviceName> <deploymentName> new "" "" ""
 ```
 
 If you want to migrate to an existing virtual network in the Resource Manager deployment model, use the following command.
 
-```azurecli
+```azurecli-interactive
 azure service deployment prepare-migration <serviceName> <deploymentName> existing <destinationVNETResourceGroupName> <subnetName> <vnetName>
 ```
 
 After the prepare operation is successful, you can look through the verbose output to get the migration state of the VMs and ensure that they are in the `Prepared` state.
 
-```azurecli
+```azurecli-interactive
 azure vm show <vmName> -vv
 ```
 
 Check the configuration for the prepared resources by using either CLI or the Azure portal. If you are not ready for migration and you want to go back to the old state, use the following command.
 
-```azurecli
+```azurecli-interactive
 azure service deployment abort-migration <serviceName> <deploymentName>
 ```
 
 If the prepared configuration looks good, you can move forward and commit the resources by using the following command.
 
-```azurecli
+```azurecli-interactive
 azure service deployment commit-migration <serviceName> <deploymentName>
 ```
 
 ## Step 4: Option 2 -  Migrate virtual machines in a virtual network
+
 Pick the virtual network that you want to migrate. Note that if the virtual network contains web/worker roles or VMs with unsupported configurations, you will get a validation error message.
 
 Get all the virtual networks in the subscription by using the following command.
 
-```azurecli
+```azurecli-interactive
 azure network vnet list
 ```
 
@@ -171,46 +174,47 @@ In the above example, the **virtualNetworkName** is the entire name **"Group cla
 
 First, validate if you can migrate the virtual network using the following command:
 
-```shell
+```azurecli-interactive
 azure network vnet validate-migration <virtualNetworkName>
 ```
 
 Prepare the virtual network of your choice for migration by using the following command.
 
-```azurecli
+```azurecli-interactive
 azure network vnet prepare-migration <virtualNetworkName>
 ```
 
 Check the configuration for the prepared virtual machines by using either CLI or the Azure portal. If you are not ready for migration and you want to go back to the old state, use the following command.
 
-```azurecli
+```azurecli-interactive
 azure network vnet abort-migration <virtualNetworkName>
 ```
 
 If the prepared configuration looks good, you can move forward and commit the resources by using the following command.
 
-```azurecli
+```azurecli-interactive
 azure network vnet commit-migration <virtualNetworkName>
 ```
 
 ## Step 5: Migrate a storage account
+
 Once you're done migrating the virtual machines, we recommend you migrate the storage account.
 
 Prepare the storage account for migration by using the following command
 
-```azurecli
+```azurecli-interactive
 azure storage account prepare-migration <storageAccountName>
 ```
 
 Check the configuration for the prepared storage account by using either CLI or the Azure portal. If you are not ready for migration and you want to go back to the old state, use the following command.
 
-```azurecli
+```azurecli-interactive
 azure storage account abort-migration <storageAccountName>
 ```
 
 If the prepared configuration looks good, you can move forward and commit the resources by using the following command.
 
-```azurecli
+```azurecli-interactive
 azure storage account commit-migration <storageAccountName>
 ```