Auto capture of emails and meetings

What it does

Looks at the seller's Exchange mailbox and surfaces recent emails and meetings that appear relevant to the record they are looking at, as suggestions on the timeline. The seller decides which ones to track into Dynamics 365; until then nobody else can see them.

Key facts

Enabled at Sales Insights settings > Productivity > Auto capture, with an Enable basic auto capture toggle. Standard Sales Insights has to be enabled first.
Needs Exchange and Outlook in the same tenant as the Dynamics 365 environment, server-side synchronisation set up, and tenant-level approval of user email addresses so the service can query Exchange on their behalf.
Suggestions cover up to 50 recent emails and meetings from the last three days in the seller's mailbox. Appointment suggestions start appearing three days before the meeting itself.
Untracked (auto-captured) suggestions are private to the seller. Only when tracked do they become real activities visible to anyone with access to the record.
Matching is on email addresses in the To, CC and From fields against the record's people: for accounts, the primary contact plus up to the top 50 related contacts and the account's own addresses; for opportunities, the opportunity contact, stakeholders and related account contacts; for leads and contacts, their own addresses. Custom tables match through their account or contact lookups.
Only untracked items are suggested — anything already tracked is a normal activity and appears as such.
From version 9.2.24031.00102, users covered by conditional access policies may see nothing at all. The documented alternatives are the Sales app in Outlook or plain server-side synchronisation.
Configuration is an administration and customisation role; sellers need their normal sales roles.
Turning it on is an explicit consent to share data about customer email activity with an external service.
Suggestions are not stored as Dataverse records until tracked, so they do not appear in reports, do not count towards storage, and do not exist for anyone else.

When to use / skip

Useful where sellers genuinely do their correspondence in Outlook and the client's complaint is "nothing is in CRM". Auto capture reduces logging to a single click on something the seller can already see, which is a much easier behaviour change than asking them to remember to track.

Skip it where the client has conditional access policies that will block the Exchange query — you will spend a week diagnosing an empty timeline that was never going to fill. Skip it too where the Sales app in Outlook is already deployed and used properly, because that covers the same ground with a clearer story and fewer moving parts. And do not sell it as an activity capture guarantee: three days of history and 50 items is a nudge, not an archive.

Configuration decisions

Whether auto capture or the Sales app in Outlook is the primary capture route. Running both without explaining the difference just confuses sellers.
Whether the tenant admin will approve the mailbox querying, which is a genuine security conversation and not always a yes.
Whether the client's conditional access posture is compatible, checked before the feature reaches the design document.
Which record types matter — the matching rules differ by table, and opportunity matching through stakeholders is much richer than lead matching.
Whether tracked meetings should also flow through server-side synchronisation, and how you avoid the same appointment arriving twice.
What the client expects sellers to track versus leave private, because "capture everything" and "personal mail stays personal" are both defensible policies and need stating.

Gotchas

The conditional access interaction is the big one. It fails silently: the toggle is on, permissions look fine, and the timeline simply shows nothing.
Three days is a hard horizon. A seller returning from a week off finds the correspondence they wanted to log has already dropped off the list.
Sellers frequently assume auto capture is tracking things for them. It is not — an untracked suggestion is invisible to colleagues and vanishes with the window.
Mailbox approval is tenant-level and sits with whoever owns Exchange, which is often not the person sponsoring the CRM project. Start that conversation early.
Matching depends on the email addresses actually being on the records. Poor contact data produces poor suggestions, and the client blames the feature.
Personal correspondence appears in suggestions if the address happens to match a contact. Say so during rollout, before someone notices in front of their manager.

Consultant notes

Check conditional access before you promise anything. It is one question to the client's identity team and it saves a fortnight.
Demo the private-versus-tracked distinction explicitly. It is the concept sellers get wrong and it undermines trust in the timeline when they do.
Position it as a prompt rather than a compliance mechanism. If the client needs guaranteed capture of all correspondence, this is not the feature and server-side sync with folder-level tracking is a better conversation.
Check it after any Exchange or identity change post go-live, since the failure mode is an empty list rather than an error anyone raises.
Set the expectation on the three-day window during training, or you will get a ticket titled "auto capture stopped working" every Monday.

Worth revisiting as capture moves further into the agent and Outlook-app experiences, since the boundaries keep moving.