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
⚠️
missing_linux_example
Summary:
The documentation is structured with a clear separation between Windows and Linux content using pivots, which is good for parity. However, there are several signs of Windows bias: Windows sections are often presented first, Windows-specific tools and patterns (like KuduScript, .dll extensions, and Windows file paths) are emphasized, and some deployment automation examples (e.g., custom deployment scripts for Composer, Bower, Gulp, Grunt) are only detailed for Windows, with no equivalent Linux guidance. In some areas, Linux instructions are less detailed or require more manual steps (e.g., editing .ini files via echo due to lack of editors).
Recommendations:
- Alternate the order of Windows and Linux pivots or present Linux first in some sections to avoid implicit prioritization.
- Provide equivalent, detailed Linux examples for deployment automation tools (Composer, Bower, Gulp, Grunt), including how to generate and use custom deployment scripts in Linux App Service.
- Where Windows-specific tools (like KuduScript) are recommended, clarify if/how they are supported on Linux, or provide Linux-native alternatives.
- For file editing on Linux (e.g., .ini files), suggest practical alternatives or tools for editing files, or provide downloadable templates to reduce manual echo commands.
- Ensure all troubleshooting and advanced configuration sections have Linux parity, with step-by-step instructions matching the detail level of Windows.
- Highlight any differences in extension compatibility or deployment patterns between Windows and Linux, and provide guidance for both.
Create pull request