IoT Operations
159
Total Pages
139
Linux-Friendly Pages
20
Pages with Bias
12.6%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
68 issues found
Showing 51-68 of 68 flagged pages
IoT Operations
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-operations/discover-manage-assets/howto-use-media-connector.md
...ns/discover-manage-assets/howto-use-media-connector.md
Medium Priority
View Details →
Detected Bias Types
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.
Create Pull Request
IoT Operations
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-operations/discover-manage-assets/howto-manage-assets-remotely.md
...discover-manage-assets/howto-manage-assets-remotely.md
Medium Priority
View Details →
Detected Bias Types
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.
IoT Operations
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-operations/end-to-end-tutorials/tutorial-add-assets.md
...operations/end-to-end-tutorials/tutorial-add-assets.md
Medium Priority
View Details →
Detected Bias Types
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.
IoT Operations
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-operations/troubleshoot/tips-tools.md
...ain/articles/iot-operations/troubleshoot/tips-tools.md
Medium Priority
View Details →
Detected Bias Types
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.
IoT Operations
Tutorial: Bi-directional MQTT bridge to Azure Event Grid
...ot-operations/connect-to-cloud/tutorial-mqtt-bridge.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Bash and PowerShell examples for all Azure CLI commands, ensuring parity for Linux/macOS and Windows users. However, in each code section, PowerShell examples are consistently shown after Bash, and PowerShell is given equal prominence throughout. There are no Windows-only tools or patterns, and no steps that require Windows-specific software. The only minor bias is the consistent inclusion of PowerShell examples, which may slightly favor Windows users by making their experience more seamless.
Recommendations
- Maintain Bash examples as the default/first shown for CLI commands, as Bash is cross-platform.
- Consider explicitly stating that all CLI commands work on Linux, macOS, and Windows (with PowerShell).
- If possible, add a note for macOS users regarding any platform-specific caveats (none detected here, but good practice).
- Ensure future updates do not introduce Windows-only tools or instructions.
IoT Operations
Enable Secure Settings to a Test Instance
...rations/deploy-iot-ops/howto-enable-secure-settings.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Bash and PowerShell examples for key commands, but PowerShell is presented as a primary tab alongside Bash, which may suggest a Windows-first approach. There are no Linux-specific tools or patterns missing, and the instructions for k3s cluster configuration and service management use Linux-native commands (nano, systemctl). However, the presence of PowerShell examples and tabs may indicate a slight bias towards Windows users.
Recommendations
- Present Bash examples first, as Bash is the default shell on most Linux/macOS systems.
- Clarify that PowerShell examples are for Windows users, and Bash for Linux/macOS.
- Consider adding explicit notes about platform compatibility for each example.
- If possible, include macOS-specific notes or troubleshooting tips.
- Ensure that all steps (especially those involving Azure CLI) are tested and confirmed to work on Linux/macOS as well as Windows.
IoT Operations
Configure OPC UA certificates
...https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-operations/discover-manage-assets/howto-configure-opc-ua-certificates-infrastructure.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Powershell Heavy
Summary
The documentation page exhibits mild Windows bias, primarily through repeated references to Windows-based OPC UA server tools (KEPServerEx) and configuration UIs, and by mentioning Windows options before Linux alternatives. PowerShell examples are provided alongside Bash, but no macOS-specific guidance is given. The use of Azure CLI and Kubernetes tools is cross-platform, and Bash examples are present throughout, but Windows-centric references may create friction for Linux/macOS users.
Recommendations
- Add explicit examples or references for Linux and macOS OPC UA server certificate export workflows, such as typical file paths or commands.
- Mention popular Linux OPC UA servers (e.g., open62541, Prosys, Unified Automation) and how to export certificates from them.
- Provide macOS-specific notes where relevant, especially for file handling and CLI usage.
- Ensure that non-Windows tools and interfaces are mentioned with equal prominence to Windows ones.
- Where PowerShell is used, clarify that Bash commands are suitable for both Linux and macOS, and consider adding zsh/fish shell notes if relevant.
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Bash and PowerShell examples for key command-line steps, but consistently lists PowerShell examples immediately after Bash, and includes full PowerShell syntax for certificate manipulation. There is some subtle Windows-first bias in the deployment overview, which mentions Windows before Ubuntu, and references Azure Kubernetes Service Edge Essentials (Windows) before K3s (Linux). No critical steps are Windows-only, and Linux users can complete all tasks, but the ordering and inclusion of PowerShell may create minor friction.
Recommendations
- Alternate the order of Bash and PowerShell examples, or group them together to avoid implicit prioritization.
- Explicitly state Linux/macOS compatibility in the prerequisites and throughout the tutorial.
- Provide additional context or troubleshooting tips for Linux users, especially for certificate management and secret handling.
- Ensure that Linux tools and patterns (e.g., Bash, K3s) are mentioned first or equally alongside Windows equivalents.
- Consider including macOS-specific notes if relevant.
IoT Operations
Quickstart: Configure your cluster
.../get-started-end-to-end-sample/quickstart-configure.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Bash and PowerShell examples for environment variable setup and cluster configuration, but consistently lists Bash first. There is no exclusive use of Windows tools or commands, and Linux users are not blocked from completing any steps. However, the inclusion of PowerShell examples and explicit mention of PowerShell as an option may indicate a slight Windows bias, especially since macOS/Linux users are expected to use Bash. No Linux-specific tools or patterns are omitted, and all commands are cross-platform.
Recommendations
- Explicitly state that Bash examples apply to both Linux and macOS, and PowerShell is for Windows.
- Consider listing Bash and PowerShell examples in random or alternating order to avoid perceived prioritization.
- Add a note clarifying that all commands are cross-platform and tested on both Linux/macOS and Windows.
- If possible, provide a single set of commands that work identically on all platforms to reduce duplication.
IoT Operations
Tips and tools for troubleshooting Azure IoT Operations
...ain/articles/iot-operations/troubleshoot/tips-tools.md
Low Priority
View Details →
Detected Bias Types
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 second and is clearly labeled as requiring PowerShell. There is a slight bias in that the AKS instructions assume PowerShell usage, which may not be ideal for Linux users running AKS. However, the overall documentation is balanced, with most command-line examples using bash and Linux tools, and MQTT troubleshooting instructions are platform-agnostic.
Recommendations
- Clarify that AKS clusters can be managed from Linux/macOS as well, and provide equivalent bash examples for AKS where possible.
- Explicitly mention that PowerShell is required only on Windows, and offer bash alternatives for all steps.
- Ensure that all major workflows (especially those for AKS) have both Windows/PowerShell and Linux/bash examples side-by-side.
- Consider listing Linux/bash instructions first if the majority of users are expected to be on Linux/macOS.
IoT Operations
Tutorial: Bi-directional MQTT bridge to Azure Event Grid
...ot-operations/connect-to-cloud/tutorial-mqtt-bridge.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Bash and PowerShell examples for all Azure CLI commands, ensuring parity for Linux/macOS and Windows users. However, in each code section, the Bash example is shown first, followed by PowerShell, which is a minor 'windows_first' bias. There is no evidence of exclusive use of Windows tools, missing Linux examples, or Windows-only patterns. The use of Azure CLI throughout is cross-platform, and Kubernetes examples are provided for deployment and configuration steps. No critical steps are Windows-only.
Recommendations
- Continue providing both Bash and PowerShell examples for all CLI commands.
- Consider alternating the order of Bash and PowerShell tabs, or defaulting to Bash for cloud-native tutorials.
- Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows to reassure non-Windows users.
- Ensure that any future troubleshooting or advanced sections do not introduce Windows-only tools or patterns.
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides both Bash and PowerShell examples for command-line operations, and explicitly states that commands can be run in either environment. However, in the prerequisites section, Windows is mentioned before Ubuntu when describing deployment options, and Azure Kubernetes Service Edge Essentials (a Windows-focused solution) is listed before K3s (Linux). There are no sections that are Windows-only, and Linux users are given parity in examples and instructions.
Recommendations
- List Linux/Ubuntu deployment options before or alongside Windows options to avoid perceived prioritization.
- Ensure that any references to tools or environments (e.g., Azure Kubernetes Service Edge Essentials) are balanced with Linux equivalents.
- Continue providing both Bash and PowerShell examples for all command-line instructions.
- Explicitly mention macOS compatibility where applicable, if supported.
IoT Operations
Enable Secure Settings to a Test Instance
...rations/deploy-iot-ops/howto-enable-secure-settings.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Bash and PowerShell examples for critical Azure CLI commands, but consistently lists Bash first. PowerShell examples are included for Windows users, but there are no examples or notes for Linux/macOS-specific shell environments beyond Bash. No Windows-only tools or patterns are present, and the Azure CLI is cross-platform. The severity of bias is low, as Linux/macOS users can follow all instructions without friction.
Recommendations
- Explicitly state that Bash examples apply to Linux/macOS and Windows (via WSL or Git Bash), and PowerShell examples are for Windows.
- Consider adding a note clarifying that Azure CLI commands work identically on Linux, macOS, and Windows.
- If relevant, provide Zsh or other shell examples, or clarify that Bash syntax is portable.
- Ensure parity in troubleshooting steps or environment setup for Linux/macOS (e.g., permissions, file paths).
IoT Operations
Quickstart: Configure your cluster
.../get-started-end-to-end-sample/quickstart-configure.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Bash and PowerShell examples for environment variable setup and cluster configuration, but consistently lists Bash examples first. PowerShell is included as a separate tab, ensuring Windows users are supported, but there is no evidence of exclusive use of Windows tools or commands. All commands are cross-platform (kubectl, az CLI, wget/Invoke-WebRequest). No Linux/macOS functionality is missing, and no Windows-specific tools are required.
Recommendations
- Continue providing both Bash and PowerShell examples in parallel.
- Explicitly mention that all commands are cross-platform and supported on Linux/macOS and Windows.
- Consider listing Bash and PowerShell tabs in alphabetical order or randomizing their order to avoid implicit prioritization.
- Add a note clarifying that Linux/macOS users should use Bash and Windows users can use either Bash (via WSL) or PowerShell.
IoT Operations
Tips and tools for troubleshooting Azure IoT Operations
...ain/articles/iot-operations/troubleshoot/tips-tools.md
Low Priority
View Details →
Detected Bias Types
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 instructions are presented immediately after the Linux section and are more verbose. The PowerShell example is detailed and uses Windows-specific scripting, while the Linux example uses standard bash commands. There is no explicit prioritization, but Windows/PowerShell is given equal prominence and detail. The rest of the documentation uses cross-platform tools (kubectl, k9s, mosquitto, mqttui, MQTT Explorer) and shell commands, which are platform-agnostic.
Recommendations
- Ensure that Linux/macOS instructions are presented first or side-by-side with Windows instructions, especially in sections where both are relevant.
- For PowerShell-heavy examples, provide equivalent bash/zsh commands for Linux/macOS users.
- Clearly label which instructions are for which platform, and avoid implying that Windows/PowerShell is the default or preferred environment.
- Where possible, add explicit macOS notes if any commands or tools require adaptation.
- Consider summarizing platform parity at the start of the page to reassure users that all major OSes are supported.
IoT Operations
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-operations/deploy-iot-ops/howto-manage-update-uninstall.md
...ations/deploy-iot-ops/howto-manage-update-uninstall.md
Low Priority
View Details →
Detected Bias Types
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.
IoT Operations
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-operations/manage-layered-network/includes/retirement-notice.md
...s/manage-layered-network/includes/retirement-notice.md
Low Priority
View Details →
Detected Bias Types
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.
IoT Operations
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-operations/reference/custom-rbac.md
.../main/articles/iot-operations/reference/custom-rbac.md
Low Priority
View Details →
Detected Bias Types
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.