Microsoft Planner · Rate Limits

Microsoft Planner Rate Limits

Microsoft Planner is administered exclusively via the Microsoft Graph planner endpoints. Microsoft does not publish Planner-specific per-second / per-minute throttling numbers; Planner inherits the Microsoft Graph global ceiling (130,000 requests per 10 seconds per app) and the Identity & Access per-app-per-tenant ResourceUnit budget for user / group lookups. Returns 429 Too Many Requests with Retry-After.

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

It captures 4 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, serviceUnavailable, and preconditionFailed.

Tagged areas include Rate Limiting, Project Management, Tasks, Microsoft Graph, and Microsoft.

4 Limits Throttle: 429
Rate LimitingProject ManagementTasksMicrosoft 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 · second
3500–8000 RU per 10s based on tenant size
Identity & Access (write) per app/tenant app/tenant
requests_per_2m30s · second
3000
Planner endpoints app/tenant
varies
see Microsoft Graph throttling guidance — no Planner-specific numbers published

Policies

ETag concurrency
Planner uses optimistic concurrency. Every PATCH / DELETE must include the If-Match header with the resource ETag; mismatches return 412 Precondition Failed.
Backoff Strategy
Honour Retry-After on 429 / 503; the Microsoft Graph SDK handlers do this automatically.
Use change notifications
Subscribe to plan and task change notifications instead of polling.
Use $batch
Combine read calls in $batch envelopes; each is throttled individually.
Group-aware writes
Each plan is owned by a Microsoft 365 Group; bulk writes that touch many plans across a tenant should be rate-paced to avoid hitting Identity & Access write limits.

Sources