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 176-200 of 238 flagged pages
Network Watcher Install and upgrade Azure Monitor Agent on Azure Arc-enabled servers ...cher/connection-monitor-install-azure-monitor-agent.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides both Windows and Linux examples for installing, upgrading, and uninstalling the Azure Monitor Agent using PowerShell and Azure CLI. However, all command examples are given using PowerShell and Azure CLI only, with no mention of native Linux tools or shell commands (e.g., Bash). Additionally, in each example, the Windows tab is presented before the Linux tab, suggesting a Windows-first approach. There is a strong reliance on PowerShell, which is traditionally a Windows-centric tool, even for Linux instructions.
Recommendations
  • Include native Bash or shell script examples for Linux users, especially for installation and management tasks.
  • Consider presenting Linux examples before Windows examples in some sections to balance the perceived priority.
  • Clarify that PowerShell is available on Linux, or provide guidance for users who may not have PowerShell installed on their Linux systems.
  • Reference Linux package management or automation tools (e.g., Ansible, shell scripts) where appropriate.
  • Explicitly state platform requirements and alternatives for Linux users who may prefer not to use PowerShell.
GitHub Create Pull Request
Network Watcher Troubleshoot outbound connections ...cles/network-watcher/connection-troubleshoot-manage.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation consistently uses Windows-centric examples, specifically focusing on RDP (port 3389) for connectivity tests, which is a Windows-only protocol. There are no examples or guidance for Linux scenarios, such as SSH (port 22) or Linux firewall configuration. The troubleshooting steps and solutions reference RDP and Windows patterns exclusively, omitting Linux equivalents.
Recommendations
  • Add Linux-specific examples, such as testing connectivity to port 22 (SSH) between Linux VMs.
  • Include troubleshooting steps for common Linux issues, such as SSH daemon not running or Linux firewall (iptables, firewalld, ufw) blocking connections.
  • Provide guidance on configuring Linux guest firewalls to allow inbound SSH traffic.
  • Balance examples by alternating between Windows (RDP) and Linux (SSH) scenarios throughout the documentation.
  • Explicitly mention that the connectivity troubleshooting applies to both Windows and Linux VMs, and clarify protocol/port selection for each OS.
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 00:00
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 OS for virtual machines, with instructions focused on RDP and Windows-specific setup. There are no Linux VM creation steps, nor SSH or Linux-specific guidance, and all screenshots and walkthroughs assume a Windows environment. This creates a bias toward Windows users and leaves Linux administrators without direct parity in the tutorial.
Recommendations
  • Include parallel instructions for creating a Linux VM (e.g., Ubuntu), including SSH setup and login steps.
  • Provide screenshots and walkthroughs for both Windows and Linux VM scenarios.
  • Mention Linux as an option when selecting the VM image, and provide guidance for Linux authentication and connectivity.
  • Ensure troubleshooting steps (such as verifying connectivity) include Linux commands (e.g., using curl or wget instead of a browser).
  • Link to Linux-specific versions of the tutorial, or integrate them into the main page for cross-platform parity.
GitHub Create Pull Request
Network Watcher Diagnose on-premises VPN connectivity with Azure ...r/network-watcher-diagnose-on-premises-connectivity.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Missing Linux Example 🔧 Windows Tools
Summary
The documentation page focuses exclusively on using the Azure portal and does not provide any command-line examples or troubleshooting steps for Linux environments. There is no mention of Linux tools (such as Azure CLI, Bash, or Linux-native VPN diagnostics), and log file references (e.g., IKEErrors.txt) are generic but may be more familiar to Windows users. The absence of Linux-specific guidance or parity in troubleshooting steps suggests a bias toward Windows-centric workflows.
Recommendations
  • Add step-by-step instructions for using Azure CLI or PowerShell to run VPN troubleshoot, ensuring both Windows and Linux users are supported.
  • Include examples of how to download and analyze diagnostic logs using Linux tools (e.g., wget, curl, unzip, grep).
  • Mention Linux-native VPN troubleshooting tools (such as strongSwan, libreswan, or OpenVPN logs) and how to correlate Azure diagnostics with these.
  • Provide screenshots or terminal output examples from Linux environments alongside the Azure portal UI.
  • Clarify that the troubleshooting steps are platform-agnostic, or explicitly state any platform-specific requirements.
