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 151-175 of 388 flagged pages
Load Balancer https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/basic/quickstart-basic-public-load-balancer-portal.md .../basic/quickstart-basic-public-load-balancer-portal.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation demonstrates a clear Windows bias, particularly in the VM creation and configuration steps. Only Windows Server images are used for the virtual machines, and the IIS installation instructions are exclusively for Windows, using PowerShell commands. There are no examples or guidance for creating or configuring Linux VMs, nor for installing a Linux web server (such as Apache or Nginx). All scripting and administrative steps are Windows-centric, and Linux users are not provided with equivalent instructions.
Recommendations
  • Provide parallel instructions for creating Linux VMs (e.g., Ubuntu or CentOS) alongside the Windows VM steps.
  • Include Linux-specific examples for installing a web server (e.g., Apache or Nginx) using bash commands.
  • Show how to connect to Linux VMs via SSH using Bastion, and provide sample commands for updating the web root.
  • Ensure that both Windows and Linux options are presented equally in tables and step-by-step guides.
  • Avoid assuming the use of Windows tools (like PowerShell) exclusively; offer bash or shell alternatives where appropriate.
GitHub Create Pull Request
Load Balancer https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/basic/quickstart-basic-internal-load-balancer-powershell.md ...https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/basic/quickstart-basic-internal-load-balancer-powershell.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
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, and there are no CLI, Bash, or Linux-native instructions. Virtual machines are provisioned with Windows Server images only, and IIS (a Windows web server) is installed using Windows-specific commands. The test steps reference Internet Explorer, a Windows-only browser, and there is no mention of Linux VMs, Apache/Nginx, or cross-platform alternatives.
Recommendations
  • Provide parallel Azure CLI (az) or Bash examples for all resource creation and management steps.
  • Include instructions for creating Linux virtual machines (e.g., Ubuntu) in addition to Windows Server VMs.
  • Demonstrate installation of a Linux web server (such as Apache or Nginx) using cloud-init or custom script extensions for Linux.
  • In testing steps, reference cross-platform browsers (e.g., Edge, Chrome, Firefox) and avoid Windows-only tools like Internet Explorer.
  • Clearly indicate at the top that the guide is Windows/PowerShell-specific, and link to equivalent Linux/CLI quickstarts if available.
  • Where possible, use neutral terminology and tools that work across platforms, or provide both Windows and Linux alternatives side by side.
GitHub Create Pull Request
Load Balancer https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/quickstart-load-balancer-standard-internal-template.md ...ttps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/quickstart-load-balancer-standard-internal-template.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation provides both Azure CLI and PowerShell examples, but PowerShell is mentioned first in the deployment section and is used in the initial deployment instructions. There are no explicit Linux shell (bash) examples or references to Linux-specific environments, and the PowerShell command for resource deletion is incorrectly placed under the CLI tab, which may confuse Linux users. The documentation assumes familiarity with PowerShell, which is more common on Windows, and does not address Linux users directly or provide guidance for running commands in a native Linux shell.
Recommendations
  • Ensure that Azure CLI (bash) examples are presented first or at least equally with PowerShell, as CLI is cross-platform and more familiar to Linux users.
  • Correct the 'Clean up resources' section: the CLI tab contains a PowerShell command. Replace it with the appropriate Azure CLI command (az group delete --name "${projectName}rg").
  • Explicitly mention that Azure CLI commands can be run in bash on Linux/macOS as well as in Cloud Shell, and clarify that PowerShell is optional.
  • Add guidance or links for Linux users on how to set up and use Azure CLI in their environment.
  • Where possible, include bash script examples for automation alongside PowerShell scripts.
