Menu
Here is a situation:
An Azure Windows 10 VM is working through a day and is being used via RDP without a problem, while suddenly RDP drops and RDP is no longer a mean to connect. Looking at Azure portal, in an Activity Log, one can see that the VM is deallocated and the Entity that started the action is VS DevTest Lab.
While I've been using some Azure Fluent API for .Net to test start and stop of VM, those tests never came up as being triggered by VS DevTest Lab.
Can someone explain what VS DevTest Lab mean when it comes to practically determining who triggered a VM deallocation? Thank you in advance.
623
You can also deallocate a VM using an Azure CLI command, such as azure vm deallocate. Deallocating stops the VM and releases all the compute resources so you are no longer charged for the VM compute resources. However, all persistent disks remain, such as the operating system disk and the attached data disks.
Azure's Deallocated State When you stop a VM through Azure, rather than through the OS, it goes into a “Stopped (deallocated)” state. This means that any non-static public IPs will be released, but you'll also stop paying for the VM's compute costs.
Azure DevTest Labs is a service for easily creating, using, and managing infrastructure-as-a-service (IaaS) virtual machines (VMs) and platform-as-a-service (PaaS) environments in labs.
Stopped (Deallocated): In this state, the instance is stopped through the management portal. This option is available at the bottom on the management portal. If you shut down the VM from here, it goes to the stopped (deallocated) state. Stopped (Deallocated) instance doesn't cost for VM compute hours.
I believe this is because in DevTest Labs you can have the auto-shutdown configured to save on expenses. Check to see if that is configured in the portal
97
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
