Microsoft licensing is not complicated because the products are complex. It is complicated because the complexity benefits Microsoft. Every answer below cuts through the programme rules to the commercial decision that actually matters.
Microsoft is the largest enterprise software vendor in the world by revenue and the most complex by licensing structure. The average enterprise holds 6–12 different Microsoft agreements simultaneously: Enterprise Agreements, CSP subscriptions, SPLA for hosting, OEM pre-installs, Visual Studio subscriptions, and Azure commitments. Each has different terms, different metrics, and different renewal cycles. This complexity is not accidental: it creates information asymmetry that consistently benefits Microsoft in every negotiation.
Microsoft’s licensing team is excellent at explaining programme rules. They are less forthcoming about which programme rules are negotiable, which programme structures cost you the most, and which alternatives would save you 20–40%. This FAQ provides the commercial context that Microsoft’s documentation leaves out.
Jump to section: Fundamentals (1–10) | Microsoft 365 (11–20) | Azure (21–28) | Server and On-Premise (29–36) | Compliance and Audits (37–43) | Negotiation (44–50)
The foundational questions every procurement leader and IT asset manager needs to answer before any Microsoft commercial event.
A Microsoft Enterprise Agreement is a three-year volume licensing contract for organisations with 500 or more users or devices. It provides organisation-wide licensing for Microsoft products (Windows, Office/Microsoft 365, CALs) at discounted per-user or per-device pricing, with annual true-up obligations and an option to add Azure and other cloud services.
Commercial reality: The EA is Microsoft’s primary lock-in mechanism. The three-year term, annual true-up requirement, and organisation-wide commitment create significant switching costs. However, the EA is also where you have the most negotiation leverage, because Microsoft values EA renewals above almost all other revenue. Every EA term, every pricing level, and every add-on is negotiable. Organisations that treat the EA as a take-it-or-leave-it programme overpay by 15–30%. See EA Negotiation Strategies.
An Enterprise Agreement is a direct three-year commitment with Microsoft, offering the deepest discounts and broadest terms for large organisations. A Cloud Solution Provider (CSP) subscription is a month-to-month or annual subscription purchased through a Microsoft partner, with simpler terms but less discount depth and fewer negotiation levers.
Commercial reality: CSP is cheaper on a per-unit, short-term basis for organisations under 500 users or those wanting flexibility. But above 500 users, an EA almost always provides deeper discounts (10–25% lower per-seat cost) plus negotiation leverage that CSP cannot match. The trap: some organisations use CSP alongside an EA without realising the overlap creates duplicate licensing costs. Consolidate before your next renewal.
The Microsoft Products and Services Agreement (MPSA) is a transactional volume licensing agreement for organisations that want to purchase Microsoft licences without a three-year commitment. It provides volume discounts based on cumulative purchase points but lacks the organisation-wide pricing and negotiation flexibility of an EA.
Commercial reality: MPSA is typically 10–20% more expensive than an equivalent EA for the same products. Microsoft positions MPSA as “flexible,” but the flexibility comes at a premium. For organisations with 500+ users, an EA is almost always the better commercial structure. MPSA makes sense primarily for organisations below the EA threshold or those in transition between agreement types.
The Microsoft Customer Agreement is a simplified, click-through licensing agreement that replaced the Microsoft Cloud Agreement. It governs Azure, Microsoft 365, Dynamics 365, and Power Platform purchases through CSP partners or direct. It is not negotiable in the same way as an EA: terms are standard and accepted electronically.
Commercial reality: The MCA’s simplicity is a double-edged sword. Standard terms mean no negotiation on data processing, SLA credits, or liability caps. For organisations with significant cloud spend, negotiate an Enterprise Agreement or a direct agreement with Microsoft that provides customised terms, particularly around data sovereignty, security commitments, and termination rights.
A true-up is an annual reconciliation under an Enterprise Agreement where you report any increase in users, devices, or subscriptions since the last anniversary. You pay for the additional quantity at your EA pricing. True-ups occur at each EA anniversary date and you cannot defer them.
Commercial reality: True-ups only go up. The standard EA does not include true-down rights. If you over-deployed in Year 1 and reduced in Year 2, you still pay for the Year 1 peak. Negotiate true-down provisions at EA signing: the ability to reduce quantities at each anniversary if usage decreases. This is not standard but is achievable in mid-to-large EA deals. Without it, you pay for ghost users indefinitely.
Microsoft’s Enterprise Agreement uses pricing levels based on your total quantity of qualifying desktop licences. Level A: 500–2,399. Level B: 2,400–5,999. Level C: 6,000–14,999. Level D: 15,000+. Higher levels receive deeper base discounts.
Commercial reality: The level determines your starting discount, but not your ending discount. Organisations that accept level-based pricing without further negotiation leave 5–20% on the table. Microsoft’s Enterprise sales team has discretionary discount authority above the level-based price for strategic accounts, competitive situations, and large commitments. The level is a floor, not a ceiling.
Software Assurance (SA) is an annual maintenance programme that provides version upgrade rights, deployment planning services, training vouchers, and mobility rights (the ability to move licences to authorised cloud environments). SA is typically included in EA subscriptions and costs approximately 25–29% of the licence price annually for standalone purchases.
Commercial reality: The key SA benefit is License Mobility, which allows you to deploy SA-covered server licences in shared hosting or cloud environments without repurchasing. If you are not using SA benefits (version upgrades, mobility, training vouchers), you are paying for insurance you never claim. Audit your SA utilisation before renewal.
A Client Access Licence (CAL) grants a user or device the right to access a Microsoft server product (Windows Server, SQL Server, Exchange Server, SharePoint Server). CALs are required for each user or device accessing the server. The server licence alone does not include access rights. CALs come in User CAL (per person) and Device CAL (per device) variants.
Commercial reality: CALs are the most frequently under-licensed Microsoft product in audits. Organisations that have migrated to Microsoft 365 often assume cloud subscriptions replace CAL requirements. They do for Exchange Online and SharePoint Online, but not for on-premise servers that remain active during migration. If you run hybrid environments, you likely need both cloud subscriptions and on-premise CALs.
Per-user licensing covers one named individual across all their devices, ideal when employees use multiple devices (laptop, tablet, phone). Per-device licensing covers one device regardless of how many users share it, ideal for shared workstations, kiosks, and factory-floor devices. Choosing the wrong model can double your licence count.
Commercial reality: The default Microsoft motion is per-user (it aligns with the M365 subscription model). But organisations with shift workers, shared devices, or high device-to-user ratios save 20–40% by licensing those specific scenarios per-device. Run both models against your actual deployment data before committing at EA renewal.
Microsoft’s fiscal year ends June 30. The final quarter (April–June) is when Microsoft’s sales teams face maximum quota pressure and discount authority is at its peak.
Commercial reality: EA renewals and new agreements signed in Q4 (April–June) consistently achieve 5–15% deeper discounts than equivalent deals in Q1–Q3. On a $3M EA, timing alone can save $150K–$450K. Structure your EA renewal timeline to conclude negotiations in May–June, but maintain the credible option to defer if terms are not acceptable.
Microsoft 365 is Microsoft’s fastest-growing revenue stream and the area where most organisations have the greatest optimisation opportunity, because most are over-licensed by 15–30%.
M365 E3 ($36/user/month list) includes Office apps, Exchange Online, SharePoint, Teams, Intune, Azure AD P1, and Windows Enterprise. M365 E5 ($57/user/month list) adds Phone System, Power BI Pro, Defender for Office 365 P2, Azure AD P2, eDiscovery, and advanced compliance tools.
Commercial reality: E5 costs 58% more than E3. Most organisations deploy E5 for the security features (Defender, Azure AD P2) and phone system, but fewer than 40% of E5 users actually consume the advanced features that justify the premium. The optimal strategy for most: E3 for the majority of users, E5 for IT, security, legal, and executive teams, with standalone add-ons (Defender P2, Phone System) where needed. This mixed-SKU approach saves 15–25% versus blanket E5 deployment.
Yes. Microsoft allows mixed-SKU deployments within an Enterprise Agreement. You can assign E3 to some users and E5 to others based on role requirements.
Commercial reality: Microsoft’s sales team will push blanket E5 because the per-seat revenue is 58% higher. They position it as “simpler to manage” and “better security posture.” In reality, mixed-SKU deployments are straightforward to manage with Azure AD group-based licensing. On a 5,000-user organisation, moving from blanket E5 to 70% E3 / 30% E5 saves approximately $500K annually.
M365 F1 ($2.25/user/month) provides web and mobile Office apps, Teams, and basic security for frontline workers who use shared devices. M365 F3 ($8/user/month) adds desktop Office apps on shared devices, Intune, and Windows Virtual Desktop access.
Commercial reality: F-series licences cost 75–94% less than E3. Organisations with large frontline workforces (retail, manufacturing, healthcare) that licence everyone on E3 are dramatically over-spending. A 10,000-user organisation with 6,000 frontline workers switching from E3 to F3 saves approximately $2M annually. The challenge: accurately categorising users as frontline vs information workers requires HR and IT collaboration.
It depends on which on-premise servers remain active. Microsoft 365 E3/E5 includes rights to access Exchange Online, SharePoint Online, and Teams, but not on-premise Exchange Server, SharePoint Server, or Skype for Business Server. If those servers are still running, you need on-premise CALs in addition to your M365 subscriptions.
Commercial reality: Hybrid environments during cloud migration are the most common source of Microsoft over-licensing. Organisations pay for both M365 subscriptions and on-premise CALs during the transition, and forget to drop the CALs once migration completes. Audit your hybrid licensing 90 days after each migration milestone and remove redundant entitlements.
Microsoft 365 Copilot is an AI assistant integrated into Office apps, Teams, and Outlook. It requires a Microsoft 365 E3 or E5 base licence plus a Copilot add-on at $30/user/month ($360/user/year). The add-on is licensed per-user with a minimum seat count in most EA deals.
Commercial reality: At $30/user/month, Copilot is the most expensive M365 add-on ever introduced, adding 83% to the cost of an E3 licence. Microsoft is pushing blanket deployment, but early adoption data shows actual usage varies dramatically by role. Pilot Copilot with 10–15% of your user base for 90 days, measure productivity impact, and deploy selectively based on demonstrated ROI. Negotiate Copilot pricing separately from your EA base. Achievable discounts of 10–25% with commitment volume.
Under standard EA terms, you can reduce subscription quantities only at the EA anniversary (true-up). Downgrading from E5 to E3 mid-term requires replacing the E5 subscription with E3, which may be subject to minimum commitment terms in your EA.
Commercial reality: Microsoft’s default EA terms make mid-term downgrades difficult by design. Negotiate downgrade and true-down rights at EA signing: the explicit right to reduce quantities or change SKU levels at each anniversary without penalty. This single negotiation point protects you from being locked into a licensing level that no longer matches your needs.
After subscription cancellation, Microsoft provides a 90-day retention period during which data is accessible but the account is in a disabled state. After 90 days, data is permanently deleted and unrecoverable.
Commercial reality: 90 days is insufficient for enterprise-scale data migration from Exchange Online, SharePoint, OneDrive, and Teams. Negotiate extended retention (180–365 days), defined export formats, and continued read-only access during the transition period. These terms are achievable in EA renewals where Microsoft faces competitive risk.
Teams free: basic chat, video (60 min), 5 GB storage. Teams Essentials ($4/user/month): unlimited meetings, 10 GB storage, no Office apps. Teams in M365 E3/E5: full Teams functionality with Office integration, compliance tools, meeting recordings, and enterprise administration.
Commercial reality: Microsoft uses Teams as a gateway to full M365 adoption. Once an organisation standardises on Teams for meetings and collaboration, the switching cost to competing platforms (Slack, Zoom, Google Meet) increases significantly. If you are evaluating Teams, evaluate it as the entry point to a multi-year M365 commitment, not as a standalone communications tool.
Power BI Pro is included in M365 E5 or available standalone at $10/user/month. Power BI Premium starts at $4,995/capacity/month. Power Apps starts at $20/user/app/month. Power Automate starts at $15/user/month. Pricing varies significantly by usage pattern and whether you need per-user or per-capacity licensing.
Commercial reality: Power Platform is Microsoft’s fastest-growing add-on revenue stream and the area where licensing complexity creates the most unexpected costs. “Seeded” Power Apps and Power Automate capabilities included in M365 are deliberately limited to drive standalone purchases. If your organisation is building citizen-developer applications on Power Platform, model the licensing cost at scale before deploying. Costs escalate rapidly from pilot to production.
Plan 1 ($4/user/month, included in M365 E3): 50 GB mailbox, basic archiving. Plan 2 ($8/user/month, included in M365 E5): unlimited archiving, Data Loss Prevention, in-place hold, advanced compliance.
Commercial reality: Most organisations need Plan 2 only for users subject to regulatory retention requirements (legal, finance, compliance). Deploying Plan 2 organisation-wide because “a few departments need archiving” doubles the Exchange cost. Use M365 E3 for most users and add Exchange Online Plan 2 as a standalone add-on for regulated roles.
Azure is Microsoft’s fastest-growing business, and its consumption-based pricing model creates unique cost management challenges that differ fundamentally from traditional licensing.
Azure uses consumption-based pricing: you pay for compute, storage, networking, and services based on actual usage, measured in per-second, per-hour, or per-GB increments. Discounts are available through Reserved Instances (1 or 3-year commitments), Azure Savings Plans, and EA-negotiated rates.
Commercial reality: The consumption model sounds fair but creates cost unpredictability. Without governance, Azure spend typically exceeds projections by 20–40%. The key levers: Reserved Instances (save 30–72% on predictable workloads), Azure Savings Plans (save 15–30% with flexible commitments), and right-sizing (most VMs are over-provisioned by 30–50%). Implement FinOps practices before committing to Azure at scale.
A MACC is a pre-committed Azure spend over a defined period (typically 1–3 years), negotiated as part of an EA or direct agreement. In exchange for a commitment, you receive a discount on consumption rates, often 5–15% below standard pricing.
Commercial reality: MACCs are Microsoft’s primary Azure lock-in mechanism. The discount is real, but the commitment creates use-it-or-lose-it pressure. If you under-consume, you forfeit the remaining commitment at term end. Size your MACC at 70–80% of projected consumption and negotiate: credit rollover for unused amounts, true-down rights if business needs change, and flexibility to apply credits across Azure services without restriction.
Azure Hybrid Benefit (AHB) allows you to use existing Windows Server and SQL Server licences with active Software Assurance on Azure VMs, reducing compute costs by up to 40% for Windows and up to 55% for SQL Server compared to pay-as-you-go rates.
Commercial reality: AHB is one of the most valuable and most under-utilised benefits in Microsoft licensing. Many organisations pay full Azure rates while sitting on hundreds of unused SA-covered licences. Audit your on-premise licence inventory against your Azure deployment: every SA-covered Windows Server or SQL Server licence not applied to Azure is money being left on the table.
Three options: (1) Azure SQL Database (PaaS, fully managed, pay per DTU or vCore), (2) SQL Server on Azure VMs (IaaS, bring your own licence or pay licence-included rates), (3) Azure SQL Managed Instance (PaaS with near-100% SQL Server compatibility). AHB applies to options 2 and 3.
Commercial reality: Licence-included Azure SQL pricing is 2–3× the cost of BYOL. If you have SQL Server Enterprise with SA, use AHB for every Azure SQL workload. For new deployments without existing licences, Azure SQL Database (PaaS) is typically 30–50% cheaper than SQL on VMs for equivalent performance, but evaluate compatibility requirements carefully before choosing PaaS over IaaS.
Reserved Instances (RIs) are 1-year or 3-year commitments to specific Azure VM sizes in specific regions. In exchange for the commitment, you receive 30–72% discount versus pay-as-you-go pricing. RIs can be exchanged (same VM family) or cancelled with an early termination fee.
Commercial reality: RIs are the single highest-impact Azure cost optimisation lever. Most organisations have 40–60% of their Azure compute running on predictable, steady-state workloads that qualify for RIs. The 3-year term provides the deepest discount but requires confidence in the workload’s longevity. Start with 1-year RIs for workloads you are confident about, then extend to 3-year as you build Azure consumption data.
Azure Savings Plans are flexible 1-year or 3-year commitments to a fixed hourly spend (e.g., $50/hour). The commitment applies across any VM family, region, or operating system, offering 15–30% savings with more flexibility than RIs.
Commercial reality: Savings Plans complement RIs: use RIs for predictable, stable workloads (maximum discount) and Savings Plans for workloads where VM family or region may change. The optimal strategy combines both: RI coverage for 50–70% of steady-state compute and Savings Plans for the flexible remainder. Together, they can reduce total Azure compute costs by 35–55%.
Yes, through License Mobility (for server applications with SA) and Azure Hybrid Benefit (for Windows Server and SQL Server with SA). Most server products qualify for License Mobility. Windows Desktop licences require Windows Enterprise E3/E5 subscriptions or VDA for Azure Virtual Desktop access.
Commercial reality: License Mobility and AHB are powerful cost reducers, but the rules differ by product and require active SA. If your SA lapses, you lose mobility rights and must repurchase at cloud rates. Before your next EA renewal, map every SA-covered licence to its potential Azure utilisation. If you are not using SA mobility rights, either activate them or consider dropping SA to save 25–29% of licence cost annually.
Direct comparison is complex because pricing varies by VM type, region, commitment model, and licensing. Generally, Azure is 5–15% cheaper for Windows and SQL Server workloads (due to AHB), while AWS is 5–10% cheaper for Linux and open-source workloads.
Commercial reality: The licensing advantage is Microsoft’s strongest Azure differentiator for Windows-heavy organisations. Running Windows Server on AWS requires paying Microsoft licensing separately (or using AWS-included rates, which are higher). This creates a structural cost advantage for Azure that can reach 30–40% for SQL Server workloads with AHB. For multi-cloud strategies, run Windows/SQL on Azure and Linux/open-source on AWS for optimal cost.
Despite the cloud migration trend, most enterprises will run hybrid environments for 5–10+ years. On-premise licensing remains critical and frequently non-compliant.
Windows Server is licensed per physical core, with a minimum of 16 cores per server (8 cores per processor, minimum 2 processors). Standard Edition covers 2 VMs per set of 16 core licences. Datacenter Edition covers unlimited VMs on the licensed server. Both require CALs for user/device access.
Commercial reality: The Standard vs Datacenter decision is purely economic: if you run more than 2 VMs per server, Datacenter is cheaper. With modern servers running 10–50+ VMs, most virtualised environments should be on Datacenter. Organisations on Standard who have grown their VM count are often unknowingly under-licensed. Each additional pair of VMs beyond the initial 2 requires another set of Standard core licences. Calculate your actual VM-to-host ratio before your next audit.
SQL Server offers two licensing models: Per-core (licensed by physical cores, minimum 4 cores, sold in 2-core packs) and Server + CAL (one server licence plus a CAL per accessing user or device). Enterprise Edition is per-core only. Standard Edition supports both models.
Commercial reality: Per-core licensing is Microsoft’s preferred model and the one they push. But for SQL Server Standard with fewer than approximately 20 users, Server+CAL is significantly cheaper. Run both calculations for every SQL deployment. Also note: SQL Server Enterprise ($15,123 per 2-core pack) is 4× the cost of Standard ($3,945 per 2-core pack). Many organisations deploy Enterprise for features available in Standard, creating massive over-spend. Right-size your SQL editions before renewal.
The Services Provider License Agreement (SPLA) is a monthly licensing programme for service providers and hosting companies that provide Microsoft software-based services to third parties. If you host applications for external users or customers using Microsoft software, you need SPLA, not an EA or volume licence.
Commercial reality: SPLA is one of the most misunderstood Microsoft licensing areas. Organisations that host Microsoft-based applications for subsidiaries, clients, or partners without SPLA are in violation even if they hold an EA. The test: are external users accessing Microsoft software on your infrastructure? If yes, SPLA applies. This frequently surfaces in audit findings for managed service providers, SaaS companies, and shared-service centres.
Yes. Microsoft’s virtualisation licensing is more straightforward than Oracle’s. For Windows Server Datacenter: unlimited VMs on the licensed physical cores. For Standard: 2 VMs per licence set. For SQL Server: licensed by the physical cores allocated to the VM (not the entire host), with SA-enabled License Mobility for server applications.
Commercial reality: Microsoft’s virtualisation rules are more customer-friendly than Oracle’s, but they still create compliance exposure. The most common mistake: licensing Windows Server Standard and running more VMs than the licence covers. With Datacenter, there is no VM limit, making it the “safe” choice for heavily virtualised environments. The additional cost of Datacenter over Standard is justified the moment you exceed 2 VMs per host.
Windows E3 ($7/user/month) adds enterprise security (BitLocker, Credential Guard, AppLocker) and management features over Windows Pro. Windows E5 ($11/user/month) adds Microsoft Defender for Endpoint P2 and advanced threat protection. Both are included in the corresponding M365 E3/E5 plans.
Commercial reality: If you are purchasing M365 E3 or E5, Windows Enterprise is already included. Do not purchase it separately. Organisations with standalone Windows Enterprise subscriptions alongside M365 are double-paying. Consolidate into M365 at EA renewal for 10–15% net savings versus purchasing components separately.
ESU provides critical and important security updates for Microsoft products that have reached end of support (Windows Server 2012/R2, SQL Server 2012/2014). ESU is purchased annually at 75% of the licence cost for Year 1, increasing each subsequent year. ESU is free for workloads running in Azure.
Commercial reality: ESU is deliberately expensive to incentivise migration. At 75% of licence cost per year (increasing annually), ESU costs more than the original licence within 2 years. For most organisations, the better strategy is: migrate to Azure (ESU is free), upgrade to a supported version, or migrate to a cloud-native alternative. If you are paying for ESU on-premise, calculate the Azure migration cost. The ESU savings alone often justify the move.
Co-management rights allow you to manage devices with both Microsoft Endpoint Configuration Manager (SCCM/MECM) and Microsoft Intune simultaneously, enabling a gradual migration from on-premise to cloud management. Co-management is available with Intune licences included in M365 E3/E5.
Commercial reality: Co-management is a transition mechanism, not a permanent state. Microsoft’s strategic direction is full Intune management (cloud-only). If you are investing in SCCM infrastructure while also paying for Intune through M365, you are paying for two management platforms. Define a migration timeline: full Intune within 18–24 months for most modern-device environments, allowing SCCM decommissioning and associated cost savings.
Dynamics 365 uses per-user subscription licensing with a “base + attach” model. The first Dynamics 365 app a user licences is at full price (e.g., Sales Enterprise at $95/user/month). Subsequent apps for the same user are at a reduced “attach” rate (e.g., Customer Service at $20/user/month as an attach).
Commercial reality: The attach model makes additional Dynamics apps seem cheap, but the base licence is expensive, and the total cost per user across multiple apps grows quickly. Compare Dynamics 365 total cost against Salesforce, SAP, and other alternatives at each renewal. The attach discount creates perceived value but may still exceed competitive pricing for equivalent functionality.
Redress Compliance provides independent Microsoft licensing advisory for enterprises. Our specialists have negotiated 150+ Enterprise Agreements, delivering average savings of 20–35% on renewals. Fixed-fee, no vendor affiliations.
Explore Microsoft Advisory Services →Microsoft audits fewer customers than Oracle but has equal contractual rights and a growing compliance enforcement programme.
Yes. Your Enterprise Agreement and volume licensing agreements include a compliance verification clause giving Microsoft the right to audit your deployments, typically with 30 days’ notice. Microsoft may also engage third-party audit firms to conduct the review.
Commercial reality: Microsoft audits less aggressively than Oracle but is increasing compliance enforcement, particularly for SQL Server, Windows Server, and Microsoft 365 under-deployment. Audit triggers include: declining EA spend, competitive evaluations (Google Workspace), M&A activity, and high Azure growth without corresponding licence compliance. Conduct an internal self-assessment annually to avoid surprises.
The five most common findings: (1) Windows Server Standard over-virtualisation (more VMs than licences cover), (2) SQL Server Enterprise deployed where Standard would suffice, (3) missing CALs for on-premise servers in hybrid environments, (4) SPLA non-compliance for third-party hosting, (5) Office/Microsoft 365 deployed on unlicensed devices.
Commercial reality: Most Microsoft audit findings are caused by complexity, not intentional under-licensing. The hybrid transition from on-premise to cloud creates temporary compliance gaps that are structurally difficult to avoid. Address the five common findings proactively: audit VM-to-licence ratios, right-size SQL editions, verify CAL coverage in hybrid environments, confirm SPLA for external hosting, and reconcile M365 assignments with actual deployments.
A SAM engagement is a Microsoft-sponsored review of your licensing position, conducted by a Microsoft partner at no cost to you. Microsoft positions SAM as a “benefit” to help optimise your licensing. The output is a detailed deployment and entitlement analysis.
Commercial reality: A SAM engagement is a compliance review in helpful clothing. The SAM partner shares findings with Microsoft, which uses them to identify under-licensing and inform commercial proposals. Accept SAM engagements cautiously: conduct your own internal assessment first so you understand your position before Microsoft sees the data. If you participate, review the SAM findings before they are shared with Microsoft and challenge any inaccuracies.
Three steps: (1) Compile all licensing agreements (EA, CSP, MPSA, OEM, SPLA, and any legacy agreements). (2) Deploy a SAM tool (Microsoft MAP Toolkit is free) to inventory all Microsoft deployments across servers, desktops, and cloud. (3) Compare entitlements against deployments and identify gaps before Microsoft does.
Commercial reality: Organisations that self-assess before a Microsoft audit resolve 50–70% faster and at 30–45% lower cost. The self-assessment also reveals optimisation opportunities: shelfware, over-licensed SKUs (E5 where E3 suffices), and unused SA benefits. These savings often offset or exceed any compliance shortfall.
A formal audit is a contractual compliance verification under your agreement’s audit clause; you are obligated to participate. A SAM review is a voluntary, partner-conducted engagement positioned as optimisation advice. Both produce deployment data that Microsoft uses commercially.
Commercial reality: The practical difference is that you can decline a SAM review but not a formal audit. However, declining SAM may trigger a formal audit later. The best approach: accept SAM but engage independent advisory to review findings before sharing with Microsoft. This preserves the collaborative relationship while protecting your commercial interests.
Yes. Like Oracle, Microsoft audit findings are a starting position. You can challenge methodology, dispute counting rules, present missing entitlements, and negotiate the resolution commercially.
Commercial reality: Microsoft is generally more willing to negotiate audit resolutions than Oracle, particularly if you frame the resolution as part of a broader commercial commitment (EA renewal, Azure expansion, M365 upgrade). Resolution pricing of 30–50% below list is achievable. The key: separate the compliance resolution from any expansion discussion so the audit finding does not inflate the renewal deal.
Licence Verification is Microsoft’s formal audit process. You receive a notification letter requiring a self-audit within a specified timeframe (typically 60–90 days). You deploy inventory tools, report results, and Microsoft compares deployments against your entitlements.
Commercial reality: The self-audit requirement is actually an advantage: you control what data is collected and how it is reported. Use this window to optimise your environment before reporting. Remove unused installations, reassign licences, and consolidate deployments. Report accurately, but ensure your environment is as optimised as possible before submitting data.
The questions that determine whether your Microsoft relationship costs $3M or $1.8M per year.
Achievable discounts beyond level-based pricing: M365 E3/E5 5–20%, Azure 5–15% (MACC), SQL Server 15–30%, Windows Server 10–25%, Dynamics 365 10–20%. Discounts vary by deal size, competitive pressure, timing, and Microsoft’s strategic priorities for your account.
Commercial reality: Microsoft’s published level-based pricing is the starting point. Every EA is negotiable beyond level pricing for organisations that present: competitive alternatives (Google Workspace, AWS, Salesforce), multi-year commitment, significant Azure growth, and willingness to adopt strategic Microsoft products (Copilot, Defender, Intune). The combination of these levers achieves 10–25% beyond level-based discounts on a blended basis.
The most effective lever is a credible competitive evaluation. Google Workspace for productivity and collaboration, AWS for cloud infrastructure, and Salesforce for CRM each create specific, measurable pressure on Microsoft’s EA pricing.
Commercial reality: A documented Google Workspace evaluation achieves 10–20% deeper M365 discounts. A documented AWS evaluation achieves 5–15% better Azure MACC terms. The evaluation does not need to be your preferred outcome; it needs to be credible enough that Microsoft’s account team cannot dismiss it. A pilot deployment of Google Workspace for 200 users with preliminary migration costing is credible. A casual mention of “we’re considering Google” is not.
Yes, in most cases. Consolidating multiple agreements (EA, CSP, MPSA, standalone subscriptions) into a single EA or EA + CSP hybrid structure simplifies management, eliminates duplicate licences, and creates a larger spend base for negotiation leverage.
Commercial reality: Many organisations unknowingly pay for the same capabilities through multiple agreements: CALs through EA, M365 through CSP, and standalone subscriptions directly. The overlap typically represents 5–15% of total Microsoft spend. A consolidation audit before EA renewal identifies these duplicates and funds the transition to an optimised agreement structure.
Five proven approaches: (1) Right-size M365 SKUs (E3 for most, E5 only where needed). (2) Implement F1/F3 for frontline workers. (3) Activate Azure Hybrid Benefit for every eligible workload. (4) Reserved Instances for predictable Azure compute. (5) Remove shelfware and reassign unused licences.
Commercial reality: These five actions collectively reduce Microsoft spend by 20–35% for the average enterprise. The challenge: each requires cross-functional coordination between IT, procurement, and finance. Organisations that assign a dedicated Microsoft licensing optimisation workstream achieve savings within 60–90 days. See M365 Optimisation Guide.
Six must-negotiate terms: (1) True-down rights at each anniversary. (2) Price protection (cap increases at 0–3% for the full term). (3) Step-up rights (upgrade E3 to E5 at a fixed price during the term). (4) Azure MACC flexibility (rollover, cross-service credit). (5) Copilot trial pricing and exit rights. (6) Extended data retention on termination.
Commercial reality: Most organisations negotiate only on price and miss the structural protections that save far more over the three-year term. True-down rights alone can save $200K–$500K on a mid-size EA if your headcount decreases. Price protection prevents Microsoft from raising per-seat costs mid-term. These contractual protections are achievable in every EA, but only if you ask for them explicitly.
Treat Copilot as a separate commercial event. Do not let Microsoft bundle it into your base EA at the standard $30/user/month without independent negotiation. Demand: pilot pricing for 6–12 months, annual exit rights if ROI does not materialise, and Copilot pricing that does not affect your base M365 discount if you later reduce Copilot seats.
Commercial reality: Microsoft is under intense pressure to accelerate Copilot adoption to justify AI investments. This creates negotiation leverage: Copilot discounts of 10–25% are achievable with volume commitment, and pilot-to-production ramp terms (pay for 500 seats in Year 1, expand to 2,000 in Year 2 at the same rate) are available for organisations willing to commit to a deployment plan. Do not pay full price for a product that has not yet proven enterprise ROI.
For any EA renewal exceeding $1M, Azure commitment exceeding $500K, or Microsoft audit, independent advisory typically generates 5–20× ROI. Advisory fees of $30K–$100K routinely produce savings of $300K–$2M+ through SKU optimisation, benchmark-informed negotiation, and structural protections.
Commercial reality: Microsoft’s own Licensing Solution Providers (LSPs) and Cloud Solution Providers (CSPs) earn margin on your Microsoft spend. Their incentive is to maximise your commitment, not minimise your cost. Independent advisors with no Microsoft partnership or referral revenue are the only source of commercially aligned guidance. The cost of advisory is typically recovered within the first negotiation improvement. Book a confidential consultation to start.
Our Microsoft practice advises on EA renewals, M365 optimisation, Azure commitment structuring, and compliance resolution. No Microsoft partnership or referral revenue. Every recommendation made purely in your commercial interest.