Confidential Computing

67
Total Pages
53
Linux-Friendly Pages
14
Pages with Bias
20.9%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

83 issues found
Showing 1-25 of 83 flagged pages
Confidential Computing Secure Key Release with Azure Key Vault and application on Confidential VMs with AMD SEV-SNP ...idential-computing/skr-flow-confidential-vm-sev-snp.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. Windows and PowerShell examples are given more prominence, especially in scripting the key release operation, with a full PowerShell script provided and no equivalent Bash or Linux shell script. Windows tools and patterns (e.g., PowerShell, VC_redist, Windows-specific instructions) are mentioned before or in more detail than Linux equivalents. While Linux is supported and some Linux instructions are present, the scripting and automation focus is heavily on Windows/PowerShell, and Linux users are left to adapt the Windows-centric examples.
Recommendations
  • Provide a full Bash or Linux shell script equivalent for the Secure Key Release operation, similar to the PowerShell example.
  • Ensure that Linux instructions (e.g., for guest attestation, key release, certificate validation) are given equal prominence and detail as Windows instructions.
  • Mention Linux tools (e.g., curl, jq, openssl) for interacting with Azure services and parsing responses, not just PowerShell and Windows tools.
  • Where examples are provided, present both Windows and Linux versions side-by-side, or default to cross-platform tools first.
  • Clarify any OS-specific requirements or differences early in the documentation, and avoid assuming Windows as the default environment.
GitHub Create Pull Request
Confidential Computing Create an Azure confidential VM with ARM template ...idential-computing/quick-create-confidential-vm-arm.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates several Windows biases: PowerShell syntax and variables are used throughout, even in Azure CLI examples; Windows-specific tools (PowerShell, Microsoft Graph PowerShell SDK) are referenced as prerequisites and for key steps; Windows parameter file examples are presented before Linux ones; and some steps (e.g., variable assignment, object conversion) use Windows/PowerShell patterns without Linux/Bash equivalents. There are no explicit Bash/Linux shell examples for variable assignment or object manipulation, and Linux users may find it harder to follow or adapt the instructions.
Recommendations
  • Provide Bash/Linux shell equivalents for all variable assignments and scripting steps, especially where PowerShell syntax is currently used.
  • List both Windows and Linux prerequisites (e.g., Bash, Azure CLI) and avoid requiring PowerShell for CLI usage.
  • Present Linux parameter file examples before or alongside Windows examples to avoid 'Windows first' ordering.
  • For steps involving Microsoft Graph, offer REST API or cross-platform SDK alternatives, not just PowerShell.
  • Explicitly note cross-platform compatibility and provide guidance for Linux users throughout the document.
GitHub Create Pull Request
Confidential Computing Create a confidential VM with the Azure CLI for Azure confidential computing ...al-computing/quick-create-confidential-vm-azure-cli.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page exhibits several Windows biases: many of the advanced steps (especially those involving service principal creation, key vault policy setting, and disk encryption set creation) rely heavily on PowerShell commands and patterns, even though the Azure CLI is cross-platform. Windows tools (e.g., Microsoft Graph PowerShell SDK) are referenced without Linux alternatives. In multi-step procedures, PowerShell is used for scripting and variable assignment, which is less natural for Linux users. While the basic VM creation examples use Azure CLI and Linux images, the more complex workflows assume a Windows/PowerShell environment, and Windows-specific instructions or links are often mentioned before Linux equivalents.
Recommendations
  • Replace PowerShell scripting and variable assignment with Bash equivalents where possible, especially in CLI-focused documentation.
  • Provide Linux-native instructions for steps currently using PowerShell (e.g., service principal creation, variable assignment, piping JSON output).
  • Reference cross-platform tools and SDKs, or provide Linux alternatives to Windows-specific tools like the Microsoft Graph PowerShell SDK.
  • Ensure that Linux examples are given equal prominence and detail as Windows examples, and avoid mentioning Windows instructions before Linux ones unless contextually necessary.
  • Where both Windows and Linux workflows exist, clearly separate them and provide parity in explanation and code samples.
