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 126-150 of 238 flagged pages
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.
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 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/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 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.
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 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.
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 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.
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 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.
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
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.
Network Watcher
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/network-watcher/packet-capture-manage.md
...main/articles/network-watcher/packet-capture-manage.md
High Priority
View Details →
Detected Bias Types
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.
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 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.
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
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'.
Network Watcher
Install the Azure Connected Machine agent for connection monitor
...-watcher/connection-monitor-connected-machine-agent.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias. Windows instructions and tools (PowerShell, Windows Admin Center) are presented first and in greater detail, with explicit mention of Windows-specific workflows. PowerShell is highlighted as a cross-platform tool, but Linux-specific alternatives (such as Bash scripts or CLI commands) are not discussed in equivalent detail. Windows Admin Center is featured as a management tool, while no Linux-native management tools are referenced.
Recommendations
- Alternate the order of Windows and Linux instructions, or present them side-by-side to avoid implicit prioritization.
- Provide Linux CLI or Bash-based automation examples equivalent to the PowerShell cmdlet workflow.
- Mention or link to Linux-native management tools (such as Cockpit or Ansible) for agent deployment, if supported.
- Clarify that PowerShell is available on Linux and macOS, and provide explicit Linux/macOS PowerShell usage examples.
- Add more detail to Linux installation steps, matching the depth of Windows instructions (e.g., prerequisites, troubleshooting, verification).
Network Watcher
Quickstart: Configure NSG flow logs using an ARM template
...ain/articles/network-watcher/nsg-flow-logs-template.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation exclusively uses Azure PowerShell for deployment instructions, with commands and file paths tailored to Windows environments. There are no CLI/bash examples or references to Linux/macOS workflows, and Windows-centric tooling is presented as the default approach.
Recommendations
- Add equivalent Azure CLI (az) examples for deploying ARM templates, which work cross-platform (Linux/macOS/Windows).
- Include bash shell examples and use generic file paths (e.g., ~/MyTemplates/azuredeploy.json) alongside Windows paths.
- Explicitly mention that Azure CLI and PowerShell are both supported, and link to cross-platform installation guides.
- Consider showing CLI/bash examples before or alongside PowerShell to avoid Windows-first bias.
Network Watcher
Troubleshoot and monitor VPN gateways - Azure Automation
...tcher/network-watcher-monitor-with-azure-automation.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation exclusively uses PowerShell for scripting and automation examples, with no mention of Bash, Azure CLI, or Linux/macOS alternatives. All code samples, naming conventions, and instructions assume a Windows/PowerShell environment, creating friction for users on Linux or macOS platforms.
Recommendations
- Provide equivalent examples using Azure CLI and/or Bash scripts for Linux/macOS users.
- Mention cross-platform options for Azure Automation runbooks, such as Python or Azure CLI runbook types.
- Clarify which steps are platform-agnostic (e.g., Azure portal navigation) and which are Windows/PowerShell-specific.
- Include guidance or links for Linux/macOS users to set up and use Azure Automation with non-PowerShell scripts.
Network Watcher
Troubleshoot outbound connections
...cles/network-watcher/connection-troubleshoot-manage.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation consistently uses Windows-centric terminology and examples, such as focusing on RDP (port 3389) for connectivity tests, which is specific to Windows. There is a lack of Linux/macOS-specific scenarios (e.g., SSH on port 22), and troubleshooting steps and solutions reference Windows patterns (like enabling RDP) without mentioning Linux equivalents. PowerShell is given as a primary automation example, with no Bash or Linux shell script alternatives. The documentation does not provide parity for Linux users in terms of troubleshooting OS-level connectivity (e.g., enabling SSH, checking Linux firewall rules).
Recommendations
- Add Linux/macOS-specific connectivity scenarios, such as testing SSH (port 22) between VMs.
- Include troubleshooting steps for Linux, such as enabling SSH, checking ufw/firewalld rules, and verifying SSH daemon status.
- Provide example commands for Linux shells (Bash) alongside PowerShell, especially for local execution.
- Clarify that the Azure CLI and PowerShell examples work on Linux/macOS, and provide explicit instructions for those platforms.
- When describing solutions, mention both Windows (RDP) and Linux (SSH) approaches for configuring the OS to accept connections.
- Use more neutral language in generic sections, e.g., 'remote access' instead of 'RDP', unless specifically discussing Windows.
Network Watcher
Check security rules using NSG diagnostics
...les/network-watcher/diagnose-network-security-rules.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation consistently uses Windows Server as the default VM image in all examples, both in the Azure Portal and CLI/PowerShell instructions. There are no examples or guidance for deploying or diagnosing Linux VMs, nor are Linux-specific considerations mentioned. The documentation also uses Windows-centric terminology and patterns (e.g., username/password for Windows, Windows image names), and does not provide parity for Linux users who may want to use SSH keys or Linux images.
Recommendations
- Include Linux VM creation examples in all sections, showing how to select a popular Linux image (e.g., Ubuntu) and use SSH keys for authentication.
- Add notes or tabs for Linux-specific steps, such as configuring SSH access and using Linux image references in CLI/PowerShell commands.
- Clarify that the NSG diagnostics process applies to both Windows and Linux VMs, and provide troubleshooting tips relevant to Linux scenarios.
- Ensure that CLI and PowerShell examples use generic or parameterized image names, or alternate between Windows and Linux images.
- Mention Linux-specific security group considerations, such as port 22 for SSH, in rule creation examples.
Network Watcher
Troubleshoot VPN gateways and connections - PowerShell
...rticles/network-watcher/vpn-troubleshoot-powershell.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation is heavily focused on PowerShell, with all examples and instructions using PowerShell cmdlets. There are no Azure CLI or Bash examples provided inline, and the prerequisites and workflow assume the use of PowerShell, which is more native to Windows. While Azure Cloud Shell can run PowerShell on any OS, the lack of parity with CLI/Bash examples creates friction for Linux/macOS users. References to Azure CLI are only found in the 'Related content' section, not in the main instructional flow.
Recommendations
- Provide equivalent Azure CLI (az) command examples alongside PowerShell in each section, ideally using tabbed code blocks for parity.
- Explicitly mention that Azure Cloud Shell supports both PowerShell and Bash, and clarify that users can choose their preferred shell.
- Adjust prerequisites to include both Azure PowerShell and Azure CLI as supported options.
- Ensure that links to CLI documentation are as prominent as those for PowerShell, not relegated to 'Related content'.
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows Error Codes
Summary
The documentation page shows moderate Windows bias. While it mentions that VPN troubleshoot can be called via Azure portal, PowerShell, CLI, or REST API, several sections and examples reference Windows-specific tools, error codes, and log formats. For example, troubleshooting logs include Windows error codes (e.g., ERROR_IPSEC_IKE_AUTH_FAIL), and log file paths use Windows-style notation. The guidance for downloading logs references Azure Storage Explorer (a cross-platform tool, but often associated with Windows) and does not mention Linux-native alternatives. The 'Considerations' section suggests using PowerShell or the portal as alternatives to CLI, which may imply a Windows-first approach. There are no explicit Linux/macOS command examples or troubleshooting patterns.
Recommendations
- Include Linux/macOS-specific troubleshooting examples, such as using Azure CLI on Linux.
- Reference Linux-native tools for downloading blobs (e.g., azcopy, curl, wget) alongside Storage Explorer.
- Clarify that log files and error codes may reference Windows terminology, but provide mapping or explanation for Linux users.
- Add explicit instructions or notes for Linux/macOS users where PowerShell is suggested.
- Use platform-neutral file path notation in examples, or provide both Windows and Linux formats.
Network Watcher
Managed Identity for Virtual Network Flow Logs
...les/network-watcher/vnet-flow-logs-managed-identity.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation exclusively uses Azure PowerShell cmdlets for all examples and instructions, with no mention of Azure CLI, Bash, or Linux-native tooling. Prerequisite links and instructions consistently reference PowerShell and do not provide Linux/macOS alternatives. This creates friction for users on Linux or macOS, who may prefer or require Azure CLI or Bash-based workflows.
Recommendations
- Add equivalent Azure CLI examples for all PowerShell cmdlets shown, using Bash syntax where appropriate.
- Update prerequisite links to include both PowerShell and Azure CLI/Bash instructions, ensuring parity for Linux/macOS users.
- Explicitly state that Azure Cloud Shell supports both Bash and PowerShell, and provide guidance for choosing the appropriate shell.
- Where possible, mention cross-platform tools first or side-by-side with Windows-specific tools.
Network Watcher
Filter Virtual Network Flow Logs (Preview)
...n/articles/network-watcher/vnet-flow-logs-filtering.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation exclusively uses Azure PowerShell cmdlets (New-AzNetworkWatcherFlowLog, Set-AzNetworkWatcherFlowLog, etc.) for all examples and instructions. There are no CLI (az), Bash, or Linux/macOS-specific examples or guidance. This creates friction for users on Linux or macOS who typically use the Azure CLI or REST API, and may not have PowerShell installed or prefer not to use it.
Recommendations
- Add equivalent Azure CLI (az network watcher flow-log ...) examples for all PowerShell cmdlet instructions.
- Include Bash script examples for Linux/macOS users.
- Mention REST API options for advanced users or automation.
- Clearly state at the beginning that PowerShell is used, and link to cross-platform installation guides if PowerShell is required.
- Consider presenting CLI and PowerShell examples side-by-side or alternating their order.
Network Watcher
Tutorial: Log network traffic
...in/articles/network-watcher/vnet-flow-logs-tutorial.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The tutorial demonstrates a notable Windows bias by exclusively using Windows Server as the VM image, guiding users to connect via RDP, and referencing Microsoft Edge for browsing. There are no instructions or examples for creating or connecting to Linux VMs, nor for using SSH or Linux-native tools. The workflow assumes Windows as the default platform for both VM creation and user interaction.
Recommendations
- Include parallel instructions for creating a Linux VM (e.g., Ubuntu) and connecting via SSH.
- Show how to open the downloaded flow log file using common Linux text editors (e.g., nano, vim, gedit) or command-line tools (e.g., cat, jq).
- Provide examples of accessing the VM and downloading logs from Linux/macOS clients, including use of Azure CLI and Storage Explorer on those platforms.
- Mention that the Azure portal and Storage Explorer are cross-platform, and clarify any platform-specific steps.
- When listing VM images, present both Windows and Linux options, or let the user choose.
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation page demonstrates moderate Windows bias. PowerShell is the only CLI tool shown for configuring NSG flow log properties (e.g., FlowTimeoutInMinutes), and the example references the Windows-centric Set-AzVirtualNetwork cmdlet. No equivalent Azure CLI (az network) or REST API example is provided for Linux/macOS users. Additionally, Power BI is listed before open-source visualization tools, and PowerShell-based reading of logs is highlighted before other methods.
Recommendations
- Add Azure CLI (az network) and REST API examples for all configuration tasks, especially for setting FlowTimeoutInMinutes.
- Include Linux/macOS-friendly instructions for reading and exporting NSG flow logs, such as using jq, az storage blob, or Python scripts.
- Present visualization options in a neutral order (e.g., list Power BI, Grafana, Elastic Stack, Graylog together, or alternate order).
- Reference cross-platform tools and workflows wherever possible, and avoid assuming PowerShell is the default.
- Explicitly state that all tasks can be performed from Linux/macOS and provide links or examples.
Network Watcher
Migrate to virtual network flow logs
...main/articles/network-watcher/nsg-flow-logs-migrate.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation exclusively provides migration instructions using a PowerShell script (.ps1), with no mention of Bash, Azure CLI, or Linux/macOS-specific alternatives. Prerequisites and usage steps focus on PowerShell, and all examples reference Windows-centric tooling. While PowerShell 7 is cross-platform, the lack of Linux/macOS-specific guidance or CLI alternatives may create friction for non-Windows users.
Recommendations
- Provide equivalent migration instructions using Azure CLI or Bash scripts, which are native to Linux/macOS environments.
- Explicitly document how to run the PowerShell script on Linux/macOS, including installation steps and troubleshooting tips for those platforms.
- Include example commands and screenshots from Linux/macOS terminals to demonstrate cross-platform support.
- Offer a downloadable Bash or Python migration script if feasible, or clarify any platform limitations.
Network Watcher
Visualizing Azure NSG flow logs - Power BI
...er/network-watcher-visualize-nsg-flow-logs-power-bi.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation is heavily focused on using Power BI Desktop, a Windows-centric tool, for visualizing Azure NSG flow logs. All instructions and examples assume the use of Power BI Desktop, with no mention of Linux/macOS alternatives or cross-platform BI tools. The setup steps and template are tailored for Power BI Desktop, which is not natively available on Linux or macOS. While there is a brief mention of open source tools (Elastic Stack) in the 'Next steps' section, the main content does not provide Linux/macOS parity or guidance.
Recommendations
- Provide equivalent instructions and templates for cross-platform BI tools such as Power BI Service (web), Grafana, or Kibana.
- Explicitly note platform requirements and limitations for Power BI Desktop, and suggest alternatives for Linux/macOS users.
- Include a parallel walkthrough using open source or web-based visualization tools, with sample queries and dashboards.
- Reorder or balance examples so that Linux/macOS options are presented alongside or before Windows-specific tools.
Network Watcher
Update Network Watcher extension to the latest version
...ticles/network-watcher/network-watcher-agent-update.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation provides both Linux and Windows examples for most Azure CLI operations, but heavily favors PowerShell scripting for automation and bulk operations, which is a Windows-centric tool. The only provided automation script is a PowerShell script, and there is no equivalent Bash or cross-platform script for Linux users. Additionally, PowerShell and Windows tools are often mentioned first or exclusively in sections about automation and manual update options.
Recommendations
- Provide equivalent Bash or shell scripts for Linux users to automate bulk extension updates, not just PowerShell.
- Where PowerShell is used, clarify if it is available cross-platform (e.g., PowerShell Core), or provide native Bash/CLI alternatives.
- Balance the order of examples so Linux and Windows are presented equally, or alternate which comes first.
- Highlight Azure CLI as the primary cross-platform tool for scripting and automation, and provide full examples for both OS types.
- Explicitly mention when a command or script is Windows-only, and offer guidance for Linux/macOS users.
Network Watcher
Manage Network Watcher Agent VM extension - Linux
...rticles/network-watcher/network-watcher-agent-linux.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation, while focused on Linux VMs, consistently presents PowerShell examples and instructions alongside Azure CLI and Portal, with PowerShell often described in detail and referenced as a primary tool for deployment and management. PowerShell (a Windows-centric tool) is given equal or greater prominence than Azure CLI, and instructions for deploying ARM templates mention PowerShell before CLI. There are no native Linux shell (bash, sh) or scripting examples, and no mention of Linux package managers or Linux-specific troubleshooting. The use of PowerShell and references to installing Azure PowerShell locally may create friction for Linux/macOS users who prefer native CLI or shell environments.
Recommendations
- Prioritize Azure CLI examples over PowerShell, or present CLI first, as CLI is cross-platform and native to Linux/macOS.
- Remove or minimize references to installing Azure PowerShell locally for Linux-focused documentation; instead, highlight Azure CLI installation and usage.
- Add bash/sh scripting examples for common tasks, such as installing or listing extensions, to improve accessibility for Linux users.
- Clarify that all management tasks can be performed via Azure CLI and Portal, and that PowerShell is optional.
- Include troubleshooting steps or tips specific to Linux environments.