
Introduction
Azure Blob soft delete saves you when someone deletes the wrong file. It also keeps that file on your bill. Deleted data stays recoverable, and billable, until the retention window closes.
This article covers object (blob) soft delete only. It does not cover container soft delete, which recovers a deleted container but does not protect a single blob removed from a live container. It also excludes managed disk protection.
Below you'll find East US pricing, a cost formula, the factors that inflate retained capacity, and ways to trim spend without giving up recovery.
Key Takeaways
- Soft delete has no flat fee; cost follows retained GB, tier, redundancy, and retention days.
- Retained data bills at the same rate as active data until it expires.
- Versioning, snapshots, and high churn multiply the retained footprint.
- Pick the shortest retention that still covers discovery time and compliance.
How Much Does Azure Blob Soft Delete Cost? (Pricing Overview)
Microsoft says enabling Blob Storage features has no cost, and soft delete is not a separate billing meter. You pay for the bytes it keeps, plus any operations that follow.
Soft-deleted data bills at the same rate as active data and stays in its original tier until retention expires. Three misunderstandings drive most surprises:
- Assuming deleted data stops billing immediately
- Setting retention longer than operations need
- Forgetting that versioning or replication enlarges the retained footprint
Typical Cost Range
Microsoft publishes no fixed soft-delete total, so ranges are more useful than a single number. These East US rates are USD per GB-month for the Data Stored meter under Microsoft retail pricing (rates vary by agreement and date):
| Tier | LRS | ZRS | GRS | RA-GRS |
|---|---|---|---|---|
| Hot | $0.0208 | $0.026 | $0.0458 | $0.0589 |
| Cool | $0.0152 | $0.019 | $0.0334 | $0.0425 |
| Cold | $0.0036 | $0.004 | $0.0081 | $0.0101 |
| Archive | $0.00099 | n/a | $0.00299 | $0.00299 |
Hot tier drops slightly above 50 TB (Hot LRS falls to $0.019968) and again above 500 TB.
Illustrative math at Hot LRS, capacity only:
- Baseline: no meaningful deleted backlog, so the bill is active data alone.
- Moderate: 5 TB (5,000 GB) of deleted data retained on average costs about $104/month.
- High: 50 TB retained in Hot RA-GRS costs about $2,945/month.

These figures exclude transactions, retrieval, cross-region transfer, early deletion charges, monitoring, and taxes.
Cost impact scales with churn and retention settings.
Low-impact configuration. Few deletions, a short window, and little version buildup keep retained GB small. Temporary data, or apps where mistakes surface within days, fit here. Don't shorten retention if compliance demands longer preservation.
Moderate-impact configuration. Routine deletes and overwrites create a steady pool of billable deleted data, even when active capacity looks flat. Estimate it by multiplying average retained GB by your tier's rate. A workload deleting 200 GB daily with 14-day retention holds roughly 2,800 GB at steady state, about $58/month in Hot LRS.
High-impact configuration. High churn, long retention, many versions, snapshots, and GRS or RA-GRS can dwarf the active dataset's cost. Model this carefully for:
- Data pipelines and analytics staging
- AI workloads
- Backups
- Apps that frequently replace large objects
Key Factors That Affect Azure Blob Soft Delete Cost
Cost comes from configuration, deletion behavior, protection settings, and billing meters combined, not from a soft-delete fee.
Retention Period
Retention runs from 1 to 365 days, and Microsoft recommends at least 7. Every extra day keeps deleted bytes billable longer. Compare the window to how long it really takes your team to notice a mistake.
Storage Volume and Deletion Churn
Active capacity matters less than how much you delete or overwrite per period. Steady-state retained data is roughly daily deleted volume times retention days.
Access Tier and Lifecycle Behavior
Soft-deleted blobs stay in their tier. Minimum storage durations still apply:
- Cool: 30 days
- Cold: 90 days
- Archive: 180 days
Early deletion, overwrite, or tier moves can trigger charges. Microsoft's example: deleting an Archive blob after 45 days can incur a charge for the remaining 135 days. Cooler tiers also add retrieval fees.
Redundancy and Region
Redundancy choice multiplies what you pay for retained soft-deleted data:
- LRS: copies in one data center
- ZRS: spans three or more zones
- GRS: async replication to a secondary region
- RA-GRS: GRS plus read access in the secondary region
In the table above, Hot RA-GRS costs about 2.8 times Hot LRS, and retained data pays that premium too. Choose redundancy for resilience first, then see what it does to retained bytes.

Versioning, Snapshots, and Overwrites
With versioning on, overwriting creates a previous version rather than a soft-deleted snapshot. That version persists until explicitly deleted. Deleting the current blob turns it into a previous version that keeps billing.
- Current blob: your live data
- Previous version: retained until deleted
- Snapshot: read-only point-in-time copy
- Soft-deleted version: removed item awaiting expiry
Unchanged blocks shared across a blob, snapshots, and versions are charged once. Changed blocks add capacity.
Transactions, Retrieval, and Data Transfer
Delete Blob can be free, but Undelete Blob and Copy Blob are billed as writes, and List Blobs is billable. Cool, Cold, and Archive add per-GB retrieval, and copying to another region adds transfer. Check the current Azure pricing page before forecasting recovery-heavy workloads.

