Virtual Machines
1080
Total Pages
1005
Linux-Friendly Pages
75
Pages with Bias
6.9%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
815 issues found
Showing 451-475 of 815 flagged pages
Virtual Machines
Support matrix for VM restore points
...n/articles/virtual-machines/concepts-restore-points.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation presents Windows operating system support for application consistency before Linux, but otherwise provides parity in listing both Windows and Linux support. No Windows-only tools, examples, or patterns are given, and Linux support is clearly described. The 'Next steps' section references CLI, Portal, and PowerShell documentation equally, without favoring Windows tools.
Recommendations
- Consider listing Linux operating system support before Windows, or presenting both in a single table or section to avoid 'Windows first' bias.
- Ensure that linked 'CLI' and 'PowerShell' guides provide Linux and macOS examples where applicable.
Create Pull Request
Virtual Machines
Restrict managed disks from being imported or exported
...tual-machines/disks-restrict-import-export-overview.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides both Azure CLI and PowerShell options for configuring disk restrictions, but references to PowerShell and Windows-centric links appear before Linux equivalents. The custom RBAC role section links to a PowerShell-focused guide, and the Network access policy section mentions PowerShell alongside CLI, but the PowerShell link is listed first. There are no Linux-specific command examples or explicit parity in example ordering.
Recommendations
- Ensure that CLI (Linux/macOS-friendly) examples and links are presented before or alongside PowerShell/Windows examples.
- Add explicit Linux/macOS command examples where possible, especially for custom RBAC role creation and disk configuration.
- Link to general (platform-neutral) documentation for custom roles, not just PowerShell guides.
- Clarify that all steps can be performed on Linux/macOS using Azure CLI, and provide sample commands.
Virtual Machines
Customer intent: "As a cloud architect, I want to develop a robust backup and disaster recovery strategy for my Azure VMs and their managed disks, so that my organization can ensure data availability and minimize downtime during outages or data loss incidents."
...s/backup-and-disaster-recovery-for-azure-iaas-disks.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation is generally cross-platform, explicitly stating applicability to both Linux and Windows VMs. However, in several places, Windows tools and patterns (such as Volume Shadow Service and SQL Server Always On) are mentioned before their Linux equivalents. For example, application-consistent backup coordination is described first with Windows tools, and only later is fsfreeze for Linux mentioned, with less detail. SQL Server (Windows) backup scenarios are described in more depth than Oracle or other Linux-based databases. The comparison table also highlights Windows-specific benefits before Linux equivalents.
Recommendations
- Provide equal detail for Linux backup coordination tools (e.g., expand on fsfreeze and mention other Linux application-consistent backup solutions).
- When discussing database backup scenarios, include examples for Linux-based databases (e.g., Oracle, PostgreSQL) with links to relevant documentation.
- Ensure that Linux tools and patterns are mentioned alongside Windows tools, not after or as an afterthought.
- Where possible, add Linux-specific example commands or workflows for backup and disaster recovery.
- Review the comparison table and scenario descriptions to ensure Linux parity in benefits and operational considerations.
Virtual Machines
Best practices for virtual machine cost optimization
...s/virtual-machines/cost-optimization-best-practices.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation is generally cross-platform and neutral, but there is a minor instance of Windows bias: in the section about B-Series VMs for development and test environments, the guidance 'Use at least B2 for Windows machines' is given, while no equivalent recommendation is made for Linux machines. Additionally, Windows and Linux pricing links are presented together, but Windows is listed first. No PowerShell-heavy examples, Windows-only tools, or missing Linux examples are present.
Recommendations
- Provide equivalent guidance for Linux VM sizing if relevant (e.g., 'Use at least B2 for Linux machines' or clarify if Linux has different requirements).
- Ensure that recommendations for VM types, disk choices, and automation tools are explicitly applicable to both Windows and Linux, or clarify differences.
- Alternate the order of Windows and Linux links or present them together to avoid subtle Windows-first bias.
Virtual Machines
Server-side encryption of Azure Managed Disks
...blob/main/articles/virtual-machines/disk-encryption.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation generally provides parity between Windows and Linux, with clear references to both Azure PowerShell and Azure CLI for enabling encryption features. However, there is a mild 'windows_first' bias: PowerShell/Windows links and instructions are often listed before their Linux/CLI counterparts. Additionally, some references (such as to PowerShell for revoking access) appear before CLI, and the automatic key rotation walkthrough links only to a PowerShell-based guide, with no direct Linux/CLI equivalent linked in that section.
Recommendations
- Alternate the order of PowerShell and CLI/portal links throughout the documentation, or list CLI first in some sections to balance the presentation.
- Where a step-by-step guide is linked for PowerShell (e.g., automatic key rotation), ensure a corresponding CLI/Linux guide is linked alongside it if available.
- In sections referencing both PowerShell and CLI (such as revoking access), present both options together or in parallel, rather than PowerShell first.
- Consider adding explicit Linux/macOS/CLI code snippets or walkthroughs in sections that currently only link to Windows/PowerShell guides.
Virtual Machines
Secure Azure Managed Disk Downloads and Uploads
...icles/virtual-machines/disks-secure-upload-download.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides both Azure PowerShell and Azure CLI examples for securing managed disk uploads/downloads, but PowerShell examples are often presented before CLI, and references to PowerShell are slightly more prominent. However, Linux parity is generally maintained, with CLI instructions and Linux-specific links included in 'Next steps'.
Recommendations
- Ensure Azure CLI examples are presented alongside or before PowerShell examples, especially in sections relevant to cross-platform users.
- Explicitly mention that Azure CLI commands work on Linux/macOS and Windows, to reinforce cross-platform applicability.
- Add Bash or shell script examples where appropriate, especially for disk operations, to further assist Linux users.
- Review tab ordering and section headings to avoid subtle Windows-first presentation.
Virtual Machines
What's new in Azure Disk Storage
...blob/main/articles/virtual-machines/disks-whats-new.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation is primarily a changelog/news summary for Azure Disk Storage features and enhancements. While most content is platform-neutral, there are a few instances where Windows-specific links or references are listed before Linux equivalents, and some links point to Windows-specific documentation (e.g., 'expand-disks' and 'find-unattached-disks'). However, Linux parity is generally maintained, and most features are applicable to both Windows and Linux workloads.
Recommendations
- Ensure that links to both Windows and Linux documentation are provided wherever relevant, and avoid listing Windows links first unless the feature is Windows-only.
- Where features are cross-platform, provide examples or links for both Windows and Linux usage.
- Review linked documentation to confirm Linux parity and update summaries to mention Linux support when applicable.
- Consider adding a brief note clarifying platform applicability for each feature, especially when linking to platform-specific guides.
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation covers ephemeral OS disks for both Linux and Windows VMs, with clear applicability to both. However, there are minor signs of Windows bias: Windows-specific details (such as page file placement and Windows image sizing) are mentioned before Linux equivalents, and PowerShell is listed before CLI in the section on customer managed keys. Linux examples and tools are present but sometimes appear after Windows ones.
Recommendations
- Ensure Linux and Windows examples are presented with equal prominence and in parallel, rather than Windows first.
- When listing tooling (e.g., PowerShell, CLI), alternate the order or group them together as 'PowerShell/CLI/SDK' without preference.
- Add explicit Linux image sizing examples alongside Windows ones in all relevant sections.
- Where possible, provide Linux-specific operational details (e.g., swap file placement) in parity with Windows-specific notes.
Virtual Machines
Azure VM Extensions and Features for Linux
...articles/virtual-machines/extensions/features-linux.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples throughout, but PowerShell examples are consistently presented immediately after CLI, and sometimes with more detail. There is minor 'windows_first' bias in referencing PowerShell alongside CLI as a primary management tool, despite the Linux focus. However, all examples, screenshots, and guidance are tailored for Linux VMs, and Linux-specific tools (like waagent) are highlighted. No critical Linux gaps are present.
Recommendations
- Consider presenting Azure CLI examples before PowerShell in all sections, as CLI is more universal across platforms.
- Explicitly note that Azure PowerShell can be run on Linux/macOS, but CLI is often preferred for Linux workflows.
- Where possible, provide Bash shell script examples for common tasks (e.g., checking agent logs, troubleshooting) alongside CLI.
- Review for any subtle language implying PowerShell is the default or preferred tool for Linux VM management, and clarify parity.
- Add links or notes about using Azure CLI and PowerShell on Linux/macOS, including installation instructions.
Virtual Machines
NVIDIA GPU Driver Extension - Azure Linux VMs
...es/virtual-machines/extensions/hpccompute-gpu-linux.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation is primarily focused on Linux, as indicated by the title and content. However, PowerShell examples are provided alongside Azure CLI and ARM template examples for deploying the extension, and PowerShell is mentioned before Azure CLI in some sections. This may create minor friction for Linux users, as PowerShell is not a native Linux tool, though Azure CLI and ARM template examples are also present. There is a brief mention of a Windows extension, but it is appropriately separated and not the focus of the page.
Recommendations
- Move Azure CLI examples before PowerShell examples, as Azure CLI is more commonly used on Linux.
- Clearly indicate that PowerShell examples are primarily for Windows users, and Azure CLI is recommended for Linux/macOS.
- Consider adding Bash script examples for common operations, as Bash is native to Linux.
- Ensure troubleshooting sections prioritize Azure CLI and Bash commands over PowerShell.
Virtual Machines
Azure Key Vault VM Extension for Linux
...rticles/virtual-machines/extensions/key-vault-linux.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation is focused on Linux, but in several sections, Windows-oriented tools (PowerShell) are presented first or in greater detail than Linux-native alternatives. Azure PowerShell deployment instructions and troubleshooting are shown before Azure CLI, even though CLI is more cross-platform and native to Linux. Some PowerShell-specific warnings and examples are included, but Linux-specific shell or scripting guidance is minimal.
Recommendations
- Present Azure CLI examples and troubleshooting before PowerShell, as CLI is more native to Linux.
- Add Linux shell (bash) scripting examples for deploying the extension, especially for automation scenarios.
- Clarify that PowerShell instructions are optional for Linux users and highlight CLI as the preferred method.
- Include troubleshooting steps using Linux-native tools (journalctl, systemctl, etc.) for extension status.
- Ensure all JSON and deployment examples use Linux file path conventions and avoid Windows-specific syntax (e.g., backslashes).
Virtual Machines
Azure Disk Encryption scenarios on Linux VMs
...ticles/virtual-machines/linux/disk-encryption-linux.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for all major operations, but PowerShell (a Windows-centric tool) is often mentioned first or in more detail, and some backup/encryption instructions reference PowerShell cmdlets before CLI equivalents. Resource Manager template instructions also reference PowerShell and CLI, but PowerShell is sometimes prioritized. However, Azure CLI (cross-platform) is well-represented, and Linux-specific context is clear throughout.
Recommendations
- Ensure Azure CLI examples are always presented before PowerShell, as CLI is cross-platform and native to Linux.
- Where possible, clarify that PowerShell can be used on Linux/macOS (via Azure Cloud Shell or local installation), to reduce perceived Windows bias.
- Expand Linux-native tooling references (e.g., bash, shell scripting) where relevant, especially for disk management or backup operations.
- Avoid referencing PowerShell-specific parameters or behaviors before CLI equivalents unless necessary.
- Consider adding a brief note at the start of each section explaining that both CLI and PowerShell are supported on Linux, but CLI is often preferred for Linux users.
Virtual Machines
Create and upload a Red Hat Enterprise Linux VHD for use in Azure
...les/virtual-machines/linux/redhat-create-upload-vhd.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation covers preparing and uploading a Red Hat Enterprise Linux VHD for Azure, with detailed instructions for multiple hypervisors (Hyper-V, KVM, VMware, Kickstart). While Linux-centric throughout, the structure and ordering of sections consistently present Hyper-V (a Windows technology) instructions first for each RHEL version, followed by KVM, VMware, and Kickstart. This ordering may subtly signal Windows/Hyper-V as the default or preferred environment, despite full Linux support and parity in examples.
Recommendations
- Reorder hypervisor sections so that Linux-native options (KVM, Kickstart) appear before Hyper-V, or present all options in a neutral order (alphabetical or by popularity).
- Explicitly state that all hypervisor options are equally supported, and that users can choose based on their environment.
- Add a short introductory note clarifying that Hyper-V is not required, and that Linux-native workflows are fully supported.
- Consider grouping instructions by workflow (e.g., 'Linux-native', 'Windows/Hyper-V', 'VMware') to avoid implicit prioritization.
Virtual Machines
Time sync for Linux VMs in Azure
...blob/main/articles/virtual-machines/linux/time-sync.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation is focused on Linux VM time synchronization in Azure and provides extensive Linux-specific guidance, commands, and configuration examples. However, the introductory section discusses Windows Server 2016 time sync improvements and references Windows documentation before Linux-specific details. No PowerShell or Windows tool examples are given for Linux configuration, but a PowerShell command is shown for base64 encoding cloud-init (which is relevant for Azure users on any OS). All configuration guidance, tools, and examples are Linux-centric.
Recommendations
- Move or minimize the Windows Server 2016 discussion in the introduction, focusing first on Linux-specific mechanisms and their interaction with Azure infrastructure.
- Clarify that the PowerShell example for base64 encoding is for Azure users on Windows, and provide a Linux equivalent (e.g., 'base64 cloud-config.txt') for parity.
- Ensure that Linux guidance and examples are always presented before or alongside any Windows infrastructure references, unless Windows context is essential for understanding Azure's host time source.
Virtual Machines
Overview of Azure Disk Storage
...in/articles/virtual-machines/managed-disks-overview.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Minor Windows Reference
Summary
The documentation is generally balanced and covers both Linux and Windows VM scenarios. However, there are minor signs of Windows bias: Windows terminology and links are sometimes presented first (e.g., MBR/GPT partitioning), Windows-specific tools are referenced (e.g., Azure PowerShell), and some explanations use Windows-centric language (drive letters, Sysprep, etc.) before mentioning Linux equivalents. Linux examples and terminology are present, but occasionally appear after Windows references.
Recommendations
- Ensure Linux and Windows examples/tools are presented together or Linux-first where appropriate.
- When referencing partitioning (MBR/GPT), include links to Linux documentation or mention Linux partitioning tools.
- Where drive letters are discussed, clarify Linux device paths alongside Windows terminology.
- For upload instructions, ensure both Azure CLI (Linux) and PowerShell (Windows) links are equally prominent.
- When mentioning cluster managers, list Linux options (e.g., Pacemaker) before or alongside Windows options (e.g., WSFC).
Virtual Machines
Associate a virtual machine to a capacity reservation group
.../virtual-machines/capacity-reservation-associate-vm.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides both Windows (PowerShell) and cross-platform (Azure CLI, API, Portal) instructions for associating a VM to a capacity reservation group. However, there is a minor bias in the ARM template section, where only Windows VM images are shown by default, and the OSVersion parameter only lists Windows options. In all other sections, Linux is clearly supported and examples (e.g., CLI with Ubuntu image) are present. PowerShell is included as a tab equal to CLI, not prioritized above it.
Recommendations
- In the ARM template example, add a comment or alternative showing how to deploy a Linux VM (e.g., Ubuntu) by adjusting the imageReference and OSVersion parameters.
- In the OSVersion parameter, clarify that the template is for Windows VMs, or provide a Linux equivalent parameter and allowedValues.
- Consider adding a note in the ARM template section that Linux VMs are supported, with a link or snippet for a Linux image example.
Virtual Machines
Azure VM Extensions and Features for Linux
...articles/virtual-machines/extensions/features-linux.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples throughout, but consistently presents Azure CLI (Linux-friendly) examples before PowerShell. However, PowerShell examples are always included, even though PowerShell is less commonly used on Linux. There are no Windows-only tools or patterns mentioned, and all examples and screenshots are Linux-specific. The only minor bias is the inclusion of PowerShell examples, which may not be as relevant for Linux users, but this is mitigated by the clear focus on Linux tools and content.
Recommendations
- Consider clarifying that PowerShell examples are optional for Linux users, or note that Azure CLI is the primary cross-platform tool.
- Add brief guidance about PowerShell availability on Linux (if relevant), or link to Azure CLI installation instructions for Linux.
- Ensure that all troubleshooting and reference sections prioritize Linux-native commands and paths.
Virtual Machines
Customer intent: As a cloud administrator, I want to expand virtual machine disks efficiently, so that I can manage storage capacity without downtime and ensure optimal performance in my infrastructure.
...al-machines-disks-expand-without-downtime-restrictions.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation mentions both Windows and Linux VM disk rescan procedures, but the Windows rescan function is referenced before the Linux equivalent. All major tools (Azure CLI, PowerShell, Portal) are presented neutrally, but the order of Windows/Linux instructions shows minor Windows-first bias.
Recommendations
- Present Linux and Windows rescan instructions in parallel or list Linux first to balance visibility.
- Ensure that links to Linux documentation are as prominent and descriptive as Windows links.
- Consider adding explicit examples for both Linux and Windows disk expansion/rescan commands.
Virtual Machines
Enable Azure Disk Encryption for Linux VMs
...les/virtual-machines/linux/disk-encryption-overview.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation is focused on Linux VMs and provides Linux-centric instructions and examples. However, in several places, Azure PowerShell is mentioned alongside Azure CLI, and PowerShell examples/scripts are referenced equally or before Linux CLI equivalents. The 'Next steps' section lists both CLI and PowerShell quickstarts, with CLI first, but also includes PowerShell scripts. The terminology table includes 'PowerShell cmdlets' as a term, even though the feature is Linux-specific.
Recommendations
- Ensure that Linux CLI (bash) examples and scripts are always presented before PowerShell equivalents.
- Clarify that Azure PowerShell can be used cross-platform, but emphasize Linux-native tools (Azure CLI, bash) for Linux VM management.
- Consider removing or de-emphasizing PowerShell terminology unless it is critical for Linux users.
- If PowerShell is mentioned, explicitly note its cross-platform nature and relevance for Linux users.
Virtual Machines
Expand Virtual Hard Disks on a Linux VM
...b/main/articles/virtual-machines/linux/expand-disks.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Summary
The documentation is overwhelmingly Linux-focused, with detailed instructions and examples for Ubuntu, SUSE, and Red Hat distributions. However, in the section about classic VM SKU support for expanding disks without downtime, only a PowerShell script is provided to check SKU compatibility, with no equivalent Bash/Azure CLI example for Linux users.
Recommendations
- Add a Bash or Azure CLI example for checking classic VM SKU support, so Linux users can perform the same check without relying on PowerShell.
- Clarify that the PowerShell script is optional and provide guidance for Linux users on how to access this information via the Azure CLI or portal.
Virtual Machines
Time sync for Linux VMs in Azure
...blob/main/articles/virtual-machines/linux/time-sync.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation is focused on Linux VM time synchronization in Azure and provides comprehensive Linux-specific guidance, commands, and configuration examples. However, the introductory section discusses Windows Server 2016 and its time sync improvements before describing Linux mechanisms. References to Windows time service documentation are also given before Linux-specific details. No PowerShell or Windows tool examples are used for Linux configuration, except for a single PowerShell command to base64 encode a cloud-init file for use in an ARM template, which is relevant for cross-platform Azure users. All configuration and troubleshooting examples are Linux-centric.
Recommendations
- Move the Windows Server 2016 discussion to a background section or as a note, clarifying its relevance to Azure host time only.
- Prioritize Linux-specific information in the introduction and overview, mentioning Windows host context only as needed.
- Replace the PowerShell base64 example with a Linux equivalent (e.g., 'base64 cloud-config.txt') or provide both Windows and Linux commands for cross-platform parity.
- Ensure that all links and references to Windows documentation are clearly marked as background/context and not configuration guidance for Linux users.
Virtual Machines
Support matrix for VM restore points
...n/articles/virtual-machines/concepts-restore-points.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation presents Windows operating system support before Linux in the 'Operating system support for application consistency' section. However, both Windows and Linux are covered with comparable detail, and no Windows-specific tools, examples, or patterns are prioritized elsewhere. The 'Next steps' section lists CLI, Portal, and PowerShell options, with CLI (cross-platform) listed first.
Recommendations
- Consider listing Linux and Windows support together or in alphabetical order to avoid implicit prioritization.
- Ensure future examples and walkthroughs (linked pages) provide parity for Linux and Windows users, especially for CLI and PowerShell usage.
- Explicitly state that both Windows and Linux are equally supported where applicable.
Virtual Machines
Customer intent: "As a cloud architect, I want to develop a robust backup and disaster recovery strategy for my Azure VMs and their managed disks, so that my organization can ensure data availability and minimize downtime during outages or data loss incidents."
...s/backup-and-disaster-recovery-for-azure-iaas-disks.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation provides a balanced overview of backup and disaster recovery strategies for Azure Managed Disks, explicitly stating applicability to both Linux and Windows VMs. However, in several sections, Windows-specific tools and patterns (such as Volume Shadow Service for application-consistent backups and SQL Server Always On) are mentioned first or exclusively, with Linux equivalents (like fsfreeze) referenced later and with less detail. Some backup consistency options are described in more depth for Windows, and Windows examples (e.g., SQL Server) are more prominent than Linux database solutions.
Recommendations
- Provide equal detail for Linux tools and patterns (e.g., expand on fsfreeze and other Linux application-consistent backup options).
- Include Linux-first or Linux-specific examples alongside Windows examples, such as PostgreSQL or MySQL backup strategies.
- When mentioning Windows tools (e.g., Volume Shadow Service), immediately follow with Linux equivalents and clarify their limitations or strengths.
- Ensure comparison tables and scenario descriptions highlight Linux and Windows parity, including file system and application consistency for both platforms.
Virtual Machines
Best practices for virtual machine cost optimization
...s/virtual-machines/cost-optimization-best-practices.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides general best practices for virtual machine cost optimization and references both Windows and Linux VM pricing. However, there is a minor bias where Windows examples and recommendations (such as 'Use at least B2 for Windows machines' and Windows pricing links) are mentioned before Linux equivalents. There are no PowerShell-heavy examples, Windows-only tools, or missing Linux examples for general VM operations. The page is not Windows-specific and covers both OS types.
Recommendations
- When mentioning VM sizing recommendations, provide equivalent guidance for Linux VMs (e.g., 'Use at least B2 for Windows machines; for Linux, review minimum recommended sizes').
- Ensure that links to pricing and VM sizes for both Windows and Linux are presented together or in parallel, rather than Windows first.
- Where automation or shutdown examples are given, clarify that these apply to both Windows and Linux VMs, and provide links to relevant Linux automation documentation if available.
Virtual Machines
Server-side encryption of Azure Managed Disks
...blob/main/articles/virtual-machines/disk-encryption.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation covers both Linux and Windows VM scenarios and explicitly states applicability to both. However, throughout the page, Windows/PowerShell examples and links are consistently listed before Linux/CLI equivalents. References to PowerShell are frequent, sometimes with CLI mentioned second. There are no missing Linux examples or exclusive Windows tools; parity is maintained, but Windows is prioritized in ordering.
Recommendations
- Alternate the order of Windows and Linux examples/links, or list Linux/CLI first in some sections.
- Ensure that references to PowerShell and CLI are equally prominent, and avoid always listing PowerShell first.
- Consider adding explicit Linux/macOS command-line snippets or screenshots where relevant.
- Review for any subtle language that implies Windows is the default or primary platform.