Migrate your general-purpose v1 (GPv1) storage account to a general-purpose v2 (GPv2) storage account by 13 October 2026

Question

I have identified 4 storage accounts that need to be upgraed to v2 and some of the documentation says the only databricks will be auto updated but the email says -

"After 13 October 2026, all existing GPv1 storage accounts will be automatically migrated over to a GPv2 account, which may result in higher billing costs. Your decision not to migrate an existing GPv1 storage account will be construed as consent for Microsoft to migrate the account on your behalf.

Any non-Azure Databricks accounts that use GPv1 will require manual migration."

So my question is if we do not manually upgrade them will they automatically get upraded by Microsoft or do we need to manually migrate them anyway. The 4 are of kind "storage".

Answer 1

I think GPv1 accounts are moved to GPv2 by Azure after 13 October 2026, and manual upgrade is only for controlling the timing or settings. Databricks GPv1 may be upgraded earlier, and all GPv1 accounts are migrated by Azure after the deadline.

The manual migration mentioned in the email does not mean u are required to upgrade urself, it means that non‑Databricks GPv1 accounts are not upgraded early by Azure.

If you do nothing, Azure will still migrate the account for you after the deadline. You can check the account kind in Storage Account → Configuration.

Answer 2

Yes. If those four GPv1 accounts of kind Storage are not manually upgraded, Microsoft will automatically migrate them to GPv2 by the retirement deadline.

Supported points from the documentation:

• GPv1 storage accounts are being retired.
• If a GPv1 account is not migrated by the deadline, it will be auto migrated to GPv2 by Microsoft.
• That automatic migration may result in higher billing costs.
• The upgrade is non-disruptive, with no downtime and no data loss.
• Existing endpoint names and data are retained.
• Once upgraded from GPv1 to GPv2, the change is permanent and can't be reverted.

For those four accounts, manual migration is still the better approach because it lets the workload owner validate:

1. Pricing impact under GPv2.
2. Any application logic that depends on the account kind.
3. Tiering, redundancy, and feature settings before the forced migration.
4. Testing in a staging environment before production.

If technical help is needed, create a support request in Azure portal under:

1. Help + support
2. Create a support request
3. Issue type: Technical
4. Service type: Storage Account Management
5. Problem type: Upgrade or change account type, tier or replication
6. Problem subtype: Upgrade to general purpose v2 storage account

---

• About the retirement of general-purpose v1 (GPv1) storage accounts
• About the retirement of general-purpose v1 (GPv1) storage accounts
• Upgrade to a general-purpose v2 storage account
• General Purpose v1 (GPv1) storage account retirement FAQ