Confidential Computing
134
Total Pages
120
Linux-Friendly Pages
14
Pages with Bias
10.4%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
34 issues found
Showing 1-25 of 34 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 →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page exhibits several signs of Windows bias. PowerShell is the only scripting example provided for performing the key release operation, with no equivalent Bash or Linux shell script. Windows tools and patterns (such as PowerShell, VC_redist, and Windows-specific instructions) are mentioned before or more prominently than their Linux equivalents. The instructions for retrieving managed identity object IDs mention PowerShell first, and the main scripting example is PowerShell-centric, despite the scenario being equally applicable to Linux confidential VMs. There is a lack of parity in scripting examples and tool usage for Linux users.
Recommendations
- Provide a Bash or Linux shell script example for the key release operation, mirroring the PowerShell example.
- Ensure that instructions for retrieving managed identity object IDs mention Azure CLI and Linux-native tools before or alongside PowerShell.
- Where possible, use cross-platform tools (e.g., Azure CLI, REST API) in examples, or provide both Windows and Linux variants.
- Balance the order and prominence of Windows and Linux instructions throughout the documentation.
- Clarify which steps are OS-agnostic and which require platform-specific commands, and offer guidance for both platforms.
Create Pull Request
Confidential Computing
About Azure confidential VMs
...les/confidential-computing/confidential-vm-overview.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Windows Reference Links
Summary
The documentation page demonstrates mild Windows bias. Windows tools and documentation are referenced more frequently and prominently than Linux equivalents, especially in sections discussing Trusted Platform Module (TPM), Secure Boot, and feature limitations. Reference links for TPM and Secure Boot point to Windows documentation, and some feature limitations link to Windows Server/Hyper-V docs. In the OS support table, Windows versions are listed in detail and with more granularity than Linux distributions, and Windows is presented before Linux in some feature limitation links.
Recommendations
- Provide equivalent Linux documentation links for TPM and Secure Boot concepts (e.g., point to Linux kernel or distribution documentation on TPM and Secure Boot).
- Balance reference links by including both Windows and Linux resources where applicable.
- Ensure Linux examples and tools are mentioned alongside Windows ones, especially for key features like attestation, disk encryption, and boot security.
- Expand the OS support table to include more Linux distributions and versions, and provide parity in detail with Windows listings.
- Where feature limitations reference Windows-specific technologies (e.g., Hyper-V live migration), clarify Linux equivalents or note if the limitation applies to Linux as well.
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 page exhibits several signs of Windows bias. PowerShell syntax is used for variable assignment and command chaining throughout, with no equivalent Bash/Linux shell examples. Windows tools (PowerShell, Microsoft Graph SDK) are referenced for prerequisite installation and key management steps, and variable assignment is shown in PowerShell style. In the parameter file section, the Windows example is presented before the Linux example. There are missing Linux/Bash equivalents for critical steps such as variable assignment, command output parsing, and Microsoft Graph SDK usage.
Recommendations
- Provide Bash/Linux shell equivalents for all PowerShell variable assignments and command chaining.
- Include instructions for installing and using Microsoft Graph SDK on Linux, or offer alternative CLI-based approaches.
- Present Windows and Linux parameter file examples side-by-side or alternate their order to avoid Windows-first bias.
- Ensure all command output parsing (e.g., extracting IDs from az CLI output) is shown for both PowerShell and Bash (using jq or grep/awk).
- Review all steps for implicit Windows assumptions and clarify cross-platform compatibility.
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 provides both Linux and Windows options for deploying Intel SGX VMs, but there is a subtle Windows bias. Windows tools and patterns (such as PowerShell, RDP, and references to Windows authentication) are mentioned alongside or before Linux equivalents. The instructions for connecting to a VM mention PowerShell and Windows-specific scenarios before Linux, and there is a separate section for connecting to Windows VMs, but not for Linux. Additionally, Windows terminology (Administrator name, RDP) is used in places where Linux equivalents could be emphasized.
Recommendations
- Ensure Linux examples and terminology are presented first, especially in cross-platform sections.
- Provide explicit, step-by-step Linux connection instructions before Windows instructions.
- Use neutral terms (e.g., 'username' instead of 'Administrator name') where possible.
- Include Linux-specific troubleshooting or tips, such as using native SSH clients or OpenSSH on Linux.
- Balance references to Windows tools (PowerShell, RDP) with Linux tools (Bash, SSH) and avoid assuming Windows as the default environment.
- Add a dedicated section for connecting to Linux VMs, similar to the Windows VM connection section.
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 generally presents a balanced approach, but there are subtle signs of Windows bias. Windows terminology and tools (e.g., PowerShell, RDP) are mentioned alongside or before Linux equivalents in several places. The instructions for connecting to the VM mention PowerShell on Windows before Bash on Linux, and there are references to Windows-specific connection methods and tools. There is also a direct link to Windows-specific instructions for post-deployment steps, while Linux instructions are embedded in the main flow.
Recommendations
- Ensure Linux tools and workflows are mentioned before or alongside Windows equivalents, especially in connection instructions.
- Provide Linux and Windows examples in parallel where possible, rather than linking out to Windows instructions.
- Avoid referencing Windows-specific tools (e.g., PowerShell, RDP) before Linux tools unless the majority of users are expected to be on Windows.
- Where possible, provide explicit Linux command-line examples for all steps, not just for SSH.
- Add a section or links for post-deployment steps on Linux, similar to the Windows links provided.
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 shows moderate Windows bias in the advanced (customer-managed key) scenario. Several steps use PowerShell syntax and Windows-specific tools (e.g., Microsoft Graph PowerShell SDK) without providing equivalent Bash or cross-platform alternatives. PowerShell commands are interleaved with Azure CLI, and variables are set using PowerShell syntax, which may not work for Linux/macOS users. The initial sections are cross-platform, but the advanced scenario assumes a Windows/PowerShell environment. Linux parity is restored in the attestation section, which is Linux-focused.
Recommendations
- For every PowerShell command, provide a Bash (or cross-platform) equivalent, especially for variable assignment and Azure CLI invocations.
- Clearly separate Windows/PowerShell and Linux/Bash instructions, or provide tabs for both environments.
- For steps requiring Microsoft Graph, provide REST API or Azure CLI alternatives, or link to platform-agnostic instructions.
- Avoid using PowerShell-specific constructs (e.g., Out-String, ConvertFrom-Json, $var assignment) in mainline CLI documentation unless alternatives are shown.
- Review the order of examples to ensure neither Windows nor Linux is prioritized without justification.
- Add a note at the start of advanced sections clarifying which OS/shell the instructions target, and link to equivalents for other platforms.
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
Os Type Windows Default
Powershell Heavy
Summary
The documentation demonstrates a Windows bias in several ways: Windows is used as the default or sole OS example in disk creation commands (e.g., --os-type Windows), and PowerShell examples and notes are given equal or greater prominence than CLI or REST. There are no explicit Linux-specific examples or references to Linux disk types, and the documentation does not mention Linux-specific considerations or patterns. The ordering and language suggest Windows as the default use case.
Recommendations
- Provide explicit Linux examples in CLI and REST sections, e.g., use --os-type Linux and show a Linux disk creation workflow.
- Add notes or examples for Linux-specific scenarios, such as disk formats, guest state, or metadata differences.
- Balance PowerShell and CLI coverage by including Bash/Linux shell script examples where appropriate.
- Clarify that the feature is supported for both Windows and Linux VMs, and highlight any differences in usage or behavior.
- Avoid using Windows as the default in examples; alternate or show both OS types in sample commands.
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 mild Windows bias. Windows Server images are mentioned before Ubuntu images in several places, and the ARM template example lists Windows first. The only direct command-line example uses Azure CLI, which is cross-platform, but the command is shown with PowerShell-style backticks for line continuation, which is specific to Windows/PowerShell. There are no Linux shell (bash) examples, nor is there mention of Linux-specific deployment patterns or tools.
Recommendations
- Provide both Windows (PowerShell) and Linux (bash) command-line examples, especially for Azure CLI usage. Use bash-style line continuation (\) alongside PowerShell backticks.
- Alternate or randomize the order of OS images in examples and lists, or explicitly state that the order does not imply preference.
- Include references to Linux-specific deployment tools or patterns, such as cloud-init, where relevant.
- Ensure that links and instructions for ARM templates and VM creation reference both Windows and Linux documentation equally.
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 Windows bias by referencing Windows TPM documentation and features (e.g., links to Windows TPM overview, recommendations, Secure Boot, PCR banks) exclusively. There are no examples, references, or links to Linux TPM usage, tools, or documentation. The explanations and links assume familiarity with Windows-centric TPM concepts and do not mention Linux equivalents or how vTPMs are used in Linux confidential VMs.
Recommendations
- Add references and links to Linux TPM documentation, such as tpm2-tools and Linux kernel TPM support.
- Include examples or explanations of how vTPMs are used and accessed in Linux confidential VMs, including command-line usage.
- Mention Linux equivalents for features like Measured Boot and Secure Boot (e.g., Linux's IMA/EVM, UEFI Secure Boot).
- Provide parity in describing how PCRs and attestation are handled in Linux environments.
- Ensure that both Windows and Linux users are addressed in introductory and technical sections.
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
Missing Linux Example
Summary
The documentation page exhibits a notable Windows bias in the 'Customer Managed Key' section, where several steps use PowerShell syntax and Windows-specific tooling (e.g., Connect-Graph, New-MgServicePrincipal, Out-String, ConvertFrom-Json). These commands are not cross-platform and lack equivalent Bash/Linux examples, creating friction for Linux/macOS users. The rest of the guide is mostly Azure CLI-based and cross-platform, but the critical steps for customer-managed keys are Windows-centric.
Recommendations
- Provide Bash/Linux equivalents for all PowerShell commands, especially for Azure AD and Microsoft Graph interactions.
- Explicitly note which commands require Windows/PowerShell and offer alternatives for Linux/macOS users.
- Where possible, use Azure CLI or REST API calls instead of PowerShell modules.
- Add a dedicated section or callouts for Linux/macOS users to clarify how to perform each step without PowerShell.
- Ensure all example scripts and variable manipulations are shown in both Bash and PowerShell where applicable.
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
Missing Linux Example
Summary
The documentation page exhibits several Windows-centric biases. PowerShell is used exclusively for the key release operation example, with no Linux shell or cross-platform scripting alternatives provided. Windows tools and patterns (e.g., PowerShell, .ps1 scripts, Windows-specific binaries) are mentioned first or exclusively in critical sections, such as retrieving managed identity object IDs and performing the key release. Linux instructions are present for the attestation client, but the final key release operation lacks a Linux-native example, and Windows terminology (e.g., 'PS C:\>') is used throughout. This creates friction for Linux/macOS users who must adapt or translate Windows-specific instructions.
Recommendations
- Provide Linux/bash and cross-platform scripting examples for the key release operation, including curl or Python equivalents.
- Present Linux and Windows instructions in parallel tabs or sections, ensuring parity in detail and clarity.
- Reference Linux tools (e.g., Azure CLI, bash scripting) alongside PowerShell, not as an afterthought.
- Avoid using Windows-specific terminology or paths (e.g., 'PS C:\>') in generic instructions.
- Explicitly state cross-platform compatibility for binaries and scripts, and provide download/install instructions for both OSes.
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 demonstrates a moderate Windows bias. PowerShell syntax is used for variable assignment and command chaining, and Windows tools (PowerShell, Microsoft Graph SDK) are referenced in prerequisites and steps. Windows parameter file examples are presented before Linux ones. While Linux examples are present and most commands are cross-platform via Azure CLI, the use of PowerShell syntax and Windows-centric tooling may create friction for Linux/macOS users.
Recommendations
- Provide variable assignment and command chaining examples using Bash syntax alongside PowerShell, especially for Azure CLI commands.
- Clarify that Azure CLI commands can be run in Bash, and provide equivalent Bash variable assignment and usage.
- Mention installation instructions for Azure CLI and Microsoft Graph SDK for Linux/macOS, not just PowerShell.
- Present Linux and Windows parameter file examples side-by-side, or alternate which comes first.
- Where PowerShell is required (e.g., Connect-Graph), note alternatives or limitations for Linux/macOS users.
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 page demonstrates moderate Windows bias. PowerShell commands are provided for key steps (service principal opt-in), with no equivalent Azure CLI or Bash alternatives for Linux/macOS users. Windows tools (PuTTY) are mentioned repeatedly as SSH clients, and Windows connection instructions are referenced before Linux. Linux-specific instructions are less detailed, and Linux tools (native SSH, OpenSSH) are not mentioned. Azure CLI is only referenced indirectly, and not for critical steps.
Recommendations
- Provide Azure CLI or Bash equivalents for all PowerShell commands, especially for service principal opt-in and key creation.
- Mention native SSH clients (OpenSSH) for Linux/macOS users, not just PuTTY.
- Ensure Linux connection instructions are as detailed as Windows instructions.
- Present Linux/macOS examples and tools alongside or before Windows examples where appropriate.
- Add explicit instructions for Linux users for all critical steps, including disk encryption set creation and key management.
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 exhibits a Windows bias by referencing Windows TPM documentation, using Windows terminology and links, and omitting Linux/macOS-specific examples or guidance. All technical references and examples are Windows-centric, with no mention of Linux TPM tools, usage patterns, or relevant documentation for non-Windows platforms.
Recommendations
- Include references to Linux TPM documentation, such as tpm2-tools or Linux kernel TPM modules.
- Provide examples or guidance for using vTPMs in Linux confidential VMs, including commands and configuration steps.
- Mention cross-platform compatibility and any differences in vTPM usage between Windows and Linux.
- Add links to Linux-specific measured boot and secure boot documentation.
- Clarify whether macOS is supported or relevant, and provide guidance if applicable.
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 demonstrates a moderate Windows bias. Examples for Azure CLI and REST API are provided, which are cross-platform, but PowerShell examples are given equal or greater prominence, including detailed notes about PowerShell-specific syntax. All sample commands use Windows as the OS type, and there are no explicit Linux/macOS shell examples (e.g., bash, zsh) or references to Linux disk images. The documentation does not mention Linux-specific considerations or show Linux as an OS type in creation examples.
Recommendations
- Provide explicit Linux/macOS shell examples alongside PowerShell, especially for Azure CLI usage.
- Show disk creation examples with 'osType': 'Linux' and Linux VHD images.
- Add notes or sections clarifying cross-platform compatibility for CLI commands.
- Reduce PowerShell-specific notes or balance them with Linux shell tips (e.g., line continuation in bash).
- Ensure that Linux tools and workflows are mentioned where relevant, not just Windows/PowerShell.
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 shows moderate Windows bias. PowerShell is the only example given for service principal setup, and Windows tools (PuTTY) are mentioned first and most prominently for SSH. Windows connection instructions are referenced before Linux, and Linux connection steps rely on PuTTY (a Windows tool) rather than native SSH. There are no Linux CLI or shell examples for critical setup steps, and Linux users may need to infer or search for equivalents.
Recommendations
- Provide Azure CLI or Bash examples alongside PowerShell for service principal setup and key creation.
- Mention native SSH clients (ssh command) for Linux/macOS users before or alongside PuTTY.
- Include explicit Linux/macOS instructions for connecting to VMs using terminal SSH, not just PuTTY.
- Ensure that references to Windows and Linux tools are balanced, with Linux/macOS options shown first or equally.
- Add links to Linux-specific documentation for tasks currently only referenced with Windows tools.
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 demonstrates a moderate Windows bias. PowerShell syntax is used for variable assignment and scripting throughout, even in sections that are platform-agnostic or Linux-relevant. Windows parameter file examples are presented before Linux ones. There are explicit instructions to install PowerShell as a prerequisite, and some steps (e.g., using ConvertFrom-Json, Out-String) rely on PowerShell-specific tooling, which is not natively available on Linux/macOS. The use of Windows-centric tools and patterns may create friction for Linux users.
Recommendations
- Provide Bash shell equivalents for all variable assignments and scripting steps, especially those currently shown only in PowerShell.
- List Linux and Bash examples before or alongside Windows examples to avoid 'windows_first' bias.
- Clarify that PowerShell is optional for Linux/macOS users and provide instructions for using native shells.
- Replace or supplement PowerShell-specific commands (e.g., ConvertFrom-Json, Out-String) with cross-platform alternatives (jq, grep, etc.).
- Explicitly mention Linux/macOS compatibility in prerequisites and steps.
- Ensure all example parameter files and deployment commands have Linux versions with SSH key authentication and Bash syntax.
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
Missing Linux Example
Summary
The documentation page demonstrates notable Windows bias in the section on creating a confidential VM with a customer-managed key. Several critical steps use PowerShell syntax and Windows-specific tooling (e.g., Connect-Graph, New-MgServicePrincipal, Out-String, ConvertFrom-Json), with no equivalent Bash/Linux commands or guidance. This creates friction for Linux/macOS users, who may not have access to PowerShell or Microsoft Graph PowerShell SDK. The lack of Linux-native examples for service principal and key vault policy management is a significant gap, though the rest of the guide (resource group creation, VM deployment, attestation) is Bash/Azure CLI oriented.
Recommendations
- Provide Bash/Azure CLI equivalents for all PowerShell commands, especially for service principal creation and key vault policy management.
- Document how to perform Microsoft Graph operations using Azure CLI, REST API, or cross-platform tools.
- Clearly indicate which steps require PowerShell and offer alternatives for Linux/macOS users.
- Review and update examples to ensure Linux parity throughout, not just in attestation sections.
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 exhibits a Windows bias by referencing Windows-specific TPM documentation, tools, and concepts (such as Secure Boot and PCR banks) exclusively, without mentioning or providing equivalent Linux/macOS examples, tools, or workflows. All external links and terminology are Windows-centric, and no Linux-specific TPM usage or attestation guidance is provided.
Recommendations
- Include references to Linux TPM documentation (e.g., tpm2-tools, Linux kernel TPM subsystem).
- Provide examples or links for attesting vTPMs and using PCRs on Linux (e.g., using tpm2_pcrread, tpm2_quote).
- Mention Linux equivalents for Secure Boot and Measured Boot (e.g., Linux's UEFI Secure Boot, IMA/EVM for integrity measurement).
- Add guidance or links for macOS users if applicable, or clarify platform support.
- Ensure parity in terminology and workflows for both Windows and Linux environments.
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 page demonstrates a moderate Windows bias. While both Linux and Windows are referenced for the guest attestation client, the scripting example for performing the key release operation is provided only in PowerShell, which is natively a Windows tool (even though PowerShell Core is cross-platform, most Linux users prefer Bash or Python). Additionally, references to retrieving managed identity object IDs mention PowerShell before Azure CLI, and some instructions (such as VC_redist for Windows) are more detailed for Windows than Linux. The key release operation lacks a Linux-native example (e.g., Bash or Python), and the PowerShell example is shown without an equivalent for Linux/macOS users.
Recommendations
- Provide a Bash or Python example for the key release operation, showing how to use curl or Python requests to perform the HTTP POST to Key Vault.
- When listing ways to retrieve managed identity object IDs, mention Azure CLI and Linux-native tools first or equally.
- Clarify that PowerShell Core is cross-platform, but also offer examples in Linux-native scripting languages.
- Ensure parity in detail between Windows and Linux instructions (e.g., package installation, prerequisites).
Confidential Computing
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/confidential-computing/create-confidential-vm-from-compute-gallery.md
...mputing/create-confidential-vm-from-compute-gallery.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page exhibits mild Windows bias. Windows-specific scenarios (such as creating images from Windows confidential VMs with disk encryption) are mentioned explicitly, while Linux equivalents are not described in similar detail. In the steps for generalizing a VHD, the link to Linux instructions is provided after the Windows link, and no Linux-specific examples or considerations are given elsewhere. There are no command-line examples (e.g., PowerShell or Bash), but the narrative and links tend to prioritize or exclusively mention Windows workflows.
Recommendations
- Add explicit Linux scenarios and examples, such as creating images from Linux confidential VMs with disk encryption.
- Ensure Linux links and instructions are presented alongside or before Windows equivalents where applicable.
- Include Linux-specific considerations, such as differences in generalization, encryption, and supported OS features.
- If command-line examples are added, provide both Bash/Azure CLI and PowerShell examples for parity.
Confidential Computing
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/confidential-computing/key-rotation-offline.md
...rticles/confidential-computing/key-rotation-offline.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation exclusively describes key rotation using the Azure Portal GUI, which is a cross-platform web interface, but does not provide any command-line examples. There are no references to PowerShell, Windows tools, or CLI commands, but the lack of Azure CLI or Bash examples means Linux users do not have parity with Windows users who may be more accustomed to GUI or PowerShell workflows.
Recommendations
- Add Azure CLI examples for key rotation, including commands to stop VMs, update Disk Encryption Sets, and select keys.
- Provide Bash script snippets for automating key rotation tasks.
- Explicitly mention that the Azure Portal is cross-platform, but supplement with CLI instructions for users who prefer or require command-line workflows.
- Ensure that any future examples include both Azure CLI (Linux/macOS) and PowerShell (Windows) where relevant.
Confidential Computing
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/confidential-computing/migrate-nested-confidential-vms.md
...fidential-computing/migrate-nested-confidential-vms.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page exclusively describes migration steps using the Azure Portal GUI, which is most commonly used on Windows systems. There are no CLI, Powershell, or Bash examples, nor are Linux-specific tools or workflows mentioned. The screenshots and instructions assume a graphical interface, which is less common for Linux users who often prefer command-line automation.
Recommendations
- Add equivalent migration instructions using Azure CLI (az) commands, which are cross-platform and commonly used on Linux.
- Include examples for Powershell and Bash scripts to automate the migration process.
- Explicitly mention that the Azure Portal is accessible from any OS, but provide parity for users who prefer command-line or automated workflows.
- Reference Linux-friendly tools and patterns, such as using SSH, Bash scripting, or cloud-init for post-migration configuration.
Confidential Computing
Deploy Intel SGX virtual machines
...onfidential-computing/virtual-machine-solutions-sgx.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation page shows mild Windows bias. The Azure CLI example uses backticks (`) for line continuation, which is a PowerShell/Windows convention, and the ARM template deployment link points to a Windows-specific page. Windows Server images are mentioned before Ubuntu images in several places. However, Linux images (Ubuntu) are supported and referenced, and the Azure CLI is cross-platform.
Recommendations
- Provide Azure CLI examples using standard Bash syntax (backslash `\` for line continuation) alongside PowerShell examples.
- Link to both Windows and Linux ARM template deployment documentation, or use a neutral page.
- Alternate or randomize the order of OS images (Windows and Ubuntu) when listing supported images.
- Explicitly mention that Azure CLI commands work on Linux/macOS and provide example commands for those platforms.
- Ensure that any referenced tools or instructions are available and clear for Linux/macOS users.
Confidential Computing
Create a confidential VM from an Azure Compute Gallery image
...mputing/create-confidential-vm-from-compute-gallery.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Note
Missing Linux Example
Summary
The documentation page is generally platform-neutral, focusing on Azure portal workflows. However, there are subtle Windows biases: Windows is mentioned first in notes and example links, and Linux generalization is referenced only as a link, without explicit steps or parity in guidance. No command-line examples (PowerShell, CLI, Bash) are present, but Windows is prioritized in references.
Recommendations
- Present Linux and Windows generalization steps side-by-side, or at least with equal prominence.
- When referencing generalization, provide direct steps or examples for both Linux and Windows, not just links.
- Avoid mentioning Windows first in notes or examples; alternate or group by OS.
- Explicitly state that the process applies equally to Linux and Windows VMs, and clarify any OS-specific requirements.