IoT Operations
245
Total Pages
238
Linux-Friendly Pages
7
Pages with Bias
2.9%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
13 issues found
Showing 1-13 of 13 flagged pages
IoT Operations
Test connectivity to MQTT broker with MQTT clients
...operations/manage-mqtt-broker/howto-test-connection.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Windows First
Summary
The documentation provides generally cross-platform instructions for testing MQTT connectivity, primarily using Kubernetes and Mosquitto clients (which are available on Linux, macOS, and Windows). However, in the section on port forwarding for AKS Edge Essentials, Windows-specific tools and commands (netsh, PowerShell New-NetFirewallRule) are presented exclusively, with no Linux/macOS equivalents or guidance. Additionally, Azure Portal instructions (a web UI) are platform-agnostic, but the order of presentation sometimes puts Windows-centric approaches before Linux-native alternatives.
Recommendations
- For the AKS Edge Essentials port forwarding section, add equivalent Linux/macOS instructions (e.g., using iptables, firewall-cmd, ufw, or other common Linux firewall/port forwarding tools).
- When presenting platform-specific commands (netsh, PowerShell), explicitly note that these are for Windows and provide alternatives for other OSes.
- Where possible, show Linux/macOS examples alongside Windows ones, or link to relevant external documentation for those platforms.
- Consider reordering sections so that cross-platform or Linux-native approaches are presented first, or in parallel tabs.
- Review for other subtle Windows-first language or assumptions and clarify platform applicability.
Create Pull Request
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
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Powershell Heavy
Summary
The documentation page displays a moderate Windows bias. Windows-based OPC UA servers and configuration tools (e.g., KEPServerEx) are mentioned first and exclusively in tips about certificate export, with no Linux server examples. PowerShell commands are provided alongside Bash, and Windows configuration UIs are referenced, while Linux alternatives are not. There are no explicit Linux server-side examples or guidance for common Linux OPC UA servers.
Recommendations
- Include examples and references for exporting certificates from popular Linux-based OPC UA servers (e.g., open62541, Prosys, Unified Automation).
- Mention Linux file paths and certificate management patterns alongside Windows UIs.
- Provide explicit Linux command-line examples for certificate export and management, not just conversion.
- Balance references to Windows tools (KEPServerEx) with Linux alternatives.
- Ensure that Bash and PowerShell examples are presented with equal prominence, and clarify OS applicability.
IoT Operations
Test connectivity to MQTT broker with MQTT clients
...operations/manage-mqtt-broker/howto-test-connection.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Windows First
Summary
The documentation page is generally cross-platform, with most examples using Linux-native tools (kubectl, bash, mosquitto_pub/sub). However, in the section on port forwarding for AKS Edge Essentials, Windows-specific tools and commands (netsh, PowerShell's New-NetFirewallRule) are presented exclusively, with no Linux/macOS equivalents or guidance. Additionally, the AKS Edge Essentials scenario is presented before more general Linux-based port forwarding approaches, which may create friction for non-Windows users.
Recommendations
- Add Linux/macOS equivalents for port forwarding and firewall configuration in the AKS Edge Essentials section (e.g., using iptables, ufw, or firewall-cmd).
- Clarify when Windows-only steps are required, and provide alternative instructions for Linux/macOS users.
- Ensure that cross-platform solutions (such as kubectl port-forward) are presented before platform-specific tools.
- Consider adding a table or callout summarizing platform-specific steps for port forwarding and firewall configuration.
IoT Operations
Tips and tools for troubleshooting Azure IoT Operations
...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 presented immediately after the Linux example and is more verbose. The AKS instructions explicitly require PowerShell, with no mention of Bash or cross-platform alternatives for AKS users. Other sections use Bash/console commands and tools that are cross-platform, but the initial cluster access setup for AKS is Windows/PowerShell-centric.
Recommendations
- Provide Bash equivalents for AKS setup steps, or clarify if PowerShell is required for AKS on Windows only.
- Explicitly mention that AKS users on Linux/macOS can use Bash and provide example commands.
- Where possible, present Linux/macOS and Windows instructions side-by-side, or clarify platform requirements.
- Ensure parity in tool recommendations and examples for both platforms throughout the documentation.
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
Powershell Heavy
Windows First
Summary
The documentation provides both Bash and PowerShell examples for key CLI commands, but PowerShell is given equal prominence and is presented immediately after Bash in each case. There is no explicit Linux bias, but the inclusion of PowerShell examples and tabs may suggest a slight Windows orientation, especially since PowerShell is primarily used on Windows (though available on Linux). No Windows-only tools or patterns are used, and Linux commands (Bash, systemctl, nano) are present and correct.
Recommendations
- Clarify that PowerShell examples are for users who prefer PowerShell, which is available on both Windows and Linux, to avoid implying Windows exclusivity.
- Consider listing Bash examples first, as Bash is the default shell on most Linux/macOS systems.
- Explicitly mention that all CLI commands work identically on Linux, macOS, and Windows (with Azure CLI and PowerShell Core installed).
- Add a note that PowerShell examples are also suitable for Linux/macOS users who use PowerShell Core.
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 configuration tools (e.g., KEPServerEx), and by mentioning Windows configuration UIs before alternatives. PowerShell examples are provided alongside Bash, but there are no explicit Linux/macOS-specific examples or guidance for common Linux OPC UA servers. The documentation does mention cross-platform tools like openssl and kubectl, and most CLI instructions are platform-neutral, but the narrative and examples tend to reference Windows tools and patterns first.
Recommendations
- Include explicit examples for Linux and macOS OPC UA servers, such as guidance for popular open-source servers (e.g., open62541, Prosys, or Unified Automation).
- When mentioning server certificate export, provide Linux/macOS file path examples and reference typical certificate storage locations on those platforms.
- Balance references to Windows-based configuration UIs with equivalent Linux/macOS instructions or screenshots.
- Add more Bash-only examples where PowerShell is not needed, and clarify which commands work on Linux/macOS.
- Where possible, avoid mentioning Windows tools first; present platform-neutral or Linux/macOS instructions before or alongside Windows-specific ones.
IoT Operations
Quickstart: Configure your cluster
.../get-started-end-to-end-sample/quickstart-configure.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides both Bash and PowerShell examples for environment variable setup and cluster configuration, but consistently lists Bash examples before PowerShell. There is no exclusive use of Windows tools, nor are Linux examples missing. No Windows-specific tools or patterns are mentioned, and all instructions are cross-platform.
Recommendations
- Continue providing both Bash and PowerShell examples.
- Explicitly state that all commands work on Linux, macOS, and Windows where applicable.
- Consider alternating the order of Bash and PowerShell examples in different sections to avoid perceived preference.
- Add a note clarifying that the Azure CLI and kubectl commands are fully supported on Linux/macOS.
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 sometimes with more detail. The prerequisites section references Windows and Ubuntu deployments, but Windows is mentioned first. There is no exclusive use of Windows tools, but the presence and ordering of PowerShell examples may subtly favor Windows users.
Recommendations
- Alternate the order of Bash and PowerShell examples, or present Bash first in some sections.
- Explicitly state Linux/macOS compatibility in all command-line instructions.
- Add notes or troubleshooting tips for Linux/macOS users where behaviors may differ.
- Ensure parity in screenshots and UI instructions for Linux/macOS environments if applicable.
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 more verbose. There is a slight bias in the AKS section, which assumes PowerShell usage for Windows users and does not mention Linux AKS scenarios or Bash alternatives for AKS. All other tooling (kubectl, k9s, mosquitto, mqttui, MQTT Explorer) is cross-platform and examples are shown in Bash or generic CLI, with no exclusive Windows tools or patterns. The severity of the bias is low, as Linux users can complete all tasks, but AKS users on Linux may need to adapt the PowerShell example themselves.
Recommendations
- Add Bash/Linux command examples for AKS scenarios, not just PowerShell.
- Explicitly mention that AKS clusters can be managed from Linux/macOS and provide equivalent Bash commands.
- Where PowerShell is used, offer a Bash alternative or clarify OS requirements.
- Ensure that all examples are presented in parallel tabs (Windows/PowerShell and Linux/Bash) for parity.
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 CLI commands, but PowerShell examples are consistently presented after Bash and use Windows-centric syntax (e.g., `$variable=$(...)`), which may not work in native PowerShell. There is a slight Windows bias in the inclusion of PowerShell tabs, but Linux/macOS users are not blocked from completing any tasks, as Bash examples are present and all tooling is cross-platform.
Recommendations
- Clarify that PowerShell examples are intended for Windows users and Bash for Linux/macOS.
- Ensure PowerShell examples use correct syntax for native PowerShell (e.g., use `$variable = ...` instead of `$variable=$(...)`).
- Consider adding explicit Linux/macOS instructions where file paths or editors (e.g., nano) are mentioned.
- Where possible, present Bash and PowerShell examples side-by-side, or default to Bash first for CLI-heavy documentation.
- Add a note at the top specifying that all CLI commands work on Linux/macOS unless otherwise stated.
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 PowerShell examples are shown immediately after Bash, and in some cases, the PowerShell example is more detailed. The prerequisites and deployment instructions mention Windows and Ubuntu/K3s equally, but Windows is listed first. There are no Windows-only tools or commands, and Linux users can follow all steps. However, the order and prominence of Windows/PowerShell examples indicate a mild Windows-first bias.
Recommendations
- Alternate the order of Bash and PowerShell examples, or group them together under a common heading to avoid implying priority.
- Explicitly state that Bash examples work on Linux/macOS and that PowerShell examples are for Windows, to clarify parity.
- Where possible, provide additional context for Linux/macOS users, such as package installation commands or troubleshooting tips.
- Ensure that any references to Windows tools or environments are balanced with Linux/macOS equivalents, especially in prerequisites and deployment sections.
IoT Operations
Quickstart: Configure your cluster
.../get-started-end-to-end-sample/quickstart-configure.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides both Bash and PowerShell examples for environment variable setup and cluster configuration, but consistently lists Bash examples before PowerShell. No Windows-specific tools or patterns are mentioned exclusively, and Linux parity is maintained throughout. There are no sections that are Windows-only, and Linux/macOS users can complete all tasks as described.
Recommendations
- Continue to provide both Bash and PowerShell examples to support cross-platform usage.
- Consider alternating the order of Bash and PowerShell tabs or explicitly stating that both environments are equally supported.
- Add a note clarifying that all commands are cross-platform and tested on both Linux/macOS and Windows.
Low Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation exclusively describes using the Azure portal UI for RBAC role management, which is platform-agnostic. However, it does not mention or provide examples for command-line approaches (such as Azure CLI or PowerShell), nor does it clarify cross-platform tooling. There is no explicit Windows bias, but the lack of Linux/macOS-specific instructions or parity for CLI-based workflows may create friction for non-Windows users who prefer or require command-line automation.
Recommendations
- Add instructions and examples for creating and assigning custom RBAC roles using Azure CLI, which is cross-platform and widely used on Linux/macOS.
- If PowerShell examples are added, ensure Azure CLI equivalents are provided and shown first or side-by-side.
- Clarify that the Azure portal is accessible from any OS with a web browser, and mention cross-platform options for automation.
- Include links to official documentation for Azure CLI and PowerShell RBAC role management.