Microsoft SAM and License Optimization: How to Find and Recover Licence Waste

Why Microsoft SAM Matters More in 2026 Than Ever Before

Microsoft Software Asset Management has historically been positioned as a risk mitigation exercise — finding and closing licence gaps before a Microsoft audit creates an embarrassing true-up demand. That framing undervalues SAM's role in modern enterprise Microsoft cost management. In 2026, SAM data is the foundation of every commercially significant decision in the Microsoft relationship: renewal negotiations, SKU right-sizing, True-Up liability forecasting, and E7 upsell evaluation.

The combination of the November 2025 EA discount tier collapse and the M365 price increases landing July 2026 has created an environment where the stakes of an uninformed renewal are higher than at any point in the last decade. An enterprise with 5,000 M365 seats that renews based on Microsoft's proposal rather than internally generated utilisation data is leaving a predictable and significant sum on the table. The industry average SaaS utilisation rate is approximately 57%, meaning that on average, 43% of licensed capabilities in a typical enterprise deployment are unused. For Microsoft's M365 stack, with per-seat pricing ranging from $10.50 for E1 to $99 for E7, the waste accumulates quickly.

SAM as Negotiation Infrastructure

The most commercially valuable SAM deliverable for a Microsoft customer is not a compliance report — it is a utilisation-by-user-by-SKU dataset that documents exactly which features each user actively accesses and compares that against their contracted licence tier. This dataset is the evidence base for every right-sizing request in an EA negotiation. Microsoft's account team cannot argue against utilisation data that demonstrates 1,200 users on M365 E5 have not accessed a single E5 Security or E5 Compliance feature in the prior 90 days.

The SAM Methodology for Microsoft Environments

Effective Microsoft SAM follows a four-phase methodology: inventory, utilisation analysis, optimisation modelling, and renewal preparation. Each phase builds on the previous one, and the quality of the data at each stage determines the accuracy and commercial value of the output.

Phase 1: Licence Inventory

The first phase establishes a complete, accurate picture of every Microsoft licence your organisation currently holds. For M365, this means extracting the licence assignment data from the Microsoft 365 Admin Centre — which users hold which licences, which add-ons are assigned, and which licences are assigned but unactivated. For Azure, it means inventorying Reserved Instance commitments, Savings Plans, and active resource deployments against those commitments. For Dynamics 365, it means mapping licenced users against the application modules they are assigned.

The inventory phase also covers on-premises licensing — Windows Server, SQL Server, System Centre — which is particularly relevant for organisations with hybrid environments where the boundary between on-premises and cloud licensing determines whether Azure Hybrid Benefit is being maximally applied.

Phase 2: Utilisation Analysis

The second phase overlays actual usage data against the licence inventory to identify the gap between what is licensed and what is actually used. For M365, this data comes from the Microsoft 365 Usage Reports in the Admin Centre, which provide per-user activity data for Exchange, SharePoint, Teams, OneDrive, and individual applications. For E5 specifically, the usage report shows whether E5 Security features (Defender for Endpoint, Defender for Identity, Entra ID P2) and E5 Compliance features (Advanced eDiscovery, Insider Risk Management) have been activated and used by specific users.

The utilisation analysis produces a right-sizing matrix: for each user, what is their current licence tier, which features do they actively use, and what is the lowest licence tier that covers their actual feature utilisation? The financial value of this matrix — the annual savings from right-sizing each user to their minimum required tier — is the primary commercial output of the SAM process.

Phase 3: Optimisation Modelling

The third phase models the cost and risk implications of different optimisation scenarios. For SKU right-sizing, this means calculating the annual saving from moving users from E5 to E3, from E3 to E1, or from E7 back to E5 plus selective Copilot licences. The modelling must account for three factors that complicate simple right-sizing calculations: users who appear to have low feature utilisation but whose role requires access to E5 features in a disaster recovery or compliance scenario; the transition cost of reassigning licences and communicating with business units; and the contractual constraints of the current EA that may restrict mid-term licence reductions.

The optimisation model typically identifies three categories of opportunities: immediate right-sizing that can be executed without contractual risk, renewal right-sizing that is best executed at EA renewal where contracted counts can be formally reduced, and future optimisation that requires process changes or technology transitions before the licence reduction can be realised.

Phase 4: Renewal Preparation

The fourth phase converts the SAM output into negotiation-ready material. This means preparing a formal right-sizing request — documented with utilisation data per user per SKU — that presents the organisation's proposed contracted counts for the next EA term. It also means identifying the True-Up liability trend (are you above or below contracted count at the current rate?) and modelling whether the True-Up position warrants adjusting the contracted baseline at renewal.

The Top Five Microsoft Licence Optimisation Opportunities

1. E5 Right-Sizing to E3

