help.salesforce.com Open in urlscan Pro
2600:1408:9000::1730:24e8  Public Scan

Submitted URL: http://click.mail.salesforce.com/?qs=eyJEZWtJZCI6ImVtY19kZWtfdjEiLCJEZWtWZXJzaW9uIjoxLCJJdiI6Imd1ZmFLckdMM2V5am91ejhrVWxCbGc9PSIs...
Effective URL: https://help.salesforce.com/s/articleView?language=en_US&id=002723592&type=1&utm_source=techcomms&utm_medium=email&utm_campa...
Submission: On October 03 via api from US — Scanned from US

Form analysis 1 forms found in the DOM

POST

<form id="fileUploadForm" enctype="multipart/form-data" method="post" target="fileUploadIframe"><input type="file" id="fileSelector" name="file" style="display: none;"><input name="filename" type="hidden"></form>

Text Content

Loading
×Sorry to interrupt
This page has an error. You might just need to refresh it. [PromiseRejection:
[object Object]]

Refresh


MICROSOFT UPDATING SALESFORCE OUTLOOK INTEGRATION 2024

Publish Date: Oct 1, 2024
Description

 As a part of its Secure Future Initiative, Microsoft is deprecating legacy
features that will impact the Salesforce Outlook integration in the coming
months. This Knowledge Base article outlines steps that Microsoft 365 (M365)
admins must take to support Salesforce admins in ensuring that they maintain
access to their Salesforce Outlook integration as the feature is updated in 2024
and 2025. Salesforce admins will not have the required permissions/access to
make these changes. M365 admins must execute these steps before Exchange Online
tokens are turned off in the tenant. Failure to do so could prevent users from
being able to access the Salesforce Outlook integration.

 Please refer to the official Microsoft documentation, available here, for more
information including timelines based on which channel(s) customers are using.
While we encourage customers to work on implementing these changes immediately,
any questions related to the exact timing for the milestones outlined should be
directed to M365 admins. 

 * When reviewing the documentation outlined above, there are two key milestones
   to be mindful of: 
   
   * Date when Microsoft turns off Exchange Online tokens for all tenants. At
     this point, an admin will be able to re-enable Exchange tokens for a tenant
     or a specific add-in.
   
   * Date when Microsoft removes the option to re-enable Exchange tokens. At
     this point, if an admin has not taken the actions outlined in this
     Knowledge Base article, it’s possible that users will no longer be able to
     access the integration.

The following actions should be taken before Exchange Online tokens are turned
off in the tenant:

 * ACTION 1 (required): Verify that M365 is not configured with policies that
   will prevent the Outlook integration from working after Exchange Online
   tokens are turned off in the tenant. Please note that failure to do so could
   prevent all users from accessing the Outlook integration.
   
   * The following scopes are required in order for the Salesforce Outlook
     integration to function:
     
     * Calendars.ReadWrite.Shared
     
     * email
     
     * Mail.ReadWrite.Shared
     
     * offline_access
     
     * openid
     
     * profile
     
     * User.Read
   
   * For example, if Calendars.ReadWrite.Shared is unavailable to all
     integrations, the Salesforce Outlook integration will not function.

 * ACTION 2 (suggested and COMING SOON): We are developing an Admin Consent Flow
   (details from Microsoft) which will automate the scope authorization process
   for all users in an account’s tenant so that individual users do not have to
   manually authorize the integration after Microsoft rolls out changes. This
   feature is currently unavailable but will be released soon. We will update
   this section of the Knowledge Base article when it is live.
   
   * While not required, this step will make the migration more seamless for end
     users, and alleviate confusion that may come from prompting a user to
     authenticate the application.
   
   * Authorize the integration for all users in the tenant by clicking on the 
     “Outlook Integration and Sync” page in Setup.

Customers can also proactively test in advance of the deadlines.

 * In order to test, customers can take the following actions before changes are
   rolled out: 
   
   * Authorize the Salesforce Outlook integration for users in the tenant using
     the Admin Consent Flow (please see the details from Microsoft).
   
   * Manually turn off Exchange Online tokens. Microsoft will be adding this
     capability in October 2024.  Latest timeline and updates can be found in
     the Microsoft FAQ here.
   
   * Launch the Outlook integration, verify the Microsoft authorization and
     Salesforce authentication flow, then verify users can access the
     application as expected.  

Knowledge Article Number

002723592

Did this article solve your issue?
Let us know so we can improve!
YesNo
 
1-800-667-6389
 * 
 * 
 * 
 * 

SALESFORCE
 * Privacy Statement
 * Security Statement
 * Terms of Use
 * Participation Guidelines
 * Cookie Preference Center
 * Your Privacy Choices

COMMUNITY
 * AppExchange
 * Salesforce Admins
 * Salesforce Developers
 * Trailhead
 * Training
 * Trust

SUPPORT & SERVICES

Need help? Find more resources or connect with an expert.

Get Support

Powered by Experience Cloud

--------------------------------------------------------------------------------

© Copyright 2024 Salesforce.com, inc. All rights reserved. Various trademarks
held by their respective owners.
Salesforce, Inc. Salesforce Tower, 415 Mission Street, 3rd Floor, San Francisco,
CA 94105, United States


English
Select Org
 * Select OrgEnglish
 * Français
 * Deutsch
 * Italiano
 * 日本語
 * Español (México)
 * Español
 * 中文(简体)
 * 中文(繁體)
 * 한국어
 * Русский
 * Português (Brasil)
 * Suomi
 * Dansk
 * Svenska
 * Nederlands
 * Norsk

Live chat:Let's Chat


Loading



COOKIE CONSENT MANAGER




 * GENERAL INFORMATION


 * REQUIRED COOKIES


 * FUNCTIONAL COOKIES


 * ADVERTISING COOKIES

GENERAL INFORMATION

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

Always Active

Required cookies are necessary for basic website functionality. Some examples
include: session cookies needed to transmit the website, authentication cookies,
and security cookies.

Cookies Details‎

FUNCTIONAL COOKIES

Functional 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.

Cookies Details‎

ADVERTISING COOKIES

Advertising Cookies


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.

Cookies Details‎
Back Button


COOKIE LIST

Filter Button
Consent Leg.Interest
checkbox label label
checkbox label label
checkbox label label

Clear
checkbox label label
Apply Cancel
Save Settings
Accept All Cookies