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 76-100 of 184 flagged pages
IoT Edge https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-edge/how-to-create-transparent-gateway.md ...articles/iot-edge/how-to-create-transparent-gateway.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation provides both Linux and Windows instructions, but Windows-specific tools (PowerShell cmdlets) are featured prominently for EFLOW scenarios. Windows/PowerShell examples are given for file transfer and port opening, while Linux equivalents (e.g., scp, firewall-cmd, ufw) are not mentioned. The EFLOW (Windows) workflow relies on custom PowerShell commands, and these are described in detail, whereas Linux instructions use standard bash commands. There is a slight ordering bias, with Windows/EFLOW instructions sometimes appearing before or more extensively than Linux equivalents.
Recommendations
  • For every PowerShell/Windows-specific command (e.g., Copy-EflowVMFile, Invoke-EflowVmCommand), provide the equivalent Linux command (e.g., scp for file transfer, firewall-cmd or ufw for opening ports) in the Linux section.
  • Explicitly mention cross-platform alternatives for file transfer and firewall configuration, not just Windows/PowerShell tools.
  • Ensure that Linux instructions are as detailed as Windows ones, including troubleshooting tips and references.
  • Where possible, avoid introducing Windows/PowerShell tools before Linux equivalents, or present both side-by-side.
  • Add a summary table or section comparing Linux and Windows workflows for common tasks.
GitHub Create Pull Request
IoT Edge https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-edge/how-to-observability.md ...cs/blob/main/articles/iot-edge/how-to-observability.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates Windows bias primarily in the deployment instructions, where only PowerShell is mentioned and used for running the deployment script. The instructions explicitly direct users to open a PowerShell console and run a PowerShell script, without providing equivalent Linux shell (bash) instructions or mentioning cross-platform alternatives. The prerequisites list PowerShell before Azure CLI, and there is no mention of Linux-specific tools or steps. No Linux or bash examples are provided for deployment, and the documentation implicitly assumes a Windows environment for setup and execution.
Recommendations
  • Provide Linux/bash deployment instructions alongside PowerShell, e.g., include a bash script or show how to run the deployment using Azure CLI commands in a Linux terminal.
  • Explicitly mention that the solution can be deployed from Linux or macOS, and list any prerequisites or differences for those platforms.
  • If the deployment script is PowerShell-only, offer a cross-platform version (e.g., bash or Python), or document how to install and use PowerShell Core on Linux/macOS.
  • Reorder the prerequisites to list Azure CLI first, as it is cross-platform, and clarify the role of each tool for different operating systems.
  • Add troubleshooting and monitoring examples that use Linux-native tools (e.g., journalctl, systemd, bash commands) where applicable, especially for IoT Edge device diagnostics.
GitHub Create Pull Request
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 →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a strong Windows bias. All setup, configuration, and file transfer instructions are given using Windows tools (Visual Studio, PowerShell, Windows directories), and Windows-specific cmdlets (Set-EflowVmFeature, Copy-EflowVmFile, Connect-EflowVm) are used exclusively. There are no Linux-native examples for equivalent workflows, and the prerequisites and instructions assume the user is operating from a Windows environment. Linux alternatives for development, file transfer, and TPM initialization are not mentioned.
Recommendations
  • Provide equivalent instructions for users working from a Linux host, including how to enable TPM passthrough and initialize NV indexes using Linux tools.
  • Include Linux-native development workflow examples, such as using VS Code or command-line .NET tools, and NuGet package installation via CLI.
  • Offer file transfer alternatives (e.g., scp, rsync, SFTP) for copying files to the EFLOW VM from Linux.
  • Document how to connect to the EFLOW VM from Linux (e.g., SSH) and perform necessary operations without PowerShell.
  • Clarify which steps are Windows-only and which can be performed from Linux, and provide parity where possible.
