The Microsoft 365 E3 vs E5 conversation is usually had backwards. People compare feature lists, decide E5 looks better, and then discover the uplift was justified by two capabilities they could have bought as a much cheaper add-on. Work from the cliff edges instead.
What E3 already covers
More than most people assume, which is why the uplift often fails to pay for itself. Everything below is checked against the Microsoft 365 security and compliance licensing guidance, which is the document that decides these arguments. On the compliance side alone, E3 covers Audit (Standard), manual sensitivity labelling, retention label creation, and retention policies scoped organisation-wide, location-wide, or with include and exclude lists.
If your compliance requirement is “retain mail for seven years and be able to search it”, E3 does that. No uplift required. The feature by feature version of that argument is in Microsoft Purview cost.
The three cliff edges that decide Microsoft 365 E3 vs E5
These are the points where E3 genuinely stops rather than merely doing less.
Outgrowing Business Premium does not force the whole tenant onto E3, because Business and Enterprise plans can be mixed in one account: what the Business Premium 300 user limit actually covers.
| Capability | Why it is a cliff, not a gradient |
|---|---|
| Adaptive policy scopes | Retention works on E3. Adaptive scoping, which keeps a policy correctly targeted as people join and leave, does not. On a static org you will not notice. On one with turnover, the alternative is somebody maintaining membership by hand. |
| Audit (Premium) | E3 gives you Audit (Standard). One year retention and the crucial events used in real investigations need Premium. Ten year retention needs a further add-on on top of that. |
| Automatic labelling | Manual labelling is E3. Auto-application by trainable classifier is not. Any labelling programme that depends on users choosing correctly at scale will not hold, so this is the one that decides whether a data protection programme is real. |
Worth knowing
If two of those three are what you are buying, price the Microsoft Purview Suite add-on against the full E5 uplift before deciding. Purview Suite is £9.20 per user per month on an annual subscription, excluding VAT, and sits on top of E3. E5 also brings Defender P2, Entra ID P2 and Teams Phone, so the question is whether you need the security and telephony half at all. The identity half is priced out in Entra ID P1 vs P2.
Where the money usually is, and it is not the uplift
One line in Microsoft’s service description is worth more than most licensing reviews. For shared locations such as SharePoint sites, Microsoft 365 Groups and Teams channel messages, users holding owner or member roles need the licence. Users with visitor or view-only roles do not. That is the Microsoft Purview service description talking, and it is worth reading the exact plan column yourself.
In an estate with a large read-only population, that single distinction is often larger than the E3 to E5 delta you were arguing about.
The endpoint half of that gap is Defender for Endpoint Plan 1 in E3 against Plan 2 in E5; what Plan 2 adds over Plan 1 covers it, including mixed mode for a phased move.
Microsoft’s pricing page now lists the Intune Plan 2 capabilities as part of both plans, which changes whether anyone on E3 should still buy them: Intune Plan 1 vs Plan 2 after the E3 change.
Two things that fail without telling you
Most licensing gaps present as a blocked button. These two do not, which is why they survive licensing reviews.
Customer Key reverts to default encryption. Data encryption policies apply at tenant level, so the tenant needs at least as many Customer Key licences as it has users assigned Exchange or Teams licences, whichever is greater, with SharePoint counted separately. Microsoft validates periodically. If you are short, encryption quietly falls back to the default service encryption while the configuration stays exactly where you left it.
Shared and resource mailboxes need licences to receive several features, despite nobody signing into them. Inactive mailboxes do not. Estates that lean on shared mailboxes accumulate silent non-coverage this way.
For mail-only users the standalone route is set out in the comparison of the two standalone Exchange Online plans.
The Windows layer of the same decision is narrower than it looks: what Windows Enterprise E5 adds over E3 is Defender for Endpoint Plan 2, and nothing else on Microsoft’s licensing page.
The newsletter
Get the next licensing fix like this one by email
Subscribe and get the free 8-page Intune troubleshooting field guide (PDF), then new fixes about twice a month. From a Microsoft MVP.
Auditing what you already own
Do this before any renewal conversation. SKU display names are unreliable and marketing names change; service plan names do not.
# Requires Microsoft.Graph.Identity.DirectoryManagement.
Connect-MgGraph -Scopes 'Organization.Read.All'
Get-MgSubscribedSku -All |
Select-Object SkuPartNumber,
@{ n = 'Purchased'; e = { $_.PrepaidUnits.Enabled } },
ConsumedUnits,
@{ n = 'Unused'; e = { $_.PrepaidUnits.Enabled - $_.ConsumedUnits } },
@{ n = 'Waste%'; e = {
if ($_.PrepaidUnits.Enabled -gt 0) {
[math]::Round( (($_.PrepaidUnits.Enabled - $_.ConsumedUnits) / $_.PrepaidUnits.Enabled) * 100, 1 )
} else { 0 }
} } |
Sort-Object Waste% -Descending |
Format-Table -AutoSize
Anything above roughly 10 per cent unused is either a migration remnant or a renewal nobody questioned. Fix that before you argue about tiers.
For the step up from the small business plan, see Business Premium vs E5 for organisations nearing 300 users.
Both E3 and E5 include Intune, so the device management question between them is usually about the advanced capabilities rather than the base service. See how Intune licensing splits across Plan 1, Plan 2 and the Suite.
Below E3 sits Office 365 E1, which loses the desktop apps, the larger mailbox and Litigation Hold: when E1 is enough and when it is a false saving.
Defender for Identity is one of the E5 items an E3 tenant can buy on its own; the Defender for Identity licensing options compares the standalone route with the bundles.
What I would do
Write down the three capabilities you will genuinely operate in the next six months. Find each one in Microsoft’s service description and read the exact plan column rather than a comparison chart. Two of the three are usually already covered by E3.
Two capabilities crossed into E5 on 1 July 2026 that did not use to be there, which changes the arithmetic for anyone who was already paying for them separately. The Endpoint Privilege Management cost is the clearest example, because a standalone add-on bought before that date keeps billing without anything in the portal pointing out the overlap. Cloud PKI crossed into E5 on the same date, so the same check applies to anyone still billed for its $2.00 add-on.
If the third is a compliance capability, price Purview Suite against E5 before committing. If it is Defender P2 or Entra ID P2, E5 is probably the cleaner answer. Entra ID P2 is also what Conditional Access policy design assumes you hold. And if Defender is the driver, decide which channel owns its settings before you buy: Defender Controlled Configuration. Either way, run the headroom script first, because unused licences are found money and they do not require a negotiation.



