Salesforce and Outlook: Einstein Activity Capture and Its Trade-off
Salesforce for Outlook is retired. What replaced it is a side panel plus Einstein Activity Capture — and EAC stores activity somewhere that does not behave like the rest of your Salesforce data.
- Connector
- Native — Outlook Integration add-in plus Einstein Activity Capture
- Sync direction
- Outlook → Salesforce for email and event capture; Salesforce → Outlook for record context in the side panel
- Setup time
- A day for admin setup, minutes per user
- Availability
- Outlook Integration is broadly available; Einstein Activity Capture entitlement and retention vary by edition and add-on
| What | Direction | Detail |
|---|---|---|
| Emails → activity timeline | Outlook → Salesforce | With EAC on, sent and received mail is captured automatically and matched to contacts and leads by address. |
| Calendar events | Two-way | Meetings sync and appear on related records. Two-way calendar sync is configurable and needs a policy on private events. |
| Manual logging | Outlook → Salesforce | The side panel's log button writes a standard Task, which is the reportable, automatable option EAC is not. |
| Record context in Outlook | Salesforce → Outlook | Contact, account, opportunity and case details render beside the message, including related open opportunities. |
| Record creation | Outlook → Salesforce | Create a contact, lead, opportunity or case directly from an email without leaving the inbox. |
| Activity metrics | Outlook → Salesforce | EAC rolls captured activity into Activity Metrics fields — first and last activity dates — which are reportable even though the raw activity is not stored as Tasks. |
Setting it up
- Confirm your EAC entitlement and retention period before designing anything on top of it. This determines whether captured activity is a permanent record or a rolling window.
- Deploy the Outlook Integration add-in centrally through Microsoft 365 admin rather than asking reps to install it individually.
- Configure EAC exclusion rules first — your own domain, recruiters, personal addresses — then enable capture for a pilot group.
- Decide the calendar policy explicitly: which events sync, whether private events are excluded, and who can see a rep's calendar on a record.
- Tell the team the difference between captured activity and logged activity, and mandate manual logging for anything that must be reportable — a demo, a negotiation call, a commitment.
- Rebuild any report or automation that assumed all activity is a Task before switching off the old logging behaviour, not after.
Where the integration stops
- EAC activity is not stored as standard Task records. It lives in a separate store surfaced on the timeline. Reports, list views, triggers and workflow rules built on Tasks will not see it, which is the single most consequential fact about this integration.
- Captured data has a retention window. Depending on entitlement, EAC activity ages out. It is a visibility layer, not a permanent archive.
- Salesforce for Outlook is retired. Anyone still searching for it needs the Outlook Integration plus EAC combination, and the migration is not purely cosmetic.
- Automatic capture pulls in everything. Personal mail, recruiters, vendors — anything to a matched address gets captured unless excluded. Exclusion rules are day-one work, not cleanup.
- Shared mailboxes are not a good fit. The model assumes a personal mailbox belonging to a Salesforce user; team aliases behave badly.
The thing to understand before anything else
Einstein Activity Capture is not a sync. It is a capture-and-display service.
That distinction sounds academic until a sales operations manager tries to build the activity report they have run every quarter for five years and finds it empty. Activity is on the timeline. It is not in the Task object. Reports query the Task object.
Everything else about this integration is straightforward. This part is the one that causes a rollout to be described as a failure six weeks in.
What the side panel is actually good at
Context at the moment of writing. A rep replying to a customer sees the open opportunity, the amount, the close date and any open case without leaving the message. That reduces the number of emails that say something contradicting what support told the same customer yesterday.
It also makes record creation cheap. A new contact from an inbound email is two clicks rather than a context switch, which is the difference between it happening and not.
The exclusion rules deserve real thought
Automatic capture is indiscriminate by design. Left open, it pulls internal mail, supplier correspondence and anything else touching a matched address onto records. Beyond the noise, there is a privacy dimension: reps are often unaware how much of their mailbox becomes visible to colleagues on a shared record.
Set exclusions before enabling capture, tell the team what is being captured, and revisit the list a month in. It is a five-minute configuration that prevents an awkward conversation.