Cost Breakdown of Azure Blob Soft Delete
Blob Storage is usage-based and recurring. There is no purchase or installation price, but soft delete shows up on several line items.
| Component | Type | What drives it |
|---|---|---|
| Active blob capacity | Recurring | GB stored, tier, region, redundancy |
| Soft-deleted capacity | Recurring during retention | Average retained GB × tier rate |
| Versions and snapshots | Recurring until removed | Changed blocks, lifecycle rules |
| Transactions and retrieval | Usage-based | Undelete, copy, list, retrieval, transfer |
| Redundancy | Recurring | Multiplies active and retained data |
| Monitoring and governance | Recurring or usage-based | Log ingestion, inventory scans |
Soft-Deleted Blob Capacity
You pay average soft-deleted GB × the applicable USD/GB-month rate for your tier. That charge runs for the entire time data remains in the retention window.
Versions and Snapshots
Lifecycle policies can delete previous versions by creation time. With soft delete on, those deletions enter the soft-deleted state and keep billing until retention ends. Lifecycle policies don't affect items already soft-deleted.
Monitoring and Governance
Azure Monitor's BlobCapacity metric splits only by blob type and tier, not by deleted or version state. For object-level detail, use Blob Inventory with includeDeleted, includeBlobVersions, and includeSnapshots enabled. Inventory is billed per million objects scanned, and Log Analytics ingestion is billed per GB.
Low-Cost vs High-Cost Retention: How to Estimate the Right Budget
The cheapest setting isn't automatically right. Match retention to recovery needs, compliance, and workload behavior.
Low-Cost vs High-Cost Retention
| Factor | Shorter, leaner | Longer, heavier |
|---|---|---|
| Recovery window | Days | Weeks to a year |
| Retained capacity | Small | Large |
| Versions | Limited, lifecycle-managed | Many |
| Redundancy | LRS or ZRS | GRS or RA-GRS |
| Best for | Disposable, closely monitored data | Regulated or high-impact data |
Spend more when deletions can go unnoticed for weeks, regulations apply, or business impact is high. Go shorter for data you can regenerate.
How to Estimate the Right Budget
- Record active capacity for the storage account.
- Measure daily or monthly deleted and overwritten volume.
- Multiply deleted volume by retention days for average retained GB.
- Factor in tier, redundancy, and region rates.
- Include versioning and snapshot settings that extend retained data.
- Estimate transactions, retrieval, and transfer charges.
Soft-delete storage cost = average retained deleted GB × monthly storage rate. Then add versions, transactions, retrieval, cross-region transfer, early-deletion, and inventory or diagnostic charges.

What Most People Miss
Common blind spots:
- Checking only active capacity
- Ignoring previous versions
- Assuming a retention change retroactively shortens existing deleted items (Microsoft docs don't say it does; verify before relying on it)
- Enabling versioning with no lifecycle rule
Good habits:
- Track retained capacity and deletion trends
- Alert on unusual delete activity
- Review Cost Management by storage account and tag
- Test recovery
- Revisit retention against real discovery times
If you also run Azure block storage, Lucidity offers real-time visibility and autonomous optimization for cloud block storage, with cost reductions of up to 70%. It doesn't replace Blob soft delete, versioning, or lifecycle policies.
Conclusion
Soft delete protects against accidental loss, but deleted and overwritten content keeps billing through the retention window. Model deleted capacity, versions, redundancy, tiers, and usage charges against current Azure US pricing. Then choose the shortest retention and simplest protection design that still meets recovery and compliance needs.
Frequently Asked Questions
What does BLOB stand for?
BLOB stands for Binary Large Object. Azure Blob Storage is Microsoft's object storage for unstructured data such as files, media, logs, and backups.
What are LRS and ZRS in Azure?
LRS copies data within one data center in the primary region. ZRS copies it synchronously across three or more availability zones. Redundancy affects resilience and the price of active and retained data.
How does Azure Blob soft delete affect storage costs?
Deleted or overwritten data keeps consuming billable storage until retention expires. The impact depends on tier, redundancy, region, and retained volume.
Does Azure charge for soft-deleted blobs during retention?
Yes, at the same rate as active data in that tier. Delete Blob operations can be free, but Undelete and Copy are write transactions, and retrieval or transfer fees may apply.
How do versioning and soft delete change the bill?
Versioning keeps previous versions until they're deleted, while soft delete holds deleted items through retention. Together they can raise retained capacity unless lifecycle rules clean up.
How can I reduce Azure Blob soft-delete costs without losing recovery protection?
Right-size retention, add lifecycle rules for old versions, pick suitable tiers, and monitor deletions with cost alerts. Confirm recovery requirements before shortening anything.