# High transaction cost due to misaligned tier in Azure Blob Storage Canonical: https://www.pointfive.co/efficiency-hub/inefficiencies/high-transaction-cost-due-to-misaligned-tier-in-azure-blob-storage Azure Blob Storage tiers are designed to optimize cost based on access frequency. By: Balazs Engedi Updated: 2026-09-28 [Cloud Efficiency Hub](https://www.pointfive.co/efficiency-hub) # High Transaction Cost Due to Misaligned Tier in Azure Blob Storage The short version Azure Blob Storage tiers are designed to optimize cost based on access frequency. [Balazs Engedi](https://www.linkedin.com/in/engedib/) FinOps Specialist @ KPN Azure service [Azure Blob Storage](https://www.pointfive.co/efficiency-hub/cloud-services/azure-blob-storage) Category [Storage](https://www.pointfive.co/efficiency-hub/service-category/storage) Reference CER-0172 Type Inefficient Configuration ## Explanation Why the waste happens and who it affects. However, when frequently accessed data is stored in the Cool or Cold tiers - either due to misconfiguration, default settings, or cost-only optimization - transaction costs can spike. These tiers impose significantly higher charges for read/write operations and metadata access compared to the Hot tier. The Archive tier is different: it is an offline tier, so archived blobs cannot be read or modified at all until they are rehydrated to an online tier, which can take up to 15 hours and is billed as data retrieval from Archive. This misalignment is common in analytics, backup, and log-processing scenarios where large volumes of object-level operations occur regularly. While the per-GB storage rate is lower, the overall cost becomes higher due to frequent access. This inefficiency is silent but accumulates rapidly in active workloads. ## Billing model The pricing dimensions that drive this cost. - Charges include per-GB storage cost and per-operation transaction cost - Hot tier : higher storage cost, lower transaction cost - Cool tier : lower storage cost, higher transaction cost - Cold tier : lower storage cost than Cool, higher access cost than Cool, with a 90-day minimum storage duration - Archive tier : lowest storage cost, highest retrieval cost, offline - blobs must be rehydrated before they can be read - Access tier is set per blob, or inferred from the storage account default access tier (Hot, Cool, or Cold), and determines both baseline storage and access costs ## How to detect 4 checks to find it in your estate. - Identify storage accounts with Blob data stored in the Cool or Cold tier - Analyze access patterns to determine if objects in these tiers are frequently read, written, or queried - Review transaction cost line items relative to storage cost to detect skewed ratios - Determine whether lifecycle management policies are in place and correctly applied ## How to fix 5 ways to remove the waste. - Move frequently accessed data to the Hot tier, either manually or via lifecycle management policies - Account for the cost of the move: changing a blob to a warmer tier is billed as a read from the source tier (read operations plus per-GB data retrieval), and blobs moved out of Cool or Cold before 30 or 90 days incur a prorated early deletion charge - Evaluate default tiering settings on upload processes to prevent misplacement of active data - Incorporate access pattern analysis into storage tier selection decisions - Periodically review storage access metrics to ensure ongoing alignment between access frequency and tier ## Documentation Vendor references for pricing and configuration. - [Azure Blob Storage Access Tiers learn.microsoft.com](https://learn.microsoft.com/en-us/azure/storage/blobs/access-tiers-overview) - [Blob Storage Pricing azure.microsoft.com](https://azure.microsoft.com/en-us/pricing/details/storage/blobs/) ## Related inefficiencies [Browse the library](https://www.pointfive.co/efficiency-hub) - Azure Blob Storage CER-0052 ### [Archival Blob Container Storing Objects in Non-Archival Tiers](https://www.pointfive.co/efficiency-hub/inefficiencies/archival-blob-container-storing-objects-in-non-archival-tiers) 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... Storage - Azure Blob Storage CER-0335 ### [Excessive Transaction Cost Overhead on Blob Storage from I/O-Intensive Workloads](https://www.pointfive.co/efficiency-hub/inefficiencies/excessive-transaction-costs-from-filesystem-style-access-patterns-on-blob-storage) 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... Storage - Azure Blob Storage CER-0268 ### [Excessive Retention of Audit Logs](https://www.pointfive.co/efficiency-hub/inefficiencies/excessive-retention-of-audit-logs) 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... Storage --- Source: the public page above. Product screenshots and illustrative interfaces are examples, not live customer data.