GitHub Create Pull Request
Network Watcher Visualizing Azure NSG flow logs - Power BI ...er/network-watcher-visualize-nsg-flow-logs-power-bi.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation exclusively describes using Power BI Desktop, a Windows-centric application, for visualizing Azure NSG flow logs. All setup and usage instructions assume the reader is using Windows, with no mention of Linux-compatible tools, alternatives, or cross-platform workflows. There are no examples or guidance for Linux users, nor any mention of Power BI on Linux or web-based alternatives until a brief 'Next steps' section referencing Elastic Stack.
Recommendations
  • Add explicit guidance for Linux users, such as how to access NSG flow logs and visualize them using open source or cross-platform tools (e.g., Elastic Stack, Grafana, Kibana).
  • Include Linux-specific setup instructions or examples, such as using Azure CLI, Python, or other scripting languages to download and process logs.
  • Mention Power BI web service as a possible alternative for non-Windows users, if applicable.
  • Present open source or cross-platform visualization options earlier in the document, not only in 'Next steps', to ensure parity and visibility.
  • Clarify platform requirements at the beginning and provide links to equivalent Linux workflows.
GitHub Create Pull Request
Network Watcher Manage NSG flow logs using Azure Policy ...rticles/network-watcher/nsg-flow-logs-policy-portal.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation exclusively uses the Azure Portal (GUI) for all instructions and examples, which is platform-neutral but implicitly favors Windows users due to the historical association of the Azure Portal with Windows environments. There are no command-line examples provided (such as Azure CLI, Bash, or PowerShell), and no mention of Linux-specific tools or workflows. This omission can disadvantage Linux users or those who prefer automation and scripting, as they are unable to follow along using their preferred command-line interfaces.
Recommendations
  • Add Azure CLI examples for all major steps, including policy assignment and compliance checking. Azure CLI is cross-platform and works on both Windows and Linux.
  • Include PowerShell examples for users who prefer scripting, but ensure they are presented alongside Azure CLI/Bash examples, not exclusively or first.
  • Explicitly mention that all steps can be performed using command-line tools on Linux, macOS, and Windows, and provide links to relevant documentation.
  • Add a section or callout highlighting automation options for Linux users, such as using Bash scripts with Azure CLI.
  • Ensure screenshots and instructions do not assume a Windows environment (e.g., avoid showing Windows-specific UI elements or file paths).
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
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides both Windows and Linux examples for installing, uninstalling, and upgrading the Azure Monitor Agent using PowerShell and Azure CLI. However, all examples use PowerShell as the primary scripting language, even for Linux scenarios, which is not typical for Linux administrators. Additionally, in each example section, Windows instructions are presented before Linux instructions, which may reinforce a Windows-centric perspective.
Recommendations
  • Provide native Bash or shell script examples for Linux scenarios, rather than PowerShell, as most Linux administrators use Bash.
  • Present Linux and Windows instructions in parallel or alternate their order to avoid consistently prioritizing Windows.
  • Include notes or guidance on prerequisites for using PowerShell on Linux, or recommend the most common tools for each platform.
  • Clarify that Azure CLI commands are cross-platform and show examples in native Linux shell environments (e.g., Bash) where appropriate.
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-10 00:00
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 diagnosing Linux-based virtual machines, nor is there mention of Linux-specific considerations. This creates a Windows-first bias and omits Linux parity in practical usage scenarios.
Recommendations
  • Provide parallel examples for creating and diagnosing Linux virtual machines (e.g., using Ubuntu or CentOS images) in all sections where VM creation is demonstrated.
  • Explicitly mention that the instructions apply to both Windows and Linux VMs, and highlight any differences in NSG diagnostics or Bastion connectivity for Linux.
  • Include sample Azure CLI and PowerShell commands for Linux VM creation and management, alongside the Windows examples.
  • Add screenshots and portal instructions for selecting a Linux image when creating a VM.
  • Clarify that Bastion and NSG diagnostics work with both Windows and Linux VMs, and provide troubleshooting tips for common Linux connectivity issues.
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-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation exclusively uses Windows Server as the VM OS in its main tutorial flow, with all instructions and screenshots tailored to Windows (e.g., RDP setup, Windows image selection, browser testing). There are no Linux VM creation or SSH connection examples, and Linux is not mentioned in the main steps. While alternative CLI and PowerShell tutorials are linked, the portal-based instructions are Windows-centric.
Recommendations
  • Add parallel instructions and screenshots for creating a Linux VM (e.g., Ubuntu) alongside the Windows VM, including SSH connection steps.
  • Provide examples for testing connectivity from a Linux VM (e.g., using curl or wget in the terminal) in addition to browser-based testing.
  • Explicitly mention that the tutorial applies to both Windows and Linux VMs, and clarify any OS-specific differences in steps.
  • Include guidance for opening SSH ports (22) for Linux VMs in the networking setup, similar to the RDP instructions for Windows.
  • Balance screenshots and walkthroughs to show both Windows and Linux VM experiences in the Azure portal.
