Marketing automation in Dynamics 365: how the journeys engine works and how to set one up

Marketing automation in Dynamics 365 is delivered by Dynamics 365 Customer Insights - Journeys, the app Microsoft previously called Dynamics 365 Marketing. Its documentation describes every piece of automated communication as three decisions: who, defined by a segment, what, which is an email, a text message or a push notification, and when, which is either a scheduled time or a trigger raised by something the customer did. Build in that order. Get the data and the consent right first, authenticate your sending domain, create one audience and one message, then wire the journey and go live on a small group before you widen it.

Last verified: 09 October 2026, against Microsoft's Customer Insights - Journeys documentation at learn.microsoft.com/dynamics365/marketing

What the app is called now

The naming has moved twice, which is why search results disagree. Microsoft's current documentation set is published as Dynamics 365 Customer Insights, split into two apps that are licensed and used together: Customer Insights - Journeys, which is the marketing automation app formerly named Dynamics 365 Marketing, and Customer Insights - Data, which unifies customer records into profiles and segments that Journeys can use.

Microsoft also publishes a transition page covering the move from the older outbound marketing module to real time journeys. It states that outbound marketing is being removed from the app and points new work at real time journeys, with functional guides for journeys, segments, consent and personalisation. If you are inheriting an older implementation, read that page first, at learn.microsoft.com/en-us/dynamics365/marketing/real-time-marketing-transition-resources, because it tells you which features to stop building on.

Who, what, when

The documentation frames the whole product around three questions, and it is a genuinely useful way to plan.

• Who. A segment: a subset of your contacts that meets some criteria. Segments can be built inside Journeys or brought in from Customer Insights - Data.
• What. The content and the channel. Email, text message and push notification, used on their own or together in one journey.
• When. A planned time, or an event that triggers the communication. That single choice splits the two journey types below.

Segment based or trigger based

Question	Segment based journey	Trigger based journey
Who enters	Everybody in a segment	One person, at the moment they do something
Starts on	A schedule you set	A trigger you define
Natural fit	Newsletters, announcements, event invitations, re engagement campaigns	Welcome series, abandoned forms, booking confirmations, renewal reminders, post purchase follow up
Design effort	Mostly in the segment query	Mostly in the trigger definition and the exit rules
Build it when	The message is about your calendar	The message is about the customer's action

Most teams need both, and the common mistake is building everything as a scheduled send because that is the habit carried over from an email tool. Anything that follows a customer action belongs in a trigger based journey, where the timing is right by construction rather than by luck.

The build order that avoids rework

• One. Settle the data model. Decide whether journeys run on contacts, on leads, or on Customer Insights - Data profiles, and write down which system owns each field. Automation built on a field two teams edit differently becomes unpickable later.
• Two. Set up consent before the first send. Purposes, topics and the preference centre go in at the start. Retrofitting consent across live journeys is the most expensive piece of remedial work in this product.
• Three. Authenticate the sending domain. Add the DNS records Microsoft asks for and verify the domain inside the app. Send from a real subdomain you control, not a shared one.
• Four. Build one segment and one email. Prove the audience count is what you expected and that personalisation resolves correctly on a test send.
• Five. Wire the journey. Entry, branches, waits, exit conditions and a goal. Write the exit conditions before the branches; a journey that cannot release somebody keeps messaging them.
• Six. Go live on a small audience. A few hundred contacts, one week, then read the results before widening.
• Seven. Decide reporting on day one. Agree which numbers go to the business, where they come from, and who publishes them.

When Dynamics 365 is the right choice for automation

It is strongest when your customer records already live in Dataverse and your sales team works in Dynamics 365 Sales. Then automation sits on the same data as the pipeline, journeys can react to changes a salesperson makes, and there is no sync to maintain between two systems that each think they own the contact.

It is a heavier choice when your records live somewhere else and the only requirement is campaign email. The implementation cost of this product is mostly data and consent work, and that cost is worth paying when the payoff is one customer record across marketing, sales and service.

Licences and cost

Microsoft publishes the plans and what each one includes on the Customer Insights product page at microsoft.com/en-us/dynamics-365/products/customer-insights. Read the figures there rather than from a blog, because the packaging has changed more than once and the allowances attached to each plan are the part that decides your real cost. Two things to check before you sign: how the plan counts the people you interact with, and which licences the rest of your team need to view or edit the records a journey touches.

What to automate first

• A welcome sequence triggered by the form submission that created the record. Three messages, each with one job.
• An enquiry acknowledgement that confirms what happens next and when. It reduces chasing calls more than any campaign.
• A dormant customer journey built on a segment, with an exit as soon as the person engages.
• A renewal or reorder reminder triggered off a date field the business already maintains.
• An internal alert to the owner when a high value record reaches a stage, so the automation prompts a human rather than replacing one.

This page covers the automation mechanics. For what the app is, the naming history and when it is the right pick, see Dynamics 365 Marketing, the new name and what the app does, and for the wider question of how a marketing database differs from a sales one, see marketing CRM.

marketing automation in Dynamics 365: the questions that keep coming up

Is Dynamics 365 Marketing discontinued?

The capability continues under a new name. Microsoft's documentation now presents it as Dynamics 365 Customer Insights - Journeys, and the older outbound marketing module is being removed in favour of real time journeys. Build new work in journeys.

Do I need Customer Insights - Data as well as Journeys?

Journeys runs on its own with contacts and segments held in Dataverse. Customer Insights - Data earns its place when customer records are spread across several systems and you want one unified profile and one segment definition feeding every journey.

Can it send text messages and push notifications, or only email?

The documentation lists email, text message and push notification as channels, usable separately or together inside one journey. Text and push need their own configuration and a provider connection, so plan those as separate pieces of setup rather than a tick box.

How many journeys should we start with?

Two live journeys, running well and reported on, beat ten half built ones. Pick the welcome sequence and one trigger that follows a real customer action, run both for a month, then add the next.

What breaks most often in these implementations?

Three things, in order: a domain that was never properly authenticated, so delivery suffers from the first campaign; consent handled after launch rather than before it; and exit conditions nobody wrote, so people stay in a journey after they have already bought. All three are an hour of work at the start and a month of work later.

The journey before the first trigger

Your journey begins at a trigger: a form fill, an email click, a page visit. A buyer's real journey started earlier, with a question typed into an assistant that produced a short list of vendors.

That earlier step never fires a trigger, so it cannot be segmented. What you can do is learn what the assistant says about your offer and write the first journey email to match it. Ask for a recommendation in your category and see whether it describes your product accurately. With AI Knows Us you can run those questions across assistants and keep the answers.