Azure networking problems are easier to diagnose when monitoring and troubleshooting tools are used for the jobs they were designed to perform.<\/p>\n
Azure Monitor<\/strong> collects and analyzes telemetry such as metrics and logs and can trigger alerts.<\/p>\n Azure Network Watcher<\/strong> provides networking-specific diagnostic capabilities.<\/p>\n Connection Monitor<\/strong> continuously tests connectivity and measures characteristics such as latency and packet loss between endpoints.<\/p>\n Network Watcher helps turn a connectivity complaint into evidence about routes, packet filtering and connection paths. Suppose a virtual machine can resolve a service name but cannot connect to the expected port. First inspect the effective route and next hop, then the effective NSG rule, source\/destination scope and application listener. A successful DNS response proves neither that a route is valid nor that a firewall permits traffic. In independent AZ-104 networking practice<\/a> scenarios, the right administrative action follows the failing layer; opening every port or replacing a route table may hide the cause and expose unrelated resources. Record the original configuration and a rollback path before changing network controls, especially when the tested workload shares a subnet with production systems.<\/p>\n Azure Monitor is the general telemetry platform.<\/p>\n Microsoft describes it as a service for collecting, analyzing, and acting on metrics, logs, and traces from Azure and hybrid environments.<\/p>\n For networking, Azure Monitor can collect platform metrics and resource logs from services such as:<\/p>\n It can also generate alerts when telemetry crosses a threshold or matches a query.<\/p>\n This makes Azure Monitor a strong starting point when the problem was first detected through health, performance, or alerting.<\/p>\n Azure monitoring<\/a> can show that a resource or dependency degraded, but Network Watcher investigates whether the actual network path explains the symptom. Correlate metric and log timestamps first, then use connection tests, effective routes and NSG rules from the affected endpoints. A network test that succeeds after the incident cannot retroactively prove reachability at the earlier failure time.<\/p>\n Start by fixing the time window and blast radius. Azure Monitor can show whether a metric, resource-health event, configuration change, or alert began at the same time as the reported failure. Comparing one affected VM with an unaffected peer helps determine whether the problem is local to an interface, subnet, or route path or belongs to a shared network service.<\/p>\n Metrics and logs should narrow the investigation before packet-level tools are used. A gateway throughput change, load-balancer health-probe failure, or firewall event can point directly to the failing component. If broad telemetry is normal and one source-to-destination flow is failing, Network Watcher becomes the more precise next step.<\/p>\n Network Watcher is focused on Azure networking.<\/p>\n Its capabilities help answer questions such as:<\/p>\n The right Network Watcher tool depends on the question.<\/p>\n Do not run every diagnostic at once.<\/p>\n Start with the symptom and select the evidence that can prove or disprove the likely failure.<\/p>\n Network Watcher provides several diagnostics that answer different questions. IP flow verify<\/strong> and NSG diagnostics<\/strong> help determine whether security rules allow or deny a flow. Next hop<\/strong> helps confirm the routing decision for a destination. Effective routes and effective security rules show the configuration Azure has actually applied to a network interface rather than only the administrator’s intended design. VPN troubleshoot targets gateway and connection problems.<\/p>\nStart with Azure Monitor for the broad operational signal<\/h2>\n
\n
Network Watcher provides network-specific diagnostics<\/h2>\n
\n