Protocols and Components TLS versus SSLīefore going further, let us take a moment to clarify TLS and SSL in case they are unfamiliar terms. We are seeing an uptick in requests for guidance related to this date and want to assure you we have the guidance underway. In addition to the Office 365 announcement, we know there are customers interested in this topic due to the PCI DSS 3.1 that currently has an effective date of June 30 th, 2018. Part 3: Disabling TLS 1.0 and TLS 1.1 as well as how to run a TLS 1.2-only Exchange Server deployment aligned with Office 365’s configuration. Part 2: Enabling and confirming TLS 1.2 is operational in supported Exchange Server deployments. What you need to be ready for TLS 1.2 being enabled.
Today, in part 1 of this series we will provide you with the information required to prepare your environments for using TLS 1.2, as well as, what our plans are during the next few weeks. It only means TLS 1.2 must be enabled and used when communicating with Office 365. For clarity, this does not mean your on-premises deployments must disable TLS 1.0/1.1 by the time Office 365’s change takes place. By the time you are reading this article you may have learned Office 365 intends to stop accepting inbound network connections if they are using TLS protocol versions prior to TLS 1.2, and started to wonder how this may affect your on-premises deployments of Exchange Server.
OverviewĪs the realm of security in technology continues to evolve over time, every so often we say hello to newer and more competent versions of technologies while saying goodbye to their older siblings. Update: please see our official documentation which is now available on this subject: Exchange Server TLS configuration best practices.
0 kommentar(er)
