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 51-75 of 388 flagged pages
Load Balancer Tutorial: Protect your public load balancer with Azure DDoS Protection ...s/load-balancer/tutorial-protect-load-balancer-ddos.md
High Priority View Details →
Scanned: 2026-01-10 00:00
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 IIS installation sections. Only Windows Server is used as the VM image, and all instructions for web server setup use Windows PowerShell commands. There are no examples or guidance for deploying Linux VMs or installing/configuring a web server (such as Apache or Nginx) on Linux. The use of Windows-specific tools and patterns (PowerShell, IIS) is exclusive, and Linux alternatives are neither mentioned nor provided.
Recommendations
  • Provide parallel instructions for creating Linux VMs (e.g., Ubuntu or CentOS) in the backend pool.
  • Include Linux-specific steps for installing a web server (e.g., Apache or Nginx) using Bash commands.
  • Offer both Windows and Linux examples for configuring and testing the load balancer.
  • Explicitly mention that either Windows or Linux VMs can be used, and link to relevant documentation for both platforms.
  • Where PowerShell is used, provide equivalent Bash or shell commands for Linux users.
GitHub Create Pull Request
Load Balancer Backend Pool Management ...main/articles/load-balancer/backend-pool-management.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a Windows bias by providing extensive PowerShell examples first, using Windows-centric tools and patterns (e.g., New-AzVMConfig with WindowsServer images), and omitting equivalent Linux-focused PowerShell examples. While the Azure CLI section includes a Linux VM creation example, the PowerShell section only shows Windows VM creation, and all scripting examples in PowerShell use Windows-specific constructs. There is no PowerShell example for creating a Linux VM or using SSH keys, and Windows terminology and tools are prioritized.
Recommendations
  • Add PowerShell examples for creating Linux VMs, including use of SSH keys and Linux images (e.g., Ubuntu).
  • Provide PowerShell snippets that demonstrate cross-platform usage, not just Windows-centric commands.
  • Alternate the order of examples so that CLI and PowerShell are presented with equal prominence, or start with CLI (which is more OS-agnostic).
  • Explicitly mention Linux support and provide guidance for Linux administrators in both PowerShell and CLI sections.
  • Include notes or tables comparing Windows and Linux workflows for backend pool management.
  • Avoid using only WindowsServer images in VM creation examples; show both Windows and Linux images.
GitHub Create Pull Request
Load Balancer Attach a cross-subscription frontend to an Azure Load Balancer ...-balancer/cross-subscription-how-to-attach-frontend.md
High Priority View Details →
Scanned: 2026-01-10 00:00
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 presenting Azure PowerShell (a Windows-centric tool) as the primary example in each section, listing PowerShell before Azure CLI, and referencing Windows-specific patterns and tools. The PowerShell instructions are more verbose and detailed, and the page metadata includes 'devx-track-azurepowershell', further emphasizing PowerShell. Although Azure CLI examples are provided, the overall structure and emphasis favor Windows/PowerShell users, with no mention of Linux-specific shell usage or considerations.
Recommendations
  • Alternate the order of examples so that Azure CLI (cross-platform) is presented first in some sections.
  • Add explicit notes or examples for Linux/macOS users, such as shell syntax differences or environment setup.
  • Ensure parity in detail and explanation between PowerShell and CLI sections.
  • Remove or balance metadata tags (e.g., 'devx-track-azurepowershell') with equivalent CLI tags.
  • Reference cross-platform tools and patterns (e.g., Bash, zsh) where appropriate.
  • Include troubleshooting or environment setup notes for Linux users, such as package managers or permissions.
