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 201-225 of 238 flagged pages
Network Watcher
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/network-watcher/vm-network-troubleshooter.md
.../articles/network-watcher/vm-network-troubleshooter.md
Medium Priority
View Details →
Detected Bias Types
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)').
Create Pull Request
Network Watcher
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/network-watcher/diagnose-vm-network-routing-problem.md
...network-watcher/diagnose-vm-network-routing-problem.md
Medium Priority
View Details →
Detected Bias Types
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.
Network Watcher
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/network-watcher/connection-monitor-overview.md
...rticles/network-watcher/connection-monitor-overview.md
Medium Priority
View Details →
Detected Bias Types
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.
Network Watcher
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/network-watcher/connection-troubleshoot-manage.md
...cles/network-watcher/connection-troubleshoot-manage.md
Medium Priority
View Details →
Detected Bias Types
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.
Network Watcher
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/network-watcher/diagnose-network-security-rules.md
...les/network-watcher/diagnose-network-security-rules.md
Medium Priority
View Details →
Detected Bias Types
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.
Network Watcher
Connection monitor overview
...rticles/network-watcher/connection-monitor-overview.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page exhibits mild Windows bias. While it mentions both Windows and Linux support for agents and extensions, it references Windows-specific management documentation before Linux equivalents and lists Azure PowerShell as a primary automation method, with no explicit Linux CLI or shell examples. There is a lack of Linux-specific usage examples, and PowerShell is highlighted as an automation tool without parity for Bash or Linux-native tools. However, Linux support is acknowledged in agent installation and feature tables.
Recommendations
- Present Linux and Windows instructions/examples side by side or in parallel sections.
- Include explicit Bash/Azure CLI examples for automation and configuration, not just PowerShell.
- Reference Linux documentation links before or alongside Windows links, not after.
- Add troubleshooting and diagnostic examples relevant to Linux environments.
- Clarify that all features and agents are supported equally on Linux and Windows, with any exceptions noted.
Network Watcher
Install and upgrade Azure Monitor Agent on Azure Arc-enabled servers
...cher/connection-monitor-install-azure-monitor-agent.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides both Windows and Linux examples for all commands, but consistently presents Windows examples before Linux ones in each tabbed section. There are no missing Linux examples or exclusive use of Windows tools; parity is maintained in functionality and instructions.
Recommendations
- Alternate the order of Windows and Linux examples in tabbed sections, or present Linux examples first in some sections.
- Add a note at the beginning clarifying that all instructions are available for both Windows and Linux, to reassure non-Windows users.
- Consider grouping examples by OS or providing a combined example table for quick comparison.
Network Watcher
Enable or disable Azure Network Watcher
...ain/articles/network-watcher/network-watcher-create.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation exhibits mild Windows bias by consistently listing PowerShell examples and instructions before Azure CLI equivalents, and by referencing Windows-centric tools (PowerShell) more frequently. PowerShell is presented as a primary automation method, with additional details and links for installation and usage. While Azure CLI is included and parity is generally maintained, the ordering and emphasis may create friction for Linux/macOS users who prefer CLI or Bash.
Recommendations
- Alternate the order of PowerShell and Azure CLI examples, or present CLI first in some sections to balance visibility.
- Explicitly mention that Azure CLI is cross-platform and suitable for Linux/macOS users.
- Provide Bash shell snippets or notes where relevant, especially for local installation and usage.
- Reduce PowerShell-specific instructions unless necessary, and ensure CLI instructions are equally detailed.
- Clarify that both PowerShell and CLI can be used in Cloud Shell, which is OS-agnostic.
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Minor Windows Path Examples
Summary
The documentation provides examples and instructions for both Windows and Linux, but there is a consistent pattern of Windows-first presentation and a slight emphasis on Windows tools and conventions. PowerShell is featured prominently as a cross-platform tool, but examples and file paths often default to Windows formats before mentioning Linux equivalents. Download instructions and local file path examples use Windows paths as defaults, with Linux paths mentioned secondarily.
Recommendations
- Alternate the order of Windows and Linux examples to avoid consistently presenting Windows first.
- Provide Linux/macOS-specific examples and file paths before or alongside Windows examples, not as a secondary note.
- Explicitly mention Linux/macOS tools (e.g., curl, wget, scp) for downloading files, in addition to Azure CLI and PowerShell.
- Where file paths are shown, use neutral or both formats (e.g., '/var/captures/myVM_1.cap' and 'C:\Capture\myVM_1.cap') in parallel.
- Clarify that PowerShell and Azure CLI are cross-platform, and provide guidance for Linux/macOS users on installation and usage.
- Include screenshots or terminal output from Linux/macOS environments where possible.
Network Watcher
Connection monitor overview
...rticles/network-watcher/connection-monitor-overview.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation exhibits mild Windows bias, primarily by referencing Windows tools and PowerShell before Linux equivalents, and by linking to Windows extension management before Linux. Examples and instructions for automation mention PowerShell first, and Windows-centric terminology (such as 'Local Computer Trusted Certification Authorities store') is used in diagnostic sections. However, Linux support is explicitly mentioned throughout, and links to Linux-specific instructions are present.
Recommendations
- Present Linux and Windows instructions/examples side-by-side or in parallel, rather than listing Windows first.
- When referencing extension management, link to both Windows and Linux guides equally, or provide a combined section.
- Include Azure CLI and Bash examples alongside PowerShell, especially in automation sections.
- Avoid Windows-centric terminology in generic diagnostic sections; clarify Linux equivalents where needed.
- Explicitly call out Linux/macOS compatibility in agent and troubleshooting instructions.
Network Watcher
Install and upgrade Azure Monitor Agent on Azure Arc-enabled servers
...cher/connection-monitor-install-azure-monitor-agent.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides both Windows and Linux examples for all major commands, ensuring functional parity. However, in each code example section, the Windows tab is presented before the Linux tab, indicating a 'windows_first' ordering bias. No evidence of missing Linux examples, exclusive use of Windows tools, or PowerShell-heavy bias is found, as both platforms are equally supported in instructions and tooling.
Recommendations
- Alternate the order of tabs so that Linux examples are sometimes shown first, or present both tabs side-by-side to avoid implicit prioritization.
- Include a brief statement at the beginning clarifying that all instructions apply equally to both Windows and Linux, and that examples for both are provided.
- Consider adding macOS-specific notes if relevant, or clarify Linux instructions are applicable to macOS where appropriate.
Low Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Windows First
Summary
The documentation page demonstrates mild Windows bias. The only explicit CLI example for configuring NSG flow log timeout uses PowerShell (Set-AzVirtualNetwork), with no equivalent Azure CLI or REST API example for Linux/macOS users. References to tools like Power BI (Windows-centric) appear before open-source alternatives. The documentation does mention cross-platform visualization tools (Grafana, Elastic Stack, Graylog), but operational/configuration instructions are Windows-first.
Recommendations
- Provide Azure CLI and/or REST API examples alongside PowerShell for configuration tasks such as setting FlowTimeoutInMinutes.
- Explicitly mention that all log file formats and storage paths are OS-agnostic.
- When listing visualization options, alternate or randomize the order so open-source/cross-platform tools are not always listed after Windows tools.
- Add troubleshooting and operational examples using Bash/Azure CLI for Linux/macOS users.
- Where PowerShell is referenced, add a note or link to equivalent Azure CLI documentation.
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Minor Path Bias
Summary
The documentation provides examples for both Windows and Linux, but there is a subtle Windows bias. Windows file paths (e.g., C:\Capture\myVM_1.cap) are shown first in examples and tables, and PowerShell is presented as a primary automation tool, which is more native to Windows. References to Azure PowerShell and Storage Explorer (a Windows-centric tool) are prominent. Linux paths are mentioned, but typically as a secondary note. There are no Linux/macOS-specific command-line examples (e.g., bash, scp), and local file download examples use Windows paths by default.
Recommendations
- Alternate the order of Windows and Linux examples in tables and code blocks, or present both side-by-side.
- Include explicit Linux/macOS shell command examples for downloading files (e.g., using curl, wget, or scp).
- Show Linux file paths first in at least some examples, or clarify parity.
- Mention cross-platform tools (e.g., Storage Explorer for macOS/Linux, azcopy) and provide download instructions for all OSes.
- Clarify that PowerShell is available on Linux/macOS, or provide bash equivalents where possible.
Network Watcher
Audit and deploy virtual network flow logs using Azure Policy
...main/articles/network-watcher/vnet-flow-logs-policy.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation exclusively uses the Azure portal UI for all instructions and examples, without providing any command-line alternatives. There are no examples using Windows-specific tools (such as PowerShell), but there is also a lack of parity for Linux users, as no CLI (Azure CLI, Bash, etc.) instructions are provided. This omission can be considered a bias of missing Linux example, as many Linux administrators prefer or require command-line automation and scripting.
Recommendations
- Add equivalent instructions for auditing and deploying virtual network flow logs using Azure CLI commands, which are cross-platform and widely used by Linux users.
- Include sample scripts for both Bash and PowerShell to demonstrate policy assignment and compliance checking.
- Explicitly mention that all steps can be performed via Azure CLI or REST API, and link to relevant documentation.
- Provide a comparison table or section showing how to perform these tasks using the portal, Azure CLI, PowerShell, and REST API, to ensure parity and inclusivity for all platforms.
Network Watcher
Effective security rules overview
...s/network-watcher/effective-security-rules-overview.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation does not provide any platform-specific examples or instructions, but it does reference the Azure portal exclusively for viewing and downloading effective security rules. There are no examples or guidance for accessing or managing effective security rules via command-line tools, such as PowerShell (Windows) or Bash/Azure CLI (Linux). This omission results in a subtle bias: Linux users who prefer CLI workflows are not supported, while Windows users may be more accustomed to GUI-based Azure portal usage.
Recommendations
- Add examples for accessing effective security rules using Azure CLI (cross-platform, Linux-friendly).
- Include PowerShell examples if relevant, but ensure Azure CLI instructions are presented with equal prominence.
- Provide guidance on downloading and parsing security rules via command-line tools, not just through the Azure portal.
- Explicitly mention that the Azure portal is platform-agnostic, but offer alternatives for users who prefer CLI or automation.
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation references both Windows and Linux for the Network Watcher agent VM extension, but lists the Windows link before the Linux link. No examples or instructions are provided for either platform, but the ordering suggests a subtle Windows-first bias. There are no PowerShell-heavy examples, exclusive mention of Windows tools, or missing Linux examples in this overview.
Recommendations
- List Windows and Linux resources in alphabetical order or together to avoid perceived prioritization.
- Ensure that future examples and walkthroughs provide parity between Windows (e.g., PowerShell) and Linux (e.g., Bash/CLI) usage.
- Explicitly state that both Windows and Linux are supported and provide links to platform-specific documentation side by side.
Network Watcher
Diagnose on-premises VPN connectivity with Azure
...r/network-watcher-diagnose-on-premises-connectivity.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation page provides instructions for diagnosing VPN connectivity using Azure Network Watcher, but all examples and tool usage are described via the Azure Portal UI. There are no command-line examples, and notably, there is no mention of Linux-specific tools, CLI commands, or troubleshooting patterns. The absence of PowerShell or Windows-specific tools avoids overt Windows bias, but the lack of Linux parity (e.g., Azure CLI, Bash, or Linux troubleshooting steps) constitutes a subtle bias by omission.
Recommendations
- Add Azure CLI examples for running VPN troubleshoot operations, including commands for initiating diagnostics and downloading logs.
- Include instructions for accessing and analyzing diagnostic logs on Linux systems (e.g., using curl, unzip, grep).
- Mention Linux-compatible VPN devices and troubleshooting patterns where relevant.
- Ensure screenshots or UI instructions are supplemented with equivalent CLI steps for cross-platform accessibility.
Network Watcher
Audit and deploy virtual network flow logs using Azure Policy
...main/articles/network-watcher/vnet-flow-logs-policy.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation exclusively uses the Azure portal UI for all instructions and examples, without providing any command-line alternatives. There are no examples using Windows-specific tools (such as PowerShell), but there is also a lack of parity for Linux users, as no CLI (Azure CLI, Bash, etc.) instructions are given. This omission can disadvantage users who prefer or require command-line automation, especially on Linux or cross-platform environments.
Recommendations
- Add Azure CLI examples for all major steps (policy assignment, compliance checking, remediation) alongside portal instructions.
- Include sample Bash scripts for common tasks, such as auditing and deploying flow logs.
- Explicitly mention that all steps can be performed via CLI and provide links to relevant CLI documentation.
- Ensure screenshots or UI references are supplemented with equivalent command-line output examples.
- If PowerShell is relevant, provide both PowerShell and Bash/Azure CLI examples, but do not prioritize Windows tools over cross-platform alternatives.
Network Watcher
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/network-watcher/effective-security-rules-overview.md
...s/network-watcher/effective-security-rules-overview.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation page describes the Azure Network Watcher effective security rules feature but does not provide any platform-specific examples or instructions. However, it references the Azure portal UI exclusively and does not mention command-line or automation options, such as PowerShell, Azure CLI, or REST API. There is no evidence of explicit Windows bias (e.g., PowerShell-heavy examples or Windows tools), but the absence of Linux/Azure CLI examples or mention of cross-platform automation options constitutes a 'missing_linux_example' bias.
Recommendations
- Add instructions or examples for accessing effective security rules using Azure CLI, which is cross-platform and commonly used on Linux.
- Include REST API references or examples for programmatic access, ensuring parity for automation on both Windows and Linux.
- If PowerShell examples are added in future revisions, ensure Azure CLI equivalents are provided alongside.
- Explicitly mention that the feature is accessible via cross-platform tools, not just the Azure portal.
Network Watcher
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/network-watcher/network-watcher-diagnose-on-premises-connectivity.md
...r/network-watcher-diagnose-on-premises-connectivity.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation provides instructions for diagnosing on-premises VPN connectivity with Azure using Network Watcher, but it does not include any platform-specific examples or references. However, it lacks any mention of Linux-specific troubleshooting steps, tools, or log analysis patterns, and does not address how administrators using Linux systems might interact with the diagnostic logs or automate troubleshooting outside the Azure portal.
Recommendations
- Add examples of how to download and analyze the diagnostic log files using Linux command-line tools (e.g., curl, wget, unzip, grep, less).
- Include instructions for automating VPN troubleshooting via Azure CLI or REST API, with sample commands for Linux environments.
- Mention common Linux VPN devices and provide troubleshooting tips or references for those platforms.
- Ensure that log file analysis steps are platform-agnostic or provide parallel instructions for both Windows and Linux users.
Network Watcher
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/network-watcher/packet-capture-overview.md
...in/articles/network-watcher/packet-capture-overview.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation mentions both Windows and Linux extensions for the Network Watcher agent, but lists the Windows extension first. There are no usage examples provided for either platform, but the ordering in the 'IMPORTANT' note prioritizes Windows over Linux, which can subtly reinforce a Windows-first perspective.
Recommendations
- List Windows and Linux extension documentation links in alphabetical order or together to avoid perceived prioritization.
- Ensure future documentation includes usage examples for both Windows (PowerShell, CMD) and Linux (Bash, CLI) platforms.
- Explicitly state parity of features and support between Windows and Linux where applicable.
- Add a section comparing platform-specific considerations, if any, to help users on both OSes.
Network Watcher
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/network-watcher/vnet-flow-logs-policy.md
...main/articles/network-watcher/vnet-flow-logs-policy.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation exclusively uses Azure Portal GUI instructions and screenshots, with no command-line examples provided. There is no mention of Windows-specific tools (such as PowerShell), but the lack of CLI examples means Linux users (who often prefer Bash/CLI) are underserved. There is no evidence of explicit Windows bias, but the absence of Azure CLI or REST API instructions represents a bias toward GUI workflows, which are more common among Windows users.
Recommendations
- Add equivalent Azure CLI examples for all major steps (policy assignment, compliance checking, remediation) to support Linux and cross-platform users.
- Include REST API sample requests for advanced automation and platform neutrality.
- Explicitly mention that all operations can be performed via CLI or API, and link to relevant documentation.
- Where screenshots are used, consider adding terminal output examples for parity.
Network Watcher
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/network-watcher/packet-capture-overview.md
...in/articles/network-watcher/packet-capture-overview.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation references both Windows and Linux for the Network Watcher agent VM extension, but lists the Windows link before the Linux link. There are no usage examples provided for either platform, and no evidence of PowerShell-heavy or Windows-only tools/patterns. However, the ordering of references suggests a subtle Windows-first bias.
Recommendations
- List Windows and Linux resources in alphabetical order or alternate their ordering to avoid implicit prioritization.
- Provide explicit usage examples for both Windows (e.g., PowerShell) and Linux (e.g., Bash/CLI) to ensure parity.
- Mention platform-agnostic tools and commands first, or group platform-specific instructions clearly and equally.
Network Watcher
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/network-watcher/effective-security-rules-overview.md
...s/network-watcher/effective-security-rules-overview.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation page describes the Azure Network Watcher effective security rules feature but does not provide any platform-specific examples or instructions. However, it omits any mention of how to access or interact with this feature using Linux tools, CLI, or scripting environments, focusing solely on the Azure portal UI. There is no evidence of Windows-specific bias (such as Powershell examples or Windows tools), but the lack of Linux parity is notable.
Recommendations
- Add examples showing how to retrieve effective security rules using Azure CLI commands, which are cross-platform and commonly used on Linux.
- Include instructions or references for using Bash scripts to automate compliance audits, alongside any PowerShell examples if added.
- Explicitly mention that the feature is accessible from any OS via the Azure portal and CLI, and provide links to CLI documentation.
- If downloadable CSV files are referenced, suggest tools for viewing/manipulating CSVs on Linux (e.g., csvkit, awk).
Network Watcher
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/network-watcher/vnet-flow-logs-policy.md
...main/articles/network-watcher/vnet-flow-logs-policy.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation exclusively uses Azure Portal UI instructions and screenshots, without providing any command-line examples. There is no mention of Windows-specific tools (e.g., PowerShell), but there is also a lack of CLI-based instructions (such as Azure CLI or Bash), which are commonly used on Linux and cross-platform environments. This omission creates a bias by not supporting Linux or automation-focused users who may prefer or require command-line approaches.
Recommendations
- Add equivalent instructions using Azure CLI commands for auditing and deploying virtual network flow logs.
- Include Bash script examples for common tasks, such as assigning policies and checking compliance.
- Explicitly mention that these CLI instructions work on Linux, macOS, and Windows to ensure cross-platform parity.
- Provide links to Azure CLI documentation and reference pages for policy management.
- Consider adding a section comparing portal and CLI approaches, highlighting use cases for each.