Register the sources
Microsoft 365 and cloud tenants, Entra, and every datasource you want read — each with its scanner group and sensitivity tier.
← Platform GOVERNANCE
Prove it. Don’t promise it.
From a scan of your estate to evidence you can hand over. Five steps, in the order the work actually happens. Each one is a page in the portal, not a services engagement.
Governance, end to end
Look for what matters
A template says what a scan looks for — the classifier rules it matches values against. Bound to its sources, it becomes a profile you can run, stop and watch.
File the facts
Findings, paths, permissions and file metadata land in your own metadata catalogue, each object stamped with the scan it came from.
Apply your policy
Your classification levels and their match rules run against the catalogue — as a dry run first, with a full history and a rollback.
Take the data point
Snapshots of identity risk, sharing, retention and GDPR posture, compared over time.
Facts first, judgement second.
Facts first, judgement second.
Extraction records what was found and assigns no sensitivity of its own. The level is derived afterwards, from your policy — which is what lets you reclassify the whole estate without scanning it again.
The gaps show themselves.
Objects of one shape classified several ways, classified data in public teams, sensitive objects with no owner — the catalogue surfaces the rule you have not written yet, and an automation can alert on it the next time posture moves the wrong way.
The last step is a page in the portal. See the reporting, or explore the architecture it runs on.
Prove it. Don’t promise it.
Assess your AI readiness
Takes one workshop. Grounded in your real data.