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 26-50 of 238 flagged pages
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-10 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 provides only PowerShell-based examples for diagnosing VM network routing problems. There are no Bash, Azure CLI, or Linux-native command examples, and the prerequisites and workflow assume familiarity with PowerShell and Windows-centric tooling. This creates a bias toward Windows users and may hinder Linux users or those preferring Azure CLI or Bash.
Recommendations
  • Add equivalent Azure CLI (az) commands for all steps, including VM creation, Network Watcher setup, next hop diagnostics, and resource cleanup.
  • Include Bash script examples and instructions for running commands in the Azure Cloud Shell Bash environment.
  • Explicitly mention Linux support and provide guidance for users who prefer Linux or non-PowerShell environments.
  • Reorganize prerequisites to present both PowerShell and CLI/Bash options equally, rather than defaulting to PowerShell.
  • Where possible, reference cross-platform tools and avoid assuming PowerShell as the default interface.
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-10 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 tools (PowerShell, Windows Admin Center) before or more prominently than Linux equivalents. PowerShell is highlighted as a cross-platform onboarding method, but only the Windows Admin Center is mentioned as a GUI tool, with no Linux GUI alternatives. The Linux installation steps are brief and lack detail compared to Windows, and there are no Linux-specific automation or management tool examples.
Recommendations
  • Provide Linux installation instructions with equal detail and step-by-step guidance as Windows, including troubleshooting tips.
  • Mention and link to Linux-native automation tools (e.g., Ansible, shell scripts) for agent deployment, similar to PowerShell and Windows Admin Center.
  • If GUI tools exist for Linux (such as Cockpit or other management consoles), reference them for parity with Windows Admin Center.
  • Present Windows and Linux instructions in parallel or with equal prominence, rather than leading with Windows.
  • Include Linux-specific verification steps and examples for post-installation checks, not just referencing the Azure portal.
  • Clarify that PowerShell is available on Linux, or provide Bash/CLI alternatives for all PowerShell examples.
