A distributor wants Copilot for Sales to include real-time product availability from its external ERP system inside AI-generated quote-preparation summaries. The ERP data is not replicated into Dataverse, and the built-in Copilot for Sales summary only draws on Dataverse records plus connected email and calendar content. A consultant is asked how to get the ERP availability data into the AI-generated summary without duplicating the ERP inventory tables into Dataverse. What should the consultant recommend?
Select an answer to reveal the explanation.
Short Explanation
Out of the box, the assistant only knows what lives inside the CRM plus whatever emails and calendar items are connected to it. If the numbers you need live in a separate system, like an ERP tracking real inventory, the assistant has no way to see them unless someone builds it a bridge. That bridge is a custom plugin you configure through the Copilot Studio tooling, which lets the assistant reach out to that outside system and pull back a live answer instead of a stale copy. Waiting around for some future update is unnecessary, since that bridge-building capability already exists. Stuffing an exported spreadsheet onto the record does not work either, because the assistant is not scanning attachments for numbers. And recording phone calls will not magically teach the assistant what is sitting in the warehouse, since transcription only captures what people say, not what is stored in another system's database.
Full Explanation
The correct answer is D. Copilot for Sales can be extended through Copilot Studio, where a consultant builds a custom plugin, sometimes called a skill, that calls out to an external system such as an ERP and returns live results into the Copilot conversation. This lets the quote-preparation summary include real-time inventory availability from the ERP without ever copying the ERP's inventory tables into Dataverse, satisfying the requirement to avoid data duplication. Option A is incorrect because Copilot for Sales is designed to be extended beyond its default Dataverse, email, and calendar grounding through Copilot Studio; there is no need to wait for a future release to reach an external system. Option B is incorrect because Copilot does not treat file attachments on a record as a queryable data source for its generated summaries, so an exported CSV would not appear in the AI-generated text and would quickly go stale besides. Option C is incorrect because conversation intelligence transcribes spoken calls and extracts things like sentiment and mentioned competitors; it has no mechanism for capturing numeric inventory figures a seller happens to read aloud, and it does nothing to connect the ERP system to Copilot's summaries.