Dynamics 365 Copilot Cowork Adds 30 CRM Skills: Setup, Licensing and Governance

What Microsoft announced​

Deva Rajamohan, Corporate Vice President of Dynamics 365 Customer Experience, said on October 8, 2026 that the 30 skills are generally available in Cowork. Autopilot is in private preview. Code is available through the Frontier program. Microsoft says that across supported experiences the skills work with more than 180 generally available tools. It also says organizations can extend them into custom agents and AI harnesses.

Those counts are Microsoft's own. The Learn documentation I reviewed doesn't list all 30 skills or all 180 tools, so treat the headline numbers as vendor-reported.

The timing fits a broader push. Microsoft's September 25 Copilot announcement said Cowork, Code, and Autopilot, new long-running agentic capabilities, and frontier models like Astra and Fable all run on UBB, meaning usage-based billing. Satya Nadella also pointed to the skills, saying you can use Copilot across Chat, Cowork, Autopilot, and even Code to complete more end-to-end workflows.

Tools versus skills​

The distinction is useful for anyone designing agents.

• Dynamics 365 apps hold the customer data and business logic.
• MCP tools give AI experiences a standard way to reach that context and approved actions.
• Skills add task guidance: what evidence to weigh, how to handle uncertainty, and what a good output looks like.

Microsoft's example: fetching an opportunity record is a tool action. Working out why a deal has stalled and structuring a recommendation is a skill. In plain terms, a tool is the filing cabinet key and a skill is the colleague who knows which folders to read first.

Skills named in the announcement​

Microsoft's examples are not a complete list.

Microsoft Learn's Sales page lists more packaged skills. Examples are Deal catch-up, Executive deal review, Forecast rollup, Meeting preparation, Post-meeting follow-up, Segment analysis, Team activity coaching and Team pipeline review. It also says the list will evolve and points users to the plugin page in Cowork for the current set.

The Customer Insights documentation names three skills: Customer brief and value metrics (read-only), Customer outreach, and Email content advisor.

How the three experiences differ​

• Cowork handles immediate work and finished deliverables. A seller might combine competitive strategy, business case composer and deal desk on one deal.
• Code is for reusable solutions. Microsoft's example is a service workspace built around case triage and case preparation brief.
• Autopilot is for recurring work such as reviewing deal changes. It remains in private preview, with limits on recurring automation and background notifications.

Microsoft is explicit that this does not imply automatic handoffs between experiences or identical functionality in each one.

Recommend, propose, execute​

The most useful part of the announcement is its insistence on separating four states: analysis, recommendation, proposed change and completed action.

• Reconcile my opportunity can find differences and propose field-level updates.
• Draft customer reply prepares a response for review.
• Stage advance readiness assesses evidence against your criteria. It does not change the stage.

For a pilot, Microsoft's framing amounts to a test you can run:

• Can the user tell what is being proposed?
• Does execution follow your authorization and review rules?
• Does the reported result match what actually happened?

A proposed update should never look like a saved one, and a draft should never look like a sent email. For Code and Autopilot, Microsoft says to confirm which actions are authorized, when review is required, and how failed or unconfirmed actions are reported.

Setup and prerequisites from Microsoft Learn​

The Learn pages describe Cowork specifically. Don't assume the same controls apply to Code, Autopilot or custom agents without product-specific documentation.

Sales

• The plugin uses the Dataverse MCP server, which must be enabled for the environment.
• Users need a Sales Enterprise or Sales Premium license plus an appropriate Copilot license.
• To enable it, open the Cowork tab, choose Customize, and turn on Sales. If you have no CRM license, the Sales for Cowork toggle gives access to CRM-agnostic skills that work with uploaded data.
• On first use, Cowork asks for a Dynamics 365 environment and remembers the choice.
• Cowork sees exactly the records you can see in Customer Insights, and the Sales page says it asks for confirmation before updating records, sending email or creating tasks.
• Cowork is billed on usage, with charges varying by token consumption, not as a fixed license amount.

Customer Service

