Load Balancer

188
Total Pages
143
Linux-Friendly Pages
45
Pages with Bias
23.9%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

117 issues found
Showing 26-50 of 117 flagged pages
Load Balancer Tutorial: Create a public load balancer with an IP-based backend - Azure portal ...d-balancer/tutorial-load-balancer-ip-backend-portal.md
Medium Priority View Details →
Scanned: 2026-01-23 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides only Windows Server VM creation instructions and exclusively uses PowerShell commands to install IIS, with no mention of Linux VM options or equivalent Linux web server setup. This creates friction for Linux users who wish to follow the tutorial.
Recommendations
  • Provide parallel instructions for creating Linux-based VMs (e.g., Ubuntu) in the 'Create virtual machines' section.
  • Add a section or alternative steps for installing a web server (such as Apache or Nginx) on Linux VMs, including the necessary shell commands.
  • When showing PowerShell commands for Windows, also show bash commands for Linux where applicable.
  • Explicitly mention that the tutorial can be followed with Linux VMs and link to relevant Linux documentation for web server installation.
GitHub Create Pull Request
Load Balancer Move an Azure Load Balancer to another Azure region ...ad-balancer/move-across-regions-azure-load-balancer.md
Medium Priority View Details →
Scanned: 2026-01-23 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example
Summary
The documentation provides detailed instructions for moving an Azure Load Balancer across regions using the Azure Portal and Azure PowerShell. However, it does not include any examples or guidance for users of Azure CLI (which is cross-platform and preferred by many Linux/macOS users) or Bash scripting. All command-line instructions are exclusively in PowerShell, and there is no mention of Azure CLI equivalents.
Recommendations
  • Add equivalent Azure CLI examples for all PowerShell command-line steps, including resource export, deployment, and verification.
  • Explicitly mention that Azure CLI can be used on Linux/macOS and provide links or code blocks for common tasks.
  • Where file editing is required (e.g., editing JSON templates), suggest cross-platform editors (such as 'code', 'nano', or 'vim') instead of only 'notepad.exe'.
  • Add a short section or note clarifying that all operations can be performed from Linux/macOS using Azure CLI, and link to relevant Azure CLI documentation.
GitHub Create Pull Request
Load Balancer Quickstart: Create a public load balancer - Azure portal ...cer/quickstart-load-balancer-standard-public-portal.md
Medium Priority View Details →
Scanned: 2026-01-23 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides only Windows/PowerShell instructions for configuring the backend VMs (specifically, installing IIS using PowerShell). There are no equivalent instructions or examples for Linux VMs or for using Linux-native tools (e.g., Apache, Nginx). This creates friction for users who wish to use Linux VMs as load balancer backends.
Recommendations
  • Add a parallel section showing how to create Linux VMs as backend pool members.
  • Provide Linux-specific instructions for installing a web server (e.g., Apache or Nginx) on Ubuntu/CentOS VMs, including the necessary shell commands.
  • Explicitly state that the backend VMs can be either Windows or Linux, and link to relevant quickstarts for both.
  • When showing PowerShell commands, also show equivalent Bash/SSH commands for Linux.
  • Clarify in the prerequisites or introduction that the example uses Windows VMs, but Linux is also supported.
GitHub Create Pull Request
Load Balancer Quickstart: Create an internal load balancer - Azure portal ...r/quickstart-load-balancer-standard-internal-portal.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
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 notable Windows bias. All VM creation steps use Windows Server images, and the only example for installing a web server (IIS) is via Windows PowerShell. There are no instructions or examples for deploying Linux VMs, nor for installing a web server (such as Apache or Nginx) on Linux. The testing steps also assume a Windows environment (using Microsoft Edge). This creates friction for users who prefer or require Linux-based solutions.
Recommendations
  • Add parallel instructions for creating Linux VMs (e.g., Ubuntu) in the portal.
  • Provide Linux-specific steps for installing a web server (e.g., Apache or Nginx) using Bash commands.
  • Include testing instructions using Linux tools (e.g., curl, Firefox) on the test VM.
  • Present both Windows and Linux examples side-by-side or allow users to select their preferred OS path.
  • Avoid assuming Windows-only environments in screenshots and step descriptions.
GitHub Create Pull Request
Load Balancer Backend Pool Management ...main/articles/load-balancer/backend-pool-management.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation page exhibits a Windows bias by providing extensive PowerShell examples first, using Windows-centric tools and patterns, and referencing Windows Server images in VM creation. While Azure CLI examples (cross-platform) are present, PowerShell is given priority and more detail, and the VM creation example in PowerShell uses a Windows image exclusively.
Recommendations
  • Present Azure CLI examples before or alongside PowerShell examples to emphasize cross-platform support.
  • Add PowerShell Core examples or clarify that PowerShell commands can be run on Linux/macOS with PowerShell Core.
  • In VM creation examples, show both Windows and Linux images in PowerShell and CLI sections.
  • Explicitly mention platform compatibility for all command-line tools.
  • Balance the depth and detail of examples between PowerShell and CLI sections.
GitHub Create Pull Request
Load Balancer Azure Load Balancer health probes ...s/load-balancer/load-balancer-custom-probe-overview.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page references PowerShell as the primary method for creating a public load balancer, with no equivalent Linux/macOS CLI or Bash example in the 'Next steps' section. The mention of Azure PowerShell, Azure CLI, Templates, or API is grouped together, but only PowerShell is directly linked for a quickstart. This creates a subtle Windows bias by prioritizing Windows tooling and omitting Linux/macOS-specific guidance or examples.
Recommendations
  • Add equivalent Azure CLI (az) quickstart links and examples for Linux/macOS users alongside PowerShell references.
  • Provide Bash or shell script examples for probe configuration and management.
  • Ensure that all instructions and code samples are available for both PowerShell and Azure CLI, and present them in parallel or alternate order.
  • Explicitly state cross-platform compatibility and provide guidance for users on Linux/macOS.
GitHub Create Pull Request
Load Balancer Backend Pool Management ...main/articles/load-balancer/backend-pool-management.md
Medium Priority View Details →
Scanned: 2026-01-12 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 notable Windows bias. The PowerShell section is extensive, with detailed step-by-step instructions and examples for backend pool management, including VM creation using Windows images. The PowerShell examples are presented before CLI (which is cross-platform), and the VM creation example in PowerShell uses a Windows Server image by default, with no mention of Linux alternatives. The CLI section does provide Linux VM creation (Ubuntu), but the overall structure and depth favor Windows tools and patterns.
Recommendations
  • Add Linux-focused PowerShell examples (using Linux VM images) or clarify that PowerShell can be used on Linux/macOS.
  • Present CLI examples before PowerShell, or interleave them to avoid Windows-first bias.
  • Explicitly mention that Azure PowerShell is available cross-platform, and provide installation guidance for Linux/macOS.
  • Include Bash or shell script snippets for common operations, where appropriate.
  • Ensure parity in detail and completeness between PowerShell and CLI sections.
  • Highlight Linux/macOS compatibility in introductory sections.
GitHub Create Pull Request
Load Balancer Common error codes for Azure Instance Metadata Service (IMDS) ...icles/load-balancer/troubleshoot-load-balancer-imds.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page consistently links to Windows-specific Azure Instance Metadata Service (IMDS) documentation, both in error code explanations and in the 'Next steps' section. There are no references to Linux or cross-platform IMDS documentation, and no examples or mitigation steps tailored for Linux or macOS users. This may create friction for non-Windows users seeking platform-relevant guidance.
Recommendations
  • Include links to both Windows and Linux/macOS versions of the Azure IMDS documentation where appropriate.
  • Add examples or troubleshooting steps relevant to Linux (e.g., using curl or wget for IMDS requests) alongside any Windows/Powershell examples.
  • Clarify that IMDS is available and supported on both Windows and Linux VMs, and provide parity in guidance.
  • Where tabs or platform-specific instructions exist in linked documentation, mention them explicitly so users know to select their platform.
GitHub Create Pull Request
Load Balancer Tutorial: Protect your public load balancer with Azure DDoS Protection ...s/load-balancer/tutorial-protect-load-balancer-ddos.md
Medium Priority View Details →
Scanned: 2026-01-12 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 exclusively provides instructions for creating Windows Server VMs and installing IIS using Windows PowerShell. There are no examples or guidance for deploying Linux VMs, using Linux-native web servers (e.g., Apache, Nginx), or configuring them via SSH or Linux command line. The tutorial assumes Windows as the default platform for demonstration and omits Linux/macOS alternatives, making it notably Windows-centric.
Recommendations
  • Add parallel instructions for creating Linux VMs (e.g., Ubuntu) in the Azure portal.
  • Provide Linux-specific steps for installing and configuring a web server (such as Apache or Nginx) using SSH and shell commands.
  • Include example shell commands for Linux (e.g., apt install apache2, echo "Hello World from $(hostname)" > /var/www/html/index.html).
  • Clarify that either Windows or Linux VMs can be used and provide guidance for both.
  • Show both PowerShell and Bash/SSH examples for remote configuration.
  • Mention cross-platform tools and patterns (e.g., Azure CLI, SSH) where appropriate.
GitHub Create Pull Request
Load Balancer Create a cross-subscription internal load balancer ...er/cross-subscription-how-to-internal-load-balancer.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides both Azure PowerShell and Azure CLI examples for creating a cross-subscription internal load balancer, but the PowerShell (Windows-centric) example is presented first and in greater detail. The page is tagged with 'devx-track-azurepowershell', and the PowerShell section includes more granular steps and explanations, while the CLI section is shorter and less detailed. There are no Linux/macOS-specific tools or patterns mentioned, and no explicit Linux/macOS parity guidance.
Recommendations
  • Present Azure CLI (cross-platform) examples before PowerShell to avoid Windows-first bias.
  • Ensure CLI and PowerShell examples are equally detailed and comprehensive.
  • Add explicit notes confirming CLI commands work on Linux/macOS and provide troubleshooting tips for those platforms if needed.
  • Remove or balance 'devx-track-azurepowershell' custom tags with CLI equivalents.
  • Consider including Bash or other Linux-native scripting examples if relevant.
GitHub Create Pull Request
Load Balancer Outbound-only load balancer configuration ...e-docs/blob/main/articles/load-balancer/egress-only.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation provides step-by-step instructions for configuring an outbound-only load balancer in Azure, but all virtual machine creation and connectivity testing examples use Windows Server as the VM image and Microsoft Edge as the browser. There are no Linux VM creation examples, nor instructions for Linux-based connectivity testing. This creates a subtle but notable bias toward Windows environments.
Recommendations
  • Include parallel instructions for creating a Linux VM (e.g., Ubuntu) alongside the Windows VM example.
  • Provide guidance for connecting to a Linux VM via Bastion (using SSH and a browser such as Firefox or Chrome).
  • Show how to test outbound connectivity from a Linux VM (e.g., using curl or a browser).
  • Explicitly mention that the configuration works for both Windows and Linux VMs, and highlight any OS-specific considerations.
GitHub Create Pull Request
Load Balancer Attach a cross-subscription backend to an Azure Load Balancer ...d-balancer/cross-subscription-how-to-attach-backend.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides both Azure PowerShell and Azure CLI examples for creating and configuring a cross-subscription Azure Load Balancer. However, the PowerShell (Windows-centric) example is presented first and in greater detail, with step-by-step resource creation and variable usage. The Azure CLI (Linux/macOS-friendly) example is shorter and less detailed, potentially making it harder for non-Windows users to follow complex scenarios.
Recommendations
  • Present Azure CLI examples before or alongside PowerShell examples to avoid Windows-first bias.
  • Ensure CLI examples are as detailed and comprehensive as PowerShell ones, including variable usage and step-by-step resource creation.
  • Explicitly mention that Azure CLI works on Windows, Linux, and macOS, and provide links to installation guides for all platforms.
  • Add notes or sections for Bash scripting or automation for Linux/macOS users where appropriate.
GitHub Create Pull Request
Load Balancer Deploy IPv6 dual stack application ...https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/deploy-ipv4-ipv6-dual-stack-standard-load-balancer.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation page exhibits a Windows bias by exclusively providing examples for deploying Windows Server VMs (both in PowerShell and Azure CLI), using Windows-centric tools (PowerShell, RDP), and omitting any instructions or examples for deploying Linux-based VMs or using SSH for remote access. Windows terminology and tools are mentioned first and exclusively, with no Linux-specific guidance or parity.
Recommendations
  • Add examples for deploying Linux VMs (e.g., Ubuntu, CentOS) in both Azure CLI and PowerShell sections.
  • Include SSH-based access instructions and security group rules for port 22, alongside RDP/port 3389.
  • Show how to set up Linux administrator credentials (e.g., using SSH keys) in VM creation steps.
  • Balance the documentation by providing Linux examples before or alongside Windows examples.
  • Clarify that the process applies to both Windows and Linux VMs, and highlight any differences.
GitHub Create Pull Request
Load Balancer Add IPv6 to an IPv4 application in Azure Virtual Network - PowerShell .../load-balancer/ipv6-add-to-existing-vnet-powershell.md
Medium Priority View Details →
Scanned: 2026-01-12 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 biased towards Windows and PowerShell usage. All examples use Azure PowerShell cmdlets, and there are no equivalent instructions or examples for Linux/macOS users (e.g., Azure CLI or ARM templates). The prerequisites and workflow assume familiarity with PowerShell and Windows tooling, making it difficult for Linux/macOS users to follow without switching platforms or tools.
Recommendations
  • Add equivalent Azure CLI examples for each PowerShell command, as Azure CLI is cross-platform and commonly used on Linux/macOS.
  • Include a section on using ARM templates or Bicep for infrastructure-as-code deployments, which are platform-agnostic.
  • Explicitly mention that all steps can be performed from Azure Cloud Shell, which supports both Bash and PowerShell, and provide Bash/CLI instructions.
  • Reorder or parallelize examples so that Linux/macOS-friendly methods (CLI, templates) are shown alongside PowerShell, not after or omitted.
GitHub Create Pull Request
Load Balancer Upgrading from Basic Load Balancer - Guidance .../load-balancer/load-balancer-basic-upgrade-guidance.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page exhibits a notable Windows bias by recommending automated migration using PowerShell scripts as the primary method, without mentioning or providing equivalent CLI/bash examples for Linux/macOS users. The upgrade steps and automation guidance are centered on PowerShell, and no Linux-native tools or Azure CLI commands are referenced. This creates friction for users on non-Windows platforms who may not have access to PowerShell or prefer bash/CLI workflows.
Recommendations
  • Provide equivalent Azure CLI (az) commands and bash script examples for all migration steps, alongside PowerShell.
  • Explicitly mention that PowerShell Core is cross-platform, but also offer guidance for Linux/macOS users who may prefer bash or native CLI tools.
  • Reorder or parallelize automation guidance so that both PowerShell and CLI/bash options are presented together, rather than PowerShell-first.
  • Include links to Azure CLI documentation and migration scripts, if available.
  • Clarify prerequisites for each approach (e.g., PowerShell on Windows, Azure CLI on Linux/macOS).
GitHub Create Pull Request
Load Balancer Manage Azure Load Balancer health status ...es/load-balancer/load-balancer-manage-health-status.md
Medium Priority View Details →
Scanned: 2026-01-12 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 primarily in its guidance for obtaining a Bearer access token for the REST API. It references only the Windows PowerShell cmdlet Get-AzAccessToken, without mentioning Linux/macOS alternatives (such as Azure CLI or cross-platform authentication methods). No Linux-specific examples or parity are provided for this critical step. The rest of the documentation is platform-neutral, but the lack of Linux/macOS instructions for authentication creates friction for non-Windows users.
Recommendations
  • Add instructions for obtaining a Bearer access token using Azure CLI (az account get-access-token), which works on Linux, macOS, and Windows.
  • Include cross-platform examples for authentication, such as using curl with Azure CLI or environment variables.
  • Explicitly mention that PowerShell is available on Linux/macOS, but also provide Azure CLI examples as the default cross-platform method.
  • Where possible, order examples so that cross-platform methods (Azure CLI) are shown before or alongside Windows-specific tools.
GitHub Create Pull Request
Load Balancer Configure Azure Load Balancer distribution mode ...icles/load-balancer/load-balancer-distribution-mode.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation page presents configuration instructions for Azure Load Balancer with a notable Windows bias. The PowerShell example is given before the Azure CLI example, and PowerShell is a Windows-centric tool. The CLI section is present, but the 'Next steps' links favor PowerShell-based quickstarts. There are no explicit Linux/macOS examples or mentions of platform-specific considerations for CLI usage.
Recommendations
  • Present Azure CLI instructions before PowerShell, as CLI is cross-platform.
  • Include explicit notes that Azure CLI works on Linux/macOS and provide installation/setup links for those platforms.
  • Add examples or screenshots for Linux/macOS users where relevant (e.g., terminal usage).
  • Balance 'Next steps' links to include CLI-based quickstarts and guides for Linux/macOS users.
  • Clarify that PowerShell Core is available cross-platform, if relevant, and provide guidance for non-Windows users.
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
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation demonstrates a notable Windows bias. PowerShell is featured heavily, with entire sections and automation scripts relying exclusively on PowerShell modules and tooling. Prerequisites and automation steps require installation of PowerShell and Azure PowerShell modules, with no mention of Bash, shell scripting, or Linux-native alternatives. While Azure CLI examples are provided for manual migration, advanced and automated migration is only documented for PowerShell, leaving Linux/macOS users without parity for these workflows.
Recommendations
  • Provide Bash or shell script equivalents for automation steps, especially for the migration of NAT Pools to NAT Rules.
  • Document how to perform automated migration using Azure CLI or REST API, not just PowerShell.
  • Include installation instructions for Azure CLI and scripting examples for Linux/macOS users.
  • Avoid stating PowerShell prerequisites as universal; clarify when alternatives are available.
  • Ensure that examples and tooling are presented in a cross-platform manner, or explicitly note platform limitations.
GitHub Create Pull Request
Load Balancer Load Balancer TCP Reset and idle timeout in Azure ...main/articles/load-balancer/load-balancer-tcp-reset.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page references .NET examples for TCP keep-alive configuration, which are primarily relevant to Windows environments. There are no examples or references for configuring TCP keep-alive on Linux or macOS systems, nor are cross-platform tools or commands mentioned. This creates a subtle bias toward Windows users by omitting guidance for Linux/macOS administrators.
Recommendations
  • Include examples for configuring TCP keep-alive on Linux (e.g., using sysctl, socket options, or iptables).
  • Reference cross-platform programming languages and libraries (such as Python, Java, or Go) for TCP keep-alive implementation.
  • Provide links to official Linux documentation or community resources for TCP keep-alive settings.
  • Clarify that the .NET example is just one option and suggest alternatives for non-Windows environments.
GitHub Create Pull Request
Load Balancer Troubleshoot Azure Load Balancer health probe status ...ncer/load-balancer-troubleshoot-health-probe-status.md
Medium Priority View Details →
Scanned: 2026-01-12 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 notable Windows bias. Troubleshooting steps frequently reference Windows-specific tools (PsPing, TCPing, Netsh), and command examples are primarily given for Windows (e.g., 'netstat -an', 'netsh advfirewall'). Linux equivalents are mentioned only as alternatives and lack detailed usage instructions or examples. There are no Linux/macOS-specific troubleshooting workflows or tool recommendations, making it harder for non-Windows users to follow the guidance.
Recommendations
  • Provide Linux/macOS equivalents for all Windows tools mentioned (e.g., suggest 'nc', 'ss', or 'nmap' for port/probe testing, 'iptables' or 'ufw' for firewall checks).
  • Include example commands for Linux/macOS alongside Windows commands, with clear syntax and expected output.
  • Mention cross-platform tools where possible and avoid assuming users have access to Windows-only utilities.
  • Structure troubleshooting steps to present Windows and Linux/macOS guidance in parallel, rather than Windows-first.
  • Add notes or links to installation instructions for Linux/macOS 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
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates a notable Windows bias. Troubleshooting steps and network capture instructions reference Windows-specific tools (PsPing, Netsh) and commands, with no mention of Linux/macOS equivalents. All example commands are Windows-centric, and there is no guidance for performing similar diagnostics on Linux systems. This creates friction for Linux users attempting to follow the troubleshooting process.
Recommendations
  • Include Linux/macOS equivalents for network diagnostics, such as using 'ping', 'nc' (netcat), 'ss', or 'tcpdump' for network traces.
  • Provide example commands for both Windows and Linux platforms side-by-side.
  • Mention cross-platform tools or clarify which steps are platform-specific.
  • Add guidance for collecting network captures on Linux (e.g., using 'tcpdump' or 'wireshark').
  • Explicitly state when a tool or command is Windows-only and offer alternatives for other platforms.
