Load Balancer

188
Total Pages
143
Linux-Friendly Pages
45
Pages with Bias
23.9%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

117 issues found
Showing 76-100 of 117 flagged pages
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-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy πŸ”§ Windows Tools Windows First Missing Linux Example
Summary
The documentation page exhibits a notable Windows bias. PowerShell is featured heavily, especially in the automation and migration sections, with references to installing PowerShell and Azure PowerShell modules. The automation script is only provided for PowerShell, with no equivalent for Bash or other Linux-native scripting environments. The prerequisites and instructions for automation are Windows-centric, and Windows/PowerShell tools are mentioned before or instead of Linux alternatives. There are no explicit Linux/macOS-specific examples or guidance, and the CLI examples are present but not as detailed or prioritized as PowerShell.
Recommendations
  • Provide Bash or shell script equivalents for automation tasks, especially for the migration process.
  • Include instructions for installing and using Azure CLI on Linux/macOS, and clarify that all CLI commands work cross-platform.
  • Offer parity in automation modules/scripts, such as a Python or Bash script for NAT Pool migration.
  • List CLI examples before PowerShell, or present them side-by-side to avoid Windows-first ordering.
  • Remove or supplement Windows-specific prerequisites (e.g., PowerShell installation) with Linux/macOS alternatives.
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 06:20
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, which are primarily relevant to 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 code example link is Windows/.NET-centric, and no Linux equivalents (such as sysctl, socket options, or relevant documentation) are provided.
Recommendations
  • Include Linux-specific instructions or examples for configuring TCP keep-alive, such as using sysctl or modifying /etc/sysctl.conf.
  • Reference cross-platform programming libraries (e.g., Python, Java) and how they handle TCP keep-alive.
  • Provide links to Linux documentation or man pages (e.g., man 7 tcp) for further reading.
  • Add macOS-specific notes if there are differences in TCP keep-alive configuration.
GitHub Create Pull Request
Load Balancer Manage Azure Load Balancer health status ...es/load-balancer/load-balancer-manage-health-status.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy πŸ”§ Windows Tools Missing Linux Example
Summary
The documentation page demonstrates Windows bias primarily in the REST API section, where guidance for obtaining the required Bearer access token references only the Windows PowerShell cmdlet Get-AzAccessToken, with no mention of Linux/macOS alternatives (such as Azure CLI or REST calls). No Linux/macOS-specific instructions or examples are provided for authentication, which may hinder non-Windows users. The rest of the page is platform-neutral, focusing on Azure portal and REST API usage.
Recommendations
  • Add instructions for obtaining a Bearer access token using Azure CLI (az account get-access-token), which works on Linux/macOS/Windows.
  • Include a cross-platform example for authentication, such as using curl with a token retrieved via Azure CLI.
  • Reference official Azure CLI documentation alongside PowerShell for token retrieval.
  • Explicitly state that the REST API method is platform-agnostic and provide guidance for Linux/macOS users.
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-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
πŸ”§ Windows Tools Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. Troubleshooting steps frequently reference Windows-specific tools (PsPing, TCPing, netsh advfirewall), and examples are shown using Windows command syntax first. Linux alternatives (e.g., iptables, netstat -l) are mentioned, but not with equal detail or example commands. Some tools (PsPing, TCPing) are not natively available on Linux, and no Linux-native equivalents or installation guidance are provided.
Recommendations
  • Provide Linux-native equivalents for PsPing and TCPing (e.g., use nc, nmap, or hping3) and show example commands.
  • Offer step-by-step Linux troubleshooting commands alongside Windows examples, with equal detail.
  • Include installation instructions for any third-party tools used on Linux.
  • Present command examples for both platforms in parallel, rather than Windows-first.
  • Clarify which steps/tools are platform-specific and offer alternatives where needed.
