Unofficial. Independent community helper — not a Microsoft product, not endorsed by Microsoft. Verify licensing with your Microsoft account team. The Microsoft Product Terms are the source of truth.
Independent · MIT-licensed · No tracking

The right Microsoft 365 license for every profile.

An interactive, source-cited decision tree that matches a Microsoft 365 identity profile to the right license tier — across Entra ID Free / P1 / P2, Entra ID Governance, Entra Suite, M365 E3 / E5 / Business Premium / F1 / F3 / A1 / A3 / A5 / G3 / G5, Defender Suite, Purview Suite, Intune Suite, Teams Premium, Microsoft 365 Copilot, and the new M365 E7 (Frontier Suite).

Right-size every license

Step-by-step questions narrow 60+ Microsoft 365 SKUs down to the exact tier each identity profile actually needs — no over-buying.

Cited at every step

Every question, recommendation and edge case links to Microsoft Learn or another primary source so your team can verify the logic.

PDF handout in one click

Generate a branded, citation-linked handout to share with your account team, CIO, or finance — no copy-paste, no slides.

Stays in your browser

Static site. No accounts, no analytics, no telemetry, no cookies. Your answers live in this tab and disappear when you close it.

Five ways a feature gets scoped

Every premium feature in the tree is tagged with one of these scopes so you know exactly who needs the licence and whether you can dial it down.

Per user

Licensed user-by-user. You pay for and assign the SKU to each individual identity that benefits.

Examples: Most Microsoft 365 SKUs — E3 / E5 / Copilot, Entra ID P1 / P2, and most Purview features.

Per device

Licensed to the device, not the user. The feature follows the onboarded endpoint.

Examples: Defender for Endpoint P2, Endpoint DLP, and Intune device licences.

Per mailbox

Licensed per Exchange Online mailbox that the feature acts on.

Examples: Exchange Online Plan 1 / Plan 2 and Exchange Online Archiving.

Tenant-wide, scopeable

Enabled at the tenant level, but you can scope its effect down to specific users, groups, or recipients via product configuration.

Examples: Defender for Office 365 P2 (recipient filters), Defender for Cloud Apps (Scoped Deployment), Defender XDR.

Tenant-wide, not scopeable

Once enabled, the benefit applies tenant-wide; the product has no control to limit it to a subset of users. Microsoft's Product Terms still expect every benefitting user to be licensed.

Examples: Customer Lockbox, Customer Key, and Defender for Identity.

How the tree works

  1. Pick the identity profile — privileged admin, information worker, frontline, education, government, nonprofit, SMB, or external guest. Government tenants get an extra sovereign-cloud picker.
  2. Answer a few short questions — yes/no or multiple choice. Every screen explains why we ask and cites the Microsoft Learn page that defines the rule.
  3. Get a specific recommendation — a named SKU (not "consider E5") with rationale, bullets, sovereign-cloud caveats, and footnotes.
  4. Take the handout with you — download a branded PDF or copy a plain-text summary. No accounts, no email gates.

Ready when you are.

One tab, no signup, no tracking. Average run takes 90 seconds.

Start the assessment →