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 251-275 of 388 flagged pages
Load Balancer Troubleshoot common problems with Azure Load Balancer ...n/articles/load-balancer/load-balancer-troubleshoot.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 page demonstrates Windows bias by exclusively referencing Windows-specific tools (PsPing, Netsh) for network troubleshooting and capture, without providing Linux/macOS equivalents or examples. All command-line instructions and troubleshooting steps assume a Windows environment, and no Linux alternatives (such as tcpdump, ping, or nmap) are mentioned.
Recommendations
  • Include Linux/macOS equivalents for network troubleshooting, such as using 'tcpdump', 'ping', or 'nmap' for connectivity tests and packet captures.
  • Provide example commands for both Windows and Linux environments side-by-side.
  • Mention cross-platform tools and clarify which steps are OS-specific.
  • Add guidance for collecting network traces on Linux (e.g., using 'tcpdump' or 'wireshark').
GitHub Create Pull Request
Load Balancer Migrate from Inbound NAT rules version 1 to version 2 ...cles/load-balancer/load-balancer-nat-pool-migration.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation demonstrates a notable Windows bias. While Azure CLI examples are provided (which are cross-platform), there is a heavy emphasis on PowerShell, including a dedicated automation section that only uses PowerShell modules and commands. Prerequisites and automation steps explicitly require PowerShell and Azure PowerShell modules, with no mention of Bash, shell scripts, or Linux-native automation. Additionally, the upgrade process for Basic to Standard Load Balancer is linked only to a PowerShell-based guide. There are no Linux/macOS-specific instructions or alternative automation paths.
Recommendations
  • Provide equivalent Bash/shell script automation examples for Linux/macOS users, especially for the automation section.
  • Include instructions for installing and using Azure CLI for all steps where PowerShell is currently required.
  • Link to or create documentation for upgrading Load Balancer SKU using Azure CLI or REST API, not just PowerShell.
  • Explicitly state that Azure CLI commands work cross-platform and highlight any OS-specific considerations.
  • Where PowerShell modules are referenced, offer alternatives or note their (in)compatibility with PowerShell Core on Linux/macOS.
GitHub Create Pull Request
Load Balancer Load Balancer TCP Reset and idle timeout in Azure ...main/articles/load-balancer/load-balancer-tcp-reset.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation references .NET examples for TCP keep-alive configuration and provides a link to Microsoft's .NET API documentation, which is primarily relevant for Windows environments. There are no examples or references for configuring TCP keep-alive on Linux or macOS systems, nor are cross-platform tools or commands mentioned. The only concrete example given is Windows/.NET-centric, and Linux/macOS equivalents are omitted.
Recommendations
  • Add examples for configuring TCP keep-alive on Linux (e.g., using sysctl, socket options in Python, or iptables).
  • Include references to cross-platform programming languages and libraries (e.g., Python, Java, Go) for TCP keep-alive.
  • Provide links to Linux and macOS documentation for TCP keep-alive settings.
  • Ensure that examples and guidance are presented for both Windows and Linux/macOS environments.
GitHub Create Pull Request
Load Balancer Troubleshoot Azure Load Balancer health probe status ...ncer/load-balancer-troubleshoot-health-probe-status.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page exhibits a moderate Windows bias. Troubleshooting steps frequently reference Windows-specific tools (PsPing, TCPing, Netsh), and commands (netstat -an, netsh advfirewall) are shown in Windows syntax first or exclusively. Linux equivalents are sometimes mentioned, but not consistently, and examples for Linux tools (e.g., how to use TCPing or alternatives on Linux) are missing. The overall troubleshooting flow assumes familiarity with Windows environments, making it less accessible for Linux/macOS users.
Recommendations
  • Provide Linux/macOS equivalents for all troubleshooting steps, including tool usage (e.g., recommend nmap, nc, ss, or hping for port/probe testing on Linux).
  • Include explicit Linux/macOS command examples alongside Windows commands, not just in passing.
  • Mention installation steps for required tools on Linux (e.g., how to install TCPing alternatives, or use built-in utilities).
  • Ensure parity in troubleshooting workflows, so Linux users can follow along without needing to translate Windows-specific instructions.
  • Consider adding a table or section summarizing tool/command equivalents across platforms.
