The VM size (or combination of VM sizes) required by this deployment cannot be provisioned due to deployment request constraints


 

While trying to deploy a D-Series IaaS VM (could happen for A 8/A9 IaaS VMs as well) from the Azure Portal or PowerShell you may get the following error. It could also happen if you try to deploy or re-deploy a PaaS Cloud Service after increasing the VM size in the configuration to a Virtual Network(VNET) .

Current Portal

image

New Portal

image

Error:

The VM size (or combination of VM sizes) required by this deployment cannot be provisioned due to deployment request constraints. If possible, try relaxing constraints such as virtual network bindings, deploying to a hosted service with no other deployment in it and to a different affinity group or with no affinity group, or try deploying to a different region. The long running operation tracking ID was: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx. 

Please check if you are trying to deploy this IaaS VM to a Cloud Service that is part of an existing Virtual Network. The cause of the failure is that existing VNET (Virtual Networks) are attached to an Affinity Group. Affinity Group is bound to a set of servers.

Deployment Configuration for Local Virtual Network

<VirtualNetworkSitename=“VNetLocal” AffinityGroup= “VNetLocalAffinity”>

So you try the following options

a) Deploy this IaaS VM outside the VNET.

b) If it’s required to have this VM in the same VNET e.g. in a situation where it need to be part of the existing solution, then you need to convert the VNET from a Local Virtual Network to a Regional Virtual Network.

Details - http://azure.microsoft.com/blog/2014/05/14/regional-virtual-networks/

Regards,
Angshuman Nayak
Cloud Integration Engineer


Comments (1)

  1. Awesome Solution. Thanks for sharing.

Skip to main content