GitHub Create Pull Request
Network Watcher Manage NSG flow logs using Azure Policy ...rticles/network-watcher/nsg-flow-logs-policy-portal.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation exclusively uses the Azure portal UI for all instructions, with screenshots and step-by-step guidance. There are no command-line examples (such as Azure CLI, PowerShell, or Bash), nor any mention of Linux-specific tools or workflows. This approach implicitly favors Windows users, as the Azure portal UI is most commonly accessed from Windows environments and does not address cross-platform automation or scripting needs. Linux users, who often prefer CLI or automation via scripts, are not provided with equivalent instructions.
Recommendations
  • Add Azure CLI examples for auditing and deploying NSG flow logs via Azure Policy, as Azure CLI is cross-platform and widely used on Linux.
  • Include PowerShell examples if desired, but ensure CLI examples are presented first or equally.
  • Mention automation options, such as using ARM templates or Bicep, and provide links or examples for deploying policies via these methods.
  • Clarify that all steps can be performed from any OS via the portal, but highlight CLI/script options for Linux and macOS users.
  • Add a section comparing portal, CLI, and script-based approaches, with pros and cons for each.
GitHub Create Pull Request
Network Watcher https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/network-watcher/connection-monitor-install-azure-monitor-agent.md ...cher/connection-monitor-install-azure-monitor-agent.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides both Windows and Linux examples for installing, upgrading, and uninstalling the Azure Monitor Agent using PowerShell and Azure CLI. However, all examples use PowerShell as the primary scripting language, which is less common on Linux systems. Additionally, in each example section, Windows commands are presented before Linux commands, indicating a 'Windows-first' ordering. There is no mention of native Linux tools (such as Bash or shell scripting), nor are Linux-specific considerations discussed.
Recommendations
  • Provide native Bash/shell script examples for Linux users alongside PowerShell and Azure CLI.
  • Alternate the order of Windows and Linux examples or present them side-by-side to avoid implicit prioritization.
  • Include notes on Linux-specific prerequisites, troubleshooting, or differences in agent behavior.
  • Clarify that PowerShell is available on Linux, but many Linux administrators may prefer Bash or other native tools.
  • Add links to Linux-focused documentation or community resources.
GitHub Create Pull Request
Network Watcher https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/network-watcher/diagnose-vm-network-routing-problem.md ...network-watcher/diagnose-vm-network-routing-problem.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
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 only demonstrates connecting to the VM via RDP, with no mention of Linux VM options or SSH access. All step-by-step instructions assume a Windows environment, and there are no Linux-specific examples or parity in the main flow.
Recommendations
  • Provide parallel instructions for creating a Linux VM (e.g., Ubuntu) alongside the Windows VM, including appropriate image selection and authentication setup.
  • Include SSH access instructions for Linux VMs, such as opening port 22 and connecting via SSH, in addition to RDP for Windows.
  • When demonstrating network connectivity tests, show examples using a Linux VM (e.g., using curl or wget to test internet access) as well as a Windows VM.
  • Explicitly mention that the tutorial steps apply to both Windows and Linux VMs, and clarify any differences in portal UI or required settings.
  • Where possible, alternate or combine examples for Windows and Linux to ensure equal visibility and guidance for both platforms.
GitHub Create Pull Request
Network Watcher https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/network-watcher/nsg-flow-logs-policy-portal.md ...rticles/network-watcher/nsg-flow-logs-policy-portal.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation exclusively uses the Azure portal UI for all instructions and screenshots, which is platform-agnostic but typically most accessible from Windows environments. There are no command-line examples (such as Azure CLI, PowerShell, or Bash), nor are there references to Linux-native tools or workflows. This omission may disadvantage Linux users who prefer or require CLI-based automation or management, and it implicitly prioritizes GUI workflows commonly associated with Windows.
Recommendations
  • Add Azure CLI examples for policy assignment, auditing, and remediation. The Azure CLI is cross-platform and works natively on Linux, macOS, and Windows.
  • If relevant, include Bash scripting examples for automating NSG flow log management.
  • Provide PowerShell examples only alongside Azure CLI/Bash, not as the sole automation option.
  • Explicitly mention that all steps can be performed from any OS via the portal, but highlight CLI alternatives for Linux users.
  • Link to documentation on using Azure Policy via CLI and ARM templates, emphasizing cross-platform compatibility.
