Unused Volumes#
The Unused volumes policy deletes disks that are no longer attached to any machine. These orphans remain after a VM is deleted and keep generating cost.
What it deletes#
Provider |
Volumes |
|---|---|
Azure |
Managed disks in |
AWS |
EBS volumes in |
GCP |
Persistent disks with no users |
Attached volumes are never touched. Two options narrow the candidates further:
Option |
Default |
Effect |
|---|---|---|
Minimum age (days) |
30 |
Only disks created more than N days ago |
No activity period (days) |
14 |
Only disks with no read/write activity for N days |
Create it#
Open Automation → Policy Catalog and select Use on Unused volumes.
Choose the groups, version and a schedule (see Automation Policies).
Adjust the options and consider Require approval before executing actions.
Select Create.
Warning
Deletion is permanent. Without a snapshot or backup, deleted volumes cannot be recovered.
Recommended approach#
Dry run first — use Trigger now with Dry Run on and review the log.
Start small — target non-production groups, then extend.
Require approval — review each batch of candidates before deletion.
Run weekly — gives teams time to reclaim accidental orphans.
Snapshot production — use Azure Backup, AWS Data Lifecycle Manager or GCP scheduled snapshots before enabling it on production.
Permissions#
The connection must be ReadWrite and allowed to delete disks:
Provider |
Permission |
|---|---|
Azure |
|
AWS |
|
GCP |
|
A Failed result usually means this permission is missing or the disk is locked. See Troubleshooting.