A consultant sets up Dynamics 365 Sales Copilot and Conversation Intelligence for a sales team. After go-live, sellers report that Copilot never generates meeting-prep summaries or call insights for emails and appointments sent from Outlook, even though the same sellers' Teams calls are transcribed correctly. What configuration is most likely missing?
Select an answer to reveal the explanation.
Short Explanation
Copilot can only talk about what's actually stored in Dataverse; it doesn't reach into someone's Outlook inbox directly. Teams calls get into the system through Conversation Intelligence's own recording pipeline, so those show up fine. Outlook emails and appointments need a different bridge: mailbox sync has to be turned on so that activity actually lands in Dataverse in the first place. If that bridge was never built for certain sellers, Copilot has nothing to read for them, no matter how well it works for calls. The wrong turns here are a security role that controls call access rather than email sync, a made-up per-channel enablement step for Copilot, and a mailbox storage limit that has nothing to do with how Copilot reads data. The real fix is turning on mailbox synchronization for the sellers who are missing it.
Full Explanation
The correct answer is B. Copilot generates meeting-prep summaries and email-based insights from activities that live in Dataverse, and Outlook items only reach Dataverse once server-side sync or auto capture is turned on for a mailbox. Teams calls are captured through Conversation Intelligence's own recording pipeline, so those work even while Outlook items for the same sellers are never synchronized, which explains why one channel functions and the other does not. Option A is incorrect because the Conversation Intelligence security role governs access to call recordings and transcripts, not whether Outlook email and appointments are synchronized into Dataverse. Option C is incorrect because Copilot for Sales tenant enablement is not scoped separately by channel; enabling it does not require a distinct Outlook extension step once the underlying data is available. Option D is incorrect because Copilot reads activity records already stored in Dataverse rather than indexing content directly inside a seller's mailbox, so mailbox storage quotas do not affect its ability to summarize. The fix is to enable server-side sync or auto capture for the affected mailboxes so their Outlook activity flows into Dataverse.