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 26-50 of 184 flagged pages
IoT Edge Connect a downstream device to an Azure IoT Edge gateway .../articles/iot-edge/how-to-connect-downstream-device.md
High Priority View Details →
Scanned: 2026-01-11 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 provides both Ubuntu (Linux) and Windows instructions for installing CA certificates, but Windows instructions are more detailed, listing multiple methods (PowerShell, certlm GUI, .NET APIs), while Ubuntu is limited to basic CLI commands. Windows tools (Schannel, certlm, Import-Certificate) are mentioned explicitly and explained, whereas Linux TLS libraries are referenced only in passing. In SDK sections, Windows-specific details (Schannel, certificate store requirements) are emphasized, and .NET instructions mention both Linux and Windows but focus on Windows certificate store. There is a slight 'Windows-first' ordering in explanations and more extensive troubleshooting guidance for Windows environments. Some Linux-specific troubleshooting or alternative tools (e.g., update-ca-certificates alternatives, SELinux, systemd specifics) are missing.
Recommendations
  • Expand Linux instructions to include alternative certificate installation methods (e.g., for Red Hat/CentOS, using update-ca-trust, or for Debian, using dpkg-reconfigure ca-certificates).
  • Provide parity in troubleshooting steps for Linux environments, such as checking permissions, SELinux/AppArmor issues, and systemd service restarts.
  • List Linux TLS stack details (OpenSSL, LibreSSL) with the same depth as Schannel for Windows, including configuration file locations and debugging tips.
  • Offer programmatic certificate installation examples for Linux (e.g., using Python, Bash scripts, or C APIs), similar to the .NET example for Windows.
  • Ensure that Linux tools and patterns are mentioned before or alongside Windows equivalents, and avoid Windows-first ordering in explanations.
  • Add explicit instructions for verifying certificate installation on Linux (e.g., using openssl, certtool, or viewing /etc/ssl/certs contents).
