Azure Blob Storage Tiers: Hot, Cool and Archive Explained Azure Blob Storage access tiers let you match unstructured data to how often it's read, how fast it must come back, and how long it must stay put. Backups, logs, media, and datasets rarely share one profile.

Picking a tier on the per-GB price alone is where teams get burned. Access operations, retrieval fees, early-deletion charges, redundancy, and data transfer all change the bill. Microsoft's own guidance notes that cost estimation separates capacity, operations, retrieval, and transfer.

This guide compares Hot, Cool, Cold, and Archive: how each works, where it fits, and how to choose.

Key Takeaways

  • Colder tiers trade lower storage prices for higher access costs, retention minimums, or slower retrieval.
  • Hot, Cool, and Cold stay online with millisecond access; Archive does not.
  • Archive is the cheapest to store but needs rehydration before any read.
  • Choose by access pattern, latency, retention, and total cost, not storage price alone.

What Is Azure Blob Storage and Why Do Access Tiers Matter?

Azure Blob Storage is Microsoft's object storage for large volumes of unstructured data: documents, images, audio and video, logs, backups, and datasets. An access tier tells Azure how to price and serve a blob based on expected access frequency. Warmer tiers favor availability and cheap access. Colder tiers favor cheap storage.

Scope: this article covers standard block blobs in general-purpose v2 (GPv2) and legacy Blob Storage accounts. Premium block blob accounts are separate, and their blobs can't move through these tiers. Azure Managed Disks and other storage services are also out of scope.

A bad tier choice costs money in two directions:

  • Dormant data sitting in Hot pays top capacity rates for nothing.
  • Active data in a colder tier racks up read charges, latency, and early-deletion fees.

New GPv2 accounts default to Hot, and individual blobs can override the account default. Archive can't be the account default.

Azure Blob Storage Access Tiers

Each tier is "optimized to support a particular pattern of data usage," per Microsoft's training material. Confirm current terminology, account support, and regional availability on Microsoft Learn before you commit.

Hot access tier

Hot is the online tier for active data: application workloads, analytics, reporting, and content delivery, plus staging data before it moves to a cooler tier. It has the highest capacity cost but the lowest access and transaction costs.

  • Availability: 99.9% (99.99% for RA-GRS reads)
  • No minimum retention period
  • Supports every redundancy configuration

Hot suits active datasets, current logs, and frequently served media. It's wasteful for older data nobody touches.

Cool access tier

Cool holds infrequently accessed data that still needs immediate reads and writes, with no rehydration. Typical uses are short-term backups, older data, and datasets awaiting processing.

  • Minimum duration: 30 days in GPv2 (none in legacy Blob Storage)
  • Availability: 99% (99.9% for RA-GRS reads)
  • Lower capacity cost, higher access and transaction costs than Hot

Early deletion matters here. Delete, overwrite, or re-tier a blob before 30 days and you're charged for the remaining days. Delete after 21 days and 9 days are still billed. Note that this is a billing rule, not a lock.

Cool gets expensive when data is read often, moved repeatedly, or hit with many small operations.

Cold access tier

Cold sits between Cool and Archive. It's still online with millisecond access, but priced for data kept longer and read rarely. Microsoft announced general availability on August 10, 2023, positioning its capacity price below Cool, with higher read prices.

  • Minimum duration: 90 days in GPv2
  • Availability: 99% (99.9% for RA-GRS reads)
  • Object replication supports Hot, Cool, and Cold

Good fits include long-retention backups, historical datasets, and compliance content that must stay directly readable. Model the access charges carefully, since cheaper capacity can be erased by a few unexpected reads.

Archive access tier

Archive is offline storage for data you must keep but rarely touch: long-term backups, compliance records, preserved raw data. Content can't be read or modified until you rehydrate it to an online tier. Metadata stays readable, and listing still works.

  • Minimum duration: 180 days
  • Redundancy: LRS, GRS, and RA-GRS only (no ZRS variants)
  • Lowest capacity cost, highest access and transaction costs

Rehydration options:

Method What happens
Set Blob Tier Blob changes tier in place; stays Archive while pending; leaving before 180 days can trigger early-deletion charges
Copy Blob Creates a separate online copy; the archived source stays unchanged

Standard priority can take up to 15 hours for objects under 10 GB. High priority may finish in under an hour for objects under 10 GB, but it's not guaranteed, and it's capped at 10 GiB per account per hour.

Azure Archive rehydration priorities and retrieval time comparison

Use Archive when hours of delay are fine and access is truly rare. Skip it for active applications, frequent investigations, or uncertain access needs.

The four tiers side by side

