Source note · Running a virtual SBC in Azure or AWS
Changing an Azure subnet between private and non-private only takes effect on existing VMs after they are stopped and deallocated.
Checked 2026-10-14
- Vendor
- Microsoft
- Product
- Azure Virtual Network
- Subsystem
- operations
- Deployment
- iaas
- Region
- not restricted
- Release range
- current as of 2026-10-14
- Checked
- 2026-10-14
Sources
- Default Outbound Access in Azure — Microsoft · tier 2 current vendor documentation · How to configure private subnets, Important note after the tabs
Cite this note
APA
WarmTransfer. (2026, October 14). Running a virtual SBC in Azure or AWS: source note cloud-hosted-sbc-azure-subnet-change-deallocate. WarmTransfer. https://warmtransfer.net/knowledge/claims/cloud-hosted-sbc-azure-subnet-change-deallocate
BibTeX
@misc{warmtransfer-claim-cloud-hosted-sbc-azure-subnet-change-deallocate,
title = {Running a virtual SBC in Azure or AWS: source note cloud-hosted-sbc-azure-subnet-change-deallocate},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/cloud-hosted-sbc-azure-subnet-change-deallocate},
note = {Source note cloud-hosted-sbc-azure-subnet-change-deallocate, checked 2026-10-14}
}