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 26-50 of 388 flagged pages
Load Balancer Configure load balancer TCP reset and idle timeout ...ticles/load-balancer/load-balancer-tcp-idle-timeout.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation provides step-by-step instructions for configuring TCP reset and idle timeout in Azure Load Balancer using the Azure Portal (which is platform-agnostic but often associated with Windows environments), PowerShell (Windows-centric), and Azure CLI (cross-platform). The PowerShell example is detailed and includes installation and usage instructions, which are specific to Windows environments. There is a slight bias towards Windows tools, as PowerShell is featured prominently and its prerequisites are discussed in detail, whereas Linux-specific guidance (such as Bash or shell scripting) is not mentioned. The Azure CLI section is cross-platform but does not explicitly address Linux usage or provide Linux-specific context.
Recommendations
  • Add explicit Linux/Bash examples for Azure CLI usage, including installation and environment setup instructions for Linux.
  • Clarify that Azure CLI commands can be run on Linux, macOS, and Windows, and provide links to installation guides for each OS.
  • Include troubleshooting or environment validation steps for Linux users, such as checking CLI dependencies or permissions.
  • Balance the PowerShell section with equivalent Bash or shell script examples for users who prefer Linux environments.
  • Consider adding a note that PowerShell Core is available on Linux and macOS, and provide installation instructions if relevant.
GitHub Create Pull Request
Load Balancer Troubleshoot common problems with Azure Load Balancer ...n/articles/load-balancer/load-balancer-troubleshoot.md
High Priority View Details →
Scanned: 2026-01-11 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 a Windows bias by exclusively referencing Windows-specific troubleshooting tools and commands (e.g., PsPing, Netsh trace) without providing equivalent Linux examples or alternatives. All diagnostic instructions assume a Windows environment, and there is no mention of Linux tools or commands for network capture or connectivity testing. This may hinder Linux users from effectively following the guidance.
Recommendations
  • Include Linux equivalents for all troubleshooting steps, such as using 'ping', 'nc' (netcat), 'ss', or 'tcpdump' for network testing and capture.
  • Provide example commands for both Windows and Linux environments side-by-side.
  • Explicitly mention that the instructions apply to both Windows and Linux VMs, or clarify when a step is OS-specific.
  • Reference cross-platform tools or Azure-native diagnostics where possible.
  • Avoid assuming the use of Windows-only utilities unless necessary, and always offer Linux alternatives.
GitHub Create Pull Request
Load Balancer Manage inbound NAT rules for Azure Load Balancer ...ain/articles/load-balancer/manage-inbound-nat-rules.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation demonstrates a moderate Windows bias: PowerShell is featured as a primary automation example alongside the Azure portal and CLI, with detailed step-by-step instructions and code samples. PowerShell is a Windows-centric tool, and its inclusion (and prominence) may disadvantage Linux users, who typically use Bash or other shells. The prerequisites and instructions reference PowerShell-specific setup and commands before CLI equivalents, and there is no mention of Bash, Linux shell, or cross-platform scripting alternatives. The CLI examples are present and useful for Linux users, but the overall structure and language favor Windows/PowerShell users.
Recommendations
  • Add explicit Bash examples for each CLI scenario, showing how commands would be run in a Linux shell (including environment setup, authentication, and variable usage).
  • Clarify that Azure CLI is cross-platform and can be used on Windows, Linux, and macOS, and provide links or notes for installing CLI on Linux systems.
  • Balance the order of examples: alternate or randomize the order of PowerShell and CLI sections, or lead with CLI in some cases to avoid Windows-first impression.
  • Include a short section in prerequisites for Linux users, e.g., how to install Azure CLI on Ubuntu, authentication steps, and any Linux-specific considerations.
  • Avoid language that implies PowerShell is the default or preferred automation tool; explicitly state that both CLI and PowerShell are supported and cross-platform users should choose based on their environment.