GitHub Create Pull Request
Load Balancer Troubleshoot common problems with Azure Load Balancer ...n/articles/load-balancer/load-balancer-troubleshoot.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy πŸ”§ Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Windows-specific tools (PsPing, Netsh) for network diagnostics and providing no Linux/macOS equivalents or examples. All troubleshooting steps involving command-line utilities assume a Windows environment, and there is no mention of Linux-native tools or cross-platform alternatives.
Recommendations
  • Include Linux/macOS equivalents for network diagnostics, such as 'ping', 'nc' (netcat), 'ss', 'tcpdump', or 'nmap'.
  • Provide example commands for both Windows (PsPing, Netsh) and Linux/macOS (ping, netcat, tcpdump) in troubleshooting sections.
  • Explicitly state that the procedures apply to both Windows and Linux VMs, or clarify any OS-specific steps.
  • Reorder examples to present both Windows and Linux options side-by-side, or alternate which OS is shown first.
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 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation consistently references Windows virtual machines in all prerequisites and example links, with no mention of Linux VM equivalents. All resource creation links point to Windows-specific guides, and there are no Linux-specific instructions or examples. This creates friction for Linux users, who must infer or search for Linux VM steps themselves.
Recommendations
  • Add explicit links to Linux VM creation guides in the prerequisites for each method (portal, PowerShell, CLI).
  • Include example commands and instructions for Linux VM scenarios, ensuring parity with Windows examples.
  • Clarify that the Azure CLI and PowerShell examples work for both Windows and Linux environments, and specify any platform-specific considerations.
  • Where VM OS is referenced, use neutral language (e.g., 'virtual machines' instead of 'Windows virtual machines') unless OS-specific steps are required.
  • If any steps differ for Linux VMs (e.g., NIC configuration), document those differences.
GitHub Create Pull Request
Load Balancer Move an Azure Load Balancer to another Azure region ...ad-balancer/move-across-regions-azure-load-balancer.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
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 using the Azure portal and Azure PowerShell. All command-line examples are exclusively in PowerShell, with explicit references to Windows tools (e.g., notepad.exe) and PowerShell cmdlets. There are no CLI or Bash examples, nor any mention of Linux/macOS command-line workflows. The structure and examples assume a Windows environment, which may create friction for Linux/macOS users.
Recommendations
  • Add equivalent instructions using Azure CLI (az) commands, which are cross-platform and widely used on Linux/macOS.
  • Replace or supplement references to Windows-only tools (e.g., notepad.exe) with platform-neutral alternatives (e.g., 'edit the file in your preferred text editor').
  • Explicitly mention that the process can be completed on Linux/macOS and provide any necessary environment setup steps.
  • Where PowerShell is used, clarify if PowerShell Core (pwsh) is supported on non-Windows platforms, and provide examples if so.
  • Reorder or parallelize examples so that Linux/macOS-friendly approaches (Azure CLI, Bash) are presented alongside or before Windows/PowerShell methods.
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-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example Powershell Heavy
Summary
The documentation demonstrates notable Windows bias in the virtual machine creation and configuration steps. Only Windows Server images are used for VM creation, and the instructions for installing a web server rely exclusively on Windows-specific tools (IIS, PowerShell). There are no examples or guidance for deploying Linux VMs or installing a Linux web server (e.g., Apache or Nginx). This creates friction for Linux/macOS users who may prefer or require Linux-based backend servers.
Recommendations
  • Provide parallel examples for creating Linux VMs (e.g., using --image UbuntuLTS or other Linux images).
  • Include instructions and Azure CLI commands for installing a web server on Linux VMs (e.g., using CustomScriptExtension to install Apache or Nginx).
  • Explicitly mention that both Windows and Linux VMs are supported, and link to relevant documentation for Linux setup.
  • Offer users a choice at the start of the quickstart to follow either a Windows or Linux path.
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-11 06:20
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 or Bash instructions. The step-by-step deployment section is written for PowerShell users, which is most common on Windows. While it briefly mentions that other methods (Azure CLI, REST API, Portal) exist, it does not provide examples or guidance for Linux/macOS users, nor does it mention Bash or shell scripting. This creates friction for users on non-Windows platforms.
Recommendations
  • Add equivalent Azure CLI (az) example for template deployment, shown alongside or before PowerShell.
  • Explicitly mention that Azure Cloud Shell supports Bash and PowerShell, and provide instructions for both.
  • Reorder deployment instructions so that CLI and Portal methods are presented before or alongside PowerShell.
  • Include notes or links to Linux/macOS-specific guidance for ARM template deployment.
