@MNik Thanks for posting your query on Microsoft Q&A.
Migrating Classic Storage Accounts to Azure Resource Manager (ARM) can have some impact on your deployed clients and existing app installations.
Impact on Deployed Clients:
-The endpoint URL for your storage account may change after migration. If your client apps have the storage account URL hardcoded, you will need to update them to use the new endpoint.
-If the access keys or the method of generating Shared Access Signatures (SAS) tokens changes during the migration, you will need to update your web app to use the new keys or update the logic for generating SAS tokens.
-Any IP restrictions or firewall rules set up for the classic storage account may need to be reconfigured for the new ARM storage account.
Impact on Existing App Installations:
Web App Changes: If the endpoint of your storage account changes, your web app that generates signed URLs for client access will need to be updated to use the new endpoint. Also, ensure that your web app’s configuration is updated to reflect any changes in access keys or SAS token generation methods.
Client App Changes: If the web endpoint changes, the client application will need to be updated to point to the new web endpoint URL. Also, make sure that users receive the updated client application with the new endpoint URL.
Recommendations:
- Before migrating, plan the changes and test the new configuration in a staging environment to ensure that everything works as expected.
- Update any documentation related to your storage account endpoints, access keys, and SAS token generation methods.
- Inform your users about the changes and provide them with the updated client application if necessary.
Additional reading:
https://learn.microsoft.com/en-us/azure/storage/common/classic-account-migration-overview
https://learn.microsoft.com/en-us/azure/storage/common/classic-account-migration-process
If you have any questions, let me know in the comments.