Document Details
Diagnose Vm Network Routing Problem Powershell
❌
This page contains Windows bias
About This Page
This page is part of the Azure documentation. It contains code examples and configuration instructions for working with Azure services.
Bias Analysis
Bias Types:
⚠️
powershell_heavy
⚠️
windows_tools
⚠️
missing_linux_example
⚠️
windows_first
Summary:
The documentation exclusively uses Azure PowerShell cmdlets and Windows-oriented tooling (PowerShell, Azure Cloud Shell with PowerShell), with no mention or examples for Linux users (such as Azure CLI or Bash). All code samples and instructions are PowerShell-based, and there is no guidance for users who may prefer or require Linux-native tools or scripting environments.
Recommendations:
- Add equivalent Azure CLI (az) command examples for each PowerShell cmdlet shown, and present them alongside or before the PowerShell examples.
- Explicitly mention that Azure Cloud Shell supports both Bash and PowerShell, and provide instructions for both environments.
- Include guidance or links for Linux/macOS users on how to install and use Azure CLI, and how to perform the same diagnostics using CLI commands.
- Where possible, use neutral language that does not assume the user is on Windows or using PowerShell.
- Consider restructuring the article to present cross-platform solutions first (e.g., Azure CLI), or provide parallel sections for PowerShell and CLI/Bash.
Create pull request
Scan History
| Date | Scan ID | Status | Bias Status |
|---|---|---|---|
| 2025-08-17 00:01 | #83 | in_progress | ✅ Clean |
| 2025-07-13 21:37 | #48 | completed | ❌ Biased |
| 2025-07-12 23:44 | #41 | in_progress | ❌ Biased |
| 2025-07-09 13:09 | #3 | cancelled | ✅ Clean |
| 2025-07-08 04:23 | #2 | cancelled | ❌ Biased |
Flagged Code Snippets
Create the VM with [New-AzVM](/powershell/module/az.compute/new-azvm). When running this step, you are prompted for credentials. The values that you enter are configured as the user name and password for the VM.
If you don't already have a network watcher enabled in the East US region, use [New-AzNetworkWatcher](/powershell/module/az.network/new-aznetworkwatcher) to create a network watcher in the East US region:
The VM takes a few minutes to create. Don't continue with remaining steps until the VM is created and PowerShell returns output.
## Test network communication
To test network communication with Network Watcher, you must first enable a network watcher in the region the VM that you want to test is in, and then use Network Watcher's next hop capability to test communication.
## Enable network watcher
If you already have a network watcher enabled in the East US region, use [Get-AzNetworkWatcher](/powershell/module/az.network/get-aznetworkwatcher) to retrieve the network watcher. The following example retrieves an existing network watcher named *NetworkWatcher_eastus* that is in the *NetworkWatcherRG* resource group:
As you can see in the previous output, the route with the **AddressPrefix** of **0.0.0.0/0** routes all traffic not destined for addresses within other route's address prefixes with a next hop of **Internet**. As you can also see in the output, though there is a default route to the 172.16.0.0/12 prefix, which includes the 172.31.0.100 address, the **nextHopType** is **None**. Azure creates a default route to 172.16.0.0/12, but doesn't specify a next hop type until there is a reason to. If, for example, you added the 172.16.0.0/12 address range to the address space of the virtual network, Azure changes the **nextHopType** to **Virtual network** for the route. A check would then show **Virtual network** as the **nextHopType**.
## Clean up resources
When no longer needed, you can use [Remove-AzResourceGroup](/powershell/module/az.resources/remove-azresourcegroup) to remove the resource group and all of the resources it contains: