IT Asset Manager's Guide to Microsoft EA in 2026: The Complete Framework for Compliance, Optimisation, and Cost Control

A Microsoft Enterprise Agreement is a multi-million-dollar, multi-year commitment, but its financial value is realised or lost in the day-to-day operational practices of licence management. The IT Asset Manager (ITAM) is the person who determines whether the organisation captures full value from its EA investment or slowly bleeds money through over-licensing, shelfware, compliance gaps, and missed entitlements.

Our advisory experience consistently shows that organisations with mature Software Asset Management (SAM) practices spend 10-25% less on Microsoft licensing than those without. The savings come from multiple sources: accurate licence inventories that prevent over-purchasing, continuous compliance that eliminates audit risk, proactive true-up management that minimises annual cost increases, full utilisation of Software Assurance benefits that would otherwise expire unused, and data-driven insights that power better renewal negotiations.

This guide provides the complete ITAM operational framework for Microsoft EA management: every inventory process, compliance check, optimisation technique, and governance practice needed to maintain licence accuracy, prevent audit exposure, and maximise the financial return on your EA investment throughout its 3-year lifecycle.

Executive Summary: Why the IT Asset Manager Is Critical

The ITAM discipline directly determines EA value realisation. Without accurate licence inventory, you cannot make informed decisions about anything else. Without continuous compliance, you face audit risk and hidden liabilities. Without proactive true-up management, annual cost increases become uncontrolled. Without Software Assurance tracking, entitlements expire unused. Without usage data at renewal, you accept whatever Microsoft quotes.

Maintaining an Accurate Licence Inventory: The Foundation of Everything

Every other ITAM practice depends on having an accurate, continuously updated licence inventory. If you do not know exactly what you own, what is assigned, and what is available, you cannot make informed decisions about anything else.

1. The Three-Layer Inventory Model

Entitlements (what you own): Every licence purchased under the EA, by SKU, quantity, and effective dates. Source from the signed EA schedule, VLSC portal, and Microsoft 365 Admin Center.

Assignments (what is deployed): Every licence assigned to a user, device, or server. Source from M365 Admin Center, Azure AD (Entra ID), SCCM/Intune, and server inventories.

Availability (what is unassigned): The gap between entitlements and assignments, your licence pool. This pool should be actively managed, not just a residual number.

2. Reconciliation Cadence

Reconciliation between entitlements and assignments should happen at minimum quarterly, and monthly in the quarter leading up to the EA anniversary (true-up). Each reconciliation should identify:

• Over-assignments (licences assigned beyond entitled count, compliance risk)
• Under-assignments (entitled licences not assigned, potential waste)
• Inactive users (licences assigned to users with no activity in 90 days, reclaim candidates)
• Departed employees (licences assigned to terminated users, immediate reclaim)
• Device-based licensing gaps (devices with software installations but no corresponding licence)

3. The Licence Pool Strategy

Maintain a deliberate licence pool (typically 3-5% of total entitlements) for new hires, project needs, and temporary requirements. This pool prevents emergency purchases at premium rates and ensures new employees can be productive from day one. However, the pool should be monitored. If it consistently exceeds 5%, you are likely over-licensed and can reduce at renewal. Learn more about independent Microsoft advisory services.

Ensuring Continuous Compliance: Preventing Problems Before They Become Audit Findings

Compliance is not a point-in-time exercise, it is a continuous practice. Organisations that treat compliance as an annual check (at true-up) or a reactive response (to an audit notice) consistently face larger exposure and higher costs than those that maintain compliance as an ongoing operational discipline.

The Five Core Compliance Safeguards

1. Integrate licence assignment with HR processes: Every new hire receives the correct licence type from the pool as part of onboarding. Every departure triggers automatic licence reclaim. Automate where possible using identity governance tools or scripted processes between HR systems and M365/Entra ID.

2. Never deploy without a licence: Establish a policy that no software installation, cloud service activation, or server deployment occurs without a confirmed licence entitlement. This applies to all environments: production, development, test, and disaster recovery.

3. Quarterly internal compliance reviews: Compare deployed software against entitlements every quarter. Focus on highest-risk areas: server products in virtualised environments, Azure Hybrid Benefit usage, and device-based installations.

4. Monitor cloud service assignments continuously: M365 licence assignments change daily as users join, leave, change roles, or request new services. Use M365 Admin Center reports or SAM tools to flag any SKU where assignments exceed entitlements.

5. Control shadow IT and self-service: Establish governance around self-service capabilities (Power Platform, Azure subscriptions, Teams app installations) to prevent unapproved licence consumption.

