Merge pull request #234401 from tamram/tamram23-0412

classic account migration: add links to VM disk error info

Author: AnnaMHuff

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

@@ -7,7 +7,7 @@ author: tamram
 
 ms.service: storage
 ms.topic: how-to
-ms.date: 04/10/2023
+ms.date: 04/13/2023
 ms.author: tamram
 ms.subservice: common
 ---
@@ -46,10 +46,10 @@ The process of migrating a classic storage account involves four steps:
 1. **Validate**. During the Validation phase, Azure checks the storage account to ensure that it can be migrated.
 1. **Prepare**. In the Prepare phase, Azure creates a new general-purpose v1 storage account and alerts you to any problems that may have occurred. The new account is created in a new resource group in the same region as your classic account.
 
-    At this point your classic storage account still exists. If there are any problems reported, you can correct them or abort the process.
+    At this point, your classic storage account still exists. If there are any problems reported, you can correct them or abort the process.
 
 1. **Check manually**. It's a good idea to make a manual check of the new storage account to make sure that the output is as you expect.
-1. **Commit or abort**. If you are satisfied that the migration has been successful, then you can commit the migration. Committing the migration permanently deletes the classic storage account.
+1. **Commit or abort**. If you're satisfied that the migration has been successful, then you can commit the migration. Committing the migration permanently deletes the classic storage account.
 
     If there are any problems with the migration, then you can abort the migration at this point. If you choose to abort, the new resource group and new storage account are deleted. Your classic account remains available. You can address any problems and attempt the migration again.
 
@@ -74,7 +74,7 @@ To migrate a classic storage account to the Azure Resource Manager deployment mo
 
 1. If the Prepare step completes successfully, you'll see a link to the new resource group. Select that link to navigate to the new resource group. The migrated storage account appears under the **Resources** tab in the **Overview** page for the new resource group.
 
-    At this point you can compare the configuration and data in the classic storage account to the newly migrated storage account. You'll see both in the list of storage accounts in the portal. Both the classic account and the migrated account have the same name.
+    At this point, you can compare the configuration and data in the classic storage account to the newly migrated storage account. You'll see both in the list of storage accounts in the portal. Both the classic account and the migrated account have the same name.
 
     :::image type="content" source="media/classic-account-migrate/compare-classic-migrated-accounts.png" alt-text="Screenshot showing the results of the Prepare step in the Azure portal." lightbox="media/classic-account-migrate/compare-classic-migrated-accounts.png":::
 
@@ -83,14 +83,14 @@ To migrate a classic storage account to the Azure Resource Manager deployment mo
 
 # [PowerShell](#tab/azure-powershell)
 
