Microsoft

Dynamics 365Customer Insights

Customer Insights MCP tools let agents resolve source identities into unified customers, inspect profile provenance and analytics, check consent, and generate context-specific unsubscribe links.

Marketing automation, lifecycle & CDPSystem of engagementExtensible SaaS
An illustration of access surfaces surrounding a governed system.
System roleSystem of engagement
Access maturityExtensible SaaS
MCP supportOfficial MCP server
Reference updatedNot stated by publisher
BYO-UI reviewedJul 22, 2026

Concrete capability record

Data, retrieval, actions, identity, and operating limits

A field-by-field summary of what the reviewed first-party references actually support. Publisher update dates and BYO-UI review dates are shown separately below.

01 · Records and state owned

Source records, unified customer profiles, winning-value provenance, segments, measures, predictions, clusters, consent records, compliance profiles, purposes, topics, and unsubscribe links.

02 · Data you can retrieve

Resolve source or Contact IDs, retrieve unified profiles with source provenance, inspect segment membership, measures, predictions and clusters, and check channel-specific consent.

03 · Actions and write paths

The documented tools retrieve customer data and consent or generate unsubscribe links; the Journeys consent tools do not send messages or update consent records.

04 · Authentication and permissions

Calls execute in the user's Dataverse context and honor custom API privileges, tool authorization, security roles, and row-level access without privilege escalation.

05 · Monitoring, approval, and recovery

Apply Dataverse role and row security, authorize individual tools, and bind consent checks or unsubscribe links to the intended compliance profile, purpose, topic, channel, and contact point.

06 · Limits and caveats

The capability is prerelease Preview and Microsoft says it is not intended for production use. Many data tools require a unified customer ID.

First-party MCP tool catalog

11 named MCP tools · Customer Insights MCP preview

The 11 exact Customer Insights Data and Customer Insights Journeys tool names in Microsoft's preview reference. The tools resolve source records to unified profiles and retrieve profile, segment, measure, prediction, cluster, and consent context. Reviewed Jul 10, 2026. Preview documentation is subject to change. Customer Insights Data tools read live Dataverse virtual entities; source types are discovered dynamically. Microsoft advises confirming parameters and schemas against the deployed server definition.

First-party exact listComplete list on cited pageDynamics 365 Customer Insights MCP server
Source discovery and identity resolution4
msdynci_listsourcesreadmsdynci_findcustomerbynamereadmsdynci_getcustomeridforcontactreadmsdynci_getcustomerbysourceidread
Unified profile and insights5
msdynci_getcustomerdetailsreadmsdynci_getcustomersegmentsreadmsdynci_getcustomermeasuresreadmsdynci_getpredictionsreadmsdynci_getclusterinformationread
Journeys consent2
msdynmkt_checkconsentreadmsdynmkt_getunsubscribelinkread

Agent access

MCP support

Official MCP serverDynamics 365 Customer Insights MCP toolsPreview

Support: Official MCP server

Read scope: Expose identity resolution, profile provenance, memberships, measures, predictions, clusters, and consent status while preserving source identifiers, unified customer ID, business unit, and consent context.

Write scope: All 11 reviewed named tools in the published catalog are read-only.

Authentication: Customer Insights tools are Dataverse custom APIs invoked in the caller's Microsoft environment context; Microsoft documents mutual TLS between Copilot Studio and Dataverse.

Approval boundary: Confirm the customer match and full consent context before exposing an unsubscribe link; distinguish generated output from any later delivery or consent-change workflow.

Protocol does not erase product boundaries.

Confirm the current tool catalog, plan, region, scopes, rate limits, terms, and write behavior before implementation.

Editorial assessment

Access-maturity dimensions

A comparative architecture lens—not a quality score, market ranking, or buying recommendation. Scale: 1–5.

Data access4
Action access4
Event access1
Identity4
Governance4
Agent access3
UI extensibility4
Portability3
Observability3
Documentation4

Proposed customer-shaped experiences

What customers could create on top.

The output could be an export, report, graph, artifact, application, agent, workflow, or downstream feed. These proposals are derived from documented access—not claims that Microsoft ships them.

Single-platform patterns

  • Customer profile, segment, and journey cockpit
  • Lifecycle journey debugger
  • Audience activation workbench
  • Campaign QA and approval room
Use in the brief builder →

Multi-platform compositions

  • Dynamics 365 Customer Insights + CRM or commerce system: lifecycle journey debugger
  • Dynamics 365 Customer Insights + warehouse or CDP + content-production platform: cross-system decision workspace
Explore composition recipes →

Evidence and dates

First-party references, with publisher and review dates separated

“Publisher updated” is shown only when the page exposes an update date. “BYO-UI reviewed” records when this research checked the reference. A missing publisher date is reported as missing—not replaced with the review date.

4 recorded sources

Verified fact

Tied to cited first-party evidence reviewed for this profile.

Source inventory

Official links recorded for deeper research but not necessarily reopened endpoint by endpoint.

Editorial assessment

System role, maturity interpretation, and architectural boundary.

Proposed design

Interface patterns and compositions—not vendor product claims.