Outlook and Salesforce Integration: The 2026 Setup Guide

Your best rep works every deal from Outlook. Emails fly back and forth, a meeting gets booked, a follow-up gets promised, and none of it lands in Salesforce. Friday afternoon the sales manager pulls an activity report to see which accounts are actually moving, and half the real work is invisible, sitting in inboxes nobody logged.

That gap is what an Outlook and Salesforce integration exists to close. Done right, the emails and meetings your team already sends get logged against the correct contact and opportunity with no copy-paste, and a rep can create or update Salesforce records from the Outlook pane they live in all day. Done wrong, you get a side panel nobody opens, a sync that silently drops history after a few months, or a connector Salesforce is about to switch off.

Salesforce supports two native paths in 2026, and getting the licensing and retention rules right is what decides whether either one survives real volume. Make these decisions in order and the integration fades into the background. Skip them and you rebuild it in a year.

Decide what "integration" actually means for your team

"Connect Outlook and Salesforce" hides three different jobs, and most failed setups tried to do the wrong one. Before you install anything, name which of these you need:

Log activity automatically. Every email and calendar event your reps send or receive gets captured and attached to the matching Salesforce contact, lead, or opportunity, so the activity timeline reflects reality without anyone clicking "log a call."
Work Salesforce from inside Outlook. A side pane in Outlook that shows the Salesforce record for whoever emailed you, and lets a rep add a contact, log an email, or update an opportunity without leaving their inbox.
Two-way sync of contacts and events. Salesforce contacts and calendar events mirror into Outlook and back, so a change in one appears in the other.

These map to different features, and conflating them is the first mistake. A team that just wants clean activity reporting does not need the side pane open all day. A rep who wants to create records from Outlook does not automatically get their sent mail captured. Write down which job matters, because it decides everything downstream. If sorting out which systems own which records feels murky before you touch a single setting, that mapping is the Workflow Design work a project should start with, and it is the same discipline behind deciding when a task is worth automating at all.

Pick the native path, and skip the one that is retiring

Salesforce ships two current, supported ways to connect Outlook, plus a third you should not build on.

| Feature | What it does | Status in 2026 | |---|---|---| | Outlook Integration (the add-in) | Salesforce pane inside Outlook: view records, log emails, create and update records from the inbox | Supported, recommended | | Einstein Activity Capture (EAC) | Automatically captures emails and events and syncs them to the activity timeline | Supported, actively changing | | Salesforce for Outlook (legacy) | Old desktop side panel and contact/event sync connector | Retiring, do not build on it |

Salesforce lists the old desktop connector as "Salesforce for Outlook (Retiring)" and has rescheduled its full retirement to December 2027, per Salesforce's retirement notice. When it goes, it stops syncing contacts, events, and tasks, and the old side panel disappears. If you are on it, you are not integrating, you are running down a clock. Salesforce directs everyone to the Outlook Integration add-in and Einstein Activity Capture instead.

The practical read: the add-in covers the "work Salesforce from Outlook" job, and Einstein Activity Capture covers the "log activity automatically" job. Most teams turn on both, because they solve different halves of the problem. The pair replaces everything the retiring connector used to do.

Check editions, licensing, and the 100-user cap first

The native tooling has no separate connector fee. You pay through the Salesforce edition you already hold, so the real question is whether your tier includes what you want and how many people it covers.

The Outlook Integration add-in requires a Salesforce subscription and Lightning Experience, and its requirements page focuses on client compatibility rather than gating a specific edition, per Salesforce's system requirements. Einstein Activity Capture is where the limits bite. Per Salesforce's comparison of EAC Standard and the full version:

EAC Standard is included at no extra cost with Sales Cloud editions including Starter, Pro Suite, Professional, and Enterprise.
Standard is capped at 100 users. Past that, you need the full version.
The full version comes with Unlimited edition, Einstein 1 Sales, and Agentforce 1, or as a paid add-on such as Sales Cloud Einstein, Inbox, or Sales Engagement on Enterprise.

