Azure Archive Blob Storage Pricing Explained Azure Archive Blob Storage is built for data you must keep but rarely touch: compliance records, old backups, historical logs, and inactive datasets. The per-GB rate looks tiny, and that's the trap.

Retrieval, transactions, redundancy, data transfer, and early deletion can change the final bill materially. A team that archives data it later needs back can end up paying more than it would have in Cool.

This guide walks through current US pricing for East US, the main cost components, tier trade-offs, and a practical way to build and validate an estimate with Microsoft's own tools.

Key Takeaways

  • Archive pricing is usage-based, and rates shift with region and redundancy.
  • Cost drivers: capacity, operations, rehydration, redundancy, transfer, and the 180-day minimum.
  • Use Archive for data left untouched for months; active data often costs less in Cool, Cold, or Hot.
  • Budget on total cost, not the lowest per-GB rate.

How Much Does Azure Archive Blob Storage Cost? (Pricing Overview)

There's no universal fixed price. Rates vary by region, redundancy, billing terms, and usage.

Current US pricing snapshot

The figures below come from Microsoft's pricing page for East US, USD, Standard GPv2 block blobs, pay-as-you-go (retrieved November 18, 2026). Displayed prices are estimates, not quotes. Your agreement terms and purchase date can change the final amounts.

Archive meter LRS GRS / RA-GRS
Capacity, $/GB-month $0.00099 $0.00299
Writes, per 10,000 $0.10 $0.21
List/Create Container, per 10,000 $0.05 $0.10
Standard reads, per 10,000 $5 $5
High-priority reads, per 10,000 $50 $50
Standard retrieval, $/GB $0.02 $0.02
High-priority retrieval, $/GB $0.10 $0.10

A few details matter:

  • Archive supports LRS, GRS, and RA-GRS. ZRS, GZRS, and RA-GZRS are not supported.
  • Capacity rates are identical across all size bands.
  • Delete operations are free, but early-deletion charges are separate.
  • Reserved capacity is available in 100 TiB or 1 PiB units on one- or three-year terms. It excludes early deletion, operations, and transfer.
  • Lifecycle policies are free. The Set Blob Tier operations they execute are billed.

Example budget scenarios

These are illustrations built from the East US LRS rates above, not universal ranges.

Low-volume case: 10 TB (10,240 GB) of compliance records, with 1% retrieved in a month.

  • Storage: 10,240 GB × $0.00099 ≈ $10.14/month
  • Retrieval of about 102 GB at standard priority: ≈ $2.05
  • Reads for a few hundred blobs: pennies

Total: roughly $12 to $13 in a month with a small recovery.

Larger enterprise case: 500 TB (512,000 GB) in LRS, 1% retrieved monthly, 2 million files.

  • Storage: 512,000 × $0.00099 ≈ $507/month
  • Retrieval of about 5,120 GB at standard priority: ≈ $102
  • Reads, if 20,000 blobs are rehydrated: 2 reads × $5 ≈ $10
  • Switch to GRS and storage alone rises to about $1,531/month

One-time ingest of 2 million blobs adds about $20 in write charges ($0.10 per 10,000). If you move to GRS, geo-replication at $0.02/GB adds around $10,240 for the initial copy. That single line can dwarf months of storage.

Azure Archive storage scenario costs comparing LRS and GRS

What the quoted price includes and excludes

The storage rate covers data at rest. Transactions, retrieval, rehydration, transfer, replication, and related Azure services bill separately. Never reuse a price from another region or redundancy type. Recalculate.

Key Factors and Cost Breakdown of Azure Archive Blob Storage

Think of monthly spend as stored data plus access, retrieval, retention, redundancy, transfer, and any enabled features.

Storage capacity and Archive tier selection

Billing uses average daily stored GB across the month, and both data and metadata count. Growth raises the base charge gradually.

Archive applies only to block blobs. Microsoft documents it for long-term backups, archival datasets, and retained raw originals. It is a poor fit for anything needing immediate reads or frequent modification.

Tier Minimum retention Latency
Hot None Milliseconds
Cool 30 days Milliseconds
Cold 90 days Milliseconds
Archive 180 days Hours

Transactions, retrieval, and rehydration

Reads ($5 per 10,000) and retrieved GB ($0.02) are separate meters. Millions of small objects mean millions of operations, so the read line can outgrow capacity.

Archived data is offline. You must rehydrate it first:

  • Standard priority: may take up to 15 hours for objects under 10 GB.
  • High priority: may finish in under an hour for objects under 10 GB, but size and demand can extend that. It is not a guaranteed one-hour recovery.
  • Set Blob Tier: moves the existing blob to Hot, Cool, or Cold. Early deletion may apply.
  • Copy Blob: creates an online copy while the source stays archived, so there's no early deletion on the source, but both copies bill for storage.

Azure Archive rehydration options and recovery timing comparison

Archived versions and snapshots can't be rehydrated directly. Copy them to a new online blob, as Microsoft's rehydration guide describes.

Minimum retention and early deletion

Archive has a 180-day minimum. Delete, overwrite, or re-tier earlier and you pay prorated storage for the remaining days. Remove a blob after 45 days and you're charged for the other 135.

That's why temporary files, short-lived backups, and data likely to be re-tiered soon don't belong here.

Redundancy, region, and data transfer

GRS and RA-GRS roughly triple the capacity rate compared with LRS. Geo-replication to the secondary region costs $0.02/GB, including when you convert from LRS.

Transfer is a different meter from retrieval:

  • Inbound transfer is free.
  • Internet egress: first 100 GB/month free, then $0.087/GB for the next 10 TB.
  • Inter-region transfer within North America: $0.02/GB.

