Bias Analysis
Detected Bias Types
windows_tools
windows_first
powershell_heavy
windows_examples
Summary
The documentation page generally provides cross-platform instructions for developing Azure Functions locally using Core Tools, but there are several subtle signs of Windows bias. Windows-specific tools (PowerShell, cmd) are mentioned alongside or before Linux equivalents, and some examples are shown for both Bash and Windows command line, with Windows syntax sometimes appearing first. The use of terms like 'command prompt' and references to func.exe also reflect Windows-centric language. The installation and usage instructions for Azure CLI and Azure PowerShell are presented together, but Linux-specific alternatives (e.g., bash scripts) are not highlighted. The cURL tool is described as being available by default on Linux and newer Windows, but the Windows installation is called out separately, suggesting a Windows-first audience. PowerShell is given its own programming language pivot, which may reinforce the Windows focus.
Recommendations
- Ensure all examples are shown for both Linux/macOS and Windows, with equal prominence and ordering.
- Use neutral terminology such as 'terminal' or 'shell' instead of 'command prompt' and avoid references to func.exe unless platform-specific.
- Highlight Linux/macOS installation and usage patterns for Azure CLI and other tools, and provide bash/zsh script examples where appropriate.
- When showing command examples, alternate the order or group them by platform rather than always showing Windows first.
- Clarify that Core Tools and related workflows are fully supported on Linux/macOS, and link to platform-specific installation guides.
- Consider adding troubleshooting notes for common Linux/macOS issues (e.g., permissions, path, npm installation).
Create Pull Request