Microsoft Purview Pricing: What Purview Costs in 2026

Microsoft Purview data governance bills on two meters and Microsoft publishes both rates. Unified Catalog costs $0.0165 per governed asset per day, roughly $0.50 per asset per month. Data quality and health jobs cost $15, $60, or $240 per data governance processing unit on the Basic, Standard, and Advanced tiers. There is no seat licence and no platform fee, so a 2,000-asset catalog running 50 quality checks a day works out near $1,400 a month.

That makes Purview close to unique in this category. Collibra, Alation, Atlan, Informatica, Ataccama, and almost every other enterprise governance vendor will not show you a number without a call. Microsoft publishes exact metered rates, and they are queryable from the public Azure retail price API, so you can model your bill from your own asset counts before anyone books a demo.

Here is what each meter actually charges for, what counts as a billable asset, and where the model surprises people. Every figure below was pulled from Microsoft's own price API and billing documentation on 5 August 2026, in USD for the East US region. Prices vary by region, so check yours.

How much does Microsoft Purview cost?

Two meters run for data governance, and they are independent of each other:

Everything else in the data governance experience, including the catalog interface, glossary terms, data products, governance domains, and the Data Map scanning underneath, carries no separate charge once you are on the pay-as-you-go model. That model took effect on 6 January 2025.

What counts as a governed asset?

This is the part that decides your bill, and it is more forgiving than most people assume. A governed asset is a data asset you have actively attached to a governance concept: a data product, a critical data element, a glossary term, or a data quality rule. Assets that Data Map has scanned but that nobody has linked to anything are not governed assets and are not billed.

Microsoft's own example in the billing documentation is worth quoting because it sets the shape of the model. A SQL Server with 200 tables, of which 20 sit in the gold tier and have been made into data products, produces 20 governed assets, not 200. The other 180 tables sit in the catalog and cost nothing.

Three counting rules follow from that, and all three work in your favour:

• An asset is counted once per day no matter how many concepts point at it. A table referenced by six different data products is one governed asset, not six.
• Creating 50 governance domains and data products with no tables attached bills nothing at all. The concept is free; only the attached asset counts.
• Attaching a server rather than its tables counts the server as one asset, not every child table underneath it.

The practical consequence is that Purview rewards deliberate curation and punishes attaching everything in sight. A team that governs the 300 tables anyone actually reports on pays for 300 assets. A team that reflexively links its whole estate pays for its whole estate, at $6 per asset per year.

What is a data governance processing unit?

A DGPU is 60 minutes of managed compute, run across a variable set of nodes depending on the workload. It is the unit for data quality scanning and for the health controls that produce governance scorecards. Basic is the default tier until you deliberately select a higher one, and health controls, self-serve analytics, and reports always run on Basic regardless of what you pick for quality.

The useful thing is that Microsoft publishes real consumption figures rather than leaving you to guess. Against a million-row Azure SQL table on the Basic tier, a documented set of rules consumes:

Microsoft's worked example: 100 data quality runs in a day at 0.02 DGPU each is 2 DGPU, which on Basic is $30 for that day. Complexity scales the number less than you would expect. Even at a billion records, a high-complexity rule is documented at 0.04 DGPU on the Standard tier, so volume moves the bill far less than run frequency does. If you want to cut DGPU spend, run rules less often before you try to make them simpler.

What would Purview actually cost my team?

Below is straight arithmetic on the published rates, at three sizes. These are not quotes and not Microsoft figures, just the two meters multiplied out for a 30-day month on Basic, so you can sanity-check your own numbers the same way.

The shape matters more than the totals. Asset count drives the base and it is linear with no volume discount published, while quality compute is genuinely cheap until you schedule a lot of rules hourly. And unlike every quote-only vendor in the category, none of this changes because you added ten people to the data team, since there is no per-seat component at all.

What about the classic Purview Data Map pricing?

If you are an existing Azure Purview customer who has not consented to the pay-as-you-go model, you are on the older Data Map meters instead. Those rates are also published, and they are a different shape entirely, closer to a running-capacity bill than a per-asset one:

A capacity unit running continuously is about $300 a month before you scan anything, which is why the newer per-asset model is usually cheaper for teams governing a focused set of assets and more expensive for teams that want to govern everything. Data Map and scan charges stop applying once you consent to the new billing model or upgrade from the free tier to enterprise.

The three things called Purview

More evaluations go wrong on naming than on pricing, because Microsoft has used the word for three different products and search results mix all three freely:

