A consultant is troubleshooting why one seller in an otherwise successful Copilot for Sales rollout cannot see any Copilot features in either Outlook or the Dynamics 365 Sales app, while every other pilot seller can. The environment has Copilot for Sales enabled in the Power Platform admin center, and the seller has a valid Dynamics 365 Sales Premium license. (Select TWO.) Which two additional things should the consultant verify for this specific seller?
Select all correct answers, then click Submit.
Short Explanation
When everyone else on a rollout can use a feature and one person can't, the environment-level switches are already proven fine, so the search narrows to whatever is configured per person rather than per organization. Two things fit that description here: the security role assigned to that individual, since turning a feature on for the environment doesn't automatically hand every user the privileges to see it, and the client-side add-in itself, since installing and signing into it is something each person has to do on their own machine, not something that gets pushed out the moment the feature is enabled centrally. Neither of those depends on licensing, which has already been confirmed. What doesn't fit the pattern are things like a forecast needing to be republished or some approval tied to a scoring threshold, those are unrelated mechanisms borrowed from completely different parts of the system, and neither one has any real connection to whether a person can see an AI assistant feature. Stick to what's actually configured at the individual level: role privileges and the add-in itself.
Full Explanation
The correct answers are B and C. When every other pilot seller can use Copilot for Sales but one cannot, and the environment-wide enablement and licensing are already confirmed, the remaining gaps are almost always tied to that individual seller: whether their security role actually grants the Copilot for Sales privileges, since environment enablement does not automatically give every user visibility into the feature, and whether they have personally installed and signed in to the Copilot for Sales add-in in Outlook, since the add-in is a per-user client installation rather than something environment enablement pushes out automatically. Option D is incorrect because forecast republishing affects forecast configuration and calculation, not whether a seller can access Copilot features, and there is no relationship between the two. Option A is incorrect because there is no manager approval workflow tied to predictive opportunity score thresholds that gates Copilot access; predictive scoring and Copilot for Sales are separate capabilities, and no such approval step exists in either. The consultant should check the seller's assigned security role and confirm the add-in installation and sign-in status before assuming a deeper licensing or environment problem.