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 301-325 of 388 flagged pages
Load Balancer https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/manage-admin-state-how-to.md ...in/articles/load-balancer/manage-admin-state-how-to.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation consistently references and links to Windows-based virtual machine creation guides in all prerequisites sections, omitting any mention or links to Linux VM equivalents. All example resource links for VM creation are Windows-specific, which may imply Windows is the default or preferred platform. There are no Linux-specific instructions, examples, or parity links for users who may be managing Linux backend pool instances.
Recommendations
  • Add parallel links and instructions for creating Linux virtual machines in the prerequisites sections, e.g., reference /azure/virtual-machines/linux/quick-create-portal, /quick-create-powershell, and /quick-create-cli.
  • Clarify that the admin state feature and all Azure CLI/PowerShell commands are equally applicable to Linux backend pool instances.
  • Include example resource names and scenarios that reference Linux VMs, not just Windows.
  • Where possible, provide notes or guidance for Linux users, especially regarding differences in VM management or network configuration.
  • Review all cross-references and ensure Linux documentation is linked wherever Windows documentation is referenced.
GitHub Create Pull Request
Load Balancer https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/monitor-load-balancer.md ...b/main/articles/load-balancer/monitor-load-balancer.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation presents PowerShell (Windows-centric) examples before Azure CLI (cross-platform) examples when describing how to create diagnostic settings for Azure Load Balancer. The PowerShell section is more detailed, with multiple scenarios (Log Analytics, Storage Account, Event Hub) and step-by-step variable assignments, while the Azure CLI section, though present, is listed after PowerShell. There are no Linux-specific shell examples (e.g., bash scripts), nor is there mention of platform-specific considerations for Linux users. The documentation implicitly prioritizes Windows tooling and patterns by leading with PowerShell.
Recommendations
  • Present Azure CLI examples before PowerShell, or interleave them so that each scenario (Log Analytics, Storage, Event Hub) shows both CLI and PowerShell side-by-side.
  • Explicitly state that Azure CLI is cross-platform and suitable for Linux, macOS, and Windows users.
  • Add bash script examples or notes for Linux users, especially for common automation scenarios.
  • Include a brief section or note on platform parity, clarifying that all operations can be performed from Linux, macOS, or Windows using Azure CLI.
  • Avoid language or ordering that implies PowerShell is the default or preferred method unless there is a technical reason.
GitHub Create Pull Request
Load Balancer https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/troubleshoot-load-balancer-imds.md ...icles/load-balancer/troubleshoot-load-balancer-imds.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates Windows bias by consistently linking to Windows-specific documentation (e.g., '/azure/virtual-machines/windows/instance-metadata-service') and not mentioning Linux equivalents. There are no Linux-specific examples, links, or references, and the guidance on supported HTTP verbs and rate limiting refers only to Windows documentation. This may confuse or exclude users running Azure VMs on Linux.
Recommendations
  • Include parallel links to Linux documentation (e.g., '/azure/virtual-machines/linux/instance-metadata-service') wherever Windows links are present.
  • Add examples or references for retrieving IMDS metadata using Linux tools (such as curl or wget) and shell commands.
  • Clarify that error codes and mitigation steps apply to both Windows and Linux VM environments, or specify any differences.
  • Ensure that troubleshooting steps and sample requests/responses are platform-agnostic or provide both Windows and Linux variants.
GitHub Create Pull Request
Load Balancer https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/tutorial-add-lb-existing-scale-set-portal.md ...-balancer/tutorial-add-lb-existing-scale-set-portal.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The tutorial demonstrates a Windows bias by exclusively using Windows Server as the VM image in the scale set creation steps, with no mention or example of Linux-based images or configuration differences. All instructions and screenshots are tailored to the Azure portal, but the only OS-specific detail is Windows, and there is no guidance for Linux administrators or parity in examples.
Recommendations
  • Include Linux VM image options (e.g., Ubuntu, CentOS) in the scale set creation step, and show how to select them.
  • Add notes or examples highlighting any differences in network configuration or health probe setup for Linux VMs.
  • Provide parity in administrator account setup, mentioning SSH key authentication for Linux VMs.
  • Consider adding a section or sidebar for Linux-specific considerations when adding a load balancer to a scale set.
  • Ensure screenshots and instructions do not imply Windows is the default or only supported OS.
