A self-signed SBC certificate is invalid for Teams 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-10-02
- Vendor
- Microsoft
- Product
- Teams Direct Routing
- Subsystem
- SBC certificate
- Deployment
- multi-tenant
- Region
- not restricted
- Release range
- current as of 2026-10-02
- Checked
- 2026-10-02
Sources
- SBC connectivity issues — Microsoft · tier 2 current vendor documentation · Issues related to the TLS connection: 'The SBC certificate is self-signed or not from a trusted CA'
Cite this note
APA
WarmTransfer. (2026, October 2). SIP trunk authentication: registration and static IP and mutual TLS: source note sip-trunk-authentication-models-teams-dr-no-self-signed. WarmTransfer. https://warmtransfer.net/knowledge/claims/sip-trunk-authentication-models-teams-dr-no-self-signed
BibTeX
@misc{warmtransfer-claim-sip-trunk-authentication-models-teams-dr-no-self-signed,
title = {SIP trunk authentication: registration and static IP and mutual TLS: source note sip-trunk-authentication-models-teams-dr-no-self-signed},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/sip-trunk-authentication-models-teams-dr-no-self-signed},
note = {Source note sip-trunk-authentication-models-teams-dr-no-self-signed, checked 2026-10-02}
}