Microsoft 365 Licence Optimisation Assessment
We analyse every licence in your Microsoft estate, identify the 20–30% waste, build the remediation plan, and negotiate the optimised quantities into your EA renewal — delivering measurable, recurring savings.
1. The Anatomy of Microsoft 365 Waste
Microsoft 365 licence waste follows a predictable pattern that we observe in virtually every enterprise engagement. The waste has five distinct sources, each with its own root cause, its own detection method, and its own remediation approach. Understanding the anatomy is essential because the tactics that eliminate one source of waste are different from those that eliminate another — and applying the wrong tactic to the wrong source either fails or creates new problems.
Source 1 — Ghost licences (5–15% of spend): Active subscriptions assigned to users who no longer exist in the organisation. Departed employees, completed contractors, merged accounts after M&A, test accounts that were never deprovisioned. These licences generate zero value — they are not over-provisioned; they are not suboptimal; they are entirely wasted. Source 2 — SKU mismatch (10–20% of spend): Users assigned to a higher-tier plan than their usage justifies. E5 users who don't touch advanced compliance or voice features. E3 users who only use Teams and email. Knowledge worker licences assigned to frontline populations. Source 3 — Redundant licences (3–8% of spend): Capabilities purchased twice — a standalone Power BI Pro licence for a user who already has it included in E5, or an Exchange Online Plan 2 licence for a mailbox covered by a user's E3 subscription. Source 4 — Add-on sprawl (2–5% of spend): Point-solution add-ons purchased to address specific requirements that have since been bundled into the base plan or made redundant by a platform upgrade. Source 5 — Structural EA inefficiency (3–8% of spend): True-up overages, suboptimal agreement types, misconfigured Azure commitments, and Unified Support pricing that hasn't been renegotiated.
Combined, these five sources typically account for 20–30% of total Microsoft 365 spend — a range we have validated across hundreds of enterprise engagements spanning retail, healthcare, financial services, manufacturing, technology, and professional services. For the most common Microsoft licensing mistakes and the broader optimisation context, see our Microsoft Optimisation Services overview.
2. Tactic 1: Ghost Licence Purge
Typical savings: 5–15% of Microsoft 365 spend. Implementation risk: Zero. Time to execute: 2–4 weeks.
Ghost licences are the lowest-hanging fruit in Microsoft optimisation — they represent pure waste with zero functional impact when removed. Yet most organisations have never conducted a systematic ghost licence purge because the provisioning process that creates accounts is never paired with a deprovisioning process that removes them. Learn more about independent Microsoft advisory services.
How to Find Ghost Licences
Pull the Microsoft 365 licence assignment report from the admin centre or via Microsoft Graph API. Cross-reference against your HR system's active employee list. Any licence assigned to a user not in the active employee list is a ghost candidate. Additionally, pull the sign-in activity report: any licensed user with zero sign-in activity in the past 90 days is a ghost candidate regardless of HR status (the HR system may not have caught the departure, or the user may be a test/service account that was never cleaned up).
Where Ghost Licences Hide
Post-M&A duplicate accounts: When organisations merge, user accounts are often created in the new tenant before the legacy tenant accounts are deprovisioned — creating a window where the same person holds licences in both tenants. See our guide on Microsoft licensing in M&A. Contractor and temp accounts: Created for project durations, never removed when the project ends. Shared mailboxes with unnecessary licences: Shared mailboxes in Exchange Online do not require a licence (up to 50GB) — yet we routinely find shared mailboxes holding E3 licences that cost $36/month for a resource that should cost $0. Seasonal workforce: Retail and hospitality organisations with seasonal hiring cycles frequently retain licences for workers who won't return for 6–9 months.
Scenario: The 1,200 Ghosts
A professional services firm with 9,500 Microsoft 365 E3 licences engaged our licence usage audit. The analysis identified: 680 licences assigned to users not in the active HR system, 320 licences with zero sign-in activity in 180+ days (confirmed as departed employees missed by HR sync), 140 shared mailboxes holding E3 licences unnecessarily, and 60 test/service accounts. Total ghost licences: 1,200 (12.6%). Annual waste: 1,200 × $432 = $518,400. Remediated in 3 weeks with zero impact on any active user.
3. Tactic 2: SKU Right-Sizing (E5 → E3 → F3 → F1)
Typical savings: 10–20% of Microsoft 365 spend. Implementation risk: Low. Time to execute: 4–8 weeks.
SKU right-sizing is the highest-value single tactic in Microsoft 365 optimisation — and the one that requires the most analytical rigour to execute correctly. The objective: ensure every user is on the lowest-cost plan that provides every capability they actually use. See our complete E3 vs E5 vs F3 comparison and plan selection playbook for the decision framework.
The Four Downgrade Paths
E5 → E3: The E5-to-E3 downgrade is viable for any user who doesn't actively use E5-exclusive features: Microsoft Defender for Office 365 Plan 2, Cloud App Security, Phone System and Audio Conferencing (PSTN calling), advanced eDiscovery, advanced Information Protection, and the full Defender for Endpoint suite. In our experience, 30–50% of E5 users don't consume any E5-exclusive feature. The per-user saving is approximately $21/month ($252/year). For 2,000 users: $504,000 annually. For organisations that need specific E5 features for a subset of users, a targeted E5 add-on (like a standalone Defender for Endpoint P2 licence or a Compliance add-on) on top of E3 is often 40–60% cheaper than full E5. See our E5 security add-ons playbook for the component-by-component analysis.
E3 → F3: For frontline workers who use shared workstations with desktop Office apps, Windows Enterprise rights, and moderate email — but don't need 50GB mailboxes, personal-device Office, eDiscovery, or advanced compliance. The saving is $28/user/month ($336/year). For organisations with 5,000+ frontline workers on E3, this single downgrade delivers $1.5M+ annually. Learn more about Microsoft 365 licensing costs per user in 2026.
E3 → F1: For frontline workers who use only Teams, Shifts, and web/mobile Office on shared or personal mobile devices — no desktop apps, no significant email or file storage. The saving is $33.75/user/month ($405/year). This is the largest per-user saving available in Microsoft 365 SKU optimisation.
E3 → Business Standard/Premium: For small offices, subsidiaries, or acquired entities with fewer than 300 users that don't need enterprise-grade compliance features. Business plans offer the same core productivity apps at lower pricing and with simpler administration. This path is relevant during M&A integration when acquired entities are being onboarded to the parent's Microsoft environment.
How to Identify Downgrade Candidates
Microsoft 365 usage reports (available in the admin centre and via Graph API) provide per-user activity data: which apps each user has used in the past 30/90/180 days, email send/receive volume, Teams meeting participation, SharePoint file access, and OneDrive storage consumption. Cross-reference this usage data against the features exclusive to each SKU tier. A user on E5 who has never used Defender for Endpoint, never used Audio Conferencing, never used advanced eDiscovery, and never used Cloud App Security is an E3 downgrade candidate — regardless of their job title. Use our M365 Licence Optimisation Calculator to automate this analysis.
4. Tactic 3: Redundant Licence Elimination
Typical savings: 3–8% of Microsoft 365 spend. Implementation risk: Zero. Time to execute: 1–2 weeks.
Microsoft's product portfolio is a maze of overlapping capabilities — and the overlaps create situations where organisations pay for the same functionality twice. The most common redundancies, per our redundant licence elimination guide:
Power BI Pro bundled in E5 + standalone: E5 includes Power BI Pro. Organisations that purchased standalone Power BI Pro licences before upgrading to E5 often retain both — paying $10/user/month for a capability already included. Exchange Online Plan 2 + E3/E5: E3 includes Exchange Online Plan 2. Legacy Exchange licences purchased before the M365 migration may still be active. Azure Active Directory P1 + E3/E5: E3 and E5 include Entra ID (formerly Azure AD) P1. Standalone AAD P1 licences purchased for specific security projects may still be assigned alongside the M365 licence. Microsoft Intune + E3/E5: E3 and E5 include Intune Plan 1. Standalone Intune licences from pre-M365 deployments frequently persist. Defender for Office 365 Plan 1 + E5: E5 includes Defender Plan 2 (which supersedes Plan 1). Standalone Plan 1 licences purchased as E3 add-ons that weren't removed when users upgraded to E5. For details, see our endpoint management licensing guide. Learn more about Microsoft 365 price increases and how to avoid overpaying.
The diagnostic is straightforward: export all licence assignments per user, identify users with overlapping SKUs, and remove the redundant SKU. There is zero functional impact — the user retains the capability through their higher-tier licence. The only risk is removing the wrong one (removing the E5 instead of the standalone), so validate before executing.
5. Tactic 4: Add-On Rationalisation
Typical savings: 2–5% of Microsoft 365 spend. Implementation risk: Low. Time to execute: 2–4 weeks.
Enterprise Microsoft environments accumulate add-on subscriptions over time — each purchased to address a specific need at a specific moment. Some of those needs no longer exist. Some add-ons have been superseded by capabilities now included in the base plan. Some were purchased for a project that ended two years ago.
Common Add-On Waste
Teams add-ons post-unbundling: The Teams unbundling from Office 365 in certain markets created add-on complexity. Some organisations now hold Teams add-on licences alongside M365 plans that already include Teams — paying twice for the same service. Copilot licences with low adoption: Organisations that rolled out Microsoft 365 Copilot broadly may find that only 30–50% of licensed users are actively using it. At $30/user/month, inactive Copilot licences are expensive — reassign them to active users or reduce the commitment at renewal. Use our Copilot ROI Assessment to measure actual adoption. Power Platform licences: Power Platform per-user licences may overlap with capacity-based licences or with Power Automate entitlements included in M365 plans. Legacy Visio/Project Online subscriptions: Purchased for specific teams that have since migrated to alternative tools or stopped using the product.
Need Expert Microsoft Licensing Guidance?
Redress Compliance provides independent Microsoft licensing advisory — fixed-fee, no vendor affiliations. Our specialists help enterprises optimize Microsoft costs, negotiate better EA terms, and ensure compliance.
Explore Microsoft Advisory Services →6. Tactic 5: Unified Support Optimisation
Typical savings: 10–30% of Unified Support cost. Implementation risk: Zero. Time to execute: 4–8 weeks (aligned with support renewal).
Microsoft Unified Support is priced as a percentage of your Microsoft spend — typically 5–10% of your total enterprise Microsoft licensing. As your Microsoft spend grows (and it does, with every true-up and every price increase), your Unified Support fee grows proportionally — even if your support consumption is flat or declining.
Optimisation tactics: tier right-sizing (evaluate whether you're on Core, Advanced, or Performance tier — most organisations are on a tier higher than their support consumption justifies; see our Unified Support tier comparison), base amount renegotiation (the percentage of Microsoft spend that determines the Unified Support fee is negotiable — competitive quotes from third-party support providers create downward pressure), third-party support alternatives (providers like US Cloud offer Microsoft Premier-equivalent support at 30–60% below Unified Support pricing; see our guide on alternatives to Unified Support), and alignment with EA renewal (renegotiating Unified Support concurrently with the EA creates combined negotiation leverage; see our support-EA alignment guide).
7. Tactic 6: Azure Hybrid Benefit and Reserved Instance Alignment
Typical savings: 20–50% of Azure compute spend. Implementation risk: Low. Time to execute: 2–4 weeks. Learn more about Microsoft EA negotiation guide.
This tactic extends beyond Microsoft 365 into Azure — but the licences that enable it are managed within the same EA, and the savings often exceed the Microsoft 365 optimisation savings themselves.
Azure Hybrid Benefit (AHB): Every Windows Server or SQL Server Per Core licence with active Software Assurance can be applied to Azure VMs, reducing compute costs by 40–80%. We consistently find organisations with eligible licences that aren't applied — Azure VMs running at the full "licence included" rate when a BYOL rate is available. The fix is configuration, not purchasing. See our Azure licensing and cost optimisation playbook.
Reserved Instances (RIs): Azure VMs running 24/7 (production databases, application servers, domain controllers) should be on 1- or 3-year Reserved Instances — saving 30–60% compared to pay-as-you-go pricing. Combined with AHB, RIs create compound savings of 60–80% on steady-state compute. See our Azure spend management guide.
MACC alignment: Microsoft Azure Consumption Commitment (MACC) provides a committed-spend discount on Azure services. Aligning your MACC commitment with actual consumption avoids both over-commitment (paying for Azure credits you don't use) and under-commitment (missing available discounts). See our Azure overage management guide for the governance framework.
8. Tactic 7: EA Structure and True-Up Optimisation
Typical savings: 3–8% of total EA spend. Implementation risk: Low. Time to execute: Aligned with EA renewal (12–18 month planning horizon). Learn more about Microsoft EA renewal preparation toolkit.
The commercial structure of your Enterprise Agreement itself contains optimisation opportunities that most organisations don't realise are negotiable.
Agreement Type Optimisation
Is your EA the right agreement type for your organisation? The EA vs CSP vs MCA decision has evolved significantly — particularly for organisations with fluctuating headcount. CSP provides monthly flexibility that the EA's annual true-up process cannot match. For organisations with seasonal workforces (retail, hospitality, agriculture), a hybrid EA + CSP approach can reduce costs by allowing subscription quantities to flex with headcount. The MCA framework offers additional structural options. See our renewal proposal evaluation playbook for the comparison.
True-Up Discipline
EA true-ups are annual reconciliations where you report (and pay for) licences deployed beyond your contracted baseline. Poor true-up governance — adding users throughout the year without tracking the licensing impact — creates overpayment through several mechanisms: licences added mid-year that are reported at true-up but weren't needed for the full year (you pay the full annual price for 6 months of use), headcount reductions that aren't reflected in the true-up (you pay for departed users until the EA term ends), and duplicated licences across tenants or subsidiaries that nobody reconciled. See our true-up cost avoidance guide and EA true-up guide.
Pricing and Discount Optimisation
Microsoft EA pricing is determined by pricing levels and tiers based on your organisation's total Microsoft spend. Moving between pricing tiers — by consolidating subsidiaries' spending into a single EA, or by restructuring your product mix — can unlock lower unit prices across the entire agreement. See our EA discount benchmarking guide and 2026 pricing playbook. Price protection clauses — caps, locks, and freeze provisions — limit Microsoft's ability to increase pricing at renewal and should be negotiated into every EA. For the complete set of negotiation tactics, see our key leverage points guide and EA negotiation strategies.
9. The Governance Framework: Preventing Waste From Returning
Every optimisation tactic in this playbook delivers immediate savings. None delivers permanent savings — because Microsoft 365 waste is not a one-time problem. It's a structural condition that regenerates naturally as employees join, leave, change roles, and adopt new tools. Without ongoing governance, an optimised estate drifts back to 15–20% waste within 12–18 months.
📊 Free Microsoft 365 Licence Optimisation Calculator
Calculate your potential savings with our free M365 optimization calculator. Identify redundant licences, right-size SKUs, and model cost reduction scenarios.
Use the Free Calculator →Monthly: Automated Deprovisioning
Connect your Microsoft 365 licence management to your HR system (or Entra ID) via automated workflows. When an employee status changes to "terminated" in HR, the workflow should: revoke the Microsoft 365 licence within 24 hours, convert the mailbox to a shared mailbox (free, retains email history for compliance), and transfer OneDrive files to the employee's manager or a designated archive. This single automation eliminates ghost licence accumulation — the largest source of waste — at the root.
Quarterly: Usage-Based SKU Review
Pull Microsoft 365 usage reports quarterly and compare actual usage against assigned SKUs. Identify: new E5/E3 users who aren't using tier-exclusive features (downgrade candidates), new ghost licences that slipped through automation gaps, new redundant licences created by project purchases, and new add-ons that overlap with existing entitlements. The quarterly cadence is the minimum effective frequency — faster than waste accumulates but infrequent enough to be operationally sustainable. Use our M365 Licence Optimisation Calculator as the analytical engine. Learn more about Microsoft audits and compliance playbook.
Annually: EA Alignment Review
Before each annual true-up, conduct a comprehensive review: reconcile licence assignments against the EA baseline, forecast next-year requirements based on headcount plans and project roadmaps, model the true-up cost and identify reduction opportunities, and prepare the EA renewal negotiation strategy if the renewal is within 18 months. For the annual cycle, see our ITAM compliance and optimisation guide and SAM and licence optimisation guide.
At Renewal: Full Optimisation Reset
The EA renewal is the single most important moment in the Microsoft licensing lifecycle — and the only moment where you can reduce committed quantities, change agreement structures, renegotiate pricing, and restructure the entire commercial relationship. Every optimisation tactic in this playbook should be executed and the results locked into the renewal terms. See our EA Renewal Readiness Assessment, EA Renewal Preparation Toolkit, and EA Renewal Playbook for the complete methodology.
| Tactic | Typical Savings | Risk Level | Time to Execute | Recurring? |
|---|---|---|---|---|
| Ghost licence purge | 5–15% | Zero | 2–4 weeks | Monthly (automated) |
| SKU right-sizing | 10–20% | Low | 4–8 weeks | Quarterly |
| Redundant licence elimination | 3–8% | Zero | 1–2 weeks | At onboarding + quarterly |
| Add-on rationalisation | 2–5% | Low | 2–4 weeks | Quarterly |
| Unified Support optimisation | 10–30% of support | Zero | 4–8 weeks | At support renewal |
| Azure AHB + RI alignment | 20–50% of Azure compute | Low | 2–4 weeks | Monthly (Azure review) |
| EA structure + true-up | 3–8% | Low | 12–18 month cycle | At EA renewal |
10. Frequently Asked Questions
Standard EA terms do not allow quantity reductions during the agreement term. You can add licences (at each annual true-up), but you cannot subtract them until the EA renews. This is why the renewal is the critical moment for optimisation — it's the only time you can reset the baseline to match your actual needs. However, there are exceptions: the CSP model offers monthly flexibility, and some EA negotiations can include step-down rights or early termination provisions. If mid-term flexibility is important for your organisation, negotiate these provisions before signing. See our Microsoft Contract Negotiation Service for guidance.
Reducing quantities at renewal is a contractual right — not a compliance risk. You are entitled to set your baseline at any level that matches or exceeds your actual deployment. However, Microsoft may conduct a licence compliance review around the renewal to verify that your actual usage matches your declared quantities. The best preparation: conduct your own internal audit before the renewal, ensure your deployment matches your proposed baseline, and remediate any over-deployment before Microsoft discovers it. Our Microsoft Audit Defence Service and Audit Survival Checklist provide the complete preparation framework.
Data beats opinion. Pull the Microsoft 365 usage reports for every E5 user and identify which E5-exclusive features each user has accessed in the past 90 days. Present the results: "Of our 3,000 E5 users, 1,400 have not used Audio Conferencing, Cloud App Security, advanced eDiscovery, or any other E5-exclusive feature in the past 90 days. Moving these 1,400 users to E3 saves $352,800 annually with zero impact on their work." The usage data makes the case objectively. No stakeholder will argue for paying $21/user/month for features their team demonstrably doesn't use — provided you can show the data. For the feature-by-feature comparison, see our E3 vs E5 vs F3 guide.
Ghost licence purges should run continuously via automated deprovisioning (triggered by HR events) with a monthly manual sweep for anything the automation missed. SKU right-sizing should run quarterly — frequent enough to catch changes in usage patterns but infrequent enough to allow meaningful data accumulation. Redundant licence and add-on reviews should run quarterly alongside the SKU review. Azure AHB and RI reviews should run monthly (Azure costs change rapidly with workload scaling). EA structural reviews should begin 18 months before renewal and intensify in the final 6 months. The full seven-tactic optimisation should run as a comprehensive exercise annually, with the quarterly cadence maintaining the gains between annual reviews. Learn more about Microsoft Copilot licensing guide 2026.
For any organisation spending $3M+ annually on Microsoft, independent advisory delivers measurable, immediate ROI. The typical advisory engagement identifies 20–30% savings — on a $5M annual spend, that's $1–$1.5M in recurring savings against an advisory fee that is a fraction of that amount. Internal teams can execute tactics 1–3 (ghost purge, SKU right-sizing, redundant elimination) with the right data tools, but tactics 5–7 (Unified Support, Azure alignment, EA structure) require pricing benchmarks, competitive intelligence, and negotiation expertise that most internal teams don't have. An independent advisor provides cross-client benchmarks (what comparable organisations pay Microsoft), negotiation support (leveraging EA renewal timing, competitive pressure, and structural optimisation), and implementation planning (prioritising tactics by ROI and sequencing them for maximum impact). At Redress Compliance, Microsoft 365 optimisation is our core Microsoft advisory service — we deliver the analysis, the negotiation, and the ongoing governance framework. Our EA Optimisation Service covers the full engagement, and the Microsoft Knowledge Hub provides additional self-service resources.