Microsoft Purview label coverage
You designed the labels. Where did they actually land?
Most tenants spend months designing a Purview taxonomy and never measure where it landed. 1Security counts it: how many real files, emails and groups carry each label, which labels actually encrypt and which only print a word in the ribbon, and - the number that matters - how many files with card numbers, IDs or health data carry no label whatsoever.
- 20-40%of files with detected sensitive data carry no sensitivity label in a typical tenant
- 3resource types counted per label - files, emails and groups - live, not as designed
- 0E5 licenses needed: the coverage gap is found by 1Security's own 300+ detectors
The problem
A taxonomy is a plan. Coverage is what happened to it.
A taxonomy is a design. Coverage is what happened afterwards - and it is worth counting.
The first gap is deployment. A label named Highly Confidential applied to twelve files is not a data protection programme, and that only shows up when somebody counts. In the tenants we connect to, the top-priority label is routinely on fewer than 1% of the files it was designed for.
The second gap is protection. Some labels encrypt and watermark; others display a name and nothing else. Thousands of documents marked Confidential that any recipient can open and forward is the most common false comfort in Microsoft 365, and the two kinds look identical in a list of label names.
The third gap is sensitive data with no label at all. Card numbers in a scanned contract, ID numbers in an HR spreadsheet, credentials in a text file. Whatever users did not label by hand and no auto-labelling rule caught stays unlabelled - typically 20-40% of everything sensitive. 1Security finds it with its own detectors, on any license.
What you get
Six columns that measure the programme.
The labels stay Microsoft's and sync natively. What 1Security adds is the count of where they landed and what they missed.
Live counts per label
Sensitivity labels shows every Purview label with real file, email and group counts. Sort by files and the aspirational labels - designed for the crown jewels, applied to a handful of documents - sink to the bottom.
Protection flag
A column that says whether the label encrypts and watermarks or only displays a name. Filter high priority + no protection + high count: those documents are readable by anyone who receives them.
The unlabelled sensitive files
Files: filter with sensitive info + without label. Found by 1Security's own 300+ detectors with OCR for scans and screenshots - so it works on any Microsoft 365 license and adds OCR coverage for scans and images.
Coverage per site
Sites carries label counts next to sensitive-info counts, so "the HR site holds 4,000 sensitive files and 900 labels" is a row, not a project. Sort by the gap and start there.
Taxonomy drift
Inactive labels still sitting on content from before they were retired, priority orders that stopped making sense two reorganisations ago, labels scoped to formats nobody uses - each a filter.
Evidence for auditors
Per-label deployment numbers and the unlabelled-sensitive count, exportable to CSV, replace "we have a labelling policy" with a control that is demonstrably operating.
How deep it goes
The false-comfort check, in one filter.
The list that comes out is usually short, uncomfortable and fixable in an afternoon.
On Sensitivity labels, filter to your highest-priority labels without protection, sorted by file count. In most tenants one or two labels named Confidential or Internal carry tens of thousands of documents and encrypt none of them. The label is doing reputational work rather than technical work, and everybody involved believes the opposite.
Then the other side. On Files, filter with sensitive info + without label, sort by detections. This is the number every labelling programme needs and rarely has: how much sensitive content nobody classified. It is common to find that a third of files holding card numbers or ID numbers carry no label - and that half of those sit in sites with external users or anyone links.
Both numbers come from the same scan, on a Business Basic tenant. Where you run Purview, its labels and detections are synced alongside and the two engines are compared; where you do not, the measurement still works. Together they turn "are we protected?" into two numbers you can track quarter over quarter.
In practice
Four ways a labelling programme fails - and how each shows up.
A per-label count surfaces each of these on day one. A policy review never does.
- 01
Sort labels by file count
The aspirational label surfaces immediately: designed for the most sensitive material, applied to a few dozen documents because applying it correctly needs a judgement nobody made. Typical finding: the top-priority label on under 1% of sensitive files.
- 02
Filter to no protection
The decorative label: high usage, no encryption. The one that produces the most confidence and the least security. Fixing the label definition in Purview once protects every document carrying it.
- 03
Filter to inactive labels with content
The zombie label: retired in the taxonomy, still on thousands of files from before, sometimes still enforcing an old policy. Re-label or accept, but decide.
- 04
Open Files, sensitive + no label
The uncovered majority: the sensitive content nobody classified. This list, sorted by exposure, is the work queue - and the "Unlabelled sensitive files" trend keeps the count on a chart so it goes down and stays down.


