Understanding Azure Network Tree

By following the steps below, you will be able to view and understand the detailed information of your tenants, for example:

•Level 0: Tenant

•Level 1: Subscription 

•Level 2: Region

•Level 3: VNet

•Level 4: Virtual Network Distributed Router 

•Level 4： Subnet

•Level 5: Virtual machines

•Level 4: VPN Gateway

•Level 4: Express Route Gateway

•Level 4: Application Gateway

•Level 4: Azure Load Balancer(Internal)

•Level 4: NAT Gateway

•Level 4: Azure Firewall

•Level 3: MSEE

•Level 3: Azure Load Balancer (Public)

•Level 3: Unassigned NAT Gateway

•Level 2: Virtual WAN

•Level 3: Virtual WAN Hub

•Level 4: VPN Gateway for vHub

•Level 4: Express Route Gateway for vHub

•Level 4: Azure Firewall

 
 

1.Click Network on the task bar.

2.In the Network pane, select Network Centric View > View by Accounts. The AWS data model is organized in this order: Account > Region > VPC > Subet.

3.Expand a tenant node to view the relationship between its child nodes.

4.Select the interested object (e.g., Virtual Network, Subnet, Region, etc.)

Tip: You can use the search box in the network pane to quickly find the desired resources.

5.  Click the Context Maps tab to view the corresponding context map of the object.

6.  Click the Device Details tab to view the details of the object and the hyperlink will take you to the Azure console directly. 

Note: In the Network Tree, you will also find the network objects organized in hierarchy as below:

•The virtual network as a parent node to include sub node virtual network distributed router and subnet.

oThe virtual network distributed router is a NetBrain conceptual component to simulate virtual network as a network object to build relationship with other resources that belong to this virtual network.

oThe virtual machine is listed under subnet that belong to this virtual network.

•The VPN gateway, ExpressRoute gateway, application gateway, Azure load balancer (internal), NAT gateway, Azure firewall are listed under virtual network which they belong to.

•The MSEE is simulated as a network object to connect with virtual network and on-premise network, so it is listed under region.

•The Azure load balancer (public) might not belong to a certain virtual network, so it is listed under region.

•If the NAT gateway does not belong to any virtual network, it will be listed under region as an unassigned NAT gateway.

•The Virtual WAN is used to connect networks within different region, so it is listed under subscription. The virtual WAN hub is listed under virtual WAN, and the VPN gateway for vhub, ExpressRoute gateway for vhub and Azure firewall are listed under virtual WAN hub 

Azure Context Map

The following table list the available context maps for Azure:

Name

Description

Sample Map

Virtual Network Context Map

This context map helps you understand the relationship of resources within the same virtual network. The virtual machine will not be mapped by default due to its massive number.

Subnet Context Map

This context map helps you understand the virtual machine connecting to the same subnet within the virtual network.

Region Context Map

This context map displays all virtual network and its resources relationship within the same region.

This context map also displays the management view for the selected region.

VPN Context Context Map

This context map demonstrates the IPsec VPN connection between VPN gateway and on-premise edge device.  

ExpressRoute Gateway Context Map

This context map demonstrates the connection between ExpressRoute gateway and on-promise network via MSEE.

Virtual Hub Context Map

This context map demonstrates the resources used to connect to on-promise network, the connected virtual network within different region(s), and other connected virtual hub(s) via MS backbone.