Microsoft 365 Copilot does not stand alone. The product requires a qualifying Microsoft 365 base license. The prerequisite drives both eligibility and the audit risk for customers running mixed Microsoft 365 estates.
Microsoft 365 Copilot looks like a 30 USD per user per month line item. In practice it is a Microsoft 365 base upgrade plus a 30 USD per user per month line item for any customer not already on a qualifying base. The buyer side that maps the prerequisite first prices the full conversation second.
The prerequisite map decides whether the Copilot pilot is a clean add to the existing estate or a multi line transformation that drags the M365 base upgrade through the same conversation.
Microsoft publishes a defined list of qualifying base SKUs for Microsoft 365 Copilot. Five SKUs qualify across enterprise and small business. Other SKUs, including Office 365 plans and standalone Microsoft cloud services, do not qualify.
The enterprise productivity baseline. Includes Office apps, Exchange Online, SharePoint, Teams, OneDrive, Windows 11 Enterprise, and core security. The most common base SKU for Copilot rollouts in 2026.
E3 plus Microsoft Defender, Purview compliance, Power BI Pro, and Teams Phone. Customers on E5 already pay a premium and the Copilot add carries cleanly. The cleanest base for the largest enterprises.
The frontline worker SKU. Includes Office Online (no desktop apps), Exchange Online, Teams, OneDrive, and a subset of M365 productivity. Copilot on F3 is functional but constrained by the missing desktop app experience.
The small and mid market SKUs capped at 300 users. Both qualify for Copilot. Business Standard is broadly E3 equivalent. Business Premium adds Entra ID P1, Defender for Business, and Intune.
| SKU | Qualifies for Copilot | Typical user segment | Notes |
|---|---|---|---|
| Microsoft 365 E3 | Yes | Information workers | Default enterprise base |
| Microsoft 365 E5 | Yes | Information workers (premium) | Best Copilot fit, premium price |
| Microsoft 365 F3 | Yes | Frontline workers | Functional but constrained |
| Microsoft 365 F1 | No | Shared device frontline | License only SKU |
| Microsoft 365 Business Standard | Yes | SMB (300 user cap) | Below 300 users only |
| Microsoft 365 Business Premium | Yes | SMB (300 user cap) | Below 300 users only |
| Office 365 E1, E3, E5 | No | Mixed estates | Upgrade to M365 required |
The largest Copilot prerequisite trap is the Office 365 estate. Many enterprises run Office 365 E3 or E5 from prior years. Office 365 does not qualify for Copilot. Customers must upgrade to Microsoft 365 first, then add Copilot on top.
Office 365 is the productivity suite. Microsoft 365 wraps Office 365 with Windows 11 Enterprise, Enterprise Mobility plus Security, and core endpoint management. The wrapper is the qualifying boundary for Copilot eligibility.
Office 365 E3 to Microsoft 365 E3 typically adds roughly 9 USD per user per month at list. Office 365 E5 to Microsoft 365 E5 typically adds roughly 16 USD per user per month at list. The upgrade compounds with Copilot pricing.
The Copilot conversation forces the M365 base upgrade conversation for any Office 365 customer. The upgrade enlarges the EA commitment band before the Copilot line is added. The double uplift is the renewal risk that mapping mitigates.
Most large enterprises run mixed Office 365 and Microsoft 365 populations. Some users on E3, some on E5, some on O365 legacy plans. The prerequisite map identifies which populations need the upgrade before Copilot can be added.
Frontline workers carry different licensing realities. The F SKU family was built for shared device and limited desktop scenarios. Copilot on frontline workers is functional in some cases but constrained in others. Mapping the right SKU per worker segment is the discipline.
F1 is the license only SKU primarily used for shared device kiosks, signage, and identity for non productivity users. F1 does not qualify for Copilot. Workers needing Copilot must move to F3 or higher.
F3 includes Office Online (no desktop), Exchange Online, Teams, and OneDrive. Copilot on F3 works in the browser experience but loses value where workers depend on desktop Outlook or full Teams clients.
Some frontline scenarios overlap with information worker patterns. A field services supervisor on F3 plus Copilot may need to move to E3 plus Copilot to capture the full document and email experience. The map drives the SKU decision.
The Copilot eligible population is rarely the full workforce. The mapping exercise identifies which users have qualifying base SKUs today and which need an upgrade. The output drives the Copilot pilot scope and the EA renewal proposal.
Pull the active license assignment report from the Microsoft 365 admin centre. Document the count of users on E3, E5, F1, F3, Business Standard, Business Premium, and any Office 365 plans.
Align the license map to job role and business function. Information workers, frontline supervisors, frontline operators, executives, and contractors each carry different Copilot eligibility considerations.
For any user segment on Office 365 or unqualified plans, quantify the upgrade cost to Microsoft 365 E3 or E5. The upgrade plus the Copilot per user line is the true Copilot deployment cost.
Define a Copilot pilot scope against the qualifying base population. Avoid scoping a pilot that drags an Office 365 upgrade across an unrelated workforce segment. The pilot should be value driven, not prerequisite driven.
Four buyer side moves protect the Copilot deployment from the prerequisite trap. The buyer side that runs all four captures the discount band that uncritical adopters concede to Microsoft sales.
The prerequisite map runs before Microsoft puts a Copilot proposal on the table. The map identifies upgrade exposure and forces the conversation to include the base license economics.
Customers on Office 365 face a base upgrade before Copilot is even on the table. Pre committing the upgrade at the EA signing captures the discount band on both lines. Staging the upgrade later concedes the band.
Microsoft sales will scope a Copilot pilot across F3 frontline populations to maximize user count. Most F3 deployments rarely capture full Copilot value. The pilot should target qualifying information workers.
Copilot list pricing has risen since launch. A multi year EA term locks the Copilot price for the full term. The same lock applies to the M365 base upgrade. Both prices protected for three years.
The checklist takes the IT and procurement functions from a Copilot interest conversation to a scoped, eligibility cleared proposal. The earlier the prerequisite mapping runs, the wider the option set on the day Microsoft puts the proposal on the table.
Microsoft 365 E3, E5, F3, Business Standard, or Business Premium qualifies. Office 365 plans without the Microsoft 365 wrapper do not qualify. Standalone Exchange or SharePoint users cannot add Copilot.
No. Office 365 E3 does not qualify. The customer must upgrade to Microsoft 365 E3 first. The upgrade carries a meaningful base license uplift before Copilot can be added.
F3 frontline users can add Copilot but the experience is constrained. Workers without Outlook desktop or Teams full client see limited Copilot value. The frontline addition rarely passes business case scrutiny.
Microsoft 365 Business Standard and Business Premium qualify (capped at 300 users). Microsoft 365 Apps for Business standalone does not qualify. The user needs the broader Microsoft 365 wrapper.
F1 is a license only SKU primarily used for shared device scenarios. F1 alone does not qualify for Copilot. Most frontline organizations should map F3 plus role specific Copilot to suitable workforce subsets.
Office 365 E3 to Microsoft 365 E3 typically adds roughly 9 USD per user per month. Office 365 E5 to Microsoft 365 E5 typically adds roughly 16 USD per user per month. The upgrade compounds with Copilot pricing.
Yes. Copilot adds as a new EA line item or via the Microsoft Customer Agreement. Mid term additions price at list. The buyer side prefers to negotiate Copilot at EA renewal to capture the discount band.
Redress runs Copilot scoping inside the broader Microsoft EA renewal motion. The work covers prerequisite mapping, eligible population sizing, base upgrade economics, and the multi year Copilot price lock.
Redress runs this practice inside the Vendor Shield subscription, the Renewal Program, and the Software Spend Assessment.
Read the related Microsoft Copilot licensing 2026 article, the Microsoft EA renewals article, the Microsoft services, the Microsoft knowledge hub, the benchmarking service, and the Benchmark Program.
Microsoft Enterprise Agreement renewal motion, true up exposure, Copilot bundling, and the buyer side discount band moves.
Independent. Written for CIOs, CFOs, and procurement leaders. No vendor partner affiliation.
Open the playbook in your browser. Corporate email only.
Open the Paper →Copilot looks like a 30 dollar per user line. It is actually a Microsoft 365 base upgrade plus a 30 dollar per user line. The buyer side that maps the prerequisite first prices the full conversation second.
We run Copilot scoping decisions inside the broader Microsoft EA renewal motion. Median 22 percent recovery on the consolidated renewal when the prerequisite map runs before the Copilot proposal.
Cost benchmarks, license rightsizing patterns, and the negotiation moves that worked. Written for buyer side teams running active vendor decisions.
Once a month. Audit patterns, renewal benchmarks, vendor commercial signals across Oracle, Microsoft, SAP, Salesforce, IBM, Broadcom, AWS, Google Cloud, ServiceNow, Workday, Cisco, and the GenAI vendors. No follow up sales pressure.
Free providers (Gmail, Yahoo, Outlook) cannot subscribe. Work email only. Unsubscribe in one click.
