Share via

Learn about data governance billing

Microsoft Purview data governance solutions include Microsoft Purview Unified Catalog and Microsoft Purview Data Map. For Unified Catalog, there are charges for governed assets and data health management capabilities, and the billing for these components operates on a pay-as-you-go model. There's no cost to scan assets into Data Map when certain billing conditions are met. This article explains how to prepare for billing and how data governance capabilities are charged.

To find complete pricing information, with pricing calculators, see the Microsoft Purview pricing site.

To learn more about the pay-as-you-go billing model for Microsoft Purview, including the consent experience, see Microsoft Purview billing models.

Prerequisites

To use Microsoft Purview pay-as-you go, you need:

If you already have these resources for other purposes, you can also use them with Microsoft Purview.

Billing setup

To use the data governance experience in the Microsoft Purview portal, you need to be set up for Microsoft Purview pay-as-you-go billing. Pay-as-you-go took effect for Microsoft Purview on January 6, 2025. For details about required roles and the setup experience, visit one of the resources below based on your situation:

If you don't consent to the pay-as-you-go pricing model, you can still use the classic Data Catalog in the classic data Microsoft Purview portal.

Your Data Map assets remain intact regardless of whether you consent to the new billing experience for Unified Catalog.

Pricing components

There are two pricing components that support data governance in Microsoft Purview. Unified Catalog has two meters that run based on:

  1. Number of unique governed assets per day; see Unified Catalog billing.
  2. Data governance processing units per run; see Data health management.

Unified Catalog billing

A single meter is initiated for an organization when users begin to govern unique data assets. A unique data asset could be a table or a view linked to a governance concept, such as a data product or a critical data element.

Assets that are collected in Data Map but aren't linked to a governance concept aren't counted as governed assets.

Tip

To view specific pricing information and a calculator for your region, see the Data Governance tab on the Microsoft Purview pricing site.

What are governed assets and how are they billed

In Unified Catalog, the active management and curation of data assets turns assets into "governed assets." A governed asset is a technical file or table or report that is attached or associated to a governance concept, such a data product or a critical data element. If a technical asset isn't associated to a governance concept, it isn't a governed asset.

For example, if you have a SQL server with 200 tables, and only 20 tables are in the gold tier of the medallion structure, you've created 20 data products with each data product linked to a table. Every day, the Unified Catalog billing system looks for the count of tables that are associated to the data product. Only 20 tables are linked to data products, so only 20 tables are governed assets, instead of the full 200 tables.

Over time, you might want to attach a glossary term and a policy to the data product, which will then also apply to the governed assets. In each case, a governed asset is still a single governed asset regardless of how many concepts are attached to the asset.

  • Example 1: A SQL table is referenced within a data product. The same SQL table is used in five other data products. The SQL table is counted one time only, once a day.
  • Example 2: You create 50 governance domains and data products, but haven't attached any tables, files, reports, or dashboards. In this case, you won't be charged for any governed assets.
  • Example 3: You accidentally attached a server to the data product. Microsoft Purview counts just the server as a single asset, not all the children tables within the server.

View pricing information on the Data Governance tab on the Microsoft Purview pricing site.

Data health management usage

The Microsoft Purview Data Governance Enterprise Data Management meter is initiated when a customer runs data quality and health management actions on their governed data estate. Data management usage is billed based on the data governance processing unit (DGPU) pay-as-you-go meters. A DGPU is the amount of service performance consumed for 60 minutes and is available in three different performance options: Basic, Standard, and Advanced. The Basic SKU option is set as the default performance option until an organization selects a higher option.

View pricing information at each performance level on the Data Governance tab on the Microsoft Purview pricing site.

Data governance processing units explained

A DGPU is a fully managed compute unit used to run compute heavy capabilities such as data quality and data health management. Each DGPU is 60 minutes of compute time run across varying sets of nodes based on the workload need.

