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 exhibits a Windows-first bias in several ways. Windows-specific paths and tools (such as D:\home, Web Deploy/MSDeploy, and references to IIS, w3wp.exe, and applicationHost.config) are mentioned frequently and often before or instead of their Linux equivalents. Many environment variable descriptions and examples default to Windows conventions, with Linux details sometimes appearing as an afterthought or not at all. There are also numerous references to Windows-specific behaviors, tools, and error messages, while Linux-specific guidance is less detailed or omitted.
Recommendations:
- Ensure that all environment variable descriptions and examples include both Windows and Linux paths, formats, and behaviors where applicable.
- When mentioning tools or deployment methods (e.g., Web Deploy/MSDeploy), provide equivalent Linux-native alternatives or clarify their applicability.
- Avoid defaulting to Windows paths (e.g., D:\home) in examples; instead, show both Windows and Linux paths side by side.
- Balance the level of detail for Windows and Linux throughout the documentation, especially in troubleshooting and configuration sections.
- Where Windows-specific settings or behaviors are described, explicitly state if and how they differ on Linux, and provide Linux-specific guidance.
- Review and expand Linux-specific sections (such as Oryx build automation) to match the depth and clarity of the Windows/Kudu sections.
- Audit for references to Windows-only tools, error messages, or file structures, and add Linux equivalents or clarifications as needed.
Create pull request