- 5 min read
- November 2026
How Can You Measure Data Quality in Microsoft Dynamics 365?
Rebekah Harkin
In Microsoft Dynamics 365, data quality is measured by applying defined rules to CRM records and scoring how well they meet them. A required-field check identifies missing information, while a format rule highlights values that fall outside the chosen standard. The results give administrators a basis for deciding which records need reviewing.
Two records with the same score need not have the same problems. One might be missing an essential detail, while another contains a contact value that fails verification. This is why understanding the rules behind a score matters when deciding what needs attention.
With Data8 Data Integrity, we help Dynamics 365 teams configure quality rules and view the resulting scores in Dataverse. This supports ongoing data quality management by making the standards used to assess records visible and measurable.
What should a data quality score measure in Dynamics 365?
Data quality management in Dynamics 365 starts with the information needed for a record’s purpose. A contact used for email outreach needs an address suitable for that activity, whereas an account used for reporting depends on different fields. If every populated field carries equal importance, a missing optional value might affect the result as much as an essential one.
The main data quality dimensions include the following, although an individual score only measures the aspects covered by its configured rules:
- Completeness: Required CRM fields contain information.
- Validity: Values meet defined requirements, such as expected formats or supported verification checks.
- Consistency: Information follows agreed conventions, without conflicts between related values.
- Uniqueness: Records are assessed for duplication against the chosen criteria.
- Accuracy and timeliness: Real-world correctness and the continued relevance of information are assessed where reliable evidence is available.
In practice, these dimensions need different kinds of evidence. A populated email field meets a basic completeness rule but does not establish that the address is valid. Similarly, a date falling outside a chosen range identifies a record for review without proving the information is wrong.
Data8 Data Integrity can assess configured quality rules across large groups of CRM records, helping teams identify recurring issues and prioritise improvements. Where corrections are needed, the appropriate action depends on the issue identified and the information available.
How does Data8 Data Integrity calculate data quality scores?
One part of data quality management is deciding which conditions a CRM record should meet. Data Data Integrity assesses those conditions through configured rules in Dataverse. Administrators choose the table and scoring field, then define which criteria contribute to the result. Our Data Quality Rules guide describes the available settings.
Static scoring awards a configured value when a condition is met. Conditions include a populated field or a date within a specified range, while regular expressions provide a way to test a value’s format. Multiple criteria are supported within a rule.
The scope of each rule matters too. Filters determine which records are assessed against a particular condition. If a field is required only for a defined group of accounts, the filter restricts the check to that group rather than assessing every account against a requirement that does not apply to it.
Meanwhile, calculated scoring brings related records into data quality management by using their existing scores. An account score, for example, can average the scores of its associated contacts, where those contacts have configured static scores. The account result then represents the selected contacts’ scores rather than a direct quality check of the account’s own fields.
That average also depends on which related records are included. Data8 Data Integrity supports a view filter for calculated scores, so an Active Contacts view excludes inactive contacts from the calculation. The result reflects the selected contact population, which is useful when the quality of current contact information matters more than historical records.
Some rule types rely on additional products. Email and telephone verification scoring uses Data8 Validation, while duplicate-related scoring uses Duplicare. Our Score Types guide explains those dependencies.
These scores serve a different purpose from predictive lead scores in Dynamics 365 Sales. Data Integrity measures the configured quality criteria, whereas predictive lead scoring estimates the likelihood of a lead converting into an opportunity.
How do you use data quality scores to find CRM records that need attention?
In day-to-day CRM data quality management, understanding the reason behind an unexpected score is more useful than looking at the number alone. A missing email address fails a populated-field check. Where an address is present but fails a separate verification rule, the field contains information, but the relevant verification criteria have not been met.
Both checks are supported through Data Integrity, although email verification scoring requires Data8 Validation. Neither check supplies a replacement address. The appropriate response therefore depends on whether reliable information is available and how the contact record is used.
On the CRM record, our Data Quality Score Indicator displays the result with weighted improvement suggestions known as Quick Wins. These suggestions relate to rules the record has not satisfied. Their messages are customisable, allowing teams to explain the finding in terms that make sense to people working with the records.
The indicator also shows recent score changes and provides access to historical performance. A numerical score remains available without the custom indicator, as described in our Displaying the Score guide.
The same need for interpretation applies to duplicate-related scoring. Where Duplicare is configured, its scoring rule checks for unapproved duplicates. An unmet rule identifies an issue for review but does not establish that the records should automatically be merged.
What is a good data quality score in Dynamics 365?
There is no universal pass mark for Dynamics 365 data quality. An acceptable result depends on the rules selected and how important those requirements are to the records being assessed.
Email outreach makes the distinction clear. An address that fails verification is a greater concern than an empty optional field, even when the contact has a high completeness score. Comparing results across teams presents a similar problem, as identical scores do not necessarily reflect the same level of data quality when different rules or scoring values are used.
Benchmarks used in data quality management depend on agreed criteria and a clearly defined set of records. Without that shared basis, a percentage might look precise but reveal very little about the quality of the information being assessed.
How do you track data quality scores over time?
Data8 Data Integrity stores snapshots when scores change and retains rule-version information during recalculation. The score indicator shows previous results, giving administrators a history to examine when the current score differs from an earlier one.
That history helps with ongoing data quality management, provided the rules used at each point remain clear. Revised criteria or scoring values also affect results, so a higher score does not necessarily mean the underlying information has improved. Understanding what changed helps distinguish differences in measurement from differences in the records themselves.
Data Integrity supports batch recalculation and scheduling for relevant rules. This matters particularly for date-dependent checks, where the result might change as time passes even without anyone editing the record.
For reporting, Data8 Data Integrity offers the option to store improvement tips with score snapshots and link a record to its most recent snapshot. Those details provide context for analysis in tools such as Power BI when the reporting environment is configured. They do not amount to an automatically generated, organisation-wide quality dashboard.
Making CRM quality scores useful
Our Data8 Data Integrity solution supports data quality management in Dynamics 365 through configurable scoring and historical monitoring, giving your team a clearer view of how records meet its chosen standards. Our team is available to discuss your scoring requirements and arrange a Data Integrity demonstration through our contact page.