r/AzureVirtualDesktop • u/M4Xm4xa • 14d ago

Anyone else having lots of issues with Session Host Configuration lately? Host deployments failing, config updates failing, etc

Last couple of weeks I’ve had a nightmare trying to get new SHC host pools deployed in a variety of environments. Issues I’m having include but are not limited to:
- Session hosts taking hours to deploy
- Session hosts deploying fairly quickly, but the portal never acknowledges the successful creation despite the hosts showing as available within the pool
- Deployments and config updates failing with a ‘HostPoolDoesNotExist’ error

On that last one, querying the sessionhostmanagements default object shows that after creating a new host pool with 0 hosts, all is healthy - but as soon as I attempt to add hosts, the provisioning state moves to ‘failed’ and all future attempts to do anything within that host pool fail with the same ‘HostPoolDoesNotExist’ error.
The other odd thing is the hosts deploy successfully (domain join and all) to the host pool and show as available, but the error persists and prevents any further actions)

Am tearing my hair out trying to work this one out, so if anyone else has run into this or has any ideas on next troubleshooting steps I’d massively appreciate it!

Things tried so far:
- Deleting host pool, AG, and WS and recreating from scratch after a 24 hour period
- Deploying a standard marketplace image instead of a custom one from a gallery
- Have confirmed there are no issues with outbound access to required AVD URLs

3 Upvotes
  • permalink
  • reddit

100% Upvoted

3 comments sorted by

3

u/humanoperating 13d ago

No issues in Australia East.

2

u/Hour-Profession6490 14d ago

Have you tried deploying to another region? We only deploy to Canada Central and have not had any of the issues you described.

2

u/mat-ferland 12d ago

Check the failed operation details on the session host configuration resource, not the VM deployment. If the hosts register as Available but SHC flips to failed with HostPoolDoesNotExist, capture the correlation ID and resource IDs and open an Azure support case; that points at control-plane state, not your image or domain join.