Share via

Unsure if code changes are needed for classic storage account migration

Frank Ma 40 Reputation points
2024-08-12T09:00:23.9266667+00:00

I have a Cloud Service (extended support) that accesses a Storage Account (classic) which I'm currently looking to migrate to a Storage Account managed through ARM.

Looking at this page of the migration documentation, step 4 of "What actions should I take" says the following:

Check your applications and logs to determine whether you're dynamically creating, updating, or deleting classic storage accounts from your code, scripts, or templates. If you are, then you must update your applications to use Azure Resource Manager APIs for account management. For more information, see Update your applications to use Azure Resource Manager APIs.

The cloud service currently using the older Microsoft.WindowsAzure.Storage.Blob library, but is only used to upload/download files, and doesn't dynamically create, update, or delete storage accounts. Can I expect it to continue to function after the migration cut-off date of August 31st? Or is there a way to make my own changes as to simulate the behaviour after the deadline has hit?

Thanks.

Azure Cloud Services
Azure Cloud Services
An Azure platform as a service offer that is used to deploy web and cloud applications.
704 questions
Azure Storage Accounts
Azure Storage Accounts
Globally unique resources that provide access to data management services and serve as the parent namespace for the services.
3,243 questions
Azure Blob Storage
Azure Blob Storage
An Azure service that stores unstructured data in the cloud as blobs.
2,940 questions
0 comments
Accepted answer
  1. Sumarigo-MSFT 47,106 Reputation points Microsoft Employee
    2024-08-12T14:45:00.3633333+00:00

    @Frank Ma Welcome to Microsoft Q&A Forum, Thank you for posting your query here!

    If your Cloud Service is only using the older Microsoft.WindowsAzure.Storage.Blob library to upload/download files and is not dynamically creating, updating, or deleting storage accounts, then you should be able to continue using the library after the migration cut-off date of August 31st.

    However, it is still recommended to update your applications to use Azure Resource Manager APIs for account management, as this will ensure that your applications are using the latest and most secure APIs for managing storage accounts.

    If you do decide to update your applications to use Azure Resource Manager APIs, you can follow the guidance provided in the documentation to make the necessary changes to your code, scripts, or templates. This will involve updating your code to use the latest Azure Storage SDK, which supports both classic and ARM storage accounts.

    If you choose not to update your applications to use Azure Resource Manager APIs, you should still be able to continue using the older Microsoft.WindowsAzure.Storage.Blob library to upload/download files, but you may not be able to take advantage of the latest features and security enhancements provided by Azure Storage.

    Note: To simulate the behavior after the deadline, you could consider setting up a test environment to migrate your Cloud Service (extended support) and Storage Account (classic) to ARM and observe the behavior of your application using the Microsoft.WindowsAzure.Storage.Blob library. This would give you an indication of any potential issues that might arise post-migration.

    Please let us know if you have any further queries. I’m happy to assist you further.    

    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.

    1 person found this answer helpful.

0 additional answers

Sort by: Most helpful
Most helpful Newest Oldest

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.