How to Track Microsoft License Usage Across Your Enterprise

You cannot negotiate what you cannot measure. Enterprises that track Microsoft licence usage with precision — not estimates, not IT team assumptions, but data-sourced usage intelligence — consistently outperform those that don't by an average of £280,000 in annual licence spend per 10,000 users. The gap is not driven by better deals. It is driven by better data.

Tracking Microsoft licence usage across an enterprise is not straightforward. Microsoft's product estate spans cloud services, desktop software, server infrastructure, and a rapidly expanding AI layer — each with different usage signals, different licence models, and different reporting tools. This guide gives you the framework to build genuine, cross-estate licence usage visibility that feeds both your compliance programme and your negotiation strategy.

Why Usage Tracking Is Not Optional

The EA model makes usage tracking financially consequential in ways that are not always obvious. Your annual true-up obligation is calculated against peak deployment — not average deployment. That means an unused user account that peaked in month three and has been inactive since still contributes to your true-up calculation unless it was deprovisioned before the measurement window.

The second financial consequence is less discussed: enterprises without usage data enter EA renewal negotiations without the ability to demonstrate what they actually need versus what they currently pay for. Microsoft's renewal proposal will be anchored to your current contract quantities. Without usage data, you have no evidence-based counterposition. With usage data, you can present a documented case for licence count reduction and SKU right-sizing backed by twelve months of actual consumption evidence.

The Four Primary Usage Data Sources

Microsoft provides several native tools for usage tracking. Understanding what each measures — and what it misses — is essential before building any tracking programme.

1. Microsoft 365 Admin Centre Usage Reports

The M365 Admin Centre provides usage reports covering active users across all M365 services: Exchange, SharePoint, Teams, OneDrive, Yammer, and individual Microsoft 365 apps. The standard active user definition is a user who has performed at least one qualifying activity in a given period.

Key limitations to understand:

• Reports default to a 30-day window. For licence compliance purposes, you need to export 90-day and 180-day views to understand sustained inactivity patterns.
• Guest users are included in some reports and excluded from others. Export raw data and filter explicitly rather than relying on the dashboard counts.
• The reports do not distinguish between users with different licence tiers — an E3 user and an E5 user both appear in the same active user count. Cross-referencing with Entra ID licence assignments is required for SKU-level analysis.
• Privacy settings in your tenant may suppress individual user data, forcing you to work with aggregate-only reports. This must be resolved before usage tracking can deliver licence-level accuracy.

2. Microsoft Entra ID (Azure Active Directory) Licence Assignment Reports

Entra ID is the authoritative source for who has been assigned which licence. The Entra ID licence management module shows every assigned licence, the group or direct assignment through which it was granted, and the last sign-in date for each user. Last sign-in date is the most reliable single indicator of whether a user is genuinely active.

The 90-day sign-in threshold is the industry standard for active licence validation: a user whose last sign-in to the Entra tenant is more than 90 days ago is operationally inactive, regardless of what their M365 activity reports show. Licences held by such users should be reviewed for recovery.

Entra ID also captures group-based licence assignments, which are the operationally efficient delivery model but create a tracking challenge: if a user is added to a group that carries an E5 licence as a convenience measure (because they need access to one E5 feature), they receive the full E5 entitlement bundle. Group-based assignment audits frequently reveal this over-entitlement pattern — licences assigned for convenience rather than genuine need.

3. Microsoft Endpoint Manager / Intune

For device-based licences — Windows licences, Microsoft 365 Apps for Enterprise deployed to managed devices, and server products deployed through SCCM — Intune and Configuration Manager are the authoritative sources. Key data points include:

• Device inventory with last check-in dates (inactive devices may still consume Windows or Office licences)
• Installed software versions (critical for server product licence compliance — specific versions may require specific licence editions)
• Device compliance state (useful for identifying devices that may need remediation before a true-up)

One frequently missed use case: identifying dormant shared devices (kiosk machines, shared workstations) that are consuming user-based M365 licences when they should be on shared device licences or frontline worker SKUs. In retail, healthcare, and manufacturing environments, this pattern is common and expensive — we have found £600,000+ in recoverable spend from shared-device reclassification in a single engagement.

