What This Process Costs Before It Saves Anything
The outcome here is straightforward: a documented plan that reassigns Microsoft 365 licenses by role, cancels redundant add-ons, and reduces monthly spend without removing any capability people actually use. Getting there takes more than one afternoon. A proper license audit requires Global Admin or at least Global Reader access to the tenant, a current billing statement, and someone who can interpret usage telemetry across workloads. Most organizations also need an up-to-date headcount file, because the admin center alone won’t tell you who left the company three months ago.
For a 50- to 200-seat tenant, the audit itself typically runs one to two weeks of elapsed time, depending on how quickly the internal team can surface billing records and HR data. Organizations with clean documentation finish faster. Those without it should expect the first few days to be spent just assembling inputs, which is time the consultant bills for regardless of what the final savings look like. That honest cost is worth weighing before deciding whether this is a DIY spreadsheet exercise or an engagement that needs outside help.
Why Overspending on M365 Licenses Is So Common
The usual assumption is that someone picked the wrong plan at the start, but that’s rarely the real problem. Most organizations chose a reasonable tier when they first deployed Microsoft 365. The waste accumulates afterward, through what amounts to license drift: employees leave, and their seats stay assigned, roles change, but license tiers don’t follow, and automatic renewals keep billing for seats nobody reviews. Over 18 to 24 months, a 100-person company can easily end up paying for 110 or 115 licenses, with a dozen of those sitting on disabled accounts or shared mailboxes that never needed a paid seat.
The per-seat math makes this worse than it sounds. An E3 license costs roughly three to four times what a Business Basic seat does, and the gap widens further at E5. When a warehouse coordinator or a part-time receptionist holds an E3 seat because that’s what was available during onboarding, the organization is paying for advanced compliance, voice, and analytics tools that person has never opened. Multiply that across a handful of mismatched seats and the annual overspend can reach thousands of dollars, quietly, with no one noticing because the invoice just looks like “Microsoft 365” on a single line.
What to Pull Together Before the Audit Starts
An Office 365 consultant needs four inputs before touching the tenant, and missing any one of them extends the engagement and weakens the output.
- The current billing statement, showing per-license SKU costs and quantities. This is the financial baseline the entire savings estimate is built against.
- The license assignment report from the Microsoft 365 admin center, which maps every assigned license to a user principal name.
- A current org chart or HR headcount file that identifies active employees, contractors, and recently departed staff.
- Any existing IT documentation on role-based software requirements, even if it’s informal. If the organization has ever written down which roles need desktop Office apps versus browser-only access, that document saves hours of interview time.
When the headcount file is stale, or the billing statement is buried in a procurement system no one has logged into since renewal, the consultant spends the first phase of the engagement doing data archaeology instead of analysis. That’s billable time that produces no savings recommendation, so it’s worth getting these four items into a shared folder before the kickoff call.
The Audit Itself, Step by Step
Once the inputs are assembled, the audit follows a repeatable sequence. Each step produces a discrete output that feeds the next, and skipping one weakens everything downstream.
Map Every Assigned License to an Active User
The first pass pulls the full license assignment list from the admin center and cross-references it against Active Directory accounts and the HR headcount file. The goal is to flag three categories: licenses still assigned to disabled or departed accounts, shared mailboxes holding paid seats they don’t need, and service accounts running on license tiers far above their actual function. In a typical mid-market tenant, this step alone identifies five to fifteen seats that can be reclaimed immediately. Those are licenses the organization is paying for every month with zero return, and they’re invisible until someone runs the comparison.
Check Which Features Each User Actually Uses
The Microsoft 365 usage analytics report shows which workloads each assigned seat has touched over the past 90 days. This is where the audit moves from headcount reconciliation to behavioral evidence. A user holding an E3 license who has never opened Teams, Planner, Power Automate, or any of the advanced compliance tools is, in practice, using a Business Basic workload at an E3 price. The usage report makes that gap visible and gives the consultant an evidence base for downgrade recommendations rather than assumptions about what people “probably” need.
In practice, the 90-day window matters. Shorter windows miss seasonal usage patterns, and longer windows aren’t available in the standard reports without additional configuration. Ninety days is the default, and it’s usually sufficient for a first-pass audit.
Match License Tiers to Role Clusters
With usage data in hand, the consultant groups users by job function and maps each cluster to the minimum license tier that covers their actual workload. A three-tier structure works for most organizations: Business Basic for light users who only need email and browser-based apps, Business Standard for office workers who need desktop Office applications, and E3 reserved for IT staff, compliance officers, or executive roles that genuinely use advanced security and analytics features.
This clustering is where an experienced Office 365 consultant earns the fee. The license comparison matrix across Microsoft’s SKUs is dense, and the differences between tiers aren’t always intuitive. Moving a user from E3 to Business Standard saves money, but only if that user doesn’t rely on a feature, like in-place hold or information barriers, that quietly disappears with the downgrade. The role-cluster approach forces that check at the group level rather than seat by seat, which keeps the project manageable for larger tenants.
Flag Add-Ons That Duplicate Base-Plan Features
This step requires comparing add-on invoice line items against the feature matrix of the assigned base plan, because the usage report alone won’t surface it. Organizations frequently carry paid add-ons, such as standalone Exchange Online plans, third-party email archiving subscriptions, or extra OneDrive storage, that are already included in the base license they hold. The add-on was purchased before the base plan was upgraded, or by a different department, and no one reconciled the overlap.
A standalone Exchange Online Plan 2 subscription running alongside E3 seats is a common example. E3 already includes Exchange Online Plan 2 functionality, so the standalone subscription is pure double-spend. The same pattern shows up with third-party archiving tools that duplicate the native compliance features in E3 and E5. Identifying these overlaps usually requires a line-by-line walk-through of the invoice, which is tedious but often produces some of the cleanest savings in the entire audit.
Two Forks That Change the Recommendation
A straightforward downgrade isn’t always the right move, and a good consultant flags the exceptions before finalizing the plan. Two scenarios come up regularly.
If the organization is approaching a regulatory requirement that demands audit log retention beyond 90 days, eDiscovery capabilities, or advanced data loss prevention, those features live in E3 or E5 regardless of whether anyone has used them yet. Downgrading seats to save money today and then re-upgrading in six months when the compliance mandate arrives costs more in licensing friction and project time than holding the higher tier through the transition.
An organization adding headcount fast enough that downgraded seats will need to be re-upgraded within two quarters creates churn that erodes the savings estimate. The consultant weighs projected hiring against the per-seat savings and, in some cases, recommends holding a higher tier for a defined group rather than optimizing for the current month alone. The value of the audit is in the judgment applied to these forks, not just the arithmetic of cheaper seats.
What a Finished Audit Delivers and What Happens Next
At the end of the engagement, the organization should receive four concrete deliverables: a documented license inventory showing every assigned seat and its status, a tiered reassignment plan with projected monthly savings, a list of add-ons to cancel or consolidate, and a recommended review cadence to prevent drift from recurring. That last item matters more than buyers typically expect. Without a scheduled quarterly or semiannual review, the same drift that created the overspend will rebuild itself within 12 to 18 months as new hires get default license assignments and departures go unreconciled.
The post-engagement question most organizations never ask is who owns the license roster going forward. If no one internal is accountable for reconciling licenses against headcount on a regular cycle, the audit becomes a one-time correction rather than a lasting operational improvement. This is where a managed services relationship changes the math. When license management is folded into ongoing IT operations, the review happens as part of routine tenant administration rather than as a separate project that has to be re-scoped and re-purchased every time drift accumulates. Agility Networks, a Chicago-area managed services provider operating since 1996, handles this kind of recurring Microsoft 365 administration as part of its managed IT engagements rather than as a standalone consulting project.
How to Vet the Office 365 Consultant Before Handing Over Tenant Access
A certification badge on a proposal doesn’t prove current standing. According to the Nigel Frank Microsoft Careers and Hiring Guide, 75% of Microsoft 365 Consultants surveyed reported holding a certification, but only 46% of those had renewed to maintain active Microsoft Certified status, a sharp drop from 73% in the prior survey. The guide notes that M365 consultant responses were limited in that study, so the figures are indicative rather than definitive, but the pattern is worth taking seriously before granting Global Admin access to someone whose credentials may have lapsed.
Three questions are worth asking before the engagement starts. Does the consultant hold an active Microsoft certification, not just a historical one? Have they performed license audits specifically, or is their experience limited to deployments and migrations? Do they have a documented process for knowledge transfer so the organization isn’t dependent on re-engagement for every future change? An Office 365 consultant who can answer all three with specifics is a stronger bet than one who leads with a partner badge and a generic capabilities deck.
When an MSP Handles This Instead of a One-Time Consultant
A project-based consultant makes sense when the organization has stable internal IT staff and just needs a corrective pass on licensing. The audit runs, the recommendations get implemented, and someone internal takes ownership of the roster going forward.
An ongoing managed services relationship makes more sense when no one internal owns the license roster, when the tenant is also being managed for security and business continuity, and when the organization wants the audit to become a recurring process rather than a one-time event. In that model, license optimization is one piece of broader tenant administration, not a separate line item that has to be re-scoped every 18 months. Agility Networks provides this kind of ongoing Microsoft-centered IT management for small and mid-sized businesses in the Chicago area. If recurring license drift is the problem you keep solving, a managed services partner may be the more practical fix. Reach out to get in touch and see whether the fit is there.
TLDR
License overspend usually comes from drift rather than a bad initial plan, meaning departed employees keep seats, roles change without license tiers following, and renewals bill for unreviewed seats. Before an audit starts, a consultant needs a current billing statement, the license assignment report, an HR headcount file, and any role-based software documentation, since missing inputs turn the engagement into data gathering instead of analysis. The audit itself maps assigned licenses to active users, checks 90-day usage data per seat, clusters roles into tiers like Business Basic, Business Standard, and E3, and flags add-ons that duplicate features already in the base plan. Two exceptions can override a straightforward downgrade: upcoming compliance requirements needing E3/E5 features, or fast headcount growth that would force re-upgrading soon. A finished audit delivers a license inventory, a reassignment plan with projected savings, an add-on cancellation list, and a recommended review cadence, since without ongoing ownership, drift rebuilds within 12 to 18 months. Vetting a consultant should include checking active certification status, prior audit-specific experience, and a knowledge transfer process.