By FinOps Beacon · Published
Do stopped Azure VMs still cost money?
Yes. A stopped but allocated Azure virtual machine still incurs compute charges. Deallocation stops instance-usage billing, but it does not make the whole deployment free. Check the power state first, then the associated resources and billing period.
| Power state | Compute usage | Meaning |
|---|---|---|
| Running | Billed | The VM is running. |
| Stopped (allocated) | Billed | The VM remains allocated to a host. |
| Stopped (deallocated) | Not billed | The VM has released its host allocation. |
Source: Microsoft's VM states and billing reference. This table concerns instance usage, not prepaid commitments or every related service.
Why shutting down the operating system is different
Shutting down inside Windows or Linux can leave the VM in the allocated state. In the Azure portal, inspect the VM's current power status and look specifically for Stopped (deallocated). Do not use provisioning status, such as Succeeded, as evidence that compute billing stopped. Microsoft's state definitions distinguish the two.
Before requesting deallocation, confirm the workload can tolerate an interruption. Check dependencies, restart procedures, and data storage with the owner. Temporary-disk data may be lost when a VM stops; it is not a substitute for durable storage. See Microsoft's temporary-disk guidance.
Which charges can continue after deallocation?
Managed disks: retained OS and data disks have their own costs. Include associated storage in your review, even when the compute instance is off. Deleting a VM can also leave billable resources behind, depending on its deletion settings. See Microsoft's VM cost planning guide.
Static public IP addresses: these can remain billable while the attached VM is deallocated. Check the address's allocation method and SKU against Azure public IP pricing. Do not assume all networking charges follow the VM's power state.
Other retained services: investigate snapshots, backup retention, and separately provisioned network services where your bill shows them. A snapshot exists independently of its source disk. Review its purpose before removal; see Microsoft's managed-disk snapshot explanation.
Reservations and savings plans need a separate check
Deallocating a VM does not automatically produce an equivalent reduction in a prepaid or committed bill. A reservation benefit can move to another matching resource in scope; otherwise the unused hour is lost. See how VM reservation discounts apply.
A savings plan's hourly commitment continues, and unused commitment does not roll over. Review eligible usage across its scope before counting a shutdown as cash savings. Microsoft explains this in its savings plan overview.
How to investigate the next cost report
- Record the VM's resource ID, confirmed power state, and time of deallocation.
- Inspect the VM and associated disk, IP, and service line items separately.
- Compare usage dates after the change with an equally long, completed period before it.
- Check whether reservations or savings plans changed where costs were assigned.
- Keep the measured result separate from the original savings estimate.
Cost data can arrive late, and reports retain past usage for resources that are now stopped or deleted. A charge visible today may describe earlier consumption. Consult Microsoft's cost-data timing and coverage before concluding that deallocation failed.
Make stopped-VM review part of a repeatable process
Use the broader Azure cost optimization checklist to connect each finding to an owner and verified outcome. FinOps Beacon brings resource context, cost history, and recommendations into one workspace; it performs read-only scans and does not change your infrastructure.
Read the self-serve setup guide, then try the 14-day Business trial with no card. Paid continuation is $49/month for Pro or $199/month for Business; an unpaid expired trial cannot continue scanning.