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 26-50 of 81 flagged pages
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 demonstrates a moderate Windows bias. Windows and PowerShell are mentioned explicitly and given equal or greater prominence than Linux and cross-platform tools. The tools table lists Azure PowerShell as a primary option, and while Azure CLI (cross-platform) is included, there are no explicit Linux-specific examples, nor is there mention of Linux-native tools or shell commands. Windows is mentioned first in several places, and there is no guidance for Linux users on common patterns or troubleshooting. The documentation does not provide parity in examples or tool recommendations for Linux users.
Recommendations
- Add explicit Linux shell/bash examples and references alongside PowerShell commands.
- Mention Linux-first or cross-platform tools (e.g., Azure CLI, REST APIs) before Windows-specific tools.
- Include troubleshooting or setup notes for Linux environments, especially for device development.
- Clarify that Azure CLI is cross-platform and highlight its use for Linux users.
- Add links to Linux-specific documentation or tutorials where available.
- Consider including a table or section comparing Windows and Linux development workflows for Azure IoT.
Create Pull Request
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
Summary
The documentation page demonstrates a moderate Windows bias, particularly in the CLI section for cloud-based solutions, where PowerShell examples and references are presented before Azure CLI equivalents. PowerShell is highlighted as a primary automation tool for cloud-based IoT management, with dedicated links and reference documentation, while Linux-native tools and patterns (e.g., Bash scripting, Linux shell usage) are not mentioned. The inclusion of 'PowerShell functions for IoT Edge for Linux on Windows' further reinforces a Windows-centric approach. Although Azure CLI examples are present, they are introduced after PowerShell, and there is no explicit mention of Linux-specific workflows or parity.
Recommendations
- Present Azure CLI and PowerShell examples side-by-side or in parallel, rather than listing PowerShell first for cloud-based solutions.
- Explicitly mention Linux compatibility and workflows, such as Bash scripting or Linux shell usage, especially in automation sections.
- Include links to Linux-specific documentation or troubleshooting guides where relevant.
- Avoid referencing Windows-only tools (e.g., PowerShell functions for IoT Edge for Linux on Windows) without providing Linux-native alternatives or context.
- Add a short section or note clarifying that all CLI tools (Azure CLI, Bicep, ARM templates) are cross-platform and provide guidance for 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 explicitly lists Windows 10/11 as a prerequisite, references Windows-specific tools (such as Device Manager), and provides step-by-step instructions using Windows UI elements (Start menu, CMD prompt). There are no instructions or examples for Linux or macOS users, nor any mention of equivalent Linux tools or workflows. All examples and troubleshooting steps assume a Windows environment.
Recommendations
- Add a section for Linux/macOS prerequisites, including supported distributions and required packages.
- Provide instructions for installing ESP-IDF and related tools on Linux/macOS, including terminal commands.
- Replace or supplement Windows-specific steps (e.g., Device Manager for COM port detection) with Linux/macOS equivalents (e.g., using 'lsusb' or 'dmesg' to find serial ports).
- Include notes about path length issues on Linux/macOS if relevant, or clarify when issues are Windows-specific.
- Ensure all CLI commands (git, idf.py, Azure CLI) are shown in a cross-platform manner, with example paths for both Windows and Linux/macOS.
- Mention that Azure IoT Explorer is available on multiple platforms, or provide alternatives if it is Windows-only.
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
Summary
The documentation page demonstrates a Windows bias by specifying Windows 10/11 as a prerequisite, providing only Windows batch scripts (*.bat) for tool installation and build steps, referencing Windows-specific tools (Termite, File Explorer, Device Manager), and omitting Linux equivalents or instructions. There are no examples or guidance for Linux users regarding setup, flashing, or monitoring, despite the cross-platform nature of many embedded development tools.
Recommendations
- Add explicit instructions for Linux users, including required OS packages and dependencies.
- Provide Linux shell script equivalents (e.g., get-toolchain.sh, rebuild.sh) alongside Windows batch files.
- Include instructions for using Linux serial terminal tools (e.g., minicom, screen, picocom) as alternatives to Termite.
- Replace or supplement references to Windows File Explorer and Device Manager with Linux file manager and command-line tools (e.g., lsblk, dmesg, udevadm).
- Clarify that Azure CLI and Git are cross-platform, and provide installation links for Linux.
- Ensure screenshots and examples reflect both Windows and Linux environments where applicable.
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 page demonstrates a Windows bias in several ways: deployment instructions exclusively use a Windows 11 Enterprise VM, with no mention of Linux VM alternatives; connection and setup steps (RDP, Windows command prompt) are Windows-centric; installation of Linux tools (WSL, K3S) is performed within Windows via WSL rather than on native Linux; and references to Windows-specific editions (Windows IoT Enterprise LTSC) are present. There are no examples or guidance for deploying the solution directly on Linux VMs or using Linux-native workflows, and Linux is only introduced as a subsystem within Windows rather than as a first-class platform.
Recommendations
- Provide parallel instructions for deploying the solution on a native Linux VM (e.g., Ubuntu, CentOS), including setup, simulation, and edge infrastructure.
- Include Linux-specific connection methods (SSH, SCP) and command-line usage, rather than only RDP and Windows command prompt.
- Offer guidance for installing and running K3S, Docker, and the production line simulation directly on Linux, without requiring WSL.
- Mention Linux-compatible OS options for production scenarios, such as Ubuntu Server or Red Hat Enterprise Linux, alongside Windows IoT Enterprise.
- Ensure all scripts and automation steps are tested and documented for Linux environments.
- Highlight cross-platform compatibility and any platform-specific considerations or limitations.
IoT
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot/tutorial-use-mqtt.md
...azure-docs/blob/main/articles/iot/tutorial-use-mqtt.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation shows some Windows bias, particularly in the ordering and detail of prerequisites. Windows instructions (Visual Studio, CMake, Mosquitto installer) are listed first and in more detail, while Linux instructions are more concise. The repository cloning example uses Windows command prompt syntax (git clone in a code block labeled 'cmd'), and there is no explicit Linux shell example for this step. The build output locations are described for both platforms, but Windows is mentioned second. There are no PowerShell-specific commands, but the overall structure and tool recommendations (Visual Studio, CMake installer) lean toward Windows development patterns.
Recommendations
- Alternate the order of Windows and Linux instructions or present them side-by-side to avoid always listing Windows first.
- Provide equivalent detail for Linux prerequisites (e.g., mention recommended IDEs or editors, clarify where binaries are located after build).
- Include Linux shell examples for repository cloning and other steps, not just Windows command prompt.
- Where possible, use cross-platform instructions (e.g., 'git clone' in a generic shell block) or show both Windows and Linux command syntax.
- Mention Linux-native tools or workflows (such as using VS Code, Makefiles, or GCC directly) alongside Windows tools like Visual Studio.
- Ensure parity in troubleshooting tips and notes for both platforms.
IoT
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot/howto-iot-industrial-dataspaces.md
...b/main/articles/iot/howto-iot-industrial-dataspaces.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a Windows bias by repeatedly instructing users to use a Windows command prompt and the Windows Subsystem for Linux (WSL) to execute Linux commands. There are no native Linux or macOS instructions, and the workflow assumes a Windows environment. This excludes users on Linux or macOS from following the steps directly, and Windows-specific tools and patterns are mentioned without Linux equivalents.
Recommendations
- Provide native Linux and macOS instructions alongside Windows instructions, especially for command-line steps.
- Avoid assuming the use of WSL; instead, show how to run commands directly in a Linux or macOS terminal.
- When referencing command prompts, clarify which OS is being used and offer alternatives for other platforms.
- If using online tools or Azure Portal steps, ensure that any OS-specific instructions are clearly marked and alternatives are provided.
- Consider restructuring the step order so that no platform is prioritized over another (e.g., 'On Windows, do X. On Linux/macOS, do Y.').
IoT
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot/concepts-using-c-sdk-and-embedded-c-sdk.md
...rticles/iot/concepts-using-c-sdk-and-embedded-c-sdk.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation shows a mild Windows bias by consistently listing Windows before Linux in recommendations and descriptions, and by mentioning Windows-specific tools (e.g., Schannel, Win32 sockets) alongside but before or more prominently than Linux equivalents (e.g., OpenSSL, Berkeley sockets). There are no code examples for either platform, but references to Windows tools and APIs are more explicit. Linux is mentioned, but often after Windows, and there are no Linux-specific tools or patterns highlighted.
Recommendations
- List Linux and Windows in a neutral or alternating order (e.g., 'Linux and Windows' or 'Windows and Linux') to avoid implicit prioritization.
- When mentioning platform-specific tools (e.g., Schannel for Windows, OpenSSL for Linux), ensure both are described with equal detail and prominence.
- Include explicit Linux examples or references to Linux-specific tools (e.g., GnuTLS, epoll) where appropriate.
- Highlight Linux as a first-class supported platform, not just as an alternative to Windows.
- If mentioning Windows-specific APIs (e.g., Win32 sockets), also mention and describe Linux equivalents (e.g., POSIX/Berkeley sockets) in the same context.
- Consider adding sample commands or code snippets for both Windows and Linux environments where relevant.
IoT
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot/howto-connect-on-premises-sap-to-azure.md
...articles/iot/howto-connect-on-premises-sap-to-azure.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Windows environments for the SAP system (e.g., 'Sign in to the SAP Windows virtual machine'), providing only Windows-based installation paths and instructions (such as copying DLLs from 'C:\Program Files'), and mentioning only the SAP Connector for Microsoft .NET (Windows-only). There are no examples or guidance for Linux-based SAP systems or cross-platform alternatives.
Recommendations
- Include parallel instructions for configuring SAP systems running on Linux, including relevant screenshots and SAP GUI steps.
- Mention and provide guidance for Linux-compatible SAP connectors (e.g., SAP Java Connector or other cross-platform options) where applicable.
- When referencing file paths or installation procedures, provide both Windows and Linux equivalents.
- Clarify in prerequisites or relevant sections whether the solution is limited to Windows-based SAP systems, or expand support to Linux-based SAP deployments.
- If certain features (such as the .NET connector) are Windows-only, suggest Linux alternatives or note the limitation explicitly.
IoT
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot/troubleshoot-embedded-device-tutorials.md
...articles/iot/troubleshoot-embedded-device-tutorials.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing Windows-specific tools and solutions (such as Windows Device Manager and the Windows maximum path length limitation) without providing equivalent guidance for Linux users. Troubleshooting steps and error messages are often framed in a Windows context, and there are no Linux-specific examples or instructions for common cross-platform tasks like identifying serial ports or handling path length issues.
Recommendations
- For every Windows-specific troubleshooting step (e.g., using Device Manager to find COM ports), provide equivalent instructions for Linux (e.g., using 'ls /dev/tty*' or 'dmesg | grep tty').
- When referencing Windows path length limitations, mention that Linux does not typically have this issue, but suggest checking for other filesystem limitations if relevant.
- Include Linux-specific error messages or terminal output where applicable, or note differences in expected output.
- Ensure that all steps and resolutions are presented in a cross-platform manner, or clearly separate instructions for Windows and Linux users.
- Add a section or note at the beginning clarifying that the tutorials are cross-platform and that Linux users should refer to provided Linux-specific instructions.
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 requires a Windows 10 or 11 PC as a prerequisite, provides only Windows-specific setup scripts (*.bat files), and references Windows tools (such as Termite and File Explorer) without offering Linux alternatives. Instructions for tasks like flashing the device, running setup scripts, and monitoring serial output are all tailored to Windows, with no mention of Linux or cross-platform equivalents. While the Azure CLI is cross-platform, the overall workflow and tooling assume a Windows environment.
Recommendations
- Add explicit support and instructions for Linux (and macOS) users, including prerequisites and alternative tools.
- Provide Linux-compatible setup scripts (e.g., get-toolchain.sh) and update instructions to reference them.
- Suggest cross-platform serial monitoring tools (e.g., minicom, screen, PuTTY) alongside or instead of Termite.
- Replace or supplement File Explorer instructions with command-line equivalents (e.g., cp command) for Linux/macOS.
- Clarify which steps are Windows-specific and provide parallel steps for Linux/macOS where applicable.
- Test the workflow on Linux and document any differences or additional requirements.
IoT
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot/tutorial-use-mqtt.md
...azure-docs/blob/main/articles/iot/tutorial-use-mqtt.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation shows some Windows bias in the ordering and detail of examples. Windows prerequisites are listed before Linux, and the Windows section is more detailed (e.g., specifying Visual Studio and CMake installation options). The repository cloning example uses Windows command prompt syntax (git clone in a code block labeled 'cmd'), and there are no explicit Linux shell equivalents. Output folder locations are described for both OSes, but the Windows path is emphasized. There are no PowerShell-specific commands, but the overall structure and example ordering favor Windows users. Some Linux-specific details (like package manager alternatives for non-Ubuntu distros) are missing.
Recommendations
- Alternate the order of Windows and Linux instructions or present them side-by-side to avoid implicit prioritization.
- Provide equivalent Linux shell commands and examples wherever Windows commands are shown, including repository cloning and file path references.
- Expand Linux prerequisites to mention common distributions and alternatives to apt (e.g., yum, dnf, zypper).
- Ensure all code snippets and file path references are shown for both Windows and Linux, using appropriate syntax and conventions.
- Where possible, use cross-platform tools and commands (e.g., generic git, cmake, make) and clarify any OS-specific steps.
- Add troubleshooting tips or notes for common Linux issues (e.g., permissions, library paths) to match the detail given for Windows.
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 demonstrates a Windows-first bias by exclusively deploying the simulation and edge infrastructure on a Windows 11 Enterprise VM, instructing users to use RDP, Windows command prompt, and Windows Subsystem for Linux (WSL) to access Linux tools. There are no instructions or examples for deploying or running the solution natively on Linux hosts, nor for using Linux-native tools or environments. The documentation assumes a Windows-centric workflow, with Linux capabilities only available via WSL, and omits guidance for users who may want to use Linux VMs or physical machines directly.
Recommendations
- Provide parallel instructions for deploying the simulation and edge infrastructure on a native Linux VM (e.g., Ubuntu, CentOS) in Azure, including SSH access and Linux-native command-line usage.
- Include Linux-native installation steps for K3S and the simulation, without requiring WSL or Windows command prompt.
- Offer guidance for users who wish to use Docker and Kubernetes directly on Linux, including any necessary prerequisites and troubleshooting tips.
- Clarify which steps are platform-agnostic and which are Windows-specific, and ensure Linux users are not required to use Windows tools or environments.
- Where possible, present Linux and Windows instructions side by side, or clearly indicate both options, to ensure parity and inclusivity for cross-platform users.
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 exhibits a strong Windows bias. It explicitly requires Windows 10 or 11 as a prerequisite, provides only Windows batch scripts for tool installation and build steps, and references Windows-specific tools (e.g., Termite, File Explorer, Device Manager). There are no instructions or examples for Linux (or macOS) users, and alternative cross-platform tools are not mentioned. Even when Azure CLI is discussed, the local installation context is implicitly Windows, and the use of Windows command shells is assumed.
Recommendations
- Provide equivalent instructions and scripts for Linux (and optionally macOS), including shell (.sh) scripts for toolchain setup and build steps.
- List cross-platform alternatives to Windows-only tools such as Termite (e.g., minicom, screen, PuTTY) and provide usage examples.
- Update the prerequisites to include Linux (and macOS) as supported development environments, or clearly state if they are unsupported.
- When referencing file navigation, include Linux command-line equivalents (e.g., using terminal and file paths with forward slashes).
- For serial port identification, describe how to find device ports on Linux (e.g., using dmesg, ls /dev/tty*), not just Windows Device Manager.
- If Azure CLI is used, clarify that it is cross-platform and provide any OS-specific notes as needed.
- Consider restructuring the documentation so that instructions for different operating systems are presented in parallel or as tabs/sections.
IoT
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot/troubleshoot-embedded-device-tutorials.md
...articles/iot/troubleshoot-embedded-device-tutorials.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by referencing Windows-specific limitations (such as maximum path length), linking to Windows documentation, and suggesting the use of Windows Device Manager for troubleshooting. There are no equivalent instructions or examples for Linux or macOS users, and Linux tools or patterns are not mentioned.
Recommendations
- For path length issues, add Linux/macOS context (e.g., note that Linux filesystems typically do not have the same path length limitation, but mention any relevant caveats).
- When referencing Windows Device Manager to find COM ports, also describe how to identify serial ports on Linux (e.g., using 'ls /dev/tty*' or 'dmesg | grep tty') and macOS.
- If terminal software settings are discussed, mention popular cross-platform tools (e.g., PuTTY, minicom, screen) and provide example commands for Linux/macOS.
- Where Windows-specific links are provided, add parallel notes or links for Linux/macOS users.
- Review all troubleshooting steps to ensure parity for Linux/macOS users, including USB troubleshooting and flashing utilities.
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 demonstrates a strong Windows bias. It explicitly requires a Windows 10/11 PC as a prerequisite, provides only Windows-specific scripts (e.g., .bat files), and references Windows tools and workflows (such as File Explorer, Device Manager, and Termite, which is Windows-only). There are no instructions or alternatives for Linux or macOS users, and no mention of equivalent tools or scripts for non-Windows environments.
Recommendations
- Provide equivalent setup scripts for Linux and macOS (e.g., shell scripts like get-toolchain.sh).
- Include instructions for installing and using cross-platform or Linux-native serial terminal tools (e.g., minicom, screen, or picocom) as alternatives to Termite.
- Replace or supplement references to Windows File Explorer and Device Manager with cross-platform alternatives or command-line instructions.
- Update prerequisites to clarify support for Linux/macOS, or explicitly state if only Windows is supported (and why).
- Ensure all command-line examples and workflow steps are demonstrated for both Windows and Linux/macOS environments.
- If certain tools are Windows-only, suggest open-source or cross-platform alternatives and provide usage instructions.
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
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. PowerShell is mentioned as a primary automation tool alongside Azure CLI, and in some cases, PowerShell examples or links are provided before or more prominently than Azure CLI equivalents. There are references to Windows-specific tools (e.g., 'PowerShell functions for IoT Edge for Linux on Windows'), and the use of PowerShell is highlighted in the cloud-based solution section before Azure CLI. There is also a lack of explicit Linux/Bash examples or references to Linux-native tooling, which may make the documentation less approachable for Linux users.
Recommendations
- Ensure that Azure CLI (cross-platform) examples are always presented before or alongside PowerShell examples, especially in introductory or summary sections.
- Add explicit Bash/Linux shell examples where automation or scripting is discussed, or clarify that Azure CLI commands work identically on Linux, macOS, and Windows.
- Avoid referencing Windows-specific tools (such as 'PowerShell functions for IoT Edge for Linux on Windows') without providing Linux-native alternatives or clarifying cross-platform support.
- Where PowerShell is mentioned, also mention Bash or other Linux-native scripting environments to ensure parity.
- Consider a dedicated section or callout for Linux users, highlighting any differences or additional steps required on Linux platforms.
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 demonstrates a clear Windows bias: it specifies Windows 10/11 as a prerequisite, uses Windows-specific tools and instructions (e.g., ESP-IDF CMD, Windows Device Manager), and provides file paths and commands in Windows format. There are no instructions or examples for Linux or macOS users, and Linux equivalents for steps like finding the serial port or running the ESP-IDF environment are missing.
Recommendations
- Add a section in prerequisites listing supported Linux and macOS versions, or clarify if only Windows is supported.
- Provide parallel instructions for Linux/macOS, including how to install ESP-IDF, launch the build environment, and run commands in a terminal.
- Include Linux/macOS equivalents for finding the serial port (e.g., using 'ls /dev/tty*' or 'dmesg | grep tty').
- Use cross-platform file paths in examples, or show both Windows and Unix-style paths.
- Mention how to run ESP-IDF tools from a standard terminal (bash/zsh) on Linux/macOS.
- Reference cross-platform tools (e.g., Visual Studio Code) for debugging, and provide any necessary setup steps for non-Windows systems.
- Ensure all steps that reference Windows-specific UI (e.g., Device Manager) have Linux/macOS alternatives (e.g., using 'udevadm', 'lsusb', or system settings).
IoT
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot/iot-overview-security.md
...e-docs/blob/main/articles/iot/iot-overview-security.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation demonstrates a mild Windows bias. While most guidance is platform-neutral and focuses on Azure services, there are several instances where Windows tools or patterns are mentioned explicitly or before Linux equivalents. For example, BitLocker is named as the OS-level encryption tool for data at rest, with no mention of Linux alternatives (such as LUKS/dm-crypt). The section on protecting against malicious activity refers to 'install the latest antivirus and anti-malware capabilities on each device operating system' but does not provide Linux-specific recommendations or examples. The only explicit OS-level tool mentioned is BitLocker (Windows), and there are no Linux command-line or configuration examples provided anywhere in the document.
Recommendations
- When recommending OS-level encryption, mention both BitLocker (Windows) and LUKS/dm-crypt (Linux) to provide parity.
- If suggesting antivirus/anti-malware, provide examples or references for both Windows (e.g., Microsoft Defender) and Linux (e.g., ClamAV, Sophos, etc.).
- Where device or edge runtime updates are discussed, include references to both Windows Update and Linux package management (e.g., apt, yum) or OS update mechanisms.
- If providing examples or naming tools, ensure both Windows and Linux equivalents are mentioned, or use platform-neutral language.
- Consider adding a table or section summarizing common security tools and practices for both Windows and Linux IoT devices.
IoT
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot/howto-connect-on-premises-sap-to-azure.md
...articles/iot/howto-connect-on-premises-sap-to-azure.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a Windows bias by exclusively referencing Windows environments and tools when configuring the on-premises SAP system and the Microsoft on-premises data gateway. All SAP configuration steps assume use of a Windows virtual machine, and installation instructions for the SAP Connector for Microsoft .NET are Windows-specific. There are no examples or guidance for Linux-based SAP servers or for using cross-platform alternatives.
Recommendations
- Include parallel instructions for configuring SAP on Linux-based servers, acknowledging that many SAP installations run on Linux.
- Provide examples or references for using the SAP Java Connector (JCo) or other cross-platform connectors, not just the .NET Connector for Windows.
- Clarify whether the on-premises data gateway and SAP Logic Apps integration can be achieved from non-Windows environments, and if not, explicitly state this limitation.
- If possible, offer guidance for Linux-based deployment of the required connectors and data gateway, or link to relevant Microsoft or SAP documentation.
- Ensure screenshots and step-by-step instructions are not solely based on Windows desktops, or supplement them with Linux equivalents where applicable.
IoT
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot/concepts-using-c-sdk-and-embedded-c-sdk.md
...rticles/iot/concepts-using-c-sdk-and-embedded-c-sdk.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a mild Windows bias, primarily by listing Windows before Linux in several places ("Windows or Linux devices"), mentioning Windows-specific technologies (Schannel, Win32 sockets) before or alongside cross-platform or Linux equivalents (OpenSSL, Berkeley sockets), and omitting concrete Linux-specific examples or tools. There are no code samples, but the pattern of mentioning Windows first and referencing Windows-specific stack components without equal Linux detail suggests a subtle prioritization of Windows.
Recommendations
- When listing supported platforms, alternate the order (e.g., 'Linux and Windows' as often as 'Windows and Linux'), or use alphabetical order.
- When mentioning platform-specific technologies (e.g., Schannel, Win32 sockets), ensure Linux equivalents (OpenSSL, Berkeley sockets) are given equal prominence and explanation.
- Add explicit Linux-focused examples, such as sample commands, build instructions, or references to Linux distributions and tools.
- Where possible, provide parity in platform-specific guidance, such as linking to Linux-specific setup guides or troubleshooting resources.
- Consider including a table or section that clearly outlines platform-specific requirements and differences for both Windows and Linux, rather than focusing on Windows-specific details.
IoT
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot/howto-iot-industrial-dataspaces.md
...b/main/articles/iot/howto-iot-industrial-dataspaces.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a Windows bias by repeatedly instructing users to use a Windows command prompt and the Windows Subsystem for Linux (WSL) to execute Linux commands, rather than providing native Linux or macOS instructions. All command-line steps are framed from a Windows perspective, with no direct guidance for users on Linux or macOS systems. There are also references to Windows-specific installation steps (e.g., 'wsl --install'), and no mention of equivalent Linux-native environments or tools.
Recommendations
- Provide parallel instructions for Linux and macOS users, including native shell commands and environment setup steps.
- Avoid assuming the user is on Windows; structure command-line instructions with tabs or sections for each major OS (Windows, Linux, macOS).
- Replace or supplement WSL-specific instructions with native Linux and macOS alternatives (e.g., running curl directly in a terminal).
- Explicitly mention required tools (curl, etc.) and how to install them on all supported platforms.
- Review all references to Windows tools and ensure Linux/macOS equivalents are given equal prominence and detail.
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 moderate Windows bias. In the 'Tools to connect and manage devices' section, Windows-specific tools like Azure PowerShell are listed alongside cross-platform tools, but there is no mention of Linux-specific tools or workflows. PowerShell is highlighted as a primary interface, and there are no explicit Linux shell/bash examples or references to Linux-native tools. Additionally, the ordering of tools often places Windows-centric options (PowerShell) before more universally cross-platform options, and there are no Linux-specific instructions or parity notes.
Recommendations
- Add explicit examples or references for Linux users, such as bash shell commands or Linux package installation steps for the Azure CLI.
- Balance the tool listing by including Linux-native tools or workflows (e.g., bash scripts, systemd integration, or references to Linux package managers).
- When listing tools, avoid putting Windows-centric tools (like PowerShell) before cross-platform options unless there is a clear reason; consider grouping by platform or indicating cross-platform compatibility.
- Include a note or section clarifying which tools are cross-platform and which are Windows-only, and provide equivalent Linux instructions where possible.
- Add links to Linux-specific getting started guides or tutorials for Azure IoT device development.
IoT
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot/concepts-using-c-sdk-and-embedded-c-sdk.md
...rticles/iot/concepts-using-c-sdk-and-embedded-c-sdk.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation generally treats Windows and Linux as equivalent in most places, but there is a subtle Windows bias. In scenario 1, 'Windows' is consistently mentioned before 'Linux' ("for Linux and Windows", "Windows or Linux devices"), and Windows-specific technologies (e.g., Schannel, Win32 sockets) are called out alongside cross-platform ones, but Linux-specific equivalents (e.g., GnuTLS, epoll) are not. There are no explicit Linux command-line or tool examples, and no Linux-specific integration details are provided. The documentation also lists Windows as a recommended platform for the C SDK, but does not provide Linux-specific guidance or examples.
Recommendations
- Alternate the order of 'Windows' and 'Linux' mentions, or use 'Windows and Linux' consistently to avoid perceived prioritization.
- Include Linux-specific details where Windows-specific technologies are mentioned (e.g., mention GnuTLS or other common Linux TLS stacks alongside Schannel).
- Provide Linux-specific examples, such as command-line usage, build instructions, or integration tips, to ensure parity with Windows.
- Highlight any Linux-specific considerations or optimizations, especially in areas where Windows-specific tools (like Schannel or Win32 sockets) are discussed.
- Ensure that tables and recommendations do not list Windows before Linux unless there is a technical reason to do so.
IoT
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot/concepts-model-discovery.md
...ocs/blob/main/articles/iot/concepts-model-discovery.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page demonstrates a bias towards Windows environments and tooling. It references only .NET/NuGet-based tools (ModelsRepositoryClient in C#), provides code samples exclusively in C#, and does not mention or provide examples for Linux-native tools, cross-platform SDKs, or command-line alternatives. There are no Linux shell, Python, or REST API examples, and no mention of how to use these features on Linux or macOS. The focus on NuGet and C# implicitly prioritizes Windows development environments.
Recommendations
- Add equivalent code samples in cross-platform languages such as Python, JavaScript, or Java, using their respective Azure SDKs.
- Provide REST API usage examples (e.g., using curl or HTTPie) to demonstrate platform-agnostic access.
- Mention and demonstrate how to install and use the Azure CLI or Azure SDKs on Linux/macOS, including package installation instructions.
- Include shell script examples for retrieving models or interacting with IoT Hub, where applicable.
- Reorganize sections to present cross-platform or platform-neutral approaches before Windows/.NET-specific ones.
- Reference package managers and tools common on Linux (e.g., pip for Python, npm for Node.js) alongside NuGet.