IoT Edge
95
Total Pages
59
Linux-Friendly Pages
36
Pages with Bias
37.9%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
184 issues found
Showing 176-184 of 184 flagged pages
IoT Edge
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-edge/includes/debug-without-container-run.md
...icles/iot-edge/includes/debug-without-container-run.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Powershell Heavy
Summary
The documentation page demonstrates a mild Windows bias. It assumes Visual Studio Code is being used on Windows, referencing Windows-specific shells (Git Bash, WSL Bash) and warning that PowerShell or Command Prompt cannot run the curl command. There are no explicit Linux/macOS examples or guidance, and Windows shell workarounds are mentioned before any Linux equivalents.
Recommendations
- Include explicit instructions for Linux/macOS users, such as confirming that the curl command works natively in their terminals.
- Add a note clarifying that on Linux/macOS, no shell change is needed for curl.
- Provide examples or troubleshooting tips for Linux/macOS environments.
- Reorder notes so that Linux/macOS instructions are presented alongside or before Windows-specific guidance.
Create Pull Request
IoT Edge
Create test certificates - Azure IoT Edge
...n/articles/iot-edge/how-to-create-test-certificates.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation consistently presents Windows instructions and examples before Linux equivalents in every major section. Windows-specific tools (PowerShell, vcpkg, Get-Pfxcertificate) are emphasized, with detailed PowerShell commands and setup steps. Linux instructions are present and generally complete, but Windows users see their workflow prioritized and receive more context for certain steps (e.g., OpenSSL installation).
Recommendations
- Alternate the order of Windows and Linux tabs in each section, or present both platforms equally in introductory text.
- Provide equally detailed instructions for Linux OpenSSL installation and troubleshooting, matching the Windows section.
- Where Windows-specific tools (PowerShell, vcpkg) are mentioned, offer Linux equivalents (e.g., apt/yum for OpenSSL, bash scripts) with equal detail.
- Ensure that any troubleshooting or verification steps (such as checking thumbprints) use cross-platform commands or offer both PowerShell and bash/openssl alternatives side by side.
- Add a summary table at the top listing platform parity and any differences in workflow.
- Consider including macOS instructions if supported.
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation page demonstrates a mild Windows bias by consistently referencing Windows as a primary platform, especially through the repeated emphasis on 'IoT Edge for Linux on Windows' (EFLOW) as the recommended approach for Windows devices. Windows is listed alongside Linux distributions in Tier 1, and Windows-specific tooling (EFLOW) is mentioned before Linux equivalents. However, Linux platforms are well-represented, and there are no Windows-only examples or instructions; both Linux and Windows are covered in platform tables and support notes.
Recommendations
- Balance the order of platform mentions so Linux is not always secondary to Windows, especially in recommendations.
- Provide equal detail and visibility for native Linux installation and management, not just EFLOW for Windows.
- Clarify that EFLOW is a compatibility solution for Windows, while native Linux is the primary runtime.
- Add explicit links or references to Linux-specific troubleshooting and support resources, matching the detail given for Windows/EFLOW.
- Ensure that all support and installation instructions are equally detailed for Linux and Windows.
IoT Edge
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-edge/tutorial-deploy-stream-analytics.md
.../articles/iot-edge/tutorial-deploy-stream-analytics.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation demonstrates a mild 'windows_first' bias by listing the Windows quickstart link before the Linux equivalent in the prerequisites. However, the rest of the tutorial is platform-neutral, with no PowerShell- or Windows-specific commands, tools, or screenshots. All command-line examples use cross-platform commands (iotedge), and both Linux and Windows are acknowledged as supported platforms.
Recommendations
- List Linux and Windows quickstart links in the same order or in parallel (e.g., 'for Linux or Windows devices'), or list Linux first to avoid implicit prioritization.
- Where possible, provide explicit notes or links for both Linux and Windows users in setup and troubleshooting sections.
- Continue to use cross-platform tools and commands, and avoid platform-specific screenshots or instructions unless both are provided.
IoT Edge
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-edge/iot-edge-modules.md
...e-docs/blob/main/articles/iot-edge/iot-edge-modules.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation page does not provide any OS-specific examples, but it also does not mention or demonstrate Linux-specific tools, commands, or patterns. There are no explicit Windows or PowerShell examples, but the absence of any platform-specific guidance or examples (especially for Linux, which is a common IoT Edge deployment target) may leave Linux users underserved.
Recommendations
- Add explicit examples or notes for both Windows and Linux environments, especially in sections discussing module deployment and management.
- Include sample commands for common tasks (such as running containers, managing modules, or accessing logs) using both PowerShell (Windows) and Bash (Linux) where relevant.
- Reference cross-platform tools (such as Docker CLI) and clarify any OS-specific differences in workflow or configuration.
- Link to platform-specific setup or troubleshooting guides for both Windows and Linux IoT Edge devices.
IoT Edge
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-edge/tutorial-deploy-stream-analytics.md
.../articles/iot-edge/tutorial-deploy-stream-analytics.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation presents both Linux and Windows as options for setting up an IoT Edge device, but consistently lists Linux before Windows. However, throughout the rest of the tutorial, all instructions, commands, and examples are platform-neutral, using Azure portal UI and the cross-platform 'iotedge' CLI, with no Windows- or PowerShell-specific commands or tools. There are no examples or instructions that are exclusive to Windows, nor are there any Windows tools or patterns mentioned preferentially. Linux is slightly prioritized in the prerequisites by being listed first.
Recommendations
- Maintain explicit parity by providing both Linux and Windows quickstart links side-by-side, or clarify that the steps are identical for both platforms.
- If any platform-specific steps exist (such as service management, troubleshooting, or log access), provide both Linux and Windows examples.
- Explicitly state that the 'iotedge' CLI commands work on both Linux and Windows, and provide any necessary notes for Windows users (e.g., running commands in PowerShell or CMD).
- If future updates add troubleshooting or advanced configuration, ensure both Linux and Windows instructions are included.
IoT Edge
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-edge/iot-edge-modules.md
...e-docs/blob/main/articles/iot-edge/iot-edge-modules.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation page does not provide any OS-specific examples, but the only code sample shown is in C#, which is cross-platform. However, there are no explicit references to Windows, Windows tools, or PowerShell, nor are there any instructions or examples that are Windows-specific. The main bias is the lack of explicit Linux (or cross-platform) command-line or deployment examples, which could help Linux users understand how to interact with IoT Edge modules on their systems.
Recommendations
- Add explicit examples or references for both Windows and Linux environments, especially for common tasks such as deploying modules, managing containers, or interacting with the IoT Edge runtime.
- Include sample commands for both PowerShell (Windows) and Bash (Linux) where appropriate.
- Clarify in the documentation that Azure IoT Edge is supported on both Windows and Linux, and provide links to OS-specific setup guides.
- If showing code samples for interacting with the IoT Edge runtime, consider including examples in languages commonly used on Linux (e.g., Python, Bash scripts) in addition to C#.
IoT Edge
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-edge/support.md
...Docs/azure-docs/blob/main/articles/iot-edge/support.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation page generally presents Linux as the primary platform for Azure IoT Edge, but when discussing Windows support, it consistently refers to 'IoT Edge for Linux on Windows' (EFLOW) as the recommended approach. Windows is mentioned after Linux in most tables and explanations, but the Windows experience is always described as running Linux containers via a VM, not as a first-class native experience. There are no explicit PowerShell-heavy examples, Windows-only tools, or missing Linux examples, but the phrasing and ordering suggest a Linux-first, Windows-second approach, with Windows support being indirect.
Recommendations
- Clarify that Windows support is via EFLOW and explain the rationale for this approach, possibly in a dedicated section.
- If possible, provide more parity in examples or instructions for both Linux and Windows (even if Windows is via EFLOW), such as installation or troubleshooting steps.
- Explicitly state the limitations or differences in experience between native Linux and Windows (EFLOW) to set expectations.
- Consider adding a brief summary table at the top comparing native Linux, EFLOW on Windows, and (deprecated) Windows containers for quick reference.
IoT Edge
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-edge/version-history.md
...re-docs/blob/main/articles/iot-edge/version-history.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation page demonstrates a subtle Windows bias by consistently mentioning 'IoT Edge for Linux on Windows (EFLOW)' as a primary variant, with detailed versioning and support information. While the core product is cross-platform, the prominence and repeated focus on the Windows-hosted Linux variant (EFLOW) may give the impression that Windows is the preferred or primary platform, even though the underlying runtime is Linux-based. There are no explicit PowerShell examples, Windows-only tools, or missing Linux examples, but the structure and emphasis place Windows (via EFLOW) before native Linux deployments.
Recommendations
- Balance the coverage of EFLOW and native Linux deployments by providing equivalent detail and visibility for both.
- Include a section or table summarizing native Linux distributions and their support status, similar to the EFLOW version table.
- Clarify in the introduction that IoT Edge is primarily a Linux-based solution, and EFLOW is a way to run it on Windows, rather than presenting EFLOW as a co-equal or primary deployment method.
- Ensure that future documentation and release notes provide parallel information for both native Linux and EFLOW, so that Linux users do not feel secondary.