IoT Hub

112
Total Pages
83
Linux-Friendly Pages
29
Pages with Bias
25.9%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

155 issues found
Showing 1-25 of 155 flagged pages
IoT Hub Upload files from your device to the cloud with Azure IoT Hub ...-docs/blob/main/articles/iot-hub/how-to-file-upload.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a bias towards Windows by mentioning Azure PowerShell as a configuration option alongside Azure CLI and the Azure portal, but does not mention Linux-specific tools or provide parity for Linux users. The order of configuration options lists PowerShell (a Windows-centric tool) before CLI, and there are no explicit Linux examples or references to Linux shell commands, despite the cross-platform nature of the SDKs.
Recommendations
  • Explicitly mention that Azure CLI is cross-platform and provide examples for both Windows (PowerShell) and Linux (Bash) where relevant.
  • Include Linux/Bash command examples for configuring file upload, not just Azure PowerShell.
  • Clarify that all SDK samples are runnable on both Windows and Linux, and provide any necessary platform-specific instructions.
  • If PowerShell is mentioned, also mention Bash or other Linux shells to ensure parity.
  • Consider reordering configuration options to list Azure CLI before PowerShell, or group them by platform.
GitHub Create Pull Request
IoT Hub Managing public network access for Azure IoT Hub ...main/articles/iot-hub/iot-hub-public-network-access.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 Missing Linux Example
Summary
The documentation provides command-line examples for Azure CLI and Azure PowerShell, but does not mention or provide Linux-specific shell examples (e.g., bash) or clarify that Azure PowerShell is primarily a Windows tool. The order of examples places PowerShell after CLI, but the troubleshooting and access instructions do not address Linux-specific scenarios, such as proxy configuration or shell differences. There is no mention of Linux tools or patterns, and the documentation assumes familiarity with Windows-centric tools and workflows.
Recommendations
  • Explicitly state that Azure CLI works cross-platform (Windows, Linux, macOS) and provide bash shell examples for Linux users.
  • Clarify that Azure PowerShell is primarily a Windows tool and suggest alternatives for Linux users (e.g., using Azure CLI in bash/zsh).
  • Add troubleshooting steps for Linux environments, such as checking iptables, firewalld, or proxy settings commonly used on Linux.
  • Include screenshots or instructions for accessing Cloud Shell from Linux terminals.
  • Ensure parity in examples by providing both PowerShell and bash equivalents for all command-line instructions.
GitHub Create Pull Request
IoT Hub How to manage devices and modules using twins ...docs/blob/main/articles/iot-hub/manage-device-twins.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 exhibits mild Windows bias. PowerShell-specific tips are provided (escaping double quotes), and Windows Terminal is mentioned as an example app for Azure Cloud Shell. No Linux-specific shell guidance (e.g., Bash quoting) is given, and Windows tools are referenced before any Linux equivalents. While the Azure CLI is cross-platform, the documentation assumes Windows environments in examples and tips.
Recommendations
  • Add Linux/Bash-specific tips for quoting and escaping JSON in CLI commands (e.g., single vs double quotes, backslash usage).
  • Mention Linux terminal applications (e.g., GNOME Terminal, Konsole) alongside Windows Terminal when discussing Azure Cloud Shell.
  • Provide explicit examples or notes for running Azure CLI commands in Linux/macOS environments, including differences in shell syntax.
  • Ensure that PowerShell-specific advice is paired with equivalent Bash/zsh guidance for Linux users.
GitHub Create Pull Request
IoT Hub Register and connect an IoT device ...cs/blob/main/articles/iot-hub/create-connect-device.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation page demonstrates a moderate Windows bias. While the main examples for device management use the Azure portal and Azure CLI (which are cross-platform), the 'Other tools for managing device identities' section lists PowerShell commands and Visual Studio Code before mentioning the REST API. PowerShell is a Windows-centric tool, and its mention before Linux-native options (such as Bash scripting or Linux-specific tools) suggests a preference for Windows environments. There are no explicit Linux examples, and no Linux-specific tools or patterns are discussed.
Recommendations
  • Add explicit Linux/Bash examples for common device management tasks, such as using curl with the REST API.
  • Mention Linux-native tools or workflows (e.g., Bash scripts, shell utilities) alongside PowerShell in the 'Other tools' section.
  • Clarify that Azure CLI is cross-platform and provide installation/usage notes for Linux users.
  • Consider listing REST API usage before PowerShell to avoid Windows-first ordering.
  • Include troubleshooting or environment setup notes for Linux users where relevant.
