Sad Tux - Windows bias detected
This page contains Windows bias

About This Page

This page is part of the Azure documentation. It contains code examples and configuration instructions for working with Azure services.

Bias Analysis

Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
windows_tools
Summary
The documentation demonstrates a strong Windows bias throughout. Prerequisites, environment setup, and all code execution instructions are presented for Windows first, with explicit references to Windows tools (Visual Studio, Windows command prompt, certmgr.msc, .NET SDK for Windows, etc.). Linux and macOS users are repeatedly directed to external SDK documentation rather than being provided with in-page, step-by-step instructions or examples. All shell commands for device provisioning, SDK setup, and certificate management are shown using Windows command prompt or Git Bash on Windows, with only brief notes about differences for Linux (e.g., subject name slashes in OpenSSL). There are no full Linux-native or macOS-native walkthroughs, and Windows-specific tools and patterns (e.g., certificate store, Visual Studio solution files) are assumed as defaults.
Recommendations
  • For each programming language section, provide in-page, step-by-step instructions for Linux and macOS environments, not just links to SDK docs.
  • Include Linux/macOS command-line examples (bash, zsh, etc.) for cloning, building, and running SDKs, alongside Windows examples.
  • When referencing tools like Visual Studio, also mention and give instructions for common Linux/macOS IDEs or build systems (e.g., gcc, clang, make, cmake, VS Code).
  • For certificate management, provide Linux-native instructions (e.g., using update-ca-certificates, trust, or manual copying to /etc/ssl/certs) alongside Windows certmgr.msc steps.
  • Ensure all OpenSSL commands and file path examples are shown in both Windows and Linux/macOS formats.
  • Avoid assuming the use of Windows command prompt or Git Bash; clarify which shell is being used and provide alternatives.
  • Where environment variables are set, show both Windows (set VAR=val) and Linux/macOS (export VAR=val) syntax.
  • Summarize any platform-specific differences in a dedicated section or table for quick reference.
GitHub Create Pull Request

Scan History

Date Scan Status Result
2026-01-14 00:00 #250 in_progress Clean Clean
2026-01-13 00:00 #246 completed Clean Clean
2026-01-11 00:00 #240 completed Clean Clean
2026-01-10 00:00 #237 completed Clean Clean
2026-01-09 00:34 #234 completed Clean Clean
2026-01-08 00:53 #231 completed Clean Clean
2026-01-06 18:15 #225 cancelled Clean Clean
2025-09-15 00:00 #112 completed Clean Clean
2025-08-17 00:01 #83 cancelled Clean Clean
2025-07-13 21:37 #48 completed Clean Clean
2025-07-12 23:44 #41 cancelled Biased Biased
2025-07-09 13:09 #3 cancelled Clean Clean
2025-07-08 04:23 #2 cancelled Biased Biased

Flagged Code Snippets

    dotnet run -- -s <id-scope> -c <your-certificate-folder>\certs\device-02-full-chain.cert.pfx -p 1234
    
    cd .\azure-iot-sdk-java\provisioning\provisioning-device-client-samples\provisioning-X509-sample
    
    cmake -Duse_prov_client:BOOL=ON -Dhsm_custom_lib=c:/<path>/azure-iot-sdk-c/cmake/provisioning_client/samples/custom_hsm_example/Debug/custom_hsm_example.lib ..
    
    cmake -Duse_prov_client:BOOL=ON -Dhsm_custom_lib=c:/azure-iot-sdk-c/cmake/provisioning_client/samples/custom_hsm_example/Debug/custom_hsm_example.lib ..
    -- Building for: Visual Studio 17 2022
    -- Selecting Windows SDK version 10.0.19041.0 to target Windows 10.0.22000.
    -- The C compiler identification is MSVC 19.32.31329.0
    -- The CXX compiler identification is MSVC 19.32.31329.0
    
    ...

    -- Configuring done
    -- Generating done
    -- Build files have been written to: C:/azure-iot-sdk-c/cmake
    
    dotnet run -- -s <id-scope> -c <your-certificate-folder>\certs\device-01-full-chain.cert.pfx -p 1234
    
    cd .\azure-iot-sdk-node\provisioning\device\samples
    npm install
    
    set PROVISIONING_HOST=global.azure-devices-provisioning.net
    set PROVISIONING_IDSCOPE=<id-scope>
    
    set CERTIFICATE_FILE=<your-certificate-folder>\certs\device-01-full-chain.cert.pem
    set KEY_FILE=<your-certificate-folder>\private\device-01.key.pem
    
    set PROVISIONING_HOST=global.azure-devices-provisioning.net
    set PROVISIONING_IDSCOPE=<ID scope for your DPS resource>
    
    set X509_CERT_FILE=<your-certificate-folder>\certs\device-01-full-chain.cert.pem
    set X509_KEY_FILE=<your-certificate-folder>\private\device-01.key.pem