IoT
80
Total Pages
73
Linux-Friendly Pages
7
Pages with Bias
8.8%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
14 issues found
Showing 1-14 of 14 flagged pages
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 notably Windows-centric: prerequisites require Windows 10/11, all setup and build scripts are provided as .bat files (Windows batch), and tool usage instructions reference Windows-specific utilities (e.g., Termite, Windows Device Manager, File Explorer). There are no Linux/macOS equivalents or instructions for critical steps such as toolchain setup, flashing, or serial monitoring. This creates significant friction for non-Windows users.
Recommendations
- Add explicit support and instructions for Linux/macOS, including prerequisites and supported OS versions.
- Provide shell script equivalents (e.g., get-toolchain.sh, rebuild.sh) for setup and build steps.
- List and describe cross-platform serial monitoring tools (e.g., minicom, screen, picocom) and how to use them.
- Explain how to identify serial ports on Linux/macOS (e.g., /dev/ttyUSB*), and provide troubleshooting tips.
- Avoid referencing Windows tools (File Explorer, Device Manager) without Linux/macOS alternatives.
- Reorder instructions to present cross-platform options first, or in parallel, rather than Windows-only steps.
Create Pull Request
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 Windows bias by specifying Windows 10/11 as a prerequisite, referencing Windows-specific tools and workflows (e.g., Device Manager, ESP-IDF CMD via Start Menu), and providing examples and instructions only for Windows environments. There are no instructions or examples for Linux or macOS users, and Linux/macOS equivalents for steps like finding the serial port or launching the ESP-IDF environment are missing.
Recommendations
- Add explicit instructions and examples for Linux and macOS users, including prerequisites and tool installation steps.
- Provide alternative methods for finding the serial port on Linux (e.g., using 'ls /dev/ttyUSB*' or 'dmesg') and macOS.
- Describe how to launch the ESP-IDF environment on Linux/macOS (e.g., using terminal and source scripts).
- Use cross-platform paths in examples, or provide both Windows and Linux/macOS path formats.
- Clarify that Azure CLI and IoT Explorer are cross-platform, and provide installation links for all OSes.
- Reorder or parallelize instructions so that Windows and Linux/macOS steps are presented together, or in separate clearly labeled sections.
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
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a notable Windows bias. It explicitly lists Windows 10/11 as a prerequisite, uses Windows batch scripts (.bat) for tool installation and building, references Windows-specific tools (Termite, File Explorer, Device Manager), and provides instructions and screenshots tailored to Windows environments. There are no Linux/macOS equivalents or instructions for key steps such as toolchain setup, serial monitoring, or device flashing, making it difficult for non-Windows users to follow the tutorial.
Recommendations
- Add Linux/macOS as supported platforms in prerequisites and throughout the guide.
- Provide alternative instructions for running setup scripts (e.g., shell scripts like get-toolchain.sh) and building the image on Linux/macOS.
- Suggest cross-platform serial monitoring tools (e.g., minicom, screen, PuTTY) and provide setup instructions for these platforms.
- Replace or supplement File Explorer/Device Manager steps with platform-agnostic or Linux/macOS-specific instructions (e.g., using lsblk, dmesg, or Finder).
- Include troubleshooting steps and driver installation guidance for Linux/macOS.
- Ensure all screenshots and examples have Linux/macOS equivalents.
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 demonstrates a notable Windows bias. The prerequisites require a Windows 10/11 PC, 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 alternatives provided for critical steps such as toolchain installation, flashing, or serial monitoring. The use of Windows tools is assumed throughout, and Linux users are left without guidance for completing the tutorial.
Recommendations
- Add explicit support for Linux/macOS in prerequisites, or clarify platform limitations.
- Provide Linux/macOS equivalents for setup scripts (e.g., shell scripts like get-toolchain.sh, rebuild.sh).
- Include instructions for flashing the device on Linux/macOS (e.g., using dd, cp, or platform-specific tools).
- Suggest cross-platform serial monitoring tools (e.g., minicom, screen, PuTTY) and provide configuration steps.
- Replace or supplement File Explorer/Device Manager steps with cross-platform alternatives (e.g., using lsusb, dmesg, or file managers on Linux/macOS).
- Clearly indicate which steps are Windows-only and offer workarounds or alternatives for other platforms.
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 is heavily oriented towards Windows, with prerequisites specifying Windows 10/11, instructions referencing Windows-specific tools (such as Device Manager), and examples using Windows paths and commands. There are no Linux/macOS equivalents or instructions provided for key steps such as enabling long paths, launching the ESP-IDF environment, or identifying the serial port. This creates friction for Linux/macOS users attempting to follow the tutorial.
Recommendations
- Add explicit Linux/macOS prerequisites and instructions alongside Windows.
- Provide alternative steps for launching the ESP-IDF environment on Linux/macOS (e.g., using terminal and source scripts).
- Include instructions for identifying the serial port on Linux/macOS (e.g., using 'ls /dev/tty*' or 'dmesg').
- Show example build and flash commands with Linux/macOS-style paths (e.g., '/home/user/espbuild').
- Mention any differences in tool installation or usage for Linux/macOS (e.g., using package managers or shell scripts).
- Ensure all critical steps (cloning, building, flashing, monitoring) have Linux/macOS equivalents.
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
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page exhibits a notable Windows bias. It explicitly lists Windows 10/11 as a prerequisite, references Windows-specific tools (Termite, batch scripts), and provides instructions using Windows paths and utilities (File Explorer, CMD, PowerShell). There is no mention of Linux or macOS alternatives for key steps such as running setup scripts, flashing the device, or monitoring serial output. Linux/macOS users are left without guidance for completing the tutorial.
Recommendations
- Add explicit support and instructions for Linux/macOS users in the prerequisites section.
- Provide alternative setup scripts (e.g., shell scripts) for non-Windows platforms.
- List cross-platform serial monitoring tools (e.g., minicom, screen, PuTTY) alongside Termite.
- Include Linux/macOS command-line examples and file paths where relevant.
- Clarify whether the STM DevKit flashing process works on Linux/macOS and provide instructions if so.
- Avoid using Windows-centric terminology (e.g., File Explorer, CMD) exclusively; mention Finder/Terminal for macOS and file managers/terminals for Linux.
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation page exhibits 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 a Windows-centric tool, and its prominence may create friction for Linux/macOS users. Additionally, references to 'PowerShell functions for IoT Edge for Linux on Windows' reinforce the Windows-first perspective. However, Azure CLI examples are present and comprehensive, and ARM templates/Bicep are cross-platform, mitigating the overall impact.
Recommendations
- Present Azure CLI examples before PowerShell in all relevant sections, as CLI is cross-platform.
- Explicitly note that Azure CLI works on Linux/macOS and provide installation links.
- Where PowerShell is mentioned, clarify its cross-platform availability or provide Bash equivalents if possible.
- Remove or rephrase references that imply Windows is the default (e.g., 'IoT Edge for Linux on Windows') unless strictly necessary.
- Ensure all links to management actions include both CLI and PowerShell tabs/examples where applicable.
IoT
Implement the Azure industrial IoT reference solution architecture
...s/iot/tutorial-iot-industrial-solution-architecture.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation page exhibits a notable Windows bias. The deployment instructions exclusively use a Windows 11 Enterprise VM, with explicit recommendations for Windows IoT Enterprise in production. All remote access instructions use RDP, and initial setup commands are Windows-centric (e.g., installing WSL from a Windows command prompt). There are no instructions for deploying the solution directly on Linux or macOS hosts, nor are there alternative examples for non-Windows environments. The use of Windows-specific tools and patterns (RDP, Windows command prompt, WSL) is pervasive, and Linux is only mentioned as a subsystem within Windows, not as a first-class deployment target.
Recommendations
- Provide parallel instructions for deploying the solution on native Linux hosts (e.g., Ubuntu, CentOS), including VM creation, remote access (SSH), and simulation setup.
- Offer examples for macOS users where feasible, especially for containerized workloads.
- Document how to run the production line simulation and edge infrastructure directly on Linux VMs, including installation of Docker, K3s, and other dependencies.
- Include Linux-first deployment scripts and clarify any platform-specific requirements or limitations.
- Mention alternatives to RDP for remote access, such as SSH, and provide guidance for non-Windows environments.
- Review all command-line examples to ensure Linux/macOS parity and highlight any differences.
IoT
Implement the Azure industrial IoT reference solution architecture
...s/iot/tutorial-iot-industrial-solution-architecture.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a notable Windows bias. The deployment process creates a Windows 11 Enterprise VM by default, and all instructions for accessing and configuring the simulation environment assume Windows (RDP, Windows command prompt, WSL). There are no instructions or examples for deploying or running the solution natively on Linux or macOS, nor for connecting via SSH or using Linux-native tools. The use of WSL is suggested as a workaround for Linux tooling, but only within a Windows VM context.
Recommendations
- Provide parallel instructions for deploying the simulation and edge infrastructure on Linux VMs, including SSH access and native Linux commands.
- Offer examples for installing and running K3s, Docker containers, and the simulation directly on Linux (Ubuntu, CentOS, etc.), without requiring WSL.
- Include guidance for macOS users where feasible, especially for client-side tasks.
- Clarify which steps are OS-agnostic and which require Windows, and offer alternatives where possible.
- Consider offering an ARM template or deployment script that supports both Windows and Linux VM targets.
IoT
Introduction to Azure IoT device development
...b/main/articles/iot/concepts-iot-device-development.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Windows First
Summary
The documentation lists Windows-specific tools (Azure PowerShell) alongside cross-platform options, and includes PowerShell as a primary interface for IoT Hub management. The order of tools in the table places Windows-centric tools (PowerShell) before Linux-native equivalents (CLI), and does not provide explicit Linux/macOS usage examples or highlight Linux-specific workflows. There is no mention of Linux package managers, shell scripts, or Linux/macOS-specific setup, which may leave Linux users with less guidance.
Recommendations
- Add explicit Linux/macOS examples and workflows, such as bash shell commands and package installation instructions.
- Clarify which tools are cross-platform and which are Windows-only (e.g., Azure PowerShell).
- Reorder tool listings to place cross-platform options (Azure CLI, VS Code) before Windows-specific tools.
- Include references to Linux-native tools and patterns, such as shell scripting and package managers.
- Provide links to Linux/macOS-specific documentation or troubleshooting guides.
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation page exhibits a moderate Windows bias, especially in the CLI section for cloud-based solutions, where PowerShell is presented before Azure CLI and receives more detailed example coverage. Windows-specific tools (PowerShell, references to 'IoT Edge for Linux on Windows') are highlighted, and PowerShell examples are sometimes given before or in greater detail than their Linux-friendly Azure CLI counterparts. However, Azure CLI is also well-represented, and most management options are cross-platform.
Recommendations
- Present Azure CLI examples before PowerShell in CLI sections, as CLI is natively cross-platform.
- Ensure all PowerShell examples have equivalent Azure CLI examples and links, especially for cloud-based management tasks.
- Avoid referencing Windows-specific tools (e.g., 'IoT Edge for Linux on Windows') without clarifying Linux-native alternatives.
- Add explicit notes about platform compatibility for each tool and example.
- Consider adding bash or Linux shell script examples where automation is discussed.
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation mentions PowerShell as an alternative management tool alongside Azure CLI and REST API, and lists it before REST API. While Azure CLI is cross-platform, PowerShell is traditionally associated with Windows, and its mention may signal a Windows-centric approach. No explicit Linux/macOS examples or tools are highlighted, and the order of listing puts Windows tools before Linux-native or cross-platform alternatives.
Recommendations
- Explicitly state that Azure CLI is cross-platform and provide links or examples for Linux/macOS usage.
- Include Linux/macOS-specific instructions or examples where relevant, especially for SDK installation and usage.
- When listing management tools, alternate the order or clarify platform compatibility (e.g., 'Azure CLI (cross-platform), PowerShell (Windows/macOS/Linux), REST API').
- Add a note or section highlighting parity and support for Linux/macOS environments.
IoT
Introduction to Azure IoT device development
...b/main/articles/iot/concepts-iot-device-development.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation lists Windows-specific tools (PowerShell) alongside cross-platform options, and presents Windows tools (PowerShell) before Linux/macOS equivalents (CLI) in the 'Tools to connect and manage devices' section. However, Linux is mentioned as a supported OS for general device development, and most tools (Azure CLI, VS Code, REST APIs) are cross-platform. No examples or instructions are given that are Windows-only, and Linux users are not blocked from completing any tasks.
Recommendations
- Explicitly mention platform compatibility for each tool in the table (e.g., Azure CLI: Windows, Linux, macOS; PowerShell: Windows, Linux, macOS).
- Present cross-platform tools (Azure CLI) before Windows-specific tools (PowerShell) in lists and tables.
- Add Linux/macOS-specific examples or notes where relevant, especially for command-line tools.
- Clarify that PowerShell Core is available on Linux/macOS, if relevant.
- Consider including links to Linux/macOS setup guides for CLI and other tools.
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation mentions both Azure CLI and PowerShell as alternatives to the management SDKs, but lists PowerShell before REST API and does not explicitly mention Linux/macOS equivalents or parity. There are no explicit Linux/macOS examples or tool recommendations, and PowerShell (a Windows-centric tool) is referenced without clarifying cross-platform support.
Recommendations
- Explicitly mention that Azure CLI is cross-platform and suitable for Linux/macOS users.
- List Azure CLI before PowerShell when suggesting alternatives, as CLI is more universally available.
- Add examples or links for using management SDKs and tools on Linux/macOS.
- Clarify PowerShell's cross-platform availability if referenced, or provide bash/shell alternatives.
- Ensure that referenced guides and included content cover Linux/macOS usage where relevant.