Every agreement type, every product family, every metric, every trap. Explained for the CIOs, procurement leaders, and IT asset managers who cannot afford to get this wrong. This is not a glossary. It is the complete operational guide to Microsoft licensing in 2026: how the agreements work, how the metrics are counted, where the money hides, where the compliance traps are, and how the enterprises that manage Microsoft well save 20–35% compared to those that do not.
This is the comprehensive pillar guide for the Microsoft Knowledge Hub. For the EA-specific deep-dive, see our Microsoft Enterprise Agreement Guide. For licence type comparisons, see Microsoft License Types Explained. For assessment tools, see Microsoft Assessment Tools.
Before understanding Microsoft's products and licensing metrics, you must understand the commercial vehicles through which Microsoft sells them. The agreement type determines the pricing structure, the discount mechanics, the flexibility to scale, and the exit options. Choosing the wrong agreement type can cost more than choosing the wrong product mix.
The Enterprise Agreement is Microsoft's flagship volume licensing programme for organisations with 500+ users or devices. The EA is a 3-year commitment with standardised pricing, organisation-wide deployment rights, and annual true-up obligations.
The enterprise commits to a minimum set of products (typically Microsoft 365 and/or Windows/Office licences) across the entire organisation for 3 years. Pricing is set at the beginning of the term. Each year, the enterprise reports changes in user/device counts through the annual true-up process and pays for net additions.
EA pricing is tiered by organisation size (A, B, C, D levels) with larger organisations receiving deeper base discounts. Beyond the tier discount, Microsoft offers additional negotiation discounts that vary dramatically. The difference between a well-negotiated EA and a poorly-negotiated EA can be 15–25% of total contract value. See EA pricing levels and benchmarking EA discounts.
Initial user/device count, pricing, and product mix are set.
Net additions are invoiced, but net reductions typically cannot reduce below the initial baseline. The enterprise pays for growth but does not benefit from contraction during the term.
The 6–12 months before EA expiry is when the most significant cost reductions are negotiated. Microsoft needs the renewal. The enterprise has the option to renew, transition to MCA, move to CSP, or evaluate non-Microsoft alternatives. See the EA renewal preparation toolkit.
The MCA is Microsoft's newer agreement framework, gradually positioned as the successor to the EA. Unlike the EA's fixed 3-year term, the MCA provides more flexible subscription structures with annual or monthly commitment options. The MCA can offer greater flexibility but may reduce the enterprise's negotiation leverage compared to a 3-year EA commitment. See our CIO playbook for evaluating EA vs MCA vs CSP.
The CSP programme allows organisations to purchase Microsoft cloud subscriptions through a partner. CSP provides seat-level flexibility but typically at higher per-unit pricing and with less negotiation leverage than an EA. See EA vs CSP vs MCA decision guide.
Microsoft also offers the MPSA for transactional purchasing, Open Value for smaller organisations, the Server and Cloud Enrollment (SCE) for infrastructure, and Direct vs Indirect EA structures. See MPSA and other licensing programmes.
For most enterprises, Microsoft 365 represents the single largest line item in the Microsoft relationship. The choice between plans, the assignment of the correct SKU to each user, and the management of add-ons determine whether the enterprise pays a fair price or overpays by 20–40%.
| Plan | Price | Target User | Key Inclusions |
|---|---|---|---|
| M365 F3 | ~$8/user/month | Frontline workers (retail, manufacturing, warehouse, healthcare) | Limited Office web apps, Exchange (2 GB), Teams, basic security. No desktop Office. |
| M365 E3 | ~$36/user/month | Standard knowledge workers (70–80% of enterprise) | Full desktop Office, Exchange Online (100 GB), Teams, SharePoint, OneDrive, Intune, Entra ID P1, information protection. |
| M365 E5 | ~$57/user/month | Security, compliance, and telephony users | Everything in E3 plus Defender for Office 365 P2, Cloud App Security, Entra ID P2, eDiscovery Premium, Advanced Audit, Phone System. 58% more than E3. |
The optimisation opportunity: Most enterprises achieve 15–25% savings by properly segmenting their user base across F3, E3, and E5 rather than defaulting all users to E3 or E5. A 10,000-user enterprise that moves 2,000 frontline workers from E3 to F3 saves approximately $672,000 annually. See the E3 vs E5 vs F3 comparison and the licence optimisation calculator.
Beyond the core plans, Microsoft offers dozens of add-ons: Power BI Pro ($10/user/month), Project Plan 3 ($30/user/month), Visio Plan 2 ($15/user/month), Intune add-ons, Defender add-ons, compliance add-ons. The cumulative effect across an enterprise is a per-user cost that can exceed the base E3/E5 price by 30–50%. The add-on layer is where Microsoft generates incremental revenue and where procurement teams must exercise discipline.
Microsoft has implemented multiple price increases across M365 SKUs since 2022. EA customers with existing agreements are protected by the pricing set at agreement inception, but renewal is where the increases bite. See negotiating price protections and the 2026 pricing and discounts playbook.
Microsoft's unbundling of Teams from Microsoft 365 creates both a licensing complexity and an optimisation opportunity. Enterprises can now purchase M365 without Teams and license Teams separately, or use a competitor like Slack or Zoom. The unbundling makes the true cost of Teams visible and creates genuine negotiation leverage.
Azure is consumption-based: you pay for what you use, measured in compute hours, storage gigabytes, network bandwidth, and service-specific metrics. The consumption model creates flexibility but also creates cost unpredictability that can turn Azure from a strategic platform into a budget crisis.
Within an EA, organisations can make Azure consumption commitments (MACC) at discounted rates. Over-committing results in wasted pre-payment. Under-committing results in a significant portion at pay-as-you-go rates. The optimal commitment requires accurate forecasting. See negotiating Azure commitments and managing Azure overages.
1-year or 3-year commitments for specific VM sizes provide 30–72% savings over pay-as-you-go. The savings are substantial but the commitment is real: an RI for a specific VM size in a specific region must be consumed or it is wasted. Purchase RIs only for workloads with predictable, consistent usage.
Enterprises with Windows Server or SQL Server licences covered by active SA can apply those licences to Azure VMs, reducing compute costs by 40–55% for Windows Server and 55%+ for SQL Server. When combined with Reserved Instances, savings stack to 70–80% versus pay-as-you-go. See the BYOL vs Azure licensing calculator.
Right-sizing (matching VM sizes to actual workload requirements) typically reduces compute costs by 20–40%. Auto-scaling eliminates paying for idle capacity. Azure Advisor provides built-in recommendations that most enterprises never act on.
Azure OpenAI Service (GPT-4, GPT-4o) is token-based pricing with significant variation between models. For enterprises deploying AI at scale, costs can reach six or seven figures annually. See Azure OpenAI pricing guide and negotiation guide.
Enterprises that actively manage Azure consumption spend 25–40% less than those that deploy and forget. See our Azure licensing and cost optimisation playbook and the Azure cost optimisation assessment.
Windows Server and SQL Server licensing remains among the most complex and error-prone areas of Microsoft licensing. Both products use core-based licensing models that interact with virtualisation, hybrid cloud, and Software Assurance.
| Edition | Licensing Model | Virtualisation Rights | Best For |
|---|---|---|---|
| Standard | Per physical core (min 16 cores/server). ~$6,156 per 16-core set. | Up to 2 OS environments (VMs) per set of 16 core licences. Additional VMs require additional sets. | Small number of VMs per host (1–4). |
| Datacenter | Per physical core (min 16 cores/server). ~$6,156 per 16-core set. | Unlimited virtualisation rights on the licensed physical server. | Dense virtualisation (4+ VMs per host). Crossover is typically 4–8 VMs. |
The virtualisation trap: Windows Server licensing in virtualised environments is the most common area of Microsoft audit findings. Each VM requires core licences for the physical host, with different rules for Standard (2 VMs per licence set) and Datacenter (unlimited VMs). Miscounting VMs or misunderstanding the Standard Edition stacking rules generates compliance gaps that auditors identify immediately. See core-based licensing mechanics.
In addition to core licences, every user or device accessing Windows Server services requires a Windows Server CAL. CALs are per user or per device. The CAL requirement is separate from and additional to the core licences.
| Edition | Price (per 2-core pack) | Limits | Key Decision Factor |
|---|---|---|---|
| Standard | ~$3,945 | 24 cores per instance, 128 GB memory | Departmental databases, applications not requiring Enterprise features. |
| Enterprise | ~$15,123 (3.8× Standard) | No resource limits | Required for Always On AG (2+ replicas), columnstore indexes, in-memory OLTP. See edition strategy guide. |
SQL Server Enterprise is 3.8× more expensive than Standard per core. The decision to deploy Enterprise should be driven by a documented requirement for Enterprise-only features, not by default or convenience. See common SQL Server compliance pitfalls and the SQL Server licensing calculator.
Dynamics 365 licensing is one of the most complicated areas in the Microsoft ecosystem. It uses a combination of base licences, attach licences, capacity add-ons, and module-specific pricing that varies by application family.
Each Dynamics 365 application (Sales, Customer Service, Finance, Supply Chain Management, Human Resources, Marketing) has its own per-user pricing. Users can be licensed for a "base" application at full price and "attach" additional applications at reduced pricing (typically 60–70% off standalone). The attach model encourages adding modules the enterprise may not fully utilise.
The attach trap: The distinction between base and attach licensing is not always intuitive. Licensing a user for the wrong base application can result in paying full price for what should have been an attach licence. See common Dynamics 365 licensing mistakes, the CIO advisory playbook, and Dynamics 365 in Enterprise Agreements.
Microsoft Copilot is the most significant new licensing cost in the Microsoft ecosystem in 2026. Microsoft 365 Copilot, priced at $30/user/month, adds a substantial per-user cost layer on top of existing M365 licensing.
| Configuration | Monthly Per-User Cost | Annual Cost (5,000 Users) |
|---|---|---|
| E3 + Copilot | $66/user/month | $3,960,000 |
| E5 + Copilot | $87/user/month | $5,220,000 |
| Copilot Only (Add-On) | $30/user/month | $1,800,000 |
Copilot does not need to be deployed to every user. A phased rollout, deploying to high-value user segments (executives, analysts, sales teams, content creators) and measuring productivity impact before expanding, provides both cost control and ROI evidence. The enterprise that deploys to 100% of users on day one pays for 100% of the licences while the productivity benefit is concentrated in perhaps 20–30% of the user base. See negotiating Copilot pricing and the Copilot ROI assessment.
Microsoft's AI services introduce data usage and privacy terms that require legal review. Questions of data residency, model training on customer data, output ownership, and liability for AI-generated content must be addressed. See AI services terms analysis.
Software Assurance (SA) is Microsoft's annual maintenance programme for on-premise products. SA provides version upgrade rights, deployment flexibility, training vouchers, Azure Hybrid Benefit, and other rights. It is purchased as a percentage of the licence cost, typically 25–29% annually.
SA provides genuine value when the enterprise actively uses the benefits: Azure Hybrid Benefit (40–55% savings on Azure VM costs), version upgrade rights for on-premise products, and License Mobility for moving workloads to cloud. For organisations pursuing hybrid cloud strategies, SA can deliver a strong ROI.
SA on products that will never be upgraded, that are not being moved to Azure, and where the enterprise does not use training vouchers or other benefits is pure cost with no return. The decision to renew or drop SA should be evaluated product-by-product, not as a blanket decision. See the SA CIO playbook.
The EA true-up is an annual reconciliation where the enterprise reports changes in licences deployed. Net additions are invoiced. Net reductions are not credited in most EAs.
Why the true-up is a cost leak: Most enterprises over-report because they lack accurate, real-time licence deployment data. The IT team reports "estimated" user counts that include buffer for growth. The buffer is invoiced at full price. Over three years, cumulative over-reporting can amount to 5–15% of the total EA value.
60 days before each anniversary date, not the week before. Reconcile Active Directory user counts against actual M365 assignments.
Dormant accounts, service accounts, and terminated employees with active licences are common over-counts.
For server products, reconcile physical deployments against the contract.
If your organisation is undergoing headcount reductions or divestitures, negotiate step-down provisions (typically 10–20% of baseline) before signing the EA. See the true-up guide and risk assessment.
Microsoft conducts licence compliance audits ("Software Asset Management Reviews") that verify deployed products against purchased entitlements. The financial consequences of non-compliance are significant.
Recently reduced Microsoft spend signals potential under-licensing.
Reporting that shows unusual patterns triggers scrutiny.
Mergers and acquisitions create licence gaps that Microsoft targets.
Audit findings create renewal urgency and weaken negotiation position.
The most frequent findings involve Windows Server virtualisation miscounts, SQL Server edition discrepancies (Enterprise deployed where Standard is licensed), Office/M365 deployment exceeding purchased quantities, and Dynamics 365 user count discrepancies. Penalties can range from hundreds of thousands to millions. Enterprises that engage professional audit defence before responding consistently achieve 30–60% reductions in the initial compliance claim. See our audit survival checklist and audit settlement guide.
Microsoft Unified Support replaced Premier Support and is priced as a percentage of the enterprise's total Microsoft spend (typically 4–10%). For large customers, this percentage-based model produces support costs that can reach seven figures annually.
The percentage rate, the qualifying revenue base, and the support tier (Core, Advanced, Performance) all affect the total cost. Third-party support and pay-per-incident models should be evaluated as negotiation leverage. See Unified Support negotiation strategies and choosing the right support level.
Microsoft licensing in virtualised environments follows product-specific rules. Windows Server, SQL Server, and other products each have distinct virtualisation mechanics involving core counting, VM counting, and SA requirements. See the CIO playbook for hybrid environments.
The shift to remote and hybrid work has created new licensing requirements for VDI, Azure Virtual Desktop, Citrix/VMware deployments, and BYOD scenarios.
Corporate transactions create complex challenges: consolidating tenants and contracts, EA novation and transfer, and splitting entitlements during divestitures.
The Power Platform (Power BI, Power Apps, Power Automate) uses per-user and per-app models that escalate costs quickly. Uncontrolled proliferation, particularly Power Apps premium connectors and Power Automate RPA flows, generates unexpected licensing costs.
The EA renewal is the single most important Microsoft commercial event in a 3-year cycle. Begin with a licence usage review and establish strategy 12+ months before the renewal date. See building the renewal negotiation team.
The most effective lever is credible competitive alternatives: Google Workspace, AWS/GCP, PostgreSQL, Salesforce. Even partial substitution threats create pricing flexibility. See the EA renewal playbook.
Microsoft EA pricing varies significantly between customers. Benchmarking your EA discounts against peers reveals whether your pricing is competitive or inflated. Without benchmarks, you negotiate based on Microsoft's assertion of what constitutes a "good deal."
Price protections, termination and renewal options, future-proofing for new technology, and Azure support terms all affect total cost of ownership.
Enterprise Microsoft estates routinely contain redundant licensing: users with both E3 and standalone Exchange licences, SA on products that should have been cloud-migrated, overlapping Dynamics 365 and Power Platform capabilities. A thorough redundancy audit typically identifies 5–15% savings.
Microsoft deals worth $1M+ per year warrant independent advisory support. The advisory fee is a fraction of the cost reduction achieved. See key leverage points.
Achieved 35% savings through competitive leverage and licence optimisation.
Realised 26% savings by unifying global licensing under a single optimised EA.
Saved 30% while increasing contract flexibility.
Cut costs 25% while securing hybrid cloud agility.
Microsoft is steering customers from EAs to MCAs. The MCA is not inherently worse, but it requires careful evaluation. The EA's 3-year commitment creates negotiation leverage that the MCA's more flexible structure may not replicate. See 2025–2026 licensing trends.
Copilot at $30/user/month is the first wave. Expect additional AI-powered features as paid add-ons across the suite. The cumulative AI cost layer could add 20–40% to per-user costs over the next 2–3 years. See negotiating generative AI contracts.
As enterprises migrate more workloads to Azure, the consumption component grows relative to per-user licensing. This shifts the optimisation focus from licence count management to consumption governance.
"Microsoft licensing is the largest single vendor line item in most enterprise IT budgets. It is also the line item most frequently managed on autopilot: renewals processed without negotiation, true-ups submitted without validation, new products adopted without licence impact analysis. The enterprises that treat Microsoft as a managed commercial relationship save 20–35% compared to those that do not. That gap, on a $5M Microsoft relationship, is $1M–$1.75M per year. Every year."
— Fredrik Filipsson, Co-Founder, Redress Compliance
For enterprises with 500+ users, the Enterprise Agreement (EA) typically provides the best pricing and most comprehensive terms. The EA offers a 3-year commitment with tiered discounts, annual true-up flexibility, and the ability to negotiate additional discounts. However, the MCA is being positioned as an alternative with more flexibility for cloud-first organisations. The optimal choice depends on your size, growth trajectory, Azure commitment, and negotiation leverage.
The highest-impact strategies: segment users across F3/E3/E5 plans based on actual requirements (15–25% savings), optimise Azure consumption through Reserved Instances and right-sizing (25–40% cloud savings), eliminate redundant licensing (5–15% savings), manage true-ups accurately, negotiate the EA renewal with competitive leverage and independent benchmarks (15–25% additional discount), and evaluate Software Assurance value product-by-product. Combined, these strategies typically deliver 20–35% total cost reduction.
Microsoft 365 Copilot is licensed at $30/user/month and requires a qualifying M365 plan (E3 or E5) as prerequisite. Copilot cannot be purchased standalone. The total per-user cost is $66/month (E3 + Copilot) or $87/month (E5 + Copilot). Copilot does not need to be deployed to all users. A phased rollout targeting high-value user segments provides cost control and ROI evidence before broader deployment.
The most frequent findings involve Windows Server virtualisation miscounts (incorrect VM-to-core mapping), SQL Server edition discrepancies (Enterprise deployed where Standard is licensed), Microsoft 365 or Office deployment exceeding purchased quantities, and Dynamics 365 user count discrepancies. Most findings can be prevented through regular internal licence reviews using Microsoft's SAM tools.
Evaluate both options at renewal. The EA provides stronger negotiation leverage through the 3-year commitment, predictable pricing, and established discount structures. The MCA provides more flexibility with shorter commitment terms and easier scaling. For organisations with stable Microsoft usage and strong negotiation positions, the EA typically delivers better economics. Model both options across the full agreement period before deciding.
Azure Hybrid Benefit allows enterprises with Windows Server or SQL Server licences covered by active SA to use those licences to offset Azure compute costs. For Windows Server VMs, this saves 40–55%. For SQL Server on Azure VMs or Azure SQL Database, savings can be 55% or more. The benefit is available on both reserved and pay-as-you-go instances. It is one of the highest-ROI benefits of maintaining SA on server products being migrated to Azure.