55
Total Pages
48
Linux-Friendly Pages
7
Pages with Bias
12.7%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues (16)

Page-Level Analysis

Windows First Powershell Heavy
Summary:
The documentation demonstrates mild Windows bias by referencing PowerShell-specific syntax and issues before or more prominently than Linux equivalents. While the primary examples use Bash/Azure Cloud Shell, there are multiple notes and tips about PowerShell-specific line continuation and escaping, without providing equivalent Linux/Bash troubleshooting or tips. No Linux examples are missing, but the documentation assumes familiarity with Windows/PowerShell environments.
Recommendations:
  • Balance PowerShell-specific notes with equivalent Bash/Linux tips (e.g., mention common Bash pitfalls or escaping requirements).
  • If providing PowerShell-specific syntax advice, also provide explicit Bash/Linux advice where relevant.
  • Consider including a PowerShell example block if PowerShell is supported, or clarify that Bash is the recommended shell for these commands.
  • Review the order of tips and notes to ensure Linux/Bash is not always presented as secondary to Windows/PowerShell.

Page-Level Analysis

Windows First Powershell Heavy
Summary:
The documentation demonstrates a mild Windows bias by referencing PowerShell-specific syntax and considerations before Linux/Bash equivalents, and by providing tips for PowerShell users while assuming Bash as the default. However, it does provide Bash-first CLI examples and does not omit Linux-specific instructions, but the presence of PowerShell notes and the order of browser support listings suggest a subtle prioritization of Windows environments.
Recommendations:
  • Provide explicit Linux and macOS instructions and examples alongside Windows/PowerShell, not just as notes.
  • List browser and tool support in a neutral or alphabetical order rather than putting Microsoft/Windows options first.
  • Where line continuation or command syntax differs between shells, show both Bash and PowerShell examples side by side.
  • Include references to common Linux tools (e.g., curl, jq) where relevant, not just Azure CLI.
  • Explicitly mention Linux and macOS compatibility in prerequisites and environment setup sections.

Page-Level Analysis

Powershell Heavy Windows Tools Missing Linux Example
Summary:
The documentation provides detailed PowerShell/MSAL.PS examples for obtaining OAuth tokens, but does not include equivalent Linux-native or cross-platform command-line examples (e.g., curl, Python, or bash). The focus on PowerShell and the MSAL.PS module, which is Windows-centric, may disadvantage Linux or macOS users. There is also a lack of explicit Linux or cross-platform guidance for authentication flows.
Recommendations:
  • Add examples using curl or HTTPie to demonstrate how to obtain OAuth tokens from the command line on Linux/macOS.
  • Include a Python example using MSAL or requests to show cross-platform programmatic authentication.
  • Explicitly mention that Azure CLI is cross-platform and provide more detailed CLI-based authentication flows.
  • Where PowerShell is used, provide equivalent bash or shell script examples for Linux users.
  • Review all sections for Windows-specific terminology or tool references and ensure Linux alternatives are presented with equal prominence.

Page-Level Analysis

Windows Tools Windows First
Summary:
The documentation page generally maintains cross-platform language and highlights Linux and MCU support, but it references the 'proven reliability of the Windows Update platform' as a foundational technology without mentioning Linux update mechanisms. There are no explicit Windows/Powershell examples or exclusive Windows tools, but the only platform-specific technology mentioned in the context of reliability and scale is Windows Update, which may imply a Windows-first perspective.
Recommendations:
  • Acknowledge the reliability and prevalence of Linux update mechanisms (such as APT, RPM, or Yocto-based OTA solutions) alongside Windows Update when discussing the foundational technologies behind Device Update.
  • Include references or examples of how Device Update leverages or integrates with common Linux update workflows, not just Windows.
  • Ensure that any mention of platform reliability or scale includes both Windows and Linux to avoid implying that Device Update is primarily based on Windows technologies.
  • If referencing Windows Update as a model, provide a parallel statement about Linux update systems to reinforce cross-platform parity.

Page-Level Analysis