GitHub Create Pull Request
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 →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
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, including advanced credential handling. Windows installation steps are described in greater detail and appear before or in more depth than Linux equivalents. Windows-specific tools and patterns (PowerShell, registry edits) are highlighted, while Linux instructions are more generic and refer out to external documentation for details. Linux examples are present but less detailed, and some advanced scenarios (like credential handling) are only covered for Windows.
Recommendations
  • Provide equally detailed, step-by-step Linux installation instructions, including handling proxy credentials with apt/yum and environment variables.
  • Include Linux-specific advanced scenarios, such as configuring proxies with authentication for apt/yum and Docker, and troubleshooting common Linux proxy issues.
  • Offer direct Linux command-line examples for all steps where Windows PowerShell is shown (e.g., downloading scripts, restarting services, verifying environment variables).
  • Balance the order of presentation so that Linux and Windows instructions are given equal prominence, or group them together for each step.
  • Avoid referring out to external documentation for Linux steps when Windows steps are fully documented inline; include the key Linux commands and configuration snippets directly.
GitHub Create Pull Request
IoT Edge https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-edge/includes/iot-edge-create-dps-enrollment-symmetric.md ...e/includes/iot-edge-create-dps-enrollment-symmetric.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides a PowerShell-only example for deriving a device key, explicitly referencing Windows and omitting equivalent Linux or cross-platform instructions. Windows tooling and patterns are mentioned exclusively, with no parity for Linux users. The example and sample output are both in PowerShell, reinforcing a Windows-centric approach.
Recommendations
  • Add equivalent Linux instructions using common tools such as openssl, bash, or Python for deriving the device key.
  • Include cross-platform code samples (e.g., Python) that work on both Windows and Linux.
  • Explicitly mention that the steps are applicable on both Windows and Linux, or provide tabs/switches for OS-specific instructions.
  • Avoid language such as 'On Windows' unless there is a corresponding 'On Linux' section.
  • Provide sample outputs for Linux commands as well.
GitHub Create Pull Request
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 →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation is heavily oriented toward Windows, with all installation and usage instructions focused on Windows tools (usbipd-win, PowerShell, winget, Services app, firewall rules). All example commands are given in PowerShell, and there are no Linux-side command examples or instructions for using usbip from the Linux VM directly. The Linux perspective is only briefly mentioned, and Linux-native workflows or troubleshooting are not covered.
Recommendations
  • Add explicit instructions and examples for using usbip on the Linux VM, including installation, listing devices, and attaching/detaching devices from the Linux side.
  • Provide Linux shell (bash) command equivalents for each PowerShell example, especially for device attachment and verification.
  • Include troubleshooting steps and tips for common Linux issues (e.g., driver compatibility, permissions, service status).
  • Present Windows and Linux steps in parallel, or clearly separate them, to avoid Windows-first bias.
  • Reference Linux documentation and tools (e.g., usbip, lsusb, systemctl) alongside Windows tools.
  • Clarify which steps are performed on the Windows host and which on the Linux VM, and ensure Linux users have parity in instructions.
GitHub Create Pull Request
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 →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation is heavily biased towards Windows, with all configuration steps relying on PowerShell commands and Windows-specific tools. There are no Linux-native examples or instructions, and the workflow assumes the user is operating from a Windows environment. Even when interacting with the Linux VM, access is provided via Windows PowerShell, and Linux commands are only briefly mentioned for verification inside the VM.
Recommendations
  • Provide equivalent Linux-native instructions for managing EFLOW networking, such as using Azure CLI, SSH, or Hyper-V Manager from a Linux host.
  • Include examples of how to configure multiple NICs for EFLOW from a Linux environment, if supported.
  • Document any limitations or differences when managing EFLOW networking from Linux versus Windows.
  • Ensure that Linux tools and workflows are mentioned alongside Windows/PowerShell methods, not only as verification steps inside the VM.
  • Clarify which steps are Windows-only and which can be performed from Linux, to help users on non-Windows platforms.
GitHub Create Pull Request
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 →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation provides both Ubuntu (Linux) and Windows instructions for installing CA certificates, but Windows tools (PowerShell, certlm, .NET APIs, Schannel) are described in greater detail, with multiple methods and explanations. Windows-specific terminology and tools (Schannel, certlm, PowerShell) are mentioned before or more extensively than their Linux equivalents. In SDK sections, Windows behaviors (e.g., Schannel usage) are highlighted, while Linux alternatives (e.g., OpenSSL) are mentioned but not explained in depth. Some SDK instructions assume Windows defaults, and troubleshooting steps reference host file edits and DNS, which may be more familiar to Windows users. There are no explicit examples for other Linux distributions besides Ubuntu, and macOS is not mentioned.
Recommendations
  • Provide equivalent certificate installation instructions for other popular Linux distributions (e.g., CentOS, Red Hat, Debian) and for macOS.
  • Expand explanations of Linux TLS stacks (e.g., OpenSSL, LibreSSL) and how to configure them for IoT Edge, similar to the detail given for Schannel on Windows.
  • Offer Linux command-line alternatives for all Windows GUI and PowerShell steps (e.g., using update-ca-certificates, keytool for Java, etc.).
  • Ensure troubleshooting steps include Linux-specific advice (e.g., editing /etc/hosts, checking iptables/firewalld, using systemd-resolved).
  • Balance the order and depth of Windows and Linux instructions so that Linux users receive as much guidance as Windows users.
  • Explicitly mention cross-platform considerations for SDKs, including any differences in certificate handling between Windows, Linux, and macOS.
GitHub Create Pull Request
IoT Edge https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-edge/how-to-create-test-certificates.md ...n/articles/iot-edge/how-to-create-test-certificates.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation consistently presents Windows instructions and PowerShell examples before Linux/bash equivalents, and uses Windows-specific tools and commands (e.g., PowerShell cmdlets, vcpkg, Set-ExecutionPolicy, Write-Host, Get-Pfxcertificate) without always providing direct Linux analogs or explanations. This ordering and tool selection may make Linux users feel like second-class citizens and can hinder parity in understanding and usability.
Recommendations
  • Alternate the order of Windows and Linux sections, or present both side-by-side where possible to avoid always privileging Windows.
  • Where Windows-specific tools or commands are used (e.g., PowerShell cmdlets), provide clear Linux/bash equivalents or explanations.
  • Avoid using Windows-only tools (such as vcpkg or Set-ExecutionPolicy) as the default or 'recommended' path; if mentioned, provide equally detailed Linux alternatives (e.g., apt, yum, or source builds for OpenSSL).
  • Where possible, use cross-platform tools and commands, or clearly indicate when a step is platform-specific.
  • Ensure that all steps, especially for prerequisites and environment setup, are equally detailed for both Windows and Linux.
  • Consider including a summary table or section at the start that highlights parity and differences between platforms, so users can quickly find their relevant instructions.
GitHub Create Pull Request
IoT Edge https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-edge/includes/iot-edge-create-dps-enrollment-x509.md ...t-edge/includes/iot-edge-create-dps-enrollment-x509.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates Windows bias by providing only PowerShell-based certificate verification examples (e.g., New-CACertsVerificationCert), referencing Windows-style file paths (e.g., <WRKDIR>), and omitting equivalent Linux or cross-platform command-line instructions. There is no mention of Linux tools (such as OpenSSL or Bash scripts) for certificate handling, and Windows-centric patterns appear before or instead of Linux alternatives.
Recommendations
  • Provide Linux and macOS equivalents for all PowerShell commands, such as OpenSSL or Bash script examples for certificate verification.
  • Use platform-neutral file path notation or show both Windows and Linux path formats in examples.
  • Explicitly mention cross-platform tooling (e.g., Azure CLI, OpenSSL) and provide step-by-step instructions for both Windows and Linux environments.
  • Add tabs or sections for Linux-specific instructions wherever Windows-specific tools or commands are referenced.
  • Ensure that references to scripts or verification tools clarify their compatibility with Linux and provide installation or usage notes for non-Windows platforms.
GitHub Create Pull Request
IoT Edge https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-edge/how-to-create-virtual-switch.md ...main/articles/iot-edge/how-to-create-virtual-switch.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation is heavily focused on Windows environments, specifically guiding users through PowerShell commands and Windows-native tools (Hyper-V, Windows DHCP Server). All examples and instructions are for Windows, with no Linux equivalents or cross-platform alternatives provided, despite the product being 'Azure IoT Edge for Linux on Windows'. Linux tools, commands, or patterns are not mentioned, and the workflow assumes a Windows host throughout.
Recommendations
  • Add equivalent instructions for setting up virtual switches, NAT, and DHCP on Linux hosts using common Linux tools (e.g., ip, brctl, dnsmasq, isc-dhcp-server).
  • Provide cross-platform examples or clarify that the guide is only for Windows hosts, and link to Linux-specific guides if available.
  • Include a section comparing Windows and Linux approaches, highlighting differences and similarities.
  • Where possible, use generic terminology and avoid assuming PowerShell or Windows-only workflows.
  • If the product is only supported on Windows hosts, make this limitation explicit at the beginning of the documentation.
GitHub Create Pull Request
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 →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation exhibits a Windows-first bias in several areas. The tutorial explicitly states that it uses a Windows computer for examples, with Linux/macOS differences only occasionally noted. Windows-specific tools and patterns (e.g., Docker Desktop for Windows, Windows paths in CLI examples, references to PowerShell/Command Prompt, and links to Windows virtualization documentation) are mentioned before or more prominently than their Linux equivalents. Some commands and environment variable instructions use Windows conventions first or exclusively, and Linux-specific setup steps are less detailed or deferred to external links. There is limited direct guidance for Linux users, and Linux tools or workflows are not presented with equal prominence.
Recommendations
  • Provide parallel, equally detailed Linux and macOS instructions and examples throughout the tutorial, not just as side notes or external links.
  • Use neutral language and paths in CLI examples (e.g., use $HOME/dev/iotedgesolution or ~/dev/iotedgesolution alongside c:\dev\iotedgesolution).
  • Include Linux-first sections or pivots, especially for container engine installation, environment variable setup, and CLI usage.
  • Add explicit Linux shell commands (bash/zsh) and troubleshooting steps for common Linux issues (e.g., permissions, Docker group membership).
  • Reference Linux documentation and patterns before or alongside Windows equivalents, especially for virtualization, Docker installation, and environment variables.
  • Ensure all environment variable and path instructions include both Windows and Linux/macOS formats.
  • Highlight Linux-native tools (e.g., Podman, Docker CE, systemd) where appropriate, not just Docker Desktop for Windows.
  • Make it clear that the tutorial is equally applicable to Linux/macOS development environments, not just Windows.
GitHub Create Pull Request
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
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Windows Heavy Messaging
Summary
The documentation page demonstrates a moderate Windows bias. Windows is frequently mentioned as a primary platform, with 'IoT Edge for Linux on Windows' recommended as the way to run IoT Edge on Windows devices. Windows-specific tooling (EFLOW) and support channels are highlighted, and Windows appears before or alongside Linux in several tables and sections. There is repeated emphasis on Windows compatibility and migration, while Linux instructions and tooling are less foregrounded. No explicit Linux command-line examples or Linux-first guidance are present.
Recommendations
  • Add Linux-specific troubleshooting and support channels, similar to the EFLOW Windows links.
  • Provide Linux-first installation and usage examples, including command-line instructions for popular distributions.
  • Balance messaging so that Linux is presented as the primary or co-primary platform, especially in introductory and recommendation sections.
  • Include explicit guidance for Linux-native deployments, not just Linux-on-Windows scenarios.
  • Highlight Linux container engine management and update patterns, not just moby-engine recommendations.
  • Ensure parity in documentation for both Linux and Windows, including examples, screenshots, and links.
GitHub Create Pull Request
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 →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits a strong Windows bias. All device setup and deployment instructions are exclusively for Windows environments, specifically using PowerShell and Windows-specific tools (e.g., Hyper-V, MSI installers, PowerShell cmdlets). There are no instructions or examples for setting up IoT Edge on native Linux devices, nor are Linux equivalents (e.g., bash scripts, Linux package managers) mentioned. The page assumes the user is working from a Windows device and only provides Linux commands after the device is provisioned, not for initial setup or installation.
Recommendations
  • Add parallel instructions for setting up Azure IoT Edge on native Linux devices, including prerequisites, installation, and provisioning steps using bash and Linux package managers (apt, yum, etc.).
  • Provide Linux-specific examples for device setup, such as enabling virtualization (KVM), downloading and installing IoT Edge packages, and configuring the runtime.
  • Ensure that Linux instructions are presented alongside Windows instructions, or in a separate section, rather than only after Windows setup is complete.
  • Reference Linux tools and patterns (e.g., SSH, systemctl, shell scripts) where appropriate, and avoid assuming PowerShell is the only remote management solution.
  • Clarify in the introduction that the quickstart is Windows-specific, and link to equivalent Linux quickstart guides if available.
