Skip to content
tenantcraft
( Insights)

Copilot Chat limits start November 9 for staff without a licence

From November 9, 2026, Microsoft adds limits to Copilot Chat for everyone without a Microsoft 365 Copilot licence. The limits change through the day, Microsoft doesn't publish the numbers, and admins can't see or change them. What you can control is the help desk script and where licence requests go.

Stage
Govern
Topic
Copilot
Published
Written by

Tested in a live tenant,

(Short version)

MC1536163 puts limits on Copilot Chat for users without a Microsoft 365 Copilot licence from November 9. You can't see or raise the limits. Brief the help desk that a limit message is not an outage, check Billing > License requests in the admin center, and decide who gets a licence before the year-end freeze.

In this post

On Tuesday, November 3, 2026, Microsoft posted message MC1536163 to the Microsoft 365 message centre. The title is three words: Limits in Copilot Chat. Starting November 9, people without a Microsoft 365 Copilot licence will hit limits on some Copilot Chat features.

Microsoft gave six days of notice. The message says no action is required. That’s true for the tenant settings, because there are none to change. It isn’t true for your help desk, which will start getting tickets that say “Copilot is broken.”

We’re seeing a lot of Microsoft changes land at year end, right when most IT departments go into change freeze. This one lands first, and the rest of December follows close behind. Here’s what changes, what to tell staff, and which other dates fall inside a freeze.

What changes on November 9

Copilot Chat is the free chat that comes with Microsoft 365 work accounts. Staff use it in the browser, in the desktop apps and on their phones. Until now, most of it has had no visible cap for people without the paid licence.

From November 9, Microsoft adds what it calls fair use limits to more Copilot Chat features. Here is what MC1536163 says, in plain words:

  • Who: users without a Microsoft 365 Copilot licence, in commercial tenants.
  • Where: Copilot Chat in apps on the web, desktop and mobile.
  • How: the limits can vary throughout the day.
  • Control: Microsoft sets and manages them. In Microsoft’s words, “Admins can’t view or adjust the limits.”
  • Mid-answer: a response that’s already being written won’t be cut off.

Image generation in Copilot Chat already has a limit, announced in MC1064749. MC1536163 extends the same idea to more features, and says the limits may expand over time.

Who gets hit, and who doesn’t

Staff with a Microsoft 365 Copilot licence are outside these limits. Everyone else in a commercial tenant is inside them.

Microsoft’s support article calls it the Copilot licence add-on, and that word matters. A Microsoft 365 plan on its own doesn’t include it. In my own tenant, the licence list shows Microsoft 365 E5 Developer and no Microsoft 365 Copilot licence. Every account there falls under the new limits.

For a typical 20 to 500 person organisation in Ontario, that’s most of the staff. Copilot licences usually go to a pilot group first, so the pilot group won’t notice anything and everyone else might.

How the limits behave

Microsoft’s support article, Limits for features and capabilities in Copilot Chat, fills in a few gaps. It applies to Microsoft 365 users without a Copilot licence who sign in with a work or school account.

For your help desk, these are the lines to quote:

  1. “Microsoft does not publish or share specific numeric limits.” Nobody can tell a user they have 10 chats left. That number doesn’t exist in public.
  2. “This isn’t an error or product malfunction.” When a user hits a limit, it’s working as designed.
  3. “Users will be notified in-product if the feature is not available.” The message tells them they can retry later, and the product gives the timeframe.

Microsoft also says availability “can vary based on service conditions.” Two people asking the same thing at 10 a.m. and 3 p.m. can get different results. So “it worked for Sam” is not proof that something is wrong with the user who got blocked.

What to tell your help desk

You control this part. Send it before Monday, November 9.

The short version for staff. “From November 9, Copilot Chat has daily limits for people without a Copilot licence. If you see a message that a feature isn’t available, nothing is broken. Try again later, at the time the message shows.”

