IoT
41
Total Pages
26
Linux-Friendly Pages
15
Pages with Bias
36.6%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
81 issues found
Showing 1-25 of 81 flagged pages
IoT
Connect an STMicroelectronics B-L475E to Azure IoT Hub
...in/articles/iot/tutorial-devkit-stm-b-l475e-iot-hub.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation is notably Windows-centric: prerequisites specify Windows 10/11, tool installation relies on Windows batch scripts (*.bat), and instructions reference Windows-specific tools (Termite, File Explorer, Device Manager). There are no Linux/macOS equivalents or instructions for key steps such as toolchain setup, flashing, or serial monitoring, making it difficult for non-Windows users to follow the tutorial.
Recommendations
- Add explicit support and instructions for Linux/macOS, including prerequisites and alternative tool recommendations.
- Provide shell script equivalents (e.g., get-toolchain.sh, rebuild.sh) for toolchain setup and image building.
- Suggest cross-platform serial monitoring tools (e.g., minicom, screen, PuTTY) and provide setup instructions for each OS.
- Replace or supplement Windows File Explorer instructions with command-line alternatives (e.g., cp command for copying files on Linux/macOS).
- Include guidance for identifying device mount points and serial ports on Linux/macOS (e.g., using lsblk, dmesg, or /dev/tty*).
- Mention how to install required drivers or dependencies on Linux/macOS, if applicable.
Create Pull Request
IoT
Connect an MXCHIP AZ3166 to Azure IoT Hub
.../articles/iot/tutorial-devkit-mxchip-az3166-iot-hub.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation page exhibits a notable Windows bias. The prerequisites specify a Windows 10/11 PC as required, and all setup/build/flash instructions reference Windows-specific scripts (*.bat files), tools (Termite, File Explorer, Device Manager), and workflows. There are no Linux/macOS equivalents or instructions for critical steps such as toolchain setup, building, flashing, or serial monitoring. Windows tools (Termite, Device Manager, File Explorer) are mentioned exclusively, and Linux alternatives are not discussed. This bias creates significant friction for Linux/macOS users attempting to follow the tutorial.
Recommendations
- Explicitly state support for Linux/macOS in prerequisites if available, or clarify Windows-only support.
- Provide Linux/macOS equivalents for setup scripts (e.g., shell scripts like get-toolchain.sh, rebuild.sh).
- Include instructions for building/flashing using Linux/macOS tools (e.g., using dfu-util, st-flash, or generic USB mass storage copy commands).
- Suggest cross-platform serial monitoring tools (e.g., minicom, screen, PuTTY) instead of or in addition to Termite.
- Replace or supplement references to Windows File Explorer and Device Manager with Linux/macOS alternatives (e.g., lsusb, dmesg, file managers).
- Add example commands and screenshots for Linux/macOS environments.
IoT
Implement the Azure industrial IoT reference solution architecture
...s/iot/tutorial-iot-industrial-solution-architecture.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation exhibits a Windows bias by exclusively deploying the solution on a Windows 11 Enterprise VM, instructing users to connect via RDP and use Windows-specific tools (e.g., Windows Subsystem for Linux, Windows command prompt). Linux/macOS deployment options are not mentioned, and all setup instructions assume a Windows environment, with Linux only present as a subsystem within Windows. No guidance is provided for deploying the simulation or edge infrastructure directly on native Linux hosts or macOS, nor are alternative remote access methods (e.g., SSH) discussed.
Recommendations
- Provide instructions for deploying the production line simulation and edge infrastructure directly on native Linux (e.g., Ubuntu, CentOS) VMs, including container runtime and Kubernetes setup.
- Include alternative remote access instructions (e.g., SSH for Linux/macOS) alongside RDP for Windows.
- Offer parity in examples and commands for Linux/macOS users, such as direct shell commands and environment setup steps.
- Clarify which solution components are cross-platform and which are Windows-only, and suggest alternatives where possible.
- Consider providing ARM templates or deployment scripts that work for both Windows and Linux VM images.
IoT
Connect an ESPRESSIF ESP-32 to Azure IoT Hub tutorial
...ot/tutorial-devkit-espressif-esp32-freertos-iot-hub.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The tutorial exhibits a notable Windows bias: Windows is listed as the only supported OS in prerequisites, all environment setup instructions reference Windows-specific tools (such as 'ESP-IDF 5.0 CMD' and Windows Device Manager), and file paths use Windows conventions. There are no instructions or examples for Linux or macOS users, and key steps (like enabling long paths, finding the COM port, launching the build environment) are described only for Windows. This creates friction for non-Windows users, who must adapt or research alternative steps.
Recommendations
- Explicitly state support for Linux/macOS in prerequisites, or clarify if Windows is required.
- Provide parallel instructions for Linux/macOS users, including how to install ESP-IDF, launch the build environment, and find the serial port (e.g., using 'ls /dev/ttyUSB*' or 'dmesg').
- Use platform-agnostic file paths or provide both Windows and Unix-style examples.
- Include troubleshooting notes for common Linux/macOS issues (e.g., permissions, udev rules for serial devices).
- Reference cross-platform tools and avoid assuming Windows-only workflows.
IoT
Connect an MXCHIP AZ3166 to Azure IoT Hub
.../articles/iot/tutorial-devkit-mxchip-az3166-iot-hub.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation is heavily Windows-centric, requiring Windows 10/11, using Windows batch scripts (*.bat), referencing Windows tools (Termite, Device Manager, File Explorer), and providing no Linux/macOS alternatives or instructions. Linux/macOS users are left without guidance for key steps such as toolchain setup, flashing, and serial monitoring.
Recommendations
- Provide explicit instructions for Linux/macOS users, including supported OS versions.
- Include alternative setup scripts (e.g., get-toolchain.sh) and document their usage.
- Suggest cross-platform serial monitoring tools (e.g., minicom, screen, PuTTY) and provide configuration steps.
- Replace or supplement references to Windows Device Manager and File Explorer with Linux/macOS equivalents (e.g., lsusb, dmesg, file managers).
- Clarify whether the Azure CLI and IoT Explorer steps are cross-platform, and provide installation guidance for non-Windows systems.
- Add troubleshooting notes for Linux/macOS, including driver installation and device recognition.
IoT
Connect an STMicroelectronics B-L475E to Azure IoT Hub
...in/articles/iot/tutorial-devkit-stm-b-l475e-iot-hub.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation exhibits a notable Windows bias: prerequisites require Windows 10/11, setup and build scripts are provided only as Windows batch files (.bat), and Windows tools (Termite, Device Manager, File Explorer) are referenced exclusively. There are no Linux/macOS equivalents or instructions for key steps such as toolchain setup, flashing, or serial monitoring, making it difficult for non-Windows users to follow the tutorial without significant adaptation.
Recommendations
- Provide explicit instructions and scripts for Linux/macOS users, including shell (.sh) versions of setup and build scripts.
- List Linux/macOS as supported platforms in prerequisites, or clarify platform limitations.
- Suggest cross-platform serial monitoring tools (e.g., minicom, screen, PuTTY) alongside Termite.
- Describe how to identify the device and flash the binary using Linux/macOS tools (e.g., using 'lsblk', 'dd', or drag-and-drop in file managers).
- Include instructions for using Azure CLI on Linux/macOS, and clarify that Cloud Shell is platform-agnostic.
- Avoid referencing Windows-specific tools (File Explorer, Device Manager) without Linux/macOS alternatives.
IoT
Implement the Azure industrial IoT reference solution architecture
...s/iot/tutorial-iot-industrial-solution-architecture.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation exhibits a Windows bias by exclusively deploying the solution on a Windows 11 Enterprise VM, instructing users to use RDP and Windows command prompt, and only mentioning Windows IoT Enterprise as the recommended production OS. Linux deployment options, native Linux VMs, or direct Linux instructions are missing. The use of WSL is presented as a workaround within Windows rather than supporting Linux as a first-class platform. There are no examples or guidance for deploying the solution natively on Linux, nor are Linux tools or patterns discussed.
Recommendations
- Provide instructions for deploying the production line simulation and Edge infrastructure on a native Linux VM (e.g., Ubuntu, CentOS), including setup steps for Docker, K3s, and Kubernetes.
- Offer Linux-first deployment options in the ARM template or deployment scripts, and clarify OS requirements for both Windows and Linux.
- Include examples for connecting via SSH to Linux VMs, and using Linux terminal commands directly, rather than relying on RDP and Windows command prompt.
- Mention Linux equivalents for Windows IoT Enterprise, such as Ubuntu Core or other industrial Linux distributions, and discuss their suitability.
- Ensure all shell scripts and tools are compatible with Linux environments and document any platform-specific differences.
- Add troubleshooting tips for Linux users, such as common issues with Docker, K3s, or networking on Linux.
IoT
Connect an MXCHIP AZ3166 to Azure IoT Hub
.../articles/iot/tutorial-devkit-mxchip-az3166-iot-hub.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation page demonstrates a clear Windows bias. The prerequisites require a Windows 10/11 PC, and all setup and build instructions reference Windows-specific scripts (*.bat files), Windows tools (Termite, Device Manager, File Explorer), and Windows console environments (CMD, PowerShell, Git Bash for Windows). There are no instructions or examples for Linux or macOS users, nor are Linux equivalents for tools or scripts provided. The order and language throughout assume Windows as the default platform.
Recommendations
- Add explicit instructions and tested steps for Linux (and optionally macOS), including prerequisites, tool installation, and usage.
- Provide Linux-compatible setup scripts (e.g., get-toolchain.sh) alongside the Windows .bat files.
- List cross-platform alternatives for Windows-only tools (e.g., suggest minicom, screen, or picocom for serial monitoring instead of Termite).
- Replace references to Windows File Explorer and Device Manager with platform-neutral or Linux/macOS equivalents (e.g., using the terminal, lsblk, dmesg, etc.).
- Ensure all CLI examples work on Linux and macOS, and note any platform-specific differences.
- Update the prerequisites section to include supported Linux distributions and macOS versions.
- Where screenshots or instructions reference Windows UI, provide Linux/macOS alternatives or clarify platform-specific steps.
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias, particularly in the CLI section for cloud-based solutions, where PowerShell is presented before Azure CLI and receives more detailed coverage. PowerShell examples and references are prominent, and there is mention of 'PowerShell functions for IoT Edge for Linux on Windows,' which is a Windows-specific tool. While Azure CLI is covered and suitable for Linux, the ordering and emphasis favor Windows/PowerShell tools, and Linux-specific patterns or shell examples are not highlighted.
Recommendations
- Present Azure CLI examples before PowerShell in all sections, especially for cloud-based solutions, to reflect its cross-platform nature.
- Ensure parity in example depth and links between PowerShell and Azure CLI, including explicit Linux shell usage where relevant.
- Add references or examples for Linux-native tools or workflows (e.g., bash scripts, systemd integration for IoT Edge).
- Remove or clarify Windows-specific tool mentions (e.g., 'IoT Edge for Linux on Windows') to avoid confusion and ensure Linux users are not overlooked.
- Consider a dedicated section or callout for Linux users, summarizing recommended management approaches and tools.
IoT
Connect an STMicroelectronics B-L475E to Azure IoT Hub
...in/articles/iot/tutorial-devkit-stm-b-l475e-iot-hub.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation exhibits a strong Windows bias: Windows is the only OS listed as a prerequisite, all setup and build instructions reference Windows-specific tools and batch scripts (.bat), and Windows utilities (File Explorer, Device Manager) are used for critical steps. There are no Linux or macOS equivalents or instructions, and the serial monitor tool (Termite) is Windows-only. The guidance for running Azure CLI locally does not mention Linux or macOS, and PowerShell/CMD are referenced as consoles, with no mention of Bash or other shells outside Azure Cloud Shell.
Recommendations
- Add Linux and macOS as supported platforms in prerequisites, or clarify Windows-only support if intentional.
- Provide instructions for running setup and build scripts on Linux/macOS (e.g., .sh scripts, CMake commands).
- List Linux/macOS alternatives for Windows-only tools, such as using minicom, screen, or PuTTY for serial monitoring instead of Termite.
- Include steps for identifying serial ports on Linux/macOS (e.g., using dmesg, ls /dev/tty*, or system tools).
- Reference Bash and other shells for local Azure CLI usage, not just Windows CMD/PowerShell.
- Ensure all critical steps (cloning, building, flashing, monitoring) have cross-platform instructions and examples.
IoT
Connect an ESPRESSIF ESP-32 to Azure IoT Hub tutorial
...ot/tutorial-devkit-espressif-esp32-freertos-iot-hub.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a strong Windows bias. It explicitly lists Windows 10/11 as a prerequisite, provides instructions and screenshots for Windows-specific tools (such as Device Manager), and references launching the ESP-IDF environment via Windows Start Menu and the ESP-IDF CMD prompt. There are no instructions or examples for Linux or macOS users, nor are alternative commands or troubleshooting steps provided for those platforms.
Recommendations
- Add explicit support and instructions for Linux and macOS users, including prerequisites, installation steps, and environment setup.
- Provide alternative commands for launching the ESP-IDF environment on Linux/macOS (e.g., using terminal and source scripts).
- Include instructions for identifying serial ports on Linux (e.g., using 'ls /dev/tty*' or 'dmesg | grep tty') and macOS.
- Replace or supplement Windows Device Manager screenshots with equivalent steps for Linux (e.g., using 'lsusb' or 'dmesg') and macOS.
- Avoid using only Windows-specific paths (e.g., 'C:\espbuild'); provide examples for Linux/macOS file paths.
- Clarify that Azure CLI and IoT Explorer are cross-platform, and provide installation links or notes for Linux/macOS.
- Review troubleshooting and debugging sections to ensure parity for Linux/macOS users, including references to platform-agnostic tools.
IoT
Introduction to Azure IoT device development
...b/main/articles/iot/concepts-iot-device-development.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation page demonstrates a mild Windows bias in its presentation of tools and examples. In the 'Tools to connect and manage devices' section, Windows-centric tools such as Azure PowerShell are listed alongside cross-platform options, and PowerShell is mentioned before Linux-specific alternatives. There is no explicit mention of Linux-specific tools or shell examples (e.g., Bash), and Windows tools (PowerShell, Azure portal) are presented as primary options. The documentation does mention Linux as a supported OS for general device development, but does not provide Linux-first or Linux-specific guidance or examples.
Recommendations
- Add explicit Linux shell (Bash) examples for common tasks, such as creating and managing IoT hubs.
- Include Linux-specific tools or workflows (e.g., reference to using Azure CLI on Linux, or using native Linux utilities for device management).
- Balance the order of tool presentation by listing cross-platform tools (Azure CLI, VS Code) before Windows-specific tools (PowerShell).
- Mention package managers and installation instructions for Linux environments where relevant.
- Provide links to Linux-focused tutorials or documentation, if available.
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias, particularly in the CLI section for cloud-based solutions, where PowerShell examples and links are presented before Azure CLI equivalents. PowerShell is highlighted as a primary automation tool for cloud scenarios, and references to Windows-specific modules and functions (e.g., 'PowerShell functions for IoT Edge for Linux on Windows') are included. While Azure CLI is covered, its placement after PowerShell and the emphasis on PowerShell modules suggest a preference for Windows tooling and patterns.
Recommendations
- Present Azure CLI and PowerShell examples side-by-side or in parallel tabs, rather than listing PowerShell first for cloud scenarios.
- Ensure that all actions demonstrated with PowerShell have equivalent Azure CLI examples and links, especially for cloud-based management tasks.
- Avoid referencing Windows-specific modules (e.g., 'PowerShell functions for IoT Edge for Linux on Windows') without also mentioning or linking to Linux-native alternatives.
- Explicitly state cross-platform support for all CLI tools and clarify when examples are platform-agnostic.
- Consider adding a section or note highlighting best practices for Linux users and referencing Linux-native automation tools or shell scripting where appropriate.
IoT
Introduction to Azure IoT device development
...b/main/articles/iot/concepts-iot-device-development.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation page demonstrates a mild Windows bias in its presentation of development tools. In the 'Tools to connect and manage devices' section, Windows-centric tools such as Azure PowerShell are listed alongside cross-platform options, and PowerShell is mentioned before Linux-specific alternatives. While Azure CLI and VS Code are cross-platform, there are no explicit Linux-specific examples or mentions of Linux-native tools (e.g., bash scripts, Linux package managers, or Linux desktop environments). The documentation also references Windows as a general-purpose OS before Linux in several places, and does not provide parity in examples or instructions for Linux users.
Recommendations
- Add explicit Linux examples and instructions, such as using bash or Linux terminal commands for device management.
- Mention Linux as a general-purpose OS before or alongside Windows in relevant sections to avoid 'windows_first' ordering.
- Include references to Linux-native tools (e.g., GNOME Terminal, KDE, or Linux package managers) where appropriate.
- Provide links to Linux-specific tutorials or documentation for Azure IoT development.
- Clarify that Azure CLI and VS Code are cross-platform, and provide installation instructions for Linux.
- Consider adding a table column or notes indicating OS compatibility for each tool listed.
IoT
Connect an MXCHIP AZ3166 to Azure IoT Hub
.../articles/iot/tutorial-devkit-mxchip-az3166-iot-hub.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation page exhibits a strong Windows bias. The prerequisites explicitly require Windows 10 or 11, and all setup and build instructions reference Windows-specific tools and scripts (e.g., .bat files, File Explorer, Termite, Windows Device Manager). There are no instructions or examples for Linux or macOS users, nor are equivalent Linux tools or workflows mentioned. The use of Windows CMD, PowerShell, and Git Bash for Windows is suggested, but no Linux terminal or shell alternatives are provided.
Recommendations
- Add explicit instructions and examples for Linux (and optionally macOS) users, including supported OS versions.
- Provide equivalent shell scripts (e.g., get-toolchain.sh, rebuild.sh) for Linux/macOS alongside the Windows .bat files.
- List and describe Linux-compatible serial terminal tools (e.g., minicom, screen, picocom) as alternatives to Termite.
- Replace or supplement File Explorer steps with Linux file manager or command-line equivalents.
- Describe how to identify serial ports on Linux (e.g., using dmesg, ls /dev/tty*, or lsusb) instead of relying solely on Windows Device Manager.
- Clarify whether the Azure CLI and IoT Explorer steps are cross-platform, and provide installation guidance for Linux/macOS.
- Add troubleshooting notes for Linux-specific issues, such as udev rules for USB devices or permissions for serial ports.
IoT
Implement the Azure industrial IoT reference solution architecture
...s/iot/tutorial-iot-industrial-solution-architecture.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Powershell Heavy
Summary
The documentation demonstrates a clear Windows bias. The deployment instructions exclusively use a Windows 11 Enterprise VM, with no mention of Linux alternatives for hosting the simulation or edge infrastructure. Users are instructed to connect via RDP and use Windows-specific tools (Windows command prompt, WSL), and the base OS recommendation is Windows IoT Enterprise. There are no examples or guidance for deploying the solution natively on Linux VMs or using Linux tools directly. The workflow assumes familiarity with Windows environments and only introduces Linux tooling (WSL, bash) as a subsystem within Windows, not as a first-class platform.
Recommendations
- Provide parallel instructions for deploying the production line simulation and edge infrastructure on a Linux VM (e.g., Ubuntu, CentOS), including native installation steps for Docker, K3s, and other required components.
- Offer SSH-based access instructions for Linux VMs, rather than only RDP for Windows.
- Include Linux-native command-line examples and troubleshooting tips, not just WSL within Windows.
- Mention Linux as a supported base OS for the simulation and edge workloads, and discuss any differences or considerations.
- Ensure that all scripts and tools used in the tutorial are cross-platform, or provide Linux-specific alternatives where necessary.
- Highlight open-source and cross-platform tools before or alongside Windows-specific ones, to avoid the impression that Windows is required.
IoT
Connect an ESPRESSIF ESP-32 to Azure IoT Hub tutorial
...ot/tutorial-devkit-espressif-esp32-freertos-iot-hub.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page exhibits a strong Windows bias. It assumes the user is running Windows 10 or 11, references Windows-specific tools (such as Device Manager), and provides instructions and screenshots exclusively for Windows. There are no examples or guidance for Linux or macOS users, nor are alternative tools or commands mentioned for those platforms.
Recommendations
- Add explicit instructions for Linux and macOS users, including prerequisites and environment setup steps.
- Provide equivalent commands and tooling for Linux (e.g., using /dev/ttyUSB* for serial ports, using lsusb or dmesg instead of Device Manager).
- Include screenshots or terminal output examples for Linux/macOS where Windows screenshots are currently shown.
- Clarify that ESP-IDF tools are cross-platform and provide guidance on launching the ESP-IDF environment on Linux/macOS (e.g., using terminal, sourcing export.sh).
- Mention any platform-specific caveats (such as long path issues) for Linux/macOS if applicable, or clarify if they are Windows-only.
- Ensure parity in troubleshooting and debugging sections by referencing Linux/macOS-compatible editors and debuggers.
IoT
Connect an STMicroelectronics B-L475E to Azure IoT Hub
...in/articles/iot/tutorial-devkit-stm-b-l475e-iot-hub.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation exhibits a strong Windows bias. It explicitly requires a Windows 10/11 PC, provides only Windows batch scripts (*.bat) for toolchain setup and build, and references Windows-specific tools (Termite, File Explorer, Device Manager). There are no instructions or examples for Linux or macOS users, nor alternative scripts (e.g., shell scripts) for non-Windows platforms. The guidance for console usage and troubleshooting is also Windows-centric.
Recommendations
- Add explicit support and instructions for Linux and macOS, including prerequisites and compatible tools.
- Provide shell script equivalents (e.g., get-toolchain.sh, rebuild.sh) for setup and build steps.
- List cross-platform serial terminal alternatives to Termite (e.g., minicom, screen, PuTTY) and include setup instructions for each OS.
- Replace or supplement File Explorer and Device Manager steps with platform-agnostic or Linux/macOS-specific alternatives (e.g., using lsblk, dmesg, or /dev/tty* for device identification).
- Clarify which steps are Windows-only and which are cross-platform; reorganize instructions so that Windows, Linux, and macOS users can follow parallel workflows.
- Test and document the full tutorial on Linux and macOS to ensure parity and update troubleshooting sections accordingly.
IoT
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot/tutorial-devkit-mxchip-az3166-iot-hub.md
.../articles/iot/tutorial-devkit-mxchip-az3166-iot-hub.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation page demonstrates a strong Windows bias. It lists Windows 10/11 as the required OS in prerequisites, references only Windows-specific scripts (*.bat files), and recommends Windows tools (Termite, File Explorer, Device Manager). There are no Linux equivalents or instructions for Linux users, and no mention of Linux-compatible serial terminal tools or shell scripts. The order and language consistently prioritize Windows, with Linux support absent.
Recommendations
- Add explicit instructions and examples for Linux users, including supported distributions.
- Provide Linux-compatible setup scripts (e.g., get-toolchain.sh) and document their usage.
- List Linux alternatives for Windows-only tools (e.g., suggest minicom, screen, or picocom instead of Termite).
- Include instructions for flashing the device using Linux file managers or command-line tools.
- Show how to identify serial ports on Linux (e.g., using dmesg, ls /dev/tty*, or udevadm).
- Ensure all Azure CLI examples are tested and documented for Linux shells.
- Avoid assuming Windows-only workflows (e.g., File Explorer, Device Manager) and offer cross-platform alternatives.
IoT
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot/concepts-iot-device-development.md
...b/main/articles/iot/concepts-iot-device-development.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in several ways. Windows is consistently mentioned before Linux when describing general device development platforms. The tools table lists Azure PowerShell as a primary tool, which is Windows-centric, and does not mention Linux-specific tools or provide parity for Linux users (e.g., Bash, shell scripts, or Linux package managers). There are no explicit Linux command examples or references to Linux-native workflows, and PowerShell is given equal prominence to Azure CLI, despite CLI being cross-platform. No Linux-specific troubleshooting or setup guidance is provided.
Recommendations
- Ensure Linux is mentioned alongside Windows, or even first, when discussing general-purpose operating systems.
- Add explicit Linux command-line examples (e.g., Bash) and reference Linux package managers or shell environments where appropriate.
- Clarify that Azure CLI is cross-platform and highlight its use on Linux and macOS.
- Provide links to Linux-specific setup or troubleshooting guides for Azure IoT development.
- Include Linux-native tools (e.g., shell scripts, systemd services) in the tools table and documentation.
- Balance references to PowerShell with equivalent Linux shell commands or scripts.
IoT
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot/iot-overview-solution-management.md
.../main/articles/iot/iot-overview-solution-management.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in several ways: PowerShell is presented as the primary automation tool for cloud-based solutions, often before or in more detail than Azure CLI. Windows-specific tools and terminology (e.g., PowerShell, references to 'IoT Edge for Linux on Windows') are prominent, while Linux-native patterns and examples are less visible or missing. In some sections, PowerShell examples are given without equivalent Bash or Linux shell examples, and Windows tools are mentioned before their Linux counterparts.
Recommendations
- Ensure CLI (Azure CLI) examples are presented before or alongside PowerShell, especially for cloud-based scenarios.
- Add explicit Bash/Linux shell examples where only PowerShell is shown.
- Avoid referring to Windows-specific tools (e.g., PowerShell) as the default or primary automation method; present cross-platform options equally.
- Include references to Linux-native workflows and tools (e.g., Bash scripts, systemd, etc.) where relevant.
- Review and update links and tabs to ensure Linux parity and visibility, such as including 'Linux' tabs in code samples and walkthroughs.
- Clarify that Azure CLI is cross-platform and suitable for both Windows and Linux users.
IoT
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot/tutorial-devkit-espressif-esp32-freertos-iot-hub.md
...ot/tutorial-devkit-espressif-esp32-freertos-iot-hub.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page exhibits a strong Windows bias. It assumes the user is running Windows 10 or 11, references Windows-specific tools (such as Device Manager), and provides instructions and screenshots exclusively for Windows environments. There are no examples or guidance for Linux or macOS users, nor are alternative tools or commands mentioned for those platforms.
Recommendations
- Add explicit instructions and examples for Linux (and optionally macOS) users, including prerequisites and setup steps.
- Provide alternative commands for common Linux shells (bash, zsh) and clarify any differences in paths or permissions.
- Replace or supplement Windows-specific instructions (e.g., Device Manager for COM port detection) with Linux equivalents (e.g., using 'lsusb', 'dmesg', or 'ls /dev/tty*').
- Include screenshots or terminal output examples from Linux environments where relevant.
- Mention cross-platform compatibility of ESP-IDF tools and clarify any platform-specific limitations or requirements.
- Rephrase prerequisites to include Linux and macOS as supported development environments if applicable.
IoT
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot/tutorial-devkit-stm-b-l475e-iot-hub.md
...in/articles/iot/tutorial-devkit-stm-b-l475e-iot-hub.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation page exhibits a strong Windows bias. The prerequisites require a Windows 10 or 11 PC, and all setup and build instructions reference Windows-specific tools and patterns (e.g., .bat batch scripts, File Explorer, Windows Device Manager, Termite serial monitor, and Windows CMD/PowerShell/Git Bash). There are no instructions or examples for Linux or macOS users, nor are Linux equivalents for tools or workflows mentioned. The use of Windows-centric terminology and tools is pervasive throughout the tutorial.
Recommendations
- Add explicit support and instructions for Linux (and optionally macOS) users, including prerequisites for those platforms.
- Provide alternative setup scripts (e.g., .sh shell scripts) and document their usage for non-Windows environments.
- List cross-platform tools for serial monitoring (e.g., minicom, screen, picocom) alongside or instead of Termite.
- Replace or supplement File Explorer instructions with command-line equivalents that work on Linux/macOS.
- Describe how to identify serial ports on Linux (e.g., /dev/ttyACM0) and how to install necessary drivers if applicable.
- Ensure all Azure CLI commands are presented in a way that works on all platforms, and clarify any platform-specific differences.
- Review all screenshots and tool references to ensure Linux users are not excluded or confused.
IoT
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot/tutorial-iot-industrial-solution-architecture.md
...s/iot/tutorial-iot-industrial-solution-architecture.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation exhibits a Windows bias by exclusively deploying the solution on a Windows 11 Enterprise VM, instructing users to use RDP and Windows command prompt, and referencing Windows-specific tools (WSL). There are no instructions or examples for deploying or operating the solution natively on Linux, nor is there guidance for Linux VMs or environments. Linux usage is only introduced via WSL, which itself is a Windows feature, rather than supporting Linux as a first-class platform.
Recommendations
- Provide instructions for deploying the production line simulation and edge infrastructure on native Linux VMs (e.g., Ubuntu, CentOS), including setup steps for Docker, K3s, and Kubernetes.
- Include Linux-native commands for installation and operation, such as SSH access, bash shell usage, and service management.
- Offer parity in example workflows, showing both Windows and Linux deployment paths side-by-side.
- Clarify platform requirements and support for both Windows and Linux, and avoid implying Windows is the default or only supported option.
- Reference cross-platform tools and avoid reliance on Windows-only features (e.g., WSL, RDP) when alternatives exist (e.g., SSH, native Linux shells).
IoT
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot/tutorial-devkit-mxchip-az3166-iot-hub.md
.../articles/iot/tutorial-devkit-mxchip-az3166-iot-hub.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation page demonstrates a strong Windows bias. It explicitly lists Windows 10/11 as a prerequisite, uses Windows-specific batch scripts (*.bat), references Windows tools (Termite, Device Manager, File Explorer), and provides instructions tailored to Windows environments. There are no Linux or macOS equivalents for key steps such as tool installation, flashing, or serial monitoring. Linux alternatives and instructions are missing throughout, making the tutorial inaccessible or confusing for non-Windows users.
Recommendations
- Add Linux and macOS as supported platforms in prerequisites, or clarify platform limitations.
- Provide Linux/macOS equivalents for all steps, including shell scripts (e.g., get-toolchain.sh, rebuild.sh) and instructions for running them.
- Suggest cross-platform or Linux-native serial monitoring tools (e.g., minicom, screen, picocom) alongside Termite.
- Replace or supplement references to Windows Device Manager and File Explorer with Linux/macOS alternatives (e.g., lsusb, dmesg, Nautilus/Finder).
- Ensure all CLI commands and tool usage are demonstrated in both Windows and Linux/macOS environments.
- Include troubleshooting steps for Linux/macOS users, such as permissions for USB devices and driver installation.