Deployment failed

Question

Deployment failed

Mohanraj K (Centific Technologies Inc) 20 Microsoft External Staff

Issue Summary: The resource write operation failed to complete successfully, because it reached terminal provisioning state Failed.

VM OS version and image type: Windows 11 multi-session and Windows 10 multi-session
Exact error message or code: ResourceDeploymentFailure or Conflict.

Ankit Yadav 4,555 Reputation points Microsoft External Staff Moderator

2025-10-21T20:02:52.99+00:00

Hello @Mohanraj K (Centific Technologies Inc)

Just checking in, if you got a chance to review my earlier response, let me know if you're still blocked with the issue.

Answer accepted by question author

0 additional answers

Your answer

Ankit Yadav 4,555 Reputation points Microsoft External Staff Moderator

2025-10-21T20:02:52.99+00:00

Hello @Mohanraj K (Centific Technologies Inc)

Just checking in, if you got a chance to review my earlier response, let me know if you're still blocked with the issue.

Answer 1

Ankit Yadav 4,555 Microsoft External Staff Moderator

Hello @Mohanraj K (Centific Technologies Inc)

The error message is not much descriptive, so it'll be difficult to understand the cause behind failure.

Could you please share the complete error message in the Private message to avoid sharing error PII information over here.
Could you please also share if this is a fresh deployment of the session host VMs or is it an update deployment over pre-existing session host VMs of an AVD?
Are you trying the deployment using some scripting tools (terraform or Bicep or ARM templates), if yes can you please share the template as well in the Private message ?

Ankit Yadav 4,555 Reputation points Microsoft External Staff Moderator

2025-10-18T00:36:39.1533333+00:00
Additionally, sharing some general guidance around conflict errors for the deployment failures, kindly review them as well.

Check Resource Limits: Quota Limits: Ensure you haven’t hit your subscription or region-specific resource limits. If you’re deploying multiple VMs, check whether the quota for CPU, memory, or disk is exhausted.
Check in Azure portal: Go to Subscription > Usage + Quotas to verify that your quota hasn’t been exceeded.

VM Size Availability: Ensure that the VM size you're trying to deploy is available in the region you're deploying to. Some VM sizes are region-specific, and if the required size isn't available, it might cause a conflict.

Conflicting Extensions or Custom Scripts If you have custom extensionsor startup scripts configured, try removing them and redeploying. Sometimes, custom extensions or startup scripts can interfere with the provisioning process.
Mohanraj K (Centific Technologies Inc) 20 Reputation points Microsoft External Staff

2025-10-22T16:55:05.97+00:00

Please find the deployment failed issue
{

"code": "DeploymentFailed",

"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": "VMExtensionProvisioningError",

"message": "VM has reported a user failure when processing extension 'joindomain'. Please correct the error and try again. (publisher 'Microsoft.Compute' and type 'JsonADDomainExtension'). Error code: '2'. Error message: 'Join failed for Domain 'xxxxx.onmicrosoft.com'. More information: 0x2558. Debug logs: -----------------------------------------------------------------\r\nNetpDoDomainJoin\r\nNetpDoDomainJoin: using current computer names\r\nNetpDoDomainJoin: NetpGetComputerNameEx(NetBios) returned 0x0\r\nNetpDoDomainJoin: NetpGetComputerNameEx(DnsHostName) returned 0x0\r\ nNetpValidateName: checking to see if ' xxxx.onmicrosoft.com' is valid as type 3 name\r\nNetpValidateName: ' .onmicrosoft.com' is not a valid NetBIOS domain name: 0x7b\r\nNetpValidateName: ' xxxxx.onmicrosoft.com' is not a valid Dns domain name: 0x2558\r\nNetpJoinDomainOnDs: Domain name is invalid, NetpValidateName returned: 0x2558\r\nNetpJoinDomainOnDs: Function exits with status of: 0x2558\r\nNetpJoinDomainOnDs: NetpResetIDNEncoding on '(null)': 0x0\r\nNetpDoDomainJoin: status: 0x2558\r\n
Ankit Yadav 4,555 Reputation points Microsoft External Staff Moderator

2025-10-22T17:16:02.88+00:00
Hello @Mohanraj K (Centific Technologies Inc)

Thank you for sharing the error details for the deployment failure.

The deployment has failed because of the VM extension you are trying to provision along with the VM Hostpool.

Details extracted from the error message:

Error Code: VMExtensionProvisioningError

Extension: joindomain (Microsoft.Compute/JsonADDomainExtension)

Error message:
NetpValidateName: ' xxxx.onmicrosoft.com' is not a valid Dns domain name: 0x2558 NetpJoinDomainOnDs: Domain name is invalid

To fix it, make sure to review below steps in order:

Kindly fix the domain name:
From the error message shared there seems be an extra space between ' and the first letter of the domain name starting.

Make sure the user account details you are passing in while the deployment are correct and has the right set of permissions to join the domain.

Make sure to review the communication is allowed to the domain controllers (ports like 88, 389, 445, etc.).

If the above steps also don't help out, you can try out manual domain join after creating the VM without the domain join extension, the steps would be as below:

Deploy the VM without the domain join extension.

RDP into the VM and try joining the domain manually to isolate whether the issue is with the extension or the domain configuration.

Share via

Deployment failed

0 additional answers

Your answer