Multi-cloud guide
Unattached cloud disks on AWS, Azure, and GCP
Every major cloud bills for provisioned disk even when nothing is attached. Unattached disks are a universal FinOps quick win across AWS, Azure, and Google Cloud.
Same problem, three names
AWS calls them unattached EBS volumes. Azure: unattached managed disks. GCP: unattached Persistent Disks. The pattern is identical—storage left behind after compute moves on.
Multi-cloud cleanup playbook
Inventory by project/subscription/account, age the disks, snapshot if needed, delete with ownership, then verify each cloud’s billing source.
- AWS → Cost Explorer (EBS)
- Azure → Cost Management (Disks)
- GCP → BigQuery billing export (Persistent Disk)
Why tools fail without ownership
Scanners list orphans forever if nobody is assigned. SpendPilot’s Actions board maps each disk finding to team, project, and environment so cleanup actually finishes.
Checklist
- Scan AWS, Azure, and GCP connections you use
- Filter unattached / available disks
- Assign owners and approve deletions
- Clean up in each cloud console
- Verify spend drop per cloud
FAQ
- Are unattached disks billed on GCP and Azure too?
- Yes. Persistent Disks and Azure managed disks bill when provisioned, including when unattached.
- Can one tool cover all three clouds?
- SpendPilot scans waste and verifies savings across AWS, Azure, and GCP in one Actions and Savings workflow.