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 601-625 of 815 flagged pages
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 multiple hypervisors (Hyper-V, KVM, VMware, Kickstart) for preparing and uploading a Red Hat Enterprise Linux VHD for Azure. However, throughout the article, instructions for Hyper-V (a Windows-based hypervisor) are consistently presented first in each major section and tab group. This ordering may subtly suggest Windows/Hyper-V as the primary or preferred platform, even though full Linux-native (KVM, VMware, Kickstart) instructions are provided. There are no missing Linux examples, and Linux tools and patterns are well represented.
Recommendations
- Consider reordering sections so that Linux-native hypervisors (KVM, VMware, Kickstart) are presented before Hyper-V, or at least alternate the order to avoid implicit prioritization.
- Explicitly state in the introduction that all major hypervisors are equally supported, and that the order of presentation does not imply preference.
- Where possible, highlight that Linux-native workflows (KVM, VMware, Kickstart) are fully supported and may be preferable for Linux users.
- Add a summary table at the top showing parity across hypervisors, so users can quickly identify their preferred workflow.
Create Pull Request
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
Summary
The documentation provides both Windows and Linux guidance for Azure Image Builder, but there are several areas where Windows tools and patterns are emphasized or presented first. PowerShell is frequently referenced for checksum generation and template operations, sometimes before Linux equivalents. Windows-specific customizers (PowerShell, WindowsRestart, WindowsUpdate) are described in detail, while Linux customizers are less prominent. Some examples and notes use Windows terminology or tools (e.g., Get-FileHash, shutdown commands) before mentioning Linux alternatives.
Recommendations
- Ensure Linux and macOS command-line examples (e.g., for checksum generation) are presented alongside or before Windows/PowerShell equivalents.
- Where PowerShell is referenced, also provide bash or shell alternatives for Linux/macOS users, especially for operations like file hash generation and template actions.
- Balance the order of examples so that Linux and Windows are equally represented, or alternate which OS is shown first.
- Clarify when a feature or customizer is Windows-only, and provide Linux equivalents or explicitly state when no equivalent exists.
- Expand Linux-specific customizer and validator examples to match the detail given for Windows (e.g., more shell script examples, troubleshooting tips).
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 Linux-specific guidance, examples, and tools. However, the 'Overview' section and introduction spend several paragraphs describing Windows Server 2016 time sync improvements and Windows host infrastructure before discussing Linux-specific mechanisms. Windows references and links appear before Linux configuration details, which may create confusion or friction for Linux users seeking direct guidance.
Recommendations
- Move Windows Server 2016 background information to a separate 'Background' or 'Azure host infrastructure' section, or summarize briefly before focusing on Linux-specific mechanisms.
- Begin the page with Linux VM time sync options and configuration steps, referencing Windows host infrastructure only as needed for context.
- Ensure Linux-specific examples and tools are presented first and clearly, minimizing Windows-centric framing unless directly relevant.
- Consider adding a short summary at the top clarifying that the Windows host information is background and that the page is Linux-focused.
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 section is given equal prominence to the CLI, despite PowerShell being primarily a Windows tool. Additionally, the PowerShell example is presented immediately after the CLI example, which may subtly reinforce Windows-centric workflows. No Linux-specific tools or shell examples (e.g., Bash scripting) are provided, but the CLI example is cross-platform.
Recommendations
- Clearly indicate that Azure CLI is cross-platform and preferred for Linux/macOS users.
- Consider adding a brief Bash shell example (e.g., piping Azure CLI output to grep or awk) to demonstrate Linux-native workflows.
- Explicitly mention that PowerShell is primarily for Windows users, and that Azure CLI works on all platforms.
- If possible, provide links to Azure CLI installation instructions for Linux/macOS users.
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 both Linux and Windows VMs and generally maintains parity in describing backup and disaster recovery approaches. However, there are several instances where Windows-specific tools (such as PowerShell and Volume Shadow Service) are mentioned first or in more detail, and PowerShell is often referenced as the primary scripting/automation method. Linux equivalents (such as Azure CLI or fsfreeze) are mentioned, but sometimes after Windows tools or with less detail. There are also references to Windows-specific backup consistency mechanisms (VSS) before Linux alternatives, and links to Windows-focused pages (e.g., incremental snapshots under 'windows'). However, Linux options are present and described, and critical tasks can be completed on Linux.
Recommendations
- Ensure that scripting/automation examples are provided for both PowerShell and Azure CLI, with equal prominence.
- When mentioning backup consistency mechanisms, describe Linux options (such as fsfreeze and application-consistent backup for Linux VMs) before or alongside Windows VSS.
- Provide links to both Linux and Windows incremental snapshot guides in relevant sections, not just Windows.
- Where PowerShell is referenced, add Azure CLI equivalents and note their parity.
- Review and balance the order of tool mentions so Linux tools are not consistently secondary.
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 signs of Windows bias. PowerShell examples are consistently provided alongside Azure CLI, sometimes referenced first. Windows-specific tools (Sysprep) are mentioned before Linux equivalents (waagent) in the generalization section. Some links and examples reference Windows paths or documentation before Linux equivalents. However, Linux parity is generally maintained, and most tasks can be completed by Linux users.
Recommendations
- Ensure that CLI and PowerShell examples are presented with equal prominence, or alternate which comes first.
- Where both Windows and Linux tools are mentioned, list Linux tools first or together, rather than defaulting to Windows-first ordering.
- Add explicit Linux examples or links wherever Windows examples are given, especially in sections referencing upload or specialized image creation.
- Review FAQ and troubleshooting sections for balanced coverage of Linux and Windows scenarios.
- Where possible, use generic language (e.g., 'generalize your VM') and then specify both Windows and Linux methods equally.
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 PowerShell and Azure CLI links for configuring the NetworkAccessPolicy, but the PowerShell link is listed first and the custom RBAC role creation is linked only to a PowerShell-based guide. There are no explicit Linux/macOS examples or references, and the CLI link for private links is specifically labeled 'linux', but the main guidance and examples tend to favor Windows/PowerShell tools.
Recommendations
- Provide links to both Azure CLI and PowerShell guides for custom RBAC role creation, not just PowerShell.
- List Azure CLI and PowerShell options together or alternate their order to avoid Windows-first bias.
- Clarify that Azure CLI is cross-platform and provide explicit Linux/macOS usage examples where relevant.
- Ensure that all referenced guides (such as for private links) have parity between Windows and Linux instructions.
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 PowerShell and Azure CLI examples for securing managed disk uploads/downloads, but PowerShell examples are presented before CLI examples in several sections. Portal instructions are also included. While CLI is cross-platform, PowerShell is more commonly associated with Windows, and its precedence in examples may create a subtle Windows bias. However, Linux-specific guidance is present in the 'Next steps' section, and CLI instructions are available throughout.
Recommendations
- Present Azure CLI examples before PowerShell examples, as CLI is cross-platform and more accessible to Linux/macOS users.
- Explicitly note that Azure CLI works on Linux/macOS, and provide links to installation instructions for those platforms.
- Where possible, add Bash shell script examples alongside PowerShell, especially for disk operations.
- Ensure that any screenshots or UI references are not Windows-specific unless necessary.
- Review included files (prereqs, restrictions) to confirm Linux parity in prerequisites and restrictions.
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 all tasks. PowerShell is a Windows-centric tool, and its inclusion alongside CLI in every section may create friction for Linux users. Additionally, in several sections, PowerShell examples are given immediately after CLI, sometimes with more detailed output, which may subtly reinforce Windows tooling. However, all examples and explanations are applicable to Linux VMs, and Linux-specific tools (bash, waagent) are referenced where relevant.
Recommendations
- Consider prioritizing Azure CLI examples, as CLI is cross-platform and native to Linux/macOS.
- Move PowerShell examples to a secondary position or into expandable sections, so Linux users see CLI first.
- Clarify that PowerShell is optional and primarily for users on Windows or those who prefer it.
- Add explicit notes or links for Linux-native scripting and automation (bash, shell scripts) where relevant.
- Ensure that troubleshooting and log file references use Linux paths and conventions, as is mostly done.
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 alongside Azure CLI and ARM template examples. The PowerShell example is presented before the Azure CLI example, which is more relevant for Linux users. There is also mention of a Windows extension, but only as a cross-reference, not as a primary topic. All screenshots and manual steps are Linux-specific, and troubleshooting/logging paths are Linux-centric.
Recommendations
- Move the Azure CLI example before the PowerShell example, as Azure CLI is more commonly used for Linux VM management.
- Clearly indicate that PowerShell is optional and primarily for users managing Azure from Windows environments.
- Consider adding Bash shell script examples for common tasks, as Bash is the default shell for most Linux users.
- If PowerShell is included, add a note explaining its cross-platform nature, but clarify its typical usage scenarios.
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 the Azure Key Vault VM Extension for Linux and provides extensive Linux-specific details. However, in several sections, Windows-oriented tools (Azure PowerShell) are presented before their Linux equivalents (Azure CLI), and PowerShell deployment examples are more detailed and appear first. Troubleshooting instructions also mention PowerShell before CLI. There are no missing Linux examples or Windows-only tools, but the ordering and emphasis could create friction for Linux users.
Recommendations
- Present Azure CLI examples before Azure PowerShell examples, as CLI is cross-platform and preferred for Linux users.
- Expand CLI troubleshooting instructions to match the detail provided for PowerShell.
- Clarify that PowerShell examples are optional and primarily for Windows users, while CLI is recommended for Linux.
- Consider adding Bash script examples for common deployment scenarios.
- Ensure all deployment and troubleshooting instructions are equally detailed for CLI and PowerShell.
Virtual Machines
What's New in Azure VM Image Builder
...ual-machines/image-builder-api-update-release-notes.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation covers Azure VM Image Builder updates for both Linux and Windows VMs. However, in sections providing API usage examples, Windows/PowerShell commands are presented alongside Azure CLI and HTTP, with PowerShell shown last but present. In customization and validation feature lists, Windows-specific tools (PowerShell, Windows Update, Windows restart) are mentioned, but Linux equivalents (Shell, File) are also included. The documentation does not prioritize Windows tools or patterns over Linux, but Windows examples and tools are consistently present, sometimes with more detail (e.g., PowerShell options like 'run elevated, run as system').
Recommendations
- Ensure Linux and Windows examples are given equal prominence and detail.
- Where PowerShell examples are provided, also include Bash or Shell script examples for Linux users.
- If Windows-specific features are described in detail (e.g., PowerShell options), provide comparable detail for Linux features (e.g., shell script execution modes).
- Consider alternating the order of examples so Linux and Windows are not always in the same sequence.
- Explicitly note when a feature or example is cross-platform or platform-specific.
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 between Windows and Linux throughout most sections, including CLI, REST, and portal instructions. However, in the PowerShell example, Windows is shown first and Linux is only mentioned as a note. Additionally, PowerShell is presented as a primary scripting option, which is more common for Windows users. The CLI examples are Linux-centric, but PowerShell sections could be more balanced. Overall, the bias is minor and does not prevent Linux/macOS users from completing the task.
Recommendations
- In PowerShell sections, provide Linux examples first or equally, rather than defaulting to Windows.
- Explicitly show both Linux and Windows values in example code blocks, rather than referencing Linux as a note.
- Consider adding Bash or shell scripting examples for Linux/macOS users, especially for automation scenarios.
- Clarify that PowerShell can be used cross-platform, but highlight CLI as the preferred option for Linux/macOS 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
Windows Tools
Summary
The documentation covers multiple hypervisors (Hyper-V, KVM, VMware, Kickstart) for preparing a Red Hat Enterprise Linux VHD for Azure. However, Windows/Hyper-V tools and workflows are consistently presented first in each major section, and Windows-centric terminology (e.g., 'Hyper-V Manager', 'convert-vhd cmdlet') is referenced before Linux alternatives. Linux/KVM/VMware instructions are present and detailed, but Windows/Hyper-V is prioritized in ordering and tool mentions.
Recommendations
- Reorder sections so that Linux-native hypervisors (KVM, VMware, Kickstart) are presented before or alongside Hyper-V, rather than always after.
- In introductory notes, mention Linux-native tools (e.g., qemu-img, guestfish) equally or before Windows tools (e.g., Hyper-V Manager, convert-vhd).
- Where conversion tools are discussed, provide Linux command-line alternatives (e.g., qemu-img) in the same breath as Windows/PowerShell tools.
- Consider a summary table or flowchart at the top showing parity between Windows and Linux workflows for each hypervisor.
- Avoid language that implies Hyper-V is the default or preferred method for Linux VHD preparation.
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 section is given equal prominence to the CLI section, and PowerShell is a Windows-centric tool. The CLI example is cross-platform, but the documentation does not explicitly mention Linux/macOS compatibility or alternative tools. The PowerShell example may create friction for Linux/macOS users, as it is not natively available on those platforms without additional installation steps.
Recommendations
- Explicitly state that Azure CLI is cross-platform and works on Linux, macOS, and Windows.
- Consider mentioning that PowerShell Core is available for Linux/macOS, or clarify that the PowerShell example is primarily for Windows users.
- Provide links or brief instructions for installing Azure CLI and PowerShell Core on Linux/macOS.
- If possible, add a note about using Bash or other shell environments for Linux/macOS users.
- Ensure that CLI examples are shown first, as CLI is more universal across platforms.
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
Summary
The documentation covers both Linux and Windows VM images and is generally platform-neutral. However, there are subtle signs of Windows bias: PowerShell examples are often presented alongside or before CLI examples, and references to Windows-specific tools (like Sysprep) appear before Linux equivalents (waagent). Some links and examples reference Windows paths or documentation first. Linux parity is mostly maintained, but Windows tools and patterns are sometimes mentioned first or more prominently.
Recommendations
- Ensure CLI and PowerShell examples are presented in parallel, with equal prominence.
- Where possible, alternate the order of Windows and Linux references (e.g., mention waagent before Sysprep in some sections).
- Add explicit Linux-focused examples or links where only Windows examples are given.
- Review FAQ and troubleshooting sections to ensure Linux scenarios are equally covered.
Virtual Machines
HBv3-series virtual machine (VM) overview, architecture, topology - Azure Virtual Machines | Microsoft Docs
...main/articles/virtual-machines/hbv3-series-overview.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation generally presents both Linux and Windows as supported platforms for HBv3-series VMs. However, in the 'Software specifications' table, the 'Recommended OS for Performance' is listed as 'Windows Server 2019+' without mentioning any recommended Linux distributions, despite Linux being widely used for HPC workloads. Additionally, the order of OS support in the SRIOV RDMA row lists Linux distributions first, but the explicit recommendation for Windows may create a perception of Windows preference.
Recommendations
- Add recommended Linux distributions for performance (e.g., RHEL, Ubuntu, SLES) alongside Windows in the 'Recommended OS for Performance' row.
- Clarify that both Linux and Windows are supported and that the best OS may depend on workload requirements.
- If Windows is recommended for specific scenarios, specify those scenarios and provide equivalent Linux recommendations where applicable.
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 and examples. However, the introduction and overview sections discuss Windows Server 2016 time sync improvements and reference Windows documentation before Linux-specific details, which may create a perception of Windows-first bias. All configuration examples, tools, and commands are Linux-centric, with only a single PowerShell snippet used for base64 encoding cloud-init (which is relevant for Azure users on Windows workstations). No Linux examples are missing, and Linux tools are prioritized throughout.
Recommendations
- Move Windows Server 2016 discussion and references to a background or context section, clarifying that Azure infrastructure uses Windows but the focus is Linux VM configuration.
- Add a brief summary at the start emphasizing that the page is Linux-focused and all examples are for Linux VMs.
- For the PowerShell base64 example, provide a Linux equivalent (e.g., 'base64 cloud-config.txt') for users preparing cloud-init data on Linux/macOS workstations.
- Ensure that Linux documentation links are as prominent as Windows links in the 'Next steps' section.
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, the Windows section includes more detailed prerequisites and troubleshooting steps, and Windows PowerShell/Command Prompt examples are shown first in some places. The Linux section is concise and relies heavily on waagent, but does provide links to distro-specific guides. Both OSes are covered, but Windows examples and tools are sometimes presented with more depth.
Recommendations
- Expand Linux prerequisites to match the detail level of Windows (e.g., common issues, troubleshooting).
- Provide more explicit Linux CLI examples for deprovisioning and generalizing, including error handling.
- Ensure parity in guidance for post-generalization steps (e.g., marking VM as generalized, disk handling).
- Consider listing Linux instructions first, or alternating order in future revisions.
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, PowerShell is presented as a primary method alongside CLI, despite PowerShell being predominantly a Windows tool. The CLI example is given first, which is positive, but the PowerShell section is equally prominent and may imply parity, even though PowerShell usage on Linux/macOS is less common. No Linux-specific tools or shell examples (e.g., Bash) are provided, but Azure CLI is cross-platform.
Recommendations
- Clarify that PowerShell is primarily for Windows users, and Azure CLI is recommended for Linux/macOS.
- Consider adding a Bash shell example or note that Azure CLI commands work natively in Bash on Linux/macOS.
- Explicitly state platform compatibility for each example (e.g., 'Azure CLI: Windows, Linux, macOS; PowerShell: Windows, Linux (with PowerShell Core)').
- If possible, provide links or guidance for installing Azure CLI and PowerShell on Linux/macOS.
Virtual Machines
Create a Gallery for Sharing Resources
.../blob/main/articles/virtual-machines/create-gallery.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides examples for creating an Azure Compute Gallery using the Azure Portal, Azure CLI, PowerShell, and REST API. While all major cross-platform tools are covered, the PowerShell example is presented alongside CLI and REST, and the CLI is shown first in most cases. However, PowerShell is a Windows-centric tool, and its inclusion does not disadvantage Linux/macOS users since the CLI and REST examples are fully cross-platform and appear before PowerShell. There are no Windows-specific tools or patterns mentioned exclusively or before Linux equivalents, and no critical steps are Windows-only.
Recommendations
- Maintain the current order of examples, with Azure CLI and REST API shown before PowerShell.
- Clarify in the PowerShell section that it is primarily for Windows users, and recommend Azure CLI or REST for Linux/macOS users.
- Ensure parity in example detail and completeness across CLI, REST, and PowerShell sections.
- Consider adding a brief note at the top indicating that Azure CLI and REST API are fully cross-platform, while PowerShell is Windows-centric.
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 for all major tasks, but consistently presents PowerShell examples immediately after CLI, and sometimes with more detailed output. There are no missing Linux examples or Windows-only tools, but PowerShell is emphasized alongside CLI throughout, even though PowerShell is less common on Linux. The ordering (CLI first, then PowerShell) is good, but the repeated PowerShell focus may create minor friction for Linux users.
Recommendations
- Consider clarifying that Azure PowerShell is cross-platform but less common on Linux, and recommend CLI as the primary method for Linux users.
- Where possible, highlight Bash/CLI as the default for Linux, and mention PowerShell as an alternative.
- Add explicit notes about PowerShell availability on Linux, or link to installation instructions for Linux users.
- Review output examples to ensure parity between CLI and PowerShell, and avoid implying PowerShell is required for Linux tasks.
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 Azure PowerShell and Azure CLI examples for securing managed disk uploads/downloads, but PowerShell (a Windows-centric tool) is presented before CLI in several sections. Portal, PowerShell, and CLI are all referenced, but PowerShell is often listed before CLI, which may subtly prioritize Windows users. However, Linux/macOS users are not blocked from completing tasks, as CLI instructions are present and relevant links for Linux-specific tasks are included.
Recommendations
- Alternate the order of PowerShell and CLI examples, or present CLI first to avoid implicit Windows prioritization.
- Explicitly mention that Azure CLI works cross-platform and is recommended for Linux/macOS users.
- Ensure that all critical tasks have both PowerShell and CLI examples, and clarify any platform-specific limitations.
- Consider grouping PowerShell and CLI examples together, labeling them clearly for each platform.
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 'What's new in Azure Disk Storage' page is mostly platform-neutral, focusing on Azure Disk Storage features, regional availability, and enhancements. However, there are minor signs of Windows bias: some links and references point to Windows documentation first or exclusively, and Windows-specific documentation is sometimes mentioned before Linux equivalents. For example, the 'expand with Ultra Disks and Premium SSD v2' feature links to a Windows-specific article, and the 'LastOwnershipUpdateTime' property documentation links to a Windows page. Linux documentation is referenced in some places, but not always with equal prominence.
Recommendations
- Ensure that all feature documentation links include both Windows and Linux versions, or use platform-neutral pages when possible.
- When referencing platform-specific guides (e.g., expanding disks), mention both Windows and Linux articles equally and in parallel.
- Review linked documentation to confirm Linux parity and add Linux/macOS examples where missing.
- Avoid defaulting to Windows documentation unless the feature is Windows-only.
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 VMs, but includes PowerShell examples for deploying the extension, and in some sections, PowerShell is presented before Azure CLI or Linux-native commands. This may create friction for Linux users, as PowerShell is not the default scripting environment on Linux, and Azure CLI is more commonly used. However, Linux-specific commands and troubleshooting steps are provided throughout, and the overall guidance is Linux-centric.
Recommendations
- Move Azure CLI examples before PowerShell examples, as Azure CLI is the primary tool for Linux users.
- Clearly indicate that PowerShell examples are optional and primarily for users who prefer PowerShell or are working cross-platform.
- Add Bash shell script examples for common tasks, such as extension deployment and troubleshooting, to further improve Linux parity.
- Ensure that all screenshots and walkthroughs use Linux environments and tools.
- Consider removing PowerShell examples entirely, or placing them in a separate 'Windows users' section, since the extension is Linux-specific.