Auditing Your Microsoft License Usage: A Step-by-Step Guide to Find Savings

Why a Microsoft Licence Audit Matters More Than Ever in 2026

Three things converged in late 2025 and early 2026 to make licence auditing urgent in a way it simply was not two years ago. First, Microsoft eliminated automatic volume discount tiers — Levels B, C, and D — for all Enterprise Agreement and MPSA customers from November 1, 2025. Every organisation, regardless of size, now pays Level A list price for cloud services unless individual discounts are negotiated. A 15,000-seat enterprise that previously held Level D automatically, receiving a 12% discount, now has to argue for that concession from scratch at renewal. The built-in leverage is gone.

Second, Microsoft is raising M365 prices materially on July 1, 2026: E3 moves from $36 to $39 per user per month (an 8.3% increase), and E5 moves from $57 to $60 (5.3%). These are list-price increases that affect every renewal landing after that date. Third, Microsoft has introduced E7 as the new top-tier SKU at $99 per user per month, positioned above E5. Microsoft field teams are actively running an E5-to-E7 upsell motion at every renewal. Without granular usage data, your account team will make a compelling-sounding case that E7's bundled Copilot, Agent 365 governance, and Entra Suite justify upgrading the entire estate. Without data, you cannot push back credibly.

The practical reality is this: a well-executed audit, completed 90 days before your EA anniversary, delivers three distinct advantages. It identifies licence reclamation that directly offsets the price increases. It quantifies which users genuinely consume E5 or E7 capabilities — enabling a segmented SKU strategy rather than accepting a blanket upsell. And it produces internal evidence that moves Microsoft's discounting authority. The audit is not optional preparation; it is the price of admission to a meaningful negotiation.

Step 1 — Establish Your Licence Baseline

The first step is deceptively simple: compile a complete, current picture of every licence you are paying for. In a large enterprise this is rarely straightforward. Licences accumulate through M&A activity, department-level purchasing, CSP subscriptions running alongside an EA, and shadow IT procurement bypasses. The goal at this stage is not analysis — it is inventory.

Pull your licence counts from three sources and reconcile them. Start with your Microsoft Admin Centre: navigate to Billing then Your Products and export the full subscription list, including quantities purchased and quantities assigned. This is your contractual position. Then pull usage data from the Microsoft 365 Admin Centre under Reports then Usage, which shows active users per workload — Exchange, Teams, SharePoint, OneDrive — for the last 30 days. Finally, cross-reference your EA or CSP invoice to confirm what you are actually being billed for. There are routinely discrepancies between what contracts state and what invoices charge.

The output of Step 1 should be a single spreadsheet with every SKU, the number of seats purchased, the number assigned, and the number with confirmed recent activity. Any gap between purchased and assigned is immediate reclamation potential. Any gap between assigned and actively used flags seats that may be candidates for downgrade or cancellation.

Step 2 — Identify Inactive and Departed User Accounts

Inactive accounts are the most reliable source of wasted licence spend in any M365 estate. When employees leave, accounts are frequently disabled in Active Directory but the M365 licence is not removed. The licence continues to consume quota, and for E5 licences at $57 to $60 per user per month these zombied accounts represent substantial ongoing waste.

Use Microsoft Graph PowerShell to export last sign-in data for all licensed accounts. The core command is Get-MgUser with the signInActivity property. Filter for accounts with no sign-in in the past 90 days, then cross-reference against your HR system's active employee records. Any account that appears inactive in M365 and is absent from current headcount is a licence that should be reclaimed immediately. Industry benchmarks suggest 10 to 15% of all licensed accounts at a large enterprise fall into this category at any given time.

A secondary check targets shared mailboxes and service accounts assigned user licences unnecessarily. Shared mailboxes do not require a licence for most M365 scenarios. A common misconfiguration is assigning an E3 or E5 licence to a shared mailbox simply because the admin provisioning it was unaware that licences are not required. Every such account is recoverable cost requiring only a configuration correction, not a commercial negotiation.

