If your reps live in Outlook, your Salesforce data is only as good as the bridge between them. And in 2026 that bridge moved under everyone’s feet.
Microsoft started switching off Exchange Web Services, Salesforce changed how Einstein Activity Capture stores email, and 2 older tools are counting down to retirement. This guide sorts out what to run now, how to set it up, and what tends to break in the first month.
The 4 tools people mean when they say “Outlook integration”
Salesforce has shipped 4 different Microsoft products over the years, and they still get mixed up in support tickets. Here’s how they differ.
| Tool | What it does | Status in late 2026 |
|---|---|---|
| Outlook Integration (the add-in) | Side panel inside Outlook. Reps see Salesforce records, log emails and events, and create records without leaving the inbox. | Current. Salesforce’s recommended path. |
| Einstein Activity Capture (EAC) | Background sync of emails, events and contacts, with no clicks from the rep. | Current. Changed a lot in 2026 (see below). |
| Lightning Sync | Older background sync for contacts and events. | Being retired. Not sold to new orgs since Winter ’21. |
| Salesforce for Outlook | Desktop plugin from the Classic era. | Retiring. Full retirement scheduled for December 2027. |
The add-in and EAC are designed to work together. The add-in is what the rep sees. EAC is what runs behind it.
Salesforce’s own Salesforce for Outlook getting started guide now carries a banner saying full retirement is scheduled for December 2027. If anyone on your team still has that plugin installed, that’s your first migration.
What changed in 2026, and why it matters to you
This year brought 3 separate changes. Each one can break a setup that worked fine in 2025.
Microsoft is shutting off Exchange Web Services
Any Salesforce sync that still talks to Exchange Online through EWS is on borrowed time. Microsoft’s Exchange Team confirmed in its February 2026 post, updated in October 2026, that tenants started being switched to “EWS blocked” from October 1, 2026, and that EWS is fully disabled on April 1, 2027.
This hits Lightning Sync hardest. Salesforce Ben’s Summer ’26 roundup noted that orgs running Lightning Sync with Microsoft 365 and EWS authentication had to move to Einstein Activity Capture by August 2026. If you’re reading this and still on Lightning Sync, you’re already past that date.
Einstein Activity Capture now needs configurations
From April 2026, Salesforce stopped capturing email for users who aren’t part of an EAC configuration, and started placing unassigned users into an automatic default one. If your sync went quiet for some users this spring, check Setup, then Einstein Activity Capture, then the Summary tab for “Users not in a configuration.”
Captured email is becoming real Salesforce data
This is the change we like most. The older EAC kept captured emails outside your org, which meant they showed on the activity timeline but stayed out of standard reports. Salesforce Ben’s review of EAC (updated 2023) put the retention at 6 months by default and 24 months on paid licenses, after which the data was deleted.
The updated version syncs email as Salesforce activity. Salesforce’s help article on the migration says automigration started in June 2026, the move is one-way, and “unmigrated email bodies can’t be retrieved later.” Read that last line twice before you pick how many months to migrate.
Pick your setup by how your team actually logs email
Most teams pick a tool first and argue about logging rules later. Do it the other way round. Decide what should end up in Salesforce, then pick the setup that gets it there.
| Your situation | Run this | Why |
|---|---|---|
| Reps should choose what gets logged (legal, finance, recruiting, sensitive deals) | Outlook Integration only | Every logged email is a deliberate click. Nothing private slips in. |
| You want a complete activity history with no rep effort | Outlook Integration plus EAC, synced as Salesforce activity | Reps keep the side panel. Email and meetings land on records automatically. |
| You need activity in reports, flows or Agentforce | EAC with Sync Email as Salesforce Activity, full email capture | Header-only capture won’t give an agent the body text to work from. |
| You’re regulated and must control retention | Outlook Integration, plus EAC with header-only capture and tight exclusions | You keep a record of who talked to whom without storing every email body. |
| You’re still on Lightning Sync or Salesforce for Outlook | Migrate to Outlook Integration plus EAC now | Both are on retirement paths, and EWS is already being blocked. |
There’s no prize for capturing everything. A 200-person firm that syncs every email from every rep will fill timelines with newsletters and internal threads unless someone sets exclusions on day 1.
What it costs
The Outlook Integration add-in comes with Sales Cloud and Service Cloud. You don’t buy it separately.
EAC has a standard tier that ships with most Sales Cloud editions, and paid tiers that raise limits and retention. The exact entitlement depends on your edition and contract, so check Setup, then Company Information, then Permission Set Licenses before you plan the rollout. We’ve seen teams design around full capture for 300 users and then find their contract only covers part of that.
The bigger cost is admin time. A clean rollout for a 30 to 50 user sales team usually takes us 2 to 3 weeks: 1 week to configure and pilot, 1 week to fix matching rules and exclusions, and a few days to train.
How to set it up, step by step