GitHub Create Pull Request
Load Balancer Deploy an IPv6 dual stack application using Standard Internal Load Balancer in Azure - PowerShell ...-dual-stack-standard-internal-load-balancer-powershell.md
High Priority View Details →
Scanned: 2026-01-10 00:00
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 focused on Azure PowerShell, providing only PowerShell-based examples and instructions. There are no equivalent examples for Linux users (e.g., Azure CLI, Bash), and the virtual machine creation steps exclusively use Windows Server images. Windows-centric tools and patterns (such as RDP and Windows VM configuration) are mentioned throughout, with no mention of Linux alternatives or parity.
Recommendations
  • Add equivalent Azure CLI (az) and Bash examples for each step, especially for resource creation and configuration.
  • Include instructions and examples for deploying Linux-based virtual machines (e.g., Ubuntu, CentOS) alongside Windows examples.
  • Mention SSH access and Linux-specific network security group rules (e.g., port 22 for SSH) in addition to RDP/Windows-centric rules.
  • Clearly indicate in the introduction that the guide is PowerShell/Windows-focused, and provide links to Linux/Azure CLI documentation.
  • Ensure that references to tools and patterns (such as credential management and VM provisioning) include Linux alternatives.
GitHub Create Pull Request
Load Balancer Deploy a dual-stack Azure Gateway Load Balancer ...ad-balancer/gateway-deploy-dual-stack-load-balancer.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation consistently presents PowerShell (Windows) examples before Azure CLI (cross-platform), and all scripting examples are either PowerShell or Azure CLI. There are no explicit Linux shell (bash) or platform-specific instructions, nor any mention of Linux tools or patterns. The prerequisite and reference links also point to PowerShell-based guides first. This ordering and focus may subtly reinforce a Windows-centric workflow, and Linux users may feel secondary or unsupported.
Recommendations
  • Alternate the order of PowerShell and Azure CLI tabs, or present CLI examples first to emphasize cross-platform parity.
  • Add explicit bash shell scripting examples where possible, especially for steps that involve scripting or automation.
  • Reference Linux-specific documentation or workflows in the prerequisites and 'Next steps' sections.
  • Clarify that Azure CLI commands work on both Windows and Linux, and provide guidance for Linux users (e.g., installation, environment setup).
  • Where PowerShell-specific concepts are used, note Linux equivalents or alternatives.
  • Consider adding troubleshooting or tips sections for common Linux scenarios (e.g., permissions, environment variables).
GitHub Create Pull Request
Load Balancer Upgrading from Basic Load Balancer - Guidance .../load-balancer/load-balancer-basic-upgrade-guidance.md
High Priority View Details →
Scanned: 2026-01-10 00:00
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, without mentioning or providing equivalent Bash/CLI examples for Linux/macOS users. The upgrade steps and automation guidance are Windows-centric, and Linux tools or workflows are not referenced or supported.
Recommendations
  • Provide Azure CLI (az) script examples for Linux/macOS users alongside PowerShell scripts.
  • Explicitly mention that migration can be performed from Linux/macOS environments and link to relevant CLI documentation.
  • Ensure that automation recommendations do not prioritize Windows/PowerShell over cross-platform solutions.
  • Add a section or note for Linux users, outlining steps and tools available for migration.
  • Review and update all referenced scripts and guides to include Linux-compatible instructions.
GitHub Create Pull Request
Load Balancer Configure Azure Load Balancer distribution mode ...icles/load-balancer/load-balancer-distribution-mode.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell is featured as a primary automation example, and the 'Next steps' section links to a PowerShell-based quickstart. There is no explicit mention of Linux-specific tools or shell environments (e.g., Bash), nor are there examples tailored for Linux users. The CLI section is cross-platform, but the overall flow and examples lean toward Windows-first usage patterns.
Recommendations
  • Add explicit Bash/Linux shell examples for Azure CLI commands, including environment setup instructions for Linux.
  • Clarify that Azure CLI commands work on both Windows and Linux, and provide any OS-specific notes if needed.
  • Include links to Linux-focused quickstarts or tutorials in the 'Next steps' section.
  • Balance PowerShell examples with Bash equivalents, especially for automation scenarios.
  • Mention cross-platform compatibility in introductory sections to reassure non-Windows users.
