Network Watcher

126
Total Pages
102
Linux-Friendly Pages
24
Pages with Bias
19.0%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

50 issues found
Showing 1-25 of 50 flagged pages
Network Watcher Visualizing Azure NSG flow logs - Power BI ...er/network-watcher-visualize-nsg-flow-logs-power-bi.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation exclusively focuses 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. There are no examples or guidance for users on non-Windows platforms, and the workflow is presented as universally applicable without noting platform limitations.
Recommendations
  • Explicitly state that Power BI Desktop is only available for Windows and note platform limitations.
  • Provide alternative instructions or links for Linux/macOS users, such as using Power BI Service (web), or open-source BI tools (e.g., Grafana, Kibana, Apache Superset).
  • Include a parallel example or workflow for visualizing NSG flow logs on Linux/macOS, possibly referencing the 'Elastic Stack' documentation linked in 'Next steps'.
  • Reorder or clarify the documentation to avoid implying that the Power BI Desktop workflow is the only or primary solution.
GitHub Create Pull Request
Network Watcher Use packet capture to proactively monitor your network ...cles/network-watcher/packet-capture-alert-triggered.md
High Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation is heavily biased towards Windows and PowerShell. All code samples, authentication steps, and automation instructions use PowerShell, with no equivalent Bash, CLI, or Python examples for Linux/macOS users. The prerequisites and workflow mention both Windows and Linux VM extensions, but all actionable steps and scripts are Windows/PowerShell-centric. There is no guidance for Linux-native automation, and Windows tools and file paths are referenced throughout.
Recommendations
  • Provide equivalent examples using Azure CLI, Bash, or Python for Linux/macOS users, especially for authentication and packet capture automation.
  • Include instructions for creating and running Azure Functions using non-PowerShell runtimes (e.g., Python, Node.js) and show how to interact with Network Watcher from those environments.
  • Offer sample scripts for Linux environments, including key generation and credential management using Linux tools.
  • Reference Linux file paths and tools where appropriate, and avoid assuming Windows-only paths (e.g., C:\temp).
  • Clarify which steps are OS-agnostic and which require adaptation for Linux/macOS.
GitHub Create Pull Request
Network Watcher Filter Virtual Network Flow Logs (Preview) ...n/articles/network-watcher/vnet-flow-logs-filtering.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 3 bias types
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, with no mention of Azure CLI, REST API, or other cross-platform tools. This creates friction for Linux/macOS users who may prefer or require non-PowerShell workflows.
Recommendations
  • Add equivalent Azure CLI examples for all PowerShell cmdlet instructions.
  • Reference REST API documentation for programmatic access from any platform.
  • Explicitly state that PowerShell cmdlets can be run on Linux/macOS via PowerShell Core, but provide native CLI alternatives.
  • Consider reordering or balancing examples so CLI and PowerShell are presented side-by-side.
GitHub Create Pull Request
Network Watcher Managed Identity for Virtual Network Flow Logs ...les/network-watcher/vnet-flow-logs-managed-identity.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation exclusively uses Azure PowerShell cmdlets for all examples and setup instructions, with no mention of Azure CLI, Bash, or Linux-native workflows. Prerequisites and links consistently reference PowerShell, and there are no Linux/macOS-specific instructions or examples. This creates friction for users on non-Windows platforms who may prefer or require Bash/Azure CLI.
Recommendations
  • Provide equivalent Azure CLI examples for all PowerShell cmdlets shown.
  • Update prerequisite links to include both PowerShell and Azure CLI/Bash instructions.
  • Clarify that Azure Cloud Shell supports both Bash and PowerShell, and show how to select Bash.
  • Add notes or sections for Linux/macOS users, including installation and usage guidance for Azure CLI.
  • Ensure that all critical workflows can be completed using Azure CLI/Bash, not just PowerShell.
GitHub Create Pull Request
Network Watcher Troubleshoot outbound connections ...cles/network-watcher/connection-troubleshoot-manage.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation consistently uses Windows-centric examples, specifically RDP (port 3389) for connectivity tests, and references Windows-specific protocols and troubleshooting scenarios. There are no Linux/macOS-specific examples (e.g., SSH on port 22), nor any mention of Linux tools or troubleshooting patterns. This creates a subtle but notable bias toward Windows environments.
Recommendations
  • Include Linux/macOS scenarios, such as testing SSH connectivity (port 22) between VMs.
  • Add troubleshooting steps and example outputs for Linux guest firewalls (e.g., iptables, ufw) and SSH listeners.
  • Clarify that the connection troubleshoot feature works for any TCP/ICMP port, and provide examples for Linux services.
  • Balance the documentation by alternating Windows and Linux examples, or presenting both side-by-side.
  • Explicitly mention that the Azure CLI and PowerShell tools are cross-platform, and provide guidance for Linux/macOS users where appropriate.