4. Azure Cost Management and Billing

Azure licence usage — consumption against your MACC commitment, reserved instance utilisation, and Pay-As-You-Go spend outside commitment — is tracked through Azure Cost Management. Key metrics to track:

• Reserved instance utilisation rate (below 85% is waste — you are paying for capacity you are not using)
• Azure Hybrid Benefit (AHUB) activation rate on eligible VMs — unactivated AHUB on eligible workloads is a direct overpayment
• Commitment burn rate against MACC — tracking whether you are on track to consume your committed spend has implications for negotiating future MACC terms
• Resource group tagging completeness — untagged resources cannot be attributed to business units, which prevents internal chargeback and creates cost governance blind spots

The Enterprise Tracking Model

Building a sustainable tracking programme requires a structured data model that consolidates inputs from multiple sources into a single, decision-ready view. The model has four layers:

Layer 1: Entitlement Data

What you are licensed for, at the product and SKU level, including quantities, term dates, and amendment history. Source: VLSC / Microsoft Admin Centre licence inventory + EA order form. Updated: after every EA amendment and at the start of each true-up cycle.

Layer 2: Assignment Data

Who (or what device) has been assigned each licence, through which assignment mechanism (direct or group), and when the assignment was made. Source: Entra ID licence management reports, exported via Microsoft Graph API for automation. Updated: real-time through automated export or minimum monthly pull.

Layer 3: Active Usage Data

Which assigned licences are being actively used — defined as users with qualifying activity in the past 90 days for cloud services, or device check-in within 90 days for device-based licences. Source: M365 Admin Centre usage reports (export required for full data), Entra ID last sign-in data, Intune device activity. Updated: monthly minimum, quarterly for formal reconciliation.

Layer 4: Variance Analysis

The comparison of entitlement against assignment against active usage — the three-way reconciliation that identifies both compliance exposure (deployment exceeding entitlement) and waste (entitlement or assignment with no active usage). This layer is where the commercial intelligence is generated.

Product-Specific Tracking Priorities

Microsoft 365 (Cloud Services)

M365 tracking should operate at three levels simultaneously: SKU-level (how many E3s vs E5s assigned), service-level (which services within each SKU are being used), and feature-level (are premium features that justify premium SKUs actually being accessed).

The feature-level analysis is where the most valuable data is. An organisation with 8,000 E5 licences where only 1,200 users access Defender XDR and Purview has a documented case that at least 6,800 users could be served by E3 with targeted security add-ons at lower total cost — saving potentially £3.5M annually at 2026 pricing.

Track using the M365 Admin Centre product-level reports combined with Microsoft 365 Apps activity reports, which show adoption rates for individual Office applications.

Copilot for Microsoft 365

Copilot licensing deserves separate tracking because adoption rates remain low across most enterprise deployments. Microsoft's own data acknowledges that monthly active users on paid Copilot licences are substantially below the number of licences purchased. Tracking Copilot usage separately — using the Microsoft Copilot usage report in the M365 Admin Centre — is essential to understanding your true per-seat ROI and building the data you need to negotiate pricing at renewal.

Key Copilot metrics to track monthly: active user rate (users with at least one Copilot interaction in 30 days), interaction volume by product (Teams, Word, Excel, Outlook), and the cohort of users with zero Copilot usage. Any user with zero usage in 60+ days is a licence recovery candidate.

Azure

Azure tracking requires three parallel views: reservation utilisation (are you using what you have committed to), AHUB activation (have you activated Hybrid Benefit on all eligible resources), and untagged resource identification (spend that cannot be attributed and therefore cannot be managed). The Azure Cost Management + Billing portal provides all three, but only if tagging policies have been enforced through Azure Policy — retroactive tagging of unmanaged resources is a significant remediation exercise in estates without governance controls.

SQL Server and Windows Server

