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
⚠️
powershell_heavy
⚠️
windows_tools
Summary:
The documentation generally provides parity between Linux and Windows, but there are subtle signs of Windows bias. In several sections, Windows instructions or tools (such as Kudu, Advanced Tools, and FTPS) are mentioned first or in more detail. Some diagnostic and profiler steps for Windows use the Kudu/SCM portal and FTPS, which are more familiar to Windows users, while Linux sections focus on SSH and CLI. There are also references to Windows-specific conventions (such as web.config) and file paths (C:\home), and some notes are specifically about Windows behavior. However, Linux coverage is strong, with detailed SSH, CLI, and container-based examples, and Linux is often mentioned explicitly in configuration and deployment examples.
Recommendations:
- Ensure that Linux and Windows instructions are always presented in parallel, with neither platform consistently preceding the other.
- Where Windows tools like Kudu/SCM or FTPS are mentioned, provide equivalent Linux-native approaches (e.g., SCP, SFTP, rsync) or clarify that these tools are cross-platform.
- Avoid Windows-centric terminology (such as 'web.config') in general notes; clarify when something is Windows-only.
- For sections like Java Flight Recorder and logging, ensure Linux and Windows have equally detailed, step-by-step instructions, including troubleshooting tips.
- Highlight Linux-specific best practices and tools (e.g., using package managers, shell scripting) as prominently as Windows tools.
- Review for any subtle ordering bias (e.g., always listing Windows before Linux) and alternate the order or present both together.
Create pull request