Dynamics 365 Customer Insights - Journeys: Features, SME Fit & Alternatives

What is Dynamics 365 Marketing today?

Dynamics 365 Marketing — the application Microsoft now sells as Dynamics 365 Customer Insights - Journeys — is Microsoft’s real-time marketing and customer engagement application built on the Power Platform and Dataverse. It orchestrates personalized journeys, segmentation, event management, lead scoring, and multi-channel engagement across email, SMS, push, and custom channels.

The rebrand is not cosmetic. In September 2023 Microsoft merged the former Dynamics 365 Marketing product with the Customer Insights CDP into a single Customer Insights family: Customer Insights - Journeys (engagement) and Customer Insights - Data (unified profiles). One Customer Insights base license unlocks both apps for unlimited users and, under current purchase guidance, rights to install both apps across production and sandbox Dataverse environments (Microsoft documents four installations of each app with the base offer, with unlimited production/sandbox installs called out for paid Customer Insights SKUs after June 2024).

The older product also carried a module called Outbound Marketing that ran scheduled, batch-style campaigns. Microsoft announced in August 2024 that outbound would be removed after June 30, 2025, then ran a multi-phase shutdown (notifications, freezes of new outbound assets, then live-asset stop) through late 2025 and early 2026. Microsoft Learn confirms the outbound module was removed from all environments in May 2026. Historical outbound tables and many assets may still be readable in Dataverse, but outbound UI, services, and execution are gone. Every live customer now runs Real-Time Marketing (RTM) journeys — trigger-based paths that respond to form submissions, abandoned carts, website events, CRM stage changes, and custom triggers rather than a calendar blast.

Search confusion is still common in 2026: people look up “Dynamics 365 Marketing” and land on a product page labeled Customer Insights. Treat those as the same commercial offer. For SMEs evaluating the platform, any guide still describing Outbound Marketing as a live capability is out of date. The product you buy and implement is Customer Insights - Journeys, centered on real-time, behavior-driven engagement.

Journeys vs Data: two apps, one license

Buyers often confuse the two Customer Insights applications. Customer Insights - Journeys is the marketing automation and journey engine — emails, SMS, push, segments, events, lead scoring, and the visual journey canvas. Customer Insights - Data is the customer data platform (CDP) — it unifies, deduplicates, and enriches profiles from CRM, ecommerce, support, and other sources into Unified People.

A single Dynamics 365 Customer Insights base (or attach) license includes rights to both applications, with base entitlements of 10,000 Interacted People for Journeys and 100,000 Unified People for Data. You can buy Interacted People and Unified People add-on packs independently when one meter grows faster than the other.

SMEs that only need email journeys and live entirely in Dynamics 365 Sales contacts may lean on Journeys first. SMEs whose marketing data is split across ecommerce, support, and a non-Dynamics CRM get more value when Data unifies those sources and Journeys targets the resulting profiles. Plan capacity for both meters early — they are independent, and sandbox plus production usage both count against the same tenant quota.

Real-time marketing journeys: triggers and segments

Real-Time Marketing journeys come in two shapes, and SMEs typically use both. Trigger-based journeys fire when something happens — a contact submits a form, abandons a cart, registers for an event, reaches a CRM stage, or hits a custom trigger — and then route that person down a multi-channel path of email, SMS, push, or custom-channel steps.

Segment-based journeys target a defined audience at planned times or on a recurring condition rather than on a single event. Both types share the same building blocks: conditions and branches, waits, goals, exits, and multi-channel steps. That visual canvas is what lets a marketing team compose a welcome series, re-engagement flow, or event-registration nurture without writing code.

The shift from outbound to real-time changes ownership and skill mix. Outbound campaigns were planned and dispatched; real-time journeys are assembled and then react to customers. Marketing operations owns the canvas, not an email batch schedule. Teams that still think in “blast lists” need redesign time for triggers, consent, and goal definitions before go-live. Outbound-era segments, emails, and events are not drop-in reusable: Microsoft Learn is explicit that outbound-created events must be recreated for real-time, and outbound segments should not be relied on even when they still appear in the UI.