GitHub Create Pull Request
Confidential Computing Quickstart - Create Intel SGX VM in the Azure Portal ...articles/confidential-computing/quick-create-portal.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation demonstrates mild Windows bias by mentioning Windows options and tools before or alongside Linux equivalents, referencing PowerShell and RDP, and providing explicit links and instructions for Windows VM connection and SDK installation. Linux is covered, but Windows tools and patterns are often mentioned first or in parallel, and some instructions are more detailed for Windows users.
Recommendations
  • Ensure Linux instructions and examples are presented before or equally with Windows options, especially in authentication and connection sections.
  • Provide explicit Linux command-line examples for all steps, including VM connection and SDK installation, not just SSH.
  • Avoid referencing Windows tools (PowerShell, RDP) before Linux tools (Bash, SSH) unless contextually necessary.
  • Add parity in post-deployment steps, such as linking to Linux OE SDK installation guides alongside Windows guides.
  • Clarify that Azure Cloud Shell and WSL are cross-platform solutions, and highlight Linux-native workflows where possible.
GitHub Create Pull Request
Confidential Computing Create an Azure confidential VM in the Azure portal ...ntial-computing/quick-create-confidential-vm-portal.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates several Windows biases: PowerShell is the only scripting example provided for service principal setup, with no equivalent Bash or Azure CLI example for Linux users. Windows tools (PuTTY) are mentioned as SSH clients, and Windows connection instructions are referenced before Linux. There is a lack of Linux-specific command-line examples, and Windows-centric patterns (RDP, PowerShell) are described in more detail than Linux alternatives.
Recommendations
  • Provide Azure CLI or Bash equivalents for all PowerShell commands, especially for service principal setup and key creation.
  • Mention native Linux SSH clients (e.g., OpenSSH) before or alongside PuTTY, and clarify usage for both Windows and Linux users.
  • Ensure Linux connection instructions are as detailed and prominent as Windows instructions, including command-line usage examples.
  • Add explicit Linux command-line examples for key vault and disk encryption set creation, not just referencing PowerShell.
  • Review the ordering of instructions and examples so that Linux and Windows are presented with equal prominence and detail.
GitHub Create Pull Request
Confidential Computing Quickstart - Create Intel SGX VM in the Azure Marketplace ...les/confidential-computing/quick-create-marketplace.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation provides both Linux and Windows options for deploying Intel SGX VMs, but there is a subtle Windows bias. Windows tools and patterns (e.g., PowerShell, RDP) are mentioned alongside or before Linux equivalents, and instructions for connecting to VMs include PowerShell as a primary option for Windows users. The documentation references Windows-specific details (like RDP port 3389) and tools (PowerShell, WSL) before or alongside Linux alternatives, sometimes without giving Linux-first examples or parity in depth.
Recommendations
  • Ensure Linux examples and tools (e.g., Bash, SSH) are presented first or with equal prominence before Windows-specific options.
  • Provide explicit Linux command-line examples and troubleshooting steps, not just generic SSH instructions.
  • When mentioning Windows tools (PowerShell, RDP), immediately follow with Linux alternatives and avoid assuming Windows as the default environment.
  • Add more Linux-specific guidance for post-deployment tasks, such as driver verification and VM management.
  • Consider separating Linux and Windows quickstart flows for clarity and parity.
GitHub Create Pull Request
Confidential Computing Virtual Machine Metablob Disk ...onfidential-computing/virtual-machine-metablob-disk.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation demonstrates Windows bias by consistently using Windows as the example OS type in REST and CLI commands, providing detailed PowerShell examples and notes, and omitting explicit Linux-specific command examples or usage patterns. The CLI and REST sections use generic shell syntax, but all sample commands and parameters (e.g., --os-type Windows) default to Windows, with no parity for Linux VM creation or disk management. PowerShell, a Windows-centric tool, is given equal or greater prominence than CLI, and special notes are included for PowerShell multiline syntax, further emphasizing Windows workflows.
Recommendations
  • Include explicit Linux examples in REST, CLI, and PowerShell sections, such as using --os-type Linux and Linux-specific VM disk scenarios.
  • Provide sample commands for common Linux shells (bash/zsh) and clarify any differences in parameter usage or returned values for Linux VMs.
  • Add notes or sections describing Linux-specific considerations for confidential VM disks, such as supported OS types, file formats, and security profiles.
  • Balance PowerShell and CLI coverage by offering more detailed CLI examples and troubleshooting tips for Linux users.
  • Where PowerShell syntax is explained, offer equivalent guidance for bash/zsh multiline commands and scripting best practices.
