A consultant is configuring Dynamics 365 Sales for a client that wants reps preparing for first calls to see an AI-generated account brief pulling in recent public news about the prospect company, not just data already stored in the CRM. During setup, the account brief only surfaces CRM record fields such as industry and revenue, with no news content. What is the most likely reason?
Select an answer to reveal the explanation.
Short Explanation
When a feature that is supposed to pull in outside news is only showing the same fields already sitting in the CRM record, the likely story is not that the feature is missing, it is that the pipe bringing in outside information was never turned on. Once that connection is switched on, the brief has something new to draw from; until then it is just reflecting back what was already there. It is worth being careful not to mix this up with a feature that needs months of closed deal history before it gets useful, that is a different capability with a different appetite for data, this one is about a live connection, not accumulated history. And who happens to be formally assigned to the account is really a separate question from whether outside content is being pulled in at all, a single rep working solo could get the full picture just as easily as an entire team, as long as the connection itself is configured. Check the plumbing before assuming the ceiling.
Full Explanation
The correct answer is D. Account briefs that include public information beyond what is stored in Dynamics 365 Sales depend on a connected external data source being enabled and configured; until that connection is turned on, the brief has nothing to draw external content from and falls back to whatever fields already exist on the CRM record, such as industry and revenue. The fix is to enable and configure that data source as part of setup, not to change anything about the opportunity or account records themselves. Option A is incorrect because it treats a configuration gap as a permanent product limitation; account briefs are designed to incorporate broader context once the right connection is in place. Option B is incorrect because it confuses predictive opportunity scoring, which genuinely needs a volume of historical closed deals to train on, with account briefs, a generative summary feature with a different set of requirements. Option C is incorrect because assigning an account team affects who can see and act on account records, not whether the brief's external content connector has been switched on; a solo rep with no formal account team could still receive a fully populated brief once the connection exists. The consultant should check the data-source configuration before concluding the feature cannot do what the client wants.