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 126-150 of 155 flagged pages
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
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and PowerShell examples for deploying Resource Manager templates, but PowerShell is given equal prominence to CLI, and Windows-style file paths (e.g., my\path\to\template.json) are used in examples. There are no explicit Linux shell or Bash-specific examples, and PowerShell is highlighted as a primary method alongside CLI, which may indicate a slight Windows bias. However, the use of Azure CLI, which is cross-platform, helps mitigate this bias.
Recommendations
- Use POSIX-style (Linux/macOS) file paths (e.g., my/path/to/template.json) in CLI examples, or provide both Windows and Linux path variants.
- Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and provide Bash shell examples where appropriate.
- If PowerShell is shown, consider also showing Bash or sh equivalents for common tasks, especially for scripting or automation.
- Clarify in the prerequisites or deployment sections that all steps can be performed on Linux, macOS, or Windows, and link to platform-specific setup guides if needed.
- Where file uploads or downloads are discussed (e.g., in Azure Cloud Shell), mention any differences in file navigation or commands between Windows and Linux environments.
Create Pull Request
IoT Hub
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-hub/iot-hub-devguide-file-upload.md
.../main/articles/iot-hub/iot-hub-devguide-file-upload.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation references Windows-specific tools (PowerShell) alongside cross-platform options (Azure CLI and portal), but lists PowerShell before mentioning management APIs. There are no explicit Linux or Bash examples, and no mention of Linux-specific tools or shell environments. The documentation does not provide parity in example commands or tooling guidance for Linux users, potentially making it less approachable for non-Windows users.
Recommendations
- When listing configuration options, mention cross-platform tools (Azure CLI) before Windows-specific tools (PowerShell), or group them together without preference.
- Explicitly state that Azure CLI and the portal are cross-platform and suitable for Linux, macOS, and Windows.
- Provide example commands for both Azure CLI (Bash/shell) and PowerShell where appropriate.
- Include a note or section highlighting Linux compatibility and any Linux-specific considerations.
- Ensure parity in code snippets and walkthroughs for both Windows and Linux environments.
IoT Hub
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-hub/iot-hub-live-data-visualization-in-web-apps.md
...iot-hub/iot-hub-live-data-visualization-in-web-apps.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation assumes a Windows development environment throughout, with all command-line examples (e.g., setting environment variables, running commands) shown only in Windows CMD syntax. There are no explicit Linux or cross-platform shell equivalents provided for key steps such as setting environment variables or running the app. The instructions and screenshots reference Windows tools and patterns first, and do not offer parity for Linux or macOS users.
Recommendations
- For every command-line example (e.g., setting environment variables, running npm commands, git commands), provide both Windows CMD and Linux/macOS (bash/zsh) equivalents, clearly labeled.
- In the 'Configure environment variables' section, add Linux/macOS export commands (e.g., export IotHubConnectionString=...) alongside the Windows set commands.
- When referencing file navigation or editors, use neutral language (e.g., 'your preferred editor') and avoid screenshots or instructions that are Windows-specific unless alternatives are also shown.
- Where App Service plans are discussed, give equal prominence to Linux hosting options, not just mentioning them as an aside.
- Add a note or table at the start of the tutorial summarizing which commands to use for Windows vs. Linux/macOS.
- Include troubleshooting steps relevant to Linux/macOS environments (e.g., checking environment variables, npm/node issues on Unix-like systems).
IoT Hub
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-hub/monitor-iot-hub.md
...ure-docs/blob/main/articles/iot-hub/monitor-iot-hub.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page primarily describes Azure IoT Hub monitoring using the Azure portal and platform-agnostic tools (Kusto queries, Log Analytics, Event Grid), with no explicit command-line examples. However, in the 'SDK version in IoT Hub logs' section, all sample SDK version strings shown are from Windows environments (e.g., 'Windows_NT', 'Microsoft Windows'), and no Linux or macOS examples are provided. There are no PowerShell or Windows-specific tool instructions, but the absence of Linux/macOS examples and the exclusive use of Windows in SDK version samples indicate a subtle Windows-first bias.
Recommendations
- Include SDK version log examples from Linux and macOS environments (e.g., show sample sdkVersion strings from devices running on Ubuntu, Debian, or macOS).
- When showing sample log outputs or properties, provide a mix of OS platforms to reflect cross-platform usage.
- If referencing tutorials or external samples (such as Event Hubs client samples), ensure that links or instructions are available for both Windows and Linux environments.
- Explicitly mention that the monitoring and logging features are platform-agnostic, and provide guidance or screenshots from non-Windows environments where relevant.
IoT Hub
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-hub/quickstart-send-telemetry-cli.md
...main/articles/iot-hub/quickstart-send-telemetry-cli.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation generally maintains cross-platform parity by focusing on the Azure CLI and Cloud Shell, which are available on both Windows and Linux. However, there are subtle signs of Windows bias: Windows tools (e.g., Windows Terminal) are mentioned before Linux equivalents, and PowerShell is given special attention, including dedicated notes and command variants, while Linux shells are not similarly highlighted. There are no Linux-specific examples or troubleshooting notes, and the documentation does not mention Linux terminals or tools by name.
Recommendations
- When referencing local CLI usage, mention both Windows Terminal and common Linux terminals (e.g., GNOME Terminal, Konsole, xterm) to reinforce cross-platform support.
- Provide equal attention to Bash and PowerShell, including troubleshooting notes or command variants for Bash where relevant (not just PowerShell).
- Add explicit statements or notes confirming that all examples work identically on Linux, macOS, and Windows, or highlight any differences.
- Include screenshots or references to Linux environments where possible, not just Windows-based visuals.
- If mentioning PowerShell-specific syntax (e.g., JSON escaping), consider also noting any Bash-specific tips or common issues.
IoT Hub
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-hub/reference-x509-certificates.md
...b/main/articles/iot-hub/reference-x509-certificates.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation is generally cross-platform and uses OpenSSL (a cross-platform tool) and Bash shell commands for most certificate operations, which is favorable for Linux users. However, in the 'Verify certificate manually after upload' section, the PowerShell script option is listed first, and the Bash script is mentioned second. This ordering, along with explicit mention of PowerShell, subtly prioritizes Windows workflows. There is also a reference to a PowerShell script 'supplied by Microsoft' without a corresponding mention of a native Linux tool or parity in script support.
Recommendations
- List Bash/Linux examples before or alongside PowerShell/Windows examples to avoid implying Windows is the primary or preferred platform.
- Ensure that any scripts or tools supplied by Microsoft for Windows (e.g., PowerShell scripts) have equivalent, well-documented Linux/Bash versions, and mention them equally.
- Explicitly state that all steps can be performed on both Windows and Linux, and clarify any platform-specific requirements.
- Where possible, provide cross-platform scripts (e.g., in Python or as Docker containers) to further reduce platform bias.
- Review future documentation to ensure that Windows-specific tools or workflows are not given priority unless there is a technical reason.
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
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows Tools
Summary
The documentation provides instructions for using the Azure Portal (web-based, cross-platform) and Azure CLI (cross-platform), but the only code sample for simulating device messages is a .NET console application (SimulatedDevice), which is Windows-centric by default. There are no examples or guidance for running the simulated device on Linux or using other common cross-platform languages/tools (such as Python). The documentation also references editing and running a C# file (Program.cs), which assumes a Windows development environment or familiarity with .NET tooling.
Recommendations
- Provide alternative simulated device code samples in a cross-platform language such as Python or Node.js, and include instructions for running them on Linux.
- Explicitly mention that the .NET sample can be run on Linux using .NET Core, and provide installation instructions or a link.
- Add a note or section for Linux/macOS users, clarifying any differences or prerequisites for running the sample code.
- Consider including Bash shell examples alongside Azure CLI commands, especially for variable setting and environment preparation.
- Reference or link to official cross-platform SDKs and samples for Azure IoT Hub, highlighting their compatibility with Linux.
IoT Hub
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-hub/tutorial-routing.md
...re-docs/blob/main/articles/iot-hub/tutorial-routing.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a bias towards Windows by only providing .NET (C#) sample code, which is most commonly associated with Windows environments, and by referencing Azure IoT Explorer, a GUI tool that is only officially available for Windows and Mac. There are no Linux-specific code samples, nor are there instructions for sending device telemetry using cross-platform or Linux-native tools (such as Python, Node.js, or command-line utilities like mosquitto_pub). The tutorial assumes the user is comfortable with .NET and does not mention or link to equivalent SDKs or instructions for Linux users.
Recommendations
- Provide sample code and instructions using cross-platform SDKs, such as Python or Node.js, which are popular and well-supported on Linux.
- Include explicit instructions or examples for sending device telemetry using command-line tools available on Linux (e.g., mosquitto_pub for MQTT).
- Mention and link to the Azure IoT SDKs for other languages (Python, JavaScript, Java, C) and show how to run the sample on Linux.
- Clarify the availability of Azure IoT Explorer on Linux, and if not available, suggest alternative methods (such as using the Azure CLI or other open-source tools) for monitoring device messages.
- Add a note in the prerequisites and sample code sections that the tutorial is cross-platform, and provide any necessary Linux-specific setup steps (e.g., installing .NET Core on Linux, or using a different SDK).
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
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation demonstrates a mild Windows bias by consistently referencing Windows-specific tools and workflows before their Linux equivalents. For example, it recommends using Git Bash (a Windows tool) to access OpenSSL, and provides Windows-specific instructions and notes before Linux ones. The documentation assumes a Windows environment in several prerequisite and setup steps, and only later provides Linux alternatives. However, both Windows and Linux command examples are ultimately provided, and OpenSSL (a cross-platform tool) is used throughout.
Recommendations
- Present Linux and Windows instructions in parallel or in a neutral order, rather than listing Windows first.
- In the prerequisites, clarify that OpenSSL and Git are available natively on Linux/macOS, and that Git Bash is primarily needed for Windows users.
- Avoid assuming the use of Git Bash for all users; suggest native terminals for Linux/macOS.
- Explicitly mention macOS support and provide corresponding instructions where applicable.
- Where possible, use cross-platform language and tools, and avoid Windows-centric terminology unless necessary.
- In notes and recommendations, avoid defaulting to Windows-specific advice (e.g., 'unless you're familiar with OpenSSL and it's already installed on your Windows machine...'). Instead, provide equivalent guidance for all platforms.
IoT Hub
Register and connect an IoT device
...cs/blob/main/articles/iot-hub/create-connect-device.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation page references PowerShell commands and Visual Studio Code (a tool more commonly used on Windows) as additional management options, and lists PowerShell before REST API. While the main instructions use the Azure portal and Azure CLI (both cross-platform), the explicit mention of PowerShell and the ordering of tools suggest a mild Windows bias. No Linux/macOS-specific tools or patterns are mentioned, and PowerShell is not marked as Windows-only, which could confuse Linux/macOS users.
Recommendations
- Clarify that PowerShell commands are primarily for Windows, and provide equivalent Bash or shell script examples for Linux/macOS users.
- List REST API and CLI options before PowerShell in the 'Other tools' section to avoid Windows-first ordering.
- Mention Linux/macOS compatibility for Visual Studio Code and Azure CLI, and suggest alternative editors or tools where appropriate.
- If possible, add explicit Linux/macOS command-line examples (e.g., using curl for REST API calls) to improve parity.
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
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation mentions Azure PowerShell as a configuration option alongside Azure CLI and Azure Portal, but does not mention Linux/macOS-specific tools or provide parity for command-line examples. The order of configuration tools lists Azure PowerShell after CLI and Portal, but does not clarify cross-platform compatibility or provide Bash or Linux shell examples.
Recommendations
- Explicitly state that Azure CLI is cross-platform and provide example commands for both Windows (PowerShell) and Linux/macOS (Bash).
- Include instructions or links for configuring file upload using Linux/macOS tools, such as Bash scripts or native shell commands.
- Clarify the availability of Azure PowerShell on non-Windows platforms, or provide alternatives for Linux/macOS users.
- Ensure that all referenced SDK samples include instructions for running on Linux/macOS as well as Windows.
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation for the C#/.NET SDK presents Windows-specific instructions (ETW, PowerShell scripts) before Linux alternatives, with detailed guidance and links for Windows tools. The Linux section is present and reasonably detailed, but Windows is prioritized and receives more attention to tooling. Other language sections are OS-neutral or provide parity.
Recommendations
- Present Windows and Linux instructions in parallel or with equal prominence, rather than Windows first.
- Provide equally detailed tooling and troubleshooting guidance for Linux/macOS users, including links to relevant resources.
- Explicitly mention macOS support (if applicable) and provide examples or caveats.
- Where possible, use cross-platform tools or highlight their availability.
- Add a summary table comparing Windows and Linux/macOS approaches for quick reference.
IoT Hub
Create and delete routes and endpoints by using Azure Resource Manager
...-docs/blob/main/articles/iot-hub/how-to-routing-arm.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides deployment instructions using both Azure CLI and PowerShell, but PowerShell examples are given equal prominence and use Windows-style file paths (e.g., 'my\path\to\template.json'), which may confuse Linux/macOS users. The Azure portal instructions and screenshots are platform-neutral, but the command-line examples do not mention Linux/macOS explicitly, nor do they provide Bash-specific notes or file path conventions. PowerShell is a Windows-centric tool, though it is available cross-platform; however, its usage is still more common on Windows.
Recommendations
- Add explicit notes clarifying that Azure CLI commands work identically on Linux, macOS, and Windows.
- Use POSIX-style file paths (e.g., 'my/path/to/template.json') in CLI examples, or provide both Windows and Linux/macOS variants.
- Clarify that PowerShell is available on Linux/macOS, but most users on those platforms will use Bash with Azure CLI.
- Consider listing Azure CLI examples before PowerShell, as CLI is more cross-platform.
- Add a brief section or callout for Linux/macOS users, highlighting any differences or confirming parity.
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides examples for both Azure CLI and Azure PowerShell, but the PowerShell section is given its own dedicated heading and detailed code block, while the CLI section is shorter and less detailed. The PowerShell examples are Windows-specific, and there is no mention of Linux/macOS equivalents for PowerShell. The ordering places the Azure CLI section before PowerShell, but the PowerShell section is more comprehensive. There are no explicit Linux/macOS examples or notes about cross-platform usage for CLI or PowerShell.
Recommendations
- Clarify that Azure CLI works cross-platform (Windows, Linux, macOS) and provide explicit examples or notes for Linux/macOS users.
- Note that Azure PowerShell is available on Linux/macOS via PowerShell Core, and provide installation or usage guidance if relevant.
- Ensure parity in example depth and troubleshooting for both CLI and PowerShell sections.
- Consider adding a table comparing CLI and PowerShell commands for common tasks.
- Add a brief section or note on REST API usage from Linux/macOS (e.g., using curl or httpie).
IoT Hub
How to manage devices and modules using twins
...docs/blob/main/articles/iot-hub/manage-device-twins.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation is generally cross-platform, focusing on Azure Portal and Azure CLI, which are available on Windows, Linux, and macOS. However, there are repeated PowerShell-specific tips for escaping quotes, and Cloud Shell is mentioned as available in Windows Terminal before other platforms. No Linux/macOS-specific examples or considerations are provided, and Windows tools/patterns are referenced first.
Recommendations
- Add explicit examples or tips for Linux/macOS users, such as how to escape quotes in Bash/zsh.
- Mention that Azure CLI and Cloud Shell are available on Linux/macOS terminals (e.g., GNOME Terminal, iTerm2) as well as Windows Terminal.
- Provide command-line examples showing both Windows (PowerShell) and Linux/macOS (Bash/zsh) syntax where escaping or file paths differ.
- Avoid mentioning Windows tools (like Windows Terminal) before cross-platform alternatives unless relevant.
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation page is generally cross-platform and avoids explicit command-line examples, but it does show a mild Windows bias in the SDK version examples, where only Windows platforms are shown for Node.js and .NET SDKs. Additionally, the only external sample link for Event Hubs is to a .NET (Windows-centric) sample, with no Linux/macOS or cross-platform alternatives mentioned. No Linux-specific tools, patterns, or examples are provided, and Windows appears first in platform mentions.
Recommendations
- Include SDK version examples for Linux and macOS platforms alongside Windows in the 'SDK version in IoT Hub logs' section.
- Provide links to Event Hubs client samples for other languages (e.g., Python, Java, Node.js) that are commonly used on Linux/macOS.
- Explicitly mention that all portal and Kusto query operations are cross-platform and accessible from any OS.
- If command-line or scripting examples are added in the future, ensure both PowerShell/Windows and Bash/Linux equivalents are provided.
IoT Hub
X.509 certificates | Microsoft Docs
...b/main/articles/iot-hub/reference-x509-certificates.md
Low Priority
View Details →
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 before Bash/OpenSSL, and the PowerShell script is described as 'supplied by Microsoft', potentially implying a Windows-first approach. There is a slight emphasis on Windows tooling and ordering, but Linux parity is generally maintained with Bash/OpenSSL instructions.
Recommendations
- List Bash/OpenSSL and PowerShell examples in parallel or alternate their order to avoid Windows-first impression.
- Explicitly mention Linux/macOS compatibility for Bash/OpenSSL steps.
- Provide links to Bash script documentation with equal prominence as PowerShell.
- Clarify that all examples are supported on both Windows and Linux/macOS where applicable.
IoT Hub
Tutorial - Set up and use metrics and logs with an Azure IoT hub
...ain/articles/iot-hub/tutorial-use-metrics-and-diags.md
Low Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation is generally cross-platform, using Azure CLI and .NET Core SDK, which are available on Windows, Linux, and macOS. However, there are subtle Windows-first biases: the simulated device app example is C#/.NET only, with no mention of Linux/macOS-specific instructions or alternative languages. The instructions for running commands use generic 'cmd/sh', but screenshots and navigation steps are Azure Portal-centric, which is platform-agnostic. There is no explicit mention of Linux/macOS differences, nor are Linux-specific troubleshooting steps or alternative device samples (e.g., Python) provided.
Recommendations
- Explicitly state that all CLI and .NET instructions work on Linux/macOS, and provide troubleshooting notes for common platform-specific issues (e.g., permissions, dependencies).
- Offer alternative device simulation samples in Python or Node.js, with instructions for Linux/macOS users.
- Include example commands and screenshots from Linux/macOS terminals, or clarify that the steps are identical across platforms.
- Add a note about installing Azure CLI and .NET Core SDK on Linux/macOS, with links to official instructions.
- If PowerShell is mentioned elsewhere, ensure Bash equivalents are provided and shown first or equally.
IoT Hub
Register and connect an IoT device
...cs/blob/main/articles/iot-hub/create-connect-device.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Windows First
Summary
The documentation page demonstrates mild Windows bias by explicitly listing PowerShell as a management option and referencing Visual Studio Code (commonly associated with Windows, though cross-platform). PowerShell is mentioned before REST API, and there is no mention of Linux-specific tools or patterns. However, the main CLI instructions use Azure CLI, which is cross-platform, and no steps are strictly Windows-only.
Recommendations
- Explicitly mention that Azure CLI works on Linux/macOS and provide example shell environments (e.g., bash, zsh).
- Include Linux-native management options, such as using curl for REST API calls, or reference Linux desktop tools if available.
- When listing management tools, avoid listing PowerShell first or exclusively; balance with Linux/macOS equivalents.
- Clarify that Visual Studio Code and Azure CLI are cross-platform, and provide installation links for Linux/macOS.
- If PowerShell is mentioned, note that PowerShell Core is available on Linux/macOS.
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation page is largely platform-neutral, focusing on Azure portal, Event Grid, and Kusto queries, which are accessible from any OS. However, there is a subtle Windows bias in the SDK version examples, which exclusively show Windows environments (Node.js and .NET SDKs running on Windows) and do not mention or show Linux/macOS equivalents. Additionally, the only external code sample referenced is for .NET (Windows-centric), with no mention of Linux/macOS or cross-platform alternatives.
Recommendations
- Include SDK version examples for Linux and macOS environments alongside Windows examples to demonstrate parity.
- Reference or link to Event Hubs client samples for Python, Java, or Node.js, which are cross-platform, not just .NET.
- Explicitly state that all monitoring and analytics features (Azure portal, Kusto queries, Event Grid) are accessible from Linux/macOS as well as Windows.
- Where screenshots or instructions reference the Azure portal, clarify that it is web-based and OS-independent.
- If CLI or scripting is relevant, provide examples for Azure CLI (cross-platform) in addition to any PowerShell or .NET references.
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation presents three configuration methods: Azure portal, Azure CLI, and Azure PowerShell. While Azure CLI is cross-platform, the explicit inclusion of Azure PowerShell as a primary method introduces a Windows bias, as PowerShell is traditionally associated with Windows environments. The zone pivot order lists PowerShell after CLI, but its presence as a top-level method may imply parity with CLI, despite PowerShell's historical Windows association. There are no explicit Linux/macOS-specific instructions or examples, and no mention of platform-specific considerations for CLI or PowerShell usage.
Recommendations
- Clarify that Azure CLI is fully cross-platform and provide explicit instructions or notes for Linux/macOS users where relevant.
- If PowerShell is included, mention that PowerShell Core is available on Linux/macOS, and provide installation guidance or links for non-Windows users.
- Consider adding bash or shell script examples for Linux users, or at least note that CLI commands work natively in bash/zsh.
- Ensure that any referenced tools or scripts are available and tested on Linux/macOS platforms.
Low Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Windows First
Summary
The documentation provides parallel instructions for Azure Portal, Azure CLI, and Azure PowerShell throughout, but PowerShell (a Windows-centric tool) is consistently presented as a primary option alongside CLI. There is no explicit mention of Linux/macOS alternatives to PowerShell, nor guidance for users who may not have access to PowerShell. The CLI examples are cross-platform, but PowerShell is a Windows-specific tool and its inclusion may suggest Windows bias. Additionally, PowerShell instructions are given equal prominence to CLI, which is more universal.
Recommendations
- Clarify that Azure CLI is fully supported on Linux/macOS and is the recommended cross-platform tool.
- Add notes indicating that Azure PowerShell is primarily for Windows users, and suggest CLI for Linux/macOS.
- Consider presenting CLI examples before PowerShell, or grouping PowerShell as a Windows-specific section.
- Explicitly mention that all tasks can be completed on Linux/macOS using the CLI.
- If possible, add bash shell script examples for common tasks to further support Linux users.
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
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation mentions Azure PowerShell as a tool for configuring file upload, alongside Azure CLI and Azure Portal, but does not mention Linux/macOS equivalents or alternatives (e.g., Bash scripts, cross-platform shell usage). The order of tools listed places Azure PowerShell after CLI and Portal, but its inclusion without explicit Linux parity may suggest a slight Windows bias.
Recommendations
- Explicitly state that Azure CLI and Azure Portal are cross-platform, and clarify that Azure PowerShell is available on Linux/macOS as well.
- Provide examples or links for configuring file upload using Bash or other Linux-native tools if available.
- Ensure that referenced SDK samples and included guides cover Linux/macOS usage, not just Windows environments.
- Add a note about platform compatibility for each tool mentioned.
IoT Hub
Overview of Azure IoT Hub message enrichments
...ticles/iot-hub/iot-hub-message-enrichments-overview.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation lists Azure PowerShell as a configuration method alongside Azure CLI and Portal, but does not mention Linux/macOS-specific tools or clarify cross-platform compatibility. PowerShell is a Windows-centric tool, and its mention before any Linux-specific alternatives may suggest a Windows-first bias. However, Azure CLI and Portal are cross-platform, and no examples or instructions are given that are exclusive to Windows.
Recommendations
- Explicitly state that Azure CLI and Portal are cross-platform and suitable for Linux/macOS users.
- Clarify that Azure PowerShell is available on Linux/macOS, or provide Bash/shell script examples for Linux users.
- Add a note or section highlighting Linux/macOS usage patterns or common tools for managing IoT Hub enrichments.
- Ensure that future examples or tutorials include both PowerShell and Bash/CLI commands, with equal prominence.
IoT Hub
How to manage devices and modules using twins
...docs/blob/main/articles/iot-hub/manage-device-twins.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation is generally cross-platform, focusing on Azure Portal and Azure CLI, which are available on Windows, Linux, and macOS. However, there are minor signs of Windows bias: PowerShell-specific tips are included (escaping double quotes), and references to running Azure CLI in Windows Terminal are made before mentioning other platforms. No Linux/macOS-specific examples or shell tips are provided, and the only shell-specific advice is for PowerShell users.
Recommendations
- Add shell-specific tips for Bash/zsh users, such as how to escape quotes or handle JSON in Linux/macOS terminals.
- Mention that Azure CLI commands work equally on Linux/macOS and provide examples of running them in Bash/zsh.
- Balance references to Windows Terminal with mentions of common Linux/macOS terminals (e.g., GNOME Terminal, Terminal.app).
- Include a note that PowerShell is available cross-platform, but also provide Bash/zsh equivalents where shell-specific syntax matters.