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
windows_tools
missing_linux_example
powershell_heavy
Summary
The documentation demonstrates a Windows bias in several ways: Windows credentials and tools are mentioned first or exclusively in multiple sections, especially for SQL Server and File Server discovery. Windows-specific roles (IIS, File Server) and tools (Active Directory, SCCM, RDP, Exchange Server) are highlighted, often with limited or no Linux equivalents or examples. Linux credentials and requirements are mentioned but lack detailed guidance or parity in examples, especially for roles/features discovery and server management. There are no Linux-specific tool examples for file server discovery, and the documentation does not provide Linux command-line or shell examples, focusing instead on Windows and PowerShell-centric workflows.
Recommendations
  • Provide Linux-specific examples and workflows for all major discovery scenarios, including file server and web server roles (e.g., Samba, NFS, Apache, Nginx).
  • Include Linux command-line or shell script examples for credential provisioning and server management, alongside PowerShell/Windows examples.
  • Ensure Linux tools and patterns (e.g., SSH, systemd, SELinux, Linux package managers) are mentioned with equal prominence to Windows tools.
  • Clarify support for Linux file servers and web servers, including supported distributions and versions, and document any limitations.
  • Add guidance for discovering Linux-specific roles and features, such as system services, daemons, and package inventories.
  • Balance the order of presentation so that Linux and Windows are treated equally, rather than Windows-first.
  • Explicitly state any feature gaps or limitations for Linux environments, and provide workarounds or roadmap information where possible.
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-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 Biased Biased
2026-01-06 18:15 #225 cancelled Clean Clean
2025-09-16 00:00 #113 completed Clean Clean
2025-09-15 00:00 #112 completed Clean Clean
2025-09-14 00:00 #111 completed Clean Clean
2025-09-13 00:00 #110 completed Clean Clean
2025-09-12 00:00 #109 completed Clean Clean
2025-08-17 00:01 #83 cancelled Clean Clean
2025-07-13 21:37 #48 completed Clean Clean
2025-07-12 23:44 #41 cancelled Biased Biased
2025-07-09 13:09 #3 cancelled Clean Clean
2025-07-08 04:23 #2 cancelled Biased Biased