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 276-300 of 388 flagged pages
Load Balancer
Outbound-only load balancer configuration
...e-docs/blob/main/articles/load-balancer/egress-only.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates bias towards Windows by exclusively providing VM creation instructions for Windows Server 2022, with no mention of Linux images or Linux-specific configuration steps. All examples and walkthroughs assume a Windows VM, including the use of Microsoft Edge for connectivity testing, and do not offer Linux alternatives or parity in guidance.
Recommendations
- Add parallel instructions for creating a Linux VM (e.g., Ubuntu, CentOS) in the 'Create virtual machine' section, including appropriate image selection and authentication methods (SSH keys).
- Include Linux-specific steps for connectivity testing, such as using Firefox or curl/wget from the command line, instead of only referencing Microsoft Edge.
- Explicitly mention that the configuration applies to both Windows and Linux VMs, and provide guidance for both where steps differ (e.g., OS-specific firewall settings, browser usage, authentication).
- Where administrator credentials are referenced, offer Linux-appropriate options (e.g., SSH username/key) alongside Windows username/password.
- Review all sections for implicit Windows assumptions and update language and examples to ensure Linux parity.
Create Pull Request
Load Balancer
What is Azure Load Balancer?
.../main/articles/load-balancer/load-balancer-overview.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page for Azure Load Balancer does not provide any platform-specific examples, but it does show subtle Windows bias. All referenced quickstarts, tutorials, and advanced features link to guides that use the Azure Portal or, in the case of IPv6 support, specifically mention PowerShell in the URL (which is most commonly associated with Windows). There is no mention of Linux-specific tools (such as Azure CLI or Bash), nor are Linux administration patterns or examples provided. Windows-centric terminology (PowerShell) appears before any Linux equivalents, and Linux command-line usage is absent.
Recommendations
- Add equivalent Linux examples using Azure CLI or Bash scripts alongside or before PowerShell examples.
- Ensure that advanced feature guides (e.g., IPv6 support) include both PowerShell and Azure CLI instructions.
- Reference Linux administration patterns and tools where relevant, such as iptables, netcat, or curl for health probe testing.
- Explicitly mention cross-platform compatibility and provide links to Linux-focused quickstarts and tutorials.
- Review all linked guides to ensure Linux parity in walkthroughs and screenshots.
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Summary
The documentation page describes Azure Load Balancer inbound NAT rules in a platform-neutral way, but it implicitly favors Windows by omitting any mention of Linux-specific tools, patterns, or examples. The only references to accessing virtual machines are generic, and there is no guidance or examples for Linux administrators (e.g., using SSH, Linux CLI tools, or Linux port forwarding patterns). The tutorials and instructions are portal-focused and do not provide parity for Linux command-line workflows, which are common in cross-platform environments.
Recommendations
- Add explicit examples for Linux scenarios, such as SSH port forwarding to Linux VMs using inbound NAT rules.
- Include CLI-based instructions using Azure CLI or PowerShell, and ensure both Windows and Linux command-line workflows are covered.
- Mention common Linux tools (e.g., ssh, netcat) when discussing port forwarding and connectivity.
- Provide links to Linux-specific documentation or tutorials for managing inbound NAT rules and accessing VMs.
- Ensure that any screenshots or walkthroughs show both Windows and Linux VM use cases where applicable.
Load Balancer
Create a global load balancer with cross-subscription backends
...d-balancer/cross-subscription-how-to-global-backend.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation page demonstrates a moderate Windows bias. Azure PowerShell (commonly used on Windows) is presented before Azure CLI in every section, with more detailed explanations and code samples. The prerequisites and instructions for PowerShell are more elaborate, and the page metadata references Azure PowerShell specifically. There is no mention of Linux-specific tools, shell environments, or considerations, and PowerShell is implicitly treated as the default or primary approach.
Recommendations
- Alternate the order of examples so that Azure CLI instructions appear first in some sections.
- Provide equal detail and explanation for Azure CLI steps as for PowerShell.
- Add explicit notes about running Azure CLI on Linux/macOS, including shell compatibility and installation instructions.
- Include references to Bash scripting or Linux terminal usage where appropriate.
- Avoid metadata or custom tags that imply PowerShell is the default (e.g., ms.custom: devx-track-azurepowershell).
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 →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation demonstrates subtle Windows bias in the SSH connection instructions. It mentions Windows and PowerShell before Mac/Linux and Bash, and the SSH command example uses Windows path syntax (backslashes) and PowerShell conventions. No explicit Linux example is provided for the SSH command, and Windows terminology appears first in the instructions.
Recommendations
- Present Mac/Linux and Windows instructions in parallel, or list Mac/Linux first to balance representation.
- Provide separate SSH command examples for Bash (Linux/Mac) and PowerShell (Windows), using appropriate path syntax (e.g., './Downloads/lb-key-pair.pem' for Linux/Mac, '.\Downloads\lb-key-pair.pem' for Windows).
- Clarify which OS each command example is for, possibly using tabs or callouts.
- Avoid defaulting to Windows terminology or tools unless the majority of users are on Windows; otherwise, strive for equal coverage.
- Consider including screenshots or step-by-step instructions for both Bash and PowerShell environments.
Load Balancer
What's new in Azure Load Balancer
...ure-docs/blob/main/articles/load-balancer/whats-new.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates subtle Windows bias. The only explicit example reference is in the IPv6 support feature, which links to a Powershell-based guide for creating a dual stack application, without mentioning or linking to Linux/CLI alternatives. No Linux-specific tools, commands, or examples are provided, and Powershell/Windows patterns are referenced first or exclusively where examples are given.
Recommendations
- Wherever examples are referenced (e.g., dual stack application creation), provide both Windows/Powershell and Linux/Azure CLI/Bash alternatives, or link to equivalent Linux documentation.
- Ensure that documentation links and guides do not default to Windows tools (such as Powershell) unless Linux/CLI options are equally visible and accessible.
- Add explicit Linux/Azure CLI examples for common operations (e.g., configuring Load Balancer, managing backend pools, testing reachability) alongside any Powershell/Windows examples.
- Review linked guides and ensure parity in step-by-step instructions for both platforms.
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 →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation presents Azure PowerShell (Windows-centric) 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, potentially making Linux users feel secondary or less supported.
Recommendations
- Present Azure CLI (cross-platform) examples before or alongside PowerShell examples to avoid implying Windows is the primary platform.
- Ensure both Azure CLI and PowerShell sections have equivalent detail and coverage, including step-by-step resource creation and configuration.
- Explicitly mention that Azure CLI works on Linux, macOS, and Windows, and provide links to installation guides for all platforms.
- If any step requires platform-specific tools, note alternatives for Linux (e.g., Bash scripts, native Linux tools) and provide parity in instructions.
- Review included content ([!INCLUDE]) to confirm that referenced steps and prerequisites do not assume Windows or PowerShell usage.
Load Balancer
Create a cross-subscription internal load balancer
...er/cross-subscription-how-to-internal-load-balancer.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation page demonstrates a moderate Windows bias. The primary example for creating a cross-subscription internal load balancer is given first in Azure PowerShell, which is more commonly used on Windows. The PowerShell example is more detailed and step-by-step, while the Azure CLI example is shorter and less comprehensive. There are no Linux-specific tools or patterns mentioned, and the CLI example does not reference Linux explicitly, but the ordering and depth favor Windows/PowerShell users.
Recommendations
- Provide equally detailed Azure CLI examples, including step-by-step breakdowns matching the PowerShell coverage.
- Explicitly mention that Azure CLI is cross-platform and can be used on Linux, macOS, and Windows.
- Consider adding Bash script examples for Linux users, especially for automation scenarios.
- If possible, include a note or section on using the Azure portal for users who prefer a GUI, which is platform-agnostic.
- Ensure that any referenced tools or commands are available and documented for Linux environments.
Load Balancer
Outbound-only load balancer configuration
...e-docs/blob/main/articles/load-balancer/egress-only.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates bias toward Windows by exclusively providing instructions for deploying a Windows Server VM (specifically 'Windows Server 2022 Datacenter: Azure Edition - Gen2') and referencing Microsoft Edge for connectivity tests. There are no examples or guidance for deploying a Linux VM, nor are Linux-specific tools or browsers mentioned. This may lead Linux users to feel unsupported or unclear about how to follow the steps with their preferred OS.
Recommendations
- Include parallel instructions and screenshots for deploying a Linux VM (e.g., Ubuntu, CentOS) alongside the Windows VM example.
- In connectivity test sections, mention Linux browsers (e.g., Firefox, Chromium) and provide equivalent steps for Linux environments.
- Clarify that the load balancer configuration applies to both Windows and Linux VMs, and highlight any OS-specific considerations.
- Where administrator credentials are referenced, note differences in authentication methods (e.g., SSH keys for Linux, passwords for Windows).
- Provide sample commands for connectivity tests using Linux CLI tools (e.g., curl, wget) in addition to browser-based tests.
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 →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation page demonstrates a mild Windows bias: Windows/PowerShell examples and links are presented before Linux equivalents, and references to Windows-specific tools (PowerShell, -NoProxy parameter) are more detailed. The prerequisites and important notes link to Windows-centric documentation first, and troubleshooting/learning links default to Windows tabs.
Recommendations
- Present Linux and Windows examples side-by-side or alternate their order to avoid Windows-first bias.
- Ensure all links to further documentation use neutral or Linux-inclusive tabs, not defaulting to Windows.
- Expand Linux-specific notes, such as proxy bypassing with curl, to match the detail given for Windows/PowerShell.
- Reference both Linux and Windows documentation in prerequisites and troubleshooting sections.
- Where Windows-specific tooling is mentioned (e.g., PowerShell -NoProxy), provide equivalent Linux command explanations.
Load Balancer
Azure Load Balancer Floating IP configuration
...in/articles/load-balancer/load-balancer-floating-ip.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation presents Windows Server instructions before Ubuntu/Linux, and references Windows-specific tools and configuration patterns (e.g., Always On availability group listener with PowerShell). Windows command-line tools (netsh, advfirewall) are detailed, and the example scenario links to a Windows-specific guide. Linux instructions are present but less emphasized, and alternative Linux distributions or firewall tools are not discussed.
Recommendations
- Alternate the order of Windows and Linux sections, or present them side-by-side for parity.
- Include references and links to Linux-based configuration patterns (e.g., for clustering or high availability) alongside Windows equivalents.
- Expand Linux instructions to mention other distributions (e.g., CentOS, RHEL) and common firewall tools (e.g., firewalld, iptables) in addition to UFW.
- Provide example links for Linux-based Always On availability group listener or similar high-availability configurations.
- Ensure terminology and examples are balanced between Windows and Linux, avoiding Windows-centric language or scenarios.
Load Balancer
What is Azure Load Balancer?
.../main/articles/load-balancer/load-balancer-overview.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page for Azure Load Balancer does not provide any platform-specific examples, but there is evidence of subtle Windows bias. References to virtual machines (VMs) and network security groups (NSGs) are generic, but links to advanced features (such as IPv6 support) point to PowerShell-based guides, which are typically Windows-centric. There are no explicit Linux command-line examples (e.g., Bash, CLI), nor are Linux tools or patterns mentioned. The documentation does not clarify cross-platform management options or provide parity for Linux administrators.
Recommendations
- Include examples using Azure CLI and Bash scripts alongside PowerShell, especially in advanced feature guides.
- Explicitly mention that Azure Load Balancer can be managed from both Windows and Linux environments.
- Provide links to Linux-specific tutorials or documentation where available.
- Ensure that platform-agnostic tools (such as Azure CLI) are referenced before or alongside PowerShell in all relevant sections.
- Add a section or note highlighting cross-platform support and management options for Azure Load Balancer.
Load Balancer
Load Balancer TCP Reset and idle timeout in Azure
...main/articles/load-balancer/load-balancer-tcp-reset.md
Medium Priority
View Details →
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 describing error messages typical of Windows environments. There are no Linux-specific examples, tools, or error messages provided, and the only code reference is to .NET, which is primarily associated with Windows. No mention is made of Linux utilities or configuration methods (such as sysctl, iptables, or socket options in Python or C), nor are Linux error messages or troubleshooting steps discussed.
Recommendations
- Add Linux-specific examples for configuring TCP keep-alive, such as sysctl settings or socket options in Python/C.
- Include references to Linux error messages that may occur when connections are closed due to idle timeout.
- Provide parity by mentioning cross-platform tools and methods, such as using netcat, socat, or iptables for connection management.
- Where .NET examples are given, also provide equivalent examples for popular Linux programming environments (e.g., Python, Java, C).
- Explicitly state that the guidance applies to both Windows and Linux endpoints, and clarify any platform-specific differences.
Load Balancer
Manage Administrative State in Azure Load Balancer
...in/articles/load-balancer/manage-admin-state-how-to.md
Medium Priority
View Details →
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 example links or instructions, and the resource creation steps are Windows-centric. While Azure CLI and PowerShell are both covered, the examples and references for VM creation and management are exclusively Windows-focused, omitting Linux parity.
Recommendations
- Add explicit Linux VM creation links and instructions in the prerequisites for each method (portal, PowerShell, CLI), such as '/azure/virtual-machines/linux/quick-create-portal', '/azure/virtual-machines/linux/quick-create-powershell', and '/azure/virtual-machines/linux/quick-create-cli'.
- Include Linux VM examples alongside Windows VM examples in all relevant sections, showing both OS types in resource creation and management steps.
- Clarify that the admin state feature and commands apply equally to Linux and Windows backend pool instances.
- Where possible, provide sample commands or screenshots for Linux VM scenarios, especially in CLI sections.
- Ensure terminology and instructions do not assume Windows as the default platform for backend pool instances.
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure PowerShell and Azure CLI examples for creating diagnostic settings, but PowerShell (typically associated with Windows) is presented first and in more detail, with multiple scenarios (Log Analytics, Storage Account, Event Hub) and explicit variable usage. The CLI examples follow and are functionally equivalent, but the ordering and depth may suggest a Windows-first approach. There are no Linux-specific tools, shell, or OS references, nor are there examples using Bash, scripting, or Linux-native patterns. No explicit Windows-only tools are mentioned, but the PowerShell emphasis and ordering could be interpreted as a subtle bias.
Recommendations
- Alternate the order of PowerShell and Azure CLI examples, or present CLI first to better reflect cross-platform usage.
- Explicitly mention that Azure CLI works natively on Linux, macOS, and Windows, and provide Bash script examples where appropriate.
- Add a note clarifying that PowerShell Core is cross-platform, but Azure CLI is often preferred on Linux systems.
- Include links or references to Linux-specific guidance or troubleshooting for Azure Load Balancer monitoring.
- Ensure parity in example depth and clarity between PowerShell and CLI sections.
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 →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The tutorial demonstrates a Windows bias by exclusively using Windows Server as the VM image in the scale set creation steps, with no mention of Linux alternatives. All example values and instructions assume a Windows environment, and there are no Linux-specific notes, examples, or parity checks. The documentation does not provide guidance for users who may wish to deploy Linux-based scale sets, nor does it mention Linux administrator account patterns or OS-specific considerations.
Recommendations
- Include Linux as an alternative VM image in the scale set creation steps, e.g., Ubuntu, CentOS, etc.
- Provide guidance on Linux administrator account setup (e.g., SSH key authentication, username conventions).
- Add notes or examples highlighting differences in configuration or management for Linux-based scale sets.
- Ensure that all instructions and screenshots are OS-neutral or provide both Windows and Linux variants.
- Explicitly mention that the tutorial is applicable to both Windows and Linux VM scale sets, and link to relevant Linux documentation.
Load Balancer
Common error codes for Azure Instance Metadata Service (IMDS)
...icles/load-balancer/troubleshoot-load-balancer-imds.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page consistently links to Windows-specific Azure Instance Metadata Service (IMDS) documentation, and does not mention or provide Linux-specific examples, links, or guidance. All references to further information use Windows documentation tabs, and there is no parity for Linux users.
Recommendations
- Include links to both Windows and Linux versions of the Azure Instance Metadata Service documentation, or use neutral links that allow users to select their OS.
- Add Linux-specific examples or troubleshooting guidance where relevant, especially for common error codes.
- Ensure that references to supported HTTP verbs, rate limiting, and other IMDS features are not exclusively tied to Windows documentation.
- Review and update cross-references to ensure Linux users can easily find equivalent information.
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 →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation shows mild Windows bias in troubleshooting steps. For example, when instructing users to check listening ports, the Windows command ('netstat -a') is mentioned first, with the Linux equivalent ('netstat -l') mentioned second. Additionally, the link for troubleshooting high CPU issues points only to Azure Windows VM documentation, with no equivalent for Linux VMs. There are no PowerShell-heavy sections or exclusive use of Windows tools, but Linux parity is lacking in some troubleshooting guidance.
Recommendations
- Provide links to equivalent Linux VM troubleshooting guides, especially for high CPU issues.
- When listing OS-specific commands, alternate the order or present both Windows and Linux commands together, possibly in a table.
- Include examples for common Linux troubleshooting tools (e.g., top, systemctl, journalctl) where relevant.
- Explicitly mention that instructions apply to both Windows and Linux VMs, and clarify any OS-specific differences in probe configuration or firewall rules.
Load Balancer
Tutorial: Configure outbound connectivity with a gateway load balancer
...oad-balancer/tutorial-gateway-outbound-connectivity.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates Windows bias by referencing only Windows virtual machine deployment in the prerequisites and not providing equivalent Linux VM guidance or examples. All instructions assume a generic VM but link only to Windows VM creation, omitting Linux-specific considerations or examples.
Recommendations
- Include links and instructions for creating a Linux VM in Azure alongside the Windows VM reference.
- Explicitly mention that the tutorial applies to both Windows and Linux VMs, and provide examples or notes for Linux users where relevant.
- Where VM configuration steps may differ between Windows and Linux (e.g., networking, IP configuration), clarify any differences or provide parallel guidance.
- Ensure that future tutorials provide parity in examples and references for both operating systems to avoid implicit platform bias.
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 →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The tutorial demonstrates load balancing VMs using the Azure portal and includes steps to create a basic Internet Information Services (IIS) site for testing. IIS is a Windows-only web server, and there are no instructions or examples for deploying or testing with a Linux-based web server (such as Apache or Nginx). This indicates a bias toward Windows environments and tools, with Linux alternatives missing from the documentation.
Recommendations
- Include parallel instructions for deploying and testing with a Linux-based web server (e.g., Apache or Nginx) alongside the IIS example.
- Explicitly mention that IIS is a Windows-only option and provide guidance for users who wish to use Linux VMs.
- Add screenshots or command examples for Linux VM setup and web server installation to ensure parity.
- Clarify in the prerequisites or introduction that the tutorial is applicable to both Windows and Linux VMs, and link to relevant Linux documentation if available.
Load Balancer
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/concepts.md
...zure-docs/blob/main/articles/load-balancer/concepts.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates subtle Windows bias by referencing the creation of VMs with a custom IIS extension installed in its 'Next steps' section. IIS is a Windows-specific web server, and there are no equivalent Linux examples (such as Apache or Nginx) provided. The documentation does not mention Linux tools or patterns, nor does it provide parity in examples for Linux users.
Recommendations
- Include examples for Linux-based web servers (e.g., Apache, Nginx) alongside IIS when demonstrating load balancing scenarios.
- Explicitly mention that Azure Load Balancer supports both Windows and Linux VMs, and provide links to quickstarts or tutorials for both platforms.
- When referencing extensions or application scenarios, offer both Windows and Linux options to ensure cross-platform parity.
- Review and update documentation to avoid implicit prioritization of Windows tools or patterns, especially in introductory or 'getting started' sections.
Load Balancer
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/cross-subscription-how-to-internal-load-balancer.md
...er/cross-subscription-how-to-internal-load-balancer.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation presents Azure PowerShell examples first and in greater detail, with step-by-step cmdlets and variable usage. The Azure CLI example is provided second, is less detailed, and lacks parity in explanation and context. There are no Linux-specific tools or shell examples (e.g., Bash scripting), and the PowerShell focus may disadvantage Linux users, as PowerShell is primarily associated with Windows environments.
Recommendations
- Present Azure CLI examples before or alongside PowerShell examples to avoid Windows-first ordering.
- Ensure CLI examples are as detailed and comprehensive as PowerShell examples, including variable usage and step-by-step breakdowns.
- Add Bash script examples for Linux users, especially for multi-step operations.
- Explicitly mention cross-platform compatibility for both CLI and PowerShell, and clarify prerequisites for running PowerShell on Linux.
- Include troubleshooting or environment setup notes for Linux users (e.g., installing Azure CLI, running PowerShell Core on Linux).
Load Balancer
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/howto-load-balancer-imds.md
...ain/articles/load-balancer/howto-load-balancer-imds.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation page demonstrates a Windows bias by presenting Windows/Powershell examples and links before Linux equivalents. The prerequisites and important notes reference Windows-specific documentation and tools (PowerShell, -NoProxy), with Linux examples provided only after Windows. References to further reading and troubleshooting also default to Windows documentation tabs.
Recommendations
- Present Windows and Linux examples side-by-side or in parallel, rather than listing Windows first.
- Ensure all prerequisite and reference links include both Windows and Linux tabs, or link to a neutral landing page.
- Add Linux-specific notes where relevant (e.g., proxy bypassing in curl) and avoid assuming PowerShell as the default tool.
- Review troubleshooting and 'next steps' links to ensure Linux parity and visibility.
- Consider a platform-neutral introduction and summary, emphasizing cross-platform applicability.
Load Balancer
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/load-balancer-floating-ip.md
...in/articles/load-balancer/load-balancer-floating-ip.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation presents Windows Server instructions before Ubuntu/Linux, and the only detailed scenario link provided is for Windows (Always On availability group listener with PowerShell). Windows-specific tools (netsh, advfirewall) are described in detail, while Linux instructions are less extensive and only cover Ubuntu with UFW. There is no mention of other Linux distributions or firewalls, and the advanced scenario documentation is Windows-only.
Recommendations
- Alternate the order of Windows and Linux instructions, or present them side-by-side to avoid Windows-first bias.
- Provide equivalent advanced scenario documentation 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 firewalls (e.g., firewalld, iptables).
- Include links to Linux-specific documentation and tools where appropriate.
- Clarify that the steps apply to both platforms and highlight any platform-specific differences.
Load Balancer
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/load-balancer-tcp-reset.md
...main/articles/load-balancer/load-balancer-tcp-reset.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a bias towards Windows by referencing .NET examples for TCP keep-alive configuration and omitting equivalent Linux or cross-platform examples. There are no command-line or configuration examples for Linux environments, and the only code reference is specific to the Windows/.NET ecosystem.
Recommendations
- Include Linux-specific examples for configuring TCP keep-alive, such as using sysctl or editing /etc/sysctl.conf.
- Provide cross-platform code samples (e.g., Python, Java) for setting TCP keep-alive options.
- Mention relevant Linux tools (e.g., netstat, ss, tcpdump) for monitoring TCP resets and idle timeouts.
- Balance references to .NET with equivalent documentation for Linux and open-source stacks.
- Explicitly state that the guidance applies to both Windows and Linux endpoints, and clarify any platform-specific differences.