Every enterprise reviews its headcount annually. Every enterprise reviews its real estate annually. Almost none review their Microsoft 365 licence assignments annually. The cost of that oversight is 20–30% of total Microsoft spend, hiding in plain sight inside the Enterprise Agreement. This is the complete playbook for eliminating that waste — every tactic, every tool, every sequence — without removing a single capability from a single user who actually needs it.
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, detection method, and remediation approach. Understanding the anatomy is essential because the tactics that eliminate one source are different from those that eliminate another.
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 entirely wasted.
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.
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.
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.
True-up overages, suboptimal agreement types, misconfigured Azure commitments, and Unified Support pricing that has not been renegotiated.
Cost-cutting removes capability. Optimisation removes waste. Every tactic in this playbook preserves the user’s functional experience — no worker loses access to a tool they actually use. The savings come entirely from eliminating licences that are not used, downgrading plans where premium features are not consumed, and restructuring agreements where the commercial terms are suboptimal. If any user’s day-to-day experience changes, the optimisation has been executed incorrectly.
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.
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.
Post-M&A duplicate accounts: User accounts created in the new tenant before legacy accounts are deprovisioned — creating double licensing. Contractor and temp accounts: Created for project durations, never removed when projects end. 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 at $36/month for a resource that should cost $0. Seasonal workforce: Retail and hospitality organisations retaining licences for workers who will not return for 6–9 months.
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, 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.
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.
| Downgrade Path | Saving Per User/Month | Annual Per-User Saving | Example: 2,000 Users |
|---|---|---|---|
| E5 → E3 | ~$21 | $252 | $504,000/year |
| E3 → F3 | ~$28 | $336 | $672,000/year |
| E3 → F1 | ~$33.75 | $405 | $810,000/year |
| E3 → Business Standard | ~$23.50 | $282 | $564,000/year |
The E5-to-E3 downgrade is viable for any user who does not actively use E5-exclusive features: Microsoft Defender for Office 365 Plan 2, Cloud App Security, Phone System and Audio Conferencing, advanced eDiscovery, advanced Information Protection, and the full Defender for Endpoint suite. In our experience, 30–50% of E5 users do not consume any E5-exclusive feature. For organisations that need specific E5 features for a subset of users, a targeted E5 add-on on top of E3 is often 40–60% cheaper than full E5.
F3 is designed for frontline workers on shared workstations who do not need 50GB mailboxes, personal-device Office, eDiscovery, or advanced compliance. F1 is for workers who use only Teams, Shifts, and web/mobile Office on shared or personal mobile devices. For organisations with 5,000+ frontline workers on E3, the F3 downgrade alone delivers $1.5M+ annually.
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, Audio Conferencing, advanced eDiscovery, or Cloud App Security is an E3 downgrade candidate — regardless of their job title.
Model the savings from SKU right-sizing, ghost licence purges, and redundant licence elimination with our interactive optimisation calculator.
Use the Calculator →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.
| Redundancy | Included In | Standalone Cost Wasted |
|---|---|---|
| Power BI Pro + E5 | E5 includes Power BI Pro | $10/user/month |
| Exchange Online Plan 2 + E3/E5 | E3/E5 includes Exchange Online P2 | $8/user/month |
| Azure AD P1 + E3/E5 | E3/E5 includes Entra ID P1 | $6/user/month |
| Intune Plan 1 + E3/E5 | E3/E5 includes Intune P1 | $8/user/month |
| Defender for Office 365 P1 + E5 | E5 includes Defender P2 (supersedes P1) | $2/user/month |
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.
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.
Teams add-ons post-unbundling: 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. Power Platform licences: Per-user licences may overlap with capacity-based licences or with Power Automate entitlements included in M365 plans. Legacy Visio/Project Online: Purchased for teams that have since migrated to alternative tools.
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 (with every true-up and every price increase), your Unified Support fee grows proportionally — even if your support consumption is flat or declining.
Evaluate whether you are on Core, Advanced, or Performance tier. Most organisations are on a tier higher than their support consumption justifies. The tier comparison guide provides the decision framework.
The percentage of Microsoft spend that determines the Unified Support fee is negotiable. Competitive quotes from third-party support providers create downward pressure. Providers like US Cloud offer Microsoft Premier-equivalent support at 30–60% below Unified Support pricing.
Renegotiating Unified Support concurrently with the EA creates combined negotiation leverage. See the support-EA alignment guide for the methodology.
Typical savings: 20–50% of Azure compute spend. Implementation risk: Low. Time to execute: 2–4 weeks.
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 are not applied — Azure VMs running at the full “licence included” rate when a BYOL rate is available. The fix is configuration, not purchasing.
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.
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 do not use) and under-commitment (missing available discounts).
Typical savings: 3–8% of total EA spend. Implementation risk: Low. Time to execute: Aligned with EA renewal (12–18 month planning horizon).
The EA vs CSP vs MCA decision has evolved significantly. 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.
EA true-ups are annual reconciliations where you report (and pay for) licences deployed beyond your contracted baseline. Poor true-up governance creates overpayment through several mechanisms: licences added mid-year that are reported at true-up but were not needed for the full year (you pay the full annual price for 6 months of use), headcount reductions that are not reflected in the true-up (you pay for departed users until the EA term ends), and duplicated licences across tenants or subsidiaries.
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. Price protection clauses — caps, locks, and freeze provisions — limit Microsoft’s ability to increase pricing at renewal and should be negotiated into every EA.
Our independent Microsoft advisory helps enterprises negotiate optimal EA terms, benchmark discount levels, and build commercial frameworks that deliver maximum value.
Microsoft Negotiation Service →Every optimisation tactic in this playbook delivers immediate savings. None delivers permanent savings — because Microsoft 365 waste is not a one-time problem. It is 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.
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 at the root.
Pull Microsoft 365 usage reports quarterly and compare actual usage against assigned SKUs. Identify new E5/E3 users who are not 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.
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.
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.
| 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 |
Ghost purge saves $500K–$1.5M. SKU right-sizing saves $1M–$2M. Redundant elimination saves $300K–$800K. Add-on rationalisation saves $200K–$500K. Unified Support saves $100K–$300K. Azure AHB/RI saves $400K–$1M on Azure compute. EA structure saves $300K–$800K. Total estimated savings: $2.8M–$6.9M annually — though the realistic range for a well-run enterprise is 20–35%. The savings are recurring: they reduce the baseline from which future renewals, true-ups, and price increases are calculated.
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. 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, negotiate these provisions before signing.
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.
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.
Ghost licence purges should run continuously via automated deprovisioning (triggered by HR events) with a monthly manual sweep. SKU right-sizing should run quarterly. Redundant licence and add-on reviews should run quarterly alongside the SKU review. Azure AHB and RI reviews should run monthly. 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.
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 is $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 do not have.
Redress Compliance provides independent Microsoft licensing advisory. We identify 20-30% waste, build the remediation plan, and negotiate optimised quantities into your EA renewal. Fixed-fee, 100% vendor-independent.