IoT Hub

210
Total Pages
191
Linux-Friendly Pages
19
Pages with Bias
9.0%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

54 issues found
Showing 26-50 of 54 flagged pages
IoT Hub Get started with module identity and module twins (Portal) ...ob/main/articles/iot-hub/module-twins-portal-dotnet.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation is heavily oriented towards Windows development, specifically using Visual Studio and .NET. All examples and instructions assume a Windows environment, with no mention of Linux/macOS alternatives (e.g., VS Code, CLI, or cross-platform .NET usage). Steps for creating and running the sample app are tailored to Windows tools and workflows, leaving Linux users without guidance for completing the task.
Recommendations
  • Add instructions for creating and running the .NET sample using VS Code or the .NET CLI, which are cross-platform.
  • Include Linux/macOS-specific setup steps, such as installing .NET SDK and running the application from the terminal.
  • Provide screenshots or terminal commands relevant to Linux/macOS environments.
  • Mention alternative editors (VS Code, JetBrains Rider) and clarify that the .NET SDK and Azure IoT libraries are cross-platform.
  • Explicitly state platform compatibility and provide parity in examples.
GitHub Create Pull Request
IoT Hub Tutorial - Create and upload certificates for testing ...blob/main/articles/iot-hub/tutorial-x509-test-certs.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation exhibits a moderate Windows bias. Windows-specific instructions and tools (e.g., Git Bash, winpty) are mentioned first or exclusively in several places. The prerequisites and setup steps focus heavily on Windows environments, with Git Bash and OpenSSL guidance tailored to Windows users. Windows command examples are shown before Linux equivalents, and some instructions assume the use of Windows tools even when cross-platform alternatives exist.
Recommendations
  • Present Linux/macOS instructions and examples alongside or before Windows examples, rather than after.
  • Clarify that Git Bash is primarily a Windows workaround and suggest native Bash/terminal usage for Linux/macOS.
  • Remove or minimize references to Windows-specific tools (e.g., winpty) in cross-platform sections.
  • Explicitly describe installation and verification steps for OpenSSL on Linux/macOS, not just Windows.
  • Ensure parity in troubleshooting and environment setup guidance for non-Windows platforms.
  • Consider providing macOS-specific notes where relevant.
GitHub Create Pull Request
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
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. While the Azure CLI is used for resource setup (which is cross-platform), all code and device simulation examples are based on .NET/C# and use Windows-centric folder paths and conventions. There are no Linux/macOS-specific instructions, troubleshooting tips, or alternative language samples (e.g., Python, Node.js). The tutorial assumes familiarity with Windows tooling and does not mention Linux-specific considerations (such as package installation, file permissions, or alternative device simulation samples).
Recommendations
  • Add explicit instructions for running the .NET sample on Linux/macOS, including required dependencies and any platform-specific caveats.
  • Provide alternative device simulation samples in other languages (e.g., Python, Node.js) that are popular on Linux/macOS.
  • Include troubleshooting tips for common Linux/macOS issues (e.g., file permissions, installing Azure CLI, using Bash instead of PowerShell).
  • Clarify that all Azure CLI commands work on Linux/macOS and provide example terminal commands (e.g., Bash) where appropriate.
  • Mention cross-platform compatibility for all steps, and avoid Windows-centric folder structures and terminology.
GitHub Create Pull Request
IoT Hub How to manage devices and modules using twins ...docs/blob/main/articles/iot-hub/manage-device-twins.md
Low Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation includes several tips specifically for PowerShell users, such as escaping double quotes, but does not mention Linux/macOS shell equivalents (e.g., bash, zsh). Additionally, references to running Azure CLI in Windows Terminal and Cloud Shell are made before mentioning cross-platform compatibility, and no Linux/macOS-specific shell usage notes are provided. All CLI examples are generic, but the only shell-specific advice is for Windows/PowerShell users.
Recommendations
  • Add equivalent shell escaping advice for bash/zsh users (e.g., how to handle quotes in Linux/macOS shells).
  • Explicitly state that Azure CLI commands work on Linux/macOS and provide example commands for those platforms if there are differences.
  • Mention common Linux/macOS terminals (e.g., GNOME Terminal, iTerm2) alongside Windows Terminal when discussing where to run Cloud Shell.
  • Where PowerShell-specific tips are given, provide parity for bash/zsh users.