GitHub Create Pull Request
Load Balancer https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/tutorial-multi-availability-sets-portal.md ...ad-balancer/tutorial-multi-availability-sets-portal.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation demonstrates a clear Windows bias: all virtual machine creation steps use Windows Server images by default, and the only example for configuring the backend web server uses PowerShell scripts to install IIS (a Windows-only web server). There are no examples or guidance for deploying Linux VMs, using Bash/SSH, or installing a Linux-based web server like Apache or Nginx. Windows tools and patterns (PowerShell, IIS) are used exclusively, with no mention of Linux equivalents.
Recommendations
  • Provide parallel instructions for creating Linux-based virtual machines (e.g., Ubuntu or CentOS) alongside the Windows Server examples.
  • Include example scripts for installing a web server on Linux VMs (e.g., using Bash to install Apache or Nginx via apt/yum).
  • Show how to use the Azure portal's Run Command feature with Bash scripts for Linux VMs, not just PowerShell for Windows.
  • Mention both Windows and Linux options in all relevant steps, including VM image selection and administrator account setup.
  • Add screenshots or code snippets that reflect both Windows and Linux scenarios.
  • Clarify in the prerequisites or introduction that the tutorial is applicable to both Windows and Linux, and provide links to Linux-specific documentation if available.
GitHub Create Pull Request
Load Balancer https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/cross-subscription-how-to-global-backend.md ...d-balancer/cross-subscription-how-to-global-backend.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation demonstrates a Windows bias by consistently presenting Azure PowerShell (a Windows-centric tool) instructions and examples before Azure CLI (cross-platform) equivalents. The structure and language prioritize PowerShell, and there is no mention of Linux-specific considerations, shells, or tooling. The use of PowerShell as the primary example and the presence of the 'devx-track-azurepowershell' custom metadata further reinforce the Windows-centric approach.
Recommendations
  • Alternate the order of examples so that Azure CLI (cross-platform) instructions are presented first in some sections, or present both equally without prioritizing one.
  • Explicitly mention that Azure CLI works natively on Linux, macOS, and Windows, and provide shell-specific notes where relevant.
  • Add a brief section or note on using Bash or other Linux shells with Azure CLI, including any differences in command syntax or environment setup.
  • Review metadata and custom tags to ensure they do not reinforce a PowerShell/Windows bias (e.g., avoid 'devx-track-azurepowershell' unless equally tracking CLI).
  • Where possible, provide guidance or troubleshooting tips for both Windows and Linux users, especially for environment setup and authentication steps.
GitHub Create Pull Request
Load Balancer https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/basic/quickstart-basic-internal-load-balancer-cli.md ...r/basic/quickstart-basic-internal-load-balancer-cli.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example Powershell Heavy 🔧 Windows Tools
Summary
The documentation exclusively demonstrates creating and configuring Windows Server-based virtual machines (using the 'win2019datacenter' image) and uses Windows-specific tools and commands (such as PowerShell and IIS). There are no examples or instructions for deploying or configuring Linux VMs, nor for installing or testing with Linux-based web servers. The instructions for installing IIS use PowerShell commands, and the test steps reference Internet Explorer, further reinforcing a Windows-centric approach.
Recommendations
  • Provide parallel examples for creating Linux-based VMs (e.g., using Ubuntu or CentOS images) alongside the Windows examples.
  • Include instructions for installing a web server on Linux VMs (e.g., using apt to install nginx or Apache) with corresponding az vm extension set commands.
  • Show how to test the load balancer using Linux tools (e.g., curl or wget) in addition to or instead of Internet Explorer.
  • Avoid assuming the use of Windows-only tools (such as PowerShell or Internet Explorer) and offer cross-platform alternatives.
  • Explicitly mention that the process works for both Windows and Linux VMs, and link to relevant documentation for Linux VM management where appropriate.
GitHub Create Pull Request
Load Balancer https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/tutorial-nat-rule-multi-instance-portal.md ...ad-balancer/tutorial-nat-rule-multi-instance-portal.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation shows a mild Windows bias in the 'Install web server' section, where users are instructed to open a PowerShell prompt on Windows and a Bash prompt on Mac/Linux, but all SSH command examples use Windows-style paths (e.g., '.\Downloads\myKey.pem') and do not provide a Linux/macOS equivalent. There are no explicit Linux/macOS command examples for SSH, and the documentation assumes familiarity with Windows conventions. Additionally, the order of instructions often lists Windows before Linux/macOS.
Recommendations
  • Provide both Windows (PowerShell/CMD) and Linux/macOS (Bash) command examples for SSH, with correct path syntax for each platform.
  • When instructing users to open a terminal, list Linux/macOS first or present both options equally.
  • Include notes or callouts clarifying path differences (e.g., '.\Downloads\myKey.pem' for Windows, '~/Downloads/myKey.pem' for Linux/macOS).
  • Wherever possible, avoid assuming a Windows environment; use cross-platform language and examples.
  • Consider adding screenshots or terminal output examples for both Windows and Linux/macOS environments.
