Create Pull Request
| Date | Scan | Status | Result |
|---|---|---|---|
| 2026-01-14 00:00 | #250 | in_progress |
Biased
|
| 2026-01-13 00:00 | #246 | completed |
Biased
|
| 2026-01-11 00:00 | #240 | completed |
Biased
|
| 2026-01-10 00:00 | #237 | completed |
Biased
|
| 2026-01-09 00:34 | #234 | completed |
Biased
|
| 2026-01-08 00:53 | #231 | completed |
Biased
|
| 2026-01-06 18:15 | #225 | cancelled |
Clean
|
| 2025-08-17 00:01 | #83 | cancelled |
Clean
|
| 2025-07-13 21:37 | #48 | completed |
Clean
|
| 2025-07-12 23:44 | #41 | cancelled |
Biased
|
| 2025-07-09 13:09 | #3 | cancelled |
Clean
|
| 2025-07-08 04:23 | #2 | cancelled |
Biased
|
Locate the Azure Network Watcher extension in the output and identify the version number from the *“TypeHandlerVersion”* field in the output. You should see something like the below:  ### Update your extension If your version is below the latest version mentioned above, update your extension by using any of the following options. #### Option 1: Use PowerShell Run the following commands:
# [Windows](#tab/windows)
--- ## Update your extension using a PowerShell script If you have large deployments, use a PowerShell script to update multiple VMs at once. The following PowerShell script updates Network Watcher extension of all Windows VMs in a subscription:
Locate **"AzureNetworkWatcherExtension"** in the output and identify the version number from the *“TypeHandlerVersion”* field in the output. Information about the extension appears multiple times in the JSON output. The full version number of the extension is available under the Extensions block. You should see something like the below:  #### Use PowerShell Run the following commands from a PowerShell prompt: