A consultant is scoping a Dynamics 365 Sales implementation for a client that wants relationship health scores, who-knows-whom connection mapping, and talking points generated automatically from sellers' email and calendar activity. The client currently holds only base Dynamics 365 Sales licenses for its sellers. What should the consultant tell the client about delivering these capabilities?
Select an answer to reveal the explanation.
Short Explanation
When a client describes relationship scores, who-knows-whom mapping, and auto-generated talking points, that is basically a checklist of the premium relationship analytics features, and those live behind the higher Dynamics 365 Sales licensing tier, not the base one. So the honest scoping answer is straightforward: move the sellers who need this onto the tier that includes it, rather than hunting for a hidden switch or a workaround. It is tempting to think everything in Dynamics 365 is unlocked by a settings toggle, but premium analytics specifically is not one of those things, it is tied to what each user is licensed for. It is also tempting to reach for Power BI since relationship data sounds like a reporting problem, but that is a different product entirely and is not what powers this feature inside Sales. And building a custom automation to replicate what is already a supported, native capability would just mean reinventing something the platform already does well, at far more cost and risk than simply licensing correctly.
Full Explanation
The correct answer is C. Relationship health scores, connection insights, and auto-generated talking points are part of the relationship analytics and Sales Insights capability set bundled into Dynamics 365 Sales Premium; sellers who need them must be licensed at that tier, so the consultant should scope a licensing upgrade for the affected users rather than expect them on the base license. Option A is incorrect because these are premium capabilities gated by licensing, not hidden settings available to every seller for free; an administrator cannot simply switch them on for base-licensed users. Option B is incorrect because it confuses the feature with Power BI, a separate analytics product; relationship analytics runs natively inside Dynamics 365 Sales and does not depend on a Power BI Premium capacity to function. Option D is incorrect because it overstates the engineering effort needed, since these are native, supported features of the premium license rather than something that must be reconstructed with custom automation. Advising the client to license the right sellers at the premium tier is both the accurate and the lowest-effort path to the outcome they are describing.