Selecting the Right Microsoft 365 Enterprise Plan

Microsoft 365 licensing is not a simple pick-one-tier decision. Organisations that treat it that way routinely overspend by hundreds of thousands of dollars annually — paying E5 prices for employees who need E1 capabilities, or locking frontline workers into full-featured plans they cannot use. The right approach is a deliberate mix-and-match strategy grounded in actual job function requirements, negotiated hard at Enterprise Agreement renewal.

This playbook walks through the six core plan tiers, explains the role-based assignment framework that typically cuts Microsoft 365 spend by 30 to 50 percent, covers the add-on landscape (Copilot, Defender, Power BI, Teams Phone), and gives you the negotiation levers to use at renewal. For a broader view of controlling Microsoft costs, the Microsoft Knowledge Hub covers EA optimisation, True-Up mechanics, and Azure spend governance alongside your M365 position.

Understanding the Six Plan Tiers

Microsoft publishes M365 in two broad families: Business plans (capped at 300 users) and Enterprise plans (unlimited users). Most organisations above 300 users are on the Enterprise track, but Business plans sometimes make sense for subsidiaries, regional entities, or newly acquired companies still on separate agreements.

Enterprise Plans: E1, E3, and E5

The jump from E1 to E3 is the most commonly justified move. The jump from E3 to E5 is where most organisations overspend. E5 bundles a significant security and compliance stack that many organisations either already own separately, procure via add-ons, or frankly do not fully use. Before upgrading any cohort to E5, audit which specific E5-only features you actually intend to activate within the first 12 months. If the honest answer is fewer than three, you are paying a bundling premium for capabilities you are not using. See our detailed Microsoft 365 E3 vs E5 vs Business Premium decision framework for the 2026 pricing changes and role-based hybrid licensing models that consistently save 10 to 30 percent. Our Microsoft contract advisory practice routinely identifies E3-to-E5 uplift as the single largest source of waste in enterprise M365 estates.

Frontline Plans: F1 and F3

Frontline Worker licences are engineered for employees who do not sit at a desk and do not need full Office productivity. Retail associates, warehouse staff, field technicians, nurses, and logistics workers are the canonical use cases. The price difference is dramatic.

The most common mistake is assigning frontline workers E1 licences when F1 or F3 would fully meet their functional requirements. An organisation with 5,000 frontline workers on E1 at $10 per user per month is spending $600,000 per year more than necessary if F1 covers their use case. Confirm whether your frontline workers need Exchange mailboxes. If they communicate via Teams channels only, F1 is sufficient. If they need individual email, F3 at $8 is still 20 percent cheaper than E1 with the same communications capability.

Business Plans (Under 300 Users)

Microsoft 365 Business Basic, Business Standard, and Business Premium are structurally similar to E1, E3, and E5 respectively, but are capped at 300 users per tenant. They are not available under an Enterprise Agreement and cannot be mixed with Enterprise plans on the same tenant agreement. Business Premium at $22 per user per month is worth evaluating for subsidiaries or small entities that need the integrated Defender for Business security layer without the full E5 complexity and price.

The Role-Based Assignment Framework

Uniform licensing — assigning every employee the same plan tier — is the default and the wrong approach. A role-based framework segments your workforce by actual software consumption and assigns the minimum sufficient licence tier for each cohort. Done properly, this exercise typically reduces total M365 spend by 30 to 50 percent compared with a blanket E3 deployment.

The framework has five steps. First, classify every role in your organisation into one of four consumption archetypes: Power Users (full E5 or E3 with security add-ons), Information Workers (E3), Light Users (E1 or F3), and Frontline Workers (F1 or F3). Second, map your current user population to those archetypes using HR system data, Active Directory group membership, and application usage telemetry from M365 admin centre reports. Third, identify every user currently over-licenced relative to their archetype. Fourth, calculate the annualised savings from right-sizing. Fifth, obtain sign-off from department heads and implement the changes before your next True-Up date or renewal.

Microsoft's own usage analytics within the M365 admin centre (under Reports > Usage) show you per-user activity across Exchange, SharePoint, Teams, and the Office apps. Any user with zero OneDrive activity, zero desktop Office sessions, and only occasional Teams messages in the past 90 days is a strong candidate for downgrade. The Microsoft licence management practice can run this analysis against your tenant data and produce a ranked list of reclassification candidates with financial impact estimates.

