Network Watcher

126
Total Pages
102
Linux-Friendly Pages
24
Pages with Bias
19.0%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

50 issues found
Showing 26-50 of 50 flagged pages
Network Watcher Filter Virtual Network Flow Logs (Preview) ...n/articles/network-watcher/vnet-flow-logs-filtering.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
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 (using cmdlets like New-AzNetworkWatcherFlowLog and Set-AzNetworkWatcherFlowLog) for all tasks related to filtering virtual network flow logs. There are no CLI (az), Bash, or REST API examples, which are preferred or required on Linux/macOS platforms. The use of PowerShell cmdlets and syntax is inherently Windows-centric and may create friction for users on other operating systems.
Recommendations
  • Add equivalent Azure CLI (az network watcher flow-log ...) examples for all tasks, including creation, updating, and filtering.
  • Include Bash script snippets or REST API payloads for users who do not use PowerShell.
  • Clearly state at the beginning that PowerShell is cross-platform, but provide links or guidance for installing and using PowerShell on Linux/macOS if PowerShell is required.
  • Consider listing CLI/Bash examples before or alongside PowerShell to avoid implicit prioritization of Windows workflows.
GitHub Create Pull Request
Network Watcher Troubleshoot outbound connections ...cles/network-watcher/connection-troubleshoot-manage.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation consistently uses Windows-centric examples, notably focusing on RDP (port 3389) for connectivity tests, which is a Windows-only protocol. There are no Linux-specific scenarios (e.g., SSH on port 22), nor any mention of Linux troubleshooting patterns or tools. The examples, solutions, and troubleshooting steps all assume Windows environments, creating friction for Linux/macOS users who need to adapt instructions for their platforms.
Recommendations
  • Include Linux-specific connectivity scenarios, such as testing SSH (port 22) between Linux VMs.
  • Provide troubleshooting examples for Linux guest firewalls (e.g., iptables, firewalld, ufw) alongside Windows firewall instructions.
  • Add notes or sections explaining how to adapt PowerShell/CLI commands for Linux/macOS environments, including differences in authentication and shell usage.
  • Ensure that examples alternate between Windows and Linux use cases, or present both side-by-side where relevant.
  • Mention common Linux tools (e.g., netstat, ss, systemctl) when discussing OS-level listener issues.
GitHub Create Pull Request
Network Watcher Diagnose a VM network routing problem - Azure PowerShell ...cher/diagnose-vm-network-routing-problem-powershell.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
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 or Bash alternatives. All instructions and code samples are PowerShell-based, which are native to Windows and less familiar to Linux/macOS users. There is no guidance for users who prefer or require Bash or Azure CLI, nor are there notes about cross-platform usage.
Recommendations
  • Add equivalent Azure CLI (az) commands for all major steps, including VM creation, Network Watcher setup, next hop diagnostics, and resource cleanup.
  • Explicitly mention that Azure Cloud Shell supports both Bash and PowerShell, and provide links or toggles to switch between example types.
  • Include notes or sections for Linux/macOS users, clarifying how to run these diagnostics using their preferred shell.
  • Ensure that introductory and prerequisite sections highlight cross-platform options and do not imply PowerShell is required.
GitHub Create Pull Request
Network Watcher Quickstart: Diagnose a VM traffic filter problem - Azure PowerShell ...agnose-vm-network-traffic-filtering-problem-powershell.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation exclusively uses Azure PowerShell cmdlets for all steps, with no mention or examples of Azure CLI, Bash, or Linux-native tooling. All code blocks are PowerShell, and instructions reference PowerShell-specific modules and commands. While Azure Cloud Shell is cross-platform, the focus on PowerShell and lack of Linux CLI examples creates friction for Linux/macOS users who may prefer Bash or Azure CLI.
Recommendations
  • Provide equivalent Azure CLI (az) commands for each PowerShell example, ideally side-by-side.
  • Clarify that Azure Cloud Shell supports both Bash and PowerShell, and show how to select Bash.
  • Mention that all tasks can be completed using Azure CLI from Linux/macOS terminals.
  • Add links to Azure CLI documentation for relevant operations.
  • Consider reordering examples so Bash/Azure CLI is shown first or equally with PowerShell.
