Salesforce for Outlook Configuration
A Salesforce for Outlook Configuration is a set of attributes, stored in Setup, that controlled how the Salesforce for Outlook desktop add-in synced contacts, events, and tasks between Microsoft Outlook and Salesforce.
Definition
A Salesforce for Outlook Configuration is a set of attributes, stored in Setup, that controlled how the Salesforce for Outlook desktop add-in synced contacts, events, and tasks between Microsoft Outlook and Salesforce. Each configuration defined which users it applied to, the direction data flowed, how sync conflicts were resolved, which records qualified through data set filters, and what side panel and email options those users saw. Administrators built and assigned these configurations from Setup under Desktop Administration, then Outlook Configurations.
This feature is on its way out. Salesforce for Outlook is retiring, with full retirement scheduled for December 2027 (a date that has shifted several times, from June 2023 to June 2024 and onward). New orgs cannot adopt it, and the supported path is the Outlook integration (formerly Lightning for Outlook) paired with Einstein Activity Capture. Because the desktop add-in is being wound down, its configuration area is legacy and should not be the basis for new email and calendar work.
How the Salesforce for Outlook Configuration worked, and what to use now
What the configuration actually controlled
A configuration was the admin control panel for the Salesforce for Outlook client. It bundled every setting that decided what a group of users could sync and how. The first thing a configuration did was scope itself to people. You assigned it to specific users, roles, public groups, or profiles, so different teams could get different sync rules from one place. A user picked up exactly one active configuration, and Salesforce resolved which one applied based on that assignment. Inside the configuration, an administrator set the sync direction for contacts, events, and tasks, chose conflict behavior for two-way sync, attached data sets that filtered which records were eligible, and turned the email side panel features on or off. The configuration also decided whether users could override any of these settings locally on their own machine. Locking the settings kept a team consistent. Leaving them open let power users tune sync to their own mailbox. Everything funneled through this one Setup record, which is why understanding it mattered for anyone supporting the old desktop add-in.
Sync direction and conflict behavior
Sync direction told the add-in which way records moved for each object. You could set Outlook to Salesforce, Salesforce to Outlook, or sync both ways. You could also turn syncing off for an object entirely. A common setup synced contacts both ways but pushed events and tasks in one direction only, so calendars stayed authoritative in one system. Direction was set per object, not globally, which gave admins fine control over what flowed where. Conflict behavior only came into play with two-way sync. A conflict happened when the same record changed in both Outlook and Salesforce between sync cycles, so the client could not tell which edit should win. The configuration let you decide the tiebreaker in advance. The two choices were that Salesforce always wins or that Outlook always wins. Picking one removed the guesswork and stopped users from being prompted on every clash. Without a clear rule, conflicting edits could quietly overwrite each other, so this setting protected data quality during round-trip sync.
Data sets: filtering what users could sync
Every configuration had to include a data set, because without one users had nothing to sync. A data set was a collection of filters that limited which Salesforce records were eligible to move into Outlook. The point was to keep mailboxes small and relevant. A sales rep rarely wants every contact in the org synced to a personal Outlook profile, so filters narrowed the set to records that person owned or cared about. Filters used field criteria and ownership conditions. You might sync only contacts the user owns, or only contacts tied to opportunities the user is working. For events and tasks, you could limit sync to a rolling date window so old activity did not pile up locally. Admins could test a data set to preview roughly how many records it would pull, which helped catch filters that were too broad before users felt the load. Because Outlook and the local machine had practical limits, a tight data set was the difference between sync that felt fast and sync that dragged or hit record ceilings.
The side panel and email logging
Beyond background sync, the configuration governed the Salesforce side panel that appeared inside Outlook. When a user selected an email, the side panel searched Salesforce for contacts and leads matching the From, To, and Cc addresses, then showed related records right next to the message. This let reps see Salesforce context without leaving their inbox. The configuration controlled whether users could add an email and its attachments to Salesforce records straight from that panel. Users picked which records to relate the email to, and the message landed against those accounts, opportunities, or cases. One capability that disappeared early was the Action menu in the side panel, which let users create records directly from Outlook. Salesforce retired that menu in June 2020, well before the full product retirement. Email logging through the side panel was one of the most used parts of the add-in, and it is exactly the capability the newer Outlook integration rebuilt with the Email Application Pane and Enhanced Email.
Why it is being retired
Salesforce for Outlook was a downloadable desktop add-in tied to the Windows version of Outlook. That architecture aged poorly. It required local installs, version management, and machine-by-machine troubleshooting, and it did not work cleanly with Outlook on the web or on Mac. As Microsoft moved toward web and add-in based Outlook, a client that lived on each desktop became hard to support. Salesforce announced retirement and has moved the date more than once, landing on December 2027 for full retirement. The phased wind-down means new customers cannot start using it, and existing users will eventually lose sync and the side panel. Salesforce has been explicit that the product will stop syncing contacts, events, and tasks at retirement. Importantly, data already saved in Salesforce stays put. Contacts, events, tasks, and logged emails that synced previously are not deleted when the add-in goes away. What ends is the live connection, not the historical records, so the migration is about reconnecting Outlook through a supported tool rather than rescuing data.
What replaces it: the Outlook integration and Einstein Activity Capture
The modern replacement is two products working together. The Outlook integration, once called Lightning for Outlook, gives users a Salesforce panel inside Outlook on Windows, Mac, and the web. It is enabled in Setup under Outlook Integration and Sync, and it relies on Enhanced Email so messages relate properly to records. Admins shape what the panel shows using the Email Application Pane in the App Builder, which is the spiritual successor to the old side panel configuration. Einstein Activity Capture handles the syncing that the desktop client used to do. It automatically captures emails and events and adds them to the activity timeline of related records, and it can sync contacts and calendar events without a local install. Salesforce Inbox layers productivity features like read receipts and send later on top. Together these cover what a configuration set up by hand: relating email, logging activity, and keeping contacts and events aligned. The setup model is different, since you tune capture and panes rather than per-user desktop configurations, but the outcomes line up with what teams expect from the old tool.
Migrating off the old configuration cleanly
Moving from a Salesforce for Outlook configuration is less about copying settings and more about rebuilding intent in the new tools. Start by listing what each existing configuration did. Note which users it covered, what synced and in which direction, and how email logging was set up. That inventory becomes your requirements for the new stack. Then enable the Outlook integration and decide how syncing should happen. For most teams, Einstein Activity Capture replaces both contact and event sync and the manual logging the side panel offered. Where you previously locked sync direction or set conflict behavior, you now choose capture settings and decide which users are in scope. Data set filters do not carry over directly, so think about what records reps genuinely need surfaced rather than recreating old filters one for one. Communicate the change early, because users who relied on the desktop panel will notice the interface move into a cleaner in-Outlook experience. Plan the cutover before December 2027 so no one loses sync unexpectedly when the old client finally stops.
Trust & references
Cross-checked against the following references.
Straight from the source - Salesforce's reference material on Salesforce for Outlook Configuration.
Hands-on resources to go deeper on Salesforce for Outlook Configuration.
About the Author
Dipojjal Chakrabarti is a B2C Solution Architect with 29 Salesforce certifications and over 13 years in the Salesforce ecosystem. He runs salesforcedictionary.com to help admins, developers, architects, and cert/interview candidates sharpen their fundamentals. More about Dipojjal.
Test your knowledge
Q1. Is Salesforce for Outlook Configuration current?
Q2. What replaces it?
Q3. Should you invest in this configuration?
Discussion
Loading discussion…