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 26-50 of 155 flagged pages
IoT Hub https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-hub/manage-device-twins.md ...docs/blob/main/articles/iot-hub/manage-device-twins.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page demonstrates mild Windows bias. It references Windows Terminal as an example application for running Azure Cloud Shell, and provides PowerShell-specific tips for escaping double quotes, without offering equivalent guidance for Linux shells (e.g., Bash). The mention of PowerShell appears twice in CLI usage tips, and Windows Terminal is the only specific terminal application named. There are no explicit Linux/Bash examples or shell-specific notes for Linux users.
Recommendations
  • Add equivalent shell escaping tips for Bash and other Linux shells (e.g., explain single vs double quotes, escaping strategies).
  • Mention common Linux terminal applications (e.g., GNOME Terminal, Konsole) alongside Windows Terminal when discussing Cloud Shell.
  • Where PowerShell-specific instructions are given, provide parallel Bash/Linux instructions.
  • Explicitly state that Azure CLI commands work on Linux, macOS, and Windows, and link to platform-specific installation guides.
  • Consider adding a short section or note for Linux/macOS users, highlighting any differences in command usage or environment setup.
GitHub Create Pull Request
IoT Hub https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-hub/tutorial-x509-test-certs.md ...blob/main/articles/iot-hub/tutorial-x509-test-certs.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation shows a moderate Windows bias. Windows-specific instructions and tooling (e.g., Git Bash, winpty) are mentioned first or exclusively in several places. The prerequisites and OpenSSL installation guidance are Windows-centric, with Linux alternatives mentioned only as secondary. Command examples are often presented with Windows instructions first, and the use of 'winpty' is specific to Windows environments. There is also an emphasis on using Git Bash, which is primarily a Windows solution for Unix-like tooling.
Recommendations
  • Present Linux and Windows instructions in parallel, or alternate which comes first to avoid implicit prioritization.
  • Provide clear, native Linux installation instructions for OpenSSL and Git, rather than focusing on Git Bash (which is not standard on Linux).
  • Remove or minimize Windows-specific tooling references (e.g., winpty, Git Bash) in favor of cross-platform or native solutions.
  • Explicitly mention macOS support and provide examples where appropriate.
  • Ensure that all scripts and commands are tested and documented for both Windows (PowerShell, CMD, Git Bash) and Linux (bash, sh), and clarify any platform-specific differences.
  • Add troubleshooting notes for common Linux issues (e.g., file permissions, environment variables) to match the detail given for Windows.
GitHub Create Pull Request
IoT Hub https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-hub/tutorial-use-metrics-and-diags.md ...ain/articles/iot-hub/tutorial-use-metrics-and-diags.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. While the Azure CLI is cross-platform and used throughout, examples and instructions for running the simulated device app are focused on .NET/C# and use Windows-centric terminology (e.g., 'cmd/sh', references to local terminal windows, and screenshots that appear to be from Windows environments). There is mention of PowerShell as an option for resource creation, but no Linux shell or bash-specific instructions or examples are provided. There are no explicit Linux or macOS instructions for running the sample app, installing dependencies, or troubleshooting platform-specific issues. The documentation does not mention Linux tools or patterns, nor does it provide parity for Linux users in terms of screenshots or step-by-step guidance.
Recommendations
  • Add explicit instructions and examples for Linux and macOS users, including bash shell commands and screenshots from those environments.
  • Clarify that Azure CLI commands work on all platforms and provide notes on any platform-specific differences (e.g., environment variable syntax).
  • Include troubleshooting tips for common Linux/macOS issues (such as file permissions, dependency installation, or .NET SDK setup).
  • Provide alternative instructions for running the simulated device app on Linux/macOS, including terminal commands and expected output.
  • Balance screenshots to include both Windows and Linux environments, or use neutral screenshots where possible.
  • Mention Linux equivalents when referencing PowerShell, and avoid implying Windows as the default environment.
