During a discovery call last week, an IT director mentioned almost in passing that their Microsoft 365 tenant carried 4,500 licenses. Then came the kicker: they didn't have anywhere near that many people. Staff who left years ago were still in the system, and nobody could say why the count was that high in the first place.
If you've never reconciled your Microsoft license count against your real headcount, there's a decent chance you're in the same boat. It's one of the most common and least noticed ways organizations overspend on Microsoft.
How license bloat happens
Licenses drift upward over time. Someone leaves and their account stays active. A department grows, licenses get added, and nobody trims them back when it shrinks. Accounts get created for testing or one-off projects and never cleaned up. If a provider isn't actively managing the count against a real source of truth, the number just climbs.
The fix isn't complicated, but it does require a source of truth. In this case, that meant the organization's student records system and current staff roster. You compare your active-people list against your assigned licenses, remove what's stale, and match license types to what each person needs.
Reconcile your Microsoft 365 license count against your actual active users at least once a year. Removing stale accounts cuts cost and shrinks the number of doors an attacker could walk through.
Education licensing has its own rules
This particular client is a school district, and education licensing works differently from standard commercial licensing. Microsoft offers education-specific plans for students and for faculty and staff, and the mix you need depends on how many of each you have. In this case the real numbers were roughly 2,400 students and around 450 faculty, not the 4,500 sitting in the tenant.
Getting the student-to-faculty split right, and picking the appropriate education plan for each group, is where the real savings and the correct feature coverage come from. It's worth confirming the specifics with a partner who works in education licensing, because the plan names and eligibility rules change over time.
There's also a Cloud Solution Provider angle
The client didn't want to buy licenses directly from Microsoft and manage them alone. That's a common preference, and it's exactly what the Cloud Solution Provider (CSP) model is for. Through CSP, a partner handles the licensing on your behalf, so you have one point of contact for adding, removing, and adjusting licenses instead of doing it all yourself in the admin portal.
One important note for organizations with strict compliance needs: certain government cloud environments, like Microsoft 365 Government Community Cloud High (GCC High), have their own rules and can't always be resold the same way as commercial or education licensing. If part of your environment lives there, it's worth confirming what a partner can and can't take over.
Worth a look
If you're not sure how many Microsoft licenses you're paying for versus how many you use, that's a quick thing to check and often a quick win. We're glad to help you reconcile your counts, sort out the right plan mix, and figure out whether the CSP model makes sense for you. You'll leave with a clearer picture of what you're spending.