Network Watcher

60
Total Pages
31
Linux-Friendly Pages
29
Pages with Bias
48.3%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues (67)

https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/network-watcher/nsg-flow-logs-template.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Missing Linux Example Windows Tools
Summary:
The documentation page demonstrates a strong Windows bias by exclusively providing Azure PowerShell commands for deploying the ARM template, referencing Windows-style file paths (e.g., C:\MyTemplates\azuredeploy.json), and omitting any CLI or Bash/Linux-based deployment instructions. There are no examples or guidance for Linux or cross-platform users, and Windows tools and patterns are presented as the default.
Recommendations:
  • Add equivalent Azure CLI (az) command examples for deploying the ARM template, with Linux/macOS-friendly file paths (e.g., ~/MyTemplates/azuredeploy.json).
  • Explicitly mention that both PowerShell and Azure CLI can be used, and provide parallel instructions for each.
  • Avoid using Windows-specific file paths in examples; use generic or cross-platform paths, or provide both Windows and Linux/macOS variants.
  • Include a note or section for Linux/macOS users, highlighting any differences or considerations.
  • Ensure that portal-based instructions are clearly platform-agnostic.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/network-watcher/nsg-flow-logs-overview.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Windows First Powershell Heavy Missing Linux Example
Summary:
The documentation page demonstrates a Windows bias primarily through the exclusive use of PowerShell (Windows-centric) for configuration examples (e.g., setting FlowTimeoutInMinutes), and by referencing PowerShell-based guides before or instead of cross-platform or Linux-native alternatives. There are no CLI (az), Bash, or Linux-specific instructions or examples provided for key tasks, such as configuring NSG flow logs or setting properties, which may disadvantage Linux users.
Recommendations:
  • Provide equivalent Azure CLI (az) and/or Bash examples alongside PowerShell for all configuration tasks, especially for setting NSG properties like FlowTimeoutInMinutes.
  • When listing guides or instructions, present cross-platform (CLI, REST API, Portal) options before or alongside Windows/PowerShell-specific ones.
  • Explicitly mention that all features and configuration steps are available and supported on Linux, and link to relevant Linux or cross-platform documentation.
  • Include troubleshooting and usage examples that are relevant to Linux users, such as using jq or grep to parse logs, or automating tasks with Bash scripts.
  • Ensure that visualization and export tool instructions are not biased toward Windows-only tools (e.g., Power BI), and highlight open-source or cross-platform alternatives equally.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/network-watcher/migrate-to-connection-monitor-from-network-performance-monitor.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Windows First Windows Tools Missing Linux Example
Summary:
The documentation demonstrates a Windows bias by referencing Windows-specific tools and extensions (such as the Network Watcher extension for Windows), mentioning Windows/PowerShell automation before Linux equivalents, and lacking explicit Linux-focused migration instructions or examples. While Linux is mentioned in compatibility tables, there are no detailed Linux agent installation or migration steps, and references to documentation or extensions are Windows-centric.
Recommendations:
  • Include explicit Linux migration steps and examples, such as how to install and configure the Network Watcher extension on Linux VMs.
  • When referencing automation (PowerShell, Azure CLI, Terraform), provide Linux/Unix shell examples alongside or before Windows/PowerShell examples.
  • Link to both Windows and Linux agent documentation where relevant, not just to Windows-specific pages.
  • Clarify any differences in agent behavior or prerequisites between Windows and Linux platforms.
  • Add troubleshooting steps and error messages specific to Linux environments, if applicable.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/network-watcher/connection-monitor-connected-machine-agent.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Windows First Powershell Heavy Windows Tools Missing Linux Example
Summary:
The documentation demonstrates a Windows bias by consistently presenting Windows instructions and tooling (such as PowerShell and Windows Admin Center) before Linux equivalents, providing more detailed steps for Windows, and emphasizing Windows-specific tools. Linux instructions are present but less detailed and lack parity in tooling examples (e.g., no Bash/CLI automation equivalent to PowerShell or Windows Admin Center).
Recommendations:
  • Alternate the order of Windows and Linux instructions, or present them side-by-side to avoid always listing Windows first.
  • Provide Linux-specific automation examples, such as using Bash scripts or Azure CLI, in parity with PowerShell examples.
  • Include references to Linux-native management tools or workflows where Windows Admin Center is mentioned for Windows.
  • Ensure that all steps and details provided for Windows are also present for Linux, including troubleshooting and verification steps.
  • Where PowerShell cmdlets are highlighted, also mention equivalent Azure CLI or Bash commands for Linux environments.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/network-watcher/diagnose-vm-network-traffic-filtering-problem-powershell.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows Tools Missing Linux Example Windows First
Summary:
The documentation is heavily focused on Azure PowerShell, with all examples and instructions using PowerShell cmdlets. There are no CLI, Bash, or Linux-native command examples provided, and the prerequisites and workflow assume the use of PowerShell (either locally or in Cloud Shell). This creates a Windows-centric experience, even though the VM created is Linux-based.
Recommendations:
  • Provide equivalent Azure CLI (az) command examples alongside or in place of PowerShell examples, as Azure CLI is cross-platform and commonly used on Linux and macOS.
  • Explicitly mention that Azure Cloud Shell supports both Bash and PowerShell, and show how to select Bash.
  • Include Linux/Bash shell command snippets for each step, especially for users who prefer or require a non-Windows workflow.
  • Clarify that all steps can be performed from any OS using Azure CLI, not just from a Windows/PowerShell environment.
  • Where possible, link to documentation for both PowerShell and CLI approaches, and avoid implying PowerShell is the default or only method.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/network-watcher/effective-security-rules-overview.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Missing Linux Example
Summary:
The documentation page does not provide any OS-specific examples, commands, or tooling references. However, it also does not mention or provide parity for Linux environments, such as CLI commands or troubleshooting steps that might be relevant for Linux users. The focus is entirely on the Azure portal UI, with no examples for either Windows or Linux command-line environments.
Recommendations:
  • Add examples using Azure CLI and/or Azure PowerShell to retrieve effective security rules, ensuring both Windows and Linux users are supported.
  • Explicitly mention that the Azure CLI commands work cross-platform (Windows, Linux, macOS).
  • Provide sample scripts or command lines for common Linux shells (e.g., Bash) to download or process the CSV output.
  • If relevant, include troubleshooting steps or references for both Windows and Linux VM network interfaces.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/network-watcher/vpn-troubleshoot-powershell.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Missing Linux Example
Summary:
The documentation is heavily focused on PowerShell, providing only PowerShell-based examples and instructions for troubleshooting VPN gateways and connections. There are no equivalent examples using the Azure CLI, Bash, or other Linux-friendly tools within this page. The prerequisites and workflow assume the use of PowerShell (either in Cloud Shell or locally), which is more familiar to Windows users. While there is a link to a separate Azure CLI-based troubleshooting guide in the 'Related content' section, this page itself does not provide parity for Linux users or those preferring CLI/Bash workflows.
Recommendations:
  • Add parallel Azure CLI (az) command examples alongside PowerShell examples for all troubleshooting steps.
  • Include explicit instructions for running these commands in Bash (Cloud Shell or local Linux/macOS terminal).
  • Update prerequisites to mention both PowerShell and Azure CLI as supported options, with links to installation guides for each.
  • Consider using tabbed code blocks (e.g., 'PowerShell' and 'Azure CLI') to allow users to select their preferred environment.
  • Reference the Azure CLI troubleshooting page more prominently at the start of the document, and clarify that all steps can be performed with either tool.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/network-watcher/connection-monitor-overview.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Windows First Powershell Heavy Missing Linux Example
Summary:
The documentation demonstrates subtle Windows bias. While both Windows and Linux are mentioned as supported platforms, Windows is often referenced first (e.g., 'Manage Network Watcher extension for Windows' before Linux), and PowerShell is highlighted as a primary automation method. There are no explicit Linux CLI or shell command examples, and Linux-specific tooling or workflows are not equally emphasized. The documentation lacks parity in example commands or guidance for Linux users, especially for automation and agent management.
Recommendations:
  • Ensure that references to Windows and Linux are presented with equal prominence, alternating order or listing both together (e.g., 'Manage Network Watcher extension for Windows or Linux').
  • Provide equivalent example commands for both Windows (PowerShell) and Linux (Bash/Azure CLI) wherever automation or agent installation is discussed.
  • Include Linux-specific troubleshooting steps or notes where relevant, not just generic or Windows-centric guidance.
  • Highlight Azure CLI usage alongside PowerShell for cross-platform automation, and provide links to both sets of documentation.
  • Where screenshots or UI steps are shown, clarify any OS-specific differences or provide Linux-centric visuals if applicable.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/network-watcher/vpn-troubleshoot-overview.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows Tools Windows First Missing Linux Example
Summary:
The documentation page exhibits several signs of Windows bias. While it mentions that VPN troubleshoot can be called via Azure portal, PowerShell, CLI, or REST API, the only specific example of command-line tooling is PowerShell (in the 'Considerations' section). There are no Linux-specific examples or instructions. Several log file examples and error messages reference Windows-specific error codes and terminology (e.g., 'Windows error 13801', 'Windows error 13843'). The log file paths and formats (e.g., C:\Resources\...) are Windows-centric. There is no mention of Linux tools or workflows for accessing or analyzing logs, nor are there CLI examples tailored for Linux environments.
Recommendations:
  • Provide explicit Linux/Azure CLI examples alongside or before PowerShell examples, especially in sections discussing command-line usage.
  • Reference Linux-compatible tools (e.g., azcopy, Azure CLI, or standard Linux utilities) for downloading and analyzing logs from Azure Storage.
  • When showing log file paths, use platform-agnostic or Linux-style paths as well, or clarify that paths may differ on Linux.
  • If error codes are Windows-specific, add explanations or mappings for Linux users, or clarify how similar issues would appear on non-Windows systems.
  • Ensure that troubleshooting workflows and recommendations are equally accessible and actionable for Linux administrators.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/network-watcher/nsg-flow-logs-migrate.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Missing Linux Example Windows Tools
Summary:
The documentation page demonstrates a strong bias toward Windows and PowerShell environments. All scripting and automation instructions are provided exclusively using PowerShell (.ps1 script), with no mention or example of Bash, Azure CLI, or Linux-native alternatives. The prerequisites and instructions assume the use of PowerShell, and there are no Linux-specific considerations or examples, despite PowerShell Core being cross-platform. There is also no guidance for users who may prefer or require Bash scripting or Azure CLI for automation.
Recommendations:
  • Provide equivalent migration instructions and scripts using Azure CLI and/or Bash, ensuring Linux users have a first-class experience.
  • Explicitly mention that PowerShell 7 is cross-platform and provide Linux/macOS installation and usage notes, including any known issues or differences.
  • Offer downloadable migration scripts in both PowerShell (.ps1) and Bash (.sh) formats, or provide guidance on how to adapt the process for non-PowerShell environments.
  • Include Linux/macOS-specific screenshots or terminal examples where relevant.
  • Clarify any limitations or differences in running the migration process on Linux/macOS versus Windows.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/network-watcher/diagnose-vm-network-routing-problem-powershell.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows Tools Missing Linux Example Windows First
Summary:
The documentation exclusively uses Azure PowerShell cmdlets and Windows-oriented tooling (PowerShell, Azure Cloud Shell with PowerShell), with no mention or examples for Linux users (such as Azure CLI or Bash). All code samples and instructions are PowerShell-based, and there is no guidance for users who may prefer or require Linux-native tools or scripting environments.
Recommendations:
  • Add equivalent Azure CLI (az) command examples for each PowerShell cmdlet shown, and present them alongside or before the PowerShell examples.
  • Explicitly mention that Azure Cloud Shell supports both Bash and PowerShell, and provide instructions for both environments.
  • Include guidance or links for Linux/macOS users on how to install and use Azure CLI, and how to perform the same diagnostics using CLI commands.
  • Where possible, use neutral language that does not assume the user is on Windows or using PowerShell.
  • Consider restructuring the article to present cross-platform solutions first (e.g., Azure CLI), or provide parallel sections for PowerShell and CLI/Bash.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/network-watcher/diagnose-vm-network-routing-problem-powershell.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Missing Linux Example Windows Tools
Summary:
The documentation page exclusively uses Azure PowerShell cmdlets and PowerShell scripting throughout all examples and instructions. There are no references to Azure CLI, Bash, or Linux-native tools. The prerequisites and instructions assume the use of PowerShell (either in Azure Cloud Shell or locally), and all code samples are PowerShell-specific. This creates a strong Windows/PowerShell bias and does not address users who prefer or require Linux or cross-platform command-line tools.
Recommendations:
  • Provide equivalent Azure CLI (az) command examples alongside PowerShell cmdlets for each step (resource group creation, VM creation, Network Watcher operations, cleanup, etc.).
  • Explicitly mention that Azure Cloud Shell supports both Bash and PowerShell, and show how to select the Bash environment.
  • Include Bash/Linux shell script examples where appropriate, especially for users who may be working from Linux or macOS environments.
  • Add a section or callout explaining the parity between PowerShell and Azure CLI, and link to relevant Azure CLI documentation.
  • Ensure that references to installing tools locally include both Azure PowerShell and Azure CLI, with links and brief instructions for each.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/network-watcher/effective-security-rules-overview.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Missing Linux Example
Summary:
The documentation page does not provide any platform-specific examples or instructions, but it also omits any mention of how to access or interact with effective security rules from Linux or cross-platform command-line tools. The only interaction described is through the Azure Portal GUI, with no CLI (PowerShell, Azure CLI, Bash, etc.) examples for either Windows or Linux. However, the absence of Linux-specific or cross-platform command-line guidance may disadvantage Linux users who typically rely on CLI tools.
Recommendations:
  • Add examples for accessing effective security rules using Azure CLI, which is cross-platform and commonly used on Linux.
  • If PowerShell examples are added in the future, ensure equivalent Azure CLI or Bash examples are provided.
  • Include a section on how to download or view effective security rules from the command line on both Windows and Linux.
  • Mention any platform-specific considerations if there are differences in experience or tooling between Windows and Linux.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/network-watcher/vpn-troubleshoot-powershell.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Missing Linux Example Windows Tools
Summary:
The documentation page exclusively uses PowerShell cmdlets and Azure PowerShell modules for all examples and instructions, with no mention or examples of Linux-native tools, Bash, or Azure CLI commands within the main content. The prerequisites and workflow are centered around PowerShell and Azure Cloud Shell (which defaults to PowerShell), and Windows-centric tools like Storage Explorer are referenced. Although a related link to an Azure CLI-based guide is provided at the end, the main troubleshooting workflow is presented only in PowerShell, implicitly prioritizing Windows environments and omitting Linux parity.
Recommendations:
  • Provide equivalent Azure CLI (az) command examples alongside PowerShell for all troubleshooting steps.
  • Explicitly mention that Azure Cloud Shell supports both Bash and PowerShell, and show how to select Bash.
  • Include Linux/Bash-specific instructions for setting up prerequisites and running troubleshooting commands.
  • Reference cross-platform tools for accessing storage account logs (e.g., az storage blob download, or third-party Linux tools) in addition to Storage Explorer.
  • Consider restructuring the documentation to present both PowerShell and CLI/Bash workflows in parallel tabs or sections, ensuring equal visibility.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/network-watcher/ip-flow-verify-overview.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Missing Linux Example
Summary:
The documentation page does not display overt Windows bias in terms of language, tools, or examples. However, it lacks any platform-specific usage examples, including both Windows (e.g., PowerShell) and Linux (e.g., Bash/CLI). This absence means Linux users do not see parity in example coverage, which could be improved by including explicit Linux command-line usage or references.
Recommendations:
  • Add explicit examples showing how to use IP flow verify from both Windows (PowerShell/Azure CLI) and Linux (Bash/Azure CLI) environments.
  • Include screenshots or command snippets demonstrating the process on both Windows and Linux VMs.
  • Mention any platform-specific considerations, such as differences in interpreting results or prerequisites for Linux vs. Windows VMs.
  • Ensure that any referenced tools (e.g., Azure CLI, PowerShell) are introduced in a cross-platform manner, with equal prominence for Linux and Windows usage.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/network-watcher/connection-monitor-install-azure-monitor-agent.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/network-watcher/connection-monitor-connected-machine-agent.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Windows First Powershell Heavy Windows Tools
Summary:
The documentation demonstrates a Windows-first bias by presenting Windows installation steps and tools (such as PowerShell and Windows Admin Center) before their Linux equivalents. PowerShell is highlighted as an automation method, but there is no mention of equivalent Linux-native automation (e.g., Bash scripting or Ansible). Additionally, Windows-specific tools like Windows Admin Center are discussed, while no comparable Linux management tools are referenced.
Recommendations:
  • Alternate the order of Windows and Linux instructions, or present them in parallel tabs to avoid prioritizing one platform.
  • Include Linux-native automation options, such as Bash scripts or Ansible playbooks, alongside PowerShell examples.
  • Reference Linux management tools (e.g., Cockpit, Ansible, or CLI-based workflows) where Windows Admin Center is mentioned, or clarify that such tools are not required for Linux.
  • Ensure that all steps and automation options are equally detailed for both Windows and Linux environments.
  • Explicitly state platform parity goals and direct users to additional Linux resources where appropriate.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/network-watcher/connection-monitor-overview.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Windows First Powershell Heavy Windows Tools Missing Linux Example
Summary:
The documentation demonstrates a mild Windows bias. References to Windows-specific tools (e.g., PowerShell) and documentation links for Windows appear before Linux equivalents. There is a tendency to mention Windows or PowerShell first in agent installation and automation contexts, and Linux-specific instructions or examples are either secondary or missing. The documentation also references 'Manage Network Watcher extension for Windows' before Linux, and automation examples are only linked for PowerShell, with no explicit Linux shell/CLI examples provided.
Recommendations:
  • Ensure that Linux and Windows instructions are presented with equal prominence, ideally side-by-side or in parallel sections.
  • When linking to agent installation guides, list both Windows and Linux links together, or alternate which is mentioned first.
  • Provide explicit Linux CLI (bash/az CLI) examples wherever PowerShell examples are given, especially in sections about automation and resource creation.
  • Include references to Linux-native tools and workflows (e.g., bash scripts, systemd, Linux troubleshooting steps) where relevant.
  • Audit for any missing Linux-specific troubleshooting or diagnostic guidance and add parity where needed.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/network-watcher/vnet-flow-logs-policy.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Missing Linux Example
Summary:
The documentation exclusively uses the Azure Portal (web UI) for all instructions and examples, without providing any command-line alternatives. There are no references to Windows-specific tools or PowerShell, but there is also a complete absence of CLI-based instructions (such as Azure CLI or Azure PowerShell), which are important for Linux and cross-platform users. This omission results in a subtle bias, as Linux users often prefer or require CLI-based workflows.
Recommendations:
  • Add equivalent Azure CLI instructions for all policy assignment and compliance-checking steps, ensuring that Linux and cross-platform users can follow along without relying on the Azure Portal.
  • Where relevant, provide both Azure CLI and Azure PowerShell examples, and present Azure CLI (which is cross-platform) before PowerShell (which is more Windows-centric, though available on Linux).
  • Include notes or links to documentation on how to perform these tasks via automation or scripting, which is common in Linux environments.
  • Explicitly state that all tasks can be performed via CLI and provide references or code snippets to support this.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/network-watcher/connection-troubleshoot-manage.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/network-watcher/diagnose-vm-network-routing-problem.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/network-watcher/diagnose-network-security-rules.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/network-watcher/diagnose-vm-network-traffic-filtering-problem-powershell.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Missing Linux Example Windows Tools
Summary:
The documentation is heavily focused on Azure PowerShell, with all examples and instructions using PowerShell cmdlets. There are no examples or guidance for using Azure CLI, Bash, or other Linux-native tools, despite mentioning the creation of a Linux VM. The prerequisites and workflow assume familiarity with PowerShell, which is more common on Windows, and do not provide parity for Linux users.
Recommendations:
  • Provide equivalent Azure CLI (az) command examples alongside PowerShell for all steps, as Azure CLI is cross-platform and widely used on Linux.
  • In the prerequisites, mention and link to instructions for installing and using Azure CLI and Bash in Cloud Shell, not just PowerShell.
  • Where possible, use neutral language (e.g., 'Azure Cloud Shell or Azure CLI/PowerShell') and avoid assuming PowerShell as the default.
  • Include notes or sections specifically for Linux users, highlighting any differences or additional considerations.
  • If PowerShell is required for a specific feature, explicitly state this and suggest alternatives or workarounds for Linux users.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/network-watcher/migrate-to-connection-monitor-from-network-performance-monitor.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Windows First Windows Tools Missing Linux Example
Summary:
The documentation demonstrates a Windows bias by referencing Windows-specific tools and extensions before or instead of their Linux equivalents. For example, the migration steps and prerequisites focus on the 'Network Watcher extension' with a direct link to a Windows-specific page, and there is no mention of the Linux agent installation or migration process. Additionally, while Linux support is mentioned in a comparison table, there are no Linux-specific instructions or examples provided throughout the migration process.
Recommendations:
  • Include explicit instructions and links for installing and migrating the Network Watcher extension on Linux VMs, not just Windows.
  • When referencing agent installation or migration, provide parity by mentioning both Windows and Linux procedures, ideally with side-by-side examples or links.
  • Avoid linking only to Windows-specific documentation (e.g., network-watcher-agent-windows.md); instead, link to a platform-neutral or Linux-specific page as well.
  • Add troubleshooting steps and common error messages that are relevant to Linux environments.
  • Ensure that automation examples (e.g., PowerShell, Azure CLI, Terraform) include Linux-friendly CLI commands and not just PowerShell scripts.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/network-watcher/network-watcher-agent-linux.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows Tools Windows First
Summary:
The documentation, while focused on Linux VMs, demonstrates a moderate Windows bias by prioritizing PowerShell (a Windows-centric tool) in both prerequisites and procedural steps, and by referencing Azure PowerShell cmdlets and tooling before or alongside Azure CLI. There is also a minor error in the Azure CLI install example, referencing 'Network Watcher Agent for Windows' in a Linux context. The documentation does not provide any native Linux shell (bash) or scripting examples, and assumes the use of Windows-oriented management tools even for Linux VM management.
Recommendations:
  • Prioritize Azure CLI examples before PowerShell, as Azure CLI is cross-platform and more familiar to Linux users.
  • Add native Linux shell (bash) examples for relevant operations, especially for users managing Linux VMs from Linux environments.
  • Clarify that PowerShell is available cross-platform, but highlight Azure CLI and bash as the primary tools for Linux VM management.
  • Correct the Azure CLI example comment to reference 'Network Watcher Agent for Linux' instead of Windows.
  • Where possible, provide guidance for managing extensions directly from within the Linux VM (e.g., using the Azure CLI installed on the VM), not just from external management endpoints.
  • Consider including a section on using REST API or SDKs from Linux environments for advanced users.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/network-watcher/nsg-flow-logs-template.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Missing Linux Example Windows Tools Windows First
Summary:
The documentation page demonstrates a clear Windows bias by exclusively using Azure PowerShell for deployment instructions, referencing Windows-style file paths (e.g., C:\MyTemplates\azuredeploy.json), and omitting any CLI or Bash/Linux-based examples. There is no mention of Azure CLI, Bash, or cross-platform alternatives, and the only automation example provided is specific to Windows environments.
Recommendations:
  • Add equivalent Azure CLI examples for deploying ARM templates, which are cross-platform and widely used on Linux and macOS.
  • Include Bash shell commands and use POSIX-style file paths (e.g., ~/MyTemplates/azuredeploy.json) alongside Windows paths.
  • Explicitly mention that the steps can be performed on any OS, and provide links to both PowerShell and CLI documentation.
  • Reorder or parallelize instructions so that Windows and Linux/macOS users see their options presented equally, rather than Windows-first.
  • Where possible, use neutral language and tooling (e.g., 'use your preferred shell or CLI') to avoid implying Windows is the default or only supported environment.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/network-watcher/network-watcher-diagnose-on-premises-connectivity.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Missing Linux Example
Summary:
The documentation page provides instructions for diagnosing on-premises VPN connectivity with Azure using the Network Watcher VPN troubleshoot tool, but it does not include any command-line examples or guidance for either Windows (e.g., PowerShell) or Linux (e.g., Bash, CLI). However, the absence of any Linux-specific instructions or references to Linux tools/logs, especially in the context of on-premises VPN devices (which are often Linux-based), may be seen as a subtle bias by omission. The documentation assumes use of the Azure Portal and does not address parity for users who may prefer or require CLI-based troubleshooting, which is common on Linux systems.
Recommendations:
  • Add Azure CLI and/or PowerShell command-line examples for running VPN troubleshoot, and ensure both Windows and Linux usage is covered.
  • Include references or links to how to access and interpret VPN logs on common Linux-based VPN devices, not just Azure-side logs.
  • Mention or provide troubleshooting steps that are applicable to both Windows and Linux on-premises VPN devices, or clarify if the steps are platform-agnostic.
  • If screenshots or examples are provided, ensure there is a balance between Windows and Linux environments, or use neutral/portal-based screenshots.
  • Explicitly state that the troubleshooting steps apply regardless of the on-premises VPN device OS, or provide separate sections for Windows and Linux devices if relevant.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/network-watcher/network-watcher-visualize-nsg-flow-logs-power-bi.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Windows Tools Missing Linux Example Windows First