• Users need Cowork access, applicable Customer Service licensing, and permission to the intended environment and records.
• Administrators must confirm the Service app is installed and assigned to the user or an effective Entra group, and that the Customer Service MCP configuration is in place.
• Installing the app does not enable Cowork or grant data access.
• Users turn on Service under Customize and confirm the environment in the plugin's Settings.
• A selection made in another Copilot experience might not apply to Cowork, so check the signed-in account and environment before touching records.
• Some tool calls may need approval, and checkpoints let representatives review proposed updates before they are committed.

Customer Insights

• You need an accessible Customer Insights environment, Dataverse MCP enabled, a Microsoft 365 Copilot license and the appropriate Customer Insights license.
• Under Customize, then Plugins, turn on the Dynamics 365 Customer Insights toggle. Then pick the environment from the plugin's settings.
• write operations are gated, with explicit confirmation before records are created or changed and a consent check before any outbound send.
• The consent check evaluates contact point, channel type, purpose, business unit and optional topic.
• publish-readiness validation covering the from address, company address, compliance profile, and unsubscribe surface.
• When a name matches several profiles, it presents the candidates and asks you to choose.

Suggested pilot checks​

These are my suggestions, built from the documented behavior.

• Environment drift. Verify the environment in Cowork separately from any other Copilot surface. If you run test, preproduction and production, make the intended target unambiguous.
• Licensing gaps. A user with a Copilot license but no Dynamics license gets, at most, the CRM-agnostic Sales skills. That is not access to your CRM records.
• Write-path honesty. Use a sandbox. Ask for a field update, decline it, then approve it. Confirm the response describes each outcome accurately.
• Consent edge cases. Test a segment containing opted-out contacts. The documentation says the plugin reports blocked contacts with reasons before any send is planned.
• Ambiguous identities. Use a common name and confirm the plugin asks which profile you mean.
• Cost. Usage-based billing means a long multi-step deal analysis costs more than a quick lookup. Budget accordingly.

Context and caveats​

Microsoft's documentation says that Every write waits for a person. That was said in the June Cowork-for-Dynamics post and is consistent with the October messaging. It's a sensible default, but it is also a default that someone must keep checking as workflows get more autonomous. Autopilot's recurring and background work is where review gaps are most likely to appear, and that is exactly the part still in private preview.

The announcement is a vendor blog post, so read the benefit language ("better customer experiences faster") as marketing. The documented controls are the verifiable part. Availability also depends on tenant, license, administrator configuration and consent. The sources don't establish that all 30 skills are available in every environment, region or language.

For IT teams, the practical upside is reuse. Instead of building sales, service and marketing prompts from scratch, you start from Microsoft's packaged skills, keep your existing Dynamics and Microsoft 365 permissions, and spend your effort on validation and governance. That is the real work, and no skill will do it for you.

Update: Microsoft’s CRM announcement also includes new agents and migration tools (October 9, 2026)​

The October 8 announcement goes beyond the 30 Copilot skills covered above. According to The Futurum Group, Microsoft also put Dynamics 365 CRM in Teams into public preview, bringing seller briefs, case alerts and account updates into Teams. For organizations testing the skills, this is a separate preview experience—not evidence that the skills automatically hand off work between Copilot surfaces.

Futurum also reports that Service Agent in Microsoft 365 is entering private preview for select Frontier customers. It can handle customer requests across Microsoft 365 apps and create CRM cases. Sales Development Agent, which researches prospects and manages outreach, is in public preview; Copilot-credit billing is scheduled to start November 16, 2026. These previews introduce more autonomous workflows than the review-and-confirm patterns emphasized in the Cowork documentation above, so admins should verify each feature’s availability, permissions and approval controls before evaluating it in a tenant.

The report also says Dynamics 365 Activate, an AI-assisted CRM migration tool, has been in public preview since September. For IT teams considering a CRM transition, that may offer a new way to assess migration paths, but it is not a guarantee of lower-risk or effortless migration. The added announcements broaden the practical scope of Microsoft’s October release: alongside packaged skills, it includes collaboration, agent and migration offerings with distinct preview and billing timelines.