GitHub Create Pull Request
IoT Hub https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-hub/how-to-collect-device-logs.md ...ob/main/articles/iot-hub/how-to-collect-device-logs.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page shows 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 the Linux equivalent. The Windows instructions use dedicated scripts and reference ETW, while the Linux instructions use a generic dotnet tool. The ordering and depth of the Windows example may suggest Windows as the primary platform. Other language sections are generally cross-platform or platform-neutral.
Recommendations
  • Present Linux and Windows instructions in parallel or with equal prominence, rather than Windows first.
  • Provide more detailed Linux instructions, including troubleshooting tips and equivalent provider lists.
  • If using PowerShell scripts for Windows, consider providing Bash scripts or automation for Linux.
  • Explicitly state platform parity and note any limitations or differences between Windows and Linux tracing.
  • Ensure that examples (such as file paths in Java) use platform-neutral or platform-specific alternatives for both Windows and Linux.
GitHub Create Pull Request
IoT Hub https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-hub/create-hub.md ...cs/azure-docs/blob/main/articles/iot-hub/create-hub.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation provides parity between Azure Portal, Azure CLI, and Azure PowerShell for all major tasks. However, there is a notable emphasis on Azure PowerShell, which is primarily a Windows tool, and PowerShell examples are given equal prominence to CLI examples. The documentation refers to installing Azure PowerShell and uses PowerShell-specific commands, which are less common on Linux. There are no explicit Linux shell (bash) examples, nor are Linux-specific tools or patterns mentioned. The CLI examples are cross-platform, but PowerShell is presented as a first-class option, which may suggest a Windows bias.
Recommendations
  • Clarify that Azure PowerShell is available on Linux and macOS, or note its Windows origins.
  • Add bash shell examples for common tasks, especially for scripting scenarios.
  • Highlight cross-platform compatibility of Azure CLI and provide links to Linux-specific installation guides.
  • Consider mentioning Linux-native tools (e.g., curl for REST API calls) in the 'Other tools' section.
  • If PowerShell is shown, also show equivalent bash or shell script snippets for Linux users.
GitHub Create Pull Request
IoT Hub https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-hub/how-to-file-upload.md ...-docs/blob/main/articles/iot-hub/how-to-file-upload.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page references Azure PowerShell as a configuration option alongside Azure CLI and Azure Portal, but does not mention Linux-specific tools or provide explicit Linux examples. The ordering of configuration options lists PowerShell before CLI, which may suggest a Windows-first bias. There are no explicit Linux shell (bash) or cross-platform command examples, and the SDK samples are referenced but not shown, so their platform parity cannot be assessed.
Recommendations
  • Explicitly mention that Azure CLI and Azure PowerShell are available on both Windows and Linux, and provide installation instructions for both platforms.
  • Include bash or shell script examples for configuring file upload, especially for Linux users.
  • When listing configuration options, alternate or randomize the order, or explicitly state cross-platform compatibility.
  • Add a section or note highlighting Linux usage scenarios, such as running SDK samples on Linux devices.
  • Ensure referenced SDK samples include instructions for both Windows and Linux environments.
