Azure Storage Account · Rate Limits

Azure Storage Account Rate Limits

Azure Storage standard accounts target high request rates and bandwidth ceilings per account per region, with higher defaults in primary regions. Limits cover request rate (requests/sec), ingress (Gbps), egress (Gbps), and capacity. When the partition limit is exceeded, the service returns HTTP 503 (Server Busy) or 500 (Operation Timeout); clients should apply exponential backoff. Higher capacity and bandwidth limits can be requested through Azure Support.

Azure Storage Account Rate Limits is the machine-readable rate-limit profile for Azure Storage Account on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 13 rate-limit definitions, measuring accounts, PiB, requests_per_second, Gbps, and rules.

The profile also includes 5 backoff/retry policies defined and response codes documented for serverBusy, operationTimeout, and throttled.

Tagged areas include Storage, Blob, and Rate Limiting.

13 Limits Throttle: 429
StorageBlobRate Limiting

Limits

Storage accounts per subscription per region subscription/region
accounts
250
Default; raise to 500 by request.
Storage accounts with Azure DNS zone endpoints (preview) subscription/region
accounts
5000
Default account capacity account
PiB
5
Request rate per account (primary regions) account/region
requests_per_second · second
40000
Includes US, EU, AP primary regions; raise via support.
Request rate per account (other regions) account/region
requests_per_second · second
20000
Ingress per account (primary regions) account/region
Gbps
60
Default; raise via support.
Ingress per account (other regions) account/region
Gbps
25
Egress per account (primary regions) account/region
Gbps
200
Egress per account (other regions) account/region
Gbps
50
IP rules per account account
rules
400
VNet rules per account account
rules
400
Resource instance rules per account account
rules
200
Private endpoints per account account
endpoints
200

Policies

Backoff on 503/500
Server Busy (503) or Operation Timeout (500) indicate partition saturation. Apply exponential backoff with jitter to ease the partition.
Partition design
Distribute traffic across blob/queue/table partitions; avoid hot prefixes.
Quota raise via support
Higher capacity, ingress/egress, and request-rate limits can be requested through Azure Support.
Per-service variation
Premium accounts and ADLS Gen2 have different limits; consult per-service scalability target pages.
Smooth bursts
Avoid sudden traffic spikes; ramp up gradually for the partition manager to redistribute load.

Sources