Microsoft 365 plans and pricing

Microsoft 365 licensing looks like a wall of SKUs, but the real decision tree is short. Almost every organisation lands in one of three places: Business Premium if you're under 300 users, E3 plus targeted add-ons if you're an enterprise, or E5 if you'll genuinely use what E5 bundles. Everything else — frontline plans, suites, Copilot — attaches to one of those three anchors.

This guide routes you to the right anchor, then points you at the detailed comparison for each fork in the road. If you want the mechanics of how licences are structured and assigned first — per-user subscriptions, add-ons, group-based assignment — start with licensing models explained.

The plan families in one minute

• Business (Basic / Standard / Premium) — capped at 300 users per SKU. Cheaper than the enterprise equivalents because Microsoft assumes smaller organisations need less.
• Enterprise (E1 / E3 / E5) — no seat cap, deeper security and compliance at the top end, and access to the full add-on catalogue.
• Frontline (F1 / F3) — cut-down, cheap plans for workers who share devices and don't live in Office. Covered in the frontline plans deep dive.
• Education and consumer (A-series, Family/Personal) — out of scope here; the A-series mirrors the enterprise tiers at education pricing.

Within each family the tiers step up the same three ladders: desktop Office apps, device management with Intune, and security/compliance depth. Prices change and vary by region and agreement type, so treat any number you read in a blog post — including this one, which is why there aren't any — as stale. Check Microsoft's current price list or your CSP.

Route 1: Under 300 users → Business Premium

If you're under the 300-seat cap, the decision is rarely which family — it's which Business tier, and the answer is usually higher than people first budget for.

• Business Basic — web and mobile Office, Exchange, Teams, SharePoint/OneDrive. Fine for mailbox-only staff.
• Business Standard — adds the installable desktop apps. Where most small companies start.
• Business Premium — adds Intune, Entra ID P1, and Defender for Business. This is the one to default to.

The case for Business Premium is that the gap between it and Business Standard is exactly the gap attackers exploit: conditional access, device compliance, endpoint protection. A small company on Standard has business-grade email and consumer-grade security. The full walkthrough of what Premium contains and how to actually switch its features on is the Business Premium deep dive; a broader orientation for small organisations is Microsoft 365 for small business.

Two situations push you out of this route while still under 300 users: you're growing through the cap soon, or you need something only enterprise SKUs carry (unlimited archiving, certain compliance features, larger mailboxes). That's the Business Premium vs E3 decision — and the short version is that Business Premium wins on security value per seat, E3 wins on ceiling.

Route 2: Enterprise standard → E3 plus targeted add-ons

Over 300 users, or over the feature ceiling, the default anchor is Microsoft 365 E3: desktop apps, Entra ID P1, Intune, and the core compliance set. (E1 exists for web-only users, but in practice most enterprises use F-plans for that population instead.)

The modern pattern is not "E3 vs E5" as a binary — it's E3 as the base, plus suite add-ons for the capabilities you'll actually deploy:

• Entra Suite — identity governance, Internet Access, Private Access, and verified ID on top of E3's P1. The route to advanced identity without buying E5.
• Intune Suite — Endpoint Privilege Management, Remote Help, advanced analytics and patching on top of the Intune Plan 1 that E3 includes.
• E5 Security and E5 Compliance mini-suites — the Defender products or the Purview premium features as add-on bundles, without the rest of E5.
• Microsoft 365 Copilot — always an add-on, never included, on Business and Enterprise plans alike. Licence the pilot group, not the tenant.

This route wins when your needs are lopsided — strong security requirements but no interest in Power BI Pro or Teams Phone, say. You pay for the two suites you'll deploy instead of the seven workloads E5 bundles. The trade-off is administrative: more SKUs to track, more per-user assignment decisions, which is exactly what group-based licensing exists to absorb.

Route 3: Enterprise advanced → E5

Microsoft 365 E5 bundles the top of every ladder: the full Defender stack, Purview's premium compliance features, Entra ID P2, Power BI Pro, Teams Phone Standard, and audio conferencing. The E3 vs E5 comparison walks the differences feature by feature.

The honest test for E5 is utilisation, not capability. E5 is priced so that if you'd otherwise buy three or four of its components as add-ons — E5 Security plus Teams Phone plus Power BI Pro is the classic trio — the bundle is cheaper than the parts. If you'd deploy one component, it isn't. The most common licensing waste in large tenants is E5 bought for the security stack while the phone system stays on a legacy PBX, Power BI Pro sits unused, and nobody has turned on half of Purview.

Two patterns that work in practice:

• Mixed assignment — E5 for security teams, IT, and executives; E3 plus targeted add-ons for everyone else. Licences are per-user; nothing forces uniformity.
• E5 with a deployment plan — buy it, but with named owners and dates for each bundled workload. E5 justified "because security" and then half-deployed is the outcome to avoid.

The populations that aren't knowledge workers

Frontline staff — retail, manufacturing, healthcare, logistics — shouldn't carry knowledge-worker licences. F1 and F3 exist for shared-device, shift-based work: Teams, shift management, web Office, small or no mailboxes, at a fraction of the E-plan price. The seat-count maths matter here; a 5,000-person organisation with 3,500 frontline workers is mostly an F-plan tenant with an E-plan minority. Details and the F1-vs-F3 fork are in the frontline plans deep dive.

What Microsoft 365 licences don't cover

Two adjacent stacks bill separately and surprise people at renewal:

• Power Platform — Power Apps and Power Automate have limited "seeded" rights inside Microsoft 365, and real per-app/per-user licences beyond them. The line between seeded and paid is where most budget surprises live: Power Platform licensing explained.
• Copilot — the per-user add-on economics, the prerequisites, and who should actually get a seat first: Microsoft 365 Copilot licensing.

How to decide

| Your situation | Anchor | The comparison to read | | --- | --- | --- | | Under 300 users | Business Premium | Business Premium deep dive | | Under 300, hitting feature ceilings or growing past the cap | E3 | Business Premium vs E3 | | Enterprise, lopsided needs | E3 + Entra/Intune/E5-mini suites | Entra Suite, Intune Suite | | Enterprise, will deploy 3+ premium workloads | E5 | E3 vs E5 | | Large frontline population | F1/F3 alongside the above | Frontline plans deep dive |

Then pressure-test the choice: list the features you will actually deploy in the next twelve months, price the anchor plus add-ons against the next tier up, and assign the result with licensing groups rather than by hand. For the wider enterprise picture beyond licensing, see Microsoft 365 for enterprise.

Licensing is the one Microsoft 365 decision you revisit every renewal. Buy the anchor that matches this year's deployment reality — not the aspiration — and let the add-on model absorb the growth.