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 1-25 of 238 flagged pages
Network Watcher Use packet capture to proactively monitor your network ...cles/network-watcher/packet-capture-alert-triggered.md
High Priority View Details →
Scanned: 2026-01-14 00:00
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 by exclusively providing PowerShell-based examples and scripts for Azure Functions, authentication, and packet capture orchestration. All code samples use PowerShell cmdlets, with no equivalent Bash, CLI, or Python examples. The authentication workflow and environment variable setup are described only in terms of PowerShell and Windows file paths. The prerequisites mention both Windows and Linux VM extensions, but all automation and scripting guidance is Windows-centric, making it difficult for Linux/macOS users to follow or adapt the instructions.
Recommendations
  • Provide equivalent examples using Azure CLI, Bash, or Python for function code and authentication workflows.
  • Include Linux/macOS-friendly instructions for key generation, environment variable setup, and file paths.
  • Clarify which steps are platform-agnostic and which require adaptation, offering explicit guidance for non-Windows users.
  • Reorder sections or provide parallel tracks so Linux/macOS users do not need to translate PowerShell logic themselves.
  • Reference cross-platform tools and patterns (e.g., Azure CLI, REST API) alongside PowerShell.
GitHub Create Pull Request
Network Watcher Filter Virtual Network Flow Logs (Preview) ...n/articles/network-watcher/vnet-flow-logs-filtering.md
High Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example πŸ”§ Windows Tools
Summary
The documentation exclusively uses Azure PowerShell cmdlets for all examples and instructions, with no mention of Azure CLI, Bash, or cross-platform alternatives. This creates a strong bias toward Windows and PowerShell users, leaving Linux/macOS users without direct guidance for completing the documented tasks.
Recommendations
  • Add equivalent Azure CLI (az network watcher flow-log ...) examples for all PowerShell cmdlets shown.
  • Explicitly mention that Azure CLI is cross-platform and suitable for Linux/macOS users.
  • Provide Bash scripting examples where appropriate.
  • Include a section comparing PowerShell and CLI usage for flow log filtering.
  • Clarify any feature gaps or differences between PowerShell and CLI, if applicable.
GitHub Create Pull Request
Network Watcher Install the Azure Connected Machine agent for connection monitor ...-watcher/connection-monitor-connected-machine-agent.md
High Priority View Details →
Scanned: 2026-01-11 00:00
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 PowerShell usage before Linux equivalents, providing more detail for Windows tools (PowerShell, Windows Admin Center), and referencing Windows-specific management patterns. Linux instructions are present but less detailed, and alternative Linux management tools are not mentioned.
Recommendations
  • Present Linux and Windows instructions in parallel, ensuring equal detail and prominence.
  • Include Linux-native automation examples (e.g., Bash scripts, Ansible, systemd) alongside PowerShell.
  • Mention and link to Linux management tools (such as Cockpit or CLI-based workflows) where Windows Admin Center is referenced.
  • Expand Linux agent installation and verification steps to match the detail provided for Windows.
  • Clarify that PowerShell is cross-platform, or provide Azure CLI examples for Linux users.
  • Ensure that references to downloading and running scripts specify both Windows and Linux file/script formats.
GitHub Create Pull Request
Network Watcher Diagnose a VM network routing problem - Azure PowerShell ...cher/diagnose-vm-network-routing-problem-powershell.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation exclusively uses Azure PowerShell cmdlets and examples, with no mention of Azure CLI, Bash, or Linux-native tooling. All instructions and code samples are tailored to PowerShell, which is most commonly used on Windows. There is no guidance for users who prefer Linux or Bash environments, and no parity for cross-platform usage.
Recommendations
  • Add equivalent Azure CLI (az) commands and examples alongside PowerShell for each step.
  • Explicitly mention that Azure Cloud Shell supports both Bash and PowerShell, and provide Bash instructions.
  • Include notes or sections for Linux users, highlighting any differences or additional steps.
  • Ensure that prerequisites mention both Azure CLI and PowerShell as supported options.
  • Provide links to Linux/Bash-specific documentation where relevant.
GitHub Create Pull Request
Network Watcher Quickstart: Diagnose a VM traffic filter problem - Azure PowerShell ...agnose-vm-network-traffic-filtering-problem-powershell.md
High Priority View Details →
Scanned: 2026-01-11 00:00
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 no mention of Azure CLI or Bash alternatives. The prerequisites and workflow assume PowerShell usage, which is more common on Windows, and there is no guidance for Linux users or parity in command-line tooling. This creates a Windows-centric bias and may hinder accessibility for users on Linux or macOS platforms.
Recommendations
  • Add equivalent Azure CLI (az) examples for each PowerShell command, with Bash syntax where appropriate.
  • Update the prerequisites section to mention Azure CLI and Bash as alternatives to PowerShell, and provide installation instructions for Linux/macOS.
  • Clearly indicate which commands work cross-platform and provide guidance for running them in Linux/macOS environments.
  • Where possible, use neutral terminology (e.g., 'command-line interface') rather than 'PowerShell' when referring to steps that can be performed with multiple tools.
  • Consider reordering examples so that Azure CLI/Bash and PowerShell are presented side-by-side, or alternate which is shown first.
GitHub Create Pull Request
Network Watcher Migrate to Connection monitor from Connection monitor (classic) ...-to-connection-monitor-from-connection-monitor-classic.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation mentions automation via PowerShell, Azure CLI, and Terraform, listing PowerShell first, which may suggest a Windows-first bias. There are no explicit Linux-specific examples, commands, or troubleshooting steps, and no mention of Linux tools or shell commands. The documentation does state that Linux is supported, but does not provide parity in examples or guidance for Linux users.
Recommendations
  • Provide Linux-specific examples, such as Bash/CLI commands for migration and troubleshooting.
  • List Azure CLI and Terraform before PowerShell, or present all automation options equally.
  • Include troubleshooting steps and error messages relevant to Linux environments (e.g., extension installation on Linux VMs).
  • Reference Linux tools or patterns where appropriate, such as shell scripting for automation.
  • Add screenshots or walkthroughs from Linux environments to balance the Windows-centric visuals.
GitHub Create Pull Request
Network Watcher Manage Network Watcher Agent VM extension - Linux ...rticles/network-watcher/network-watcher-agent-linux.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy πŸ”§ Windows Tools Windows First
Summary
Although the documentation is targeted at Linux VMs, it consistently prioritizes Azure PowerShell (a Windows-centric tool) in examples and instructions, often listing PowerShell before Azure CLI. PowerShell is referenced as a primary automation tool, and its installation and usage are described in detail, while Linux-native scripting or automation options (such as Bash scripts or SSH) are not mentioned. The documentation also refers to 'Azure PowerShell' and 'Azure CLI' as the only local deployment options for ARM templates, omitting Linux-native alternatives. There is a minor error in the Azure CLI install example, referencing 'Network Watcher Agent for Windows' instead of Linux.
Recommendations
  • List Azure CLI examples before PowerShell, as CLI is platform-agnostic and more commonly used on Linux.
  • Include Bash script examples for common operations, such as installing/uninstalling extensions, to better support Linux administrators.
  • Mention Linux-native automation tools (e.g., Ansible, SSH, cloud-init) as alternatives for extension management.
  • Clarify that Azure PowerShell can be run on Linux, but highlight Azure CLI and Bash as preferred options for Linux environments.
  • Correct the CLI example to reference 'Network Watcher Agent for Linux' instead of Windows.
  • Add troubleshooting or verification steps using Linux commands (e.g., systemctl, journalctl, ls) to check extension status locally.
GitHub Create Pull Request
Network Watcher Update Network Watcher extension to the latest version ...ticles/network-watcher/network-watcher-agent-update.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First πŸ”§ Windows Tools
Summary
The documentation page exhibits a moderate Windows bias. The only bulk-update script provided is in PowerShell, which is natively a Windows tool, and the script is explicitly written for updating Windows VMs (with only minor logic for Linux VMs, but still using PowerShell). PowerShell is presented as the primary automation tool, with no equivalent Bash or shell script for Linux users. In several places, PowerShell examples and screenshots are given before or in greater detail than Azure CLI or Linux-native alternatives. There is no Linux shell script for bulk updating, and PowerShell is referenced as a general solution, despite its limited adoption on Linux.
Recommendations
  • Provide a Bash or shell script example for bulk updating the Network Watcher extension on Linux VMs, using Azure CLI.
  • Ensure that CLI examples are given equal prominence and detail as PowerShell examples, especially for Linux users.
  • When presenting manual update steps, alternate the order of Windows and Linux examples, or present them side-by-side.
  • Clarify that PowerShell is cross-platform, but also acknowledge that Bash/shell is the default on most Linux systems.
  • Add screenshots or output examples for Linux CLI commands, not just PowerShell.
  • Explicitly mention Linux-native automation options (e.g., Bash, Ansible) for large deployments.
GitHub Create Pull Request
Network Watcher Enable or disable Azure Network Watcher ...ain/articles/network-watcher/network-watcher-create.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy πŸ”§ Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell is consistently presented as a primary automation option alongside the Azure CLI, and is referenced for advanced customization (such as naming resources) before CLI or REST API. The instructions for installing and using PowerShell are more detailed than those for Azure CLI, and PowerShell is mentioned as a local tool without clarifying its cross-platform availability. There is a subtle prioritization of Windows-centric tools and patterns, with PowerShell examples and terminology appearing before or more prominently than Linux-native equivalents.
Recommendations
  • Clarify that both PowerShell and Azure CLI are cross-platform and available on Windows, Linux, and macOS.
  • Provide equal detail for installing and running Azure CLI locally on Linux and macOS, including links to platform-specific installation guides.
  • When mentioning advanced customization (e.g., naming resources), explicitly state whether CLI, REST API, or ARM templates can achieve the same results, and provide examples for each.
  • Avoid implying PowerShell is a Windows-only tool; note its availability on Linux and macOS.
  • Ensure that references to tools and commands do not consistently place Windows-centric options (PowerShell) before Linux-native ones (CLI), or alternate their order.
  • Where screenshots or instructions reference local environments, include examples or notes for Linux/macOS terminals as well as Windows PowerShell.
GitHub Create Pull Request
Network Watcher Troubleshoot and monitor VPN gateways - Azure Automation ...tcher/network-watcher-monitor-with-azure-automation.md
High Priority View Details →
Scanned: 2026-01-11 00:00
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 PowerShell for scripting examples and runbook creation, which is a Windows-centric tool. There are no references to Bash, Python, or other cross-platform scripting languages, nor are there instructions or examples for Linux users. The documentation assumes familiarity with PowerShell conventions and tools, and does not mention or prioritize Linux-compatible alternatives.
Recommendations
  • Provide equivalent Bash or Python script examples for Linux users, demonstrating how to interact with Azure Automation and Network Watcher.
  • Include instructions for creating and running runbooks using non-PowerShell options, such as Python or Bash, and clarify any platform-specific requirements.
  • Mention cross-platform Azure CLI commands as alternatives to PowerShell cmdlets for resource management and troubleshooting.
  • Add guidance on configuring SMTP and credentials for Linux environments, including examples for popular mail clients or libraries.
  • Explicitly state platform compatibility for each step, and ensure Linux users are not excluded from automation and monitoring scenarios.
GitHub Create Pull Request
Network Watcher Migrate to virtual network flow logs ...main/articles/network-watcher/nsg-flow-logs-migrate.md
High Priority View Details →
Scanned: 2026-01-11 00:00
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. The prerequisites and workflow focus on PowerShell and the Az PowerShell module, which are more commonly used in Windows environments. While PowerShell is available on Linux and macOS, the documentation does not provide explicit guidance, troubleshooting, or alternative examples for Linux users, nor does it mention platform-specific considerations beyond a generic install link.
Recommendations
  • Add explicit Bash or Azure CLI examples for generating and running the migration script, including instructions for Linux and macOS environments.
  • Clarify any platform-specific steps or troubleshooting for running PowerShell scripts on Linux/macOS (e.g., permissions, execution policy, dependency installation).
  • Include a note or section on running the migration process from Linux, with screenshots or terminal output from a Linux shell.
  • Provide parity in tool recommendations, mentioning Azure CLI as an alternative where possible.
  • Reorder prerequisites to mention cross-platform compatibility first, and avoid implying Windows as the default environment.