GitHub Create Pull Request
Load Balancer Tutorial: Create a load balancer with more than one availability set in the backend pool - Azure portal ...ad-balancer/tutorial-multi-availability-sets-portal.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example Powershell Heavy 🔧 Windows Tools
Summary
The documentation page demonstrates a strong Windows bias. All virtual machine creation steps specify 'Windows Server 2022 Datacenter' as the image, with no mention of Linux alternatives. The IIS installation and configuration are performed exclusively via Windows PowerShell commands, with no Linux equivalent (such as Apache or Nginx) provided. There are no examples or instructions for deploying Linux VMs, nor for installing or testing a web server on Linux. The use of Windows tools and patterns (IIS, PowerShell, Windows Server) is exclusive throughout the tutorial.
Recommendations
  • Provide parallel instructions for creating Linux-based virtual machines (e.g., Ubuntu, CentOS) alongside Windows examples.
  • Include steps for installing and configuring a web server on Linux VMs (e.g., Apache or Nginx), using Bash or the Azure portal's Run Command for Linux.
  • Offer both PowerShell and Bash/CLI examples for remote command execution and configuration.
  • Explicitly mention that the load balancer works with both Windows and Linux VMs, and show how to mix or choose between them.
  • Add screenshots and code snippets demonstrating Linux VM setup and web server testing.
GitHub Create Pull Request
Load Balancer Tutorial: Create Inbound NAT rule V2 - Azure portal ...ad-balancer/tutorial-nat-rule-multi-instance-portal.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation demonstrates a subtle Windows bias in several areas. In the 'Install web server' section, users are instructed to open a PowerShell prompt if on Windows, but a Bash prompt if on Mac or Linux. However, the SSH command examples use Windows-style paths (e.g., .\Downloads\myKey.pem) and do not provide Linux/Mac equivalents (e.g., ~/Downloads/myKey.pem). There are no explicit Linux command examples for SSH, and the instructions consistently mention Windows tools and patterns first or exclusively. This may cause confusion for Linux users and suggests a prioritization of Windows environments.
Recommendations
  • Provide both Windows (PowerShell/CMD) and Linux/Mac (Bash) command examples side-by-side, especially for SSH commands and file paths.
  • When referencing prompts, mention Bash first or equally with PowerShell to avoid Windows-first ordering.
  • Include notes or tips for Linux/Mac users regarding file path conventions and command syntax differences.
  • Ensure that all instructions and screenshots are platform-agnostic or offer alternatives for both Windows and Linux/Mac users.
GitHub Create Pull Request
Load Balancer Quickstart: Create an internal load balancer - Azure CLI ...ncer/quickstart-load-balancer-standard-internal-cli.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation demonstrates a strong Windows bias: all VM creation examples use Windows images (win2022datacenter, Win2019Datacenter), IIS installation is performed via PowerShell commands, and the test instructions reference Internet Explorer. There are no examples for Linux VM images, nor instructions for installing or testing with Linux tools (e.g., Apache, curl, SSH). Windows-specific tools and patterns are mentioned exclusively, with no Linux equivalents provided.
Recommendations
  • Provide parallel examples for creating Linux VMs (e.g., using Ubuntu or CentOS images) alongside Windows examples.
  • Include instructions for installing and configuring a web server on Linux VMs (e.g., Apache or Nginx) using bash commands.
  • Offer test steps for Linux VMs, such as using curl or a browser like Firefox, and SSH access via Bastion.
  • Avoid referencing Windows-only tools (e.g., Internet Explorer, PowerShell) without Linux alternatives.
  • Clearly indicate that both Windows and Linux VMs are supported and provide guidance for both platforms throughout the documentation.
GitHub Create Pull Request
Load Balancer Quickstart: Create an internal load balancer - ARM template ...ttps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/quickstart-load-balancer-standard-internal-template.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias. Azure PowerShell (a Windows-centric tool) is mentioned first in the deployment section, with explicit instructions and code samples. PowerShell examples are provided alongside Azure CLI, but PowerShell is referenced as the primary method in some sections. The cleanup section also uses PowerShell commands, and the overall flow assumes familiarity with Windows tools and patterns. There are no explicit Linux shell examples (e.g., bash scripts), nor is there mention of Linux-specific considerations or parity.
Recommendations
  • Present Azure CLI (cross-platform) instructions before PowerShell, or give equal prominence to both.
  • Add explicit bash shell examples and instructions for Linux/macOS users.
  • Clarify that Azure CLI works natively on Linux/macOS and Windows, while PowerShell may require installation on non-Windows platforms.
  • Avoid language that implies PowerShell is the default or preferred method.
  • Include links or notes about using the Azure portal, REST API, or ARM templates from Linux environments.
  • Ensure screenshots and diagrams do not show Windows-only interfaces unless alternatives are also shown.
