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 1-25 of 55 flagged pages
IoT Central Device authentication in Azure IoT Central ...les/iot-central/core/concepts-device-authentication.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page demonstrates some Windows bias, particularly in the 'For testing purposes only' section, where PowerShell scripts are mentioned before Bash scripts for certificate generation. Windows-oriented tools (PowerShell) are referenced explicitly, and while Bash is also mentioned, the ordering and emphasis favor Windows. There are no explicit Linux-only examples, and the Azure CLI (cross-platform) is used elsewhere, but Windows patterns (PowerShell) are given prominence in key areas.
Recommendations
  • Ensure that Bash and Linux tools/scripts are mentioned and demonstrated with equal prominence and ordering as PowerShell equivalents.
  • Provide explicit Linux/macOS examples for certificate generation and device authentication, not just mention Bash scripts.
  • Where possible, use cross-platform tools (e.g., OpenSSL, Azure CLI) in examples and highlight their usage on both Windows and Linux.
  • Add a section or callouts for Linux/macOS users, clarifying any platform-specific steps or differences.
  • Review all sample code and utilities to ensure parity between Windows and Linux, and avoid defaulting to Windows-first patterns.
GitHub Create Pull Request
IoT Central Create an IoT Central application ...t-central/core/howto-create-iot-central-application.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation provides examples for creating IoT Central applications using the Azure portal (GUI), Azure CLI, and Azure PowerShell. The PowerShell section is given equal prominence as the CLI, and there is no mention of Linux-specific tools or shell environments (e.g., Bash). The CLI examples use Azure CLI, which is cross-platform, but there is no explicit guidance or examples for Linux users (such as shell-specific notes, package manager installation, or troubleshooting). The PowerShell examples and terminology are Windows-centric, and there is no mention of Linux alternatives or parity for PowerShell usage. The GUI screenshots and instructions are based on the Azure portal, which is platform-agnostic, but the command-line sections implicitly assume Windows environments.
Recommendations
  • Add explicit instructions for installing and using Azure CLI on Linux, including package manager commands (e.g., apt, yum).
  • Clarify that Azure CLI commands work on Linux, macOS, and Windows, and provide troubleshooting tips for Linux users.
  • If PowerShell is mentioned, note that PowerShell Core is available on Linux and macOS, and provide installation instructions for those platforms.
  • Consider adding Bash script examples or referencing shell environments commonly used on Linux.
  • Review screenshots and terminology to ensure they do not assume a Windows environment (e.g., avoid referencing Windows-specific paths or UI elements).
GitHub Create Pull Request
IoT Central Create a private endpoint for Azure IoT Central ...cles/iot-central/core/howto-create-private-endpoint.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation exhibits Windows bias in several ways: the only CLI example for querying private DNS zones uses Chocolatey (a Windows package manager) and ARMClient (with PowerShell commands), with no Linux or cross-platform alternatives. The troubleshooting section mentions 'Test-NetConnection', a Windows-only tool, before listing 'nslookup', which is cross-platform. There are no Linux-specific instructions or examples for tasks such as installing ARMClient, querying DNS, or troubleshooting connectivity, and Windows-centric tools and patterns are presented first or exclusively.
Recommendations
  • Provide equivalent Linux/macOS instructions for installing ARMClient (e.g., via npm or direct download) and running the same queries.
  • Include Azure CLI or REST API examples for querying private DNS zones, which work on all platforms.
  • Mention cross-platform tools (e.g., dig, curl) for DNS and connectivity troubleshooting alongside or before Windows-only tools like Test-NetConnection.
  • Avoid referencing Windows package managers (Chocolatey) exclusively; suggest alternatives for Linux (apt, yum, etc.) and macOS (brew).
  • Ensure all code samples and troubleshooting steps have both Windows and Linux/macOS variants, or use platform-agnostic tools where possible.
