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 76-100 of 118 flagged pages
IoT Dps Symmetric key attestation with Azure DPS ...articles/iot-dps/concepts-symmetric-key-attestation.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation presents platform-specific examples for generating derived device keys in a tabbed format, but the Windows/PowerShell example is listed before the Linux/openssl example. The Windows/PowerShell example is more verbose and detailed, which may suggest a slight preference for Windows tooling and patterns. However, Linux parity is maintained with an openssl example, and the Azure CLI example is noted as cross-platform. There is no outright omission of Linux instructions, but the ordering and depth of Windows examples indicate mild Windows bias.
Recommendations
  • List platform examples in alphabetical order (e.g., Azure CLI, CSharp, Linux, Windows) or place cross-platform tools first to avoid implicit prioritization.
  • Ensure that Linux examples are as detailed and explanatory as Windows/PowerShell examples, including troubleshooting tips or common pitfalls.
  • Explicitly state that all examples are equivalent and supported, and clarify cross-platform compatibility for each method.
  • Consider adding a Python or Bash script example for Linux users who may not use openssl directly.
  • Review other sections for similar ordering or depth disparities and standardize example presentation.
GitHub Create Pull Request
IoT Dps Microsoft Azure IoT DPS IP connection filters ...ocs/blob/main/articles/iot-dps/iot-dps-ip-filtering.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a subtle Windows bias by referencing Azure PowerShell alongside Azure CLI as a management option, without clarifying cross-platform support or providing Linux-specific guidance. All interactive instructions focus exclusively on the Azure Portal UI (which is OS-agnostic but often associated with Windows workflows), and there are no command-line examples for Linux users. Additionally, the note that 'Azure CLI and Azure PowerShell don't currently support DPS IP filter rules updates' is helpful, but the lack of any Linux-native or cross-platform automation alternatives (such as curl, bash, or Python examples) further limits Linux parity.
Recommendations
  • When mentioning Azure PowerShell and Azure CLI, clarify that Azure CLI is cross-platform and provide explicit Linux usage notes where relevant.
  • Include command-line examples using Azure CLI (if/when supported), or REST API examples using curl or HTTPie, to demonstrate how Linux users can automate these tasks.
  • If certain features are not available via CLI or PowerShell, suggest cross-platform alternatives (e.g., using REST API calls with curl or Postman) and provide sample commands.
  • Ensure that any references to management tools or workflows do not assume a Windows environment; highlight cross-platform options and explicitly mention Linux compatibility where possible.
GitHub Create Pull Request
IoT Dps Virtual network connections for DPS .../blob/main/articles/iot-dps/virtual-network-support.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by exclusively referencing the Azure portal UI for configuration steps and management, without providing command-line examples (such as Azure CLI or PowerShell) or Linux-specific instructions. There are no examples or guidance for performing the same operations from Linux environments, nor is there mention of cross-platform tooling or parity. The only code sample provided is in C and is platform-agnostic, but all operational instructions assume use of the Azure portal, which is most commonly accessed from Windows environments.
Recommendations
  • Add step-by-step instructions for setting up private endpoints using Azure CLI, which is cross-platform and widely used on Linux.
  • Include PowerShell examples for completeness, but ensure Azure CLI instructions are presented first or alongside them.
  • Explicitly mention that all operations can be performed from Linux, macOS, or Windows using CLI tools.
  • Provide links to official Azure CLI documentation for each major step (creating private endpoints, managing DNS, etc.).
  • Where screenshots are used, consider including terminal output or command examples to supplement the portal UI.
  • Clarify that the device provisioning code and SDKs are cross-platform, and provide sample commands for building/running on Linux.