GitHub Create Pull Request
Load Balancer Quickstart: Create an internal load balancer - Azure portal ...r/quickstart-load-balancer-standard-internal-portal.md
High Priority View Details →
Scanned: 2026-01-11 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 clear Windows bias. The VM creation instructions specify Windows Server as the image, and all configuration and testing steps (such as IIS installation and web page setup) use Windows PowerShell commands. There are no Linux VM examples, nor are there instructions for installing or configuring a web server on Linux. The use of Windows-specific tools (PowerShell, IIS, Windows Administrative Tools) is exclusive, and Linux alternatives are not mentioned.
Recommendations
  • Provide parallel instructions for creating and configuring Linux VMs (e.g., Ubuntu or CentOS) alongside the Windows example.
  • Include Linux-specific steps for installing a web server (such as Apache or Nginx) and customizing the index.html file.
  • Offer Bash shell commands for Linux VM setup, similar to the PowerShell commands given for Windows.
  • Mention Linux tools and patterns (e.g., SSH, apt/yum, systemctl) where appropriate.
  • Ensure screenshots and walkthroughs include both Windows and Linux scenarios, or clarify that the steps apply to both platforms if possible.
GitHub Create Pull Request
Load Balancer Quickstart: Create a public load balancer - Bicep ...ncer/quickstart-load-balancer-standard-public-bicep.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates bias toward Windows environments by exclusively referencing Windows-centric technologies (such as IIS), omitting Linux alternatives, and providing examples for Azure CLI and PowerShell without explicit Linux shell guidance. The web server deployed is IIS, which is Windows-specific, and there is no mention of deploying a Linux-based web server or instructions for Linux users. PowerShell is presented as an equal alternative to Azure CLI, but no Bash or Linux-specific instructions are provided.
Recommendations
  • Include Linux-based deployment examples, such as using Apache or Nginx web servers on the VMs.
  • Add explicit Bash shell instructions for deploying the Bicep file, clarifying cross-platform usage of Azure CLI.
  • Provide guidance for Linux users on connecting to VMs (e.g., SSH instructions) and managing resources.
  • Present both Windows and Linux options for VM extensions and configuration, ensuring parity in documentation.
  • Avoid defaulting to Windows tools and technologies (such as IIS) without mentioning Linux equivalents.
GitHub Create Pull Request
Load Balancer Quickstart: Create a public load balancer - Azure CLI ...lancer/quickstart-load-balancer-standard-public-cli.md
High Priority View Details →
Scanned: 2026-01-11 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-based virtual machines (win2019datacenter) and provides only Windows-specific configuration commands (using PowerShell for IIS installation). There are no examples or instructions for deploying Linux VMs or configuring a Linux-based web server, and the only VM extension example is for Windows/IIS via PowerShell.
Recommendations
  • Provide parallel examples for deploying Linux VMs (e.g., using Ubuntu or CentOS images) alongside Windows examples.
  • Include instructions and az vm extension set examples for installing a web server on Linux VMs (e.g., Apache or Nginx) using bash commands.
  • Clearly indicate in each step whether the instructions apply to Windows, Linux, or both, and avoid assuming Windows as the default.
  • Add a section or note explaining how to adapt the quickstart for Linux environments, including differences in VM images, extensions, and configuration scripts.
  • Ensure that both Windows and Linux users can follow the quickstart without needing to infer missing steps for their platform.