GitHub Create Pull Request
Load Balancer https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/tutorial-cross-region-portal.md ...articles/load-balancer/tutorial-cross-region-portal.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. While it provides Azure Portal, Azure CLI, and Azure PowerShell instructions, several patterns indicate a preference for Windows-centric tools and workflows. PowerShell is given equal prominence to CLI, and Windows-specific technologies (such as IIS) are assumed in testing. There are no explicit Linux-specific examples or references (e.g., Apache/Nginx for backend VMs), and the documentation does not address Linux shell or scripting nuances, despite the CLI examples being generally cross-platform.
Recommendations
  • Include explicit Linux examples for backend pool VMs, such as using Apache or Nginx instead of only referencing IIS.
  • In test instructions, mention both Windows (IIS) and Linux (Apache/Nginx) default web pages to clarify cross-platform applicability.
  • Add notes or examples for running Azure CLI commands in Bash or other Linux shells, including handling of environment variables and command output.
  • Where PowerShell is referenced, clarify that it is available cross-platform, or provide Bash equivalents for common scripting patterns.
  • Review terminology and instructions to ensure they do not assume a Windows environment (e.g., file paths, shell commands, browser defaults).
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: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation exhibits a Windows bias by providing detailed PowerShell examples before Azure CLI, using Windows-centric tools and terminology (e.g., RDP, Windows images), and omitting explicit Linux/SSH examples for VM creation and access. The VM creation steps default to Windows Server images, and remote access is described only via RDP, with no mention of SSH or Linux images. There are no examples or guidance for deploying or accessing Linux VMs, nor are there instructions for Linux administrators.
Recommendations
  • Add explicit Linux/SSH examples for VM creation and remote access, including az vm create commands with --image UbuntuLTS and SSH key authentication.
  • Include guidance for both Windows and Linux VM images in all relevant steps, making it clear that either OS is supported.
  • Provide instructions for accessing VMs via SSH (for Linux) as well as RDP (for Windows), and clarify the differences.
  • Ensure that CLI and PowerShell examples are presented with equal prominence, or alternate which comes first.
  • Avoid using Windows-specific terminology (e.g., RDP) as the default; instead, use neutral language or mention both RDP and SSH.
  • Add troubleshooting or verification steps relevant to Linux environments (e.g., checking IPv6 connectivity from a Linux shell).
  • Where possible, use cross-platform tools and commands, or clearly indicate OS-specific steps.
GitHub Create Pull Request
Load Balancer https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/move-across-regions-azure-load-balancer.md ...ad-balancer/move-across-regions-azure-load-balancer.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides detailed instructions for moving Azure Load Balancers using the Azure portal and Azure PowerShell, but does not include any examples or guidance for Linux users or cross-platform CLI tools such as Azure CLI (az). All command-line examples are in PowerShell, and there are references to Windows-specific tools (e.g., notepad.exe). There is no mention of Bash, shell scripting, or Linux-native editors, which may hinder Linux or macOS users.
Recommendations
  • Add equivalent Azure CLI (az) command examples for all PowerShell steps, as Azure CLI is cross-platform and widely used on Linux and macOS.
  • Replace or supplement references to Windows-only tools (e.g., 'notepad.exe') with cross-platform alternatives (e.g., 'nano', 'vim', or 'code'), or use generic language like 'open the file in your preferred text editor'.
  • Explicitly mention that the steps can be performed on Linux/macOS using Azure CLI and standard text editors.
  • Where possible, provide Bash script snippets or guidance for users on non-Windows platforms.
  • Review all prerequisites and instructions to ensure they are not assuming a Windows environment by default.
GitHub Create Pull Request
Load Balancer https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/howto-load-balancer-imds.md ...ain/articles/load-balancer/howto-load-balancer-imds.md
High Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation page demonstrates a Windows-first bias by listing Windows/PowerShell instructions and links before Linux equivalents. The prerequisites and important notes reference Windows-specific documentation and tools (PowerShell, -NoProxy), and the sample request is presented for Windows before Linux. There is a heavier emphasis on PowerShell-specific parameters and troubleshooting, while Linux instructions are present but less detailed.
Recommendations
  • Provide Linux and Windows instructions in parallel, or list Linux first where appropriate.
  • Ensure all prerequisite and troubleshooting links have Linux equivalents and are not Windows-specific.
  • Expand Linux sections to include notes about proxy bypassing and curl options, matching the detail given for PowerShell.
  • Use neutral language and cross-platform links in introductory and prerequisite sections.
  • Where possible, provide a combined or platform-agnostic example before platform-specific tabs.
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: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation demonstrates a Windows bias by presenting PowerShell examples first and in greater detail, using Windows-centric tools and patterns (e.g., New-AzVMConfig with Windows image), and referencing Windows-specific VM images in PowerShell examples. Linux parity is only partially addressed in the CLI section, and the PowerShell section lacks Linux VM creation examples.
Recommendations
  • Provide both Windows and Linux VM creation examples in PowerShell, not just Windows.
  • Alternate the order of PowerShell and CLI sections or present them in parallel to avoid 'windows_first' bias.
  • Explicitly mention cross-platform compatibility of Azure PowerShell and show Linux image usage in PowerShell examples (e.g., Set-AzVMOperatingSystem -Linux).
  • Ensure that CLI examples are as detailed as PowerShell ones, including retrieval and update operations.
  • Add a note clarifying that both PowerShell and CLI are cross-platform and can be used on Windows, Linux, and macOS.
GitHub Create Pull Request
Load Balancer https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/basic/quickstart-basic-public-load-balancer-portal.md .../basic/quickstart-basic-public-load-balancer-portal.md
High Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example Powershell Heavy 🔧 Windows Tools
Summary
The documentation page demonstrates a clear Windows bias, especially in the 'Install IIS' section, where only Windows Server VMs and PowerShell commands are provided. There are no instructions or examples for deploying Linux VMs or installing a web server (such as Apache or Nginx) on Linux. The VM creation steps default to Windows Server images, and all post-deployment configuration is Windows-specific, with no Linux parity.
Recommendations
  • Add parallel instructions for creating Linux VMs (e.g., using Ubuntu or CentOS images) alongside the Windows VM steps.
  • Provide Linux-specific examples for installing a web server (such as Apache or Nginx) using bash commands (e.g., apt or yum) and updating the default web page.
  • Include both Windows and Linux options in the 'Image' selection step when creating VMs.
  • Show both PowerShell and bash/SSH command examples for post-deployment configuration.
  • Explicitly mention that the quickstart supports both Windows and Linux, and provide links to Linux-focused tutorials if available.
