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.