What is the early deletion charge for Azure Cool and Archive tiers?

Cool tier has a minimum storage duration of 30 days, and Archive tier requires 180 days. If you delete or move a blob before the minimum duration, Azure charges the equivalent storage cost for the remaining days. The estimator flags this so you can factor early deletion risk into your cost model.

How does redundancy choice affect cost?

LRS (locally redundant) is the cheapest option, storing three copies in a single datacenter. GRS and GZRS replicate data to a secondary region for disaster recovery, roughly doubling storage costs. RA-GRS/RA-GZRS add read access to the secondary copy at a small premium. The estimator shows exact pricing for each option.

Does the tool account for Azure Blob operation costs?

Yes. Each read, write, and list operation has a per-10,000-operation charge that varies by tier. The estimator includes these operation costs alongside storage and retrieval fees for a complete monthly projection.

Azure Storage Cost Estimator

StorageAzure

Estimate monthly Azure Blob Storage costs across tiers and redundancy options.

Last verified: May 2026

Azure Blob Storage Configuration

Access Tier

Redundancy

Storage Size (GB)

Write Operations (per 10K)

Read Operations (per 10K)

Data Retrieval (GB)

Data Transfer Out (GB)

Raw Output

Output will appear here...

About This Tool

The Azure Storage Cost Estimator projects your monthly Azure Blob Storage bill across access tiers and redundancy configurations. It covers Hot, Cool, Cold, and Archive tiers with LRS, ZRS, GRS, RA-GRS, GZRS, and RA-GZRS redundancy options. Enter your storage volume, read/write operation counts, and data retrieval expectations to get a detailed cost breakdown including early deletion penalties for Cool and Archive tiers. This tool is essential for Azure architects planning data lake, backup, or media storage solutions who need to balance cost against access frequency and durability requirements.

Real-World Scenario

Your engineering team is storing 100 TB of build logs on Azure Hot tier with GRS, costing $4,800/month. The logs are written once and read maybe twice per quarter for incident debugging. The estimator shows that moving to Cool tier with LRS drops storage to $1,000/month, plus ~$50/month in retrieval fees during the rare reads. Net savings: $3,750/month. You implement a lifecycle policy to auto-tier logs older than 30 days and the savings start accumulating immediately.

When to Use This Tool

•Comparing monthly costs between Hot and Cool tiers for a web application's user-uploaded media library.
•Estimating the total cost of archiving compliance data in the Archive tier including retrieval fees for occasional audits.
•Evaluating the cost impact of upgrading from LRS to GRS redundancy for mission-critical backup data.
•Modeling Azure Blob Storage costs for a data lake that mixes frequently accessed analytics data with cold historical datasets.

Pro Tips

TIP

Cool tier's 30-day minimum and Archive's 180-day minimum are calendar days, not access days. Uploading a blob to Archive on day 1 then deleting on day 90 still bills you for the remaining 90 days at full storage cost. Lifecycle policies that move data to Archive too aggressively can backfire badly.

TIP

GRS replication doubles your storage cost AND charges geo-replication egress when data first crosses regions. For backup workloads where the secondary copy is rarely read, GRS is fine. For active workloads where you want read-from-secondary, RA-GRS or RA-GZRS is the right choice — but expect the cost to be 2.2-2.5x LRS.

TIP

Per-operation costs vary by tier in unexpected ways: Hot tier reads cost $0.0044/10K ops, but Archive tier reads cost $5/10K ops AND require a rehydration period. Even occasional script-driven LIST operations against an Archive container can run up surprising bills.

How It Works Under the Hood

The estimator computes monthly Azure Blob Storage cost across four dimensions: per-GB storage cost (varies by tier × redundancy), per-operation cost (Class A: writes, Class B: reads, with different per-tier rates), retrieval cost for Cool/Cold/Archive tiers, and early-deletion penalty if data is moved out before the minimum duration. It surfaces the dominant cost driver in the breakdown so you know where to optimize.

Frequently Asked Questions

What is the early deletion charge for Azure Cool and Archive tiers?: Cool tier has a minimum storage duration of 30 days, and Archive tier requires 180 days. If you delete or move a blob before the minimum duration, Azure charges the equivalent storage cost for the remaining days. The estimator flags this so you can factor early deletion risk into your cost model.
How does redundancy choice affect cost?: LRS (locally redundant) is the cheapest option, storing three copies in a single datacenter. GRS and GZRS replicate data to a secondary region for disaster recovery, roughly doubling storage costs. RA-GRS/RA-GZRS add read access to the secondary copy at a small premium. The estimator shows exact pricing for each option.
Does the tool account for Azure Blob operation costs?: Yes. Each read, write, and list operation has a per-10,000-operation charge that varies by tier. The estimator includes these operation costs alongside storage and retrieval fees for a complete monthly projection.

Related Learning Guides

Multi-Cloud Storage Cheat Sheet8 min read

Featured In

Cloud Storage Tiering: When to Use Standard, Infrequent, Archive, and Deep Archive

Was this tool helpful?

Disclaimer: This tool runs entirely in your browser. No data is sent to our servers. Always verify outputs before using them in production. AWS, Azure, and GCP are trademarks of their respective owners.