Load Balancer

102
Total Pages
45
Linux-Friendly Pages
57
Pages with Bias
55.9%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues (87)

https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/whats-new.md [View Details]
Scanned: 2025-07-17 00:00 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example Powershell Heavy
Summary:
The documentation page exhibits subtle Windows bias. For example, the only explicit link to a hands-on guide for creating a dual stack application refers to a PowerShell-based tutorial (which is Windows-centric), and there are no visible Linux or cross-platform CLI examples or references. The documentation does not mention Linux tools or provide parity in example commands or scripts. This could make Linux users feel less supported or require extra effort to find relevant guidance.
Recommendations:
  • Add equivalent Linux/bash/Azure CLI examples and links wherever PowerShell or Windows-specific instructions are referenced.
  • Ensure that links to tutorials or how-to guides (e.g., for creating dual stack applications) include both PowerShell and Azure CLI/Bash options, and mention both in the main documentation.
  • Wherever possible, use cross-platform tools (such as Azure CLI) in examples, or provide both PowerShell and Bash/Azure CLI snippets side by side.
  • Explicitly mention Linux support and tools in relevant sections to reassure non-Windows users that their platforms are equally supported.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/howto-load-balancer-imds.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Windows First Windows Tools Missing Linux Example
Summary:
The documentation displays a mild Windows bias: Windows/PowerShell examples and links are presented before Linux equivalents, and references to Windows-specific tools and documentation are more prominent. The prerequisites and important notes link only to Windows-specific IMDS documentation, and troubleshooting/learning links default to Windows tabs. While a Linux example is present, Linux documentation is less emphasized.
Recommendations:
  • Present Linux and Windows examples in parallel or in a neutral order, or default to a platform-agnostic example.
  • Ensure all documentation links (e.g., prerequisites, further reading) include both Windows and Linux versions or use platform-neutral links.
  • Add Linux-specific notes where relevant (e.g., proxy bypassing in curl).
  • Avoid referencing Windows tools or documentation exclusively; mention Linux equivalents with equal prominence.
  • Consider a 'Platform' selector at the top of the page to allow users to choose their OS context.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/load-balancer-multiple-ip.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example Windows Tools Powershell Heavy
Summary:
The documentation is heavily biased towards Windows environments. It only references the creation of Windows server virtual machines, uses Windows-specific tools (IIS), and provides PowerShell examples. There are no mentions or examples for Linux VMs, Linux web servers (such as Apache or Nginx), or Linux command-line tools. The steps and examples are tailored exclusively to Windows users, leaving Linux users without guidance.
Recommendations:
  • Add parallel instructions and examples for creating and configuring Linux virtual machines.
  • Include steps for setting up popular Linux web servers (e.g., Apache, Nginx) alongside IIS.
  • Provide Linux CLI examples (using Bash/Azure CLI) for all configuration steps.
  • Ensure that portal, CLI, and PowerShell sections all include Linux-specific guidance where relevant.
  • Mention Linux as an option in the tutorial introduction and checklist, not just Windows.
  • Balance the order of presentation so that Linux and Windows are given equal prominence.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/load-balancer-troubleshoot-backend-traffic.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example
Summary:
The documentation provides only Windows-specific command-line instructions (e.g., using 'netstat' in a Windows command prompt) for troubleshooting, without offering equivalent Linux commands or examples. This creates a bias toward Windows environments and may hinder users operating Linux-based Azure VMs.
Recommendations:
  • Include Linux equivalents for all command-line examples. For instance, alongside 'netstat -an' in Windows, provide 'ss -ltn' or 'netstat -ltn' for Linux.
  • When referencing command prompts or shells, mention both Windows (Command Prompt/PowerShell) and Linux (Bash/shell) environments.
  • Ensure that troubleshooting steps and validation commands are platform-agnostic or provide parallel instructions for both Windows and Linux.
  • Explicitly state that the guidance applies to both Windows and Linux VMs, and clarify any platform-specific differences in behavior or commands.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/load-balancer-troubleshoot-health-probe-status.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Windows First Powershell Heavy Windows Tools Missing Linux Example
Summary:
The documentation demonstrates a Windows bias by prioritizing Windows tools (PsPing, TCPing, netstat, netsh) in troubleshooting steps, providing Windows command examples first or exclusively, and only briefly mentioning Linux equivalents (netstat -l, sudo iptables -L) as secondary notes. There are no Linux-specific troubleshooting tools or detailed Linux command examples, and the overall troubleshooting workflow assumes a Windows environment.
Recommendations:
  • Provide Linux-first or parallel Linux command examples alongside Windows commands for each troubleshooting step.
  • Include Linux-native tools (e.g., ss, nc/ncat, lsof, firewalld-cmd, ufw) for port and firewall checks, with example commands.
  • Offer example commands for both Windows and Linux for connectivity testing (e.g., using nc or curl for Linux instead of only PsPing/TCPing).
  • Explicitly state that the instructions apply to both Windows and Linux VMs, and structure sections so that Linux and Windows guidance are equally prominent.
  • Where third-party tools are suggested (PsPing, TCPing), recommend open-source or pre-installed Linux alternatives and provide installation instructions if needed.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/troubleshoot-load-balancer-imds.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example
Summary:
The documentation page demonstrates a Windows-first bias by linking exclusively to Windows-specific documentation for the Azure Instance Metadata Service (IMDS), such as /azure/virtual-machines/windows/instance-metadata-service, and by referencing documentation tabs with '?tabs=windows'. There are no Linux or cross-platform examples, nor are Linux-specific links or guidance provided. This may make it harder for Linux users to find relevant information or feel equally supported.
Recommendations:
  • Include links to both Windows and Linux versions of the Azure Instance Metadata Service documentation, such as /azure/virtual-machines/linux/instance-metadata-service.
  • When referencing documentation with tabbed content (e.g., '?tabs=windows'), either use the default tab or explicitly mention both Windows and Linux tabs.
  • Add Linux-specific examples or notes where appropriate, especially if there are differences in usage or troubleshooting steps.
  • Ensure that all guidance and mitigation steps are applicable to both Windows and Linux users, or clearly indicate any platform-specific differences.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/quickstart-load-balancer-standard-internal-bicep.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

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 alternative throughout. There are no Linux-specific shell examples (e.g., Bash), and no explicit mention of Linux environments or tools, which may lead to a subtle Windows bias, especially for users unfamiliar with PowerShell.
Recommendations:
  • Clarify that Azure CLI commands work cross-platform (Windows, macOS, Linux), and recommend CLI as the default for Linux/macOS users.
  • Consider listing Azure CLI examples before PowerShell, or labeling CLI as the preferred method for non-Windows users.
  • Add explicit notes or callouts for Linux/macOS users, reassuring them that PowerShell is optional and not required.
  • Optionally, provide Bash script examples or usage notes for Linux users, especially for common automation scenarios.
  • In the prerequisites, mention that Azure CLI is available on all major platforms, while PowerShell is primarily used on Windows (though cross-platform versions exist).
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/ipv6-add-to-existing-vnet-powershell.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Missing Linux Example Windows Tools Windows First
Summary:
The documentation is heavily biased towards Windows and PowerShell usage. All examples and instructions are provided exclusively using Azure PowerShell cmdlets, with no mention of Azure CLI, Bash, or Linux-native tooling. The prerequisites, setup, and resource management steps all assume a PowerShell environment, and there are no alternative instructions or code samples for Linux users. The article title and repeated references to PowerShell reinforce this bias.
Recommendations:
  • Provide equivalent Azure CLI (az) command examples for each PowerShell example, ideally side-by-side or in separate tabs.
  • Update the article title and description to reflect cross-platform support, or create a parallel article for Azure CLI/Linux users.
  • Add a section on how to perform these tasks using Bash or in the Azure Cloud Shell with Bash.
  • Mention both PowerShell and CLI options in the prerequisites and setup sections, including installation links for both.
  • Ensure that references to tools and commands do not assume a Windows environment by default.
  • Where possible, use neutral language (e.g., 'using Azure PowerShell or Azure CLI') and avoid Windows-first phrasing.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/load-balancer-manage-health-status.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Windows Tools Missing Linux Example Windows First
Summary:
The documentation page demonstrates Windows bias primarily through its exclusive reference to the Windows PowerShell cmdlet (Get-AzAccessToken) for obtaining a Bearer access token, without mentioning Linux or cross-platform alternatives. There are no CLI or Bash examples, and the only tool referenced for authentication is a Windows-centric PowerShell module. This may hinder Linux users or those using non-Windows environments from easily following the instructions.
Recommendations:
  • Provide equivalent Azure CLI (az account get-access-token) instructions for obtaining a Bearer access token, which works on Windows, Linux, and macOS.
  • Include Bash/cURL examples for making REST API requests, not just REST request syntax.
  • Avoid referencing only PowerShell modules; when mentioning tools, list cross-platform options first or alongside Windows-specific tools.
  • Explicitly state that the instructions apply to all platforms, and provide links to relevant Linux/macOS guidance where appropriate.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/troubleshoot-rhc.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example
Summary:
The documentation demonstrates a subtle Windows bias by referencing Windows-specific troubleshooting content first (e.g., linking only to Windows VM CPU troubleshooting) and providing a Windows command prompt example before the Linux equivalent. There are no Linux-specific troubleshooting links or parity in example depth.
Recommendations:
  • Include links to both Windows and Linux troubleshooting guides (e.g., for high CPU usage) to ensure platform parity.
  • When providing command-line examples, present both Windows and Linux commands side by side, or in a neutral order (alternating which comes first).
  • Add Linux-specific troubleshooting steps or references where appropriate, especially in sections that currently only mention Windows resources.
  • Review all external links and ensure Linux equivalents are present wherever Windows-specific documentation is referenced.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/tutorial-gateway-outbound-connectivity.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example
Summary:
The documentation demonstrates a Windows bias by referencing only the creation of a Windows VM in the prerequisites and omitting any mention or example of Linux virtual machines. There are no Linux-specific instructions, links, or parity in the examples, which may lead Linux users to feel unsupported or uncertain about the process.
Recommendations:
  • Include references and links to both Windows and Linux VM creation guides in the prerequisites section (e.g., add a link to 'Create a Linux VM in the Azure portal').
  • Explicitly state that the instructions apply to both Windows and Linux VMs, unless there are platform-specific differences.
  • Where examples refer to a VM (e.g., 'myVM1'), clarify that it can be either a Windows or Linux VM.
  • If there are any platform-specific steps (such as verifying network settings inside the VM), provide both Windows and Linux command examples.
  • Review all sections for implicit Windows assumptions and ensure Linux users are equally guided.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/tutorial-deploy-cross-region-load-balancer-template.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example Windows Tools
Summary:
The documentation page demonstrates a Windows bias by only referencing Windows Server (IIS) as the web server deployed on the virtual machines, with no mention of Linux alternatives. The verification step specifically instructs users to expect the default IIS Windows Server web page, and the template configures IIS, which is Windows-specific. There are no examples or guidance for deploying or verifying with a Linux-based web server (e.g., Apache, Nginx), nor are there any Linux command-line or deployment instructions.
Recommendations:
  • Include parallel instructions and screenshots for deploying and verifying a Linux-based web server (such as Apache or Nginx) in addition to IIS.
  • Modify the ARM template or provide an alternative template that configures a Linux VM with a popular web server.
  • In the verification section, show what users should expect if they deployed a Linux VM (e.g., default Apache/Nginx page).
  • Explicitly mention that the tutorial can be followed with either Windows or Linux VMs, and provide parameter options or guidance for both.
  • Avoid assuming Windows as the default platform; present both Windows and Linux options equally throughout the documentation.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/instance-metadata-service-load-balancer.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example
Summary:
The documentation page demonstrates a Windows bias by linking to the Windows-specific Azure Instance Metadata Service documentation in the 'Next steps' section, without referencing the Linux equivalent. There are no operating system-specific examples or commands, but the only direct link for further learning is for Windows, and there is no mention of Linux or cross-platform guidance.
Recommendations:
  • Include links to both Windows and Linux versions of the Azure Instance Metadata Service documentation in the 'Next steps' section.
  • Explicitly state that the IMDS REST API is OS-agnostic and can be accessed from both Windows and Linux VMs.
  • Provide example commands for retrieving metadata using common Linux tools (e.g., curl or wget) alongside any Windows/Powershell examples.
  • Ensure that troubleshooting and support guidance is not Windows-centric and covers common issues for both platforms.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/quickstart-load-balancer-standard-public-bicep.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Windows First Powershell Heavy Missing Linux Example
Summary:
The documentation provides both Azure CLI and Azure PowerShell deployment instructions, but PowerShell is given equal prominence despite being Windows-centric. The example workload is Internet Information Services (IIS), a Windows-only web server, with no mention of Linux alternatives. There are no Linux-specific examples or guidance for deploying or testing with Linux-based VMs or tools.
Recommendations:
  • Include Linux-focused deployment and testing examples, such as using Apache or Nginx on Linux VMs.
  • Provide explicit instructions for connecting to Linux VMs (e.g., SSH) and verifying deployment from a Linux perspective.
  • Clarify that Azure CLI is cross-platform and recommend it as the default for broader compatibility.
  • Add a Linux tab or section alongside PowerShell for parity, especially in deployment and validation steps.
  • Show how to configure and test the load balancer with both Windows and Linux backend VMs.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/basic/quickstart-basic-internal-load-balancer-portal.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example Windows Tools Powershell Heavy
Summary:
The documentation page demonstrates a significant Windows bias. All VM creation steps use Windows Server images by default, and there are no instructions or examples for deploying or configuring Linux VMs. The IIS installation and configuration are provided exclusively with Windows PowerShell commands, and the test instructions assume the use of Internet Explorer. No Linux alternatives (such as Apache/Nginx installation, Bash commands, or Linux VM images) are mentioned or offered.
Recommendations:
  • Provide parallel instructions for creating Linux VMs (e.g., Ubuntu or CentOS) alongside Windows VMs.
  • Include Linux-specific steps for installing a web server (such as Apache or Nginx) using Bash commands.
  • Offer both PowerShell (Windows) and Bash (Linux) command examples for server configuration.
  • When referencing tools (e.g., Internet Explorer), mention Linux equivalents (e.g., Firefox, curl, wget).
  • Explicitly state that the process works for both Windows and Linux VMs, and link to relevant Linux documentation.
  • Consider alternating the order of Windows and Linux examples, or presenting them side-by-side for parity.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/cross-subscription-how-to-attach-backend.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First
Summary:
The documentation provides both Azure PowerShell and Azure CLI examples, but the PowerShell (Windows-centric) example appears first and is more detailed, with step-by-step variable assignments and explanations. The CLI (cross-platform) example is shorter and less detailed. There are no Linux-specific tools or shell examples, and the structure implicitly prioritizes Windows/PowerShell usage.
Recommendations:
  • Present Azure CLI examples before PowerShell examples, as CLI is cross-platform and more accessible to Linux users.
  • Ensure that both PowerShell and CLI sections have equivalent detail and explanation, so Linux users are not disadvantaged.
  • Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and provide any necessary Linux shell context (e.g., bash variable usage if needed).
  • Consider adding bash or shell script examples where appropriate, especially for steps involving multiple commands or variables.
  • If referencing tools or commands that are Windows-specific (like PowerShell cmdlets), always provide a CLI or bash alternative.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/egress-only.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example