GitHub Create Pull Request
Load Balancer Quickstart: Create an internal load balancer - Azure CLI ...ncer/quickstart-load-balancer-standard-internal-cli.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example Powershell Heavy πŸ”§ Windows Tools
Summary
The documentation exhibits notable Windows bias: all VM creation examples use Windows images (win2022datacenter, Win2019Datacenter), and the IIS installation uses PowerShell commands and Windows-specific tooling. There are no Linux VM examples, nor instructions for deploying or testing with Linux (e.g., Apache/Nginx). The test steps reference Internet Explorer, a Windows-only browser, further excluding Linux/macOS users.
Recommendations
  • Include parallel examples for creating Linux VMs (e.g., using Ubuntu or CentOS images).
  • Provide instructions for installing and configuring a web server on Linux VMs (e.g., Apache or Nginx) using Bash commands.
  • In the testing section, mention how to use browsers or command-line tools (curl, wget) available on Linux/macOS to verify the load balancer.
  • Avoid referencing Windows-only tools (like Internet Explorer); use cross-platform alternatives.
  • Add notes or sections highlighting differences or additional steps for Linux/macOS users.
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-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation provides deployment instructions using both Azure CLI and Azure PowerShell, but PowerShell is featured prominently and sometimes first. There are no explicit Linux/macOS shell examples (e.g., bash), and PowerShell commands are shown without noting their limited availability on Linux/macOS. The cleanup section uses PowerShell commands exclusively, omitting the Azure CLI equivalent for Linux/macOS users.
Recommendations
  • Ensure Azure CLI examples are shown first or equally alongside PowerShell, as CLI is cross-platform.
  • Add explicit bash shell examples for Linux/macOS users, especially for resource cleanup.
  • Clarify that PowerShell examples are for Windows, and note Azure CLI is recommended for Linux/macOS.
  • Where possible, use generic commands (Azure CLI) that work across all platforms.
  • Instruct users how to install Azure CLI and run commands on Linux/macOS.
GitHub Create Pull Request
Load Balancer Tutorial: Create an Azure Global Load Balancer ...articles/load-balancer/tutorial-cross-region-portal.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First πŸ”§ Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. While it provides Azure Portal, Azure CLI, and Azure PowerShell instructions, several patterns favor Windows: PowerShell is given equal weight to CLI (which is cross-platform), but the test and example workloads are Windows-centric (IIS web server), and there are no Linux-specific examples or references. Windows tools (PowerShell, IIS) are mentioned, and the test scenario assumes a Windows backend. Linux users must adapt steps and cannot follow the test as written without substituting their own web server.
Recommendations
  • Include Linux-specific backend pool examples (e.g., Apache or Nginx on Ubuntu VMs) alongside IIS.
  • Add explicit instructions or notes for Linux/macOS users on how to test the load balancer using a Linux web server.
  • Ensure CLI examples use cross-platform shell syntax and avoid Windows-specific conventions.
  • Clarify that PowerShell is available on Linux/macOS, but provide Bash alternatives where appropriate.
  • Present CLI and PowerShell examples in parallel, but highlight CLI as the default for cross-platform usage.
  • Add troubleshooting notes for Linux users, especially regarding VM setup and connectivity.
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-11 06:20
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 only referencing Windows Server (IIS) as the web server deployed on the virtual machines. The verification step explicitly instructs users to expect the default IIS Windows Server web page, with no mention of Linux alternatives (e.g., Apache, Nginx). There are no examples or instructions for deploying or verifying Linux-based VMs or web servers, and no PowerShell or CLI examples are present, but the template and walkthrough are implicitly Windows-centric.
Recommendations
  • Include instructions and screenshots for deploying Linux VMs with a common web server (e.g., Apache, Nginx) alongside the Windows/IIS example.
  • Provide guidance on how to verify deployment for Linux-based web servers (e.g., what default page to expect, troubleshooting tips).
  • Mention that the ARM template can be customized to deploy Linux VMs and link to relevant documentation or templates.
  • Ensure terminology and examples are platform-neutral, or present both Windows and Linux options side-by-side.
