Azure Virtual Desktop Web Client - Hostpools visible but not responding to being clicked on

Burgess, Martyn 10 Reputation points
2025-11-04T20:18:44.79+00:00

Hi,

Bit of a strange one this, we have 3 different hostpools configured in AVD and these have been working fine for nearly 3 years now, we originally started with WVD so not new to this.

In the last couple of days we have noticed that although all the hostpools are visible in the web client two of them do not respond to being clicked on. The hosts in those pools are available, and normally any messages related to problems with the hosts would come later after the next authentication prompt.

I have reproduced the issue on Edge, Chrome and Firefox and on both corporate and personal devices. We have not changed any configuration in the time since it was last known to work.

I have tried the 'Windows App' and that works fine to access all three pools which to me suggests the issue is not with the parts of the environment we can control.

Is anyone else having a similar issue?

Regards,

Martyn

Windows for business | Windows Client for IT Pros | User experience | Configure Azure Virtual Desktop
0 comments

7 answers

Sort by: Newest
Most helpful Newest Oldest
  1. Burgess, Martyn 10 Reputation points
    2025-11-05T09:10:42.7366667+00:00

    Thanks, its good to know we are not alone! I have tried clearing caches, cookies and turning off browser protection settings. The assignments / permissions are unchanged, and of course when not assigned the hostpools dont show in the web client as expected. There was nothing on the Azure status or service health pages yesterday I will have another look this morning.

    Regards,

    Martyn

    Was this answer helpful?

    0 comments
  2. Quinnie Quoc 11,835 Reputation points Independent Advisor
    2025-11-05T03:44:59.48+00:00

    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:

    1. Clear browser cache and test in an incognito/private window.
    2. Confirm that the affected hostpools are assigned to the correct workspace and that user permissions remain intact.
    3. Check the Azure portal for any service health advisories related to AVD.
    4. 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,

    QQ

    Was this answer helpful?

    0 comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.