Summary:
The documentation demonstrates a Windows bias by exclusively using Windows Server as the VM image in the creation steps and referencing Microsoft Edge for connectivity tests. There are no examples or instructions for deploying or testing with Linux-based virtual machines, nor are Linux tools or browsers mentioned. This may lead Linux users to feel unsupported or unsure if the process is applicable to their environments.
Recommendations:
  • Provide parallel instructions for creating a Linux-based VM (e.g., Ubuntu or CentOS) alongside the Windows example.
  • Include Linux-specific details for connecting to the VM (e.g., using SSH via Bastion, or using a Linux desktop environment and browser).
  • When testing outbound connectivity, mention using a browser available on Linux (e.g., Firefox) or using command-line tools like curl or wget to verify external IP.
  • Clarify that the process is OS-agnostic unless there are steps that are truly Windows-specific, and highlight any differences for Linux users.
  • Where possible, use neutral language and examples (e.g., 'open a web browser' instead of 'open Microsoft Edge').
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/backend-pool-management.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Windows Tools
Summary:
The documentation demonstrates a Windows bias by presenting PowerShell examples first and in greater detail, using Windows-centric tooling (Azure PowerShell), and providing a Windows Server image in the PowerShell VM creation example. While CLI examples are present and include a Linux (Ubuntu) image, the PowerShell section is more comprehensive and implicitly assumes a Windows environment, especially for VM provisioning.
Recommendations:
  • Provide both PowerShell and CLI examples in parallel for each step, ensuring parity in detail and coverage.
  • In PowerShell VM creation examples, include both Windows and Linux image options, or use a neutral example.
  • Explicitly mention that Azure PowerShell can be used cross-platform, or provide Bash/Cloud Shell alternatives where possible.
  • Avoid defaulting to Windows Server images in examples; alternate or provide both Windows and Linux image options.
  • Consider starting with CLI examples or alternating the order to avoid 'windows_first' bias.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/load-balancer-basic-upgrade-guidance.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Missing Linux Example
Summary:
The documentation page demonstrates a Windows bias by exclusively recommending and linking to PowerShell scripts for automation, with no mention of Azure CLI, Bash, or Linux-based automation alternatives. The term 'PowerShell' is used as the default and only automation method, and there are no Linux/Unix command examples or references to cross-platform tooling. Manual steps reference the Azure Portal, which is cross-platform, but all scripting guidance is Windows-centric.
Recommendations:
  • Provide equivalent Azure CLI scripts for all PowerShell automation examples, and link to them alongside the PowerShell scripts.
  • Explicitly mention that automation can be performed from Linux, macOS, or Windows using Azure CLI or PowerShell Core.
  • Add Bash shell examples or guidance for users on Linux/macOS, especially for common migration tasks.
  • Rephrase recommendations to present both PowerShell and Azure CLI options equally, rather than defaulting to PowerShell.
  • Include a table or section summarizing automation options by platform (Windows, Linux, macOS) and tool (PowerShell, Azure CLI, Portal).
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/basic/quickstart-basic-public-load-balancer-portal.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example Windows Tools Powershell Heavy
Summary:
The documentation demonstrates a clear Windows bias, particularly in the VM creation and configuration steps. Only Windows Server images are used for the virtual machines, and the IIS installation instructions are exclusively for Windows, using PowerShell commands. There are no examples or guidance for creating or configuring Linux VMs, nor for installing a Linux web server (such as Apache or Nginx). All scripting and administrative steps are Windows-centric, and Linux users are not provided with equivalent instructions.
Recommendations:
  • Provide parallel instructions for creating Linux VMs (e.g., Ubuntu or CentOS) alongside the Windows VM steps.
  • Include Linux-specific examples for installing a web server (e.g., Apache or Nginx) using bash commands.
  • Show how to connect to Linux VMs via SSH using Bastion, and provide sample commands for updating the web root.
  • Ensure that both Windows and Linux options are presented equally in tables and step-by-step guides.
  • Avoid assuming the use of Windows tools (like PowerShell) exclusively; offer bash or shell alternatives where appropriate.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/cross-subscription-how-to-internal-load-balancer.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First
Summary:
The documentation presents both Azure PowerShell and Azure CLI examples, but the PowerShell section is listed first and is more detailed, with step-by-step explanations and variable usage. The CLI section is less detailed and lacks some of the explanatory context provided in the PowerShell section. There are no Linux-specific shell examples or explicit mention of Linux environments, and the documentation implicitly assumes familiarity with PowerShell, which is more common on Windows.
Recommendations:
  • Alternate the order of PowerShell and CLI examples, or present CLI examples first to avoid implicit Windows-first bias.
  • Ensure both PowerShell and CLI sections have equivalent detail and explanation, including variable usage and step-by-step breakdowns.
  • Explicitly mention that Azure CLI commands can be run natively on Linux, macOS, and Windows, and provide bash/zsh syntax where appropriate.
  • Consider adding a short section or note for Linux users, clarifying that all CLI commands are cross-platform and providing any Linux-specific tips if relevant.
  • If possible, provide examples using Azure REST API or ARM templates, which are platform-agnostic, to further enhance cross-platform parity.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/basic/quickstart-basic-internal-load-balancer-powershell.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Missing Linux Example Windows Tools
Summary:
The documentation is heavily biased towards Windows and PowerShell. All examples use Azure PowerShell cmdlets, and there are no CLI, Bash, or Linux-native instructions. Virtual machines are provisioned with Windows Server images only, and IIS (a Windows web server) is installed using Windows-specific commands. The test steps reference Internet Explorer, a Windows-only browser, and there is no mention of Linux VMs, Apache/Nginx, or cross-platform alternatives.
Recommendations:
  • Provide parallel Azure CLI (az) or Bash examples for all resource creation and management steps.
  • Include instructions for creating Linux virtual machines (e.g., Ubuntu) in addition to Windows Server VMs.
  • Demonstrate installation of a Linux web server (such as Apache or Nginx) using cloud-init or custom script extensions for Linux.
  • In testing steps, reference cross-platform browsers (e.g., Edge, Chrome, Firefox) and avoid Windows-only tools like Internet Explorer.
  • Clearly indicate at the top that the guide is Windows/PowerShell-specific, and link to equivalent Linux/CLI quickstarts if available.
  • Where possible, use neutral terminology and tools that work across platforms, or provide both Windows and Linux alternatives side by side.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/whats-new.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example
Summary:
The documentation page generally avoids platform-specific instructions, but there is evidence of subtle Windows bias. For example, the link for creating a dual stack application points specifically to a PowerShell-based guide (which is Windows-centric) and does not mention or link to Linux/CLI equivalents. No explicit Linux examples or parity are provided, and PowerShell is implicitly prioritized.
Recommendations:
  • Provide links to both PowerShell (Windows) and Azure CLI (cross-platform) or Bash (Linux) guides for all procedural documentation, especially for tasks like creating dual stack applications.
  • Wherever a PowerShell example or link is given, ensure an equivalent Azure CLI/Bash example or link is also present and given equal prominence.
  • Review all linked articles (e.g., 'virtual-network-ipv4-ipv6-dual-stack-standard-load-balancer-powershell.md') to ensure Linux users are not excluded and update them to include Linux/CLI instructions if missing.
  • Explicitly mention that Azure CLI is available cross-platform and provide guidance for both Windows and Linux users in all relevant sections.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/quickstart-load-balancer-standard-internal-template.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Windows First Powershell Heavy Missing Linux Example
Summary:
The documentation provides both Azure CLI and PowerShell examples, but PowerShell is mentioned first in the deployment section and is used in the initial deployment instructions. There are no explicit Linux shell (bash) examples or references to Linux-specific environments, and the PowerShell command for resource deletion is incorrectly placed under the CLI tab, which may confuse Linux users. The documentation assumes familiarity with PowerShell, which is more common on Windows, and does not address Linux users directly or provide guidance for running commands in a native Linux shell.
Recommendations:
  • Ensure that Azure CLI (bash) examples are presented first or at least equally with PowerShell, as CLI is cross-platform and more familiar to Linux users.
  • Correct the 'Clean up resources' section: the CLI tab contains a PowerShell command. Replace it with the appropriate Azure CLI command (az group delete --name "${projectName}rg").
  • Explicitly mention that Azure CLI commands can be run in bash on Linux/macOS as well as in Cloud Shell, and clarify that PowerShell is optional.
  • Add guidance or links for Linux users on how to set up and use Azure CLI in their environment.
  • Where possible, include bash script examples for automation alongside PowerShell scripts.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/tutorial-multi-availability-sets-portal.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example Windows Tools Powershell Heavy
