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 26-50 of 68 flagged pages
IoT Operations
Tutorial: Bi-directional MQTT bridge to Azure Event Grid
...ot-operations/connect-to-cloud/tutorial-mqtt-bridge.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Bash and PowerShell examples for all Azure CLI commands, but consistently lists Bash first and PowerShell second. There is no evidence of exclusive Windows tools or patterns, nor are Linux examples missing. However, the presence of PowerShell examples throughout and the explicit tab for PowerShell may indicate a slight Windows bias, especially since PowerShell is primarily a Windows shell (though available on Linux). No Windows-only tools or instructions are present, and Linux parity is generally maintained.
Recommendations
- Clarify that PowerShell examples work on both Windows and Linux (since PowerShell Core is cross-platform), or explicitly mention this in the prerequisites.
- Consider adding a note for users on macOS/Linux that Bash is the recommended shell, and for Windows users that both Bash (via WSL) and PowerShell are supported.
- Ensure that any future instructions or troubleshooting steps do not assume Windows-only environments (e.g., avoid referencing Windows-specific paths or GUI tools).
- If possible, provide examples for other common shells (e.g., zsh, fish) or clarify that Bash examples are compatible with these shells.
- Explicitly state shell requirements in the prerequisites section to help users choose the correct tab for their environment.
Create Pull Request
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Bash and PowerShell examples for certificate management and secret patching, but PowerShell commands are presented alongside Bash rather than as secondary or alternative options. In the prerequisites, Windows deployment options are mentioned before Ubuntu, and Azure Kubernetes Service Edge Essentials (Windows) is listed before K3s (Linux). There are no Linux-specific tools or troubleshooting steps, and the use of PowerShell may suggest a slight preference for Windows environments. However, most command-line examples use cross-platform tools (kubectl, wget), and the tutorial generally supports both platforms.
Recommendations
- Explicitly state Linux and Windows parity in all command-line sections, and clarify which commands are for which OS.
- Provide Linux-first ordering in deployment instructions or alternate between Windows and Linux to avoid implicit prioritization.
- Add troubleshooting steps or tips specific to Linux environments (e.g., file permissions, shell differences).
- Include references to Linux-native tools (e.g., curl as an alternative to wget) and clarify any PowerShell-specific syntax.
- Ensure screenshots and UI instructions are not Windows-centric (e.g., avoid showing only Windows-style paths or environments).
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation exclusively describes using the Azure portal (web UI) to manage custom RBAC roles, without mentioning or providing examples for command-line tools such as Azure CLI or PowerShell. There are no Linux-specific instructions or parity for non-GUI workflows, and no mention of cross-platform automation or scripting options. This implicitly favors Windows users, who are more likely to use the portal and PowerShell, and omits guidance for Linux users who may prefer Azure CLI or automation.
Recommendations
- Add instructions and examples for managing custom RBAC roles using Azure CLI, which is cross-platform and widely used on Linux.
- Include PowerShell examples if relevant, but ensure Azure CLI examples are presented first or alongside them.
- Explicitly mention that all steps can be performed on Linux, macOS, and Windows using CLI tools.
- Provide sample commands for downloading, editing, and uploading JSON role definitions using CLI tools.
- Reference documentation for Azure CLI role management commands (e.g., 'az role definition create', 'az role assignment create').
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 instructions are presented immediately after the Linux section and use PowerShell-specific syntax. There is a slight 'windows_first' bias in the ordering and prominence of the AKS/PowerShell example, and the use of PowerShell may be less familiar to Linux users. However, most other tooling (kubectl, k9s, mosquitto, mqttui, MQTT Explorer) is cross-platform and examples are generally shell-agnostic or Linux-oriented. No major Linux examples are missing, and Linux tools are well represented.
Recommendations
- Ensure both Linux and Windows instructions are presented with equal prominence, possibly by using tabs or side-by-side formatting.
- Explicitly mention that PowerShell commands are for Windows users and provide bash equivalents for all steps where possible.
- Add a note clarifying which operating system each example is intended for, and ensure Linux examples are not presented as secondary.
- Where possible, provide cross-platform commands or highlight differences in command syntax between platforms.
- Consider starting with Linux/bash examples if the majority of Kubernetes users are on Linux, or alternate the order in different sections.
IoT Operations
Tutorial: Bi-directional MQTT bridge to Azure Event Grid
...ot-operations/connect-to-cloud/tutorial-mqtt-bridge.md
Medium 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 between Linux and Windows users. However, in each code section, the PowerShell tab is presented immediately after Bash, and the PowerShell syntax is given equal prominence throughout. There are no Linux-specific tools, patterns, or troubleshooting steps; all examples use Azure CLI, which is cross-platform. No Windows-only tools or exclusive PowerShell features are used, but the consistent inclusion of PowerShell examples and their order may reflect a subtle Windows-first bias.
Recommendations
- Consider listing Bash examples before PowerShell in tab order, as Bash is the default shell on most Linux and macOS systems.
- Add explicit notes clarifying that all Azure CLI commands work identically on Linux, macOS, and Windows, and that Bash syntax is suitable for Linux/macOS terminals.
- Include troubleshooting or environment setup notes for Linux users (e.g., installing Azure CLI on Ubuntu, using kubectl on Linux).
- Where possible, provide examples using native Linux tools or idioms (e.g., using grep, jq, or other shell utilities for output parsing).
- Ensure that any references to the Azure portal or GUI tools do not assume Windows usage (e.g., avoid mentioning Edge/IE-specific features).
IoT Operations
Enable Secure Settings to a Test Instance
...rations/deploy-iot-ops/howto-enable-secure-settings.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides both Bash and PowerShell examples for key commands, but PowerShell is given equal prominence, and its inclusion suggests a bias toward Windows environments. The use of PowerShell tabs and examples may imply a Windows-first approach, especially since PowerShell is primarily used on Windows, even though it is available cross-platform. There are no explicit Linux-only examples or Linux-first instructions, and the documentation does not mention Linux-specific tools or patterns beyond Bash. However, the overall instructions are largely cross-platform due to the reliance on Azure CLI and Kubernetes tools.
Recommendations
- Clarify that Bash examples are suitable for Linux/macOS environments and PowerShell for Windows, and explicitly state platform applicability for each example.
- Consider providing Linux-specific troubleshooting tips or notes, especially for file editing and service management (e.g., alternatives to 'nano' for editing config files).
- Add a note about PowerShell Core availability on Linux/macOS, or suggest Bash as the default for non-Windows users.
- Ensure that Linux tools and patterns (such as systemd, nano, etc.) are explained or alternatives are provided for Windows users.
- Review the order of example tabs: consider listing Bash first to reflect the prevalence of Linux in cloud-native and Kubernetes environments.
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Bash and PowerShell examples for certificate management and other command-line steps, but PowerShell examples are consistently presented immediately after Bash, and sometimes with more detail. The deployment overview lists Windows (Azure Kubernetes Service Edge Essentials) before Ubuntu (K3s), and Windows is mentioned explicitly in several places. There are no Linux-only examples, and no Linux-specific troubleshooting or tool recommendations. The documentation does not mention Linux equivalents for Windows-specific tools or patterns, and the overall flow assumes parity but subtly prioritizes Windows environments.
Recommendations
- Alternate the order of Bash and PowerShell examples, or provide Bash examples first in some sections to avoid implicit prioritization of Windows.
- Explicitly state Linux support and provide troubleshooting steps or tips for common Linux environments (e.g., Ubuntu, CentOS).
- Include references to Linux-specific tools or patterns where relevant, such as using 'nano' or 'vim' for editing files, or 'systemctl' for service management.
- Ensure that deployment instructions and prerequisites mention Linux options with equal prominence and detail as Windows options.
- Add a note clarifying that all command-line examples work equally well on Linux and Windows, and highlight any platform-specific caveats.
- Consider providing a dedicated Linux quickstart or section for users deploying on Linux environments.
Medium 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 but typically accessed from Windows environments. There are no examples or instructions for using CLI tools (such as Azure CLI or PowerShell), and no mention of Linux-specific workflows or tools. This omission may disadvantage Linux users who prefer command-line automation or scripting, as only the portal workflow is documented.
Recommendations
- Add examples for creating and assigning custom RBAC roles using Azure CLI commands, which are cross-platform and widely used on Linux.
- If relevant, include PowerShell examples but ensure Azure CLI examples are presented first or alongside them.
- Explicitly mention that the Azure portal is accessible from any OS, and provide links to CLI documentation for users on Linux or macOS.
- Consider adding a section comparing portal, CLI, and PowerShell workflows for role management, highlighting cross-platform options.
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 (bash) and Windows/AKS (PowerShell) examples for configuring kubectl access, but the AKS/PowerShell instructions are presented second, and the PowerShell example is more verbose and detailed. There is a slight Windows bias in the explicit mention of opening a PowerShell prompt and the use of Windows-specific scripting constructs, while Linux instructions use standard bash. However, most other tooling (kubectl, k9s, mosquitto, mqttui, MQTT Explorer) is cross-platform and the examples are generally platform-agnostic.
Recommendations
- Present Linux and Windows instructions in parallel (side-by-side tabs or sections) to avoid implicit prioritization.
- Clarify that AKS can be managed from Linux as well, and provide bash equivalents for PowerShell commands where possible.
- Explicitly mention that tools like kubectl, k9s, mosquitto, mqttui, and MQTT Explorer are available on both platforms, and link to installation instructions for both.
- Where PowerShell is used, offer bash alternatives for Linux users, especially for scripting or token extraction steps.
- Review screenshots and UI instructions to ensure they are not Windows-centric (e.g., referencing Windows terminal features or file paths).
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
Windows First
Summary
The documentation provides a generally cross-platform approach, 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 (netsh, PowerShell New-NetFirewallRule) are mentioned exclusively, with no Linux equivalents or parity guidance. Additionally, the AKS Edge Essentials port forwarding section appears before any mention of Linux alternatives, which may reinforce a Windows-first perspective for users of AKS Edge Essentials.
Recommendations
- For every Windows-specific tool or command (such as netsh and New-NetFirewallRule), provide equivalent Linux commands (such as iptables, firewall-cmd, or ufw) for port forwarding and firewall configuration.
- Explicitly mention that AKS Edge Essentials can be run on Linux and provide guidance for Linux users in the relevant sections.
- Where platform-specific instructions are required, use tabbed content or clear headings to separate Windows and Linux workflows.
- Review the ordering of platform-specific instructions to ensure Linux options are presented with equal prominence and not only after Windows solutions.
- Add troubleshooting notes for Linux users in AKS Edge Essentials scenarios, especially regarding port forwarding and firewall setup.
IoT Operations
Troubleshoot Azure IoT Operations
...n/articles/iot-operations/troubleshoot/troubleshoot.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page provides troubleshooting guidance for Azure IoT Operations but demonstrates Windows bias by referencing Azure CLI commands and portal steps without clarifying Linux compatibility or providing Linux-specific examples. All CLI examples use generic 'az' commands, but there is no mention of Linux shell differences, nor are there any PowerShell-specific commands. However, instructions for portal navigation and screenshots implicitly assume a Windows-centric workflow, and there is no explicit mention of Linux tools, shell environments, or alternative workflows for Linux users.
Recommendations
- Explicitly state that Azure CLI commands work on both Windows and Linux, and provide example commands in both Bash (Linux/macOS) and PowerShell (Windows) where relevant.
- Include notes or sections on how to perform troubleshooting steps using Linux-native tools (e.g., kubectl, journalctl, systemctl) where applicable.
- Add screenshots or instructions for Linux desktop environments if UI steps are required.
- Mention any OS-specific prerequisites or differences (e.g., file paths, permissions, package installation) for Linux users.
- Ensure parity in troubleshooting guidance by referencing both Windows and Linux environments in all relevant sections.
IoT Operations
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-operations/connect-to-cloud/tutorial-mqtt-bridge.md
...ot-operations/connect-to-cloud/tutorial-mqtt-bridge.md
Medium 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 between Linux and Windows users. However, in every case, the PowerShell tab is presented immediately after Bash, and the examples are equally detailed. There is no evidence of exclusive use of Windows tools, nor are Windows-specific patterns or tools mentioned before their Linux equivalents. The only minor bias is the consistent inclusion of PowerShell examples, which may signal a slight Windows orientation, but Linux users are fully supported. There are no missing Linux examples, and all instructions (including Kubernetes and Bicep) are platform-neutral.
Recommendations
- Consider listing Bash examples before PowerShell in tab order, or randomize tab order to avoid perceived prioritization.
- Explicitly mention that all CLI commands work on Linux, macOS, and Windows to reinforce cross-platform support.
- Add a short note at the start clarifying that both Bash and PowerShell are supported and that users should choose the tab matching their environment.
- Ensure screenshots and references to Azure Portal features are equally accessible from all platforms.
IoT Operations
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-operations/deploy-iot-ops/howto-enable-secure-settings.md
...rations/deploy-iot-ops/howto-enable-secure-settings.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides both Bash and PowerShell examples for key commands, but PowerShell is given equal prominence, which may indicate a slight Windows bias. The use of PowerShell tabs and examples suggests an assumption that users may be on Windows. However, Linux-specific instructions (such as nano, systemctl, and k3s config) are present, and Azure CLI is used throughout, which is cross-platform. There is no evidence of exclusive use of Windows tools or missing Linux examples, but the inclusion of PowerShell examples and tabs may be unnecessary for a primarily Linux/Kubernetes audience.
Recommendations
- Consider making Bash the default or primary example, as most Kubernetes and edge deployments are Linux-based.
- Move PowerShell examples to a secondary position or into expandable sections, rather than giving them equal prominence.
- Clarify in the prerequisites that Azure CLI commands work on both Windows and Linux, and note any OS-specific differences if relevant.
- Review whether PowerShell examples are needed for this audience; if not, remove them to streamline documentation.
- Ensure all instructions (such as file editing and service restart) have clear Linux equivalents and note any Windows-specific alternatives only if necessary.
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 provides both Bash and PowerShell command examples for certificate management and secret handling, but consistently lists PowerShell examples immediately after Bash, and occasionally refers to Windows deployment options before Linux. There is a slight preference for Windows tools and patterns, such as explicit mention of Azure Kubernetes Service Edge Essentials for Windows and PowerShell scripting, while Linux equivalents (Ubuntu/K3s) are mentioned but not emphasized. All command-line examples are given for both platforms, but the ordering and explicit references suggest a mild Windows-first and PowerShell-heavy bias.
Recommendations
- Alternate the order of Bash and PowerShell examples so that Linux users see their commands first in some sections.
- Explicitly state Linux/Ubuntu/K3s options before or alongside Windows/AKS Edge Essentials in prerequisite and deployment sections.
- Where possible, provide additional Linux-specific tips or troubleshooting notes to match the level of detail given for Windows.
- Ensure parity in screenshots and UI instructions by referencing both Linux and Windows environments when applicable.
- Consider including a summary table of commands for both Bash and PowerShell at the end of each section for quick reference.
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
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation exclusively describes using the Azure portal (web UI) for RBAC role creation and assignment, without mentioning command-line alternatives such as Azure CLI or PowerShell. There are no examples or instructions for Linux users, nor any cross-platform command-line guidance. This may implicitly favor Windows users, as the Azure portal is often associated with Windows-centric workflows and omits Linux-friendly, scriptable approaches.
Recommendations
- Add instructions for creating and assigning custom RBAC roles using Azure CLI, which is cross-platform and widely used on Linux.
- Include PowerShell examples for completeness, but ensure Azure CLI examples are presented first or alongside them.
- Explicitly mention that all procedures can be performed from Linux, macOS, or Windows using Azure CLI.
- Provide links to Azure CLI documentation for RBAC role management.
- Clarify that the Azure portal is web-based and accessible from any OS, but highlight command-line alternatives for automation and Linux parity.
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, but the Windows/PowerShell example appears before the Linux example in the tab order. The Windows/PowerShell instructions are more verbose and detailed, potentially making them more prominent. There are no Linux-specific tools or patterns missing, and most troubleshooting tools (kubectl, k9s, mosquitto, mqttui, MQTT Explorer) are cross-platform. However, the PowerShell example is given special attention, and Windows terminology (PowerShell prompt) is used explicitly.
Recommendations
- Present Linux and Windows examples in parallel, with equal prominence, or default to Linux first since Kubernetes clusters are often deployed on Linux.
- Ensure that Linux (bash) instructions are as detailed as the PowerShell ones, including explanations for each step.
- Explicitly mention cross-platform compatibility for all tools, and provide guidance for macOS users where relevant.
- Avoid using Windows-specific terminology (e.g., 'PowerShell prompt') without also referencing Linux equivalents (e.g., 'bash shell' or 'terminal').
- Consider adding a summary table comparing steps for Linux, Windows, and macOS, to reinforce parity.
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 provides both Bash and PowerShell command examples for certificate management and deployment tasks, but PowerShell examples are given alongside Bash, and Windows deployment options are mentioned before Ubuntu/K3s equivalents. There is a slight preference for Windows in deployment instructions and command-line examples, which may be perceived as Windows bias.
Recommendations
- Ensure Linux (Bash) examples are presented first or equally alongside PowerShell, especially in command snippets.
- In deployment instructions, alternate the order of Windows and Linux/K3s options or present them in parallel to avoid implicit prioritization.
- Explicitly mention that all steps and tools (kubectl, wget, etc.) are cross-platform and provide troubleshooting notes for both Windows and Linux environments.
- Where PowerShell is used, clarify if Bash syntax is fully supported and provide links to platform-specific guidance if needed.
- Add more Linux-specific tips or notes, such as handling file permissions, editor choices, or environment setup for Ubuntu/K3s users.
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
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page exclusively describes using the Azure portal (web UI) for RBAC role creation and assignment, without mentioning or providing examples for command-line or automation approaches. There are no references to cross-platform tools such as Azure CLI, nor are there any PowerShell or Linux-specific instructions. However, the omission of Azure CLI (which is cross-platform and widely used on Linux) means the documentation implicitly favors Windows workflows, as the Azure portal is most commonly used in Windows environments and the lack of CLI examples can disadvantage Linux users.
Recommendations
- Add instructions and examples for creating and assigning custom roles using Azure CLI, which works on both Windows and Linux.
- Explicitly mention that the Azure portal is accessible from any OS, but provide parity by including automation/CLI steps.
- If PowerShell examples are added in future, ensure equivalent Azure CLI examples are provided.
- Reference documentation for both Azure CLI and PowerShell role management commands, and clarify their cross-platform compatibility.
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 instructions are presented immediately after the Linux section and use PowerShell-specific syntax. The AKS tab assumes a Windows environment by default, and the instructions for running commands on the cluster machine are PowerShell-centric, with no mention of Linux equivalents for AKS. Other tooling and examples (kubectl, k9s, MQTT tools) are cross-platform and use bash/console syntax, but the AKS section is notably Windows-biased.
Recommendations
- For AKS, provide equivalent Linux/bash instructions alongside PowerShell, or clarify that both Windows and Linux are supported for AKS cluster management.
- Explicitly state platform requirements or options for each example (e.g., 'On Windows, use PowerShell; on Linux, use bash').
- Ensure that Linux examples are given equal prominence and detail as Windows examples, especially in sections where Windows/PowerShell is currently assumed.
- Consider reordering or merging platform-specific instructions so that neither platform is presented as the default or primary option.
- Add notes about tool availability and usage on both Windows and Linux for all major steps.
IoT Operations
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-operations/deploy-iot-ops/howto-enable-secure-settings.md
...rations/deploy-iot-ops/howto-enable-secure-settings.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides both Bash and PowerShell examples for key commands, but PowerShell examples are given equal prominence and detail as Bash, which may indicate a bias towards Windows users. The use of PowerShell tabs and examples throughout the page, especially for Azure CLI commands, suggests a Windows-centric approach. However, Linux-specific instructions (such as editing k3s config files and restarting services) are present, showing some Linux consideration. There is no exclusive use of Windows tools, but the parity between Bash and PowerShell examples could be improved by clarifying platform applicability and prioritizing Bash (Linux) examples where appropriate.
Recommendations
- Clearly indicate which examples are intended for which platforms (e.g., Bash for Linux/macOS, PowerShell for Windows).
- Present Bash (Linux) examples before PowerShell (Windows) examples to emphasize cross-platform support.
- Add explicit notes about platform compatibility for each command block.
- Ensure that all Linux-specific steps (such as file editing and service management) are grouped and clearly marked for Linux users.
- Consider adding a summary table or section outlining differences in steps for Windows vs. Linux environments, if any exist.
- Review the use of PowerShell tabs and ensure they are only present where Windows-specific instructions are necessary.
IoT Operations
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-operations/connect-to-cloud/tutorial-mqtt-bridge.md
...ot-operations/connect-to-cloud/tutorial-mqtt-bridge.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Bash and PowerShell examples for all Azure CLI commands, but PowerShell is always presented immediately after Bash and with equal prominence. There are no Linux-specific tools or patterns mentioned outside Bash, but the presence of PowerShell examples throughout the page indicates a Windows bias, as Linux users are more likely to use Bash. There are no examples for other shells (e.g., zsh, fish) or for native Linux tools beyond Bash. The instructions for deploying MQTT clients and interacting with Kubernetes use Bash and kubectl, which are cross-platform but more common on Linux. No explicit Windows-only tools are used, but the consistent inclusion of PowerShell examples and lack of Linux-first language or examples (such as only Bash, or Bash before PowerShell) suggests a mild Windows bias.
Recommendations
- Present Bash examples before PowerShell, or make Bash the default tab to reflect the prevalence of Linux in cloud and IoT scenarios.
- Add a note clarifying that Bash examples work on Linux, macOS, and Windows (with WSL), while PowerShell is primarily for Windows users.
- Consider including zsh or fish shell examples if relevant for advanced Linux users.
- Explicitly mention that all Azure CLI commands work on Linux, macOS, and Windows, and provide guidance for installing Azure CLI on Linux.
- If PowerShell is included, clarify its use case (e.g., for Windows users) and avoid implying it is the primary or preferred method.
IoT Operations
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-operations/deploy-iot-ops/howto-enable-secure-settings.md
...rations/deploy-iot-ops/howto-enable-secure-settings.md
Medium Priority
View Details →
Detected Bias Types
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.
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
Medium Priority
View Details →
Detected Bias Types
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.
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
Medium Priority
View Details →
Detected Bias Types
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.
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 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.