Microsoft 365 E3 vs E5 vs F3 for enterprise users. Which plan each user needs, and what the mix saves.

Put every user on the cheapest plan that covers their work and a heavy E5 company models a list saving near 27 percent. Most collect far less, because exceptions, security standards and contracts without a step down right absorb the rest.

What is the difference between Microsoft 365 E3, E5 and F3?

E3 is the productivity plan for desk based staff, with full desktop Office and 1 TB of OneDrive storage. E5 is E3 plus advanced Defender and Purview security, Teams Phone and Power BI Pro. F3 is the frontline plan: Office on web and mobile only, 2 GB of OneDrive, and none of the E5 extras.

At the current list, E5 costs exactly six times F3, $60 against $10. Under the old list the spread was wider, about 7 to 1. Either way, an E5 license on a frontline worker is the most expensive placement error a Microsoft 365 contract can carry.

What changed in the July 2026 price list?

Microsoft raised Microsoft 365 list prices on July 1, 2026. E3 went from $36 to $39, E5 from $57 to $60 and F3 from $8 to $10 per user per month on annual terms. F1, the lighter frontline plan, now lists at $3, and our F1 versus F3 guide compares the two.

The worked example further down uses the old list, because many agreements still running were priced against it. We then rerun it at current prices. How to handle the increase at renewal is covered in negotiating the 2026 price increase.

What does F3 leave out?

F3 users get Word, Excel and PowerPoint in the browser and on mobile, plus Teams, but no installed desktop Office. Mailbox and OneDrive are each capped at 2 GB. Check mailbox size before moving anyone, because a user with years of archived mail will not fit. The detailed boundary is in F3 versus E3.

Which users belong on E3, E5 or F3?

Each user belongs on the cheapest plan that covers the work they actually do. In most companies six personas account for nearly everyone, and two of them can be served either by E5 or by E3 with a single add on.

• Knowledge worker. E3. Desktop Office, email, Teams meetings, file sharing.
• Security or compliance owner. E5. Investigators, eDiscovery managers and the people who run insider risk or data loss prevention.
• Analyst. E5, or E3 plus Power BI Pro.
• Voice user. E5, or E3 plus Teams Phone.
• Frontline shift, retail and field staff. F3.
• Deskless approver. F3. The light reader who approves workflows and reads mail but never opens desktop Office.

Build the map from usage data, then list the exceptions deliberately before anyone reviews it. An exception list you write yourself is a planning input. One that surfaces during review arrives in clusters and wipes out part of the saving you already reported. The broader placement question across all Microsoft 365 plans is in Microsoft 365 licensing.

When does E3 plus add ons cost less than E5?

At current list prices, E3 plus one add on is cheaper than E5, and E3 plus any two is more expensive. So the add on route wins for users who need one E5 capability, and the suite wins for users who need two or more.

Defender Suite and Purview Suite are the security and compliance halves of E5 sold separately, and both require an E3 base. Negotiated discounts move the break even, because the E5 rate and each add on rate are discounted separately and seldom by the same percentage. Rerun the table with your own contract rates before you decide.

Why the answer changes from group to group

Cost the add on route separately for each persona. An analyst team that only needs Power BI Pro belongs on E3 plus Pro. A security operations team that needs Defender and Purview together belongs on E5. How the individual add ons compare is set out in our E5 add on guide.

How much does remapping 10,000 users across E3, E5 and F3 save?

Take a hypothetical company with 10,000 users and a heavy E5 footprint. Moving 3,500 users from E5 to E3 and 2,000 from E3 to F3 cuts annual list spend from $5,664,000 to $4,110,000, a saving of $1,554,000 or 27.4 percent. The seat count stays at 10,000 throughout.

The monthly difference is $129,500. Every dollar of it comes from placement, since no seat is removed. That is why the saving holds up through a headcount freeze and can be pursued without cancelling any service.

The same remap at the July 2026 list

At $60, $39 and $10, the starting bill is $501,500 a month, or $6,018,000 a year. After the same changes it is $370,000 a month, or $4,440,000 a year.

