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 126-150 of 388 flagged pages
Load Balancer https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/manage-inbound-nat-rules.md ...ain/articles/load-balancer/manage-inbound-nat-rules.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 demonstrates a moderate Windows bias. PowerShell is featured prominently as a primary automation method alongside the Azure portal and CLI, with detailed step-by-step instructions and code samples. The prerequisites and instructions reference Windows-specific tools (PowerShell) and patterns, such as module installation and usage, without mentioning Linux shell equivalents or alternatives (e.g., Bash, Cloud Shell, or native Linux scripting). The CLI examples are present, but PowerShell is often listed before CLI, and there is no explicit mention of Linux-specific considerations or parity in the examples.
Recommendations
  • Add explicit Bash shell examples for Linux users, especially for CLI commands, showing how to run them in native Linux environments.
  • Clarify that Azure CLI is fully cross-platform and can be used on Linux, macOS, and Windows, and provide installation links for all platforms.
  • In the prerequisites, mention how to prepare the environment for Linux (e.g., installing Azure CLI via apt, yum, or curl), and reference Azure Cloud Shell as a platform-agnostic option.
  • Avoid listing PowerShell before CLI, or alternate the order to avoid perceived prioritization.
  • Where PowerShell-specific instructions are given, provide equivalent Bash or Linux shell scripting examples if possible.
  • Explicitly state that all operations can be performed from Linux, macOS, or Windows, and highlight any platform-specific caveats.
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: 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 provides detailed instructions for moving Azure Load Balancers between regions using the Azure portal and Azure PowerShell, with all CLI examples and automation scripts exclusively using PowerShell cmdlets. There are no examples or guidance for Linux users, such as using Azure CLI (az) or bash scripting, and references to tools like 'notepad.exe' and PowerShell-specific commands reinforce a Windows-centric approach. The structure and examples prioritize Windows/PowerShell workflows, leaving Linux users without parity or clear alternatives.
Recommendations
  • Add equivalent step-by-step instructions using Azure CLI (az) commands for all PowerShell examples.
  • Include bash shell scripting examples for template editing and deployment.
  • Replace or supplement references to 'notepad.exe' with cross-platform editors (e.g., 'nano', 'vim', 'code').
  • Explicitly mention that all procedures can be performed on Linux/macOS using Azure CLI and provide links to relevant documentation.
  • Ensure that references to obtaining resource IDs, editing JSON files, and deploying templates include both PowerShell and Azure CLI methods.
  • Where possible, use generic terminology (e.g., 'open your preferred text editor') instead of Windows-specific instructions.
GitHub Create Pull Request
Load Balancer https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/quickstart-load-balancer-standard-public-bicep.md ...ncer/quickstart-load-balancer-standard-public-bicep.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 demonstrates a bias towards Windows environments. The only example of VM configuration is for Internet Information Services (IIS), a Windows web server, with no mention of Linux alternatives (e.g., Apache, Nginx). The review of deployed resources references IIS exclusively. While deployment instructions include both Azure CLI and PowerShell, the post-deployment validation and examples are Windows-centric, and there are no Linux-specific instructions or screenshots.
Recommendations
  • Include examples and instructions for deploying and validating Linux-based VMs (e.g., using Apache or Nginx).
  • Add screenshots and validation steps for Linux web servers alongside IIS.
  • Mention Linux VM extensions and provide sample configuration for Linux environments.
  • Ensure that both Windows and Linux scenarios are presented equally in all sections, especially in testing and validation.
  • Clarify that the quickstart works for both Windows and Linux VMs, and provide guidance for choosing between them.
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-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 page demonstrates a strong Windows bias. All virtual machine creation examples use Windows images (win2022datacenter, Win2019Datacenter) with no mention of Linux alternatives. The IIS installation and configuration is performed using PowerShell commands via CustomScriptExtension, with no Linux equivalent (e.g., Apache or Nginx) provided. The testing instructions direct users to use Internet Explorer on the test VM, further reinforcing Windows-centric guidance. There are no examples or instructions for deploying, configuring, or testing with Linux VMs or tools.
Recommendations
  • Provide parallel examples for Linux VM deployment (e.g., using Ubuntu or CentOS images).
  • Include instructions for installing and configuring a web server on Linux VMs (e.g., Apache or Nginx) using Bash scripts.
  • Offer testing steps using Linux tools (e.g., curl, wget, or a browser like Firefox) on a Linux test VM.
  • Explicitly mention that the Azure CLI commands work cross-platform and highlight any OS-specific considerations.
  • Ensure that both Windows and Linux options are presented equally throughout the documentation, including screenshots and command snippets.
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: 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 demonstrates a moderate Windows bias. PowerShell is featured prominently alongside Azure CLI, with PowerShell-specific commands and patterns shown in all deployment, review, and cleanup steps. In the cleanup section, the PowerShell command is incorrectly placed under the CLI tab, and PowerShell is often mentioned first or equally with CLI. There are no Linux-specific shell examples (e.g., bash), and the documentation assumes familiarity with PowerShell, a Windows-centric tool, rather than providing parity for Linux users.
Recommendations
  • Ensure that Azure CLI (bash) examples are given equal or greater prominence than PowerShell, as Azure CLI is cross-platform and more familiar to Linux users.
  • Correct tab labeling in the cleanup section to avoid confusion (PowerShell command is under CLI tab).
  • Add explicit bash shell examples and instructions for Linux/macOS users, including environment setup and command usage.
  • Clarify that both Azure CLI and PowerShell are cross-platform, but highlight bash usage for Linux users.
  • Avoid assuming PowerShell as the default scripting language; provide clear, parallel instructions for both environments.
  • Where possible, include screenshots or terminal output from both Windows (PowerShell) and Linux (bash) environments.
