IoT Hub Device Update

55
Total Pages
45
Linux-Friendly Pages
10
Pages with Bias
18.2%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

56 issues found
Showing 26-50 of 56 flagged pages
IoT Hub Device Update Monitoring Device Update for IoT Hub ...iot-hub-device-update/monitor-device-update-iot-hub.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation references Azure portal, CLI, and PowerShell for creating diagnostic settings, but does not provide explicit Linux-specific examples or mention Linux tools. The ordering of examples (portal, CLI, PowerShell) is typical, but PowerShell is a Windows-centric tool, and there is no mention of Bash, shell scripts, or Linux command-line patterns. There are no examples or guidance tailored for Linux users.
Recommendations
  • Include explicit Bash or shell script examples for Linux users when describing CLI operations.
  • Mention cross-platform compatibility of Azure CLI and provide sample commands for both Windows (PowerShell) and Linux (Bash).
  • Clarify that Azure CLI works on Linux, macOS, and Windows, and provide links to installation instructions for each platform.
  • Avoid listing PowerShell before Linux alternatives unless there is a specific reason; consider presenting CLI/Bash examples first or side-by-side.
  • Add a section or note for Linux users highlighting relevant tools and patterns for monitoring and log analysis.
GitHub Create Pull Request
IoT Hub Device Update Azure Device Update for IoT Hub using a Raspberry Pi image ...es/iot-hub-device-update/device-update-raspberry-pi.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation is generally Linux-focused, given the use of a Raspberry Pi and Yocto image, and most command-line instructions use Linux tools (bmaptool, nano, systemctl, etc.). However, there is evidence of Windows bias in the SSH instructions, which specifically direct users to open a PowerShell window for SSH access, rather than mentioning a Linux or cross-platform terminal. Additionally, Azure portal instructions and screenshots are presented in a way that assumes a Windows-centric workflow, with no mention of Linux desktop alternatives or Azure CLI usage.
Recommendations
  • When providing SSH instructions, mention that SSH can be run from any terminal (Linux, macOS, Windows PowerShell, Windows Terminal, etc.), not just PowerShell.
  • Include Azure CLI commands as alternatives to portal-based steps for device registration, tagging, and update deployment, to support Linux users and automation.
  • Where screenshots or UI instructions are given, clarify that the Azure portal is web-based and accessible from any OS, or provide CLI alternatives.
  • Avoid language that implies Windows is the default environment (e.g., 'in a PowerShell window'); use neutral phrasing like 'in your terminal'.
GitHub Create Pull Request
IoT Hub Device Update Deploy an update by using Azure Device Update for IoT Hub | Microsoft Docs ...b/main/articles/iot-hub-device-update/deploy-update.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation demonstrates a mild Windows bias. It references PowerShell specifically in the CLI section, explaining line continuation differences between Bash and PowerShell, and provides guidance for PowerShell users. The Azure Cloud Shell is mentioned, which supports Bash and PowerShell, but the documentation's tips and examples are Bash-centric with only a brief note for PowerShell users. There are no explicit Linux-specific examples, nor are Linux tools or patterns highlighted. The documentation does not mention Linux distributions, shell environments, or provide parity for Linux-specific usage scenarios.
Recommendations
  • Add explicit Linux shell examples (e.g., zsh, sh) and clarify compatibility.
  • Include notes about running Azure CLI commands on popular Linux distributions and any prerequisites or differences.
  • Provide examples for both Bash and PowerShell side-by-side, rather than referencing PowerShell only in a tip.
  • Mention Linux package managers (apt, yum) when discussing Azure CLI installation.
  • Clarify that Azure Cloud Shell supports both Bash and PowerShell, and highlight Linux usage where relevant.
