Network Watcher

64
Total Pages
28
Linux-Friendly Pages
36
Pages with Bias
56.2%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

238 issues found
Showing 51-75 of 238 flagged pages
Network Watcher https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/network-watcher/network-watcher-visualize-nsg-flow-logs-power-bi.md ...er/network-watcher-visualize-nsg-flow-logs-power-bi.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page focuses exclusively on using Power BI Desktop, a Windows-centric tool, for visualizing Azure NSG flow logs. All setup and usage instructions assume the reader is using Windows, with no mention of Linux-compatible alternatives or cross-platform approaches. There are no examples or guidance for Linux users, nor are open-source or cross-platform visualization tools discussed until the 'Next steps' section, which is secondary to the main content.
Recommendations
  • Include instructions or examples for visualizing NSG flow logs using Power BI on non-Windows platforms, such as Power BI web or Power BI on Mac (if available).
  • Provide parallel examples using open-source, cross-platform tools (e.g., Grafana, Kibana/Elastic Stack) within the main body of the documentation, not just as a 'Next steps' link.
  • Explicitly mention platform requirements and alternatives at the beginning of the article, so Linux and Mac users are aware of their options.
  • Add a comparison table of visualization tools, indicating OS compatibility and feature parity.
  • Offer guidance for exporting or transforming NSG flow logs for use in Linux-friendly BI or visualization tools.
GitHub Create Pull Request
Network Watcher https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/network-watcher/nsg-flow-logs-migrate.md ...main/articles/network-watcher/nsg-flow-logs-migrate.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by exclusively providing migration instructions and examples using PowerShell scripts (.ps1), with no mention or examples of Bash, Azure CLI, or Linux-native scripting alternatives. The prerequisites and migration steps center around PowerShell, which is traditionally associated with Windows, even though PowerShell Core is cross-platform. There is no guidance for users who prefer or require Linux-native tools, and the script file provided is a PowerShell script only.
Recommendations
  • Provide equivalent migration instructions using Azure CLI commands and Bash scripts, which are more native to Linux environments.
  • Explicitly mention that PowerShell Core is cross-platform, but also offer Linux-specific setup steps and troubleshooting tips.
  • Include examples of running the migration process on Linux and macOS, not just Windows.
  • Offer a downloadable Bash or Python script alternative for users who do not use PowerShell.
  • Clarify any platform-specific limitations or considerations for running the migration on Linux or macOS.
GitHub Create Pull Request
Network Watcher https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/network-watcher/nsg-flow-logs-overview.md ...ain/articles/network-watcher/nsg-flow-logs-overview.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page exhibits Windows bias in several areas. PowerShell is the only CLI tool shown for configuring NSG flow log properties (specifically, setting FlowTimeoutInMinutes), with no Bash, Azure CLI, or Linux-native examples. The troubleshooting and workflow sections reference PowerShell and Windows-centric tools first or exclusively. There are no explicit Linux or cross-platform command-line examples for managing or analyzing NSG flow logs, and the use of Windows tools (such as PowerShell and Power BI) is mentioned before or instead of Linux alternatives.
Recommendations
  • Add Azure CLI and Bash examples alongside PowerShell for all configuration and management tasks, especially for setting properties like FlowTimeoutInMinutes.
  • Explicitly mention Linux-compatible tools and workflows for reading, exporting, and analyzing NSG flow logs (e.g., jq, grep, Azure CLI, Python scripts).
  • Ensure that visualization and export guides include Linux-first or cross-platform instructions, not just Power BI or Windows-centric tools.
  • Where possible, provide parity in troubleshooting steps for Linux users (e.g., using Azure CLI or REST API calls).
  • Review and update all references to tools and patterns to ensure Linux and cross-platform options are presented equally or before Windows-specific ones.
