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 101-117 of 117 flagged pages
Load Balancer Create a global load balancer with cross-subscription backends ...d-balancer/cross-subscription-how-to-global-backend.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides both Azure PowerShell and Azure CLI instructions in parallel tabs, but PowerShell (a Windows-centric tool) is consistently listed first in every section. The PowerShell examples are more verbose and detailed, sometimes including additional context or variable usage not mirrored in the CLI examples. There is no mention of Linux/macOS-specific considerations, nor are Bash or shell scripting examples provided. The CLI instructions are present, but the overall structure and emphasis favor Windows/PowerShell users.
Recommendations
  • Alternate the order of PowerShell and CLI tabs so that CLI is shown first in some sections, reducing perceived Windows-first bias.
  • Add explicit notes clarifying that Azure CLI works natively on Linux/macOS and is cross-platform, while PowerShell may require installation or additional steps on non-Windows systems.
  • Ensure parity in example detail and variable usage between PowerShell and CLI sections.
  • Consider adding Bash script examples or guidance for Linux/macOS users where relevant.
  • Mention platform-specific installation instructions or troubleshooting tips for both PowerShell and CLI.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Missing Linux Example
Summary
The documentation does not provide any OS-specific examples, commands, or tooling references. However, it implicitly assumes use of the Azure Portal for all management tasks, and does not mention or provide parity for command-line or automation approaches (such as Azure CLI, PowerShell, or REST API). There is no explicit Windows bias, but Linux/macOS users may find the lack of CLI examples limiting, especially if they prefer or require non-GUI workflows.
Recommendations
  • Add examples for managing inbound NAT rules using Azure CLI, which is cross-platform and widely used by Linux/macOS users.
  • If PowerShell examples are added in the future, ensure Azure CLI or REST API equivalents are also provided.
  • Explicitly mention that the Azure Portal is OS-agnostic, and provide links or references to CLI documentation for users who prefer command-line management.
  • Include sample scripts or commands for retrieving port mappings and configuring NAT rules via CLI.
GitHub Create Pull Request
Load Balancer Azure Load Balancer Floating IP configuration ...in/articles/load-balancer/load-balancer-floating-ip.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 presents Windows Server instructions before Ubuntu/Linux instructions, and uses Windows-specific tools (netsh, Windows firewall) in detail. While Linux instructions are provided, the ordering and tool emphasis show a subtle Windows bias.
Recommendations
  • Present Linux and Windows instructions in parallel or alternate order, or clarify that both platforms are equally supported.
  • Include examples for other popular Linux distributions (e.g., CentOS, Red Hat) or macOS if applicable.
  • Reference Linux firewall alternatives (e.g., firewalld, iptables) alongside UFW.
  • Add a summary table comparing steps for Windows and Linux to highlight parity.
  • Ensure links to advanced scenarios (e.g., Always On availability group listeners) include Linux equivalents, not just Windows/PowerShell.
GitHub Create Pull Request
Load Balancer Manage inbound NAT rules for Azure Load Balancer ...ain/articles/load-balancer/manage-inbound-nat-rules.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation provides instructions for managing inbound NAT rules using the Azure portal, PowerShell, and Azure CLI. PowerShell examples are given equal prominence to CLI, but PowerShell is a Windows-centric tool, and its usage is described in detail, including prerequisites and installation steps. The prerequisites section lists PowerShell requirements before CLI, and PowerShell is referenced in metadata and custom tags. There are no Linux-specific shell examples (e.g., Bash), and no mention of Linux/macOS nuances or alternative tools. However, Azure CLI is cross-platform and included throughout, mitigating most friction for Linux/macOS users.
Recommendations
  • Clarify that PowerShell is primarily a Windows tool and recommend Azure CLI for Linux/macOS users.
  • Add explicit Bash shell examples or notes for Linux/macOS users where appropriate.
  • In prerequisites, mention CLI setup before or alongside PowerShell, and provide installation links for Linux/macOS.
  • Review metadata and custom tags to ensure CLI is not deprioritized.
  • Add a note in the introduction or prerequisites section about cross-platform support and tool recommendations based on OS.
GitHub Create Pull Request
Load Balancer Quickstart: Create an internal Azure load balancer - Bicep ...er/quickstart-load-balancer-standard-internal-bicep.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 provides both Azure CLI and Azure PowerShell examples for deployment, resource review, and cleanup. However, PowerShell examples are given equal prominence to CLI, and PowerShell is a Windows-centric tool. There is no explicit mention of Linux/macOS shell environments, nor are there any Bash-specific notes or examples. The CLI examples are cross-platform, but the documentation does not clarify this or encourage their use for non-Windows users. PowerShell is presented as an equivalent option, which may confuse Linux/macOS users who do not have PowerShell installed by default.
Recommendations
  • Clearly state that Azure CLI commands work on Windows, Linux, and macOS, and are recommended for cross-platform use.
  • Add notes or callouts for Linux/macOS users, such as mentioning that PowerShell is optional and CLI is natively supported.
  • Consider listing CLI examples before PowerShell examples to reinforce CLI as the default, cross-platform choice.
  • If PowerShell is mentioned, provide a brief note about its availability on Linux/macOS (with installation links if relevant).
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
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 demonstrates minor Windows bias in the troubleshooting checklist. Specifically, the example for checking listening ports lists the Windows command ('netstat -a') before the Linux equivalent ('netstat -l'), and the link for high CPU troubleshooting refers only to Azure Windows VMs, omitting Linux VM guidance. No PowerShell-exclusive instructions or critical Windows-only steps are present.
Recommendations
  • Present Linux and Windows commands in parallel or alternate order to avoid Windows-first bias.
  • Include links to troubleshooting high CPU issues for Azure Linux VMs alongside the Windows VM link.
  • Where OS-specific instructions are given, ensure both Windows and Linux/macOS users are equally supported.
  • Consider adding macOS-specific notes if relevant for cross-platform parity.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation displays minor Windows bias in the SSH connection instructions: the example command uses Windows-style path separators ('.\Downloads\lb-key-pair.pem') and refers to opening a PowerShell prompt for Windows users, while Mac/Linux users are told to open a Bash prompt. The SSH command is presented in a way that favors Windows conventions, and no explicit Linux/macOS example is given. However, the rest of the tutorial is platform-neutral and does not rely on Windows-specific tools or patterns.
Recommendations
  • Provide both Windows (PowerShell/CMD) and Linux/macOS (Bash) SSH command examples, with correct path separators for each.
  • Explicitly show the Linux/macOS version of the SSH command (e.g., 'ssh -i ~/Downloads/lb-key-pair.pem azureuser@20.99.165.176 -p 221').
  • Clarify that the SSH command syntax may differ slightly between platforms, and link to platform-specific SSH usage documentation if possible.
  • Consider listing Linux/macOS instructions before or alongside Windows instructions to avoid implicit 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-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation shows minor Windows bias in the SSH connection instructions: Windows/PowerShell prompts are mentioned before Linux/macOS, and the SSH command uses Windows path syntax ('.\Downloads\myKey.pem'), which may confuse Linux/macOS users. However, Linux is otherwise well-supported throughout the tutorial, including VM creation and web server installation.
Recommendations
  • Present Linux/macOS and Windows instructions side-by-side or in separate sections, rather than mentioning Windows first.
  • Use platform-appropriate path syntax in SSH examples (e.g., '~/Downloads/myKey.pem' for Linux/macOS, '.\Downloads\myKey.pem' for Windows).
  • Explicitly show both Linux/macOS and Windows SSH command examples.
  • Clarify which steps or commands are platform-specific, and provide alternatives where needed.
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-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation displays minor Windows bias in the SSH connection instructions, where Windows/PowerShell is mentioned before Linux/macOS, and the SSH command uses Windows path syntax ('.\Downloads\myKey.pem') rather than the more common Linux/macOS syntax ('~/Downloads/myKey.pem'). The instructions do acknowledge Linux/macOS users, but Windows is prioritized in both the narrative and examples.
Recommendations
  • Present Linux/macOS and Windows instructions in parallel, or list Linux/macOS first to balance representation.
  • Provide both Windows (PowerShell) and Linux/macOS (Bash) SSH command examples, using appropriate path syntax for each.
  • Explicitly mention that the Azure portal steps are OS-agnostic, and clarify any OS-specific differences where relevant.
  • Consider adding a note or table showing the SSH command for both platforms.
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-11 06:20
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. However, there is a minor instance of Windows bias: the only explicit example link for creating a dual stack application refers to a PowerShell-based guide, which is typically associated with Windows environments. No Linux or cross-platform CLI example is referenced in this context.
Recommendations
  • Provide equivalent Linux/macOS examples (e.g., using Azure CLI or Bash) alongside or before PowerShell examples.
  • When linking to platform-specific guides, clarify their applicability and offer alternatives for other platforms.
  • Ensure that documentation for common tasks (such as creating dual stack applications) includes instructions for both Windows and Linux/macOS users.
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-11 06:20
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 PowerShell (commonly associated with Windows) is consistently listed first in every section. The PowerShell examples are more verbose and detailed, sometimes including additional context or variable usage that is less emphasized in the CLI sections. There is a slight bias towards Windows/PowerShell users, but Linux/macOS users can still follow the CLI instructions without major obstacles.
Recommendations
  • Alternate the order of PowerShell and CLI tabs, or present CLI instructions first in some sections to avoid implicit prioritization.
  • Ensure parity in example detail and context between PowerShell and CLI sections (e.g., variable usage, explanatory notes).
  • Explicitly mention that Azure CLI is cross-platform and suitable for Linux/macOS users.
  • Add a brief note at the top clarifying that both PowerShell and CLI are supported on all platforms, but CLI may be more familiar to Linux/macOS users.
GitHub Create Pull Request
Load Balancer Create a cross-subscription internal load balancer ...er/cross-subscription-how-to-internal-load-balancer.md
Low Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides both Azure PowerShell and Azure CLI examples for creating a cross-subscription internal load balancer, but the PowerShell example is presented first and in greater detail. The CLI example is present, but the PowerShell section is more verbose and uses advanced features, which may suggest a preference for Windows-centric tooling. No Linux/macOS-specific tools or patterns are mentioned, and there are no Bash or shell script examples.
Recommendations
  • Present Azure CLI examples before or alongside PowerShell examples to avoid implicit prioritization of Windows tooling.
  • Expand the Azure CLI section to match the detail and coverage of the PowerShell section, including step-by-step explanations and advanced configuration.
  • Explicitly mention that Azure CLI is cross-platform and suitable for Linux/macOS users.
  • Consider adding Bash script examples or notes for Linux/macOS environments where relevant.
  • Review included files ([!INCLUDE ...]) to ensure they do not contain Windows-only instructions or bias.
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-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation page presents Windows examples and links before Linux equivalents, and references Windows-specific tools (PowerShell) and documentation paths. Although Linux examples are provided, Windows is prioritized in both structure and external references.
Recommendations
  • Present Linux and Windows examples side-by-side or in a neutral order, rather than Windows first.
  • Include links to both Windows and Linux documentation in prerequisites and 'Learn more' sections.
  • Clarify that the API and metadata service are OS-agnostic, and avoid referencing Windows-specific documentation paths unless equally providing Linux paths.
  • Expand troubleshooting and next steps to include Linux-specific guidance where relevant.
GitHub Create Pull Request
Load Balancer Azure Load Balancer Floating IP configuration ...in/articles/load-balancer/load-balancer-floating-ip.md
Low Priority View Details →
Scanned: 2026-01-11 06:20
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, Windows firewall) in detail. While Linux instructions are present and reasonably complete, the ordering and tool focus may create minor friction for Linux/macOS users.
Recommendations
  • Present Linux and Windows examples in parallel or alternate order, or clarify that both are equally supported.
  • Include macOS configuration instructions if relevant, or note any limitations for macOS.
  • Reference cross-platform tools where possible, or provide links to equivalent Linux/macOS documentation for advanced scenarios.
  • Explicitly state that both Windows and Linux are supported and highlight any OS-specific caveats up front.
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
Low 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 provides troubleshooting steps for Azure Load Balancer health probe failures and includes an example command for checking listening ports: 'netstat -a' for Windows is mentioned first, followed by 'netstat -l' for Linux. No Linux-specific troubleshooting links or examples are provided, while a link to troubleshooting high-CPU issues for Azure Windows VMs is included without a Linux equivalent.
Recommendations
  • Provide Linux-specific troubleshooting links, such as a guide for diagnosing high-CPU issues on Azure Linux VMs.
  • Alternate the order of example commands so Linux is not always listed second.
  • Include macOS-specific notes or commands where relevant.
  • Ensure parity in troubleshooting steps and external references for both Windows and Linux environments.
GitHub Create Pull Request
Load Balancer Quickstart: Create an internal Azure load balancer - Bicep ...er/quickstart-load-balancer-standard-internal-bicep.md
Low Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for deployment, resource review, and cleanup. However, PowerShell (a Windows-centric tool) is given equal prominence to Azure CLI, and is presented as a primary option throughout. There is no explicit mention of Linux/macOS shell environments, nor are there any Linux-specific notes or examples. The use of PowerShell may create friction for Linux/macOS users, who are more likely to use Bash or other shells.
Recommendations
  • Clarify that Azure CLI commands work natively on Linux/macOS, and provide explicit instructions for those platforms if needed.
  • Consider listing Azure CLI examples first, as it is cross-platform, and note that PowerShell is primarily for Windows users.
  • Add a note or section for Linux/macOS users, confirming that all CLI commands are supported and providing troubleshooting tips if necessary.
  • If there are any platform-specific caveats (e.g., file path formats), mention them explicitly.
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-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation demonstrates minor Windows bias in the SSH connection instructions: Windows/PowerShell users are mentioned first, and the SSH command uses Windows path syntax ('.\Downloads\lb-key-pair.pem'), which may confuse Linux/macOS users. There are no explicit Linux/macOS examples or clarifications for their file path conventions. However, the overall tutorial is platform-neutral and Linux users can complete all steps.
Recommendations
  • Present Linux/macOS instructions before or alongside Windows instructions for SSH commands.
  • Provide both Windows (PowerShell) and Linux/macOS (Bash) path syntax in SSH command examples.
  • Add a note clarifying path differences between platforms (e.g., '.\Downloads\...' for Windows, '~/Downloads/...' for Linux/macOS).
  • Consider using a generic path placeholder (e.g., <path-to-key>) and show both platform-specific examples.
GitHub Create Pull Request
← Previous Page 5 of 5 Next →