In this article
Guest shutdown can leave allocated compute billable. Verify the final VM power state, then review independently retained disks and network resources.
Azure Stopped is not equivalent to Deallocated. A stopped but allocated VM can continue incurring compute charges. Deallocation releases the hardware allocation, but disks and some networking resources can remain billable. Check the actual power state and related objects rather than the application’s reachability.
Do not infer billing from guest shutdown
Shutting down Linux or Windows can leave the machine allocated to a host. Closed SSH or an unavailable notebook does not prove that compute allocation ended. Inspect the VM through the documented control-plane interface after the operation.
Save exact state, time and resource ID. “We turned it off” is too vague to reconcile a later bill. If an automation performs the action, inspect its result and log; the scheduled intention does not prove the operation completed successfully.
Compare states with resource components
| State or object | What to understand |
|---|---|
| Running | Active billable compute |
| Stopped Allocated | Equipment remains allocated and billable |
| Deallocated | Compute allocation released |
| Managed disk | Independent storage lifecycle and expense |
| Networking | Its own retention and pricing rules |
Distinguish the final power state from a transitional or provisioning state. Successful configuration is not evidence that hardware was released at the end of the day.
Test an evening-pilot procedure
Suppose a researcher shuts down the guest OS and leaves. The next day compute charges remain. The team checks the power state, finds that allocation continued and replaces the vague closing instruction with a documented control-plane action and verification.
After releasing compute, it checks disks and addresses separately. Keep necessary data intentionally with an owner and retention date. The goal is an explained residual cost, not indiscriminate deletion of every result to obtain a zero immediately.
Account for a later restart
A deallocated VM needs equipment allocated again. The documented allocation-failure guidance describes possible shortages during start and other operations. A retained disk and approved quota do not guarantee an immediate GPU restart.
For a fixed working window, plan the startup and investigate the appropriate supported availability mechanism. A concise close-out routine saves results, performs the chosen operation, verifies its final state and inventories retained components. Compare subsequent charges with those expectations using the saved IDs and times, rather than changing settings randomly after an unclear bill.
Turn the check into a practical next step
Guest shutdown can leave allocated compute billable. Verify the final VM power state, then review independently retained disks and network resources.
For the documented details, consult the primary documentation; configuration reference. Continue with azure gpu regional family quotas and cloud gpu resource cleanup audit.