An SBC FQDN paired with Azure Communication Services direct routing must differ from the SBC FQDN used for Teams Direct Routing, and one SBC FQDN cannot pair with more than one Communication Services resource.
Checked 2026-10-02
- Vendor
- Microsoft
- Product
- Azure Communication Services
- Subsystem
- SBC identity
- Deployment
- multi-tenant
- Region
- not restricted
- Release range
- current as of 2026-10-02
- Checked
- 2026-10-02
Sources
- Azure direct routing infrastructure requirements - Azure Communication Services — Microsoft · tier 2 current vendor documentation · Section 'SBC certificates and domain names' (Note and pairing paragraph)
Cite this note
APA
WarmTransfer. (2026, October 2). SIP trunk authentication: registration and static IP and mutual TLS: source note sip-trunk-authentication-models-acs-dr-fqdn-distinct. WarmTransfer. https://warmtransfer.net/knowledge/claims/sip-trunk-authentication-models-acs-dr-fqdn-distinct
BibTeX
@misc{warmtransfer-claim-sip-trunk-authentication-models-acs-dr-fqdn-distinct,
title = {SIP trunk authentication: registration and static IP and mutual TLS: source note sip-trunk-authentication-models-acs-dr-fqdn-distinct},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/sip-trunk-authentication-models-acs-dr-fqdn-distinct},
note = {Source note sip-trunk-authentication-models-acs-dr-fqdn-distinct, checked 2026-10-02}
}