Common Cohort Patterns

In most enterprise environments, Power Users who genuinely require E5 represent 10 to 20 percent of the workforce — typically senior managers, finance staff, legal, compliance officers, and IT administrators. Information Workers who need full desktop Office and compliance tooling represent 40 to 60 percent of the workforce. Light Users who primarily consume email, Teams, and browser-based applications represent 20 to 30 percent. Frontline Workers who need scheduling, shift management, and basic communications represent whatever proportion of your workforce is non-desk-based.

These proportions vary significantly by industry. A financial services firm may have 60 percent Power Users and very few Frontline Workers. A retail or logistics operation may have 80 percent Frontline Workers and only a small Information Worker core. Understanding your specific profile before negotiating with Microsoft is essential — Microsoft's default is to push every renewal toward E3 or E5 for all users, regardless of fit.

The Add-On Strategy

Microsoft sells a substantial catalogue of add-on services on top of M365 base plans. The strategic question is whether to acquire these add-ons individually, bundle up to a higher base plan, or procure them via separate agreements (for example, Defender plans via Microsoft Defender for Business or Microsoft 365 Defender standalone). The answer depends on the volume of users who genuinely need each capability.

Microsoft 365 Copilot

Copilot is priced at $30 per user per month and requires an E3 or E5 base plan as a prerequisite. It integrates generative AI assistance across Word, Excel, PowerPoint, Outlook, Teams, and Microsoft 365 Chat. The key licensing question is not whether Copilot is valuable in principle, but which roles will see measurable productivity uplift within the first 90 days of deployment. Broad rollouts without adoption programmes typically see 30 to 40 percent of licences go unused in the first six months, which at $30 per user per month represents significant waste. Pilot with targeted cohorts, measure, and expand based on actual usage data before committing to a large Copilot seat count at renewal.

For detailed guidance on optimising your Microsoft AI investment, the CIO Playbook on Adopting Microsoft 365 Copilot and AI Services covers pilot structure, adoption governance, and negotiation of Copilot at scale.

Microsoft Defender Add-Ons

E5 includes Defender for Office 365 Plan 2, Defender for Identity, Microsoft Sentinel integration, and Purview advanced compliance. If you are on E3 and need these capabilities for a subset of users — typically security operations, privileged administrators, and compliance officers — procuring them as add-ons is almost always cheaper than upgrading the full population to E5. Defender for Office 365 Plan 2 as a standalone add-on is approximately $5 per user per month for the users who need it. Compare this with the $21 per user per month E3-to-E5 uplift applied across all users and the arithmetic becomes obvious.

Power BI Pro

E5 includes Power BI Pro. E3 does not. If only your analytics team and report consumers need Power BI Pro, acquiring it as an add-on at $10 per user per month for those users is significantly cheaper than upgrading your entire E3 population to E5. Power BI Premium Per Capacity is a separate consideration for organisations with large-scale self-service BI deployments.

Teams Phone

Teams Phone (formerly Phone System) replaces traditional PBX infrastructure using Teams as the calling platform. It requires an additional licence at approximately $8 per user per month on top of your base M365 plan, plus a Calling Plan or Direct Routing arrangement for PSTN connectivity. E5 includes Teams Phone, which is part of what justifies the E5 premium for roles that need it. For all other users, Teams Phone as an add-on is the right procurement path, and only for users who genuinely make and receive external calls — typically not the majority of an enterprise workforce.

EA Negotiation Tactics at Renewal

Microsoft Enterprise Agreements run on three-year cycles. The renewal is your primary opportunity to restructure your licence mix, negotiate discounts, and lock in favourable terms for the next cycle. Microsoft sales teams are under significant pressure to grow revenue at each renewal, which means they will push for tier upgrades, Copilot adoption, and additional workloads. The following tactics protect your position.

Start Renegotiation 12 Months Before Expiry

Microsoft's leverage diminishes the closer you are to the renewal date from the vendor's perspective, but increases the pressure you feel if you leave it too late. Starting 12 months out gives you time to run the role-based segmentation analysis, obtain competitive quotes from Google Workspace or other alternatives, and engage Microsoft in substantive commercial discussions rather than last-minute renewal scrambles. The Microsoft contract negotiation service typically engages clients 9 to 12 months before their EA expiry for this reason.

Use Competitive Alternatives as Leverage