GitHub Create Pull Request
Load Balancer https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/basic/quickstart-basic-internal-load-balancer-cli.md ...r/basic/quickstart-basic-internal-load-balancer-cli.md
High Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example Powershell Heavy 🔧 Windows Tools
Summary
The documentation demonstrates a strong Windows bias. All virtual machine creation examples use Windows Server images (win2019datacenter), and the only provided instructions for configuring backend servers use PowerShell commands to install IIS (a Windows web server) via the CustomScriptExtension. There are no Linux VM examples, nor are there instructions for installing or configuring a web server on Linux. Additionally, the test instructions reference Internet Explorer, a Windows-only browser, and do not mention Linux alternatives.
Recommendations
  • Provide parallel examples for Linux virtual machines, such as using Ubuntu or CentOS images in the az vm create commands.
  • Include instructions for installing and configuring a web server (e.g., Apache or Nginx) on Linux VMs using the CustomScriptExtension with bash commands.
  • When referencing tools or browsers for testing (e.g., Internet Explorer), also mention Linux-compatible alternatives such as Firefox or Chromium.
  • Ensure that all scripts and automation steps have both Windows and Linux variants, and clearly label them.
  • Consider alternating the order of Windows and Linux examples or presenting them side-by-side to avoid 'windows_first' bias.
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: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by consistently presenting Azure PowerShell (typically used on Windows and in PowerShell environments) instructions and examples before Azure CLI (which is cross-platform and more common on Linux/macOS). The prerequisites and all procedural steps are introduced with PowerShell first, and the documentation metadata includes 'devx-track-azurepowershell', further emphasizing PowerShell. There are no Bash, Linux shell, or platform-specific notes for Linux users, and no mention of Linux tools or patterns. While Azure CLI examples are present, the overall structure and emphasis favor Windows/PowerShell users.
Recommendations
  • Alternate the order of PowerShell and CLI examples, or present CLI first to balance platform representation.
  • Explicitly mention that both PowerShell and CLI are cross-platform, but highlight that CLI is often preferred on Linux/macOS.
  • Add Bash shell snippets or Linux-specific notes where relevant, especially for environment setup and authentication.
  • Remove or balance metadata tags (such as 'devx-track-azurepowershell') to reflect equal support for CLI.
  • Where possible, provide context or links for Linux users (e.g., installing Azure CLI on Linux, using Bash scripting).
GitHub Create Pull Request
Load Balancer https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/basic/quickstart-basic-internal-load-balancer-portal.md ...asic/quickstart-basic-internal-load-balancer-portal.md
High Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation demonstrates a strong Windows bias. All VM creation steps use Windows Server images by default, and there are no Linux alternatives or examples provided. The IIS installation and configuration steps are exclusively shown using Windows PowerShell commands, with no mention of how to perform similar tasks on Linux VMs (e.g., using Apache or Nginx with Bash commands). Windows-specific tools and patterns (such as Internet Explorer, Windows PowerShell, and Windows Administrative Tools) are referenced throughout, with no Linux equivalents or parity.
Recommendations
  • Provide parallel instructions for creating Linux VMs (e.g., Ubuntu or CentOS) alongside Windows Server, including screenshots or configuration tables.
  • Include Linux-specific steps for installing a web server (such as Apache or Nginx) using Bash commands (e.g., apt or yum), and show how to create a custom index.html file.
  • Demonstrate how to connect to Linux VMs using SSH via Azure Bastion, and provide example commands for Linux terminal usage.
  • When referencing tools (e.g., PowerShell, Internet Explorer), also mention Linux alternatives (e.g., Bash, Firefox, or curl).
  • Ensure that all code snippets and configuration steps have both Windows and Linux variants, or clearly indicate if a step is Windows-only and provide guidance for Linux users.
GitHub Create Pull Request
Load Balancer https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/basic/quickstart-basic-public-load-balancer-cli.md ...cer/basic/quickstart-basic-public-load-balancer-cli.md
High Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example Powershell Heavy
Summary
The documentation demonstrates Windows bias primarily by provisioning only Windows Server virtual machines (using the 'win2019datacenter' image) and providing an IIS installation example that exclusively uses PowerShell commands. There are no Linux VM creation examples or instructions for installing a web server on Linux, and the only web server setup shown is for Windows/IIS. This omits guidance for users who wish to use Linux-based backend servers.
Recommendations
  • Provide parallel examples for creating Linux virtual machines (e.g., using the 'UbuntuLTS' image) alongside the Windows VM examples.
  • Include instructions and sample commands for installing a web server (such as Apache or Nginx) on Linux VMs using the CustomScriptExtension or cloud-init.
  • Present both Windows and Linux options for backend server setup, making it clear that either OS is supported.
  • Where scripts or commands are provided (e.g., for web server installation), offer both PowerShell (for Windows) and Bash/shell (for Linux) equivalents.
  • Explicitly mention that the load balancer works with both Windows and Linux VMs, and link to relevant Linux documentation where appropriate.
