# 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

[Cloud Efficiency Hub](https://www.pointfive.co/efficiency-hub) 

# High Transaction Cost Due to Misaligned Tier in Azure Blob Storage

## Explanation

Azure Blob Storage tiers are designed to optimize cost based on access frequency. However, when frequently accessed data is stored in the Cool or Archive 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.

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.

## Relevant Billing Model

- 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

- Archive tier : lowest storage cost, highest retrieval cost, with delayed access

- Storage tier is set per object or container and determines both baseline storage and access costs

## Detection

- Identify storage accounts with Blob data stored in the Cool or Archive 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

## Remediation

- Move frequently accessed data to the Hot tier, either manually or via lifecycle management policies

- 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

## Relevant Documentation

- [Azure Blob Storage Access Tiers](https://learn.microsoft.com/en-us/azure/storage/blobs/access-tiers-overview)

- [Blob Storage Pricing](https://azure.microsoft.com/en-us/pricing/details/storage/blobs/)

[Submit Feedback](https://hub.pointfive.co/inefficiencies/high-transaction-cost-due-to-misaligned-tier-in-azure-blob-storage)

## At a glance

Reference

CER-0172

Cloud provider

Azure

Service

Azure Blob Storage

Category

[Storage](https://www.pointfive.co/efficiency-hub/service-category/storage)

Inefficiency type

Inefficient Configuration

## Contributed by

- Balazs Engedi 

### Balazs Engedi

FinOps Specialist @ KPN

[LinkedIn](https://www.linkedin.com/in/engedib/)

---
Source: the public page above. Product screenshots and illustrative interfaces are examples, not live customer data.