You are viewing a free preview of this lesson.
Subscribe to unlock all 10 lessons in this course and every other course on LearningBro.
Azure Blob Storage offers multiple access tiers that let you optimise storage costs based on how frequently you access your data. By placing data in the right tier, you can significantly reduce your storage bill without sacrificing availability when you need it. This lesson covers each tier, their cost trade-offs, and how to move data between them.
Not all data is accessed equally. An e-commerce site might frequently read product images but rarely touch old order archives. A compliance system might store audit logs that are read once a year. Azure access tiers let you match storage costs to access patterns.
The principle is simple:
| Tier | Storage Cost | Access Cost | Min Retention | Availability SLA |
|---|---|---|---|---|
| Hot | Highest | Lowest | None | 99.9% (99.99% RA-GRS) |
| Cool | Lower | Higher | 30 days | 99% (99.9% RA-GRS) |
| Cold | Even lower | Even higher | 90 days | 99% (99.9% RA-GRS) |
| Archive | Lowest | Highest | 180 days | Offline (not directly accessible) |
The Hot tier is optimised for data that is accessed or modified frequently.
Use cases:
Characteristics:
The Cool tier is for data that is infrequently accessed and stored for at least 30 days.
Use cases:
Characteristics:
The Cold tier is designed for data that is rarely accessed and stored for at least 90 days.
Use cases:
Characteristics:
The Archive tier offers the lowest storage cost but the highest access cost and latency.
Use cases:
Characteristics:
The default access tier is set at the storage account level and applies to any blob uploaded without an explicit tier:
# Set the default account tier to Cool
az storage account update \
--name mystorageaccount \
--resource-group rg-storage-demo \
--access-tier Cool
Subscribe to continue reading
Get full access to this lesson and all 10 lessons in this course.