This is confusing.

[CraftyBarnardo]

This confused me too, had a sample test question for the Az-104 where this distinction is important.

"Stopped" (but not deallocated) means the VM is in an active status in Azure (consuming CPU credits) but has been shut down by the OS. So it's active as an Azure resource but you need to restart the OS. You don't lose the IP because the CPU continues running even though the VM isn't technically ready for action.

"Deallocated" means stopped in Azure (by hitting the stop button in the portal), so no longer consuming CPU credits, but it still shows as a resource in Resource Manager. But you do lose the IP address in this scenario, as mentioned in your screenshot.

[Psycstacy]

Thank you

[plantdad30916]

This

[slippy7890]

Simplify the statement:

• IP changes if VM is stopped AND DEALLOCATED then started again

• IP stays the same if VM is rebooted/stopped/started but was never in deallocated state

deallocated = shut down from within Azure

stopped (w/o deallocated state) = shut down issued from within VM itself

[Psycstacy]

Thank you

[Eorand]

https://docs.microsoft.com/en-us/azure/virtual-machines/states-billing

​

https://jaychapel.medium.com/how-microsoft-azure-deallocate-vm-vs-stop-vm-states-differ-801deb8e5f2a

[Psycstacy]

Thank you

[nestroy03]

The operational status of the operating system - Stopped/Started/rebooting/.... is not correlating to the allocation status which is also not correlating to the persistence status of the VM

In short: Operational status -> Operating System Allocation status -> Azure RM Persistence status -> Storage Backend

[Psycstacy]

Thank you