Salesforce Inbox and Outlook Integration (OI) do not support Outlook.com email addresses (for example, user@outlook.com, user@hotmail.com, or user@live.com). This is because Outlook.com does not support the Exchange Web Services (EWS) protocol, which is required for Salesforce Inbox and Outlook Integration to connect to and retrieve email and calendar data.
Exchange Web Services (EWS) is a Microsoft API that allows Salesforce to communicate with Microsoft Exchange servers to read email, sync calendar events, and enable features like Send Later and Insert Availability.
Although the initial login to the Outlook Integration Side Panel may appear successful, the backend cannot grant access to email or calendar from an Outlook.com account using EWS. When the user switches to another email, Salesforce Inbox or Outlook Integration logs the user out because it cannot establish a valid EWS connection.
Outlook Integration System Requirements
This is a known platform limitation with no workaround via Outlook Integration.
## Root Cause
On the backend, EWS connections to Outlook.com accounts return a ResponseCode 401 — Unauthorized error. This prevents all Inbox features — including Send Later and Insert Availability — from functioning because they all depend on connecting to an Exchange server using the EWS protocol.
## Impact on Salesforce Inbox Features
All Salesforce Inbox features that depend on EWS connectivity are unavailable when using an Outlook.com email address:
## Recommended Action
Users must connect Salesforce Inbox or Outlook Integration using a corporate Microsoft Exchange or Microsoft 365 (Office 365) email account. Personal Outlook.com, Hotmail, and Live accounts are not supported.
If the user's organization requires use of Outlook.com addresses, refer them to the Outlook Integration System Requirements article for supported email configurations.
000380485

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.