azurerm_purview_account cost estimation

An azurerm_purview_account provides data governance — the Data Map (a catalog of your data estate), scanning/classification, and lineage. The standing cost is the Data Map's always-on capacity units (elastic vCore-equivalents): one capacity unit runs continuously at ~$300/month, and the Data Map auto-scales capacity units up as the catalog grows in size and operation rate.

On top of the always-on Data Map, scanning is billed per vCore-hour while scans run, and advanced features (data-quality, some insights) have their own charges. So the bill is the standing Data Map capacity plus scan compute.

The cost levers: the Data Map scales with how much metadata you hold and how heavily you query it, so cataloging only the data estate you actually govern keeps capacity units down; and scans bill per vCore-hour, so scoping scans to relevant sources and sensible schedules (not scanning everything nightly) controls scan cost.

c3x prices the account from the always-on Data Map capacity unit; scanning is usage-driven and modelled separately.

Terraform example

A minimal but realistic configuration that C3X can estimate.

resource "azurerm_purview_account" "governance" { name = "data-governance" resource_group_name = azurerm_resource_group.main.name location = azurerm_resource_group.main.location identity { type = "SystemAssigned" } }

Pricing dimensions

What you actually pay for when you provision azurerm_purview_account.

Dimension	Unit	What's being charged
Data Map capacity unit	per hour	Always-on Data Map capacity, billed continuously. Auto-scales up with catalog size and operation rate. ~$0.41/capacity-unit-hour → 1 unit ≈ $300.03/month
Scanning	per vCore-hour	Scan/classification compute billed per vCore-hour while scans run. Usage-based.

Optimization tips

Common ways to reduce azurerm_purview_account cost without changing the workload.

Catalog only the estate you govern

Per capacity unit avoided

The Data Map's always-on capacity scales with how much metadata it holds and how heavily it's queried. Registering and cataloging only the data sources you actually govern keeps capacity units — and the standing cost — down.

Scope and schedule scans

Proportional to scan vCore-hours

Scanning bills per vCore-hour. Scope scans to relevant sources and run incremental scans on sensible schedules rather than full scans of everything nightly.

Right-size scan compute

Per scan vCore-hour

Scans run on configurable integration runtime capacity. Match the scan tier to the data volume rather than over-provisioning scan compute that finishes quickly but bills the higher rate.

Be selective with advanced features

Feature-dependent

Data quality and some insights features carry their own charges on top of the Data Map. Enable them where they deliver governance value, not blanket across the estate.

FAQ

How is Microsoft Purview billed?

Primarily by the Data Map's always-on capacity units — one unit runs continuously at ~$300/month and auto-scales with catalog size and query rate — plus scanning billed per vCore-hour while scans run, plus charges for advanced features like data quality.

Why is my Purview cost higher than one capacity unit?

The Data Map auto-scales capacity units as your catalog grows in metadata volume and operation rate, and scans add per-vCore-hour compute on top. A large cataloged estate with frequent scanning runs well above the single-unit baseline.

How does c3x estimate the cost?

From the always-on Data Map capacity unit (the standing cost). Scanning is usage-driven and modelled separately, since it depends on how much you scan and how often.

`azurerm_purview_account` cost estimation