GitHub Create Pull Request
Confidential Computing Virtual TPMs in Azure confidential VMs ...ial-computing/virtual-tpms-in-azure-confidential-vm.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exhibits a Windows bias by referencing Windows-specific TPM documentation, Secure Boot, and PCR management links, without mentioning Linux equivalents or providing Linux-centric examples. All external links and terminology are oriented toward Windows, and there is no discussion of how vTPMs are used or managed in Linux-based Azure confidential VMs.
Recommendations
  • Include references to Linux TPM documentation, such as tpm2-tools and Linux kernel TPM support.
  • Provide examples or guidance for managing vTPMs in Linux confidential VMs, including attestation and measured boot processes.
  • Add links to Linux Secure Boot and measured boot documentation.
  • Clarify that vTPMs are supported on both Windows and Linux confidential VMs, and highlight any differences or considerations for each platform.
  • Balance external references between Windows and Linux resources to ensure parity.
GitHub Create Pull Request
Confidential Computing Virtual TPMs in Azure confidential VMs ...ial-computing/virtual-tpms-in-azure-confidential-vm.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits a Windows bias by referencing Windows-specific TPM documentation, Secure Boot, and PCR management links, without mentioning or providing equivalent Linux resources, examples, or tooling. All external links and terminology are Windows-centric, and there are no Linux-specific instructions or references.
Recommendations
  • Include references to Linux TPM documentation and tooling, such as tpm2-tools and Linux kernel TPM support.
  • Provide examples or guidance for using vTPMs in Linux confidential VMs, including attestation and measured boot processes.
  • Add links to Linux resources for Secure Boot and PCR management, such as Linux Unified Key Setup (LUKS) integration, or Linux boot integrity measurement guides.
  • Balance Windows and Linux terminology and examples throughout the documentation to ensure cross-platform parity.
GitHub Create Pull Request
Confidential Computing Create a confidential VM with the Azure CLI for Azure confidential computing ...al-computing/quick-create-confidential-vm-azure-cli.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page exhibits several Windows biases. Many steps, especially those involving Azure AD and Key Vault permissions, use PowerShell commands and Windows-centric tooling (e.g., Microsoft Graph SDK for PowerShell) without offering equivalent Bash or Linux-native alternatives. PowerShell is used for scripting and variable assignment, even though the Azure CLI is cross-platform. Windows tools and patterns (like Out-String, ConvertFrom-Json) are referenced, and the instructions for service principal creation and policy assignment are Windows-first. Linux examples are present for VM creation and attestation, but the overall scripting workflow assumes a Windows/PowerShell environment.
Recommendations
  • Provide Bash or Azure CLI-only alternatives for all scripting steps, especially those currently shown only in PowerShell.
  • Replace or supplement PowerShell-specific commands (e.g., Out-String, ConvertFrom-Json) with cross-platform equivalents (e.g., jq for JSON parsing in Bash).
  • Explicitly mention and demonstrate how to perform prerequisite steps (such as service principal creation and policy assignment) on Linux/macOS environments.
  • Ensure that all examples and scripts are runnable in Azure Cloud Shell (Bash) and do not require PowerShell unless strictly necessary.
  • Where Windows tools or SDKs are referenced, provide links or instructions for Linux equivalents or clarify cross-platform compatibility.
GitHub Create Pull Request
Confidential Computing Create an Azure confidential VM in the Azure portal ...ntial-computing/quick-create-confidential-vm-portal.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page exhibits several signs of Windows bias. PowerShell commands are provided for key setup steps (service principal creation) without Linux CLI equivalents. Windows tools (PuTTY) are mentioned as the primary SSH client, and Windows connection instructions are referenced before Linux ones. There is a lack of Linux-native command examples (e.g., Azure CLI, Bash) for tasks like service principal creation and key management, and the documentation often defaults to Windows-centric patterns and tools.
Recommendations
  • Provide Azure CLI or Bash equivalents for all PowerShell commands, especially for service principal and key creation steps.
  • Mention Linux-native SSH clients (e.g., OpenSSH, terminal SSH) before or alongside PuTTY, and clarify platform-specific instructions.
  • Ensure connection instructions for Linux VMs are as detailed and prominent as those for Windows VMs.
  • Where Windows tools or patterns are referenced, offer Linux alternatives in parallel.
  • Review the order of presentation so that Linux and Windows instructions/examples are given equal prominence and detail.
