Hi Rashmit Chawla,
The error means: Your VM couldn't find or join the domain during deployment. This breaks the registration of the session host to Azure Virtual Desktop.
The "Domainjoin and Domain trust error" indicates that your session hosts are not successfully joining a domain. This will prevent your applications from being created and can lead to virtual machines showing as "Unavailable." Here's what you can try:
- Verify Domain Join Configuration:
- Check if the virtual network the virtual machines are deployed in has proper connectivity to the domain controller.
- Ensure that the virtual machines have the correct DNS settings pointing to the domain controller's IP.
- Review Security Group Rules:
- Make sure any necessary inbound/outbound firewall rules are configured to allow traffic to the domain controller.
- Log into the VM: If possible, log into the VM directly and check the system event logs for any domain join errors.
https://learn.microsoft.com/en-us/entra/identity/domain-services/join-windows-vm#join-the-vm-to-the-managed-domain
https://learn.microsoft.com/en-us/azure/virtual-desktop/deploy-azure-virtual-desktop?pivots=host-pool-session-host-configuration&tabs=portal-session-host-configuration%2Cportal-standard%2Cportal. - If it still fails, remove the VM from the domain and re-join the domain: https://learn.microsoft.com/en-us/troubleshoot/azure/virtual-machines/windows/troubleshoot-broken-secure-channel#remove-the-vm-from-the-domain-and-re-join-the-domain
Even though you selected the image with M365 Apps included (e.g., Windows 11 Enterprise multi-session + Microsoft 365 Apps
), the apps like Word, Excel, and PowerPoint will not automatically show up as RemoteApps (application group icons) until certain conditions are met.
The VM must be domain-joined and healthy ✅ (You're currently facing domain join issues — Error 1 — which blocks further configuration.)
The apps must be properly installed and available in Program Files
or Program Files (x86)
— they usually are, but only fully configured after the first user login or first-run process.
Confirm Microsoft 365 Licensing: Users must have AVD-compatible licenses with Microsoft 365 Apps (E3/E5 or Business Premium).
You must manually add the apps (even for M365) in the RemoteApp Application Group, referencing the installed paths.
Publishing Microsoft 365 apps as RemoteApps:
In the Application Group, you must explicitly add the RemoteApp programs:
- winword.exe for Word
- excel.exe for Excel
- powerpnt.exe for PowerPoint
- cmd.exe for Command Prompt (optional)
After app creation, assign users to the Application Group and make sure the Application Group is linked to the host pool.
Virtual machine creation fails with “Validation failed” and disabled Create button:
Recheck all required parameters:
- Subscription, Resource Group, Region must match and be consistent.
- Validate the virtual network/subnet details: The VM subnet must allow private endpoint connections and have no IP conflicts.
- Check Private DNS Zone: Verify your DNS zone is linked to the VNet.
- Check Azure Quotas: Use the portal or CLI to confirm quota for the VM size you are selecting.
- Try creating a VM with simpler parameters first: Test basic VM creation in the same VNet before private endpoint-enabled VM.https://learn.microsoft.com/en-us/answers/questions/2183753/azure-virtual-desktop-hostpool-deployment-failed
Hope it helps!
Let me know if you have any further queries!
If the information is helpful, please click accept answer and "upvote" to let us know.