GitHub Create Pull Request
Load Balancer https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/tutorial-gateway-outbound-connectivity.md ...oad-balancer/tutorial-gateway-outbound-connectivity.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates Windows bias by referencing only Windows virtual machine creation in the prerequisites and omitting any mention of Linux VM deployment or Linux-specific guidance. All examples and instructions implicitly assume a Windows VM, with no parity for Linux users.
Recommendations
  • Include links and instructions for creating a Linux VM in Azure alongside the Windows VM reference in the prerequisites.
  • Clarify that the tutorial applies equally to both Windows and Linux VMs, and provide examples or notes for Linux users where relevant.
  • Ensure that any VM-specific steps (such as networking or IP configuration) are described in a way that is platform-agnostic, or provide platform-specific guidance for both Windows and Linux.
  • Review other sections for implicit Windows assumptions and update terminology or examples to reflect cross-platform applicability.
GitHub Create Pull Request
Load Balancer https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/tutorial-deploy-cross-region-load-balancer-template.md ...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-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a bias toward Windows by only referencing the deployment and verification of IIS on Windows Server virtual machines, with no mention of Linux alternatives or examples. The verification step specifically instructs users to expect the default IIS Windows Server web page, and there are no instructions or examples for deploying or verifying a Linux-based web server (e.g., Apache or Nginx).
Recommendations
  • Provide parallel examples for deploying Linux virtual machines, including instructions for configuring a common Linux web server such as Apache or Nginx.
  • In the verification section, include screenshots and steps for accessing the default web page on a Linux VM, not just IIS on Windows.
  • Explicitly mention that the ARM template can be customized for either Windows or Linux VMs, and link to relevant templates or documentation for Linux deployments.
  • Ensure that terminology and instructions do not assume a Windows environment; for example, refer to 'web server' generically rather than specifically referencing IIS unless both platforms are covered.
GitHub Create Pull Request
Load Balancer https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/tutorial-load-balancer-standard-public-zonal-portal.md ...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-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The tutorial specifically instructs users to create a basic Internet Information Services (IIS) site, which is a Windows-only web server. There are no examples or instructions for deploying a Linux-based web server (such as Apache or Nginx), nor are Linux-specific management or configuration steps mentioned. The documentation implicitly assumes the use of Windows VMs for the web workload, omitting Linux alternatives.
Recommendations
  • Add parallel instructions for deploying a Linux-based web server (e.g., Apache or Nginx) on a Linux VM.
  • Include examples of connecting to Linux VMs (e.g., via SSH) and installing/configuring web servers using Linux command-line tools.
  • Explicitly mention both Windows and Linux options when describing VM creation and workload setup.
  • Provide screenshots or code snippets for both Windows and Linux scenarios to ensure parity.
GitHub Create Pull Request
Load Balancer https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/tutorial-load-balancer-port-forwarding-portal.md ...ancer/tutorial-load-balancer-port-forwarding-portal.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation demonstrates mild Windows bias in the section on connecting to VMs via SSH. It instructs Windows users to open a PowerShell prompt, while Mac and Linux users are told to open a Bash prompt. The SSH command example uses Windows-style path separators ('.\Downloads\lb-key-pair.pem'), which may confuse Linux/Mac users. There are no explicit Linux command-line examples or instructions for Linux-specific tools, and the order of instructions places Windows before Linux/Mac. However, the rest of the tutorial is largely platform-neutral and does not use Windows-specific tools or patterns.
Recommendations
  • Provide both Windows (PowerShell) and Linux/Mac (Bash) command examples side-by-side, with appropriate path syntax for each.
  • Use platform-neutral path examples (e.g., '~/Downloads/lb-key-pair.pem' for Linux/Mac, '.\Downloads\lb-key-pair.pem' for Windows) and clarify which applies to which OS.
  • Mention alternative SSH clients for Windows (e.g., PuTTY) and for Linux/Mac (native SSH), if relevant.
  • Avoid listing Windows instructions before Linux/Mac; consider presenting both together or alternating order.
  • Explicitly state that the SSH command works on all platforms, with only the path syntax differing.
