Microsoft 365 Copilot for Dynamics 365

How Microsoft 365 Copilot reaches into Dynamics 365 — graph connectors, agents, and the licensing layers that determine what users actually get.

Updated 2026-04-20

Microsoft 365 Copilot is the AI experience embedded across Microsoft 365 — in Word, Excel, PowerPoint, Outlook, Teams, OneNote, and the standalone Copilot app. It is different from the embedded copilots in Dynamics 365 (Copilot for Sales, Copilot in Business Central, F&O copilots), but the two stacks increasingly overlap. Understanding how M365 Copilot sees Dynamics 365 data — and what it can do with it — is increasingly central to the platform story.

The architecture. M365 Copilot uses semantic indexing of a user's Microsoft 365 data (emails, files, calendar, Teams chats) combined with Microsoft Graph as the data plane, then layers Azure OpenAI for reasoning and generation. To bring data outside M365 into Copilot's awareness, two mechanisms exist:

  1. Graph connectors. Index content from external systems into Microsoft Graph so Copilot can retrieve and cite it. Microsoft ships Graph connectors for Dynamics 365 — items, accounts, opportunities, and other key tables can be indexed.

  2. Agents (Copilot Studio). Custom Copilot Studio agents can act as M365 Copilot plugins, extending its behaviour to query Dynamics 365 live and execute actions. The agent appears in the Copilot pane and Copilot calls it when relevant.

What users actually get.

  • In Outlook. Drafting an email to a customer, Copilot can reference recent open opportunities, recent cases, or recent invoices from Dynamics 365 (if the right plugins are installed).
  • In Word. Drafting a proposal, Copilot can pull customer history, past quotes, and pricing from CRM via plugins.
  • In Excel. Summarising data exported from Dynamics 365, building forecasting models on top.
  • In Teams. During a meeting with a customer, Copilot summary references CRM data and creates follow-up actions back to Dynamics 365.

The licensing layers. Microsoft 365 Copilot is a separate paid add-on (per user per month, M365 E3/E5 or Business Standard/Premium required as base). It is distinct from Copilot for Sales, which is a different per-user add-on. The embedded copilots inside Dynamics 365 (BC, F&O, customer service AI assist) are included with the relevant D365 SKUs.

  • Microsoft 365 Copilot Chat (formerly Copilot Free) — free standalone consumer-style chat, no business data grounding.
  • Microsoft 365 Copilot — full enterprise; grounded in M365 data; supports plugins; data residency and DLP.
  • Copilot for Sales — separate licence; sales-specific; lives inside Outlook/Teams/CRM.
  • Copilot in [D365 product] — bundled with each D365 SKU; specific to that product.

Configuration. A Microsoft 365 admin enables Copilot per user, installs the Dynamics 365 plugins from the Microsoft 365 plugin catalogue, and configures data sharing and DLP. Copilot Studio agents that target M365 Copilot are published with the right manifest to appear in the M365 Copilot experience.

The future. Microsoft is converging the copilot stack. The eventual end state is one Copilot experience that knows the user's M365 data and their Dynamics 365 data and reasons across both. The transition is incremental; expect the licensing landscape to evolve.

Practical advice. Start with one well-defined use case (e.g. Outlook + Dynamics Sales). Measure adoption. Expand based on actual value, not vendor enthusiasm.

Related guides