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 226-238 of 238 flagged pages
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 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.
Create Pull Request
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 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.
Network Watcher
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/network-watcher/ip-flow-verify-overview.md
...in/articles/network-watcher/ip-flow-verify-overview.md
Low Priority
View Details →
Detected Bias Types
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.
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 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.
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 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.
Network Watcher
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/network-watcher/nsg-flow-logs-policy-portal.md
...rticles/network-watcher/nsg-flow-logs-policy-portal.md
Low Priority
View Details →
Detected Bias Types
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.
Network Watcher
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/network-watcher/traffic-analytics-policy-portal.md
...les/network-watcher/traffic-analytics-policy-portal.md
Low Priority
View Details →
Detected Bias Types
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.
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 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.
Network Watcher
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/network-watcher/ip-flow-verify-overview.md
...in/articles/network-watcher/ip-flow-verify-overview.md
Low Priority
View Details →
Detected Bias Types
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.
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 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.
Network Watcher
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/network-watcher/traffic-analytics-policy-portal.md
...les/network-watcher/traffic-analytics-policy-portal.md
Low Priority
View Details →
Detected Bias Types
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).
Network Watcher
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/network-watcher/nsg-flow-logs-policy-portal.md
...rticles/network-watcher/nsg-flow-logs-policy-portal.md
Low Priority
View Details →
Detected Bias Types
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.
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 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.