IoT Central

176
Total Pages
168
Linux-Friendly Pages
8
Pages with Bias
4.5%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

16 issues found
Showing 1-16 of 16 flagged pages
IoT Central Create a private endpoint for Azure IoT Central ...cles/iot-central/core/howto-create-private-endpoint.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation exhibits Windows bias in the 'Use a custom DNS server' section, where only Windows-specific tooling (Chocolatey and ARMClient via PowerShell) is provided for querying private DNS zones. There are no Linux/macOS equivalents or alternative instructions, and the Windows-centric example is presented as the sole method. Elsewhere, troubleshooting and verification steps use cross-platform tools (nslookup), but the critical DNS query workflow is Windows-only.
Recommendations
  • Provide Linux/macOS alternatives for installing and using ARMClient (e.g., direct .NET install, or use Azure CLI/REST API with curl).
  • Include example commands for querying private DNS zones using Azure CLI or REST API, which work on all platforms.
  • Explicitly mention cross-platform options and avoid assuming Chocolatey/PowerShell are available.
  • Reorder examples or add notes to clarify platform compatibility.
GitHub Create Pull Request
IoT Central Integrate Azure IoT Central with CI/CD ...ticles/iot-central/core/howto-integrate-with-devops.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation relies heavily on PowerShell scripts for core automation tasks, with all scripting examples and pipeline integration steps using PowerShell. While PowerShell 7 is cross-platform, there are no Bash, Python, or Linux-native alternatives provided, and all example commands and scripts are PowerShell-centric. This creates friction for Linux/macOS users who may prefer or require Bash or other scripting environments. The documentation also presents PowerShell as the default tool for configuration generation and deployment, with no mention of Linux-first tools or patterns.
Recommendations
  • Provide equivalent Bash or Python scripts for key automation steps, especially for configuration generation and deployment.
  • Include Linux/macOS-specific instructions and examples alongside PowerShell, or at least clarify PowerShell 7 usage on non-Windows platforms.
  • Highlight cross-platform compatibility of PowerShell 7, and link to installation guides for Linux/macOS.
  • Offer guidance on adapting the pipeline to use Azure CLI or REST API calls directly, which are more native to Linux environments.
  • Present examples in both PowerShell and Bash, or alternate which is shown first.
GitHub Create Pull Request
IoT Central Manage and monitor IoT Central ...t-central/core/howto-manage-and-monitor-iot-central.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
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 given equal prominence to CLI, and several sections (such as role assignment and managed identity configuration) provide detailed PowerShell scripts. PowerShell is a Windows-centric tool, and its inclusion as a primary method may signal Windows bias. Additionally, the use of PowerShell is mentioned before Linux-native alternatives (such as Bash scripting), and no explicit Linux/macOS shell examples are provided. There are no examples using Bash, zsh, or other Unix shells, nor is there mention of Linux-specific tooling or considerations.
Recommendations
  • Add explicit Bash/zsh/Linux shell examples alongside PowerShell, especially for scripting tasks such as role assignment and managed identity configuration.
  • Clarify that Azure CLI is cross-platform and provide examples showing usage in Linux/macOS environments (e.g., using Bash variables and syntax).
  • Reorder sections so that cross-platform tools (Azure CLI) are presented before Windows-centric tools (PowerShell), or clarify parity.
  • Mention any platform-specific considerations for Linux/macOS users, such as installation steps or environment setup.
  • Consider including a table or note summarizing tool availability and platform compatibility.
GitHub Create Pull Request
IoT Central Azure IoT Central application administration guide ...rticles/iot-central/core/overview-iot-central-admin.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation references PowerShell and Azure CLI together, but PowerShell is mentioned first and repeatedly as a primary tool for administration and monitoring. There are no explicit Linux/macOS examples or mentions of Bash, and Windows-centric tools (PowerShell) are emphasized over cross-platform or Linux-native alternatives. The ordering and phrasing suggest a Windows-first approach, potentially creating friction for Linux/macOS users.
Recommendations
  • Provide explicit Linux/macOS examples, such as Bash commands, alongside PowerShell examples.
  • Clarify that Azure CLI is fully cross-platform and show usage in Bash or zsh shells.
  • Avoid listing PowerShell before Azure CLI unless there is a technical reason; alternate the order or group them as cross-platform tools.
  • Mention that all administrative tasks can be performed from Linux/macOS environments, and link to relevant platform-specific guides if available.
  • Add screenshots or walkthroughs from Linux/macOS environments where applicable.
