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 76-100 of 155 flagged pages
IoT Hub Get Started with ADR and Certificate Management in IoT Hub (Preview) ...main/articles/iot-hub/iot-hub-device-registry-setup.md
Medium Priority View Details →
Scanned: 2026-01-15 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation offers two deployment methods: Azure CLI and PowerShell script. The PowerShell script is explicitly labeled as 'Windows only,' and is presented alongside the cross-platform Azure CLI method. There are no Linux/macOS shell script equivalents provided, and PowerShell is the only scripting automation option mentioned. The ordering and labeling may imply a preference or greater support for Windows tooling.
Recommendations
  • Add a Bash or shell script example for Linux/macOS users to automate the deployment process, mirroring the PowerShell script functionality.
  • Clarify that the PowerShell script is Windows-only and suggest alternatives for Linux/macOS users, such as using Azure CLI or providing a sample Bash script.
  • Consider listing the cross-platform Azure CLI method first, or explicitly stating that it is recommended for all platforms.
  • If automation is important, provide guidance or templates for scripting with Bash/zsh on non-Windows platforms.
GitHub Create Pull Request
IoT Hub Understand Azure IoT Hub endpoints ...ob/main/articles/iot-hub/iot-hub-devguide-endpoints.md
Medium Priority View Details →
Scanned: 2026-01-14 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 exhibits moderate Windows bias. The only code example provided uses C# and the Microsoft.Azure.Storage library, which is most commonly used in Windows/.NET environments. In the section about assigning roles for Cosmos DB, Azure PowerShell and Azure CLI are mentioned, but PowerShell is listed first and the instructions do not clarify Linux/macOS usage. There are no explicit Linux or cross-platform examples, and no mention of Linux-specific tools or patterns. The documentation assumes familiarity with Windows-centric development environments.
Recommendations
  • Provide equivalent code samples using cross-platform languages (e.g., Python, Node.js) and SDKs that work natively on Linux/macOS.
  • When referencing Azure CLI and PowerShell, clarify that Azure CLI is fully supported on Linux/macOS and provide explicit Linux/macOS command examples.
  • Add notes or examples for listing blobs/files using Linux tools (e.g., az CLI, REST API via curl, Python SDK).
  • Ensure that instructions for role assignment and other management tasks include Linux/macOS compatible steps and do not default to PowerShell.
  • Where possible, avoid listing Windows/PowerShell tools before cross-platform alternatives.
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
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation page mentions PowerShell scripts as a deployment method, explicitly noting 'Windows only', while the Azure CLI method is presented as cross-platform. The PowerShell option is listed second, but its presence and explicit Windows-only note highlight a Windows bias. No Linux/macOS-specific scripting alternatives (e.g., Bash) are mentioned, nor is there guidance for Linux users wishing to automate the process outside Azure CLI.
Recommendations
  • Add Bash or shell script examples for Linux/macOS users alongside PowerShell scripts.
  • Clarify that Azure CLI is cross-platform and recommend it as the default for non-Windows users.
  • If automation is possible via other scripting languages (Python, etc.), mention or link to those options.
  • Explicitly state platform compatibility for each method in the deployment table, and consider listing cross-platform options first.
GitHub Create Pull Request
IoT Hub Monitor IoT messages with distributed tracing (preview) ...b/main/articles/iot-hub/iot-hub-distributed-tracing.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation provides detailed build and run instructions for Windows environments, specifically using Visual Studio and Windows command prompts. Linux/macOS build instructions are only referenced via external links and not described inline. All example commands and troubleshooting are Windows-centric, and there are no step-by-step Linux or macOS instructions for compiling or running the sample application.
Recommendations
  • Add explicit, step-by-step instructions for building and running the sample on Linux and macOS, including required packages, compiler setup, and example shell commands.
  • Include troubleshooting tips for common Linux/macOS build issues (e.g., missing dependencies, permissions).
  • Present Windows and Linux/macOS instructions in parallel tabs or sections to ensure equal visibility.
  • Provide example output and run commands for Linux/macOS (e.g., using ./iothub_ll_telemetry_sample instead of .exe).
