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
powershell_heavy
windows_first
windows_tools
missing_linux_example
Summary
The documentation page exhibits several signs of Windows bias. PowerShell syntax is used for variable assignment and command chaining throughout, with no equivalent Bash/Linux shell examples. Windows tools (PowerShell, Microsoft Graph SDK) are referenced for prerequisite installation and key management steps, and variable assignment is shown in PowerShell style. In the parameter file section, the Windows example is presented before the Linux example. There are missing Linux/Bash equivalents for critical steps such as variable assignment, command output parsing, and Microsoft Graph SDK usage.
Recommendations
  • Provide Bash/Linux shell equivalents for all PowerShell variable assignments and command chaining.
  • Include instructions for installing and using Microsoft Graph SDK on Linux, or offer alternative CLI-based approaches.
  • Present Windows and Linux parameter file examples side-by-side or alternate their order to avoid Windows-first bias.
  • Ensure all command output parsing (e.g., extracting IDs from az CLI output) is shown for both PowerShell and Bash (using jq or grep/awk).
  • Review all steps for implicit Windows assumptions and clarify cross-platform compatibility.
GitHub Create Pull Request

Scan History

Date Scan Status Result
2026-01-12 00:00 #99 completed Biased Biased
2026-01-11 06:20 #98 completed Biased Biased
2026-01-10 00:00 #92 completed Clean Clean
2026-01-06 22:28 #78 completed Clean Clean
2025-12-29 18:00 #48 cancelled Biased Biased
2025-12-15 00:00 #7 completed Clean Clean
2025-12-14 05:05 #6 completed Clean Clean

Flagged Code Snippets

1. Set the variables for your confidential VM. Provide the deployment name (`$deployName`), the resource group (`$resourceGroup`), the VM name (`$vmName`), and the Azure region (`$region`). Replace the sample values with your own information.

    > [!NOTE]
    > Confidential VMs are not available in all locations. For currently supported locations, see [which VM products are available by Azure region](https://azure.microsoft.com/global-infrastructure/services/?products=virtual-machines).

    
1. Grant confidential VM Service Principal `Confidential VM Orchestrator` to tenant

    For this step you need to be a Global Admin or you need to have the User Access Administrator RBAC role. [Install Microsoft Graph SDK](/powershell/microsoftgraph/installation) to execute the commands below.

    
    1. Deploy your confidential VM using a confidential VM ARM template for Intel TDX and a [deployment parameter file](#example-windows-parameter-file) (for example, `azuredeploy.parameters.win2022.json`) with the customer-managed key.