GitHub Create Pull Request
Load Balancer Tutorial: Create a load balancer with more than one availability set in the backend pool - Azure portal ...ad-balancer/tutorial-multi-availability-sets-portal.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example Powershell Heavy πŸ”§ Windows Tools
Summary
The tutorial exclusively uses Windows Server images for all VM creation steps and provides only Windows PowerShell commands for configuring IIS. There are no Linux VM options, nor are there Bash or Linux-native instructions for web server setup. The documentation assumes Windows as the default and does not mention Linux alternatives, creating friction for users who prefer or require Linux-based deployments.
Recommendations
  • Include instructions for creating Linux VMs (e.g., Ubuntu, CentOS) alongside Windows VMs.
  • Provide equivalent Bash/SSH commands for installing and configuring a web server (such as Apache or Nginx) on Linux VMs.
  • Add screenshots and portal steps for selecting Linux images during VM creation.
  • Explicitly mention that both Windows and Linux VMs are supported in backend pools, and link to relevant Linux setup documentation.
  • Present Windows and Linux examples in parallel or alternate their order to avoid 'windows_first' bias.
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
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example Powershell Heavy πŸ”§ Windows Tools
Summary
The tutorial exclusively demonstrates VM creation using Windows Server images and provides only Windows PowerShell commands for IIS installation and configuration. There are no examples or instructions for Linux VM creation, nor for installing/configuring a web server on Linux. Windows tools and patterns (PowerShell, IIS) are used throughout, with no mention of Linux equivalents (e.g., Bash, Apache/Nginx). This creates friction for users wishing to deploy Linux-based solutions.
Recommendations
  • Add parallel instructions for creating Linux VMs (e.g., Ubuntu, CentOS) in the VM creation section.
  • Provide Linux shell commands for installing and configuring a web server (e.g., Apache or Nginx) on Linux VMs.
  • Include screenshots or CLI examples for Linux where appropriate.
  • Explicitly mention that both Windows and Linux VMs are supported and provide guidance for both.
  • Where PowerShell is used, offer equivalent Bash commands for Linux users.
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 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation consistently references Windows virtual machines, providing links and examples only for Windows VM deployment. There are no examples, instructions, or references for Linux VM deployment or management, which may create friction for users working with Linux or macOS environments.
Recommendations
  • Include parallel instructions and links for creating and managing Linux virtual machines (e.g., 'Create a Linux VM in the Azure portal').
  • Clarify that the steps apply equally to Linux VMs, or note any differences if they exist.
  • Provide examples or screenshots using both Windows and Linux VMs where relevant.
  • Avoid using Windows VM as the sole example; alternate or use generic VM names.
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
Low Priority View Details →
Scanned: 2026-01-25 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation provides SSH connection instructions for both Mac/Linux (Bash prompt) and Windows (PowerShell prompt) users. However, the SSH command examples use Windows path syntax ('.\Downloads\lb-key-pair.pem'), and the instructions present the Windows/PowerShell context first, which may create minor friction for Linux/macOS users. No Windows-only tools or patterns are used, and Linux-specific steps (such as installing NGINX via apt-get) are included.
Recommendations
  • Provide separate SSH command examples for Windows (PowerShell) and Linux/macOS (Bash), using appropriate path syntax (e.g., './Downloads/lb-key-pair.pem' for Linux/macOS).
  • Explicitly show both sets of commands side-by-side or in tabs to improve clarity for users on different platforms.
  • Consider listing Linux/macOS instructions before or alongside Windows instructions to avoid implicit prioritization.
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
Low Priority View Details →
Scanned: 2026-01-24 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation provides SSH connection instructions for both Mac/Linux (Bash) and Windows (PowerShell) users, but the example SSH command uses Windows path syntax ('.\Downloads\lb-key-pair.pem') and is shown before any Linux/macOS equivalent. There is no explicit Linux/macOS example for the SSH command with typical Unix-style paths, which may cause minor confusion for non-Windows users. However, the rest of the tutorial is platform-agnostic and uses Linux VMs and tools (NGINX, apt-get), making it accessible to all users.
Recommendations
  • Provide both Windows and Linux/macOS SSH command examples, with appropriate path syntax (e.g., './Downloads/lb-key-pair.pem' for Linux/macOS).
  • Explicitly mention that the SSH command path should be adapted to the user's OS.
  • Consider listing Linux/macOS instructions first or side-by-side with Windows instructions to avoid implicit Windows prioritization.