Working with Purview
Purview labels, measured - not replaced.
Labels sync natively from Purview, so every number here agrees with your configuration.
- Live counts of the files, emails and groups actually carrying each Purview label
- A protection column that separates labels that encrypt from labels that only display a name
- 300+ detectors with OCR find unlabelled sensitive data on Business Basic - no auto-labelling license required
- Inactive labels still sitting on live content, as one filter
- Priority orders compared with how the labels are actually used
- Labels next to sites, users, groups and apps, so a label's reach is one click away
- A per-site coverage ratio: label counts against sensitive-info counts on the Sites screen
- Per-label deployment numbers as an export, for auditors who want a control operating rather than a taxonomy document
Licensing
No premium requirement on our side.
A Business Basic tenant is enough for every number on this page, including the sensitive-data detections behind the coverage gap. Taxonomy, auto-labelling and enforcement stay in Purview, where they belong - 1Security shows you exactly where they did and did not land.
- 300+sensitive information types detected by 1Security's own engine, with OCR for images and scans
- 3resource types counted per label - files, emails and groups - synced natively from Purview
- 90 daysis the window most teams pick to trend the unlabelled-sensitive count down
Related
Where this fits.
Coverage has two sides. This screen holds the labelled half; the unlabelled half lives with the sensitive files and the sites they sit in.
Sensitive data discovery
Where the card numbers, IDs and health data actually are, and who can reach them - the source of the unlabelled count.
See sensitive data →File permissions
The Files screen where sensitive + no label lives, with exposure - anyone links, external users - resolved per file.
See files →Purview integration
How the two products fit together across detections and labels, and what each one needs licensed.
See Purview →
The 1Security platform
Label Coverage is just the beginning
Label Coverage is one screen of the 1Security platform for Microsoft 365. Locations, devices, apps, AI agents, logs, permissions, sensitive data, compliance, reports and actions run on the same read-only connection, on the licence you already have.
- Anomalies and detectionsSpikes in sharing, downloads, sign-ins, consent and agent activity, scored against each tenant’s own pattern, with curated response actions.


- Permissions and sharingWho can reach what, through which group, link or guest, and whether anyone meant it. The sharing map every audit asks for.


- Sensitive dataPersonal data, credentials, financial and health records found by our own classifiers, with a Microsoft second opinion where the client has it.


- Files, sites and the column browserBrowse the tenant like a file system: site, library, folder, file, with the permissions and sensitivity of each level beside it. A problem solved in itself.


- Users, groups and lifecycleDormant accounts, guests who never left, groups nested three deep, orphaned owners, admins without MFA. The review that is a spreadsheet everywhere else.


- External domainsEvery outside organization with a foothold in the tenant, its trust posture, its drift, and who it was invited by.