GitHub Create Pull Request
Load Balancer Manage Administrative State in Azure Load Balancer ...in/articles/load-balancer/manage-admin-state-how-to.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
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-specific virtual machine creation guides in all prerequisite sections, omitting Linux VM equivalents. This creates a subtle but persistent Windows bias, as Linux users are not provided direct guidance or parity in example links, even though the Azure CLI and PowerShell commands themselves are cross-platform.
Recommendations
  • Add links to Linux VM creation guides alongside Windows links in all prerequisite sections.
  • Clarify that both Windows and Linux VMs are supported as backend pool instances.
  • Where examples reference VM creation, provide both Windows and Linux options or use neutral language.
  • Ensure that referenced quickstart and example pages for CLI and PowerShell include Linux scenarios or links.
GitHub Create Pull Request
Load Balancer Quickstart: Create an internal load balancer - Azure portal ...r/quickstart-load-balancer-standard-internal-portal.md
Medium Priority View Details →
Scanned: 2026-01-13 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 configuration and testing steps (IIS installation, web server setup) use Windows-specific tools (PowerShell, IIS, Windows Administrative Tools). There are no Linux VM examples, nor instructions for deploying or configuring a Linux-based web server (e.g., Apache or Nginx). All command-line examples are PowerShell-only, and the workflow assumes familiarity with Windows environments.
Recommendations
  • Add parallel instructions for creating a Linux VM (e.g., Ubuntu) in the Azure portal.
  • Provide Linux-specific steps for installing a web server (e.g., Apache or Nginx) and customizing the index.html file.
  • Include Bash or shell commands for Linux VM configuration, alongside the PowerShell examples.
  • Mention Linux as a supported/tested platform in the prerequisites and VM creation steps.
  • Show screenshots or command examples for both Windows and Linux environments.
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-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation provides both Azure CLI and PowerShell examples for deployment, but PowerShell is mentioned first in the main deployment instructions and is featured in the initial explanation. There is no explicit mention of Linux/macOS environments, nor are there any Bash-specific or Linux-native instructions. The cleanup section also uses PowerShell first, and the CLI examples use generic shell commands but do not clarify Linux/macOS usage or differences. There are no references to Linux tools or patterns, and no guidance for Linux users on prerequisites or environment setup.
Recommendations
  • Explicitly mention Linux/macOS compatibility and provide Bash-specific instructions where appropriate.
  • Ensure Azure CLI examples are shown first or in parallel with PowerShell, as CLI is cross-platform.
  • Add notes or sections clarifying how to run commands on Linux/macOS, including shell differences and environment setup.
  • Avoid assuming PowerShell as the default, especially for cross-platform documentation.
  • Include troubleshooting tips for Linux/macOS users if any steps differ.
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-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example Powershell Heavy
Summary
The documentation demonstrates a notable Windows bias in the virtual machine creation and configuration steps. Only Windows Server images are used for backend VMs, and the IIS installation relies exclusively on PowerShell commands. No Linux VM examples or Linux web server installation instructions are provided, which may hinder Linux/macOS users from following the quickstart without significant adaptation.
Recommendations
  • Include parallel examples for creating Linux VMs (e.g., using Ubuntu or CentOS images) alongside Windows examples.
  • Provide instructions for installing a web server on Linux VMs (e.g., using apt/yum to install nginx or Apache) and updating the default web page.
  • Explicitly mention that the steps can be adapted for Linux, and link to relevant documentation for Linux VM setup.
  • When showing code blocks for VM creation and configuration, alternate or combine Windows and Linux examples to ensure parity.
  • Clarify that the 'commandToExecute' in CustomScriptExtension can run bash scripts for Linux VMs.
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-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides only Azure PowerShell examples for deploying the ARM template, with no equivalent Azure CLI (bash) or Linux/macOS shell instructions. The deployment walkthrough is centered on PowerShell, which is most familiar to Windows users, and does not mention or demonstrate Linux-native tools until a brief note after the main instructions. This creates friction for Linux/macOS users who may prefer or require bash/CLI workflows.
Recommendations
  • Add equivalent Azure CLI (bash) instructions for deploying the ARM template, including variable prompts and deployment commands.
  • Present both PowerShell and CLI examples side-by-side, or clearly indicate both options at the start of the deployment section.
  • Explicitly mention that Azure Cloud Shell supports both PowerShell and Bash, and link to relevant CLI documentation.
  • Ensure screenshots and output examples are provided for both PowerShell and CLI where relevant.
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-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits Windows bias by consistently linking to Windows-specific documentation (e.g., /azure/virtual-machines/windows/instance-metadata-service) for further information, including supported HTTP verbs and rate limiting. There are no references to Linux or cross-platform equivalents, nor are Linux/macOS usage patterns or troubleshooting steps mentioned. This may create friction for Linux users seeking parity or platform-specific guidance.
Recommendations
  • Include links to both Windows and Linux versions of the Azure Instance Metadata Service documentation (e.g., /azure/virtual-machines/linux/instance-metadata-service).
  • Ensure that mitigation steps and examples reference cross-platform tools (e.g., curl, wget, bash) in addition to any Windows-specific tools.
  • Add a section or note clarifying that the guidance applies to both Windows and Linux VMs, and highlight any platform-specific differences.
  • Present examples and documentation links for Linux/macOS first or in parallel with Windows, rather than Windows-only or Windows-first.
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-13 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 notable Windows bias: the deployed virtual machines are configured with IIS (Internet Information Server), a Windows-only web server, and the verification step explicitly references the default IIS Windows Server web page. There are no examples or instructions for deploying or verifying a Linux-based web server (such as Apache or Nginx). The template and tutorial steps do not mention Linux options or provide parity for Linux users.
Recommendations
  • Provide alternative instructions and template parameters for deploying Linux virtual machines (e.g., Ubuntu) with a common Linux web server (Apache or Nginx).
  • Include screenshots and verification steps for Linux-based web pages, not just IIS.
  • Explicitly mention that the template can be adapted for Linux workloads and provide example ARM template snippets for Linux VM configuration.
  • Ensure that both Windows and Linux options are presented equally in the tutorial, including in the verification and clean-up steps.
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-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page consistently references Windows virtual machines as the example platform and provides links only to Windows VM creation guides. There are no Linux-specific instructions, examples, or references, which may create friction for users deploying Linux-based NVAs or VMs.
Recommendations
  • Include parallel instructions and examples for Linux virtual machines, such as referencing the Azure Linux VM creation guide.
  • Clarify that the steps are applicable to both Windows and Linux VMs unless there are platform-specific differences.
  • Add notes or links for deploying Linux-based NVAs and VMs in Azure.
  • Ensure terminology and screenshots (if any) are platform-neutral or provide both Windows and Linux variants.
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-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation demonstrates bias towards Windows by exclusively referencing Windows virtual machines in the prerequisites and setup steps. There are no examples, links, or instructions for deploying or configuring Linux VMs, nor is there mention of Linux-specific considerations. This may lead Linux users to feel unsupported or unclear about how to follow the tutorial.
Recommendations
  • Include parallel instructions and links for creating and configuring Linux virtual machines (e.g., add a link to 'Create a Linux VM in the Azure portal').
  • Clarify that the steps apply equally to Linux VMs, or note any differences in networking or outbound connectivity for Linux.
  • Provide examples or screenshots using both Windows and Linux VMs to demonstrate cross-platform applicability.
  • Explicitly mention that the Gateway Load Balancer configuration is OS-agnostic, if true, to reassure users of Linux support.
