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 76-100 of 238 flagged pages
Network Watcher https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/network-watcher/diagnose-vm-network-routing-problem-powershell.md ...cher/diagnose-vm-network-routing-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 exclusively uses Azure PowerShell cmdlets and Windows-oriented tooling for all examples and instructions. There are no references to Linux-native tools, Bash, or Azure CLI, and the prerequisites and workflow assume PowerShell usage, which is more common on Windows. This creates a bias toward Windows users and leaves Linux users without equivalent guidance.
Recommendations
  • Add parallel examples using Azure CLI (az commands) and Bash scripting for each PowerShell example.
  • Update prerequisites to mention Bash and Azure CLI as alternatives to PowerShell, including instructions for installing and using Azure CLI on Linux.
  • Include notes or sections highlighting how Linux users can perform the same troubleshooting steps, possibly with screenshots or terminal output.
  • Ensure that Cloud Shell instructions clarify that both Bash and PowerShell environments are available, and provide guidance for both.
  • Where possible, mention cross-platform compatibility of tools and commands, and avoid language that implies PowerShell is the only or primary method.
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-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 Windows bias by listing PowerShell as the first automation option and not providing explicit Linux-specific examples or tools. While it mentions Linux support in a feature comparison table, it does not offer parity in examples or instructions for Linux users. The documentation also references the Network Watcher extension, which is available for both Windows and Linux, but does not clarify installation or usage for Linux environments.
Recommendations
  • Provide explicit Linux command-line examples (e.g., Bash, Azure CLI) alongside or before PowerShell examples.
  • Clarify installation and usage steps for the Network Watcher extension on Linux VMs, including package managers and shell commands.
  • List automation options (PowerShell, Azure CLI, Terraform) in a neutral order or highlight cross-platform usage.
  • Include troubleshooting steps and error messages relevant to Linux environments.
  • Add links to Linux-specific documentation or guides for Connection monitor migration.
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-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
Although the documentation is focused on Linux VMs, there is a noticeable bias towards Windows-centric tools and patterns. PowerShell is featured heavily and often mentioned before Azure CLI, even in Linux contexts. References to Azure PowerShell and its installation are frequent, and instructions for deploying ARM templates prioritize PowerShell before CLI. There are no native Linux shell (bash) examples, and the use of PowerShell is assumed for command-line operations, which is less common for Linux users.
Recommendations
  • Prioritize Azure CLI examples before PowerShell in all sections, as CLI is more native to Linux environments.
  • Add bash shell script examples for common operations, such as installing, listing, and uninstalling the extension.
  • Clarify that PowerShell is optional and not required for Linux users, and provide guidance for using bash or other native Linux tools.
  • When referencing Cloud Shell, note that both bash and PowerShell environments are available, and show how to select bash.
  • Remove or de-emphasize instructions for installing Azure PowerShell locally on Linux, unless there is a specific advantage.
  • Ensure that all example commands and screenshots use Linux-friendly conventions (e.g., single quotes, bash prompt, Linux file paths).
GitHub Create Pull Request
Network Watcher https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/network-watcher/network-watcher-create.md ...ain/articles/network-watcher/network-watcher-create.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 🔧 Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell is featured prominently and often mentioned before Azure CLI, with detailed instructions and notes about installing and using PowerShell locally. The use of PowerShell as a primary scripting example and frequent references to Windows-centric tools and patterns (such as PowerShell cmdlets and installation instructions) suggest a preference for Windows environments. Although Azure CLI is included and Cloud Shell is referenced (which is cross-platform), the documentation tends to present PowerShell examples and instructions before CLI, and does not explicitly address Linux-specific usage or considerations.
Recommendations
  • Alternate the order of PowerShell and Azure CLI instructions to avoid consistently prioritizing Windows tools.
  • Explicitly mention that Azure CLI works natively on Linux and macOS, and provide installation and usage notes for those platforms.
  • Include examples or notes for Bash shell usage, especially for scripting and automation scenarios.
  • Add references to Linux/macOS terminal environments where appropriate, such as mentioning that Azure CLI commands can be run in Bash or zsh.
  • Ensure that instructions for installing and using Azure CLI locally include Linux/macOS steps and links.
  • Where PowerShell is referenced for customization or advanced scenarios, clarify if and how equivalent functionality can be achieved with Azure CLI or other cross-platform tools.
