Peer two VNets

vnet-a (10.10.0.0/16) and vnet-b (10.20.0.0/16) are separate networks, so vm-a can't reach the HTTPS service on vm-b (10.20.1.4, port 443). Peer the two VNets, watch the peering state change, then test the connection from vm-a.

1. Create the link from vnet-a to vnet-b.

   az network vnet peering create -g rg-lab --name a-to-b --vnet-name vnet-a --remote-vnet vnet-b --allow-vnet-accessType it
   What's this?

   Connects two virtual networks, or changes what the connection allows. A peering needs a link from each side.

   • -g the resource group the resources live in
   • --name the name of the thing to look at or change
   • --vnet-name the virtual network
   • --remote-vnet the virtual network on the other side
   • --vnet-name vnet-a the local side of this link
   • --remote-vnet vnet-b the other VNet, by name or resource ID
   • --allow-vnet-access let traffic flow through this link

2. Check the state from vnet-a. It should say Initiated.

   az network vnet peering list -g rg-lab --vnet-name vnet-a -o tableType it
   What's this?

   Shows the peerings on a virtual network and their state.

   • -g the resource group the resources live in
   • --vnet-name the virtual network

3. Create the reverse link.

   az network vnet peering create -g rg-lab --name b-to-a --vnet-name vnet-b --remote-vnet vnet-a --allow-vnet-accessType it
   What's this?

   Connects two virtual networks, or changes what the connection allows. A peering needs a link from each side.

   • -g the resource group the resources live in
   • --name the name of the thing to look at or change
   • --vnet-name the virtual network
   • --remote-vnet the virtual network on the other side

4. Check the state again. Both links should now say Connected.

   az network vnet peering list -g rg-lab --vnet-name vnet-a -o tableType it
   What's this?

   Shows the peerings on a virtual network and their state.

   • -g the resource group the resources live in
   • --vnet-name the virtual network

5. Connect to vm-a so the next command runs from there.

   ssh vm-aType it
   What's this?

   Opens a shell on vm-a, so the next commands run on that VM. In this lab it's a shortcut. In real Azure you'd connect through something like Azure Bastion, or SSH to an address you can reach.

6. From vm-a, test vm-b's port 443. Then type exit.

   nc -zv 10.20.1.4 443Type it
   What's this?

   netcat, a standard Linux tool. Tries to open a TCP connection and reports whether it worked.

   • -z only check whether the port answers. Send no data
   • -v print the result in words
   • 10.20.1.4 where to connect
   • 443 the port to try