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.

Quotas

One global pool. Zero regional control. Until now.

Without Portalliz

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.

πŸ”΄ No regional reservationπŸ”΄ Silent consumption by other regionsπŸ”΄ Manual coordination every cycle
With Portalliz

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.

βœ… Regional quota protectedβœ… No silent consumptionβœ… Real-time visibility per country
Country quota dashboard
CountrySKUReservedAssignedBufferAvailableStatus
DEM365 E51201185-3Exhausted
FRM365 E39072513Low
PTM365 E36022533OK
Workflow

License requests without a process are just chaos with extra steps.

Without Portalliz

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.

πŸ”΄ No standard request formatπŸ”΄ No approval workflowπŸ”΄ Cost visibility only after assignment
With Portalliz

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.

βœ… Structured monthly cycleβœ… Line-by-line approval with costβœ… Full audit trail before assignment
Reservation batch
batch-3Germany2026-063 items17 licenses€277.60/monthIn review
M365 E110 requestedPending€80.00
M365 E35 requestedPending€180.00
Power BI Pro2 requestedPending€17.60
Drift

Someone assigned a license directly. Your governance layer never knew.

Without Portalliz

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.

πŸ”΄ Assignments bypass your process silentlyπŸ”΄ Quota drift undetected until auditπŸ”΄ No way to know who assigned what
With Portalliz

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.

βœ… Every bypass detected automaticallyβœ… Human decision β€” nothing auto-reversedβœ… Complete out-of-band audit log
Out-of-band assignments
Anna MΓΌllerPower BI ProDEDetected todayOpen
Marie DuboisM365 E3FRDetected todayOpen
Savings

You're paying twice. The Admin Center will never tell you.

Without Portalliz

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.

πŸ”΄ No SKU inclusion awareness nativelyπŸ”΄ Redundancies accumulate silentlyπŸ”΄ Waste only visible after manual audit
50 users Γ— €8.80/month = €440/month
€440 Γ— 12 months     = €5,280/year

β€” in one SKU combination alone.
With Portalliz

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.

βœ… SKU inclusion map maintained automaticallyβœ… Redundancies flagged on every syncβœ… Cost impact calculated per user
Inconsistency engine
Klaus WeberEngineeringDEM365 E5 includes Power BI Pro€8.80/moWarningOpen
Marie DuboisOperationsFRM365 E3 includes Exchange Online Plan 1€4.20/moInfoOpen
Estimated waste
Monthly: €26.00 Β· Annual: €312.00 Β· Highest impact country: DE
Sync

Everything Portalliz knows about your tenant comes from a read-only connection. Nothing more.

The Concern

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.

How Portalliz Connects

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.

βœ… Read-only β€” no write permissionsβœ… Every sync logged and auditableβœ… Preflight check before first connection
Graph sync Β· last run
Status: SUCCESS
Last sync: today Β· 16:16:07
Duration: 133ms
Users: 6
Assignments: 10
SKUs: 8
What we access
  • /subscribedSkus
  • /users
  • /users/{id}/licenseDetails
What we never access
  • βœ• Email, calendar, Teams content
  • βœ• Files (OneDrive, SharePoint)
  • βœ• Security & sign-in data
  • βœ• Any write permission
Analytics

License costs by country, by SKU, by month. Finally in one place.

Without Portalliz

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.

πŸ”΄ No cost visibility by region nativelyπŸ”΄ Manual spreadsheet every monthπŸ”΄ No trend data without custom reporting
With Portalliz

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
βœ… Cost by country and SKU automaticallyβœ… Pending cost visible before approvalβœ… Savings tracked from inconsistency engine

Seen enough?

Start with the demo β€” no Microsoft 365 credentials needed.