Azure Migration from Classic to Resource Manager. Prepare phase

Question

My WPF Apps are dot net 4.5.2 using WindowsAzure.Storage v 9.3.3 to access Azure storage.

My website is .NET 8.0 using Azure.Storage.Blobs v 12.19.1 to access Azure storage

I'm in the Prepare phase of migration from Classic to Resource Manager. My container is pdfs only. I see that adding a pdf to either the new Resource Manager or Classic causes the pdf to show in both. Makes sense as I think both are interfaces on the same underlying storage. I have a couple of WPF Apps and a Website adding and reading pdfs from Azure storage. All is working.

My confusion/question is since the connection string does not change for the classic version or the Resource Manager version, how do I know which one my Apps are using and if all is working is this success? Success meaning I'm ready to move to the commitment phase.

Answer 1

As you’ve noticed, adding a PDF to either the Classic or Resource Manager interface shows up in both because they share the same underlying storage account. This is expected behavior and confirms that both interfaces are accessing the same data.

Since the connection string remains unchanged, your applications will continue to interact with the same storage account, regardless of whether you’re using the Classic or Resource Manager interface. The connection string is tied to the storage account itself, not the management interface.

Since the connection string remains unchanged, your applications will continue to interact with the same storage account, regardless of whether you’re using the Classic or Resource Manager interface. The connection string is tied to the storage account itself, not the management interface.

Answer 2

@Bob Beasley Thanks for posting your query on Microsoft Q&A.

My confusion/question is since the connection string does not change for the classic version or the Resource Manager version, how do I know which one my Apps are using? How do I know if pdf came from the classic version or the Resource Manager version? 

The PDFs you are uploading / downloading are being transferred using data plane APIs. The migration from Classic --> ARM is a control plane operation. 

If all is working, is this success (meaning I'm ready to move to the commitment phase)?

If you have any tooling interacting with the classic control plane, the Validation phase is there to give you time to retool and point those updated tools to ARM. If you don't have any control plane tooling (e.g., you created this account a long time ago and now only use the data plane), you can move immediately to ARM.

As you guessed (correctly), migration is a metadata operation. Not a data movement operation. So, while it appears you have two storage accounts during the Validation phase - you in fact have one account / one data store. But it now has metadata in both Classic (ASM) and ARM. The Commit phase commits your metadata migration. Throughout the migration process, there are no impacts to the data plane - it remains available for reads and writes the entire time.

My WPF Apps are dot net 4.5.2 using WindowsAzure.Storage v 9.3.3 to access Azure storage.

Please note that any SDK <v12 is formally retired. This SDK and the other one you mentioned are both data plane SDKs and do not interact with the control plane. The migration of any accounts you have from Classic --> ARM would not be impacted by operations coming from these SDKs.

Hope that clarifies things. If not, please let me know what else you need.