If your audit reveals material overspend or compliance gaps ahead of a True-Up, our Microsoft EA advisory specialists provide structured remediation support and renewal negotiation — working exclusively on the buyer's side with no Microsoft financial relationship.

Step 3 — Map Workload Utilisation Against SKU Entitlement

With active accounts confirmed, the next question is whether those active users are consuming the features that justify their current SKU tier. The M365 stack runs from F1 through F3, E3, E5, and now E7. The cost difference between tiers is significant. E3 at $39 per user per month versus E5 at $60 represents a $21 monthly delta per seat. For a 1,000-seat deployment that is $252,000 per year. For 5,000 seats it is $1.26 million annually.

The key E5-over-E3 differentiators are advanced security (Defender for Endpoint Plan 2, Defender for Identity, Defender for Office 365 Plan 2), advanced compliance (eDiscovery, Communication Compliance, Advanced Audit via Microsoft Purview), and advanced analytics (Power BI Pro). If your E5 users are not actively using at least two of these capability families, E5 is over-provisioned for them. The M365 Admin Centre usage reports do not break down by advanced security feature consumption, so a rigorous assessment requires pulling data separately from the Microsoft Defender portal and the Purview compliance portal.

In our experience across 500+ enterprise engagements, approximately 30 to 40% of E5 seats at a typical enterprise are consuming only E3-equivalent capabilities. Right-sizing those seats to E3 — even at the higher July 2026 E3 price of $39 — saves $21 per seat per month versus E5 at $60. A 500-seat right-sizing saves $126,000 per year before any negotiated discounts are applied. Multiply that across a large estate and the audit pays for itself many times over before a single negotiation conversation takes place.

Step 4 — Audit E7 Readiness Candidly

Microsoft field teams are running a coordinated E5-to-E7 upsell motion. At $99 per user per month, E7 bundles E5 capabilities with Microsoft 365 Copilot (worth $30 standalone), Agent 365 ($15 standalone), and Entra Suite ($12 standalone) — a combined value of $117 if bought piecemeal, making the $99 E7 price appear attractive. Your account team will present exactly this arithmetic at renewal.

Before accepting the E7 pitch for your full estate, audit three things. First, Copilot adoption. Only 3.3% of M365 subscribers had purchased Copilot as of early 2026 — roughly 15 million out of 450 million total seats. If your organisation has not actively adopted Copilot or has run a pilot with limited uptake, including it in a licence bundle for every user creates significant shelfware. Second, Agent 365 is a governance control plane, not an agent execution engine. It does not run agents or provide compute. Organisations wanting to build and run agents still need Copilot Studio or Microsoft Foundry on top of E7 — those are separate consumption-based costs that the E7 pitch routinely obscures. Third, Entra Suite relevance. Entra Suite covers Identity Governance, External ID, Internet Access, and Private Access. If you already have third-party identity governance or your requirements are satisfied by Entra P2 (included in E5), the Entra Suite component of E7 adds no net value.

The realistic E7 calculus for most enterprises is that E7 makes economic sense for perhaps 20 to 30% of users — those actively using Copilot, with genuine agent governance needs, and without existing Entra Suite coverage. Auditing your estate to identify that precise cohort enables a segmented counter-proposal: E7 for the power users, E3 or E5 for the rest, with Copilot available as an add-on for users who demonstrate adoption. This segmented model consistently saves 15 to 25% versus a blanket estate upgrade — and it is much harder for Microsoft to argue against when you arrive with granular usage data.

Step 5 — Analyse True-Up History for Over-Commitment Signals

If you are on an Enterprise Agreement, your EA anniversary triggers a True-Up — a mandatory report of all licence additions during the past year, followed by a payment for any licences consumed above your committed baseline. Many organisations over-commit at the start of their EA term to simplify administration, then fail to conduct mid-year reviews that would reveal whether consumption has actually reached that committed number.

Pull your last three True-Up submissions and compare them to your actual consumption. If True-Up payments have consistently been nominal — meaning you committed to more seats than you used — you have a structural over-commitment problem. At your next renewal, reduce your committed baseline to match actual consumption, using your True-Up history as documented evidence. Microsoft will resist this, arguing that a lower baseline reduces your ability to grow. Counter with the data: if you have not grown into your committed seats in three consecutive annual periods, the commitment was not anchored in your actual usage trajectory and any renewal baseline must reflect reality.

