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 1-25 of 38 flagged pages
IoT Edge How to connect a USB device to Azure IoT Edge for Linux on Windows ...b/main/articles/iot-edge/how-to-connect-usb-devices.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First Missing Linux Example
Summary
The documentation is heavily focused on Windows, with all installation and usage instructions centered around Windows tools (usbipd-win, PowerShell, winget). All code samples and step-by-step instructions use PowerShell and Windows-specific utilities, with no equivalent Linux commands or workflows provided. The Linux side (EFLOW VM) is only briefly mentioned, and Linux-native usbip workflows are not explained. This creates friction for users who may want to use Linux hosts or understand the Linux-side configuration in detail.
Recommendations
  • Provide equivalent instructions for setting up usbip on a native Linux host, including installation and usage.
  • Include Linux command-line examples for listing, attaching, and detaching USB devices using usbip.
  • Clarify the steps required inside the EFLOW VM, including any Linux-specific configuration or troubleshooting.
  • Present both Windows and Linux approaches in parallel, or at least link to Linux documentation for usbip.
  • Add a section explaining how to perform similar tasks on macOS, or note any limitations.
GitHub Create Pull Request
IoT Edge GPU acceleration for Azure IoT Edge for Linux on Windows ...e-docs/blob/main/articles/iot-edge/gpu-acceleration.md
High Priority View Details →
Scanned: 2026-01-12 00:00
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, with all examples using Windows-specific tools (PowerShell, Device Manager), commands, and terminology. Linux is only referenced as a guest OS in a Windows VM, and there are no examples or instructions for configuring GPU acceleration on native Linux hosts or using Linux-native tools. All setup and configuration steps assume a Windows host, and PowerShell commands are used exclusively for deployment and management.
Recommendations
  • Add equivalent instructions and examples for native Linux deployments, including how to configure GPU passthrough and acceleration using Linux tools (e.g., lspci, nvidia-smi, virsh, etc.).
  • Provide Linux shell command examples for tasks like checking GPU availability, deploying IoT Edge modules, and managing virtual machines.
  • Clarify in the prerequisites and introduction that the guide is specific to Windows hosts, and link to Linux-native documentation if available.
  • Include a comparison table or section outlining differences and similarities between Windows and Linux GPU acceleration setups.
  • Mention Linux alternatives to PowerShell and Device Manager, such as bash scripts and lspci/nvidia-smi for GPU detection.
GitHub Create Pull Request
IoT Edge dTPM access for Azure IoT Edge for Linux on Windows ...docs/blob/main/articles/iot-edge/how-to-access-dtpm.md
High Priority View Details →
Scanned: 2026-01-12 00:00
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 prerequisites, setup, and file transfer steps relying on Windows tools (Visual Studio, PowerShell, Windows directories, Windows-specific cmdlets). Linux equivalents for key steps (project creation, file transfer, TPM initialization) are not provided, and Windows instructions are always presented first and exclusively. There is no guidance for users who might want to perform similar tasks from a Linux or macOS host.
Recommendations
  • Provide equivalent instructions for Linux/macOS hosts, including project creation (e.g., using dotnet CLI), file packaging (tar), and file transfer (scp, rsync, etc.).
  • Include Linux/macOS examples for enabling TPM passthrough and initializing NV indexes, if supported.
  • Offer alternative steps for users who do not have access to Visual Studio, such as using VS Code or command-line tools.
  • Clearly state any host OS limitations and provide workarounds or references for Linux/macOS users.
  • Balance the order of examples so Linux instructions are not always secondary or missing.
GitHub Create Pull Request
IoT Edge Configure multiple NICs for Azure IoT Edge for Linux on Windows ...in/articles/iot-edge/how-to-configure-multiple-nics.md
High Priority View Details →
Scanned: 2026-01-12 00:00
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 exclusively on PowerShell commands and Windows-specific tools. There are no Linux-native examples or instructions, and all procedures assume a Windows host environment. Even when interacting with the Linux VM, access is provided via Windows PowerShell, and only a single Linux command (ifconfig) is shown, executed from within the VM. This creates friction for users who may wish to manage EFLOW from a Linux or macOS host, or who expect parity in tooling and examples.
Recommendations
  • Provide equivalent instructions for managing EFLOW networking from Linux/macOS hosts, if supported.
  • Include examples using cross-platform tools (e.g., Azure CLI, SSH, Hyper-V Manager alternatives) where possible.
  • Clarify host OS requirements and limitations at the top of the documentation.
  • If EFLOW management is only possible from Windows, explicitly state this and link to Linux-native IoT Edge documentation for users with non-Windows hosts.
  • Where Linux commands are used inside the VM, expand examples to cover troubleshooting and verification steps using standard Linux networking tools.
