Microsoft Purview · Unified Catalog Governance
Data Quality Metadata Reader
Browse data quality insights, rule definitions, and scores. Sub-role requiring Governance Domain Reader and catalog reader.
Scope: Read-only access to quality metadata within domain
Permissions
- Browse data quality insights (except profiling column-level)
- View data quality rule definitions
- Access rule-level quality scores
- Cannot access error records
- Cannot run profiling or quality scanning jobs
- Read-only access to quality metadata
Common use cases
- Auditors reviewing quality control implementation
- Compliance teams verifying quality rules exist
- Management monitoring quality rule coverage
- Documentation teams describing quality controls
- External consultants assessing quality maturity
Best practices
- Assign to auditors and compliance reviewers
- Use for quality control transparency
- Provide visibility into quality governance
- More limited than Data Quality Reader (no error records)
- Combine with Global Catalog Reader for broad assignment
Security considerations
- Most restrictive quality-related reader role
- Cannot see error records or data samples
- Read-only with minimal security concerns
- Safe for external auditors and broad assignment
- No access to operational quality data
Common questions
When should I assign the Data Quality Metadata Reader role?
Assign Data Quality Metadata Reader when you need to: Auditors reviewing quality control implementation; Compliance teams verifying quality rules exist; Management monitoring quality rule coverage; Documentation teams describing quality controls; and External consultants assessing quality maturity. It is part of Microsoft Purview and should be granted as a least-privilege alternative to broader roles like Global Administrator.
What can someone with the Data Quality Metadata Reader role do?
The Data Quality Metadata Reader role grants permissions including: Browse data quality insights (except profiling column-level); View data quality rule definitions; Access rule-level quality scores; Cannot access error records; Cannot run profiling or quality scanning jobs; and Read-only access to quality metadata. See the Permissions section above for the full list.
What are the security risks of the Data Quality Metadata Reader role?
Key considerations when assigning Data Quality Metadata Reader: Most restrictive quality-related reader role; Cannot see error records or data samples; Read-only with minimal security concerns; and Safe for external auditors and broad assignment. Review the Security considerations section before assignment, and pair with Privileged Identity Management (PIM) for just-in-time access where possible.