Outbound marketing removal and what's left behind

What it does

Outbound marketing — the original Dynamics 365 Marketing module with customer journeys, marketing pages, subscription lists and segment members — was removed from all environments in May 2026. The user interface, sitemap entry and backing services are gone. Most of the Dataverse tables and rows are still sitting there, which is the part administrators now have to deal with.

Key facts

Removal completed in May 2026, after a phased wind-down: creation of new outbound journeys, segments and forms was restricted from around June 2025, admins were notified during the phased removal from around November 2025, and live outbound journeys, forms and events were stopped in January 2026.
Removed: the outbound sitemap area and UI, the outbound services, and the Insights reports that were part of that UI. Retained in the database but not usable: outbound emails, content blocks, forms, marketing pages, templates, social posts, subscription lists, lead scoring models and consent data.
Segment member data is gone. The internal tables holding computed membership were removed. Segment definitions survive in msdyncrm_segment but are not maintained and should not be pointed at real-time journeys.
Event tables are shared with real-time journeys, so the data survives, but outbound-era event records don't fit the real-time event structure. Events have to be recreated through the real-time UI or the event API.
Marketing lists are a Sales entity and were never part of outbound marketing, so they are unaffected.
Outbound analytics data was merged with real-time journeys data, but the old outbound Power BI reports won't read it — the format, location and access method all changed. Use the SourceSystem attribute to tell outbound-origin rows from real-time ones.
Surviving outbound records are reachable only through the Power Apps maker portal or advanced find. Contact timelines still show links to outbound messages that were sent historically.
Custom UI, plugins or integrations that called outbound marketing services may fail outright. Nothing about them is supported.
The outbound documentation set is archived as a password-protected PDF (password Outbound(not-supported)), receives no updates, and Microsoft reserves the right to withdraw it without notice.
There is no extension, no opt-out and no per-tenant reprieve.

When to use / skip

Nobody chooses this topic — you inherit it. The question on a live project is how much archaeology is worth doing.

If the client migrated properly before removal, the job now is tidy-up: confirm nothing in a Power Automate flow, integration or report still references outbound tables, and decide whether to keep the residual rows for audit or delete them. That's a couple of days.

If the client did not migrate — and there are plenty who assumed the deadline would slip again — you're doing a rebuild, not a migration. Emails, forms, pages and journeys have to be recreated in real-time journeys. Do not budget it as a data migration exercise. The only things that carry across cleanly are contacts, leads and consent data, and consent needs its own migration path into contact point consent records.

Configuration decisions

Whether residual outbound rows are archived and deleted, or retained in place for audit and record-keeping. Retention policy is the client's call, not yours.
What replaces the outbound Power BI reports: rebuild against the Fabric integration, or accept a break in the reporting history at the cut-over date.
Which historical outbound content is genuinely worth recreating in real-time journeys versus quietly retired. Most clients rebuild far more than they need to.
How subscription lists map onto the real-time consent model — purposes and topics rather than lists — before any preference centre wording is signed off.
Whether legacy DoNotEmail and DoNotBulkEmail values from the outbound era should be honoured, which means turning on the contact-consent feature switch in real-time journeys.
What to do with custom code, flows and integrations that touched outbound tables: repoint, retire, or leave dormant.

Gotchas

Segment definitions still exist and look usable in advanced find. They aren't — the membership is gone and nothing recalculates them. Someone will try to reuse one.
Consent did not migrate itself. Outbound consent lived on the contact record and in subscription lists; real-time journeys works from contact point consent records. Skipping this step means either emailing people who opted out, or a database that appears to have no consent at all.
Reporting is the surprise. Clients discover in the first month after cut-over that their marketing dashboards are empty, because the Power BI reports pointed at outbound structures that no longer exist.
Integrations fail quietly. A nightly flow that wrote to an outbound entity may still succeed against a table that nothing reads, and nobody notices for months.
The archived documentation is on borrowed time. If you need it for a migration or an audit trail, download it now rather than assuming it will be there next year.
Contact timelines still show outbound message links, which makes it look to end users as though outbound is partly working. It isn't.

Consultant notes

Run a dependency sweep early: search flows, plugins, custom reports and integrations for outbound table names. That list is the real scope of the clean-up, and it's usually longer than the client expects.
Be direct with clients still hoping for a migration tool. There isn't one for content. Framing it as a rebuild up front avoids a much worse conversation at the halfway point.
Treat consent migration as a separate, tracked workstream with the client's privacy owner signing it off. It is the one piece with legal exposure.
Take an export of anything the client might want for audit — consent history, sent-message records, outbound email content — before you start deleting residual rows.
Check the contact timeline behaviour with the client before go-live so the service desk isn't fielding "why can't I open this email" tickets.

Worth another look if Microsoft withdraws the archived outbound documentation or changes how the retained tables are treated.