GitHub Create Pull Request
Network Watcher Connection monitor overview ...rticles/network-watcher/connection-monitor-overview.md
High Priority View Details →
Scanned: 2026-01-10 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 moderate Windows bias. Windows is often mentioned before Linux, especially in references to the Network Watcher extension ("Manage Network Watcher extension for Windows" is listed before Linux). PowerShell is highlighted as a primary automation method, with explicit links to PowerShell-based creation of connection monitors, while Linux CLI or scripting examples are not equally emphasized. References to Windows-specific tools and concepts (e.g., 'Local Computer Trusted Certification Authorities store') appear without Linux equivalents or explanations. There are no direct Linux command-line examples or instructions for Linux-specific troubleshooting, and the documentation lacks parity in example coverage for Linux users.
Recommendations
  • Ensure Linux is mentioned alongside or before Windows in extension management and agent installation sections.
  • Provide explicit Azure CLI and Bash examples for all major tasks, including connection monitor creation and configuration.
  • Include troubleshooting guidance and terminology relevant to Linux systems (e.g., certificate stores, agent health checks).
  • Add links and examples for managing Network Watcher extension on Linux with equal prominence to Windows.
  • Clarify any platform-specific differences in agent behavior, error states, or monitoring data collection.
  • Review all references to Windows-specific tools and add Linux equivalents or note differences.
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-10 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 or examples of equivalent Azure CLI commands or Bash scripting. The prerequisites and workflow are centered around PowerShell, which is traditionally associated with Windows environments, even though Azure Cloud Shell supports Bash and Azure CLI. There is no guidance for Linux users or parity in tooling, leading to a clear Windows/PowerShell bias.
Recommendations
  • Add equivalent Azure CLI (az) commands for each PowerShell example, ideally side-by-side or in separate tabs.
  • Update the prerequisites section to mention Bash and Azure CLI as fully supported alternatives, with links to installation and usage guides.
  • Include instructions for running the workflow in Bash (Cloud Shell or local Linux/macOS terminal), highlighting any differences or considerations.
  • Ensure that references to tools and modules (such as Az PowerShell) are balanced with Azure CLI documentation.
  • Consider using neutral language in titles and descriptions, e.g., 'Diagnose a VM traffic filter problem - Azure PowerShell or CLI', to signal cross-platform support.
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-10 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 Windows migration steps before Linux, and lacking explicit Linux-focused migration examples or guidance. Automation examples mention PowerShell first, and references to agent installation and migration steps are primarily focused on Windows VMs, with Linux support only briefly mentioned in a comparison table.
Recommendations
  • Provide explicit migration instructions and examples for Linux VMs, including agent installation and extension enablement steps.
  • Include Linux-specific troubleshooting guidance and error messages where relevant.
  • Present automation options (PowerShell, Azure CLI, Terraform) in a neutral order or highlight cross-platform parity.
  • Reference both Windows and Linux documentation links for agent installation and migration.
  • Clarify differences in agent behavior or requirements between Windows and Linux environments.
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-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page mentions automation via PowerShell, Azure CLI, and Terraform, listing PowerShell first, which may suggest a Windows-first approach. There are no explicit Linux-specific examples, commands, or troubleshooting steps, and no mention of Linux tools or shell commands. The documentation does not provide parity in examples or instructions for Linux users, focusing on generic or Windows-centric patterns.
Recommendations
  • Provide explicit Linux shell (bash) examples alongside PowerShell for automation tasks.
  • 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).
  • Mention Linux-specific tools or commands where appropriate, such as using shell scripts for agent installation.
  • Clarify that instructions apply to both Windows and Linux VMs, and highlight any differences in process.
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-10 00:00
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. The bulk of automation and scripting guidance is provided via PowerShell, which is a Windows-centric tool, and the only bulk-update script is for Windows VMs using PowerShell. PowerShell is presented as the primary automation method, with no equivalent Bash or shell script for Linux VM bulk updates. In several sections, Windows examples or tools (PowerShell) are mentioned before Linux alternatives, and the scripting patterns are tailored to Windows environments. While Azure CLI examples are provided for both platforms, advanced scenarios and automation are Windows-focused.
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.
  • Offer parity in automation guidance by including Linux-native tooling (e.g., Bash, Python, Ansible) for managing extensions at scale.
  • When listing manual update options, alternate the order of Windows and Linux examples, or present them side-by-side to avoid implicit prioritization.
  • Explicitly mention cross-platform tools (like Azure CLI) as the recommended approach for both Windows and Linux, and clarify when PowerShell is required or optional.
  • Add troubleshooting and support guidance specific to Linux environments, not just generic or Windows-centric advice.
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-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
Although the documentation is for Linux VMs, it consistently presents PowerShell (a Windows-centric tool) as a primary management option alongside Azure CLI and Portal. PowerShell examples and instructions are given equal or greater prominence, and references to installing Azure PowerShell locally (a Windows-first pattern) are frequent. There is no mention of native Linux shell scripting or Linux-specific management tools (e.g., Bash, SSH, Ansible), and the workflow assumes users are comfortable with PowerShell, which is less common on Linux. The documentation also refers to 'Azure Cloud Shell' generically, but emphasizes PowerShell usage and installation, which may reinforce Windows-centric patterns.
Recommendations
  • Prioritize Azure CLI examples and instructions before PowerShell, as CLI is more native to Linux environments.
  • Include Bash shell script examples for common tasks (install, uninstall, list extensions) to improve Linux parity.
  • Mention Linux-native automation tools (e.g., Ansible, SSH) as alternatives for managing extensions.
  • Clarify that PowerShell is cross-platform, but highlight that Azure CLI is typically pre-installed or easier to use on Linux.
  • Reduce emphasis on installing Azure PowerShell locally, and provide guidance for Linux users who may prefer CLI or Bash.
  • Add troubleshooting and management tips specific to Linux environments (e.g., log file locations, systemd integration, SELinux considerations).
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-10 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 featured prominently and often mentioned before Azure CLI, with detailed instructions and notes about installing and running PowerShell locally (which is primarily a Windows tool, though cross-platform now). In several places, customization options are described as only available via PowerShell or REST API, with CLI mentioned after or not at all. The documentation refers to Azure Cloud Shell, which is cross-platform, but local instructions and links are PowerShell-centric. There is no explicit mention of Linux-specific considerations, nor are Linux shell examples (e.g., bash) provided.
Recommendations
  • Ensure Azure CLI examples and instructions are given equal prominence and detail as PowerShell, especially for customization options.
  • Explicitly mention that Azure CLI runs natively on Linux/macOS and provide installation instructions for those platforms.
  • Where PowerShell is referenced for local installation, also reference bash or other Linux-native shells for CLI usage.
  • If customization is possible via Azure CLI or REST API, clarify those options and provide examples.
  • Avoid language that implies PowerShell is the default or preferred tool, and balance with CLI and cross-platform guidance.
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-10 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 and automation examples, with no mention of Bash, Python, or other cross-platform alternatives. It references PowerShell naming standards and cmdlets, and does not provide Linux or macOS-specific guidance or examples. The workflow assumes familiarity with Windows-centric tools and patterns, such as Send-MailMessage and AzureRM modules, which are most commonly used in Windows environments.
Recommendations
  • Include equivalent Bash or Python script examples for Linux users, leveraging Azure CLI or REST API calls.
  • Mention that Azure Automation supports Python runbooks and provide a sample Python implementation for the same scenario.
  • Reference cross-platform tools and patterns (e.g., Azure CLI, az commands) alongside PowerShell, and clarify which steps are platform-agnostic.
  • Add notes or sections highlighting any differences or additional steps required when using Linux/macOS environments.
  • Avoid assuming PowerShell as the default scripting language; present it as one option among several.
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-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page demonstrates a Windows bias primarily through the exclusive use of PowerShell for configuration examples (e.g., setting FlowTimeoutInMinutes), referencing Windows-centric tools (Power BI), and listing PowerShell-based guides before any Linux/CLI alternatives. There are no Bash, Azure CLI, or Linux-native command examples for managing or configuring NSG flow logs, and the only code sample for changing network settings uses PowerShell. This may make it less accessible for Linux users or those preferring cross-platform tooling.
Recommendations
  • Provide equivalent Azure CLI and/or Bash examples alongside PowerShell for all configuration and management tasks, especially for setting properties like FlowTimeoutInMinutes.
  • When listing guides or tools, ensure Azure CLI and cross-platform options are mentioned alongside or before PowerShell/Windows-specific ones.
  • Include references to Linux-compatible visualization tools (such as Kibana, or open-source alternatives) with equal prominence as Power BI.
  • Explicitly state when a procedure is platform-agnostic or provide platform-specific instructions for both Windows and Linux.
  • Audit all linked articles (e.g., 'Read flow logs using PowerShell functions') to ensure Linux/CLI parity and update links or content as needed.
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-10 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 are given in Windows format (e.g., C:\MyTemplates\azuredeploy.json), and there is no guidance for Linux or macOS users. The use of PowerShell is assumed throughout, and no Linux-specific tools or cross-platform alternatives are provided.
Recommendations
  • Add Azure CLI examples for deploying ARM templates, which work on Linux, macOS, and Windows.
  • Include file path examples using Linux/macOS conventions (e.g., /home/user/azuredeploy.json) alongside Windows paths.
  • Explicitly mention that Azure CLI and PowerShell are both supported, and provide links to installation guides for each platform.
  • Add a note or section for Linux/macOS users, clarifying any differences in commands or environment setup.
  • Consider reordering instructions so that cross-platform tools (Azure CLI) are presented before or alongside PowerShell.
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-10 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 demonstrates a strong Windows bias by exclusively providing PowerShell-based examples and scripts for Azure Functions and authentication, with no equivalent Bash, CLI, or Linux-native code samples. Windows tools and patterns (such as PowerShell cmdlets, Windows extension references, and Windows-style file paths) are mentioned and used throughout, while Linux alternatives are either absent or only referenced in passing. The documentation assumes familiarity with Windows-centric workflows and does not offer guidance for users who prefer Linux environments.
Recommendations
  • Provide equivalent examples using Azure CLI, Bash, or Python for all PowerShell scripts and automation steps.
  • Include Linux-specific instructions for authentication, environment variable management, and packet capture initiation (e.g., using Bash scripts or Azure CLI commands).
  • Reference both Windows and Linux VM extensions equally, and offer guidance on differences in setup or troubleshooting.
  • Avoid using Windows-style file paths (e.g., C:\temp) in generic examples; use platform-neutral or Linux-style paths when possible.
  • Mention and demonstrate cross-platform tools and workflows, such as using Azure CLI or REST API, to ensure parity for Linux users.
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-10 00:00
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 managing and filtering virtual network flow logs, with no mention of Azure CLI, Bash, or Linux-native tools. All code samples use PowerShell cmdlets, which are primarily associated with Windows environments, and there is no guidance for users working on Linux or macOS platforms.
Recommendations
  • Add equivalent Azure CLI examples for all operations (creation, updating, filtering) to support Linux and macOS users.
  • Explicitly mention cross-platform options, such as Bash scripts or REST API usage, where applicable.
  • Include a section comparing PowerShell and CLI usage, highlighting platform compatibility.
  • Ensure links to Azure CLI documentation are provided alongside PowerShell references.
  • Review related content pages for similar bias and update them for parity.
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-10 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 using a PowerShell script (.ps1), referencing PowerShell as a prerequisite, and not offering any Linux-specific or cross-platform CLI examples (such as Bash or Azure CLI). The script and instructions assume familiarity with PowerShell, which is more commonly used on Windows, and do not mention alternative methods for Linux users beyond a generic link to PowerShell installation.
Recommendations
  • Provide equivalent migration instructions using Azure CLI or Bash scripts, which are natively available on Linux and macOS.
  • Include explicit examples of running the migration script on Linux and macOS, such as using pwsh (PowerShell Core) and any required permissions or environment setup.
  • Clarify cross-platform compatibility of the migration script, including any OS-specific caveats or requirements.
  • List prerequisites for Linux and macOS environments separately, including package managers and installation steps.
  • Offer troubleshooting tips for common issues encountered on non-Windows platforms (e.g., file permissions, execution policies).
