Building a Microsoft Software Asset Management Programme

Most enterprise Microsoft SAM programmes were built in response to an audit — or the threat of one. They are defensive constructions, designed to demonstrate compliance in an adversarial context, not to actively manage cost or support commercial decisions. That defensive orientation produces a programme that is expensive to operate, produces limited commercial value, and is often abandoned between audit cycles.

A Microsoft SAM programme built for the right purpose looks different. It is not primarily an audit-readiness tool — it is a continuous intelligence system that tells the organisation exactly what it owns, what it deploys, what it uses, and what it is paying for. That intelligence reduces compliance risk as a by-product, but its primary value is commercial: it feeds the true-up process, supports the renewal negotiation, identifies waste continuously, and provides the data foundation for every Microsoft cost reduction initiative.

This guide sets out how to build a Microsoft SAM programme that delivers that commercial value — not a compliance exercise performed once and filed away, but an operational programme that earns its investment every quarter.

Why Microsoft SAM Is Different from General SAM

Generic software asset management tools and methodologies were designed for a world of perpetual licences on managed devices. Microsoft in 2026 is primarily a subscription, SaaS, and cloud consumption business. The SAM approach that works for managing Office 2019 perpetual licences on domain-joined Windows machines does not work for managing M365 subscriptions, Azure consumption commitments, Power Platform usage entitlements, and Copilot seat allocations across a hybrid workforce.

Microsoft-specific SAM requires competency in several areas that generic SAM programmes do not address:

• Subscription licence management: Assigned vs active vs licensed seat tracking, with harvesting workflows for inactive assignments
• Entitlement mapping: Understanding which products are included in which M365 bundle, and which standalone licences are therefore redundant
• Azure consumption management: FinOps discipline applied to Azure spend — separate from software licence management but increasingly part of the total Microsoft cost picture
• True-up management: Tracking the licence position continuously so the annual true-up reflects accurate deployment data and is negotiated rather than simply accepted
• EA compliance: Understanding the Microsoft-specific licence rules (virtualisation, core factor tables, product use rights) that determine whether a deployment is compliant

Most SAM tools cover the first and partially the third of these competencies. The others require Microsoft-specific expertise and processes that are built around the Microsoft licensing model rather than grafted onto a generic framework.

The Five Components of an Effective Microsoft SAM Programme

Component 1: Licence Entitlement Repository

The entitlement repository is the authoritative record of what your organisation is licensed to use. It combines data from multiple sources into a single, maintained licence position statement.

Sources that must be integrated:

• Volume Licensing Service Centre (VLSC) — EA, Select, OLP perpetual entitlements and SA coverage
• Microsoft 365 Admin Centre — subscription licences, assignment status, and product inclusion mapping
• Azure portal — subscription details, MACC commitment and consumption, and PaaS licence entitlements
• Finance and procurement records — historical licence purchases outside volume agreements, including retail and OEM licences
• Third-party contract records — any Microsoft licences acquired through resellers or LSPs that may not appear in VLSC

The entitlement repository is not a tool — it is a process. Many organisations have SAM tools that connect to some of these sources but lack the discipline to maintain them accurately. A tool with stale data produces misleading reports. The process of keeping the repository current is the discipline that determines whether the programme delivers value.

Component 2: Deployment Discovery

Deployment discovery identifies what Microsoft software and services are actually deployed and in use, across all device and user populations. This requires different technical approaches for different deployment models:

Component 3: Gap and Waste Analysis

The gap and waste analysis compares entitlements against deployments to identify two types of positions: gaps (deployments that exceed entitlements, creating compliance exposure) and waste (entitlements that exceed deployments, representing unnecessary cost).

For Microsoft specifically, the waste analysis has several distinct dimensions:

• Inactive M365 assignments: Users with licences assigned but with no recorded activity in 30+ days. Standard benchmarks suggest 8–15% of assigned seats in a typical enterprise are inactive at any given time. Systematic licence harvesting recovers these consistently.
• SKU overlap: Licences assigned from multiple products that provide the same entitlement (e.g., Intune standalone + M365 E3). Every overlap is direct waste.
• Over-specified SKUs: Users assigned E5 licences where E3 would meet their actual usage requirements. The usage data from discovery provides the evidence base for right-sizing decisions.
• SA on undeployed products: Software Assurance payments on products that are no longer deployed. See our legacy licence management guide for the retirement framework.
• Azure waste: Unattached disks, over-provisioned VM sizes, resources running outside business hours, and failure to apply Azure Hybrid Benefit. Azure FinOps is a distinct discipline but feeds into the total Microsoft spend management picture.

Component 4: True-Up Management Process

The annual true-up is the moment when the EA licence position is reconciled and any incremental committed count is priced and paid. Most organisations approach the true-up reactively: they receive a request from Microsoft or their LSP, compile a point-in-time deployment count, and submit it. This approach produces accurate reporting but no commercial value.

