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 201-225 of 388 flagged pages
Load Balancer Outbound-only load balancer configuration ...e-docs/blob/main/articles/load-balancer/egress-only.md
Medium Priority View Details →
Scanned: 2026-01-24 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page for configuring an outbound-only load balancer in Azure provides step-by-step instructions using the Azure portal, but when it comes to VM creation and connectivity testing, it exclusively references Windows Server (specifically Windows Server 2022 Datacenter) and Windows tools (Microsoft Edge browser). There are no examples or guidance for deploying or testing with Linux VMs, nor are Linux-specific tools or patterns mentioned.
Recommendations
  • Include instructions for creating a Linux VM (e.g., Ubuntu) alongside the Windows VM example, or clarify that the process is identical for Linux.
  • Provide guidance for connectivity testing on Linux VMs, such as using Firefox, Chrome, or command-line tools like curl or wget to verify outbound connectivity.
  • Explicitly state that the load balancer configuration applies to both Windows and Linux VMs, and note any differences if applicable.
  • Where possible, show both Windows and Linux examples in parallel, especially in sections involving VM creation and connectivity testing.
GitHub Create Pull Request
Load Balancer Quickstart: Create a public load balancer - Azure portal ...cer/quickstart-load-balancer-standard-public-portal.md
Medium Priority View Details →
Scanned: 2026-01-24 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools Windows First
Summary
The documentation provides step-by-step instructions for creating a public load balancer in Azure using the portal, but when configuring the backend VMs, it exclusively demonstrates installing IIS using Windows PowerShell commands. There are no equivalent instructions or examples for Linux VMs (e.g., installing Apache or Nginx), nor are Linux command-line examples provided. The use of Windows PowerShell and IIS is presented as the default, with no mention of Linux alternatives.
Recommendations
  • Add a parallel section demonstrating how to install a web server (such as Apache or Nginx) on Linux VMs, including relevant Bash commands.
  • Explicitly state that the backend VMs can be either Windows or Linux, and provide guidance for both.
  • When showing code examples, present both Windows and Linux commands side-by-side or indicate which OS each applies to.
  • Consider using a more platform-neutral test workload (e.g., a simple HTML file served by any web server) to illustrate load balancing.
GitHub Create Pull Request
Load Balancer Move an Azure Load Balancer to another Azure region ...ad-balancer/move-across-regions-azure-load-balancer.md
Medium Priority View Details →
Scanned: 2026-01-24 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides detailed instructions for moving Azure Load Balancers between regions using the Azure portal and Azure PowerShell. All CLI-based examples and automation steps use Azure PowerShell cmdlets, which are primarily Windows-centric and require PowerShell. There are no examples or guidance for using Azure CLI (az), which is cross-platform and preferred by many Linux/macOS users. Additionally, instructions for editing exported templates reference Windows tools (e.g., notepad.exe) and PowerShell-specific workflows, with no mention of Linux/macOS equivalents or editors.
Recommendations
  • Add parallel instructions and examples using Azure CLI (az) for all steps currently covered with Azure PowerShell.
  • Reference cross-platform text editors (e.g., vim, nano, VS Code) when instructing users to edit JSON files, or use generic language like 'open in a text editor'.
  • Explicitly note that both Azure PowerShell and Azure CLI can be used for resource export, deployment, and verification, and link to relevant Azure CLI documentation.
  • Consider providing a comparison table or guidance on choosing between Azure PowerShell and Azure CLI based on OS/platform.
GitHub Create Pull Request
Load Balancer Tutorial: Protect your public load balancer with Azure DDoS Protection ...s/load-balancer/tutorial-protect-load-balancer-ddos.md
Medium Priority View Details →
Scanned: 2026-01-24 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example Powershell Heavy 🔧 Windows Tools
Summary
The documentation provides only Windows VM creation instructions and exclusively uses Windows PowerShell commands to install and configure IIS on the backend VMs. There are no examples or guidance for deploying Linux VMs, nor are Linux equivalents (such as Apache or Nginx) mentioned or demonstrated. The tutorial assumes Windows as the default platform for backend pool members and web server configuration.
Recommendations
  • Add parallel instructions for creating Linux VMs (e.g., Ubuntu) in the backend pool.
  • Provide Linux-specific examples for installing and configuring a web server (such as Apache or Nginx), including sample shell commands.
  • Include both Windows and Linux options in the VM creation steps, making it clear that either OS can be used.
  • Present PowerShell and Bash/CLI examples side-by-side where relevant.
  • Clarify that IIS is only required if using Windows VMs; suggest alternatives for Linux users.
