Your Shelfware Overbuy Report is ready.

Thank you for registering. Your 22-page report is prepared for immediate access — naming the five Microsoft licenses enterprises most consistently overbuy, the measurement that separates assigned from actually used, and the reclaim sequence that turns the finding into a lower true-up and a smaller renewal commitment.

Shelfware Overbuy Report
PDF · 22 Pages · Updated June 2026
Download PDF Now
Why It Accumulates

Shelfware is not a mistake you made once. It is a state the Enterprise Agreement is built to maintain.

Every enterprise that has run a Microsoft Enterprise Agreement for more than one cycle is carrying shelfware — licensing it pays for and does not use. It accumulates for three structural reasons that have nothing to do with carelessness. First, the annual true-up only counts upward: you report and pay for growth, but you cannot return licenses mid-term, so any over-purchase rides forward as fixed cost. Second, your license records show assignment, not consumption — an E5 seat assigned to someone who only sends email reads as fully deployed in every standard report. Third, the people quoting you have a commercial incentive to sell ahead of need, and the November 2025 removal of programmatic EA volume discounts pushes harder toward higher committed quantities, not lower. Reclaiming shelfware is therefore a buyer-side discipline: it has to be measured by you, or by an independent advisor on your side of the table, and it has to be done before a renewal closes the window. This report names the five SKUs where the overspend concentrates and gives you the method to find and recover it.

SKU 1

Microsoft 365 E5 Assigned to Users Who Live in E3

E5 carries a substantial premium over E3 for security, compliance, analytics, and voice capabilities — Defender for Endpoint P2, advanced eDiscovery, Power BI Pro, audio conferencing, and the phone system. The premium is only worth paying where those capabilities are used. On the typical estate, a large block of E5 seats are assigned to information workers who touch none of them. The reclaim is not a blunt downgrade; it is a feature-activation analysis per user, stepping the non-consumers back to E3 plus targeted add-ons where a genuine need exists. Done at renewal, the committed quantity of E5 drops and the saving compounds across the term. Our Microsoft 365 optimization service runs exactly this measurement.

Where to look: the M365 admin centre usage and feature-activation reports, cross-referenced against assigned E5 seats. Genuine E5 utilisation below your threshold is the reclaim candidate list.
SKU 2

Copilot for Microsoft 365 Seats With No Activity

Copilot for M365 was purchased in optimistic blocks through 2024 and 2025, often before deployment plans were mature. Months on, the usage reports show a meaningful share of assigned seats with little or no activity. Because Copilot is an add-on priced per assigned user, every dormant seat is unrecovered spend. The discipline is to set an activation threshold, identify seats below it, and either reallocate them to active users or release them at the next renewal point rather than auto-renewing the full block. This is also the cleanest internal proof point that disciplined assignment, not optimistic bulk purchasing, is the right operating model.

Where to look: the Copilot usage report in the admin centre. Seats with no prompts over a defined window are dormant by definition and should not silently renew.
SKU 3

Software Assurance on Cores That No Longer Exist

Windows Server and SQL Server Software Assurance renews against core counts captured when the estate was larger. Virtualisation consolidation, cloud migration, and hardware refresh shrink the real core footprint, but the SA keeps billing on the old number unless someone reconciles it. The report covers matching current deployed cores to your SA count, retiring coverage on decommissioned cores at renewal, and using Azure Hybrid Benefit so the surviving licenses cover Azure workloads rather than being duplicated. This is where shelfware and over-licensing overlap with the broader cost picture our cost optimization engagement addresses.

Where to look: your current CMDB or hypervisor core inventory against the SA quantities on your licensing statement. The delta is stranded SA.
SKU 4

Dynamics 365 Full Licenses Where Team Member Rights Fit

Dynamics 365 uses a base-and-attach model with a wide price gap between full application licenses (Sales, Customer Service, Field Service) and the Team Member SKU intended for light, read-mostly use. Enterprises routinely assign full licenses to occasional users — executives who only view dashboards, staff who update a handful of records — whose actual rights fit Team Member. The reclaim maps each user's real interaction pattern against the use rights of each SKU and reassigns the over-licensed users down, capturing the difference without removing anyone's necessary access.

Where to look: D365 user roles and activity against the published Team Member use rights. Full-license users whose actions fall inside Team Member scope are the candidates.
SKU 5

Per-User Add-Ons That Outlived Their Project

Power BI Pro, Power Apps per-user plans, Entra ID P2, Project, and Visio plans get bought for a specific initiative and rarely get reclaimed when it ends. They linger on leavers, disabled accounts, and users who changed roles. Individually small, collectively they are a persistent drain — and they re-accumulate every cycle without governance. The report provides the orphaned-assignment sweep to find them and the lightweight joiner-mover-leaver process that stops them coming back.

Where to look: add-on assignments filtered against active, licensed, recently-signed-in accounts. Assignments to inactive or departed users are immediate reclaims.
The Method and the Reclaim

Measuring the gap, then converting it into a lower true-up and renewal.

