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 51-75 of 83 flagged pages
Confidential Computing Create an Azure confidential VM in the Azure portal ...ntial-computing/quick-create-confidential-vm-portal.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page exhibits moderate Windows bias. PowerShell is used exclusively for service principal setup, with no Linux/CLI alternative provided. PuTTY (a Windows SSH client) is mentioned repeatedly as the primary SSH tool, and Windows connection instructions are referenced before Linux. Linux users are expected to adapt or find their own equivalents, which may create friction.
Recommendations
  • Provide Azure CLI or Bash alternatives for service principal setup, not just PowerShell.
  • Mention native Linux/macOS SSH clients (e.g., OpenSSH) before or alongside PuTTY.
  • Include explicit Linux/macOS command examples for connecting to VMs (e.g., 'ssh username@ip').
  • Ensure that Linux instructions are presented with equal prominence and detail as Windows instructions.
  • Add links to Linux/macOS-specific documentation where appropriate.
GitHub Create Pull Request
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 →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits a moderate Windows bias. The only full code example for performing the Secure Key Release operation is provided in PowerShell, which is Windows-centric, and references Windows-specific tools and patterns (e.g., System.Security.Cryptography.X509Certificates). While Linux is mentioned and supported in the attestation client section, there is no equivalent Linux shell script or code sample for the key release operation. Windows instructions and tools (PowerShell, MSVC runtime) are often mentioned first or exclusively, and Linux alternatives are not always provided with equal detail.
Recommendations
  • Provide a complete Linux shell (bash/curl) example for performing the key release operation, including obtaining an Azure AD token from IMDS and making the HTTP request to Key Vault.
  • Include cross-platform code samples (e.g., Python, curl, or REST API calls) for critical operations, not just PowerShell.
  • When referencing tools or libraries, mention Linux equivalents alongside Windows ones, and avoid Windows-first ordering.
  • Clarify which steps are identical across platforms and which require OS-specific instructions.
  • Add explicit notes or tables summarizing OS support and any differences in procedure.
GitHub Create Pull Request
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 →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page exhibits moderate Windows bias, especially in the section on creating confidential VMs with customer-managed keys. Several critical steps use PowerShell syntax and Windows-specific tooling (e.g., Connect-Graph, New-MgServicePrincipal), with no equivalent Linux/bash examples provided. This creates friction for Linux/macOS users, who may not have access to PowerShell or Microsoft Graph PowerShell SDK. Additionally, PowerShell commands are presented before or instead of bash alternatives, and some steps assume a Windows environment. The attestation section is Linux-focused, but the earlier VM creation steps lack Linux parity.
Recommendations
  • Provide bash/Azure CLI equivalents for all PowerShell commands, especially those involving Microsoft Graph and service principal creation.
  • Clearly indicate which steps require Windows/PowerShell and offer alternative instructions for Linux/macOS users.
  • Add notes or links to cross-platform tools or REST API equivalents for steps currently requiring PowerShell.
  • Ensure that Linux/macOS users can complete all critical tasks without needing Windows tools.
  • Reorder examples so that cross-platform or Linux/bash instructions are shown first or alongside Windows/PowerShell examples.
GitHub Create Pull Request
Confidential Computing Virtual Machine Metablob Disk ...onfidential-computing/virtual-machine-metablob-disk.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation displays a moderate Windows bias. In several examples, the OS type is set to 'Windows' by default, and PowerShell commands are given equal prominence to CLI, with detailed notes about PowerShell multiline syntax. There are no explicit Linux/macOS shell examples (e.g., Bash), and the CLI examples use variable syntax that is more common in Bash but do not clarify Linux/macOS usage. 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 (e.g., Bash) alongside PowerShell, especially for Azure CLI commands.
  • Show disk creation examples with 'osType' set to 'Linux' as well as 'Windows'.
  • Add notes or sections clarifying any differences or additional steps for Linux/macOS users.
  • Balance the order of examples so that Linux/Bash and Windows/PowerShell are presented equally, or alternate which comes first.
  • Remove unnecessary PowerShell-specific notes from sections that are not PowerShell-focused, or add equivalent notes for Bash if needed.
