Azure Virtual Desktop fails UrlsAccessibleCheck

Question

Azure Virtual Desktop fails UrlsAccessibleCheck

Jim Nickell 0

I get the following error for all session hosts.

This health check verifies that the required AVD service and Geneva URLs are reachable from the session host, including the RdTokenUri, RdBrokerUri, RdDiagnosticsUri, and storage blob URLs for Geneva agent monitoring. If this check fails, it may be fatal. Learn more

To resolve this, you'll need to reconfigure your networking, firewall, or proxy settings to unblock the following inaccessible URLs:

rdbroker.wvd.microsoft.com
rdbroker-g-us-r1.wvd.microsoft.com
rddiagnostics-g-us-r1.wvd.microsoft.com
rdgateway-host-green-c101-wus-r1.wvd.microsoft.com

Anonymous

2024-10-16T23:36:10.28+00:00
Hi Jim Nickell,

Thank you for reaching out to us on the Microsoft Q&A forum.

Based on your query, it appears that your Azure Virtual Desktop (AVD) session hosts are unable to reach essential URLs required for AVD services and Geneva monitoring. To resolve this issue, please review and update your network, firewall, or proxy settings to ensure that outbound traffic is allowed to the required URLs over TCP port 443.

For your reference, please refer to the following documentation:

Azure Virtual Desktop Required FQDN Endpoint

Azure Virtual Desktop Session Host Status Health Checks

If you find this information helpful, kindly consider Upvote on the post.
Jim Nickell 0 Reputation points

2024-10-17T17:55:12.6366667+00:00

This is an interesting problem. Our VDI environment has been operable since 2019. VDI worked at the beginning of this week, then suddenly started failing. We have made no adjustments to our network either. When you say, "your firewall", I presume you are referring to the Azure firewall, not site firewalls. Is that correct?
Jim Nickell 0 Reputation points

2024-10-17T18:23:15.8366667+00:00

I have also confirmed I can reach 3 of the 4 URLs you listed from our firewall. The only URL that does not reply is rdgateway-host-green-c101-wus-r1.wvd.microsoft.com

Our Azure firewall is a Cisco Meraki VMx appliance. I have also restarted the appliance with no luck. Outbound is set to Any - Any.

I have also confirmed that URL is not reachable (via ping) from my home network. Not just at work.
Anonymous

2024-10-17T21:24:23.9566667+00:00

Hi Jim Nickell,

Thank you for sharing the update!
We will check with our internal team and will get back to you soon.
Anonymous

2024-10-22T01:50:43.0333333+00:00

Hi Jim Nickell,
Thanks for sharing more information on this issue.

As you have mentioned three URLs are working out of four. I suggest filing a support case to investigate this issue further. The support team will be able to examine the situation and assist in resolving the issue.

If you don't have the ability to open a technical support ticket, please let me know and I can help you further with this.
Jim Nickell 0 Reputation points

2024-10-22T17:14:35.7166667+00:00

I have resolved this issue. I created outbound "Allow" firewall policies on the Azure hosted Cisco Meraki vMX appliance. I'm really not sure why this change needed to be made. This environment has been in production since 2021 and nothing changed. It suddenly broke about 2 weeks ago, right around Patch Tuesday.

1 answer

Your answer

Anonymous

2024-10-16T23:36:10.28+00:00

Hi Jim Nickell,

Thank you for reaching out to us on the Microsoft Q&A forum.

Based on your query, it appears that your Azure Virtual Desktop (AVD) session hosts are unable to reach essential URLs required for AVD services and Geneva monitoring. To resolve this issue, please review and update your network, firewall, or proxy settings to ensure that outbound traffic is allowed to the required URLs over TCP port 443.

For your reference, please refer to the following documentation:

Azure Virtual Desktop Required FQDN Endpoint

Azure Virtual Desktop Session Host Status Health Checks

If you find this information helpful, kindly consider Upvote on the post.
Jim Nickell 0 Reputation points

2024-10-17T17:55:12.6366667+00:00

This is an interesting problem. Our VDI environment has been operable since 2019. VDI worked at the beginning of this week, then suddenly started failing. We have made no adjustments to our network either. When you say, "your firewall", I presume you are referring to the Azure firewall, not site firewalls. Is that correct?
Jim Nickell 0 Reputation points

2024-10-17T18:23:15.8366667+00:00

I have also confirmed I can reach 3 of the 4 URLs you listed from our firewall. The only URL that does not reply is rdgateway-host-green-c101-wus-r1.wvd.microsoft.com

Our Azure firewall is a Cisco Meraki VMx appliance. I have also restarted the appliance with no luck. Outbound is set to Any - Any.

I have also confirmed that URL is not reachable (via ping) from my home network. Not just at work.
Anonymous

2024-10-17T21:24:23.9566667+00:00

Hi Jim Nickell,

Thank you for sharing the update!
We will check with our internal team and will get back to you soon.
Anonymous

2024-10-22T01:50:43.0333333+00:00

Hi Jim Nickell,
Thanks for sharing more information on this issue.

As you have mentioned three URLs are working out of four. I suggest filing a support case to investigate this issue further. The support team will be able to examine the situation and assist in resolving the issue.

If you don't have the ability to open a technical support ticket, please let me know and I can help you further with this.
Jim Nickell 0 Reputation points

2024-10-22T17:14:35.7166667+00:00

I have resolved this issue. I created outbound "Allow" firewall policies on the Azure hosted Cisco Meraki vMX appliance. I'm really not sure why this change needed to be made. This environment has been in production since 2021 and nothing changed. It suddenly broke about 2 weeks ago, right around Patch Tuesday.

Answer 1

Hi Jim Nickell,

I'm glad that you were able to resolve your issue and thank you for posting your solution so that others experiencing the same thing can easily reference this! Since the Microsoft Q&A community has a policy that "The question author cannot accept their own answer. They can only accept answers by others ", I'll repost your solution in case you'd like to "Accept " the answer.

Issue:

Azure Virtual Desktop fails UrlsAccessibleCheck.

Solution:

Resolved the issue by creating outbound 'Allow' firewall policies on the Azure-hosted Cisco Meraki vMX appliance.

If you have any other questions or are still running into more issues, please let me know. Thank you again for your time and patience throughout this issue.

Please remember to "Accept Answer" if any answer/reply helped, so that others in the community facing similar issues can easily find the solution. User's image

Thank you.

Share via

Azure Virtual Desktop fails UrlsAccessibleCheck

1 answer

Your answer