On 4 November 2026, Microsoft announced additional fair use limits for Copilot Chat users without a Microsoft 365 Copilot licence. The rollout began on 2 November for organisations with 2,000 or fewer Microsoft 365 seats. Copilot Chat remains included in Microsoft 365 subscriptions; this announcement does not mean everyone must buy the paid add-on.
If someone in your team sees a limit message, I would treat it as a reason to ask about their work. What were they trying to finish, how often does that happen, and what would better access be worth?
A limit message tells you someone has reached a product boundary. You still need to establish whether paying to change their access would help the business.
Understand what the message means
Microsoft says limits can vary during the day, are managed by Microsoft and cannot be viewed or adjusted by your administrator. It does not publish fixed numerical allowances. I would avoid planning a business process around an assumed number of prompts or promising staff a guaranteed daily quota.
The rollout dates below come from Microsoft’s announcement. They describe when rollout starts for each organisation size, rather than a deadline to purchase anything.
Smaller organisations: rollout beganOrganisations with 2,000 or fewer Microsoft 365 seats.
Partner announcement publishedMicrosoft explains the limits and licence-request options.
Larger organisations: rollout beginsOrganisations with more than 2,000 Microsoft 365 seats.
Microsoft’s support guidance says a limit notification is expected behaviour, rather than a product fault, and work already in progress will not be interrupted. Ask staff to keep the message and follow the availability information shown in the product. Your help desk needs to recognise it so that an ordinary limit does not become a long troubleshooting exercise.
Record the work affected
Ask the person to describe the task in ordinary language. “Preparing the customer briefing” is useful. “Using AI more” is too broad to support a spending decision.
For each occurrence, I would record the feature they were using, the task, whether it had a deadline and what they did next. Note whether they finished another way, waited, or left the work unfinished. Avoid collecting the underlying customer or employee information when a short task description will do.
Then ask what the interruption actually cost. Waiting until a feature becomes available again might make little difference to a draft for next month. A repeated interruption during time-sensitive preparation deserves closer attention. Distinguish time spent actively redoing work from time when the person could get on with something else.
Keep this record alongside a sample of the finished output. Frequent use alone would not persuade me to buy a licence if the results still need extensive correction. I would want evidence that the task is useful and that the person can check the answer.
Ask for a quote against that task
Take the record to whoever manages your Microsoft 365 subscriptions. Ask them to confirm the person’s current licence, the exact feature affected and what an eligible paid option would change. Get that answer before treating an upgrade as the solution.
Ask for a written UK quote covering the full commitment, renewal terms and any other subscriptions the proposed setup needs. I would also ask what limits or service conditions would still apply. Do not turn “paid” into an internal promise of unlimited access.
Compare the proposed cost with the value of the specific work. Include time spent preparing inputs, checking results and correcting mistakes. Count only the time the change could reasonably release, and decide how the team would use it. A saving that lets someone handle more customer work has a clearer purpose than an unexplained estimate of hours.
If the case looks worthwhile, I would start with the people doing that task and agree a review date. Ask the supplier what purchase or trial terms are available before committing. Check whether the change actually improves access for the relevant feature and whether the finished work is better or faster after review.
Make licence requests a deliberate decision
Microsoft says the limit message may offer a licence request, and some organisations may also allow users to purchase directly. Administrators can approve or deny requests and can turn off direct purchases for each product. I would ask your administrator to review those settings against your normal purchasing process.
Give staff a simple route: send the request to a named person with the task, the problem and the expected benefit. Explain which AI tools remain approved while they wait. Keep business information in those approved tools rather than opening a personal account to get around a limit.
During November, review the requests together. Some may justify a paid licence; others may be better served by waiting, changing the working method or using an existing business tool. Record the reason for each decision so that the next request starts with evidence.
The question I would put on the purchase request is: what useful work will this licence let us complete, and how will we check that it did?