This is the order we use. It assumes Microsoft 365 and Lightning Experience.
- Turn it on in Salesforce. In Setup, search “Outlook Integration and Sync.” Switch on Outlook Integration and decide which email features reps get.
- Deploy the add-in from Microsoft’s side. Have your Microsoft 365 admin push the Salesforce add-in with centralized deployment from the admin center. Central deployment beats asking 50 people to install it themselves.
- Design the side panel. Use the Lightning App Builder to set what reps see on an email: the matched contact, open opportunities, recent cases. Keep it to 3 or 4 components or reps stop reading it.
- Create your EAC configuration. Choose the connection (org-level through Microsoft Graph is easier to manage than per-user), what syncs (emails, events, contacts) and the sync direction for each.
- Set exclusions before anyone syncs. Exclude internal domains, personal email providers, executive assistants’ shared mailboxes and any domain your legal team names.
- Choose capture type and migration window. Full email or header only, and how many months of history to bring across. Remember the migration is one-way.
- Pilot with 5 to 10 users for a week. Check matching, duplicates and calendar sync before you widen it.
- Roll out by team, not by org. Sales first, then account management, then support.
If your Salesforce email sending also changed this year, our post on Salesforce email behavior changes in 2026 covers verified domains and SMTP settings, which are a separate project from inbox sync.
The problems we see in the first month
Almost every Outlook rollout hits some mix of these. None are hard to fix once you know where to look.
Emails attach to the wrong record. EAC matches on email addresses. If the same person exists as a lead and 2 contacts, the email goes somewhere you didn’t expect. Clean duplicates before go-live. A one-off Salesforce CRM cleanup is cheaper than untangling 6 months of misfiled history.
Contact sync creates duplicates. Bidirectional contact sync turns every Outlook address book into a source of new Salesforce contacts. Start with Salesforce-to-Outlook only, then open the other direction once your matching is solid.
Some users stopped syncing in April or May. They’re outside an EAC configuration. Add them by profile rather than one by one so new hires get picked up automatically.
Reports don’t show the emails. On the older EAC, they won’t. Check whether your org has migrated to Sync Email as Salesforce Activity.
The add-in is missing in new Outlook or Outlook on the web. Usually a deployment scope problem on the Microsoft side. The add-in was pushed to a group that doesn’t include those users.
Reps log the same thread 3 times. Train one rule: log the first email of a thread to the right record and let threading do the rest.
A worked example: a 40-person sales team
Picture a B2B software company with 40 sellers on Sales Cloud, a mix of Lightning Sync and manual logging, and Microsoft 365. Leadership wants to see every customer touch on the opportunity before the quarterly forecast call.
We’d run Outlook Integration for all 40, plus EAC in one configuration for the sales profile, synced as Salesforce activity with full email capture. Exclusions cover the company’s own domain, 3 partner domains used for internal coordination, and Gmail and Yahoo addresses.
Contacts sync one way at first. History migrates for 12 months, which covers the current fiscal year plus a buffer. Lightning Sync gets switched off the day EAC goes live for each user, never before.
The result to aim for in 30 days: at least 90% of customer meetings showing on the related opportunity, and a duplicate rate on new contacts under 2%. Those are targets, not a benchmark, so set your own baseline in week 1.
We’ve seen the cost of skipping this step. In our swivel-chair prospecting case study, reps were copying data between tools by hand and leadership had stopped trusting the forecast. Inbox activity is the same problem with a different tool.
Where Outlook fits in your wider integration plan
Outlook is usually the first integration a sales team asks for and the one they notice most when it fails. It’s rarely the only one. For the rest of the stack (ERP, billing, support desks, e-signature), our rundown of the 15 most common Salesforce integrations shows what each one fixes.
Teams on Google Workspace face a parallel set of choices. Our Salesforce Gmail integration guide covers that side.
Frequently asked questions
1. Is the Salesforce Outlook integration free?
The Outlook Integration add-in is included with Sales Cloud and Service Cloud, so there’s no separate fee for the side panel. Einstein Activity Capture has a standard tier included with most Sales Cloud editions and paid tiers with higher limits and longer retention. Check your org’s permission set licenses to see which you have before you design the rollout around automatic capture for every user.
2. Is Salesforce for Outlook being retired?
Yes. Salesforce’s documentation lists December 2027 as the full retirement date for the Salesforce for Outlook desktop plugin.
It’s separate from the modern Outlook Integration add-in, which is Salesforce’s recommended replacement alongside Einstein Activity Capture. If anyone still runs the old plugin, plan that migration now so it isn’t squeezed against other year-end work.
3. Does Microsoft’s EWS shutdown affect Salesforce?
It affects any Salesforce sync that connects to Exchange Online through Exchange Web Services, which mainly means older Lightning Sync setups and some third-party tools. Microsoft began blocking EWS tenant by tenant from October 1, 2026 and disables it fully on April 1, 2027. The Outlook add-in and current Einstein Activity Capture connect through Microsoft Graph instead.
4. Can I report on emails captured by Einstein Activity Capture?
With the older version, mostly no, because captured emails were stored outside your org and didn’t appear in standard activity reports. With Sync Email as Salesforce Activity, which Salesforce began automigrating orgs to in June 2026, synced emails become Salesforce activity data you can report on. Header-only capture limits what’s available, so pick full capture if reporting or AI agents need the email body.
5. How long does an Outlook integration rollout take?
For a sales team of 30 to 50 users, plan on 2 to 3 weeks. That’s roughly a week to configure and pilot, a week to fix matching rules and exclusions, and a few days of training. Larger orgs with several business units, regulated data or a Lightning Sync migration take longer, mainly because exclusions and retention need sign-off from legal or compliance.
Get Outlook and Salesforce working together
HyphenX sets up Outlook Integration and Einstein Activity Capture, migrates teams off Lightning Sync and Salesforce for Outlook, and cleans the data so emails land on the right records. Talk to our Salesforce integration services team about your rollout.