Sales and Marketing Alignment in Dynamics 365: 5 Settings

Gartner surveyed 243 CSOs and senior sales leaders from November through December 2024 and found that “49% of CSOs report their sales organization’s definition of a qualified lead differs greatly from marketing’s definition” (Gartner press release, May 21, 2025). Sales and marketing alignment means both teams work from one written lead definition, one handoff field and one feedback loop, enforced in the CRM.

More alignment meetings will not fix that 49%. The disagreement does not live in the room. It lives in fields, defaults and rules that nobody wrote down. Robert Blaisdell, VP Analyst, Chief of Research in the Gartner Sales Practice, put it this way: “The alignment between sales and marketing teams is increasingly crucial for achieving strategic goals and driving revenue growth.” I agree. I would add that alignment you cannot see on a lead record does not exist.

A lead you want sellers to work passes seven stops in Dynamics 365: form, matching rule, scoring, qualification, assignment, sequence and SLA, and feedback closes the loop. Each one is a place a lead goes missing. Those seven stops collapse into five settings both teams have to sign off on. As a marketing leader, you own the first three by default, even if you have never opened them. And for the Lead audience, the out-of-the-box form already creates a new lead every time a known person submits again.

If the two teams cannot point to the same field on the same lead record, they are not aligned. They are only polite.

The five checkpoints, and the default at each one

Checkpoint	The Dynamics 365 setting	Default behaviour	Who owns it	Where the lead gets lost
Shared lead definition	Lead scoring model plus qualification criteria in Customer Insights - Journeys	Grades “aren’t mandatory”	Marketing, signed by sales	Sellers ignore a score nobody explained
Capture and dedupe	Form Duplicate records setting and matching rule	Lead: “Always create a new record”	Marketing	Repeat submitters become separate leads
Scoring readiness and qualification	Status Reason = Marketing Qualified, or Sales-Ready = Yes	Scores refresh every two hours; a lead “remains as Marketing Qualified” when its score drops	Marketing	Stale or reversed scores still look ready
Routing and SLA	Segments, assignment rules and an enhanced SLA on Lead	A rule “considers only the records that are created or updated after activation”	RevOps, on marketing’s requirements	Backlog never routes; nothing flags a slow touch
Handoff feedback and reporting	A shared reason list on disqualified or returned leads (our design, not a Microsoft default)	If no opportunity is created, “the business process flow doesn’t progress”	Sales and marketing jointly	”Junk” is never defined, so nothing changes

Read the “Who owns it” column twice. The first three rows sit in the app your team runs.

Sales and marketing alignment starts with a lead definition written as data

Checkpoint 1: shared lead definition.

Your lead definition is not the slide in the quarterly business review. It is the lead scoring model in Customer Insights - Journeys. Microsoft’s description is plain: “Dynamics 365 Customer Insights - Journeys scores leads using demographic attributes and interactions” (Create lead scoring models). Two constraints matter at your level. The Lead Management feature switch has to be enabled, and “You can only use Dynamics 365 standard interactions to create conditions.”

Two caveats belong in every conversation with your sales counterpart.

First, timing. “Scoring models refresh every two hours.” Do not promise sales an instant score. A lead that downloads three assets at 9:00 may not look hot until the next refresh, up to two hours later.

Second, grades. “As a reminder, grades aren’t mandatory, and you can publish the model without defining any grades.” The docs allow it. In our experience, you should define grades anyway, because a grade is the part sellers actually read. A seller glances at “A” in the list view. Nobody reverse-engineers a points total.

Then make the number visible. The Lead Score Viewer role exists for “Marketers and salespeople that should see calculated lead scores (must be combined with one of the other marketing and/or sales roles)” (Manage user accounts, user licenses, and security roles). If sales cannot see the score, the definition is marketing’s private opinion.

One more trap if your model is old. Outbound marketing “was removed in May 2026.” Its lead scoring models and forms “weren’t removed,” but “These assets can’t be used in real-time” (Notes about outbound marketing removal). A definition that lived there has to be rebuilt, not migrated.

Get the thresholds signed by both leaders and stored as the published model, not as a deck.

Capture and dedupe: the default form creates the duplicate you later blame on sales

Checkpoint 2: capture and dedupe.

Every form in a Dynamics 365 Customer Insights journey picks an audience, and each audience has its own duplicate default (Manage Customer Insights - Journeys forms):

