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 51-75 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 page demonstrates a subtle Windows bias in several areas. In the 'Tools to connect and manage devices' section, Windows-centric tools such as Azure PowerShell are listed alongside cross-platform options, but there is no mention of Linux-specific tools or guidance. The order of tool presentation often puts Windows-first tools (PowerShell) before Linux-native alternatives. There are no explicit Linux command-line examples or references to Linux package managers or shell environments. The documentation does not provide parity in examples or tool recommendations for Linux users, and the language and tool choices may implicitly favor Windows development environments.
Recommendations
- Explicitly mention Linux compatibility for all tools, especially Azure CLI and VS Code extensions.
- Include Linux-specific instructions or examples (e.g., bash commands, package installation via apt/yum, using Azure CLI in Linux shells).
- Add references to Linux-native tools or workflows for IoT device management, if available.
- Reorder tool listings to alternate or balance Windows and Linux options, or group cross-platform tools first.
- Clarify that PowerShell Core is cross-platform, if relevant, and provide examples for both Windows PowerShell and bash/zsh.
- Ensure that all tutorials and next steps include Linux as a first-class development environment.
Create Pull Request
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 references for Linux or macOS users, and no examples or troubleshooting steps tailored to non-Windows environments.
Recommendations
- For path length issues, mention that this is a Windows-specific problem and clarify that Linux/macOS users are not affected. Optionally, provide guidance for long path handling on those platforms if relevant.
- When suggesting the use of Windows Device Manager to identify COM ports, also provide instructions for Linux (e.g., using `dmesg`, `ls /dev/tty*`, or `lsusb`) and macOS (e.g., `ls /dev/tty.*`).
- Wherever Windows-specific tools or settings are mentioned, add parallel instructions for Linux and macOS users.
- Include examples and troubleshooting steps that are platform-agnostic or explicitly cover all major operating systems.
- Review all links and references to ensure that they are not exclusively Windows-focused, or provide equivalent references for other platforms.
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 demonstrates some Windows bias, primarily by listing Windows prerequisites and tools (such as Visual Studio) before Linux equivalents, and by providing more detailed setup steps for Windows. The use of Windows-specific tools (Visual Studio) and the ordering of instructions (Windows first, then Linux) reinforce this bias. However, the tutorial does provide Linux instructions and examples, and the main sample build and run commands are cross-platform.
Recommendations
- Alternate the order of Windows and Linux instructions or present them in parallel tabs to avoid always listing Windows first.
- Provide equivalent detail for Linux as for Windows, e.g., mention recommended Linux IDEs or editors (such as VS Code, CLion, or gedit) and any relevant Linux-specific setup tips.
- Avoid assuming Visual Studio is the default C++ development environment; mention cross-platform alternatives.
- Ensure all command-line examples are provided for both Windows (cmd or PowerShell) and Linux (bash), especially for git clone and build steps.
- Where possible, use neutral, cross-platform language and tools in explanations and code snippets.
- Explicitly state that all steps are supported on both Windows and Linux, and ensure parity in troubleshooting or notes sections.
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 consistently referencing Windows-specific workflows, such as instructing users to use the Windows command prompt and Windows Subsystem for Linux (WSL) to access Linux tools. There are no native Linux or macOS instructions or examples, and the use of WSL is presented as the default way to run Linux commands. This approach assumes a Windows environment and omits guidance for users on Linux or macOS systems.
Recommendations
- Provide native Linux and macOS instructions alongside Windows instructions, especially for command-line operations.
- Replace or supplement WSL-based steps with direct Linux/macOS shell commands and clarify any differences in environment setup.
- Avoid assuming the user is on Windows; use neutral language such as 'In your terminal' instead of 'From a Windows command prompt'.
- Where Windows-specific tools or portals are referenced, include equivalent steps for Linux/macOS users (e.g., accessing Azure portal, setting environment variables, etc.).
- Add a prerequisites section that clearly states supported platforms and any platform-specific requirements or alternatives.
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 for the on-premises SAP system configuration. All SAP system steps assume a Windows virtual machine, and the SAP Connector for Microsoft .NET is only described for Windows x64. File paths and instructions are Windows-specific, with no mention of Linux alternatives or parity. There are no examples or guidance for Linux-based SAP deployments.
Recommendations
- Add parallel instructions and screenshots for configuring SAP systems running on Linux, including using SAP GUI for Java or web-based SAP interfaces.
- Document the use of SAP connectors and gateways on Linux, such as SAP NetWeaver RFC SDK or Java connectors, and provide installation and configuration steps for Linux environments.
- Include Linux file paths and command-line examples where relevant, or clarify any platform limitations.
- Explicitly state platform requirements and, if Windows is required for certain components, provide rationale and suggest workarounds or alternatives for Linux users.
- Ensure that all references to tools (e.g., SAP Connector for Microsoft .NET) are accompanied by Linux equivalents or a note about their availability.
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 demonstrates a strong Windows bias. It explicitly requires Windows 10 or 11 as a prerequisite, provides only Windows batch scripts (e.g., .bat files) for toolchain setup and build, and references Windows-specific tools (Termite, File Explorer, Device Manager). There are no equivalent instructions, scripts, or tool recommendations for Linux users, nor are Linux terminal commands or alternatives provided. The use of Windows CMD, PowerShell, and Git Bash for Windows is mentioned, but no mention is made of native Linux shells or workflows.
Recommendations
- Add Linux as a supported platform in the prerequisites, or clarify if it is unsupported.
- Provide equivalent shell scripts (e.g., get-toolchain.sh, rebuild.sh) for Linux users, and document their usage.
- List Linux alternatives for Windows-only tools such as Termite (e.g., minicom, screen, picocom) and provide setup instructions.
- Replace or supplement File Explorer and Device Manager steps with Linux equivalents (e.g., using the terminal, lsusb, dmesg, or /dev/tty* for serial ports).
- Include Linux command-line examples alongside Windows commands throughout the tutorial.
- Explicitly state any platform limitations or differences in the workflow.
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 exhibits a strong Windows bias. It specifies Windows 10/11 as a prerequisite, uses Windows-specific tools and commands (e.g., ESP-IDF CMD, Windows Device Manager), and provides file paths and instructions only for Windows environments. There are no instructions or examples for Linux or macOS users, and Linux equivalents for key steps (such as finding the serial port or running the ESP-IDF environment) are missing.
Recommendations
- Add a section in prerequisites listing supported Linux distributions (e.g., Ubuntu) and macOS, or clarify if only Windows is supported.
- For each step involving Windows-specific tools (e.g., ESP-IDF CMD, Device Manager), provide equivalent instructions for Linux (e.g., using terminal, lsusb, dmesg, or /dev/ttyUSB*) and macOS.
- Include Linux/macOS file path examples alongside Windows paths (e.g., ~/espbuild instead of C:\espbuild).
- When referencing enabling long paths or other Windows-specific settings, provide analogous guidance for Linux/macOS if relevant, or state if not needed.
- Mention and show how to launch the ESP-IDF environment on Linux/macOS (e.g., source export.sh, use terminal).
- For flashing and monitoring, show how to identify the serial port on Linux/macOS and provide example commands.
- If Azure IoT Explorer is Windows-only, suggest cross-platform alternatives or clarify platform limitations.
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, only provides instructions and scripts for Windows (e.g., .bat files), and references Windows-specific tools and workflows (e.g., File Explorer, Device Manager, Termite, and Windows CMD/PowerShell). There are no equivalent instructions, scripts, or tool recommendations for Linux (or macOS) users, and Linux alternatives for serial monitoring or flashing are not mentioned.
Recommendations
- Add Linux (and optionally macOS) as supported platforms in the prerequisites, or clearly state if they are unsupported.
- Provide equivalent setup scripts for Linux (e.g., get-toolchain.sh) and include instructions for running them.
- List Linux-compatible tools for serial port monitoring (e.g., minicom, screen, picocom) alongside or instead of Termite, and provide configuration steps for these tools.
- Replace or supplement Windows-specific instructions (e.g., File Explorer, Device Manager) with cross-platform or Linux-specific alternatives (e.g., using the terminal, lsusb, dmesg, or /dev/tty* devices).
- Ensure all command-line examples are cross-platform or provide both Windows and Linux variants.
- If certain steps are only possible on Windows, clearly indicate this and suggest workarounds or alternatives for Linux users.
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
Powershell Heavy
Summary
The documentation demonstrates a clear Windows bias: deployment instructions exclusively use a Windows 11 Enterprise VM, require RDP for access, and reference Windows-specific tools (e.g., Windows Subsystem for Linux, Windows command prompt). There are no instructions or examples for deploying or running the solution natively on Linux or macOS systems, nor are there alternatives to Windows-specific steps. Linux is only mentioned as a subsystem within Windows, not as a first-class platform.
Recommendations
- Provide parallel instructions for deploying and running the production line simulation and edge infrastructure on native Linux VMs (e.g., Ubuntu Server) and/or macOS, including setup steps for Docker, Kubernetes (K3s), and related tools.
- Include Linux-native commands and shell script examples outside of WSL context, and clarify any OS-specific differences.
- Offer guidance for connecting to Linux VMs (e.g., via SSH) instead of only RDP/Windows.
- Mention and support Linux-based Azure VM images as deployment targets.
- Ensure all scripts and tools referenced are cross-platform or provide alternatives for Linux/macOS users.
- Reorder sections or provide tabs so that Linux and Windows instructions are presented with equal prominence.
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 demonstrates a moderate Windows bias, particularly in the CLI section for cloud-based solutions, where PowerShell is presented before Azure CLI and receives a dedicated section with multiple examples and links. There is also a reference to 'PowerShell functions for IoT Edge for Linux on Windows,' which is a Windows-specific scenario. While Azure CLI is covered, the prominence and ordering of PowerShell, as well as the lack of explicit Linux/Bash examples or mention of native Linux tools, indicate a bias toward Windows environments.
Recommendations
- Present Azure CLI examples before PowerShell in CLI sections, as Azure CLI is cross-platform and more commonly used on Linux.
- Ensure parity in example depth and coverage between Azure CLI and PowerShell, especially for cloud-based scenarios.
- Add explicit Bash/Linux shell examples or references where appropriate, especially for automation and scripting.
- Avoid referencing Windows-specific tools (such as 'PowerShell functions for IoT Edge for Linux on Windows') without providing native Linux alternatives or clarifying their applicability.
- Where possible, clarify that all Azure CLI commands work natively on Linux, macOS, and Windows, and provide guidance for Linux users.
- Consider adding a section or callout for Linux users, highlighting any differences or additional steps required.
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 exhibits a mild Windows bias. While it is generally cross-platform and focuses on Azure-native and Kubernetes-based solutions, there are specific instances where Windows tools (e.g., BitLocker) are mentioned for encryption, and Windows is referenced before Linux in some cases (e.g., 'IoT Edge for Linux on Windows'). There are no explicit Linux command-line or tool examples, and Linux-native encryption solutions are not mentioned alongside Windows ones. No PowerShell-specific commands or Windows-only patterns dominate, but Linux parity could be improved.
Recommendations
- When recommending OS-level encryption (e.g., 'Encrypt data at rest'), mention Linux-native solutions such as LUKS/dm-crypt alongside BitLocker.
- Where Windows is referenced (e.g., 'IoT Edge for Linux on Windows security'), also mention standard Linux deployments and link to their security guidance.
- Provide examples or references for both Windows and Linux where OS-level or device-level security tools are discussed.
- Audit for any other implicit Windows-first language and ensure Linux equivalents are given equal prominence.
- Consider including a table or section summarizing security tool recommendations for both Windows and Linux environments.
Medium 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 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 a Windows-oriented perspective. However, Azure CLI examples are also provided, and most management options (portal, ARM templates, Bicep) are cross-platform, mitigating the overall impact.
Recommendations
- Present Azure CLI examples before PowerShell in all sections, as CLI is cross-platform and preferred by Linux/macOS users.
- Explicitly state platform compatibility for each tool (e.g., note that PowerShell is available on Linux/macOS, but CLI is native).
- Add Bash or shell script examples where appropriate, especially for automation scenarios.
- Reduce references to Windows-specific tools or patterns unless necessary, and provide Linux/macOS alternatives.
- Clarify when instructions or modules are Windows-only (e.g., 'IoT Edge for Linux on Windows') and offer native Linux guidance.
IoT
Connect an ESPRESSIF ESP-32 to Azure IoT Hub tutorial
...ot/tutorial-devkit-espressif-esp32-freertos-iot-hub.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page exhibits a notable Windows bias. It explicitly lists Windows 10/11 as a prerequisite, references Windows-specific tools (such as Device Manager), and provides instructions tailored to Windows (e.g., using ESP-IDF CMD, enabling long paths in Windows, specifying Windows file paths like C:\espbuild). There are no instructions or examples for Linux or macOS users, nor are alternative tools or workflows mentioned for those platforms. This may create friction or confusion for non-Windows users attempting to follow the tutorial.
Recommendations
- Add explicit support for Linux and macOS in the prerequisites section, or clarify platform limitations if any exist.
- Provide alternative instructions for installing ESP-IDF tools on Linux/macOS, including relevant commands and environment setup.
- Include examples for common Linux/macOS terminal commands (e.g., using /dev/ttyUSBx for serial ports, using Terminal instead of CMD).
- Replace or supplement Windows-specific instructions (such as Device Manager for COM port detection) with Linux/macOS equivalents (e.g., using dmesg, lsusb, or ls /dev/tty*).
- Use platform-agnostic file paths in examples, or provide both Windows and Linux/macOS versions.
- Clarify any steps that are Windows-only and provide workarounds or alternatives for other platforms.
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 page lists Windows-specific tools (PowerShell) alongside cross-platform options (CLI, VS Code), and includes PowerShell as a primary method for managing IoT resources. Windows tools are mentioned explicitly and given equal prominence to cross-platform tools, with no explicit Linux/macOS alternatives or examples. The ordering in the tools table places Azure PowerShell before VS Code, which may subtly prioritize Windows workflows. No Linux/macOS-specific tools or shell examples are provided, and there is no mention of platform-specific considerations for Linux users.
Recommendations
- Add explicit Linux/macOS shell examples (e.g., bash) for common tasks, especially where PowerShell is mentioned.
- Clarify which tools are cross-platform and which are Windows-only, including notes on installation and usage for Linux/macOS.
- Include Linux-native tools or workflows (e.g., bash scripts, package managers) where relevant.
- Reorder tool lists to start with cross-platform options (CLI, VS Code) before Windows-specific tools.
- Provide links or references to Linux/macOS documentation for Azure IoT development.
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 a Windows-first perspective. However, Azure CLI examples are also provided, and most management options (ARM templates, Bicep, Azure portal) are cross-platform, mitigating the overall impact.
Recommendations
- Present Azure CLI examples before PowerShell in all sections, as CLI is cross-platform.
- Explicitly state platform compatibility for each tool (e.g., Azure CLI works on Windows, Linux, and macOS; PowerShell Core is cross-platform but Windows PowerShell is not).
- Add Bash or shell script examples where automation is discussed, especially for Linux users.
- Avoid referencing Windows-specific tools (e.g., 'PowerShell functions for IoT Edge for Linux on Windows') without Linux-native alternatives or clarifications.
- Ensure that all critical workflows have CLI or ARM template examples, not just PowerShell.
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 exhibits a Windows bias by defaulting to Windows 11 Enterprise VM deployment, instructing users to use RDP and Windows command prompt, and only mentioning Windows IoT Enterprise as the recommended production OS. Linux usage is only introduced via WSL (Windows Subsystem for Linux) inside the Windows VM, rather than supporting native Linux VM deployment or providing Linux/macOS-specific instructions. There are no examples for deploying or operating the solution on native Linux or macOS environments, and all operational steps (including installation, simulation, and edge infrastructure) are described from a Windows-first perspective.
Recommendations
- Provide instructions for deploying the production line simulation and edge infrastructure on native Linux VMs (e.g., Ubuntu, CentOS) and macOS, including required dependencies and setup steps.
- Include Linux/macOS-specific examples for connecting to VMs (e.g., SSH instead of RDP), running shell scripts, and managing Kubernetes clusters.
- Mention Linux distributions as supported base OS options for production scenarios, not just Windows IoT Enterprise.
- Reorder examples so that Linux and Windows instructions are presented with equal prominence, or provide parallel instructions for both platforms.
- Clarify which steps are platform-agnostic and which are platform-specific, and provide alternatives where possible.
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation references Windows-specific tools (PowerShell) alongside cross-platform options (Azure CLI and REST API) when discussing management SDK alternatives. PowerShell is mentioned explicitly, which is a Windows-centric tool, and it is listed before REST API, potentially indicating a Windows-first bias. There are no explicit Linux examples or Linux-specific tools mentioned, and no evidence of Powershell-heavy examples or missing Linux examples in code samples, as the page is mostly descriptive and links to includes.
Recommendations
- Explicitly mention that Azure CLI is cross-platform and suitable for Linux, macOS, and Windows.
- Provide parity by listing Azure CLI before PowerShell, or group them together as platform-specific alternatives.
- Include links or notes about using SDKs and management tools on Linux systems.
- Where PowerShell is referenced, clarify its platform limitations and suggest Bash or shell alternatives for Linux users.
- Add examples or references for Linux usage where possible, especially in sections discussing tooling.
Medium 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 links to a PowerShell-specific guide before the REST API. This prioritizes Windows-centric tooling and patterns, with no explicit mention of Linux-specific alternatives or parity in examples. There are no Linux shell (bash) or cross-platform CLI usage examples, and PowerShell is listed before REST API, which may suggest a Windows-first approach.
Recommendations
- Explicitly mention that Azure CLI is cross-platform and provide links or examples for both Windows (PowerShell) and Linux/macOS (bash) usage.
- When listing alternatives, avoid ordering that implies preference unless justified; consider listing Azure CLI, PowerShell, and REST API in alphabetical order or clarify cross-platform support.
- Add examples or links for Linux/macOS users, such as bash scripts or terminal commands, to ensure parity with Windows/PowerShell examples.
- Clarify in the documentation that PowerShell is available cross-platform, or provide guidance for Linux users where appropriate.
IoT
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot/iot-sdks.md
...softDocs/azure-docs/blob/main/articles/iot/iot-sdks.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation references PowerShell as a management tool alongside Azure CLI and REST API, listing PowerShell before REST API and without explicit mention of Linux equivalents or parity. This subtly prioritizes Windows tooling and may imply a Windows-first approach for management tasks. No explicit Linux or cross-platform examples are provided, nor is there mention of Bash or other Linux-native tools.
Recommendations
- Explicitly mention that Azure CLI is cross-platform and can be used on Linux, macOS, and Windows.
- Provide Bash or shell script examples for Linux users where management tasks are discussed.
- When listing management tools, avoid ordering that implies preference (e.g., list Azure CLI, PowerShell, and REST API in alphabetical order or clarify platform compatibility).
- Add a note or section highlighting Linux support and parity for SDK usage and management operations.
- Ensure any referenced guides or included content also offer Linux-specific instructions or examples.
IoT
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot/iot-sdks.md
...softDocs/azure-docs/blob/main/articles/iot/iot-sdks.md
Medium 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, listing it before REST API and without explicit mention of Linux shell equivalents (such as Bash or shell scripting). This subtly prioritizes Windows-centric tooling and patterns, and does not provide parity in examples or references for Linux users.
Recommendations
- Explicitly mention Bash or Linux shell scripting as alternatives alongside PowerShell and Azure CLI.
- Ensure that examples and references for management tasks include both Windows (PowerShell) and Linux (Bash/CLI) options.
- Where possible, provide links to Linux-specific guides or documentation for SDK usage and management.
- Review referenced include files to ensure they do not contain Windows-only examples or instructions.
IoT
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot/howto-use-iot-explorer.md
...-docs/blob/main/articles/iot/howto-use-iot-explorer.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation demonstrates a mild Windows bias by specifically mentioning Windows (e.g., launching from the Start menu) when describing how to run Azure IoT explorer, while not providing equivalent details or examples for Linux users. There are no Linux-specific instructions or examples, and the only platform-specific launch method mentioned is for Windows.
Recommendations
- Add explicit instructions for launching Azure IoT explorer on Linux (e.g., using AppImage, .deb, or .tar.gz, and how to run from terminal or create desktop shortcuts).
- Mention Linux alongside Windows when describing installation and launch procedures, ensuring parity in the level of detail.
- Include troubleshooting tips or known issues relevant to Linux users if applicable.
- Where platform-specific behavior is described, provide parallel guidance for both Windows and Linux users.
IoT
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot/iot-sdks.md
...softDocs/azure-docs/blob/main/articles/iot/iot-sdks.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation mentions PowerShell as an alternative to the Azure CLI and REST API for management tasks, listing it before REST API and alongside Azure CLI. This subtly prioritizes Windows tooling by explicitly naming PowerShell, which is primarily a Windows-centric tool, and by listing it before REST API. There are no explicit Linux examples or Linux-specific tools mentioned, and no indication of parity in examples or instructions for Linux users.
Recommendations
- Explicitly mention Bash or shell scripting as an alternative alongside PowerShell and Azure CLI, to acknowledge Linux users.
- Ensure that any referenced guides (such as those for Azure CLI or PowerShell) provide both Windows and Linux usage examples.
- Where PowerShell is mentioned, clarify that Azure CLI is cross-platform and provide links or notes for Linux/macOS usage.
- Consider listing Azure CLI before PowerShell, as it is the more cross-platform tool.
- Add a note or section highlighting cross-platform compatibility and where to find Linux/macOS-specific instructions.
IoT
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot/concepts-model-discovery.md
...ocs/blob/main/articles/iot/concepts-model-discovery.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows Tools
Summary
The documentation page provides only C#/.NET (NuGet) code samples and references to Windows-centric tooling (NuGet, AzureEventSourceListener), with no mention of Linux, cross-platform, or non-Windows development environments. There are no examples or guidance for Linux users, such as using Python, Node.js, or command-line tools commonly available on Linux.
Recommendations
- Add code samples in additional languages that are popular on Linux (e.g., Python, Node.js, Java).
- Reference cross-platform SDKs and tools, not just .NET/NuGet.
- Explicitly mention that the APIs and tools are cross-platform if applicable, and provide Linux-specific installation or usage notes where relevant.
- Include instructions or examples for retrieving models using curl, wget, or other command-line tools available on Linux.
- Provide guidance for setting up the development environment on Linux, including package installation and dependencies.
IoT
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot/howto-use-iot-explorer.md
...-docs/blob/main/articles/iot/howto-use-iot-explorer.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page exhibits mild Windows bias. While it generally describes Azure IoT Explorer as cross-platform, the only platform-specific example given is for Windows (launching from the Start menu). There are no explicit Linux (or macOS) installation or usage instructions, nor are Linux-specific launch patterns or troubleshooting tips mentioned.
Recommendations
- Add explicit instructions or examples for installing and launching Azure IoT Explorer on Linux (e.g., AppImage, .deb, .rpm, or manual launch from terminal).
- Mention Linux and macOS alongside Windows when describing platform-specific behaviors (e.g., how to launch the application after installation).
- Provide troubleshooting tips or known issues relevant to Linux users, if any.
- Ensure screenshots or UI references are not Windows-specific, or provide equivalents for Linux/macOS if the UI differs.
IoT
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot/concepts-model-discovery.md
...ocs/blob/main/articles/iot/concepts-model-discovery.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows Tools
Summary
The documentation provides only C#/.NET (NuGet) code samples and references to Windows-centric tools (NuGet, AzureEventSourceListener), with no equivalent examples or guidance for Linux users or alternative languages/platforms. There are no CLI, Python, or REST API examples, and no mention of Linux-specific considerations or parity.
Recommendations
- Add equivalent code samples in other popular languages/platforms such as Python (using Azure SDK for Python), JavaScript/Node.js, and Java.
- Include examples using cross-platform tools such as Azure CLI, curl, or REST API calls to retrieve model definitions and interact with the Models Repository.
- Reference package managers and tools available on Linux (e.g., pip for Python, npm for Node.js) alongside NuGet.
- Clarify that the APIs and repositories are accessible from any OS, and provide explicit instructions or troubleshooting tips for Linux users.
- Provide sample commands for retrieving models using command-line tools available on Linux (e.g., wget, curl).