GitHub Create Pull Request
Network Watcher Check security rules using NSG diagnostics ...les/network-watcher/diagnose-network-security-rules.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation consistently uses Windows Server as the example operating system for virtual machine creation, both in the Azure Portal and in CLI/PowerShell instructions. There are no examples or instructions for creating or managing Linux-based VMs, nor any mention of Linux-specific considerations. This creates a subtle but notable bias toward Windows, potentially leaving Linux users without direct guidance for their scenarios.
Recommendations
  • Add parallel examples for creating and managing Linux virtual machines (e.g., using Ubuntu or CentOS images) in all sections where VM creation is demonstrated.
  • Explicitly mention that the steps apply to both Windows and Linux VMs, and highlight any differences in network security group configuration or diagnostics relevant to Linux.
  • Where VM image selection is shown, provide both Windows and Linux options, or use a generic placeholder and explain how to select either.
  • Include notes or links to Linux-specific troubleshooting or diagnostic procedures if any exist.
GitHub Create Pull Request
Network Watcher Tutorial: Diagnose a VM network routing problem - Azure portal ...network-watcher/diagnose-vm-network-routing-problem.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The tutorial exclusively uses Windows Server as the VM image and provides only RDP-based connection instructions, with no mention of Linux VM creation, SSH access, or Linux-specific steps. All examples and screenshots assume a Windows environment, which may hinder Linux/macOS users from following the tutorial directly.
Recommendations
  • Include parallel instructions for creating a Linux VM (e.g., Ubuntu) alongside the Windows VM steps.
  • Provide SSH connection instructions for Linux VMs, including port selection and credential setup.
  • Add screenshots and examples showing Linux VM network troubleshooting (e.g., using a browser or curl from a Linux shell).
  • Mention that the tutorial applies to both Windows and Linux VMs, and clarify any OS-specific differences.
  • Ensure that references to CLI and PowerShell tutorials are equally visible and clarify their cross-platform applicability.
GitHub Create Pull Request
Network Watcher Migrate to Connection monitor from Network performance monitor ...to-connection-monitor-from-network-performance-monitor.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page shows evidence of Windows bias. Windows tools and patterns are mentioned first or exclusively, such as referencing the Network Watcher extension for Azure VMs with a link specifically to the Windows agent documentation. There is no equivalent mention or link for Linux agent installation or migration steps. Additionally, the migration instructions and prerequisites focus on Windows-centric workflows, with no Linux-specific examples or guidance, despite the product supporting Linux endpoints.
Recommendations
  • Add explicit instructions and links for installing and migrating the Network Watcher extension on Linux VMs, similar to the Windows documentation.
  • Provide Linux-specific troubleshooting steps and error messages where relevant.
  • Ensure that examples and references to agent installation, migration, and configuration are presented for both Windows and Linux, or in a platform-neutral manner.
  • Where tools or extensions differ by OS, mention both equally and provide parity in documentation coverage.
GitHub Create Pull Request
Network Watcher Manage Network Watcher Agent VM extension - Linux ...rticles/network-watcher/network-watcher-agent-linux.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation, while focused on Linux VMs, consistently presents PowerShell-based examples and instructions alongside Azure CLI and Portal methods. PowerShell is a Windows-centric tool, and its inclusion (and occasional prioritization) may create friction for Linux/macOS users. Additionally, references to 'installing Azure PowerShell locally' and using PowerShell cmdlets are present in multiple sections, sometimes before Azure CLI alternatives. The documentation does not provide native Linux shell (bash) or scripting examples, and relies heavily on Azure PowerShell, which is less common on Linux platforms.
Recommendations
  • Prioritize Azure CLI examples over PowerShell in Linux-focused documentation, as CLI is cross-platform and more familiar to Linux users.
  • Where PowerShell is mentioned, clarify its cross-platform availability and provide installation instructions for Linux/macOS if relevant.
  • Add native bash script examples for common tasks (listing, installing, uninstalling extensions) to improve accessibility for Linux users.
  • Review the order of examples and instructions to ensure CLI and Portal methods are presented before PowerShell in Linux documentation.
  • Consider removing or minimizing references to Windows-specific tools unless they offer unique functionality not available in CLI.