GitHub Create Pull Request
Load Balancer Tutorial: Create Inbound NAT rule V2 - Azure portal ...ad-balancer/tutorial-nat-rule-multi-instance-portal.md
Low Priority View Details →
Scanned: 2026-01-24 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation provides both Linux and Windows instructions for opening a terminal (Bash for Mac/Linux, PowerShell for Windows) and uses cross-platform SSH and NGINX commands. However, in the SSH command examples, the path to the private key is given in Windows (backslash) format (e.g., '.\Downloads\myKey.pem'), and PowerShell is mentioned before Bash. This is a minor 'windows_first' bias, but Linux users can easily adapt the instructions.
Recommendations
  • Show both Windows and Linux/Mac SSH command examples, with appropriate path separators (e.g., '.\Downloads\myKey.pem' for Windows, '~/Downloads/myKey.pem' for Linux/Mac).
  • List Bash (Linux/Mac) before PowerShell (Windows) in the instructions, or present them together.
  • Explicitly state that the SSH command is the same on all platforms, but the path format may differ.
  • Consider using a generic path (e.g., '<path-to-key>/myKey.pem') in the SSH command example.
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
Low Priority View Details →
Scanned: 2026-01-23 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation provides SSH connection instructions for both Mac/Linux (Bash prompt) and Windows (PowerShell prompt), but the example SSH commands use Windows-style paths (e.g., .\Downloads\lb-key-pair.pem) and show the Windows example first. No PowerShell-specific commands or Windows-only tools are used, and Linux users are not blocked from completing the tutorial. The NGINX installation steps are Linux-specific, indicating the VMs are likely Linux-based.
Recommendations
  • Present both Linux/Mac and Windows SSH command examples, with Linux/Mac shown first or side-by-side.
  • 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 is for which OS.
  • Explicitly state that the tutorial is for Linux VMs (if true), or provide Windows VM instructions if applicable.
GitHub Create Pull Request
Load Balancer Inbound NAT rules .../blob/main/articles/load-balancer/inbound-nat-rules.md
Low Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Missing Linux Example Windows First
Summary
The documentation does not provide any OS-specific examples, but all references to connecting to virtual machines via port forwarding implicitly assume RDP or similar Windows-centric scenarios. There is no mention of Linux tools (e.g., SSH) or Linux/macOS workflows, and all tutorials and screenshots focus on the Azure portal, which is platform-neutral but omits command-line or OS-specific guidance. The lack of explicit Linux/macOS parity is a subtle bias.
Recommendations
  • Add explicit examples for connecting to Linux VMs using SSH, including port mapping scenarios.
  • Include references to Linux/macOS command-line tools and workflows (e.g., using SSH with custom ports).
  • Ensure tutorials mention both RDP (Windows) and SSH (Linux/macOS) use cases.
  • Add screenshots or CLI examples for both Windows and Linux/macOS environments.
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
Low Priority View Details →
Scanned: 2026-01-12 00:00
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/bash examples, and links in prerequisites and further reading default to Windows-focused documentation. PowerShell tooling is mentioned explicitly, while Linux uses generic curl. However, Linux examples are present and functional.
Recommendations
  • Present Linux and Windows examples side-by-side or alternate which comes first.
  • Ensure prerequisite and reference links include both Linux and Windows tabs or default to a neutral landing page.
  • Mention Linux-specific considerations (e.g., curl version, proxy settings) as thoroughly as Windows/PowerShell notes.
  • Add troubleshooting and next steps links for Linux users, not just Windows.
  • Clarify that both Windows and Linux are fully supported and provide parity in documentation structure.