GitHub Create Pull Request
Load Balancer https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/tutorial-nat-rule-multi-instance-portal.md ...ad-balancer/tutorial-nat-rule-multi-instance-portal.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation demonstrates a subtle Windows bias in the 'Install web server' section, where users are instructed to open a PowerShell prompt if on Windows, and a Bash prompt if on Mac or Linux. The SSH command examples use Windows-style paths ('.\Downloads\myKey.pem'), which may confuse Linux users. The order of instructions consistently lists Windows before Linux/Mac, and PowerShell is mentioned as the default terminal for Windows users, while Bash is for others. There are no Linux-specific tools or patterns highlighted, and the documentation does not provide explicit Linux command-line examples for file paths or alternative shell usage.
Recommendations
  • Provide both Windows and Linux/Mac command examples, especially for SSH commands and file paths (e.g., use '~/Downloads/myKey.pem' for Linux/Mac).
  • List Linux/Mac instructions before Windows, or present them side-by-side to avoid implying Windows primacy.
  • Mention common Linux terminals (e.g., GNOME Terminal, Konsole) alongside Bash, and clarify that PowerShell is specific to Windows.
  • Add notes about file path differences between Windows and Linux/Mac.
  • Ensure parity in troubleshooting steps and tips for both platforms.
GitHub Create Pull Request
Load Balancer https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/egress-only.md ...e-docs/blob/main/articles/load-balancer/egress-only.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
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 exclusively using Windows Server as the VM image in all examples and instructions. There are no references to Linux VM images, nor are there any Linux-specific configuration steps or validation examples. All testing and connectivity instructions assume a Windows environment (e.g., using Microsoft Edge browser), with no mention of Linux tools or alternatives.
Recommendations
  • Include parallel instructions for deploying a Linux VM (e.g., Ubuntu, CentOS) alongside the Windows example.
  • Provide Linux-specific steps for connecting via Bastion (e.g., using SSH from the Azure portal or a browser-based SSH client).
  • Offer Linux-based connectivity validation examples, such as using curl or wget from the command line to test outbound access.
  • Mention both Windows and Linux VM images in the VM creation step, and clarify that the configuration applies to both platforms.
  • Reference Linux documentation or troubleshooting guides where relevant.
GitHub Create Pull Request
Load Balancer https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/cross-subscription-how-to-attach-backend.md ...d-balancer/cross-subscription-how-to-attach-backend.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation presents Windows-oriented tooling (Azure PowerShell) before Linux-friendly alternatives (Azure CLI), with detailed PowerShell examples and explanations. The CLI section is present but less detailed, and there are no explicit Linux shell examples or references to Linux-specific patterns or tools.
Recommendations
  • Present Azure CLI examples before or alongside Azure PowerShell to avoid Windows-first bias.
  • Expand Azure CLI sections with step-by-step explanations matching the detail of PowerShell instructions.
  • Include explicit Linux shell examples (e.g., bash scripts) and note compatibility with Linux/macOS terminals.
  • Add a note clarifying that Azure CLI is cross-platform and preferred for Linux/macOS users.
  • Ensure parity in troubleshooting and cleanup instructions for both PowerShell and CLI users.
GitHub Create Pull Request
Load Balancer https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/cross-subscription-how-to-internal-load-balancer.md ...er/cross-subscription-how-to-internal-load-balancer.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page presents both Azure PowerShell and Azure CLI examples for creating a cross-subscription internal load balancer. However, the PowerShell example is more detailed, with step-by-step resource creation and configuration, while the CLI example is more concise and lacks equivalent depth. The PowerShell example appears first, suggesting a Windows-first approach. There are no Linux-specific tools or shell examples (e.g., Bash), nor is there mention of Linux patterns or considerations.
Recommendations
  • Provide equally detailed Azure CLI examples, including step-by-step resource creation and configuration, matching the PowerShell example.
  • Consider adding Bash script examples for Linux users, especially for multi-step operations.
  • Explicitly mention platform neutrality for CLI commands and clarify that Azure CLI works on Windows, Linux, and macOS.
  • If relevant, add troubleshooting or environment setup notes for Linux users.
  • Ensure that CLI examples are not only present but also as comprehensive and prominent as PowerShell examples.