Summary:
The documentation demonstrates a clear Windows bias: all virtual machine creation steps use Windows Server images by default, and the only example for configuring the backend web server uses PowerShell scripts to install IIS (a Windows-only web server). There are no examples or guidance for deploying Linux VMs, using Bash/SSH, or installing a Linux-based web server like Apache or Nginx. Windows tools and patterns (PowerShell, IIS) are used exclusively, with no mention of Linux equivalents.
Recommendations:
  • Provide parallel instructions for creating Linux-based virtual machines (e.g., Ubuntu or CentOS) alongside the Windows Server examples.
  • Include example scripts for installing a web server on Linux VMs (e.g., using Bash to install Apache or Nginx via apt/yum).
  • Show how to use the Azure portal's Run Command feature with Bash scripts for Linux VMs, not just PowerShell for Windows.
  • Mention both Windows and Linux options in all relevant steps, including VM image selection and administrator account setup.
  • Add screenshots or code snippets that reflect both Windows and Linux scenarios.
  • Clarify in the prerequisites or introduction that the tutorial is applicable to both Windows and Linux, and provide links to Linux-specific documentation if available.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/cross-subscription-how-to-global-backend.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Windows Tools
Summary:
The documentation demonstrates a Windows bias by consistently presenting Azure PowerShell (a Windows-centric tool) instructions and examples before Azure CLI (cross-platform) equivalents. The structure and language prioritize PowerShell, and there is no mention of Linux-specific considerations, shells, or tooling. The use of PowerShell as the primary example and the presence of the 'devx-track-azurepowershell' custom metadata further reinforce the Windows-centric approach.
Recommendations:
  • Alternate the order of examples so that Azure CLI (cross-platform) instructions are presented first in some sections, or present both equally without prioritizing one.
  • Explicitly mention that Azure CLI works natively on Linux, macOS, and Windows, and provide shell-specific notes where relevant.
  • Add a brief section or note on using Bash or other Linux shells with Azure CLI, including any differences in command syntax or environment setup.
  • Review metadata and custom tags to ensure they do not reinforce a PowerShell/Windows bias (e.g., avoid 'devx-track-azurepowershell' unless equally tracking CLI).
  • Where possible, provide guidance or troubleshooting tips for both Windows and Linux users, especially for environment setup and authentication steps.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/basic/quickstart-basic-internal-load-balancer-cli.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example Powershell Heavy Windows Tools
Summary:
The documentation exclusively demonstrates creating and configuring Windows Server-based virtual machines (using the 'win2019datacenter' image) and uses Windows-specific tools and commands (such as PowerShell and IIS). There are no examples or instructions for deploying or configuring Linux VMs, nor for installing or testing with Linux-based web servers. The instructions for installing IIS use PowerShell commands, and the test steps reference Internet Explorer, further reinforcing a Windows-centric approach.
Recommendations:
  • Provide parallel examples for creating Linux-based VMs (e.g., using Ubuntu or CentOS images) alongside the Windows examples.
  • Include instructions for installing a web server on Linux VMs (e.g., using apt to install nginx or Apache) with corresponding az vm extension set commands.
  • Show how to test the load balancer using Linux tools (e.g., curl or wget) in addition to or instead of Internet Explorer.
  • Avoid assuming the use of Windows-only tools (such as PowerShell or Internet Explorer) and offer cross-platform alternatives.
  • Explicitly mention that the process works for both Windows and Linux VMs, and link to relevant documentation for Linux VM management where appropriate.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/tutorial-nat-rule-multi-instance-portal.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Windows First Powershell Heavy Missing Linux Example
Summary:
The documentation shows 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 a Linux/macOS equivalent. There are no explicit Linux/macOS command examples for SSH, and the documentation assumes familiarity with Windows conventions. Additionally, the order of instructions often lists Windows before Linux/macOS.
Recommendations:
  • Provide both Windows (PowerShell/CMD) and Linux/macOS (Bash) command examples for SSH, with correct path syntax for each platform.
  • When instructing users to open a terminal, list Linux/macOS first or present both options equally.
  • Include notes or callouts clarifying path differences (e.g., '.\Downloads\myKey.pem' for Windows, '~/Downloads/myKey.pem' for Linux/macOS).
  • Wherever possible, avoid assuming a Windows environment; use cross-platform language and examples.
  • Consider adding screenshots or terminal output examples for both Windows and Linux/macOS environments.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/tutorial-cross-region-portal.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Windows First Powershell Heavy Windows Tools Missing Linux Example
Summary:
The documentation demonstrates a moderate Windows bias. While it provides Azure Portal, Azure CLI, and Azure PowerShell instructions, several patterns indicate a preference for Windows-centric tools and workflows. PowerShell is given equal prominence to CLI, and Windows-specific technologies (such as IIS) are assumed in testing. There are no explicit Linux-specific examples or references (e.g., Apache/Nginx for backend VMs), and the documentation does not address Linux shell or scripting nuances, despite the CLI examples being generally cross-platform.
Recommendations:
  • Include explicit Linux examples for backend pool VMs, such as using Apache or Nginx instead of only referencing IIS.
  • In test instructions, mention both Windows (IIS) and Linux (Apache/Nginx) default web pages to clarify cross-platform applicability.
  • Add notes or examples for running Azure CLI commands in Bash or other Linux shells, including handling of environment variables and command output.
  • Where PowerShell is referenced, clarify that it is available cross-platform, or provide Bash equivalents for common scripting patterns.
  • Review terminology and instructions to ensure they do not assume a Windows environment (e.g., file paths, shell commands, browser defaults).
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/deploy-ipv4-ipv6-dual-stack-standard-load-balancer.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Windows First Powershell Heavy Windows Tools Missing Linux Example
Summary:
The documentation exhibits a Windows bias by providing detailed PowerShell examples before Azure CLI, using Windows-centric tools and terminology (e.g., RDP, Windows images), and omitting explicit Linux/SSH examples for VM creation and access. The VM creation steps default to Windows Server images, and remote access is described only via RDP, with no mention of SSH or Linux images. There are no examples or guidance for deploying or accessing Linux VMs, nor are there instructions for Linux administrators.
Recommendations:
  • Add explicit Linux/SSH examples for VM creation and remote access, including az vm create commands with --image UbuntuLTS and SSH key authentication.
  • Include guidance for both Windows and Linux VM images in all relevant steps, making it clear that either OS is supported.
  • Provide instructions for accessing VMs via SSH (for Linux) as well as RDP (for Windows), and clarify the differences.
  • Ensure that CLI and PowerShell examples are presented with equal prominence, or alternate which comes first.
  • Avoid using Windows-specific terminology (e.g., RDP) as the default; instead, use neutral language or mention both RDP and SSH.
  • Add troubleshooting or verification steps relevant to Linux environments (e.g., checking IPv6 connectivity from a Linux shell).
  • Where possible, use cross-platform tools and commands, or clearly indicate OS-specific steps.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/move-across-regions-azure-load-balancer.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Missing Linux Example Windows Tools
Summary:
The documentation provides detailed instructions for moving Azure Load Balancers using the Azure portal and Azure PowerShell, but does not include any examples or guidance for Linux users or cross-platform CLI tools such as Azure CLI (az). All command-line examples are in PowerShell, and there are references to Windows-specific tools (e.g., notepad.exe). There is no mention of Bash, shell scripting, or Linux-native editors, which may hinder Linux or macOS users.
Recommendations:
  • Add equivalent Azure CLI (az) command examples for all PowerShell steps, as Azure CLI is cross-platform and widely used on Linux and macOS.
  • Replace or supplement references to Windows-only tools (e.g., 'notepad.exe') with cross-platform alternatives (e.g., 'nano', 'vim', or 'code'), or use generic language like 'open the file in your preferred text editor'.
  • Explicitly mention that the steps can be performed on Linux/macOS using Azure CLI and standard text editors.
  • Where possible, provide Bash script snippets or guidance for users on non-Windows platforms.
  • Review all prerequisites and instructions to ensure they are not assuming a Windows environment by default.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/howto-load-balancer-imds.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Windows First Windows Tools Powershell Heavy
Summary:
The documentation page demonstrates a Windows-first bias by listing Windows/PowerShell instructions and links before Linux equivalents. The prerequisites and important notes reference Windows-specific documentation and tools (PowerShell, -NoProxy), and the sample request is presented for Windows before Linux. There is a heavier emphasis on PowerShell-specific parameters and troubleshooting, while Linux instructions are present but less detailed.
Recommendations:
  • Provide Linux and Windows instructions in parallel, or list Linux first where appropriate.
  • Ensure all prerequisite and troubleshooting links have Linux equivalents and are not Windows-specific.
  • Expand Linux sections to include notes about proxy bypassing and curl options, matching the detail given for PowerShell.
  • Use neutral language and cross-platform links in introductory and prerequisite sections.
  • Where possible, provide a combined or platform-agnostic example before platform-specific tabs.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/load-balancer-troubleshoot-backend-traffic.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example
