Source note · Running a virtual SBC in Azure or AWS
The Direct Routing SBC certificate must carry the SBC FQDN in the CN or SAN and be signed by a CA in the Microsoft Trusted Root Program with the Server Authentication EKU.
Checked 2026-10-14
- Vendor
- Microsoft
- Product
- Teams Direct Routing
- Subsystem
- tls
- Deployment
- multi-tenant
- Region
- not restricted
- Release range
- current as of 2026-10-14
- Checked
- 2026-10-14
Sources
- Plan Direct Routing — Microsoft (Microsoft Learn) · tier 2 current vendor documentation · Public trusted certificate for the SBC
Cite this note
APA
WarmTransfer. (2026, October 14). Running a virtual SBC in Azure or AWS: source note cloud-hosted-sbc-dr-trusted-cert. WarmTransfer. https://warmtransfer.net/knowledge/claims/cloud-hosted-sbc-dr-trusted-cert
BibTeX
@misc{warmtransfer-claim-cloud-hosted-sbc-dr-trusted-cert,
title = {Running a virtual SBC in Azure or AWS: source note cloud-hosted-sbc-dr-trusted-cert},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/cloud-hosted-sbc-dr-trusted-cert},
note = {Source note cloud-hosted-sbc-dr-trusted-cert, checked 2026-10-14}
}