Learn Editor: Update classic-account-migration-overview.md

Author: schoag-msft

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

@@ -47,6 +47,12 @@ If your applications are using Azure Service Manager classic APIs to manage clas
 > [!WARNING]
 > If you do not migrate your classic storage account to Azure Resource Manager by August 31, 2024, you will no longer be able to perform management operations through Azure Service Manager.
 
+On or after 1 November 2024:
+
+- Your ability to perform write operations using the classic service model APIs, including PUT and PATCH, will be limited. You will only be able to perform read and list operations using the classic service model APIs.
+- Your remaining classic storage accounts will be migrated to Azure Resource Manager on your behalf on a rolling schedule. Your data will continue to be stored, but any applications that use the classic service model APIs to perform management plane operations will experience disruptions if you're actively using any write operations. Write operations will only be available through the Azure Resource Manager APIs after your account(s) have been migrated. Once migration is completed, you will see two storage accounts with the same name through interfaces such as the Azure Portal. This is by design. One account is your classic storage account and the other is your Azure Resource Manager and Storage Resource Provider account. To perform any management operations that udpate your storage account, you must use Azure Resource Manager and Storage Resource Provider APIs. 
+  - Note: There are no impacts on the availability of the data plane APIs before, during, or after the migration of classic storage accounts.
+
 ## What actions should I take?
 
 Before you get started with the migration, read [Understand storage account migration from the classic deployment model to Azure Resource Manager](classic-account-migration-process.md) for an overview of the process.
@@ -122,6 +128,18 @@ Any RBAC role assignments that are scoped to the classic storage account are mai
 
 Your storage account will be a general-purpose v1 account after the migration process completes. You can then upgrade it to general-purpose v2. For more information about upgrading your account, see [Upgrade to a general-purpose v2 storage account](storage-account-upgrade.md).
 
+### I want to delete my account, but the operation is blocked. How do I delete my account if write operations are blocked on the classic control plane? 
+
+You can delete your account using the Azure Resource Manager APIs for Azure Storage after your account has been migrated from the classic service model.
+
+### Will I be able to use the legacy PowerShell cmdlets to manage my classic storage accounts and their configuration?
+
+No. After your accounts have been migrated, they can be managed with the modern PowerShell cmdlets for Azure Storage and Azure Resource Manager to make updates to the configuration of your storage account, including performing delete operations. Note that read and list operations (for example, listing the access keys for your storage account) will continue to work using the legacy PowerShell cmdlets. You should also consider that the legacy PowerShell cmdlets for working with Azure Service Management resources is also unsupported and move such logic over to use the modern Azure PowerShell cmdlets.
+
+### What resource group will my migrated resources appear in? 
+
+Any classic storage accounts that are migrated on your behalf will be placed in a new resource group. The name of the new resource group follows the pattern <classic-account-name>-Migrated. For more information on the migration process, visit [Understand storage account migration from the classic deployment model to Azure Resource Manager](classic-account-migration-process.md). 
+
 ### Will the URL of my storage account remain the same post-migration?
 
 Yes, the migrated storage account has the same name and address as the classic account.