IoT Operations

99
Total Pages
82
Linux-Friendly Pages
17
Pages with Bias
17.2%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues (25)

https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-operations/deploy-iot-ops/howto-enable-secure-settings.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First
Summary:
The documentation provides both Bash and PowerShell examples for key CLI operations, but PowerShell is given equal prominence to Bash, which can indicate a Windows-centric approach. There are no explicit Linux-only or Windows-only tools, but the inclusion of PowerShell tabs and examples throughout, rather than focusing on Bash (which is more universal across platforms), suggests a slight Windows bias. However, Linux-specific instructions (e.g., editing k3s config with nano, using systemctl) are present, and no steps are missing for Linux users.
Recommendations:
  • List Bash examples before PowerShell, as Bash is available on both Linux and Windows (via WSL or Git Bash), while PowerShell is less common on Linux.
  • Clarify that Bash examples are cross-platform and can be used on Windows via WSL or Git Bash.
  • Consider providing a single Bash example by default, with PowerShell as an optional/secondary tab for Windows users.
  • Explicitly mention that all CLI commands work on Linux, macOS, and Windows (with Bash or PowerShell), to reinforce cross-platform parity.
  • If possible, provide guidance for macOS users as well, or clarify that instructions are valid for both Linux and macOS.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-operations/troubleshoot/troubleshoot.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Windows First Windows Tools Powershell Heavy Missing Linux Example
Summary:
The documentation generally avoids explicit Windows bias in most troubleshooting steps, focusing on cross-platform tools like Azure CLI and kubectl. However, in the section on capturing network packet traces for Layered Network Management, the Windows host instructions (using Wireshark) are presented before the Linux host instructions (using tcpdump), and Wireshark (a GUI Windows tool) is mentioned as the default for opening trace files. There are no PowerShell-specific examples, but the ordering and tool choices show a mild Windows-first and Windows-tools bias. In other sections, Linux-native commands (kubectl, bash) are used, but there are no explicit Linux-first or Linux-only examples, and some steps (e.g., rebooting the host) are generic.
Recommendations:
  • Present Linux and Windows instructions in parallel tabs or sections, or alternate which platform appears first to avoid Windows-first ordering.
  • When suggesting tools for packet capture, mention both Wireshark and tcpdump for both platforms, and clarify that Wireshark is available on Linux as well.
  • Where possible, provide CLI-based alternatives for Windows users (e.g., using tshark or tcpdump on Windows), not just GUI tools.
  • Ensure that all examples and troubleshooting steps are clearly marked as applicable to both Windows and Linux, or provide explicit instructions for both.
  • Consider including a table or matrix summarizing which tools/commands are available on which platforms.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-operations/reference/custom-rbac.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example
Summary:
The documentation exclusively describes how to create and assign custom RBAC roles using the Azure Portal, which is a graphical interface accessible from any OS, but does not mention or provide any command-line examples. There are no references to PowerShell, Windows tools, or CLI commands, but the lack of Azure CLI (cross-platform) or Bash examples means Linux users do not see parity in automation or scripting guidance. The documentation implicitly assumes a GUI-first workflow, which is more common among Windows users.
Recommendations:
  • Add Azure CLI examples for creating and assigning custom roles, as the CLI is cross-platform and widely used on Linux.
  • Include Bash shell command examples for downloading and editing JSON files, to complement the GUI instructions.
  • Explicitly mention that all steps can be performed from any OS using the Azure CLI, and link to relevant CLI documentation.
  • If PowerShell examples are added in the future, ensure equivalent Bash/Azure CLI examples are provided for Linux users.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-operations/manage-layered-network/howto-connect-arc-enabled-servers.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Windows First Powershell Heavy Windows Tools Missing Linux Example
