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
⚠️
missing_linux_example
Summary:
The documentation demonstrates a Windows-first bias in several areas: Windows-specific deployment methods (such as source control, Local Git, and FTPS) are called out as 'Windows-only' in the availability table, with no Linux equivalents or alternatives described. Explanations of remote build and deployment behaviors often start with Windows, providing more detail for Windows scenarios (e.g., Kudu/SCM site), and Linux instructions are less prominent or require additional manual configuration. There are also references to Visual Studio (a Windows-centric tool) before cross-platform or Linux-native tools, and some deployment methods (e.g., FTPS, Local Git) lack Linux-specific guidance or alternatives.
Recommendations:
- Provide Linux equivalents or alternatives for deployment methods currently marked as 'Windows-only' (e.g., Source Control, Local Git, FTPS), or clearly state if no equivalent exists and suggest best practices for Linux users.
- Ensure that deployment examples and instructions are given for both Windows and Linux platforms, ideally side-by-side or with equal prominence.
- When listing tools, mention cross-platform options (e.g., Azure Functions Core Tools, VS Code) before Windows-specific tools (e.g., Visual Studio), or present them together.
- Expand explanations for Linux deployment scenarios, including details on how to perform common tasks (such as remote build, trigger syncing, or storage configuration) on Linux.
- Where a feature is not available on Linux, provide a rationale and suggest alternative workflows for Linux users.
Create pull request