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

Bias Types:
⚠️ powershell_heavy
⚠️ windows_tools
⚠️ missing_linux_example
Summary:
The documentation demonstrates a bias towards Windows environments by relying exclusively on PowerShell scripts for configuration and deployment tasks, and referencing Windows-centric tools like Visual Studio Code. While PowerShell 7 is cross-platform, there are no examples or guidance for using native Linux/Unix shell scripting or tools. The documentation does not provide equivalent bash or shell script examples, nor does it mention how to adapt the process for users who prefer or require non-PowerShell environments.
Recommendations:
  • Provide equivalent bash or shell script examples for all PowerShell scripts, especially for generating and applying configuration files.
  • Explicitly mention and demonstrate how to run the process on Linux/macOS, including any required dependencies or environment setup.
  • Reference cross-platform editors and tools more broadly (e.g., mention nano, vim, or other editors alongside Visual Studio Code).
  • Clarify that while PowerShell 7 is cross-platform, users may use bash or other shells, and provide guidance or links for adapting the scripts.
  • Where possible, offer Azure CLI or REST API alternatives for steps currently handled by PowerShell scripts.
GitHub Create pull request

Scan History

Date Scan ID Status Bias Status
2025-08-17 00:01 #83 in_progress ❌ Biased
2025-07-17 00:00 #53 completed ❌ Biased
2025-07-13 21:37 #48 completed ❌ Biased
2025-07-12 23:44 #41 in_progress ❌ Biased

Flagged Code Snippets

## Generate IoT Central API tokens In this guide, your pipeline uses API tokens to interact with your IoT Central applications. It's also possible to use a service principal. > [!NOTE] > IoT Central API tokens expire after one year. Complete the following steps for both your development and production IoT Central apps. 1. In your IoT Central app, select **Permissions** and then **API tokens**. 1. Select **New**. 1. Give the token a name, specify the top-level organization in your app, and set the role to **App Administrator**. 1. Make a note of the API token from your development IoT Central application. You use it later when you run the *IoTC-Config.ps1* script. 1. Save the generated token from the production IoT Central application as a secret called `API-Token` to the production key vault:
1. Follow the instructions to sign in to your Azure account. 1. After you sign in, the script displays the IoTC Config options menu. The script can generate a config file from an existing IoT Central application and apply a configuration to another IoT Central application. 1. Select option **1** to generate a configuration file. 1. Enter the necessary parameters and press **Enter**: - The API token you generated for your development IoT Central application. - The subdomain of your development IoT Central application. - Enter *..\Config\Dev* as the folder to store the config file and device templates. - The name of your development key vault. 1. The script creates a folder called *IoTC Configuration* in the *Config\Dev* folder in your local copy of the repository. This folder contains a configuration file and a folder called *Device Models* for all the device templates in your application. ## Modify the configuration file Now that you have a configuration file that represents the settings for your development IoT Central application instance, make any necessary changes before you apply this configuration to your production IoT Central application instance. 1. Create a copy of the *Dev* folder created previously and call it *Production*. 1. Open IoTC-Config.json in the *Production* folder using a text editor. 1. The file has multiple sections. However, if your application doesn't use a particular setting, that section is omitted from the file: