Skip to main content
Managed disk snapshots are billed every month for as long as you keep them. Snapshots taken before a change or a migration are rarely needed after a few weeks, but nothing removes them. nOps finds snapshots that have been billed for at least three months and estimates the saving from deleting them.

Why it matters

Old snapshots pile up quietly and are often the largest part of disk storage cost in accounts that have run for years.

How nOps finds it

nOps reads your pay-as-you-go managed disk snapshot billing. A snapshot is flagged when it was billed on at least 85 of the last 90 complete days, and nOps has at least 85 days of snapshot billing for your account. Snapshots created by Azure Backup are left out, because Azure Backup deletes them itself. The saving is what the snapshot cost over the last 7 days, scaled to a month, and must be at least $5 a month.

Before you start

Confirmation from the snapshot owner that it is not needed for recovery, audit or legal hold.

How to implement

  1. In the Azure portal, open Snapshots and sort by Time created.
  2. Check the tags and owner of each old snapshot, and whether a policy requires you to keep it.
  3. Delete snapshots that are no longer needed, or run az snapshot delete --resource-group MY_RG --name MY_SNAPSHOT.
  4. If snapshots are created by a script or pipeline, add a cleanup step so they do not pile up again.

Risks and considerations

  • Deleting a snapshot is permanent. If you might need it, keep it or copy it to cheaper storage first.
  • Some snapshots are kept for compliance or legal reasons, so check before deleting.

FAQs

No. Snapshots created by Azure Backup are managed by its backup policy and are not flagged.