Most orgs already migrated; the work is mostly verifying the configuration and updating documentation to use modern naming.
- Audit current state
Setup, Outlook Integration and Sync. Confirm the integration is active. Check that EAC is the configured sync engine (not Lightning Sync, which is deprecated).
- Coordinate with the Microsoft 365 admin
The MS admin must approve the Salesforce add-in for the org. Without approval, users cannot install.
- Install the Outlook add-in
Users install via Microsoft 365 admin center or via the Outlook Add-ins menu. Most orgs deploy centrally so every user gets it automatically.
- OAuth Outlook to Salesforce
Users complete the OAuth handshake to grant the add-in read access to their Outlook mailbox.
- Verify EAC sync
Confirm activities flow into Salesforce automatically. Verify the activity feed on relevant records.
- Update internal documentation
Replace Lightning for Outlook references with Outlook Integration in admin docs and onboarding material.
- Salesforce for Outlook (the desktop sync client) was retired in 2024. Orgs still relying on it must migrate to Outlook Integration plus EAC.
- Microsoft 365 admin approval is the most common rollout blocker. Coordinate in advance.
- Lightning Sync is deprecated; EAC is the modern path. New deployments should use EAC.
- Inbox productivity features (send-later, tracking) require separate Inbox licensing; the basic Outlook Integration covers email logging.