GitHub Create Pull Request
IoT Hub Overview of Azure IoT Hub message enrichments ...ticles/iot-hub/iot-hub-message-enrichments-overview.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation lists Azure PowerShell as a primary method for configuring message enrichments, alongside Azure CLI and Portal, but does not mention Linux/macOS-specific tools or provide parity for shell scripting. PowerShell is a Windows-centric tool, and its mention before any Linux-native alternatives (like Bash scripts or REST API usage) may create friction for non-Windows users. No explicit Linux/macOS examples or guidance are provided.
Recommendations
  • Add explicit Linux/macOS examples, such as using Bash with Azure CLI or REST API calls.
  • Clarify that Azure CLI is cross-platform and provide sample commands for Linux/macOS terminals.
  • Reorder the configuration methods to list cross-platform tools (Azure CLI, Portal) before Windows-centric tools (PowerShell).
  • Mention REST API as an alternative for automation on any OS.
GitHub Create Pull Request
IoT Hub Understanding the IP address of your IoT hub | Microsoft Docs ...main/articles/iot-hub/iot-hub-understand-ip-address.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation references Azure CLI and PowerShell as clients that may be affected by firewall rules, but does not mention Linux/macOS equivalents or provide examples for non-Windows platforms. The focus on PowerShell and CLI without clarifying cross-platform support or offering Linux-specific guidance creates a subtle Windows bias.
Recommendations
  • Explicitly mention that Azure CLI is cross-platform and can be used on Linux/macOS as well as Windows.
  • Add examples or notes for Linux/macOS users, such as using Bash or shell scripts to automate service tag retrieval.
  • Reference Linux-native tools (e.g., iptables, ufw) when discussing firewall configuration, alongside Windows firewall.
  • Clarify that PowerShell Core is available on Linux/macOS, or provide alternative command-line instructions for those platforms.
GitHub Create Pull Request
IoT Hub Managing public network access for Azure IoT Hub ...main/articles/iot-hub/iot-hub-public-network-access.md
Medium Priority View Details →
Scanned: 2026-01-14 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 the PowerShell example is given equal prominence despite being Windows-specific. There are no explicit Linux/macOS shell examples (e.g., Bash), and troubleshooting steps do not mention Linux/macOS-specific issues or tools. The Azure portal instructions are platform-agnostic, but command-line and troubleshooting guidance leans toward Windows users.
Recommendations
  • Add explicit Bash/Linux/macOS shell examples alongside Azure CLI and PowerShell, clarifying that Azure CLI works cross-platform.
  • Clarify that Azure PowerShell is Windows-specific and recommend Azure CLI for Linux/macOS users.
  • Include troubleshooting notes for Linux/macOS users, such as checking firewall rules, proxy settings, or using curl for endpoint testing.
  • Where possible, present Azure CLI (cross-platform) examples before PowerShell examples.
  • Mention that Azure Cloud Shell is available on all platforms via browser.
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
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation is heavily oriented toward Windows development environments, specifically Visual Studio and .NET, with all examples and instructions tailored to Windows users. There are no Linux/macOS equivalents or alternative SDK/language examples provided, and the workflow assumes Visual Studio is available.
Recommendations
  • Add instructions and examples for Linux/macOS users, such as using VS Code or command-line tools.
  • Include .NET Core/.NET 6+ cross-platform instructions, not just .NET Framework/Visual Studio.
  • Provide examples for other languages supported by Azure IoT SDKs (e.g., Python, Node.js) with Linux-friendly workflows.
  • Explicitly mention how Linux/macOS users can install dependencies and run the sample.
  • Reorder or parallelize instructions so that Windows and Linux/macOS users see relevant steps side-by-side.
