Dynamics 365 Duplicate Detection Rules: Complete Setup Guide

What Is Duplicate Detection in Dynamics 365?

Duplicate records are one of the most damaging data quality issues in any CRM system. A single contact appearing three times means three separate sales reps chasing the same lead, marketing emails going out multiple times to the same person, and service cases being created without context of previous interactions. In Dynamics 365, duplicate detection rules give you the power to prevent this – at the point of record creation and through bulk system jobs.

In this guide, you will learn how to configure duplicate detection rules in Dynamics 365 CRM from the ground up: creating rules, setting match criteria, enabling detection, and running bulk duplicate checks on existing data.

Duplicate detection in Dynamics 365 is a system-level feature that compares records against defined criteria when new records are created or updated. When a potential duplicate is found, Dynamics 365 warns the user or blocks the save – depending on your configuration. Duplicate detection works across all core entities including Contacts, Accounts, Leads, and any custom entities you have created. For teams connecting Dynamics 365 to external data sources, duplicate detection also applies when records are imported via data migration or synced from connected systems – see our guide on the D365 CRM SQL connection for more context.

Prerequisites

• System Administrator or System Customizer role in Dynamics 365
• Access to the Power Platform Admin Centre or Dynamics 365 Settings
• An active Dynamics 365 Sales, Customer Service, or Dataverse environment

How Duplicate Detection Works

When a user creates or updates a record, Dynamics 365 runs the active duplicate detection rules for that entity. If a match is found:

• Warning mode: The user sees a dialog showing potential duplicates and can choose to proceed or cancel
• Strict mode (via publisher config): The record cannot be saved until duplicates are resolved

Rules are also used in Bulk Duplicate Detection System Jobs, which scan your entire database and generate a report of existing duplicates.

Step 1: Enable Duplicate Detection

Before creating rules, ensure duplicate detection is enabled at the organisation level.

1. Navigate to Settings → Data Management → Duplicate Detection Settings.
2. Check Enable duplicate detection.
3. Optionally enable detection When Dynamics 365 for Outlook syncing, When records are imported via data import, and When records are created or updated.
4. Click OK.

Note: Enabling duplicate detection does not activate any rules yet – you still need to create and publish rules in the next steps.

Step 2: Navigate to Duplicate Detection Rules

1. Go to Settings → Data Management → Duplicate Detection Rules.
2. You will see any existing rules (Dynamics 365 includes several default rules for Contacts, Accounts, and Leads).
3. To edit a default rule, select it and click Unpublish first – you cannot edit a published rule.

Step 3: Create a New Duplicate Detection Rule

Let’s create a rule that detects duplicate Contacts based on email address.

1. Click New.
2. Fill in the form: Name: Duplicate Contact – Same Email Address, Base Record Type: Contact, Matching Record Type: Contact.
3. Under Duplicate Detection Rule Criteria, click Select to add a condition.

Step 4: Configure Match Criteria

Match criteria define which fields are compared and how strictly they must match. For email address matching:

Field (Base Record)	Criteria	Field (Matching Record)	Case-sensitive
Email	Exact Match	Email	No

To add this:

1. In the criteria grid, click New.
2. Base Record Field: Email
3. Criteria: Exact Match
4. Matching Record Field: Email
5. Case Sensitive: No (recommended for email)
6. Click OK.

You can add multiple criteria rows – all criteria use AND logic by default, meaning a record must match on all specified fields to be flagged as a duplicate. Recommended criteria combinations for Contacts:

Scenario	Criteria Fields
Strict email match	Email (Exact Match)
Name + company match	First Name (Exact) + Last Name (Exact) + Company Name (Exact)
Phone number duplicates	Business Phone (Exact Match)
Fuzzy name match	Full Name (Same First Characters, 5)

Tip: Use “Same First Characters” criteria for name fields to catch typos (e.g., “Jon” vs “John”). Set the number of characters to 4–5 for a good balance of accuracy.

Step 5: Publish the Rule

1. With your rule configured, click Save and Close.
2. Back in the Duplicate Detection Rules list, select your new rule.
3. Click Publish in the ribbon.
4. The rule status will change to Published.

Published rules are active immediately – any new or updated Contact record will now be checked against this rule.

Step 6: Test the Rule

1. Navigate to Contacts and open an existing contact record.
2. Note their email address.
3. Click New to create a new Contact.
4. Enter the same email address and click Save.
5. Dynamics 365 should display a Duplicates Detected dialog showing the existing contact as a potential match.

If the dialog does not appear: confirm the rule is published, confirm duplicate detection is enabled in Settings, and refresh your browser cache.

Step 7: Run a Bulk Duplicate Detection Job

Existing records created before the rule was published are not automatically checked. Use a Bulk Duplicate Detection System Job to scan historical data.

1. Navigate to Settings → Data Management → Duplicate Detection Jobs.
2. Click New and name the job: Contact Email Duplicate Scan – [Date]
3. Set the entity to Contact and select All records.
4. Set an email notification recipient, then click Next → Next → Submit.

For teams managing large data volumes, consider scheduling these jobs monthly and pairing them with Power Automate flow monitoring for automated alerts.

Step 8: Merge Duplicate Records

When duplicates are found, Dynamics 365 provides a native Merge function.

1. Open one of the duplicate records.
2. Select the other duplicate from the Duplicates Detected dialog or search.
3. Click Merge in the ribbon (available on Account, Contact, and Lead).
4. In the Merge dialog, choose the Master Record (the one to keep) and select which field values to retain.
5. Click OK to merge.

Important: Merging is permanent. The subordinate record is deactivated, and all related records are re-parented to the master record.

Best Practices

• Start with email and phone rules – these are the most reliable unique identifiers
• Avoid over-matching – too many criteria can flag legitimate similar records as duplicates
• Review and tune rules quarterly – business data patterns change over time
• Combine with import-time detection – always enable detection during data imports
• Train users – ensure your CRM users understand what to do when the Duplicates Detected dialog appears

For organisations using Outlook email tracking with Dynamics 365, duplicate detection on Contacts is especially important – email tracking links to Contact records, and duplicates create fragmented activity histories.

Conclusion

Duplicate detection rules are a foundational element of any well-managed Dynamics 365 environment. By investing 30 minutes in setting them up correctly, you protect years of data quality, improve user trust in the CRM, and prevent the operational headaches that come from fragmented customer records. Start with the core entities – Contacts, Accounts, and Leads – and expand to custom entities as your data governance maturity grows. Pair your rules with regular bulk detection jobs and a clear process for reviewing and merging flagged records. Need help reviewing your Dynamics 365 data quality setup? AlphaVima offers CRM health checks and data governance consulting. Contact our team today.