-To migrate a classic storage account to the Azure Resource Manager deployment model with PowerShell, you'll need to use the Azure PowerShell Service Management module. To learn how to install this module, see [Install and configure the Azure PowerShell Service Management module](/powershell/azure/servicemanagement/install-azure-ps#checking-the-version-of-azure-powershell). The key steps are included here for convenience.
+To migrate a classic storage account to the Azure Resource Manager deployment model with PowerShell, you must use the Azure PowerShell Service Management module. To learn how to install this module, see [Install and configure the Azure PowerShell Service Management module](/powershell/azure/servicemanagement/install-azure-ps#checking-the-version-of-azure-powershell). The key steps are included here for convenience.
 
 > [!NOTE]
 > The cmdlets in the Azure Service Management module are for managing legacy Azure resources that use Service Management APIs, including classic storage accounts. This module includes the commands needed to migrate a classic storage account to Azure Resource Manager.
 >
 > To manage Azure Resource Manager resources, we recommend that you use the Az PowerShell module. The Az module replaces the deprecated AzureRM module. For more information about moving from the AzureRM module to the Az module, see [Migrate Azure PowerShell scripts from AzureRM to Az](/powershell/azure/migrate-from-azurerm-to-az).
 
-First, install PowerShellGet if you do not already have it installed. For more information on how to install PowerShellGet, see [Installing PowerShellGet](/powershell/scripting/gallery/installing-psget#installing-the-latest-version-of-powershellget). After you install PowerShellGet, close and reopen the PowerShell console.
+First, install PowerShellGet if you don't already have it installed. For more information on how to install PowerShellGet, see [Installing PowerShellGet](/powershell/scripting/gallery/installing-psget#installing-the-latest-version-of-powershellget). After you install PowerShellGet, close and reopen the PowerShell console.
 
 Next, install the Azure Service Management module. If you also have the AzureRM module installed, you'll need to include the `-AllowClobber` parameter, as described in [Step 2: Install Azure PowerShell](/powershell/azure/servicemanagement/install-azure-ps#step-2-install-azure-powershell). After the installation is complete, import the Azure Service Management module.
 
@@ -125,7 +125,7 @@ Check the configuration for the prepared storage account with either Azure Power
 Move-AzureStorageAccount -Abort -StorageAccountName $accountName
 ```
 
-Finally, when you are satisfied with the prepared configuration, move forward with the migration and commit the resources with the following command:
+Finally, when you're satisfied with the prepared configuration, move forward with the migration and commit the resources with the following command:
 
 ```azurepowershell
 Move-AzureStorageAccount -Commit -StorageAccountName $accountName

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

@@ -18,37 +18,30 @@ The [Azure Resource Manager](../../azure-resource-manager/management/overview.md
 
 If you have classic storage accounts, start planning your migration now. Complete it by August 31, 2024, to take advantage of Azure Resource Manager. To learn more about the benefits of Azure Resource Manager, see [The benefits of using Resource Manager](../../azure-resource-manager/management/overview.md#the-benefits-of-using-resource-manager).
 
-Storage accounts created using the classic deployment model will follow the [Modern Lifecycle Policy](https://support.microsoft.com/help/30881/modern-lifecycle-policy) for retirement.
+Storage accounts created using the classic deployment model follow the [Modern Lifecycle Policy](https://support.microsoft.com/help/30881/modern-lifecycle-policy) for retirement.
 
 ## Why is a migration required?
 
-On August 31, 2024, we'll retire classic Azure storage accounts and they'll no longer be accessible. Before that date, you'll need to migrate them to Azure Resource Manager, which provides the same capabilities as well as new features, including:
+On August 31, 2024, we'll retire classic Azure storage accounts and they'll no longer be accessible. Before that date, you must migrate them to Azure Resource Manager, which provides all of the same functionality, as well as new features, including:
 
 - A management layer that simplifies deployment by enabling you to create, update, and delete resources.
 - Resource grouping, which allows you to deploy, monitor, manage, and apply access control policies to resources as a group.
 - All new features for Azure Storage are implemented for storage account in Azure Resource Manager deployments, so customers that are still using classic resources will no longer have access to new features and updates.
 
-## How does this affect me?
+## What happens if I don't migrate my accounts?
 
-On September 1, 2024, customers will no longer be able to connect to classic storage accounts by using Azure Service Manager. Any data still contained in these accounts will no longer be accessible through Azure Service Manager.
+Starting on September 1, 2024, customers will no longer be able to connect to classic storage accounts by using Azure Service Manager. Any data still contained in these accounts will no longer be accessible through Azure Service Manager.
 
 > [!WARNING]
 > If you do not migrate your classic storage accounts to Azure Resource Manager by August 31, 2024, you will permanently lose access to the data in those accounts.
 
-Depending on when your subscription was created, you may no longer to be able to create classic storage accounts:
-
-- Subscriptions created after August 31, 2022 can no longer create classic storage accounts.
-- Subscriptions created before September 1, 2022 will be able to create classic storage accounts until September 1, 2023
-
-We recommend creating storage accounts only in Azure Resource Manager from this point forward.
-
 ## What actions should I take?
 
 To migrate your classic storage accounts, you should:
 
 1. Identify all classic storage accounts in your subscription.
 1. Migrate any classic storage accounts to Azure Resource Manager.
-1. Check your applications and logs to determine whether you are dynamically creating, updating, or deleting classic storage accounts from your code, scripts, or templates. If you are, then you need to update your applications to use Azure Resource Manager accounts instead.
+1. Check your applications and logs to determine whether you're dynamically creating, updating, or deleting classic storage accounts from your code, scripts, or templates. If you are, then you need to update your applications to use Azure Resource Manager accounts instead.
 
 For step-by-step instructions, see [How to migrate your classic storage accounts to Azure Resource Manager](classic-account-migrate.md). For an in-depth overview of the migration process, see [Understand storage account migration from the classic deployment model to Azure Resource Manager](classic-account-migration-process.md).
 
@@ -76,31 +69,36 @@ For step-by-step instructions, see [How to migrate your classic storage accounts
 
 For step-by-step instructions for migrating your classic storage accounts, see [How to migrate your classic storage accounts to Azure Resource Manager](classic-account-migrate.md). For an in-depth overview of the migration process, see [Understand storage account migration from the classic deployment model to Azure Resource Manager](classic-account-migration-process.md).
 
-### At what point can classic storage accounts no longer be created?
+### Can I create new classic accounts?
 
-Subscriptions created after August 2022 are no longer be able to create classic storage accounts. Subscriptions created before August 2022 can continue to create and manage classic storage resources until the retirement date of August 31, 2024.
+Depending on when your subscription was created, you may no longer be able to create classic storage accounts:
+
+- Subscriptions created after August 31, 2022 can no longer create classic storage accounts.
+- Subscriptions created before September 1, 2022 will be able to create classic storage accounts until September 1, 2023
+
+We recommend creating storage accounts only in Azure Resource Manager from this point forward.
 
 ### What happens to existing classic storage accounts after August 31, 2024?
 
-After August 31, 2024, you will no longer be able to access data in your classic storage accounts or manage them. It won't be possible to migrate a classic storage account after August 31, 2024.
+After August 31, 2024, you'll no longer be able to access data in your classic storage accounts or manage them. It won't be possible to migrate a classic storage account after August 31, 2024.
 
 ### Can Microsoft handle this migration for me?
 
-No, Microsoft cannot migrate a customer's storage account on their behalf. Customers must use the self-serve options listed above.
+No, Microsoft can't migrate a customer's storage account on their behalf. Customers must use the self-serve options listed above.
 
 ### Will there be downtime when migrating my storage account from Classic to Resource Manager?
 
-There is no downtime to migrate a classic storage account to Resource Manager. However, there is downtime for other scenarios linked to classic virtual machine (VM) migration.
+There's no downtime to migrate a classic storage account to Resource Manager. However, there may be downtime for other scenarios linked to classic virtual machine (VM) migration.
 
-### What operations are not available during the migration?
+### What operations aren't available during the migration?
 
-Also, during the migration, management operations are not available on the storage account. Data operations can continue to be performed during the migration.
+Also, during the migration, management operations aren't available on the storage account. Data operations can continue to be performed during the migration.
 
-If you are creating or managing container objects with the Azure Storage resource provider, note that those operations will be blocked while the migration is underway. For more information, see [Understand storage account migration from the classic deployment model to Azure Resource Manager](classic-account-migration-process.md).
+If you're creating or managing container objects with the Azure Storage resource provider, keep in mind that those operations are blocked while the migration is underway. For more information, see [Understand storage account migration from the classic deployment model to Azure Resource Manager](classic-account-migration-process.md).
 
 ### Are storage account access keys regenerated as part of the migration?
 
-No, account access keys are not regenerated during the migration. Your access keys and connection strings will continue to work unchanged after the migration is complete.
+No, account access keys aren't regenerated during the migration. Your access keys and connection strings will continue to work unchanged after the migration is complete.
 
 ### Are Azure RBAC role assignments maintained through the migration?
 
@@ -112,9 +110,9 @@ Your storage account will be a general-purpose v1 account after the migration pr
 
 ### Will the URL of my storage account remain the same post-migration?
 
-Yes, the migrated storage account will have the same name and address as the classic account.
+Yes, the migrated storage account has the same name and address as the classic account.
 
-### Can additional verbose logging be added as part of the migration process?
+### Can verbose logging be added as part of the migration process?
 
 No, migration is a service that doesn't have capabilities to provide additional logging.