A SAM programme with an effective true-up management process does the following differently:

1. Maintain a running licence position: The gap and waste analysis should be refreshed monthly, so the licence position at true-up is known in advance rather than discovered at the time of reporting. No surprises means no pressure to accept Microsoft's count without scrutiny.
2. Prepare a negotiated true-up position: If the true-up reveals a significant incremental deployment count, prepare the commercial response before the conversation. Incremental licence volume is leverage — use it. Our true-up negotiation leverage guide covers the specific mechanics.
3. Challenge Microsoft's true-up data: Microsoft may produce a different count than yours, typically via telemetry data. Do not accept discrepancies without understanding and challenging them. Microsoft's telemetry counts do not always reflect correct licensing rules — for example, virtualisation scenarios, shared device licensing, and developer edition use all have specific product use rights that may affect the correct count.
4. Document the true-up position formally: The agreed true-up position should be documented in writing with Microsoft before any payment is made. Verbal agreements on true-up counts are not sufficient.

Component 5: EA Renewal Intelligence Feed

The SAM programme's highest-value output for most organisations is the intelligence it provides to the EA renewal team. An organisation that arrives at renewal knowing exactly what it has deployed, what it uses, and what it is paying for versus market is in a fundamentally different negotiating position than one that arrives with estimates and assumptions.

Twelve months before EA renewal, the SAM programme should produce:

• Committed vs deployed vs actively used licence counts by product, with trend data over the past 12 months
• SKU appropriateness analysis — where is the organisation over-specified, and what would right-sizing cost versus current commitment?
• Total cost of ownership by product family, including infrastructure, administration, and integration costs beyond the licence fee
• Three-year forecast of licence requirements based on business plans and deployment trends
• Azure consumption trajectory versus MACC commitment, with optimisation potential identified

This package is the foundation for a structured EA renewal preparation programme. Without it, the renewal negotiation is conducted on Microsoft's data rather than your own — a significant disadvantage.

Tooling: What You Actually Need

The SAM tooling market for Microsoft is mature but uneven in quality. Tools range from basic M365 licence inventory tools to comprehensive SAM platforms with Azure FinOps integration. The right tool depends on your environment's complexity and your team's capacity to use it properly.

The minimum viable tooling set for a Microsoft SAM programme:

• Microsoft 365 Admin Centre usage reports (free, included in M365) — for subscription licence assignment and service usage data
• Microsoft Cost Management (free, included in Azure) — for Azure spend, resource inventory, and AHUB application tracking
• SCCM or Intune device inventory (already licensed if in EA) — for on-premises and managed device software discovery
• A structured spreadsheet or lightweight SAM tool — for maintaining the entitlement repository and gap analysis

Organisations with complex hybrid environments or significant server estates may require a dedicated SAM tool such as Snow, Flexera, or Certero to manage discovery across unmanaged and legacy systems. The tool selection should follow the programme design, not precede it.

Microsoft's SAM Engagement Programme: What It Is and What It Is Not

Microsoft offers a SAM Engagement Programme through its partner network — a structured review of your licence position conducted by a Microsoft-authorised SAM partner. Understanding what this programme delivers — and what it does not — is important before participating.

Microsoft SAM engagements provide: a structured methodology for licence position discovery; access to Microsoft's licensing tools and VLSC data; and a formal output report that can be used as evidence of compliance management. In the right circumstances, they provide genuine value.

What they do not provide: independent commercial advice; recommendations to reduce your Microsoft spend; or negotiating support for your EA renewal. SAM partners are Microsoft-authorised, which means they have a structural relationship with Microsoft and are compensated within the Microsoft ecosystem. A SAM engagement that identifies significant under-licensing creates a compliance gap that Microsoft can reference. See our Microsoft SAM engagement guide for the full analysis of when to participate and when to use an independent alternative.

Resourcing a Microsoft SAM Programme

A well-designed Microsoft SAM programme does not require a large dedicated team. The programme's size should be proportionate to the complexity and value of the Microsoft estate being managed. For most mid-market enterprises (£2M–£20M annual Microsoft spend), a part-time SAM owner supported by periodic independent expert review is an appropriate investment.

The SAM owner role requires:

• Understanding of Microsoft's licensing rules across the products in scope (M365, Azure, server software at minimum)
• Ability to maintain and interpret the entitlement repository and discovery data
• Process ownership for true-up management and waste reporting
• Coordination with procurement, finance, and IT to ensure licence changes are tracked

Independent expert review — either through an advisory engagement or periodic programme health checks — provides the market benchmarking, licensing rule verification, and EA renewal support that internal teams typically cannot provide cost-effectively at scale. An organisation with a strong internal SAM programme that also engages independent advisors at renewal consistently achieves better outcomes than one relying on either approach alone.