64
Total Pages
60
Linux-Friendly Pages
4
Pages with Bias
6.2%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

8 issues found
Showing 1-8 of 8 flagged pages
Ddos Protection Azure DDoS Protection Overview ...n/articles/ddos-protection/ddos-protection-overview.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page exhibits Windows bias primarily in its references to enabling DDoS IP Protection via Azure PowerShell, a tool most commonly associated with Windows environments. The quickstart for DDoS IP Protection explicitly points to a PowerShell-based guide, with no mention of Azure CLI or Bash alternatives. Additionally, Windows-centric tools and patterns are referenced before any cross-platform or Linux-native equivalents, and there are no Linux/macOS-specific instructions or examples provided.
Recommendations
  • Provide equivalent quickstart guides for enabling DDoS IP Protection using Azure CLI and/or Bash scripts, which are cross-platform and widely used on Linux/macOS.
  • Mention Azure CLI as an alternative to PowerShell wherever configuration steps are discussed.
  • Ensure all example commands and configuration steps are available for both PowerShell and Azure CLI, and present them side-by-side or in a platform-neutral order.
  • Add explicit notes clarifying cross-platform support and linking to Linux/macOS-specific documentation where relevant.
Ddos Protection Tutorial: Configure Azure DDoS Protection diagnostic logging alerts ...les/ddos-protection/ddos-diagnostic-alert-templates.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation exclusively describes configuration via the Azure Portal and Resource Manager templates, with all screenshots and instructions referencing the Azure Portal UI. There are no examples or instructions for command-line configuration using cross-platform tools such as Azure CLI, nor are there references to Linux/macOS workflows. The prerequisites mention enabling DDoS IP Protection via a PowerShell-specific page, and there is no mention of Bash, Azure CLI, or Linux-native approaches.
Recommendations
  • Add equivalent instructions for configuring diagnostic logging alerts using Azure CLI, which is cross-platform and works on Linux/macOS.
  • Include examples for deploying Resource Manager templates via Azure CLI or Bash scripts.
  • Reference Linux/macOS workflows and tools where applicable, such as using az commands for resource creation and management.
  • Ensure that prerequisite links include both PowerShell and CLI/Bash alternatives.
  • Add screenshots or terminal output examples for Linux/macOS users.
Ddos Protection Azure DDoS Protection Overview ...n/articles/ddos-protection/ddos-protection-overview.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page shows evidence of Windows bias, primarily by referencing Azure PowerShell for enabling DDoS IP Protection and linking to a PowerShell-specific quickstart, without mentioning or providing equivalent instructions for Linux/macOS users (e.g., Azure CLI or REST API). Windows tools and terminology are presented first and exclusively in the context of DDoS IP Protection setup, which may create friction for non-Windows users.
Recommendations
  • Provide Azure CLI and REST API instructions and quickstart links alongside or before PowerShell examples for enabling DDoS IP Protection.
  • Explicitly mention cross-platform tools (Azure CLI) in all setup and configuration sections.
  • Ensure all referenced quickstarts and guides have Linux/macOS parity and are discoverable from this overview page.
  • Add a note clarifying that Azure CLI is available on Windows, Linux, and macOS, and provide links to installation guides.
Ddos Protection Tutorial: Configure Azure DDoS Protection diagnostic logging alerts ...les/ddos-protection/ddos-diagnostic-alert-templates.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation exclusively describes configuration via the Azure Portal and Resource Manager templates, with no mention of command-line or automation options for Linux/macOS users (e.g., Azure CLI, Bash, or ARM template deployment via non-Windows tools). There are no examples or instructions for Linux-native workflows, and the only referenced automation guide is linked to a PowerShell page in the prerequisites.
Recommendations
  • Add instructions and examples for deploying the alert templates using Azure CLI and Bash, which are cross-platform and commonly used on Linux/macOS.
  • Explicitly mention that the portal and template deployment methods are OS-agnostic, or clarify any platform-specific requirements.
  • Provide links to documentation for ARM template deployment via Azure CLI and/or REST API.
  • Avoid referencing PowerShell-only guides in prerequisites unless Linux alternatives are also provided.