GitHub Create Pull Request
IoT Central Create a private endpoint for Azure IoT Central ...cles/iot-central/core/howto-create-private-endpoint.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
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 a notable Windows bias, especially in the 'Use a custom DNS server' section, where only Windows-specific tools (Chocolatey and ARMClient via PowerShell) are provided for querying DNS zones. There are no equivalent Linux/macOS instructions or alternatives. Additionally, the troubleshooting section lists Windows-centric tools (Test-NetConnection) before mentioning cross-platform options, and the order of examples and instructions generally favors Windows environments.
Recommendations
  • Provide Linux/macOS equivalents for installing ARMClient (e.g., via npm or direct download) and show usage with bash/zsh.
  • Include instructions for querying Azure resources using Azure CLI or REST API with curl, which are cross-platform.
  • List cross-platform tools (e.g., nslookup, dig) before Windows-only tools in troubleshooting steps.
  • Explicitly mention that ARMClient and Chocolatey are Windows-specific, and offer alternatives for other platforms.
  • Add bash/zsh command examples alongside PowerShell examples wherever possible.
GitHub Create Pull Request
IoT Central Integrate Azure IoT Central with CI/CD ...ticles/iot-central/core/howto-integrate-with-devops.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation relies heavily on PowerShell scripts (.ps1) for core automation steps, with no equivalent Bash or shell script examples provided. While PowerShell 7 is cross-platform, the instructions and code samples assume familiarity with PowerShell, which is more common among Windows users. There is no mention of Linux/macOS-specific tooling or alternative approaches, and PowerShell is listed before other options in prerequisites, reinforcing a Windows-first perspective.
Recommendations
  • Provide equivalent Bash/shell script examples for key automation steps, especially for generating and applying configuration files.
  • Explicitly mention and demonstrate how Linux/macOS users can run the PowerShell scripts (e.g., using pwsh), including installation and troubleshooting tips.
  • Offer alternative approaches using Azure CLI or REST API calls for users who prefer not to use PowerShell.
  • Reorder prerequisites to avoid listing Windows-centric tools first, and clarify cross-platform compatibility.
  • Add notes or sections highlighting any platform-specific caveats or optimizations for Linux/macOS users.
GitHub Create Pull Request
IoT Central Manage and monitor IoT Central ...t-central/core/howto-manage-and-monitor-iot-central.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation provides parallel instructions for Azure portal, Azure CLI, and Azure PowerShell throughout, but PowerShell examples and references are prominent, including detailed scripts and cmdlets. The presence of 'devx-track-azurepowershell' metadata and frequent PowerShell usage signals a Windows-centric approach. While Azure CLI is cross-platform and examples are present, PowerShell is a Windows-first tool, and its inclusion may imply preference for Windows environments. There are no explicit Linux/macOS-specific instructions or troubleshooting notes, and examples are not always shown in a Linux-first order.
Recommendations
  • Clarify that Azure CLI is fully cross-platform and recommend it for Linux/macOS users.
  • Add explicit notes or sections for Linux/macOS users, including any environment setup or troubleshooting tips.
  • Ensure that CLI examples are shown before PowerShell examples, or provide a Linux/macOS tab if platform-specific steps exist.
  • Remove or balance metadata/tags that suggest PowerShell is the primary or preferred method.
  • Where PowerShell is mentioned, note that it is available on Linux/macOS via PowerShell Core, or provide Bash alternatives if relevant.
GitHub Create Pull Request
IoT Central Upload files from devices to Azure storage ...icles/iot-central/core/howto-configure-file-uploads.md
Low Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation page exhibits minor Windows bias, primarily in the sample output and tooling references. The sample code's terminal output explicitly shows 'Machine: Windows_NT', and instructions reference using VS Code and <kbd>F5</kbd> for debugging, which is most common on Windows. However, the code snippets and commands (git, npm) are cross-platform, and there are no PowerShell-specific examples or Windows-only tools. Linux/macOS users can follow the instructions, but may encounter minor friction due to Windows-centric references.
Recommendations
  • Show sample output for Linux/macOS (e.g., 'Machine: Linux', 'Machine: Darwin') alongside Windows output.
  • Clarify that VS Code and <kbd>F5</kbd> debugging works on Linux/macOS as well.
  • Avoid referencing OS-specific details in sample outputs unless necessary, or provide equivalent examples for other platforms.
  • Explicitly state that the sample code and commands work on Linux/macOS, and mention any prerequisites for those platforms if needed.