GitHub Create Pull Request
IoT Central Integrate Azure IoT Central with CI/CD ...ticles/iot-central/core/howto-integrate-with-devops.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation demonstrates a bias toward Windows and PowerShell by exclusively providing PowerShell script examples for key automation steps, such as generating configuration files and deploying changes. There are no equivalent examples using Bash, shell scripting, or Linux-native tools. The use of PowerShell is presented as the primary (and only) automation method, even though PowerShell 7 is cross-platform. Additionally, Windows-centric tools (Visual Studio Code, PowerShell) are mentioned before or instead of Linux alternatives. There is a lack of explicit guidance for Linux users, and no mention of adapting scripts for Bash or other shells.
Recommendations
  • Provide equivalent Bash/shell script examples for all PowerShell automation steps, especially for generating and applying configuration files.
  • Explicitly mention that PowerShell 7 is cross-platform, and clarify how Linux/macOS users can install and run the scripts.
  • Include instructions for using Linux-native editors (e.g., Vim, Nano) alongside Visual Studio Code.
  • Add troubleshooting notes or adaptations for common Linux environments (e.g., Ubuntu, CentOS) where file paths, permissions, or environment variables may differ.
  • Reference Linux package managers and installation commands for prerequisites (e.g., PowerShell, Azure CLI, Git).
  • Consider providing Docker-based or containerized examples to ensure parity across platforms.
GitHub Create Pull Request
IoT Central Azure IoT Central application administration guide ...rticles/iot-central/core/overview-iot-central-admin.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell is mentioned alongside Azure CLI as a primary tool for administration, and 'PowerShell' is listed before 'Azure CLI' in multiple places. There are no explicit Linux-specific examples, nor is there mention of Linux-native tools or shell environments. The documentation assumes familiarity with Windows-centric tools and patterns, such as PowerShell and the Azure portal, without providing parity for Linux users or referencing Bash or other Linux shells.
Recommendations
  • Provide explicit Linux/Bash examples alongside PowerShell, especially for command-line tasks.
  • List Azure CLI before PowerShell when both are supported, as Azure CLI is cross-platform.
  • Reference Linux-native environments and workflows (e.g., Bash, zsh, Linux terminal) in tool sections.
  • Clarify that all CLI examples work on Linux and macOS, not just Windows.
  • Include links or notes about installing and using Azure CLI and other tools on Linux.
  • Avoid assuming the Azure portal is the default interface; mention cross-platform alternatives where relevant.
GitHub Create Pull Request
IoT Central Manage and monitor IoT Central ...t-central/core/howto-manage-and-monitor-iot-central.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by providing extensive Azure PowerShell examples and cmdlets, which are primarily used on Windows. PowerShell is presented as a first-class option alongside Azure CLI and portal, but there is no mention of Linux-specific tools, shell environments, or guidance for Bash users. The examples and instructions assume familiarity with PowerShell, and there are no explicit Linux or cross-platform shell examples (e.g., Bash, zsh). The documentation does not clarify that Azure CLI is fully cross-platform or provide Linux-specific troubleshooting, installation, or usage notes.
Recommendations
  • Explicitly state that Azure CLI is cross-platform and provide installation instructions for Linux and macOS.
  • Add Bash/zsh examples for all CLI commands, including environment variable usage and command chaining.
  • Clarify that PowerShell examples are primarily for Windows users, and suggest alternatives for Linux/macOS users.
  • Include troubleshooting tips or links for common Linux issues (e.g., permissions, package managers).
  • Mention Linux-native tools or patterns where relevant, such as using curl for REST API calls.
  • Ensure parity in example depth and coverage between PowerShell and CLI/Bash examples.
  • Consider adding a section or tab for Linux/macOS users, highlighting any platform-specific considerations.
GitHub Create Pull Request
IoT Central Device authentication in Azure IoT Central ...les/iot-central/core/concepts-device-authentication.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page shows mild Windows bias, especially in the 'For testing purposes only' section, where PowerShell scripts are mentioned before Bash scripts for certificate generation. The referenced tooling for certificate management includes PowerShell scripts and Windows-centric instructions, and there is a tendency to mention Windows tools or patterns first. However, Linux alternatives (Bash scripts, OpenSSL) are present, and Azure CLI examples are cross-platform.
Recommendations
  • Present Bash and PowerShell scripts equally, or mention Bash first to balance the order.
  • Explicitly state cross-platform compatibility for all tools and scripts, and provide usage examples for both Windows and Linux.
  • Where PowerShell is referenced, include equivalent Bash/Unix shell commands side-by-side.
  • Ensure that links to tooling (e.g., certificate generation) highlight Linux and macOS support as clearly as Windows.
  • Add more Linux-specific examples, such as using OpenSSL for certificate management, and clarify when a tool is Windows-only.
