Microsoft Purview Unified Catalog: Features, Pricing & Limits

“Microsoft Purview” names three solution areas, and only one is a catalog. Data governance holds two products: the Purview Data Map, and Purview Unified Catalog, the curation layer over it where an asset’s governance state lives (Purview overview, ms.date 2026-05-15). Atlan builds a different layer, the enterprise context layer; the useful fact is that Microsoft already split those two jobs inside its own stack.

The conference for teams teaching AI their business

October 28 / 11 AM ET / Virtual. Join the leaders and builders defining the context layer, the missing infrastructure of the AI era.

Save Your Spot →

Agent grounding went to Fabric IQ, part of Microsoft IQ, “a set of capabilities that form the enterprise intelligence layer of the Microsoft stack,” whose two core items are an ontology (preview) and a Power BI semantic model (Fabric IQ overview, ms.date 2026-07-08, updated 2026-08-31). Purview appears nowhere in that document. The live question on an Azure estate is which layer answers when an agent asks what a metric means, and what happens to governed context on the way out, the other half of what a context layer is.

Check Your Catalog’s AI Readiness

Give it the catalog’s own docs. It checks the agent interface, the enforcement boundary, and whether a definition survives a rename. Read the skill.

Paste into a new chat

Use the skill at https://atlan.com/skills/catalog-ai-readiness-check.md to check whether our data catalog is ready for AI agents. Ask me for whatever it needs.

Run once in a terminal

curl -fsSL --create-dirs \
  -o ~/.agents/skills/catalog-ai-readiness-check/SKILL.md \
  https://atlan.com/skills/catalog-ai-readiness-check.md

For an agent

curl -fsSL https://atlan.com/skills/catalog-ai-readiness-check.md

Human Agent ClaudeChatGPTGeminiCursorOther Copy

What is Microsoft Purview Unified Catalog, and what does it govern?

Microsoft’s definition: “Unified Catalog is a searchable catalog of your scanned data where you curate, grant access to, and improve the health of your data. The catalog is a software as a service (SaaS) experience based on a single-tenant model” (data governance overview, ms.date 2025-02-19, updated 2025-11-18). Microsoft’s data governance solution went generally available on September 1, 2024, announced by Rohan Kumar, Corporate Vice President, Microsoft Security Platform, Microsoft Purview and Microsoft Priva (Microsoft Security blog, 2024). The blog announces the whole solution by that name, not Unified Catalog specifically. Microsoft scopes what sits inside either product in one sentence: “All data in Data Map and Unified Catalog is metadata, not the underlying data itself. None of the permissions or roles in Data Map or Unified Catalog provide access to underlying data itself.”

Its scope is precisely bounded, because every object inside it is a governance object and none of them is the data. Governance domains hold data products, terms, OKRs and critical data elements (governance domains, 2024-04-08 / 2025-11-18). Data products group assets under owners, a use case, a terms-of-use attestation and one access policy (data products, 2024-04-08 / 2025-11-18); that attestation is a weaker object than a data contract for AI. Glossary terms do more than define. Microsoft calls them “active values that provide context” that “also apply policies,” propagating to whatever the term lands on (glossary terms, ms.date 2026-04-24). All of it is curated above the Data Map, roughly the seam between the types of metadata for AI agents.

Then critical data elements, which reconcile columns into one concept, mapping CustID and CID into a single “Customer ID” container (critical data elements, 2026-04-20 / 2026-09-05). That page has read Preview for over two years. The object carrying the most semantic weight in the product is the object a programmatic interface cannot read yet.

Which capabilities carry a status label