GitHub Create Pull Request
Network Watcher Update Network Watcher extension to the latest version ...ticles/network-watcher/network-watcher-agent-update.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation demonstrates a moderate Windows bias, primarily through the use of PowerShell for automation and bulk update scenarios, with no equivalent Bash or Linux shell scripting example. Windows tooling (PowerShell) is presented as the default for scripting, and the bulk update script is Windows-centric, even though it nominally supports Linux VMs. In several sections, Windows examples or tools are mentioned first, and Linux parity is only achieved in CLI commands, not in automation or scripting guidance.
Recommendations
  • Provide a Bash or shell script example for bulk updating Network Watcher extensions on Linux VMs, using Azure CLI.
  • When presenting manual update instructions, alternate the order of Windows and Linux examples, or present them side-by-side.
  • Explicitly mention cross-platform automation options (e.g., Azure CLI in Bash, Python SDK) for large deployments, not just PowerShell.
  • Clarify which commands/tools are cross-platform and which are Windows-only.
  • Add a note that PowerShell Core is available on Linux/macOS, if relevant, and provide usage guidance.
GitHub Create Pull Request
Network Watcher Troubleshoot and monitor VPN gateways - Azure Automation ...tcher/network-watcher-monitor-with-azure-automation.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation exclusively uses PowerShell for scripting and automation examples, with no mention of Bash, Azure CLI, or other cross-platform alternatives. All code samples, naming conventions, and runbook types are centered around PowerShell, which is traditionally associated with Windows environments. There is no guidance for Linux/macOS users or for using non-Windows tools.
Recommendations
  • Provide equivalent examples using Azure CLI and/or Bash scripts, which are natively supported on Linux/macOS.
  • Clarify that Azure Automation runbooks can use Python or other languages, and provide sample runbooks in those formats.
  • Include notes or sections specifically addressing Linux/macOS users, outlining any differences in setup or execution.
  • List PowerShell and non-PowerShell options side-by-side, or indicate which steps are platform-agnostic.
GitHub Create Pull Request
Network Watcher NSG Flow Logs Overview ...ain/articles/network-watcher/nsg-flow-logs-overview.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page shows evidence of Windows bias, primarily through the use of PowerShell in configuration examples (e.g., setting FlowTimeoutInMinutes), references to Windows-centric tools (Power BI), and listing PowerShell-based guides before Linux-friendly alternatives. There are no explicit Linux CLI (az CLI, Bash) examples for key configuration steps, and PowerShell is presented as the main automation method. Visualization and export guides do mention cross-platform tools (Grafana, Elastic Stack), but Windows/PowerShell approaches are generally listed first or exclusively for some tasks.
Recommendations
  • Add equivalent az CLI and Bash examples for all PowerShell configuration steps, especially for setting properties like FlowTimeoutInMinutes.
  • Ensure that Linux/macOS-friendly tools and workflows (e.g., az CLI, Bash scripts) are mentioned alongside or before Windows/PowerShell methods.
  • Provide explicit Linux/macOS instructions for downloading, reading, and exporting flow logs, including sample commands.
  • Balance the order of tool recommendations so that cross-platform solutions (Grafana, Elastic Stack) are not listed after Windows-centric tools.
  • Where PowerShell is referenced, clarify that az CLI and REST API alternatives exist and link to them.
GitHub Create Pull Request
Network Watcher Migrate to virtual network flow logs ...main/articles/network-watcher/nsg-flow-logs-migrate.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page is heavily biased toward Windows and PowerShell. The migration script is provided only as a PowerShell (.ps1) file, and all instructions for running the migration use PowerShell commands and conventions. There are no examples or guidance for Linux/macOS users, such as using Bash, Azure CLI, or cross-platform scripting. The prerequisites and workflow assume PowerShell is the primary or only tool, and Windows-centric terminology and patterns are used throughout.
Recommendations
  • Provide equivalent migration scripts using Bash or Azure CLI for Linux/macOS users.
  • Include explicit instructions and examples for running the PowerShell script on Linux/macOS, including prerequisites and troubleshooting.
  • List installation steps for PowerShell on Linux/macOS before or alongside Windows instructions, not after.
  • Clarify any platform-specific limitations or requirements for the migration process.
  • Consider offering a cross-platform script (e.g., Python) or an Azure CLI-based workflow.