GitHub Create Pull Request
IoT Central Create an IoT Central application ...t-central/core/howto-create-iot-central-application.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by providing PowerShell examples and instructions for creating IoT Central applications, with no equivalent Linux shell or cross-platform examples. Windows tools (PowerShell) are featured alongside Azure CLI, but there is no mention of Linux-specific tools or shell commands (e.g., Bash). The ordering of examples places PowerShell on equal footing with Azure CLI, but does not clarify cross-platform compatibility or provide Linux-centric guidance.
Recommendations
  • Add explicit Bash/Linux shell examples for all CLI commands, including resource group creation and app creation.
  • Clarify that Azure CLI commands work on Linux, macOS, and Windows, and provide installation instructions for Linux users.
  • If PowerShell is included, note its cross-platform availability, or provide alternative instructions for Linux users who may not use PowerShell.
  • Consider reordering examples to present Azure CLI (cross-platform) before PowerShell, and explicitly mention platform compatibility.
  • Include troubleshooting or notes for common Linux issues (e.g., permissions, package managers) when installing Azure CLI or extensions.
GitHub Create Pull Request
IoT Central Create a private endpoint for Azure IoT Central ...cles/iot-central/core/howto-create-private-endpoint.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation demonstrates a Windows bias in several areas. The only command-line example for interacting with ARMClient uses PowerShell and Chocolatey, both Windows-centric tools, with no Linux or cross-platform alternatives provided. The documentation assumes the use of Windows tools for custom DNS server configuration and omits Linux equivalents or instructions. Troubleshooting steps mention 'Test-NetConnection', a PowerShell cmdlet, before mentioning cross-platform tools like 'nslookup', and do not provide Linux-specific guidance. Overall, the documentation prioritizes Windows workflows and tools, leaving Linux users without clear instructions.
Recommendations
  • Provide Linux equivalents for all command-line instructions, such as using apt/yum for ARMClient installation and bash/curl examples.
  • Include cross-platform or Linux-specific tools and commands (e.g., curl, wget, dig) alongside PowerShell examples.
  • Explicitly mention that ARMClient can be used on Linux and provide installation steps for Linux distributions.
  • In troubleshooting, list Linux commands (e.g., dig, host) before or alongside Windows-specific ones.
  • Review all steps to ensure parity between Windows and Linux environments, and add notes or sections for Linux users where workflows differ.
GitHub Create Pull Request
IoT Central Integrate Azure IoT Central with CI/CD ...ticles/iot-central/core/howto-integrate-with-devops.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation relies heavily on PowerShell scripts for core automation tasks, with all scripting examples and pipeline steps using PowerShell. While PowerShell 7 is cross-platform, there are no equivalent Bash or Linux-native script examples provided. The tooling and workflow patterns (e.g., Visual Studio Code, PowerShell modules) are more familiar to Windows users, and Linux alternatives are not mentioned or demonstrated.
Recommendations
  • Provide equivalent Bash script examples for key automation steps, especially for generating and applying configuration files.
  • Include instructions and examples for using Linux-native tools (e.g., shell scripts, text editors like Vim or Nano) alongside Visual Studio Code.
  • Clarify cross-platform compatibility of all scripts and modules, and explicitly test/document usage on Linux and macOS.
  • Mention and demonstrate how to run the pipeline steps using Bash or other shells in Azure Pipelines, not just PowerShell.
  • Add troubleshooting notes for common Linux-specific issues (e.g., file paths, permissions, environment setup).
