01 · Records and state owned
Search data and metadata; create, update and delete records; query supported SQL SELECT; create/update/delete tables and skills; transfer files, governed by Dataverse security and explicit approval for destructive tools
Microsoft
Dynamics 365 / Dataverse
Curated anchor platform in crm and business application platform with material relevance to the Marcom operating stack and a first-party developer surface.
CRM, revenue & customerSystem of recordBYO-UI-ready platform
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.
02 · Data you can retrieve
Search data and metadata; create, update and delete records; query supported SQL SELECT; create/update/delete tables and skills; transfer files, governed by Dataverse security and explicit approval for destructive tools
03 · Actions and write paths
Dynamics 365 / Dataverse's first-party MCP/agent surface includes state-changing tools in the documented capability area: Search data and metadata; create, update and delete records; query supported SQL SELECT; create/update/delete tables and skills; transfer files, governed by Dataverse security and explicit approval for destructive tools. The audit did not enumerate every mutation; verify the current tool catalog and require explicit confirmation for consequential actions.
04 · Authentication and permissions
Authentication model is documented by the vendor; inspect the cited source before implementation. Official Microsoft documentation confirms a per-environment endpoint, row-level and role-based security, external-agent billing, and a separate preview-tool surface.
05 · Monitoring, approval, and recovery
Official Microsoft documentation confirms a per-environment endpoint, row-level and role-based security, external-agent billing, and a separate preview-tool surface. Official Microsoft documentation confirms a per-environment endpoint, row-level and role-based security, external-agent billing, and a separate preview-tool surface. Distinguish Dataverse data MCP from Power Apps agent-feed/supervision MCP.
06 · Gaps and implementation limits
Official Microsoft documentation confirms a per-environment endpoint, row-level and role-based security, external-agent billing, and a separate preview-tool surface. Distinguish Dataverse data MCP from Power Apps agent-feed/supervision MCP.
First-party access
Documented surfaces
Dataverse SQL SELECT ↗The Dataverse MCP read_query tool runs the supported Dataverse SQL SELECT subset. Dataverse row-level security, roles, environment selection, supported syntax, billing, tool availability, and approval requirements for separate destructive tools define the boundary.Source: Connect to Dataverse with model context protocol (MCP)API ↗Developer accessDeveloper docs ↗SDKs and platform guidanceEvents / extensions ↗Webhooks, apps, or extensionsProduct ↗Native platform experience
Agent access
MCP and adjacent posture
Verified first-party provider MCPEnvironment-specific Dataverse remote MCP plus separate Power Apps MCP toolsCurrent service with additional preview tools
Role: provider
Read scope: Search data and metadata; create, update and delete records; query supported SQL SELECT; create/update/delete tables and skills; transfer files, governed by Dataverse security and explicit approval for destructive tools
Write scope: State-changing tools are present in the documented scope; review the official tool catalog and require confirmation for consequential actions.
Authentication: Authentication model is documented by the vendor; inspect the cited source before implementation.
Approval boundary: Official Microsoft documentation confirms a per-environment endpoint, row-level and role-based security, external-agent billing, and a separate preview-tool surface.
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 access4
Identity4
Governance4
Agent access3
UI extensibility3
Portability4
Observability3
Documentation5
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
- Role-specific CRM and customer-operations workspace
- Account journey room
- Pipeline-quality debugger
- Customer expansion cockpit
Multi-platform compositions
- Dynamics 365 / Dataverse + marketing or intent platform: account journey room
- Dynamics 365 / Dataverse + conversation or support system + analytics or warehouse: cross-system decision workspace
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.
5 recorded sources
MCPRepresentative source
https://learn.microsoft.com/en-us/power-apps/maker/data-platform/data-platform-mcp ↗Official Microsoft documentation confirms a per-environment endpoint, row-level and role-based security, external-agent billing, and a separate preview-tool surface. Distinguish Dataverse data MCP from Power Apps…
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 10, 2026
Targeted first-party MCP/agent-role review; broader API inventory retained
APISource inventory
https://learn.microsoft.com/en-us/power-apps/developer/data-platform/webapi/overview ↗First-party API reference or API overview recorded for this platform.
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 10, 2026
Inventory source: structurally normalized; content was not individually reopened in this pass.
Developer docsSource inventory
https://learn.microsoft.com/en-us/power-apps/developer/data-platform/ ↗First-party developer documentation or platform overview.
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 10, 2026
Inventory source: structurally normalized; content was not individually reopened in this pass.
Webhooks / extensionsSource inventory
https://learn.microsoft.com/en-us/power-apps/developer/data-platform/webapi/use-webhooks ↗First-party webhook, event, SDK, embedded-app, or extension documentation.
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 10, 2026
Inventory source: structurally normalized; content was not individually reopened in this pass.
HomepageSource inventory
https://www.microsoft.com/en-us/dynamics-365 ↗First-party product homepage used to confirm product identity and current positioning.
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 10, 2026
Inventory source: structurally normalized; content was not individually reopened in this pass.
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.