Source note · CUCM to Teams Phone migration
The SBC certificate should carry the SBC FQDN as Common Name or Subject Alternative Name, be signed by a Certificate Authority in the Microsoft Trusted Root Program and include the Server Authentication EKU, and wildcard certificates are supported when they comply with RFC 2818.
Checked 2026-09-21
- Vendor
- Microsoft
- Product
- Teams Phone
- Subsystem
- direct-routing-security
- Deployment
- multi-tenant
- Region
- not restricted
- Release range
- current as of 2026-09-21
- Checked
- 2026-09-21
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 21). CUCM to Teams Phone migration: source note cucm-to-teams-phone-sbc-certificate-requirements. WarmTransfer. https://warmtransfer.net/knowledge/claims/cucm-to-teams-phone-sbc-certificate-requirements
BibTeX
@misc{warmtransfer-claim-cucm-to-teams-phone-sbc-certificate-requirements,
title = {CUCM to Teams Phone migration: source note cucm-to-teams-phone-sbc-certificate-requirements},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/cucm-to-teams-phone-sbc-certificate-requirements},
note = {Source note cucm-to-teams-phone-sbc-certificate-requirements, checked 2026-09-21}
}