GitHub Create Pull Request
Confidential Computing Virtual TPMs in Azure confidential VMs ...ial-computing/virtual-tpms-in-azure-confidential-vm.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
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-specific TPM usage or examples. All external references and conceptual explanations are Windows-centric, with no mention of Linux tools, workflows, or equivalent documentation.
Recommendations
  • Include references to Linux TPM documentation, such as tpm2-tools and relevant Linux kernel documentation.
  • Provide examples or explanations for how vTPMs are accessed and used in Linux confidential VMs (e.g., using tpm2-tools, Linux attestation workflows).
  • Add links to cross-platform TPM resources and clarify that vTPMs are usable from both Windows and Linux guests.
  • Balance the order of references and examples so Linux is not implicitly deprioritized.
GitHub Create Pull Request
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 →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. While both Linux and Windows are mentioned for the guest attestation client, scripting examples for performing the key release operation are provided only in PowerShell, which is primarily a Windows tool (though available on Linux, it's less common in Linux workflows). The instructions for obtaining managed identity object IDs mention PowerShell first, and the main example for the key release operation is a PowerShell script, with no equivalent Bash, Python, or Linux-native example. Windows-specific tools (e.g., VC_redist.x64.exe) are referenced in the Windows section, and Windows instructions are often presented before or more prominently than Linux equivalents.
Recommendations
  • Provide a Bash or Python example for the key release operation, demonstrating how to perform the HTTP request and handle JWTs on Linux.
  • When listing ways to retrieve managed identity object IDs, mention Azure CLI and Linux-native tools before or alongside PowerShell.
  • Ensure that instructions and examples for both Windows and Linux are presented with equal prominence and in parallel tabs/sections.
  • Clarify that PowerShell Core is cross-platform, but also offer alternatives more familiar to Linux users.
  • Include troubleshooting steps and package installation instructions for Linux environments where PowerShell is not available.
GitHub Create Pull Request
Confidential Computing Create a confidential VM from an Azure Compute Gallery image ...mputing/create-confidential-vm-from-compute-gallery.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation exhibits mild Windows bias by mentioning Windows-specific scenarios (such as Windows confidential VM disk encryption) before Linux equivalents and by providing explicit links and instructions for generalizing Windows VHDs before Linux VHDs. Linux-specific instructions and references are present but are consistently listed after Windows, and there are no Linux command-line examples or Linux-specific tooling mentioned.
Recommendations
  • Present Linux and Windows instructions in parallel or in separate, equally prominent sections to avoid ordering bias.
  • Include explicit Linux examples and references wherever Windows examples are given (e.g., generalizing a Linux VM, encryption scenarios).
  • Add Linux command-line examples (such as Bash/Azure CLI) where relevant, not just portal-based instructions.
  • Ensure that references to Linux documentation are as visible and detailed as those for Windows.
  • Review notes and callouts to ensure Linux scenarios are not omitted or treated as secondary.
GitHub Create Pull Request
Confidential Computing About Azure confidential VMs ...les/confidential-computing/confidential-vm-overview.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation page exhibits mild Windows bias. Several key security features (TPM, Secure Boot, Live Migration, Dynamic Memory) are referenced using Windows-centric documentation links, and Windows terminology/tools are mentioned before or more prominently than Linux equivalents. In the benefits section, the TPM and Secure Boot features link to Windows documentation, and in the limitations section, features like Live Migration and Dynamic Memory are described using Windows Server/Hyper-V documentation. However, the OS support table lists Linux options first and provides parity in supported distributions.
Recommendations
  • Where possible, link to cross-platform or Linux-specific documentation for features like TPM and Secure Boot (e.g., Linux TPM documentation, Linux Secure Boot guides).
  • When mentioning features such as Live Migration or Dynamic Memory, clarify if and how these concepts apply to Linux guests or provide links to Linux virtualization documentation (e.g., KVM, QEMU, libvirt).
  • Balance references to Windows and Linux tools/documentation throughout the page, ensuring Linux users have equivalent guidance and resources.
  • Consider adding Linux-specific examples or usage patterns, especially for security and management features.
  • Review and update documentation links to avoid defaulting to Windows-centric sources when cross-platform alternatives exist.
GitHub Create Pull Request
Confidential Computing Deploy Intel SGX virtual machines ...onfidential-computing/virtual-machine-solutions-sgx.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation demonstrates a mild Windows bias by referencing Windows Server images before Linux equivalents in several places and linking to a Windows-specific ARM template guide. There are no explicit Linux-specific deployment examples or references to Linux tools, and the CLI example is generic (Azure CLI) rather than platform-specific. However, both Windows and Ubuntu images are mentioned as supported, and the pricing link points to Linux VMs.
Recommendations
  • Provide explicit Linux deployment examples, such as using Bash scripts or Linux-specific tooling alongside Azure CLI.
  • Ensure links to ARM template documentation include both Windows and Linux VM examples, or use a neutral entry point.
  • List supported OS images in a neutral order (alphabetically or grouped by type) to avoid Windows-first perception.
  • Add troubleshooting or operational notes relevant to Linux users, such as SELinux/AppArmor or package dependencies for SGX workloads.
GitHub Create Pull Request
Confidential Computing Create a confidential VM from an Azure Compute Gallery image ...mputing/create-confidential-vm-from-compute-gallery.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates subtle Windows bias by referencing Windows-specific scenarios first (e.g., mentioning Windows confidential VM disk encryption in the first note) and providing links to both Windows and Linux generalization steps, but listing the Windows link before the Linux link. There are no explicit Linux command-line examples, and the guidance is largely platform-neutral but leans toward Windows in ordering and specificity.
Recommendations
  • Ensure Linux examples and references are presented with equal prominence and ordering as Windows examples.
  • Add explicit Linux command-line or Azure CLI examples where relevant, especially for tasks like generalizing images or configuring encryption.
  • When mentioning platform-specific steps (e.g., generalizing a VHD), alternate the order between Windows and Linux, or present them side-by-side.
  • Include notes or guidance for common Linux scenarios, such as handling SSH keys, disk encryption, and OS-specific configuration nuances.
  • Review all references and links to ensure Linux documentation is as detailed and accessible as Windows documentation.
GitHub Create Pull Request
Confidential Computing Deploy Intel SGX virtual machines ...onfidential-computing/virtual-machine-solutions-sgx.md
Medium Priority View Details →
Scanned: 2026-01-10 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. In the ARM template deployment section, the link for further details points to a Windows-specific page ('Virtual machines in an Azure Resource Manager template' under /azure/virtual-machines/windows/template-description), while Linux equivalents are not mentioned or linked. Throughout the document, examples and instructions are generally platform-neutral, but there is a lack of Linux-specific guidance or parity in referenced resources.
Recommendations
  • Add links to Linux-specific ARM template documentation (e.g., /azure/virtual-machines/linux/template-description) alongside Windows links.
  • Ensure that examples and references for both Windows and Linux images are provided equally and in parallel.
  • Where platform-specific instructions or considerations exist (such as post-deployment configuration), include both Windows and Linux workflows.
  • Review referenced pages and ensure that both Windows and Linux users are guided to appropriate resources for further steps.
GitHub Create Pull Request
Confidential Computing About Azure confidential VMs ...les/confidential-computing/confidential-vm-overview.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation page exhibits mild Windows bias by referencing Windows-specific technologies and documentation before or exclusively, such as TPM and Secure Boot links pointing to Windows documentation, and feature support/limitations referencing Windows tools (e.g., Hyper-V live migration, dynamic memory). Linux support is present and OS parity is listed, but Windows-centric references and links appear first or exclusively in key sections.
Recommendations
  • Provide equivalent Linux documentation links for TPM and Secure Boot (e.g., link to Linux TPM and Secure Boot guides alongside Windows links).
  • Mention Linux virtualization technologies or migration tools where relevant, not just Windows/Hyper-V features.
  • Ensure that examples and references to OS features (e.g., boot diagnostics, dynamic memory) include Linux-specific notes or links if applicable.
  • Where Windows documentation is referenced, add Linux documentation in parallel or clarify cross-platform applicability.
  • Review feature support/limitations to clarify which limitations apply to Linux, Windows, or both, and provide Linux context where missing.
GitHub Create Pull Request
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
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page presents Windows and Linux options for Intel SGX VM deployment, but exhibits subtle Windows bias. Windows Server is mentioned before Ubuntu in several places (e.g., Gen2 OS image section), and the ARM template example lists the Windows image first. There are no explicit Linux-specific deployment examples or guidance, and the only CLI example uses Azure CLI, which is cross-platform, but no Linux shell-specific commands or PowerShell examples are provided.
Recommendations
  • Alternate the order of Windows and Linux references to avoid consistently listing Windows first.
  • Provide explicit Linux shell examples (e.g., bash) for Azure CLI usage, especially when showing command syntax.
  • Include Linux-specific deployment considerations, such as package installation or configuration steps for Ubuntu images.
  • Ensure parity in troubleshooting and operational guidance for both Windows and Linux images.
  • Add PowerShell examples only if Linux equivalents (bash, etc.) are also provided, or clarify cross-platform applicability.
GitHub Create Pull Request
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 →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a mild Windows bias. Windows-specific scenarios (such as creating images from Windows confidential VMs with disk encryption) are explicitly mentioned in notes, while equivalent Linux scenarios are not discussed. When generalizing VHDs, both Linux and Windows links are provided, but Windows is listed first. There are no command-line examples (e.g., Azure CLI, PowerShell), but the narrative and examples tend to reference Windows scenarios more directly and frequently, with Linux guidance only appearing as a secondary mention.
Recommendations
  • Add explicit Linux examples and scenarios, such as creating images from Linux confidential VMs with disk encryption.
  • Ensure that Linux and Windows instructions are presented with equal prominence, alternating which is listed first or grouping them together.
  • Include references to Linux-specific documentation and best practices for confidential VMs, especially where Windows-specific notes are given.
  • If command-line examples are added in future revisions, provide both Azure CLI (cross-platform) and PowerShell examples, with Linux parity in instructions and screenshots.
GitHub Create Pull Request
Confidential Computing https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/confidential-computing/confidential-vm-overview.md ...les/confidential-computing/confidential-vm-overview.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation page shows evidence of Windows bias primarily through the use of Windows-centric references and links. Trusted Platform Module (TPM) and Secure Boot are described with links to Windows documentation, and features like Live Migration and Dynamic Memory are referenced using Windows Server/Hyper-V documentation. In the feature support section, Windows tools and patterns are mentioned before or instead of Linux equivalents. However, the OS support table does list Linux distributions alongside Windows, and no command-line examples (PowerShell or Bash) are present.
Recommendations
  • Add links to equivalent Linux documentation for TPM and Secure Boot (e.g., Linux kernel or distribution-specific guides).
  • When mentioning features like Live Migration or Dynamic Memory, provide references to Linux virtualization technologies (e.g., KVM, libvirt) and their documentation.
  • Ensure that any tool or feature mentioned has both Windows and Linux context, or clarify if a feature is Windows-only.
  • Consider adding Linux-specific examples or workflows where relevant, especially for attestation and disk encryption.
  • Review all documentation links to ensure Linux parity and avoid defaulting to Windows documentation when cross-platform alternatives exist.
GitHub Create Pull Request
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 →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page exhibits mild Windows bias. Windows is mentioned first in notes about creating images with confidential compute disk encryption, and the process for generalizing a VHD gives the Windows link before the Linux link. There are no explicit Linux-specific examples or guidance, and the instructions are generic, portal-based, and do not provide parity for Linux-specific scenarios or tools.
Recommendations
  • Alternate the order of Windows and Linux references to avoid Windows-first bias.
  • Provide explicit Linux examples or guidance where relevant, such as generalizing Linux VMs or VHDs.
  • Include references to Linux-specific documentation and tools (e.g., cloud-init, SSH key setup) where appropriate.
  • Ensure that any notes or tips mentioning Windows also mention Linux equivalents, and vice versa.
  • Consider adding CLI-based instructions (e.g., Azure CLI, Bash) for Linux users alongside portal instructions.
GitHub Create Pull Request
Confidential Computing https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/confidential-computing/confidential-vm-overview.md ...les/confidential-computing/confidential-vm-overview.md
Medium Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation page exhibits mild Windows bias. References to Windows-specific technologies (such as TPM and Secure Boot) link to Microsoft/Windows documentation, and the Trusted Platform Module (TPM) section links exclusively to Windows resources. In the OS support table, while Linux options are listed first, Windows versions are described in greater detail and with more granularity. Some feature limitations reference Windows-centric features (e.g., Live Migration, Dynamic Memory) without Linux equivalents or context.
Recommendations
  • Provide equivalent Linux documentation links for technologies like TPM and Secure Boot (e.g., link to Linux TPM and Secure Boot documentation alongside Windows links).
  • When mentioning features like Live Migration or Dynamic Memory, clarify if there are Linux equivalents or note their absence for parity.
  • Ensure that Linux and Windows OS support are described with equal granularity and detail in tables and lists.
  • Where possible, include Linux-specific examples, tools, or references in addition to Windows ones, especially in sections discussing security technologies.
  • Review all external documentation links to ensure both Linux and Windows users are equally supported.
GitHub Create Pull Request
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 →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a subtle Windows bias by referencing Windows-specific scenarios (such as creating images from Windows confidential VMs) before mentioning Linux equivalents, and by not providing explicit Linux-focused examples or guidance. While there are some links to Linux generalization steps, the overall flow and examples are not balanced between Windows and Linux, and Linux-specific considerations are not highlighted.
Recommendations
  • Add explicit Linux-focused examples and scenarios alongside Windows examples, especially when discussing image creation and generalization.
  • Ensure that references to generalization steps for both Linux and Windows are given equal prominence and are mentioned together, rather than Windows first.
  • Include notes or sections that address Linux-specific requirements or caveats for confidential VMs, such as supported distributions, kernel versions, or configuration steps.
  • Where possible, provide parity in screenshots or step-by-step instructions for both Windows and Linux VM images.
  • Review the order of presentation to avoid consistently mentioning Windows before Linux, and strive for a neutral or alternating order.
GitHub Create Pull Request
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
Medium Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation generally maintains parity between Windows and Linux in terms of supported images and references. However, there is a subtle 'windows_first' bias: in the ARM template deployment section, the link for further information points to a Windows-specific template description page, and the Windows image is listed first in the example image references. There are no explicit Linux command-line examples (e.g., bash), and the Azure CLI example uses PowerShell-style backticks for line continuation, which may confuse Linux users. No Linux-specific deployment patterns or tools are mentioned.
Recommendations
  • Provide links to both Windows and Linux ARM template documentation, or use a neutral, combined page.
  • List Linux and Windows images in a neutral or alternating order, or clarify that the order is not significant.
  • Use bash-style line continuation (backslash) in Azure CLI examples or provide both PowerShell and bash variants.
  • Explicitly mention Linux deployment considerations or tools where relevant, ensuring Linux users are equally supported.
GitHub Create Pull Request
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-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation references both Windows and Linux in generalization steps, but Windows examples and notes are presented first, and there are no concrete, step-by-step CLI or portal examples specifically for Linux users. The only explicit Linux mention is a link to generalizing a Linux VHD, which is listed after the Windows equivalent. There are no Linux-specific patterns, troubleshooting, or parity in examples.
Recommendations
  • Provide explicit, step-by-step examples for Linux VMs alongside Windows examples, including portal and CLI workflows.
  • Ensure Linux links and instructions are presented with equal prominence and order as Windows equivalents.
  • Include troubleshooting notes or tips for common Linux-specific issues in confidential VM creation.
  • Clarify any differences in supported features or limitations for Linux confidential VMs.
GitHub Create Pull Request
Confidential Computing About Azure confidential VMs ...les/confidential-computing/confidential-vm-overview.md
Low Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation page for Azure confidential VMs shows minor Windows bias. Several key security features (TPM, Secure Boot) are linked to Windows documentation, and Windows terminology/tools are referenced (e.g., Windows TPM, Secure Boot, Live Migration) without Linux equivalents or links. In feature lists and limitations, Windows features are mentioned first or exclusively. However, Linux support is clearly documented, and supported Linux OS images are listed alongside Windows.
Recommendations
  • Provide equivalent Linux documentation links for TPM and Secure Boot (e.g., point to Linux kernel docs or distribution-specific guides).
  • Mention Linux tools and patterns for attestation, disk encryption, and boot security where relevant.
  • Balance references to Windows and Linux features/tools in feature lists and limitations.
  • Where Windows-specific features are listed (e.g., Live Migration), clarify Linux alternatives or state if not applicable.
  • Ensure examples and links are provided for both Linux and Windows users, especially for security and management tasks.
GitHub Create Pull Request
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-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation is generally balanced, but there are subtle Windows biases: Windows is mentioned first in some places, Windows tools (PowerShell, RDP) are referenced before Linux equivalents, and instructions for connecting to VMs mention PowerShell for Windows users. However, Linux is well-supported, with Ubuntu as the default image and SSH instructions provided.
Recommendations
  • Present Linux and Windows options side-by-side or alternate which is shown first.
  • Explicitly mention Linux tools (e.g., Bash, Terminal) before or alongside Windows tools.
  • Provide direct links to Linux/macOS connection guides in the 'Connect to the Linux VM' section.
  • Ensure parity in post-deployment instructions (e.g., SDK install guides for both OSes).
GitHub 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 →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
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 terminology (RDP, PowerShell) is mentioned before Linux equivalents (SSH, Bash) in several places. Windows tools and connection methods are referenced explicitly, and Windows VM connection instructions are linked separately, while Linux connection steps are included inline. However, Linux is well-supported overall, with Ubuntu as the default image and SSH as the recommended authentication method.
Recommendations
  • Present Linux and Windows instructions in parallel, rather than referencing Windows steps separately.
  • List SSH/Bash (Linux/macOS) connection instructions before PowerShell/Windows alternatives.
  • Include explicit Linux/macOS tool recommendations (e.g., Terminal, iTerm2) alongside Windows tools.
  • Ensure examples and screenshots are balanced between platforms.
  • Clarify that both platforms are equally supported and provide parity in troubleshooting and next steps.
GitHub Create Pull Request
Confidential Computing Deploy Intel SGX virtual machines ...onfidential-computing/virtual-machine-solutions-sgx.md
Low Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Minor Windows Tools
Summary
The documentation provides both Windows and Linux (Ubuntu) examples for deploying Intel SGX VMs, including ARM template image references and links to Linux pricing. However, there is a slight Windows bias: Windows Server is listed first in the Gen2 OS image examples, and the ARM template deployment link points to a Windows-specific page. No PowerShell-only or Windows-only tools are used, and Azure CLI is cross-platform.
Recommendations
  • List Linux (Ubuntu) images before Windows Server in examples to avoid implicit prioritization.
  • Provide a link to ARM template deployment documentation for Linux VMs alongside the Windows link.
  • Ensure that any referenced quickstart or template pages include both Linux and Windows examples.
  • Explicitly state that Azure CLI commands work on Linux/macOS as well as Windows.
GitHub Create Pull Request
Confidential Computing About Azure confidential VMs ...les/confidential-computing/confidential-vm-overview.md
Low Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Windows Links
Summary
The documentation page exhibits mild Windows bias. Windows-specific tools and documentation are referenced before or more prominently than Linux equivalents (e.g., TPM and Secure Boot links point to Windows docs). Some features and limitations reference Windows technologies (like Hyper-V live migration, dynamic memory) without mentioning Linux alternatives. However, Linux support is clearly listed in the OS support table, and no critical steps are Windows-only.
Recommendations
  • Provide equivalent Linux documentation links for TPM and Secure Boot (e.g., point to Linux TPM usage guides or UEFI Secure Boot on Linux).
  • When referencing features or limitations (e.g., live migration, dynamic memory), clarify if/how these apply to Linux guests, or mention Linux-specific technologies if relevant.
  • Ensure that examples, guides, and references are balanced between Windows and Linux, especially in sections discussing security features and VM management.
  • Consider listing Linux OS options first in tables or examples to avoid subtle ordering bias.
GitHub Create Pull Request
← Previous Page 3 of 4 Next →