Dynamics 365 Customer Service Plugin for Copilot Cowork: Setup, Case Workflows and Governance

Microsoft is tackling that cross-application friction with its Dynamics 365 Customer Service plugin for Microsoft Copilot Cowork. Tracked under Microsoft's AI at Work roadmap ID 576851 and documented in the Dynamics 365 2026 release wave 1 plan, the feature entered public preview on May 5, 2026, and reached general availability on June 16, 2026, for web users in Worldwide Standard Multi-Tenant cloud environments. Rather than functioning as a simple chat sidebar that summarizes a single text box, the Customer Service plugin in Copilot Cowork allows representatives to delegate multi-step case workflows that merge live Dynamics 365 records with broader Microsoft 365 context, all while enforcing human-in-the-loop review checkpoints before any CRM changes are saved.

From Single Prompts to Delegated Case Workflows​

To understand what makes this update distinct for enterprise IT administrators and service desk managers, it helps to look at how Copilot Cowork processes a request. According to Microsoft Learn documentation on using Dynamics 365 Customer Service skills in Copilot Cowork, Cowork does not treat a natural-language prompt as one opaque, black-box task. Instead, when a representative submits a request, Cowork's workspace plan translates the prompt into a visible sequence of smaller actions. It identifies the user's intent, determines which systems hold the required data, and invokes the corresponding plugin or skill for each step while displaying real-time progress in the Workspace panel.

Behind the scenes, Cowork combines three categories of skills to execute these plans:

• Built-in WorkIQ skills: Native integration with Microsoft Word, Excel, PowerPoint, PDF files, email, calendar, meetings, daily briefings, enterprise search, communications, deep research, and adaptive cards.
• Customer Service-related skills: Domain-specific skills powered by Dynamics 365 Model Context Protocol (MCP) tools that pull live case data and insights for case enrichment, response drafting, and incident resolution.
• Custom skills: Team-specific skills that users or organizations can create and store in OneDrive to tailor Cowork to bespoke triage rules, specialized knowledge sources, and internal workflows.

Because every task is grounded in both live Dynamics 365 case data and Microsoft 365 activity—such as emails, meetings, and chats—representatives do not have to manually copy and paste context between their productivity suite and their ticketing platform.

Summary: Workflow Architecture​

Copilot Cowork breaks complex customer service prompts into transparent, step-by-step execution plans, bridging Dynamics 365 records (via MCP tools) and Microsoft 365 communication history in a single web workspace.

Seven Core Capabilities for Service Representatives​

According to the Microsoft 365 roadmap and the Dynamics 365 2026 release wave 1 documentation, the out-of-the-box Customer Service plugin centers on seven core capabilities once enabled for an organization's representatives:

Microsoft Learn's usage guide illustrates how these capabilities translate into practical daily prompts. For instance, if a representative asks Cowork to "Draft a summary that lists all open cases blocked on customer reply for more than 48 hours," Cowork breaks the query into discrete steps, retrieves the matching open cases, and organizes the output by case number, title, and days waiting.

Similarly, representatives can run targeted operational prompts such as:

• "Give me a one-screen brief on case #12345 - customer, product, history, prior cases."
• "Find me my cases that are open > 5 days with no customer reply - diagnose each."
• "Draft my reply to the customer using the knowledge article that matches a specific article ID#1234."
• "Compose an escalation summary for case #12345 on what's been tried, known, and what the customer expects to assist the correct next owner or assignee."

When executing that last escalation prompt, Cowork structures the handoff packet to include an overall escalation summary, what the customer has reported so far, what troubleshooting steps the customer has already tried, a list of known facts, the customer's expectations, recommended next steps for the incoming assignee, and the specific reason the case was flagged for escalation.

Summary: Core Capabilities​

The plugin targets high-friction triage, intake briefing, knowledge matching, customer follow-ups, and escalation handoffs, turning multi-record lookups into structured single-screen briefs and action plans.

Governance, Permissions, and the Human-in-the-Loop Boundary​

Whenever an AI assistant is granted the ability to interact with a production CRM system, the first question any seasoned sysadmin asks is: Can it accidentally overwrite production records or expose restricted data?

Microsoft's architecture for Copilot Cowork addresses this on two fronts: strict permission inheritance and mandatory review checkpoints.

First, Cowork does not bypass existing security boundaries. It operates strictly within the Dynamics 365 and Microsoft 365 permissions already assigned to the individual user or their Microsoft Entra security groups. Sharing or deploying a plugin never grants a user access to records they could not view natively. Furthermore, as detailed in Microsoft Learn's plugin administration guide, plugin connectors cannot be authorized on a user's behalf; each representative must complete the Microsoft Entra ID sign-in or consent flow themselves the first time they connect.