GitHub Create Pull Request
Confidential Computing Quickstart - Create Intel SGX VM in the Azure Portal ...articles/confidential-computing/quick-create-portal.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation page generally maintains cross-platform parity, but there are subtle signs of Windows bias. Windows is mentioned as an option alongside Ubuntu, but is listed after Ubuntu in the OS selection. However, Windows-specific tools (PowerShell, RDP) are referenced before or alongside Linux equivalents, and instructions for connecting to VMs mention PowerShell and Windows-specific scenarios (Win32 OpenSSH, WSL) prominently. The connection instructions reference PowerShell for Windows users, and there is a separate callout for connecting to Windows VMs and installing the OE SDK on Windows, while Linux instructions are more integrated. There is no explicit Linux bias, but Windows tooling and patterns are given significant attention.
Recommendations
  • Provide Linux-specific examples and tools first when describing cross-platform steps, such as connecting to VMs.
  • Include parity in SDK installation instructions, e.g., link to both Linux and Windows OE SDK install guides in the same section.
  • When mentioning SSH clients, list Linux and macOS tools before Windows tools, and clarify that PowerShell is available on all platforms.
  • Avoid referencing Windows-specific scenarios (e.g., Win32 OpenSSH, WSL) before Linux equivalents unless contextually necessary.
  • Ensure that any Windows-specific instructions are matched with Linux equivalents in the same location for easy comparison.
GitHub Create Pull Request
Confidential Computing Create an Azure confidential VM with ARM template ...idential-computing/quick-create-confidential-vm-arm.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation demonstrates a Windows bias by requiring PowerShell for variable assignment and scripting, referencing PowerShell installation as a prerequisite, and using PowerShell-specific constructs (e.g., `$variable` syntax, backticks for line continuation, ConvertFrom-Json, Out-String). Windows parameter file examples are presented before Linux ones, and Windows tools (PowerShell, Microsoft Graph SDK for PowerShell) are referenced without Linux alternatives. There are no explicit Bash or Linux shell equivalents for variable assignment, scripting, or Azure CLI usage, which may hinder Linux users.
Recommendations
  • Provide Bash/Linux shell examples for variable assignment and scripting alongside PowerShell examples.
  • List Linux prerequisites (e.g., Bash, Azure CLI installation on Linux) equally with Windows prerequisites.
  • Use cross-platform syntax for Azure CLI commands, avoiding PowerShell-specific constructs (e.g., `$variable`, backticks, ConvertFrom-Json).
  • Present Linux and Windows parameter file examples in parallel or alternate their order to avoid Windows-first bias.
  • Reference Linux-native tools (e.g., Microsoft Graph CLI, jq for JSON parsing) where PowerShell is mentioned.
  • Clarify which steps are OS-agnostic and which require OS-specific tools, providing guidance for both platforms.
GitHub Create Pull Request
Confidential Computing Quickstart - Create Intel SGX VM in the Azure Marketplace ...les/confidential-computing/quick-create-marketplace.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation provides both Linux and Windows options for deploying Intel SGX VMs, but there is a slight Windows bias. Windows tools (PowerShell, RDP) are mentioned alongside or before Linux equivalents, and instructions for connecting to VMs reference PowerShell and Windows-specific scenarios. There is a separate section for connecting to Windows VMs, but Linux instructions are more detailed. The documentation mentions installing WSL or using Azure Cloud Shell for Windows users, which is helpful but still centers Windows as a primary platform.
Recommendations
  • Ensure Linux examples and tools (e.g., Bash, SSH) are presented before Windows equivalents in each section.
  • Provide equally detailed instructions for connecting to both Linux and Windows VMs, possibly in parallel subsections.
  • Mention Linux-native tools and workflows first, with Windows alternatives as secondary options.
  • Avoid referencing Windows-specific tools (PowerShell, RDP) unless necessary, and always provide Linux alternatives.
  • Add explicit CLI examples for Linux users (e.g., Azure CLI commands for deployment and connection).