GitHub Create Pull Request
Network Watcher https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/network-watcher/diagnose-network-security-rules.md ...les/network-watcher/diagnose-network-security-rules.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
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 default and only example for virtual machine creation, both in the Azure Portal and CLI/PowerShell instructions. There are no examples or instructions for creating a Linux VM, nor any mention of Linux-specific considerations, images, or administrator account setup. This presents a Windows-first bias and omits Linux parity in practical usage scenarios.
Recommendations
  • Add parallel instructions and examples for creating a Linux virtual machine (e.g., using Ubuntu or CentOS images) in all sections where VM creation is demonstrated.
  • In the Portal instructions, include a step for selecting a Linux image and configuring SSH authentication, alongside the Windows example.
  • For PowerShell and Azure CLI, provide sample commands for creating a Linux VM, including appropriate image references and authentication methods (e.g., SSH keys).
  • Explicitly mention that the NSG diagnostics process applies equally to Linux VMs, and highlight any differences in network access or security group configuration relevant to Linux.
  • Ensure that administrator account setup instructions cover both Windows (username/password) and Linux (username/SSH key) scenarios.
GitHub Create Pull Request
Network Watcher https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/network-watcher/connection-monitor-install-azure-monitor-agent.md ...cher/connection-monitor-install-azure-monitor-agent.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides both Windows and Linux examples for installing, upgrading, and uninstalling the Azure Monitor Agent using PowerShell and Azure CLI. However, all examples use PowerShell as the primary scripting language, which is less common on Linux systems. Additionally, in each example section, Windows commands are presented before Linux commands, indicating a 'Windows-first' ordering. There are no native Bash or shell script examples for Linux users, and the use of PowerShell on Linux may not align with typical Linux administrator workflows.
Recommendations
  • Add native Bash/shell script examples for Linux users alongside PowerShell and Azure CLI.
  • Present Windows and Linux examples in parallel or alternate the order to avoid implicit prioritization.
  • Clarify that PowerShell is available on Linux, but provide guidance for users who prefer native Linux tools.
  • Ensure that all instructions and tooling references are equally accessible and familiar to both Windows and Linux administrators.
GitHub Create Pull Request
Network Watcher https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/network-watcher/azure-monitor-agent-with-connection-monitor.md ...watcher/azure-monitor-agent-with-connection-monitor.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation describes agent installation and configuration for monitoring network connectivity using Azure Monitor agent, but does not provide any OS-specific examples, commands, or instructions. While it mentions both Windows and Linux machines can be managed, there are no explicit Linux examples, and references to Windows (such as 'Windows events') appear before Linux equivalents (such as 'Syslog events'), suggesting a subtle Windows-first bias. There are no PowerShell-heavy sections or exclusive references to Windows tools, but the lack of parity in examples and ordering indicates a mild bias.
Recommendations
  • Add explicit installation and configuration examples for both Windows and Linux platforms, including command-line instructions (e.g., PowerShell for Windows, Bash for Linux).
  • When mentioning event collection, present Windows and Linux options together or alternate their order to avoid Windows-first bias.
  • Include troubleshooting steps and agent management guidance for Linux systems, such as common log file locations and service management commands.
  • Ensure screenshots and UI references are relevant for both Windows and Linux environments where applicable.
GitHub Create Pull Request
Network Watcher https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/network-watcher/diagnose-network-security-rules.md ...les/network-watcher/diagnose-network-security-rules.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation demonstrates a Windows bias by exclusively using Windows Server images for all virtual machine creation examples in the Portal, PowerShell, and Azure CLI sections. There are no Linux VM examples or instructions, and the VM creation steps (including image selection and CLI parameters) are tailored to Windows. This could mislead users into thinking NSG diagnostics or Bastion scenarios are only relevant for Windows VMs, or that Linux is unsupported.
Recommendations
  • Add parallel examples for creating and diagnosing Linux virtual machines (e.g., Ubuntu, CentOS) in all sections (Portal, PowerShell, Azure CLI).
  • In the Portal instructions, show how to select a Linux image and set SSH authentication, not just Windows credentials.
  • In CLI and PowerShell, provide commands for Linux VM creation (e.g., --image 'UbuntuLTS', --admin-username, --authentication-type ssh).
  • Clarify in the introduction and throughout that NSG diagnostics and Bastion work for both Windows and Linux VMs.
  • Where screenshots are shown, include Linux VM configuration screens as well as Windows.