GitHub Create Pull Request
IoT Hub Understand Azure IoT Hub endpoints ...ob/main/articles/iot-hub/iot-hub-devguide-endpoints.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates Windows bias primarily in the section about assigning roles for Cosmos DB authentication. It explicitly mentions Azure CLI and Azure PowerShell as the only supported methods, with PowerShell listed before CLI. There are no Linux-specific examples, nor is there mention of Bash or other Linux-native tools. The only code sample provided is in C#, which is cross-platform, but the operational instructions focus on Windows-centric tooling. No Linux shell or cross-platform command-line examples are provided for tasks like listing blobs or assigning roles.
Recommendations
  • Provide explicit Bash/Azure CLI examples for role assignment and other management tasks, ensuring parity with PowerShell instructions.
  • List Azure CLI before PowerShell when describing cross-platform management options, or clarify that both are cross-platform.
  • Include Linux-specific notes or examples where relevant, especially for command-line operations.
  • Add a section or callout confirming that all SDKs and APIs are usable from Linux environments, and provide links to Linux setup guides.
  • Where code samples are given, note their cross-platform compatibility and, if possible, provide equivalent samples in languages or tools popular on Linux (e.g., Python, Bash).
GitHub Create Pull Request
IoT Hub Collect device debug logs ...ob/main/articles/iot-hub/how-to-collect-device-logs.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 page exhibits a Windows bias in the C#/.NET section by presenting Windows/PowerShell/ETW instructions and tools before Linux equivalents, with more detailed scripting guidance for Windows (PowerShell scripts, ETW) and only later mentioning Linux (dotnet-trace). The Windows instructions are more prominent and prescriptive, while Linux instructions are less detailed and lack parity in tooling explanations. Other language sections (C, Java, JS, Python, Embedded C) are generally OS-neutral or provide examples applicable to both platforms.
Recommendations
  • Present Windows and Linux instructions side-by-side or in parallel sections, rather than listing Windows first.
  • Provide equally detailed guidance and tooling for Linux, including example scripts or automation for trace collection.
  • Mention Linux tools (e.g., dotnet-trace) before or alongside Windows tools (ETW, PowerShell scripts) to avoid prioritizing Windows.
  • Clarify any limitations or differences between Windows and Linux trace collection methods, and offer troubleshooting tips for both.
  • Ensure all examples (e.g., file paths, environment variables) use OS-agnostic or dual-platform formats where possible.
GitHub Create Pull Request
IoT Hub Create and delete routes and endpoints by using Azure Resource Manager ...-docs/blob/main/articles/iot-hub/how-to-routing-arm.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 Missing Linux Example
Summary
The documentation provides deployment instructions using both Azure CLI and PowerShell, but PowerShell examples are given equal prominence to CLI, and file path examples use Windows-style backslashes (e.g., "my\path\to\template.json") in CLI commands. There is no explicit mention of Linux or macOS environments, nor are there examples tailored for those platforms (e.g., forward slashes in file paths, bash-specific notes). The documentation assumes use of the Azure portal and Cloud Shell, which are cross-platform, but local deployment instructions show a subtle Windows bias.
Recommendations
  • Add explicit Linux/macOS examples for local deployment, including file paths with forward slashes (e.g., "my/path/to/template.json").
  • Clarify that Azure CLI commands work on all platforms, and provide platform-specific notes where file paths or shell syntax may differ.
  • Consider including bash or shell script examples for Linux/macOS users, or a note about using bash in Cloud Shell.
  • If PowerShell is mentioned, clarify that PowerShell Core is cross-platform, and provide instructions for installing and using it on Linux/macOS.
  • Review screenshots and instructions for any platform-specific UI differences, and note them if relevant.
