Copilot across Dynamics 365

Microsoft has been shipping Copilot features into every Dynamics 365 app over the past two years, and the shape of what "Copilot" means differs materially between apps. This guide walks each surface, what it actually does, how it's licensed, and where the natural boundaries are between the app-specific Copilots and the wider Microsoft 365 Copilot.

The short version: every Dynamics 365 app has a Copilot inside it, tuned for that app's workflow. Two of them — Copilot for Sales and Copilot for Service — also ship as standalone products that connect to Salesforce, so an org that runs Salesforce today can adopt the Copilot experience without moving off it.

The taxonomy

There are three families of Copilot in Dynamics 365, and getting them straight prevents most licensing and rollout confusion.

App-embedded Copilot. Copilot features inside a specific Dynamics 365 app — draft an email in Sales, summarise a case in Customer Service, translate a bank statement in Business Central. These are included in the app's Enterprise / Premium licence and appear as buttons and panels inside the app itself.

Copilot for Sales / Copilot for Service. Two standalone Copilot products that sit inside Outlook, Teams, and the Sales / Service app. They bring CRM context into the Microsoft 365 productivity apps — a seller reading an email in Outlook sees the CRM view of the person they're emailing without opening Dynamics 365. Licensed separately from the underlying app, and connectable to Salesforce as an alternative to Dynamics 365.

Microsoft 365 Copilot with Dynamics 365 plugins. The general-purpose Microsoft 365 Copilot chat (the one in Teams, the Copilot app, and the web) can be extended with Dynamics 365 plugins that let it read pipeline, cases, or projects when asked. Licensed as part of Microsoft 365 Copilot.

The three families overlap in places and complement in others. An organisation running the full stack typically has all three.

Sales

App-embedded Copilot in Sales drafts email replies, summarises long email threads, prepares meeting briefings, extracts notes back to CRM after a call, and answers natural-language questions across the pipeline. All inside the Sales app.

Copilot for Sales does the same job from inside Outlook and Teams — a seller reading an email in Outlook sees the CRM record without switching apps, and can update opportunity fields or log a call from Outlook directly. This is the Copilot that most changes seller behaviour in day-to-day work; sellers live in Outlook, and CRM adoption improves when the CRM lives where the seller already is.

Licensed as Sales Premium (bundles Copilot for Sales) or as a Copilot for Sales add-on to Sales Enterprise. Standalone-connected-to-Salesforce is a separately licensed product with its own pricing.

Customer Service