The 2026 Data Governance entries in Microsoft’s release notes are updates, not GA announcements. Since August 2026, Purview data quality needs the account and its data sources in the same Azure region, and since July 2026 Purview protection policies no longer support Azure SQL Database (what’s new, ms.date 2026-08-26, updated 2026-09-16). Preview covers critical data elements, governed-assets semantic search and term-to-column linking (data assets search, 2026-09-08), natural language product search (data products search, ms.date 2026-05-21), and live view (live view, 2024-05-22 / 2025-11-18). The REST API is Public Preview (API overview, 2026-04-30). Governance domains, data products, glossary terms, OKRs, access policies and health controls carry no stage label at all (unified catalog, 2024-08-28 / 2026-03-16): no Microsoft sentence asserts GA or Preview for them, checked 2026-09-16, so read them as shipped, not GA-claimed.

What Purview can scan, and what it can apply a policy to

The Data Map registers Snowflake, Amazon S3, Amazon Redshift, Google BigQuery, Oracle, Teradata, SAP S/4HANA, Salesforce, Tableau and Looker, among others (data map data sources, ms.date 2026-07-01). That is a multicloud observation surface on Microsoft’s own list, a starting point for any multi-cloud context layer argument. Register is the right verb, because the same grid varies the capability by source: automatic classification reads Yes for Snowflake, Oracle, Teradata and Amazon S3, and No for Redshift, BigQuery, Salesforce, Tableau and Looker, while SAP S/4HANA and Looker sit under services and apps with lineage only.

The policies column down all four tables in that doc says Yes for Azure multiple sources, Blob Storage (preview), ADLS Gen2 (preview), Azure SQL Database, SQL Managed Instance and SQL Server on Azure Arc. Zero non-Microsoft sources. Unified Catalog’s access policies are a request-and-approval workflow on a data product, a different mechanism from enforcement at the engine, the gap that separates observing an estate from governing AI agents across multiple clouds. Its table-level read of Unity Catalog is covered in Purview versus Databricks Unity Catalog.

What’s the difference between Purview Data Map, Unified Catalog and Information Protection?

“Microsoft Purview” spans three separately licensed solution areas, and a team evaluating “Purview” as one line item is really evaluating three. Microsoft markets all three under a single umbrella brand, even though each ships, prices and renews on its own schedule. The Data Map scans sources and stores their technical metadata: schema, classifications, lineage. Unified Catalog curates that scanned metadata into governance domains, data products and quality scores, the software-as-a-service curation layer over the Data Map.

Information Protection is the third leg, and it is a genuinely different product with a genuinely different bill. Microsoft’s own description: Information Protection helps organizations “discover, classify, and protect sensitive information wherever it lives or travels,” covering sensitivity labels, encryption including Double Key Encryption and Message Encryption, and data loss prevention that reaches endpoint devices, the Chrome browser through a dedicated extension, and Teams chat and channel messages (Microsoft Purview Information Protection, ms.date 2026-02-26, updated 2026-06-25). Microsoft draws its own boundary rather than leaving it implied: the same page points readers elsewhere “for information about governing your data for compliance or regulatory requirements.”

Information Protection is a sibling of Data Governance, not a subset folded inside it, per how Microsoft’s own service description licenses and scopes the two areas separately (Microsoft Purview service description, ms.date 2026-08-03). The two layers still touch: Information Protection can auto-label Data Map assets, including files in Azure Data Lake Storage and Azure Files and schematized columns in Azure SQL Database and Cosmos DB, so a sensitivity label can attach directly to a Data Map asset. But the governance state Unified Catalog curates, which domain owns an asset, which data product it belongs to, its quality score, is a different object from a sensitivity classification, and the pillar page’s own phrasing already covers the capability without a fourth term: sensitivity labels and DLP policies are “configured centrally in Purview and applied across Fabric workspaces.”

Three products, three separate bills, on two different billing systems: Data Governance runs on Azure consumption regardless of Microsoft 365 tier, Information Protection largely rides the Microsoft 365 seat a tenant already has. Whether that split changes the calculation on paying for a dedicated context layer alongside Purview is the comparison run in Purview alternatives.

Where did Microsoft put the layer an agent reads?