GitHub Create Pull Request
IoT Dps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-dps/concepts-symmetric-key-attestation.md ...articles/iot-dps/concepts-symmetric-key-attestation.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation presents platform-specific examples for generating derived device keys using Azure CLI, Windows (PowerShell), Linux (openssl), and C#. However, the Windows/PowerShell example is given before the Linux example, and the PowerShell example is more verbose and detailed compared to the Linux example. The Azure CLI example is cross-platform, but the explicit mention of PowerShell and Bash shells may subtly prioritize Windows. There is a slight 'windows_first' ordering and more emphasis on PowerShell scripting, which may suggest a Windows bias.
Recommendations
  • Present Linux and Windows examples in parallel or alternate their order in documentation to avoid implicit prioritization.
  • Ensure that Linux examples (e.g., using openssl) are as detailed and explanatory as Windows/PowerShell examples.
  • Explicitly state that Azure CLI is fully cross-platform and provide equal guidance for both Bash (Linux/macOS) and PowerShell (Windows) environments.
  • Consider adding examples for macOS if relevant, or clarify that Linux examples are applicable to macOS.
  • Review and balance the depth of explanation for each platform to ensure parity.
GitHub Create Pull Request
IoT Dps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-dps/how-to-verify-certificates.md ...ob/main/articles/iot-dps/how-to-verify-certificates.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation mentions PowerShell (Windows) and Bash (Linux) scripts for certificate management, but lists PowerShell first and refers to Microsoft-provided tools and samples primarily. There is a subtle prioritization of Windows tooling and patterns, with Windows/PowerShell examples mentioned before Linux equivalents. No explicit Linux-only example or tool is provided, and OpenSSL is referenced only as a dependency for the scripts, not as a standalone workflow.
Recommendations
  • Present Bash (Linux) and PowerShell (Windows) examples in parallel, or alternate their order in documentation.
  • Include explicit, step-by-step OpenSSL command-line examples for Linux users, independent of Microsoft SDK scripts.
  • Reference Linux-native tools and workflows (e.g., OpenSSL, shell scripts) before or alongside Windows/PowerShell equivalents.
  • Clarify that all steps can be performed on Linux, and provide screenshots or terminal outputs from Linux environments.
  • Add a section or callout for Linux users, highlighting any differences or considerations when using non-Windows platforms.
GitHub Create Pull Request
IoT Dps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-dps/iot-dps-understand-ip-address.md ...main/articles/iot-dps/iot-dps-understand-ip-address.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation references PowerShell and Azure CLI clients in the context of firewall rules, but does not mention or provide examples for Linux-specific tools or workflows. There are no explicit Linux command examples or references to Linux firewall management, and the only client tools mentioned are Azure CLI and PowerShell, which are often associated with Windows environments.
Recommendations
  • Include explicit examples for Linux environments, such as using iptables, ufw, or firewalld for firewall configuration.
  • Mention that Azure CLI is cross-platform and provide Linux-specific usage notes or troubleshooting tips.
  • Add references to Linux shell commands for automating retrieval of service tag JSON files (e.g., using curl or wget).
  • Clarify that PowerShell is available on Linux, but also provide Bash or shell script alternatives for parity.
  • Ensure that any client tool references (CLI, PowerShell) are accompanied by notes on their cross-platform availability and usage.
GitHub Create Pull Request
IoT Dps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-dps/monitor-iot-dps.md ...ure-docs/blob/main/articles/iot-dps/monitor-iot-dps.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a mild Windows bias by referencing PowerShell and the Azure portal as primary tools for monitoring and configuration, without providing explicit Linux or cross-platform command-line examples. While it mentions CLI and PowerShell in passing, no concrete examples or instructions for Azure CLI (which is cross-platform) or Linux shell usage are given. The workflow descriptions and screenshots focus on the Azure portal, which is platform-agnostic but often associated with Windows environments. There are no references to Linux-specific tools, nor are there step-by-step instructions or examples for Linux users.
Recommendations
  • Add explicit Azure CLI command examples for creating diagnostic settings, viewing metrics, and querying logs, alongside or before PowerShell references.
  • Include instructions or examples for common Linux shell environments (bash, zsh) where applicable.
  • Ensure that references to PowerShell are balanced with Azure CLI, highlighting CLI as a cross-platform solution.
  • Add screenshots or terminal output examples from Linux environments to reinforce cross-platform usability.
  • Where the Azure portal is referenced, clarify that it is accessible from any OS and suggest CLI alternatives for automation or scripting.