Summary:
The documentation exclusively describes using Power BI Desktop, a Windows-only tool, for visualizing Azure NSG flow logs. All setup and usage instructions assume the reader is on Windows, with no mention of Linux-compatible alternatives or cross-platform options. There are no examples or guidance for Linux users, and the workflow is centered around Windows tooling from the outset.
Recommendations:
  • Provide equivalent instructions for Linux users, such as using Power BI on the web (if supported for this scenario), or alternative open-source visualization tools (e.g., Grafana, Kibana, or Jupyter Notebooks).
  • Explicitly mention platform requirements and offer guidance for non-Windows users at the start of the article.
  • Where possible, include cross-platform scripts or methods for downloading and parsing NSG flow logs (e.g., using Python, Azure CLI, or Bash scripts).
  • Reference and link to the 'Visualize Azure Network Watcher NSG flow logs using open source tools' article earlier in the page, and summarize its relevance for Linux users.
  • Consider providing a table comparing visualization options for Windows and Linux, highlighting supported features and limitations.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/network-watcher/network-watcher-monitor-with-azure-automation.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Missing Linux Example Windows Tools Windows First
Summary:
The documentation is heavily biased towards Windows and PowerShell usage. All scripting examples are provided exclusively in PowerShell, with explicit recommendations to follow PowerShell naming conventions. There is no mention of Linux, Bash, or cross-platform scripting alternatives. The tools and modules referenced (e.g., AzureRM.Network, Send-MailMessage) are PowerShell-centric and typically associated with Windows environments. No equivalent instructions or code samples are provided for Linux users or those preferring Bash, Azure CLI, or Python.
Recommendations:
  • Provide equivalent examples using Azure CLI and/or Bash scripts for Linux users.
  • Mention cross-platform automation options, such as Python runbooks or Azure CLI runbooks, and provide guidance on their use.
  • Include notes or sections that address Linux environments and how to achieve the same automation and monitoring tasks.
  • Avoid language that assumes PowerShell is the default or only scripting environment; instead, present PowerShell and other options side-by-side.
  • Reference Linux-compatible SMTP/email tools or libraries for sending notifications, not just Send-MailMessage.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/network-watcher/network-watcher-agent-update.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Missing Linux Example Windows Tools
Summary:
The documentation demonstrates a Windows bias by providing a PowerShell script only for bulk updating extensions (with no Bash or cross-platform alternative), prioritizing PowerShell-based workflows, and referencing Windows tools and patterns. While some CLI examples are provided for both Linux and Windows, the advanced automation scenario (bulk update) is only covered for Windows/PowerShell. Linux users are not given equivalent scripting guidance, and PowerShell is presented as the primary automation method.
Recommendations:
  • Provide a Bash or Azure CLI script example for bulk updating the Network Watcher extension across multiple Linux VMs, similar to the PowerShell script for Windows.
  • When presenting manual update instructions, ensure Linux and Windows examples are equally detailed and appear in parallel, rather than PowerShell (Windows) first.
  • Explicitly mention cross-platform tools (such as Azure CLI and Bash) as automation options, not just PowerShell.
  • Where possible, use cross-platform scripting (e.g., Azure CLI in Bash or PowerShell Core) for automation examples.
  • Add a section or note clarifying automation options for Linux users, and link to relevant Linux scripting resources.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/network-watcher/nsg-flow-logs-overview.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows Tools Windows First Missing Linux Example
Summary:
The documentation page shows a moderate Windows bias. PowerShell is the only command-line example provided for configuring NSG flow log settings (specifically, setting FlowTimeoutInMinutes), with no equivalent CLI or Linux shell example. The only scripting tool referenced for configuration is PowerShell, and the cmdlet Set-AzVirtualNetwork is highlighted without mention of Azure CLI or REST API alternatives. This may disadvantage Linux or cross-platform users. Additionally, the 'Read flow logs using PowerShell functions' link is listed before any cross-platform or Linux-native tooling, and there are no explicit Linux/Bash examples for log access, export, or configuration.
Recommendations:
  • Provide Azure CLI (az network vnet update ...) and/or REST API examples alongside PowerShell for all configuration tasks, especially for setting FlowTimeoutInMinutes.
  • Include Linux/Bash shell command examples for reading, exporting, and processing NSG flow logs.
  • When listing tools or guides, avoid placing Windows/PowerShell options first by default; alternate ordering or group by platform.
  • Explicitly mention that all features are available via cross-platform tools (Azure CLI, REST API) and provide links to those docs.
  • Where possible, add troubleshooting and workflow examples relevant to Linux environments.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/network-watcher/nsg-flow-logs-migrate.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Missing Linux Example Windows Tools
Summary:
The documentation is heavily biased towards PowerShell, with all scripting and automation examples provided exclusively in PowerShell (.ps1) format. There are no equivalent Bash, Azure CLI, or Linux-native script examples. The prerequisites and instructions assume the use of PowerShell, and while there is a brief mention that PowerShell 7 can be installed on Linux and macOS, no Linux-specific guidance, troubleshooting, or alternative workflows are provided. This may create barriers for Linux users or those who prefer Bash/Azure CLI.
Recommendations:
  • Provide equivalent migration scripts and instructions using Azure CLI and/or Bash, ensuring Linux users have a native option.
  • Explicitly document how to run the provided PowerShell script on Linux (e.g., using pwsh), including any platform-specific prerequisites or troubleshooting tips.
  • Add examples and screenshots from Linux environments (e.g., terminal output, file extraction commands) to demonstrate cross-platform support.
  • Clarify in the prerequisites and throughout the guide that all steps are cross-platform, or provide separate sections for Windows and Linux/Mac users.
  • Consider offering downloadable migration scripts in both PowerShell and Bash/Azure CLI formats.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/network-watcher/nsg-flow-logs-tutorial.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example Windows Tools
Summary:
The documentation demonstrates a Windows bias by exclusively using Windows Server as the VM image, instructing users to enable RDP (Remote Desktop Protocol), and guiding them to connect via RDP and use Microsoft Edge. There are no examples or instructions for deploying or accessing a Linux VM, nor are SSH or Linux tools mentioned. The workflow assumes a Windows environment throughout.
Recommendations:
  • Provide parallel instructions for creating a Linux VM (e.g., Ubuntu) alongside the Windows VM example.
  • Include steps for connecting to a Linux VM using SSH, and mention opening port 22 for SSH access.
  • Show how to access flow logs from a Linux VM, possibly using command-line tools like curl, wget, or Azure CLI.
  • Mention Linux-compatible text editors (e.g., nano, vim) for viewing the downloaded JSON log file.
  • Balance the use of Windows-specific tools (like RDP and Microsoft Edge) with Linux equivalents (SSH, Firefox, etc.), or clarify that the tutorial applies to both OS types.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/network-watcher/nsg-flow-logs-policy-portal.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Missing Linux Example
Summary:
The documentation exclusively describes how to manage NSG flow logs using the Azure Portal GUI, without providing any command-line examples. There are no references to Windows-specific tools (such as PowerShell), but there is also a complete absence of CLI-based instructions (such as Azure CLI or Bash), which are commonly used on Linux and cross-platform environments. This omission may disadvantage Linux users or those who prefer automation and scripting.
Recommendations:
  • Add Azure CLI examples for all policy assignment and compliance-check steps, using Bash syntax.
  • Where possible, provide both Azure CLI and PowerShell examples, and present them in parallel or with tabs, ensuring neither platform is prioritized.
  • Explicitly mention that the Azure CLI commands can be run on Windows, Linux, or macOS.
  • Include links to relevant Azure CLI and PowerShell documentation for further reference.
  • Ensure screenshots and walkthroughs are not solely portal-based; consider including terminal output or code snippets.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/network-watcher/traffic-analytics-policy-portal.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Missing Linux Example
Summary:
The documentation exclusively describes how to manage traffic analytics using the Azure Portal GUI, with no command-line examples provided for any platform. There are no references to Windows-specific tools, PowerShell, or Windows-first patterns. However, the absence of CLI (Azure CLI, Bash, or PowerShell) examples means that Linux and cross-platform users do not have parity with Windows users who might expect PowerShell or GUI workflows. This lack of CLI coverage can be considered a subtle bias, as many Azure docs provide both portal and CLI/PowerShell instructions to support all user environments.
Recommendations:
  • Add Azure CLI examples for all policy assignment and remediation tasks, as Azure CLI is cross-platform and widely used on Linux.
  • If relevant, provide PowerShell examples as well, but ensure CLI/Bash examples are presented first or alongside PowerShell.
  • Explicitly mention that all steps can be performed via the Azure CLI or ARM templates, and link to relevant documentation.
  • Include a section or callout for Linux/macOS users, highlighting cross-platform tools and commands.
  • Ensure screenshots and instructions are not portal-only, or at least provide equivalent command-line steps for automation and scripting scenarios.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/network-watcher/packet-capture-alert-triggered.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Missing Linux Example Windows Tools
