Skip to article
Compute Virtual Machines

Deallocated VM

A virtual machine state where compute allocation is released and billing changes accordingly.

Source: Microsoft Learn - Azure Virtual Machines documentation Reviewed 2026-05-03

Exam trap
Treating Deallocated VM as an isolated setting instead of checking the surrounding resource, network, identity, and deployment context.
Production check
Can you identify the subscription and resource group that own Deallocated VM?
Practice this topic Microsoft Learn
Article details and learning context
Aliases
None listed
Difficulty
intermediate
CLI mappings
5
Last verified
2026-05-03
Learning paths Learn Virtual machine operations Deallocated VM
Compare related concepts Search related resources Browse the glossary

Understand the concept

Why it matters

Deallocated VM matters because compute decisions become production behavior: cost, security, reliability, performance, and supportability all depend on whether the team understands the resource, setting, or pattern before changing it.

Technical context

In Azure, Deallocated VM belongs to the Virtual Machines area and usually shows up when a workload crosses resource configuration, identity, networking, data, or operations boundaries. The mapped CLI commands, especially commands near az vm list, help turn the term from a definition into something you can inventory, verify, automate, or troubleshoot.

Exam context

Compare with

Virtual machine Managed disk

Where it is used

Where you see it

  1. Virtual Machines
  2. VM scale sets
  3. Disks
  4. Images
  5. Boot diagnostics and extensions

Common situations

  • Choose or inspect the runtime that hosts an application, agent, database, or background worker.
  • Troubleshoot startup, networking, disk, image, or extension behavior.
  • Automate consistent server creation across environments.
  • Understand cost and availability tradeoffs before scaling or resizing.

Illustrative Azure scenarios

These examples show how the concept can affect design and operations. They are illustrative scenarios, not customer claims.

Using Deallocated VM in a production workload

A platform team can review Deallocated VM together with related Azure resources, CLI commands, and source docs before changing a live environment.

Azure CLI

Use Azure CLI for Deallocated VM when you need repeatable evidence or automation instead of a one-off portal check. Commands near az vm list let you inspect current state, script environment setup, compare dev/test/prod, and document exactly what changed.

Useful for

  • List VM and disk inventory before maintenance windows or cost reviews.
  • Start, stop, resize, or inspect compute resources from a repeatable operations script.
  • Capture VM configuration during an incident without depending on portal navigation.
  • Validate image, identity, network, and disk settings before redeployment.

Before you run a command

  • Run az account show and confirm the tenant, subscription, and user or service principal context.
  • Confirm the resource group, resource name, and region match the environment you intend to inspect or change.
  • Prefer read-only discovery commands first; only run mutating, cost-impacting, security-impacting, or destructive commands after review.
  • Copy command output into a change record or incident notes when the command is used for production evidence.

What the output tells you

  • Whether Deallocated VM exists at the expected Azure scope and under the expected resource owner.
  • Which location, SKU, identity, network, state, or relationship fields are currently configured.
  • Whether the command is showing a resource problem, an access problem, a naming/scope problem, or a missing dependency.
  • What safe follow-up command or related term should be checked next.

Mapped commands

Vm operations

direct 
az vm list --resource-group <resource-group>
az vmdiscoverCompute
read-only Microsoft Learn 
az vm show --name <vm-name> --resource-group <resource-group>
az vmdiscoverCompute
read-only Microsoft Learn 
az vm create --name <vm-name> --resource-group <resource-group> --image <image>
az vmprovisionCompute
cost-impacting Microsoft Learn 
az vm start --name <vm-name> --resource-group <resource-group>
az vmoperateCompute
mutating Microsoft Learn 
az vm stop --name <vm-name> --resource-group <resource-group>
az vmoperateCompute
mutating Microsoft Learn

Architecture context

A deallocated VM is a compute lifecycle state with real architecture consequences. The guest is stopped, allocated host capacity is released, and compute billing normally stops, but attached managed disks, snapshots, static public IPs, backup protection, reservations, and some monitoring costs can remain. In well-run environments, deallocation is handled through automation schedules, DevTest policies, deployment pipelines, or runbooks rather than ad hoc portal clicks. Architects design around the restart impact: dynamic IP changes, application warm-up, dependency ordering, patch windows, identity availability, and capacity constraints in the target region or zone. For stateful workloads, deallocation must be coordinated with backup, replication, and maintenance windows so cost savings do not turn into unplanned recovery work.

Security
Check OS access, managed identity, disk encryption, extension trust, and public IP exposure.
Cost
Watch VM size, uptime, disks, snapshots, reservations, and orphaned resources.
Reliability
Use availability zones, scale sets, backups, and restart policies where outages matter.
Performance
Match VM family, disk tier, accelerated networking, and scale settings to workload demand.
Operations
Script build, patch, start/stop, inventory, and cleanup operations to avoid manual drift.

Common mistakes

  • Treating Deallocated VM as an isolated setting instead of checking the surrounding resource, network, identity, and deployment context.
  • Copying a mutating or destructive CLI command into production without confirming subscription, resource group, and target resource name.
  • Treating Deallocated VM as just a label instead of checking the Azure scope, owner, and resource that it affects.
  • Running a mutating or destructive CLI command before confirming the active subscription, resource group, and target name.