Application Gateway stuck in Failed provisioning state - all operations fail with AllocationFailureDueToOverconstrainedZonalAllocationRequest (UAE North)

Hi tanishq

AllocationFailureDueToOverconstrainedZonalAllocationRequest typically maps to the message:

“We have a temporary capacity issue with Application Gateways in one of the zones. Please retry after a few days or please try the operation in another region or without a zone specified.”

Even if the gateway is configured for zone redundancy, the platform can still hit capacity limits / allocation pressure that prevent the resource from being allocated during an operation (start/update), and operations continue to fail while the gateway is in Failed.

Please review the Application Gateway Activity Log and examine the most recent failed operation, including the operation name, error code, error message, and the statusMessage in the JSON details, to confirm whether the gateway entered the Failed provisioning state due to the same zonal allocation constraint and not a separate cascading error

The documented mitigation is to remove zone specificity (so allocation is not forced to the constrained zonal allocation path):

Example approach (conceptually): redeploy/create without zones specified (zones = “”).

From the guidance:

az network application-gateway create \
  --name <gateway-name> \
  --resource-group <resource-group> \
  --sku Standard_v2 \
  --gateway-ip-config subnet-1 \
  --zones ""

If you’re not able to recreate immediately, use this as a planning step: the doc’s specific guidance for this error is to try without a zone specified or in another region.

If allocation continues to fail in UAE North, the guidance is to deploy in a different region:

az network application-gateway create \
  --name <gateway-name> \
  --resource-group <resource-group> \
  --location <new-region> \
  --sku WAF_v2

Cause 1: Limited zone availability in a SKU

You're trying to deploy, upgrade, or scale up a cluster in a zone that has limited availability for the specific SKU.

Solution 1: You can try redeploying the workload using a different SKU, a different availability zone within the same region, or a different region altogether to avoid the current zonal capacity constraint.

Refer this article: Troubleshoot the ZonalAllocationFailed, AllocationFailed, or OverconstrainedAllocationRequest error code

Meantime,

1. What is the exact Activity Log error Error code / statusMessage for the most recent failed operation (timestamp + operation name)?
2. During the original create/update, were you using any zone-specific constraints on any dependencies (e.g., Public IP / subnet / any zonal settings)?
3. Are your gateway subnets delegated correctly for Application Gateways (Microsoft.Network/applicationGateways)?
4. Have you attempted a redeploy/create without specifying zones (even temporarily for testing), or a redeploy in another region?

Can you please update us if the action plan provided was helpful?

Should there be any follow-up questions or concerns, please let us know and we shall try to address them.