Update on classic storage account retirement and upcoming changes for classic storage customers

We previously announced that support would end for retired Azure classic storage accounts on 31 August 2024. Now that we are past the retirement date and Azure classic storage accounts are not supported, we have some updates to share on our plans and the considerations for customers who have not migrated their remaining classic storage accounts to Azure Resource 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. 
  • Note: There are no impacts on the availability of the data plane APIs before, during, or after the migration of classic storage accounts.

Azure storage accounts under Azure Resource Manager provides the same capabilities 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.

To avoid service disruptions, you'll need to migrate your classic storage accounts to Azure Resource Manager as soon as possible. Our recommendation is that customers self-service their migrations using the existing migration capabilities instead of waiting for Azure Storage to migrate any remaining classic storage accounts on your behalf. This ensures that you can migrate on your schedule and minimize impacts. We cannot guarantee that you will not experience service interruptions if you further delay your migration.

Required action

To avoid service disruptions, migrate your classic storage accounts as soon as possible. Additionally, update any management operations in code or applications that target the classic deployment model. Read our FAQ and migration guidance for more information.

Help and support

If you have questions, get answers from community experts in Microsoft Q&A. If you have a support plan and you need technical help, open the Azure portal and select the question mark icon at the top of the page.

FAQ

Q: 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? 
A: 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.

Q: Will I be able to use the legacy PowerShell cmdlets to manage my classic storage accounts?
A: No. After your accounts have been migrated, they can be managed with the modern PowerShell cmdlets for Azure Storage and Azure Resource Manager. 

Q: What resource group will my migrated resources appear in? 

A: 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.