We’ve consulted hundreds of companies on M365 licensing strategies, and most are overpaying for Microsoft 365 by 10% to 20% or more. The waste rarely comes from one big mistake; rather, it’s a couple of different scenarios that compound. It's a license tier assigned by default instead of by role. A device management gap nobody closed. Three collaboration tools doing the same job. A security initiative that stalls because nobody realized the budget was already sitting in the licensing line item. Below are four real scenarios TrustedTech has worked through with clients: what each one cost, and what it took to fix.
We see the same patterns across audits regardless of company size or industry, because M365 licensing tends to drift the same way everywhere. It gets purchased once under time pressure, then left alone as the organization grows around it. TrustedTech is a Microsoft Direct CSP Partner holding all six Microsoft Solutions Partner designations, and we run these audits daily. The four scenarios below are what work turns up most often. If even one sounds familiar, it's worth checking whether your own M365 environment has the same blind spot.
Scenario 1: Same License Tier Across the Board
A 1,200-person company had standardized on Microsoft 365 E3, from office-based teams in HR and Sales to frontline and part-time employees. IT knew some of those users probably didn’t need E3, but they didn’t have the usage data to know who could be moved without taking away something they needed.
The licensing audit gave them that answer. Many frontline and part-time employees weren’t using desktop Office apps or the advanced security features included with E3. TrustedTech reviewed usage by role and reassigned those employees to F3, while leaving E3 in place for users who relied on its additional capabilities.
Rightsizing alone cut licensing costs by 15%, on top of an 11% reduction from switching to TrustedTech's CSP pricing. That freed-up budget went toward stronger security tooling, and IT ended up with a licensing strategy built on data instead of habit.
The first place to look is whether license tiers match how employees actually work. A licensing audit can identify users assigned E3 who aren’t using the features that justify it. For example, employees who don’t need desktop Office apps or advanced Defender and compliance capabilities may be better suited for F3. The right tier depends on the role and your compliance requirements, so use actual usage data to make that call.
Scenario 2: Acquisition Growth Outpacing Endpoint Management
One company had grown through a string of acquisitions, and IT was still working through the differences in how each business managed its devices. Some employees worked on Windows, others on iOS, and each acquisition brought another set of devices and policies into the mix. Without a common approach to device management, IT had a harder time seeing what was protected, what wasn’t, and where security gaps remained.
The fix wasn't a new tool. Microsoft Intune, already included in their existing M365 entitlements, could handle the whole problem once someone actually turned it on. That's a detail organizations miss constantly: Intune is bundled into a number of common M365 and EMS suites, so a lot of companies already own the tool that would fix their device management problem and just haven't deployed it. TrustedTech's professional services team stood up Intune to unify device management across both platforms.
The organization now manages 1,400 mobile devices with 6x faster device setup and a much stronger, unified security posture, without adding headcount. It's the same pattern behind our Senske case study, where a four-person IT team took on 1,200 employees' worth of devices and came out with better security, not worse. What surprises people most is how often the fix was already sitting in a license they'd paid for. The audit just connects the entitlement to the gap it can close.
The lesson holds beyond M&A: any organization running mixed-OS devices without a unified endpoint strategy is probably already paying for the fix. It just isn't turned on yet.
Scenario 3: Multiple Overlapping Collaboration Tools
A mid-sized organization with 1,700 employees had built up a full stack of communication tools over time: Slack, Zoom, Google Meet, Microsoft Teams, and Cisco Webex, each adopted by a different team for a different reason. The result was extensive SaaS sprawl, which resulted in inconsistent workflows, siloed conversations, both internal and external, and an IT team that knew licensing was bloated but couldn't say by how much or where.
TrustedTech surveyed which features each tool's users actually cared about, then showed how Teams, already part of their M365 licensing, covered the core capabilities driving that usage. Professional Services ran a Cloud Environment Assessment and led a consolidation plan covering adoption, policy guidance, and user enablement.
Moving to Teams allowed the company to drop licenses from four other vendors. But the biggest impact wasn’t the license savings. IT estimated it was spending about 20 hours each week supporting and administering five different platforms. Consolidating those tools gave the team roughly half of a full-time role back while also making it easier to manage security and see which tools employees were using. If you’re considering a similar move, our Slack vs. Teams comparison breaks down where Teams can replace Slack—and where it may not.
Scenario 4: Licensing Waste Blocking a Security Budget
An investment firm, an active TrustedTech customer, started planning a cybersecurity initiative that the executive team had just made a priority. During planning, IT found a gap between the budget available and what a proper security rollout would actually cost. The firm had managed its own Microsoft licensing up to that point and, like most companies that do, had drifted into an over-provisioned environment without realizing it.
TrustedTech's advisory team walked the firm through its M365 and Azure licensing, moving a number of ME3 and OE3 licenses down to OE1, where the higher tier wasn't doing anything, and consolidating other redundancies along the way. That work surfaced $33,000 in unnecessary monthly spend that could go straight back into the IT budget. The exact number here is specific to this firm's seat count and SKU mix, so treat it as one data point rather than a benchmark, but the underlying pattern, entitlements bought above what a role actually needs, shows up in nearly every self-managed licensing environment we audit.
With that budget recovered, the firm moved ahead on re-architecting its security posture, pulling in Microsoft Defender, KnowBe4, and Sophos alongside Platinum Support through TrustedTech's Partner Ecosystem. The security initiative that stalled during planning got funded, not by asking for new money, but by redirecting money the firm was already spending on licenses it didn't need.
A Quick Self-Audit: Four Questions Before Your Next Renewal
The four examples above had one thing in common: the licensing issues weren’t obvious until someone looked at how licenses and tools were actually being used. That’s why it makes sense to review your environment before renewal, while there’s still time to make changes. Start with the same four areas TrustedTech reviews with customers.
- Does your current licensing setup match how your teams actually use M365 day to day, or does it reflect decisions made years ago that nobody's revisited?
- If your workforce uses a mix of device types, do you have one unified way to manage and secure all of them?
- Are you paying for more than one tool that does the same job, just because different teams picked different tools at different times?
- And if your budget for a new security or IT initiative feels tight, have you actually confirmed that money isn't already sitting in licensing you're paying for and not using?
A "no" or "not sure" to any of those is a decent signal that an audit would pay for itself, often within the first finding.
The Takeaway
Every scenario above started the same way: a company assumed its Microsoft licensing was roughly fine because nobody had the data to say otherwise. In every case, an actual audit found real, quantifiable waste. And in every case, fixing it funded something the organization actually wanted to do next.
If your last licensing review was more than a year ago, or you've never run one, schedule a licensing consultation with TrustedTech, or read more on how licensing optimization reduces M365 costs first. We'll show you exactly where your environment stands before we recommend anything.
Microsoft 365 Cost Optimization
How to Reduce Microsoft 365 Costs by 20% or More
The Complete Playbook for Reducing M365 Spend. Everything IT leaders and procurement teams need to cut Microsoft 365 costs without cutting capability.
- License right-sizing strategies
- SKU comparison and downgrades
- CSP vs. direct pricing analysis
- Governance and audit frameworks
- Copilot and add-on cost controls
- Renewal negotiation tactics
