Azure VM Stopped vs Deallocated: Billing and What Costs A VM that shows as powered off in Azure can still be billing you for compute. Shut it down from inside Windows or Linux, and Azure keeps the hardware reserved. The meter keeps running.

Flexera's 2026 report puts wasted IaaS and PaaS spend at an estimated 29%. That figure covers cloud spend broadly, not Azure VMs alone. Still, idle VMs left in the wrong state are one of the easiest leaks to plug.

This guide compares "Stopped" and "Stopped (deallocated)," shows which costs survive deallocation, and gives you commands to verify the state.

Key Takeaways

  • A guest OS shutdown leaves compute allocated and billable.
  • Deallocation stops compute charges, but disks and other resources keep billing.
  • Always confirm the exact status in the Portal, CLI, or PowerShell.
  • Pick a state based on restart needs, IP dependencies, disk type, and total cost.

Azure VM Stopped vs Deallocated: Quick Comparison

Per Microsoft's states documentation, a Stopped VM is powered off but still allocated on a host, so it is billed. A Deallocated VM has released that hardware, so compute is not billed.

Dimension Stopped (allocated) Stopped (deallocated)
Compute billing Continues Stops
OS and data disks Billed Still billed
Typical trigger Shutdown inside Windows or Linux, az vm stop Portal Stop, az vm deallocate, default Stop-AzVM, auto-shutdown
Restart Allocation retained Azure provisions compute again; capacity can be a constraint
Static public IP Retained, billed Retained, billed
Dynamic public IP (legacy Basic) Retained Can change on restart

Stopped versus deallocated Azure VM billing comparison

Retained allocation is not a promise of the same physical host. Azure healing can move a VM to a healthy machine while preserving its disks.

What Happens When You Stop an Azure VM?

Stopped: meaning, billing, and use cases

Run shutdown on Linux or use the Windows Start menu, and the guest OS powers off. Azure still holds the CPU and memory for you, so the VM shows Stopped and compute billing continues.

That compute charge is only part of the bill; storage and other attached resources still need their own review. This state only makes sense for brief interruptions, when keeping the allocation matters more than saving a few idle hours.

Stopped (deallocated): meaning, billing, and use cases

Deallocation is an Azure-level action. It powers down the VM and releases the compute allocation. Compute charges generally stop once it succeeds.

You may still be billed for:

  • Managed disks and snapshots
  • Azure Backup recovery points
  • Static public IPs
  • Log Analytics retention
  • NAT Gateway
  • Reservation or savings plan commitments

Deallocation fits dev and test boxes, overnight shutdowns, and any workload idle long enough that compute savings outweigh restart trade-offs.

How to deallocate and verify the state

Portal: Open Virtual machines, select the VM, click Stop, then wait for Stopped (deallocated).

CLI:

az vm deallocate --resource-group MyResourceGroup --name MyVm
az vm get-instance-view -g MyResourceGroup -n MyVm

Note that az vm stop only powers off. It stays billable.

PowerShell:

Stop-AzVM -ResourceGroupName "myResourceGroupVM" -Name "myVM" -Force
Get-AzVM -ResourceGroupName "myResourceGroupVM" -Name "myVM" -Status

Stop-AzVM deallocates by default. Adding -StayProvisioned keeps the allocation and continues billing.

For fleet-wide checks, use Azure Resource Graph:

Resources
| where type == 'microsoft.compute/virtualmachines'
| summarize count() by PowerState = tostring(properties.extended.instanceView.powerState.code)

Check power state, not provisioning success. A failed automation job can leave a VM stopped but billable. Cost Management is no substitute for a live check. Data typically lags 8 to 24 hours for EA and MCA accounts, and up to 72 hours for pay-as-you-go.

Azure VM state verification workflow across Portal CLI PowerShell

Before automating deallocation, run through this checklist:

  • Does anything depend on a dynamic public IP?
  • Do you need a static IP, and are you willing to pay for it while idle?
  • Is the OS disk ephemeral? Stop and deallocate are unsupported there.
  • Do backup policies and monitoring agents tolerate downtime?
  • Does the application have a clean shutdown procedure?

