Microsoft Azure Cache For Redis · Rate Limits

Microsoft Azure Cache For Redis Rate Limits

Published throttling limits for the Azure Resource Manager control plane that serves management.azure.com — the host every operation in openapi/ is called on. Microsoft.Cache publishes no resource-provider-specific override, so the platform token-bucket limits below are the limits that apply to this API.

Microsoft Azure Cache For Redis Rate Limits is the machine-readable rate-limit profile for Microsoft Azure Cache For Redis on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 7 rate-limit definitions.

The profile also includes response codes documented for throttled, retryable_non_throttle, and note.

Tagged areas include Rate Limiting, Quotas, and Throttling.

7 Limits Throttle: 429
Rate LimitingQuotasThrottling

Limits

per subscription (per service principal, per region)
25
per subscription (per service principal, per region)
10
per subscription (per service principal, per region)
10
per tenant (per region)
25
per tenant (per region)
10
per tenant (per region)
10
global per subscription (all service principals)

Work with this as data

Every rate limit here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for rate limits

4 MCP tools reach this
  • find_rate_limitsBrowse and filter every rate limit in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This rate limit 
curl "https://apis.io/api/v1/rate-limits/microsoft-azure-cache-for-redis-rate-limits"
All rate limits 
curl "https://apis.io/api/v1/rate-limits?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.