Copilot Chat Fair-Use Limits: What Changes for Unlicensed Users

The free tier just got a meter

On 4 November 2026, Microsoft introduced fair-use limits on Copilot Chat for users without a Microsoft 365 Copilot licence. The change reaches commercial tenants on the web, desktop and mobile apps. Licensed users are unaffected and continue to get additional features.

Microsoft's own framing to its partner channel is unusually direct about what this is for. The announcement is titled around the fact that these limits "create an upsell conversation with your customers."

That is worth sitting with, because it tells you exactly what changed and what did not. Copilot Chat has not been withdrawn. It is still included in Microsoft 365 subscriptions, and administrators are not required to take any action. What changed is that the unlicensed tier now has a ceiling, and the ceiling is the product boundary that makes the paid licence legible.

If your organisation has been running a deliberate two-tier estate — a small group of licensed power users and a long tail of people on Copilot Chat — that strategy has not been invalidated. But the assumption underneath it, that the unlicensed tier was effectively unlimited, no longer holds.

What "fair use" does and does not tell you

Fair-use limits are not a published seat allowance. They are a throttle expressed as a usage policy rather than a number on a price list, and that distinction matters for planning.

A per-user quota you can read off a page is something you can model. You multiply it by headcount, compare it against observed demand, and decide how many licences to buy. A fair-use policy is not that. It is a commitment to reasonable access with a reserved right to limit outliers, which means:

• You cannot compute your exposure in advance from the policy text alone.
• Your heaviest unlicensed users are the ones who will feel it first, and they are the users most likely to be doing something valuable.
• The signal that you have a problem arrives as a degraded experience for a specific person, not as a billing alert or an admin notification.

This is the operational trap. Capacity problems that surface as individual frustration rather than as a centrally visible event tend to get reported late, inconsistently, or not at all. Someone hits a wall, assumes the tool is flaky, and goes back to doing the task the old way. Nothing in your telemetry says "licence shortfall."

Measure before you buy

The instinct when a free tier gets limited is to buy licences for the people who complain. That is the most expensive possible order of operations, because complaint volume correlates with seniority and confidence, not with usage.

Microsoft shipped the instrument for doing this properly in the same month. A new agents usage report is arriving in the Microsoft 365 admin center, and its most useful property for this specific problem is easy to miss: it reports usage by both licensed and unlicensed users.

That gives you the one number the licensing decision actually needs — real demand from people who do not currently have a licence. The report covers total active agent users, total active agents, and segmentation of active users by licence status. We cover that report, and the new authoritative content list that shipped alongside it, in two new Copilot admin controls.

So the sequence is:

1. Read the unlicensed usage segmentation first. Find out who is genuinely active without a licence, before anyone escalates.
2. Separate depth from breadth. A hundred people asking one question a week is a different purchase than ten people working in Copilot Chat all day. Only the second group is a licensing case.
3. Then buy, against observed demand. Not against the complaints queue, and not against a headcount percentage somebody picked in a planning meeting.

If you have not stood up any Copilot measurement yet, that is the gap to close this month. We cover the broader instrumentation question in building a Microsoft Copilot adoption metrics dashboard, and the licensing trade-offs in the Copilot licensing guide.

This is a separate change from the December purchasing shift

Two Copilot commercial changes are landing weeks apart and they are being discussed as though they were one announcement. They are not, and conflating them will put your remediation work on the wrong deadline.

• 4 November 2026 — fair-use limits on Copilot Chat for unlicensed users. This is an entitlement change. It affects what people can do.
• 1 December 2026 — the purchasing and billing changes, including usage-based billing becoming the default for new Copilot Business licences in CSP and the removal of the base-subscription prerequisite. This is a procurement change. It affects how you buy.

The second set has its own operational traps, including a licence-automation break that hits organisations which never purchase Copilot Business at all. We treat those separately in Copilot's December 1 billing and licensing changes.

Keeping them apart on your change calendar is not pedantry. The November change needs a measurement response. The December change needs a procurement and scripting response. Different owners, different work, different dates.

Deciding who actually needs a licence

The question "who needs a full Microsoft 365 Copilot licence" has a cleaner answer than it used to, because the tiers now diverge on capability rather than on capacity alone.

Copilot Chat's value is bounded by what it can reach. The full licence is what puts Copilot inside the applications where work is produced and grounds it in your tenant's own content. If someone's use case is answering general questions, the chat tier was always the right fit and still is. If their use case is drafting from a document set, working inside Excel or PowerPoint, or anything that depends on grounding in organisational data, the chat tier was never going to be sufficient and the fair-use ceiling simply makes that clearer sooner.

Our Copilot Chat versus full Copilot selection guide walks the decision in detail.

What to do in the next two weeks

• Confirm the change applies to you. Commercial tenant, users without a Copilot licence, using Copilot Chat on web, desktop or mobile. If that describes part of your estate, you are in scope.
• Check whether the agents usage report has reached your tenant and look at the unlicensed segmentation as soon as it does.
• Tell your service desk what to listen for. Throttling will not arrive labelled as throttling. It will arrive as "Copilot stopped working for me." Give them a tag for it so the pattern becomes visible centrally instead of dying in individual tickets.
• Keep your November and December work streams separate. Entitlement now, procurement next month.
• Do not pre-buy against a worst case. The whole point of having a usage report that covers unlicensed users is that you no longer have to guess.

The change itself is modest. The risk is not the limit — it is deciding your licence count from whoever shouts loudest, four weeks before a procurement change that alters how you buy in the first place.

Sources

• Partner Center announcements, November 2026 - "Copilot Chat: limits for users without a Microsoft 365 Copilot license" (4 November 2026)
• Microsoft 365 Copilot release notes - agents usage report, Microsoft 365 admin center
• Microsoft 365 Copilot licensing

Microsoft may change dates and availability. Verify against the Partner Center announcement before acting on a specific date.