Duplicate Detection Rules Not Working in Dynamics 365? Here Is Why

You set up duplicate detection rules, published them, and duplicates keep appearing anyway. This is one of the most common frustrations with Dynamics 365, and in most environments it has several causes stacked on top of each other. Here is the full checklist, from configuration mistakes you can fix in five minutes to hard limits you cannot configure around.

The quick checklist: nine reasons rules do not fire

1. Duplicate detection is disabled globally. Go to Settings, Data Management, Duplicate Detection Settings. If the global option is off, no rule fires anywhere, regardless of its own status.
2. The rule is not published. A rule that exists is not a rule that runs. Check the status on each rule; only Published rules are evaluated.
3. The rule was unpublished by an edit. Editing a rule unpublishes it, and it stays unpublished until someone republishes it manually. This is the classic silent failure: a small change months ago, and detection has been off ever since.
4. A solution import or environment copy reset it. Deployments and sandbox refreshes can leave duplicate rules unpublished. Add a republish step to your release checklist.
5. The matchcode is over the 450-character limit. All criteria in one rule share a combined matchcode budget of 450 characters. Exceed it and the rule cannot publish.
6. You hit the five-rule limit. Dynamics 365 allows at most five published duplicate detection rules per table. A sixth rule means unpublishing one of the others.
7. The record slipped through the matchcode window. Matchcodes are generated asynchronously, up to five minutes after a record is created. Two records created within that window do not see each other.
8. The integration bypasses detection. Records created through the API can suppress duplicate detection entirely, and many integrations do exactly that for speed.
9. Users click Ignore and save. Native detection warns; it does not block. Under time pressure, the warning dialog becomes a formality.

The limits you cannot configure around

Fixing the checklist above gets the native rules working exactly as Microsoft designed them. The harder problem is what that design does not cover.

Exact matching only. Native rules compare matchcodes literally, with only the exact, same-first-characters and same-last-characters operators. Jon Petersen and John Pedersen will never collide, no matter how you configure the rule. This whole class of hidden records is covered in the duplicate you cannot see: phonetic matching in Dynamics 365.

Detection, not resolution. Even when the dialog fires, the native experience merges one pair at a time by hand. At a few hundred duplicates that is a project; at tens of thousands it is simply not happening. One of our enterprise customers had more than 2 million duplicate records, which is not a number anyone merges manually.

No ongoing measurement. Native detection cannot tell you whether your database is getting cleaner or dirtier over time, so problems only surface when someone trips over them.

What a complete approach looks like

The Data Quality App treats the native limits as the starting point. Duplicate detection runs with exact, fuzzy and phonetic matching, in the foreground while users work and in the background across the entire database, on any entity, with filtering to scope each analysis. Confirmed duplicates are resolved with merge and bulk merge instead of one dialog at a time.

Prevention then moves upstream of the duplicate: data quality rules on every table enforce requirements at the point of entry, from required fields and formats to rules like requiring at least one of email or phone, so the sloppy record that becomes tomorrow’s duplicate is corrected today. Data Health Studio measures the result over 30, 60 and 90 days, which turns data quality from a one-off cleanup into something you can actually manage.

The fastest way to see where you stand is the free 15-day trial: it analyzes your full environment and reports every duplicate the native rules missed, before you commit to anything.

Frequently asked questions

Why does Dynamics 365 not detect duplicates during import or integration?

Duplicate detection during import must be explicitly enabled in the import wizard, and API-based integrations can suppress detection entirely. Records created moments apart can also miss each other because matchcodes are generated asynchronously, up to five minutes after creation.

How many duplicate detection rules can I have in Dynamics 365?

You can have up to five published duplicate detection rules per table, and the combined matchcode of each rule is limited to 450 characters. Rules also become unpublished whenever they are edited, and must be republished manually.

Can Dynamics 365 do fuzzy or phonetic duplicate matching?

Not natively. The built-in rules support exact matchcode comparison only. Catching typos, spelling variants and sound-alike names such as Kristensen and Christensen requires a dedicated tool like the Data Quality App, which adds fuzzy and phonetic matching plus bulk merge.