Almanac
Microsoft/d365salesDynamics 365

Consultant-focused KB for Microsoft Dynamics 365 Sales: implementation notes, gotchas, and configuration decisions beyond the official docs — across pipeline management, opportunities, forecasting, sequences, sales accelerator, Copilot, integrations, administration, and licensing.

d365sales/03-leads-and-activities/feature-lead-qualification.md
feature-lead-qualification.mdv1 · history
CurrentApplies to AllUpdated 6 days agoSource Microsoft Learn ↗

What it does

Qualifying a lead closes it as Qualified and spins up some combination of account, contact and opportunity from the lead's data. The admin decides, per record type, whether the system creates the record silently or whether the seller chooses in a side pane at the moment of qualification.

Key facts

  • Configured at App Settings > General Settings > Lead + Opportunity management > Lead Qualification in the Sales Hub app.
  • Try the new lead qualification experience is on by default, including in orgs that had configured the older behaviour. Your previous auto-create setting is retained underneath, so switching back is not destructive.
  • For each of account, contact and opportunity you pick Seller (the seller creates new, picks an existing, or creates nothing) or Automatic (the system creates it and the seller reviews afterwards).
  • With Seller selected for opportunity, you can let one lead produce up to five opportunities. Only one of them — the default — carries the business process flow.
  • The opportunity quick create form shown in the side pane is editable from the settings page, which opens the standard form designer in Power Apps.
  • Custom apps need the Opportunity qualify lead Form component added, otherwise sellers get a side pane where they cannot create or edit the opportunity at all.
  • Field mapping on qualify is the standard Dataverse entity map: lead Topic to opportunity Topic, Company to account name, first/last name, job title, phones, email and address 1 fields to contact. Custom fields are not mapped unless you add them to the entity mappings.
  • The optional Copilot lead summary writes a summary card — name, company, email, phone, address, links to the created records — to the timeline of both the primary opportunity and the lead. It needs Copilot enabled for the org.
  • Qualified leads move out of My Open Leads into Closed Leads. The lead record survives, and notes and attachments taken during the lead's life surface on the resulting opportunity.
  • You can only disqualify a lead that has no opportunity attached. Both qualified and disqualified leads can be reactivated without re-keying anything.
  • The legacy equivalent still exists in Advanced Settings > System Settings > Sales, as "Create Account, Contact, and Opportunity records by default upon qualifying a lead".

When to use / skip

There is no skipping this one — qualification is the hinge of the whole lead process, and if you get it wrong the client notices in week one of UAT. The real decision is how much of it is automatic. B2B clients with clean marketing data are usually happy with Automatic for account and contact, because the duplicate check catches the obvious collisions and sellers stop complaining about clicks. B2C-shaped businesses, or anyone whose leads arrive as a name and a Gmail address, should put account on Seller or turn it off entirely — otherwise you will build a database of one-person accounts named after individuals, and nobody will thank you for it eighteen months later.

Turn on multiple opportunities only where a single enquiry genuinely splits into separate deals with separate close dates. Most clients ask for it because it sounds useful, then never use it, and it complicates the BPF story.

Configuration decisions

  • Seller versus Automatic, decided separately for account, contact and opportunity — this is the setting that shapes the seller's daily experience.
  • Whether account creation happens at all, which is really a data model decision about whether you keep orphan contacts.
  • Which fields appear on the opportunity quick create in the side pane, and which of them are mandatory at that moment rather than later in the BPF.
  • Whether custom lead fields need to survive qualification, and therefore which entity mappings you extend (lead to account, lead to contact, lead to opportunity are three separate maps).
  • Whether Copilot lead summarisation goes on, and whether the client is comfortable with a generated summary landing in the timeline as a permanent record.
  • Whether a single lead can produce multiple opportunities, and which one you nominate as primary.

Gotchas

  • Custom fields do not carry across on their own. Every project hits this, usually the day after go-live, and the fix is entity mappings in the solution — not anything on the settings page.
  • If no opportunity is created, the lead's status still goes to Qualified but the business process flow does not advance to the opportunity stage. Sellers read that as "it didn't work".
  • Disqualify is blocked once an opportunity exists, which sounds sensible until a seller qualifies by accident and then cannot tidy up. Agree the correction path — close the opportunity as lost, reactivate the lead — before go-live.
  • Automatic account creation and duplicate detection interact: the seller sees a duplicate prompt mid-qualification and can pick an existing account, so "automatic" is not always silent.
  • Plugins and flows written against the qualification path should be registered on the QualifyLead message rather than on create of the opportunity, or they will miss the records the side pane creates and fire in the wrong order.
  • Bulk qualification from a grid applies the same rules, which means an automatic configuration can generate a few hundred accounts from one careless multi-select.

Consultant notes

  • Demo the side pane early, with the client's own dirty data. Their reaction to what gets created tells you more about the right configuration than any workshop.
  • Push back on "just make it all automatic" unless the lead source is genuinely trustworthy. The cleanup cost lands on the same client six months later.
  • Check the entity mappings as part of your go-live checklist, with a test lead carrying every custom field the client cares about, and check them again after any solution import that touches the lead form.
  • If they run a custom app rather than Sales Hub, verify the qualify side pane properly before you promise the new experience — the missing form component failure is silent and looks like a bug.

Worth revisiting when the qualification agent work in the current release waves lands properly, since it changes who presses Qualify.

Was this accurate?
Related
Predictive lead scoring03-leads-and-activitiesCopilot record summaries07-copilot-in-salesOpportunity records and the deal shell02-opportunitiesSales Qualification Agent07-copilot-in-salesSequence design and activation05-sequences-and-cadencesSetting up the sales accelerator06-sales-accelerator