GitHub Create Pull Request
Network Watcher https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/network-watcher/diagnose-vm-network-routing-problem.md ...network-watcher/diagnose-vm-network-routing-problem.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The tutorial exclusively demonstrates VM creation and connectivity using Windows Server as the guest OS, with instructions focused on RDP and Windows-specific workflows. There are no examples or guidance for deploying or connecting to Linux-based VMs, nor are SSH or Linux authentication methods mentioned. This presents a Windows-first and missing-Linux-example bias.
Recommendations
  • Provide parallel instructions for creating a Linux VM (e.g., Ubuntu), including appropriate image selection and authentication (SSH key setup).
  • Include steps for connecting to the Linux VM using SSH, both from the Azure portal and from a local terminal.
  • Demonstrate network connectivity testing from a Linux VM (e.g., using curl or wget to access www.bing.com).
  • Ensure that screenshots and command examples reflect both Windows and Linux scenarios where applicable.
  • Explicitly mention that the tutorial applies to both Windows and Linux VMs, and link to relevant OS-specific guidance.
GitHub Create Pull Request
Network Watcher https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/network-watcher/network-watcher-diagnose-on-premises-connectivity.md ...r/network-watcher-diagnose-on-premises-connectivity.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Missing Linux Example 🔧 Windows Tools
Summary
The documentation page focuses exclusively on using the Azure portal GUI for VPN troubleshooting and references log files (IKEErrors.txt, IkeLogs.txt) that are typically generated by Windows-based gateways. There are no examples or instructions for Linux-based VPN devices, CLI usage, or Linux troubleshooting patterns. The validated VPN devices list is mentioned, but no Linux-specific guidance or parity is provided.
Recommendations
  • Add troubleshooting steps and examples for Linux-based VPN devices, including common log file locations and formats (e.g., strongSwan, libreswan).
  • Include CLI-based instructions using Azure CLI and Bash, not just portal GUI steps.
  • Reference Linux tools and commands for analyzing VPN connectivity (e.g., tcpdump, ipsec status, journalctl).
  • Provide sample error messages and resolutions for popular Linux VPN solutions.
  • Ensure that log file references include both Windows and Linux gateway scenarios.
GitHub Create Pull Request
Network Watcher https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/network-watcher/nsg-flow-logs-policy-portal.md ...rticles/network-watcher/nsg-flow-logs-policy-portal.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation exclusively demonstrates management of NSG flow logs using the Azure Portal GUI, which is platform-agnostic but implicitly Windows-first due to the historical association of the Azure Portal with Windows environments. There are no command-line examples (such as Azure CLI, PowerShell, or Bash), and no mention of Linux-specific tools or workflows. This omission may disadvantage Linux users who prefer or require automation or command-line management.
Recommendations
  • Add Azure CLI examples for auditing and deploying NSG flow logs via Azure Policy, as Azure CLI is cross-platform and widely used on Linux.
  • Include PowerShell examples if desired, but ensure Azure CLI or Bash scripts are presented first or alongside them.
  • Mention that all steps can be performed from any OS using the Azure Portal, but highlight command-line alternatives for Linux users.
  • Provide links to relevant Azure CLI documentation for policy assignment and management.
  • Consider adding ARM template deployment steps using CLI commands, not just referencing the ARM template documentation.
GitHub Create Pull Request
Network Watcher https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/network-watcher/connection-monitor-install-azure-monitor-agent.md ...cher/connection-monitor-install-azure-monitor-agent.md
Medium Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation consistently presents PowerShell-based workflows for both Windows and Linux, rather than using native Linux shell commands for Linux scenarios. Additionally, in all tabbed code blocks, Windows examples are listed before Linux, reinforcing a Windows-first perspective. While Linux is not omitted, there is a lack of parity in using platform-appropriate tools and conventions for Linux users.
Recommendations
  • Provide native Bash/shell command examples for Linux scenarios, especially when using the Azure CLI, rather than only PowerShell.
  • When presenting tabbed code blocks, alternate the order of Windows and Linux examples or use a neutral default (e.g., CLI first, then platform-specific).
  • Where possible, use platform-appropriate scripting languages and conventions (e.g., Bash for Linux, PowerShell for Windows) to improve clarity and accessibility for Linux users.
  • Explicitly mention that PowerShell Core is required for Linux PowerShell examples, or provide equivalent Bash commands.
  • Review and update documentation templates to ensure Linux parity in both tooling and instructional flow.
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
Medium Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation demonstrates a Windows bias primarily by focusing on RDP (port 3389) as the default connectivity scenario throughout all examples, which is specific to Windows virtual machines. There are no equivalent examples for Linux-based protocols (such as SSH on port 22), and all troubleshooting scenarios and solutions reference RDP and Windows patterns. While the documentation does mention Linux in the context of installing the Network Watcher agent, all connectivity tests and diagnostic flows are centered around Windows use cases, with no Linux-specific examples or parity.
Recommendations
  • Include Linux-centric connectivity scenarios, such as testing SSH (port 22) between virtual machines, alongside or instead of RDP examples.
  • Provide troubleshooting examples and solutions relevant to Linux VMs (e.g., checking SSH daemon status, Linux firewall rules).
  • Balance the documentation by alternating or combining Windows and Linux examples in each section, making it clear that both platforms are supported.
  • Explicitly mention that the procedures apply to both Windows and Linux VMs, and clarify any platform-specific differences where relevant.
  • Add sample outputs and error cases for Linux scenarios, such as failed SSH connections due to iptables or firewalld rules.
