Source note · Troubleshooting Teams Direct Routing
After renewing the SBC certificate, the TLS connections already set up with the old certificate must be torn down and re-established, or the Teams admin center keeps raising expiration warnings. Microsoft suggests restarting the SBC in a low-traffic window, or asking the SBC vendor how to force old TLS connections closed.
Checked 2026-09-25
- Vendor
- Microsoft
- Product
- Microsoft Teams Phone Direct Routing
- Subsystem
- tls-certificates
- Deployment
- multi-tenant
- Region
- not restricted
- Release range
- current as of 2026-09-25
- Checked
- 2026-09-25
Sources
- SBC connectivity issues — Microsoft · tier 2 current vendor documentation · TLS connection issues > SBC certificate is invalid, second paragraph
Cite this note
APA
WarmTransfer. (2026, September 25). Troubleshooting Teams Direct Routing: source note teams-direct-routing-troubleshooting-cert-renew-restart. WarmTransfer. https://warmtransfer.net/knowledge/claims/teams-direct-routing-troubleshooting-cert-renew-restart
BibTeX
@misc{warmtransfer-claim-teams-direct-routing-troubleshooting-cert-renew-restart,
title = {Troubleshooting Teams Direct Routing: source note teams-direct-routing-troubleshooting-cert-renew-restart},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/teams-direct-routing-troubleshooting-cert-renew-restart},
note = {Source note teams-direct-routing-troubleshooting-cert-renew-restart, checked 2026-09-25}
}