Microsoft SIP endpoints currently accept SBC certificates that lack the Client Authentication EKU, and Microsoft expects this to continue for the foreseeable future, with advance notice before any change.
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
- What's New Direct Routing — Microsoft · tier 2 current vendor documentation · Entry 'Clarification on Client Authentication Extended Key Usage (EKU)'
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-client-eku-optional. WarmTransfer. https://warmtransfer.net/knowledge/claims/sip-trunk-authentication-models-teams-dr-client-eku-optional
BibTeX
@misc{warmtransfer-claim-sip-trunk-authentication-models-teams-dr-client-eku-optional,
title = {SIP trunk authentication: registration and static IP and mutual TLS: source note sip-trunk-authentication-models-teams-dr-client-eku-optional},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/sip-trunk-authentication-models-teams-dr-client-eku-optional},
note = {Source note sip-trunk-authentication-models-teams-dr-client-eku-optional, checked 2026-10-02}
}