GitHub Create Pull Request
Load Balancer Azure Load Balancer health probes ...s/load-balancer/load-balancer-custom-probe-overview.md
High Priority View Details →
Scanned: 2026-01-10 00:00
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 by referencing PowerShell in the 'Next steps' section as the only example for creating a load balancer, without mentioning Linux equivalents (e.g., Azure CLI or Bash). There are no Linux-specific instructions, examples, or references to Linux tools or workflows. The documentation also lists PowerShell before other automation options (CLI, Templates, API) in the design guidance, reinforcing a Windows-first perspective.
Recommendations
  • Add explicit Linux/Azure CLI examples for creating and managing health probes and load balancers alongside PowerShell instructions.
  • Include references to Bash scripting and Linux firewall configuration (e.g., iptables, firewalld) when discussing local firewall policies.
  • Ensure parity in 'Next steps' by providing links to Azure CLI and ARM template quickstarts, not just PowerShell.
  • When listing automation options (PowerShell, CLI, Templates, API), alternate the order or mention CLI first to avoid implicit Windows-first bias.
  • Add troubleshooting and configuration notes relevant to Linux environments, such as SELinux, systemd, or common Linux network stack behaviors.
GitHub Create Pull Request
Load Balancer Tutorial: Load balance multiple IP configurations ...in/articles/load-balancer/load-balancer-multiple-ip.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates Windows bias by exclusively referencing Windows server virtual machines, IIS websites, and omitting any mention of Linux VMs or web servers. All examples and steps are tailored to Windows environments, with no Linux equivalents or alternative instructions provided.
Recommendations
  • Add parallel instructions and examples for Linux virtual machines, such as using Ubuntu or CentOS.
  • Include steps for configuring Apache or Nginx web servers on Linux VMs, alongside IIS for Windows.
  • Ensure that CLI and PowerShell examples are complemented by Linux shell commands where applicable.
  • Explicitly mention Linux support in the tutorial introduction and checklist.
  • Provide troubleshooting and testing steps for both Windows and Linux environments.
GitHub Create Pull Request
Load Balancer Configure load balancer TCP reset and idle timeout ...ticles/load-balancer/load-balancer-tcp-idle-timeout.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation provides step-by-step instructions for configuring TCP reset and idle timeout using the Azure Portal (GUI), PowerShell, and Azure CLI. The PowerShell example is detailed and assumes the use of Windows tools, with explicit instructions for installing and using the Azure PowerShell module. There is no mention of Linux-specific tools or shell environments (e.g., Bash), and the PowerShell section appears before the Azure CLI section, which is more cross-platform. There are no Linux-specific examples or guidance for Linux users, and the documentation implicitly prioritizes Windows-centric tooling.
Recommendations
  • Add explicit Bash/Linux shell examples for Azure CLI usage, including installation and environment setup instructions for Linux.
  • Include notes or sections on using Azure CLI in Bash or other Linux shells, highlighting any differences from Windows environments.
  • Reorder the examples so that cross-platform tools (Azure CLI) are presented before Windows-specific tools (PowerShell) to reduce perceived Windows-first bias.
  • Mention alternative automation options for Linux users, such as using REST API calls or SDKs in Python.
  • Clarify that PowerShell is available on Linux and macOS, and provide installation instructions for those platforms if PowerShell examples are retained.
GitHub Create Pull Request
Load Balancer Manage Azure Load Balancer health status ...es/load-balancer/load-balancer-manage-health-status.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates Windows bias primarily in the section describing how to retrieve a Bearer access token for REST API usage. It references the PowerShell cmdlet Get-AzAccessToken and links to its documentation, without mentioning or providing equivalent instructions for Linux/macOS users (e.g., Azure CLI or other cross-platform methods). No Linux-specific tools or examples are provided, and the only tool mentioned for token retrieval is PowerShell, which is traditionally associated with Windows environments.
Recommendations
  • Add instructions for retrieving a Bearer access token using Azure CLI (az account get-access-token), which works on Linux, macOS, and Windows.
  • Include example commands for both PowerShell and Azure CLI, and present them side-by-side or in tabs labeled 'Windows (PowerShell)' and 'Linux/macOS (Azure CLI)'.
  • Explicitly state that both PowerShell and Azure CLI can be used to retrieve access tokens, and provide links to relevant documentation for each.
  • Review other sections for implicit Windows-first assumptions and ensure parity in tool references and examples.
