Skip to content
TrustList
News

Microsoft widens Copilot Chat limits and will not say what they are

Editorial

By TrustList Editorial

Users without a Microsoft 365 Copilot licence now hit fair-use limits on more features. Limits vary through the day, and admins can neither see nor change them.

About Microsoft widens Copilot Chat limits and will not say what they are

Microsoft widens Copilot Chat limits and will not say what they are

3 November 2026: Microsoft is applying fair-use limits to more Copilot Chat features for commercial users who do not hold a Microsoft 365 Copilot licence, and admins can neither see the limits nor change them. Computerworld reports that smaller tenants started on 2 November and those with more than 2,000 seats follow from 9 November.

Not yet independently verified. We read the notice MC1536158 on a mirror of Microsoft's Message Center. The rollout dates and the plan list come from Computerworld only, and the mirror says only that the change is rolling out. We will update this when it can be confirmed, and remove this note.

What the notice says and leaves out

Message Center post MC1536158 covers web, desktop and mobile. Limits can vary through the day, an in-product notice tells a user when to try again, and responses already under way are not interrupted. Image generation already had limits under an earlier notice, MC1064749.

The post says "No action is required". It does not name the affected features, and it gives no thresholds. According to Computerworld the affected plans include Business Basic, Standard and Premium, Office 365 E3 and E5, and Microsoft 365 E3 and E5.

A limit that an admin cannot view is hard to plan around. A team that built a weekly process on Copilot Chat, a summary of a long document or a contract comparison, cannot test how far that process will run before it stops, and the answer may differ at 10:00 and 16:00.

Who will notice it first

Tenants with 2,000 seats or fewer are already in the rollout on Computerworld's dates, so the first complaints may be with help desks now. Microsoft's own advice is to brief help desk staff, and to review the Microsoft Support page on limits and the settings for self-service licence requests.

That second suggestion shows where this leads. The settings decide whether a user who hits a limit can ask for a paid Copilot licence. Organisations that have not decided who may do that should settle it before the limits start producing requests, since a rise in licence requests from one department could otherwise become an unplanned cost.

How to plan with no published number

Staff should be told plainly that Copilot Chat is not a guaranteed service at the free tier, so anything with a deadline needs a fallback. Help desk scripts can say that the message is expected and that the in-product notice gives the retry time, which will save a round of tickets about a fault that is not a fault.

IT and finance can also start counting. With no published thresholds, the only measure a customer has is its own record: how often users report the limit, in which teams and at what time of day. A few weeks of that gives a basis for deciding who actually needs a paid licence, and for asking Microsoft's account team questions it has so far left unanswered in public.

Related on TrustList:

Sources

Categories & features

TrustList Weekly

The week in software and IT, in one email

The news that matters to buyers, new rankings and our own research. Every Thursday, free, and easy to leave.

We will email you to confirm. Unsubscribe with one click in any issue. Privacy policy

You may be interested in

Microsoft has revised its notes on how Office extends ISO/IEC 29500 57 times since 2009; the core standard text dates from 2016. Why progress should not wait for ballots, and what buyers can ask.