GitHub Create Pull Request
IoT Edge Create virtual switch for Azure IoT Edge for Linux on Windows | Microsoft Docs ...main/articles/iot-edge/how-to-create-virtual-switch.md
High Priority View Details →
Scanned: 2026-01-12 00:00
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 focused on Windows, with all examples and instructions using Windows-specific tools (PowerShell, Hyper-V, Windows DHCP Server). No Linux or cross-platform alternatives are provided, and Windows terminology and commands are used exclusively throughout. Linux users are not given guidance for equivalent tasks, despite the product being 'IoT Edge for Linux on Windows'.
Recommendations
  • Add a section or links describing how to create and configure virtual switches, NAT, and DHCP on Linux hosts (e.g., using ip, brctl, dnsmasq, or NetworkManager).
  • Provide parity examples for Linux/macOS environments, or clarify that the guide is only for Windows hosts if Linux is unsupported.
  • Reference cross-platform virtualization tools (e.g., libvirt, KVM, VirtualBox) where appropriate.
  • Explicitly state the limitations for non-Windows users and offer guidance or workarounds if possible.
GitHub Create Pull Request
IoT Edge Nested virtualization - Azure IoT Edge for Linux on Windows ...s/blob/main/articles/iot-edge/nested-virtualization.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation exclusively describes deployment scenarios for Azure IoT Edge for Linux on Windows using Windows-based virtualization technologies (Hyper-V, Windows VMs on VMware ESXi, Azure VMs running Windows). All instructions and references are for Windows tools and patterns, with no mention of Linux hosts, Linux hypervisors (such as KVM or QEMU), or Linux-specific configuration steps. Linux users seeking to deploy EFLOW on native Linux virtualization platforms are not addressed.
Recommendations
  • Add equivalent deployment instructions for Linux hosts using common Linux hypervisors (e.g., KVM, QEMU, VirtualBox).
  • Include examples and configuration steps for enabling nested virtualization on Linux platforms.
  • Clarify whether EFLOW can be deployed on Linux-based VMs and, if not, explicitly state the limitation.
  • Provide parity in troubleshooting notes for Linux environments.
  • Reference Linux documentation and tools alongside Windows ones where relevant.
GitHub Create Pull Request
IoT Edge Develop and debug Azure IoT Edge modules using Visual Studio ...ticles/iot-edge/how-to-visual-studio-develop-module.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation is heavily oriented toward Windows development environments, specifically Visual Studio on Windows. Windows is assumed as the default platform, with instructions, tooling, and examples (such as vcpkg installation, file paths, and project templates) tailored for Windows. Linux development is mentioned only as a target for containers, not as a development environment, and Linux/macOS equivalents for key steps (e.g., vcpkg setup, Visual Studio alternatives, file locations) are missing or relegated to secondary status. The use of Windows-specific tools and paths (e.g., .bat files, %userprofile%) further reinforces this bias.
Recommendations
  • Add explicit instructions for setting up the development environment on Linux and macOS, including installation of Visual Studio alternatives (e.g., VS Code) and required extensions.
  • Provide Linux/macOS equivalents for vcpkg installation and usage (e.g., bootstrap-vcpkg.sh, x64-linux triplet).
  • Include Linux/macOS file paths and project template locations alongside Windows examples.
  • Clarify which steps are Windows-only and offer alternative workflows for Linux/macOS users, especially for project creation and debugging.
  • Reorder examples so that Linux and Windows are presented equally, or use tabs/pivots to let users select their OS.
  • Highlight cross-platform CLI tools and workflows where possible, and avoid assuming Windows as the default development OS.
GitHub Create Pull Request
IoT Edge Quickstart to create an Azure IoT Edge device on Windows | Microsoft Docs ...s/azure-docs/blob/main/articles/iot-edge/quickstart.md
High Priority View Details →
Scanned: 2026-01-12 00:00
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, specifically on deploying Azure IoT Edge for Linux on Windows (EFLOW). All installation and configuration steps use PowerShell commands and Windows-specific tooling (Hyper-V, MSI installers, PowerShell modules), with no equivalent instructions for native Linux or macOS environments. Linux commands are only shown for post-deployment module management inside the EFLOW VM, not for initial setup or installation. There is no guidance for users who want to deploy IoT Edge on a native Linux device.
Recommendations
  • Add a parallel quickstart or clear links for deploying Azure IoT Edge on native Linux devices, including prerequisites, installation, and configuration steps.
  • Provide Linux shell (bash) examples for installation and setup, not just PowerShell/Windows commands.
  • Explicitly state the scope of the guide (Windows-only) at the top, and direct Linux/macOS users to appropriate documentation.
  • Include troubleshooting and uninstall instructions for Linux environments.
  • Balance example order and visibility so Linux users are not disadvantaged.
