Source note · Troubleshooting Teams Direct Routing
A self-signed SBC certificate isn't valid for Direct Routing. The certificate must come from a trusted CA and contain at least one FQDN that belongs to a Microsoft 365 tenant.
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 self-signed or not from a trusted CA
Cite this note
APA
WarmTransfer. (2026, September 25). Troubleshooting Teams Direct Routing: source note teams-direct-routing-troubleshooting-self-signed. WarmTransfer. https://warmtransfer.net/knowledge/claims/teams-direct-routing-troubleshooting-self-signed
BibTeX
@misc{warmtransfer-claim-teams-direct-routing-troubleshooting-self-signed,
title = {Troubleshooting Teams Direct Routing: source note teams-direct-routing-troubleshooting-self-signed},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/teams-direct-routing-troubleshooting-self-signed},
note = {Source note teams-direct-routing-troubleshooting-self-signed, checked 2026-09-25}
}