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
Summary:
The documentation demonstrates a mild Windows bias. In several places, Windows-specific tools, paths, or behaviors are mentioned before or instead of Linux equivalents. For example, the use of Windows-style environment variable syntax (e.g., %HOME%\typescript), the explicit mention of Windows-only settings (e.g., WEBSITE_NODE_DEFAULT_VERSION), and the use of Windows paths (e.g., d:\home\data\SitePackages) without always providing Linux alternatives. Some instructions and examples are Windows-centric or lack Linux-specific guidance, even though Azure Functions is cross-platform.
Recommendations:
- For every Windows-specific example or path (e.g., %HOME%\typescript, d:\home\data\SitePackages), provide the Linux equivalent (e.g., $HOME/typescript, /home/site/wwwroot/SitePackages).
- When describing OS-specific behaviors (such as environment variable delimiters), always mention Linux behavior first or equally, and clarify differences explicitly.
- For settings that are Windows-only (e.g., WEBSITE_NODE_DEFAULT_VERSION), clearly state the Linux alternative or note if not applicable.
- When referencing tools (e.g., Azure PowerShell), mention Azure CLI alongside it, and provide CLI examples where possible.
- Audit all sample values and code snippets to ensure parity between Windows and Linux, especially for file paths and environment variable syntax.
- Add explicit Linux examples for local development and deployment scenarios, not just references to local.settings.json.
- Review and update legacy references (such as d:\ paths) to clarify their relevance for Windows only, and provide Linux context.
Create pull request