Prepare Your Users to Continue Working with Lightning for Outlook and Lightning Sync When Salesforce Disables TLS 1.0
|Knowledge Article Number||000231407|
-- Note: Before Summer '16, Lightning for Outlook was known as Lightning For Outlook, and Lightning Sync was known as Exchange Sync. --
To comply with the latest industry standards surrounding TLS encryption, Salesforce is no longer supporting TLS 1.0 encryption protocol. Salesforce will stop responding to calls using TLS 1.0, and only to those using TLS 1.1 or 1.2. These changes require customers to ensure that their computing environments are compatible with TLS 1.1 or 1.2.
In addition, Lighting for Outlook and Lightning Sync users must take additional steps to continue using those products. To prepare your company, review the actions required from you below.
What action do I need to take for my users?
In addition to following those instructions, Lightning for Outlook and Lightning Sync users must take additional steps to continue working with those products. Below you’ll find a list of the TLS-compatible system requirements you’ll have to meet.
Lightning for Outlook
Winter ‘17 customers can test whether their Lightning for Outlook users are prepared for TLS 1.0 disablement by enabling the Critical Update Console (CRUC) setting.
Winter ‘17 customers can test whether their Lightning Sync users are prepared for TLS 1.0 disablement by enabling the Critical Update Console (CRUC) setting.
If you like, you can also test whether your users can sync their contacts and events after TLS disablement reaches your org. Log in to Salesforce and run the Lightning Sync Connection test. The connection test will fail if your version of TLS (or any other issue) is preventing Salesforce and Exchange from connecting.
When will Salesforce disable TLS 1.0 encryption?
Where can I get more information?