Second, the Customer Service plugin enforces human-in-the-loop checkpoints. While Cowork can propose root causes, rank resolutions, and prepare field updates, representatives must review and approve proposed field changes and service-related tool calls before any modifications are committed to Dynamics 365. It is worth noting from an operational perspective that AI-proposed root causes, severity mismatch flags, and drafted replies remain assistive suggestions rather than guaranteed diagnostics—making human verification at each checkpoint essential for accuracy and compliance.

Summary: Security and Governance​

Cowork respects existing Microsoft Entra ID, Microsoft 365, and Dynamics 365 role-based permissions, and it requires explicit user approval at built-in checkpoints before committing record updates to Dynamics 365.

How to Set Up and Enable the Customer Service Plugin in Cowork​

Getting the Customer Service skills running requires coordination between Microsoft 365/Dynamics 365 administrators and the end-user representatives. Installing the Service app alone does not automatically enable Cowork or grant access to Dynamics 365 data.

Prerequisites for Administrators​

Before representatives can toggle the plugin on, IT administrators must verify the following requirements outlined in Microsoft Learn:

1. Licensing: Users must hold an assigned Microsoft 365 Copilot license (with access to Copilot Cowork under the organization's licensing and spending policy) and an applicable Dynamics 365 Customer Service license.
2. Environment and MCP Configuration: The user must have permissions to the target Customer Service environment and records, and the required Customer Service MCP (Dataverse MCP server) configuration must be enabled for that environment.
3. App Deployment: In the Microsoft 365 admin center (Agents > All Agents or Agents > Tools), the administrator must ensure the Service app is installed and assigned either to the entire organization or to specific users and Microsoft Entra groups.
4. Compliance Constraints: Administrators should note that Microsoft Purview Information Barriers (IB) are not currently supported for Cowork plugin or skill management and sharing. In tenants where Information Barriers are enabled, embedded knowledge file uploads are blocked at the tenant level. Meanwhile, all Copilot and plugin interactions are captured in Microsoft Purview audit logs under Copilot activities.

Step-by-Step Setup for Service Representatives​

Once an administrator has deployed the Service app and verified environment permissions, representatives can activate the skills in their web workspace using these steps from Microsoft Learn:

1. Sign In: Open Microsoft Copilot and select Cowork using the assigned organizational work account.
2. Enable the Plugin: Navigate to Customize, search for Service, and turn on the toggle for the Service plugin. (Admin-deployed plugins appear with a Managed by your organization label; users cannot uninstall them, though they can enable or disable them per device from the Sources & Skills panel.)
3. Select and Verify the Environment: Open the Settings option within the Service plugin to confirm or select the intended Dynamics 365 Customer Service environment. If the user only has access to a single environment, Cowork selects it automatically; if multiple environments exist (such as Sandbox, UAT, and Production), Cowork prompts the user to choose one.

Crucial Operational Pitfall to Avoid: Microsoft explicitly warns that selecting a Dynamics 365 environment in another Copilot experience does not necessarily carry over to Copilot Cowork. Representatives should always check their active signed-in account and selected Customer Service environment inside Cowork's Customize settings before retrieving or modifying case records. If the expected environment does not appear in the list, the user must contact their Dynamics 365 administrator to verify security role access.

Summary: Deployment and Configuration​

Administrators manage deployment and licensing through the Microsoft 365 admin center and Power Platform/Dynamics 365 MCP settings, while representatives must manually enable the Service toggle in Cowork and verify they are connected to the correct Dynamics 365 environment.

Where Native Cowork Fits in the Broader CRM Landscape​

For IT leaders planning their customer engagement roadmap, the arrival of out-of-the-box Dynamics 365 Customer Service skills in Copilot Cowork—alongside parallel Cowork plugins for Dynamics 365 Sales, Dynamics 365 ERP, and Fabric IQ—clarifies how Microsoft is segmenting its AI tools. As industry coverage from MSDynamicsWorld notes, organizations now have a clear architectural rule of thumb: rely on native Copilot Cowork skills first for standard workflows grounded in Microsoft 365 and Dynamics 365 data, and turn to Microsoft Copilot Studio when service operations demand bespoke business logic, third-party external system connectors, or heavily customized process orchestration.

For everyday support representatives, however, the immediate benefit is much simpler. Instead of playing detective across half a dozen apps just to figure out why a five-day-old ticket is stalled, they can delegate the legwork to Cowork, verify the proposed action plan at the checkpoint, and get back to actually solving the customer's problem.