Bias Analysis
Detected Bias Types
powershell_heavy
windows_tools
windows_first
Summary
The documentation page shows mild Windows bias. While it mentions both PowerShell and Bash for deployment scripts, the only concrete tooling example for testing (arm-ttk) is a PowerShell script, and the authoring tools highlighted are Visual Studio and Visual Studio Code, both of which are more Windows-centric (though VS Code is cross-platform). In the CI/CD section, Azure DevOps and Visual Studio project pipelines are emphasized, which are often associated with Windows workflows. PowerShell is mentioned before Bash, and there are no explicit Linux-specific examples or tool recommendations. The deployment options list Azure CLI and PowerShell, but PowerShell is mentioned before Bash in the extensibility section.
Recommendations
- Provide explicit Linux/bash examples or references alongside PowerShell, especially for testing and scripting (e.g., mention Bash-based test kits or how to use arm-ttk in Linux environments).
- Highlight cross-platform or Linux-native authoring tools (such as vim, nano, or JetBrains IDEs) or clarify that Visual Studio Code is cross-platform.
- In the CI/CD section, mention other popular CI/CD systems (such as GitHub Actions, Jenkins, or GitLab CI) with Linux runners, and provide links to relevant guides.
- When listing deployment options, alternate the order or explicitly state that both Azure CLI and PowerShell are cross-platform, and provide example commands for both.
- Where PowerShell is mentioned, ensure Bash is given equal prominence and provide sample Bash scripts or references.
- If possible, include screenshots or walkthroughs from Linux environments (e.g., Azure Cloud Shell in Bash mode).
Create Pull Request