GitHub Create Pull Request
IoT Hub https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-hub/iot-hub-devguide-endpoints.md ...ob/main/articles/iot-hub/iot-hub-devguide-endpoints.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 in several ways. Role assignment for Cosmos DB is described as only possible via Azure CLI or Azure PowerShell, with no mention of Bash or cross-platform shell usage. The only code example provided is in C#, a language most commonly used on Windows, and there are no Linux-specific or cross-platform shell examples for tasks such as listing blobs. The documentation refers to the Azure portal and PowerShell before mentioning CLI, and does not provide parity for Linux users in terms of command-line instructions or tools.
Recommendations
  • Include Bash and cross-platform Azure CLI examples for role assignment and blob listing, alongside PowerShell.
  • Provide code samples in languages commonly used on Linux (e.g., Python, Node.js) for SDK and API usage.
  • Explicitly mention that Azure CLI is cross-platform and provide instructions for both Windows and Linux environments.
  • Avoid referencing Windows tools (PowerShell, C#) exclusively or before Linux equivalents; present both options side by side.
  • Add notes or sections clarifying Linux compatibility for all described procedures.
GitHub Create Pull Request
IoT Hub https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-hub/iot-hub-distributed-tracing.md ...b/main/articles/iot-hub/iot-hub-distributed-tracing.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 in several areas: build and run instructions for the sample application are provided only for Windows (Visual Studio, .exe execution), with Linux equivalents relegated to a brief link; Windows-specific tools (Visual Studio, command prompt) are referenced exclusively; and step-by-step examples prioritize Windows workflows, omitting parallel Linux instructions. There are no explicit PowerShell examples, but the overall guidance and screenshots focus on Windows environments.
Recommendations
  • Provide explicit Linux build and run instructions, including commands for gcc/clang, make, and running the binary (e.g., ./iothub_ll_telemetry_sample) on Linux/macOS.
  • Include examples using Linux tools and editors (e.g., VS Code on Linux, nano/vim) alongside Visual Studio.
  • Add screenshots and step-by-step guidance for configuring distributed tracing and device twins using the Azure CLI and/or on Linux.
  • Ensure all code snippets and shell commands have both Windows (cmd/PowerShell) and Linux (bash) versions.
  • Reference cross-platform SDK installation and troubleshooting steps, not just Visual Studio-specific issues.
GitHub Create Pull Request
IoT Hub https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-hub/iot-hub-device-registry-setup.md ...main/articles/iot-hub/iot-hub-device-registry-setup.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 option for deployment, which is labeled as 'Windows only', while not providing an equivalent Bash or shell script for Linux/macOS users. The deployment method table lists PowerShell before mentioning the Azure CLI, and PowerShell is presented as a primary automation tool. There are no Linux-specific scripting examples or references to Linux-native tools. The prerequisites and instructions focus on Azure CLI, which is cross-platform, but the scripting automation is Windows-centric.
Recommendations
  • Provide a Bash or shell script example for Linux/macOS users alongside the PowerShell script.
  • Clearly indicate cross-platform options and parity in deployment automation (e.g., offer both PowerShell and Bash scripts).
  • Avoid labeling PowerShell as the only scripting option; mention alternatives for Linux and macOS.
  • Ensure that any references to tools or automation scripts include Linux equivalents or instructions.
  • Consider reordering the deployment method table to list cross-platform options first, or present them in parallel.
GitHub Create Pull Request
IoT Hub https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-hub/iot-hub-message-enrichments-overview.md ...ticles/iot-hub/iot-hub-message-enrichments-overview.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation lists Azure PowerShell as a primary method for configuring message enrichments, alongside Azure CLI and Portal, but does not provide any Linux-specific examples or mention Linux shell commands. The order of methods places PowerShell before any Linux-native alternatives, and there is no explicit guidance for Linux users. This may lead to a perception that Windows environments are preferred or better supported.
Recommendations
  • Explicitly mention that Azure CLI is cross-platform and works on Linux, macOS, and Windows.
  • Provide example commands for both Azure CLI (bash/zsh) and PowerShell, clarifying which platforms they are suitable for.
  • List Azure CLI before Azure PowerShell in tables and examples to avoid Windows-first bias.
  • Add a note or section for Linux users, including installation and usage tips for Azure CLI.
  • Ensure that any referenced tutorials include Linux command-line examples where applicable.
GitHub Create Pull Request
IoT Hub https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-hub/iot-hub-public-network-access.md ...main/articles/iot-hub/iot-hub-public-network-access.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation provides command-line examples for both Azure CLI and Azure PowerShell, but the PowerShell example is given immediately after the CLI example without any mention of Linux-specific shells or tools. There are no explicit Linux or bash examples, nor is there any mention of Linux-specific troubleshooting or patterns. The documentation assumes use of the Azure portal and Cloud Shell, which are cross-platform, but command-line instructions lean toward Windows/PowerShell usage and do not clarify Linux parity.
Recommendations
  • Add explicit bash or Linux shell examples alongside Azure CLI and PowerShell commands.
  • Clarify that Azure CLI commands work on Linux, macOS, and Windows, and provide sample bash usage.
  • Include troubleshooting steps or notes relevant to Linux environments (e.g., common proxy issues, file permissions).
  • Avoid listing PowerShell examples immediately after CLI examples without also providing bash equivalents, or clarify platform applicability.
  • Mention that Azure Cloud Shell is available for both bash and PowerShell, and show how to select the shell.
GitHub Create Pull Request
IoT Hub https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-hub/iot-hub-device-registry-setup.md ...main/articles/iot-hub/iot-hub-device-registry-setup.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits Windows bias by explicitly mentioning PowerShell as a deployment method and labeling it as 'Windows only', while not providing an equivalent Linux shell script example or guidance. The deployment method table lists PowerShell before any Linux alternatives, and there is no mention of Bash or Linux-native scripting for automation. The focus on PowerShell and lack of Linux-specific instructions or parity in scripting options may disadvantage Linux users.
Recommendations
  • Add a Bash or shell script example for Linux users alongside the PowerShell script.
  • Clarify that Azure CLI is cross-platform and provide explicit instructions for Linux and macOS environments.
  • Reorder the deployment method table to list cross-platform options first, or present them in parallel.
  • Include troubleshooting notes or environment setup steps for Linux and macOS users.
  • Ensure that all automation and scripting examples have Linux equivalents, not just PowerShell.
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-08 00:53
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 Windows tools (Visual Studio), .NET, and workflows typical of Windows environments. There are no Linux-specific instructions, nor are alternative Linux development tools or SDKs mentioned. The steps and screenshots assume the user is on Windows, and there is no parity for Linux users wanting to follow the same workflow.
Recommendations
  • Add equivalent instructions for Linux users, such as using VS Code or JetBrains Rider, and provide command-line steps for .NET development on Linux.
  • Include examples of installing the Azure IoT Hub SDK using the dotnet CLI, which works cross-platform.
  • Provide screenshots or terminal output for Linux environments.
  • Mention and link to Linux-specific quickstarts or guides where relevant.
  • Clarify that the .NET SDK and development can be performed on Linux and macOS, not just Windows.
  • Add a section or callout for Linux prerequisites (e.g., installing .NET SDK, using terminal, etc.).
GitHub Create Pull Request
IoT Hub https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-hub/iot-hub-devguide-endpoints.md ...ob/main/articles/iot-hub/iot-hub-devguide-endpoints.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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 the section about assigning roles for Cosmos DB authentication, where it recommends using Azure CLI or Azure PowerShell and notes that the Azure portal does not support this operation. The code example for listing blobs is in C#, a language most commonly associated with Windows development, and there are no Linux-specific or cross-platform shell examples (such as Bash or Python). Windows tools and patterns (PowerShell, C#) are mentioned, while Linux equivalents are absent. The documentation does not provide parity for Linux users in terms of example commands or tooling.
Recommendations
  • Include Bash and/or Python examples for blob listing and other operations, alongside C#.
  • Explicitly mention that Azure CLI is cross-platform and provide example commands for Linux/macOS users.
  • Add instructions for assigning roles to managed identities using Azure CLI on Linux/macOS, not just PowerShell.
  • Where code samples are provided, offer alternatives in languages popular on Linux (e.g., Python, Node.js).
  • Avoid implying that Windows tools are the primary or only way to perform management tasks; present cross-platform options first or equally.
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-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation page demonstrates a mild Windows bias by listing PowerShell commands and Visual Studio Code (a Microsoft tool) as primary alternatives for managing device identities, with PowerShell mentioned first among 'other tools.' There are no explicit Linux-specific tools or examples (such as Bash scripts or Linux-native utilities) provided. However, the main procedural examples use Azure CLI, which is cross-platform, and the Azure portal, which is web-based, so the bias is limited to the 'Other tools' section and the lack of Linux parity in alternative tool recommendations.
Recommendations
  • Include Linux-native alternatives in the 'Other tools' section, such as Bash scripting examples or references to Linux shell utilities.
  • Add examples or links for using the REST API with curl or wget, demonstrating device management from a Linux shell.
  • Mention that Azure CLI is cross-platform and works on Linux, macOS, and Windows.
  • If PowerShell is referenced, clarify that PowerShell Core is available on Linux and macOS, or provide equivalent Bash examples.
  • Consider listing non-Windows tools before or alongside Windows-specific tools to avoid 'windows_first' ordering.
GitHub Create Pull Request
IoT Hub https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-hub/how-to-file-upload.md ...-docs/blob/main/articles/iot-hub/how-to-file-upload.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page references Windows-specific tools (Azure PowerShell) and lists them before Linux-friendly alternatives (Azure CLI). There are no explicit Linux examples or mentions of Linux-specific patterns for configuring file upload, and the prerequisites section gives equal weight to Azure portal, CLI, and PowerShell, but PowerShell is a Windows-centric tool. The SDK samples are referenced but not shown, so it's unclear if they include Linux usage or examples.
Recommendations
  • Explicitly mention Linux compatibility for all steps, especially for configuring file upload.
  • Prioritize cross-platform tools (e.g., Azure CLI) before Windows-specific tools (e.g., PowerShell) in instructions and links.
  • Add Linux-specific examples or notes, such as using Bash scripts or Linux shell commands for configuration.
  • Clarify that the SDK samples work on Linux and provide links or instructions for running them on Linux.
  • Where PowerShell is mentioned, also mention alternatives for Linux users (e.g., Bash, CLI).
GitHub Create Pull Request
IoT Hub https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-hub/how-to-routing-arm.md ...-docs/blob/main/articles/iot-hub/how-to-routing-arm.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation provides deployment instructions using both Azure CLI and PowerShell, but PowerShell is a Windows-specific tool and is presented alongside Azure CLI in all deployment sections. File path examples use backslashes (e.g., "my\path\to\template.json"), which are Windows conventions. There are no explicit Linux shell examples (e.g., Bash), nor are Linux-specific instructions or notes provided. The documentation does not mention Linux tools or patterns, and does not address cross-platform differences in file paths or shell usage.
Recommendations
  • Add explicit Bash/Linux shell examples for deployment, using forward slashes in file paths (e.g., "my/path/to/template.json").
  • Clarify that Azure CLI commands work on Linux, macOS, and Windows, and provide platform-specific notes where relevant.
  • Reorder examples to present Azure CLI (cross-platform) before PowerShell, or provide CLI-only instructions for parity.
  • Include a note about file path differences between Windows and Linux/macOS.
  • Avoid using Windows-specific conventions (such as backslashes in file paths) in generic examples, or provide both formats.
GitHub Create Pull Request
IoT Hub https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-hub/how-to-collect-device-logs.md ...ob/main/articles/iot-hub/how-to-collect-device-logs.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation for collecting debug logs in the C#/.NET SDK section presents Windows-specific instructions (ETW, PowerShell scripts) before Linux alternatives, with more detail and emphasis on Windows tools. The Windows method uses dedicated scripts and references ETW, while the Linux method is described as an alternative using dotnet-trace, with less context and no parity in scripting. Other language sections are generally OS-neutral, but the C#/.NET section demonstrates a clear Windows-first and Windows-tool bias.
Recommendations
  • Present Linux and Windows instructions in parallel or with equal prominence, rather than Windows-first.
  • Provide Linux shell script equivalents for the PowerShell scripts used on Windows, or reference community tools/scripts for Linux.
  • Expand the Linux section to include troubleshooting tips, provider file usage, and trace analysis steps similar to the Windows section.
  • Clarify that both Windows and Linux are fully supported for trace collection, and avoid implying Windows is the primary platform.
  • Where possible, use cross-platform tools or document their usage equally for both OSes.
GitHub Create Pull Request
IoT Hub https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-hub/manage-device-twins.md ...docs/blob/main/articles/iot-hub/manage-device-twins.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page displays mild Windows bias. PowerShell is specifically mentioned in tips for escaping quotes, but there is no equivalent guidance for Bash or Linux shells. The Azure Cloud Shell is described as usable in 'Windows Terminal' before mentioning browser/app, and there are no explicit Linux shell examples or troubleshooting notes. All CLI examples are generic, but tips and tool mentions lean toward Windows and PowerShell.
Recommendations
  • Add equivalent tips for Bash/Linux shells, such as how to escape quotes in Bash (e.g., using single quotes or proper escaping).
  • Mention Linux terminal applications (e.g., GNOME Terminal, Konsole) alongside Windows Terminal when describing Cloud Shell usage.
  • Include troubleshooting notes for common issues in Bash/Linux shells, such as handling JSON and escaping.
  • Explicitly state that all Azure CLI commands work on Linux, macOS, and Windows, and provide example commands for Bash where quoting/escaping differs.
  • Avoid mentioning Windows tools or patterns first; use neutral phrasing or alternate between platforms.
GitHub Create Pull Request
IoT Hub https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-hub/iot-hub-message-enrichments-overview.md ...ticles/iot-hub/iot-hub-message-enrichments-overview.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation lists Azure PowerShell as a primary method for configuring message enrichments, alongside Azure CLI and Portal, but does not provide any Linux-specific examples or mention Linux shell commands. PowerShell is a Windows-centric tool, and its inclusion without equivalent Linux/Bash examples suggests a Windows bias. The ordering also places PowerShell before any Linux-native alternatives, and there is no mention of Linux-specific usage patterns or troubleshooting.
Recommendations
  • Add explicit Bash/Linux shell 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).
  • Consider reordering the configuration methods to list cross-platform tools (Portal, CLI) before Windows-specific tools (PowerShell).
  • Include troubleshooting steps or notes relevant to Linux environments, such as authentication or environment setup for Azure CLI.
  • Where PowerShell is mentioned, clarify its availability on Linux, or provide alternative Linux-native scripting examples.
