Microsoft Azure Health Data Services Rate Limits
Azure Health Data Services enforces rate limits per service. FHIR service throughput scales with provisioned RU/s (automatically managed by Azure — not manually configurable). DICOM service handles thousands of image ingestions per second but doesn't publish explicit per-second request caps. The de-identification service throttles at 1 MB per 5 seconds or 100 requests per 5 seconds. When limits are exceeded, the service returns HTTP 429 (Too Many Requests). Higher throughput is available by submitting a support request.
Microsoft Azure Health Data Services Rate Limits is the machine-readable rate-limit profile for Microsoft Azure Health Data Services on the APIs.io network, conforming to the API Commons Rate Limits specification.
It captures 9 rate-limit definitions, measuring payload_size, mb_per_window, requests_per_window, documents, and mb.
The profile also includes 3 backoff/retry policies defined and response codes documented for rateLimitExceeded and serviceUnavailable.
Tagged areas include Rate Limiting, FHIR, DICOM, De-identification, and Healthcare.
Limits
Policies
Sources
- https://learn.microsoft.com/en-us/azure/healthcare-apis/deidentification/overview#input-requirements-and-service-limits
- https://learn.microsoft.com/en-us/azure/healthcare-apis/fhir/overview
- https://learn.microsoft.com/en-us/azure/healthcare-apis/dicom/overview
Work with this as data
Every rate limit here is available over the APIs.io API and to AI agents over MCP.