GitHub Create Pull Request
IoT Hub Tutorial - Create and upload certificates for testing ...blob/main/articles/iot-hub/tutorial-x509-test-certs.md
Medium Priority View Details →
Scanned: 2026-01-14 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, such as using 'winpty' for OpenSSL commands and references to Git Bash (a Windows-centric tool), are presented before Linux equivalents. The prerequisites and notes emphasize Windows installation patterns and tools, and recommend using Git Bash/OpenSSL as installed via Git for Windows. While Linux instructions are present and parity is generally maintained for command syntax, the overall flow and tool recommendations favor Windows users and may create friction for Linux/macOS users.
Recommendations
  • Present Linux/macOS instructions and tools with equal prominence and detail as Windows, including installation steps for OpenSSL and Git.
  • Avoid recommending Git Bash as the default shell for non-Windows platforms; suggest native terminals for Linux/macOS.
  • Clarify that 'winpty' is only needed on Windows and provide context for Linux/macOS users.
  • Add explicit instructions for verifying OpenSSL installation on Linux/macOS (e.g., using package managers like apt, yum, brew).
  • Where possible, avoid Windows-centric terminology or ordering (e.g., do not list Windows tabs/examples first).
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
Medium Priority View Details →
Scanned: 2026-01-13 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 notable Windows bias by exclusively providing instructions and examples for Visual Studio and .NET on Windows, with no mention of Linux or macOS development environments. All steps for creating and running the sample app assume a Windows setup, and there are no alternative instructions for Linux users (e.g., using VS Code, .NET CLI, or Mono). The only cross-platform tool mentioned is openssl for certificate generation, but the main workflow is Windows-centric.
Recommendations
  • Add instructions for creating and running the sample app using .NET CLI and VS Code, which are cross-platform.
  • Include Linux/macOS-specific setup steps, such as installing .NET SDK on Ubuntu/macOS.
  • Provide screenshots or terminal examples for Linux/macOS environments.
  • Clarify that the .NET SDK and Azure IoT libraries are cross-platform and provide links to relevant Linux/macOS documentation.
  • Mention alternative editors (VS Code, JetBrains Rider) and how to run the sample outside Visual Studio.
GitHub Create Pull Request
IoT Hub Tutorial - Create and upload certificates for testing ...blob/main/articles/iot-hub/tutorial-x509-test-certs.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation exhibits a moderate Windows bias. Windows-specific tools (Git Bash, winpty) are emphasized, and Windows instructions are consistently presented before Linux equivalents. The prerequisites and setup sections focus on Windows scenarios, and the use of PowerShell scripts is mentioned, though Bash scripts are also referenced. Linux instructions are present and functional, but Windows patterns dominate the narrative and ordering.
Recommendations
  • Present Linux/macOS instructions before or alongside Windows instructions, rather than after.
  • Explicitly mention Linux/macOS installation and usage patterns for OpenSSL and Git, including package manager commands (e.g., apt, yum, brew).
  • Clarify that Git Bash and winpty are Windows-specific, and provide native Linux/macOS alternatives (e.g., standard terminal usage).
  • Expand on Bash script usage for Linux/macOS users, and provide parity in script documentation.
  • Avoid language that assumes Windows as the default environment (e.g., 'your Windows machine').
GitHub Create Pull Request
IoT Hub Collect device debug logs ...ob/main/articles/iot-hub/how-to-collect-device-logs.md
Medium Priority View Details →
Scanned: 2026-01-13 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 .NET/C# section by presenting Windows/PowerShell/ETW instructions first, with detailed guidance and links to Windows-specific tools. The Linux equivalent (dotnet-trace) is described after the Windows instructions, with less detail and no parity in scripting or automation. Other language sections (C, Java, JavaScript, Python, Embedded C) are platform-neutral or provide examples applicable to both Windows and Linux.
Recommendations
  • Present Linux and Windows instructions in parallel or with equal prominence, rather than Windows-first.
  • Provide Linux automation examples (e.g., shell scripts) for trace collection, similar to the PowerShell scripts offered for Windows.
  • Include troubleshooting tips for Linux users, such as permissions or common issues with dotnet-trace.
  • Clarify cross-platform applicability in each section, especially where file paths or tooling may differ.
  • Consider adding macOS-specific notes or examples where relevant.
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
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation presents both Azure CLI and PowerShell commands for deployment, but PowerShell examples are given equal prominence to CLI, and file path examples use Windows-style backslashes. There are no Linux/macOS-specific instructions, nor are Linux file path conventions shown. The Azure portal instructions and screenshots are platform-neutral, but command-line instructions could be confusing for Linux/macOS users due to the Windows-centric file paths and lack of explicit Linux guidance.
Recommendations
  • Show Linux/macOS file path examples (e.g., use forward slashes in CLI examples).
  • Explicitly state that Azure CLI works on Windows, Linux, and macOS, and provide any OS-specific notes if needed.
  • Add a note clarifying that PowerShell examples are for Windows, and suggest using Azure CLI for Linux/macOS users.
  • Consider listing Azure CLI instructions before PowerShell, as CLI is cross-platform.
  • If any steps differ for Linux/macOS (e.g., uploading files in Cloud Shell), provide those details.
