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 126-150 of 184 flagged pages
IoT Edge
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-edge/debug-module-vs-code.md
...cs/blob/main/articles/iot-edge/debug-module-vs-code.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. Windows is frequently mentioned first when listing supported platforms and development environments. There are references to Windows-specific tools and patterns, such as IoT Edge for Linux on Windows (EFLOW), and examples include PowerShell output. Some instructions and examples are tailored to Windows users, and Linux-specific guidance is sometimes less prominent or missing. While Linux is supported and mentioned, parity in examples and tool usage could be improved.
Recommendations
- Ensure all code snippets and command outputs are shown for both Windows (PowerShell/CMD) and Linux/macOS (bash) where relevant, especially for commands like 'docker ps' and file paths.
- When listing supported platforms or development environments, alternate the order or explicitly state that all platforms are equally supported.
- Provide Linux/macOS-specific troubleshooting tips and notes alongside Windows-specific ones, especially for Docker Desktop and remote debugging.
- Avoid using Windows-specific screenshots or outputs exclusively; include Linux/macOS equivalents.
- Where Windows-only tools or patterns are mentioned (e.g., EFLOW), provide equivalent Linux-native workflows or clearly state their scope.
- Add explicit Linux/macOS setup and usage instructions for all major steps, including Docker, SSH, and Visual Studio Code extensions.
- Review all sections for implicit assumptions of Windows usage (e.g., file paths, environment variables) and provide cross-platform alternatives.
Create Pull Request
IoT Edge
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-edge/gpu-acceleration.md
...e-docs/blob/main/articles/iot-edge/gpu-acceleration.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation is heavily oriented toward Windows environments, with all setup, configuration, and deployment instructions using Windows tools (PowerShell, Device Manager, winver). There are no Linux-native examples or instructions, and the only Linux context is within a Windows-hosted VM (EFLOW). The documentation assumes Windows as the host and does not provide parity for users who might want to run similar workloads on native Linux systems or need Linux-based setup/configuration steps.
Recommendations
- Add equivalent Linux-native instructions or clarify that EFLOW is only supported on Windows hosts, and provide references for native Linux GPU acceleration with Azure IoT Edge.
- Include Linux shell (bash) command examples for tasks such as checking GPU availability, driver installation, and deployment, even if only for the guest VM.
- Mention Linux tools (e.g., lspci, nvidia-smi, glxinfo) alongside Windows tools like Device Manager and winver.
- If EFLOW is strictly a Windows-hosted solution, explicitly state this at the beginning and provide links to Linux-native Azure IoT Edge GPU acceleration documentation for users on Linux.
- Ensure that any references to driver installation or system requirements include both Windows and Linux perspectives where applicable.
IoT Edge
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-edge/how-to-access-dtpm.md
...docs/blob/main/articles/iot-edge/how-to-access-dtpm.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a strong Windows bias. All setup, configuration, and file transfer steps are described using Windows tools (PowerShell, Visual Studio, Windows file paths, and cmdlets like Copy-EflowVmFile). There are no equivalent Linux-based instructions or examples for users who may be running the host or development environment on Linux. The documentation assumes Visual Studio and NuGet usage on Windows, and all initial steps are Windows-centric, with Linux commands only appearing after the executable is copied to the EFLOW VM.
Recommendations
- Provide equivalent instructions for users developing on Linux hosts, including how to build and publish the .NET executable using the dotnet CLI.
- Offer Linux shell (bash) commands for file packaging (tar) and transfer (e.g., using scp or rsync) to the EFLOW VM, not just PowerShell and Windows cmdlets.
- Include instructions for initializing the TPM NV index from a Linux environment, if possible, or clarify if this is only possible from Windows.
- Present both Windows and Linux command examples side by side where appropriate, or clearly label which steps are Windows-only.
- Mention and link to cross-platform tools (such as VS Code, dotnet CLI) as alternatives to Visual Studio and NuGet Package Manager GUI.
IoT Edge
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-edge/how-to-authenticate-downstream-device.md
...cles/iot-edge/how-to-authenticate-downstream-device.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation demonstrates a mild Windows bias. In the X.509 self-signed authentication section, the Windows (PowerShell) openssl command is listed before the Linux (Bash) equivalent, and the Windows command is not clearly differentiated from the Linux one. The use of PowerShell syntax for openssl on Windows may confuse Linux users, and the Linux command is only shown as a variant. There are no explicit Linux-specific tools or instructions for certificate management, and the guidance for copying certificates mentions Azure Key Vault and SCP generically, without platform-specific details. There are no Linux-first or Linux-only examples, and the overall flow assumes familiarity with Windows tooling and ordering.
Recommendations
- Present Linux and Windows commands side-by-side or in parallel, rather than listing Windows first.
- Use neutral shell syntax (e.g., bash) for openssl commands, or provide both PowerShell and bash examples with clear headings.
- Include explicit Linux instructions for certificate management, such as using scp, chmod, and file permissions.
- Where tools or scripts are referenced, clarify their compatibility with both Windows and Linux, and provide platform-specific notes if needed.
- Ensure screenshots and UI instructions are not Windows-centric, or provide Linux/CLI alternatives where possible.
IoT Edge
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-edge/how-to-configure-multiple-nics.md
...in/articles/iot-edge/how-to-configure-multiple-nics.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation is heavily oriented towards Windows, with all configuration steps relying exclusively on PowerShell commands and Windows-specific tools. There are no Linux-native examples or alternative instructions for users who may wish to interact with the EFLOW VM or its networking from a Linux environment. The workflow assumes the user is operating from a Windows host, and Linux commands are only mentioned for in-VM inspection, not for configuration.
Recommendations
- Provide equivalent instructions for managing EFLOW networking from a Linux host, if supported, or clarify host OS limitations.
- Include examples using cross-platform tools (e.g., Azure CLI, SSH) where possible, not just PowerShell cmdlets.
- If PowerShell is required, mention PowerShell Core and its availability on Linux/macOS, and provide guidance for those platforms.
- Add a section explicitly addressing Linux/macOS users, outlining what is and isn't possible from those environments.
- Where only Windows is supported, clearly state this limitation at the start of the article.
IoT Edge
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-edge/how-to-connect-downstream-device.md
.../articles/iot-edge/how-to-connect-downstream-device.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation provides both Ubuntu and Windows instructions for installing certificates, but Windows instructions are consistently presented after Ubuntu. However, the Windows section is more detailed, offering multiple methods (PowerShell, certlm GUI, .NET APIs), while the Ubuntu section only covers the standard CLI method. The Windows instructions reference specific tools (PowerShell Import-Certificate, certlm, Schannel) and provide more context about the Windows TLS stack. There is no explicit omission of Linux examples, but the Windows ecosystem is described in greater depth, and more Windows-specific tooling is mentioned.
Recommendations
- Expand the Ubuntu/Linux section to include alternative certificate installation methods (e.g., using update-ca-trust on RHEL/CentOS, or using GUI tools like GNOME Certificates).
- Provide parity in troubleshooting and background information for Linux, such as mentioning OpenSSL, NSS, or GnuTLS as common TLS stacks and how they interact with the OS certificate store.
- Add examples for programmatic certificate installation on Linux (e.g., using shell scripts or with .NET APIs on Linux).
- Where Windows-specific tools are mentioned (e.g., certlm, Schannel), provide Linux equivalents (e.g., update-ca-certificates, OpenSSL) and explain their roles.
- Ensure that all language-specific SDK instructions clarify any OS-specific steps or differences, especially for .NET and C, which may behave differently on Linux vs. Windows.
IoT Edge
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-edge/tutorial-deploy-custom-vision.md
...ain/articles/iot-edge/tutorial-deploy-custom-vision.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation generally focuses on Linux container development and provides a Linux-first workflow, but there are subtle signs of Windows bias. The sample images are sourced from a repository named 'Cognitive-CustomVision-Windows', and there is no mention of a Linux-specific sample image repository. In the prerequisites, both Linux and Windows device setup links are provided, but the Windows link is listed second. However, there are no PowerShell or Windows command-line examples, and all CLI instructions use Bash syntax. The documentation does not provide explicit Linux shell alternatives for every step, and some references (such as the sample repo and image paths) are Windows-centric. There is also a lack of explicit instructions for running the workflow on a native Linux desktop (as opposed to a VM or container), and no mention of Linux-specific troubleshooting or differences.
Recommendations
- Provide sample image repositories or paths that are not Windows-specific, or clarify that the sample repo is cross-platform.
- Include explicit Linux-native instructions and troubleshooting steps, not just for containerized environments but also for common Linux distributions.
- Where sample paths or repositories are named with 'Windows', also mention or provide equivalent Linux-named resources.
- Ensure all screenshots and file path examples use cross-platform or Linux-style paths (e.g., forward slashes), or provide both styles.
- Add a section or notes about any differences or considerations when running the workflow on Windows vs. Linux hosts.
- If referencing Windows devices or tools, ensure Linux equivalents are always mentioned first and with equal detail.
IoT Edge
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-edge/quickstart.md
...s/azure-docs/blob/main/articles/iot-edge/quickstart.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation is heavily focused on Windows, specifically on deploying Azure IoT Edge for Linux on Windows (EFLOW). All device-side installation and configuration steps are provided exclusively as PowerShell commands, with no equivalent Linux-native instructions. Windows tools and patterns (e.g., Hyper-V, MSI installers, PowerShell cmdlets) are used throughout, and Linux is only referenced as the OS running inside a Windows-managed VM. Linux-native workflows, tools, or direct installation on a Linux host are not covered, and Linux command-line examples only appear after the Windows setup, for module management inside the EFLOW VM.
Recommendations
- Provide equivalent instructions for installing and configuring Azure IoT Edge directly on a native Linux device, including supported distributions and package managers.
- Include Linux shell (bash) command examples alongside or before PowerShell commands, especially for common tasks like installation, configuration, and troubleshooting.
- Mention Linux-native virtualization/containerization options (e.g., Docker, systemd) where Hyper-V or Windows-specific features are referenced.
- Clarify in the introduction that this guide is Windows-specific, and link prominently to a Linux-native quickstart for users on Linux devices.
- Balance the order of presentation so that Linux and Windows instructions are given equal prominence, or provide a platform selection tab/switcher at the top of the page.
IoT Edge
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-edge/how-to-connect-usb-devices.md
...b/main/articles/iot-edge/how-to-connect-usb-devices.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation is heavily Windows-centric, focusing almost exclusively on Windows tools (usbipd-win, PowerShell, Windows Package Manager) and workflows. All example commands are given in PowerShell, and there are no Linux command-line examples or instructions for performing similar tasks on a native Linux host. The only mention of Linux is in the context of the EFLOW VM, which is managed from Windows. Linux tools and workflows are not discussed, and Windows-specific patterns (such as using 'Add or Remove Programs', 'Services' app, and PowerShell modules) are presented without Linux equivalents.
Recommendations
- Provide equivalent Linux command-line instructions for attaching USB devices using usbip (e.g., using 'usbip' and 'usbipd' on Linux).
- Include examples of how to perform the USB/IP setup and device attachment from a Linux host, not just from Windows.
- When listing steps or tools, mention Linux-native approaches alongside Windows ones, or clarify that the instructions are Windows-only if no Linux equivalent exists.
- Add a section or note explaining how to achieve similar functionality on a pure Linux environment, or link to relevant Linux documentation.
- Balance PowerShell examples with bash or shell script examples where possible, especially for actions that can be performed inside the EFLOW VM.
IoT Edge
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-edge/troubleshoot-common-errors.md
...b/main/articles/iot-edge/troubleshoot-common-errors.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Windows Examples
Missing Linux Example
Summary
The documentation generally covers both Linux and Windows, but there are several instances of Windows bias. Windows-specific networking (NAT) is mentioned before Linux (bridge) in the runtime section, and Windows-specific error messages and patterns (e.g., hnsCall failed in Win32, Windows VM hostname length) are highlighted. Some troubleshooting steps and examples are tailored to Windows environments or Azure Portal/GUI workflows, with less emphasis on Linux CLI or configuration file methods. There are also sections where Windows tools or behaviors are discussed without equivalent Linux examples or with Linux mentioned only as an aside.
Recommendations
- Ensure Linux and Windows troubleshooting steps are presented in parallel, with equal detail and prominence.
- For every Windows-specific error or tool mentioned (e.g., NAT, hnsCall, Windows VM hostname), provide the Linux equivalent (e.g., bridge networking, relevant Linux error messages).
- Where Azure Portal or GUI steps are given, also provide CLI or configuration file alternatives for Linux users.
- Add explicit Linux examples and commands where only Windows or portal-based instructions are present.
- Review for sections where Windows is discussed first or exclusively, and restructure to present Linux and Windows options side by side or in a neutral order.
IoT Edge
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-edge/how-to-configure-proxy-support.md
...in/articles/iot-edge/how-to-configure-proxy-support.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation provides both Linux and Windows instructions, but Windows-specific details and PowerShell examples are more extensive and appear before or in greater detail than Linux equivalents in some sections. Windows tools and patterns (e.g., PowerShell, registry edits) are described in depth, while Linux instructions are sometimes more concise or refer out to external documentation. The Windows installation process is described with multiple PowerShell code blocks and parameter explanations, while Linux installation is summarized and links to external guides.
Recommendations
- Ensure Linux instructions are as detailed and self-contained as Windows instructions, including explicit command-line examples for all steps (e.g., show apt/yum/dnf proxy configuration inline, not just as a link).
- Provide Linux examples first in each section, or present both OSes in parallel to avoid a 'Windows-first' impression.
- Where Windows-specific tools (like PowerShell or registry edits) are shown, provide equivalent Linux commands (e.g., using sed, systemctl, or editing files with nano/vim) with the same level of detail.
- Include troubleshooting tips and environment variable configuration examples for both Linux and Windows, not just for Windows.
- Avoid referring to Linux instructions as 'see external documentation' when Windows instructions are inline; instead, summarize or reproduce the key steps for Linux within the doc.
- Balance the number and depth of code examples between platforms to ensure Linux users are equally supported.
IoT Edge
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-edge/troubleshoot.md
...azure-docs/blob/main/articles/iot-edge/troubleshoot.md
High Priority
View Details →
Detected Bias Types
Windows First
Cmd Examples
Missing Linux Example
Summary
The documentation is generally cross-platform, with most examples using 'bash' and 'iotedge' CLI commands that are applicable to both Linux and Windows. However, there are several instances where Windows-specific (cmd) syntax is used or presented first, such as for 'iotedge logs', 'docker rm', and 'iotedge restart'. There are no explicit PowerShell examples, but the use of 'cmd' blocks and lack of explicit Linux alternatives in some sections may confuse Linux users. Additionally, some commands (like 'docker rm') are shown only in Windows cmd syntax, and the documentation does not clarify platform differences where they may exist.
Recommendations
- For every 'cmd' example, provide a corresponding 'bash' example or clarify that the command is identical on both platforms.
- When presenting commands, avoid using 'cmd' blocks unless there is a Windows-specific syntax difference; otherwise, use 'bash' or a neutral code block.
- If there are platform-specific behaviors or prerequisites (such as service names, log file locations, or command syntax), explicitly document them for both Windows and Linux.
- Consider adding a section at the top clarifying that all commands are cross-platform unless otherwise noted, and specify any exceptions.
- Where tools or commands are platform-specific (e.g., service management), provide both Windows and Linux instructions.
IoT Edge
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-edge/tutorial-store-data-sql-server.md
...in/articles/iot-edge/tutorial-store-data-sql-server.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation is generally focused on Linux containers and development, but there are subtle Windows biases: Windows device setup is mentioned before Linux in some places, Windows tools and patterns (e.g., Visual Studio Code, .NET, C#) are used exclusively, and there are no examples for Linux-native tools or alternative workflows (e.g., using VS Code on Linux, or using non-Microsoft languages). The SQL Server module is Windows-centric, and there is no mention of Linux-native SQL tools or alternative database engines in the main workflow.
Recommendations
- When listing device setup options, mention Linux devices before Windows devices to reflect the Linux container focus.
- Provide explicit examples for using VS Code and Docker on Linux hosts (e.g., Ubuntu), including any Linux-specific commands or troubleshooting.
- Include alternative workflows using Linux-native tools (e.g., using Azure CLI or Docker CLI directly, or using editors like Vim or nano for editing files).
- Offer examples or notes for using other database engines (e.g., MySQL, PostgreSQL) in addition to SQL Server, especially since the intro mentions them.
- Clarify that the tutorial is cross-platform and provide links or notes for Linux users where steps may differ (e.g., file paths, permissions).
- Add a section or callout for common Linux troubleshooting steps (e.g., Docker permissions, SELinux/AppArmor issues).
IoT Edge
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-edge/tutorial-develop-for-linux.md
...b/main/articles/iot-edge/tutorial-develop-for-linux.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation demonstrates a Windows-first bias in several areas: it explicitly states that the tutorial uses a Windows computer, references Windows-specific features (such as Docker Desktop for Windows and Windows Subsystem for Linux), and provides Windows-style paths and commands before (or instead of) Linux equivalents. While the content claims to note differences for Linux/macOS, actual Linux-specific instructions, examples, or troubleshooting steps are often missing or less prominent. The use of PowerShell/Windows command prompts and the focus on Windows tools (e.g., Docker Desktop for Windows) further reinforce this bias.
Recommendations
- Provide parallel Linux/macOS instructions and examples wherever Windows-specific steps are given (e.g., directory creation, Docker installation, command-line usage).
- List Linux and macOS installation steps and links before or alongside Windows, not after.
- Use platform-agnostic paths (e.g., ~/dev/iotedgesolution or /home/user/dev/iotedgesolution) and commands in code snippets, or provide both Windows and Linux/macOS variants.
- Include troubleshooting steps and tips specific to Linux/macOS environments, not just Windows.
- When referencing tools like Docker Desktop, also mention and link to Linux-native alternatives (e.g., Docker Engine, Podman) and clarify their usage.
- Avoid assuming the development machine is Windows; instead, explicitly support all major platforms in instructions and examples.
- Ensure that environment variable instructions and path settings are clear for both Windows (%APPDATA%) and Linux/macOS (~/.local/), with equal prominence.
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 examples before Linux equivalents, with a strong emphasis on PowerShell commands and Windows-specific tooling (e.g., vcpkg, Set-ExecutionPolicy, Get-Pfxcertificate). Windows installation and scripting steps are more detailed, and Windows tools are referenced by name, while Linux instructions are generally shorter and rely on bash scripts. Linux parity is present, but the Windows-first ordering and PowerShell-centric approach may create friction for Linux/macOS users.
Recommendations
- Alternate the order of Windows and Linux sections, or present them side-by-side to avoid Windows-first bias.
- Provide equally detailed installation instructions for OpenSSL and prerequisites on Linux/macOS, including package manager commands (e.g., apt, yum, brew).
- Where PowerShell commands are shown (e.g., for thumbprint extraction), offer equivalent bash/openssl commands with explanations.
- Mention macOS explicitly where Linux is referenced, and clarify any differences or additional steps for macOS users.
- Consider using cross-platform scripting (e.g., Python) or provide guidance for users who may not have PowerShell available.
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
Windows Tools
Powershell Heavy
Windows First
Summary
The documentation provides both Linux and Windows instructions, but the Windows (EFLOW) sections make heavy use of PowerShell-specific cmdlets and tools (e.g., Copy-EflowVMFile, Invoke-EflowVmCommand) without Linux equivalents. Windows/PowerShell examples are given in detail, and Windows-specific tooling is referenced before or more prominently than standard Linux methods. The Linux instructions are present and generally sufficient, but Windows tooling is emphasized, and some steps (like opening ports) are shown only with PowerShell for EFLOW, not with standard Linux firewall commands.
Recommendations
- For every PowerShell/Windows-specific command, provide an equivalent Linux command or method (e.g., use scp for file copy, iptables or ufw for firewall configuration).
- When introducing tools or workflows, mention Linux-native options first or equally alongside Windows/PowerShell options.
- Add explicit Linux instructions for opening ports (e.g., iptables, ufw) in the IoT Edge section, not just in the EFLOW/Windows section.
- Clarify when steps are OS-specific and ensure parity in detail and guidance for both platforms.
- Avoid referencing Windows/PowerShell documentation or tools before Linux equivalents unless contextually necessary.
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 notable Windows bias in the deployment instructions, requiring PowerShell and providing only PowerShell-based deployment steps. There are no Linux/macOS shell examples or instructions, and the use of PowerShell is presented as the default and only option. This creates friction for Linux/macOS users who may not have PowerShell installed or prefer Bash/Zsh. The rest of the documentation is platform-neutral, but the deployment section is Windows-centric.
Recommendations
- Provide equivalent Bash shell instructions for Linux/macOS users, including how to run the deployment script using Azure CLI and shell scripts.
- Mention that PowerShell Core is available cross-platform, but clarify installation steps for Linux/macOS if PowerShell is required.
- Offer alternative deployment scripts (e.g., deploy-e2e-tutorial.sh) or document how to use Azure CLI directly for deployment.
- Explicitly state platform requirements and provide parity in tooling recommendations (e.g., show both PowerShell and Bash options).
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
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Windows Example
Summary
The documentation provides a Linux-style curl example and notes that Windows users must use Git Bash or WSL Bash, but does not offer a native Windows (PowerShell or Command Prompt) alternative. The guidance assumes Linux tooling is available, placing Windows users at a disadvantage unless they install additional shells.
Recommendations
- Provide equivalent PowerShell or Command Prompt examples for sending the HTTP POST request (e.g., using Invoke-WebRequest or similar).
- Explicitly mention how Windows users can install and use curl natively (since recent Windows versions include curl), or clarify compatibility.
- List both Linux and Windows instructions/examples side by side for parity.
- Clarify any limitations or prerequisites for Windows users up front.
IoT Edge
[Individual enrollment](#tab/individual-enrollment)
...e/includes/iot-edge-create-dps-enrollment-symmetric.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation provides a PowerShell example for deriving a device key, explicitly referencing Windows and omitting equivalent Linux/macOS instructions. No bash, OpenSSL, or Python examples are given, and the only code sample for key derivation is Windows-centric. This creates friction for Linux/macOS users who must find their own solution.
Recommendations
- Add Linux/macOS examples for device key derivation, such as using openssl, Python, or bash.
- Present cross-platform instructions side-by-side or indicate parity in tooling.
- Avoid language like 'On Windows...' unless followed by 'On Linux/macOS...' with equivalent guidance.
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
Windows First
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. File path examples use Windows-style backslashes. There is no guidance for Linux/macOS users regarding equivalent tooling or commands, and Windows tools/scripts are referenced without cross-platform notes.
Recommendations
- Provide equivalent Linux/macOS command-line instructions for certificate verification, e.g., using OpenSSL or bash scripts.
- Include Linux/macOS file path examples (forward slashes) alongside Windows paths.
- Mention cross-platform compatibility of scripts/tools, or link to platform-specific instructions.
- Clarify whether the referenced verification tool (New-CACertsVerificationCert) is available or supported on Linux/macOS, and if not, offer alternatives.
- When referencing scripts or tools, specify OS requirements and provide parity where possible.
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 demonstrates a moderate Windows bias. Windows is presented as the default development environment, with Windows-specific instructions and links (e.g., Docker Desktop for Windows, nested virtualization on Windows, PowerShell/command prompt references) appearing before Linux/macOS equivalents. Some examples use Windows-style paths (e.g., c:\dev\iotedgesolution), and environment variable instructions reference Windows locations first. While Linux and macOS are acknowledged and supported, Linux-specific instructions are often secondary, and there are few explicit Linux command-line examples or troubleshooting steps. The overall flow assumes familiarity with Windows tools and patterns, which may create friction for Linux/macOS users.
Recommendations
- Provide Linux/macOS examples and instructions alongside Windows ones, not after or as notes.
- Use platform-agnostic file paths and environment variable references in code samples.
- Explicitly show Linux shell commands (e.g., bash) for all steps, including directory creation and Docker usage.
- Include troubleshooting steps and tips for Linux/macOS environments, not just Windows.
- Mention Linux container engines (e.g., Podman) as alternatives to Docker Desktop.
- Ensure all environment variable instructions include both Windows and Linux/macOS formats.
- Add a section or callouts for common Linux/macOS issues (permissions, package installation, etc.).
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias by consistently referencing Windows as a primary platform, especially in the context of running IoT Edge via 'IoT Edge for Linux on Windows' (EFLOW). Windows is mentioned first in several key sections, and the recommended pattern for Windows is to use a Linux VM (EFLOW), which is a Microsoft-specific solution. There is no evidence of missing Linux examples or PowerShell-heavy instructions, but the documentation does prioritize Windows compatibility and tooling in its explanations.
Recommendations
- Present Linux and Windows platforms with equal prominence, listing Linux options first where appropriate.
- Provide more details and examples for native Linux deployments, not just Linux-on-Windows scenarios.
- Clarify that EFLOW is a workaround for Windows users rather than the default or preferred deployment method.
- Include explicit instructions or links for Linux troubleshooting and support channels, matching the detail given for Windows/EFLOW.
- Avoid language that positions Windows as the default or recommended platform unless justified by technical reasons.
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 Windows bias primarily through the use of Windows-style paths (e.g., <WRKDIR>\certs\...), and by providing a PowerShell-only example for certificate verification (New-CACertsVerificationCert). There are no equivalent Linux/macOS shell commands or instructions, nor are Linux-style paths shown. The verification tool is referenced but only demonstrated with PowerShell, leaving Linux/macOS users without clear guidance.
Recommendations
- Include Linux/macOS shell command examples (e.g., bash) for certificate verification alongside PowerShell.
- Show Linux-style paths (e.g., <WRKDIR>/certs/...) wherever Windows paths are mentioned.
- Clarify whether the verification tool can be run on Linux/macOS, and provide installation and usage instructions for those platforms.
- Explicitly mention cross-platform compatibility of scripts and tools, or provide alternatives if some are Windows-only.
IoT Edge
Connect a downstream device to an Azure IoT Edge gateway
.../articles/iot-edge/how-to-connect-downstream-device.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation provides both Ubuntu (Linux) and Windows instructions for installing CA certificates, but Windows examples are more detailed, listing multiple methods (PowerShell, GUI, .NET API) and referencing Windows-specific tools (Schannel, certlm). Windows tooling and patterns are described in greater depth, while Linux instructions are limited to a brief Ubuntu example. The order of presentation also places Ubuntu before Windows, but Windows instructions are more comprehensive. There is no explicit omission of Linux examples for SDK usage, but Windows-specific TLS stack (Schannel) is discussed in detail.
Recommendations
- Expand Linux instructions to include other distributions (e.g., CentOS, RHEL) and provide equivalent detail for installing certificates via CLI and GUI.
- Describe Linux TLS stack usage (e.g., OpenSSL, GnuTLS) in parity with the Windows Schannel explanation.
- Provide .NET/Linux-specific guidance for programmatic certificate installation, similar to the Windows/.NET API example.
- Include troubleshooting steps specific to Linux environments (e.g., SELinux, permissions, systemd trust store reload).
- Mention cross-platform certificate management tools (e.g., certutil, update-ca-trust) where applicable.
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 and registry editing instructions for Windows, while Linux instructions are more generic and refer to external documentation for package manager and Docker configuration. Windows-specific tools and patterns (e.g., PowerShell commands, registry edits) are described in detail, and Windows installation instructions are presented before Linux in some sections. Linux examples are present but less detailed, and Linux users are sometimes directed to external resources rather than given explicit commands.
Recommendations
- Provide equally detailed, step-by-step Linux instructions for all major tasks, including explicit shell commands for installation and configuration.
- Include Linux examples for proxy credential handling, similar to the Windows PowerShell example with -ProxyCredential.
- Ensure Linux instructions are presented before or alongside Windows instructions, especially in sections relevant to both platforms.
- Avoid referring Linux users to external documentation for critical steps; include the necessary commands and configuration snippets directly.
- Add troubleshooting steps and verification commands for Linux users, matching the detail given to Windows users.