Copilot Studio for Dynamics 365
Building AI agents on top of Dynamics 365 with Copilot Studio — topics, knowledge sources, generative answers, and Dataverse integration.
Microsoft Copilot Studio is the low-code platform for building AI agents — conversational and increasingly autonomous — that integrate deeply with Dynamics 365 and the rest of the Microsoft cloud. It is the successor to Power Virtual Agents, with a much heavier generative AI core. For Dynamics 365 customers, Copilot Studio is the standard way to deflect routine support, augment sales sellers, and front-end the data and processes the rest of the platform manages.
Agents. A Copilot Studio agent is configured with a role and instructions (its job and tone), one or more knowledge sources (Dataverse data, SharePoint sites, websites, documents), one or more actions (the operations it can perform via connectors), and trigger conditions (where it activates — Teams, the web, a Power Pages site, inside Dynamics 365). The agent uses an LLM (Azure OpenAI under the hood) to converse, reason, and decide what to do at each turn.
Topics and generative answers. Classic agent design used topics — structured conversation paths with named triggers and explicit dialog steps. Modern Copilot Studio combines topics with generative answers that synthesise responses from knowledge sources on the fly. Topics still handle critical, deterministic flows (e.g. "reset my password" with strict steps); generative answers handle the long tail of "how do I..." questions.
Knowledge. Connect Copilot Studio to:
- Dataverse tables — query Dynamics 365 data with natural language.
- SharePoint sites — index documents and pages.
- Public websites — index a public domain.
- File uploads — PDFs, Office documents, knowledge articles.
- External APIs — through Power Platform connectors.
The agent answers questions grounded in these sources, with citations linking back to the source for verification.
Actions. Beyond reading, agents act. Built-in actions can create cases in Customer Service, update opportunities in Sales, fetch records, post journal entries, send emails, kick off Power Automate flows. Each action is permissioned and respects the user's CRM security.
Channels. A single agent publishes to Microsoft Teams, the web (embed widget), Power Pages portals, Dynamics 365 Customer Service Omnichannel, WhatsApp, SMS, Facebook Messenger, and a handful of others. The same conversation logic runs everywhere.
Hand-off. Agents recognise when a question is beyond them and hand off to a human agent via Omnichannel for Customer Service, with the full conversation context.
Governance. Microsoft Purview integrates for content filtering, content tracking, and data loss prevention. Multi-environment ALM (dev → test → prod) is supported via solutions.
Operating reality. Start small. Pick one well-defined use case (FAQ deflection, an internal HR helper), measure deflection and customer satisfaction, and grow from there.
Related guides
- Building agents with Copilot StudioHow to design Copilot Studio agents — topics vs generative answers, knowledge grounding, actions, multi-turn dialogs, and operational patterns.
- Copilot agents vs Copilot StudioHow Microsoft's agent strategy splits — Copilot Studio for building custom agents, declarative agents in Microsoft 365 Copilot, autonomous agents — and how the pieces fit together.
- Microsoft 365 Copilot for Dynamics 365How Microsoft 365 Copilot reaches into Dynamics 365 — graph connectors, agents, and the licensing layers that determine what users actually get.
- AI Builder document automation, in depthHow AI Builder's document automation works — pre-built models, custom training, output structure, and the right way to integrate it with Dynamics 365.
- AI Builder explainedMicrosoft's no-code AI model library inside the Power Platform — pre-built models, custom training, and what AI Builder is good at.