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 26-34 of 34 flagged pages
Confidential Computing
About Azure confidential VMs
...les/confidential-computing/confidential-vm-overview.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page shows mild Windows bias, primarily in the form of linking to Windows-specific resources (such as TPM and Secure Boot documentation) and listing Windows tools and features before Linux equivalents. However, Linux support is clearly documented, and there are no critical omissions preventing Linux users from understanding or using confidential VMs.
Recommendations
- Provide links to equivalent Linux documentation for TPM and Secure Boot, such as Linux TPM usage guides or UEFI/Secure Boot documentation for Linux distributions.
- When referencing features like Trusted Platform Module or Secure Boot, mention both Windows and Linux support and link to relevant Linux resources.
- Ensure that examples, if added in future, include both Linux and Windows usage patterns.
- Consider listing Linux and Windows OS options in parallel or alternating order to avoid implicit prioritization.
Create Pull Request
Confidential Computing
Quickstart - Create Intel SGX VM in the Azure Marketplace
...les/confidential-computing/quick-create-marketplace.md
Low 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 slight Windows bias. Windows tools and terminology (e.g., RDP, PowerShell) are mentioned first or more prominently in several sections. The SSH example for Linux is present, but Windows connection instructions are linked out rather than shown inline. Windows-specific advice (e.g., using PowerShell, RDP, Win32 OpenSSH, WSL) appears before Linux alternatives, and some steps are described from a Windows-centric perspective.
Recommendations
- Present Linux and Windows instructions side-by-side or in parallel sections, rather than referencing Windows tools first.
- Include direct Linux/macOS connection instructions and troubleshooting tips, not just links.
- When mentioning tools, list Linux/macOS options first or equally (e.g., 'Open your SSH client of choice, such as Bash on Linux, Terminal on macOS, or PowerShell on Windows').
- Provide explicit Linux/macOS examples for all steps, not just for SSH connection.
- Avoid language that assumes Windows as the default platform.
Confidential Computing
Quickstart - Create Intel SGX VM in the Azure Portal
...articles/confidential-computing/quick-create-portal.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Summary
The documentation provides a generally balanced approach for both Linux and Windows users, but there are subtle signs of Windows bias. Windows terminology (like RDP, PowerShell) is mentioned before Linux equivalents in several places, and Windows tools are referenced (e.g., PowerShell, Win32 OpenSSH) with workarounds for older Windows versions. The connection instructions mention Bash and PowerShell, but PowerShell is listed first. The instructions for connecting to a Windows VM are linked out, while Linux instructions are included inline. There are no Linux-specific commands missing, but Windows patterns and tools are often mentioned before Linux ones.
Recommendations
- Present Linux and Windows instructions in parallel, rather than referencing Windows steps as an afterthought.
- List Linux tools and patterns before Windows ones when both are supported.
- Include explicit Linux/macOS command examples where possible, not just references.
- Avoid assuming PowerShell as the default cross-platform tool; mention Bash or terminal first.
- Provide direct links to Linux/macOS-specific documentation in the 'Next steps' section.
Confidential Computing
Virtual Machine Metablob Disk
...onfidential-computing/virtual-machine-metablob-disk.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation shows a mild Windows bias: examples consistently use Windows-centric values (e.g., osType: Windows), PowerShell is given equal prominence to CLI, and there are no explicit Linux/macOS shell examples or mentions of Linux-specific patterns. The CLI examples use generic shell syntax but do not clarify Linux/macOS compatibility or show Linux-specific values (e.g., osType: Linux). The PowerShell section includes detailed notes about multiline syntax, which is only relevant for Windows users.
Recommendations
- Add explicit Linux/macOS shell examples, including setting osType: Linux in sample requests.
- Clarify that Azure CLI commands work on Linux/macOS and show example environment variable usage for those platforms.
- Include notes or examples for bash/zsh users, especially for multiline commands.
- Balance PowerShell and shell examples, and avoid Windows-specific notes unless mirrored for Linux/macOS.
- In REST API examples, alternate between Windows and Linux values for osType and related fields.
Confidential Computing
About Azure confidential VMs
...les/confidential-computing/confidential-vm-overview.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Windows Links
Summary
The documentation page for Azure confidential VMs shows mild Windows bias. Several key security features (TPM, Secure Boot) link to Windows-focused documentation, and Windows terminology/tools are referenced before or instead of Linux equivalents. The Secure Boot and TPM sections reference Windows documentation, and the limitations section includes links to Windows Server features. However, Linux support is clearly listed in the OS support table, and no critical steps are Windows-only.
Recommendations
- Add equivalent Linux documentation links for TPM and Secure Boot (e.g., point to Linux kernel or distribution documentation on Secure Boot and TPM usage).
- When mentioning features like Secure Boot or TPM, clarify how they apply to Linux VMs and provide Linux-specific guidance or references.
- In limitations, balance references to Windows features (e.g., Hyper-V live migration) with Linux virtualization equivalents if relevant.
- Ensure that examples, guides, and links are provided for both Windows and Linux users wherever possible.
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 demonstrates mild Windows bias by referencing Windows-specific scenarios first (e.g., notes about Windows confidential VM disk encryption), and by linking to Windows generalization instructions before Linux equivalents. Linux instructions are present but are mentioned after Windows, and no Linux-specific examples or screenshots are provided. There are no CLI, PowerShell, or platform-specific tool examples, but the overall flow assumes parity between Windows and Linux, with minor prioritization of Windows.
Recommendations
- Present Linux and Windows instructions side-by-side or in parallel, rather than listing Windows first.
- Include explicit Linux-specific examples, screenshots, or notes where relevant (e.g., generalizing a Linux VHD).
- Add a table or section summarizing differences or requirements for Linux vs. Windows confidential VMs.
- Ensure that links to Linux documentation are as prominent as those for Windows.
- Clarify any steps that differ for Linux users, such as disk preparation or encryption settings.
Confidential Computing
Quickstart - Create Intel SGX VM in the Azure Marketplace
...les/confidential-computing/quick-create-marketplace.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation generally maintains parity between Windows and Linux, but there are subtle biases: Windows terminology and tools (PowerShell, RDP) are mentioned first or more prominently in several places, and Windows-specific instructions are referenced before Linux equivalents. The SSH example is cross-platform, but Windows tools (PowerShell, WSL) are highlighted. Linux instructions are present, but sometimes appear as secondary or after Windows notes.
Recommendations
- Present Linux and Windows instructions in parallel, rather than referencing Windows steps first or as the default.
- When mentioning tools, list Linux/macOS options before or alongside Windows tools (e.g., 'Open your SSH client of choice, such as Bash on Linux/macOS, or PowerShell/WSL on Windows').
- Provide direct links to Linux/macOS connection guides in the same way as for Windows.
- Avoid language that implies Windows is the default (e.g., 'If you deployed a Windows VM, follow these steps...' could be rephrased to treat both OSes equally).
- Ensure that Linux-specific steps (such as SSH key generation) are as detailed and visible as Windows steps.
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
Summary
The documentation page demonstrates minor 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 documentation page. However, Linux images and options are mentioned alongside Windows, and the Azure CLI is cross-platform.
Recommendations
- Provide Azure CLI examples using standard Bash syntax (backslash for line continuation) or clarify cross-platform usage.
- Link to both Windows and Linux ARM template documentation, or use a neutral page covering both.
- Ensure that examples and instructions are presented in a platform-neutral way, or provide both Windows and Linux/macOS variants where conventions differ.
Confidential Computing
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/confidential-computing/confidential-computing-enclaves.md
...fidential-computing/confidential-computing-enclaves.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation does not provide any platform-specific examples or instructions, but it also does not mention or highlight any Windows-specific tools, commands, or patterns. However, it lacks explicit examples or guidance for Linux users, which may leave Linux developers uncertain about platform compatibility or required steps.
Recommendations
- Add explicit statements clarifying that SGX development is supported on both Windows and Linux platforms.
- Include links or references to Linux-specific SGX development tools (e.g., Intel SGX SDK for Linux) alongside any Windows equivalents.
- Provide example workflows or commands for both Windows (e.g., Visual Studio, PowerShell) and Linux (e.g., GCC, Bash) environments in the 'Developing for enclaves' section.
- Mention any platform-specific requirements or differences in the development and deployment process for SGX enclaves.