GitHub Create Pull Request
IoT Hub Monitor IoT messages with distributed tracing (preview) ...b/main/articles/iot-hub/iot-hub-distributed-tracing.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias in the 'Run a sample application' section, where build and run instructions are provided exclusively for Windows (Visual Studio, Windows command prompt, .exe output). There are no equivalent Linux or macOS build/run instructions, and Windows-specific tools (Visual Studio, MSVC) are mentioned without cross-platform alternatives. Earlier sections do not show overt bias, but the hands-on sample setup is Windows-centric.
Recommendations
  • Add explicit Linux and macOS instructions for building and running the sample application, including required dependencies (e.g., GCC/Clang, make, cmake usage on Unix-like systems).
  • Provide terminal commands for cloning, building, and running the sample on Linux/macOS, including expected output and troubleshooting tips.
  • Mention cross-platform CMake generators and compilers, and clarify that Visual Studio is not required on non-Windows platforms.
  • Where screenshots or code blocks show Windows paths or .exe files, include equivalent Unix-style paths and commands.
  • Consider adding a table or tabbed section for 'Windows', 'Linux', and 'macOS' to ensure parity in hands-on instructions.
GitHub Create Pull Request
IoT Hub Get started with module identity and module twins (Portal) ...ob/main/articles/iot-hub/module-twins-portal-dotnet.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by exclusively providing instructions and examples for Visual Studio and .NET on Windows, with no equivalent guidance for Linux users. All development steps assume the use of Visual Studio (a Windows-centric IDE), and there are no alternative instructions for Linux-compatible tools or SDKs. The only non-Windows command shown is an OpenSSL example for certificate creation, but the main workflow is Windows/.NET-focused.
Recommendations
  • Add equivalent instructions for developing with .NET on Linux, such as using VS Code or command-line tools (dotnet CLI).
  • Provide Linux-specific steps for installing the Azure IoT Hub SDK, including package installation via dotnet CLI or other Linux package managers.
  • Include example code and build/run instructions for Linux environments (e.g., using terminal commands instead of Visual Studio UI).
  • Mention cross-platform compatibility of the SDK and clarify any OS-specific limitations.
  • Add screenshots or terminal output examples from Linux environments to balance the Windows-centric visuals.
GitHub Create Pull Request
IoT Hub Get Started with ADR and Certificate Management in IoT Hub (Preview) ...main/articles/iot-hub/iot-hub-device-registry-setup.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 a Windows bias by explicitly offering a PowerShell script deployment method labeled as 'Windows only', while not providing an equivalent for Linux (e.g., Bash). The deployment method table lists PowerShell before mentioning any Linux alternatives, and no Linux-specific scripting examples (such as Bash) are provided. The Azure CLI instructions are cross-platform, but the scripting option is Windows-centric. There is also mention of Windows tools (PowerShell) without Linux parity.
Recommendations
  • Add a Bash script example for Linux users alongside the PowerShell script, ensuring parity in automation options.
  • Clarify that Azure CLI is cross-platform and highlight its usage for both Windows and Linux.
  • In the deployment method table, avoid listing Windows-only options before cross-platform or Linux options; consider listing Azure CLI first.
  • Explicitly mention Linux support and provide links or instructions for Linux users where appropriate.
  • Review included script samples to ensure Linux/Bash equivalents are present and referenced.
GitHub Create Pull Request
IoT Hub Overview of Azure IoT Hub message enrichments ...ticles/iot-hub/iot-hub-message-enrichments-overview.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 Missing Linux Example
Summary
The documentation lists configuration methods for message enrichments in a table, mentioning Azure Portal, Azure CLI, and Azure PowerShell. Azure PowerShell is highlighted as a distinct method, which is primarily a Windows tool, and no Linux-specific tools or shell examples (e.g., Bash) are provided. The Azure CLI is cross-platform, but no explicit Linux or Bash examples are given, nor is there mention of scripting in Linux environments. The order of presentation (Portal, CLI, PowerShell) puts Windows-centric tooling before any Linux-specific guidance, and the only command-line example with a link is for PowerShell.
Recommendations
  • Add explicit Linux/Bash examples for configuring message enrichments using Azure CLI.
  • Clarify that Azure CLI is cross-platform and provide sample commands for both Windows (CMD/PowerShell) and Linux (Bash).
  • If possible, mention automation via REST API or SDKs that are platform-agnostic.
  • Avoid presenting PowerShell as a primary method unless parity is shown for Linux shells.
  • Consider reordering the configuration methods to list cross-platform tools (CLI, REST API) before Windows-specific tools.
