← Back to blog

Microsoft 365 Licensing Audit: A Practical Guide for SMBs

November 21, 2026
Microsoft 365 Licensing Audit: A Practical Guide for SMBs

A Microsoft 365 licensing audit is a reconciliation: what you pay for, what each person is assigned, and what each person actually uses. Done yourself every quarter, it removes idle seats and exposes mismatches before anyone outside your company asks about them. Done with an outside technology lead, it also produces a written plan you own. We run a free technology assessment at Mindpod Technologies that starts with exactly this kind of inventory.

The word "audit" means two different things in this search. One is the internal review described above. The other is a formal vendor verification of your compliance. The steps below cover the internal review, how audit logs fit in, and what to keep on file if Microsoft ever asks.

Mindpodtech
Make Microsoft 365 Licensing Easier to Govern
Mindpod Technologies can assess your technology environment and provide a prioritized, plain-language plan you own.
Visit

TL;DR

  • An internal audit compares purchased licenses, assigned licenses and real usage. Run it at least quarterly, and monthly if staff turnover is high.
  • Microsoft's admin center already has the data you need: Billing > Licenses, Active users and usage reports covering 7 to 180 days.
  • Auditing is not on by default for Business Basic, Business Standard and Business Premium tenants. Turn it on, or you will have no log of who changed a license.
  • If a vendor verification finds unlicensed use of 5% or more, Microsoft's volume licensing terms call for reimbursing verification costs and buying at 125% of the then-current price.
  • Keep a simple evidence folder: assignment exports, a change register and approvals.

Table of Contents

What a Microsoft 365 licensing audit actually checks

A license audit reconciles three things: licenses purchased, licenses assigned to users, and the features and services those users actually touch. It has two goals. One is finding waste, such as paid seats for people who left or premium tiers nobody uses. The other is surfacing compliance gaps before a formal review does.

Microsoft's own enterprise licensing guidance is blunt on the compliance side: you must license the use of a product appropriately even when a feature is not technically enforced. Tenant-wide settings are where small companies slip. A data loss prevention policy applied broadly, or a security feature switched on for everyone, can reach users whose plan does not include it. The check that catches this is license-to-feature mapping: for each premium capability enabled in the tenant, confirm which user plans include it.

In practice, your audit answers five questions:

  1. How many seats do we own, by plan?
  2. How many are assigned, and to whom?
  3. Which assigned accounts are disabled, departed or inactive?
  4. Which people hold a more expensive plan than their work requires?
  5. Which enabled features reach people whose plan does not include them?

Step 1: Pull the license inventory

In the Microsoft 365 admin center, Billing > Licenses shows how many licenses you hold and how many are assigned or unassigned. The Active users view shows who is licensed, unlicensed or a guest. Microsoft recommends exporting reports to Excel or Power BI, or using the Graph reports API once you have thousands of users. For most SMBs, a CSV export is enough.

Where it goes wrong: the license page tells you what is assigned, not who deserves it. A spreadsheet that stops here only proves you are paying. Also check the Errors & Issues list for each product. It shows users who did not receive a license and why, for example no available seats, conflicting plans or a missing usage location. Those users are working somewhere between licensed and unlicensed, which is a compliance question too.

Step 2: Match assignments to HR reality

Export your active employee and contractor list from payroll or HR. Compare it with licensed accounts. Three groups show up almost every time:

  • Licensed accounts for people who have left.
  • Licensed shared mailboxes or service accounts that do not need a paid seat for their function.
  • Contractors still holding full plans after the project ended.

This is the cheapest win, and it needs no judgment about anyone's work. It also exposes the real cause of license drift: offboarding that is not connected to license removal. We cover the identity side of that in Entra ID governance for IT leaders.

Step 3: Check usage, not just assignment

Microsoft's usage reports show who uses each service heavily and who barely uses it and might not need a license. Reports cover the last 7, 30, 90 and 180 days and typically appear within 24 to 72 hours. They exclude perpetual license models, so an on-premises Office install will not appear.

Set a rule before you look at names. A common starting point is 30 days without sign-in for standard employees and a shorter window for contractors. Then treat the list as candidates for a conversation, not for automatic removal. Someone on parental leave, a seasonal employee or a board member who checks email twice a quarter is not waste.

The measurable outcome is simple: seats reclaimed, plans downgraded, and the monthly dollar difference. Record all three.

Step 4: Right-size plans without removing what people need

Optimization is where audits often disappoint, because the savings come from changing plans, and people notice when a feature disappears. Work in this order:

  1. Remove clearly dead seats (departed, disabled, no sign-in beyond your threshold).
  2. Identify premium-tier users who use only base features. Compare what the higher plan adds against what that person's usage reports show.
  3. Move people by role, not one at a time. Frontline staff, office staff and executives usually need three different bundles.
  4. Announce changes and set a rollback. If someone loses something they need, you can reassign the license within the day.

Then make the result stick with group-based licensing. Microsoft lets you assign licenses to security groups so that people receive and lose licenses as they join or leave the group. Note the stated limits: it does not support nested groups, and you can assign licenses to a maximum of 20 groups at a time in the admin center. For a 40-person company, that is plenty.

Our Microsoft 365 cost optimization guide for SMBs walks through a 30 to 90 day approach to the same work, and our SaaS cost optimization playbook applies the same logic to the rest of your subscriptions.

