Networking

56
Total Pages
52
Linux-Friendly Pages
4
Pages with Bias
7.1%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

7 issues found
Showing 1-7 of 7 flagged pages
Networking Azure for Network Engineers ...ain/articles/networking/azure-for-network-engineers.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 page references PowerShell as a primary tool for managing Azure networking, including linking to a PowerShell-specific cmdlet (Get-AzEffectiveRouteTable) for route verification. While Azure CLI is mentioned, examples and deep links are PowerShell-centric, and there are no Linux/macOS-specific instructions or CLI command examples. The order of tool mentions (Portal, PowerShell, CLI) also places Windows tools first. This creates friction for Linux/macOS users who may prefer or require Azure CLI or Bash-based workflows.
Recommendations
  • Provide explicit Azure CLI examples for all tasks currently shown with PowerShell, especially for route and NSG verification.
  • Include links to Azure CLI documentation equivalent to PowerShell cmdlets (e.g., az network nic show-effective-route-table).
  • When listing tools, alternate or randomize the order (e.g., 'Portal, CLI, PowerShell') or clarify that all are equally supported.
  • Add notes or sections highlighting Linux/macOS compatibility and workflows.
  • Ensure that all referenced commands and deep links have CLI and PowerShell equivalents.
GitHub Create Pull Request
Networking Troubleshoot Azure Microsoft.Network failed Provisioning State .../main/articles/networking/troubleshoot-failed-state.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 Tools Missing Linux Example Windows First
Summary
The documentation exclusively uses Azure PowerShell cmdlets for all troubleshooting steps, with instructions to install and use PowerShell. There are no examples or guidance for Linux/macOS users using Azure CLI, Bash, or other cross-platform tools. The workflow assumes a PowerShell environment, which is native to Windows and less common on Linux/macOS. This creates friction for non-Windows users and may prevent them from easily following the troubleshooting steps.
Recommendations
  • Provide equivalent Azure CLI examples for each resource operation (e.g., az network application-gateway show/update).
  • Add a section explaining how to perform these tasks using Bash or shell scripting on Linux/macOS.
  • Clarify that Azure PowerShell can be installed on Linux/macOS, but highlight CLI alternatives for users who prefer them.
  • Present both PowerShell and CLI examples side-by-side or allow users to select their preferred environment.
  • Mention prerequisites for Linux/macOS users, such as installing PowerShell Core or Azure CLI.
GitHub Create Pull Request
Networking Azure for Network Engineers ...ain/articles/networking/azure-for-network-engineers.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation references PowerShell and the Azure Portal as primary management tools, with Azure CLI mentioned but not exemplified. The only direct command reference is to a PowerShell cmdlet (Get-AzEffectiveRouteTable), with no equivalent Azure CLI or Linux/macOS example provided. The ordering and emphasis suggest a Windows-centric approach, potentially creating friction for Linux/macOS users.
Recommendations
  • Provide equivalent Azure CLI examples alongside PowerShell cmdlets, especially for critical tasks like viewing effective routes.
  • Explicitly mention cross-platform compatibility of Azure CLI and provide sample commands for Linux/macOS users.
  • Where management tools are listed, avoid listing PowerShell first or exclusively; use neutral phrasing such as 'Azure CLI, PowerShell, or Portal'.
  • Include notes or links to documentation for Linux/macOS users where workflows differ.
GitHub Create Pull Request
Networking Check Azure resource usage against limits | Microsoft Docs ...main/articles/networking/check-usage-against-limits.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation provides detailed PowerShell instructions and references to Windows-specific tools before mentioning Azure CLI. PowerShell examples and prerequisites (such as module installation and login steps) are described in greater detail than their CLI counterparts, and PowerShell is presented before CLI, which may suggest a Windows-first approach. There are no Linux/macOS-specific examples or notes, and the CLI section does not mention shell-specific considerations for Linux/macOS users.
Recommendations
  • Add explicit Linux/macOS instructions, such as running Azure CLI commands in Bash or Zsh, and note any differences in output formatting or prerequisites.
  • Provide parity in example detail: ensure CLI instructions are as thorough as PowerShell, including login steps and troubleshooting.
  • Consider presenting CLI examples before PowerShell, or alternate their order, to avoid implicit Windows-first bias.
  • Mention cross-platform compatibility of Azure Cloud Shell and clarify that both PowerShell and Bash are available regardless of OS.
GitHub Create Pull Request
Networking Troubleshoot Azure Microsoft.Network failed Provisioning State .../main/articles/networking/troubleshoot-failed-state.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
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 troubleshooting steps, with instructions to install and use PowerShell. There are no examples or guidance for using Azure CLI, REST API, or ARM templates, which are platform-agnostic and commonly used on Linux/macOS. The instructions assume access to PowerShell and do not mention alternatives for non-Windows environments.
Recommendations
  • Add equivalent Azure CLI examples for each resource operation (e.g., az network application-gateway show/update).
  • Clarify that Azure PowerShell is cross-platform, but also provide installation and usage instructions for Linux/macOS.
  • Include REST API or ARM template methods for advanced users who may not use PowerShell.
  • Present CLI and PowerShell examples side-by-side or in separate tabs, rather than only PowerShell.
  • Explicitly mention that all steps can be performed on Linux/macOS, and link to relevant cross-platform installation guides.
GitHub Create Pull Request
Networking Accelerated connections network performance optimization on NVAs and VMs ...ain/articles/networking/nva-accelerated-connections.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation lists PowerShell as the first supported enablement method, which may suggest a Windows-centric approach. While other cross-platform tools (CLI, Terraform, ARM templates, SDK) are mentioned, there are no explicit Linux/macOS examples or references to Bash, and PowerShell is the only named scripting environment. No Linux-specific tools or workflows are described, and the order of presentation subtly prioritizes Windows users.
Recommendations
  • Provide explicit Linux/macOS examples using Bash and Azure CLI.
  • List cross-platform tools (CLI, Terraform) before PowerShell to avoid Windows-first impression.
  • Clarify that all methods (CLI, Terraform, SDK) are fully supported on Linux/macOS.
  • Include sample commands for both PowerShell and Bash/CLI where relevant.
  • Mention that PowerShell Core is available cross-platform, if relevant, or clarify Windows-only aspects.
GitHub Create Pull Request
Networking Accelerated connections network performance optimization on NVAs and VMs ...ain/articles/networking/nva-accelerated-connections.md
Low Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation lists PowerShell as the first supported enablement method, which may suggest a Windows-centric approach. There are no explicit Linux/macOS examples or tool recommendations, and PowerShell is mentioned before cross-platform tools like Azure CLI and Terraform.
Recommendations
  • List cross-platform tools (Azure CLI, Terraform) before PowerShell to avoid implying Windows-first workflows.
  • Provide explicit examples for Linux/macOS environments, such as CLI commands and shell scripts.
  • Clarify that all listed methods (CLI, Terraform, SDK) are fully supported on Linux/macOS.
  • Add a note or section highlighting Linux/macOS parity and any platform-specific considerations.
GitHub Create Pull Request