On-premises server licences require discovery-based tracking — software inventory from SCCM or Intune that captures the specific edition of SQL Server or Windows Server running on each host, combined with the physical and virtual core count. The licence requirement is calculated from the core count using Microsoft's specific rounding rules (minimum 4 cores per processor, minimum 2 processors per server). Errors in core counting are the most common cause of under-licensing in server infrastructure — and the source of significant audit exposure.

Automating the Tracking Process

Manual tracking — spreadsheet-based data pulls from multiple admin consoles — is not sustainable at enterprise scale. The minimum automation requirement for a reliable tracking programme is:

Power BI connected to these automated data feeds provides the visualisation layer — enabling the cross-source variance analysis that produces the three-way licence position view (entitled vs assigned vs active). This is achievable without third-party SAM tooling in estates under 15,000 users; at larger scale, purpose-built platforms (Snow, Flexera, ServiceNow SAM) handle the data integration and add licence rule libraries that account for Microsoft's complex licensing models.

The Governance Cadence

Data is only useful if it drives decisions. The tracking programme needs a governance cadence that converts data into action:

• Monthly: Licence assignment review — identify and act on accounts inactive for 60+ days. Threshold alerts for any product line where deployment exceeds 90% of entitlement (early warning for true-up exposure).
• Quarterly: Full licence reconciliation — three-way comparison, gap analysis, remediation planning. Output feeds into the true-up preparation timeline.
• Pre-renewal (6–9 months out): Annual usage trend analysis — which product lines have grown, which have contracted, where adoption is below the rate that justifies the SKU tier. This is the data package for your renewal negotiation team.

Turning Usage Data into Negotiation Leverage

The commercial value of a mature tracking programme goes beyond compliance. Twelve months of clean, documented usage data generates three categories of negotiation leverage:

• Licence count reduction evidence: If your data shows that active M365 users have decreased from 12,000 to 10,400 over the EA term, you have documented evidence for a 1,600-seat reduction in your renewal base. Without this data, Microsoft's renewal proposal will be anchored to your peak contract quantity.
• SKU right-sizing evidence: Feature-level usage data that shows, for instance, that only 30% of your E5 user population accesses the advanced security features that differentiate E5 from E3 creates a credible basis for partial downgrade — saving £14–£22 per user per month on the reclassified seats.
• Adoption-gated Copilot commitment: Usage data showing actual Copilot monthly active user rates provides the evidence needed to negotiate an adoption-gated commitment structure — where your licence volume commitment increases only as adoption demonstrates value, rather than committing to 5,000 seats and hoping for the best. This is explored in detail in our guide to negotiating Copilot pricing.

The Microsoft Negotiation Tactics white paper covers how Microsoft account teams respond to data-backed positions — and how to use your usage evidence to counter the standard anchor price without triggering escalation.

The Tracking Errors That Undermine Your Position

Three tracking errors are common enough — and consequential enough — to warrant specific attention:

Tracking Assignments, Not Usage

The difference between assigned licences and active licences is typically 15–25% in enterprise estates without rigorous offboarding processes. Tracking assignment data and calling it usage data produces a materially incorrect picture of your deployment — one that overstates both your compliance obligations and your licence costs. Active usage data requires activity signals, not just assignment records.

Using Snapshot Data for Trend Decisions

A single point-in-time snapshot of licence usage is insufficient for renewal negotiation purposes. You need trend data — monthly active user counts over 12 months — to distinguish between genuine declining usage (which supports a count reduction at renewal) and seasonal fluctuation (which does not). A retail organisation that sees 35% lower M365 activity in January than in November is experiencing seasonal variation, not a licence surplus.

Not Aligning Tracking Methodology to Microsoft's Assessment Methodology

If your usage tracking uses a different active user definition from Microsoft's licence compliance assessment — different time windows, different activity thresholds, different guest-user treatment — your data will not be directly comparable to Microsoft's findings. When your numbers differ from theirs at true-up, you need to be able to explain the delta with matching methodology. Build your tracking on the same foundations Microsoft uses: Entra ID activity, 90-day windows, internal-user-only counts.

For further context on how Microsoft approaches licence compliance assessment, our guide to what to expect from a Microsoft licence compliance audit covers their methodology in detail.