Dynamics 365 plugins for Copilot Cowork: an admin setup checklist
- Published
- Author
- Lloyd Sebag
- Type
- Chronicle

At Ignite, on November 17, 2026, Microsoft announced that the Sales, Customer Service and ERP apps plugins for Copilot Cowork are generally available. Behind a one-line announcement sits a chain of settings spread over three admin centers, and a single missing link gives users a plugin that is greyed out, invisible or unable to connect. This article walks through that chain for each plugin, explains the security model, and lists the symptoms you will meet on the first day.
What the plugins are
Copilot Cowork is the agent experience of Microsoft Copilot that plans a multistep task, calls tools and asks for confirmation before it changes anything. A plugin packages skills (task recipes) and the connection to a business system. The Ignite announcement lists three of them for Dynamics 365:
| Plugin | Talks to | Through |
|---|---|---|
| Sales | Dynamics 365 Sales | The Dataverse MCP server |
| Service (Customer Service) | Dynamics 365 Customer Service | The Customer Service MCP tools |
| Dynamics 365 ERP apps | Finance and operations apps | The dynamic Dynamics 365 ERP MCP server |
The important point for an architect is the last column: every plugin is an MCP client of a server that already exists in your environment. Cowork does not get a back door into the data. It goes through the same server, with the signed-in user's identity, that a Copilot Studio agent or GitHub Copilot would use. Configuring Cowork is therefore mostly about allowing one more client on servers you may already govern.
A note on status: the blog post calls the plugins generally available, while the Learn pages, as of November 22, 2026, describe the setup without a preview banner but do not state a GA date. Treat the steps below as current, and expect the admin screens to move.
Common prerequisites
Some requirements apply to all three plugins:
- Access to Cowork: Cowork enabled in the Microsoft 365 admin center and a licence that gives access to it. The ERP page explicitly requires a Microsoft 365 Copilot licence per user; the Sales and Customer Service pages speak of "an appropriate license" under the organization's policy.
- Usage-based billing. Cowork tasks are billed in Copilot Credits according to token usage, on top of the licence. The ERP plugin page notes that a billing policy can hide the plugin, and that a user without billing sees Request access instead of Install.
- The tenant setting "Dataverse data available in Microsoft Copilot", under Copilot > Settings in the Microsoft 365 admin center. The ERP documentation explains that this setting decides whether the plugin is offered at all, and that a change can take up to an hour to propagate.
- Anthropic models in Europe. Cowork uses Anthropic models as a subprocessor for some capabilities. In the EU, EFTA and UK this is off by default and an admin must turn it on; it is not available in government or sovereign clouds.
The Dataverse setting deserves attention in European projects. The ERP documentation points out that it is often disabled where works councils are involved (it names Germany, France and Sweden), and users then see the plugin with the message that their admin disabled it. That is a governance discussion to have before the pilot, not a bug to fix on the day.
Sales plugin
The Sales skills page lists four admin checks:
- The Dataverse MCP server is enabled for the environment. In the Power Platform admin center, open the environment, then Settings > Product > Features, and check Allow MCP clients to interact with Dataverse MCP server (Dataverse MCP configuration). If you turned it off after reading about MCP risks, the Sales plugin stops with it.
- The Sales app is installed. It carries the plugin and is installed automatically for eligible organizations and users according to their licence.
- Nothing is blocked in the Microsoft 365 admin center: under Agents > Tools, neither the Sales plugin nor the Dynamics 365 Sales MCP component may be blocked.
- The toggle "Copilot Cowork, Copilot Code, and Microsoft Scout" is on in the Sales agent admin settings.
Users need a Sales Enterprise or Sales Premium licence. They switch the plugin on under Customize in the Cowork tab. On the first sales prompt, Cowork asks which Dynamics 365 environment to use and remembers it; "list environments" or "Set environment to …" changes it later. That matters in organizations with one environment per region or business line: check which one a user is pointing at before you investigate "wrong" numbers.
There is also a Sales for Cowork plugin with a subset of CRM-agnostic skills (meeting preparation, deal catch-up, business case composer…) that works on uploaded data without a Dynamics 365 licence. Make sure pilot users know which one they enabled: the skill list differs, and the CRM-agnostic version does not read your Dataverse data.
Customer Service plugin
Customer Service skills come in the Service app, which also carries the Service Agent for other Copilot experiences. The Service app page is explicit that four independent controls are involved:
| Control | Decides | Does not grant |
|---|---|---|
| Microsoft 365 admin roles | Who can install and manage the app | Access to case data |
| Service app assignment (users, Entra groups) | Who receives and may use the app | Dynamics 365 data rights |
| Dynamics 365 security roles | Which environments, records and actions a user reaches | Access to Cowork |
| Host licensing and billing | Whether the user can use Cowork at all | App assignment |
The app is managed in the Microsoft 365 admin center under Agents > All agents > Registry. Two scopes on the Users tab are easy to confuse: Installed to (preinstallation) and Available to (who may install or use it). They are independent, so narrowing only Available to does not undo an earlier organization-wide installation. For a controlled pilot, align both scopes with the same Entra group and test with an excluded user as well as an included one.
The documentation adds one piece of advice worth repeating to the people who will troubleshoot: when a user cannot see records or tools, do not give them an admin role to "make it work". Check the account, the selected environment, the Dynamics 365 privileges and the Customer Service MCP configuration instead.
ERP apps plugin
The ERP plugin has the most demanding prerequisites, because it relies on the dynamic Dynamics 365 ERP MCP server (MCP for finance and operations apps):
- Version: at least 10.0.47, 10.0.46 PQU-2 or 10.0.45 PQU-7.
- Environment: Tier 2 or above, or a Unified Developer Environment. Cloud-hosted environments (CHE) and on-premises are not supported, so the classic developer VM will not do for a demonstration.
- Feature: Dynamics 365 ERP Model Context Protocol server enabled in Feature Management (on by default).
- Licence: a qualifying finance and operations user licence (Finance, Supply Chain Management, Commerce, Human Resources, Project Operations, the Attach, Premium and Team Member variants, legacy AX full users…). Device plans, capacity add-ons and on-premises licences do not count.
- Allowed MCP client: open the Allowed MCP Clients page in the environment and add the Cowork client application ID given in the ERP plugin documentation,
6ab48b67-cd74-4ad4-81af-5932984589be. The change takes up to a minute.
Then the user installs Dynamics 365 ERP apps from Customize > Discover in Cowork, opens Sources & Skills, configures the Finance & Operations connector, picks the environment and signs in. An admin can also deploy the plugin to groups from the Microsoft 365 admin center: it then appears as managed and cannot be uninstalled, but each user still configures and signs in to the connector, and no licensing or security requirement is bypassed.
If you built agents on the earlier static ERP MCP server, with its 13 predefined tools, note that it was scheduled for retirement on October 1, 2026; Cowork uses only the dynamic server.
The security model
All three plugins act as the signed-in user. For finance and operations, the MCP documentation describes how the server returns only the menu items, entities, form fields and actions that the user's security roles allow, and rejects any explicit call outside them. Some admin forms (security configuration, users, Entra applications, feature management) are excluded from the server altogether.
Three consequences for your design:
- Security roles become an AI boundary. A role that was "a bit broad but harmless" in the UI is now reachable by an agent that can chain dozens of calls. Review the roles of pilot users before the pilot, not after.
- Confirmation is the last line of defence. Cowork asks before it updates a record, sends an email or creates a task. Train users to read the proposed change, especially for bulk operations.
- Data leaves the application boundary. The Service app page reminds admins to review destination-service terms, because data processed by another experience can leave the Dynamics 365 compliance or geographic boundary. Involve your data protection officer when EU data and Anthropic models are both in play.
Troubleshooting the first day
| Symptom | Likely cause |
|---|---|
| "Your admin has disabled this plugin" | The tenant setting "Dataverse data available in Microsoft Copilot" is off, or an admin policy blocks the plugin. Allow an hour after changing it. |
| Plugin missing from Discover | Licence, billing or deployment policy. Check Microsoft 365 Copilot, the Dynamics 365 licence and usage-based billing. |
| Request access instead of Install | Billing is not configured for the user, or a policy requires approval. |
| "No compatible Dynamics environment found" (ERP) | CHE or on-premises environment, version too old, no access, or no qualifying licence. |
| "Unable to connect" (ERP) | MCP server disabled, Cowork client ID missing from Allowed MCP Clients, or missing security roles. |
| Sales answers from the wrong data | The user selected another environment; ask Cowork to list environments. |
| Sales plugin stopped working | Someone disabled the Dataverse MCP server, or blocked the Sales MCP component under Agents > Tools. |
Key takeaways
- Each plugin is an MCP client of a server you already own: the Dataverse MCP server for Sales, the Customer Service MCP tools for Service, the dynamic ERP MCP server for finance and operations.
- Budget for usage-based billing in Copilot Credits on top of the Microsoft 365 Copilot and Dynamics 365 licences.
- In Europe, the Dataverse tenant setting and the Anthropic subprocessor switch are governance decisions; settle them before the pilot.
- For finance and operations, check the version, the environment tier and the Allowed MCP Clients entry first: they explain most connection failures.
- Review security roles with an agent in mind. The plugins never exceed the user's rights, but they make every right easier to use.
Researched and drafted with AI assistance, then reviewed, edited and published by a human.
Sources
- Microsoft Ignite 2026: Introducing Dynamics 365 in Copilotmicrosoft.com
- Enable the Dynamics 365 ERP apps plugin for Copilot Coworklearn.microsoft.com
- Use Model Context Protocol for finance and operations appslearn.microsoft.com
- Use sales skills in Copilot Coworklearn.microsoft.com
- Use Dynamics 365 Customer Service skills in Copilot Coworklearn.microsoft.com
- Manage the Service app in the Microsoft 365 admin centerlearn.microsoft.com
- Configure the Dataverse model context protocol (MCP) serverlearn.microsoft.com