Real-time vs outbound journeys

Customer Insights – Journeys (the successor to Dynamics 365 Marketing) ships two distinct journey models — real-time journeys and outbound journeys. They look similar in the designer but operate on very different mechanisms. Microsoft is moving customers toward real-time as the default; understanding why matters for both new builds and existing-tenant migrations.

Outbound journeys. The original model, inherited from the older Dynamics 365 Marketing product. Built around:

• Segments — saved queries that produce static lists of contacts at journey-start time.
• Static membership — once the journey starts, the contact list is largely fixed; mid-journey additions are limited.
• Scheduled execution — the journey runs on a calendar, sending email at planned times.
• Email-centric — historically email-heavy with limited support for other channels.
• Less personalisation — limited mid-flight branching on real-time signals.

Outbound is the right pattern for traditional campaigns: "send this email to everyone in segment X tomorrow at 9am, follow up with a second email three days later if they didn't open the first".

Real-time journeys. The modern model, built natively for the new Customer Insights – Journeys product. Built around:

• Triggers — events that fire the journey for one specific person at the exact moment the event happens. Triggers come from Dataverse changes, web form submissions, API calls, page visits, custom events.
• Dynamic membership — every event evaluates eligibility; the journey activates per individual the moment their data matches.
• Real-time execution — milliseconds-to-seconds between trigger and action.
• Multi-channel — email, SMS, push notifications, in-product messages, Teams cards, custom channels.
• Richer branching — wait for behaviour signals (opened the email? clicked? visited the page?) and adapt the next step.

Real-time is the right pattern for behaviour-driven engagement: "when a customer downloads a whitepaper, wait 24 hours, send a follow-up email, wait for their click, if they clicked the demo link, send a sales-handoff email; if they didn't, send a different nurture email".

The differences in practice.

| Aspect | Outbound | Real-time | |---|---|---| | Trigger | Segment + schedule | Event | | Membership | Mostly static | Fully dynamic | | Latency | Seconds-to-hours | Near-instant | | Channels | Email-led | Multi-channel native | | Mid-journey branching | Limited | Rich | | Volume | Large batches | Distributed bursts | | Compliance | Legacy | Modern (consent-by-design) |

Microsoft direction. Microsoft is investing in real-time as the strategic platform. Outbound is in maintenance mode — supported, but not the focus of new feature work. Microsoft has announced timelines for outbound deprecation; new customers should build real-time-first.

Migration. For existing customers with outbound journeys, Microsoft provides tools to migrate journeys to the real-time model. Many require rebuilding (the underlying mechanics differ enough that automatic conversion has limits). Plan migration as a small project, not a flip-switch.

When outbound is still right. Some scenarios remain outbound-friendly: bulk monthly newsletters with no behaviour-driven follow-up, simple announcement campaigns, lift-and-shift legacy campaigns awaiting migration. But for any new behaviour-driven engagement, build real-time.

The hybrid period. Mature tenants run both side-by-side during the migration window — real-time for new builds, outbound for legacy campaigns yet to migrate. Document which lives where and migrate the highest-value journeys first.

Operational reality. Real-time journeys demand cleaner data and better event design. The reward is dramatically more relevant customer experiences; the investment is real but bounded.