Microsoft Copilot Licensing Guide 2026: Pricing, SKUs, Prerequisites and Negotiation Strategy

The Microsoft 365 SKU Stack in 2026: E1 Through E7

The first thing every enterprise buyer needs to understand is that the Microsoft 365 SKU stack has changed fundamentally in 2026. The stack now runs E1 → E3 → E5 → E7, with E7 sitting above E5 as the new top-tier enterprise licence. If your account team, broker, or internal IT team is still describing E5 as "the most comprehensive" Microsoft 365 plan, they are operating with outdated information.

Microsoft announced E7 in March 2026, with availability beginning in May 2026. At a list price of $99 per user per month, E7 is not merely E5 with Copilot bolted on. It is a bundled suite that packages three previously separate commercial products: Microsoft 365 E5 ($57/user/month), Microsoft 365 Copilot ($30/user/month), and the new Agent 365 product ($15/user/month) which handles AI agent orchestration and identity governance via Entra Suite. The Entra identity tools ($12/user/month as a standalone) are also included.

Understanding where you sit in this stack — and where Microsoft wants you to go — is the foundation of any 2026 Copilot licensing decision.

E1: The Collaboration Baseline

Microsoft 365 E1 provides cloud-based productivity applications, Teams, Exchange Online, and SharePoint at approximately $10.50/user/month. E1 is a qualifying licence for the Copilot add-on, meaning you can deploy Copilot on an E1 estate — but you will encounter significant capability limitations. Many Copilot features that rely on E3 or E5 data governance tooling (Purview labels, sensitivity classifications, DLP policies) will not function as designed without the corresponding base licence features. E1 Copilot deployments typically produce the lowest adoption rates and the highest support burden.

E3: The Most Common Starting Point

Microsoft 365 E3 at approximately $36/user/month is the most widely deployed enterprise licence tier. It includes full Office application entitlements, compliance fundamentals via Purview (E3 boundary), Windows 10/11 Enterprise, and basic information protection. E3 is a full qualifying licence for the $30 Copilot add-on. The Copilot E3 guide from Microsoft covers a dedicated deployment path for E3 customers, recognising that the majority of enterprise Copilot rollouts begin from an E3 baseline. From a total cost perspective, E3 plus Copilot = approximately $66/user/month before EA discounting.

E5: The Security and Compliance Anchor

Microsoft 365 E5 at approximately $57/user/month adds advanced security (Defender XDR, Sentinel SIEM/SOAR integration), advanced compliance (Purview eDiscovery Premium, Communication Compliance, Insider Risk Management), and Microsoft Entra P2 for identity protection. E5 is the most feature-complete base licence for a Copilot deployment — the data governance, sensitivity labelling, and information protection capabilities of E5 enable Copilot to operate safely across sensitive content. E5 plus Copilot = approximately $87/user/month before EA discounting. Microsoft field teams are currently under active instruction to convert E5 customers to E7 at renewal rather than renewing E5 plus Copilot add-on separately.

E7: The New Top SKU — What Is Actually Included

Microsoft 365 E7 at $99/user/month bundles the following components that would cost approximately $114/user/month if purchased separately: Microsoft 365 E5 ($57), Microsoft 365 Copilot ($30), Agent 365 for AI agent orchestration ($15), and Entra Suite for identity governance ($12). The headline E7 pitch is a 13% saving versus itemised components at list price — before EA negotiation on either path.

E7 includes advanced capabilities that were previously sold only as premium add-ons: Microsoft Copilot Cowork (Microsoft's agentic collaboration product built in partnership with Anthropic), Work IQ (Microsoft's AI productivity intelligence layer), advanced Defender and Purview capabilities beyond E5, and Intune Suite for endpoint management. For organisations that were planning to acquire E5, Copilot, and Entra Suite separately, E7 can represent genuine consolidation value — provided the agent management and advanced Intune capabilities are actually needed and will be activated.

Microsoft Copilot Add-On Licensing: The $30 Model Explained

For organisations not ready to move to E7, the $30 per user per month Microsoft 365 Copilot add-on remains the primary acquisition path. Understanding how this model works — and where it creates hidden cost — is essential for accurate total cost of ownership modelling.

Qualifying Base Licences