GitHub Create Pull Request
Load Balancer https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/load-balancer-tcp-reset.md ...main/articles/load-balancer/load-balancer-tcp-reset.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a mild Windows bias by referencing .NET examples for TCP keep-alive configuration and not providing equivalent Linux or cross-platform examples. There are no command-line or configuration examples for Linux environments, and the only code reference is to a Windows-centric technology stack.
Recommendations
  • Include Linux-specific examples for configuring TCP keep-alive, such as using sysctl or socket options in common programming languages (e.g., Python, Java, or C on Linux).
  • Provide references to Linux documentation or tools (e.g., man pages for tcp_keepalive, or links to Linux networking guides).
  • When mentioning .NET examples, also mention cross-platform or Linux-native approaches to ensure parity.
  • Consider adding a section or callout that addresses configuration steps for both Windows and Linux environments.
GitHub Create Pull Request
Load Balancer https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/troubleshoot-load-balancer-imds.md ...icles/load-balancer/troubleshoot-load-balancer-imds.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page consistently references Windows-specific documentation links (e.g., /azure/virtual-machines/windows/instance-metadata-service) and does not mention or link to Linux equivalents. There are no examples or troubleshooting steps tailored for Linux users, and the guidance is Windows-centric throughout.
Recommendations
  • Include parallel links to Linux documentation (e.g., /azure/virtual-machines/linux/instance-metadata-service) wherever Windows links are provided.
  • Add examples and troubleshooting steps for Linux environments, such as using curl or bash scripts to interact with IMDS.
  • Clarify that the error codes and mitigations apply to both Windows and Linux VMs, or specify any differences.
  • Ensure that sample requests and responses are shown for both Windows (PowerShell) and Linux (bash/curl) contexts.
GitHub Create Pull Request
Load Balancer https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/tutorial-add-lb-existing-scale-set-portal.md ...-balancer/tutorial-add-lb-existing-scale-set-portal.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
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 example OS for the virtual machine scale set. There are no Linux-based examples, nor is there mention of Linux images or configuration patterns. This may lead Linux users to feel unsupported or unsure about parity in the process.
Recommendations
  • Include Linux-based VM image options (e.g., Ubuntu, CentOS) in the 'Image' selection step.
  • Add notes or examples for configuring scale sets with Linux VMs, including any differences in administrator account setup (e.g., SSH keys vs. passwords).
  • Clarify that the process is OS-agnostic, or explicitly state any OS-specific considerations.
  • Provide links to Linux-specific tutorials or documentation where relevant.
GitHub Create Pull Request
Load Balancer https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/whats-new.md ...ure-docs/blob/main/articles/load-balancer/whats-new.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page exhibits subtle Windows bias, most notably in the 'Recent releases' section where the link for creating a dual stack application points specifically to a PowerShell-based guide (which is Windows-centric) and does not mention or link to Linux or cross-platform alternatives. No explicit Linux command-line examples (e.g., Bash, CLI) or Linux-specific tooling are referenced. The documentation generally avoids platform-specific examples, but when it does, Windows/PowerShell is prioritized or exclusively mentioned.
Recommendations
  • Ensure that all feature guides (e.g., dual stack application creation) include both PowerShell (Windows) and Bash/CLI (Linux/macOS) instructions, or link to cross-platform guides.
  • Wherever PowerShell is referenced, provide equivalent Azure CLI or Bash examples and links, ideally side-by-side.
  • Audit all linked articles for platform parity and update them to include Linux examples if missing.
  • Explicitly mention that Azure Load Balancer management is supported on both Windows and Linux, and provide documentation navigation for both audiences.
GitHub Create Pull Request
Load Balancer https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/concepts.md ...zure-docs/blob/main/articles/load-balancer/concepts.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
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 web server—without mentioning Linux alternatives (such as Apache or Nginx). No Linux-specific examples, tools, or patterns are provided, and the only concrete workload described is Windows-based.
Recommendations
  • Add Linux-based quickstart examples, such as creating VMs with Apache or Nginx installed and load balancing those web apps.
  • Explicitly mention that Azure Load Balancer supports both Windows and Linux backend VMs.
  • Provide parity in walkthroughs and tutorials by including both Windows (IIS) and Linux (Apache/Nginx) scenarios.
  • Avoid referencing only Windows tools or workloads in introductory or example sections; offer Linux equivalents side-by-side.
