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
⚠️
windows_tools
Summary:
The documentation generally maintains good cross-platform parity, but there are subtle signs of Windows bias. In particular, references to 'command prompt' and 'Terminal or command prompt' as development environments, and recommendations to use remote build when developing on Windows, suggest a Windows-first perspective. The documentation also mentions that Python is supported only on Linux-based hosting plans, but local development on Windows is possible. There are no explicit PowerShell-heavy examples, and Linux is well-represented in hosting and deployment sections. However, Linux CLI tools (like bash) are not mentioned, and Windows terminology (e.g., 'command prompt') is used preferentially.
Recommendations:
- Use neutral terminology such as 'terminal' or 'shell' instead of 'command prompt' to avoid Windows-centric language.
- Explicitly mention both Windows and Linux/macOS development environments and tools (e.g., 'Command Prompt or Bash terminal') in all relevant sections.
- Provide example commands for both Windows and Linux shells where applicable, especially in setup and deployment instructions.
- Clarify that Azure Functions Core Tools and related workflows are fully supported on Linux/macOS, and link to any Linux/macOS-specific guidance if available.
- When recommending remote or local build, explain the rationale for both Windows and Linux users, and avoid implying that Windows is the default or primary development environment.
Create pull request