Summary:
The documentation provides troubleshooting steps that reference Windows-specific tools (e.g., 'netstat' in a command prompt) and does not include equivalent Linux commands or examples. This may make it less accessible for users managing Linux-based Azure VMs.
Recommendations:
  • For each troubleshooting step involving command-line validation (such as checking listening ports), provide both Windows and Linux examples. For example, alongside 'netstat -an' in Windows, include 'ss -tuln' or 'netstat -tuln' for Linux.
  • Avoid assuming the use of Windows command prompt; instead, refer to 'terminal' or 'shell' generically, and specify both environments where appropriate.
  • Where tools or commands are mentioned, offer parity by listing the Linux equivalent either alongside or immediately after the Windows example.
  • Review the documentation for other implicit Windows-centric language or workflows and ensure Linux users are equally supported.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/backend-pool-management.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Windows Tools
Summary:
The documentation demonstrates a Windows bias by presenting PowerShell examples first and in greater detail, using Windows-centric tools and patterns (e.g., New-AzVMConfig with Windows image), and referencing Windows-specific VM images in PowerShell examples. Linux parity is only partially addressed in the CLI section, and the PowerShell section lacks Linux VM creation examples.
Recommendations:
  • Provide both Windows and Linux VM creation examples in PowerShell, not just Windows.
  • Alternate the order of PowerShell and CLI sections or present them in parallel to avoid 'windows_first' bias.
  • Explicitly mention cross-platform compatibility of Azure PowerShell and show Linux image usage in PowerShell examples (e.g., Set-AzVMOperatingSystem -Linux).
  • Ensure that CLI examples are as detailed as PowerShell ones, including retrieval and update operations.
  • Add a note clarifying that both PowerShell and CLI are cross-platform and can be used on Windows, Linux, and macOS.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/basic/quickstart-basic-public-load-balancer-portal.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example Powershell Heavy Windows Tools
Summary:
The documentation page demonstrates a clear Windows bias, especially in the 'Install IIS' section, where only Windows Server VMs and PowerShell commands are provided. There are no instructions or examples for deploying Linux VMs or installing a web server (such as Apache or Nginx) on Linux. The VM creation steps default to Windows Server images, and all post-deployment configuration is Windows-specific, with no Linux parity.
Recommendations:
  • Add parallel instructions for creating Linux VMs (e.g., using Ubuntu or CentOS images) alongside the Windows VM steps.
  • Provide Linux-specific examples for installing a web server (such as Apache or Nginx) using bash commands (e.g., apt or yum) and updating the default web page.
  • Include both Windows and Linux options in the 'Image' selection step when creating VMs.
  • Show both PowerShell and bash/SSH command examples for post-deployment configuration.
  • Explicitly mention that the quickstart supports both Windows and Linux, and provide links to Linux-focused tutorials if available.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/basic/virtual-network-ipv4-ipv6-dual-stack-cli.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example
Summary:
The documentation provides only Windows-based VM deployment examples (using MicrosoftWindowsServer images) and does not include any Linux VM examples. There are no Linux-specific instructions, images, or notes, and the only OS-specific step (VM creation) defaults to Windows. No PowerShell or Windows-only CLI commands are present, but the lack of Linux parity in examples is a clear bias.
Recommendations:
  • Add parallel Linux VM creation examples using popular distributions (e.g., Ubuntu, CentOS) alongside the Windows examples.
  • Include a note or section explaining how to select Linux images with az vm create, and provide sample image URNs.
  • Where OS-specific steps are required (such as RDP vs SSH), provide both Windows (RDP) and Linux (SSH) network security group rule examples.
  • Clarify in the prerequisites or introduction that the instructions apply to both Windows and Linux, and highlight any differences.
  • Consider alternating the order of Windows and Linux examples or presenting them side-by-side to avoid implicit prioritization.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/cross-subscription-how-to-internal-load-balancer.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First
Summary:
The documentation presents Azure PowerShell instructions before Azure CLI, with detailed PowerShell cmdlet explanations and a full script, while the Azure CLI section is less detailed. There are no Linux-specific tools or shell examples, and the PowerShell focus may implicitly favor Windows users.
Recommendations:
  • Provide Bash/Linux shell examples alongside PowerShell, especially for Azure CLI commands.
  • Consider presenting Azure CLI examples before or alongside PowerShell, as CLI is cross-platform and more familiar to Linux users.
  • Explicitly mention that both PowerShell and CLI are cross-platform, and clarify which environments are supported.
  • Balance the level of detail between PowerShell and CLI sections, ensuring parity in explanations and context.
  • Where possible, include references to Linux-native scripting or automation approaches (e.g., Bash scripts) for common tasks.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/basic/quickstart-basic-internal-load-balancer-cli.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example Powershell Heavy Windows Tools
Summary:
The documentation demonstrates a strong Windows bias. All virtual machine creation examples use Windows Server images (win2019datacenter), and the only provided instructions for configuring backend servers use PowerShell commands to install IIS (a Windows web server) via the CustomScriptExtension. There are no Linux VM examples, nor are there instructions for installing or configuring a web server on Linux. Additionally, the test instructions reference Internet Explorer, a Windows-only browser, and do not mention Linux alternatives.
Recommendations:
  • Provide parallel examples for Linux virtual machines, such as using Ubuntu or CentOS images in the az vm create commands.
  • Include instructions for installing and configuring a web server (e.g., Apache or Nginx) on Linux VMs using the CustomScriptExtension with bash commands.
  • When referencing tools or browsers for testing (e.g., Internet Explorer), also mention Linux-compatible alternatives such as Firefox or Chromium.
  • Ensure that all scripts and automation steps have both Windows and Linux variants, and clearly label them.
  • Consider alternating the order of Windows and Linux examples or presenting them side-by-side to avoid 'windows_first' bias.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/cross-subscription-how-to-attach-frontend.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Windows Tools
Summary:
The documentation page demonstrates a Windows bias by consistently presenting Azure PowerShell (typically used on Windows and in PowerShell environments) instructions and examples before Azure CLI (which is cross-platform and more common on Linux/macOS). The prerequisites and all procedural steps are introduced with PowerShell first, and the documentation metadata includes 'devx-track-azurepowershell', further emphasizing PowerShell. There are no Bash, Linux shell, or platform-specific notes for Linux users, and no mention of Linux tools or patterns. While Azure CLI examples are present, the overall structure and emphasis favor Windows/PowerShell users.
Recommendations:
  • Alternate the order of PowerShell and CLI examples, or present CLI first to balance platform representation.
  • Explicitly mention that both PowerShell and CLI are cross-platform, but highlight that CLI is often preferred on Linux/macOS.
  • Add Bash shell snippets or Linux-specific notes where relevant, especially for environment setup and authentication.
  • Remove or balance metadata tags (such as 'devx-track-azurepowershell') to reflect equal support for CLI.
  • Where possible, provide context or links for Linux users (e.g., installing Azure CLI on Linux, using Bash scripting).
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/basic/quickstart-basic-internal-load-balancer-portal.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example Windows Tools Powershell Heavy
Summary:
The documentation demonstrates a strong Windows bias. All VM creation steps use Windows Server images by default, and there are no Linux alternatives or examples provided. The IIS installation and configuration steps are exclusively shown using Windows PowerShell commands, with no mention of how to perform similar tasks on Linux VMs (e.g., using Apache or Nginx with Bash commands). Windows-specific tools and patterns (such as Internet Explorer, Windows PowerShell, and Windows Administrative Tools) are referenced throughout, with no Linux equivalents or parity.
Recommendations:
  • Provide parallel instructions for creating Linux VMs (e.g., Ubuntu or CentOS) alongside Windows Server, including screenshots or configuration tables.
  • Include Linux-specific steps for installing a web server (such as Apache or Nginx) using Bash commands (e.g., apt or yum), and show how to create a custom index.html file.
  • Demonstrate how to connect to Linux VMs using SSH via Azure Bastion, and provide example commands for Linux terminal usage.
  • When referencing tools (e.g., PowerShell, Internet Explorer), also mention Linux alternatives (e.g., Bash, Firefox, or curl).
  • Ensure that all code snippets and configuration steps have both Windows and Linux variants, or clearly indicate if a step is Windows-only and provide guidance for Linux users.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/basic/quickstart-basic-public-load-balancer-cli.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example Powershell Heavy