GitHub Create Pull Request
Load Balancer https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/basic/quickstart-basic-internal-load-balancer-powershell.md ...https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/basic/quickstart-basic-internal-load-balancer-powershell.md
High Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
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, and the only operating system referenced for VM creation and configuration is Windows Server. Steps for installing IIS and testing the load balancer are specific to Windows (e.g., using PowerShell commands, Internet Explorer, and Windows-specific VM images). There are no equivalent instructions or examples for Linux users, such as using Azure CLI, Bash, or deploying Linux VMs and web servers (e.g., Apache or Nginx).
Recommendations
  • Provide parallel examples using Azure CLI (az commands) and Bash scripts for all resource creation and configuration steps.
  • Include instructions and code samples for deploying Linux-based VMs (e.g., Ubuntu) in the backend pool, with examples of installing and configuring a Linux web server (such as Apache or Nginx) using cloud-init or custom script extensions.
  • When demonstrating VM creation, show both Windows and Linux image options, and explain how to set up credentials for each.
  • In the 'Test the load balancer' section, describe how to connect to a Linux VM (e.g., using SSH via Bastion or Cloud Shell) and test the web server using curl or a browser.
  • Avoid referencing Windows-only tools (like Internet Explorer) as the default; mention cross-platform alternatives.
  • Consider restructuring the documentation to present both Windows and Linux paths side-by-side, or provide clear navigation to Linux-specific quickstarts.