GitHub Create Pull Request
IoT Hub Tutorial - Create and upload certificates for testing ...blob/main/articles/iot-hub/tutorial-x509-test-certs.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 demonstrates a moderate Windows bias. Windows-specific instructions and tools (such as Git Bash and winpty) are mentioned first or exclusively in several places. The prerequisites and setup sections focus on Windows users, suggesting Git Bash as the primary shell and referencing Windows installation paths. PowerShell scripts are mentioned before Bash scripts, and the use of winpty for OpenSSL commands is emphasized for Windows users. Linux instructions are present and correct, but are generally secondary in presentation.
Recommendations
  • Present Linux and Windows instructions with equal prominence, alternating which platform is listed first or using a neutral ordering.
  • In prerequisites, provide clear instructions for installing OpenSSL and Git on Linux and macOS, not just Windows.
  • Avoid recommending Git Bash as the primary shell for all users; suggest native shells for Linux/macOS.
  • Mention Bash scripts before or alongside PowerShell scripts, and clarify script compatibility for each platform.
  • Where winpty is required for Windows, explain why and offer alternatives for users on other platforms.
  • Add explicit instructions for macOS users where applicable.
  • Ensure all examples and tooling references are available and tested on Linux/macOS, not just Windows.
GitHub Create Pull Request
IoT Hub Register and connect an IoT device ...cs/blob/main/articles/iot-hub/create-connect-device.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation page demonstrates a moderate Windows bias. While the main examples use the Azure portal and Azure CLI (which are cross-platform), the 'Other tools' section lists PowerShell commands and Visual Studio Code before mentioning REST API, with PowerShell being a Windows-centric tool. There are no Linux-specific tools or patterns mentioned, and PowerShell is highlighted as a primary alternative management method. No Linux shell or scripting examples are provided, and the ordering of tools favors Windows-first approaches.
Recommendations
  • Include examples or references for Linux-native tools, such as Bash scripts or Linux shell utilities for device management.
  • Mention cross-platform alternatives to PowerShell, such as Bash or Python scripts, especially for automation.
  • Clarify that Azure CLI is cross-platform and provide explicit instructions for installation and usage on Linux and macOS.
  • Add links or examples for using REST API with curl or other Linux-friendly tools.
  • Balance the 'Other tools' section by listing Linux-friendly options before or alongside Windows-centric tools like PowerShell.
GitHub Create Pull Request
IoT Hub Understand Azure IoT Hub endpoints ...ob/main/articles/iot-hub/iot-hub-devguide-endpoints.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page exhibits Windows bias primarily in its guidance for assigning roles to managed identities for Cosmos DB. It explicitly mentions Azure PowerShell and Azure CLI as required tools, but the CLI example is referenced only in a link, while PowerShell is mentioned directly. There are no Linux-specific instructions or examples, and the only code sample provided is in C#, which is more commonly associated with Windows development environments. No Bash or Linux shell examples are present, and there is no mention of Linux tools or patterns for common tasks such as listing blobs or assigning roles.
Recommendations
  • Provide explicit Bash/Azure CLI examples for role assignment and other management tasks, not just PowerShell.
  • Include Linux shell code samples for blob listing and other storage operations, such as using az CLI or REST API with curl.
  • When referencing tools, mention Azure CLI before or alongside Azure PowerShell, and clarify that CLI is cross-platform.
  • Add notes or sections highlighting Linux compatibility and usage patterns for IoT Hub management.
  • Ensure that all examples and instructions are platform-neutral or offer both Windows and Linux alternatives.
