Confidential Computing

65
Total Pages
54
Linux-Friendly Pages
11
Pages with Bias
16.9%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues (14)

https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/confidential-computing/quick-create-confidential-vm-portal.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows Tools Windows First
Summary:
The documentation demonstrates some Windows bias, particularly in the use of PowerShell for required configuration steps and the frequent mention of Windows-centric tools (e.g., PuTTY) and patterns. PowerShell is the only example given for service principal setup, and Windows tools are referenced before or instead of native Linux alternatives. While Linux is mentioned, parity in examples and tool recommendations is lacking.
Recommendations:
  • Provide equivalent Azure CLI or Bash commands for service principal and key creation steps, not just PowerShell.
  • When referencing SSH clients, mention native Linux/macOS SSH first, with PuTTY as an alternative for Windows users.
  • In connection instructions, show both command-line (ssh) and GUI (PuTTY) methods, and clarify which are for which OS.
  • Ensure that any step requiring scripting or automation includes both Windows (PowerShell) and Linux (Bash/Azure CLI) examples.
  • Review the order of presenting Windows and Linux instructions to avoid always listing Windows first.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/confidential-computing/attestation.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Missing Linux Example
Summary:
The documentation page does not provide any platform-specific examples or instructions, but it also does not mention or demonstrate Linux-specific tools, commands, or workflows. There are no explicit Windows or PowerShell examples, but the lack of any Linux examples or references may leave Linux users without clear guidance.
Recommendations:
  • Add explicit examples or references for both Windows and Linux environments, especially for common attestation workflows.
  • Include sample commands or scripts for Linux (e.g., using bash, curl, or OpenSSL) where relevant.
  • Mention any platform-specific requirements or differences in the attestation process for Linux users.
  • Provide links to Linux-focused resources or documentation if available.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/confidential-computing/guest-attestation-confidential-vms.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Windows First Windows Tools Missing Linux Example
Summary:
The documentation page demonstrates a Windows bias primarily through the use of Windows-specific terminology and claims in example outputs (e.g., 'x-ms-azurevm-is-windows': true, 'x-ms-azurevm-ostype': 'Windows'), and by referencing Windows as the default or only operating system in JSON web token examples. There are no explicit Linux or cross-platform usage examples, nor are Linux-specific tools, claims, or patterns mentioned. The documentation does not provide parity in examples or guidance for Linux-based confidential VMs.
Recommendations:
  • Include example JSON web tokens and claims for Linux-based confidential VMs, such as 'x-ms-azurevm-ostype': 'Linux' and related fields.
  • Explicitly mention that the attestation process and APIs are cross-platform, and provide guidance or notes for both Windows and Linux environments.
  • Add Linux-specific operational scenarios or diagrams, or clarify that the described scenarios apply equally to Linux workloads.
  • Reference Linux tools or libraries (if available) for guest attestation, or provide sample code snippets for both Windows and Linux.
  • Ensure that any sample outputs, especially in the 'JSON web token' section, alternate or include Linux values and not just Windows defaults.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/confidential-computing/attestation.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Missing Linux Example
Summary:
The documentation page does not provide any platform-specific examples or instructions, but it also does not mention or show any examples for Linux users, despite SGX enclaves being commonly used on Linux. There is no explicit Windows bias, but the absence of Linux-specific guidance or parity examples is a notable omission.
Recommendations:
  • Include explicit examples or references for both Windows and Linux environments, especially for common developer tasks such as running attestation commands or setting up the environment.
  • Clarify whether the attestation process or sample code is platform-agnostic, or provide separate instructions for each supported OS.
  • Link to or provide sample scripts for Linux (bash) as well as Windows (PowerShell), if applicable.
  • Mention any platform-specific prerequisites or differences in the attestation process for Linux users.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/confidential-computing/confidential-vm-overview.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Windows Tools Windows First
Summary:
The documentation page exhibits mild Windows bias. References to Windows-specific technologies (such as TPM and Secure Boot) link to Microsoft/Windows documentation, and the Trusted Platform Module (TPM) section links exclusively to Windows resources. In the OS support table, while Linux options are listed first, Windows versions are described in greater detail and with more granularity. Some feature limitations reference Windows-centric features (e.g., Live Migration, Dynamic Memory) without Linux equivalents or context.
Recommendations:
  • Provide equivalent Linux documentation links for technologies like TPM and Secure Boot (e.g., link to Linux TPM and Secure Boot documentation alongside Windows links).
  • When mentioning features like Live Migration or Dynamic Memory, clarify if there are Linux equivalents or note their absence for parity.
  • Ensure that Linux and Windows OS support are described with equal granularity and detail in tables and lists.
  • Where possible, include Linux-specific examples, tools, or references in addition to Windows ones, especially in sections discussing security technologies.
  • Review all external documentation links to ensure both Linux and Windows users are equally supported.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/confidential-computing/create-confidential-vm-from-compute-gallery.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example
Summary:
The documentation page demonstrates a subtle Windows bias by referencing Windows-specific scenarios (such as creating images from Windows confidential VMs) before mentioning Linux equivalents, and by not providing explicit Linux-focused examples or guidance. While there are some links to Linux generalization steps, the overall flow and examples are not balanced between Windows and Linux, and Linux-specific considerations are not highlighted.
Recommendations:
  • Add explicit Linux-focused examples and scenarios alongside Windows examples, especially when discussing image creation and generalization.
  • Ensure that references to generalization steps for both Linux and Windows are given equal prominence and are mentioned together, rather than Windows first.
  • Include notes or sections that address Linux-specific requirements or caveats for confidential VMs, such as supported distributions, kernel versions, or configuration steps.
  • Where possible, provide parity in screenshots or step-by-step instructions for both Windows and Linux VM images.
  • Review the order of presentation to avoid consistently mentioning Windows before Linux, and strive for a neutral or alternating order.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/confidential-computing/guest-attestation-confidential-vms.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Windows First Windows Tools Missing Linux Example
Summary:
The documentation page demonstrates a Windows bias in several ways. The JSON web token example and claims focus heavily on Windows-specific fields (e.g., 'x-ms-azurevm-is-windows', 'x-ms-azurevm-ostype': 'Windows'), and there is no mention of Linux-specific claims or examples. The documentation does not provide Linux-specific instructions, examples, or parity in the attestation process, nor does it mention Linux tools or patterns. The focus on Windows is evident both in the example data and the absence of Linux guidance.
Recommendations:
  • Include Linux-specific examples and claims in the JSON web token section, such as 'x-ms-azurevm-ostype': 'Linux' and relevant Linux distribution fields.
  • Provide sample attestation workflows or diagrams for Linux confidential VMs, highlighting any differences or considerations.
  • Mention Linux guest attestation libraries, tools, or SDKs if available, and provide links or references.
  • Ensure that API usage examples and error codes cover both Windows and Linux scenarios, noting any platform-specific differences.
  • Balance the documentation by presenting Windows and Linux information side-by-side where applicable, rather than focusing on Windows first or exclusively.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/confidential-computing/quick-create-confidential-vm-arm.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/confidential-computing/quick-create-confidential-vm-azure-cli.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows Tools Missing Linux Example
Summary:
The documentation page demonstrates a bias toward Windows environments in the sections related to customer-managed keys and Azure Key Vault integration. Several steps use PowerShell syntax and Windows-specific tools (e.g., Microsoft Graph SDK for PowerShell), and there are no equivalent Bash or Linux-native command examples provided for these steps. This may hinder Linux users who expect parity in CLI-based documentation.
Recommendations:
  • For every PowerShell example, provide an equivalent Bash/Azure CLI example that works natively on Linux/macOS.
  • Where Microsoft Graph SDK is required, document how to perform the same actions using REST APIs or CLI tools available on Linux.
  • Explicitly note when a step is Windows-only, and provide alternative instructions for Linux users where possible.
  • Ensure that all scripting and automation steps can be performed in cross-platform environments, not just in PowerShell.
  • Review the use of Windows-centric terminology and tools, and balance with Linux-native approaches throughout the documentation.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/confidential-computing/quick-create-confidential-vm-portal.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows Tools Windows First Missing Linux Example
Summary:
The documentation exhibits several signs of Windows bias. PowerShell is the only example given for service principal setup, with no Azure CLI or Bash equivalent. Windows tools (e.g., PuTTY) are mentioned prominently as SSH clients, and Windows port (RDP 3389) is listed before Linux (SSH 22) in inbound port selection. The documentation refers to Windows connection instructions first and provides more detailed steps for Windows tools, while Linux instructions are less detailed and lack native SSH/Bash command examples.
Recommendations:
  • Provide Azure CLI and/or Bash equivalents for all PowerShell commands, especially for service principal and key creation steps.
  • Mention native SSH clients (e.g., OpenSSH) before or alongside PuTTY, and provide command-line SSH examples for Linux/macOS users.
  • List Linux ports (SSH 22) before Windows ports (RDP 3389) or present both equally.
  • Ensure that connection instructions for Linux VMs include native SSH command-line examples, not just PuTTY.
  • Wherever Windows-specific tools or patterns are mentioned, ensure Linux equivalents are also referenced with equal prominence.
  • Add explicit Linux/Bash/CLI examples for all steps that currently only show PowerShell or Windows-centric instructions.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/confidential-computing/quick-create-portal.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example Windows Tools
