Every Salesforce sales org eventually asks the same question: how do we get email and calendar activity into the CRM without making reps log it by hand? The answer used to be Salesforce for Outlook, then Lightning Sync. Both are gone or going. Today the supported path is the Outlook integration add-in working alongside Einstein Activity Capture, and deploying it well is an admin project on two platforms at once.
That is where most deployments stumble. The Salesforce side is configured, but nobody talked to the Microsoft 365 tenant admin. Or the tenant consent is granted, but sync filters are wrong and private events start appearing on records. A clean deployment needs a checklist that covers both sides, plus a rollout plan that does not turn day one into a support ticket storm.
This guide is that checklist: what the pieces are, what changed, how to configure Microsoft and Salesforce in the right order, and how to roll out at scale.
To connect Salesforce with Outlook and Microsoft 365, deploy two components: the Outlook integration (an add-in that puts Salesforce records in the Outlook side panel) and Einstein Activity Capture (which automatically syncs emails, events, and contacts). The Microsoft 365 tenant admin grants org-wide consent for the Microsoft Graph permissions Salesforce needs, the Salesforce admin configures sync direction, filters, and user assignments, and users either connect their own accounts or are connected centrally depending on the authentication model. Vantage Point helps organizations plan this deployment so security, sync scope, and user rollout are settled before anyone clicks connect.
The phrase "Salesforce Outlook integration" actually covers several distinct tools, and conflating them causes bad purchasing and configuration decisions:
| Component | What it does | Who it is for |
|---|---|---|
| Outlook integration add-in | Puts Salesforce records and actions in an Outlook side panel; reps can log emails manually and see CRM context while reading mail | Teams that want rep-controlled logging and in-inbox CRM access |
| Einstein Activity Capture | Automatically captures emails, events, and contacts from Microsoft 365 and surfaces them on related Salesforce records | Teams that want activity in CRM without rep effort |
| Salesforce for Teams | Brings Salesforce records into Microsoft Teams conversations | Orgs standardized on Teams for collaboration |
| Files Connect | Surfaces SharePoint and OneDrive documents inside Salesforce | Orgs storing documents in Microsoft 365 |
Most sales deployments mean the first two. The add-in gives reps control; Einstein Activity Capture gives the organization completeness. Planning for only one of them is the most common scoping error.
Two retirements reshaped this space. Salesforce for Outlook, the old desktop add-in, was retired first. Lightning Sync, the background engine that synchronized contacts and events, followed it into retirement, with Salesforce directing customers to Einstein Activity Capture as the replacement. Our Lightning Sync migration guide covers the transition details for orgs still moving.
The practical consequence: if your documentation, onboarding materials, or admin runbooks reference either legacy tool, they are describing infrastructure that no longer exists. New deployments should be designed around the Outlook integration plus Einstein Activity Capture from the start.
Salesforce talks to mailboxes through Microsoft Graph, and Microsoft takes the consent for that seriously. Before any Salesforce configuration matters, a tenant admin must grant the permissions Salesforce requests. The admin granting consent needs to hold a Global Admin, Cloud Application Admin, or Application Admin role in Microsoft Entra ID.
Two decisions belong to the Microsoft side:
Get the Microsoft admin into the first planning meeting. Deployments stall for weeks when Salesforce admins discover the tenant consent requirement after everything else is done.
Once consent exists, the Salesforce admin configures how capture behaves. The settings that matter most:
Treat the rollout as three waves:
One more expectation to set early: captured activity behaves differently from standard Salesforce records. Emails captured by Einstein Activity Capture are stored in Salesforce's activity platform rather than as fully editable, reportable Task records, which has real consequences for reporting and automation. Understand that model before promising anyone a report on captured email volume.
| Mistake | Symptom | Fix |
|---|---|---|
| No tenant admin involvement | Users cannot connect; consent errors | Get Entra admin consent first |
| Sync scope never decided | Private events or noise on records | Document direction, filters, and privacy before pilot |
| Expecting historical backfill | "Where are my emails from last year?" | Set the lookback-window expectation up front |
| Big-bang rollout | Support storm on day one | Pilot, then waves by team |
| Treating captured data like standard records | Reports and edits that do not work | Learn the activity-platform storage model first |
Vantage Point is a Salesforce Solutions Partner that deploys email and calendar integration as part of broader Salesforce implementation and advisory work. Senior consultants only — no junior handoffs; the experts you meet are the experts who deliver. We coordinate the Microsoft 365 and Salesforce configuration together, define sync policy with your security team, and stage the rollout so adoption sticks. For orgs that want the integration monitored and tuned after go-live, our managed services team handles that as ongoing support.
Get the consent model, sync scope, and rollout waves right before the first user connects. Vantage Point can design the deployment and run the pilot with you. Talk to Vantage Point about your Salesforce deployment.
The replacement is a combination of the Outlook integration add-in, which surfaces Salesforce records inside Outlook and supports manual logging, and Einstein Activity Capture, which automatically captures and syncs email, calendar, and contact activity. Lightning Sync, the older sync engine, has also been retired in favor of Einstein Activity Capture.
It depends on the authentication model. With org-level consent, a Microsoft 365 tenant admin approves Salesforce once and users are connected centrally. With user-level authentication, each user connects their own Microsoft account. Security policy usually dictates which model you use.
At minimum, a Salesforce admin and a Microsoft 365 admin holding a Global Admin, Cloud Application Admin, or Application Admin role in Entra ID. The tenant admin grants the Microsoft Graph permissions Salesforce needs, and the deployment cannot proceed without that consent.
Initial capture covers a limited recent window, roughly the last 30 days of activity. Einstein Activity Capture is designed for ongoing capture, not historical migration, so set that expectation with users before rollout.
Yes. Sync configuration includes filters for private events and control over what message content is captured. Decide and document these settings before the pilot, because employees will ask about privacy as soon as the integration is announced.
Einstein Activity Capture stores captured emails and events in Salesforce's activity platform rather than as standard Task or Event records. They surface in timelines and activity views but are not fully editable or reportable like standard records, which is a deliberate part of the product's design.
A Salesforce consulting partner like Vantage Point can plan the consent model, configure sync settings and filters, and run a phased rollout. Getting both the Microsoft and Salesforce sides configured in the right order is what separates a two-week deployment from a two-month one.