GitHub Create Pull Request
Network Watcher Install the Azure Connected Machine agent for connection monitor ...-watcher/connection-monitor-connected-machine-agent.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. Windows instructions and tools (PowerShell, Windows Admin Center) are mentioned first or exclusively in several sections, with more detailed steps and tool integrations for Windows. Linux instructions are present but less detailed, and Linux-specific automation (e.g., Bash scripting, Linux package managers) is not covered. PowerShell is promoted as a cross-platform solution, but examples and linked resources focus on Windows-centric workflows.
Recommendations
  • Provide Linux examples and instructions with equal detail and prominence as Windows, including automation via Bash scripts and Linux-native tools.
  • Include Linux-first or side-by-side examples, rather than listing Windows instructions first.
  • Mention and link to Linux package manager installation methods (e.g., apt, yum) for the agent.
  • Highlight cross-platform PowerShell usage for Linux, or provide alternative Linux-native automation approaches.
  • Add parity for Linux in tool integrations (e.g., mention Azure CLI or Ansible for Linux environments).
GitHub Create Pull Request
Network Watcher Check security rules using NSG diagnostics ...les/network-watcher/diagnose-network-security-rules.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation consistently uses Windows Server as the example operating system for the virtual machine, both in the Azure Portal and CLI/PowerShell instructions. There are no examples or instructions for creating or managing a Linux VM, nor any mention of Linux-specific considerations. All command-line examples use Azure CLI and PowerShell, which are cross-platform, but the VM image and admin account setup are Windows-only. This creates friction for Linux users who wish to follow the guide with a Linux VM.
Recommendations
  • Provide parallel examples for creating a Linux VM (e.g., Ubuntu) in the Portal, PowerShell, and Azure CLI sections.
  • Mention that the steps are applicable to both Windows and Linux VMs, and clarify any differences in setup (e.g., SSH keys for Linux vs. passwords for Windows).
  • Include sample commands for Linux VM creation, such as using '--image UbuntuLTS' in Azure CLI and the equivalent in PowerShell.
  • Add notes or links to Linux VM documentation for users who prefer Linux.
  • Ensure screenshots and walkthroughs do not imply Windows is the only supported or recommended OS.
GitHub Create Pull Request
Network Watcher Diagnose a VM network routing problem - Azure PowerShell ...cher/diagnose-vm-network-routing-problem-powershell.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation exclusively uses Azure PowerShell cmdlets and examples, with no mention of Azure CLI, Bash, or Linux/macOS-specific instructions. All code samples and workflow descriptions assume PowerShell usage, which is native to Windows and less common on Linux/macOS. There is no guidance for users who prefer or require Linux-native tools or shell environments.
Recommendations
  • Add equivalent Azure CLI examples for all major steps (resource group creation, VM creation, Network Watcher operations, cleanup).
  • Explicitly mention that Azure Cloud Shell supports both Bash and PowerShell, and provide instructions for selecting Bash.
  • Include notes or links for Linux/macOS users on installing and using Azure CLI.
  • Reorder or parallelize examples so that Linux/Bash instructions are presented alongside or before Windows/PowerShell ones.
GitHub Create Pull Request
Network Watcher Tutorial: Diagnose a VM network routing problem - Azure portal ...network-watcher/diagnose-vm-network-routing-problem.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The tutorial exclusively uses Windows Server as the VM image and provides only RDP-based connection instructions, with no mention of Linux VM creation, SSH access, or Linux-specific steps. All examples and screenshots are Windows-centric, and Linux/macOS users are not shown how to complete the tasks using their preferred OS.
Recommendations
  • Add parallel instructions for creating a Linux VM (e.g., Ubuntu), including SSH access setup and connection steps.
  • Provide screenshots and examples for both Windows and Linux VM scenarios.
  • Explicitly mention that the tutorial works for both Windows and Linux VMs, and clarify OS-specific differences where relevant.
  • Include a table or section comparing RDP (Windows) and SSH (Linux/macOS) access methods.
  • Reference the Azure CLI tutorial more prominently as a cross-platform alternative.
