Load Balancer

104
Total Pages
41
Linux-Friendly Pages
63
Pages with Bias
60.6%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

388 issues found
Showing 101-125 of 388 flagged pages
Load Balancer https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/tutorial-protect-load-balancer-ddos.md ...s/load-balancer/tutorial-protect-load-balancer-ddos.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example Powershell Heavy 🔧 Windows Tools
Summary
The tutorial demonstrates a clear Windows bias in its VM creation and configuration steps. Only Windows Server images are used for the virtual machines, and IIS installation is performed exclusively via Windows PowerShell commands. There are no examples or instructions for deploying Linux VMs, installing a web server on Linux, or using Linux command-line tools. The documentation assumes a Windows environment for backend workloads and omits Linux alternatives entirely.
Recommendations
  • Provide parallel instructions for deploying Linux VMs (e.g., Ubuntu or CentOS) in the backend pool.
  • Include Linux-specific steps for installing and configuring a web server (e.g., Apache or Nginx) using Bash commands.
  • Offer both PowerShell and Bash command examples for server setup and configuration.
  • Explicitly mention that either Windows or Linux VMs can be used, and link to relevant documentation for both.
  • Ensure screenshots and portal instructions show both Windows and Linux options where applicable.
GitHub Create Pull Request
Load Balancer https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/gateway-deploy-dual-stack-load-balancer.md ...ad-balancer/gateway-deploy-dual-stack-load-balancer.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation consistently presents PowerShell (Windows-centric) examples before Azure CLI (cross-platform) in each code section. References to prerequisite guides and resource creation link to PowerShell-based documentation first. The overall structure and example ordering suggest a preference for Windows/PowerShell workflows, potentially making Linux users feel secondary. There is no mention of Linux-specific tools, shell environments, or considerations for Linux users.
Recommendations
  • Alternate the order of examples, sometimes presenting Azure CLI before PowerShell to signal equal support.
  • Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and provide links to installation guides for Linux users.
  • Add a short section or callout for Linux users, noting any differences or considerations (e.g., shell quoting, environment setup).
  • Reference cross-platform documentation in prerequisites, not just PowerShell-based guides.
  • Where possible, include Bash script examples or highlight usage in Linux shell environments.
GitHub Create Pull Request
Load Balancer https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/quickstart-load-balancer-standard-internal-cli.md ...ncer/quickstart-load-balancer-standard-internal-cli.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation page demonstrates a strong Windows bias. All virtual machine creation examples use Windows images (win2022datacenter, Win2019Datacenter), and installation of IIS is performed via PowerShell commands. There are no examples or instructions for deploying Linux VMs, installing a Linux web server (such as Apache or Nginx), or using Linux-native tools. The test instructions reference Internet Explorer, further reinforcing a Windows-centric approach. No Linux alternatives or parity are provided.
Recommendations
  • Provide parallel examples for Linux VMs, such as using Ubuntu or CentOS images in the az vm create commands.
  • Include instructions for installing a web server on Linux VMs (e.g., Apache or Nginx) using appropriate shell commands.
  • Show how to test the load balancer from a Linux VM, using browsers like Firefox or command-line tools like curl.
  • Avoid referencing Windows-only tools (e.g., Internet Explorer, PowerShell) without Linux equivalents.
  • Explicitly mention that the Azure CLI works cross-platform and highlight any OS-specific considerations.
GitHub Create Pull Request
Load Balancer https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/load-balancer-tcp-idle-timeout.md ...ticles/load-balancer/load-balancer-tcp-idle-timeout.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell is presented as a primary automation method, with detailed instructions and prerequisites for installing and using the Azure PowerShell module, which is most commonly used on Windows. The CLI section is present and platform-neutral, but the PowerShell example and tooling are given prominence and detail. There is no mention of Linux-specific tools, shell environments, or considerations (e.g., Bash, zsh, or Linux package managers for CLI installation). The documentation does not provide Linux-specific examples or highlight Linux workflows, and Windows-centric tools (PowerShell) are described in more depth.
Recommendations
  • Add explicit Linux/Bash shell examples for Azure CLI usage, including sample commands run in Bash.
  • Include notes or instructions for installing and using Azure CLI on Linux distributions (e.g., apt, yum, zypper).
  • Mention that PowerShell Core is available cross-platform, and clarify how Linux/macOS users can use PowerShell if desired.
  • Balance the depth of instructions for PowerShell and CLI, ensuring CLI instructions are as detailed as PowerShell, especially for Linux users.
  • Consider adding a troubleshooting section for common Linux-specific issues (e.g., permissions, environment variables).