Switching M365 E5 users who do not actively use E5 Security or E5 Compliance features to M365 E3 saves between $22 and $24 per user per month at post-July 2026 pricing ($60 E5 versus $38 E3). For a 5,000-user organisation where 2,000 users are on E5 but only 500 genuinely require E5 features, the annual saving is $22 multiplied by 1,500 users multiplied by 12 months — approximately $396,000 per year. This is the single largest licence optimisation opportunity in the typical enterprise Microsoft environment.

2. Azure Reserved Instance Optimisation

Azure Reserved Instances provide discounts of up to 72% against pay-as-you-go rates for committed Azure resource consumption. Many enterprise organisations have Reserved Instance commitments that are misaligned with their current Azure deployment — either reserving VM types that are no longer deployed, reserving resources in regions that have changed, or maintaining reserved capacity for workloads that have been decommissioned. Azure Reservations management, conducted quarterly, typically recovers 15 to 25% of committed Reserved Instance spend through rationalisation and scope adjustment.

3. Copilot Licence Right-Sizing

Microsoft 365 Copilot at $30 per user per month — or included in E7 — is the highest per-user cost in the M365 add-on portfolio. In early Copilot deployments (typically 6 to 18 months post-launch), actual active utilisation rates average 40 to 60%. Licences assigned to users who have not become active Copilot users within 90 days of assignment should be reassigned to users with higher potential for active adoption, rather than carried as shelfware. For organisations evaluating E7 as an E5 upgrade path, the Copilot utilisation rate among the proposed E7 population is a critical input into the TCO calculation.

4. Dynamics 365 Attach Licence Optimisation

Dynamics 365 uses an attach licence model where qualifying users can access certain Dynamics 365 applications at a reduced rate if they already hold an M365 E3 or E5 licence. Many enterprise deployments carry users on full Dynamics 365 licences who qualify for the attach licence rate, generating avoidable overspend. A SAM review of Dynamics 365 licence assignments against M365 entitlements identifies every user eligible for attach licence pricing — a saving of $20 to $40 per user per month for qualifying Dynamics 365 applications.

5. Azure Hybrid Benefit Maximisation

Azure Hybrid Benefit allows organisations to apply existing Windows Server and SQL Server Software Assurance licences to Azure VMs and SQL Server deployments in Azure, reducing Azure compute costs by up to 40%. Many enterprises with significant on-premises Windows Server and SQL Server estates are not maximising Azure Hybrid Benefit because the licence tracking required to assert Hybrid Benefit claims is managed separately from Azure deployment provisioning. A SAM review that maps on-premises Software Assurance coverage to Azure deployments typically identifies a 15 to 35% reduction in Azure IaaS costs for SQL Server and Windows Server workloads.

SAM and the Microsoft True-Up: Managing Liability

The EA True-Up anniversary requires the organisation to declare and pay for any licences added above the contracted count during the prior 12 months. Without an ongoing SAM programme that tracks licence assignments against contracted counts throughout the year, many organisations encounter True-Up demands that are larger than anticipated — because organic licence growth through starters, IT provisioning, and project deployments accumulated without visibility or controls.

Effective SAM for True-Up management means running a monthly licence count reconciliation that compares active licence assignments against the contracted baseline, flags any exceeding of the contracted count, and initiates a review of whether the excess reflects genuine business need or provisioning errors. This monthly cadence eliminates the True-Up surprise and provides the organisation with accurate forecasting data for budgeting the True-Up payment or negotiating an amended contracted baseline before the anniversary date.

Building a Continuous Microsoft SAM Programme

One-time SAM assessments, while valuable, do not provide the ongoing visibility needed to manage Microsoft licence costs across a three-year EA term. A continuous SAM programme consists of three operational components: a monthly licence reconciliation, a quarterly utilisation review, and an annual renewal preparation cycle.

The monthly reconciliation takes 30 to 60 minutes using Microsoft 365 Admin Centre data and a simple tracking spreadsheet. It prevents the True-Up surprise and keeps the licence baseline accurate. The quarterly utilisation review identifies significant changes in usage patterns — new product deployments, workforce reductions, application migrations — that warrant licence reassignments before they accumulate into a True-Up liability or waste. The annual renewal preparation cycle, conducted six to twelve months before the EA renewal date, generates the comprehensive right-sizing analysis needed to enter the renewal with a documented, defensible licensing position.

Organisations that operate a continuous SAM programme consistently achieve better commercial outcomes at EA renewal than organisations that commission point-in-time assessments. The data quality is higher, the preparation timeline is longer, and the negotiation position is more defensible because it is backed by twelve months of tracked utilisation data rather than a 30-day snapshot. Engaging Microsoft EA advisory specialists to establish and run this programme provides access to the benchmarking data and commercial intelligence needed to convert SAM insights into maximum renewal savings.