Ddos Protection QuickStart: Create and configure Azure DDoS Network Protection using Terraform ...es/ddos-protection/manage-ddos-protection-terraform.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for verifying results, but PowerShell is given equal prominence and is presented immediately after CLI, which may suggest a Windows-centric approach. There are no explicit Linux/macOS-specific instructions or troubleshooting notes, and PowerShell is a Windows-first tool. However, the CLI examples are cross-platform and shown first.
Recommendations
  • Explicitly state that Azure CLI commands work on Linux/macOS and Windows.
  • Clarify that PowerShell examples are for Windows users, and provide Bash alternatives for any scripting shown.
  • Add troubleshooting notes for common Linux/macOS issues (e.g., file permissions, environment variables).
  • If any step requires a Windows-only tool, provide a Linux/macOS equivalent or workaround.
Ddos Protection QuickStart: Create and configure Azure DDoS IP Protection - ARM template .../ddos-protection/manage-ddos-ip-protection-template.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation presents both Azure PowerShell and Azure CLI examples for resource review and cleanup, but PowerShell (a Windows-centric tool) is consistently listed first in each section. There is no explicit mention of Linux/macOS-specific tools or workflows, and screenshots and instructions focus on the Azure Portal, which is cross-platform. No critical steps are Windows-only, but the ordering and emphasis may subtly favor Windows users.
Recommendations
  • Alternate the order of CLI and PowerShell examples so that CLI (cross-platform) is sometimes shown first.
  • Explicitly mention that Azure CLI works natively on Linux/macOS and provide installation links for those platforms.
  • Add a brief note clarifying that PowerShell Core is available on Linux/macOS, or link to cross-platform installation guides.
  • Consider including Bash script examples for common tasks, especially in cleanup sections.
  • Ensure screenshots and instructions do not assume a Windows environment (e.g., file paths, shell conventions).
Ddos Protection QuickStart: Create and configure Azure DDoS IP Protection - ARM template .../ddos-protection/manage-ddos-ip-protection-template.md
Low Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation presents both Azure PowerShell and Azure CLI examples for resource management tasks, but consistently lists PowerShell (Windows-centric) examples before CLI (cross-platform) examples. Output samples are also shown with PowerShell first. There is no explicit mention of Linux/macOS usage, nor are there any Bash or shell script examples, but the CLI examples do provide Linux parity. No Windows-only tools or patterns are used, and all tasks can be completed on Linux/macOS using Azure CLI.
Recommendations
  • Alternate the order of PowerShell and CLI examples, or present CLI examples first to better reflect cross-platform usage.
  • Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and that Cloud Shell is available in-browser for all platforms.
  • Add a note clarifying that PowerShell is primarily used on Windows, while CLI is recommended for Linux/macOS users.
  • Consider adding Bash script examples for common tasks, or link to Linux/macOS-specific guidance.
Ddos Protection QuickStart: Create and configure Azure DDoS Network Protection using Terraform ...es/ddos-protection/manage-ddos-protection-terraform.md
Low Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for verifying results, but the PowerShell example is given equal prominence and detail as the CLI example. There is a slight Windows bias in the inclusion of PowerShell, which is primarily a Windows tool, and in the use of Windows-style variable assignment syntax in the PowerShell tab. However, the CLI example is cross-platform and shown first, and no critical steps are Windows-only.
Recommendations
  • Clarify that Azure CLI commands work on Linux/macOS and Windows equally.
  • Consider adding explicit bash/zsh shell examples for Linux/macOS users, especially for variable assignment and command usage.
  • Note that PowerShell Core is available cross-platform, but most Linux users will prefer Azure CLI.
  • Ensure that any file creation or directory navigation steps use OS-agnostic language or provide both Windows and Linux/macOS command examples if relevant.