![](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)
Azure Virtual Machines
An Azure service that is used to provision Windows and Linux virtual machines.
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.