Study guide
8.5 Network Watcher: IP Flow, Next Hop, and Connection Troubleshoot
AZ-104 Microsoft Azure Administrator Study Guide Exam
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: Exam Orientation and Microsoft Learn Source Control
1.1 Current AZ-104 Exam Facts 1.2 Administrator Role and Candidate Profile 1.3 Skills Outline and Weighted Study Map 1.4 Exam Duration, Question Types, Labs, and Learn Access 1.5 Scoring, Retakes, Renewal, and Account Choice 1.6 Using the Practice Bank, Labs, and Error Log
2 Chapter 2: Identity, RBAC, and Governance Foundations
2.1 Microsoft Entra Users, Groups, and Properties 2.2 Licenses, External Users, and SSPR 2.3 Azure RBAC Built-In Roles and Scopes 2.4 Role Assignment Interpretation and Deny Effects 2.5 Management Groups, Subscriptions, and Resource Groups 2.6 Azure Policy, Locks, Tags, and Governance Controls 2.7 Identity and Governance Case Lab
3 Chapter 3: Subscriptions, Policy, Costs, and Resource Organization
3.1 Subscription Design and Management Groups 3.2 Resource Groups, Lifecycle, and Move Operations 3.3 Tagging Strategy and Cost Allocation 3.4 Budgets, Alerts, and Azure Advisor Cost Recommendations 3.5 Policy, Initiative, Assignment, and Remediation 3.6 Resource Locks, RBAC, Policy, and Tags Combined 3.7 Governance and Cost Case Lab
4 Chapter 4: Storage Accounts, Access, and Data Protection
4.1 Storage Account Design, Redundancy, and Encryption 4.2 Storage Firewalls, Private Access, and Network Rules 4.3 SAS Tokens, Stored Access Policies, and Access Keys 4.4 Identity-Based Access for Azure Files 4.5 Blob Tiers, Lifecycle, Soft Delete, and Versioning 4.6 Azure Files, Snapshots, File Sync, and AzCopy 4.7 Storage Case Lab
5 Chapter 5: Compute, Virtual Machines, Scale Sets, and Bicep
5.1 ARM Templates, Bicep, and Deployment Workflow 5.2 Create, Configure, and Manage Virtual Machines 5.3 VM Disks, Sizes, Encryption, and Host Settings 5.4 Availability Zones, Sets, and VM Scale Sets 5.5 Move VMs Across Resource Groups, Subscriptions, and Regions 5.6 Backup, Restore, and Operational Maintenance for VMs 5.7 VM Compute Case Lab
6 Chapter 6: Containers, App Service, and Platform Compute
6.1 Azure Container Registry and Image Workflow 6.2 Azure Container Instances and Container Apps 6.3 Container Sizing, Scaling, and Environment Choices 6.4 App Service Plan, Apps, and Runtime Configuration 6.5 App Service Certificates, TLS, Custom Domains, and Networking 6.6 App Service Backups, Deployment Slots, and Scaling 6.7 Platform Compute Case Lab
7 Chapter 7: Virtual Networking, Routing, and Secure Access
7.1 VNet, Subnet, and Address Space Design 7.2 VNet Peering and Cross-Network Connectivity 7.3 Public IP Addresses and NAT Patterns 7.4 User-Defined Routes and Effective Routes 7.5 NSGs, ASGs, and Effective Security Rules 7.6 Azure Bastion, Service Endpoints, and Private Endpoints 7.7 Secure Networking Case Lab
8 Chapter 8: Name Resolution, Load Balancing, and Connectivity Troubleshooting
8.1 Azure DNS, Private DNS, and Name Resolution 8.2 Public and Internal Load Balancer Design 8.3 Backend Pools, Health Probes, and Load Balancing Rules 8.4 Load Balancing Troubleshooting Workflow 8.5 Network Watcher: IP Flow, Next Hop, and Connection Troubleshoot 8.6 Hybrid Connectivity, VPN, ExpressRoute, and DNS Considerations 8.7 Connectivity Troubleshooting Case Lab
9 Chapter 9: Monitoring, Alerting, Backup, and Site Recovery
9.1 Azure Monitor Metrics, Logs, and Diagnostic Settings 9.2 Log Analytics, KQL, and Operational Queries 9.3 Alert Rules, Action Groups, and Alert Processing Rules 9.4 VM, Storage, and Network Insights 9.5 Recovery Services Vault, Backup Vault, and Backup Policies 9.6 Azure Site Recovery, Failover, and Replication 9.7 Monitoring and Recovery Case Lab
10 Chapter 10: AZ-104 Integration and Troubleshooting Case Labs
10.1 Domain Weight Triage and Study Prioritization 10.2 Identity, Storage, and Compute Integrated Cases 10.3 Networking, Monitoring, and Security Integrated Cases 10.4 Migration, Move, Backup, and Recovery Cases 10.5 Permissions, Network, and Storage Troubleshooting Chain 10.6 Microsoft Learn Lookup Strategy Under Time Pressure 10.7 Full-Domain Case Lab
11 Chapter 11: Final Review, Exam Experience, Renewal, and Career Path
11.1 Final Two-Week Study Plan 11.2 Hands-On Lab Checklist and Command Review 11.3 Exam Day, Pearson VUE, Breaks, and Learn Access 11.4 Retake Plan, Score Report, and Weak-Domain Repair 11.5 Renewal Assessment and Annual Certification Maintenance 11.6 After AZ-104: AZ-305, AZ-400, SC-500, and Job Paths
8.5 Network Watcher: IP Flow, Next Hop, and Connection Troubleshoot
Key Takeaways Explain This Topic AI
Network Watcher provides diagnostic tools for security rules, routes, connectivity, packet capture, topology, and monitoring.
IP flow verify evaluates whether NSG rules allow or deny a specific 5-tuple for a VM.
Next hop identifies the route Azure selects from a source VM to a destination IP.
Connection troubleshoot tests reachability and reports failure causes such as DNS, TCP, NSG, route, or listener issues.
Use Network Watcher results together with guest OS and application checks for complete troubleshooting.
Last updated: May 2026
Network Watcher in the administrator toolbox
Network Watcher is Azure's regional network diagnostic and monitoring service. It helps administrators inspect packet permission, routing, topology, connectivity, packet captures, VPN diagnostics, and long-running connection monitoring. AZ-104 does not require you to memorize every field in every output, but you should know which tool answers the operational question.
The three tools most tied to connectivity troubleshooting are IP flow verify, next hop, and connection troubleshoot. IP flow verify asks, Would an NSG allow this traffic to or from this VM? Next hop asks, Which route will Azure use from this VM to that destination? Connection troubleshoot asks, Can this source reach that destination on this protocol and port, and what failed if not?
Question Network Watcher tool Typical result
Is an NSG blocking TCP 443 from a source to this VM? IP flow verify Allowed or denied, with rule name.
Where does Azure route traffic from VM1 to 10.30.1.5? Next hop Virtual network, Internet, virtual appliance, gateway, or none.
Can VM1 connect to app.contoso.com on port 443? Connection troubleshoot Reachable or unreachable with hop and failure details.
What changed in effective rules? Effective security rules Combined NSG rules from subnet and NIC.
What route table is actually effective? Effective routes System routes, BGP routes, and UDRs applied to a NIC.
Need continuous path monitoring Connection Monitor Historical latency, reachability, and test results.
IP flow verify
IP flow verify evaluates NSG processing for a VM. You provide direction, protocol, local IP and port, remote IP and port, and the VM. The result says whether traffic is allowed or denied and which NSG rule caused the decision. This is excellent when a question says connectivity fails after an NSG change.
- Example: az network watcher test-ip-flow \
- -resource-group rg-network \
- -vm vm-web-1 \
- -direction Inbound \
- -protocol TCP \
- -local 10.20.2.4:443 \
- -remote 198.51.100.25:51515
If the result is denied by DenyAllInBound , you need an allow rule with higher priority than the default deny. If the result is denied by a custom rule, inspect priority, source, destination, protocol, and port. Remember that NSGs can apply at the subnet and NIC. Effective security rules combine both, so a rule in either place can affect the flow.
Limitations matter. IP flow verify evaluates NSG logic; it does not prove the application is listening, DNS is correct, or a firewall appliance allows the flow. If IP flow verify says allowed but the app is still unreachable, continue to route, guest firewall, and listener checks.
Next hop
Next hop shows how Azure routes traffic from a VM to a destination IP. It is useful when a UDR, forced tunneling, peering, VPN, ExpressRoute, or virtual appliance might be involved. The output can identify next hop types such as virtual network, internet, virtual network gateway, virtual appliance, or none.
- Example: az network watcher show-next-hop \
- -resource-group rg-network \
- -vm vm-web-1 \
- -source-ip 10.20.2.4 \
- -dest-ip 10.50.1.10
If the next hop is a virtual appliance, verify the appliance route, firewall policy, and return path. If the next hop is internet when you expected VPN or ExpressRoute, inspect route tables, propagated routes, BGP, peering settings, and address prefix overlap. If the next hop is none, a route is missing or invalid for that destination.
Next hop is especially useful for private endpoint and hybrid cases. If DNS resolves to a private endpoint IP but next hop does not stay inside the private network, the routing design needs attention. If an on-premises prefix is learned through ExpressRoute but a UDR overrides it to a firewall, the route table explains the behavior.
Connection troubleshoot and Connection Monitor
Connection troubleshoot performs an active test from a source to a destination. The source can be an Azure VM in many common cases, and the destination can be an IP, FQDN, or URI depending on the interface. It helps identify whether failure is due to DNS, TCP connectivity, routing, NSG blocking, or endpoint refusal.
Portal path: Network Watcher > Connection troubleshoot . Choose source, destination, protocol, and port. For repeated monitoring, use Network Watcher > Connection Monitor to create test groups, sources, destinations, and test configurations.
Connection Monitor is better when the problem is intermittent. A single test may pass during a quiet period, but historical data can show packet loss, latency spikes, or failures during a deployment window. For AZ-104, recognize that Connection Monitor is not only a one-time ping; it is used to monitor connectivity between endpoints over time.
Effective rules and routes
When a single NSG or route table looks correct, the effective view may still reveal the problem. Effective security rules show the combined result of subnet-level and NIC-level NSGs. Effective routes show system routes, BGP routes, and user-defined routes that apply to a NIC.
Portal paths:
- Need Portal path
- Combined NSG rules VM > Networking > Effective security rules
- Effective routes Network interface > Effective routes or Network Watcher route tools
- One flow NSG decision Network Watcher > IP flow verify
- One route decision Network Watcher > Next hop
- End-to-end reachability Network Watcher > Connection troubleshoot
- Practical diagnostic sequence Connectivity failure to VM or service
|-- Does DNS resolve as expected from the source?
|-- Does IP flow verify allow the flow at the VM NSG layer?
|-- Does next hop show the expected route from source to destination?
|-- Does connection troubleshoot report reachable?
|-- Does the destination OS firewall allow the port?
|-- Is the application listening on the destination IP and port?
|-- Do return routes and stateful firewalls allow the response?
Use Network Watcher to narrow the Azure control plane view, then use guest tools to confirm runtime behavior. On the guest, use Test-NetConnection , curl , ss , netstat , logs, and service status. A clean Azure path does not prove the app is healthy.
Exam traps
Do not use IP flow verify to troubleshoot DNS. Do not use next hop to prove an NSG allow. Do not assume ping failure means TCP failure, because ICMP may be blocked while TCP 443 works. Do not overlook regional availability of Network Watcher resources; in normal Azure operations, ensure Network Watcher is enabled in the relevant region.
A frequent scenario says VM1 cannot connect to VM2 after a route table was added. The best first tool is next hop, not IP flow verify, because the change was routing. If the scenario says access failed after a new NSG rule, IP flow verify is the better first test.