Summary:
The documentation page demonstrates a strong Windows and PowerShell bias. All code examples for automation, authentication, and packet capture are provided exclusively in PowerShell, with no equivalent Bash, CLI, or Python examples for Linux users. The prerequisites and workflow focus on Azure PowerShell and Windows-centric tooling, and the authentication steps assume a Windows environment (e.g., file paths like C:\temp). Although there is a brief mention of a Linux VM extension, the actual automation and scripting guidance is entirely Windows/PowerShell-based, leaving Linux users without clear guidance.
Recommendations:
  • Provide equivalent examples using Azure CLI (az) and/or Bash scripts for Linux environments, especially for authentication and packet capture automation.
  • Include Python or REST API examples for cross-platform automation, as Azure Functions support multiple languages.
  • When referencing file paths or environment setup, include Linux-compatible paths and instructions (e.g., /tmp/PassEncryptKey.key).
  • Explicitly mention and link to documentation for Linux VM extensions and how to use them in automation scenarios.
  • Balance the order of presentation so that Linux and Windows approaches are given equal prominence, or present cross-platform solutions first.
  • Clarify which steps are platform-agnostic and which are OS-specific, and provide guidance for both.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/network-watcher/vm-network-troubleshooter.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/network-watcher/vpn-troubleshoot-overview.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows Tools Windows First Missing Linux Example
Summary:
The documentation shows a moderate Windows bias. While it mentions that VPN troubleshooting can be performed via Azure portal, PowerShell, CLI, or REST API, there is a clear preference for PowerShell and Windows-centric tools. For example, PowerShell is mentioned as an alternative to Azure CLI for scenarios where resources are in different resource groups, but no Linux/Unix alternatives are suggested. Log file examples and error messages reference Windows-specific error codes and paths (e.g., C:\Resources\...), and logs such as IKEErrors.txt explicitly mention 'Windows error' codes. There are no Linux-specific troubleshooting examples, error codes, or references to common Linux VPN tools or logs.
Recommendations:
  • Provide Linux/Unix command-line examples (e.g., using Azure CLI on Linux, Bash scripts) alongside or before PowerShell examples.
  • Include references to Linux error codes or troubleshooting steps for common Linux VPN clients (e.g., strongSwan, OpenVPN).
  • When discussing log files and error messages, clarify which are Windows-specific and provide Linux equivalents if available.
  • Avoid using only Windows file paths in examples; include Linux path formats where relevant.
  • Mention Linux-compatible tools for downloading blobs (e.g., azcopy, wget, or Azure CLI) alongside Storage Explorer.
  • Explicitly state when a troubleshooting step or log is only relevant to Windows, and provide Linux alternatives or note their absence.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/network-watcher/diagnose-vm-network-routing-problem-powershell.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Missing Linux Example Windows Tools
Summary:
The documentation exclusively uses Azure PowerShell cmdlets and PowerShell scripting syntax for all examples and instructions. There are no references to Azure CLI, Bash, or Linux-native tools, nor are there any examples or guidance for users on Linux or macOS platforms. The prerequisites and workflow assume the use of PowerShell, which is more familiar to Windows users, and do not mention alternative cross-platform tools or approaches.
Recommendations:
  • Provide equivalent Azure CLI (az) command examples alongside PowerShell examples throughout the documentation.
  • Explicitly mention that Azure CLI and Bash can be used in Azure Cloud Shell, and provide instructions for both environments.
  • Include a section or callouts for Linux/macOS users, highlighting any differences or additional steps required.
  • Where possible, use cross-platform language and tools first, or present them alongside Windows/PowerShell instructions.
  • Update the prerequisites to mention both Azure PowerShell and Azure CLI, with links to installation and usage guides for each.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/network-watcher/vm-network-troubleshooter.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example
Summary:
The documentation page exhibits a subtle Windows bias by prioritizing RDP (port 3389) as a primary example of a commonly checked port, without mentioning SSH (port 22), which is the standard for Linux VMs. There are no Linux-specific examples or references, and the troubleshooting workflow is described in a way that implicitly assumes Windows-centric usage patterns.
Recommendations:
  • Include SSH (port 22) as a commonly checked port alongside RDP, HTTP, and HTTPS.
  • Explicitly mention that the troubleshooter can be used for both Windows and Linux VMs.
  • Provide examples or screenshots that show troubleshooting for Linux VMs (e.g., checking SSH connectivity).
  • Clarify that the tool is platform-agnostic and applicable to both Windows and Linux environments.
  • Consider reordering the list of ports or providing parity in examples (e.g., 'Port 3389 (RDP, Windows)' and 'Port 22 (SSH, Linux)').
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/network-watcher/diagnose-vm-network-routing-problem.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example
Summary:
The tutorial demonstrates a bias toward Windows by exclusively using Windows Server as the VM image and only providing instructions for connecting via RDP. There are no Linux VM creation steps, nor are there SSH or Linux-specific instructions. This may lead Linux users to feel unsupported or unclear about how to follow the tutorial with Linux VMs.
Recommendations:
  • Provide parallel instructions for creating a Linux VM (e.g., Ubuntu) alongside the Windows VM example.
  • Include steps for connecting to a Linux VM using SSH, in addition to the RDP instructions for Windows.
  • Show how to verify network connectivity from a Linux VM (e.g., using curl or wget to access www.bing.com).
  • Clarify in the prerequisites or introduction that the tutorial applies to both Windows and Linux VMs, and link to both sets of instructions.
  • Where possible, use neutral terms (e.g., 'connect to your VM') and provide both RDP (Windows) and SSH (Linux) options.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/network-watcher/effective-security-rules-overview.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Missing Linux Example
Summary:
The documentation page does not provide any OS-specific examples or instructions, but it also does not mention or demonstrate how to access effective security rules using command-line tools or scripts on either Windows (e.g., PowerShell) or Linux (e.g., Bash, CLI). This omission results in a lack of Linux parity, as users on Linux systems are not shown how to interact with the feature outside the Azure portal.
Recommendations:
  • Add examples for accessing effective security rules using Azure CLI commands, which are cross-platform and work on both Windows and Linux.
  • If scripting examples are provided in the future, ensure both PowerShell (Windows) and Bash (Linux) examples are included.
  • Explicitly mention that the Azure portal is OS-agnostic, but provide links or references to documentation for command-line access on different platforms.
  • Include a section on automating rule retrieval using scripts, with parity between Windows and Linux approaches.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/network-watcher/ip-flow-verify-overview.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Missing Linux Example
Summary:
The documentation page does not provide any OS-specific examples, commands, or tools, but it also does not mention or show parity for Linux or Windows environments. There are no explicit references to Windows tools, PowerShell, or command-line examples for any platform. However, the lack of any example commands or screenshots showing both Windows and Linux VMs may implicitly bias the documentation towards users who are familiar with the Azure Portal UI, which is platform-agnostic but often more familiar to Windows users.
Recommendations:
  • Add explicit examples or notes clarifying that IP flow verify works for both Windows and Linux VMs.
  • Include screenshots or walkthroughs that reference both Windows and Linux VM scenarios to demonstrate parity.
  • If CLI or PowerShell examples are added in the future, ensure that equivalent Azure CLI (cross-platform) and PowerShell (Windows and cross-platform) instructions are provided.
  • Mention in the overview that the feature is OS-agnostic and can be used with any VM OS supported by Azure.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/network-watcher/connection-monitor-connected-machine-agent.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Windows First Powershell Heavy Windows Tools
Summary:
The documentation demonstrates a Windows bias by consistently presenting Windows instructions and tools (such as PowerShell and Windows Admin Center) before their Linux equivalents. PowerShell is emphasized as a cross-platform automation tool, but Linux-specific automation (e.g., Bash, shell scripts, or Ansible) is not mentioned. Windows Admin Center is highlighted as a management tool, with no Linux-native alternatives discussed. While Linux installation steps are present, they are less detailed and not given parity in automation or tooling recommendations.
Recommendations:
  • Alternate the order of Windows and Linux instructions or present them side-by-side to avoid always listing Windows first.
  • Include Linux-native automation options (e.g., Bash scripts, Ansible, or shell-based onboarding) alongside PowerShell.
  • Mention or link to Linux management tools (such as Cockpit or other open-source solutions) if relevant, or clarify that similar Linux-native tooling is not available.
  • Ensure that Linux examples are as detailed as Windows examples, including troubleshooting and verification steps.
  • Where PowerShell is recommended for automation, clarify its cross-platform nature and provide equivalent Bash or shell script examples for Linux users.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/network-watcher/connection-monitor-overview.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example
