Salesforce’s Outlook integration connects Microsoft Outlook and Microsoft 365 to Salesforce in two ways: a sidebar add-in that surfaces CRM data inside Outlook and enables record creation without leaving email, and Einstein Activity Capture (EAC) which automatically syncs emails and calendar events to Salesforce without any manual logging. Salesforce for Outlook – the legacy desktop application – is retired as of 2025, so any organisation still using it must migrate to the current browser-based integration. This guide covers setup for both the Outlook Integration add-in and Einstein Activity Capture, the differences between them, and how to troubleshoot the most common configuration problems.
The best guide is the one that makes the inbox feel connected to the CRM.
A useful explanation should help the reader see how the tools work together.
That means the guide should focus on everyday workflow rather than just the technical connection.
For many teams, the value is in keeping communication tied to customer records and deal activity.
It should also show how the setup improves visibility without adding unnecessary manual steps.
A good guide should explain what the connection helps with and why email activity matters in sales work.
That makes the integration a practical productivity move rather than a cosmetic one.
Salesforce Outlook integration is useful because many teams still live in email and calendar tools while working inside a CRM. Connecting Outlook with Salesforce helps reduce context switching and makes communication easier to track.
The Two Components: Add-In vs Einstein Activity Capture
Many administrators confuse the Salesforce Outlook Integration add-in with Einstein Activity Capture – they are separate features that work together but serve different purposes:
- Salesforce Outlook Integration add-in: a Microsoft Office add-in (visible as a Salesforce panel inside Outlook) that allows users to view related CRM records alongside emails, manually log emails to Salesforce records, and create new Contacts, Leads, Opportunities, Cases, and Tasks from within Outlook. Requires user action – reps click to log emails or view records.
- Einstein Activity Capture (EAC): an automatic background sync that continuously captures all emails sent and received between a connected Outlook account and CRM contacts, and syncs Outlook calendar events to Salesforce. Requires no user action after initial setup – emails and meetings are logged automatically. Included with Sales Cloud Enterprise and above.
Most Salesforce orgs deploy both together: EAC handles automatic background logging, and the Outlook Integration add-in gives reps the contextual sidebar for viewing and creating CRM records from within email.
Prerequisites and Admin Requirements
Before configuring the Salesforce Outlook integration, confirm these prerequisites are in place:
- Salesforce edition: Outlook Integration add-in available from all editions. Einstein Activity Capture (automatic sync) requires Sales Cloud Enterprise or above, or a separate EAC licence for lower editions.
- Microsoft 365 subscription: the add-in requires Microsoft 365 (Exchange Online). On-premises Exchange Server (Exchange 2016/2019) is supported with limitations – confirm your Exchange version with your IT team.
- Enhanced Email: must be enabled in Salesforce before email logging works. Setup ? Activity Settings ? Enable Enhanced Email. This converts EmailMessage from a Task subtype to a standalone object, enabling richer email threading and reporting.
- Microsoft 365 admin permissions: deploying the Salesforce add-in organisation-wide requires a Microsoft 365 Global Administrator to approve the add-in in the Microsoft 365 Admin Centre. If reps are installing it individually from Microsoft AppSource, this is not required – but organisation-wide deployment is recommended for consistency.
Step 1: Enable the Outlook Integration in Salesforce Setup
- Go to Setup ? Outlook Integration and Sync (or search “Outlook Integration” in Setup Quick Find)
- Toggle Let users access Salesforce records from Outlook to On
- Under Outlook Integration Settings, configure:
- Enable Use Salesforce from Outlook: the core add-in functionality
- Enable Allow users to relate emails to records without logging them: lets reps associate an email with a Salesforce record and view the record without writing the email to Salesforce’s server – useful for sensitive email content
- Enable Log Emails to Salesforce: controls whether users can manually log email messages as EmailMessage records on related Contacts, Leads, or Opportunities
- Assign the Standard Salesforce Inbox permission set (or a custom permission set including the Outlook Integration permission) to users who should have access to the integration
Step 2: Deploy the Outlook Add-In
Option A: Organisation-Wide Deployment (Recommended)
- Log into the Microsoft 365 Admin Centre (admin.microsoft.com) as a Global Administrator
- Navigate to Settings ? Integrated Apps ? Add apps
- Search for “Salesforce” and select the Salesforce add-in from the Microsoft AppSource catalogue
- Configure deployment scope: deploy to All Users, specific Groups (your Salesforce users’ M365 group), or specific users by email address
- Accept the permissions the add-in requests and complete the deployment
- The Salesforce panel appears in Outlook (desktop, web, and mobile) for all deployed users within 24 hours – no user action required
Option B: Individual User Installation
Users can install the Salesforce add-in individually from Microsoft AppSource (appsource.microsoft.com, search “Salesforce”) or from within Outlook: Home tab ? Get Add-ins ? search “Salesforce.” After installation, users connect their Salesforce account by clicking the Salesforce panel icon and completing the OAuth authorisation flow.
Step 3: Configure Einstein Activity Capture
- In Salesforce Setup, navigate to Einstein Activity Capture Settings (search in Quick Find)
- Toggle Einstein Activity Capture to On
- Under Configuration, create an Activity Capture Configuration:
- Name the configuration (e.g., “Sales Team Activity Capture”)
- Select Microsoft Exchange as the email service
- Configure Sync Direction for Email: Salesforce and Email Application (bidirectional – emails logged to Salesforce AND Outlook shows sent emails as logged), or Email to Salesforce only
- Configure Sync Direction for Events: Salesforce and Email Application (calendar events sync both ways – Outlook events appear in Salesforce, Salesforce events appear in Outlook calendar)
- Configure Email sharing settings: Everyone (all users with sharing access to the related Contact can see the email), or Internal Only (only the email participant and Salesforce admins can see the email content)
- Assign the configuration to users (or user profiles) who should have Activity Capture enabled
- Users connect their Outlook account: the first time they open the Salesforce add-in in Outlook, they are prompted to connect their Exchange account via OAuth – they click Connect and authorise Salesforce to access their email and calendar
How Einstein Activity Capture Matches Emails to Records
EAC automatically matches emails to Salesforce records using email addresses – when an email is sent to or received from an address that matches a Contact or Lead in Salesforce, the email is logged as an EmailMessage on that Contact’s or Lead’s activity timeline.
Matching logic:
- Direct match: the email address matches the Email field on a Contact or Lead record
- Related records: if the Contact is related to an Account or has open Opportunities, the email also appears on those related records’ activity timelines (configurable)
- No match: emails to addresses not in Salesforce are not logged – they are captured but held in a buffer. Users can manually match and log unmatched emails from the add-in panel.
- Multiple matches: if the same email address exists on multiple records (a known duplicate issue), EAC logs to all matched records
Einstein Activity Capture Data Storage Considerations
Emails and events captured by EAC are stored in Salesforce’s Activity Capture data store – not in standard Salesforce storage (Salesforce’s 10GB standard storage does not include EAC data). EAC data is retained for 24 months by default, after which older items are removed from the activity timeline. This is a key difference from manually logged emails, which are stored in standard Salesforce storage and retained indefinitely.
If your organisation requires permanent email logging (for compliance, legal discovery, or CRM audit trail purposes), supplement EAC with manual email logging for critical conversations, or evaluate Salesforce Inbox or a third-party archiving tool that stores email content in standard Salesforce objects.
Privacy Considerations
Einstein Activity Capture syncs all emails between a connected Outlook account and matched Salesforce contacts. This creates privacy considerations administrators must communicate to users before deployment:
- Personal emails sent from a business account to a contact who happens to be in Salesforce are logged to that contact’s record
- HR-sensitive emails between managers and employees who are Salesforce contacts are logged if the email addresses match
- Legal correspondence may be inadvertently captured
Configure Excluded Email Addresses in EAC Settings to prevent specific email addresses (HR team, legal counsel, executive assistants) from triggering Activity Capture logging. Users can also temporarily exclude specific email threads using the Salesforce add-in panel.
Emails not appearing on Salesforce records
- Verify Enhanced Email is enabled (Setup ? Activity Settings)
- Check that the email address on the Contact/Lead matches the exact email address of the correspondent – including domain capitalisation and alias differences
- Confirm the user’s EAC connection is active: Setup ? Einstein Activity Capture Settings ? Connected Accounts – look for the user’s account status
- Allow up to 30 minutes for newly sent/received emails to sync from Outlook to Salesforce
Salesforce panel not appearing in Outlook
- Confirm the add-in is deployed via Microsoft 365 Admin Centre – check Integrated Apps for deployment status
- In Outlook, go to Home ? Get Add-ins ? My Add-ins to confirm Salesforce appears and is enabled
- For Outlook desktop: ensure Outlook is version 16.0+ (2016 or later) – older Outlook versions do not support web add-ins
Calendar events not syncing
- Verify bidirectional sync is enabled in the EAC Configuration for Events
- Check that the event is not excluded by EAC filters (events marked as private in Outlook are not synced by default)
Salesforce Inbox: The Premium Email Add-On
Salesforce Inbox is a separate paid add-on (approximately $25/user/month) that extends the Outlook integration with additional capabilities:
- Email open and link click tracking: real-time notifications when a recipient opens your email or clicks a link – visible in the Outlook sidebar when the email is tracked
- Scheduling links: insert a scheduling link (backed by your Salesforce calendar) directly in email – recipients book a meeting without email back-and-forth
- Email templates in Outlook: access Salesforce email templates from within the Outlook compose window – merge fields populated from the related Salesforce record
- Einstein Email Insights: AI-powered suggestions in the Outlook sidebar – next best action recommendations, deal risk alerts, and follow-up reminders
Inbox is most valuable for high-volume external email senders (SDRs, AEs with large prospect volumes) who benefit from open tracking and scheduling links in their daily outbound workflow.
How long does it take to see ROI from Salesforce?
Most organizations see measurable ROI from Salesforce within 6-12 months of go-live, assuming the implementation was done correctly and adoption is active. Early wins typically come from pipeline visibility (fewer deals falling through the cracks) and time savings from automation (fewer manual follow-up reminders). Larger ROI gains – from better forecasting accuracy, improved win rates, and shorter sales cycles – typically take 9-18 months as the system accumulates enough data to reveal patterns. Companies that invest in change management alongside the technical implementation consistently reach ROI faster than those that treat it as a pure software deployment.
What’s the biggest mistake companies make with Salesforce?
The most common mistake is configuring Salesforce to match a generic best-practice template rather than the company’s actual sales process. When the CRM doesn’t reflect how the team works, reps build workarounds and CRM usage becomes performative – they update it because they have to, not because it helps them. The second most common mistake is under-investing in data quality from the start. Importing dirty, duplicate, or incomplete data as a “we’ll clean it up later” plan almost never results in cleanup – the bad data compounds and eventually undermines trust in the system.
How many users does Salesforce work well for?
Salesforce scales from individual users to enterprise organizations with thousands of seats, though the right tier and configuration differs significantly by team size. Small teams (under 10 users) benefit most from simplicity – stick to standard features, avoid over-customization, and prioritize adoption over sophistication. Mid-market teams (10-100 users) need more process definition, automation, and reporting structure. Enterprise implementations require dedicated admin resources, governance policies, and often external implementation support. Match the complexity of your Salesforce setup to the maturity and size of your team.
Can Salesforce integrate with our existing tools?
Most modern CRM platforms including Salesforce offer native integrations with common business tools – email clients (Gmail, Outlook), calendar apps, marketing platforms, support desks, and accounting software. For tools without native connectors, middleware platforms like Zapier, Make, or dedicated integration tools fill the gap. Before assuming an integration is available, verify whether it’s native (built and maintained by the CRM vendor), partner-built (listed on their marketplace but maintained by a third party), or middleware-dependent (requires Zapier or similar). Native integrations are generally more reliable and require less maintenance than middleware-based connections.
The best integration setup is the one that keeps email activity visible without extra effort. If the connection is clumsy, the benefit drops quickly.
Troubleshooting Common Issues
Problem: Configuration Completed Without Documenting the Setup
Salesforce configurations built without documentation create fragility – when the admin who set it up leaves or is unavailable, nobody understands why things are configured the way they are. Undocumented customizations, workflows, and field choices become institutional knowledge that walks out the door. Fix this by maintaining a living configuration document that records every non-default setting: custom fields and their purpose, automation rules and their trigger logic, permission sets and who holds them. Store it in a shared location and update it whenever the configuration changes.
Problem: Team Adoption Stalls Because Training Was One-Time Only
Organizations that run a single training session at launch and then leave users to figure things out on their own see adoption rates decline within 60 days as habits revert to spreadsheets and email threads. New hires get no structured Salesforce training at all. Fix this by building a recurring training cadence: a 30-minute monthly “tips and tricks” session for the whole team, a structured onboarding checklist for new users (covering the 10 most common tasks), and recorded walkthrough videos for each role stored in a shared knowledge base. The best-adopted Salesforce implementations treat training as a continuous program, not a one-time event.
Problem: Reports Built for Management Don’t Help the Frontline Team
Most Salesforce dashboards are designed to give managers visibility into team metrics – pipeline totals, activity counts, conversion rates. Reps who only see management-facing reports get no personal value from the CRM, which reduces their motivation to keep data clean and current. Fix this by building personal dashboards for each user role: a rep sees their own pipeline, their overdue activities, and their win rate this quarter versus last quarter. When individual contributors see Salesforce as a tool that helps them close more deals rather than just a reporting layer for management, data quality improves significantly.