Error in Proviusion for Azure Virtual desktop

Use the error message as a starting point, then drill into the failed deployment operations to find the specific cause and fix it.

1. Check the failed deployment operations
   The message explicitly says “Please list deployment operations for details.” Follow that guidance to see the exact error:
   • In the Azure portal, go to Resource groups → select ATNIS-AVD-RG → Deployments.
   • Open the failed deployment and review the Operation details and error text for each failed resource (host pool, session host VM, NIC, extensions, etc.).
   • Alternatively, use Azure CLI as documented in View deployment history with Azure Resource Manager:

          az deployment operation group list \
            --resource-group ATNIS-AVD-RG \
            --name <DeploymentName>
     

     To see only failed operations:

          az deployment operation group list \
            --resource-group ATNIS-AVD-RG \
            --name <DeploymentName> \
            --query "[?properties.provisioningState=='Failed']"
     

     To get the detailed status message for failures:

          az deployment operation group list \
            --resource-group ATNIS-AVD-RG \
            --name <DeploymentName> \
            --query "[?properties.provisioningState=='Failed'].properties.statusMessage.error"
     

2. Interpret common AVD deployment errors
   Once the failed operation details are visible, compare the error text with known Azure Virtual Desktop deployment issues:
   • Subscription or region limitations (for example, MSDN, Free, Education subscriptions, or unsupported region):
     If the error indicates the subscription type cannot access required features in the chosen region, change either:
     • The subscription type (to a supported one), or
     • The deployment region to one that supports AVD features.
   • NIC or name conflicts (InvalidResourceReference):
     If the error is DeploymentFailed - InvalidResourceReference and mentions NIC or resource name conflicts, use a different host prefix so the NIC name is unique in the virtual network.
   • Download/extension errors (Error downloading / VMExtensionProvisioningError / DSC errors):
     If the error mentions Error downloading, VMExtensionProvisioningError, or PowerShell DSC configuration failures:
     • Check for static routes, firewalls, or NSGs blocking outbound access to required URLs or the template’s ZIP file.
     • Remove or adjust the blocking rule, then redeploy.
     • Ensure the admin username/password used for the VM have local admin rights so the DSC/agent extensions can run.
3. Validate AVD prerequisites before redeploying
   Before retrying the deployment, confirm the environment meets Azure Virtual Desktop prerequisites:
   • Review Prerequisites for Azure Virtual Desktop for supported OS, vNet, identity, and region requirements.
   • Ensure the target subnet can reach the required FQDNs and endpoints for Azure Virtual Desktop. Network blocks are a common cause of registration and extension failures.
   • After the first session host is joined, run the Azure Virtual Desktop Agent URL Tool on that host to confirm connectivity.
4. If adding session hosts via session host configuration
   If using the newer session host configuration model, note that ARM deployment can succeed even if domain join fails, leaving unhealthy hosts. For domain join or health errors, review the session host details JSON in the portal and follow the guidance in the session host troubleshooting article.
5. Redeploy after fixing the root cause
   After addressing the specific error (quota/region, name conflict, network block, credentials, etc.), rerun the AVD deployment (via portal, ARM template, or PowerShell) and monitor the Deployments blade again for any remaining failures.

References:

• View deployment history with Azure Resource Manager
• Troubleshoot host pool creation
• Deploy Azure Virtual Desktop (host-pool-standard)
• Troubleshoot session host configuration and session host update in Azure Virtual Desktop
• Troubleshoot deployment issues when creating a new Windows VM in Azure