Bias Analysis
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
windows_tools
Summary
The documentation exhibits a notable Windows bias, especially in automation and scripting sections. Initial setup and artifact deployment scripts are provided only in PowerShell, with explicit instructions to use PowerShell ISE, and no Linux/bash equivalents are offered for these critical steps. Windows tools and patterns (PowerShell ISE, Remove-Module, Import-Module, etc.) are mentioned exclusively and before any Linux alternatives. Only in the optional app service registration and web app update sections are both Linux (bash) and Windows (PowerShell) examples given. This bias creates friction for Linux/macOS users, who must translate or adapt Windows-centric instructions to their platforms.
Recommendations
- Provide bash/Linux equivalents for all PowerShell scripts, especially for initial setup and artifact deployment.
- Avoid referencing Windows-specific tools (e.g., PowerShell ISE) as the only option; suggest cross-platform alternatives like VS Code or terminal.
- Where custom modules (e.g., SDAFUtilities) are used, document how to use them from bash or Linux shells, or provide alternative scripts.
- Ensure all critical automation steps have both Windows and Linux/macOS instructions, ideally side-by-side.
- Review and update screenshots and UI references to ensure they are not Windows-only where Azure DevOps is cross-platform.
Create Pull Request