Reading the audit log: who changed a license, and when

The other common reason people search this topic is a mystery: a user lost a license, or a seat was assigned and nobody remembers why. The answer is in the unified audit log.

In the Microsoft Purview portal, open Audit, then build a search with a date range, the activity "Changed user license" and, if you know them, the users involved. Microsoft's training module notes the maximum search range is 180 days. Results show the date and time, the account that performed the action, the activity and the item modified.

Two details trip up small businesses:

Also restrict who can change licenses. If five people hold admin roles and share credentials, the log will tell you an account acted, not who. Our Entra security best practices cover separating admin accounts from daily accounts.

When a formal Microsoft audit is possible

Most SMBs will never receive a formal notice, but the mechanics are worth knowing so your records are ready. According to a law firm that defends software audits, Microsoft states that Select, Open and Enterprise Agreement customers should expect a license compliance audit at least every three years, with on-site audits starting with 30 days' written notice and often run by an independent accounting firm. Customers on other agreement types may face a different process, so read your own agreement.

Auditor reviewing software licensing records

Soft reviews, where Microsoft asks you to self-certify, are more common than hard audits. Events that tend to raise questions include sudden spikes or swings in license spend, mergers or acquisitions that create duplicate licensing, and any compliance review that turns up discrepancies.

Your agreement's terms matter. Microsoft's volume licensing language, as quoted on its own Q&A site, says you must keep records of product use, give independent auditors the information they reasonably request, and complete a self-audit when asked as an alternative to a third-party audit.

What underlicensing can cost

Those same quoted terms set out the remedy. If verification shows unlicensed use, you must order enough licenses within 30 days. If the shortfall is 5% or more, you also reimburse Microsoft's verification costs, and the additional licenses are priced at 125% of the then-current price.

A worked example: you hold 50 licenses of a plan and discover 56 people using it. That is a 12% shortfall, so the threshold is crossed. Six additional seats at 125% of list, plus audit costs, is a far worse outcome than buying six seats at the normal price after a routine internal check. Terms differ by agreement and date, so confirm the language in your own contract before relying on these figures.

Evidence to keep on file

You do not need a compliance department. You need a short, dated trail:

RecordWhat it showsHow often
License export (Billing > Licenses and Active users)Seats owned and assigned by planQuarterly
Purchase records and invoicesWhat you bought and whenOn every purchase
Change registerSeats reclaimed or downgraded, who approved, the reason, the savingsOn every change
Admin role listWho can assign licensesQuarterly
Audit log exportEvidence of who changed whatWhen a question arises

One caution from audit practitioners: Microsoft's own license statement is often the starting point of a review and can be incomplete, for instance because purchases take time to appear. Your own purchase records are what correct it.

A quarterly audit routine

  1. Export licensed users and compare to the HR list.
  2. Pull 30 and 90 day usage reports for sign-in and service activity.
  3. Flag disabled, departed and inactive accounts, and review each with the manager.
  4. Review premium plan holders against what they use.
  5. Reclaim or downgrade, log the change and the dollar savings.
  6. Confirm admin roles and that auditing is on.
  7. File the exports.

Over time the goal is to make the routine boring. Group-based licensing and offboarding tied to HR remove most of the manual work. If you also want a recovery plan for the data these licenses cover, see our Microsoft 365 backup plan.

Our view: licensing is a governance problem

Most license waste we would expect to find in a small tenant is not a purchasing mistake. It is a process gap: hiring, role changes and exits that never reach the admin center.

That is why we treat a licensing review as part of technology leadership, not a one-off cleanup. Our approach is practical: inventory first, a prioritized plain-language plan you own, then delivery. The plan names which seats to reclaim, which plans to change, who approves license changes and which evidence to keep.

A company without a full-time technology leader can still run this well. It needs a clear owner, a short routine and a record of decisions. We build those with the clients we work with, so the next audit takes an afternoon.

jaras

Get an outside read on your tenant

If you would rather not build the routine alone, our Cloud & Training work covers cloud cost optimization, and our fractional CTO engagements give you an accountable technology owner without a full-time hire. Engagement starts with a free technology assessment, and you can book a 30-minute call to begin.

Mindpodtech

FAQ

What triggers a Microsoft licensing audit?

Unusual swings in license spend, mergers or acquisitions that create duplicate licensing, and discrepancies found in a compliance review are common triggers. Some volume agreement customers should also expect a verification at least every three years, according to Microsoft's stated practice as reported by a software audit law firm. Accurate records are the best preparation.

Where do I find Microsoft 365 audit logs for license changes?

Open the Microsoft Purview portal, choose Audit, and search the activity "Changed user license" for a date range of up to 180 days. Results show who made the change and when. If you run Business Basic, Standard or Premium, confirm auditing is turned on first.

How often should I audit Microsoft 365 licenses?

Quarterly suits most small and midsize businesses. Companies with frequent hiring, seasonal staff or many contractors benefit from a monthly check on departed and inactive accounts, since that is where most waste sits.

Will optimizing licenses remove features my team needs?

Not if you change plans by role and verify usage first. Compare what each plan adds against the usage reports, move groups rather than individuals, tell people before the change, and keep the ability to reassign a license immediately.

Sources