GitHub Create Pull Request
IoT Edge Create test certificates - Azure IoT Edge ...n/articles/iot-edge/how-to-create-test-certificates.md
High Priority View Details →
Scanned: 2026-01-11 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 examples before Linux equivalents, with Windows sections using PowerShell scripts and commands extensively. Windows-specific tooling (vcpkg, PowerShell execution policy, Get-Pfxcertificate) is described in detail, while Linux instructions are briefer and rely on bash scripts. Some advanced certificate management steps (e.g., thumbprint extraction) use Windows-centric commands and tools, with Linux alternatives provided but less explained.
Recommendations
  • Alternate the order of Windows and Linux instructions in each section, or present both side-by-side to avoid implicit prioritization.
  • Provide equally detailed explanations for Linux commands and tools (e.g., explain openssl and sed usage for thumbprint extraction as thoroughly as PowerShell equivalents).
  • Include troubleshooting steps and environment setup guidance for Linux that matches the depth of Windows instructions (e.g., PATH setup for openssl, bash script permissions).
  • Where possible, use cross-platform commands and avoid Windows-specific tools unless absolutely necessary; highlight Linux-native alternatives for certificate management.
  • Add notes on differences in file paths, permissions, and shell environments to help Linux users avoid common pitfalls.
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 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, with all examples and instructions using Windows-specific tools (PowerShell, Hyper-V, Windows DHCP Server). There are no Linux equivalents or cross-platform alternatives provided, and the guide assumes the user is operating in a Windows environment throughout. Linux commands, tools, or patterns are not mentioned, despite the context being Azure IoT Edge for Linux on Windows.
Recommendations
  • Add equivalent instructions for creating virtual switches, NAT, and DHCP on Linux hosts (e.g., using ip, brctl, dnsmasq, or isc-dhcp-server).
  • Provide Linux command-line examples alongside PowerShell commands, or clarify that the process is only supported on Windows if that is the case.
  • Reference Linux networking tools and patterns where appropriate, and discuss any platform limitations or differences.
  • Explicitly state the scope of the guide (Windows-only, or cross-platform) at the beginning to set user expectations.
  • If the product is only supported on Windows hosts, provide rationale and link to Linux-native alternatives for similar scenarios.
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-11 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 page demonstrates a clear Windows bias. It assumes the development machine is Windows, provides Windows-specific instructions and commands (e.g., use of .bat files, Windows paths, Visual Studio workflows), and prioritizes Windows tools and patterns (such as Visual Studio and Vcpkg for Windows). Linux equivalents are either missing, mentioned only as secondary options, or require Windows as a host (e.g., Docker Desktop for Linux containers on Windows). There are few, if any, Linux-specific examples, and the overall workflow is centered around Windows development environments.
Recommendations
  • Provide explicit Linux development instructions, including setup steps for Visual Studio on Linux (if supported) or alternative IDEs like VS Code.
  • Include Linux-specific commands and examples (e.g., using bootstrap-vcpkg.sh, Linux file paths, and shell commands).
  • Offer parity in module creation, debugging, and deployment workflows for Linux users, including Docker installation and usage on native Linux.
  • Clarify which steps are Windows-only and provide alternatives for Linux/macOS where possible.
  • Present Linux and Windows instructions side-by-side or use tabs/pivots to allow users to select their OS.
  • Highlight cross-platform CLI tools and avoid assuming Windows as the default development environment.
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
High Priority View Details →
Scanned: 2026-01-11 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 its deployment instructions by exclusively referencing PowerShell and providing only a PowerShell script for setup. The instructions explicitly ask the user to open a PowerShell console, with no mention of Linux shells or bash equivalents. There are no Linux-specific deployment steps or examples, and the use of PowerShell is presented as the default and only option.
Recommendations
  • Provide equivalent bash shell instructions and scripts for Linux users, such as a deploy-e2e-tutorial.sh script.
  • Explicitly mention support for Linux and macOS platforms in the prerequisites and deployment steps.
  • List both Windows and Linux tools in the prerequisites, e.g., 'PowerShell (Windows), Bash (Linux/macOS)'.
  • Add examples for running the deployment on Linux, including any required permissions or environment setup.
  • Ensure troubleshooting and monitoring steps reference cross-platform tools and interfaces, not just those available in Windows 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 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, specifically guiding users through deploying Azure IoT Edge for Linux on Windows. All installation and configuration steps use PowerShell commands and Windows-specific tooling (Hyper-V, MSI installers, PowerShell execution policy). There are no equivalent instructions or examples for deploying directly to native Linux devices, and Linux commands only appear at the very end for module verification, not for setup or installation.