Summary:
The documentation demonstrates Windows bias primarily by provisioning only Windows Server virtual machines (using the 'win2019datacenter' image) and providing an IIS installation example that exclusively uses PowerShell commands. There are no Linux VM creation examples or instructions for installing a web server on Linux, and the only web server setup shown is for Windows/IIS. This omits guidance for users who wish to use Linux-based backend servers.
Recommendations:
  • Provide parallel examples for creating Linux virtual machines (e.g., using the 'UbuntuLTS' image) alongside the Windows VM examples.
  • Include instructions and sample commands for installing a web server (such as Apache or Nginx) on Linux VMs using the CustomScriptExtension or cloud-init.
  • Present both Windows and Linux options for backend server setup, making it clear that either OS is supported.
  • Where scripts or commands are provided (e.g., for web server installation), offer both PowerShell (for Windows) and Bash/shell (for Linux) equivalents.
  • Explicitly mention that the load balancer works with both Windows and Linux VMs, and link to relevant Linux documentation where appropriate.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/basic/quickstart-basic-internal-load-balancer-powershell.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Missing Linux Example Windows Tools
Summary:
The documentation is heavily biased towards Windows and PowerShell. All examples use Azure PowerShell cmdlets, and the only operating system referenced for VM creation and configuration is Windows Server. Steps for installing IIS and testing the load balancer are specific to Windows (e.g., using PowerShell commands, Internet Explorer, and Windows-specific VM images). There are no equivalent instructions or examples for Linux users, such as using Azure CLI, Bash, or deploying Linux VMs and web servers (e.g., Apache or Nginx).
Recommendations:
  • Provide parallel examples using Azure CLI (az commands) and Bash scripts for all resource creation and configuration steps.
  • Include instructions and code samples for deploying Linux-based VMs (e.g., Ubuntu) in the backend pool, with examples of installing and configuring a Linux web server (such as Apache or Nginx) using cloud-init or custom script extensions.
  • When demonstrating VM creation, show both Windows and Linux image options, and explain how to set up credentials for each.
  • In the 'Test the load balancer' section, describe how to connect to a Linux VM (e.g., using SSH via Bastion or Cloud Shell) and test the web server using curl or a browser.
  • Avoid referencing Windows-only tools (like Internet Explorer) as the default; mention cross-platform alternatives.
  • Consider restructuring the documentation to present both Windows and Linux paths side-by-side, or provide clear navigation to Linux-specific quickstarts.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/concepts.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Windows First Windows Tools Missing Linux Example
Summary:
The documentation page demonstrates subtle Windows bias by referencing the creation of VMs with a custom IIS extension installed in the 'Next steps' section. IIS is a Windows-specific web server, and there is no mention of Linux-based alternatives or examples. There are no Linux-specific tools, patterns, or examples provided, nor is there parity in guidance for Linux users.
Recommendations:
  • Include examples or references for deploying Linux-based VMs and web servers (such as Apache or Nginx) in the 'Next steps' section.
  • When mentioning IIS or Windows-specific technologies, also mention equivalent Linux options to ensure parity.
  • Provide links or guidance for both Windows and Linux scenarios when describing setup or configuration steps.
  • Review other documentation pages linked from this one to ensure Linux users are equally supported throughout the workflow.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/cross-subscription-how-to-attach-backend.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First
Summary:
The documentation presents both Azure PowerShell and Azure CLI examples, but the PowerShell section is listed first and is more detailed, including step-by-step resource creation and variable usage. The CLI section is briefer and less explanatory. There are no Linux-specific tools or shell examples (e.g., Bash scripts), and no mention of Linux environments or considerations. The focus on PowerShell and its placement before CLI may indicate a subtle Windows bias.
Recommendations:
  • Alternate the order of PowerShell and CLI sections, or present CLI (which is cross-platform) first to avoid the impression of Windows-first bias.
  • Ensure that CLI examples are as detailed and explanatory as the PowerShell ones, including step-by-step resource creation and variable usage.
  • Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and consider including Bash shell scripting examples where appropriate.
  • If relevant, add troubleshooting or environment setup notes for Linux users.
  • Review included content (via [!INCLUDE]) to ensure parity in instructions and examples for both Windows and Linux environments.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/egress-only.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example
Summary:
The documentation demonstrates a Windows bias by exclusively using Windows Server as the virtual machine image in the example and referencing Microsoft Edge as the browser to test connectivity. There are no Linux VM creation steps, nor are there instructions for Linux users to test outbound connectivity. The only administrator account option shown is username/password (no mention of SSH keys, which are standard for Linux).
Recommendations:
  • Provide parallel instructions for creating a Linux virtual machine (e.g., Ubuntu) alongside the Windows example, including appropriate image selection and authentication (SSH key).
  • Include Linux-specific steps for testing outbound connectivity, such as using curl or wget from the command line, instead of (or in addition to) opening a browser.
  • Mention both Windows and Linux options when referencing tools or actions (e.g., 'Open Microsoft Edge or your preferred browser' or 'use curl/wget').
  • Clarify that the steps apply to both Windows and Linux VMs, and highlight any differences in configuration or testing.
  • When referencing administrator account creation, include SSH key authentication as an option for Linux VMs.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/cross-subscription-how-to-global-backend.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Windows First Powershell Heavy
Summary:
The documentation consistently presents Azure PowerShell (a Windows-centric tool) instructions and examples before Azure CLI (cross-platform) equivalents in every section. The structure and language reinforce PowerShell as the primary or default approach, which can be perceived as a Windows-first bias. However, both PowerShell and CLI examples are provided throughout, and there are no missing Linux examples or exclusive references to Windows-only tools beyond PowerShell.
Recommendations:
  • Alternate the order of PowerShell and CLI tabs in different sections to avoid always privileging PowerShell.
  • Explicitly mention that both Azure PowerShell and Azure CLI are cross-platform, and that users on Linux/macOS can use the CLI or PowerShell Core.
  • Add a short note at the start clarifying that all steps can be performed on Linux, macOS, or Windows using the Azure CLI or PowerShell Core.
  • Consider providing Bash script examples or references for Linux users where appropriate.
  • Avoid language that implies PowerShell is the default or preferred method, and instead present both options as equally valid.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/ipv6-add-to-existing-vnet-powershell.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Missing Linux Example Windows Tools Windows First
Summary:
The documentation is heavily biased towards Windows and PowerShell usage. All examples and instructions are provided exclusively using Azure PowerShell cmdlets, with no mention of Azure CLI, Bash, or Linux-native tooling. The prerequisites and setup steps assume a PowerShell environment, and there are no alternative instructions for Linux users or those preferring cross-platform tools. The title and structure reinforce PowerShell as the default or only method.
Recommendations:
  • Provide parallel examples using Azure CLI (az) commands, which are cross-platform and commonly used on Linux and macOS.
  • Include a section or callout at the beginning clarifying that the steps can be performed using either PowerShell or Azure CLI, and link to both sets of instructions.
  • Where possible, use neutral terminology (e.g., 'command line' instead of 'PowerShell') in headings and introductory text.
  • Add Linux/Bash-specific notes for any environment setup or prerequisites, such as installing Azure CLI or using the Azure Cloud Shell in Bash mode.
  • Ensure that all referenced tools and modules have Linux-compatible alternatives or clearly state if a step is Windows/PowerShell-only.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/instance-metadata-service-load-balancer.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example
Summary:
The documentation page demonstrates a subtle Windows bias. The 'Next steps' section links only to the Windows-specific Azure Instance Metadata Service documentation, with no mention or link to the Linux equivalent. There are no code examples, but the reference to Windows documentation without Linux parity suggests a preference or assumption of Windows usage.
Recommendations:
  • Include links to both Windows and Linux versions of the Azure Instance Metadata Service documentation in the 'Next steps' section.
  • Explicitly mention that the IMDS REST API is platform-agnostic and provide examples or references for both Windows (e.g., PowerShell, CMD) and Linux (e.g., curl, bash) usage where appropriate.
  • Ensure that troubleshooting and usage guides are inclusive of both Windows and Linux environments.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/load-balancer-distribution-mode.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Missing Linux Example
