pranusha.
Back to All Articles
Decommissioning
6 min read
•October 2026

Azure VM Decommission Checklist: Safe Production Shutdowns

An operational checklist for decommissioning Azure Virtual Machines, Managed Disks, NICs, Public IPs, and NSGs with zero surprises.

Pranusha Palaparthi, Cloud Ops Engineer
Pranusha PalaparthiCloud Operations Engineer • Hyderabad, India
Target Keyword: azure vm decommission

Retiring an Azure Virtual Machine requires a methodical teardown across compute, networking, storage, and identity layers. Leaving behind unattached Premium SSD managed disks or static Public IPs drives unnecessary cloud expenditure.

11. Stakeholder Notification & CAB Approval

Ensure the change request is approved in ServiceNow with documented RTO and RPO objectives.

Notify application stakeholders 14 days and 48 hours prior to shutting down the VM.

22. Azure Backup & Managed Disk Snapshots

Trigger an on-demand Azure Backup via the Recovery Services Vault.

Create standalone snapshots of the OS disk and all attached data disks. Tag snapshots with 'Retention=Permanent-Archival' and the Change Request number.

Command ExecutionProduction Safe
# Azure CLI: Snapshot OS Disk
az snapshot create \
  --resource-group rg-production-workloads \
  --name snap-vm-prod-app01-os-decom \
  --source "/subscriptions/{sub-id}/resourceGroups/rg-production-workloads/providers/Microsoft.Compute/disks/vm-prod-app01-os"

33. Disassociate and Stop (Quarantine)

Deregister the VM from Azure Application Gateway backend pools or Load Balancer backend sets.

Deallocate the VM to stop compute charges: az vm deallocate --resource-group rg --name vm-name.

Maintain the deallocated VM for the agreed quarantine window (e.g. 10 business days).

44. Resource Group Teardown Checklist

Once quarantine completes with zero escalations, delete the VM and systematically evaluate remaining assets.

Operational Verification Checklist
  • Confirm VM deletion in Azure Portal / CLI
  • Delete or archive detached OS and Data Managed Disks
  • Disassociate and release Public IP addresses
  • Delete orphaned Network Interface Cards (NICs)
  • Remove dead records from Azure Private DNS Zones

Summary & Operational Takeaway

An audit-ready Azure VM decommission guarantees clean resource groups, prevents orphaned cloud billing, and maintains complete compliance.

Pranusha Palaparthi, Cloud Ops Engineer
Written by

Pranusha Palaparthi

Cloud Operations Engineer based in Hyderabad with 7 years of AWS and Azure experience. Specialises in safe cloud decommissioning, production shutdowns, and audit-ready operations.