Why Most Organisations Manage Microsoft Spend Without Visibility
Most enterprise organisations manage their Microsoft licensing relationship the same way they manage utilities: pay the invoice, renew when asked, and review the cost only when someone raises a budget concern. This approach has become increasingly expensive as Microsoft's product complexity has grown. The average enterprise now has 8–12 distinct Microsoft product families with separate licence pools, utilisation patterns, and cost drivers — none of which are visible in a single consolidated view without deliberate architecture.
The consequence is systematic overspend. Unassigned licences continue to consume budget. Azure consumption exceeds MACC commitments in some months and falls short in others, with no mid-term correction mechanism. True-up exposures accumulate invisibly until the anniversary review. Product additions during the year are never modelled against three-year commitment implications. The renewal arrives with all of these issues embedded in the baseline — and the organisation negotiates from a position of ignorance rather than intelligence.
Spend analytics is the infrastructure that converts this situation into a managed programme. This guide covers the data sources, metrics, reporting cadence, and governance framework that we implement across our client engagements — the system that turns Microsoft licensing from a reactive cost into a managed commercial asset.
ROI benchmark: Organisations with a functioning spend analytics programme identify and recover 18–28% of their Microsoft licensing spend as avoidable cost within the first 12 months. The analytics infrastructure itself costs a fraction of that recovery. The investment case is not marginal — it is structural: the question is not whether to build spend analytics but how quickly to do it before the next renewal locks in current patterns for three more years.
The Five Data Sources You Need
A complete Microsoft licensing spend analytics system requires five data inputs. Most organisations have partial access to each; the discipline is connecting them into a unified view:
1. VLSC / Microsoft 365 Admin Centre Entitlement Data
The Volume Licensing Service Centre (VLSC) holds the master entitlement record for on-premises products, Software Assurance benefits, perpetual licence keys, and EA subscription counts. The Microsoft 365 Admin Centre holds the cloud subscription entitlements — how many licences of each SKU are assigned versus purchased. These two sources together define what you are paying for. They are the supply side of the equation.
The critical metric from these sources is the licence surplus ratio: purchased licences minus assigned licences divided by purchased licences. A ratio above 10% on any individual SKU is an immediate cost reduction opportunity. On M365 products, industry benchmarks suggest that 15–20% of purchased licences are unassigned at any point in time. At £30/user/month for M365 E3 and 5,000 users, a 15% surplus is £27,000 per month in waste — £972,000 over three years.
2. M365 Usage Analytics
The Microsoft 365 Usage Reports (available in the M365 Admin Centre) provide product-level activity data for each user over 7-, 30-, 90-, and 180-day windows. This is the demand side — what users are actually consuming versus what they are licensed for. The key metrics are:
Active users per product: Users who have performed at least one product action in the reporting period. This is the fundamental utilisation metric. Below 60% active rate on any product within 30 days should trigger a review.
Features used per product: Within M365, which specific features users are consuming. This is critical for tier right-sizing — an E5 user who is using only the core E3 capabilities is a candidate for SKU downgrade.
Adoption trends: Whether utilisation is growing, stable, or declining over the 90–180 day window. Declining utilisation on a product you are expanding in the next EA is a warning signal.
3. Azure Cost Management and Billing Data
Azure consumption data requires its own analytics track. The key metrics are: total monthly consumption versus MACC commitment (the underspend/overspend position), cost by service family and resource group (identifies runaway consumption categories), Reserved Instance coverage ratio (uncovered on-demand consumption is typically 30–40% more expensive than covered), and Hybrid Benefit utilisation rate (unused AHB entitlements are a common waste item). Azure Cost Management provides native tooling for all of these — the governance discipline is ensuring the data is reviewed monthly against a defined target state.
4. Invoice and Contract Data
Your invoices and the EA price sheet are the financial ground truth. The analytics discipline here is maintaining a line-item cost model that maps each invoice line to a product category, business unit, and contract commitment — so mid-year additions can be immediately assessed for three-year cost implications, and so the renewal baseline is built from actual invoice data rather than the renewal proposal Microsoft provides.
One consistent finding in our engagements: the renewal proposal Microsoft submits is almost never the same as the actual invoice baseline. Products are repackaged, pricing basis changes, and add-ons that were separately invoiced appear in bundles. Building your own invoice-based baseline before engaging on the renewal proposal is non-negotiable for effective negotiation.
5. HR/HRIS Data
Microsoft licence counts are driven by headcount. Connecting your HRIS data to your licensing analytics creates predictive capability: planned headcount growth drives true-up forecasting; planned redundancies or restructuring create licence reduction opportunities. Organisations that manage this connection typically forecast their annual true-up within 5% accuracy — those that do not typically discover true-up exposure 30–60 days before the anniversary, when the options to mitigate are limited.
The Core Metrics Dashboard
Once the five data sources are connected, the analytics output should produce a core metrics dashboard that can be reviewed monthly at the operational level and quarterly at the commercial level. The recommended metric set:
| Metric | Source | Target State | Action Threshold |
|---|---|---|---|
| M365 licence surplus ratio | M365 Admin Centre | <5% unassigned | >10% → harvest review |
| M365 E5/E3 active ratio (30-day) | M365 Usage Reports | >85% active | <70% → SKU review |
| Azure MACC consumption vs commitment | Azure Cost Management | 95–105% of monthly target | <85% → underspend risk; >115% → overage risk |
| Reserved Instance coverage ratio | Azure Cost Management | >70% of stable workloads covered | <50% → RI purchase review |
| True-up exposure forecast | VLSC + HRIS | Within 3% of anniversary count | >10% variance → mid-term correction |
| Copilot seat utilisation | M365 Admin Centre | >80% active (30-day) | <60% → deployment review |
| SA benefit utilisation rate | VLSC benefits portal | >70% of available benefits claimed | <50% → benefit activation campaign |
| Power Platform storage usage vs entitlement | Power Platform Admin Centre | <80% of pooled capacity | >90% → overage risk assessment |
Reporting Cadence: Monthly, Quarterly, Annual
The spend analytics programme is only valuable if it produces decisions at the right frequency. The recommended three-tier cadence:
Monthly Operational Review (IT/SAM team)
Focus: waste identification and immediate action. Review the licence surplus ratio for M365 SKUs and initiate harvest processes for licences above the 10% threshold. Review Azure consumption versus MACC target and flag outlier resource groups. Review Copilot seat utilisation and identify users who have not activated. This review should take 60–90 minutes and produce a specific action list with owners and deadlines. The operational review does not require senior management involvement — it is an IT governance activity.
Quarterly Commercial Review (IT + Finance + Procurement)
Focus: financial performance and forward trajectory. Review three-month trend data for each key metric. Assess the true-up forecast against current licence counts. Review the SKU mix against the cost optimisation targets from the last renewal or mid-term review. Identify any new product additions that need three-year cost modelling. Consider whether any mid-term negotiation triggers have been met (expansion events, M&A, significant count reductions). The quarterly review typically takes half a day and should produce a written summary for the CIO and CFO.
Annual Renewal Intelligence Review (IT + Finance + Procurement + Leadership)
Focus: EA renewal preparation and strategic positioning. This is the highest-value review in the programme. It synthesises 12 months of operational and quarterly data into a renewal position: the optimised licence mix, the three-year cost model, the benchmark data, the leverage points, and the negotiation strategy. Our EA renewal preparation guide covers this in full — but the critical point is that the annual review should be running at 18–24 months before renewal, not in the 90-day window when Microsoft presents its proposal.
Est. 2016 — 500+ engagements — £2.1B managed: The organisations that achieve 30%+ cost reduction in EA renewals are not lucky — they are the ones with 24 months of spend data that gives them a negotiating position Microsoft cannot easily dismiss. Organisations that start the renewal conversation with Microsoft's proposal as the baseline are starting from a position of commercial disadvantage that data could have eliminated.
Tooling: What You Actually Need
The spend analytics stack does not require a specialist platform if the volume is managed correctly. The minimum viable tooling set for an organisation spending £1M–£5M per year on Microsoft:
Microsoft native tools: M365 Admin Centre usage reports, Azure Cost Management, Power Platform Admin Centre, and VLSC. These provide the raw data for all five required data sources. They are free and included in your licensing. The discipline is scheduling regular exports and maintaining historical data — native tools typically provide only 180 days of historical data without archiving.
Power BI: Connecting the native data sources into Power BI (included in most M365 E3 plans) creates a unified dashboard without additional tooling cost. The Microsoft 365 Usage Analytics content pack provides a starting point. Custom reports can be built to produce the core metrics table above with relatively modest Power BI effort.
Dedicated SAM platform (optional above £5M spend): At £5M+ annual Microsoft spend, a dedicated SAM platform (Snow Software, Flexera, LicenseDashboard, Certero) provides automated reconciliation, compliance alerting, and more granular discovery that the native tools cannot match. The platform ROI calculation should be: (annual overspend recovered + audit exposure prevented) vs (platform licence + implementation). For most organisations above £5M, the ROI is clearly positive. Below £5M, the native tools with structured governance often deliver equivalent business outcomes at lower cost. See our SAM tool evaluation guide for the full vendor comparison.
The data without interpretation problem: SAM tools generate data. They do not generate decisions. The most common failure mode we encounter is organisations that have invested in a SAM platform, produce beautiful dashboards, and then do nothing with the output because there is no governance owner responsible for acting on the findings. A basic analytics programme with clear ownership and a defined action cadence delivers more value than a sophisticated platform without governance. Start with ownership, then invest in tooling.
Connecting Spend Analytics to EA Negotiation
The spend analytics programme earns its commercial value when it is connected to the EA negotiation process. The connection has three dimensions:
Baseline construction: Your spend data constructs a true licence baseline — the optimised count of each SKU after harvest, right-sizing, and true-up adjustment. This baseline is typically 12–18% lower than the count Microsoft uses as the renewal starting point. Presenting your independently constructed baseline as the negotiation anchor, rather than accepting Microsoft's, is the single highest-value action in most EA renewals.
Leverage development: Spend analytics identifies the products where you are overcommitted relative to actual usage — and those products are negotiating leverage. Low Copilot adoption rates, underutilised Azure MACC, or low E5 feature utilisation all create arguments for price adjustments, count reductions, or contract restructuring that Microsoft's account team cannot easily dismiss when backed by admin centre data.
Benchmark validation: Your own utilisation data validates (or challenges) the benchmark pricing data from independent sources. If you are paying above-benchmark for a product with below-average utilisation, you have a compounded negotiating argument. For the mechanics of using benchmark data in negotiation, see our EA third-party benchmarking guide and cost benchmarking guide.
Building the Programme: Four-Step Implementation
For organisations starting from scratch, this is the recommended build sequence:
Step 1 (Month 1): Establish data access. Confirm admin access to M365 Admin Centre usage reports, Azure Cost Management, Power Platform Admin Centre, and VLSC. Export the last 180 days of available data from each source. Identify gaps where historical data is unavailable and set up automated monthly exports from this point forward.
Step 2 (Months 2–3): Build the baseline dashboard. Connect data sources in Power BI or equivalent. Produce the first version of the core metrics table. Run the first waste identification exercise — calculate the licence surplus ratio for each M365 SKU and identify the top three harvest opportunities. Quantify the annual saving from addressing each.
Step 3 (Months 4–6): Establish governance ownership. Assign a named owner for each metric category (IT for utilisation, Finance for cost, Procurement for contract intelligence). Define the monthly and quarterly review cadence. Produce the first quarterly commercial review report. Initiate the first harvest campaign for the top waste item identified in Step 2.
Step 4 (Ongoing): Connect to EA cycle. Maintain 18–24 months of rolling data. Build the renewal baseline from actual invoice and utilisation data 18 months before renewal. Commission independent benchmarking 12 months before renewal. Begin the renewal preparation programme as described in our EA multi-year roadmap.
FAQ
How long does it take to build a functional spend analytics programme?
Three to six months to establish data connections, governance ownership, and the first operational review cadence. The first material cost recoveries typically follow within 60–90 days of the first waste identification exercise. The full programme value — particularly in EA renewal positioning — accumulates over 12–24 months of consistent operation.
Who should own the Microsoft spend analytics programme?
Ownership should be split but clear: IT owns utilisation data and operational review; Finance owns cost data and budget forecasting; Procurement owns the EA contract intelligence and renewal strategy. The programme needs a single co-ordinator — typically a senior IT manager or dedicated SAM analyst — who drives the cadence across all three functions and escalates when action thresholds are breached.
What if we only have 90 days before renewal and haven't built analytics?
Commission an accelerated spend review with an independent advisor. In 90 days, an experienced advisor can construct the optimised baseline, identify the top three negotiation levers, and build the three-year cost model that creates a negotiating position — even without a pre-built internal analytics programme. It is not the ideal position to be in, but it is far better than entering the renewal with only Microsoft's proposal as the reference. Contact us at Microsoft Negotiations if you are in this position.