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
⚠️
powershell_heavy
Summary:
The documentation exhibits a mild Windows bias in several areas: Windows terminology ("command prompt") is used alongside or before cross-platform terms ("terminal"), and recommendations for development and publishing workflows often mention Windows scenarios first or specifically. The 'Remote build' section explicitly recommends remote build for Windows users and discourages local builds on Windows, and the phrase 'command prompt' is used instead of 'shell' or 'terminal'. There are also references to Windows-specific patterns (e.g., Visual Studio Code, which is cross-platform but often associated with Windows in Microsoft docs). However, Linux is well represented in hosting and deployment sections, and no critical Linux functionality is missing.
Recommendations:
- Replace 'command prompt' with 'terminal' or 'shell', or clarify with 'terminal (Linux/macOS) or command prompt (Windows)'.
- When listing development options, avoid putting Windows-specific tools or terminology first unless there is a technical reason.
- In the 'Publishing to Azure' section, clarify that both remote and local builds are supported on all platforms, and provide parity in recommendations for Linux/macOS users.
- Where possible, provide explicit Linux/macOS command-line examples (e.g., using bash) alongside any Windows-specific instructions.
- Review all references to Visual Studio Code to ensure they are presented as cross-platform, and consider mentioning other popular Linux editors or tools if appropriate.
- Audit for any subtle language that assumes a Windows environment (e.g., file paths, environment variable syntax) and provide Linux/macOS equivalents where relevant.
Create pull request