Over-Licensing Is More Common Than Under-Licensing
The Microsoft compliance conversation in most enterprises focuses almost entirely on under-licensing risk — the threat of audit, the cost of true-up overages, the liability of running software without coverage. Under-licensing is a real risk and deserves serious attention. But for the majority of enterprises we engage, the larger immediate financial problem is not what they are missing but what they are paying for that they do not need.
Over-licensing — maintaining committed licence baselines that exceed actual deployment — is endemic to enterprise Microsoft estates. It accumulates through four consistent mechanisms: EA commitments made at inflated headcount projections that were never revised as growth slowed; add-on products purchased at scale that were never fully deployed; acquired entities whose licence estates were absorbed without rationalisation; and product SKU choices made during previous contract cycles that have since been superseded by more cost-efficient options.
The three-year EA commitment structure means over-licensing does not self-correct. Once you have committed to a licence count, you pay for it until the next renewal — regardless of how many seats remain undeployed. Over a three-year term on a 5,000-seat estate with 20% over-licensing on M365 E3, the cumulative waste is approximately £600,000 at current rates. That figure sits unrecovered in most enterprises because no one has done the analysis to surface it.
Four Over-Licensing Waste Categories
Category 1: Stale Account Licence Waste
Every enterprise accumulates user accounts that remain active in Entra ID or Active Directory long after the individuals have left the organisation. These accounts consume licences in the true-up count because they have not been de-provisioned. The stale account problem is not primarily a security issue — though it is also a significant security risk. It is a licence waste issue: you are paying for Microsoft 365, Exchange, SharePoint, and Teams licences for users who have not worked at your organisation for months or years.
Industry benchmarks suggest 8–15% of enterprise Entra ID accounts are stale by any reasonable definition — not logged in within 90 days, associated with departed employees per HR records, or provisioned for roles that no longer exist. On a 5,000-user estate, 10% stale accounts represent 500 unnecessary licence commitments. On M365 E3 at £200/user/year, that is £100,000 in annual waste before considering add-on products.
The stale account remediation process is covered in detail in our 2026 true-up preparation guide — the six-week sprint specifically prioritises stale account identification and de-provisioning before the annual true-up submission closes.
Category 2: Unused Add-On and SKU Waste
Add-on products purchased via EA amendment — additional security licences, Teams Phone, Visio or Project licences, compliance add-ons — are frequently deployed at rates significantly below the committed seat count. The committed seat count in the amendment becomes the true-up baseline; actual deployment is irrelevant to the true-up obligation until renewal.
The gap between committed and deployed add-on seats is the most consistently recoverable waste in enterprise Microsoft estates. A common pattern: an organisation purchases 2,000 Microsoft Defender for Identity licences following a security incident. 18 months later, deployment has reached 850 seats. The remaining 1,150 committed seats — at £15/user/month — represent £207,000 in annual waste that continues until renewal.
Add-on waste is recoverable at renewal through committed seat reduction, but only if the deployment data is documented and presented as part of the renewal negotiation. If you arrive at renewal without this analysis, Microsoft's account team will maintain the committed baseline by default. Read our M365 licence harvesting guide for the full methodology across all add-on categories.
Category 3: SKU Over-Specification Waste
Enterprise agreements frequently contain a uniform SKU commitment across all users in a qualifying population — most commonly M365 E5 or E3 applied to every employee regardless of actual product use. The reality of enterprise Microsoft deployment is that not all users have equivalent software needs. A significant portion of most enterprise user populations — typically 25–40% — can be adequately served by a lighter SKU: M365 F3 (frontline worker) at £6.20/user/month instead of E3 at £29.40/user/month, or M365 E3 instead of E5 where the E5 security and compliance capabilities are either unused or duplicated by third-party products already in the estate.
SKU over-specification waste is politically complex — it requires challenging procurement decisions that were made by senior stakeholders during the previous renewal — but the financial case is clear. A 5,000-user estate where 1,500 users could be correctly served by F3 rather than E3 represents £345,000 in annual over-spend. Our frontline worker licensing guide and E3 vs E5 comparison guide cover the segmentation methodology in detail.
Category 4: Software Assurance Value Waste
Software Assurance adds a significant premium to on-premises licence costs — typically 25–35% of the base licence value annually. The SA premium is justified when organisations actively use SA benefits: Azure Hybrid Use Benefit, Extended Security Updates, step-up licensing rights, home use programme, and virtualisation coverage. When SA-dependent benefits are not being used, the SA premium is pure waste.
In practice, many enterprises have SA coverage on large pools of on-premises licences and are using one or two SA benefits — typically AHUB — while the remainder of the SA benefit catalogue sits unclaimed. A rigorous SA value analysis, covering benefit-by-benefit utilisation across the estate, identifies the SA coverage that can be eliminated at renewal without operational impact. Our Software Assurance value guide covers the full benefit-by-benefit analysis methodology.
Quantifying the Waste: The Licence Waste Audit
Before you can recover over-licensing waste, you need to quantify it precisely by product line. Vague claims about over-licensing do not move Microsoft's account team at renewal. A product-by-product waste analysis with documented deployment figures and a proposed reduction for each line item is the instrument that creates the commercial case.
| Waste Category | Primary Data Source | Key Metric | Typical Waste Range |
|---|---|---|---|
| Stale user accounts | Entra ID last-sign-in report; HR leavers list | Accounts inactive 90+ days | 8–15% of total user count |
| Unused M365 add-ons | M365 admin centre Usage Reports | Assigned vs. active users per add-on | 20–45% of committed add-on seats |
| E5 over-specification | M365 admin centre per-feature usage; Security Centre | E5-exclusive feature activation rate | 15–30% of E5 seats replaceable with E3 |
| Frontline over-specification | Teams usage by role; device assignment data | E3/E5 seats in non-knowledge-worker roles | 10–25% of estate potentially F3-eligible |
| SA benefit non-utilisation | SA benefit redemption records; Azure AHUB tags | Benefit value claimed vs. SA premium paid | 40–70% of SA value unclaimed in average estate |
| Project/Visio excess | M365 admin centre; application usage logs | Active users vs. assigned seats | 25–50% of assigned seats unused |
Recovery Timing: The EA Term Constraint
Over-licensing waste cannot typically be recovered during an EA term. The EA baseline commitment — the minimum licence count you agreed to at signing or amendment — cannot be reduced unilaterally. You are committed to paying for those licences for the duration of the term regardless of whether you deploy them.
The recovery window is renewal. This is why the timing of waste quantification work matters so much. Waste analysis conducted nine to twelve months before EA expiry gives you the maximum window to document the over-licensing position, build the commercial case, and present it to Microsoft's account team before the renewal negotiation opens.
Waste analysis conducted in the final 90 days before expiry is useful but constrained. Microsoft's renewal process — including internal pricing approvals — requires time. Arriving at the negotiation table with a licence waste analysis when there is insufficient runway for Microsoft to formally process the resulting changes limits the discount improvement you can extract.
The Exception: Mid-Term True-Up Amendment
There is one partial exception to the renewal-only recovery constraint. If you have add-on products committed at a count that significantly exceeds deployment, and you have more than 12 months remaining on your EA term, a mid-term true-up amendment can sometimes reduce the committed add-on count. This is not a standard Microsoft offer — it requires making the case that the original commitment was based on deployment projections that have materially changed. Success rates are variable, and Microsoft typically requires a corresponding increase elsewhere in the estate as a condition of reduction. But for large add-on overcommitments, the attempt is worth making.
Microsoft's Standard Objections to Waste Recovery
When you present a waste analysis at renewal, Microsoft's account team will deploy several standard objections. Understanding these in advance allows you to prepare the counter-argument before the negotiation begins.
"These licences are committed — you agreed to them."
True for the current term. Not relevant for the renewal term. The renewal is a new commitment decision. The waste documentation shows you should not recommit to the same baseline.
"Your deployment will grow — you need buffer."
Counter with your actual three-year deployment trend data. If peak deployment has been consistently below the committed baseline, the growth argument is speculative. Commit to a renewed baseline that reflects actual deployment reality, with a defined process for mid-term amendment if growth accelerates beyond projections.
"Reducing the count will affect your EA pricing tier."
Run the pricing tier analysis before the negotiation. If tier reduction is a real risk — and it sometimes is — quantify the pricing tier impact against the waste cost savings. In most cases, the waste savings exceed the tier pricing degradation even when accounting for the tier change effect.
"These add-ons were purchased as part of a package — they can't be removed individually."
This is sometimes true — certain bundle structures do limit individual component reduction. Have your EA amendment terms reviewed before accepting this objection. In many cases, the bundle constraint applies only to the initial term commitment and not to the renewal structure.
Over-licensing waste analysis is not just a cost recovery exercise — it is a negotiation leverage instrument. When you can document precisely that you are paying for 1,200 seats that you have never deployed, Microsoft faces a choice: help you right-size the renewal, or lose you to a competitive evaluation that would allow you to restructure from scratch. This framing — documented waste as evidence that you have choices — shifts the renewal dynamic in ways that affect not just the seat count discussion but the unit pricing, term structure, and add-on commitment discussions as well.
The Five-Step Over-Licensing Recovery Process
The complete recovery methodology moves from data collection to renewal negotiation in five defined steps.
Step 1: Inventory your deployment reality. Pull M365 admin centre usage reports, Entra ID last-sign-in data, Teams usage data, and security product activation data for every product in your EA. This is your actual deployment picture — what is genuinely in use versus what you are paying for.
Step 2: Map deployment against commitment. Take your EA order form and compare committed seat counts against your actual deployment figures for each product line. The gaps are your waste opportunities.
Step 3: Validate and segment the waste. Not all deployment gaps are reclaimable. Some represent users who are provisioned but infrequent — a genuine active user, not stale. Some represent growth buffer that is legitimately needed. Segment your waste into confirmed recoverable (stale accounts, zero-deployment add-ons), probable recoverable (low-activity users, over-specified SKUs), and indeterminate (potential growth). The confirmed and probable categories form your waste case; the indeterminate category becomes your buffer argument.
Step 4: Quantify the financial value. Calculate the annual cost of each waste category at your current EA unit prices. Sum the confirmed and probable categories for your total recoverable waste figure. This is the number you present at renewal.
Step 5: Build into the renewal negotiation framework. Waste analysis is most powerful when integrated with the broader renewal strategy — combined with true-up history leverage, competitive positioning, and term structure preferences. Our true-up leverage guide and licence count reduction guide cover the integration of waste analysis with the full renewal framework.