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

tanishq 0 Reputation points
2026-08-03T07:04:00.44+00:00

We have an Application Gateway stuck in a Failed provisioning state, and every operation we attempt (start, tag update) fails with the same zonal allocation error, even though diagnostics show no configuration issues.

Resource details:

  • Region: UAE North
  • SKU: WAF_v2
  • Autoscale: min 2, max 10
  • Zones: 1, 2, 3 (zone-redundant)
  • Current provisioningState: Failed

What we've tried:

  • az network application-gateway start -> fails with AllocationFailureDueToOverconstrainedZonalAllocationRequest
  • az network application-gateway update (tag change only, no config change) -> same error
  • Portal "Support + troubleshooting" diagnostics (Timeout errors, Key Vault, Failed configuration) -> all report "no issues detected"
  • Confirmed via CLI that provisioningState is Failed at the resource level, not just on the frontend IP config

The error message suggests retrying in a few days or deploying without a zone specified, but since this gateway is already zone-redundant across all 3 zones and is stuck in Failed state rather than being a fresh deployment, we're unsure whether this needs backend intervention or if there's a supported recovery path we're missing.

Our support plan is Developer tier, so we're posting here rather than filing a technical ticket. Any guidance on recovering a gateway from this state, or confirmation of a zone capacity issue in UAE North, would be appreciated.

Azure Application Gateway
Azure Application Gateway

An Azure service that provides a platform-managed, scalable, and highly available application delivery controller as a service.

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Ganesh Patapati 12,170 Reputation points Microsoft External Staff Moderator
    2026-08-03T22:19:50.7533333+00:00

    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.

    Was this answer helpful?

    0 comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.