GitHub Create Pull Request
IoT Edge [Individual enrollment](#tab/individual-enrollment) ...e/includes/iot-edge-create-dps-enrollment-symmetric.md
High Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides a PowerShell-only example for deriving a device key, explicitly referencing Windows and omitting equivalent Linux/macOS instructions. No cross-platform alternatives (e.g., Bash, OpenSSL, Python) are mentioned, which may hinder Linux/macOS users attempting to complete this critical provisioning step.
Recommendations
  • Add Linux/macOS examples for deriving the device key, such as Bash with OpenSSL or Python scripts.
  • Clearly indicate cross-platform alternatives and tools where possible.
  • Present Windows and Linux/macOS instructions side-by-side or in tabs to ensure parity.
  • Avoid language that implies Windows is the default or only supported platform for key generation.
GitHub Create Pull Request
IoT Edge GPU acceleration for Azure IoT Edge for Linux on Windows ...e-docs/blob/main/articles/iot-edge/gpu-acceleration.md
High Priority View Details →
Scanned: 2026-01-11 06:20
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, with all examples and instructions using Windows-specific tools (PowerShell, Device Manager, WSL). There are no native Linux or macOS setup or usage examples, and all GPU passthrough technologies and drivers are described in the context of Windows hosts. Linux is only referenced as the guest OS inside a Windows VM, not as a host or standalone environment.
Recommendations
  • Provide equivalent instructions for deploying Azure IoT Edge with GPU acceleration on native Linux hosts, if supported.
  • Include Linux shell (bash) command examples for tasks like checking GPU hardware, deploying modules, and configuring GPU passthrough.
  • Clarify whether GPU passthrough and EFLOW features are available or planned for Linux or macOS hosts, or explicitly state Windows-only support.
  • Reference Linux tools (e.g., lspci, nvidia-smi) for GPU identification and management alongside Windows tools.
  • If Linux/macOS host support is not available, add a prominent note to inform users.
GitHub Create Pull Request
IoT Edge Configure multiple NICs for Azure IoT Edge for Linux on Windows ...in/articles/iot-edge/how-to-configure-multiple-nics.md
High Priority View Details →
Scanned: 2026-01-11 06:20
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 focused on Windows and PowerShell, with all configuration steps and examples using Windows-specific tools and cmdlets. There are no Linux-native instructions or examples, and the workflow assumes the user is operating from a Windows host. Linux tools and patterns are not mentioned, and PowerShell commands are used exclusively for VM management and network configuration.
Recommendations
  • Provide equivalent instructions for configuring multiple NICs on Azure IoT Edge for Linux VMs running on native Linux hosts, using Linux tools (e.g., ip, nmcli, or Azure CLI).
  • Include Linux shell command examples for network interface management inside the VM, not just ifconfig.
  • Clarify in the prerequisites and introduction that the guide is Windows-centric and provide links or references to Linux-native guides if available.
  • Where possible, mention cross-platform alternatives to PowerShell cmdlets, such as Azure CLI or REST API calls.
  • Add a section or sidebar for Linux/macOS users explaining how to achieve similar results without Windows or PowerShell.
GitHub Create Pull Request
IoT Edge Create virtual switch for Azure IoT Edge for Linux on Windows | Microsoft Docs ...main/articles/iot-edge/how-to-create-virtual-switch.md
High Priority View Details →
Scanned: 2026-01-11 06:20
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 instructions, examples, and tooling focused exclusively on Windows and PowerShell. Windows-specific tools (Hyper-V, PowerShell cmdlets, Windows DHCP server) are used throughout, with no mention of Linux equivalents or alternative approaches for non-Windows hosts. The guide assumes the user is on Windows and does not provide Linux/macOS parity.
Recommendations
  • Add a section or separate guide for creating a virtual switch and configuring NAT/DHCP on Linux hosts (using tools like ip, brctl, dnsmasq, etc.).
  • Mention Linux virtualization technologies (e.g., KVM, libvirt, VirtualBox) and provide equivalent steps for those environments.
  • Clarify in the prerequisites and introduction that the guide is Windows-specific, and link to Linux/macOS instructions if available.
  • Provide cross-platform comparison tables or notes to help users on non-Windows systems understand what steps/tools are analogous.
  • If IoT Edge for Linux on Windows is only supported on Windows hosts, state this explicitly and explain why Linux/macOS hosts are not covered.
GitHub Create Pull Request
IoT Edge How to connect a USB device to Azure IoT Edge for Linux on Windows ...b/main/articles/iot-edge/how-to-connect-usb-devices.md
High Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First Missing Linux Example
Summary
The documentation is strongly Windows-centric, focusing exclusively on Windows tools (usbipd-win, PowerShell, winget) and workflows for connecting USB devices to Azure IoT Edge for Linux on Windows (EFLOW). All setup and usage instructions are given using Windows and PowerShell, with no Linux-side or cross-platform examples. Linux-native usbip tools and workflows are not mentioned, and Linux users are not provided with equivalent instructions or parity.
Recommendations
  • Include instructions for using native Linux usbip tools to connect USB devices, both on the host and within the EFLOW VM.
  • Provide Linux command-line examples (e.g., bash, usbip) alongside PowerShell examples.
  • Clarify which steps are Windows-only and which can be performed from Linux/macOS hosts, or explicitly state limitations.
  • Add troubleshooting and setup guidance for Linux users, including installation of usbip utilities and device attachment.
  • Present examples for both Windows and Linux hosts, or at least reference Linux documentation for similar workflows.
GitHub Create Pull Request
IoT Edge Nested virtualization - Azure IoT Edge for Linux on Windows ...s/blob/main/articles/iot-edge/nested-virtualization.md
High Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation exclusively describes deployment scenarios for Azure IoT Edge for Linux on Windows using Windows-based virtualization technologies (Hyper-V, VMware with Windows VMs, Azure VMs running Windows). All configuration steps, examples, and referenced tools are Windows-centric, with no mention of Linux hosts, Linux virtualization tools (e.g., KVM, QEMU), or Linux-specific instructions. This creates friction for users seeking to deploy EFLOW in environments where Linux is the primary host OS.
Recommendations
  • Add equivalent instructions for deploying nested virtualization on Linux hosts using KVM/QEMU or other Linux hypervisors.
  • Include examples and configuration steps for Linux-based virtualization platforms.
  • Clarify whether EFLOW can be hosted on Linux VMs, and if not, explain the limitations.
  • Provide parity in troubleshooting and networking guidance for Linux environments.
GitHub Create Pull Request
IoT Edge Quickstart to create an Azure IoT Edge device on Windows | Microsoft Docs ...s/azure-docs/blob/main/articles/iot-edge/quickstart.md
High Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
This documentation page is heavily focused on Windows environments, specifically guiding users through deploying Azure IoT Edge for Linux on Windows (EFLOW) using Windows 10/11 and PowerShell commands. All installation and configuration steps are provided exclusively for Windows, with no instructions or examples for native Linux or macOS environments. Windows tools (PowerShell, Hyper-V, MSI installers) are used throughout, and Linux commands only appear after the device is provisioned and running inside the EFLOW VM. There is no guidance for users who wish to deploy IoT Edge directly on Linux or macOS devices.
Recommendations
  • Add a parallel quickstart or clear links for deploying Azure IoT Edge on native Linux devices, including prerequisites, installation, and configuration steps.
  • Include Linux shell (bash) examples for installation and management tasks, not just PowerShell.
  • Explicitly state at the beginning that this guide is Windows-specific, and provide references to Linux/macOS guides.
  • Where possible, mention Linux equivalents for Windows tools (e.g., Hyper-V alternatives, package managers, etc.).
  • Ensure that Linux users are not left without actionable steps for completing the same tasks.
GitHub Create Pull Request
IoT Edge [Individual enrollment](#tab/individual-enrollment) ...e/includes/iot-edge-create-dps-enrollment-symmetric.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides a PowerShell-only example for deriving a device key, explicitly referencing Windows and omitting equivalent Linux/macOS instructions (e.g., Bash, OpenSSL, Python). This creates friction for non-Windows users, who must find their own method to complete a critical provisioning step.
Recommendations
  • Add a Linux/macOS example for deriving the device key, using Bash and OpenSSL or Python.
  • Present cross-platform instructions side-by-side or clarify that the method is not Windows-specific.
  • Avoid referencing Windows or PowerShell exclusively in critical steps; use generic language or provide alternatives.
GitHub Create Pull Request
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 →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation provides both Linux and Windows instructions for configuring Azure IoT Edge devices behind a proxy, but Windows-specific examples (especially PowerShell commands and registry edits) are more detailed and appear before Linux equivalents in several sections. Windows tools and patterns (e.g., PowerShell, registry edits, Invoke-WebRequest) are emphasized, while Linux instructions are more generic and sometimes refer out to external documentation. Linux examples are present but less detailed, and Windows-specific options (like offline installation) are highlighted.
Recommendations
  • Ensure Linux instructions are as detailed and explicit as Windows ones, with step-by-step commands and troubleshooting notes.
  • Present Linux and Windows instructions in parallel or alternate order, rather than consistently listing Windows first.
  • Include Linux-specific troubleshooting tips and examples for proxy credential handling, similar to the PowerShell credential examples for Windows.
  • Expand on Linux offline installation options if available, or clarify parity.
  • Reference Linux-native tools (e.g., curl, wget, environment variables) where appropriate, not just package manager configuration.
GitHub Create Pull Request
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 →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
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 presented with more detail and multiple methods (PowerShell, certlm GUI, .NET API), while Linux is limited to Ubuntu CLI commands. Windows tools and patterns (Schannel, certlm, Import-Certificate) are mentioned and explained in depth, whereas Linux alternatives (other distros, certificate stores, TLS stacks) are not discussed. The order of presentation sometimes puts Windows before Linux, and troubleshooting steps mention host file edits (common in Windows) without Linux equivalents.
Recommendations
  • Expand Linux instructions to cover other distributions (e.g., CentOS, RHEL, SUSE) and their certificate store management.
  • Provide parity for programmatic certificate installation on Linux (e.g., using Python, Bash, or .NET on Linux).
  • Mention and explain Linux TLS stacks (OpenSSL, LibreSSL) in more detail, similar to Schannel for Windows.
  • Include GUI-based certificate installation instructions for Linux (e.g., using GNOME/KDE certificate managers).
  • Ensure troubleshooting steps include Linux-specific advice (e.g., editing /etc/hosts, checking iptables/firewalld).
  • Present Linux and Windows instructions side-by-side or in a consistent order to avoid Windows-first impression.
GitHub 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 →
Scanned: 2026-01-12 00:00
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. Windows-specific tools (e.g., vcpkg, PowerShell execution policy, Get-Pfxcertificate) are described in detail, while Linux instructions are more concise and lack comparable detail. Windows terminology and tooling (e.g., PATH environment variable, PowerShell commands) are emphasized, and some advanced certificate management steps (like thumbprint extraction) use Windows-specific commands first.
Recommendations
  • Alternate the order of Windows and Linux sections, or present them side-by-side to avoid implicit prioritization.
  • Provide equally detailed explanations for Linux steps, including troubleshooting and environment setup (e.g., OpenSSL installation on Linux).
  • Where Windows-specific tools (like vcpkg or PowerShell) are mentioned, offer Linux alternatives (e.g., apt-get/yum for OpenSSL, bash scripting tips).
  • Ensure advanced tasks (like thumbprint extraction) include Linux-first or cross-platform commands, and explain any differences in output or usage.
  • Clarify any platform-specific terminology and provide cross-platform context (e.g., PATH variable differences, script execution policies).
GitHub Create Pull Request
IoT Edge Create transparent gateway device using Azure IoT Edge ...articles/iot-edge/how-to-create-transparent-gateway.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
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 (e.g., Copy-EflowVMFile, Connect-EflowVm, Invoke-EflowVmCommand) that 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/EFLOW instructions are presented before or with more emphasis than Linux, and Windows-specific networking warnings are prominent.
Recommendations
  • Provide equivalent Linux/macOS instructions for all PowerShell cmdlets, especially for file transfer and port opening (e.g., use scp, rsync, or standard SSH for copying files, and direct iptables commands for opening ports).
  • Where possible, present Linux and Windows instructions with equal detail and prominence, avoiding Windows-first ordering.
  • Add notes or tables comparing Windows/PowerShell tools with their Linux equivalents to help users translate steps.
  • Include troubleshooting tips for Linux users, especially around permissions and networking.
  • Consider a unified example section that shows both Linux and Windows commands side-by-side for each major step.
GitHub Create Pull Request
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 →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in the deployment instructions for the sample scenario. Only PowerShell and Windows-centric tooling are mentioned for deployment, with no Linux/macOS equivalents or instructions. The script provided is a PowerShell script, and users are explicitly told to open a PowerShell console, which is not native to Linux/macOS. There are no Bash or shell script alternatives, nor are there instructions for using Azure CLI directly from a Linux/macOS terminal.
Recommendations
  • Provide Linux/macOS deployment instructions alongside Windows/PowerShell steps.
  • Offer a Bash or shell script alternative to the PowerShell deployment script.
  • Clarify whether the PowerShell script can run on PowerShell Core on Linux/macOS, and provide guidance if so.
  • Include Azure CLI-only instructions for users who prefer not to use PowerShell.
  • Explicitly mention cross-platform compatibility in the prerequisites section.
GitHub Create Pull Request
IoT Edge [Individual enrollment](#tab/individual-enrollment) ...t-edge/includes/iot-edge-create-dps-enrollment-x509.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates Windows bias primarily through the exclusive use of PowerShell commands (e.g., New-CACertsVerificationCert) and Windows-style file paths (e.g., <WRKDIR>\certs\...). There are no Linux/macOS shell equivalents or instructions for certificate verification, and the demo certificate paths use Windows conventions. This creates friction for Linux/macOS users attempting to follow the steps, especially for certificate verification.
Recommendations
  • Provide Linux/macOS shell (bash) equivalents for PowerShell commands, especially for certificate verification (e.g., using OpenSSL).
  • Include Linux-style file paths in examples (e.g., <WRKDIR>/certs/...).
  • Explicitly mention cross-platform tooling or provide links to platform-specific instructions/scripts.
  • Clarify whether the verification tool is available for Linux/macOS and how to use it on those platforms.
GitHub Create Pull Request
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 →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy 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 terminology appearing first or exclusively in several sections. Docker Desktop for Windows is described in greater detail than its Linux equivalent, and references to PowerShell and Windows paths are frequent. Some instructions, such as setting environment variables or directory paths, use Windows conventions by default, with Linux/macOS alternatives mentioned only as notes or afterthoughts. The tutorial claims to support Linux/macOS, but Windows-centric patterns and tools are emphasized throughout.
Recommendations
  • Present Linux/macOS instructions and examples alongside Windows, not as secondary notes.
  • Use platform-neutral language and paths in code samples (e.g., use $HOME or ~ for home directories, /dev for directories, etc.).
  • Provide explicit Linux/macOS commands for tasks like directory creation, environment variable setting, and Docker installation.
  • Include troubleshooting steps and common issues for Linux/macOS users.
  • Avoid assuming Windows as the default; clarify when instructions differ by platform.
  • Ensure parity in tool recommendations (e.g., mention Podman or Docker CE for Linux, not just Docker Desktop).
GitHub Create Pull Request
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 →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page primarily addresses Windows users by warning about PowerShell/cmd limitations and recommending Git Bash or WSL Bash, but does not mention Linux or macOS terminals. There are no Linux/macOS-specific instructions or examples, and the guidance assumes a Windows environment for shell selection.
Recommendations
  • Explicitly mention that the curl command works natively on Linux and macOS terminals.
  • Add a note for Linux/macOS users confirming that their default terminals are compatible.
  • Provide troubleshooting steps for Linux/macOS users if issues arise.
  • Reorder notes to address all platforms equally, not just Windows.
GitHub Create Pull Request
IoT Edge dTPM access for Azure IoT Edge for Linux on Windows ...docs/blob/main/articles/iot-edge/how-to-access-dtpm.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
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 workflows and tools, with all setup, build, and file transfer steps relying on Windows, PowerShell, and Visual Studio. Linux alternatives for building, packaging, and transferring files are not provided, and Windows-specific commands and tools are presented first and exclusively. This creates friction for users who may want to work from a Linux or macOS host, or use Linux-native development tools.
Recommendations
  • Provide equivalent instructions for Linux/macOS hosts, including how to build the .NET executable using the 'dotnet' CLI and package files using standard Linux tools.
  • Include Linux-native file transfer methods (e.g., scp, rsync) for copying files to the EFLOW VM.
  • Offer examples using Linux development environments (e.g., VS Code, JetBrains Rider) in addition to Visual Studio.
  • Clarify which steps must be performed on Windows and which can be done from Linux/macOS, and provide guidance for cross-platform scenarios.
  • Add Linux/macOS shell command equivalents alongside PowerShell commands.
GitHub Create Pull Request
← Previous Page 1 of 2 Next →