The M365 License Audit Every MSP Should Run for Their Clients
If a client is using Microsoft 365, there is usually money leaking somewhere in the tenant.
Not in a dramatic way. Not in a way that triggers an alert. Just a slow drip of licenses assigned to people who do not need them, add-ons nobody remembers buying, and users sitting on the wrong plan because the tenant grew faster than the documentation did.
That is why an M365 license audit should be a standard quarterly QBR deliverable for every MSP.
It is one of the easiest ways to show value, reduce waste, and create a conversation the client can understand immediately: here is what you are paying for, here is what is actually being used, and here is what we can fix.
And if Scopable is connected to the tenant, the audit goes from a half-day spreadsheet exercise to something your team can do in minutes because the live license data is already in front of you.
What this audit is really looking for
A good M365 license audit is not just "how many seats are assigned."
It is a check for mismatch:
- assigned versus actively used
- licensed versus required
- premium versus baseline
- current plan versus actual workload
- paid add-ons versus business value
That mismatch is where waste lives.
The client usually does not see it because Microsoft 365 billing is spread across users, service accounts, add-ons, and exceptions. By the time the invoice arrives, everything looks normal. It is only when you compare usage, role, and entitlement that the bad math shows up.
The 5 most common M365 license mistakes
1. Former employees still holding paid licenses
This is the obvious one, and it still happens constantly.
Someone leaves. Their account gets disabled. Their license never gets removed. Then that seat quietly keeps billing every month.
The audit should catch:
- disabled users still assigned licenses
- duplicate user accounts for the same person
- contractors and seasonal staff kept on full licenses after their work ended
Even if the amount seems small, this is the easiest win to present because the fix is clear.
2. Users on premium plans they do not need
A lot of tenants drift upward over time.
A user starts on Business Basic, then gets moved to a premium plan for one project, then never gets moved back. Multiply that by a few dozen users and the annual waste gets real.
This is especially common when the tenant has grown by acquisition or by informal account creation. Nobody did anything wrong. The plan just never got revisited.
The audit should compare the role and workflow of each user against the license they actually need.
3. Add-ons nobody can explain
Copilot. Audio conferencing. Advanced security. Archiving. Extra storage. Defender. Teams add-ons.
A client will often buy these during a project or a vendor review, then forget they are still active months later.
That is not always waste. Sometimes the add-on is justified. But if the tenant cannot explain why it exists, it needs review.
The question is simple: does this license add business value, or did it survive because no one cleaned up the subscription list?
4. Shared mailboxes and service accounts burning expensive licenses
This is a classic MSP problem.
A shared mailbox should not be carrying a premium user license just because it was easier to make the warning go away. A service account should not be sitting on a full user seat unless there is a real dependency.
The audit should flag:
- shared resources with full user licenses
- service accounts assigned premium features they do not use
- automation accounts that should be handled differently
These are the kinds of items that get missed when billing and identity live in separate mental buckets.
5. The wrong plan for the way the client actually works
Some clients need premium security and compliance features. Others do not.
Some clients need desktop apps and device management. Others live in browser-only workflows.
If the tenant is paying for a higher tier only because "that is what we always do," the audit should surface that.
A proper review does not ask what the client bought last year. It asks what the client needs now.
How to run the audit
You do not need to overcomplicate this.
A practical audit usually follows the same pattern:
- Export the current license inventory
- Map assigned licenses to active users
- Compare license tier against actual work pattern
- Review add-ons and subscriptions separately
- Identify obvious exceptions and document why they exist
- Turn the findings into a cleanup plan
The exact tooling can vary. Microsoft 365 admin center, Entra, billing exports, PowerShell, and your PSA all have a role. The important thing is not the tool. It is that someone is comparing entitlement to reality instead of just reading the invoice.
If Scopable is connected, this is where the audit becomes much easier. The platform can pull live M365 license data, including assigned versus actively used licenses, so the review starts with the signal instead of the spreadsheet.
What to look for in the results
Do not just count waste. Classify it.
The useful buckets are:
- obvious waste: disabled users, duplicate accounts, forgotten add-ons
- probable waste: users on a plan too large for their role
- needs context: premium licenses attached to security or compliance requirements
- keep as-is: licenses that look expensive but are justified by actual use
That structure matters because it keeps the conversation from becoming a blame session.
Most clients are not trying to overspend. They are trying to stay operational. Your job is to separate accidental waste from necessary spend.
How to present the findings without creating friction
Do not open with "you are wasting money."
Open with:
- here is what we checked
- here is where the tenant is overprovisioned
- here is what can be fixed quickly
- here is what should stay in place
That tone matters. It keeps the client from feeling like they are being audited by a vendor and makes the MSP look organized instead of punitive.
A good QBR slide usually shows:
- total licenses purchased
- licenses actively used
- licenses that can be removed or downgraded
- subscriptions worth reviewing next quarter
- estimated annual savings
The output should feel like a decision memo, not a dump of raw admin data.
How to turn this into a recurring quarterly deliverable
This is the real opportunity.
Once the audit is repeatable, it stops being a one-off cleanup and becomes a standard QBR deliverable.
That means you can offer:
- quarterly M365 license review
- license cleanup and optimization
- renewal prep and plan right-sizing
- security and compliance review tied to licensing
If you want the client to take it seriously, package it as part of the account management motion, not as a side task someone does when the invoice looks weird.
That also makes the work easier to price.
You are not selling time spent staring at exports. You are selling ongoing financial hygiene for the tenant.
What to charge
There is no single right number.
The right fee depends on seat count, tenant complexity, and whether you are just reviewing or also making the changes.
A simple approach is:
- include it inside a premium QBR or vCIO package
- charge a fixed quarterly optimization fee for larger tenants
- use the first audit to identify the savings, then price the ongoing review against the value found
The first audit is usually the most valuable because it finds the backlog.
After that, the recurring work is about keeping the tenant from drifting again.
Why this matters now
Microsoft keeps changing packaging, licensing, and add-on strategy. Clients keep asking whether they need Copilot, whether they are on the right plan, and why the bill changed again.
That means the MSP that can answer licensing questions clearly is already ahead of the MSP that only reacts to invoices.
A quarterly audit gives you a clean story:
- we know what you own
- we know what is being used
- we know what can be reduced
- we know what to revisit next quarter
That is useful operationally, but it is also useful commercially. It creates a recurring conversation about value, not just support.
The short version
If you manage Microsoft 365 tenants, run this audit every quarter.
It will find waste, surface bad defaults, and give you a concrete way to show ROI.
And if you want the same review to take minutes instead of hours, connect Scopable so the license data is already live when QBR time comes around.
See how Scopable helps MSPs build faster QBRs
Read more about revenue leakage in MSP operations