Fabric IQ “provides structured grounding for copilots and agents, so answers reflect your enterprise language as defined in your ontology (preview),” and Unified Catalog is not on that path. That puts two artifacts most teams govern least at the center of agent reasoning: an ontology in preview, where ontology design for AI starts deciding answers, and a modelling surface built for reporting, the substance of Power BI semantic model versus a dedicated semantic layer.

Microsoft documents six Purview applications for Fabric, and Unified Catalog is the first of them: live view, same-tenant and cross-tenant connection, and publication workflows for data products and glossary terms. The sixth is governance over the agent itself, “risk discovery in prompts and responses, audit coverage for AI interactions, and retention and eDiscovery applicability to AI-generated content” (Microsoft Purview and Fabric, ms.date 2026-02-09, updated 2026-05-11). Both are real jobs, and both are different from supplying business meaning, whether that meaning is built in Azure AI Foundry or via Microsoft Copilot Studio agents. The same page also loosens the governed-asset frame in one direction: “Data quality checks can be applied to ungoverned assets, including Fabric data, even when those assets aren’t linked to data products.”

So whatever Unified Catalog knows has to leave the portal first. The REST API covers eight object types and “only covers the Unified Catalog features that are available in General Availability (GA)” (API overview, 2026-04-30), which leaves out critical data elements, search by meaning and term-to-column linking. Microsoft states that boundary itself rather than leaving it to be inferred, and it is the sharper fact: the way out is a preview API scoped to GA objects. Whether that is the right shape for an agent is the trade in why MCP matters for AI agents and when to use MCP versus an API.

The bulk way out is the finding. Microsoft’s own note on the self-serve analytics export:

“The Catalog implements role-based access control (RBAC), ensuring that not all users can view all domains or data products. However, for self-serve analytics, Purview publishes all data, allowing anyone with access to this data to view the entire catalog.”

Only part of the estate travels, because “Purview only publishes governed assets data” (self-serve analytics, ms.date 2026-06-23), and known issue 10 logs the same RBAC behavior (known issues, ms.date 2026-04-15). Governed context either stays inside the portal, or it reaches the agent surface with the permission model that made it trustworthy removed. That is why context layer role-based access control belongs at the front of a retrieval-path conversation. One more bound, stated on the critical data elements page rather than as a platform-wide service level: “metadata changes are reflected in Unified Catalog within 24 hours” (critical data elements, 2026-09-05). Whether the agent reading that data product knows it holds a day-old record is context drift nobody is instrumenting.

What does Unified Catalog cost, and what do its instruments measure?

Scanning is effectively free once you are on pay-as-you-go, and two meters carry the rest. Unified Catalog charges $0.0165 per governed asset per day on Standard, about $0.50 a month. Enterprise Data Management runs on Data Governance Processing Units, one DGPU equal to 60 minutes of managed compute, at $15 Basic, $60 Standard and $240 Advanced; the Data Map’s Advanced Resource Set bills $0.21 per vCore hour (Microsoft Purview pricing, Data Governance tab, East US, USD, read 2026-09-30). Managed assets are priced uniformly across regions and prorated by days governed.

A free version of the Purview portal exists, but Microsoft scopes it to “a subset of applications and sources”; production-scale governance almost always means upgrading to the Enterprise version, which is unconditionally pay-as-you-go and requires its own linked Azure subscription (Upgrade to Enterprise Microsoft Purview Data Governance, ms.date 2025-05-01, updated 2025-11-18).

The first meter runs on an unusual definition: “A governed asset is a data asset that you attach or associate to governance concepts, such as data products, critical data elements, glossary terms, and data quality. If you don’t associate a technical asset to a governance concept, it isn’t a governed asset” (data governance billing, ms.date 2026-04-24). Microsoft’s worked example: 500 assets in the Data Map with only 200 governed costs $100 a month over 30 days, because “the 300 assets that aren’t linked to governance concepts aren’t considered governed assets and therefore not counted.”