GitHub Create Pull Request
Load Balancer Outbound-only load balancer configuration ...e-docs/blob/main/articles/load-balancer/egress-only.md
Medium Priority View Details →
Scanned: 2026-01-23 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation provides step-by-step instructions for configuring an outbound-only load balancer in Azure, but all virtual machine creation and connectivity testing examples use Windows Server as the VM image and Microsoft Edge as the browser. There are no Linux VM creation examples, nor are there instructions for testing connectivity from a Linux VM (e.g., using curl or a Linux browser). This creates a bias toward Windows, making it less clear for Linux users how to follow the guide.
Recommendations
  • Include parallel instructions for creating a Linux VM (e.g., Ubuntu) in the 'Create virtual machine' section, with appropriate admin account setup.
  • Add connectivity testing steps for Linux VMs, such as using curl or wget from the command line to verify outbound connectivity (e.g., curl https://whatsmyip.org).
  • Clarify that the configuration applies to both Windows and Linux VMs, and provide notes or links to Linux-specific guidance where relevant.
  • When referencing browsers, mention alternatives available on Linux (e.g., Firefox, Chromium) or use command-line tools for parity.
GitHub Create Pull Request
Load Balancer Tutorial: Create a public load balancer with an IP-based backend - Azure portal ...d-balancer/tutorial-load-balancer-ip-backend-portal.md
Medium Priority View Details →
Scanned: 2026-01-23 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example Powershell Heavy 🔧 Windows Tools
Summary
The documentation exclusively uses Windows Server VM images and Windows PowerShell commands for configuring IIS on backend VMs. There are no Linux VM options or Linux-based web server installation instructions, and Windows/PowerShell patterns are presented as the only approach. This creates friction for users wishing to deploy Linux-based backend pools.
Recommendations
  • Provide parallel instructions for creating Linux VMs (e.g., Ubuntu) in the backend pool.
  • Include Linux-based web server setup (e.g., Apache or Nginx) using Bash/SSH commands.
  • Show both Windows and Linux examples for backend VM configuration and load balancer testing.
  • Explicitly mention that backend pools can use Linux VMs and link to relevant Linux setup guides.
GitHub Create Pull Request
Load Balancer Tutorial: Protect your public load balancer with Azure DDoS Protection ...s/load-balancer/tutorial-protect-load-balancer-ddos.md
Medium Priority View Details →
Scanned: 2026-01-23 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example Powershell Heavy 🔧 Windows Tools
Summary
The tutorial exclusively uses Windows Server VM images and provides only Windows PowerShell commands for installing and configuring IIS. There are no Linux VM options, nor are there Bash or Linux-native instructions for web server setup. The documentation assumes Windows as the default, which creates friction for users who prefer or require Linux-based solutions.
Recommendations
  • Provide parallel instructions for creating Linux VMs (e.g., Ubuntu) in the 'Create virtual machines' section.
  • Include Bash commands for installing and configuring a web server (such as Apache or Nginx) on Linux VMs.
  • Offer users a choice between Windows and Linux VM images when demonstrating backend pool configuration.
  • Clarify that IIS installation is for demonstration purposes and suggest Linux alternatives for cross-platform parity.
  • Add notes or links to documentation for Linux-based load balancer backend scenarios.
GitHub Create Pull Request
Load Balancer Move an Azure Load Balancer to another Azure region ...ad-balancer/move-across-regions-azure-load-balancer.md
Medium Priority View Details →
Scanned: 2026-01-23 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
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/macOS command-line users. All CLI-based instructions use Azure PowerShell cmdlets, which are primarily Windows-centric, and reference Windows tools like notepad.exe for editing templates. There are no Azure CLI (az) examples, which are cross-platform and preferred by many Linux/macOS users.
Recommendations
  • Add equivalent Azure CLI (az) command examples for all PowerShell steps, including exporting, editing, and deploying ARM templates.
  • Replace or supplement references to Windows-specific tools (e.g., notepad.exe) with cross-platform alternatives (e.g., code, nano, vim, or generic 'edit with your preferred text editor').
  • Clarify that both Azure PowerShell and Azure CLI can be used for these operations, and provide links to relevant Azure CLI documentation.
  • Consider reordering sections so that cross-platform methods (Azure portal and Azure CLI) are presented before Windows-specific PowerShell instructions.
GitHub Create Pull Request
Load Balancer Quickstart: Create a public load balancer - Azure portal ...cer/quickstart-load-balancer-standard-public-portal.md
Medium Priority View Details →
Scanned: 2026-01-23 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools Windows First
Summary
The documentation provides only Windows/PowerShell instructions for configuring IIS on backend VMs, with no mention of Linux alternatives (such as Apache or Nginx) or Linux command-line examples. The VM setup and load balancer creation steps are platform-neutral, but the web server installation and configuration section is Windows-centric, using PowerShell and IIS exclusively. This creates friction for users deploying Linux VMs as backend pool members.
Recommendations
  • Add a parallel section for Linux VMs, showing how to install and configure a web server (e.g., Apache or Nginx) using Bash commands.
  • Explicitly state that backend VMs can be either Windows or Linux, and provide guidance for both.
  • Include example scripts for Linux (Ubuntu, CentOS, etc.) to match the PowerShell IIS setup.
  • Mention that IIS is Windows-only, and suggest alternatives for Linux users.
GitHub Create Pull Request
Load Balancer Quickstart: Create a public load balancer - ARM template ...r/quickstart-load-balancer-standard-public-template.md
Medium Priority View Details →
Scanned: 2026-01-23 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides only Azure PowerShell examples for deploying the ARM template, with no equivalent Azure CLI (bash) or Linux/macOS shell instructions. The step-by-step deployment walkthrough is PowerShell-centric, and the example commands use Windows-oriented patterns (e.g., Read-Host, Write-Host). Although the Azure portal and CLI are briefly mentioned as alternatives, no concrete Linux/macOS-friendly instructions or examples are given.
Recommendations
  • Add step-by-step deployment instructions using Azure CLI (az) in bash, suitable for Linux/macOS users.
  • Present both PowerShell and CLI examples side-by-side, or allow users to select their preferred environment.
  • Avoid using Windows/PowerShell-specific patterns (e.g., Read-Host) as the only example for input collection.
  • Explicitly mention that Azure Cloud Shell supports both Bash and PowerShell, and provide examples for both.
  • Ensure screenshots and walkthroughs are not exclusively Windows/PowerShell-centric.
GitHub Create Pull Request
Load Balancer Load Balancer TCP Reset and idle timeout in Azure ...main/articles/load-balancer/load-balancer-tcp-reset.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation references .NET examples for TCP keep-alive configuration and describes error messages typical of Windows environments, but does not provide equivalent Linux or cross-platform examples. There is no mention of Linux tools, commands, or code samples for configuring TCP keep-alive or handling TCP resets, which may leave Linux/macOS users without clear guidance.
Recommendations
  • Add Linux-specific examples for configuring TCP keep-alive, such as using sysctl or socket options in Python or other cross-platform languages.
  • Include references to Linux error messages or behaviors when connections are closed due to idle timeout.
  • Provide parity in code samples and troubleshooting steps for both Windows (.NET, PowerShell) and Linux (Bash, Python, etc.).
  • Explicitly mention cross-platform considerations and tools where relevant.
GitHub Create Pull Request
Load Balancer Backend Pool Management ...main/articles/load-balancer/backend-pool-management.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits a notable Windows bias. The PowerShell section is extensive, with step-by-step examples for backend pool creation, NIC, and VM provisioning, all using Windows-centric tools and patterns. The VM creation example in PowerShell uses a Windows Server image, with no mention of Linux alternatives. The CLI section, while present, is less detailed and only provides basic commands, with the VM creation example using Ubuntu. There are no Bash or Linux shell script examples, and PowerShell is presented first, reinforcing a Windows-first approach.
Recommendations
  • Provide Bash or Linux shell script equivalents for backend pool, NIC, and VM provisioning.
  • Include PowerShell examples for Linux VM creation, not just Windows Server.
  • Alternate the order of examples, sometimes presenting CLI/Bash first.
  • Explicitly mention cross-platform compatibility for all commands and clarify any OS-specific limitations.
  • Expand CLI examples to match the detail and completeness of the PowerShell section.
GitHub Create Pull Request
Load Balancer Deploy IPv6 dual stack application ...https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/deploy-ipv4-ipv6-dual-stack-standard-load-balancer.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation page exhibits a notable Windows bias. All virtual machine deployment examples use Windows Server images exclusively, with no mention of Linux VM images or SSH access. The PowerShell section is extensive and detailed, using Windows-centric tools and patterns (e.g., RDP, Get-Credential), while the Azure CLI section also defaults to Windows VM images. There are no examples or instructions for deploying Linux VMs, configuring SSH access, or using Linux-friendly tools. The documentation assumes RDP as the remote access method, which is not applicable to Linux VMs.
Recommendations
  • Add explicit Linux VM deployment examples in both Azure CLI and PowerShell sections, using images such as Ubuntu or CentOS.
  • Include instructions for configuring SSH access (e.g., generating and using SSH keys) alongside or instead of RDP for Linux VMs.
  • When presenting VM creation commands, show both Windows and Linux image options, or use tabs/switches for OS choice.
  • Mention Linux-friendly remote access tools and patterns (e.g., SSH, cloud-init) where appropriate.
  • Ensure that network security group rules include SSH (port 22) examples, not just RDP (port 3389).
  • Review all PowerShell examples for Windows-specific assumptions and provide Linux alternatives where needed.
GitHub Create Pull Request
Load Balancer Create a cross-subscription internal load balancer ...er/cross-subscription-how-to-internal-load-balancer.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides both Azure PowerShell and Azure CLI examples for creating a cross-subscription internal load balancer, but the PowerShell (Windows-centric) example is presented first and in greater detail. The page is tagged with 'devx-track-azurepowershell', and the PowerShell example uses more granular steps and explanations, while the Azure CLI example is shorter and less detailed. There are no Linux-specific tools or patterns mentioned, and no Bash or shell script examples are provided.
Recommendations
  • Present Azure CLI examples before or alongside PowerShell examples to avoid Windows-first bias.
  • Expand the Azure CLI section to match the level of detail provided in the PowerShell example, including step-by-step breakdowns and explanations.
  • Add explicit Bash/shell script examples for Linux/macOS users where appropriate.
  • Remove or balance the 'devx-track-azurepowershell' custom tag with an equivalent for Azure CLI or Bash.
  • Mention platform parity and clarify that both PowerShell and CLI work cross-platform.
GitHub Create Pull Request
Load Balancer Outbound-only load balancer configuration ...e-docs/blob/main/articles/load-balancer/egress-only.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation provides step-by-step instructions for configuring an outbound-only load balancer in Azure, but all virtual machine creation and connectivity testing examples use Windows Server as the OS and Microsoft Edge as the browser. There are no Linux VM examples, nor instructions for Linux-based connectivity testing (e.g., using curl or a Linux browser). The documentation implicitly assumes a Windows environment for both VM deployment and user interaction.
Recommendations
  • Include parallel instructions for creating a Linux VM (e.g., Ubuntu) in the 'Create virtual machine' section, with appropriate settings for SSH authentication.
  • Provide Linux-specific connectivity testing steps, such as using SSH via Bastion and running 'curl https://whatsmyip.org' from the command line.
  • Mention that the process is OS-agnostic and provide guidance for both Windows and Linux users.
  • Add screenshots or command examples for Linux environments where relevant.
GitHub Create Pull Request
Load Balancer Add IPv6 to an IPv4 application in Azure Virtual Network - PowerShell .../load-balancer/ipv6-add-to-existing-vnet-powershell.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation is exclusively focused on Azure PowerShell, with all examples and instructions using PowerShell cmdlets. There are no references to Linux/macOS command-line tools, nor are equivalent Azure CLI or Bash examples provided. The prerequisites and setup steps assume the user is familiar with PowerShell, which is primarily a Windows-centric tool, although it is available on other platforms. The article title, structure, and content reinforce a Windows-first approach, making it less accessible for Linux/macOS users who may prefer Bash or Azure CLI.
Recommendations
  • Add equivalent Azure CLI examples for each PowerShell command, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Include a section on how to perform the same tasks using Bash scripts or shell commands.
  • Mention that PowerShell Core is available on Linux/macOS and provide installation instructions or links.
  • Rephrase the title and introduction to clarify that the instructions are PowerShell-specific, and link to cross-platform alternatives.
  • Ensure that prerequisites and resource links include both PowerShell and Azure CLI documentation.
GitHub Create Pull Request
Load Balancer Upgrading from Basic Load Balancer - Guidance .../load-balancer/load-balancer-basic-upgrade-guidance.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias by exclusively recommending and providing PowerShell-based automation scripts for migration, without mentioning or providing equivalent CLI or Bash examples for Linux/macOS users. The upgrade steps and automation guidance are centered around PowerShell, which is traditionally a Windows tool, and there is no reference to Azure CLI or cross-platform scripting alternatives. This creates friction for users on Linux or macOS who may not have PowerShell readily available.
Recommendations
  • Provide Azure CLI (az) examples and scripts for automating the migration process, alongside PowerShell.
  • Explicitly mention that PowerShell Core is available cross-platform, or clarify prerequisites for Linux/macOS users.
  • Add Bash script examples or step-by-step instructions using Azure CLI for manual and automated migration.
  • Ensure that all automation guidance is platform-neutral or offers parity for Linux/macOS environments.
GitHub Create Pull Request
Load Balancer Manage Azure Load Balancer health status ...es/load-balancer/load-balancer-manage-health-status.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Powershell Heavy
Summary
The documentation page demonstrates a moderate Windows bias by referencing Windows-specific tools (such as Get-AzAccessToken PowerShell cmdlet) for obtaining a Bearer token, without providing equivalent Linux/macOS CLI examples or guidance. There are no command-line examples for Linux/macOS users, and the only tool referenced for authentication is a PowerShell module, which is primarily used on Windows.
Recommendations
  • Provide equivalent Azure CLI (az account get-access-token) instructions for obtaining a Bearer token on Linux/macOS.
  • Include example commands for both Windows (PowerShell) and Linux/macOS (Bash/Azure CLI) where authentication or scripting is required.
  • Reference cross-platform tools and documentation links, not just PowerShell modules.
  • Explicitly state that the REST API method is platform-agnostic and provide generic curl or HTTP request examples.
GitHub Create Pull Request
Load Balancer Azure Load Balancer health probes ...s/load-balancer/load-balancer-custom-probe-overview.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page exhibits Windows bias primarily through its 'Next steps' section, which highlights PowerShell (a Windows-centric tool) as the main example for creating a load balancer. There are no equivalent Linux or cross-platform CLI examples provided, and PowerShell is mentioned before REST API and other options. Throughout the page, there is a lack of explicit Linux or cross-platform command-line instructions, and no mention of Linux-specific tools or workflows for configuring or testing health probes.
Recommendations
  • Add Azure CLI examples for health probe and load balancer configuration, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Include links to Linux/macOS-specific quickstart guides and documentation alongside PowerShell examples.
  • Provide sample commands or scripts for testing health probes using common Linux tools (e.g., curl, nc, iptables) in relevant sections.
  • Ensure that 'Next steps' and instructional sections present cross-platform options first or in parallel with Windows/PowerShell options.
GitHub Create Pull Request
Load Balancer Azure Load Balancer Floating IP configuration ...in/articles/load-balancer/load-balancer-floating-ip.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation presents Windows Server configuration instructions before Ubuntu/Linux instructions. Windows-specific tools and terminology (netsh, 'weak host' model) are described in detail, while Linux instructions are more concise and generic. The example for advanced configuration patterns links only to a Windows-specific scenario (Always On availability group listener with PowerShell), with no Linux equivalent referenced.
Recommendations
  • Alternate the order of OS examples, or present Linux and Windows instructions side-by-side.
  • Provide links to Linux-specific advanced configuration scenarios, such as configuring Always On availability group listeners on Linux VMs.
  • Expand Linux instructions to match the detail level of Windows instructions, including troubleshooting tips and alternative firewall tools (e.g., firewalld, iptables).
  • Clarify any OS-specific caveats, such as differences in the 'weak host' model and how to verify or configure it on Linux.
  • Ensure parity in example complexity and completeness for both platforms.
GitHub Create Pull Request
Load Balancer Migrate from Inbound NAT rules version 1 to version 2 ...cles/load-balancer/load-balancer-nat-pool-migration.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias. PowerShell is heavily featured, especially for automation and scripting, with a dedicated migration module and prerequisite steps only for PowerShell. There are no Linux/macOS-specific automation or scripting examples, and the only automation script provided is for PowerShell. Prerequisites and upgrade instructions reference Windows tools and PowerShell modules exclusively. While Azure CLI examples are present for manual migration, advanced/automated scenarios are Windows/PowerShell-only.
Recommendations
  • Provide equivalent Bash or Python scripts for automation and migration tasks, especially for Virtual Machine Scale Set migration.
  • Include instructions for installing and using Azure CLI for automation, not just for manual steps.
  • List both Azure CLI and PowerShell options for prerequisites and automation modules, or clarify cross-platform alternatives.
  • If a PowerShell module is required, note its compatibility with PowerShell Core on Linux/macOS, or provide a CLI-based alternative.
  • Ensure that all advanced/automated migration scenarios have Linux/macOS-friendly solutions.
GitHub Create Pull Request
Load Balancer Troubleshoot Azure Load Balancer health probe status ...ncer/load-balancer-troubleshoot-health-probe-status.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. Troubleshooting steps frequently reference Windows-specific tools (PsPing, TCPing, Netsh), and command examples are shown using Windows syntax first or exclusively. Linux alternatives are mentioned but less prominently, and some steps lack direct Linux equivalents or guidance.
Recommendations
  • Provide Linux-native equivalents for all troubleshooting tools (e.g., suggest 'nc', 'ss', or 'telnet' for port testing instead of only PsPing/TCPing).
  • Include Linux command examples alongside Windows ones, not just as afterthoughts (e.g., show 'netstat -l' and 'ss -ltn' for listening ports).
  • Offer guidance for capturing network traces on Linux (e.g., using 'tcpdump' or 'wireshark'), not just Netsh.
  • Balance the order of presentation so Linux and Windows instructions appear with equal prominence.
  • Explicitly mention macOS where relevant, or clarify which steps apply to both Linux and macOS.
GitHub Create Pull Request
Load Balancer Manage Administrative State in Azure Load Balancer ...in/articles/load-balancer/manage-admin-state-how-to.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation consistently references Windows-based virtual machines in all example links and prerequisites, omitting explicit Linux VM instructions or links. All sample resource creation links point to Windows VM guides, and there are no Linux-specific examples or parity guidance for Linux users. While Azure CLI and PowerShell are cross-platform, the documentation's examples and prerequisites are Windows-centric.
Recommendations
  • Add explicit links and instructions for creating Linux-based virtual machines in the prerequisites for each method (portal, PowerShell, CLI).
  • Include example commands and resource names that reference Linux VMs alongside Windows VMs.
  • Clarify that Azure CLI and PowerShell commands work for both Windows and Linux VM backend pool members.
  • Consider adding a note or section addressing Linux/macOS users, confirming parity and highlighting any differences if present.
GitHub Create Pull Request
Load Balancer Manage inbound NAT rules for Azure Load Balancer ...ain/articles/load-balancer/manage-inbound-nat-rules.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation provides examples for managing inbound NAT rules using the Azure portal, PowerShell, and Azure CLI. PowerShell is featured prominently and in detail, with extensive step-by-step examples and explanations. PowerShell is a Windows-centric tool, and its usage is described before CLI in each section. The prerequisites section also focuses on installing and using PowerShell locally, with Windows-specific commands and instructions. There is no explicit mention of Linux/macOS alternatives for scripting (e.g., Bash), and no Linux/macOS-specific nuances or troubleshooting are discussed.
Recommendations
  • Add Bash or shell script examples for Linux/macOS users where relevant, especially for tasks that can be automated outside Azure CLI.
  • Clarify that Azure CLI works cross-platform and provide explicit instructions for Linux/macOS environments (e.g., installation, authentication).
  • In the prerequisites, include steps for setting up Azure CLI on Linux/macOS and mention that PowerShell Core is available cross-platform, but CLI is often preferred on Linux.
  • Alternate the order of PowerShell and CLI examples, or present CLI first to avoid implicit Windows prioritization.
  • Add troubleshooting notes or tips for Linux/macOS users, such as file path differences, shell quoting, or permission issues.
GitHub Create Pull Request
Load Balancer Troubleshoot common problems with Azure Load Balancer ...n/articles/load-balancer/load-balancer-troubleshoot.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates a notable Windows bias by exclusively referencing Windows-specific tools (PsPing, Netsh) and commands for network troubleshooting, without providing Linux/macOS equivalents or examples. All troubleshooting steps involving command-line utilities assume a Windows environment, and no mention is made of Linux-native tools or alternative approaches.
Recommendations
  • Include Linux/macOS equivalents for network troubleshooting, such as using 'nc', 'ss', 'tcpdump', or 'nmap' for port testing and packet capture.
  • Provide example commands for Linux (e.g., 'nc -zv 10.0.0.4 3389' for port testing, 'tcpdump' for network traces) alongside Windows examples.
  • Clarify that PsPing and Netsh are Windows-only, and suggest cross-platform alternatives.
  • Ensure that troubleshooting steps are platform-agnostic or offer parallel instructions for both Windows and Linux environments.
GitHub Create Pull Request
← Previous Page 9 of 16 Next →