CF-AZ-ST-06Storage

How to detect old storage snapshots.

Old Storage Snapshots can quietly add recurring Azure cost when resource state, utilization, or lifecycle policy no longer matches real usage. This guide explains why it costs money, how to find it manually, and how Costframe detects it read-only.

CF-AZ-ST-06 • DETECTOR TYPE

Old Storage Snapshots

Impact: High
Resource: backup-snap-2025-q2
+€110.00/mo
Utilization Telemetry
0 IOPS / Low utilization detected
Audit Rationale

Orphaned old storage snapshots found in billing records with zero active workload associations over a rolling 30-day window.

Operational Description

Snapshots provide a point-in-time copy of a managed disk for backup and disaster recovery. Over time, recurring backup scripts often accumulate old snapshots that are redundant and are no longer required for active recovery plans.

Primary Root Cause

Absence of automated snapshot lifecycle retention policies, resulting in backups that accumulate indefinitely in the subscription.

How Costframe Detects & Verifies This

We list all snapshot resources of type Microsoft.Compute/snapshots, sorting them by creation timestamp, and flag those that exceed your organization's configured data retention window (e.g. 90 days).

Evidence:Creation date: 412 days ago • Retention policy threshold: 90 days.

Continuous cloud audits, automated

Run this detector and dozens of other cloud-waste rules across all your Azure subscriptions continuously.