GitHub Create Pull Request
Load Balancer Quickstart: Create a public load balancer - ARM template ...r/quickstart-load-balancer-standard-public-template.md
High Priority View Details →
Scanned: 2026-01-11 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 bias towards Windows by providing only Azure PowerShell deployment instructions, referencing Windows-centric tools (PowerShell, IIS), and omitting Linux/CLI examples. The deployment walkthrough is exclusively PowerShell-based, and the web server used for demonstration is IIS, which is Windows-specific. There is no mention or example of using Azure CLI, Bash, or Linux-based web servers, nor are Linux deployment patterns shown alongside or before Windows ones.
Recommendations
  • Add equivalent Azure CLI (az) deployment instructions and code blocks, suitable for Bash and Linux environments.
  • Include examples of deploying and testing with a Linux-based web server (e.g., Apache or Nginx) in addition to IIS.
  • Present both PowerShell and CLI/Bash examples side-by-side, or offer a choice at the start of the deployment section.
  • Explicitly mention cross-platform compatibility and provide links to Linux-focused quickstarts or tutorials.
  • Ensure screenshots and output examples include both PowerShell and CLI results where applicable.
GitHub Create Pull Request
Load Balancer Quickstart: Create a public load balancer - Azure portal ...cer/quickstart-load-balancer-standard-public-portal.md
High Priority View Details →
Scanned: 2026-01-11 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 page demonstrates a clear Windows bias in the VM configuration section. Only Windows VM instructions are provided, specifically using Windows PowerShell to install IIS. No Linux VM example, nor equivalent Linux commands (e.g., for Apache or Nginx), are mentioned. The workflow assumes Windows as the default, both in tool choice and step order.
Recommendations
  • Add parallel instructions for configuring Linux VMs, including SSH access and commands to install a web server (e.g., Apache or Nginx).
  • Provide Linux shell command examples alongside PowerShell, ensuring both platforms are equally represented.
  • Explicitly mention that both Windows and Linux VMs are supported and link to relevant documentation for each.
  • Avoid assuming Windows as the default; present both options or let users choose their preferred OS early in the workflow.
  • Include screenshots or terminal outputs for Linux steps to match the visual guidance given for Windows.
GitHub Create Pull Request
Load Balancer Tutorial: Create an Azure Global Load Balancer ...articles/load-balancer/tutorial-cross-region-portal.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates Windows bias by exclusively referencing Windows-centric tools and patterns, such as IIS web server for backend pool testing and PowerShell for scripting. There are no explicit Linux examples for backend pool configuration or testing (e.g., Apache/Nginx), and instructions for stopping VMs and verifying load balancer failover are described in terms of IIS and Windows workflows. The documentation mentions Azure PowerShell and Windows-based resource group names before or alongside CLI, but does not provide parity for Linux users in terms of backend configuration or testing.
Recommendations
  • Include Linux-based backend pool examples, such as deploying Apache or Nginx web servers on Linux VMs, and provide screenshots or expected output for those scenarios.
  • Add instructions for stopping Linux VMs (e.g., using SSH and systemctl or service commands) and verifying failover with Linux-based web servers.
  • Reference both Windows and Linux tools equally in prerequisites and testing sections, ensuring that Linux users have clear, step-by-step guidance.
  • Clarify that Azure CLI is cross-platform and provide shell-agnostic command examples (e.g., bash, zsh) where appropriate.
  • Avoid assuming IIS as the default backend and mention alternatives for Linux environments.
GitHub Create Pull Request
Load Balancer Move an Azure Load Balancer to another Azure region ...ad-balancer/move-across-regions-azure-load-balancer.md
High Priority View Details →
Scanned: 2026-01-11 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 between regions using the Azure portal and Azure PowerShell. All command-line examples use PowerShell cmdlets, and references to command-line editors (e.g., notepad.exe) and tools are Windows-centric. There are no examples or guidance for Linux users (e.g., Azure CLI, bash, or Linux-native editors). The structure and order of examples prioritize Windows tools and workflows, potentially excluding or inconveniencing Linux users.
Recommendations
  • Add equivalent Azure CLI (az) examples for all PowerShell commands, showing how to perform each step on Linux/macOS.
  • Replace or supplement references to Windows-only tools (e.g., notepad.exe) with cross-platform alternatives (e.g., vim, nano, code, or generic 'text editor').
  • Explicitly mention that all steps can be performed on Linux/macOS, and provide any necessary platform-specific notes.
  • Ensure that instructions for obtaining resource IDs, editing JSON files, and deploying templates include both PowerShell and Azure CLI workflows.
  • Consider reordering or parallelizing instructions so that Linux and Windows approaches are presented side-by-side, rather than Windows-first.
