A unified data governance solution that helps manage, protect, and discover data across your organization
Based on the current Microsoft Purview documentation, here's what can be confirmed:
- Data Profiling is part of the Microsoft Purview Data Quality capability in Unified Catalog.
- Data Quality usage is billed using Data Governance Processing Units (DGPUs), and the billing documentation states that the Enterprise Data Management meter starts when you run data quality and data health management actions.
- A DGPU is a managed compute unit used for compute-intensive capabilities such as Data Quality and Data Health Management, and its consumption varies depending on factors such as the workload, data volume, source type, and processing performed.
However, the documentation doesn't explicitly state whether executing a standalone Data Profile is billed as a separate DGPU-consuming operation or whether its compute is included within the broader Data Quality processing.
Similarly, while Microsoft publishes DGPU examples for data quality rule execution (for example, DGPU per rule per run), it doesn't publish a profiling-specific DGPU rate or billing example. Therefore, we can't definitively state whether each Data Profile execution incurs DGPU consumption or provide a fixed DGPU cost based solely on the published documentation.
If you would like to validate the behavior in your own environment, you can:
- Review Usage Monitoring (Preview) in Microsoft Purview after running a Data Profile job to observe DGPU consumption.
- Check Azure Cost Management for the Enterprise Data Management meter to correlate the usage.
References
- https://learn.microsoft.com/purview/data-governance-billing
- https://learn.microsoft.com/purview/purview-billing-models
- https://learn.microsoft.com/purview/unified-catalog-data-quality
Please let us know if you have any further questions.
If this solution helped resolve your issue, please consider clicking ‘Accept Answer’ or giving it an upvote to help others find it easily.