Managed DevOps Pool: maximumConcurrency won't change (portal InvalidIdentityValues; PATCH logged "Succeeded" but not applied)
Ziad Antar
0
Reputation points
I'm trying to raise a Managed DevOps Pool from 2 to 4 maximum agents, and none of the supported ways applies the change.
Pool setup
- Region: UK South, Standard_D2ads_v5, Ubuntu 22.04, Stateful agents
- Networking: Microsoft-hosted, with 1 static IP address (no subnet)
- Standby: Automatic (MoreCostEffective)
- Identity: one user-assigned managed identity
- Azure DevOps org profile: one org, one project, parallelism 2
Goal: maximumConcurrency 2 → 4, and the org's parallelism 2 → 4.
Already checked
- Quota: DADSv5 family for Managed DevOps Pools in UK South is 12 vCPUs
- Azure DevOps: self-hosted parallel jobs raised to 4
- The managed identity exists, and its client and principal IDs match what the pool stores
What fails
- Portal (Pool → Settings → Scaling → Max agents 4 → Apply): fails with
InvalidIdentityValues. It does the same in a fresh InPrivate session. -
az mdp pool update: fails withCrossVersionApiValidationFailed, which asks for a subnetId. The extension seems to use api-version 2024-10-19. We don't want to add a subnet, because it would change the networking and the static IP. -
az restPATCH, api-version 2025-09-20:- With only
maximumConcurrency:ResourcePatchFailed/ Bad Request. - With the identity sent as
{},maximumConcurrency: 4andparallelism: 4: the Activity log shows the PATCH as Succeeded, but a GET a minute later, and again 10+ minutes later, still returns 2 and 2.
- With only
Questions
- Is this a known issue with pools that use Microsoft-hosted networking and a static IP?
- Is there a supported way to raise max agents that keeps the current networking and static IP unchanged?
Azure DevOps
Sign in to answer