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-first bias in several ways: Windows terminology and tools (e.g., 'Download Executable', registry edits, Windows Explorer/File Explorer) are often mentioned before or in more detail than their Linux equivalents. Powershell and Windows-specific troubleshooting steps are prominent, while Linux steps are sometimes less detailed or appear after Windows instructions. Some advanced Windows scenarios (like registry edits for iSCSI timeouts) are described in depth, while Linux equivalents are less emphasized or missing. The 'Next steps' section also lists PowerShell before Azure CLI, reinforcing the Windows-first pattern.
Recommendations:
- Ensure Linux instructions and troubleshooting steps are as detailed and prominent as Windows ones, especially for advanced scenarios (e.g., provide more in-depth guidance for Linux iSCSI/RAID/LVM troubleshooting).
- Present Linux and Windows instructions in parallel or in clearly separated, equally detailed sections, rather than always listing Windows first.
- Include Linux CLI examples and tools (e.g., show how to browse and copy files using common Linux file managers or CLI commands, not just Windows Explorer).
- In 'Next steps', alternate the order of PowerShell and CLI links, or group them by platform to avoid reinforcing a Windows-first impression.
- Where Windows registry edits are described, provide equivalent Linux configuration file changes (e.g., for iSCSI timeouts) with equal prominence and explanation.
- Use neutral language and headings (e.g., 'For Windows and Linux' or 'Platform-specific steps') to avoid implying Windows is the default or primary platform.
Create pull request