Why Microsoft 365 Has No Regional License Quotas — And What It's Costing You
It's 3pm on a Tuesday. Your phone buzzes.
It's the IT coordinator in Germany. Ten new hires start Monday. They need Microsoft 365 E1 licenses. Standard request, planned weeks in advance, fully budgeted.
You check the tenant. The licenses are gone.
Not expired. Not cancelled. Gone — consumed by another region that saw availability in the global pool and helped themselves. No alert. No approval. No process. Just ten employees in Stuttgart who can't start work on Monday, and a conversation you're going to have to have with their manager.
If you've never experienced this exact scenario, you haven't managed a multinational Microsoft 365 tenant long enough.
The Architecture Problem Microsoft Won't Fix
Microsoft 365 is built around a single model: one tenant, one global pool, one Admin Center. It's a clean, scalable architecture — for a company that operates as a single entity with centralised IT decision-making.
Most multinationals aren't that company.
They have subsidiaries in six countries, each with its own IT coordinator, its own headcount budget, and its own onboarding cycles. They have a Global IT team that negotiates the Enterprise Agreement and manages the pool centrally. And they have a Microsoft 365 tenant that treats every license as a shared global resource — first come, first served.
The problem isn't a bug. It's by design.
Microsoft's native tools give you:
- A global license count (how many you bought)
- A global assigned count (how many are in use)
- A global available count (the difference)
What they don't give you:
- Regional allocation (Germany has 120 E5, China has 80 E1)
- Reserved quotas (those licenses are spoken for — hands off)
- Consumption alerts (France just hit 90% of their allocation)
- An approval workflow before someone assigns a license
This isn't an oversight. A frictionless global pool maximises consumption, which aligns with Microsoft's commercial model. Every license consumed is a license that justifies the next renewal. Creating regional quotas natively would introduce friction that works against that model.
Understanding this isn't about blaming Microsoft. It's about knowing why the problem exists — and why it won't be solved from inside the platform.
The Real Cost of an Unmanaged Global Pool
Let me be specific. These aren't hypothetical numbers — they're patterns I've seen repeatedly in multinational tenants with 300 to 5,000 users.
Cost 1: Silent consumption
Region A requests 15 licenses. By the time the request is processed (email, Teams thread, manual Admin Center work), Region B has already consumed 12 of them. Region A gets 3. Region B gets away with it because there was nothing to stop them.
At €22/user/month average, 12 licenses consumed out of turn costs €3,168/year in misallocated budget. Not waste — misallocation. The licenses are used. But not where the money was budgeted.
This happens silently. No one flags it. It shows up as a budget variance in Q4 that nobody can explain.
Cost 2: Out-of-band assignments
An IT admin in Brazil — good intentions, time pressure — goes directly to the Microsoft Admin Center and assigns three E3 licenses to users who need urgent access. No request. No approval. No reservation.
Your tenant now has three licenses assigned outside any governance process. They're not linked to any budget centre. They won't appear in your monthly reconciliation until someone runs a manual export. And when they do appear, the assignment is weeks old and the approval conversation is moot.
Industry data shows that 27% of assigned M365 licenses belong to users inactive for 30 days or more, and 12% to disabled or departed accounts. Out-of-band assignments are a significant contributor to this drift — licenses assigned in urgency, never reviewed, never reclaimed.
Cost 3: SKU redundancies that nobody catches
This one is the most insidious because it requires knowing something that Microsoft's Admin Center never tells you: which licenses include which other licenses.
Microsoft 365 E5 includes Power BI Pro. Assign both to the same user and you're paying €8.80/user/month for a license that's already covered. At 50 users, that's €5,280/year. At 200 users, that's €21,120/year — in one SKU combination alone.
There are dozens of these combinations across the Microsoft licensing portfolio. Without a tool that maintains a map of SKU inclusions and checks every user's assignment against it, you won't know until someone audits manually — which means never, or once a year when it's too late to recover the cost.
Cost 4: Wrong tier, wrong user, every month
Across enterprise M365 estates, 15 to 30% of seats sit one tier above what the role actually needs.
A warehouse supervisor with Microsoft 365 E5 who uses Outlook, Teams, and occasionally Word. A frontline retail worker with E3 when F3 covers everything they need at a fraction of the cost. A contractor with a full E3 assigned for a three-month engagement that was extended indefinitely without license review.
Each of these is a recurring monthly cost with no corresponding value. And without regional visibility — knowing which users in which country have which licenses and whether those licenses match their actual usage — the wrong tier persists indefinitely.
What IT Managers Actually Do Today
Before I describe the solution, let me describe the workaround — because every IT Manager in a multinational has built one.
PowerShell exports. You write a script that queries the Graph API, exports user assignments to CSV, and loads it into Excel. You run it monthly. You colour-code the anomalies manually. It takes half a day. The data is already two weeks old when you look at it. It tells you what happened. It doesn't prevent anything.
Power BI dashboards. A step up — real-time-ish, visually useful. But Power BI shows you the problem. It doesn't give you the workflow to prevent it, the approval chain to authorise it, or the reservation to protect against it. A beautiful dashboard of a budget leak is still a budget leak.
Email and Teams threads. "Can you check if we have E1 licenses available for the new hires in Stuttgart?" Replied to three hours later. Forwarded to someone who has access. Answered the next morning. By which time the answer has changed. This is the coordination cost that nobody measures but everyone feels.
Spreadsheet-based tracking. A shared Excel that theoretically tracks allocations by country. Updated manually. Conflicting versions. Last reliable entry from three months ago.
None of these solve the problem. They document it retrospectively, at cost of significant IT time, with data that's always behind reality.
What Regional License Governance Actually Looks Like
The solution to the regional quota problem isn't complex. It's a governance layer between your Microsoft 365 tenant and the people who consume from it. It has four components:
1. Reserved quotas by country or subsidiary
Each region gets an allocation — a number of licenses per SKU that are reserved for them and protected from consumption by other regions. Germany has 120 E5. China has 80 E1. Neither can touch the other's allocation. The global pool shows what's reserved, what's assigned within each reservation, and what's genuinely available for unplanned needs.
This is the Emergency Buffer concept: a small number of licenses in each country's allocation held back for urgent cases, separate from the main reservation.
2. A monthly request cycle
Instead of ad-hoc requests via email and Teams, license needs flow through a structured cycle. Country admins submit a reservation batch each month: what they need, how many, for which SKU. Global IT reviews each batch line by line — with the monthly cost calculated automatically for each item. Approved quantities are blocked from the pool before the cycle opens to others.
This replaces the spreadsheet, the email thread, and the manual Admin Center work with a single workflow. The audit trail is built in. The cost visibility is real-time.
3. Out-of-band detection
Every license assigned directly in the Microsoft Admin Center — bypassing the reservation process — is flagged automatically on the next sync cycle. Global IT sees the user, the SKU, the country, and the detection date. The decision is human: review it, regularise it in the portal, or escalate to the regional admin.
Nothing is auto-reversed. The governance layer informs and flags. Humans decide and act.
4. Inconsistency detection
A maintained map of SKU inclusions — Power BI Pro inside E5, Exchange Online Plan 1 inside E3, Defender inside various bundles — checked against every user's actual assignment on each sync. Redundancies surface automatically with the monthly cost impact and severity level. The decision to act remains with the IT team, but the discovery is automatic and continuous.
The Business Case in One Paragraph
For a 1,000-user multinational with operations in five countries and an average license cost of €22/user/month, regional license governance typically recovers between €40,000 and €80,000 per year in combined savings — from inactive licenses, SKU redundancies, out-of-band drift, and wrong-tier assignments. That's a conservative estimate based on industry benchmarks. The operational savings — IT time freed from manual reconciliation, coordination threads, and monthly audit work — add further value that's harder to quantify but immediately visible to the team that lives it.
A governance tool at €599/month pays for itself in under six weeks at that scale.
What to Look For in a Governance Solution
If you're evaluating options — and by now you should be — here's what actually matters:
Country-level quotas, not department-level. Most tools that have quota concepts work at the department or Administrative Unit level within a single location. Multinational governance needs country or subsidiary as the primary organisational unit.
A reservation cycle, not just reporting. Reporting tells you what happened. A reservation cycle shapes what happens. The distinction is between reactive management and proactive governance.
Out-of-band detection. If the tool doesn't flag assignments made directly in the Admin Center, it can't close the governance loop. Someone will always go directly to Microsoft when under time pressure.
SKU inclusion awareness. Any tool worth using should know that E5 includes Power BI Pro, and that assigning both is redundant. This shouldn't require a consultant to identify.
Self-hosted or EU-hosted option. For European organisations subject to GDPR, knowing where your tenant metadata is processed matters. A tool that requires you to send data to servers in the US creates compliance questions you don't need.
Transparent pricing. If you can't see the price without booking a demo, the pricing is designed for enterprise procurement cycles, not mid-market decision-making. Your CFO will thank you for a product with a public price table.
The Conversation You Want to Stop Having
The IT coordinator in Germany gets her ten licenses on Monday. Not because you scrambled to fix it over the weekend, but because Germany's allocation was reserved three weeks ago during the monthly cycle, and nobody else could touch it.
The admin in Brazil who assigned three licenses directly gets a notification — not a reprimand, just a flag that the assignment was detected outside the portal and needs to be reviewed. The conversation with the regional manager is a fifteen-minute process, not a budget investigation.
The €21,120/year in E5 + Power BI Pro redundancies appears in the inconsistency report on the first sync after deployment. Someone reviews it, removes the redundant assignments, and the savings hit the next invoice.
This is what governance looks like when it's working. Not more tools, not more meetings, not more PowerShell. Just a process that runs continuously, flags what needs human attention, and protects what's already been allocated.
About Portalliz
Portalliz is a Microsoft 365 license governance platform built specifically for multinational organisations with a single global tenant. It provides regional license quotas by country, a monthly reservation and approval cycle, automatic out-of-band detection, and a SKU inconsistency engine — as a self-hosted application or EU-hosted SaaS.
It was built by a Global IT Manager who managed 600+ users across 19 sites and ran out of patience with the problem described in this article.
Try it yourself: portalliz.com/download — fully functional demo, no Microsoft 365 credentials needed, Docker-based, running in under 15 minutes.
Request a pilot: portalliz.com/contact — 90 days free, no credit card, no commitment.
Microsoft 365 and Microsoft Graph are trademarks of Microsoft Corporation. Portalliz is an independent product and is not affiliated with or endorsed by Microsoft.