Naming the five SKUs is only half the work. The value comes from a defensible measurement of your own estate and a sequence that turns the finding into a contractual reduction — which, under the EA, can only happen at the right moments and only if you arrive prepared.

01

Build the Deployed-vs-Purchased Position

The foundation is a reconciliation that sets what you have purchased against what is genuinely deployed and used — not merely assigned. That means pulling feature-level activity for M365 and Copilot, core inventory for Server SA, role-and-activity data for D365, and assignment-versus-sign-in data for add-ons. The output is a single view of every SKU where purchased exceeds used, with the gap quantified in seats, cores, and dollars. This is the artifact that changes the renewal conversation, because it replaces the account team's assumptions with your evidence. Our independent licensing specialists assemble this position routinely; an internal team can build it too, given access to the right reports.

Key finding: Across the estates we review before a true-up, an average of 22% of assigned premium licenses show usage below the threshold that would justify the SKU — the single largest source of recoverable spend.
02

Time the Reclaim to the EA Calendar

Because the true-up only adds and never subtracts, reductions are recognised at renewal — and the strategy work that decides what to cut belongs to the period before that. Mapping your reclaim to the renewal timeline (the T-12 to signature window covered in our EA renewal preparation guidance) means the deployed-versus-purchased position is finished, validated, and ready to put on the table when the committed quantities for the next term are set. Bring it late and the baseline locks in; bring it early and the reduction is yours to negotiate.

Key finding: Shelfware identified after the renewal commitment is signed cannot be returned mid-term. The window to convert the finding into a lower committed quantity is the renewal itself — miss it and the overspend is fixed for the full term.
03

Hold the Reduction Against the Upsell Pressure

A reclaim only sticks if it survives the renewal conversation, where the account team will frame reductions as risk and pair them with new commitments. The report covers how to present the deployed-versus-purchased evidence so the reduction is treated as a correction of over-purchase rather than a negotiable concession, how to separate the genuine future need from the speculative upsell, and how to govern assignment afterward so shelfware does not simply re-accumulate before the next cycle. The goal is a baseline that reflects reality and a process that keeps it there.

Key finding: A 14,000-seat retailer reclaimed roughly $3.4M at renewal by stepping 1,300 over-assigned E5 users to E3, clearing a dormant Copilot block, and retiring SA on decommissioned cores — the committed quantity fell for the first time in the life of the agreement.
Worked Example

How a national retailer cut its committed quantity for the first time ever.

A national retail group with 14,000 Microsoft 365 seats believed its estate was lean because it negotiated price hard every cycle. Price discipline, though, is not the same as quantity discipline. A deployed-versus-purchased review found three of the five SKUs in this report sitting unused: roughly 1,300 E5 seats assigned to users whose feature activation fit E3, a block of Copilot for M365 licenses with no activity for four months, and Software Assurance still billing on Windows Server cores retired two years earlier in a virtualisation consolidation. None of it appeared in the standard admin-centre license counts because all of it was assigned. The reclaim was timed to the EA renewal: the E5 seats were stepped down with targeted add-ons where justified, the dormant Copilot block was released rather than auto-renewed, and the stranded SA was retired with surviving licenses redirected through Azure Hybrid Benefit. The committed quantity dropped for the first time in the agreement's life, recovering roughly $3.4M against the prior baseline. The moves were not clever; they were measured, and they were brought to the table in time. Reclaiming overspend like this is the core of what our buyer-side advisory practice does, and if a true-up or renewal is on your horizon, that is precisely what a free estate review is for.

Reviewed by the Microsoft Negotiations advisory team. Microsoft Negotiations is an independent, buyer-side advisory firm. Not affiliated with Microsoft Corporation.

Renewal or true-up ahead? Find the shelfware before the next term locks it in.

Our advisors run the deployed-versus-purchased reconciliation across all five SKUs — E5 over-assignment, dormant Copilot, stranded Server SA, D365 license mismatch, and orphaned add-ons — and build the reclaim position you take into the renewal while the committed quantity is still negotiable.

22%Avg unused premium licenses found
500+Engagements completed
100%Buyer-side — no Microsoft tie
Continue Reading

More from the Microsoft Negotiations research library.

Advisory Service

Microsoft 365 Optimization

The service that reclaims over-assigned E5, dormant Copilot, and orphaned add-ons — measuring feature-level activation your standard reports cannot see.

Learn More →
Authority

Microsoft Licensing Experts

Reclaiming shelfware is buyer-side work. Meet the independent specialists who reconcile deployed against purchased and build the position you take to renewal.

Meet the Team →
Report

Why Your Unified Support Quote Jumped 40%

Shelfware inflates the spend that Unified Support is priced against. This companion report covers the six counters that bring the support fee back down.

Download Free →

Apply This to Your Live Microsoft Situation

The frameworks in this guide work. They work better with 20 years of deal data behind them. If you have an upcoming EA renewal, true-up, or Microsoft audit — a 20-minute call with a senior advisor will tell you exactly where your exposure is and what you can negotiate.

500+Engagements
$2.1BManaged Spend
32%Avg Cost Reduction
100%Independent