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
⚠️
powershell_heavy
Summary:
The documentation exhibits a Windows-first bias in several areas. Windows-specific paths, tools, and terminology (such as 'D:\home', 'w3wp.exe', 'Web Deploy/MSDeploy', and references to Windows Communication Foundation) are mentioned before or instead of their Linux equivalents. Many examples and default values are given only for Windows, with Linux alternatives either missing, less detailed, or presented after the Windows information. Some features are described primarily in terms of Windows tooling and behaviors, with Linux support noted as an exception or afterthought.
Recommendations:
- Provide Linux and Windows examples side by side for environment variable values, file paths, and configuration steps.
- Ensure Linux-specific tools and behaviors (such as Oryx build automation, Linux file paths like '/home', and Linux container behaviors) are described with equal detail and prominence as Windows equivalents.
- Avoid using Windows terminology (e.g., 'D:\home', 'w3wp.exe', 'applicationHost.config') without also providing the Linux equivalent or clarifying when it is Windows-only.
- Where features or settings differ between Windows and Linux, clearly indicate the differences in a comparative table or callout, rather than describing Windows as the default and Linux as an exception.
- Add Linux-specific troubleshooting steps, examples, and references (e.g., for log file locations, deployment methods, and runtime behaviors) wherever Windows-specific guidance is given.
- Review and update references to Windows-only tools (such as MSDeploy, Web Deploy, and PowerShell scripts) to include Linux-friendly alternatives (such as SCP, rsync, Azure CLI, or bash scripts).
Create pull request