GitHub Create Pull Request
Network Watcher Quickstart: Configure NSG flow logs using an ARM template ...ain/articles/network-watcher/nsg-flow-logs-template.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
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 for deployment instructions and examples, with no mention of Azure CLI or Bash alternatives. File paths use Windows conventions, and there are no Linux/macOS-specific instructions or examples. This creates friction for users on non-Windows platforms.
Recommendations
  • Add equivalent Azure CLI deployment instructions and examples, using Bash syntax and Linux/macOS file paths.
  • Explicitly state that the ARM template can be deployed from any OS using Azure CLI, PowerShell, or the portal.
  • Provide cross-platform notes or links to relevant documentation for Linux/macOS users.
  • Show both Windows and Linux file path examples when referencing local files.
GitHub Create Pull Request
Network Watcher Tutorial: Log network traffic ...in/articles/network-watcher/vnet-flow-logs-tutorial.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The tutorial demonstrates a notable Windows bias: the virtual machine is created with Windows Server, and all remote access instructions use RDP, a Windows-centric protocol. There are no examples or instructions for creating or accessing a Linux VM, nor for using SSH (the standard for Linux/macOS). The workflow assumes use of Microsoft Edge within the Windows VM, further reinforcing the Windows focus. No Linux-specific tools, patterns, or alternatives are mentioned.
Recommendations
  • Add parallel instructions for creating a Linux VM (e.g., Ubuntu) and accessing it via SSH, including opening port 22 in the network security group.
  • Provide examples for downloading and viewing flow logs from a Linux VM, such as using curl, wget, or Azure CLI.
  • Mention cross-platform tools (e.g., Azure Storage Explorer is available for Linux/macOS) and provide usage examples.
  • Clarify that the tutorial works for both Windows and Linux VMs, and highlight any differences in setup or access.
  • Include screenshots or terminal commands relevant to Linux/macOS environments.
GitHub Create Pull Request
Network Watcher Managed Identity for Virtual Network Flow Logs ...les/network-watcher/vnet-flow-logs-managed-identity.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation is heavily focused on Azure PowerShell cmdlets, with all examples and prerequisite links referencing PowerShell. There are no CLI (az), Bash, or Linux/macOS-specific instructions, and the guidance assumes use of Azure Cloud Shell or local PowerShell installation. This creates friction for Linux/macOS users who may prefer or require Bash or Azure CLI workflows.
Recommendations
  • Add equivalent Azure CLI (az) examples for all PowerShell cmdlets shown.
  • Include Bash script examples where appropriate, especially for Cloud Shell usage.
  • Update prerequisite links to include both PowerShell and CLI/Bash instructions.
  • Clarify that Azure Cloud Shell supports Bash as well as PowerShell, and provide guidance for both.
  • Ensure that all critical tasks can be completed using Azure CLI/Bash, not just PowerShell.
GitHub Create Pull Request
Network Watcher VPN troubleshoot overview .../articles/network-watcher/vpn-troubleshoot-overview.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
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 moderate Windows bias. While it mentions that VPN troubleshooting can be performed via Azure portal, PowerShell, CLI, or REST API, several examples and log file contents reference Windows-specific tools, error codes, and terminology (e.g., Windows error codes in logs, WFP logs, and PowerShell as a workaround for CLI limitations). Linux/macOS equivalents are not discussed, and Windows terminology appears first or exclusively in critical troubleshooting sections.
Recommendations
  • Provide explicit Linux/macOS command examples for VPN troubleshooting using Azure CLI and REST API.
  • Clarify how Linux/macOS users can interpret log files, especially those referencing Windows error codes (e.g., ERROR_IPSEC_IKE_AUTH_FAIL).
  • Include troubleshooting steps or log analysis guidance for non-Windows VPN devices and platforms.
  • List Linux/macOS tools (e.g., azcopy, native CLI commands) for downloading blobs from Azure Storage, alongside Storage Explorer.
  • Avoid using Windows terminology (e.g., WFP, Windows error codes) without explanation or cross-reference for other platforms.
GitHub Create Pull Request
Network Watcher Troubleshoot VPN gateways and connections - PowerShell ...rticles/network-watcher/vpn-troubleshoot-powershell.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
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 cmdlets for all troubleshooting steps, with no examples or guidance for Linux/macOS users using Bash or Azure CLI. The prerequisites and instructions assume familiarity with PowerShell, which is traditionally a Windows-centric tool, and there is no mention of equivalent CLI commands within the main content. Although Azure Cloud Shell supports PowerShell on all platforms, the lack of Bash/CLI examples creates friction for users on Linux or macOS who may prefer or expect non-PowerShell workflows.
Recommendations
  • Add equivalent Azure CLI (az) examples alongside PowerShell for all troubleshooting steps.
  • Explicitly mention that Azure Cloud Shell supports Bash and provide instructions/examples for Bash users.
  • Reorder prerequisites and instructions to present both PowerShell and CLI options equally, rather than PowerShell-first.
  • Include a note clarifying cross-platform support and linking to CLI documentation directly in relevant sections, not just in 'Related content'.
