This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
On 31 August 2024, we'll retire classic Azure storage accounts and they'll no longer be accessible. Before that date, you'll need to migrate them to Azure Resource Manager, which 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.
Beginning 1 August 2022, you'll no longer be able to create new classic storage account resources, however, resources created before that date will be supported through 31 August 2024.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(192, 22%, 28%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ETZ%3C/text%3E%3C/svg%3E)
Hello,
I would also like to know if migrating from ASM to ARM will affect our C# API coding, CDN URLs, etc. Can you please let us know if we need to plan configuration updates to our systems for the migration?
T.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(297.6, 21%, 38%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EVY%3C/text%3E%3C/svg%3E)
Hello,
We keep getting email reminders to migrate our classic storage accounts to Azure Resource Manager. When we follow the instructions to do so, we do not have the option to Migrate under Services. Also, from what I can tell, none of our storage accounts are listed as classic. Is everyone getting the reminders regardless of whether they have classic storage accounts or not? Or is there something wrong since we do not see the Migrate option?
Thanks!
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(22.400000000000002, 13%, 12%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ER%3C/text%3E%3C/svg%3E)
I’d like to know as well, if migration will result in new CDN Urls so that we’ll have to update our app once migrated, or CDN remains the same.
I saw Rick asking the same above but didn’t see any answer.
Kindly let us know @deherman-MSFT
To avoid losing access to your data, review Azure Resource Manager pricing and migrate your classic storage accounts before 31 August 2024.
If you have any additional questions regarding this retirement, please use this thread to ask your specific queries and we will try our best to answer them. Thank you!
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(137.6, 49%, 23%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ETJ%3C/text%3E%3C/svg%3E)
After August 1 2022, can we generate and save new files in an existing storage account until August 2024?
Beginning 1 August 2022, you'll no longer be able to create new classic storage account resources.
It is not clear to me if this means we can still use our already existing storage account until 2024, or we can only view the information in the storage account until 2024.
Yes, any subscriptions/classic storage accounts that were created before August 2022 will continue to be fully functional and supported until the retirement date (31 August 2024).
A few questions to start with:
Background: Our product started using Azure Storage in 2012. We access via C# in Visual Studio using Microsoft.WindowsAzure.Storage. I upgraded to newer Azure Storage libraries a few times, but at some point the library changed in a way that wasn't backward compatible, and it would have been a huge amount of work and re-testing to use it. So we stuck with the older version - v4.0.30319. (Presumably it shouldn't matter since it's all HTTP on the back end.)
We also use an Azure Storage-backed CDN (for static resources), and direct URLs to Azure Storage blobs for certain public resources.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(16, 83%, 11%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAJ%3C/text%3E%3C/svg%3E)
When migrating from classic storage to Azure Resource Manager, are there any configuration changes needed for applications using the storage?
For example, I have a .NET web app that connects to my classic storage via a connection string. Will the connection string (which includes AccountName and AccountKey) change?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(304, 95%, 39%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EKS%3C/text%3E%3C/svg%3E)
I have facing Migrate to ARM validate failed.
Error Message as below:
Virtual Network:
Virtual Network Group xxx xxxx has encountered validation failures, and hence it is not supported for migration. Please go through resolutions for common migration errors at https://aka.ms/vm-migration-errors. If you have a technical support plan, contact support else use https://aka.ms/vm-vnet-validate-support free support link for migration assistance.
Cloud Service
Deployment xxxx in Cloud Service xxxx has encountered validation failures, and hence it is not supported for migration.
Virtual Machine
VM xxxx in HostedService xxxx is currently configured with the Azure Backup service and therefore currently not supported for Migration. To migrate this VM, please follow the procedure described at https://aka.ms/vmbackupmigration.
anyone can help on this issue? thanks a lot