how to delete classic disk artifacts

Author: tamram

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

@@ -27,7 +27,7 @@ To list classic storage accounts in your subscription with the Azure portal:
 1. Navigate to the list of your storage accounts in the Azure portal.
 1. Select **Add filter**. In the **Filter** dialog, set the **Filter** field to **Type** and the **Operator** field to **Equals**. Then set the **Value** field to **microsoft.classicstorage/storageaccounts**.
 
-    :::image type="content" source="media/storage-account-migrate-classic/classic-accounts-list-portal.png" alt-text="Screenshot showing how to list classic storage accounts in Azure portal" lightbox="media/storage-account-migrate-classic/classic-accounts-list-portal.png":::
+    :::image type="content" source="media/classic-account-migrate/classic-accounts-list-portal.png" alt-text="Screenshot showing how to list classic storage accounts in Azure portal" lightbox="media/storage-account-migrate-classic/classic-accounts-list-portal.png":::
 
 # [PowerShell](#tab/azure-powershell)
 
@@ -60,9 +60,13 @@ To migrate a classic storage account to the Azure Resource Manager deployment mo
 1. In the **Settings** section, click **Migrate to ARM**.
 1. Click on **Validate** to determine migration feasibility.
 
-   :::image type="content" source="./media/storage-account-migrate-classic/validate-storage-account.png" alt-text="Screenshot showing how to migrate your classic storage account to Azure Resource Manager.":::
+   :::image type="content" source="./media/classic-account-migrate/validate-storage-account.png" alt-text="Screenshot showing how to migrate your classic storage account to Azure Resource Manager." lightbox="./media/classic-account-migrate/validate-storage-account.png":::
 
 1. After a successful validation, click on **Prepare** to begin the migration.
+
+  > [!IMPORTANT]
+  > There may be a delay of a few minutes after validation is complete before the Prepare button is enabled.
+
 1. Type **yes** to confirm, then select **Commit** to complete the migration.
 
 # [PowerShell](#tab/azure-powershell)
@@ -114,6 +118,19 @@ azure 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.
+
+To delete disk artifacts from the Azure portal, follow these steps:
+
+1. Navigate to the Azure portal.
+1. In the **Search** bar at the top, search for **Disks (classic)**, **OS Images (classic)**, or **VM Images (classic)** to display classic disk artifacts.
+1. Locate the classic disk artifact to delete, and select it to view its properties.
+1. Select the **Delete** button to delete the disk artifact.
+
+    :::image type="content" source="media/classic-account-migrate/delete-disk-artifacts-portal.png" alt-text="Screenshot showing how to delete classic disk artifacts in Azure portal." lightbox="media/classic-account-migrate/delete-disk-artifacts-portal.png":::
+
 ## See also
 
 - [Migrate your classic storage accounts to Azure Resource Manager by August 31, 2024](classic-account-migration-overview.md)

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

@@ -1,7 +1,7 @@
 ---
 title: We're retiring classic storage accounts on August 31, 2024
 titleSuffix: Azure Storage
-description: Overview - migrate your classic storage accounts to the Azure Resource Manager deployment model. All classic accounts must be migrated by August 31, 2024.
+description: Overview of migration of classic storage accounts to the Azure Resource Manager deployment model. All classic accounts must be migrated by August 31, 2024.
 services: storage
 author: tamram
 
@@ -16,7 +16,7 @@ ms.subservice: common
 
 The [Azure Resource Manager](../../azure-resource-manager/management/overview.md) deployment model now offers extensive functionality for Azure Storage accounts. For this reason, we deprecated the management of classic storage accounts through Azure Service Manager (ASM) on August 31, 2021. Classic storage accounts will be fully retired on August 31, 2024. All data in classic storage accounts must be migrated to Azure Resource Manager storage accounts by that date.
 
-Today, about x??? percent of Azure storage accounts are using Azure Resource Manager. 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).
+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.
 