GitHub Create Pull Request
Load Balancer https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/tutorial-load-balancer-ip-backend-portal.md ...d-balancer/tutorial-load-balancer-ip-backend-portal.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example Powershell Heavy 🔧 Windows Tools
Summary
The documentation demonstrates a Windows bias, especially in the VM creation and configuration steps. Only Windows Server is used as the VM image, and all instructions for installing and configuring IIS use Windows-specific tools (PowerShell, Windows Administrative Tools). There are no Linux VM examples, nor instructions for setting up a web server on Linux. The use of PowerShell and IIS is exclusive, with no mention of Linux alternatives such as SSH, Bash, or Apache/Nginx.
Recommendations
  • Add parallel instructions for creating Linux VMs (e.g., Ubuntu) in the 'Create virtual machines' section.
  • Provide Linux-specific steps for installing a web server (e.g., Apache or Nginx) using Bash/SSH.
  • Include command examples for Linux (e.g., apt install apache2, echo 'Hello World' > /var/www/html/index.html).
  • Present both Windows and Linux options side-by-side, or allow the user to select their OS preference at the start of the tutorial.
  • Avoid assuming Windows as the default platform; mention Linux as a supported and common alternative.
GitHub Create Pull Request
Load Balancer https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/quickstart-load-balancer-standard-public-template.md ...r/quickstart-load-balancer-standard-public-template.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools Windows First
Summary
The documentation page demonstrates a bias toward Windows environments by providing only Azure PowerShell deployment instructions and examples, referencing Windows-centric tools (such as IIS), and omitting Linux CLI/bash examples. The use of PowerShell is presented as the primary method for deploying the ARM template, with no equivalent Bash, Azure CLI, or Linux shell instructions. Additionally, the web server used for demonstration is IIS, a Windows technology, with no mention of Linux alternatives.
Recommendations
  • Add equivalent Azure CLI (az) deployment instructions and code blocks, suitable for Linux/macOS users.
  • Include Bash shell examples for template deployment in addition to PowerShell.
  • Demonstrate deployment of a Linux-based web server (e.g., Apache or Nginx) alongside or instead of IIS.
  • Explicitly mention cross-platform options and clarify that ARM templates can be deployed from any OS.
  • Reorder or parallelize instructions so that Windows and Linux methods are presented together, rather than Windows-first.
  • Provide screenshots or output examples from Linux environments where relevant.
GitHub Create Pull Request
Load Balancer https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/whats-new.md ...ure-docs/blob/main/articles/load-balancer/whats-new.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page displays subtle Windows bias. The only explicit example link for creating a dual stack application points to a PowerShell-based guide, which is Windows-centric. There are no Linux or cross-platform CLI examples referenced, and no mention of Linux tools or patterns for managing Azure Load Balancer. This may unintentionally signal to users that Windows or PowerShell is the primary or preferred environment for Azure Load Balancer operations.
Recommendations
  • Add equivalent Linux and Azure CLI examples alongside PowerShell guides, especially for key scenarios like dual stack application setup.
  • Reference Linux-native tools and commands (e.g., Bash, curl, ip, traceroute) where relevant, and provide links to Linux documentation.
  • Ensure that cross-platform instructions (Azure CLI, REST API, Terraform, etc.) are given equal prominence and are easy to find.
  • Review all example links and ensure parity between Windows/PowerShell and Linux/Azure CLI content.
  • Explicitly state that Azure Load Balancer is fully supported and manageable from Linux environments.
