Product · for the company that owns the tenant
What's actually protecting your data, screen by screen.
You already pay for Microsoft Purview inside Microsoft 365. Neoview connects to your tenant read-only and shows you what it's doing, what's switched off, and what to fix first.
Your data security, scored.
One number your board can follow, three things worth fixing this month, and a PDF button. That's the page.
- ✓A score that moves when the tenant does.
74 of 100. It changes when a policy changes, not when someone updates a slide.
- ✓The three things worth fixing.
Ranked by exposure. Here: a DLP policy your people skip 56% of the time, one person doing it repeatedly, and a licensed capability nobody switched on.
- ✓The PDF, with or without names.
Names hidden for the board or the insurer, names shown for IT. Same page, two buttons.
Where your data is actually protected.
Rows are places, columns are kinds of sensitive data, and each cell is the strongest thing Purview does there today. Simulation counts as measuring, not protecting.
See it in the demo →- ✓Simulation is not protection.
Policies in test mode are counted on their own. "5 of 5 locations protected" means enforcing, not "has a policy".
- ✓The strongest action per cell.
A block your people can override is a weaker promise than a block. The map says which one you actually have, for each kind of data in each place.
- ✓Laptops: audit only.
No Endpoint DLP rule blocks anything yet. Not a reason to panic; it's the next line on the roadmap below.
Which rule covers which data, and what happens to it.
Follow a kind of data across to the policy, the place and the outcome. Flip the switch and it shows what isn't covered at all.
See it in the demo →- ✓231 kinds of data with no rule.
Purview knows about hundreds of sensitive information types. Your rules name a handful. The gap is a number you can put in front of someone, not a feeling.
- ✓Show what's not covered.
One switch turns the map inside out: the data types, labels and places that no policy touches.
- ✓The outcome, in words.
Blocked for external recipients. Watched only. Simulation. Not "rule 3 of policy B".
A 90-day plan that your own tenant keeps honest.
Generated from the coverage map: measure, then warn, then protect, place by place. Status comes from a daily snapshot of the configuration. Your IT team, or your partner, works through it; nothing is marked done because someone said so.
See it in the demo →- ✓66% done, measured.
23 of 35 items, read from the configuration, not from a checklist.
- ✓Three phases, dated.
Days 0–30 measure, 31–60 warn, 61–90 protect. Nobody gets blocked in month one.
- ✓"In progress, postponed."
The honest status. A postponed item stays visible until someone deals with it.
Which policies work, and which ones people click through.
The Purview portal makes you open each policy to learn this. Here it's one table.
See it in the demo →- ✓Simulation or enforcing, at a glance.
A policy that has been "in test" for eight months is a finding, not a setting.
- ✓Override rate per policy.
5 of 9 blocks skipped. Over a third means the rule is in the wrong place or too broad.
- ✓Microsoft's own scans don't count.
Crawler matches are kept apart from what your people do, so the numbers mean what they say.
Every finding comes with the evidence and the fix.
A specific policy, the numbers behind it, and what to do. Neoview reads by default; someone on your team makes the change in the Microsoft portal.
- 9 items blocked, 5 overridden with a justification
- 1 user accounts for 3 of the 5 overrides
- ✓Evidence from your own audit log.
9 items blocked, 5 overridden, 1 reported as a false positive.
- ✓Read-only by default.
Neoview reads; your team decides. Each suggested action comes written for a person to carry out in the Microsoft portal. Nothing changes in Microsoft Purview unless someone on your team decides it.
- ✓Accept or dismiss, and it's remembered.
What you decided and when becomes part of the record an auditor can see.
Insider Risk Management: 20 licenses, 0 events in 6 days.
What you pay for and don't use.
Your licenses and your activity, side by side, sorted by what each gap costs to close.
- ✓Already paid for. Turn it on.
Example: Insider Risk Management licensed for all 20 users and never used (illustrative). Zero extra cost.
- ✓Paid for half the people.
8 of 28 users have no license, so no DLP, no labels, no retention. Are they still active?
- ✓Needs a better license: none, today.
When there is one, you'll see what it unlocks. We don't sell licenses and we don't show prices.
Work with an MSP?
Neoview runs the same way for the partner who looks after your tenant: one screen for every client, your report with their logo, and nothing changed without a person deciding. How Neoview works for MSPs →
What Neoview reads today, and what's next
We'd rather tell you what isn't there yet than let you find out.
| Area | What we read | Status |
|---|---|---|
| DLP policies and incidents | Every policy across Exchange, SharePoint, OneDrive and Teams, with its real mode (test or enforcing), where it applies, and what it actually caught: matches, blocks, overrides and the justifications people typed. Metadata only, never the content itself. | Available |
| Sensitivity labels | Which labels are published, which ones people actually apply, and which have never been used once. So you know whether "Confidential" means anything in practice. | Available |
| Licenses and capabilities | What every plan in the tenant unlocks (Business Premium, E3, E5, the add-ons), kept current as Microsoft renames things. So "you already pay for this" is always a fact, not a guess. | Available |
| Coverage map, flow map, roadmap | Where data is protected, which rule covers which data, and a 90-day plan whose progress is measured from the tenant itself. All built from daily snapshots, not from a questionnaire. | Available |
| Alerts | Alerts rebuilt from the audit trail, so a spike of overrides or a policy quietly flipped back to test shows up in this week's digest, not in next year's audit. | Available |
| eDiscovery, in plain language | Describe what you need ("everything Maria sent outside the company about Project Obsidian in March") and Neoview drafts the eDiscovery search: the right locations, conditions and date range, ready to review and run in Purview. No KQL to learn. | Next up |
| Audit search, without the syntax | Ask a question ("who changed a DLP policy this quarter?", "which files were shared externally last week?") and get the audit query built and the answer explained, across 13 months of history instead of the portal's 180 days. | Next up |
| Retention labels | Which retention labels and policies exist, what they cover, and the gap between "keep for seven years" on paper and what is actually labeled. | Coming |
| Endpoint DLP | USB, print and upload activity from onboarded devices, so the laptop a file left on is as visible as the mailbox it came from. | Coming |
| Insider Risk Management | Whether a licensed IRM policy exists at all, what it watches, and how many alerts it raises. The capability most E5 tenants pay for and never switch on. | Coming |
Under the hood
- One consent, read-only. A Microsoft Entra application with read permissions to Microsoft Graph and the Office 365 Management Activity API. No admin role, no PowerShell write access, nothing in your tenant to break.
- Daily configuration snapshots, continuous audit activity. Policies, labels, licenses and users are captured once a day; DLP and label events flow in as they happen.
- 13 months of normalized history. A full year of evidence plus the same month a year earlier.
- Redaction at ingest. Detected sensitive values and file contents are never stored; for emails with DLP activity we keep the subject line so you can tell which message was involved. Only the fields needed to count, trend and explain.
- Your data stays yours. Every row is scoped to your tenant, will be held in the United States, and is deleted within 30 days after you disconnect.
- Backfill from day one. If audit logging is already on, Neoview pulls the available history so the first report isn't empty.
Data handling, retention and deletion in detail: Security.
See it on your own tenant.
Thirty minutes, on our demo tenant or on yours. Read-only by default: your team decides every change to Microsoft Purview.