GitHub Create Pull Request
Load Balancer Tutorial: Create a single virtual machine inbound NAT rule - Azure portal ...ancer/tutorial-load-balancer-port-forwarding-portal.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation demonstrates a mild Windows bias, particularly in the 'Install web server' section. It instructs users to open a Bash prompt if on Mac or Linux, but a PowerShell prompt if on Windows, and the SSH command example uses Windows path syntax ('.\Downloads\lb-key-pair.pem'), which is PowerShell/Windows-specific. There are no explicit Linux shell examples or Linux-first instructions, and Windows terminology is presented before Linux/Mac alternatives.
Recommendations
  • Provide both Windows and Linux/Mac command examples for SSH, using appropriate path syntax (e.g., './Downloads/lb-key-pair.pem' for Linux/Mac, '.\Downloads\lb-key-pair.pem' for Windows).
  • Explicitly mention that Bash is available on Windows via WSL, and provide instructions for using it.
  • When referencing prompts, list Linux/Mac first or equally with Windows, rather than defaulting to Windows-first phrasing.
  • Include a note or table summarizing the differences in command syntax between platforms for key steps.
  • Ensure that any tool or pattern mentioned (e.g., PowerShell) is matched with its Linux/Mac equivalent (e.g., Bash, Terminal) and that examples are provided for both.
