Microsoft has made 30 prebuilt CRM skills generally available in Copilot Cowork, covering Dynamics 365 Sales, Customer Service, and Customer Insights. Deva Rajamohan, corporate vice president of Dynamics 365 Customer Experience. Autopilot support is in private preview, and Copilot Code access runs through Microsoft’s Frontier program.
The key design choice is the split between tools and skills. Model Context Protocol (MCP) tools let AI agents reach CRM records and approved actions. Skills add the method for a task, such as what evidence to consider and what a finished output should include. Microsoft says pulling up an opportunity record is a tool action, while working out why a deal has stalled calls for a skill.
Jeff Teper, executive vice president of Microsoft Apps and Agents, calls the approach agentic, headless CRM in a companion post: customer data and processes stay in Dynamics 365 while the work moves into Copilot and Teams. The release follows Microsoft’s Sept. 23 ERP update, which made the ERP plugin for Copilot Cowork and the ERP MCP server generally available and put prebuilt ERP skills, including procure-to-pay, on the roadmap. The CRM set shows how Microsoft structures prebuilt skills before the ERP versions ship.
How the Skills Work
Dynamics 365 applications supply the customer data and business logic, MCP tools expose that context and approved actions, and skills tell agents how to use the tools for a specific job.
Skills chain into workflows. A seller can flag opportunities that need attention with pipeline prioritizer, investigate a stalled deal with deal rescue, and get a 30-day account plan from customer engagement strategy. Service skills triage cases, research answers from verified knowledge, and draft customer replies, while marketing skills cover consent-aware outreach and brand-compliant content.
Cowork handles immediate tasks, Code builds reusable solutions, and Autopilot runs recurring work within private-preview limits. Organizations can also use the skills in custom agents.
Organizations enable the skills from the Copilot customization area, connect the relevant accounts, and select a Dynamics 365 environment. Existing Dynamics 365 and Microsoft 365 permissions apply, along with licensing, consent, and organizational policy. Neither post lists separate pricing for the skills.
Where Microsoft Draws the Line on Agent Actions
Microsoft’s skill definitions separate analysis, recommendations, proposed changes, and completed actions. The reconcile my opportunity skill proposes field-level updates, draft customer reply prepares a response for review, and stage advance readiness assesses a deal without moving it to the next stage.
Microsoft turns that into a validation test for IT: a proposed update should not appear as a saved change, a draft should not appear as a sent message, and reported results should match what happened. IT teams using Code or Autopilot should also confirm which actions are authorized, when review applies, and how failed or unconfirmed actions are reported.
Teper’s post also updates two agents governed through Agent 365. Service Agent in Microsoft 365, in private preview for select Frontier customers, drafts replies for approval and opens CRM cases when an issue needs tracking. Sales Development Agent, in public preview, researches prospects, sends outreach from its own Exchange account, and starts consuming Copilot credits on Nov. 16.
The same questions apply to ERP. Microsoft lists agent-specific ERP restrictions, which would separate what employees can do from what agents can do for them, as a coming capability. Until then, teams using the generally available ERP connectors set agent boundaries through their existing security roles.
What This Means for ERP Insiders
Study the CRM skills as a model for ERP skills. Prebuilt ERP skills such as procure-to-pay are still on the roadmap. Reviewing how the CRM skills define evidence, outputs, and review points gives ERP teams a template for finance and supply chain skills.
Test the gap between proposed and completed actions. Running Microsoft’s validation test in CRM pilots, and later on postings and payments, gives auditors a clear record of what agents recommended, what people approved, and what changed.
Map where customer-facing agents touch ERP data. Microsoft’s Service Agent example involves a billing issue, and billing questions usually depend on ERP records. Identifying those dependencies now lets ERP teams set access rules before the agents leave preview.