Summary:
The documentation demonstrates a Windows-first bias by presenting the Windows onboarding process and PowerShell script editing steps in detail before the Ubuntu/Linux process. The Windows section includes explicit instructions for modifying and running a PowerShell script, while the Ubuntu section focuses mainly on repository configuration and omits a step-by-step onboarding example. Windows-specific tools (e.g., OnboardingScript.ps1, azcmagent.exe) are highlighted, and there is a lack of parity in Linux onboarding instructions.
Recommendations:
  • Provide a detailed, step-by-step onboarding example for Ubuntu/Linux hosts, including the exact commands to run (e.g., azcmagent connect) and any required parameters or flags, mirroring the detail given for Windows.
  • Include Linux shell script examples or command-line equivalents alongside PowerShell/Windows examples.
  • Present Windows and Linux onboarding instructions in parallel sections or tables to emphasize equal support.
  • Reference both Windows and Linux tools/utilities equally, and avoid assuming the use of Windows-specific scripts or editors.
  • Clarify any differences in onboarding steps between platforms, and ensure that Linux users are not required to infer steps from Windows instructions.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-operations/deploy-iot-ops/howto-manage-update-uninstall.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example
Summary:
The documentation consistently presents Azure CLI and Azure portal instructions, but when referencing command-line usage, it does not provide any OS-specific guidance or examples. There are no explicit Windows-only tools (like PowerShell), but the lack of Linux/macOS-specific notes or examples (such as shell differences, package managers, or environment setup) means Linux users may not have full parity or clarity. The documentation implicitly assumes a Windows or generic environment, with no mention of Linux-specific considerations.
Recommendations:
  • Explicitly mention that Azure CLI commands are cross-platform and provide any OS-specific installation or usage notes, especially for Linux/macOS users.
  • Include examples or notes for common Linux/macOS shell environments (e.g., bash, zsh) where command syntax or environment variables might differ.
  • Add troubleshooting tips or prerequisites for Linux (such as required dependencies or permissions).
  • Reference Linux package managers (apt, yum, etc.) in the Azure CLI installation section.
  • If screenshots or file paths are shown, provide both Windows and Linux/macOS variants where relevant.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-operations/discover-manage-assets/howto-configure-opcua-certificates-infrastructure.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Windows First Windows Tools Powershell Heavy
Summary:
The documentation exhibits a mild Windows bias. Windows-based OPC UA server tools (e.g., KEPServerEx) are mentioned first and specifically, while Linux equivalents are not named. Powershell examples are provided alongside Bash, but Windows UI tools are referenced before generic or Linux alternatives. There is no explicit omission of Linux instructions, but the ordering and tool references prioritize Windows environments.
Recommendations:
  • When mentioning OPC UA server certificate export, provide named examples of Linux-based OPC UA servers and their certificate management methods, not just Windows (e.g., reference open62541, Prosys, or Unified Automation servers).
  • If referencing Windows-based configuration UIs (like KEPServerEx), also mention common Linux server management patterns (e.g., file system paths, command-line tools) with equal prominence.
  • In all sections where Powershell and Bash are shown, ensure Bash appears first or alternate the order to avoid implicit prioritization.
  • Add explicit guidance or links for Linux users on how to locate, export, and manage certificates on popular Linux OPC UA servers.
  • Where possible, avoid phrases like 'Windows-based configuration UI' without balancing with 'Linux-based' or 'cross-platform' alternatives.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-operations/deploy-iot-ops/howto-prepare-cluster.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Windows First Powershell Heavy Windows Tools
Summary:
The documentation provides both Linux (Ubuntu/K3s) and Windows (AKS Edge Essentials) guidance, but there is a notable Windows bias in the ordering, tool recommendations, and example depth. Windows/AKS Edge Essentials is often mentioned before or more prominently than Linux equivalents, and the only automated cluster creation script provided is a PowerShell script for Windows. There is also a lack of parity in automation and scripting examples for Linux users.
Recommendations:
  • Ensure that Linux and Windows instructions are presented with equal prominence, alternating order or grouping by scenario rather than platform.
  • Provide equivalent automation scripts for Linux environments (e.g., a bash script to automate K3s cluster creation and Arc-enablement, similar to the provided PowerShell script for AKS Edge Essentials).
  • Where PowerShell scripts are referenced for Windows, offer bash or shell script alternatives for Linux users.
  • Explicitly state platform limitations or differences (e.g., if a feature is only available on Windows or Linux), and provide guidance for both platforms where possible.
  • Review all sections to ensure that Linux tools and patterns are not omitted or placed after Windows equivalents without justification.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-operations/manage-layered-network/howto-configure-l4-cluster-layered-network.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Windows Tools Missing Linux Example