GitHub Create Pull Request
Load Balancer Tutorial: Load balance VMs within an availability zone - Azure portal ...ttps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/tutorial-load-balancer-standard-public-zonal-portal.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The tutorial focuses on creating and testing a load balancer using Azure portal, but the checklist and included steps specifically mention creating a basic Internet Information Services (IIS) site, which is a Windows-only web server. There is no mention of Linux alternatives (e.g., Apache, Nginx), nor are there examples or instructions for deploying or testing with Linux VMs. The documentation implicitly assumes a Windows environment for the application workload.
Recommendations
  • Include parallel instructions for deploying a Linux-based web server (e.g., Apache or Nginx) alongside the IIS example.
  • Provide examples of creating and configuring Linux VMs in the load balancer backend pool.
  • Add testing steps for Linux workloads, such as verifying access to an Apache/Nginx site.
  • Explicitly mention that both Windows and Linux VMs are supported and link to relevant Linux documentation.
GitHub Create Pull Request
Load Balancer Attach a cross-subscription backend to an Azure Load Balancer ...d-balancer/cross-subscription-how-to-attach-backend.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
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) instructions before Azure CLI examples, and the PowerShell section is more detailed and extensive. This ordering and depth may signal a bias toward Windows users and workflows, as Linux users typically prefer Azure CLI. No Linux-specific tools or shell examples are provided, and the CLI section is shorter and less explanatory.
Recommendations
  • Present Azure CLI examples before PowerShell, as CLI is cross-platform and preferred by many Linux users.
  • Ensure both PowerShell and CLI sections have equal detail, including step-by-step explanations and resource references.
  • Add explicit notes about platform compatibility for each tool (e.g., CLI works natively on Linux/macOS/Windows, PowerShell requires installation on Linux).
  • Consider including Bash script examples or guidance for Linux users where appropriate.
  • Review included files ([!INCLUDE ...]) to ensure they do not contain Windows-centric instructions or terminology.
GitHub Create Pull Request
Load Balancer Create a cross-subscription internal load balancer ...er/cross-subscription-how-to-internal-load-balancer.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page demonstrates a bias toward Windows by presenting Azure PowerShell instructions and examples before Azure CLI, with more detailed PowerShell steps and explanations. The PowerShell section is more verbose, with step-by-step variable assignments and resource creation, while the CLI section is more concise. There are no Linux-specific tools or shell examples (e.g., Bash), and no mention of Linux environments or considerations.
Recommendations
  • Alternate the order of examples so that Azure CLI (commonly used on Linux/macOS) appears before PowerShell, or present both side-by-side.
  • Expand CLI examples to match the detail and step-by-step guidance provided in the PowerShell section.
  • Include explicit Bash shell examples or notes for Linux users, such as environment setup or command syntax differences.
  • Add a section or note clarifying that both PowerShell and CLI are cross-platform, and provide links or instructions for using the CLI on Linux/macOS.
  • Review included files ([!INCLUDE ...]) to ensure they do not contain Windows-specific instructions or assumptions.
GitHub Create Pull Request
Load Balancer Retrieve load balancer and virtual machine IP metadata using Azure Instance Metadata Service (IMDS) ...ain/articles/load-balancer/howto-load-balancer-imds.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation demonstrates a mild Windows bias: Windows/PowerShell examples and links are presented before Linux equivalents, and Windows-specific tools (PowerShell) are referenced with additional detail and notes. The 'Learn more' and 'Prerequisites' sections link to Windows-focused documentation first, and troubleshooting/usage notes are PowerShell-centric.
Recommendations
  • Present Linux and Windows examples side-by-side or alternate which comes first to avoid implicit prioritization.
  • Ensure all links to further documentation include both Linux and Windows tabs, or link to neutral pages.
  • Provide equal detail and troubleshooting notes for Linux tools (e.g., curl proxy bypass nuances) as for PowerShell.
  • Add explicit mention of Linux prerequisites and considerations in the 'Prerequisites' section.
  • Review and update references to ensure Linux users are equally supported in 'Next steps' and related links.
