Microsoft / Copilot
Copilot has prerequisites. Map them first.
Microsoft 365 Copilot only runs on top of an eligible base license, and the eligible list has widened since launch. Map the prerequisites before you buy a single seat.
Microsoft 365 Copilot only runs on top of an eligible base license, and the eligible list has widened since launch. Map the prerequisites before you buy a single seat.
Microsoft 365 Copilot only runs on top of an eligible base license, and the eligible list has widened since launch. This guide maps which Microsoft 365 and Office 365 SKUs qualify, the eligibility traps that catch buyers, and the scoping moves that stop a project stalling on day one.
Microsoft 365 Copilot is an add on. Every Copilot user needs an eligible Microsoft 365 or Office 365 base license before Copilot can be assigned. There is no standalone Copilot seat.
That single rule decides the real cost of a rollout, because the gap is the users who do not yet sit on a qualifying base.
Copilot works inside the Microsoft 365 apps a user already has. It needs the base license to provide the apps, the identity, and the content it reasons over. Microsoft sets the eligible bases in the Microsoft 365 Copilot requirements.
The core qualifying bases are Microsoft 365 E3 and E5, Business Standard and Business Premium, and Office 365 E3 and E5. Frontline plans do not qualify on their own. Confirm against the live Microsoft 365 Copilot documentation, since the list has changed before.
Microsoft 365 Copilot base license eligibility
| Base license | Copilot eligible | Note |
|---|---|---|
| Microsoft 365 E3 and E5 | Yes | Core enterprise bases |
| Business Standard and Premium | Yes | Small and mid sized tenants |
| Office 365 E3 and E5 | Yes | Added after launch |
| Microsoft 365 F1, F3, Office 365 F3 | Not on their own | Frontline plans need a step up |
| Exchange Online standalone | No | Not a qualifying base |
Many tenants still run Office 365 rather than Microsoft 365 and assume they are blocked from Copilot. That was true early on. It is not true now.
Microsoft made Office 365 E3 and E5 eligible bases after the initial launch. Tenants on those plans can add Copilot without first moving to Microsoft 365, which removes a costly assumed upgrade.
Frontline plans such as F1 and F3 do not qualify on their own. A frontline heavy estate needs a deliberate decision on which workers move to a qualifying base and which do not get Copilot at all.
An eligible base is necessary but not sufficient. Copilot also needs the identity, storage, and apps that let it work across Microsoft 365.
Each Copilot user needs a Microsoft Entra ID account and OneDrive provisioned. Copilot stores and reasons over user content through these services, so a missing OneDrive blocks core features.
Copilot expects current Microsoft 365 apps, including a supported Outlook and Teams. Old or unsupported clients limit what Copilot can do inside each app.
The common advice is that Copilot eligibility is simple because most enterprises are on E3 or E5 already. We disagree. In most scoping reviews we ran, a meaningful slice of the workforce, often frontline and deskless staff, sat on plans that do not qualify on their own, and that gap was found after the Copilot deal was signed. The buyer side move is to map eligibility per user group before any purchase, price the step up for ineligible users, and decide group by group whether Copilot is worth the base upgrade. Treating eligibility as a footnote is how budgets slip.
Source: Redress Compliance advisory engagement file, 2024 to 2025.
Copilot eligibility is not a yes or no for the company. It is a yes or no for each user group. Map it before you sign, not after.
Three moves stop a Copilot project stalling on prerequisites.
Pull the current base license for every user and tag each as eligible or not. The gap is the population that needs a decision.
Treat eligibility as a per group question. Some groups justify the base upgrade for Copilot, others do not need Copilot at all.
Add the base upgrade cost for the upgrade group to the Copilot business case. The prerequisite cost, not the Copilot fee, is what most early cases miss. Cross check the SKU prices on the Microsoft 365 plans and pricing page, and read the Microsoft product terms for the assignment rules.
You need an eligible Microsoft 365 or Office 365 base license per user. Copilot is an add on and cannot be assigned without a qualifying base.
Yes. Office 365 E3 and E5 became eligible bases after launch. Tenants still on Office 365 are no longer blocked.
Frontline plans such as F1 and F3 do not qualify on their own. Frontline users need a step up to a qualifying base before Copilot can be assigned.
Yes. Copilot needs a Microsoft Entra ID account, OneDrive, and supported Outlook and Teams clients to work across the Microsoft 365 apps.
Often yes. Stepping ineligible users up to a qualifying base adds to the Copilot business case and should be priced before purchase.
Microsoft 365 E3, E5, Business Standard, Business Premium, and Office 365 E3 and E5 are the core qualifying bases. Microsoft updates the list, so confirm against the current requirements.
Assuming every user can take Copilot. Whole populations, usually frontline staff, often sit below the eligible base and are found late.
No. Redress Compliance is independent and 100 percent buyer side. We advise on the scoping and negotiation and never resell Microsoft products.
Microsoft renewal moves, the EA framework, the M365 SKU framework, the Copilot framework, and the buyer side moves across the full Microsoft estate.
Used across more than five hundred enterprise engagements. Independent. Buyer side. Built for procurement leaders running the next renewal cycle.
The Copilot license is the easy part. The prerequisite base, the identity, and the data are where the real scoping work lives.