Summary:
The documentation provides detailed instructions for configuring Azure Load Balancer distribution mode using the Azure portal, PowerShell, and Azure CLI. However, it shows a Windows bias by presenting PowerShell instructions before CLI, referencing a PowerShell-based quickstart in the 'Next steps', and not providing explicit Linux/Bash examples or guidance. The CLI section is generic and does not clarify cross-platform usage, and there are no Bash or Linux-specific notes or troubleshooting tips.
Recommendations:
  • Add explicit Bash/Linux shell examples for the Azure CLI section, including sample commands and expected outputs.
  • Clarify that Azure CLI commands work cross-platform and provide any Linux-specific prerequisites or troubleshooting tips.
  • Balance the order of examples by presenting CLI (cross-platform) instructions before or alongside PowerShell, or clearly indicate platform applicability.
  • Include a 'Next steps' link to a Linux/Bash-based quickstart or tutorial, not just PowerShell.
  • If relevant, mention any differences in behavior or setup between Windows and Linux environments.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/gateway-deploy-dual-stack-load-balancer.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Windows First Powershell Heavy
Summary:
The documentation consistently presents PowerShell (a Windows-centric tool) examples before Azure CLI examples in every procedural section. This ordering and the heavy use of PowerShell may suggest a bias toward Windows users, even though all steps are also provided for Azure CLI (which is cross-platform). There are no Linux-specific tools or shell examples (e.g., Bash scripts), and no mention of Linux environments or considerations.
Recommendations:
  • Alternate the order of example tabs, sometimes presenting Azure CLI before PowerShell, or default to CLI as it is cross-platform.
  • Explicitly mention that Azure CLI commands can be run on Linux, macOS, and Windows, and provide Bash shell context where appropriate.
  • Add a brief section or note for Linux users, clarifying that all CLI steps are fully supported on Linux and macOS.
  • Consider including sample Bash scripts or guidance for automating these steps in Linux environments.
  • Avoid implying PowerShell is the primary or preferred method unless there is a technical reason.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/load-balancer-basic-upgrade-guidance.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows Tools Missing Linux Example Windows First
Summary:
The documentation page demonstrates a Windows bias by exclusively recommending and providing PowerShell scripts for automation, with no mention of Azure CLI, Bash, or Linux-native tooling. The 'automated scripts' section only references PowerShell, and the manual steps reference the Azure Portal (which is cross-platform, but the automation focus is Windows-centric). There are no Linux or cross-platform command-line examples, and the guidance implicitly assumes a Windows/PowerShell environment.
Recommendations:
  • Provide equivalent Azure CLI scripts/examples for all PowerShell automation steps, ensuring Linux and macOS users have parity.
  • Explicitly mention that automation can be performed using Azure CLI or ARM templates, not just PowerShell.
  • When referencing 'automated scripts', offer both PowerShell and Azure CLI/Bash options, and link to relevant documentation for each.
  • Ensure that any step recommending PowerShell also includes a Linux-friendly alternative, or at least acknowledges the option.
  • Consider reordering or presenting automation options in a neutral way (e.g., 'Use these scripts: PowerShell | Azure CLI'), rather than PowerShell-only.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/load-balancer-floating-ip.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Windows First Windows Tools
Summary:
The documentation presents Windows Server configuration instructions before Ubuntu/Linux, and uses Windows-specific tools (netsh, Windows firewall) in both the main text and examples. The only detailed scenario link provided is for Windows (SQL AG listener with PowerShell). Linux instructions are present but appear after Windows, and the Linux scenario is less emphasized.
Recommendations:
  • Alternate the order of Windows and Linux/Ubuntu sections, or present them side-by-side to avoid the perception of Windows primacy.
  • Include links to Linux-based scenario documentation (e.g., configuring Always On AG listeners on Linux VMs).
  • When mentioning tools or patterns (e.g., firewall configuration), give equal detail and prominence to both Windows and Linux equivalents.
  • Use more generic language in introductory sections (e.g., 'Windows and Linux systems require...') rather than focusing on Windows first.
  • Expand the 'limitations' and scenario sections to explicitly mention Linux-specific considerations or references.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/load-balancer-custom-probe-overview.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Missing Linux Example
Summary:
The documentation page exhibits Windows bias primarily through its 'Next steps' section, which features a PowerShell-based quickstart as the only explicit example for creating a public load balancer. There are no Linux/Unix CLI (Azure CLI, Bash) examples or references, and no mention of Linux-specific tools or workflows. The documentation does not provide parity for Linux users in terms of example commands or guidance, and the only automation example is Windows-centric (PowerShell).
Recommendations:
  • Add Azure CLI (cross-platform) examples alongside or before PowerShell examples for all relevant tasks, especially in the 'Next steps' and any quickstart sections.
  • Include Bash or shell command examples where appropriate, especially for probe testing or firewall configuration.
  • Ensure that references to automation or scripting tools are balanced between Windows (PowerShell) and Linux (Azure CLI, Bash).
  • Explicitly mention that all configuration steps can be performed on both Windows and Linux platforms, and provide links to Linux-focused tutorials or documentation.
  • Review all example links and ensure that for every PowerShell example, there is an equivalent Azure CLI or Linux shell example.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/load-balancer-manage-health-status.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Windows Tools Powershell Heavy Missing Linux Example Windows First
Summary:
The documentation page demonstrates a Windows bias by referencing the PowerShell cmdlet Get-AzAccessToken as the only example for obtaining a Bearer access token, without mentioning equivalent Linux or cross-platform CLI methods. No Azure CLI, Bash, or Linux-native instructions are provided for authentication or token retrieval. The only tool referenced for token acquisition is a Windows-centric PowerShell module, and no Linux-first or cross-platform alternatives are presented.
Recommendations:
  • Add Azure CLI examples (e.g., 'az account get-access-token') for obtaining the Bearer access token, which works cross-platform (Windows, Linux, macOS).
  • Include Bash shell command examples for REST API calls using curl, demonstrating how to authenticate and retrieve health status from Linux environments.
  • Mention both PowerShell and CLI methods in parallel, or present CLI/Bash examples before or alongside PowerShell to avoid a 'Windows-first' impression.
  • Explicitly state that the REST API and Azure CLI methods are supported on all platforms, and provide links to relevant Linux/macOS documentation.
  • Where possible, avoid referencing only Windows-specific tools (like Get-AzAccessToken) without cross-platform alternatives.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/ipv6-dual-stack-standard-internal-load-balancer-powershell.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Missing Linux Example Windows Tools Windows First
Summary:
The documentation is heavily biased towards Windows and PowerShell. All examples use Azure PowerShell cmdlets, with no mention of Azure CLI, Bash, or Linux-based workflows. The VM creation steps specifically use Windows Server images, and the only remote access method shown is RDP (port 3389), which is Windows-specific. There are no Linux VM examples, nor are there instructions for SSH or Linux image deployment. The documentation assumes the user is working in a Windows/PowerShell environment throughout.
Recommendations:
  • Provide parallel examples using Azure CLI (az commands) and Bash scripts for all resource creation steps.
  • Include Linux VM deployment examples (e.g., using Ubuntu or CentOS images) alongside or instead of Windows Server.
  • Show how to configure SSH access (port 22) in the network security group rules, not just RDP.
  • Explicitly mention that the steps can be performed from Linux/macOS using Azure CLI or Cloud Shell, and provide relevant instructions.
  • Reorganize the documentation to present cross-platform options equally, rather than focusing exclusively on PowerShell/Windows.
  • Add a section or callout for Linux users, highlighting any differences or considerations.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/load-balancer-multiple-ip.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/load-balancer-tcp-reset.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Windows Tools Missing Linux Example