GitHub Create Pull Request
Load Balancer https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/quickstart-load-balancer-standard-public-cli.md ...lancer/quickstart-load-balancer-standard-public-cli.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 Powershell Heavy
Summary
The documentation demonstrates Windows bias in several ways: the only VM images used are Windows (win2019datacenter), and the only example for installing a web server uses Windows-specific PowerShell commands to install IIS. There are no examples for deploying Linux VMs or installing a Linux web server (e.g., Apache or Nginx). The VM creation and extension setup steps are exclusively tailored to Windows, with no mention of Linux alternatives.
Recommendations
  • Provide parallel examples for Linux VMs (e.g., using Ubuntu or CentOS images) alongside Windows examples.
  • Include instructions and az vm extension set commands for installing a web server on Linux VMs (e.g., using CustomScriptExtension to install Apache or Nginx).
  • Explicitly mention both Windows and Linux options when creating VMs and configuring backend servers.
  • Ensure that testing instructions (e.g., browsing to the public IP) clarify expected results for both Windows (IIS) and Linux (Apache/Nginx) scenarios.
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-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 bias toward Windows by providing only Azure PowerShell deployment instructions and examples, with no equivalent Azure CLI (bash) or Linux shell examples. The use of PowerShell is presented as the primary method for deploying the ARM template, and Windows-centric tools (such as IIS) are referenced without mention of Linux alternatives. Although the page briefly mentions that other deployment methods exist, it does not provide guidance or examples for Linux users.
Recommendations
  • Add Azure CLI (bash) deployment instructions and examples alongside PowerShell, ensuring Linux users have clear guidance.
  • Include screenshots or output examples from Azure CLI deployments to match the PowerShell visuals.
  • Mention Linux-friendly web server alternatives (e.g., Apache, Nginx) in addition to IIS, or provide instructions for configuring them.
  • Explicitly state parity between PowerShell and CLI methods, and link to relevant Linux documentation.
  • Reorder or parallelize instructions so that Windows and Linux methods are presented with equal prominence.
GitHub Create Pull Request
Load Balancer https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/quickstart-load-balancer-standard-public-portal.md ...cer/quickstart-load-balancer-standard-public-portal.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools Windows First
Summary
The documentation page exhibits a strong Windows bias in the VM configuration section. Only Windows PowerShell commands are provided for installing and configuring IIS on the backend VMs, with no mention of Linux alternatives or examples. The instructions and screenshots focus exclusively on Windows tools and workflows, implicitly assuming the use of Windows Server VMs. There is no guidance for users deploying Linux VMs or using Linux-native web servers such as Apache or Nginx.
Recommendations
  • Add parallel instructions for Linux VMs, including steps for connecting via SSH and installing/configuring a web server (e.g., Apache or Nginx) using bash commands.
  • Provide both Windows and Linux code examples for server setup, clearly labeling each for the relevant OS.
  • Include screenshots or terminal output for Linux workflows where appropriate.
  • Explicitly mention that the load balancer works with both Windows and Linux VMs, and link to further documentation for Linux-based deployments.
  • Avoid assuming Windows as the default platform; present OS options up front and allow users to choose their preferred environment.