GitHub Create Pull Request
Load Balancer https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/quickstart-load-balancer-standard-internal-portal.md ...r/quickstart-load-balancer-standard-internal-portal.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example Powershell Heavy 🔧 Windows Tools
Summary
The documentation demonstrates a clear Windows bias: VM creation defaults to Windows Server, IIS installation is shown only for Windows using PowerShell, and all testing steps use Windows tools (PowerShell, Edge browser). There are no Linux VM examples, nor instructions for installing a web server on Linux or testing with Linux tools. Windows-specific terminology and patterns (e.g., Windows Administrative Tools, PowerShell) are used exclusively.
Recommendations
  • Provide parallel instructions for creating a Linux VM (e.g., Ubuntu) alongside the Windows VM example.
  • Include steps for installing a web server on Linux (e.g., Apache or Nginx) using appropriate Linux commands.
  • Show how to test the load balancer from a Linux VM (e.g., using curl or a browser like Firefox).
  • Use neutral terminology where possible (e.g., 'Connect to your VM using Bastion' instead of referencing Windows-specific tools).
  • Present both Windows and Linux examples side-by-side or allow users to select their preferred OS path at the start of the guide.
GitHub Create Pull Request
Load Balancer https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/tutorial-deploy-cross-region-load-balancer-template.md ...ttps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/tutorial-deploy-cross-region-load-balancer-template.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a bias toward Windows by exclusively referencing IIS (Internet Information Server) and showing the default IIS Windows Server web page as the deployment test. There are no examples or instructions for deploying or verifying with Linux-based web servers (e.g., Apache, Nginx), nor are Linux-specific deployment or verification steps mentioned. The use of Windows terminology and tools (IIS, Windows Server) is present, while Linux equivalents are absent.
Recommendations
  • Include examples for deploying Linux virtual machines and configuring a Linux web server (e.g., Apache, Nginx) in the ARM template.
  • Show screenshots and verification steps for accessing a default Linux web page after deployment.
  • Mention both Windows and Linux options when describing the virtual machine extensions and web server configuration.
  • Provide parity in instructions for both Windows and Linux environments, including troubleshooting and cleanup steps.
GitHub Create Pull Request
Load Balancer https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/tutorial-protect-load-balancer-ddos.md ...s/load-balancer/tutorial-protect-load-balancer-ddos.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example Powershell Heavy 🔧 Windows Tools
Summary
The documentation demonstrates a Windows bias by exclusively using Windows Server images for the virtual machines, providing only Windows PowerShell commands for IIS installation and configuration, and referencing Windows-specific tools and patterns. There are no Linux VM examples, nor are there instructions for installing a web server on Linux (e.g., Apache or Nginx with Bash commands). The tutorial assumes the reader will use Windows throughout, omitting Linux alternatives.
Recommendations
  • Add parallel instructions for creating Linux-based VMs (e.g., Ubuntu) in the 'Create virtual machines' section.
  • Provide Linux shell (Bash) commands for installing and configuring a web server (e.g., Apache or Nginx) alongside the Windows PowerShell IIS instructions.
  • Explicitly mention that either Windows or Linux VMs can be used, and provide guidance for both.
  • Ensure screenshots and portal instructions do not assume a Windows-only workflow.
  • Where possible, use cross-platform terminology and examples, or clearly indicate OS-specific steps.
GitHub Create Pull Request
Load Balancer https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/backend-pool-management.md ...main/articles/load-balancer/backend-pool-management.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by providing extensive PowerShell examples before CLI examples, using Windows-centric tooling (Azure PowerShell), and showing VM creation steps that default to Windows Server images in PowerShell, while only mentioning Linux (Ubuntu) in the CLI section. There is no parity in OS examples across both toolsets, and Windows tools/patterns are prioritized.
Recommendations
  • Provide both Windows and Linux VM creation examples in PowerShell, not just Windows Server.
  • Ensure CLI and PowerShell examples are presented with equal prominence and order, or alternate which comes first.
  • Include notes or examples for common Linux administration scenarios (e.g., SSH key usage in PowerShell, not just Get-Credential).
  • Reference cross-platform tools and patterns, such as Azure CLI, Bash, or REST API, alongside PowerShell.
  • Explicitly mention that both PowerShell and CLI can be used on Windows, Linux, and macOS, and provide guidance for Linux users where appropriate.