Summary:
The documentation page references .NET examples for TCP keep-alive configuration, which is a Windows-centric technology, and does not provide equivalent Linux or cross-platform examples. There are no PowerShell or explicit Windows command-line examples, but the only code reference is Windows-specific. No Linux tools, commands, or configuration patterns are mentioned.
Recommendations:
  • Add examples or references for configuring TCP keep-alive on Linux, such as sysctl settings (e.g., net.ipv4.tcp_keepalive_time) or using tools like socat or iptables.
  • Include cross-platform code samples, such as Python or Java, to demonstrate TCP keep-alive configuration in a way that is not tied to Windows/.NET.
  • If referencing .NET, also mention Mono or .NET Core on Linux, or provide a parallel example for Linux environments.
  • Explicitly mention how to check or configure TCP keep-alive and idle timeout on both Windows and Linux endpoints.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/deploy-ipv4-ipv6-dual-stack-standard-load-balancer.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/load-balancer-test-frontend-reachability.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/load-balancer-nat-pool-migration.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/load-balancer-troubleshoot-health-probe-status.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/load-balancer-tcp-idle-timeout.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/load-balancer-troubleshoot.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/quickstart-load-balancer-standard-internal-bicep.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/manage-inbound-nat-rules.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

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).
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/quickstart-load-balancer-standard-internal-cli.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/monitor-load-balancer.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First
Summary:
The documentation provides extensive PowerShell examples for configuring diagnostic settings, with detailed, step-by-step scripts for each scenario (Log Analytics, Storage Account, Event Hub). The PowerShell section is presented before the Azure CLI section, which is more commonly used on Linux and macOS. There are no examples using Bash scripting or Linux-specific tools, and no mention of cross-platform shell considerations. While Azure CLI examples are present, the prominence and depth of PowerShell coverage, as well as its placement before CLI, indicate a Windows-first and PowerShell-heavy bias.
Recommendations:
  • Present Azure CLI examples before PowerShell examples, as Azure CLI is cross-platform and more widely used on Linux/macOS.
  • Add Bash script examples or notes on running Azure CLI commands in Linux/macOS environments.
  • Explicitly mention that both PowerShell and Azure CLI are supported on all platforms, and clarify any OS-specific requirements.
  • Where possible, provide parity in the level of detail and explanation between PowerShell and Azure CLI sections.
  • Consider including a table or section comparing the commands in PowerShell, Azure CLI, and Bash to highlight cross-platform support.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/quickstart-load-balancer-standard-public-portal.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/quickstart-load-balancer-standard-internal-template.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/quickstart-load-balancer-standard-internal-portal.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/quickstart-load-balancer-standard-public-bicep.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/quickstart-load-balancer-standard-public-template.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/manage-admin-state-how-to.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example
Summary:
The documentation consistently references and links to Windows-based virtual machine creation guides in all prerequisite sections, omitting Linux VM equivalents. All examples and instructions are provided in Azure Portal, Azure PowerShell, and Azure CLI formats, but there are no explicit Linux-specific instructions, notes, or examples. This results in a subtle but clear bias toward Windows environments, especially for users looking for Linux parity in VM setup and management.
Recommendations:
  • In the prerequisites for each method, provide links to both Windows and Linux VM creation guides (e.g., /azure/virtual-machines/linux/quick-create-portal and /azure/virtual-machines/linux/quick-create-cli) alongside the Windows links.
  • Explicitly mention that the Azure CLI examples are cross-platform and can be run on Linux, macOS, and Windows, and consider adding a note or example showing CLI usage in a Linux shell (e.g., bash).
  • Where relevant, clarify any differences or additional steps for Linux VMs (for example, if NIC-based pools or IP configuration steps differ).
  • Ensure that all references to VM creation, management, and Azure CLI usage are inclusive of Linux users, not just Windows.
  • Consider adding a short section or callout for Linux users, highlighting any Linux-specific considerations or confirming that the instructions are fully applicable to Linux environments.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/quickstart-load-balancer-standard-public-cli.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/tutorial-multi-availability-sets-portal.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/troubleshoot-load-balancer-imds.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/tutorial-deploy-cross-region-load-balancer-template.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/troubleshoot-rhc.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example
Summary:
The documentation demonstrates a subtle Windows bias by referencing Windows-specific troubleshooting content before Linux equivalents and providing a Windows command prompt example before the Linux equivalent. Additionally, when linking to further troubleshooting resources, only a Windows VM high-CPU troubleshooting guide is referenced, with no Linux counterpart provided.
Recommendations:
  • When mentioning OS-level troubleshooting (e.g., checking CPU utilization), provide links for both Windows and Linux VM troubleshooting guides.
  • When giving command-line examples (such as checking listening ports), present both Windows and Linux commands side by side, or alternate the order to avoid always listing Windows first.
  • Ensure that all troubleshooting steps and external references are equally available for both Windows and Linux environments.
  • Explicitly mention that the guidance applies to both Windows and Linux VMs, and provide OS-agnostic instructions where possible.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/tutorial-gateway-outbound-connectivity.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example
Summary:
The documentation page demonstrates a Windows bias by referencing only the creation of a Windows VM in the prerequisites and not mentioning Linux VM equivalents. There are no Linux-specific instructions, examples, or links provided, and the only VM deployment link is for Windows. This may lead Linux users to feel unsupported or unclear about the process for their platform.
Recommendations:
  • Include a link to the official documentation for creating a Linux VM in Azure alongside the Windows VM link in the prerequisites section.
  • Explicitly state that the instructions apply to both Windows and Linux VMs, unless there are platform-specific differences.
  • If there are any platform-specific steps (e.g., for verifying network configuration inside the VM), provide examples for both Windows (PowerShell, GUI) and Linux (bash, CLI).
  • Review all example names and instructions to ensure they are platform-neutral or provide parallel examples for both Windows and Linux environments.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/tutorial-add-lb-existing-scale-set-portal.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example
Summary:
The documentation demonstrates Windows bias by exclusively using Windows Server as the image for the virtual machine scale set and omitting any mention or example of Linux-based deployments. There are no Linux options or guidance for users who may wish to deploy Linux VM scale sets, and all instructions assume a Windows environment.
Recommendations:
  • Include Linux as an alternative in the 'Image' selection step, such as 'Ubuntu Server 22.04 LTS' or another popular distribution.
  • Provide parallel instructions or notes for Linux-based deployments, including any differences in configuration or recommended settings.
  • Add a brief section or callout explaining that both Windows and Linux VM images are supported, with links to relevant documentation for each.
  • Ensure screenshots and example values reflect both Windows and Linux options where appropriate.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/tutorial-protect-load-balancer-ddos.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/tutorial-cross-region-portal.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/tutorial-load-balancer-ip-backend-portal.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/tutorial-load-balancer-port-forwarding-portal.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Windows First Powershell Heavy
Summary:
The documentation demonstrates a mild Windows bias, primarily by mentioning Windows/PowerShell before Linux/Bash in instructions for connecting to VMs. The SSH command examples use Windows-style paths (backslashes) and reference PowerShell, with Linux/Mac users mentioned secondarily. No explicit Linux tools or commands are omitted, but the ordering and example formatting favor Windows users.
Recommendations:
  • Present Linux/Bash and Windows/PowerShell instructions in parallel, or alternate which is mentioned first.
  • Use platform-neutral path examples (e.g., ./Downloads/lb-key-pair.pem) or provide both Windows and Linux/Mac variants.
  • Explicitly show both Bash and PowerShell prompts and commands where relevant.
  • Add a note clarifying differences in path separators and shell usage between platforms.
  • Ensure that any screenshots or command snippets do not implicitly assume a Windows environment.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/tutorial-load-balancer-standard-public-zonal-portal.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Missing Linux Example Windows Tools
Summary:
The tutorial includes a step to create a basic Internet Information Services (IIS) site, which is a Windows-specific web server. There is no mention of Linux-based alternatives (such as Apache or Nginx), nor are there instructions for setting up a Linux VM or web server. The documentation implicitly assumes the use of Windows VMs and tools, with no parity for Linux users.
Recommendations:
  • Provide parallel instructions for deploying a Linux VM and installing a common Linux web server (e.g., Apache or Nginx) alongside the IIS example.
  • Explicitly mention that IIS is Windows-specific and offer a Linux alternative in the tutorial steps.
  • Ensure that screenshots, sample commands, and configuration steps are available for both Windows and Linux scenarios.
  • Consider including a section or callout box that highlights cross-platform options for web server setup within the load balancer context.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/tutorial-nat-rule-multi-instance-portal.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/whats-new.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

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.