Summary:
The documentation generally maintains OS neutrality but exhibits subtle Windows bias in the order of references and lack of Linux-specific examples. In the 'Monitoring connectivity from Azure virtual machines and virtual machine scale sets' section, the link to 'Manage Network Watcher extension for Windows' is listed before the Linux equivalent, and there are no explicit Linux or cross-platform command-line examples (e.g., Bash, Azure CLI) in the 'Create a connection monitor' section, where only Azure PowerShell is mentioned as a programmatic method. This may give the impression that Windows or PowerShell is the primary or preferred environment.
Recommendations:
  • When listing OS-specific instructions or links, alternate the order or list Linux first in some sections to avoid implicit prioritization.
  • Provide explicit Linux/Bash/Azure CLI examples alongside or before PowerShell examples when describing command-line or automation workflows.
  • Mention cross-platform tools (such as Azure CLI or ARM templates) equally or before Windows-specific tools like PowerShell.
  • Add a table or section summarizing parity between Windows and Linux for agent installation, troubleshooting, and automation.
  • Ensure that all references to monitoring agents, troubleshooting steps, and automation methods clearly state support for both Windows and Linux, and provide parallel examples where applicable.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/network-watcher/connection-monitor-install-azure-monitor-agent.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Windows Tools
Summary:
The documentation demonstrates a mild Windows bias. PowerShell is presented as the primary scripting method, even for Linux scenarios, rather than using native Linux shells (e.g., Bash). In all code tab groups, Windows examples are listed before Linux, and the use of Windows-specific tools and naming conventions (such as PowerShell cmdlets and 'WindowsAgent' naming) is prevalent. There are no Bash or native Linux shell examples, and Linux instructions are essentially adaptations of the Windows/PowerShell workflow.
Recommendations:
  • Provide native Bash or shell script examples for Linux scenarios, especially when using the Azure CLI.
  • List Linux and Windows examples in parallel or alternate the order to avoid always presenting Windows first.
  • When referencing tools, clarify if they are cross-platform or provide Linux-native alternatives where possible.
  • Use more neutral language and variable names (e.g., avoid 'WindowsAgent' as the default unless contextually necessary).
  • Explicitly mention any differences or considerations unique to Linux environments beyond just swapping agent names.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/network-watcher/diagnose-vm-network-traffic-filtering-problem-powershell.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Missing Linux Example Windows Tools
Summary:
The documentation is heavily focused on Azure PowerShell, providing only PowerShell-based examples and instructions. There are no examples or guidance for using Azure CLI, Bash, or other cross-platform tools, even though the scenario (diagnosing VM network issues) is relevant for both Windows and Linux users. The prerequisites and step-by-step instructions assume the use of PowerShell, which is more familiar to Windows users, and there is no mention of Linux-native workflows or tools.
Recommendations:
  • Add equivalent Azure CLI (az) command examples alongside PowerShell commands for each step.
  • Explicitly mention that Azure Cloud Shell supports both Bash and PowerShell, and provide instructions for both.
  • Include a section or callout for Linux users, highlighting any differences or additional considerations.
  • Where possible, use cross-platform terminology and avoid assuming PowerShell as the default shell.
  • Link to documentation for both Azure PowerShell and Azure CLI installation and usage.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/network-watcher/connection-troubleshoot-manage.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example
Summary:
The documentation consistently uses Windows-centric examples, particularly by focusing on RDP (port 3389) connectivity, which is specific to Windows environments. There are no equivalent Linux scenarios (such as SSH on port 22) provided. The troubleshooting steps and sample outputs are all based on RDP, and solutions reference enabling RDP or related Windows firewall/security group rules. While the documentation does mention Linux in the context of installing the Network Watcher agent, it does not provide Linux-specific connectivity tests or troubleshooting examples.
Recommendations:
  • Include Linux-centric connectivity scenarios, such as testing SSH (port 22) between virtual machines, alongside or instead of RDP examples.
  • For each troubleshooting example, provide parallel steps and outputs for both RDP (Windows) and SSH (Linux) to ensure parity.
  • In solution sections, mention updating firewall rules for SSH on Linux (e.g., opening port 22) as well as RDP for Windows.
  • Where operating system configuration is referenced, provide guidance for both Windows (enabling RDP) and Linux (enabling SSH, checking sshd status, etc.).
  • Ensure that screenshots and sample outputs reflect both Windows and Linux use cases where applicable.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/network-watcher/diagnose-network-security-rules.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example
Summary:
The documentation exhibits a 'windows_first' bias by exclusively using Windows Server images and Windows-centric terminology in all virtual machine creation steps, both in the Azure Portal and command-line examples. There are no examples or instructions for deploying or managing Linux-based virtual machines, nor is there any mention of Linux-specific considerations or differences. This may lead Linux users to feel unsupported or uncertain about following the guide for their scenarios.
Recommendations:
  • Add parallel Linux examples for all VM creation steps, both in the Portal and CLI/PowerShell sections (e.g., show how to select Ubuntu or another popular Linux image).
  • In the Portal instructions, include a step or note showing how to select a Linux image and set up SSH authentication.
  • In PowerShell and Azure CLI examples, provide Linux image references (e.g., 'Canonical:UbuntuServer:20_04-lts:latest') and show how to configure Linux-specific parameters such as SSH keys.
  • Where administrator credentials are discussed, mention SSH keys for Linux and provide guidance for secure setup.
  • Add a note clarifying that the NSG diagnostics and other procedures are applicable to both Windows and Linux VMs, and highlight any OS-specific considerations if relevant.
  • Ensure screenshots and example outputs are not exclusively Windows-centric, or provide Linux equivalents where possible.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/network-watcher/migrate-to-connection-monitor-from-network-performance-monitor.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Windows First Windows Tools Missing Linux Example
Summary:
The documentation demonstrates subtle Windows bias. It references Windows-specific tools and extensions (e.g., Network Watcher extension for Windows), and provides links and instructions that are Windows-centric. Linux support is mentioned, but Linux-specific instructions, examples, or agent documentation are missing. Automation examples mention PowerShell before Azure CLI and Terraform, and there are no Linux command-line or agent installation examples.
Recommendations:
  • Provide explicit Linux agent installation and migration instructions, including links to Linux-specific documentation.
  • Include Linux command-line examples (e.g., Bash, Azure CLI) alongside or before PowerShell examples.
  • When referencing extensions or agents, mention both Windows and Linux versions, and provide links to both.
  • Ensure automation tooling is presented in a cross-platform order (e.g., Azure CLI, Terraform, then PowerShell), or group them together without preference.
  • Add a section or callout for Linux users highlighting any differences or additional steps required.
  • Review all references to ensure Linux parity in troubleshooting, error messages, and integration guidance.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/network-watcher/network-watcher-create.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Windows First Powershell Heavy Windows Tools
Summary:
The documentation demonstrates a mild Windows bias by consistently presenting PowerShell (a Windows-centric tool) before Azure CLI in both prerequisites and procedural sections. PowerShell-specific instructions and terminology are detailed, and PowerShell is referenced as the method for advanced customization (e.g., naming resources), sometimes to the exclusion of CLI or Linux-native alternatives. There is no explicit mention of Linux or Bash, and no Linux-specific examples or guidance are provided, even though Azure CLI is cross-platform.
Recommendations:
  • Alternate the order of PowerShell and Azure CLI sections, or present Azure CLI first in some sections to avoid the impression of Windows-first bias.
  • Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and provide Bash-specific usage notes or examples where relevant.
  • Where PowerShell is referenced for advanced scenarios (e.g., custom naming), ensure equivalent Azure CLI methods are described, or clarify if not possible.
  • Add a brief section or note in prerequisites highlighting that Azure CLI is available natively on Linux and macOS, and that Cloud Shell supports both Bash and PowerShell.
  • Avoid language that implies PowerShell is the default or preferred scripting environment unless there is a technical reason.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/network-watcher/network-watcher-diagnose-on-premises-connectivity.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Missing Linux Example
Summary:
The documentation does not display overt Windows bias in terms of tools or command-line examples, as it relies entirely on Azure Portal UI instructions. However, there is a lack of parity for Linux users: there are no examples or guidance for performing VPN troubleshooting using CLI tools (such as Azure CLI, Bash, or PowerShell), nor is there mention of how to access or interpret logs from a Linux environment. The documentation implicitly assumes a GUI/portal workflow, which may not suit Linux administrators who prefer or require command-line or scriptable solutions.
Recommendations:
  • Add step-by-step instructions for using Azure CLI (az network watcher vpn-troubleshoot) to perform the same troubleshooting tasks, including log retrieval and interpretation.
  • Provide examples for downloading and analyzing diagnostic logs using Bash or other Linux-native tools.
  • Mention and link to PowerShell and CLI documentation equally, ensuring both Windows and Linux administrators can follow along.
  • Clarify that the portal-based workflow is cross-platform, but offer alternatives for users who prefer or require command-line access.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/network-watcher/network-watcher-agent-linux.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows Tools Windows First
