Azure Virtual Machines
An Azure service that is used to provision Windows and Linux virtual machines.
This suggestion does not work.
Cannot Connect to a Running VM
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(217.60000000000002, 22%, 31%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMH%3C/text%3E%3C/svg%3E)
Man Ho
0
Reputation points
I have a VM that is currently running. I can power On/Off/Restart/Hibernate the VM; however, I cannot connect to it. Every time I tried to connect via Web Browser or Windows App I got this error message:
"You can't connect to this dev box right now. Try stop then start it or contact your administrator."
Azure DevCenter shows the DevBox status as Good and NO issue. Networks also good.
Please help.
Thanks
Azure Virtual Machines
2 answers
Sort by: Most helpful
-
Man Ho 0 Reputation points
2026-10-16T04:16:02.1566667+00:00 -
Man Ho 0 Reputation points
2026-10-16T18:32:18.84+00:00 I restored one of the older snapshot of the DevBox and started it again. This time I can connect to the VM via the web-browser, haven't tried the Windows App.
Cheers.
Sign in to comment -
-
AI answer
2026-10-15T22:30:12.7866667+00:00 For a Dev Box connectivity failure where the dev box shows as Running/Good but Windows App and browser both return "You can't connect to this dev box right now", use Troubleshoot & repair first.
- Sign in to the developer portal.
- Confirm the dev box is running.
- If it is not running, start it and test the connection again.
- If it is already running, open the more actions (...) menu for the dev box and select Troubleshoot & repair.
- In Troubleshoot & repair connectivity, select Yes, I want to troubleshoot this dev box, then select Troubleshoot.
What this does:
- Checks critical connectivity components including domain join, SxS stack listener readiness, URL accessibility, VM power status, Azure resource availability, VM extensions, and Windows guest OS readiness.
- Usually completes in about 20 minutes, but can take up to 40 minutes.
- The dev box cannot be used during the process.
Important:
- Running Troubleshoot & repair might effectively restart the dev box.
- Any unsaved data on the dev box will be lost.
If the dev box was not running, starting it and reconnecting is the first check. If it was already running and still fails from both Windows App and browser, Troubleshoot & repair is the supported next step from the developer portal.
AI-generated content may be incorrect. Read our transparency notes for more information.