Microsoft Exchange Server Setup for the Outlook Integration

Set Up Exchange Without Public Exchange Web Services

If your Exchange server and Outlook versions support JavaScript API v1.8 or later, and you don’t use Inbox, you can set up the Outlook integration without public web services. A local EWS connection is still required between Outlook and Exchange, and the Exchange Metadata URL must still be publicly exposed.

Note This configuration is part of the Summer ‘21 release, available to instances on a rolling basis. Contact your Salesforce account representative for more details about your eligibility.

To determine which API version is available in each Outlook application, see the Microsoft Documentation about the JavaScript API.

If your Exchange server or Outlook versions support JavaScript API versions 1.4 through 1.7, you can still choose to set up the Exchange without public EWS. However, users lose the following features:

• Logging attachments directly from Outlook. Users can add attachments to logged emails in Salesforce.
• Inbox productivity features.

Set Up Exchange with Public Exchange Web Services

Important Using this setup ensures that Outlook users have access to all the features available in the integration.

Work with your IT professional to ensure that the Exchange server is set up to do the following things.

• Reach the Salesforce listing in Microsoft AppSource (All Versions of Outlook and Exchange)

  The Exchange server must be able to authorize calls to and from Business Apps - Microsoft AppSource. Choose whether the Exchange administrator sets up the integration add-in on users’ behalf or Outlook users get the add-in from the Store themselves. If users get the add-in themselves, they need access to the store. You can also choose to install the add-in using a file available for download from the Outlook Integration and Sync page in Salesforce setup.

• Accept incoming Exchange Web Services (EWS) calls from Salesforce

  Your internal company policies around Exchange determine what is required in your setup to ensure Exchange can accept incoming EWS calls from Salesforce. Steps can include:

  • Enabling an EWS endpoint (a common practice with on-premises servers)
  • Using AutoDiscover (optional)
  • If there’s a firewall, allowing incoming EWS calls to originate from Salesforce IP addresses and domains (allowlists). Valid calls contain json web tokens (JWT)

  Review the following for more information.

  • External Link: Start using web services in Exchange
  • Knowledge Article: Salesforce IP Addresses & Domains to Allow
  • External Link: Autodiscover service in Exchange Server
  • External Link: Inside the Exchange Identity token

• Accept incoming authentication calls to the Exchange Metadata URL from Salesforce

  The web tokens contain a MetaData URL. If you use Autodiscover to accept EWS calls, the MetaData URL could be same as the Autodiscover URL.

  

  Tip To check the Exchange server connection and confirm that it’s configured properly to communicate with the add-in, use the Salesforce Debug Tool. If you see 500 internal error responses, check Outbound Messaging SSL CA Certificates to ensure the certificate is valid.

Note A service account isn’t required for the Outlook integration. If you’re using Lightning Sync to sync calendar events and contacts, you could require a service account depending on your configuration.