GitHub Create Pull Request
Load Balancer Troubleshoot Azure Load Balancer health probe status ...ncer/load-balancer-troubleshoot-health-probe-status.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by primarily referencing Windows tools (PsPing, TCPing, netsh, netstat -an), providing command examples for Windows before Linux, and omitting equivalent Linux troubleshooting tools and detailed Linux command examples. Linux commands are mentioned only briefly and without the same depth or context as their Windows counterparts.
Recommendations
  • Include Linux-native troubleshooting tools and examples, such as 'ss', 'nc', or 'telnet' for port checks, and 'iptables' or 'firewalld' for firewall checks.
  • Provide step-by-step Linux command examples alongside Windows commands, ensuring parity in detail and clarity.
  • Mention Linux alternatives to PsPing and TCPing, such as 'nmap', 'hping3', or 'tcping' for Linux (if available), and provide usage examples.
  • Ensure that instructions for network trace collection include Linux methods, such as using 'tcpdump' or 'wireshark'.
  • Balance the order of presentation so that Linux and Windows instructions are given equal prominence, or group them together for each troubleshooting step.
GitHub Create Pull Request
Load Balancer Configure Azure Load Balancer distribution mode ...icles/load-balancer/load-balancer-distribution-mode.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page displays a moderate Windows bias. PowerShell is given a dedicated tab and example, and the 'Next steps' section links to a PowerShell-specific quickstart. The CLI example is present, but there is no explicit mention of Linux, nor are there any Linux-specific instructions, troubleshooting notes, or examples. The ordering places PowerShell before CLI, which may subtly prioritize Windows workflows. There are no references to Linux tools or shell environments.
Recommendations
  • Add explicit Linux/Bash examples for Azure CLI usage, including environment setup and command execution in a Linux shell.
  • Include troubleshooting notes or tips for Linux users (e.g., differences in CLI behavior, authentication, or file paths).
  • Balance tab ordering by placing CLI before PowerShell or clarifying that CLI is cross-platform.
  • Add links to Linux-focused quickstarts or documentation in the 'Next steps' section.
  • Clarify that Azure CLI commands work on Windows, Linux, and macOS, and provide context for users on different platforms.
GitHub Create Pull Request
Load Balancer What's new in Azure Load Balancer ...ure-docs/blob/main/articles/load-balancer/whats-new.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page exhibits subtle Windows bias. The only explicit example link for creating a dual stack application points to a PowerShell-based guide, which is Windows-centric. There are no equivalent Linux or cross-platform CLI examples referenced, nor are Linux tools or patterns mentioned. The documentation does not provide parity for Linux users in terms of example commands or guidance, and Windows/PowerShell is implicitly prioritized.
Recommendations
  • Add equivalent Linux examples using Azure CLI and/or Bash scripts alongside PowerShell examples.
  • Reference cross-platform tools (e.g., Azure CLI) before or alongside Windows-specific tools.
  • Ensure links to how-to guides (such as creating dual stack applications) include both PowerShell and Azure CLI/Bash options.
  • Explicitly mention platform-agnostic approaches and clarify when instructions are Windows-specific.
  • Review all referenced guides for parity in Linux and cross-platform documentation.
