IoT Edge
188
Total Pages
169
Linux-Friendly Pages
19
Pages with Bias
10.1%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
38 issues found
Showing 26-38 of 38 flagged pages
IoT Edge
Configure devices for network proxies for Azure IoT Edge
...in/articles/iot-edge/how-to-configure-proxy-support.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation provides detailed, step-by-step PowerShell examples for Windows installation and configuration, including registry edits and credential handling, while Linux instructions are more generic and refer out to external resources. Windows-specific tools and patterns (PowerShell, registry edits) are described in detail, and Windows installation steps are presented before Linux in some sections. Linux instructions rely on links or brief command snippets, with less emphasis on troubleshooting or advanced scenarios.
Recommendations
- Provide equally detailed, step-by-step Linux installation and configuration instructions, including troubleshooting and credential handling.
- Include Linux examples for complex proxy scenarios (e.g., authenticated proxies) similar to the Windows PowerShell credential example.
- Present Linux and Windows instructions in parallel or in separate, clearly labeled sections to avoid Windows-first ordering.
- Expand Linux-specific guidance for certificate management and proxy configuration, matching the depth of Windows coverage.
- Add explicit Linux troubleshooting steps for common proxy issues.
Create Pull Request
IoT Edge
Create test certificates - Azure IoT Edge
...n/articles/iot-edge/how-to-create-test-certificates.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation consistently presents Windows instructions and PowerShell examples before Linux equivalents, and relies heavily on Windows-specific tools and patterns (e.g., vcpkg, PowerShell cmdlets like Set-ExecutionPolicy and Get-Pfxcertificate). While Linux instructions are present and generally complete, Windows users are prioritized in ordering and tool recommendations, and some PowerShell-specific commands (e.g., thumbprint extraction) are more straightforward than their Linux counterparts.
Recommendations
- Alternate the order of Windows and Linux sections, or present both side-by-side to avoid implicit prioritization.
- Provide Linux installation instructions for OpenSSL with equal detail as Windows (e.g., package manager commands for apt, yum, etc.).
- Where PowerShell commands are given for certificate management (e.g., thumbprint extraction), provide equally simple Linux/bash alternatives, possibly with helper scripts.
- Avoid recommending Windows-only tools (like vcpkg) without mentioning Linux equivalents (e.g., apt, yum, dnf, or source compilation).
- Clarify any differences in script capabilities or limitations between platforms, and ensure parity in functionality.
IoT Edge
Create transparent gateway device using Azure IoT Edge
...articles/iot-edge/how-to-create-transparent-gateway.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation provides both Linux and Windows instructions, but the Windows (EFLOW) sections rely heavily on PowerShell-specific cmdlets and tools, such as Copy-EflowVMFile and Invoke-EflowVmCommand, which have no direct Linux equivalents. Windows/PowerShell examples are detailed and use custom Azure cmdlets, while Linux instructions use standard bash commands. In some sections, Windows-specific tooling is referenced before Linux alternatives, and the EFLOW workflow is more tool-driven, potentially making the Windows experience appear more streamlined.
Recommendations
- Provide equivalent Linux tooling or scripts for certificate copying and port management, such as using scp or rsync for file transfer and standard iptables/bash for port opening.
- Ensure Linux instructions are as detailed and streamlined as Windows/PowerShell examples, including troubleshooting tips and automation suggestions.
- Where possible, present Linux and Windows instructions side-by-side, or alternate which platform is presented first.
- Clarify that PowerShell cmdlets are Windows-specific and offer alternative approaches for Linux users.
- Add explicit notes or links for Linux users on how to perform similar tasks without custom Azure cmdlets.
IoT Edge
How to implement IoT Edge observability using monitoring and troubleshooting
...cs/blob/main/articles/iot-edge/how-to-observability.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias in the deployment instructions for the sample scenario. Only PowerShell is mentioned and used for deployment, with no Linux/macOS shell or Bash alternatives provided. The instructions explicitly tell users to open a PowerShell console and run a PowerShell script, without acknowledging or supporting Linux-native workflows. This creates friction for Linux/macOS users who may not have PowerShell installed or prefer Bash. The rest of the documentation is platform-neutral, but the critical deployment step is Windows-centric.
Recommendations
- Provide equivalent Bash shell instructions for Linux/macOS users, such as a .sh deployment script.
- Explicitly mention Linux/macOS compatibility and required tools (e.g., Azure CLI, Bash, PowerShell Core).
- If PowerShell is required, clarify that PowerShell Core is cross-platform and provide installation instructions for Linux/macOS.
- Offer troubleshooting tips for Linux/macOS users who may encounter issues running PowerShell scripts.
- Consider restructuring deployment instructions to present Bash and PowerShell options side-by-side.
IoT Edge
[Individual enrollment](#tab/individual-enrollment)
...t-edge/includes/iot-edge-create-dps-enrollment-x509.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. The only explicit command-line example for certificate verification uses a PowerShell cmdlet (New-CACertsVerificationCert), with no mention of Linux/macOS alternatives or cross-platform tooling. File path examples use Windows-style backslashes, and there is no guidance for Linux users on equivalent commands or scripts. The documentation assumes familiarity with Windows tools and does not provide parity for Linux/macOS users in critical steps like certificate verification.
Recommendations
- Provide equivalent Linux/macOS command-line instructions for certificate verification, such as using OpenSSL or cross-platform scripts.
- Mention and show Linux-style file paths (forward slashes) alongside Windows paths.
- Clarify whether the IoT Edge verification tool is cross-platform, and if so, provide usage examples for bash/zsh.
- Explicitly state platform requirements for any scripts or tools referenced.
- Add notes or links to Linux/macOS-specific guidance where applicable.
IoT Edge
Develop and debug Azure IoT Edge modules using Visual Studio
...ticles/iot-edge/how-to-visual-studio-develop-module.md
Medium 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 assumes the development machine is Windows, provides Windows-specific instructions and paths, and prioritizes Visual Studio (a Windows-centric IDE) and Windows tools like vcpkg and batch scripts. Linux development is mentioned only as an option for container targets, not as a host environment, and Linux-specific instructions (e.g., for vcpkg, Docker, or project setup) are missing or secondary. Most examples, screenshots, and step-by-step guides are tailored to Windows users, with Linux alternatives either omitted or referenced only in passing.
Recommendations
- Add explicit instructions for setting up the development environment on Linux (and macOS), including Visual Studio alternatives (e.g., VS Code) and Linux-specific package manager commands.
- Provide Linux shell equivalents for all Windows command-line examples (e.g., vcpkg bootstrap, Docker commands, file paths).
- Include Linux file paths and template installation steps alongside Windows paths.
- Clarify which steps are cross-platform and which are Windows-only, and offer parity for Linux/macOS users wherever possible.
- Add screenshots and workflow examples for Linux-based development, including debugging and deployment.
- Rephrase prerequisites to not assume Windows as the default development OS.
IoT Edge
Develop Azure IoT Edge modules using Visual Studio Code tutorial
...b/main/articles/iot-edge/tutorial-develop-for-linux.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page exhibits a moderate Windows bias. Windows is consistently mentioned first as the development environment, and Windows-specific tools and patterns (such as Docker Desktop for Windows, PowerShell, and Windows paths) are referenced before their Linux/macOS equivalents. Many code and setup examples use Windows paths (e.g., c:\dev\iotedgesolution), and guidance for nested virtualization links to Windows documentation. While Linux and macOS are acknowledged, and Linux-targeted development is supported, Linux-specific instructions and troubleshooting are less prominent, and some steps (e.g., Docker installation, environment variable setup) are described in a Windows-centric manner.
Recommendations
- Present Linux/macOS instructions and examples before or alongside Windows ones, especially in setup and prerequisites.
- Provide Linux/macOS paths and shell commands in all code examples, not just Windows (e.g., use ~/dev/iotedgesolution and bash commands).
- Link to Linux/macOS documentation for virtualization and Docker installation with equal prominence.
- Include troubleshooting steps and tips specific to Linux/macOS environments.
- Avoid referencing PowerShell or Windows command prompt as the default terminal; mention bash/zsh and Terminal for Linux/macOS.
- Ensure all environment variable setup instructions are clear for Linux/macOS users (e.g., ~/.bashrc, ~/.profile).
IoT Edge
Authenticate downstream devices - Azure IoT Edge
...cles/iot-edge/how-to-authenticate-downstream-device.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation shows minor Windows bias in the X.509 self-signed authentication section, where the openssl command is presented first for Windows/PowerShell, followed by the Linux version. The Windows command is labeled explicitly, and the Linux command is shown as an alternative. No exclusive use of Windows tools or missing Linux examples are present, and Azure CLI is used for cross-platform operations.
Recommendations
- Present Linux and Windows command examples side-by-side or in a tabbed format to emphasize parity.
- Avoid labeling Windows examples first unless there is a technical reason; consider listing Linux first or both equally.
- Where possible, use generic commands that work on both platforms, or clarify platform-specific differences.
- Explicitly mention macOS compatibility if relevant, or provide macOS-specific notes if commands differ.
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 First
Missing Linux Example
Summary
The documentation provides instructions for running a curl command in the Visual Studio Code integrated terminal, with a note specifically addressing Windows users and recommending Git Bash or WSL Bash. There is no explicit mention of Linux or macOS users, nor are there examples or guidance tailored to those platforms. The focus on Windows shells and lack of Linux/macOS instructions suggests a mild Windows-first bias.
Recommendations
- Explicitly mention that the curl command works natively on Linux and macOS terminals.
- Add a note for Linux/macOS users confirming that no special shell configuration is needed.
- Provide parity in troubleshooting tips for Linux/macOS users, if applicable.
- Consider listing Linux/macOS instructions before or alongside Windows-specific notes.
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation page demonstrates a mild Windows bias by consistently referencing Windows-specific tooling (such as 'IoT Edge for Linux on Windows' and 'Azure IoT EFLOW') and placing Windows platforms prominently in Tier 1 support tables, sometimes before or alongside Linux equivalents. Windows support channels and prerequisites are highlighted, and Windows virtualization technologies (Hyper-V) are mentioned explicitly. However, Linux distributions are well represented, and there are no critical sections that exclude Linux/macOS users or provide only Windows/Powershell examples.
Recommendations
- Ensure Linux examples and tools are mentioned with equal prominence and detail as Windows equivalents.
- When listing supported platforms, consider listing Linux distributions first or in a neutral order.
- Provide explicit support channels and troubleshooting guidance for Linux users, not just for 'Linux on Windows'.
- Clarify virtualization support for Linux-based hypervisors (e.g., KVM, Xen) alongside Hyper-V and vSphere.
- Avoid language that implies Windows is the default or recommended platform unless justified by technical reasons.
IoT Edge
Authenticate downstream devices - Azure IoT Edge
...cles/iot-edge/how-to-authenticate-downstream-device.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation shows a mild Windows bias in the X.509 self-signed authentication section, where the openssl command is presented first for Windows (PowerShell) and then for Linux (Bash). The Windows command is given without modification, while the Linux command includes a sed pipeline to remove colons, suggesting a slightly less straightforward experience for Linux users. No other sections show exclusive use of Windows tools or missing Linux examples, and the CLI instructions are cross-platform.
Recommendations
- Present openssl commands for Linux and Windows in parallel, with equal prominence.
- Clarify that openssl is available on both platforms and provide installation instructions for both if needed.
- Where post-processing (like sed) is required, explain why and offer equivalent Windows solutions if applicable.
- Consider showing Linux examples first or side-by-side to avoid implicit prioritization of Windows.
- Explicitly mention that the Azure CLI and IoT CLI extension are cross-platform.
IoT Edge
Connect a downstream device to an Azure IoT Edge gateway
.../articles/iot-edge/how-to-connect-downstream-device.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation provides both Ubuntu and Windows instructions for installing CA certificates, but Windows examples are more detailed, listing multiple approaches (PowerShell, certlm utility, .NET APIs) and explaining the Windows TLS stack (Schannel) in depth. Windows tooling (PowerShell, certlm) is mentioned by name, while the Ubuntu section is limited to two shell commands. In SDK sections, Windows-specific details (Schannel, certificate store) are discussed before Linux equivalents (OpenSSL, WolfSSL), and Windows is referenced more frequently. However, Linux/macOS users are not blocked from completing the task, as Linux instructions and cross-platform SDK usage are included.
Recommendations
- Expand Linux/macOS instructions to match the detail provided for Windows, e.g., include GUI-based certificate installation steps for Ubuntu (using 'Settings' or 'Certificates' app), and mention macOS certificate store installation (Keychain Access).
- List Linux/macOS instructions before or alongside Windows instructions to avoid 'windows_first' ordering.
- Discuss Linux TLS stack options (OpenSSL, LibreSSL) in equal detail to Schannel, including troubleshooting tips for common Linux certificate issues.
- Explicitly mention macOS support and provide relevant commands/examples.
- Where Windows tools are named (PowerShell, certlm), mention Linux/macOS equivalents (e.g., update-ca-certificates, Keychain Access) by name.
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation page is generally balanced in listing supported platforms, with Linux distributions featured prominently and in detail. However, there is a subtle Windows bias: Windows support is described primarily via 'IoT Edge for Linux on Windows' (EFLOW), and Windows is often mentioned first when discussing how to run IoT Edge on Windows devices. The documentation refers to Windows-specific tooling (EFLOW) and links to Windows prerequisites before Linux equivalents. There are no Linux-specific examples or tooling highlighted, but Linux platforms are well represented in support tables.
Recommendations
- Present Linux and Windows options with equal prominence, avoiding language that suggests Windows is the default or preferred platform.
- When mentioning EFLOW or Windows-specific solutions, also highlight native Linux installation and management options in parallel.
- Add explicit references to Linux management tools and patterns (e.g., systemd, package managers) where appropriate.
- Ensure that links to prerequisites and installation guides for Linux are as visible and accessible as those for Windows.
- If examples or troubleshooting steps are added in future, ensure parity between Linux and Windows instructions.