Dynamics 365 Customer Insights: Data, Journeys & the D365 CDP

Customer Insights Is Two Apps Under One License

The first thing to get straight about Dynamics 365 Customer Insights is that the product name refers to a licence, not a single application. Buy Customer Insights and you receive the right to install two distinct apps that share one entitlement pool: Customer Insights - Data, which Microsoft describes as its customer data platform (CDP), and Customer Insights - Journeys, the real-time marketing and journey-orchestration engine. Microsoft's product overview is explicit that the two together 'comprise the Dynamics 365 Customer Insights product,' and that the combined CDP plus real-time journey orchestration is what lets teams deliver personalised customer experiences across sales, marketing, and service.

This two-apps-one-licence structure is the result of a consolidation that folded the old standalone Customer Insights (Data) SKU and the old standalone Dynamics 365 Marketing SKU into a single combined entitlement. Microsoft's Customer Insights FAQ states the rename plainly: Customer Insights - Journeys is formerly Dynamics 365 Marketing, and Customer Insights - Data is formerly the standalone Customer Insights app. If you learned Dynamics 365 marketing five years ago, you knew 'Dynamics 365 Marketing' as a separate product and 'Customer Insights' as a separate analytics product — they are now one buy. That history matters for scoping: it explains why the same licence key unlocks both a data platform and a marketing-automation engine, and why pricing conversations talk about profile volume and marketing volume rather than seats.

Because the apps share a tenant-level entitlement, the two meter differently but on the same invoice. Data drives a People Unified meter (unique resolved customer profiles); Journeys drives a People Interacted meter (contacts, leads, accounts, or Insights profiles you actually engage). You can lean heavily on one app and barely touch the other, and the platform is designed so that unified profiles built in Data flow into segments and journeys in Journeys. Understanding that split is the foundation for everything else in this guide — architecture, pricing, outbound-removal risk, and the 2026 journey features all flow from it.

What 'Customer Data Platform' Actually Means Here

Customer Insights - Data is Microsoft's customer data platform, and Microsoft's own documentation defines the CDP's job plainly: deliver 'a holistic view of customers' by unifying customer data with operational and IoT data in real time, then enriching those profiles and turning the result into a customer-centric organisation for marketing, sales, and service teams. In practice that means the Data app ingests records from your transactional systems, your website and behavioural sources, your demographic and survey data, and even IoT signals, resolves them into one trusted profile per customer, and exposes that profile to every other Dynamics 365 app and to Power Platform.

What separates a true CDP from a marketing database is the unification step. Raw source data arrives with duplicate contacts, mismatched IDs, and partial records — a customer who is 'John Smith' in the POS, 'jsmith@gmail.com' in the web analytics, and 'Account 4471' in the ERP. Customer Insights - Data matches and merges those identities using configurable match rules, deduplicates them, and produces a single resolved profile that carries a unified timeline of interactions. That resolved profile is the asset the rest of the product is built on: segments are built from it, journeys query it, sellers see it, and AI predictions are scored against it.

The other defining CDP trait Microsoft emphasises is governance. The Data app is built on Microsoft Azure, which means the security, privacy, and compliance tooling — encryption, data residency, role-based access, audit — is enterprise-grade and inherits the customer's existing Microsoft compliance posture. Microsoft positions this as the reason regulated industries choose a CDP built on Azure over a point solution: the same controls that govern Dynamics 365 and Microsoft 365 govern the customer profile. For finance, healthcare, and public-sector buyers, that lineage is often the deciding factor rather than any single feature.

Where the Data Comes From: Connectors and Unification

Before the CDP can unify anything it has to ingest, and Customer Insights - Data offers two fundamentally different ways to connect a data source: a connector can attach directly to the source data, or it can copy it. Microsoft's data-sources guidance recommends attaching whenever possible, because attached data is read live at processing time and avoids the lag that copies introduce when the source updates. The attach-capable connectors include Fabric OneLake managed Delta tables (in preview), Azure Data Lake Storage Delta tables, Azure Data Lake Storage Common Data Model tables, Microsoft Dataverse, and Azure Synapse Analytics (in preview). For SMEs already on the Microsoft stack, Dataverse and Azure Data Lake Storage are the most common entry points because the data is already there.