GitHub Create Pull Request
IoT Hub Collect device debug logs ...ob/main/articles/iot-hub/how-to-collect-device-logs.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 in the C#/.NET section, where Windows-specific tools (Event Tracing for Windows, PowerShell scripts) are described first and in greater detail than Linux equivalents. The Windows instructions use dedicated scripts and ETW, while Linux instructions rely on a generic dotnet-trace tool. The Windows approach is presented before the Linux one, and the use of PowerShell scripts is emphasized. Other language sections (C, Java, JavaScript, Python, Embedded C) are generally cross-platform or neutral.
Recommendations
  • Present Linux and Windows instructions in parallel, or alternate which is described first.
  • Provide equivalent Linux-specific tooling or scripts if available, or clarify any feature gaps.
  • Give equal detail and troubleshooting tips for Linux as for Windows (e.g., how to analyze .nettrace files, common issues).
  • Mention cross-platform alternatives where possible, and avoid assuming PowerShell or ETW are the default.
  • Explicitly state platform limitations or differences in SDK logging capabilities.
GitHub Create Pull Request
IoT Hub Get Started with ADR and Certificate Management in IoT Hub (Preview) ...main/articles/iot-hub/iot-hub-device-registry-setup.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by explicitly offering a PowerShell script deployment method labeled as 'Windows only', while not providing an equivalent Bash or shell script for Linux/macOS users. The deployment method table lists PowerShell before any mention of Linux scripting, and there is no example or guidance for Linux users wishing to automate setup outside of Azure CLI. The documentation references Windows-specific tooling (PowerShell) and does not mention Linux alternatives or parity in scripting automation.
Recommendations
  • Provide a Bash or shell script example for Linux/macOS users alongside the PowerShell script.
  • Clarify that Azure CLI is cross-platform and highlight its use for both Windows and Linux.
  • If automation scripts are provided, ensure both PowerShell and Bash versions are available and referenced equally.
  • Avoid labeling deployment methods as 'Windows only' without offering a Linux/macOS equivalent.
  • Consider adding a section discussing cross-platform compatibility and best practices for both Windows and Linux environments.
GitHub Create Pull Request
IoT Hub Overview of Azure IoT Hub message enrichments ...ticles/iot-hub/iot-hub-message-enrichments-overview.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 Missing Linux Example
Summary
The documentation lists Azure PowerShell as a configuration method alongside Azure CLI and Portal, but does not mention Linux-specific tools or provide Linux shell examples. PowerShell is a Windows-centric tool, and its mention before any Linux alternatives (such as Bash scripts or REST API usage) suggests a Windows-first bias. There are no explicit Linux examples or references to Linux command-line usage, and the documentation does not clarify cross-platform compatibility for the CLI or PowerShell commands.
Recommendations
  • Add explicit Bash or shell examples for configuring message enrichments using Azure CLI on Linux.
  • Clarify that Azure CLI is cross-platform and provide usage examples for both Windows and Linux environments.
  • Include REST API examples for configuring enrichments, which are platform-agnostic.
  • Mention that PowerShell Core is available on Linux, if relevant, and provide instructions for both Windows PowerShell and PowerShell Core.
  • Ensure that configuration methods are presented in a neutral order (e.g., Portal, CLI, PowerShell, REST API) rather than prioritizing Windows-centric tools.
GitHub Create Pull Request
IoT Hub Get started with module identity and module twins (Portal) ...ob/main/articles/iot-hub/module-twins-portal-dotnet.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by exclusively providing instructions and examples for Visual Studio (a Windows-centric IDE), .NET Framework, and Windows-specific development workflows. There are no Linux or cross-platform alternatives mentioned for creating the module identity, installing SDKs, or running the sample code. The use of Visual Studio and NuGet Package Manager is presented as the default, with no mention of Linux-compatible tools or command-line alternatives.
Recommendations
  • Include instructions for creating and running the sample app on Linux, using .NET Core/SDK and cross-platform editors (e.g., VS Code, JetBrains Rider, or command line).
  • Provide examples for installing the Azure IoT Hub SDK using the dotnet CLI (e.g., 'dotnet add package') instead of only NuGet Package Manager in Visual Studio.
  • Mention Linux-compatible development environments and workflows, such as using VS Code or the terminal.
  • Add explicit Linux/macOS setup steps, including prerequisites (e.g., .NET SDK installation on Linux) and build/run commands.
  • Ensure screenshots and UI references are not exclusively tied to Windows tools; provide alternatives or clarify cross-platform options.