Summary:
The documentation provides both Linux (K3S/Ubuntu) and Windows (AKS Edge Essentials/Windows 11) setup paths, but there are notable biases. PowerShell syntax is used for environment variable setup and Azure CLI commands even in the Linux/K3S section, which is non-idiomatic for Linux users. Windows-specific tools and commands (e.g., netsh portproxy) are described in detail, while equivalent Linux networking steps (such as iptables or firewall-cmd) are not provided. In several places, Windows instructions are more explicit or appear first. There is also a lack of parity in post-deployment networking configuration for Linux clusters.
Recommendations:
  • Provide Bash syntax for all Azure CLI and environment variable setup steps in the K3S/Linux sections, instead of PowerShell.
  • Include Linux-native networking configuration instructions (e.g., iptables, firewall-cmd) for exposing Kubernetes LoadBalancer services, mirroring the detailed Windows netsh portproxy steps.
  • Ensure that Linux and Windows instructions are presented with equal detail and in parallel, rather than Windows-first or more thoroughly.
  • Add troubleshooting and verification steps for Linux environments where they exist for Windows.
  • Review all command examples to ensure they are idiomatic for the target OS (e.g., avoid PowerShell on Linux).
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-operations/manage-layered-network/howto-configure-l3-cluster-layered-network.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Windows First Powershell Heavy Windows Tools Missing Linux Example
Summary:
The documentation provides both Linux (Ubuntu/K3S) and Windows (AKS Edge Essentials) setup instructions, but there is a noticeable Windows bias in several areas. Powershell and Windows-specific tools and commands are used exclusively or given first in key sections (e.g., Arc-enabling the cluster, network/firewall configuration). Some steps, such as environment variable setup and Azure CLI usage, are only shown in Powershell syntax, with no Bash/Linux equivalents. Windows UI steps for DNS configuration are detailed, while the Linux (Ubuntu) DNS configuration is only briefly described and relies on the UI, not CLI. The network configuration and troubleshooting steps are Windows-centric, and some advanced configuration (firewall, port forwarding) is only shown for Windows.
Recommendations:
  • Provide Bash/Linux equivalents for all Powershell commands, especially for Azure CLI usage, environment variable setup, and Arc-enabling the cluster.
  • Include Linux CLI-based instructions for DNS configuration (e.g., using nmcli or editing /etc/netplan or /etc/resolv.conf), not just Ubuntu UI steps.
  • Offer Linux-native alternatives for Windows-only tools and commands (e.g., netsh, New-NetFirewallRule), such as iptables or ufw for firewall rules and socat or iptables for port forwarding.
  • Ensure that troubleshooting and verification steps (e.g., checking service IPs, verifying DNS) are shown with Linux commands as well as Windows.
  • Present both Linux and Windows instructions in parallel or in clearly separated tabs, rather than defaulting to Windows-first or Windows-only examples in shared sections.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-operations/troubleshoot/tips-tools.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Windows First Powershell Heavy
Summary:
The documentation provides both Linux (Ubuntu/k3s) and Windows (AKS/PowerShell) examples for configuring kubectl access, but the Windows/PowerShell example is presented after the Linux example and is clearly labeled for AKS. The PowerShell example is more complex and uses Windows-specific scripting, which could be seen as a bias if Linux/Bash alternatives for AKS are not provided. However, the rest of the documentation uses cross-platform tools and Bash/console commands, with no exclusive reliance on Windows tools or patterns.
Recommendations:
  • For the AKS section, provide both PowerShell and Bash (or Azure Cloud Shell) command examples, as AKS can be managed from Linux/macOS as well as Windows.
  • Clearly indicate that both Linux and Windows clients can be used for AKS, and provide parity in scripting examples.
  • Where possible, use cross-platform commands first (e.g., Azure CLI, Bash), and include PowerShell as an alternative, not the default.
  • Review other sections for any implicit assumptions about the user's OS, and ensure that instructions are inclusive of both Linux and Windows environments.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-operations/discover-manage-assets/howto-use-media-connector.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Windows First Powershell Heavy
