Microsoft Copilot licensing has two moving parts, and most of the guidance in circulation describes only one of them. The per-user add-on is the part everyone quotes. The consumption meter sitting behind agents is the part that turns up on a later invoice, and the add-on does not cover all of it. The eligibility list is also far wider than the E3 and E5 shortlist that gets repeated: Exchange Plan 1 qualifies, so does SharePoint Kiosk, so does Clipchamp.
There is a prior question. A licence is the last decision in a Copilot rollout rather than the first, because an unprepared tenant wastes the entitlement whatever it cost, which is what a copilot readiness assessment is for. What follows assumes that decision is made and you now need to know what to buy, what it entitles, and why a correctly assigned licence sometimes produces nothing at all. Every fact below was verified against Microsoft Learn on 20 October 2026.
What Microsoft Copilot licensing covers now
The product names changed recently enough that stale terminology is the first thing to clear up. The app formerly called Microsoft 365 Copilot is now Microsoft Copilot, and its primary URL is moving to copilot.cloud.microsoft. The Microsoft 365 Copilot Chat app is now Microsoft Copilot Chat.
On the commercial side there are two add-on SKUs rather than one. Microsoft Copilot Business sits on top of the small-business base plans. Microsoft Copilot sits on top of everything else. Which one you are entitled to buy is decided entirely by the base plan you already hold.
Be aware that Microsoft’s own documentation is not consistent on these names right now. The licence options article names the SKUs Microsoft Copilot and Microsoft Copilot Business. The overview article describes the experience tiers as Microsoft 365 Copilot (Basic) and Microsoft 365 Copilot (Premium). Both pages were updated within the last month. This is not a trivial inconsistency when you are on a renewal call and procurement is reading one page while support is reading the other.
Which plans qualify as a prerequisite
This is the table that is usually reduced to three SKUs and should not be. Taken from License options for Microsoft Copilot, last updated 30 September 2026.
| Add-on | Qualifying base plans |
|---|---|
| Microsoft Copilot Business | Microsoft 365 Business Premium, Business Standard, Business Basic, Microsoft 365 Apps for Business, Microsoft Teams Essentials |
| Microsoft Copilot (Microsoft 365 plans) | Microsoft 365 E7 (includes Microsoft Copilot), E5, E3, F1, F3, Business Premium, Business Standard, Business Basic, Apps for Enterprise, Apps for Business |
| Microsoft Copilot (Office 365 plans) | Office 365 E5, E3, E1, F3 |
| Microsoft Copilot (Teams plans) | Microsoft Teams Enterprise, Microsoft Teams EEA, Microsoft Teams Essentials |
| Microsoft Copilot (Exchange plans) | Exchange Plan 2, Exchange Plan 1, Exchange Kiosk |
| Microsoft Copilot (SharePoint plans) | SharePoint Plan 2, SharePoint Plan 1, SharePoint Kiosk |
| Microsoft Copilot (OneDrive plans) | OneDrive for work and school Plan 2, Plan 1 |
| Microsoft Copilot (Planner and Project plans) | Microsoft Project and Planner Plan 5, Plan 3, Microsoft Planner Plan 1 |
| Microsoft Copilot (Visio plans) | Visio Plan 2, Visio Plan 1 |
| Microsoft Copilot (Other plans) | Microsoft Clipchamp |
Government tenants on GCC, GCC-High and DoD have their own list, as do education tenants buying through Enrollment for Education Solutions or a Cloud Solution Provider. No seat minimum is stated anywhere on that page.
Two things follow from the breadth of that list. The first is that estates nobody models in a Copilot business case are eligible: Teams-only, Exchange-only, and frontline F plans can all carry the add-on. The second is a caution. That is a prerequisite list, not a feature list. Being eligible to buy the add-on tells you nothing about what a given user will be able to do with it, because the in-app experiences need the apps. An Exchange Plan 1 user is eligible for the add-on and is not going to be using Copilot in Excel.
What the add-on buys, and what you already have
The overview article now describes four tiers, and the gap between the second and third is the one that costs organisations money.
| Tier | Add-on held | What it gives |
|---|---|---|
| Copilot Chat (Basic) | No | Baseline experience included with eligible Microsoft 365 licences. No Copilot in Word, Excel, PowerPoint or OneNote. Agents that use web data, with pay-as-you-go work data agents. |
| Microsoft 365 Copilot (Basic) | No | Standard access to Copilot in Word, Excel, PowerPoint and OneNote. |
| Microsoft 365 Copilot (Premium) | Yes | Priority access to the full experience in those apps, plus agents using web and work data. |
| Usage-based billing | Yes | As Premium, plus Copilot Cowork and Copilot Code, billed on consumption. |
The real boundary is narrower than the tier table suggests. Web-based chat, which returns results from the internet, is automatically included with an eligible Microsoft 365 subscription at no extra cost. Work-based chat, which returns results the user’s Microsoft Entra work or school account can actually reach, requires a Microsoft Copilot licence. That distinction decides whether Copilot is useful to an organisation, because a chat experience that cannot see tenant data is a different product wearing the same name, as the architecture behind Copilot Chat makes fairly clear.
The Basic tier is the surprise in that table. Standard access to Copilot in the Office apps without the add-on means some of what an organisation is about to buy may already be present at a lower service level. Confirm which tier your tenant is actually on before a renewal, because the add-on may be buying priority access and extensibility rather than access itself.
Agents, Copilot Credits, and the part that bills separately
Grounding decides the bill. That is the whole rule, and it is stated plainly in Plan licensing and cost for Microsoft 365 Copilot extensibility, last updated 30 September 2026.
Hold the add-on and there are no extra charges for extensibility: Copilot connectors, agents and plugins are included. Without the add-on, agents grounded only in instructions or public websites still cost nothing, but the moment an agent reaches shared tenant data such as SharePoint or a Copilot connector, usage is metered in Copilot Credits through Copilot Studio. The Work IQ API bills the same way. The Microsoft 365 Copilot APIs are free to licensed users and simply not available to unlicensed ones.
Custom engine agents are a separate budget line again. They are hosted outside Microsoft 365 Copilot, so Copilot Studio licensing or a Power Platform plan may apply, and Azure AI Foundry, Azure App Service and Azure Bot Service bill under their own pricing.
Spending controls live in the Microsoft 365 admin center under Copilot, then Cost Management, then the Configuration tab, where you add a spending policy. Per Managing AI experiences enabled by usage-based billing, last updated 2 October 2026, a per-user monthly budget has to be set at a minimum of 2,000 credits per user per month, at least two models must be selected, and prepaid credits from capacity packs or pre-purchase plans are always consumed before pay-as-you-go.
One line on that page deserves to be read twice. When users hit the limit, they lose access to agents and services for the rest of the month, until credits reset on the first of the month. A cap is not a warning, it is a stop.
The newsletter
Get the next Copilot fix like this one by email
Subscribe and get the free 8-page Intune troubleshooting field guide (PDF), then new fixes about twice a month. From a Microsoft MVP.
Why I am not quoting a per-user price
Because the number would be wrong for most people reading it. Copilot pricing varies by region, by agreement type, and by whether the commitment is annual or monthly, and it changes on Microsoft’s schedule rather than mine. Microsoft publishes current pricing on its own Copilot plans page, and that is the only figure worth acting on.
What does not change month to month is the structure, and the structure is where the money actually goes: which base plan you hold, whether you need the add-on at all, and whether your agents touch tenant data. Get those three right and the arithmetic is straightforward. Get them wrong and no amount of per-seat negotiation recovers it, which is the same pattern that runs through the rules that decide a Microsoft 365 bill generally.
The failure modes
These are the ones worth knowing before they cost an afternoon.
- The licence is assigned and Copilot does not appear. Documented behaviour, not a fault. For some apps users might wait up to 24 hours for Copilot to appear, and may need to restart or refresh the app. Check elapsed time before escalating anything.
- The licence was assigned to a guest. Assigning Copilot licences to cross-tenant users, including guests, is not supported. It does not fail loudly. The seat is consumed from your pool and delivers nothing.
- The user is licensed and the capability is still missing, because it needs a different licence. Some Copilot-adjacent features require Microsoft Purview, and some require Microsoft SharePoint Premium with SharePoint Advanced Management. A Copilot licence is not a blanket entitlement to the controls that govern Copilot, which is how the controls that actually limit oversharing end up being budgeted after the rollout rather than before it.
- Agents stop working halfway through the month. Not an outage. A spending policy limit was reached, and access returns on the first of the next month.
- Two Microsoft pages give the licence two different names. Quote the SKU name from the licence options article to procurement, and the tier name from the overview article to support, until the documentation settles.
Before raising a ticket for any of the first three, run the Copilot License Details diagnostic in the Microsoft 365 admin center. It checks whether a specific user account meets the requirements, which resolves the question faster than a support thread will.
I have not run a Copilot deployment at scale in production. My tenant is a lab with no enrolled devices, so everything above is read off dated Microsoft documentation rather than measured. The one I would expect to bite hardest in a real estate is the fourth, because a mid-month loss of agent access looks exactly like a product fault to the people reporting it and exactly like working-as-designed to the people who set the policy.
What I would do differently
Decide the grounding question before the licence question. The cost driver in a Copilot estate is not how many people hold the add-on, it is how many agents read tenant data and who is holding the add-on when they do. An organisation that buys Chat broadly to save money and then builds three SharePoint-grounded agents has not saved money, it has moved the bill onto a meter it is not watching. The honest version of the return on investment argument for Copilot has to include that meter.
Set the spending policy before anyone builds an agent rather than after the first invoice, and treat the 2,000 credit per user per month floor as the cost of having a cap rather than something to argue down.
Check which tier the tenant is on before the renewal, not during it. If standard access to Copilot in the Office apps is already there, the conversation is about priority access and extensibility, which is a much smaller conversation than buying Copilot from scratch.
And re-check your own links. Three of the five Microsoft Learn pages I started from this morning now return a 301: Microsoft is renaming the Copilot documentation tree and dropping the microsoft-365 prefix from the paths. Any internal runbook or onboarding document that cites those older URLs is already pointing at a redirect, and will eventually point at nothing.
Last verified: 20 October 2026
