VM states (running, stopped, deallocated) in Azure - Step-by-Step Execution

Process Flow - VM states (running, stopped, deallocated)

VM Created

↓

Start VM

→VM Running

↓

Stop VM

→VM Stopped

↓

Deallocate VM

→VM Deallocated

↓

Start VM

This flow shows how a virtual machine moves between states: starting runs it, stopping pauses it, and deallocating frees resources.

Execution Sample

Azure

Create VM
Start VM
Stop VM
Deallocate VM
Start VM

This sequence creates a VM, starts it, stops it, deallocates it, then starts it again.

Process Table

Step	Action	VM State Before	VM State After	Notes
1	Create VM	None	Stopped	VM is created but not running yet
2	Start VM	Stopped	Running	VM is powered on and running
3	Stop VM	Running	Stopped	VM is powered off but resources still allocated
4	Deallocate VM	Stopped	Deallocated	VM resources are freed, no charges for compute
5	Start VM	Deallocated	Running	VM is allocated resources and powered on again

💡 After step 5, VM is running and ready for use.

Status Tracker

VM State	Start	After Step 1	After Step 2	After Step 3	After Step 4	After Step 5
state	None	Stopped	Running	Stopped	Deallocated	Running

Key Moments - 3 Insights

Why is the VM state 'Stopped' after creation and not 'Running'?

When a VM is created, it is initially in the 'Stopped' state because it is not powered on yet. This is shown in execution_table row 1.

What is the difference between 'Stopped' and 'Deallocated' states?

'Stopped' means the VM is powered off but still holds resources and incurs charges. 'Deallocated' means resources are freed and no compute charges apply, as seen in rows 3 and 4.

Can you start a VM directly from the 'Deallocated' state?

Yes, starting a VM from 'Deallocated' reallocates resources and powers it on, shown in row 5.

Visual Quiz - 3 Questions

Look at the execution table, what is the VM state after step 3?

A Stopped

B Running

C Deallocated

D None

💡 Hint

Check the 'VM State After' column for step 3 in the execution_table.

At which step does the VM free its resources and stop incurring compute charges?

A Step 2

B Step 4

C Step 3

D Step 5

💡 Hint

Look for the 'Deallocated' state in the execution_table and notes.

If you start the VM immediately after creation, what will be the VM state after that action?

A Stopped

B Deallocated

C Running

D None

💡 Hint

Refer to step 2 in the execution_table where 'Start VM' changes state to 'Running'.

Concept Snapshot

VM states in Azure:
- Created VM starts in 'Stopped' state.
- 'Running' means VM is powered on.
- 'Stopped' means VM is off but resources held.
- 'Deallocated' means resources freed, no compute charges.
- You can start VM from 'Stopped' or 'Deallocated' to run it.

Full Transcript

This lesson shows how an Azure virtual machine changes states. When you create a VM, it starts in the stopped state, meaning it is off but ready. Starting the VM powers it on and it becomes running. Stopping the VM powers it off but keeps resources allocated, so you still pay for them. Deallocating the VM frees those resources and stops compute charges. You can start the VM again from either stopped or deallocated states to run it. The execution table traces these state changes step by step.

Practice

1. What does the deallocated state mean for an Azure VM?

easy

A. The VM is off and resources are freed.

B. The VM is running and using resources.

C. The VM is off but still reserving resources.

D. The VM is paused but still running.

Solution

1. Step 1: Understand VM states

   Azure VMs can be running, stopped, or deallocated. Running means active, stopped means off but resources reserved, deallocated means off and resources freed.

2. Step 2: Identify deallocated meaning

   Deallocated means the VM is turned off and Azure releases the compute resources, so you don't pay for them.

3. Final Answer:

   The VM is off and resources are freed. -> Option A

4. Quick Check:

   Deallocated = off + freed resources [OK]

Hint: Deallocated means VM off and no resources reserved [OK]