GitHub Create Pull Request
Network Watcher Use packet capture to proactively monitor your network ...cles/network-watcher/packet-capture-alert-triggered.md
High Priority View Details →
Scanned: 2026-01-11 00:00
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. All code samples and automation instructions use PowerShell, with no equivalent Bash, CLI, or Python examples for Linux users. The authentication and environment variable setup is described only with PowerShell scripts. The prerequisites and extension references mention Windows before Linux, and the use of Windows-specific paths (e.g., C:\temp) further reinforces the bias. There is no guidance for Linux users on how to perform these steps using native tools or languages.
Recommendations
  • Provide equivalent examples using Bash scripts, Azure CLI, or Python for Linux users.
  • Include instructions for storing and encrypting credentials on Linux, using Linux file paths and tools (e.g., openssl, gpg).
  • Offer cross-platform guidance for authentication, such as using environment variables and service principals via Azure CLI.
  • Present both Windows and Linux extension setup steps side-by-side, or in parallel sections.
  • Avoid using Windows-specific file paths in generic examples; use platform-agnostic or dual-path examples.
  • Add notes or links to Linux-specific documentation for packet capture automation and Azure Functions integration.
GitHub Create Pull Request
Network Watcher NSG Flow Logs Overview ...ain/articles/network-watcher/nsg-flow-logs-overview.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy πŸ”§ Windows Tools Windows First
Summary
The documentation page displays a moderate Windows bias. PowerShell is the only CLI tool shown for configuring advanced settings (e.g., setting FlowTimeoutInMinutes), and the example provided is exclusively in Azure PowerShell. There are no equivalent Azure CLI (cross-platform) or Bash examples. Additionally, the documentation references Windows-centric tools (e.g., Power BI) before mentioning open-source or Linux-friendly alternatives (e.g., Grafana, Elastic Stack). This ordering and lack of Linux/CLI parity may disadvantage Linux users.
Recommendations
  • Provide Azure CLI (az) and/or Bash examples alongside PowerShell for all configuration tasks, especially for settings like FlowTimeoutInMinutes.
  • When listing visualization or analytics tools, alternate the order or group by platform neutrality (e.g., mention Grafana and Elastic Stack before or alongside Power BI).
  • Explicitly state that all features and instructions are available cross-platform where applicable, and link to Linux/macOS-specific guidance if available.
  • For any code snippets or automation, include both PowerShell and Bash/Azure CLI versions to ensure Linux users are equally supported.
  • Audit related documentation for similar patterns and update to ensure Linux parity.
GitHub Create Pull Request
Network Watcher Quickstart: Configure NSG flow logs using an ARM template ...ain/articles/network-watcher/nsg-flow-logs-template.md
High Priority View Details →
Scanned: 2026-01-11 00:00
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 Azure CLI or Bash examples. File paths use Windows conventions (e.g., C:\MyTemplates\azuredeploy.json), and there are no Linux or cross-platform alternatives provided. The focus on PowerShell and Windows-centric patterns may hinder accessibility for users on Linux or macOS systems.
Recommendations
  • Add equivalent Azure CLI (az) commands for deploying ARM templates, which are cross-platform and widely used on Linux/macOS.
  • Include file path examples using Linux/macOS conventions (e.g., ~/MyTemplates/azuredeploy.json) alongside Windows paths.
  • Explicitly state that both Azure PowerShell and Azure CLI can be used, and link to relevant installation guides for each platform.
  • Add troubleshooting and validation steps using Azure CLI, not just PowerShell.
  • Consider a section that highlights platform-agnostic deployment options, such as using the Azure portal or GitHub Actions.
GitHub Create Pull Request
Network Watcher Manage virtual network flow logs ...main/articles/network-watcher/vnet-flow-logs-manage.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy πŸ”§ Windows Tools Windows First
Summary
The documentation provides examples for the Azure portal, PowerShell, and Azure CLI. PowerShell is featured heavily throughout, with detailed explanations and multiple code samples. There are frequent references to PowerShell-specific tools and patterns (e.g., cmdlets, installation instructions, usage in Cloud Shell, and local installation guidance). PowerShell is a Windows-centric tool, and its prominence may suggest a bias toward Windows users. The documentation also references Azure Storage Explorer, which is available cross-platform but is often associated with Windows environments. While Azure CLI is included and is cross-platform, PowerShell examples and instructions are generally more detailed and sometimes appear before CLI equivalents.
Recommendations
  • Ensure Azure CLI examples are as detailed and comprehensive as PowerShell examples, including variable usage and advanced scenarios.
  • Explicitly mention that Azure CLI is cross-platform and highlight its parity with PowerShell for Linux and macOS users.
  • Add Bash shell examples for common operations, especially for Linux users, where appropriate.
  • Clarify that Azure Cloud Shell supports both Bash and PowerShell, and provide instructions for both.
  • Avoid language that assumes PowerShell is the default or preferred scripting environment.
  • Where tools like Azure Storage Explorer are mentioned, note their cross-platform availability and provide links to Linux/macOS installation guides.