Recommendations
  • Provide parallel instructions for setting up Azure IoT Edge on native Linux devices, including prerequisites, installation, and configuration steps using Linux tools and shell commands.
  • Include Linux-first examples for installation (e.g., using apt, yum, or direct Docker installation) and configuration, not just verification.
  • Mention Linux system requirements and supported distributions alongside Windows requirements.
  • Avoid assuming the user is on Windows; offer clear sections for both Windows and Linux users, or link to Linux-specific quickstarts.
  • Balance PowerShell and Bash examples throughout the documentation, especially for core setup steps.
  • Reference Linux virtualization options (e.g., KVM, VirtualBox) if relevant, not just Hyper-V.
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
High Priority View Details →
Scanned: 2026-01-11 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 exhibits a Windows bias in several ways: Windows is presented as the default development environment, with references to Windows-specific features (e.g., Docker Desktop for Windows, nested virtualization, Windows paths in examples), and Windows installation instructions are listed before Linux/macOS equivalents. There is frequent mention of PowerShell, command prompt, and Windows environment variable patterns, while Linux-specific instructions (e.g., for Docker, environment variables, and file paths) are less emphasized or only mentioned as alternatives. The tutorial uses Windows-centric terminology and examples, and Linux equivalents are sometimes missing or only referenced in passing.
Recommendations
  • Present Linux and macOS instructions and examples alongside Windows, not after or as alternatives.
  • Use cross-platform file paths (e.g., ~/dev/iotedgesolution or /home/user/dev/iotedgesolution) in examples, or provide both Windows and Linux/macOS versions.
  • Include explicit Linux/macOS command-line examples for all steps, especially for environment variable setup, Docker installation, and directory creation.
  • Avoid Windows-centric terminology (e.g., 'command prompt', '%APPDATA%') without providing Linux equivalents (e.g., 'terminal', '~/.local/bin').
  • Highlight Linux as a first-class development environment, not just as the target device OS.
  • Add troubleshooting steps specific to Linux/macOS environments.
  • Ensure that all language-specific instructions (C#, C, Java, Node.js, Python) include Linux/macOS details where relevant.
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 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 example for deriving a device key, explicitly referencing Windows and omitting equivalent Linux or cross-platform command-line examples (such as Bash/OpenSSL or Python). Windows tooling is mentioned first and exclusively in this context, which may hinder Linux users or those on other platforms from following the instructions without additional research.
Recommendations
  • Add Linux/Bash/OpenSSL and/or Python examples for deriving the device key, alongside the PowerShell example.
  • Explicitly state that the process can be performed on any OS and provide cross-platform instructions.
  • Reference platform-agnostic tools or libraries (e.g., OpenSSL, Python's hashlib) before or alongside Windows-specific tools.
  • Consider reordering or grouping platform-specific instructions under clear headings (e.g., 'On Windows', 'On Linux/macOS').
GitHub Create Pull Request
IoT Edge IoT Edge supported platforms ...Docs/azure-docs/blob/main/articles/iot-edge/support.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Windows Heavy Recommendation
Summary
The documentation page demonstrates a Windows bias primarily by emphasizing Windows as a recommended platform for running Azure IoT Edge (via EFLOW), mentioning Windows-specific tools and patterns (such as 'IoT Edge for Linux on Windows'), and placing Windows information and recommendations before or more prominently than Linux equivalents. There is a strong focus on Windows devices running Linux containers through a Microsoft-provided VM, and Windows support channels are highlighted. Linux platforms are well represented in the Tier 1 and Tier 2 tables, but Windows is repeatedly called out as a special case and the recommended approach for Windows is to run Linux in a VM, rather than supporting native Windows containers.
Recommendations
  • Provide equal prominence to Linux installation and usage patterns, including direct installation instructions and troubleshooting for Linux hosts.
  • Include explicit Linux-first examples and recommendations, rather than positioning Windows (via EFLOW) as the primary or recommended approach.
  • Clarify and expand support channels for Linux users, ensuring that bug reporting and support instructions are not Windows-centric.
  • Avoid language that positions Windows as the default or preferred platform, and ensure that Linux usage is presented as a first-class, fully supported scenario.
  • If Windows containers are deprecated, provide migration guides and parity documentation for Linux container users, rather than focusing only on Windows users transitioning to EFLOW.
GitHub Create Pull Request
IoT Edge Create transparent gateway device using Azure IoT Edge ...articles/iot-edge/how-to-create-transparent-gateway.md
High Priority View Details →
Scanned: 2026-01-10 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 Windows-specific tools (PowerShell cmdlets like Copy-EflowVMFile, Connect-EflowVm, Invoke-EflowVmCommand) are highlighted for EFLOW scenarios. The use of PowerShell and Windows-centric workflows is prominent, and Windows/EFLOW instructions are often presented with more detail and dedicated sections. Linux instructions are present and generally sufficient, but the Windows/EFLOW path receives more explicit tooling and step-by-step guidance, especially for file transfer and port management.
Recommendations
  • Provide equivalent Linux-native instructions for all steps, especially for file transfer and port management (e.g., using scp, rsync, or standard SSH commands for copying files).
  • Where PowerShell cmdlets are used for EFLOW, offer alternative Linux commands or clarify how similar tasks are performed on pure Linux deployments.
  • Ensure that Linux instructions are as detailed and explicit as Windows/EFLOW instructions, including troubleshooting tips and command explanations.
  • Consider presenting Linux instructions first, or in parallel, to avoid the perception of Windows-first bias.
  • Add a summary table or section comparing Linux and Windows workflows for each major step, highlighting parity and differences.
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-10 00:00
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 example for deriving a device key and explicitly mentions 'On Windows', with no equivalent example or instructions for Linux or cross-platform environments. This prioritizes Windows tooling and patterns, omits Linux alternatives, and may hinder Linux users from following the instructions easily.
Recommendations
  • Add a Linux example for deriving the device key, such as using OpenSSL or a Python script.
  • Present cross-platform solutions (e.g., Python, Node.js) before or alongside Windows/PowerShell examples.
  • Avoid language such as 'On Windows' unless also providing 'On Linux' or 'On macOS' sections.
  • Reference Linux tools (e.g., openssl, sha256sum) and provide command-line examples.
  • Clearly indicate that the process can be performed on any OS and provide parity in instructions.
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-10 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, with all installation and usage instructions centered around Windows tools (usbipd-win, winget, PowerShell). Examples are exclusively given in PowerShell, and Windows-specific steps (such as using 'Add or Remove Programs', 'Services' app, and 'ipconfig') are described in detail. Linux-side instructions are minimal and only briefly mentioned, with no concrete Linux command examples or guidance for users who may want to use Linux tools or interact directly with the EFLOW VM using Linux-native methods.
Recommendations
  • Provide equivalent Linux-side command examples for attaching and managing USB devices (e.g., using 'usbip' commands directly in the EFLOW VM).
  • Include instructions for users who may want to connect USB devices from a Linux host, or clarify host OS requirements.
  • Offer bash script samples for automating USB device attachment on the EFLOW VM, as briefly mentioned.
  • Balance PowerShell examples with Linux shell commands where appropriate, especially for actions performed inside the EFLOW VM.
  • Clarify which steps are performed on the Windows host and which on the Linux VM, and provide parity in documentation for both environments.
GitHub Create Pull Request
IoT Edge Authenticate downstream devices - Azure IoT Edge ...cles/iot-edge/how-to-authenticate-downstream-device.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation demonstrates mild Windows bias. In the X.509 self-signed authentication section, the openssl command is presented first for Windows/PowerShell, with the Linux example following. The Windows example does not use any Windows-specific tools, but the ordering suggests a Windows-first approach. There are no explicit Linux-only tools or patterns mentioned, and no Linux-specific guidance is provided for certificate generation or device registration. The documentation does not provide parity in terms of example ordering or platform-specific troubleshooting.
Recommendations
  • Present Linux and Windows examples side-by-side, or alternate which platform is shown first.
  • Include explicit Linux instructions for certificate generation and file management, not just openssl commands.
  • Add troubleshooting tips for common Linux issues (e.g., permissions, DNS resolution).
  • Reference Linux-native tools (e.g., scp, bash scripts) equally with Windows tools.
  • Ensure screenshots and UI guidance are not Windows-centric, or provide Linux equivalents where relevant.
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
High Priority View Details →
Scanned: 2026-01-10 00:00
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 instructions are more verbose and appear before Linux equivalents in several sections. Windows-specific tools (PowerShell, registry editor) are highlighted, while Linux instructions are more generic and sometimes reference external documentation. Linux examples are present but less detailed, and the overall structure tends to prioritize Windows scenarios.
Recommendations
  • Ensure Linux instructions are as detailed and self-contained as Windows instructions, including troubleshooting and credential handling.
  • Present Linux and Windows examples in parallel or alternate the order to avoid implicit prioritization.
  • Include direct Linux command-line examples for all steps where Windows PowerShell is shown, such as credential management and proxy configuration.
  • Reference Linux-specific tools and configuration files (e.g., environment variables, systemd, apt) with the same depth as Windows tools.
  • Add explicit troubleshooting steps for Linux, similar to those provided for Windows.
  • Where external documentation is referenced for Linux, consider summarizing key steps inline for parity.
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-10 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 environments, with all setup, configuration, and deployment examples using Windows tools (PowerShell, Device Manager, winver). There are no Linux-native examples or instructions, and Windows-specific requirements and patterns are presented exclusively and first. The use of WSL is mentioned, but only as a dependency for running Linux workloads on Windows, not as a standalone Linux environment. No Linux command-line or tooling examples are provided.
Recommendations
  • Provide equivalent Linux-native instructions and examples for GPU passthrough and deployment, including relevant Linux commands and configuration steps.
  • Include Linux shell (bash) examples for querying GPU information and managing deployments.
  • Mention Linux distributions and supported kernel/driver versions for GPU acceleration.
  • Clarify which steps are specific to Windows and which are applicable to Linux, and organize documentation so that Linux instructions are not subordinate to Windows.
  • Reference Linux documentation for NVIDIA and Intel GPU drivers and setup, not just WSL or Windows-focused guides.
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-10 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 page demonstrates a strong Windows bias. All setup, configuration, and file transfer instructions use Windows tools and PowerShell commands, with no Linux equivalents or alternatives provided. The development workflow is centered on Visual Studio and NuGet, both Windows-centric tools, and assumes the user is operating from a Windows host. Linux-native approaches (e.g., using Linux as the host, Linux-based development environments, or Linux command-line tools for file transfer) are not discussed.
Recommendations
  • Provide equivalent instructions for users working from a Linux host, including Linux-native commands for enabling TPM passthrough, file transfer, and connecting to the EFLOW VM.
  • Include examples using Linux development tools (e.g., VS Code, CLI-based .NET SDK usage) and package managers (e.g., dotnet CLI, apt, yum) for building and publishing the executable.
  • Offer Linux shell command alternatives for all PowerShell commands (e.g., using scp, tar, ssh).
  • Clarify which steps are strictly Windows-only and which can be adapted for Linux, and provide guidance for cross-platform scenarios.
  • Add a section or callouts for Linux users to ensure parity and inclusivity in the documentation.
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-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation is heavily biased towards Windows, with all configuration steps and examples using PowerShell commands and Windows-specific tools. There are no Linux-native commands or examples for managing NICs, and the workflow assumes a Windows environment throughout. The only Linux command shown is 'ifconfig', and even that is run inside a VM managed from Windows. There is no guidance for users who may want to perform similar tasks from a Linux host or using Linux-native tooling.
Recommendations
  • Provide equivalent Linux command-line examples (e.g., using 'nmcli', 'ip', or 'netplan') for managing NICs inside the EFLOW VM.
  • Include instructions for configuring multiple NICs from a Linux host, if supported by EFLOW.
  • Mention Linux-native virtualization and networking tools (e.g., KVM, libvirt, bridge-utils) where relevant.
  • Clarify which steps are Windows-specific and offer Linux alternatives or note limitations.
  • Ensure that Linux users are not excluded by documenting any EFLOW features or limitations that are Windows-only.
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
High Priority View Details →
Scanned: 2026-01-10 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 instructions are more detailed, listing multiple methods (PowerShell, certlm utility, .NET APIs) and mentioning specific Windows technologies (Schannel). Windows tools and patterns (PowerShell, certlm) are described before their Linux equivalents in some sections. The troubleshooting and testing sections use cross-platform tools (openssl), but overall, Windows-specific guidance is more prominent and detailed.
Recommendations
  • Expand Linux instructions to match the detail of Windows guidance, e.g., provide alternative methods for installing certificates (using GUI tools, programmatic installation via Python or Bash).
  • Mention Linux TLS stacks (OpenSSL, LibreSSL, GnuTLS) with similar detail as Schannel for Windows.
  • Ensure Linux examples and tools are presented with equal prominence and order as Windows equivalents.
  • Provide troubleshooting steps specific to Linux environments (e.g., checking certificate installation, permissions, common errors).
  • Reference Linux-specific documentation or utilities where appropriate (e.g., update-ca-certificates, certtool, systemd-coredump for debugging).
GitHub Create Pull Request
IoT Edge Create test certificates - Azure IoT Edge ...n/articles/iot-edge/how-to-create-test-certificates.md
High Priority View Details →
Scanned: 2026-01-10 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 examples before Linux equivalents, with Windows-specific tooling (PowerShell, vcpkg, Get-Pfxcertificate) and commands featured prominently. Windows installation and usage patterns (e.g., setting execution policy, using PowerShell scripts/functions, referencing .exe files) are described in greater detail, while Linux instructions are generally shorter and rely on bash scripts. Some certificate management steps use Windows-only tools (e.g., Get-Pfxcertificate for thumbprint extraction) with less explanation or alternative for Linux users.
Recommendations
  • Alternate the order of Windows and Linux instructions in each section, or present them side-by-side to avoid implicit prioritization.
  • Provide equal detail for Linux steps, including troubleshooting tips, environment setup, and script usage.
  • Where Windows-specific tools (e.g., PowerShell, vcpkg, Get-Pfxcertificate) are used, offer Linux equivalents (e.g., openssl commands for thumbprint extraction, package manager instructions for OpenSSL installation).
  • Include explicit notes on differences in file paths, permissions, and environment variables between Windows and Linux.
  • Ensure parity in script functionality and documentation for both platforms, and highlight any limitations or differences.
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-10 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, providing only Windows and PowerShell-based instructions for creating a virtual switch, NAT, and DHCP server. All examples use Windows-specific tools (PowerShell cmdlets, Windows Features), and there are no Linux equivalents or cross-platform instructions. The prerequisites and steps assume the user is on Windows, with no mention of how similar tasks could be performed on Linux or with Linux-native tools.
Recommendations
  • Add equivalent instructions for Linux environments, such as using Linux networking tools (e.g., ip, brctl, dnsmasq, isc-dhcp-server) to create virtual switches, configure NAT, and set up DHCP.
  • Provide cross-platform context, explaining how the process differs on Linux and referencing relevant Linux documentation.
  • Include Linux command-line examples alongside PowerShell examples, or provide links to Linux-specific guides.
  • Clarify in the prerequisites and introduction whether the guide is intended only for Windows users, and if so, link to Linux-specific documentation for users on Linux hosts.
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-10 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 page exhibits a strong Windows bias. It assumes the development machine is Windows, provides Windows-specific installation steps (e.g., vcpkg with .bat files), and references Windows paths and tools (Visual Studio, Developer Command Prompt) throughout. Linux equivalents are rarely mentioned, and Linux development scenarios are treated as secondary or require using Windows with Docker Desktop. Examples and instructions for Linux users (e.g., installing vcpkg, using Visual Studio on Linux, or Linux-native workflows) are missing or only briefly referenced. The documentation prioritizes Windows tools and patterns, with little guidance for Linux developers.
Recommendations
  • Add explicit instructions and examples for Linux development environments, including installation steps for vcpkg and Azure IoT Edge Tools on Linux.
  • Provide Linux-native paths and commands alongside Windows examples (e.g., ~/.local/share/ for templates, bash scripts for vcpkg).
  • Clarify whether Visual Studio for Linux (or Visual Studio Code) can be used for equivalent workflows, and provide guidance for those tools.
  • Include Linux CLI commands and workflows for building, debugging, and deploying modules, not just Docker and Azure CLI steps.
  • Avoid assuming the development machine is Windows; structure prerequisites and steps so both Windows and Linux users are equally supported.
  • List Linux tools and patterns before or alongside Windows tools, rather than as an afterthought.
  • Provide troubleshooting and tips for common Linux-specific issues (e.g., Docker permissions, SSH debugging).
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
High Priority View Details →
Scanned: 2026-01-10 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 Windows bias primarily in the deployment instructions, where only PowerShell and Windows-centric tooling are mentioned and exemplified. The deployment steps explicitly require PowerShell and instruct users to run a PowerShell script, with no mention of Linux shell equivalents or cross-platform alternatives. There are no Bash or Linux-specific instructions, nor is there guidance for users on non-Windows platforms. This may hinder Linux users from following the documentation seamlessly.
Recommendations
  • Provide Linux and macOS deployment instructions alongside Windows/PowerShell steps, including Bash script equivalents if available.
  • Clarify whether the PowerShell script can be run with PowerShell Core on Linux/macOS, and provide installation guidance for those platforms.
  • Offer alternative deployment methods (e.g., Azure CLI only, Bash scripts) for users who do not use PowerShell.
  • Explicitly mention cross-platform compatibility and test instructions on multiple operating systems.
  • Add notes or sections addressing common Linux troubleshooting patterns and tools where relevant.
GitHub Create Pull Request
IoT Edge [Individual enrollment](#tab/individual-enrollment) ...t-edge/includes/iot-edge-create-dps-enrollment-x509.md
High Priority View Details →
Scanned: 2026-01-10 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 page demonstrates Windows bias by providing only PowerShell-based certificate verification commands (e.g., New-CACertsVerificationCert), referencing Windows-style file paths (e.g., <WRKDIR>\certs\...), and omitting equivalent Linux shell or OpenSSL examples. Windows tools and patterns are mentioned exclusively, with no parity for Linux users, which may hinder cross-platform adoption and usability.
Recommendations
  • Provide equivalent Linux shell commands (e.g., using Bash and OpenSSL) for certificate verification and generation steps.
  • Include Linux-style file path examples (e.g., <wrkdir>/certs/...) alongside Windows paths.
  • Mention and demonstrate cross-platform tools or scripts where possible, or clarify platform-specific requirements.
  • Ensure that CLI instructions and examples are shown for both Windows and Linux environments, especially for common tasks like certificate management.
  • Add notes or sections explicitly addressing Linux users, highlighting any differences or additional steps required.
GitHub Create Pull Request
IoT Edge Quickstart: Create an Azure IoT Edge Device on Linux ...e-docs/blob/main/articles/iot-edge/quickstart-linux.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
Although the documentation is focused on Linux, there is some Windows bias present. PowerShell instructions are provided alongside bash/Cloud Shell examples, and the use of the Azure portal (a web interface often associated with Windows workflows) is emphasized for module deployment. The PowerShell example is given after the bash example, but its inclusion may suggest parity is not fully achieved. There are no Linux-specific tools or patterns highlighted beyond basic bash/CLI usage, and the documentation does not mention Linux desktop tools or alternatives to the Azure portal for module deployment. The overall workflow is cloud-centric, but the inclusion of PowerShell and lack of Linux desktop alternatives indicate mild Windows bias.
Recommendations
  • Remove or de-emphasize PowerShell instructions, or provide equivalent instructions for popular Linux shells (e.g., zsh, fish) if relevant.
  • Highlight Linux-native tools or workflows for module deployment, such as using VS Code on Linux or direct CLI-based deployment without the Azure portal.
  • Add instructions for deploying modules using only CLI commands, avoiding reliance on the Azure portal, to better support headless or non-GUI Linux environments.
  • Include troubleshooting steps or tips that are specific to Linux environments, such as using journalctl or systemd for service management.
  • If PowerShell is included, clarify its cross-platform availability and provide guidance for Linux users who may prefer bash or other shells.
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-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a clear Windows bias: all deployment examples and instructions focus exclusively on Windows virtual machines, Windows Server, and Hyper-V. There are no Linux VM examples, nor are Linux hypervisors (such as KVM or VirtualBox) mentioned. Windows tools and patterns (Hyper-V, Windows VM creation, Windows-specific requirements) are referenced throughout, with no parity for Linux environments.
Recommendations
  • Add equivalent instructions for deploying Azure IoT Edge for Linux on Windows using Linux-based hypervisors (e.g., KVM, VirtualBox, VMware on Linux).
  • Include examples and configuration steps for nested virtualization on Linux hosts.
  • Mention Linux networking options and troubleshooting steps analogous to those given for Windows (e.g., configuring bridges, virtual switches on Linux).
  • Clarify whether EFLOW can be deployed on Linux VMs and, if not, explain the limitations.
  • Provide links to Linux documentation and tools where relevant.
GitHub Create Pull Request
← Previous Page 2 of 8 Next →