Can AI agents automate Microsoft Dynamics 365 Customer Service?

Dynamics 365 Customer Service is automatable as Microsoft's case and service application on Dataverse, not as Dynamics 365 Sales, Zendesk, or Intercom. The Case (incident) table exposes Web API POST, GET, PATCH, and DELETE on /incidents plus actions such as CloseIncident, ApplyRoutingRule, Merge, and Assign. Microsoft Learn lists further Customer Service Dataverse tables including incidentresolution, knowledgearticle, and conversation work-item tables. The Dataverse OData v4 Web API adds metadata, search, functions, actions, batch, file, and relationship operations. Microsoft Entra OAuth supports delegated users and service-principal application users. Official .NET and Python SDKs and the Power Platform CLI apply to the same environment. The generally available first-party Dataverse MCP server at /api/mcp can search, describe, read SQL, and perform record and table CRUD under existing role and row security; destructive tools need explicit approval, and external-agent calls can consume Copilot credits. Copilot agents in Customer Service are not MCP. The premium Dataverse connector covers row CRUD, files, bound and unbound actions, changesets, and row-change triggers. Microsoft's comparison table marks Omnichannel for Customer Service as Deprecated; Copilot Service workspace is the current multi-session app. Computer-use viability is unassessed.

Best path today: api · Overall automatability: 9/10