Windows First Powershell Heavy
Summary:
The documentation is generally cross-platform and primarily uses Bash/Azure CLI examples, but it does exhibit some Windows bias by referencing PowerShell-specific syntax and workarounds before or instead of providing Linux equivalents. For example, there are tips about replacing Bash line continuations with PowerShell-specific characters and escaping JSON in PowerShell, but no equivalent Linux-specific guidance. No Windows-only tools are used, but the documentation assumes familiarity with PowerShell and Windows environments in its tips.
Recommendations:
  • Provide Linux-specific tips alongside PowerShell guidance, such as how to escape JSON in Bash or Zsh.
  • When mentioning PowerShell-specific syntax (e.g., line continuation, escaping), also explicitly state that the Bash examples work as-is on Linux/macOS.
  • If possible, add a short section or callout summarizing differences between running commands on Windows (PowerShell/CMD) and Linux/macOS (Bash), including any necessary adjustments.
  • Ensure that all examples and troubleshooting notes are equally applicable to both Linux and Windows users, or provide parallel guidance for each platform.

Page-Level Analysis

Windows Tools Missing Linux Example
Summary:
The documentation references a Windows PowerShell script (AduUpdate.psm1) for calculating file hashes but does not provide equivalent Linux or cross-platform examples. There are no Linux shell or cross-platform command examples for tasks like hash calculation, and the only tool mentioned is Windows-specific.
Recommendations:
  • Provide equivalent Linux (e.g., bash, sha256sum) and cross-platform (e.g., Python) examples for calculating file hashes alongside or instead of the PowerShell reference.
  • Mention and link to cross-platform tools or scripts for manifest preparation and hash calculation, not just Windows PowerShell modules.
  • Ensure that any referenced scripts or tools are available and documented for both Windows and Linux users.
  • Where possible, use neutral language and examples that are not specific to a single operating system.

Page-Level Analysis

Powershell Heavy Windows First
Summary:
The documentation is primarily Linux/Ubuntu-focused, but there is a notable instance where PowerShell (a Windows tool) is referenced as the default way to copy files to the VM, without providing a Linux or cross-platform alternative. This suggests a mild Windows bias in tooling assumptions, despite the overall Linux context.
Recommendations:
  • When providing file transfer instructions (such as using scp), offer both Windows (PowerShell) and Linux/macOS (native terminal) examples, or clarify that scp is available on all platforms.
  • If referencing PowerShell, also mention alternatives like Linux/macOS terminal or cross-platform tools (e.g., WinSCP, FileZilla, or native scp).
  • Review all command-line instructions to ensure they are platform-neutral or provide platform-specific variants as appropriate.
  • Explicitly state that the tutorial is Linux/Ubuntu-based, and provide links or notes for Windows users if relevant.

Page-Level Analysis

Windows First Powershell Heavy
Summary:
The documentation demonstrates a mild Windows bias by referencing PowerShell-specific syntax and providing guidance for PowerShell users before Linux users. While the main CLI examples use Bash syntax and recommend the Azure Cloud Shell (which is Bash-based), the documentation includes explicit instructions for PowerShell users, such as replacing backslashes with backticks for line continuation. There are no Linux-specific tools or troubleshooting steps, and the documentation does not provide parity for Linux command-line environments beyond Bash.
Recommendations:
  • Provide explicit Linux (non-Bash) and macOS instructions or notes where relevant, especially for users running CLI commands in native Linux terminals.
  • Include troubleshooting steps or references for common Linux issues (e.g., file permissions, path differences) when configuring the device agent.
  • Balance PowerShell-specific notes with equivalent notes for Linux shells (e.g., zsh, fish) or clarify that Bash syntax is cross-platform in Cloud Shell.
  • When referencing tools or environments, mention Linux-native options (e.g., WSL, native Linux Azure CLI installation) alongside Windows and PowerShell.
  • Ensure that any screenshots or UI references do not assume a Windows environment unless unavoidable.

Page-Level Analysis