GitHub Create Pull Request
IoT Hub Device Update Deploy an update by using Azure Device Update for IoT Hub | Microsoft Docs ...b/main/articles/iot-hub-device-update/deploy-update.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation demonstrates mild Windows bias by referencing PowerShell-specific syntax and providing guidance for PowerShell users before Linux users. The tip about line continuation syntax explicitly addresses PowerShell and Bash, but gives PowerShell instructions second. The Azure CLI examples are Bash-oriented, but the documentation does not provide direct PowerShell examples or Linux-specific troubleshooting. The Azure Cloud Shell is mentioned, which is cross-platform, but the overall tone and examples lean slightly toward Windows environments.
Recommendations
  • Provide explicit PowerShell command examples alongside Bash examples, or clarify that Azure CLI works equally on Windows, macOS, and Linux.
  • Include troubleshooting steps or notes for common Linux shell environments (e.g., zsh, fish) if there are differences.
  • Mention that Azure CLI is available and supported on Linux and macOS, not just Windows.
  • Add a note about installing Azure CLI on Linux distributions, with a link to Linux-specific install instructions.
  • Ensure that any references to line continuation or shell syntax are equally detailed for both PowerShell and Bash, and consider listing Linux/Bash instructions first if parity is desired.
GitHub Create Pull Request
IoT Hub Device Update Prepare an update to import into Azure Device Update for IoT Hub | Microsoft Docs ...b/main/articles/iot-hub-device-update/create-update.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page demonstrates mild Windows bias by explicitly referencing PowerShell syntax and providing tips for PowerShell users before Linux users. While the main examples use Bash and Azure CLI, there is a notable focus on PowerShell-specific line continuation and escaping, with no equivalent Linux-specific troubleshooting or tips. No Linux-specific tools or patterns are mentioned, and the documentation assumes Bash is the default but spends extra effort accommodating Windows/PowerShell users.
Recommendations
  • Add Linux-specific troubleshooting tips, such as handling file paths, permissions, or escaping in Bash.
  • Provide explicit examples for both Bash and PowerShell, clearly labeling each, rather than only referencing PowerShell in tips.
  • Mention common Linux tools (e.g., nano, vim) for editing JSON manifests, alongside any Windows equivalents.
  • Include a note about running Azure CLI on Linux distributions and any potential differences in behavior or prerequisites.
  • Ensure parity in guidance for both platforms, such as environment setup, command syntax, and error handling.
GitHub Create Pull Request
IoT Hub Device Update Azure Device Update for IoT Hub using a Raspberry Pi image ...es/iot-hub-device-update/device-update-raspberry-pi.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation is generally Linux-focused, as it centers on updating a Raspberry Pi with a Yocto Linux image. However, there is evidence of Windows bias in the instructions for SSH access to the Raspberry Pi, which specifically mention using a PowerShell window. This may imply Windows as the default environment for users, despite the rest of the workflow being Linux-native. No explicit Linux alternatives (e.g., Linux/macOS terminal) are provided for this step, and there is no mention of Linux tools or patterns before Windows equivalents, as the rest of the tutorial is Linux-centric.
Recommendations
  • When describing SSH access, mention that users can use any terminal (Linux, macOS, Windows PowerShell, or Windows Terminal) and provide examples for each.
  • Avoid specifying 'PowerShell window' unless there is a Windows-specific command or behavior; use 'terminal' or 'command prompt' generically.
  • If screenshots or instructions are platform-specific, provide parity for Linux/macOS users.
  • Review other steps for subtle Windows-first language and ensure Linux parity in all instructions.
GitHub Create Pull Request
IoT Hub Device Update https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-hub-device-update/device-update-raspberry-pi.md ...es/iot-hub-device-update/device-update-raspberry-pi.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation is generally Linux-focused, as it describes updating a Raspberry Pi running Yocto Linux. However, there is evidence of Windows bias: the SSH example instructs users to connect 'using the following command in a PowerShell window', which assumes the user is on Windows and using PowerShell. No equivalent instructions or mention are given for Linux or macOS users, nor is there guidance for using a standard terminal or alternative SSH clients. This places Windows tooling and patterns before Linux equivalents in at least one instance.
Recommendations
  • Provide SSH instructions for Linux and macOS users, e.g., 'Open a terminal and run the following command', not just PowerShell.
  • Avoid referencing Windows-specific tools or shells unless necessary, and always provide cross-platform alternatives.
  • Where screenshots or UI instructions are given, clarify if steps differ for non-Windows users.
  • Review other command-line instructions to ensure they are platform-neutral or include platform-specific notes as needed.
