You are here:
Tell Reps How to Sync Microsoft® Contacts with Salesforce
It’s time for Salesforce admins to tell their sales reps to manage the Microsoft contacts that reps want to sync with Salesforce.

Use more general search terms.
Select fewer filters to broaden your search.
You are here:
It’s time for Salesforce admins to tell their sales reps to manage the Microsoft contacts that reps want to sync with Salesforce.
| Available to sync records from: Salesforce Classic, Lightning Experience, and the Salesforce mobile app |
| Available to set up from: Salesforce Classic and Lightning Experience |
| Available in: Professional, Enterprise, Performance, Unlimited, and Developer Editions with Sales Cloud, Service Cloud, and Lightning Platform |
If you’ve set up reps to sync contacts from only Salesforce to Microsoft Exchange, you can skip this step: Reps’ contacts and events are already syncing.
Reps set up to sync contacts from Exchange to Salesforce or sync both ways can kick off sync by choosing which Microsoft contacts sync to Salesforce. If you’ve set up reps to sync both ways, we recommend that you or your reps create relevant Salesforce accounts before you roll out contact sync. Otherwise, if reps don’t resolve unmatched Salesforce contacts before the next sync cycle, Lightning Sync removes the company from Microsoft contacts.
After you define reps’ sync settings by adding them to active Lightning Sync configurations, Lightning Sync creates a folder called Salesforce_Sync within each reps’ email account. Lightning Sync nests Salesforce_Sync within reps’ Contacts directories.
Reps choose the contacts that sync by moving those contacts into the Salesforce_Sync folder. When reps can see and access the Salesforce_Sync folder in their email application, they can start moving contacts into it.

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.