VM creation keeps failing while deploying AVD in host pool.

[vihanga]

Hello,

I am trying to deploy AVD, but it keeps failing when it comes to creating the VM.

The error message is:

"Deployment to resource group 'AVD-RG' failed.
Additional details from the underlying API that might be helpful: At least one resource deployment operation failed. Please list deployment operations for details. See https://aka.ms/arm-deployment-operations for usage details."

I am using a Free Subscription with $200 in credits and a global account to deploy the AVD. Has anyone faced this issue recently?

[#2]

Hi @vihanga 

Sorry for my question, but what reason/error is given in the deployment operations?

There could be several reasons for the problem.

For example:

• Quota Limits - With a free subscription, there are specific resource limits, including CPU cores and storage, which might be insufficient for creating VMs used by AVD.

• Region Availability - Certain VM sizes or types may not be available in the region you're deploying.

Best regards,
Matthias

[#3]

Hi @Matthias-Braun

I did the deployment many times. This time, i got the below

{
"status": "Failed",
"error": {
"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": "Conflict",
"message": "{\r\n \"status\": \"Failed\",\r\n \"error\": {\r\n \"code\": \"ResourceDeploymentFailure\",\r\n \"message\": \"The resource write operation failed to complete successfully, because it reached terminal provisioning state 'Failed'.\",\r\n \"details\": [\r\n {\r\n \"code\": \"VMExtensionProvisioningError\",\r\n \"message\": \"VM has reported a failure when processing extension 'Microsoft.PowerShell.DSC' (publisher 'Microsoft.Powershell' and type 'DSC'). Error message: 'The DSC Extension failed to execute: Error downloading https://wvdportalstorageblob.blob.core.windows.net/galleryartifacts/Configuration_1.0.02774.414.zip after 17 attempts: Unable to connect to the remote server.\\r\\nMore information about the failure can be found in the logs located under 'C:\\\\WindowsAzure\\\\Logs\\\\Plugins\\\\Microsoft.Powershell.DSC\\\\2.83.5' on the VM.'. More information on troubleshooting is available at https://aka.ms/VMExtensionDSCWindowsTroubleshoot. \"\r\n }\r\n ]\r\n }\r\n}"
}
]
}
}

[#4]

I'm getting this error as well. The issue seems to be related to the VM not having an internet connection when it first starts up for some reason so it can't download the configuration file. After connecting to the vm it created remotely I was able to restart it a few times then the internet access son it kicked in but it was too late as the deployment has already failed. It's not NSG or firewall related. Can someone please advise?

[#5]

@Mr_BiskitsTrue. When you create hosts inside host pool it has an outbound connectivity issue. So I tried creating a NAT gateway and then create hosts in the AVD host pool and it worked.

[#6]

Hi @Mr_Biskits,

If you're struggling to get internet access from a newly deployed Azure VM in a new subnet, check if the VM is connected to a subnet where “Enable private subnet (no default outbound access)” is enabled.

This feature is enabled by default when new subnets are created in a VNET and cannot be disabled once it was enabled during subnet creation.

More info about default outbound access: Default outbound access in Azure - Azure Virtual Network | Microsoft Learn

Hope this helps!

Matthias

[#7]

I,m having the same error while deploying an AVD. 

{"code":"VMExtensionProvisioningError","message":"VM has reported a failure when processing extension 'Microsoft.PowerShell.DSC' (publisher 'Microsoft.Powershell' and type 'DSC'). Error message: 'The DSC Extension failed to execute: Error downloading https://wvdportalstorageblob.blob.core.windows.net/galleryartifacts/Configuration_1.0.02774.414.zip after 17 attempts: Unable to connect to the remote server.\r\nMore information about the failure can be found in the logs located under 'C:\\WindowsAzure\\Logs\\Plugins\\Microsoft.Powershell.DSC\\2.83.5' on the VM.'. More information on troubleshooting is available at https://aka.ms/VMExtensionDSCWindowsTroubleshoot. "}

After attaching a public ip immediately after the VM creation the issue got fixed. It seems like the default outbound internet connection is not working for new VMs.

@vihanga