GitHub Create Pull Request
Network Watcher Manage packet captures ...main/articles/network-watcher/packet-capture-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 🔧 Windows Tools Powershell Heavy
Summary
The documentation page demonstrates a mild Windows bias. Windows file paths (C:\Capture\...) are consistently presented before Linux equivalents (/var/captures) in both tables and examples. PowerShell is given a dedicated tab and is referenced as a primary automation method, with cmdlet examples and links to Windows-specific extension management. The download examples for packet captures use Windows-style paths by default. Azure Storage Explorer, a Windows-centric tool, is mentioned as the recommended GUI for downloading files, with no mention of Linux alternatives. While Linux is supported and referenced, it is generally presented after Windows, and Linux-specific tooling or workflows are not highlighted.
Recommendations
  • Present Linux and Windows file path examples side-by-side or alternate their order to avoid always listing Windows first.
  • Explicitly mention Linux tools for downloading and managing packet captures, such as azcopy, wget, or native Linux file managers.
  • Include references to Linux-friendly GUI tools (e.g., cross-platform Storage Explorer, Nautilus, Dolphin) for accessing Azure Storage.
  • Ensure that extension management links and instructions for Linux are as prominent and detailed as those for Windows.
  • Where PowerShell is referenced, also mention Bash scripting and provide equivalent Bash/CLI automation examples.
  • Clarify that all CLI and portal instructions apply equally to Linux and Windows VMs, and highlight any OS-specific caveats.
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-10 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 and references Azure Cloud Shell and local PowerShell installation for all example workflows. There are no CLI (az), Bash, or Linux-native examples provided, and prerequisites and links consistently point to PowerShell-based instructions. This creates a strong Windows and PowerShell bias, making it less accessible for Linux or cross-platform users who may prefer Bash, Azure CLI, or automation via shell scripts.
Recommendations
  • Add equivalent Azure CLI (az) examples for all PowerShell cmdlets shown, with clear code blocks and instructions.
  • Update prerequisite links to include both PowerShell and Azure CLI/Bash tabs, ensuring parity in setup steps.
  • Mention and demonstrate how to use Azure CLI in Azure Cloud Shell, which is available for both Windows and Linux users.
  • Explicitly state that all operations can be performed from Linux/macOS environments using Azure CLI, and provide sample commands.
  • Ensure that documentation does not assume PowerShell as the default tool, and present both PowerShell and CLI options side-by-side.
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-10 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 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 most familiar to Windows users. There is no mention of Linux-specific tools, nor are CLI examples integrated into the main content (only referenced in 'Related content'). This creates a Windows-centric experience and may hinder Linux users seeking parity.
Recommendations
  • Add equivalent Azure CLI examples alongside PowerShell steps, either in parallel tabs or inline, to ensure Linux users have direct guidance.
  • Explicitly mention that Azure Cloud Shell supports both Bash and PowerShell, and provide instructions for both.
  • Reference Linux-native tools or workflows where appropriate, such as using Bash scripts or integrating with Linux shell environments.
  • Reorder or balance examples so that CLI and PowerShell are presented with equal prominence, avoiding a 'Windows first' impression.
  • Clarify in prerequisites that all steps can be performed from Linux environments using Azure CLI or Bash in Cloud Shell.
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-10 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 Windows bias by exclusively using a Windows Server VM image, guiding users to connect via RDP (Remote Desktop Protocol), and referencing Microsoft Edge as the browser to test outbound connectivity. There are no instructions or examples for deploying or connecting to a Linux VM, nor are SSH or Linux-native tools mentioned. The documentation assumes a Windows environment for both VM creation and user interaction, omitting Linux alternatives throughout.
Recommendations
  • Include parallel instructions for creating a Linux VM (e.g., Ubuntu) alongside the Windows VM steps.
  • Provide SSH connection steps for Linux VMs, including port selection and security recommendations.
  • Demonstrate how to test outbound connectivity from a Linux VM (e.g., using curl or wget in the terminal).
  • Mention Linux-compatible text editors (e.g., nano, vim, gedit) for viewing downloaded flow logs.
  • Add notes or examples for using Azure CLI or Bash scripts, not just portal-based workflows.
  • Reference Linux tools for downloading and viewing logs (e.g., azcopy, Azure CLI storage commands).
