I am getting a error creating a Virtual Machine in Azure Virtual Device.

Question

I am getting a error creating a Virtual Machine in Azure Virtual Device.

Doug Burdett 0

Error message is {"error":{"code":"InvalidTemplateDeployment","details":[{"code":"QuotaExceeded","message":"Operation could not be completed as it results in exceeding approved Total Regional Cores quota.

I have tried South Central US, East US 2, and Central US, as well as various VM sizes.

If I create the AVD in Quickstart, it works randomly, but it sets up in a different resource group than the VM server I have already created. I initially used Quickstart, deleted it, tried it manually and failed, tried it with Quickstart and it failed, deleted what it did create, and tried Quickstart again, which worked but is not in the same RG & virtual network as the server and storage already set up.

I am testing functionality during the 30-day trial.

Doug Burdett 0 Reputation points

2026-07-24T18:23:10.59+00:00

I deleted every resource in the subscription and started over. I created the resource group, virtual network with subnets, workspace, and host pool. Adding the CPU size fails regardless of the size I use. When I check the quote for DSv4 family it shows a quota of 0 of 10.

When I select Windows 11 Enterprise multihost with Apps, 24H2 or 25H2, it passes validation and then fails immediately during deployment. If I select Windows 10 Enterprise from the default list, it passes validation and fails after a long deployment with the following error (I used "xxxxx" to replace the subscription and resource group name).

The resource write operation failed to complete successfully, because it reached terminal provisioning state 'Failed'. (Code: ResourceDeploymentFailure, Target: /subscriptions/xxxxxxxxxx/resourceGroups/xxxxxxxxx/providers/Microsoft.Resources/deployments/vmCreation-linkedTemplate-99f5773e-10f5-4bb0-8a18-edbd2a3de065)

I tried it a second time with the same result.

1 answer

Your answer

Doug Burdett 0 Reputation points

2026-07-24T18:23:10.59+00:00

I deleted every resource in the subscription and started over. I created the resource group, virtual network with subnets, workspace, and host pool. Adding the CPU size fails regardless of the size I use. When I check the quote for DSv4 family it shows a quota of 0 of 10.

When I select Windows 11 Enterprise multihost with Apps, 24H2 or 25H2, it passes validation and then fails immediately during deployment. If I select Windows 10 Enterprise from the default list, it passes validation and fails after a long deployment with the following error (I used "xxxxx" to replace the subscription and resource group name).

The resource write operation failed to complete successfully, because it reached terminal provisioning state 'Failed'. (Code: ResourceDeploymentFailure, Target: /subscriptions/xxxxxxxxxx/resourceGroups/xxxxxxxxx/providers/Microsoft.Resources/deployments/vmCreation-linkedTemplate-99f5773e-10f5-4bb0-8a18-edbd2a3de065)

I tried it a second time with the same result.

Answer 1

The error indicates that the deployment would exceed your Azure subscription's approved regional vCPU (core) quota. Although it appears to be a quota issue, the fact that the deployment succeeds intermittently with the Azure Virtual Desktop (AVD) Quickstart suggests there may also be temporary regional capacity constraints or differences in the VM sizes and availability zones selected by the deployment.

First, verify your regional vCPU quotas by going to Azure Portal > Help + Support > Quotas (or Subscriptions > Usage + quotas) and confirm that the target region has enough available cores for the selected VM size. If necessary, request a quota increase or choose a VM size that requires fewer vCPUs.

If sufficient quota exists, the issue may be due to limited capacity for specific VM sizes in the selected region. Try a different VM size within the same family, disable availability zones if they are enabled, or retry the deployment later. The Quickstart template may automatically select a different VM size or deployment configuration, which explains why it occasionally succeeds.

Since you already have a virtual network, storage account, and server in an existing resource group, review the Quickstart deployment settings to ensure it targets your existing resource group and virtual network. If Quickstart created resources in a different resource group, it was likely using its default deployment configuration rather than your existing infrastructure. Deleting partially created resources before retrying is also recommended to avoid conflicts from failed deployments.

If the above response helps answer your question, remember to "Accept Answer" so that others in the community facing similar issues can easily find the solution. Your contribution is highly appreciated.

hth

Marcin