GitHub Create Pull Request
Confidential Computing Secure Key Release with Azure Key Vault and application on Confidential VMs with AMD SEV-SNP ...idential-computing/skr-flow-confidential-vm-sev-snp.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits a moderate Windows bias. The main example for performing the key release operation is provided as a PowerShell script, which is primarily a Windows-centric tool (even though PowerShell Core is cross-platform, its usage and idioms are more familiar to Windows users). The script includes Windows-specific checks and references, such as .exe files and certificate handling with .NET APIs. While Linux instructions are present for the attestation client, there is no equivalent Linux shell (bash) example for the key release operation, nor is there a demonstration using common Linux tools like curl or jq. Additionally, references to retrieving managed identity object IDs mention PowerShell before Azure CLI and other options. Windows tools and patterns (PowerShell, .exe binaries, .NET certificate handling) are mentioned and exemplified before or instead of Linux equivalents.
Recommendations
  • Provide a full Linux shell (bash) example for the key release operation using curl and jq, demonstrating how to obtain the attested platform report, retrieve the managed identity token, and perform the HTTP POST to Key Vault.
  • Ensure that both Windows and Linux instructions are presented in parallel tabs or sections, with equal detail and prominence.
  • When referencing ways to retrieve managed identity object IDs, list Azure CLI and Linux-friendly methods before or alongside PowerShell.
  • Include examples of certificate validation using Linux tools such as openssl, rather than only .NET APIs.
  • Clarify cross-platform compatibility of tools (e.g., PowerShell Core) and provide guidance for both environments.
  • Avoid using Windows-centric terminology (such as .exe) without also mentioning Linux binary equivalents.
GitHub Create Pull Request
Confidential Computing Virtual Machine Metablob Disk ...onfidential-computing/virtual-machine-metablob-disk.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation demonstrates a Windows bias by consistently using 'Windows' as the example OS type in all CLI and REST API samples, providing PowerShell examples for every operation, and omitting explicit Linux-specific examples or references. There are no Linux shell or distribution-specific instructions, and the CLI examples do not clarify Linux usage or differences. The documentation also mentions PowerShell-specific syntax notes, reinforcing a Windows-centric approach.
Recommendations
  • Include Linux-specific examples, such as using 'osType: Linux' in REST and CLI samples.
  • Add sample CLI commands explicitly run on Linux shells (bash, zsh) and clarify any differences in syntax or environment variables.
  • Provide guidance for common Linux distributions (Ubuntu, CentOS, etc.) where relevant, especially for prerequisites and environment setup.
  • Balance PowerShell examples with bash or other Linux shell equivalents, and avoid PowerShell-specific notes unless also providing Linux shell notes.
  • Ensure documentation does not default to Windows terminology or tools when cross-platform alternatives exist.
GitHub Create Pull Request
Confidential Computing https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/confidential-computing/virtual-machine-metablob-disk.md ...onfidential-computing/virtual-machine-metablob-disk.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates Windows bias in several ways: Windows and PowerShell examples are provided and emphasized, with explicit instructions and notes about PowerShell syntax. The REST and CLI examples use 'osType: Windows' and Windows-centric parameters, while Linux-specific examples or references are missing. There are no explicit Linux shell or Linux VM creation examples, and the CLI and REST examples default to Windows settings. PowerShell is given its own section and detailed notes, while Linux command-line patterns (e.g., bash scripting, Linux-specific flags) are not covered.
Recommendations
  • Add explicit Linux VM examples, including 'osType: Linux' in REST and CLI samples.
  • Provide bash shell examples alongside PowerShell, especially for Azure CLI usage.
  • Include notes or sections on Linux command-line conventions (e.g., line continuation, environment variables).
  • Ensure parity in documentation for Linux and Windows, such as troubleshooting, FAQ, and tool usage.
  • Avoid defaulting to Windows-centric parameters in generic examples; alternate or show both OS types.