GitHub Create Pull Request
Network Watcher Quickstart: Diagnose a VM traffic filter problem - Azure PowerShell ...agnose-vm-network-traffic-filtering-problem-powershell.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation exclusively uses Azure PowerShell cmdlets for all steps, with no mention or examples of Azure CLI, Bash, or Linux-native tooling. The prerequisites and instructions assume PowerShell usage, which is more familiar to Windows users. There are no Linux/macOS-specific instructions, nor are alternative command-line interfaces presented.
Recommendations
  • Add equivalent Azure CLI (az) commands for each PowerShell example, as Azure CLI is cross-platform and preferred by many Linux/macOS users.
  • Update the prerequisites to mention both Azure PowerShell and Azure CLI, with links to installation guides for both.
  • Clarify that Azure Cloud Shell supports both Bash and PowerShell, and provide instructions for running the steps in Bash.
  • Where possible, provide Bash script examples alongside PowerShell, especially for resource creation and querying.
  • Reorder examples so that cross-platform tools (Azure CLI) are presented first or side-by-side with PowerShell.
GitHub Create Pull Request
Network Watcher Migrate to Connection monitor from Network performance monitor ...to-connection-monitor-from-network-performance-monitor.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits minor Windows bias, primarily in its references to Windows-specific tooling and extensions. For example, it instructs users to replace Log Analytics agents on Azure virtual machines with the Network Watcher extension, linking specifically to a Windows-focused agent installation guide. There are no explicit Linux migration instructions or examples, and Linux agent installation or troubleshooting is not covered. While the feature comparison table does mention Linux support, actionable migration steps and troubleshooting are Windows-centric.
Recommendations
  • Add explicit instructions and links for installing and configuring the Network Watcher extension on Linux VMs.
  • Include troubleshooting steps and common errors specific to Linux environments.
  • Ensure parity in agent migration guidance for both Windows and Linux, possibly with a dedicated section for Linux users.
  • Reference Linux documentation pages where appropriate, not just Windows-focused ones.
GitHub Create Pull Request
Network Watcher Manage Network Watcher Agent VM extension - Linux ...rticles/network-watcher/network-watcher-agent-linux.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
While the documentation is focused on managing the Network Watcher Agent extension for Linux VMs, it consistently presents PowerShell (a Windows-centric tool) as a primary management interface, with detailed instructions and references to installing Azure PowerShell locally. The use of PowerShell is emphasized alongside Azure CLI, but PowerShell is often listed first, and its usage is described in more detail. There are also references to Windows-style tooling and patterns (e.g., PowerShell cmdlets, Cloud Shell), which may create friction for Linux users who typically prefer Bash or native Linux tools.
Recommendations
  • Present Azure CLI examples before PowerShell examples, as CLI is more native to Linux environments.
  • Reduce emphasis on PowerShell and Windows tooling in Linux-focused documentation. Where PowerShell is mentioned, clarify that Azure CLI is the recommended approach for Linux users.
  • Add Bash script examples for common tasks, especially for installation and management steps.
  • Highlight that Azure CLI can be installed natively on Linux and macOS, and provide links to Bash shell usage.
  • Review and update instructions to avoid assuming users have access to PowerShell or Windows tools.
GitHub Create Pull Request
Network Watcher NSG Flow Logs Overview ...ain/articles/network-watcher/nsg-flow-logs-overview.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation page for NSG Flow Logs Overview demonstrates a moderate Windows bias. The only explicit command-line example for configuring flow timeout uses Azure PowerShell (Windows-centric), and references to PowerShell functions are given before any mention of Linux or cross-platform CLI alternatives. There is no mention of Azure CLI or Bash examples for Linux/macOS users, nor are Linux-specific tools or workflows highlighted. Visualization and export tools are platform-neutral, but the operational/configuration instructions are Windows-first.
Recommendations
  • Provide Azure CLI examples alongside or before PowerShell examples for all configuration tasks, especially for setting properties like FlowTimeoutInMinutes.
  • Explicitly mention that Azure CLI and Bash can be used on Linux/macOS for managing NSG flow logs, with links to relevant documentation.
  • Include sample scripts or commands for reading, exporting, and managing flow logs using Linux-native tools (e.g., jq, curl, az CLI).
  • Ensure that references to PowerShell are balanced with cross-platform alternatives in all 'How-to' sections.
  • Add a note clarifying that all features and workflows are available on Linux/macOS, and highlight any platform-specific caveats if they exist.
