Microsoft Copilot Rate Limits
Microsoft Copilot rate limits depend on the surface. Microsoft 365 Copilot has per-user fair-use throttling (not publicly published as per-second numbers; soft limits in the high tens of requests per minute per user). Copilot APIs accessed through Microsoft Graph apply Microsoft Graph throttling (per-app, per-tenant, and per-user). Copilot Studio applies per-message metering (counts toward the purchased message pack). GitHub Copilot has per-user request quotas and Copilot Chat conversation pacing. All surfaces use HTTP 429 with Retry-After.
Microsoft Copilot Rate Limits is the machine-readable rate-limit profile for Microsoft Copilot on the APIs.io network, in the API Commons Rate Limits shape.
It captures 5 rate-limit definitions, measuring requests_per_10s, requests_per_minute, and messages_per_month.
Limit state is signalled in the retryAfter, rateLimitLimit, rateLimitRemaining, and rateLimitReset response headers, and an exhausted limit returns HTTP 429.
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 5 backoff/retry policies defined and response codes documented for throttled and serviceUnavailable.
Tagged areas include Agents, AI Assistant, Artificial Intelligence, Chatbot, and Copilot.
retryAfterrateLimitLimitrateLimitRemainingrateLimitReset
generated, dated 2026-05-05.
Limits
Policies
Sources
- https://learn.microsoft.com/en-us/graph/throttling
- https://learn.microsoft.com/en-us/microsoft-copilot-studio/requirements-messages-management
- https://learn.microsoft.com/en-us/microsoft-365-copilot/microsoft-365-copilot-licensing
Work with this as data
Every rate limit here is available over the APIs.io API and to AI agents over MCP.