GitHub Create Pull Request
Network Watcher https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/network-watcher/packet-capture-alert-triggered.md ...cles/network-watcher/packet-capture-alert-triggered.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exhibits a strong Windows bias, primarily through exclusive use of PowerShell for all code examples and automation steps. All authentication, environment variable setup, and packet capture initiation are demonstrated only with PowerShell scripts and cmdlets, which are native to Windows. There is no mention or example of equivalent Bash, CLI, or Python approaches suitable for Linux users. The prerequisites and extension setup mention both Windows and Linux, but all actionable guidance and scripting is Windows-centric, and Windows tools (e.g., PowerShell, Windows file paths) are used throughout.
Recommendations
  • Provide equivalent examples using Bash scripts and Azure CLI commands for Linux users.
  • Include authentication setup instructions for Linux environments, such as using service principal credentials with Azure CLI.
  • Show how to automate packet capture initiation using Azure CLI or REST API, with sample scripts in Bash or Python.
  • Clarify cross-platform compatibility for Azure Functions, including how to use non-PowerShell runtimes (e.g., Python, Node.js) for the automation.
  • When referencing file paths or tools, use platform-neutral or Linux-specific examples alongside Windows ones.
  • Explicitly state that the process can be performed from Linux and provide links or sections for Linux workflows.
GitHub Create Pull Request
Network Watcher https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/network-watcher/nsg-flow-logs-template.md ...ain/articles/network-watcher/nsg-flow-logs-template.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page exclusively uses Azure PowerShell for deployment instructions, with no mention of cross-platform alternatives such as Azure CLI or Bash. The example command uses Windows-style file paths and assumes a local PowerShell environment, which may not be available or preferred on Linux or macOS systems. There are no Linux-specific instructions, examples, or references to Linux tools.
Recommendations
  • Add equivalent Azure CLI examples for template deployment, which are cross-platform and commonly used on Linux and macOS.
  • Include Bash shell command examples for saving and deploying ARM templates.
  • Use platform-neutral file paths in examples (e.g., ./azuredeploy.json instead of C:\MyTemplates\azuredeploy.json).
  • Explicitly mention that the instructions can be followed on Linux/macOS using Azure CLI or PowerShell Core, and provide links to relevant setup guides.
  • Consider a 'Choose your platform' section at the start of the deployment instructions, allowing users to select Windows/PowerShell or Linux/Azure CLI paths.
GitHub Create Pull Request
Network Watcher https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/network-watcher/packet-capture-manage.md ...main/articles/network-watcher/packet-capture-manage.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation shows a moderate Windows bias. PowerShell is featured prominently as a primary automation method, and examples for downloading files use Windows-style paths (e.g., C:\Capture\myVM_1.cap) before mentioning Linux equivalents. References to Windows file paths and tools (such as Storage Explorer) are given without equal emphasis on Linux alternatives. There are no explicit Linux shell (bash) examples for file operations, and the documentation does not provide parity for Linux-specific workflows, such as using SCP or Linux-native tools for file download and management.
Recommendations
  • Provide Linux shell (bash) examples alongside PowerShell, especially for file download and management (e.g., using wget, curl, or scp).
  • List Linux file path examples before or alongside Windows paths, not after.
  • Mention Linux-native tools for storage access (e.g., AzCopy, rclone, or mounting blob storage via fuse) in addition to Storage Explorer.
  • Clarify that Azure CLI and PowerShell are cross-platform, but show examples of running commands on both Windows and Linux terminals.
  • Add explicit instructions for connecting to Linux VMs and retrieving packet capture files using SSH/SCP.
  • Ensure screenshots and step-by-step instructions reflect both Windows and Linux environments where applicable.
GitHub Create Pull Request
Network Watcher https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/network-watcher/vnet-flow-logs-manage.md ...main/articles/network-watcher/vnet-flow-logs-manage.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation provides parity between Azure Portal, PowerShell, and Azure CLI for all major operations. However, there is a noticeable bias toward Windows/PowerShell: PowerShell is given equal prominence to Azure CLI, despite being primarily a Windows tool, and all scripting examples use PowerShell or Azure CLI, with no mention of Bash, Linux shell, or cross-platform scripting patterns. Additionally, references to running PowerShell locally and using Windows-centric tools (e.g., Storage Explorer) appear before or without Linux alternatives. There is no explicit mention of Linux-specific instructions, nor are Bash examples provided, which may disadvantage Linux users.
Recommendations
  • Add explicit Bash examples for Azure CLI commands, demonstrating usage in Linux/macOS terminals.
  • Clarify that Azure CLI commands are cross-platform and can be run natively on Linux/macOS, not just in Cloud Shell.
  • Mention Linux-native tools for blob access (e.g., azcopy, curl, or s3cmd) alongside Storage Explorer.
  • Include instructions for installing and using Azure CLI on Linux/macOS, with links to relevant documentation.
  • Avoid presenting PowerShell as the default scripting option; instead, highlight Azure CLI and Bash as first-class, cross-platform choices.
  • Where PowerShell is referenced, add notes about its availability on Linux/macOS, or suggest Bash/CLI alternatives.
