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 51-75 of 117 flagged pages
Load Balancer Quickstart: Create a public load balancer - ARM template ...r/quickstart-load-balancer-standard-public-template.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 provides only Azure PowerShell examples for deploying the ARM template, with no equivalent Azure CLI (bash) or Linux/macOS shell instructions. The step-by-step deployment section is written for PowerShell users, and the screenshots and output are PowerShell-specific. While the text briefly mentions that Azure CLI and REST API can be used, no examples or guidance are provided for those methods. This creates friction for Linux/macOS users who typically use Azure CLI in bash or other shells.
Recommendations
  • Add Azure CLI (bash) examples for deploying the ARM template, including step-by-step instructions and sample output.
  • Present both PowerShell and CLI examples side-by-side or in tabs, allowing users to choose their preferred environment.
  • Update screenshots and instructions to reflect both Windows and Linux/macOS workflows.
  • Explicitly mention platform compatibility and provide links to relevant CLI documentation.
GitHub Create Pull Request
Load Balancer Quickstart: Create an internal load balancer - Azure CLI ...ncer/quickstart-load-balancer-standard-internal-cli.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 demonstrates a notable Windows bias. All VM creation examples use Windows images (win2022datacenter, Win2019Datacenter) with no mention of Linux alternatives. The IIS installation uses PowerShell commands and Windows-specific tooling (Add-WindowsFeature, Internet Explorer), with no Linux web server (e.g., Apache, Nginx) or shell examples. Testing instructions reference Internet Explorer, a Windows-only browser. There are no Linux/macOS-specific instructions or parity examples.
Recommendations
  • Provide parallel examples for Linux VMs (e.g., use UbuntuLTS image in az vm create).
  • Show how to install a web server (e.g., Apache or Nginx) on Linux VMs using az vm extension set with bash commands.
  • Include test instructions for Linux/macOS users (e.g., using curl or a browser available on all platforms).
  • Avoid referencing Windows-only tools (e.g., Internet Explorer); use cross-platform alternatives.
  • Explicitly mention that the steps work for both Windows and Linux, or call out differences where applicable.
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-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 page demonstrates a notable Windows bias. All VM creation examples use Windows Server images, and the only instructions for installing a web server (IIS) are provided using Windows PowerShell commands. There are no Linux VM examples, nor are there instructions for installing or configuring a web server on Linux. The testing steps also assume the use of Microsoft Edge on a Windows VM. This creates friction for users who prefer or require Linux-based environments.
Recommendations
  • Include parallel instructions for creating a Linux VM (e.g., Ubuntu) alongside the Windows VM example.
  • Provide Linux-specific steps for installing a web server (e.g., Apache or Nginx) and customizing the index.html file.
  • Offer shell (bash) command examples for Linux VM setup, in addition to PowerShell for Windows.
  • Mention cross-platform browser options for testing (e.g., Firefox, Chrome) rather than only Microsoft Edge.
  • Clearly indicate that the load balancer works with both Windows and Linux VMs, and link to relevant Linux 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-12 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 demonstrates a notable Windows bias in the 'Install IIS' section, where only Windows PowerShell commands are provided for installing IIS on backend VMs. There are no equivalent instructions for Linux VMs (e.g., using Apache/Nginx with Bash commands). The workflow assumes Windows Server as the default OS for VMs, referencing Windows-specific tools and patterns (PowerShell, IIS), and does not mention Linux alternatives or provide parity in examples. The order and content reinforce Windows as the primary platform, leaving Linux/macOS users without guidance for completing the task.
Recommendations
  • Add a parallel section for Linux VM setup, showing how to install and configure a web server (e.g., Apache or Nginx) using Bash commands.
  • Provide example commands for both Windows (PowerShell/IIS) and Linux (Bash/Apache/Nginx) when configuring backend servers.
  • Explicitly state that the instructions are for Windows VMs and offer links or inline instructions for Linux VM scenarios.
  • Ensure screenshots and walkthroughs include both Windows and Linux VM options.
  • Mention cross-platform considerations in the prerequisites and setup sections.
GitHub Create Pull Request
Load Balancer Tutorial: Add Azure Load Balancer to an existing Virtual Machine Scale Set - Azure portal ...-balancer/tutorial-add-lb-existing-scale-set-portal.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 demonstrates a bias towards Windows by exclusively using Windows Server as the VM image in the scale set creation steps, with no mention or example of Linux-based images. All configuration steps are performed via the Azure portal, which is cross-platform, but the only OS-specific reference is Windows, and there are no Linux alternatives or parity notes.
Recommendations
  • Include examples using popular Linux distributions (e.g., Ubuntu, CentOS) when creating VM scale sets.
  • Add a note clarifying that Linux images are supported and provide guidance for Linux-specific configuration if needed.
  • Show parallel steps or screenshots for Linux-based VM scale sets where OS-specific settings may differ (e.g., SSH key authentication instead of password).
  • Ensure that any OS-specific guidance (e.g., administrator account setup) covers both Windows and Linux scenarios.
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
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 🔧 Windows Tools
Summary
The documentation demonstrates a bias toward Windows by only referencing IIS (Internet Information Server) and showing the default IIS Windows Server web page as the deployment verification step. There are no Linux-based examples (e.g., Apache, Nginx), nor is there mention of Linux VM configuration or verification. The template configures IIS, a Windows-specific tool, and the verification step is Windows-centric.
Recommendations
  • Provide parallel Linux examples, such as configuring Apache or Nginx on Linux VMs.
  • Show how to verify deployment using a Linux-based web server (e.g., default Apache page) in addition to IIS.
  • Clarify that the template can be modified for Linux VMs and provide sample parameters or scripts for Linux.
  • Include screenshots or instructions for Linux verification steps.
  • Mention Linux VM options in the template review section.
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
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 deploying and configuring Windows Server virtual machines, including installation of IIS via Windows PowerShell. There are no examples or guidance for Linux-based VMs, nor instructions for installing a web server (such as Apache or Nginx) on Linux. The only OS image mentioned is Windows, and all configuration and testing steps assume a Windows environment, creating a notable bias toward Windows users.
Recommendations
  • Add parallel instructions for creating Linux VMs (e.g., Ubuntu or CentOS) in the Azure portal.
  • Provide Linux-specific steps for installing a web server (such as Apache or Nginx) using Bash or the Azure Cloud Shell.
  • Include sample shell commands for Linux (e.g., apt install apache2, echo 'Hello World from $(hostname)' > /var/www/html/index.html).
  • Mention both Windows and Linux images when selecting the VM OS during creation.
  • Ensure testing steps (accessing the web server) are valid for both Windows IIS and Linux web servers.
GitHub Create Pull Request
Load Balancer Tutorial: Create an Azure Global Load Balancer ...articles/load-balancer/tutorial-cross-region-portal.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 demonstrates a moderate Windows bias. While it provides Azure Portal, Azure CLI, and Azure PowerShell instructions, several patterns favor Windows users: PowerShell is featured as a primary automation method, and the test scenario assumes IIS (a Windows-only web server) is running on backend VMs. There are no explicit Linux-specific examples, such as using Apache/Nginx for backend pools, nor are there Linux shell commands for VM management or verification. The CLI examples are cross-platform, but the overall flow and testing steps implicitly assume a Windows environment.
Recommendations
  • Include Linux-specific backend pool examples, such as deploying Apache or Nginx on Linux VMs.
  • In the 'Test the load balancer' section, mention how to verify with a Linux-based web server (e.g., using curl or checking Apache/Nginx default page).
  • Provide explicit instructions or links for creating Linux VMs in backend pools.
  • Clarify that Azure CLI commands work on Linux/macOS and Windows, and provide shell-specific notes if needed.
  • Avoid assuming IIS is the default backend; offer parity for Linux web servers.
  • Consider showing Linux shell commands for stopping VMs (e.g., az vm deallocate) alongside portal/PowerShell instructions.
GitHub Create Pull Request
Load Balancer Tutorial: Configure outbound connectivity with a gateway load balancer ...oad-balancer/tutorial-gateway-outbound-connectivity.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 virtual machines, both in prerequisites and example steps, without mentioning or providing guidance for Linux VM deployment or configuration. All VM-related instructions and links are Windows-centric, and there are no Linux-specific examples or parity notes.
Recommendations
  • Include references and links for creating Linux VMs alongside Windows VM instructions.
  • Clarify that the tutorial applies equally to Linux VMs, and note any platform-specific differences if relevant.
  • Provide examples or screenshots for Linux VM configuration where applicable.
  • Ensure terminology and instructions are platform-neutral unless a step is genuinely Windows-specific.
GitHub Create Pull Request
Load Balancer Tutorial: Load balance VMs within an availability zone - Azure portal ...ttps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/tutorial-load-balancer-standard-public-zonal-portal.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The tutorial includes a step to create a basic Internet Information Services (IIS) site, which is a Windows-only web server. There is no mention of Linux alternatives (e.g., Apache, Nginx) or instructions for deploying a web server on Linux VMs. This creates a bias toward Windows environments and may exclude or confuse users intending to deploy Linux-based workloads.
Recommendations
  • Provide parallel instructions for deploying a web server on Linux VMs (e.g., Apache or Nginx).
  • Include examples and screenshots for both Windows and Linux VM configurations.
  • Clarify that IIS is Windows-specific and suggest Linux alternatives for non-Windows users.
  • Ensure that all steps (including health probe configuration and testing) are covered for both OS types.
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
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 uses Windows Server images for all virtual machines and provides only Windows PowerShell examples for configuring IIS. There are no Linux VM options, nor are there Bash or Linux-native instructions for installing a web server. The tutorial assumes Windows as the default platform, which may create friction for users preferring or requiring Linux-based deployments.
Recommendations
  • Provide parallel instructions for deploying Linux VMs (e.g., Ubuntu or CentOS) alongside Windows VMs.
  • Include Bash/SSH examples for installing Apache or Nginx on Linux VMs, mirroring the IIS setup for Windows.
  • Offer guidance on using the Azure portal to select Linux images and configure Linux-specific settings.
  • Clarify that both Windows and Linux VMs are supported in backend pools and link to relevant Linux documentation.
  • Present examples for both platforms side-by-side or allow users to select their preferred OS path in the tutorial.
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-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation exclusively uses Windows Server as the example operating system for the virtual machine, with no mention of Linux or macOS alternatives. All instructions for VM creation specify Windows Server 2022, and testing steps reference Microsoft Edge, a Windows browser. There are no Linux-specific examples, nor any guidance for Linux VM creation, configuration, or connectivity testing.
Recommendations
  • Include parallel instructions for creating a Linux VM (e.g., Ubuntu) alongside the Windows VM steps.
  • Provide example administrator account setup for Linux (e.g., SSH key or password).
  • Offer connectivity testing instructions using Linux tools (e.g., curl, wget, or Firefox/Chromium browser).
  • Clarify that the load balancer configuration applies to both Windows and Linux VMs.
  • Add notes or sections highlighting any OS-specific considerations for outbound connectivity.
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-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias by exclusively recommending and providing PowerShell scripts for automated migration, with no mention of Azure CLI, Bash, or Linux/macOS-compatible automation. The 'Upgrade using automated scripts' section only references PowerShell, and the manual steps and linked quickstarts are focused on Portal usage, which is platform-neutral but does not compensate for the lack of Linux-friendly automation. There are no Linux-specific or cross-platform CLI examples, and Windows tooling is presented as the default and recommended approach.
Recommendations
  • Provide equivalent Azure CLI scripts for automated migration, ensuring Linux/macOS users have parity with PowerShell automation.
  • Explicitly mention that PowerShell scripts can be run on Linux/macOS with PowerShell Core, or clarify any limitations.
  • Add Bash script examples or guidance for users who prefer shell scripting.
  • Present CLI (Azure CLI) examples before or alongside PowerShell examples to avoid Windows-first bias.
  • Include a table or section comparing automation options for different platforms.
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-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation consistently links to Windows-specific pages and tabs for further information about IMDS, such as HTTP verbs and rate limiting. There are no references to Linux or cross-platform usage, nor are Linux/macOS equivalents or examples provided. This creates friction for non-Windows users seeking parity.
Recommendations
  • Include links to Linux/macOS documentation or tabs where available, such as /azure/virtual-machines/linux/instance-metadata-service.
  • Clarify that IMDS is accessible from any OS and provide sample requests using Linux tools (e.g., curl, wget) alongside any Windows/PowerShell examples.
  • Ensure that mitigation steps and next steps reference both Windows and Linux documentation, or use cross-platform examples.
  • Add a note or section explicitly addressing Linux/macOS usage and troubleshooting.
GitHub Create Pull Request
Load Balancer Tutorial: Add Azure Load Balancer to an existing Virtual Machine Scale Set - Azure portal ...-balancer/tutorial-add-lb-existing-scale-set-portal.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation demonstrates a Windows bias by specifying Windows Server as the default image for the Virtual Machine Scale Set, with no mention of Linux alternatives or guidance for Linux users. All examples and instructions assume Windows, and there are no Linux-specific steps or parity notes.
Recommendations
  • Explicitly mention that both Windows and Linux images are supported for VM Scale Sets.
  • Provide parallel instructions or notes for selecting a Linux image (e.g., Ubuntu, CentOS) in the 'Image' field.
  • Add guidance for Linux administrator account setup (e.g., SSH key authentication instead of password).
  • Include a brief section or callout highlighting any differences in configuration or management for Linux-based scale sets.
  • Ensure screenshots and walkthroughs do not imply Windows exclusivity.
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-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools Windows First
Summary
The documentation provides step-by-step instructions for creating a public load balancer in Azure using the portal, but when configuring the backend VMs, it exclusively demonstrates how to install and configure IIS using Windows PowerShell. There are no examples or guidance for Linux-based VMs, such as installing Apache or Nginx, nor are there Bash or Linux command-line instructions. The use of Windows PowerShell and IIS is presented as the default, with no mention of Linux alternatives.
Recommendations
  • Add parallel instructions for Linux VMs, such as how to install Apache or Nginx using Bash commands.
  • Include examples of connecting to Linux VMs via SSH and configuring web servers.
  • Present both Windows and Linux options side-by-side, or clarify that the example is Windows-specific and link to Linux-specific guides.
  • Avoid assuming Windows as the default; mention cross-platform possibilities in the prerequisites and installation steps.
GitHub Create Pull Request
Load Balancer Tutorial: Load balance VMs within an availability zone - Azure portal ...ttps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/tutorial-load-balancer-standard-public-zonal-portal.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The tutorial includes a step to create a basic Internet Information Services (IIS) site, which is a Windows-only web server. There is no mention of Linux alternatives (such as Apache or Nginx), nor are there instructions for deploying a web server on Linux VMs. This creates a bias toward Windows environments and may exclude or confuse users who wish to use Linux-based VMs.
Recommendations
  • Provide parallel instructions for deploying a web server on Linux VMs, such as using Apache or Nginx.
  • Explicitly mention that IIS is Windows-only and offer Linux alternatives.
  • Include screenshots or step-by-step guides for both Windows and Linux VM configurations.
  • Clarify that the load balancer works with both Windows and Linux VMs, and provide examples for each.