Microsoft’s 2026 release wave 1 for Customer Insights - Journeys emphasizes three investment areas: agents and Copilot (Journey Creation Agent, Outreach Optimization Agent, conversational SMS, Dynamics 365 AI Hub governance), elevated experiences (message expiration so delayed or stuck messages stay relevant, branded content links, emails that can refresh to latest content), and pipeline acceleration (create leads and other Dataverse records from journeys, connect behavioral signals from Data into Journeys). Implementation plans should leave room for these building blocks — and for AI-assisted authoring — rather than treating the canvas as a pure manual designer.

Segmentation: dynamic and static

Segmentation in Customer Insights - Journeys supports two complementary approaches. Dynamic segments are built from attribute and interaction queries against contacts, leads, or unified profiles — for example, “contacts in Canada who opened an email in the last 30 days but did not register for the webinar.” Membership updates automatically as the underlying data changes.

Static segments are populated manually or via CSV import, typically for one-time inclusions or exclusions — a trade-show list or a suppression list. Both types give a member preview before activation so you can sanity-check size and composition before a journey depends on them.

When Customer Insights - Data is in play, segmentation gets stronger: the journey builder can target unified profiles — a deduplicated, cross-source view of a customer — rather than only native contact or lead records. That matters when marketing data is spread across CRM, ecommerce, and support. Partner and community guidance in 2025–2026 still treats static-vs-dynamic design as a common implementation decision, not a set-and-forget default. Wave 1 also continues work on marketing-website interaction segments (page visits and clicks as audience criteria) and live segment updates that do not interrupt running journeys — useful when membership rules change mid-campaign.

Event management: the full lifecycle

Event management inside Customer Insights - Journeys covers the full event lifecycle, not just registration: planning and budgeting, sessions and speakers, venues, passes, sponsors, registration forms, Microsoft Teams webinars and live events, check-ins, attendance history, analytics, and lead generation with ROI tracking.

Events belong in a marketing application because of the loop back into journeys and lead scoring. A contact registers, attends, and that attendance becomes both a trigger for a follow-up journey and an interaction that feeds a lead-score model. For an SME running a handful of webinars or a quarterly user event, that closed loop beats stitching a separate webinar tool, registration form, and CRM update step.

Important post-outbound note: events created under the old outbound module are not usable in real-time journeys and must be recreated. Shared event tables may still hold historical data, but live orchestration runs only on real-time event assets.

Lead scoring and the handoff to sales

Lead scoring uses a visual builder to compose models that combine demographic attributes (and related tables) with interactions — email opens, form submissions, event attendance, and similar signals. A model defines scoring conditions, assigns grades (for example Hot or Cold), sets publishing behavior, and specifies qualification criteria for the handoff to sales.

Done well, lead scoring is what makes a marketing platform earn its keep for an SME sales team: it stops reps from treating every form-fill equally and routes warmed leads forward. The discipline is model design — choosing attributes and interactions that correlate with deals, and revisiting the model as the business learns what converts.

Because Journeys sits on Dataverse next to Dynamics 365 Sales, qualification can surface on the same contact or lead record the rep already works. Record-creation steps in journeys (2026 wave) further tighten that loop: a journey can write a lead, opportunity, or activity without a separate integration job. That native handoff is a practical reason Microsoft-centric SMEs choose Journeys over a bolted-on email tool that only syncs scores overnight.

Copilot, Journey Creation Agent, and AI Hub

Microsoft positions Copilot and AI agents as first-class authoring surfaces inside Customer Insights - Journeys. Marketers can describe goals in natural language to draft real-time journeys, define audience criteria for segments, generate email copy from key points or tone and topic, rewrite content for impact, and get image recommendations that fit the message.

Journey Creation Agent (preview) is the 2026 step beyond earlier journey Copilot: you describe a campaign goal, audience, and timeline in plain language; the agent proposes a multi-channel structure with waits, branches, and content assignments from assets you already have. You review a visual preview, refine via follow-up prompts, then open the standard journey canvas before anything goes live. Microsoft documents availability with the 1.1.65002.153 update (NAM and Oceania called out with the June 2026 update wave), English-only preview, enablement through Dynamics 365 AI Hub, and use of Microsoft Copilot Studio / Copilot credits. It replaces the previously released Journey Copilot for journey creation and works best when segments and draft content already exist — it scaffolds structure; it does not invent your segments or brand voice for you.

