Almanac
Microsoft/d365salesDynamics 365

Consultant-focused KB for Microsoft Dynamics 365 Sales: implementation notes, gotchas, and configuration decisions beyond the official docs — across pipeline management, opportunities, forecasting, sequences, sales accelerator, Copilot, integrations, administration, and licensing.

feature-email-engagement.mdv1 · history
CurrentApplies to EnterpriseUpdated 6 days agoSource Microsoft Learn

What it does

Tracks what recipients do with emails sent from Dynamics 365 — opens, link clicks, attachment views and replies — and shows the results on the email, the timeline and in email views. Sellers opt an individual message in by following it.

Key facts

  • Enabled from Sales Insights settings: grant permissions under Email engagement (standard), then set up and switch on Email engagement. Standard Sales Insights has to be enabled first.
  • Only emails sent from Dynamics 365 are analysed, and only where an account, contact or lead record is in the To or CC line. Mail sent from Outlook without going through the app is invisible to it.
  • Open tracking is a transparent one-pixel image hosted by Dynamics 365. If the recipient's client blocks images, the open never registers.
  • Link clicks work by rewriting hyperlinks as redirects through Dynamics 365. The click count is recorded but not which link was clicked when a message contains several.
  • Attachment views require the attachment to be followed, which stores it as a OneDrive link rather than a true attachment. Same limitation — you get a view count, not which attachment.
  • Attachment tracking therefore needs OneDrive for Business, SharePoint document management for emails and external sharing enabled on SharePoint so an unauthenticated recipient can open the file.
  • Reply tracking depends on the email conversation tracking settings in the Power Platform admin centre being configured correctly.
  • Delivery-time recommendations, based on the recipient's time zone, need Bing Maps enabled in the Sales app.
  • KPIs available in Activities, timeline and email views: total opens, last opened time, link clicks, attachment views, replies, reply rate and open rate.
  • Per-record privacy is controlled by the Follow Email field in Contact Preferences on the contact, account or lead. Default is Allow. Set to Do Not Allow and that recipient gets no beacon, no rewritten links and a direct file attachment instead — scheduling and recommendations still work.
  • Sellers can check View Recipients' Preferences above the message body to see the tracking stance of everyone on the message before sending.
  • Enabling the feature is an explicit consent to share customer email activity data with other Microsoft services.

When to use / skip

Good fit where sellers write genuinely one-to-one email from inside Dynamics and want to know whether a proposal was opened before they ring. It is cheap to switch on and the follow-up reminder is the bit sellers actually use day to day.

Skip it, or scope it tightly, where the team lives in Outlook and only tracks messages back into CRM afterwards — engagement only covers mail composed and sent from Dynamics, so you will get sparse, misleading data. Skip it too for anything bulk or marketing-shaped: that belongs in Customer Insights - Journeys, and using engagement as a substitute gets you neither consent management nor proper analytics. And be careful in privacy-sensitive sectors or jurisdictions with a strict view of tracking pixels — the mechanism is a web beacon, and some clients' own policies rule it out before you have finished the sentence.

Configuration decisions

  • Whether attachment tracking is in scope at all, given it changes attachments into shared OneDrive links and needs SharePoint external sharing switched on.
  • Whether the client's privacy position allows tracking by default, or whether Follow Email should be set to Do Not Allow across the existing contact base as part of data migration.
  • Whether follow-up reminders and the related insight cards — email opened, email reminder — are enabled, since the feature is much less useful without them.
  • Whether Bing Maps goes on for delivery-time recommendations, which is a separate admin decision with its own data-sharing implications.
  • Which email templates sellers work from, because template recommendations are driven by open and reply history across the organisation.
  • Who explains the numbers: agreeing up front that these are approximations avoids an argument about accuracy later.

Gotchas

  • Security scanners and email service providers open messages on the recipient's behalf, inflating open counts. A "three opens within four seconds of sending" pattern is a gateway, not a keen prospect.
  • Web clients cache images, so the second and third genuine opens frequently do not register. The counts skew low as well as high, in different directions for different recipients.
  • Enabling attachment tracking without external SharePoint sharing produces links the recipient cannot open. That is a visible, embarrassing failure in front of a customer.
  • Follow Email defaults to Allow on every record, including migrated ones. If the client's position is opt-in, that default is a compliance problem on day one.
  • Emails to recipients who are not an account, contact or lead cannot be followed at all, which confuses sellers who write to a personal address before creating the record.
  • Rewriting links through a redirect occasionally trips a recipient's link-protection tooling, which is worth knowing before the client's biggest customer reports a phishing warning.

Consultant notes

  • Get the client's data protection people in the room before you enable this. It is a conversation about tracking individuals, not a feature toggle, and having it late is expensive.
  • Demo the sequence sellers care about: send, see the open, get the reminder, make the call. Nobody is moved by an open-rate KPI on its own.
  • Tell the client plainly that the figures are indicative. Set that expectation in the demo, not in the support ticket.
  • Check attachment behaviour end to end with an external mailbox before go-live, not just internally where SharePoint permissions quietly work.
  • If the team lives in Outlook, be honest that engagement will cover only part of their mail and consider whether that partial picture is worth having at all.

Worth another look if the tracking mechanism changes or the client's privacy policy is rewritten.

Was this accurate?