A consultant enables Copilot in Dynamics 365 Sales for a team that wants to ask natural-language questions such as 'which of my opportunities are likely to slip this quarter.' The sales manager asks where Copilot pulls the facts behind its answers, since leadership does not want responses based on unindexed public web content. What should the consultant tell the manager?
Select an answer to reveal the explanation.
Short Explanation
Think of Copilot here less like a chatbot pulling from the whole internet and more like a very fast analyst who only has access to the CRM records you're already allowed to see. When it answers a question about opportunities slipping this quarter, it's reading real opportunity and activity data tied to that seller's account, not scanning the web for general information. That's exactly why the manager's concern makes sense to raise and exactly why the answer should be reassuring: the system is built to reason over the seller's own permitted records first. The traps here involve flipping that order, imagining an extra web-search plug-in has to be bolted on before any CRM answer works, or assuming the assistant is just freestyling from whatever it learned during training. None of those match how grounding actually works. The practical takeaway for someone configuring this for a team is that the trustworthiness of an answer traces back to whether the underlying records are accurate and access is scoped correctly, since that's the real source of truth Copilot is drawing from.
Full Explanation
The correct answer is B. Copilot in Dynamics 365 Sales grounds its natural-language answers in the records the requesting seller already has access to in Dataverse, including opportunities, activities, emails, and related entities, which is why it can answer pipeline questions accurately without depending on public web content. This grounding also respects existing security roles, so a seller only sees answers built from data they are already permitted to view. Option A is incorrect because Copilot does not query the open web as a first step for CRM-grounded questions like pipeline risk; that reverses how the feature retrieves facts. Option C is incorrect because no separate web-search connector is required for Copilot to reference a seller's own CRM data; grounding in Dataverse is native to the feature, not dependent on an external search integration. Option D is incorrect because Copilot does not rely solely on the underlying language model's pretrained knowledge; it retrieves and reasons over the seller's actual records, which is what allows it to reference specific opportunities and dates rather than generic language. Confirming this grounding behavior is important when a manager wants assurance that AI-generated pipeline answers reflect the organization's real, access-controlled data rather than external or fabricated content.