Skip to main content
Azure Network Watcher is a collection of monitoring and diagnostic tools for observing and troubleshooting network performance and health in Azure. Use it to validate connectivity, identify routing or security issues, capture traffic, and visualize network topology — useful for both operational troubleshooting and certification exam preparation.
A screenshot of an Azure "Network Watcher" interface showing three columns: Network diagnostic tools, Monitoring, and Logs. It lists items like IP flow verify, NSG diagnostic, topology and connection monitors, and NSG flow logs/traffic analytics.
Summary of core Network Watcher features
For exam scenarios, be prepared to explain when to use IP Flow Verify vs. Connection Troubleshoot, and how Next Hop reports system routes versus user-defined routes (UDRs). Understanding which tool to pick for specific troubleshooting tasks is commonly tested.

Accessing Network Watcher in the Azure portal

  1. Search for “Network Watcher” in the Azure portal and open the resource.
  2. Choose the subscription and region where you want to run diagnostics (Network Watcher is regional).
  3. Use the left-hand menu to access specific tools such as IP Flow Verify, Next Hop, Connection Troubleshoot, Packet Capture, Topology, and NSG diagnostics.
We’ll walk through the most commonly used tools in the same order as they appear in the portal.

IP Flow Verify

IP Flow Verify validates whether traffic to or from a virtual machine is permitted by the effective NSG rules. Provide the source and destination IP/port/protocol and the tool reports whether access is allowed or denied and the NSG rule that produced that decision. Example steps:
  • Select the target VM (for example, gembox or jumpbox-vm) and its network interface.
  • Protocol: TCP
  • Direction: Inbound
  • Local IP: the VM’s private IP
  • Local port: e.g. 3389 (RDP) or 22 (SSH)
  • Remote IP/port: the source you want to test
This validates whether a packet from the remote endpoint to the VM’s IP/port is allowed or denied by the effective NSG rules. In the example below, a test to port 3389 is denied due to a “deny all inbound” NSG rule; testing port 22 shows access allowed.
A screenshot of the Microsoft Azure portal showing the Network Watcher "IP flow verify" tool configured for the jumpbox-vm (TCP, inbound) with local IP 10.0.0.4:22 and remote IP 52.17.45.11:22. The results area at the bottom shows "Access allowed."
Tips:
  • IP Flow Verify is ideal when you need a quick check to identify which NSG rule permits or blocks a single flow.
  • If you need hop-by-hop diagnostics, latency, or port accessibility across the network path, use Connection Troubleshoot instead.

NSG Diagnostics and NSG Flow Logs

NSG diagnostics (also known as NSG Flow Logs when enabled) capture ingress and egress traffic flowing through a Network Security Group. Configure diagnostic settings to send logs to a storage account, Log Analytics workspace, or Event Hub to support auditing and Traffic Analytics. Use NSG diagnostics to:
  • Audit traffic patterns and identify suspicious flows.
  • Feed logs into Traffic Analytics for visual analysis and reporting.
  • Retain flow data in a storage account for historical analysis.
A screenshot of the Microsoft Azure portal open to the Network Watcher "NSG diagnostics" page, showing form fields for target resource, protocol, direction, and IP/port details. The left sidebar lists monitoring and network diagnostic tools like IP flow verify, next hop, and packet capture.

Next Hop

The Next Hop tool shows the immediate routing decision Azure makes for a packet from a VM to a destination IP. Typical results include:
  • VirtualNetwork — destination inside the same VNet
  • Internet — traffic exits to the internet
  • VirtualAppliance — a user-defined route (UDR) sends traffic to a firewall or appliance (the UI will show the appliance IP and route table ID)
  • If a UDR is in effect, Next Hop displays the route table ID and the configured next hop. If the system route is used, it indicates the system route source.
Use Next Hop when you need to verify whether routing is following Azure’s system routes or your custom UDRs.

Effective Security Rules

When NSGs are applied at both subnet and NIC levels, the Effective Security Rules view shows the consolidated and ordered set of rules that actually apply to a network interface. This view is useful to determine exactly which rule will permit or block traffic for a given NIC.

VPN troubleshoot

VPN troubleshoot diagnoses VPN gateways and connections to on-premises networks. Select the VPN gateway and choose a storage account for results; the diagnostic run will capture metrics such as bandwidth, throughput, and packet failures. Save results to a storage account for later analysis and to share with support teams.

Packet capture

Use Packet Capture to capture traffic from a VM without installing tcpdump or Wireshark on the VM itself. Steps:
  1. Click Add to create a packet capture session.
  2. Select the target VM and a storage account to store the capture.
  3. Optionally add filters (for example, port 53 for DNS).
  4. Start the capture and stop when you have the required data.
  5. Download the PCAP file from the storage account and analyze it in Wireshark.
Ensure your account has permission to write to the selected storage account before starting packet capture or NSG diagnostics (for example, Storage Blob Data Contributor or equivalent).

Connection Troubleshoot (Connectivity checks)

Connection Troubleshoot runs a richer end-to-end connectivity test between two endpoints and returns a consolidated diagnostic including hop-by-hop details, next hop/route, NSG evaluation, port accessibility, and round-trip time. Example:
  • Source: a VM such as blue-01
  • Destination: another VM, IP address, or FQDN (manual entry is supported)
  • IP version: IPv4 or IPv6
  • Protocol: TCP or UDP
  • Destination port: e.g. 22
When the test completes you receive:
  • A connectivity status (reachable/unreachable)
  • Where traffic was blocked (NSG, UDR, or other)
  • Hop-by-hop information and latency (RTT)
  • Port accessibility results
A screenshot of the Microsoft Azure portal showing the Network Watcher "Connection troubleshoot" page with diagnostic test results. It shows successful connectivity checks between source "blue-01" and destination "jumpbox-vm," with hop-by-hop details and latency/probe statistics.
Use Connection Troubleshoot when you need a holistic view of the path and performance between two endpoints rather than a single NSG rule check.

Topology

Topology provides a visual representation of resources within a virtual network: VNets, subnets, network interfaces, public IPs, NSGs, gateways, and how they connect. Expanding a subnet reveals attached NICs and VMs plus IP configurations. Use this view to validate design, understand relationships, and quickly find misconfigurations. Tips for using topology:
  • Select a resource group or virtual network scope to narrow the diagram.
  • Expand nodes to reveal details such as NIC IPs and associated NSGs.
  • Use topology to confirm whether resources are attached to the expected subnets or network security groups.

Closing notes

Azure Network Watcher equips you with multiple complementary tools:
  • Use IP Flow Verify for quick NSG permit/deny checks.
  • Use Connection Troubleshoot for end-to-end path and performance diagnostics.
  • Use Next Hop to validate routing decisions and identify UDRs or virtual appliances.
  • Use NSG diagnostics/Flow Logs for traffic auditing and analytics.
  • Use Packet Capture for in-depth packet-level investigation.
With these tools you can monitor connectivity, validate security rules, capture traffic for forensic analysis, and visualize network architecture — completing the core set of Network Watcher features used in operations and exam scenarios.

Watch Video