Bias Analysis
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation page shows a mild Windows bias: PowerShell is mentioned and linked before Azure CLI, and Visual Studio (a Windows-centric tool) is highlighted as a deployment method, including references to PowerShell scripts. There are no explicit Linux/macOS command-line examples or references to Linux-native editors (e.g., vim, nano), and the .NET client library example links to a Windows-specific page. While cross-platform tools like VS Code and Azure CLI are mentioned, Windows tools and patterns are presented first or with more detail.
Recommendations
- Present Azure CLI examples and links before or alongside PowerShell to emphasize cross-platform support.
- Include explicit Linux/macOS command-line examples for template deployment (e.g., bash scripts, use of native editors).
- Mention Linux-native editors (vim, nano, gedit) as alternatives to VS Code for editing templates.
- Provide parity in client library examples, linking to both Windows and Linux/.NET Core documentation.
- Clarify that all deployment methods (CLI, REST API) work on Linux/macOS as well as Windows.
Create Pull Request