GitHub Create Pull Request
Network Watcher Update Network Watcher extension to the latest version ...ticles/network-watcher/network-watcher-agent-update.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation demonstrates a moderate Windows bias, primarily through the extensive use of PowerShell for automation and bulk update scenarios, with no equivalent Bash or shell script for Linux users. The bulk update example is Windows-centric, and PowerShell is presented as the main automation tool, even though Azure CLI is cross-platform. In several sections, Windows examples or tools are mentioned first or exclusively, and PowerShell is used for both Windows and Linux VM management, which may not be ideal for Linux administrators.
Recommendations
  • Provide a Bash or shell script example for bulk updating the Network Watcher extension on Linux VMs, using Azure CLI.
  • Ensure that automation and scripting examples are presented for both Windows (PowerShell) and Linux (Bash/Azure CLI), or use Azure CLI as the primary cross-platform tool.
  • When listing manual update commands, alternate the order or present Linux and Windows examples side-by-side, rather than Windows-first.
  • Clarify which commands are platform-agnostic and which require a specific OS or shell.
  • Add a section or note on using Azure CLI in automation scenarios for Linux/macOS users.
GitHub Create Pull Request
Network Watcher Troubleshoot and monitor VPN gateways - Azure Automation ...tcher/network-watcher-monitor-with-azure-automation.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
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 cross-platform alternatives. All code samples and naming conventions are PowerShell-centric, and the workflow assumes familiarity with Windows tooling. There is no guidance for Linux/macOS users or for using non-Windows shells.
Recommendations
  • Provide equivalent examples using Azure CLI and Bash scripts for Linux/macOS users.
  • Mention that Azure Automation supports Python runbooks and provide a sample.
  • Clarify which steps are platform-agnostic (e.g., portal navigation) and which are Windows-specific.
  • Add a section discussing cross-platform automation options and their limitations.
  • List prerequisites for Linux/macOS users, such as installing Azure CLI or Python modules.
GitHub Create Pull Request
Network Watcher Migrate to virtual network flow logs ...main/articles/network-watcher/nsg-flow-logs-migrate.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation exclusively provides a PowerShell script (.ps1) for migration, with all instructions and examples focused on running PowerShell. There are no Bash, CLI, or Linux/macOS-specific script alternatives or usage examples. The prerequisites and workflow assume PowerShell is the only supported method, which may create friction for Linux/macOS users who prefer Bash or Azure CLI.
Recommendations
  • Provide equivalent migration scripts or instructions using Bash or Azure CLI to support Linux/macOS users.
  • Include explicit examples for running the migration on Linux and macOS, such as using pwsh (PowerShell Core) or alternative shell commands.
  • Clarify whether the PowerShell script is compatible with PowerShell Core on Linux/macOS, and provide troubleshooting tips for non-Windows environments.
  • List Azure CLI as an alternative where possible, or explain why PowerShell is required.
  • Reorder prerequisites to mention cross-platform compatibility first, and avoid implying Windows as the default platform.
GitHub Create Pull Request
Network Watcher Quickstart: Configure NSG flow logs using an ARM template ...ain/articles/network-watcher/nsg-flow-logs-template.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation exclusively provides Azure PowerShell examples for deploying ARM templates, with no mention of cross-platform alternatives such as Azure CLI, Bash, or Linux/macOS-specific instructions. Windows file paths are used in examples, and PowerShell is assumed as the default environment, creating friction for Linux and macOS users who may prefer or require other tools.
Recommendations
  • Add equivalent Azure CLI examples for deploying ARM templates, showing commands that work natively on Linux/macOS.
  • Include Bash shell instructions and use cross-platform file paths (e.g., ~/MyTemplates/azuredeploy.json) in examples.
  • Explicitly mention that Azure PowerShell is available on Linux/macOS, or link to installation instructions for those platforms.
  • Present CLI and PowerShell examples side-by-side, or clarify which steps are platform-specific.
  • Add a note at the beginning indicating that both PowerShell and CLI can be used, with links to relevant documentation.