GitHub Create Pull Request
IoT Hub Device Update https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-hub-device-update/deploy-update.md ...b/main/articles/iot-hub-device-update/deploy-update.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page demonstrates a mild Windows bias. While it provides Azure CLI examples suitable for Bash (Linux/macOS), it references PowerShell syntax and Windows-specific line continuation patterns before mentioning Linux equivalents. The tip about line continuation syntax prioritizes PowerShell, and the Azure Cloud Shell is presented as a cross-platform solution but is closely tied to the Azure Portal, which is most commonly used on Windows. There are no explicit Linux-only examples or references to Linux-specific tools, and no mention of running CLI commands on native Linux terminals outside of Cloud Shell.
Recommendations
  • Add explicit instructions and examples for running Azure CLI commands on native Linux and macOS terminals, including installation steps and environment setup.
  • When discussing line continuation, mention Bash/Linux syntax first, then PowerShell, or present both equally.
  • Include screenshots or references to Linux/macOS environments where appropriate, not just Azure Portal or Cloud Shell.
  • Clarify that Azure CLI is fully supported on Linux and macOS, and provide troubleshooting tips for those platforms.
  • If any platform-specific issues exist, document them and provide workarounds for Linux/macOS users.
GitHub Create Pull Request
IoT Hub Device Update https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-hub-device-update/deploy-update.md ...b/main/articles/iot-hub-device-update/deploy-update.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation exhibits mild Windows bias by referencing PowerShell as an alternative to Bash for Azure CLI commands and providing syntax conversion tips for PowerShell users. The Azure Cloud Shell and CLI examples are presented in Bash syntax, but the only alternative mentioned is PowerShell, with no reference to Linux-specific shells or environments. There is no explicit mention of Linux tools, nor are Linux-specific issues or patterns discussed.
Recommendations
  • Explicitly mention that Azure CLI commands work in Linux and macOS terminals, not just Bash and PowerShell.
  • Provide examples or notes for running Azure CLI commands in common Linux shells (e.g., zsh, fish) if there are differences.
  • Include troubleshooting tips or environment setup instructions for Linux users, such as package dependencies or permissions.
  • Avoid implying PowerShell is the only alternative to Bash; clarify that Bash is available on Linux, macOS, and Windows (via WSL or Git Bash).
  • Add a note about using Azure CLI natively on Linux and macOS, including installation links for those platforms.
GitHub Create Pull Request
IoT Hub Device Update https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-hub-device-update/device-update-raspberry-pi.md ...es/iot-hub-device-update/device-update-raspberry-pi.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation is generally Linux-focused, as it describes updating a Raspberry Pi with a Yocto Linux image and uses Linux tools (bmaptool, nano, systemctl, etc.). However, there is evidence of Windows bias in the instructions for SSH access, which specifically mention using a PowerShell window, and in the general assumption that users are interacting with the Azure Portal (which is most commonly accessed from Windows). There are no explicit Linux desktop or terminal examples for interacting with the Azure Portal, and the SSH example could be more platform-neutral.
Recommendations
  • Replace 'use PowerShell window' with platform-neutral language such as 'open a terminal or command prompt on your computer.'
  • Provide explicit instructions or notes for Linux and macOS users for SSH access, e.g., 'On Linux or macOS, open a terminal and run the same ssh command.'
  • If relevant, mention cross-platform Azure CLI usage for device registration and management, with examples for both Windows and Linux.
  • Ensure screenshots and instructions for Azure Portal do not assume a Windows environment (e.g., avoid showing Windows-specific UI elements unless necessary).
  • Review other steps for subtle Windows-first assumptions and clarify where steps are platform-agnostic.
GitHub Create Pull Request
IoT Hub Device Update https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-hub-device-update/create-update.md ...b/main/articles/iot-hub-device-update/create-update.md
Medium Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
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.
GitHub Create Pull Request
IoT Hub Device Update https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-hub-device-update/device-update-log-collection.md .../iot-hub-device-update/device-update-log-collection.md
Medium Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
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.
GitHub Create Pull Request
IoT Hub Device Update https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-hub-device-update/understand-device-update.md ...cles/iot-hub-device-update/understand-device-update.md
Medium Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
🔧 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.
GitHub Create Pull Request
IoT Hub Device Update https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-hub-device-update/device-update-log-collection.md .../iot-hub-device-update/device-update-log-collection.md
Medium Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
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.
GitHub Create Pull Request
IoT Hub Device Update https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-hub-device-update/device-update-howto-proxy-updates.md ...hub-device-update/device-update-howto-proxy-updates.md
Medium Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
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.
GitHub Create Pull Request
IoT Hub Device Update https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-hub-device-update/import-schema.md ...b/main/articles/iot-hub-device-update/import-schema.md
Medium Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
🔧 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.
GitHub Create Pull Request
IoT Hub Device Update https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-hub-device-update/create-update.md ...b/main/articles/iot-hub-device-update/create-update.md
Medium Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
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.
GitHub Create Pull Request
IoT Hub Device Update https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-hub-device-update/device-update-howto-proxy-updates.md ...hub-device-update/device-update-howto-proxy-updates.md
Medium Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
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.
GitHub Create Pull Request
IoT Hub Device Update https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-hub-device-update/import-update.md ...b/main/articles/iot-hub-device-update/import-update.md
Medium Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
🔧 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.
GitHub Create Pull Request
IoT Hub Device Update https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-hub-device-update/understand-device-update.md ...cles/iot-hub-device-update/understand-device-update.md
Medium Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
🔧 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.
GitHub Create Pull Request
IoT Hub Device Update https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-hub-device-update/device-update-log-collection.md .../iot-hub-device-update/device-update-log-collection.md
Medium Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
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.
GitHub Create Pull Request
IoT Hub Device Update https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-hub-device-update/create-update.md ...b/main/articles/iot-hub-device-update/create-update.md
Medium Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
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.
GitHub Create Pull Request
IoT Hub Device Update https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-hub-device-update/import-schema.md ...b/main/articles/iot-hub-device-update/import-schema.md
Medium Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
🔧 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.
GitHub Create Pull Request
IoT Hub Device Update Prepare an update to import into Azure Device Update for IoT Hub | Microsoft Docs ...b/main/articles/iot-hub-device-update/create-update.md
Low Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation demonstrates minor Windows bias by referencing PowerShell-specific syntax and escape characters before Linux equivalents, and by providing tips and examples that prioritize Windows/PowerShell considerations. However, the main workflow and examples use Bash/Azure CLI, which is cross-platform.
Recommendations
  • When discussing command syntax differences, mention Bash/Linux conventions first, then PowerShell/Windows as an alternative.
  • Provide explicit Linux/macOS examples for escaping JSON and line continuation, not just PowerShell notes.
  • Clarify that Azure CLI is fully supported on Linux/macOS and provide links to platform-specific installation guides.
  • Add a short section or tip for macOS users if there are any unique considerations.
GitHub Create Pull Request
IoT Hub Device Update Azure Device Update for IoT Hub using a Raspberry Pi image ...es/iot-hub-device-update/device-update-raspberry-pi.md
Low Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation is primarily Linux-focused, given the use of Raspberry Pi and Yocto images. However, there is a minor Windows bias in the SSH instructions, which specifically mention using PowerShell to connect to the Raspberry Pi, rather than providing a cross-platform example or mentioning Linux/macOS terminals. All other command-line instructions use Linux tools and patterns.
Recommendations
  • Update the SSH instructions to mention that SSH can be used from any terminal (Linux, macOS, Windows) and provide examples for each if needed.
  • Avoid referencing PowerShell exclusively; use neutral language such as 'open a terminal' or 'use your preferred SSH client'.
  • If screenshots or further instructions are provided, ensure parity for Linux/macOS users.
GitHub Create Pull Request
← Previous Page 2 of 3 Next →