Dynamics 365 Customer Insights Forms: Stop Duplicate Leads
Dynamics 365 Customer Insights forms with a lead audience make a new lead on each submission by default. Add a lead matching rule, then merge duplicates.
Here is a hypothetical. One visitor fills in three Dynamics 365 Customer Insights forms in a week: a gated download, a pricing request and a contact-us form. Each submission creates a new lead. Each lead gets its own owner from assignment, its own score and its own row in your routing reports. Then a sales manager asks you why one person has three leads with three owners.
The cause fits in one line. Microsoft documents the default for the Lead audience as “Always create a new record”.
You own the lead table, so this is your problem. Scoring reads from that table, routing assigns from it, and SLA reports count it. A duplicate lead does not stay a cosmetic issue. It shows up downstream as a wrong number.
Takeaway: if a Lead or Lead & Contact form still uses the out-of-the-box audience setting, assume it creates a new lead on every submission today.
How Dynamics 365 Customer Insights - Journeys handles duplicates by default
Microsoft states the defaults plainly on Manage Customer Insights - Journeys forms:
“The default way to handle duplicate records is different for contact and lead entities. Contact (default: Update contact using email): When a user submits a form with an existing email address, the form updates the existing record and doesn’t create a new record. Lead (default: Always create a new record): When a user submits a form with an existing email address, the form creates a new record with the same email address. Lead & Contact (default: Update contact using email and always create a new lead): When a user submits a form with an existing email address, the form updates the existing contact and creates a new lead.”
The trap is in that last line. Lead & Contact looks like the safe, combined option because the contact side matches on email. The lead side does not. It updates the contact and still creates a new lead every time.
Contact is not the problem. By default a Contact form updates the existing record when the email matches. The default configuration page describes the out-of-the-box Lead setting the same way the manage page does: “Always create a new lead, even if the same lead already exists (no matching rules apply).”
| Audience | Default behavior (quoted) | Creates duplicate leads by default? | What to change |
|---|---|---|---|
| Contact | “Update contact using email”: the form “updates the existing record and doesn't create a new record” | No. It creates no lead at all | Nothing for lead dedupe |
| Lead | “Always create a new record”: the form “creates a new record with the same email address” | Yes | Switch to “Use a rule to match existing record” and select a lead matching rule |
| Lead & Contact | “Update contact using email and always create a new lead” | Yes, on the lead side | Switch the lead side to “Use a rule to match existing record” and select a lead matching rule |
Takeaway: Lead and Lead & Contact forms both need a lead matching rule. Contact-only forms don’t.
Build the lead matching rule (Settings > Matching rules)
Microsoft’s Matching rules for forms and journeys page gives the creation steps:
- “Go to Settings > Matching rules, and select New in the top ribbon.”
- “Enter a name for your new rule. This name is used to select the rule when creating new forms or journeys.”
- “Select the target entity, which can be a lead or contact.” Choose Lead.
- “Select the Save button.”
- “The matching rule is created, and you access it in the Conditions tab.” Add your conditions there.
My position: the main condition is emailaddress1, and nothing else to start. Microsoft says the main condition “is a direct query to database, so the degree of match is always Exact (it isn’t possible to set up fuzzy matching).” Email is the one field on a lead form that a person types the same way every time and that the form can require.
Be careful with additional conditions. Microsoft says “All conditions are linked by an AND operator.” Its Example 1 uses emailaddress1 in the main condition and mobilephone as an additional condition. The result is that the record updates only “if the email address and phone number match the values stored in the record.”
That reads like a stricter, safer rule. In our experience it is the opposite. An AND condition on an optional field quietly brings duplicates back the first time someone leaves the field blank or types the number differently, because the rule finds no match and the form creates a new lead.
If you truly need email OR phone, follow Example 2: “Use emailaddress1 as the attribute in the main condition. Add mobilephone as an additional attribute to the same condition.” Inside a condition, “There’s always an OR operator between the attributes.”
Fuzzy matching exists only on additional conditions. The Degree of match values are “Exact: All of the characters must match. High: Almost all of the characters must match. Medium: At least half of the characters must match. Low: At least a quarter of the characters must match.” Keep fuzzy matching off lead rules unless you can show a specific case that needs it. Additional conditions are “executed on the group of records filtered out by the main condition”, so a fuzzy name check can only narrow the leads your email condition already found. It never brings in a lead the email missed. In our experience a Low match narrows that group so little that it adds nothing.
Leave Match inactive records Off. Microsoft says “Matching an inactive record doesn’t reactivate the record. Inactive records have the same priority for matching as active ones. It’s recommended to keep this toggle Off.”
Know what happens when the rule finds more than one record: “If the matching rule finds multiple existing records, the latest updated record is used.” The rule does not fail. It picks one. With a clean table, that behavior is fine. With three leads for the same email, the new submission lands on whichever was touched last, which is why the cleanup section below is not optional.
As an illustration, take a rule named “Lead: match on email only”, target entity Lead, main condition emailaddress1, no additional conditions, Match inactive records Off. The name matters more than it looks. Form builders select the rule by name, so make it obvious which one is the lead rule.
Takeaway: one email-first lead rule, named clearly so form builders pick the right one.
Apply it: per form first, then the defaults
The rule does nothing until a form uses it. Microsoft says: “Change the default matching rule by using the Duplicate records drop-down in the Forms settings.” Per form, the Audience setting is where you “Set how to handle duplicate records by selecting the matching rule. Choose whether form submission creates new records or updates existing records.”
The default configuration page describes the choice itself. There are two options: “Always create a new contact: A new contact is always created. No matching rules are applied. Use a rule to match existing record: Use a matching rule to find an existing record and avoid duplicates.” The page walks through a Contact audience and then says “You see the same details for a Lead audience. The Lead & Contact audience lets you set separate details for both contact and lead.” On a Lead & Contact form, you set the lead side separately.
Here is the practitioner caveat. Microsoft describes the default configuration this way: “The form configuration feature lets you preset all your new forms.” It documents no effect on forms that already exist. Do not rely on the defaults to fix live forms. Open every live form’s Audience settings and change it there. Then update the out-of-the-box Audience settings so the next form starts right.
Three settings go alongside the rule.
Create a new record if there was no match = Yes. (Microsoft documents the contact-side label, “Create a new contact if there was no match to an existing one?”, and says “You see the same details for a Lead audience.”) Microsoft describes the No option on the contact side as “No new record is created. The form submission data can be accessed only through the form submission.” On a lead form, that means a brand-new prospect produces no lead at all.
Update matched record with submitted data (contact-side label: “Update matched contact with submitted data”). Microsoft: “Yes: The best matching record is updated with form submission data. No: The matched record isn’t updated with form submission data. The form’s submission data is only linked to the matched record.” In our experience Yes is right for most lead forms, because sellers want the latest company name and phone on the record they already own.
Ignore empty values = On. From the Ignore empty values section: “Toggle off (disabled): The existing value is overwritten by the empty input. Toggle on (enabled): The existing value stays and isn’t replaced by the empty input.” Without it, a blank phone field on a short form wipes the phone number your seller already has.
Then mark every matching field as required. Two separate Microsoft statements apply here, and they are not the same thing. Among the “Errors that block form publishing”, the form must include “all attributes required by the matching rule (email field by default).” Separately, Microsoft advises: “To prevent unexpected results, don’t use empty values for matching. Make sure all form fields used for matching are set as required.” A missing attribute blocks publishing. A present but optional field is allowed, and it is where unexpected results come from.
Know what changes on update and what doesn’t. According to form submission processing, attributes including ownerid and, if the business units feature is enabled, owningbusinessunit are set when the form creates a new record, and for leads subject is set too, where “the form name is used as the value”. Microsoft adds: “These attributes don’t update when a form submission updates an existing record.” The owner stays with the original lead. In our experience that is usually what routing wants: the second submission goes to the seller already working the person.
Link tracking also matters. Microsoft says that when a user “is identified through link tracking, and the submitted values match the matching rule, the existing record (contact or lead) identified by link tracking is updated. If the submitted values don’t match the matching rule, link tracking isn’t used, and the last modified record is updated.” On Lead & Contact forms, “The matching rule for contacts is applied first. If a child lead is found for the matched contact, the child lead is prioritized in the lead matching rule evaluation if the existing lead meets all the conditions defined in the lead matching rule.”
- 1
Audience
On each live Lead or Lead & Contact form, change the lead side from always creating a new lead to “Use a rule to match existing record”.
- 2
Lead matching rule
Select your email-first lead rule by name. On Lead & Contact forms, set the contact and lead sides separately.
- 3
Create if no match
Set the create-a-new-record-if-no-match option to Yes so new prospects still become leads.
- 4
Update matched
Decide on updating the matched lead with submitted data. In our experience Yes fits most lead forms.
- 5
Ignore empty values
Turn the toggle on so blank fields don't clear existing values.
- 6
Required fields
Make sure every attribute in the rule is on the form, and mark each matching field as required.
- 7
Save the live form
On a live form, select Edit, make the changes and select Save. Microsoft says “All changes are automatically published when you select the Save button.”
- 8
Verify
Submit a test using the email of an existing test lead. Confirm no new lead appears and the existing lead shows the submission.
Takeaway: the fix is per form. Defaults are for the future.
Clean up the duplicates that already exist
Microsoft describes matching rules only at submission time and when a journey creates a lead: “Matching rules can be applied in marketing and registration forms, and when creating new leads during a journey.” It does not describe them as a way to merge or clean up duplicates already in Dataverse. Once every live form uses the rule, your Dynamics 365 Customer Insights forms stop creating a second lead for an email that already has one. The old ones stay until you merge them.
Do the cleanup now, before or straight after the form fix. Otherwise the latest-updated behavior attaches each new submission to whichever duplicate someone touched last, and your three leads become three partially updated leads.
Use the Dataverse tools for the bulk pass:
- Create and publish lead duplicate detection rules on email, and turn duplicate detection on. That is Microsoft’s prerequisite for the wizard: “create and publish duplicate detection rules, and turn duplicate detection on before you run the wizard” (Run bulk system jobs). Microsoft recommends a field “that has unique values, for example, Email”, and notes you can compare across tables: “you might want to compare the Email field in Contacts to the Email field in Leads” (Set up duplicate detection rules). Plan your rules, because “you can publish a maximum of five duplicate detection rules per table type at one time” (Detect duplicate data).
- Run the Check for Duplicates wizard. It “helps you set up a bulk ‘job’ that finds and cleans up duplicate records. You can schedule the job to run daily.” If you do, set up a Power Automate alert on failed system jobs so a run that breaks doesn’t go unnoticed. That walkthrough is built for workflow jobs, so add the Bulk Duplicate Detection job type (
operationtype8 in the System Job reference) to its filter. Expect to run it more than once on a large table: “A maximum of 5,000 duplicates are returned by the duplicate detection job” (Run duplicate detection). - Merge, lead to lead. Per Detect duplicate records and merge, “Merging duplicate records from different tables is not supported.” Nothing is deleted: “The primary record is kept, and the secondary record is deactivated,” and “All notes, activities, and details associated with the secondary record are linked to the primary record.” Pick the primary deliberately. Our recommendation is the lead with the right owner and the real history, not whichever row the grid shows first.
- Re-check a sample. Open merged leads and confirm owner, score and routing queue match what the business expects. If you run lead scoring models, Microsoft warns that after a merge “the scoring models don’t score the primary record” until you manually delete the score of the merged non-primary leads or republish your scoring models (Create lead scoring models).
Which default rules you start with is a genuine documentation conflict. Run duplicate detection says “Dynamics 365 includes default duplicate detection rules for accounts, contacts, and leads.” Set up duplicate detection rules says the apps “include default, duplicate detection rules for accounts and contacts, but not for other types of records.” Two Learn pages, two answers. Open the duplicate detection rules list in your own environment and check before you assume either.
Dynamics 365 Sales has its own option. With duplicate lead detection enabled, “the AI model uses the following rules to identify duplicates: Same email address, Same phone number, Similar lead name and company name, Similar lead name and the same email domain,” and “Sellers can compare and remove the duplicate leads in the organization.” Microsoft also says: “For an optimal experience of the duplicate detection of leads in Dynamics 365 Sales, disable the duplicate detection of leads in Microsoft Power Platform.”
That creates a sequencing decision, and my answer is this. Use the Power Platform rules and the Check for Duplicates wizard for the one-time bulk cleanup, because the wizard needs those rules published. Once the backlog is merged, pick one mechanism for ongoing seller-side checks. If you choose the Sales feature, that is the point to disable Power Platform lead detection, as Microsoft advises. Don’t run both on leads indefinitely.
In our experience the cleanup goes wrong in one place: teams merge and immediately retune scoring on the merged data before anyone has looked at a sample. Owners shifted, histories combined, and the first scoring pass after a merge reflects the merge as much as the buyers.
Takeaway: freeze scoring and routing changes until the duplicate sets are merged and a sample checks out.
Three more checks while you are in the forms
Resubmitting failed submissions. The forms troubleshooting page says “By resubmitting, you might create a duplicate contact” and “Resubmitting runs the entire submission process again. To avoid duplicate records, you can change the matching strategy before you resubmit.” Fix the rule first, then resubmit.
Old outbound marketing forms. Outbound marketing “was removed in May 2026,” and its forms “weren’t removed” but “can’t be used in real-time” (removal notes). Any lead matching you set up there is history. Real-time forms follow the audience and matching rule settings above.
The matching rule protects the lead table from today forward. Your merge and verification pass is what makes yesterday’s data fit for scoring and routing. The rule has to be set on every live form, not just in the defaults.
Takeaway: republish each form once, with the matching rule and reCAPTCHA both in place.
Prove the whole path holds
You’ve fixed the forms and merged the backlog. The next question is whether a lead that arrives clean stays clean all the way to a seller. Citizen Development Academy runs a 30-minute Lead-to-Revenue Review. We walk one real lead from form to first seller touch and check five points: shared lead definition, capture and dedupe, scoring readiness, routing and SLA, and handoff feedback and reporting. Nonprofits can get help free.
Request a 30-minute Lead-to-Revenue Review with Citizen Development Academy