Reads the signals
We read the data behind all six review areas, accounts, admin access, apps, groups, licences and security settings, straight from Microsoft 365 and Entra ID. Nothing gets changed.
How It Works
A controlled Microsoft 365 review, run the same way each time.
LicenMark reads the evidence across your accounts, admin access, applications, groups, licences and core security settings, checks it against fixed rules, and hands you back a plain-English, prioritised list of what needs a look, and why.
No write-back. No remediation. Start your review online when you are ready — create your account, connect Microsoft 365, and continue through payment.
What the review actually does
It turns scattered Microsoft signals into a clear review output.
Applies explicit review rules
Every account, admin assignment, app, group, licence and security setting gets checked against the same fixed rules, every time. If we don't have the evidence we need, we say so, we don't guess and we don't quietly mark it as fine.
Produces a prioritised review
Related findings get pulled together into one clear picture: what to look at first, what to look at next, why it matters, and what we'd suggest checking. We don't take the action for you, that decision stays with your team.
What the review looks at
Six areas. The ones that quietly go unreviewed until someone asks.
The method stays deliberately narrow, read-only, fixed rules, no guessing, while the review itself covers six areas that are easy to lose track of and hard to explain cleanly if someone asks.
- User and guest accounts Inactive, disabled, never-used or external accounts still holding access or a paid licence.
- Administrator access Admin rights that are unused, excessive, external, or have been standing far longer than they should.
- Applications and integrations Apps and integrations with broad access, unclear ownership, or credentials about to expire.
- Groups that control access Groups that control something important but have no owner, unclear membership, or don't apply to anyone anymore.
- Licences and paid features Licences nobody's using, and paid features you're already covered for but haven't switched on.
- Tenant security settings Gaps in the basics: Conditional Access, MFA, legacy authentication, password reset, and who can bring in external users.
- Review-ready reporting outputs Structured outputs built for internal circulation and management review, not raw data dumps.
Review items
What the review work actually looks like.
Every open item, an access risk, an overdue admin check, a licence going to waste, or a security setting that's not where it should be, lands in one prioritised list you can work through in order.
What gets surfaced
The review separates what is obvious from what still needs judgement.
Some findings are clear-cut: a disabled account still holding an admin role, or a purchased licence nobody's assigned to.
Other times, we simply don't have enough evidence to say for certain, maybe a permission or an API limit got in the way. When that happens, we say so directly, rather than guessing or quietly marking it as fine.
Clear findings
- A disabled account still holding admin access
- An external account with more access than it should have
- An app whose only working credential is about to expire
- Licences that are paid for but assigned to nobody
Review-required findings
- Areas where we couldn't get the evidence we needed, due to permissions or an API limit
- We say so plainly, we don't count it as a pass
- The rest of the review carries on around it
What the output looks like
A clear current position, open review items, and evidence you can circulate.
The output is built for internal review, not for technical curiosity.
Current review position
A short summary across all six areas: what's fine, what needs a look, and anywhere we couldn't get enough evidence to say for sure.
Open review items
The specific accounts, admin assignments, apps, groups, licences or settings that need your attention now, ranked so you know what to look at first.
Exportable evidence
A report you can hand to your manager, your auditor, or your own team, with the finding, the evidence behind it, and why it matters, already written up.
Review detail
Each item is backed by a clear conclusion and supporting evidence.
Every finding gets the same treatment: what we found, why it matters, the evidence behind it, and what we'd suggest reviewing next. Where we can put a number on it, we do.
Why the model is read-only
Because trust falls fast when review tools start making changes.
LicenMark doesn't disable accounts, remove licences, change admin roles, touch apps or groups, switch security settings on or off, or write anything back to Microsoft 365.
That is deliberate. The product exists to surface the current position clearly, not to take actions inside your tenant.
For this kind of review, read-only is not a limitation. It is part of why the output is easier to trust.
- Reads your tenant. Changes nothing.
- Surfaces review items clearly.
- Leaves remediation decisions with your team.
- States uncertainty plainly instead of hiding it.
How teams use it
Start with a one-off review. Use quarterly reviews to see what changed.
Some teams just need one clear picture of where they stand right now, across accounts, admin access, apps, groups, licences and security settings.
Others want that same review run every quarter, so they can see what's been sorted, what's still open, and what's quietly crept back since last time.
LicenMark supports both. Start with a one-off review, then continue only if tracking change over time is useful.
Next step
Move forward in the way that fits your buying process.
Create your account and continue online when you are ready. Connect Microsoft 365, see the correct price for your organisation, and pay securely through Stripe.
Start with a one-off review. Move to quarterly only if seeing what changed between reviews is useful for your team.
For more context, review the read-only security model or see the Microsoft 365 review pricing bands.