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 76-100 of 388 flagged pages
Load Balancer https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/backend-pool-management.md ...main/articles/load-balancer/backend-pool-management.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by providing extensive PowerShell examples first, using Windows-centric tools and patterns (e.g., PowerShell cmdlets, Windows VM images), and omitting Linux-specific PowerShell or CLI examples. The VM creation example in PowerShell uses a Windows image exclusively, while the CLI example uses Ubuntu, but there is no parity in showing Linux VM creation via PowerShell. The documentation also assumes familiarity with Windows tooling and does not mention Linux alternatives or cross-platform scripting approaches in the PowerShell section.
Recommendations
  • Add PowerShell examples for creating and managing Linux VMs (e.g., using Ubuntu or other Linux images) to demonstrate parity.
  • Include Bash scripting examples alongside PowerShell for backend pool management, especially for users on Linux or macOS.
  • Present CLI and PowerShell examples in parallel, rather than giving PowerShell (Windows) examples first and in greater detail.
  • Explicitly mention cross-platform compatibility of Azure CLI and PowerShell, and provide guidance for Linux/macOS users.
  • Avoid using only Windows-specific VM images in examples; alternate or show both Windows and Linux VM creation in all tool sections.
  • Add notes or links for Linux users on how to install and use Azure PowerShell and CLI on their platforms.
GitHub Create Pull Request
Load Balancer https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/cross-subscription-how-to-attach-frontend.md ...-balancer/cross-subscription-how-to-attach-frontend.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation page exhibits a moderate Windows bias. PowerShell examples are presented first in every section, and the prerequisites and instructions reference Azure PowerShell and its installation before mentioning Azure CLI. The documentation also uses Windows-centric terminology and tools (PowerShell, Connect-AzAccount, etc.) more prominently, even though Azure CLI is cross-platform. There is no mention of Linux-specific considerations, shell environments, or alternative scripting approaches. The page does provide Azure CLI examples, but PowerShell is consistently prioritized.
Recommendations
  • Alternate the order of examples so that Azure CLI is presented first in some sections, or present both examples side-by-side.
  • Explicitly mention that Azure CLI works on Linux, macOS, and Windows, and provide guidance for Linux users (e.g., shell syntax, installation commands).
  • Add notes or links for Linux users regarding environment setup, such as using Bash or Zsh, and clarify that PowerShell is also available on Linux if desired.
  • Avoid Windows-centric language (e.g., 'If you choose to install and use PowerShell locally...') and instead use platform-neutral phrasing.
  • Ensure that all referenced quickstart or prerequisite links include Linux/Bash examples and not just PowerShell.
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: 2026-01-09 00:34
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 consistently presenting Azure PowerShell (a Windows-centric tool) examples before Azure CLI, using PowerShell-specific patterns and terminology, and referencing PowerShell modules and commands in detail. The Azure CLI (more cross-platform) examples are present but often less detailed, and the overall structure and notes favor PowerShell usage and installation, which is most common on Windows.
Recommendations
  • Alternate the order of examples so that Azure CLI is presented first in some sections, or present both examples side-by-side.
  • Ensure equal detail and explanation for both Azure PowerShell and Azure CLI instructions, including troubleshooting and environment setup.
  • Add explicit notes highlighting that Azure CLI is fully supported on Linux and macOS, and provide links to installation guides for those platforms.
  • Avoid language that implies PowerShell is the default or preferred tool; instead, clarify that both PowerShell and CLI are supported and cross-platform.
  • Include example shell environments (e.g., Bash) for CLI commands to reinforce Linux parity.
  • Review and update reusable content includes to ensure they do not favor Windows or PowerShell environments.
GitHub Create Pull Request
Load Balancer https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/deploy-ipv4-ipv6-dual-stack-standard-load-balancer.md ...https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/deploy-ipv4-ipv6-dual-stack-standard-load-balancer.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exhibits Windows bias by exclusively providing examples for deploying Windows Server VMs (no Linux VM examples), using RDP (Windows Remote Desktop) for remote access, and referencing Windows-centric tools and patterns (e.g., PowerShell, RDP ports, Windows images) throughout both PowerShell and Azure CLI sections. Linux equivalents, such as SSH access or Linux VM images, are not mentioned or demonstrated, and all VM creation examples default to Windows Server.
Recommendations
  • Add Linux VM deployment examples alongside Windows Server examples in both Azure CLI and PowerShell sections (e.g., using Ubuntu or CentOS images).
  • Include instructions and code samples for configuring SSH access (port 22) for Linux VMs, including network security group rules and public IP assignment.
  • Mention and demonstrate Linux-friendly tools and patterns (e.g., SSH, Linux images) before or alongside Windows-specific ones.
  • Clarify in the documentation that both Windows and Linux VMs are supported, and provide guidance for users who prefer Linux.
  • Ensure ARM template snippets and references are not Windows-specific, or provide Linux variants where appropriate.
GitHub Create Pull Request
Load Balancer https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/ipv6-add-to-existing-vnet-powershell.md .../load-balancer/ipv6-add-to-existing-vnet-powershell.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation is heavily biased toward Windows and PowerShell usage. All examples and instructions use Azure PowerShell cmdlets, with no mention of Azure CLI, Bash, or Linux-native workflows. The prerequisites and resource management steps reference only PowerShell tools and patterns, and there are no Linux or cross-platform alternatives provided. The article title and structure reinforce PowerShell as the default approach, implicitly prioritizing Windows users.
Recommendations
  • Add equivalent Azure CLI (az) examples for each step, with Bash syntax, to support Linux and macOS users.
  • Include a section or note at the beginning highlighting cross-platform options (PowerShell, Azure CLI, REST API), and link to relevant documentation.
  • Adjust the article title and headings to clarify that PowerShell is one of several supported methods, not the only or default approach.
  • Where possible, provide guidance for running commands in Bash or Cloud Shell (with CLI), and clarify any platform-specific differences.
  • Ensure resource cleanup and management instructions include CLI equivalents, not just PowerShell.
  • Consider adding a comparison table or quick-start links for both PowerShell and CLI workflows.
GitHub Create Pull Request
Load Balancer https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/ipv6-dual-stack-standard-internal-load-balancer-powershell.md ...-dual-stack-standard-internal-load-balancer-powershell.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation is heavily biased towards Windows and PowerShell. All examples use Azure PowerShell cmdlets, with no mention of Azure CLI, Bash, or Linux-native tooling. The VM creation steps exclusively use Windows images and Windows-specific configuration. There are no Linux VM examples, nor any guidance for users working from Linux or macOS environments. Windows tools and patterns (e.g., RDP, PowerShell, WindowsServer images) are referenced exclusively and/or before any Linux equivalents.
Recommendations
  • Provide equivalent Azure CLI (az) examples for each step, suitable for Bash or other shells on Linux/macOS.
  • Include Linux VM creation examples alongside Windows VM examples, using popular distributions (e.g., Ubuntu, CentOS).
  • Mention Linux-native connection methods (e.g., SSH) and provide corresponding network security group rules.
  • Clarify that the process can be performed from Linux/macOS environments using Azure CLI or Cloud Shell Bash.
  • Balance references to Windows tools (RDP, PowerShell) with Linux alternatives (SSH, Bash scripting).
  • Consider renaming the article or adding a parallel article for Linux users if the focus is intentionally Windows/PowerShell.
GitHub Create Pull Request
Load Balancer https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/load-balancer-basic-upgrade-guidance.md .../load-balancer/load-balancer-basic-upgrade-guidance.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by exclusively recommending and providing PowerShell scripts for automated migration, with no mention of Linux CLI (Azure CLI, Bash) alternatives. Windows tools (PowerShell) are referenced as the primary automation method, and no Linux or cross-platform examples are given. The guidance implicitly assumes a Windows environment, potentially excluding users who manage Azure resources from Linux or macOS systems.
Recommendations
  • Provide equivalent Azure CLI (az) script examples for automating the migration process, suitable for Linux/macOS users.
  • Mention both PowerShell and Azure CLI options in the upgrade steps, giving equal prominence to cross-platform tools.
  • Add explicit guidance or links for users working from Linux or macOS environments.
  • Review all automation recommendations to ensure parity between Windows and Linux tooling, avoiding exclusive reliance on Windows-centric solutions.
GitHub Create Pull Request
Load Balancer https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/load-balancer-distribution-mode.md ...icles/load-balancer/load-balancer-distribution-mode.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by providing detailed PowerShell instructions (which are Windows-centric), listing PowerShell before Azure CLI, and omitting explicit Linux shell examples or guidance. The CLI section uses Azure CLI, which is cross-platform, but does not clarify usage in Linux environments or provide Linux-specific context. There are no references to Linux tools, shell environments, or considerations for Linux users.
Recommendations
  • Add explicit Bash/Linux shell examples for Azure CLI commands, including environment setup and usage notes for Linux users.
  • Clarify that Azure CLI commands work on Linux, macOS, and Windows, and provide any OS-specific caveats if applicable.
  • Consider including a Linux-first or cross-platform-first approach in the ordering of examples, or alternate the order to avoid implicit prioritization of Windows tools.
  • If PowerShell is included, mention that PowerShell Core is available on Linux and macOS, and provide examples for those platforms where relevant.
  • Review 'Next steps' links to ensure parity between Windows and Linux getting started guides.
GitHub Create Pull Request
Load Balancer https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/load-balancer-custom-probe-overview.md ...s/load-balancer/load-balancer-custom-probe-overview.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates Windows bias primarily by referencing PowerShell in the 'Next steps' section as the only example for creating a load balancer, without mentioning Linux tools or providing CLI/Bash examples. There is no mention of Linux-specific commands, nor are there examples using Azure CLI or Bash, which are commonly used on Linux systems. The documentation also refers to firewall policies and NSG rules in a generic way, but does not provide parity for Linux environments or tools.
Recommendations
  • Include Azure CLI examples for health probe and load balancer configuration, especially in the 'Next steps' section.
  • Provide Bash shell command examples alongside PowerShell, or link to Linux-focused quickstarts.
  • Explicitly mention Linux firewall tools (e.g., iptables, firewalld) when discussing local firewall configuration for health probes.
  • Ensure that any references to management tools (e.g., PowerShell) are balanced with cross-platform alternatives.
  • Add links to Linux-specific documentation for creating and managing Azure Load Balancers and health probes.
GitHub Create Pull Request
Load Balancer https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/load-balancer-manage-health-status.md ...es/load-balancer/load-balancer-manage-health-status.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Missing Linux Example Windows First
Summary
The documentation page exhibits Windows bias primarily in its guidance for REST API authentication, referencing only the Windows PowerShell 'Get-AzAccessToken' command for obtaining a Bearer token. No equivalent Linux or cross-platform CLI instructions (such as Azure CLI or Bash examples) are provided. The only tool mentioned for authentication is PowerShell, which is traditionally associated with Windows environments. This may lead Linux or macOS users to feel unsupported or confused about how to perform the same operation on their platforms.
Recommendations
  • Add Azure CLI examples for obtaining the Bearer access token (e.g., 'az account get-access-token'), which work on Linux, macOS, and Windows.
  • Include Bash or shell script examples for making REST API calls, demonstrating cross-platform usage.
  • Reference both PowerShell and Azure CLI in the authentication note, making it clear that either can be used depending on the user's environment.
  • Consider adding a section or table comparing methods for retrieving access tokens across different platforms (Windows, Linux, macOS).
  • Review other sections for similar tool-specific references and ensure parity in examples and instructions for Linux users.
GitHub Create Pull Request
Load Balancer https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/load-balancer-multiple-ip.md ...in/articles/load-balancer/load-balancer-multiple-ip.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by specifying the creation of 'two Windows server virtual machines' and the use of Internet Information Server (IIS) websites, with no mention of Linux VMs or Apache/Nginx equivalents. All example steps and scenarios are centered on Windows environments, and there is no guidance for Linux users or alternative web servers.
Recommendations
  • Include parallel instructions for creating and configuring Linux virtual machines alongside Windows VMs.
  • Provide examples for deploying and configuring popular Linux web servers such as Apache or Nginx, including website binding steps.
  • Ensure that all steps (NIC configuration, website setup, load balancer testing) have Linux-specific guidance and command-line examples (e.g., Bash, Azure CLI for Linux).
  • Use neutral language in checklists and summaries (e.g., 'Create two virtual machines' instead of 'Create two Windows server virtual machines').
  • Add a section or tab for Linux users in the tutorial, mirroring the structure for Windows.
GitHub Create Pull Request
Load Balancer https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/load-balancer-overview.md .../main/articles/load-balancer/load-balancer-overview.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example Powershell Heavy
Summary
The documentation page for Azure Load Balancer shows subtle Windows bias. While the page is mostly conceptual, the only technical example referenced is an IPv6 load balancing tutorial that is specifically for PowerShell (which is traditionally Windows-centric, though now cross-platform). There are no explicit Linux CLI (e.g., Bash, Azure CLI) examples or references, and no mention of Linux-specific tools or workflows. The linked tutorials and guides do not clarify whether Linux users are equally supported, and the PowerShell example is presented without Linux parity.
Recommendations
  • Add explicit examples using Azure CLI (az), Bash, or Linux shell commands alongside PowerShell examples.
  • Clarify in each tutorial or feature section whether the instructions apply to both Windows and Linux, and provide platform-specific guidance if needed.
  • Include references to Linux tools and workflows (e.g., SSH, iptables, netstat) where relevant, especially in scenarios involving VM configuration or diagnostics.
  • Ensure that any code samples or walkthroughs are available for both Windows and Linux environments, and link to both sets of instructions.
  • Review linked tutorials to ensure Linux parity and add cross-platform badges or notes.
GitHub Create Pull Request
Load Balancer https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/load-balancer-nat-pool-migration.md ...cles/load-balancer/load-balancer-nat-pool-migration.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page demonstrates a Windows bias by providing extensive PowerShell examples and automation scripts, referencing Windows-centric tools (PowerShell Gallery, Azure PowerShell modules), and mentioning PowerShell prerequisites and upgrade steps before or instead of Linux alternatives. There are no Bash, Linux shell, or cross-platform scripting examples, and the automation section is exclusively PowerShell-focused.
Recommendations
  • Provide equivalent Bash or shell script examples for all migration steps, especially for automation.
  • Reference Azure CLI and cross-platform tools equally or before PowerShell in instructions and prerequisites.
  • Include instructions for installing and using Azure CLI on Linux/macOS, and mention Linux package managers where relevant.
  • If a PowerShell module is required for automation, offer a Python or Bash alternative, or clarify cross-platform compatibility.
  • Explicitly state platform compatibility for all scripts and tools, and avoid assuming PowerShell is the default automation environment.
GitHub Create Pull Request
Load Balancer https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/load-balancer-troubleshoot-health-probe-status.md ...ncer/load-balancer-troubleshoot-health-probe-status.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing Windows-specific tools (PsPing, TCPing, Netsh) for troubleshooting, providing command prompt instructions before Linux equivalents, and omitting Linux-native alternatives for some steps. Linux commands are mentioned only as secondary options, and there is a lack of parity in example detail and tool recommendations for Linux users.
Recommendations
  • Provide Linux-native troubleshooting tool examples (e.g., use 'nc', 'ss', or 'telnet' for port checks instead of only PsPing/TCPing).
  • List Linux commands and tools alongside Windows commands in all troubleshooting steps, not just as afterthoughts.
  • Offer detailed Linux command examples (e.g., show how to use 'ss -ltn', 'nc -zv', or 'iptables' for equivalent checks).
  • Avoid referencing Windows tools exclusively or first; alternate the order or present both platforms equally.
  • Include links to Linux-specific documentation or tool installation guides.
  • Ensure all example commands are provided for both Windows and Linux environments.
GitHub Create Pull Request
Load Balancer https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/load-balancer-troubleshoot.md ...n/articles/load-balancer/load-balancer-troubleshoot.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates Windows bias by exclusively referencing Windows-specific tools (PsPing, Netsh) for network capture and troubleshooting, without providing equivalent Linux commands or examples. All troubleshooting steps involving command-line tools assume a Windows environment, and there are no Linux alternatives or parity in the examples.
Recommendations
  • Include Linux equivalents for all troubleshooting steps, such as using 'ping', 'nc' (netcat), or 'ss' for connectivity tests, and 'tcpdump' or 'wireshark' for network captures.
  • Provide example commands for both Windows and Linux environments side-by-side, ensuring users on either platform can follow the guidance.
  • Explicitly mention that the steps apply to Windows VMs and add a section for Linux VM troubleshooting.
  • Avoid assuming the use of Windows-only tools; reference cross-platform or platform-specific tools as appropriate.
GitHub Create Pull Request
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-09 00:34
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 method alongside the Azure portal and CLI, with detailed step-by-step instructions and code samples. PowerShell is a Windows-centric tool, and its prominence may disadvantage Linux users. The CLI examples are present and reasonably complete, but there is no mention of Bash, Linux shell scripting, or Linux-specific considerations. The prerequisites and instructions for PowerShell (including module installation and Connect-AzAccount) are detailed, while Linux setup or shell environment preparation is not discussed. The documentation does not reference Linux-native tools or patterns, and PowerShell is often listed before CLI, reinforcing a Windows-first approach.
Recommendations
  • Add explicit Bash/Linux shell examples for Azure CLI commands, including sample scripts and environment setup instructions.
  • Include notes or links for Linux users on how to install and use Azure CLI on Linux distributions.
  • Balance the order of examples so that CLI (cross-platform) instructions appear before PowerShell, or alternate their order.
  • Mention that PowerShell Core is available on Linux and macOS, and provide guidance for those platforms if PowerShell is retained.
  • Reference Linux-native automation tools (e.g., Bash, Ansible) where appropriate, or provide links to relevant documentation.
  • Clarify that all CLI commands are cross-platform 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-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools Windows First
Summary
The documentation provides detailed instructions for moving Azure Load Balancers between regions using the Azure portal and Azure PowerShell. However, it exclusively features PowerShell-based CLI examples and references Windows tools (e.g., notepad.exe), with no mention of Azure CLI (az), Bash, or Linux-native workflows. The PowerShell approach is presented as the only command-line method, and Windows-specific patterns (such as using notepad.exe) are referenced. There is no parity for Linux users or those preferring cross-platform tools.
Recommendations
  • Add equivalent Azure CLI (az) examples for all PowerShell steps, including resource export, template editing, and deployment.
  • Replace or supplement Windows-specific tools (e.g., notepad.exe) with cross-platform alternatives (e.g., vim, nano, code, or generic 'edit in your preferred editor').
  • Explicitly mention that all steps can be performed on Linux, macOS, and Windows, and provide guidance for non-Windows environments.
  • Ensure that references to command-line workflows do not assume PowerShell or Windows as the default; present Azure CLI and Bash examples before or alongside PowerShell.
  • Include troubleshooting notes or tips for Linux/macOS users where workflows may differ (e.g., file paths, editor commands).
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-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation provides both Azure CLI and PowerShell examples for deployment, but PowerShell (a Windows-centric tool) is mentioned first in the deployment section introduction and is used in the initial deployment command example. The command to open Azure Cloud Shell also defaults to PowerShell. Additionally, the cleanup section contains a CLI example that mistakenly uses a PowerShell command, indicating a possible bias toward PowerShell/Windows workflows. There are no Linux-specific shell examples (e.g., Bash), and no mention of Linux-native tools or patterns.
Recommendations
  • Ensure that Azure CLI (which is cross-platform and popular on Linux) is presented first or equally alongside PowerShell in all sections.
  • Correct the CLI cleanup example to use the actual Azure CLI command (az group delete) instead of a PowerShell command.
  • Explicitly mention that Azure CLI commands can be run from Bash or other Linux shells, and provide Bash-specific usage notes where relevant.
  • Where Cloud Shell is referenced, clarify that both Bash and PowerShell environments are available, and provide instructions for both.
  • Review for any other Windows-centric language or assumptions, and ensure parity for Linux users in all instructions and examples.
GitHub Create Pull Request
Load Balancer https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/quickstart-load-balancer-standard-internal-portal.md ...r/quickstart-load-balancer-standard-internal-portal.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example Powershell Heavy 🔧 Windows Tools
Summary
The documentation demonstrates a strong Windows bias. All VM creation and configuration steps use Windows Server images by default, and all examples for installing and configuring the web server (IIS) are provided exclusively with Windows PowerShell commands. There are no Linux VM options, nor are there any examples for installing a web server on Linux (e.g., Apache or Nginx). The workflow assumes the use of Windows tools (PowerShell, IIS, Microsoft Edge) and does not mention or provide parity for Linux-based alternatives.
Recommendations
  • Provide parallel instructions for creating a Linux VM (e.g., Ubuntu or CentOS) alongside the Windows VM instructions.
  • Include Linux shell (bash) commands for installing a web server (such as Apache or Nginx), customizing the index.html, and verifying the setup.
  • Show how to connect to Linux VMs (e.g., via SSH through Bastion) and use Linux-native tools (e.g., curl, Firefox) for testing.
  • When giving examples, present both Windows and Linux options, or at least mention that Linux is supported and link to relevant guides.
  • Avoid assuming Windows as the default platform; clarify that the steps can be adapted for Linux environments.
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-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a bias toward Windows environments. It references Internet Information Services (IIS), a Windows-only web server, as the default workload on the deployed VMs, without mentioning or providing examples for Linux alternatives. The deployment instructions include both Azure CLI and PowerShell, but the example workload and screenshots are Windows-centric. There are no examples or guidance for deploying Linux-based web servers (e.g., Apache, Nginx), nor are there screenshots or instructions for Linux users.
Recommendations
  • Provide alternative examples for Linux-based web servers (such as Apache or Nginx) in addition to IIS.
  • Include screenshots and instructions for accessing and verifying deployments on Linux VMs.
  • Mention that the Bicep template can be customized to deploy Linux VMs and provide sample parameters or code snippets.
  • Clarify that the Azure CLI is cross-platform and highlight its use for Linux and macOS users.
  • Ensure parity in troubleshooting and post-deployment verification steps for both Windows and Linux 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-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example Powershell Heavy
Summary
The documentation demonstrates Windows bias primarily in the virtual machine creation and configuration steps. Only Windows VM images (win2019datacenter) are used, and the IIS installation relies exclusively on Windows PowerShell commands. There are no examples for creating Linux VMs or installing a web server (such as Apache or Nginx) on Linux. This limits the quickstart's applicability for users who prefer or require Linux-based backend servers.
Recommendations
  • Provide parallel examples for Linux VMs (e.g., using Ubuntu or CentOS images) in the VM creation section.
  • Include instructions and Azure CLI commands for installing a web server (such as Apache or Nginx) on Linux VMs, using appropriate shell commands.
  • Explicitly mention that both Windows and Linux VMs are supported, and link to further documentation for Linux-specific setup.
  • Where PowerShell is used for configuration, offer equivalent Bash or shell script examples for Linux environments.
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-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools Windows First
Summary
The documentation demonstrates a clear Windows bias, especially in the 'Install IIS' section, where only Windows PowerShell commands are provided for configuring IIS on the backend VMs. There are no equivalent instructions or examples for deploying a web server on Linux VMs (e.g., using Apache or Nginx with Bash commands). The workflow assumes the use of Windows Server and Windows tools (PowerShell, IIS), with no mention of Linux alternatives or parity in the setup or testing process.
Recommendations
  • Add parallel instructions for deploying and configuring a web server (such as Apache or Nginx) on Linux VMs, including Bash command examples.
  • Where PowerShell is used for Windows, provide equivalent Bash/Shell commands for Linux.
  • Explicitly mention that the example uses Windows VMs and provide a note or section for Linux users.
  • Ensure that screenshots and walkthroughs are not exclusively Windows-centric, or provide Linux equivalents where appropriate.
  • Consider a table or toggle to allow users to select their OS (Windows/Linux) and see relevant instructions.
