A consultant enables email engagement tracking, part of Sales Insights, so reps can see open and click notifications on emails sent from Dynamics 365 Sales. Testing shows the feature works correctly for reps whose mailboxes are configured through server-side synchronization with Exchange Online, but produces no notifications at all for a subset of reps whose mailboxes are configured through a POP3 connection. What should the consultant tell the client?
Select an answer to reveal the explanation.
Short Explanation
Email engagement tracking needs a real pipe back to the mail server so it can hear about opens and clicks after a message goes out, and that pipe is built through Exchange Online sync. A POP3 connection is more like a one-way mailbox check, it pulls messages down but was never built to report back these kinds of signals, so there is simply no channel for the tracking data to travel through, no matter how the feature itself is switched on. The tempting wrong explanations all borrow real settings from elsewhere in the product, a generative assistant toggle, a security boundary between business units, a storage limit, and apply them somewhere they do not actually reach. None of those affect the mail-server integration itself, which is the one thing that actually decides whether tracking data can flow at all.
Full Explanation
The correct answer is B. Email engagement tracking is built on top of Exchange Online integration, using server-side synchronization to detect and report open and click events back into Dynamics 365 Sales; a POP3 connection does not provide that integration path, so tracking data has nowhere to flow from for those mailboxes no matter how the Sales Insights feature itself is configured. This explains the exact pattern in the scenario, where reps on server-side sync see the feature work while POP3 reps see nothing. Option A is incorrect because Copilot in the Outlook add-in is a separate generative-assistance capability and has no dependency relationship with engagement tracking, which is a Sales Insights notification feature. Option C is incorrect because business unit membership governs record-level security and visibility, not whether an individual mailbox's technical connection method supports engagement tracking. Option D is incorrect because mailbox storage quota affects a user's ability to send and receive mail, not whether Dynamics 365 Sales can register open and click events on already-sent messages, and a full mailbox would generate visible delivery errors rather than silently disabling one feature.