AllocationFailed, AnotherOperationInProgress and DeploymentFailed
AllocationFailed is capacity, AnotherOperationInProgress is concurrency, and DeploymentFailed is a wrapper. Open the inner error to find the real cause.
What you see
AllocationFailedAnotherOperationInProgressDeploymentActiveAndUneditableDeploymentFailed
What it means
Per Microsoft's error table: AllocationFailed means the cluster or region does not have resources available, or cannot support the requested VM size. AnotherOperationInProgress and DeploymentActiveAndUneditable mean a concurrent operation or deployment is still running on the resource group.
DeploymentFailed is a general error that does not give the details you need. Look in the error details for the inner error code, which is the real failure.
How to confirm the cause
- 1Read the inner error of a failed deployment
az deployment operation group list --resource-group RESOURCE_GROUP --name DEPLOYMENT_NAME --query "[?properties.provisioningState=='Failed'].properties.statusMessage"
This lists the failed operations and their status messages. The innermost message names the real code.
- 2Check for deployments still running
az deployment group list --resource-group RESOURCE_GROUP --query "[?properties.provisioningState=='Running'].name"
Causes and fixes
Capacity: AllocationFailed
- HOW TO TELL
- The inner error is
AllocationFailed. - ROOT CAUSE
- The region or cluster cannot supply the requested size right now.
- FIX
- Retry later, or request a different VM size, region or zone.
A concurrent operation holds the resource
- HOW TO TELL
AnotherOperationInProgressorDeploymentActiveAndUneditable.- ROOT CAUSE
- Another operation or another deployment into the same resource group is still running.
- FIX
- Wait for it to complete, and serialize pipelines that deploy into the same resource group.
A wrapper error hiding a template or permission problem
- HOW TO TELL
DeploymentFailedwith an inner code such asInvalidTemplate,AuthorizationFailedorInvalidParameter.- ROOT CAUSE
DeploymentFailedonly reports that something failed.- FIX
- Follow the inner code. For
InvalidTemplate, check syntax and validate before deploying. ForAuthorizationFailed, see the Azure authorization runbook.
How to stop it coming back
- Run
az deployment group validate(or what-if) before deploying. - Do not run two pipelines against one resource group at once.
- Retry capacity errors with backoff, and try a second size.
Keep going
Sources
Microsoft Learn (learn.microsoft.com), read 18 Nov 2026 from the official docs source. The az commands are standard Azure CLI and were not on that page.