Zonal Allocation Failure

Question

We've detected the deployment for virtual machine vm-app01-dev initiated at 8/14/2026 11:19:03 AM (UTC) failed because the availability zone uksouth-2 doesn't have the capacity to support its allocation.

the resource operation completed with terminal provisioning state 'failed'..

Availability zones are distinct groups of datacenters within a specific region. Each Azure datacenter holds servers that are organized into clusters. Typically, when a request for allocation is made, it is tried across multiple clusters within the datacenter associated with that availability zone.

However, there may be certain restrictions from the allocation request that limit the Azure platform to only a few clusters. As a result, the fluctuating availability of free blades or space within a blade in the cluster might not meet the requirements for service allocation. If these requirements are not fulfilled, the request is returned as an allocation failure.

In many cases, retrying after some time can help mitigate the problem, unless the required size is not available on the specified availability zone. In such cases, choosing a different availability zone is the best course of action.

Refer to the article below for further general troubleshooting of Allocation Failures.

Answer 1

Welcome to Microsoft Q&A!

Hello @Raju Indukuri ,I hope you are doing well,

As the error message correctly explains, this is a platform-side capacity issue, not a misconfiguration on your end. The specific hardware clusters inside UK South (Zone 2) currently do not have the available blades or space to support the exact VM size (SKU) you are requesting. Cloud capacity is highly fluid, and these localized constraints happen during spikes in regional demand.

To get your VM deployed as quickly as possible, I recommend trying the following steps in this order:

Deploy to a different Zone (Fastest Solution): If your architecture does not strictly require Zone 2, simply change your deployment parameters to target Zone 1 or Zone 3 in uksouth. Capacity is isolated by zone, so the others likely have plenty of space.

Change the VM Size (SKU): If you absolutely must deploy into Zone 2, try selecting a different VM family or a newer generation. For example, if you requested a Standard_D2s_v3, try switching to a Standard_D2s_v4 or Standard_D2as_v4. Different SKUs run on different physical clusters, which may have free capacity.

1. Retry Later: Because capacity fluctuates constantly as other customers deallocate resources, simply waiting a few hours and retrying the deployment often succeeds.

Please let me know if switching the zone or SKU gets you unblocked today!

If this answer helped you, please consider marking it as Accepted. This helps others in the community find similar solutions.