GitHub Create Pull Request
IoT Hub Understand Azure IoT Hub endpoints ...ob/main/articles/iot-hub/iot-hub-devguide-endpoints.md
Medium Priority View Details →
Scanned: 2026-01-13 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 exhibits mild Windows bias in several areas. The only code example provided uses C# and the Microsoft.Azure.Storage library, which is most commonly used on Windows. Additionally, role assignment for Cosmos DB is described as only possible via Azure CLI or Azure PowerShell, with explicit mention of PowerShell before CLI. There are no Linux-specific tools, shell examples, or cross-platform code samples. The documentation does not mention Linux/macOS equivalents or provide parity in examples, which may create friction for non-Windows users.
Recommendations
  • Provide code samples in cross-platform languages (e.g., Python, Node.js) using SDKs that run on Linux/macOS.
  • Include CLI (az) examples before or alongside PowerShell, especially for role assignments and management tasks.
  • Explicitly mention that Azure CLI is cross-platform and provide Linux/macOS installation links.
  • Add shell script examples for listing blobs/files using az CLI or REST APIs.
  • Clarify that the Microsoft.Azure.Storage library is available for .NET Core, which runs on Linux/macOS, or suggest alternatives.
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
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Powershell Heavy
Summary
The documentation page exhibits Windows bias by explicitly highlighting PowerShell as a deployment method ('Windows only'), mentioning PowerShell before any Linux/macOS equivalents, and referencing Windows-specific scripting tools. While the Azure CLI is cross-platform, the PowerShell script option is presented as a primary method and is not accompanied by a Linux shell script or macOS-specific instructions. There are no Linux/macOS-specific examples or tools mentioned, and the scripting pivot does not clarify Linux support.
Recommendations
  • Add a Bash or shell script example for Linux/macOS users alongside the PowerShell script.
  • Clarify in the deployment method table that PowerShell is Windows-only and provide equivalent instructions for Linux/macOS.
  • Ensure that all code samples and automation scripts have Linux/macOS parity, or explicitly link to such resources.
  • Consider listing the Azure CLI (cross-platform) as the first and preferred method, with platform-specific scripts as secondary options.
  • Include notes or guidance for Linux/macOS users where Windows-specific tools (like PowerShell) are referenced.
GitHub Create Pull Request
IoT Hub Azure IoT Hub IP filters ...ocs/blob/main/articles/iot-hub/iot-hub-ip-filtering.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for managing IP filters, but the PowerShell section is given equal prominence to the CLI, despite PowerShell being primarily a Windows tool. There are no Linux/macOS-specific examples (e.g., bash scripting, curl for REST API), and the ordering of examples places Azure CLI first but does not offer additional Linux-native tooling or guidance. The portal instructions are platform-neutral, but the scripting sections lean toward Windows-centric tools.
Recommendations
  • Add explicit Linux/macOS examples, such as using curl or httpie to interact with the REST API.
  • Clarify that Azure CLI is cross-platform and provide bash script snippets for common tasks.
  • Mention that PowerShell Core is available on Linux/macOS, or link to installation instructions for non-Windows users.
  • Include troubleshooting notes for Linux/macOS users (e.g., network/firewall considerations, CLI authentication differences).
  • Consider listing CLI and REST API examples before PowerShell to reinforce cross-platform parity.
GitHub Create Pull Request
IoT Hub Understanding the IP address of your IoT hub | Microsoft Docs ...main/articles/iot-hub/iot-hub-understand-ip-address.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation references Azure CLI and PowerShell clients when discussing firewall rules, but does not mention Linux/macOS equivalents or provide parity for non-Windows tooling. There are no explicit Linux/macOS examples or references to Bash, shell scripting, or cross-platform command-line usage.
Recommendations
  • Explicitly mention that Azure CLI is cross-platform and can be used on Linux/macOS, not just Windows.
  • Add examples or references for using Bash or shell scripting to automate service tag retrieval and firewall configuration.
  • When discussing PowerShell, also mention alternatives such as Bash or Python scripts for Linux/macOS users.
  • Ensure that any tooling or automation guidance is presented in a cross-platform manner, with examples for both Windows and Linux/macOS environments.