GitHub Create Pull Request
Load Balancer https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/cross-subscription-how-to-attach-backend.md ...d-balancer/cross-subscription-how-to-attach-backend.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation presents Azure PowerShell (commonly used on Windows) examples before Azure CLI examples, and the PowerShell section is more detailed, with step-by-step commands and explanations. This ordering and depth may signal a bias toward Windows users and workflows, even though Azure CLI is cross-platform and preferred by many Linux users.
Recommendations
  • Present Azure CLI examples before PowerShell, or alternate the order in different sections to avoid implicit prioritization.
  • Ensure both Azure CLI and PowerShell examples are equally detailed, with step-by-step breakdowns and explanations.
  • Explicitly mention that Azure CLI is cross-platform and suitable for Linux, macOS, and Windows users.
  • Add a short section or note for Linux users, highlighting any platform-specific considerations (such as shell quoting differences).
  • Review included files ([!INCLUDE ...]) to ensure they do not contain Windows-specific instructions or terminology.
GitHub Create Pull Request
Load Balancer https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/distribution-mode-concepts.md ...n/articles/load-balancer/distribution-mode-concepts.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation page demonstrates Windows bias by referencing Remote Desktop Gateway (RD Gateway)—a Windows-only technology—as a primary use case for the three-tuple session persistence mode. No equivalent Linux scenario or tool is mentioned. The example is presented before any general or cross-platform use cases, suggesting a Windows-first perspective.
Recommendations
  • Add Linux-specific use cases, such as scenarios involving SSH bastion hosts, NGINX, or HAProxy, to illustrate session persistence requirements for Linux workloads.
  • Mention cross-platform or Linux-native protocols and applications (e.g., SFTP, rsync, or media streaming servers) that benefit from specific distribution modes.
  • Ensure that examples and use cases are balanced between Windows and Linux, or presented in a neutral, platform-agnostic order.
  • If referencing Windows tools like RD Gateway, provide equivalent Linux alternatives or note that the guidance applies to both platforms where possible.
GitHub Create Pull Request
Load Balancer https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/cross-subscription-how-to-global-backend.md ...d-balancer/cross-subscription-how-to-global-backend.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page provides both Azure PowerShell and Azure CLI examples for all steps, but PowerShell (a Windows-centric tool) is consistently presented first in every section. The introductory and prerequisite sections emphasize Azure PowerShell, including installation and usage notes, before mentioning Azure CLI. There are no Linux-specific shell examples (e.g., Bash), nor are there any references to Linux tools or environments. The overall structure and ordering suggest a subtle Windows bias by prioritizing PowerShell and Windows patterns.
Recommendations
  • Alternate the order of examples, sometimes presenting Azure CLI (Linux-friendly) first.
  • Explicitly mention that Azure CLI works natively on Linux/macOS and provide Bash-specific notes or examples where relevant.
  • Add a short section in prerequisites about using Azure CLI in Linux environments, including installation instructions for Linux.
  • Clarify that both Azure PowerShell and Azure CLI are cross-platform, but highlight CLI's native compatibility with Linux.
  • Consider including screenshots or terminal prompts that reflect Linux environments, not just Windows/PowerShell.
  • Review and update any language that implies PowerShell is the default or preferred approach.
GitHub Create Pull Request
Load Balancer https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/egress-only.md ...e-docs/blob/main/articles/load-balancer/egress-only.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates Windows bias by exclusively using Windows Server as the VM image in all examples and instructions. There are no Linux VM options or examples provided, and all steps (such as connectivity testing) assume a Windows environment (e.g., using Microsoft Edge browser). This may hinder Linux users from following the guide without adaptation.
Recommendations
  • Include Linux VM creation instructions alongside Windows, specifying a popular image such as Ubuntu or CentOS.
  • Provide connectivity test steps for Linux VMs (e.g., using Firefox, Chrome, or curl/wget in the terminal).
  • Explicitly mention that the configuration applies to both Windows and Linux VMs, and highlight any OS-specific considerations.
  • Where administrator credentials are required, clarify differences for Linux (e.g., SSH key authentication vs. password).
  • Ensure screenshots and portal steps are OS-neutral or provide parallel examples for Linux.