GitHub Create Pull Request
Confidential Computing https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/confidential-computing/confidential-vm-overview.md ...les/confidential-computing/confidential-vm-overview.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Windows Documentation Links
Summary
The documentation page exhibits mild Windows bias. Several key security features (TPM, Secure Boot, Live Migration, Dynamic Memory) link to Windows-centric documentation or use Windows terminology. Windows tools and patterns are referenced before or instead of Linux equivalents, and some feature explanations (e.g., Secure Boot, TPM) link only to Windows documentation. The OS support table lists Linux and Windows options side-by-side, but Windows versions are more granular and detailed. There are no Linux-specific usage examples, nor links to Linux documentation for equivalent features.
Recommendations
  • Provide Linux-focused documentation links for features like TPM and Secure Boot (e.g., point to Linux kernel documentation or distribution-specific guides).
  • Include Linux-specific examples and usage patterns, especially for security features (e.g., how attestation, TPM, and disk encryption work on Ubuntu/RHEL/SUSE).
  • Balance the OS support table by listing Linux distributions and versions with similar granularity as Windows.
  • When mentioning tools or features (e.g., Live Migration, Dynamic Memory), reference both Windows and Linux documentation or clarify cross-platform support.
  • Add Linux command-line examples (e.g., using bash, cloud-init, or Linux disk encryption tools) where relevant.
GitHub Create Pull Request
Confidential Computing https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/confidential-computing/quick-create-confidential-vm-arm.md ...idential-computing/quick-create-confidential-vm-arm.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation page demonstrates several Windows biases: PowerShell syntax and variables are used throughout, including in Azure CLI examples; instructions for installing prerequisites mention PowerShell before Azure CLI; and Windows parameter file examples are presented before Linux equivalents. Additionally, some steps (such as using Microsoft Graph SDK and variable assignment) assume a Windows/PowerShell environment, with no explicit Linux shell alternatives or guidance.
Recommendations
  • Provide Bash shell equivalents for all variable assignments and scripting steps, especially for Azure CLI usage.
  • List Linux and Windows parameter file examples side-by-side or alternate their order to avoid Windows-first bias.
  • Clarify that Azure CLI can be used natively on Linux/macOS and provide installation instructions for those platforms.
  • For steps requiring Microsoft Graph SDK, offer guidance for Linux users (e.g., using Python SDK or CLI alternatives) or note cross-platform compatibility.
  • Avoid using PowerShell-specific syntax (e.g., `$variable = value`, backticks for line continuation) in CLI examples; use Bash syntax or provide both.
GitHub Create Pull Request
Confidential Computing https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/confidential-computing/quick-create-confidential-vm-portal.md ...ntial-computing/quick-create-confidential-vm-portal.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page demonstrates mild Windows bias. PowerShell is the only example given for service principal setup, with no Linux CLI or Bash equivalent. Windows tools (PuTTY) are referenced as SSH clients, and Windows connection instructions are listed before Linux. The page does mention Linux VMs and SSH, but Windows-centric tools and patterns are more prominent, and Linux alternatives are not always presented equally.
Recommendations
  • Provide Azure CLI or Bash equivalents for PowerShell commands, especially for service principal setup.
  • Mention native Linux SSH clients (e.g., OpenSSH) before or alongside PuTTY, and clarify cross-platform options.
  • Present Linux connection instructions before or equally with Windows instructions.
  • Ensure all steps referencing tools or commands include both Windows and Linux alternatives.
  • Add explicit examples for Linux users where only Windows/PowerShell instructions are given.
GitHub Create Pull Request
Confidential Computing https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/confidential-computing/quick-create-portal.md ...articles/confidential-computing/quick-create-portal.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation page demonstrates some Windows bias, including mentioning Windows VM options before Linux in several places, referencing Windows-specific tools (PowerShell, RDP) and connection patterns, and providing links to Windows-specific instructions and SDK installation. Linux instructions are present, but Windows tools and patterns are often mentioned first or exclusively.
Recommendations
  • Ensure Linux examples and instructions are presented before or alongside Windows equivalents, especially in authentication and connection sections.
  • Provide parity in SDK installation instructions for both Linux and Windows, with direct links to Linux installation guides where Windows links are provided.
  • Avoid referencing Windows tools (e.g., PowerShell, RDP) without mentioning Linux alternatives (e.g., Bash, SSH) in equal detail.
  • Where possible, use cross-platform terminology (e.g., 'terminal' instead of 'PowerShell') and clarify steps for both OS types.
  • Add explicit Linux quickstart and troubleshooting sections if Windows ones are present.