The $30 Copilot add-on requires one of the following qualifying base licences: Microsoft 365 E1, E3, E5, F1, F3, Business Basic, Business Standard, Business Premium, Microsoft 365 Apps for Enterprise, or Office 365 E1, E3, or E5. The requirement for a qualifying base licence is non-negotiable — there is no standalone Copilot licence without a base subscription. This structure means the true cost of Copilot is always the base licence cost plus $30, making the TCO calculation licence-tier dependent.

Technical Prerequisites Beyond the Base Licence

Acquiring the Copilot licence is only the first step. Deployment requires: Exchange Online as the primary mailbox platform (Copilot uses mailbox metadata for summarisation and drafting), a Microsoft Entra ID account for each user, current versions of the Microsoft 365 Apps (not Office 2016 or 2019 perpetual), and a compliant data governance configuration. Organisations running Exchange on-premises or hybrid configurations face additional migration prerequisites before Copilot can be fully activated.

Many enterprises discover these prerequisites late — after licences have been committed in an EA. The result is a wave of shelfware: Copilot licences activated on paper but not deployed in practice because the underlying infrastructure or compliance posture is not ready.

Copilot Chat: The Free Tier Distinction

Microsoft has expanded Copilot Chat — the conversational AI layer integrated into Teams, Edge, and the Microsoft 365 apps — to most Microsoft 365 subscription tiers at no additional charge. This is distinct from the full Microsoft 365 Copilot ($30 add-on), which provides AI-powered features embedded directly into Word, Excel, PowerPoint, Outlook, and Teams across the entire Microsoft Graph. Copilot Chat provides generalist web-grounded and document-grounded chat. The full Copilot provides AI-assisted drafting, summarisation, analysis, and meeting intelligence tightly integrated into the Microsoft 365 application suite. Buyers who conflate the two tiers are at risk of either over-buying (acquiring full Copilot when Copilot Chat meets their use cases) or being misled by Microsoft field teams positioning Copilot Chat as a free proof of concept for full Copilot upsell.

Copilot Studio: Credit-Based Pricing and TCO Implications

Microsoft Copilot Studio is the low-code/no-code platform for building custom AI agents and extending Copilot capabilities with enterprise-specific knowledge sources and workflows. Its pricing model is entirely separate from the Copilot add-on and operates on a Copilot Credits system that introduces consumption-based cost volatility into otherwise predictable licensing structures.

How Copilot Credits Work

Copilot Studio licences are purchased as capacity packs of 25,000 Copilot Credits for $200 per pack per month. Credits are consumed when agents respond to queries or execute actions — the number of credits consumed per interaction varies based on the complexity of the agent, the knowledge sources it uses, and the actions it performs. A simple FAQ agent consuming basic SharePoint content might use one or two credits per interaction. An agent that retrieves data from multiple sources, calls external APIs, and triggers workflows in downstream systems can consume significantly more per session.

The consumption variability is intentional on Microsoft's part. It creates a pricing structure where enterprise AI automation costs are difficult to forecast from a contractual standpoint and where usage spikes — from a successful agent deployment driving high user adoption — translate directly to unexpected cost. Organisations that deploy Copilot Studio agents at scale without a credit consumption baseline will encounter budget surprises in their Azure billing at the end of each month.

Pay-as-You-Go vs. Pre-Purchase

Microsoft offers three acquisition models for Copilot Studio capacity: the standard pre-purchase pack ($200/pack/month via Enterprise Agreement), a pay-as-you-go meter through Azure (no upfront commitment, credits billed at consumption), and a pre-purchase commit unit model (prepaid credits at a fixed amount, suited for organisations with predictable agent usage volumes). For EA customers, the pre-purchase model is typically included in the agreement structure but must be explicitly sized — the number of packs committed should be based on agent deployment plans and estimated interaction volumes, not arbitrary round numbers.

Copilot Studio vs. Agent 365 in E7

One of the most commercially significant questions in 2026 Copilot licensing is whether E7's included Agent 365 component replaces the need for Copilot Studio. It does not, but the two products address adjacent use cases. Agent 365 (included in E7) provides AI agent orchestration and management — tracking and governing agents deployed across the enterprise, including agents built in Copilot Studio. Copilot Studio itself is the development and deployment platform for those agents, and still requires separate capacity licensing. Buyers who assume E7 eliminates Copilot Studio costs will be surprised when their agent development programme generates consumption-based billing that falls outside their E7 entitlement.