GitHub Create Pull Request
Load Balancer https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/cross-subscription-how-to-attach-frontend.md ...-balancer/cross-subscription-how-to-attach-frontend.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias. Azure PowerShell (commonly used on Windows) is presented first in every code example section, with detailed PowerShell instructions and module references. The prerequisites and instructions for PowerShell are more prominent and detailed, including explicit module version checks and installation steps. The page also references PowerShell-specific patterns and tools before mentioning Azure CLI, which is more cross-platform and preferred by many Linux users. There is no mention of Bash scripting, Linux-specific considerations, or alternative shells, and the overall structure prioritizes Windows-centric workflows.
Recommendations
  • Alternate the order of PowerShell and Azure CLI examples so that CLI is presented first in some sections.
  • Add explicit Bash shell examples and instructions for Linux users, including environment setup and common patterns.
  • Include notes on using Azure CLI in Bash or other Linux shells, and clarify cross-platform compatibility.
  • Reduce the emphasis on PowerShell-specific module management and provide equivalent details for CLI installation and usage.
  • Add troubleshooting tips or references for common Linux issues (e.g., permissions, path differences) when using Azure CLI.
  • Ensure that documentation language and structure do not assume a Windows-first workflow.
GitHub Create Pull Request
Load Balancer https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/deploy-ipv4-ipv6-dual-stack-standard-load-balancer.md ...https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/deploy-ipv4-ipv6-dual-stack-standard-load-balancer.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a bias toward Windows environments. All virtual machine deployment examples use Windows Server images, and remote access instructions focus exclusively on RDP (Remote Desktop Protocol), which is a Windows-centric tool. There are no examples or instructions for deploying Linux VMs, nor are there any references to SSH, which is the standard remote access method for Linux. The PowerShell and Azure CLI examples only show Windows VM creation, and the ARM template snippets do not specify Linux images or configurations. This results in missing Linux parity and a perception that the solution is intended primarily for Windows workloads.
Recommendations
  • Add parallel examples for deploying Linux VMs (e.g., Ubuntu, CentOS) in both Azure CLI and PowerShell sections.
  • Include instructions and examples for configuring SSH access to Linux VMs, alongside RDP for Windows.
  • Mention Linux-friendly tools and patterns (such as using SSH keys, cloud-init, etc.) in the prerequisites and deployment steps.
  • Update ARM template sample snippets to show both Windows and Linux VM configurations.
  • Where remote access is discussed, clarify the difference between RDP (Windows) and SSH (Linux), and provide both sets of instructions.
  • Ensure screenshots and output samples include Linux VM scenarios as well as Windows.
GitHub Create Pull Request
Load Balancer https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/gateway-deploy-dual-stack-load-balancer.md ...ad-balancer/gateway-deploy-dual-stack-load-balancer.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation consistently presents PowerShell examples before Azure CLI, and references Windows-centric tools and patterns (e.g., PowerShell cmdlets, .ps1 file references, and Windows-style variable assignment). There is a notable emphasis on PowerShell, which is traditionally associated with Windows environments, and the prerequisite links and examples often default to PowerShell-based workflows. There is no mention of Linux-specific shell environments, nor are Bash or other Linux-native tools referenced.
Recommendations
  • Alternate the order of examples, sometimes presenting Azure CLI (which is cross-platform and native to Linux) before PowerShell.
  • Explicitly mention that both PowerShell and Azure CLI are available on Linux, macOS, and Windows, and provide guidance for Linux users (e.g., Bash shell usage, installation notes).
  • Include Bash script examples or references to Linux-native tooling where appropriate.
  • Avoid referencing only PowerShell-based prerequisite documentation; provide links to equivalent Azure CLI or Bash-based guides.
  • Clarify that all steps can be performed from Linux environments, and note any differences or caveats for Linux users.
