7 documented Azure Blob Storage cost inefficiencies, each with how to detect it and how to fix it.
Azure Blob StorageCER-0335
Azure Blob Storage and ADLS Gen2 bill per transaction - every list, read, write, rename, and metadata operation is a separately metered API call. When organizations migrate workloads from on-premises Hadoop/HDFS environments or local...
Azure Blob StorageCER-0268
Audit logs are often retained longer than necessary, especially in environments where the logging destination is not carefully selected. Projects that initially route SQL Audit Logs or other high-volume sources to LAW or Azure Storage may...
Azure Blob StorageCER-0172
Azure Blob Storage tiers are designed to optimize cost based on access frequency. However, when frequently accessed data is stored in the Cool or Cold tiers - either due to misconfiguration, default settings, or cost-only optimization -...
Azure Blob StorageCER-0052
A blob container intended for long-term or infrequently accessed data continues to store objects in higher-cost tiers like Hot or Cool, instead of using the Archive tier. This often happens when no lifecycle management rules target the...
Azure Blob StorageCER-0058
Storage accounts can accumulate blob data that is no longer actively accessed - such as legacy logs, expired backups, outdated exports, or orphaned files. When these blobs remain in the Hot tier, they continue to incur the highest storage...
Azure Blob StorageCER-0431
Blob versioning and blob soft delete are part of Microsoft's recommended data protection configuration, so they are often switched on for every storage account. With versioning enabled, every write to a blob (Put Blob, Put Block List, Copy...
Azure Blob StorageCER-0432
Large block blob and Azure Data Lake Storage Gen2 estates such as data lakes, media libraries, backup targets and archives often hold hundreds of TiB that change slowly from month to month, yet stay on pay-as-you-go capacity pricing. Azure...
