What it does
Copilot is the AI assistance built into the Dynamics 365 apps — Sales, Customer Service, Field Service, Finance, Supply Chain, Business Central and the rest. Each app has its own Copilot surface tuned to that workload, plus a growing set of autonomous agents.
Key facts
- There isn't one "Dynamics 365 Copilot" product. It's a label over per-app assistants that ship and licence separately.
- Most in-app Copilot help is included with the app licence; the newer autonomous agents are metered and consume Copilot Studio message packs or capacity.
- Grounding is app-specific — Sales Copilot reads sales data, Service Copilot reads cases and knowledge. Don't assume one sees another's data.
- Availability and GA status vary by app and region. What's live in one geo may still be preview elsewhere.
When to use / skip
Use this doc to orient a client on the landscape before drilling into a single app. Skip it as an implementation reference — the real decisions live in the per-app pages.
Configuration decisions
- Which apps you turn Copilot on for, and in which environments.
- Whether the newer agents are in scope for phase one or deferred.
- Data governance and admin controls that span the apps.
Gotchas
- Clients hear "Copilot" and expect one consistent assistant. Set the expectation early that behaviour differs app to app.
- Release wave notes churn fast. Check the current wave, not last year's blog.
Consultant notes
- Scope per app, not per "Copilot". Licensing, GA state and admin toggles differ across the suite.
- Separate the free-with-licence assistants from the metered agents at costing time, or your capacity forecast will be wrong.
- Confirm regional and language availability before you promise anything in a workshop.
*Revisit each release w