Powershell Heavy Missing Linux Example Windows Tools
Summary:
The documentation provides detailed PowerShell examples for obtaining authentication tokens using the MSAL.PS module, but does not offer equivalent examples for Linux-native tools or scripting environments (such as Bash with curl, Python, or other cross-platform methods). The focus on PowerShell and the absence of Linux/Unix command-line examples indicate a Windows-centric bias. Additionally, the use of Azure CLI is shown, but only for a basic login/token retrieval, while advanced scenarios are only covered with PowerShell.
Recommendations:
  • Add equivalent Linux/Bash examples for obtaining OAuth tokens, such as using curl with the Microsoft identity platform endpoints.
  • Provide Python or other cross-platform scripting examples for authentication, especially for REST API calls.
  • When presenting PowerShell examples, also include Bash or shell script equivalents side-by-side.
  • Mention and demonstrate the use of cross-platform tools (e.g., Azure CLI, curl, Python requests) before or alongside Windows-specific tools like PowerShell.
  • Clarify in the documentation that all examples are cross-platform where possible, and explicitly note any platform-specific steps.

Page-Level Analysis

Windows Tools Missing Linux Example
Summary:
The documentation references a PowerShell function (Get-AduFileHashes in AduUpdate.psm1) as the example for calculating file hashes, but does not provide equivalent Linux or cross-platform command-line examples. No Linux-native tools or scripts are mentioned, and the only tooling guidance is specific to Windows/PowerShell.
Recommendations:
  • Provide equivalent Linux and cross-platform examples for calculating file hashes, such as using 'sha256sum' or 'openssl dgst -sha256' in Bash.
  • Mention or link to Linux shell scripts or commands that can generate the required base64-encoded SHA-256 hash.
  • If referencing a PowerShell script, clarify whether it is cross-platform (PowerShell Core) or Windows-only, and provide alternatives for other platforms.
  • Ensure that all tooling references are accompanied by platform-agnostic or platform-specific alternatives as appropriate.

Page-Level Analysis

Windows First Powershell Heavy
Summary:
The documentation is generally cross-platform and uses Azure CLI with Bash as the primary environment. However, there is a subtle Windows-first bias: PowerShell is mentioned as an alternative for line continuation syntax, and escaping JSON characters in PowerShell is specifically called out, while Linux/Bash is treated as the default. There are no explicit Linux examples missing, but the documentation assumes familiarity with PowerShell for Windows users and provides tips for them, which is a mild form of Windows-centric bias.
Recommendations:
  • Provide explicit Linux/Bash and Windows/PowerShell command examples side by side where syntax differs, rather than only mentioning PowerShell as an aside.
  • Include a table or section summarizing differences in command syntax and escaping for Bash vs. PowerShell, rather than only referencing PowerShell in tips.
  • Ensure that any tips or troubleshooting steps are equally detailed for both Linux and Windows environments.
  • Where possible, add examples or notes for MacOS users if there are any platform-specific considerations.

Page-Level Analysis

Windows First Powershell Heavy
Summary:
The documentation demonstrates a mild Windows bias by referencing PowerShell syntax and usage before mentioning Linux/Bash alternatives, and by providing tips that prioritize PowerShell users. However, the main command-line examples use Azure CLI with Bash syntax, and there are no exclusive Windows-only tools or missing Linux examples. The documentation does not provide Linux-specific troubleshooting or examples beyond Bash, and it assumes familiarity with Azure Portal (which is cross-platform but often associated with Windows environments).
Recommendations:
  • Provide explicit Linux command-line examples where relevant, especially for file path manipulations or troubleshooting.
  • Include notes or sections for common Linux shell environments (e.g., zsh, fish) if command syntax may differ.
  • Balance PowerShell tips with equivalent Bash/Linux shell tips, and avoid placing Windows/PowerShell guidance before Linux/Bash guidance unless usage data supports it.
  • Add troubleshooting steps or examples for both Windows and Linux environments, especially for device-side configuration and log file access.
  • Clarify that Azure Portal and Azure CLI are cross-platform, and provide links to Linux-specific installation or usage guides where appropriate.

Page-Level Analysis