GitHub Create Pull Request
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
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Bash (Azure CLI) and Azure PowerShell examples for verifying results, but the PowerShell example is given equal prominence and is included as a dedicated tab. There is no explicit mention of Linux-specific tools or workflows, and Windows/PowerShell is presented as a primary option alongside Bash. The documentation does not reference Linux-specific patterns or troubleshooting, nor does it clarify cross-platform differences in setup or usage.
Recommendations
  • Explicitly state that all steps and code samples work on Linux, macOS, and Windows unless otherwise noted.
  • Provide troubleshooting guidance for Linux environments, especially for common issues (e.g., permissions, environment variables).
  • Include a note or section about installing and using Azure CLI and Terraform on Linux and macOS, with links to official installation guides.
  • If PowerShell is mentioned, clarify that PowerShell Core is cross-platform and provide instructions for installing it on Linux/macOS.
  • Consider adding examples for other shells (e.g., zsh, fish) or at least clarify that Bash commands are compatible with most Unix-like systems.
  • Ensure that any referenced scripts or code samples do not assume Windows-specific file paths or conventions.
GitHub 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 →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by exclusively using Azure portal (GUI) instructions for resource creation and management, which is primarily accessible and familiar to Windows users. While it briefly mentions Azure CLI and PowerShell as alternatives for managing enrollments after public access is disabled, it does not provide any command-line examples or instructions for either Azure CLI (cross-platform) or PowerShell. There are no Linux-specific examples, nor is there guidance for Linux users on how to perform these tasks outside the portal. The only code sample provided is in C and is platform-neutral, but all operational instructions are Windows-centric.
Recommendations
  • Add step-by-step instructions for setting up private endpoints using Azure CLI, which is cross-platform and widely used on Linux.
  • Include PowerShell instructions only alongside Azure CLI, not before, and clarify platform compatibility.
  • Provide explicit Linux usage notes, such as how to install and use Azure CLI on Linux for these tasks.
  • Ensure screenshots and UI references are supplemented with equivalent command-line instructions.
  • Where possible, mention any Linux-specific considerations for device provisioning and network setup.
GitHub 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 →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by exclusively referencing the Azure portal for all configuration steps, with no mention of command-line alternatives (such as Azure CLI or PowerShell) until a brief note about enrollment management. There are no Linux-specific examples or guidance, and the only code sample provided is in C, which is cross-platform but does not address platform-specific setup. The documentation does not provide parity for Linux users who may prefer or require CLI-based workflows.
Recommendations
  • Add step-by-step instructions for setting up private endpoints using Azure CLI, which is cross-platform and widely used on Linux.
  • Include PowerShell examples for Windows users, but ensure CLI examples are presented first or alongside them.
  • Explicitly mention that all portal-based steps can be performed using CLI or automation tools, and link to relevant documentation.
  • Provide troubleshooting or verification steps using CLI commands, which benefit both Linux and Windows users.
  • Clarify that the C code sample is platform-agnostic, and provide guidance for compiling and running it on both Windows and Linux.
GitHub Create Pull Request
IoT Dps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-dps/iot-dps-understand-ip-address.md ...main/articles/iot-dps/iot-dps-understand-ip-address.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation references Azure CLI and PowerShell as tools for managing DPS connectivity, but does not mention Linux-specific tools or provide examples for Linux users. There are no explicit command-line examples, but the mention of PowerShell and CLI clients implies a Windows-centric approach. No Linux firewall configuration guidance or examples are provided.
Recommendations
  • Include explicit examples for both Windows (PowerShell) and Linux (bash, iptables, ufw) when discussing firewall rule configuration.
  • Mention Linux equivalents to PowerShell, such as Azure CLI usage in bash or shell scripts.
  • Add guidance for configuring firewalls on Linux systems (e.g., using iptables, firewalld, or ufw) alongside Windows firewall instructions.
  • Clarify that Azure CLI is cross-platform and provide sample commands for both Windows and Linux environments.
