Issue starting VMs in Azure Lab Services (January 2024)

Question

I have a VM in Azure Lab Services that is currently in stopped state. When I try to start it from the UI, the start toggle resets back to stopped state in about 60 seconds. The VM never starts.

On the surface, this appears to be related to this older issue, but I am starting a new thread since that issue was resolved 2+ years ago.

Answer 1

Hello, @CG ! Thank you for the update! I'm adding comments from [the other thread](https://learn.microsoft.com/en-us/answers/questions/821321/vms-in-azure-lab-services-are-not-starting-(4-21-2?page=1&orderby=Helpful&comment=answer-821637#newest-answer-comment) here for tracking and resolution.

Why is my VM in Azure Lab Services not starting? My VM will start but toggle back to stopped after 60 seconds.

There is currently an outage affecting GPU labs using lab accounts. The status of this outage will be kept up to date here:

https://techcommunity.microsoft.com/t5/azure-lab-services-blog/outage-gpu-labs-that-use-lab-accounts/ba-p/4020895

If you are using a lab account with our service and are utilizing one of these virtual machine sizes:

• Small GPU (Compute)
• Small GPU (Visualization)
• Medium GPU (Visualization)

You may get an allocation error, similar to this, when starting the virtual machine in a lab using any of the above virtual machine sizes: "Unable to start due to Allocation failed. We do not have sufficient capacity for the requested VM size in this region."         This is due to the Azure virtual machine families (NV and NC) that back these three virtual machines sizes being deprecated.         We are working with internal teams to mitigate the issue and are considering various options as a solution for the issue. Please come back to this post to get the latest update.

---

I hope this has been helpful! Your feedback is important so please take a moment to accept answers.

If you still have questions, please let us know what is needed in the comments so the question can be answered. Thank you for helping to improve Microsoft Q&A!