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 51-75 of 155 flagged pages
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 →
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 instructions and commands are provided specifically for Windows environments (Visual Studio, .cmd commands, .exe output), with only a brief mention that other environments are possible and a link to external documentation for Linux or cross-platform builds. There are no explicit Linux or macOS build/run instructions, and Windows tools (Visual Studio, Visual Studio Code) are referenced first and in detail.
Recommendations
- Add explicit Linux and macOS instructions for building and running the C SDK sample, including required dependencies (e.g., gcc/clang, make, cmake) and terminal commands.
- Provide example shell commands (bash) for cloning, building, and running the sample on Linux/macOS, alongside the Windows .cmd examples.
- Mention cross-platform editors (such as VS Code, which is already referenced) and provide parity in instructions for both Windows and Linux/macOS users.
- Where Windows-specific tools (Visual Studio, .exe) are mentioned, add equivalent alternatives for Linux/macOS (e.g., gcc, ./iothub_ll_telemetry_sample).
- Consider reordering or parallelizing instructions so that Windows and Linux/macOS steps are presented together, rather than Windows-first.
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 →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation shows some Windows bias, particularly in the .NET/C# section, where Windows (ETW and PowerShell scripts) is described first and in more detail, with Linux instructions following. The Windows approach uses specialized tools (ETW, PowerShell scripts), while the Linux approach uses a more generic tool (dotnet-trace). There is also a slight bias in the Java example, where the log file path uses a Windows-style path (c/temp/logs) without a Linux alternative.
Recommendations
- Present Linux and Windows instructions in parallel or in a consistent order (e.g., alphabetical or by usage share), rather than always listing Windows first.
- Ensure that Linux tooling is described with equal detail and prominence as Windows tools (e.g., provide troubleshooting tips, links, and context for dotnet-trace similar to ETW).
- Avoid using Windows-centric paths (e.g., 'c/temp/logs') in cross-platform examples; instead, provide both Windows and Linux path examples or use neutral paths.
- Where possible, mention cross-platform tools and approaches before platform-specific ones.
- If PowerShell scripts are provided for Windows, consider providing equivalent Bash scripts for Linux where feasible.
IoT Hub
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-hub/quickstart-bicep-route-messages.md
...in/articles/iot-hub/quickstart-bicep-route-messages.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a mild Windows bias by referencing Windows-centric tools and workflows, such as Visual Studio Code and C# SDK examples, without providing equivalent Linux or cross-platform alternatives. The only code sample for decoding messages refers to a C# method, and the monitoring tip suggests using the Visual Studio Code extension, which is more commonly associated with Windows development. There are no explicit Linux or cross-platform code examples for tasks like decoding messages or monitoring the IoT Hub, and the documentation does not mention Linux-specific tools or workflows.
Recommendations
- Provide code examples for decoding messages in cross-platform languages such as Python or Bash, in addition to the C# example.
- Mention and provide instructions for using cross-platform editors and tools (e.g., VS Code is cross-platform, but clarify this and suggest alternatives like Vim, nano, or CLI-based monitoring tools).
- Include Linux-specific instructions or tips for tasks such as downloading and viewing files, decoding base64/UTF-8 messages using command-line utilities (e.g., base64, iconv, cat).
- When referencing SDK samples, link to equivalent samples in other languages (e.g., Python, Node.js) that are popular on Linux.
- Explicitly state that all Azure CLI commands work on Linux, macOS, and Windows, and provide any OS-specific caveats if needed.
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 →
Detected Bias Types
Windows Tools
Powershell Heavy
Windows First
Summary
The documentation page demonstrates a mild Windows bias. While the main device management instructions are provided for both the Azure Portal (web-based, cross-platform) and Azure CLI (cross-platform), the 'Other tools' section highlights PowerShell commands and Visual Studio Code (which, while cross-platform, is often associated with Windows development) before mentioning the REST API. There are no explicit Linux-specific tools or examples, and PowerShell is called out as a management option without mentioning Bash or Linux-native scripting alternatives. No Linux-specific patterns or package managers are referenced, and there is no mention of Linux shell scripting for automation.
Recommendations
- Add explicit mention of Bash scripting or Linux shell automation as alternatives to PowerShell for device management, especially when using the Azure CLI.
- In the 'Other tools' section, balance the mention of PowerShell with references to Bash or shell scripting, and clarify that Azure CLI commands work natively on Linux and macOS.
- Provide example scripts or automation snippets in Bash alongside any PowerShell examples.
- When listing tools, avoid listing Windows-centric tools (like PowerShell) first, or group cross-platform tools together and clarify their OS compatibility.
- Consider including a note or section on managing IoT Hub devices from Linux environments, including package installation tips for the Azure CLI on Linux.
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 →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates subtle Windows bias, particularly in the section about assigning roles for Cosmos DB access. It explicitly mentions Azure PowerShell and Azure CLI as required tools for role assignment, listing PowerShell before CLI. There are no explicit Linux or cross-platform command examples, and the only code sample is in C#, a language more commonly associated with Windows development. No Linux-specific tools or shell examples are provided, and there is no mention of Bash or other cross-platform scripting environments.
Recommendations
- When referencing command-line tools, list Azure CLI before PowerShell, as CLI is cross-platform and more commonly used on Linux.
- Provide explicit Bash or shell command examples alongside PowerShell where relevant, especially for role assignments or scripting.
- Include code samples in languages popular on Linux (e.g., Python, Node.js) in addition to or instead of C#.
- Clarify that all management operations can be performed from Linux, macOS, or Windows, and provide links to cross-platform tool documentation.
- Avoid language or ordering that implies Windows-first workflows; ensure parity in tool and example coverage.
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 →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation page shows some Windows bias in the .NET/C# section: Windows/PowerShell/ETW instructions are presented before Linux/dotnet-trace instructions, and the Windows workflow is described in more detail, including specific PowerShell scripts and links to Windows-specific tools. There is also a focus on Event Tracing for Windows (ETW) and PowerShell, which are not cross-platform. Other language sections (Java, Python, Node.js, Embedded C) are generally OS-neutral or provide examples that work on both Windows and Linux.
Recommendations
- Present Linux and Windows instructions in parallel or in a more balanced order (e.g., 'On Windows' and 'On Linux' subsections, or a table).
- Ensure equal detail and prominence for Linux tooling (e.g., provide as much explanation for dotnet-trace as for ETW/PowerShell).
- Where possible, mention cross-platform tools first, or highlight them as preferred for portability.
- Add explicit notes about how to perform similar actions on macOS, if supported.
- Avoid assuming PowerShell or ETW are the default or primary mechanisms; clarify their OS specificity.
- Where Windows file paths or conventions are shown (e.g., in Java logging config), provide Linux equivalents or note differences.
IoT Hub
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-hub/iot-hub-bulk-identity-mgmt.md
...ob/main/articles/iot-hub/iot-hub-bulk-identity-mgmt.md
High Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation is heavily focused on C# and the .NET SDK, with all code samples in C#. There is an implicit Windows bias due to exclusive use of .NET tooling, references to NuGet, and lack of examples or guidance for Linux users or those using other languages/platforms (e.g., Python, Node.js, CLI, or Bash). There are no explicit PowerShell or Windows command-line examples, but the .NET/C# focus and absence of Linux/CLI alternatives create a Windows-centric experience.
Recommendations
- Provide equivalent examples using the Azure CLI and/or Azure PowerShell, which are cross-platform, to show how to perform import/export operations without C# code.
- Include code samples in other popular languages supported by the Azure IoT SDK (e.g., Python, Node.js) to broaden platform inclusivity.
- Add instructions for generating SAS tokens and managing blob storage using Bash scripts or CLI commands, not just C#.
- Mention how to install and use the required SDKs and tools on Linux and macOS, not just via NuGet.
- Reference cross-platform tools and patterns (such as VS Code, Docker, or containerized workflows) where appropriate.
- Explicitly state that the .NET SDK and code samples are cross-platform, and provide links or notes for Linux/macOS users.
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 →
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 mention or provide examples for Linux-specific tools or workflows. The order of methods places PowerShell before any Linux-native alternatives, and there are no explicit Linux/Bash examples or clarifications about cross-platform compatibility. This may give the impression of a Windows-centric approach.
Recommendations
- Explicitly state that Azure CLI is cross-platform and works on Linux, macOS, and Windows.
- Provide example commands for both Azure CLI (with Bash syntax) and PowerShell, making it clear which is suitable for Linux users.
- Consider listing Azure CLI before PowerShell in tables or lists, as CLI is more universal.
- Add a note or section clarifying that all features are accessible from Linux environments, and link to any relevant Linux setup guides.
- If possible, include screenshots or walkthroughs from a Linux terminal in tutorials.
IoT Hub
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-hub/iot-hub-query-avro-data.md
.../blob/main/articles/iot-hub/iot-hub-query-avro-data.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Visual Studio (a Windows-centric tool) for creating U-SQL projects, without mentioning or providing alternatives for Linux users. There are no Linux-specific instructions or examples for setting up or running the workflow, and the only development environment mentioned is Visual Studio. No cross-platform or command-line alternatives are suggested.
Recommendations
- Include instructions for creating and running U-SQL scripts using Azure Data Lake Tools for Visual Studio Code, which is available on Linux, or via the Azure Portal.
- Provide command-line examples using Azure CLI or PowerShell Core (which is cross-platform) for uploading DLLs and submitting U-SQL jobs.
- Explicitly mention cross-platform options for each step, especially for development environments and tooling.
- Add screenshots or walkthroughs for Linux/macOS users where applicable.
- Reference documentation or guides for setting up the required environment on Linux.
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 →
Detected Bias Types
Missing Linux Example
Windows Tools
Windows First
Summary
The documentation is heavily oriented toward Windows development, specifically using Visual Studio and .NET. All examples and setup instructions assume the use of Visual Studio (a Windows-centric IDE) and do not provide alternative instructions or examples for Linux users or those using cross-platform tools. There are no Linux or cross-platform code samples, nor are there instructions for using .NET Core/SDK on Linux, VS Code, or command-line alternatives. The only non-Windows-specific command is the OpenSSL example for certificate creation.
Recommendations
- Provide equivalent instructions for Linux users, such as using .NET SDK and VS Code or command-line tools instead of Visual Studio.
- Include code samples and project setup steps for .NET Core/SDK on Linux and macOS.
- Add instructions for installing the Azure IoT Hub SDK using the .NET CLI (dotnet add package) rather than only NuGet Package Manager in Visual Studio.
- Clarify that the .NET SDK and Azure IoT Hub client libraries are cross-platform and provide explicit Linux/macOS guidance.
- Consider including bash or shell commands for building and running the sample app on Linux.
- Ensure screenshots and UI steps are supplemented with command-line alternatives where possible.
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 →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation page is generally cross-platform, focusing on the Azure portal and Azure CLI, both of which are available on Windows, Linux, and macOS. However, there are subtle signs of Windows bias: PowerShell-specific tips are included, and Windows Terminal is mentioned as an example app for Cloud Shell. There are no Linux- or macOS-specific shell tips or examples, and no mention of Linux terminals or shell environments. The PowerShell escaping tip is repeated, but no equivalent bash/zsh guidance is provided.
Recommendations
- Add bash/zsh shell escaping tips alongside PowerShell tips, especially for JSON quoting and escaping.
- When mentioning terminal applications (e.g., Windows Terminal), also mention common Linux (e.g., GNOME Terminal, Konsole) and macOS (Terminal.app, iTerm2) terminals.
- Explicitly state that the Azure CLI commands work on Linux, macOS, and Windows, and provide example shell commands for both bash and PowerShell where quoting/escaping differs.
- If providing PowerShell-specific notes, provide equivalent notes for bash/zsh users.
- Consider including a short section or tip for Linux/macOS users regarding common pitfalls or differences in command-line usage.
IoT Hub
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-hub/quickstart-bicep-route-messages.md
...in/articles/iot-hub/quickstart-bicep-route-messages.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a subtle Windows bias by referencing Visual Studio Code (a Microsoft tool popular on Windows), providing code samples and tips that assume use of the Azure CLI (which is cross-platform but often associated with Windows), and offering a C#/.NET code sample for message decoding without mentioning Linux-native tools or alternatives. There are no explicit Linux or macOS-specific instructions or examples, and the only code-based decoding example is in C# (commonly used on Windows), with no mention of how to perform the same task using Linux command-line tools or scripts.
Recommendations
- Provide equivalent Linux/macOS command-line examples for tasks such as decoding base64/UTF-8 messages (e.g., using bash, base64, and iconv commands).
- Mention and link to cross-platform or Linux-native editors (such as VS Code Insiders on Linux, Vim, or nano) when suggesting tools for monitoring IoT Hub messages.
- Include a code snippet or command-line example for decoding the message file using common Linux tools (e.g., cat, base64, iconv) in addition to the C# example.
- Clarify that the Azure CLI is cross-platform and works on Linux/macOS, and provide any necessary installation or troubleshooting tips for those platforms.
- Balance references to Visual Studio Code with alternatives or explicitly state its availability on Linux/macOS.
IoT Hub
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-hub/migrate-hub-arm.md
...ure-docs/blob/main/articles/iot-hub/migrate-hub-arm.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation demonstrates a Windows-first bias in several ways: instructions for setting environment variables and running commands are presented with Windows examples first and in more detail, references to Windows-specific tools (such as Notepad and Visual Studio) are made without equivalent Linux alternatives, and command-line instructions for running the sample application are described primarily in the context of Windows command prompts. While Linux equivalents are sometimes mentioned, they are often secondary and less detailed. There is also a lack of Linux-specific troubleshooting or tool recommendations, and no mention of Linux-native editors or shells beyond a brief 'export' example.
Recommendations
- Present Linux and Windows instructions in parallel, or alternate which comes first to avoid implicit prioritization.
- Include Linux-native tool recommendations (e.g., gedit, nano, vim) alongside Notepad and Visual Studio.
- Provide explicit instructions for running the sample application in Linux shells (e.g., bash, zsh), including how to set environment variables and execute dotnet commands.
- Add troubleshooting tips for common Linux issues (e.g., file permissions, dependency installation).
- Reference cross-platform editors (e.g., VS Code) more prominently and clarify that all steps can be performed on Linux.
- Ensure screenshots and UI instructions are not Windows-centric, or provide Linux equivalents where possible.
- Where Visual Studio is mentioned, also mention Visual Studio Code or JetBrains Rider as cross-platform alternatives.
IoT Hub
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-hub/tutorial-message-enrichments.md
.../main/articles/iot-hub/tutorial-message-enrichments.md
High Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows Tools
Windows First
Summary
The documentation provides instructions for using the Azure portal and Azure CLI, which are cross-platform. However, the only code sample for simulating a device is a .NET console application (SimulatedDevice), which is Windows-centric by default and lacks explicit Linux instructions or alternatives. There are no examples using Linux-native tools (such as Python, Bash, or MQTT CLI clients), and the documentation assumes familiarity with Windows development patterns. The sample path and instructions (e.g., `/iot-hub/Tutorials/Routing/SimulatedDevice/` and editing `Program.cs`) are also more familiar to Windows/.NET users.
Recommendations
- Provide a Linux-native example for simulating device messages, such as using Python, Bash, or an MQTT CLI tool (e.g., mosquitto_pub).
- Explicitly mention that the .NET sample can be run on Linux using .NET Core, and provide installation instructions if needed.
- Include file path examples and instructions that are platform-agnostic or show both Windows and Linux path formats.
- Offer alternative code samples in other languages commonly used on Linux (e.g., Python, Node.js) for sending device messages.
- Clarify that the Azure CLI commands work on all platforms and, if any step is platform-specific, provide equivalent instructions for both Windows and Linux.
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 →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation references PowerShell and Visual Studio Code (VS Code) as alternative tools for managing device identities, both of which are commonly associated with Windows environments. PowerShell is mentioned explicitly, and VS Code is referenced with an Azure IoT Hub extension, which may be more familiar to Windows users. The 'Other tools' section lists PowerShell before REST API, which is platform-neutral. However, the main how-to instructions use the Azure CLI, which is cross-platform, and there are no explicit Windows-only command examples or screenshots. There are no Linux-specific tools or workflows mentioned, nor are there any Linux-first examples or troubleshooting tips.
Recommendations
- Add explicit mention and examples of using the Azure CLI on Linux/macOS, including any OS-specific considerations (e.g., installation, permissions, shell differences).
- If referencing PowerShell, clarify that PowerShell Core is cross-platform and provide Linux/macOS usage notes or examples.
- Include alternative Linux-native tools or scripts (e.g., Bash scripts, curl commands for REST API usage) where appropriate.
- Balance the order of tool mentions in the 'Other tools' section by listing REST API or CLI before PowerShell, or grouping them by platform neutrality.
- Consider adding troubleshooting or environment setup notes for Linux users, especially for certificate management and CLI usage.
IoT Hub
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-hub/horizontal-arm-route-messages.md
...main/articles/iot-hub/horizontal-arm-route-messages.md
High Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows Tools
Windows First
Summary
The documentation page demonstrates a Windows bias by referencing only Windows-based tools and workflows, such as Visual Studio Code and the .NET/C# SDK, without providing equivalent Linux or cross-platform alternatives. The code example for message decoding is given exclusively in C# and references a Windows-style file path. There are no explicit Linux or cross-platform code samples or instructions for viewing or decoding the stored messages, and the guidance for opening downloaded files assumes a Windows environment.
Recommendations
- Provide equivalent code samples for Linux users, such as Python or Bash scripts, for decoding and reading the stored messages.
- Reference cross-platform editors (e.g., VS Code, Vim, nano) and provide instructions for both Windows and Linux environments.
- When mentioning file paths or actions like 'double-click', include Linux alternatives (e.g., using cat, less, or xdg-open).
- Include explicit instructions for Linux users on how to download, locate, and open the files, and how to decode the messages using common Linux tools.
- If referencing SDKs, mention and link to cross-platform SDKs (e.g., Azure IoT SDK for Python or Node.js) alongside .NET/C#.
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 →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation demonstrates a Windows-first bias in the .NET/C# section by presenting Windows/PowerShell/ETW instructions before Linux/dotnet-trace equivalents. It also references Windows-specific tools (Event Tracing for Windows, PowerShell scripts) and provides more detailed, step-by-step instructions for Windows users. Linux instructions are present but appear after the Windows section, and the Windows approach is given more prominence.
Recommendations
- Present Linux and Windows instructions in parallel or in a unified table, rather than listing Windows first.
- Ensure both platforms receive equally detailed, step-by-step instructions and troubleshooting notes.
- Where possible, use cross-platform tools or highlight them first if available.
- Avoid referencing Windows-only tools (like ETW and PowerShell scripts) without offering equivalent Linux-native alternatives or context.
- Explicitly state platform support in each section and avoid implying Windows is the default or primary environment.
IoT Hub
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-hub/iot-hub-bulk-identity-mgmt.md
...ob/main/articles/iot-hub/iot-hub-bulk-identity-mgmt.md
High Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows Tools
Windows First
Summary
The documentation page demonstrates a bias toward Windows by exclusively providing C#/.NET code samples, referencing the Microsoft Azure IoT SDK for .NET, and assuming the use of Windows-centric development tools and workflows. There are no examples or guidance for Linux users, alternative SDKs (such as Python or Node.js), or cross-platform command-line usage. The instructions for obtaining connection strings and managing resources are tailored to the Azure Portal UI, which is more commonly used on Windows, and there is no mention of Azure CLI or Powershell alternatives for Linux/macOS users.
Recommendations
- Provide code samples using cross-platform SDKs, such as Python or Node.js, in addition to C#/.NET.
- Include instructions and examples for performing import/export operations using the Azure CLI, which is available on all platforms.
- Explicitly mention that the SDK and examples can be used on Linux and macOS, and provide setup instructions for those environments.
- Add guidance for obtaining connection strings and managing resources using command-line tools (Azure CLI, az commands) rather than only through the Azure Portal.
- Where possible, avoid referencing Windows-specific tools or workflows, or provide Linux/macOS equivalents alongside them.
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 →
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 instructions for building and running the Azure IoT C SDK are provided only for Windows (using Visual Studio, Windows command prompt, and .exe executables). There are no equivalent Linux or macOS build/run instructions, and Windows-specific tools and patterns (e.g., Visual Studio, .exe output) are mentioned exclusively or before any cross-platform alternatives.
Recommendations
- Provide parallel instructions for building and running the C SDK sample on Linux and macOS, including required dependencies (e.g., gcc/clang, make, cmake) and example shell commands.
- Mention and demonstrate use of cross-platform editors and tools (e.g., VS Code, nano, vim) alongside Windows-specific ones.
- Show Linux/macOS terminal commands (e.g., bash shell, ./iothub_ll_telemetry_sample) in addition to Windows command prompt examples.
- Clarify that the SDK and distributed tracing features are cross-platform, and link directly to Linux/macOS-specific build guides where appropriate.
- Avoid assuming Visual Studio or Windows as the default development environment; present all supported platforms equally.
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 →
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 there are no explicit Linux or Bash shell examples. The CLI examples are cross-platform, but there is no mention of Linux-specific considerations, nor are there any screenshots or instructions referencing Linux environments. The PowerShell section assumes familiarity with Windows tooling, and there are no alternative examples for Linux users who might use Bash scripting or other shell environments.
Recommendations
- Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and provide example shell prompts (e.g., $ for Bash) to reinforce cross-platform compatibility.
- Add a short Bash script example for retrieving and updating IP filters using Azure CLI, demonstrating piping and jq for JSON parsing if needed.
- Clarify that PowerShell examples are primarily for Windows users, and suggest alternatives for Linux users (e.g., Bash with Azure CLI).
- Include at least one screenshot or terminal snippet from a Linux environment to visually reinforce parity.
- If there are any platform-specific caveats (such as differences in CLI installation or authentication), mention them in a dedicated section.
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 →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation lists Azure CLI and Azure PowerShell as command-line methods for configuring message enrichments, with PowerShell (a Windows-centric tool) given equal prominence to Azure CLI. There are no explicit Linux/bash examples or mention of Linux-native tools. The ordering of methods (Portal, Azure CLI, Azure PowerShell) is neutral, but the inclusion of PowerShell without Linux/bash parity and the lack of Linux-specific guidance or examples suggests a subtle Windows bias.
Recommendations
- Add explicit bash/Linux shell examples for configuring message enrichments using Azure CLI.
- Clarify that Azure CLI is cross-platform and provide example commands for both Windows (cmd/PowerShell) and Linux/macOS (bash/zsh).
- If PowerShell is mentioned, also mention Linux-native shells to ensure parity.
- Consider reordering the command-line methods to list Azure CLI before PowerShell, as CLI is more cross-platform.
- Explicitly state that all features are available on Linux and macOS, not just Windows.
IoT Hub
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-hub/migrate-hub-arm.md
...ure-docs/blob/main/articles/iot-hub/migrate-hub-arm.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows bias in several ways: instructions for setting environment variables and running commands are presented with Windows examples first, and in greater detail. Steps for running the sample application reference Windows-specific tools (such as NotePad and Visual Studio) and workflows (like using the command prompt and .sln files), with only brief or secondary mention of Linux equivalents. The Linux instructions for setting environment variables are present but less emphasized, and there are no examples for running the sample on Linux terminals or using Linux-native editors/IDEs. The overall workflow assumes familiarity with Windows tools and patterns, and lacks parity in Linux-focused guidance.
Recommendations
- Present Linux and Windows instructions in parallel, or alternate which comes first in each section.
- Provide equivalent Linux command-line examples for running the sample application, including using bash/zsh and common Linux editors (e.g., nano, vim, gedit) instead of only Visual Studio/NotePad.
- Include instructions for running the sample in popular Linux IDEs (e.g., VS Code on Linux, JetBrains Rider) and clarify that .NET Core is cross-platform.
- Expand environment variable setup instructions for Linux, including how to persist variables in shell profiles.
- Avoid referencing Windows-only tools (like NotePad) without Linux alternatives.
- Add troubleshooting tips relevant to Linux environments (e.g., permissions, shell differences).
- Ensure screenshots and UI references are not Windows-centric, or provide Linux equivalents where applicable.
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 →
Detected Bias Types
Missing Linux Example
Windows Tools
Windows First
Summary
The documentation is heavily oriented toward Windows development, specifically using Visual Studio and .NET. All code examples and setup instructions assume a Windows environment, with no mention of Linux-compatible tools, editors, or workflows. There are no Linux or cross-platform code samples, and the only development environment referenced is Visual Studio, which is primarily a Windows tool.
Recommendations
- Add parallel instructions for Linux users, such as using VS Code or JetBrains Rider, and include relevant terminal commands.
- Provide .NET CLI commands for project creation, dependency installation, and running the app, which work cross-platform.
- Include code snippets and instructions for running the sample on Linux/macOS, including any required dependencies or environment setup.
- Mention and link to cross-platform SDKs and editors earlier in the prerequisites section.
- Where screenshots are used, consider including those from cross-platform editors (e.g., VS Code) or clarify that the steps are similar in other environments.
IoT Hub
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-hub/quickstart-bicep-route-messages.md
...in/articles/iot-hub/quickstart-bicep-route-messages.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a subtle Windows bias by referencing Visual Studio Code (a Microsoft tool popular on Windows), providing .NET/C# code samples, and suggesting the use of Windows-centric tools and workflows. There are no explicit Linux or cross-platform command-line examples for tasks like decoding messages, and the only code sample for message decoding is in C#. The instructions for downloading and opening files assume a GUI file explorer, which is more typical for Windows users, and there are no alternative instructions for Linux or macOS users.
Recommendations
- Include cross-platform or Linux-specific instructions for tasks such as decoding base64/UTF-8 messages (e.g., using Python or command-line tools like base64 and iconv).
- Provide alternative examples for downloading and opening files using command-line tools (e.g., wget, curl, cat, base64) suitable for Linux/macOS users.
- Reference code samples in other languages (such as Python or Node.js) in addition to C#/.NET, especially for common IoT SDK tasks.
- When suggesting tools like Visual Studio Code, mention that it is available cross-platform and provide alternatives (e.g., Vim, nano, or other editors) for Linux users.
- Explicitly state that all Azure CLI commands work on Linux, macOS, and Windows, and avoid language that assumes a Windows environment.
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 →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. While it primarily uses Azure CLI (which is cross-platform), several subtle cues and omissions indicate a Windows-centric approach: the use of Windows command prompt syntax (e.g., 'cmd/sh'), references to local command lines without clarifying cross-platform differences, and the exclusive use of .NET/C# for the simulated device sample. There are no explicit Linux or macOS-specific instructions, nor are there alternative code samples or troubleshooting notes for non-Windows environments. The tutorial assumes familiarity with Windows tools and patterns, and does not address potential differences in file paths, shell syntax, or package management on Linux/macOS.
Recommendations
- Explicitly state that Azure CLI commands work on Windows, Linux, and macOS, and provide example shell commands for both Bash (Linux/macOS) and PowerShell/Command Prompt (Windows) where syntax differs.
- Include a note or section for Linux/macOS users regarding any environment-specific prerequisites or differences (e.g., file paths, shell commands, package installation).
- Offer alternative device simulation samples in Python or Node.js, which are more commonly used on Linux/macOS, or at least link to such samples.
- Clarify in the 'Run the simulated device app' section how to build and run the .NET sample on Linux/macOS, including any required dependencies or troubleshooting tips.
- Where screenshots or navigation steps are shown, note any UI differences that may appear on non-Windows platforms (if applicable).
- Avoid using 'cmd/sh' as a command block language; instead, specify 'bash' or 'powershell' as appropriate, or provide both variants.