GitHub Create Pull Request
IoT Hub Register and connect an IoT device ...cs/blob/main/articles/iot-hub/create-connect-device.md
Low Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation mentions Windows-centric tools such as PowerShell and Visual Studio Code extensions as primary alternatives for managing device identities, with PowerShell listed first. While the main instructions use the Azure portal and Azure CLI (which are cross-platform), the 'Other tools' section prioritizes Windows tools and does not mention Linux-native options (e.g., Bash scripts, Linux desktop tools) or clarify CLI parity for Linux/macOS. There are no explicit Linux/macOS examples or recommendations, and Windows tools are referenced before REST API or other platform-neutral methods.
Recommendations
  • Add explicit examples or notes for Linux/macOS users, such as using Bash scripts or shell commands for device management.
  • Clarify that Azure CLI is fully supported on Linux/macOS and provide installation links for those platforms.
  • List REST API and cross-platform tools before Windows-specific tools like PowerShell.
  • If PowerShell is mentioned, note that PowerShell Core is available on Linux/macOS and provide usage examples for those platforms.
  • Include references to Linux desktop tools or open-source alternatives if available.
GitHub Create Pull Request
IoT Hub Create and delete routes and endpoints by using Azure Resource Manager ...-docs/blob/main/articles/iot-hub/how-to-routing-arm.md
Low Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI and PowerShell examples for deploying Resource Manager templates, but PowerShell (a Windows-centric tool) is given equal prominence to Azure CLI, and in some cases appears first. File path examples use backslashes (e.g., "my\path\to\template.json"), which are Windows-style and may confuse Linux/macOS users. There are no explicit Linux/macOS-specific instructions, nor is Bash or shell scripting mentioned. The Azure portal instructions are platform-neutral, but command-line sections show a mild Windows bias.
Recommendations
  • Show Azure CLI examples first, as it is cross-platform and preferred for Linux/macOS users.
  • Use forward slashes in file path examples or note that Linux/macOS users should use forward slashes.
  • Explicitly mention that Azure CLI works on Linux/macOS and provide Bash shell usage notes where relevant.
  • Consider adding a Bash script example for template deployment.
  • Clarify that PowerShell Core is available cross-platform, but most Linux/macOS users will use Azure CLI.
GitHub Create Pull Request
IoT Hub Understand Azure IoT Hub endpoints ...ob/main/articles/iot-hub/iot-hub-devguide-endpoints.md
Low Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page shows mild Windows bias, primarily in the example code for listing blobs in Azure Storage, which uses C# and the Microsoft.Azure.Storage library—a pattern most familiar and accessible to Windows users. Additionally, the instructions for assigning Cosmos DB roles mention Azure CLI and Azure PowerShell, but do not provide explicit Linux/macOS command examples or clarify cross-platform usage. No Linux-specific tools, SDKs, or code samples are provided, and Windows-centric technologies are implicitly prioritized.
Recommendations
  • Provide equivalent code samples using Python (with Azure SDK), Bash, or other cross-platform languages for tasks like listing blobs in Azure Storage.
  • Explicitly mention that Azure CLI is cross-platform and provide example commands for Linux/macOS users, especially for role assignment in Cosmos DB.
  • Include references to Linux/macOS compatible SDKs and tools where relevant.
  • Balance example order by alternating or leading with cross-platform or Linux-friendly examples.
  • Clarify that PowerShell is available on Linux/macOS, or offer Bash alternatives where possible.
GitHub Create Pull Request
IoT Hub Upload files from your device to the cloud with Azure IoT Hub ...-docs/blob/main/articles/iot-hub/how-to-file-upload.md
Low Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation mentions Azure PowerShell as a configuration option for file upload before listing Linux-friendly alternatives like Azure CLI and the Azure portal. PowerShell is primarily a Windows tool, and its mention alongside CLI and portal may suggest a Windows-centric approach. However, the main SDK usage examples are language-based and do not show explicit OS bias.
Recommendations
  • List Azure CLI before Azure PowerShell when describing configuration options, as CLI is cross-platform.
  • Explicitly state that Azure CLI and Azure portal are cross-platform and suitable for Linux/macOS users.
  • If PowerShell is mentioned, clarify that Azure PowerShell is available on Linux/macOS, or provide links to installation instructions for non-Windows platforms.
  • Consider adding a note or section for Linux/macOS users to highlight parity and any OS-specific considerations.
