Microsoft Azure Cost Management Rate Limits
Published Cost Management limits, replacing the 2026-05-04 scaffold that carried invented X-RateLimit-* headers and invented per-tier quotas. Cost Management does NOT use the generic X-RateLimit-* family. It throttles on two independent mechanisms: the Azure Resource Manager platform limits that apply to every ARM call, and — unique to this resource provider — a Query Processing Unit (QPU) budget that prices a call by how much data it asks for rather than by how many calls you make. The QPU quotas are per TENANT, not per subscription or per key, so every team in an organisation shares one budget.
Microsoft Azure Cost Management Rate Limits is the rate-limit profile for Azure Cost Management on the APIs.io network — every limit transcribed verbatim from the provider’s own documentation on 2026-09-17.
It captures 3 rate-limit definitions, including Query API — QPU per 10 seconds — 12 QPU per 10 seconds; Query API — QPU per minute — 60 QPU per 1 min; Query API — QPU per hour — 600 QPU per 1 hour.
Limit state is signalled in the qpuConsumed, qpuRemaining, qpuRetryAfter, and consumptionRetryAfter response headers, and an exhausted limit returns HTTP 429.
The profile also includes response codes documented for throttled, serviceUnavailable, and payloadTooLarge.
Tagged areas include Rate Limiting, Quotas, Throttling, and FinOps.
qpuConsumedqpuRemainingqpuRetryAfterconsumptionRetryAfter
Limits
Work with this as data
Every rate limit here is available over the APIs.io API and to AI agents over MCP.