GitHub Create Pull Request
IoT Hub Monitor IoT messages with distributed tracing (preview) ...b/main/articles/iot-hub/iot-hub-distributed-tracing.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias, especially in the 'Run a sample application' section, where build and run instructions are provided only for Windows (Visual Studio, .cmd commands, .exe output). There are no explicit Linux or macOS build/run instructions, and Windows-specific tools (Visual Studio, Visual Studio Code) are mentioned first or exclusively. The documentation does not provide parity for Linux users, who would need to adapt the instructions themselves.
Recommendations
  • Provide parallel build and run instructions for Linux (and optionally macOS), including required dependencies (e.g., gcc, make, cmake), and shell commands for cloning, building, and running the sample.
  • Mention Linux tools (e.g., gcc, g++, make) alongside Windows tools (Visual Studio), and provide equivalent steps for both platforms.
  • Include example terminal commands for Linux (bash shell) in addition to Windows command prompt commands.
  • Clarify that the C SDK and distributed tracing features are cross-platform, and link directly to Linux/macOS-specific build guides where appropriate.
  • Add screenshots or terminal output examples from Linux environments to balance the visual representation.
GitHub Create Pull Request
IoT Hub Managing public network access for Azure IoT Hub ...main/articles/iot-hub/iot-hub-public-network-access.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 Missing Linux Example
Summary
The documentation provides command-line examples for both Azure CLI and Azure PowerShell, but PowerShell is listed immediately after CLI without mention of Linux-specific shell usage (e.g., Bash). There are no explicit Linux or macOS instructions, nor is there mention of platform differences or alternatives to PowerShell for non-Windows users. The troubleshooting and workflow descriptions assume use of the Azure portal and tools that are most familiar to Windows users, with no guidance for Linux environments.
Recommendations
  • Add explicit Bash shell examples for Linux/macOS users alongside Azure CLI and PowerShell commands.
  • Clarify that Azure CLI works cross-platform and provide instructions for installing and running CLI on Linux/macOS.
  • Mention that PowerShell Core is available on Linux/macOS, or recommend Bash alternatives where appropriate.
  • Include screenshots or instructions for accessing Azure Cloud Shell from Linux/macOS terminals.
  • Add troubleshooting steps relevant to Linux network configurations (e.g., iptables, firewalld, proxy settings) in addition to Windows-specific advice.
GitHub Create Pull Request
IoT Hub How to manage devices and modules using twins ...docs/blob/main/articles/iot-hub/manage-device-twins.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 demonstrates mild Windows bias. PowerShell-specific tips are included for escaping quotes, but no equivalent guidance is provided for Linux shells (e.g., Bash). The mention of Windows Terminal as an app for Azure Cloud Shell precedes any mention of Linux terminals. No Linux-specific examples or troubleshooting notes are present, and the CLI examples do not address shell differences. The documentation assumes familiarity with Windows tooling and patterns, with no explicit parity for Linux users.
Recommendations
  • Add tips for Bash/Linux users on escaping quotes and handling JSON in CLI commands.
  • Mention Linux terminal applications (e.g., GNOME Terminal, Konsole) alongside Windows Terminal when discussing Azure Cloud Shell.
  • Include troubleshooting notes for common Linux shell issues (e.g., single vs double quotes, file paths).
  • Ensure that PowerShell-specific instructions are paired with equivalent Bash/Linux instructions.
  • Review screenshots and UI references to ensure they are not Windows-centric, or provide Linux alternatives where relevant.