DGPUs consumed is dependent on:

  1. Data quality or health (metadata quality) rule type: Out of the box or custom.
  2. The volume of data.
  3. Source type: The same volume of data might generate different DGPUs across two different source types.

Some ranges of DGPU generated are as follows:

Data Source Row count SKU type Rule type DGPU per rule per run
Azure SQL DB 1 Million Basic Empty/blank check 0.02
Azure SQL DB 1 Million Basic StringFormat=Regex/Like check 0.02
Azure SQL DB 1 Million Basic Table lookup (1 mill row reference table) 0.03
Azure SQL DB 1 Million Basic Unique check 0.02
Azure SQL DB 1 Million Basic Duplicate check = 3 column-combo 0.02

Data health controls pricing

For data health controls, self-serve analytics, and reports within Health management, the Basic SKU is always used, as higher processing capacity is not required for these capabilities.

The total DGPU consumption depends on the data volume, the calculation of control scores, and report generation. The control job is scheduled to run daily upon initial provisioning and will only trigger if at least one business domain has been created. If a user removes all business domains, the job will not run.

Users can adjust the schedule as needed; the job will always run based on the user-configured schedule. If a user doesn't want to refresh a specific control, they can edit the control and toggle it to deactivate.

This flexibility allows users to fully manage schedules and selectively inactivate controls to optimize costs and manage DGPU consumption.

Tip

  • Default control is refreshed daily. The scheduled controls run based on the schedule configured by customer.
  • If you prefer not to use data health controls, you can manually disable them from the schedule page. Individual controls can be activated or deactivated separately, helping you focus on the most relevant controls.

Data quality pricing

Data quality usage is billed based on DGPU pay-as-you-go meters. An example of how data quality could be billed: if you run 100 data quality jobs in a single day, and each run produces 0.02 DGPU, then the total DGPU for that day is two DGPUs. To calculate the cost based on performance option and region, visit the Microsoft Purview pricing site.

Here's example of consumed processing units for basic to complex rules for different data volumes, based on the standard performance option.

Rule complexity 10,000 records - 100,000 records - 1,000,000 records - 10,000,000 records - 100,000,000 records - 1,000,000,000 records -
Duration PU Duration PU Duration PU Duration PU Duration PU Duration PU
Simple Elapsed time: 1m 1s 0.02 Elapsed time: 1m 1s 0.02 Elapsed time: 1m 1s 0.02 Elapsed time: 1m 16s 0.02 Elapsed time: 1m 16s 0.02 Elapsed time: 1m 31s 0.03
Medium Elapsed time: 1m 1s 0.02 Elapsed time: 1m 1s 0.02 Elapsed time: 1m 1s 0.02 Elapsed time: 1m 16s 0.02 Elapsed time: 1m 31s 0.03 Elapsed time: 2m 1s 0.03
High Elapsed time: 1m 1s 0.02 Elapsed time: 1m 1s 0.02 Elapsed time: 1m 31s 0.03 Elapsed time: 1m 32s 0.03 Elapsed time: 2m 1s 0.03 Elapsed time: 2m 51s 0.04

Tip

  • Increase data volume: For testing, you can use the same data asset by adding more data, or you can create multiple data assets with different data volumes; see the example above.
  • Example of rule complexity
    • Simple rule: Blank / Empty value check
    • Medium complex rule: Uniqueness rule, data type/format check rule
    • High complex rule: Duplicate check with multiple selected columns; credit card, national ID, table lookup, and SSN validation are in the category of complex rule.

Data Map and scanning charges

Unified Catalog currently runs on the existing Data Map. Data Map and scan charges won't apply to Unified Catalog customers once they either consent to the Microsoft Purview billing model or upgrade from free to enterprise tier. The new Unified Catalog is rolling out in multiple regions; check the supported regions for Unified Catalog.

Customers using the classic Data Catalog can check pricing on the Data Map (Classic) tab of the Microsoft Purview pricing site.

Resources