GitHub Create Pull Request
Network Watcher VPN troubleshoot overview .../articles/network-watcher/vpn-troubleshoot-overview.md
High Priority View Details →
Scanned: 2026-01-10 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 several signs of Windows bias. Powershell is mentioned as a primary method for interacting with the VPN troubleshoot feature, and in some cases, is required 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 formatting. There is no mention of Linux-specific troubleshooting tools, error codes, or log formats. The documentation does not provide Linux command-line examples or guidance for Linux administrators, and Windows-centric tools and patterns are referenced without Linux equivalents.
Recommendations
  • Add Linux-specific troubleshooting examples and guidance, including command-line usage with Azure CLI and REST API from Linux shells.
  • Include information about interpreting logs and error codes on Linux VPN devices, such as strongSwan or Openswan.
  • Provide parity in instructions for downloading and analyzing logs using Linux tools (e.g., azcopy, curl, unzip) alongside Storage Explorer.
  • Reference Linux error codes and troubleshooting steps for common VPN issues.
  • Clarify that log file paths and error codes may differ on non-Windows platforms and provide examples for Linux environments.
  • Ensure that Powershell is not presented as the only or preferred method, and that Linux administrators have clear, equivalent workflows.
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-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation consistently uses Windows-centric examples, specifically RDP (port 3389) for connectivity tests, and refers to Windows tools and patterns (RDP, PowerShell) without providing equivalent Linux scenarios (such as SSH on port 22). There are no explicit Linux-focused troubleshooting examples, and the guidance assumes Windows as the default operating system for virtual machines.
Recommendations
  • Include Linux-centric examples, such as testing SSH connectivity (port 22) between Linux VMs, alongside or before RDP examples.
  • Explicitly mention Linux operating systems in troubleshooting scenarios, including common firewall and listener issues for Linux (e.g., SSH service not running, iptables/firewalld blocking).
  • Provide command-line examples using Bash and Linux-native tools where relevant, not just PowerShell.
  • When discussing solutions, include steps for both Windows (RDP) and Linux (SSH) environments, such as enabling the SSH service or adjusting UFW/iptables rules.
  • Balance the use of Windows and Linux terminology and tools throughout the documentation to ensure parity and inclusivity for cross-platform users.