GitHub Create Pull Request
Network Watcher https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/network-watcher/vnet-flow-logs-filtering.md ...n/articles/network-watcher/vnet-flow-logs-filtering.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation exclusively provides Azure PowerShell examples for managing and filtering virtual network flow logs, with no mention of equivalent Azure CLI (cross-platform) or Bash examples. All command-line instructions use PowerShell cmdlets, which are most commonly used on Windows, and there is no guidance for Linux or macOS users. This creates a strong Windows bias and may hinder accessibility for users on non-Windows platforms.
Recommendations
  • Add equivalent Azure CLI examples for all PowerShell cmdlets shown, using az network watcher flow-log commands.
  • Explicitly mention that Azure CLI is available and supported on Linux, macOS, and Windows.
  • Provide Bash script examples where appropriate, especially for automation scenarios.
  • Reorder examples so that cross-platform (CLI) instructions are presented before or alongside PowerShell examples.
  • Include a section on platform compatibility and recommend tools for Linux/macOS users.
GitHub Create Pull Request
Network Watcher https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/network-watcher/vnet-flow-logs-managed-identity.md ...les/network-watcher/vnet-flow-logs-managed-identity.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exclusively uses Azure PowerShell cmdlets for all examples and instructions, with explicit references to Azure PowerShell and Cloud Shell. There are no CLI (az), Bash, or Linux-native examples provided, and all prerequisite links and instructions default to PowerShell-based workflows. This presents a strong Windows bias, making it less accessible for Linux users or those who prefer cross-platform tools.
Recommendations
  • Add equivalent Azure CLI (az) examples for all PowerShell cmdlets, including creating and managing flow logs with managed identities.
  • Update prerequisite links to include both PowerShell and Azure CLI tabs, ensuring parity for Linux and macOS users.
  • Mention Bash and Linux shell environments as alternatives to Cloud Shell or PowerShell, and clarify that Azure CLI is fully supported on Linux.
  • Where possible, provide code blocks for both PowerShell and CLI, and order them so that CLI/Bash examples are presented first or side-by-side with PowerShell.
  • Review related content and ensure tutorials and guides offer cross-platform instructions, not just Windows/PowerShell-centric workflows.
GitHub Create Pull Request
Network Watcher https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/network-watcher/vnet-flow-logs-tutorial.md ...in/articles/network-watcher/vnet-flow-logs-tutorial.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The tutorial exhibits Windows bias by exclusively using a Windows Server VM image, guiding users to connect via RDP (a Windows protocol), and referencing Microsoft Edge as the browser to test outbound connectivity. There are no instructions or examples for deploying a Linux VM, connecting via SSH, or using Linux-native tools. The documentation does not mention Linux alternatives or provide parity in examples for Linux users.
Recommendations
  • Include steps for creating a Linux VM (e.g., Ubuntu) alongside the Windows VM example.
  • Provide instructions for connecting to the Linux VM using SSH, including opening port 22 and using SSH clients.
  • Offer examples of viewing flow logs using Linux-native tools (e.g., cat, jq, less) and mention Linux-compatible browsers for connectivity tests.
  • Clarify that the tutorial applies to both Windows and Linux VMs, and note any differences in setup or connectivity.
  • Add screenshots and step-by-step guidance for Linux scenarios where relevant.
GitHub Create Pull Request
Network Watcher https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/network-watcher/vpn-troubleshoot-powershell.md ...rticles/network-watcher/vpn-troubleshoot-powershell.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page exclusively uses PowerShell for all troubleshooting examples and instructions, with no Azure CLI, Bash, or Linux-native command examples provided. The prerequisites and workflow are centered around Azure PowerShell and Cloud Shell, which, while available on Linux, are more closely associated with Windows environments. There is no mention or demonstration of Linux-specific tools, nor are Linux command-line patterns shown. The related content section does link to an Azure CLI-based guide, but this page itself is entirely PowerShell-focused.
Recommendations
  • Add equivalent Azure CLI examples alongside PowerShell for all troubleshooting steps.
  • Explicitly mention that Azure Cloud Shell supports Bash and Azure CLI, and provide instructions for those environments.
  • Include Linux-native workflow notes, such as using Bash in Cloud Shell or running Azure CLI locally on Linux.
  • Ensure that prerequisites and setup instructions cover both PowerShell and CLI/Bash environments equally.
  • Consider reordering or parallelizing examples so that Windows/PowerShell and Linux/CLI approaches are presented side-by-side.
