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
missing_linux_example
windows_tools
Summary
The documentation claims support for both Windows and Linux Arc-enabled servers, but the majority of concrete examples (especially in PowerShell and REST API sections) are Windows-centric. PowerShell examples use Windows-style paths and scripts, and REST API examples exclusively show Windows firewall configuration (New-NetFirewallRule, .ps1 scripts). There are no Linux-specific script examples (e.g., bash, shell scripts, or Linux firewall commands like iptables or ufw). Azure CLI examples use PowerShell-style commands (Write-Host), and there are no Linux shell script examples. The documentation also references Windows tools (e.g., New-AzStorageBlobSASToken) without mentioning Linux alternatives. Linux is only mentioned in passing, and Linux-specific scripting patterns are not demonstrated.
Recommendations
  • Add Linux-specific script examples in all sections (PowerShell, Azure CLI, REST API), such as running bash scripts, using Linux shell commands (e.g., echo, id, iptables, ufw), and referencing .sh files.
  • In the REST API section, provide a Linux scenario (e.g., configuring a firewall rule with iptables or ufw) alongside the Windows example.
  • When showing how to upload or reference scripts, include Linux file paths and script types (.sh) as well as Windows (.ps1).
  • For Azure CLI examples, use Linux-native commands (e.g., echo, id) and show both Windows and Linux script invocations.
  • Reference cross-platform tools or clarify that New-AzStorageBlobSASToken is available on all platforms, or provide az CLI equivalents.
  • Explicitly call out any differences in script parameter handling between Windows and Linux, and provide examples for both.
GitHub Create Pull Request

Scan History

Date Scan Status Result
2026-03-10 00:00 #475 in_progress Biased Biased
2026-03-09 00:00 #471 in_progress Biased Biased
2026-03-08 00:00 #467 in_progress Biased Biased
2026-03-07 00:00 #463 in_progress Biased Biased
2026-03-06 00:00 #459 in_progress Biased Biased
2026-03-05 00:00 #455 in_progress Biased Biased
2026-03-04 00:00 #451 in_progress Biased Biased
2026-03-03 00:00 #447 in_progress Biased Biased
2026-03-02 00:00 #443 in_progress Biased Biased
2026-03-01 00:00 #439 in_progress Biased Biased
2026-02-28 00:00 #435 in_progress Biased Biased
2026-02-27 00:00 #431 in_progress Biased Biased
2026-02-26 00:00 #427 in_progress Biased Biased
2026-02-25 00:00 #423 in_progress Biased Biased
2026-02-23 00:00 #415 in_progress Biased Biased
2026-02-22 00:00 #411 in_progress Biased Biased
2026-02-21 00:00 #407 in_progress Biased Biased
2026-02-20 00:00 #403 in_progress Biased Biased
2026-02-19 00:00 #399 in_progress Biased Biased
2026-02-18 00:00 #395 in_progress Biased Biased
2026-02-17 00:00 #391 in_progress Biased Biased
2026-02-16 00:00 #387 in_progress Biased Biased
2026-02-15 00:00 #383 in_progress Biased Biased
2026-02-14 00:00 #379 in_progress Biased Biased
2026-02-13 00:00 #375 in_progress Biased Biased
2026-02-12 00:00 #371 in_progress Clean Clean
2026-02-11 00:00 #367 in_progress Clean Clean
2026-02-10 00:00 #363 completed Biased Biased
2026-02-09 00:00 #359 completed Clean Clean
2026-02-08 00:00 #355 completed Biased Biased
2026-02-05 00:00 #343 completed Biased Biased
2026-02-04 00:00 #339 completed Biased Biased
2026-02-03 00:00 #335 completed Biased Biased
2026-01-14 00:00 #251 completed Biased Biased
2026-01-13 00:00 #247 completed Biased Biased
2026-01-11 00:00 #241 completed Biased Biased
2026-01-10 00:00 #238 completed Biased Biased
2026-01-09 00:34 #235 completed Biased Biased
2026-01-08 00:53 #232 completed Biased Biased

Flagged Code Snippets