GitHub Create Pull Request
Load Balancer Deploy a global load balancer with Azure Resource Manager templates | Microsoft Docs ...ttps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/tutorial-deploy-cross-region-load-balancer-template.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation demonstrates Windows bias by exclusively deploying IIS (Internet Information Server) on Windows Server virtual machines, with no mention or example of Linux-based alternatives (e.g., Apache, Nginx). The verification step references the default IIS Windows Server web page, and there are no instructions or screenshots for Linux VM deployments. Windows terminology and tools (IIS, Windows Server) are used throughout, while Linux equivalents are absent.
Recommendations
  • Provide parallel examples for deploying Linux-based web servers (e.g., Apache, Nginx) in the ARM template and walkthrough.
  • Include screenshots and verification steps for accessing a default Linux web server page.
  • Mention Linux VM options in the template review and deployment steps.
  • Clarify that both Windows and Linux VMs are supported, and link to relevant documentation for Linux deployments.
  • Avoid using Windows-specific terminology (e.g., IIS) as the sole example; present both Windows and Linux options equally.
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
High Priority View Details →
Scanned: 2026-01-11 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 strong Windows bias, especially in the VM creation and configuration steps. Only Windows Server images are used for virtual machines, and IIS installation is performed exclusively via Windows PowerShell commands. There are no Linux VM options, nor are there instructions for deploying or configuring a Linux-based web server (e.g., Apache or Nginx). All examples and screenshots focus on Windows tools and workflows, with no mention of Linux equivalents.
Recommendations
  • Include parallel instructions for deploying Linux VMs (e.g., Ubuntu) in the backend pool.
  • Provide Linux-specific steps for installing and configuring a web server (e.g., Apache or Nginx) using Bash or cloud-init scripts.
  • Offer both Windows and Linux command examples for server setup, and clarify that either OS can be used.
  • Add screenshots and portal instructions relevant to Linux VM creation and configuration.
  • Explicitly state that the load balancer and DDoS protection work with both Windows and Linux workloads.
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
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exclusively uses Azure PowerShell commands and tools, with no mention or examples of Azure CLI, Bash, or Linux-native workflows. All code samples, prerequisites, and instructions are centered around PowerShell, which is traditionally a Windows-centric tool, though it is available cross-platform. There is no guidance for users who prefer Linux environments or command-line interfaces other than PowerShell.
Recommendations
  • Add equivalent Azure CLI (az) examples for each PowerShell command, showing how to perform the same tasks in Bash or other shell environments.
  • Include a section or note at the beginning clarifying cross-platform options and linking to Linux/Bash/CLI documentation.
  • Ensure prerequisites mention both PowerShell and Azure CLI, and provide installation/usage instructions for both.
  • Where possible, use neutral language (e.g., 'using Azure PowerShell or Azure CLI') and avoid implying PowerShell is the only or preferred method.
  • Provide links to Linux-focused quickstarts and tutorials for Azure networking tasks.
GitHub Create Pull Request
Load Balancer Azure Load Balancer concepts ...zure-docs/blob/main/articles/load-balancer/concepts.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates Windows bias primarily in the 'Next steps' section, where the quickstart example references creating VMs with a custom IIS extension installed—a Windows-centric technology—without mentioning Linux alternatives (such as Apache or Nginx). No Linux-specific examples, tools, or patterns are provided, and Windows tools (IIS) are referenced exclusively. The main content does not provide platform-specific examples, but the guidance for getting started is Windows-first and omits Linux parity.
Recommendations
  • Include Linux-based examples in the quickstart, such as deploying VMs with Apache or Nginx and load balancing a web app between them.
  • Mention both Windows and Linux options when discussing backend pool VM configuration and application scenarios.
  • Provide links to Linux-specific guides or tutorials for Azure Load Balancer.
  • Avoid referencing only Windows tools (IIS) and ensure that equivalent Linux tools are presented with equal prominence.
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
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a bias toward Windows by exclusively providing examples for deploying Windows Server VMs, using RDP for remote access, and omitting Linux VM deployment and SSH access instructions. All VM creation commands specify Windows images, and network security group rules focus on RDP (port 3389), which is specific to Windows. There are no examples or guidance for deploying Linux VMs or configuring SSH (port 22) access, nor are Linux-specific tools or patterns mentioned.
Recommendations
  • Add parallel examples for deploying Linux VMs (e.g., using Ubuntu or other popular distributions) in both Azure CLI and PowerShell sections.
  • Include instructions for configuring SSH access (port 22) in network security group rules, alongside or instead of RDP.
  • Show how to retrieve SSH public IP addresses for Linux VMs, similar to the RDP examples.
  • Mention Linux images in VM creation steps, and provide sample commands for both Windows and Linux.
  • Clarify that the steps apply to both Windows and Linux, or provide tabs/sections for each OS where relevant.
  • Avoid assuming RDP is the default remote access method; reference SSH as the standard for Linux.
