A sales manager at a distribution company wants to turn on predictive lead scoring for her team directly from within Dynamics 365 Sales. She opens the app but cannot find any option to enable the feature, even though her user record has a Dynamics 365 Sales Premium license assigned and she is listed as the owner of every lead in her team's queue. She asks a consultant why she cannot make the change herself. What should the consultant tell her?
Select an answer to reveal the explanation.
Short Explanation
Think of this as two separate keys that unlock two separate doors. One key is the Sales Premium license, and that key only unlocks the door for using the feature day to day, things like seeing a score and grade on a lead. The other door is the setup room where someone actually flips the switch to turn predictive scoring on for the whole environment, and that door needs an administrative key, a security role like System Administrator, not a sales license. Owning the leads in her queue does not help either, because record ownership is about who can work a specific record, not who can reconfigure how the whole system behaves. So when this manager cannot find the toggle, it is not a licensing gap or a data glitch, and she does not need to escalate to Microsoft. She simply is not holding the administrative key. The practical fix is straightforward: someone with the right admin privileges needs to go into the AI Insights configuration area and turn the feature on, after which everyone with the right license, including her, can use it normally.
Full Explanation
The correct answer is A. Predictive lead scoring is an environment-level AI feature, and turning it on or adjusting its configuration is a system administration task performed through the AI Insights (Sales Insights) settings area, which requires a security role like System Administrator or System Customizer. A Sales Premium license controls whether a user can consume the feature, such as viewing scores and grades on leads, but it does not grant the administrative permissions needed to configure the model itself, and being the owner of lead records is a data-access concept that has no bearing on system setup screens. Option B is incorrect because enabling predictive scoring is a self-service configuration step available to properly privileged admins within the tenant; it does not require Microsoft support intervention. Option C is incorrect because it conflates license assignment, which controls feature usage, with security role assignment, which controls administrative configuration access, so a license alone will never surface the setup screen. Option D is incorrect because table-level ownership is not a real Dataverse concept tied to feature configuration, and record or table ownership does not unlock administrative settings anywhere in the platform.