GitHub Create Pull Request
Load Balancer https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/tutorial-create-gateway-load-balancer.md ...load-balancer/tutorial-create-gateway-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 provides parity between Azure Portal, Azure CLI, and Azure PowerShell, but there is a noticeable Windows bias. PowerShell (a Windows-centric tool) is given equal prominence to Azure CLI, and in some places, PowerShell-specific instructions and troubleshooting steps (such as module installation and version checks) are included. The documentation refers to 'Azure PowerShell installed locally' and gives instructions for running PowerShell commands locally, which is primarily a Windows workflow. There are no explicit Linux shell examples (e.g., bash scripts), and no mention of Linux-specific tools or workflows. The CLI examples are generic and could be run from either Windows or Linux, but the documentation does not clarify or encourage Linux usage. PowerShell is presented as a first-class option, which may implicitly suggest a Windows-first approach.
Recommendations
  • Explicitly mention that Azure CLI commands work natively on Linux, macOS, and Windows, and encourage use from Linux shells (bash, zsh) where appropriate.
  • Provide bash script equivalents or examples for common tasks, especially in sections where PowerShell scripting is shown.
  • Clarify that Azure PowerShell can be used on Linux and macOS via PowerShell Core, and provide installation instructions for those platforms.
  • Where troubleshooting or setup steps are given for PowerShell (e.g., module installation), offer equivalent steps for Azure CLI on Linux (e.g., package manager installation, updating CLI).
  • Consider listing Azure CLI examples before PowerShell examples to reduce implicit Windows-first bias.
  • Add notes or callouts for Linux users, such as environment setup, shell compatibility, and common Linux workflows.
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: 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 demonstrates a Windows bias by exclusively referencing Windows-centric tools and patterns, such as IIS for backend testing and PowerShell for scripting. The test instructions assume IIS is installed on backend VMs, which is a Windows-only web server, and there are no examples or references for Linux-based backend pools (e.g., Apache, Nginx). While Azure CLI is cross-platform, the tutorial does not provide Linux-specific guidance, such as using SSH, Bash, or Linux-native web servers. PowerShell examples are given equal prominence, but no Bash or Linux shell scripting alternatives are offered. The documentation also refers to Windows tools (PowerShell, IIS) before or instead of Linux equivalents.
Recommendations
  • Add explicit examples for Linux-based backend pools, such as using Apache or Nginx instead of IIS.
  • Include instructions for testing the load balancer using curl or wget from a Linux terminal, not just a browser.
  • Provide Bash shell script equivalents for resource creation and management alongside PowerShell examples.
  • Clarify that Azure CLI commands work on Linux, macOS, and Windows, and show Linux-specific usage patterns (e.g., using environment variables, SSH).
  • Mention how to install and use Azure CLI and Cloud Shell on Linux systems.
  • Balance references to Windows and Linux tools, ensuring Linux administrators see their workflows represented.
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-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, especially in the VM creation and configuration sections. Only Windows Server is used as the VM image, and all instructions for installing and configuring IIS are given using Windows PowerShell. There are no Linux VM examples, nor any equivalent instructions for deploying a web server on Linux (e.g., Apache or Nginx). Windows-specific tools and patterns (PowerShell, Windows Administrative Tools) are mentioned exclusively, with no mention of Linux alternatives.
Recommendations
  • Provide parallel instructions for creating and configuring Linux VMs, including selecting a Linux image (e.g., Ubuntu) during VM creation.
  • Include Linux-specific steps for installing a web server (e.g., Apache or Nginx) and updating the default web page, using bash commands.
  • Offer both Windows and Linux examples side-by-side in relevant sections, especially for server setup and testing.
  • Reference Linux tools (e.g., SSH, bash) and patterns where appropriate, not just Windows tools.
  • Explicitly state that the tutorial works for both Windows and Linux VMs, and link to further documentation for each OS.
