Azure virtual desktop setup issue

Kiran N 0 Reputation points
2026-10-14T22:48:21.3733333+00:00

I am trying to setup azure virtual desktop and running into an issue with VM not getting attached to hostpool / session hosts. I tried to create session hosts inside hostpool configuration and add VMs. And selected D2S_V4 as machine image for windows 11 version . At the end of the setup it says deployment failed but VM is created and up and running except it’s not attached to the hostpool as connect host count is zero under hostpool

Any ideas how to address this problem please

Azure Virtual Desktop
Azure Virtual Desktop

A Microsoft desktop and app virtualization service that runs on Azure. Previously known as Windows Virtual Desktop.

0 comments

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Jose Benjamin Solis Nolasco 12,856 Reputation points Volunteer Moderator
    2026-10-14T22:58:03.3033333+00:00

    Welcome to Microsoft Q&A

    Hello @Kiran N , I hope you are doing well today,

    If the VM was created successfully but does not appear as a Session Host and the Host Pool shows 0 connected hosts, the most common causes are:

    • The AVD agent registration failed.
    • The VM failed to join Microsoft Entra ID or Active Directory.
    • The registration token expired during deployment.
    • A VM extension (AVD agent, domain join, DSC extension) failed even though the VM itself was created.

    I recommend checking the following first:

    1. Go to Resource Group → Deployments and review the failed deployment details. The exact error is often recorded there.
    2. Open the VM and check Extensions + Applications for any extensions in a Failed state.
    3. Verify the VM can reach required Azure Virtual Desktop service endpoints.
    4. Check whether the VM successfully joined the intended domain (Microsoft Entra ID DS, Active Directory, or Entra Join).
    5. In the Host Pool, generate a new registration token and try registering the session host again.

    Could you share the exact deployment error message from the failed deployment and whether you're using:

    • Microsoft Entra joined session hosts, or
    • Active Directory domain-joined session hosts?

    That will help identify whether this is an AVD agent registration issue or a domain join issue.

    References

    If my answer helped you resolve your issue, please consider marking it as the correct answer. This helps others in the community find similar solutions.

    Was this answer helpful?

    0 comments

  2. AI answer

    2026-10-14T22:48:44.2033333+00:00

    For a VM that gets created successfully but never shows up in the Azure Virtual Desktop host pool, the supported troubleshooting path depends on whether the host pool uses session host configuration or standard management.

    1. If the host pool uses session host configuration
      • Add session hosts through the Azure portal. This is the supported method for host pools that use session host configuration.
      • In this model, the domain join extension isn’t used. The Azure Virtual Desktop agent performs the domain join instead.
      • Because of that, the ARM deployment can report success for the VM creation even when domain join fails, which leaves the session host unhealthy and not attached to the host pool.
      • In the Azure portal, open the session host details and view the JSON for session host health to check domain join failure diagnostics.
    2. Check whether the session host configuration itself failed validation Common causes include:
      • VM availability issues: the combination of VM SKU, region, availability zone, and subscription isn’t available. Example errors include VmSkuNotAvailableInRegion, VmSkuNotAvailableInRegionDueToRestriction, and AvailabilityZoneNotAvailable.
      • Parameter compatibility issues: the combination of VM SKU, disk, image, and virtual network isn’t compatible. Example errors include ComputeSkuIncompatibleWithImageHyperVGeneration, ImageDiskTypeIncompatible, and VnetLocationIncompatible.
      For the D2s_v4 + Windows 11 scenario, verify that the selected VM SKU, image, disk type, virtual network location, region, and zone are a supported combination. Use Get-AzComputeResourceSku to check SKU restrictions for the region.
    3. Review deployment errors in Azure Resource Manager
      • In Azure, review the deployment operations first.
      • If no useful error appears there, review the Activity Log.
      • After identifying the exact error, fix that issue and then delete any resources created during the failed deployment and retry.
    4. If the failure is related to domain join A common cause is the virtual network DNS configuration.
      • In the Azure portal, go to Virtual networks.
      • Select the virtual network used by the session host VM.
      • Open DNS servers.
      • If it is set to Default, change it to Custom.
      • Make sure the custom DNS servers point to the domain controller or Active Directory DNS servers.
    5. If the host pool was created but the session host configuration is missing or failed
      • If Get-AzWvdSessionHostConfiguration returns SessionHostConfiguration does not exist, create it with New-AzWvdSessionHostConfiguration.
      • If the configuration failed during host pool creation, the documented options are to create the session host configuration with PowerShell using New-AzWvdSessionHostConfiguration, or delete and recreate the host pool.
    6. If the deployment failed during VM extension provisioning One documented cause is a transient Azure Virtual Desktop or connection issue. In that case:
      • Confirm the Azure Virtual Desktop environment is healthy by signing in with PowerShell.
      • Finish the VM registration manually using the PowerShell-based host pool creation flow.

    The most likely next checks for this scenario are:

    • confirm whether the host pool is session host configuration or standard,
    • inspect deployment operations for the exact failure,
    • check session host health JSON for domain join errors,
    • verify DNS settings on the virtual network,
    • validate that the D2s_v4 / Windows 11 / region / zone combination is supported.

    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

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