GitHub Create Pull Request
Load Balancer https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/troubleshoot-rhc.md ...s/blob/main/articles/load-balancer/troubleshoot-rhc.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates Windows bias by referencing Windows troubleshooting resources before Linux equivalents, specifically in the high-CPU troubleshooting section. It also provides a Windows command prompt example ('netstat -a') before the Linux equivalent ('netstat -l'), and links only to Windows VM troubleshooting documentation, omitting Linux VM guidance. There is a lack of parity in example commands and troubleshooting links for Linux users.
Recommendations
  • Provide links to both Windows and Linux VM troubleshooting guides when referencing high-CPU issues.
  • Present command examples for both Windows and Linux platforms side-by-side, or in parallel, rather than listing Windows first.
  • Ensure that troubleshooting steps and references are equally detailed for both Windows and Linux environments.
  • Explicitly mention Linux tools and patterns where relevant, such as referencing Linux-specific firewall configuration or system monitoring tools.
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-09 00:34
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 in several ways: it references IIS (a Windows web server) as the default backend for testing, omits Linux-specific backend examples (such as Apache or Nginx), and consistently uses Windows-centric terminology and tools (IIS, PowerShell) without providing parity for Linux users. The test instructions and screenshots assume a Windows environment, and there is no mention of Linux VM setup or verification steps. While Azure CLI is cross-platform, the examples and guidance do not address Linux-specific patterns or troubleshooting.
Recommendations
  • Include Linux backend pool examples (e.g., Ubuntu VMs running Apache or Nginx) alongside IIS.
  • Provide test instructions for Linux users, such as verifying with curl or checking Apache/Nginx default pages.
  • Add screenshots or CLI output examples from Linux environments.
  • Mention Linux VM creation guides and link to relevant quickstarts.
  • Clarify that Azure CLI commands work on Linux, macOS, and Windows, and provide shell-specific notes where appropriate.
  • Balance references to PowerShell with Bash or other Linux-native tools when discussing local scripting.
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-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example Powershell Heavy 🔧 Windows Tools
Summary
The documentation page demonstrates a strong Windows bias. All virtual machine creation steps specify Windows Server images exclusively, with no mention of Linux alternatives. The IIS installation and configuration is performed using Windows PowerShell scripts, and only Windows tooling (IIS, PowerShell) is referenced. There are no examples or instructions for deploying Linux VMs, installing a Linux web server (such as Apache or Nginx), or using Linux-native command-line tools. This limits the tutorial's applicability for users who prefer or require Linux-based workloads.
Recommendations
  • Provide parallel instructions for creating Linux virtual machines (e.g., Ubuntu, CentOS) alongside Windows examples.
  • Include steps for installing and configuring a web server on Linux VMs (such as Apache or Nginx), using Bash or cloud-init scripts.
  • Offer sample Linux shell commands for web server setup and verification, in addition to PowerShell.
  • Explicitly mention that both Windows and Linux VMs are supported in Azure Load Balancer backend pools, and link to relevant Linux documentation.
  • Add screenshots or code snippets showing the Linux experience in the Azure portal where appropriate.
GitHub Create Pull Request
← Previous Page 4 of 16 Next →