GitHub Create Pull Request
Load Balancer https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/concepts.md ...zure-docs/blob/main/articles/load-balancer/concepts.md
High Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates subtle Windows bias by referencing the creation of VMs with a custom IIS extension installed in the 'Next steps' section. IIS is a Windows-specific web server, and there is no mention of Linux-based alternatives or examples. There are no Linux-specific tools, patterns, or examples provided, nor is there parity in guidance for Linux users.
Recommendations
  • Include examples or references for deploying Linux-based VMs and web servers (such as Apache or Nginx) in the 'Next steps' section.
  • When mentioning IIS or Windows-specific technologies, also mention equivalent Linux options to ensure parity.
  • Provide links or guidance for both Windows and Linux scenarios when describing setup or configuration steps.
  • Review other documentation pages linked from this one to ensure Linux users are equally supported throughout the workflow.
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: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools Windows First
Summary
The documentation is heavily biased towards Windows and PowerShell usage. All examples and instructions are provided exclusively using Azure PowerShell cmdlets, with no mention of Azure CLI, Bash, or Linux-native tooling. The prerequisites and setup steps assume a PowerShell environment, and there are no alternative instructions for Linux users or those preferring cross-platform tools. The title and structure reinforce PowerShell as the default or only method.
Recommendations
  • Provide parallel examples using Azure CLI (az) commands, which are cross-platform and commonly used on Linux and macOS.
  • Include a section or callout at the beginning clarifying that the steps can be performed using either PowerShell or Azure CLI, and link to both sets of instructions.
  • Where possible, use neutral terminology (e.g., 'command line' instead of 'PowerShell') in headings and introductory text.
  • Add Linux/Bash-specific notes for any environment setup or prerequisites, such as installing Azure CLI or using the Azure Cloud Shell in Bash mode.
  • Ensure that all referenced tools and modules have Linux-compatible alternatives or clearly state if a step is Windows/PowerShell-only.
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: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides detailed instructions for configuring Azure Load Balancer distribution mode using the Azure portal, PowerShell, and Azure CLI. However, it shows a Windows bias by presenting PowerShell instructions before CLI, referencing a PowerShell-based quickstart in the 'Next steps', and not providing explicit Linux/Bash examples or guidance. The CLI section is generic and does not clarify cross-platform usage, and there are no Bash or Linux-specific notes or troubleshooting tips.
Recommendations
  • Add explicit Bash/Linux shell examples for the Azure CLI section, including sample commands and expected outputs.
  • Clarify that Azure CLI commands work cross-platform and provide any Linux-specific prerequisites or troubleshooting tips.
  • Balance the order of examples by presenting CLI (cross-platform) instructions before or alongside PowerShell, or clearly indicate platform applicability.
  • Include a 'Next steps' link to a Linux/Bash-based quickstart or tutorial, not just PowerShell.
  • If relevant, mention any differences in behavior or setup between Windows and Linux environments.
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: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates a Windows bias by exclusively recommending and providing PowerShell scripts for automation, with no mention of Azure CLI, Bash, or Linux-native tooling. The 'automated scripts' section only references PowerShell, and the manual steps reference the Azure Portal (which is cross-platform, but the automation focus is Windows-centric). There are no Linux or cross-platform command-line examples, and the guidance implicitly assumes a Windows/PowerShell environment.
Recommendations
  • Provide equivalent Azure CLI scripts/examples for all PowerShell automation steps, ensuring Linux and macOS users have parity.
  • Explicitly mention that automation can be performed using Azure CLI or ARM templates, not just PowerShell.
  • When referencing 'automated scripts', offer both PowerShell and Azure CLI/Bash options, and link to relevant documentation for each.
  • Ensure that any step recommending PowerShell also includes a Linux-friendly alternative, or at least acknowledges the option.
  • Consider reordering or presenting automation options in a neutral way (e.g., 'Use these scripts: PowerShell | Azure CLI'), rather than PowerShell-only.
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: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page exhibits Windows bias primarily through its 'Next steps' section, which features a PowerShell-based quickstart as the only explicit example for creating a public load balancer. There are no Linux/Unix CLI (Azure CLI, Bash) examples or references, and no mention of Linux-specific tools or workflows. The documentation does not provide parity for Linux users in terms of example commands or guidance, and the only automation example is Windows-centric (PowerShell).
Recommendations
  • Add Azure CLI (cross-platform) examples alongside or before PowerShell examples for all relevant tasks, especially in the 'Next steps' and any quickstart sections.
  • Include Bash or shell command examples where appropriate, especially for probe testing or firewall configuration.
  • Ensure that references to automation or scripting tools are balanced between Windows (PowerShell) and Linux (Azure CLI, Bash).
  • Explicitly mention that all configuration steps can be performed on both Windows and Linux platforms, and provide links to Linux-focused tutorials or documentation.
  • Review all example links and ensure that for every PowerShell example, there is an equivalent Azure CLI or Linux shell example.
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: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Missing Linux Example Windows First
Summary
The documentation page demonstrates a Windows bias by referencing the PowerShell cmdlet Get-AzAccessToken as the only example for obtaining a Bearer access token, without mentioning equivalent Linux or cross-platform CLI methods. No Azure CLI, Bash, or Linux-native instructions are provided for authentication or token retrieval. The only tool referenced for token acquisition is a Windows-centric PowerShell module, and no Linux-first or cross-platform alternatives are presented.
Recommendations
  • Add Azure CLI examples (e.g., 'az account get-access-token') for obtaining the Bearer access token, which works cross-platform (Windows, Linux, macOS).
  • Include Bash shell command examples for REST API calls using curl, demonstrating how to authenticate and retrieve health status from Linux environments.
  • Mention both PowerShell and CLI methods in parallel, or present CLI/Bash examples before or alongside PowerShell to avoid a 'Windows-first' impression.
  • Explicitly state that the REST API and Azure CLI methods are supported on all platforms, and provide links to relevant Linux/macOS documentation.
  • Where possible, avoid referencing only Windows-specific tools (like Get-AzAccessToken) without cross-platform alternatives.
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: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools Windows First
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-based workflows. The VM creation steps specifically use Windows Server images, and the only remote access method shown is RDP (port 3389), which is Windows-specific. There are no Linux VM examples, nor are there instructions for SSH or Linux image deployment. The documentation assumes the user is working in a Windows/PowerShell environment throughout.
Recommendations
  • Provide parallel examples using Azure CLI (az commands) and Bash scripts for all resource creation steps.
  • Include Linux VM deployment examples (e.g., using Ubuntu or CentOS images) alongside or instead of Windows Server.
  • Show how to configure SSH access (port 22) in the network security group rules, not just RDP.
  • Explicitly mention that the steps can be performed from Linux/macOS using Azure CLI or Cloud Shell, and provide relevant instructions.
  • Reorganize the documentation to present cross-platform options equally, rather than focusing exclusively on PowerShell/Windows.
  • Add a section or callout for Linux users, highlighting any differences or considerations.
GitHub Create Pull Request
← Previous Page 7 of 16 Next →