GitHub Create Pull Request
Network Watcher Use packet capture to proactively monitor your network ...cles/network-watcher/packet-capture-alert-triggered.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation is heavily biased towards Windows and PowerShell. All code samples and authentication instructions use PowerShell, with no equivalent Bash, CLI, or Python examples for Linux/macOS users. The prerequisites and workflow mention both Windows and Linux VM extensions, but all automation and scripting guidance is Windows-centric. This creates friction for Linux/macOS users who may not have PowerShell installed or prefer native tools.
Recommendations
  • Provide equivalent examples using Azure CLI, Bash, or Python for Linux/macOS users.
  • Explicitly document how to perform authentication and environment variable setup on Linux/macOS, including key generation and encryption using OpenSSL or other native tools.
  • Include guidance for installing and using PowerShell Core on Linux/macOS if PowerShell is required.
  • Reorder examples or provide parallel sections for Windows and Linux/macOS, rather than presenting Windows/PowerShell first and exclusively.
  • Mention and link to Linux-native packet capture tools (e.g., tcpdump) where relevant, and clarify how Azure Network Watcher interacts with Linux VMs.
GitHub Create Pull Request
Network Watcher Filter Virtual Network Flow Logs (Preview) ...n/articles/network-watcher/vnet-flow-logs-filtering.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation exclusively uses Azure PowerShell cmdlets for all examples and instructions, with no mention of Azure CLI, Bash, or cross-platform alternatives. This creates a strong Windows bias, as PowerShell is natively available only on Windows and less commonly used on Linux/macOS. There are no Linux/macOS-specific instructions or examples, and no guidance for users who prefer or require CLI/Bash workflows.
Recommendations
  • Add equivalent Azure CLI (az network watcher flow-log ...) examples for all PowerShell cmdlets shown.
  • Explicitly mention that PowerShell Core is available cross-platform, but provide Bash/Azure CLI examples for Linux/macOS users.
  • Include a section comparing PowerShell and CLI usage, and link to installation guides for both tools on all platforms.
  • Ensure that Linux/macOS users can follow the documentation without needing to install PowerShell unless they choose to.
GitHub Create Pull Request
Network Watcher Managed Identity for Virtual Network Flow Logs ...les/network-watcher/vnet-flow-logs-managed-identity.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
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/macOS-specific workflows. Prerequisites and guidance focus on PowerShell and Cloud Shell, which, while cross-platform, are presented in a way that assumes familiarity with Windows tooling. There are no Linux-native or Azure CLI examples, and all referenced tabs and links default to PowerShell, creating friction for Linux/macOS users who may prefer or require CLI or Bash-based workflows.
Recommendations
  • Add equivalent Azure CLI examples for all PowerShell cmdlets shown, using Bash syntax.
  • Update prerequisite links to include both PowerShell and Azure CLI tabs, ensuring parity.
  • Clarify that Azure Cloud Shell supports both Bash and PowerShell, and provide instructions for both.
  • Explicitly mention that all operations can be performed from Linux/macOS using Azure CLI, and provide guidance.
  • Consider reordering examples or providing side-by-side PowerShell and CLI/Bash instructions.
GitHub Create Pull Request
Network Watcher Tutorial: Log network traffic ...in/articles/network-watcher/vnet-flow-logs-tutorial.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The tutorial exhibits a Windows bias by exclusively using a Windows Server VM image, guiding users to connect via RDP, and referencing Microsoft Edge for traffic generation. There are no instructions or examples for deploying a Linux VM, connecting via SSH, or generating network traffic from Linux/macOS environments. Windows tools and patterns (RDP, Edge) are mentioned without Linux/macOS equivalents.
Recommendations
  • Add instructions for creating a Linux VM (e.g., Ubuntu) alongside the Windows VM steps.
  • Provide SSH connection steps for Linux/macOS users, including how to open a terminal and connect to the VM.
  • Include examples of generating outbound traffic from a Linux VM (e.g., using curl or wget).
  • Mention Linux/macOS text editors for viewing the downloaded JSON file (e.g., nano, vim, VS Code).
  • Clarify that the tutorial applies to both Windows and Linux VMs, and highlight any differences in network traffic logging or access patterns.