GitHub Create Pull Request
Load Balancer Azure Load Balancer health probes ...s/load-balancer/load-balancer-custom-probe-overview.md
Low Priority View Details →
Scanned: 2026-01-12 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 mild Windows bias. In the 'Next steps' section, the only explicit example for creating a load balancer is via PowerShell, which is a Windows-centric tool. There are no Linux/macOS CLI or Bash examples, nor are Azure CLI or template-based instructions highlighted equally. The mention of PowerShell before other automation or scripting tools may create friction for Linux/macOS users.
Recommendations
  • Add Azure CLI and Bash examples for creating and managing health probes and load balancers, especially in the 'Next steps' section.
  • Include links to ARM template and REST API guides alongside PowerShell instructions.
  • Ensure that any automation or scripting references are cross-platform, or provide parity for Linux/macOS users.
  • Explicitly mention that health probe configuration and management can be performed via Azure CLI, ARM templates, or REST API, not just PowerShell.
GitHub Create Pull Request
Load Balancer What's new in Azure Load Balancer ...ure-docs/blob/main/articles/load-balancer/whats-new.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation page is largely platform-neutral, focusing on feature announcements, release notes, and general product information for Azure Load Balancer. However, there is a minor instance of Windows bias: in the 'Recent releases' table, the link for 'IPv6 support for Azure Load Balancer (generally available)' points to a PowerShell-based guide for creating a dual stack application, which is typically associated with Windows environments. There are no explicit Linux/macOS examples, nor are Linux tools or patterns mentioned. No critical tasks are Windows-only, and the page does not reference Windows-specific tools or PowerShell commands directly in the main content.
Recommendations
  • Where links or examples reference PowerShell, provide equivalent CLI, Bash, or Linux-native instructions alongside or before Windows/PowerShell examples.
  • Ensure that referenced guides (such as dual stack application setup) include both PowerShell and Azure CLI/Bash examples for cross-platform parity.
  • Audit linked documentation for similar platform bias and update to include Linux/macOS instructions where missing.
GitHub Create Pull Request
Load Balancer Attach a cross-subscription frontend to an Azure Load Balancer ...-balancer/cross-subscription-how-to-attach-frontend.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation presents both Azure PowerShell and Azure CLI instructions, but consistently lists PowerShell (a Windows-centric tool) first in every section. The PowerShell examples are more verbose and detailed, sometimes including more context or variable usage than the CLI equivalents. There is no mention of Linux-specific shell environments or macOS, nor any guidance for Bash, Zsh, or other common Linux tools. The CLI examples are present and functional, but the overall structure and example order subtly favor Windows users.
Recommendations
  • Alternate the order of PowerShell and CLI tabs, or default to CLI first to better reflect cross-platform usage.
  • Explicitly mention that Azure CLI works on Windows, Linux, and macOS, and provide links or notes for installing CLI on those platforms.
  • Add notes or sections for Linux/macOS users, such as shell environment setup, or common troubleshooting tips for those platforms.
  • Ensure parity in example detailβ€”expand CLI examples to match the variable usage and context shown in PowerShell examples.
  • Consider including Bash script examples for common tasks, or at least reference that CLI commands can be used in Bash/Zsh.
GitHub Create Pull Request
← Previous Page 4 of 5 Next →