Microsoft throttles free Copilot Chat. Not even IT knows the limit

Sound familiar? The company never bought Copilot licenses, but Copilot Chat comes with Microsoft 365. So the marketing team uses it for briefs, summaries and first drafts. Free, and it works. That quiet dependency now has a ceiling nobody knows.

What Microsoft announced

In admin notice MC1536163, published November 3, Microsoft says new Copilot Chat limits begin rolling out on November 9. The key points:

• Who: users without a Microsoft 365 Copilot license in commercial tenants, on web, desktop and mobile. Personal plans like Family aren't affected, according to Born City.
• What: image generation already had limits. Now fair-use limits extend to more features. Microsoft doesn't say which, and the list may grow.
• How it feels: limits vary through the day. When a feature is unavailable, Copilot shows a notice and when to retry. Responses already in progress aren't cut off.
• What IT can do: nothing. Admins can't view or adjust the limits. Microsoft suggests briefing the help desk and reviewing settings for self-service license requests.

The fine print is a value transfer

What I find interesting isn't the throttling. Any vendor can cap a free tier. It's the design: the limit is invisible, it fluctuates and it can't be managed. Build your team on a tool whose capacity the vendor alone controls, with no numbers, and you give up predictability. My rule of thumb: read the terms first, then scale. That goes for ad platforms, and it goes for the assistant in your office suite.

And note the hint about license requests. Translation: whoever hits the limit is supposed to ask for a license themselves. The pressure on budget no longer comes from Microsoft's sales team. It comes from your own people.

The catch: where do people go instead?

The real second-order effect: when the company Copilot gives up at 11 a.m., someone opens a personal chatbot in the browser and pastes the brief in. AI doesn't fix broken ways of working, it widens the cracks. Without a clear rule on what's allowed, a throttle turns into a shadow-AI problem.

What I'd do now

• Count your dependencies. Ask the team this week: which three tasks run through Copilot Chat today? What happens if it's unavailable for two hours?
• Name an approved fallback. One sanctioned tool or a clear rule, so nobody drifts to personal accounts with company data.
• License by usage, not hierarchy. Help-desk tickets over the next few weeks will show who actually hits the limit. License those people first instead of everyone or no one.

Bottom line: A free tool with an unknown limit isn't a process. It's a bet on the vendor's goodwill.