Microsoft License Usage Review Template:

The Microsoft license usage review is the internal audit a customer runs in the six months before a Microsoft renewal. The output is a defensible position on every paid SKU, an unpaid usage map, an over deployment map, and a negotiation pack that takes 8 to 22 percent off the renewal demand.

This guide is the template Vendor Shield clients use. Sources of truth, evidence pack, decision math, and the seven commercial levers the review unlocks. Read it alongside the Microsoft knowledge hub and the EA renewal playbook.

Most renewal surprises are visible in the usage data 90 days before the renewal date. The internal audit makes them visible to the buyer side, not just to the Microsoft account team.

Key Takeaways

What every Microsoft renewal owner needs in the internal audit

Run it six months out. The audit window opens at the start of the last contract year, not in the renewal month.
Eleven workstreams. Identity, M365 base SKUs, Copilot, Teams telephony, Power Platform, Dynamics, Azure, Defender security, Sentinel, Visual Studio, SQL Server, and Windows Server.
One evidence pack. A single PDF and spreadsheet bundle covering the deployed user count, the active user count, the assigned SKU mix, the actual usage telemetry, and the over deployment exposures.
Two sources of truth. Microsoft 365 Admin Center, plus a usage telemetry source. Both required.
Document the unpaid usage. Visio, Project, Power Apps premium, Defender for Cloud Apps E5 features deployed but not licensed. Mitigate or license before the renewal.
Quantify the inactive licenses. Inactive assigned licenses across M365 E3, E5, and Copilot frequently sit at 8 to 18 percent of the paid count.
Build the renewal pack. Right sized SKU mix, alternative bundle scenarios, and a commercial position before the Microsoft proposal lands.

Why the internal audit matters before a Microsoft renewal

The Microsoft account team has full telemetry on the customer deployment. The customer typically does not. The information asymmetry at the renewal table costs 10 to 25 percent on the EA value.

The information asymmetry

Microsoft sees every user, every workload, every paid SKU. The seller carries a clear deployment heat map into the renewal call.
The customer often sees only the order count. Without an internal usage review, procurement walks in with a price negotiation, not a position negotiation.
The Copilot expansion makes it worse. Copilot adds a per user month SKU on top of the existing M365 base. Without usage telemetry, the customer cannot price the right pilot count or the right enterprise scale.
Dynamics 365 and Power Platform add complexity. Dataverse capacity, AI Builder credits, and Power Apps premium licenses each carry separate metrics that change the renewal math.

Outcomes the audit unlocks

Right sized SKU mix. Move the right percentage of users from E5 to E3 or F3 where the workload supports it.
Documented compliance position. A signed ELP that protects against the Microsoft compliance review or formal SAM engagement.
Decommission plan. Inactive user accounts shut down before the renewal locks them in.
Copilot expansion plan. A tiered pilot to enterprise rollout based on actual usage signals, not vendor projections.
Negotiation pack. A position document procurement carries into the Microsoft renewal call.

Eleven workstreams in a complete usage review

A complete Microsoft usage review covers eleven distinct workstreams. Each carries its own data source, its own audit risk, and its own negotiation lever.

The eleven workstreams

#	Workstream	Primary data source	Common over deployment risk
1	Identity and access	Entra ID directory export	Inactive accounts holding paid SKUs
2	M365 base SKUs (E3, E5, F1, F3)	M365 Admin Center license report	E5 over assignment to users not consuming E5 workloads
3	Microsoft 365 Copilot	Copilot usage telemetry via Viva Insights	Inactive Copilot assignments after the 90 day onboarding window
4	Teams Phone and Calling Plans	Teams Admin Center usage	Inactive Teams Phone seats
5	Power Platform (Apps, Automate, BI)	Power Platform Admin Center	Power Apps premium usage on standard licenses
6	Dynamics 365 (Sales, Service, F&O)	D365 Admin Center, Lifecycle Services	Team Member SKU misuse for full user activity
7	Azure consumption	Azure Cost Management export	Reserved instance under utilization, dev/test spend on production rates
8	Defender for Cloud Apps and Defender XDR	Defender portal license report	E5 Security features deployed on E3 base estate
9	Sentinel	Log Analytics workspace ingest	Commitment tier shortfall or oversize
10	Visual Studio and GitHub	VS subscription portal, GitHub admin	Inactive VS subscriptions, GitHub seat sprawl
11	SQL Server and Windows Server	SCCM or MECM inventory export	Core under licensing, SA lapse risk, Azure Hybrid Benefit eligible cores unmapped

Workstream priority by renewal scale

Above 10,000 users. All eleven workstreams. Six week sprint with parallel work in M365, Azure, and on premises infrastructure tracks.
2,000 to 10,000 users. Nine workstreams (drop Sentinel and Visual Studio if not deployed). Four week sprint.
500 to 2,000 users. Seven workstreams (focus on M365, Copilot, Power Platform, Dynamics, Azure, Defender, on premises). Three week sprint.
Under 500 users. Five workstreams (M365 base, Copilot, Azure, Defender, on premises). Two week sprint.

