Approve attached-resource delete policies before retiring an Azure VM

Source facts

For managed disks and NICs, Azure’s Delete option permanently removes the associated resource when the VM is deleted; Detach leaves that resource available for reuse. Microsoft documents configurable behavior for managed disks, NICs, and public IPs. The public IP’s Delete behavior is linked to deletion of its associated NIC. Shared disks cannot use Delete as their deleteOption. The documentation also warns against force deletion when virtual hard disks are intended for reuse. Microsoft Learn.

Applicability

Identify the exact VM and every attached resource before approving retirement. Distinguish resources that must be retained for investigation, replacement, or recovery from those approved for removal. Inspect the actual options rather than inferring them from the creation tool or a different VM’s defaults.

DSE recommendation

Approve a resource-by-resource survival list and compare it with the VM’s actual delete options before deletion. Have the data and network owners review their respective entries, including any shared disk and whether the NIC itself will be retained. Resolve a disagreement between the intended outcome and configured behavior before proceeding. Keep replacement planning separate from expedited cleanup, and do not select force deletion merely to shorten a task that depends on disk reuse.

Verification

Use a disposable representative VM to validate the approved policy pattern first. After an authorized retirement, reconcile every previously attached resource against its intended retained or removed state. Record the identifiers of retained disks and interfaces and assign their next owner or disposition. Investigate an unexpected survivor or missing resource explicitly; deletion of the VM object alone is not the completion criterion for the retirement record.

Official references

Microsoft Learn: Delete a VM and attached resources. Source reviewed September 9, 2026.