Faced internal server error while migrating a Classic Storage account to Azure Resource Manager (ARM)

Question

Faced internal server error while migrating a Classic Storage account to Azure Resource Manager (ARM).

How to migrate when MS backend is non functional for the migration required of us, by them?

Answer 1

@Michael Meldgård Thornberg Welcome to Microsoft Q&A Forum, Thank you for posting your query here!
Adding more information to the above response!
For better understanding the issue: Can you please share the screenshot of the error message?
Can you try to migrate Classic Storage account o ARM using PowerShell or CLi and let me know the status?

If you are facing issues with the Azure backend, you can try the following steps to migrate your Classic Storage account to ARM:

1. Use the Azure Storage Explorer tool to copy the data from the Classic Storage account to a new ARM Storage account. You can download the Azure Storage Explorer tool from the following link: https://azure.microsoft.com/en-us/features/storage-explorer/
2. Once you have copied the data to the new ARM Storage account, you can update your application to use the new ARM Storage account.

After you have verified that your application is working correctly with the new ARM Storage account, you can delete the Classic Storage account.

This article catalogs the most common errors and mitigations during the migration of Classic to Azure Resource Manager migration

Identify classic storage accounts in your subscription: You can do this via the Azure portal or PowerShell2.

Locate and delete any disk artifacts in a classic account: Classic storage accounts may contain classic (unmanaged) disks, virtual machine images, and operating system (OS) images. To migrate the account, you will need to delete these artifacts first2. If you do not delete classic disk artifacts first, the migration may fail2.

Migrate your classic storage accounts: After deleting the disk artifacts, you can proceed with the migration2.

Update your applications to use Azure Resource Manager APIs: After the migration, ensure your applications are updated to use the Azure Resource Manager APIs

Addition information: How to migrate your classic storage accounts to Azure Resource Manager

https://stackoverflow.com/questions/73057732/error-migrating-azure-classic-storage-to-arm

If you are still facing issues, please open a support case and let me know the case number so I can track its progress.

---

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

Hi Michael , Welcome to MS Q&A

• Can you retry the operation again using Powershell or CLI Step-by-Step: Migrate your classic Cloud Services to ARM–Storage Migration.
• Recommended to use the below link and delete if there is any orphan disk object and images that might be impacting the storage account migration. https://learn.microsoft.com/en-us/azure/virtual-machines/migration-classic-resource-manager-ps?toc=%2Fazure%2Fvirtual-machines%2Fwindows%2Ftoc.json#step-52-migrate-a-storage-account

Please check this also --> Errors that commonly occur during Classic to Azure Resource Manager migration

If the issue still persists. I wish to engage with you offline for a closer look and provide a quick and specialized assistance,

Hope this helps!, kindly accept answer ,

Thanks

Deepanshu