Outbound lead scoring after the removal

What it does

Outbound marketing had its own lead scoring engine — scoring models with conditions, grades and a sales-ready threshold, running off the legacy marketing insights service. Outbound was removed from all Customer Insights - Journeys environments in May 2026, and those models no longer run. The tables and their data are still there; the capability isn't.

Key facts

Outbound marketing was removed from every environment in May 2026. The sitemap entry, the user interface and the underlying outbound services all went with it.
Lead scoring model records were not deleted. The publicly documented tables remain and the data in them is intact, but Microsoft is explicit that these assets can't be used in real-time journeys.
There is no migration tool from outbound scoring models to real-time journeys scoring models. You rebuild the logic by hand in Lead management > Scoring models.
Other outbound assets are in the same position — emails, forms, pages, templates, consent data and subscription lists are retained as data but not usable.
Segment membership was removed outright. Segment queries survive in the msdyncrm_segment table; the actual member lists do not. That matters if outbound scoring conditions depended on segment membership.
Marketing lists remain usable, because they're Sales entities rather than outbound ones.
Outbound analytics and insights reports were removed, so historical score trend reporting from outbound is gone. Custom Power BI reports built against outbound data won't work against the consolidated real-time journeys data.
The outbound documentation is now an archived PDF only, downloadable from the removal notes page with the password Outbound(not-supported). No further updates are planned.
Custom plugins that reacted to retrieve or retrieve-multiple messages against outbound services can fail after removal — worth checking on any environment with bespoke lead automation.

When to use / skip

Nothing to use here — this is a doc about what you'll find in an environment, not a feature to configure. Read it when you inherit a tenant that predates the removal and someone asks why the lead scores in an old view have stopped moving, or why a Power BI dashboard has gone flat.

The practical work it points at is a rebuild. If the client had outbound scoring, the useful salvage is the logic, not the records: the conditions and point weights represent real thinking somebody did, and reconstructing them in the real-time model builder is a day's work rather than a fresh design exercise.

Where you'd skip the salvage entirely: if the outbound models were built years ago, never tuned, and nobody can name the person who set the thresholds. Rebuilding a model nobody trusted is a waste of a workshop. Start from the current data instead.

Configuration decisions

Salvage or start fresh. Read the old conditions out of the retained tables, decide which still reflect the business, and treat the rest as archaeology.
What to do with stale score fields. The old score values sit on lead records looking authoritative. Decide whether to blank them, hide them from forms and views, or leave them and relabel.
Reporting continuity. Outbound analytics are gone. Decide whether historical score reporting is rebuilt from the retained tables, exported and parked, or dropped.
Segment-dependent logic. Any outbound scoring that leant on segment membership needs replacing with attribute or interaction conditions, since the member lists no longer exist.
Custom code review. Audit plugins, flows and integrations that touched outbound tables or services before you promise the client a clean environment.

Gotchas

The retained tables are the trap. Records exist, views can be built over them, and everything looks live — but nothing recalculates. Clients report this as a bug.
Real-time journeys scoring is not a like-for-like replacement. There's no contact scoring, only standard Dynamics 365 interactions are available as conditions, and scores refresh on a roughly two-hourly cycle. Set that expectation before promising parity.
The archived PDF is the only remaining reference for how the outbound models behaved. Download a copy now rather than assuming the link will still be there when you need it.
Interaction history from the outbound era does not feed the new models in the way clients assume. Expect a cold-start period where the new model scores everyone low.
Anything built on outbound analytics data — Power BI, exports, integrations — needs rework, not remapping.
Environments restored from old backups can reappear with outbound artefacts in place. Treat any pre-removal restore as a migration exercise, not a restore.

Consultant notes

On any inherited tenant, check for populated legacy score fields early and agree what happens to them before sales users start quoting the numbers back at you.
Tell the client plainly that scoring was rebuilt, not migrated, and that the numbers will differ. It's a much easier conversation up front than after the first sales team complaint.
Demo the new model's Insights tab against the old scoring view side by side if the old data is still visible. It makes the "this is a new thing" point better than any slide.
Budget a proper workshop for the rebuild rather than a config task. The conditions are the easy part; agreeing the thresholds again is where the time goes.
Before go-live, confirm no flow, plugin or report still reads the old outbound scoring tables expecting fresh values.

Worth another look if a client turns up on a very old environment or restores a pre-May-2026 backup.