Handling a full Azure VNET
Read OriginalThis article provides a practical guide for handling a full Azure VNET by extending its IP address space. It covers two methods: increasing the existing IP range (e.g., /16 to /15) and adding additional non-contiguous ranges (e.g., /24). The changes can be done live with minimal impact on running VMs. The article includes Terraform code examples for modifying address_space definitions and addresses the gotcha of resyncing VNET peerings after expansion, using Azure Portal or PowerShell commands like Sync-AzVirtualNetworkPeering. Targeted at Azure administrators and DevOps engineers.
Comments
No comments yet
Be the first to share your thoughts!
Browser Extension
Get instant access to AllDevBlogs from your browser
Top of the Week
No top articles yet