GitHub Create Pull Request
Network Watcher https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/network-watcher/diagnose-vm-network-routing-problem.md ...network-watcher/diagnose-vm-network-routing-problem.md
Medium Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation demonstrates a Windows bias by exclusively using Windows Server as the VM image in the main tutorial flow, providing only RDP (Windows Remote Desktop) instructions for connecting to the VM, and omitting any Linux-based examples or SSH connection steps. There are no instructions for creating or connecting to a Linux VM, nor are there references to Linux tools or patterns. While the page mentions that CLI and PowerShell tutorials are available elsewhere, this portal-based tutorial is Windows-centric.
Recommendations
  • Provide parallel instructions for creating a Linux VM (e.g., using Ubuntu or another common distribution) alongside the Windows VM example.
  • Include SSH connection steps for Linux VMs, in addition to RDP for Windows.
  • Show how to verify connectivity from a Linux VM (e.g., using curl or wget in a terminal) as an alternative to opening a web browser on Windows.
  • When listing VM image selection, mention both Windows and Linux options, or provide a choice.
  • Where possible, use neutral language and examples that apply to both OS types, or clearly indicate differences.
  • Add screenshots or command examples from Linux environments where relevant.
GitHub Create Pull Request
Network Watcher https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/network-watcher/diagnose-network-security-rules.md ...les/network-watcher/diagnose-network-security-rules.md
Medium Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation demonstrates a Windows bias by exclusively using Windows Server images for virtual machine creation in all examples (Portal, PowerShell, Azure CLI), and by not providing any Linux-based VM examples or instructions. All command-line and portal steps assume the use of Windows VMs, with no mention of Linux images, usernames, or SSH key authentication. This may lead Linux users to feel unsupported or unclear about how to adapt the instructions for their environment.
Recommendations
  • Provide parallel Linux-based examples for creating virtual machines, including using popular Linux images (e.g., Ubuntu LTS) in both Portal and CLI/PowerShell instructions.
  • Include steps for Linux-specific authentication (e.g., SSH key generation and usage) alongside Windows password authentication.
  • When showing CLI/PowerShell commands, demonstrate both Windows and Linux image parameters, and clarify any differences in required flags or options.
  • In the Portal instructions, show how to select a Linux image and configure SSH authentication.
  • Add a note or section addressing differences in VM management or diagnostics for Linux versus Windows, if any.
  • Ensure that all code samples and screenshots are inclusive of both Windows and Linux scenarios, or provide tabs for each.
GitHub Create Pull Request
Network Watcher https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/network-watcher/vm-network-troubleshooter.md .../articles/network-watcher/vm-network-troubleshooter.md
Medium Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation lists RDP (port 3389) as a primary example of a commonly checked port, which is specific to Windows VMs, while not mentioning SSH (port 22), the standard for Linux VMs. There are no Linux-specific examples or references, and the workflow is described in a way that centers Windows use cases.
Recommendations
  • Include SSH (port 22) in the list of commonly checked ports to represent Linux VM scenarios.
  • Explicitly mention that the troubleshooter can be used for both Windows and Linux VMs.
  • Provide examples or screenshots that show troubleshooting for both RDP (Windows) and SSH (Linux) ports.
  • Clarify in the documentation that the tool is not limited to Windows VMs and can help diagnose connectivity issues for Linux VMs as well.
GitHub Create Pull Request
← Previous Page 8 of 10 Next →