@@ -59,7 +59,7 @@ For step-by-step instructions, see [Migrate a classic storage account to Azure R
 
 ## Unsupported features and known issues
 
-- [Customer-managed failover](https://supportability.visualstudio.com/AzureIaaSVM/_wiki/wikis/AzureIaaSVM/496078/Storage-Account-Failover_Storage?anchor=unsupported-storage-accounts)
+- [Customer-managed failover](storage-disaster-recovery-guidance.md) is not supported for classic storage accounts.
 - Challenges locating classic OS disks or images - https://supportability.visualstudio.com/AzureIaaSVM/_wiki/wikis/AzureIaaSVM/496154/Locate-Classic-OS-Disks-VM-Images-in-Storage-Account_Storage
 - Classic artifacts blocking storage account deletion - https://supportability.visualstudio.com/AzureIaaSVM/_wiki/wikis/AzureIaaSVM/496138/Delete-Classic-Storage-Account-Portal_Storage
 - Customers that only have internal billable Classic Storage and have no visibility into those resources and no ability to migrate those resources to ARM - https://supportability.visualstudio.com/AzureIaaSVM/_wiki/wikis/AzureIaaSVM/606146/Classic-Storage-Account-Retirement-Message_Storage 

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

@@ -1,7 +1,7 @@
 ---
 title: Understand storage account migration from classic to Azure Resource Manager
 titleSuffix: Azure Storage
-description: Deep dive - migrate your classic storage accounts to the Azure Resource Manager deployment model. All classic accounts must be migrated by August 31, 2024.
+description: Learn about the process of migrating classic storage accounts to the Azure Resource Manager deployment model. All classic accounts must be migrated by August 31, 2024.
 services: storage
 author: tamram
 
@@ -58,13 +58,9 @@ There are four steps to the migration process, as shown in the following diagram
 
 The Validation step is the first step in the migration process. The goal of this step is to analyze the state of the resources that you want to migrate from the classic deployment model. The Validation step evaluates whether the resources are capable of migration (success or failure). If the the classic storage account is not capable of migration, Azure lists the reasons why.
 
-#### Checks not done during the Validation step
-
 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.
 
-It's not possible to check for all issues that the Azure Resource Manager stack might impose on the storage account during migration. These issues are only checked when the resources undergo transformation in the next step of migration (the Prepare step). The following table lists all the issues not checked in the Validation step:
-
-???Charles - do we have anything here/need this section or a table like VMs have???
+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).
 
 ### Prepare
 
@@ -75,7 +71,7 @@ The Prepare step is the second step in the migration process. The goal of this s
 
 If the storage account is not capable of migration, Azure stops the migration process and lists the reason why the Prepare step failed.
 
-If the storage account is capable of migration, Azure blocks management plane operations for the storage account under migration. For example, you cannot regenerate the storage account keys while the Prepare phase is underway ???true? and what about data operations - not blocked at this step???. Azure then creates a new resource group ???in the same region??? as the classic storage account. The name of the new resource group follows the pattern `<classic-account-name>-Migrated`.
+If the storage account is capable of migration, Azure blocks management plane operations for the storage account under migration. For example, you cannot regenerate the storage account keys while the Prepare phase is underway. Azure then creates a new resource group as the classic storage account. The name of the new resource group follows the pattern `<classic-account-name>-Migrated`.
 
 > [!NOTE]
 > It is not possible to select the name of the resource group that is created for a migrated storage account. After migration is complete, however, you can use the move feature of Azure Resource Manager to move your migrated storage account to a different resource group. For more information, see [Move resources to a new subscription or resource group](../../azure-resource-manager/management/move-resource-group-and-subscription.md).
@@ -86,7 +82,7 @@ Finally, Azure migrates the storage account and all of its data and configuratio
 
 After the Prepare step is complete, both accounts exist in your subscription, so that you can review and compare the classic storage account in the pre-migration state and in Azure Resource Manager. For example, you can examine the new account via the Azure portal to ensure that the storage account's configuration is as expected.
 
-There is no set window of time before which you need to commit or abort the migration. You can take as much time as you need for the Check phase. However, management plane operations are blocked for the classic storage account (???what about new account?) until you either abort or commit.
+There is no set window of time before which you need to commit or abort the migration. You can take as much time as you need for the Check phase. However, management plane operations are blocked for the classic storage account until you either abort or commit.
 
 ### Abort