GitHub Create Pull Request
Load Balancer Azure Load Balancer Floating IP configuration ...in/articles/load-balancer/load-balancer-floating-ip.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
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) in detail. The only scenario link provided is for Windows (Always On availability group listener with PowerShell), with no equivalent Linux scenario or parity in linked examples. Linux instructions are present but less detailed and lack cross-distro guidance.
Recommendations
  • Alternate the order of Windows and Linux instructions, or present them side-by-side to avoid implicit prioritization.
  • Provide equivalent scenario links and examples for Linux (e.g., configuring Always On availability group listeners on Linux VMs).
  • Expand Linux instructions to cover other distributions (e.g., CentOS, Red Hat) and common firewall tools (e.g., firewalld, iptables) in addition to UFW.
  • Reference Linux-specific documentation and tools where appropriate, not just Windows-centric ones.
  • Explicitly state parity and differences between Windows and Linux approaches in the introduction and throughout the document.
GitHub Create Pull Request
Load Balancer Load Balancer TCP Reset and idle timeout in Azure ...main/articles/load-balancer/load-balancer-tcp-reset.md
Medium Priority View Details →
Scanned: 2026-01-11 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 .NET examples for TCP keep-alive configuration and mentioning Windows-centric error messages, while omitting Linux-specific examples, tools, or guidance. There are no PowerShell commands or explicit Windows tools, but the only code reference is for .NET, which is primarily associated with Windows environments. No Linux commands (e.g., sysctl, iptables, or socket options) or examples are provided for configuring TCP keep-alive or handling TCP resets.
Recommendations
  • Add Linux-specific examples for configuring TCP keep-alive, such as using sysctl or modifying /etc/sysctl.conf.
  • Include sample commands for checking and setting TCP keep-alive parameters on Linux (e.g., using netstat, ss, or sysctl).
  • Reference Linux error messages or behaviors that may occur when connections are reset or idle timeouts are reached.
  • Provide parity in code samples, such as showing both .NET (Windows) and Python or C (Linux) examples for TCP keep-alive.
  • Mention relevant Linux documentation or man pages (e.g., man 7 tcp) for further reading.
GitHub Create Pull Request
Load Balancer Manage Administrative State in Azure Load Balancer ...in/articles/load-balancer/manage-admin-state-how-to.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation consistently references Windows-based virtual machines in all example links and prerequisites, such as '/azure/virtual-machines/windows/quick-create-portal', '/azure/virtual-machines/windows/quick-create-powershell', and '/azure/virtual-machines/windows/quick-create-cli'. There are no explicit Linux VM examples, links, or instructions, even though Azure supports Linux VMs equally. This creates a subtle Windows bias, especially in the onboarding and prerequisites sections, by implying Windows is the default or only supported platform.
Recommendations
  • Add parallel Linux VM links in the prerequisites for each method (portal, PowerShell, CLI), e.g., '/azure/virtual-machines/linux/quick-create-portal', etc.
  • Include example resource names and walkthroughs that reference Linux VMs, or clarify that the instructions apply equally to Linux and Windows VMs.
  • Where VM creation is referenced, provide both Windows and Linux options, or use neutral language and links that encompass both.
  • Review all code samples and ensure that any OS-specific steps (such as VM provisioning) are not Windows-centric, or provide Linux equivalents.
  • Explicitly state in the introduction and prerequisites that both Windows and Linux backend pool instances are supported.
