A Teams Direct Routing SBC certificate should carry the SBC FQDN in CN or SAN, be signed by a CA in the Microsoft Trusted Root Program, and include the Server Authentication EKU; RFC 2818-compliant wildcards are supported.
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
- Plan Direct Routing — Microsoft (Microsoft Learn) · tier 2 current vendor documentation · Section 'Public trusted certificate for the SBC'
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-sbc-cert-reqs. WarmTransfer. https://warmtransfer.net/knowledge/claims/sip-trunk-authentication-models-teams-dr-sbc-cert-reqs
BibTeX
@misc{warmtransfer-claim-sip-trunk-authentication-models-teams-dr-sbc-cert-reqs,
title = {SIP trunk authentication: registration and static IP and mutual TLS: source note sip-trunk-authentication-models-teams-dr-sbc-cert-reqs},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/sip-trunk-authentication-models-teams-dr-sbc-cert-reqs},
note = {Source note sip-trunk-authentication-models-teams-dr-sbc-cert-reqs, checked 2026-10-02}
}