temporarily remove PSH/CLI examples

Author: tamram

articles/storage/common/classic-account-migrate.md

@@ -52,8 +52,6 @@ $ az resource list \
 
 ## Migrate a classic storage account
 
-# [Portal](#tab/azure-portal)
-
 To migrate a classic storage account to the Azure Resource Manager deployment model with the Azure portal:
 
 1. Navigate to your classic storage account in the Azure portal.
@@ -76,55 +74,6 @@ To migrate a classic storage account to the Azure Resource Manager deployment mo
 1. If you're not satisfied with the results of the migration, select **Abort** to delete the new storage account and resource group. You can then address any problems and try again.
 1. When you're ready to commit, type **yes** to confirm, then select **Commit** to complete the migration.
 
-# [PowerShell](#tab/azure-powershell)
-
-To migrate a classic storage account to the Azure Resource Manager deployment model with PowerShell, first validate that the account is ready for migration by running the following command. Remember to replace the placeholder values in brackets with your own values:
-
-```azurepowershell
-$storageAccountName = "<storage-account>"
-Move-AzureStorageAccount -Validate -StorageAccountName $storageAccountName
-```
-
-Next, prepare the account for migration:
-
-```azurepowershell
-Move-AzureStorageAccount -Prepare -StorageAccountName $storageAccountName
-```
-
-Check the configuration for the prepared storage account with either Azure PowerShell or the Azure portal. If you're not ready for migration, use the following command to revert your account to its previous state:
-
-```azurepowershell
-Move-AzureStorageAccount -Abort -StorageAccountName $storageAccountName
-```
-
-Finally, when you are satisfied with the prepared configuration, move forward with the migration and commit the resources with the following command:
-
-```azurepowershell
-Move-AzureStorageAccount -Commit -StorageAccountName $storageAccountName
-```
-
-# [Azure CLI](#tab/azure-cli)
-
-To migrate a classic storage account to the Azure Resource Manager deployment model with the Azure CLI, first prepare the account for migration by running the following command. Remember to replace the placeholder values in brackets with your own values:
-
-```azurecli
-az storage account prepare-migration <storage-account>
-```
-
-Check the configuration for the prepared storage account with either Azure CLI or the Azure portal. If you're not ready for migration, use the following command to revert your account to its previous state:
-
-```azurecli
-az storage account abort-migration <storage-account>
-```
-
-Finally, when you are satisfied with the prepared configuration, move forward with the migration and commit the resources with the following command:
-
-```azurecli
-az storage account commit-migration <storage-account>
-```
-
----
-
 ### Locate and delete disk artifacts in a classic account
 
 Classic storage accounts may contain classic (unmanaged) disks, virtual machine images, and operating system (OS) images. To migrate the account, you may need to delete these artifacts first.

articles/storage/common/classic-account-migration-process.md

@@ -60,7 +60,9 @@ The Validation step is the first step in the migration process. The goal of this
 
 The Validation step analyzes the state of resources in the classic deployment model. It checks for failures and unsupported scenarios due to different configurations of the storage account in the classic deployment model.
 
-Keep in mind that it's not possible to check for every issues that the Azure Resource Manager stack might impose on the storage account during migration. Some issues are only checked when the resources undergo transformation in the next step of migration (the Prepare step).
+The Validation step does not check for virtual machine (VM) disks that may be associated with the storage account. You must check your storage accounts manually to determine whether they support VM disks.
+
+Keep in mind that it's not possible to check for every constraint that the Azure Resource Manager stack might impose on the storage account during migration. Some constraints are only checked when the resources undergo transformation in the next step of migration (the Prepare step).
 
 ### Prepare
 
@@ -98,10 +100,28 @@ After you are satisfied that your classic storage account has been migrated succ
 > [!NOTE]
 > Committing the migration is an idempotent operation. If it fails, retry the operation. If it continues to fail, create a support ticket or ask a question on [Microsoft Q&A](/answers/index.html)
 
-### After the migration
+## After the migration
+
+After the migration is complete, your new storage account is ready for use. You can resume write operations at this point to the storage account.
+
+### Migrated account type
 
 After the migration is complete, your new storage account is a general-purpose v1 storage account. We recommend upgrading to a general-purpose v2 account to take advantage of the newest features that Azure Storage has to offer for security, data protection, lifecycle management, and more. To learn how to upgrade to a general-purpose v2 storage account, see [Upgrade to a general-purpose v2 storage account](storage-account-upgrade.md).
 
+### Account properties
+
+Any properties that are set on the classic storage account are migrated with their values to the new storage account.
+
+### RBAC role assignments
+
+Any RBAC role assignments that are scoped to the classic storage account are maintained after the migration.
+
+### Account keys
+
+The account keys are not changed or rotated during the migration. You do not need to regenerate your account keys after the migration is complete. You will not need to update connection strings in any applications that are using the account keys after the migration.
+
+### Portal support
+
 You can manage your migrated storage accounts in the [Azure portal](https://portal.azure.com). You will not be able to use the classic portal to manage your migrated storage accounts.
 
 ## See also