GitHub Create Pull Request
IoT Hub Azure IoT Hub IP filters ...ocs/blob/main/articles/iot-hub/iot-hub-ip-filtering.md
Low Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for managing IP filter rules, but the PowerShell section is given equal prominence to CLI, and no Linux/macOS-specific shell examples (e.g., Bash) are provided. The screenshots and portal instructions are platform-neutral, but the command-line guidance may feel Windows-centric due to the inclusion of PowerShell and lack of Linux/macOS shell examples.
Recommendations
  • Add explicit Bash or shell script examples for Linux/macOS users, especially for tasks like parsing or manipulating the JSON output from Azure CLI.
  • Clarify that Azure CLI commands work cross-platform and provide tips for Linux/macOS environments (e.g., using jq for JSON parsing).
  • Consider reordering sections so that Azure CLI (which is cross-platform) appears before PowerShell, or explicitly state platform applicability for each method.
  • Mention that PowerShell Core is available on Linux/macOS, if relevant, and provide installation guidance or links.
GitHub Create Pull Request
IoT Hub Managing public network access for Azure IoT Hub ...main/articles/iot-hub/iot-hub-public-network-access.md
Low Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for checking IoT Hub access, but PowerShell is shown alongside CLI without explicit Linux/macOS shell examples. The troubleshooting and workflow instructions reference the Azure portal and Cloud Shell, which are cross-platform, but command-line examples do not clarify Linux/macOS usage or show bash-specific patterns. There is a subtle Windows-first bias in the ordering and inclusion of PowerShell commands, and no explicit Linux/macOS shell commands or screenshots.
Recommendations
  • Add explicit bash/zsh shell examples for Linux/macOS users, especially for Azure CLI commands.
  • Clarify that Azure CLI commands work cross-platform and can be run in bash, zsh, or other shells.
  • If showing PowerShell, also show equivalent bash commands and note platform compatibility.
  • Include screenshots or instructions for Linux/macOS environments where relevant.
  • State platform compatibility for each command example (e.g., 'This command works in bash, PowerShell, etc.')
GitHub Create Pull Request
IoT Hub X.509 certificates | Microsoft Docs ...b/main/articles/iot-hub/reference-x509-certificates.md
Low Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation page is largely cross-platform, with most examples using OpenSSL and Bash, which are standard on Linux/macOS. However, in the 'Verify certificate manually after upload' section, the PowerShell script is mentioned first as a method to generate a verification certificate, and Windows tooling (PowerShell) is given equal prominence to Bash/OpenSSL. The reference to 'the PowerShell script supplied by Microsoft' and the ordering of Windows tools before Bash/OpenSSL indicate a mild Windows bias.
Recommendations
  • List Bash/OpenSSL methods before PowerShell to reflect the prevalence of Linux/macOS in IoT and cloud development.
  • Clarify that all methods (PowerShell, Bash, OpenSSL) are equally supported and available on their respective platforms.
  • Explicitly mention platform compatibility for each script/tool (e.g., 'PowerShell (Windows), Bash (Linux/macOS)').
  • Provide links or instructions for installing Bash/OpenSSL on Windows, and PowerShell on Linux/macOS, if relevant.
  • Ensure parity in example depth and troubleshooting for both Windows and Linux/macOS users.
GitHub Create Pull Request
IoT Hub Overview of Azure IoT Hub message enrichments ...ticles/iot-hub/iot-hub-message-enrichments-overview.md
Low Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 2 bias types
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 parity. PowerShell is a Windows-centric tool, and its mention before any Linux-specific alternatives (such as Bash scripts or REST API usage) may suggest a Windows-first approach. However, Azure CLI is cross-platform, and no examples are given that are exclusive to Windows or PowerShell.
Recommendations
  • Explicitly state that Azure CLI is cross-platform and supported on Linux/macOS.
  • Provide REST API or SDK examples for configuring enrichments, which are platform-neutral.
  • Clarify that PowerShell is available on Linux/macOS, or provide Bash script examples for parity.
  • Ensure that any command-line examples are shown for both Azure CLI and PowerShell, with CLI (Linux-friendly) examples shown first.