Azure VM Stopped vs Deallocated: Which Is Better?

For most idle periods, deallocated wins. But compare total cost, not compute alone.

Run the numbers

Take a Standard_D2s_v5 in East US. Microsoft's retail API lists Linux at $0.096/hour and Windows at $0.188/hour, while a P10 Premium SSD costs $19.71/month. Deallocating removes the hourly rate for idle time. The P10 disk charge stays regardless.

Windows and SQL pay-as-you-go pricing FAQs state that a deallocated instance isn't billed for those meters. A stopped instance still bills allocated vCores rather than a separate standalone license charge.

When each state fits

  • Stopped, not deallocated: Use for rapid restart, a short maintenance window, or when you need to hold allocation.
  • Deallocated: Use for predictable idle periods when the workload tolerates reprovisioning and you've confirmed IPs, data, and services persist.

Commitments don't pause

Per Microsoft's documentation on reservation discounts, unused reservation hours don't carry forward. The discount moves to another matching resource in scope, or that hour is lost. Savings plans work the same way. Paid support plans also continue regardless of VM power state. Verify your own billing terms.

Production and automated environments

  • Validate application dependencies before you change power state
  • Use schedules with failure alerts
  • Tag resources with owner and shutdown policy
  • Review actual billing after rollout

Decision rule: confirm required availability and restart behavior, deallocate when the VM is genuinely idle, then audit what's left. The bill won't reach zero.

Real World Examples

Carlsberg Group's Microsoft customer story, published October 2024, describes snoozing policies for Azure SAP development and sandbox environments, avoiding unused nights and weekends.

By the end of 2019, combined VM rightsizing, storage optimization, reservations, and policies like snoozing produced 7-10% annual cost savings.

That number is a multi-intervention result, not a shutdown-only benchmark. The lesson is governance: Carlsberg used Azure Policy and tagging to make shutdown the default for non-production.

What remained after snoozing? Disks, for one. Managed disks keep billing while VMs sleep, so idle or oversized block storage becomes its own waste category once compute is under control.

Lucidity addresses that remaining gap. It provides real-time multi-cloud block storage visibility and autonomous optimization across AWS, Azure, and Google Cloud, with cost reductions of up to 70% on block storage:

  • Focuses on disk waste left after VMs are deallocated
  • Does not deallocate VMs or touch compute optimization
  • Targets idle and oversized block storage that keeps billing while compute sleeps

Conclusion

Shutting down a VM inside its OS isn't the same as deallocating it through Azure. The right choice depends on restart needs, schedules, and operational risk.

Deallocation stops compute billing but not charges for disks, static IPs, backups, or commitments. Verify the actual status, then review the full resource bill.

Frequently Asked Questions

What happens when an Azure virtual machine is stopped?

An OS-level shutdown leaves the VM Stopped with compute still allocated, so compute billing continues. "Stopped (deallocated)" releases the compute allocation, and compute charges stop.

Does stopping an Azure VM stop billing?

Not necessarily. Compute billing continues unless the VM is successfully deallocated. Disks and other resource charges remain either way.

What is the difference between stopped and stopped (deallocated) in Azure?

Stopped keeps the hardware allocated and billed. Deallocated releases it, so compute isn't billed, but restart requires fresh provisioning. Confirm the status in the Portal, CLI, or PowerShell.

What costs continue when an Azure VM is deallocated?

Managed disks, snapshots, backups, static public IPs, Log Analytics retention, NAT Gateway, and unused reservation or savings plan commitments can all continue. Check each resource individually.

How do I deallocate an Azure VM using the Portal, CLI, or PowerShell?

Use Stop in the Portal, az vm deallocate in the CLI, or Stop-AzVM in PowerShell. In every case, wait until the status reads "Stopped (deallocated)."

Does deallocating an Azure VM change its IP address or delete its data?

Static IPs persist, while legacy dynamic IPs can change on restart. Persistent OS disks are kept and the temporary disk is wiped. Ephemeral OS disk VMs don't support stop-deallocate, so verify first.