Network Watcher
64
Total Pages
28
Linux-Friendly Pages
36
Pages with Bias
56.2%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
238 issues found
Showing 101-125 of 238 flagged pages
Network Watcher
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/network-watcher/diagnose-vm-network-routing-problem-powershell.md
...cher/diagnose-vm-network-routing-problem-powershell.md
High Priority
View Details →
Detected Bias Types
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.
Create Pull Request
Network Watcher
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/network-watcher/diagnose-vm-network-routing-problem-powershell.md
...cher/diagnose-vm-network-routing-problem-powershell.md
High Priority
View Details →
Detected Bias Types
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.
Network Watcher
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/network-watcher/vpn-troubleshoot-powershell.md
...rticles/network-watcher/vpn-troubleshoot-powershell.md
High Priority
View Details →
Detected Bias Types
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.
Network Watcher
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/network-watcher/connection-monitor-connected-machine-agent.md
...-watcher/connection-monitor-connected-machine-agent.md
High Priority
View Details →
Detected Bias Types
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.
Network Watcher
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/network-watcher/connection-monitor-overview.md
...rticles/network-watcher/connection-monitor-overview.md
High Priority
View Details →
Detected Bias Types
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.
Network Watcher
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/network-watcher/diagnose-vm-network-traffic-filtering-problem-powershell.md
...agnose-vm-network-traffic-filtering-problem-powershell.md
High Priority
View Details →
Detected Bias Types
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.
Network Watcher
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/network-watcher/migrate-to-connection-monitor-from-network-performance-monitor.md
...to-connection-monitor-from-network-performance-monitor.md
High Priority
View Details →
Detected Bias Types
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.
Network Watcher
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/network-watcher/network-watcher-agent-linux.md
...rticles/network-watcher/network-watcher-agent-linux.md
High Priority
View Details →
Detected Bias Types
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.
Network Watcher
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/network-watcher/nsg-flow-logs-template.md
...ain/articles/network-watcher/nsg-flow-logs-template.md
High Priority
View Details →
Detected Bias Types
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.
Network Watcher
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/network-watcher/network-watcher-visualize-nsg-flow-logs-power-bi.md
...er/network-watcher-visualize-nsg-flow-logs-power-bi.md
High Priority
View Details →
Detected Bias Types
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.
Network Watcher
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/network-watcher/network-watcher-monitor-with-azure-automation.md
...tcher/network-watcher-monitor-with-azure-automation.md
High Priority
View Details →
Detected Bias Types
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.
Network Watcher
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/network-watcher/network-watcher-agent-update.md
...ticles/network-watcher/network-watcher-agent-update.md
High Priority
View Details →
Detected Bias Types
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.
Network Watcher
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/network-watcher/nsg-flow-logs-overview.md
...ain/articles/network-watcher/nsg-flow-logs-overview.md
High Priority
View Details →
Detected Bias Types
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.
Network Watcher
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/network-watcher/nsg-flow-logs-migrate.md
...main/articles/network-watcher/nsg-flow-logs-migrate.md
High Priority
View Details →
Detected Bias Types
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.
Network Watcher
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/network-watcher/nsg-flow-logs-tutorial.md
...ain/articles/network-watcher/nsg-flow-logs-tutorial.md
High Priority
View Details →
Detected Bias Types
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.
Network Watcher
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/network-watcher/packet-capture-alert-triggered.md
...cles/network-watcher/packet-capture-alert-triggered.md
High Priority
View Details →
Detected Bias Types
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.
Network Watcher
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/network-watcher/vpn-troubleshoot-overview.md
.../articles/network-watcher/vpn-troubleshoot-overview.md
High Priority
View Details →
Detected Bias Types
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.
Network Watcher
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/network-watcher/diagnose-vm-network-routing-problem-powershell.md
...cher/diagnose-vm-network-routing-problem-powershell.md
High Priority
View Details →
Detected Bias Types
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.
Network Watcher
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/network-watcher/connection-monitor-connected-machine-agent.md
...-watcher/connection-monitor-connected-machine-agent.md
High Priority
View Details →
Detected Bias Types
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.
Network Watcher
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/network-watcher/connection-monitor-install-azure-monitor-agent.md
...cher/connection-monitor-install-azure-monitor-agent.md
High Priority
View Details →
Detected Bias Types
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.
Network Watcher
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/network-watcher/diagnose-vm-network-traffic-filtering-problem-powershell.md
...agnose-vm-network-traffic-filtering-problem-powershell.md
High Priority
View Details →
Detected Bias Types
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.
Network Watcher
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/network-watcher/migrate-to-connection-monitor-from-network-performance-monitor.md
...to-connection-monitor-from-network-performance-monitor.md
High Priority
View Details →
Detected Bias Types
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.
Network Watcher
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/network-watcher/network-watcher-create.md
...ain/articles/network-watcher/network-watcher-create.md
High Priority
View Details →
Detected Bias Types
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.
Network Watcher
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/network-watcher/network-watcher-agent-linux.md
...rticles/network-watcher/network-watcher-agent-linux.md
High Priority
View Details →
Detected Bias Types
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.
Network Watcher
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/network-watcher/network-watcher-agent-update.md
...ticles/network-watcher/network-watcher-agent-update.md
High Priority
View Details →
Detected Bias Types
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.