Licence Utilisation Audit: Where Most Savings Hide
The single most consistent source of Microsoft overspend is unused or underused licences. In every Microsoft estate we assess — across hundreds of enterprise engagements — we find a meaningful proportion of licences provisioned for users who no longer require them, never activated them, or are using only a fraction of the capability for which they're paying.
The starting point is a utilisation pull from Microsoft 365 Admin Center or the Microsoft Graph API. This data shows login frequency, active application use by product, and storage consumption. The key metrics to examine are: active users in the last 30 days versus licensed users; active use of E5-exclusive features (Phone System, advanced compliance, Power BI Pro, advanced security analytics); and licence assignments to shared mailboxes, service accounts, or terminated employees still in the directory.
Our standard Microsoft utilisation assessment finds an average of 22% of enterprise M365 licences are assigned to accounts with less than 10 active days in the prior 30-day period — representing immediate right-sizing or reclamation opportunity.
The utilisation data is the foundation for every other cost reduction conversation. Microsoft's account team will use this data too — but they will frame it in terms of adoption improvement rather than licence reduction. Your frame should be commercial: unused licences represent overpayment for capability you are not consuming.
Reclaiming unused licences in-year typically requires a contractual mechanism. Under a standard Enterprise Agreement, licence counts are set at the start of each annual period and adjusted upward at the anniversary true-up. Downward adjustments mid-term require negotiation — but they are achievable, particularly when the unused licences represent a documented, material proportion of the estate.
Tier Right-Sizing: E5 vs E3 vs F3
Microsoft's licence tier structure creates substantial pricing differentiation between user types. The gap between E5 (approximately $57/user/month at list) and F3 (approximately $8/user/month) is enormous — and most enterprise deployments contain a significant proportion of users who do not require E3 or E5 functionality to perform their role effectively.
| Licence Tier | Approx. List Price | Best Fit User Profile | Key Features |
|---|---|---|---|
| M365 E5 | ~$57/user/month | Security, compliance, executive, finance, legal roles | Advanced compliance, Phone System, Power BI Pro, Defender P2, Purview |
| M365 E3 | ~$36/user/month | General information workers | Full Office apps, Teams, SharePoint, Exchange, Intune, Entra ID P1 |
| M365 F3 | ~$8/user/month | Frontline workers, shift-based staff, manufacturing floor | Teams (no desktop), web Office apps, SharePoint, limited Exchange |
| M365 F1 | ~$2.25/user/month | Kiosk workers, very limited needs | Teams (limited), SharePoint read, no email |
The right-sizing analysis requires mapping your user population — by role, department, and actual application utilisation data — to the appropriate licence tier. Frontline workers in manufacturing, retail, healthcare, and logistics environments frequently hold E3 licences despite having no business need for desktop Office applications, Intune MDM, or advanced identity features. Migrating these users to F3 reduces per-user cost by approximately 78% without operational disruption.
For E5 users, the right-sizing question is whether the E5-exclusive features are actively deployed and used. If your organisation purchased E5 for the security bundle but uses a third-party SIEM, CASB, or endpoint detection platform — or if Phone System was purchased but Teams calling was never deployed — the premium over E3 is difficult to justify on utilisation grounds alone.
Azure Cost Optimisation
Azure environments accumulate cost inefficiency faster than any other Microsoft product line. The combination of self-service provisioning, dev/test sprawl, forgotten pilot environments, and pay-as-you-go pricing creates a persistent over-run versus optimal cost. A structured Azure optimisation engagement typically finds 20–35% cost reduction opportunity within the first 60-day assessment.
Reserved Instances and Savings Plans
The most impactful Azure cost lever for stable, predictable workloads is Reserved Instance (RI) commitment. One-year RI commitments for virtual machines deliver approximately 40% cost reduction versus pay-as-you-go; three-year commitments save approximately 60%. Azure Savings Plans extend similar discounts to compute broadly, without tying to specific VM SKUs or regions — appropriate for workloads that require flexibility in resource type or region while maintaining stable overall consumption levels.
Most enterprise Azure deployments have a core of stable infrastructure — production databases, always-on application servers, persistent security workloads — that should be 100% covered by RI or Savings Plan commitments. Identifying the gap between current RI coverage and the stable-workload baseline is the first Azure cost action. Microsoft's Cost Management tooling provides the data; interpreting it correctly requires understanding which workloads are genuinely stable versus which appear stable but fluctuate in practice.
Azure Hybrid Benefit
Azure Hybrid Benefit (AHB) allows organisations to apply existing on-premises Windows Server and SQL Server licences with active Software Assurance to Azure VMs, eliminating the Windows and SQL licence cost embedded in Azure VM pricing. For SQL Server Standard workloads, AHB reduces Azure VM costs by approximately 36%. For SQL Server Enterprise, savings reach 75–85% of the licence component of the VM cost. AHB activation requires Software Assurance coverage — which most EA customers already hold — but many organisations fail to activate it consistently across their Azure estate.
Right-Sizing and Zombie Resource Elimination
Azure Advisor provides automated recommendations for VM right-sizing based on actual CPU and memory utilisation. Organisations that have grown Azure organically — provisioning new resources without retiring old ones — typically find 15–25% of compute spend on over-provisioned VMs that could be resized without performance impact. Zombie resources — storage accounts, unattached managed disks, unused public IPs, orphaned snapshots, and idle load balancers — typically represent 3–8% of Azure spend and can be eliminated immediately with no operational consequence.
Eliminating Duplicate Subscriptions
Enterprise Microsoft deployments frequently pay for the same capability twice: once through the Microsoft 365 bundle and again through a separate SaaS subscription that predated the bundle expansion. Common duplication patterns we find in enterprise Microsoft estates include:
Third-party endpoint security versus Microsoft Defender: Organisations that purchased Defender for Endpoint P2 (included in E5) while retaining a legacy CrowdStrike, SentinelOne, or Symantec deployment. The Microsoft Defender suite has reached maturity in most use cases; retaining both is rarely justified on capability grounds and adds 20–40% to the organisation's security tool cost.
Third-party video conferencing versus Teams: Organisations running both Teams and Zoom or Webex enterprise licences across overlapping user populations. The TCO of maintaining two conferencing platforms — licence cost, support overhead, meeting room hardware duplication — consistently exceeds any functional benefit of the dual deployment.
Third-party project management versus Microsoft Project/Planner: Organisations with Microsoft Project licences (either standalone or included in bundle add-ons) alongside Smartsheet, Asana, or Monday.com enterprise deployments. Rationalising project management tooling to the Microsoft stack where capability is sufficient eliminates a typically significant per-user cost.
Identifying duplication requires cross-referencing your Microsoft product entitlements with your broader SaaS portfolio. Our SaaS contract optimisation practice routinely identifies £300K–£2M in annual duplication savings in enterprise Microsoft environments.
EA Renegotiation Tactics
The Enterprise Agreement is the structural commercial relationship that governs Microsoft pricing for most large organisations. EA pricing is negotiated at the start of the 3-year term — but for most organisations, the initial negotiation does not extract the full discount available. EA renewals represent the primary opportunity to reset pricing, but mid-term commercial events can also create negotiation moments.
The core EA negotiation leverage points are: utilisation data showing significant underuse (which supports a right-sizing claim at renewal); competitive alternatives to specific Microsoft products (particularly for Azure, where AWS and GCP create credible alternatives for new workloads); significant new workload additions (which create a commercial event that Microsoft wants to capture and can use to reopen pricing discussions); and fiscal year timing — Microsoft's Q4 (July–September) creates account team quota pressure that translates to genuine commercial flexibility for organisations with pending decisions.
For organisations in the 1,000–5,000 seat range, a well-prepared EA renewal negotiation typically achieves 15–25% better pricing than an unmanaged renewal. For organisations above 5,000 seats, the gap between managed and unmanaged renewal outcomes is even larger — because Microsoft's commercial terms at enterprise scale include significant non-standard provisions (price lock extensions, custom escalator caps, product sunset protections) that are only available when the buyer presents a credible, documented commercial position. Read our comprehensive Microsoft EA negotiation guide for the full framework.
Copilot and AI Add-On Commercial Discipline
Microsoft Copilot for Microsoft 365 is currently priced at $30/user/month as an add-on to qualifying M365 plans. For large deployments, this represents a substantial incremental spend — $360/user/year — that requires rigorous commercial scrutiny before commitment. Microsoft's account teams are under significant pressure to grow Copilot adoption and will propose broad deployment scenarios with commercial incentives designed to accelerate adoption decisions.
The commercial discipline required around Copilot procurement includes: piloting before committing to enterprise deployment (the productivity evidence from limited pilots is the only credible basis for calculating ROI); negotiating pricing below list (Copilot pricing is more flexible than Microsoft's public positioning suggests, particularly for commitments above 1,000 users or multi-year terms); and ensuring any Copilot commitment includes clear exit provisions if adoption targets are not met — because at $30/user/month, a 2,000-user deployment that achieves poor adoption represents $720,000 per year in unrecoverable spend. See our dedicated Microsoft Copilot licensing guide for the full commercial analysis.
Ongoing Governance to Prevent Spend Creep
Microsoft spend reduction is not a one-time exercise — it requires structural governance to prevent the conditions that created overspend from recurring. The core governance mechanisms are: a monthly licence utilisation review using Microsoft 365 Admin Center reports or automated tooling; a formal off-boarding process that revokes Microsoft licences within 24 hours of employee termination or role change; an annual EA position review conducted at least 6 months before the anniversary date; and a clear approval process for new Microsoft add-on or Azure resource provisioning that includes cost accountability assignment.
Organisations that implement these governance mechanisms typically hold Microsoft spend flat through headcount growth of up to 15% — because licence reclamation from attrition and role changes absorbs the growth without net new licence additions. This structural efficiency compounds over the 3-year EA term, producing savings that dwarf any one-time renegotiation outcome.
Across our Microsoft advisory engagements, organisations with formal licence governance processes spend an average of 28% less per employee on Microsoft than comparable organisations managing Microsoft reactively — without any difference in functionality deployment.