The broader 2026 wave 1 plan also lists Outreach Optimization Agent (send-time and variant testing), Copilot-powered conversational text messaging, and central governance of agents and Copilot features through Dynamics 365 AI Hub so tenant Copilot policies stay coherent across Sales, Service, and Journeys. Practitioner coverage in mid-2026 also highlights adjacent automation such as Create Record (preview) from journeys and ongoing education on static vs dynamic segments — signals that the product conversation has moved from “does it send email?” to “how do we govern agents and quota while journeys write CRM records.”

For SMEs, agents compress first-draft time; they do not replace a clean data model, consent design, or brand review. Budget implementation for data quality, segment logic, AI Hub opt-in, and capacity for Copilot credits rather than assuming AI removes configuration work.

Pricing overview (details live on the pricing guide)

Customer Insights - Journeys is licensed at the tenant level, not per marketer seat. Unlimited users can access the apps once the tenant license is in place. You size cost by marketing reach (Interacted People and Unified People), not by headcount of marketers.

Microsoft’s published Customer Insights list pricing (USD, paid yearly) has two base SKUs with the same included capacity: $1,700 per tenant per month for organizations without a qualifying Dynamics 365 attach path, and $1,000 per tenant per month attach for organizations with at least 10 users of a qualifying Dynamics 365 app (Sales Professional, Enterprise, or Premium; Customer Service Professional or Enterprise; Field Service; Supply Chain Management; Finance; or Commerce). Both include 10,000 Interacted People and 100,000 Unified People. SMS delivery is not bundled — you pay a supported provider such as Azure Communication Services separately.

This page is the product and SME-fit guide. Full add-on pack tiers, the 10× monthly interaction safe-use rule, sandbox quota traps, worked total-cost scenarios, and attach eligibility edge cases live on our dedicated Dynamics 365 Customer Insights pricing guide — that is the pricing owner for “Customer Insights Journeys pricing” queries. Use the summary table below only to shortlist attach eligibility before you open the pricing deep-dive.

Interacted People, Unified People, and what to size first

Two independent meters drive ongoing cost. An Interacted Person is any Dataverse entity (contact, lead, account, or Customer Insights profile) Microsoft counts as engaged through Journeys — via outbound channel touches or inbound marketing interactions such as filling a form on a marketing website. Each person counts once regardless of how many times you touch them; after 12 months without a counting interaction they drop out of the meter.

Monthly interactions are the outbound sends orchestrated by Journeys. Microsoft’s safe-use ceiling is about 10× Interacted People per month at tenant level (for example, 10,000 Interacted People → about 100,000 interactions per month). Interactions reset monthly and do not roll over. System events that burn interaction quota include EmailSent, EmailCcSent, SmsSent, PushNotificationSent, VoiceChannelSent, and CustomChannelSent. Usage is summed across production, sandbox, and trial environments — sandbox test blasts count.

Unified People are unique profiles produced by Customer Insights - Data when source records are merged (base entitlement 100,000). For SME scoping, estimate three inputs before procurement: attach eligibility, unique people you will engage in a rolling 12 months, and peak monthly outbound volume. Microsoft’s purchase guidance for high-volume engagement is roughly “divide monthly interactions by 10” for Interacted People needed. Pack-level dollar tiers and worked monthly software math belong in the Dynamics 365 Customer Insights pricing guide so this page does not compete as a pure pricing result.

Customer Insights - Journeys vs HubSpot, Salesforce MC, and Odoo

The decision is rarely “cheapest software line item.” Compare ecosystem lock-in, implementation effort after outbound retirement, attach eligibility, and who owns the system of record for leads and consent.

HubSpot Marketing Hub is often faster to first campaign for SMBs, with seat- and contact-tier economics that feel familiar. Public 2026 list guidance commonly puts Marketing Hub Professional around the high-hundreds to ~$890/month entry (limited core seats included, contact tiers extra) and Enterprise multi-thousand dollars per month — still seat-shaped, not Interacted People–shaped. It is weaker as a native Dynamics/Dataverse citizen; integrations exist, but you maintain a second system of engagement, dual consent models, and nightly or connector-based score syncs. Salesforce Marketing Cloud (and Account Engagement) targets large enterprise multi-channel programs with deep SFDC CRM alignment and higher complexity and cost. Customer Insights - Journeys wins when Sales, Service, or Field Service already live in Dynamics and you want one Dataverse model for journeys, scores, events, and Copilot agents.