Summary:
The documentation provides both Bash and PowerShell examples for all major workflows, but consistently presents Bash (Linux/macOS) instructions before PowerShell (Windows). There are no exclusive Windows tools or patterns, and no steps are missing for Linux users. However, the PowerShell examples are present throughout, which may be seen as a mild Windows bias, though not at the expense of Linux parity. No Windows-only tools or instructions are given, and Linux command-line tools (e.g., wget, base64, kubectl, az CLI) are used throughout.
Recommendations:
  • Maintain the current structure of providing both Bash and PowerShell examples for all workflows.
  • Consider clarifying in the introduction that both Linux/macOS and Windows are fully supported, and that users should select the tab that matches their environment.
  • Ensure that any troubleshooting or advanced scenarios also include both Bash and PowerShell examples, if applicable.
  • If possible, add explicit notes about cross-platform compatibility for tools like az CLI and kubectl, to reassure users on both platforms.
  • Continue to avoid Windows-only tools or patterns unless a Linux equivalent is also provided.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-operations/deploy-iot-ops/howto-manage-update-uninstall.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Missing Linux Example
Summary:
The documentation is generally cross-platform in its use of the Azure CLI, which is available on both Windows and Linux. However, there are no explicit Linux-specific examples, shell commands, or references to Linux environments. All CLI examples use the generic Azure CLI syntax, but there are no examples showing Linux shell usage (e.g., bash scripting, environment variables, or file paths), nor is there mention of Linux-specific considerations. There is also no mention of PowerShell or Windows-specific tools, so there is no overt Windows bias, but Linux parity could be improved.
Recommendations:
  • Add explicit Linux shell (bash) examples where relevant, such as using environment variables or piping output.
  • Include notes or examples for running Azure CLI commands in Linux terminals, especially for commands involving file paths or output redirection.
  • Mention that the Azure CLI commands work identically on Linux, macOS, and Windows, and provide any OS-specific caveats if they exist.
  • Where file paths or directories are referenced (e.g., --to-dir), clarify the syntax for both Windows and Linux.
  • If screenshots or UI references are shown, consider including examples from both Windows and Linux environments where applicable.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-operations/discover-manage-assets/howto-configure-opcua-certificates-infrastructure.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Windows First Windows Tools Powershell Heavy
Summary:
The documentation displays a mild Windows bias. Windows-based OPC UA server tools (such as KEPServerEx) are mentioned explicitly and before Linux alternatives. Powershell examples are provided alongside Bash, and Windows-specific patterns (such as referencing Windows-based configuration UIs) are called out, while Linux equivalents are not mentioned with equal prominence. There are no explicit Linux-only examples or references to Linux-native OPC UA servers or their certificate management interfaces.
Recommendations:
  • When mentioning OPC UA server certificate export, provide examples or references for both Windows-based (e.g., KEPServerEx) and popular Linux-based OPC UA servers (e.g., open62541, Prosys, Unified Automation), including their certificate management interfaces.
  • Balance the mention of Windows tools with Linux equivalents. For example, if referencing a Windows configuration UI, also mention typical Linux file paths or CLI tools for certificate management.
  • If Powershell is shown, ensure Bash or Linux shell examples are always present and given equal or greater prominence, possibly listing Bash first.
  • Consider adding a table or section summarizing certificate export/import steps for both Windows and Linux OPC UA servers.
  • Explicitly state that the instructions are cross-platform and highlight any platform-specific steps or differences.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-operations/deploy-iot-ops/howto-prepare-cluster.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Windows Tools Powershell Heavy Windows First
Summary:
The documentation provides detailed, step-by-step instructions and command-line examples for Ubuntu (Linux) and TKG, but for Windows-based AKS Edge Essentials, it only references a PowerShell script (AksEdgeQuickStartForAio.ps1) and links to external instructions, rather than providing equivalent inline steps or command breakdowns. The Windows/AKS Edge Essentials section is less detailed and relies on a Windows-specific automation tool (PowerShell script), indicating a reliance on Windows tooling and patterns. Additionally, AKS Edge Essentials (Windows) is listed before Azure Local and TKG in the tab order, suggesting a mild 'windows_first' ordering.
Recommendations:
  • Provide detailed, step-by-step instructions for AKS Edge Essentials (Windows) inline, similar to the Ubuntu and TKG sections, rather than only referencing an external PowerShell script.
  • Where possible, break down what the PowerShell script does into individual steps or commands, so users can understand and replicate the process manually if needed.
  • If there are any manual or CLI-based alternatives to the PowerShell script for Windows, document those as well.
  • Ensure that Linux and Windows instructions are given equal prominence and detail, and consider alternating the order of tabs or sections to avoid implicit prioritization.
  • If possible, provide parity in troubleshooting, configuration, and advanced options for both Linux and Windows environments.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-operations/discover-manage-assets/howto-manage-assets-remotely.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Missing Linux Example Windows First