• Contact is “Update contact using email.”
• Lead is “Always create a new record.”
• Lead & Contact is “Update contact using email and always create a new lead.”

Here is what the Lead default means. When a known person submits again, “the form creates a new record with the same email address.” In our experience, each of those lead records can then be scored, routed and worked on its own. Two sellers call the same person. Sales calls it a junk lead. It is a form setting.

The fix is a lead matching rule. Microsoft says to “Change the default matching rule by using the Duplicate records drop-down in the Forms settings.” Know what a matching rule is and is not. “The main rule is a direct query to database, so the degree of match is always Exact (it isn’t possible to set up fuzzy matching)” (Matching rules for forms and journeys). Microsoft also warns: “don’t use empty values for matching. Make sure all form fields used for matching are set as required.” If email is your match field, email is required on every form.

Do not confuse that with duplicate detection on the Sales side, which works differently. “Dynamics 365 Sales detects duplicates with an AI model that compares leads using fuzzy logic and the matchcode that is generated for each lead” (Lead management FAQs). And it has teeth: “If the duplicate detection rules feature is enabled in your organization, the application won’t allow qualification of leads if duplicates of that lead exist.” If that feature is on, your form default becomes their blocked Qualify button.

Cleanup has a cost too. If you merge duplicate records, “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). Fixing capture upstream is cheaper than merging downstream.

Open every live lead form this week and check two things: the Duplicate records setting and the captcha element.

Qualification: one field flips, and that is the handoff

Checkpoint 3: scoring readiness and qualification.

Qualification criteria do one thing. “Actions are updates to the Status Reason (as Marketing Qualified) or Sales-Ready (as Yes) attribute of the lead entity” (Qualify the best leads).

Then Microsoft says that once the lead is updated, “you can” trigger a journey, “Assign leads to your sales team using Dynamics 365 Sales assignment,” or “Trigger a sales sequence.” Read the word “can.” Nothing routes until someone wires it, usually with Sales assignment or with the kind of Power Platform extensions to Dynamics 365 your RevOps team already builds. A flipped field with nothing listening is a lead that looks handed off and is not.

Three behaviours to know before you promise anything:

• “only leads in an open status can be marketing-qualified.”
• If scores later drop below the threshold, “the lead remains as Marketing Qualified.”
• “To add or modify new qualification criteria, you need to stop the current qualification model.”

Because of that, plan a review window for changes instead of editing live.

Journeys can now act on the handoff directly. Record creation from journeys reached general availability in the September 2026 update (What’s new). Microsoft’s own example: a trigger-based journey “starts when a lead submits a pricing request form,” then a Create a record tile creates a Phone Call (Create records and activities from journeys). It works on contacts and leads, and “It doesn’t support Customer Insights - Data profiles.” Test before you trust it: “Publishing a journey doesn’t guarantee that all records will be created. You should test the journey with a sample audience and review execution results before using it with live data.”

For attribution, Microsoft’s August 2026 release notes list a “Track journey origin” enhancement that stamps created records “with live journey metadata.” Treat it as a release-notes item and ask RevOps whether it is live in your environment.

Decide which single field is the handoff signal, Sales-Ready or Status Reason, and report on that field only.

Routing with an SLA: what to require from RevOps, and the limits that bite

Checkpoint 4: routing and SLA.

You do not configure assignment rules. You do write the requirements, and these are the ones worth fighting for.

In our experience, the cleanest wiring is a work assignment segment whose condition is Sales-Ready = Yes. That design is ours, not documented automation. Ask for it by name.

Then know the limits (Create and activate assignment rules). “A rule considers only the records that are created or updated after activation.” Test with new leads, and do not expect the backlog to move when the rule goes live. Rules apply top down, and “If a record meets the conditions of a rule, that rule is applied and no other rule is considered.” Order is policy. A segment “can have any number of assignment rules, but only 10 rules can be active at one time” (Create segments).

Pick the distribution method on purpose. Round robin “distributes the records evenly in turn.” Load balancing “distributes leads to sellers based on their workload, so that all sellers are equally busy.” My opinion: load balancing is the right call when lead quality is uneven, because a seller buried in follow-ups should not get the next hot lead. Round robin is the right call when the fight is about fairness, because everyone can see the turn order.

Ask for “Consider record type created in the last.” It sets a window in hours, and “If no seller is available to take the record within that time, the record is marked overdue.” That turns an unassigned lead into a visible failure instead of a quiet one.

