Managed Disk Attached to a Stopped VM

Retaining these disks without validation leads to unnecessary monthly storage costs. Reviewing and cleaning up inactive disks helps optimize spend and maintain storage hygiene.

Managed Disks are billed per provisioned GB per month, regardless of whether the associated virtual machine is running. Disks remain billable whether the VM is Stopped (allocated) or Stopped (deallocated), resulting in ongoing storage charges for unused capacity. A VM that is Stopped but still allocated, for example after a shutdown from inside the guest OS, also continues to incur compute charges; only a deallocated VM stops compute billing.

• Identify Managed Disks attached to virtual machines that have remained in a stopped state over a representative time window
• Analyze disk activity metrics to detect absence of read/write operations during the lookback period
• Review VM metadata, ownership tags, and decommissioning records to assess whether the disk is still required
• Check compliance and backup retention requirements before initiating deletion activities
• Validate findings with infrastructure owners or application teams to avoid accidental loss of necessary data

Deallocate or delete VMs that are still in the Stopped (allocated) state, and delete Managed Disks confirmed to be redundant or obsolete to eliminate unnecessary storage charges. Where long-term retention is required, create a snapshot of the disk or export its contents to a lower-cost storage option before deletion. Incorporate disk ownership tracking and regular audits into operational practices to minimize future accumulation of unused resources.

• Azure Managed Disks Overviewlearn.microsoft.com
• Azure Managed Disks Pricingazure.microsoft.com
• States and billing status - Azure Virtual Machineslearn.microsoft.com