Azure Purview pricing

Microsoft Purview Data Governance | Enterprise Data Catalogue

Microsoft Purview Data Governance Enterprise Catalogue is billed based on a single meter, data catalogue, that is initiated when customers govern unique data assets. Data assets such as tables, views, AI models, semantic models, and many others that are linked to governance concepts in the product, such as data products and critical data elements, are counted as governed assets. Assets that are collected in the Purview Data Map, but not linked to the governance concepts aren't counted as governed assets.

For example, if an organisation has 500 tables, views, stored procedures, resource sets, and AI models in their data map, while only 200 unique governed assets in the data catalogue, the monthly cost, for 30-days, would be $100 (without discounts). The 300 assets that aren't linked to the data products or critical data elements aren't considered governed assets and therefore not counted. Data catalogue managed assets are priced uniformly across regions. This pay-as-you-go model for a managed asset is prorated based on days governed within the monthly billing cycle.

Microsoft Purview Data Governance | Enterprise Data Management

Data management usage is billed based on the Data Governance Processing Unit (DGPU) pay-as-you-go meters. A DGPU (1 DGPU) is the equivalent to 60 minutes of fully-managed compute time, taken to produce data management results. DGPU is available in three different performance options: Basic, standard and advanced. By default any data management rule or health control is run on the Basic SKU. A customer can switch SKU’s based on the speed of compute suitable for their organisation. Learn more.

For example, if a customer runs 100 Data Management rules and controls in a single day, and each run produces 0.02 DGPU with the Basic SKU, then the total DGPU for that day would equal two DGPU, costing the customer $30. See the table below for pricing for Data Health Management feature by SKU in US East pricing.

Data Map (classic) – Formerly Azure Purview

Data Map (Classic) Population / Automated Scanning and Classification

Data Map population is serverless and billed based on the duration of scans (includes metadata extraction and classification) and ingestion jobs. Automated scans using native connectors trigger both scan and ingestion jobs. Push based updates from a Microsoft Purview client (e.g., lineage push from Azure Data Factory) only trigger ingestion jobs.

Duration of these jobs can vary based on the number of systems scanned or pushing updates, data assets contained in the scanned systems, number of classifications selected, the shape of the data and performance of the system scanned.

Data Map Enrichment / Advanced Resource Set

Advanced Resource Set is a built-in feature of the Data Map used to optimise the storage and search of data assets associated with partitioned files in data lakes. Billing for processing the resource set data assets is serverless and based on the duration of the processing, which can vary based on the change in partitioned files and resource set profile configured.

Insights Generation

Insights Generation aggregates metadata and classifications in the raw Data map into enriched, executive-ready reports that can be visualised in the Data Estate Insights application and granular asset level information in business-friendly format that can be exported. Report visualisation and export incurs charges from Insights Report Consumption in the Data Estate Insights application.

Data Map Consumption / Elastic data Map

By default, a Microsoft Purview account is provisioned with a Data Map of at least 1 Capacity Unit. 1 Capacity Unit supports requests of up to 25 data map operations per second and includes storage of up to 10 GB of metadata about data assets. The first 1 MB of Data Map meta data storage is free for all customers.

The Data Map can scale capacity elastically based on the request load. Request load is measured in terms of data map operations per second. As a cost control measure, a Data Map is configured by default to elastically scale within the elasticity window.

A data map operation is a create, read, update, or delete of an entity in the Data Map. Examples of an entity include a data asset or a lineage relationship between two data assets. A search request may require multiple operations depending on the assets returned and complexity of the request. The storage size of an entity may vary depending on the type of entity and annotations associated with the entity.

Data Map requires an additional Capacity Unit for every 10 GB of metadata storage required. For example, a Data Map with 10 GB of metadata storage is billed at 1 Capacity Unit per hour. If the addition of new data assets increases the size to 10.1 GB, the Data Map is billed at 2 Capacity Unit per hour.

Microsoft Purview Applications

Microsoft Purview Applications are a set of independently adoptable, but highly integrated user experiences built on the Data Map including Data Catalogue, Data Estate Insights and more. These applications are used by data consumers, producers, data stewards and officers that enable enterprises to ensure that data is easily discoverable, understood, high quality, and all use is per corporate and regulatory requirements.

Microsoft Purview Applications / Data Catalogue (Classic)

Data Catalogue (classic) is an application built on Data Map for use by business users, data engineers and stewards to discover data, identify lineage relationships and assign business context quickly and easily.

Capabilities marked Included with Data Map are billed as the consumption of the Data Map Capacity Unit.

Workflows

Data owners and stewards can automate commonly used repetitive tasks associated with business processes like glossary curation and approval tracking using workflow management.

Microsoft Purview Applications / Data Estate Insights (classic)

Data Estate Insights (classic) is an application built on Data Map (classic) for use by Data Officers and Stewards to understand the data estate health and governance posture of their diverse data estate and drive corrective actions to close gaps. Data Estate Insights (classic) serve up enriched data generated through Insights Generation, which is charged separately as indicated above in the Data Map Enrichment – Insights Generation section.

Insights consumption is billed per API call. One API call returns up to 10,000 rows of tabular result.

Microsoft Purview Applications / Data Policy

Data owners can centrally manage thousands of SQL Servers and data lakes to enable quick and easy access to data assets mapped in the Data Map for performance monitors, security auditors, and data users.

Data Sharing

In-place Data Sharing lets users share data easily both within and between organisations, providing near real-time access to data without duplication.