Property Hot Cool Cold Archive
Access Online Online Online Offline
Availability 99.9% 99% 99% 99%
Minimum duration None 30 days 90 days 180 days
First-byte latency Milliseconds Milliseconds Milliseconds Hours
Capacity / access cost Higher / lower Lower / higher Lower / higher Lowest / highest

Azure Blob Storage Hot Cool Cold Archive tier comparison

Cool and Cold minimums apply to GPv2, not legacy accounts. For current dollar rates, use Microsoft's pricing calculator rather than any fixed figure quoted in an article.

How to Choose the Right Azure Blob Storage Access Tier

The cheapest advertised rate is rarely the cheapest outcome. Work through these checks in order.

  1. Measure access behavior. Microsoft's guidance centers on the percentage of data read each month. Review last-access telemetry and container-level patterns periodically.
  2. Match retention. How long must data stay, and how often will it be deleted or moved? Minimum durations only hurt when data leaves early.
  3. Model total cost. Include capacity, read and write transactions, retrieval, early deletion, redundancy, regional pricing, and egress. Cool, Cold, and Archive downloads carry per-GiB retrieval fees on top of transactions.
  4. Check workload quirks. Every read or write is a billable operation, so many small files add up. Packing them into TAR or ZIP archives cuts operation counts.
  5. Confirm feature fit. Check immutability, replication, and downstream service compatibility.

Five-step Azure Blob Storage access tier selection workflow

Immutability policies allow tier changes but block lifecycle deletion, so tiering and deletion protection are separate concerns.

Automate with lifecycle management

Lifecycle policies move blobs between tiers automatically. Conditions can use days since creation, modification, or last access, with filters on prefix or blob index tags.

  • Actions: tierToCool, tierToCold, tierToArchive, and delete
  • Up to 100 rules per policy
  • Optional promotion of accessed Cool blobs back to Hot
  • Policies are free; the Set Blob Tier operations they trigger are billed

Changes can take 24 hours to start, and runs can take days. Lifecycle policies can't rehydrate Archive blobs, and last-access conditions require access tracking to be enabled.

Test rules on representative data, then watch actual costs after rollout.

What to Check Before Finalising an Azure Blob Storage Tier

What to Check Before Finalizing an Azure Blob Storage Tier

Avoid these common mistakes:

  • Leaving everything in Hot or applying one universal policy. Classify datasets by access pattern, business criticality, retention, and recovery needs first.
  • Moving data to Cold or Archive for price alone. Check minimum retention, retrieval charges, rehydration time, small-object effects, and the cost of an unexpected read.
  • Skipping validation. Confirm current feature support, regional pricing, redundancy choice, lifecycle behavior, and application compatibility.

One more point: Microsoft paused its planned minimum billable object size change for Cool, Cold, and Archive, so recheck billing updates before modeling small objects.

If your environment also includes Azure Managed Disks or AWS and Google Cloud block volumes, that's a different layer. Lucidity's multi-cloud platform provides visibility and autonomous optimization for cloud block storage, not Blob access-tier lifecycle automation.

Lucidity Lumen offers evidence-backed disk-tier recommendations based on IOPS, throughput, latency, and cost. AutoScaler expands and shrinks disks with zero downtime.

Conclusion

Blob tiers exist to align storage economics with access needs. Hot, Cool, Cold, and Archive each serve a different workload profile, and the right one depends on more than a headline price.

Put that into practice with a few disciplined steps:

  • Audit real access patterns before you move data
  • Model every cost component, not just storage rates
  • Automate transitions carefully and monitor after each change

Frequently Asked Questions

What are the differences between the Hot, Cool, and Archive access tiers in Azure Blob Storage?

Hot is online for active data with the highest storage cost and lowest access cost. Cool is online for infrequent access with a 30-day minimum. Archive is offline and cheapest to store, needs hours of rehydration, and has a 180-day minimum, while Cold sits between Cool and Archive.

What are the different storage tiers in Azure Blob Storage?

Hot, Cool, Cold, and Archive. Hot suits frequent access, Cool suits infrequent access, and Cold suits rare access; all three stay online. Archive is offline long-term retention.

What is the Archive tier in Azure Blob Storage?

Archive is for rarely accessed, long-term retention. Blobs must be rehydrated before reading or modifying. Expect retrieval charges and a 180-day minimum.

How do I choose the right Azure Blob Storage access tier?

Assess access frequency, latency needs, retention, transaction volume, and retrieval needs. Then model total cost, not just storage price.

What is the difference between Azure Blob Storage Cool and Cold tiers?

Both give millisecond online access and the same published availability. Cool has a 30-day GPv2 minimum versus 90 for Cold. Cold has lower capacity pricing but higher read pricing.

Can Azure Blob Storage tiers be changed automatically?

Yes. Lifecycle management transitions blobs by age or last access. Test rules first, and account for minimum-retention and early-deletion charges.