There’s no volume discount today: Microsoft’s own billing FAQ states the team “can work on volume-based pricing for future releases,” so pricing at scale is still the per-asset rate times the count, not a lower blended one (data governance billing FAQ, ms.date 2026-02-13). The processing meter works the same way on activity rather than inventory.

So the coverage instrument is the billing dimension itself, not a number a marketing team picked. The health scoreboard works the same way from the other side: twelve out-of-the-box health controls ship in six groupings, ten of them scored as a percentage of data products, and Microsoft’s limitation line is verbatim: “Currently, you can’t create custom controls” (controls, 2025-07-27 / 2025-11-18). The other two count differently: compliant data use is a percentage of data subscriptions, and critical data identification is a percentage of business domains with at least one critical data element. Owners can still edit thresholds, activate or deactivate a control, add rules and schedule a refresh. Traditional catalogs were measured by coverage. A catalog built for agents gets measured by answers.

One hundred characters satisfies that control whether or not an agent could answer anything from the description, and neither instrument has a place to record an answer. That is a statement about what a metric can see, not about Microsoft’s engineering. Reading outcomes instead of percentages is where business context for AI starts to matter, and whether the bundled trade is right is the comparison run in context layer TCO.

Purview supplies context automatically and serves it collaboratively, with a steward curating after the scan. A catalog built for agents needs Context Agents creating context from evidence, a Context Lakehouse storing and vectorizing it, consumption over MCP, SQL and APIs, and a learning loop that finds the gaps. Vectorization is the difference between an MCP-connected data catalog and a portal with a search box, between semantic search and keyword search.

What are the best practices for Unified Catalog?

Because the service sits in the Azure tenant and gets switched on rather than installed, teams often start with nothing in mind: scan every source, hand out access, and watch the catalog fill with thousands of assets nobody asked for. Seven practices keep that from happening.

1. Start with one question worth answering. Pick a decision the business already cares about, then work backward to the sources that serve it. This is the same discipline that separates a working context layer reference architecture from an inventory.
2. Design governance domains before you scan. Domains can follow business areas such as HR or finance, subject areas such as product or party, or regulatory boundaries such as SOX, PCI and anti-money laundering.
3. Name a real owner per domain. Every domain needs a single decision authority for the data consumed inside it, not a shared inbox. Ownership is the field that decays fastest and the one tribal knowledge quietly replaces.
4. Govern selectively, not exhaustively. Assets in the Data Map that are not linked to a data product or critical data element are not counted as governed assets and are not billed, which makes selective linkage a governance decision and a cost decision at once.
5. Profile before you write rules. Run data profiling first, then base quality rules on what the profile actually shows rather than what the schema implies.
6. Treat health actions as a backlog. Work the action list in priority order rather than chasing a single composite score, because a composite score can improve while the thing you care about gets worse.
7. Publish deliberately. A domain and its products should go live only once descriptions, terms and access policies are in place.

How do you get started with Unified Catalog?

1. Confirm prerequisites. You need a Microsoft Purview Enterprise instance, either by upgrading an existing account to the new experience or upgrading from the free version, plus data sources registered and scanned in the Data Map.
2. Assign the Data Governance Administrator role. This role delegates the first level of access for Unified Catalog users and is the recommended first step.
3. Build your first governance domain. Assign a domain creator, create at least one domain, then assign a domain owner to it.
4. Register and scan sources. Capture metadata in the Data Map so assets are available to link.
5. Create data products. Assign product owners who understand both the data and the business scenario, then publish at least one product per domain.
6. Grant catalog reader permissions. Consumers cannot browse or request access until they have reader rights in the domain.
7. Layer in terms, OKRs and quality. Add glossary terms, link OKRs to products, then assign a data quality steward to configure connections, profiling and rules.
8. Review controls and act. Baseline your health controls, then work the health actions list.

Billing is pay-as-you-go and requires an Azure subscription and resource group in the same tenant. Step 7 is where most estates stall, because glossary terms are cheap to create and expensive to reconcile once two domains define the same word differently, the problem Active Ontology exists to solve across systems rather than inside one.