Summary:
The documentation page provides instructions for managing asset configurations in Azure IoT Operations, focusing on the operations experience web UI and the Azure CLI. While the CLI commands are cross-platform, there is a notable absence of explicit Linux/macOS-specific guidance or examples. The documentation assumes the use of the Azure CLI without clarifying installation or usage differences between Windows and Linux environments. Additionally, there are no references to Linux-native tools, shell environments, or potential platform-specific considerations, and the only sign-in instructions reference the Azure portal, which is platform-agnostic but often associated with Windows-centric workflows.
Recommendations:
  • Explicitly mention that the Azure CLI commands work on Windows, Linux, and macOS, and provide installation links or instructions for each platform.
  • Include example CLI commands using both Windows (cmd/PowerShell) and Linux/macOS (bash/zsh) shell syntax where relevant, especially for environment variable usage or file paths.
  • Add troubleshooting tips or notes for common Linux/macOS issues (e.g., file permissions, case sensitivity, CLI authentication differences).
  • Reference Linux-native tools or workflows where appropriate (e.g., using curl, jq, or other common utilities for automation or scripting).
  • Ensure screenshots and UI references are not Windows-specific, or provide clarifying notes if the UI differs on other platforms.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-operations/end-to-end-tutorials/tutorial-add-assets.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Windows First Powershell Heavy
Summary:
The documentation demonstrates some Windows bias by presenting PowerShell and Bash command examples side-by-side, but consistently lists Bash first. However, the PowerShell examples are present throughout, and there is no exclusive use of Windows tools or patterns. The prerequisites and deployment instructions mention both Windows (Azure Kubernetes Service Edge Essentials) and Ubuntu (K3s), but the Windows option is listed before Ubuntu. There are no missing Linux examples, and most commands are cross-platform (kubectl, wget, Azure CLI).
Recommendations:
  • Alternate the order of Bash and PowerShell examples to avoid implicit prioritization.
  • Explicitly state that all command-line examples are cross-platform unless otherwise noted.
  • Where possible, provide a single, unified example if the command is identical in both environments.
  • Ensure that Linux and Windows deployment options are given equal prominence, or alternate which is listed first.
  • Add a note clarifying that the Azure CLI and kubectl commands work on both Windows and Linux.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-operations/manage-mqtt-broker/howto-test-connection.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Windows Tools Powershell Heavy Windows First
Summary:
The documentation is generally cross-platform and Linux-oriented, using Linux-native tools (kubectl, bash, mosquitto_pub/sub, wget) and Kubernetes YAML/Bicep for most examples. However, in the section on port forwarding with AKS Edge Essentials, Windows-specific tools and commands (netsh, New-NetFirewallRule in PowerShell) are presented exclusively, with no Linux equivalents or guidance for non-Windows users. Additionally, the Windows approach is described in more detail and appears before any mention of Linux alternatives, which are not provided.
Recommendations:
  • For every Windows-specific command (e.g., netsh, New-NetFirewallRule), provide equivalent Linux/macOS commands (e.g., iptables, firewall-cmd, ufw) and instructions.
  • Explicitly mention cross-platform alternatives for port forwarding and firewall configuration, such as using ssh port forwarding or Linux firewall tools.
  • Where possible, structure sections so that Linux and Windows approaches are presented in parallel or with equal prominence, rather than Windows-first.
  • Add a table or callout summarizing how to perform port forwarding and firewall changes on both Windows and Linux/macOS.
  • Consider including a note that AKS Edge Essentials is Windows-only, but if Linux-based edge Kubernetes is used, provide guidance for that scenario.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-operations/manage-layered-network/howto-configure-l3-cluster-layered-network.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Windows First Powershell Heavy Windows Tools Missing Linux Example