GitHub Create Pull Request
Load Balancer Backend Pool Management ...main/articles/load-balancer/backend-pool-management.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits a notable Windows bias. The PowerShell section is extensive, with detailed step-by-step examples for backend pool management, network interface creation, and VM deployment, all using Azure PowerShell (primarily used on Windows). The VM creation example specifically uses a Windows Server image. The CLI section is present and provides parity for most operations, but the PowerShell examples are listed first and are more detailed. There is no mention of Bash scripting, Linux-specific tools, or macOS considerations, and the PowerShell examples do not clarify cross-platform usage (e.g., PowerShell Core on Linux/macOS).
Recommendations
  • Add Bash and/or Linux shell script examples for backend pool management, network interface creation, and VM deployment.
  • Clarify that Azure PowerShell can be used on Linux/macOS via PowerShell Core, or provide links to installation guides for non-Windows platforms.
  • Include Linux VM creation examples in the PowerShell section, not just Windows Server.
  • Alternate the order of examples, sometimes presenting CLI or Linux-native methods first.
  • Explicitly mention platform compatibility for all tools and commands.
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-11 06:20
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 backend for Azure Load Balancer. However, the PowerShell example is presented first and in much greater detail, with step-by-step commands and variable usage, while the Azure CLI example is more concise and lacks equivalent depth. This structure may favor Windows users or those familiar with PowerShell, potentially creating friction for Linux/macOS users who typically use Azure CLI.
Recommendations
  • Present Azure CLI and PowerShell examples with equal detail and clarity, ensuring parity in the steps and explanations.
  • Alternate the order of examples or explicitly state that both methods are fully supported on all platforms.
  • Add notes clarifying that Azure CLI is cross-platform and preferred for Linux/macOS users.
  • Include troubleshooting or tips specific to Linux/macOS environments if any differences exist.
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-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a notable Windows bias. All VM creation examples use Windows Server images only, both in Azure CLI and PowerShell. The PowerShell tab is presented first in the main deployment section, and all scripting examples use PowerShell, which is a Windows-centric tool. Remote access instructions focus exclusively on RDP (port 3389), which is specific to Windows, with no mention of SSH or Linux VM options. There are no examples for deploying Linux VMs, nor any Linux-specific remote access instructions. The ARM template section is neutral, but the procedural sections lack Linux parity.
Recommendations
  • Add examples for deploying Linux VMs (e.g., Ubuntu, CentOS) alongside Windows Server in both Azure CLI and PowerShell sections.
  • Include SSH-based remote access instructions and network security group rules for port 22, in addition to RDP for Windows.
  • Present Azure CLI examples before or alongside PowerShell, as CLI is cross-platform.
  • Explicitly mention that both Windows and Linux VMs are supported, and provide sample commands for both.
  • Where PowerShell is used, clarify that Azure CLI is available and suitable for Linux/macOS users.
  • Add notes or links to Linux VM documentation for users who prefer non-Windows environments.
GitHub Create Pull Request
Load Balancer Create a global load balancer with cross-subscription backends ...d-balancer/cross-subscription-how-to-global-backend.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation exhibits a moderate Windows bias by prioritizing Azure PowerShell (a Windows-centric tool) in every section, providing more detailed PowerShell instructions, and referencing PowerShell-specific installation and usage patterns before Azure CLI. The Azure PowerShell tab is consistently presented first, and the prerequisites and examples assume familiarity with PowerShell and its conventions. While Azure CLI examples are present and reasonably complete, the overall tone and structure favor Windows users and PowerShell workflows.
Recommendations
  • Alternate the order of PowerShell and CLI tabs so that neither is consistently first.
  • Add explicit notes that both Azure PowerShell and Azure CLI are cross-platform, and clarify that PowerShell Core is available on Linux/macOS.
  • Provide parity in depth and explanation for Azure CLI examples, ensuring both tabs have equally detailed steps and context.
  • Include a brief section or callout for Linux/macOS users, mentioning platform-specific considerations (e.g., shell syntax differences, installation instructions for PowerShell Core and Azure CLI on Linux/macOS).
  • Avoid language that implies PowerShell is the default or preferred tool; present both options neutrally.
GitHub Create Pull Request
Load Balancer Inbound NAT rules .../blob/main/articles/load-balancer/inbound-nat-rules.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Missing Linux Example Windows First
Summary
The documentation page does not provide any OS-specific examples, but all references to connecting to virtual machines and port forwarding are generic and do not mention Linux or macOS tools. There is a subtle 'Windows-first' bias in that the lack of Linux/macOS examples or references may leave non-Windows users uncertain about how to connect to VMs using NAT rules, especially since Azure documentation often defaults to Windows-centric tools like RDP and PowerShell in related pages.
Recommendations
  • Add explicit examples for connecting to Linux VMs using SSH through NAT rules, including command-line instructions for Linux/macOS clients.
  • Mention common Linux/macOS tools (e.g., OpenSSH, scp) alongside any references to Windows tools.
  • Ensure that tutorials and next steps include parity for Linux/macOS scenarios, not just Windows-centric workflows.
  • Where screenshots or walkthroughs are provided, include both Windows and Linux client perspectives.
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-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation provides configuration instructions for Azure Load Balancer distribution mode using the Azure Portal (web UI), PowerShell, and Azure CLI. PowerShell is featured as a primary automation example, which is a Windows-centric tool, and is listed before the CLI. The CLI example is cross-platform, but there are subtle signs of Windows bias: PowerShell is given a dedicated section, and the 'Next steps' links include a PowerShell-specific quickstart. There are no Linux/macOS-specific shell examples (e.g., Bash), nor is there mention of Linux-specific considerations.
Recommendations
  • Add Bash or shell script examples for Linux/macOS users where appropriate.
  • Ensure CLI examples use syntax and conventions that work seamlessly on Linux/macOS (e.g., line continuations, environment setup).
  • Balance PowerShell and CLI coverage, possibly listing CLI before PowerShell since CLI is cross-platform.
  • Include links to Linux/macOS quickstart guides in the 'Next steps' section.
  • Explicitly state that Azure CLI works on all platforms and provide installation/setup guidance for Linux/macOS.
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-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation exclusively uses Azure PowerShell commands and patterns throughout, with no mention or examples of Azure CLI, Bash, or Linux/macOS workflows. All code samples, prerequisites, and instructions are PowerShell-centric, which is most familiar to Windows users. There is no guidance for users who prefer or require Linux-native tools, nor any parity for cross-platform command-line usage.
Recommendations
  • Add equivalent Azure CLI (az) examples for each step, with Bash syntax where appropriate.
  • Explicitly mention that all steps can be performed on Linux/macOS using Azure CLI, and link to relevant CLI documentation.
  • Reorder or parallelize examples so that Linux/macOS and Windows users see their respective instructions side-by-side.
  • Clarify tool requirements for cross-platform users (e.g., Azure CLI installation, Bash shell usage).
  • Update the prerequisites section to include links and instructions for Azure CLI and Bash usage.
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-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page exhibits mild Windows bias. In the 'Next steps' section, the only explicit example for creating a load balancer is via PowerShell, a Windows-centric tool, with no equivalent Azure CLI, Bash, or Linux/macOS example provided. The mention of PowerShell, Azure CLI, Templates, or API in the 'Design guidance' section is neutral, but the ordering places PowerShell first. There are no command-line examples or walkthroughs for Linux/macOS users, and no mention of Bash or shell scripting. The page does not reference Windows-specific tools elsewhere, but the lack of Linux parity in examples and guidance creates friction for non-Windows users.
Recommendations
  • Add Azure CLI and Bash examples for creating and managing health probes and load balancers, especially in the 'Next steps' section.
  • Provide explicit instructions or links for Linux/macOS users alongside PowerShell examples.
  • When listing tools (PowerShell, CLI, Templates, API), alternate or randomize the order, or group by platform.
  • Ensure all walkthroughs and quickstarts have both Windows (PowerShell) and Linux/macOS (CLI/Bash) versions.
GitHub Create Pull Request
← Previous Page 3 of 5 Next →