Dynamics 365 Ships 30 CRM Skills for Copilot Cowork

Thirty Dynamics 365 CRM skills are now generally available in Copilot Cowork. That does not mean Microsoft’s broader collection of CRM agents and autonomous workflows is ready for unrestricted deployment.

Microsoft’s October 8, 2026 sales and service announcement draws several important boundaries: CRM in Teams and Sales Development Agent are public previews, Autopilot support is in private preview, and the expanded autonomous Service Agent experience is limited to selected Frontier customers.

The distinction matters for organizations evaluating these AI products. Microsoft is making existing Dynamics 365 capabilities reusable across Copilot experiences, but customers need to separate capabilities they can deploy today from workflows they can only evaluate through preview programs.

What Customers Can Use Now

The release covers Dynamics 365 Sales, Customer Service and Customer Insights. Availability depends on which experience customers want to use, not simply whether a CRM skill exists.

This is not one release with a single access status. General availability applies to the skills in Cowork, while other interfaces and agent capabilities have separate restrictions.

Microsoft also cautions that the examples do not imply identical functionality across experiences or automatic handoffs between them. A workflow demonstrated in Cowork should not be assumed to run unchanged in Code or Autopilot.

Even the generally available features remain subject to licensing, administrator configuration, user or tenant consent, and organizational policies. “Generally available” describes release status, not automatic entitlement for every Microsoft 365 or Dynamics 365 customer.

Skills Add Task Guidance to More Than 180 CRM Tools

The technical change is more specific than giving Copilot another way to search customer records.

According to Microsoft’s Dynamics 365 technical announcement, the skills work with more than 180 generally available tools across the three Dynamics 365 applications. Microsoft describes three layers:

• Dynamics 365 applications provide customer data and business logic.
• Model Context Protocol (MCP) tools expose customer context and approved business actions to AI experiences.
• Skills supply reusable, task-specific guidance for using those tools.

That last layer carries the workflow expertise. Retrieving an opportunity record is a tool operation. Investigating why an opportunity has stalled requires guidance about which evidence to examine, how to handle incomplete information, and how to structure a useful recommendation.

Microsoft says skills provide that guidance, allowing organizations to reuse CRM procedures rather than redesigning them for each AI interface or custom agent.

The practical consequence is that Dynamics 365 remains the underlying system for customer data and business processes while users interact through Copilot. The interface changes; the CRM foundation does not disappear.

This also explains why the tool count and skill count are different. A skill can use multiple tools to complete a task, and the same tools can support different skills. Neither count, by itself, establishes how reliably a workflow performs.

Cowork Supports CRM Analysis and Proposed Actions

The generally available release includes skills for sellers, service representatives and marketers. Microsoft’s examples emphasize preparation, investigation and proposed next steps, alongside business actions that remain subject to authorization.

For sales teams, Pipeline prioritizer identifies opportunities needing attention, Deal rescue investigates stalled or at-risk opportunities, and Customer engagement strategy recommends a 30-day account plan. Other examples include preparing competitive strategies, investment cases, and product or pricing configurations.

For service teams, Case triage surfaces urgent issues, Answer research looks for relevant guidance from verified knowledge and similar cases, and Draft customer reply prepares a response grounded in customer information.

Marketing examples include consent-aware outreach, brand-compliant content, and customer journeys with consent and readiness checks.

These descriptions should not be read as blanket permission for AI to change records or contact customers. Microsoft explicitly distinguishes analysis, recommendations, proposed changes and completed actions.

For example, Reconcile my opportunity can identify differences between customer interactions and a CRM opportunity record, then propose field-level updates. Stage advance readiness assesses evidence against an organization’s criteria; that assessment is not itself a stage change. A drafted customer reply is likewise not a sent message.

For deployment teams, these distinctions matter more than the headline skill count. Users need to see whether Copilot has suggested an update, obtained approval, or actually saved it.

CRM in Teams Brings Account Context Into Channels

The public-preview Dynamics 365 CRM-in-Teams experience takes a different approach: bringing shared customer context into collaboration rather than asking each employee to retrieve it separately.

Microsoft says organizations can connect a Teams channel to a customer account. Agents can then provide updates such as pre-meeting briefs, case notifications and account developments within that channel.

The intended benefit is a shared view spanning sales and service. An account team discussing a customer could see relevant support developments alongside sales context, without treating each department’s CRM activity as a separate conversation.

That is distinct from the generally available Cowork skills. The Teams feature is a public preview with its own setup and access requirements. The announcement also does not establish that every CRM action available elsewhere becomes available inside a connected channel.

Customers evaluating it should therefore check the account connection, permissions and supported actions, rather than treating “CRM in Teams” as full replacement access to Dynamics 365.

Service Agent’s Autonomous Expansion Is Restricted

The more autonomous Service Agent is the least broadly available part of the announcement.

Microsoft says it is extending the early Service Agent experience in Microsoft 365 to a selected group of Frontier customers through a private preview. That restriction applies to the expanded autonomous capabilities described in this update.

The company positions the agent for customer-facing employees beyond traditional support teams, including account managers, customer success staff and subject matter experts. It describes assistance within Outlook, Teams, Word, Excel and PowerPoint.

In Microsoft’s example, a customer emails an account manager about an unresolved billing issue. Service Agent retrieves relevant organizational knowledge and drafts a response for review and approval. If formal tracking is necessary, Microsoft says the agent can automatically create a CRM case and share its link.

The company also describes resolving issues outside business hours where possible and escalating to specialists when needed, with managers retaining visibility into actions and outcomes.

These are vendor-described workflows, not independently demonstrated results in the supplied announcements. They also combine different levels of autonomy: drafting for approval, creating a case, and resolving an issue are separate actions with different consequences.

The private preview is therefore not evidence that every Dynamics 365 customer can now delegate end-to-end customer support to Service Agent.

Sales Development Agent Has a Public Preview and Billing Date

Sales Development Agent has broader preview access than the Service Agent expansion.

Microsoft says the agent researches prospects, personalizes outreach, manages follow-up conversations and advances qualified opportunities before handing them to sellers. It is managed in Teams, sends email through its own Exchange account, and connects to leading CRM platforms.

The operational distinction is important. This agent is described as conducting outreach and nurturing prospects, rather than merely drafting material for a seller to use.

Microsoft’s announcement does not identify every supported CRM platform or provide independently measured qualification accuracy. Its claims about expanding selling capacity should be treated as the intended business outcome, not a guaranteed result.

The company gives one concrete cost-related milestone: Copilot-credit consumption begins on November 16, 2026. Customers should include that date in preview planning, but it is not a complete pricing model. The announcement does not supply a per-task credit estimate or a deployment cost calculation.

Deployment Depends on Authorization, Not Just Access

For the skills, Microsoft describes enabling the relevant Sales, Customer Service or Customer Insights plugins through the desired Copilot experience’s customization area, connecting accounts, and selecting a Dynamics 365 environment when prompted.

The plugins respect applicable Dynamics 365 and Microsoft 365 permissions, according to Microsoft. That provides an access foundation, but organizations still need to validate how workflows behave.

A useful acceptance test is whether the experience clearly reports what happened: a proposed update must not appear as a saved record, a draft must not appear as a sent email, and an unsuccessful action must not appear complete. Microsoft explicitly calls out these distinctions.

That is the consequential part of this product update. Reusable skills and MCP-backed tools can reduce the need to rebuild CRM workflows for each interface, but reuse also makes clear action boundaries essential. Before expanding from Cowork assistance into preview automation, customers should establish which actions require review and how they will confirm execution.