GitHub Create Pull Request
Load Balancer Move an Azure Load Balancer to another Azure region ...ad-balancer/move-across-regions-azure-load-balancer.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation provides detailed instructions for moving Azure Load Balancers between regions using the Azure portal and Azure PowerShell. All command-line examples and automation are exclusively shown using Azure PowerShell, with no mention of Azure CLI or Bash scripting, which are cross-platform and preferred on Linux/macOS. Additionally, text editors referenced (e.g., notepad.exe) and command-line workflows (e.g., PowerShell cmdlets) are Windows-centric. There are no Linux-specific instructions, nor is Azure CLI presented as an alternative. The structure and ordering also present Windows/PowerShell methods before any mention of alternatives, reinforcing a Windows-first approach.
Recommendations
  • Add equivalent Azure CLI examples for all PowerShell commands, showing how to perform the same resource export, template editing, and deployment steps using az commands.
  • Reference cross-platform text editors (e.g., nano, vim, VS Code) instead of or alongside notepad.exe.
  • Explicitly state that all steps can be performed on Linux/macOS using Azure CLI and compatible editors.
  • Where possible, provide Bash script snippets for automation, especially for template manipulation and deployment.
  • Reorder sections to present cross-platform methods (Azure CLI, portal) before Windows-specific PowerShell instructions, or provide parallel tabs for CLI and PowerShell.
  • Include notes or callouts for Linux/macOS users, highlighting any differences or additional steps required.
GitHub Create Pull Request
Load Balancer Quickstart: Create a public load balancer - ARM template ...r/quickstart-load-balancer-standard-public-template.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a bias toward Windows environments by providing only Azure PowerShell examples for deploying the ARM template, with no equivalent Azure CLI (bash) or Linux shell instructions. The deployment walkthrough is written with PowerShell syntax and terminology, and references to other deployment methods (Azure CLI, REST API) are mentioned only after the PowerShell example, not in parallel or with examples. There are no Linux-specific instructions or examples, and the web server used for demonstration is IIS, which is Windows-centric.
Recommendations
  • Add equivalent Azure CLI (bash) deployment instructions alongside the PowerShell example, including parameter prompts and resource creation steps.
  • Present both PowerShell and CLI examples in parallel, or offer a tabbed interface for users to select their preferred environment.
  • Include notes or links for Linux users on how to access Azure Cloud Shell (bash) and run the deployment.
  • Provide an example using a Linux-based web server (such as Apache or Nginx) in addition to IIS, or clarify how to modify the template for Linux VMs.
  • Ensure references to deployment methods (PowerShell, CLI, portal, REST API) are presented with equal prominence and example coverage.
GitHub Create Pull Request
Load Balancer Tutorial: Create Inbound NAT rule V2 - Azure portal ...ad-balancer/tutorial-nat-rule-multi-instance-portal.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation demonstrates a Windows bias in several ways. When instructing users to SSH into VMs, it mentions Windows/PowerShell before Linux/Bash, and the SSH command examples use Windows path syntax (e.g., .\Downloads\myKey.pem) without providing a Linux equivalent. There are no explicit Linux command examples for SSH, and the instructions for opening a prompt prioritize Windows. This can make the tutorial less accessible or clear for Linux users.
Recommendations
  • Provide both Windows (PowerShell/CMD) and Linux (Bash) command examples for SSH, including correct path syntax for each platform.
  • When mentioning how to open a terminal, list Linux/Bash first or equally with Windows/PowerShell.
  • Add notes or tips for Linux users regarding file paths and permissions (e.g., chmod 600 myKey.pem).
  • Ensure all command examples are cross-platform or provide alternatives for each OS.
  • Consider including screenshots or instructions for both Windows and Linux environments where relevant.
GitHub Create Pull Request
← Previous Page 2 of 16 Next →