GitHub Create Pull Request
Load Balancer Monitor Azure Load Balancer ...b/main/articles/load-balancer/monitor-load-balancer.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides detailed examples for both Azure PowerShell and Azure CLI when creating diagnostic settings for Azure Load Balancer monitoring. However, PowerShell examples are presented first and in greater detail, which may signal a Windows-first bias. The PowerShell section includes variable assignment and step-by-step instructions for multiple destinations (Log Analytics, Storage, Event Hub), while the CLI section is somewhat more concise. No explicit Linux-specific tools or shell patterns (e.g., bash, zsh) are mentioned, and there are no references to Linux-native scripting or automation approaches. The CLI examples are cross-platform, but the ordering and depth of PowerShell coverage may reinforce a perception of Windows preference.
Recommendations
  • Alternate the order of PowerShell and CLI examples, or present CLI first to signal platform neutrality.
  • Explicitly state that Azure CLI commands work on Linux, macOS, and Windows, and mention shell compatibility where relevant.
  • Provide bash/zsh script examples for automation, especially for Linux users.
  • Where PowerShell is referenced, clarify that Azure PowerShell is available cross-platform (Windows, Linux, macOS) and link to installation guides for all platforms.
  • Consider adding a brief section on using REST API directly with curl or similar Linux-native tools for advanced users.
  • Review reusable content includes to ensure parity in platform references and avoid implicit Windows prioritization.
GitHub Create Pull Request
Load Balancer Common error codes for Azure Instance Metadata Service (IMDS) ...icles/load-balancer/troubleshoot-load-balancer-imds.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page consistently links to Windows-specific Azure Instance Metadata Service (IMDS) documentation, both in error code explanations and in the 'Next steps' section. There are no references to Linux-specific documentation, nor are there examples or guidance for Linux users. This creates a Windows-first bias and leaves Linux users without clear parity or tailored troubleshooting information.
Recommendations
  • Include links to Linux-specific IMDS documentation (e.g., /azure/virtual-machines/linux/instance-metadata-service) alongside or instead of Windows links.
  • Ensure that mitigation steps and examples reference both Windows and Linux environments, or are platform-neutral.
  • Add troubleshooting guidance and sample requests for Linux users, such as using curl or bash, in addition to any PowerShell or Windows examples.
  • Review referenced articles (such as 'How to retrieve load balancer metadata') to confirm they provide Linux parity and update them if necessary.
GitHub Create Pull Request
Load Balancer Troubleshoot Azure Load Balancer resource health, frontend, and backend availability problems ...s/blob/main/articles/load-balancer/troubleshoot-rhc.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation demonstrates Windows bias by referencing Windows tools and examples before Linux equivalents. For instance, when instructing users to check listening ports, the Windows command ('netstat -a') is mentioned first, and the Linux command ('netstat -l') is mentioned second. Additionally, the troubleshooting link for high CPU issues is specific to Azure Windows VMs, with no equivalent link or guidance for Linux VMs. There are no PowerShell-heavy examples or exclusive use of Windows tools, but the ordering and omission of Linux-specific troubleshooting resources indicate a subtle bias.
Recommendations
  • Present Linux and Windows commands in parallel or alternate their order to avoid implicit prioritization.
  • Include troubleshooting links and guidance for both Windows and Linux VMs, such as a link to troubleshooting high CPU issues on Azure Linux VMs.
  • Ensure that examples and instructions are platform-neutral or provide equal detail for both operating systems.
  • Review other troubleshooting steps for OS-specific bias and add Linux equivalents where missing.
GitHub Create Pull Request
Load Balancer Tutorial: Add Azure Load Balancer to an existing Virtual Machine Scale Set - Azure portal ...-balancer/tutorial-add-lb-existing-scale-set-portal.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation demonstrates bias towards Windows by exclusively using Windows Server as the VM image in the scale set creation steps, with no mention or example of Linux-based images. There are no Linux-specific instructions, nor is there guidance for users who may want to deploy Linux VMs in their scale set. The tutorial implicitly assumes a Windows environment, which may not reflect the diversity of Azure users and workloads.
Recommendations
  • Provide parallel instructions and examples for creating a Virtual Machine Scale Set using a popular Linux image (e.g., Ubuntu, CentOS) alongside the Windows example.
  • Include notes or sections highlighting any differences in configuration or management for Linux-based scale sets, such as SSH key authentication instead of passwords.
  • Ensure that all steps, including networking and load balancer configuration, are applicable to both Windows and Linux VM types, and clarify any OS-specific considerations.
  • Consider adding screenshots or references that show Linux options in the Azure portal where relevant.
GitHub Create Pull Request
← Previous Page 11 of 16 Next →