Share via

I need help in setting up Azure Virtual Desktop for a POC

Akheel Ahmed 0 Reputation points
2026-05-25T08:43:45.2466667+00:00

{

"code": "DeploymentFailed",

"target": "/subscriptions/9321fbef-579f-4593-9807-80bf0624bf15/resourceGroups/RG-SBTESTAVD01/providers/Microsoft.Resources/deployments/HostPool-d088b1b5-4cf6-48db-a104-ac2efe85305c-deployment",

"message": "At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/arm-deployment-operations for usage details.",

"details": [

{

  "code": "ResourceDeploymentFailure",

  "target": "/subscriptions/9321fbef-579f-4593-9807-80bf0624bf15/resourceGroups/RG-SBTESTAVD01/providers/Microsoft.Resources/deployments/vmCreation-linkedTemplate-d088b1b5-4cf6-48db-a104-ac2efe85305c",

  "message": "The resource write operation failed to complete successfully, because it reached terminal provisioning state 'Failed'."

}

]

}

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. Jilakara Hemalatha 14,115 Reputation points Microsoft External Staff Moderator
    2026-05-25T09:31:24.1333333+00:00

    Hello Akheel,

    Thank you for sharing the deployment error details.

    Based on the information provided, the Azure Virtual Desktop deployment appears to be failing during the session host VM provisioning stage within the linked template deployment (vmCreation-linkedTemplate). Currently, the error shown is a generic DeploymentFailed / ResourceDeploymentFailure message, which does not yet provide the exact root cause.

    To help identify the precise failure point, could you please review and share the detailed error message from the deployment operations?

    Azure Portal path: Resource Group → RG-SBTESTAVD01 → Deployments → HostPool-... deployment → Operations

    Please check the failed VM creation operation and share the complete inner error details displayed there.

    In the meantime, we recommend validating the following common areas that frequently cause Azure Virtual Desktop session host deployment failures:

    Quota and VM Size Availability

    • Verify that sufficient vCPU quota is available in the selected Azure region.
    • Confirm that the selected VM SKU/size (for example, Standard_D2s_v3) is supported and currently available in that region.

    VM Naming and Credential Requirements

    • Ensure the VM naming convention complies with Azure requirements (1–15 characters, supported characters only).
    • Avoid using restricted or reserved administrator usernames.

    Image Validation

    • If using a custom image/VHD, confirm that the image exists in the correct subscription and region and has been properly generalized.
    • If using a Marketplace or Azure Compute Gallery image, validate that the selected image version and OS configuration are correct.

    Domain Join and Network Connectivity

    • If the session hosts are configured for domain join, verify connectivity to the domain controllers and confirm that DNS resolution, LDAP, and Kerberos communication are functioning correctly.
    • Ensure the provided domain join credentials or Key Vault references are valid.

    Network Security and Endpoint Access

    • Review NSG, Firewall, and UDR configurations to ensure required Azure Virtual Desktop and Azure management endpoints are not being blocked.
    • Confirm outbound internet access is available if deployment scripts/extensions need to download content from Azure endpoints during provisioning.

    Reference: Prerequisites for Azure Virtual Desktop

    Deploy Azure Virtual Desktop

    Troubleshoot host pool creation

    Required FQDNs and endpoints for Azure Virtual Desktop

    Hope this helps! Please let me know if you have any queries in comments.

    Was this answer helpful?

  2. AI answer

    2026-05-25T08:44:00.2166667+00:00

    The error shows that the overall deployment failed because the linked template that creates the session host VMs (vmCreation-linkedTemplate-...) reached the terminal provisioning state Failed. To proceed, check the detailed error for that specific deployment and then apply the matching fix.

    1. In the Azure portal, go to Resource groups → RG-SBTESTAVD01 → Deployments.
    2. Open the failed deployment vmCreation-linkedTemplate-d088b1b5-4cf6-48db-a104-ac2efe85305c and review the Operation details for the exact error message on the VM or extension resource.
    3. Compare the detailed error with the known Azure Virtual Desktop ARM template issues and apply the corresponding resolution:
      • If the error mentions subscription type or region not supported (for example MSDN, Free, Education):
        • Use a subscription type or region that supports the required features for Azure Virtual Desktop.
      • If the error is VMExtensionProvisioningError:
        • This is typically a transient issue with the Azure Virtual Desktop environment or connection.
        • Confirm the environment is healthy by signing in using PowerShell and then complete VM registration manually as described in Create a host pool with PowerShell.
      • If the error says “The Admin Username specified isn't allowed” or references forbidden substrings:
        • Change the local admin username or password so that it does not contain admin, administrator, or root.
      • If the error is “VM has reported a failure when processing extension” or “PowerShell DSC Configuration 'FirstSessionHost' completed with errors”:
        • The PowerShell DSC extension could not get admin access on the VM.
        • Ensure the username and password used in the template have local administrative rights on the VM, then rerun the ARM template.
      • If the error is DeploymentFailed - InvalidResourceReference:
        • Check if the NIC name or other resource names generated by the template conflict with existing resources in the same virtual network or subscription.
        • Make the first two characters of the resource group name unique for the subscription and/or use a different host prefix so that NIC names and other resources are unique, then redeploy.
      • If the error is DeploymentFailed - Error downloading or mentions failure to download a ZIP or script:
        • Check for static routes, firewalls, or NSG rules blocking outbound access from the session host subnet.
        • Remove or adjust the blocking rule, or download the referenced ZIP to an allowed location and update the template if applicable, then redeploy.
    4. After applying the appropriate fix, rerun the Azure Virtual Desktop deployment (host pool + session hosts) from the Azure portal, CLI, or PowerShell as described in the deployment guidance.

    If the deployment continues to fail, capture the exact inner error message from the failed VM or extension resource in vmCreation-linkedTemplate-... and align it with the specific ARM template error patterns above.

    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.