Sources of truth for each workstream

Every workstream has a primary data source and at least one corroborating source. The audit defense rests on triangulation, not on a single export.

Primary sources

Microsoft 365 Admin Center. License reports, user assignment exports, active user telemetry across Exchange, SharePoint, OneDrive, Teams.
Entra ID directory. User lifecycle data, sign in activity, MFA enforcement, last successful login.
Azure Cost Management. Subscription level consumption, reservation utilization, savings plan coverage.
Power Platform Admin Center. Environment level user activity, premium connector usage, Dataverse capacity.
D365 Lifecycle Services or Admin Center. Application lifecycle, environment activity, license assignment.
Viva Insights and Copilot Dashboard. Per user Copilot activity, action counts by application, adoption percentages.
SCCM or Microsoft Endpoint Configuration Manager. On premises Windows Server, SQL Server, and SA tracked product inventory.

Corroborating sources

Single sign on logs. Active user count derived from real authentication events, not from license assignment.
VPN and conditional access logs. Inactive accounts that still hold paid SKUs but have not authenticated in 90 days.
HR system exports. Leavers, contractors, project based access patterns that drive license churn.
Internal helpdesk tickets. Real user reports of license assignment errors or duplicate accounts.

Evidence pack template

The evidence pack is the single bundle a buyer side reviewer carries into the renewal call. One PDF, one spreadsheet, one position document.

PDF: the executive summary

Cover page. Customer name, contract reference, renewal date, audit lead, audit completion date.
Estate snapshot. Total users, total assigned licenses, total active users, total paid spend year over year.
Workstream summary. One paragraph per workstream with deployed count, active count, exposure value, mitigation status.
Top five renewal risks. Ranked by financial exposure with a recommended position for each.
Position document index. Reference to the detailed evidence in the spreadsheet workbook.

Spreadsheet: the deep evidence

Sheet 1 user master. Every user, every assigned SKU, last sign in, HR status, recommended action.
Sheet 2 SKU summary. Every SKU, paid count, assigned count, active count, gap analysis.
Sheet 3 Azure consumption. Subscription level spend, reservation utilization, savings plan coverage, optimization opportunities.
Sheet 4 on premises infrastructure. Windows Server, SQL Server, Visual Studio inventory with core counts, SA status, Azure Hybrid Benefit eligibility.
Sheet 5 over deployment. Documented unpaid usage with mitigation or licensing action.
Sheet 6 position document. Renewal SKU mix, alternative bundle scenarios, commercial position.

Worked example: 6,200 user financial services customer

A regional financial services customer ran an internal license usage review nine months before the EA renewal. The Microsoft renewal proposal arrived at 12.4M USD year one. The internal audit revealed 2.1M USD of inactive licenses and 1.6M USD of over assignment to E5.

Before the internal audit

SKU	Paid count	Active count	Annual cost
M365 E5	4,800	2,950	3.46M USD
M365 E3	1,400	1,310	588K USD
M365 Copilot	1,200	340	432K USD
Teams Phone Standard	2,200	1,140	211K USD
Power BI Pro	900	620	108K USD
Total selected SKUs	10,500	6,360	4.80M USD

After the internal audit

SKU	Right sized count	Annual cost	Saving
M365 E5	2,950	2.13M USD	1.33M USD
M365 E3 (former E5)	1,850 additional	777K USD	--
M365 E3 (existing)	1,310	551K USD	37K USD
M365 Copilot	500 (post pilot)	180K USD	252K USD
Teams Phone Standard	1,140	109K USD	102K USD
Power BI Pro	620	74K USD	34K USD
Total selected SKUs	8,370	3.82M USD	980K USD

The audit also identified 410K USD of unpaid Power Apps premium usage and 280K USD of Defender for Cloud Apps features deployed on the E3 base estate. Both mitigated before the renewal.

Seven commercial levers the audit unlocks

A clean internal audit converts into seven specific commercial levers at the renewal table. Each one carries a measurable percentage of the renewal value.

The seven levers

Right sized SKU mix. Move inactive E5 users to E3 or F3 where the workload supports it. Typical saving 12 to 22 percent of the affected SKU spend.
Inactive license drop. Decommission inactive accounts before the renewal locks them in. Typical saving 6 to 14 percent of paid count.
Copilot pilot scaling. Right size the Copilot expansion to actual usage signals. Avoid a 4,800 user enterprise rollout when the pilot data supports 1,200.
Reservation and savings plan optimization. Match Azure reservation portfolio to actual consumption pattern. Typical Azure saving 8 to 14 percent.
Bundle vs unbundled compare. Some workloads price better unbundled (Teams Premium, Defender XDR add ons) and some bundle better (E5 over E3 plus add ons).
Multi year commitment lever. Trade a three year EA renewal for a measurable percentage off the year one price, plus uplift cap on years two and three.
Compliance position protection. Document the ELP in the renewal correspondence. Lock the no audit position into the contract.

