Microsoft Purview Pricing for Data Governance Explained

Microsoft Purview pricing is unusual among data governance tools because most of it is public. Microsoft publishes pay-as-you-go rates for the data governance side of Purview, so you can estimate a bill before talking to sales. The catch is that the bill is driven by usage, not by a flat subscription: you pay for every asset you actively govern, for every data quality run, and, on the older classic model, for scanning and metadata storage.

This guide explains each meter with the current US East rates, works through a monthly estimate for three sizes of deployment, and lists the costs that do not appear on the price list. All prices below were taken from Microsoft's pricing page in October 2026 and exclude discounts and negotiated agreements.

How Is Microsoft Purview Priced?

Microsoft Purview is a family of products, and the word "pricing" covers three different things:

• Data security and compliance features, such as information protection, data loss prevention, insider risk management, and eDiscovery, are mostly licensed per user through Microsoft 365 E5 or Purview add-on suites, with some pay-as-you-go meters on top.
• Data governance, meaning the Unified Catalog, data quality, and data health management, is billed pay-as-you-go through an Azure subscription. This is the part that competes with a data catalog or governance platform, and the focus of this article.
• Azure Purview (classic) is the previous data governance service, still billed on its own meters for organizations that have not moved to the new model.

Pay-as-you-go billing for Purview data governance took effect on January 6, 2025. To use the data governance experience in the Microsoft Purview portal, an organization links an Azure subscription and resource group in the same tenant, and usage is billed there like any other Azure service.

Unified Catalog Pricing

The Unified Catalog has one meter for content: the number of unique governed assets per day.

A governed asset is a data asset, such as a table or a view, that is attached to at least one governance concept: a data product, a critical data element, a glossary term, or a data quality rule. Assets that sit in the Data Map without such a link are not counted. Three rules from Microsoft's billing documentation shape the bill:

• Each asset counts once per day, however many data products or terms reference it.
• Governance concepts without assets cost nothing. Creating 50 domains and data products with no tables attached produces no governed-asset charge.
• Attaching a server counts as one asset. Microsoft counts the server itself, not all of its child tables.

Microsoft's own example: an organization with 500 assets in the Data Map, of which 200 are linked to governance concepts, pays about $100 for a 30-day month. Charges are prorated by the days an asset is governed.

Data Quality and Data Health Pricing

Running data quality rules and data health controls is billed separately, in Data Governance Processing Units. One DGPU is 60 minutes of fully managed compute, and it comes in three performance options:

The number of DGPUs depends on the rule type, the data volume, and the source. Microsoft's documentation shows a simple check on one million rows in Azure SQL Database consuming about 0.02 DGPU per run on the Basic option. Its own worked example: 100 rule runs at 0.02 DGPU each equal 2 DGPUs, or $30 on the Basic option. Data health controls, such as the scores and reports in Health management, run daily by default on the Basic option until you change the schedule or deactivate them.

Data Map and Azure Purview Classic Pricing

Unified Catalog runs on the existing Purview Data Map. According to Microsoft, Data Map and scanning charges do not apply to Unified Catalog customers once they consent to the pay-as-you-go model or upgrade from the free to the enterprise tier. Organizations that stay on the classic Data Catalog continue to pay the classic meters:

One capacity unit running for a full month costs roughly $300 (0.411 x 730 hours), before scanning. Managed resources such as the storage and Event Hubs accounts that Purview provisions can add small charges of their own, and scanning data in other clouds can incur data transfer and API costs on that cloud's bill.

Microsoft Purview Cost Example

Because the bill depends on usage, the most useful exercise is an estimate. The figures below use the published US East rates and simple assumptions: 30-day months, the Basic DGPU option, and 0.02 DGPU per data quality run. They are illustrations, not quotes.

Two patterns stand out. The governed-asset charge grows in a straight line with the governed estate, so a catalog that covers ten times more assets costs ten times more. And data quality can match or exceed the catalog charge once rules run daily at scale. Scheduling rules less often, or only on critical data, is the main cost lever.

Costs Beyond the Price List

The meters above are only part of the cost of running Purview as a governance platform.

• Security and compliance licensing. Information protection, data loss prevention, and other Purview security features are mostly licensed per user through Microsoft 365. They are a separate budget from governance, even though they share a brand.
• Non-Microsoft sources. Purview connects to many sources beyond Azure, but coverage and depth vary by source. Organizations with significant Snowflake, Databricks, Oracle, SAP, or Tableau estates should check scan and lineage support for each one before estimating.
• People and operating model. As with any governance tool, most of the work is defining domains, data products, terms, and owners. Purview bills nothing for an empty governance concept, but someone still has to fill it in.
• Forecasting effort. Usage-based billing needs monitoring. Microsoft provides a usage monitoring view in preview and a pricing calculator, and finance teams will want a budget alert on the subscription.

When Purview Fits and When You Need a Cross-Platform Catalog

Purview is a natural choice when most of the data estate lives in Azure, Microsoft Fabric, and Microsoft 365, and when the same team owns data security and data governance. Its pricing rewards a focused scope: govern the critical assets, attach them to data products, and keep data quality rules targeted.

The pricing model is less predictable when governance needs to cover a large, mixed estate. A per-asset meter turns every newly governed table into a recurring cost, which can discourage teams from extending governance where it is needed. Organizations with several platforms often pair a Microsoft-native tool with a cross-platform catalog, or choose one that prices by team rather than by asset. For context on the wider Microsoft stack, see Microsoft Fabric pricing.

How Dawiso Compares on Cost

Dawiso prices by user, with a generous object allowance per seat, and publishes its pricing. The Standard plan starts at 5,340 EUR per year (445 EUR per month) for five contributor seats and twenty viewer seats, and includes an unlimited number of connectors and an allowance of 100,000 cataloged objects per contributor, so cataloging another thousand tables does not change the bill. Larger Corporate and Enterprise plans scale by seats.

The two models suit different situations. Purview's per-asset pricing can be inexpensive for a small, Microsoft-centered governance scope. Dawiso's per-user pricing is easier to forecast when the goal is to cover the whole estate across Microsoft and non-Microsoft systems, with connectors for platforms such as Microsoft Fabric, Power BI, Azure Synapse, Azure Data Factory, Snowflake, Databricks, Oracle, SAP HANA, and Tableau, and with lineage and the business glossary connecting them. For a side-by-side view of public prices across vendors, see data catalog pricing compared.

Conclusion

Microsoft Purview pricing for data governance is transparent and usage-based. The Unified Catalog costs about $0.50 per governed asset per month, data quality and health checks cost $15 to $240 per processing unit, and classic accounts still pay for Data Map capacity and scanning. That makes Purview easy to start small, and harder to forecast as governance grows. Estimate from the number of assets you will actually govern and the data quality rules you will run, add the Microsoft 365 licenses you need for security features, and compare that total with per-user alternatives before committing.

Sources

• Microsoft Azure - Microsoft Purview pricing (Data Governance and Azure Purview (Classic) tabs, US East, accessed October 2026)
• Microsoft Learn - Billing in Microsoft Purview Data Governance (governed assets, DGPU consumption, Data Map and scanning charges)
• Dawiso - Pricing