GitHub Create Pull Request
IoT Hub Monitor IoT messages with distributed tracing (preview) ...b/main/articles/iot-hub/iot-hub-distributed-tracing.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example Powershell Heavy
Summary
The documentation page exhibits a notable Windows bias in the 'Run a sample application' section, where build and run instructions are provided exclusively for Windows (Visual Studio, .exe, cmd shell). Linux/macOS build instructions are referenced only via external links and not shown inline. The initial setup steps and example outputs are Windows-centric, and there are no Linux/macOS terminal commands or build/run examples. This creates friction for non-Windows users, who must consult external resources to complete the task.
Recommendations
  • Add explicit Linux/macOS build and run instructions inline, including commands for gcc/clang, make, and running the binary (e.g., './iothub_ll_telemetry_sample').
  • Show example outputs for Linux/macOS environments.
  • Present cross-platform instructions side-by-side or in tabs, rather than referencing Linux/macOS instructions externally.
  • Avoid using Windows-specific terminology (e.g., Visual Studio command prompt) without Linux/macOS equivalents.
  • Include troubleshooting tips for common Linux/macOS build issues.
GitHub Create Pull Request
IoT Hub Managing public network access for Azure IoT Hub ...main/articles/iot-hub/iot-hub-public-network-access.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for checking IoT Hub access, but lists PowerShell commands directly after CLI, with no mention of Linux/macOS-specific shell environments or tools. The troubleshooting and workflow instructions are centered around the Azure portal and Cloud Shell, which are cross-platform, but command-line examples do not explicitly address Linux/macOS users or provide bash-specific guidance. There are no references to Linux-specific tools or patterns, and Windows/PowerShell is implicitly prioritized.
Recommendations
  • Explicitly mention that Azure CLI commands work on Linux/macOS and provide bash/zsh shell examples where relevant.
  • Add notes or examples for Linux/macOS users, such as how to install and use Azure CLI locally.
  • Clarify that PowerShell examples are for Windows/PowerShell Core and offer equivalent bash commands for Linux/macOS.
  • Consider listing CLI (cross-platform) examples before PowerShell (Windows-centric) examples.
  • Reference Linux/macOS environments in troubleshooting steps, such as proxy settings or shell configuration.
GitHub Create Pull Request
IoT Hub Azure IoT Hub IP filters ...ocs/blob/main/articles/iot-hub/iot-hub-ip-filtering.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for managing IP filter rules, but the PowerShell section is given equal prominence to the CLI, and there is no explicit mention of Linux or Bash-specific usage, nor are there any screenshots or instructions tailored for Linux users. The portal instructions are generic, but command-line examples may implicitly favor Windows users due to the inclusion of PowerShell and lack of Linux shell context.
Recommendations
  • Add explicit Bash/Linux shell examples for Azure CLI usage, including sample commands and expected outputs.
  • Clarify that Azure CLI commands work cross-platform (Windows, Linux, macOS) and provide any necessary notes about installation or environment differences.
  • If PowerShell is included, mention PowerShell Core and its availability on Linux/macOS, or provide equivalent Bash scripting examples.
  • Include screenshots or instructions that show the Azure CLI in use on Linux/macOS terminals.
  • Review and update any references to tools or workflows that are Windows-centric to ensure Linux parity.
GitHub Create Pull Request
IoT Hub Monitor Azure IoT Hub ...ure-docs/blob/main/articles/iot-hub/monitor-iot-hub.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a mild Windows bias. In the 'SDK version in IoT Hub logs' section, all concrete examples of the sdkVersion property use Windows platforms (e.g., Node.js on Windows, .NET on Windows), with no mention of Linux or macOS equivalents. Additionally, the only linked sample for reading events from Event Hubs is a .NET example, which is most commonly associated with Windows environments. There are no explicit Linux or cross-platform CLI examples, nor are Linux tools or shell commands mentioned anywhere. The documentation relies heavily on Azure portal screenshots and Kusto queries, which are platform-neutral, but the lack of Linux-specific examples or references may leave Linux users underserved.
Recommendations
  • Add examples of sdkVersion properties for devices running on Linux and macOS platforms (e.g., Node.js on Ubuntu, Python on Raspbian).
  • Include links to Event Hubs client samples for Python, Java, or Node.js, which are commonly used on Linux.
  • Where possible, provide Azure CLI or Bash command examples for monitoring and diagnostics setup, in addition to portal instructions.
  • Explicitly mention that the SDKs and monitoring tools are cross-platform, and provide guidance for Linux users where workflows differ.
  • Balance screenshots and instructions with text-based steps that can be performed on any OS, especially for automation scenarios.
