Forum Discussion
ResourceDeploymentFailure when creating a HostPool for Azure Virtual Desktop
When I try to create a Azure Virtual Desktop I get the following error:
{
"code": "DeploymentFailed",
"target": "/subscriptions/a-b-c-d-e/resourceGroups/rg-avd-wcus/providers/Microsoft.Resources/deployments/HostPool-x-y-z-æ-ø-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/a-b-c-d-e/resourceGroups/rg-avd-wcus/providers/Microsoft.DesktopVirtualization/hostpools/hp-avd-wcus/sessionHostConfigurations/default",
"message": "The resource write operation failed to complete successfully, because it reached terminal provisioning state 'Failed'."
}
]
}
Anyone know what it is or how I can fix it?
Subscription
Subscription Microsoft.DesktopVirtualization = Registered
Resource group
Resource group Region = (US) West Central US
Virtual network
Region: (US) West Central US
Key vault
Region: (US) West Central US
Pricing tier: Standard
Access control (IAM): Gave myself Key Vault Administrator
Key Vault → Objects → Secrets → Generate/Import
Name: avd-admin-username
Name: avd-admin-password
AVD Host Pool
Location: (US) West Central US
Validation environment: No
Preferred app group type: Dektop
Host pool type: Pooled
Create Session Host Configuration: Yes
Load balancing algorithm: Depth-first
Max session limit: 5
Session hosts
Number of session hosts: 1
Name prefix: vm-avdwcus
Location: (US) West Central US
Availability options: No infrastructure required
Secure type: Trusted launch virtual machine
Image: Windows 11 Enterprise mulit-session, Version 25H2
Size: Standard D2as v5
Number of VMs: 1
OS disk type; Standard HDD
OS disk size: Default size (128 GB)
Virtual network: vn-avd-network-wcus
Public inbound port: No
Domain to join: Microsoft Entra ID
Entroll VM with Intune: Yes
3 Replies
The deployment failed the session host VM provisioning may have reached a terminal “Failed” state. This is a generic ResourceDeploymentFailure error and most often caused by VM SKU availability, quota limits, image/disk incompatibility, or domain join/Intune enrollment issues.
https://learn.microsoft.com/en-us/troubleshoot/azure/virtual-desktop/troubleshoot-vm-configuration
to me it looks like machine is not able to reach domain, can you let me know at what stage this gets failed during the compute resource creation or after the compute is created
The host pool exists, but its managed session-host configuration reaches a failed terminal state. The displayed DeploymentFailed message is therefore a wrapper, not the underlying cause. Because you selected Create Session Host Configuration, Microsoft documents that diagnostics for this workflow are written to Azure Monitor and Log Analytics rather than the normal ARM deployment history. Enable host-pool diagnostics, retry once, and inspect the failure at that timestamp. Then verify the deployment identity has the required resource-group roles and can retrieve both Key Vault secrets; granting Key Vault Administrator only to your own account does not prove that. Also check regional vCPU quota, D2as v5 availability, subnet address capacity, and whether the selected 25H2 image supports Trusted Launch. Correct the first specific failure you find, then retry the configuration. If no detailed diagnostic record appears, open an Azure support case with the correlation ID.