GitHub Create Pull Request
Network Watcher Manage packet captures ...main/articles/network-watcher/packet-capture-manage.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First πŸ”§ Windows Tools Powershell Heavy
Summary
The documentation page demonstrates a moderate Windows bias. Windows file paths (e.g., C:\Capture\...) are consistently used as primary examples, with Linux paths mentioned secondarily or parenthetically. PowerShell is given prominence as a scripting interface, and instructions for downloading files use Windows-style paths by default. References to Windows tools (e.g., Storage Explorer) and patterns (such as local file paths) are presented before or more prominently than their Linux equivalents.
Recommendations
  • Provide Linux-first or parallel examples for file paths, e.g., show /var/captures/... before or alongside C:\Capture\...
  • Explicitly mention Linux tools (such as scp, rsync, or Linux-native storage browsers) for downloading packet captures from VMs or storage.
  • Balance PowerShell and CLI coverage by including Bash script examples and Linux-native command-line patterns.
  • Ensure that references to managing the Network Watcher Agent VM extension for Linux are as prominent and detailed as those for Windows.
  • Where screenshots or examples are shown, alternate between Windows and Linux environments, or provide both.
  • In download instructions, show both Windows and Linux destination paths and clarify OS-specific steps.
GitHub Create Pull Request
Network Watcher Filter Virtual Network Flow Logs (Preview) ...n/articles/network-watcher/vnet-flow-logs-filtering.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy πŸ”§ Windows Tools Missing Linux Example Windows First
Summary
The documentation page exclusively provides Azure PowerShell examples for configuring and managing virtual network flow logs, with no mention of Azure CLI, Bash, or Linux-native workflows. All command-line instructions use PowerShell cmdlets, which are most familiar and accessible to Windows users. There is no guidance for users on Linux or macOS platforms, nor any reference to cross-platform tools or alternative methods.
Recommendations
  • Add equivalent Azure CLI examples for all PowerShell cmdlets shown, as Azure CLI is cross-platform and widely used on Linux and macOS.
  • Explicitly mention that both PowerShell and Azure CLI can be used for these operations, and provide links to relevant CLI documentation.
  • Consider including Bash script examples or guidance for users working in Linux environments.
  • Where possible, avoid using Windows-centric terminology or tools as the default, and present cross-platform options first or in parallel.
  • Add a section clarifying platform compatibility and recommending tools for Linux/macOS users.
GitHub Create Pull Request
Network Watcher Managed Identity for Virtual Network Flow Logs ...les/network-watcher/vnet-flow-logs-managed-identity.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a strong Windows bias by exclusively providing Azure PowerShell examples and referencing Azure PowerShell and Cloud Shell throughout. All prerequisites and instructions assume use of PowerShell, with no mention of Azure CLI, Bash, or Linux-native tooling. This approach prioritizes Windows-centric tools and omits equivalent guidance for Linux users.
Recommendations
  • Add parallel examples using Azure CLI (az commands) alongside PowerShell for all resource creation and management steps.
  • Update prerequisite links and instructions to include both PowerShell and Azure CLI options, with tabs or sections for each.
  • Explicitly mention that Azure Cloud Shell supports both Bash and PowerShell, and show how to select Bash.
  • Ensure role assignment and managed identity steps are documented for both PowerShell and CLI workflows.
  • Review related content to ensure Linux parity and cross-platform accessibility.