Under the hood, the native processing format is Delta — the same open table format that powers the Databricks lakehouse — and Microsoft recommends supplying source data in Delta whenever you can. Delta brings real engineering advantages to the CDP: superior compression for faster ingestion, ACID transactions that reduce corrupted partitions and the data-corruption issues common with older CSV formats, and the ability to do incremental unification. With incremental unification, Customer Insights - Data only reprocesses the records that actually changed (using Delta's time-travel feature) instead of rebuilding the entire profile set on every run — a large efficiency gain as the profile count grows past tens of thousands.

Once data is ingested, the unification pipeline runs through a guided process: map the source fields to a common schema, define match rules to identify the same customer across sources, set merge preferences to decide which source wins when fields conflict, and review the resulting unified profiles. Microsoft Dataverse is special here because it is the native system of record for Dynamics 365 — contacts, leads, and accounts already live there, so a Dynamics 365 customer can stand up a first unified profile set quickly by attaching to Dataverse and then layering web behavioural data and transactional data on top. The output of unification is a customer profile table that downstream features — segments, measures, enrichment, predictions, and journeys — all read from.

Segments, Enrichment, and Predictive Models

Unified profiles are only useful if you can act on them, and Customer Insights - Data turns them into action through three capabilities: segmentation, enrichment, and prediction. Segments are dynamic audiences built on any combination of unified attributes and measures — 'customers in Canada who purchased in the last 90 days and have not opened an email in 60 days,' for example — and they refresh as the underlying data changes, so a segment defined once keeps representing the current reality rather than a static snapshot. Microsoft describes the goal as letting marketers build new segments or discover new audiences with AI recommendations that are 'continually updated with real-time data.'

Operational detail that trips teams up: published segments that sit unused are expired so they stop consuming evaluation resources. Microsoft has extended that unused-segment expiration window to 120 days; expired segments can be republished into a ready-to-use state. In Journeys, keep live-campaign segments on an intentional publish cadence so they do not quietly fall out of evaluation. Treat segment hygiene as part of capacity and performance planning, not a one-time setup task.

Enrichment extends profiles with data the customer does not own outright. Microsoft and partner data sources layer on firmographics, interests, product usage, and market data so that a thin transactional record becomes a rich, targetable profile. A B2B account that arrives as little more than a domain name can be enriched with industry, employee count, and revenue band; a B2C contact can be enriched with demographic and affinity data. Enrichment is what turns a unified profile from a record of 'what happened' into a prediction of 'what this customer is likely to do next,' and it is the capability most often underused by teams who stop at unification.

Prediction is where the prebuilt AI models earn their keep. Customer Insights - Data ships with out-of-the-box models for common marketing questions — customer churn risk, transactional anomaly, subscription churn, and customer lifetime value, among others — that can be applied without a data-science team, and Microsoft also positions the platform for organisations that want to rapidly build, test, and deploy custom AI/ML models. For an SME, the practical first step is usually the prebuilt churn or lifetime-value model applied to the top revenue segment; the custom-model path is a later phase for teams that have a data scientist and a specific question the prebuilt models do not answer. Scored attributes then become segment filters and journey branches — for example, high-churn-risk customers enter a win-back path while high-LTV customers enter a white-glove nurture.

Customer Insights - Journeys: Orchestration, Not Bulk Email

Customer Insights - Journeys is the engagement half of the product, and it is best understood as a real-time journey orchestrator rather than a bulk-email blaster. It uses triggers — a behavioural event like 'abandoned cart,' a segment membership change, a date, or a custom event — to start a customer on a branched journey, and it then orchestrates the next message across channels based on how that customer responds. Microsoft's product page frames it as the engine that helps you engage customers using prebuilt digital channels including text, email, and push notifications, with the ability to add custom channels to the journey. For SMEs that means one tool can run a welcome email series, an SMS shipping alert, and a win-back push notification as a single connected flow rather than three disconnected campaigns.

A critical scoping detail, and one that catches migrating customers off guard, is that Customer Insights - Journeys is real-time marketing only. The legacy outbound marketing engine that older Dynamics 365 Marketing customers relied on is gone: Microsoft's outbound-removal notes state the outbound module was removed from all environments in May 2026, after a multi-year transition that stopped new outbound creation earlier and phased out live outbound assets through late 2025 and early 2026. If you are still holding outbound emails, forms, journeys, or lead-scoring models, those assets are not usable in real-time journeys even when underlying tables remain readable in Dataverse or the Maker portal. Plan a real-time rebuild for campaign logic, consent, triggers, and events — not a checkbox migration.

The journey engine also closes the loop back into the rest of Dynamics 365. As journeys progress, they score and qualify leads and then hand those scored, qualified leads off to sellers automatically, complete with prebuilt analytics dashboards that measure pipeline impact. That handoff is the heart of the connected customer journeys across sales, marketing, and service promise: a contact's behaviour in a marketing journey can surface them to a seller at the right moment, with the unified profile from the Data app attached so the seller sees the full context. Consent is enforced with compliance profiles, purposes, and topics so who can be emailed, texted, or called is governed at the journey level rather than left to campaign-by-campaign discipline.

Outbound Marketing Removed (May 2026): What Still Exists

Microsoft's official removal notes are unambiguous: Dynamics 365 Customer Insights - Journeys previously included an additional module called outbound marketing, and that module was removed in May 2026. The sitemap entry and outbound services are gone. This is not a deprecation warning anymore — it is completed product surgery. Organisations that delayed the real-time transition are now in recovery mode: historical data may still be queryable, but the outbound designer and runtime are not coming back.

What Microsoft did not delete wholesale is the data layer. Publicly documented outbound tables and many assets remain in the environment, but they are not refreshed and often cannot be used from the real-time UI. Asset library items that are shared components remain available to real-time journeys. Events tables were shared and were not removed — yet outbound event forms and pages are not usable in real-time and must be recreated. Outbound segments may still appear, but member lists lived in internal tables that were removed, so those segments should not be trusted. Marketing lists (the Sales entity) can still feed real-time dynamic segments. Emails, content blocks, forms, marketing pages, consent records, outbound journeys, templates, lead scoring models, social posts, and subscription lists may still exist as records, but they cannot be used in real-time and custom UIs that depended on outbound services may fail.

Analytics is another trap. Outbound marketing analytics data was merged with real-time journeys interaction data; old Power BI custom reports against outbound shapes break because format, location, and access methods differ. Rebuild reports against the Customer Insights - Journeys interaction data schema (including SourceSystem to distinguish historical outbound vs real-time) or export via Microsoft Fabric. Treat May 2026 as a hard cutover for operations: inventory any remaining outbound-dependent automations, recreate events and high-value journeys in real-time, re-map consent purposes/topics, and retire custom plugins that expected outbound retrieve patterns. Partner chatter still flags this as an admin-ticket generator months after the formal cutover.

2026 Wave 1: Dynamic Content, Live Segments, and Agentic Ops

Microsoft's 2026 release wave 1 plan for Customer Insights - Journeys (April–September 2026) groups investment into three themes: agents and Copilot, elevated customer experiences, and pipeline growth. For marketing operators, the day-to-day upgrades that cut friction are dynamic content blocks, live segment membership updates without journey restarts, message expiration, and journey-driven record creation — the features that reduce rebuilds and stale sends.

Dynamic content blocks (public preview, general availability targeted mid-2026) solve a classic email-operations tax: legal disclaimers, footers, product offers, and other shared snippets used to be static. A dynamic block updates everywhere it is used when the source content changes, and it supports personalisation and conditional content inside the block. That turns reusable components into a controlled content system instead of copy-paste debt across hundreds of emails.

Live segment updates without journey interruptions (targeted for general availability later in the wave) address a long-standing real-time journeys pain: changing segment criteria used to mean pausing or rebuilding a live journey so newly qualifying contacts could enter. The updated behaviour lets you publish segment changes and have newly qualifying contacts enter ongoing journeys in real time, while contacts already mid-journey complete their current path and recurring journeys pick up the new logic on the next cycle. Message expiration keeps event reminders and time-bound offers from sending after they are irrelevant. Create Record (preview) lets journeys write Dataverse records without custom code — useful for cases, opportunities, or operational follow-ups spawned from marketing engagement.

Wave 1 also doubles down on agentic orchestration: Copilot-assisted journey design, lead and record creation from journeys, and tighter use of behavioural and predictive signals from earlier campaigns. Practitioners tracking Microsoft Dynamics community coverage in mid-2026 still call out journey quota limits and operational controls as day-two concerns — capacity planning for People Interacted and interaction volumes remains as important as flashy AI features. Design governance (who can publish dynamic blocks, who can change live segments, which agents may create records) before you scale autonomous outreach.

Copilot and the New Agentic Layer

Microsoft Copilot is woven through Customer Insights, and it changes how non-technical users interact with both apps. In the Data app, Copilot lets analysts ask questions in plain language to explore and understand customer data, discover attributes through individual profile summaries, and get insights faster without writing queries. In segmentation, you describe the audience you want to Copilot — 'show me high-value customers at risk of churn' — and it builds, reviews, and modifies the segment for you. In Journeys, Copilot helps define the business goal, target audience, or desired flow to simplify journey creation, and it can generate tailored content, headlines, branded emails, and images for any segment.

The newer and more strategically important layer is agentic AI. Microsoft now positions Customer Insights as the intelligence layer to power agentic customer experience, with purpose-built agents such as the Journey Creation Agent (assembles complex customer journeys and supports A/B testing) and the Outreach Optimization Agent (automates timing and follow-up across sales, marketing, and service). Conversational capabilities can deliver SMS and voice via an AI agent to proactively engage customers. For a buyer evaluating the platform in 2026, the question is no longer just whether it has a CDP and a marketing engine but how far along the agentic roadmap is, because Microsoft's investment is clearly tilting toward agents that act, not just assistants that suggest.

The practical implication for an SME is that the skills needed to run Customer Insights are shifting. Where the first generation of the product rewarded a marketing-operations specialist who could build segments and journeys by hand, the Copilot-and-agent generation rewards someone who can describe outcomes in natural language, evaluate the AI's output critically, and govern what the agents are allowed to do automatically. That is a lower barrier to entry for getting started, but a higher governance bar for letting agents send real customer communications unsupervised. Planning for that governance — who approves an agent's outreach, what guardrails constrain it, how you audit it — should be part of the implementation from day one.

How Customer Insights Fits the Dynamics 365 Stack

Customer Insights is designed to be the connective intelligence layer that sits across the Dynamics 365 apps, and understanding that position is what makes the licence worthwhile rather than an isolated purchase. The foundation is Microsoft Dataverse, the shared data platform that already underpins Dynamics 365 Sales, Customer Service, and Field Service. Because Customer Insights - Data attaches to Dataverse, the unified profiles it builds are available to those apps natively: a seller sees the unified timeline and predicted lifetime value inside Sales, a service agent sees the same profile inside Customer Service, and there is no second copy of the customer record to reconcile.

The integration works in both directions. Journeys hand scored, qualified leads to sellers, and Microsoft positions the platform as helping service agents prioritise and personalise the service level using a predicted customer lifetime value. Beyond the first-party Dynamics 365 apps, Customer Insights connects into the broader Microsoft data and low-code stack. Power Platform (Power Apps, Power Automate, Power BI) reads from the same Dataverse foundation, so a custom internal app or an automated workflow can consume unified profiles and segment membership. For data-rich organisations, the bridge to Microsoft Fabric — and the Fabric OneLake Delta-table connector in preview — means Customer Insights - Data can live alongside a full lakehouse rather than forcing customer data into a silo.

This stack fit is the real differentiator versus buying a standalone CDP or a standalone marketing-automation tool. A standalone product has to be integrated, synced, and reconciled with your CRM forever; Customer Insights is already part of the same security model, the same data layer, and the same admin tooling. The trade-off is that the value compounds only if you actually run more than one Dynamics 365 workload. An organisation that buys Customer Insights in isolation, with no Sales or Service app to feed and no Power Platform build to extend it, gets a capable CDP but leaves most of the integration advantage on the table. The architecture argument is strongest for teams that are, or are becoming, a Dynamics 365 shop.

Customer Insights Journeys vs HubSpot vs Salesforce Marketing Cloud

Dynamics-centric buyers usually shortlist three marketing-automation paths: stay native with Customer Insights - Journeys, adopt HubSpot as a faster SMB marketing suite, or go enterprise multichannel with Salesforce Marketing Cloud (or Marketing Cloud Account Engagement for lighter Salesforce CRM shops). Feature grids from partner guides converge on the same pattern: Journeys wins on native Dynamics and Dataverse fit; HubSpot wins on time-to-value and marketing-plus-light-CRM packaging; Salesforce Marketing Cloud wins on channel breadth and large-scale enterprise programmes.

Choose Journeys when sellers and service agents already live in Dynamics 365, when you need real-time trigger journeys tied to CRM state changes, and when a unified CDP profile (Customer Insights - Data) should feed Sales and Service without a second integration project. Choose HubSpot when a small marketing team needs landing pages, email, and basic automation quickly and your CRM is light or multi-vendor. Choose Salesforce Marketing Cloud when you are already a Salesforce house with high-volume multichannel programmes and dedicated marketing-ops staff. Mixing HubSpot or SFMC with Dynamics Sales is common but permanently pays an integration tax — identity sync, consent dual-write, and campaign attribution glue never fully go away.

Price models also diverge. Customer Insights is a prepaid tenant capacity licence (People Unified + People Interacted), not a seat pack for marketers. HubSpot is typically seat- and contact-tier based with onboarding packages. Salesforce Marketing Cloud is enterprise-quoted and often multi-cloud. For an SME already carrying Dynamics 365 user licences, the attach-priced Customer Insights base is often cheaper than standing up a second CRM-adjacent marketing stack — but only if you will actually use the unified profile and real-time journeys rather than treating Journeys as a simple email blaster.

Sizing, Pricing, and the Metered Reality

Customer Insights pricing inverts the mental model most buyers bring from the rest of Dynamics 365, and getting it right early prevents budget surprises. Microsoft's Customer Insights FAQ and product guidance list the base SKU at $1,700 per tenant per month for new Dynamics 365 customers, or $1,000 per tenant per month attach pricing for existing, qualifying Dynamics 365 customers. The base includes the minimum required capacity: 100,000 People Unified and 10,000 People Interacted, with rights to install the apps across environments. Crucially, there is no per-user line: the same licence covers a five-person marketing team and a fifty-person one, provided they work from the same profile and marketing-contact counts. Microsoft's licensing guidance states that Customer Insights licenses are not seat-based and that the base plan includes unlimited users.

The metered part is what turns that headline into the real invoice, and it runs on two independent axes. People Unified counts the unique customer profiles the Data app merges; People Interacted counts the contacts, leads, accounts, or Insights profiles you engage through Journeys (outbound or inbound interactions such as form fills, across first-party channels, Azure Communication Services, or integrated third-party channels). When either meter grows past the base entitlement, you buy additional capacity SKUs separately — so you can scale Data without scaling Journeys, or the reverse. Capacity increases can happen mid-term; reductions typically wait for agreement anniversary under commercial programme rules. We cover every tier, the metering rules, and a worked total-cost scenario in our dedicated Dynamics 365 Customer Insights pricing guide.

The platform's economics are best evidenced by Microsoft's own commissioned study. A Forrester Total Economic Impact study of Dynamics 365 Customer Insights, cited on Microsoft's product page, reports a 324% return on investment over three years, 75% time savings on customer journey development, less than six months to payback, and a 15% improvement to the conversion rate per customer journey (April 2024 Forrester TEI for a composite organisation). Those figures describe what a well-implemented deployment can return, and they are useful for building the internal business case — but they are realised only when the unified profiles, the journeys, and the sales handoff are all live and feeding each other. Buying the licence without the implementation discipline to connect those pieces is how organisations end up paying for a CDP they never fully switch on.

When to Choose Customer Insights — and When Not To

Customer Insights is the right answer when three conditions line up: your customer data is genuinely fragmented across systems that need unifying, you run (or are committing to) more than one Dynamics 365 workload so the integration advantage compounds, and your marketing volume and profile count are large enough that a metered tenant licence beats per-seat marketing-tool pricing. In that profile — a mid-market business already on Dynamics 365 Sales or Business Central with real data silos and a marketing team larger than a couple of people — the platform's combination of a unified CDP, real-time journey orchestration, and native Dataverse fit is hard to beat without stitching multiple vendors together.

It is the wrong answer in two common situations. The first is the very small team that needs basic email marketing and a simple contact database: the metered, tenant-level model and the implementation effort to unify data sources are overkill, and a lighter marketing module — including Odoo's own marketing, email-marketing, and marketing-automation apps, which are included in the Odoo enterprise subscription rather than metered separately — will reach the same outcome at a fraction of the cost and complexity. The second is the organisation whose data is already clean and unified in a single system and whose only need is campaign execution: there is no CDP problem to solve, so paying for a CDP adds overhead without adding insight. A third failure mode is post-outbound denial: teams that still expect classic Dynamics Marketing campaign designers and bulk outbound patterns will be frustrated — real-time journeys are a different operating model.

Because the decision genuinely depends on how your customer data is shaped and which platforms you already run, the useful next step is a platform-neutral scoping conversation rather than a product demo. Flectic implements both Microsoft Dynamics 365 and Odoo for SMEs across Canada, the UK, and the US, and the honest recommendation is sometimes Customer Insights and sometimes a lighter path — the right call depends on how fragmented your data is, how much of the Dynamics 365 stack you run, and whether your marketing volume justifies a metered tenant licence. If you are weighing Customer Insights against alternatives, our broader look at the Dynamics 365 application family and our CRM services overview lay out the surrounding context; either way, the goal is to match the platform to your real data and engagement problem before you commit to a licence.

Frequently asked questions