A Microsoft desktop and app virtualization service that runs on Azure. Previously known as Windows Virtual Desktop.
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.
- 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.
- 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, andAvailabilityZoneNotAvailable. - Parameter compatibility issues: the combination of VM SKU, disk, image, and virtual network isn’t compatible. Example errors include
ComputeSkuIncompatibleWithImageHyperVGeneration,ImageDiskTypeIncompatible, andVnetLocationIncompatible.
Get-AzComputeResourceSkuto check SKU restrictions for the region. - VM availability issues: the combination of VM SKU, region, availability zone, and subscription isn’t available. Example errors include
- 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.
- 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.
- If the host pool was created but the session host configuration is missing or failed
- If
Get-AzWvdSessionHostConfigurationreturns SessionHostConfiguration does not exist, create it withNew-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.
- If
- 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: