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 226-250 of 388 flagged pages
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-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation provides detailed instructions for moving Azure Load Balancers between regions using the Azure portal and Azure PowerShell. All command-line examples use Azure PowerShell, which is primarily a Windows-centric tool, and references to editors like 'notepad.exe' further reinforce Windows bias. There are no examples or guidance for Linux/macOS users, such as using Azure CLI or cross-platform editors. This creates friction for non-Windows users who may prefer or require Linux-native tools.
Recommendations
  • Add equivalent Azure CLI examples for all PowerShell commands, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Replace or supplement references to 'notepad.exe' with instructions for using cross-platform editors (e.g., 'nano', 'vim', 'code', or generic 'open in your preferred editor').
  • Explicitly mention that all steps can be performed on Linux/macOS using Azure CLI and compatible editors.
  • Provide a tab or section for Linux/macOS workflows, or clarify tool parity in the prerequisites.
  • Avoid language or tool choices that assume a Windows environment unless strictly necessary.
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-14 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 virtual machine creation examples use Windows images (win2022datacenter, Win2019Datacenter) with no mention of Linux alternatives. The IIS installation step uses PowerShell commands and Windows-specific tooling, with no Linux equivalent provided (e.g., Apache or Nginx setup). The testing instructions reference Internet Explorer, a Windows-only browser, and do not mention Linux/macOS alternatives. No Linux VM images, shell commands, or Linux web server setup instructions are included.
Recommendations
  • Provide parallel examples using popular Linux VM images (e.g., UbuntuLTS) when creating VMs.
  • Include instructions for installing a web server on Linux VMs (e.g., Apache or Nginx) using bash commands.
  • Offer testing steps for Linux/macOS users, such as using curl or a browser available on those platforms.
  • Avoid referencing Windows-only tools (e.g., Internet Explorer, PowerShell) exclusively; mention cross-platform alternatives.
  • Explicitly state that the steps apply to both Windows and Linux, or clarify any platform-specific requirements.
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-14 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. VM creation defaults to Windows Server, and all instructions for installing and configuring IIS use Windows PowerShell commands. There are no Linux VM examples, nor are there instructions for installing a web server on Linux. Windows tools and workflows (PowerShell, IIS, Microsoft Edge) are referenced exclusively, making it difficult for Linux users to follow along or replicate the setup.
Recommendations
  • Add parallel instructions for creating a Linux VM (e.g., Ubuntu) in the portal.
  • Provide Linux-specific steps for installing a web server (e.g., Apache or Nginx) and customizing the index.html file.
  • Include Bash command examples for Linux VMs alongside PowerShell for Windows.
  • Mention using SSH for Linux VM access, and suggest a cross-platform browser for testing (e.g., Firefox or Chrome).
  • Clearly indicate that the steps can be performed on either Windows or Linux VMs, and link to relevant documentation for both.
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-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation provides deployment instructions using Azure PowerShell and Azure CLI, with PowerShell examples shown first in several sections. There is a notable emphasis on PowerShell, which is traditionally associated with Windows, and no explicit mention of Linux/macOS shell environments or alternative command-line tools. The cleanup section incorrectly uses PowerShell syntax in the CLI tab, and there are no Linux-specific notes or troubleshooting tips.
Recommendations
  • Ensure Azure CLI examples use standard Bash syntax and are shown first, as CLI is cross-platform.
  • Correct the cleanup section to use 'az group delete' for Azure CLI instead of PowerShell commands.
  • Add explicit notes that Azure CLI commands work on Linux/macOS and provide any necessary environment setup instructions.
  • Include troubleshooting tips or links for Linux/macOS users, such as installing Azure CLI or using Bash.
  • Balance the order of examples, alternating between CLI and PowerShell or showing CLI first to reflect cross-platform usage.
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-14 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools Windows First
Summary
The documentation page demonstrates a notable Windows bias, especially in the 'Install IIS' section, where only Windows PowerShell commands are provided for installing and configuring IIS on the backend VMs. There are no instructions or examples for deploying a Linux-based web server (such as Apache or Nginx) on Linux VMs, nor are Linux command-line equivalents given. The workflow assumes Windows VMs and Windows tooling (PowerShell, IIS), and does not mention Linux alternatives or provide parity for non-Windows users.
Recommendations
  • Add a parallel section for Linux VMs, showing how to install Apache or Nginx using Bash commands (e.g., apt, yum) and configure a custom index.html.
  • Explicitly state that both Windows and Linux VMs are supported, and provide guidance for choosing between them.
  • Include Linux command-line examples alongside PowerShell, and mention SSH as a connection method for Linux VMs.
  • Reference Linux documentation and tools (e.g., systemctl, nano, vi) where appropriate.
  • Consider reordering or splitting instructions so that Windows and Linux paths are equally visible and accessible.
