Microsoft Licensing Optimisation Assessment
We analyse your Microsoft licensing across all three models — Per User, Per Device, Per Core — and identify the optimal metric, the right SKU mix, and the savings available at your next EA renewal.
1. The Architecture: Why Three Models Exist
Microsoft's licensing architecture is the product of three decades of adaptation. Each model was created to monetise a different era of computing — and all three persist because enterprises still operate across all three eras simultaneously.
Per Device was the original model, born in the 1990s when computing meant one person sitting at one desktop PC. You bought a licence for the machine, and whoever sat at that machine was covered. It was simple, intuitive, and perfectly suited to a world where hardware was expensive and people didn't move between devices. Per Device licensing still governs products like Windows Desktop OS (Windows 11 Pro/Enterprise), certain Microsoft 365 Apps deployments, and Office LTSC for shared machines.
Per User emerged as workers became mobile — using a desktop at the office, a laptop at home, a tablet on the road, and a phone everywhere. Licensing every device separately was prohibitively expensive and operationally unmanageable. Per User licensing solved this: one licence per person, entitling them to use the software on any number of their devices. This model now dominates Microsoft 365 (E3, E5, F1, F3), Dynamics 365, Power Platform, and the entire cloud subscription portfolio.
Per Core was designed for the data centre, where the relevant question is not "who's using it?" or "what device runs it?" but "how much compute infrastructure hosts it?" Windows Server and SQL Server are licensed by the number of processor cores in the physical server — a model that reflects data centre economics but creates extraordinary complexity in virtualised and hybrid cloud environments. See our Microsoft Licensing Metrics guide for the high-level framework.
2. Per User Licensing: The Cloud-Era Metric
Per User licensing has become Microsoft's preferred model — not because it's always cheapest for the customer, but because it generates the most predictable recurring revenue for Microsoft and aligns with their strategic push toward cloud subscriptions.
How It Works
One licence per person. The user is entitled to install and use the licensed software (or access the cloud service) on any number of their personal devices — typically up to five PCs/Macs, five tablets, and five smartphones for Microsoft 365 subscriptions. The licence follows the person, not the machine. If a user leaves the organisation, the licence can be reassigned to another user (subject to reassignment rules — typically a 90-day minimum assignment period). Learn more about independent Microsoft advisory services.
Products Licensed Per User
Microsoft 365 (E3, E5, F1, F3, Business Premium/Standard/Basic): The core productivity suite — Word, Excel, PowerPoint, Outlook, Teams, SharePoint, OneDrive, Exchange Online — licensed as a per-user monthly subscription. The E3 vs E5 vs F3 decision is one of the highest-impact licensing choices in any Microsoft estate. E5 costs roughly double E3, and most organisations have a significant population of users who don't need the E5 security and compliance features — paying for E5 across the board when 60% of users could run on E3 or F3 is one of the most common and costly licensing errors.
Dynamics 365: Each Dynamics module (Sales, Customer Service, Finance, Supply Chain Management, Human Resources) is licensed per user per month, with different user types: full users (complete module access), team members (limited read/write access), and self-service users. The pricing varies dramatically by module and user type — a Dynamics 365 Finance full user is significantly more expensive than a Customer Service team member. See our Dynamics 365 negotiation playbook for pricing strategies.
Power Platform (Power BI Pro, Power Apps Per User, Power Automate): Licensed per user per month, though Power Platform licensing also offers per-app and per-flow alternatives that can be cheaper for specific deployment patterns.
Microsoft Copilot: The AI assistant layered on top of Microsoft 365 is licensed per user at a significant premium — $30/user/month on top of the M365 E3/E5 subscription. For guidance on negotiating Copilot licensing and assessing Copilot ROI, see our dedicated guides.
The Per User Traps
Over-provisioning by edition: Assigning E5 to users who need E3 functionality. The delta is roughly $20–$25/user/month — multiplied across thousands of users, this is a six- or seven-figure annual cost. Ghost licences: Paying for users who have left the organisation, are on extended leave, or have duplicate accounts. In our EA optimisation engagements, we consistently find 8–15% of Per User licences assigned to inactive or departed users. Frontline worker over-licensing: Giving full E3/E5 licences to employees who only need email and basic document access — the F1/F3 SKU at $2.25–$8/user/month serves this population at a fraction of the E3/E5 cost. Use our Microsoft 365 Licence Optimisation Calculator to identify where your SKU assignments are mismatched.
Scenario: The E5 Blanket
A professional services firm with 12,000 employees deployed Microsoft 365 E5 across the entire organisation — a $5.04M annual subscription. Our analysis found that 3,200 employees (primarily administrative and support staff) used only email, Teams, and basic Office apps — functionality fully covered by E3. Another 1,800 frontline workers (facilities, mailroom, reception) needed only Teams and email — covered by F3. Rebalancing the SKU mix: 7,000 × E5 + 3,200 × E3 + 1,800 × F3 = $3.38M annually. Annual savings: $1.66M — a 33% reduction from simply matching the SKU to the user's actual needs.
3. Per Device Licensing: The Legacy That Persists
Per Device licensing is the oldest Microsoft model — and it remains the right choice in specific scenarios that are frequently overlooked because the industry's attention has shifted to Per User.
How It Works
One licence per device, regardless of how many users access that device. The licence is assigned to the physical machine (PC, tablet, thin client, kiosk, or workstation). Any number of users can access the licensed software on that device without needing individual licences. The device licence cannot be reassigned to another device for 90 days (to prevent "licence floating"). Learn more about Microsoft EA negotiation guide.
Products Licensed Per Device
Windows Desktop Operating System: Windows 11 Pro is sold with new hardware (OEM) or as a standalone Per Device licence. Windows Enterprise (the upgrade from Pro, required for certain management features, DirectAccess, AppLocker, and advanced security) is licensed Per Device through Volume Licensing or as a Per User subscription through Microsoft 365. Microsoft 365 Apps for Enterprise: Can be licensed either Per User (through M365 E3/E5 subscription) or Per Device (for shared machines where multiple users access the same workstation). Windows Server CALs: Client Access Licences for Windows Server can be purchased Per Device or Per User — the choice affects how you count and manage compliance.
Where Per Device Still Wins
Shared workstations: Factory floors, hospital nursing stations, call centres, retail POS terminals, and reception desks where multiple users share the same machine throughout the day. If 50 users share 10 machines, Per Device licensing requires 10 licences; Per User requires 50. Kiosks and digital signage: Devices with no named user — nobody "logs in" with personal credentials. Per User licensing doesn't apply because there's no user to assign the licence to. Lab and training environments: Computer labs with 200 machines used by rotating populations of students or trainees — Per Device is significantly cheaper than licensing every potential user. Dedicated single-user desktops: In environments where each user has exactly one device and never accesses Microsoft software from any other device, Per Device may be cheaper than Per User because you're not paying for multi-device access rights you don't need.
The Per Device Traps
Device sprawl: As organisations issue laptops, desktops, tablets, and smartphones, Per Device licensing becomes expensive because each device needs its own licence. A user with a desktop and a laptop needs two device licences — one Per User licence covers both. BYOD incompatibility: Per Device licensing requires you to licence devices you don't own (employees' personal phones and tablets) if they access Microsoft software. This is operationally impractical — Per User is the only workable model for BYOD environments. VDI complications: Virtual Desktop Infrastructure creates complex Per Device counting scenarios — see our VDI licensing playbook for the full analysis.
4. Per Core Licensing: The Data Centre Tax
Per Core licensing is Microsoft's model for server infrastructure — and it is the most complex, the most expensive, and the most frequently misconfigured of the three models. The majority of Microsoft licensing compliance gaps we identify in enterprise audits are Per Core counting errors. For the complete server licensing framework, see our Windows Server and SQL Server practical guide.
How It Works
Server products (Windows Server and SQL Server) are licensed based on the number of physical processor cores in the server hosting the software. The licence count is determined by counting every core in every populated processor socket, subject to minimums: a minimum of 8 cores per physical processor and a minimum of 16 cores per physical server. A two-socket server with two 8-core processors requires 16 core licences (2 × 8 = 16, meeting the 16-core server minimum). A single-socket server with a 4-core processor still requires 16 core licences (the server minimum overrides the actual count).
Core licences are sold in 2-packs. A server requiring 16 core licences needs 8 two-pack purchases. This seemingly minor packaging detail inflates the perceived pricing complexity and creates rounding traps — you always buy in increments of 2.
Windows Server Per Core
Windows Server comes in two editions: Standard and Datacenter. Both are licensed Per Core, but the editions differ dramatically in virtualisation rights. Standard Edition allows two virtual machines (VMs) per core licence set — meaning your 16-core licence covers the physical host plus two Windows Server VMs. Datacenter Edition provides unlimited VMs on the licensed host. The edition choice directly depends on your virtualisation density: if you run more than two Windows Server VMs per physical host, Datacenter is cheaper; if two or fewer, Standard is sufficient. Learn more about Microsoft EA renewal preparation toolkit.
This Standard vs. Datacenter decision is one of the highest-value licensing optimisations available. A host running 20 Windows Server VMs needs either 10× the Standard core licences (to cover 20 VMs at 2 per licence set) or 1× the Datacenter core licences (unlimited VMs). The cost difference can be 5–10× in favour of Datacenter for dense virtualised environments. See our Windows Server core-based licensing mechanics deep-dive and SAM professional guide for the complete methodology.
SQL Server Per Core
SQL Server licensing adds another layer of complexity. SQL Server is available in two Per Core editions: Standard (capped at 24 cores and limited features) and Enterprise (unlimited cores, full feature set including AlwaysOn Availability Groups, in-memory OLTP, and advanced analytics). The Per Core cost for SQL Server Enterprise is among the highest per-core licence fees in Microsoft's portfolio — approximately $15,123 list price per 2-core pack. A 32-core server running SQL Server Enterprise at list price costs $241,968 in licensing alone.
SQL Server also offers Server + CAL licensing as an alternative to Per Core — but only for Standard Edition. Under Server + CAL, you buy a single server licence plus a CAL for each user or device accessing the SQL Server instance. For small databases accessed by a limited number of users, Server + CAL can be dramatically cheaper than Per Core. The crossover point depends on the number of users/devices and the server core count. See our SQL Server edition strategy guide and SQL Server Licensing Calculator for the analysis.
The Per Core Traps
Virtualisation under-licensing: The most common and most expensive Per Core error. Running SQL Server Standard on a VMware host without licensing the physical cores of the host (or properly applying VM-based core counting rules) creates immediate compliance exposure. Microsoft requires licensing either the physical cores of the host or the virtual cores assigned to the VM — and the rules differ depending on the product, the edition, and whether you have Software Assurance. See our Microsoft virtualised environments guide and SQL Server virtualisation strategy.
Core count misidentification: Organisations frequently miscount cores — confusing physical cores with logical processors (hyper-threads), using socket counts instead of core counts, or failing to account for multi-chip module (MCM) processors where a single "chip" contains multiple dies with separate core counts. A server that appears to have "2 processors" may have 64, 96, or 128 physical cores depending on the CPU generation.
Need Expert Microsoft Licensing Guidance?
Redress Compliance provides independent Microsoft licensing advisory — fixed-fee, no vendor affiliations. Our specialists help enterprises optimize Microsoft costs, negotiate better terms, and ensure compliance.
Explore Microsoft Advisory Services →Minimum core floors: The 16-core server minimum catches organisations running Oracle on small servers. A 2-socket, 4-core server (8 total cores) still requires 16 core licences — doubling the actual core count. This minimum is particularly painful for SQL Server Enterprise, where each unnecessary core licence costs over $7,500.
Scenario: The SQL Server Virtualisation Disaster
A logistics company runs SQL Server Enterprise on a VMware cluster with 4 hosts, each with 2× 20-core processors (40 cores per host, 160 cores across the cluster). The SQL Server VM is allocated 8 vCPUs. The IT team purchased 8 core licences, believing they only needed to licence the vCPUs. Microsoft's position: without Software Assurance and Licence Mobility, you must licence the physical cores of the host — 40 cores. If the VM can migrate (via vMotion) between hosts, all hosts in the cluster must be licensed — 160 cores. At $15,123 per 2-core pack, the compliance gap: 80 two-core packs × $15,123 = $1.21 million. The IT team's 8-core purchase covered $60,000. The gap is over a million dollars — from a single virtualised SQL Server instance.
5. Side-by-Side: When Each Model Wins
| Scenario | Best Model | Why | Cost Indicator |
|---|---|---|---|
| Knowledge workers with multiple devices | Per User | One licence covers desktop + laptop + phone + tablet | $$$ |
| Frontline workers (email + Teams only) | Per User (F1/F3) | Low-cost SKU covers limited functionality needs | $ |
| Shared workstations (factory, hospital, call centre) | Per Device | 10 machines × many users costs less than many users × Per User | $$ |
| Kiosks and digital signage | Per Device | No named user exists to assign a Per User licence to | $ |
| Computer labs with rotating users | Per Device | 200 devices < 2,000 potential users | $$ |
| BYOD environment | Per User | Cannot practically licence employee-owned devices | $$$ |
| Dense virtual server environment (>2 VMs/host) | Per Core (Datacenter) | Unlimited VMs per host for a single core licence set | $$$$ |
| Small physical servers (1–2 VMs) | Per Core (Standard) | Standard covers 2 VMs per licence set — cheapest for low density | $$ |
| SQL Server with few users | Server + CAL | CAL-based licensing avoids the full Per Core cost | $$ |
| SQL Server with many/unlimited users | Per Core | CAL count exceeds Per Core cost at scale | $$$$ |
| Azure hybrid (on-prem + cloud) | Per Core with SA | Azure Hybrid Benefit converts on-prem licences to cloud savings | $$$ |
6. Virtualisation: Where All Three Models Get Complicated
Virtualisation introduces complexity that multiplies across all three licensing models — and is the single largest source of Microsoft audit findings. Learn more about Microsoft audits and compliance playbook.
Per Core in Virtualised Environments
Windows Server and SQL Server Per Core licensing in virtualised environments follows a specific hierarchy. Without Software Assurance: you must licence the physical cores of the host. Virtualisation does not reduce the core count. With Software Assurance: you can license individual VMs based on their virtual core count (minimum 8 cores per VM), and you gain Licence Mobility rights allowing VMs to move between hosts within a server farm without relicensing. For Windows Server in virtualisation and container environments, the rules add further nuance — Datacenter Edition is particularly valuable because it permits unlimited VMs regardless of whether they move between hosts.
The virtualisation platform matters. Hyper-V (Microsoft's own hypervisor) and VMware are both supported, but the licensing mechanics differ in how core counts are calculated and how VM mobility is treated. For the complete breakdown, see our virtualised environments guide.
Per User and Per Device in VDI
Virtual Desktop Infrastructure creates a special licensing challenge. When users access a virtual desktop running on a centralised server, the VDI session requires: a Windows Enterprise licence for the virtual desktop (either Per User via M365 E3/E5 or via Windows VDA — Virtual Desktop Access — Per Device), a Windows Server Datacenter licence for the host (Per Core), and appropriate CALs for Remote Desktop Services. The layered requirements mean a single VDI session can require three separate licence components — a complexity that catches organisations migrating from physical desktops to VDI without adjusting their licensing model. See our remote work and VDI licensing playbook for the complete architecture. For details, see our Entra ID licensing guide.
7. Hybrid Cloud and Azure: How the Models Intersect
The intersection of on-premise licensing models with Azure cloud services is where Microsoft's licensing architecture reaches its maximum complexity — and where the greatest optimisation opportunities exist.
Azure Hybrid Benefit
Azure Hybrid Benefit (AHB) allows organisations with existing Windows Server or SQL Server licences (with active Software Assurance) to apply those licences to Azure VMs — effectively eliminating the Windows or SQL Server component of the Azure VM cost. This is one of the most valuable Microsoft licensing optimisations available: AHB can reduce Azure VM costs by 40–80% for workloads running Windows Server or SQL Server. The benefit requires Per Core licences with active Software Assurance — Per Device licences don't qualify, and licences without SA aren't eligible.
The strategic implication: organisations planning Azure migration should maintain (and in some cases increase) their on-premise Per Core licence count and Software Assurance specifically to enable AHB — even if the on-premise workloads are being retired. The cost of maintaining SA for AHB eligibility is typically a fraction of the Azure savings it unlocks. See our BYOL vs Azure Licensing Calculator to model your specific scenario, and our broader Azure licensing and cost optimisation playbook for the full strategy.
CALs in Hybrid Environments
Windows Server CALs (Per User or Per Device) cover access to on-premise Windows Servers. They do not cover access to Azure-hosted Windows Servers (which are covered by the Azure subscription). However, organisations running hybrid environments — where users access both on-premise and Azure-hosted servers — need CALs for the on-premise component and Azure subscriptions for the cloud component. Over-purchasing CALs for users who have fully migrated to Azure, or under-purchasing for users who still access on-premise servers, are both common errors. Use our cloud migration licensing implications guide to plan the transition.
Azure Reserved Instances and Licensing
Azure Reserved Instances (RIs) provide discounted VM pricing in exchange for 1- or 3-year commitments. When combined with Azure Hybrid Benefit, RIs create double-stacked discounts that can reduce Azure compute costs by 60–80%. The catch: RI commitments are non-refundable, and the interaction between RI sizing, AHB eligibility, and your on-premise SA renewal timeline must be carefully coordinated. Our Azure commitments negotiation guide covers the tactical details, and our Azure spend management guide provides the ongoing governance framework.
8. Software Assurance: The Multiplier You're Probably Overpaying For
Software Assurance (SA) is Microsoft's maintenance and upgrade programme — an annual fee (typically 25–29% of the licence cost) that provides version upgrade rights, planning services, training vouchers, and critically important virtualisation rights and Azure Hybrid Benefit eligibility. SA is not mandatory — but without it, you lose rights that are essential for modern infrastructure management. Learn more about Microsoft 365 license optimization.
Where SA Delivers Genuine Value
Per Core products in virtualised environments: SA provides Licence Mobility (the right to move VMs between hosts without relicensing) and enables VM-based core counting instead of physical host counting. For SQL Server and Windows Server in VMware or Hyper-V environments, SA is essentially mandatory — the cost of licensing without SA's virtualisation benefits is 3–10× higher. Azure Hybrid Benefit: Only available with active SA. The AHB savings typically exceed the SA cost by 2–5×, making SA investment self-funding for organisations with Azure workloads. Version upgrades: SA includes rights to deploy the latest version of the licensed product. Without SA, you're locked into the version you purchased — functional but increasingly unsupported.
Where SA Is Wasted Spend
Stable, non-virtualised environments: A physical server running a single instance of Windows Server Standard that will never be virtualised, never moved to Azure, and doesn't require the latest version gains minimal value from SA. The 25–29% annual cost is paying for benefits you won't use. Products approaching replacement: Paying SA on SQL Server licences that are being migrated to Azure SQL Database within 12 months — the SA cost buys upgrade rights you'll never exercise. Over-provisioned SA: SA applied to licences that exceed your actual deployment (shelfware SA) — paying for maintenance on products nobody uses.
Our Software Assurance CIO Playbook provides the decision framework, and for SQL Server-specific SA benefits, see our dedicated analysis.
9. Seven Optimisation Strategies Across All Three Models
Strategy 1: SKU Right-Sizing (Per User)
Audit every Microsoft 365 licence assignment against actual usage. Move E5 users who don't need advanced security/compliance to E3. Move E3 users who only use email and Teams to F3. The typical enterprise can reduce Per User costs by 15–30% through SKU right-sizing alone. Use our M365 Licence Optimisation Calculator for the analysis, and review the M365 plan selection playbook for the decision framework.
📊 Free Microsoft EA Renewal Readiness Assessment
Preparing for your EA renewal? Our free assessment benchmarks your pricing, evaluates compliance, and identifies optimization opportunities.
Take the Free Assessment →Strategy 2: Shared Device Conversion (Per Device)
Identify workstations shared by multiple users and convert them from Per User to Per Device licensing where the economics favour it. A call centre with 200 shared machines used by 800 agents on rotating shifts needs 200 Per Device licences — not 800 Per User licences. The savings are 75% in this scenario.
Strategy 3: Datacenter vs Standard Edition Analysis (Per Core)
Count the Windows Server VMs per physical host across your estate. Any host running more than two VMs should be evaluated for Datacenter Edition (unlimited VMs per host). Any host running two or fewer VMs should be on Standard. Most organisations have a mix — and most are using the wrong edition on at least 20% of their hosts. See our Windows Server and SQL Server hybrid licensing playbook for the methodology. Learn more about Microsoft licensing metrics cores users devices.
Strategy 4: Azure Hybrid Benefit Maximisation
Ensure every eligible Windows Server and SQL Server Per Core licence (with SA) is applied to Azure through AHB. Many organisations have AHB-eligible licences that aren't being used — the Azure VMs are paying the full Licence Included rate when a BYOL rate is available. The savings are typically 40–80% per eligible VM. Our BYOL vs Azure Calculator identifies the opportunity.
Strategy 5: CAL Model Optimisation (Per User vs Per Device)
Windows Server and SQL Server CALs can be purchased Per User or Per Device. The optimal choice depends on the ratio of users to devices. If users outnumber devices (shared machines), Per Device CALs are cheaper. If devices outnumber users (multiple devices per person), Per User CALs are cheaper. Most organisations have never revisited this decision since the original CAL purchase — and changes in working patterns (remote work, BYOD, VDI) have shifted the economics significantly.
Strategy 6: Licence Elimination for Redundant Products
Microsoft's broad portfolio creates overlapping functionality: Power BI Pro included in M365 E5 but also purchased standalone, Exchange Online bundled with M365 but also licensed separately for specific mailboxes, SharePoint included in M365 but also licensed through legacy Per Server licences. Eliminating redundant licences — products you're paying for twice because one is included in a bundle you already own — delivers immediate savings with zero operational impact.
Strategy 7: True-Up Governance
Microsoft EA true-ups are annual reconciliations where you report (and pay for) any licences deployed beyond your contracted quantities. Poor true-up governance — adding users or servers throughout the year without tracking the licensing impact — creates budget surprises and overpayment risk. Implement a quarterly internal true-up process that tracks licence additions in real time, validates them against EA quantities, and budgets for the annual true-up well in advance. Our true-up guide and risk assessment tool provide the framework.
10. Frequently Asked Questions
For most products, yes — but the rules vary. Windows Server and SQL Server CALs can be mixed: some users licensed with Per User CALs and some devices licensed with Per Device CALs within the same environment. However, you must be consistent per entity — a specific user is either covered by a User CAL or by the Device CAL on the machine they're accessing, not both. For Microsoft 365, the Per User subscription is the primary model, but Microsoft 365 Apps can be licensed Per Device for shared machines through a separate Per Device subscription SKU. The key is that each access point must be covered by exactly one licence — either through the user's licence or the device's licence, with no gaps and no double-counting.
Microsoft counts physical cores — not logical processors, not hyper-threads, not virtual CPUs. A dual-socket server with two 16-core processors has 32 physical cores and requires 32 core licences (16 two-core packs). Hyper-threading, which doubles the logical processor count, does not affect the core licence requirement. However, the 16-core server minimum and 8-core processor minimum still apply — so a server with two 6-core processors (12 physical cores) requires 16 core licences, not 12. In virtualised environments, you can choose to licence the VM's virtual cores instead of the host's physical cores — but only with Software Assurance and subject to the 8-core VM minimum. See our core-based licensing mechanics guide for the complete rules. Learn more about licensing across Microsoft programmes.
It depends entirely on which benefits you'll actually use. SA costs 25–29% of the licence price annually — a significant investment that must be justified by specific benefits. SA is clearly worth it when: you're running virtualised Windows Server or SQL Server (Licence Mobility and VM-based counting), you're using Azure Hybrid Benefit (SA is required for AHB eligibility), or you need version upgrade rights for products you actively upgrade. SA is not worth it when: you're on stable, non-virtualised infrastructure with no Azure plans, you're not upgrading to newer versions, or you're paying SA on shelfware. Review our Software Assurance playbook for the decision framework.
Microsoft audits focus on three areas: Per Core under-licensing (SQL Server and Windows Server in virtualised environments — the highest-value finding), Per User/Per Device over-deployment (more users or devices accessing Microsoft products than licences purchased), and CAL shortfalls (insufficient Client Access Licences for Windows Server, SQL Server, or Exchange access). The most common finding is SQL Server in VMware environments where the physical cores weren't licensed. The most common Per User finding is Office installations on devices that aren't covered by either a user subscription or a device licence. Our Microsoft Audit Defence Service provides expert support, and the Audit Survival Checklist prepares your team for the process.
The EA vs CSP vs MCA decision depends on your organisation's size, purchasing pattern, and cloud strategy. Enterprise Agreement (EA) is best for organisations with 500+ users needing centralised licensing, volume discounts, and a single contract covering all Microsoft products. Cloud Solution Provider (CSP) offers monthly flexibility and works well for organisations with fluctuating user counts or those that prefer to purchase through a partner. Microsoft Customer Agreement (MCA) is Microsoft's newer framework that can replace or supplement the EA — see our MCA guide for the evolving landscape. For EA-specific guidance, see our Enterprise Agreement Guide and contract negotiation service.
For any organisation spending $2M+ annually on Microsoft licensing, independent advisory pays for itself many times over. The complexity of managing three licensing models simultaneously — across on-premise, virtualised, and cloud environments — combined with Microsoft's opaque pricing structure, SA optimisation opportunities, and Azure Hybrid Benefit mechanics — creates a surface area that most internal teams cannot fully optimise without specialist support. An independent advisor provides: licensing model optimisation (ensuring each workload uses the cheapest eligible model), SKU right-sizing (matching Microsoft 365 plans to actual usage), SA rationalisation (paying for SA only where it delivers value), EA negotiation support (pricing benchmarks, competitive leverage, and term negotiation), and audit preparedness. At Redress Compliance, Microsoft licensing is one of our core practices — our Microsoft Advisory Services cover the complete lifecycle. Visit the Microsoft Knowledge Hub for additional resources, or explore our Microsoft Assessment Tools for self-service analysis.