Sequences or marketing journeys for outreach

What it does

Two products in the same Dataverse tenant both send email to prospects: sequences in Dynamics 365 Sales, and journeys in Customer Insights - Journeys. Sequences are a seller's to-do list with some automation bolted on. Journeys are a marketing automation engine with consent, segmentation and volume behind it. Picking the wrong one gives you either a marketing tool nobody in sales will open, or a sales tool quietly doing unconsented bulk email.

Key facts

A sequence supports eight step types: A/B test, email activity, automated email activity, send a text message, send an automated text message, phone call activity, task activity, and set wait time.
Manual steps (email, text, phone call, task) put an item in front of the seller. Automated email, automated text, wait and A/B test run without seller involvement.
Maximum wait time on a Set wait time step is 90 days. A sequence cannot end on a wait step.
A/B test audience split is between 10% and 90% per version, and an A/B test step cannot be renamed once the sequence is active and assigned.
Automated email requires email engagement to be configured first, and Send Email as Another User enabled in the Power Platform admin centre. For accounts, the account needs a primary contact with a valid email address.
Sequences connect to leads and opportunities. Permissions run through the Sequence, Sequence Target and Sequence Target Step tables; Sequence Manager, Sales Manager and Salesperson roles carry them by default.
On Sales Enterprise, sales accelerator is capped at 1,500 sequence-connected records per month. Premium removes the cap.
Journeys come in two shapes: trigger-based, reacting to a customer action, and segment-based, targeting a set of people sharing attributes.
A journey can be edited while live — that creates a new version while the current one finishes — and can be paused and resumed without ejecting customers already in it.
Stopping a high-volume journey can delete messages that were queued but not yet sent.
Customer Insights - Journeys is a separate licence and a separate app. Nothing about Sales Enterprise or Premium entitles you to it.

When to use / skip

The line is one-to-one versus one-to-many, and it holds up better than any feature comparison. If a named seller owns the relationship and the email is meant to look like it came from a person, that is a sequence. If the send is to a list, the content is templated marketing content, and nobody would be embarrassed if the recipient saw it went to five thousand people, that is a journey.

The second test is consent. Journeys carry marketing consent and preference handling as a first-class concern. Sequences do not — an automated email step in a sequence sends because a seller connected a record, and the compliance position rests entirely on your process discipline. For UK and EU clients doing genuine cold outreach at volume, that difference is the decision. I would not build a bulk prospecting programme on sequences for a client with a serious data protection function, and I have talked two clients out of exactly that.

The third test is who maintains it. Sequences are edited by a sales ops person or a sequence manager. Journeys live in a marketing app with its own security, content model and usually its own team. With no marketing function to own them, buying Customer Insights so sales can send nurture email is an expensive way to get a worse experience for the seller.

Most mid-market Sales implementations do not need journeys at all in phase one. Sequences plus a handful of email templates cover follow-up discipline, which is the actual problem. Where both exist, keep the boundary explicit: marketing hands over a qualified lead, sales picks it up in a sequence. Running both against the same contact at the same time is how clients end up apologising to prospects.

Configuration decisions

Where the handover point sits — which lead status or qualification event ends journey participation and starts sequence enrolment.
Whether automated email steps are allowed at all, or whether sequences stay manual-only so a human sees every send.
Which mailbox automated email sends from, and whether Send Email as Another User is acceptable to the client's security team.
How sequence connection is triggered — manual seller action, segment-based assignment rules, or a Power Automate flow — because this drives the 1,500-a-month consumption on Enterprise.
Who owns sequence content and who approves changes, given that an active sequence is edited in place and affects records already running through it.

Gotchas

Automated email steps fail quietly for accounts with no primary contact or no valid email. The step does not error loudly; the record just stalls.
The 90-day wait cap bites on long-cycle nurture. A twelve-month re-engagement pattern cannot be one sequence, and chaining sequences to fake it produces reporting nobody can read.
A/B test steps cannot be renamed once the sequence is active and assigned, so the name you type in a hurry is the name in reporting forever.
Editing a live sequence changes behaviour for records already connected. It is not versioned the way a live journey is.
Stopping a journey mid-flight can drop pending messages. Pause, do not stop, unless you actually want the sends abandoned.
Nobody counts the 1,500 Enterprise cap until a bulk connect blows it. Automation that connects sequences on lead creation is the usual culprit.

Consultant notes

Draw the handover on one slide in discovery — journey ends here, sequence starts there — and get both the sales and marketing sponsor to agree to it in the room. Almost every problem in this area is an ownership problem wearing a technical costume.
Demo a sequence as a seller's daily work queue, not as an email tool. Demo it as email and the client compares it to their marketing platform, where it loses.
Push back on "we'll just use sequences for the newsletter". Say the consent problem plainly and put it in writing.
Before go-live, check email engagement is configured and send a real automated step to a real mailbox. Automated email is the single most common thing that is switched on but never actually tested.
If the client has no Customer Insights licence, say so early. Do not let a journeys-shaped requirement sit in the backlog implying it is buildable in Sales.

Worth another look after the next release wave, or if the Enterprise sequence capacity or journeys licensing changes.