Microsoft 365 Enterprise Plan Selection CIO Playbook. The buyer side framework for Microsoft 365.

Microsoft 365 plan selection is a persona exercise: map worker types to E3, E5, and F3 before the renewal, because the all E5 default and the all E3 default both overpay in different ways.

What do E3, E5, and F3 actually differ on?

The plans share the productivity core; what separates them is security depth, compliance tooling, analytics, and telephony, which is why plan selection is a security architecture decision wearing a licensing costume. Current pricing sits on the Microsoft 365 enterprise pricing page.

F3 is the outlier: a frontline plan with web and mobile apps and capped mailbox, priced for workers who never sit at a desk.

The capability lines that decide

• Security. E5 adds the full Microsoft Defender suite, richer identity protection, and cloud app security.
• Compliance. E5 carries advanced eDiscovery, insider risk, and information protection tiers regulated industries actually use.
• Analytics and voice. Power BI Pro and Teams Phone sit in E5; on E3 they are paid add ons.
• Usage rights. The fine print lives in the Microsoft licensing terms, including F3 scope limits.

The persona question that starts the analysis

Ask which workers handle regulated data, which need advanced threat protection, and which never open a desktop app. Those three questions sort most of the directory.

When does E5 actually pay for itself?

E5 pays for itself when the security and compliance stack it includes retires third party spend of comparable value; without that offset, the E5 uplift is pure premium. The math is mechanical: list the tools E5 would replace, price their renewals, and compare.

The add on path nobody prices

E3 plus a single add on, such as E5 Security or Power BI Pro, frequently beats full E5 for personas needing exactly one premium capability. Price both paths per persona; the answer differs by estate.

The third party retirement test

An E5 business case that leaves the displaced tools running is not a business case. Tie the E5 uplift to named tool retirements with renewal dates, or buy the add on instead.

How does the mixed plan strategy cut spend?

A persona mapped mix of E5, E3, add ons, and F3 typically lands 20 to 30 percent below the all E5 default, because every license matches a consumption profile instead of a worst case. The mix also strengthens the EA negotiation, since Microsoft discounts deepest when E5 count grows from a defended baseline.

• Map personas first. Directory roles to plan fit, with usage data as the referee.
• Price the add on paths. Per persona, against full E5, at your actual discount levels.
• Deploy F3 honestly. Frontline populations on E3 are the most common silent overspend.
• Negotiate the mix. Take the defended plan map into the EA; concede E5 growth only for price.

Where the common advice on M365 plans is wrong

The standard advice, often sponsored by the seller, is that all E5 simplifies management and the security value justifies the blanket uplift. We disagree. In the M365 reviews Morten Andersen ran in 2024 to 2025, 30 to 50 percent of users in all E5 estates consumed no E5 exclusive capability in a quarter, and the displaced security tools were still running anyway. The buyer side move is persona mapping with the add on path priced per segment. Simplicity is worth something, but at the E5 uplift across a whole directory, it is the most expensive simplicity in enterprise software.

Microsoft sells E5 as a security decision. Make it one: if the third party tools it displaces are not retired, you did not buy security, you bought duplication.

What to do next

1. Pull license assignment and capability usage data from the admin center for the trailing quarter.
2. Build the persona map: regulated handlers, knowledge workers, security sensitive roles, frontline.
3. Price the E3 plus add on path against full E5 per persona at your discount levels.
4. Identify frontline populations contractually eligible for F3 and model the move.
5. Tie any E5 expansion to named third party tool retirements with renewal dates.
6. Take the defended plan mix into the EA negotiation calendar.
7. Re run the persona map annually; roles drift and the mix decays.

For the wider Microsoft picture, start with the Microsoft knowledge hub or the Microsoft advisory practice. For an always on review lane across all your vendors, see Vendor Shield.

Frequently asked questions

Should everyone be on Microsoft 365 E5?

No. In our 2024 to 2025 reviews, 30 to 50 percent of users in all E5 estates consumed no E5 exclusive capability in a quarter. Persona mapping with E3, add ons, and F3 typically lands 20 to 30 percent below the all E5 default.

When is E5 worth the uplift?

When it retires third party security and compliance spend of comparable value. Tie the uplift to named tool retirements with renewal dates; an E5 case that leaves displaced tools running is duplication, not value.

Who should be on Microsoft 365 F3?

Frontline and deskless workers who live in web and mobile apps and accept the mailbox cap. F3 is the most under deployed plan in enterprise estates and the most common silent overspend when frontline staff sit on E3.

Is E3 plus add ons cheaper than E5?

Often, when a persona needs exactly one premium capability such as E5 Security or Power BI Pro. Price both paths per persona at your actual discounts; the answer differs by estate and by Microsoft's current promotion cycle.

How does plan mix affect the EA negotiation?

A defended persona map is leverage. Microsoft discounts deepest when E5 growth comes from a credible baseline, and conceding E5 expansion only against price improvement converts the map into money.