Document Details
Troubleshoot Assessment
❌
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
Bias Types:
⚠️
windows_first
⚠️
windows_tools
⚠️
powershell_heavy
⚠️
missing_linux_example
Summary:
The documentation demonstrates a Windows bias in several ways: Windows tools and protocols (WinRM, WMI, PowerShell cmdlets) are mentioned first or exclusively in troubleshooting steps, with Linux alternatives (SSH) often mentioned secondarily or with less detail. Several error codes and recommended actions focus on Windows-specific technologies (e.g., WMI, Get-WmiObject, WinRM TrustedHosts) without providing equivalent Linux command examples or troubleshooting steps. The web apps discovery errors section is heavily IIS/Windows-centric, with no mention of Linux-based web servers or migration scenarios.
Recommendations:
- For every troubleshooting step involving Windows tools (e.g., WinRM, WMI, PowerShell), provide equivalent Linux commands and troubleshooting steps (e.g., SSH, systemd, journalctl, relevant Linux commands).
- When listing protocols or ports (e.g., WinRM and SSH), present Linux and Windows options in parallel, not always with Windows first.
- Include Linux-specific error codes and troubleshooting guidance where applicable, such as common SSH or Linux service issues.
- For web app migration errors, add examples and troubleshooting steps for Linux-based web servers (e.g., Apache, Nginx, Tomcat) and clarify which steps are Windows/IIS-specific.
- Where PowerShell cmdlets are referenced (e.g., Get-WmiObject), provide equivalent Linux shell commands or scripts for parity.
- Review all sections to ensure Linux scenarios are not only mentioned but are given equal detail and prominence as Windows scenarios.
Create pull request