Document Details
Configure Language Nodejs
This page contains Windows bias
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
Detected Bias Types
windows_first
windows_tools
powershell_heavy
missing_linux_example
Summary
The documentation demonstrates a moderate Windows bias. Windows-specific tools and patterns (such as IISNode, web.config, and PowerShell) are mentioned prominently, sometimes before or in more detail than their Linux equivalents. Windows examples or explanations often precede Linux ones, and some advanced configuration or troubleshooting steps are only detailed for Windows (e.g., web.config troubleshooting), with Linux sections being more generic or referring to includes. PowerShell is referenced for Application Insights instrumentation, with no equivalent Bash/Azure CLI example for Linux. Some sections (like custom deployment scripts) are more detailed for Linux, but overall, Windows concepts and tools are more deeply integrated and explained.
Recommendations
- Ensure Linux and Windows instructions/examples are presented with equal prominence and detail, ideally side-by-side or in parallel sections.
- For every PowerShell or Windows tool reference (e.g., web.config, IISNode), provide the Linux/container equivalent (e.g., startup scripts, PM2, nginx/apache config, etc.), or explicitly state when there is no equivalent.
- Add Bash/Azure CLI examples for Application Insights instrumentation on Linux, not just PowerShell.
- Expand troubleshooting and advanced configuration sections for Linux to match the depth provided for Windows (e.g., what to do if the app does not start, common misconfigurations, etc.).
- When referencing tools like IISNode or web.config, clarify their scope (Windows-only) and provide links or guidance for Linux users.
- Review the order of presentation so that Linux and Windows are treated equally, or alternate which platform is presented first in each section.
Create Pull Request
Scan History
| Date | Scan | Status | Result |
|---|---|---|---|
| 2026-01-14 00:00 | #250 | in_progress |
Biased
|
| 2026-01-13 00:00 | #246 | completed |
Biased
|
| 2026-01-12 00:00 | #243 | cancelled |
Biased
|
| 2026-01-11 00:00 | #240 | completed |
Biased
|
| 2026-01-10 00:00 | #237 | completed |
Biased
|
| 2026-01-09 00:34 | #234 | completed |
Biased
|
| 2026-01-08 00:53 | #231 | completed |
Biased
|
| 2026-01-08 00:00 | #228 | cancelled |
 Clean
|
| 2026-01-06 18:15 | #225 | cancelled |
Clean
|
| 2025-09-14 00:00 | #111 | completed |
Clean
|
| 2025-09-13 00:00 | #110 | completed |
Clean
|
| 2025-09-12 00:00 | #109 | completed |
Clean
|
| 2025-09-11 00:00 | #108 | completed |
Clean
|
| 2025-09-10 00:00 | #107 | completed |
Clean
|
| 2025-09-09 00:00 | #106 | completed |
Clean
|
| 2025-08-15 00:01 | #81 | cancelled |
Biased
|
| 2025-07-13 21:37 | #48 | completed |
Biased
|
| 2025-07-13 21:25 | #47 | cancelled |
Clean
|
| 2025-07-13 20:48 | #44 | cancelled |
Biased
|
| 2025-07-09 13:09 | #3 | cancelled |
Clean
|
| 2025-07-08 04:23 | #2 | cancelled |
Biased
|
Flagged Code Snippets
::: zone-end ## Set Node.js version ::: zone pivot="platform-windows" To set your app to a [supported Node.js version](#show-nodejs-version), run the following command in the [Cloud Shell](https://shell.azure.com) to set `WEBSITE_NODE_DEFAULT_VERSION` to a supported version: