Load Balancer
104
Total Pages
41
Linux-Friendly Pages
63
Pages with Bias
60.6%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
388 issues found
Showing 351-375 of 388 flagged pages
Load Balancer
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/manage-admin-state-how-to.md
...in/articles/load-balancer/manage-admin-state-how-to.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation consistently references 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.
Create Pull Request
Load Balancer
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/troubleshoot-rhc.md
...s/blob/main/articles/load-balancer/troubleshoot-rhc.md
Medium Priority
View Details →
Detected Bias Types
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.
Load Balancer
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/tutorial-gateway-outbound-connectivity.md
...oad-balancer/tutorial-gateway-outbound-connectivity.md
Medium Priority
View Details →
Detected Bias Types
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.
Load Balancer
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/tutorial-add-lb-existing-scale-set-portal.md
...-balancer/tutorial-add-lb-existing-scale-set-portal.md
Medium Priority
View Details →
Detected Bias Types
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.
Load Balancer
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/tutorial-load-balancer-port-forwarding-portal.md
...ancer/tutorial-load-balancer-port-forwarding-portal.md
Medium Priority
View Details →
Detected Bias Types
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.
Load Balancer
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/tutorial-load-balancer-standard-public-zonal-portal.md
...ttps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/tutorial-load-balancer-standard-public-zonal-portal.md
Medium Priority
View Details →
Detected Bias Types
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.
Load Balancer
Tutorial: Create a single virtual machine inbound NAT rule - Azure portal
...ancer/tutorial-load-balancer-port-forwarding-portal.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides instructions for both Linux/macOS and Windows users when connecting via SSH, but Windows/PowerShell is mentioned first and the SSH example uses Windows path notation ('.\Downloads\lb-key-pair.pem'). There are no Linux-specific tools or patterns missing, but the ordering and example syntax favor Windows users slightly.
Recommendations
- Present Linux/macOS and Windows instructions in parallel or alternate which is shown first.
- Provide SSH command examples with both Linux/macOS and Windows path syntax, e.g., '~/Downloads/lb-key-pair.pem' for Linux/macOS.
- Clarify that the SSH command works on all platforms and adjust the example to be platform-neutral if possible.
Load Balancer
Tutorial: Create a single virtual machine inbound NAT rule - Azure portal
...ancer/tutorial-load-balancer-port-forwarding-portal.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides SSH connection instructions for both Mac/Linux (Bash) and Windows (PowerShell) users, but the SSH command examples use Windows path notation (backslashes) and show the Windows-style example first. There are no PowerShell-specific commands or Windows-only tools mentioned, and the tutorial is otherwise platform-neutral.
Recommendations
- Provide both Windows and Linux/macOS SSH command examples, with correct path notation for each (e.g., use './Downloads/lb-key-pair.pem' for Linux/macOS and '.\Downloads\lb-key-pair.pem' for Windows).
- Explicitly show the Bash/Linux/macOS example first, or present both side-by-side.
- Clarify that the SSH command syntax may differ slightly depending on the user's OS and shell.
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Summary
The documentation does not provide any OS-specific examples, but all references to connecting to VMs and managing NAT rules are generic and do not mention Windows or Linux tools. However, the absence of command-line examples (such as PowerShell, Azure CLI, or SSH) means Linux/macOS users do not see parity or guidance for their platforms. Additionally, the tutorials and guidance focus on the Azure portal, which is platform-agnostic but often associated with Windows-first workflows.
Recommendations
- Add explicit examples for connecting to backend VMs using both Windows (RDP) and Linux (SSH) clients.
- Include Azure CLI and/or Bash examples for managing NAT rules, alongside any PowerShell examples.
- Mention Linux/macOS tools and workflows where relevant, such as using SSH from a terminal.
- Ensure tutorials and screenshots reflect both Windows and Linux scenarios.
Load Balancer
Attach a cross-subscription frontend to an Azure Load Balancer
...-balancer/cross-subscription-how-to-attach-frontend.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias by consistently presenting Azure PowerShell (typically used on Windows) examples before Azure CLI, and by providing more detailed PowerShell code samples and context. The prerequisites and instructions reference PowerShell-specific patterns and tools (e.g., Connect-AzAccount, Set-AzContext) before their CLI equivalents, and the page metadata includes 'devx-track-azurepowershell', further emphasizing PowerShell. While Azure CLI examples are present, PowerShell is given priority and more depth.
Recommendations
- Alternate the order of examples so that Azure CLI is shown first in some sections, or present both examples side-by-side.
- Ensure equal detail and explanation for both PowerShell and CLI examples, including troubleshooting and context.
- Add explicit notes about cross-platform compatibility, clarifying that Azure CLI works natively on Linux/macOS.
- Remove or balance metadata tags that prioritize PowerShell (e.g., 'devx-track-azurepowershell') with CLI equivalents.
- Consider including Bash or scripting examples for Linux users where appropriate.
Load Balancer
Attach a cross-subscription backend to an Azure Load Balancer
...d-balancer/cross-subscription-how-to-attach-backend.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides both Azure PowerShell and Azure CLI examples for creating and configuring a cross-subscription Azure Load Balancer. However, the PowerShell (Windows-centric) example is presented first and in greater detail, with step-by-step commands and variable usage, while the Azure CLI (cross-platform) example is more concise and less explanatory. There are no Linux/macOS-specific tools or patterns mentioned, and no explicit Linux/macOS examples or troubleshooting guidance.
Recommendations
- Present Azure CLI examples before PowerShell, or alternate the order to avoid Windows-first bias.
- Expand Azure CLI sections to match the detail and step-by-step guidance provided in the PowerShell examples.
- Include notes or troubleshooting tips for Linux/macOS users, such as shell differences or common issues.
- Explicitly state that Azure CLI is cross-platform and suitable for Linux/macOS, and link to installation guides for those platforms.
- If possible, provide Bash script examples or mention how to adapt commands for Linux/macOS environments.
Load Balancer
Create a global load balancer with cross-subscription backends
...d-balancer/cross-subscription-how-to-global-backend.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation page provides both Azure PowerShell and Azure CLI instructions for all major steps, but PowerShell (a Windows-centric tool) is consistently presented first and in greater detail. The page assumes familiarity with PowerShell and includes more verbose PowerShell code samples, while CLI instructions are shorter and sometimes less descriptive. There is no mention of Linux-specific tools, shell environments, or considerations for macOS users. The use of PowerShell as the primary example and its placement before CLI instructions indicates a mild Windows bias.
Recommendations
- Alternate the order of PowerShell and CLI instructions, or present CLI examples first to better support Linux/macOS users.
- Add explicit notes clarifying that Azure CLI works natively on Linux/macOS and is recommended for those platforms.
- Ensure CLI examples are as detailed and explanatory as PowerShell examples.
- Mention cross-platform shell environments (e.g., Bash, zsh) and provide guidance for users on those systems.
- Consider including links or references to installing Azure CLI on Linux/macOS in the prerequisites.
Load Balancer
Deploy a dual-stack Azure Gateway Load Balancer
...ad-balancer/gateway-deploy-dual-stack-load-balancer.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation consistently presents PowerShell (Windows-centric) examples before Azure CLI examples in every code section. The PowerShell examples are detailed and use Windows-specific cmdlets, which may be unfamiliar or unavailable to Linux/macOS users. While Azure CLI examples are provided for each step, the ordering and emphasis on PowerShell may create friction for non-Windows users.
Recommendations
- Present Azure CLI examples before PowerShell, or alternate the order to avoid implicit prioritization.
- Add a note at the top clarifying that Azure CLI is cross-platform and recommended for Linux/macOS users.
- Consider including Bash or other Linux-native scripting examples where relevant.
- Explicitly state that all tasks can be completed using Azure CLI on any OS.
- Reduce reliance on PowerShell-specific terminology and cmdlets in explanations.
Load Balancer
Retrieve load balancer and virtual machine IP metadata using Azure Instance Metadata Service (IMDS)
...ain/articles/load-balancer/howto-load-balancer-imds.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation page demonstrates a mild Windows bias: Windows/PowerShell examples are presented before Linux/bash equivalents, and links in prerequisites and further reading default to Windows-focused documentation. However, Linux examples are present and functional, so Linux users are not blocked from completing the task.
Recommendations
- Present Linux and Windows examples side-by-side or alternate their order to avoid implicit prioritization.
- Ensure prerequisite and reference links include both Windows and Linux tabs or point to OS-agnostic documentation.
- Explicitly mention that both Windows and Linux are supported and provide parity in troubleshooting and advanced usage sections.
Load Balancer
Configure Azure Load Balancer distribution mode
...icles/load-balancer/load-balancer-distribution-mode.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation provides configuration instructions for Azure Load Balancer using the Azure Portal, PowerShell, and Azure CLI. The PowerShell example is given before the CLI, and PowerShell is a Windows-centric tool. The CLI example is cross-platform, but there is a subtle Windows bias in the ordering and the inclusion of PowerShell. No Linux-specific tools or shell examples are provided, and the CLI instructions do not mention Linux/macOS explicitly.
Recommendations
- Explicitly state that Azure CLI commands work on Linux/macOS and provide example shell environments (e.g., bash).
- Consider providing bash or shell script examples for Linux users where appropriate.
- If PowerShell is included, clarify that PowerShell Core is available cross-platform, or provide links to installation instructions for Linux/macOS.
- Alternate the order of examples, sometimes presenting CLI before PowerShell to avoid Windows-first perception.
- Add a note or section for Linux/macOS users, confirming parity and any platform-specific considerations.
Load Balancer
Configure load balancer TCP reset and idle timeout
...ticles/load-balancer/load-balancer-tcp-idle-timeout.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides configuration instructions for Azure Load Balancer TCP reset and idle timeout using the Azure Portal, PowerShell, and Azure CLI. The PowerShell example is detailed and assumes local installation, which is most common on Windows. The PowerShell tab is presented before the Azure CLI tab, and there is no mention of Bash, Linux, or macOS-specific considerations. While the Azure CLI example is cross-platform, the documentation does not explicitly address Linux/macOS users or provide parity guidance.
Recommendations
- Explicitly mention that Azure CLI commands work on Linux/macOS and provide links to installation guides for those platforms.
- Add Bash or shell script examples for Linux/macOS users where relevant.
- Reorder tabs or examples so that cross-platform tools (Azure CLI) are shown before Windows-specific tools (PowerShell).
- Include notes about PowerShell Core availability on Linux/macOS if PowerShell is recommended.
- Add troubleshooting or environment validation steps specific to Linux/macOS (e.g., verifying az installation on Ubuntu).
Load Balancer
Quickstart: Create an internal Azure load balancer - Bicep
...er/quickstart-load-balancer-standard-internal-bicep.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell instructions for deployment, resource review, and cleanup. However, PowerShell examples are given equal prominence to CLI, which may suggest a Windows-centric approach, as PowerShell is primarily associated with Windows. There is no explicit mention of Linux/macOS-specific considerations, nor are there examples for Bash scripting or shell environments beyond Azure CLI.
Recommendations
- Clarify that Azure CLI commands work natively on Linux/macOS and are cross-platform.
- Indicate that PowerShell Core is available on Linux/macOS, or provide a note about its installation and usage on those platforms.
- Consider listing Azure CLI examples first, as it is the most cross-platform tool.
- Add a brief section or note for Linux/macOS users, confirming parity and pointing to any relevant platform-specific documentation if needed.
Load Balancer
Troubleshoot Azure Load Balancer resource health, frontend, and backend availability problems
...s/blob/main/articles/load-balancer/troubleshoot-rhc.md
Low Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation shows minor Windows bias in the troubleshooting checklist. Specifically, the example for checking listening ports lists the Windows command (`netstat -a`) before the Linux equivalent (`netstat -l`). Additionally, the link for troubleshooting high CPU issues refers only to Azure Windows virtual machines, with no mention of Linux VM troubleshooting resources.
Recommendations
- Present Linux and Windows commands in parallel, or alternate which is listed first.
- Include links to troubleshooting high-CPU issues for Linux virtual machines alongside the Windows VM link.
- Ensure that all troubleshooting steps and examples are provided for both Windows and Linux environments, especially in sections referencing OS-level diagnostics.
Load Balancer
Tutorial: Create a single virtual machine inbound NAT rule - Azure portal
...ancer/tutorial-load-balancer-port-forwarding-portal.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation demonstrates minor Windows bias in the SSH connection instructions. The prompt order is 'Mac or Linux: Bash prompt' and 'Windows: PowerShell prompt', but the SSH command example uses Windows path separators ('.\Downloads\lb-key-pair.pem'), which is PowerShell/Windows-specific. No Linux/macOS command example is given, and the path format may confuse non-Windows users. The rest of the documentation is platform-neutral, focusing on Azure Portal UI and generic commands.
Recommendations
- Provide both Windows (PowerShell) and Linux/macOS (Bash) SSH command examples, with correct path separators for each.
- Explicitly show the Linux/macOS command: 'ssh -i ~/Downloads/lb-key-pair.pem azureuser@20.99.165.176 -p 221'.
- Add a note clarifying path differences between platforms.
- Consider listing Linux/macOS instructions first, or side-by-side, to avoid implicit Windows primacy.
Load Balancer
Tutorial: Create Inbound NAT rule V2 - Azure portal
...ad-balancer/tutorial-nat-rule-multi-instance-portal.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation demonstrates minor Windows bias in the SSH connection instructions: Windows/PowerShell prompts are mentioned before Linux/macOS, and the SSH command uses Windows path syntax ('.\Downloads\myKey.pem') rather than a cross-platform or Linux-style path. However, Linux/macOS users are not blocked from completing the tutorial, and most steps are platform-agnostic.
Recommendations
- Present Linux/macOS instructions before or alongside Windows instructions for command-line steps.
- Use cross-platform path examples in SSH commands (e.g., '~/Downloads/myKey.pem').
- Explicitly show both PowerShell and Bash command examples where relevant.
- Clarify that the Azure portal steps are identical regardless of OS, but command-line steps may differ.
Load Balancer
What's new in Azure Load Balancer
...ure-docs/blob/main/articles/load-balancer/whats-new.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation page for Azure Load Balancer 'What's New' shows minor evidence of Windows bias. Notably, the IPv6 support feature links to a guide specifically for creating a dual stack application using PowerShell, which is most commonly used on Windows. There are no explicit Linux/macOS examples or references to Linux-native tools, and the only command-line example referenced is PowerShell-based. However, the majority of the page is release notes and feature descriptions, which are platform-neutral, and there are no critical sections that are Windows-only.
Recommendations
- Where command-line examples are referenced (e.g., dual stack application creation), provide equivalent instructions for Azure CLI and/or Bash scripts, which are cross-platform and widely used on Linux/macOS.
- Ensure that links to how-to guides or tutorials include both PowerShell and Azure CLI/Bash options, or clarify that the instructions are applicable across platforms.
- Add explicit notes or links for Linux/macOS users where relevant, especially in sections that currently reference Windows-centric tools or workflows.
Load Balancer
Guidance for virtual machine scale sets with Azure Standard Load Balancer
...r/load-balancer-standard-virtual-machine-scale-sets.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation lists Azure PowerShell (Windows-centric) as a deployment method before Azure CLI (cross-platform), and does not provide explicit Linux/macOS examples or mention platform-specific considerations. The ordering and emphasis may subtly favor Windows users.
Recommendations
- List Azure CLI (cross-platform) before PowerShell to signal parity.
- Explicitly mention that Azure CLI works on Linux/macOS and provide example commands for those platforms.
- Add notes or links for Linux/macOS users regarding any platform-specific steps or differences.
- Ensure screenshots and instructions are not Windows-specific unless necessary.
Load Balancer
Create a cross-subscription internal load balancer
...er/cross-subscription-how-to-internal-load-balancer.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides both Azure PowerShell and Azure CLI examples, but PowerShell instructions are presented first and in greater detail, with more step-by-step breakdowns and explanations. This can create a perception of Windows bias, as PowerShell is primarily associated with Windows environments, while Azure CLI is more cross-platform. No Linux-specific tools or patterns are mentioned, and there are no explicit Linux/macOS instructions or troubleshooting notes.
Recommendations
- Alternate the order of examples so that Azure CLI instructions appear first or are given equal prominence.
- Expand Azure CLI sections to match the detail and step-by-step guidance provided in PowerShell examples.
- Add explicit notes or troubleshooting tips for Linux/macOS users, such as shell quoting, authentication, or environment setup.
- Consider including Bash script examples or references to Linux-native tools where relevant.
- Clarify that both Azure CLI and PowerShell are cross-platform, and provide links to installation guides for Linux/macOS.
Load Balancer
Attach a cross-subscription backend to an Azure Load Balancer
...d-balancer/cross-subscription-how-to-attach-backend.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides both Azure PowerShell and Azure CLI examples for creating and configuring a cross-subscription Azure Load Balancer. However, the PowerShell (Windows-centric) instructions are presented first and in greater detail, with step-by-step variable assignments and resource creation. The Azure CLI (Linux/macOS-friendly) section is shorter, less detailed, and lacks some of the explanatory context found in the PowerShell section. There are no Linux-specific tools or shell scripting examples, and the overall structure subtly prioritizes Windows/PowerShell users.
Recommendations
- Present Azure CLI examples before PowerShell, or interleave them for parity.
- Expand Azure CLI instructions to match the detail and step-by-step guidance provided in the PowerShell section.
- Add notes or examples for Linux/macOS environments, such as shell scripting or environment setup tips.
- Explicitly state that both CLI and PowerShell are cross-platform and highlight any platform-specific considerations.
Load Balancer
Create a global load balancer with cross-subscription backends
...d-balancer/cross-subscription-how-to-global-backend.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides parallel Azure PowerShell and Azure CLI instructions for all major steps, ensuring both Windows and Linux/macOS users can complete the task. However, PowerShell examples and explanations are consistently presented first in each section, and the prerequisites and introductory notes emphasize Azure PowerShell (a Windows-centric tool) before mentioning Azure CLI. There is also a custom metadata tag indicating a PowerShell focus. No steps are Windows-only, and CLI parity is maintained throughout.
Recommendations
- Alternate the order of PowerShell and CLI sections, or present CLI examples first in some sections to avoid implicit prioritization.
- Add a brief note at the top clarifying that both PowerShell and CLI are fully supported and that CLI is cross-platform.
- Remove or balance metadata tags (e.g., ms.custom: devx-track-azurepowershell) to reflect equal support for CLI.
- Consider including Bash or shell scripting context for CLI examples to further support Linux/macOS users.