Every feature exists because someone felt the pain first.
No roadmap padding. No enterprise bloat. Each capability below was built to solve a specific, measurable problem in multinational Microsoft 365 tenants.
One global pool. Zero regional control. Until now.
Your Microsoft 365 tenant shows 6,800 licenses available. Germany submits a request for 10 E1 licenses β standard onboarding cycle, planned weeks in advance. By the time the order is processed, the licenses are gone. Another region saw availability in the global pool and consumed them. No alert. No reservation. No process.
The result: a Teams conversation at 3pm, manual coordination across time zones, and a new employee who can't start work on Monday.
Each country or subsidiary gets a reserved quota β a defined number of licenses blocked from the global pool before any other region can touch them. Germany's 80 E1 licenses are Germany's. Full stop.
Administrators see Reserved, Assigned, Available, and Emergency Buffer per country, per SKU, in real time. Status indicators (OK / LOW / EXHAUSTED) surface problems before they become incidents.
| Country | SKU | Reserved | Assigned | Buffer | Available | Status |
|---|---|---|---|---|---|---|
| DE | M365 E5 | 120 | 118 | 5 | -3 | Exhausted |
| FR | M365 E3 | 90 | 72 | 5 | 13 | Low |
| PT | M365 E3 | 60 | 22 | 5 | 33 | OK |
License requests without a process are just chaos with extra steps.
License requests arrive by email, Teams message, ticket, or phone call β depending on the region, the urgency, and who happens to pick up. There is no standard format. No approval chain. No visibility into what was requested, by whom, for how many people, at what cost.
Global IT spends hours each month reconciling requests against actual assignments β manually, in spreadsheets, after the fact.
Every month opens a request cycle. Country admins submit reservation batches β specifying which licenses they need, how many, and for which cycle. Global IT reviews each batch line by line, with cost per item calculated automatically.
Approved quantities are immediately blocked from the global pool. Pending items are tracked. The audit trail is complete before anyone opens the Microsoft Admin Center.
| M365 E1 | 10 requested | Pending | β¬80.00 |
| M365 E3 | 5 requested | Pending | β¬180.00 |
| Power BI Pro | 2 requested | Pending | β¬17.60 |
Someone assigned a license directly. Your governance layer never knew.
An admin in France opens Microsoft 365 Admin Center and assigns an E3 license directly to a new hire. No request. No approval. No reservation batch. The license is consumed from the global pool without touching any internal process.
Your monthly report is now wrong. Your quota calculation is off. And nobody will know until the next audit β if there is one.
Every license assignment in your Microsoft 365 tenant is compared against Portalliz reservation records on each Graph sync. Any assignment made directly in Microsoft 365 Admin Center β without a linked reservation batch β is flagged as out-of-band.
Your team sees the user, the SKU, the country, and the detection date. You decide: mark as reviewed, regularize in the portal, or escalate to the regional admin. Nothing is changed automatically.
| Anna MΓΌller | Power BI Pro | DE | Detected today | Open | |
| Marie Dubois | M365 E3 | FR | Detected today | Open |
You're paying twice. The Admin Center will never tell you.
Microsoft 365 E5 includes Power BI Pro. If a user has both assigned separately, they β and you β are paying β¬8.80 per user per month for nothing.
This happens because license assignments accumulate over time. Someone gets E5 as part of a role change. Nobody removes the standalone Power BI Pro they had before. Multiply this across hundreds of users in multiple countries and the waste is significant β and completely invisible in the Microsoft Admin Center.
50 users Γ β¬8.80/month = β¬440/month β¬440 Γ 12 months = β¬5,280/year β in one SKU combination alone.
Portalliz maintains a map of SKU inclusions β which standalone licenses are already included in higher-tier plans. On every sync, it compares each user's assignment against this map and flags redundancies automatically.
Each inconsistency shows the user, department, country, the redundant SKU, the monthly cost, and a severity rating. Nothing is removed automatically β you review and decide.
| Klaus Weber | Engineering | DE | M365 E5 includes Power BI Pro | β¬8.80/mo | Warning | Open |
| Marie Dubois | Operations | FR | M365 E3 includes Exchange Online Plan 1 | β¬4.20/mo | Info | Open |
Everything Portalliz knows about your tenant comes from a read-only connection. Nothing more.
Giving a third-party tool access to your Microsoft 365 tenant is a decision that requires trust. What data does it read? Can it make changes? What happens if it's compromised?
These are the right questions. And they deserve precise answers β not marketing language.
Portalliz connects to your tenant via Microsoft Graph API with read-only permissions. The consent screen shows exactly what is requested. Nothing is hidden, nothing is bundled.
We read three things:
- Which SKUs your tenant has subscribed to
- Which users exist and what licenses they hold
- Per-user license assignment details
We never read email, calendar, Teams, files, or security data. We never request write permissions. Every sync is logged with timestamp, duration, and record count.
- /subscribedSkus
- /users
- /users/{id}/licenseDetails
- β Email, calendar, Teams content
- β Files (OneDrive, SharePoint)
- β Security & sign-in data
- β Any write permission
License costs by country, by SKU, by month. Finally in one place.
How much does Germany spend on M365 licenses per month? Which SKU is your biggest cost driver? Which country is approaching its quota limit before the cycle closes?
These questions require pulling data from Microsoft Admin Center, cross-referencing with your EA agreement pricing, and building a spreadsheet β every single month.
Portalliz tracks license costs against configurable SKU pricing, broken down by country, by SKU, and by billing cycle. Analytics surfaces:
- Monthly cost per country
- Cost per SKU across the tenant
- Quota utilization trends over time
- Pending request cost before approval
- Estimated savings from inconsistency resolution
Seen enough?
Start with the demo β no Microsoft 365 credentials needed.