GitHub Create Pull Request
Network Watcher https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/network-watcher/migrate-to-connection-monitor-from-network-performance-monitor.md ...to-connection-monitor-from-network-performance-monitor.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits a Windows bias by referencing Windows-specific tools and extensions (e.g., Network Watcher extension for Windows), mentioning PowerShell and Windows agents before Linux equivalents, and lacking explicit Linux migration steps or examples. Linux support is mentioned only in passing, and there are no concrete Linux-focused instructions or troubleshooting guidance.
Recommendations
  • Add explicit migration instructions and examples for Linux-based agents, including steps for installing and configuring the Network Watcher extension on Linux VMs.
  • Include Linux CLI commands (e.g., Bash, Azure CLI) alongside or before PowerShell examples to ensure parity.
  • Clarify agent replacement steps for both Windows and Linux, with links to Linux-specific documentation where appropriate.
  • Provide troubleshooting guidance for common Linux migration issues.
  • Ensure references to tools and extensions are platform-neutral or clearly indicate Windows vs. Linux applicability.
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-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 shows a moderate Windows bias. The only bulk update script provided is a PowerShell script that targets Windows VMs, with no equivalent Bash or Azure CLI script for Linux VMs. PowerShell is used extensively for both Windows and Linux instructions, even though Linux users typically prefer Bash or native CLI. In several sections, PowerShell examples and screenshots are presented before or more prominently than Azure CLI or Linux-native alternatives. There is no example of a bulk update for Linux VMs using Bash or Azure CLI, and the manual update instructions rely heavily on PowerShell, which is less common on Linux.
Recommendations
  • Provide a Bash or Azure CLI script example for bulk updating Network Watcher extensions on Linux VMs, similar to the PowerShell script for Windows.
  • Ensure that Azure CLI and Bash examples are given equal prominence and ordering to PowerShell, especially in manual update and version check sections.
  • Include screenshots or output examples from Linux CLI environments, not just PowerShell.
  • Clarify which commands are cross-platform and which are Windows-specific, and avoid implying PowerShell is the default for Linux users.
  • Consider adding a table summarizing update methods for both Windows and Linux, with links to platform-specific instructions.