• Annual saving. $1,578,000, about 26.2 percent of the starting bill.
• Realized band on the same basis. Roughly $722,000 to $1.08m a year.
• Why the percentage dips. The E5 to E3 gap is still $21 and the E3 to F3 gap grew only from $28 to $29. The dollar saving rises by $24,000 while the starting bill rises by $354,000.

Why does the realized saving fall short of the model?

Three things take the difference: role exceptions, security standards and a contract that blocks reductions until the term ends. On the example, the model says $1.55m while the realized band in the table is roughly half that. The arithmetic is rarely the problem. These three factors are how a 27 percent model becomes roughly 15 percent in the ledger.

Role exceptions telemetry cannot see

A persona map built from feature telemetry misses the user who needs Purview four times a year during a regulatory response. It also misses the executive whose E5 seat is a policy decision rather than a usage one. Those seats return to E5 during review, usually in groups of related roles.

Security standards that set a floor

Most companies have a written standard that puts a whole class of user on the advanced tier regardless of measured use, often anyone who handles regulated data. That standard is usually right. It is also rarely rewritten to suit a licensing project, so plan around it from the start.

A contract that blocks reductions mid term

Moving users from E5 to E3 reduces the quantity of your most expensive SKU. An Enterprise Agreement does not generally let you reduce quantities whenever an analysis finishes. Without a negotiated step down right at anniversary, work completed in month three of a three year term cannot be banked until month thirty six, and by then usage has drifted again.

Why we advise against chasing a deeper E5 discount

The usual account team advice is that E5 is the safe default and the prize is a deeper discount on a broad E5 base. We disagree. In roughly 30 of the 45 renewals we reviewed, a quarter to nearly half of E5 seats never touched an E5 only feature.

A discount negotiated on those seats is a lower price for capability that sits unused. Correct the seat count first, then negotiate the rate on the result.

Finding the misplaced E5 seats is the easy half. Having the contractual right to move them before the term ends decides whether the work pays.

Commit to a number your users will accept

Say review sends 400 of the 3,500 planned E5 to E3 seats back to E5. At the old list each costs $21 a month more, or $100,800 a year in total, so the ceiling falls to $1,453,200. Take off the security floor and the seats the contract will not let you move yet, and give the board what remains.

Used this way, the exception list becomes a negotiation input rather than a surprise.

Can F3 users get Microsoft 365 Copilot, and what does it cost?

Yes. Microsoft's current Copilot licensing documentation lists Microsoft 365 F1 and F3 as qualifying base plans, so a frontline user can add the $30 Copilot license without leaving F3. When Copilot first launched for enterprises it required Microsoft 365 E3 or E5, and many pilot plans still assume that rule.

On the E3 route, a seat that cost $8 now costs $66, roughly eight times as much. Of the $58 increase, $28 is the base plan jump and $30 is Copilot, so nearly half the new spend has nothing to do with AI. The E3 assignment also outlives the pilot unless someone reassigns the user.

When moving a frontline user to E3 is justified

F3 has no desktop Office, so Copilot on F3 works in the web and mobile apps and in Teams. If the business case depends on Copilot inside desktop Excel or Word, the base plan change belongs in the pilot budget, planned and reversible.

Count it there, so it does not surface in the following year's true up. Current Copilot pricing is in Microsoft 365 Copilot pricing.

What have we seen in Microsoft 365 renewals in 2024 and 2025?

Across roughly 30 to 45 Microsoft 365 renewals we benchmarked in 2024 and 2025, putting everyone on E5 was the largest single source of waste. Three patterns came up again and again.

• Unused E5. Between 25 and 45 percent of E5 seats used no security or compliance feature beyond what E3 already includes.
• Frontline staff on E3. Between 10 and 20 percent of E3 seats belonged to frontline workers who fit F3 at roughly a fifth of the old E3 price, or about a quarter at current list.
• Copilot pilots that moved the base plan. Pilots moved F3 users onto E3 before a single Copilot license was bought. The cost appeared as an unexplained E3 growth line, and it stayed after the pilots ended.

