The SBC certificate should carry the SBC FQDN in the CN or SAN, be signed by a CA in the Microsoft Trusted Root Program, and include the Server Authentication EKU; RFC 2818-compliant wildcard certificates are supported.
Checked 2026-09-24
- Vendor
- Microsoft
- Product
- Teams Phone Direct Routing
- Subsystem
- SBC certificate
- Deployment
- multi-tenant
- Region
- not restricted
- Release range
- current as of 2026-09-24
- Checked
- 2026-09-24
Sources
- Plan Direct Routing — Microsoft (Microsoft Learn) · tier 2 current vendor documentation · Public trusted certificate for the SBC
Cite this note
APA
WarmTransfer. (2026, September 24). Building a hybrid Unified CM and Teams Phone environment for a phased migration: source note cucm-teams-hybrid-build-plan-certificate. WarmTransfer. https://warmtransfer.net/knowledge/claims/cucm-teams-hybrid-build-plan-certificate
BibTeX
@misc{warmtransfer-claim-cucm-teams-hybrid-build-plan-certificate,
title = {Building a hybrid Unified CM and Teams Phone environment for a phased migration: source note cucm-teams-hybrid-build-plan-certificate},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/cucm-teams-hybrid-build-plan-certificate},
note = {Source note cucm-teams-hybrid-build-plan-certificate, checked 2026-09-24}
}