A consultant is configuring Dynamics 365 Sales so an enterprise account team can see relationship insights showing which stakeholders are engaged, which are going cold, and how the overall buying group is trending. Partway through testing, the insights panel shows no meaningful data even though the opportunity has several contacts attached. (Select TWO.) Which two conditions are necessary for the relationship insights to populate correctly?

Relationship insights populate only when two conditions are met: contacts must be linked to the opportunity with defined roles, and email and calendar activity must be flowing into Dynamics 365 through server-side sync or a similar integration. The role links tell the system who the stakeholders are and what role each one plays, while the synced activity gives it evidence of how those stakeholders are actually being engaged. Without both pieces, the feature has no one to analyze and no interactions to analyze them against, which explains why the panel is empty despite contacts existing on the record. The requirement that each contact record have a populated LinkedIn profile URL is incorrect because relationship insights are derived from tracked interactions within Dynamics 365 Sales, not from external social profile completeness; a missing LinkedIn URL has no bearing on whether engagement trends can be calculated. The requirement that the opportunity must be in the final pipeline stage before insights become available is incorrect because gating insights to only the final pipeline stage would defeat the purpose of the feature, which is to give teams early visibility into stakeholder engagement so they can act on a cooling relationship well before the deal reaches its final stage.