GitHub Create Pull Request
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
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
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 no explicit mention of Linux or cross-platform considerations in the prerequisites or tooling sections. The documentation does not provide any Linux-specific troubleshooting or highlight differences in experience between Windows and Linux users.
Recommendations
  • Clearly label PowerShell examples as Windows-specific and Bash/Azure CLI examples as cross-platform.
  • Provide explicit guidance for Linux users in the prerequisites, including installation steps for Terraform and Azure CLI on Linux.
  • Ensure that Bash/Azure CLI examples are presented first or given primary prominence, as they are cross-platform.
  • Include troubleshooting notes for common Linux-specific issues (e.g., permissions, environment variables).
  • Mention alternative shells (e.g., zsh, fish) and note any differences in command syntax or behavior.
  • Add a note about the availability of Azure PowerShell on Linux, if relevant, or clarify its typical usage on Windows.
GitHub Create Pull Request
IoT Dps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-dps/iot-dps-https-sym-key-support.md ...main/articles/iot-dps/iot-dps-https-sym-key-support.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation page demonstrates a mild Windows bias. While the main workflow uses cross-platform tools (cURL, Python, Bash), Windows-specific instructions and tooling (Git Bash) are mentioned first and in more detail than their Linux equivalents. The prerequisites and command instructions repeatedly reference Windows environments and Git Bash, while Linux/WSL is treated as an alternative. There is no PowerShell bias, and all command examples are platform-neutral, but the overall narrative assumes Windows as the primary environment.
Recommendations
  • Present Linux and Windows instructions in parallel, rather than listing Windows first.
  • Explicitly mention native Bash on Linux before Git Bash on Windows, or provide equal detail for both.
  • Add a note that most commands work natively in Linux/macOS terminals, and clarify any platform-specific differences.
  • Where Git Bash is recommended for Windows, also mention alternatives like Windows Terminal with WSL, or PowerShell if applicable.
  • Ensure that installation and usage instructions for prerequisites (Python, Azure CLI, OpenSSL) are provided for both Linux and Windows, with equal detail.
GitHub Create Pull Request
IoT Dps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-dps/how-to-verify-certificates.md ...ob/main/articles/iot-dps/how-to-verify-certificates.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation mentions PowerShell (Windows) and Bash (Linux) scripts for certificate operations, but lists PowerShell first and refers to Microsoft-provided tools and samples with a Windows-centric ordering. There is a slight emphasis on Windows tooling and terminology, with PowerShell examples referenced before Bash/Linux equivalents. No explicit Linux example is shown, and Windows patterns are mentioned first.
Recommendations
  • Present Bash (Linux) and PowerShell (Windows) examples side-by-side, or alternate which is listed first.
  • Include explicit Linux command-line examples (e.g., OpenSSL commands) for manual certificate operations.
  • Clarify that all steps can be performed on Linux and macOS, not just Windows.
  • Reference cross-platform tools and avoid Windows-centric terminology where possible.
  • Add screenshots or walkthroughs using Linux environments in addition to Windows.
GitHub Create Pull Request
IoT Dps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-dps/public-network-access.md ...cs/blob/main/articles/iot-dps/public-network-access.md
Medium Priority View Details →
Scanned: 2025-08-17 00:01
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page primarily describes how to manage public network access for Azure IoT Device Provisioning Service using the Azure Portal, with no command-line examples. Where command-line management is mentioned, it lists Azure CLI and PowerShell together, but does not provide any concrete examples for either, nor does it mention Linux-specific tools or workflows. The ordering of 'Azure CLI, PowerShell, or service APIs' puts the cross-platform CLI first, but the lack of examples for Linux users or explicit mention of Linux environments may leave Linux users underserved.
Recommendations
  • Add explicit command-line examples for both Azure CLI and PowerShell, showing how to enable/disable public network access.
  • Ensure that Azure CLI examples are clearly marked as cross-platform and runnable on Linux, macOS, and Windows.
  • Include notes or sections specifically addressing Linux users, such as how to install and use Azure CLI on Linux.
  • If PowerShell examples are included, provide Bash equivalents to ensure parity.
  • Review the documentation for any implicit assumptions about the user's operating system and clarify where necessary.
