Source note · Troubleshooting Teams Direct Routing
A wildcard certificate matches only one subdomain level. For example, *.contoso.com matches sbc1.contoso.com but not customer10.sbc1.contoso.com. If the SBC FQDN doesn't match the certificate CN or SAN, Microsoft says to get a new certificate that does.
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 · SIP options issues > FQDN doesn't match the contents of CN or SAN in the provided certificate
Cite this note
APA
WarmTransfer. (2026, September 25). Troubleshooting Teams Direct Routing: source note teams-direct-routing-troubleshooting-wildcard-level. WarmTransfer. https://warmtransfer.net/knowledge/claims/teams-direct-routing-troubleshooting-wildcard-level
BibTeX
@misc{warmtransfer-claim-teams-direct-routing-troubleshooting-wildcard-level,
title = {Troubleshooting Teams Direct Routing: source note teams-direct-routing-troubleshooting-wildcard-level},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/teams-direct-routing-troubleshooting-wildcard-level},
note = {Source note teams-direct-routing-troubleshooting-wildcard-level, checked 2026-09-25}
}