High-Risk Compliance Areas for ITAM Focus

True-Up Management: Turning an Annual Cost Event Into an Optimisation Opportunity

The EA annual true-up is the process where you report actual licence usage to Microsoft and purchase any licences consumed above your committed counts. Without proactive management, the true-up becomes an unpleasant financial surprise. With proactive management, it becomes a controlled, predictable, and often minimised cost.

The True-Up Timeline

The true-up occurs at each EA anniversary. The ITAM team should begin preparation 90 days before the anniversary date, not in the final week. Follow this timeline:

• 90 days before: Pull comprehensive licence usage data for all SKUs; identify any SKUs trending above committed counts.
• 60 days before: Execute clean-up actions: reclaim licences from departed employees, inactive users, and completed projects; downgrade users who do not need premium SKUs (E5 to E3, etc.).
• 30 days before: Finalise the true-up report; verify that all clean-up actions have been completed; calculate the exact true-up quantity and cost per SKU.
• Anniversary date: Submit the true-up report to Microsoft; purchase additional licences as required.

Clean-Up Tactics That Reduce True-Up Cost

Learn more about Microsoft Enterprise Agreement negotiation strategy.

• Reclaim departed employee licences: Users terminated but licence still assigned. Typical recovery: 2-5% of total licence count. Cross-reference HR termination list with M365 assignment list.
• Reclaim inactive user licences: Users with no login in 90+ days. Typical recovery: 3-8% of assigned licences. Pull M365 usage report and contact managers to confirm status.
• Downgrade over-provisioned users: E5 users who only use E3 features. Potential downgrade: 5-15% of E5 users. Analyse E5 feature usage (Phone System, analytics, compliance); downgrade non-users.
• Consolidate duplicate assignments: Users with multiple overlapping licences. Typical recovery: 1-3% of licence count. Audit for users with both E3 and standalone Exchange/SharePoint licences.
• Remove test/service accounts: Non-human accounts consuming licences. Typical recovery: 1-2% of licence count. Identify service principals and test accounts with assigned licences; remove or use service-specific licensing.

Negotiated True-Up Protections

The best time to address true-up risk is during the EA negotiation (before signing), but ITAM should advocate for these terms regardless:

• Request pre-agreed true-up pricing: Ensure that any licences purchased at true-up are at the same discounted rate as the original EA, not at list price.
• Negotiate a growth cap: Request a clause limiting the true-up obligation to a maximum percentage increase (for example, 10% above committed counts) in any single year.
• Explore true-down rights: Standard EAs only allow true-up (increases). Negotiate the ability to reduce licence counts at the anniversary if usage has decreased. This is rare but achievable in some negotiations.

Software Assurance Benefits Maximisation

Software Assurance (SA) entitlements include valuable benefits that organisations frequently fail to claim. Common benefits include home use programme eligibility, developer tool access, training credits, and technical support incident hours.

An ITAM tracking programme should maintain a Software Assurance benefits register that documents: all SKUs with SA coverage, quantity of licences with active SA, benefit eligibility per SKU, claimed benefits to date, and unclaimed benefits expiring in the next 12 months.

Many organisations capture 50-70% of their SA benefit value. Mature ITAM organisations claim 90%+ of benefits through proactive benefit tracking, integration with development teams, and quarterly benefits reconciliation.

Preparing for Microsoft Audit Readiness

Microsoft audits can create significant financial exposure if compliance gaps are discovered. However, proactive audit defence preparation reduces exposure dramatically. An audit-ready organisation has:

• Complete documentation of all licences owned, by SKU and quantity, from the signed EA schedule and VLSC portal
• Current hardware inventory showing all physical and virtual systems using Microsoft products
• Software deployment records showing every installation of Microsoft software, matched to a licence entitlement
• Clear documentation of any licensing assumptions, exceptions, or grey areas, explained with supporting evidence
• A remediation plan for any compliance gaps identified during internal audit preparation

Working With Your Renewal Cycle

The 3-year EA renewal is where accurate ITAM data drives maximum negotiation value. At renewal, Microsoft presents renewal quote based on historical usage and current committed SKUs. However, organisations with 3 years of accurate usage data can challenge Microsoft's assumptions, propose different SKU mix, and negotiate better pricing based on demonstrated usage patterns.

Before renewal, ITAM should prepare: 3 years of monthly usage data by SKU, documentation of cost avoidance achieved through SAM practices, analysis of SKU trends (which SKUs are growing, which are declining), audit readiness documentation, and negotiation brief for procurement team.