GitHub Create Pull Request
Network Watcher https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/network-watcher/network-watcher-monitor-with-azure-automation.md ...tcher/network-watcher-monitor-with-azure-automation.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation exclusively uses PowerShell for scripting and automation examples, with no mention of Bash, Python, or other Linux-friendly scripting options. The runbook creation process is described using PowerShell conventions and cmdlets, and there are no alternative instructions or code samples for Linux users. The documentation assumes familiarity with Windows tooling and patterns, such as PowerShell naming standards and the Send-MailMessage cmdlet, which is not available on Linux. There is no guidance for users who may prefer or require Linux-based automation.
Recommendations
  • Provide equivalent Bash or Python script examples for monitoring and troubleshooting VPN gateways using Azure CLI or REST API.
  • Mention and demonstrate how to create runbooks using the 'Python' or 'Bash' runbook types in Azure Automation, including sample code.
  • Include instructions for sending email notifications using Linux-compatible tools (e.g., 'mail' command, Python's smtplib) instead of Send-MailMessage.
  • Add a section comparing PowerShell and Linux scripting approaches, highlighting cross-platform options and considerations.
  • Clarify that Azure Automation supports multiple runbook types and link to documentation for Linux and cross-platform scripting.
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-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 Windows bias in several ways. PowerShell is the only CLI tool shown for configuring NSG flow log settings (specifically, setting FlowTimeoutInMinutes), with no equivalent Azure CLI or Linux shell example. The 'Read flow logs using PowerShell functions' link is listed before any Linux or cross-platform alternatives, and there are no explicit Linux or bash examples for managing or processing flow logs. This prioritizes Windows tooling and omits Linux-native workflows.
Recommendations
  • Add Azure CLI (az) examples for all configuration and management tasks currently shown only in PowerShell, especially for setting FlowTimeoutInMinutes.
  • Include bash or shell script examples for reading, exporting, and processing NSG flow logs.
  • When listing guides or tools, present cross-platform or Linux options (such as Azure CLI, bash, or Python) alongside or before Windows/PowerShell options.
  • Explicitly mention that all operations can be performed from Linux, macOS, or Windows, and provide parity in instructions.
  • Where possible, link to documentation or tutorials for Linux users, such as using jq or grep to process JSON logs.
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-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 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 is no guidance for Linux/macOS users. The focus on PowerShell and Windows-centric patterns may hinder accessibility for users on Linux or macOS platforms.
Recommendations
  • Add equivalent Azure CLI examples for deploying ARM templates, using Bash syntax and Linux/macOS file paths.
  • Include notes or sections specifying cross-platform compatibility, clarifying that Azure CLI and PowerShell are available on all major OSes.
  • Present deployment options for both PowerShell and CLI side-by-side, or allow users to select their preferred environment.
  • Avoid using Windows-specific file paths in generic instructions; use platform-neutral paths or provide both Windows and Linux/macOS examples.
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-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a strong Windows bias. All code examples are exclusively in PowerShell, which is traditionally associated with Windows environments. The authentication and environment variable setup instructions rely on PowerShell scripts and cmdlets, with no mention of Bash, Azure CLI, or Linux-native alternatives. The prerequisites and workflow sections mention both Windows and Linux VM extensions, but the step-by-step instructions and automation examples are Windows-centric. There are no Linux shell or cross-platform examples, and tools like Azure Storage Explorer (Windows-first) are referenced before any Linux alternatives.
Recommendations
  • Provide equivalent examples using Bash scripts and Azure CLI commands for Linux users.
  • Include instructions for setting up authentication and environment variables using Linux-native tools (e.g., openssl, az CLI).
  • Offer sample Azure Functions written in Python or Node.js, which are more common in Linux environments.
  • Reference Linux-compatible tools (e.g., azcopy, rclone) for downloading files from Azure Storage, alongside Azure Storage Explorer.
  • Ensure that both Windows and Linux workflows are presented in parallel, or clearly indicate cross-platform support for each step.
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-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 demonstrates a Windows bias by exclusively providing migration instructions using a PowerShell script (.ps1), referencing PowerShell as a prerequisite, and omitting any examples or guidance for running the migration on Linux or macOS platforms. While it briefly mentions that PowerShell 7 can be installed on Linux and macOS, all operational steps, script references, and screenshots are tailored to a Windows/PowerShell workflow, with no mention of Bash, Azure CLI, or cross-platform alternatives.
Recommendations
  • Provide explicit instructions and examples for running the migration script on Linux and macOS, including command syntax and environment setup.
  • Include Azure CLI or Bash script alternatives for users who prefer not to use PowerShell.
  • Add screenshots or terminal output examples from Linux/macOS environments to demonstrate parity.
  • Clarify any platform-specific requirements or limitations for the migration process.
  • Reorder prerequisites to mention cross-platform compatibility before referencing Windows/PowerShell specifics.
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-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 moderate Windows bias. PowerShell is featured as a primary automation method, and examples frequently use Windows-style file paths (e.g., C:\Capture\myVM_1.cap) before mentioning Linux equivalents. Download instructions and local file path examples default to Windows conventions, with Linux paths mentioned as secondary. References to Windows tools (PowerShell, Storage Explorer) are prominent, and Linux-specific instructions or examples are minimal or absent. There are no explicit Linux shell (bash) or OS-specific troubleshooting steps, and Windows patterns are often presented first.
Recommendations
  • Present Linux and Windows examples side-by-side, or alternate which is shown first.
  • Include bash shell commands for Linux users, especially for downloading files and managing packet captures locally.
  • Explicitly document Linux-specific troubleshooting steps or caveats where applicable.
  • Use neutral file path examples (e.g., /var/captures/myVM_1.cap and C:\Capture\myVM_1.cap together) in all relevant sections.
  • Mention Linux tools (e.g., scp, wget, curl) for downloading packet captures from VMs or storage.
  • Clarify any OS-specific limitations or behaviors in packet capture management.
  • Add links to Linux-focused documentation where available, and ensure parity in referenced resources.
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-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation exclusively provides Azure PowerShell examples for enabling and managing virtual network flow log filtering, with no mention of equivalent Azure CLI or REST API commands. This creates a bias toward Windows users and PowerShell environments, omitting guidance for Linux users who typically use Azure CLI or other cross-platform tools.
Recommendations
  • Add equivalent Azure CLI examples for all PowerShell commands shown, demonstrating how to enable, update, and manage flow log filtering from Linux/macOS environments.
  • Reference REST API documentation or provide sample API calls for users who prefer automation outside of PowerShell.
  • Explicitly mention cross-platform options and tools at the start of the article, clarifying that the functionality is accessible from Linux, macOS, and Windows.
  • Where possible, use generic terminology (e.g., 'command-line tools') rather than focusing solely on PowerShell cmdlets.
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-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 of Azure CLI, Bash, or Linux-native workflows. All prerequisite links and instructions default to PowerShell, and the use of Azure Cloud Shell is described in terms of running PowerShell, which is more familiar to Windows users. There are no Linux-specific or cross-platform examples provided, and no mention of how to accomplish the same tasks using Azure CLI or Bash.
Recommendations
  • Add parallel examples using Azure CLI (az) commands for all PowerShell cmdlet instructions.
  • Update prerequisite links to include both PowerShell and Azure CLI tabs, ensuring Linux users have clear guidance.
  • Explicitly mention that Azure Cloud Shell supports both Bash and PowerShell, and provide instructions for both.
  • Include notes or sections highlighting cross-platform compatibility and differences, if any, between PowerShell and CLI workflows.
  • Ensure that all resource creation and management steps have CLI equivalents documented and linked.
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-08 00:53
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, but PowerShell is featured heavily throughout, with detailed instructions and code blocks. PowerShell is a Windows-centric tool, and its prominence may signal a Windows bias. Additionally, references to Azure Cloud Shell and local installation instructions for Azure PowerShell are included, but there is no mention of Linux-native scripting alternatives (e.g., Bash) or cross-platform shell usage outside of Azure CLI. The documentation also refers to Azure Storage Explorer, which, while cross-platform, is historically associated with Windows. The ordering of examples (Portal, PowerShell, Azure CLI) puts PowerShell before CLI, which is more commonly used on Linux.
Recommendations
  • Add Bash shell examples alongside PowerShell and Azure CLI, especially for tasks like downloading blobs or managing resources.
  • Explicitly mention that Azure CLI commands can be run in Bash, Zsh, or other Linux shells, and provide sample usage in those environments.
  • Reorder example tabs to put Azure CLI before PowerShell, or alternate the order to avoid implicit prioritization.
  • Include notes or links for Linux users on installing and using Azure CLI and Storage Explorer on Linux.
  • When referencing Azure Cloud Shell, clarify that both Bash and PowerShell environments are available, and provide guidance for both.
  • Review screenshots and tool recommendations to ensure parity for Linux/macOS users (e.g., show Storage Explorer on Linux).
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-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows Error Codes Windows First
Summary
The documentation page demonstrates a moderate Windows bias. While it mentions Azure CLI, PowerShell, portal, and REST API as entry points, PowerShell is referenced multiple times as an alternative to CLI, and there is no explicit Linux example or parity guidance. Log file examples and error messages reference Windows-specific error codes (e.g., 'Windows error 13801'), and diagnostic logs (e.g., WFP logs) are Windows-centric. The troubleshooting guidance and log analysis are tailored to Windows environments, with no mention of Linux-based VPN devices, troubleshooting steps, or error codes.
Recommendations
  • Add explicit Linux-based troubleshooting examples, such as using Azure CLI on Linux, or analyzing logs from Linux VPN devices.
  • Include Linux error codes and diagnostic patterns alongside Windows codes in log file examples.
  • Provide parity guidance for Linux administrators, such as how to interpret logs and errors from non-Windows VPN endpoints.
  • Mention Linux tools (e.g., tcpdump, strongSwan logs) for troubleshooting VPN connections, and provide links to relevant documentation.
  • Clarify when instructions or logs are Windows-specific, and offer equivalent steps for Linux environments.
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: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a strong Windows bias by exclusively providing Azure PowerShell commands for deploying the ARM template, referencing Windows-style file paths (e.g., C:\MyTemplates\azuredeploy.json), and omitting any CLI or Bash/Linux-based deployment instructions. There are no examples or guidance for Linux or cross-platform users, and Windows tools and patterns are presented as the default.
Recommendations
  • Add equivalent Azure CLI (az) command examples for deploying the ARM template, with Linux/macOS-friendly file paths (e.g., ~/MyTemplates/azuredeploy.json).
  • Explicitly mention that both PowerShell and Azure CLI can be used, and provide parallel instructions for each.
  • Avoid using Windows-specific file paths in examples; use generic or cross-platform paths, or provide both Windows and Linux/macOS variants.
  • Include a note or section for Linux/macOS users, highlighting any differences or considerations.
  • Ensure that portal-based instructions are clearly platform-agnostic.
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: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a Windows bias primarily through the exclusive use of PowerShell (Windows-centric) for configuration examples (e.g., setting FlowTimeoutInMinutes), and by referencing PowerShell-based guides before or instead of cross-platform or Linux-native alternatives. There are no CLI (az), Bash, or Linux-specific instructions or examples provided for key tasks, such as configuring NSG flow logs or setting properties, which may disadvantage Linux users.
Recommendations
  • Provide equivalent Azure CLI (az) and/or Bash examples alongside PowerShell for all configuration tasks, especially for setting NSG properties like FlowTimeoutInMinutes.
  • When listing guides or instructions, present cross-platform (CLI, REST API, Portal) options before or alongside Windows/PowerShell-specific ones.
  • Explicitly mention that all features and configuration steps are available and supported on Linux, and link to relevant Linux or cross-platform documentation.
  • Include troubleshooting and usage examples that are relevant to Linux users, such as using jq or grep to parse logs, or automating tasks with Bash scripts.
  • Ensure that visualization and export tool instructions are not biased toward Windows-only tools (e.g., Power BI), and highlight open-source or cross-platform alternatives equally.
GitHub Create Pull Request
Network Watcher https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/network-watcher/migrate-to-connection-monitor-from-network-performance-monitor.md ...to-connection-monitor-from-network-performance-monitor.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a Windows bias by referencing Windows-specific tools and extensions (such as the Network Watcher extension for Windows), mentioning Windows/PowerShell automation before Linux equivalents, and lacking explicit Linux-focused migration instructions or examples. While Linux is mentioned in compatibility tables, there are no detailed Linux agent installation or migration steps, and references to documentation or extensions are Windows-centric.
Recommendations
  • Include explicit Linux migration steps and examples, such as how to install and configure the Network Watcher extension on Linux VMs.
  • When referencing automation (PowerShell, Azure CLI, Terraform), provide Linux/Unix shell examples alongside or before Windows/PowerShell examples.
  • Link to both Windows and Linux agent documentation where relevant, not just to Windows-specific pages.
  • Clarify any differences in agent behavior or prerequisites between Windows and Linux platforms.
  • Add troubleshooting steps and 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-connected-machine-agent.md ...-watcher/connection-monitor-connected-machine-agent.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a Windows bias by consistently presenting Windows instructions and tooling (such as PowerShell and Windows Admin Center) before Linux equivalents, providing more detailed steps for Windows, and emphasizing Windows-specific tools. Linux instructions are present but less detailed and lack parity in tooling examples (e.g., no Bash/CLI automation equivalent to PowerShell or Windows Admin Center).
Recommendations
  • Alternate the order of Windows and Linux instructions, or present them side-by-side to avoid always listing Windows first.
  • Provide Linux-specific automation examples, such as using Bash scripts or Azure CLI, in parity with PowerShell examples.
  • Include references to Linux-native management tools or workflows where Windows Admin Center is mentioned for Windows.
  • Ensure that all steps and details provided for Windows are also present for Linux, including troubleshooting and verification steps.
  • Where PowerShell cmdlets are highlighted, also mention equivalent Azure CLI or Bash commands for Linux environments.
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: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation is heavily focused on Azure PowerShell, with all examples and instructions using PowerShell cmdlets. There are no CLI, Bash, or Linux-native command examples provided, and the prerequisites and workflow assume the use of PowerShell (either locally or in Cloud Shell). This creates a Windows-centric experience, even though the VM created is Linux-based.
Recommendations
  • Provide equivalent Azure CLI (az) command examples alongside or in place of PowerShell examples, as Azure CLI is cross-platform and commonly used on Linux and macOS.
  • Explicitly mention that Azure Cloud Shell supports both Bash and PowerShell, and show how to select Bash.
  • Include Linux/Bash shell command snippets for each step, especially for users who prefer or require a non-Windows workflow.
  • Clarify that all steps can be performed from any OS using Azure CLI, not just from a Windows/PowerShell environment.
  • Where possible, link to documentation for both PowerShell and CLI approaches, and avoid implying PowerShell is the default or only method.
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: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation is heavily focused on PowerShell, providing only PowerShell-based examples and instructions for troubleshooting VPN gateways and connections. There are no equivalent examples using the Azure CLI, Bash, or other Linux-friendly tools within this page. The prerequisites and workflow assume the use of PowerShell (either in Cloud Shell or locally), which is more familiar to Windows users. While there is a link to a separate Azure CLI-based troubleshooting guide in the 'Related content' section, this page itself does not provide parity for Linux users or those preferring CLI/Bash workflows.
Recommendations
  • Add parallel Azure CLI (az) command examples alongside PowerShell examples for all troubleshooting steps.
  • Include explicit instructions for running these commands in Bash (Cloud Shell or local Linux/macOS terminal).
  • Update prerequisites to mention both PowerShell and Azure CLI as supported options, with links to installation guides for each.
  • Consider using tabbed code blocks (e.g., 'PowerShell' and 'Azure CLI') to allow users to select their preferred environment.
  • Reference the Azure CLI troubleshooting page more prominently at the start of the document, and clarify that all steps can be performed with either tool.
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: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation demonstrates subtle Windows bias. While both Windows and Linux are mentioned as supported platforms, Windows is often referenced first (e.g., 'Manage Network Watcher extension for Windows' before Linux), and PowerShell is highlighted as a primary automation method. There are no explicit Linux CLI or shell command examples, and Linux-specific tooling or workflows are not equally emphasized. The documentation lacks parity in example commands or guidance for Linux users, especially for automation and agent management.
Recommendations
  • Ensure that references to Windows and Linux are presented with equal prominence, alternating order or listing both together (e.g., 'Manage Network Watcher extension for Windows or Linux').
  • Provide equivalent example commands for both Windows (PowerShell) and Linux (Bash/Azure CLI) wherever automation or agent installation is discussed.
  • Include Linux-specific troubleshooting steps or notes where relevant, not just generic or Windows-centric guidance.
  • Highlight Azure CLI usage alongside PowerShell for cross-platform automation, and provide links to both sets of documentation.
  • Where screenshots or UI steps are shown, clarify any OS-specific differences or provide Linux-centric visuals if applicable.
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: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page exhibits several signs of Windows bias. While it mentions that VPN troubleshoot can be called via Azure portal, PowerShell, CLI, or REST API, the only specific example of command-line tooling is PowerShell (in the 'Considerations' section). There are no Linux-specific examples or instructions. Several log file examples and error messages reference Windows-specific error codes and terminology (e.g., 'Windows error 13801', 'Windows error 13843'). The log file paths and formats (e.g., C:\Resources\...) are Windows-centric. There is no mention of Linux tools or workflows for accessing or analyzing logs, nor are there CLI examples tailored for Linux environments.
Recommendations
  • Provide explicit Linux/Azure CLI examples alongside or before PowerShell examples, especially in sections discussing command-line usage.
  • Reference Linux-compatible tools (e.g., azcopy, Azure CLI, or standard Linux utilities) for downloading and analyzing logs from Azure Storage.
  • When showing log file paths, use platform-agnostic or Linux-style paths as well, or clarify that paths may differ on Linux.
  • If error codes are Windows-specific, add explanations or mappings for Linux users, or clarify how similar issues would appear on non-Windows systems.
  • Ensure that troubleshooting workflows and recommendations are equally accessible and actionable for Linux administrators.
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: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a strong bias toward Windows and PowerShell environments. All scripting and automation instructions are provided exclusively using PowerShell (.ps1 script), with no mention or example of Bash, Azure CLI, or Linux-native alternatives. The prerequisites and instructions assume the use of PowerShell, and there are no Linux-specific considerations or examples, despite PowerShell Core being cross-platform. There is also no guidance for users who may prefer or require Bash scripting or Azure CLI for automation.
Recommendations
  • Provide equivalent migration instructions and scripts using Azure CLI and/or Bash, ensuring Linux users have a first-class experience.
  • Explicitly mention that PowerShell 7 is cross-platform and provide Linux/macOS installation and usage notes, including any known issues or differences.
  • Offer downloadable migration scripts in both PowerShell (.ps1) and Bash (.sh) formats, or provide guidance on how to adapt the process for non-PowerShell environments.
  • Include Linux/macOS-specific screenshots or terminal examples where relevant.
  • Clarify any limitations or differences in running the migration process on Linux/macOS versus Windows.
GitHub Create Pull Request
← Previous Page 4 of 10 Next →