Network Design Ideas for VMs in Azure
Hello, I am analyzing the current Azure environment at my new job and trying to figure out the architectural choices mostly networking wise. Currently, we have 10 VMs and each VM has its own VNet and they are all in the same region. In my experience so far, I have never seen such network design in Azure before. If all VMs are in the same region, we could have one Vnet and utilize subnets and NSGs to segment the VMs and control the traffic. Having so many different VNets makes it very complex to manage. Looking for opinions what other people think. Is this just a bad design or just to keep the VMs separate from each other.
Avilable IP address in the CIDR is zero
I have vnet created for SQL PASS and under that I have created subnet for the same. As it is an environment for lab requirement I have provided any address Space 10.x.x.x/24 … but entire IP address got used... there is no available ip address now. Is there any way to release the IP address from subnet.… because it is difficult release from each resources...
Which route to add in following peering scenario for traffic forwarding ?
Hi, I am trying a scenario as per the diagram where ABC Azure network are peered in a chain & VM-A is trying to communicate with VM-C. "Allow forwarded traffic" is enabled for all peering's. A is not directly peered with C. Will a traffic transit work over B with custom route here or is A-C direct peering the way to go.
VM: to add/change vnet i need to redeploy VM ?
Hello Team, I could not add another vnet to my vm, nor change assigned vnet to another. Found in a documentation: If you create a VM and later want to migrate it into a virtual network, it is not a simple configuration change. You have to redeploy the VM into the virtual network. The easiest way to do this is to delete the VM, but not any disks attached to it, and then re-create the VM using the original disks in the virtual network That's strange. Why i can not attach my VM to a different network ? I could do it on any hypervisor. Interface flap for OS causes DHCP process to jump in to get the right ip. Could you clarify ? Thanks, Michal