Summary:
Although the documentation is focused on managing the Network Watcher Agent VM extension for Linux, there is a notable emphasis on PowerShell usage, which is traditionally a Windows-centric tool. PowerShell is presented as a primary automation/scripting method alongside Azure CLI, and instructions for deploying ARM templates reference Azure PowerShell before Azure CLI. There is also a minor error in the Azure CLI install example referencing 'Network Watcher Agent for Windows' instead of Linux. No Linux-native tools or shell scripting examples (e.g., Bash) are provided, and the documentation assumes the use of Azure-specific tools rather than generic Linux administration patterns.
Recommendations:
  • Provide Bash shell script examples for common operations (install, list, uninstall) using Azure CLI, to better align with Linux administrator workflows.
  • When listing automation options, present Azure CLI before PowerShell, as CLI is cross-platform and more familiar to Linux users.
  • Clarify that PowerShell is available cross-platform, but highlight that Azure CLI is often preferred for Linux environments.
  • Correct the minor error in the Azure CLI install example that refers to 'Network Watcher Agent for Windows' instead of Linux.
  • Consider including examples of how to automate extension management using native Linux tools (e.g., curl with Azure REST API) for advanced users.
  • Explicitly state that no Linux-native package management (apt, yum, etc.) is involved, to avoid confusion.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/network-watcher/network-watcher-agent-update.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Missing Linux Example
Summary:
The documentation demonstrates a Windows bias in several ways: (1) The only provided script for bulk updating extensions across multiple VMs is a PowerShell script, which is inherently Windows-centric and requires Azure PowerShell modules. (2) The 'Update your extension using a PowerShell script' section exclusively targets Windows VMs, with no equivalent Bash or Azure CLI script for Linux VMs. (3) In several sections, PowerShell is presented as the primary or first method, with Linux/Azure CLI alternatives appearing later or not at all. (4) There is no example of a Bash or shell script for bulk updating Linux VMs, and no mention of automation approaches for Linux outside of Azure CLI one-liners.
Recommendations:
  • Provide a Bash or Azure CLI script example for bulk updating the Network Watcher extension across multiple Linux VMs, similar to the PowerShell script for Windows.
  • Ensure that automation examples for both Windows and Linux are given equal prominence and detail, ideally in parallel sections or tabs.
  • When listing manual update options, present Azure CLI and PowerShell examples side-by-side, or alternate which is shown first.
  • Explicitly mention cross-platform automation options (such as using Azure CLI in Bash or Python scripts) for managing both Windows and Linux VMs at scale.
  • Review the order of examples and ensure Linux and Windows are treated equally throughout the documentation.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/network-watcher/network-watcher-monitor-with-azure-automation.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Missing Linux Example Windows Tools
Summary:
The documentation is heavily biased towards Windows and PowerShell. All scripting examples use PowerShell, and the instructions reference PowerShell-specific cmdlets and naming conventions. There are no examples or guidance for users on Linux or macOS, nor are cross-platform tools or alternatives mentioned. The documentation assumes familiarity with Windows tooling and does not address how to achieve the same results using Bash, Azure CLI, or other cross-platform scripting environments.
Recommendations:
  • Provide equivalent examples using Azure CLI (az commands), which is cross-platform and works on Linux, macOS, and Windows.
  • Include Bash script samples for Linux users, demonstrating how to automate VPN gateway monitoring and notifications.
  • Mention that Azure Automation supports Python runbooks and provide a Python example for the scenario.
  • Clarify which steps are platform-agnostic (e.g., using the Azure Portal) and which are specific to Windows/PowerShell.
  • Add a section or note for Linux/macOS users, outlining how to set up and monitor VPN gateways using non-Windows tools.
  • Reference documentation or guides for setting up Azure Automation runbooks with languages other than PowerShell.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/network-watcher/network-watcher-visualize-nsg-flow-logs-power-bi.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Windows Tools Missing Linux Example Windows First
Summary:
The documentation is heavily focused on using Power BI Desktop, a Windows-only tool, for visualizing Azure NSG flow logs. There are no instructions or examples for Linux users, nor are alternative cross-platform or Linux-native visualization tools mentioned in the main body of the guide. The workflow assumes access to and use of Windows-specific software, and Linux alternatives are only referenced in a 'Next steps' link at the end.
Recommendations:
  • Add explicit instructions or a parallel workflow for Linux users, such as using Power BI on the web (if supported for this scenario), or open-source alternatives like Grafana or Kibana.
  • Mention cross-platform or Linux-compatible tools earlier in the documentation, not just as a 'next step'.
  • Provide example commands or steps for accessing and preparing NSG flow logs on Linux (e.g., using Azure CLI, Python scripts, or other tools).
  • Clarify in the prerequisites that Power BI Desktop is only available for Windows, and suggest alternatives for users on other operating systems.
  • Consider offering a downloadable template or dashboard for open-source tools alongside the Power BI template.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/network-watcher/traffic-analytics-policy-portal.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Missing Linux Example
Summary:
The documentation exclusively uses the Azure Portal (web UI) for all instructions and does not provide any command-line examples (such as Azure CLI, PowerShell, or Bash scripts). While this avoids explicit Windows bias (e.g., PowerShell-only commands), it also omits Linux-friendly approaches, such as Azure CLI commands, which are cross-platform and commonly used on Linux. There is no mention of Linux tools, shell commands, or parity for non-Windows environments.
Recommendations:
  • Add Azure CLI examples for all policy assignment, remediation, and compliance-check steps. Azure CLI is cross-platform and works on Linux, macOS, and Windows.
  • If relevant, provide Bash script snippets for automating policy management tasks.
  • Include a section or callout that highlights how to perform these tasks using the Azure CLI or ARM templates, with links to relevant documentation.
  • Ensure screenshots and instructions do not assume a Windows environment (e.g., avoid references to Windows-specific file paths or tools).
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/network-watcher/nsg-flow-logs-migrate.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Missing Linux Example Windows Tools
Summary:
The documentation demonstrates a strong bias toward Windows and PowerShell usage. All scripting and automation examples are provided exclusively as PowerShell scripts (.ps1), with no mention of Bash, CLI, or Linux-native alternatives. The prerequisites and instructions assume the use of PowerShell, and there are no Linux- or cross-platform-specific examples or guidance, despite PowerShell Core being cross-platform. The documentation also references Windows-centric tools and patterns, such as the .ps1 script and Windows-style command prompts, without clarifying or demonstrating usage on Linux or macOS.
Recommendations:
  • Provide equivalent Bash or Azure CLI scripts/examples for Linux/macOS users, or at least mention how to run the PowerShell script on Linux/macOS using PowerShell 7.
  • Clarify in the prerequisites and instructions that PowerShell 7 is cross-platform, and provide explicit instructions for installing and running the script on Linux and macOS.
  • Add notes or sections that address common Linux/macOS environments, such as file extraction, script execution permissions (chmod +x), and how to invoke the script from a Linux shell.
  • Where screenshots or command prompts are shown, include examples from both Windows and Linux terminals to demonstrate parity.
  • If the migration process is only supported via PowerShell, explicitly state this limitation and provide a roadmap or alternatives for Linux users if possible.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/network-watcher/nsg-flow-logs-policy-portal.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Missing Linux Example
Summary:
The documentation exclusively describes how to manage NSG flow logs using the Azure Portal UI, with no mention of command-line alternatives such as Azure CLI, PowerShell, or scripting. There are no examples or instructions for Linux users or for cross-platform command-line tools, which could disadvantage users who prefer or require non-Windows environments.
Recommendations:
  • Add Azure CLI examples for all policy assignment and compliance tasks, as Azure CLI is cross-platform and widely used on Linux.
  • If relevant, include PowerShell examples, but always provide Azure CLI or REST API equivalents and present them first or side-by-side.
  • Explicitly mention that the Azure Portal is accessible from any OS, but also provide command-line and automation options for users who do not use the Portal.
  • Link to documentation on using Azure Policy with ARM templates, Azure CLI, and REST API for full cross-platform coverage.
  • Consider a section or callout for 'Command-line and automation options' to highlight parity for Linux and automation-focused users.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/network-watcher/nsg-flow-logs-template.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Missing Linux Example Windows Tools Windows First
