Connect to Azure Local AVD

Question

Connect to Azure Local AVD

Jaco 125

Hi, I have setup an AVD setup where I have an AVD-hostpool, an application group (made by Azure automation during hostpool deployment) and a workspace. I have correctly assigned my users to the AVD-setup but when I want to connect I get the following error:

User's image

Is there a way I can inspect and modify the AVD-gateway? I think it's weird because I am able to RDP to the VM's within the hostpool. Any thoughts on this? This has all been setup within Azure Local btw.

Greetings Jaco

Ankit Yadav 410 Reputation points Microsoft External Staff Moderator

2025-08-25T20:29:46.2233333+00:00
Hello Jaco,
Could you please answer our below questions to understand the issue better:

What type of certificate is currently bound to the Remote Desktop Gateway ? Is it from a Certificate Authority (for example, GoDaddy) or an internal/self-signed certificate?

Check it via opening
https://<your_gateway_FQDN>

In a browser and check if you get any certificate related error (like Invalid Certificate or a blank page)

Have you checked if the DNS is configured properly? Does nslookup for the FQDN resolve to expected IP address?

Have you reviewed the network configurations with your AVD to ensure it's allowing traffic on the required ports (like 443 for AVD)?
Jaco 125 Reputation points

2025-08-26T17:40:57.1533333+00:00

Hi thank you for your answer!

I'm not sure what my FQDN gateway is. By the time I posted this issue, I was trying to connect to it while not being able to resolve the domainname so maybe that was the issue?

I'm currently getting the following (new) error when connecting.

So the AVD-host pool VM's are all domain joined into my domain (jacoazurelocal.local) and I assigned my Azure AD user called "azurelocal" to this AVD-host pool and the workspace. Any thoughts?

I used the following guide to setup my AVD:

https://www.youtube.com/watch?v=ol2Nyfm4ziY
Ankit Yadav 410 Reputation points Microsoft External Staff Moderator

2025-08-28T19:16:30.56+00:00
Hello Jaco,

You should be able to find the gateway FQDN from Properties of your HostPool.

Thanks for the sharing the new error message with the error code and details however this seems to be from different source as well.

It seems the earlier shared error was from the RDP web-client and new error seems to be from Desktop client.

Can you please do below checks:

Can you re-check your web-client if it throws the same error as the Desktop client or both are different?

Review your firewall rules if traffic is allowed to port 443.

Check if the DNS is configured properly.

The Youtube reference guide video shared seems to be reference for setting up AVD but it's not related to Azure Local I believe. If you are looking for AVD on Azure Local on Youtube maybe this playlist might be helpful for you: https://www.youtube.com/playlist?list=PLxvjnnGdNX6PZm_2g3zk50LZHZ2z2SubS
Jaco 125 Reputation points

2025-08-28T21:05:01.09+00:00

Hi,

I can't find the FQDN gateway in the properties, this is all I see:

I checked both the webclient and desktopclient and they both give different errors (the same as I gave earlier). I did a Test-NetConnection to my VM's and suprisingly port 3389 is able to setup a TCP connection but port 443 is not. Could this be something?

I looked through the videos in the playlist you've sent and I think it could also have something to do with the assignment to the VM. I assigned a user from my Microsoft Entra ID to the hostpool while my VM's are in my on-prem AD.

Any thoughts?

Your answer

Ankit Yadav 410 Reputation points Microsoft External Staff Moderator

2025-08-25T20:29:46.2233333+00:00

Hello Jaco,
Could you please answer our below questions to understand the issue better:

What type of certificate is currently bound to the Remote Desktop Gateway ? Is it from a Certificate Authority (for example, GoDaddy) or an internal/self-signed certificate?

Check it via opening
https://<your_gateway_FQDN>

In a browser and check if you get any certificate related error (like Invalid Certificate or a blank page)

Have you checked if the DNS is configured properly? Does nslookup for the FQDN resolve to expected IP address?

Have you reviewed the network configurations with your AVD to ensure it's allowing traffic on the required ports (like 443 for AVD)?
Jaco 125 Reputation points

2025-08-26T17:40:57.1533333+00:00

Hi thank you for your answer!

I'm not sure what my FQDN gateway is. By the time I posted this issue, I was trying to connect to it while not being able to resolve the domainname so maybe that was the issue?

I'm currently getting the following (new) error when connecting.

So the AVD-host pool VM's are all domain joined into my domain (jacoazurelocal.local) and I assigned my Azure AD user called "azurelocal" to this AVD-host pool and the workspace. Any thoughts?

I used the following guide to setup my AVD:

https://www.youtube.com/watch?v=ol2Nyfm4ziY
Ankit Yadav 410 Reputation points Microsoft External Staff Moderator

2025-08-28T19:16:30.56+00:00

Hello Jaco,

You should be able to find the gateway FQDN from Properties of your HostPool.

Thanks for the sharing the new error message with the error code and details however this seems to be from different source as well.

It seems the earlier shared error was from the RDP web-client and new error seems to be from Desktop client.

Can you please do below checks:

Can you re-check your web-client if it throws the same error as the Desktop client or both are different?

Review your firewall rules if traffic is allowed to port 443.

Check if the DNS is configured properly.

The Youtube reference guide video shared seems to be reference for setting up AVD but it's not related to Azure Local I believe. If you are looking for AVD on Azure Local on Youtube maybe this playlist might be helpful for you: https://www.youtube.com/playlist?list=PLxvjnnGdNX6PZm_2g3zk50LZHZ2z2SubS
Jaco 125 Reputation points

2025-08-28T21:05:01.09+00:00

Hi,

I can't find the FQDN gateway in the properties, this is all I see:

I checked both the webclient and desktopclient and they both give different errors (the same as I gave earlier). I did a Test-NetConnection to my VM's and suprisingly port 3389 is able to setup a TCP connection but port 443 is not. Could this be something?

I looked through the videos in the playlist you've sent and I think it could also have something to do with the assignment to the VM. I assigned a user from my Microsoft Entra ID to the hostpool while my VM's are in my on-prem AD.

Any thoughts?

Share via

Connect to Azure Local AVD

Your answer