GitHub Create Pull Request
IoT Hub https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-hub/iot-hub-distributed-tracing.md ...b/main/articles/iot-hub/iot-hub-distributed-tracing.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exhibits a Windows bias in several ways. The sample application build instructions are detailed only for Windows, specifically referencing Visual Studio and Windows command prompts. There are no explicit Linux or macOS build/run examples, and Windows tools (Visual Studio, MSVC) are mentioned exclusively or before any cross-platform alternatives. While there are links to general compilation instructions for other platforms, the step-by-step guidance and troubleshooting are Windows-centric.
Recommendations
  • Add explicit Linux and macOS build instructions, including required packages (e.g., gcc, clang, make, cmake) and example commands for cloning, building, and running the sample application.
  • Provide troubleshooting tips for common Linux/macOS build errors (e.g., missing dependencies, permissions).
  • Mention cross-platform editors (e.g., VS Code, Vim, Emacs) alongside Visual Studio, and clarify that the sample can be built and run on non-Windows environments.
  • Include example shell commands (bash/zsh) for Linux/macOS users, and show how to run the sample binary on those platforms.
  • Ensure that any references to Windows-specific tools (e.g., Visual Studio command prompt) are paired with equivalent instructions for other operating systems.
GitHub Create Pull Request
IoT Hub https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-hub/tutorial-use-metrics-and-diags.md ...ain/articles/iot-hub/tutorial-use-metrics-and-diags.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. While the Azure CLI is used for resource setup (which is cross-platform), the tutorial's code and instructions focus exclusively on .NET/C# and reference Windows-centric development patterns. The simulated device app is a C# console application, and instructions for running it use 'dotnet' commands but do not mention Linux-specific considerations (such as permissions, mono, or shell differences). There are no examples or screenshots showing Linux terminals, nor any mention of alternative Linux tools or shell environments. PowerShell is mentioned as an option for resource creation, but no Bash or Linux shell scripts are provided. The documentation assumes familiarity with Windows development environments and does not provide parity for Linux users.
Recommendations
  • Add explicit instructions and examples for running the simulated device app on Linux, including any required dependencies or environment setup.
  • Include screenshots or terminal examples from Linux environments (e.g., Ubuntu, bash shell) alongside Windows examples.
  • Mention Linux-specific considerations for .NET Core (such as permissions, package managers, or troubleshooting common Linux issues).
  • Provide Bash shell script equivalents for resource setup, or clarify that Azure CLI commands work identically on Linux and macOS.
  • Reference Linux tools and patterns (such as using 'chmod', 'nano', or 'vi' for editing files) where appropriate.
  • Clarify that the tutorial is cross-platform and highlight any steps that differ between Windows and Linux.
