IoT Dps
49
Total Pages
25
Linux-Friendly Pages
24
Pages with Bias
49.0%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
118 issues found
Showing 101-118 of 118 flagged pages
IoT Dps
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-dps/quick-setup-auto-provision-cli.md
...ain/articles/iot-dps/quick-setup-auto-provision-cli.md
Medium Priority
View Details →
Detected Bias Types
Bash First
Windows Shell Note
Summary
The documentation primarily uses Bash syntax for variable assignment and command examples, with a note indicating that users on Windows CMD or PowerShell should adapt the commands. However, no explicit Windows CMD or PowerShell examples are provided, and Bash is presented as the default environment. There is no exclusive use of Windows tools or patterns, but Linux/Bash is favored in the examples.
Recommendations
- Provide equivalent command examples for Windows CMD and PowerShell alongside the Bash examples, especially for variable assignment and usage.
- Include a table or section summarizing syntax differences for key commands (e.g., variable assignment, echoing variables) across Bash, CMD, and PowerShell.
- Explicitly mention that the Azure CLI works cross-platform and link to official guidance on using it in different shells.
- Consider alternating the order of examples or providing tabs for Bash, CMD, and PowerShell to ensure parity and clarity for all users.
Create Pull Request
IoT Dps
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-dps/virtual-network-support.md
.../blob/main/articles/iot-dps/virtual-network-support.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a 'Windows-first' bias by exclusively referencing the Azure portal UI for configuration steps and mentioning PowerShell as a management option before the Azure CLI. There are no explicit Linux-specific instructions or CLI examples, and all screenshots and step-by-step guides are based on the Azure portal, which is platform-agnostic but often more familiar to Windows users. Additionally, there are no command-line examples (neither PowerShell nor Bash/CLI), and Linux tooling or workflows are not discussed.
Recommendations
- Add explicit Azure CLI (bash) examples for all configuration steps, especially for setting up private endpoints and managing enrollments.
- When listing management options, mention Azure CLI before or alongside PowerShell to avoid Windows-first ordering.
- Include at least one example using Linux-native tools or workflows (e.g., bash scripts, curl, jq) for interacting with DPS and private endpoints.
- Provide screenshots or terminal output from cross-platform tools (CLI) in addition to or instead of Azure portal UI.
- Clarify that all instructions are cross-platform where possible, and highlight any steps that are platform-specific.
IoT Dps
Quickstart - Use Terraform to create a DPS instance
...ticles/iot-dps/quick-setup-auto-provision-terraform.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Bash (Azure CLI) and Azure PowerShell examples for verifying the results, but the PowerShell example is given equal prominence and is not clearly marked as Windows-specific. There is a slight 'windows_first' bias in the ordering and presentation, as PowerShell is often associated with Windows, and no explicit Linux/macOS instructions or notes are provided for PowerShell. However, Bash examples are present, and the core Terraform workflow is platform-neutral.
Recommendations
- Clearly label PowerShell examples as Windows-only and Bash examples as cross-platform.
- Present Bash (Azure CLI) examples before PowerShell to prioritize cross-platform usage.
- Add explicit notes clarifying which commands are suitable for Linux/macOS and which are Windows-only.
- Consider providing macOS-specific tips if any OS-specific issues exist.
- Ensure troubleshooting and cleanup sections mention platform differences if applicable.
IoT Dps
Symmetric key attestation with Azure DPS
...articles/iot-dps/concepts-symmetric-key-attestation.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides platform-specific examples for generating derived device keys, with Windows/PowerShell instructions presented before Linux/openssl. The Windows example is more detailed and uses PowerShell, a Windows-centric tool. However, Linux instructions are present and functional, and Azure CLI is noted as cross-platform.
Recommendations
- Present Linux and Windows examples in parallel or alternate their order to avoid implicit prioritization.
- Clarify that Azure CLI is fully cross-platform and can be used on both Windows and Linux, possibly making it the primary recommended method.
- Ensure equal detail and explanation for Linux/bash and Windows/PowerShell examples.
- Consider adding macOS-specific notes if there are platform nuances.
- Explicitly state that all methods are equivalent and available on all major platforms where possible.
IoT Dps
How to use raw HTTPS in Azure IoT Hub Device Provisioning Service
...main/articles/iot-dps/iot-dps-https-sym-key-support.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation demonstrates mild Windows bias by consistently mentioning Windows and Windows-specific tools (Git Bash) before Linux equivalents. Instructions for running commands on Windows reference Git Bash, while Linux users are directed to Bash. However, all command examples (cURL, Python, Bash) are cross-platform and do not rely on Windows-only tools or patterns. No PowerShell examples or Windows-only commands are present, and Linux users can follow all steps without friction.
Recommendations
- Present Linux and Windows instructions in parallel, rather than listing Windows first.
- Explicitly mention that Bash on Linux and Git Bash on Windows are functionally equivalent for these commands.
- Add a note clarifying that all examples work natively on Linux/macOS terminals, and on Windows via Git Bash or WSL.
- Consider including macOS in environment mentions, not just Linux and Windows.
- Where possible, avoid implying Windows as the default or primary platform.
IoT Dps
Symmetric key attestation with Azure DPS
...articles/iot-dps/concepts-symmetric-key-attestation.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides platform-specific examples for generating derived device keys using Azure CLI, Windows PowerShell, Linux (openssl), and C#. However, the Windows/PowerShell example is presented before the Linux example, and the PowerShell script is more detailed than the Linux equivalent. The CLI example is cross-platform, but the narrative mentions Windows and PowerShell before Linux and Bash. No Linux-specific tools (other than openssl) are discussed, and the Windows/PowerShell approach is given prominence.
Recommendations
- Present platform examples in a neutral or rotating order (e.g., Linux first in some sections, or alphabetical).
- Ensure parity in example detail: expand the Linux example to match the explanation and comments provided in the PowerShell example.
- Mention Linux tools and patterns (e.g., Python, shell scripting) as alternatives to openssl for key derivation.
- Explicitly state cross-platform compatibility for CLI commands and clarify that Bash and PowerShell are equally supported.
- Avoid language like 'On Windows...' before 'On Linux...' unless there is a technical reason.
IoT Dps
Verify X.509 CA certificates with DPS
...ob/main/articles/iot-dps/how-to-verify-certificates.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation references both PowerShell (Windows) and Bash (Linux) scripts for certificate proof-of-possession, but PowerShell is mentioned first and C# SDK samples are highlighted, which are more Windows-centric. There is no explicit example or walkthrough for Linux/macOS users, and Windows terminology (PowerShell) appears before Linux equivalents.
Recommendations
- Present Bash (Linux/macOS) and PowerShell (Windows) examples side-by-side, or alternate which is shown first.
- Add explicit step-by-step instructions or code samples for Linux/macOS users using Bash and OpenSSL.
- Highlight cross-platform tools (e.g., OpenSSL) and clarify their usage on Linux/macOS.
- Include screenshots or CLI examples from Linux/macOS environments, not just Windows/PowerShell.
- Mention that the C# SDK sample can be run on Linux/macOS using .NET Core, if applicable.
IoT Dps
How to use raw HTTPS in Azure IoT Hub Device Provisioning Service
...main/articles/iot-dps/iot-dps-https-sym-key-support.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation demonstrates minor Windows bias by mentioning Windows-specific tools (Git Bash) and instructions for Windows users before Linux equivalents. The guidance for running commands on Windows focuses on Git Bash, while Linux/WSL users are directed to Bash. However, all command examples (curl, Python, Bash) are cross-platform and do not rely on Windows-only tooling or syntax.
Recommendations
- Present Linux and Windows instructions in parallel, rather than listing Windows first.
- Explicitly mention that Bash is available natively on Linux/macOS and via WSL or Git Bash on Windows.
- Include a brief note about running commands in macOS Terminal, not just Linux/WSL.
- Clarify that all examples are cross-platform and do not require Windows-specific tools.
- Consider listing Linux/macOS instructions before Windows, or in a neutral order.
IoT Dps
Quickstart - Set up the Azure IoT Hub Device Provisioning Service (DPS) with an Azure Resource Manager template (ARM template)
...main/articles/iot-dps/quick-setup-auto-provision-rm.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation page demonstrates a mild Windows bias. While the main quickstart flow uses the Azure portal and Azure CLI (both cross-platform), references to PowerShell and Windows-centric tools appear frequently and are often mentioned before Linux/macOS alternatives. PowerShell is highlighted as a primary alternative deployment method, and links to PowerShell documentation are provided before REST API or SDK options. There are no explicit Linux/macOS examples, and no mention of platform-specific considerations for those environments.
Recommendations
- Add explicit Linux/macOS examples, such as Bash shell commands, where interactive CLI usage is shown.
- When listing alternative deployment methods, mention cross-platform options (CLI, REST API, SDKs) before PowerShell.
- Include notes or links for installing and using Azure CLI on Linux/macOS.
- Clarify that PowerShell is available cross-platform, but provide parity in examples for Bash and other shells.
- Ensure screenshots and instructions for the Azure portal do not assume Windows-specific UI conventions.
IoT Dps
Quickstart - Use Terraform to create a DPS instance
...ticles/iot-dps/quick-setup-auto-provision-terraform.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides verification steps for both Bash (Azure CLI) and Azure PowerShell, but lists Bash first. There is no evidence of exclusive Windows tools or missing Linux examples; both platforms are covered for the verification step. However, the inclusion of Azure PowerShell as a primary alternative may indicate a slight Windows bias, as PowerShell is more commonly used on Windows, though it is cross-platform. No critical steps are Windows-only, and Linux/macOS users can complete all tasks.
Recommendations
- Continue listing Bash/Azure CLI examples first, as they are more universally cross-platform.
- Consider clarifying that Azure PowerShell is available on Linux/macOS, or provide a note about cross-platform compatibility.
- If possible, add explicit Linux/macOS troubleshooting notes or tips where relevant.
- Ensure future documentation sections do not introduce Windows-only tools or workflows.
IoT Dps
Quickstart - Set up Azure IoT Hub Device Provisioning Service using Azure CLI
...ain/articles/iot-dps/quick-setup-auto-provision-cli.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation primarily uses Bash syntax for Azure CLI commands and explicitly mentions that the commands are valid for Bash. It provides only a brief note that users on Windows/CMD or PowerShell should modify the commands for their environment, without giving concrete examples or guidance for those platforms. No PowerShell or CMD examples are provided, but Windows users are mentioned before Linux users in the note, suggesting a subtle 'windows_first' bias.
Recommendations
- Provide equivalent command examples for Windows CMD and PowerShell, alongside the Bash examples.
- Include a table or section summarizing syntax differences for variable assignment and command usage across Bash, CMD, and PowerShell.
- Clarify that Azure CLI is cross-platform and can be used on Windows, Linux, and macOS, with links to platform-specific installation and usage guides.
- Ensure that references to shell environments mention Linux/Bash and Windows/PowerShell/CMD in a neutral order, or group them together without prioritizing one.
IoT Dps
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-dps/quick-setup-auto-provision-cli.md
...ain/articles/iot-dps/quick-setup-auto-provision-cli.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation primarily uses Azure CLI examples, which are cross-platform. However, when discussing shell-specific syntax for setting variables, the documentation presents Bash syntax first and only briefly mentions that users of Windows/CMD or PowerShell should modify the commands, without providing explicit Windows or PowerShell examples. This could be interpreted as a slight bias toward Bash/Linux environments, but the only explicit mention of platform difference puts Windows second.
Recommendations
- Provide explicit command examples for Windows CMD and PowerShell alongside Bash examples when discussing environment-specific syntax (e.g., setting variables).
- Add a table or section summarizing the syntax differences for common commands across Bash, CMD, and PowerShell.
- Clarify that Azure CLI is available on all major platforms and provide links or instructions for installing it on Windows, Linux, and macOS.
- Ensure that tips and notes about environment differences are equally detailed for both Linux/Bash and Windows/PowerShell users.
IoT Dps
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-dps/concepts-tpm-attestation.md
...blob/main/articles/iot-dps/concepts-tpm-attestation.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation provides a conceptual overview of TPM attestation with Azure DPS but does not include any platform-specific examples or tooling instructions. However, it references 'the set of TPM tools being used, and the device operating system' without providing any concrete examples for either Windows or Linux. The absence of any examples or tool references means there is a lack of parity, but not explicit Windows bias. Still, Linux users may find the lack of Linux-specific guidance or examples limiting.
Recommendations
- Add practical examples for both Windows (e.g., using PowerShell or Windows TPM tools) and Linux (e.g., using tpm2-tools) to illustrate how to extract EK_pub and SRK_pub, take ownership, or clear a TPM.
- Include references or links to official documentation for both Windows and Linux TPM management tools.
- Explicitly mention common cross-platform tools (such as tpm2-tools for Linux) alongside any Windows tools, ensuring both are given equal prominence.
- Provide example commands or scripts for both operating systems to help users perform key TPM operations relevant to DPS attestation.
IoT Dps
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-dps/concepts-deploy-at-scale.md
...blob/main/articles/iot-dps/concepts-deploy-at-scale.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation provides only C# code samples and file storage patterns that implicitly assume a Windows or .NET environment, with no mention of Linux-specific considerations, tools, or code examples. There are no references to Linux shell commands, Linux file paths, or cross-platform SDK usage. The use of .NET APIs for file access and environment variables is not explained for Linux users, and there is no guidance on adapting the examples for Linux-based IoT devices.
Recommendations
- Provide equivalent code samples in a cross-platform language such as Python or C, or explicitly show how the C#/.NET code can be run on Linux (e.g., using .NET Core on Linux).
- Include Linux-specific instructions for setting environment variables and file paths (e.g., using $HOME or /var/lib for data directories).
- Mention and demonstrate how to run the provided code on both Windows and Linux, including any prerequisites (such as installing .NET on Linux).
- Add shell script (Bash) examples for provisioning and monitoring tasks where appropriate.
- Clarify that the patterns and APIs used are cross-platform, or provide alternatives for Linux-only environments.
- Reference Linux-native tools (such as systemd for background work, or Linux logging mechanisms) where relevant.
IoT Dps
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-dps/concepts-tpm-attestation.md
...blob/main/articles/iot-dps/concepts-tpm-attestation.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation provides a conceptual overview of TPM attestation with Azure DPS but does not include any concrete examples or tooling references for either Windows or Linux. However, it mentions that the steps for taking ownership of a TPM vary by manufacturer, tools, and operating system, but does not provide any examples or guidance for Linux users, nor does it mention any Linux-specific tools or commands. This omission may leave Linux users at a disadvantage compared to Windows users, especially since TPM management is often platform-specific.
Recommendations
- Add explicit examples for both Windows and Linux on how to take ownership of a TPM, including references to common tools (e.g., Windows TPM Management Console, Linux tpm2-tools).
- Mention popular Linux TPM utilities such as tpm2-tools and provide sample commands for reading EK_pub or taking ownership.
- Include links to official documentation or guides for TPM management on both Windows and Linux platforms.
- Ensure that any future procedural or code examples are provided for both operating systems to maintain parity.
IoT Dps
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-dps/quick-setup-auto-provision-terraform.md
...ticles/iot-dps/quick-setup-auto-provision-terraform.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides both Bash (Linux/macOS) and Azure PowerShell (Windows) examples for verifying the results, but the Bash example is presented first. There are no exclusive references to Windows tools or patterns, and Linux examples are not missing. No evidence of PowerShell-heavy bias or exclusive use of Windows tools was found.
Recommendations
- Maintain parity by continuing to provide both Bash and PowerShell examples for all command-line steps.
- Explicitly mention that Bash commands work on Linux and macOS, and that PowerShell is for Windows, to help users choose the right tab.
- Consider including a note about using the Azure CLI in Windows environments (e.g., via WSL or native CLI) to further support cross-platform users.
- Ensure that any referenced scripts or code samples are tested on both Linux and Windows environments.
IoT Dps
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-dps/concepts-tpm-attestation.md
...blob/main/articles/iot-dps/concepts-tpm-attestation.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation provides a conceptual overview of TPM attestation with Azure DPS but does not include any platform-specific examples or instructions. However, it references 'the set of TPM tools being used, and the device operating system' without giving concrete examples for either Windows or Linux. There is a lack of practical guidance or examples for Linux users, which may leave them underserved compared to Windows users if other documentation pages provide Windows-specific instructions.
Recommendations
- Add explicit examples or references for both Windows and Linux TPM tooling (e.g., tpm2-tools for Linux, Windows built-in TPM management tools).
- Include sample commands or workflows for taking ownership of a TPM and extracting EK_pub/SRK_pub on both Windows (e.g., using PowerShell or TPM.msc) and Linux (e.g., using tpm2_getpubek, tpm2_createprimary, etc.).
- Provide links to platform-specific TPM documentation or guides for both operating systems.
- Ensure that any future updates or related articles maintain parity by presenting Linux and Windows instructions side-by-side.
IoT Dps
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-dps/how-to-use-allocation-policies.md
...ain/articles/iot-dps/how-to-use-allocation-policies.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation provides command-line examples exclusively using the Azure CLI, which is cross-platform, and does not mention or show any Windows-specific tools (such as PowerShell or CMD), nor does it reference Windows-only patterns. However, it also does not provide any Linux- or macOS-specific examples, shell syntax, or notes about platform-specific considerations. Thus, while not overtly Windows-biased, the documentation lacks explicit Linux parity in examples or guidance.
Recommendations
- Explicitly state that the Azure CLI commands work on Windows, Linux, and macOS, to reassure non-Windows users.
- Where relevant, provide example shell commands using both Bash (for Linux/macOS) and PowerShell (for Windows), especially if there are differences in quoting, environment variables, or command syntax.
- Mention any platform-specific prerequisites or considerations (e.g., installation instructions for Azure CLI on Linux).
- Add a note or section clarifying that the documented procedures are cross-platform, and link to official Azure CLI installation guides for all supported operating systems.