True-Up history also helps in a subtler way. It establishes your growth rate as a documented fact in writing. If Microsoft argues for a higher price based on anticipated growth, your True-Up data provides a factual counter-narrative that a field team cannot simply dismiss.

Step 6 — Review Add-On and Stand-Alone Licences for Consolidation

Beyond the core M365 SKU tiers, most enterprise estates carry a collection of add-on and stand-alone licences that accumulate over time: Power BI Pro, Teams Phone, Microsoft 365 Copilot add-ons, Intune Plan 2, Defender for Business, Dynamics 365 qualifying user licences, and others. These add-ons are frequently purchased by different teams at different times, often with capabilities overlapping what is already included in the base SKU.

The audit should map every add-on licence against the features included in the base SKU for each user group. Common findings include Power BI Pro licences assigned to users already on E5 (where Power BI Pro is included), Intune add-on plans assigned to users whose E5 licence already includes Intune Plan 1, and Teams Phone stand-alone licences being paid for users who have Teams in their base plan but calling has not been enabled. Each of these requires nothing more than accurate mapping to reclaim.

Teams Phone deserves specific attention. As a separate add-on from core M365, Teams Phone is priced at approximately $8 per user per month. It is frequently assigned to users who do not make or receive external PSTN calls but were included in an all-or-nothing departmental deployment. Auditing actual call activity through Teams admin centre reports and right-sizing the Teams Phone deployment often recovers meaningful spend, particularly in large deployments where the original rollout was driven by convenience rather than validated usage data.

Step 7 — Assess Azure Consumption Alignment

Many EA customers carry Azure commitments alongside their M365 licences under a single EA or a separate Azure Enterprise Agreement commitment. The audit should include a review of Azure Reserved Instance and Savings Plan coverage against actual compute consumption. Under-utilised reserved instances — common in organisations that have right-sized their VM fleet without adjusting their reservations — represent wasted committed spend that can be exchanged, modified, or applied to other workloads.

Azure Hybrid Benefit is frequently under-utilised in large estates. If your organisation holds on-premises Windows Server or SQL Server licences with Software Assurance, Azure Hybrid Benefit allows those licences to be applied to Azure VMs, cutting Azure compute costs by 30 to 50% for eligible workloads. Auditing AHB coverage as part of a broader Microsoft licence review routinely surfaces tens of thousands of dollars in unclaimed benefit, particularly in organisations that moved workloads to Azure rapidly without conducting a licence entitlement review.

Step 8 — Build Your Negotiation Data Package

The output of steps 1 through 7 is not merely a cost-reduction spreadsheet — it is negotiation ammunition. The most effective Microsoft EA negotiations are built on documented, irrefutable data: here is what we committed to, here is what we consumed, here is where we were over-provisioned, and here is our forward demand model based on validated business plans rather than Microsoft's growth assumptions.

Structure your data package around three elements. First, a licence reclamation summary — the seats you are returning or downgrading and the cost basis for doing so. Second, a segmented SKU proposal — your recommended allocation of E3, E5, and E7 seats, with utilisation evidence for each tier. Third, a committed growth schedule — the incremental licences you are prepared to commit to over the next 12 to 24 months, with a corresponding discount expectation attached. The third element is what actually moves Microsoft's discounting authority. They want growth commitment; you want price relief. Structuring the negotiation as a growth-commitment exchange for negotiated discount consistently produces better outcomes than presenting audit findings and simply asking for a reduction.

What Microsoft does not want buyers to know: with automatic discount tiers eliminated from November 2025, the only path to pricing below Level A list is to ask for it explicitly, with supporting data and a credible growth narrative. Organisations that renew without audit data pay 6 to 12% more than peers who arrived at the table with evidence. The audit is not optional preparation — it is table stakes for a competitive renewal outcome.

Tools and Methods That Actually Work