GitHub Create Pull Request
Network Watcher Connection monitor overview ...rticles/network-watcher/connection-monitor-overview.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation demonstrates mild Windows bias. Windows and PowerShell are mentioned before Linux in several places, such as in agent installation and automation tooling. References to 'Manage Network Watcher extension for Windows' precede Linux equivalents, and PowerShell is listed as a primary automation method alongside ARMClient and the Azure portal, with Azure CLI and Terraform only mentioned in a comparison table. Windows-specific terminology (e.g., 'Local Computer Trusted Certification Authorities store') appears in troubleshooting, and screenshots and examples do not show Linux-specific workflows.
Recommendations
  • Present Linux and Windows instructions side-by-side or alternate which comes first.
  • Include explicit Linux CLI and shell examples where PowerShell is shown.
  • Highlight Azure CLI and Terraform as automation options equally with PowerShell.
  • Add troubleshooting notes relevant to Linux (e.g., certificate stores, agent issues).
  • Ensure screenshots and step-by-step instructions reflect both OSes.
GitHub Create Pull Request
Network Watcher Install and upgrade Azure Monitor Agent on Azure Arc-enabled servers ...cher/connection-monitor-install-azure-monitor-agent.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation provides both Windows and Linux examples for all major commands (installation, upgrade, uninstall) using PowerShell and Azure CLI. However, in each code block, Windows examples are consistently presented before Linux examples, which may subtly signal a Windows-first approach. No critical functionality is missing for Linux users, and Linux-specific commands are present and accurate.
Recommendations
  • Alternate the order of Windows and Linux examples in code blocks, or present them side-by-side to avoid implicit prioritization.
  • Add a brief statement at the top clarifying equal support for both Windows and Linux platforms.
  • Consider grouping platform-specific instructions under neutral headings, or using tabs that do not default to Windows.
  • Ensure future updates maintain parity in detail and clarity between Windows and Linux instructions.
GitHub Create Pull Request
Network Watcher Enable or disable Azure Network Watcher ...ain/articles/network-watcher/network-watcher-create.md
Low Priority View Details →
Scanned: 2026-01-12 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 mild Windows bias by providing detailed PowerShell instructions and references, mentioning PowerShell as a primary automation tool, and occasionally suggesting PowerShell for advanced customization (such as naming resources). PowerShell is a Windows-centric tool, and its examples and references appear before or more prominently than Azure CLI equivalents. While Azure CLI is documented and supported, PowerShell is often presented as the method for advanced scenarios, which may create friction for Linux/macOS users who prefer Bash or native CLI workflows.
Recommendations
  • Ensure Azure CLI examples are equally detailed and mention customization options available via CLI, not just PowerShell.
  • Avoid suggesting PowerShell as the only way to perform advanced tasks; clarify if CLI or REST API can do the same.
  • Explicitly state that Azure CLI works natively on Linux/macOS and provide Bash shell usage notes where relevant.
  • Where PowerShell is referenced for local installation, include parallel instructions for Bash/Azure CLI on Linux/macOS.
  • Review and balance the order of examples so CLI and PowerShell are presented with equal prominence.
GitHub Create Pull Request
Network Watcher Manage packet captures ...main/articles/network-watcher/packet-capture-manage.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Minor Path Bias
Summary
The documentation provides parity between Windows and Linux in most areas, but there is a subtle Windows bias: Windows paths (C:\Capture) are shown first in examples, PowerShell is emphasized as a primary automation tool, and some instructions reference Windows tools (e.g., Storage Explorer) without mentioning Linux alternatives. Linux paths are mentioned, but often as a secondary note. The documentation does not omit Linux support, but Windows conventions are prioritized.
Recommendations
  • Alternate the order of Windows and Linux path examples, or present Linux paths first in some sections.
  • Explicitly mention Linux/macOS equivalents for tools like Storage Explorer (e.g., clarify cross-platform support, or mention azcopy, scp, etc.).
  • Where PowerShell is referenced, clarify that Azure CLI is fully supported on Linux/macOS and provide links to installation guides for those platforms.
  • Add explicit notes or examples for connecting to Linux VMs and downloading files (e.g., using scp, sftp, or azcopy).
  • In tables and parameter descriptions, present both Windows and Linux path formats side by side.