GitHub Create Pull Request
IoT Hub Quickstart - Send telemetry to Azure IoT Hub (CLI) quickstart ...main/articles/iot-hub/quickstart-send-telemetry-cli.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation shows mild Windows bias by mentioning Windows Terminal as a primary local CLI option and referencing PowerShell throughout. PowerShell is presented as an alternative to Bash in the Cloud Shell environment selection, and special instructions are given for PowerShell command syntax. However, all CLI examples use Azure CLI commands, which are cross-platform and run equally on Linux, macOS, and Windows. No Linux-specific tools or patterns are mentioned, and Windows is referenced before Linux in some cases.
Recommendations
  • Mention Linux and macOS terminal applications (e.g., GNOME Terminal, iTerm2) alongside Windows Terminal when discussing local CLI usage.
  • Provide explicit confirmation that all CLI commands work identically on Linux, macOS, and Windows, and note any platform-specific caveats.
  • Include a brief section or note on installing and running Azure CLI on Linux and macOS, with links to official instructions.
  • When discussing Cloud Shell, clarify that Bash is the default and most common environment for Linux/macOS users, and PowerShell is more typical for Windows users.
  • If PowerShell-specific syntax is discussed, consider also mentioning any Bash-specific issues (e.g., quoting, escaping) to ensure parity.
GitHub Create Pull Request
IoT Hub X.509 certificates | Microsoft Docs ...b/main/articles/iot-hub/reference-x509-certificates.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation generally provides platform-neutral information about X.509 certificates, with a strong focus on standards and OpenSSL (Linux/macOS-friendly). However, in the 'Verify certificate manually after upload' section, the PowerShell script example is listed first, before the Bash script and OpenSSL instructions. This ordering, along with the explicit mention of PowerShell, subtly prioritizes Windows tooling and workflow, which may suggest a Windows-first bias. There are no Linux-specific tools (e.g., certtool, gnutls) mentioned, but Bash/OpenSSL examples are present and comprehensive.
Recommendations
  • List Bash and OpenSSL examples before PowerShell examples to avoid implicit prioritization of Windows workflows.
  • Explicitly state that all examples are cross-platform where applicable, and clarify which commands/scripts work on Linux, macOS, and Windows.
  • Consider adding Linux-specific certificate management tool references (e.g., certtool, gnutls) if relevant.
  • Ensure parity in script availability and documentation for both PowerShell and Bash, including links and troubleshooting notes for each platform.
GitHub Create Pull Request
IoT Hub X.509 certificates | Microsoft Docs ...b/main/articles/iot-hub/reference-x509-certificates.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Bash/OpenSSL and PowerShell examples for certificate generation and verification, but in the 'Verify certificate manually after upload' section, the PowerShell method is listed first, followed by Bash and OpenSSL. This ordering may subtly prioritize Windows users. Additionally, the explicit mention of a Microsoft-supplied PowerShell script as a primary method reinforces a Windows-centric approach, even though Linux alternatives are present.
Recommendations
  • Present Bash/OpenSSL and PowerShell methods in parallel or alternate their order in different sections to avoid implicit prioritization.
  • Explicitly state that both Windows and Linux workflows are equally supported and provide clear guidance for each.
  • Ensure that Linux/Bash/OpenSSL examples are as detailed and prominent as their Windows/PowerShell counterparts.
  • Consider adding a table or section comparing Windows and Linux workflows for certificate management, highlighting parity.
  • Avoid language that implies one platform is preferred or primary unless there is a technical reason.
GitHub Create Pull Request
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
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation page references Azure PowerShell as a configuration option for file upload before mentioning Linux-friendly alternatives like Azure CLI. This ordering and inclusion of PowerShell (primarily a Windows tool) suggests a Windows-first bias. No explicit Linux examples or tools are highlighted, and PowerShell is listed alongside CLI and portal without clarifying cross-platform support.
Recommendations
  • Explicitly mention that Azure CLI is cross-platform and suitable for Linux and macOS users.
  • List Azure CLI before Azure PowerShell when presenting configuration options to avoid Windows-first ordering.
  • Add examples or notes for configuring file upload using Linux shell commands or scripts.
  • Clarify that Azure PowerShell is available on Linux, or provide links to installation instructions for non-Windows platforms.
  • Ensure parity in examples and instructions for both Windows and Linux environments throughout the documentation.
GitHub Create Pull Request
← Previous Page 4 of 7 Next →