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 101-125 of 155 flagged pages
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for managing IP filters, but the PowerShell section is given equal prominence and detail, despite PowerShell being primarily a Windows tool. There are no explicit Linux shell (bash) or cross-platform scripting examples, and the GUI instructions reference 'your computer' without clarifying cross-platform differences. Azure CLI is cross-platform, but no Linux-specific context or troubleshooting is provided. The PowerShell section may suggest a Windows-centric audience.
Recommendations
- Add explicit bash/shell examples for Linux users, especially for scripting or automation.
- Clarify that Azure CLI commands work identically on Linux, macOS, and Windows, and provide troubleshooting tips for common Linux issues (e.g., authentication, JSON parsing).
- Mention that PowerShell Core is available cross-platform, but provide bash alternatives for Linux users.
- In GUI instructions, clarify any OS-specific steps (e.g., how to find your IP address on Linux vs. Windows).
- Consider reordering sections to present Azure CLI (cross-platform) before PowerShell, or combine scripting guidance with clear OS parity.
Create Pull Request
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page shows subtle Windows bias in the SDK version examples, which exclusively reference Windows platforms (e.g., 'Windows_NT', 'Microsoft Windows'). There are no Linux or macOS platform examples, and no Linux-specific tools, commands, or screenshots are mentioned. All portal screenshots and instructions are platform-neutral, but the only concrete OS references are Windows. There are no PowerShell-heavy sections or Windows-only tools, but Linux parity is lacking in examples and platform mentions.
Recommendations
- Add SDK version examples for Linux and macOS platforms alongside Windows examples to demonstrate cross-platform support.
- Include references or screenshots showing IoT Hub monitoring from Linux environments, such as using Azure CLI or relevant shell commands.
- Explicitly mention that all features and monitoring capabilities are available on Linux and macOS, not just Windows.
- Where OS-specific properties or behaviors are discussed (e.g., sdkVersion), provide sample outputs for Linux and macOS.
- If possible, link to cross-platform sample code or tutorials, including those using Bash or other Linux-native tools.
IoT Hub
Quickstart - Send telemetry to Azure IoT Hub (CLI) quickstart
...main/articles/iot-hub/quickstart-send-telemetry-cli.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation demonstrates mild Windows bias by referencing Windows Terminal as an example app for running the Azure CLI, and by providing explicit PowerShell command syntax and escape guidance before or alongside Bash equivalents. While Bash is used as the primary example, PowerShell is mentioned frequently, and special notes are given for PowerShell users. There is no explicit Linux example or mention of Linux-specific tools or environments, and Windows tools are referenced first in some cases.
Recommendations
- Mention Linux terminal applications (e.g., GNOME Terminal, Konsole) alongside Windows Terminal when describing local CLI usage.
- Provide explicit examples or notes for running the Azure CLI on Linux and macOS, including installation and environment setup.
- Ensure Bash examples are presented first, with PowerShell as an alternative, and clarify parity between environments.
- Add a section or note confirming that all CLI commands work equally on Linux, macOS, and Windows, and link to cross-platform CLI documentation.
- Avoid referencing Windows tools or environments before Linux/macOS equivalents unless there is a technical reason.
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 exhibits a mild Windows bias. In the SDK version section, only Windows-based examples are provided for the Node.js and .NET SDKs, with explicit references to Windows OS versions. There are no Linux or macOS examples or mentions. Additionally, when referencing sample code for reading events from Azure Event Hubs, only a .NET (Windows-centric) sample is linked, with no mention of Linux-friendly languages or tools. Throughout the document, there are no examples or instructions that specifically address Linux environments, nor is there guidance for Linux users on how to perform monitoring tasks outside the Azure Portal.
Recommendations
- Add SDK version examples for Linux and macOS platforms alongside Windows examples to demonstrate cross-platform support.
- Include links to sample code for reading events from Event Hubs in Linux-friendly languages such as Python, Java, or Node.js.
- Explicitly mention that the Azure Portal and monitoring features are accessible from any OS, and provide CLI or script examples (e.g., using Azure CLI, Bash) for common monitoring tasks.
- Where screenshots or instructions reference Windows-specific UI or terminology, clarify that the steps are OS-agnostic or provide Linux/macOS equivalents if applicable.
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 Azure CLI, and Windows-style file paths (e.g., 'my\path\to\template.json') are used in CLI examples. There are no Linux-specific instructions, nor is there mention of Linux shell patterns or tools. The documentation assumes familiarity with PowerShell and Windows conventions, which may disadvantage Linux users.
Recommendations
- Use platform-neutral file path examples in CLI commands (e.g., 'my/path/to/template.json' for Linux/macOS).
- Explicitly mention that Azure CLI works on Linux, macOS, and Windows, and provide shell-specific guidance if needed.
- Consider adding Bash or Linux shell examples where appropriate, especially for file operations or scripting.
- Clarify that PowerShell examples are for users on Windows or PowerShell Core on Linux/macOS, and provide links to relevant installation guides.
- Review screenshots and instructions to ensure they do not assume a Windows environment unless necessary.
IoT Hub
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-hub/iot-hub-configure-file-upload.md
...main/articles/iot-hub/iot-hub-configure-file-upload.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation page presents configuration instructions for IoT Hub file uploads using three methods: Azure portal, Azure CLI, and Azure PowerShell. The inclusion of Azure PowerShell as a primary method introduces a Windows bias, as PowerShell is traditionally a Windows-centric tool, even though it is now cross-platform. The zone pivots list 'powershell' as a top-level option alongside 'portal' and 'azcli', which may prioritize Windows workflows. There is no explicit mention of Linux-specific tools or patterns, and no Linux-first examples are given.
Recommendations
- Clarify that Azure CLI and PowerShell are both cross-platform, and provide explicit instructions or notes for Linux users where relevant.
- Consider adding Linux-specific examples or workflows, such as using Bash scripts or referencing common Linux shell environments.
- If PowerShell is included, note its availability on Linux and macOS, and provide installation guidance for those platforms.
- Ensure that examples and instructions do not assume a Windows environment (e.g., avoid referencing Windows-only paths or conventions).
- Add a section or note highlighting parity between Windows and Linux for all configuration methods.
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
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for managing IP filters, but PowerShell (a Windows-centric tool) is given its own dedicated section after CLI. There are no explicit Linux shell (bash) examples, nor is there mention of Linux-specific tools or patterns. The screenshots and portal instructions are platform-neutral, but the command-line guidance leans toward Windows/PowerShell, and PowerShell is presented after CLI, which may imply parity but still reinforces Windows familiarity.
Recommendations
- Add explicit bash/Linux shell examples for retrieving and updating IP filters using Azure CLI, including sample commands and expected outputs.
- Clarify that Azure CLI is cross-platform and can be used on Linux, macOS, and Windows.
- If possible, provide examples using native Linux tools (e.g., curl for REST API calls) to demonstrate REST interactions.
- Balance the prominence of PowerShell and CLI sections, perhaps by grouping them under a 'Command-line' heading and noting platform compatibility.
- Include a note or table summarizing which tools are available on which platforms (Windows, Linux, macOS) to help users choose appropriately.
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 page is largely neutral and cross-platform, especially in its use of OpenSSL and Bash examples for certificate generation and management. However, in the 'Verify certificate manually after upload' section, the PowerShell script is mentioned first when describing ways to generate a verification certificate, with the Bash script and OpenSSL methods following. This ordering may subtly prioritize Windows users and workflows. Additionally, the explicit mention of a Microsoft-supplied PowerShell script as a primary option reinforces a Windows-centric approach.
Recommendations
- Present Bash and OpenSSL examples before PowerShell examples, or list all methods in parallel without ordering preference.
- Explicitly state that all methods (PowerShell, Bash, OpenSSL) are equally supported and available for both Windows and Linux users.
- Where possible, provide direct Linux shell equivalents for any Windows-specific tools or scripts.
- Add a note clarifying cross-platform support and encourage users to select the method that matches their environment.
- Consider including example usage for macOS if relevant, to further broaden platform parity.
IoT Hub
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-hub/iot-hub-configure-file-upload.md
...main/articles/iot-hub/iot-hub-configure-file-upload.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation page presents configuration instructions for IoT Hub file uploads using the Azure portal, Azure CLI, and Azure PowerShell. While the Azure CLI is cross-platform, the inclusion of Azure PowerShell as a primary method and its equal prominence alongside CLI and portal suggests a Windows bias, as PowerShell is traditionally associated with Windows environments. The documentation does not explicitly provide Linux-specific examples or mention Linux tools, and the ordering of pivots (portal, CLI, PowerShell) does not prioritize Linux-native workflows.
Recommendations
- Explicitly mention that Azure CLI works on Linux, macOS, and Windows, and provide examples of running CLI commands on Linux.
- Clarify that PowerShell Core is cross-platform, or note that PowerShell instructions are primarily for Windows users.
- Add Linux-specific notes or troubleshooting tips for file upload configuration, especially for common issues encountered on Linux.
- Consider including bash script examples or references to Linux shell environments where relevant.
- Ensure parity in detail and troubleshooting between PowerShell and CLI sections, so Linux users are not disadvantaged.
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 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 the Bash and OpenSSL equivalents. The PowerShell script is described as 'supplied by Microsoft', which may imply a Windows-first approach. There is a slight emphasis on Windows tooling and patterns by listing PowerShell first and referencing Microsoft-supplied scripts, though Linux parity is generally maintained with Bash/OpenSSL examples.
Recommendations
- List Bash/OpenSSL and PowerShell methods in parallel or alternate the order to avoid implicit prioritization of Windows tools.
- Explicitly state that both Windows and Linux workflows are supported and provide equal prominence to both.
- Where Microsoft-supplied scripts are referenced, clarify if equivalent scripts are available for Linux and provide direct links.
- Add a short introductory note in relevant sections indicating cross-platform support and parity.
- Consider including a table or side-by-side comparison of Windows (PowerShell) and Linux (Bash/OpenSSL) commands for clarity.
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 demonstrates a subtle Windows bias. In the 'SDK version in IoT Hub logs' section, the only concrete examples of the sdkVersion property use Windows platforms (Node.js on Windows, .NET on Windows), with no Linux or macOS equivalents. Additionally, when referencing sample code for reading events from Azure Event Hubs, only a .NET (Windows-centric) sample is linked, with no mention of Linux-friendly languages or tools. There are no PowerShell-specific examples, but the platform references and sample links prioritize Windows environments and omit Linux-specific guidance.
Recommendations
- Add sdkVersion examples for devices running on Linux and macOS platforms (e.g., Node.js on Ubuntu, Python on Raspberry Pi OS, .NET on Linux).
- When referencing sample code for Event Hubs or other SDKs, include links to samples in cross-platform languages (e.g., Python, Java, Node.js) and clarify their compatibility with Linux.
- Explicitly mention that all SDKs and monitoring tools are supported on Linux, and provide guidance or screenshots for Linux users where portal or CLI usage may differ.
- Where platform-specific properties (such as sdkVersion) are shown, provide a table or list of typical values for Linux and macOS in addition to Windows.
- Ensure that any instructions for setting up monitoring, alerts, or diagnostics include CLI or automation examples that work on Linux (e.g., Azure CLI, Bash scripts), not just portal screenshots.
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
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for managing IP filters, but PowerShell (a Windows-centric tool) is given its own dedicated section after CLI. There are no explicit Linux shell (bash) or cross-platform scripting examples, and no mention of Linux-specific tools or patterns. The screenshots and UI instructions are platform-neutral, but the command-line guidance leans toward Windows users by including PowerShell and omitting Linux shell equivalents.
Recommendations
- Add explicit bash (Linux/macOS) shell examples for retrieving and updating IP filters using Azure CLI, including usage with jq for parsing JSON.
- Clarify that Azure CLI commands work cross-platform and provide sample commands for Linux/macOS environments.
- If PowerShell is included, consider also including examples using bash or zsh to ensure parity.
- Mention that Azure CLI is available on Windows, Linux, and macOS, and provide installation links for all platforms.
- Ensure that any scripting or automation examples are presented in both PowerShell and bash, or in a platform-neutral way.
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
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page shows mild Windows bias by listing Azure PowerShell as a configuration option alongside Azure CLI and Azure Portal, and by mentioning PowerShell after CLI (which is cross-platform) but before any Linux-specific tools. There are no explicit Linux shell or command-line examples, and no mention of Linux-specific tools or patterns. However, the programming language examples themselves are not shown, so further bias in code samples cannot be assessed from the provided content.
Recommendations
- Ensure that all command-line instructions are provided for both Azure CLI and Azure PowerShell, with clear indications of platform compatibility (e.g., note that Azure CLI is cross-platform, while PowerShell is available on both Windows and Linux).
- When listing configuration options, avoid listing PowerShell immediately after CLI, or clarify that both are available on all platforms.
- Add explicit Linux shell (bash) examples or references where relevant, especially for device-side operations.
- If any code samples or instructions use Windows-specific paths, commands, or conventions, provide equivalent Linux/macOS examples.
- Consider adding a section or note on platform compatibility for all tools and SDKs mentioned.
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 provides both Bash/OpenSSL and PowerShell examples for certificate creation and verification, but in the 'Verify certificate manually after upload' section, the PowerShell script is mentioned first, followed by Bash and OpenSSL. This ordering subtly prioritizes Windows tooling. Additionally, the explicit mention of a 'PowerShell script supplied by Microsoft' as the first option, with Bash and OpenSSL as alternatives, reflects a mild Windows-first and PowerShell-heavy bias. However, Linux tooling (Bash/OpenSSL) is well represented and not omitted.
Recommendations
- Present Bash/OpenSSL and PowerShell examples in parallel or randomize their order to avoid implying a default platform.
- Explicitly state that all methods are equally supported and that users should choose the one that fits their environment.
- Where possible, provide cross-platform scripts or note any platform-specific limitations.
- Ensure that Linux-first or neutral ordering is used in at least some sections, especially in cross-platform documentation.
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 by default, provides only Windows (cmd) commands for setting environment variables and running commands, and does not include equivalent Linux/bash examples. While it mentions that steps can be performed on Linux, it does not provide explicit Linux instructions or command syntax, which may hinder Linux users.
Recommendations
- Provide Linux/bash equivalents for all command-line instructions, especially for setting environment variables (e.g., export VAR=value).
- When showing command-line examples, present both Windows (cmd) and Linux (bash) commands side by side or in tabs.
- Avoid language such as 'the steps in this article assume a Windows development machine' unless absolutely necessary; instead, state that instructions are cross-platform and provide both sets of commands.
- Explicitly mention any OS-specific differences in steps, tools, or behaviors.
- Include screenshots or references to popular Linux editors or terminals where relevant, not just Visual Studio Code.
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 presents a cross-platform workflow using the Azure CLI and Cloud Shell, which are available on both Windows and Linux. However, there are subtle indications of Windows bias: Windows tools (Windows Terminal) are mentioned before Linux equivalents, and PowerShell is given equal or slightly more prominence than Bash in some sections. Additionally, PowerShell-specific command syntax is included, but there is no mention of Linux-specific shells or issues. There are no Linux-specific examples or troubleshooting notes, and the guidance for local CLI use references Windows tools first.
Recommendations
- When mentioning local CLI usage, list both Windows Terminal and common Linux terminals (e.g., GNOME Terminal, Konsole) to avoid Windows-first bias.
- Include troubleshooting notes or tips for common Linux shell issues (e.g., line endings, permissions) alongside PowerShell notes.
- When presenting command syntax differences, ensure Bash (or other Unix shells) are given equal or first prominence, and clarify that PowerShell is just one of several options.
- Explicitly state that all commands work on both Windows and Linux, and provide links to platform-specific installation or usage guides where relevant.
- Consider adding a brief section or callout for Linux/macOS users, especially when discussing local CLI installation or environment setup.
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
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation references Azure PowerShell as a configuration option alongside Azure CLI and the Azure portal, which may indicate a slight Windows bias by explicitly mentioning a Windows-centric tool. Additionally, PowerShell is mentioned after CLI and portal, but its inclusion without mention of Bash or Linux-native tools could suggest a subtle preference for Windows environments.
Recommendations
- Explicitly mention that Azure CLI is cross-platform and works on Linux, macOS, and Windows.
- If referencing PowerShell, clarify that PowerShell Core is also available cross-platform, or provide Bash/Linux shell equivalents where appropriate.
- Consider including examples or links for configuring file upload using Bash scripts or Linux-native tools, if available.
- Ensure that all referenced tooling is clearly marked as cross-platform or provide alternatives for Linux users.
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 First
Windows Tools
Summary
The documentation references configuration via Azure portal, Azure CLI, and PowerShell, listing PowerShell as a primary method alongside CLI and portal. PowerShell is a Windows-centric tool, and its mention alongside CLI (which is cross-platform) without explicitly noting Linux alternatives or parity may indicate a subtle Windows bias. However, the documentation does not provide any OS-specific command-line examples, nor does it show preference for Windows-only SDKs or scripting languages. The SDK examples are language-based and not OS-specific. There are no explicit PowerShell-heavy examples or missing Linux examples, but the inclusion of PowerShell as a main configuration tool and its mention before management APIs could be seen as a mild Windows-first bias.
Recommendations
- Clarify that Azure CLI is cross-platform and can be used on Linux, macOS, and Windows.
- If mentioning PowerShell, also mention Bash or shell scripting as alternatives for Linux users, or clarify that PowerShell Core is available cross-platform.
- Consider listing Azure CLI before PowerShell, as CLI is more universally accessible.
- Provide explicit notes or links for Linux/macOS users where configuration steps may differ, or confirm that all steps are OS-agnostic.
- Ensure that all code/configuration examples are presented in a way that is not OS-specific, or provide parallel examples for both Windows (PowerShell) and Linux (Bash/CLI) where relevant.
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 provides examples of SDK version strings that only reference Windows platforms (e.g., 'Windows_NT', 'Microsoft Windows'), and .NET/Node.js SDKs running on Windows. No Linux or macOS examples are shown, and there are no CLI or shell examples for Linux users. The only code samples are Kusto queries, which are platform-neutral, but where platform-specific output is shown, only Windows is mentioned.
Recommendations
- When showing SDK version strings, include examples for Linux and macOS platforms (e.g., Ubuntu, Debian, macOS) alongside Windows.
- If referencing .NET or Node.js SDKs, show example sdkVersion outputs for those SDKs running on Linux (e.g., '.NET/1.21.2 (.NET Core 3.1; Ubuntu 20.04; X64)').
- Where screenshots or instructions reference the Azure portal, consider adding notes or links for equivalent Azure CLI or az commands, which are cross-platform.
- Explicitly state that the monitoring and logging features are available and supported on all major platforms, not just Windows.
- If referencing sample code or Event Hubs client samples, include links to Linux/macOS compatible samples (e.g., Python, Java, or Node.js) in addition to .NET.
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 generally avoids strong Windows bias, providing OpenSSL/bash examples for certificate operations. However, in the 'Verify certificate manually after upload' section, the PowerShell script is mentioned before the Bash script, and the PowerShell script is described as 'supplied by Microsoft' (implying official support), which may suggest a Windows-first approach. Additionally, the presence of a dedicated PowerShell script, but not a corresponding Linux-native tool, could be seen as a subtle bias toward Windows environments.
Recommendations
- Present Bash and PowerShell script options in parallel, or alternate their order in different sections to avoid always listing Windows tools first.
- Clarify that both Bash and PowerShell scripts are officially supported and available, and provide equal prominence to both.
- Where possible, provide explicit Linux-native (e.g., shell/CLI) alternatives for all certificate management tasks, not just OpenSSL commands.
- Consider adding a table or section summarizing all available tooling (PowerShell, Bash, OpenSSL) for both Windows and Linux users, with clear guidance on when to use each.
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
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for managing IP filters, but PowerShell (a Windows-centric tool) is given its own dedicated section after the CLI. There are no Linux- or macOS-specific command-line or scripting examples, and no mention of platform differences or cross-platform considerations. The Azure CLI examples are cross-platform, but PowerShell is highlighted separately, which may suggest a Windows bias.
Recommendations
- Clarify that Azure CLI commands work on Windows, Linux, and macOS, and explicitly mention this cross-platform compatibility.
- If including a dedicated PowerShell section, consider also including a Bash scripting example for Linux/macOS users, or at least acknowledge that PowerShell Core is available cross-platform.
- Add a note or section about managing IP filters using Bash or other common Linux tools, if applicable.
- Ensure screenshots and UI instructions are not Windows-specific (e.g., avoid showing only Windows browser or OS UI elements).
- Where PowerShell is mentioned, clarify if the instructions are for Windows PowerShell or cross-platform PowerShell Core.
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 demonstrates mild Windows bias by referencing Windows-specific tools (Windows Terminal) before Linux equivalents, and by providing PowerShell-specific guidance and examples. Although Bash is presented as the default environment, PowerShell is mentioned frequently, and special instructions are given for PowerShell users, with no equivalent Linux-specific notes. There are no missing Linux examples, but the ordering and emphasis slightly favor Windows users.
Recommendations
- When referencing local CLI usage, mention both Windows Terminal and common Linux terminals (e.g., GNOME Terminal, Konsole) equally, or use neutral language such as 'terminal application'.
- When providing notes about command syntax differences, include explicit examples for both Bash (Linux/macOS) and PowerShell (Windows), and clarify which applies to which OS.
- Where PowerShell-specific escaping or syntax is discussed, consider also mentioning any common Linux shell issues or tips, to provide parity.
- Ensure that screenshots and UI references (such as Cloud Shell) are not visually or descriptively biased toward Windows environments.
- In the prerequisites, clarify that the Azure CLI can be installed and used on Windows, Linux, and macOS, and provide links or notes for all platforms.
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 (such as setting environment variables and running commands) given in Windows CMD syntax only. There are no Linux or macOS shell equivalents provided for setting environment variables or running the app, despite a brief mention that the steps can be performed on Linux. This creates a Windows-first bias and leaves Linux users without clear guidance for key steps.
Recommendations
- For every command-line example (e.g., setting environment variables, running npm commands, git commands), provide both Windows CMD and Linux/macOS shell (bash) equivalents, either side-by-side or in clearly marked tabs/sections.
- In the prerequisites, explicitly mention that the tutorial is cross-platform and provide links or notes for installing Node.js and Git on Linux/macOS.
- When referencing file navigation or editors, avoid Windows-specific terminology or provide Linux/macOS alternatives (e.g., mention 'your terminal' instead of 'command window').
- In the App Service section, clarify how to deploy to both Windows and Linux App Service plans, and provide Linux-specific az CLI examples where relevant.
- Add troubleshooting tips for common Linux/macOS issues (e.g., permissions, environment variable syntax, npm differences).
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 referencing Windows-specific tools and patterns before their Linux equivalents. For example, it recommends using Git Bash (a Windows tool) for OpenSSL access and provides Windows-specific instructions (e.g., 'winpty') before Linux ones in code tabs. The prerequisites and notes also focus on Windows installation paths and environment variables, with less emphasis on native Linux environments. However, Linux parity is generally maintained through side-by-side command examples.
Recommendations
- Present Linux-native instructions and tools before or alongside Windows-specific ones, rather than defaulting to Windows-first.
- Clarify that Git Bash is primarily a Windows solution and provide explicit instructions for native Linux/macOS terminals.
- In the prerequisites, mention Linux package managers (e.g., apt, yum, dnf) for OpenSSL installation, not just Windows installation methods.
- Avoid assuming the use of Git Bash for all platforms; instead, refer to 'terminal' or 'shell' generically, and specify platform-specific instructions only where necessary.
- Ensure that all environment variable and path instructions are cross-platform, or provide separate guidance for Linux/macOS.
- Where possible, provide PowerShell and Bash script examples side-by-side, or clarify when a script is platform-specific.
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
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation references Azure PowerShell as a configuration method alongside Azure CLI and the Azure portal, which can indicate a Windows bias, especially since PowerShell is traditionally associated with Windows environments. Additionally, the order of listing (portal, CLI, PowerShell) puts PowerShell before any mention of Linux-native tools or workflows. There are no explicit Linux-only examples or mentions of Linux-specific tools, and no indication that the examples or instructions are cross-platform.
Recommendations
- Clarify that Azure CLI is cross-platform and can be used on Linux, macOS, and Windows.
- If referencing PowerShell, note that PowerShell Core is also available on Linux and macOS, or provide equivalent Bash shell commands where appropriate.
- Add explicit Linux/macOS instructions or examples, especially for command-line configuration steps.
- Consider reordering the configuration methods to list the Azure CLI before PowerShell, as CLI is more commonly used in Linux environments.
- Where possible, include notes or callouts about cross-platform compatibility for all tools and SDKs mentioned.