Salesforce Outlook Integration
Setup, add-in options and support for the Salesforce Outlook integration: the add-in approved in Microsoft 365, Einstein Activity Capture configured, and email logged from Outlook landing on the right record with the fields you need.
01
The products
What Salesforce’s Outlook integration actually includes
“Salesforce Outlook integration” means one of three things: the Outlook integration add-in, Einstein Activity Capture, or Salesforce for Outlook — the old desktop plug-in, which has been retired. Knowing which one a team is using explains most of what it can and cannot do.
The Outlook integration add-in
An add-in pane inside Outlook — on the web, the new Outlook, and Outlook desktop for Windows and Mac — that shows the Salesforce contacts, leads, opportunities and cases related to the email or event you have open. Users log emails and events to records by hand, create records from the pane and see recent activity without leaving the inbox. It was called Lightning for Outlook, and it needs Lightning Experience.
Einstein Activity Capture
Activity Capture connects each user’s mailbox and calendar to Salesforce and adds their emails and events to the activity timeline of related records automatically, with nobody clicking Log. It can also sync contacts and events between the two systems. What it captures is shown on the timeline, but it is not stored as ordinary Task records, which matters the first time someone tries to build a report on it.
Salesforce for Outlook (retired)
The Windows desktop plug-in Salesforce offered before the add-in. It is retired and no longer supported, and orgs still depending on it need to move to the add-in, Activity Capture or both.
02
What syncs
What the add-in does — and does not — sync
- Syncs, when a user logs it: emails and events, to the contact, lead, account, opportunity or case the user chooses, with attachments if the org allows them.
- Syncs automatically with Activity Capture: sent and received email and calendar events for connected users, plus contacts and events if contact and event sync are on.
- Does not sync on its own: anything in a mailbox that is not connected, including most shared and delegated mailboxes; emails a user never logged, if Activity Capture is off; and custom fields nobody put on the logging layout.
- Is not reportable by default: Activity Capture’s emails. Logged emails become Task records, or EmailMessage records with Enhanced Email on, and those report normally.
So the usual design is both: Activity Capture for the sales team, whose email should reach Salesforce without anyone thinking about it, and the add-in for logging the specific emails that need to sit on a record with the right fields filled in.
03
Failure points
Common failure points, and the fix for each
“Need admin approval”
The most searched Outlook integration problem. Your Microsoft 365 tenant blocks users from consenting to third-party apps, so the Salesforce add-in stops at an approval screen. A Microsoft 365 or Entra ID administrator grants tenant-wide consent to the Salesforce app once, or deploys the add-in centrally from the Microsoft 365 admin centre to the users who need it. Centralised deployment is better anyway: the add-in appears for everyone without each user installing it.
Shared mailboxes and delegates
Support and sales-ops teams often work from a shared inbox, and neither the add-in nor Activity Capture treats one like a personal mailbox. The workable patterns are logging from each user’s own mailbox, routing the shared address into Salesforce with Email-to-Case, or a small custom service for the rest. Pick one deliberately rather than discovering the gap after rollout.
Field mapping for Log an Email
When a user logs an email, the fields they see and fill come from the action layouts the Outlook integration settings assign in Salesforce, not from the Task page layout. A custom field that is not on that layout never gets captured, and a required field or validation rule on Task can block logging entirely. Put the fields on the logging layout, check validation rules against Task, and turn on Enhanced Email if you want logged emails stored as EmailMessage records with their full body and recipients.
Requirements nobody checked
Lightning Experience in Salesforce, the Outlook integration enabled in Setup, Microsoft 365 or a supported on-premises Exchange Server, and for Activity Capture its own licence and connection method. Most rollouts that stall fail one of these on day one.
04
When to call
When you need a partner
A small team on Microsoft 365, starting fresh, can switch on the add-in by following Salesforce’s setup guide. Bring us in when the rollout crosses two admin centres with different owners, when emails already captured need to become reportable, when a shared mailbox has to reach Salesforce, or when you are moving off Salesforce for Outlook and need logged history and user habits to survive the move.
We decide which product each team should use, get consent and centralised deployment done in Microsoft 365, configure Activity Capture and the logging layouts, and hand over a one-page guide users actually read. Outlook is one of the Salesforce integrations we build most often.
05
The problem
Why people call us about this.
A
Users click the Salesforce add-in and get “Need admin approval” instead of their records.
B
Emails were captured for months, and nobody can report on them.
C
The team works from a shared mailbox, and none of it reaches Salesforce.
06
What’s covered
The Salesforce we actually configure.
The Outlook integration is two products and a retired third, set up across two admin centres. Most of the work is deciding which one each team should use and getting Microsoft 365 and Salesforce to agree on it.
07
How it runs
Five phases, and what you see at the end of each.
01 · Week 1
Inventory
What exists, who owns it, and which system is really the source of truth. Almost always surfaces something nobody knew was live.
A written map
02 · Weeks 2–3
Contract
The design in writing, with each decision and its reversal cost named. This is where we argue with the brief — before money is spent.
A signed scope
03 · Middle
Build
Built against the contract and reviewed against it. You see working software every two weeks, in your own sandbox.
Fortnightly demos
04 · Late
Prove
Volume testing at twice expected load, deliberate failure injection, and a replay run with your team watching.
A test evidence pack
05 · Final week
Hand over
Runbook, monitoring, escalation path and a named owner on your side — then a month watching it together before we step back.
Runbook and owner
08
First call
Thirty minutes. Three answers.
You speak to a certified architect, not a sales engineer. No deck, no discovery fee, and no obligation to go further — you leave the call with three things whether you hire us or not.
Whether this is even the right line
About a third of the time it is not, and we say so. Usually the ask is custom development when the real problem sits in the data model underneath.
A shape and a range
Roughly how long, roughly how many people, and the band it falls in. The firm number follows discovery about two weeks later, and it holds.
The two risks we would flag
The things most likely to blow the timeline on a project like yours — named on the call, before anyone has signed anything.
Book it for this week.
Pick a slot directly in the calendar — most questions get answered inside the thirty minutes.
09
FAQ
Asked on nearly every call.
Why does the Salesforce Outlook integration say it needs admin approval?
Your Microsoft 365 tenant does not let users consent to third-party apps on their own. A Microsoft 365 or Entra ID administrator has to grant consent to the Salesforce app once, or deploy the add-in centrally from the admin centre, and the prompt disappears for everyone.
What are the requirements for the Salesforce Outlook integration?
Lightning Experience in Salesforce, the Outlook integration switched on in Setup, and Microsoft 365 or a supported Exchange Server. It runs in Outlook on the web, the new Outlook and Outlook desktop for Windows and Mac. Einstein Activity Capture has its own licence and connection settings on top.
Can we map custom fields when logging an email from Outlook?
Yes. Logged emails become Task records, or EmailMessage records with Enhanced Email turned on. The fields users see come from the action layouts assigned in the Outlook integration settings, so custom fields go on those layouts, and validation rules on Task apply to them.
Is Salesforce for Outlook still supported?
No. The old Windows desktop plug-in has been retired, and orgs still relying on it need to move to the Outlook integration add-in, Einstein Activity Capture, or both. We plan that move so logged history and user habits survive it.
Other lines