Event details

If you’re running workloads in Azure, you already know the world of Virtual Networks, subnets, IP ranges, and all the moving parts that come with cloud networking. But have you met Azure Virtual N...
lukemurraynz
Published May 24, 2026
PanosGR191's avatar
PanosGR191
MCT
Jul 29, 2026

Excellent centralized management ! 
Some quick questions, 
You show how to create an "Allow ALL" NSG that overrides local NSGs, but this allow-all is visible inside the nsg for verification
After that you demo the mesh-config, showing in the Peerings that vn1,vn2,vn3 were not having ANY Peering at all , but still able to connect to each other because of the "mesh-config" from AVNM !
How is this "visible" on each network for verification ? 
Or Network Watcher is able to see , if we are trying to troubleshoot something ? 

Thanks again for your interesting demo's
BR , Panos

  • rexdekoning's avatar
    rexdekoning
    MVP
    Jul 29, 2026

    I was a bit to quick with my previous reply.. It is visible on the VM level. If you go to the nic of your VM and to the effictive routes page you will see:

    So the NIC for this VM is in VNET1 (10.31.1.0/24) and the other VNETS 10.31.2.0/24 and 10.31.3.0/24 have a Next HOP Type of Connected Network

  • rexdekoning's avatar
    rexdekoning
    MVP
    Jul 29, 2026

    Its not directly visible, but is it is sort of a managed peering underneed the hood. If you use network watcher to monitor traffic it will show that the traffic just flows freely, same with the connection trouble shooter