A consultant enables Copilot for a pilot group of ten sellers in a Dynamics 365 Sales Premium environment. After the rollout, three sellers report the Copilot pane never appears on their opportunity and account forms, while the other seven see it working normally. The consultant confirms all ten sellers have identical Dynamics 365 Sales Premium licenses and are in the same business unit. What should the consultant check first to explain the gap?
Select an answer to reveal the explanation.
Short Explanation
When a feature works for most people but not everyone, and licensing checks out, think in terms of layers rather than a single switch. Getting the Copilot pane in front of a seller actually requires two things to both be true at once: an administrator has to flip the feature on for the whole environment, and that specific seller's security role has to carry the permission that lets the pane show up on their screen. If the environment switch is on but a handful of sellers are sitting in a role that never picked up that permission, they will look identical to everyone else on paper, same license, same business unit, and still see nothing. The traps here all point somewhere else entirely: one confuses this built-in assistant with a completely different product used for building custom bots, another drags in an old add-on from a prior generation of the platform that has nothing to do with this feature, and the last one imagines a personal on/off switch that doesn't exist because this is controlled centrally, not by each individual user.
Full Explanation
The correct answer is A. Copilot visibility in Dynamics 365 Sales depends on two independent gates: the feature must be switched on for the environment in the Power Platform admin center, and the signed-in user's security role must carry the privilege that surfaces the Copilot pane. Because licensing and business unit are already identical across all ten sellers, a role or team-based security difference affecting only three users is the most likely explanation, so checking role assignments and the environment toggle is the right first step. Option B is incorrect because Copilot inside Dynamics 365 Sales is a native capability of the Sales app itself; Copilot Studio is a separate product for building custom copilots and is not a prerequisite for the built-in Sales Copilot pane. Option C is incorrect because the Sales Insights add-on solution belongs to an earlier, separate embedded-intelligence architecture and has no bearing on whether the newer Copilot pane renders. Option D is incorrect because Copilot is enabled at the environment level by an administrator, not through an individual user preview toggle, so there is no per-user switch for sellers to find or forget to enable.