Explanation
Why the waste happens and who it affects.
This often happens when no lifecycle management rules target the container's data. The account default access tier can only be Hot, Cool, or Cold, so data reaches Archive only when individual blobs are tiered or a lifecycle policy moves them. Over time, storing archival data in non-archival tiers results in avoidable cost without any performance benefit, especially for compliance data, backups, or historical logs that rarely need to be accessed.
Billing model
The pricing dimensions that drive this cost.
Blob storage is billed based on the total volume of data stored per tier (Hot, Cool, Archive), with higher per-GB costs for tiers optimized for frequent access. The Hot tier has the highest storage cost but lowest access latency and transaction cost. Archive tier is the least expensive for storage but comes with higher data retrieval costs and latency. The Cool and Cold tiers sit in between, with minimum retention periods of 30 and 90 days respectively. Costs accrue based on the selected tier, regardless of whether the data is actively used.
How to detect
5 checks to find it in your estate.
- Identify blob containers with large volumes of data stored in the Hot or Cool tier
- Evaluate access patterns to confirm whether the data is rarely or never read
- Review whether the container's data retention requirements align with archival use cases
- Check for the absence of lifecycle management rules that move the container's blobs to cooler tiers (the account default tier cannot be set to Archive)
- Confirm with data owners that the objects do not require immediate or frequent retrieval
How to fix
How to remove the waste.
Transition eligible objects to the Archive tier to reduce long-term storage costs. Implement Azure Blob Lifecycle Management policies to automatically move data to lower-cost tiers based on age or last access time. When migrating existing objects, confirm that the retrieval latency and cost profile of the Archive tier aligns with business needs.
Archive has a 180-day minimum retention period (deleting or re-tiering a blob earlier incurs a prorated early deletion charge), each move to a cooler tier is billed as a write operation per blob, rehydration can take up to 15 hours, and Archive is supported only on LRS, GRS, and RA-GRS accounts. For data that must remain online, the Cold tier (90-day minimum) may be a better fit.
Documentation
Vendor references for pricing and configuration.