GitHub Create Pull Request
Load Balancer https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/howto-load-balancer-imds.md ...ain/articles/load-balancer/howto-load-balancer-imds.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation page demonstrates a mild Windows bias. Windows/PowerShell examples are presented before Linux/cURL examples, and references to documentation links and troubleshooting steps default to Windows-focused pages. The use of PowerShell-specific flags and notes further centers the Windows experience, while Linux instructions are present but less emphasized.
Recommendations
  • Present Linux and Windows examples side-by-side or alternate which comes first to avoid implicit prioritization.
  • Ensure documentation links and references include both Windows and Linux variants, or use platform-neutral landing pages.
  • Provide equal detail and troubleshooting notes for both Linux and Windows command-line tools (e.g., explain --noproxy for curl as well as -NoProxy for PowerShell).
  • Avoid language or structure that assumes Windows as the default platform; clarify that both platforms are supported equally.
GitHub Create Pull Request
Load Balancer https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/load-balancer-floating-ip.md ...in/articles/load-balancer/load-balancer-floating-ip.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation presents Windows Server configuration instructions before Ubuntu/Linux instructions, and uses Windows-specific tools (netsh, PowerShell, Windows firewall) as primary examples. The only advanced scenario linked is for Windows (Always On availability group listener with PowerShell), with no Linux equivalent mentioned. Linux instructions are present but less detailed and appear after Windows examples.
Recommendations
  • Present Linux and Windows configuration instructions in parallel or alternate order to avoid Windows-first bias.
  • Include links to advanced Linux scenarios (e.g., configuring floating IP for Linux-based clustering or HA setups) similar to the Windows Always On listener example.
  • Expand Linux configuration examples to include other distributions (e.g., CentOS, Red Hat) and alternative firewall tools (e.g., firewalld, iptables).
  • Reference Linux-specific documentation and best practices alongside Windows examples.
  • Clarify that both platforms are equally supported and provide troubleshooting tips for common Linux issues.
GitHub Create Pull Request
Load Balancer https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/load-balancer-overview.md .../main/articles/load-balancer/load-balancer-overview.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page for Azure Load Balancer does not provide any platform-specific examples, but where advanced features are referenced (e.g., IPv6 support), the linked documentation uses PowerShell in the URL, suggesting a Windows-centric approach. There is no mention of Linux tools, CLI, or cross-platform command examples, and no explicit Linux parity in instructions or references. The absence of Linux or Azure CLI examples and the implicit prioritization of PowerShell-based documentation indicate a subtle Windows bias.
Recommendations
  • Ensure that all feature and scenario documentation includes both PowerShell and Azure CLI examples, with explicit instructions for Linux users.
  • Reference cross-platform tools and workflows (e.g., Bash, Azure CLI) alongside or before Windows-specific tools like PowerShell.
  • Add a section or note clarifying platform parity and providing links to Linux-specific guidance where available.
  • Review linked documentation to ensure Linux and cross-platform examples are present and easy to find.
  • Avoid using PowerShell as the default or only example in advanced feature guides; provide CLI and REST API alternatives.
GitHub Create Pull Request
Load Balancer https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/manage-admin-state-how-to.md ...in/articles/load-balancer/manage-admin-state-how-to.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation consistently references Windows-based virtual machines in all example links and prerequisites, with no mention of Linux VM equivalents. All resource creation links point to Windows-specific guides (e.g., '/azure/virtual-machines/windows/quick-create-portal', '/azure/virtual-machines/windows/quick-create-powershell', '/azure/virtual-machines/windows/quick-create-cli'). There are no Linux VM creation links or examples, which may lead Linux users to feel excluded or uncertain about parity. While Azure CLI and PowerShell examples are provided (which are cross-platform), the supporting documentation and context are Windows-centric.
Recommendations
  • Add links to Linux VM creation guides alongside Windows VM links in prerequisites for portal, PowerShell, and CLI sections.
  • Explicitly state that the admin state feature and commands work with both Windows and Linux backend pool instances.
  • Include example resource names and scenarios that reference Linux VMs (e.g., 'myLinuxVM') in addition to Windows VMs.
  • Where possible, provide a short note or example showing how to create or manage backend pool instances with Linux VMs.
  • Ensure parity in documentation references, so that Linux users can follow along without ambiguity or extra research.
GitHub Create Pull Request
← Previous Page 13 of 16 Next →