Hi Martyn,
Thank you for your detailed report. Based on your description, it appears the issue is isolated to the AVD web client and not the underlying hostpool configuration, especially since the Windows App continues to access all three pools successfully.
This behavior has recently been observed by other users and may be related to a backend change in the web client or session broker service. While no configuration changes were made on your end, we recommend the following steps:
- Clear browser cache and test in an incognito/private window.
- Confirm that the affected hostpools are assigned to the correct workspace and that user permissions remain intact.
- Check the Azure portal for any service health advisories related to AVD.
- If the issue persists, consider opening a support ticket with session logs from the affected pools.
If this guidance helps clarify the situation, feel free to mark this answer as accepted so others can benefit too.
Thank you so much!!!
Best regards,