GitHub Create Pull Request
Confidential Computing https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/confidential-computing/quick-create-confidential-vm-azure-cli.md ...al-computing/quick-create-confidential-vm-azure-cli.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page demonstrates a moderate Windows bias. Several critical steps in the customer-managed key workflow rely on PowerShell commands and Windows-centric tooling (e.g., Microsoft Graph SDK for PowerShell, use of PowerShell syntax for variable assignment and piping). These examples are given without equivalent Bash/Linux alternatives, and PowerShell is introduced before any Linux scripting options. Additionally, instructions for attestation sample apps mention Windows as a secondary option, with Linux as the primary example, but do not provide Windows build instructions inline.
Recommendations
  • Provide Bash/Linux shell equivalents for all PowerShell commands, especially for Azure AD and Key Vault operations.
  • Include instructions for installing and using Microsoft Graph SDK on Linux, or suggest cross-platform alternatives.
  • Ensure variable assignment and command chaining examples use Bash syntax where appropriate, or offer both PowerShell and Bash versions side-by-side.
  • Add inline build instructions for the attestation sample app on Windows, not just a link.
  • Review the order of examples and tooling references to avoid introducing Windows-specific tools before Linux equivalents.
  • Explicitly state cross-platform compatibility for all CLI commands and scripts, and clarify any OS-specific requirements.
GitHub Create Pull Request
Confidential Computing https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/confidential-computing/quick-create-marketplace.md ...les/confidential-computing/quick-create-marketplace.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation demonstrates mild Windows bias by mentioning Windows tools (PowerShell, RDP) before or alongside Linux equivalents, and by providing explicit instructions for connecting to Windows VMs and using Windows authentication methods. While Linux options are present and the main example uses Ubuntu, Windows tools and patterns are referenced frequently and sometimes first, such as PowerShell for SSH and RDP for remote access.
Recommendations
  • Provide Linux-specific examples and instructions before Windows ones, especially in sections about connecting to VMs.
  • Highlight Linux command-line tools (e.g., Bash, SSH) as primary options, with Windows alternatives as secondary.
  • Include explicit Linux-only quickstart flows, and avoid grouping Windows and Linux instructions unless necessary.
  • Reference Linux tools and patterns (e.g., SSH, SCP, Bash) before mentioning Windows tools like PowerShell or RDP.
  • Ensure parity in troubleshooting and driver installation instructions for both Linux and Windows.
GitHub Create Pull Request
Confidential Computing https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/confidential-computing/skr-flow-confidential-vm-sev-snp.md ...idential-computing/skr-flow-confidential-vm-sev-snp.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. PowerShell is used exclusively for scripting the key release operation, with no equivalent Linux shell (bash) example. Windows tools and patterns (PowerShell, VC_redist) are mentioned and demonstrated before or instead of Linux alternatives. While the guest attestation section provides both Windows and Linux instructions, the main scripting example for the key release operation is only shown in PowerShell, leaving Linux users without a direct bash or shell script equivalent.
Recommendations
  • Provide a Linux bash (shell) script example for the key release operation, using curl or similar tools, to match the PowerShell example.
  • When mentioning tools to retrieve managed identity object IDs, list Azure CLI and Linux-friendly methods before or alongside PowerShell.
  • Ensure that all code samples and operational steps have both Windows and Linux equivalents, and present them in parallel tabs or sections.
  • Avoid Windows-first ordering in examples and tool recommendations; alternate or group by platform.
  • Explicitly mention Linux package installation and runtime requirements where Windows equivalents (e.g., VC_redist) are discussed.
GitHub Create Pull Request
Confidential Computing https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/confidential-computing/virtual-tpms-in-azure-confidential-vm.md ...ial-computing/virtual-tpms-in-azure-confidential-vm.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing Windows-specific TPM documentation, tools, and concepts (such as Secure Boot and PCR management) without providing equivalent Linux resources or examples. All links and terminology are oriented toward Windows, and there are no Linux-specific instructions or references.
Recommendations
  • Include links to Linux TPM documentation and tools, such as tpm2-tools and Linux kernel TPM documentation.
  • Provide examples or references for using vTPMs in Linux confidential VMs, including how to interact with vTPMs from Linux guests.
  • Mention Linux equivalents for Secure Boot and Measured Boot, such as shim, GRUB, and Linux Integrity Measurement Architecture (IMA).
  • Balance references to Windows and Linux in both terminology and external links to ensure parity for cross-platform users.
GitHub Create Pull Request
← Previous Page 1 of 4 Next →