classic account migration: add links to VM disk error info

Author: tamram

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

@@ -28,20 +28,13 @@ On August 31, 2024, we'll retire classic Azure storage accounts and they'll no l
 - 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 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:
@@ -76,9 +69,14 @@ 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 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 happens to existing classic storage accounts after August 31, 2024?
 

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

@@ -7,7 +7,7 @@ author: tamram
 
 ms.service: storage
 ms.topic: conceptual
-ms.date: 04/12/2023
+ms.date: 04/13/2023
 ms.author: tamram
 ms.subservice: common
 ---
@@ -33,6 +33,9 @@ You can migrate your classic storage account with the Azure portal, PowerShell,
 Before you start the migration:
 
 - Ensure that the storage accounts that you want to migrate don't use any unsupported features or configurations. Usually the platform detects these issues and generates an error.
+
+    If you are migrating Azure virtual machines (VMs) that include disks in classic storage accounts, be sure to familiarize yourself with the process of VM migration. For information about unsupported features and configurations, see [Overview of platform-supported migration of IaaS resources from classic to Azure Resource Manager](../../virtual-machines/migration-classic-resource-manager-overview.md#unsupported-features-and-configurations). For a list of errors that may occur in relation to classic disk artifacts, see [Common errors during Classic to Azure Resource Manager migration](../../virtual-machines/migration-classic-resource-manager-errors.md#list-of-errors).
+
 - Plan your migration during non-business hours to accommodate for any unexpected failures that might happen during migration.
 - Evaluate any Azure role-based access control (Azure RBAC) roles that are configured on the classic storage account, and plan for after the migration is complete.
 
@@ -59,7 +62,7 @@ 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.
 
-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. For more information, see the following articles:
+The Validation step does not check for VM disks that may be associated with the storage account. You must check your storage accounts manually to determine whether they support VM disks. For more information, see the following articles:
 
 - [Migrate classic storage accounts to Azure Resource Manager](classic-account-migrate.md)
 - [Migrate VMs to Resource Manager with PowerShell](../../virtual-machines/migration-classic-resource-manager-ps.md#step-52-migrate-a-storage-account)