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 101-125 of 184 flagged pages
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 →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation is heavily biased towards Windows, providing only PowerShell commands and Windows-specific tools (such as Hyper-V, Windows DHCP Server, and Windows networking cmdlets) for creating a virtual switch for Azure IoT Edge for Linux on Windows. There are no Linux or cross-platform examples, and the instructions assume the user is operating entirely within a Windows environment. Linux alternatives or equivalent commands are not mentioned or referenced.
Recommendations
- Add a section or references for how to create and configure virtual switches, NAT, and DHCP on Linux hosts (e.g., using iproute2, dnsmasq, or NetworkManager).
- Include Linux command-line examples alongside PowerShell commands where applicable, or clarify that the process is only supported on Windows if that is the case.
- Mention and link to Linux-native virtualization solutions (such as KVM, libvirt, or VirtualBox) and how to achieve similar networking setups for IoT Edge for Linux scenarios.
- Clearly state in the prerequisites and introduction if the process is only intended for Windows users, and provide guidance or links for Linux users.
- Consider providing a comparison table of Windows and Linux tools/commands for each step, to help users translate the instructions to their platform.
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 →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation provides both Ubuntu and Windows instructions for installing CA certificates, but Windows instructions are generally more detailed, include multiple methods (PowerShell, certlm GUI, .NET API), and mention Windows-specific tools (Schannel, certlm, Import-Certificate) before or in greater depth than Linux equivalents. The .NET section emphasizes Windows parity, and Windows-specific TLS stack (Schannel) is discussed in detail, while Linux alternatives are mentioned only briefly. There is no explicit Linux bias, but the Windows ecosystem receives more attention and tool coverage.
Recommendations
- Ensure Linux (and macOS, if relevant) instructions are as detailed as Windows, including multiple methods (e.g., using update-ca-certificates, trust, or keytool for Java).
- Provide parity in troubleshooting and tool references: mention Linux TLS stack details (e.g., OpenSSL, GnuTLS) and how to verify certificate installation on Linux.
- In .NET and C SDK sections, clarify Linux-specific behaviors and provide Linux-oriented code/configuration examples where appropriate.
- When listing tools or methods, alternate the order or present Linux and Windows approaches side by side to avoid 'Windows first' bias.
- Expand on Linux-specific certificate management (e.g., using update-ca-certificates, trust anchors, or Java's cacerts) and provide links to official documentation.
- Where Windows tools like certlm or Schannel are mentioned, provide equivalent Linux commands or references (e.g., update-ca-certificates, openssl, or system trust store locations).
IoT Edge
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-edge/debug-module-vs-code.md
...cs/blob/main/articles/iot-edge/debug-module-vs-code.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. Windows is mentioned first in several key sections, such as development machine requirements and Docker Desktop prerequisites. There are references to Windows-specific tools and scenarios (e.g., IoT Edge for Linux on Windows/EFLOW), and PowerShell-style output is shown in code blocks. While Linux is supported and mentioned, Linux-specific instructions, troubleshooting, or examples are less prominent, and some examples (such as Docker output) use Windows-style prompts. There are also cases where Linux-specific nuances (like permissions or package installation) are not addressed, and Linux command-line examples are not always provided alongside Windows ones.
Recommendations
- Ensure Linux and macOS are mentioned before or alongside Windows in all prerequisites and setup sections.
- Provide explicit Linux (and macOS, if supported) command-line examples and troubleshooting steps, especially for Docker and SSH usage.
- Avoid using Windows-style prompts (e.g., 'PS C:\>') in code blocks unless also showing the equivalent Linux prompt.
- Include Linux-specific notes for permissions (e.g., sudo usage, Docker group membership) and package installation where relevant.
- Balance references to Windows-only tools (like EFLOW) with equivalent Linux-native workflows.
- Where possible, use cross-platform language and avoid assuming the user is on Windows.
- Add a section or callouts for common Linux/macOS issues or environment differences.
IoT Edge
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-edge/how-to-configure-multiple-nics.md
...in/articles/iot-edge/how-to-configure-multiple-nics.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation is heavily focused on Windows and PowerShell tooling for configuring multiple NICs in 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 examples or cross-platform alternatives. The Linux environment is only referenced as the guest OS inside the VM, not as a host or as a platform for performing configuration tasks.
Recommendations
- Provide equivalent Linux command-line instructions (e.g., using Azure CLI, SSH, or Linux-native tools) for each step where possible.
- Include examples of how to perform network configuration from a Linux host, or clarify that the process is only supported on Windows hosts.
- Mention and, if possible, demonstrate how to use cross-platform tools (such as Azure CLI) for VM and network interface management.
- Reorganize the documentation to clarify the platform requirements up front and avoid assuming a Windows-only environment.
- If PowerShell is required, note whether PowerShell Core (cross-platform) can be used, and provide instructions for Linux users where applicable.
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 →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation provides both Linux and Windows (specifically EFLOW) instructions, but the Windows/PowerShell tooling is emphasized for EFLOW scenarios. Several steps for EFLOW require the use of custom PowerShell cmdlets (e.g., Copy-EflowVMFile, Connect-EflowVm, Invoke-EflowVmCommand), and these tools are referenced before or instead of standard cross-platform alternatives. The Linux path uses standard Bash commands, while the Windows/EFLOW path assumes the user is operating from a Windows host using PowerShell, potentially limiting accessibility for users on non-Windows platforms. There is also a slight 'windows_first' bias in the EFLOW sections, where Windows-specific instructions and tools are introduced before cross-platform or Linux-native alternatives.
Recommendations
- Where possible, provide cross-platform alternatives to PowerShell cmdlets for EFLOW, such as using SSH/SCP from Linux/macOS hosts to the EFLOW VM.
- Clarify that EFLOW is a Windows-specific scenario, but highlight how similar tasks can be accomplished from non-Windows hosts if possible.
- In the EFLOW sections, mention standard Linux tools (e.g., scp, ssh) as alternatives to PowerShell cmdlets for copying files and executing commands, or explain any limitations.
- Ensure that Linux and Windows instructions are presented with equal prominence and detail, and avoid assuming the user is operating from a Windows host when working with EFLOW.
- Consider adding a table or section summarizing all possible ways (Windows/PowerShell, Linux/SSH, etc.) to interact with the EFLOW VM for certificate management and port configuration.
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 →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation provides parallel instructions for both Windows and Linux, but consistently presents Windows instructions before Linux in every section. Windows examples use PowerShell scripts and commands extensively, including Windows-specific tools like vcpkg and PowerShell cmdlets (e.g., Set-ExecutionPolicy, Write-Host, Get-Pfxcertificate), while Linux instructions use bash scripts. Some Windows-specific installation guidance (such as vcpkg for OpenSSL) is more detailed than the Linux equivalent. There are no major missing Linux examples, but the ordering and tool emphasis reflect a Windows-first and PowerShell-heavy bias.
Recommendations
- Alternate the order of Windows and Linux sections in each major heading, or present Linux first in some sections to balance perceived priority.
- Where possible, provide equal detail for Linux installation steps (e.g., recommend package managers like apt, yum, or dnf for OpenSSL installation).
- Avoid using Windows-specific tools (like vcpkg) as the 'recommended' method without offering a Linux equivalent or a cross-platform alternative.
- Where PowerShell cmdlets are used for certificate inspection (e.g., Get-Pfxcertificate), provide equivalent Linux commands (e.g., openssl) and highlight them equally.
- Consider a unified table or tabbed interface that does not always default to Windows as the first or primary example.
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 →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation provides a PowerShell example for deriving a device key, explicitly referencing Windows, but does not provide equivalent Linux or cross-platform command-line examples (e.g., Bash, OpenSSL, Python). This creates a bias toward Windows users and may hinder Linux users from following the instructions easily.
Recommendations
- Add a Linux/Bash example for deriving the device key, using common tools like openssl or a Python script.
- Present both Windows (PowerShell) and Linux (Bash/Python) examples side by side, or use tabbed sections for each platform.
- Avoid language such as 'On Windows...' unless there is a corresponding 'On Linux...' section.
- Where possible, use cross-platform tools or scripts, or at least reference them.
- Explicitly mention that the process can be performed on both Windows and Linux, and provide links to relevant tools or documentation for each.
IoT Edge
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-edge/how-to-update-iot-edge.md
.../blob/main/articles/iot-edge/how-to-update-iot-edge.md
High Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows Tools
Windows First
Summary
The documentation is heavily focused on Linux-based IoT Edge deployments, with detailed step-by-step instructions and examples for Ubuntu/Debian and RHEL. Windows is only mentioned to state that native Windows containers are not supported and to redirect users to Linux containers or EFLOW (IoT Edge for Linux on Windows). There are no PowerShell or Windows command examples, but the lack of Windows-native instructions and the explicit direction to use Linux containers on Windows devices indicate a bias toward Linux. The documentation also references Linux tools and patterns (systemctl, apt-get, yum) exclusively, and troubleshooting commands are only shown for Linux environments.
Recommendations
- If Windows-native IoT Edge is not supported, clarify this at the top of the article and provide a clear migration or alternative path for Windows users.
- If EFLOW is the only supported method on Windows, include a summary of EFLOW update steps or a direct link to equivalent update documentation, rather than just a reference.
- If/when Windows-native support returns, add equivalent PowerShell or Windows command-line examples for all update and troubleshooting steps.
- Ensure that all references to tools and commands are clearly scoped to the relevant OS, and provide parity in troubleshooting and verification steps for EFLOW/Windows scenarios.
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 →
Detected Bias Types
Windows Tools
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page exhibits Windows bias by referencing Windows-style paths (e.g., <WRKDIR>\certs\...), using a PowerShell command (New-CACertsVerificationCert) without providing a Linux/bash equivalent, and omitting Linux-specific instructions or examples. File path examples and tooling references are Windows-centric, and there is no mention of Linux shell commands or cross-platform alternatives.
Recommendations
- Provide Linux/bash equivalents for all PowerShell commands, such as OpenSSL commands for certificate operations.
- Include Linux-style file path examples (e.g., <WRKDIR>/certs/...) alongside Windows paths.
- Explicitly mention cross-platform compatibility for scripts and tools, or provide links to Linux-compatible versions.
- Add notes or tabs for Linux users where steps or commands differ, ensuring parity in instructions.
- Where possible, use platform-neutral language and examples, or clearly indicate when instructions are platform-specific.
IoT Edge
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-edge/security.md
...ocs/azure-docs/blob/main/articles/iot-edge/security.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation generally maintains a cross-platform tone but demonstrates subtle Windows bias in the 'Encryption at rest' section. Here, BitLocker (a Windows-specific tool) is explicitly recommended for Windows, while Linux is mentioned generically with no specific tools or examples provided. This prioritizes a Windows solution and leaves Linux users without concrete guidance or parity in recommendations.
Recommendations
- Provide specific Linux encryption tools (e.g., LUKS, dm-crypt, eCryptfs) alongside BitLocker, and link to their documentation.
- Offer example commands or configuration steps for both Windows (BitLocker) and Linux (e.g., setting up LUKS).
- Ensure that, where platform-specific recommendations are made, both Windows and Linux are treated equally in detail and prominence.
- Consider listing Linux options before or alongside Windows options to avoid 'windows_first' ordering.
- Review other sections for similar patterns and ensure parity in tool recommendations and examples across platforms.
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 →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Summary
While the tutorial is primarily Linux-focused for the actual IoT Edge device setup, there is evidence of Windows bias in several areas: directory and command output examples use Windows paths and PowerShell formatting, Windows-specific tools and documentation links are referenced before or instead of Linux equivalents, and some instructions assume familiarity with Windows environments. However, the core configuration and deployment steps are Linux-centric.
Recommendations
- Provide Linux shell (bash) output examples alongside or instead of PowerShell/Windows examples, especially for directory listings and file operations.
- When referencing documentation for opening ports or configuring VMs, include both Windows and Linux links (e.g., link to Linux NSG quickstart, not just Windows).
- Ensure that all example paths and commands are shown in both Windows and Linux formats, or default to Linux if the tutorial is Linux-focused.
- Avoid using PowerShell-specific output (e.g., 'PS C:\nested-edge\output> dir') unless also providing the equivalent Linux command ('ls ./output').
- In troubleshooting and configuration sections, clarify any OS-specific steps and provide parity for both Windows and Linux users.
- Review all screenshots and code snippets to ensure they are representative of the intended platform (Linux in this case), or provide both variants.
IoT Edge
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-edge/nested-virtualization.md
...s/blob/main/articles/iot-edge/nested-virtualization.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation is heavily focused on Windows-based virtualization environments and tools (Hyper-V, Windows VMs, Windows Server, Windows 10/11), with no mention of Linux-based virtualization options or examples. All setup instructions, requirements, and troubleshooting are centered on Windows, and there are no Linux equivalents or guidance for Linux-first users.
Recommendations
- Include examples and instructions for deploying Azure IoT Edge for Linux on Windows using Linux-based hypervisors (e.g., KVM, QEMU, VirtualBox on Linux hosts).
- Provide parity in documentation by listing Linux options alongside Windows options, not just as an afterthought.
- Add troubleshooting and configuration notes relevant to Linux virtualization environments.
- Clarify in the introduction whether Linux hosts are supported or not, and if not, provide a rationale or roadmap.
- If the product is truly Windows-only, make this explicit and consider linking to Linux-native IoT Edge deployment docs for Linux users.
IoT Edge
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-edge/quickstart.md
...s/azure-docs/blob/main/articles/iot-edge/quickstart.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation is heavily focused on Windows, specifically on deploying Azure IoT Edge for Linux on Windows (EFLOW). All installation and configuration steps are provided exclusively for Windows using PowerShell commands and Windows-specific tools (e.g., Hyper-V, MSI installers). There are no equivalent instructions or examples for setting up IoT Edge on native Linux devices, nor are Linux command-line alternatives provided for installation or configuration. Linux commands only appear for module management after the Windows-based EFLOW VM is running.
Recommendations
- Add a parallel quickstart or clearly linked section for native Linux devices, including prerequisites, installation, and configuration steps using Linux commands (e.g., apt, yum, systemctl).
- Provide Linux shell (bash) command equivalents alongside PowerShell commands where possible, especially for steps like downloading and installing the IoT Edge runtime.
- Mention Linux-native virtualization/containerization requirements (e.g., Docker, containerd) and how to prepare a Linux host for IoT Edge.
- Balance the order of presentation: if both Windows and Linux are supported, present both options equally or provide a clear choice at the start.
- Explicitly state that this quickstart is for Windows hosts only, and link prominently to Linux-native instructions if available.
IoT Edge
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-edge/tutorial-develop-for-linux.md
...b/main/articles/iot-edge/tutorial-develop-for-linux.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation demonstrates a Windows-first bias in several areas: it explicitly states that the tutorial uses a Windows computer, provides Windows paths and commands before Linux equivalents, and references Windows-specific tools and patterns (such as Docker Desktop for Windows and Windows Subsystem for Linux). While it mentions Linux and macOS, Linux-specific instructions and examples are often less detailed or are referenced as external links. There is also a tendency to present Windows installation steps and terminology before Linux alternatives, and some environment variable examples and path conventions are Windows-centric. No PowerShell-specific commands are present, but the overall flow and examples assume a Windows development environment.
Recommendations
- Provide parallel, side-by-side instructions and examples for Linux (and macOS) wherever Windows-specific steps, paths, or tools are mentioned. For example, show both Windows and Linux commands for creating directories, setting environment variables, and file paths.
- Avoid stating that the tutorial 'uses a Windows computer' as the default; instead, clarify that the steps apply equally to Windows, Linux, and macOS, and highlight any differences as needed.
- When referencing Docker Desktop, include explicit instructions for Docker Engine on Linux, and clarify when WSL is required or optional.
- Ensure that environment variable instructions and path conventions are shown for both Windows (%APPDATA%\Python) and Linux/macOS (~/.local/), not just one or the other.
- Wherever possible, avoid Windows-centric terminology (such as 'command prompt') in favor of cross-platform terms (such as 'terminal').
- Add Linux/macOS-specific troubleshooting tips and common issues, not just those relevant to Docker Desktop on Windows.
- Consider using tabs or callouts to separate Windows and Linux/macOS instructions, so users can easily follow the steps for their platform.
IoT Edge
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-edge/how-to-visual-studio-develop-module.md
...ticles/iot-edge/how-to-visual-studio-develop-module.md
High Priority
View Details →
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 and usage instructions (e.g., vcpkg, Visual Studio, .bat scripts, Windows file paths), and references Windows tools and patterns throughout. Linux alternatives are mentioned only in passing or as secondary options, and Linux-specific instructions/examples are largely missing or deferred to other documents. The CLI and Docker workflows are described, but the primary flow is tightly coupled to Windows and Visual Studio, with minimal guidance for Linux developers.
Recommendations
- Provide explicit Linux development instructions alongside Windows steps, including installation of dependencies (e.g., vcpkg on Linux, Docker on Linux, Visual Studio alternatives).
- Avoid assuming the development machine is Windows; instead, offer parallel prerequisites and setup for both Windows and Linux.
- Include Linux shell command examples (e.g., bash equivalents for vcpkg bootstrap, file paths, and Docker commands).
- Reference and link to Linux-native development tools (e.g., Visual Studio Code, cross-platform CLI tools) earlier and with equal prominence.
- Ensure all code snippets and file paths are provided in both Windows and Linux formats where applicable.
- Clarify which features or tools are Windows-only and suggest Linux alternatives or workarounds.
- Encourage use of cross-platform tools and document any limitations or differences in workflow for Linux users.
IoT Edge
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-edge/troubleshoot.md
...azure-docs/blob/main/articles/iot-edge/troubleshoot.md
High Priority
View Details →
Detected Bias Types
Windows First
Cmd Examples
Missing Linux Example
Summary
The documentation generally uses cross-platform commands (iotedge, docker, az) and mostly shows bash examples, which are suitable for Linux. However, there are several instances where Windows command prompt (cmd) syntax is shown (e.g., iotedge logs <container name>, docker rm --force <container name>, iotedge restart <container name>), and these are presented without equivalent Linux/bash examples. In some sections, the cmd syntax is shown first or exclusively, and there is a lack of explicit Linux-specific troubleshooting steps or notes, which may confuse Linux users. There is also a lack of clarity on platform-specific differences (e.g., service management, log locations, or permissions), and the documentation does not mention or address Linux-specific tools or patterns.
Recommendations
- For every command shown in cmd syntax, provide the equivalent bash/Linux command, and clearly label which platform each example is for.
- If a command is cross-platform (e.g., iotedge, docker), use bash syntax by default, as most IoT Edge deployments are on Linux, or show both bash and cmd examples side by side.
- Add a section or notes about platform-specific differences, such as service management (systemctl vs. Windows Services), log file locations, and permissions.
- Avoid using 'cmd' code blocks unless the command is truly Windows-only; otherwise, prefer 'bash' or 'shell' for cross-platform commands.
- Include troubleshooting steps or tips that are specific to Linux environments, such as checking systemd service status, journalctl logs, or SELinux/AppArmor issues.
- Review the order of examples and ensure Linux is not deprioritized in favor of Windows.
IoT Edge
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-edge/troubleshoot-common-errors.md
...b/main/articles/iot-edge/troubleshoot-common-errors.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation generally provides Linux-centric troubleshooting steps and examples (e.g., bash commands, Linux file paths), but there are several instances of Windows bias. Windows-specific networking patterns (NAT), error messages, and VM hostname issues are described in detail, sometimes before or instead of Linux equivalents. Some troubleshooting steps reference Azure Portal or Visual Studio Code workflows that may be more familiar to Windows users. There are also error messages and solutions that are specific to Windows (e.g., HNS/Win32 errors, Windows VM hostname length), while Linux alternatives are not always equally detailed. There are no PowerShell examples, but some Windows-specific terminology and patterns are prioritized or explained first.
Recommendations
- For every Windows-specific error or solution (e.g., NAT networking, HNS/Win32 errors), provide a Linux equivalent or clarify if the issue is exclusive to Windows.
- When describing networking or deployment patterns, present Linux and Windows approaches side by side, or clarify which applies to which OS.
- Where Azure Portal or Visual Studio Code workflows are described, include CLI or config-file-based alternatives that are OS-agnostic.
- For error messages or logs that are Windows-specific, provide Linux log examples or clarify if the issue manifests differently on Linux.
- Ensure that Linux troubleshooting steps are as detailed as Windows ones, especially for common issues like port conflicts, DNS, and network configuration.
IoT Edge
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-edge/tutorial-store-data-sql-server.md
...in/articles/iot-edge/tutorial-store-data-sql-server.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a mild Windows bias. While the tutorial is primarily focused on Linux containers and mentions Linux as the default/primary target, there are several instances where Windows is mentioned first or Windows-specific tools and patterns are referenced without providing equivalent Linux examples. For example, the prerequisites list both Linux and Windows device setup links, but the Windows link is listed second. The command to check module status uses a combined 'cmd/sh' code block, but does not provide explicit Linux shell examples or clarify differences. The documentation also references Visual Studio Code (a cross-platform tool), but does not mention any Linux-specific editors or command-line alternatives. There are no PowerShell-specific commands, but the overall pattern assumes familiarity with Windows-centric workflows.
Recommendations
- Ensure Linux examples are always present and, where possible, listed before or alongside Windows examples, especially since the tutorial is focused on Linux containers.
- When referencing commands (e.g., 'iotedge list'), provide explicit Linux shell examples and clarify any differences for Windows users.
- Include alternative instructions for users who may prefer Linux-native editors or command-line tools, not just Visual Studio Code.
- Where Windows tools or patterns are mentioned, provide equivalent Linux alternatives or clarify cross-platform compatibility.
- Review the order of device setup links and instructions to avoid subtle prioritization of Windows over Linux.
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 →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation provides both Linux and Windows (specifically IoT Edge for Linux on Windows/EFLOW) instructions, but Windows/PowerShell-specific tooling and workflows are heavily emphasized in the EFLOW sections. PowerShell cmdlets (e.g., Copy-EflowVMFile, Connect-EflowVm, Invoke-EflowVmCommand) are used exclusively for file transfer and port management on EFLOW, with no mention of alternative Linux-native or cross-platform methods. The EFLOW (Windows) instructions are more detailed in terms of Windows-specific tooling, and PowerShell is presented as the primary interface for EFLOW management, which may disadvantage users more familiar with Linux-native workflows. The Linux instructions are present and functional, but the Windows/PowerShell approach is more prominent and sometimes appears first or with more detailed steps.
Recommendations
- For EFLOW, provide alternative instructions using standard SSH/SCP/SFTP for file transfer and remote command execution, not just PowerShell cmdlets, to support users on non-Windows platforms or those preferring Linux-native tools.
- Where PowerShell is used for port management (e.g., opening ports with Invoke-EflowVmCommand), offer equivalent instructions for users who may access EFLOW via SSH or other means.
- Clarify that PowerShell cmdlets are one option and that standard Linux tools can also be used within the EFLOW VM, making the documentation more inclusive for Linux users.
- Consider presenting Linux-native instructions first or in parallel, rather than defaulting to Windows/PowerShell-centric workflows for EFLOW.
- Explicitly mention cross-platform alternatives and note any limitations or prerequisites for each approach.
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 →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation consistently presents Windows instructions and examples before Linux ones, uses PowerShell-specific scripts and commands heavily, and references Windows-specific tools (such as vcpkg and PowerShell cmdlets) without always providing equivalent Linux context or alternatives. While Linux instructions are present and generally complete, the overall structure and emphasis favor Windows users.
Recommendations
- Alternate the order of Windows and Linux sections throughout the documentation, or present both platforms side-by-side where feasible.
- Where Windows-specific tools (like vcpkg or PowerShell cmdlets) are mentioned, provide equivalent Linux package manager commands (e.g., apt, yum) and bash alternatives.
- Ensure that all prerequisite steps (such as installing OpenSSL) are equally detailed for Linux, including common installation commands for major distributions.
- Where possible, use cross-platform language and avoid assuming PowerShell as the default shell. Highlight bash and POSIX-compliant alternatives.
- Consider providing a summary table of commands for both platforms at the end of each major section for quick reference.
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 →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation is heavily focused on Windows, providing only Windows-specific instructions and PowerShell commands for creating a virtual switch, NAT, and DHCP server. There are no Linux equivalents or cross-platform guidance, despite the topic being related to 'IoT Edge for Linux on Windows'. All tooling and examples are Windows/PowerShell-centric, and Linux networking tools or commands are not mentioned at all.
Recommendations
- Add a section or parallel instructions for performing similar networking setup (virtual switch, NAT, DHCP) on Linux hosts using common Linux tools (e.g., ip, brctl, dnsmasq, systemd-networkd).
- Clarify in the introduction that the instructions are Windows-only, and provide links or references for Linux users if applicable.
- Where possible, provide conceptual parity by describing what each step accomplishes in platform-agnostic terms before showing Windows-specific commands.
- If the product is only supported on Windows hosts, explicitly state this limitation and explain why Linux host instructions are not included.
- Include a comparison table or FAQ addressing differences between Windows and Linux networking setup for IoT Edge scenarios.
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 →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a bias toward Windows environments by exclusively providing PowerShell-based deployment instructions and referencing PowerShell as a prerequisite, without offering equivalent Bash or Linux shell examples. There is no mention of Linux-specific tools or deployment patterns, and the sample deployment script is only provided for PowerShell, which may hinder accessibility for Linux or macOS users.
Recommendations
- Provide equivalent Bash shell deployment instructions and scripts for Linux/macOS users alongside PowerShell examples.
- List both PowerShell and Bash as prerequisites, with installation links for each platform.
- Explicitly mention cross-platform compatibility of the deployment scripts, or provide separate scripts for Windows (PowerShell) and Linux/macOS (Bash).
- Include notes or callouts clarifying any platform-specific steps or differences.
- Ensure that screenshots and instructions referencing terminal commands or environments are inclusive of both Windows and Linux/macOS users.
IoT Edge
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-edge/how-to-update-iot-edge.md
.../blob/main/articles/iot-edge/how-to-update-iot-edge.md
High Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows Tools
Windows First
Summary
The documentation is heavily focused on Linux-based IoT Edge deployments, with detailed step-by-step instructions and examples for Ubuntu/Debian and RHEL. Windows is only mentioned to state that native Windows containers are not supported and to direct users to use Linux containers (EFLOW) on Windows. There are no PowerShell or Windows command-line examples, but also no native Windows instructions or parity. The troubleshooting and update commands are all Linux-centric. The only Windows-specific content is a note about lack of support and a pointer to a separate EFLOW page.
Recommendations
- If Windows support is not available, clarify this at the top of the page and remove the Windows tab to avoid confusion.
- If EFLOW (IoT Edge for Linux on Windows) is the only supported scenario, provide a summary of the EFLOW update process or link to the EFLOW update guide more prominently.
- If/when Windows-native support is added, ensure that all update, verification, and troubleshooting steps are provided with both Windows (PowerShell/cmd) and Linux (bash) examples.
- For parity, consider providing a table or matrix at the top summarizing which OSes are supported and linking to the relevant instructions.
- Explicitly state that all commands are for Linux unless otherwise noted, to avoid confusion for Windows users.
IoT Edge
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-edge/nested-virtualization.md
...s/blob/main/articles/iot-edge/nested-virtualization.md
High Priority
View Details →
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 virtual machines and hypervisors (Hyper-V, VMware with Windows VMs, Azure VMs with Windows). All configuration steps, requirements, and references are tailored to Windows environments, with no mention of Linux-based virtualization hosts, tools, or workflows. There are no examples or instructions for deploying EFLOW on Linux hosts or using Linux-native hypervisors (e.g., KVM, QEMU), and all tooling and troubleshooting guidance is Windows-centric.
Recommendations
- Add equivalent deployment instructions for Linux-based virtualization hosts (e.g., Ubuntu with KVM/QEMU, or other popular Linux distributions).
- Provide Linux-native examples for enabling nested virtualization and configuring networking for EFLOW.
- Include troubleshooting notes and requirements specific to Linux environments.
- Reference Linux tools and commands (e.g., virsh, virt-manager) alongside or before Windows tools where applicable.
- Clarify in the introduction whether Linux host support is possible or not, and if not, explain the limitation.
IoT Edge
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-edge/how-to-visual-studio-develop-module.md
...ticles/iot-edge/how-to-visual-studio-develop-module.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation page demonstrates a strong Windows bias. It assumes the development machine is Windows, provides only Windows-specific installation commands (e.g., vcpkg bootstrap with .bat, use of Visual Studio, Windows file paths), and references Windows tools and patterns (e.g., Developer Command Prompt, Visual Studio Solution Explorer) without offering equivalent Linux instructions or examples. Linux is mentioned primarily as a target for deployment, not as a development environment. There are no Linux shell commands for setup, no Visual Studio for Linux guidance, and no parity in tool installation or usage instructions.
Recommendations
- Provide explicit instructions for setting up the development environment on Linux, including installation of Visual Studio Code or other supported IDEs, and relevant extensions.
- Include Linux shell command examples for all setup steps (e.g., vcpkg installation, Docker installation, Azure CLI installation).
- Offer Linux file path examples alongside Windows paths, especially for template and project locations.
- Clarify which features and workflows are available or not available on Linux, and offer alternatives where possible.
- Add screenshots and walkthroughs for Linux-based development, including debugging and deployment.
- Where Windows-only tools are referenced (e.g., Visual Studio 2022), suggest cross-platform alternatives or note the limitations for Linux users.
- Rephrase the prerequisites to not assume Windows as the default, or provide parallel Linux sections.
- Ensure all CLI commands are shown in both Windows (cmd/PowerShell) and Linux (bash) syntax.