GitHub Create Pull Request
Load Balancer https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/tutorial-load-balancer-port-forwarding-portal.md ...ancer/tutorial-load-balancer-port-forwarding-portal.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 demonstrates a mild Windows bias in its instructions for connecting to VMs via SSH. It explicitly mentions opening a PowerShell prompt for Windows users and a Bash prompt for Mac/Linux users, but the SSH command example uses Windows path syntax ('.\Downloads\lb-key-pair.pem'), which is not valid on Linux/Mac. There are no Linux-specific command examples for the SSH key path, and no mention of Linux terminal conventions. The rest of the tutorial is platform-neutral, focusing on Azure portal UI steps, but the only command-line example is Windows-centric.
Recommendations
  • Provide both Windows and Linux/Mac command examples for SSH, including correct path syntax (e.g., './Downloads/lb-key-pair.pem' for Linux/Mac).
  • Explicitly mention how to open a terminal on Linux/Mac and Windows, and clarify the differences in file path conventions.
  • Consider listing Linux/Mac instructions before or alongside Windows instructions to avoid 'windows_first' ordering.
  • Add a note about file permissions for the SSH key on Linux/Mac (e.g., 'chmod 600 lb-key-pair.pem').
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: 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 strong Windows bias: all VM creation steps use Windows Server images exclusively, and the only example for configuring backend web servers uses Windows-specific tools (PowerShell and IIS). There are no Linux VM options, nor are there Bash/SSH or Apache/Nginx instructions. The tutorial assumes Windows as the default platform for both deployment and configuration, omitting Linux alternatives entirely.
Recommendations
  • Add parallel instructions for creating Linux-based VMs (e.g., Ubuntu, CentOS) in the portal steps.
  • Provide Linux-specific configuration examples, such as installing Apache or Nginx via Bash/SSH, alongside the IIS/PowerShell steps.
  • Include sample Bash scripts for Linux VM setup, and show how to use the Azure portal's Run Command feature with Linux commands.
  • Explicitly mention that both Windows and Linux VMs are supported in backend pools, and link to relevant Linux documentation.
  • Ensure screenshots and walkthroughs show both Windows and Linux scenarios where applicable.
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: 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 demonstrates a subtle Windows bias in several areas. When instructing users to open a terminal for SSH, it lists Windows/PowerShell before Mac/Linux/Bash. The SSH command examples use Windows path syntax ('.\Downloads\myKey.pem'), which may confuse Linux/Mac users. There are no explicit Linux/Mac command examples for SSH, nor is there guidance on file permissions or path differences for those platforms. The documentation does not mention Linux tools or patterns (e.g., chmod for key files) and generally assumes a Windows-centric workflow.
Recommendations
  • Provide both Windows/PowerShell and Linux/Mac/Bash SSH command examples, with correct path syntax for each.
  • Mention file permission requirements for Linux/Mac (e.g., 'chmod 600 myKey.pem').
  • List Mac/Linux instructions before or alongside Windows instructions to avoid ordering bias.
  • Explicitly state differences in terminal usage and file paths between platforms.
  • Include troubleshooting tips for common Linux/Mac SSH issues (e.g., permissions, path).
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: 2025-07-17 00:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example Powershell Heavy
Summary
The documentation page exhibits subtle Windows bias. For example, the only explicit link to a hands-on guide for creating a dual stack application refers to a PowerShell-based tutorial (which is Windows-centric), and there are no visible Linux or cross-platform CLI examples or references. The documentation does not mention Linux tools or provide parity in example commands or scripts. This could make Linux users feel less supported or require extra effort to find relevant guidance.
Recommendations
  • Add equivalent Linux/bash/Azure CLI examples and links wherever PowerShell or Windows-specific instructions are referenced.
  • Ensure that links to tutorials or how-to guides (e.g., for creating dual stack applications) include both PowerShell and Azure CLI/Bash options, and mention both in the main documentation.
  • Wherever possible, use cross-platform tools (such as Azure CLI) in examples, or provide both PowerShell and Bash/Azure CLI snippets side by side.
  • Explicitly mention Linux support and tools in relevant sections to reassure non-Windows users that their platforms are equally supported.
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-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation displays a mild Windows bias: Windows/PowerShell examples and links are presented before Linux equivalents, and references to Windows-specific tools and documentation are more prominent. The prerequisites and important notes link only to Windows-specific IMDS documentation, and troubleshooting/learning links default to Windows tabs. While a Linux example is present, Linux documentation is less emphasized.
Recommendations
  • Present Linux and Windows examples in parallel or in a neutral order, or default to a platform-agnostic example.
  • Ensure all documentation links (e.g., prerequisites, further reading) include both Windows and Linux versions or use platform-neutral links.
  • Add Linux-specific notes where relevant (e.g., proxy bypassing in curl).
  • Avoid referencing Windows tools or documentation exclusively; mention Linux equivalents with equal prominence.
  • Consider a 'Platform' selector at the top of the page to allow users to choose their OS context.
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: 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 is heavily biased towards Windows environments. It only references the creation of Windows server virtual machines, uses Windows-specific tools (IIS), and provides PowerShell examples. There are no mentions or examples for Linux VMs, Linux web servers (such as Apache or Nginx), or Linux command-line tools. The steps and examples are tailored exclusively to Windows users, leaving Linux users without guidance.
Recommendations
  • Add parallel instructions and examples for creating and configuring Linux virtual machines.
  • Include steps for setting up popular Linux web servers (e.g., Apache, Nginx) alongside IIS.
  • Provide Linux CLI examples (using Bash/Azure CLI) for all configuration steps.
  • Ensure that portal, CLI, and PowerShell sections all include Linux-specific guidance where relevant.
  • Mention Linux as an option in the tutorial introduction and checklist, not just Windows.
  • Balance the order of presentation so that Linux and Windows are given equal prominence.
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: 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 Windows bias by prioritizing Windows tools (PsPing, TCPing, netstat, netsh) in troubleshooting steps, providing Windows command examples first or exclusively, and only briefly mentioning Linux equivalents (netstat -l, sudo iptables -L) as secondary notes. There are no Linux-specific troubleshooting tools or detailed Linux command examples, and the overall troubleshooting workflow assumes a Windows environment.
Recommendations
  • Provide Linux-first or parallel Linux command examples alongside Windows commands for each troubleshooting step.
  • Include Linux-native tools (e.g., ss, nc/ncat, lsof, firewalld-cmd, ufw) for port and firewall checks, with example commands.
  • Offer example commands for both Windows and Linux for connectivity testing (e.g., using nc or curl for Linux instead of only PsPing/TCPing).
  • Explicitly state that the instructions apply to both Windows and Linux VMs, and structure sections so that Linux and Windows guidance are equally prominent.
  • Where third-party tools are suggested (PsPing, TCPing), recommend open-source or pre-installed Linux alternatives and provide installation instructions if needed.
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-13 21:37
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, setup, and resource management steps all assume a PowerShell environment, and there are no alternative instructions or code samples for Linux users. The article title and repeated references to PowerShell reinforce this bias.
Recommendations
  • Provide equivalent Azure CLI (az) command examples for each PowerShell example, ideally side-by-side or in separate tabs.
  • Update the article title and description to reflect cross-platform support, or create a parallel article for Azure CLI/Linux users.
  • Add a section on how to perform these tasks using Bash or in the Azure Cloud Shell with Bash.
  • Mention both PowerShell and CLI options in the prerequisites and setup sections, including installation links for both.
  • Ensure that references to tools and commands do not assume a Windows environment by default.
  • Where possible, use neutral language (e.g., 'using Azure PowerShell or Azure CLI') and avoid Windows-first phrasing.
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-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates Windows bias primarily through its exclusive reference to the Windows PowerShell cmdlet (Get-AzAccessToken) for obtaining a Bearer access token, without mentioning Linux or cross-platform alternatives. There are no CLI or Bash examples, and the only tool referenced for authentication is a Windows-centric PowerShell module. This may hinder Linux users or those using non-Windows environments from easily following the instructions.
Recommendations
  • Provide equivalent Azure CLI (az account get-access-token) instructions for obtaining a Bearer access token, which works on Windows, Linux, and macOS.
  • Include Bash/cURL examples for making REST API requests, not just REST request syntax.
  • Avoid referencing only PowerShell modules; when mentioning tools, list cross-platform options first or alongside Windows-specific tools.
  • Explicitly state that the instructions apply to all platforms, and provide links to relevant Linux/macOS guidance where appropriate.
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: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by only referencing Windows Server (IIS) as the web server deployed on the virtual machines, with no mention of Linux alternatives. The verification step specifically instructs users to expect the default IIS Windows Server web page, and the template configures IIS, which is Windows-specific. There are no examples or guidance for deploying or verifying with a Linux-based web server (e.g., Apache, Nginx), nor are there any Linux command-line or deployment instructions.
Recommendations
  • Include parallel instructions and screenshots for deploying and verifying a Linux-based web server (such as Apache or Nginx) in addition to IIS.
  • Modify the ARM template or provide an alternative template that configures a Linux VM with a popular web server.
  • In the verification section, show what users should expect if they deployed a Linux VM (e.g., default Apache/Nginx page).
  • Explicitly mention that the tutorial can be followed with either Windows or Linux VMs, and provide parameter options or guidance for both.
  • Avoid assuming Windows as the default platform; present both Windows and Linux options equally throughout the documentation.
