Bias Analysis
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for authentication and resource listing, but PowerShell is given equal prominence and is referenced in links and examples. There are several references to PowerShell-specific workflows and tools (such as Visual Studio Code and PowerShell deployment guides), and PowerShell is presented as a primary method for interacting with Azure REST APIs. There is a lack of explicit Linux shell (bash) or cross-platform scripting examples beyond Azure CLI, and Windows-centric tools and patterns (PowerShell, Visual Studio Code) are mentioned before or instead of Linux alternatives.
Recommendations
- Add explicit bash shell examples for authentication and REST calls, especially for Linux users.
- Include references to Linux-native tools (e.g., wget, curl in bash scripts) and editors (e.g., Vim, VS Code on Linux) where applicable.
- Ensure that Azure CLI examples are presented first or with equal prominence to PowerShell, as CLI is cross-platform.
- Provide links to Linux-specific deployment guides and documentation, not just PowerShell-based workflows.
- Avoid assuming Visual Studio Code or PowerShell as the default tooling; mention alternatives or clarify cross-platform support.
Create Pull Request