GitHub Create Pull Request
Network Watcher https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/network-watcher/vpn-troubleshoot-overview.md .../articles/network-watcher/vpn-troubleshoot-overview.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates several forms of Windows bias. PowerShell is mentioned as a primary method for invoking VPN troubleshoot, and in the 'Considerations' section, PowerShell is recommended for scenarios where Azure CLI is insufficient. Log file examples and error messages reference Windows-specific error codes and terminology (e.g., 'Windows error 13801'), and log paths use Windows-style notation (e.g., 'C:\Resources\...'). There are no Linux-specific troubleshooting examples, log formats, or references to Linux tools or error codes. The documentation does not provide parity for Linux administrators or environments.
Recommendations
  • Include Linux-specific troubleshooting examples, such as using Azure CLI from Linux shells and handling log files on Linux systems.
  • Reference Linux error codes and terminology where applicable, or provide mappings between Windows and Linux errors.
  • Show log file paths and handling in Linux format (e.g., '/home/user/...') alongside Windows examples.
  • Mention Linux tools (such as azcopy, curl, or native blob download methods) for downloading logs from Azure Storage.
  • Clarify whether the troubleshooting logs and formats are compatible with Linux-based VPN devices and how Linux admins should interpret them.
  • Ensure that PowerShell and Windows recommendations are balanced with equivalent Linux guidance, and avoid suggesting Windows tools as the only or preferred solution.
GitHub Create Pull Request
Network Watcher https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/network-watcher/connection-monitor-connected-machine-agent.md ...-watcher/connection-monitor-connected-machine-agent.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a Windows bias by presenting Windows instructions and tools (PowerShell, Windows Admin Center) before or more prominently than Linux equivalents. PowerShell is highlighted as a cross-platform onboarding tool, but Linux-specific automation (e.g., Bash, shell scripting) is not equivalently covered. Windows Admin Center is mentioned as a dedicated tool for Windows, with no Linux GUI alternatives referenced. The Linux installation steps are brief and lack detail compared to the Windows instructions.
Recommendations
  • Provide Linux installation examples with equal detail and step-by-step instructions, including common Linux distributions and package managers.
  • Highlight Linux automation options (e.g., Bash scripts, Ansible, cloud-init) alongside PowerShell.
  • Mention and link to Linux-native management tools or GUIs if available, or clarify parity in tooling.
  • Present Windows and Linux instructions in parallel or side-by-side tabs, ensuring neither is prioritized.
  • Include troubleshooting and verification steps for Linux environments, not just Windows.
  • Clarify that PowerShell is available on Linux, and provide explicit Linux usage examples if recommending PowerShell.
GitHub Create Pull Request
Network Watcher https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/network-watcher/connection-monitor-overview.md ...rticles/network-watcher/connection-monitor-overview.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation demonstrates a moderate Windows bias. Windows and PowerShell are mentioned before Linux and Azure CLI in several places, such as in agent installation and automation. Example links and references prioritize Windows (e.g., 'Manage Network Watcher extension for Windows' is listed before Linux). There is a lack of explicit Linux command examples, and PowerShell is highlighted as a primary automation method, with Azure CLI and ARM templates mentioned but not equally emphasized. Windows-specific tools and troubleshooting patterns (e.g., certificate store references) are present, while Linux equivalents are not described.
Recommendations
  • Ensure Linux and Windows instructions/examples are presented side-by-side or with equal prominence.
  • Provide explicit Linux command-line examples (e.g., Bash, Azure CLI) wherever PowerShell is shown.
  • Mention Linux tools and troubleshooting patterns (e.g., OpenSSL, Linux certificate stores) alongside Windows-specific ones.
  • When listing links or references, alternate the order or group by OS rather than listing Windows first.
  • Clarify that automation can be performed equally with Azure CLI, Bash scripts, and Terraform, not just PowerShell.
  • Add troubleshooting steps and diagnostic messages relevant to Linux environments.