App-embedded Copilot in Customer Service handles case summary (the case's history condensed for an agent picking it up mid-flight), email draft replies, conversation summary at end of chat that writes back to the case timeline, knowledge search in natural language, and agent-assist suggestions during a live conversation.

Copilot for Service brings CRM context into Outlook and Teams for service agents — the same "no switching apps" pattern as Copilot for Sales, but for service scenarios. It also plugs into Salesforce Service Cloud, ServiceNow, and Zendesk for organisations that don't run Customer Service but want the Copilot experience.

Supervisor Copilot rolls up sentiment monitoring across live conversations, conversation intelligence across calls and chats with keyword tracking, and Copilot-generated summaries of team performance.

Licensing follows the Sales pattern: Customer Service Enterprise + Copilot for Service add-on, or standalone Copilot for Service.

Field Service

Copilot in Field Service summarises the work order for a technician on arrival, drafts the completion notes from the technician's spoken summary, and finds relevant knowledge articles inside the mobile app. It also helps dispatchers by pre-populating schedule suggestions and flagging at-risk bookings.

The technician-side Copilot is the most impactful — technicians spend limited time in front of a keyboard, and a Copilot that turns a two-minute voice summary into a complete work order write-up saves real time per job.

Licensed as part of Field Service Enterprise or as an add-on.

Business Central

Business Central was one of the first Dynamics 365 apps to ship serious Copilot features and it has kept extending them. Highlights:

• Bank reconciliation Copilot matches statement lines to ledger entries and flags exceptions.
• Sales line suggestions propose line items for a sales order based on the customer's history and current basket.
• Marketing text generation drafts product descriptions from item attributes.
• Chart explanations turn a BI chart into a written analysis paragraph.

These are targeted features, not a general chat surface — they sit inside the pages where the work happens. Business Central's Copilot approach is deliberately conservative and productivity-focused, which suits the SMB customer base.

Included in Business Central Essentials and Premium; no separate Copilot licence.

Finance and Supply Chain (F&O)

F&O Copilot is broader in scope than the CRM-side app Copilots because the workflow surface is bigger. Notable features:

• Bank reconciliation and vendor invoice capture (AP automation) both use Copilot for matching and exception handling.
• Demand planning Copilot proposes forecast overrides and explains the underlying signals.
• Warehouse optimisation Copilot flags picking-path improvements and layout inefficiencies from the movement data.
• Financial insights turns the general ledger data into narrative analysis for month-end review.

The F&O Copilot roadmap is heavy — Microsoft ships new features every Wave — and the depth of each Copilot varies. Some are polished; some are early-stage. Track the release plans rather than assuming a feature you saw at a Microsoft event is generally available.

Included in F&O licensing; no separate Copilot licence for the app-embedded features.

Project Operations

Copilot in Project Operations speeds up time entry (draft a week's timesheet from Teams meetings and calendar), assists with project quote configuration, and summarises project health for the weekly delivery review. Less mature than the Sales / Service Copilots but useful, particularly for reducing the friction on consultant time entry — one of the persistent adoption problems in PSA deployments.

Included in Project Operations licensing.

Microsoft 365 Copilot with Dynamics 365 plugins

The general-purpose Microsoft 365 Copilot chat can query Dynamics 365 through published plugins. "Show me the top ten deals slipping this quarter" answered by Copilot chat in Teams. "What's my pipeline of open cases from customers above X in revenue" answered in the Copilot app.

This is the newest surface and it's genuinely useful for executives and functional leaders who don't live in the Dynamics 365 apps themselves. Licensed as part of Microsoft 365 Copilot ($30/user/month at 2026 pricing); requires the underlying Dynamics 365 app licence for the data being queried.

Copilot Studio agents

Copilot Studio (the low-code agent builder) is the extensibility layer for all of the above. A custom agent can be built once and surfaced in Teams, Microsoft 365 Copilot, or the Dynamics 365 apps. Common patterns:

• A customer-service self-service agent deflects routine cases before they hit human agents.
• A sales assistant agent in Teams answers seller questions about a specific account by querying Dynamics 365, LinkedIn Sales Navigator, and internal SharePoint.
• A project-status agent in Copilot chat rolls up project margin, resource load, and next milestones from Project Operations.

Copilot Studio is licensed per message pack or per user, depending on the deployment model. It is the right tool when a shipped Copilot doesn't cover a specific workflow and building a custom agent is cheaper than waiting for Microsoft to ship it.

What matters at rollout

Two decisions dominate a Dynamics 365 Copilot rollout.

Which Copilots go first. The natural sequence is: app-embedded Copilots (they're already licensed if the app is), then Copilot for Sales / Copilot for Service (biggest behaviour change but real license cost), then Microsoft 365 Copilot with Dynamics plugins (broadest reach but again real cost), then Copilot Studio custom agents (highest customisation, highest project cost).

Data readiness. Every Copilot's quality depends on the data it can read. A Sales Copilot answering pipeline questions against a CRM full of stale opportunities gives bad answers. Cleaning Dataverse master data — closed opportunities marked closed, stale accounts archived, ownership current — is the unglamorous prerequisite that decides whether Copilot delivers value. Rush the licence rollout past this step and Copilot's reputation in the org takes the hit for CRM hygiene problems.

The short version

Every Dynamics 365 app has a Copilot; the pattern is app-embedded (bundled with the app), Copilot for Sales / Service (separately licensed, cross-CRM), and Microsoft 365 Copilot with plugins (broadest). Copilot Studio is the extensibility layer. Data readiness decides whether any of it works well.