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 paths and conventions are often mentioned before or instead of Linux equivalents (e.g., 'D:\home' before '/home'), Windows-specific tools and settings (such as MSDeploy, Web Deploy, and IIS) are referenced without always providing Linux alternatives, and some configuration examples use Windows environment variable syntax or reference Windows-only features. While there are sections for Linux (e.g., Oryx build, Linux-specific variables), Windows terminology and tools are generally foregrounded, and Linux examples or explanations are sometimes missing or less detailed.
Recommendations:
- For every environment variable or feature that behaves differently on Windows and Linux, provide both Windows and Linux examples side by side.
- When referencing file paths, always show both Windows (e.g., 'D:\home') and Linux ('/home') formats together.
- Avoid using Windows environment variable syntax (e.g., '%HOME%') exclusively; include Linux syntax ('$HOME') as well.
- When mentioning deployment tools (e.g., MSDeploy, Web Deploy), explicitly state their Linux alternatives or note if not available.
- Ensure that Linux-specific build and deployment flows are as thoroughly documented as Windows ones, with equal detail and prominence.
- Review all sections for references to Windows-only features or behaviors and clarify their applicability to Linux or provide Linux equivalents where possible.
- In tables and lists, avoid placing Windows-specific information first by default; alternate or present both platforms equally.
Create pull request