Copilot requirements, eligibility is a per group decision
Microsoft 365 Copilot only runs on top of an eligible base license, and 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. In our scoping reviews the prerequisite step was where projects slipped, not the price negotiation.
Prepared by Redress Compliance · August 7, 2026 · Microsoft advisory. Based on 25 to 35 Copilot scoping reviews run 2024 to 2025.
Executive summary
The eligibility gap is bigger than buyers assume. Between 10 and 30 percent of users in a typical enterprise sat on a base license that did not qualify for Copilot, a 20 percent median, mostly frontline and deskless staff on F1 and F3 plans that do not qualify on their own.
The gap was found after the Copilot deal was signed in most reviews, which is exactly the wrong order.
The step up cost is the hidden half of the business case. Stepping ineligible users up to a qualifying base added 10 to 25 percent to the Copilot business case, an 18 percent median, and was usually discovered late.
The prerequisite math, not the Copilot fee, decides the real rollout cost, and it prices per user group before purchase or surprises the budget after it.
The Office 365 trap runs the other way. Tenants still on Office 365 rather than Microsoft 365 assumed they were blocked from Copilot, which was true at launch and is not now: Office 365 E3 and E5 became eligible bases after launch, removing a costly assumed upgrade.
The eligible core: Microsoft 365 E3 and E5, Business Standard and Premium, and Office 365 E3 and E5, with the list confirmed against live documentation because it has changed before.
The license is necessary and not sufficient. Copilot also needs a Microsoft Entra ID account and provisioned OneDrive per user, because it stores and reasons over content through those services, plus current Microsoft 365 apps including a supported Outlook and Teams.
A missing OneDrive blocks core features, and old clients limit what Copilot does inside each app: the readiness check is per user, alongside the eligibility map.
The eligibility map, base by base
| Base license | Copilot eligible | The note |
|---|---|---|
| Microsoft 365 E3 and E5 | Yes | The core enterprise bases |
| Business Standard and Premium | Yes | Small and mid sized tenants |
| Office 365 E3 and E5 | Yes | Added after launch: the trap that runs backward |
| Microsoft 365 F1, F3, Office 365 F3 | Not on their own | Frontline plans need a step up decision |
| Exchange Online standalone | No | Not a qualifying base |
Copilot is an add on by design. It works inside the Microsoft 365 apps a user already has, needing the base license for the apps, the identity, and the content it reasons over, which is why no standalone seat exists and why the company level question, are we eligible, is the wrong one.
Eligibility is a yes or no per user group, and mapping every population to its base before purchase is where the prerequisite cost becomes visible.
The three scoping moves, before any purchase
- Map eligibility per user: the current base license for every user, tagged eligible or not, because the gap is the population needing a decision.
- Decide group by group: eligible today and ready; role justifies the step up to a qualifying base; or out of scope for this phase, which is a legitimate answer for frontline populations.
- Price the gap into the case: the step up cost for every group moving, the 10 to 25 percent that arrives late otherwise, weighed per group against what Copilot is worth to that role.
The Microsoft EA renewal playbook
The negotiation the eligibility map feeds: the persona mix, the step up economics, and the Copilot attach worked on a representative estate.
Get the white paper →Beyond the license, the readiness floor
The technical prerequisites are unglamorous and blocking: a Microsoft Entra ID account per user, OneDrive provisioned because Copilot stores and reasons over user content through it.
And current Microsoft 365 apps with a supported Outlook and Teams, since old clients limit what Copilot does inside each app.
The readiness check runs beside the eligibility map, per user, and feeds the same rollout sequence.
The step up decision itself is the E3 versus E5 versus F3 framework applied with Copilot in the equation, and the seat licensing detail above the base, including what the Copilot fee actually buys, sits in the Copilot licensing guide.
- Percentile standing for your exact deal size and industry, from real closed transactions
- Scenario simulation before the call: test alternative terms and see the financial impact of each
- A negotiation playbook, talking points, and a two page executive brief on day one
What we saw across scoping reviews, 2024 to 2025
Across roughly 25 to 35 Microsoft 365 Copilot scoping reviews run between 2024 and 2025, the prerequisite step was where projects slipped, not the price negotiation:
Users below a qualifying base, found after the Copilot deal was signed in most reviews.
What moving ineligible users to a qualifying base added to the business case, late.
The eligibility work connects to the economics on both sides: the rollout that maps groups first avoids buying Copilot seats for users who cannot activate them, and the estate that runs the placement discipline anyway, the lowest qualifying tier per role, holds the base cost the step ups build on.
The full cost picture above the prerequisites, the idle seats and the per active user multiple, is worked in the Copilot true cost analysis, and the license optimizer runs the eligibility and placement map from a usage export in minutes.
Your first five moves
- Pull the base license for every user and tag eligibility, because the gap population is the real cost of the rollout.
- Decide per group, not per company: eligible, step up justified, or out of scope, with frontline populations decided deliberately.
- Price the step up into the business case now, the 10 to 25 percent that otherwise arrives after signature.
- Check the Office 365 assumption, because E3 and E5 tenants on the older paper are eligible and many still assume otherwise.
- Verify Entra ID, OneDrive, and current apps per user before seats are assigned. The Microsoft practice runs the scoping with you.
Frequently asked questions
What licenses are required for Microsoft 365 Copilot?
An eligible base license per user, because Copilot is an add on with no standalone seat: Microsoft 365 E3 and E5, Business Standard and Premium, and Office 365 E3 and E5 qualify, while frontline F1 and F3 plans and standalone Exchange Online do not.
Confirm against live documentation, since the eligible list has changed before.
Can Office 365 tenants use Copilot?
Yes: Office 365 E3 and E5 became eligible bases after the initial launch, removing the assumed Microsoft 365 upgrade many tenants still budget for.
The early blocker is gone, and tenants on those plans add Copilot directly, which is worth checking before any migration is priced into the Copilot case.
Do frontline workers qualify for Copilot?
Not on F1 or F3 alone: frontline plans need a step up to a qualifying base, which makes frontline heavy estates a deliberate decision, which workers move up for Copilot and which stay out of scope.
In our reviews frontline and deskless staff were most of the 10 to 30 percent sitting below an eligible base.
What does Copilot need beyond the license?
A Microsoft Entra ID account and provisioned OneDrive per user, because Copilot stores and reasons over content through those services, plus current Microsoft 365 apps including a supported Outlook and Teams.
A missing OneDrive blocks core features and old clients limit in app functionality, so the readiness check runs per user beside the eligibility map.
How much does Copilot eligibility add to the cost?
Stepping ineligible users up to a qualifying base added 10 to 25 percent to the business case, an 18 percent median, and was usually discovered after the deal was signed.
The prerequisite math, not the Copilot fee, decides the real rollout cost, which is why the eligibility map prices before purchase.
How should a Copilot rollout be scoped?
Per user group: map every population to its base license, tag eligibility, decide group by group whether the step up is justified or the group is out of scope, and price the gap into the case before signature.
Eligibility is not a company level yes or no, and treating it as a footnote is how budgets slip.