GitHub Create Pull Request
IoT Hub https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-hub/tutorial-x509-test-certs.md ...blob/main/articles/iot-hub/tutorial-x509-test-certs.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation exhibits 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 OpenSSL installation guidance are Windows-centric, with Git Bash recommended as the primary shell and OpenSSL access method on Windows. PowerShell scripts are referenced before Bash scripts. In command examples, Windows tabs and winpty usage are presented before Linux equivalents, and the overall workflow assumes a Windows environment (e.g., Git Bash as the shell, OpenSSL bundled with Git for Windows). Linux instructions are present, but often secondary.
Recommendations
  • Present Linux and Windows instructions with equal prominence, alternating which is shown first or using a neutral order.
  • Add explicit instructions for installing OpenSSL on Linux distributions (e.g., apt, yum, dnf commands) and clarify that OpenSSL is typically pre-installed or easily available on Linux.
  • Reference Bash scripts before or alongside PowerShell scripts, and clarify their applicability to both platforms.
  • Avoid assuming Git Bash as the default shell for all users; suggest native Linux terminals and macOS Terminal where appropriate.
  • Where winpty is used for Windows, explain its purpose and provide alternatives for Linux/macOS users.
  • Include troubleshooting notes for Linux-specific issues (e.g., file permissions, SELinux/AppArmor, environment variables).
  • Ensure screenshots and UI instructions are platform-neutral or provide both Windows and Linux/macOS variants.
