Document Details

Vm Applications How To
Home / Scan #124 / Vm Applications How To
Sad Tux - Windows bias detected
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.
GitHub View on GitHub 📚 View on Microsoft Learn

Bias Analysis

Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation exhibits a notable Windows bias in several areas. Windows and PowerShell examples are frequently presented first or exclusively (e.g., .EXE, .MSI, .PS install scripts), and Windows-specific tools and patterns (msiexec, powershell.exe, .exe/.msi packaging) are emphasized. In CI/CD pipeline samples (GitHub Actions, Azure DevOps, GitLab, Jenkins), the default application and config file names are always Windows-centric (.exe, .json), and the creation of VM Application definitions defaults to Windows OS type, with no parallel Linux example. While Linux install script examples are present for .tar, .deb, .rpm, and .sh, the overall flow and automation guidance prioritize Windows scenarios, and Linux parity is not consistently maintained.
Recommendations
  • Provide Linux-first or side-by-side examples for all install script types, especially for .deb, .rpm, .sh, and .tar.gz.
  • In CI/CD pipeline samples, alternate or parallelize examples for Linux apps (e.g., use app.sh, app.deb, app-config.yaml) and set --os-type Linux in at least half of the samples.
  • Explicitly show how to create and deploy Linux VM Applications in automation flows (GitHub Actions, DevOps, etc.), not just Windows.
  • Balance the order of presentation so Linux and Windows examples are equally visible and accessible.
  • Avoid defaulting to Windows file types (.exe, .msi, .json) in variable names and sample scripts; use generic or Linux-centric names where appropriate.
  • Add guidance for Linux-specific packaging and deployment nuances (e.g., SELinux, systemd integration, permissions).
GitHub Create Pull Request

Scan History

Date Scan Status Result
2026-01-14 01:31 #124 completed Biased Biased
2026-01-13 06:17 #109 completed Biased Biased
2026-01-12 00:00 #101 completed Biased Biased
2026-01-10 00:00 #94 completed Clean Clean
2026-01-09 19:00 #91 completed Clean Clean
2026-01-06 22:28 #80 completed Clean Clean

Flagged Code Snippets