GitHub Create Pull Request
IoT Central Manage and monitor IoT Central ...t-central/core/howto-manage-and-monitor-iot-central.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by providing extensive Azure PowerShell examples and cmdlets, which are primarily used on Windows. PowerShell is presented alongside Azure CLI, but there are no explicit Linux shell (bash) examples, nor is there mention of Linux-specific tools or workflows. The documentation references Windows-centric tools and patterns (PowerShell, cmdlets) and does not clarify cross-platform compatibility or provide parity for Linux users. Additionally, the ordering of examples sometimes places PowerShell before CLI, and there is no mention of Linux installation or usage nuances.
Recommendations
  • Explicitly state that Azure CLI commands work on Linux, macOS, and Windows, and provide bash/zsh shell examples where appropriate.
  • Add notes or sections on installing and using Azure CLI and PowerShell on Linux, including any platform-specific caveats.
  • Include Linux-native command examples (e.g., bash scripts, use of environment variables, piping, etc.) for common workflows.
  • Clarify that PowerShell Core is cross-platform, but also provide bash alternatives for users who do not use PowerShell.
  • Ensure ordering of examples does not prioritize Windows tools (PowerShell) over cross-platform tools (CLI), or alternate the order.
  • Mention and link to Linux documentation or guides for managing IoT Central applications.
GitHub Create Pull Request
IoT Central Azure IoT Central application administration guide ...rticles/iot-central/core/overview-iot-central-admin.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by frequently mentioning PowerShell and Azure CLI together, listing PowerShell before CLI, and referencing the Azure portal (a GUI tool most commonly used on Windows). There are no explicit Linux-specific examples or mentions of Linux-native tools or workflows. The documentation does not provide parity in examples or instructions for Linux users, and Windows-centric tools and patterns are referenced first or exclusively.
Recommendations
  • Ensure that examples using Azure CLI are presented before or alongside PowerShell, as CLI is cross-platform and more commonly used on Linux.
  • Explicitly mention Linux compatibility and provide Linux-specific instructions or screenshots where relevant.
  • Include references to Linux-native tools and workflows, such as bash scripting, and clarify that all CLI commands work on Linux, macOS, and Windows.
  • Avoid listing PowerShell before CLI unless there is a specific reason; consider grouping CLI and PowerShell examples together with clear tabs for each platform.
  • Add a section or note highlighting cross-platform support and best practices for Linux administrators.
GitHub Create Pull Request
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 →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page demonstrates mild Windows bias. In the section on generating test CA certificates, PowerShell scripts are mentioned alongside Bash scripts, but PowerShell is listed first, and the link points to a repository where Windows/PowerShell tooling is prominent. The examples for certificate generation and device key computation do not provide explicit Linux shell equivalents (e.g., Bash commands for Azure CLI usage), and there is no mention of Linux-specific tools or workflows. The documentation references OpenSSL for key generation, which is cross-platform, but overall, Windows-centric tools and patterns are presented before or more prominently than Linux alternatives.
Recommendations
  • Provide explicit Bash/Linux shell examples alongside PowerShell commands for certificate and key generation.
  • Clarify that Azure CLI commands work on both Windows and Linux, and show example invocations in Bash.
  • Highlight Linux-native tools or workflows (e.g., OpenSSL, Bash scripts) equally with Windows/PowerShell options.
  • Ensure that links to tooling repositories clearly indicate support for both Windows and Linux environments.
  • Where scripts are referenced, specify which are for Windows (PowerShell) and which are for Linux (Bash), and provide usage instructions for both.
GitHub Create Pull Request
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 →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation provides step-by-step instructions for creating an IoT Central application using the Azure portal, Azure CLI, and Azure PowerShell. The PowerShell example is given equal prominence as the CLI example, but there is no mention of Linux-specific tooling or shell environments (e.g., Bash), nor are there examples tailored for Linux users. The CLI instructions are generic and could apply to Linux, but the explicit inclusion of PowerShell and lack of Linux/Bash examples or references creates a subtle Windows bias. Additionally, the documentation references the Azure portal and PowerShell, both of which are more commonly used in Windows environments.
Recommendations
  • Add explicit Bash shell examples for the Azure CLI commands, including notes about compatibility with Linux/macOS terminals.
  • Clarify that the Azure CLI commands work cross-platform (Windows, Linux, macOS) and provide any necessary instructions for installing the CLI on Linux.
  • Include references to Linux-native tools or environments where applicable (e.g., mention that PowerShell Core is available on Linux, or suggest using Bash for scripting).
  • Reorder or balance the presentation so that CLI and Linux-friendly methods are not implicitly secondary to Windows/PowerShell approaches.
  • Add troubleshooting notes or links for common Linux-specific issues (e.g., permissions, package installation).