GitHub Create Pull Request
Network Watcher VPN troubleshoot overview .../articles/network-watcher/vpn-troubleshoot-overview.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows Error Codes
Summary
The documentation page shows moderate Windows bias, mainly through references to PowerShell as a workaround for Azure CLI limitations, mentions of Windows-specific error codes in log files, and log file examples that reference Windows paths and terminology. There are no explicit Linux/macOS command examples or troubleshooting patterns, and Windows tools are mentioned as alternatives before cross-platform solutions.
Recommendations
  • Provide explicit Linux/macOS command examples for downloading logs (e.g., using Azure CLI, azcopy, or curl).
  • Clarify whether PowerShell commands can be run on Linux/macOS (using PowerShell Core), and offer equivalent bash/CLI instructions.
  • Add troubleshooting notes for interpreting logs and error codes on non-Windows platforms.
  • Avoid referencing Windows error codes exclusively; provide mappings or explanations for Linux/macOS equivalents if applicable.
  • Mention cross-platform tools (e.g., Azure CLI, azcopy) before or alongside Windows-specific tools.
GitHub Create Pull Request
Network Watcher Troubleshoot VPN gateways and connections - PowerShell ...rticles/network-watcher/vpn-troubleshoot-powershell.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation is heavily focused on PowerShell, with all troubleshooting steps and code samples using Azure PowerShell cmdlets. There are no examples or instructions for Linux/macOS users who may prefer or require Azure CLI or Bash. The prerequisites and workflow assume PowerShell usage, which is most common on Windows, and do not mention Linux-specific tools or patterns. Although Azure Cloud Shell supports PowerShell on all platforms, the lack of CLI/Bash parity and PowerShell-first approach creates friction for non-Windows users.
Recommendations
  • Add equivalent Azure CLI examples for all troubleshooting steps, including storage account and container creation, and running the troubleshooting command.
  • Explicitly mention that Azure Cloud Shell supports both PowerShell and Bash, and provide guidance for Linux/macOS users.
  • Reorganize the documentation to present both PowerShell and CLI/Bash options side-by-side or in tabs, rather than PowerShell-only.
  • Clarify any platform-specific requirements or limitations for each approach.
GitHub Create Pull Request
Network Watcher Install the Azure Connected Machine agent for connection monitor ...-watcher/connection-monitor-connected-machine-agent.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page exhibits a moderate Windows bias. Windows instructions and tools (PowerShell, Windows Admin Center) are presented before Linux equivalents, and PowerShell is emphasized as a cross-platform automation tool, even though its usage is more natural on Windows. Windows-specific tooling (Windows Admin Center) is highlighted, while Linux alternatives are not mentioned. Linux instructions are present and functional, but Windows-centric patterns dominate the narrative.
Recommendations
  • Present Linux and Windows instructions in parallel or alternate their order to avoid implicit prioritization.
  • Include Linux-native automation options (e.g., Bash scripts, Ansible, cloud-init) alongside PowerShell for Linux users.
  • Mention Linux management tools (such as Cockpit, or CLI-based workflows) where Windows Admin Center is referenced.
  • Clarify PowerShell's cross-platform availability and provide Bash or shell script equivalents for Linux users.
  • Ensure that all features and steps described for Windows (such as agent onboarding via Windows Admin Center) have Linux equivalents or note any limitations.
GitHub Create Pull Request
Network Watcher Visualizing Azure NSG flow logs - Power BI ...er/network-watcher-visualize-nsg-flow-logs-power-bi.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation exclusively describes using Power BI Desktop, a Windows-centric tool, to visualize Azure NSG flow logs. There are no examples or instructions for Linux or macOS users, nor are alternative cross-platform visualization tools mentioned in the main content. The only nod to open source or Linux-friendly solutions is a brief link in the 'Next steps' section, with no parity in the main walkthrough.
Recommendations
  • Provide instructions for visualizing NSG flow logs using cross-platform tools (e.g., Power BI on the web, Jupyter Notebooks, Grafana, Kibana/Elastic Stack) within the main content.
  • Include explicit notes about Power BI Desktop's OS requirements and alternatives for Linux/macOS users.
  • Offer sample scripts or templates for Linux/macOS users to parse and visualize logs using open source tools.
  • Reorder or parallelize instructions so that Linux/macOS alternatives are presented alongside Windows/Power BI steps, not relegated to 'Next steps'.
GitHub Create Pull Request
← Previous Page 1 of 2 Next →