When is Purview Unified Catalog the right answer on its own?

There is a clear condition under which Unified Catalog plus Fabric IQ covers what a team needs. If the estate is Azure, Fabric and Power BI, the agent surface is Copilot and Fabric data agents, no definition has to hold outside what Microsoft observes, and the governed slice is the slice that matters, then Microsoft’s two products are a coherent answer. The per-asset price is low, scanning is free, and the health controls are sensible. The data quality engine is real and maturing fast, and the access-request workflow solves a problem most teams have. Microsoft is candid about its own preview AI too: the application card publishes the scope limits, the language constraints and a requirement that “Human oversight is required before operational use” (application card, ms.date 2026-06-01). For the rest of the portfolio, there is Microsoft data governance tools, and for evaluation criteria in that market, Purview alternatives.

What changes the answer is a condition, not a verdict. A second agent vendor in the building. A source Purview can register but cannot enforce on. One definition that has to resolve identically in two places. Any of those turns the question into the single-stack lock-in versus neutral context layer decision: governing an agent and supplying it context are separate jobs, a split also written up for Google Knowledge Catalog.

Real customers, real stories: Modern data catalog in action

53 % less engineering workload and 20 % higher data-user satisfaction

"Kiwi.com has transformed its data governance by consolidating thousands of data assets into 58 discoverable data products using Atlan. 'Atlan reduced our central engineering workload by 53 % and improved data user satisfaction by 20 %,' Kiwi.com shared. Atlan's intuitive interface streamlines access to essential information like ownership, contracts, and data quality issues, driving efficient governance across teams."

Data Team

Kiwi.com

🎧 Listen to podcast: How Kiwi.com Unified Its Stack with Atlan

One trusted home for every KPI and dashboard

"Contentsquare relies on Atlan to power its data governance and support Business Intelligence efforts. Otavio Leite Bastos, Global Data Governance Lead, explained, 'Atlan is the home for every KPI and dashboard, making data simple and trustworthy.' With Atlan's integration with Monte Carlo, Contentsquare has improved data quality communication across stakeholders, ensuring effective governance across their entire data estate."

Otavio Leite Bastos, Global Data Governance Lead

Contentsquare

🎧 Listen to podcast: Contentsquare's Data Renaissance with Atlan

How do Unified Catalog and an enterprise context layer divide authority?

The line worth drawing runs per class of context. The Data Map is authoritative for schema, scan results and classification; invert that and a stale copy of the schema drives a query plan. Unified Catalog is authoritative for the governance state of a governed asset and for enforcement on Azure sources; invert that and approval and quality state diverge from the workflow that produced them. An enterprise context layer is authoritative for the reconciled definition of a metric and the accountable owner, serving all of it to any agent vendor with the access model intact.

Microsoft’s docs already say what goes wrong when nobody sets the rule: a curated record can lag the Data Map by up to 24 hours, the bulk export drops RBAC, and nothing alerts when two layers hold the same term with different meanings. So decide the precedence rule per object, set a reconciliation cadence, and name an owner. Authority, not connector counts, is where context layer evaluation criteria should start, and why a model-agnostic context layer is a design decision rather than a slogan. The operating version lives in the context layer for data governance teams.

Atlan is the Context Layer for AI. It holds the class of context no cloud platform observes: the definition two teams argued their way to, the approval that happened in a review meeting, the named human accountable when the number turns out wrong. Atlan AI Labs found that agents grounded in governance metadata achieve 38% higher SQL accuracy than agents working from raw schema alone.

Microsoft’s authority is real, cheap to run, precisely bounded, and published with dates on it. It just put agent grounding in a different product and doc set with no bridging document, so the handoff between its two layers is where the decision lives. Sequencing is the next problem: how to implement an enterprise context layer for AI. When a Copilot agent and a Claude agent both ask what a metric means, which layer answered, and did anyone choose that.