Powershell Heavy Windows First
Summary:
The documentation is primarily focused on Linux (Ubuntu) for the device setup and update process, providing detailed shell (bash) commands and Linux-specific instructions. However, there is a notable instance where PowerShell is referenced as the default tool for copying files to the VM (using scp), and the instructions assume the user is running PowerShell on their computer. There are no explicit Linux desktop or cross-platform alternatives mentioned for this step, and the only desktop-side example is Windows-centric. No Windows-only tools or patterns dominate, but the assumption of PowerShell as the user's shell introduces a subtle Windows-first bias.
Recommendations:
  • Provide explicit cross-platform instructions for file transfer (e.g., mention using scp from Linux/macOS terminal, or alternatives like WinSCP for Windows).
  • Avoid assuming PowerShell as the default shell; instead, offer both Windows (PowerShell/CMD) and Linux/macOS (terminal/bash) command examples where relevant.
  • Where desktop-side actions are required, clarify that the steps apply to all platforms, or provide platform-specific alternatives.
  • Consider including a note or table summarizing equivalent commands/tools for Windows, Linux, and macOS users.

Page-Level Analysis

Powershell Heavy Windows First Missing Linux Example
Summary:
The documentation page demonstrates a Windows bias by providing detailed PowerShell examples for obtaining authorization tokens, while omitting equivalent Linux or cross-platform scripting examples (e.g., Bash, curl, Python). The PowerShell MSAL example is given more prominence and detail than the Azure CLI example, and there are no Linux-native command-line or scripting alternatives shown. This may hinder Linux users or those working in cross-platform environments.
Recommendations:
  • Add equivalent Linux/Bash/curl examples for obtaining OAuth tokens, such as using curl with the Microsoft identity platform endpoints.
  • Provide Python or other cross-platform scripting examples using MSAL libraries.
  • Ensure that Azure CLI examples are as detailed as the PowerShell examples, and clarify that Azure CLI is cross-platform.
  • When listing command-line options, present cross-platform tools (e.g., Azure CLI, REST with curl) before or alongside Windows-specific tools like PowerShell.
  • Explicitly mention that the PowerShell examples are primarily for Windows users, and provide guidance for Linux/macOS users.

Page-Level Analysis

Windows Tools Windows First
Summary:
The documentation generally maintains cross-platform parity, especially in the Azure CLI section, which explicitly references Bash and provides guidance for PowerShell users. However, there is a subtle Windows bias in the 'Import using the Device Update APIs' section, where PowerShell modules are mentioned as a sample method, and PowerShell is listed first among supported platforms. Additionally, in the 'Prerequisites' and 'Portal' sections, there is a slight preference for Microsoft Edge (a Windows-centric browser), and Windows-style screenshots are used throughout.
Recommendations:
  • When mentioning PowerShell modules, also highlight equivalent Linux/macOS scripting options or provide Bash/Python script samples for parity.
  • In the API/programmatic section, list cross-platform SDKs and tools before or alongside PowerShell, and clarify that PowerShell is available on Linux/macOS as well as Windows.
  • Where browser support is mentioned, list browsers in alphabetical order or mention Chrome/Firefox/Safari alongside Edge to avoid Windows-first perception.
  • Consider including at least one screenshot or example from a Linux environment (e.g., Azure CLI in a Linux terminal) to visually reinforce cross-platform support.
  • Explicitly state that all CLI and API methods are supported equally on Linux, macOS, and Windows.

Page-Level Analysis

Windows Tools Windows First
Summary:
The documentation references the Windows Update platform as the foundation for Device Update, highlighting its reliability and global scale. This mention appears before any Linux-specific update frameworks or tools are discussed. While the document does mention Linux support, Yocto images, and open-source agent extensibility, it does not provide Linux-first or Linux-equal examples, nor does it mention Linux update tools (e.g., apt, rpm, swupd) as foundational. There are no explicit PowerShell or Windows command examples, but the underlying bias is present in the framing and tool references.
Recommendations:
  • Acknowledge and briefly describe Linux-native update mechanisms (e.g., apt, rpm, swupd) and how Device Update integrates with or differs from them.
  • Balance the mention of Windows Update platform by also referencing established Linux update frameworks or open-source OTA solutions.
  • Provide explicit Linux command-line examples or references where relevant, especially in sections discussing agent integration and update workflows.
  • Ensure that Linux and Windows are presented with parity in foundational technology references, not just in agent support.
  • Consider adding a section or callout highlighting Linux-first workflows or best practices for Device Update integration.