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 326-350 of 388 flagged pages
Load Balancer https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/monitor-load-balancer.md ...b/main/articles/load-balancer/monitor-load-balancer.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure PowerShell and Azure CLI examples for creating diagnostic settings, but PowerShell (Windows-centric) examples are presented first and in greater detail, with multiple scenarios (Log Analytics, Storage Account, Event Hub) covered before CLI equivalents. There are no Linux-specific shell examples (e.g., Bash), nor is there mention of Linux-native tools or workflows. The CLI examples are generic and do not reference Linux directly, but the ordering and depth favor Windows/PowerShell users.
Recommendations
  • Alternate the order of PowerShell and CLI examples, or present CLI (cross-platform, Linux-friendly) examples first.
  • Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and provide Bash-specific usage notes if relevant.
  • Include sample Bash scripts or usage patterns for Linux users where appropriate.
  • Reference Linux-native monitoring tools or workflows if they can be integrated with Azure Monitor (e.g., exporting logs for use with syslog, journald, or other Linux log management systems).
  • Add a note clarifying platform compatibility for each tool (PowerShell is primarily Windows, CLI is cross-platform).
GitHub 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 →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing Windows troubleshooting resources first and providing more detailed guidance for Windows users. For example, the link to troubleshooting high-CPU issues is specific to Azure Windows VMs, with no equivalent Linux guidance. Additionally, the example for checking listening ports lists the Windows command prompt syntax ('netstat -a') before the Linux terminal syntax ('netstat -l'), and does not provide further Linux-specific troubleshooting steps or links.
Recommendations
  • Include links to equivalent Linux troubleshooting guides, such as 'Troubleshoot high-CPU issues for Azure Linux virtual machines'.
  • Present command examples for both Windows and Linux side-by-side, or in parallel, rather than listing Windows first.
  • Expand Linux-specific troubleshooting steps, such as commands for checking firewall rules (e.g., 'sudo ufw status' or 'iptables -L'), and mention common Linux tools (e.g., 'ss', 'systemctl status').
  • Ensure parity in references and guidance for both Windows and Linux environments throughout the documentation.
GitHub Create Pull Request
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 →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates Windows bias by referencing only Windows virtual machine creation and omitting Linux VM examples. The prerequisite section links exclusively to Windows VM deployment instructions, and the tutorial steps use a Windows VM as the example throughout. There are no Linux-specific instructions, examples, or parity in guidance for Linux users.
Recommendations
  • Include links to both Windows and Linux VM creation guides in the prerequisites.
  • Provide examples and screenshots for both Windows and Linux VMs when demonstrating configuration steps.
  • Clarify that the tutorial applies equally to Linux VMs and mention any OS-specific considerations if relevant.
  • Use neutral VM naming or alternate between Windows and Linux VM examples to avoid implicit prioritization.
GitHub Create Pull Request
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 →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The tutorial demonstrates how to load balance VMs within an availability zone using the Azure portal. It specifically includes steps to create a basic Internet Information Services (IIS) site, which is a Windows-only web server, and does not mention or provide examples for Linux-based alternatives (such as Apache or Nginx). There are no instructions or references for deploying or testing Linux VMs or web servers, indicating a Windows-first approach and missing Linux parity.
Recommendations
  • Include parallel instructions for deploying and configuring a Linux VM (e.g., Ubuntu) alongside the Windows VM steps.
  • Provide examples for installing and configuring a common Linux web server (such as Apache or Nginx) in addition to IIS.
  • Ensure that testing steps cover both Windows and Linux scenarios, demonstrating how to verify load balancing for each.
  • Explicitly mention that the tutorial applies to both Windows and Linux VMs, and provide links to relevant Linux documentation where appropriate.
GitHub Create Pull Request
Load Balancer https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/load-balancer-troubleshoot-backend-traffic.md ...balancer/load-balancer-troubleshoot-backend-traffic.md
Medium Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
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.
GitHub Create Pull Request
Load Balancer https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/troubleshoot-load-balancer-imds.md ...icles/load-balancer/troubleshoot-load-balancer-imds.md
Medium Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
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.
GitHub Create Pull Request
Load Balancer https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/quickstart-load-balancer-standard-internal-bicep.md ...er/quickstart-load-balancer-standard-internal-bicep.md
Medium Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
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).
GitHub 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 →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
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.
GitHub Create Pull Request
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 →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
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.
GitHub Create Pull Request
Load Balancer https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/instance-metadata-service-load-balancer.md ...ad-balancer/instance-metadata-service-load-balancer.md
Medium Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
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.
GitHub Create Pull Request
Load Balancer https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/cross-subscription-how-to-attach-backend.md ...d-balancer/cross-subscription-how-to-attach-backend.md
Medium Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
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.
GitHub Create Pull Request
Load Balancer https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/egress-only.md ...e-docs/blob/main/articles/load-balancer/egress-only.md
Medium Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
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').
GitHub Create Pull Request
Load Balancer https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/cross-subscription-how-to-internal-load-balancer.md ...er/cross-subscription-how-to-internal-load-balancer.md
Medium Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
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.
GitHub Create Pull Request
Load Balancer https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/whats-new.md ...ure-docs/blob/main/articles/load-balancer/whats-new.md
Medium Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
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.
GitHub Create Pull Request
Load Balancer https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/load-balancer-troubleshoot-backend-traffic.md ...balancer/load-balancer-troubleshoot-backend-traffic.md
Medium Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
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.
GitHub Create Pull Request
Load Balancer https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/basic/virtual-network-ipv4-ipv6-dual-stack-cli.md ...ncer/basic/virtual-network-ipv4-ipv6-dual-stack-cli.md
Medium Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
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.
GitHub Create Pull Request
Load Balancer https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/cross-subscription-how-to-internal-load-balancer.md ...er/cross-subscription-how-to-internal-load-balancer.md
Medium Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
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.
GitHub Create Pull Request
Load Balancer https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/cross-subscription-how-to-attach-backend.md ...d-balancer/cross-subscription-how-to-attach-backend.md
Medium Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
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.
GitHub Create Pull Request
Load Balancer https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/egress-only.md ...e-docs/blob/main/articles/load-balancer/egress-only.md
Medium Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
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.
GitHub Create Pull Request
Load Balancer https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/cross-subscription-how-to-global-backend.md ...d-balancer/cross-subscription-how-to-global-backend.md
Medium Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
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.
GitHub Create Pull Request
Load Balancer https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/instance-metadata-service-load-balancer.md ...ad-balancer/instance-metadata-service-load-balancer.md
Medium Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
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.
GitHub Create Pull Request
Load Balancer https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/gateway-deploy-dual-stack-load-balancer.md ...ad-balancer/gateway-deploy-dual-stack-load-balancer.md
Medium Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
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.
GitHub Create Pull Request
Load Balancer https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/load-balancer-floating-ip.md ...in/articles/load-balancer/load-balancer-floating-ip.md
Medium Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
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.
GitHub Create Pull Request
Load Balancer https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/load-balancer-tcp-reset.md ...main/articles/load-balancer/load-balancer-tcp-reset.md
Medium Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
🔧 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.
GitHub Create Pull Request
Load Balancer https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/monitor-load-balancer.md ...b/main/articles/load-balancer/monitor-load-balancer.md
Medium Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
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.
GitHub Create Pull Request
← Previous Page 14 of 16 Next →