We’re making some changes to the Direct Routing SIP interface. Starting on February 1, 2022, the Direct Routing SIP interface will only trust certificates that are signed by Certificate Authorities (CAs) that are part of the Microsoft Trusted Root Certificate Program.
Updated December 31, 2021: We have updated the post to ensure it shows for all tenants as intended. No changes have been made to the content below. Thank you for your patience.
How this will affect your organization
If your SBC certificate is not signed by a CA, you service may be impacted when this change takes effect. Unsupported certificates will not be accepted and you will lose PSTN connectivity via Direct Routing.
Note: Make sure that your SBC certificate is signed by a CA that is part of the program and that the Extended Key Usage (EKU) extension of your certificate includes Server Authentication.
Message ID: MC299923
Published: 24 November 2021
Updated: 14 January 2022
#UserImpact #AdminImpact #UpdatedMessage #365Apps
Plan For Change