• Azure Data Catalog was retired on 15 May 2024. Anything you find about it is historical.
• The classic Purview Data Catalog is described by Microsoft as no longer taking on new customers and now in customer support mode. There is no published end-of-life date, but it is not what you would buy today.
• Unified Catalog in the Microsoft Purview portal is the current data governance product, and it is the one the $0.0165 per asset rate applies to.

Separately, the Purview brand also covers compliance and data security products with their own meters entirely, including data loss prevention, eDiscovery, insider risk, and audit. When someone in your organization says the company already pays for Purview, it is worth establishing which of those they mean, because a Microsoft 365 compliance deployment tells you nothing about whether the governance meters have ever been switched on.

Where Purview's lineage stops

Pricing transparency is genuinely the best thing about Purview, and it is not the only thing to evaluate. Column-level lineage is supported, with two documented limits worth knowing before you commit: manual column-level lineage is unsupported when a process asset sits in between two assets, and automated lineage only arrives from a fixed list of process systems rather than from anything you connect.

The wider limit is the same one every platform-native governance layer has. Purview is strongest across the Microsoft estate and thinner as you move away from it. If your reporting path runs from a Postgres source through Snowflake into a Looker dashboard, no single vendor's native layer follows that whole path, which is the honest reason teams add a third-party tool on top. We built column-level lineage for exactly that case: a read-only connection to the warehouse, query history parsed into a graph, and downstream impact analysis before a change ships.

One more thing the 2026 governance criteria have pushed everyone toward, Purview included, is unstructured content: contracts, invoices, and reports that were never rows in a table. Governing those is a different problem from governing a warehouse, and it usually starts with turning the documents into structured records before any catalog can meaningfully describe them.

Is Microsoft Purview cheaper than Collibra or Alation?

Almost certainly, and nobody can prove it, which is the whole point. Collibra, Alation, Atlan, Informatica, Ataccama, and Immuta publish no pricing at all, so the comparison can only be made against a quote you personally hold. Third-party figures for those vendors circulate widely and contradict each other badly enough that some of them are simply wrong, which is why we do not reprint them here or in our breakdown of how much Collibra costs.

What can be said accurately is that enterprise governance suites are sold on annual contracts with implementation attached, and they are not competing for a team that would be happy at $300 a month. Purview, the hyperscaler catalog layers, and a small number of self-serve tools including us are. If published pricing is a hard requirement for you, the full list of who publishes what is in our data governance tools comparison, and our own plans are on the pricing page.

Frequently asked questions

Is Microsoft Purview free?

There is a free tier of the Purview data governance experience with limited capability, and Data Map scanning carries no charge once you are on the pay-as-you-go model. Actual governance is not free: the moment you link a table to a data product, a glossary term, or a quality rule, it becomes a governed asset and bills at $0.0165 per day. Running a quality rule bills DGPU separately. Budget from your intended governed-asset count, not from the free tier.

Does Microsoft Purview charge per user?

No. The data governance meters are per governed asset per day and per data governance processing unit consumed. There is no seat licence, so adding analysts, stewards, or engineers does not change the bill. That is unusual in this category, where per-seat pricing is common and is often the component that grows fastest as a governance program spreads beyond the original team.

How do I estimate my Microsoft Purview bill?

Count the tables and views you intend to link to a governance concept, not everything a scan would find, and multiply by $0.0165 per day. Then estimate quality runs per day and multiply by roughly 0.02 DGPU per rule per run at $15 per DGPU on Basic. Microsoft also publishes a calculator on the Azure pricing site with the same inputs. Both meters are visible per governance domain in the usage monitoring view once you are live.

What is a DGPU in Microsoft Purview?

A data governance processing unit is 60 minutes of managed compute used for data quality scanning and health controls, priced at $15 on Basic, $60 on Standard, and $240 on Advanced. Basic is the default and is always used for health controls and reports. Documented consumption is around 0.02 DGPU per simple rule per run against a million rows, so most rules cost cents rather than dollars to execute.

Does Purview do data lineage?

Yes, including column-level lineage, with two documented caveats. Manual column-level lineage is not supported when a process asset sits between two assets, and automated lineage is only captured from a fixed list of supported process systems rather than from every connected source. Coverage is strongest across Azure services and thins out beyond them, which is the usual reason teams pair it with a warehouse-native lineage tool. Our data catalog tools guide compares the lineage granularity of every major option side by side.