Dynamics 365 Customer Insights

About Dynamics 365 Customer Insights

Dynamics 365 Customer Insights is Microsoft's customer data and journey orchestration product for organizations that want to unify customer profiles, build segments and measures, and use those audiences in personalized engagement. Microsoft currently positions the product as a combination of Customer Insights - Data and Customer Insights - Journeys. It is best evaluated as a marketing and customer data platform rather than as a general CRM replacement, because its value depends on the quality of the source data, identity matching, consent design, channel setup and the surrounding Dynamics 365 or Power Platform environment.

What does Dynamics 365 Customer Insights do?

Customer Insights - Data ingests customer data from multiple sources and uses a unification process to create a single customer profile. Microsoft documents a four-step unification flow that starts with selecting customer data and then proceeds through deduplication, matching and profile consolidation. The resulting profiles can support measures, segments, enrichments and downstream activation.

Customer Insights - Journeys focuses on customer engagement. Teams can build segment-based or trigger-based journeys, use profile and interaction data for targeting, and review journey analytics. The two parts work together, but buyers should treat customer data preparation and journey orchestration as separate operational disciplines. A clean profile model does not automatically produce a good campaign, and a sophisticated journey cannot compensate for poor identity resolution or weak consent governance.

How are unified profiles and segments used?

Microsoft defines a unified customer profile as a profile created from data sources that have been matched and combined into a single customer record. Customer Insights - Data supports known profiles with identifiers such as email, phone or loyalty ID, and unknown profiles created from web tracking. Microsoft states that unknown profiles expire after seven days of inactivity unless they are converted to known profiles, and that unknown profiles do not count against profile billing.

Segments can group customers using demographic, transactional and behavioral attributes. Current Microsoft documentation supports quick segments, a rule-based segment builder, Copilot-assisted segments and suggested segments. Segment logic can use related tables and relationship paths, so data modeling matters. Teams should test segment membership carefully because incorrect relationships, stale source data or misunderstood AND/OR logic can change who is included.

What can teams measure and analyze?

Customer Insights - Data supports measures that calculate customer-level or business-level values from unified data. Microsoft examples include total spend per customer, total returns and other KPIs that can later be used in segmentation or decision making. Measures can be built from scratch or from templates, and some journey interaction data can also be used in measures.

There are operational limits to consider. Microsoft notes that having too many active measures can slow refreshes and increase the chance of failures. It also recommends deactivating or deleting unused measures and reducing refresh frequency for measures that do not need to run daily. Journey interaction data used in Customer Insights - Data segments and measures is processed in batch during system refresh, so it should not be treated as real-time event processing.

What are the current Customer Insights pricing options?

Pricing checked September 6, 2026. Microsoft's US pricing page currently lists Dynamics 365 Customer Insights at $1,700 per tenant per month, paid yearly. The base plan includes unlimited users, 100,000 Unified People and 10,000 Interacted People. Microsoft also lists Dynamics 365 Customer Insights Attach at $1,000 per tenant per month, paid yearly, for organizations that meet the qualifying Dynamics 365 application requirement.

Additional capacity is sold separately. Microsoft currently lists tiered Unified People packs and Interacted People packs, with pack size and price changing by volume tier. Buyers should not treat the base subscription as an unlimited data or engagement license. Capacity planning should include the number of unified profiles, the number of people or accounts interacted with, expected campaign volume and the cost of growth beyond the included allowances. Microsoft states that displayed prices can vary by country, region and transaction context.

What service limits matter for journey design?

Microsoft's current fair-use documentation lists several limits that can affect larger programs. Real-time journeys currently support up to 13,000 total segments, split between 3,000 dynamic segments and 10,000 static segments. A segment used to start or branch a real-time journey can contain up to 10 million members. Microsoft also documents throughput of up to 500,000 interactions per hour for segment-based journeys and up to 2,500 triggers per minute for trigger-based journeys.

These are service ceilings, not a promise that every implementation will achieve the maximum rate in every scenario. Data volume, personalization complexity, channel provider behavior, environment design and dependent Microsoft services can affect practical performance. Large programs should validate throughput and campaign timing with representative data before relying on a theoretical maximum.

How does Customer Insights integrate with the Microsoft ecosystem?

Customer Insights sits inside Dynamics 365 but also relies heavily on the wider Microsoft business applications platform. Customer Insights - Data can export unified profiles and segments for activation, while Customer Insights - Journeys can use unified profiles and measures from Customer Insights - Data. Dataverse is part of many Customer Insights workflows and is relevant to entities such as contacts, leads and accounts.

Azure Communication Services can be involved in messaging scenarios, and Power Platform can extend data, workflow and app experiences around Dynamics 365. Buyers should map these dependencies before implementation. A requirement that sounds like one Customer Insights feature can create licensing, capacity, security or administration work across several Microsoft services.

What should teams plan before deployment or migration?

Start with source data and identity rules. Teams should document which systems provide customer records, which identifiers are reliable, how duplicates should be resolved, which attributes can be used for personalization and which records require special consent or retention treatment. Microsoft recommends reviewing source data before unification and removing unwanted rows, because bad source data can create bad unified profiles.

Migration from another customer data or marketing platform should be treated as a data and operating-model project, not just a feature migration. Existing segments, scores, consent records, campaign histories, custom attributes, templates, integrations and reporting definitions may not map one-for-one. Run parallel validation for important audiences and journeys before retiring the old system.

Who is Dynamics 365 Customer Insights best suited for?

Customer Insights is a strong fit for organizations that already use Dynamics 365 or Microsoft business applications and want unified customer data plus orchestrated journeys in the same ecosystem. It is especially relevant when marketing, sales or service teams need shared profiles, richer segmentation and more coordinated engagement across customer touchpoints.

It can also suit larger organizations with fragmented customer data, provided they have the data governance and technical ownership needed to maintain identity rules, source mappings and activation processes. The product is less compelling if the business only needs basic email campaigns or a lightweight contact database.

What are the main limitations and tradeoffs?

Customer Insights can add meaningful data and campaign complexity. Profile unification requires source mapping, matching rules and ongoing data-quality work. Measures and segments need governance so unused logic does not accumulate. Some interaction data used by Customer Insights - Data is refreshed in batch rather than real time, which can matter when teams expect immediate behavioral decisions.

Pricing is also capacity-sensitive. The base license includes defined Unified People and Interacted People allowances, and additional capacity is sold in packs. Organizations with rapidly growing customer databases or high interaction volumes should model future capacity instead of evaluating only the entry price. Implementation may also involve Dataverse, consent, security roles, channel configuration and integrations outside the core product.

Who should choose something else?

A small organization that mainly needs newsletters, simple automation or basic CRM may get better value from a lighter marketing platform or from features already included in another system. Teams that only need sales pipeline management should compare Dynamics 365 Sales rather than adopting Customer Insights for functionality they do not need.

Organizations whose primary requirement is custom internal apps or workflow automation should evaluate Power Apps and Power Automate directly. Companies already standardized on another customer data platform or marketing automation suite should compare migration cost, data-model disruption, channel coverage and staff retraining before moving. Customer Insights is most defensible when unified customer data and journey orchestration are both strategic requirements, not when only one narrow campaign feature is needed.