GitHub Create Pull Request
Load Balancer Migrate from Inbound NAT rules version 1 to version 2 ...cles/load-balancer/load-balancer-nat-pool-migration.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page demonstrates a Windows bias by providing extensive PowerShell examples and automation, referencing Windows-centric tools (PowerShell Gallery, Azure PowerShell modules), and prioritizing PowerShell in automation sections. There is no mention of Linux-specific tools or scripting approaches, and prerequisites focus solely on PowerShell installation. Azure CLI examples are present for manual migration, but automation and advanced migration are exclusively PowerShell-based.
Recommendations
  • Provide equivalent automation scripts using Azure CLI and/or Bash for Linux users.
  • Include installation instructions for Azure CLI and relevant Linux tools alongside PowerShell prerequisites.
  • Reference cross-platform scripting options (e.g., Bash, Python) for migration automation.
  • Ensure that advanced migration steps and modules are available and documented for Linux environments, not just PowerShell.
  • Clarify that both Azure CLI and PowerShell are supported and indicate platform neutrality in examples.
GitHub Create Pull Request
Load Balancer Troubleshoot Azure Load Balancer health probe status ...ncer/load-balancer-troubleshoot-health-probe-status.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by predominantly referencing Windows tools (PsPing, TCPing, Netsh), providing command examples primarily for Windows (netstat -an, netsh advfirewall), and listing Windows commands before their Linux equivalents. Linux troubleshooting tools and commands are mentioned only as alternatives and lack detailed usage examples, leading to reduced parity for Linux users.
Recommendations
  • Include Linux-native troubleshooting tools (e.g., nc, ss, lsof, nmap) with detailed examples alongside Windows tools.
  • Provide step-by-step Linux command examples (e.g., using netstat -l, sudo iptables -L, nc -zv) in parallel with Windows instructions.
  • Mention Linux commands and tools first or equally when listing troubleshooting steps, rather than as alternatives.
  • Reference cross-platform tools where possible, or clarify tool availability for both Windows and Linux.
  • Add explicit guidance for Linux users on how to install and use equivalent tools (e.g., how to install TCPing or alternatives on Linux).
GitHub Create Pull Request
Load Balancer Troubleshoot common problems with Azure Load Balancer ...n/articles/load-balancer/load-balancer-troubleshoot.md
High Priority View Details →
Scanned: 2026-01-10 00:00
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 by exclusively referencing Windows-specific troubleshooting tools (PsPing, Netsh trace) and commands, without providing Linux equivalents. All example commands and diagnostic patterns assume a Windows environment, and there is no mention of Linux tools or guidance for users running Linux VMs. This may hinder Linux administrators from effectively troubleshooting Azure Load Balancer issues.
Recommendations
  • Provide equivalent Linux troubleshooting commands and tools, such as using 'ping', 'nc' (netcat), 'ss', or 'tcpdump' for network diagnostics.
  • Include Linux-specific examples alongside Windows examples for network capture and probe testing.
  • Explicitly mention both Windows and Linux environments in troubleshooting steps, ensuring parity in guidance.
  • Add a section or table comparing common Windows and Linux tools for network troubleshooting in Azure.
  • Avoid assuming the backend VM is running Windows; clarify steps for both OS types.
GitHub Create Pull Request
Load Balancer Quickstart: Create an internal load balancer - ARM template ...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-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell is featured prominently and mentioned before Azure CLI in several places. The deployment instructions and resource cleanup steps both provide PowerShell and CLI tabs, but PowerShell is presented first and uses Windows-centric commands and patterns. The use of Azure Cloud Shell is platform-neutral, but the overall structure and examples lean towards Windows/PowerShell users. There are no explicit Linux shell examples (e.g., bash scripting), and Windows tools (PowerShell) are given equal or greater prominence than cross-platform alternatives.
Recommendations
  • Alternate the order of CLI and PowerShell examples so that Azure CLI (which is cross-platform and more familiar to Linux users) appears first in some sections.
  • Explicitly mention that Azure CLI commands can be run from Bash on Linux/macOS, and provide example shell environments where appropriate.
  • Add a note clarifying that PowerShell is available cross-platform, but Azure CLI may be more familiar to Linux users.
  • Provide example commands using Bash scripting for resource deployment and cleanup, especially for Linux/macOS users.
  • Avoid using Windows-centric terminology (e.g., 'PowerShell') as the default or primary method unless justified by usage statistics.
