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 areas. Windows-specific paths, tools, and conventions are mentioned before or instead of Linux equivalents. Many environment variable descriptions and examples use Windows paths (e.g., D:\home), reference Windows-specific tools (e.g., msbuild, Web Deploy/MSDeploy), and discuss Windows behaviors in more detail. Linux-specific information is often less detailed, appears after Windows content, or is missing entirely. Some features are described as 'Windows only' without clear Linux alternatives or parity.
Recommendations:
- For every environment variable or feature that behaves differently on Windows and Linux, provide parallel examples and explanations for both platforms.
- When mentioning file paths, always include both Windows and Linux formats (e.g., D:\home and /home).
- Avoid using Windows-specific tools (like msbuild, Web Deploy/MSDeploy) as the default or only example; include Linux-native equivalents or alternatives (such as Oryx, Kudu for Linux, or CLI commands).
- In tables and explanations, do not default to Windows terminology or behaviors; explicitly state platform differences and ensure Linux is not an afterthought.
- Where features are Windows-only, clearly state whether there is Linux parity or a roadmap for it, and provide Linux workarounds if available.
- Add Linux/POSIX shell command examples where PowerShell or CMD is used.
- Review and expand Linux-specific documentation sections (such as Oryx build automation) to match the detail and clarity given to Windows/Kudu.
Create pull request