For a lean team under 100 reps on Professional or Enterprise, the answer is usually simple: Standard is included, turn it on. The sticker shock only appears if you have more than 100 users on activity capture or you want the longer retention and reporting that only the full version unlocks. Decide that before rollout, not after a rep asks why last quarter's emails vanished.

Install the Outlook add-in and connect it

With editions confirmed, the add-in itself is the quick part. It installs one of two ways, per Salesforce's setup documentation:

Per user, from Microsoft AppSource. Each person adds the Salesforce add-in to their own Outlook. Fine for a handful of reps.
Centralized deployment by an admin. Your Microsoft 365 admin pushes the add-in to everyone through the Exchange admin center. This is the right move for any team above a few people, because it stops the setup from depending on each rep finding and installing the right thing.

One catch worth confirming before you promise a rollout date: the add-in supports Outlook on the web and current desktop builds, but Salesforce pins specific minimum versions. Its requirements page lists builds like Office on Windows 2409 or later and Outlook on Windows perpetual retail 2501 or later, per the same system requirements page. Reps stuck on an old locked-down Office build can hit a wall, so check versions before you announce the launch.

Once installed, each rep authenticates the pane into your Salesforce org. From there they can see the matching record for an email sender and log messages by hand. Manual logging is the floor, not the ceiling, which is exactly why the next step matters.

Turn on Einstein Activity Capture and set retention deliberately

The add-in lets a rep log an email. Einstein Activity Capture logs them all without anyone deciding to. This is the feature that fills the activity timeline, and it is also where the quietest data loss happens.

EAC captures emails and events and attaches them to matching Salesforce records. Where that captured data lives, and how long it survives, depends on your version and settings. Historically, captured activity was stored on Salesforce's Activity Platform infrastructure rather than the core database, did not count against your Salesforce storage limits, and was governed by a retention window, per Salesforce's data storage documentation. Newer configurations that use Sync Email as Salesforce Activity write emails into standard Task and Email Message records instead, which do count toward storage but behave like normal Salesforce data.

The retention numbers are the part to internalize before rollout, per Salesforce's retention documentation:

| Version | Default retention | Adjustable range | |---|---|---| | EAC Standard | up to 6 months | 3 to 6 months | | Full EAC (paid) | 24 months | 3 months to 5 years, via Salesforce Support |

Read that table twice. On the free Standard tier, captured activity older than roughly 6 months rolls off the timeline. For a team that wants two years of email history against an account to understand a renewal, Standard alone will not hold it. That is not a bug to fix later, it is a licensing decision to make now: either move the activity you care about into real Salesforce records with Sync Email as Salesforce Activity, or budget for the full version and its 24-month default.

Reporting carries the same asymmetry. Captured EAC data reports through dedicated activity report types rather than every standard report, per Salesforce's activity reporting overview. If your revenue reporting depends on querying email and meeting activity like any other object, confirm the report types cover what you need before you tell leadership the data is there.

Migrate authentication to Microsoft Graph before EWS dies

This one has a hard deadline, and it breaks working setups that ignore it. Microsoft is retiring Exchange Web Services (EWS), the older protocol many Microsoft-to-Salesforce syncs still authenticate through, in October 2026. Salesforce is telling admins to move Einstein Activity Capture, Inbox, and the legacy Lightning Sync onto Microsoft Graph so capture and sync do not stop, per Salesforce's Einstein Activity Capture guidance.

If your integration was set up more than a year or two ago, this is the single most likely thing to silently take it down. An EAC configuration still using EWS after the retirement stops capturing and syncing, and nobody gets an alert that says so. Reps just notice, eventually, that new email stopped showing up. Put the Graph migration on the calendar as a dated task, not a someday item, and verify the connection method in your EAC setup rather than assuming a working sync is a modern one.

Common mistakes that break the sync later

The integration rarely fails on install day. It fails months in, when a version lapses, a retention window expires, or a protocol gets switched off.

Building on Salesforce for Outlook. The retiring connector still runs today, so teams keep leaning on it. It stops syncing at full retirement in December 2027, and every month you delay migrating is migration debt you still owe.
Assuming EAC keeps history forever. Standard tops out around 6 months of retained activity. Teams discover this the day someone needs last year's email trail on a renewal and it is gone.
Ignoring the Graph deadline. An EWS-based capture that works today can go dark after October 2026 with no error anyone sees.
Turning it on without deciding what gets logged. Auto-capturing every personal and internal email clutters records and raises privacy questions. Scope what syncs.
No monitoring. When capture stops, whether from a version bump, an auth change, or a limit, it fails quietly. Someone has to actually watch that activity is still flowing, or the first signal is a rep complaining.

This failure shape is not unique to Outlook. It is the same reason DIY automations quietly break as a team scales, and the same reason a connector alone rarely settles an email-to-CRM data problem the way disciplined email automation does.

When to set it up yourself vs bring in bottta

If you run one Salesforce org, fewer than 100 reps, and you just want sent mail and meetings on the timeline, you can stand up the native tooling yourself. Push the add-in through centralized deployment, turn on Einstein Activity Capture, confirm you are on Microsoft Graph, and check that activity is flowing. Plenty of lean teams do exactly that, and they should.

Bring in bottta when the integration is load-bearing and getting it wrong costs real money. We start with the part most teams skip: deciding which activity has to become permanent Salesforce records versus what can live on the capture timeline, which retention tier the business actually needs, and how the whole thing reports. Then our Integrations work handles the add-in deployment, the EAC configuration, the Graph migration, and the sync-as-activity setup so the data holds under volume instead of rolling off a cliff at month six. A one-time setup fits our $4K project: fixed scope, fixed price, integrations included, with 30 days of post-launch support. When the stack keeps moving, new reps, new fields, a Salesforce retirement to stay ahead of, our $3K/month retainer covers the monitoring and fixes so a silent capture failure gets caught by us, not by your sales lead three weeks late.

Third-party sync tools exist for edge cases the native path does not cover, and they earn a look when you need per-field control Salesforce does not expose. For most growing teams, the native add-in plus EAC done properly is enough, and the value is in the decisions around it, not the install. That build-versus-bring-in-help call is the same one behind the HubSpot to Salesforce sync, a NetSuite to Salesforce build, and any sales automation software rollout: DIY the simple case, get help when a broken sync means deals go dark.

Frequently asked questions

Is the Outlook Salesforce integration free?

The native tooling has no separate connector fee. The Outlook Integration add-in needs a Salesforce subscription, and Einstein Activity Capture Standard is included at no extra cost on Sales Cloud editions like Professional and Enterprise, capped at 100 users, per Salesforce's documentation. The full version, with longer retention, comes with higher editions or as a paid add-on.

What replaced Salesforce for Outlook?

The Outlook Integration add-in and Einstein Activity Capture. Salesforce lists the old desktop connector as retiring, with full retirement rescheduled to December 2027, per Salesforce's retirement notice, and directs customers to the add-in and EAC instead.

How long does Einstein Activity Capture keep email history?

On EAC Standard, up to 6 months, adjustable within a 3-to-6-month range. On the full paid version, 24 months by default, adjustable from 3 months to 5 years through Salesforce Support, per Salesforce's retention documentation. If you need permanent history, sync emails into standard Salesforce records instead of relying on capture alone.

Why did my Outlook to Salesforce sync suddenly stop?

The most common 2026 cause is authentication. Microsoft is retiring Exchange Web Services in October 2026, and any Einstein Activity Capture or Inbox setup still using it stops capturing unless it moves to Microsoft Graph, per Salesforce's guidance. Check your connection method before assuming a working sync is a current one.

Do I need both the add-in and Einstein Activity Capture?

They do different jobs. The add-in gives reps a Salesforce pane inside Outlook to view and update records by hand. EAC captures email and calendar activity automatically for the timeline. Most teams turn on both, since one covers working from the inbox and the other covers logging without anyone remembering to.