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

We previously presentation Support ends August 31, 2024 for expired Azure classic storage accounts. Now that the expiration date has passed and Azure classic storage accounts are no longer supported, we have a few updates to share about planning and considerations for customers who haven’t migrated. Send the remaining classic storage accounts to Azure Resource Manager.

On or after November 1, 2024:

• The ability to perform write operations using classic service model APIs, including PUT and PATCH, is limited. You can only perform read and list operations using the classic service model API.
• The remaining classic storage accounts will be migrated to Azure Resource Manager on your behalf on a rolling schedule. Data will continue to be stored, but any application that uses the classic service model API to perform management plane operations will experience interruptions if it is actively using write operations. Write operations are only available through the Azure Resource Manager API after your account is migrated.
  • Note: This does not affect the availability of data plane APIs before, during, or after classic storage account migration.

Azure storage accounts in Azure Resource Manager offer the same features and new features, including:

• A management layer that simplifies deployment by allowing you to create, update, and delete resources.
• Resource grouping – You can deploy, monitor, manage, and apply access control policies to resources as groups.

To avoid service interruption, you must migrate your classic storage account to: Azure Resource Manager As soon as possible. Rather than waiting for Azure Storage to migrate the remaining classic storage accounts on your behalf, we recommend that customers self-service the migration using existing migration capabilities. This will help you migrate on schedule and minimize impact. We cannot guarantee that there will not be a service interruption if the migration is further delayed.

Required Action

To avoid service interruption: migrate Get a classic storage account as soon as possible. It also updates any management tasks in your code or application that target the classic deployment model. Read our article FAQ and Migration instructions For more information

Help and Support

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

FAQ

Q: I want to delete my account, but the action is blocked. How do I delete my account if write operations are blocked in the classic control plane?
A: After your account is migrated from the classic service model, you can delete it using the Azure Resource Manager API for Azure Storage.

Q: Can I manage classic storage accounts using legacy PowerShell cmdlets?
A: No. After your account is migrated, you can manage it using the latest PowerShell cmdlets for Azure Storage and Azure Resource Manager.

Q: In which resource group will migrated resources appear?

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 this pattern: – It has been relocated. For more information about the migration process, please visit: Understand storage account migration from the classic deployment model to Azure Resource Manager.