Summary:
The documentation provides both Linux (Ubuntu/K3S) and Windows (AKS Edge Essentials) setup instructions, but there is a noticeable Windows bias in several areas. Windows-specific tools and instructions (e.g., PowerShell, Windows Control Panel, netsh, New-NetFirewallRule) are detailed, especially in network and firewall configuration, without equivalent Linux guidance. The Arc-enablement and network configuration steps are shown primarily with PowerShell and Windows command-line tools, and there are missing or less detailed Linux equivalents for these steps. Additionally, PowerShell is used for Azure CLI commands even in sections that could be cross-platform.
Recommendations:
  • Provide Linux (bash) equivalents for all PowerShell and Windows command-line examples, especially for Azure CLI, environment variable setting, and network/firewall configuration.
  • Include instructions for configuring firewalls and port forwarding on Linux (e.g., using ufw, iptables, or firewalld) alongside the Windows-specific steps.
  • When presenting cross-platform commands (like az CLI), use bash syntax and variables in parallel with PowerShell, or default to bash for neutrality.
  • Ensure that Linux UI and CLI methods for DNS configuration are as detailed as the Windows UI steps.
  • Avoid using Windows-first ordering in sections that are not inherently OS-specific; consider presenting Linux and Windows instructions in parallel tabs or sections.
  • Review for any other Windows-only tools or terminology and provide Linux alternatives where possible.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-operations/manage-layered-network/howto-configure-l4-cluster-layered-network.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Windows Tools Missing Linux Example
Summary:
The documentation provides both Linux (K3S/Ubuntu) and Windows (AKS Edge Essentials/Windows 11) setup instructions in parallel tabs. However, there are several signs of Windows bias: PowerShell is used for all variable and Azure CLI command examples (even in the Linux/K3S section), Windows-specific tools and commands (like netsh portproxy) are described in detail, and some steps (like port mapping) are only documented for Windows with no Linux equivalent or guidance. Additionally, PowerShell syntax is used for environment variables and Azure CLI commands in the Linux section, which is not idiomatic for Linux users.
Recommendations:
  • Provide Bash shell examples for all Azure CLI and environment variable commands in the K3S/Linux sections, using standard Linux syntax (e.g., export VAR=value).
  • Document the equivalent port mapping steps for Linux hosts (e.g., using iptables or firewalld) when exposing Kubernetes LoadBalancer services, not just for Windows/netsh.
  • Ensure that Linux tools and patterns are described with equal detail and priority as Windows tools (e.g., explain how to check service accessibility and configure networking on Linux).
  • Avoid using PowerShell syntax in Linux sections; use Bash or sh syntax instead.
  • If a step is only required for Windows, explicitly state the Linux equivalent is not needed or provide alternative instructions.
  • Review all code blocks and outputs to ensure they are platform-appropriate for the section they appear in.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-operations/manage-layered-network/howto-configure-aks-edge-essentials-layered-network.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Windows First Windows Tools Powershell Heavy
Summary:
The documentation demonstrates a mild Windows bias by consistently mentioning Windows and Windows-based tools (AKS Edge Essentials, Windows 11) before Linux equivalents (K3S, Ubuntu), and by referencing Windows-specific patterns and tools (e.g., AKS Edge Essentials, which is Windows-centric). While Linux options are present, they are often secondary, and there is a lack of parity in detail and ordering between Windows and Linux instructions.
Recommendations:
  • Ensure that Linux-based examples (K3S/Ubuntu) are given equal prominence and are not consistently listed after Windows/AKS Edge Essentials.
  • Where possible, provide parallel step-by-step instructions for both Windows and Linux environments, rather than combining or sequencing them with Windows first.
  • Avoid language that implies Windows is the default or preferred environment (e.g., 'set up a Windows 11 machine and configure AKS Edge Essentials or set up K3S Kubernetes on an Ubuntu machine'). Instead, present both options neutrally and in parallel.
  • Include explicit Linux command-line examples (e.g., bash commands) where Windows/PowerShell commands are referenced, to ensure parity.
  • Where Windows-specific tools or services are mentioned (such as AKS Edge Essentials), ensure Linux alternatives are described with equal detail and clarity.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-operations/manage-layered-network/howto-connect-arc-enabled-servers.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Windows First Powershell Heavy Windows Tools
