Migration from Classic to Basic/Standard/Premium takes a long time and/or fails about acr HOT 5 CLOSED

A quick update:
Just prior to Thanksgiving, we had a fix we were rolling out. The fix is still a temporary workaround until the permanent storage fix is deployed. However, as customers depend on Azure for their holiday shopping, we had an Azure wide blackout for deployments for Black Friday and the week of cyber monday. We plan to start the deployment December 4th, which will take the week to complete as we follow "Safe Deployment Practices", where we gradually roll out to concentric rings of regions. While it's possible your region will be available sooner than others, we need to wait until all regions are complete before we can enable the portal migration, through the overview tab, clicking update.
We appreciate your patience, and hope you understand we're working to "balance the needs of the many, over the needs of the few."
Steve

from acr.

Another quick update.
As we tested the upgrade with several customers, we found the workaround had a higher CPU utilization. To minimize the impact, we're completing our VM Scaleset work to auto-scale the registry backend if multiple customers are upgrading per region and putting a larger tax on the system.
We hope to have this completed by weeks end.
As noted above, you can use the az acr update command prior to the portal update. We just expect the Portal update to trigger far more users as we also promote the migration capability.
Thanks,
Steve

from acr.

For a approx. 200 GB upgrade from classic to Premium, what's the typical duration of the upgrade process? I just triggered it, and I am beginning to think that it was perhaps a bad idea, if it would take 24h+.

from acr.

@DonMartin76 - Did you face any issue during the migration?

from acr.

I'm happy to report the portal update has been rolled out. Customers with classic registries will be invited to upgrade to a managed registry. Upgrading through the portal is treated a bit special, when compared to the CLI. Using the az acr update CLI, you specify the target SKU. If your storage account doesn't fit, it will fail. You can, of course, upgrade to premium, then scale back down.
Using the portal, we will automatically pick the smallest SKU, based on the amount of storage you have.
Unless @DonMartin76 or others provide additional feedback we haven't seen, I'm hoping this is now resolved.
Thanks for your patience, and the customers that helped find and validated the fixes.
Steve

from acr.