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 576-600 of 815 flagged pages
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides both Azure CLI and PowerShell examples for checking vCPU quotas. However, the PowerShell example is given equal prominence to the CLI example, despite PowerShell being primarily a Windows tool. The CLI example is cross-platform, but there is no explicit mention that PowerShell is Windows-centric or that the CLI is preferred for Linux/macOS users. The ordering of examples is neutral, but the inclusion of PowerShell without clarifying its platform limitations may cause confusion for Linux/macOS users.
Recommendations
- Explicitly state that Azure CLI is cross-platform and recommended for Linux/macOS users, while PowerShell is primarily for Windows.
- Consider placing the Azure CLI example first, or labeling it as the default for Linux/macOS.
- Add a note clarifying PowerShell's platform support and limitations.
- Ensure that all critical tasks can be completed using Azure CLI, and highlight CLI as the preferred method for non-Windows environments.
Create Pull Request
Virtual Machines
Share VM images in a compute gallery
...in/articles/virtual-machines/shared-image-galleries.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Minor Windows Tools
Summary
The documentation covers both Windows and Linux VM images, but there are several instances where Windows/PowerShell examples, links, and terminology are presented before or more prominently than their Linux/CLI equivalents. PowerShell examples are given equal prominence to Azure CLI, but Windows terminology and links (e.g., Sysprep, Windows upload VHD, specialized image creation) are sometimes referenced first. However, Linux-specific information (waagent, Linux upload VHD) is included and the overall guidance is cross-platform.
Recommendations
- Ensure that Linux/CLI examples and links are presented alongside or before Windows/PowerShell equivalents, especially in sections where both are relevant.
- Where possible, use neutral language (e.g., 'Azure CLI' instead of 'PowerShell') as the primary example, or provide both examples in parallel.
- Review links and references to ensure Linux documentation is as discoverable as Windows documentation (e.g., specialized image creation links for Linux).
- Explicitly state parity in supported features and tools for both Windows and Linux, especially in FAQ and troubleshooting sections.
Virtual Machines
Share VM images in a compute gallery
...in/articles/virtual-machines/shared-image-galleries.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation provides both Windows and Linux coverage, but there are signs of Windows bias. PowerShell examples are frequently given alongside Azure CLI, sometimes with more detail. Windows-specific tools (e.g., Sysprep) are mentioned before Linux equivalents (waagent). Windows upload instructions are listed before Linux. References to Windows-specific pages and terminology (e.g., 'Computer name', 'WinRM') are more prominent. Some links and examples default to Windows paths or PowerShell tabs first.
Recommendations
- Ensure Linux and CLI examples are given equal prominence and detail as PowerShell/Windows examples.
- When mentioning tools for generalizing images, list Linux (waagent) and Windows (Sysprep) together, or alternate order.
- Where possible, provide Linux-specific troubleshooting and links alongside Windows ones.
- In FAQ and instructional sections, alternate the order of Windows and Linux instructions or present them in parallel.
- Review linked pages to ensure Linux parity in referenced content.
Virtual Machines
Instantly access managed disk snapshots
...les/virtual-machines/disks-instant-access-snapshots.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI (cross-platform) and Azure PowerShell (Windows-centric) examples for creating instant access snapshots. However, the PowerShell example is given equal prominence and appears before the portal instructions, which may subtly prioritize Windows tooling. There are no Linux-specific shell examples (e.g., Bash), but Azure CLI is inherently cross-platform. No Windows-only tools or patterns are mentioned, and the documentation does not exclusively reference Windows tools. The ordering of examples (CLI, PowerShell, Portal, ARM template) is slightly Windows-first, but not critically so.
Recommendations
- Ensure Azure CLI examples are clearly marked as cross-platform and, if possible, provide explicit Bash shell examples for Linux/macOS users.
- Consider listing Azure CLI examples before PowerShell to reinforce cross-platform parity.
- Add a note clarifying that Azure PowerShell is primarily for Windows users, while Azure CLI works on Linux/macOS/Windows.
- If relevant, provide troubleshooting or tips for Linux/macOS environments (e.g., installing Azure CLI).
Virtual Machines
Secure Azure Managed Disk Downloads and Uploads
...icles/virtual-machines/disks-secure-upload-download.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both PowerShell and Azure CLI examples for securing managed disk uploads/downloads, but PowerShell (a Windows-centric tool) is presented before Azure CLI in several sections. References to role assignment and policy assignment include both PowerShell and CLI, but PowerShell is consistently listed first. The 'Next steps' section offers parity between Linux and Windows, linking to both OS-specific guides. No critical Linux gaps are present, but the ordering and emphasis slightly favor Windows/PowerShell users.
Recommendations
- Alternate the order of PowerShell and Azure CLI examples so Linux users see CLI options first in some sections.
- Explicitly note that Azure CLI works cross-platform and is recommended for Linux/macOS users.
- Where possible, provide Bash shell script examples alongside PowerShell, especially for disk operations.
- Consider grouping examples by platform (Windows, Linux/macOS) or labeling tabs more clearly to help users find relevant instructions.
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 links and examples for both Azure PowerShell and Azure CLI, but the custom RBAC role section links only to a PowerShell-based guide, and PowerShell is mentioned before CLI in the Network access policy section. This creates a slight Windows bias, as Linux users may prefer CLI or other methods.
Recommendations
- Add a link to a custom RBAC role creation guide using Azure CLI, not just PowerShell.
- Ensure CLI examples and links are presented alongside or before PowerShell equivalents.
- Where possible, provide explicit Linux/macOS instructions or clarify cross-platform compatibility.
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 focused on Linux VM extensions, but consistently presents both Azure CLI and Azure PowerShell examples for nearly every task. PowerShell examples are always present, even though PowerShell is primarily a Windows-centric tool (though available on Linux). In several sections, PowerShell examples are shown immediately after CLI, and the introductory text mentions PowerShell alongside CLI, ARM templates, and portal. However, all actual extension usage and scripting examples are Linux-focused, and there are no Windows-only tools or commands. The documentation does not omit Linux examples, but the presence and prominence of PowerShell may create friction for Linux users who do not use PowerShell.
Recommendations
- Consider clarifying that Azure PowerShell is cross-platform, but that Azure CLI is the primary tool for Linux users.
- Present Azure CLI examples first in all sections, and consider making PowerShell examples secondary or optional (e.g., in expandable tabs).
- Explicitly mention Bash or shell scripting as the default for Linux, and highlight Linux-native tools where relevant.
- Where possible, provide Bash script examples for common extension management tasks (e.g., using az CLI in shell scripts).
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 Azure Linux VMs and the NVIDIA GPU Driver Extension for Linux, with nearly all examples, instructions, and troubleshooting steps tailored for Linux environments. 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. There is a brief reference to a Windows extension, but it is clearly separated and not the focus. No Linux examples are missing, and Linux tools and patterns are well represented.
Recommendations
- Consider moving Azure CLI examples before PowerShell examples, as CLI is more cross-platform and native to Linux.
- Clarify that PowerShell examples are for users on Windows or using Azure PowerShell on Linux/macOS, to avoid confusion.
- Optionally, provide Bash script examples for common tasks (e.g., checking extension status) to further enhance Linux parity.
- Ensure that troubleshooting and deployment sections consistently prioritize Linux-native tools and commands.
Virtual Machines
Azure Key Vault VM Extension for Linux
...rticles/virtual-machines/extensions/key-vault-linux.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation is focused on the Azure Key Vault VM Extension for Linux and provides comprehensive Linux-specific guidance. However, in deployment and troubleshooting sections, PowerShell examples are presented first and in greater detail, with Azure CLI examples following. Troubleshooting instructions reference Azure PowerShell before Azure CLI. There are no missing Linux examples or exclusive Windows tools, but the ordering and emphasis on PowerShell may create friction for Linux users who typically use Azure CLI or shell scripting.
Recommendations
- Present Azure CLI examples before PowerShell in deployment and troubleshooting sections, as CLI is more commonly used on Linux.
- Expand CLI troubleshooting instructions to match the detail provided for PowerShell.
- Add a brief note clarifying that PowerShell is optional and Azure CLI is fully supported for Linux users.
- Consider adding Bash or shell script snippets for common Linux automation scenarios.
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 instructions reference using PowerShell sessions even when working with the Azure CLI. There are minor instances of Windows-first ordering and PowerShell-heavy explanations, but Linux parity is generally maintained through CLI examples and explicit Linux context.
Recommendations
- Ensure Azure CLI examples are always presented before or alongside PowerShell examples, especially since CLI is cross-platform and preferred for Linux users.
- Remove references to using Azure CLI 'in any PowerShell session'—clarify that CLI can be used in Bash or other Linux-native shells.
- Where possible, add Bash shell scripting examples for Azure CLI usage to further reinforce Linux-native workflows.
- Consider adding explicit notes about CLI and PowerShell parity, and clarify which tool is recommended for Linux users.
Virtual Machines
Deprovision or generalize a VM before creating an image
...docs/blob/main/articles/virtual-machines/generalize.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides clear, separate instructions for both Linux and Windows VM generalization. However, in the Windows section, PowerShell and Command Prompt examples are used, and the Windows steps are presented after the Linux steps. There is no evidence of missing Linux examples or Windows tools being mentioned exclusively. Both OSes are covered with parity, but Windows-specific tooling (PowerShell) is used for Windows steps, which is appropriate. The Linux section uses waagent and Azure CLI, which are cross-platform. The order of sections (Linux first) avoids 'windows_first' bias.
Recommendations
- Ensure that Azure CLI commands for marking a VM as generalized are shown for Windows VMs, not just PowerShell.
- Consider adding a note that Azure CLI can be used on Windows as well, for cross-platform parity.
- Where possible, provide both Azure CLI and PowerShell examples for Windows VM generalization.
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 parity for both Linux and Windows users in most sections, including CLI, REST, and portal instructions. However, there is a mild Windows bias in the PowerShell examples, which default to Windows OS in their sample code, and in the ordering of OS-specific guidance, where Windows is often mentioned after Linux but PowerShell examples are more Windows-centric. Additionally, PowerShell is presented as a primary scripting option, which is more common for Windows users.
Recommendations
- In PowerShell examples, provide Linux-focused sample code (e.g., use -OsType Linux in the main example, not just as a note).
- Ensure that both Linux and Windows are equally represented in sample code and explanations, especially in scripting sections.
- Consider adding Bash or shell scripting examples for Linux users, or clarify that CLI is cross-platform.
- Explicitly state that PowerShell can be used on Linux/macOS, and provide guidance for those environments if relevant.
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 enabling Azure Disk Encryption for Linux VMs and is generally Linux-centric. However, in several places, Azure PowerShell is mentioned alongside Azure CLI as a tool for managing Linux VM disk encryption, and PowerShell examples/scripts are referenced equally with CLI ones. In the 'Next steps' and introductory sections, PowerShell is listed immediately after CLI, rather than after Bash or Linux-native tools, which may create a minor perception of Windows bias. There are no Windows-only tools, patterns, or examples given, and all technical instructions and examples are Linux-specific.
Recommendations
- Consider listing Azure CLI examples and scripts before PowerShell in all sections, as CLI is more commonly used on Linux.
- Clarify that PowerShell can be used cross-platform, but Azure CLI is the primary Linux-native tool.
- Add explicit mention that both Azure CLI and PowerShell are available on Linux, and provide guidance for users who may prefer Bash scripting or native Linux tools.
- If possible, provide Bash script examples or highlight CLI usage in Bash shells to reinforce Linux parity.
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
Powershell Heavy
Windows First
Summary
The documentation provides both Azure PowerShell and Azure CLI examples for verifying disk encryption status on Linux VMs. However, PowerShell examples are presented before Azure CLI, and the PowerShell section is more detailed and prominent, despite Linux users typically preferring Azure CLI or Bash. There are no missing Linux examples, and the OS-level section uses Linux-native commands (lsblk, cryptsetup).
Recommendations
- Present Azure CLI examples before PowerShell, as CLI is more relevant for Linux users.
- Ensure Azure CLI and Bash examples are as detailed and comprehensive as PowerShell examples.
- Consider reducing PowerShell prominence or clarifying its use for cross-platform scenarios.
- Add a brief note explaining PowerShell's cross-platform support, but emphasize CLI/Bash for Linux.
- Review and balance the depth of CLI and PowerShell sections to avoid perceived bias.
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
Windows Tools
Summary
The documentation provides comprehensive instructions for preparing and uploading a Red Hat Enterprise Linux VHD for Azure, covering multiple hypervisors (Hyper-V, KVM, VMware, Kickstart). However, there is a notable Windows bias: Hyper-V (a Windows-only tool) is consistently presented first in each major section, and Windows-centric terminology (e.g., 'Hyper-V Manager', 'Connect', 'Action > Shut Down') is used throughout. The instructions for KVM, VMware, and Kickstart are present and detailed, but Windows/Hyper-V steps are prioritized and referenced as the default workflow. Additionally, some conversion steps reference Windows tools (e.g., 'convert-vhd' cmdlet) before Linux alternatives.
Recommendations
- Reorder sections so that Linux-native hypervisors (KVM, VMware, Kickstart) are presented before or alongside Hyper-V, rather than always after.
- Where possible, use neutral terminology for actions (e.g., 'Shut down the VM' instead of 'Action > Shut Down in Hyper-V Manager').
- When mentioning disk conversion tools, provide Linux-native options (e.g., qemu-img) before or alongside Windows tools (e.g., Hyper-V Manager, convert-vhd).
- Add a summary table or flowchart at the top to help users quickly identify the relevant workflow for their platform.
- Ensure that all references to Windows tools are matched with equivalent Linux/macOS alternatives, and avoid implying that Windows/Hyper-V is the default or preferred method.
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
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation provides both Windows and Linux coverage for Azure Image Builder, but there are several areas where Windows-specific examples, tools, and terminology are presented first or more prominently. PowerShell is often referenced for checksum generation and resource actions, sometimes before or instead of Linux equivalents. Windows customizers (PowerShell, WindowsRestart, WindowsUpdate) are described in detail, while Linux customizers (Shell) are covered but with less depth. Windows-specific tools (Get-FileHash, PowerShell commands) are mentioned more frequently than Linux alternatives (sha256sum).
Recommendations
- Ensure Linux/macOS commands (e.g., sha256sum, Azure CLI) are presented alongside or before Windows/PowerShell equivalents, especially in sections about checksum generation and resource actions.
- Balance the order and depth of customizer descriptions: provide equal detail for Shell customizer as for PowerShell/Windows customizers.
- Where PowerShell is referenced for operations (e.g., invoking actions, generating checksums), always include the Linux/macOS CLI equivalent and make it equally prominent.
- Add explicit notes or examples for Linux-specific scenarios where only Windows examples are given (e.g., restart customizer, validator examples).
- Review the order of examples and ensure Linux and Windows are treated equally in introductory and summary sections.
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 sync in Azure and provides comprehensive Linux-specific guidance, including tools, commands, and configuration examples for chrony, ntpd, systemd-timesyncd, and cloud-init. However, the 'Overview' section and opening paragraphs spend several sentences discussing Windows Server 2016 time sync improvements and Windows host infrastructure before describing Linux-specific mechanisms. Windows references are presented first and in detail, even though the page is Linux-focused. All technical examples and instructions are Linux-centric, and there are no PowerShell or Windows tool examples except for a single PowerShell command for base64 encoding cloud-init, which is contextually relevant for Azure ARM templates.
Recommendations
- Move the Windows Server 2016 time sync discussion to a background or context section, or summarize it briefly before focusing on Linux-specific details.
- Begin the page with Linux time sync mechanisms and Azure-specific integration, referencing Windows infrastructure only as necessary for context.
- Clarify that Windows host improvements are relevant only insofar as they affect Linux VM time sync via VMICTimeSync.
- Consider providing the base64 encoding example for cloud-init in Linux (e.g., using 'base64 cloud-config.txt') alongside the PowerShell example for parity.
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and PowerShell examples for checking vCPU quotas. However, the PowerShell example is given equal prominence and detail, despite PowerShell being primarily a Windows tool. The CLI example is shown first, which is positive, but the presence of PowerShell may create friction for Linux/macOS users, as PowerShell is less commonly used on those platforms.
Recommendations
- Clarify that PowerShell is primarily for Windows users, and recommend Azure CLI for Linux/macOS.
- Consider adding Bash or shell script examples for Linux users, if applicable.
- Explicitly note cross-platform compatibility of Azure CLI.
- If PowerShell is supported on Linux/macOS, mention installation instructions or link to relevant docs.
Virtual Machines
Customer intent: "As an IT administrator managing Azure IaaS virtual machines, I want to implement a backup and disaster recovery plan for unmanaged disks, so that I can ensure data durability and high availability in the event of localized or regional failures."
...al-machines/page-blobs-backup-and-disaster-recovery.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Minor Windows Tools
Summary
The documentation covers backup and disaster recovery for Azure unmanaged disks on both Linux and Windows VMs. While most guidance is platform-neutral, there are several instances where Windows tools (PowerShell, Volume Shadow Service) are mentioned first or exclusively, and PowerShell is referenced more often than Linux equivalents. Linux-specific tools (fsfreeze, Azure CLI) are mentioned, but often after Windows tools or in less detail. Some links and examples (e.g., incremental snapshots) point to Windows pages first, though Linux equivalents are referenced in the 'Next steps' section.
Recommendations
- Ensure Linux and Azure CLI examples are presented alongside or before PowerShell examples, especially in automation and recovery sections.
- Where Windows tools (e.g., Volume Shadow Service) are discussed, provide equal detail for Linux alternatives (e.g., fsfreeze, application-consistent backup guidance).
- In tables and lists, avoid defaulting to Windows-centric terminology or links; ensure Linux documentation is equally prominent.
- Add explicit Linux CLI commands and scripts for snapshot, backup, and restore operations.
- Review cross-references to ensure Linux incremental snapshot documentation is linked as prominently as Windows versions.
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 mostly platform-neutral and focuses on Azure Disk Storage features and regional availability. However, there are minor instances where Windows documentation or tools are referenced first or exclusively, such as linking to Windows-specific expand disk documentation before Linux equivalents, and referencing Azure PowerShell before Azure CLI in one property update. No critical tasks are Windows-only, and Linux parity is generally maintained.
Recommendations
- Ensure that links to both Windows and Linux documentation are presented together or in a neutral order, rather than Windows first.
- When referencing Azure CLI and PowerShell, list both tools equally and avoid prioritizing Windows tools.
- Where possible, provide examples or links for Linux/macOS alongside Windows, especially for disk management operations.
- Review linked articles to ensure Linux/macOS instructions are as comprehensive as Windows instructions.
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 parity for both Linux and Windows users, with CLI and REST examples defaulting to Linux, and PowerShell examples defaulting to Windows. However, PowerShell examples are shown for Windows first, and the PowerShell section is more detailed for Windows scenarios. The CLI section defaults to Linux, but the PowerShell section defaults to Windows, which may create minor friction for Linux users who prefer PowerShell. No critical tasks are Windows-only, and Linux guidance is present throughout.
Recommendations
- In PowerShell examples, show Linux usage first or provide a Linux-specific example alongside the Windows example.
- Clarify in PowerShell sections that -OsType can be set to Linux, and provide a sample command for Linux.
- Ensure that all example blocks (CLI, PowerShell, REST) consistently show both Linux and Windows usage, or alternate which OS is shown first.
- Add a brief note in the PowerShell section that Linux images can be managed equivalently, with a sample command.
Virtual Machines
Secure Azure Managed Disk Downloads and Uploads
...icles/virtual-machines/disks-secure-upload-download.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both PowerShell and Azure CLI examples for securing managed disk uploads/downloads, but PowerShell (a Windows-centric tool) is presented before Azure CLI in several sections. The 'Assign RBAC role' and 'Restrict access to an individual disk' sections list PowerShell before CLI, and the tab order is PowerShell first. However, Linux/macOS users are not blocked, as CLI examples are present and relevant links for Linux tasks are included in 'Next steps'.
Recommendations
- Alternate the order of PowerShell and Azure CLI examples, or present Azure CLI first to avoid implicit Windows prioritization.
- Explicitly note that Azure CLI works cross-platform and is recommended for Linux/macOS users.
- Add Bash or shell script examples where relevant, especially for disk operations.
- Ensure parity in screenshots and UI descriptions for portal steps (if differences exist).
Virtual Machines
Azure VM Extensions and Features for Linux
...articles/virtual-machines/extensions/features-linux.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for all major tasks (discovering, running, managing, and troubleshooting VM extensions). However, PowerShell examples are always given alongside CLI, and in some sections, PowerShell is presented immediately after CLI, which may suggest parity but still reinforces PowerShell as a primary tool. There are no Linux-specific shell or scripting examples outside Azure CLI, and no Linux-native tooling is discussed. The documentation does not omit Linux examples, but the presence and prominence of PowerShell throughout may create friction for Linux users who do not use PowerShell.
Recommendations
- Consider providing Bash shell script examples for common extension management tasks, especially for users who prefer native Linux tools.
- Clarify that PowerShell is optional for Linux users and highlight Azure CLI as the primary cross-platform tool.
- Where possible, reorder examples to show Azure CLI first, and PowerShell second, or explicitly state that Azure CLI is recommended for Linux.
- Add a brief section explaining the typical Linux admin workflow (using Bash, SSH, etc.) and how Azure CLI fits into that.
- Remove unnecessary references to PowerShell in Linux-focused documentation unless it is required for a specific scenario.
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, even though PowerShell is a Windows-centric tool. Additionally, PowerShell is presented before Azure CLI in several sections, which may subtly prioritize Windows tooling. There are no missing Linux examples, and Linux tools and patterns are well represented throughout the document.
Recommendations
- Move Azure CLI examples before PowerShell examples, as Azure CLI is cross-platform and more relevant for Linux users.
- Clarify that PowerShell examples are optional and primarily for users on Windows or those using PowerShell Core on Linux.
- Consider adding Bash script examples for common deployment scenarios, as Bash is native to Linux.
- Explicitly note that Azure CLI is recommended for Linux users.
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 generally Linux-focused and provides extensive Linux-specific details, but there are minor signs of Windows bias. Azure PowerShell examples are presented before Azure CLI examples in deployment sections, and troubleshooting commands reference PowerShell first. There is also a link to a Windows VM access policy guide in the template deployment section, though the context is relevant for managed identities. All technical content, examples, and paths are Linux-centric, and Linux tools (Azure CLI, Fluentd, symlinks, Linux file paths) are well covered.
Recommendations
- Present Azure CLI examples before PowerShell examples, as CLI is more cross-platform and native to Linux.
- In troubleshooting sections, show Azure CLI commands first or alongside PowerShell.
- Clarify that PowerShell examples are optional for Linux users, and highlight CLI as the primary method.
- Where links reference Windows VM guides, add a Linux-specific link or clarify applicability.