GitHub Create Pull Request
Load Balancer https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/quickstart-load-balancer-standard-public-bicep.md ...ncer/quickstart-load-balancer-standard-public-bicep.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 Azure PowerShell deployment instructions, but PowerShell is given equal prominence despite being Windows-centric. The example workload is Internet Information Services (IIS), a Windows-only web server, with no mention of Linux alternatives. There are no Linux-specific examples or guidance for deploying or testing with Linux-based VMs or tools.
Recommendations
  • Include Linux-focused deployment and testing examples, such as using Apache or Nginx on Linux VMs.
  • Provide explicit instructions for connecting to Linux VMs (e.g., SSH) and verifying deployment from a Linux perspective.
  • Clarify that Azure CLI is cross-platform and recommend it as the default for broader compatibility.
  • Add a Linux tab or section alongside PowerShell for parity, especially in deployment and validation steps.
  • Show how to configure and test the load balancer with both Windows and Linux backend VMs.
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-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 page demonstrates a significant Windows bias. All VM creation steps use Windows Server images by default, and there are no instructions or examples for deploying or configuring Linux VMs. The IIS installation and configuration are provided exclusively with Windows PowerShell commands, and the test instructions assume the use of Internet Explorer. No Linux alternatives (such as Apache/Nginx installation, Bash commands, or Linux VM images) are mentioned or offered.
Recommendations
  • Provide parallel instructions for creating Linux VMs (e.g., Ubuntu or CentOS) alongside Windows VMs.
  • Include Linux-specific steps for installing a web server (such as Apache or Nginx) using Bash commands.
  • Offer both PowerShell (Windows) and Bash (Linux) command examples for server configuration.
  • When referencing tools (e.g., Internet Explorer), mention Linux equivalents (e.g., Firefox, curl, wget).
  • Explicitly state that the process works for both Windows and Linux VMs, and link to relevant Linux documentation.
  • Consider alternating the order of Windows and Linux examples, or presenting them side-by-side for parity.
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-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 presenting PowerShell examples first and in greater detail, using Windows-centric tooling (Azure PowerShell), and providing a Windows Server image in the PowerShell VM creation example. While CLI examples are present and include a Linux (Ubuntu) image, the PowerShell section is more comprehensive and implicitly assumes a Windows environment, especially for VM provisioning.
Recommendations
  • Provide both PowerShell and CLI examples in parallel for each step, ensuring parity in detail and coverage.
  • In PowerShell VM creation examples, include both Windows and Linux image options, or use a neutral example.
  • Explicitly mention that Azure PowerShell can be used cross-platform, or provide Bash/Cloud Shell alternatives where possible.
  • Avoid defaulting to Windows Server images in examples; alternate or provide both Windows and Linux image options.
  • Consider starting with CLI examples or alternating the order to avoid 'windows_first' bias.
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-13 21:37
Reviewed by: Unknown
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 linking to PowerShell scripts for automation, with no mention of Azure CLI, Bash, or Linux-based automation alternatives. The term 'PowerShell' is used as the default and only automation method, and there are no Linux/Unix command examples or references to cross-platform tooling. Manual steps reference the Azure Portal, which is cross-platform, but all scripting guidance is Windows-centric.
Recommendations
  • Provide equivalent Azure CLI scripts for all PowerShell automation examples, and link to them alongside the PowerShell scripts.
  • Explicitly mention that automation can be performed from Linux, macOS, or Windows using Azure CLI or PowerShell Core.
  • Add Bash shell examples or guidance for users on Linux/macOS, especially for common migration tasks.
  • Rephrase recommendations to present both PowerShell and Azure CLI options equally, rather than defaulting to PowerShell.
  • Include a table or section summarizing automation options by platform (Windows, Linux, macOS) and tool (PowerShell, Azure CLI, Portal).
GitHub Create Pull Request
← Previous Page 6 of 16 Next →