-
Hello samabc,
Thanks for the feedback.
The key issue lies in regional alignment rather than peering requirements.
As noted in the explanation, “A virtual machine, its network interface, and the virtual network it connects to must all reside in the same region.”
In the given scenario:
- TDVM1 and the NIC are in South East Asia.
- TDNET1 is in Japan West.
This means the NIC cannot be attached to TDNET1, as cross-region NIC-to-VNet attachment is not supported. Additionally, VNet peering (including global peering) is used to enable communication between virtual networks, not to attach a NIC to a VNet in another region.
Take note that a VM can be directly connected to a VNet via a NIC, as long as the VM, NIC, and VNet are in the same region. No peering is required in that case.
Please refer to this: https://learn.microsoft.com/en-us/azure/virtual-network/virtual-network-network-interface?tabs=azure-portal
I hope this helps! Let us know if you need further assistance.
Best regards,
JR @ Tutorials Dojo
