Document Details
Discovered Metadata
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 moderate Windows bias. Windows-specific tools (WMI, PowerShell cmdlets, registry paths) are listed first and in greater detail, with Linux equivalents often grouped together or described more generically. Windows examples and tooling (PowerShell, registry, WMI) are consistently presented before Linux commands, and some sections (e.g., ASP.NET, Spring Boot, Java web app data) are described only in the context of Windows servers. Windows storage metadata is much more detailed, with extensive PowerShell cmdlet coverage, while Linux storage metadata is presented as a list of shell commands without as much explanation or parity in structure. There are also sections (e.g., SQL Server, web app data) that assume Windows as the host platform, with Linux only mentioned as a possible value, not as a first-class scenario.
Recommendations
- Present Linux and Windows examples side-by-side in all sections, not just as an afterthought.
- Provide Linux-specific details for web app discovery (e.g., Apache, Nginx, Tomcat on Linux) and storage features (e.g., LVM, RAID, NFS, Samba).
- Expand Linux tooling explanations to match the depth given to Windows (e.g., explain what each Linux command does, provide context for output parsing).
- Explicitly call out Linux support for SQL Server and web apps, with examples of Linux-based deployments and data collection.
- Avoid listing Windows tools and cmdlets first; alternate ordering or group by scenario rather than OS.
- Where Windows uses PowerShell or WMI, provide equivalent Linux shell commands or scripts with equal detail.
- Clarify which features are Windows-only and which are cross-platform, and document Linux/macOS limitations or alternatives.
Create Pull Request
Scan History
| Date | Scan | Status | Result |
|---|---|---|---|
| 2026-01-14 00:00 | #250 | in_progress |
Biased
|
| 2026-01-13 00:00 | #246 | completed |
Biased
|
| 2026-01-11 00:00 | #240 | completed |
Biased
|
| 2026-01-10 00:00 | #237 | completed |
Biased
|
| 2026-01-09 00:34 | #234 | completed |
Biased
|
| 2026-01-08 00:53 | #231 | completed |
Biased
|
| 2026-01-06 18:15 | #225 | cancelled |
 Clean
|
| 2025-09-16 00:00 | #113 | completed |
Clean
|
| 2025-09-15 00:00 | #112 | completed |
Clean
|
| 2025-09-14 00:00 | #111 | completed |
Clean
|
| 2025-09-13 00:00 | #110 | completed |
Clean
|
| 2025-09-12 00:00 | #109 | completed |
Clean
|
| 2025-09-11 00:00 | #108 | completed |
Clean
|
| 2025-08-11 00:00 | #77 | completed |
Clean
|
| 2025-08-10 00:00 | #76 | completed |
Clean
|
| 2025-08-09 00:00 | #75 | completed |
Clean
|
| 2025-08-08 00:00 | #74 | completed |
Clean
|
| 2025-08-07 00:00 | #73 | completed |
Clean
|
| 2025-08-06 00:00 | #72 | completed |
Clean
|
| 2025-08-05 00:00 | #71 | completed |
Clean
|
| 2025-08-03 00:00 | #69 | completed |
Clean
|
| 2025-08-01 00:00 | #67 | completed |
Clean
|
| 2025-07-31 00:00 | #66 | completed |
Clean
|
| 2025-07-30 00:00 | #65 | completed |
Clean
|
| 2025-07-29 00:01 | #64 | completed |
Clean
|
| 2025-07-28 00:00 | #63 | completed |
Clean
|
| 2025-07-27 00:00 | #62 | completed |
Clean
|
| 2025-07-26 00:01 | #61 | completed |
Clean
|
| 2025-07-25 00:00 | #60 | completed |
Clean
|
| 2025-07-24 00:00 | #59 | completed |
Clean
|
| 2025-07-23 00:00 | #58 | completed |
Clean
|
| 2025-07-22 00:01 | #57 | completed |
Clean
|
| 2025-07-21 00:00 | #56 | completed |
Clean
|
| 2025-07-19 13:51 | #54 | completed |
Clean
|
| 2025-07-17 00:00 | #53 | completed |
Biased
|
| 2025-07-16 00:00 | #52 | completed |
Biased
|
| 2025-07-13 21:37 | #48 | completed |
Biased
|
| 2025-07-12 23:44 | #41 | cancelled |
Biased
|
| 2025-07-09 13:09 | #3 | cancelled |
Clean
|
| 2025-07-08 04:23 | #2 | cancelled |
Biased
|