GitHub Create Pull Request
Network Watcher https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/network-watcher/network-watcher-agent-update.md ...ticles/network-watcher/network-watcher-agent-update.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias in several ways. The bulk of the scripted automation example is provided only in PowerShell, which is a Windows-centric tool, and the script is explicitly described as updating Windows VMs. There is no equivalent Bash or shell script for Linux automation. In manual update instructions, PowerShell is presented first and in greater detail, with CLI examples following. The documentation also references Windows tools and patterns (e.g., PowerShell, Windows VM detection) more frequently and with more depth than Linux equivalents.
Recommendations
  • Provide a Bash or shell script example for bulk updating the Network Watcher extension on Linux VMs, similar to the PowerShell script for Windows.
  • Ensure that CLI examples are presented before or alongside PowerShell examples to avoid Windows-first ordering.
  • Where PowerShell is used, clarify cross-platform availability or provide alternatives for Linux users (e.g., Azure CLI, Bash).
  • Balance screenshots and walkthroughs to show both Linux and Windows environments.
  • Explicitly mention and demonstrate Linux-specific troubleshooting or update patterns where applicable.
GitHub Create Pull Request
Network Watcher https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/network-watcher/diagnose-vm-network-traffic-filtering-problem-powershell.md ...agnose-vm-network-traffic-filtering-problem-powershell.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page exclusively uses Azure PowerShell cmdlets for all examples and instructions, with no mention or examples of Azure CLI, Bash, or Linux-native tooling. The prerequisites and workflow are centered around PowerShell, which is traditionally associated with Windows environments, even though Azure Cloud Shell supports Bash and Linux users. There are no Linux-specific instructions, nor is parity demonstrated for users who prefer non-PowerShell workflows.
Recommendations
  • Provide equivalent Azure CLI (az) commands for each PowerShell example, especially for resource creation, IP flow verification, and cleanup.
  • Explicitly mention that Azure Cloud Shell supports Bash and show how to select Bash in addition to PowerShell.
  • Add a section or callout for Linux users, clarifying how to perform the same tasks using Bash and Azure CLI.
  • Ensure that references to installing tools locally include instructions for both PowerShell (Windows/macOS/Linux) and Azure CLI (cross-platform).
  • Where possible, avoid language that implies PowerShell is the default or preferred option; present both PowerShell and CLI options side-by-side.
GitHub Create Pull Request
Network Watcher https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/network-watcher/network-watcher-agent-linux.md ...rticles/network-watcher/network-watcher-agent-linux.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page, while focused on Linux, repeatedly prioritizes Azure PowerShell (a Windows-centric tool) in its examples and instructions. PowerShell is mentioned before Azure CLI in several places, and the prerequisites and deployment steps emphasize PowerShell usage, including instructions for installing it locally. There is also a mistaken reference to 'Network Watcher Agent for Windows' in the Azure CLI install example. The documentation does not provide any native Linux shell (bash) or scripting examples, and relies exclusively on Windows-oriented tools (PowerShell, Azure CLI, Portal).
Recommendations
  • Provide native bash examples for Linux users, especially for local management scenarios.
  • Ensure Azure CLI is presented before PowerShell in Linux-focused documentation, as CLI is more platform-agnostic.
  • Remove or correct references to 'Network Watcher Agent for Windows' in CLI examples.
  • Clarify that PowerShell is cross-platform, but recommend CLI or bash for Linux users.
  • Add instructions for using REST API or SDKs from Linux environments.
  • Explicitly mention that all steps can be performed from Linux terminals, and provide guidance for installing and using Azure CLI on Linux.
GitHub Create Pull Request
Network Watcher https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/network-watcher/migrate-to-connection-monitor-from-connection-monitor-classic.md ...-to-connection-monitor-from-connection-monitor-classic.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates Windows bias by listing 'Automation – PowerShell, the Azure CLI, Terraform' with PowerShell mentioned first, and by not providing any Linux-specific examples or instructions. There are no references to Linux command-line tools or shell scripts, and the migration steps do not mention Linux environments or provide parity for Linux users.
Recommendations
  • List automation options in a neutral or rotating order (e.g., 'Azure CLI, PowerShell, Terraform') to avoid Windows-first bias.
  • Provide explicit Linux examples, such as Bash scripts or Azure CLI commands run from a Linux shell, for migration and automation tasks.
  • Include references to Linux tools and environments where relevant, such as instructions for installing the Network Watcher extension on Linux VMs.
  • Clarify that all steps and features apply equally to Linux and Windows VMs, and highlight any differences or considerations for Linux users.
  • Add troubleshooting steps or error messages specific to Linux environments if applicable.
