Bemærk
Adgang til denne side kræver godkendelse. Du kan prøve at logge på eller ændre mapper.
Adgang til denne side kræver godkendelse. Du kan prøve at ændre mapper.
A data quality threshold is a predefined limit that determines whether data meets an acceptable level of quality. In simple terms, it answers the question: How good is good enough?
For example, if you run a completeness rule on a column:
- Total records: 1,000
- Records with values: 920
- Completeness score: 92%
If your threshold is 90%, the data meets the expectation.
If your threshold is 95%, the data doesn't meet the expectation.
The threshold is the cutoff point that defines whether the data meets the expectation for specific use cases.
Why thresholds matter
Different types of data require different quality expectations. For example:
- Email address column: Might require 99–100% completeness.
- Description column: Perhaps 80–90% is acceptable.
- Financial transactions: Might require 100% accuracy.
Using one fixed threshold, such as 80% for everything, can be misleading, especially for critical or regulated data.
Types of thresholds
- Rule-level threshold: Set for each rule (for example, completeness must be ≥ 95%).
- Data asset level threshold: Different expectations for different columns.
- Data product level threshold: Overall score requirement.
Configurable data quality thresholds
You can configure Data Quality thresholds to set minimum acceptable quality scores at the rule and data asset levels. Define the threshold to align quality evaluation with business criticality.
Configure or edit the default threshold for a data asset
In Microsoft Purview Unified Catalog, select Health management, and then select Data quality.
Select a governance domain, select a data product, and then select a data asset.
On the Overview page, select Set score threshold.
Change the default threshold.
Select Save.
Configure the threshold for a data quality rule
- In Unified Catalog, select Health management, and then select Data quality.
- Select a governance domain, select a data product, and then select a data asset.
- On the Rules page, select New rule.
- Select the out-of-the-box rule or the custom rule, and select Next.
- Select Score threshold and change the default threshold value.
- Select Save.
Edit a data quality rule threshold
- On the Rules page of a data asset, select the edit icon for a rule.
- From the overview, select Score threshold.
- Edit the threshold value.
- Select Save.
Configure alerts
Set an alert to notify you when the data quality score of a data asset or rule falls below a defined threshold. When you set up or edit a rule threshold, follow these steps:
- Set the Alert toggle to on.
- At Recipient, add one or more users.
- Select Save.
Note
If you don't configure a threshold, the default threshold values and colors are used. The default threshold score values are:
- Low (red): 0-40
- Medium (orange): 40-80
- High (green): 80-100
The benefits that an organization gets from the configurable data quality threshold feature are:
- Enables the enterprise to align their organization with quality governance.
- Improves trust in the data quality scores produced by Microsoft Purview Data Quality, enabling teams across the enterprise to confidently determine whether data is fit for their specific use cases.
- Helps organizations move beyond generic quality checks and toward business-driven data quality management.
- Supports regulatory and decision-critical use cases.
- Reduces user or organizational confusion caused by uniform threshold evaluation.
Setting rule-level thresholds creates a clear standard for what "good" looks like. Alerts ensure you act the moment data drifts below that standard. This has several practical benefits:
- Early detection of issues: Catch things like missing, inconsistent, or incorrect data before they impact reports, pipelines, or models.
- Reduced business risk: Prevents bad data from driving incorrect decisions, financial errors, or compliance issues.
- Faster remediation: Alerts enable teams to respond immediately instead of discovering issues days or weeks later.
- Accountability and governance: Clear thresholds define ownership and expectations for data quality.
- Operational efficiency: Eliminates manual monitoring and reduces reliance on ad hoc checks.
- Trust in data: Consistent enforcement of quality standards increases confidence in analytics and AI outputs.
In short, thresholds define acceptable quality, and alerts make that standard actionable.