Dynamics 365 Customer Service in Copilot: Cowork Plugin Documented, Chat, Code and Scout Rollout Pending

There is an important qualification: despite the item’s “now available” title, its September 30, 2026 metadata still lists In development, with a September 2026 general-availability target and availability tracked separately for each experience. That is not evidence of a simultaneous launch across all four.

What the roadmap changes—and what it does not confirm​

The entry describes an updated Service application that supplies Customer Service context, actions and guided workflows through supported Copilot experiences. First-party tools arrive through the Service package on Dynamics 365 MCP, with each call respecting Dynamics 365 business logic and the user’s existing permissions.

Its listed scope is Web, in Worldwide Standard Multi-Tenant environments. A general-availability release-ring label should not be read as proof that deployment has finished, especially alongside an “In development” status.

Microsoft also explicitly describes its roadmap dates as estimates, with information subject to change. The prudent reading is therefore a per-experience rollout—not a universal availability announcement.

The retrieved roadmap page did not expose item 571678’s individual fields, so those item-specific details remain based on the entry’s recorded metadata. Microsoft Learn does, however, independently document a Customer Service plugin for Cowork and a separate MCP connection path.

Cowork has a documented Customer Service plugin​

Microsoft Learn’s Cowork plugin catalog lists a Dynamics 365 Customer Service integration for querying and managing service cases, knowledge articles and support workflows. That gives the roadmap a concrete end-user counterpart: service work inside Cowork, rather than merely a promise of future connectivity.

The catalog establishes two useful administrative details:

• Customer Service and Sales integrations are enabled by default and can be disabled in the Microsoft 365 admin center.
• Dynamics 365 plugins require an associated Power Platform environment; users select the environment after adding the plugin.

Those requirements matter. A visible plugin is not the same thing as a connection to the correct service environment. Administrators should confirm which environment users will access before treating the integration as ready for operational work.

The boundary: Cowork documentation corroborates that integration. It does not establish identical functionality or rollout status for Chat, Code or Scout.

MCP adds an implementation path, not a launch certificate​

Microsoft Learn separately documents connecting the Dynamics 365 CX MCP Server – Service to Copilot Studio and HTTP-based MCP clients through Agent 365 Tooling Gateway. Examples include Visual Studio Code, GitHub Copilot CLI, Cursor and Claude Code; these are not confirmation that the roadmap’s Code or Scout experiences have launched.

For administrators evaluating that documented connection, three checks stand out:

• Identity: The client authenticates to the gateway, which uses an on-behalf-of exchange to reach Dataverse.
• Consent: Administrator consent is required in advance; the /.default scope does not support dynamic user consent.
• Environment: Each environment needs its own connector configuration. Omitting /mcp/environments/ from the server path produces 404 RouteNotFound.

These are deployment considerations for the MCP connection—not a claim that every Cowork user must manually build a connector.

Permissions are only part of governance​

Microsoft’s MCP documentation warns that connections to non-Dynamics 365 services, including other Microsoft services, allow data to leave the Dynamics 365 FedRAMP High boundary. The destination service’s processing, storage and residency commitments then apply. Tenant administrators must assess those requirements before enabling connections.

The practical distinction is straightforward: permission checks determine whether a user may access or act on a record. They do not, by themselves, settle whether the destination is approved to process that information.

For service teams, the potential benefit is fewer application switches. For IT, the sensible next step is narrower: validate the desired Copilot experience, confirm the target environment, and review its data-handling requirements. The roadmap points toward service work across Chat, Cowork, Code and Scout—but the evidence does not yet justify treating all four as one completed launch.