GitHub Create Pull Request
IoT Hub Tutorial - Create and upload certificates for testing ...blob/main/articles/iot-hub/tutorial-x509-test-certs.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 demonstrates a moderate Windows bias. Windows-specific instructions and tools (such as Git Bash and winpty) are mentioned first or exclusively in several places. The prerequisites and setup steps emphasize Windows environments, recommending Git Bash (a Windows tool) for OpenSSL usage and providing detailed guidance for Windows users. PowerShell scripts are referenced before Bash scripts. Although Linux instructions are present and examples are provided for both platforms, Windows tools and patterns are often foregrounded, and Linux-native workflows are not described in detail.
Recommendations
  • Present Linux and Windows instructions in parallel, or alternate which platform is shown first in code blocks and explanations.
  • Include native Linux setup instructions for OpenSSL, rather than focusing on Git Bash (which is primarily a Windows tool).
  • Reference Bash scripts before or alongside PowerShell scripts, and clarify their usage on Linux systems.
  • Add explicit guidance for Linux users regarding environment setup, such as package installation commands (e.g., apt, yum) for OpenSSL and Git.
  • Avoid recommending Windows-specific tools (like Git Bash) for Linux users, and provide platform-appropriate alternatives.
  • Ensure that all examples and instructions are equally detailed for both platforms, and avoid assuming a Windows-centric workflow.
GitHub Create Pull Request
IoT Hub https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-hub/create-connect-device.md ...cs/blob/main/articles/iot-hub/create-connect-device.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First Missing Linux Example
Summary
The documentation demonstrates a Windows bias by explicitly mentioning PowerShell as a management tool, listing it first among 'Other tools', and referencing Visual Studio Code (commonly used on Windows) before REST API. There are no Linux-specific management tools (such as Bash scripts or Linux-native utilities) mentioned, and no examples for Linux-specific environments or patterns. The CLI examples are cross-platform, but the absence of Linux-focused alternatives and the prioritization of Windows tools indicate a bias.
Recommendations
  • Include Linux-native management tool examples, such as Bash scripts or references to Linux desktop environments.
  • Mention cross-platform editors (e.g., VS Code) with explicit notes about Linux compatibility.
  • Add examples using Linux package managers for installing Azure CLI and related tools.
  • List REST API and CLI before Windows-specific tools like PowerShell in the 'Other tools' section.
  • Provide explicit instructions or links for Linux users where workflows differ (e.g., certificate management, file paths).
GitHub Create Pull Request
IoT Hub https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-hub/module-twins-portal-dotnet.md ...ob/main/articles/iot-hub/module-twins-portal-dotnet.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by exclusively using Visual Studio and .NET examples, referencing Windows-specific development tools and workflows, and omitting Linux equivalents or cross-platform alternatives. There are no instructions or examples for Linux users, such as using VS Code, command-line .NET tools, or alternative SDKs. The only non-Windows-specific command is the openssl example for certificate creation, but the main workflow is Windows-centric.
Recommendations
  • Add instructions for creating and running the sample using .NET CLI (dotnet) on Linux and macOS.
  • Include examples using VS Code or other cross-platform editors instead of only Visual Studio.
  • Provide guidance for installing the Azure IoT SDK on Linux (e.g., via dotnet CLI or package managers).
  • Explicitly mention platform compatibility and provide parity in screenshots and step-by-step instructions for Linux environments.
  • Consider including sample code in other languages supported by Azure IoT SDKs (e.g., Python, Node.js) to broaden accessibility.
GitHub Create Pull Request
IoT Hub https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-hub/iot-hub-understand-ip-address.md ...main/articles/iot-hub/iot-hub-understand-ip-address.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates Windows bias by referencing PowerShell and CLI tools in the context of firewall configuration and connectivity, without mentioning Linux equivalents or providing Linux-specific examples. The guidance on avoiding connectivity issues explicitly lists PowerShell before CLI, and there are no examples or instructions for Linux firewall tools (such as iptables, ufw, or firewalld). This may leave Linux users without clear guidance for their platform.
Recommendations
  • Include Linux-specific firewall configuration examples (e.g., using iptables, ufw, or firewalld) alongside Windows instructions.
  • Mention cross-platform CLI tools (such as Azure CLI) before or alongside PowerShell, clarifying their availability on Linux and macOS.
  • Provide explicit Linux command-line examples for querying and updating firewall rules.
  • Add notes or sections addressing Linux and macOS environments to ensure parity and inclusivity.
  • When referencing tools, use neutral language (e.g., 'CLI or PowerShell clients') and clarify platform support.
GitHub Create Pull Request
← Previous Page 1 of 7 Next →