Odoo Marketing (Email Marketing, SMS Marketing, Marketing Automation, Events, Surveys) ships inside the Odoo Enterprise per-user subscription rather than a separate tenant capacity meter. For SMEs that want CRM + ERP + marketing under one predictable per-user bill — and do not need Power Platform depth or Microsoft AI Hub governance — Odoo often wins the total-cost argument. Flectic implements both Dynamics 365 and Odoo, so the comparison is requirement-led, not brand-led.

Implementation after outbound: what SMEs should plan for

Buying the license is the easy part. Post–May 2026, every new and migrated estate runs real-time journeys only. Teams coming from classic Dynamics 365 Marketing should treat migration as a redesign: rebuild events for real-time, re-author segments and consent paths, map triggers to form submits and CRM stage changes, and retire “blast list” mental models. Outbound-era assets that still appear in Dataverse tables are history, not live orchestration.

A practical SME implementation sequence looks like this: (1) confirm attach eligibility and rough Interacted People sizing against your peak month, (2) clean contact/lead hygiene and consent flags in Dataverse, (3) stand up a small set of trigger journeys (welcome, MQL nurture, event follow-up) before complex multi-branch trees, (4) wire lead scoring grades into Dynamics 365 Sales views and SLAs, (5) enable AI Hub features only after brand and legal review of agent-generated content. Sandbox load tests burn the same tenant Interacted People and monthly interaction meters as production — schedule UAT carefully.

If your marketing data is fragmented across ecommerce and support systems, phase Customer Insights - Data unification after the first Journeys go-live rather than boiling the ocean. If your stack is not Microsoft-centric and your team needs a campaign live in days, HubSpot or Odoo Marketing may be the honest first phase with a later Dynamics path if Sales moves onto Dataverse.

Where Customer Insights - Journeys fits an SME

Tenant-level licensing makes Customer Insights - Journeys a different economic calculation than per-seat CRM. If your SME already runs a qualifying Dynamics 365 base (Sales Enterprise, Customer Service Enterprise, Field Service, Finance, Supply Chain, Commerce, or Sales Professional/Premium at the right count), the $1,000/tenant/month attach is the lever that makes the platform defensible — you add marketing automation across the whole tenant rather than buying another per-seat marketing SaaS.

If you do not qualify for attach, $1,700/tenant/month base is a real number for an SME budget, and it is the point at which a platform-neutral partner should put Odoo (or HubSpot) on the table. A 10-person company marketing to 50,000 active contacts can exhaust Interacted People faster than a 200-person company with a focused 8,000-contact list — size the database and monthly send volume before you sign, then open the Dynamics 365 Customer Insights pricing guide for pack-level math.

Also budget implementation: real-time journeys, consent, and event rebuild after outbound removal are project work, not a weekend toggle. Copilot helps draft, but data model, segments, and sales handoff still need design.

Flectic implements both Dynamics 365 and Odoo. Where Customer Insights - Journeys is the right answer, we ship it with our AI-Accelerated Delivery Framework — designed to deliver up to 3× faster than a traditional waterfall ERP/CRM rollout by embedding AI into discovery, documentation, process analysis, testing, and training. That wording is deliberate: it is a delivery target supported by reusable templates and agile execution, not an unconditional guarantee.

• →Choose Customer Insights - Journeys (attach) if you already run 10+ users of a qualifying Dynamics 365 app and want natively integrated real-time journeys, segments, events, and lead scoring on Dataverse.
• →Choose Customer Insights - Journeys (base) if Power Platform, Microsoft 365 Copilot, and Microsoft integrations justify the $1,700 tenant fee against your Interacted People footprint.
• →Choose HubSpot if time-to-first-campaign and a non-Microsoft stack matter more than Dataverse-native journeys.
• →Choose Odoo Marketing if per-user cost predictability and one subscription across CRM + ERP + operations matter more than Microsoft ecosystem depth.
• →Book an ERP Readiness Call with Flectic for a neutral scoping across Dynamics 365 and Odoo before you commit.

Frequently asked questions