Document Details
Vm Applications How To
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 exhibits a moderate Windows bias. Many code samples, especially in CI/CD pipeline sections (GitHub Actions, Azure DevOps, GitLab, Jenkins), default to Windows application file types (e.g., app.exe, app-config.json) and set --os-type Windows by default, even when running on Linux agents. PowerShell examples are abundant and sometimes precede or outnumber Linux/bash equivalents. Some install script examples for Windows (.exe, .msi, .ps1) are more detailed than their Linux counterparts. In multi-platform sections, Windows tools and patterns (msiexec, powershell.exe, .exe installers) are mentioned first or exclusively, while Linux equivalents (e.g., .deb, .rpm, .sh) are present but less emphasized. There are cases where Linux-specific examples or instructions are missing or less detailed, especially in automation pipelines.
Recommendations
- In CI/CD pipeline examples (GitHub Actions, Azure DevOps, GitLab, Jenkins), provide parallel Linux-centric samples (e.g., using .sh, .deb, .rpm files and --os-type Linux) and clarify how to deploy Linux applications.
- When showing install script examples, ensure Linux formats (.sh, .tar, .deb, .rpm) are given equal prominence and detail as Windows formats.
- Avoid defaulting to Windows file types (app.exe, app-config.json) in generic examples; use neutral or alternate Linux file types (app.sh, app-config.yaml) or show both.
- In sections where --os-type is set, explain how to set for Linux and Windows, and provide both examples.
- Balance PowerShell and bash examples, and avoid placing Windows/PowerShell instructions before Linux/bash unless contextually justified.
- Explicitly call out Linux prerequisites, tools, and patterns where Windows tools are mentioned (e.g., mention unzip/tar for Linux when msiexec/tar for Windows is shown).
Create Pull Request
Scan History
| Date | Scan | Status | Result |
|---|---|---|---|
| 2026-01-14 01:31 | #124 | completed |
Biased
|
| 2026-01-13 06:17 | #109 | completed |
Biased
|
| 2026-01-12 00:00 | #101 | completed |
Biased
|
| 2026-01-10 00:00 | #94 | completed |
 Clean
|
| 2026-01-09 19:00 | #91 | completed |
Clean
|
| 2026-01-06 22:28 | #80 | completed |
Clean
|