GitHub Create Pull Request
IoT Hub Quickstart - Send telemetry to Azure IoT Hub (CLI) quickstart ...main/articles/iot-hub/quickstart-send-telemetry-cli.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page shows some Windows bias, primarily in the way it references Windows tools and environments first (e.g., Windows Terminal), mentions PowerShell as an alternative to Bash, and provides PowerShell-specific command syntax. While Bash is used for most examples and the Azure Cloud Shell is cross-platform, there are subtle indications that Windows users are prioritized, and Linux/macOS-specific considerations are not addressed in detail. There are no explicit Linux/macOS examples or troubleshooting tips, and Windows tools are mentioned before their Linux equivalents.
Recommendations
  • Mention Linux/macOS terminals (e.g., GNOME Terminal, iTerm2) alongside Windows Terminal when discussing local CLI usage.
  • Provide troubleshooting notes for Linux/macOS users, such as common permission issues or shell differences.
  • Ensure that Bash examples are shown first, and PowerShell examples are clearly marked as alternatives.
  • Add explicit statements confirming full support for Linux/macOS environments.
  • Include links to platform-specific installation instructions for Azure CLI (e.g., apt, yum, Homebrew).
GitHub Create Pull Request
IoT Hub Upload files from your device to the cloud with Azure IoT Hub ...-docs/blob/main/articles/iot-hub/how-to-file-upload.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation mentions Azure PowerShell as a configuration option for file upload before listing Linux-friendly alternatives like Azure CLI and the Azure portal. This ordering and inclusion of PowerShell (primarily a Windows tool) may signal a Windows-first bias. However, Azure CLI and portal are also listed, which are cross-platform. No code examples are shown, so it's unclear if further bias exists in the included SDK sample links.
Recommendations
  • List Azure CLI before Azure PowerShell when presenting configuration options, as CLI is cross-platform.
  • Explicitly state that both CLI and PowerShell are available on Windows, Linux, and macOS, and provide links to installation guides for each platform.
  • Ensure that any referenced SDK samples include Linux/macOS instructions or notes where platform-specific steps are required.
  • Add a note clarifying that all configuration steps can be performed on Linux/macOS, not just Windows.
