Question

A global manufacturer runs Dynamics 365 Sales in North America, Dynamics 365 Field Service in Europe, and Dynamics 365 Customer Service in Asia, each managed by separate regional teams with distinct data models. Leadership wants a unified agentic experience so sellers, technicians, and support reps can ask cross-region questions (for example, 'Are there open service cases affecting accounts in my sales pipeline?') without abandoning their existing apps. As the solutions architect, what is the most appropriate strategy to plan this multi-Dynamics 365 solution?

Accepted Answer

Use Copilot Studio to build purpose-built agents that connect to each Dynamics 365 app via its native connectors and Dataverse, and orchestrate them so agents can delegate cross-app queries while users stay in their own apps

Answer

Consolidate all three regions onto a single Dynamics 365 environment first, then build one monolithic custom agent on top of the merged database

Answer

Deploy a separate prebuilt agent independently in each region with no connection between them, and have users manually re-key data when cross-region answers are needed

Answer

Export all Dynamics 365 data nightly to a single external data lake and point one Microsoft 365 Copilot agent only at the exported files