Microsoft Purview is Microsoft’s unified platform for data security, data governance, and data compliance, plus a set of shared capabilities, not a single product and not “just a catalog.” According to Microsoft’s own documentation, Purview is “a comprehensive set of solutions that helps your organization govern, protect, and manage data in the era of AI, wherever your data lives” (Learn about Microsoft Purview, ms.date 2026-05-15). It bundles roughly 15 named sub-products across those three areas, and the data governance piece, Data Map plus Unified Catalog, went generally available on September 1, 2024.
Most explainers shorthand Purview as “bundled into E5.” It isn’t: licensing splits across Microsoft 365 E3, E5, and now E7, several per-feature add-ons, and Azure consumption billing for data governance regardless of tier, exact SKU names, not a generic “it depends.” Microsoft governs the Microsoft-native estate this way; a cross-platform context layer like Atlan covers what it doesn’t reach. Two deeper reads follow: Microsoft Purview Unified Catalog for the Data Map, Unified Catalog, and Information Protection breakdown with pricing, and the coexist, extend, or replace decision for the harder question.
| Field | Content |
|---|---|
| What it is | Microsoft’s unified data security, governance, and compliance platform |
| Three solution areas | Data security, data governance, data compliance, plus shared capabilities (classifiers, connectors, Data/Activity Explorer, sensitivity labels) |
| GA date (data governance) | September 1, 2024 |
| Licensing | Fragmented: Microsoft 365 E3/E5 combinations vary by feature; data governance billed separately as Azure consumption; a new Microsoft 365 E7 + Agent365 tier covers agentic workloads (2026-08-03) |
| Best for | Microsoft 365, Azure, and Fabric-first enterprises standardizing governance, security, and compliance on one vendor |
| Deeper dive | Data Map, Unified Catalog, and Information Protection mechanics plus pricing (see below); the coexist, extend, or replace decision (see below) |
What is Microsoft Purview?
Most searchers don’t know that roughly 15 named sub-products sit underneath Purview’s three solution areas, most unrelated to the catalog function everyone associates with the name. The brand itself is a 2022 consolidation: starting April 19, 2022, Microsoft folded the former Azure Purview and Microsoft 365 Compliance portfolios into one Microsoft Purview name, a change Microsoft announced directly, stating the new brand family “combines the capabilities of the former Azure Purview and the Microsoft 365 Compliance portfolio” (Announcing Microsoft Purview, April 2022), a history top-ranking explainers already cover well.
The three solution areas, and the roughly 15 sub-products each holds, map out like this:
| Solution area | Key named sub-products | What it does |
|---|---|---|
| Data security | Data Loss Prevention, Data Security Investigations, Information Barriers, Information Protection, Insider Risk Management, Privileged Access Management, Microsoft Data Security Posture Management (DSPM, in preview) | Classifies, protects, and investigates sensitive data and insider risk, with DSPM now unifying security posture for both traditional apps and AI apps and agents |
| Data governance | Purview Data Map, Purview Unified Catalog | Scans and stores technical metadata, then curates it into governance domains and data products |
| Data compliance | Audit, Communication Compliance, Compliance Manager, Data Lifecycle Management, eDiscovery, Records Management | Manages retention, legal discovery, regulatory compliance, and communication risk |
| Shared capabilities | Classifiers, connectors, Data/Activity Explorer, sensitivity labels | Cross-cutting infrastructure the three solution areas draw on |
Data security
Data security spans Data Loss Prevention, Data Security Investigations, Information Barriers, Information Protection, Insider Risk Management, and Privileged Access Management, plus Microsoft Data Security Posture Management, now in preview and unifying security for traditional and AI applications alike (Learn about Microsoft Purview). It covers the most ground here: data an employee might mishandle, data an agent might now touch.
Data governance
Data governance holds two products: Purview Data Map and Purview Unified Catalog (Microsoft Purview data governance overview). The Data Map scans and stores technical metadata; Unified Catalog curates it into governance domains and data products. The full breakdown, including exact pricing, lives on Microsoft Purview Unified Catalog: Features, Pricing & Limits, which also covers what counts as a governed asset and what Purview’s REST API reaches. That’s the catalog deep dive; what a context layer is is a different question entirely.
Data compliance
Data compliance covers Audit, Communication Compliance, Compliance Manager, Data Lifecycle Management, eDiscovery, and Records Management. One line each is enough: Audit tracks activity across Microsoft 365; Communication Compliance screens messages for policy violations; Compliance Manager scores regulatory readiness; Data Lifecycle Management and Records Management handle retention and disposition; eDiscovery supports legal hold and search.
Governance and compliance sound adjacent, but they’re licensed, billed, and operated as separate products inside the same brand. A team building an enterprise context layer on a Microsoft estate has to understand this split, including the audience the context layer for data governance teams serves. The broader evaluation lens sits in 20 questions for evaluating a Fabric governance platform. Microsoft bundled three jobs under one name; evaluating “Purview” means evaluating three roadmaps, not one.
How is Microsoft Purview licensed?
Purview licensing is fragmented across several Microsoft 365 tiers and a separate Azure consumption model, not one bundle, the single most common mistake in third-party explainers. Microsoft’s own service description lists separate required-license combinations per feature: Microsoft 365 E5, A5, or G5 for the Defender Suite; the same E5/A5/F5/G5 set for Information Protection and Governance, for eDiscovery and Audit, and again for Insider Risk Management; and Office 365 E5, A5, or G5 for other capabilities (Microsoft Purview service description, ms.date 2026-08-03, updated 2026-08-21). There’s no single SKU that turns on all of “Purview.”
Data governance, meaning the Data Map and Unified Catalog together, runs on a separate pay-as-you-go Azure consumption model tied to a linked Azure subscription and resource group, independent of which Microsoft 365 license the organization holds (Billing in Microsoft Purview Data Governance, ms.date 2026-04-24). Information Protection is a separately billed sibling, largely bundled into Microsoft 365 E5 or an E3 add-on: two different bills on two different billing systems, inside the same brand.
| Capability area | Required license(s) | Billing model |
|---|---|---|
| Information Protection and Governance | Microsoft 365 E5/A5/F5/G5 | Per-seat, Microsoft 365 |
| eDiscovery and Audit | Microsoft 365 E5/A5/G5/F5 | Per-seat, Microsoft 365 |
| Insider Risk Management | Microsoft 365 E5/A5/G5/F5 | Per-seat, Microsoft 365 |
| Data governance (Data Map + Unified Catalog) | Any Microsoft 365 tier; separate Azure subscription required | Azure consumption, regardless of Microsoft 365 tier |
| Agentic-workload security and compliance | Microsoft 365 E7 + Agent365 | Per-seat, new tier |
A fact current as of the 2026-08-03 update, one no ranking competitor page mentions yet: Microsoft’s service description states plainly that “Microsoft Purview security and compliance capabilities for agents on Microsoft Foundry and Entra-connected AI apps will be supported by Microsoft 365 E7 and Agent365 SKUs” (same source, “Microsoft Purview for agentic workloads” section).
The new agentic-workloads tier
The E7 plus Agent365 combination is scoped specifically to agent security and compliance on Microsoft Foundry and Entra-connected AI applications. What it doesn’t do, per Microsoft’s own service description, is extend Purview’s reach to agents or applications outside the Microsoft ecosystem. For the specific controls this tier adds, see What are Microsoft Purview’s controls for AI agents? Weighing this tier’s cost against the rest of an AI stack is the same math covered in Context layer total cost of ownership: build vs buy vs bundle, with the fuller checklist in Context layer evaluation criteria.
The licensing fragmentation isn’t a flaw to exploit. It’s the reality a Microsoft-first team plans around before any governance rollout; getting the SKU math wrong early is a more common failure than any Purview limitation.
Who is Microsoft Purview built for?
Microsoft Purview is built for Microsoft 365, Azure, and Fabric-first enterprises standardizing governance, security, and compliance on the vendor they already run most of their estate through. That’s narrower than “any enterprise needing governance,” grounded in the solution areas named above, not a generic persona list.
Microsoft 365 and Azure-centric enterprises needing unified compliance and DLP
Organizations already licensed into Microsoft 365 E5 get sensitivity labels, DLP, and Information Protection that travel with data across SharePoint, Exchange, Teams, and OneDrive without separate configuration. For a team already paying for that tier, turning these on costs little extra.
Fabric-first analytics teams governing OneLake-scale estates
Teams running analytics primarily through Microsoft Fabric get Purview’s organization-wide DLP, sensitivity labels, and compliance scanning layered on top of Fabric’s own governance, instead of bolting a separate product onto OneLake. Teams comparing catalog options for that estate specifically can see Best data catalogs for Microsoft Fabric.
Regulated industries consolidating eDiscovery and records management under one vendor
Industries with heavy legal hold, audit, and retention requirements can consolidate eDiscovery, Records Management, and Compliance Manager under one vendor instead of stitching together point solutions per function.
“Embracing Microsoft Purview Data Governance has been a game-changer for Vanderlande. As a preview customer over the past 18 months, we’ve witnessed Microsoft Purview’s remarkable growth and the eagerness of Microsoft to bring a state-of-the-art governance solution to the market,” said Geert-Jan Verdonk, Data Governance Lead at Vanderlande, in Microsoft’s own general-availability announcement (Microsoft Security blog, 2024). It’s a real, fully credentialed quote, but it’s Microsoft’s own GA-announcement voice, not an independent practitioner account.
None of these three profiles require replacing anything. They describe when Purview alone is a coherent answer for governance, security, and compliance, a separate question from whether that estate needs role-based access control for AI agents, or how to govern AI agents across multiple clouds when the estate isn’t entirely Microsoft.
How does Microsoft Purview fit a Microsoft-first estate?
Fitting a Microsoft-first estate well is a separate axis from fitting the agent scenarios that estate is increasingly building toward. Purview layers organization-wide governance on top of Fabric and the broader Microsoft 365 and Azure estate; Copilot and agent scenarios are where that estate is heading next. Where Purview sits relative to Fabric, and where it stops, matters more now that agents read from both.
Where Purview sits alongside Fabric governance
Fabric governs natively through its own OneLake catalog, covering discovery, governance insights, recommended actions, domains, endorsement, and lineage across a Fabric tenant (Microsoft Purview and Microsoft Fabric, ms.date 2026-08-26). Microsoft’s own framing is explicit about the division of labor: Purview adds protection, audit, risk, and compliance coverage “when your security, risk, and compliance needs extend beyond Fabric,” not a replacement for Fabric’s built-in governance (same source). In practice that means information protection and sensitivity labels, DLP, audit logging, insider risk management, and governance for Fabric Copilots and agents, layered on top of what Fabric already does natively; Microsoft Fabric Governance: What’s Built In and What You Add covers Atlan’s own read of that split in more depth. Fabric handles the estate it scopes; Purview handles the policy layer that spans beyond any single Fabric workspace.
Where agent grounding actually lives
Purview governs the estate. Agent grounding, meaning giving a Copilot or Fabric data agent the ontology and semantic model it reasons from, lives in a separate Microsoft product: Fabric IQ (Fabric IQ overview). That’s not a criticism of Purview; it’s an architectural fact worth knowing before assuming governance and grounding are the same job. What is Fabric IQ? covers that layer in full, and What are Fabric data agents? covers what those agents do once grounded.
The same split shows up wherever Microsoft builds agent infrastructure. Azure AI Foundry is where teams build agents from scratch, with a practical path in How to build an agent with Azure AI Foundry and reusable patterns in Azure AI Foundry agent blueprints. Microsoft’s Agent Framework sits underneath much of that tooling, and Microsoft Copilot Studio agents are the lower-code path to the same goal. For the broader oversight questions this raises, see What questions should you ask about governing Fabric AI agents? None of these answer Purview’s governance question, and Purview doesn’t answer theirs. A Microsoft-first estate invests in both halves at once, which is why conflating them is the mistake worth avoiding.
Purview is a strong, actively invested-in answer for the governance, security, and compliance half of a Microsoft-first estate. It was never built to answer the grounding half, and an estate that assumes one product covers both ends up discovering the gap only after an agent ships.
Where does Microsoft Purview’s coverage stop?
Purview’s enforcement reach is narrower than its scanning reach, a distinction Microsoft’s own documentation states plainly. The Data Map registers sources well beyond Microsoft’s own stack, but what it can scan and what it can enforce policy on are different questions, and that gap is where most coverage confusion starts.
Microsoft’s own scope statement draws the boundary directly: “All data in Data Map and Unified Catalog is metadata, not the underlying data itself” (Microsoft Purview data governance overview, ms.date 2025-02-19, updated 2025-11-18). That’s a statement about scope, not a shortcoming. The full breakdown of which non-Microsoft sources Purview can register versus enforce on lives on What Microsoft Purview’s data governance covers, and where it stops, built to answer that question in depth.
Real, independently documented friction exists too, and shouldn’t be glossed over. On Reddit’s r/MicrosoftFabric, one practitioner put it bluntly: “Honestly, Purview is quite expensive, particularly considering its functionality (or lack thereof)” (thread, March 2025). Another, months later, found it “far more hands-on than Microsoft suggests, but the payoff is worth it” (thread, November 2025). A third-party review frames it more structurally: Purview is “designed to do” specific jobs well inside the Microsoft estate, and the honest read is knowing which jobs those are, not assuming universal coverage (Cloudficient: Microsoft Purview, What It Is (and Isn’t) Designed to Do).
None of this is a Microsoft-only problem. The same question, what a hyperscaler’s native catalog can observe versus enforce outside its own cloud, shows up again in Google Knowledge Catalog vs. neutral catalog for BigQuery, for a different platform. Why enforcement stops at the cloud boundary instead of following the data wherever it goes is covered in Multi-cloud context layer.
Knowing where coverage stops isn’t an argument for replacing Purview. It’s the fact a Microsoft-first team needs before deciding what else, if anything, has to sit alongside it for the parts of the estate Purview was never built to reach.
How does Microsoft Purview relate to a cross-platform context layer?
Microsoft Purview is genuinely broad and actively invested in: three solution areas, roughly 15 sub-products, DSPM for AI in preview, and a new E7-plus-Agent365 tier, documentation updated as recently as 2026-08-21. This isn’t a product in decline; treating it as one would ignore real Microsoft investment. Whether to replace any part of it is a separate question, taken up below.
Architecturally, Purview governs the Microsoft-native estate: Azure, Fabric, and Microsoft 365. Atlan is the Context Layer for AI across the rest of the stack, Snowflake, Databricks, dbt, Tableau, plus a business-friendly, AI-ready layer on top. The split shows up in concrete contrasts: Atlan connects to 100-plus systems spanning Microsoft and non-Microsoft platforms, where Purview’s depth is Microsoft-native; Atlan maintains automated column-level lineage across systems, where Purview’s lineage runs column-level only inside Azure; and Atlan embeds context directly into tools people already use, Slack, Teams, BI tools, Excel, where Purview’s metadata stays inside the Purview portal. What is context engineering? covers what that layer does, What is a context layer for AI agents? is the fuller architectural picture, and What is a context graph? covers the structure it’s built on. Context layer vs knowledge graph and Model-agnostic context layer go deeper on those architectural choices.
| Dimension | Microsoft Purview | Enterprise context layer |
|---|---|---|
| What it is | Unified Microsoft-native governance, security, and compliance platform | A neutral layer holding agreed definitions, lineage, and context across platforms |
| Connector breadth | Microsoft-native depth, with multicloud registration via the Data Map | 100+ connectors spanning Microsoft and non-Microsoft systems |
| Lineage | Column-level inside Azure; table-level or absent outside it | Automated column-level lineage across systems |
| Where context lives | Inside the Purview portal | Embedded in Slack, Teams, BI tools, Excel, and wherever work happens |
| Enforcement reach | Azure-only policy enforcement | Context served to any agent vendor, across clouds |
According to Atlan’s AI Labs benchmark, agents grounded in governed context show 38% higher text-to-SQL accuracy than agents working from raw schema alone. Pulling that context together is covered in how to implement an enterprise context layer for AI, with the architecture in how do you build a context layer reference architecture. Whether that layer sits on one vendor’s stack or stays neutral is what single-stack lock-in vs. neutral context layer works through; why business-readable context matters for agents is in business context for AI.
Whether to coexist, extend, or fully replace Purview for a given workload is its own question, worth answering on its own terms rather than folded into a plain definitional answer.
Microsoft Purview is broader, and more fragmented, than it looks
Microsoft Purview is three solution areas and roughly 15 sub-products wearing one brand name, not a free catalog bundled into E5. The licensing reality, Microsoft 365 E3, E5, and now E7 with Agent365, plus Azure consumption billing for data governance, is more fragmented than most explainers admit, and getting it wrong early is the most common planning mistake. It’s also a strong, actively invested-in answer for Microsoft, Azure, and Fabric-first estates, with real friction, cost surprises and hands-on setup among them, worth acknowledging rather than glossing over.
For the Data Map, Unified Catalog, and Information Protection breakdown with exact pricing, see Microsoft Purview Unified Catalog: Features, Pricing & Limits, linked above. For the sharper decision on what to do about it, see Should you coexist, extend, or replace Microsoft Purview? Teams specifically comparing Purview against other governance and catalog tools can start with Microsoft Purview alternatives.
FAQs about Microsoft Purview
1. What is Microsoft Purview?
Microsoft Purview is Microsoft’s unified platform spanning three solution areas, data security, data governance, and data compliance, plus shared capabilities like classifiers and sensitivity labels. It bundles roughly 15 named sub-products, not a single tool.
2. What is Microsoft Purview used for?
Purview is used for unified governance, security, and compliance across on-premises, multicloud, and SaaS estates: DLP, insider risk management, cataloging via the Data Map and Unified Catalog, audit, eDiscovery, and records management, all under one brand.
3. Is Microsoft Purview part of Azure?
Purview is a Microsoft 365 and Azure product, not Azure-only. Data governance specifically, the Data Map and Unified Catalog, bills as Azure consumption regardless of Microsoft 365 tier, while Information Protection and other capabilities are licensed through Microsoft 365.
4. What is the difference between Azure Purview and Microsoft Purview?
Azure Purview was the product’s name before 2022. Microsoft consolidated it with the former Microsoft 365 Compliance portfolio under one new brand, Microsoft Purview, the name and scope it carries today.
5. What are the three main areas of Microsoft Purview?
The three solution areas are data security, data governance, and data compliance, plus shared capabilities like classifiers, connectors, and sensitivity labels that all three draw on.
6. Is Microsoft Purview a data catalog?
No. Unified Catalog, inside the data governance area, is a data catalog. Microsoft Purview as a whole is a much broader platform covering security and compliance functions unrelated to cataloging.
7. How much does Microsoft Purview cost?
There’s no single number: licensing spans Microsoft 365 E3, E5, and E7 tiers plus separate Azure consumption billing for data governance. Exact Unified Catalog pricing, including per-governed-asset rates, is in Atlan’s dedicated Purview Unified Catalog pricing breakdown.
8. Is Microsoft Purview a DLP (data loss prevention) tool?
DLP is one capability inside Purview’s data security solution area, not the whole product. Purview also covers insider risk management, information protection, data governance, and compliance, all entirely separate from DLP.
Sources
- Learn about Microsoft Purview
- Microsoft Purview service description
- Microsoft Purview Data Governance general availability announcement, 2024
- Microsoft Purview data governance overview
- Billing in Microsoft Purview Data Governance
- Microsoft Purview and Microsoft Fabric
- Fabric IQ overview
- Cloudficient: Microsoft Purview, What It Is (and Isn’t) Designed to Do
- Reddit r/MicrosoftFabric: Purview for catalog and what does Purview cost?
- Reddit r/MicrosoftFabric: Anyone using Purview for Data catalog?
- Announcing Microsoft Purview (Microsoft TechCommunity, April 2022)
