Five of the six managed disks shown have no Owner, meaning they are currently unattached; review their contents and dependencies, then permanently delete any that are no longer required because previously used unattached disks continue to incur storage charges.
What each disk represents
The Owner column contains the VM resource when a managed disk is attached. A blank/dash Owner corresponds to a null ManagedBy property, which identifies an unattached disk.^1^
| Disk shown |
Type and size |
Interpretation |
Application-0_OsDisk_1_... |
Standard HDD LRS, 127 GiB |
Unattached OS disk; probably retained from a VM named Application-0. |
WVD-0_OsDisk_1_... |
Standard HDD LRS, 127 GiB |
Unattached OS disk; probably retained from WVD-0. |
WVDApp-0-0_OsDisk_1_... |
Standard SSD LRS, 128 GiB |
Attached disk owned by the VM WVDApp-0-0. Do not delete it while that VM is required. |
WVDApp-0-1-0_OsDisk_1_... |
Standard SSD LRS, 128 GiB |
Unattached OS disk. |
WVDApp-0_OsDisk_1_... |
Standard HDD LRS, 256 GiB |
Unattached OS disk. |
WVDApp-1-0_OsDisk_1_... |
Standard HDD LRS, 128 GiB |
Unattached OS disk. |
OsDisk in a name indicates that the resource was created as a VM operating-system disk. It does not mean that it is still connected to a VM.
These disks commonly remain because deleting a VM does not necessarily delete its OS and data disks. Azure retains them to prevent accidental data loss, and retained disks continue to incur applicable charges.^2^
Are they being charged?
- The attached
WVDApp-0-0 disk is billable as part of the VM’s storage.
- The five unattached disks generally continue to be billable even though no VM uses them.
- Managed-disk billing depends on factors including disk type and provisioned size. Provisioned sizes are mapped to Azure disk-size tiers and billed hourly.^3^
- A newly created empty managed disk is an exception: it does not incur disk-storage charges until storage is allocated by attaching it or uploading a VHD. That exception normally would not apply to a disk previously used as a VM OS disk.^4^
To confirm the actual amount:
- Open Azure portal → Cost Management + Billing → Cost Management → Cost analysis.
- Select the subscription and appropriate date range.
- Group or filter by Resource.
- Search for each complete disk name.
- Check both the current period and the last completed billing period.
Safely review and remove the five unattached disks
Deletion is permanent, so first confirm that each disk contains no data, old VM installation, or recovery copy that must be retained.^5^
For each disk with - under Owner:
- In Azure portal → Disks, select the disk.
- On Overview, confirm Disk state = Unattached.
- Record its:
- full name;
- resource group;
- creation time;
- disk size and storage type;
- source resource or source snapshot, if displayed.
- Check whether the corresponding VM still exists under Virtual machines, including stopped or deallocated VMs.
- Check Snapshots and Recovery Services vault → Backup items → Azure Virtual Machine if the disk may be needed for backup or recovery. Retained VM backups are separate resources and may also continue to incur storage charges.^2^
- If the disk is definitely unnecessary, return to its page and select Delete, then confirm.
Do not delete WVDApp-0-0_OsDisk_1_...: its Owner shows that it is attached to WVDApp-0-0. Also avoid deleting all five unattached disks in bulk solely from their names—the three resource groups suggest they may come from different VM deployments.
For future VMs, configure their OS and data disks with Delete with VM when creating the VM. Otherwise, a disk configured to Detach remains after VM deletion and can continue generating charges.^2^
References
- Find and delete unattached Azure managed and unmanaged disks by using Azure PowerShell
- Delete a VM and attached resources
- Azure managed disk types
- Understand Azure Disk Storage billing
- Find and delete unattached Azure managed and unmanaged disks - Azure portal