Microsoft Purview Pricing: $0.0165 per Governed Asset per Day and $15 to $240 per Processing Unit

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 license 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 on their own website, though several are forced to publish one on AWS Marketplace. 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, rechecked against the live Azure retail price API on 30 August 2026, in USD for the East US region. All four Data Governance meters were unchanged again on that check, and they returned identical rates in all 23 regions the API covers, so there is no cheaper region to deploy into. 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:

Meter	Published rate	What triggers it
Unified Catalog governed assets	$0.0165 per asset per day	Counted daily, per unique data asset linked to a governance concept
Data management, Basic tier	$15.00 per DGPU	Default tier for data quality rules and all health controls
Data management, Standard tier	$60.00 per DGPU	Opt-in higher performance for quality scanning
Data management, Advanced tier	$240.00 per DGPU	Highest performance tier for the heaviest workloads

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 favor:

• 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:

Rule	DGPU per rule per run
Empty or blank check	0.02
String format, regex or LIKE check	0.02
Unique check	0.02
Duplicate check across three columns	0.02
Table lookup against a million-row reference table	0.03

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.

Scenario	Governed assets	Quality runs per day	Assets per month	DGPU per month	Approximate total
Small team, one warehouse	300	20	$149	$180	about $329
Mid-size, governed reporting layer	2,000	50	$990	$450	about $1,440
Enterprise program	15,000	300	$7,425	$2,700	about $10,125

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:

Classic meter	Rate
Data Map standard capacity unit	$0.411 per capacity unit hour
Scanning, ingestion and classification	$0.63 per vCore hour
Advanced resource set	$0.21 per vCore hour
Data insights generation	$0.82 per vCore hour
Insights report consumption	$0.21 per API call
Power BI and on-premises SQL Server scanning	$0.00, listed as free for a limited time

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.

One caveat on that table, checked 30 August 2026: five of those six meters no longer appear in the Azure retail price API. Querying the API for the product name Microsoft Purview Data Map now returns exactly one meter across all 23 regions, Advanced Resource Set vCore at $0.21 per hour, with an effective date of 1 April 2026. The standard capacity unit, scanning vCore, data insights and insights report rates above are the published classic figures and are kept here because existing customers may still be billed on them, but they are no longer retrievable as live list prices. If a vendor comparison quotes you a Data Map capacity unit rate as a current price, check the date on it before you build a budget around it.

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.

Microsoft's own connector matrix is more specific than most comparisons admit. Amazon Redshift is marked No for lineage, classification, labels and policies alike. Snowflake lineage is static, derived from object definitions rather than executed queries, and incremental scans are not supported. Power BI column-level lineage works only when the source is Azure SQL Database. We go through the whole matrix on our Microsoft Purview comparison.

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.

The Purview meters that surprise people on the first bill

The two governance meters above, governed assets and DGPUs, are the ones every comparison article covers. They are not the only things that appear on the invoice, and the extras catch people out because they sit under different product names in the Azure price list while landing on the same subscription.

On-demand classification is billed separately, at $20 per 10,000 standard assets. This is the meter that runs when you classify content on demand rather than on the standard schedule, and it is worth knowing about before somebody kicks off a broad classification sweep across a large estate to see what is in there. Ten thousand assets sounds like a lot until you point it at a data lake.

Then there is the family confusion, which is a billing problem as well as a naming one. Microsoft Purview Data Security and Microsoft Purview Data Compliance carry their own meters entirely, and a team that enables features across the Purview portal without watching which product they belong to can end up with line items they did not plan for. As of the August 2026 price list these include a Standard Data Security Processing Unit at $25, Investigations Compute at $5 per hour plus $0.164 per GB per day, audit and communication compliance metered per thousand assets, and retention at $0.0082 per GB per day. None of these are data governance costs, and none of them appear in a governance budget built from the governed asset meter alone.

The practical advice is the same one Microsoft's own documentation implies without saying directly: build your estimate per meter, not per product. Ask which specific meters a proposed configuration will touch, then check each against the live price API for your own region rather than trusting a figure from an article, including this one. The API is public and a single query returns the current list.

It is also worth separating the license cost from the work. The DGPU meter prices the compute that runs data quality scans, but it does not decide what those scans should check or what a passing score means. That part is yours, and it is worth settling before you turn on scanning at scale, since a broad sweep of low-value rules bills the same as a focused set of good ones. Our guide to data quality dimensions and metrics covers how to choose and weight the checks themselves.

Is Microsoft Purview cheaper than Collibra or Alation?

For most estates yes, and this is now measurable rather than a guess. None of those vendors publishes a price on its own website, but a transactable AWS Marketplace listing has to carry a real figure, and several do. Read on 31 August 2026: Collibra lists $170,000 for 12 months, Alation $60,000, and Immuta $96,000. Informatica prices 120 IPU a month at $131,760 a year. Atlan and Ataccama remain the genuine exceptions, showing a private offer or a $1.00 placeholder rather than a price.

Set against Purview's $0.0165 per governed asset per day, one asset costs $6.02 a year, so Collibra's $170,000 is break-even at roughly 28,200 governed assets and Alation's $60,000 at about 10,000. Below those counts the metered model is cheaper; above them the flat contracts win. We run that comparison in full, including BigID at $175,000, in BigID vs Collibra vs Microsoft Purview pricing, and go deeper on one vendor in 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 are, and Datatrail is one of them, with plans at $99, $299 and $799 a month on the pricing page. 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 pricing is 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 license, 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.

How much does Microsoft Purview classification cost?

On-demand classification is metered separately from the governed asset and DGPU meters, at $20 per 10,000 standard assets as of the August 2026 Azure retail price list for East US. That is distinct from classification that happens as part of standard scanning. If you plan a broad one-off sweep to discover what sensitive data exists across a large estate, price that sweep on its own rather than assuming it falls under the governance meters.

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.

How does Purview pricing compare with IBM's?

The two hyperscaler-adjacent suites price on different philosophies, and only one of them tells you so up front. Microsoft publishes per-meter rates for Purview and exposes them through a public retail price API, so you can model a bill before you talk to anyone. IBM does not print a price for watsonx.data integration at all, though its cloud catalog API does return one. We pulled the numbers and showed the method in our guide to watsonx.data integration pricing, which also covers what happened to the Databand product IBM folded into it.

Informatica sits between the two. It publishes nothing on its own pricing pages, but its AWS Marketplace listing prices a bundle of 120 Informatica Processing Units per month at $131,760.00 a year, which is $91.50 per IPU. We broke that down, including the fact that its two and three year terms carry no discount whatsoever, in our guide to Informatica pricing. Ranked by how much a buyer can learn without a sales call, Microsoft is first by a wide margin, Informatica second by accident, and IBM third.

Rechecked against the live Azure retail price API on 30 August 2026: the Data Catalog Standard Asset meter is still $0.0165 per asset per day, and the Basic, Standard and Advanced Data Governance Processing Units are still $15, $60 and $240. No governance meter has changed since our previous check on 26 August 2026.