Common Mistakes:

• Confusing stopped with deallocated
• Thinking deallocated still uses resources
• Assuming deallocated means paused

2. Which Azure CLI command correctly stops a VM and releases its resources?

easy

A. az vm pause --name MyVM --resource-group MyGroup

B. az vm stop --name MyVM --resource-group MyGroup

C. az vm shutdown --name MyVM --resource-group MyGroup

D. az vm deallocate --name MyVM --resource-group MyGroup

Solution

1. Step 1: Review Azure CLI commands for VM states

   To stop a VM but keep resources, use az vm stop. To stop and free resources, use az vm deallocate.

2. Step 2: Identify command that releases resources

   az vm deallocate stops the VM and releases compute resources, matching the question.

3. Final Answer:

   az vm deallocate --name MyVM --resource-group MyGroup -> Option D

4. Quick Check:

   Deallocate command frees resources [OK]

Hint: Use 'deallocate' to stop VM and free resources [OK]

Common Mistakes:

• Using 'stop' which keeps resources reserved
• Confusing 'shutdown' with deallocate
• Using non-existent 'pause' command

3. If an Azure VM is in the stopped state, what happens to billing for compute resources?

medium

A. Billing doubles due to stopped state overhead.

B. Billing stops immediately as VM is off.

C. Billing continues because resources are reserved.

D. Billing pauses but storage costs continue.

Solution

1. Step 1: Understand billing for stopped VMs

   When a VM is stopped (not deallocated), compute resources are still reserved, so billing continues for compute.

2. Step 2: Differentiate from deallocated state

   Only when VM is deallocated are compute resources freed and billing stops for compute.

3. Final Answer:

   Billing continues because resources are reserved. -> Option C

4. Quick Check:

   Stopped = billing continues [OK]

Hint: Stopped VMs still reserve resources and incur charges [OK]

Common Mistakes:

• Assuming billing stops when VM is stopped
• Confusing storage billing with compute billing
• Thinking stopped means deallocated

4. You tried to start a VM but got an error because it is in the deallocated state. What should you do to fix this?

medium

A. Run az vm start to allocate and start the VM.

B. Run az vm stop to release resources first.

C. Run az vm restart to reset the VM state.

D. Run az vm deallocate again to confirm.

Solution

1. Step 1: Understand VM start from deallocated

   A VM in deallocated state has no resources allocated. To use it, you must start it which allocates resources and powers it on.

2. Step 2: Identify correct command to allocate and start

   az vm start allocates resources and powers on the VM, fixing the error.

3. Final Answer:

   Run az vm start to allocate and start the VM. -> Option A

4. Quick Check:

   Start command allocates resources [OK]

Hint: Use 'start' to allocate and power on deallocated VM [OK]

Common Mistakes:

• Trying to stop or deallocate an already deallocated VM
• Using restart which requires VM to be running
• Not allocating resources before starting

5. You want to save costs by stopping your VM but keep its IP address and disk data intact. Which state should you use and why?

hard

A. Use running state but reduce VM size to save costs.

B. Use stopped state because it keeps resources reserved including IP and disks.

C. Use deallocated state because it frees all resources including IP address.

D. Use stopped state because it frees compute resources but keeps IP.

Solution

1. Step 1: Understand resource reservation in stopped state

   When a VM is stopped (not deallocated), compute resources are reserved, so the IP address and disk data remain intact.

2. Step 2: Compare with deallocated state

   Deallocated frees compute resources and may release dynamic IP addresses, so IP might change.

3. Final Answer:

   Use stopped state because it keeps resources reserved including IP and disks. -> Option B

4. Quick Check:

   Stopped = keep IP and disks reserved [OK]

Hint: Stopped keeps IP and disks; deallocated frees resources [OK]

Common Mistakes:

• Choosing deallocated and losing IP address
• Thinking stopped frees compute resources
• Trying to save costs by resizing while running