Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
To stop Azure VM compute charges, confirm the VM’s status is Stopped (deallocated), not just Stopped. A deallocated VM releases its compute resources, but it does not delete the VM’s managed disks, snapshots, or other retained resources. Those can continue to incur charges, so an idle VM may have no compute charge while its storage remains billable.
Stopped versus Stopped (deallocated)
Stopped and Stopped (deallocated) are different Azure VM states. A guest operating system shutdown can leave the VM stopped but still allocated, meaning its compute resources remain reserved and compute charges can continue. Deallocation releases those resources and stops VM compute charges. Microsoft explains the distinction in its FinOps best practices for compute and VM management tutorial.
Check the state Azure reports in the portal or the management tool you use; do not rely only on whether the guest operating system appears shut down. The status to look for when stopping compute billing is Stopped (deallocated).
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →What can still cost money after deallocation?
Deallocation releases compute capacity; it does not delete the VM or its persistent resources. Billing depends on each resource’s type and configuration.
#1 Best Overall
| Resource | What to know |
|---|---|
| VM compute | Compute charges stop when the VM is deallocated. |
| Managed disks | Disks remain available after deallocation and may continue to incur storage charges. Billing depends on disk type and configuration. |
| Snapshots | Snapshots have storage billing, and transaction charges can apply in relevant cases. Full and incremental snapshots do not all have identical billing considerations. |
| Networking and other retained resources | Public IP addresses, load balancers, bandwidth, and other resources may contribute charges depending on the deployment. |
Microsoft’s managed disk billing guidance covers Ultra Disk, Premium SSD v2, Premium SSD, Standard SSD, Standard HDD, snapshots, and empty managed disks. There is no single billing rule or price that applies to every disk. For example, an empty managed disk that has never been used and has no underlying storage allocated does not incur disk storage charges; charges begin once storage is allocated. Snapshot storage and transaction considerations also depend on the case.
How to find the charge
- Confirm the VM state. In the Azure portal or your management tool, verify it says Stopped (deallocated), rather than simply Stopped.
- Review the resources tied to the VM. Check the OS disk, data disks, snapshots, public IP, load balancer, and other associated resources in your resource inventory and billing details.
- Check for resources left behind after deletion. If you deleted the VM, inspect the resource list separately: disks and networking resources may have been retained and can continue accruing charges.
- Match the bill to current pricing. Use the actual resource and meter details, VM region and size, disk type and tier, configuration, and usage to estimate costs. A general estimate without those inputs can be misleading.
Microsoft’s cost-management guidance for virtual machines discusses the potential charges from related and retained resources. The charge on a bill depends on the resources actually present and how they are configured.
Should you delete disks or snapshots?
Deleting an unneeded disk or snapshot may remove its ongoing storage cost, but deletion can also remove data or recovery options. Confirm that you no longer need the resource and have an appropriate backup or retention plan before removing it. Whether deletion is safe depends on your workload and recovery requirements; deallocation alone does not make that decision for you.
Spot VM exception: eviction policy matters
For Azure Spot VMs, the eviction policy affects what remains after eviction. With the Deallocate policy, the VM can remain stopped-deallocated while its underlying disks continue to incur storage costs. With the Delete policy, the VM and its underlying disks are deleted, avoiding ongoing storage charges for those deleted disks. This is a Spot-specific policy choice, not a general recommendation to delete production VMs. See Microsoft’s Azure Spot Virtual Machines documentation.
Quick Recap
Best Value
Rank #3
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
