Bias Analysis
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation demonstrates Windows bias primarily in the 'Connect to the developer portal' section, where instructions are given exclusively for editing the Windows hosts file using Notepad and navigating to C:\windows\System32\drivers\etc. There are no equivalent instructions for Linux or macOS users, such as using sudo and a text editor to edit /etc/hosts. Additionally, the use of backticks (`) for line continuation in Azure CLI examples is a PowerShell/Windows convention, which may confuse Linux/macOS users who expect backslashes (\) or no continuation. The document also suggests switching to PowerShell in Azure Cloud Shell, further reinforcing a Windows-first approach.
Recommendations
- Provide explicit instructions for editing the hosts file on Linux (e.g., 'sudo nano /etc/hosts') and macOS (e.g., 'sudo open -e /etc/hosts' or 'sudo nano /etc/hosts').
- Clarify line continuation syntax for Azure CLI commands: show both Windows (backtick) and Linux/macOS (backslash or multi-line without continuation) examples.
- Avoid suggesting PowerShell as the default shell in Azure Cloud Shell; mention Bash as an alternative and provide command compatibility notes.
- Where file paths are referenced, include both Windows and Unix-style paths.
- Add a note or section for cross-platform differences, especially for steps that involve local machine configuration.
Create Pull Request