GitHub Create Pull Request
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 →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation provides parallel examples for Azure portal, Azure CLI, and Azure PowerShell throughout, but PowerShell is featured as a first-class automation tool, which is primarily a Windows technology. References to PowerShell and its cmdlets are prominent, and there is no mention of Linux-specific shell environments (e.g., Bash) or cross-platform scripting patterns. The CLI examples are generic, but the absence of explicit Linux/Bash examples or notes about cross-platform usage creates a subtle Windows bias. Additionally, PowerShell is listed as a primary tab alongside CLI and portal, reinforcing its status as a preferred tool.
Recommendations
  • Add explicit Bash shell examples for Azure CLI commands, showing usage in Linux environments (e.g., variable assignment, piping, etc.).
  • Include notes or sections clarifying that Azure CLI is fully supported on Linux and macOS, and provide links to installation guides for those platforms.
  • Mention cross-platform alternatives to PowerShell, such as Bash or Zsh, especially for scripting and automation tasks.
  • Where PowerShell cmdlets are shown, consider also showing equivalent Bash/CLI scripts for Linux users.
  • Review tab ordering and ensure that CLI (which is cross-platform) is not visually subordinate to PowerShell.
  • Add troubleshooting or usage tips specific to Linux environments (e.g., file permissions, environment variables, shell differences) where relevant.
GitHub Create Pull Request
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 →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation demonstrates a Windows bias in several ways. The only CLI example for querying private DNS zones uses Chocolatey (a Windows package manager) and ARMClient (installed via PowerShell), with no Linux or cross-platform alternatives provided. The troubleshooting section mentions Windows-centric tools (Test-NetConnection) before more universal ones, and does not provide Linux equivalents or instructions. There are no bash or Azure CLI examples for Linux users, and the documentation assumes use of the Azure portal, which is platform-neutral but does not address CLI workflows that are common on Linux.
Recommendations
  • Provide equivalent instructions and examples for Linux, such as using Azure CLI (az) or bash scripts to query private DNS zones.
  • Replace or supplement Chocolatey/ARMClient instructions with cross-platform alternatives (e.g., Azure CLI, curl, or REST API calls).
  • In troubleshooting, include Linux-native tools (e.g., dig, host) alongside nslookup and Test-NetConnection, and show example outputs.
  • Where PowerShell commands are given, provide bash/Azure CLI equivalents.
  • Explicitly state that all steps can be performed on Linux and macOS, and link to relevant cross-platform tool documentation.
GitHub 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 →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation relies heavily on PowerShell scripts for all automation steps, with no alternative examples for Bash, shell scripting, or Linux-native tools. While PowerShell 7 is cross-platform, the exclusive use of PowerShell and references to Visual Studio Code (a Microsoft tool) and Windows-centric patterns may disadvantage users who prefer Linux-native workflows. There are no Linux shell script equivalents or explicit instructions for Linux environments beyond mentioning PowerShell 7 compatibility.
Recommendations
  • Provide equivalent Bash or shell script examples for key automation steps, especially for generating and applying configuration files.
  • Explicitly document how to run the scripts on Linux, including any required dependencies or environment setup.
  • Include instructions or sample pipelines using Linux agents in Azure Pipelines.
  • Mention and demonstrate the use of Linux-native editors (e.g., Vim, nano) alongside Visual Studio Code.
  • Clarify that PowerShell 7 is cross-platform and provide troubleshooting tips for Linux users.
  • Consider offering sample scripts in both PowerShell and Bash to improve accessibility for Linux-first teams.