GitHub Create Pull Request
Network Watcher Connection monitor overview ...rticles/network-watcher/connection-monitor-overview.md
Low Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation demonstrates mild Windows bias. References to Windows and PowerShell appear before Linux equivalents, especially in agent installation and automation sections. There are links to both Windows and Linux agent management, but PowerShell is the only automation method explicitly mentioned in the main text, with Azure CLI and Terraform only referenced in a comparison table. No Linux-specific examples or CLI commands are shown directly in the content, and Windows terminology (e.g., 'Local Computer Trusted Certification Authorities store') is used in troubleshooting without Linux equivalents.
Recommendations
  • Provide Linux-specific examples and commands (e.g., Bash, Azure CLI) alongside PowerShell, especially in sections about agent installation, automation, and troubleshooting.
  • Ensure that references to Windows and Linux tools are presented with equal prominence and order (e.g., 'Manage Network Watcher extension for Linux and Windows').
  • Include Linux terminology and troubleshooting steps where Windows-specific terms are used (e.g., certificate stores, agent health).
  • Expand automation guidance to show both PowerShell and Azure CLI/Terraform workflows in the main documentation, not just in comparison tables.
GitHub Create Pull Request
Network Watcher Install and upgrade Azure Monitor Agent on Azure Arc-enabled servers ...cher/connection-monitor-install-azure-monitor-agent.md
Low Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation provides both Windows and Linux examples for all commands, but consistently lists Windows examples before Linux examples in every section. No commands or tools are exclusive to Windows, and Linux parity is maintained in terms of functionality and instructions.
Recommendations
  • Alternate the order of examples so that Linux examples are sometimes shown first.
  • Add a note clarifying that all commands are equally applicable to both Windows and Linux environments.
  • Consider grouping platform-specific instructions together or using neutral language when possible.
GitHub Create Pull Request
Network Watcher Enable or disable Azure Network Watcher ...ain/articles/network-watcher/network-watcher-create.md
Low Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation demonstrates mild Windows bias by consistently listing PowerShell examples and instructions before Azure CLI, and by referencing PowerShell-specific tools and installation steps. PowerShell is a Windows-centric tool, and its prominence may suggest a preference for Windows environments. However, Azure CLI instructions are present and equally detailed, and all commands are cross-platform compatible. No critical functionality is missing for Linux/macOS users.
Recommendations
  • Alternate the order of PowerShell and Azure CLI examples, or present Azure CLI first to reflect its cross-platform nature.
  • Explicitly mention that Azure CLI works natively on Linux/macOS, and provide installation links for those platforms.
  • Add a note clarifying that PowerShell Core is available on Linux/macOS, if PowerShell is referenced.
  • Avoid language that implies PowerShell is the default or preferred method unless justified by feature parity.
  • Ensure screenshots and instructions do not assume a Windows environment (e.g., avoid referencing Windows-only UI elements or shell behaviors).
GitHub Create Pull Request
Network Watcher Manage packet captures ...main/articles/network-watcher/packet-capture-manage.md
Low Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation demonstrates mild Windows bias by consistently listing Windows file paths (e.g., C:\Capture\...) before Linux equivalents (/var/captures) in examples and parameter tables. PowerShell is presented as a primary automation method, with references to Windows-centric tools (e.g., Storage Explorer) and patterns. However, Linux is acknowledged and supported in most cases, with explicit instructions and links for Linux VM extension management and CLI usage.
Recommendations
  • Alternate the order of Windows and Linux file path examples to avoid always listing Windows first.
  • Provide explicit Linux/macOS command-line examples for downloading files (e.g., using scp, curl, or az CLI on Linux/macOS), not just PowerShell or Windows paths.
  • Mention cross-platform tools (e.g., azcopy, native CLI utilities) alongside Storage Explorer.
  • Ensure that all references to local file paths and commands include both Windows and Linux/macOS formats equally.
  • Clarify that Azure CLI and PowerShell are cross-platform, and provide installation/use instructions for Linux/macOS where relevant.
GitHub Create Pull Request
← Previous Page 2 of 2 Next →