Microsoft Intune · Rate Limits

Microsoft Intune Rate Limits

Microsoft Intune is administered via the Microsoft Graph deviceManagement endpoints; throttling is governed by the underlying Microsoft Graph Identity & Access (directory) service throttling and the global Graph ceiling, plus device-check-in fan-out limits enforced by the Intune service. Microsoft does not publish per-second numbers for the deviceManagement / device-check-in endpoints; clients should treat fair-use behaviour and honour Retry-After.

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

It captures 5 rate-limit definitions, measuring requests_per_10_seconds, resource_units_per_10_seconds, requests_per_2m30s, and varies.

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

Tagged areas include Rate Limiting, Endpoint Management, Intune, Microsoft Graph, and Microsoft.

5 Limits Throttle: 429
Rate LimitingEndpoint ManagementIntuneMicrosoft GraphMicrosoft

Limits

Microsoft Graph global ceiling application
requests_per_10_seconds · second
130000
Identity & Access (read) per app/tenant app/tenant
resource_units_per_10_seconds
see Graph throttling-limits — varies by tenant size (3500 / 5000 / 8000 RU)
Identity & Access (write) per app/tenant app/tenant
requests_per_2m30s · second
3000
Intune deviceManagement endpoints app/tenant
varies
see Microsoft Graph throttling guidance — no Intune-specific numbers published
Device check-in fan-out tenant
varies
bounded by service capacity; high-volume bulk actions are queued

Policies

Backoff Strategy
Honour Retry-After on 429 / 503; the Microsoft Graph SDK handlers do this automatically.
Use $batch for bulk
Combine related read calls in $batch envelopes; each request is throttled individually but network overhead is reduced.
Use change notifications
Subscribe to Graph change notifications for device / compliance changes rather than polling.
Plan write operations
Bulk policy assignments and device actions are queued and may take time to converge across the tenant; do not retry-storm.
Microsoft Graph Data Connect for analytics
For tenant-wide reporting, use Data Connect to bypass REST throttling.

Sources