Enterprises routinely overspend by 15–25% on Microsoft renewals because they enter negotiations without accurate usage data. This guide provides a structured, repeatable template for conducting internal licence reviews — comparing entitlements against actual deployment — so CIOs can negotiate renewals from a position of data-driven confidence.
Most enterprises enter Microsoft EA renewal negotiations relying on Microsoft’s renewal proposal as their starting point. This is fundamentally the wrong approach. Microsoft’s proposal is based on your current contracted quantities — not your actual usage. It assumes you need everything you have today, plus whatever growth Microsoft’s sales team can justify. Without your own independent usage data, you have no basis to challenge these assumptions.
An internal licensing usage review — essentially a self-audit — builds your Effective Licence Position (ELP): a verified comparison of what you are entitled to use versus what is actually deployed and actively used. This ELP becomes the foundation for every renewal decision, from identifying shelfware you can eliminate to spotting compliance gaps you should address before Microsoft discovers them.
Identify licences you are paying for but nobody uses. Organisations typically discover 10–20% of their Microsoft licences are unused — assigned to departed employees, cancelled projects, or test accounts that were never deprovisioned.
Discover any under-licensed situations before Microsoft’s auditors do. Proactively resolving a compliance gap at your normal contract pricing avoids the list-price penalties and surcharges imposed during a formal audit.
Identify users with premium licences (E5) who only use basic features (email and Office). Downgrading these users to E3 at renewal can save USD 15–22 per user per month without any loss of functionality they actually use.
Enter renewal discussions with evidence, not assumptions. When you can demonstrate that only 600 of your 1,000 Visio licences are in use, Microsoft cannot credibly push you to renew all 1,000. Data transforms negotiation dynamics.
“The real waste in modern enterprise licensing is almost always over-licensing, not under-licensing. Organisations routinely discover 15–25% of their Microsoft spend is going to licences that deliver zero business value. An internal review before renewal is the single most effective way to convert that waste into savings.”
An effective usage review follows a structured, repeatable process. These eight steps provide a comprehensive framework that can be adapted to any organisation’s size and complexity. The entire process should be completed 3–6 months before your EA expiry date to ensure findings can inform renewal negotiations.
Determine which Microsoft products and services to review. Ideally, encompass all major licence categories: Microsoft 365 (E3, E5, F1/F3), Windows Server and SQL Server, Dynamics 365, Azure consumption, and standalone products (Visio, Project, Power BI). If a comprehensive review is not feasible within your timeline, prioritise by spend — audit the highest-cost areas first. Set a clear objective: build an accurate ELP showing entitled vs deployed vs actively used for every product.
An internal audit is not an IT-only exercise. Assign a SAM/ITAM lead to coordinate the process, IT Operations to provide deployment and usage data, Procurement to gather entitlement records and contract documents, Finance to quantify the cost impact of findings, and Business Unit representatives to validate whether specific licences are genuinely needed. Clear ownership is critical — designate one person accountable for driving the project to completion and chasing down all data inputs.
Collect deployment and utilisation data across all Microsoft products. For cloud services, use Microsoft 365 admin centre reports for active user counts by subscription type and identify accounts with no login activity in 60+ days. For on-premises software, run discovery tools (SCCM/MECM, third-party SAM platforms) to inventory Windows Server, SQL Server, and desktop application installations — including version and edition. For Azure, pull consumption data from Azure Cost Management. For feature utilisation, assess whether E5 users are actually using E5-specific features (advanced security, voice, analytics) or only core Office functionality.
In parallel, collect all records of what your organisation is entitled to use: Enterprise Agreement documents listing contracted quantities, Microsoft Licence Statements (MLS) from the Volume Licensing Service Centre, CSP or MPSA purchase records, OEM licence documentation, and previous true-up reports showing mid-term additions. Organise entitlement data by product to match your usage inventory format. Note that the MLS may not include CSP purchases or OEM licences — supplement accordingly.
Compare usage against entitlements for every product to build your Effective Licence Position. Identify surplus licences (entitled but unused — candidates for elimination at renewal), compliance shortfalls (deployed beyond entitlement — resolve before an external audit), oversized licences (premium tier assigned where standard would suffice), and duplicate or redundant assignments (users with overlapping licence types due to misconfiguration). Present findings in a structured worksheet showing Entitled vs In Use vs Unused vs Action Plan for each product SKU.
Before acting on reconciliation results, validate every finding with the relevant stakeholder. Confirm with HR that inactive Microsoft 365 accounts correspond to departed employees. Check with department leads whether unused Project or Visio licences reflect genuine redundancy or seasonal usage not captured in your point-in-time analysis. Verify with infrastructure teams that server inventory data is accurate — automated scanners can miss or double-count instances. Validation prevents cutting licences that are genuinely needed and secures business unit buy-in.
Address findings that can be resolved before renewal: reclaim licences from inactive users and reassign them from the pool before purchasing new ones. Shut down unused Azure resources (immediate cost reduction on pay-as-you-go). Flag compliance gaps and quietly purchase additional licences or adjust deployments to become compliant before any external audit. Build your true-down plan — documenting every licence you intend to reduce at renewal. There are no penalties for reducing quantities when an EA term ends.
Compile all findings into a clear, structured report that serves both as an internal governance record and a negotiation tool. The template should list every product with columns for Entitled, In Use, Unused, and Action Plan. This document guides your renewal conversation, provides evidence to resist Microsoft’s upselling, and demonstrates mature IT governance to auditors or internal stakeholders.
The centrepiece of your internal audit is a structured worksheet that maps every Microsoft product to its entitlement, deployment, and usage status. This template becomes your single source of truth for renewal negotiations and ongoing licence governance.
| Product / SKU | Entitled | In Use | Unused | Action Plan |
|---|---|---|---|---|
| Microsoft 365 E5 | 1,000 | 950 | 50 | Renew 950. Review E5 feature usage — downgrade non-power users to E3. |
| Microsoft 365 E3 | 2,500 | 2,400 | 100 | Renew 2,400. Reclaim inactive accounts. Evaluate F3 for frontline workers. |
| Visio Plan 2 | 200 | 120 | 80 | Renew 120 only. Reassign or eliminate 80 unused licences. USD 28,800/yr saving. |
| Power BI Pro | 800 | 500 | 300 | Renew 500. Investigate if Power BI Premium per capacity could replace individual licences at lower cost for remaining users. |
| Windows Server Std | 50 cores | 50 cores | — | Usage matches entitlement. Renew all. Verify AHB coverage for Azure VMs. |
| SQL Server Enterprise | 100 cores | 110 cores | −10 shortfall | Purchase 10 additional cores before renewal to resolve compliance gap. |
| Azure Consumption | USD 500K/yr | USD 450K/yr | USD 50K headroom | Reduce commitment to USD 460K. Apply AHB and RIs for further savings. |
| Total Annual Savings Identified | USD 180,000–250,000 in licence reductions + USD 50,000 in Azure commitment optimisation | |||
This template format provides clarity at a glance: green cells indicate savings opportunities, red cells flag compliance risks, and the action plan column ensures every finding has a clear next step. Populate this template for every Microsoft product in your estate, regardless of whether it appears in your EA — CSP purchases, MPSA subscriptions, and OEM licences should all be included for a complete picture.
The quality of your licence review depends entirely on the quality of data you collect. Here is a comprehensive guide to the data sources available for each category of Microsoft product.
Usage data: Microsoft 365 admin centre > Reports > Usage. Pull active user counts per subscription (E5, E3, E1, F1/F3). Review the “Last Activity Date” for each user — accounts inactive for 60+ days are candidates for reclaim. Feature adoption reports show which E5-specific capabilities (Defender, Phone System, Power BI) are actually used. Entitlements: EA portal or VLSC licence summary; CSP partner portal for subscriptions purchased outside the EA.
Usage data: SCCM/MECM inventory, MAP Toolkit, or third-party SAM tools (Snow, Flexera, ServiceNow SAM). Capture server names, operating systems, editions, core counts, and virtualisation host configurations. For SQL Server, document instances, editions, and physical host core counts (licensing is based on physical cores). Entitlements: Microsoft Licence Statement, EA order confirmation, MPSA records, OEM certificates of authenticity.
Usage data: Azure Cost Management > Cost Analysis for consumption trends. Azure Advisor for underutilised VM recommendations. Azure Hybrid Benefit usage reports showing which VMs have AHB enabled. Reserved Instance utilisation reports. Entitlements: EA Azure monetary commitment details; Azure Reserved Instance purchase records; on-premises licence inventory (for AHB eligibility verification).
The reconciliation phase is where the value of your internal review materialises. By comparing usage data against entitlement records product by product, you identify four categories of findings — each with a distinct action plan.
Licences you are paying for that nobody uses. Common examples: Microsoft 365 seats assigned to departed employees, Visio/Project licences from completed projects, Power BI Pro seats for users who never adopted the tool. Action: Reclaim immediately; reduce quantities at renewal. Every surplus licence is a direct cost that can be eliminated.
Deployments exceeding your entitlement — more SQL Server instances than licences, more Windows Server VMs than your core count covers. Action: Resolve before renewal by purchasing additional licences at contract pricing (far cheaper than the list-price penalties imposed during a formal audit). Address quietly and proactively.
Users with premium licences who only use basic functionality. The classic example: E5 users who use only email and Office apps and never touch advanced security, voice, or analytics features. Action: Downgrade to E3 at renewal. The per-user saving of USD 15–22/month multiplied across hundreds of users generates substantial annual savings.
Situation: A global manufacturing company performed an internal licence audit six months before their EA renewal. They had approximately 5,000 Microsoft 365 users and a broad portfolio of server, Visio, Project, and Power BI licences.
Findings: The review identified ~300 Microsoft 365 E3 licences assigned to departed employees or unused test accounts. Additionally, 100 users with E5 licences were only using email and core Office applications — no E5-specific features (advanced security, voice, analytics). The team also found 80 unused Visio Plan 2 licences from a completed engineering project.
Situation: An IT services firm had been rapidly provisioning Windows Server VMs in Azure. Their internal self-assessment discovered that several Azure deployments were not covered by their existing on-premises licences — Azure Hybrid Benefit had not been correctly configured, and some VMs were running without any licence entitlement.
Situation: A large retail enterprise inventoried all Microsoft licences and usage before their EA renewal. Microsoft’s initial renewal proposal assumed they needed 1,000 Visio licences and 800 Power BI Pro subscriptions — matching the previous EA quantities.
Even well-intentioned internal reviews can produce incomplete or inaccurate results if common pitfalls are not avoided. Here are the mistakes we see most frequently.
| Pitfall | Impact | How to Avoid It |
|---|---|---|
| No clear ownership | Review stalls; data collection is incomplete | Assign a single accountable SAM/ITAM lead with authority to chase all inputs |
| Ignoring virtualisation detail | Server ELP is inaccurate; compliance gaps missed | Document physical host cores, VM counts, and Licence Mobility coverage |
| Using only the MLS | CSP, OEM, and MPSA licences not counted | Supplement MLS with all procurement channel records |
| Point-in-time vs usage trends | Seasonal or project-based usage missed | Analyse 3–6 months of usage data, not a single snapshot |
| Not validating with business units | Needed licences flagged as surplus | Confirm every proposed reduction with the relevant department |
| Leaving findings undocumented | Insights lost; no negotiation leverage | Record everything in the structured licence review template |
| Starting too late | Insufficient time to act before renewal | Begin the review 6 months before EA expiry; allow 4–8 weeks for completion |
Your completed Effective Licence Position is not just a compliance document — it is the most powerful tool you can bring to a Microsoft renewal negotiation. Here is how to leverage it effectively.
Microsoft’s renewal proposal will default to your current contracted quantities. Your ELP provides the evidence to counter with actual usage numbers. For every product where usage is below entitlement, propose renewing at the lower number. The burden of proof shifts to Microsoft to justify why you need more than you use.
Use feature adoption data to propose tier downgrades (E5 to E3, Enterprise to Standard) where premium capabilities are unused. Microsoft will resist downgrades because of the revenue impact, but documented feature utilisation data makes the case irrefutable.
If your ELP identified shortfalls, address them before negotiation begins. Walking into a renewal with known compliance gaps weakens your position — Microsoft may use the gap as leverage to push a larger deal. Arriving compliant and informed is the strongest possible posture.
Presenting a structured ELP signals to Microsoft that you are a sophisticated, well-managed customer. This discourages aggressive upselling tactics and often results in more favourable treatment — Microsoft prefers to retain well-informed customers with fair terms rather than risk losing them entirely.
“Microsoft’s sales team cannot easily push licences you demonstrably do not need. Data transforms the renewal from a conversation about what Microsoft wants to sell into a conversation about what you actually need to buy. That shift in dynamic is worth more than any negotiation tactic.”
The greatest value from an internal licence review comes not from a one-time exercise, but from establishing a repeatable governance practice that maintains licence accuracy continuously. Organisations that implement ongoing licence management reduce renewal overspend by 15–25% year over year.
Begin the internal review at least six months before EA expiry. This provides sufficient time for data collection, validation, quick-win execution, and integration of findings into your negotiation strategy.
Involve IT, procurement, finance, and business units. Each brings essential data and context. A review conducted in IT isolation misses procurement records and business unit requirements.
Manual data collection is error-prone and time-consuming. SAM tools automate discovery, reconciliation, and reporting — transforming the review from a project into a continuous capability.
Review 3–6 months of usage data rather than a single point-in-time. This captures seasonal patterns, project-based usage, and ensures you do not accidentally eliminate licences needed intermittently.
Record every finding, data source, and decision. Documentation guides renewal negotiation, demonstrates governance maturity to auditors, and enables knowledge transfer as team members change.
Do not wait for renewal to reclaim unused licences, shut down idle Azure resources, or resolve compliance gaps. Quick wins generate immediate savings and improve your negotiating position for the renewal conversation.
For complex estates or high-value renewals, independent licensing advisors provide benchmark data, identify gaps internal teams miss, and add credibility to your negotiation position. Advisory fees are typically a fraction of the savings they enable.
Transform the one-time review into an ongoing governance practice. Annual or semi-annual reviews, automated SAM tooling, and integrated HR deprovisioning workflows sustain savings year after year.
While internal licence reviews are achievable with in-house resources, independent advisory significantly enhances both the quality of findings and the impact on renewal outcomes. The information asymmetry between Microsoft’s licensing specialists (who manage thousands of agreements) and your internal team (who manage one) creates an inherent disadvantage that independent expertise can address.
Microsoft licensing rules are complex and frequently changing. Independent advisors maintain current expertise on product use rights, virtualisation rules, hybrid deployment entitlements, and contractual nuances that internal teams may not track. This expertise prevents ELP errors that could undermine your negotiation position or create hidden compliance risk.
Independent advisors bring pricing and discount benchmarks from hundreds of Microsoft agreements across industries. This data tells you whether Microsoft’s proposed pricing is competitive, where there is room to negotiate, and what terms other organisations of your size and profile have secured. Without benchmarks, you negotiate blind.
Redress Compliance has no commercial relationship with Microsoft — no partner status, no referral commissions, no licence resale. This ensures our review findings and negotiation recommendations are exclusively aligned with your interests, without any vendor influence on our advice.
Redress Compliance delivers independent Microsoft licensing reviews and EA renewal advisory — helping CIOs build verified Effective Licence Positions, eliminate shelfware, resolve compliance gaps, and negotiate renewals with data-driven confidence. Complete vendor independence and proven strategies.