A sales manager asks a consultant why a rep's natural-language question to Copilot, 'show me all opportunities in the Northwest territory,' returns only eight of the twenty open opportunities the manager can see in that territory. The consultant checks the rep's Dynamics 365 security role and finds it grants read access only to opportunities the rep owns or is on the sales team for. What should the consultant tell the manager?

The correct answer is that Copilot answers natural-language questions using the same Dataverse security roles and record-level access as the rep, so it will not surface opportunities the rep cannot already open. Copilot is grounded in the data the requesting user is authorized to see through Dataverse security roles and business unit structure; it does not expose records the rep could not already open by browsing the CRM directly. Since the rep's role limits visibility to owned or team-assigned opportunities, Copilot's answer reflects that same restricted view rather than the full territory the manager can see. The separate-access-list explanation is incorrect because Copilot has no independent permission model to reconfigure; it inherits Dataverse access at query time. The seven-day recency explanation is incorrect because there is no seven-day recency filter built into Copilot's natural-language answers, and nothing in the scenario suggests the missing opportunities were all stale. The independent territory-filter explanation is incorrect because there is no separate territory-filter toggle; visibility is governed by security roles and team membership, not a standalone geographic setting. The fix, if the manager wants the rep to see more, is to adjust the rep's security role or team assignment, not to look for a Copilot-specific access control.