Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Topology provides an interactive interface to view resources and their relationships in Azure across multiple subscriptions, regions, and resource groups. It helps you manage and monitor your cloud network infrastructure with interactive graphical interface that provides you with insights from Azure Network Watcher connection monitor and traffic analytics. Topology helps you diagnose and troubleshoot network issues by providing contextual access to Network Watcher diagnostic tools such as connection troubleshoot, packet capture, and next hop.
In this article, you learn how to use topology to visualize virtual networks and connected resources.
Note
Azure Resource Graph is used to draw resources topology. In case of any configuration changes, it might take up to 30 hours for the changes to reflect in Azure Resource Graph and then in topology.
Prerequisites
- An Azure account with an active subscription. Create an account for free.
- The necessary role-based access control (RBAC) permissions to use Azure Network Watcher capabilities.
Supported resource types
Topology supports the following resource types:
- Application Gateways
- Azure Bastion hosts
- Azure DDoS Protection plans
- Azure DNS zones
- Azure Firewalls
- Azure Front Door profiles
- Azure Kubernetes Service clusters (preview)
- Azure NAT Gateways
- Connections
- DNS Private Resolvers
- ExpressRoute circuits
- Load balancers
- Local network gateways
- Network interfaces
- Network security groups
- Private DNS zones
- Private endpoints
- Private Link services
- Public IP addresses
- Service endpoints
- Traffic Manager profiles
- Virtual hubs
- Virtual machine scale sets
- Virtual machines
- Virtual network gateways (VPN and ExpressRoute)
- Virtual networks
- Virtual WANs
- Web Application Firewall policies
Get started with topology
In this section, you learn how to view a region's topology and insights.
Sign in to the Azure portal.
In the search box at the top of the portal, enter network watcher. Select Network Watcher from the search results.
Under Monitoring, select Topology.
Note
You can also get to the topology from:
- Monitor: Insights > Networks > Topology.
- Virtual networks: Monitoring > Diagram.
Select Scope to define the scope of the topology.
In the Select scope pane, select the list of Subscriptions, Resource groups, and Locations of the resources for which you want to view the topology, then select Save.
Select Resource type to choose the resource types that you want to include in the topology and select Apply. See supported resource types.
Use the mouse wheel to zoom in or out, or select the plus or minus sign. You can also use the mouse to drag the topology to move it around or use the arrows on the screen.
Select Download topology if you want to download the topology view to your computer. A file with the .svg extension is downloaded.
Select a region to see its information and insights. The Insights tab provides a snapshot of connectivity and traffic insights for the selected region.
Note
- Connectivity insights are available when connection monitor is enabled. For more information, see connection monitor.
- Traffic insights are available when Flow logs and traffic analytics are enabled. For more information, see NSG flow logs, VNet flow logs and traffic analytics.
Select the Traffic tab to see detailed traffic information about the selected region. The insights presented in this tab are fetched from Network Watcher flow logs and traffic analytics. You see Set up Traffic Analytics with no insights if traffic analytics isn't enabled.
Select the Connectivity tab to see detailed connectivity information about the selected region. The insights presented in this tab are fetched from Network Watcher connection monitor. You see Set up Connection Monitor with no insights if connection monitor isn't enabled.
Drilldown resources
In this section, you learn how to navigate the topology view from regions to the individual Azure resource such as a virtual machine (VM). Once you drill down to the VM, you can see its traffic and connectivity insights. From the VM view, you have access to Network Watcher diagnostic tools such as connection troubleshoot, packet capture and next hop to help in troubleshooting any issues you have with the VM.
Select Scope to choose the subscriptions and regions of the resources that you want to navigate to. The following example shows one subscription and region selected.
Select the plus sign of the region that has the resource that you want to see to navigate to the region view.
In the region view, you see virtual networks and other Azure resources in the region. You see any virtual network peerings in the region so you can understand the traffic flow from and to resources within the region. You can navigate to the virtual network view to see its subnets.
Select the plus sign of the virtual network that has the resource that you want to see to navigate to the virtual network view. If the region has multiple virtual networks, you might see Virtual Networks. Select the plus sign of Virtual Networks to drill down to the virtual networks in your region and then select the plus sign of the virtual network that has the resource that you want to see.
In the virtual network view of myVNet, you see all five subnets that myVNet has.
Select the plus sign of a subnet to see all the resources that exist in it and their relationships.
In the subnet view of mySubnet, you see Azure resources that exist in it and their relationships. For example, you see myVM and its network interface myvm36 and IP configuration ipconfig1.
Select the virtual machine that you want to see its insights.
In insights tab, you see essential insights. Scroll down to see connectivity and traffic insights and resource metrics.
Note
- Connectivity insights are available when connection monitor is enabled. For more information, see Connection monitor.
- Traffic insights are available when flow logs and traffic analytics are enabled. For more information, see NSG flow logs, VNet flow logs and traffic analytics.
Select the Traffic tab to see detailed traffic information about the selected VM. The insights presented in this tab are fetched from Network Watcher flow logs and traffic analytics. You see Set up Traffic Analytics with no insights if traffic analytics isn't enabled.
Select the Connectivity tab to see detailed connectivity information about the selected VM. The insights presented in this tab are fetched from Network Watcher connection monitor. You see Set up Connection Monitor with no insights if connection monitor isn't enabled.
Select the Insights + Diagnostics tab to see the summary of the VM and to use Network Watcher diagnostic tools such as connection troubleshoot, packet capture and next hop to help in troubleshooting any issues you have with the VM.
AKS cluster topology visualization
Azure Kubernetes Service (AKS) clusters can be complex, with multiple interconnected Azure resources supporting containerized workloads. Topology in Network Watcher now supports AKS visualization, enabling you to view and understand the network architecture of your AKS clusters directly within the Azure portal.
AKS network topology visualization provides a graphical representation of the networking resources associated with your AKS cluster. This includes virtual networks (VNets), subnets, network security groups (NSGs), load balancers, NAT gateways, public IPs, and more. The visualization helps you:
Understand resource relationships: See how AKS nodes, pods, and supporting infrastructure are connected, helping you visualize dependencies and architecture.
Diagnose connectivity issues: Identify misconfigurations or bottlenecks in your cluster's network setup. The visualization displays connectivity details such as active connections and connection drops, allowing you to quickly spot failures or interruptions in network paths.
Monitor traffic: Analyze traffic metrics including bytes forwarded and bytes dropped across network paths. This helps you assess throughput, detect bottlenecks, and understand data transmission efficiency within your AKS environment.
Monitor resource health: Quickly assess the state and placement of critical networking components to ensure your AKS cluster is operating optimally.
Supported AKS scenarios
Topology supports visualization for a wide range of AKS deployment scenarios, including:
- Default AKS clusters (Kubenet, no custom VNet/UDR)
- Kubenet with custom VNet and UDR
- Azure CNI (with or without custom VNet)
- Managed and user-managed NAT Gateway
- Private clusters and clusters with Azure Firewall
- Node pools in separate subnets
- Dynamic IP allocation for pods
Limitations
- AKS clusters and their main network components must reside within the same subscription and region.
- Migration of clusters between subscriptions, tenants, or resource groups isn't supported.
Diagnose network issues with Network Watcher in Support + Troubleshooting (Preview)
From topology, you can now start a network diagnosis directly in Support + Troubleshooting. Select the issue you're facing, and if it's a network connectivity issue that Network Watcher can diagnose, Support + Troubleshooting uses Copilot Troubleshooting Agent to choose and run the relevant Network Watcher diagnostics for you. It then correlates the results and tells you the probable cause, how confident it is, and the recommended next steps. You don't need to open each diagnostic tool separately, decide which one to run, or fill in its parameters yourself.
The findings come from Network Watcher itself. Network Watcher works out routes, checks network security group (NSG) rules, and tests connectivity. AI decides which diagnostics fit your issue, runs them, and explains the combined results in plain language.
Important
Diagnosing network issues with Network Watcher in Support + Troubleshooting is currently in preview. Features and functionality might change before general availability.
Supported Network Watcher diagnostics
During the limited preview, Support + Troubleshooting can run the following Network Watcher diagnostics:
| Diagnostic | What it checks |
|---|---|
| Next hop | Finds the next hop type and IP address that traffic from a VM takes toward a destination. |
| IP flow verify | Checks whether NSG rules allow or deny a specific inbound or outbound flow. |
| Connection troubleshoot | Tests connectivity from a source VM to a destination and finds issues along the path. |
| NSG diagnostics | Checks how NSG rules apply to traffic between a source and a destination. |
You don't choose the diagnostic. Based on the issue you select, Support + Troubleshooting runs only the diagnostics that are relevant to it.
Prerequisites
- Azure Copilot access. Azure Copilot must be enabled for your tenant, and your account must have access to it. The Troubleshooting preview capability must also be turned on in the Azure Copilot admin center. A Global Administrator can manage both settings. For more information, see Manage access to Azure Copilot.
- Permissions. You can only diagnose resources you have access to, and every diagnostic runs with your Azure role-based access control (Azure RBAC) permissions. For more information, see Azure role-based access control permissions required to use Network Watcher capabilities.
Diagnose an issue from topology
In topology, select Diagnose network issues (Preview) at the top of the map.
The Support + Troubleshooting pane opens. Select the issue that best describes your problem.
If the issue is a network connectivity issue that Network Watcher can diagnose, Support + Troubleshooting uses AI to decide which Network Watcher diagnostics to run. If it needs more information, provide the details it asks for. When it has everything it needs, it runs the diagnostics.
Review the results. Support + Troubleshooting correlates the output of the diagnostics it ran and shows:
- Probable cause: The most likely reason for the issue, based on the Network Watcher findings.
- Findings: The specific results from each diagnostic. For example, a connection troubleshoot result includes the connection status, the number of probes sent and failed, latency when available, and any issues found, such as a user-defined route that sends traffic to a
Nonenext hop, or an NSG rule likeDefaultRule_DenyAllOutBoundthat denies outbound traffic. - Recommended next steps: Suggested actions to resolve the issue.
If the issue isn't one that Network Watcher can diagnose, Support + Troubleshooting continues with its standard troubleshooting guidance and support options.
Limitations
- Read-only. The diagnosis runs only read-only Network Watcher diagnostics. Nothing in the experience creates, modifies, or deletes route tables, NSGs, firewalls, network interfaces, virtual networks, VMs, or other Azure resources. You decide whether to make a configuration change.
- VM as the source. Diagnostics run from a target VM.
- Point in time. Each diagnostic checks the current state of your resources when it runs. For continuous monitoring, use connection monitor.
- Limited to the supported diagnostics. The AI diagnosis doesn't check application, DNS, guest OS, or firewall health beyond what the supported Network Watcher diagnostics cover.
Note
AI-generated content can be incorrect. Review the Network Watcher findings before you change your network configuration. Don't include passwords, access tokens, secrets, or unrelated sensitive information in any details you provide.