Sad Tux - Windows bias detected
This page contains Windows bias

About This Page

This page is part of the Azure documentation. It contains code examples and configuration instructions for working with Azure services.

Bias Analysis

Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation demonstrates a subtle Windows bias by referencing Visual Studio and Visual Studio Code (both Windows-centric or Windows-first tools) as primary editors for ARM templates, and by providing guidance and screenshots for these tools exclusively. There are no examples or mentions of Linux-native editors or workflows (such as Vim, Emacs, nano, or Linux-specific VS Code usage). Additionally, the only explicit mention of deploying templates with multi-line strings refers to Azure PowerShell (Windows-first) and Azure CLI, but does not provide Linux-specific instructions or considerations. There are no Linux shell (bash) or cross-platform command-line examples, and the documentation does not acknowledge Linux users' needs for editor configuration or deployment nuances.
Recommendations
  • Include examples and guidance for editing ARM templates using popular Linux editors (e.g., Vim, nano, Emacs) and how to enable JSONC or handle comments in those environments.
  • Add explicit instructions or screenshots for using Visual Studio Code on Linux, or mention that VS Code is cross-platform.
  • When discussing deployment via Azure CLI, clarify that the instructions apply equally to Linux, macOS, and Windows, and provide bash/zsh shell command examples where relevant.
  • Reference Linux-native tools and workflows where appropriate, such as using jq for JSON validation or manipulation.
  • Ensure that any references to PowerShell or Visual Studio are balanced with equivalent Linux-friendly alternatives (e.g., Azure CLI in bash, VS Code on Linux, or other editors).
  • Add a note that ARM template development and deployment is fully supported on Linux and macOS, not just Windows.
GitHub Create Pull Request

Scan History

Date Scan Status Result
2026-01-14 00:00 #250 in_progress Biased Biased
2026-01-13 00:00 #246 completed Biased Biased
2026-01-12 00:00 #243 cancelled Biased Biased
2026-01-11 00:00 #240 completed Biased Biased
2026-01-10 00:00 #237 completed Biased Biased
2026-01-09 00:34 #234 completed Biased Biased
2026-01-08 00:53 #231 completed Biased Biased
2026-01-06 18:15 #225 cancelled Clean Clean
2025-08-17 00:01 #83 cancelled Clean Clean
2025-07-13 21:37 #48 completed Biased Biased

Flagged Code Snippets