How to review an Azure stopped-but-billing vm
A VM stopped from inside the guest can remain allocated. Compute billing generally stops only when Azure reports the VM as deallocated; attached disks, public IP configurations, and other resources may still bill after deallocation.
Confirm Azure's allocation stateWho reviews this signal?
- Accountable owner
- Compute / workload owner
- Review cadence
- Daily for non-production; weekly overall
Check observation dates and read-only scope. Your team approves and implements changes outside Costframe.
How this finding happens
- →An operator shuts down the guest OS instead of deallocating the VM through Azure.
- →A maintenance script stops the OS but does not complete the provider deallocation step.
- →A development environment has no automatic schedule or owner.
Collected evidence and verification limits
Checked when available
- ✓Azure instance power state, distinguishing stopped from deallocated
- ✓Recent state observations and activity history
- ✓Associated disks, IPs, and other resources that continue to carry cost
- ✓Current compute ActualCost or rate evidence
Not always verifiable
- —A stopped state may be brief during maintenance.
- —Deallocation can release a dynamic public IP and can affect ephemeral data.
- —Stopping compute does not remove storage and networking charges.
Missing or stale evidence is a limitation, not a passed check.
Why this finding might be wrong
These conditions lower confidence or require manual owner review before action.
- Approved maintenance window
- VM awaiting an imminent restart or image operation
- Failover workflow whose state transition is still in progress
- Environment where dynamic IP or host placement must be preserved
Plan the change and recovery path.
- Confirm the workload owner and why the VM is stopped.
- Check ephemeral disk, dynamic IP, host, licensing, and availability implications.
- Deallocate through Azure if the workload can tolerate it; otherwise document the exception and expiry.
- Review attached resources separately rather than claiming the entire resource cost disappears.
Rollback / recovery
Start the VM and validate networking, storage, agents, and application health. A released dynamic IP or ephemeral state may require additional recovery.
How savings are calculated
Direct compute saving is the stopped-but-allocated compute meter that ceases after deallocation. Persistent disks and other attached services remain excluded.
Do not quote a quantified saving when the billing scope, pricing basis or required workload evidence is incomplete or stale. Treat a modeled amount as estimated until suitable billed outcomes support it.
Check the billed outcome
Azure reports deallocated and the compute meter stops while remaining charges are itemized.
Confirm Azure's allocation state
Check the VM instance view rather than its guest shutdown status. Ask the owner whether it must restart on a schedule, then plan deallocation through the normal change process. Review disk and IP charges independently because they can remain after compute billing stops.
Review remaining disk chargesIf the owner cannot resolve a dependency or recovery requirement, keep the candidate in review rather than treating it as approved.