Where unneeded Azure data accumulates
Four sources dominate. Orphaned managed disks linger after their VM is deleted and keep billing at full provisioned size. Snapshots pile up from backups and migrations that were never cleaned. Blob data sits in hot tier when it has not been read in months. Log Analytics and Azure Monitor retain telemetry far beyond the window anyone investigates.
None of these show intent to keep. They are the residue of change, and they bill every day until someone decides.
The decommissioning sweep
Start with orphaned disks: list managed disks in an unattached state and confirm with owners before deleting, since a disk billed at provisioned size is pure waste once its VM is gone. Next, age out snapshots against a retention rule rather than keeping them forever.
For blob storage, move cold data down the tiers and delete what is past policy. Hot, cool, cold, and archive tiers price storage progressively cheaper in exchange for higher access cost and latency, so data you rarely read belongs in cool, cold, or archive, and data past its retention window belongs deleted.
Make the saving stand: lifecycle and retention
A one time clean up drifts back without policy. Azure Blob Storage lifecycle management rules move blobs between tiers and delete them on age automatically, so cold data tiers itself and expired data removes itself.
For logs, set Log Analytics retention to the window you actually investigate and route anything kept for compliance to cheaper archive. Retention is the single biggest lever on a Log Analytics bill, because you pay to keep data long after its operational value has passed.
A worked example
Indicative figures, verified against the client's billing data, anonymized. A European SaaS company ran a one time sweep and then set lifecycle and retention policy.
| Source | Before | After |
|---|---|---|
| Orphaned managed disks | 7,500 USD | 400 USD |
| Stale snapshots | 4,200 USD | 900 USD |
| Blob in hot tier past policy | 11,000 USD | 4,500 USD |
| Log Analytics over retention | 9,000 USD | 3,800 USD |
| Total monthly | 31,700 USD | 9,600 USD |
Your next step
Run the sweep once, then encode it as lifecycle and retention policy so the saving holds. For the full method read the Azure cost optimization guide, and for neighbouring detail see the Azure storage review playbook and Log Analytics the quiet budget eater. To execute it safely, our Azure cost optimization service turns the clean up into verified savings, and you can request a free trial.
Put a defensible number on your cloud spend.
No provider in the room, no published price list. Tell us your footprint and we will scope the savings against your billing data — we reduce your cloud spend or we reimburse our service fee.
The Cloud Spend Navigator: what changed in cloud pricing, commitments, and FinOps — no vendor spin.