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 76-83 of 83 flagged pages
Confidential Computing Create a confidential VM from an Azure Compute Gallery image ...mputing/create-confidential-vm-from-compute-gallery.md
Low Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation shows mild Windows bias by mentioning Windows-specific scenarios and links before Linux equivalents, and by providing more detailed guidance for Windows confidential VM images. Linux examples are referenced but not elaborated, and Linux-specific steps are only linked, not described inline.
Recommendations
  • Provide explicit step-by-step examples for Linux VMs, matching the detail given for Windows.
  • Ensure Linux generalization/upload instructions are described inline, not just linked.
  • Balance references to Windows and Linux throughout, mentioning both platforms equally in notes and examples.
  • Add screenshots or UI guidance for Linux-specific scenarios where relevant.
Confidential Computing Quickstart - Create Intel SGX VM in the Azure Marketplace ...les/confidential-computing/quick-create-marketplace.md
Low Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation provides both Linux and Windows options for deploying Intel SGX VMs, but there are several subtle biases toward Windows. Windows tools and workflows (e.g., PowerShell, RDP) are mentioned first or given prominence, and instructions for connecting to VMs reference PowerShell before Bash. Windows-specific guidance is provided in separate sections, while Linux instructions are more generalized. There is some parity, but Windows patterns are often foregrounded.
Recommendations
  • Present Linux and Windows options in parallel, rather than referencing Windows tools first.
  • When mentioning SSH clients, list Bash (Linux/macOS) before PowerShell (Windows), or present both equally.
  • Provide explicit Linux/macOS instructions for all steps, including connecting and resource cleanup.
  • Ensure screenshots and examples alternate or show both OSes where relevant.
  • Add more direct links to Linux/macOS documentation for tasks like SSH key generation and VM connection.
Confidential Computing Quickstart - Create Intel SGX VM in the Azure Portal ...articles/confidential-computing/quick-create-portal.md
Low Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation page demonstrates mild Windows bias by mentioning Windows tools (PowerShell, RDP) and connection patterns before or alongside Linux equivalents. Windows VM connection instructions are referenced but not detailed, while Linux SSH instructions are included directly. Windows-specific tools (PowerShell) are suggested for SSH, and Windows connection steps are linked out rather than explained inline. However, Linux is well-represented, with Ubuntu as the default image and direct SSH instructions.
Recommendations
  • Provide direct, step-by-step connection instructions for Windows VMs (e.g., using RDP) within the main flow, similar to the Linux SSH example.
  • List Linux and Windows connection methods side-by-side, or in parallel sections, to avoid implicit prioritization.
  • Mention Linux tools (e.g., Bash, Terminal) before or alongside Windows tools (PowerShell) when discussing SSH clients.
  • Ensure parity in example detail: if Linux connection is shown inline, do the same for Windows.
  • Consider adding macOS-specific notes where relevant (e.g., SSH from Terminal).
Confidential Computing Quickstart - Create Intel SGX VM in the Azure Marketplace ...les/confidential-computing/quick-create-marketplace.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation page generally maintains parity between Windows and Linux, but there are subtle signs of Windows bias. Windows tools (PowerShell, RDP) are mentioned first or in parallel with Linux equivalents, and instructions sometimes reference Windows-specific patterns before Linux ones. The SSH example is generic, but PowerShell is mentioned as an SSH client before Bash. There are no Linux-specific command-line examples for VM creation, and the connection instructions reference Windows tools and workarounds (WSL, Azure Cloud Shell) for older Windows versions.
Recommendations
  • Present Linux and macOS tools/examples before or alongside Windows ones, especially in connection instructions.
  • Add explicit Linux/macOS CLI examples for VM creation and management, not just portal-based instructions.
  • Avoid referencing Windows tools (PowerShell, RDP) before Linux equivalents (Bash, SSH) in generic instructions.
  • Ensure parity in troubleshooting and driver update instructions for both platforms.
  • Consider a dedicated section for Linux/macOS users, highlighting platform-specific tips and best practices.
Confidential Computing Use Microsoft Defender for Cloud with guest attestation for Azure confidential VMs ...tial-computing/guest-attestation-defender-for-cloud.md
Low Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Missing Linux Example
Summary
The documentation mentions support for both Windows and Linux confidential VMs, but does not provide any OS-specific examples, commands, or instructions. There is no evidence of Windows-specific tools or PowerShell usage, but the lack of explicit Linux examples or references to Linux tooling may hinder Linux users.
Recommendations
  • Add explicit examples for both Windows and Linux, such as installation steps for the guest attestation extension using both PowerShell (Windows) and Bash/CLI (Linux).
  • Reference Linux-specific tools or commands where relevant, such as using Azure CLI or cloud-init for Linux VM configuration.
  • Ensure that troubleshooting and alert suppression instructions include Linux-specific guidance, not just generic or Windows-centric advice.
  • Where sample applications or APIs are mentioned, clarify if they are cross-platform or provide separate instructions for Linux environments.
Confidential Computing https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/confidential-computing/guest-attestation-defender-for-cloud.md ...tial-computing/guest-attestation-defender-for-cloud.md
Low Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Missing Linux Example
Summary
The documentation claims support for both Windows and Linux confidential VMs, but does not provide any OS-specific examples, commands, or instructions. There is no evidence of Windows-specific tools or PowerShell usage, but the lack of explicit Linux examples or mention of Linux tooling may leave Linux users underserved.
Recommendations
  • Add explicit examples for both Windows and Linux, such as installation steps for the guest attestation extension using common Linux tools (e.g., Azure CLI, shell commands) and Windows tools (e.g., PowerShell).
  • Include troubleshooting steps or alert handling instructions tailored for Linux environments.
  • Reference Linux-specific documentation or resources where appropriate.
  • Clarify any differences in feature support or configuration between Windows and Linux confidential VMs.
Confidential Computing https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/confidential-computing/attestation.md ...ob/main/articles/confidential-computing/attestation.md
Low Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 1 bias type
Detected Bias Types
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.
Confidential Computing https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/confidential-computing/attestation.md ...ob/main/articles/confidential-computing/attestation.md
Low Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 1 bias type
Detected Bias Types
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.
Previous Page 4 of 4 Next