GitHub Create Pull Request
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 →
Scanned: 2025-08-17 00:01
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. Windows is often mentioned first when describing development environments and requirements. There are several references to Windows-specific tools and workflows, such as IoT Edge for Linux on Windows (EFLOW), and some example outputs (e.g., docker ps) are shown in PowerShell format. While Linux is supported and mentioned, Linux-specific instructions, troubleshooting, or examples are less prominent, and there are few, if any, explicit Linux shell or terminal examples. Some sections (e.g., Docker context, remote debugging) use Windows-centric paths or screenshots. There is a lack of explicit parity in examples and troubleshooting for Linux users.
Recommendations
  • Ensure that all example commands and outputs are shown in both Windows (PowerShell/CMD) and Linux (bash) formats where appropriate.
  • When listing supported platforms or prerequisites, alternate the order of Windows and Linux, or mention Linux first in some sections.
  • Provide explicit Linux shell/terminal examples and troubleshooting steps, especially for Docker and SSH-related workflows.
  • Include Linux-specific notes, such as file paths, permissions, and common issues (e.g., Docker group membership, SELinux/AppArmor).
  • Add screenshots or terminal outputs from Linux environments alongside Windows examples.
  • Where Windows-only tools or workflows are mentioned (e.g., EFLOW), provide equivalent Linux-native alternatives or clarify when they are not needed on Linux.
GitHub Create Pull Request
IoT Edge https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-edge/how-to-observability.md ...cs/blob/main/articles/iot-edge/how-to-observability.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in the 'Try the sample' section by exclusively providing PowerShell-based deployment instructions and referencing PowerShell as a prerequisite. There are no equivalent instructions or scripts for Linux or macOS users (e.g., Bash scripts or shell commands). The use of PowerShell and the lack of cross-platform deployment guidance may hinder Linux users from following the tutorial seamlessly.
Recommendations
  • Provide equivalent Bash shell scripts and instructions for Linux/macOS users alongside PowerShell examples.
  • Clearly indicate which steps are platform-specific and offer alternatives where necessary (e.g., use Bash for Linux, PowerShell for Windows).
  • If the deployment script is inherently cross-platform (e.g., via Azure CLI), demonstrate usage in both PowerShell and Bash.
  • List prerequisites for both Windows and Linux environments, including installation steps for PowerShell Core on Linux if it is required.
  • Consider restructuring the 'Try the sample' section to present both Windows and Linux instructions in parallel, ensuring parity and inclusivity.
GitHub Create Pull Request
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 →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation is heavily focused on Windows, providing only Windows and PowerShell-based instructions and tooling (usbipd-win, PowerShell modules, Windows Package Manager, Windows Services, etc.) for connecting USB devices to Azure IoT Edge for Linux on Windows (EFLOW). There are no equivalent Linux command-line examples or instructions for users who may want to perform similar operations from a Linux host or within the EFLOW VM using native Linux tools. Linux patterns and tools are either missing or only referenced as secondary considerations.
Recommendations
  • Provide equivalent Linux command-line instructions for installing and using usbip (e.g., using apt, yum, or other package managers) for users who may be running EFLOW on a Linux host or want to interact with usbip from within the EFLOW VM.
  • Include bash shell examples for listing, attaching, and detaching USB devices using native Linux usbip tools, in addition to the PowerShell examples.
  • Mention Linux-native tools and workflows (such as lsusb, usbip, modprobe, etc.) earlier and in parallel with Windows tools, not only as an afterthought.
  • Clarify which steps are specific to Windows hosts and which can be performed from within the EFLOW VM or a Linux environment.
  • Add a section or callout for users who may want to use or test USB over IP from a Linux host, or who are troubleshooting from within the Linux VM.
GitHub Create Pull Request
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 →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation is heavily focused on Windows and PowerShell tooling for configuring multiple NICs on Azure IoT Edge for Linux on Windows (EFLOW). All configuration steps are performed using PowerShell commands and Windows-specific tools, with no equivalent Linux command-line or cross-platform alternatives provided. The workflow assumes the user is operating from a Windows environment, and Linux-native methods or tools are not mentioned or demonstrated.
Recommendations
  • Provide equivalent Linux command-line examples (e.g., using SSH, nmcli, ip, or netplan) for managing network interfaces inside the EFLOW VM.
  • Document how to perform these configuration steps from a Linux or cross-platform environment, if possible.
  • Clarify which steps must be performed on the Windows host versus inside the Linux VM, and provide Linux-native alternatives for in-VM configuration.
  • Consider including Azure CLI or portal-based instructions where possible to reduce reliance on Windows-specific tools.
  • Explicitly state if certain operations are only possible from Windows, and suggest workarounds or alternatives for Linux users.
