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
Bias Types:
⚠️
windows_first
⚠️
powershell_heavy
⚠️
windows_tools
Summary:
The documentation is generally cross-platform and Linux-focused for hosting, but there are subtle Windows biases in development and publishing workflows. Windows terminology ("command prompt"), references to developing on Windows, and recommendations for remote build when developing on Windows are present. There is also a lack of explicit Linux/macOS CLI examples or terminal commands, and no mention of Linux-specific tools or shell environments. The documentation does not provide parity in examples for Linux users, and the language often assumes familiarity with Windows development environments.
Recommendations:
- Provide explicit Linux/macOS shell examples (e.g., bash/zsh) alongside any Windows command prompt or PowerShell commands.
- Use cross-platform terminology such as "terminal" instead of "command prompt" or "command line" instead of "command prompt".
- When referencing development environments, mention Linux/macOS terminals and shells (e.g., bash, zsh) in addition to Windows command prompt/PowerShell.
- Include notes or examples for installing prerequisites (such as Azure Functions Core Tools, Python, etc.) on Linux/macOS, not just Windows.
- Clarify that all CLI commands work on Linux/macOS and provide any necessary differences (such as path separators or environment variable syntax).
- Highlight Linux-native workflows and tools where appropriate, especially since Azure Functions Python hosting is Linux-only.
- Avoid recommending remote build only for Windows users; instead, explain the pros and cons for each OS and let users choose based on their workflow.
Create pull request