Forum Discussion
Add or Update Session Host failed
I spoke with the the product team today and my specific issue was related to the our key vault configuration.
TLDR (Key Vault requires public network access to be enabled for the credentials to be retrieved)
The process that runs the domain join is now a part of the RD host session host agent. Previously it could access your Key Vault using "Azure Resource Manager for template deployment". There is an existing limitation with this new agent approach which requires public network be enabled for your key vault to retrieve the domain join secrets.
I'm in the exact same boat as Axel, I have a new host pool using Session Host Configuration preview and no matter what I try (combinations of UPN, Domain etc.) it fails to join.
I've confirmed the AVD principal can read from the key vault as I'm able to use the local admin credentials after the VM is deployed. I can also manually join the domain from the VM without any issues.
I can't find anything that stands out in the PowerShell DSC logs and my NetSetup logs similarly only reference adding the machine to the original Workgroup and nothing about the AD domain it should be trying to join.