GitHub Create Pull Request
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-14 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 Azure CLI (bash) or Linux/macOS-specific instructions. The deployment walkthrough is centered on PowerShell and Windows patterns, and Linux alternatives are mentioned only in passing, with no concrete examples or guidance.
Recommendations
  • Add equivalent Azure CLI (bash) examples for template deployment, including step-by-step instructions.
  • Present both PowerShell and CLI examples side-by-side, or allow users to select their preferred platform.
  • Explicitly mention that Azure Cloud Shell supports both bash and PowerShell, and clarify how Linux/macOS users can follow the quickstart.
  • Ensure screenshots and output examples are not Windows-specific (e.g., avoid showing only PowerShell output).
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-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page consistently references Windows-specific resources and links, such as '/azure/virtual-machines/windows/instance-metadata-service', without mentioning or linking to Linux/macOS equivalents. All example links and further reading are Windows-focused, and there are no Linux/macOS-specific instructions, examples, or troubleshooting guidance. This creates friction for non-Windows users who may need platform-specific details.
Recommendations
  • Include links to both Windows and Linux/macOS versions of the Azure Instance Metadata Service documentation.
  • Add examples and troubleshooting steps for Linux (e.g., using curl, bash, or other common Linux tools) alongside any Windows/Powershell examples.
  • Ensure parity in error code explanations and mitigation steps for all supported platforms.
  • Clearly indicate when instructions are platform-specific and provide alternatives for other platforms.
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-14 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 deploying IIS on Windows Server VMs, referencing the default IIS Windows Server web page as the verification step, and omitting any mention of Linux-based deployment or verification (e.g., Apache, Nginx). All examples and screenshots are Windows-centric, with no Linux alternatives or parity in instructions.
Recommendations
  • Provide parallel instructions for deploying and verifying with Linux VMs (e.g., Ubuntu with Apache or Nginx).
  • Include screenshots and verification steps for Linux-based web servers.
  • Mention that the ARM template can be modified for Linux VMs and provide example parameters.
  • Clarify that the tutorial is Windows-centric and link to Linux-focused tutorials if available.
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-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example Powershell Heavy
Summary
The documentation page demonstrates a notable Windows bias in the backend VM creation and configuration steps. Only Windows Server images are used for the virtual machines, and the instructions for installing a web server (IIS) rely exclusively on PowerShell commands via the CustomScriptExtension. There are no examples or guidance for deploying Linux VMs or installing a web server (such as Apache or Nginx) on Linux. This creates friction for users who prefer or require Linux-based workloads.
Recommendations
  • Provide parallel examples for creating Linux VMs (e.g., using Ubuntu or CentOS images) alongside the Windows examples.
  • Include instructions for installing a web server on Linux VMs, such as using the CustomScriptExtension to run bash commands for installing Apache or Nginx.
  • Clearly indicate that both Windows and Linux VMs are supported and provide links to relevant documentation for each OS.
  • When showing code blocks for VM creation and configuration, alternate or combine Windows and Linux examples, or use tabs to allow users to select their preferred OS.
  • Avoid assuming PowerShell as the default scripting language for VM configuration; show bash alternatives where applicable.
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-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation demonstrates a bias toward Windows by exclusively using Windows Server as the VM image in the scale set creation steps, with no mention or example of Linux images. There are no Linux-specific instructions, nor is there guidance for Linux administrators regarding OS selection or configuration. The tutorial assumes Windows as the default, which may create friction for Linux users.
Recommendations
  • Include Linux-based VM image options (e.g., Ubuntu, CentOS) in the scale set creation steps.
  • Provide guidance or examples for both Windows and Linux VM configurations, especially in sections where OS-specific settings may differ.
  • Add a note clarifying that the process is OS-agnostic and works for both Windows and Linux, unless there are exceptions.
  • Show examples of administrator account setup for Linux (e.g., SSH key authentication) alongside Windows password authentication.
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-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation consistently references IIS (a Windows web server) as the default backend for testing, without mentioning Linux alternatives (e.g., Apache, Nginx). All testing instructions assume IIS is present, which is only true for Windows VMs. There are no examples or guidance for deploying or testing with Linux-based backend pools, nor is there any mention of Linux-specific troubleshooting or validation steps. The order of presentation in portal instructions also reflects a Windows-centric approach.
Recommendations
  • Include explicit instructions or examples for deploying Linux VMs with common web servers (e.g., Apache, Nginx) in backend pools.
  • When describing test steps, mention how to verify load balancer functionality with Linux-based web servers (e.g., expected default pages, troubleshooting tips).
  • Provide links to Linux quickstarts or documentation alongside Windows/IIS references.
  • Clarify that backend pools can contain either Windows or Linux VMs, and provide parity in example commands and screenshots.
  • Avoid assuming IIS is the default; use more generic language or provide both Windows and Linux examples.
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-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing only Windows virtual machines in its examples and prerequisites. There are no examples, instructions, or links for deploying or configuring Linux VMs, nor any mention of Linux-specific considerations. This may cause friction for Linux users who need parity in guidance.
Recommendations
  • Include instructions and links for deploying a Linux VM in Azure, such as 'Create a Linux VM in the Azure portal'.
  • Clarify that the steps apply equally to Linux and Windows VMs, or note any differences if applicable.
  • Provide example resource names for both Windows and Linux VMs, or use neutral naming conventions.
  • Add a note or section addressing any Linux-specific networking or outbound connectivity considerations.
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-14 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example Powershell Heavy 🔧 Windows Tools
Summary
The tutorial demonstrates a notable Windows bias: all VM creation examples use Windows Server images exclusively, and the only instructions for configuring the web server (IIS) use Windows-specific PowerShell commands. There are no Linux VM options, nor any guidance for deploying or configuring Linux-based web servers (e.g., Apache, Nginx), nor are Bash or Linux command-line examples provided. This limits the tutorial's usefulness for Linux/macOS users and those deploying cross-platform solutions.
Recommendations
  • Include parallel instructions for creating Linux VMs (e.g., Ubuntu, CentOS) alongside Windows VMs.
  • Provide Linux-specific web server installation steps (e.g., install Apache or Nginx using Bash/SSH commands).
  • Show how to use the Azure portal's Run Command feature for Bash scripts on Linux VMs.
  • Add screenshots and examples for Linux VM configuration and testing.
  • Explicitly mention that both Windows and Linux VMs are supported in backend pools, and provide links to relevant documentation.
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 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 by providing extensive PowerShell examples first, using Windows-centric tools and patterns (e.g., New-AzVMConfig with WindowsServer images), and referencing Windows-specific constructs. Although Azure CLI examples are included and do show Linux VM creation, the PowerShell section is much longer and exclusively Windows-focused, with no Linux or cross-platform PowerShell examples. The CLI section is shorter and appears after the PowerShell section, reinforcing a Windows-first approach.
Recommendations
  • Provide PowerShell examples for Linux VM creation (using Set-AzVMOperatingSystem -Linux and appropriate images).
  • Balance the length and detail of CLI and PowerShell sections, ensuring parity in steps and explanations.
  • Consider presenting CLI examples first or interleaving them with PowerShell to avoid Windows-first ordering.
  • Explicitly mention cross-platform compatibility of Azure CLI and PowerShell, and clarify which commands work on Linux/macOS.
  • Add notes or links for Linux/macOS users regarding prerequisites and environment setup.
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-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Powershell Heavy
Summary
The documentation page demonstrates a Windows bias by referencing the PowerShell cmdlet Get-AzAccessToken as the only example for obtaining a Bearer access token, with no mention of Linux/macOS equivalents or cross-platform CLI alternatives. There are no command-line examples for Linux/macOS users, and the only tool referenced for authentication is a Windows-centric PowerShell module.
Recommendations
  • Provide Azure CLI examples (e.g., 'az account get-access-token') for obtaining Bearer tokens, which work on Windows, Linux, and macOS.
  • Include explicit instructions or links for Linux/macOS users to obtain access tokens.
  • Reference cross-platform tools (such as Azure CLI or REST tools like curl) alongside or before Windows-specific tools.
  • Avoid referencing only PowerShell modules for authentication; always provide a cross-platform alternative.
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 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page for Azure Load Balancer health probes exhibits a moderate Windows bias. The 'Next steps' section specifically highlights a PowerShell-based quickstart for creating a load balancer, without mentioning equivalent Linux/macOS CLI or Bash examples. There are no explicit Linux or cross-platform command-line instructions, and PowerShell is referenced before other tools. The rest of the content is generally platform-neutral, focusing on concepts and configuration properties.
Recommendations
  • Add equivalent Azure CLI (az) or Bash examples for managing health probes and creating load balancers, especially in the 'Next steps' section.
  • Provide links to Linux/macOS-specific documentation or tutorials alongside PowerShell resources.
  • Ensure that platform-specific instructions (e.g., PowerShell) are presented alongside or after cross-platform options, not before.
  • Explicitly state that all configuration steps can be performed using Azure CLI, REST API, or portal, not just PowerShell.
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-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation demonstrates a Windows bias by exclusively using Windows Server as the VM image in the scale set creation steps. There are no examples or instructions for deploying Linux-based VM scale sets, nor is there mention of Linux-specific considerations. All steps are portal-based, so no PowerShell or CLI bias is present, but the choice of Windows as the default image and lack of Linux parity is notable.
Recommendations
  • Include instructions or screenshots for creating a VM scale set using a popular Linux image (e.g., Ubuntu, CentOS) alongside the Windows example.
  • Add a note clarifying that the process is identical for Linux VMs, or highlight any differences (e.g., SSH key setup vs. password).
  • Provide guidance on administrator account setup for Linux (e.g., SSH public key authentication).
  • Ensure that backend pool health probes and load balancing rules are described in a way that applies to both Windows and Linux workloads.
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-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation provides detailed instructions for moving Azure Load Balancers using the Azure portal and Azure PowerShell, with all CLI examples and scripting focused exclusively on PowerShell. There are no references to cross-platform tools such as Azure CLI, nor are there any bash or Linux/macOS shell examples. Additionally, some instructions (e.g., editing exported templates) reference Windows-specific tools like Notepad.exe. This creates friction for Linux/macOS users, who must adapt PowerShell commands or use alternative tooling not mentioned in the documentation.
Recommendations
  • Add equivalent instructions and examples using Azure CLI (az), which is cross-platform and widely used on Linux/macOS.
  • Provide bash shell examples for template editing and deployment, including use of editors like nano, vim, or VS Code.
  • Explicitly state that PowerShell Core is available cross-platform, but also offer guidance for users who prefer bash/zsh.
  • Avoid referencing Windows-only tools (e.g., notepad.exe); suggest platform-neutral editors or provide alternatives.
  • Include a section or tab for Linux/macOS workflows, ensuring parity in prerequisites, commands, and troubleshooting.
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-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates notable Windows bias. The PowerShell section is extensive and exclusively uses Windows-centric tooling and VM images. All VM creation examples (both PowerShell and Azure CLI) use Windows Server images, with no mention of Linux alternatives. RDP (a Windows protocol) is used for remote access, with no SSH or Linux access examples. The PowerShell section is presented first and in much greater detail than the Azure CLI or ARM template sections. There are no Linux-specific instructions, troubleshooting, or parity examples.
Recommendations
  • Include Linux VM deployment examples (e.g., Ubuntu, CentOS) alongside Windows Server in both PowerShell and Azure CLI sections.
  • Provide SSH-based remote access instructions for Linux VMs, including network security group rules for port 22.
  • Add notes or tabs for Linux/macOS users, clarifying how to run Azure CLI commands on those platforms.
  • Balance the example order so that Azure CLI and ARM template instructions are not secondary to PowerShell.
  • Avoid exclusive use of Windows-specific protocols (RDP) and tools; offer alternatives for Linux.
  • Explicitly mention cross-platform compatibility for scripts and commands.
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-13 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 testing examples use Windows Server as the OS. There are no Linux VM examples, nor instructions for Linux-specific connectivity testing (e.g., using curl or a Linux browser). The documentation implicitly assumes Windows by specifying Windows Server 2022 and Microsoft Edge for browser-based connectivity tests, without mentioning Linux alternatives or providing parity for Linux users.
Recommendations
  • Include parallel instructions for creating a Linux VM (e.g., Ubuntu) in the 'Create virtual machine' section, with appropriate settings for SSH authentication.
  • Provide Linux-specific connectivity test steps, such as using curl or Firefox/Chromium to verify outbound connectivity.
  • Mention that the process is OS-agnostic and provide notes or links for Linux/macOS users where steps differ (e.g., connecting via Bastion with SSH instead of RDP).
  • Add screenshots or CLI/portal steps showing Linux VM configuration and connectivity testing.
  • Clarify that the load balancer configuration applies to both Windows and Linux VMs.
GitHub Create Pull Request
Load Balancer Deploy an IPv6 dual stack application using Standard Internal Load Balancer in Azure - PowerShell ...-dual-stack-standard-internal-load-balancer-powershell.md
Medium Priority View Details →
Scanned: 2026-01-13 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. All examples use Azure PowerShell cmdlets, with no mention of Azure CLI, Bash, or Linux/macOS workflows. The VM creation steps exclusively use Windows Server images, and there are no instructions for deploying Linux VMs or using Linux-native tools. This creates friction for Linux/macOS users and may prevent them from following the guide without significant adaptation.
Recommendations
  • Provide equivalent Azure CLI (az) examples alongside PowerShell for all resource creation steps.
  • Include instructions and examples for deploying Linux VMs (e.g., Ubuntu, CentOS) in addition to Windows Server.
  • Mention and demonstrate usage from Bash or Cloud Shell (Bash) environments, not just PowerShell.
  • Clarify which steps are platform-agnostic and which are Windows-specific, and provide Linux/macOS alternatives where needed.
  • Add notes or links to Linux/macOS documentation for installing and using Azure CLI.
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-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Missing Linux Example Windows First
Summary
The documentation does not provide any OS-specific examples or tooling, but it implicitly favors Windows by omitting references to Linux/macOS workflows, tools, or remote access patterns. All examples and tutorials referenced are portal-based, with no mention of command-line approaches (such as Azure CLI, PowerShell, or SSH), nor any guidance for Linux users on connecting to VMs via NAT rules.
Recommendations
  • Add explicit examples for both Windows (RDP) and Linux (SSH) scenarios, showing how inbound NAT rules enable remote access.
  • Include command-line instructions using Azure CLI and PowerShell, ensuring both Windows and Linux users are covered.
  • Reference Linux/macOS tools (e.g., SSH clients) alongside Windows tools (e.g., Remote Desktop), and clarify any OS-specific configuration steps.
  • Ensure tutorials and screenshots demonstrate parity between Windows and Linux workflows.
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-13 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 is heavily focused on Azure PowerShell, with all examples and instructions using PowerShell cmdlets. There are no references to Linux/macOS command-line tools, nor are Azure CLI or ARM template alternatives provided. The prerequisites and workflow assume a Windows-centric environment, which may create friction for Linux/macOS users who typically use Bash and Azure CLI.
Recommendations
  • Provide equivalent Azure CLI examples for each PowerShell command.
  • Include notes on how to perform these tasks using Bash on Linux/macOS.
  • Add links to ARM template or REST API documentation for users who prefer declarative or cross-platform approaches.
  • Clarify that Azure PowerShell is available on Linux/macOS, but highlight Azure CLI as the default cross-platform tool.
  • Reorder or parallelize examples so that Linux/macOS approaches are shown alongside or before Windows/PowerShell examples.
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-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by recommending automated PowerShell scripts as the primary upgrade method, without mentioning or providing equivalent CLI/bash examples for Linux/macOS users. The only automation guidance links to PowerShell, and there is no reference to Azure CLI or Bash scripting. This creates friction for users on non-Windows platforms, as they must manually adapt instructions or seek alternative tooling.
Recommendations
  • Provide equivalent Azure CLI or Bash script examples for all PowerShell automation steps.
  • Explicitly mention cross-platform options (e.g., Azure CLI, REST API) alongside PowerShell.
  • Reorder or parallelize instructions so that Linux/macOS-friendly methods are presented equally or first.
  • Add notes clarifying platform compatibility for each automation method.
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-13 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 distribution mode using three methods: Azure Portal, PowerShell, and Azure CLI. PowerShell is given a dedicated section, and the CLI section does not explicitly mention Linux or macOS usage, nor does it provide bash-specific guidance or examples. The 'Next steps' section links to a PowerShell-specific quickstart, reinforcing a Windows-centric approach. There are no explicit Linux/macOS examples or references to platform-specific considerations.
Recommendations
  • Add explicit bash/Linux/macOS examples for Azure CLI usage, including shell environment setup and command execution.
  • Clarify that Azure CLI commands work cross-platform and provide any necessary notes for Linux/macOS users (e.g., installation, authentication).
  • Include links to Linux/macOS quickstart guides in the 'Next steps' section.
  • Balance PowerShell and CLI coverage by mentioning cross-platform scripting options (e.g., bash, zsh) and their usage with Azure CLI.
GitHub Create Pull Request
← Previous Page 10 of 16 Next →