GitHub Create Pull Request
IoT Hub Understand Azure IoT Hub endpoints ...ob/main/articles/iot-hub/iot-hub-devguide-endpoints.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates mild Windows bias. The only code example provided uses the Azure .NET SDK (C#), which is most commonly used on Windows. Additionally, when discussing role assignment for Cosmos DB, the documentation mentions Azure CLI and Azure PowerShell, but lists PowerShell first and does not provide explicit Linux/macOS command examples. There is no mention of Linux-specific tools or patterns, and no Bash or cross-platform code samples are given.
Recommendations
  • Include code examples using cross-platform languages (e.g., Python, Node.js) and SDKs.
  • Provide explicit Bash/Azure CLI command examples for tasks like role assignment, especially where PowerShell is mentioned.
  • Clarify that Azure CLI is available on Linux/macOS and provide usage instructions for those platforms.
  • When listing tools, alternate or balance the order between Windows and Linux/macOS options.
  • Add notes or links for Linux/macOS users where platform-specific differences exist.
GitHub Create Pull Request
IoT Hub Register and connect an IoT device ...cs/blob/main/articles/iot-hub/create-connect-device.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation references PowerShell commands and Visual Studio Code as management tools, both of which are commonly associated with Windows environments. PowerShell is mentioned before REST API, and no Linux-specific tools (such as Bash scripts or Linux-native management utilities) are highlighted. However, the main procedural examples use the Azure CLI, which is cross-platform, and there are no explicit Windows-only instructions or screenshots.
Recommendations
  • Add explicit mentions and examples of using Azure CLI on Linux/macOS, including any platform-specific considerations.
  • Include references to Linux-native tools or workflows, such as Bash scripts for device management.
  • Clarify that PowerShell Core is available cross-platform, or provide equivalent Bash examples where possible.
  • Ensure screenshots and instructions do not imply Windows-only environments (e.g., avoid showing only Windows UI elements or file paths).
  • Consider listing REST API and CLI options before PowerShell in 'Other tools' to avoid Windows-first ordering.
GitHub Create Pull Request
IoT Hub How to manage devices and modules using twins ...docs/blob/main/articles/iot-hub/manage-device-twins.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page provides examples and instructions primarily for the Azure portal and Azure CLI, which are cross-platform. However, there are multiple explicit tips for PowerShell users regarding escaping double quotes, and references to running Azure CLI in Windows Terminal are given before mentioning other platforms. No Linux-specific shell examples (e.g., bash) or tips are provided, and PowerShell-specific guidance may be confusing or irrelevant for Linux/macOS users.
Recommendations
  • Add tips for Linux/macOS users, such as how to escape quotes in bash/zsh.
  • Mention that Azure CLI works natively on Linux/macOS and provide examples of running commands in bash/zsh.
  • Avoid referencing Windows Terminal as the primary example for running Cloud Shell; mention alternatives like macOS Terminal or GNOME Terminal.
  • Where PowerShell escaping is discussed, also provide equivalent bash/zsh escaping guidance.
GitHub Create Pull Request
IoT Hub Monitor Azure IoT Hub ...ure-docs/blob/main/articles/iot-hub/monitor-iot-hub.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Windows Examples Missing Linux Example
Summary
The documentation page exhibits mild Windows bias in the SDK version examples, which exclusively show Windows platforms (e.g., Windows_NT, Microsoft Windows) in the emitted sdkVersion property strings. There are no Linux/macOS platform examples, and the only direct code sample referencing platform details uses Windows. No PowerShell or Windows-specific tools are mentioned, and the main workflows (Azure portal, Kusto queries) are platform-agnostic. However, the lack of Linux/macOS parity in SDK version examples may cause minor friction for non-Windows users.
Recommendations
  • Add examples of sdkVersion property strings for devices running on Linux and macOS platforms, using the same SDKs.
  • Explicitly state that the SDK version property will reflect the underlying OS, and provide sample outputs for Linux (e.g., Ubuntu, CentOS) and macOS.
  • Ensure that any platform-specific instructions or screenshots are balanced with Linux/macOS equivalents if relevant.
  • Where platform is referenced in code or output, clarify that the documentation applies equally to non-Windows environments.
GitHub Create Pull Request
IoT Hub X.509 certificates | Microsoft Docs ...b/main/articles/iot-hub/reference-x509-certificates.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides both Bash/OpenSSL and PowerShell examples for certificate generation and verification, but the PowerShell method is listed first when describing ways to generate a verification certificate. This ordering may subtly prioritize Windows users. Additionally, the explicit mention of a Microsoft-supplied PowerShell script, with less detail about Linux/macOS alternatives, could be interpreted as a mild bias toward Windows tooling.
Recommendations
  • List Bash/OpenSSL and PowerShell methods in parallel or alternate the order to avoid implicit prioritization.
  • Provide equal detail and emphasis for both Linux/macOS and Windows workflows, including links and troubleshooting notes for each.
  • Explicitly mention cross-platform compatibility for all scripts and tools.
  • Include a table summarizing available tools/scripts for certificate management across Windows, Linux, and macOS.
GitHub Create Pull Request
IoT Hub Register and connect an IoT device ...cs/blob/main/articles/iot-hub/create-connect-device.md
Low Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation references Windows-centric tools such as PowerShell and Visual Studio Code extensions, and mentions PowerShell commands before REST API alternatives. There is a slight Windows-first bias in tool recommendations, but the main workflow examples use the Azure CLI, which is cross-platform. No critical steps are Windows-only, but Windows tools are highlighted more prominently than Linux-native alternatives.
Recommendations
  • Add explicit mention of Bash scripting and Linux shell alternatives alongside PowerShell for device management.
  • Clarify that Azure CLI commands work on Linux/macOS and provide example shell environments where appropriate.
  • If referencing Visual Studio Code, note its cross-platform availability and provide links to Linux/macOS installation guides.
  • List REST API and CLI options before PowerShell in 'Other tools' to avoid Windows-first ordering.
  • Consider including example workflows using Linux-native tools or scripts for common device management tasks.
GitHub Create Pull Request
IoT Hub How to manage devices and modules using twins ...docs/blob/main/articles/iot-hub/manage-device-twins.md
Low Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page 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 appear before mentioning other platforms. No Linux/macOS-specific examples or considerations are provided, and the PowerShell tip is repeated in multiple sections.
Recommendations
  • Add tips for common Linux/macOS shell quoting issues (e.g., single vs double quotes, escaping).
  • Mention that Azure CLI commands work identically on Linux/macOS and provide explicit confirmation.
  • Include examples or screenshots from Linux/macOS terminals (e.g., bash, zsh) alongside Windows/PowerShell.
  • When referencing terminal environments, mention cross-platform options first (e.g., Azure Cloud Shell, bash) before Windows-specific tools like Windows Terminal.
GitHub Create Pull Request
IoT Hub Upload files from your device to the cloud with Azure IoT Hub ...-docs/blob/main/articles/iot-hub/how-to-file-upload.md
Low Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation references Azure PowerShell as a configuration method alongside Azure CLI and Portal, and lists PowerShell after CLI in the prerequisites. There are no explicit Linux/macOS examples or tools mentioned, and no indication of parity for Linux users in configuration steps. However, programming language sections are not OS-specific and do not show Windows bias.
Recommendations
  • Explicitly mention Linux/macOS compatibility for configuration steps, especially for Azure CLI.
  • Provide example commands for both Azure CLI (cross-platform) and PowerShell, clarifying which is recommended for Linux/macOS users.
  • Add notes or links for Linux/macOS users on installing and using Azure CLI.
  • Ensure referenced SDK samples include instructions or scripts for Linux/macOS environments.
GitHub Create Pull Request
IoT Hub Configure file upload in IoT Hub ...main/articles/iot-hub/iot-hub-configure-file-upload.md
Low Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation presents configuration steps for IoT Hub file uploads using three pivots: Azure portal, Azure CLI, and Azure PowerShell. While Azure CLI is cross-platform, the explicit inclusion of Azure PowerShell as a primary method and the use of the term 'PowerShell' may signal a Windows-centric approach. The ordering of pivots (portal, CLI, PowerShell) is neutral, but the presence of PowerShell as a top-level pivot can be interpreted as Windows bias, especially if the PowerShell instructions are not clarified to work on Linux/macOS. There are no explicit Linux/macOS examples, nor is there mention of bash or shell scripting alternatives.
Recommendations
  • Clarify that Azure CLI and Azure PowerShell are available on Linux/macOS, and provide installation links for non-Windows platforms.
  • Add explicit bash or shell script examples for Linux/macOS users, especially if any steps differ from Windows.
  • If PowerShell is required, note that PowerShell Core is cross-platform and provide instructions for installation on Linux/macOS.
  • Consider adding a 'Linux/macOS' pivot or section to highlight platform-specific considerations.
GitHub Create Pull Request
IoT Hub Understand Azure IoT Hub endpoints ...ob/main/articles/iot-hub/iot-hub-devguide-endpoints.md
Low Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page shows mild Windows bias. The only code example uses the Azure .NET SDK (C#), which is most commonly used on Windows and does not mention cross-platform usage or alternatives. The instructions for assigning Cosmos DB roles explicitly mention Azure CLI and Azure PowerShell, but do not clarify that Azure CLI is cross-platform or provide Linux/macOS-specific guidance. There are no Linux/macOS-specific examples or explicit parity statements.
Recommendations
  • Add explicit Linux/macOS examples for SDK usage, such as Python or Node.js code snippets.
  • Clarify that Azure CLI is cross-platform and provide example commands for Linux/macOS environments.
  • When mentioning Azure PowerShell, also mention Bash or other common Linux shells if relevant.
  • Provide guidance or links for Linux/macOS users where Windows-centric tools are referenced.
  • Ensure that examples and instructions are not implicitly Windows-first by varying the order or including cross-platform notes.
GitHub Create Pull Request
IoT Hub Monitor Azure IoT Hub ...ure-docs/blob/main/articles/iot-hub/monitor-iot-hub.md
Low Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation page is generally cross-platform and avoids explicit OS-specific instructions or tooling. However, there is a subtle Windows bias in the SDK version examples, which exclusively show Windows environments (Windows_NT, Microsoft Windows) for Node.js and .NET SDKs. Additionally, the only external code sample referenced for Event Hubs is a .NET (Windows-centric) sample, with no mention of Linux/macOS equivalents or cross-platform SDKs. There are no PowerShell-heavy sections, but Windows is implicitly prioritized in examples and references.
Recommendations
  • Include SDK version examples for Linux and macOS environments alongside Windows in the 'SDK version in IoT Hub logs' section.
  • Reference Event Hubs client samples for other languages (e.g., Python, Java, Node.js) and note their cross-platform compatibility.
  • When showing screenshots or portal instructions, clarify that the Azure portal is accessible from any OS/browser.
  • Explicitly mention that all SDKs and tools are supported on Linux/macOS, and provide links to relevant documentation or samples.
  • Ensure that any code or tooling references are not Windows-centric, or provide parity for Linux/macOS users.
GitHub Create Pull Request
← Previous Page 2 of 3 Next →