Microsoft licensing, read in full.

Why Microsoft is a portfolio decision.

Microsoft is, commercially, four estates layered on a single Enterprise Agreement. The productivity estate (Microsoft 365, Teams, Copilot) is the seat-priced surface. The infrastructure estate (Windows Server, SQL Server, System Center) is the core-priced surface. The applications estate (Dynamics 365, Power Platform) is the user-tier-priced surface. And Azure is the consumption-priced surface, contracted through the MACC. The Enterprise Agreement is the wrapper that prices, true-ups and renews the four estates as one transaction.

The implication for procurement is that a Microsoft decision in one estate moves the others. A Copilot rollout pulls M365 E5 into the portfolio. A Windows Server estate decision touches the SQL Server licensing and the Azure Hybrid Benefit. An Azure MACC commitment touches the EA discount structure. An Admodum Microsoft engagement therefore designs the four estates as a single commercial picture, never as four parallel transactions.

This pillar groups the firm’s Microsoft commentary into ten editorial sections. Each section names the load-bearing mechanic, links the deeper spoke articles, and points to the practice page, the relevant white papers and the knowledge hub for the buyer who wants the engagement methodology.

The Enterprise Agreement and the true-up cycle.

The Enterprise Agreement is a three-year commercial wrapper that prices a defined product mix at a defined per-unit cost, and runs an annual true-up against the buyer’s deployed counts. The first-year quantities are baselined at signature; the second and third years true up the additions; the fourth year either renews the EA or transitions to MCA-E.

The procurement implication is direct. The true-up is a one-way ratchet inside the EA term. Quantities can be added at the true-up; quantities cannot be removed until the renewal window opens. A misjudged baseline in year one becomes a three-year over-commitment, with a renewal anchor that reads against the inflated count rather than the actual need.

The Admodum methodology starts with an inventory-quality baseline before signature, structures the true-up calendar so the additions flow against the deployed estate (not the forecast), and runs the renewal as a re-baselining exercise rather than a uplift conversation. The full reading sits in the Microsoft EA Renewal paper.

M365 Copilot and the seat-economics decision.

Microsoft 365 Copilot is sold as a per-user add-on to a qualifying M365 base plan (Business Standard, Business Premium, E3, E5, A3, A5). The buyer’s commercial question is not whether to buy Copilot; it is which subset of the user population the per-user price clears the productivity hurdle for, and on what cadence the seat assignment is reviewed.

The implementation arithmetic reads against three numbers. The Copilot per-user list price (in the current Microsoft schedule). The productivity uplift in saved hours per user per month (named in Microsoft’s own deployment guidance and re-measured by the buyer). And the loaded hourly cost of the user population the seats are being assigned to. The seat clears the hurdle where the saved hours times the loaded hourly cost exceeds the list price; it fails where the saved hours fall short.

The Admodum methodology runs a sixty-day Copilot pilot against a named user cohort, measures the saved hours through telemetry and surveys, sizes the rollout against the cohorts where the arithmetic clears, and renegotiates the seat allocation at the next true-up. The full reading sits in the M365 Copilot paper.

Azure commitment and the MACC mechanic.

The Microsoft Azure Consumption Commitment is the named instrument by which a buyer commits to a multi-year Azure spend in return for a contractual discount and access to Marketplace credit. The commitment runs against the buyer’s Azure consumption and against an expanding list of Marketplace publishers that count toward the commitment burn.

The buyer-side methodology sizes the MACC against the deployed workload (not against the seller’s forecast), structures the commitment so the Marketplace eligibility absorbs the third-party ISV spend that would otherwise sit outside Azure, and reads the burn rate quarterly against the commitment level. The full reading sits in the Azure MACC paper.

The Azure Hybrid Benefit sits alongside the MACC as the second commercial lever. Windows Server and SQL Server entitlements with active Software Assurance can be applied to Azure virtual machines, reducing the consumption charge to the compute-only rate. The Admodum methodology designs the Hybrid Benefit position alongside the MACC commitment, never as a separate optimisation.

Windows Server and SQL Server core licensing.

Windows Server and SQL Server are licensed on a per-core model with a sixteen-core minimum per processor (Windows Server Standard and Datacenter) or per virtual machine (SQL Server Enterprise and Standard, with the AlwaysOn passive-replica rule). The core-licensing arithmetic reads against the deployed cores, the virtualisation density, the disaster-recovery topology and the Software Assurance position.

The buyer-side methodology audits the deployed cores against the contracted cores, the virtualisation rights against the contracted edition (Standard versus Datacenter for Windows Server), the AlwaysOn topology against the SQL Server passive-replica rules, and the Azure Hybrid Benefit eligibility against the active Software Assurance. Each mismatch is either a contractual gap or a saving.

