How to Connect Salesforce to Outlook and Fix Common Setup Problems
By Eva Elekcha · October 28, 2026
Table of contents
- 1. Choose The Right Integration
- 2. Check Your Requirements First
- 3. Enable Outlook In Salesforce
- 4. Install The Salesforce Add In
- 5. Connect Your Salesforce Account
- 6. Open Salesforce Records In Outlook
- 7. Log Emails Manually
- 8. Set Up Automatic Activity Capture
- 9. Configure Calendar And Contacts
- 10. Resolve Common Connection Problems
- 11. Protect Customer Data And Access
- 12. Plan A Safe Company Rollout
- Frequently Asked Questions
1. Choose The Right Integration
How to connect Salesforce to Outlook depends on what you want the two applications to do.
For most organizations, the recommended starting point is Salesforce Outlook Integration, which lets users access Salesforce records from their Outlook inbox, associate emails with customer records, and create records without switching applications.
If you also want emails and calendar events to be captured automatically, you may need Einstein Activity Capture, which is configured separately.
Start by deciding whether you need to view Salesforce information in Outlook, log messages manually, synchronize activities automatically, or accomplish all three.
These are related capabilities, but they are not interchangeable.
Installing the Salesforce add in does not automatically mean every email, contact, and calendar event will synchronize with Salesforce.
The organization administrator must enable the appropriate features, configure access, and determine how activity data should be handled.
The standard Outlook integration is useful for sales representatives, account managers, customer support teams, and other employees who spend much of their working day in email.
When configured correctly, it can show relevant Salesforce records alongside an email conversation and make it easier to associate that conversation with a lead, contact, account, opportunity, or case.
For example, imagine a sales representative receives an email from a prospective customer asking for a revised proposal.
Without an integration, the representative might open Salesforce separately, search for the prospect, locate the opportunity, and manually record the conversation.
With the Outlook integration, the representative can open the Salesforce panel directly from Outlook, find the relevant record, and log the email against it.
Automatic activity capture addresses a different problem.
Instead of asking employees to log every supported email or calendar event individually, Einstein Activity Capture can capture qualifying activities and associate them with relevant Salesforce records according to its configuration.
This can reduce repetitive work, but administrators must understand the capture rules, data access arrangements, and reporting limitations before enabling it across a team.
There is also an important distinction between the current Outlook integration and the older Salesforce for Outlook desktop application.
Salesforce for Outlook is being retired, and Salesforce documentation directs customers toward its newer Outlook integration and Einstein Activity Capture products.
Salesforce currently identifies January 30, 2027, as the full retirement date for Salesforce for Outlook.
Organizations still using the older application should plan their migration rather than building new processes around it.
For most new deployments, the practical path is to confirm compatibility, enable the current integration in Salesforce, deploy the Salesforce add in through Microsoft Outlook, connect the user account, and then configure email or calendar activity capture if needed.
2. Check Your Requirements First
Before changing settings, confirm that your Salesforce organization, Outlook client, email environment, and user permissions support the integration.
This step prevents a common problem: installing the add in successfully, only to discover that the organization has not enabled the feature or that the required server configuration is incomplete.
Salesforce supports its Outlook integration with compatible editions of Salesforce and supported Microsoft email environments.
The exact requirements depend on the integration features you intend to use, the Salesforce edition, the Outlook version, and whether your organization uses Exchange Online or an on premises Exchange server.
Current Salesforce documentation lists supported environments that include Exchange Online with Microsoft 365 and specified versions of Exchange Server.
Supported Outlook clients include Outlook on the web and compatible desktop versions of Outlook for Windows and Mac.
Version requirements change, so administrators should check the current system requirements before deploying the add in to a large team.
You should also confirm that the user has an appropriate Salesforce license.
The Outlook integration is available across several Salesforce product editions, but additional features can require specific licenses or permissions.
Salesforce Inbox, for example, provides additional productivity capabilities beyond the standard integration.
Do not assume that purchasing or enabling one feature automatically grants access to every other feature.
Check these points before proceeding:
Confirm that the organization uses a supported Salesforce edition and experience.
Identify whether employee mailboxes are hosted in Exchange Online or an on premises Exchange environment.
Check the version of Outlook installed on each supported computer.
Confirm that users can sign in to Salesforce and have access to the records they need.
Identify whether the organization uses single sign on or a custom Salesforce domain.
Confirm who administers Microsoft 365, Exchange, and Salesforce.
Decide whether the deployment needs manual email logging, automatic activity capture, calendar synchronization, or additional Inbox capabilities.
The distinction between the Salesforce administrator and Microsoft administrator matters.
A Salesforce administrator can enable the integration in Salesforce, but may not have permission to deploy an Outlook add in across the company's Microsoft environment.
Similarly, a Microsoft administrator may be able to distribute the add in without having the Salesforce permissions required to activate the integration.
In a small business, one person may manage both systems.
In a larger organization, Salesforce administrators, Microsoft 365 administrators, security teams, and department managers may all have responsibilities.
If you are an ordinary employee rather than an administrator, you may not need to complete every configuration step yourself.
Your organization may already have enabled the integration and distributed the add in.
In that case, you can usually begin with the Outlook installation and account connection steps, provided your organization permits individual installation.
3. Enable Outlook In Salesforce
The Salesforce administrator must enable the Outlook integration before users can access Salesforce records through the Outlook add in.
Installing the add in alone does not activate the server side configuration.
Sign in to Salesforce with an account that has the required administrative permissions.
Open the Setup area using the gear icon in Salesforce Lightning Experience.
From Setup, use the Quick Find search box to locate Outlook Integration and Sync.
Select the corresponding settings page.
The page contains controls for enabling the integration and configuring related functionality.
Find the setting named Let users access Salesforce records from Outlook and enable it.
The wording and surrounding options can change as Salesforce updates its interface, so use the current setting label rather than relying on an older screenshot.
If your users access Outlook through a web browser, review the Microsoft Outlook Web App Domain section.
Salesforce provides a way to specify the Outlook web domains that users are permitted to use with the integration.
For Microsoft 365 environments, ensure the appropriate Outlook web domain is allowed.
Organizations using custom Outlook web domains must account for those addresses as well.
Save the configuration if the page requires you to do so.
At this stage, the organization has enabled the integration on the Salesforce side.
That does not necessarily mean every employee can already see it in Outlook.
The add in must also be installed or deployed, and users must authenticate with Salesforce.
If the Outlook Integration and Sync page is unavailable, do not immediately assume that the Salesforce service is broken.
Check your user permissions, organization edition, Salesforce experience, and whether the feature is available in the current environment.
Salesforce
Salesforce connects customer data, sales pipelines, service operations, marketing, and automation, giving businesses a configurable CRM platform for managing c…
- Comprehensive customer relationship management capabilities
- Flexible sales process configuration options
- Advanced features require higher subscriptions
- Total costs can increase substantially
An account without the required administrative permission may be unable to see or change the relevant settings.
Salesforce identifies Customize Application as the permission required to enable the Outlook integration.
In a controlled corporate environment, administrators should grant permissions through the organization's normal access management process rather than giving broad administrative privileges to every user.
After enabling the feature, test it with a small number of users before rolling it out company wide.
This allows the team to confirm that the add in loads, authentication works, and the required Salesforce records are accessible.
4. Install The Salesforce Add In
The Salesforce add in brings the integration into Outlook.
Salesforce recommends obtaining the add in through Microsoft AppSource or having the organization's Exchange or Microsoft 365 administrator deploy it centrally.
If your organization allows users to install Outlook add ins themselves, open the supported Outlook application and locate its add in or apps area.
The exact menu depends on the Outlook version and interface.
Search for Salesforce in the available add in catalog.
Select the official Salesforce add in and review the listing to ensure you are installing the correct application.
Follow the installation prompts.
In some Outlook versions, you may find add ins through the Home ribbon or an Apps menu.
Outlook on the web can present these controls differently from the desktop application.
If the menus do not match the instructions you have been given, check Microsoft's current documentation for your specific Outlook version.
Once the installation finishes, return to your inbox.
Open an email and look for the Salesforce control.
Depending on your Outlook version, it may appear in the ribbon, the message toolbar, the Apps menu, or another available location.
If you cannot install the add in, your company may restrict access to Microsoft AppSource or prevent individual users from adding applications.
This is common in organizations that control software deployment centrally.
Ask your IT department to deploy the Salesforce add in instead of attempting to bypass the restriction.
For larger organizations, centralized deployment is generally easier to manage.
An administrator can distribute the add in to selected users, groups, or the entire organization, depending on the available Microsoft deployment options and company policy.
Central deployment also gives IT a consistent way to manage the rollout.
Allow time for the deployment to reach users.
Microsoft notes that centralized deployment can take time to propagate, and the precise delay depends on the environment.
If a colleague can see the add in but you cannot, confirm that your account is included in the deployment assignment and that the rollout has completed.
Avoid installing unofficial tools that claim to connect Salesforce and Outlook unless your organization has evaluated and approved them.
A third party application may request access to email, contacts, calendars, or Salesforce records.
Those permissions can affect sensitive customer information and should be reviewed carefully.
The aim is to install the official integration supported by your organization, not simply any application that mentions Salesforce and Outlook.
5. Connect Your Salesforce Account
After the add in is available, connect it to your Salesforce account.
This step establishes the user identity that Outlook will use when accessing Salesforce data.
Open Outlook and select the Salesforce add in.
If it is not immediately visible, open an email message or check the available apps and add in controls.
Some Outlook layouts expose integrations only after a message is selected.
The Salesforce panel should open within Outlook.
If you are not already authenticated, the panel will prompt you to sign in.
Follow the displayed instructions and use your organization's approved Salesforce login method.
If your company uses single sign on, you may be redirected to the organization's identity provider.
Complete the authentication process using the normal company account.
Do not switch to a personal Salesforce account if your organization requires a work account.
Some organizations use a custom Salesforce My Domain address.
If the login process asks you to select a login type or enter a custom domain, use the address provided by your administrator.
Choosing the generic Salesforce login when your organization requires a custom domain can prevent the authentication process from completing correctly.
You may also encounter a consent or authorization screen.
Read the requested permissions and follow your organization's security policy.
If the sign in request looks unexpected, contact IT before approving it.
Once authentication succeeds, the Salesforce panel should become available in Outlook.
Depending on the features enabled and the email you have selected, it may display related Salesforce records or provide actions for creating or associating records.
Test the connection with an email that corresponds to a known Salesforce contact or lead.
Check whether the integration finds the expected record.
If it does not, verify that the record exists, that the email address is correct, and that your Salesforce user has permission to view the record.
A successful login does not mean every integration feature is active.
The add in can authenticate successfully while automatic email capture, event synchronization, or Inbox features remain unconfigured.
Test each required function separately.
If you have multiple Salesforce accounts or work across different Salesforce organizations, confirm that the panel is connected to the correct one.
Logging into the wrong organization can make records appear to be missing, even though the integration itself is working.
6. Open Salesforce Records In Outlook
Once connected, the Salesforce add in can help you work with customer information without leaving your inbox.
The exact set of actions available depends on the enabled features, user permissions, Salesforce configuration, and Outlook client.
When you select an email, the panel may identify Salesforce records associated with the sender or message.
These can include contacts, leads, accounts, opportunities, or cases, depending on the available data and configuration.
Suppose a customer emails you about a contract renewal.
The integration may help you locate the contact and related account, then open the opportunity associated with the renewal.
You can review the available context without manually searching through several Salesforce pages.
Matching is not always perfect.
A sender may use a different email address from the one stored in Salesforce.
A shared inbox may represent multiple people.
A prospect might have more than one record, or a duplicate contact may exist.
In these situations, inspect the record carefully before logging the message.
The add in can also support creating Salesforce records directly from Outlook.
Depending on the configuration, users may be able to create records such as contacts, leads, tasks, and other supported objects.
Administrators control which actions and components are available.
For example, if a new prospect sends an inquiry and no matching lead exists, an authorized user may be able to create the lead from the Outlook panel.
The user should check whether a record already exists before creating another one.
Duplicate records can create reporting problems, confuse ownership, and make future customer interactions harder to track.
The Salesforce panel can be particularly useful for teams that handle a high volume of customer correspondence.
It reduces the number of application switches required to find records, create tasks, or associate communications with customer activity.
However, access remains governed by Salesforce permissions.
The Outlook integration is not a way to bypass the organization's record sharing rules.
If a user cannot view a record in Salesforce, the integration should not be treated as a method for gaining access to it.
Administrators should test the integration using realistic examples from each team.
A sales representative, service agent, and account manager may need different record types and actions.
Configure the panel so that it supports the work employees actually perform instead of exposing every possible component.
7. Log Emails Manually
Manual email logging is useful when a user wants to choose exactly which conversations become part of a Salesforce record's activity history.
It is also a sensible starting point when an organization wants control over what is recorded before introducing automatic activity capture.
Open the relevant message in Outlook and launch the Salesforce add in.
Find the option to log or relate the email to Salesforce.
Depending on the interface, this may be labeled Log Email or appear as an action within the Salesforce panel.
Select the appropriate Salesforce record.
This could be a lead, contact, account, opportunity, case, or another supported record type.
The available options depend on the user's permissions and the organization's configuration.
Review the suggested match before confirming.
An email from a customer could relate to an existing contact and an active opportunity.
Logging the message against the wrong account may leave important information disconnected from the record that colleagues actually use.
If more than one record is relevant, check which relationships the interface allows.
Some configurations support relating an email to multiple records, while other actions may provide a more limited selection.
Follow the options displayed by the integration.
Confirm the logging action.
Then open the selected record in Salesforce and inspect its activity history or related activity timeline.
Verify that the email appears and that the sender, recipient, subject, and content are recorded as expected.
Email logging is particularly useful for important sales conversations, pricing discussions, renewal requests, customer complaints, and messages that establish commitments.
It allows the team to preserve the relevant business context instead of leaving it exclusively in one employee's mailbox.
Attachments require extra care.
The behavior depends on the integration settings, the email logging method, and the applicable Salesforce features.
If an attachment is important to the customer record, verify that it was included or stored through the approved process.
Do not assume that every file attached to an email will automatically be added to Salesforce.
Employees should also consider data minimization.
Not every internal message or personal conversation belongs in a customer record.
Log communications that are relevant to the business relationship and follow the organization's policies for sensitive data.
If the Log Email action is missing, confirm that the integration is enabled, that the user has the appropriate permissions, and that the email is open in a supported Outlook client.
Administrators should also check whether Enhanced Email and related settings are configured as required for the organization's chosen workflow.
8. Set Up Automatic Activity Capture
If your goal is to reduce manual work, consider Einstein Activity Capture.
This Salesforce feature can capture supported emails and calendar events and associate them with related Salesforce records according to the configured rules.
The distinction matters because the Outlook add in and automatic activity capture serve different purposes.
The add in provides an interface for working with Salesforce records from Outlook.
Salesforce
Salesforce connects customer data, sales pipelines, service operations, marketing, and automation, giving businesses a configurable CRM platform for managing c…
- Comprehensive customer relationship management capabilities
- Flexible sales process configuration options
- Advanced features require higher subscriptions
- Total costs can increase substantially
Einstein Activity Capture handles the automatic capture of supported activities, subject to the selected configuration and product capabilities.
Before enabling it, determine which users need capture, which email accounts are in scope, what types of activities should be captured, and how the resulting information will be shared.
These decisions affect privacy, access, and how much activity data is available to the organization.
A Salesforce administrator generally begins by assigning the required Einstein Activity Capture access through the appropriate permission set or license arrangement.
The administrator then opens Setup and searches for Einstein Activity Capture.
Select the relevant settings area and follow the guided configuration flow available in the organization.
The setup process can involve connecting the Microsoft environment, creating an activity capture configuration, selecting the capture and synchronization behavior, and assigning users to that configuration.
The exact steps and available options depend on the organization's Salesforce edition, licenses, and current product capabilities.
Administrators should review the rules that control which emails and events are captured.
Some configurations allow exclusions for specific people or companies.
Sharing settings can also influence which users are permitted to view captured activities.
Test the configuration before expanding it to the entire team.
Use representative test accounts and messages, then verify whether qualifying emails and calendar events appear in the expected Salesforce activity views.
Check both expected matches and cases that should be excluded.
Automatic capture can save time, but it should not be treated as a guarantee that every message is visible in every report, record, or export.
The storage method and reporting behavior can differ from activities logged manually.
Review the current Salesforce documentation to understand how captured data is stored and which reporting capabilities apply to the specific Einstein Activity Capture configuration.
If your organization depends on activity data for forecasting, compliance, auditing, or custom reporting, involve the Salesforce administrator and relevant business owners before changing the capture method.
A configuration that is convenient for individual sales representatives may not automatically meet every reporting or retention requirement.
9. Configure Calendar And Contacts
Connecting Salesforce to Outlook can involve more than email.
Some organizations also want contacts and calendar events to remain consistent between the two systems.
The right setup depends on whether you need automatic activity capture, bidirectional synchronization, or a more limited workflow.
Einstein Activity Capture can capture supported calendar events and associate them with Salesforce records.
The precise synchronization behavior depends on the configured features and current product rules.
It should not be assumed to provide identical contact and calendar synchronization behavior in every Salesforce edition.
Salesforce has also offered Lightning Sync for Microsoft Exchange, which was designed to synchronize contacts and events between Exchange and Salesforce.
However, Lightning Sync is a legacy option and is being retired.
Salesforce directs customers toward Einstein Activity Capture as the long term solution for supported email and calendar integration needs.
Check the current migration documentation before changing an existing setup.
Start by writing down the behavior you expect.
For example, should a meeting created in Outlook appear as an activity on a Salesforce opportunity?
Should an event created in Salesforce appear in an Outlook calendar?
Should contact updates flow in both directions, or should Salesforce remain the primary system for customer details?
These questions matter because activity capture and bidirectional synchronization are not the same thing.
Capturing a calendar event for Salesforce activity history does not necessarily mean that editing the Salesforce record will update the original Outlook event, or vice versa.
Review the event settings and available synchronization options in the current Salesforce setup.
Determine which users are included, which event types are supported, and how private or internal events are handled.
If the integration offers exclusion rules, configure them according to company policy.
Test the behavior with a small number of events.
Create a meeting in Outlook, associate it with a known customer where supported, and check whether the expected Salesforce record reflects the activity.
Then test any required flow in the opposite direction using the features actually available to your organization.
Avoid testing with sensitive personal appointments or confidential customer meetings.
Use approved test data so you can verify the behavior without exposing private information.
For contact synchronization, establish a clear rule about which application is authoritative for each field.
If employees can edit the same contact information in two systems, conflicts can occur.
A documented process helps prevent an old phone number or email address from overwriting a newer value.
Calendar and contact requirements should be confirmed before migration, especially for organizations still using older Salesforce integration products.
A careful inventory reduces the risk of losing expected behavior when the old setup is replaced.
10. Resolve Common Connection Problems
When Salesforce does not appear in Outlook, work through the problem in a consistent order.
Start with the simplest causes before changing server settings or reinstalling applications.
Salesforce is missing from Outlook.
Confirm that the add in has been installed and that your account is included in the organization's deployment assignment.
Open the Outlook add ins or Apps area and check whether Salesforce is available.
If your company uses centralized deployment, ask IT whether the rollout has reached your account.
The add in opens but will not sign in.
Check whether you can sign in to Salesforce through the browser.
If browser authentication also fails, the problem may involve your account, password, single sign on, or identity provider.
If browser login works but the add in fails, confirm whether your organization requires a custom Salesforce My Domain address and whether the supported Outlook client is being used.
Salesforce records do not appear.
Confirm that the sender's email address matches the information stored in Salesforce.
Check whether the contact or lead exists and whether your user has permission to view it.
A duplicate record or an alternate email address can prevent the expected match from appearing.
The Log Email option is unavailable.
Verify that the Salesforce integration is enabled and that the message is open in a supported Outlook client.
Ask the administrator to review the organization's integration configuration, relevant email settings, and your permissions.
Emails are not captured automatically.
Confirm that Einstein Activity Capture has been configured and that your user is assigned to the appropriate configuration.
Review the capture rules, connected Microsoft environment, and the type of email involved.
Automatic capture is separate from simply installing the Outlook add in.
Calendar events are missing.
Check whether the organization configured calendar activity capture or another supported synchronization feature.
Verify that the event type is included and that the event is associated with a relevant Salesforce record where required.
Review any rules that exclude private, internal, or otherwise unsupported events.
The add in loads slowly or displays an error.
Check whether Outlook and Salesforce are experiencing broader service issues, then restart the application and try again.
Confirm that the Outlook version and browser environment meet Salesforce requirements.
If the problem occurs only in Outlook on the web, ask IT to review the browser's cookie and tracking protection settings in line with Salesforce's current requirements.
Some employees have access but others do not.
Compare deployment assignments, Salesforce licenses, permission sets, and user access.
The add in may be available to one group while another group has not been included in the rollout.
Use a controlled test account to identify the difference rather than granting additional permissions indiscriminately.
The integration works in one Outlook version but not another.
Confirm the supported client versions and any organization specific restrictions.
Outlook for Windows, Outlook for Mac, and Outlook on the web may display add ins differently.
If the company uses older or perpetual Office versions, verify that the installed build meets the current Salesforce requirements.
When the issue remains unresolved, collect the relevant details before escalating it.
Record the Outlook version, operating system, Salesforce organization, error message, time of failure, and whether the problem affects one user or multiple users.
Do not include passwords, authentication tokens, or sensitive customer email content in a support ticket unless an approved secure process specifically requires it.
11. Protect Customer Data And Access
Salesforce and Outlook can contain personal information, customer correspondence, commercial negotiations, contracts, and other sensitive business data.
The integration should therefore be configured with the same care as any other system that connects email to a customer relationship management platform.
Begin with access control.
Users should have the Salesforce permissions required for their actual responsibilities.
The Outlook integration should not become a reason to give broad record access to employees who do not need it.
Next, review which activities are logged or captured.
Manual logging lets users choose specific emails, while automatic activity capture can bring a wider range of supported messages and events into the Salesforce activity experience.
The appropriate approach depends on the organization's needs, regulatory obligations, and internal policies.
Make sure employees understand what is captured and who can see it.
Sharing settings, Salesforce record permissions, product configuration, and storage behavior can all affect visibility.
Do not assume that an email is private simply because it was originally sent through Outlook.
Attachments also deserve attention.
A file attached to a customer email may contain financial details, personal information, credentials, or confidential documents.
Before logging or capturing it, follow the company's approved data handling policy and confirm where the file will be stored.
Retention requirements should be reviewed before an organization changes its integration.
Different storage and capture approaches may affect how activities are retained, searched, reported, exported, or deleted.
If the company has formal legal retention obligations, involve the relevant compliance and security teams.
Employees should be particularly careful with shared mailboxes.
A shared address may serve several departments, and automatically associating its emails with Salesforce records can expose information to people who would not otherwise have access.
Test shared mailbox behavior and permissions before enabling capture at scale.
Finally, establish a clear process for disconnecting users who leave the organization or change roles.
Remove access according to company policy, review assigned licenses, and confirm that account connections are handled appropriately.
This is part of normal identity and access management, not merely an Outlook configuration task.
A reliable integration should make relevant customer information easier to use without creating unnecessary exposure.
That requires clear ownership, appropriate permissions, transparent capture rules, and regular reviews.
12. Plan A Safe Company Rollout
A successful Salesforce and Outlook deployment involves more than enabling a setting and telling employees to install an add in.
Organizations should plan the rollout around the actual workflows, security requirements, and support capacity of each team.
Salesforce
Salesforce connects customer data, sales pipelines, service operations, marketing, and automation, giving businesses a configurable CRM platform for managing c…
- Comprehensive customer relationship management capabilities
- Flexible sales process configuration options
- Advanced features require higher subscriptions
- Total costs can increase substantially
Start with a small pilot group.
Include users who represent the main ways the company uses Salesforce, such as sales representatives, account managers, and service employees.
The pilot should test the actions those users perform every day, not just whether the panel opens.
Define a short set of acceptance tests.
Confirm that users can authenticate, find relevant Salesforce records, create records when permitted, manually log emails, and see the expected activities.
If automatic capture or calendar behavior is required, test those functions independently.
Document the intended workflow.
Employees should know when to log an email manually, when automatic capture applies, how to associate a message with the correct record, and whom to contact when something goes wrong.
Without this guidance, users may develop inconsistent habits that make Salesforce activity histories less useful.
Administrators should also decide how to support the integration after launch.
Assign an owner for Salesforce configuration, an owner for Microsoft deployment, and a process for investigating errors.
If a feature stops working after an update or policy change, the team should know where to start.
Measure whether the integration is achieving its intended purpose.
Useful indicators might include the percentage of relevant customer emails associated with Salesforce records, the frequency of duplicate record creation, the number of support requests, and employee feedback about the time required to complete routine tasks.
Avoid collecting unnecessary personal data just to measure adoption.
Do not enable every available feature at once simply because it is available.
A team that only needs to log selected sales emails may not need automatic capture across every mailbox.
Another team may benefit from calendar activity capture but have no requirement for additional Inbox features.
Configure the minimum capability that meets the documented need, then expand only when there is a clear reason.
If your organization is replacing Salesforce for Outlook, create a migration plan before the retirement deadline.
Inventory the existing workflows, identify which features need replacements, test the new integration, train users, and confirm that historical activity data remains accessible as required.
The current Salesforce for Outlook retirement schedule makes this planning particularly important for organizations still using the older application.
Once the integration is deployed, review it periodically.
Changes to Outlook versions, Microsoft security policies, Salesforce permissions, licenses, and product capabilities can affect how the integration behaves.
A short scheduled review is easier to manage than discovering months later that key activities are no longer being captured.
Connecting Salesforce to Outlook is straightforward when the organization enables the right integration and users follow the correct setup process.
Start with the official Salesforce add in, confirm that authentication and record access work, and test manual email logging before introducing automatic activity capture or calendar synchronization.
For a company wide deployment, involve both Salesforce and Microsoft administrators, review data access requirements, and test the intended workflows with a pilot group.
Organizations still using Salesforce for Outlook should prioritize migration planning before the legacy product reaches retirement.
URLS CONSULTED
- Set Up the Integration with Outlook, Salesforce Help
- Turn On the Outlook Integration in Salesforce, Salesforce Help
- Get the Outlook Integration via the Salesforce Add In, Salesforce Help
- Salesforce and Microsoft Outlook Integration Products, Salesforce Help
- Outlook Integration System Requirements, Salesforce Help
- Roles Required to Set Up the Outlook Integration, Salesforce Help
- Deploy the Outlook Integration to Users, Salesforce Help
- Set Up the Outlook Integration and Einstein Activity Capture, Salesforce Trailhead
- Outlook Integration and Outlook Integration with Inbox, Salesforce Help
- Roll Out Einstein Activity Capture to Your Testers or Users, Salesforce Help
- Guidelines for Setting Up the Outlook Integration, Salesforce Help
- Verify That You Meet the Next Generation Product Requirements, Salesforce Help
