Skip to content

Commit f0b5b5c

Browse files
Merge pull request #296930 from halkazwini/nw-hop
Freshness: Next hop overview
2 parents 6ab5f01 + 0296536 commit f0b5b5c

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

articles/network-watcher/next-hop-overview.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ author: halkazwini
66
ms.author: halkazwini
77
ms.service: azure-network-watcher
88
ms.topic: concept-article
9-
ms.date: 03/13/2024
9+
ms.date: 03/25/2025
1010

1111
#CustomerIntent: As an Azure administrator, I want to learn about Next hop feature so I can use it to get the next hop information of any virtual machine (VM) experiencing routing issues to be able to diagnose and fix the issue.
1212
---
@@ -17,7 +17,6 @@ Next hop is a feature of Azure Network Watcher that gives you the *Next hop type
1717

1818
If the route is defined using a user-defined route, next hop returns the route table that has the route. Otherwise, it returns *System Route* as the route table.
1919

20-
2120
:::image type="content" source="./media/next-hop-overview/next-hop-view.png" alt-text="Screenshot of Azure Network Watcher next hop view in Azure portal.":::
2221

2322
## Next hop types
@@ -37,4 +36,5 @@ To learn more about each next hop type, see [Virtual network traffic routing](..
3736

3837
## Next step
3938

40-
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).
39+
> [!div class="nextstepaction"]
40+
> [Diagnose a virtual machine network routing problem](diagnose-vm-network-routing-problem.md)

0 commit comments

Comments
 (0)