GitHub Create Pull Request
IoT Central https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-central/core/overview-iot-central-admin.md ...rticles/iot-central/core/overview-iot-central-admin.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page demonstrates mild Windows bias by referencing PowerShell alongside Azure CLI as primary tools for administration and monitoring, and by listing PowerShell before Azure CLI in multiple places. There is no explicit mention of Linux-specific tools, nor are there examples or guidance tailored for Linux users. The documentation assumes familiarity with Windows-centric tools and patterns, potentially making it less accessible to Linux administrators.
Recommendations
  • Provide explicit Linux examples and instructions, especially for command-line tasks (e.g., using Azure CLI on Linux, bash scripting).
  • List Azure CLI before PowerShell when referencing cross-platform command-line tools, as Azure CLI is natively cross-platform.
  • Clarify that all CLI examples work on Linux, macOS, and Windows, and provide any necessary platform-specific notes.
  • Include references to Linux-native tools or workflows where appropriate, such as bash, cron for automation, or integration with Linux-based CI/CD systems.
  • Avoid assuming PowerShell is the default or primary shell for all users; offer parity in examples and tool recommendations.
GitHub Create Pull Request
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 →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell scripts are referenced for certificate generation, and Windows-centric tooling is mentioned before Linux equivalents. While Bash scripts and OpenSSL are referenced, Windows tools and patterns (such as PowerShell and GUI screenshots) are more prominent and often listed first, with less emphasis on Linux-native workflows.
Recommendations
  • Ensure that all tooling references (e.g., certificate generation) include both Windows (PowerShell) and Linux (Bash/OpenSSL) examples side-by-side.
  • When listing utilities, alternate the order or explicitly mention Linux and Windows support, rather than defaulting to Windows-first.
  • Provide explicit Bash command examples for certificate generation and SAS key handling, not just PowerShell.
  • Include screenshots or instructions for Linux environments where GUI steps are shown for Windows.
  • Clarify which tools/scripts are cross-platform and provide installation/use instructions for both Windows and Linux.
GitHub Create Pull Request
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 →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates Windows bias in several ways. The only command-line example for querying private DNS zones uses Chocolatey and ARMClient, both Windows-centric tools, with instructions and commands given in PowerShell syntax. There are no equivalent Linux or cross-platform instructions or examples. The troubleshooting section mentions 'Test-NetConnection', a Windows PowerShell cmdlet, before mentioning 'nslookup', which is cross-platform. There is no mention of Linux-native package managers or CLI tools, nor are Linux shell commands provided. This may hinder Linux users or those working in cross-platform environments.
Recommendations
  • Provide Linux and macOS equivalents for command-line instructions, such as using curl, wget, or Azure CLI instead of ARMClient and Chocolatey.
  • Include installation instructions for ARMClient or Azure CLI via Linux package managers (apt, yum, Homebrew).
  • Show both PowerShell and Bash examples for all command-line steps.
  • Mention cross-platform tools first (e.g., Azure CLI) before Windows-specific tools.
  • In troubleshooting, list cross-platform commands (e.g., nslookup, dig, curl) before Windows-only commands like Test-NetConnection.
  • Explicitly state which steps are platform-specific and provide alternatives for other platforms.
GitHub 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 →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation is heavily focused on PowerShell for scripting and automation, with all example scripts and pipeline steps using PowerShell. While PowerShell 7 is cross-platform, there are no equivalent examples or guidance for Linux-native tools or shell scripting (e.g., Bash). The documentation also references Visual Studio Code and Git, which are cross-platform, but does not provide Linux-specific instructions or alternatives. There is no mention of Linux-first patterns or examples, and the use of PowerShell may be unfamiliar or less preferred for many Linux users.
Recommendations
  • Provide equivalent Bash shell script examples for all PowerShell scripts, especially for steps like configuration file generation and pipeline tasks.
  • Include explicit instructions for running the scripts and pipeline steps on Linux, including any required dependencies or environment setup.
  • Mention Linux-native tools and patterns (e.g., Bash, curl, jq) as alternatives to PowerShell where appropriate.
  • Clarify cross-platform compatibility for all tools and scripts, and highlight any platform-specific caveats.
  • Consider offering a choice between PowerShell and Bash in the documentation, with clear sections for each.