GitHub Create Pull Request
Network Watcher https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/network-watcher/connection-monitor-overview.md ...rticles/network-watcher/connection-monitor-overview.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. References to Windows and PowerShell appear before Linux equivalents, such as in the agent installation section and in automation tooling. PowerShell is mentioned as a primary automation method, while Linux and Azure CLI are referenced less prominently. There are no explicit Linux command examples or screenshots, and troubleshooting steps reference Windows-specific certificate stores. Although Linux is stated as supported, practical parity in examples and guidance is lacking.
Recommendations
  • Provide Linux-specific examples and screenshots alongside Windows ones, especially for agent installation, troubleshooting, and automation.
  • Mention Azure CLI and Bash scripting equally with PowerShell when discussing automation options.
  • Ensure troubleshooting guidance includes Linux-relevant details (e.g., certificate store locations, common error messages).
  • Where links to Windows documentation are given, always include parallel links for Linux.
  • Add explicit Linux command-line examples for common tasks, such as agent installation and connectivity checks.
  • Review and balance the order of presentation so Linux is not consistently mentioned after Windows.
GitHub Create Pull Request
Network Watcher https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/network-watcher/diagnose-vm-network-traffic-filtering-problem-powershell.md ...agnose-vm-network-traffic-filtering-problem-powershell.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page exclusively uses Azure PowerShell cmdlets for all examples and instructions, with no mention or examples of equivalent Azure CLI or Bash commands. The prerequisites and workflow are centered around PowerShell, which is traditionally associated with Windows environments, even though Azure Cloud Shell supports Bash and Linux users. There is no guidance for Linux users or parity in command-line tooling.
Recommendations
  • Add equivalent Azure CLI (az) commands for each PowerShell example, with clear instructions for running them in Bash or Cloud Shell.
  • Update the prerequisites section to mention Azure CLI and Bash as supported alternatives, including installation and usage instructions for Linux users.
  • Present both PowerShell and CLI/Bash examples side-by-side or provide a toggle to switch between them, ensuring equal visibility.
  • Avoid language that implies PowerShell is the default or preferred option; instead, clarify that both PowerShell and CLI/Bash are supported.
  • Include notes or links for Linux-specific considerations, such as authentication or environment setup.
GitHub Create Pull Request
Network Watcher https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/network-watcher/vnet-flow-logs-tutorial.md ...in/articles/network-watcher/vnet-flow-logs-tutorial.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The tutorial demonstrates a Windows bias by exclusively using Windows Server as the VM image, guiding users to connect via RDP, and referencing Microsoft Edge for browsing. There are no Linux VM examples, no SSH instructions, and no mention of Linux tools or workflows. Windows-centric patterns (RDP, Edge) are presented as defaults, with no parity for Linux users.
Recommendations
  • Add parallel instructions for creating a Linux VM (e.g., Ubuntu), including appropriate image selection.
  • Include SSH connection steps for Linux VMs, and mention opening port 22 for SSH in the networking section.
  • Provide examples of viewing flow logs using Linux tools (e.g., cat, jq, less) and mention alternative browsers (e.g., Firefox, Chrome).
  • Reference Linux-compatible Azure tools (e.g., Azure CLI, Storage Explorer for Linux) where relevant.
  • Ensure screenshots and step-by-step instructions cover both Windows and Linux scenarios, or clarify when steps differ.
