Merge pull request #232442 from halkazwini/nw-hop

Introduction to Azure Network Watcher next hop

Author: Jill Grant

articles/network-watcher/media/network-watcher-next-hop-overview/figure1.png

@@ -1,24 +1,26 @@
 ---
-title: Introduction to Azure Network Watcher next hop
+title: Next hop
+titleSuffix: Azure Network Watcher
 description: Learn about Azure Network Watcher next hop capability that you can use to diagnose virtual machine routing problems.
 services: network-watcher
 author: halkazwini
-ms.assetid: febf7bca-e0b7-41d5-838f-a5a40ebc5aac
 ms.service: network-watcher
 ms.topic: conceptual
 ms.workload: infrastructure-services
-ms.date: 01/29/2020
+ms.date: 03/28/2023
 ms.author: halkazwini
-ms.custom: engagement-fy23
+ms.custom: template-concept, engagement-fy23
 ---
 
-# Introduction to Azure Network Watcher next hop
+# Azure Network Watcher next hop
 
-Traffic from a virtual machine (VM) is sent to a destination based on the effective routes associated with a network interface (NIC). Next hop gets the next hop type and IP address of a packet from a specific VM and NIC. Knowing the next hop helps you determine if traffic is being directed to the intended destination, or whether the traffic is being sent nowhere. An improper configuration of routes,  where traffic is directed to an on-premises location, or a virtual appliance, can lead to connectivity issues. Next hop also returns the route table associated with the next hop. If the route is defined as a user-defined route, that route is returned. Otherwise, next hop returns **System Route**.
+Traffic from a virtual machine (VM) is sent to a destination based on the effective routes associated with the virtual machines' network interface (NIC). Azure Network Watcher next hop gives you the *Next hop type*, *IP address*, and *Route table ID* of a specific destination IP address. Knowing the next hop helps you determine if traffic is being directed to the intended destination, or whether the traffic is being sent nowhere. An improper configuration of routes, where traffic is directed to an on-premises location, or a network virtual appliance, can lead to connectivity issues. If the route is defined using a user-defined route, the route table that has the route is returned. Otherwise, next hop returns *System Route* as the route table.
 
-![next hop overview](./media/network-watcher-next-hop-overview/figure1.png)
+:::image type="content" source="./media/network-watcher-next-hop-overview/next-hop-view.png" alt-text="Screenshot of Azure Network Watcher next hop view in Azure portal.":::
 
-The next hops that might be returned by the next hop capability are as follows:
+## Next hop types
+
+Network Watcher returns the following next hop types:
 
 * Internet
 * VirtualAppliance
@@ -29,8 +31,8 @@ The next hops that might be returned by the next hop capability are as follows:
 * MicrosoftEdge
 * None
 
-To learn more about each next hop type, see [Routing overview](../virtual-network/virtual-networks-udr-overview.md?toc=%2fazure%2fnetwork-watcher%2ftoc.json).
+To learn more about each next hop type, see [Virtual network traffic routing](../virtual-network/virtual-networks-udr-overview.md?toc=%2fazure%2fnetwork-watcher%2ftoc.json).
 
 ## Next steps
 
-To learn how to use next hop to diagnose VM network routing problems, see Diagnose VM network routing problems using the [Azure portal](diagnose-vm-network-routing-problem.md), [PowerShell](diagnose-vm-network-routing-problem-powershell.md), or the [Azure CLI](diagnose-vm-network-routing-problem-cli.md).
+To learn how to use next hop to diagnose virtual machine routing problems, see Diagnose VM network routing problems using the [Azure portal](diagnose-vm-network-routing-problem.md), [PowerShell](diagnose-vm-network-routing-problem-powershell.md), or the [Azure CLI](diagnose-vm-network-routing-problem-cli.md).