GitHub Create Pull Request
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 →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by presenting PowerShell instructions and examples alongside Azure CLI, and by explicitly including a dedicated PowerShell tab. Windows tools and patterns (PowerShell, Azure portal screenshots) are featured prominently, with no mention of Linux-specific tools or shell environments. The ordering of examples (Azure portal, Azure CLI, then PowerShell) also reflects a Windows-centric approach, and there are no Linux-specific instructions, troubleshooting notes, or screenshots.
Recommendations
  • Add explicit Linux shell examples (e.g., bash, zsh) and clarify that Azure CLI commands work cross-platform.
  • Include notes or troubleshooting tips for Linux users, such as package manager installation commands for Azure CLI.
  • Provide screenshots or instructions for Linux desktop environments where relevant.
  • Clarify that PowerShell is available on Linux, or provide alternative bash scripts for common tasks.
  • Consider reordering or balancing the presentation of examples so that Windows and Linux approaches are equally represented.
GitHub Create Pull Request
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 →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by consistently providing Azure PowerShell examples alongside Azure CLI, referencing PowerShell-specific cmdlets, and mentioning Azure PowerShell as a primary management tool. There is no mention of Linux-specific tools or shell environments (e.g., Bash), and no explicit Linux-oriented examples or guidance. The structure and examples assume familiarity with Windows tooling and patterns, with PowerShell examples given equal prominence to CLI, despite CLI being more cross-platform.
Recommendations
  • Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and provide example shell environments (e.g., Bash, zsh) for Linux users.
  • Add Linux-specific notes or examples, such as using Bash variables and command syntax, especially in sections where PowerShell scripting is shown.
  • Clarify that PowerShell is available cross-platform, but highlight that CLI is the recommended tool for Linux environments.
  • Include troubleshooting or installation guidance for Azure CLI and PowerShell on Linux.
  • Consider reordering examples to present CLI (cross-platform) before PowerShell (Windows-centric), or provide a Linux-first example where appropriate.
  • Reference Linux tools or patterns (e.g., using curl for REST API calls, jq for JSON parsing) where relevant.
GitHub Create Pull Request
IoT Central https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-central/core/overview-iot-central-admin.md ...rticles/iot-central/core/overview-iot-central-admin.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits mild Windows bias. PowerShell is mentioned alongside Azure CLI as a primary tool for administration, and 'PowerShell' is listed before 'Azure CLI' in several places. There are no explicit Linux-specific examples, nor are Linux command-line patterns or tools (such as bash scripts) referenced. The documentation does not provide parity in examples or instructions for Linux users, and the ordering of tools and examples tends to favor Windows-first approaches.
Recommendations
  • Provide explicit Linux examples and instructions, such as bash command-line usage, where PowerShell is mentioned.
  • When listing tools, alternate or balance the order (e.g., 'Azure CLI or PowerShell') or clarify cross-platform availability.
  • Include notes or sections on using administrative tools from Linux and macOS environments.
  • Add links or references to Linux-specific documentation or troubleshooting guides.
  • Ensure that screenshots, walkthroughs, and tutorials are not exclusively Windows-centric.
GitHub 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 →
Scanned: 2025-08-17 00:01
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation is heavily focused on PowerShell scripts for automation, with all scripting examples 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-native tools or patterns. The documentation also references Visual Studio Code (a Microsoft tool) as the primary editor, and does not mention Linux-specific editors or alternatives. This creates a bias toward Windows and Microsoft-centric tooling, potentially making it less accessible for Linux-first users.
Recommendations
  • Provide equivalent Bash or shell script examples for key automation steps, especially for generating configuration files and interacting with Azure services.
  • Include instructions and examples for using Azure CLI directly in Bash, where possible, instead of only PowerShell.
  • Mention and provide examples for Linux-native editors (e.g., Vim, Nano) alongside Visual Studio Code.
  • Clarify that all steps can be performed on Linux and macOS, and highlight any platform-specific considerations.
  • Reference and link to documentation for using Azure Pipelines with non-Windows agents and runners.
  • Consider providing a Docker-based workflow example for cross-platform parity.
GitHub Create Pull Request
← Previous Page 1 of 3 Next →