Bias Analysis
Detected Bias Types
powershell_heavy
windows_tools
windows_first
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell is mentioned as a primary scripting option (for deployment scripts and the ARM Template Toolkit), and the only test kit referenced is a PowerShell script. Authoring tools highlighted are Visual Studio and Visual Studio Code, both of which are strongly associated with Windows (though VS Code is cross-platform). In the list of deployment options, Azure CLI and PowerShell are both mentioned, but PowerShell is listed after Azure CLI. However, Linux-specific tools or workflows are not highlighted, and there are no explicit Linux shell (bash) examples or references to Linux-native tooling.
Recommendations
- Include explicit Bash and/or Azure CLI examples alongside or instead of PowerShell examples, especially for deployment scripts and testing.
- Mention Linux-native authoring tools or editors (such as Vim, Emacs, or JetBrains IDEs) where relevant, or clarify that Visual Studio Code is cross-platform.
- Highlight that the ARM Template Toolkit (arm-ttk) can be run on Linux (if possible), or provide alternative validation tools for Linux users.
- When listing deployment options, alternate the order or explicitly state parity between PowerShell and CLI, and provide example commands for both.
- Add references or links to Linux-specific guidance or quickstarts, ensuring Linux users feel equally supported.
Create Pull Request