GitHub Create Pull Request
Load Balancer https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/ipv6-add-to-existing-vnet-powershell.md .../load-balancer/ipv6-add-to-existing-vnet-powershell.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exclusively uses Azure PowerShell commands and Windows-centric tooling for all steps, with no mention or examples of equivalent Azure CLI, Bash, or Linux workflows. The prerequisites, resource management, and all configuration steps are presented only in PowerShell syntax, which is most familiar to Windows users. There is no guidance for Linux administrators or those preferring cross-platform tools, and the article title and structure reinforce a Windows-first approach.
Recommendations
  • Add equivalent Azure CLI (az) examples for each step, with Bash syntax, to support Linux and macOS users.
  • Include a section or alternate article for performing the same tasks using Azure CLI or REST API.
  • Mention that all operations can be performed using Azure CLI, and link to relevant documentation.
  • Clarify in the introduction that the instructions are PowerShell-specific and provide links to Linux-friendly alternatives.
  • Ensure parity in troubleshooting and cleanup steps, showing how to remove resources using Azure CLI.
  • Consider renaming the article or splitting it into platform-specific guides (PowerShell/Windows and CLI/Linux).
GitHub Create Pull Request
Load Balancer https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/load-balancer-basic-upgrade-guidance.md .../load-balancer/load-balancer-basic-upgrade-guidance.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by exclusively recommending and providing PowerShell scripts for automated migration, with no mention of Linux equivalents (such as Azure CLI, Bash, or cross-platform tools). The upgrade steps and automation guidance are Windows-centric, and Linux users are not provided with parity in tooling or examples.
Recommendations
  • Add Azure CLI and Bash script examples for automating the upgrade process, alongside PowerShell.
  • Explicitly mention cross-platform options and tools for migration, ensuring Linux users are supported.
  • Reorder or parallelize recommendations so that Windows and Linux automation options are presented together, rather than PowerShell first.
  • Include references to Linux-specific documentation or troubleshooting for common migration scenarios.
  • Clarify that the guidance applies to both Windows and Linux environments, and highlight any OS-specific considerations.
GitHub Create Pull Request
Load Balancer https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/load-balancer-distribution-mode.md ...icles/load-balancer/load-balancer-distribution-mode.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by providing detailed PowerShell instructions and referencing PowerShell in the next steps, while omitting explicit Linux/Bash examples. The CLI section is present, but there is no mention of Linux-specific considerations, and PowerShell is presented before CLI, which is more platform-neutral. There are no examples or notes for Linux users, nor is there guidance for using Bash or Linux-native tools.
Recommendations
  • Add explicit Bash/Linux shell examples alongside Azure CLI commands to demonstrate usage on Linux systems.
  • Include notes or sections addressing Linux-specific considerations, such as environment setup or differences in command syntax.
  • Balance the order of examples by presenting CLI (platform-neutral) before PowerShell, or provide tabs for Bash, PowerShell, and CLI.
  • Reference Linux-focused quickstarts or tutorials in the 'Next steps' section, not just PowerShell-based guides.
  • Clarify that Azure CLI commands can be run on Linux, macOS, and Windows, and provide links to installation instructions for each platform.
GitHub Create Pull Request
Load Balancer https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/ipv6-dual-stack-standard-internal-load-balancer-powershell.md ...-dual-stack-standard-internal-load-balancer-powershell.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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 examples use Azure PowerShell cmdlets, with no mention of Azure CLI, Bash, or Linux-native tools. VM creation is shown only for Windows Server images, and there are no instructions or examples for deploying Linux VMs or using Linux-friendly tools. The documentation assumes familiarity with PowerShell and Windows-centric workflows, and does not provide parity for Linux users.
Recommendations
  • Add equivalent Azure CLI (az) examples for each step, including resource group, network, load balancer, NIC, and VM creation.
  • Include examples for deploying Linux VMs (e.g., using Ubuntu or CentOS images) alongside Windows Server examples.
  • Mention and demonstrate how to use Bash or Cloud Shell (Bash) for these tasks, not just PowerShell.
  • Provide guidance on installing and using Azure CLI on Linux systems.
  • Ensure that documentation titles and descriptions clarify if the instructions are PowerShell-specific, and link to Linux/CLI alternatives.
  • Where possible, use cross-platform terminology and avoid assuming the user is on Windows.
