This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(12.8, 16%, 11%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EBM%3C/text%3E%3C/svg%3E)
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
Just come off a call with Microsoft support, apparently there is an issue the backend team are working on but they could not provide any timescale for a resolution. I also asked when the Azure status / service health would be updated to reflect the fact there is an issue and stop leaving users and admins in the dark, that too is apparently being looked at.
The only workaround is to use the Windows App until such time as they fix the issue with the web client.
Regards,
Martyn
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(121.6, 21%, 21%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMN%3C/text%3E%3C/svg%3E)
We had the exact same problem and just got off the call with Microsoft. Neither web interfaces URLs https://windows.cloud.microsoft/ and https://client.wvd.microsoft.com/arm/webclient/index.html were able to launch the host pool in question. Eventually Microsoft gave me a workaround that allowed both web URLs and Windows App to connect to the problem host pool. These are hybrid-joined machines for fyi. He added transport:i:1 to the Advanced option of RDP Properties for that host pool. However, this removes RDP Shortpath when connecting with Windows App. Web and Windows App will use the TCP Web Socket. Not ideal, but it allowed users to launch the virtual desktop.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(201.6, 90%, 29%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EQQ%3C/text%3E%3C/svg%3E)
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:
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,
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
Hi Burgess, Martyn,
Thanks for the update, and I completely understand how reassuring it is to know you're not the only one seeing this behavior. You've done a thorough job checking browser settings, assignments, and Azure service health—those are exactly the right steps.
Since the Windows App continues to work as expected, this still points to a web client-specific issue. We recommend keeping an eye on the Azure Service Health dashboard for any new advisories, as backend changes may not always be immediately reflected.
If the issue persists and no advisories appear, capturing session logs and opening a support ticket would be the best next step for deeper investigation.
If my answer is useful for you, please feel free to hit ACCEPT THE ANSWER to support me!!!
Thank you so much!!
Best regards,
