My Azure Virtual Desktop users suddenly can't trigger automatic startup for their session host VM. When the first user tries to connect, they immediately receive: "We couldn't connect because there are currently no available resources. Try again later or if this keeps happening ask your admin or tech support for help." The VM starts normally when I turn it on manually in the Azure portal, and the configuration and roles appear to be correct. There's no waiting notification in the client and nothing useful in the event logs. This environment hasn't been changed in about a year. Has anyone else seen this behavior recently?
2 Answers
Since the VM starts manually without any problem, it may not be a guest OS issue. Check whether there’s an Azure capacity or regional service problem affecting automatic startup. Normally the first connection should place the host in a starting or waiting state, so an immediate “no resources available” response suggests the startup request may not be reaching the host pool properly.
There appear to be broader Azure Virtual Desktop control-plane problems happening as well. I’ve seen new session host deployments report that the host pool doesn’t exist even though the VMs actually deploy and register as healthy. The failed deployment then leaves the configuration stuck, so this could be related to a temporary service-side issue rather than a local setting.
In my case the issue has continued for several days, so it may be more than a short-lived outage.
Manual startup works, but the connection attempt fails immediately without showing any waiting state. I also don’t see anything in the event logs.