GitHub Create Pull Request
Load Balancer Manage inbound NAT rules for Azure Load Balancer ...ain/articles/load-balancer/manage-inbound-nat-rules.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation demonstrates a moderate Windows bias. PowerShell is featured as a primary automation example alongside the Azure portal and CLI, with detailed step-by-step instructions and code snippets. PowerShell is a Windows-centric tool, and its inclusion as a main option (alongside the portal and CLI) implicitly prioritizes Windows users. There is no mention of Bash, Linux shell scripting, or Linux-specific tooling, and the CLI examples are generic, not tailored to Linux environments. The prerequisites and instructions for PowerShell are more detailed than for CLI, and there is no discussion of Linux-specific considerations or parity.
Recommendations
  • Add explicit Bash or Linux shell examples for managing NAT rules with Azure CLI, including guidance for common Linux distributions.
  • Include notes or sections on Linux-specific prerequisites, such as installing Azure CLI on Ubuntu, CentOS, etc.
  • Balance the depth of PowerShell instructions with equivalent detail for CLI usage on Linux, including environment setup and troubleshooting.
  • Consider mentioning cross-platform scripting approaches (e.g., Bash, Python) for automation, not just PowerShell.
  • Clarify that PowerShell Core is available on Linux and macOS, if PowerShell is to be included, and provide installation instructions for those platforms.
  • Review and update terminology to avoid implying Windows as the default platform (e.g., avoid 'If you're running PowerShell locally...' without mentioning Linux alternatives).
GitHub Create Pull Request
Load Balancer Quickstart: Create an internal load balancer - Azure CLI ...ncer/quickstart-load-balancer-standard-internal-cli.md
High Priority View Details →
Scanned: 2026-01-10 00:00
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) exclusively, with no mention or example of Linux images. The IIS installation step uses PowerShell commands and Windows-specific tooling, with no Linux alternative (such as Apache or Nginx). The test instructions reference Internet Explorer, a Windows-only browser, and do not provide guidance for Linux-based testing. There are no examples or instructions for deploying Linux VMs or configuring equivalent Linux web servers.
Recommendations
  • Provide parallel examples for creating Linux-based virtual machines (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 appropriate shell commands.
  • Show how to test the load balancer from a Linux VM, including browser or command-line (curl/wget) options.
  • Avoid referencing Windows-only tools (such as Internet Explorer) and offer cross-platform alternatives.
  • When presenting VM creation commands, list both Windows and Linux options, or make Linux the default unless Windows-specific features are required.
  • Explicitly state that the Azure CLI and load balancer setup is OS-agnostic, and highlight any differences in VM configuration between platforms.
GitHub Create Pull Request
Load Balancer Quickstart: Create an internal load balancer - Azure portal ...r/quickstart-load-balancer-standard-internal-portal.md
High Priority View Details →
Scanned: 2026-01-10 00:00
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 Windows bias by exclusively using Windows Server as the VM image, providing only Windows PowerShell commands for IIS installation and configuration, and referencing Windows-specific tools (PowerShell, IIS, Microsoft Edge). There are no Linux VM examples, nor are there Bash or Linux-native instructions for web server setup or testing. The documentation assumes a Windows environment throughout the setup and testing process.
Recommendations
  • Add parallel instructions for deploying a Linux VM (e.g., Ubuntu) in the 'Create test virtual machine' section.
  • Provide Linux-specific commands for installing a web server (e.g., Apache or Nginx) and customizing the index.html file using Bash.
  • Include examples of connecting to Linux VMs via SSH and using Linux-native tools (e.g., curl, Firefox) for testing.
  • Present both Windows and Linux options side-by-side in all relevant steps, or clearly indicate which steps are OS-specific.
  • Reference cross-platform tools and avoid assuming the use of Windows-only software (e.g., PowerShell, Microsoft Edge) for testing.
GitHub Create Pull Request
Load Balancer Quickstart: Create a public load balancer - Bicep ...ncer/quickstart-load-balancer-standard-public-bicep.md
High Priority View Details →
Scanned: 2026-01-10 00:00
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 referencing Internet Information Services (IIS) as the default web server on deployed VMs, without mentioning or providing examples for Linux-based alternatives (e.g., Apache, Nginx). The deployment instructions and examples are platform-neutral (Azure CLI and PowerShell), but the validation and screenshots exclusively show IIS, implying Windows VMs are used. There are no Linux VM deployment or verification steps, nor is there mention of Linux tools or web servers.
Recommendations
  • Include examples and screenshots for Linux-based VMs using popular web servers such as Apache or Nginx.
  • Explicitly mention that the Bicep template can be used to deploy either Windows or Linux VMs, and provide instructions for both.
  • Show how to verify load balancer functionality on Linux VMs (e.g., using curl, Apache default page, etc.).
  • Balance references to Windows tools (IIS) with equivalent Linux tools and patterns.
  • Add a note or section on customizing the Bicep file for Linux VM deployment.
GitHub Create Pull Request
Load Balancer Quickstart: Create a public load balancer - Azure portal ...cer/quickstart-load-balancer-standard-public-portal.md
High Priority View Details →
Scanned: 2026-01-10 00:00
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 clear Windows bias in the VM configuration section. The only example provided for installing a web server uses Windows PowerShell commands to install IIS, remove the default file, and create a custom HTML file. There are no equivalent instructions or examples for Linux-based VMs (e.g., using Bash, installing Apache or Nginx). The workflow assumes the use of Windows tools and patterns, such as PowerShell and IIS, and does not mention or prioritize Linux alternatives.
Recommendations
  • Add parallel instructions for Linux VMs, including steps to install Apache or Nginx using Bash commands.
  • Provide both Windows and Linux examples side-by-side, or allow the user to select their OS preference at the start of the guide.
  • Reference Linux tools and patterns (e.g., SSH, apt/yum, systemctl) where appropriate.
  • Avoid assuming Windows as the default; mention both platforms equally in all relevant sections.
  • Include screenshots or command snippets for Linux where Windows examples are shown.
GitHub Create Pull Request
Load Balancer Deploy a global load balancer with Azure Resource Manager templates | Microsoft Docs ...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-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates Windows bias by exclusively deploying and verifying IIS (Internet Information Services) on Windows Server virtual machines, with no mention of Linux alternatives. The verification step instructs users to access the default IIS Windows Server web page, and all examples implicitly assume Windows-based VMs. There are no examples or instructions for deploying or verifying Linux-based web servers (such as Apache or Nginx), nor are Linux-specific tools or patterns referenced.
Recommendations
  • Include parallel instructions and examples for deploying Linux-based virtual machines, such as Ubuntu or CentOS.
  • Provide template snippets or parameter options for installing and configuring common Linux web servers (e.g., Apache, Nginx) via VM extensions.
  • Add verification steps showing how to check the default web page for Linux servers, including screenshots.
  • Mention Linux-compatible tools and commands where appropriate, and avoid assuming Windows-only environments.
  • Clarify that the ARM template can be adapted for both Windows and Linux workloads, and provide links to relevant Linux documentation.
GitHub Create Pull Request
Load Balancer Quickstart: Create a public load balancer - Azure CLI ...lancer/quickstart-load-balancer-standard-public-cli.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example Powershell Heavy
Summary
The documentation demonstrates Windows bias by exclusively creating Windows Server VMs (win2019datacenter) and providing only Windows-specific configuration examples, such as installing IIS via PowerShell commands. There are no Linux VM creation examples, nor instructions for deploying or configuring Linux-based web servers (e.g., Apache, Nginx). The VM extension script is written for Windows and PowerShell, with no Linux equivalent. This prioritizes Windows usage and omits Linux parity in the quickstart.
Recommendations
  • Include parallel examples for creating Linux VMs (e.g., using --image UbuntuLTS) alongside Windows examples.
  • Provide instructions and scripts for installing a web server on Linux VMs (e.g., Apache or Nginx) using Bash or cloud-init.
  • Show how to test the load balancer with Linux VMs, including relevant commands and expected output.
  • Clearly indicate that both Windows and Linux VMs are supported and provide guidance for each.
  • Avoid assuming PowerShell as the default scripting language; offer Bash alternatives where appropriate.
GitHub Create Pull Request
Load Balancer Tutorial: Create an Azure Global Load Balancer ...articles/load-balancer/tutorial-cross-region-portal.md
High Priority View Details →
Scanned: 2026-01-10 00:00
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 primarily through its use of IIS as the default backend web server in all test scenarios, which is Windows-specific. There are no Linux-based backend examples (e.g., Apache, Nginx), nor instructions for Linux VM setup or testing. The test and validation steps exclusively reference IIS and do not mention Linux alternatives. Additionally, the portal walkthrough and screenshots implicitly assume a Windows-centric deployment, and the PowerShell instructions (a Windows-preferred tool) are presented with equal prominence to Azure CLI, but Linux-specific nuances are not addressed.
Recommendations
  • Add explicit Linux backend pool examples, such as deploying Ubuntu VMs with Apache or Nginx, and provide links to relevant quickstarts.
  • In the 'Test the load balancer' section, include instructions for verifying load balancing with a Linux web server (e.g., using curl or a browser to access an Apache/Nginx default page).
  • Mention Linux VM creation and configuration steps alongside Windows/IIS, or provide links to Linux-specific quickstarts.
  • Clarify that Azure CLI works cross-platform and highlight any Linux-specific considerations (e.g., shell syntax differences, package installation).
  • Include screenshots or terminal outputs showing Linux web server responses to demonstrate parity.
  • Where PowerShell is referenced, note that it is available on Linux, but also suggest Bash as an alternative for scripting on Linux.
GitHub Create Pull Request
Load Balancer Tutorial: Create a load balancer with more than one availability set in the backend pool - Azure portal ...ad-balancer/tutorial-multi-availability-sets-portal.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example Powershell Heavy
Summary
The documentation exclusively uses Windows Server images for all virtual machine examples and only provides instructions for installing IIS using PowerShell scripts. There are no Linux VM options, nor are there examples for deploying or configuring Linux-based web servers (such as Apache or Nginx). The instructions for remote command execution are Windows/PowerShell-centric, and there is no mention of Linux tools, shell scripts, or alternative approaches.
Recommendations
  • Include parallel instructions for creating Linux virtual machines (e.g., Ubuntu, CentOS) in the VM creation steps.
  • Provide examples for installing and configuring a Linux web server (such as Apache or Nginx) using Bash scripts or the Azure portal's Run Command feature for Linux.
  • Show how to use SSH for remote access to Linux VMs, alongside the PowerShell/Bastion approach for Windows.
  • Ensure screenshots and walkthroughs demonstrate both Windows and Linux VM scenarios.
  • Explicitly mention that the load balancer works with both Windows and Linux backend pools, and link to relevant Linux documentation.
GitHub Create Pull Request
Load Balancer Tutorial: Create a public load balancer with an IP-based backend - Azure portal ...d-balancer/tutorial-load-balancer-ip-backend-portal.md
High Priority View Details →
Scanned: 2026-01-10 00:00
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 'Install IIS' section, where only Windows Server is used for VM images and only Windows PowerShell commands are provided for installing and configuring IIS. There are no Linux VM options or examples, nor instructions for deploying a Linux web server (e.g., Apache or Nginx). The tutorial assumes Windows as the default, both in VM creation and in administrative tooling, without mentioning or providing parity for Linux users.
Recommendations
  • Include Linux VM creation steps alongside Windows, such as selecting Ubuntu or CentOS images.
  • Provide equivalent instructions for installing and configuring a web server on Linux (e.g., Apache or Nginx) using Bash commands.
  • Offer both PowerShell and Bash command examples for server setup.
  • Explicitly mention that the tutorial applies to both Windows and Linux, and guide users to choose their preferred OS.
  • Add notes or links to Linux-specific documentation for load balancer backend configuration and testing.
GitHub Create Pull Request
← Previous Page 3 of 16 Next →