GitHub Create Pull Request
IoT Edge https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-edge/tutorial-nested-iot-edge.md ...lob/main/articles/iot-edge/tutorial-nested-iot-edge.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation is generally Linux-focused for the main tutorial steps, but there are subtle Windows biases. Windows file paths and PowerShell output are shown in examples before or instead of Linux equivalents. References to Windows-specific tools and documentation (such as opening ports in the Azure portal for Windows VMs) are present, and some output examples use Windows-style formatting. However, the actual configuration and deployment steps are performed using Bash and Azure CLI, which are cross-platform and primarily Linux-oriented.
Recommendations
  • Provide Linux output examples (e.g., 'ls' command) alongside or before Windows PowerShell output when showing directory contents.
  • When referencing how to open ports on VMs, include links and instructions for both Windows and Linux virtual machines, not just Windows.
  • Avoid using Windows file paths (e.g., C:\nested-edge\output) as the only example; show Linux paths (e.g., /home/user/nested-edge/output) as well.
  • If showing PowerShell output, also show equivalent Bash output for parity.
  • Ensure that all troubleshooting and configuration steps are equally documented for both Windows and Linux environments, or clarify when steps are OS-agnostic.
GitHub Create Pull Request
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 →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Windows Examples Windows Heavy Symptom Descriptions
Summary
The documentation generally provides Linux-oriented troubleshooting steps and examples (e.g., use of bash, Linux file paths, systemctl), but there are several instances of Windows bias. Windows-specific networking patterns (NAT), error messages, and symptom descriptions are mentioned before or in more detail than their Linux equivalents. Some troubleshooting sections reference Windows containers and Windows VM hostname issues, and error logs include Win32-specific messages. There are no PowerShell or explicit Windows command-line examples, but Windows is often referenced first or exclusively in certain contexts, and Windows-specific issues are described in more detail than Linux-specific ones.
Recommendations
  • For every Windows-specific symptom, cause, or error message, provide the equivalent Linux details and error messages.
  • Where Windows networking (NAT) is discussed, explicitly describe the Linux (bridge) equivalent and troubleshooting steps.
  • If referencing Windows-specific error logs (e.g., hnsCall failed in Win32), provide the corresponding Linux error logs for parity.
  • Ensure that Linux and Windows troubleshooting steps are presented in parallel, rather than Windows-first.
  • If a solution is only applicable to Windows or Linux, clearly label it as such and provide the counterpart for the other OS.
  • Add PowerShell or Windows command-line examples where appropriate, but always provide Linux equivalents (and vice versa).
GitHub Create Pull Request
IoT Edge https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-edge/how-to-create-test-certificates.md ...n/articles/iot-edge/how-to-create-test-certificates.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation consistently presents Windows instructions and examples before Linux, uses PowerShell-specific commands and scripts for Windows, and references Windows-specific tools and installation methods (such as vcpkg and Set-ExecutionPolicy). While Linux parity is generally maintained with corresponding bash examples, the ordering and depth of Windows-specific tooling and scripting create a subtle Windows bias.
Recommendations
  • Alternate the order of Windows and Linux sections in each major step, or present both platforms side-by-side where possible.
  • Provide equal detail for Linux tooling and prerequisites (e.g., mention common Linux OpenSSL installation methods, such as apt or yum, not just for Windows).
  • Where possible, use cross-platform tooling or highlight cross-platform compatibility of scripts.
  • Avoid Windows-specific terminology and tools (e.g., vcpkg, Set-ExecutionPolicy) unless a Linux equivalent or explanation is provided.
  • Include troubleshooting tips and environment setup steps for Linux with the same depth as for Windows.
  • Consider a summary table at the start showing parity of steps and commands for both platforms.