Summary:
The documentation presents the Windows onboarding process before the Ubuntu/Linux process, provides a detailed PowerShell script example for Windows but omits a corresponding Linux/Ubuntu command-line example, and references Windows-specific tools (e.g., OnboardingScript.ps1, azcmagent.exe with Windows paths). This may make the documentation less accessible for Linux users and suggests a Windows-centric approach.
Recommendations:
  • Present Windows and Linux/Ubuntu onboarding instructions in parallel sections or alternate the order to avoid always listing Windows first.
  • Provide equivalent command-line examples for Ubuntu/Linux, such as the azcmagent connect command with Linux paths and syntax.
  • Reference Linux-specific tools and scripts where applicable, or clarify if the same agent and commands are used across platforms.
  • Ensure that any PowerShell-specific instructions are matched with bash or shell script examples for Linux.
  • Explicitly state any differences or similarities in the onboarding process between Windows and Linux to help users understand platform parity.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-operations/manage-layered-network/includes/retirement-notice.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Missing Linux Example
Summary:
The documentation page does not provide any platform-specific examples or guidance, but it also does not mention or provide Linux-specific instructions or parity. The absence of any examples or tool references means Linux users are not directly supported or acknowledged.
Recommendations:
  • Add explicit instructions or references for both Windows and Linux environments if platform-specific steps are required.
  • If the linked sample or guidance is cross-platform, clarify this in the documentation.
  • Include at least one example or note on how to implement layered network management on Linux systems, or state explicitly if the guidance is platform-agnostic.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-operations/manage-layered-network/howto-configure-layered-network.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Windows First Windows Tools Missing Linux Example
Summary:
The documentation demonstrates a Windows bias by listing Windows 11 machines first and more frequently in network topology examples, specifying Windows 11 as the OS for most nodes, and providing more detail for Windows-based setups. Linux is only mentioned as a DNS server host or in Azure VM scenarios, and there are no examples or instructions for setting up the environment with Linux endpoints outside of DNS. There are no PowerShell or Windows command-line examples, but the network design and narrative center Windows as the default endpoint OS.
Recommendations:
  • Provide parallel examples where Linux is used as the endpoint OS in network diagrams and explanations, not just as a DNS server.
  • When listing machines in subnets, alternate the order or provide both Windows and Linux options equally.
  • Include explicit instructions or references for setting up the environment with Linux-only endpoints, not just for DNS or Azure VMs.
  • If mentioning Windows 11, also mention popular Linux distributions (e.g., Ubuntu, CentOS) as alternatives for the same role.
  • Ensure that any tooling or configuration steps that are OS-specific have both Windows and Linux variants, or clarify when steps are OS-agnostic.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-operations/reference/custom-rbac.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Missing Linux Example
Summary:
The documentation provides only Azure Portal (web UI) instructions for managing custom RBAC roles and does not include any command-line examples. There is no explicit Windows bias (such as PowerShell or Windows tools), but the absence of CLI examples (e.g., Azure CLI, which is cross-platform and commonly used on Linux) means Linux users do not have parity with users who prefer or require command-line workflows.
Recommendations:
  • Add Azure CLI examples for creating and assigning custom RBAC roles, as the Azure CLI is cross-platform and widely used on Linux.
  • If relevant, include Azure PowerShell examples as well, but ensure Azure CLI instructions are presented first or alongside PowerShell to avoid Windows-first bias.
  • Explicitly mention that the Azure Portal is accessible from any OS, but provide alternative instructions for users who prefer or require command-line or automated workflows.
  • Where possible, link to official Azure documentation for both CLI and PowerShell methods.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-operations/troubleshoot/tips-tools.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Windows First Powershell Heavy
Summary:
The documentation provides both Linux (Ubuntu/k3s) and Windows (AKS/PowerShell) examples for configuring kubectl access, but the Windows/PowerShell example is given equal prominence and is not clearly secondary. In the AKS section, PowerShell is used exclusively, with no CMD or Bash alternative for Windows users or for cross-platform parity. However, the rest of the documentation uses cross-platform or Linux-oriented tools and commands (kubectl, bash, mosquitto, mqttui), and there are no exclusive references to Windows-only tools or patterns.
Recommendations:
  • For the AKS example, provide both PowerShell and Bash/CMD alternatives, or clarify when PowerShell is required versus optional.
  • Consider presenting Linux/Bash examples first, or side-by-side with Windows/PowerShell, to avoid implicit prioritization of Windows.
  • Explicitly mention that most kubectl and MQTT client commands are cross-platform and runnable on both Windows and Linux, and provide guidance for users on both systems.
  • If PowerShell is used, note how to adapt the commands for Bash or CMD, or link to external resources for cross-platform command translation.