Hi
its sounds like your Session Host VMs have been activated with a single-session license activation key instead of a multi-session key. I've seen this happen before with AVD deployments where custom images are SysPrep-ed and then AVD Pools built using the custom image. Changing the license key normally fixes the problem. Its likely that in the portal when you check the VM, it will show the OS as "Windows 10" instead of "Windows 10 Multi-Session"
Unless you have other working AVD Pooled VMs that you can export the activation keys from, I would suggest raising a support request through the Azure Portal to get this resolved.
Hope this helps,
Thanks
Michael Durkan
- If the reply was helpful please upvote and/or accept as answer as this helps others in the community with similar questions. Thanks!