Google Workspace Enterprise Plus at $25 per user per month covers the use cases of a large proportion of M365 E3 users. You do not need to intend to migrate to use this as negotiating leverage. The credible threat of migration — demonstrated by a documented evaluation and a meeting with your Google account team — reliably produces meaningful Microsoft discount movement. Microsoft's field teams have authority to move on price when they perceive genuine competitive risk. At EA scale, a 10 percent discount on a 5,000-user E3 deployment saves $216,000 per year.

Negotiate the True-Up Mechanism

Under a standard EA, you pay for the user count you declared at signing and reconcile actual growth annually via the True-Up process. Negotiate for True-Down rights — the ability to reduce licences at True-Up if your actual user count has declined. Microsoft often resists this but will accept partial True-Down rights (for example, allowing reductions up to 10 percent per year) in competitive situations. Also negotiate annual True-Up pricing at the original per-unit rate rather than then-current list price, which protects you against price increases mid-agreement.

Separate Products from Bundles

Microsoft pushes bundled M365 suites because bundles obscure the per-capability cost and make it harder to argue for alternatives. When negotiating, request line-item pricing for each component of the bundle you are evaluating. Knowing that you are paying $X per user per month specifically for Power BI Pro within the E5 bundle, when the standalone add-on would be $10 per user for only the users who need it, gives you a concrete negotiating argument. Microsoft will typically not provide this decomposition unless you push for it explicitly.

Lock in Copilot Pricing Before Broad Rollout

If you plan to expand Copilot adoption over the next three years, negotiate volume pricing and price stability commitments now, before you have deployed broadly. Once you are dependent on Copilot at scale, Microsoft's pricing leverage increases substantially. Securing a committed price per seat for year 2 and year 3 of the EA, in exchange for a committed minimum seat count, is a standard term that sophisticated buyers negotiate upfront.

Demand Full Utilisation Reporting

Require Microsoft to provide comprehensive utilisation reporting as a contractual commitment, not just as a best-effort advisory service. This includes per-user activity data for all licensed workloads, updated monthly, accessible via admin centre API. Utilisation visibility is your primary tool for identifying ongoing reclassification opportunities throughout the agreement term. Without it, you cannot maintain the licence hygiene that prevents cost drift.

Governance and Ongoing Licence Hygiene

Plan selection and EA negotiation are point-in-time events. The ongoing discipline that sustains savings is licence hygiene — the regular process of identifying and reclassifying users whose consumption profiles no longer match their assigned tier. Organisations that do this quarterly maintain 5 to 10 percent lower per-user costs than those that review only at renewal.

The minimum governance structure for M365 licence hygiene includes a quarterly licence review meeting with data from the M365 admin centre usage reports, a defined process for submitting reclassification requests when employees change roles, an automated offboarding workflow that returns licences within 24 hours of departure (each unused licence on a terminated account costs between $10 and $57 per month), and a named licence owner who is accountable for the annual True-Up declaration accuracy.

The True-Up declaration is where annual M365 costs are determined. If your True-Up count is inflated by stale accounts, role changes that were never processed, or contractor populations who left the organisation, you are paying for licences that deliver no business value. A pre-True-Up audit in the 60 days before your annual reconciliation date is one of the highest-return activities in Microsoft cost management.

CIO Action Plan: The 90-Day Optimisation Sequence

For CIOs who want to move from intent to execution, the following 90-day sequence is the fastest path to measurable savings. In weeks one through four, pull the M365 admin centre usage report for all licensed users, identify every user with less than 20 percent active use of their licensed workloads, classify those users by role archetype, and build the reclassification business case with financial impact. In weeks five through eight, present the reclassification plan to HR and finance for approval, implement the tier changes for clear-cut cases, and flag borderline cases for manager review. In weeks nine through twelve, submit the updated user counts as your True-Up baseline, initiate the EA renewal conversation with Microsoft if you are within 12 months of expiry, and establish the quarterly review cadence. The typical output of this sequence, for an organisation of 2,000 to 10,000 users, is between $400,000 and $2,000,000 per year in sustained savings.

If your Microsoft spend is above $1 million per year, an independent assessment of your current licence position typically identifies two to four times the cost of the assessment in actionable savings within the first 90 days. The Redress Compliance assessment programme includes a full M365 licence health check as part of the Microsoft advisory engagement.