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 26-50 of 83 flagged pages
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 →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Summary
The documentation page demonstrates mild Windows bias. Windows is mentioned as an OS option alongside Ubuntu, but Windows-specific tools and patterns (like RDP, PowerShell, and references to Windows 7/WSL) are highlighted. Instructions for connecting to VMs mention PowerShell before Bash, and guidance for Windows users is more detailed (e.g., how to connect, install OE SDK). Linux instructions are present but sometimes secondary, and Linux tools are not always given equal prominence.
Recommendations
- Ensure Linux examples and instructions are presented before or alongside Windows equivalents, not after.
- Provide parity in detail for Linux and Windows steps, including links to Linux-specific SDK installation and troubleshooting.
- Mention Linux tools (e.g., Bash, SSH, SCP) first when discussing connection options, and clarify that PowerShell is cross-platform.
- Add explicit Linux cleanup instructions (e.g., using Azure CLI or Bash) to match Windows resource group deletion guidance.
- Review and balance references to OS-specific tools (e.g., avoid suggesting PowerShell as the default for SSH on Windows; mention alternatives like Git Bash or WSL equally).
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 →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page exhibits a Windows-first bias by linking almost exclusively to Windows-specific TPM resources, referencing Windows security features (like Secure Boot) with Windows documentation, and omitting any Linux-specific examples or guidance. There are no Linux TPM tool references or examples, and the documentation assumes familiarity with Windows TPM concepts and tools.
Recommendations
- Include references to Linux TPM documentation, such as links to tpm2-tools or Linux kernel TPM documentation.
- Provide examples or explanations of how vTPMs can be used and attested in Linux confidential VMs, including command-line examples.
- Mention Linux equivalents for features like Measured Boot and Secure Boot, and link to relevant Linux documentation.
- Balance references and explanations so that both Windows and Linux users can understand how to interact with vTPMs in Azure confidential VMs.
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 →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by frequently using PowerShell syntax for variable assignment and command chaining, referencing PowerShell installation as a prerequisite, and providing PowerShell-specific instructions (e.g., Connect-Graph, ConvertFrom-Json, Out-String). Windows parameter file examples are presented before Linux ones, and Windows tools/patterns are mentioned without equivalent Linux alternatives. There is a lack of explicit Linux shell (bash) examples for variable assignment and command usage, which may hinder Linux users.
Recommendations
- Provide bash-specific examples for variable assignment and command chaining alongside PowerShell examples.
- List Linux parameter file examples before or alongside Windows examples to avoid 'windows_first' ordering.
- Remove PowerShell installation as a prerequisite for Azure CLI usage, or clarify that bash/zsh/fish are equally supported.
- Replace or supplement PowerShell-specific commands (e.g., ConvertFrom-Json, Out-String) with bash/jq equivalents.
- Explicitly mention Linux tools and patterns where applicable, ensuring parity in instructions for both platforms.
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 →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation page exhibits several Windows biases, particularly in the 'Create Confidential virtual machine using a Customer Managed Key' section. Many steps use PowerShell syntax and Windows-centric tooling (e.g., Connect-Graph, Out-String, ConvertFrom-Json), and PowerShell is used for scripting even when the Azure CLI is available cross-platform. Windows tools and patterns are mentioned before or instead of Linux equivalents, and there is no guidance for performing these steps in a native Linux shell. The attestation section is Linux-focused, but the earlier sections assume a Windows/PowerShell environment.
Recommendations
- Provide equivalent Bash/Linux shell commands for all PowerShell examples, especially for Azure CLI scripting and Microsoft Graph interactions.
- Clearly indicate which steps require PowerShell and offer alternatives for Linux/macOS users (e.g., using Azure CLI and Microsoft Graph REST API via curl/jq).
- Avoid using Windows-specific tools (e.g., Out-String, ConvertFrom-Json) in cross-platform documentation, or supplement with platform-agnostic alternatives.
- Structure example blocks so that Linux/Bash alternatives are presented alongside or before Windows/PowerShell examples.
- Add a section or callout explaining how Linux users can perform Microsoft Graph operations (e.g., using REST API with curl and jq).
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 →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page exhibits Windows bias in several ways: Windows-specific terminology and examples (e.g., 'osType': 'Windows', PowerShell commands) are presented before or instead of Linux equivalents. PowerShell is given its own section with detailed notes, while Linux shell examples are minimal and lack parity in explanation. There are no explicit Linux-specific examples (e.g., using --os-type Linux or Linux disk images), and the CLI examples default to Windows settings. The documentation does not mention Linux-specific patterns or tools, and the sample requests/responses use Windows as the default operating system.
Recommendations
- Include explicit Linux examples in REST API, Azure CLI, and PowerShell sections (e.g., using 'osType': 'Linux', Linux disk images, and Linux-specific parameters).
- Provide parity in command explanations for Bash/shell and PowerShell, including multiline command notes for Bash.
- Avoid defaulting to Windows in sample requests and responses; alternate or show both Windows and Linux cases.
- Mention Linux-specific considerations, such as supported file formats, disk types, and security profiles relevant to Linux VMs.
- Ensure that CLI examples use variables and flags that are applicable to both Windows and Linux, or show separate examples for each.
Confidential Computing
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/confidential-computing/virtual-machine-solutions-sgx.md
...onfidential-computing/virtual-machine-solutions-sgx.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. Windows Server is mentioned before Linux (Ubuntu) in lists of supported images, and the ARM template example lists the Windows image first. The only example command provided uses the Azure CLI, which is cross-platform, but the syntax shown uses backticks (`) for line continuation, which is a Windows PowerShell convention and not valid in Bash. There are no explicit Linux shell (Bash) examples, nor are Linux-specific tools or patterns discussed. References to further documentation use Windows-centric links (e.g., 'Virtual machines in an Azure Resource Manager template' points to a Windows VM template page).
Recommendations
- Provide both Windows and Linux shell examples for Azure CLI commands, using appropriate line continuation for Bash (\) and PowerShell (`).
- Alternate the order of Windows and Linux images in lists and examples, or present them alphabetically to avoid implicit prioritization.
- Include links to both Windows and Linux ARM template documentation, or use a neutral landing page.
- Explicitly mention that the Azure CLI is cross-platform and provide guidance for both Windows and Linux users.
- Where possible, add Linux-specific considerations or troubleshooting steps alongside Windows ones.
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 →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Summary
The documentation page demonstrates a mild Windows bias. Windows tools and patterns (e.g., PowerShell, RDP) are mentioned alongside or before Linux equivalents. Windows-specific instructions (such as connecting via RDP) are referenced with direct links, while Linux instructions are present but sometimes secondary. PowerShell is suggested as an SSH client for Windows users, and there is mention of installing WSL for older Windows versions, reinforcing Windows-centric workflows. However, Linux options are generally present and described.
Recommendations
- Ensure Linux instructions are presented first or equally, especially in connection steps.
- Provide explicit Linux command-line examples before or alongside Windows/PowerShell alternatives.
- Include direct links to Linux-specific documentation (e.g., SSH usage on Linux, troubleshooting) in the same way as Windows links are provided.
- Avoid suggesting Windows tools (PowerShell, WSL) as primary options for SSH; instead, mention them as alternatives.
- Add parity in troubleshooting and advanced configuration sections for both Linux and Windows users.
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 →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page exhibits several instances of Windows bias. PowerShell commands are used exclusively for service principal setup, with no equivalent Bash/Azure CLI examples for Linux users. Windows tools (PuTTY) are mentioned as SSH clients, and Windows connection instructions are listed before Linux. There is a lack of parity in command-line examples and tool recommendations for Linux users, and some steps (such as key creation with managed HSM) reference PowerShell or CLI but do not provide explicit Linux-friendly instructions.
Recommendations
- Provide Azure CLI and Bash examples alongside PowerShell commands for service principal and key creation steps.
- Mention and recommend native Linux SSH clients (e.g., OpenSSH) before or alongside PuTTY.
- Ensure Linux connection instructions are as detailed and prominent as Windows instructions.
- For steps that reference PowerShell or CLI, explicitly include Linux-compatible command examples.
- Review the order of instructions to avoid consistently listing Windows tools and steps before Linux equivalents.
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 →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page exhibits a moderate Windows bias. Windows and PowerShell are frequently referenced, with PowerShell scripts provided for key operations and certificate validation, and Windows-specific tools (e.g., VC_redist.x64.exe) mentioned. In several places, Windows instructions or tools are listed before Linux equivalents, and scripting examples are provided only in PowerShell, with no equivalent Bash or Linux-native scripting. While Linux is supported and some Linux instructions are present (especially for the attestation client), the scripting and automation focus is on Windows and PowerShell, leaving Linux users to adapt or improvise.
Recommendations
- Provide Bash or shell script equivalents for all PowerShell examples, especially for key release and certificate validation operations.
- Ensure Linux instructions are presented alongside Windows instructions, not after them, and avoid listing Windows first unless there is a technical reason.
- Include Linux-native tooling and patterns (e.g., OpenSSL for certificate validation, curl for HTTP requests) in examples.
- Explicitly mention cross-platform compatibility for all binaries and scripts, and link to both Windows and Linux resources equally.
- Where possible, use platform-agnostic language and examples (e.g., REST API calls with curl or Python) to demonstrate operations.
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 →
Detected Bias Types
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.
Confidential Computing
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/confidential-computing/guest-attestation-confidential-vms.md
...ential-computing/guest-attestation-confidential-vms.md
High Priority
View Details →
Detected Bias Types
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.
Confidential Computing
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/confidential-computing/guest-attestation-confidential-vms.md
...ential-computing/guest-attestation-confidential-vms.md
High Priority
View Details →
Detected Bias Types
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.
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 →
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.
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 →
Detected Bias Types
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.
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 →
Detected Bias Types
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.
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 →
Detected Bias Types
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.
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 →
Detected Bias Types
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.
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 →
Detected Bias Types
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.
Confidential Computing
Create a confidential VM with the Azure CLI for Azure confidential computing
...al-computing/quick-create-confidential-vm-azure-cli.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation page exhibits a moderate Windows bias in the sections describing customer-managed key setup for confidential VMs. Several steps use PowerShell syntax and Windows-centric tools (e.g., Connect-Graph, New-MgServicePrincipal), and PowerShell is used for scripting even when Azure CLI is available. Linux-specific alternatives for these steps are not provided, and PowerShell commands are shown before or instead of bash equivalents. However, the main VM creation and attestation instructions are Linux-friendly and use bash/Azure CLI.
Recommendations
- Provide bash or Azure CLI-only alternatives for all steps currently shown in PowerShell, especially for service principal creation and Azure Key Vault policy management.
- Explicitly mention how Linux/macOS users can install and use Microsoft Graph SDK (e.g., via dotnet CLI or REST API) or provide REST API equivalents.
- Ensure all scripting examples are shown in both PowerShell and bash where possible, or default to bash/Azure CLI for cross-platform parity.
- Clarify that PowerShell commands can be run in Azure Cloud Shell (which supports bash and PowerShell), but highlight bash as the default for Linux/macOS users.
- Add notes or links to Linux/macOS-specific documentation for steps involving RBAC, service principals, and key management.
Confidential Computing
Create an Azure confidential VM with ARM template
...idential-computing/quick-create-confidential-vm-arm.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation page exhibits a moderate Windows bias. PowerShell syntax is used for variable assignment and scripting throughout, even in Azure CLI examples, which may confuse Linux/macOS users. The prerequisites mention installing PowerShell before Azure CLI, and the first example parameter file is for Windows, with the Linux example shown second. Some commands (e.g., Connect-Graph) are PowerShell-specific, and use of Windows-centric tools is assumed in several steps.
Recommendations
- Provide explicit Bash syntax for variable assignment and scripting alongside PowerShell examples, especially for Azure CLI usage.
- List Linux/macOS prerequisites (e.g., Bash, native Azure CLI install) before or alongside Windows/PowerShell requirements.
- Show Linux parameter file examples first or in parallel with Windows examples.
- For steps requiring PowerShell-only tools (e.g., Microsoft Graph SDK via PowerShell), offer equivalent instructions for Bash or cross-platform alternatives.
- Clarify which commands are OS-agnostic and which require Windows/PowerShell, and provide alternatives where possible.
Confidential Computing
Create an Azure confidential VM in the Azure portal
...ntial-computing/quick-create-confidential-vm-portal.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation exhibits moderate Windows bias. PowerShell is used exclusively for critical steps (service principal creation), with no Linux/CLI alternative provided. Windows tools (PuTTY) are mentioned first and repeatedly as SSH clients, and Windows connection instructions precede Linux instructions. Some steps (e.g., key creation for managed HSM) reference PowerShell or CLI, but do not provide explicit Linux-friendly examples. Linux users may need to search for equivalents or adapt Windows-centric instructions.
Recommendations
- Provide Azure CLI and/or Bash examples for service principal creation and key management, alongside PowerShell.
- Mention OpenSSH (native on Linux/macOS) as the primary SSH client, with PuTTY as a Windows alternative.
- Present Linux/macOS connection instructions before or alongside Windows instructions, not after.
- Ensure all critical steps (e.g., key creation, resource setup) have cross-platform command examples.
- Add explicit links or inline instructions for Linux/macOS users where only Windows tools or patterns are shown.
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
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation provides both Linux and Windows instructions for the guest attestation client, but scripting examples for the key release operation are exclusively in PowerShell, which is a Windows-centric tool (even though PowerShell Core is cross-platform, its usage and idioms are more familiar to Windows users). Windows tools and patterns (e.g., PowerShell, VC_redist.x64.exe) are mentioned before or more prominently than Linux equivalents. There is no example of performing the key release operation using Bash, curl, or other common Linux/macOS tools, which creates friction for non-Windows users.
Recommendations
- Add a Bash or shell script example for performing the key release operation using curl or similar tools, showing how to acquire the managed identity token and perform the HTTP POST to Key Vault.
- Explicitly mention that PowerShell Core can be used on Linux/macOS, and provide installation instructions for those platforms.
- Where Windows-specific tools (e.g., VC_redist.x64.exe) are mentioned, provide Linux equivalents or clarify their necessity.
- Ensure that Linux/macOS instructions and examples are presented with equal prominence and detail as Windows ones.
- Consider providing Python or other cross-platform language examples for the key release operation.
Confidential Computing
Virtual Machine Metablob Disk
...onfidential-computing/virtual-machine-metablob-disk.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation displays a moderate Windows bias. While Azure REST API and CLI examples are provided (which are cross-platform), the PowerShell examples and notes are prominent and detailed, including multiline command guidance specific to Windows/PowerShell. In CLI and REST API sections, the examples use Windows-centric parameters (e.g., --os-type Windows), and there are no explicit Linux/macOS disk creation or access examples. The order of presentation often places Windows/PowerShell before Linux equivalents, and there is no mention of Linux-specific considerations, such as using --os-type Linux or shell scripting nuances.
Recommendations
- Add explicit Linux/macOS examples for disk creation and access, using --os-type Linux and relevant parameters.
- Include bash/zsh shell scripting notes where PowerShell-specific guidance is given.
- Balance the order of examples so that Linux and Windows are treated equally (e.g., alternate which OS is shown first).
- Clarify that Azure CLI is cross-platform and provide sample commands for both Windows and Linux environments.
- Mention any Linux-specific requirements or differences, if applicable.
Confidential Computing
Virtual TPMs in Azure confidential VMs
...ial-computing/virtual-tpms-in-azure-confidential-vm.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing Windows TPM documentation, linking to Windows-specific resources, and mentioning Windows-centric features (e.g., Secure Boot, Measured Boot) without providing Linux equivalents or examples. There are no Linux-specific instructions, tools, or references, and all external links point to Windows documentation.
Recommendations
- Include references to Linux TPM documentation, such as tpm2-tools or Linux kernel TPM subsystem.
- Provide examples or instructions for accessing and using vTPMs in Linux confidential VMs (e.g., using tpm2-tools, attestation workflows).
- Mention Linux equivalents for features like Measured Boot and Secure Boot, such as Linux's Integrity Measurement Architecture (IMA) and UEFI Secure Boot.
- Add links to Linux community resources or official documentation for TPM usage.
Confidential Computing
Create an Azure confidential VM with ARM template
...idential-computing/quick-create-confidential-vm-arm.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation exhibits moderate Windows bias. PowerShell syntax is used for variable assignment and scripting throughout, even in sections relevant to Linux users. Windows tools (PowerShell, Connect-Graph) are referenced in prerequisites and critical steps, and Windows parameter file examples are presented before Linux ones. While Linux equivalents are provided for parameter files and the Azure CLI is cross-platform, the scripting and command patterns favor Windows environments, creating friction for Linux/macOS users.
Recommendations
- Provide explicit Bash syntax for variable assignment and scripting alongside PowerShell examples, especially in Azure CLI sections.
- Clarify that Azure CLI commands can be run in Bash, and show Bash examples for all steps.
- When referencing tools like PowerShell or Connect-Graph, note Linux/macOS installation and usage options, or provide alternative methods where possible.
- Alternate the order of Windows and Linux examples, or present them side-by-side.
- Add a note at the start clarifying cross-platform compatibility and pointing to Linux/macOS specific guidance.