The seat that costs the most is an E5 license assigned to someone who only ever opens Word, Teams and Outlook. Finding those seats takes usage reports and a spreadsheet. Being able to act on the findings depends on the contract you signed.

How do you find out which plan each user needs?

Join each user's assigned license to their actual usage, one row per user. The data sits in the Microsoft 365 admin center usage reports, the Teams admin center, and the Purview and Defender portals.

1. Microsoft 365 Apps usage report. In the admin center under Reports, Usage. It shows per user activity by platform: Windows, Mac, web and mobile. Users with no desktop activity across the longest reporting period are F3 candidates.
2. Mailbox usage and OneDrive usage reports. Storage per user, checked against the 2 GB F3 limits.
3. Teams admin center. Users with phone numbers assigned and the PSTN usage reports identify your voice persona.
4. Power BI activity in the Purview audit log. Shows who creates, publishes and shares reports, which is the analyst persona.
5. Policy scope in Purview and Defender. Which users sit in scope of insider risk management, communication compliance, eDiscovery (Premium) cases or Defender for Office 365 Plan 2 features. Many E5 security controls work through policies assigned to users, so policy scope is the usage signal.

Check whether user names are hidden in your reports

By default the admin center conceals user, group and site names in usage reports. A global administrator can turn this off in Settings, Org settings, under the Reports service. Without that change the export shows anonymized identifiers you cannot join to license data. Our Microsoft 365 license optimizer takes the joined export as input.

What will the Microsoft account team say, and how should you answer?

Expect the conversation to push toward a larger E5 commitment. These are the lines we hear most often in Microsoft 365 renewals, with the reply that holds up.

• "With E5 you can retire your point security tools." Ask them to name the tools and the user groups that use them. Price E5 for those groups and keep everyone else on E3.
• "The best discount needs a full E5 commitment." Ask for two quotes: full E5 and your corrected mix. Compare the total cost of each.
• "Frontline users need E3 before they can use Copilot." Point to Microsoft's own Copilot licensing page, which lists F1 and F3 as qualifying plans.
• "Reductions are only possible at the end of the term." That is the standard position, which is why you are asking for a step down right in this renewal while the signature is still open.

What should the renewal contract say before you remap users?

Agree the terms that let you act on the persona work before the analysis starts, while Microsoft still needs your signature. These are the clauses to request.

• Step down right at each anniversary. The right to move seats from E5 to E3 and from E3 to F3 at anniversary without penalty. This is what turns a model into savings within the term.
• Per SKU price protection. Fixed unit prices for E3, E5 and F3 for the full term, so moving seats between plans never reprices the ones that remain. Our price hold clause guide has sample wording.
• Add on prices locked. Teams Phone, Power BI Pro, Defender Suite and Purview Suite at fixed rates, so the E3 plus add on route stays cheaper for the life of the agreement.
• Discount stated per SKU. A blended percentage across the agreement can shrink when the mix changes. A rate per SKU cannot.
• Reversible Copilot pilot uplifts. Any user moved from F3 to E3 for a pilot can return to F3 at the next anniversary.

How reductions interact with the annual count is covered in our EA true up guide, and the wider Microsoft library sits in the Microsoft knowledge hub.

What to do next

1. Put the step down right on the renewal ask first. Request anniversary reductions before any persona work starts, while Microsoft still needs the signature.
2. Pull license and usage data per user. Cover security, compliance, voice and analytics, plus desktop app use and storage, and join them into one table.
3. Map every user to the lowest plan that fits. Write the exception list explicitly, so the committed number is one your users will accept.
4. Cost the add on route per persona. Compare it with full E5 for the same group and take whichever is cheaper for that group.
5. Move deskless and shift workers to F3. Check mailbox size first, then move them at the anniversary.
6. Budget any Copilot base plan changes inside the pilot, then take the rate last. Negotiate the discount on the corrected seat count. Our Microsoft practice can run the persona map with you.

Frequently asked questions