Summary:
The documentation exclusively uses Azure PowerShell for deployment instructions and examples, with no mention of Azure CLI, Bash, or Linux-native workflows. File paths use Windows conventions (e.g., C:\MyTemplates\azuredeploy.json), and there are no Linux or cross-platform alternatives provided. This creates a strong Windows and PowerShell bias, making it less accessible for users on Linux or macOS.
Recommendations:
  • Add equivalent Azure CLI (az) examples for deploying ARM templates, using Bash syntax and Linux file paths (e.g., ~/MyTemplates/azuredeploy.json).
  • Mention both PowerShell and CLI as supported options in the introduction and prerequisites.
  • Where file paths are shown, provide both Windows and Linux/macOS examples.
  • Include notes or links for users on Linux/macOS, clarifying how to perform the same steps in their environments.
  • Consider reordering or parallelizing instructions so that neither Windows nor Linux is presented as the default or primary platform.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/network-watcher/nsg-flow-logs-tutorial.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example Windows Tools
Summary:
The documentation demonstrates a clear Windows bias: the only VM image used is Windows Server, and all instructions for connecting to the VM are via RDP, a Windows-specific protocol. There are no examples or guidance for deploying or connecting to a Linux VM (e.g., using SSH), nor are Linux images or tools mentioned. The workflow assumes a Windows environment throughout.
Recommendations:
  • Provide parallel instructions for creating a Linux VM (e.g., Ubuntu) alongside the Windows VM steps.
  • Include examples for connecting to the Linux VM using SSH, both via the Azure portal and from a local terminal.
  • Mention Linux-compatible tools for viewing and analyzing the downloaded flow logs (e.g., using cat, jq, or less).
  • When listing VM images, present both Windows and Linux options, or make it clear that the tutorial applies to both.
  • Add notes or callouts indicating how steps differ for Linux users, especially in sections involving remote access and credential setup.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/network-watcher/nsg-flow-logs-overview.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows Tools Windows First Missing Linux Example
Summary:
The documentation page demonstrates a Windows bias in several ways. PowerShell is the only command-line tool shown for configuring NSG flow log settings (e.g., setting FlowTimeoutInMinutes), with no equivalent Azure CLI, Bash, or Linux-native example. The reference to PowerShell (Set-AzVirtualNetwork) appears before any mention of other platforms, and there is no guidance for Linux users. The documentation also references tools like Power BI (a Microsoft/Windows-centric tool) before open-source or cross-platform alternatives, and does not provide parity in example commands or workflows for Linux environments.
Recommendations:
  • Add Azure CLI examples (az network vnet update ...) alongside or before PowerShell for all configuration tasks, especially for setting properties like FlowTimeoutInMinutes.
  • Include Bash or shell script snippets where appropriate, to demonstrate cross-platform usage.
  • When listing visualization tools, alternate or balance the order (e.g., mention Grafana or Elastic Stack before or alongside Power BI) and provide links to Linux-friendly guides.
  • Explicitly state that all features and workflows are available on both Windows and Linux, and provide links to relevant Linux documentation.
  • Where PowerShell is referenced, add a note or section for Linux/macOS users with equivalent commands.
  • Ensure that troubleshooting and setup sections include steps for both Windows and Linux environments.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/network-watcher/packet-capture-alert-triggered.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Missing Linux Example Windows Tools Windows First
Summary:
The documentation is heavily biased towards Windows and PowerShell. All code samples and automation steps use PowerShell exclusively, with no equivalent Bash, CLI, or Python examples for Linux users. The authentication and environment setup instructions assume a Windows-style file system and scripting environment. While there are brief mentions of a Linux VM extension, all practical guidance and tooling focus on Windows-first approaches, leaving Linux users without clear, actionable instructions.
Recommendations:
  • Provide equivalent examples using Azure CLI and/or Bash scripts for Linux environments, especially for authentication, environment variable setup, and packet capture initiation.
  • Include Python or other cross-platform scripting options for Azure Functions, not just PowerShell.
  • Show how to generate and store encrypted credentials on Linux (e.g., using OpenSSL or GPG) instead of only using Windows file paths and PowerShell encryption.
  • Explicitly mention and demonstrate how to use the Linux Network Watcher extension, including any differences in setup or operation.
  • Balance the order of presentation: introduce both Windows and Linux approaches side-by-side, or alternate which is presented first.
  • Reference Linux-friendly tools for downloading and analyzing packet captures (e.g., azcopy, wget, tcpdump, tshark) alongside Windows tools.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/network-watcher/packet-capture-manage.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Windows First Powershell Heavy Windows Tools Missing Linux Example
Summary:
The documentation demonstrates a moderate Windows bias. PowerShell is featured as a primary automation method, and file path examples (e.g., C:\Capture\myVM_1.cap) are consistently shown before Linux equivalents. Download examples and tool recommendations (e.g., Azure Storage Explorer) are Windows-centric, and Linux-specific instructions or examples are minimal or only mentioned as afterthoughts. There are no explicit Linux shell (bash) examples for downloading files or handling packet captures locally, and guidance for Linux users is limited to brief notes about file paths.
Recommendations:
  • Provide Linux-first or at least parallel Linux examples (e.g., show /var/captures/myVM_1.cap alongside C:\Capture\myVM_1.cap in all relevant code and tables).
  • Include bash or Linux shell command examples for downloading packet captures from Azure Storage (e.g., using azcopy, wget, or curl).
  • Mention and link to cross-platform tools (such as azcopy or rclone) for managing Azure Storage, not just Azure Storage Explorer.
  • When referencing local file paths, always show both Windows and Linux formats together, not just as a note.
  • In PowerShell and CLI sections, explicitly call out any OS-specific differences or requirements.
  • Consider adding a dedicated section or callout for Linux/macOS users, summarizing key differences and recommended tools.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/network-watcher/vnet-flow-logs-policy.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Missing Linux Example
Summary:
The documentation exclusively uses the Azure Portal (web UI) for all instructions and does not provide any command-line examples (such as Azure CLI, PowerShell, or Bash). While this avoids explicit Windows or PowerShell bias, it also omits Linux-friendly approaches, such as Azure CLI or Bash scripting, which are commonly used on Linux and cross-platform environments. This lack of parity may disadvantage users who prefer or require command-line automation, especially on Linux systems.
Recommendations:
  • Add equivalent Azure CLI examples for all policy assignment and compliance-checking steps. The Azure CLI is cross-platform and works well on Linux, macOS, and Windows.
  • Where possible, provide Bash script snippets for automating the tasks described, or reference official documentation for CLI-based policy management.
  • Explicitly mention that all tasks can be performed via Azure CLI or PowerShell, and provide links to those instructions if not included inline.
  • Ensure screenshots and UI references are supplemented with command-line alternatives to support users working in non-GUI or Linux environments.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/network-watcher/vpn-troubleshoot-overview.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows Tools Windows First Missing Linux Example
Summary:
The documentation page demonstrates a Windows bias in several ways: it references Azure PowerShell and the Azure portal (which is often Windows-centric) before Azure CLI or REST API, and provides no Linux-specific instructions or examples. The log file examples and error messages reference Windows error codes and paths (e.g., C:\Resources\...), and troubleshooting steps mention PowerShell as an alternative to Azure CLI without mentioning Bash or Linux-native tools. There are no Linux command-line examples or guidance for Linux administrators.
Recommendations:
  • Provide explicit Linux/Bash/Azure CLI examples alongside or before PowerShell examples.
  • Include Linux file path formats and clarify if logs can be interpreted on Linux systems.
  • Reference Linux-native tools (e.g., az CLI on Bash, or third-party tools for log analysis) where appropriate.
  • When mentioning downloading blobs, include instructions for Linux (e.g., using azcopy, wget, or the Azure CLI in Bash).
  • Clarify that the Azure portal and PowerShell are cross-platform, or provide links to Linux installation guides if relevant.
  • Where Windows error codes are referenced, provide guidance for interpreting similar errors on Linux VPN devices.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/network-watcher/vpn-troubleshoot-powershell.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Missing Linux Example
Summary:
The documentation page exclusively uses PowerShell cmdlets and examples for VPN troubleshooting, with no Azure CLI, Bash, or Linux-native command examples provided. The prerequisites and instructions focus on Azure PowerShell and Cloud Shell, which, while available cross-platform, are more familiar to Windows users. There is no mention of Linux shell scripting or CLI workflows in the main content, and the only reference to CLI is in the 'Related content' section, not in the main instructional flow.
Recommendations:
  • Add parallel Azure CLI examples for all PowerShell commands, ideally using Bash syntax.
  • Update prerequisites to mention both Azure PowerShell and Azure CLI as supported options, with links to installation guides for each.
  • Where PowerShell is referenced, clarify that Azure CLI is also available and provide a tabbed interface or side-by-side examples for both.
  • Include Linux/Bash-specific notes or tips where relevant, such as accessing logs or using CLI tools.
  • Ensure that links to CLI-based troubleshooting are more prominent, not just in 'Related content'.