GitHub Create Pull Request
Network Watcher Tutorial: Log network traffic ...in/articles/network-watcher/vnet-flow-logs-tutorial.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example πŸ”§ Windows Tools
Summary
The tutorial demonstrates a clear Windows bias by exclusively using Windows Server as the VM image, guiding users to connect via RDP (a Windows protocol), and omitting any instructions or examples for Linux-based VMs or SSH connections. The workflow assumes the use of Windows tools (RDP, Microsoft Edge) and does not mention Linux alternatives or provide parity for Linux administrators.
Recommendations
  • Include instructions for creating a Linux VM (e.g., Ubuntu) alongside the Windows VM example.
  • Provide steps for connecting to a Linux VM using SSH, including port selection and security recommendations.
  • Mention Linux-compatible tools for viewing and downloading flow logs, such as azcopy, Azure CLI, or mounting Blob storage via fuse.
  • Show how to open and analyze flow logs on Linux (e.g., using cat, jq, or other text editors).
  • Balance screenshots and examples to reflect both Windows and Linux environments.
  • Explicitly note differences in network security group rules (e.g., SSH port 22 for Linux, RDP port 3389 for Windows).
GitHub Create Pull Request
Network Watcher VPN troubleshoot overview .../articles/network-watcher/vpn-troubleshoot-overview.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy πŸ”§ Windows Tools Windows Error Codes Windows First
Summary
The documentation page exhibits Windows bias through several patterns: PowerShell is mentioned as a primary method for invoking VPN troubleshoot, and in some cases is required for specific resource group configurations. Log file examples and error messages reference Windows-specific error codes and terminology (e.g., 'Windows error 13801', 'ERROR_IPSEC_IKE_AUTH_FAIL'). Diagnostic logs (e.g., WFP, IKE) and troubleshooting steps use Windows-centric formats and language. There are no explicit Linux command examples or references to Linux-native troubleshooting tools or error codes.
Recommendations
  • Include Linux-specific examples for running VPN troubleshoot, such as using Azure CLI on Linux and Bash scripting.
  • Reference Linux-native error codes and troubleshooting patterns in log file examples, or clarify cross-platform applicability.
  • Add documentation or links for troubleshooting VPN connections from Linux-based on-premises devices, including common issues and log formats.
  • Ensure parity in tool recommendations (e.g., mention azcopy or Linux-compatible blob download methods alongside Storage Explorer).
  • Clarify whether diagnostic logs and error codes are relevant for Linux-based VPN gateways and provide translation or mapping where possible.
GitHub Create Pull Request
Network Watcher Troubleshoot VPN gateways and connections - PowerShell ...rticles/network-watcher/vpn-troubleshoot-powershell.md
High Priority View Details →
Scanned: 2026-01-11 00:00
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, with no Azure CLI or Bash/Linux shell commands provided. The prerequisites and instructions focus on Azure PowerShell and Cloud Shell, which are more familiar to Windows users. There are no Linux-specific instructions or examples, and PowerShell is presented as the primary (and only) method for performing these tasks.
Recommendations
  • Add equivalent Azure CLI examples for all troubleshooting steps, as Azure CLI is cross-platform and widely used on Linux and macOS.
  • Explicitly mention that Azure Cloud Shell supports both Bash and PowerShell, and provide instructions/examples for Bash users.
  • Include a section or tabs for Linux/macOS users, showing how to perform the same tasks using CLI commands.
  • Ensure that references to tools (such as Storage Explorer) include alternatives or instructions for Linux/macOS environments.
  • Avoid presenting PowerShell as the only or default method; instead, offer parallel instructions for both PowerShell and CLI where possible.
GitHub Create Pull Request
Network Watcher Migrate to Connection monitor from Network performance monitor ...to-connection-monitor-from-network-performance-monitor.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First πŸ”§ Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing Windows-specific tools and extensions (e.g., Network Watcher extension for Windows), mentioning PowerShell and Windows tools before Linux equivalents, and lacking explicit Linux migration instructions or examples. Linux support is only briefly mentioned in a comparison table, with no detailed guidance or parity in agent installation or troubleshooting steps for Linux systems.
Recommendations
  • Provide explicit Linux migration steps, including agent installation and troubleshooting for Linux VMs.
  • Include Linux-specific examples and screenshots alongside Windows ones.
  • Mention Linux CLI tools (e.g., Bash, Azure CLI on Linux) equally or before Windows/PowerShell tools.
  • Clarify agent extension requirements for Linux (e.g., how to install the Network Watcher extension on Linux VMs).
  • Ensure that documentation for integrations and error messages includes Linux scenarios and terminology.
