Bias Analysis
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation page demonstrates a Windows bias in several ways: Windows and PowerShell tools are consistently presented alongside or before Linux alternatives, with many examples and features described as Windows-only or with limited Linux support. Some features (like Kudu, App Service editor, and console access) are unavailable or unsupported on Linux. Migration scenarios and in-portal editing are focused on Windows, with Linux options described as limited or deprecated. There is a lack of Linux-specific command examples, and Linux limitations are often highlighted without offering equivalent alternatives.
Recommendations
- Provide Linux-specific examples and workflows for all CLI and PowerShell commands, including explicit bash or shell usage where relevant.
- Clearly indicate Linux support status for each feature, and offer alternative Linux-compatible tools or approaches when Windows-only tools are mentioned (e.g., alternatives to Kudu, App Service editor, or Windows console).
- Add parity for plan migration scenarios, including explicit instructions for Linux-based function apps and clarify any limitations with actionable alternatives.
- Where features are unavailable on Linux, suggest best practices or workarounds for Linux users (e.g., using local development, deployment via Core Tools, or SSH access).
- Ensure that documentation does not default to Windows-first language or examples, and strive for equal prominence of Linux and Windows throughout the page.
Create Pull Request