๐Ÿ’ณ Recipe ยท Licensing & Cost Optimization

Analyze E5 License Usage to Identify Downgrade Candidates to E3

Cross-reference E5-exclusive service usage with assigned licenses to find safe downgrade candidates and reduce licensing spend

Complexity

Advanced

Impact

cost-savings + licensing + reporting + governance + optimization

Context

Why This Matters

Microsoft 365 E5 licenses cost roughly 2x the price of E3, with the premium justified by exclusive workloads: Power BI Pro, Audio Conferencing, Phone System, Advanced eDiscovery, Microsoft Defender for Office 365 Plan 2, Defender for Endpoint Plan 2, Microsoft Purview (advanced), and Customer Lockbox. In most tenants, a meaningful percentage of E5 seats are assigned to users who never touch any of these E5-exclusive features โ€” pure license waste.

This recipe helps you systematically identify those users so Finance and IT can confidently downgrade them to E3 (or E3 + targeted add-ons) without breaking workflows or losing data. It is typically run:

  • During annual or quarterly true-up / renewal cycles
  • Before a Microsoft Enterprise Agreement renegotiation
  • As part of a cost-optimization initiative
  • After M&A activity when license inventories merge

The core technique is to cross-reference the list of E5 license holders against activity data from the Microsoft Graph usage reports (Power BI, Teams PSTN, Defender, Purview) over a 90-day window.

Expected Outcomes

You will produce:

  • A complete inventory of users assigned an E5 SKU in your tenant
  • A per-user utilization matrix showing which E5-exclusive services each user has actually used in the last 90 days
  • A downgrade candidate list โ€” users with zero E5-exclusive activity who can safely move to E3
  • A keep-as-E5 list โ€” users actively using at least one E5-exclusive feature
  • An estimated annual cost savings figure based on candidate count
  • A CSV export suitable for review by Finance, Security, and department managers before action

Typical savings

Organizations commonly find 20โ€“40% of their E5 seats are downgrade candidates, translating to tens of thousands of dollars in annual savings per 1,000 seats.

Risks & Considerations

โš ๏ธ Do not downgrade blindly

  • Data loss risk: Downgrading removes access to E5-only features. Power BI Pro content a user owns (workspaces, reports) may become inaccessible if no other Pro user inherits ownership. Always reassign ownership first.
  • Defender coverage gap: Removing Defender for Office 365 Plan 2 strips Safe Attachments/Safe Links advanced policies, Attack Simulator, and automated investigation from that user. Ensure tenant-wide Defender coverage or licensing gaps do not expose executives or high-value targets.
  • PSTN / phone numbers: If the user has a phone number assigned via Phone System (included in E5), downgrading strips calling. Numbers must be reassigned or the user moved to E3 + Teams Phone add-on.
  • Compliance obligations: Users under legal hold, advanced eDiscovery custodianship, or with Customer Key/Customer Lockbox requirements may legally require E5. Confirm with Legal/Compliance before acting.
  • Usage reports lag: Graph usage reports have a 24โ€“48 hour lag and a maximum 90-day window. A user who used Power BI once 100 days ago will not appear as active. Consider pulling multiple 90-day snapshots or combining with Power BI admin portal export.
  • Anonymized reports: If displayConcealedNames is true in report settings, UPNs will be redacted. You must toggle this off (tenant admin action, audit-logged) to attribute usage to individuals.
  • Pilot first: Always trial the downgrade on 5โ€“10 users for 2 weeks before bulk action.

Required Permissions

PermissionWhy It's Needed
Organization.Read.AllEnumerate subscribed SKUs and identify E5 vs E3 SKU IDs and service plans
User.Read.AllList users and their assigned license details to find E5 holders
Reports.Read.AllRead Office 365, Teams, Power BI, and Yammer activity reports to determine feature usage
Directory.Read.AllSupporting directory lookups for user attributes (department, manager) used in the candidate report
ReportSettings.ReadWrite.AllTemporarily disable report anonymization so usage can be attributed to named users

The fastest way to get this done โ€” just ask Dex. Copy the prompt below and paste it into your Dex conversation.

For IT Admins

Paste into Dex CoAdmin

Analyze our tenant's E5 license usage over the last 90 days. Identify users who are NOT using any E5-exclusive features (Power BI Pro, Audio Conferencing, Phone System, Defender P2, Advanced eDiscovery, Customer Key). Produce a CSV of safe downgrade candidates to E3, a keep-as-E5 list, and an estimated annual savings figure assuming E5 costs {annual_e5_cost} and E3 costs {annual_e3_cost} per user.
Try in Dex CoAdmin