Content reviewed: 12 October 2026
Not every user must receive E5. Different groups can use different eligible combinations. However, start with the required feature, its scope and the base licence, rather than a list of people signing into the security portal. Services with broad effects may not let you restrict their benefits to a few selected roles.
Current names and prerequisites
| Current name | Previous name | Qualifying base |
|---|---|---|
| Microsoft Defender Suite | Microsoft 365 E5 Security | Microsoft 365 E3 or Office 365 E3 + EMS E3 |
| Microsoft Purview Suite | Microsoft 365 E5 Compliance | Microsoft 365 E3 or Office 365 E3 + EMS E3 |
The Microsoft Security Suites licensing matrix confirms these names and enterprise prerequisites. Business Premium and frontline variants have different prerequisites; similar names do not make their rules interchangeable. Check the actual offer, current service plans and customer programme when ordering.
Defender and Purview meet different requirements
Defender Suite adds products including Entra ID P2, Defender for Endpoint P2, Defender for Office 365 P2, Defender for Identity and Defender for Cloud Apps. Purview Suite addresses advanced data and compliance scenarios, such as Audit Premium and eDiscovery Premium. Distinguish security detection from governing and investigating content. Check each required feature’s exact scope in the current matrix.
Defender XDR prerequisites distinguish shared-portal access from individual product entitlements. A visible page or alert does not automatically cover every capability. In the pilot, record the product supplying the signal, the protected users and the licence covering that functionality.
Map features to the affected population
| Requirement | Count | Technical check |
|---|---|---|
| Identity risk-based policies | Users in protection scope | Qualifying Entra plan and actual targeting |
| Advanced endpoint or email protection | Protected users and relevant workloads | Applicable Defender products and their rules |
| Advanced Purview feature on a team site | Relevant owners, members and roles by feature | Feature used and actual content scope |
| Premium audit retention | Users whose activities need coverage | Services, events and retention settings |
| Customer Key | Population by workload | Applicable broad encryption-policy scope |
Entra ID Protection requires P2 for risk policies and distinguishes limited lower-plan information from full capabilities. Count entitlements already available through other packages before purchasing an entire add-on. One requirement does not necessarily need every product in a suite.
Purview quantities are not administrator headcounts
For shared locations such as SharePoint and Teams channels, the Purview service description requires suitable licences for owners and members when the relevant policy or feature applies. Visitors and view-only users do not need a licence in this documented scenario. The rule is neither automatically “everyone in the tenant” nor “only the compliance team”.
A hypothetical pilot has two licensed Purview administrators and a team site with forty members. Those two administrators alone do not establish licensing for an advanced feature applied to the site. Check member entitlements and the feature itself, removing overlapping people from the count. View-only access must match actual permissions rather than a group’s name.
Audit Premium extended retention concerns activities of appropriately licensed users in the relevant services. One investigator’s licence does not extend everyone else’s history. Customer Key has broader entitlement-count requirements depending on workload. Assess these features separately; a general bundle table does not describe their full licensing scope.
When to compare full E5 and add-ons
- Keep E3 where its available rights meet the actual work and protection requirements.
- Assess E3 plus Defender Suite for missing advanced security features with the qualifying base in place.
- Assess E3 plus Purview Suite for defined advanced data and compliance scenarios with the correct population.
- Compare full E5 when the same people need several areas or additional E5 services. Check exact contents and the Teams variant in the offer.
Microsoft’s enterprise page helps compare offered suites. Use actual quotes with matching currency, period and contract terms. Include the qualifying base, add-ons and other required services. Neither “E5 always costs less than two add-ons” nor the reverse is supported without specific evidence.
Technical scope must match procurement
Before expanding a policy, reconcile its target groups with assigned licences. Purchased quantities are not proof that every affected user is covered. If a service’s benefits cannot be restricted to a selected group, buy for its actual scope. Renaming a group does not resolve the difference.
Reassess when policies, team membership, investigated content or licences change. Plan add-on removal with the service owner, first confirming which functions and data must remain. Periodic review is useful, but a scope change cannot wait for the calendar checkpoint.
Decision workflow
- 01
Name the feature
Product, workload, required result and owner
- 02
Map people and content
Policy targets, membership, administrator roles, protected data and overlapping users
- 03
Check prerequisites
Current service plan, contract programme and existing entitlements
- 04
Compare equivalent quotes
Full E5, add-on or a qualifying combination for the same scope
- 05
Verify pilot and records
Actual targeting, function, assignment and reassessment triggers
Keep an evidence chain: requirement → feature → affected population → entitlement → policy. It lets you justify procurement and revise it as the environment changes. Savings mean removing unnecessary rights while preserving required coverage, rather than merely reducing invoice line items.
Frequently asked questions
Are E5 Security and Defender Suite different enterprise offers?
Current guidance identifies Microsoft Defender Suite as the current name for Microsoft 365 E5 Security. Verify the actual offer and service plans when purchasing.
Is licensing the compliance administrator enough?
Not automatically. Assess the people and content affected by the feature under the relevant service rules.
Does everyone need E5?
Not always. Different eligible combinations are possible when they match the actual feature scope. Some services have broad effects.
Is E3 with both add-ons identical to full E5?
Do not assume complete parity. Compare current contents, prerequisites and other required services in the actual offers.