GitHub Create Pull Request
IoT Central Device authentication in Azure IoT Central ...les/iot-central/core/concepts-device-authentication.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation references PowerShell scripts and Windows-centric tooling for certificate generation, and mentions Windows tools before Linux equivalents. While Bash scripts are referenced for certificate management, the documentation tends to highlight Windows/PowerShell options first and does not provide explicit Linux/macOS command-line examples for key tasks such as SAS token generation or certificate creation. This creates mild friction for Linux/macOS users, though workarounds and cross-platform tools are available.
Recommendations
  • Explicitly provide Linux/macOS command-line examples alongside Windows/PowerShell commands for certificate and key generation.
  • When referencing tooling, list cross-platform or Linux-native tools (e.g., OpenSSL, Bash scripts) before or alongside Windows/PowerShell options.
  • Clarify which tools/scripts are cross-platform and provide usage instructions for both Windows and Linux/macOS environments.
  • Add sample commands for certificate/key generation using Bash and OpenSSL where only PowerShell is currently mentioned.
GitHub Create Pull Request
IoT Central Upload files from devices to Azure storage ...icles/iot-central/core/howto-configure-file-uploads.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation page generally avoids platform-specific instructions, but there is a subtle Windows bias: the sample output from running the device code shows 'Machine: Windows_NT' and memory stats, implicitly suggesting a Windows environment. However, all command-line instructions use cross-platform syntax (git, npm), and there are no PowerShell or Windows-only tool references. No Linux/macOS examples are missing, but Windows is shown first in the output.
Recommendations
  • Clarify that the sample code and instructions work on Linux/macOS as well as Windows.
  • Provide sample output from a Linux/macOS environment alongside the Windows output, or use generic output.
  • Explicitly mention cross-platform compatibility in the prerequisites or setup steps.
  • Avoid showing OS-specific output unless necessary, or rotate examples between platforms.
GitHub Create Pull Request
IoT Central Create an IoT Central application ...t-central/core/howto-create-iot-central-application.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
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 the Azure CLI is cross-platform and suitable for Linux/macOS, the PowerShell section is Windows-centric and is presented as a primary tab alongside CLI and portal. The ordering of examples (portal, CLI, then PowerShell) is reasonable, but the inclusion of PowerShell as a main method may suggest a slight Windows bias. No Linux-specific tools or shell examples (e.g., bash scripts) are provided, but the CLI instructions are sufficient for Linux users. There are no critical omissions preventing Linux/macOS users from completing the task.
Recommendations
  • Explicitly mention that Azure CLI works on Linux/macOS and provide a brief note or link to installation instructions for those platforms.
  • Consider adding a bash shell script example for Linux users, especially for automation scenarios.
  • Clarify that PowerShell Core is available on Linux/macOS, or note that the PowerShell example is primarily for Windows users.
  • Ensure parity in troubleshooting or environment setup notes for Linux/macOS users.
GitHub Create Pull Request
IoT Central Tutorial - Use the REST API to manage an application ...ain/articles/iot-central/core/tutorial-use-rest-api.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The tutorial exclusively uses Azure CLI commands and shell scripting patterns that are compatible with Bash (Linux/macOS) and PowerShell (Windows), but all variable assignment and command examples use Bash syntax. There is no explicit Windows bias in terms of PowerShell or Windows-only tools, nor are Windows tools mentioned before Linux equivalents. However, the documentation does not provide any PowerShell examples or mention how to adapt the commands for Windows users, which could create friction for those using Windows and PowerShell. Conversely, Linux/macOS users are well supported by the Bash syntax shown.
Recommendations
  • Add PowerShell equivalents for all Azure CLI commands and variable assignments, or provide a note explaining how to adapt Bash syntax for PowerShell.
  • Explicitly state that the examples use Bash syntax and provide guidance for Windows users who may be using PowerShell.
  • Consider adding a section or callout for cross-platform command adaptation, ensuring both Linux/macOS and Windows users can follow the tutorial seamlessly.
