Azure Key Vault Rate Limits
Azure Key Vault enforces per-vault, per-region throttling measured in transactions per 10 seconds. Throttling thresholds are weighted by key type and operation - HSM keys cost more than software keys; larger RSA keys cost more than smaller ones. The subscription-wide ceiling is 5x the per-vault limit. Managed HSM has its own per-partition object limits. Throttled requests return HTTP 429.
Azure Key Vault Rate Limits is the machine-readable rate-limit profile for Azure Key Vault on the APIs.io network, in the API Commons Rate Limits shape.
It captures 13 rate-limit definitions, measuring requests_per_10s, instances, keys, and versions.
Limit state is signalled in the retryAfter and requestId response headers, and an exhausted limit returns HTTP 429.
This profile was written by API Evangelist and has not been verified against a page the provider published; treat every limit as unconfirmed until a dated transcription replaces it.
The profile also includes 4 backoff/retry policies defined and response codes documented for throttled.
Tagged areas include Security, Secrets Management, Key Management, and Rate Limiting.
retryAfterrequestId
generated, dated 2026-05-05.
Limits
Policies
Sources
- https://learn.microsoft.com/en-us/azure/key-vault/general/service-limits
- https://learn.microsoft.com/en-us/azure/key-vault/general/overview-throttling
Work with this as data
Every rate limit here is available over the APIs.io API and to AI agents over MCP.