Sad Tux - Windows bias detected
This page contains Windows bias

About This Page

This page is part of the Azure documentation. It contains code examples and configuration instructions for working with Azure services.

Bias Analysis

Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation demonstrates a Windows bias in several ways: troubleshooting steps and examples are frequently presented for Windows first or exclusively, with PowerShell commands and Windows-specific tools (e.g., registry edits, event logs, config files in Program Files) dominating the instructions. Linux troubleshooting is covered in a separate section, but is less detailed, and many scenarios (e.g., corrupt cache, proxy issues, certificate handling) are only described for Windows or with Windows-first guidance. Some issues provide only Windows examples or mention Windows tools before Linux equivalents.
Recommendations
  • Ensure that troubleshooting scenarios are presented in parallel for both Windows and Linux, with equivalent detail and step-by-step instructions.
  • Provide Linux-specific commands and file paths wherever Windows PowerShell commands or registry edits are given (e.g., systemd/service management, config file locations, log file locations).
  • When referencing tools (e.g., event logs, registry, config files), include Linux equivalents (e.g., journalctl, /var/log, config files in /etc or /opt).
  • Avoid presenting Windows solutions or examples before Linux ones; consider grouping by scenario and providing both OS instructions side-by-side.
  • Expand Linux troubleshooting coverage to match the depth and specificity of Windows sections, including common Linux issues (e.g., permissions, SELinux/AppArmor, systemd service failures, certificate management).
  • Where PowerShell is used for Windows, provide Bash or Python script examples for Linux.
  • Review all scenarios for OS parity and add missing Linux examples where only Windows is covered.
GitHub Create Pull Request

Scan History

Date Scan Status Result
2026-01-14 00:00 #250 in_progress Biased Biased
2026-01-13 00:00 #246 completed Biased Biased
2026-01-12 00:00 #243 cancelled Biased Biased
2026-01-11 00:00 #240 completed Biased Biased
2026-01-10 00:00 #237 completed Biased Biased
2026-01-09 00:34 #234 completed Biased Biased
2026-01-08 00:53 #231 completed Clean Clean
2026-01-06 18:15 #225 cancelled Clean Clean
2025-08-17 00:01 #83 cancelled Clean Clean
2025-07-13 21:37 #48 completed Clean Clean

Flagged Code Snippets