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
windows_tools
missing_linux_example
Summary
The documentation demonstrates a clear Windows bias. It repeatedly refers to 'your Windows machine' and assumes a Windows development environment by default. Instructions and examples prioritize Windows tools (Visual Studio, CMD, Git Bash, etc.), and environment setup steps are Windows-centric. Linux and macOS are only mentioned as alternatives, often with links out to other documentation rather than inline parity. Command-line instructions use Windows syntax (cmd, set) and do not provide Linux equivalents (bash, export, etc.). Visual Studio is emphasized for C/C++ development, with only a brief mention of Linux/macOS alternatives. There are no explicit Linux/macOS command examples or screenshots, and the initial framing and prerequisites are Windows-first.
Recommendations
  • Provide parallel Linux/macOS instructions and examples alongside Windows ones, including shell commands (e.g., use both 'set' and 'export' for environment variables).
  • Include explicit instructions for installing prerequisites (e.g., compilers, SDKs) on Linux/macOS, not just links to external setup guides.
  • Offer build and run instructions for Linux/macOS environments (e.g., using gcc/clang, make, or cmake with Unix Makefiles, and running from bash/zsh).
  • Add Linux/macOS screenshots where appropriate, or clarify when steps are identical across platforms.
  • Avoid language that assumes Windows as the default (e.g., 'on your Windows machine'); instead, use neutral phrasing or mention all supported OSes.
  • For Visual Studio-specific steps, provide equivalent instructions for common Linux IDEs (e.g., VS Code, CLion) or command-line workflows.
  • Ensure all code snippets and commands are cross-platform, or provide platform-specific tabs/pivots.
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 Biased Biased
2025-07-13 21:37 #48 completed Biased Biased
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

    $ cmake -Dhsm_type_symm_key:BOOL=ON -Duse_prov_client:BOOL=ON  ..
    -- Building for: Visual Studio 16 2019
    -- Selecting Windows SDK version 10.0.19041.0 to target Windows 10.0.19042.
    -- The C compiler identification is MSVC 19.29.30040.0
    -- The CXX compiler identification is MSVC 19.29.30040.0

    ...

    -- Configuring done
    -- Generating done
    -- Build files have been written to: E:/IoT Testing/azure-iot-sdk-c/cmake
    
    \azure-iot-sdk-c\cmake\azure_iot_sdks.sln

    
    cd '.\azure-iot-sdk-csharp\provisioning\device\samples\how to guides\SymmetricKeySample\'
    
    D:\azure-iot-sdk-csharp\provisioning\device\samples\how to guides\SymmetricKeySample>dotnet run --i 0ne00000A0A --r symm-key-csharp-device-01 --p sbDDeEzRuEuGKag+kQKV+T1QGakRtHpsERLP0yPjwR93TrpEgEh/Y07CXstfha6dhIPWvdD1nRxK5T0KGKA+nQ==

    Initializing the device provisioning client...
    Initialized for registration Id symm-key-csharp-device-01.
    Registering with the device provisioning service...
    Registration status: Assigned.
    Device csharp-device-01 registered to ExampleIoTHub.azure-devices.net.
    Creating symmetric key authentication for IoT Hub...
    Testing the provisioned device with IoT Hub...
    Sending a telemetry message...
    Finished.
    Enter any key to exit.
    
    set PROVISIONING_HOST=<provisioning-global-endpoint>
    
    set PROVISIONING_IDSCOPE=<id-scope>
    
    set PROVISIONING_REGISTRATION_ID=<registration-id>
    
    set PROVISIONING_SYMMETRIC_KEY=<primarykey>
    
    D:\azure-iot-samples-csharp\provisioning\device\samples>node register_symkey.js
    registration succeeded
    assigned hub=ExampleIoTHub.azure-devices.net
    deviceId=nodejs-device-01
    payload=undefined
    Client connected
    send status: MessageEnqueued
    
   cd azure-iot-sdk-python\samples\async-hub-scenarios
   
    set PROVISIONING_HOST=<provisioning-global-endpoint>
    
    set PROVISIONING_REGISTRATION_ID=<registration-id>
    
    set PROVISIONING_SYMMETRIC_KEY=<primarykey>
    
    D:\azure-iot-sdk-python\samples\async-hub-scenarios>python provision_symmetric_key.py
    RegistrationStage(RequestAndResponseOperation): Op will transition into polling after interval 2.  Setting timer.
    The complete registration result is
    python-device-008
    docs-test-iot-hub.azure-devices.net
    initialAssignment
    null
    Will send telemetry from the provisioned device
    sending message #8
    sending message #9
    sending message #3
    sending message #10
    sending message #4
    sending message #2
    sending message #6
    sending message #7
    sending message #1
    sending message #5
    done sending message #8
    done sending message #9
    done sending message #3
    done sending message #10
    done sending message #4
    done sending message #2
    done sending message #6
    done sending message #7
    done sending message #1
    done sending message #5
    
    cd azure-iot-sdk-java\provisioning\provisioning-device-client-samples\provisioning-symmetrickey-individual-sample