GitHub Create Pull Request
IoT Dps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-dps/iot-dps-https-sym-key-support.md ...main/articles/iot-dps/iot-dps-https-sym-key-support.md
Medium Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation generally aims for cross-platform parity and uses cURL, Bash, and Python, which are available on both Linux and Windows. However, there is a subtle Windows bias in the way platform-specific instructions are ordered and in the explicit recommendation of Git Bash for Windows users, while Linux/WSL users are simply told to use Bash. Windows is mentioned first in several places, and the only Windows-specific tool mentioned is Git Bash, with no mention of native Windows command prompts or PowerShell. There are no PowerShell-specific examples, and Linux is not omitted, but the documentation assumes Windows users need extra tooling (Git Bash) to follow along, which may not be necessary for all users.
Recommendations
  • Alternate the order of platform mentions (sometimes Linux/WSL first, sometimes Windows) to avoid always putting Windows first.
  • Explicitly mention that Bash is available natively on Linux and WSL, and that Windows users can use Git Bash, WSL, or other Bash environments (such as Cygwin or Windows Terminal with WSL).
  • Consider providing a brief note for Windows users who may prefer PowerShell or Command Prompt, clarifying that the examples use Bash syntax and recommending Bash-compatible environments for all platforms.
  • Where possible, avoid assuming Windows users require extra tooling; clarify that Bash is the required shell environment, and list options for obtaining it on Windows.
  • Ensure that any references to tools or environments are balanced; if Git Bash is mentioned for Windows, mention native Bash for Linux/WSL with equal prominence.
