Source note · Running a virtual SBC in Azure or AWS

For the Azure API version released after 31 March 2026, subnets in new virtual networks default to private (defaultOutboundAccess false), so VMs need an explicit outbound method; existing virtual networks are unchanged.

Checked 2026-10-14

Vendor: Microsoft
Product: Azure Virtual Network
Subsystem: nat
Deployment: iaas
Region: not restricted
Release range: API versions released after 2026-03-31
Checked: 2026-10-14

Sources

Default Outbound Access in Azure — Microsoft · tier 2 current vendor documentation · Retirement of default outbound access: scope and impact, What's affected and What isn't affected

Cite this note

APA

WarmTransfer. (2026, October 14). Running a virtual SBC in Azure or AWS: source note cloud-hosted-sbc-azure-new-vnets-private. WarmTransfer. https://warmtransfer.net/knowledge/claims/cloud-hosted-sbc-azure-new-vnets-private

BibTeX

@misc{warmtransfer-claim-cloud-hosted-sbc-azure-new-vnets-private,
  title  = {Running a virtual SBC in Azure or AWS: source note cloud-hosted-sbc-azure-new-vnets-private},
  author = {{WarmTransfer}},
  year   = {2026},
  url    = {https://warmtransfer.net/knowledge/claims/cloud-hosted-sbc-azure-new-vnets-private},
  note   = {Source note cloud-hosted-sbc-azure-new-vnets-private, checked 2026-10-14}
}

Read in context