A sales rep asks Copilot for Sales to summarize a strategic account before a renewal call. The summary omits several recent, highly relevant notes that the rep knows exist, because those notes were entered by a colleague on a different business unit's team. A consultant investigating the gap confirms the notes exist in Dataverse and are not deleted or archived. What explains the missing content in the summary?
Select an answer to reveal the explanation.
Short Explanation
It helps to remember that this assistant is not an independent researcher pulling from everywhere, it is more like a very fast colleague who is only allowed to read what you personally have access to. If another team's notes were never shared with the rep or their business unit, then the rep would not see them by scrolling through the account either, and the summary respects that same boundary rather than sneaking around it. That is actually the point of building the assistant on top of the existing security model, since it keeps sensitive notes from leaking across teams just because someone asked a chatbot instead of opening a record. The trap here is assuming something broke, whether a stale cache or a sync bug that will resolve itself, when really the system is doing exactly what the access rules told it to do. If the missing visibility is unwanted, the real lever is adjusting who can see those notes, not troubleshooting the summary feature itself.
Full Explanation
The correct answer is C. Copilot for Sales operates within the Dataverse security model, meaning any record it surfaces in a summary must already be visible to the signed-in user through their assigned security roles and the record's sharing or business-unit access rules. If the notes were entered by a colleague on a different business unit and were never shared with the rep's team, Dataverse itself would hide those records from the rep in a normal list view, and Copilot inherits that same restriction rather than bypassing it. The fix is to review and adjust the security roles or sharing rules if broader visibility is actually intended, not to treat this as a defect. Option A is incorrect because Copilot does not maintain a separate caching layer that lags behind Dataverse; it queries governed data directly, so a stale cache is not the mechanism at play. Option B is incorrect because it misdescribes the architecture entirely, Copilot's grounding is built on top of Dataverse's governed data and security model rather than an separate, unsecured store. Option D is incorrect because there is no caching defect here, and framing it as one would lead the consultant to wait for a fix that will never materialize since the exclusion is permissions working as designed.