GitHub Create Pull Request
IoT Central Device authentication in Azure IoT Central ...les/iot-central/core/concepts-device-authentication.md
Low Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation provides both PowerShell and Bash scripts for certificate generation, but PowerShell is mentioned first and more prominently. The certificate management tools referenced are Windows-centric, and there is a slight tendency to mention Windows tools and patterns before Linux equivalents. However, Linux/macOS users are not blocked from completing the tasks, as Bash scripts and cross-platform Node.js tools are also referenced.
Recommendations
  • Ensure Bash and Linux/macOS instructions/examples are given equal prominence and order to PowerShell/Windows ones.
  • Explicitly state cross-platform compatibility for all tools and scripts.
  • Add more Linux/macOS-specific examples, especially for certificate generation and device provisioning.
  • Where screenshots or UI references are given, clarify any OS-specific differences.
  • Consider providing OpenSSL-based certificate generation walkthroughs for Linux/macOS users.
GitHub Create Pull Request
IoT Central Create an IoT Central application ...t-central/core/howto-create-iot-central-application.md
Low Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
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. The PowerShell section is given equal prominence to the Azure CLI, and there is no mention of Linux/macOS-specific tools or shell environments. The CLI examples use az, which is cross-platform, but PowerShell is a Windows-centric tool and is presented as a primary method. No Linux/macOS shell examples (e.g., bash, zsh) are provided, and there is no explicit guidance for Linux users.
Recommendations
  • Clarify that Azure CLI commands work on Linux/macOS as well as Windows.
  • Add explicit bash/zsh shell examples for Linux/macOS users, especially for resource group creation and az commands.
  • Note that PowerShell is available cross-platform, but most Linux users will use bash/zsh.
  • Consider reordering examples so that cross-platform CLI comes before PowerShell, or add a Linux/macOS tab.
  • Mention prerequisites for Linux/macOS users (e.g., installing az CLI on Ubuntu/macOS).
GitHub Create Pull Request
IoT Central Azure IoT Central application administration guide ...rticles/iot-central/core/overview-iot-central-admin.md
Low Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation page references PowerShell and Azure CLI together, but PowerShell is mentioned first and repeatedly as a primary tool for administration. There are no explicit Linux/macOS examples or tool recommendations, and the ordering of tools and examples tends to favor Windows-centric approaches. While Azure CLI is cross-platform, the lack of explicit Linux/macOS instructions or parity in examples creates a subtle Windows bias.
Recommendations
  • Provide explicit Linux/macOS examples alongside PowerShell, especially for command-line tasks.
  • When listing tools, alternate or randomize the order of Azure CLI and PowerShell, or mention Azure CLI first to highlight its cross-platform nature.
  • Include notes or links for Linux/macOS users, clarifying how to perform tasks using bash or other native shells.
  • Add screenshots or walkthroughs for Linux/macOS environments where applicable.
  • Ensure that all referenced tools are available and documented for Linux/macOS users.
GitHub Create Pull Request
IoT Central Tutorial - Use the REST API to manage an application ...ain/articles/iot-central/core/tutorial-use-rest-api.md
Low Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Missing Linux Example Windows First
Summary
The tutorial exclusively uses Azure CLI commands and shell scripting syntax that is compatible with Bash (Linux/macOS) and PowerShell (Windows). However, all variable assignment examples use Bash syntax (e.g., appName=...), and there is no mention of PowerShell-specific syntax or Windows command prompt alternatives. There are no explicit Windows-only tools or examples, nor are there instructions that would only work on Windows. The Azure CLI is cross-platform, but the documentation implicitly assumes a Bash-like shell environment, which may cause friction for Windows users who use Command Prompt or PowerShell.
Recommendations
  • Add explicit notes or examples for PowerShell and Windows Command Prompt users, showing equivalent variable assignment and command usage.
  • Clarify that the Azure CLI commands are shown in Bash syntax and provide links or guidance for running Azure CLI on Windows, including PowerShell equivalents.
  • Consider including a section or callout for cross-platform shell compatibility, especially for variable assignment and command chaining.
GitHub Create Pull Request