GPv1 vs GPv2 tier/pricing differences

Shaik Ismail (AP) 0 Reputation points
2026-08-31T11:31:39.2433333+00:00

What would be the price difference between GPv1 and GPv2 for my account. I would like to understand it before migration.

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

4 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. TP 163.1K Reputation points Volunteer Moderator
    2026-08-31T12:52:53.52+00:00

    Hi,

    Below is excerpt from General Purpose v1 (GPv1) storage account retirement FAQ:

    How does pricing differ from GPv2?

    General-purpose v1 pricing differs from GPv2 in the following ways:

    • General-purpose v1 has lower transaction prices than GPv2.
    • General-purpose v1 has slightly higher capacity prices than GPv2.
    • For most workloads, GPv2 is cheaper overall once per-blob tiering and optimized capacity pricing are factored in.

    They have a GPv1 to GPv2 Billing Impact Estimator on GitHub you can deploy to Azure and use to estimate billing impact:

    https://github.com/microsoft/GPv1-Retirement-Cost-Estimator#gpv1-to-gpv2-billing-impact-estimator

    Please click Accept Answer and upvote if the above was helpful.

    Thanks. -TP

    Was this answer helpful?

    1 person found this answer helpful.
  2. Vinodh247-1375 44,716 Reputation points Volunteer Moderator
    2026-08-31T16:31:56.5933333+00:00

    The price difference between GPv1 and GPv2 is account-specific and depends on your storage usage patterns.

    In general:

    • GPv2 typically provides lower capacity (storage) pricing than GPv1.
    • Transaction charges are billed differently in GPv2, with pricing varying by operation type and access tier (Hot, Cool, Archive), whereas GPv1 uses a simpler transaction model.
    • As a result, accounts with large amounts of stored data and relatively few transactions often see cost savings after upgrading, while highly transactional workloads should be evaluated more carefully.

    To estimate the impact for your account:

    1. Use the Azure Pricing Calculator and compare GPv1 and GPv2 pricing for your region and redundancy option.
    2. Review your storage account metrics, especially Transactions, over at least one full billing cycle.
    3. In Azure Monitor Metrics, split transaction data by API Name to understand whether your workload is primarily reads, writes, or listing operations, since these can affect GPv2 costs differently.
    4. Consider whether you will benefit from access tiers (Hot, Cool, Archive) and Azure Storage Reserved Capacity, both of which are available with GPv2 and can further reduce long-term costs.

    Also keep in mind that the upgrade from GPv1 to GPv2 is a one-way operation, so it is worth validating expected costs and access tier settings before migrating.

    For pricing and migration guidance, see:

    Help make this community better for everyone: if this answer resolved your issue, please accept it or leave an upvote. If not, share more details in a comment so we can continue the discussion and find the right solution.

    Was this answer helpful?

    0 comments
  3. kagiyama yutaka 5,410 Reputation points
    2026-08-31T12:17:35.8266667+00:00

    I think the GPv1→GPv2 price change comes only from the stored GB and operation counts you enter into Azure’s pricing page, and any billing detail tied to your account is handled by Azure Support.

    Was this answer helpful?

    0 comments

  4. AI answer

    2026-08-31T11:31:55.0866667+00:00

    GPv2 uses a different pricing model than GPv1, so the price difference depends on workload pattern rather than account size alone.

    Supported pricing differences:

    • GPv1 usually has lower transaction prices than GPv2.
    • GPv1 usually has slightly higher capacity prices than GPv2.
    • GPv2 adds tier-based pricing for blobs: hot, cool, cold, and archive.
    • GPv2 can be cheaper overall for many workloads when per-blob tiering and optimized capacity pricing are used.
    • Read, write, and list-heavy workloads can cost more on GPv2 because transaction pricing differs and frequent operations may incur higher charges.
    • Upgrading from GPv1 to GPv2 changes Blob Storage billing only. Azure Files and Azure Disks pricing do not change.

    A practical way to estimate the difference before migration:

    1. Capture a monthly baseline for the account:
      • read operations
      • write operations
      • list/metadata operations
      • egress
      • stored capacity
    2. Compare GPv2 rates for the target region, redundancy, and blob tier on the Azure pricing page.
    3. Map data to the intended tiers and include early-deletion minimums for cool, cold, or archive if those tiers will be used.
    4. If lifecycle management will be used, include its transaction effects.
    5. Compare the current GPv1 bill with the modeled GPv2 bill.

    Microsoft also provides an open-source GPv1 to GPv2 Cost Estimator that can:

    • compare estimated GPv1 vs GPv2 costs
    • upload billing CSV data
    • show the effect of capacity, transactions, and access tiers
    • export results

    Cost optimization guidance for GPv2:

    • batch operations
    • write larger blocks
    • reduce broad list operations
    • move cold data out of the hot tier

    Important migration note: the upgrade is in-place, non-disruptive, and permanent.

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

    Was this answer helpful?

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.