Source note · Running a virtual SBC in Azure or AWS
Direct Routing SIP connection points for commercial clouds resolve to 52.112.0.0/14 and 52.120.0.0/14, and Microsoft says firewalls must allow all Teams ranges rather than only addresses returned by DNS.
Checked 2026-10-14
- Vendor
- Microsoft
- Product
- Teams Direct Routing
- Subsystem
- firewall
- 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 · SIP signaling: FQDNs, range list and Important note
Cite this note
APA
WarmTransfer. (2026, October 14). Running a virtual SBC in Azure or AWS: source note cloud-hosted-sbc-dr-signaling-ip-ranges. WarmTransfer. https://warmtransfer.net/knowledge/claims/cloud-hosted-sbc-dr-signaling-ip-ranges
BibTeX
@misc{warmtransfer-claim-cloud-hosted-sbc-dr-signaling-ip-ranges,
title = {Running a virtual SBC in Azure or AWS: source note cloud-hosted-sbc-dr-signaling-ip-ranges},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/cloud-hosted-sbc-dr-signaling-ip-ranges},
note = {Source note cloud-hosted-sbc-dr-signaling-ip-ranges, checked 2026-10-14}
}