Microsoft Purview
2026-07-30-79f99e65 commercialThe section your link pointed to isn't on Microsoft Purview's page any more, so we've brought you to the top.
Microsoft Purview is a unified data governance platform that discovers, manages, and protects data across cloud and on-premises environments.
Summary
Microsoft Purview is a commercial data-security platform, run as a cloud service within Microsoft 365, that gives organizations a single place to classify sensitive data and enforce loss-prevention policies across apps and networks. It extends data loss prevention to the network layer through integration with Microsoft Entra Internet Access, blocking sensitive uploads to unmanaged cloud and AI apps without third-party proxies, and it can stop Microsoft 365 Copilot from treating external-sender emails as grounding data. It's built for compliance and security teams responsible for insider risk and data governance rather than for individual developers, and its Insider Risk Management view now consolidates agentic alert triage and case notes in one place. Its Data Security Triage Agent, which reasons across user, device, and data signals, has moved from preview to general availability, indicating active, ongoing development.
Microsoft Purview is a unified data governance platform that discovers, manages, and protects data across cloud and on-premises environments.
Microsoft Purview publishes no documentation we track, so the description above is written from general knowledge rather than the vendor's own words.
How Microsoft Purview helps
Which uploads of sensitive data to AI and cloud apps outside IT's control are actually happening on the network?
inspects traffic via the network-layer integration and blocks sensitive uploads to unmanaged cloud and AI apps in real time, without a third-party proxy in the path
Is Copilot pulling in content from senders outside the company when it drafts an answer?
applies a policy that excludes external-sender emails from being referenced, summarized, or used as grounding data, so responses stay anchored to vetted internal content
Which insider-risk alerts need attention right now, and what has already been done about them?
consolidates agentic alert triage, enriched user details, and case notes with combined classic and agent filtering in one view instead of scattered queues
Why did this user, device, or data activity get flagged as risky?
the Data Security Triage Agent runs multi-step reasoning across user, device, and data signals and surfaces the chain of activity behind the alert
Can sensitivity labeling keep up with how much content lands in SharePoint and OneDrive each day?
auto-labeling policies process up to 500,000 files per day per location, so coverage scales with volume rather than stalling behind a lower daily cap
Score card
-
Shipping velocity releases a month, last 12 months
-
Documentation quality release-notes rubric, 0–100
-
Breaking-change discipline how rarely a release breaks users, and notice given
-
Maintenance risk quiet time against its own cadence, maintainers
-
Innovation & surface new capabilities, API and MCP surface
Five scores for Microsoft Purview, each built from the releases, notes and API history this site tracks — and, on Researcher and Business, where it stands among every measured tool in its category and how that has moved.
Score cards are part of every paid plan.
See plans → Already subscribed? Sign in →Trajectory
Blank means never measured; nothing here is a filled-in zero.
Peer standings are included with Researcher and Business. See how this tool ranks against its competitors, using data we don't publish anywhere else.
See plans →Each score is 0–100 on a published rubric, derived from data this site already shows. A dimension we cannot measure says so — it is never scored 0 and never enters a rank.
How this is scored
- Shipping velocity — releases a month over the last 12 months, on a log scale where 16 a month scores 100. Needs 3 releases in the window.
- Documentation quality — the release-notes rubric published on the analytics page, unchanged.
- Breaking-change discipline — the share of releases carrying a breaking change (none scores 100, half or more scores 0). Only projects that label breaking changes are measured: a clean record cannot be told from an unlabelled one.
- Maintenance risk — quiet time measured against the tool's own release cadence (quiet longer than 90 days and three typical gaps scores 0), plus the number of active maintainers and whether contributors are growing, where known. Higher is lower risk.
- Innovation & surface — new capabilities in the feature ledger this year, API and MCP operations added, and the share of commits that are features: the mean of whichever we hold.
- Community health (open-source tools only) — each is a direction, not a size: contributors this year against last, the bus factor now against a year ago, and issues closed per issue opened, where steady scores 50, doubled 100 and halved 0; plus the median time to a maintainer's first reply (an hour scores about 100, a month or more 0). A commercial card has no repository and carries none of the four.
- Documented delivery (commercial tools) — when a vendor's documented new capabilities have slowed against its own baseline, that counts against the overall standing as heavily as two low dimensions. Steady delivery, or too little history to judge, leaves the standing alone; it is never a sixth score.
- Open-source tools are scored on repository signals; commercial tools on their published changelog. Ranks compare tools within one category and one profile and need at least five measured peers; the overall standing needs three ranked dimensions. Best-in-breed or consolidator is a shape, not a quality, and is never scored.
Release-note detail over time
See how much detail Microsoft Purview puts in its release notes, quarter by quarter, and compare it with tracked tools in the same category. This history uses up to ten retained, reviewed notes per tool; sparse or blank older quarters may reflect that limit.
Checking release-note history…
Commercials
pricing & packaging history · Microsoft vendor page16 readings of Microsoft's pricing page since Mar 2022, with 3 relaunches of its plan lineup — each one dated, compared with the reading before it, and explained for someone buying the tool.
Pricing and packaging history is included with Researcher and Business. See how every vendor we track sells, and how that has changed over time, using data we don't publish anywhere else.
See plans → Already subscribed? Sign in →Plans by offering
Each offering on the pricing page links to its own page of plans, read at its latest capture.
Plan relaunches
Plans, prices and descriptions are quoted from the vendor's own pricing page as we read it on each date. A plan missing from a later reading is shown as no longer listed on the page — a statement about the page, not the product. Readings that failed to show any plans are left out rather than read as a change.
Website history
microsoft.com, every changeMicrosoft's home page and 40 more pages as they looked each month from October 2021 to October 2026: 1520 renders, 335 changes of tagline or palette. Step through them, play them, or put any two months side by side.
Website history is included with Researcher and Business.
See plans → Already subscribed? Sign in →← → or h l a month · Shift a year · [ ] previous / next change · Space play · 1 2 3 page · T whole page · C compare · F full size
← → or h l the right month · Shift the left · S swap · W wipe · T whole page · Esc back
Rebranding timeline
Dates bound when a change appeared between captures. Possible rebrands are AI suggestions; a redesign alone does not establish a rebrand.
Releases
3 entries
No entries match these filters.
- September 20261
- August 20261
- July 20261
Add the badge to your README
Maintain this project? The badge links readers straight to this page, so they can follow every release here.