Azure Virtual Desktop - DomainJoinedCheck failed

Sebastian Kluge 30

After creating a host pool with a virtual machine (connected to Entra-ID), I consistently receive notifications that the DomainJoinedCheck and DomainTrustCheck have failed. I have already implemented all the tips from the community, and as far as I can see, all access permissions are in place.

Perhaps someone else has an additional suggestion on what the issue might be.

User's image

Glenn Horton 15 Reputation points

2024-01-05T17:49:01.6366667+00:00

I'm creating an AVD environment completely with Terraform. That includes resource group, vNet, Host Pool, DAG, VMs, NSGs etc. The VMs created with Terraform get the DomainJoinedCheck failure but if I add another host to the pool thought the portal then that host doesn't get the failure. Using the portal I've compared all the settings I can find between a host that fails and one that doesn't and am unable to find a difference other than expected things like name, MAC address, IP address etc.

Accepted answer

Boris Von Dahle 3,116 Reputation points

2023-12-30T18:51:13.2166667+00:00

Hello Sebastian,

The DomainJoinedCheck and DomainTrustCheck failures you encounter usually indicate issues with domain connectivity or configuration. It's crucial to ensure the virtual machine can communicate with the domain controller.

You should verify the network settings( NSG and Firewall ), that could prevent the accessibility of domain controllers from the VM.

Also confirm the VM is using a DNS server that can resolve domain names correctly.

Sometimes, specific group policies or organizational unit settings might hinder the domain join process.

If you found this answer useful, please consider marking it as 'Accepted.' This helps other users easily find and benefit from this information

Regards
Please sign in to rate this answer.
Glenn Horton 15 Reputation points

2024-01-16T11:53:28.0766667+00:00

While it seems likely that domain connectivity can cause the failures that seems to not be the only cause since my VMs get the same failures, but I can login to them with a domain account using the remote desktop client using a public IP, but not through the web UI. Presumably because they are shown as "Can't connect" in the host pool, presumably due to these failures. I guess maybe there's some type of "domain connectivity" problem that causes these failures but doesn't prohibit login RDP login. However, I've been unable to find any evidence of such.

Terry Morrison 0 Reputation points

2024-02-02T21:46:00.61+00:00

I have the same issue, my domain is managed through google/weebly/squarespace. I'm not sure who to reach out to for help on this, I am not an expert in DNS management.

Glenn Horton 15 Reputation points

2024-04-15T11:25:39.3466667+00:00

I don't understand how the "accepted answer" got accepted since answer wasn't helpful. The VM didn't exhibit any DNS problems and I could login, with RDP but not the web client, with a domain ID so there didn't appear to be a problem with the vm joining the domain.
Sign in to comment

1 additional answer

RAHMAN Sajidur 0 Reputation points

2024-01-09T09:37:27.6566667+00:00

Hello,

I am also encountering this issue after creating an AVD with a single virtual machine to which the connection is impossible.

What should I check in the NSG to fix it ?

Best regards
Please sign in to rate this answer.
Glenn Horton 15 Reputation points

2024-01-09T12:24:46.01+00:00

In my case if I put a public IP on the VM I can login to the VM with a domain account using the RDP client. I think that shows the domain connectivity isn't a problem. However, the VM isn't available to the AVD web client because of the DomainJoinedCheck and DomainTrustCheck failures.

Glenn Horton 15 Reputation points

2024-01-17T20:12:31.7666667+00:00

I learned a bit more today. When I add a VM with Terraform it looks like the registration done in Entra may not be correct. I say that because if I delete the VM created with Terraform and then create another VM with the portal, the name used for the VM created by the portal is the same as the VM created by Terraform. However, now the VM created through the portal will fail with the same failures as the one created by Terraform until I delete the registration from Entra so the registration will be recreated when the VM is created through the portal.

Kaur, Supreet 0 Reputation points

2024-04-15T04:00:46.5+00:00

@Glenn Horton : What was eventually done to fix the domainfailed error coming through Terraform?

Glenn Horton 15 Reputation points

2024-04-15T11:22:17.8866667+00:00

I never got it fixed. I had to add VMs by hand.
Sign in to comment