Document Details
Troubleshoot Appliance
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 often reference Windows tools and commands first or exclusively (e.g., Control Panel, admin command prompt, PowerShell, Notepad, Windows file paths), and remediation steps for Windows are more detailed than for Linux. In some cases, Linux guidance is present but less prominent or appears after Windows instructions. There are also sections where only Windows-specific tools or patterns are mentioned, and Linux equivalents are missing or less detailed.
Recommendations
- Ensure that for every Windows-specific troubleshooting step (e.g., using Control Panel, PowerShell, Notepad, Windows file paths), an equivalent Linux step is provided, with equal detail and prominence.
- Where both Windows and Linux are supported, use parallel tabbed sections or side-by-side examples for commands and file locations.
- Avoid using Windows-first language (e.g., 'Open Notepad as an admin' or referencing C:\ paths) without providing the Linux equivalent (e.g., 'Open your preferred text editor as root' and '/etc/hosts').
- For sections that reference Windows tools (e.g., WMI, WinRM, Control Panel), include Linux equivalents (e.g., SSH, systemd, chrony/ntpd for time sync) and troubleshooting steps.
- When providing code samples, ensure both PowerShell and Bash/SSH examples are present where applicable.
- Review the order of presentation so that Linux and Windows are treated with parity, either by alternating order or using tabs, rather than always listing Windows first.
- Expand Linux troubleshooting guidance to match the depth and clarity of Windows instructions, especially for common issues like connectivity, authentication, and service management.
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-08-17 00:01 | #83 | cancelled |
Clean
|
| 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
|