Summary:
The documentation is generally neutral but exhibits subtle Windows bias in a few areas. Windows terminology and options are often mentioned before or more prominently than Linux equivalents, and some Linux-specific steps (such as installing the Azure DCAP client) are referenced but not detailed. There is also a lack of parity in post-deployment instructions, with explicit links and steps for Windows but not for Linux.
Recommendations:
  • Ensure Linux and Windows instructions are presented with equal prominence, or alternate which comes first.
  • Provide direct links and step-by-step instructions for Linux post-deployment tasks (e.g., installing the OE SDK on Linux), similar to the Windows guidance.
  • Include Linux-specific screenshots and examples where appropriate, not just generic or Windows-centric visuals.
  • Expand the 'Install Azure DCAP Client' section to include explicit Linux installation steps and commands.
  • Where Windows tools or patterns are mentioned (e.g., RDP, PowerShell), ensure Linux equivalents (e.g., SSH, Bash) are given equal or greater detail.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/confidential-computing/virtual-machine-solutions-sgx.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example
Summary:
The documentation generally maintains parity between Windows and Linux in terms of supported images and references. However, there is a subtle 'windows_first' bias: in the ARM template deployment section, the link for further information points to a Windows-specific template description page, and the Windows image is listed first in the example image references. There are no explicit Linux command-line examples (e.g., bash), and the Azure CLI example uses PowerShell-style backticks for line continuation, which may confuse Linux users. No Linux-specific deployment patterns or tools are mentioned.
Recommendations:
  • Provide links to both Windows and Linux ARM template documentation, or use a neutral, combined page.
  • List Linux and Windows images in a neutral or alternating order, or clarify that the order is not significant.
  • Use bash-style line continuation (backslash) in Azure CLI examples or provide both PowerShell and bash variants.
  • Explicitly mention Linux deployment considerations or tools where relevant, ensuring Linux users are equally supported.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/confidential-computing/virtual-tpms-in-azure-confidential-vm.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Windows First Windows Tools Missing Linux Example
Summary:
The documentation page demonstrates a Windows bias by referencing Windows-specific TPM documentation, Secure Boot, and PCR management links, without mentioning or linking to Linux equivalents. All conceptual explanations and links are Windows-centric, and there are no Linux-specific examples, tools, or references for working with vTPMs in Azure confidential VMs.
Recommendations:
  • Include references and links to Linux TPM documentation, such as tpm2-tools and Linux kernel TPM documentation.
  • Provide examples or guidance for managing and attesting vTPMs in Linux-based Azure confidential VMs, including command-line examples using tpm2-tools.
  • Mention Linux equivalents for Secure Boot and Measured Boot, such as shim, GRUB2, and Linux Integrity Measurement Architecture (IMA).
  • Balance references to Windows and Linux throughout the document, ensuring parity in conceptual explanations and practical guidance.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/confidential-computing/skr-flow-confidential-vm-sev-snp.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Windows Tools Missing Linux Example
Summary:
The documentation demonstrates a moderate Windows bias. While it provides both Linux and Windows instructions for the guest attestation client, the primary scripting example for performing the key release operation is a PowerShell script, which is more natural for Windows users. The script includes some Linux handling, but it is written in PowerShell, which is not a default or common shell on most Linux distributions. Additionally, references to tools like PowerShell cmdlets (e.g., Get-AzSubscription, Get-AzADUser) and .NET classes for certificate handling are prominent, and there are no equivalent Bash or Python examples for Linux users. The documentation often mentions Windows tools or patterns first or exclusively, and Linux alternatives are sometimes only referenced in passing or as an afterthought.
Recommendations:
  • Provide a full Bash (or Python) script example for performing the key release operation on Linux, including obtaining the attestation token, fetching the managed identity token, and making the HTTP request to Key Vault.
  • When referencing how to obtain object IDs or tenant IDs, include both PowerShell and Azure CLI commands, and present them in parallel or with equal prominence.
  • For certificate validation and JWT decoding, provide Linux-native alternatives (e.g., using OpenSSL, jq, or Python scripts) alongside PowerShell/.NET examples.
  • Ensure that all code samples and instructions are available for both Windows and Linux, and avoid assuming PowerShell is available on Linux unless explicitly stated and installation instructions are provided.
  • Where possible, present Linux and Windows instructions in parallel tabs or sections, rather than listing Windows first or exclusively.