Microsoft License Usage Audit Guide. Find your savings.

A Microsoft license usage audit is the single highest ROI activity in any EA preparation. Customers who run a disciplined audit 12 to 18 months before EA renewal consistently find 12 to 28 percent of assigned licenses that are inactive, over assigned, or under utilized. On a $5M annual Microsoft estate that is $600K to $1.4M of recoverable spend. This guide sets out the step by step audit framework across Microsoft 365, Azure, Dynamics 365, Power Platform, and Server licensing, the specific reports and admin centers to pull from, the reclamation playbook for inactive licenses, the true down mechanics at EA renewal, and the 11 move buyer side playbook that converts audit findings into commercial outcomes. Read the related Microsoft services practice, the Microsoft knowledge hub, and the Microsoft EA renewal playbook.

The 5 anchor audit framework

A disciplined Microsoft license audit runs across 5 anchors.

1. M365 utilization. Sourced from the Microsoft 365 admin center, Microsoft Entra ID sign in logs, and the Microsoft Graph Reports API.
2. Azure utilization. Sourced from Azure Cost Management, Azure Advisor recommendations, and Reserved Instance utilization reports.
3. Dynamics 365 utilization. Sourced from the Dynamics 365 admin center and Microsoft Lifecycle Services.
4. Server licensing. Sourced from System Center Configuration Manager, CMDB inventory, and Microsoft Volume Licensing Center entitlement reports.
5. License reclamation. Where the audit findings translate into specific user license deactivations, SKU downgrades, and EA renewal true down targets.

The M365 utilization audit

The M365 utilization audit has 3 specific moves.

1. Pull sign in activity from Microsoft Entra ID for the last 90 days. Users with no sign in activity in 60 or 90 day windows are reclamation candidates.
2. Pull product usage reports from the Microsoft 365 admin center. Reports cover Teams, Exchange Online, SharePoint Online, OneDrive for Business, and the Office desktop apps. Users licensed for M365 E5 but only consuming Exchange and Office are over assigned and should downgrade to M365 E3 or even Office 365 E3.
3. Audit the M365 E5 advanced feature utilization. The E5 SKU includes Defender for Office 365 Plan 2, Defender for Endpoint Plan 2, Defender for Cloud Apps, Purview Information Protection and Governance, Power BI Pro, Teams Phone, and Audio Conferencing. Many enterprises license E5 across the broad user base but only configure half the E5 features. The unused features are recoverable as downgrade to E3 plus targeted add ons.

Read the related Microsoft 365 E5 versus E3 comparison.

The Azure utilization audit

Azure utilization audit has 4 moves.

1. Run Azure Advisor for the full subscription portfolio. Advisor identifies underutilized VMs, unattached disks, idle public IPs, and oversized SKUs against actual consumption.
2. Pull Reserved Instance utilization reports. RIs purchased against forecast consumption that did not materialize represent immediate refund or exchange opportunity within the 30 day exchange window.
3. Audit Azure Hybrid Benefit application. AHB is enabled per VM and per database server, and many enterprises with eligible Windows Server and SQL Server licenses fail to enable AHB across the eligible Azure deployment. The miss can run 20 to 40 percent on Azure compute cost.
4. Right size auto scaling and scheduled shutdown for non production environments. Dev, test, and UAT environments running 24 by 7 typically have 60 to 65 percent recoverable cost through scheduled pause outside business hours.

Read the related Microsoft Azure cost optimization 2026.

The Dynamics 365 utilization audit

Dynamics 365 audit has 3 moves.

1. Pull user license activity reports from the Dynamics 365 admin center. Inactive Dynamics users at the 60 day window typically run 15 to 35 percent of assigned licenses, particularly on Sales Enterprise where users churn and licenses do not get deactivated.
2. Audit attach license utilization against base license assignment. Microsoft sells Dynamics 365 as a base plus attach model, where users with a base license (Sales Enterprise at $105) can add other applications at attach pricing ($20 to $30 per user per month). Many enterprises pay full base license for users who could be attach licensed under another user\'s base.
3. Audit module utilization within each user\'s license. Dynamics 365 Customer Engagement Plan covered multiple modules; many enterprises now pay per module without consolidating users onto the right base plus attach structure.

Read the related Microsoft Dynamics 365 licensing guide.

Microsoft Server licensing audit

Server licensing audit covers Windows Server, SQL Server, System Center, Exchange Server, SharePoint Server, and Skype for Business Server. The audit has 4 moves.

1. Inventory deployed Windows Server VMs against entitlement. Compare against Software Assurance status and Azure Hybrid Benefit eligibility.
2. Audit SQL Server edition deployment. SQL Server Enterprise Edition at $14,256 per core list is often deployed where Standard Edition at $3,717 per core would meet workload requirements.
3. Audit System Center deployment against management need. Compare deployed components against monitoring and configuration scope.
4. Reconcile Server CAL counts against actual user and device population. CAL over assignment is one of the most common audit findings on legacy Microsoft estates.

The license reclamation playbook

License reclamation translates audit findings into recovered spend. The playbook has 5 stages.

1. Inventory inactive licenses by category. Active versus inactive cutoff at 60 days no sign in for M365, 90 days no sign in for Dynamics 365, 30 days no activity for Visual Studio Subscriptions.
2. Notify license holders before deactivation. Standard 14 day notice period with re activation process documented.
3. Deactivate via PowerShell scripts or admin center bulk operations. Document deactivation date for compliance.
4. Hold reclaimed licenses in inventory rather than canceling immediately. The reclaimed licenses become buffer against True Up requirements and provide flexibility for new hire onboarding.
5. At EA renewal, true down the contract baseline to the reconciled active user count. Not the historical assigned count.

The EA renewal true down framework

Microsoft EA contracts have True Up at year 1 and year 2 (adds licenses based on deployment growth), and True Down only at year 3 renewal (reduces licenses based on reduced need). The audit findings produced 12 to 18 months ahead of renewal feed directly into the renewal true down target. A customer with 10,000 assigned M365 E5 licenses, audit findings of 22 percent inactive (2,200 users), realistically true downs to 8,200 active plus 500 buffer at renewal, capturing $1.66M annual recovery against the prior baseline. The true down conversation requires preparation and benchmarked data; Microsoft account teams resist downward revisions by default. Read the related Microsoft True Up cost management and the Microsoft Unified support EA alignment.

11 move buyer side audit playbook

1. Start the audit 12 to 18 months before EA renewal. The data has to mature, the reclamation has to happen, and the true down conversation has to be prepared.
2. Pull sign in activity from Microsoft Entra ID for the full M365 user base. 90 day window is the standard inactivity threshold.
3. Audit M365 E5 feature utilization, not just E5 assignment. Half the E5 features are commonly unused even when E5 is assigned.
4. Run Azure Advisor across the full subscription portfolio. Quarterly cadence captures idle resources before they accumulate.
5. Audit Reserved Instance utilization quarterly. The 30 day exchange window captures misallocated RIs before commitment becomes locked.
6. Enable Azure Hybrid Benefit everywhere it qualifies. AHB applies per VM and per database server; missed AHB is missed 20 to 40 percent discount.
7. Schedule non production Azure shutdown outside business hours. 60 to 65 percent recoverable on dev, test, and UAT.
8. Audit Dynamics 365 attach license assignment. Base plus attach structure is the largest single Dynamics 365 audit finding.
9. Document the reclamation process with notification and reactivation paths. The process matters for compliance and for stakeholder buy in.
10. True down at EA renewal, not at True Up anniversaries. EA structurally allows true down only at renewal. Audit findings produced ahead of renewal directly feed the true down target.
11. Maintain quarterly audit cadence after the renewal. Continuous audit discipline prevents license drift accumulating during the term and positions for the next renewal cycle.

How we engage

• Microsoft license audit engagement. 6 to 8 week deliverable covering M365, Azure, Dynamics 365, Power Platform, and Server licensing. Output includes named reclamation candidates and EA renewal true down targets. Microsoft Practice.
• Microsoft EA renewal program. 12 month managed sequence integrating audit findings into renewal negotiation. Renewal Program.
• Vendor Shield for Microsoft. Continuous advisory including quarterly license audit cadence. Vendor Shield.
• Microsoft 365 License Optimizer. Self service tool that sizes the M365 stack against active user population. License Optimizer.