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
Bias Types:
⚠️
windows_first
⚠️
powershell_heavy
⚠️
windows_tools
⚠️
missing_linux_example
Summary:
The documentation demonstrates a Windows bias in several ways: Windows metadata, tools, and PowerShell cmdlets are consistently presented first and in greater detail than Linux equivalents. Windows-specific tools (WMI, PowerShell, Registry, Get-WindowsFeature, etc.) are referenced throughout, while Linux examples, though present, are often grouped together and sometimes less detailed. Some sections (e.g., ASP.NET, Java, Spring Boot web app data) only mention Windows servers, omitting Linux scenarios. The documentation also uses Windows-centric terminology and patterns, and Linux parity is sometimes lacking in both depth and breadth.
Recommendations:
- Present Linux and Windows examples side-by-side or in parallel tables/sections to ensure equal visibility.
- Where Windows PowerShell cmdlets or WMI classes are listed, provide equivalent Linux commands or tools (e.g., systemctl, lsof, etc.) where possible.
- Expand Linux sections to match the detail provided for Windows, especially for application and web server discovery (e.g., include Apache, NGINX, Tomcat on Linux).
- Explicitly state when a feature or data point is only available for Windows, and clarify Linux support status.
- Include Linux-specific application and feature discovery (e.g., systemd services, package managers, web servers) in the same detail as Windows features.
- Review and update sections like ASP.NET, Java, and Spring Boot web app data to include Linux scenarios or clarify if not supported.
- Avoid always listing Windows first; alternate order or use neutral grouping (e.g., 'On Windows:' / 'On Linux:').
Create pull request