Published November 12, 2021

TLS1.2 enforcement for Direct Routing SIP interface

Reference ID: MC297438 | Effective: January 3, 2022

MC297438 – Updated November 12, 2021: Microsoft has updated the content below for clarity. Thank you for your feedback.

Microsoft is making some changes to Direct Routing SIP interface.

On January 3rd 2022, to provide the best-in-class encryption to Microsoft’s customers, they will begin retiring Transport Layer Security (TLS) versions 1.0 and 1.1 and begin obligating TLS1.2 usage for the Direct Routing SIP interface.

  • The move to TLS 1.2 is to ensure that Microsoft’s service is secure by default and in alignment with the rest of Microsoft 365 services as previously communicated (MC126199 in Dec 2017, MC128929 in Feb 2018, MC186827 in July 2019, MC218794 in July 2020, MC240160 in February 2021, and MC292797 in October 2021).

Note: If your organization has already taken steps to migrate from TLS 1.0 and 1.1, you can safely disregard this message.

How this will affect your organization:

To provide the best-in-class encryption to Microsoft’s customers, they will be retiring Transport Layer Security (TLS) versions 1.0 and 1.1 beginning January 3rd 2022 and will begin forcing TLS1.2 usage for the Direct Routing SIP interface.

  • To avoid any service impact, please make sure that your SBCs are configured to support TLS 1.2 and are able to connect using one of the following cipher suites:
    • TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 i.e. ECDHE-RSA-AES256-GCM-SHA384
    • TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 i.e. ECDHE-RSA-AES128-GCM-SHA256
    • TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384 i.e. ECDHE-RSA-AES256-SHA384
    • TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256 i.e. ECDHE-RSA-AES128-SHA256

What you need to do to prepare:

Review your SBCs and ensure they are configured to support TLS 1.2.

Learn more:

Petri Newsletters

Whether it’s Security or Cloud Computing, we have the know-how for you. Sign up for our newsletters here.