Free tools Windows power users keep installed
One-click scans. No signup required.
If your Azure VM says Stopped, compute charges may still apply. To stop VM compute billing, the state needs to be Stopped (deallocated). Deallocation releases compute resources, but it does not remove the VM’s disks or other retained resources, which can continue to incur charges.
Stopped vs. Stopped (deallocated): what changes on the bill?
Azure distinguishes a VM that is stopped but still allocated from one that is stopped and deallocated. A shutdown performed inside the guest operating system can leave the VM allocated. In that state, Azure may continue charging for reserved compute capacity. Deallocation releases those compute resources, stopping VM compute charges while the VM remains available to start again. See Microsoft’s compute FinOps guidance and VM management tutorial.
As an Amazon Associate I earn from qualifying purchases.
| State or action | What happens to compute | What may still be billed |
|---|---|---|
| Stopped, still allocated | Compute resources remain reserved; compute charges may continue. | VM-related resources such as disks and networking resources, according to their own billing rules. |
| Stopped (deallocated) | Compute resources are released, so VM compute charges stop. | Retained disks, snapshots, public IP addresses, load balancers, and other chargeable resources, depending on the deployment. |
Why charges can continue after deallocation
Deallocation changes the VM’s compute state; it is not the same as deleting the VM or its persistent resources. Managed disks and snapshots can remain in the subscription after compute has been released, and their storage charges follow their own billing rules.
Managed disks
A disk’s charges depend on its type and configuration. Azure’s managed disk billing guidance covers Ultra Disk, Premium SSD v2, Premium SSD, Standard SSD, Standard HDD, and empty managed disks. Do not assume all disks are billed identically or calculate storage cost from a single universal rate. Microsoft notes that an empty managed disk that has never been used and has no underlying storage allocated does not incur disk storage charges; billing begins once storage is allocated.
#1 Best Overall
Snapshots
Snapshots have separate storage and transaction considerations. Microsoft describes both full and incremental snapshots, and transaction billing can apply in relevant cases. The applicable cost depends on the snapshot and its use; there is no single transaction charge that applies to every snapshot.
Networking and other retained resources
Depending on the deployment, public IP addresses, load balancers, bandwidth, and other associated resources may contribute to the bill. Deleting a VM does not necessarily delete every related resource: retained disks and networking resources can continue accruing charges. Microsoft’s VM cost-management guidance recommends accounting for the surrounding resources as well as the VM.
How to find the source of a continuing charge
- Verify the power state. In the Azure portal or your management tool, check that the VM is Stopped (deallocated), not simply Stopped.
- Inspect the resource inventory and billing details. Look for the VM’s OS and data disks, snapshots, public IP addresses, load balancers, and other resources associated with the deployment. Use the billing view and resource details to identify which resource or meter is generating the charge.
- Check whether each persistent resource is still needed. A disk or snapshot may be part of your recovery plan. Confirm your retention and backup needs before deleting it; deleting storage can remove data or recovery options.
- If the VM was deleted, check separately for leftovers. Verify whether disks and networking resources were retained, since deleting the VM alone may not remove them.
- Estimate savings using the actual configuration. Match the resource and meter details to current Azure pricing for the VM’s region and SKU, and the disk’s type, tier, and configuration. Usage and retained resources also affect the estimate, so there is no reliable universal saving figure.
Spot VM eviction is a separate case
For an Azure Spot VM, the eviction policy matters. With the Deallocate policy, an evicted VM can remain stopped-deallocated while its underlying disks continue to incur storage costs. The Delete eviction policy deletes the VM and its underlying disks, avoiding ongoing storage charges for those deleted disks. This is a Spot-specific policy choice, not a general recommendation to delete a production VM. Microsoft explains the policies in its Spot Virtual Machines documentation.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
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.
