Official documentation checked October 14, 2026.
An active Copilot license does not identify every usage limit that might apply to a particular feature or agent. “Quota exceeded” can refer to a feature allowance, a metered agent’s capacity, a short-term rate limit or a connected service. First locate the failing component.
There is no documented general Microsoft 365 Copilot setting called “Daily request limit per user” with a default of 500 that administrators can set to zero for unlimited use. Do not change unrelated licensing or permissions based on that supposed fix.
Identify the product, account and exact limit
Record the full message and code, time, application, selected agent or feature, and whether one user or many are affected. Note whether ordinary Copilot chat still works when the failing agent or feature is not used. Use a non-sensitive test prompt rather than repeatedly submitting the same confidential request.
- Ordinary work or school Copilot: verify the signed-in account and the specific feature entitlement. “The subscription is active” does not establish that the correct user has the relevant service.
- A named agent: identify its owner, hosting environment and whether it uses metered features, flows or external services.
- A personal account: check that account’s subscription and displayed allowance. Its limits are not a tenant-wide pool shared with your organization’s users.
- An integration returning HTTP 429: capture the service that returned it and any retry information for the integration owner.
Microsoft explains how to identify the actual entitlement in What Copilot license do I have? If failures are widespread or sudden, an administrator should also check Health > Service health for a relevant incident, using the service-health guide.
Check the matching capacity or throttling control
For Copilot Studio agents: an authorized administrator can open the Power Platform admin center, select Licensing > Copilot Studio > Summary, and inspect capacity and consumption for the actual environment. Review any configured agent-level monthly limit as well as allocated capacity. See Manage Copilot Credits and capacity.
A capacity shortage and a requests-per-minute limit are different. Microsoft documents Copilot Studio quotas separately from purchased capacity. Extra credits do not establish that every throughput bottleneck has been removed. Use the current table for the agent’s applicable plan and environment rather than borrowing a number from another Copilot product.
If an approved workload needs more capacity, its owner can evaluate reallocating available capacity or an approved billing change. Pay-as-you-go can create additional charges; do not enable it as a cost-free troubleshooting step. Microsoft’s Studio throttling guidance also explains that a rate-limit increase is subject to eligibility and support approval, not guaranteed.
For a custom integration: its owner should inspect each downstream service. Microsoft Graph’s throttling guidance recommends honoring the response’s Retry-After delay. Reduce unnecessary retries and request bursts. Increasing an unrelated Azure quota or changing a Copilot license does not automatically raise every service’s limit.
Retest without weakening access or removing safeguards
If the app shows a reset or retry time, follow that guidance rather than assuming every limit resets at midnight. Avoid repeated rapid retries, particularly for an action that might already have partially completed. Check its outcome before sending it again.
Do not remove data-protection policies, grant broader source access or buy the same higher-tier license for everyone merely because some users are affected. A different user population, feature or agent may be hitting a different constraint.
After a scoped correction, test the same feature and inspect its relevant consumption or error record. Keep the account, environment, result and timestamp together. If ordinary licensed Copilot remains blocked and the specific limit is not identified, escalate with that evidence to Microsoft support. A generic usage graph cannot, by itself, prove the cause or justify an unlimited-quota claim.