GitHub Create Pull Request
Load Balancer Manage Administrative State in Azure Load Balancer ...in/articles/load-balancer/manage-admin-state-how-to.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation consistently references Windows-based virtual machines in all example links and prerequisites, omitting explicit Linux VM guidance. All VM creation links point to Windows instructions, and there are no Linux-specific examples or parity in the prerequisites or walkthroughs. While Azure CLI and PowerShell are both cross-platform, the documentation implicitly assumes Windows environments for backend pool instances.
Recommendations
  • Add Linux VM creation links and instructions alongside Windows VM links in the prerequisites for each method (portal, PowerShell, CLI).
  • Include explicit examples and notes for managing admin state with Linux-based backend pool instances.
  • Clarify that Azure CLI and PowerShell commands work for both Windows and Linux VMs, and provide sample resource names for Linux VMs.
  • Ensure that all referenced quickstart and how-to guides have Linux equivalents and link to them where appropriate.
GitHub Create Pull Request
Load Balancer Move an Azure Load Balancer to another Azure region ...ad-balancer/move-across-regions-azure-load-balancer.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
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 using the Azure portal and Azure PowerShell, with all command-line examples and automation steps relying exclusively on PowerShell cmdlets and Windows tools (e.g., notepad.exe). There are no CLI examples using cross-platform tools such as Azure CLI, nor are there any Linux/macOS-specific instructions or shell commands. The PowerShell approach is presented as the only scripting method, and Windows-centric tools are referenced directly. This creates friction for Linux/macOS users who may not have access to PowerShell or prefer bash/CLI workflows.
Recommendations
  • Add equivalent Azure CLI (az) examples for all PowerShell steps, including resource export, template editing, and deployment.
  • Replace or supplement references to Windows-only tools (e.g., notepad.exe) with cross-platform editors (e.g., nano, vim, code) or generic instructions.
  • Explicitly mention that PowerShell Core is available cross-platform, but provide CLI alternatives for users who prefer bash/zsh.
  • Reorder sections so that cross-platform methods (Azure CLI, portal) are presented before or alongside PowerShell.
  • Include notes or links for Linux/macOS users on installing and using Azure CLI and PowerShell Core.
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
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation provides both Azure CLI and PowerShell examples for deploying and managing resources, but PowerShell (a Windows-centric tool) is mentioned first in the deployment section and is referenced in command explanations. There are no explicit Linux/macOS shell examples (e.g., bash), and PowerShell is presented as a primary method, which may create friction for Linux/macOS users unfamiliar with PowerShell.
Recommendations
  • Present Azure CLI examples before PowerShell, as CLI is cross-platform and preferred by many Linux/macOS users.
  • Explicitly mention that Azure CLI commands work natively on Linux/macOS and provide bash-specific instructions where appropriate.
  • Remove or clarify any references that suggest PowerShell is the default or primary method, emphasizing CLI parity.
  • Add a note or section for Linux/macOS users, confirming that all CLI steps are fully supported on their platforms.
  • Ensure cleanup examples use Azure CLI first, and correct any PowerShell-only commands (e.g., Remove-AzResourceGroup should be az group delete for CLI).
GitHub Create Pull Request
Load Balancer Quickstart: Create a public load balancer - Azure CLI ...lancer/quickstart-load-balancer-standard-public-cli.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example Powershell Heavy
Summary
The documentation exclusively creates Windows Server VMs (win2019datacenter) and uses PowerShell commands for configuration (IIS installation and website setup). No Linux VM creation examples or Linux web server setup instructions are provided. This creates friction for users who prefer or require Linux-based backend servers.
Recommendations
  • Add parallel examples for creating Linux VMs (e.g., using --image UbuntuLTS) alongside the Windows VM creation steps.
  • Provide instructions and az vm extension set examples for installing a Linux web server (e.g., Apache or Nginx) and setting up a test page.
  • Explicitly mention that both Windows and Linux VMs are supported and link to relevant Linux quickstarts.
  • If scripting is required, use cross-platform shell commands (bash) or provide both PowerShell and bash alternatives.
GitHub Create Pull Request
← Previous Page 2 of 5 Next →