Merge pull request #104065 from mimckitt/patch-10

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

Author: PRMerger16

articles/storsimple/storsimple-8000-migrate-classic-azure-portal.md

@@ -31,7 +31,7 @@ You may need to move your StorSimple service to a new enrollment or to a new sub
 |Can I transfer ownership of an Azure subscription to another directory? | Yes       | No       | Associate an existing subscription to your Azure AD directory | Refer [To associate an existing subscription to your Azure AD directory](../active-directory/fundamentals/active-directory-how-subscriptions-associated-directory.md). It might take up to 10 minutes for everything to show up properly.|
 | StorSimple device from one StorSimple Device Manager service to another service in a different region?      | No        | Yes            | None, manual process |Same as above.|
 | Storage account to a new subscription or resource group?     | Yes        | No             |Move storage account to different subscription or resource group |After the move, if the storage account access keys are updated, the user will need to configure the access keys manually for the migrated storage account through the StorSimple Device Manager service.|
-| Classic storage account to an Azure Resource Manager storage account      | Yes        | No             |Migrate from classic to Azure Resource Manager |<li>For detailed instructions on how to migrate a storage account from classic to Azure Resource Manager, go to [Migrate a classic storage account](../virtual-machines/windows/migration-classic-resource-manager-ps.md#step-62-migrate-a-storage-account).</li><li> If the storage account access keys are updated after migration, the user will need to synchronize the access keys for the migrated storage account through the StorSimple Device Manager service. This is to ensure the StorSimple devices continue to function normally and are able to tier primary/backup data to Azure. For detailed instructions on synchronizing access keys, go to [Rotation workflow](storsimple-8000-manage-storage-accounts.md#key-rotation-of-storage-accounts).</li><li> In the case of a StorSimple Cloud Appliance, if the classic storage account is migrated but the underlying virtual machine still stays in classic, the appliance should function properly. If the underlying virtual machine for the cloud appliance is migrated, then the deactivate and delete functionality will not work.</li><li> You must create a new StorSimple Cloud Appliances in the Azure portal and then fail over from the older cloud appliances. You cannot create a StorSimple Cloud Appliance in the new Azure portal using a classic storage account, they need to have an Azure Resource Manager storage account. For more information, go to [Deploy and manage a StorSimple Cloud Appliance](storsimple-8000-cloud-appliance-u2.md).</li>|
+| Classic storage account to an Azure Resource Manager storage account      | Yes        | No             |Migrate from classic to Azure Resource Manager |<li>For detailed instructions on how to migrate a storage account from classic to Azure Resource Manager, go to [Migrate a classic storage account](../virtual-machines/windows/migration-classic-resource-manager-ps.md#step-52-migrate-a-storage-account).</li><li> If the storage account access keys are updated after migration, the user will need to synchronize the access keys for the migrated storage account through the StorSimple Device Manager service. This is to ensure the StorSimple devices continue to function normally and are able to tier primary/backup data to Azure. For detailed instructions on synchronizing access keys, go to [Rotation workflow](storsimple-8000-manage-storage-accounts.md#key-rotation-of-storage-accounts).</li><li> In the case of a StorSimple Cloud Appliance, if the classic storage account is migrated but the underlying virtual machine still stays in classic, the appliance should function properly. If the underlying virtual machine for the cloud appliance is migrated, then the deactivate and delete functionality will not work.</li><li> You must create a new StorSimple Cloud Appliances in the Azure portal and then fail over from the older cloud appliances. You cannot create a StorSimple Cloud Appliance in the new Azure portal using a classic storage account, they need to have an Azure Resource Manager storage account. For more information, go to [Deploy and manage a StorSimple Cloud Appliance](storsimple-8000-cloud-appliance-u2.md).</li>|
 
 ## Datacenter changes
 

articles/virtual-machines/windows/migration-classic-resource-manager-ps.md

@@ -1,4 +1,4 @@
----
+---
 title: Migrate to Resource Manager with PowerShell 
 description: This article walks through the platform-supported migration of IaaS resources such as virtual machines (VMs), virtual networks, and storage accounts from classic to Azure Resource Manager by using Azure PowerShell commands
 services: virtual-machines-windows
@@ -50,8 +50,6 @@ There are two main options to install Azure PowerShell: [PowerShell Gallery](htt
 
 For installation instructions, see [How to install and configure Azure PowerShell](/powershell/azure/overview).
 
-<br>
-
 ## Step 3: Ensure that you're an administrator for the subscription
 To perform this migration, you must be added as a coadministrator for the subscription in the [Azure portal](https://portal.azure.com).
 
@@ -101,6 +99,14 @@ Wait five minutes for the registration to finish. Check the status of the approv
 
 Make sure that RegistrationState is `Registered` before you proceed.
 
+Before switching to the classic deployment model, make sure that you have enough Azure Resource Manager virtual machine vCPUs in the Azure region of your current deployment or virtual network. You can use the following PowerShell 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).
+
+This example checks the availability in the **West US** region. Replace the example region name with your own.
+
+```powershell
+    Get-AzVMUsage -Location "West US"
+```
+
 Now, sign in to your account for the classic deployment model.
 
 ```powershell
@@ -119,27 +125,17 @@ Set your Azure subscription for the current session. This example sets the defau
     Select-AzureSubscription –SubscriptionName "My Azure Subscription"
 ```
 
-<br>
-
-## Step 5: Have enough Resource Manager VM vCPUs
-Make sure that you have enough Azure Resource Manager virtual machine vCPUs in the Azure region of your current deployment or virtual network. You can use the following PowerShell 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).
-
-This example checks the availability in the **West US** region. Replace the example region name with your own.
-
-```powershell
-Get-AzVMUsage -Location "West US"
-```
 
-## Step 6: Run commands to migrate your IaaS resources
-* [Migrate VMs in a cloud service (not in a virtual network)](#step-61-option-1---migrate-virtual-machines-in-a-cloud-service-not-in-a-virtual-network)
-* [Migrate VMs in a virtual network](#step-61-option-2---migrate-virtual-machines-in-a-virtual-network)
-* [Migrate a storage account](#step-62-migrate-a-storage-account)
+## Step 5: Run commands to migrate your IaaS resources
+* [Migrate VMs in a cloud service (not in a virtual network)](#step-51-option-1---migrate-virtual-machines-in-a-cloud-service-not-in-a-virtual-network)
+* [Migrate VMs in a virtual network](#step-51-option-2---migrate-virtual-machines-in-a-virtual-network)
+* [Migrate a storage account](#step-52-migrate-a-storage-account)
 
 > [!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 then tries the action again.
 
 
-### Step 6.1: Option 1 - Migrate virtual machines in a cloud service (not in a virtual network)
+### Step 5.1: Option 1 - Migrate virtual machines in a cloud service (not in a virtual network)
 Get the list of cloud services by using the following command. Then pick the cloud service that you want to migrate. If the VMs in the cloud service are in a virtual network or if they have web or worker roles, the command returns an error message.
 
 ```powershell
@@ -220,7 +216,7 @@ If the prepared configuration looks good, you can move forward and commit the re
     Move-AzureService -Commit -ServiceName $serviceName -DeploymentName $deploymentName
 ```
 
-### Step 6.1: Option 2 - Migrate virtual machines in a virtual network
+### Step 5.1: Option 2 - Migrate virtual machines in a virtual network
 
 To migrate virtual machines in a virtual network, you migrate the virtual network. The virtual machines automatically migrate with the virtual network. Pick the virtual network that you want to migrate.
 > [!NOTE]
@@ -263,7 +259,7 @@ If the prepared configuration looks good, you can move forward and commit the re
     Move-AzureVirtualNetwork -Commit -VirtualNetworkName $vnetName
 ```
 
-### Step 6.2: Migrate a storage account
+### Step 5.2: Migrate a storage account
 After you're done migrating the virtual machines, perform the following prerequisite checks before you migrate the storage accounts.
 
 > [!NOTE]