GitHub Create Pull Request
IoT Dps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-dps/concepts-symmetric-key-attestation.md ...articles/iot-dps/concepts-symmetric-key-attestation.md
Medium Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides example code for generating derived device keys using Azure CLI, Windows PowerShell, Linux (openssl), and C#. However, in the tabbed example section, the Windows/PowerShell example is presented before the Linux example, and the PowerShell script is more detailed and user-friendly compared to the Linux/openssl example. There is a slight 'windows_first' ordering and a more comprehensive PowerShell example, which may indicate a subtle Windows bias.
Recommendations
  • Alternate the order of Windows and Linux examples in tabbed sections, or present Linux examples first in some cases to balance exposure.
  • Ensure that Linux/bash examples are as detailed and user-friendly as the PowerShell examples, including clear variable assignments and output formatting.
  • Where possible, provide cross-platform scripts (e.g., Python) that work equally well on Windows and Linux.
  • Explicitly state that all methods are equally supported and tested on both Windows and Linux platforms.
  • Consider including a table summarizing all available methods (CLI, PowerShell, Bash, C#, etc.) with platform compatibility.
GitHub Create Pull Request
IoT Dps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-dps/how-to-verify-certificates.md ...ob/main/articles/iot-dps/how-to-verify-certificates.md
Medium Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation references both PowerShell (Windows) and Bash (Linux) scripts for certificate operations, but PowerShell is mentioned first, and there is a slight emphasis on Windows tooling. There are no explicit, step-by-step Linux command examples, and the mention of PowerShell before Bash may subtly prioritize Windows users. However, Linux is acknowledged and supported via Bash scripts.
Recommendations
  • Alternate the order of mentioning PowerShell and Bash scripts, or mention Bash first in some sections to avoid Windows-first bias.
  • Provide explicit, step-by-step Linux (Bash/OpenSSL) command examples alongside any Windows/PowerShell examples.
  • Clarify that all steps and tools are equally supported on Linux and Windows, and highlight any platform-specific prerequisites (e.g., OpenSSL installation).
  • Consider adding a dedicated section or callout for Linux users to ensure parity and visibility.
GitHub Create Pull Request
IoT Dps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-dps/iot-dps-https-sym-key-support.md ...main/articles/iot-dps/iot-dps-https-sym-key-support.md
Medium Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation demonstrates mild Windows bias by consistently mentioning Windows and Windows-specific tools (notably Git Bash) before Linux equivalents, and by providing more detailed instructions for Windows users regarding prerequisites and environment setup. However, all command-line examples use cross-platform tools (cURL, Python, Bash), and Linux/WSL usage is acknowledged throughout. There are no PowerShell-only examples or missing Linux examples.
Recommendations
  • When listing environments, alternate the order or mention Linux/WSL first in some sections to avoid always prioritizing Windows.
  • Provide equal detail for Linux/WSL setup as is given for Windows (e.g., mention that Bash is the default shell on most Linux distributions, and clarify how to install required tools on Linux).
  • Clarify that Git Bash is only needed on Windows, and that native Bash is available on Linux/WSL, to avoid implying that Git Bash is a universal requirement.
  • Where possible, include explicit Linux package installation commands for prerequisites (e.g., how to install Python, curl, openssl on Ubuntu/Debian/CentOS).
  • Consider a table or section summarizing environment setup for both Windows and Linux/WSL, making parity and differences clear.
GitHub Create Pull Request
IoT Dps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-dps/public-network-access.md ...cs/blob/main/articles/iot-dps/public-network-access.md
Medium Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page provides instructions primarily through the Azure portal and mentions Azure CLI and PowerShell for managing enrollments when public network access is disabled. However, it does not provide any explicit Linux-specific examples or mention Linux tools, and PowerShell is mentioned alongside Azure CLI without clarifying cross-platform support. There are no command-line examples shown, and the documentation implicitly assumes familiarity with Windows-centric tools and workflows.
Recommendations
  • Explicitly mention that Azure CLI is cross-platform and provide example commands for both Windows (PowerShell/CMD) and Linux (Bash).
  • Include sample CLI commands for managing enrollments and network access, demonstrating usage in both Windows and Linux shells.
  • Clarify that PowerShell Core is available on Linux if PowerShell examples are provided, or prioritize Azure CLI examples since it is cross-platform.
  • Add a section or note highlighting Linux compatibility and any platform-specific considerations.
GitHub Create Pull Request
IoT Dps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-dps/iot-dps-https-x509-support.md ...ob/main/articles/iot-dps/iot-dps-https-x509-support.md
Medium Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation demonstrates a mild Windows bias by consistently mentioning Windows (and Git Bash) before Linux/WSL in instructions, and by focusing on Windows-specific tooling (Git Bash, winpty) for running commands on Windows. While Linux/WSL is supported and examples are provided, Windows environments and workarounds are prioritized or described first, and the documentation assumes the use of Git Bash rather than native Windows terminals or PowerShell.
Recommendations
  • Alternate the order of platform instructions so that Linux/WSL is sometimes presented first, or present both platforms equally (e.g., side-by-side tabs).
  • Explicitly mention native Windows terminal or PowerShell as alternatives to Git Bash, or provide PowerShell-native command examples where appropriate.
  • Clarify that 'winpty' is only required for Git Bash, and suggest native alternatives for users running in other Windows shells.
  • Ensure that all prerequisite and command instructions are equally detailed for both Linux and Windows, and avoid assuming that Windows users will always use Git Bash.
  • Consider adding a table or section summarizing all supported environments and the recommended shell/tools for each, to avoid implicit prioritization.
GitHub Create Pull Request
IoT Dps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-dps/concepts-symmetric-key-attestation.md ...articles/iot-dps/concepts-symmetric-key-attestation.md
Medium Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides cross-platform examples for generating derived device keys (Azure CLI, Windows/PowerShell, Linux/openssl, C#), but the Windows/PowerShell example is presented before the Linux/openssl example. Additionally, the Windows/PowerShell example is more detailed and uses native Windows tools, which may give the impression of a slight preference for Windows environments.
Recommendations
  • Present Linux and Windows examples in parallel or alternate their order in different sections to avoid always listing Windows first.
  • Ensure that Linux examples are as detailed and accessible as their Windows counterparts.
  • Explicitly state at the beginning of the example section that all major platforms are supported and that equivalent tooling is available.
  • Consider including a Bash example for macOS, or clarify that the Linux example applies to macOS as well.
  • Where possible, provide platform-agnostic code (e.g., Python) to further improve parity.
GitHub Create Pull Request
IoT Dps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-dps/iot-dps-https-sym-key-support.md ...main/articles/iot-dps/iot-dps-https-sym-key-support.md
Medium Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation generally aims for cross-platform parity by using cURL, Bash, and Python examples, and explicitly mentions both Linux and Windows environments. However, there is a subtle Windows bias: Windows is mentioned first in environment setup instructions, and Windows-specific tooling (Git Bash) is emphasized for Windows users, with no mention of native Windows command prompts or PowerShell. There are no PowerShell-specific examples, but the guidance for Windows users is to use Git Bash, a third-party tool, rather than native Windows shells. Linux/WSL users are simply told to use Bash, which is native. There are no missing Linux examples or exclusive use of Windows tools, but the documentation does not mention or provide parity for native Windows shells (e.g., Command Prompt or PowerShell), which could be seen as a gap.
Recommendations
  • Explicitly provide instructions or notes for users who may want to use native Windows shells (Command Prompt or PowerShell), or clarify why Git Bash is preferred.
  • Where possible, include PowerShell or Command Prompt equivalents for Bash/cURL commands, or link to documentation that explains how to run these commands in those environments.
  • Consider mentioning Linux/WSL first in environment setup sections, or alternate the order to avoid the appearance of Windows-first bias.
  • If recommending third-party tools (like Git Bash) for Windows, provide similar recommendations for Linux users if any non-native tools are required, or clarify that Bash is native on Linux.
  • Add a brief section explaining cross-platform considerations, including any limitations or differences when running commands on Windows vs. Linux.
GitHub Create Pull Request
IoT Dps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-dps/public-network-access.md ...cs/blob/main/articles/iot-dps/public-network-access.md
Medium Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page provides instructions primarily through the Azure portal UI and mentions PowerShell as a management option, but does not provide any command-line examples for either Windows (PowerShell) or Linux (Bash/CLI). However, when discussing alternatives to the portal, it lists 'Azure CLI, PowerShell, or service APIs', with PowerShell mentioned before Linux-native tools. There are no explicit Linux/Bash examples or references to Linux-specific tools, which may make Linux users feel less directly supported.
Recommendations
  • Provide explicit command-line examples for both Azure CLI (cross-platform) and PowerShell when mentioning alternatives to the portal.
  • When listing management options, mention Azure CLI before or alongside PowerShell to emphasize cross-platform parity.
  • Include sample commands for common tasks (such as enabling/disabling public network access) using both Azure CLI and PowerShell.
  • Clarify that Azure CLI commands work on Linux, macOS, and Windows, and provide installation links for each platform.
GitHub Create Pull Request
IoT Dps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-dps/iot-dps-https-x509-support.md ...ob/main/articles/iot-dps/iot-dps-https-x509-support.md
Medium Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation demonstrates a mild Windows bias by consistently mentioning Windows and its tools (specifically Git Bash and winpty) before Linux/WSL equivalents, and by providing Windows-specific instructions and caveats (such as the need for an extra slash in certificate subjects and the use of winpty for openssl). While Linux/WSL instructions are present and parity is generally maintained, Windows is prioritized in ordering and tool recommendations.
Recommendations
  • Alternate the order in which Windows and Linux/WSL instructions are presented, or present Linux first in some sections to balance perceived priority.
  • When introducing prerequisites and command-line environments, mention Bash on Linux/WSL first, then Git Bash for Windows, to avoid defaulting to Windows-centric language.
  • Clarify that winpty and the extra slash in certificate subjects are only needed for Git Bash on Windows, and consider grouping these as footnotes or callouts rather than leading the main instructions.
  • Where possible, provide a unified command example and only note platform-specific differences as exceptions, rather than separate primary/secondary tabs.
  • Explicitly state that all examples are cross-platform unless otherwise noted, and highlight any differences in a neutral, non-prioritized way.
GitHub Create Pull Request
← Previous Page 4 of 5 Next →