The Datacenter-versus-Standard edition decision is the most common Windows Server optimisation. Datacenter offers unlimited virtualisation rights on the licensed host; Standard offers two virtual machines per fully-licensed host. The crossover sits around eight virtual machines per host; high-density estates clear the Datacenter cost, low-density estates do not. The Admodum methodology sizes the edition mix against the deployed virtualisation density.

Per-user versus per-device, revisited.

Microsoft 365 and the Office productivity suite sit on a per-user metric in most enterprise configurations. The legacy per-device metric survives in named scenarios (shift-worker estates, kiosk workloads, retail floors, manufacturing terminals) where multiple users share a single device and the per-user cost would be uneconomic.

The buyer-side question is which estates qualify for the per-device path and what the trade-off looks like against the F-series Microsoft 365 Frontline plans. The F1, F3 and F5 plans price the frontline user against a reduced functional surface; the per-device path prices the device against the full functional surface but excludes the named seat. The Admodum methodology audits the workforce against the four populations (information worker, frontline, shift, kiosk) and prices each population on the appropriate plan.

The seat-assignment hygiene is the second axis. Many EAs sit on inflated seat counts because seats are assigned on hire but not unassigned on departure, on role change or on contract end. The Admodum methodology reads the active-user telemetry against the assigned-seat count and recovers the gap as a true-down at the EA renewal.

Dynamics 365 and the application-mix question.

Dynamics 365 is a modular catalogue (Sales, Customer Service, Field Service, Marketing, Finance, Supply Chain Management, Commerce, Project Operations, Human Resources, Business Central) priced on a Base-and-Attach model. The first qualifying application is the Base licence at full list; subsequent applications attach at a materially reduced rate.

The buyer-side question is which application is named as the Base, which applications attach against it, and where the Team Member licence (the reduced-functionality access licence) substitutes for a full Dynamics user. The Base-and-Attach geometry can shift the deal economics by a multi-digit percentage on a portfolio of two-thousand-plus users.

The Power Platform sits alongside Dynamics as the second user tier. Power Apps per-user, per-app and pay-as-you-go plans, Power Automate per-user and per-flow plans, and Power BI Pro and Premium each carry their own seat economics. The Admodum methodology designs the Dynamics and Power Platform mix as a single user-tier portfolio, not as two parallel transactions.

SAM audit defence and the Verification programme.

Microsoft’s Verification programme (formerly SAM Engagement) is the named compliance instrument. The Verification runs a Microsoft-nominated partner against the buyer’s deployed estate, reconciles the deployment against the contracted entitlement and closes in a remediation position that the buyer either accepts, contests or negotiates.

The buyer-side defence methodology starts before the Verification notice. The named-contact protocol, the scope-limitation moves, the data-shipment posture, the inventory reconciliation, the legal review of the partner’s findings and the negotiation of the closing position. The full methodology sits in the SAM Audit Defence paper and runs inside the Audit Defence programme.

The closing position is rarely the full Verification find. The Admodum methodology runs the closing negotiation against the contractual position, the product use rights, the deployment realities and the buyer’s EA renewal cycle. The settlement closes on the buyer’s terms.

The renewal calendar.

The Microsoft commercial relationship runs on a three-year EA cycle (or an MCA-E annual cycle, where the buyer has transitioned). The renewal window opens twelve months before EA anniversary; the negotiation runs against Microsoft’s fiscal-year-end calendar (30 June); the signature closes inside the publisher’s named fiscal quarter.

The Admodum Microsoft practice runs the cycle across every Microsoft engagement, under one of three commercial frameworks: fixed fee for scoped deliverables, contingency / gainshare for measurable savings and annual retainer for continuous coverage across the cycle.

The Microsoft knowledge hub aggregates the wider reading: the practice page, the four white papers, named case studies, blog analysis and an FAQ block for the buyer who is two clicks from a senior advisor call.

Reading list.

The pillar groups Microsoft commentary into ten sections above. The spoke band below opens the forty named articles inside the cluster, each one a deep-read on a specific Microsoft mechanic. The white papers below sit alongside the pillar as the methodology deliverables; the practice page sits alongside as the engagement entry point.

A short follow-up checklist for the reader who is closing this page: visit the Microsoft practice for the engagement entry point; visit the Microsoft knowledge hub for the aggregated reading; request the four Microsoft white papers (EA Renewal, Azure MACC, M365 Copilot, SAM Audit Defence); or open a private conversation with a senior Admodum Microsoft advisor through /contact/.