GitHub Create Pull Request
IoT Hub https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-hub/iot-hub-devguide-endpoints.md ...ob/main/articles/iot-hub/iot-hub-devguide-endpoints.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Missing Linux Example 🔧 Windows Tools Windows First
Summary
The documentation page demonstrates subtle Windows bias. Code examples are given in C# (commonly associated with Windows development), and there are no Linux-specific or cross-platform command-line examples (such as Bash, curl, or Python). The only instructions for role assignment reference Azure CLI and Azure PowerShell, but PowerShell is mentioned first, and there is no explicit mention of Bash or Linux shell equivalents. The documentation does not provide parity for Linux users in terms of examples or tooling references.
Recommendations
  • Provide code examples in cross-platform languages such as Python or Node.js, or include Bash/curl command-line snippets alongside C#.
  • When referencing Azure CLI, clarify that it is cross-platform and provide explicit Bash/Linux shell usage examples.
  • Avoid listing PowerShell before CLI or at least mention both equally, with examples for each.
  • Include explicit instructions or notes for Linux/macOS users where relevant, such as file system paths or shell commands.
  • Where SDKs or APIs are referenced, link to language-agnostic or multi-language documentation.
GitHub Create Pull Request
IoT Hub https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-hub/iot-hub-ip-filtering.md ...ocs/blob/main/articles/iot-hub/iot-hub-ip-filtering.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
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 managing IP filters, but the PowerShell section is given equal prominence to the CLI, and no explicit Linux or cross-platform shell examples (such as Bash or curl for REST) are provided. The UI instructions reference 'your computer's IP address' without clarifying platform differences, and screenshots are from the Azure Portal, which is platform-agnostic. However, the scripting examples are limited to Windows-centric tools (PowerShell) and the Azure CLI (which is cross-platform but not shown in a Linux-specific context), with no mention of Linux-native tools or workflows.
Recommendations
  • Add explicit Bash or shell examples for Linux users, especially for REST API usage (e.g., using curl).
  • Clarify that Azure CLI commands work identically on Linux, macOS, and Windows, and consider showing CLI output in a Linux terminal context.
  • If possible, provide examples using common Linux text processing tools (jq, grep) when parsing JSON output.
  • Mention that PowerShell Core is cross-platform, but also offer native Linux alternatives for users who may not use PowerShell.
  • Ensure that references to 'your computer's IP address' include notes for how to find this on both Windows and Linux/macOS.
GitHub Create Pull Request
← Previous Page 2 of 7 Next →