Microsoft provides several native tools that form the foundation of any audit. The Microsoft 365 Admin Centre reports under Reports then Usage give 30, 90, and 180-day activity breakdowns by workload and are sufficient for identifying inactive users and under-consumed licences at scale. The Microsoft Entra admin centre provides sign-in activity data essential for inactive account identification. The Microsoft Defender portal and the Purview compliance portal provide the workload-level data needed to assess whether E5 security and compliance features are genuinely being consumed.

For organisations that need more granular analysis or want to automate recurring licence reviews, PowerShell via the Microsoft Graph API remains the most flexible approach. The Get-MgUser and Get-MgSubscribedSku cmdlets, combined with service plan mappings, can produce a comprehensive licence-to-usage correlation report with a few hundred lines of script. Commercial tools such as SysKit, AdminDroid, and 365Tune provide pre-built dashboards surfacing the same insights with less technical overhead. The practical advice for large enterprises: use Microsoft's native tooling for the baseline and for data that will appear in your negotiation package — Microsoft cannot dispute data sourced from its own admin portals.

Timing: The Q4 Window Changes Everything

Microsoft's fiscal year ends June 30, making April through June — Q4 — the highest-leverage negotiating window of the year. Microsoft field representatives have maximum discount authority during Q4 because they are closing against annual quota targets. Deals signed during Q4 average 15 to 20% better terms than deals signed in Q1. If your EA anniversary falls in Q4, you should be completing your audit now. If it does not, the long-term strategic move is to align your renewal date to Q4 through an early renewal or term restructuring — organisations that have made this shift consistently report materially better deal terms over time.

The audit completion deadline is 90 days before your renewal date, not 30. Starting too late is the most common error we see in organisations that come to us after a suboptimal renewal. With 30 days to go, you have insufficient time to remediate licence counts, prepare your counter-proposal, and allow the negotiation process to run its natural course. With 90 days, you can complete the audit, formulate your segmented SKU strategy, conduct an internal alignment process, and open the negotiation from a position of strength rather than time pressure.

What a Completed Audit Typically Finds

Based on our work across 500+ enterprise Microsoft engagements, a thorough licence audit at a typical 1,000 to 10,000 seat enterprise consistently finds 10 to 15% of licences assigned to inactive or departed users, recoverable at full cost. It finds 15 to 25% of licences at E5 tier where actual consumption is E3-equivalent, recoverable as a downgrade at the $21 per seat per month delta. It finds 5 to 10% of add-on licences that duplicate capabilities already included in the base SKU. And it finds a 20 to 35% gap between what the enterprise committed to and what a well-structured renewal position should reflect.

These are not theoretical figures. A 14,362-user enterprise that went through our full audit process found 28% underutilisation, translating to $2,068,128 in recoverable annual spend before any negotiation commenced. At a 3,000-seat mid-market company, a focused audit ahead of a three-year commitment identified $420,000 in avoidable spend that completely offset the July 2026 price increases. The audit does not just reduce costs — it changes the negotiation dynamic from defending a renewal quote to leading with data on your own terms.

Using Audit Findings Offensively, Not Defensively

The final section of any Microsoft licence audit should be a forward-looking demand forecast, not just a backward-looking waste analysis. Microsoft is most willing to negotiate when buyers articulate a clear growth trajectory with credible business rationale. If your audit shows that 1,200 users are on E3 but your Copilot pilot is producing measurable productivity gains in the test group, a structured proposal to move 300 of those users to E7 — in exchange for a negotiated discount on the remaining 900 E3 seats — gives Microsoft what it wants while giving you a lever that was not available without the usage data.

This is how sophisticated buyers use audit data offensively rather than defensively. The audit is not a justification for staying flat — it is evidence of where you will grow, on your terms, in exchange for pricing relief. Microsoft's negotiators respond to this framing because it maps to their fiscal incentives: SKU upgrades toward E5 and E7 are quota events that field teams receive commercial credit for. Giving them a credible upgrade pathway, anchored in real adoption data, is the most effective way to unlock discount authority in a post-tier-elimination environment where nothing is automatic and everything must be earned.