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 376-388 of 388 flagged pages
Load Balancer
Azure Load Balancer Floating IP configuration
...in/articles/load-balancer/load-balancer-floating-ip.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation presents Windows Server instructions before Ubuntu, and uses Windows-specific tools (netsh, Windows firewall) in detail. While Linux instructions are present and reasonably complete, the ordering and tool emphasis reflect a mild Windows bias.
Recommendations
- Present Linux and Windows instructions in parallel or alternate order, or clarify that both are equally supported.
- Include examples for other popular Linux distributions (e.g., CentOS, RHEL) or macOS if relevant.
- Reference Linux firewall alternatives (e.g., firewalld, iptables) alongside UFW for broader coverage.
- Add a summary table comparing steps for both platforms for quick parity review.
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 →
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-specific documentation. Windows tools (PowerShell) are referenced explicitly, while Linux uses generic curl. However, Linux examples are present and functional.
Recommendations
- Present Windows and Linux examples side-by-side or alternate which is shown first.
- Ensure prerequisite and reference links include Linux-specific documentation or use neutral landing pages.
- Mention Linux-specific troubleshooting or proxy bypassing notes where relevant.
- Clarify that both Windows and Linux are fully supported for these operations.
Load Balancer
Quickstart: Create an internal Azure load balancer - Bicep
...er/quickstart-load-balancer-standard-internal-bicep.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for deployment, resource review, and cleanup tasks. However, PowerShell examples are given equal prominence to CLI, and the PowerShell examples use Windows-centric syntax and tools. There is a slight Windows-first bias due to the inclusion of PowerShell examples, which are primarily used on Windows, and no mention of Bash or Linux/macOS-specific considerations (e.g., shell differences, file paths). However, the presence of Azure CLI examples (which work cross-platform) mitigates the impact.
Recommendations
- Explicitly state that Azure CLI commands work on Linux, macOS, and Windows, while PowerShell is primarily for Windows users.
- Add notes or tabs for Bash shell usage on Linux/macOS, especially for file path syntax and environment setup.
- Consider listing CLI examples first, as they are cross-platform.
- Mention installation instructions or prerequisites for Azure CLI and PowerShell on different operating systems.
- Clarify that PowerShell Core is available on Linux/macOS if users wish to use PowerShell there.
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 →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation shows minor Windows bias in the troubleshooting checklist. Specifically, when instructing users to check listening ports, the Windows command ('netstat -a') is mentioned before the Linux equivalent ('netstat -l'). Additionally, the link for troubleshooting high CPU issues references only Azure Windows VMs, with no mention of Linux VM troubleshooting resources.
Recommendations
- Present Linux and Windows commands in parallel, or mention Linux commands first in some sections.
- Include links to troubleshooting high-CPU issues for Azure Linux virtual machines alongside the Windows VM link.
- Ensure that troubleshooting steps and examples are equally detailed for both Windows and Linux environments.
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 →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation shows minor Windows bias in the SSH example commands: the file path for the SSH key uses Windows (backslash) syntax and PowerShell prompt notation, even though the instructions mention Bash for Mac/Linux. No Linux-specific example is given, and Windows syntax is shown first. However, the core instructions are cross-platform and do not rely on Windows-only tools.
Recommendations
- Provide both Windows (PowerShell) and Linux/macOS (Bash) SSH command examples, with correct path separators for each.
- Show Linux/macOS examples first or side-by-side to avoid implicit prioritization of Windows.
- Explicitly mention how to locate the SSH key file on Linux/macOS systems.
- Clarify that the SSH command works on all platforms, and note any platform-specific differences.
Load Balancer
Tutorial: Create Inbound NAT rule V2 - Azure portal
...ad-balancer/tutorial-nat-rule-multi-instance-portal.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation shows minor Windows bias in the SSH connection instructions: it mentions Windows/PowerShell before Linux/Mac, and the SSH command uses Windows path syntax ('.\Downloads\myKey.pem') in the example. However, Linux/Mac users are acknowledged, and the commands themselves are cross-platform. No critical steps are Windows-only, and Linux users can complete the tutorial without friction.
Recommendations
- Present Linux/Mac instructions before or alongside Windows instructions, rather than after.
- Provide both Windows and Linux/Mac path syntax in SSH examples (e.g., './Downloads/myKey.pem' for Linux/Mac, '.\Downloads\myKey.pem' for Windows).
- Explicitly state which commands/examples are for which OS, or provide OS-specific tabs/sections.
- Ensure all command-line examples use syntax compatible with both platforms, or clarify differences.
Load Balancer
What's new in Azure Load Balancer
...ure-docs/blob/main/articles/load-balancer/whats-new.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation page contains subtle evidence of Windows bias. Notably, the example link for creating a dual stack application points to a PowerShell-based guide, which is typically Windows-centric. The reference to PowerShell appears before any mention of Linux or cross-platform CLI alternatives. No Linux/macOS-specific tools, examples, or parity guidance are provided, and there is no explicit mention of Bash, Azure CLI, or Linux workflows in the recent features or examples. However, the page is mostly conceptual and does not contain detailed step-by-step instructions, so the impact is limited.
Recommendations
- Add links to Linux/macOS equivalent guides, such as using Azure CLI or Bash scripts for common tasks.
- Ensure that example links (e.g., for dual stack application creation) include both PowerShell and Azure CLI/Bash options, or clarify cross-platform compatibility.
- Explicitly mention that features and management tasks can be performed from Linux/macOS environments and provide relevant documentation.
- Where PowerShell is referenced, also provide Azure CLI commands or Bash script examples.
Load Balancer
Retrieve metrics with the Azure REST API
.../load-balancer/load-balancer-query-metrics-rest-api.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation provides a generic REST API example for retrieving Azure Load Balancer metrics but does not include any platform-specific instructions or examples. However, it references the Azure CLI for managing subscriptions, which is cross-platform, and avoids mentioning Windows-specific tools or patterns. The page lacks concrete examples of how to make the REST API call using common tools available on Linux (such as curl or wget), and does not provide sample scripts for either Windows (PowerShell) or Linux (bash).
Recommendations
- Add example commands using curl (Linux/macOS) to demonstrate how to make the REST API call.
- Include sample scripts for both bash (Linux/macOS) and PowerShell (Windows) to show parity.
- Explicitly mention that the REST API can be accessed from any platform and provide links to platform-agnostic tooling.
- If referencing Azure CLI, clarify its cross-platform nature and provide installation instructions for Linux.
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation page describes inbound NAT rules for Azure Load Balancer in a platform-neutral manner, but it lacks any examples or references to operating system-specific tools or commands. There are no Windows/Powershell examples, nor are there Linux equivalents. However, the absence of any Linux-specific guidance or examples (such as using SSH, iptables, or Linux CLI tools) means Linux parity is not addressed, which could disadvantage Linux administrators seeking practical implementation details.
Recommendations
- Add examples showing how to use inbound NAT rules to connect to Linux virtual machines, such as SSH port forwarding scenarios.
- Include references to Linux tools (e.g., ssh, netcat, iptables) for verifying or troubleshooting NAT rule functionality.
- Provide step-by-step guides for both Windows (RDP) and Linux (SSH) connection scenarios using inbound NAT rules.
- Ensure that any portal screenshots or walkthroughs mention both Windows and Linux VM use cases where relevant.
Load Balancer
Retrieve metrics with the Azure REST API
.../load-balancer/load-balancer-query-metrics-rest-api.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation provides a generic REST API example for retrieving Azure Load Balancer metrics but does not include any platform-specific usage examples. There are no PowerShell, Windows command-line, or Linux shell (curl, bash) examples. However, the only CLI reference is to Azure CLI, which is cross-platform, and there are no explicit Windows tools or patterns. The main bias is the lack of concrete examples for Linux users (e.g., curl or bash), which may make it less accessible for those not using Windows.
Recommendations
- Add example requests using curl or wget to demonstrate how Linux/macOS users can interact with the API.
- Include sample authentication flows for Linux environments (e.g., using Azure CLI to obtain a bearer token and passing it to curl).
- Ensure that any references to CLI tools clarify their cross-platform availability.
- If PowerShell or Windows examples are added in future, provide equivalent bash/curl examples for parity.
Load Balancer
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/inbound-nat-rules.md
.../blob/main/articles/load-balancer/inbound-nat-rules.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation page describes inbound NAT rules for Azure Load Balancer in a platform-neutral manner, but it lacks any examples or references to operating system-specific tools or commands. There is no mention of Windows, PowerShell, Linux, or Bash, nor are there examples showing how to connect to backend VMs using either Windows or Linux clients. However, the absence of Linux-specific guidance or parity in examples (such as SSH port forwarding or Linux command-line usage) constitutes a subtle bias by omission.
Recommendations
- Add examples showing how to connect to backend VMs using both Windows (e.g., RDP) and Linux (e.g., SSH) clients.
- Include references to Linux tools (such as ssh, netcat, or iptables) when discussing port forwarding scenarios.
- Provide step-by-step instructions or screenshots for both Windows and Linux users in tutorials, especially in sections about retrieving port mappings and connecting to VMs.
- Explicitly mention that inbound NAT rules can be used for both RDP (Windows) and SSH (Linux) scenarios, and link to relevant documentation for each.
Load Balancer
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/load-balancer-query-metrics-rest-api.md
.../load-balancer/load-balancer-query-metrics-rest-api.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation provides a generic REST API example for retrieving Azure Load Balancer metrics, but does not include any platform-specific instructions or examples. However, it references the Azure CLI for managing subscriptions, which is cross-platform, and does not mention Windows-specific tools, PowerShell, or provide Windows-first examples. The main bias is the lack of explicit Linux (e.g., curl, bash) or cross-platform command-line examples for making the REST API call.
Recommendations
- Add example commands using curl (Linux/macOS) to demonstrate how to make the REST API call from a Linux shell.
- Include sample scripts for both PowerShell and bash to show parity.
- Explicitly mention that the REST API can be accessed from any platform and provide guidance for common tools on Linux and macOS.
- If referencing Azure CLI, clarify its cross-platform nature and provide example usage for both Windows and Linux environments.
Load Balancer
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/load-balancer-query-metrics-rest-api.md
.../load-balancer/load-balancer-query-metrics-rest-api.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation provides a REST API example for retrieving Azure Load Balancer metrics, but does not include any platform-specific instructions or examples. However, it references the Azure CLI for managing subscriptions, which is cross-platform. There are no Windows-specific tools, PowerShell examples, or Windows-first patterns. The main bias is the absence of concrete examples showing how to make the REST API call from either Windows (e.g., PowerShell, curl in CMD) or Linux (e.g., curl, wget, bash), which may leave Linux users without clear guidance.
Recommendations
- Add example commands for making the REST API call using curl or wget in a Linux shell.
- If including platform-specific instructions, ensure parity by providing both PowerShell (Windows) and bash/curl (Linux) examples.
- Explicitly mention that the API can be accessed from any platform and provide links to cross-platform tools.