GitHub Create Pull Request
Network Watcher Connection monitor overview ...rticles/network-watcher/connection-monitor-overview.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy πŸ”§ Windows Tools
Summary
The documentation page demonstrates mild Windows bias. References to Windows tools and patterns (such as PowerShell and Windows-specific extension management) appear before or more prominently than their Linux equivalents. For example, in the section on installing the Network Watcher Agent extension, the link to 'Manage Network Watcher extension for Windows' is listed before the Linux version. The creation of connection monitors lists Azure PowerShell as a primary method, with no explicit mention of Azure CLI or Linux shell examples. Additionally, diagnostic and troubleshooting steps reference Windows-centric concepts (e.g., certificate stores) without Linux-specific guidance. There are no explicit Linux command-line examples, and PowerShell is mentioned as a way to set HTTP response codes, but not Bash/Azure CLI.
Recommendations
  • Ensure Linux equivalents (Azure CLI, Bash scripts, Linux extension management) are mentioned alongside or before Windows/PowerShell examples.
  • Provide explicit Linux command-line examples for key tasks such as creating connection monitors, managing extensions, and setting test configurations.
  • Balance references to Windows tools (PowerShell, certificate stores) with Linux alternatives (Azure CLI, OpenSSL, Linux certificate locations).
  • Where troubleshooting steps mention Windows-specific concepts (e.g., Local Computer Trusted Certification Authorities store), add Linux-specific instructions (e.g., /etc/ssl/certs or update-ca-certificates).
  • In lists or tables, avoid listing Windows methods or tools first unless there is a technical reason; alternate ordering or group by platform.
GitHub Create Pull Request
Network Watcher Troubleshoot outbound connections ...cles/network-watcher/connection-troubleshoot-manage.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example πŸ”§ Windows Tools
Summary
The documentation page demonstrates Windows bias primarily by using RDP (port 3389) as the default connectivity test scenario, which is specific to Windows systems. All troubleshooting examples focus on RDP, with no mention of Linux protocols (such as SSH on port 22) or Linux-specific troubleshooting scenarios. The solutions and explanations assume Windows endpoints, and there are no examples or guidance for Linux VM connectivity. Additionally, the PowerShell examples and references to Windows-centric tools (like RDP) are given prominence, while Linux equivalents are absent.
Recommendations
  • Include SSH (port 22) connectivity test scenarios alongside RDP to represent Linux VM use cases.
  • Add troubleshooting examples and solutions for Linux endpoints, such as configuring firewalls (iptables, ufw) and SSH listeners.
  • Provide explicit guidance for Linux users, including command-line troubleshooting steps (e.g., using netcat, telnet, or SSH commands) and how to interpret results for Linux VMs.
  • Balance the documentation by mentioning both Windows and Linux tools and patterns where relevant.
  • Clarify that the connection troubleshoot feature works for both Windows and Linux VMs, and provide parity in example scenarios.
GitHub Create Pull Request
Network Watcher Visualizing Azure NSG flow logs - Power BI ...er/network-watcher-visualize-nsg-flow-logs-power-bi.md
High Priority View Details →
Scanned: 2026-01-10 00:00
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-only applicationβ€”for visualizing Azure NSG flow logs. All setup and usage instructions assume the reader is on Windows, with no mention of Linux-compatible visualization tools or alternatives. There are no examples or guidance for Linux users, and Windows tooling is presented as the default and only option for this scenario.
Recommendations
  • Include instructions and examples for visualizing NSG flow logs using cross-platform or Linux-native tools (e.g., Kibana, Grafana, or open-source BI tools).
  • Explicitly mention platform requirements for Power BI Desktop and suggest alternatives for Linux users.
  • Provide parity in documentation by offering step-by-step guides for Linux users, such as using the Elastic Stack (as referenced in 'Next steps') or other open-source solutions.
  • Add a comparison table of visualization options for different operating systems, highlighting feature parity and limitations.
GitHub Create Pull Request
← Previous Page 1 of 10 Next →