GitHub Create Pull Request
Load Balancer https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/load-balancer-custom-probe-overview.md ...s/load-balancer/load-balancer-custom-probe-overview.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates Windows bias primarily by referencing PowerShell as the first and only example for getting started with Azure Load Balancer health probes. There are no Linux-specific examples, such as Azure CLI commands or Linux firewall configuration guidance. The documentation also refers to local firewall policies generically, but does not provide parity for Linux tools or workflows. This may make it less accessible for users managing Azure resources from Linux environments.
Recommendations
  • Add Linux-specific examples, such as Azure CLI commands for creating and managing health probes.
  • Include guidance for configuring Linux firewalls (e.g., iptables, firewalld, ufw) to allow probe traffic.
  • Provide parity in 'Next steps' by linking to Linux/CLI quickstarts alongside PowerShell.
  • When mentioning local firewall policies, explicitly reference both Windows (Windows Firewall) and Linux (iptables, firewalld, etc.) tools.
  • Ensure that all configuration and troubleshooting steps are presented for both Windows and Linux environments.
GitHub Create Pull Request
Load Balancer https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/load-balancer-manage-health-status.md ...es/load-balancer/load-balancer-manage-health-status.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Missing Linux Example Windows First
Summary
The documentation page demonstrates Windows bias primarily through its reference to Windows-specific tools (notably PowerShell's Get-AzAccessToken) for obtaining REST API access tokens, without mentioning equivalent Linux or cross-platform methods. The only guidance for authentication is via a PowerShell cmdlet, and there are no CLI, Bash, or Linux-native examples. This may hinder Linux users or those using non-Windows environments from easily following the instructions.
Recommendations
  • Include Azure CLI examples for obtaining the Bearer access token, such as 'az account get-access-token', which works cross-platform.
  • Add explicit instructions or code snippets for Linux/macOS users, e.g., using Bash and curl to make REST API calls.
  • Reference both PowerShell and CLI methods side-by-side when discussing authentication, ensuring parity for Windows and Linux users.
  • Avoid mentioning Windows tools (like PowerShell) exclusively or first; present cross-platform options together or in a neutral order.
  • Consider adding a dedicated section for Linux/macOS users, highlighting any differences or additional steps required.
GitHub Create Pull Request
Load Balancer https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/load-balancer-multiple-ip.md ...in/articles/load-balancer/load-balancer-multiple-ip.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Windows Server virtual machines and IIS (Internet Information Services) websites in the tutorial steps. There are no mentions of Linux VMs, Apache/Nginx, or Linux-specific configuration steps. All examples and instructions are implicitly or explicitly tailored to Windows environments, with no Linux alternatives provided.
Recommendations
  • Add parallel instructions and examples for deploying and configuring Linux virtual machines (e.g., Ubuntu or CentOS) alongside the Windows examples.
  • Include steps for installing and configuring common Linux web servers such as Apache or Nginx, and show how to bind multiple sites to different IP configurations.
  • Ensure that CLI and PowerShell examples are complemented by Linux shell (bash) commands where appropriate.
  • Update the checklist and tutorial overview to mention both Windows and Linux scenarios, making it clear that the tutorial supports both platforms.
  • Provide troubleshooting and testing steps that are relevant for Linux-based environments as well as Windows.
GitHub Create Pull Request
Load Balancer https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/load-balancer-nat-pool-migration.md ...cles/load-balancer/load-balancer-nat-pool-migration.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by providing extensive PowerShell examples and referencing PowerShell-specific modules and tools (e.g., Azure PowerShell, PowerShell Gallery). Automation and migration steps are described primarily using PowerShell, with prerequisites and installation instructions focused on Windows tooling. There are no Linux-specific shell (bash) or cross-platform scripting examples, and the PowerShell approach is presented before or in greater detail than Azure CLI alternatives. Linux users are not given parity in automation guidance or tool recommendations.
Recommendations
  • Add bash and/or cross-platform scripting examples for all migration steps, especially automation.
  • Include instructions for installing and using Azure CLI and related modules on Linux.
  • Provide parity in automation tooling, such as sample scripts using Azure CLI or Python SDK for Linux/macOS users.
  • Mention cross-platform compatibility and alternatives to PowerShell modules for users on non-Windows systems.
  • Reorder examples so that Azure CLI (cross-platform) is presented before PowerShell, or present both equally.
GitHub Create Pull Request
Load Balancer https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/load-balancer-tcp-idle-timeout.md ...ticles/load-balancer/load-balancer-tcp-idle-timeout.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell is presented as a primary automation method, with detailed instructions and prerequisites for installing and using PowerShell (a Windows-centric tool). The Azure CLI example is provided, but the PowerShell section appears before it, and there are no explicit Linux-specific instructions or examples (e.g., bash scripting, Linux shell environment setup). The guidance for environment validation and installation is generic but lacks Linux-specific context, such as package managers or shell differences.
Recommendations
  • Add explicit Linux shell examples (e.g., bash) for Azure CLI usage, including environment setup steps relevant to Linux (such as using apt, yum, or zypper for CLI installation).
  • Include notes or examples for configuring load balancer settings using Linux-native tools or automation (such as bash scripts or Ansible).
  • Reorder the sections so that Azure CLI (cross-platform) examples appear before PowerShell (Windows-centric) examples.
  • Clarify that Azure CLI works natively on Linux and macOS, and provide links or instructions for installing/updating CLI on those platforms.
  • If PowerShell is mentioned, note that PowerShell Core is available on Linux, and provide installation instructions for Linux users.
GitHub Create Pull Request
Load Balancer https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/load-balancer-troubleshoot-health-probe-status.md ...ncer/load-balancer-troubleshoot-health-probe-status.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Windows First Powershell Heavy Missing Linux Example
Summary
The documentation demonstrates a Windows bias by primarily referencing Windows-specific tools (PsPing, TCPing, Netsh), providing command prompt examples first, and giving more detailed instructions for Windows environments. Linux equivalents are mentioned only briefly and lack parity in explanation and example usage. There are no Linux-specific troubleshooting tools or step-by-step examples provided for Linux users.
Recommendations
  • Include Linux-native troubleshooting tools (e.g., nc, ss, nmap) with example commands for each troubleshooting step.
  • Provide step-by-step Linux command examples alongside Windows commands, not just brief mentions.
  • Offer parity in explanation for Linux firewall troubleshooting (e.g., using ufw, firewalld, or iptables with example commands).
  • Reference cross-platform tools where possible, or clarify which steps/tools apply to which OS.
  • Structure sections so that Windows and Linux approaches are presented equally, rather than Windows-first.
GitHub Create Pull Request
Load Balancer https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/load-balancer-troubleshoot.md ...n/articles/load-balancer/load-balancer-troubleshoot.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates Windows bias by providing troubleshooting examples and tool recommendations that are specific to Windows environments (e.g., PsPing, Netsh trace), without mentioning or giving equivalent Linux commands or tools. All example commands and diagnostic patterns are Windows-centric, and there are no Linux alternatives or parity in the troubleshooting steps.
Recommendations
  • Include Linux equivalents for all troubleshooting commands and tools, such as using 'ping', 'nc' (netcat), or 'ss' for connectivity tests, and 'tcpdump' or 'wireshark' for network captures.
  • Add explicit Linux example commands alongside Windows examples, ensuring parity in instructions for both platforms.
  • Mention Linux diagnostic patterns and tools before or alongside Windows tools, rather than exclusively or first.
  • Clarify that the troubleshooting steps apply to both Windows and Linux VMs, and provide platform-specific guidance where necessary.
GitHub Create Pull Request
← Previous Page 5 of 16 Next →