Inactive Blobs in Storage Account

When these blobs remain in the Hot tier, they continue to incur the highest storage cost, even if they have not been read or modified for an extended period. Without lifecycle management in place, these inactive blobs often go unnoticed and accumulate cost. In many cases, the data could be safely transitioned to a lower-cost tier or deleted altogether, depending on retention needs. Additionally, a misconfigured default access tier at the storage account level can cause even new uploads to be stored in the Hot tier unnecessarily. Lifecycle management policies themselves are free, but each tier change is billed as a write operation at the destination tier and early deletion charges may apply, so estimate transaction costs for large numbers of small blobs before automating.

Azure Blob Storage is billed based on a combination of:

• Storage used (per GB/month) - Charges vary by access tier:
• Hot (highest storage cost, lowest access cost)
• Cool (lower storage cost, higher access and operation charges)
• Cold (lower storage cost than Cool, higher access and operation charges)
• Archive (lowest storage cost, highest retrieval and rehydration cost, with delayed access)
• Data access and operations - Read/write operations and metadata access are billed separately and increase in cost for cooler tiers
• Early deletion charges - Cool and Archive tiers have minimum retention durations (30 days for Cool, 90 days for Cold, 180 days for Archive), with penalties for early deletion
• Rehydration - Retrieving data from Archive to an online tier (Hot, Cool, or Cold) incurs a separate per-GB retrieval charge

• Identify storage accounts with large amounts of data in the Hot tier
• Analyze blob-level access patterns using logs or metrics to confirm that data has not been read or written over a defined lookback period
• Determine whether the data is still relevant to any active workload, process, or compliance requirement
• Check whether lifecycle management rules are configured to transition or delete stale data, and whether they are actively being applied
• Review the default access tier setting for each storage account (there is no container-level default; tiers are set per blob or inherited from the account default) to identify misaligned defaults (e.g., Hot for archival use cases)
• Engage with application or data owners to validate whether inactive blobs can be tiered or deleted without impact

For inactive data that must be retained, transition blobs to lower-cost tiers such as Cool, Cold, or Archive using Azure Blob lifecycle policies. If the data is no longer needed, delete it to eliminate costs. Review and enforce lifecycle rules across storage accounts to automate ongoing management. Ensure that default access tier settings are aligned with data usage patterns to prevent accumulation of new blobs in the wrong tier.

• Azure Blob Storage Pricingazure.microsoft.com
• Azure Blob Lifecycle Managementlearn.microsoft.com