Set expectations on speed. Records “are processed at regular intervals,” and “There might be a delay between when a record meets the conditions of the assignment rule and when it gets assigned to a seller.” Journey-created leads follow the same path: “Dynamics 365 Sales assignment rules take precedence over the owner specified in the journey.” Any wiring that runs on a schedule also fails on a schedule, so require that RevOps monitors automation for failures and alerts on them.

Now the SLA, stated carefully. Leads take enhanced SLAs only: “A standard SLA can be created only for the Case entity” (Enable entities for SLAs). SLAs are documented under Customer Service, and Microsoft says “You can create SLAs only in environments that have customer engagement apps such as Customer Service.” Whether a Sales-only environment can run them is not stated, so check the Dynamics 365 Licensing Guide, which is where Microsoft points for SLA licenses (Configure SLAs). “Only one SLA can be applied to a record,” and you can set one default SLA (Apply SLAs).

Microsoft does publish a lead example, “Sample 1: Contact the customer,” where a Hot lead has a 1 day failure time and a 16 hours warning time (Create enhanced SLAs). It is a sample, on a page where web-client enhanced SLAs “are deprecated.” It is not a recommendation.

A forward-looking note on AI. The Sales Qualification Agent can hand promising leads to sellers, and Microsoft says “The agent doesn’t replace your judgment or decision-making process.” It runs on “the capacity assigned to your tenant,” and it evaluates each lead’s fit with “your target customer profile,” so agree that profile with sales the same way you agreed the lead definition.

Write down your segment-to-rule map and your SLA timings yourselves. None of the Microsoft pages cited here gives a recommended speed-to-lead time; the only lead timings are labeled samples.

First touch lives in the sales accelerator, not in an email alert

Still checkpoint 4: the touch that proves the route worked.

Routing tells you who owns the lead. A sequence tells you whether anyone acted. “When you connect the segment, leads, opportunities, accounts, contacts, and insights automatically start the sequence” (Connect segments to sequences). Steps include email activity, automated email activity, text messages, phone call activity, task activity and set wait time (Add steps).

Capacity is real, and marketing drives it. With the Sales Enterprise license, “you get 1,500 sequence-connected records per month,” and above that “you must upgrade your license” (Sales accelerator). By default, the sales accelerator “is available in the Sales Hub app with limited functionalities” (Configure the sales accelerator). Know your monthly Sales-Ready volume against that number before you launch the next campaign.

Timing matters here. When a seller qualifies a lead in Dynamics 365 Sales, “it becomes a read-only record,” and “it can’t be connected to a segment.” A Marketing Qualified or Sales-Ready lead is still open, so route it and start the sequence before a seller qualifies it.

Make the first touch a sequence step with an owner, so “assigned but untouched” shows up in the work list instead of disappearing.

Feedback: reason codes, not free text

Checkpoint 5: handoff feedback and reporting.

In our experience, the feedback loop only works when every lead a seller disqualifies or returns gets a reason from a fixed list your two teams write together. Free text produces opinions. A pick list produces a report.

Agree on what “qualified” means in the record, not just in status. Microsoft is clear that the flow depends on “how your administrator configured the lead qualification experience,” and “If no opportunity is created when you qualify a lead, the business process flow doesn’t progress to the next stage, although the lead’s status becomes Qualified” (Qualify and convert a lead). This is where the shared lead definition gets tested: a “qualified” lead with no opportunity is a definition both teams quietly disagree on.

Feed the reason codes back into the scoring thresholds on a fixed cadence, quarterly for example. Since changing criteria means stopping the qualification model, a cadence protects the model from live tinkering.

Step back and the pattern is obvious. The handoff is a chain of settings, and each link has a default that quietly loses leads. Marketing owns the first three links, so marketing should be the one asking to audit the whole chain.

If a reason code does not change a threshold within one review cycle, delete it.

Walk one of your own leads with us

You do not need another alignment workshop. You need to see where your own leads stall. Citizen Development Academy runs a 30-minute Lead-to-Revenue Review: we walk one real lead from your form to the first seller touch and check five points: shared lead definition, capture and dedupe, scoring readiness, routing and SLA, handoff feedback and reporting. You leave knowing which defaults are working against sales and marketing alignment in your environment and what to ask RevOps for first. Nonprofits can get this help free.

Request a 30-minute Lead-to-Revenue Review with Citizen Development Academy