Object size and additional features

Microsoft announced a minimum billable object size for Cool, Cold, and Archive, then paused it. Billing will not change on July 1, 2026, and no new date has been given. Check the Azure updates page before you lock in a budget that depends on this.

Optional features can add charges, so include only those you use:

  • Versioning and snapshots: unique blocks add capacity, and explicit tier changes can make full object lengths billable.
  • Change feed: metered per 10,000 changes.
  • Blob inventory: charged per million objects scanned.
  • SFTP: hourly while enabled, plus transactions and networking.
  • Encryption scopes: blobs using one cannot be archived.

Low-Cost vs. High-Cost Archive Storage: What's the Difference?

Same tier, very different bills. The gap comes from how the data behaves.

Storage price versus access economics

Low cost: data is rarely read and stays past 180 days. Capacity at about $1 per TB-month is hard to beat.

High cost: repeated retrievals, high-priority access at $0.10/GB and $50 per 10,000 reads, and heavy transaction volume erase the savings. Pull the same 10 TB back at high priority and retrieval alone is about $1,024.

Performance and availability

Archive data is offline, so every access begins with a rehydration workflow and a wait. If a restore must start within minutes, Cold, Cool, or Hot fits better, even at a higher storage rate. All three serve reads in milliseconds.

Retention and lifecycle

Archive works for immutable, long-lived data with predictable retention. Data that may be deleted, overwritten, or moved before day 180 triggers charges you could have avoided.

Lifecycle policies can cool current versions, previous versions, and snapshots. They cannot rehydrate Archive data, and changes can take up to 24 hours to take effect. Per Microsoft's lifecycle documentation, tiering is unsupported in premium block blob accounts.

Data organization and object size

Consolidating small files and compressing before upload reduces both write and read counts. Millions of tiny objects, frequent metadata operations, and sloppy lifecycle transitions do the opposite.

Best-fit use cases

  • Archive: regulatory retention, historical records, completed project data, disaster-recovery copies rarely touched.
  • Cold, Cool, Hot, or another service: active analytics, application content, fast-changing data, or strict recovery-time targets.

How to Estimate the Right Azure Archive Budget

Base the estimate on workload behavior and retention rules, not the Archive rate alone.

Inputs to collect before estimating

  • Current and projected capacity, plus monthly growth
  • Object count and size distribution
  • Expected reads, writes, and retrieval volume
  • Rehydration priority
  • Retention period
  • Region and redundancy
  • Expected data movement out of Azure

Separate predictable baseline data from temporary, frequently accessed, or compliance-constrained data. Each category may deserve a different tier.

Estimation workflow

  1. Price base storage: stored GB × capacity rate for your region and redundancy.
  2. Add transactions: write count × operation rate, normally priced per 10,000.
  3. Add recovery: read count plus retrieved GB at the chosen priority.
  4. Add early-deletion exposure: remaining days on anything likely to move early.
  5. Add redundancy, transfer, and feature charges.
  6. Model three scenarios: low access, expected access, high access.

Then validate in the Azure Pricing Calculator and against the Blob Storage pricing page. Sign in to surface negotiated pricing. Cost Management adds budgets, forecasts, and threshold alerts at subscription or resource-group scope.

What most people miss on Archive cost

Comparing per-GB rates alone ignores retrieval delays, transaction pricing, early deletion, redundancy, and egress. A cheaper tier on paper can cost more in practice.

Lifecycle policies cut manual tier management, but you still need to watch access patterns, retention compliance, object growth, and surprise retrievals.

If your environment also runs Azure Managed Disks or other cloud block storage, keep those costs separate from Blob. Lucidity focuses on that layer: AutoScaler works across AWS, Azure, and Google Cloud, monitors block storage, learns usage patterns, and optimizes without infrastructure changes, cutting block storage costs by up to 70%. It does not price Archive Blob, so use Microsoft's tools for object storage estimates.

Conclusion

Archive can be a very economical home for data that is rarely accessed, held past the 180-day minimum, and stored with the right redundancy. The headline rate is only the start.

A sound estimate includes storage, transactions, retrieval, rehydration, retention, transfer, and your own access assumptions. Before committing to a design, verify current regional rates in Microsoft's calculator and rate card.

Frequently Asked Questions

How much does a blob cost?

It depends on access tier, stored volume, region, redundancy, operations, retrieval, and transfer. General Blob rates differ from Archive's, so check Microsoft's current rate card for your configuration.

Is blob deprecated?

No service-wide retirement of Azure Blob Storage has been published. Notices cover legacy account types: classic accounts retired August 31, 2024, and GPv1 and legacy BlobStorage accounts are being migrated to GPv2 after October 13, 2026.

Does Azure blob storage have a file size limit?

Yes, by blob type. A block blob tops out near 190.7 TiB (50,000 blocks of up to 4,000 MiB), a single Put Blob is 5,000 MiB, and a page blob is 8 TiB.

What is the minimum retention period for Azure Archive Blob Storage?

180 days. Deleting, overwriting, or re-tiering earlier triggers a prorated charge for the remaining days.

Is Azure Archive cheaper than Cool or Cold Blob Storage?

Archive has the lowest at-rest rate, but retrieval costs, hours of rehydration delay, and the 180-day commitment are higher. Compare total cost against how often the data is actually read.

How do I calculate Azure Archive Blob Storage costs?

Gather capacity, growth, operations, retrieval, retention, redundancy, region, and transfer. Then validate the model in the Azure Pricing Calculator.