What to do next

The checklist takes a Microsoft customer from the renewal date back six months and through the internal audit.

Set the renewal date and audit window. Anchor the audit start six months before the renewal anniversary.
Assign the audit lead and workstream owners. One lead, one owner per workstream, with documented data source access.
Run the eleven workstream data extracts. Or seven, depending on the renewal scale.
Triangulate the active user count. M365 Admin Center, Entra ID, HR system. Two of three to confirm an active user.
Build the evidence pack. PDF executive summary, spreadsheet workbook, position document.
Mitigate the unpaid usage. Either decommission the unpaid features or license them before the Microsoft proposal lands.
Decommission inactive licenses. Shut down the inactive assignments before the renewal date locks them in.
Build the renewal position document. Right sized SKU mix, alternative bundle scenarios, commercial position, target landing price.

Frequently asked questions

When should I start the internal usage review before a Microsoft renewal?

Six months before the renewal anniversary, or at the start of the last contract year, whichever is sooner. The review takes four to six weeks to run cleanly, plus another four to six weeks to act on the findings (decommission inactive licenses, mitigate unpaid usage, build the position document).

Starting at three months out is workable but rushed. Starting at one month out leaves the customer at the Microsoft account team's mercy.

What is the difference between assigned and active licenses?

Assigned licenses are SKUs allocated to a user account in the M365 Admin Center. Active licenses are SKUs where the user has consumed the underlying workload (signed into Exchange, opened a Teams meeting, edited a SharePoint document) in a defined window, typically the last 30 to 90 days.

The gap between assigned and active is the inactive license exposure. On a typical 5,000 user customer that gap sits at 8 to 18 percent of the assigned count. Decommissioning inactive accounts before the renewal frees that spend for redirection or saving.

How do I measure Copilot adoption for renewal sizing?

The Microsoft 365 Copilot Dashboard inside Viva Insights gives per user adoption data. Look at three signals: per user action count per week, percentage of licensed users active in any Copilot workload monthly, and the distribution of usage across Word, Excel, PowerPoint, Outlook, and Teams.

Adoption under 25 percent at 90 days post assignment typically signals an inactive Copilot license. Use the data to right size the enterprise rollout or to stagger the next assignment batch.

How does the audit handle Power Platform premium usage on standard licenses?

The Power Platform Admin Center exposes the connectors used per environment. Standard Power Apps licenses do not entitle the user to premium connectors (SQL, custom API, on premises gateway). Premium usage on a standard license is unpaid usage.

The mitigation is either to license the affected users at Power Apps per app or per user pricing, or to remove the premium connector usage. Document the decision in the evidence pack and execute before the Microsoft proposal lands.

What is the Azure Hybrid Benefit and why does it matter at the renewal?

Azure Hybrid Benefit lets a customer apply existing Windows Server and SQL Server licenses with Software Assurance to Azure virtual machines, reducing the Azure consumption charge by up to 85 percent on a comparable workload. The benefit requires active SA on the underlying licenses.

At the renewal, mapping every Azure workload to the eligible on premises license inventory unlocks the benefit. Mis mapping leaves the customer paying both the SA fee and the full Azure consumption rate. Eligibility validation is part of the on premises workstream.

How does the internal audit affect the Microsoft compliance review or SAM engagement?

A documented internal audit completed before any Microsoft compliance review or SAM engagement protects the customer in two ways. First, the customer enters the engagement with a documented ELP, not an unknown position. Second, any over deployment identified in the internal audit can be mitigated before the formal engagement starts.

The compliance team typically uses the customer's documented ELP as the starting point for the engagement, rather than imposing the Microsoft generated baseline. Document the audit completion in writing and reference it in the renewal correspondence.

How does Redress run the internal usage review?

Redress runs the internal Microsoft license usage review inside the Vendor Shield subscription and the Microsoft services practice. The output is the evidence pack PDF, the spreadsheet workbook, the position document, the unpaid usage mitigation list, and the renewal negotiation pack.

The engagement is led by Microsoft commercial professionals on the buyer side. We have run the review across 200 plus EA and MCA renewals, from 800 user mid market customers to 80,000 user multinational estates. The review is the foundation of the Microsoft Renewal Program.

How Redress engages on Microsoft usage review

Redress runs Microsoft usage review advisory inside the Vendor Shield subscription, the Microsoft services practice, the Software Spend Assessment, and the Renewal Program.

Read the related EA renewal playbook, the Copilot licensing guide, the Copilot enterprise licensing, the Microsoft knowledge hub, the Copilot cost per user, the Copilot true cost analysis, the key leverage points, the benchmarking page, the about us page, and the contact page.

Vendor Advisory

Cloud & Emerging

Programs

Assessments

Research

Knowledge Hubs

Assessment Tools

Microsoft license usage review. The internal audit, before the renewal.