GitHub Create Pull Request
Network Watcher https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/network-watcher/network-watcher-visualize-nsg-flow-logs-power-bi.md ...er/network-watcher-visualize-nsg-flow-logs-power-bi.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page exclusively describes using Power BI Desktop—a Windows-only application—for visualizing Azure NSG flow logs. All instructions and examples assume the user is on Windows, with no mention of Linux-compatible BI tools or how to perform similar tasks on Linux. The setup steps, screenshots, and workflow are centered around Power BI Desktop, and there are no alternative examples or guidance for Linux users. While there is a 'Next steps' link to Elastic Stack (an open-source, cross-platform tool), the main content is heavily Windows-centric.
Recommendations
  • Add parallel instructions for visualizing NSG flow logs using Linux-compatible BI tools (e.g., Tableau on Linux, Grafana, Kibana/Elastic Stack).
  • Explicitly mention platform requirements for Power BI Desktop and suggest alternatives for Linux users.
  • Provide sample scripts or workflows for parsing and visualizing NSG flow logs on Linux, such as using Python (pandas, matplotlib) or open-source dashboard tools.
  • Reorder or balance the documentation so that Windows and Linux options are presented with equal prominence.
  • Include a comparison table of visualization options for different operating systems.
GitHub Create Pull Request
Network Watcher https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/network-watcher/vpn-troubleshoot-powershell.md ...rticles/network-watcher/vpn-troubleshoot-powershell.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page exclusively uses PowerShell for all troubleshooting examples and instructions, which is most commonly associated with Windows environments. There are no examples or guidance for Linux users, such as Azure CLI or Bash scripts, within the main content. The prerequisites and workflow assume PowerShell usage, and alternative Linux-native tools or command-line patterns are not mentioned. Although a related link to Azure CLI documentation is provided at the end, Linux parity is not present in the main instructional content.
Recommendations
  • Add equivalent Azure CLI examples alongside PowerShell examples in each troubleshooting section.
  • Explicitly mention that Azure CLI can be used from Linux, macOS, or Windows, and provide links to installation and usage guides.
  • Include Bash script snippets for common troubleshooting tasks to support Linux users.
  • Reorganize prerequisites to present both PowerShell and Azure CLI options equally, rather than PowerShell-first.
  • Clarify that Azure Cloud Shell supports both PowerShell and Bash/CLI environments, and show how to select each.
GitHub Create Pull Request
Network Watcher https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/network-watcher/connection-monitor-connected-machine-agent.md ...-watcher/connection-monitor-connected-machine-agent.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation exhibits a Windows bias by frequently presenting Windows-specific tools (PowerShell, Windows Admin Center) and instructions before or in greater detail than Linux equivalents. PowerShell is emphasized as an automation method, with no mention of Linux-native alternatives. Windows Admin Center is highlighted as a management tool, while no comparable Linux tool is referenced. Linux instructions are present but less detailed, and Linux automation options are not discussed.
Recommendations
  • Provide Linux-first or parallel examples when presenting installation and management steps.
  • Include automation options for Linux, such as Bash scripts or Ansible, alongside PowerShell.
  • Mention Linux-native management tools (e.g., Cockpit, Ansible) where Windows Admin Center is referenced.
  • Ensure equal detail and clarity in Linux instructions, including troubleshooting and verification steps.
  • Add links to Linux-specific onboarding documentation and community resources.
GitHub Create Pull Request
Network Watcher https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/network-watcher/connection-troubleshoot-manage.md ...cles/network-watcher/connection-troubleshoot-manage.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by exclusively using RDP (port 3389) as the example protocol for connectivity tests, which is specific to Windows environments. There are no examples or guidance for Linux scenarios, such as SSH (port 22) connectivity. The troubleshooting steps and solutions reference RDP and Windows firewall configuration, but do not mention SSH, Linux firewalls (e.g., iptables, firewalld, ufw), or Linux-specific troubleshooting patterns. The examples and error scenarios are all framed around Windows use cases, and Windows tools (PowerShell) are emphasized, with no parity for Linux command-line tools or troubleshooting steps.
Recommendations
  • Add SSH (port 22) connectivity examples alongside RDP to cover Linux VM scenarios.
  • Include troubleshooting steps and solutions for Linux firewalls (e.g., iptables, firewalld, ufw) when discussing guest OS configuration.
  • Provide sample output and error scenarios for Linux VMs, such as what happens if SSH is not listening or blocked by a Linux firewall.
  • Mention Linux-specific tools and commands (e.g., using Azure CLI from Bash, checking SSH service status) in parity with PowerShell examples.
  • Ensure that documentation language and examples are inclusive of both Windows and Linux environments, and avoid assuming RDP as the default use case.
GitHub Create Pull Request
← Previous Page 3 of 10 Next →