Source note · Running a virtual SBC in Azure or AWS
An SBC on an Azure Standard public IP receives no inbound SIP or RTP until an NSG explicitly allows the Teams signaling and media ranges and the carrier's addresses.
inferred · Checked 2026-10-14
- Vendor
- Microsoft
- Product
- Azure Public IP
- Subsystem
- firewall
- Deployment
- iaas
- Region
- not restricted
- Release range
- current as of 2026-10-14
- Status
- inferred
- Checked
- 2026-10-14
Sources
- Upgrade Basic Public IP Address to Standard SKU in Azure — Microsoft · tier 2 current vendor documentation · Basic SKU vs. Standard SKU table, Security row
Cite this note
APA
WarmTransfer. (2026, October 14). Running a virtual SBC in Azure or AWS: source note cloud-hosted-sbc-inf-azure-nsg-rules-needed. WarmTransfer. https://warmtransfer.net/knowledge/claims/cloud-hosted-sbc-inf-azure-nsg-rules-needed
BibTeX
@misc{warmtransfer-claim-cloud-hosted-sbc-inf-azure-nsg-rules-needed,
title = {Running a virtual SBC in Azure or AWS: source note cloud-hosted-sbc-inf-azure-nsg-rules-needed},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/cloud-hosted-sbc-inf-azure-nsg-rules-needed},
note = {Source note cloud-hosted-sbc-inf-azure-nsg-rules-needed, checked 2026-10-14}
}