What Are Access Tiers?
Azure Blob Storage access tiers are a way to balance storage cost against access cost. The pattern is consistent across all tiers:
- Lower storage cost = Higher access cost + longer retrieval time
- Higher storage cost = Lower access cost + instant retrieval
Choose based on how often your data is accessed. Move infrequently accessed data to cheaper tiers to save significantly on storage costs.
Hot Tier
The Hot tier is optimised for data that is accessed frequently. It has the highest storage cost but the lowest access cost and instant retrieval.
- Access frequency: Data accessed regularly or daily
- Retrieval: Immediate
- Minimum retention: None
- Best for: Active website assets, application data being read/written regularly, recently uploaded files
Cool Tier
The Cool tier is optimised for data that is infrequently accessed and stored for at least 30 days. Storage cost is lower than Hot, but access and retrieval costs are higher.
- Access frequency: Accessed less than once a month
- Retrieval: Immediate (same as Hot)
- Minimum retention: 30 days (early deletion fee applies)
- Best for: Short-term backups, older application data, disaster recovery copies used rarely
Cold Tier
The Cold tier (introduced in 2023) sits between Cool and Archive. It offers lower storage costs than Cool but higher access costs, with a 90-day minimum retention period.
- Access frequency: Rarely accessed — a few times per year
- Retrieval: Immediate (milliseconds)
- Minimum retention: 90 days
- Best for: Long-term backups, compliance archives that occasionally need access, older data that must be retrievable quickly
Archive Tier
The Archive tier is the cheapest storage option — designed for data that is rarely (if ever) accessed and can tolerate several hours of retrieval time. Data in Archive is stored offline.
- Access frequency: Almost never — regulatory or compliance archives
- Retrieval: Hours (must be "rehydrated" before access)
- Minimum retention: 180 days
- Best for: Long-term compliance data, legal archives, old backups that must be kept but rarely accessed
Side-by-Side Comparison
| Tier | Storage Cost | Access Cost | Retrieval Time | Min Retention |
|---|---|---|---|---|
| Hot | Highest | Lowest | Immediate | None |
| Cool | Medium | Medium | Immediate | 30 days |
| Cold | Low | High | Immediate | 90 days |
| Archive | Lowest | Highest | Hours | 180 days |
Setting Access Tiers
Tiers can be set at two levels:
- Account level — Default tier for all new blobs (Hot or Cool only)
- Blob level — Override for individual blobs (Hot, Cool, Cold, or Archive)
# Set a blob to Cool tier
az storage blob set-tier \
--account-name mystorageaccount2026 \
--container-name backups \
--name old-backup.bak \
--tier Cool \
--auth-mode login
# Set a blob to Archive tier
az storage blob set-tier \
--account-name mystorageaccount2026 \
--container-name archives \
--name compliance-2020.pdf \
--tier Archive \
--auth-mode login
Rehydrating from Archive
To access a blob in Archive tier, you must first rehydrate it — move it to Hot or Cool tier. There are two rehydration priorities:
| Priority | Time | Cost | Use When |
|---|---|---|---|
| High priority | Under 1 hour (for blobs < 10 GB) | Higher | Urgent retrieval needed |
| Standard priority | Up to 15 hours | Lower | Non-urgent retrieval |
# Rehydrate with standard priority (up to 15 hours)
az storage blob set-tier \
--account-name mystorageaccount2026 \
--container-name archives \
--name compliance-2020.pdf \
--tier Hot \
--rehydrate-priority Standard \
--auth-mode login
Choosing the Right Tier
| Data Example | Access Pattern | Recommended Tier |
|---|---|---|
| Profile pictures on a social app | Accessed every page load | Hot |
| Last month's backups | Rarely accessed, might restore if needed | Cool |
| 6-month-old application data | Very rarely accessed | Cold |
| 7-year compliance archive | Almost never — legal requirement only | Archive |