9.3 Orchestrating Prebuilt Copilot AI Features in Dynamics 365 Customer Experience & Service
Key Takeaways
- Copilot features in Dynamics 365 Customer Service are enabled in the Power Platform admin center under Copilot then Settings then Copilot for the environment, and the administrator must hold the System Administrator role.
- The option to enable Copilot AI features is available in region by default for environments in the United States, Australia, India, United Kingdom and GCC or GCC High, data movement is enabled by default for Europe, and all other regions require cross-region data movement to be enabled first.
- Respond to questions, compose an email, and summarise cases and conversations are generally available in North America and in preview in other supported regions, and summarise conversations is available only in Copilot Service workspace.
- The Customer Support agent is configured in Copilot Service admin center across Overview, Immersive settings, Email settings, Prompts and Extend agent tabs, where Extend agent is the bridge into Copilot Studio that converts a prebuilt capability into a customer-owned extension.
- Custom security roles need privileges on msdyn_copilotevent, msdyn_copilotinteraction, msdyn_copilotinteractiondata and msdyn_copilotagentpreference plus the miscellaneous privilege prvIntelligenceUsage, with representative read and write at Basic and create at Global.
Orchestrating Prebuilt Copilot AI Features in Dynamics 365 Customer Experience & Service
Quick Answer: Orchestrating the shipped Copilot features in Dynamics 365 customer experience and service applications is an administrative enablement sequence, not a development task, and the AB-100 blueprint tests whether an architect can order it correctly. The chain is: Power Platform admin center (enable AI-powered Copilot features for the environment, and enable cross-region data movement if required) → Copilot Service admin center (opt in to terms, configure Copilot settings, choose Copilot immersive and Copilot side pane, configure the Customer Support agent across Overview, Immersive settings, Email settings, Prompts, and Extend agent tabs) → agent experience profiles (decide which representatives see which capabilities) → security roles (grant the Copilot Dataverse table privileges and
prvIntelligenceUsage). Region matters: the option to enable Copilot AI features is available in region by default for environments in the United States, Australia, India, United Kingdom, and GCC/GCC High; for Europe, data movement for Copilot features is enabled by default; for all other regions the administrator must enable cross-region data movement in the Power Platform admin center first. Respond to questions, compose an email, and summarise cases and conversations are generally available in North America and in preview elsewhere.
There is a persistent misconception among architects that "turning on Copilot in Customer Service" is a single toggle. It is not. It is a five-layer enablement path, and a failure at any layer produces the same user-visible symptom — representatives cannot see the feature — with entirely different root causes. Diagnosing that symptom quickly is exactly what an expert-level scenario question is designed to test.
This section covers orchestration of the prebuilt Copilot capability in customer experience and service apps. It is distinct from designing business terms and Copilot customisations (Chapter 5), and distinct from orchestrating Microsoft 365 Copilot for Sales and for Service (Section 9.2), which are separately licensed Microsoft 365 experiences.
1. How the Features Are Delivered
Copilot features in Dynamics 365 Customer Service are powered by Microsoft 365 Copilot and surfaced in Customer Service applications such as Copilot Service workspace. They operate over customer service data — cases, customer records, interactions — so that representatives can retrieve information, generate responses, and complete actions without leaving their workflow.
Some capabilities are delivered through Copilot agents, such as the Service Agent, which extend Copilot with customer-service-specific functionality for summarising cases, retrieving knowledge, and performing actions. This is an important architectural nuance: not every Copilot capability is a monolithic platform feature; several are agents with their own configuration surface.
One constraint to memorise: summarise conversations is available only in Copilot Service workspace. For representatives working in Customer Service Hub or a custom app, the additional enablement steps for custom apps must be performed, and conversation summarisation still will not appear.
2. The Enablement Sequence
Layer 1 — Power Platform admin center: environment enablement
- In the Power Platform admin center site map, select Copilot.
- Select Settings > Copilot under Dynamics 365 Customer Service.
- Search for and select the environment, then select Edit setting.
- Select Enable AI-powered Copilot features and save.
The administrator performing this must hold the System Administrator role.
Layer 2 — Region availability and cross-region data movement
Copilot performance depends on the regional availability of the underlying Azure OpenAI capacity. Microsoft states the dependency precisely:
| Scenario | Requires enabling data movement |
|---|---|
| Azure OpenAI capacity is available in the same region as your tenant | No |
| Azure OpenAI capacity is available outside of your tenant | Yes |
| Capacity exists in your tenant region but falls back to external regions | Optional — but without it, expect throttling or unavailability from capacity constraints |
Data movement across regions is enabled by default in the Power Platform admin center. For a sovereignty-constrained customer, the architect's job is the inverse of the usual one: to determine whether disabling it is compatible with the Copilot features the business wants, because disabling it in a region without local capacity removes the features entirely. This is a genuine architectural trade-off between data-residency posture and feature availability, and it must be decided in design, not discovered in UAT.
Layer 3 — Copilot Service admin center: opt in and configure
On the Copilot settings or Summaries page the administrator reviews the terms and selects Opt in. If the environment is in a region where features are not available by default, the page surfaces an error, a link to the Power Platform admin center to allow data movement, and the current data-movement status.
Then, under Support experience > Productivity > Copilot settings > Manage, the administrator turns on the experiences representatives may use:
- Copilot immersive
- Copilot side pane
Under Agents within Copilot, selecting Settings next to Customer Support opens the agent's configuration across five tabs: Overview, Immersive settings, Email settings, Prompts, and Extend agent. The Extend agent tab is the bridge to Copilot Studio — it is where a shipped agent stops being purely prebuilt and starts carrying customer-owned tools and knowledge, which has ALM and governance consequences.
An optional Admin Management agent (preview) gives administrators a centralised way to manage administrative prompts, control user access, and connect tools and knowledge through Copilot Studio, configured across Overview, Prompts, and User access tabs.
Two further switches live on the Copilot settings page:
- Translation using Copilot — lets representatives translate responses into languages configured in Dynamics 365.
- Record transcripts of representative interactions with Copilot — under Support experience data. Transcripts can be downloaded and analysed to evaluate knowledge sources and build usage reports. This is the primary telemetry input for the continuous-improvement loop, and it is off until an administrator turns it on.
Opting out erases the training data. Re-enabling requires consenting to the terms and opting in again. An architect should never treat opt-out as a reversible toggle during a pilot.
Layer 4 — Agent experience profiles: who sees what
Representatives can only use Copilot features in Copilot Service workspace if those features are enabled in their experience profile. By default, representatives on the out-of-the-box profiles can use Copilot features. To restrict the feature set, the architect creates a custom experience profile, enables only the required features, and assigns that profile to the relevant representatives. In Customer Service Hub, by contrast, enabling a feature makes it available to all representatives — there is no profile-level granularity, which is a meaningful design constraint when a phased rollout is required.
Layer 5 — Security roles and privileges
Out of the box only the Customer Service Representative role can use Copilot features. Custom roles need privileges on the Copilot Dataverse tables, including msdyn_copilotevent, msdyn_copilotinteraction, msdyn_copilotinteractiondata, msdyn_copilotagentpreference, and read access to msdyn_aimodel, msdyn_aitemplate, and msdyn_conversationinsight. Critically, users also need the miscellaneous privilege prvIntelligenceUsage to access Copilot at all.
Access levels matter: for representative roles, read and write on msdyn_copilotevent are set to Basic while create is set to Global; for custom CSR Manager roles, all three are set to Global. A role that grants read but not create on msdyn_copilotevent produces a confusing partial failure rather than a clean access-denied.
3. Data Sharing — A Distinct, Optional Decision
Separately from data movement, administrators may turn on data sharing for Dynamics 365 Copilot features in the Power Platform admin center. This allows Microsoft to capture and manually review customer data — including natural-language inputs, outputs, and related telemetry — to build, improve, and validate Microsoft's features, services, and machine-learning models. Microsoft states that customer data is not used to train Azure OpenAI Service foundation models.
Architects routinely conflate three different switches. They are not the same and must be decided independently:
| Switch | What it controls | Default |
|---|---|---|
| Enable AI-powered Copilot features | Whether Copilot works in the environment at all | Off until enabled |
| Cross-region data movement | Whether inference may use capacity outside the tenant region | On in PPAC |
| Optional data sharing | Whether Microsoft may review customer data to improve services | Opt-in |
4. Troubleshooting Ladder
When a representative reports that a Copilot capability is missing, work the layers in order — each layer produces the same symptom:
- Is Enable AI-powered Copilot features set for the environment in the Power Platform admin center?
- Is the environment in a region needing cross-region data movement, and is it allowed?
- Has an administrator opted in on the Copilot settings or Summaries page?
- Is the specific experience (immersive or side pane) turned on, and is the capability configured on the Customer Support agent tabs?
- Is the capability enabled on the representative's experience profile?
- Does the representative's security role carry the Copilot table privileges and
prvIntelligenceUsage? - Is the representative in Copilot Service workspace (required for conversation summarisation) or in Customer Service Hub / a custom app?
AB-100 Exam Tip: Scenarios in this area almost always present a partially working deployment — "summarisation works for some representatives but not others", or "Copilot appears in one environment but not the identical one in Frankfurt". Differences between users point to experience profiles or security roles. Differences between environments point to the environment-level enablement or the regional data-movement setting. Differences between apps point to Copilot Service workspace versus Customer Service Hub. Answers that propose custom development to solve an enablement problem are distractors.
A global insurer runs two identically configured Dynamics 365 Customer Service environments, one in the United States and one in Brazil. Representatives in the United States environment use case summarisation successfully. Representatives in the Brazilian environment see no Copilot features at all, and the Copilot settings page displays an error with a link to the Power Platform admin center. What is the most likely cause?
A service director wants a phased Copilot rollout in which only 40 of 300 representatives can use email composition during a four-week pilot, while all representatives retain access to case summarisation. Which mechanism delivers that separation, and what constraint must the architect flag?
A compliance team asks the architect to confirm that enabling Copilot in Dynamics 365 Customer Service does not permit Microsoft personnel to review the organisation customer data. Which statement most accurately describes the relevant controls?