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 151-175 of 238 flagged pages
Network Watcher Filter Virtual Network Flow Logs (Preview) ...n/articles/network-watcher/vnet-flow-logs-filtering.md
Medium Priority View Details →
Scanned: 2026-01-14 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 (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.
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-14 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-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.
GitHub Create Pull Request
Network Watcher VPN troubleshoot overview .../articles/network-watcher/vpn-troubleshoot-overview.md
Medium Priority View Details →
Scanned: 2026-01-14 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. 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.
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-14 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 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'.
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-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias. Windows installation instructions and tools (PowerShell, Windows Admin Center) are presented before Linux equivalents, and Windows-specific tooling is highlighted in dedicated sections. PowerShell is emphasized as a cross-platform solution, but Windows-centric workflows (like Windows Admin Center) are described in detail, while Linux alternatives are not mentioned. Linux instructions are present but less detailed and appear after Windows examples.
Recommendations
  • Present Linux and Windows instructions in parallel or alternate their order to avoid 'Windows first' bias.
  • Include equivalent Linux-native automation examples (e.g., Bash scripts, Ansible, or cloud-init) where PowerShell or Windows Admin Center is highlighted.
  • Add a section for Linux management tools or workflows, such as using Azure CLI or configuration management tools for agent deployment.
  • Expand Linux installation instructions to match the detail provided for Windows, including troubleshooting and verification steps.
  • Clarify that PowerShell Core is available on Linux and macOS, and provide explicit cross-platform usage examples.
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-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The tutorial demonstrates a notable 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 or connecting to Linux VMs, nor for using SSH or Linux-native tools. The only traffic generation example uses a Windows browser, and the portal workflow assumes RDP access, which is not applicable to Linux VMs.
Recommendations
  • Include parallel instructions for creating a Linux VM (e.g., Ubuntu), including SSH access setup.
  • Provide examples for connecting to the VM using SSH (for Linux/macOS users) alongside RDP for Windows.
  • Suggest using Linux-native tools (e.g., curl, wget, or a browser) to generate outbound traffic from a Linux VM.
  • Clarify that the tutorial works for both Windows and Linux VMs, and highlight any differences in steps.
  • Add screenshots or command-line snippets relevant to Linux environments where appropriate.
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-13 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 Linux/macOS alternatives. All code samples and naming conventions are tailored to PowerShell, which is traditionally associated with Windows environments. There is no guidance for users who prefer or require Linux/macOS tooling, nor any indication of how to adapt the process for those platforms.
Recommendations
  • Provide equivalent examples using Azure CLI and/or Bash scripts for Linux/macOS users.
  • Mention that Azure Automation supports Python runbooks and include a sample for Python-based automation.
  • Clarify whether PowerShell Core (cross-platform) is supported and, if so, provide guidance for running scripts on Linux/macOS.
  • Add a section comparing PowerShell and non-PowerShell approaches, highlighting platform compatibility.
  • Ensure that prerequisites and instructions do not assume a Windows-only environment.
GitHub Create Pull Request
Network Watcher Troubleshoot outbound connections ...cles/network-watcher/connection-troubleshoot-manage.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation consistently uses Windows-centric examples, notably focusing on RDP (port 3389) for connectivity tests, which is a Windows protocol. There are no 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. The PowerShell tab is prominent, and there is no mention of Linux tools or commands outside Azure CLI, nor any guidance for Linux firewall or SSH troubleshooting.
Recommendations
  • Add Linux/macOS scenarios, such as testing SSH connectivity (port 22) between VMs.
  • Include troubleshooting steps for Linux (e.g., checking SSH service, configuring Linux firewalls like ufw or firewalld).
  • Provide example commands for Linux users (e.g., using SSH, netcat, or telnet for connectivity tests).
  • Balance the documentation by alternating between Windows and Linux examples, or presenting both side-by-side.
  • Clarify that Azure CLI works cross-platform and provide guidance for Linux shell usage where appropriate.
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-13 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 Azure PowerShell, with all examples and instructions using PowerShell cmdlets. There are no Bash, Azure CLI, or Linux/macOS-specific examples or guidance. The prerequisites and workflow assume the use of PowerShell, which is more familiar to Windows users, and do not mention or provide parity for Linux/macOS users who may prefer Bash or Azure CLI.
Recommendations
  • Add equivalent Azure CLI examples for each PowerShell command, as Azure CLI is cross-platform and commonly used on Linux/macOS.
  • Explicitly mention that Azure Cloud Shell supports both Bash and PowerShell, and provide instructions for both.
  • Include notes or links for Linux/macOS users on how to install and use Azure CLI.
  • Reorder sections or provide parallel workflows so that Linux/macOS users do not feel secondary to Windows users.
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-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation page demonstrates a moderate Windows bias. Windows Server is used as the default and only example OS for the virtual machine throughout the guide. VM creation steps and code samples (PowerShell and Azure CLI) exclusively reference Windows images, with no mention of Linux alternatives. The portal instructions also default to Windows Server. PowerShell is featured prominently as a scripting option, which is more common in Windows environments. There are no Linux-specific examples, nor is there guidance for Linux VM creation or troubleshooting.
Recommendations
  • Provide parallel Linux VM creation examples in the portal, PowerShell, and Azure CLI sections (e.g., using Ubuntu or other common Linux images).
  • Explicitly mention that the steps apply to both Windows and Linux VMs, and clarify any OS-specific differences.
  • Include troubleshooting notes or examples relevant to Linux VMs, such as SSH connectivity or Linux-specific ports.
  • Balance scripting examples by highlighting Bash or cross-platform CLI usage where appropriate, and clarify that Azure CLI works on Linux/macOS.
  • Where PowerShell is referenced, note that Azure PowerShell is available cross-platform, but CLI is often preferred on Linux/macOS.
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-13 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 configuration. All examples and screenshots are Windows-centric, and Linux/macOS users are not shown how to complete equivalent steps.
Recommendations
  • Include instructions and screenshots for creating a Linux VM (e.g., Ubuntu) alongside the Windows VM example.
  • Provide SSH connection steps for Linux VMs, including guidance for generating and using SSH keys.
  • Mention Linux/macOS-compatible tools and workflows (e.g., using SSH from a terminal, verifying connectivity with curl or ping).
  • Ensure parity in troubleshooting steps, showing how to perform all tasks on both Windows and Linux VMs.
  • Add a table or section comparing Windows and Linux VM setup and access methods.
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-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation exclusively uses Azure PowerShell cmdlets for all steps, with no mention or examples of Azure CLI, Bash, or Linux-native tooling. All code blocks are PowerShell, and instructions reference PowerShell-specific modules and commands. There is no guidance for Linux/macOS users who may prefer Bash or Azure CLI, nor any parity in example ordering or tool choice.
Recommendations
  • Add equivalent Azure CLI (az) command examples for each step, especially for resource creation and IP flow verification.
  • Explicitly mention that Azure Cloud Shell supports both Bash and PowerShell, and clarify how Linux/macOS users can follow along.
  • Provide links to Azure CLI documentation and reference pages alongside PowerShell links.
  • Consider alternating example order (PowerShell first, then CLI, or vice versa) or grouping examples by platform.
  • Add a note on platform/tool choice at the start, helping users select the best option for their OS.
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-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates mild Windows bias. It references the 'Network Watcher extension' with a link specifically to a Windows agent installation page, and does not provide equivalent Linux agent installation instructions or links. Windows tools and patterns (such as Log Analytics agent replacement) are mentioned before any Linux-specific guidance. There are no explicit Linux migration steps or examples, and the agent extension documentation is Windows-centric.
Recommendations
  • Include explicit instructions and links for installing and migrating the Network Watcher extension on Linux VMs, not just Windows.
  • Provide Linux-specific examples or mention Linux agent installation parity in migration steps.
  • Ensure references to agent installation or replacement link to both Windows and Linux documentation, or to a cross-platform page.
  • Add a section clarifying any differences or considerations for Linux users during migration.
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-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation provides parity for Linux and Windows in most Azure CLI examples, but is notably biased towards Windows in automation and scripting guidance. The only bulk update script is PowerShell-based and targets Windows VMs, with no Bash or cross-platform scripting alternative. PowerShell is used as the primary automation tool, and Windows terminology and tools are often mentioned first or exclusively.
Recommendations
  • Provide a Bash or Azure CLI script for bulk updating Network Watcher extensions on Linux VMs, similar to the PowerShell script for Windows.
  • Include automation examples using cross-platform tools (e.g., Azure CLI, Python SDK) for both Linux and Windows environments.
  • When listing manual update commands, alternate the order of Linux and Windows examples or present them side-by-side.
  • Clarify in scripting sections whether the provided scripts are cross-platform or Windows-only, and offer Linux equivalents where possible.
  • Highlight that PowerShell Core is available on Linux, or provide guidance for using it if that's the intended cross-platform solution.
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-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page is focused on Linux VMs, but PowerShell is heavily featured as a primary automation tool, with detailed instructions and examples for Azure PowerShell cmdlets. Azure PowerShell is a Windows-centric tool, and its usage is described before Azure CLI in several sections. There are also references to installing Azure PowerShell locally, which is most straightforward on Windows. The documentation does provide Azure CLI examples, but PowerShell is given equal or greater prominence, and there are no bash or shell script examples. The use of PowerShell as the main scripting interface may create friction for Linux/macOS users who prefer native shell environments.
Recommendations
  • Prioritize Azure CLI examples before PowerShell in all sections, as CLI is cross-platform and native to Linux/macOS.
  • Add bash or shell script examples for common tasks, especially for listing, installing, and uninstalling extensions.
  • Clarify that Azure PowerShell can be run on Linux/macOS, but recommend Azure CLI for Linux users.
  • Where PowerShell is mentioned, provide equivalent bash/CLI commands side-by-side for parity.
  • Remove or minimize references to installing Azure PowerShell locally unless specifically relevant to Linux users.
GitHub Create Pull Request
Network Watcher Enable or disable Azure Network Watcher ...ain/articles/network-watcher/network-watcher-create.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation consistently presents PowerShell examples and instructions before Azure CLI, and references PowerShell-specific tools and installation steps. The PowerShell sections assume familiarity with Windows tooling, and links for installing PowerShell locally are provided, which is primarily a Windows-centric workflow. While Azure CLI is supported and documented, PowerShell is given precedence and more detailed guidance, which may create friction for Linux/macOS users who typically prefer CLI or Bash-based workflows.
Recommendations
  • Alternate the order of PowerShell and Azure CLI examples, or present CLI first to better support cross-platform users.
  • Explicitly mention that Azure CLI works natively on Linux/macOS and provide links to Bash/Zsh shell usage where relevant.
  • Clarify that PowerShell Core is cross-platform, but highlight CLI as the default for Linux/macOS users.
  • Add notes or sections for common Linux/macOS shell environments, including troubleshooting and installation steps for Azure CLI.
  • Avoid language that implies PowerShell is the primary or preferred method unless justified by feature parity.
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-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation focuses exclusively on using Power BI Desktop, a Windows-centric tool, for visualizing Azure NSG flow logs. There are no instructions or examples for Linux or macOS users, nor mention of cross-platform alternatives for the described workflow. The only alternative (Elastic Stack) is referenced in 'Next steps' and not integrated into the main guide.
Recommendations
  • Provide explicit instructions or alternatives for Linux/macOS users, such as using Power BI on the web, or open-source BI tools (e.g., Grafana, Kibana) for log visualization.
  • Include cross-platform steps for downloading and parsing NSG flow logs, such as using Python, Azure CLI, or other tools available on Linux/macOS.
  • Reorder or supplement the documentation so that open-source and cross-platform visualization options are presented alongside Power BI, not only as a 'next step'.
  • Clarify system requirements and limitations for Power BI Desktop (Windows-only) early in the documentation.
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-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation demonstrates a notable Windows bias by exclusively providing migration instructions and scripts in PowerShell (.ps1), referencing Windows-centric tools and patterns, and omitting any Bash, Azure CLI, or Linux/macOS-specific examples. The prerequisites and workflow assume PowerShell usage, which is less common or less native on Linux/macOS platforms. There is no mention of alternative scripts, nor guidance for Linux/macOS users beyond a generic link to PowerShell installation.
Recommendations
  • Provide equivalent migration scripts in Bash or Azure CLI, or document how to run the migration using Azure CLI commands.
  • Include explicit instructions and tested examples for running the PowerShell script on Linux and macOS, including common troubleshooting steps (e.g., permissions, execution policy).
  • List prerequisites for Linux/macOS separately, highlighting any differences or additional setup required.
  • Offer download options for scripts in multiple formats (e.g., .sh for Bash, .ps1 for PowerShell) if feasible.
  • Reorder examples or instructions so that cross-platform tools (e.g., Azure CLI) are mentioned before or alongside PowerShell.
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-13 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 Azure CLI or Bash alternatives. File paths use Windows conventions (e.g., C:\MyTemplates\azuredeploy.json), and all command-line instructions assume a Windows/PowerShell environment. There is no guidance for Linux/macOS users or cross-platform tooling.
Recommendations
  • Add equivalent Azure CLI examples for deploying ARM templates, using Bash syntax and Linux/macOS file paths.
  • Explicitly mention that Azure CLI is cross-platform and provide links to installation guides for Linux/macOS.
  • Reorder or parallelize examples so that both PowerShell and CLI/Bash options are presented together.
  • Clarify that the ARM template deployment can be performed from any OS, not just Windows.
  • Include notes or sections for Linux/macOS users, highlighting any differences or considerations.
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-13 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 biased toward Windows and PowerShell. All code samples, authentication steps, and environment variable setup instructions use PowerShell, with no equivalent Bash, CLI, or Python examples for Linux/macOS users. The authentication workflow assumes access to Windows paths and PowerShell-specific encryption methods. While Linux VM extensions are mentioned in prerequisites, the actual implementation and automation steps are Windows-centric.
Recommendations
  • Provide equivalent Bash, Azure CLI, or Python examples for all PowerShell scripts, especially for authentication and packet capture initiation.
  • Include instructions for generating and storing encrypted credentials on Linux/macOS, avoiding Windows-specific file paths and PowerShell-only encryption.
  • Explicitly document any differences or requirements for Linux/macOS users, such as using the Azure CLI or REST API from Azure Functions.
  • Where possible, show both Windows and Linux workflows side-by-side, or indicate which steps are platform-agnostic.
  • Add references to Linux/macOS tools and patterns (e.g., using environment variables, file storage locations, and scripting best practices).
GitHub Create Pull Request
Network Watcher Manage virtual network flow logs ...main/articles/network-watcher/vnet-flow-logs-manage.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation provides parity between Azure Portal, PowerShell, and Azure CLI for all major operations. However, PowerShell is featured heavily, with detailed instructions and examples, and references to installing and using Azure PowerShell locally. This can be interpreted as a Windows bias, since PowerShell is most commonly associated with Windows environments, and the documentation does not mention Bash or shell scripting alternatives for Linux/macOS users. Additionally, instructions for downloading blobs reference PowerShell before CLI, and there are references to Windows-centric tools like Azure Storage Explorer without explicit mention of Linux/macOS compatibility.
Recommendations
  • Add explicit Bash/shell script examples for common tasks, especially for downloading and manipulating flow logs.
  • Clarify that Azure CLI works natively on Linux/macOS and provide examples of using CLI in those environments.
  • Mention that PowerShell Core is cross-platform, and provide installation instructions for Linux/macOS users.
  • When referencing Azure Storage Explorer, note its availability on Linux/macOS and provide links to installation guides for those platforms.
  • Consider alternating the order of PowerShell and CLI examples, or defaulting to CLI first, as CLI is more universally available.
GitHub Create Pull Request
Network Watcher VPN troubleshoot overview .../articles/network-watcher/vpn-troubleshoot-overview.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows Error Codes Windows First
Summary
The documentation exhibits moderate Windows bias. It references Azure PowerShell and the Azure portal as primary interfaces, and in the 'Considerations' section, PowerShell is suggested as a workaround for resource group limitations, while Azure CLI (the cross-platform tool) is restricted. Log file examples and error messages reference Windows-specific error codes (e.g., 'Windows error 13801'), and log file paths use Windows-style formatting. There are no Linux/macOS-specific troubleshooting examples, and Windows terminology appears first or exclusively in some sections.
Recommendations
  • Provide explicit Linux/macOS examples for running VPN troubleshoot via Azure CLI, including troubleshooting resource group limitations.
  • Clarify if PowerShell Core (cross-platform) is supported, and provide instructions for Linux/macOS users.
  • Include Linux/macOS file path examples and clarify if logs can be interpreted on non-Windows systems.
  • Add notes or tables mapping Windows error codes to their meanings for non-Windows users.
  • Ensure that CLI instructions are not limited by resource group placement, or provide Linux/macOS workarounds.
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 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 explicit references to Azure PowerShell and Cloud Shell. There are no CLI (az), Bash, or Linux/macOS-specific examples or guidance. Prerequisite links and instructions also default to PowerShell, and there is no mention of cross-platform alternatives or parity.
Recommendations
  • Add equivalent Azure CLI (az) commands for all PowerShell examples, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Update prerequisite links to include both PowerShell and CLI tabs, ensuring users can follow along regardless of their OS.
  • Explicitly mention that Azure Cloud Shell supports both Bash and PowerShell, and provide instructions/examples for both.
  • Clarify that all steps can be performed from Linux/macOS using Azure CLI or Bash in Cloud Shell, not just PowerShell.
  • Where possible, avoid language that implies PowerShell is the default or only supported method.
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-13 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 examples and instructions using PowerShell cmdlets. There are no Bash, Azure CLI, or Linux/macOS-native examples provided in the main content. The prerequisites and workflow assume PowerShell usage, which is more familiar to Windows users. While Azure Cloud Shell supports PowerShell on all platforms, the lack of CLI or Bash examples creates friction for Linux/macOS users. The only mention of CLI parity is in the 'Related content' section, which links to a separate page.
Recommendations
  • Add Azure CLI examples alongside PowerShell for all major steps, using tabbed code blocks for parity.
  • Explicitly mention that Azure Cloud Shell supports both PowerShell and Bash, and clarify that the steps can be performed in either shell.
  • In the prerequisites, provide instructions for installing and using Azure CLI on Linux/macOS.
  • Ensure that references to tools (e.g., Storage Explorer) include cross-platform alternatives or clarify their availability.
  • Consider restructuring the page or adding a prominent note at the top linking to the CLI/Linux version for users who prefer non-PowerShell workflows.
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-11 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 virtual machine creation, both in the Azure Portal and in CLI/PowerShell instructions. There are no examples or instructions for creating or managing Linux-based virtual machines, nor are there references to Linux-specific patterns or considerations. This creates a bias toward Windows environments and may hinder Linux users from following the documentation seamlessly.
Recommendations
  • Provide parallel examples for creating Linux virtual machines (e.g., using Ubuntu or CentOS images) in all sections where VM creation is demonstrated.
  • Include notes or guidance on Linux-specific considerations for NSG diagnostics and Bastion connections, such as SSH access and username conventions.
  • Ensure that both Windows and Linux VM creation options are presented side-by-side or in a way that does not prioritize Windows over Linux.
  • Where output or configuration is shown, clarify any differences that may arise when using Linux VMs (e.g., default ports, authentication methods).
GitHub Create Pull Request
← Previous Page 7 of 10 Next →