Data Quality Responsibilities for Data Products

Understand how Data Product Owners and Data Stewards use data quality evidence while specialist Data Quality Steward permissions control quality operations.

Data quality is an important part of deciding whether a data product is fit for use.

Owner and steward responsibilities

Data Product Owners and Data Stewards should understand the quality expectations for the product, review available quality results and make sure consumers can see relevant evidence about fitness for use.

Data Quality Steward permissions

Running Microsoft Purview data quality operations such as rule management and data quality scanning requires Data Quality Steward permissions. Data Quality Steward is a governance-domain sub-role and currently requires the user to also hold Governance Domain Reader and Data Product Owner roles.

Typical quality lifecycle

  • Register and scan the data source.
  • Add the data asset to the data product.
  • Configure the source connection for quality assessment.
  • Profile the data.
  • Create and apply data quality rules.
  • Run quality scans.
  • Review results and repeat the assessment over time.

The Data Product Owner remains accountable for whether the product is suitable for its intended use, while operational quality work can be delegated to suitably permissioned stewards or specialists.

Learning with Data SkyLab Studio

Follow practical Microsoft Purview and Data Governance learning from Data SkyLab Studio on YouTube.