GitHub Create Pull Request
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-09 00:34
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 PowerShell syntax for all examples and instructions, with no mention or examples of equivalent Azure CLI or Bash commands. This creates a strong Windows bias, as PowerShell is most commonly used on Windows, and Linux users typically use Bash or Azure CLI. The prerequisites and workflow assume PowerShell usage, and there is no guidance for Linux users or parity in tooling.
Recommendations
  • Add equivalent Azure CLI examples for each PowerShell command, using Bash syntax.
  • Include instructions for running commands in Bash within Azure Cloud Shell, which supports both Bash and PowerShell.
  • Update prerequisites to mention Azure CLI as an alternative to Azure PowerShell.
  • Provide guidance for Linux users, including installation and usage of Azure CLI.
  • Ensure that examples and instructions are presented in a cross-platform manner, or explicitly state which steps are platform-specific.
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-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates Windows bias by referencing Windows-specific tools and extensions before Linux equivalents, such as the Network Watcher extension for Windows VMs and linking to a Windows-focused agent installation guide. Automation examples mention PowerShell before the Azure CLI and Terraform, and there are no explicit Linux migration examples or Linux agent installation instructions. Linux support is mentioned, but details and parity are lacking compared to Windows.
Recommendations
  • Provide explicit Linux migration steps and examples, including agent installation and configuration for Linux VMs.
  • Link to both Windows and Linux agent documentation, not just Windows-focused guides.
  • Ensure automation examples (PowerShell, CLI, Terraform) are presented in a cross-platform manner, with CLI and Terraform shown before or alongside PowerShell.
  • Clarify Linux support for all features, especially where previous limitations existed (e.g., Service Connectivity Monitor, ExpressRoute).
  • Add troubleshooting and error messages specific to Linux environments where relevant.
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-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation demonstrates a moderate Windows bias. PowerShell is presented as a primary automation method alongside Azure CLI, with detailed instructions and references to installing PowerShell locally (a Windows-centric pattern). Customization options (such as naming instances) are described first for PowerShell, and users are directed to PowerShell or REST API for advanced tasks, even when Azure CLI is available. References to installing PowerShell locally and using PowerShell cmdlets are more prominent than equivalent Linux shell instructions. The documentation does not mention Linux-specific shell environments (bash, zsh), nor does it clarify cross-platform usage for CLI commands.
Recommendations
  • Explicitly state that Azure CLI is cross-platform and provide examples of running CLI commands in bash/zsh on Linux and macOS.
  • Include instructions for installing and using Azure CLI on Linux and macOS, not just PowerShell.
  • When discussing advanced customization (e.g., naming instances), clarify if and how it can be done with Azure CLI, or provide parity in examples.
  • Avoid suggesting PowerShell as the only way to perform advanced tasks; highlight REST API and CLI alternatives where possible.
  • Add notes or examples for Linux users, such as using bash in Azure Cloud Shell or running CLI commands in local Linux environments.
  • Balance references to PowerShell and CLI, ensuring neither is presented as the default or preferred option unless technically justified.
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-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 PowerShell for scripting and automation examples, with no mention of Bash, Python, or other cross-platform alternatives. The runbook creation process is described using PowerShell cmdlets and Windows-centric tooling, and there are no Linux or macOS-specific instructions or code samples. The guidance assumes familiarity with PowerShell and Windows conventions, such as naming standards and the Send-MailMessage cmdlet, which are not natively available on Linux systems.
Recommendations
  • Add equivalent Bash or Python script examples for monitoring VPN gateways using Azure CLI or REST API, which are cross-platform.
  • Include instructions for creating and running runbooks using non-PowerShell types, such as Python or Bash, and highlight how Linux users can automate similar workflows.
  • Mention Linux-compatible tools for sending email notifications (e.g., using 'mail' or 'sendmail' in Bash, or Python's smtplib).
  • Clarify that Azure Automation supports multiple runbook types and provide links or examples for Linux/macOS users.
  • Avoid language that assumes PowerShell is the default or only option; present alternatives side-by-side where possible.
GitHub Create Pull Request
← Previous Page 2 of 10 Next →