Microsoft 365 E5 vs E3: should you downgrade? (2026 savings math)

Microsoft 365 cost optimization · ~6 min read

Microsoft 365 E5 lists at $60 per user/month in 2026; E3 lists at $39. That's a $21/user/month gap — $252 a year, per seat. On any tenant that rolled out E5 broadly "to be safe," a chunk of those seats are paying for capabilities nobody touches. This guide covers what E5 actually adds, how to spot users who'd be fine on E3, and how to validate before you downgrade.

What E5 adds over E3

E3 already includes the Office apps, Exchange, SharePoint, OneDrive, Teams, and a solid baseline of security and compliance. E5 layers on the premium tiers that most organizations only partly use:

The question is never "is E5 better?" — it obviously is. It's "is each E5 seat using enough of those extras to justify $21/month over E3?" For a lot of seats, the honest answer is no.

Who genuinely needs E5

Keep E5 where the premium features are actually load-bearing:

Everyone else — standard knowledge workers who open Office, email, and Teams — is usually a clean E3 (or even Business Premium under 300 seats) candidate.

The downgrade math

DowngradeSaving / user / moSaving / user / yr
E5 → E3$21$252
E3 → Business Premium*$17$204

*Business Premium ($22/user/mo) is only available up to 300 seats and has feature differences — validate fit before moving.

Move 25 over-provisioned users from E5 to E3 and that's $6,300/year. The savings scale linearly, and they recur every year.

How to find downgrade candidates (read-only)

Start by listing who holds E5, then layer on usage signals so you only flag people who clearly aren't using the premium features. With the Microsoft Graph PowerShell SDK:

Connect-MgGraph -Scopes "Organization.Read.All","User.Read.All","Reports.Read.All"

# Everyone on Microsoft 365 E5 (skuPartNumber SPE_E5)
$e5 = (Get-MgSubscribedSku | Where-Object SkuPartNumber -eq 'SPE_E5').SkuId
Get-MgUser -All -Property displayName,userPrincipalName,assignedLicenses |
  Where-Object { $_.AssignedLicenses.SkuId -contains $e5 } |
  Select-Object displayName, userPrincipalName

Then cross-reference against usage: who actually signs into the security/compliance portals, who has Power BI Pro activity, who's enabled for Teams Phone. Microsoft 365 usage reports and the Defender/Purview portals show this. Anyone on E5 with no premium-feature footprint is a downgrade candidate to review with the business owner.

Validate before you cut. A downgrade is a real change — confirm a user isn't relying on an E5-only feature (a compliance hold, a Defender policy, Teams calling) before reassigning. Treat the candidate list as a review queue, not an auto-action.

Let SeatScout build the list for you

SeatScout flags E5→E3 downgrade candidates automatically (alongside unused, inactive, and disabled-but-licensed seats) and quantifies the savings in dollars — read-only, entirely inside your own tenant. Free tier available.

Get SeatScout →

Related: How to find wasted Microsoft 365 licenses (2026 guide) →

Prices are Microsoft public list prices effective July 1, 2026 (USD); your contracted/regional price may differ. SeatScout is independent and not affiliated with Microsoft.