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.

Bias Analysis

Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation page exhibits a Windows bias in several ways. The Windows section is presented first and in greater detail, with step-by-step instructions that rely heavily on Windows-specific tools (Visual Studio, Windows Explorer, PowerShell scripts). The Windows workflow is tightly coupled to the Visual Studio GUI and Windows file management patterns, with no mention of equivalent Linux or cross-platform approaches for those steps. There is no guidance for performing the Windows scenario from a non-Windows environment, and the Linux section is entirely separate, with no cross-references or parity in application scenario (the Windows example is ASP.NET with custom fonts, while the Linux example is a generic Django/Flask app). There are also missing Linux equivalents for certain steps (e.g., installing custom fonts in a Linux container, using PowerShell scripts for configuration).
Recommendations
  • Provide Linux or cross-platform equivalents for all steps shown in the Windows workflow, especially for application scenarios that require OS-level customization (e.g., installing fonts in a Linux container, not just Windows).
  • Avoid presenting Windows as the default or primary platform by giving equal prominence to both Windows and Linux pivots, or by starting with a neutral introduction.
  • Replace or supplement Windows-specific tooling (Visual Studio, Windows Explorer, PowerShell scripts) with cross-platform alternatives (VS Code, command-line instructions, Bash scripts) where possible.
  • For steps that require file installation or OS customization, show how to achieve the same result in a Linux container (e.g., using apt-get to install fonts, Bash scripts for automation).
  • Ensure that advanced scenarios (such as custom OS configuration, font installation, or other integrations) are demonstrated for both Windows and Linux, not just Windows.
  • Where PowerShell scripts are used, provide Bash equivalents for Linux users.
  • Explicitly mention any limitations or differences between Windows and Linux container support in App Service, and provide guidance for users migrating from either platform.
  • Consider using a consistent sample application or scenario across both pivots to better illustrate parity.
GitHub Create Pull Request

Scan History

Date Scan Status Result
2026-01-14 00:00 #250 in_progress Biased Biased
2026-01-13 00:00 #246 completed Biased Biased
2026-01-12 00:00 #243 cancelled Biased Biased
2026-01-11 00:00 #240 completed Biased Biased
2026-01-10 00:00 #237 completed Biased Biased
2026-01-09 00:34 #234 completed Biased Biased
2026-01-08 00:53 #231 completed Clean Clean
2026-01-06 18:15 #225 cancelled Clean Clean
2025-09-16 00:00 #113 completed Clean Clean
2025-09-15 00:00 #112 completed Clean Clean
2025-09-14 00:00 #111 completed Clean Clean
2025-09-13 00:00 #110 completed Clean Clean
2025-09-12 00:00 #109 completed Clean Clean
2025-09-11 00:00 #108 completed Clean Clean
2025-09-10 00:00 #107 completed Clean Clean
2025-09-09 00:00 #106 completed Clean Clean
2025-08-17 00:01 #83 cancelled Biased Biased
2025-07-13 21:37 #48 completed Biased Biased
2025-07-09 13:09 #3 cancelled Clean Clean
2025-07-08 04:23 #2 cancelled Biased Biased

Flagged Code Snippets

FROM mcr.microsoft.com/dotnet/framework/aspnet:4.7.2-windowsservercore-ltsc2019