GitHub Create Pull Request
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 →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Cmd Examples Missing Linux Example
Summary
The documentation provides a mix of Bash and CMD examples, but in several sections, Windows CMD syntax is used without equivalent Linux/Bash examples, especially for commands like 'iotedge logs', 'docker rm', and 'iotedge restart'. Some code blocks are marked as 'cmd' or use Windows-centric syntax, and in a few cases, the documentation does not clarify cross-platform differences or provide Linux alternatives. While the initial troubleshooting steps use Bash, later sections implicitly assume Windows usage or present Windows commands first.
Recommendations
  • For every CMD/Windows example, provide an equivalent Bash/Linux example side-by-side or clearly indicate cross-platform compatibility.
  • Use neutral code block labeling (e.g., 'shell') unless the command is truly platform-specific.
  • Clarify any differences in command usage or output between Windows and Linux environments.
  • Audit all command examples to ensure Linux users are not left to infer the correct syntax or behavior.
  • Where tools or paths differ between platforms, explicitly document both.
GitHub Create Pull Request
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 →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation shows mild Windows bias. While the main tutorial flow is Linux-focused (Linux containers, Linux device quickstart), there are several signs of Windows bias: (1) The sample images are sourced from a repository named 'Cognitive-CustomVision-Windows', with no mention of a Linux equivalent or alternative; (2) The device setup section lists 'Linux device' before 'Windows device', but only provides a link to a Windows quickstart as an alternative, not as a parallel path; (3) There are no explicit PowerShell or Windows command-line examples, but the documentation does not provide any Linux-specific troubleshooting or alternative flows for common Windows-only issues (e.g., file paths, permissions); (4) The use of Visual Studio Code and Azure IoT Edge Dev Tool is cross-platform, but the documentation does not clarify any Linux-specific nuances or provide Linux-first examples for all steps.
Recommendations
  • Provide sample images from a neutral or Linux-named repository, or clarify that the 'Cognitive-CustomVision-Windows' repo is cross-platform.
  • Include explicit Linux and Windows command-line examples where relevant, especially for file paths and Docker commands.
  • Add troubleshooting notes for common Linux-specific issues (e.g., permissions, Docker group membership, file system case sensitivity).
  • Ensure that all tool references (e.g., Visual Studio Code, Docker) clarify cross-platform compatibility and provide links to both Linux and Windows installation guides.
  • Where device setup is discussed, offer parallel quickstart links and instructions for both Linux and Windows, rather than listing Windows as an alternative.
  • If referencing Windows tools or repositories, provide Linux equivalents or clarify their cross-platform usage.
GitHub 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 →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation is heavily oriented toward Windows users, with all setup, configuration, and deployment instructions assuming a Windows host environment. All command-line examples use PowerShell, and Windows-specific tools (Device Manager, winver, WMI) are referenced exclusively. There are no Linux-native examples or instructions, and Linux tools or workflows are not discussed, despite the product involving Linux VMs.
Recommendations
  • Provide equivalent Linux command-line examples for GPU detection and configuration inside the Linux VM, such as using lspci, nvidia-smi, or glxinfo.
  • Include instructions for verifying GPU passthrough and driver installation from within the Linux guest, not just from the Windows host.
  • Mention Linux-native tools and commands alongside Windows tools (e.g., show how to check GPU status in both Device Manager and Linux tools).
  • Clarify which steps are performed on the Windows host and which should be performed inside the Linux VM, and provide parity in documentation for both environments.
  • If PowerShell is required for host-side management, explicitly state that, but also provide guidance for Linux users on how to interact with the system from the Linux side.
  • Consider adding troubleshooting steps for common Linux-side GPU issues (e.g., missing drivers, CUDA not detected, etc.).
GitHub Create Pull Request
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 →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation is heavily oriented toward Windows users, with all setup, configuration, and file transfer steps relying on Windows tools (PowerShell, Visual Studio, Windows paths, Windows-specific cmdlets). Linux-native workflows, tools, or examples are not provided, even though the target runtime is Linux. The instructions assume the user is working from a Windows environment and does not address how a user on a Linux or cross-platform system would accomplish the same tasks.
Recommendations
  • Provide equivalent instructions for users working from a Linux or macOS host, including how to build, package, and transfer files to the EFLOW VM using Linux-native tools (e.g., dotnet CLI, tar, scp, rsync).
  • Include examples using cross-platform editors and build tools (e.g., VS Code, dotnet CLI) instead of only Visual Studio.
  • Document how to enable TPM passthrough and initialize NV indexes from a Linux host, if possible, or clearly state if this is not supported.
  • Present file paths and commands in both Windows and Linux formats where applicable.
  • Add a section or callouts for Linux users, clarifying any limitations or alternative workflows.
GitHub Create Pull Request
← Previous Page 4 of 8 Next →