31
Total Pages
28
Linux-Friendly Pages
3
Pages with Bias
9.7%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues (4)

Page-Level Analysis

Windows First Missing Linux Example
Summary:
The documentation page demonstrates a Windows bias by providing detailed reference architectures and links specifically for Windows virtual machines and Windows N-tier applications, while Linux is only mentioned in passing. There are no equivalent Linux-specific examples, diagrams, or reference links, despite the mention of 'Windows/Linux' workloads. The focus on Windows architectures without Linux parity may leave Linux users underserved.
Recommendations:
  • Add explicit Linux-based reference architectures, including diagrams and detailed explanations, similar to those provided for Windows.
  • Include links to Linux-specific Azure architecture guides (e.g., 'Linux N-tier application on Azure').
  • Where 'Windows/Linux' is mentioned, ensure both platforms are equally represented with examples and guidance.
  • Review all sections to ensure Linux is not just mentioned but actively supported with actionable content.
  • If certain features or architectures are Windows-only, clearly state this and provide alternative recommendations for Linux users.

Page-Level Analysis

Powershell Heavy Windows First Missing Linux Example
Summary:
The documentation page demonstrates a Windows/Powershell bias by explicitly referencing Azure PowerShell for enabling DDoS IP Protection, while not mentioning or providing equivalent instructions for Linux users (e.g., Azure CLI, Bash, or ARM templates). There are no Linux/Unix-specific examples or parity in tooling guidance, and the only command-line example referenced is PowerShell.
Recommendations:
  • Provide parallel instructions and quickstarts for enabling DDoS IP Protection using Azure CLI (az), which is cross-platform and commonly used on Linux.
  • When referencing PowerShell, always mention or link to equivalent Azure CLI or REST API documentation.
  • Avoid implying that PowerShell is the primary or only supported method for configuration; instead, present both Windows and Linux-friendly options side by side.
  • Include explicit examples or links for Linux/macOS users, especially in sections that currently reference only PowerShell.
  • Consider a 'Choose your platform' approach in quickstart and configuration sections, allowing users to select their preferred environment (Azure Portal, PowerShell, Azure CLI, ARM/Bicep, etc.).

Page-Level Analysis

Windows First Missing Linux Example
Summary:
The documentation consistently presents Windows-focused examples and reference architectures, particularly in the 'Virtual machine (Windows/Linux) workloads' section. While the section heading mentions both Windows and Linux, all detailed examples, diagrams, and links are specific to Windows (e.g., 'Windows N-tier application on Azure'). There are no Linux-specific reference architectures, diagrams, or links provided, and Linux is not equally represented in the scenarios or guidance.
Recommendations:
  • Add parallel Linux-specific reference architectures and diagrams, such as 'Linux N-tier application on Azure', with equivalent depth and detail.
  • Include links to Linux-focused Azure architecture documentation where available.
  • Ensure that examples and best practices are presented for both Windows and Linux workloads, or use neutral, OS-agnostic language and diagrams where possible.
  • Where both Windows and Linux are supported, explicitly mention and illustrate both, rather than only referencing Windows.
  • Review and update headings and content to avoid implying parity where it does not exist (e.g., do not mention 'Windows/Linux' if only Windows is detailed).

Page-Level Analysis

Windows First Powershell Heavy
Summary:
The documentation provides both Azure PowerShell and Azure CLI examples for managing resources, but consistently presents PowerShell (a Windows-centric tool) before CLI in all code tabs and output sections. There are no Linux-specific instructions, nor is there mention of running CLI commands in a native Linux shell, though Azure CLI is cross-platform. The documentation implicitly prioritizes Windows/PowerShell workflows.
Recommendations:
  • Alternate the order of PowerShell and CLI tabs, or present CLI examples first to avoid implicit prioritization of Windows tools.
  • Explicitly mention that Azure CLI commands can be run on Linux, macOS, and Windows, and provide example shell prompts (e.g., bash) for Linux users.
  • Add a brief section or note highlighting cross-platform support and how to use Azure CLI in native Linux environments.
  • Where possible, include screenshots or instructions that reflect both Windows and Linux environments (e.g., terminal screenshots, shell prompts).