Document Details

Quick Create Confidential Vm Arm
Home / Scan #2 / Quick Create Confidential Vm Arm
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.
GitHub View on GitHub 📚 View on Microsoft Learn

Bias Analysis

Detected Bias Types
powershell_heavy
windows_first
windows_tools
Summary
The documentation demonstrates a Windows bias by relying heavily on PowerShell syntax and variables throughout the CLI examples, mentioning PowerShell installation as a prerequisite, and using Windows tools (such as PowerShell cmdlets and variable syntax) even when the main focus is Azure CLI. Additionally, in several places, Windows examples or references are presented before Linux equivalents.
Recommendations
  • Provide all CLI examples in both PowerShell (Windows) and Bash (Linux/macOS) syntax, especially for variable assignment and command chaining.
  • List Linux/Bash installation and usage instructions alongside or before Windows/PowerShell instructions in the prerequisites.
  • Avoid using PowerShell-specific constructs (e.g., `$variable` assignment, backticks for line continuation, `Out-String | ConvertFrom-Json`) in generic Azure CLI examples; instead, provide Bash equivalents (e.g., `variable=value`, `\` for line continuation, `jq` for JSON parsing).
  • When referencing example parameter files, alternate the order or present Linux examples first where appropriate.
  • Explicitly state that all steps can be performed on Linux/macOS and provide links to relevant Bash shell documentation.
  • Where PowerShell modules or tools are required (e.g., Microsoft Graph SDK), provide equivalent instructions for Linux environments if available.
GitHub Create Pull Request

Scan History

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

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.