This is regarding the migration of the general-purpose v1 (GPv1) storage account to a general-purpose v2 (GPv2) storage account. We have just one storage account impacted. Is there any disruption expected if the account is migrated automatically to GPv2?

SRIVASTAVA, DIKSHA 0 Reputation points
2026-10-13T09:09:54.62+00:00

This is regarding the migration of the general-purpose v1 (GPv1) storage account to a general-purpose v2 (GPv2) storage account. We have just one storage account impacted. Is there any disruption expected if the account is migrated automatically to GPv2? Also, what will be the difference in pricing?

Azure Storage
Azure Storage

Globally unique resources that provide access to data management services and serve as the parent namespace for the services.

0 comments
Answer accepted by question author
Marcin Policht 110.3K Reputation points MVP Volunteer Moderator
2026-10-13T11:14:31.3+00:00

In short, there is no downtime, data loss, or service disruption expected when your Azure storage account is migrated to a general-purpose v2 storage account. The migration is an in-place upgrade that preserves the existing data, account name, service endpoints, and connection strings. Existing applications should continue to connect without configuration changes because of the upgrade. However, zero disruption should not be treated as an absolute guarantee, so review Microsoft's migration notice and validate any account-type-specific configurations before the change.

The pricing impact depends on the storage account's workload because GPv1 and GPv2 use different billing models. GPv2 can offer lower per-gigabyte storage costs, but transaction costs may be higher, depending on the operation type, region, redundancy, and applicable pricing tier. The actual result depends on the account's storage volume, read and write activity, and other usage patterns.

Cost component GPv1 GPv2
Data storage per GB Pricing depends on configuration Can be lower, depending on configuration
Operations and transactions Pricing depends on operation type Rates may be higher for some operations
Access tiers More limited options Supports Hot, Cool, Cold, and Archive tiers for applicable Blob Storage workloads
Data retrieval Depends on service and configuration Cooler tiers can incur additional retrieval charges

Since only one storage account is affected, review its actual consumption in Azure Cost Management and compare it with the estimated GPv2 charges using the same region, redundancy, storage volume, and transaction levels. You can use the Azure Blob Storage pricing page to check the applicable rates.

If the above response helps answer your question, remember to "Accept Answer" so that others in the community facing similar issues can easily find the solution. Your contribution is highly appreciated.

hth

Marcin

Was this answer helpful?

1 person found this answer helpful.
Answer accepted by question author

AI answer

2026-10-13T09:10:09.5266667+00:00

Automatic migration to GPv2 is expected to be non-disruptive.

  • No downtime is required.
  • Data is preserved; blobs, containers, and metadata remain intact.
  • Existing API/service endpoints remain unchanged, so most applications continue to work.
  • Temporary access impact is still called out as a risk if Microsoft performs the migration automatically, and auto-upgrade timing can vary.

For pricing differences after moving from GPv1 to GPv2:

  • GPv1 has lower transaction prices but slightly higher capacity prices.
  • GPv2 is cheaper overall for most workloads once per-blob tiering and optimized capacity pricing are considered.
  • Billing changes in GPv2 mainly come from:
    1. Read/write operation charges
    2. Tier-based pricing such as hot, cool, cold, and archive
    3. More redundancy options
  • For some workloads, GPv2 can be more expensive, especially depending on access patterns and transaction volume.
  • Azure Files and Azure Disks pricing do not change just because the underlying storage account is upgraded; the pricing impact applies to Blob Storage pricing.

If predictable timing and configuration choices matter, a proactive upgrade is preferable because it allows control over redundancy, tiering, and feature settings before Microsoft-initiated conversion.

AI-generated content may be incorrect. Read our transparency notes for more information.

Was this answer helpful?

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' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.