An agent should reach customer data in an external CRM from Dynamics 365 Sales. What do you design?
Why D is the answer
A connector
A connector gives Copilot in Dynamics 365 Sales access to customer data held in an external CRM.
In detail
- A connector gives live, governed access to the external CRM.
- Check permissions on the external system.
Use case
An illustrative scenario, not a real incident.
A team keeps customers in another CRM. A connector lets Copilot in Dynamics 365 Sales reach that data.
See it in different ways
flowchart TD
A{"What must the agent reach?"} -->|"Tools with an open standard"| B["Model Context Protocol"]
A -->|"A service with a connector"| C["Connector"]
A -->|"An app with no API"| D["Computer use"]mindmap
root((Integration))
Has a connector
Connector
Open tool standard
Model Context Protocol
No API
Computer use
Azure AI services
Foundry ToolssequenceDiagram participant P0 as Copilot in Sales participant P1 as Connector participant P2 as External CRM P0->>P1: Request customer data P1->>P2: Query P2-->>P0: Result
Key point: Connectors reach external data.
Why the other options are wrong
- A. A Power BI semantic model
- A semantic model serves reports.
- B. A nightly CSV export that an admin uploads by hand
- A nightly export goes stale.
- C. An extra user role with no data access
- A role with no access reaches nothing.