FAQs about Microsoft Purview Unified Catalog

1. What is Microsoft Purview Unified Catalog?

Microsoft Purview Unified Catalog is the SaaS curation and discovery experience on top of the Purview Data Map, based on a single-tenant model. Microsoft describes it as “a searchable catalog of your scanned data where you curate, grant access to, and improve the health of your data.” It is where an asset’s governance state lives: its governance domain, data product, glossary terms and quality score.

2. What is the difference between Purview Data Map and Unified Catalog?

The Data Map scans sources and stores technical metadata: schema, classifications and lineage. Unified Catalog curates governance concepts on top of it: domains, data products, terms and quality scores. Changes reflect within 24 hours.

3. What counts as a governed asset in Microsoft Purview?

A governed asset is one attached to a governance concept: a data product, a critical data element, a glossary term, or data quality. Assets collected but never linked to a concept are not governed, and are not billed. Microsoft’s example bills 200 out of 500.

4. Which parts of Unified Catalog are generally available and which are in Preview?

Critical data elements, natural language search, semantic search, term-to-column linking and live view carry Microsoft’s Preview label, as does the REST API. Governance domains, data products and terms ship with no stage label at all. The 2026 Data Governance entries in Microsoft’s what’s-new page are updates, not GA announcements: an August 2026 note that data quality requires the account and its sources in the same Azure region, and a July 2026 note that protection policies no longer support Azure SQL Database.

5. Can Microsoft Purview catalog non-Microsoft sources like Snowflake and BigQuery?

Yes. The Data Map registers Snowflake, Amazon S3, Redshift, BigQuery, Oracle, Teradata, SAP, Salesforce, Tableau and Looker, so Purview is not Microsoft-only. Capability varies by source: automatic classification is supported for Snowflake, Oracle, Teradata and Amazon S3, and not for Redshift, BigQuery, Salesforce, Tableau, Looker or SAP S/4HANA. Enforcement is separate again: in Microsoft’s own source grid, no non-Microsoft source supports a Purview policy.

6. Does Microsoft Purview Unified Catalog have an API for agents?

It has a REST API, and Microsoft states the boundary itself: the API is in public preview and “only covers the Unified Catalog features that are available in General Availability (GA).” Preview objects like critical data elements therefore fall outside it. Microsoft also scopes what any interface can reach: “All data in Data Map and Unified Catalog is metadata, not the underlying data itself.”

7. Is Purview included in our Microsoft license?

“Purview” isn’t one product, so the license question splits in two. Information Protection, the sensitivity-label, encryption and DLP layer, is largely bundled into Microsoft 365 E5, or available as an add-on to E3, so a tenant already on E5 likely already has it. Data Governance, the Data Map and Unified Catalog together, is never bundled into any Microsoft 365 tier: it’s billed separately, as Azure consumption tied to a linked Azure subscription, no matter which Microsoft 365 license the organization holds.

Sources

1. Microsoft Purview overview
2. Data governance overview
3. Unified Catalog
4. Data Map supported data sources
5. Unified Catalog governance domains
6. Unified Catalog data products
7. Unified Catalog data assets search
8. Unified Catalog data products search
9. Unified Catalog glossary terms
10. Critical data elements
11. Unified Catalog data quality
12. Unified Catalog health controls
13. Unified Catalog self-serve analytics
14. Unified Catalog application card
15. Live view
16. Data governance billing
17. Data governance known issues
18. What’s new in Microsoft Purview
19. Unified Catalog API overview
20. Fabric IQ overview
21. Microsoft Purview and Microsoft Fabric
22. Microsoft Purview pricing
23. Microsoft Purview Data Governance general availability announcement, 2024
24. Data catalog vs context layer, Atlan
25. Microsoft Purview Information Protection
26. Microsoft Purview service description
27. Upgrade to Enterprise Microsoft Purview Data Governance
28. Data governance billing FAQ