Azure Blob Storage · Rate Limits

Microsoft Azure Blob Storage Rate Limits

Azure Storage publishes scalability targets per storage account and per blob. Limits are not plan-tier scoped; they are account-type scoped (standard general-purpose v2, premium block blob). When targets are exceeded, the service returns 503 (Server Busy) or 500 (Operation Timeout). Higher targets are available by support request.

Microsoft Azure Blob Storage Rate Limits is the machine-readable rate-limit profile for Azure Blob Storage on the APIs.io network, in the API Commons Rate Limits shape.

It captures 6 rate-limit definitions, measuring bandwidth and requests_per_second.

Limit state is signalled in the requestId and clientRequestId response headers.

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 serverBusy and operationTimeout.

Tagged areas include Rate Limiting, Storage, and Microsoft Azure.

6 Limits requestIdclientRequestId
Method: generated, dated 2026-05-05.
Written by API Evangelist on 2026-05-05 and not verified against a page the provider published. Treat every limit as unconfirmed until a dated transcription replaces it.
View Source
Rate LimitingStorageMicrosoft Azure

Limits

Standard storage account ingress (US/EU) account
bandwidth · second
60 Gbps
Standard storage account egress (US/EU) account
bandwidth · second
120 Gbps
Standard storage account max request rate account
requests_per_second · second
20000
Default scalability target across all blob/queue/table/file operations.
Single blob max throughput blob
requests_per_second · second
500
A single blob is targeted at ~500 requests/sec regardless of tier.
Premium block blob ingress account
bandwidth
see Azure docs (premium block blob)
Premium block blob egress account
bandwidth
see Azure docs (premium block blob)

Policies

Backoff on 503/500
When Azure Storage returns 503 (Server Busy) or 500 (Operation Timeout), back off exponentially with jitter and retry.
Partition by blob name
Distribute high-rate writes across partitions by varying the blob-name prefix to avoid single-partition hot-spotting (~500 RPS per blob/partition).
Increase via support
Workloads requiring hundreds of thousands of RPS or petabytes can request higher account targets via Azure support.
Use multiple accounts
Shard workloads across multiple storage accounts when account-level limits become the bottleneck.

Sources

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-blob-storage-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.