Active storage for frequent or occasional access
Cloud / Knowledge library
Azure Blob Archive Tier
Places blob data in an offline archive tier that must be rehydrated before use
Why learn Azure Blob Archive Tier?
Teams use Azure Blob Archive Tier to adopt archive storage without building the complete underlying platform themselves.
The problem it solves
Retains infrequently accessed data at low storage cost with slower retrieval
Where it came from
Azure Blob Archive Tier is Microsoft Azure's offering for archive storage. Its closest catalog counterparts are Amazon S3 Glacier Storage Classes and Google Cloud Archive Storage; they address the same broad need but are not feature-for-feature identical.
Build your understanding
Work through these exercises in order. Try the task before opening a reference.
- Explain the main responsibility of Azure Blob Archive Tier.
- Choose a workload that fits Azure Blob Archive Tier.
- Identify one operational tradeoff of Azure Blob Archive Tier.
- Compare Azure Blob Archive Tier with Amazon S3 Glacier Storage Classes.
- Compare Azure Blob Archive Tier with Google Cloud Archive Storage.
Documentation and sources
- Microsoft Azure product catalog (azure.microsoft.com)
Connect the ideas
Alternatives
Real World Example
Optimizing Long-Term Compliance Data Retention
Legal and financial firms requiring multi-year retention of closed case files.
The business problem
High monthly storage costs for massive volumes of inactive, legacy case data that is rarely accessed but must be kept for regulatory compliance.
How this topic solves it
Azure Blob Archive Tier provides a cost-effective storage solution for data that is not needed for immediate operations, keeping it in an offline state until explicitly requested.
- Identify inactive blobs that meet the criteria for long-term retention.
- Apply a lifecycle management policy or manual update to move the target blobs to the Archive access tier.
- Initiate a rehydration process when access to the archived data is required for an audit.
- Wait for the rehydration process to complete, which changes the blob tier to Hot or Cool.
- Access the rehydrated blob data as standard storage once the process finishes.
The flow shows data moving from active storage to the offline archive tier and the necessary rehydration path for retrieval.
Offline storage for long-term retention
Process to move data back to online state
- Hot/Cool Tier → Move to Archive → Archive Tier
- Archive Tier → Request Access → Rehydration
- Rehydration → Restore to Online → Hot/Cool Tier
Expected business outcome
Significant reduction in monthly storage expenditures while maintaining the ability to retrieve historical records for compliance audits.
Limitations and checks
The primary trade-off is latency; archived data is offline and cannot be read immediately, requiring a rehydration process that takes time to complete before the data becomes available.