BYO-UI
Microsoft

Dynamics 365 Customer Insights

Curated major addition platform in customer data and journey orchestration with material relevance to the Marcom operating stack and a first-party developer surface.

Marketing automation, lifecycle & CDPSystem of engagementExtensible SaaS
Representative source ↗Product site ↗
System roleSystem of engagement
Access maturityExtensible SaaS
Agent postureFirst-party provider
Reference updatedNot stated by publisher
BYO-UI reviewedJul 10, 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

Unified profiles, segments, measures, predictions, enrichments, consent, and supported data operations.

02 · Data you can retrieve

Unified profiles, segments, measures, predictions, enrichments, consent, and supported data operations.

03 · Actions and write paths

Preview tools include supported operations beyond retrieval; verify each tool and environment.

04 · Authentication and permissions

Microsoft Dataverse / Dynamics environment authentication Environment, role, consent, and Dataverse permissions apply.

05 · Monitoring, approval, and recovery

Consequential writes should require explicit review; use vendor confirmation controls where available. Preview status; data-governance and consent constraints are central.

06 · Gaps and implementation limits

Preview status; data-governance and consent constraints are central.

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
Catalog evidence: Customer Insights MCP server tools reference

First-party access

Documented surfaces

MCP / agent surface ↗Verified first-party provider MCPAPI ↗Developer accessDeveloper docs ↗SDKs and platform guidanceProduct ↗Native platform experience

Agent access

MCP and adjacent posture

Verified first-party provider MCPDynamics 365 Customer Insights MCP toolsPreview

Role: provider

Read scope: Unified profiles, segments, measures, predictions, enrichments, consent, and supported data operations.

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

Authentication: Microsoft Dataverse / Dynamics environment authentication

Approval boundary: Consequential writes should require explicit review; use vendor confirmation controls where available.

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 interfaces

What customers could build on top.

These are design proposals derived from documented access—not claims that Microsoft ships these experiences.

Single-platform patterns

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

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 the representative first-party source or targeted access review.

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.