IoT Central
88
Total Pages
77
Linux-Friendly Pages
11
Pages with Bias
12.5%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
55 issues found
Showing 26-50 of 55 flagged pages
IoT Central
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-central/core/howto-create-private-endpoint.md
...cles/iot-central/core/howto-create-private-endpoint.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation demonstrates a Windows bias, especially in the 'Use a custom DNS server' section, where only Windows-specific tools (Chocolatey, ARMClient via PowerShell) are mentioned for interacting with Azure APIs. There are no equivalent Linux/macOS instructions or examples. The troubleshooting section references tools like 'Test-NetConnection' (PowerShell), and while 'nslookup' is cross-platform, the context and order still favor Windows environments. No Linux-native package managers, CLI tools, or shell examples are provided.
Recommendations
- Provide equivalent instructions for Linux/macOS users, such as using curl or Azure CLI (az rest) to interact with Azure REST APIs instead of ARMClient.
- Include installation instructions for ARMClient (if cross-platform) or suggest alternatives for Linux (e.g., using curl with authentication).
- Mention Linux package managers (apt, yum, etc.) if third-party tools are required, or clarify that ARMClient is Windows-only.
- In troubleshooting, include Linux-native commands (e.g., dig, host) alongside nslookup, and avoid referencing PowerShell-only tools like Test-NetConnection without alternatives.
- Structure examples so that cross-platform or Linux instructions are given equal prominence, not just as an afterthought.
Create Pull Request
IoT Central
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-central/core/howto-integrate-with-devops.md
...ticles/iot-central/core/howto-integrate-with-devops.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a bias toward Windows and PowerShell-centric workflows. All scripting examples use PowerShell, and the main automation scripts are provided only as PowerShell (.ps1) files. There are no equivalent Bash, shell, or cross-platform scripting examples, nor is there guidance for users who prefer or require Linux-native tooling. The documentation assumes the use of PowerShell 7 on all platforms, but does not provide alternative approaches for users who may not wish to use PowerShell or are working in environments where PowerShell is not standard.
Recommendations
- Provide equivalent Bash/shell script examples for all PowerShell scripts, especially for key automation steps such as generating configuration files and applying configurations.
- Explicitly mention and demonstrate how to run the workflow on Linux/macOS environments, including any necessary prerequisites or differences.
- Offer guidance or references for users who prefer to use Azure CLI, Python, or other cross-platform scripting languages instead of PowerShell.
- If PowerShell is required, clarify why and provide troubleshooting or installation guidance for Linux/macOS users, including any known limitations.
- Consider providing Docker-based examples or containers to encapsulate the workflow in a platform-neutral way.
IoT Central
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-central/core/concepts-device-authentication.md
...les/iot-central/core/concepts-device-authentication.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation page demonstrates mild Windows bias, primarily in the 'For testing purposes only' section, where PowerShell scripts are mentioned alongside Bash, and in the linked tools for certificate generation, which often default to Windows-first approaches. While Azure CLI and Node.js tools are cross-platform, the explicit mention of PowerShell and the lack of explicit Linux command-line examples (e.g., OpenSSL for all certificate operations, Bash-only scripts) suggest a slight preference for Windows tooling and workflows.
Recommendations
- Ensure all script/tool references are clearly marked as cross-platform, or provide separate instructions for Windows (PowerShell) and Linux/macOS (Bash).
- When listing tools or scripts, alternate the order (e.g., mention Bash before PowerShell in some places) or group them as 'Bash/PowerShell' rather than listing PowerShell first.
- Expand examples using OpenSSL or other standard Linux tools for certificate/key generation, especially in sections where only PowerShell or Windows-centric tools are mentioned.
- Explicitly state the platform compatibility of each tool or script, and provide download/use instructions for both Windows and Linux users.
- Where screenshots or UI instructions are given, ensure they are not Windows-specific or provide Linux/macOS equivalents if applicable.
IoT Central
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-central/core/howto-manage-and-monitor-iot-central.md
...t-central/core/howto-manage-and-monitor-iot-central.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation provides examples for both Azure CLI and Azure PowerShell, but PowerShell examples are given equal prominence to CLI, and in some sections, PowerShell is mentioned before or alongside CLI. PowerShell is a Windows-centric tool, and its inclusion without explicit mention of Linux alternatives or parity may suggest a bias towards Windows users. There are no explicit Linux-specific instructions, nor are there examples using Bash or other common Linux shells. The documentation also references Azure portal (web-based) and REST API, which are cross-platform, but the command-line focus is split between CLI (cross-platform) and PowerShell (primarily Windows).
Recommendations
- Clearly indicate that Azure CLI commands work natively on Linux, macOS, and Windows, while PowerShell is primarily for Windows (though available on Linux).
- Add explicit Bash shell examples for Linux users where scripting is involved, especially for variable assignment and command chaining.
- In tabbed examples, list Azure CLI before PowerShell to reflect its cross-platform nature and reduce perceived Windows-first bias.
- Where PowerShell is referenced, note that PowerShell Core is available on Linux, and provide installation links or guidance.
- Consider including a section or note on using these tools in Linux environments, including any prerequisites or differences.
- If possible, provide sample scripts or automation guidance using Bash for Linux users, especially in sections involving role assignments or identity management.
IoT Central
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-central/core/howto-create-iot-central-application.md
...t-central/core/howto-create-iot-central-application.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation provides three main methods for creating an IoT Central application: Azure portal (GUI), Azure CLI, and Azure PowerShell. While the Azure CLI is cross-platform, the PowerShell section is Windows-centric and is given equal prominence to the CLI, despite PowerShell being less commonly used on Linux. There are no explicit Linux shell (bash) examples, and the documentation does not mention Linux-specific considerations or tools. The ordering of examples (portal, CLI, then PowerShell) is neutral, but the inclusion of PowerShell as a primary method and the lack of Linux shell examples indicate a Windows bias.
Recommendations
- Add explicit bash/shell examples for Linux users, especially for common tasks like creating a resource group and an IoT Central application.
- Clarify that Azure CLI commands work on Linux, macOS, and Windows, and provide any Linux-specific installation guidance if needed.
- Consider moving the PowerShell section after CLI, or labeling it as 'for Windows users' to clarify its intended audience.
- Include troubleshooting notes or links relevant to Linux environments (e.g., permissions, package dependencies).
- Where screenshots or UI references are given, note any differences for Linux users if applicable.
IoT Central
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-central/core/howto-create-private-endpoint.md
...cles/iot-central/core/howto-create-private-endpoint.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation demonstrates a Windows bias, particularly in the 'Use a custom DNS server' section, where only Windows-specific tools (Chocolatey, ARMClient, PowerShell commands) are provided for interacting with Azure resources. There are no equivalent instructions or examples for Linux or cross-platform environments. Additionally, the troubleshooting section mentions 'Test-NetConnection' (a PowerShell cmdlet) alongside 'nslookup', but does not provide Linux-native alternatives or examples, and Windows tools are mentioned first.
Recommendations
- Provide equivalent Linux and cross-platform instructions for installing and using ARMClient (e.g., via npm or .NET global tool), and show how to authenticate and run the same API calls from Linux/macOS.
- Include Linux-native commands (such as curl, wget, or Azure CLI) for querying Azure REST APIs instead of or in addition to PowerShell/ARMClient.
- In troubleshooting, add Linux equivalents for network testing, such as 'dig', 'host', or 'curl', and mention them alongside or before Windows-specific tools.
- Avoid referencing Windows package managers (like Chocolatey) as the only installation method; provide installation steps for Linux (apt, yum, snap, etc.) and macOS (brew) where applicable.
- When listing tools or commands, present cross-platform or Linux-native options first or at least equally, to ensure parity and inclusivity.
IoT Central
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-central/core/howto-integrate-with-devops.md
...ticles/iot-central/core/howto-integrate-with-devops.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a bias towards Windows environments by relying exclusively on PowerShell scripts for configuration and deployment tasks, and referencing Windows-centric tools like Visual Studio Code. While PowerShell 7 is cross-platform, there are no examples or guidance for using native Linux/Unix shell scripting or tools. The documentation does not provide equivalent bash or shell script examples, nor does it mention how to adapt the process for users who prefer or require non-PowerShell environments.
Recommendations
- Provide equivalent bash or shell script examples for all PowerShell scripts, especially for generating and applying configuration files.
- Explicitly mention and demonstrate how to run the process on Linux/macOS, including any required dependencies or environment setup.
- Reference cross-platform editors and tools more broadly (e.g., mention nano, vim, or other editors alongside Visual Studio Code).
- Clarify that while PowerShell 7 is cross-platform, users may use bash or other shells, and provide guidance or links for adapting the scripts.
- Where possible, offer Azure CLI or REST API alternatives for steps currently handled by PowerShell scripts.
IoT Central
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-central/core/how-to-connect-devices-x509.md
...ticles/iot-central/core/how-to-connect-devices-x509.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation exhibits a Windows bias, particularly in the C# sections, where instructions for importing certificates explicitly reference Windows Explorer and the Windows Certificate Import Wizard. The prerequisite section also assumes the use of the Windows command prompt for Node.js commands, even though Node.js is cross-platform. Environment variable setting examples use 'set', which is Windows-specific, and there is no mention of Linux or macOS equivalents. Linux-specific instructions are only present for IoT Edge scenarios, not for the main device connection workflows.
Recommendations
- Provide explicit instructions for Linux and macOS users alongside Windows instructions, especially for certificate import and environment variable setup.
- Use cross-platform command syntax (e.g., 'export' for Unix shells, 'set' for Windows) or provide both variants in code blocks.
- When referencing tools like the Windows Certificate Import Wizard, also mention and provide steps for Linux/macOS alternatives (e.g., using OpenSSL or keychain utilities).
- In prerequisite and code sample sections, avoid language that assumes Windows as the default (e.g., 'the instructions in this tutorial assume you're running the node command at the Windows command prompt'). Instead, clarify that the steps are cross-platform and specify differences where necessary.
- For C#/.NET, provide guidance for handling certificates on Linux (e.g., using PEM files directly or importing into the .NET Core certificate store).
IoT Central
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-central/core/concepts-device-authentication.md
...les/iot-central/core/concepts-device-authentication.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation page shows a moderate Windows bias. While it does mention Bash scripts and OpenSSL (cross-platform), it gives prominence to PowerShell scripts and Windows-centric tooling in several places. For example, the certificate generation tools reference PowerShell scripts before Bash, and the linked certificate management tools are primarily Windows/PowerShell focused. There is also a tendency to mention Windows tools or patterns before their Linux equivalents, and some examples (such as screenshots and tool references) are more familiar to Windows users.
Recommendations
- Ensure all tooling references (such as certificate generation) provide both Bash (Linux/macOS) and PowerShell (Windows) examples side by side, or clearly indicate cross-platform support.
- When referencing scripts or tools, explicitly mention their compatibility (e.g., 'PowerShell (Windows)' and 'Bash (Linux/macOS)').
- Add Linux/macOS-specific command-line examples where only Windows/PowerShell examples are currently given.
- Balance the order of tool mentions (e.g., 'Bash and PowerShell scripts') or group them together as cross-platform options.
- Where screenshots or UI references are shown, include notes or images for both Windows and Linux environments if the experience differs.
IoT Central
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-central/core/howto-create-private-endpoint.md
...cles/iot-central/core/howto-create-private-endpoint.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation demonstrates a Windows bias, particularly in the 'Use a custom DNS server' section, where only Windows-specific tools (Chocolatey, ARMClient via PowerShell) are provided for interacting with Azure resources. There are no equivalent instructions or examples for Linux or cross-platform environments. Additionally, the order and prominence of Windows tooling and patterns (e.g., Chocolatey installation, PowerShell commands) reinforce this bias, and there is an absence of Linux-native or cross-platform alternatives.
Recommendations
- Provide equivalent instructions for Linux environments, such as using native package managers (apt, yum) and cross-platform tools (e.g., Azure CLI, curl, jq) instead of Chocolatey and ARMClient.
- Include both Windows and Linux command examples side by side, or clearly indicate which instructions apply to which operating system.
- Mention cross-platform tools (such as Azure CLI or REST API via curl) before or alongside Windows-specific tools.
- Avoid assuming the use of Windows-specific package managers (like Chocolatey) or shells (PowerShell) as the default.
- Explicitly state OS requirements or alternatives where Windows-only tools are referenced.
IoT Central
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-central/core/howto-manage-and-monitor-iot-central.md
...t-central/core/howto-manage-and-monitor-iot-central.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation provides parallel examples for Azure CLI and Azure PowerShell throughout, but PowerShell is given equal prominence to the CLI, despite being primarily a Windows-centric tool. There are no explicit Linux shell (bash) or cross-platform scripting examples beyond the CLI, and PowerShell is referenced as a standard tool for automation and scripting. In some sections, PowerShell is mentioned before or alongside CLI, reinforcing its status as a primary automation tool, which may not reflect the experience of Linux users.
Recommendations
- Clarify that Azure CLI commands are fully supported on Linux, macOS, and Windows, and consider providing bash-specific examples or notes for Linux users.
- Where PowerShell is referenced, note that Azure PowerShell is available cross-platform, but that bash/shell scripting is often preferred on Linux.
- Consider including bash script equivalents for multi-step CLI examples, especially where variables or pipelines are used.
- Avoid implying that PowerShell is the default or only scripting environment for automation; present CLI/bash as the primary cross-platform option.
- Explicitly mention Linux support and provide links to Linux installation and usage guides for both Azure CLI and PowerShell.
IoT Central
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-central/core/howto-integrate-with-devops.md
...ticles/iot-central/core/howto-integrate-with-devops.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a bias toward Windows and PowerShell-centric workflows. All scripting examples use PowerShell, and the main automation scripts provided are PowerShell scripts (.ps1). While PowerShell 7 is cross-platform, there are no equivalent Bash or shell script examples, and no mention of how to adapt the process for users who prefer native Linux/Unix tools. The tooling and editor recommendations (Visual Studio Code, PowerShell, Az PowerShell module) further reinforce a Windows/PowerShell-first approach, with no mention of alternatives commonly used in Linux environments.
Recommendations
- Provide equivalent Bash or shell script examples for key automation steps, especially for generating and applying configuration files.
- Explicitly mention and demonstrate how to use the Azure CLI and REST API directly from Bash or other Unix shells, not just via PowerShell.
- Include Linux-native editor recommendations (e.g., Vim, Nano, Emacs) alongside Visual Studio Code.
- Clarify that PowerShell 7 is cross-platform, but also offer native Linux/Unix alternatives for users who do not wish to use PowerShell.
- Where possible, provide YAML or JSON-based automation steps that are platform-agnostic.
- Add a section or callout for Linux/macOS users, highlighting any differences or additional steps required.
IoT Central
Create a private endpoint for Azure IoT Central
...cles/iot-central/core/howto-create-private-endpoint.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page exhibits Windows bias in the 'Use a custom DNS server' section, where only Windows-specific tools (Chocolatey and ARMClient via PowerShell) are provided for querying private DNS zones. There are no equivalent Linux/macOS instructions or alternatives. Additionally, the order and examples for troubleshooting (e.g., mentioning Test-NetConnection before nslookup) subtly prioritize Windows tools, and the installation instructions for ARMClient assume a Windows environment.
Recommendations
- Provide Linux/macOS equivalents for ARMClient installation and usage, such as using dotnet CLI, direct downloads, or alternative REST tools (e.g., curl, az CLI).
- Include bash/curl or Azure CLI examples for querying private DNS zones on Linux/macOS.
- When listing troubleshooting tools, mention cross-platform options (e.g., nslookup, dig) before or alongside Windows-specific ones.
- Explicitly state that the instructions apply to both Windows and Linux/macOS, or provide separate sections for each OS where workflows differ.
IoT Central
Manage and monitor IoT Central
...t-central/core/howto-manage-and-monitor-iot-central.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation provides parallel examples for Azure portal, Azure CLI, and Azure PowerShell throughout, but PowerShell is featured as a primary automation tool, which is most commonly used on Windows. PowerShell examples are given equal prominence to Azure CLI, but there is no mention of Bash, shell scripting, or Linux/macOS-specific workflows. The use of PowerShell and references to cmdlets may create friction for Linux/macOS users, as PowerShell is less commonly installed or used on those platforms. Additionally, the documentation does not clarify that Azure CLI is cross-platform and may be preferred on Linux/macOS.
Recommendations
- Explicitly state that Azure CLI is cross-platform and works natively on Linux/macOS.
- Add Bash or shell scripting examples where appropriate, especially for automation tasks.
- Clarify that PowerShell is available on Linux/macOS, but Azure CLI may be more familiar to non-Windows users.
- Consider listing Azure CLI examples before PowerShell to reflect its broader cross-platform usage.
- Include notes or links for installing PowerShell on Linux/macOS if PowerShell examples are retained.
IoT Central
Integrate Azure IoT Central with CI/CD
...ticles/iot-central/core/howto-integrate-with-devops.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows First
Summary
The documentation relies heavily on PowerShell scripts for critical automation steps, with no equivalent Bash, shell, or cross-platform scripting examples provided. Although PowerShell 7 is cross-platform, the instructions and scripts are PowerShell-centric, and there is no mention of Linux/macOS-specific alternatives or patterns. Windows tools and workflows are implicitly prioritized, and Linux users may encounter friction if they prefer native shell scripting or lack PowerShell experience.
Recommendations
- Provide equivalent Bash or shell script examples for key automation steps, especially for generating configuration files and applying configurations.
- Explicitly document how to run the PowerShell scripts on Linux/macOS, including prerequisites and troubleshooting tips.
- Offer guidance or templates for using other CI/CD tools (e.g., Jenkins, GitLab CI, GitHub Actions) with non-PowerShell runners.
- Ensure that instructions for installing and using PowerShell are clear for Linux/macOS users, including package manager commands.
- Consider restructuring examples so that cross-platform approaches (e.g., Azure CLI, REST API calls) are shown before or alongside PowerShell.
IoT Central
Device authentication in Azure IoT Central
...les/iot-central/core/concepts-device-authentication.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation references PowerShell scripts for certificate management and lists Windows tooling (PowerShell) before Bash alternatives. While some Linux-compatible tools (Node.js, Bash) are mentioned, Windows-centric examples and tools are given prominence, and PowerShell is referenced explicitly for key certificate tasks. This may create friction for Linux/macOS users, especially in testing scenarios.
Recommendations
- Ensure Bash and Linux/macOS equivalents are always listed alongside PowerShell scripts, and give them equal prominence.
- Add explicit instructions and examples for Linux/macOS users wherever Windows tools or PowerShell are mentioned.
- Where possible, use cross-platform tools (e.g., OpenSSL, Node.js) as the primary example, with OS-specific alternatives as secondary options.
- Review referenced GitHub tools/scripts to ensure Linux/macOS compatibility is clear and documented.
- Avoid listing Windows/PowerShell tools first unless they are the only option.
IoT Central
Create a private endpoint for Azure IoT Central
...cles/iot-central/core/howto-create-private-endpoint.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page demonstrates a notable Windows bias, especially in the 'Use a custom DNS server' section, where only Windows-specific tools (Chocolatey, ARMClient via PowerShell) are mentioned and example commands are provided exclusively for Windows. There are no Linux/macOS equivalents or alternative instructions. Additionally, Windows tools and patterns are presented first and exclusively, with no parity for other platforms.
Recommendations
- Provide Linux/macOS alternatives for ARMClient installation (e.g., via npm or direct download) and usage.
- Include bash/curl examples for querying Azure REST APIs, as ARMClient is cross-platform but not installed via Chocolatey on Linux/macOS.
- Mention package managers and installation steps for Linux (apt, yum, Homebrew) and macOS.
- Add troubleshooting and verification steps using Linux-native tools (e.g., dig, curl) alongside nslookup.
- Clearly indicate cross-platform options wherever possible, and avoid assuming Windows as the default environment.
IoT Central
Integrate Azure IoT Central with CI/CD
...ticles/iot-central/core/howto-integrate-with-devops.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation relies heavily on PowerShell scripts for core automation tasks, with all example scripts and pipeline steps using PowerShell. While PowerShell 7 is cross-platform, there are no equivalent bash or shell script examples, nor is there guidance for Linux/macOS users who may prefer native tools. The documentation mentions PowerShell and Windows tools first in prerequisites and throughout, creating friction for Linux/macOS users who may not use PowerShell as their primary scripting environment.
Recommendations
- Provide equivalent bash/shell script examples for key automation steps, especially for generating configuration files and applying them.
- Explicitly mention that PowerShell 7 is required and cross-platform, but offer installation and usage guidance for Linux/macOS users.
- Include notes or alternative instructions for users who prefer bash or other scripting languages.
- Consider providing sample YAML pipeline steps using bash tasks or Azure CLI directly, not just PowerShell.
- List Linux/macOS tools and patterns alongside Windows tools in prerequisites and examples.
IoT Central
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-central/core/howto-configure-rules-advanced.md
...les/iot-central/core/howto-configure-rules-advanced.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation exclusively references Microsoft-centric workflow tools (Power Automate and Azure Logic Apps) for integrating Azure IoT Central, with no mention of Linux-native or cross-platform alternatives, nor any command-line or scripting examples that would be relevant to Linux users. All examples and instructions are tailored to the Microsoft ecosystem, which is most commonly associated with Windows environments.
Recommendations
- Include examples or references for integrating with Azure IoT Central using cross-platform tools such as Azure CLI, REST API calls (with curl or similar), or open-source workflow engines (e.g., Apache Airflow, Node-RED) that can run on Linux.
- Provide sample scripts or automation flows using bash, Python, or other languages commonly used on Linux.
- Explicitly mention that Power Automate and Logic Apps are web-based and can be used from any OS, but also offer guidance for users who prefer or require Linux-native solutions.
- Add a section comparing Microsoft workflow tools with open-source or third-party alternatives, and provide links or references for further reading.
IoT Central
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-central/core/howto-configure-rules-advanced.md
...les/iot-central/core/howto-configure-rules-advanced.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation exclusively references Microsoft-centric workflow tools (Power Automate and Azure Logic Apps) and provides step-by-step instructions only for these platforms. There are no examples or mentions of Linux-native automation tools, CLI-based alternatives, or cross-platform scripting approaches. The documentation assumes use of graphical interfaces typical of Windows environments and does not address Linux users or their preferred tools.
Recommendations
- Include examples or references for integrating with Azure IoT Central using cross-platform tools such as Azure CLI, REST API (with curl or httpie), or open-source workflow engines (e.g., Apache Airflow, Node-RED).
- Provide sample automation scripts or workflows that can be executed from Linux environments, such as Bash scripts or Python code using the Azure SDK.
- Mention that Power Automate and Logic Apps are web-based and accessible from any OS, but clarify any OS-specific limitations or requirements.
- Add a section or links for Linux users who may want to automate IoT Central integration without relying on Microsoft-specific workflow tools.
IoT Central
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-central/core/howto-migrate-to-iot-hub.md
.../articles/iot-central/core/howto-migrate-to-iot-hub.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation provides command-line instructions and setup steps that are platform-neutral in syntax (e.g., 'git clone', 'npm install', 'npm start'), but it does not specify or show any Linux/macOS-specific instructions, nor does it mention potential differences or prerequisites for Linux users. The use of 'cmd/sh' in code blocks is ambiguous and could confuse users about which shell to use. There are no explicit Windows-only tools or PowerShell commands, but the lack of Linux-specific guidance or troubleshooting constitutes a subtle 'windows_first' and 'missing_linux_example' bias.
Recommendations
- Explicitly state that the migrator tool and all commands work on Windows, Linux, and macOS, and mention any platform-specific prerequisites (e.g., how to install Node.js on Linux).
- Use separate code blocks for Windows (cmd/PowerShell) and Linux/macOS (bash/sh) where commands or environment setup differ, or clarify that the commands are cross-platform.
- Add troubleshooting notes for common Linux/macOS issues (e.g., permissions, environment variable syntax, npm/node installation).
- Clarify in the 'cmd/sh' code blocks which shell is expected, or provide both Windows and Linux/macOS variants if needed.
IoT Central
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-central/core/howto-configure-rules-advanced.md
...les/iot-central/core/howto-configure-rules-advanced.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation exclusively references Microsoft-centric workflow tools (Power Automate and Azure Logic Apps), which are primarily used in Windows and Microsoft cloud environments. There are no examples or mentions of Linux-native automation tools, CLI, or cross-platform alternatives. All step-by-step instructions and screenshots are focused on these Microsoft tools, with no parity for Linux users or open-source workflow solutions.
Recommendations
- Include examples or references for integrating with IoT Central using cross-platform tools such as Azure CLI, REST API via curl, or open-source workflow engines (e.g., Apache Airflow, Node-RED) that can run on Linux.
- Provide REST API request/response examples using curl or HTTPie to demonstrate how Linux users can automate similar workflows.
- Mention that Power Automate and Logic Apps are cloud-based and accessible from any OS, but clarify any OS-specific requirements or limitations.
- Add a section or links to documentation for Linux users or those preferring non-Microsoft automation platforms.
- Ensure parity in examples by showing both GUI-based (Power Automate/Logic Apps) and command-line/script-based (bash, Python, etc.) approaches.
IoT Central
Device authentication in Azure IoT Central
...les/iot-central/core/concepts-device-authentication.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation page shows mild Windows bias, primarily in the section on test certificate generation, where PowerShell scripts are mentioned before Bash scripts and Windows tooling is referenced. There is also a tendency to mention Windows-centric tools (PowerShell) and patterns before their Linux equivalents, though Linux options are present. The rest of the documentation uses cross-platform tools (Azure CLI, Node.js, OpenSSL) and does not exclude Linux/macOS users.
Recommendations
- Present Bash and PowerShell scripts side-by-side or mention Bash first to avoid Windows-first perception.
- Explicitly state cross-platform compatibility for all tools/scripts, especially in the certificate generation/testing sections.
- Add explicit Linux/macOS instructions or examples where only Windows/PowerShell are referenced.
- Where screenshots or UI instructions are given, clarify any OS-specific differences.
IoT Central
Create an IoT Central application
...t-central/core/howto-create-iot-central-application.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides examples for creating IoT Central applications using the Azure portal, Azure CLI, and Azure PowerShell. While Azure CLI is cross-platform, the PowerShell section is included as a primary tab, and there are no Linux/macOS-specific instructions or examples. The ordering of tabs places Azure portal (GUI), Azure CLI, and then PowerShell, which is Windows-centric. There is no mention of Linux-specific tools, nor are there any explicit Linux/macOS examples or troubleshooting notes.
Recommendations
- Explicitly mention that Azure CLI works on Linux/macOS and provide example commands for those platforms (e.g., bash syntax, installation instructions for CLI on Linux/macOS).
- Add troubleshooting notes or links for common Linux/macOS issues (e.g., authentication, environment setup).
- Consider including a note that PowerShell Core is available on Linux/macOS, or clarify that the PowerShell examples are not Windows-only.
- If possible, add a Linux/macOS-specific tab or section to highlight cross-platform usage.
IoT Central
Azure IoT Central application administration guide
...rticles/iot-central/core/overview-iot-central-admin.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation mentions PowerShell and Azure CLI together in multiple places, and lists PowerShell before Azure CLI. It also references the Azure portal, which is a cross-platform web tool but is often associated with Windows workflows. There are no explicit Linux/macOS examples, nor are Linux-specific tools or shell commands mentioned. The ordering and tool selection suggest a mild Windows bias, but Linux users can still complete all tasks using Azure CLI or the portal.
Recommendations
- Explicitly provide Linux/macOS shell examples alongside PowerShell, especially when referencing command-line tools.
- List Azure CLI before PowerShell, or clarify that both are fully supported on Linux/macOS.
- Add notes or links to platform-specific guidance for Linux/macOS users.
- Ensure that any referenced scripts or commands are shown in both PowerShell and Bash syntax where relevant.