Dynamics 365 Marketing: the new name, what the app does, and when it is the right pick

Dynamics 365 Marketing is now published by Microsoft as Dynamics 365 Customer Insights Journeys. It is Microsoft's marketing automation application: it builds segments, runs real time and trigger based customer journeys, sends email and other messages, hosts marketing forms, plans events, personalises content by language and region, and reports on journey performance. It runs on Microsoft Dataverse, which is the same data platform as Dynamics 365 Sales, and that shared platform is the main reason organisations choose it over a standalone marketing tool.

The rename, and what it changes

Microsoft folded the marketing application into the Customer Insights family, which has two apps. Customer Insights Journeys is the orchestration app, the one that was Dynamics 365 Marketing. Customer Insights Data is the customer data platform that unifies records from several systems into one profile. You can licence and use Journeys without Data, and many organisations do.

Practically, the rename matters for three reasons. Search results and older blog posts still use the old name, so you will find documentation under both. The official documentation now lives under the Customer Insights Journeys hub on Microsoft Learn. And the product has been reorganised around real time journeys, so guides written for the older outbound module describe screens that have moved.

What the application does

Capability	What it covers
Real time journeys	Trigger based journeys that react to a customer action, and segment based journeys that run against a list
Segments	Built from Dataverse data, including natural language segment creation
Email and messaging	Email design and sending, with AI assistance for content, plus other channels configured per tenant
Marketing forms	Forms hosted or embedded, writing straight into Dataverse
Event planning	Event records, sessions, registration and attendance
Personalisation	Dynamic content in messages, including multiple languages and regions
Analytics	Journey level reporting and cross journey analytics
Administration	Domain authentication, user roles, environment and organisation settings

Microsoft's own product page for Customer Insights carries the current feature list, and the Learn hub carries the setup documentation.

Why the Dataverse question decides the purchase

Most marketing automation tools keep their own contact database and sync it to your CRM. Customer Insights Journeys keeps contacts in Dataverse, which is where Dynamics 365 Sales and Customer Service already keep theirs. One record, one set of field definitions, one security model.

That produces four practical advantages, and they only apply if you are already a Dynamics organisation.

• No sync to maintain. There is no integration to break, no duplicate contact logic and no field mapping document.
• Sales activity can trigger marketing. A journey can start from a change to an opportunity, because the opportunity is in the same database.
• One security model. Dataverse roles govern who sees which records in both applications.
• Power Platform extends it. Power Automate flows, Power BI reports and Power Apps screens work on the same data without an export.

If your CRM is not Dynamics, most of that advantage disappears and the comparison becomes a straight feature and price comparison against the marketing platforms built around their own database.

Where this is the right pick

• Your sales team already works in Dynamics 365 Sales, and marketing and sales need to see the same contact.
• You are a Microsoft estate: Entra identity, Azure hosting, Power BI reporting, and a procurement process already set up for Microsoft agreements.
• You run considered, multi step buying journeys where a trigger from a service or sales record should change the messaging.
• You hold events as a major channel and want registration tied to the same contact records.
• You market in several languages or regions from one tenant.

Where another tool fits better

• A small team with no Dynamics. A standalone marketing platform will be live in days and needs no Dataverse administration.
• Ecommerce volume sending. Platforms built for high frequency retail messaging with native store integrations are a closer fit.
• A content and inbound led operation. If the main need is a CMS, landing pages and blogging alongside email, an inbound platform covers more of it in one place.

Our page on what a marketing CRM is for and how it differs from a sales CRM covers the choice between these architectures.

What to settle before you buy

• Licensing. Microsoft publishes the pricing and the licensing guide on its own site. Confirm what the app licence covers, how marketing capacity is counted for your contact volume, and whether you already hold entitlements through other Dynamics 365 applications.
• Environments. Which Dataverse environment the app goes into, and whether you need separate development and production environments.
• Domain authentication. Sending domains, DNS records and the deliverability setup, because this is the step that delays the first campaign.
• Consent and data. How consent is recorded against the contact record and how it is honoured across both applications.
• Data quality. Duplicate contacts in Dataverse become duplicate sends. Agree the deduplication rules before migration.
• Who administers it. This is a platform application, so it needs a named Dataverse administrator as well as a marketing owner.

A realistic implementation sequence

• Weeks one and two. Environment provisioned, licences assigned, roles configured, domain authentication completed and verified.
• Weeks three and four. Contact data reviewed and deduplicated, consent fields agreed, the first segment built and checked against a known list.
• Weeks five and six. One email template and one simple journey, live to a small segment, with analytics confirmed end to end.
• Weeks seven to ten. Forms embedded on the website, the first trigger based journey, and the reporting pack built in Power BI if that is where leadership reads numbers.
• After that. Add channels and complexity one journey at a time. Organisations that try to migrate every legacy campaign at once take far longer to get the first useful send out.

This page covers what the application does and how to decide on it. For a comparison of a mid market suite in the same category, see our page on Zoho marketing automation.

What people ask about Dynamics 365 Marketing

Is Dynamics 365 Marketing discontinued?

The product continues under a new name, Dynamics 365 Customer Insights Journeys. Older documentation and third party articles still use the previous name, and Microsoft's documentation redirects cover both.

What is the difference between Customer Insights Journeys and Customer Insights Data?

Journeys orchestrates marketing: segments, journeys, messages, forms, events and analytics. Data is the customer data platform that unifies records from multiple systems into a single profile. Journeys can be licensed and used on its own.

How much does it cost?

Microsoft publishes the per application pricing and the full licensing guide on its own site, and the figure depends on the app licence plus the marketing capacity your contact volume requires. Take the number from Microsoft's pricing page or your Microsoft partner, and ask specifically what happens when contact volume grows.

Do I need Dynamics 365 Sales to use it?

No. It needs a Dataverse environment, not the Sales application. The strongest case for choosing it, though, is that sales and marketing share one contact record, which assumes Sales is there.

Can it replace a standalone email platform?

For a Microsoft estate, yes: it covers design, sending, forms, journeys and reporting in one place. The deciding factor is usually administration capacity rather than features, because it is a platform application and expects a platform administrator.

Where to go from here

• Marketing CRM versus sales CRM
• Zoho marketing automation, priced and compared
• How lead generation actually works in practice
• A marketing budget format finance will approve

Before the first trigger fires

The questions to settle before you buy concern data, licences and the Dataverse model. One more concerns the audience you will never see in it: people who asked an assistant to compare marketing platforms and never visited a vendor site.

Try the question yourself with a Dynamics 365 Customer Insights Journeys angle. Ask two assistants what it is, what it replaced and who it fits. The answers show whether the old name still confuses buyers. If it does, your own pages need to bridge it. AI Knows Us handles that kind of question and lists the sources.