Bias Analysis
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation demonstrates Windows bias by referencing Windows-specific paths (e.g., %HOME%\site), mentioning Kudu and FTP credentials (commonly used in Windows workflows), and providing links to PowerShell-based cloning guides as the only 'Next steps'. Examples and terminology (such as session affinity and Kudu) are presented with Windows conventions first or exclusively. There is a lack of explicit Linux or cross-platform command-line examples (e.g., Bash, Azure CLI), and Linux-specific considerations (such as file permissions, case sensitivity, or deployment patterns) are not addressed.
Recommendations
- Include Linux/Bash examples alongside or before PowerShell examples, especially for tasks like app cloning and backup/restore.
- Reference Azure CLI commands in addition to PowerShell for resource management and deployment steps.
- Clarify that Kudu and FTP credentials are available and relevant for both Windows and Linux App Service plans, or provide Linux-specific alternatives.
- Discuss Linux-specific considerations, such as file system case sensitivity, permissions, and deployment patterns (e.g., zip deploy, container-based workflows).
- Balance references to Windows paths (e.g., %HOME%\site) with Linux equivalents (e.g., $HOME/site), and explain any differences in environment variables or file system structure.
- Add links to Linux-focused documentation or guides in the 'Next steps' section.
Create Pull Request