Source note · Teams Operator Connect and Azure Communication routing
An Azure Communication Services direct routing SBC FQDN must be different from any Teams Direct Routing SBC FQDN, and one SBC FQDN can pair with only one Communication resource.
Checked 2026-09-23
- Vendor
- Microsoft
- Product
- Azure Communication Services direct routing
- Subsystem
- SBC pairing
- Deployment
- multi-tenant
- Region
- not restricted
- Release range
- legacy; subject to ACS telephony retirement
- Checked
- 2026-09-23
Sources
- Azure direct routing known limitations - Azure Communication Services — Microsoft · tier 2 current vendor documentation · Azure Communication Services direct routing known limitations, bullets 4-5
Cite this note
APA
WarmTransfer. (2026, September 23). Teams Operator Connect and Azure Communication routing: source note teams-operator-connect-acs-dr-fqdn-separate. WarmTransfer. https://warmtransfer.net/knowledge/claims/teams-operator-connect-acs-dr-fqdn-separate
BibTeX
@misc{warmtransfer-claim-teams-operator-connect-acs-dr-fqdn-separate,
title = {Teams Operator Connect and Azure Communication routing: source note teams-operator-connect-acs-dr-fqdn-separate},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/teams-operator-connect-acs-dr-fqdn-separate},
note = {Source note teams-operator-connect-acs-dr-fqdn-separate, checked 2026-09-23}
}