Access Intelligence
See who can reach your classified content
Access Intelligence classifies containers from OFFICIAL through to PROTECTED data on M365, then finds PROTECTED content exposed to guests and people without clearance.
What you get
Why teams choose Access Intelligence
01
See who can reach PROTECTED content
Each scan lists the accounts that can reach a PROTECTED site or team without a recorded clearance for it, and how their access was granted.
02
Trace each classification to its source
Every classified container records whether its level came from a sensitivity label or the SharePoint classification field, so the result can be checked.
03
Find guests and dormant accounts
Guest accounts on classified containers are flagged by default, and clearance holders who have not signed in for 90 days, or the period you set, are listed.
04
Make exceptions defensible
Exemptions carry a justification, an optional expiry date and an audit trail entry, with an optional second approver for PROTECTED content.
05
Act when you decide to
Once your tenant grants remediation consent, an administrator can remove the access behind a violation, with a warning first if the user is an eDiscovery custodian in an open case.
A scan classifies each container from OFFICIAL through to PROTECTED, with the source of every classification recorded.
How it works
From connection to evidence
- 1
Map labels and clearances
You map each sensitivity label to a PSPF level and point T365 at the Entra ID groups or user attribute that record clearances.
- 2
Scan
A scheduled scan, daily by default, reads the labels and membership of SharePoint sites and Teams.
- 3
Compare
Each classified container's level is compared with the clearance of each account that can reach it.
- 4
Review
Violations, guest access and dormant accounts are listed with how access was granted.
- 5
Decide
Remove the access, raise an exemption, or start an Entra ID access review of a clearance group.
In detail
How Access Intelligence works
How classification works
A scan reads sensitivity labels on SharePoint sites and Teams and maps each label to one of three PSPF levels, OFFICIAL through to PROTECTED. Where a site's sensitivity labels aren't available, SharePoint's own classification field is used instead, and either way, where the classification came from is recorded against the container.
The result is auditable: a PROTECTED label on a container can be traced back to the sensitivity label, or SharePoint classification field, it came from, not just displayed as a number on a dashboard.
Finding exposure to PROTECTED content
Once containers are classified, Access Intelligence finds PROTECTED content exposed to people without clearance for it, comparing each container's classification against the clearance of the accounts that can reach it.
Clearance is resolved from an Entra ID group or user attribute your organisation already maintains, with the source of every clearance recorded so it can be checked. Guest access and dormant accounts that still hold access are also surfaced, since both are common ways exposure creeps in over time.
Exemptions and optional two-person approval
Not every exposure is a mistake; some are deliberate and already accepted. Exemptions record a justification of at least 50 characters and an optional expiry date, and are written to the audit trail so the decision is traceable later.
For PROTECTED exemptions, tenants can optionally require a second approver: with two-person integrity turned on, the person raising the exemption cannot also approve it. This is off by default and is a per-tenant setting.
Who it is for
Built for the people accountable for it
Agency security advisers
See where PROTECTED content is reachable by people without a recorded clearance, with the source of each classification.
Personnel security teams
Run Entra ID access reviews of clearance groups, optionally with two approvers, and find dormant clearance holders.
Microsoft 365 administrators
Remove an uncleared account from the site, team or group behind a violation, once remediation consent is granted.
Auditors and assurance teams
Check each exemption’s justification, expiry date and approver in the audit trail.
Frameworks
The frameworks it helps you evidence
Attorney-General’s Department
Protective Security Policy Framework (PSPF)
T365 maps your sensitivity labels to PSPF levels from OFFICIAL to PROTECTED and compares them with the clearances your organisation records, listing who can reach content above their recorded clearance.
Read the source (opens Attorney-General’s Department in a new tab)Australian Signals Directorate
Information Security Manual (ISM)
The ISM's personnel security guidelines expect users to hold a suitable clearance before they access classified systems and data. T365 lists the accounts that can reach PROTECTED containers without one, to support that review.
Read the source (opens Australian Signals Directorate in a new tab)Australian Signals Directorate
Blueprint for Secure Cloud
The Blueprint describes configuring Microsoft 365 sensitivity labels for OFFICIAL to PROTECTED content. Access Intelligence reads the labels applied to sites and teams and checks who can reach them.
Read the source (opens Australian Signals Directorate in a new tab)T365 measures, maps and records evidence against these frameworks. Your organisation remains responsible for its own assessment and authorisation decisions.
Questions
What buyers ask us
What classifications does Access Intelligence cover?
OFFICIAL, OFFICIAL: Sensitive and PROTECTED, the levels Microsoft 365 sensitivity labels are used for in Australian Government. It does not cover classifications above PROTECTED.
Where does clearance information come from?
From Entra ID: either a group naming convention or a user attribute your organisation already maintains, mapped to clearance levels in the tenant settings. T365 reads clearances; it does not grant or verify them, and the source of each one is recorded.
Does it read our documents?
No. It reads the sensitivity label or classification on each SharePoint site and team, and who can reach it. It does not open documents.
Does it change my tenant?
Scans only read. Removing access is a separate action that is available only after remediation consent is granted for the tenant, needs governance permission, and is written to the audit trail. Access reviews are created in Entra ID only when you start one.
How often does it scan, and are extra licences needed?
Scans run daily by default; the interval is set per tenant, or you can scan on demand only. Dormant-account detection uses Entra ID P1 sign-in data, and access reviews need Entra ID P2 or Microsoft Entra ID Governance in your tenant.
Does it use AI?
No. Results come from comparing labels, membership and recorded clearances. Access Intelligence is also off until it is turned on for a tenant.
Evidence: where each claim on this page comes from
Containers are classified from sensitivity labels, with the source of every classification recorded
apps/web/src/lib/access-intel/access-intel-worker.ts
Classification spans three PSPF levels, OFFICIAL through to PROTECTED
apps/web/src/components/access-intel/ContainersTab.tsx
Two-person approval for PROTECTED exemptions can be required, with self-approval rejected
apps/web/app/api/access-intel/[tenantId]/violations/[violationId]/exempt/route.ts
More of the platform
Works with the rest of T365
Buying for government? We are on the DTA Digital Marketplace.
- Software
- Cloud
- Professional services
- Labour hire
- Hardware
Ready to Secure Your Microsoft 365?
Start your free 14-day trial or talk to our team about your needs.