I need an classic storage account to be able to upsize a classic cloud service to a VM size I can migrate to ARM.

Question

How can I create a temporary classic storage account so I can redeploy my classic cloud service as a larger VM size so I can migrate it to ARM? The old classic storage account was inadvertently deleted.The classic cloud service needs it to be able to deploy the larger VM size so I can migrate it.

Answer 1

Hi Michael Buck - Thanks for reaching out over Q&A Forum.

Beginning 1 August 2022, you'll no longer be able to create new classic storage account resources.

https://azure.microsoft.com/en-us/updates/classic-azure-storage-accounts-will-be-retired-on-31-august-2024/

So unfortunately, there doesn't seem to be an option to create a classic out on temporary basis

In case the account has been deleted very recently, you can reach out to support team to check on the feasibility of any kind of recovery on best effort basis. If that's not possible, then you might have to spin a new account and populate the data ahead in that.

Hope that helps!

Please let me know if there are any further queries/concerns, will be glad to assist.

---

Please do not forget to "Accept the answer” and “up-vote” wherever the information provided helps you, this can be beneficial to other community members.

Answer 2

in addition to @Anonymous

instead of classic storage, you can create a new ARM-based storage account. This new storage account can be used for your migration process.

https://learn.microsoft.com/en-us/azure/templates/microsoft.storage/storageaccounts?pivots=deployment-language-bicep

Answer 3

Hello Michael Buck,

 

Greetings! Welcome to Microsoft Q&A Platform.

 

 

Creating of temporary classic storage account is "NO" longer possible because of "NEW" deployment model now offers extensive functionality for Azure Storage accounts. The reason is Classic storage accounts are created using existing Service Management API's The newer storage accounts are created with the new Azure Resource Manager (ARM) API's (which are also wrapped in PowerShell and CLI now). Ultimately, they provide the same resources to your apps, but they're created/managed differently, and there are a few nuanced differences (such as the ability to tag resources that are created via ARM scripts).

 

To redeploy your classic cloud service as a larger VM size you need to change the size of an existing role, you can change the virtual machine size in the service definition file (csdef), repackage your Cloud Service and redeploy it. Here are the Available sizes for Azure Cloud Services: https://learn.microsoft.com/en-us/azure/cloud-services-extended-support/available-sizes, https://learn.microsoft.com/en-us/azure/cloud-services/cloud-services-sizes-specs

 

As mentioned above you can reach the support for recovering the storage account on any options and try migrating it to ARM based storage account refer-https://learn.microsoft.com/en-us/azure/storage/common/classic-account-migrate?tabs=azure-portal. You can also migrate Classic Storage Accounts to ARM from within Azure, https://learn.microsoft.com/en-us/azure/virtual-machines/migration-classic-resource-manager-overview

 

Similar SO thread: https://stackoverflow.com/questions/32619221/difference-between-new-and-classic-storage-accounts-in-azure

 

 

Hope this answer helps! please let us know if you have any further queries. I’m happy to assist you further.

 Please "Accept the answer” and “up-vote” wherever the information provided helps you, this can be beneficial to other community members.