- Microsoft 365 Alerts ToolOne alert model across policies, activity and anomalies - with the evidence attached and the alert threshold in your hands.
- Microsoft 365 Monitoring ToolReal-time monitoring that catches a mass download while it is unfolding - across users, files, apps, AI agents and devices.
- Copilot Security ToolEvery AI agent's real blast radius - quantified before rollout, watched and constrained after.
- Shadow Device DetectionEvery device touching your data, reconstructed from real activity - including the machines that never enrolled anywhere.
- Impossible Travel DetectionLocations as identities, not IPs: country, city and network for every action, first-seen origins, travel timelines with verdicts - no E5, no P2.
- Conditional Access MonitoringDeclared Conditional Access compared against observed sign-ins: coverage verdicts, ungoverned traffic share, and the ranges your offices outgrew.
- Office 365 Access ManagementEffective access, resolved - who can reach what, through which grant, and one place to take it away.
- SharePoint Governance ToolEvery site ranked by exposure and abandonment - links, guests and Copilot access under control.
- Office 365 User ProvisioningLifecycle access from day one to offboarding - reach, dormant accounts and license reclaim in one flow.
- Microsoft 365 Audit ToolUp to three years of searchable activity history - every action tied to an actor, device and location.
- Microsoft 365 Inventory ToolEight live inventories on one permission graph - including the sites, devices and AI agents that were never registered anywhere.
- Office 365 ReportingAnswers, not exports - regulator-grade numbers, saved views and a read-only API for your SOC.
- Microsoft 365 File PermissionsWho has access to any file, and why - people, links, apps and AI agents on one map, with the fix in the same place.
- Sensitive Data DiscoveryWhere regulated data lives and everything that can reach it - two detection engines, no premium licence required.
- Office 365 Email MonitoringOutbound sensitive content, delegated-send abuse and whole-thread evidence that survives deletion.
- AI Agent InventoryEvery agent in the tenant with its real reach counted, its blueprint reviewed, and guardrails you can verify.
- AI Data RestrictionDeclare a data type off-limits to AI and every agent, app and user still reaching it becomes a live violation - recorded for the auditor.
- AI Spend TrackingInteractions, Copilot credits and Azure tokens in one ledger per agent - with the spend column next to what each agent can reach.
- Microsoft 365 User Access ReviewEvery identity with what it can reach, what it did, and whether it should still exist - including SharePoint-only guests that live outside the directory.
- Group Access AnalysisWhat membership in a group actually unlocks - nesting resolved, external members surfaced, blast radius counted.
- App and OAuth Consent GovernanceEvery app with a foothold in the tenant: how it got in, who let it in, and what it can actually read.
- Remediation AutomationFindings become fixes at tenant scale, counted before you enable them and staged behind a review window.
- Microsoft 365 Licence OptimizationThe seats you pay for and nobody uses - unassigned units, licences on guests, and dormant accounts still billing.
- Microsoft 365 Anomaly DetectionEvery policy, user, app and agent measured against its own baseline - with an alert line you move and see the answer to at once.
- Office 365 Sign-in LocationsEvery place your tenant is reached from, with your Conditional Access configuration laid over observed reality.
- Microsoft 365 Unified Audit LogWho did what, when, from where and on which device - retained up to three years on a standard licence.
- SharePoint Site InventoryEvery site, channel site and OneDrive in one list, ranked by external reach, abandonment and what Copilot can read.
- Microsoft 365 Activity AnalyticsThe extremes rather than the averages - a mass download inside the hour, and everything nobody has touched in a year.
- Microsoft 365 Trend TrackingAny number in the tenant followed over time, with the change and the deviation attached - and alerting on the same object.
- Microsoft 365 Compliance MonitoringReadiness for eleven regulations measured from live tenant data - with weekly snapshots and a dated evidence pack per framework.
- Microsoft 365 Security ScoreMicrosoft Secure Score beside the score measured from what actually happens - one worklist ranked by points still on the table.
- External Domain MonitoringEvery organisation your tenant exchanges data with, resolved to a real company - with drift flags and an enforceable verdict per domain.
- All featuresExplore everything
FAQ
Questions teams ask first.
Does this change my labels?
No. Labels are synced natively from Purview and stay Purview's. Taxonomy design, auto-labelling and enforcement are configured there. 1Security adds the measurement of where the labels actually landed and what they missed.
What does the protection flag mean exactly?
Whether the label applies real protection - encryption and watermarking - as opposed to only displaying a classification name. That distinction decides whether a leaked file is readable, and it is invisible in a list of label names.
Do we need E5 to see the unlabelled sensitive files?
No. The coverage gap is found by 1Security's own scanning engine - 300+ detectors plus OCR - so it works on any Microsoft 365 license and adds OCR for scans and images. Business Basic is enough.
How long until we see our numbers?
Label counts appear after the first read-only scan, usually the same day. The unlabelled-sensitive count grows as the sensitivity scan works through the tenant; on large tenants the first sites report within hours and the picture is complete over the following days.
How do I use this with an auditor?
Export per-label deployment counts and the unlabelled-sensitive count. That is evidence of a control operating rather than a control designed - a different conversation from presenting a taxonomy document, and the one auditors increasingly ask for.
Measure the labelling programme you already paid for.
Connect read-only and the per-label counts land the same day. The protection column is usually the uncomfortable one; the unlabelled-sensitive count is the one that gets fixed first.
Or keep trusting the taxonomy document.