Who actually needs a Microsoft Copilot licence?

You’re right to pause before spraying seats. Licence decisions feel urgent when finance has a quote open, but the quiet cost is shelfware and a rollout that outruns your permissions hygiene.

Here’s what’s happening. Microsoft draws a clear line between Copilot Chat (included with many eligible Microsoft 365 / Office 365 base licences — primarily web-grounded unless work content is supplied or a metered agent is in play) and the Microsoft Copilot add-on that unlocks work-grounded experiences across apps and deeper Graph context. Users also need an Entra ID account, and for the full work-grounded product the primary mailbox should be Exchange Online. SKUs and product names move; check Licence options for Microsoft Copilot and the minimum-requirements pages for your tenant’s current list.

This is really First Law thinking applied to procurement: don’t pour budget into a programme until you can see how value gets out — and Second Law for the AI register: a seat without a named owner and benefit case barely “exists” as a controlled asset.

You’ve got a few practical options:

1. Map roles to Chat vs add-on. Keep Chat as the organisational baseline for eligible staff. Reserve paid Copilot seats for cohorts with a frozen value case (knowledge work that lives in mail, files, meetings). Simple; honest about who needs Graph grounding.
2. Pilot a named cohort first. Security and GRC clear Wave 0 fences; Adoption coaches one or two teams; FinOps watches dormant seats. Moderate effort; buys evidence before renewal theatre.
3. Spray everyone with E3/E5. Fast politically. The downside is overshare amplification at scale, dormant seats, and a board story you can’t defend. Advanced only if Steady already holds — which is rare.

The caution: Agent and in-app experiences often expect the Copilot licence; Office 365 alone is not a free pass to every agent. Eligibility differs for education, government, and commercial. Use Microsoft’s Copilot licence diagnostics in the admin centre when a user “should” see features and doesn’t.

I’d suggest treating Chat as the wide floor and paid seats as a Wave 0–gated portfolio: owner, cohort, benefit metric, reclaim rule. Steady before scale beats a single big PO.

You’re asking the right question — and you’ll have a calmer renewal when every paid seat has a job.

DIGITAL SKILL WORKS LTD / 12 PANES · You ask, we answer