Licensing Paths: E7 vs. Add-On vs. Selective Deployment

There are three primary licensing paths for Microsoft Copilot in 2026, and the correct choice depends on your current estate, renewal timeline, and deployment ambition. Each path has a different financial profile and a different negotiation posture.

Path 1: Upgrade to E7 at EA Renewal

For organisations currently on E5 with Copilot add-on or planning a full E5 deployment plus Copilot, the E7 bundle at $99/user/month can represent meaningful unit economics — approximately $15/user/month cheaper than E5 ($57) + Copilot ($30) + Entra Suite ($12) purchased separately at list price. The EA negotiation case for E7 centres on the Agent 365 inclusion: if your organisation intends to build and govern AI agents (which Microsoft's own roadmap suggests will be standard enterprise practice within 24 months), pre-purchasing that capacity at the E7 unit rate locks in a lower cost basis before Agent 365 moves to mainstream pricing.

The risk of Path 1: you are paying for Agent 365 and advanced Intune Suite features from day one of your new EA term, regardless of whether your organisation has the maturity, roadmap, or IT capacity to activate them. For a 5,000-user organisation on E5 today, upgrading to E7 adds approximately $450,000/year in incremental annual spend at list price before discounts. This is not a small decision.

Path 2: E3 or E5 Plus Copilot Add-On (Selective Deployment)

The add-on model remains the right path for organisations that: have a defined initial Copilot user population (not full enterprise deployment), are on E3 and do not need E5 security/compliance capabilities, want to validate ROI before committing to enterprise-wide AI licensing, or are mid-EA with existing E3/E5 commitment and cannot justify a full renegotiation.

Under this model, Copilot licences can be purchased for a subset of users — there is no minimum user percentage requirement that forces full-tenant deployment. Starting with 100 to 500 users in high-value personas (knowledge workers, legal, finance, executives) produces measurable ROI data that justifies incremental expansion. The EA discount on the Copilot add-on SKU is typically 10 to 15%, making the effective per-user cost approximately $25.50 to $27.00/user/month in a well-negotiated EA.

Path 3: NCE Monthly or Annual Commitment (Non-EA)

For organisations outside the Enterprise Agreement framework — typically below the 300-seat EA threshold or on Microsoft Customer Agreement (MCA) — the New Commerce Experience (NCE) provides two options: monthly commitment at list price ($30/user/month, no discount) or annual commitment with up to 5% discount. The NCE annual path is structurally less favourable than an EA negotiation but provides flexibility for organisations that need to test Copilot before locking in a three-year EA commitment. Microsoft's preferred commercial motion is increasingly MCA over EA — primarily because buyer leverage is lower in the MCA structure, where pricing is closer to list and individual negotiation levers are limited.

Negotiation Strategy: How to Buy Copilot Without Overpaying

Microsoft's field teams are under significant commercial pressure to grow Copilot attach rates in 2026. This creates real negotiation leverage for buyers — but only if you understand how to use it. The following principles apply whether you are negotiating a new EA, renewing an existing one, or considering an MCA.

Know Microsoft's Fiscal Calendar

Microsoft's fiscal year ends June 30. The Q4 pressure window — April 1 to June 30 — is when Microsoft's account teams have the highest incentive to close deals and offer incremental discounts to hit their fiscal year targets. If your EA renewal falls outside Q4, consider whether you can align a Copilot add-on conversation to Q4 timing even within an existing agreement. End-of-quarter pressure is your single most powerful negotiating variable.

Use the E7 Upsell As Negotiation Leverage

If Microsoft is pushing you toward E7, that is leverage — not a directive. The fact that Microsoft wants you on E7 means they have commercial incentive to make the transition attractive. Negotiating tactics that work in this context: ask for extended True-Up periods that allow you to delay E7 deployment costs while keeping the committed price, request inclusion of Copilot Studio capacity packs as part of the E7 bundle value, demand extended pilots before full-tenant commitment, and push for floor pricing that locks E7 unit rates across your full three-year term even if Microsoft increases list price mid-term.

Discount Reality in 2026

Standard EA discounts on Microsoft 365 products currently run at 10 to 20% off list price. The era of 15 to 25% historical discounts that characterised EA negotiations before 2023 is over. Microsoft has systematically reduced the discount ceiling as its product portfolio has shifted from primarily Office productivity (highly commoditised, price-competitive) to AI and security (positioned as differentiated and premium). Copilot add-on SKUs typically attract lower discounts than base M365 SKUs — expect 10 to 15% on Copilot versus 15 to 20% on E3 or E5 in a well-structured negotiation. E7, as a new SKU, is being heavily protected by Microsoft field teams; initial E7 discount offers are typically in the 8 to 12% range.

Right-Sizing: The Shelfware Risk

The most expensive Copilot licensing mistake is over-provisioning. Enterprises that commit to full-tenant Copilot deployment at EA renewal without a validated pilot programme frequently end up with 40 to 70% of licences unused in the first 12 months. The drivers of Copilot shelfware are well-documented: inadequate change management, insufficient training investment, prerequisite infrastructure gaps (hybrid Exchange, legacy SharePoint sites with poor metadata quality), and business unit resistance to workflow change. A selective deployment model — starting with 10 to 20% of the user base in defined high-impact personas — produces better adoption metrics and a stronger commercial case for incremental expansion than a forced full-tenant rollout.

The True-Up Mechanism and Copilot

The EA True-Up occurs annually on the anniversary of the EA start date and requires the customer to report and pay for any incremental licence growth since the previous True-Up. For Copilot, the True-Up creates a specific commercial dynamic: organisations that deploy Copilot beyond their initial committed quantity during the EA term must report and pay True-Up costs at the then-current EA unit price — which may be different from the price locked in at EA signature if Microsoft has adjusted pricing in the interim.

True-Up timing matters for Copilot pilots. If you begin a Copilot pilot three months before your annual True-Up date, any user additions made during the pilot period will be captured at True-Up. Planning your pilot start date relative to your True-Up anniversary — and ensuring your pilot population is within your committed quantity — avoids unexpected True-Up costs that undermine pilot ROI calculations.

Copilot Licensing for Frontline Workers: F1 and F3

Microsoft 365 F1 ($2.25/user/month) and F3 ($8/user/month) are qualifying base licences for the Copilot add-on, but the Copilot experience on these SKUs is substantially limited. Frontline worker licences have restricted device entitlements (no full desktop Office applications on F1), limited SharePoint capabilities, and simplified Teams functionality. The standard $30 Copilot add-on on an F1 licence produces a low-value deployment in most scenarios. Microsoft offers a Copilot for Frontline Workers variant at a lower price point — organisations with significant F1/F3 populations should evaluate this separately rather than applying the enterprise Copilot add-on to frontline users at full cost.

GitHub Copilot: A Separate Licence Structure

GitHub Copilot — the AI coding assistant — is an entirely separate product from Microsoft 365 Copilot and is licensed independently. GitHub Copilot is available in three tiers: Individual ($10/user/month), Business ($19/user/month), and Enterprise ($39/user/month). The Enterprise tier includes GitHub Copilot Business plus knowledge bases, fine-tuning on internal repositories, and enterprise policy controls. GitHub Copilot is not included in any M365 SKU tier — not E3, E5, or E7 — and must be purchased separately through GitHub's commercial channels. Organisations that receive proposals bundling GitHub Copilot into an M365 E7 negotiation should ensure the pricing and contract terms are separate and clearly delineated.

What to Do Before Your Next Renewal

A structured pre-renewal process for Copilot licensing should include five steps. First, audit your current Copilot licence utilisation — if you have existing licences, determine actual monthly active user rates before renewing or expanding. Second, conduct a prerequisites assessment — validate your Exchange Online posture, Entra ID configuration, M365 Apps currency, and data governance baseline. Third, model three scenarios: E7 upgrade, E5/E3 plus selective Copilot add-on, and status quo with no Copilot expansion. Fourth, establish your ROI baseline from any existing pilot data. Fifth, engage with your renewal at least 90 days before the EA anniversary date to create negotiation runway — Microsoft field teams will not offer meaningful discounts in the final 30 days before renewal when they know you have no time to evaluate alternatives.

For organisations in the Q4 window (April to June 2026), the timing for this process is ideal. Microsoft field reps are under maximum fiscal-year pressure to close, and well-prepared buyers can secure Copilot and E7 pricing significantly below what will be available after July 1 when Microsoft resets to new fiscal year targets.

To explore how independent advisory support can strengthen your Copilot negotiation, visit our Microsoft Knowledge Hub or speak directly with our Microsoft EA negotiation specialists.