Microsoft 365 Copilot Licensing Explained: What You Actually Need Before You Buy
Licensing · Admin Readiness · SMB · 2026
Most IT admins already know what Copilot does for end users. What trips them up is the licensing — because "Copilot" in Microsoft 365 is not one thing. There is a free tier, two paid tiers, a set of base plan requirements, and five technical prerequisites that can silently prevent Copilot from working even after you have assigned the licence. Buying the wrong SKU, or buying the right SKU before fixing the environment, is one of the most common ways a Copilot rollout stalls before it starts.
This article explains exactly what you get at each tier, what base plans qualify, what needs to be in place technically before Copilot works, and what to check before approving the purchase order.
Copilot Chat vs Microsoft 365 Copilot — the distinction that matters
The confusion starts here. "Copilot" appears as a button in Word, as a panel in Teams, in the Microsoft 365 admin centre, and at copilot.microsoft.com — but not all of these are the same product backed by the same licence. The two experiences your users are most likely to encounter are Copilot Chat and Microsoft 365 Copilot, and they behave very differently.
- Web-grounded AI — answers based on the internet and general knowledge
- Can draft text, summarise content you paste in, brainstorm ideas
- Cannot automatically access your emails, files, Teams chats, or calendar
- Users must manually copy and paste work content to get AI assistance on it
- Available at copilot.microsoft.com and Microsoft 365 apps (see April 2026 note below)
- Work-grounded AI — access to the user's emails, OneDrive files, SharePoint, Teams chats, calendar, and meetings
- Copilot in Word, Excel, PowerPoint, Outlook, Teams, OneNote — all with work context
- Microsoft 365 Chat — a single conversational interface across all work data
- Meeting recaps with action items in Teams
- Copilot Pages for collaborative AI-assisted content
- Copilot Studio access for building custom agents, with differences depending on licensing scenario
The practical difference is this: with Copilot Chat, a user asking "summarise the project status" gets a general AI answer. With Microsoft 365 Copilot, the same question searches their actual emails, Teams messages, and SharePoint documents and generates a summary grounded in real work context. The productivity gap between the two is significant — but so is the cost gap.
The April 2026 change — how Copilot Chat surfaces inside Office apps is changing
The direction of travel is clear: Microsoft is consolidating the richest in-app Copilot experience behind the paid add-on. Before these changes, users with eligible Microsoft 365 plans could access web-grounded Copilot Chat inside Office applications without a paid licence. How that access changes — and on which surfaces — is worth validating in your tenant rather than assuming it will remain as-is.
The free Copilot Chat experience at copilot.microsoft.com and within Microsoft Teams is expected to continue for eligible accounts. For most SMB environments the practical concern is the same: if users are accustomed to seeing a Copilot button in Word, Excel, PowerPoint, or OneNote, verify what experience they will have going forward. Proactive communication before users notice a change prevents a helpdesk spike.
The two paid SKUs — Copilot vs Copilot Business
When Microsoft 365 Copilot became available for SMBs, Microsoft introduced a separate SKU — Copilot Business — targeted at organisations with up to 300 users. Both SKUs deliver the core work-grounded Copilot experience. Differences matter more when you move into broader agent, governance, and extensibility scenarios.
| Feature | Microsoft 365 Copilot Business | Microsoft 365 Copilot |
|---|---|---|
| Seat limit | Up to 300 users | No limit |
| Price (2026) | $21/user/month · promotional $18 through June 30, 2026 | $30/user/month |
| Copilot in Word, Excel, PowerPoint, Outlook, Teams, OneNote | ✓ Included | ✓ Included |
| Microsoft 365 Chat | ✓ Included | ✓ Included |
| Copilot Studio / custom agents | Core access included | Core access included — extensibility and capacity differ by scenario |
| Microsoft Graph connectors | Included — verify current quotas in licensing docs | Included — verify current quotas in licensing docs |
| Eligible base plans | Business Basic, Business Standard, Business Premium — verify current eligibility in Microsoft licensing docs | All eligible plans including E3, E5, F1, F3 |
Where Copilot appears after the licence is active
Once the Microsoft 365 Copilot licence is assigned and all prerequisites are met, Copilot surfaces across the M365 application stack. The table below shows which apps gain Copilot capabilities and what those capabilities look like in practice — useful for setting accurate expectations with end users before the rollout.
| Application | What Copilot can do | Requires |
|---|---|---|
| Microsoft Word | Draft, rewrite, and summarise documents. Ask questions about the document content. Transform bullet points into prose and vice versa. | M365 Apps on Current / MEC channel |
| Microsoft Excel | Analyse data with natural language. Generate formula suggestions. Identify trends and create charts from a prompt. | M365 Apps on Current / MEC channel |
| Microsoft PowerPoint | Create a presentation from a prompt or an existing Word document. Add slides, redesign layouts, and summarise existing decks. | M365 Apps + OneDrive provisioned |
| Microsoft Outlook | Summarise email threads. Draft replies with the right tone. Coaching on message clarity. Summarise meeting invites. | Exchange Online primary mailbox |
| Microsoft Teams | Live meeting summaries with action items. Recap missed meetings. Answer questions about a meeting in progress. Summarise chat threads. | Teams Premium not required for meeting recap |
| Microsoft OneNote | Summarise notes. Draft content directly into a page. Ask questions about notebook content. | M365 Apps on Current / MEC channel |
| Microsoft 365 Chat (Copilot) | A single conversational interface across all work data — emails, files, Teams chats, calendar. "What did I miss this week?" or "Summarise the project status across all recent emails." | All prerequisites met; best results with OneDrive + Exchange Online |
| SharePoint (admin + user) | Admins: surface overshared sites via natural language queries. Users: find and summarise documents within a site. | SharePoint Online; SharePoint Advanced Management for admin Copilot |
Eligible base plans
Microsoft 365 Copilot is an add-on — it cannot exist without a qualifying base licence. The list of eligible plans is wide, covering the full range of Microsoft 365 Business and Enterprise subscriptions. Always verify current eligibility in Microsoft's licensing documentation, as this list can change with licence updates.
| Base plan | Copilot Business (≤ 300 users) | Microsoft 365 Copilot |
|---|---|---|
| Microsoft 365 Business Basic | ✓ Eligible | ✓ Eligible |
| Microsoft 365 Business Standard | ✓ Eligible | ✓ Eligible |
| Microsoft 365 Business Premium | ✓ Eligible | ✓ Eligible |
| Microsoft 365 Apps for Business | Verify in Microsoft licensing docs | ✓ Eligible |
| Microsoft 365 E3 | ✗ Not eligible | ✓ Eligible |
| Microsoft 365 E5 | ✗ Not eligible | ✓ Eligible |
| Office 365 E1 / E3 / E5 | ✗ Not eligible | ✓ Eligible |
| Microsoft 365 F1 / F3 (Frontline) | ✗ Not eligible | ✓ Eligible |
Assigning the licence in the Microsoft 365 admin centre
Once you have purchased Copilot seats, assigning them is done through the Microsoft 365 admin centre. The process takes under two minutes per user, but there are a couple of things worth knowing before you start to avoid common mistakes.
Navigate to admin.microsoft.com and sign in with a Global Admin or Licence Admin account.
Search for the user you want to assign the licence to, then click their name to open the user panel.
In the user panel, click the Licences and apps tab. You will see all licences currently assigned to this user.
Check the box next to Microsoft 365 Copilot (or Microsoft 365 Copilot for Business depending on your SKU). If the licence is greyed out, the user's base plan is not eligible — see the eligible base plans table above.
Click Save changes. The licence is active immediately, but propagation isn't always instant — allow time for each app to reflect the new licence. Outlook and Teams typically update first; Word, Excel, and PowerPoint may take longer.
For larger rollouts, use Billing → Licences → Microsoft 365 Copilot → Assign licences to assign to multiple users at once. You can also use group-based licensing in Entra ID for dynamic assignment at scale — assign the licence to a group, and any user added to that group is automatically licensed.
Technical prerequisites — the five things that silently block Copilot
A valid Copilot licence assigned to a user is necessary but not sufficient. There are five technical prerequisites that are routinely missed in pre-deployment reviews. Each one can prevent Copilot from working or degrade the experience in ways that are difficult to diagnose without knowing what to look for.
1 — Exchange Online primary mailbox (not hybrid, not on-premises)
Microsoft 365 Copilot requires the user's primary mailbox to be hosted in Exchange Online. Users in hybrid environments who still have their primary mailbox on-premises — a common situation in organisations that migrated gradually — will not get the full Copilot experience. Copilot in Outlook, meeting recaps, and email summarisation all depend on cloud mailbox access. Identify any hybrid users before deployment and plan for mailbox migration if Copilot is intended for them.
2 — Microsoft 365 Apps on Current Channel or Monthly Enterprise Channel
This is the most commonly missed prerequisite. Copilot features in Word, Excel, PowerPoint, Outlook, and OneNote require Microsoft 365 Apps to be running on either the Current Channel or Monthly Enterprise Channel. Organisations still using the Semi-Annual Enterprise Channel — a deliberate choice for stability in many SMB environments — will not receive Copilot features even after the licence is assigned. The failure is silent: the Copilot button simply does not appear. If your organisation uses Intune to manage update rings (covered in Part 3 of the Intune for SMBs series), review the update channel setting for all devices before the Copilot rollout.
3 — OneDrive account provisioned for each user
Several Copilot features — including Copilot's ability to surface and reference files across OneDrive and SharePoint — require that the user's OneDrive account is provisioned. Licensing a user for OneDrive does not automatically provision the account; it is provisioned the first time the user signs in to OneDrive or when it is force-provisioned by an admin via PowerShell. In organisations where users have never opened OneDrive, this step is easily missed. Verify that all Copilot target users have an active, provisioned OneDrive account before the rollout.
4 — User-based licensing (shared-device and device-based scenarios need validation)
Copilot is licensed per user, not per device. Shared-device and device-based Microsoft 365 Apps scenarios need specific validation before rollout — what works for standard user-based deployments may not translate directly to kiosk, frontline, or shared-workstation environments. If your organisation has any devices running Microsoft 365 Apps under a device-based licensing model, verify Copilot support for that configuration in Microsoft's current documentation before assigning licences and expecting the experience to work.
5 — Third-party cookies required for web app features
Copilot in Word Online, Excel Online, and PowerPoint Online requires third-party cookies to be permitted in the browser. This is an often-overlooked consequence of Edge hardening policies — a sensible Edge security configuration that blocks third-party cookies will silently break Copilot in browser-based Office apps. If your organisation deployed Edge hardening via Intune (as recommended in the Settings Catalog article), review the cookie policy setting and add a specific exception for Microsoft 365 and Copilot domains before rolling out.
Common failures after licence assignment
Most Copilot issues reported after deployment are not licence problems — they are configuration problems that were missed before the licence was assigned. This table covers the symptoms you are most likely to encounter, along with their cause and the fix.
| Symptom | Root cause | Fix |
|---|---|---|
| Copilot icon is missing in Word, Excel, or PowerPoint | Microsoft 365 Apps is on the Semi-Annual Channel update track, which does not receive Copilot features | Switch the device (or the Intune update ring) to Current Channel or Monthly Enterprise Channel and wait for the next update cycle |
| Copilot appears in some apps but not Outlook or Teams | Licence propagation delay — typically affects Outlook and Teams when assigned outside business hours | Allow time for propagation before investigating. If Copilot is still missing after a reasonable wait, remove and reassign the licence to force re-provisioning |
| "Copilot is not available for your account" error in Teams | Exchange Online mailbox is not provisioned, is a shared mailbox, or is still in an on-premises hybrid configuration | Verify the user has a cloud-only Exchange Online primary mailbox. Shared mailboxes and resource accounts do not qualify |
| Copilot gives generic, internet-based answers instead of work context | Work-grounded responses require the Microsoft 365 Copilot (paid) licence — the free Copilot Chat tier only uses web context | Confirm the user has the paid Copilot licence, not just Copilot Chat. Check under Active users → Licences and apps |
| Copilot cannot summarise meetings or access calendar context in Teams | Third-party cookies are blocked in the browser, preventing the authentication token exchange required for work-grounded context | Allow third-party cookies for *.microsoft.com and *.microsoftonline.com, or use the Teams desktop client instead of the web app |
| OneDrive Known Folder content is not being surfaced by Copilot | OneDrive sync client is not provisioned or the user account has never signed into OneDrive | Confirm OneDrive is provisioned and the sync client is running. Deploy Known Folder Move via Intune if not already in place |
| Copilot returns results from content the user should not see | Oversharing in SharePoint — Copilot respects existing permissions, so if content is broadly shared or sensitivity labels are missing, Copilot will surface it | Run the SharePoint oversharing report, apply sensitivity labels to restrict access, and review site permissions before enabling Copilot for additional users |
| Licence assigned successfully but user still sees "Get Copilot" upsell screen | Browser cache or app cache has not refreshed since the licence was applied | Ask the user to sign out and sign back in, or clear the browser cache. In the desktop apps, use File → Account → Sign out and sign back in |
Pre-purchase admin checklist
Run through this checklist before approving the Copilot licence purchase. Each item either blocks deployment or creates a poor user experience that reflects on the rollout. Fixing these after the licences are active is harder than fixing them before.
-
Confirm base licence eligibility for every target user Check each user's assigned base plan against the eligible plan list. In mixed-licence tenants, not every user may qualify. Use the Microsoft 365 admin centre → Users → Active users → filter by licence to audit quickly.
-
Identify hybrid users with on-premises mailboxes Run a mailbox location report to identify any users whose primary mailbox is still on-premises or in a hybrid configuration. These users need cloud mailbox migration before Copilot in Outlook will work.
-
Audit Microsoft 365 Apps update channel across all devices In Intune: Apps → Monitor → App install status, or use the Microsoft 365 Apps admin centre to check the active update channel per device. Any device on Semi-Annual Enterprise Channel must be moved to Monthly Enterprise Channel or Current Channel before Copilot activates.
-
Verify OneDrive is provisioned for all target users Use PowerShell with the SharePoint PnP module or Microsoft Graph to check OneDrive provisioning status. Force-provision any unprovisioned accounts before the Copilot rollout date.
-
Review shared-device and device-based Microsoft 365 Apps scenarios Review Microsoft 365 Apps deployment configuration in Intune or the Microsoft 365 admin centre. If any devices use shared-device or device-based licensing models, validate current Copilot support for those scenarios in Microsoft's licensing documentation before rollout.
-
Review Edge and browser cookie policies Check Edge hardening profiles in Intune for third-party cookie blocking settings. Add Microsoft 365 and Copilot service domains as exceptions if the policy blocks third-party cookies broadly. This prevents Copilot from silently failing in browser-based Office apps.
-
Audit SharePoint permissions for oversharing Copilot will surface content users already have access to — including content that was overshared and forgotten. Review site sharing settings, broad access links, and "everyone except external users" permissions before Copilot goes live. This is covered in depth in the SharePoint governance article.
-
Decide: Copilot Business or Microsoft 365 Copilot If your organisation has 300 or fewer users and the core work-grounded Copilot experience is what you need, Copilot Business at $21/user/month is the right starting point. If you anticipate significant agent-building or extensibility requirements, compare both SKUs against Microsoft's current licensing documentation before committing. Confirm the 300-user ceiling applies to your headcount with room for growth.
-
Plan the April 2026 communication if not yet done If Copilot Chat was visible in Office apps for your users and you are not purchasing the paid licence, communicate the change before users notice the button disappearing. A short message to affected users prevents unnecessary helpdesk tickets.