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 301-325 of 815 flagged pages
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
Minor Windows Reference
Summary
The documentation is primarily focused on Linux, as expected given the page title and scope. However, there are minor instances of Windows bias: (1) PowerShell deployment instructions are presented before Azure CLI instructions, which may be less relevant to Linux users; (2) Some notes reference Windows documentation or PowerShell tools first; (3) Troubleshooting and deployment sections sometimes mention PowerShell before CLI, even though CLI is more commonly used on Linux. No critical Linux gaps are present, and all examples, paths, and instructions are Linux-centric.
Recommendations
- Present Azure CLI deployment instructions before PowerShell, as CLI is more relevant for Linux users.
- Where possible, avoid referencing Windows-specific documentation or tools unless necessary for context.
- Ensure troubleshooting steps prioritize Azure CLI and Linux-native tools.
- Clarify that PowerShell instructions are optional for users who prefer it, but Azure CLI is the default for Linux.
Create Pull Request
Low Priority
View Details →
Detected Bias Types
Windows First
Minor Powershell Reference
Summary
The documentation covers ephemeral OS disks for both Linux and Windows VMs, with clear parity in feature descriptions and examples. However, there are minor instances where Windows-specific information is presented first or in more detail (e.g., page file placement, cache size example), and PowerShell is mentioned before CLI in the customer-managed key section. Linux examples are present and not omitted, but Windows details sometimes precede Linux equivalents.
Recommendations
- Ensure Linux and Windows examples are presented with equal prominence and in parallel where possible.
- When referencing tools (e.g., PowerShell, CLI), alternate their order or present them together to avoid Windows-first bias.
- Provide explicit Linux command examples alongside Windows/PowerShell ones in deployment and configuration sections.
- Clarify when information is Windows-specific and provide Linux-specific details in the same section.
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 is generally Linux-focused, as expected from its title and content. However, throughout the page, Azure CLI and Azure PowerShell examples are consistently paired, with PowerShell examples always present and sometimes shown immediately after CLI. PowerShell is a Windows-centric tool, and its inclusion alongside CLI in every section may create friction for Linux/macOS users, especially since PowerShell is not a default shell on Linux. Additionally, references to Azure PowerShell are frequent and sometimes precede CLI or are given equal prominence, despite the Linux audience.
Recommendations
- Consider prioritizing Azure CLI examples, as CLI is cross-platform and native to Linux/macOS users.
- Where PowerShell is included, clarify its availability on Linux and provide installation guidance or links.
- In sections where both CLI and PowerShell are shown, ensure CLI is presented first, or mark PowerShell as optional for users who prefer it.
- Add Bash or shell script examples where relevant, especially for troubleshooting or agent operations.
- Review the use of PowerShell in ARM template sections and ensure Linux-native tools (like CLI or Bash) are emphasized.
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 focused on Linux Azure VMs, but includes PowerShell examples alongside Azure CLI and ARM template examples. In the deployment section, PowerShell is presented before Azure CLI, which is more commonly used on Linux. There is also a brief mention of a Windows extension, but this is appropriate for cross-referencing. The troubleshooting section provides both PowerShell and Azure CLI commands, but PowerShell is listed first. All technical instructions, screenshots, and manual steps are Linux-specific, and there are no Windows-only tools or patterns used for critical tasks.
Recommendations
- Present Azure CLI examples before PowerShell, as CLI is the primary cross-platform tool and preferred on Linux.
- Explicitly note that PowerShell examples are optional and primarily for users on Windows or those who prefer PowerShell.
- Consider removing or de-emphasizing PowerShell examples unless there is a clear use case for Linux users.
- Ensure troubleshooting commands prioritize Azure CLI and Bash, with PowerShell as an alternative.
- Add a short note clarifying that all instructions are for Linux VMs, and PowerShell is included for completeness.
Virtual Machines
Create an image definition and image version
...s/blob/main/articles/virtual-machines/image-version.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Linux and Windows guidance, but there are subtle signs of Windows bias. In the PowerShell section, Windows is used as the default example, with Linux mentioned as an alternative. In the CLI section, Linux is the default, but Windows is referenced. The PowerShell examples are prominent and detailed, which may favor Windows users. However, the documentation overall covers both platforms and gives parity in CLI and REST examples.
Recommendations
- In PowerShell examples, provide a Linux example as the primary or in parallel with the Windows example.
- Ensure that both Linux and Windows are equally represented in example blocks, alternating which is shown first.
- Add explicit notes or links for Linux users in PowerShell sections, clarifying usage or alternatives.
- Consider including Bash or shell script examples for Linux users, especially for tasks commonly performed outside Azure CLI.
Virtual Machines
Customer intent: As a cloud administrator, I want to benchmark disk performance using custom I/O workloads, so that I can optimize storage configurations for maximum read and write IOPS in my virtual machines.
...ncludes/virtual-machines-managed-disks-benchmarking.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation presents Windows benchmarking (DISKSPD) before Linux benchmarking (FIO), with detailed parameter explanations and sample commands for DISKSPD. Windows tools and patterns are mentioned first, and the Windows section is more prominent. Linux parity is achieved with FIO examples, but Windows bias is evident in ordering and tool emphasis.
Recommendations
- Present Linux (FIO) and Windows (DISKSPD) sections in parallel, or alternate their ordering to avoid Windows-first bias.
- Provide equally detailed explanations and parameter breakdowns for FIO as for DISKSPD.
- Explicitly mention cross-platform alternatives for DISKSPD (e.g., FIO for Windows, if applicable) or clarify tool selection rationale.
- Add a summary table comparing Windows and Linux tools, parameters, and expected results.
- Ensure images and sample outputs are balanced between Windows and Linux examples.
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
Powershell Heavy
Summary
The documentation is focused on Linux VMs and provides Linux-specific guidance throughout. However, there is mild evidence of Windows bias in the form of PowerShell examples and scripts being mentioned alongside Azure CLI, and PowerShell is referenced before CLI in some places. The 'Next steps' section lists both CLI and PowerShell quickstarts, but PowerShell is not strictly a Linux-native tool, and its inclusion may create friction for Linux users who prefer Bash or native Linux tools. The terminology table also references PowerShell cmdlets, which are not typically used in Linux environments, though Azure PowerShell is cross-platform.
Recommendations
- Ensure Azure CLI examples and scripts are listed before PowerShell in all sections, as CLI is more native to Linux environments.
- Clarify that PowerShell is optional and that Azure CLI is the recommended tool for Linux users.
- Consider removing or de-emphasizing PowerShell references in terminology for Linux-focused documentation.
- Provide Bash script examples where possible, or highlight native Linux tools for disk encryption management.
- Explicitly state that Azure PowerShell is cross-platform, but CLI is preferred 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
Windows Tools
Summary
The documentation is focused on expanding disks for Linux VMs and provides comprehensive Linux-specific guidance. However, in the section about 'Expand without downtime classic VM SKU support', only a PowerShell script is provided to check SKU support, with no equivalent Bash/Azure CLI example for Linux users. This is a minor bias, as the rest of the document is highly Linux-centric.
Recommendations
- Add a Bash or Azure CLI example for checking classic VM SKU support for disk expansion, so Linux users can perform the same check without needing PowerShell.
- Consider linking to cross-platform tools or scripts where possible, or clarify that the PowerShell example is only required for classic VM SKU checks and provide alternatives if available.
Virtual Machines
Create an Azure Image Builder Bicep file or ARM template JSON template
.../articles/virtual-machines/linux/image-builder-json.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Minor Windows Notes
Summary
The documentation covers both Linux and Windows VM image creation with Azure Image Builder, providing parity in most areas. However, there is a notable tendency to use PowerShell for checksum generation and example commands, and Windows-specific tools (e.g., Get-FileHash, shutdown, Sysprep) are referenced more frequently and sometimes before their Linux equivalents. Some notes and examples are Windows-centric, and PowerShell is often presented alongside Azure CLI, but not always with equal prominence for Linux/macOS users.
Recommendations
- Where PowerShell is referenced for tasks like checksum generation, always provide the equivalent Linux/macOS command (e.g., sha256sum) with equal prominence.
- Ensure that Azure CLI examples are shown first or equally with PowerShell, as CLI is cross-platform.
- When referencing Windows-specific tools or commands, clarify Linux/macOS equivalents or alternatives where applicable.
- Review the order of examples and notes to avoid Windows-first bias; alternate or group by OS where possible.
- Add explicit Linux/macOS troubleshooting guidance where only Windows troubleshooting is mentioned.
- For customizer types, clarify Linux limitations (e.g., no restart customizer) and suggest workarounds if possible.
Virtual Machines
Verify encryption status for Linux - Azure Disk Encryption
...tual-machines/linux/how-to-verify-encryption-status.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both PowerShell and Azure CLI examples for verifying disk encryption status, but consistently presents PowerShell (a Windows-centric tool) before Azure CLI (cross-platform and native to Linux/macOS). The PowerShell section is more detailed and prominent, potentially signaling a Windows-first bias. However, the CLI and OS-level Linux commands are present and sufficient for Linux users.
Recommendations
- Present Azure CLI examples before PowerShell, as CLI is cross-platform and more natural for Linux users.
- Ensure that all PowerShell examples have equivalent, clearly documented Azure CLI commands.
- Consider marking PowerShell sections as 'for Windows users' and CLI as 'for Linux/macOS users' to clarify intent.
- Expand the OS-level verification section with more Linux-native tools or troubleshooting tips if possible.
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 page is focused on Linux VM time synchronization in Azure and provides extensive Linux-specific guidance, commands, and examples. However, the introductory section discusses Windows Server 2016 time sync improvements and references Windows documentation before Linux-specific details, which may create a perception of Windows-first bias. All configuration examples, tools, and troubleshooting steps are Linux-centric, and there are no PowerShell or Windows-only tools used for Linux configuration. The only PowerShell example is for base64 encoding a cloud-init file, which is relevant for Azure users on Windows but is not critical to the Linux time sync topic.
Recommendations
- Move the Windows Server 2016 discussion and references to a background or context section, clarifying its relevance to Azure infrastructure rather than Linux VM configuration.
- Add a brief note explaining why Windows Server 2016 time sync improvements matter for Linux VMs (e.g., Azure hosts use Windows Server 2016, so host time accuracy benefits Linux guests).
- Provide a Linux shell command alternative for base64 encoding the cloud-init file, such as `base64 cloud-config.txt`, to ensure parity for Linux/macOS users.
- Ensure Linux-specific links and guidance appear before or alongside any Windows references.
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 largely cross-platform and neutral, but there are a few sections where Windows-specific tools, terminology, or links are mentioned before Linux equivalents, or Windows terminology is used without equal Linux context. For example, in the 'Images' section, the link provided is Windows-specific, and in the OS disk section, Windows partitioning is discussed in detail with only brief Linux mention. The 'Upload your VHD or VHDX' section does provide both Azure CLI (Linux) and PowerShell (Windows) links, but the Windows link is listed second. The temporary disk section gives both Linux and Windows paths, but Windows terminology (drive letters) is used more frequently.
Recommendations
- Ensure that all example links and deep-dive articles are provided for both Linux and Windows users, especially in sections like 'Images' where only a Windows-specific link is given.
- When discussing disk partitioning and OS disk details, provide equivalent Linux information (e.g., reference Linux partitioning schemes, default partitioning behavior, and relevant documentation).
- Balance terminology and examples so that Linux and Windows are equally represented, for instance, by mentioning Linux device paths alongside Windows drive letters in all relevant sections.
- Where possible, alternate the order of Linux and Windows examples or links to avoid implicit prioritization.
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 details before Linux, but otherwise provides parity in describing both platforms. No Windows-specific tools, examples, or patterns are favored, and Linux support is clearly outlined. The 'Next steps' section references CLI, Portal, and PowerShell, but does not show preference for Windows tools.
Recommendations
- Consider presenting Linux and Windows operating system support sections in parallel or alphabetical order to avoid perceived prioritization.
- Explicitly mention that CLI and Portal are cross-platform in the 'Next steps' section for clarity.
- If possible, provide links to Linux-specific guidance or troubleshooting for restore points.
Virtual Machines
Migrate Standard HDD OS disks by September 08, 2028
...n/articles/virtual-machines/disks-hdd-os-retirement.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation covers both Linux and Windows VMs and provides Azure CLI and PowerShell examples for listing affected disks. However, the PowerShell example is presented first, which is a minor 'windows_first' bias. Both Linux and Windows are explicitly supported, and Azure CLI (cross-platform) is included, so Linux users are not significantly impacted.
Recommendations
- Present Azure CLI examples before PowerShell examples, as Azure CLI is cross-platform and more accessible to Linux/macOS users.
- Explicitly mention that Azure CLI commands work on Linux/macOS and Windows.
- Consider providing Bash shell script examples for bulk operations if relevant.
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 is generally Linux-focused and provides parity between Azure CLI and Azure PowerShell examples for managing VM extensions. However, PowerShell examples are consistently presented alongside CLI examples, and in some sections (such as 'Discover VM extensions'), PowerShell is shown immediately after CLI, which may subtly reinforce Windows-centric workflows. The documentation also references ARM templates and the Azure portal, both of which are cross-platform. There are no missing Linux examples, and all CLI and script examples use Linux conventions. Overall, the bias is minor and does not impede Linux/macOS users.
Recommendations
- Consider presenting Azure CLI examples before PowerShell in all sections, as CLI is more native to Linux/macOS users.
- Explicitly note that Azure PowerShell is cross-platform, but CLI is often preferred for Linux workflows.
- Add a brief section clarifying that all examples are applicable to Linux VMs and that Azure CLI is recommended for Linux administrators.
- Where possible, highlight Bash scripting and Linux-native tools for troubleshooting and automation.
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 largely platform-neutral and focuses on Azure Disk Storage features and regional availability. However, there are minor signs of Windows bias: in some sections, Windows documentation links are presented before Linux equivalents (e.g., disk expansion), and references to Windows-specific documentation (such as PowerShell or Windows disk management) appear without always mentioning Linux alternatives. No critical tasks are Windows-only, but Linux/macOS users may experience slight friction due to Windows-first ordering and occasional omission of Linux-specific links.
Recommendations
- Ensure Linux and macOS documentation links are presented alongside Windows links, ideally with equal prominence.
- When referencing disk management or expansion, always include both Windows and Linux documentation links in the same sentence or section.
- Where Azure CLI or PowerShell is mentioned, clarify cross-platform support and provide examples for both environments.
- Review linked articles (e.g., expand-disks, find-unattached-disks) to confirm Linux parity and update main page links if needed.
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
Summary
The documentation generally covers both Linux and Windows VM scenarios, but there are instances where Windows terminology, tools, and links are presented first or exclusively. For example, partitioning guidance references Windows documentation and tools (MBR/GPT) before mentioning Linux equivalents. In the 'Upload your VHD or VHDX' section, both Azure CLI (Linux) and PowerShell (Windows) links are provided, but Windows terminology and links are often listed first. The OS disk section references Windows drive letters and partitioning, with Linux details appearing later or less prominently.
Recommendations
- Ensure Linux partitioning guidance (MBR/GPT) is equally referenced, with links to relevant Linux documentation (e.g., fdisk, parted, Linux GPT/MBR guides).
- When discussing disk roles, mention Linux device paths (e.g., /dev/sda, /dev/disk/azure/resource) alongside Windows drive letters, and do so in parallel.
- Alternate the order of example links (Azure CLI and PowerShell) or present them together to avoid Windows-first bias.
- Add explicit Linux examples or links where only Windows documentation is referenced (e.g., partitioning, disk conversion).
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 balanced and explicitly applies to both Linux and Windows VMs. However, in several sections, Windows-specific tools and mechanisms (such as Volume Shadow Service and SQL Server Always On Availability Groups) are mentioned first or exclusively, with Linux equivalents (like fsfreeze) referenced later and with less detail. Some backup consistency methods are described in greater depth for Windows, while Linux approaches are briefly noted. SQL Server backup options are discussed in detail, but comparable Linux database backup guidance is not provided.
Recommendations
- Provide equal detail for Linux backup consistency tools (e.g., elaborate on fsfreeze usage and limitations, and mention other Linux tools for application-consistent backups).
- When mentioning Windows-specific mechanisms (like VSS), immediately follow with Linux alternatives and examples, ensuring parity in explanation and guidance.
- Include examples or references for backing up popular Linux databases (e.g., MySQL, PostgreSQL) in Azure VMs, similar to the SQL Server guidance.
- Ensure that comparison tables and solution descriptions explicitly state Linux support and any limitations, not just Windows features.
- Where possible, provide links to Linux-focused backup and disaster recovery documentation.
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 in the development/test environment section, where B-Series recommendations specify 'Use at least B2 for Windows machines' without an equivalent Linux guidance, and Windows is mentioned first in pricing links. There are no PowerShell-heavy examples or Windows-only tools, and Linux is referenced in VM creation and pricing links.
Recommendations
- Add equivalent Linux guidance for B-Series VM sizing if applicable (e.g., 'Use at least B2 for Linux machines' or clarify if sizing differs).
- Ensure Linux examples or recommendations are provided alongside Windows-specific advice in all relevant sections.
- When linking to pricing pages or VM sizes, mention Linux and Windows equally (e.g., 'Review pricing for both Windows and Linux VMs').
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 mentioned before Linux/CLI equivalents, and PowerShell is referenced as a primary tool for certain operations (e.g., revoking access, enabling features). This ordering and emphasis may create a perception of Windows/PowerShell as the default or preferred platform/tool, even though Linux/CLI parity is present.
Recommendations
- Alternate the order of Windows/PowerShell and Linux/CLI examples and links, or present them side-by-side to reinforce equal support.
- Explicitly state that all features and procedures are equally available for Linux and Windows VMs at the start of relevant sections.
- Where PowerShell is referenced for tasks (e.g., revoking access), ensure CLI and/or Bash equivalents are also mentioned with equal prominence.
- Consider adding sample code snippets for both PowerShell and CLI in the main body, not just in linked articles.
- Review the 'Next steps' and in-text links to ensure Linux/CLI resources are not consistently listed after Windows/PowerShell.
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
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page shows a mild Windows/PowerShell bias. In the 'Custom role' section, the link for creating a custom RBAC role points to a PowerShell-specific guide, with no mention of CLI or ARM template alternatives. In the 'Configure the Network access policy' section, both Azure CLI and PowerShell are mentioned, but PowerShell is listed second. However, there are no explicit Linux/bash examples or links for custom role creation, and PowerShell is referenced multiple times without Linux-first parity.
Recommendations
- Add links or references to creating custom RBAC roles using Azure CLI and ARM templates, not just PowerShell.
- Ensure that for every PowerShell example or link, an equivalent Azure CLI (bash/Linux) example or link is provided.
- Consider listing CLI (cross-platform) options before PowerShell to avoid a Windows-first impression.
- Where possible, provide code snippets or links for both Linux and Windows users.
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 (which is more cross-platform). References to role assignment and policy assignment include portal, PowerShell, and CLI, but PowerShell is frequently mentioned first. The 'Next steps' section does provide both Linux and Windows-specific links for VHD upload/download, but overall, there is a slight tendency to foreground Windows/PowerShell tools.
Recommendations
- Present Azure CLI examples before PowerShell, as CLI is cross-platform and more accessible to Linux/macOS users.
- Where possible, clarify that Azure CLI commands work on all platforms, and explicitly mention Linux/macOS compatibility.
- Ensure parity in example scripts and screenshots for Linux/macOS users, especially in sections where PowerShell is highlighted.
- Consider adding a short note about platform compatibility for each tool (e.g., 'Azure CLI works on Windows, Linux, and macOS').
Virtual Machines
Enable shared disks for Azure Managed Disks
.../main/articles/virtual-machines/disks-shared-enable.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides both Azure CLI and PowerShell examples for all disk types, but PowerShell (a Windows-centric tool) is consistently given equal prominence and sometimes appears first in sections. There are no Linux-specific shell examples (e.g., Bash), and no Linux-specific guidance for disk attachment or SCSI PR usage. However, Azure CLI is cross-platform and all critical operations are covered via CLI, so Linux/macOS users can complete all tasks.
Recommendations
- Explicitly note that Azure CLI commands work on Linux/macOS and provide Bash shell invocation examples where relevant.
- Consider showing Azure CLI examples before PowerShell, or clarifying that PowerShell is primarily for Windows users.
- Add a brief section or link describing how to mount and use shared disks on Linux VMs after attachment (e.g., using 'lsblk', 'mount', etc.), especially for clustered applications.
- If SCSI PR commands require OS-level configuration, provide Linux-specific instructions or references.
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation covers both Linux and Windows VMs for ephemeral OS disks, with clear applicability to both. However, there are minor signs of Windows bias: Windows Server image sizing is discussed first in the 'Size requirements' section, and PowerShell is mentioned before CLI in the 'Customer Managed key' section. Linux examples and tools are present but sometimes secondary.
Recommendations
- Present Linux and Windows examples/tools in parallel or alternate order to avoid implicit prioritization.
- In the 'Size requirements' section, mention Linux image sizing before or alongside Windows image sizing.
- In the 'Customer Managed key' section, list CLI and PowerShell together or alternate their order.
- Ensure that any linked deployment guides or scripts provide both Linux and Windows instructions equally.
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 focused on Linux VM GPU driver installation, but includes PowerShell examples for deploying the extension, even though PowerShell is primarily a Windows-centric tool. The PowerShell example is presented before the Azure CLI example, which is more commonly used on Linux/macOS. However, the overall content and examples are Linux-focused, and Linux CLI and ARM template examples are provided throughout. No Windows tools or patterns are mentioned exclusively, and Linux-specific troubleshooting and manual steps are included.
Recommendations
- Move the Azure CLI example before the PowerShell example in the deployment section to prioritize Linux-native tooling.
- Clarify that PowerShell can be used cross-platform, but Azure CLI is recommended for Linux/macOS users.
- Consider adding Bash script examples for extension deployment, as Bash is the default shell on most Linux systems.
- Explicitly state that PowerShell examples are optional for Linux users and provide links to Azure CLI installation instructions if needed.