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 176-200 of 388 flagged pages
Load Balancer
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/load-balancer-multiple-ip.md
...in/articles/load-balancer/load-balancer-multiple-ip.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation demonstrates a Windows bias by specifying the creation of Windows server virtual machines and configuring IIS websites, with no mention of Linux VMs or web servers. The steps and examples focus on Windows tools (IIS, PowerShell) and do not provide Linux equivalents or alternatives. The structure and content prioritize Windows scenarios, omitting guidance for Linux users.
Recommendations
- Add parallel instructions for creating and configuring Linux virtual machines (e.g., Ubuntu, CentOS) alongside Windows VMs.
- Include examples for setting up web servers on Linux (such as Apache or Nginx) and binding them to multiple IP configurations.
- Provide Azure CLI and Bash script examples for Linux environments, not just PowerShell.
- Explicitly mention Linux support in the tutorial introduction and checklist.
- Ensure that all steps (NIC configuration, website setup, testing) have Linux-specific guidance and screenshots where applicable.
Create Pull Request
Load Balancer
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/deploy-ipv4-ipv6-dual-stack-standard-load-balancer.md
...https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/deploy-ipv4-ipv6-dual-stack-standard-load-balancer.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a Windows bias by exclusively providing examples for deploying Windows Server virtual machines (VMs) and using RDP (Remote Desktop Protocol) for access. There are no examples or guidance for deploying Linux VMs, nor for accessing VMs via SSH, which is the standard for Linux. All VM creation commands specify Windows images, and network security group rules focus on RDP (port 3389) rather than SSH (port 22).
Recommendations
- Add parallel examples for deploying Linux VMs (e.g., using Ubuntu or CentOS images) in both Azure CLI and PowerShell sections.
- Include network security group rules for SSH (port 22) alongside or instead of RDP (port 3389) to support Linux VM access.
- Demonstrate how to connect to Linux VMs using SSH, including public key authentication setup.
- In all code samples, show both Windows and Linux image options for VM creation.
- Where possible, use neutral language and examples that apply to both Windows and Linux, or clearly separate instructions for each platform.
- In the 'Determine IP addresses' section, provide examples of connecting to Linux VMs via SSH using the retrieved IP addresses.
Load Balancer
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/load-balancer-test-frontend-reachability.md
...d-balancer/load-balancer-test-frontend-reachability.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Windows Heavy Examples
Summary
The documentation consistently presents Windows examples and workflows before Linux equivalents, both for external devices and Azure VMs. It references Windows-specific tools (e.g., Command Prompt, 'tracert') and provides more detailed instructions for Windows (e.g., using the Search taskbar to open cmd). The prerequisite section links only to creating a Windows VM, omitting a Linux VM quickstart. While Linux instructions are present, they are generally less detailed and always follow Windows instructions.
Recommendations
- Alternate the order of Windows and Linux instructions in each section, or present them side-by-side to avoid Windows-first bias.
- In the prerequisites, provide links to both Windows and Linux VM creation guides.
- Ensure parity in the level of detail for both Windows and Linux instructions (e.g., explain how to open a terminal in Linux as thoroughly as for Windows).
- When referencing tools, mention both Windows and Linux equivalents together (e.g., 'tracert (Windows) or traceroute (Linux)').
- Consider using neutral language and headings, such as 'On Windows' and 'On Linux', rather than always leading with Windows.
- Where possible, provide generic instructions first, then platform-specific details.
Load Balancer
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/load-balancer-nat-pool-migration.md
...cles/load-balancer/load-balancer-nat-pool-migration.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by providing extensive PowerShell-based instructions and automation, referencing Windows-specific tools and modules, and omitting Linux-specific guidance. PowerShell is featured heavily, including for automation and module installation, with no mention of Bash scripting, Cloud Shell, or Linux-native automation. Prerequisites and upgrade steps reference PowerShell and its modules exclusively. While Azure CLI examples are present, there are no Linux shell or cross-platform scripting examples, and PowerShell is often mentioned first or exclusively for advanced scenarios.
Recommendations
- Provide equivalent Bash or shell script automation for migration tasks, especially for Virtual Machine Scale Set automation.
- Reference Azure CLI and cross-platform tools first or alongside PowerShell in all sections, including prerequisites and automation.
- Include instructions for installing and using Azure CLI and relevant extensions on Linux/macOS.
- Offer guidance for Linux users on how to perform module-based automation, or clarify if certain modules are Windows-only.
- Mention and demonstrate use of Azure Cloud Shell, which supports both Bash and PowerShell, to encourage platform-neutral approaches.
- Ensure that all advanced automation steps have CLI or REST API equivalents, and document them.
Load Balancer
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/load-balancer-troubleshoot-health-probe-status.md
...ncer/load-balancer-troubleshoot-health-probe-status.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by prioritizing Windows tools (PsPing, TCPing, netstat, netsh) and command prompt instructions, with Linux equivalents either mentioned secondarily or omitted. Troubleshooting steps and examples are predominantly Windows-centric, with Linux commands only briefly referenced and lacking parity in detail or tool recommendations.
Recommendations
- Provide Linux-first or parallel Linux examples alongside Windows instructions for all troubleshooting steps.
- Include Linux-native tools (e.g., ss, nc, lsof, firewalld, ufw) for port and firewall checks, not just netstat and iptables.
- Offer explicit Linux command-line examples for connectivity testing (e.g., using nc or curl for probe testing), not just mention Windows tools like PsPing and TCPing.
- Ensure all tool recommendations (e.g., for packet tracing or firewall inspection) have both Windows and Linux alternatives, with equal detail and example usage.
- Structure troubleshooting steps so that Windows and Linux instructions are presented together, rather than Windows first or exclusively.
Load Balancer
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/load-balancer-tcp-idle-timeout.md
...ticles/load-balancer/load-balancer-tcp-idle-timeout.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation page demonstrates a Windows bias by providing detailed PowerShell instructions and environment validation steps before mentioning Azure CLI, which is cross-platform. The PowerShell section is more elaborate and assumes familiarity with Windows tools, while Linux-specific considerations or examples are absent. The order of presentation (Portal, PowerShell, then CLI) also subtly prioritizes Windows-centric approaches.
Recommendations
- Add explicit Linux/macOS instructions or notes, especially for Azure CLI usage (e.g., mention using Bash or zsh).
- Balance the detail level between PowerShell and CLI sections; ensure CLI examples are as comprehensive as PowerShell ones.
- Consider presenting Azure CLI before PowerShell to emphasize cross-platform parity.
- Include troubleshooting or environment validation steps relevant to Linux/macOS users (e.g., how to install Azure CLI on Ubuntu, how to check CLI version in Bash).
- If referencing PowerShell, mention that PowerShell Core is available cross-platform, or provide Bash equivalents where possible.
Load Balancer
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/load-balancer-troubleshoot.md
...n/articles/load-balancer/load-balancer-troubleshoot.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates Windows bias by exclusively referencing Windows-native tools (e.g., Netsh, PsPing) and omitting Linux equivalents for network troubleshooting. There are no Linux command examples or mentions of common Linux utilities for network diagnostics.
Recommendations
- Provide equivalent Linux command examples alongside Windows tools (e.g., use tcpdump or tshark instead of Netsh, and nc or nmap instead of PsPing).
- Explicitly mention both Windows and Linux troubleshooting workflows where relevant.
- Add a section or callout for Linux users, listing commands and steps for capturing network traces and testing connectivity.
- Ensure parity in tool recommendations and troubleshooting steps for both platforms.
Load Balancer
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/quickstart-load-balancer-standard-internal-bicep.md
...er/quickstart-load-balancer-standard-internal-bicep.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for deployment, resource review, and cleanup. However, PowerShell is featured equally alongside CLI, and there are no explicit Linux shell (bash) or macOS-specific instructions or examples. The PowerShell examples and references may implicitly favor Windows users, and the lack of explicit Linux/macOS shell guidance or troubleshooting tips could disadvantage non-Windows users.
Recommendations
- Clarify that Azure CLI commands work cross-platform (Windows, Linux, macOS) and recommend it as the default for non-Windows users.
- Add explicit bash/zsh shell examples or notes for Linux/macOS users, especially for common tasks like file path syntax or environment variable usage.
- Consider reordering sections to present Azure CLI (cross-platform) examples before PowerShell, or clearly indicate CLI as the primary, platform-agnostic method.
- Include troubleshooting notes or links for common issues encountered on Linux/macOS (e.g., file permissions, CLI installation).
- Mention that PowerShell Core is available cross-platform, if PowerShell is to be retained, and provide installation guidance for non-Windows environments.
Load Balancer
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/manage-inbound-nat-rules.md
...ain/articles/load-balancer/manage-inbound-nat-rules.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation demonstrates a moderate Windows bias. PowerShell is presented as a primary automation method alongside the Azure CLI, and the prerequisites section provides detailed instructions for installing and using Azure PowerShell, which is a Windows-centric tool. The documentation refers to 'PowerShell' without clarifying cross-platform support, and the CLI examples use the Azure CLI, which is cross-platform, but there is no mention of Bash or Linux-specific shell usage. The order of presentation is mostly Portal, PowerShell, then CLI, which subtly prioritizes Windows tooling. There are no explicit Linux/Bash examples or references to Linux-native tools.
Recommendations
- Clarify that Azure PowerShell is available cross-platform, but also provide Bash shell examples where appropriate.
- Add explicit Bash/Linux shell examples for CLI commands, including sample shell scripts for automation.
- In the prerequisites, mention that Azure CLI and Azure PowerShell are both available on Linux, macOS, and Windows, and provide installation links for all platforms.
- Consider alternating the order of PowerShell and CLI examples, or explicitly stating that both are cross-platform.
- Where possible, provide guidance for Linux users (e.g., using Bash variables, scripting, or integrating with Linux-native automation tools).
Load Balancer
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/quickstart-load-balancer-standard-internal-cli.md
...ncer/quickstart-load-balancer-standard-internal-cli.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation demonstrates a Windows bias by exclusively deploying Windows Server images for all virtual machines, using Windows-specific tools (IIS, PowerShell), and providing no Linux alternatives or examples. Instructions for installing and testing use Windows-centric approaches (IIS, Internet Explorer), with no mention of Linux VMs, Apache/Nginx, or Linux command-line tools. The only OS image options shown are Windows, and all automation scripts for configuration use PowerShell commands.
Recommendations
- Provide parallel examples for deploying Linux VMs (e.g., using --image UbuntuLTS) alongside Windows examples.
- Include instructions for installing a web server on Linux (e.g., Apache or Nginx) using cloud-init or shell scripts.
- Show how to test the load balancer using Linux tools (e.g., curl, wget, or a browser on a Linux VM).
- When demonstrating automation or configuration, provide both PowerShell and Bash/shell script equivalents.
- Explicitly mention that both Windows and Linux VMs are supported, and link to relevant Linux documentation.
- Avoid referencing Windows-only tools (like Internet Explorer) as the default for testing; suggest cross-platform alternatives.
Load Balancer
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/quickstart-load-balancer-standard-public-portal.md
...cer/quickstart-load-balancer-standard-public-portal.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Windows First
Summary
The documentation provides only Windows-based instructions for configuring the backend VMs, specifically using Windows PowerShell to install and configure IIS. There are no examples or guidance for Linux VMs, such as using SSH or installing/configuring a web server like Apache or Nginx. The use of Windows tools and patterns is exclusive, and Linux alternatives are not mentioned or demonstrated.
Recommendations
- Add a parallel section for Linux VMs, including steps to connect via SSH and install/configure a web server (e.g., Apache or Nginx) with equivalent content.
- Provide both Windows and Linux command examples side-by-side or clearly label each set of instructions for different OS types.
- Mention Linux as a supported backend option early in the documentation to set expectations for cross-platform parity.
- Where PowerShell or Windows-specific tools are referenced, also provide the Linux equivalent commands (e.g., apt/yum for package installation, echo/cat for file manipulation).
- Include screenshots or terminal output for Linux steps, similar to the Windows examples.
Load Balancer
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/quickstart-load-balancer-standard-internal-template.md
...ttps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/quickstart-load-balancer-standard-internal-template.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for deployment, but it consistently presents PowerShell as a primary or co-equal method, which is more closely associated with Windows environments. The introductory deployment step specifically references Azure PowerShell first, and the use of PowerShell cmdlets (e.g., New-AzResourceGroupDeployment) and patterns (e.g., Read-Host, Write-Host) are Windows-centric. There is no mention of Linux-native scripting or shell environments (such as Bash), and the PowerShell examples use Windows-style prompts and conventions. Additionally, the cleanup section contains a mistake: the CLI tab uses a PowerShell command (Remove-AzResourceGroup), which could confuse Linux users.
Recommendations
- Ensure that Azure CLI (which is cross-platform and more familiar to Linux users) is presented first in all code examples and instructions.
- Explicitly mention that both Azure CLI and PowerShell are cross-platform, but highlight that Azure CLI is often preferred in Linux/macOS environments.
- Provide Bash-native scripting examples (using export, read, etc.) for Linux users, and clarify the shell context for each example.
- Correct the cleanup section so that the CLI tab uses the correct Azure CLI command (az group delete --name ...), not a PowerShell command.
- Add a note or section on using the Azure portal and REST API for users who prefer not to use command-line tools.
- Review prompts and variable handling to ensure parity between PowerShell and Bash/CLI examples, using idiomatic syntax for each.
Load Balancer
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/quickstart-load-balancer-standard-internal-portal.md
...r/quickstart-load-balancer-standard-internal-portal.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Powershell Heavy
Windows Tools
Summary
The documentation page demonstrates a strong Windows bias. All VM creation instructions use Windows Server images, and all configuration and testing steps (such as installing IIS and editing files) are provided exclusively with Windows PowerShell commands and Windows-specific tools. There are no Linux VM examples, nor are there instructions for installing or configuring a web server on Linux. The test steps also assume a Windows desktop environment (using Microsoft Edge).
Recommendations
- Add parallel instructions for creating Linux-based VMs (e.g., Ubuntu or CentOS) alongside the Windows VM creation steps.
- Provide Linux-specific commands for installing a web server (such as Apache or Nginx) and customizing the default web page, using bash or shell commands.
- Include examples of connecting to Linux VMs using SSH (via Bastion or other means), not just RDP/Bastion for Windows.
- When demonstrating testing steps, mention using a browser available on Linux (such as Firefox or Chromium) or using curl/wget from the command line.
- Where possible, present both Windows and Linux instructions side-by-side, or clearly indicate which steps are OS-specific.
- Avoid assuming the reader is using a Windows environment for all tasks; provide cross-platform guidance.
Load Balancer
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/quickstart-load-balancer-standard-public-bicep.md
...ncer/quickstart-load-balancer-standard-public-bicep.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation exhibits a Windows bias by prioritizing PowerShell examples alongside Azure CLI, referencing Windows-specific tools (IIS), and omitting Linux-based deployment or validation steps. The web server example uses Internet Information Services (IIS), which is Windows-only, and there are no Linux VM or Apache/Nginx examples. The validation step assumes a Windows environment, and PowerShell is given equal prominence to CLI, but no Bash or Linux-native instructions are provided.
Recommendations
- Include Linux-based examples for deploying and validating the load balancer, such as using Apache or Nginx on Linux VMs.
- Add Bash/Linux shell instructions alongside PowerShell for deploying the Bicep file.
- Demonstrate how to connect to Linux VMs (e.g., using SSH) and validate the web server response from a Linux perspective.
- Alternate the order of CLI and PowerShell tabs, or default to CLI/Bash to avoid Windows-first perception.
- Clarify that IIS is just one example and provide equivalent steps for Linux environments.
Load Balancer
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/quickstart-load-balancer-standard-public-template.md
...r/quickstart-load-balancer-standard-public-template.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Windows First
Summary
The documentation page demonstrates a Windows bias by providing only Azure PowerShell deployment instructions and code samples, with no equivalent Azure CLI (cross-platform) or Bash examples. The walkthrough assumes the use of PowerShell and references Internet Information Services (IIS), a Windows web server, as the default application. There is no mention of Linux-based deployment or tools, and Linux users are not given parity in guidance or examples.
Recommendations
- Add Azure CLI (az) and Bash examples for deploying the ARM template, alongside the PowerShell instructions.
- Include Linux-based web server examples (e.g., Apache or Nginx) in the template and testing steps, or provide parallel instructions for both Windows and Linux VMs.
- Explicitly mention that the steps are cross-platform where possible, and clarify when a step is Windows-specific.
- Reorder or supplement the instructions so that cross-platform (CLI) methods are presented before or alongside Windows-specific (PowerShell) methods.
- Provide screenshots or output examples from both Windows and Linux environments to ensure inclusivity.
Load Balancer
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/quickstart-load-balancer-standard-public-cli.md
...lancer/quickstart-load-balancer-standard-public-cli.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Powershell Heavy
Summary
The documentation demonstrates a Windows bias by exclusively creating Windows Server VMs (using the 'win2019datacenter' image) and providing only PowerShell-based IIS installation commands. There are no examples for deploying or configuring Linux VMs, nor instructions for installing a Linux web server (such as Apache or Nginx). The automation and scripting examples for configuring backend servers are Windows-specific, and Linux alternatives are not mentioned.
Recommendations
- Provide parallel examples for creating Linux VMs (e.g., using Ubuntu or CentOS images) alongside the Windows VM creation steps.
- Include instructions and az vm extension set commands for installing a web server on Linux VMs (such as Apache or Nginx), and for customizing the default web page to show the VM name.
- Clearly label sections as 'Windows example' and 'Linux example' where applicable, or present both options together.
- Avoid assuming PowerShell or Windows-specific tools/scripts; use cross-platform scripting or provide Bash/Linux shell alternatives.
- In the 'Install IIS' section, add a corresponding 'Install Apache/Nginx on Linux' section with appropriate commands.
Load Balancer
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/tutorial-multi-availability-sets-portal.md
...ad-balancer/tutorial-multi-availability-sets-portal.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Powershell Heavy
Windows Tools
Summary
The documentation exclusively uses Windows Server as the VM image and provides only Windows-specific instructions for configuring backend servers (e.g., installing IIS via PowerShell). There are no examples or guidance for deploying or configuring Linux-based VMs, nor are there alternative commands or tools for Linux environments. The use of PowerShell and Windows-specific tools is pervasive, and Linux parity is entirely absent.
Recommendations
- Include parallel instructions for deploying Linux-based VMs (e.g., Ubuntu or CentOS) in the backend pool.
- Provide Linux-specific steps for installing a web server (such as Apache or Nginx) using Bash or the Azure Run Command for Linux.
- Show both Windows and Linux options side-by-side in tables or as separate sections, making it clear that either OS can be used.
- When demonstrating the use of Azure Run Command, include Bash script examples for Linux VMs.
- Mention that the load balancer works with both Windows and Linux VMs, and link to relevant Linux documentation.
- Ensure screenshots and portal instructions show both Windows and Linux image selection where appropriate.
Load Balancer
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/troubleshoot-load-balancer-imds.md
...icles/load-balancer/troubleshoot-load-balancer-imds.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by consistently linking to Windows-specific documentation (e.g., /azure/virtual-machines/windows/instance-metadata-service) without mentioning or linking to Linux equivalents. There are no Linux-specific examples, references, or links, and the only tabbed references in links are set to 'windows'. This may mislead users into thinking the guidance is Windows-only or that Linux is not supported.
Recommendations
- Provide parallel links to both Windows and Linux documentation for the Azure Instance Metadata Service (IMDS), using tabbed content or explicit links (e.g., /azure/virtual-machines/linux/instance-metadata-service).
- Include Linux-specific examples or clarify that the error codes and mitigation steps apply equally to Linux VMs.
- Where links use tabbed content (e.g., #http-verbs, #rate-limiting), ensure the default tab is not set to Windows, or add a note about Linux applicability.
- Add a section or note explicitly stating that the guidance is valid for both Windows and Linux virtual machines, or provide separate instructions if there are differences.
Load Balancer
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/tutorial-deploy-cross-region-load-balancer-template.md
...ttps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/tutorial-deploy-cross-region-load-balancer-template.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a Windows bias by only referencing the deployment and verification of a default IIS Windows Server web page, with no mention of Linux-based alternatives. The virtual machine configuration is implicitly Windows-centric (IIS), and there are no examples or guidance for deploying or verifying a Linux-based web server. No Linux tools, patterns, or screenshots are provided.
Recommendations
- Include parallel instructions and examples for deploying a Linux-based web server (e.g., Apache or Nginx) in the virtual machines.
- Provide screenshots and verification steps for accessing a default Linux web server page, alongside the IIS example.
- Explicitly mention that the template and process can be used for both Windows and Linux VMs, and link to documentation for configuring Linux VMs.
- When referencing tools or web servers (like IIS), also mention and provide examples for common Linux equivalents.
- Ensure that any code snippets, screenshots, or validation steps are not Windows-exclusive, and offer Linux parity throughout the tutorial.
Load Balancer
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/tutorial-protect-load-balancer-ddos.md
...s/load-balancer/tutorial-protect-load-balancer-ddos.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Powershell Heavy
Windows Tools
Summary
The tutorial demonstrates a clear Windows bias by exclusively using Windows Server images for virtual machines and providing only Windows PowerShell commands for configuring IIS. There are no instructions or examples for deploying or configuring Linux VMs, nor are there Bash or Linux-native commands for installing a web server. The documentation assumes a Windows environment for demonstration and testing, omitting Linux alternatives.
Recommendations
- Provide parallel instructions for creating Linux-based VMs (e.g., Ubuntu) alongside Windows VMs.
- Include Bash or shell commands for installing and configuring a web server (such as Apache or Nginx) on Linux VMs.
- Offer both Windows and Linux examples for all configuration and testing steps, including web server setup and verification.
- Explicitly mention that the tutorial applies to both Windows and Linux environments, and guide users on how to choose the appropriate OS image.
- Where PowerShell is used, provide equivalent Bash commands for Linux users.
- Add a section or callout highlighting cross-platform considerations and links to relevant Linux documentation.
Load Balancer
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/tutorial-cross-region-portal.md
...articles/load-balancer/tutorial-cross-region-portal.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by consistently referencing Windows-centric tools and patterns. PowerShell is given equal prominence to Azure CLI, and in some cases, Windows-specific terminology (such as IIS Web server) is used without Linux alternatives. There are no explicit Linux/Bash examples for backend pool VMs or web server setup, and the testing instructions assume a Windows environment (IIS), omitting Linux-based web server guidance. The CLI examples are platform-agnostic, but the lack of Linux-specific context and examples (e.g., using Apache/Nginx, Linux VM setup, or Bash scripting) limits parity.
Recommendations
- Add explicit Linux/Bash examples for creating and configuring backend VMs, including installing and running a Linux web server (e.g., Apache or Nginx) in addition to IIS.
- In testing steps, provide instructions for both Windows (IIS) and Linux (Apache/Nginx) default web pages, clarifying expected results for each.
- Clarify that Azure CLI commands can be run from Bash on Linux/macOS, and provide sample Bash scripts where appropriate.
- When referencing PowerShell, ensure that equivalent Bash or shell scripting examples are provided, especially for tasks like variable assignment and resource manipulation.
- Avoid Windows-centric language (e.g., referencing only IIS or Windows tools) in general instructions; instead, use cross-platform terminology or provide both Windows and Linux alternatives.
- Consider adding a section or callout for Linux users, summarizing any differences or additional steps they may encounter.
Load Balancer
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/tutorial-load-balancer-ip-backend-portal.md
...d-balancer/tutorial-load-balancer-ip-backend-portal.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Powershell Heavy
Windows Tools
Summary
The documentation demonstrates a clear Windows bias, particularly in the 'Install IIS' section, where only Windows Server is used for the VM image and only Windows PowerShell commands are provided for configuring the web server. There are no Linux VM options or equivalent Linux-based instructions (e.g., using Ubuntu and Apache/nginx). The use of Windows-specific tools and administrative patterns (PowerShell, Windows Administrative Tools) further reinforces this bias.
Recommendations
- Provide parallel instructions for creating Linux-based VMs (e.g., Ubuntu or CentOS) alongside Windows VMs.
- Include Linux command-line examples (e.g., using bash/ssh) for installing and configuring a web server such as Apache or nginx.
- Offer users a choice of OS image (Windows or Linux) in the VM creation steps, and clarify that the load balancer works with both.
- Demonstrate how to connect to Linux VMs (e.g., via SSH through Bastion) and perform equivalent setup tasks.
- Balance the documentation by presenting both Windows and Linux workflows, or at minimum, link to Linux-specific tutorials for similar scenarios.
Load Balancer
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/tutorial-nat-rule-multi-instance-portal.md
...ad-balancer/tutorial-nat-rule-multi-instance-portal.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation demonstrates a mild Windows bias in the 'Install web server' section, where users are instructed to open a PowerShell prompt on Windows and a Bash prompt on Mac/Linux, but all SSH command examples use Windows-style paths (e.g., .\Downloads\myKey.pem) and do not provide Linux/macOS equivalents. There are no explicit Linux command examples for SSH, and the documentation assumes familiarity with Windows conventions. Additionally, PowerShell is mentioned before Bash, and there are no Linux-specific troubleshooting or tool references.
Recommendations
- Provide both Windows (PowerShell) and Linux/macOS (Bash) command examples for SSH, with appropriate path formats (e.g., .\Downloads\myKey.pem for Windows, ~/Downloads/myKey.pem for Linux/macOS).
- List Bash/Linux instructions before or alongside PowerShell/Windows instructions to avoid the impression of Windows primacy.
- Include troubleshooting tips or notes relevant to Linux/macOS users, such as setting key file permissions (chmod 600 myKey.pem).
- Where file paths are referenced, clarify the differences between Windows and Linux/macOS path conventions.
- Consider adding a table or callout box that shows side-by-side commands for both platforms.
Load Balancer
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/whats-new.md
...ure-docs/blob/main/articles/load-balancer/whats-new.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page exhibits subtle Windows bias, most notably by linking to a PowerShell-based guide for creating dual stack (IPv4/IPv6) applications with Azure Load Balancer, without mentioning or providing equivalent Linux/CLI/Bash examples. The only explicit example link for a technical task is PowerShell-specific, and there is no indication of Linux or cross-platform command-line alternatives. This prioritization of Windows tooling and omission of Linux examples may hinder discoverability and usability for Linux users.
Recommendations
- Wherever a PowerShell example or guide is linked, also provide equivalent Azure CLI (az) or Bash examples, or link to cross-platform documentation.
- Ensure that technical walkthroughs and how-to guides referenced from this page include both Windows (PowerShell) and Linux (CLI/Bash) instructions, or clearly indicate cross-platform compatibility.
- Audit linked articles (such as 'create a dual stack application') to ensure Linux parity and update this page to reference those alternatives.
- Consider adding a short note in the 'Recent releases' section clarifying that Azure Load Balancer can be managed from both Windows and Linux environments, with links to relevant documentation for each.
Load Balancer
Quickstart: Create a public load balancer - ARM template
...r/quickstart-load-balancer-standard-public-template.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation provides only Azure PowerShell examples for deploying the ARM template, with no equivalent Azure CLI (cross-platform) or Bash examples. The deployment walkthrough is written entirely around PowerShell usage, and the output screenshots reference PowerShell. Additionally, the template configures Internet Information Services (IIS), a Windows-only web server, as the default workload, which further centers the example on Windows environments.
Recommendations
- Add Azure CLI (az) and/or Bash examples for deploying the ARM template, alongside the PowerShell script.
- Explicitly mention that the Cloud Shell supports both Bash and PowerShell, and provide instructions for both.
- If possible, offer an alternative template or instructions for deploying a Linux-based workload (e.g., Apache or Nginx) for users who do not wish to use IIS.
- Ensure screenshots and walkthroughs include both PowerShell and CLI outputs where relevant.