Unable to create virtual machine and Microsoft 365 applications not showing in the Remote desktop

Rashmit Chawla 20 Reputation points
2025-05-28T05:35:35.9833333+00:00

Hi, I am executing the course : Configuring-and-Operating-Microsoft-Azure-Virtual-Desktop

Error 1 -- On Lab 1, I have created the host pool (Task 2: Deploy an Azure Virtual Desktop host pool) but when i open the session hosts under the host pool and continue with the Task 3: Create an Azure Virtual Desktop application group, I am not able to create Word, excel and powerpoint applications, there is an error that there is no available virtual machines under this host pool. When i check the Virtual machines on the "Virtual Machine" page, it shows "Unavailable" under the Heathcheck column and the error is - Domainjoin and Domain trust error. Due to which i am unable to execute further tasks/labs.

Error 2 -- On Lab 1 (Task 2,Step 3), I have selected the desktop image as mentioned below:

Image Windows 11 Enterprise multi-session, Version 23H2 + Microsoft 365 Apps
Virtual machine size Standard DC2s_v3

And i have also tried with the lower version as Windows 10 Enterprise multi-session, Version 22H2 + Microsoft 365 Apps. But when i start the virtual machine, it only shows the SessionDesktop icon and does not show the Microsoft 365 applications (Word, Excel, PowerPoint) and Command prompt even when i have created those applications in the previous steps.

Error 3 -- On Lab 6, Task 6: Validate the private endpoint functionality, I am unable to execute the tasks of creating the virtual machine named as az140-111e-vm0 and connect it. I am stucked at the step no.24 till step no. 41 under Task 6 of Lab 6. The error is "Validation failed" in the Basics tab and the "Create" button on the virtual machine is disabled. Due to the non-creation of Virtual machine in this lab 6, i am unable to execute the Lab 7 (specifically Task 7 and 8) as both the labs are related to building the custom image and deploying session hosts by using a custom image.

Hope these details are sufficient. As there are many gaps in this Github labs, i want to know if there are any steps missing in the labs due to which i am unable to complete the lab execution. Also, something might have been deprecated and need to know the updated details in the lab. The main issue is the selection of image (Windows 10/11 version), creating the applications (Word, excel, powerpoint), creating the virtual machine, and the remote desktop application showing all the applications including SessionDesktop, Microsoft 365 applications (Microsoft Word, Microsoft Excel, Microsoft Powerpoint) and Command prompt.

Azure Virtual Desktop
Azure Virtual Desktop
A Microsoft desktop and app virtualization service that runs on Azure. Previously known as Windows Virtual Desktop.
1,827 questions
{count} votes

Accepted answer
  1. Mounika Reddy Anumandla 5,980 Reputation points Microsoft External Staff Moderator
    2025-05-28T07:21:42.0766667+00:00

    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. User's image

    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:

    1. 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.
    2. Review Security Group Rules:
      • Make sure any necessary inbound/outbound firewall rules are configured to allow traffic to the domain controller.
    3. 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.
    4. 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.

    1 person found this answer helpful.

0 additional answers

Sort by: Most helpful

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.