What’s changing with Copilot Chat fair use limits
Microsoft has confirmed, through its own support documentation, that fair use limits now apply to Copilot Chat features used by Microsoft 365 accounts that do not hold a paid Microsoft 365 Copilot add-on license. This matters for SMB admins because many organizations have users accessing Copilot Chat without ever purchasing the full Copilot license — and those users can now encounter feature limits that didn’t exist in earlier, more open access models.
A “fair use limit” in this context means Microsoft restricts how much a user can draw on certain Copilot features over time, rather than removing access to the feature outright. According to Microsoft, this approach already applied to image generation, and Microsoft is now expanding fair use limits to additional Copilot Chat features.
Who is affected
Based on Microsoft’s documentation, the limits apply specifically to:
- Copilot Chat (Basic) users — Microsoft 365 users who do not have the Copilot add-on license and do not have access to Copilot inside Word, Excel, PowerPoint, and OneNote.
- Microsoft 365 Copilot (Basic) users — Microsoft 365 users who also lack the add-on license but still have standard (non-priority) access to Copilot features inside Microsoft 365 apps.
Users must be signed in with a work or school account for these limits to apply, according to Microsoft’s support article. Users with a full Microsoft 365 Copilot (Premium) add-on license are described separately in Microsoft’s licensing comparison and are associated with priority access rather than the basic fair use model.
It’s worth noting that Microsoft’s documentation does not state a specific calendar effective date for when fair use limits begin to apply. The most recent Microsoft support article on this topic carries a last-updated date of October 31, 2026, with content refreshed on November 10, 2026. Admins should treat these as documentation dates rather than a confirmed rollout date, since Microsoft’s sources do not explicitly label either date as an “effective date” for the policy itself.
What Microsoft says about scope and behavior
Microsoft’s support documentation is deliberately conservative about the mechanics of these limits. Key documented points include:
- No published numeric thresholds. Microsoft states it does not publish or share specific numeric limits, because service limits can vary and may change over time as the product evolves.
- In-product notification. If a user reaches a limit, Copilot notifies them directly within the product interface rather than failing silently.
- Not an error. Microsoft explicitly states that being unable to use a feature due to a limit “isn’t an error or product malfunction” — a distinction that matters for support teams trying to triage user reports.
- In-progress tasks are not interrupted. If a task is already running when a limit is reached, Microsoft says that task will continue rather than being cut off mid-process.
- Feature availability can shift. Microsoft notes that availability of features subject to fair use limits “may change over time and can vary based on service conditions,” meaning the same user might experience different availability on different days.
Because Microsoft does not publish exact thresholds, admins should not promise end users a specific number of chats, queries, or generations per day or month — that information simply isn’t available in Microsoft’s documentation.
What admins can and cannot control
Microsoft’s Copilot overview documentation outlines where admin control exists today, and it’s important to separate what is confirmed as configurable from what is not.
Documented admin controls
Through Copilot controls in the Microsoft 365 admin center, admins can:
- Control whether Copilot Chat is pinned across experiences (such as in the Microsoft 365 app and other Copilot surfaces), based on licensing.
- Manage whether users can generate images in Copilot Chat by configuring Copilot actions.
- Control how users can create and use agents, noting that agents may have expanded capabilities for Microsoft 365 Copilot (Premium) users.
- Manage web search grounding through the “Allow web search in Copilot” policy, which Microsoft states applies to Copilot Chat experiences across all license types.
- Remove user access to Copilot Chat entirely, including for Copilot Chat (Basic) users.
Microsoft also describes an AI Administrator role that provides least-privilege access to manage Copilot and related AI features across Copilot Chat (Basic), Microsoft 365 Copilot (Basic), and Microsoft 365 Copilot (Premium), without requiring Global Administrator permissions.
What’s not documented
Microsoft’s supplied documentation does not describe any admin setting that lets an organization adjust, raise, lower, or exempt specific users from fair use limits. There is also no documented admin-facing dashboard showing how close a given user is to a limit, or exact numeric thresholds admins can reference when users ask. Admins should avoid assuming such controls exist unless Microsoft publishes further guidance.
Practical recommendations for help desk preparation
The following is practical operational guidance for SMB admins, not a documented Microsoft requirement or published best practice. Consider it a starting point rather than an official checklist:
- Brief your help desk now that some users may see in-product messages about reaching a usage limit for a Copilot feature, and that this is expected behavior rather than a bug to escalate as an outage.
- Set expectations with end users that Copilot Chat features tied to fair use limits may be unavailable at times, and that availability can vary — rather than promising continuous access.
- Document which users hold a Copilot add-on license versus those on Copilot Chat (Basic) or Microsoft 365 Copilot (Basic), since license status determines whether fair use limits apply at all according to Microsoft’s licensing comparison.
- Review your Copilot controls configuration in the admin center periodically, since settings like agent creation, image generation, and web search grounding directly affect what unlicensed users can do with Copilot Chat.
A note on license requests
Because fair use limits apply specifically to users without the Microsoft 365 Copilot add-on license, some organizations may see an increase in requests from users wanting that license once they encounter a limit message. Microsoft’s supplied documentation does not describe a specific self-service license request feature or setting for this scenario. As a practical matter, SMB admins may want to have an internal process ready for evaluating and responding to these requests — for example, a simple intake form or a designated approver — rather than relying on ad hoc email threads. This is a general operational suggestion, not something described in Microsoft’s Copilot documentation.
Why this matters for SMB admins
Many small and midsize organizations deployed Microsoft 365 Copilot Chat broadly because it didn’t initially require every user to carry a paid add-on license. That accessibility is still true, but Microsoft’s confirmation that fair use limits now extend beyond image generation into additional Copilot Chat features means unlicensed users may notice more friction over time. Since Microsoft intentionally withholds exact thresholds, the most reliable approach for admins is to monitor in-product notifications your users report, rather than trying to reverse-engineer a fixed quota.
Conclusion
Microsoft has confirmed that fair use limits apply to Copilot Chat features for Microsoft 365 users without a Copilot add-on license, and that this approach is expanding beyond the previously limited image generation feature. Microsoft does not publish specific numeric thresholds, treats reaching a limit as normal product behavior rather than an error, and allows in-progress tasks to finish uninterrupted. Admins retain documented control over Copilot Chat visibility, agent creation, image generation, web search grounding, and full access removal through Copilot controls and the AI Administrator role — but there is no documented mechanism to adjust the fair use thresholds themselves. SMB admins should prepare help desk teams accordingly and treat any internal license-request process as a practical governance step rather than a Microsoft-defined requirement. As with all draft guidance on UpdateCompass, this article requires human review before any organizational decisions are finalized.