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 1-25 of 54 flagged pages
IoT Hub
Get Started with ADR and Certificate Management in IoT Hub (Preview)
...main/articles/iot-hub/iot-hub-device-registry-setup.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation mentions PowerShell scripts as a deployment method, explicitly noting they are 'Windows only', while the Azure CLI method is presented as cross-platform. The deployment method table lists Azure CLI first, followed by PowerShell, but PowerShell is highlighted as Windows-specific. No Linux/macOS shell script or Bash example is provided as an alternative to PowerShell automation. All command-line examples use Azure CLI, which is cross-platform, but the only script automation option is PowerShell (Windows).
Recommendations
- Provide a Bash or shell script example for Linux/macOS users to automate the IoT Hub, DPS, and ADR setup, paralleling the PowerShell script.
- Explicitly state that Azure CLI is supported on Windows, Linux, and macOS to reassure non-Windows users.
- If script automation is important, offer parity by linking to or including a Linux/macOS shell script.
- Consider renaming the 'script' pivot to clarify platform support (e.g., 'PowerShell (Windows only)' and 'Bash (Linux/macOS)').
Create Pull Request
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 →
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 the use of Windows tools (Visual Studio, NuGet GUI), with no mention of Linux/macOS equivalents (e.g., VS Code, CLI tools, .NET Core cross-platform usage). There are no Linux/macOS-specific instructions or examples, and Windows development patterns are presented exclusively and first.
Recommendations
- Add instructions for creating and running the .NET console app using cross-platform tools like VS Code or the .NET CLI.
- Include Linux/macOS-specific setup steps (e.g., installing .NET SDK, using terminal commands for NuGet package installation).
- Provide code snippets and screenshots for Linux/macOS environments.
- Clarify that the .NET SDK and Azure IoT libraries are cross-platform and provide guidance for non-Windows users.
- Mention alternative editors (VS Code, JetBrains Rider) and package managers (dotnet CLI) in addition to Visual Studio.
IoT Hub
Get Started with ADR and Certificate Management in IoT Hub (Preview)
...main/articles/iot-hub/iot-hub-device-registry-setup.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation page displays a Windows bias by explicitly highlighting PowerShell as a deployment method, labeling it as 'Windows only', and mentioning it alongside Azure CLI as a primary option. The PowerShell script method is presented in the deployment table before any mention of Linux/macOS shell scripting alternatives, and there is no explicit mention of Bash or Linux/macOS shell script equivalents. While the Azure CLI is cross-platform, the PowerShell method's prominence and lack of Linux script parity suggest a moderate Windows bias.
Recommendations
- Add explicit Bash or shell script examples for Linux/macOS users alongside PowerShell scripts.
- Clarify that Azure CLI is cross-platform and provide instructions for installation and usage on Linux/macOS.
- If scripts are provided, ensure both PowerShell and Bash versions are available and referenced equally.
- Avoid labeling deployment methods as 'Windows only' without offering Linux/macOS alternatives.
- Consider reordering examples so that cross-platform methods (Azure CLI, Bash) are presented before Windows-specific ones.
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation page exhibits a moderate Windows bias in the .NET/C# section, where Windows/PowerShell/ETW instructions and tools are presented first and in greater detail, with explicit mention of PowerShell scripts and Event Tracing for Windows (ETW). The Linux equivalent (dotnet-trace) is described after Windows, but is covered adequately. Other SDKs (C, Java, JavaScript, Python, Embedded C) provide platform-neutral or cross-platform instructions, with no notable Windows bias.
Recommendations
- Present Linux and Windows instructions side-by-side or in parallel sections, rather than Windows-first.
- Include explicit mention of macOS support (if applicable) for .NET tracing tools.
- Provide parity in detail and troubleshooting tips for Linux/macOS users, matching the depth given to Windows/PowerShell/ETW.
- Consider referencing cross-platform tracing tools where possible, or clarify platform limitations.
- Add a summary table comparing trace collection methods across platforms for .NET.
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation presents configuration instructions via three pivots: Azure portal, Azure CLI, and Azure PowerShell. The inclusion of Azure PowerShell as a primary method introduces a Windows bias, as PowerShell is traditionally associated with Windows environments. The order of pivots (portal, CLI, PowerShell) also places PowerShell before any explicit mention of Linux/macOS alternatives, and there is no mention of Bash or Linux-specific tooling.
Recommendations
- Clarify that Azure CLI is fully supported on Linux/macOS and provide explicit Bash examples where relevant.
- Add a note indicating that PowerShell Core is cross-platform, or provide Bash equivalents for all PowerShell commands.
- Reorder pivots or add a Linux/macOS-specific section to highlight parity and reduce perceived Windows-first bias.
- Explicitly mention platform compatibility for each method (portal, CLI, PowerShell) at the start of the documentation.
IoT Hub
Monitor IoT messages with distributed tracing (preview)
...b/main/articles/iot-hub/iot-hub-distributed-tracing.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a notable Windows bias, especially in the 'Run a sample application' section. Instructions for building and running the sample application are detailed for Windows (Visual Studio, .exe files, Windows SDK), while Linux/macOS equivalents are only referenced via external links. Windows tools and patterns (Visual Studio, command prompt, .exe) are mentioned exclusively or before alternatives, and Linux build/run steps are missing from the main flow.
Recommendations
- Add explicit Linux/macOS build and run instructions inline, including common tools (e.g., gcc/clang, make, cmake) and sample terminal commands.
- Provide example output for Linux/macOS environments, not just Windows (e.g., .out files, Linux shell prompts).
- Mention and show how to use cross-platform editors (e.g., VS Code, vim) and terminals.
- Ensure parity in troubleshooting steps (e.g., compiler errors on Linux/macOS).
- List Linux/macOS prerequisites (e.g., apt-get install cmake, build-essential) alongside Windows prerequisites.
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 →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation demonstrates a mild Windows bias. While Azure CLI is used for resource setup (which is cross-platform), the only device simulation example is a .NET/C# console app, with instructions and commands (dotnet restore/run) that are most familiar to Windows users. There are no Linux/macOS-specific instructions, troubleshooting tips, or alternative device simulation examples (e.g., Python). Screenshots and portal navigation are Windows-centric, and there is no mention of Linux-specific issues or parity. PowerShell is referenced as an alternative to CLI, but no Bash or Linux shell examples are provided.
Recommendations
- Add explicit instructions for running the simulated device app on Linux/macOS, including any required dependencies or troubleshooting tips.
- Provide a cross-platform device simulation example (e.g., Python sample) alongside the .NET/C# example.
- Include Linux/macOS-specific notes for Azure CLI usage, such as shell syntax differences or environment setup.
- Add screenshots or descriptions that reflect Linux/macOS environments where relevant.
- Mention Bash or Linux shell alternatives to PowerShell for resource setup.
IoT Hub
Tutorial - Create and upload certificates for testing
...blob/main/articles/iot-hub/tutorial-x509-test-certs.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation exhibits a moderate Windows bias. Windows-specific instructions and tools (Git Bash, winpty, references to Windows installation paths) are presented first or exclusively in key sections, and the use of PowerShell is mentioned in the context of provided scripts. Linux instructions are present and generally equivalent, but Windows-centric patterns (such as recommending Git Bash for OpenSSL on Windows, and using winpty) are emphasized, and Linux/macOS users may need to adapt steps or ignore Windows-specific advice.
Recommendations
- Present Linux/macOS instructions first or in parallel with Windows instructions, rather than defaulting to Windows-first.
- Clarify that Git Bash is a workaround for Windows users, and provide explicit instructions for native Linux/macOS terminals.
- When mentioning provided scripts, ensure parity by referencing both Bash and PowerShell equally, and clarify their applicability to each platform.
- Avoid recommending Windows-specific tools (like winpty or Git Bash) in general prerequisites; instead, provide platform-specific guidance in dedicated sections.
- Add troubleshooting notes for common Linux/macOS issues (e.g., OpenSSL config file locations, permissions).
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 →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page is heavily oriented toward Windows development environments, specifically Visual Studio and .NET. All code samples, setup instructions, and screenshots reference Visual Studio and Windows workflows. There are no examples or guidance for Linux/macOS users, such as using VS Code, .NET CLI, or alternative editors. The only non-Windows-specific mention is the use of openssl for certificate generation, which is cross-platform, but the main development workflow is Windows-centric.
Recommendations
- Add instructions for creating and running the .NET console app using the .NET CLI, which works on Linux and macOS.
- Include examples of setting up the development environment with VS Code or other cross-platform editors.
- Provide screenshots and step-by-step guidance for Linux/macOS users, including package installation and running the app from the terminal.
- Clarify that the .NET SDK and Azure IoT Hub features are cross-platform, and explicitly mention Linux/macOS compatibility.
- Reorder examples or provide parallel instructions so Linux/macOS users are not secondary.
IoT Hub
Get Started with ADR and Certificate Management in IoT Hub (Preview)
...main/articles/iot-hub/iot-hub-device-registry-setup.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Powershell Heavy
Summary
The documentation page displays moderate Windows bias, primarily through explicit mention of PowerShell as a deployment method ('Windows only') and by listing PowerShell before Linux alternatives. The deployment method table highlights PowerShell as a distinct option, while Linux/macOS users are directed to use Azure CLI or scripts, but no Bash or shell script examples are provided. The page refers to Windows-specific tooling and patterns, with no equivalent Linux/macOS scripting guidance.
Recommendations
- Add explicit Bash or shell script examples for Linux/macOS users alongside PowerShell.
- Clarify that Azure CLI is cross-platform and provide usage notes for Linux/macOS environments.
- Reorder the deployment method table to list cross-platform options first, or present them in parallel.
- If scripts are referenced, ensure both PowerShell and Bash versions are available and linked.
- Where 'Windows only' is mentioned, provide equivalent instructions for Linux/macOS.
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 to the CLI, and no Linux/macOS-specific shell examples (e.g., Bash, curl for REST) are provided. The screenshots and portal instructions are platform-neutral, but the command-line automation examples are Windows-centric due to the inclusion of PowerShell and lack of Linux shell or REST examples.
Recommendations
- Add Bash shell examples for Linux/macOS users, especially for REST API usage (e.g., using curl).
- Clarify that Azure CLI works cross-platform and provide explicit Linux/macOS usage notes if any differences exist.
- Consider showing Azure CLI examples before PowerShell, or at least note that CLI is cross-platform.
- Provide REST API examples using curl or httpie for Linux/macOS users.
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation page exhibits a moderate Windows bias in the .NET/C# section: Windows/PowerShell/ETW instructions are presented first and in greater detail, with explicit mention of PowerShell scripts and Windows-specific tracing tools. The Linux instructions are present and reasonably detailed, but appear after the Windows section and use a different tool (dotnet-trace). Other language sections (C, Java, JavaScript, Python, Embedded C) are platform-neutral or provide OS-agnostic examples.
Recommendations
- Present Linux and Windows instructions in parallel or with equal prominence, rather than Windows first.
- Explicitly mention macOS support and provide examples if applicable, especially for .NET tracing.
- Where possible, use cross-platform tools or note platform-specific differences clearly.
- Add a summary table comparing tracing approaches/tools for Windows, Linux, and macOS for .NET.
- Ensure that Linux/macOS users are not required to infer steps from Windows-only instructions.
IoT Hub
Create and delete routes and endpoints by using Azure Resource Manager
...-docs/blob/main/articles/iot-hub/how-to-routing-arm.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation provides deployment instructions using both Azure CLI and PowerShell, but PowerShell examples are given equal prominence to CLI, and file path examples use Windows-style backslashes (e.g., "my\path\to\template.json"). There is no mention of Linux/macOS-specific considerations, such as file path formats or shell differences. The Azure portal and Cloud Shell are platform-neutral, but the local deployment section could confuse Linux/macOS users due to Windows-centric patterns.
Recommendations
- Show file path examples using both Windows (backslash) and Linux/macOS (forward slash) formats, or use platform-neutral examples.
- Explicitly state that Azure CLI works on Linux/macOS and show examples with typical Linux/macOS shell syntax.
- Mention that PowerShell is available cross-platform, but clarify that Bash or other shells can be used on Linux/macOS.
- Consider listing Azure CLI examples before PowerShell, as CLI is more widely used across platforms.
- Add a note or section for Linux/macOS users highlighting any differences or considerations.
IoT Hub
Monitor IoT messages with distributed tracing (preview)
...b/main/articles/iot-hub/iot-hub-distributed-tracing.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page exhibits a moderate Windows bias, especially in the 'Run a sample application' section. Instructions for building and running the sample application are written specifically for Windows, referencing Visual Studio, Windows command prompts, and Windows-specific build outputs. Linux/macOS build instructions are mentioned only as a link, with no concrete steps or examples provided. Windows tools (Visual Studio, command prompt) are referenced exclusively in the main instructions, while Linux alternatives are omitted.
Recommendations
- Add explicit Linux/macOS build and run instructions, including required packages (e.g., gcc, make, cmake) and example shell commands.
- Provide sample output and troubleshooting steps for Linux/macOS environments.
- Include screenshots or terminal output from Linux/macOS where appropriate.
- Mention cross-platform editors (e.g., VS Code) in build steps, not just Visual Studio.
- Ensure that all code snippets and build commands have platform-agnostic alternatives or are clearly marked as platform-specific.
IoT Hub
Overview of Azure IoT Hub message enrichments
...ticles/iot-hub/iot-hub-message-enrichments-overview.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Windows First
Summary
The documentation lists Azure PowerShell as a primary method for configuring message enrichments, alongside Azure CLI and Portal. PowerShell is a Windows-centric tool, and its mention (with a direct link) may signal a Windows bias, especially since no Linux/macOS-specific alternatives (like Bash scripts or REST API examples) are provided. The ordering of methods (Portal, CLI, PowerShell) also places the Windows tool before any explicit mention of Linux/macOS compatibility.
Recommendations
- Add explicit examples for Linux/macOS users, such as Bash scripts using Azure CLI or REST API calls.
- Clarify that Azure CLI is cross-platform and highlight its use for Linux/macOS users.
- Consider providing REST API examples for advanced users who may not use CLI or PowerShell.
- Reorder the methods to list cross-platform tools (CLI, REST API) before Windows-specific tools (PowerShell).
- Add a note clarifying platform compatibility for each method.
IoT Hub
Managing public network access for Azure IoT Hub
...main/articles/iot-hub/iot-hub-public-network-access.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for checking IoT Hub access, but the PowerShell example is given equal prominence despite PowerShell being primarily a Windows tool. There are no explicit Linux/macOS-specific instructions or troubleshooting steps, and the documentation does not mention platform differences or alternative shells. The Azure portal instructions are platform-neutral, but command-line examples and troubleshooting focus on tools most familiar to Windows users.
Recommendations
- Explicitly state that Azure CLI works on Linux/macOS and provide examples of running CLI commands in bash/zsh.
- Clarify that PowerShell is available cross-platform, or note its Windows origins.
- Add troubleshooting steps for Linux/macOS users, such as checking firewall rules or proxy settings specific to those platforms.
- Include screenshots or instructions for accessing the Azure portal from Linux/macOS browsers if there are differences.
- Ensure that CLI examples are shown before PowerShell, or at least clarify platform applicability.
IoT Hub
Understanding the IP address of your IoT hub | Microsoft Docs
...main/articles/iot-hub/iot-hub-understand-ip-address.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation references Azure CLI and PowerShell as clients that may be blocked by firewall rules, but does not mention Linux/macOS equivalents or provide examples for those platforms. PowerShell is a Windows-centric tool, and its mention without alternatives or parity examples introduces a Windows bias. No Linux-specific tools or workflows are discussed, and examples for configuring firewalls or automating service tag retrieval are generic, lacking platform-specific guidance for Linux/macOS users.
Recommendations
- Explicitly mention cross-platform tools such as Azure CLI (which runs on Linux/macOS) alongside PowerShell.
- Provide example commands for both Windows (PowerShell) and Linux/macOS (bash/Azure CLI).
- Clarify that Azure CLI is available on all major platforms and provide links to installation guides for Linux/macOS.
- Include Linux/macOS-specific firewall configuration examples (e.g., using iptables, ufw, or firewalld).
- Avoid implying that PowerShell is the only or primary method for automation or management.
IoT Hub
Tutorial - Create and upload certificates for testing
...blob/main/articles/iot-hub/tutorial-x509-test-certs.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation demonstrates a moderate Windows bias. Windows-specific tools (Git Bash, winpty) are mentioned and recommended first, and Windows instructions are consistently presented before Linux equivalents. The prerequisites and instructions assume a Windows environment, referencing Git Bash as the primary shell and discussing OpenSSL installation in the context of Windows. PowerShell scripts are referenced before Bash scripts, and the use of winpty for OpenSSL commands is highlighted for Windows users. Linux instructions are present and functional, but are secondary in presentation and context.
Recommendations
- Present Linux/macOS instructions before or alongside Windows instructions, not after.
- Explicitly mention Linux/macOS shell environments (e.g., bash, zsh, terminal) in prerequisites and instructions.
- Clarify that OpenSSL is typically pre-installed on most Linux distributions and macOS, and provide installation instructions for those platforms.
- Avoid recommending Git Bash as the primary shell for all users; suggest native terminals for Linux/macOS.
- Reference Bash scripts before or alongside PowerShell scripts, and clarify their cross-platform compatibility.
- Remove or minimize Windows-specific command wrappers (e.g., winpty) in the main instructions, or provide equivalent context for Linux/macOS users.
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 →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation is generally cross-platform in its use of Azure CLI and .NET Core, 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 language samples. All command-line examples use Azure CLI, which is cross-platform, but there is no explicit mention of Linux/macOS shell usage or troubleshooting. The documentation refers to 'local terminal window' generically, but screenshots and instructions are portal-centric and do not highlight Linux/macOS specifics. There is no PowerShell bias or exclusive use of Windows tools, but the tutorial assumes familiarity with C#/.NET and does not offer parity for other platforms or languages.
Recommendations
- Add explicit instructions and troubleshooting notes for Linux/macOS users (e.g., file path differences, shell commands).
- Provide alternative simulated device samples in other languages (e.g., Python, Node.js) that are popular on Linux/macOS.
- Include screenshots or notes showing the Azure portal experience on non-Windows platforms.
- Clarify that Azure CLI commands work on Bash/zsh and provide example shell usage for Linux/macOS.
- Mention prerequisites for Linux/macOS (e.g., how to install .NET Core SDK, Azure CLI on those platforms).
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation page shows a moderate Windows bias in the C#/.NET section, where Windows/PowerShell/ETW instructions are presented first and in greater detail, with explicit references to Windows-specific tools and scripts. Linux instructions are present and reasonably complete, but appear after the Windows section. Other SDKs (C, Java, JavaScript, Python, Embedded C) provide OS-neutral or Linux-friendly instructions, but the C#/.NET section prioritizes Windows workflows.
Recommendations
- Present Linux and Windows instructions in parallel or with equal prominence in the C#/.NET section.
- Explicitly mention Linux alternatives before or alongside Windows tools/scripts.
- Ensure that Linux/macOS users are not required to adapt Windows-specific instructions (e.g., PowerShell scripts) and provide direct Linux equivalents.
- Add a note at the start of the C#/.NET section clarifying OS support and parity.
- Consider providing macOS-specific instructions if applicable.
IoT Hub
Create and delete routes and endpoints by using Azure Resource Manager
...-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 shown as a first-class option throughout, and file path examples use Windows-style backslashes. There are no Linux/macOS-specific instructions or examples, and the PowerShell examples may be less relevant for non-Windows users. The use of Azure Cloud Shell mitigates some bias, but overall, the documentation assumes familiarity with Windows tools and conventions.
Recommendations
- Add explicit Linux/macOS instructions, such as using forward slashes in file paths for Azure CLI examples.
- Clarify that Azure CLI works cross-platform and is recommended for Linux/macOS users.
- Consider showing Azure CLI examples before PowerShell, or at least alternate the order.
- Mention that PowerShell Core is available cross-platform, but provide CLI alternatives for common tasks.
- Add troubleshooting tips for Linux/macOS users, such as file permission issues or shell differences.
IoT Hub
Monitor IoT messages with distributed tracing (preview)
...b/main/articles/iot-hub/iot-hub-distributed-tracing.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page exhibits a Windows bias in the sample application section: build and run instructions are provided only for Windows (Visual Studio, .exe, cmd), with no Linux/macOS equivalents or explicit parity. Windows tools (Visual Studio, command prompt) are mentioned exclusively and before alternatives. Linux/macOS users must refer to external links for build instructions, creating friction.
Recommendations
- Add explicit Linux/macOS build and run instructions for the sample application, including required dependencies and example commands (e.g., gcc/clang, make, cmake, running the binary).
- Mention cross-platform editors and tools (e.g., VS Code, vim, nano) alongside Visual Studio.
- Provide example output and troubleshooting steps for Linux/macOS environments.
- Ensure all command-line instructions are provided for both Windows (cmd) and Unix shells (bash/zsh).
- Clarify platform-specific differences in SDK usage, if any.
IoT Hub
Overview of Azure IoT Hub message enrichments
...ticles/iot-hub/iot-hub-message-enrichments-overview.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Windows First
Summary
The documentation lists Azure PowerShell as a configuration method for message enrichments alongside Azure CLI and Portal, but does not mention Linux/macOS-specific tools or provide parity for command-line examples. The ordering of configuration methods places PowerShell before Linux-native alternatives, and there are no explicit Linux/macOS examples or notes about cross-platform usage.
Recommendations
- Ensure Azure CLI examples are provided and shown before PowerShell, as CLI is cross-platform.
- Add explicit notes that Azure CLI works on Linux/macOS, and provide example commands for those platforms.
- Clarify that PowerShell Core is available cross-platform, or link to installation instructions for Linux/macOS if PowerShell is recommended.
- Consider including bash or shell script examples where relevant.
- Review tutorials linked to ensure Linux/macOS users are not excluded from step-by-step instructions.
IoT Hub
Managing public network access for Azure IoT Hub
...main/articles/iot-hub/iot-hub-public-network-access.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation provides command-line examples for both Azure CLI and Azure PowerShell, but PowerShell is a Windows-centric tool and is listed alongside the CLI without clarifying cross-platform compatibility. The troubleshooting and access sections do not mention Linux/macOS-specific issues or alternatives, and the examples do not explicitly address Linux/macOS users. The Azure portal instructions are platform-neutral, but command-line and troubleshooting guidance is subtly Windows-first.
Recommendations
- Clearly state that Azure CLI works on Linux/macOS and provide explicit Linux/macOS usage notes where relevant.
- Clarify that Azure PowerShell is primarily for Windows and suggest Bash or other shell alternatives for Linux/macOS users.
- Add troubleshooting notes for Linux/macOS users, such as handling proxies or network settings on those platforms.
- Provide example commands in Bash or other common Linux shells, not just PowerShell.
- When listing command-line examples, show Azure CLI (cross-platform) first, then PowerShell.
IoT Hub
Understanding the IP address of your IoT hub | Microsoft Docs
...main/articles/iot-hub/iot-hub-understand-ip-address.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation references PowerShell and CLI clients in the context of firewall rules, but does not mention Linux/macOS equivalents or provide examples for those platforms. The mention of PowerShell implies a Windows-centric approach, and there are no explicit Linux/macOS instructions or tool references.
Recommendations
- Explicitly mention Linux/macOS CLI tools (e.g., Azure CLI on Bash, zsh) alongside PowerShell.
- Provide example commands for both Windows (PowerShell) and Linux/macOS (Bash) when discussing connectivity or firewall rules.
- Clarify that Azure CLI is cross-platform and provide guidance for its use on Linux/macOS.
- Avoid implying that PowerShell is the primary or only method for interacting with IoT Hub; present alternatives equally.