The triage rule for the help desk.

  1. Ask whether the user has a Microsoft 365 Copilot licence. If they don’t, a limit message is expected. Close the ticket with the short version above.
  2. If they do have a licence and still see a limit message, treat it as a real fault and escalate.
  3. If the same user hits limits most days, and the work matters, that’s a licence conversation, not a ticket. Send it to whoever owns licensing.

What not to promise. Don’t give users a number of chats per day. Microsoft doesn’t publish one, so any number you give will be wrong by next week. And don’t tell them IT can raise it. Nobody in your tenant can.

Where the licence requests land

When the triage rule says “licence conversation”, it helps to know where the request ends up.

If you’ve blocked self-service purchases, a user who tries to buy a blocked product can send you a request instead. In my own tenant on November 4, those requests live in the Microsoft 365 admin center under Billing > License requests. It’s its own item in the left menu. Microsoft’s documentation still describes it as a Requests tab on the Licenses page, so if you go looking for the tab, you won’t find it.

Microsoft 365 admin center · Billing · License requests

License requests is its own item under Billing, not a tab on Licenses. An empty list means nobody has asked yet, not that nobody needs a licence.

Microsoft’s documentation adds a few details:

  • You need at least the User Administrator or License Administrator role to work the list.
  • Requests are held for 12 months. A request from November is still there in the new year, waiting.
  • If your organisation has its own approval process, Use your existing request process instead shows users your message rather than collecting requests here.

When you approve, you can assign the licence through a security group instead of user by user. If your Copilot pilot already runs from a group, approve into that group and the licence follows the person.

The other dates inside a December freeze

Copilot Chat isn’t the only change before the holidays. If your team freezes changes in December, these are the dates I’d put on the calendar now. Each one is from a Microsoft source.

DateWhat happensWho should care
November 9Copilot Chat limits start for unlicensed users (MC1536163)Help desk, everyone
November 15, 2026No new Dataverse for Teams environments, and no new unmanaged developer environmentsPower Platform admins
November 30, 2026The App Builder agent and vibe.powerapps.com retire (MC1505609)Makers using prompt-to-app
December 2, 2026Prompts in Copilot Studio, Power Automate and Power Apps move to newer GPT models on their own (MC1536101)Anyone with an AI prompt in a flow or app
December 15, 2026Existing unmanaged developer environments are suspendedDevelopers, Power Platform admins

The December 2 change is the one most likely to surprise someone. Microsoft moves prompts off the retiring models automatically, with no change to tier pricing. But the answers can change in wording and format. If a flow reads a prompt’s output and expects a fixed format, test it before December 2. After that, the old model is gone and you’re testing in production.

The Power Platform dates are covered in more detail in which Power App to build.

What this does not fix

A help desk script doesn’t make the limits go away. If a team depends on Copilot Chat for daily work and keeps hitting limits, the script only explains why. The fix for that team is a Microsoft 365 Copilot licence, and that’s a budget decision.

You also can’t measure the problem in advance. There’s no report of who would have been limited, because Microsoft doesn’t show admins the limits. You’ll find out from tickets and complaints after November 9. Ask the help desk to tag those tickets so you have a count by January.

And this post doesn’t cover pay-per-use models or agents, which have their own billing. The cost side of those is in Copilot pay-per-use models.

The bottom line

Send the help desk the short version and the triage rule before November 9. Look at Billing > License requests so you know where requests land, and decide who approves them before the December freeze. Then put December 2 on the calendar and test any flow that reads a prompt’s output.

(Paired checklist, 7 pages)

Copilot Readiness Governance Checklist

You get one email with the link. That's the only email.

Read it on the site
  • Why Copilot mirrors your permissions, and oversharing becomes oversurfacing
  • Map oversharing with the Data Access Governance reports, then remediate it
  • Restricted Content Discovery and Restricted Search: the interim safety valves
  • Sensitivity labels, DLP, and Copilot's own controls (with E5-only items marked)
Sneak peek

Document preview

100%

Loading the document…