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 401-425 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
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, Windows-centric tools and patterns (notably Hyper-V Manager and PowerShell convert-vhd) are mentioned first and most prominently, especially in the introductory sections and throughout the step-by-step guides. Linux alternatives (KVM, VMware, Kickstart) are covered in detail, but Windows/Hyper-V tools and workflows are consistently presented before their Linux equivalents, and some conversion steps reference Windows tools as primary options.
Recommendations
- Reorder sections so Linux-native hypervisors (KVM, VMware, Kickstart) are presented before or alongside Hyper-V/Windows tools, especially in introductory notes.
- Explicitly mention Linux-native disk conversion tools (e.g., qemu-img) in the VHD conversion prerequisites and summary, not just in the hypervisor-specific sections.
- Where disk conversion is discussed, avoid suggesting Windows/PowerShell tools as the default; instead, provide parity by listing Linux tools first or equally.
- Clarify that all steps can be performed on Linux hosts, and highlight cross-platform alternatives where possible.
- Add a summary table comparing supported hypervisors and tools, with clear Linux options.
Create Pull Request
Virtual Machines
Time sync for Linux VMs in Azure
...blob/main/articles/virtual-machines/linux/time-sync.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation is focused on Linux VM time synchronization in Azure and provides extensive Linux-specific guidance, commands, and configuration examples. However, the introductory section discusses Windows Server 2016 time sync improvements and references Windows documentation before Linux-specific details. This could be seen as a minor 'windows_first' bias, as Windows technologies and links are mentioned upfront, despite the page being Linux-focused. All technical instructions, tools, and examples are Linux-centric, with no missing Linux examples or Windows-only tools.
Recommendations
- Move the Windows Server 2016 discussion and links to a background or context section, or clarify their relevance to Linux VM users.
- Consider adding a brief summary of how Azure host time sync benefits Linux VMs without focusing on Windows improvements.
- Ensure Linux-specific guidance is always prioritized and presented before any Windows-related context.
- If referencing Windows documentation, explicitly state its relevance to Linux VM users in Azure.
Virtual Machines
Overview of Azure Disk Storage
...in/articles/virtual-machines/managed-disks-overview.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Minor Windows Reference
Summary
The documentation is generally cross-platform and explicitly states applicability to both Linux and Windows VMs. However, there are minor signs of Windows bias: Windows terminology and links are sometimes presented first (e.g., MBR/GPT partitioning), Windows-specific tools (PowerShell) are referenced alongside Linux tools (Azure CLI), and some links and examples reference Windows first or more prominently. These biases are minor and do not prevent Linux/macOS users from completing tasks, as Linux equivalents are provided or referenced.
Recommendations
- Ensure Linux and Windows examples/tools are presented together, or alternate which is shown first.
- Where partitioning concepts are discussed, provide Linux-specific links and guidance alongside Windows references (e.g., link to Linux partitioning documentation when discussing MBR/GPT).
- When referencing upload tools, clarify parity between Azure CLI (Linux/macOS) and PowerShell (Windows), and ensure both are equally prominent.
- Review linked articles to confirm Linux parity in deeper content, especially for disk upload, encryption, and partitioning.
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 Azure portal, Azure CLI, PowerShell, and REST API. PowerShell is presented as a distinct example, but it is not prioritized or exclusively featured. The CLI examples (using Azure CLI) are cross-platform and shown before PowerShell. However, PowerShell is included as a separate tab, which may imply a slight Windows bias, but the overall structure ensures Linux parity. No Windows-only tools or patterns are used, and Linux/macOS users can complete all tasks using the CLI or REST API examples.
Recommendations
- Ensure that CLI examples are clearly labeled as cross-platform and are shown before PowerShell.
- Consider adding a note clarifying that Azure CLI works on Windows, Linux, and macOS.
- If possible, add Bash shell scripting examples for advanced scenarios, to further demonstrate Linux parity.
- Maintain the current tabbed structure, but avoid implying PowerShell is required for any step.
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 Windows Command Prompt examples are given, and the Windows steps are presented after the Linux steps. There is minor bias in that Windows-specific tools (Sysprep, Set-AzVm) are shown, but Linux equivalents (waagent, az CLI) are also covered. The order of sections (Linux first, Windows second) avoids 'windows_first' bias, but the Windows section uses PowerShell and Windows command-line tools exclusively, which is expected for Windows VMs.
Recommendations
- Ensure parity in detail and clarity between Linux and Windows sections.
- Consider adding explicit notes about cross-platform CLI tools (e.g., az CLI works on Windows, Linux, macOS).
- Where possible, mention that az CLI commands are available on all platforms.
- If any step is platform-specific, clarify it to avoid confusion.
Virtual Machines
Expand Virtual Hard Disks on a Linux VM
...b/main/articles/virtual-machines/linux/expand-disks.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Summary
The documentation is focused on expanding disks for Linux VMs and provides comprehensive Linux-specific guidance and examples. However, in the section about classic VM SKU support for 'expand without downtime', only a PowerShell script is provided to check SKU compatibility, with no equivalent Bash/Azure CLI example for Linux users.
Recommendations
- Add an Azure CLI or Bash example for checking classic VM SKU support for 'expand without downtime', so Linux users can perform the same check without needing PowerShell.
- Where PowerShell scripts are given, provide cross-platform alternatives or note if the check can only be performed from Windows.
- Clarify if the PowerShell script is required due to Azure API limitations, and link to any relevant CLI documentation if available.
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 provides comprehensive instructions for preparing and uploading a Red Hat Enterprise Linux VHD for Azure, covering multiple hypervisors (Hyper-V, KVM, VMware, Kickstart). However, throughout the document, Hyper-V (a Windows-centric hypervisor) is consistently presented first in each major section and example. The structure and ordering may subtly prioritize Windows users, but all Linux-centric workflows (KVM, VMware, Kickstart) are fully documented with detailed steps and parity.
Recommendations
- Reorder sections so that Linux-native hypervisors (KVM, VMware, Kickstart) are presented before or alongside Hyper-V, rather than always after.
- Add a short introductory note clarifying that all workflows are equally supported, and that the order does not imply preference.
- Consider grouping instructions by task (e.g., 'Prepare VM', 'Convert disk', 'Upload to Azure'), then provide hypervisor-specific details, rather than leading with Hyper-V.
- Ensure that references to Windows tools (e.g., Hyper-V Manager, convert-vhd cmdlet) are balanced with Linux-native alternatives (e.g., qemu-img, guestfish) in the introductory notes.
Virtual Machines
Time sync for Linux VMs in Azure
...blob/main/articles/virtual-machines/linux/time-sync.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation is focused on Linux VM time synchronization in Azure and provides extensive Linux-specific guidance, commands, and configuration examples. However, the introductory section discusses Windows Server 2016 time sync improvements and references Windows documentation before addressing Linux-specific mechanisms. This creates a minor 'windows_first' bias in the narrative, but all technical guidance and examples are Linux-centric.
Recommendations
- Move or minimize the Windows Server 2016 discussion to a background or context section, clarifying its relevance to Azure hosts rather than VM configuration.
- Begin the page with Linux-specific time sync mechanisms and configuration options, referencing Windows host infrastructure only as necessary for understanding Azure's time source.
- Ensure that Linux guidance is always presented first and Windows references are clearly marked as context, not actionable steps for Linux users.
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 covers backup and disaster recovery for Azure Managed Disks and is intended for both Linux and Windows VMs. However, there are minor signs of Windows bias: Windows-specific tools (e.g., Volume Shadow Service for application-consistent snapshots) are mentioned first and in more detail, while Linux equivalents (e.g., fsfreeze) are referenced briefly and with less explanation. Windows examples and terminology (SQL Server, Always On Availability Groups) appear before Linux options in some sections. There are no missing Linux examples, and the solutions described are generally cross-platform.
Recommendations
- Provide more detailed guidance and examples for Linux application-consistent backup, including common Linux database/application tools and patterns.
- Expand on the use of fsfreeze and clarify its limitations compared to Windows VSS.
- Mention Linux-first or cross-platform solutions in parallel with Windows tools, rather than after.
- Include references to Linux-specific backup solutions or third-party tools where relevant.
- Ensure parity in explanations for both OS types, especially in sections about coordinated backups.
Virtual Machines
Best practices for virtual machine cost optimization
...s/virtual-machines/cost-optimization-best-practices.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation is generally cross-platform, but there are minor instances of Windows bias. For example, in the VM selector section, the recommendation 'Use at least B2 for Windows machines' is given, but no equivalent guidance is provided for Linux machines. In the disk sizing section, Windows is mentioned specifically, while Linux is not. However, Linux pricing links and VM creation guides are referenced alongside Windows, and most recommendations are generic.
Recommendations
- Where specific guidance is given for Windows (e.g., 'Use at least B2 for Windows machines'), provide equivalent recommendations for Linux, or clarify if no such minimum applies.
- Ensure disk sizing and performance recommendations are equally explicit for Linux workloads.
- Review all examples and recommendations to ensure Linux is mentioned wherever Windows is, unless the guidance is genuinely Windows-specific.
- Consider adding a brief note clarifying when recommendations are OS-specific and when they are general.
Virtual Machines
Support matrix for VM restore points
...n/articles/virtual-machines/concepts-restore-points.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation presents Windows operating system support before Linux, but otherwise provides parity in describing supported OSes and limitations for both platforms. No Windows-specific tools, examples, or patterns are prioritized, and Linux support is clearly described. The 'Next steps' section references CLI, Portal, and PowerShell, but does not show a preference for Windows tools.
Recommendations
- Consider listing Linux operating system support before or alongside Windows to avoid implicit prioritization.
- Ensure that future examples or walkthroughs (linked in 'Next steps') provide both Linux and Windows instructions equally.
- Clarify in the 'Next steps' section that CLI and Portal are cross-platform, and PowerShell is available on Linux/macOS as well.
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 platforms. However, in several places, Windows/PowerShell examples and links are presented before their Linux/Azure CLI equivalents. References to PowerShell are slightly more prominent (e.g., in key rotation and revoking access), and Windows tools are mentioned first in 'Next steps' and throughout the article. Linux parity is generally maintained, but Windows examples are prioritized in ordering.
Recommendations
- Present Azure CLI (Linux/macOS) and PowerShell (Windows) examples and links side-by-side, or alternate their ordering to avoid Windows-first bias.
- Where possible, provide explicit Linux/macOS command examples alongside PowerShell, especially in sections referencing Azure Key Vault operations.
- Ensure that references to Azure CLI are as prominent as PowerShell, including in 'Next steps' and procedural links.
- Consider grouping cross-platform instructions together, clarifying which applies to each OS, rather than splitting by Windows/Linux.
- Review for any subtle language or tool preference and adjust to neutral, platform-agnostic phrasing.
Virtual Machines
Enable on-demand disk bursting
...ain/articles/virtual-machines/disks-enable-bursting.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides both Azure PowerShell and Azure CLI examples for enabling on-demand disk bursting, but the PowerShell section is presented before the CLI section. PowerShell is primarily associated with Windows environments, which may create friction for Linux/macOS users. There are no Linux-specific shell examples (e.g., Bash), but the CLI commands are cross-platform. No Windows-only tools or patterns are mentioned, and the feature itself is not Windows-specific.
Recommendations
- Present Azure CLI examples before PowerShell examples, as CLI is cross-platform and preferred by many Linux/macOS users.
- Explicitly note that Azure CLI commands work on Linux, macOS, and Windows.
- Consider adding Bash shell script examples for disk creation and bursting, or clarify that CLI commands can be run in Bash.
- Mention that Azure Cloud Shell supports both PowerShell and Bash environments.
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 key operations, but PowerShell examples are consistently presented before CLI (which is more cross-platform). Portal instructions are also included, but there is a slight preference for Windows-centric tools and ordering. However, Linux-specific guidance is present in the 'Next steps' section, and CLI examples are included throughout.
Recommendations
- Present Azure CLI examples before PowerShell, as CLI is cross-platform and more accessible to Linux/macOS users.
- Explicitly mention that Azure CLI works on Linux/macOS, and provide links to installation instructions for those platforms.
- Ensure parity in screenshots and instructions for the Azure Portal, noting any OS-specific differences if relevant.
- Consider adding bash or shell script examples where appropriate, especially for disk upload/download tasks.
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 major operations, but PowerShell examples are consistently present and often shown alongside or immediately after CLI examples. PowerShell is a Windows-centric tool, and its heavy presence may create friction for Linux/macOS users. However, Azure CLI examples are always provided, and the documentation explicitly states applicability to both Linux and Windows VMs. There are no Windows-only tools or patterns, and Linux parity is generally maintained.
Recommendations
- Consider explicitly stating that Azure CLI commands work cross-platform (Linux, macOS, Windows) and are recommended for non-Windows environments.
- Where PowerShell is used, clarify that it is primarily for Windows users, and highlight Azure CLI as the preferred option for Linux/macOS.
- If possible, provide brief guidance or links for installing and using Azure CLI on Linux/macOS.
- Ensure that any advanced operations (such as mounting disks to VMs) include CLI examples, not just PowerShell.
Virtual Machines
Share an Azure Managed Disk across VMs
...cs/blob/main/articles/virtual-machines/disks-shared.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation provides both Windows and Linux coverage, but Windows examples and tools (WSFC, CSV, Windows clustering, Windows-specific workloads) are consistently presented first and in greater detail. Windows clustering patterns (WSFC, CSV) are described before Linux equivalents (Pacemaker, Corosync), and Windows workloads are listed first with more links and explanations. Linux examples are present but less detailed, and Linux-specific tools (sg_persist, fence_scsi) are mentioned later and with less context. There are no CLI or PowerShell command examples, but Windows tools and templates are referenced more prominently.
Recommendations
- Present Linux and Windows examples in parallel or alternate order, rather than always Windows first.
- Expand Linux workload examples with more detailed descriptions and links, matching the depth of Windows coverage.
- Add explicit Linux command-line examples (e.g., sg_persist usage) and configuration steps for Pacemaker/Corosync.
- Reference Linux templates or sample architectures, similar to Windows SoFS and SAP templates.
- Clarify parity between Windows and Linux features, especially around clustering and disk reservation flows.
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 generally cross-platform and neutral, but there are minor signs of Windows bias. Some links and examples reference Windows documentation first or exclusively (e.g., 'expand with Ultra Disks and Premium SSD v2' links to a Windows-specific page, and disk conversion/expansion links show Windows before Linux). Additionally, the 'LastOwnershipUpdateTime' feature mentions Azure PowerShell and portal before Azure CLI, which may be perceived as Windows-centric. However, Linux equivalents are usually present or referenced, and no critical features are Windows-only.
Recommendations
- Ensure all feature links reference both Windows and Linux documentation equally, ideally linking to a cross-platform overview or listing both OS-specific guides.
- When mentioning tools (Azure CLI, PowerShell), list them in neutral or alphabetical order, and clarify cross-platform support.
- Where possible, provide explicit Linux/macOS examples alongside Windows/PowerShell examples, especially for disk management tasks.
- Review and update any section where only Windows documentation is linked, adding Linux/macOS equivalents.
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation covers both Linux and Windows VMs for ephemeral OS disks, and provides parity in most technical explanations. However, there are minor signs of Windows bias: Windows examples and details (such as page file placement and OS disk sizing) are sometimes mentioned first or in greater detail, and PowerShell is listed before CLI in the section on customer-managed keys. Linux-specific examples and tools are present but not always equally emphasized.
Recommendations
- Ensure Linux and Windows examples are presented with equal prominence, alternating order or grouping by OS where relevant.
- When referencing tooling (e.g., PowerShell and CLI), list both together or alternate which comes first.
- Expand Linux-specific details where Windows-specific technical nuances are discussed (e.g., page file placement, disk sizing).
- Add explicit Linux command examples or links where only Windows/PowerShell examples are given.
Virtual Machines
Azure Key Vault VM Extension for Linux
...rticles/virtual-machines/extensions/key-vault-linux.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation is focused on Linux, but in several sections, Windows-centric tools (Azure PowerShell) are presented before their Linux-friendly equivalents (Azure CLI). PowerShell deployment instructions and troubleshooting are shown first, despite Azure CLI being more native to Linux environments. However, Linux-specific details, paths, and behaviors are well covered, and Azure CLI examples are present throughout.
Recommendations
- Present Azure CLI examples before Azure PowerShell in deployment and troubleshooting sections, as CLI is more native to Linux users.
- Add explicit notes clarifying that Azure CLI is recommended for Linux environments, and PowerShell is optional.
- Ensure troubleshooting commands for Azure CLI are as prominent as PowerShell.
- Consider adding Bash script examples for common certificate management tasks, if relevant.
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, in the troubleshooting section, PowerShell commands are shown before Azure CLI commands. There is a brief mention of 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 throughout.
Recommendations
- Move Azure CLI examples before PowerShell examples, as Azure CLI is cross-platform and more relevant for Linux users.
- Clearly indicate that PowerShell is optional and primarily for Windows users, or provide Bash scripting equivalents where appropriate.
- Consider removing PowerShell examples from Linux-focused documentation, or place them in a separate section for users managing from Windows.
- In troubleshooting, show Azure CLI commands first, followed by PowerShell, to prioritize Linux user workflows.
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 is a mild Windows bias in example ordering and PowerShell usage. In the PowerShell section, Windows is shown first in the example, and Linux is mentioned as an alternative. CLI examples are Linux-first, but PowerShell examples are Windows-first. Both platforms are covered, but Windows examples tend to be prioritized or shown first in some sections.
Recommendations
- In PowerShell examples, show Linux usage first or provide parallel examples for both OS types.
- Ensure that example ordering alternates or is neutral (e.g., 'Linux and Windows') rather than 'Windows and Linux'.
- Explicitly state that all commands and workflows apply equally to Linux and Windows, and highlight any OS-specific differences.
- Where possible, provide Linux-specific PowerShell examples (e.g., using -OsType Linux) alongside Windows examples.
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
Summary
The documentation presents benchmarking instructions for both Windows (DISKSPD) and Linux (FIO), but the Windows section appears first and is more detailed in its parameter explanations. Both tools are covered with example commands and screenshots, and Linux parity is generally good, but the ordering and depth of parameter explanation may create a minor perception of Windows bias.
Recommendations
- Consider presenting Linux (FIO) and Windows (DISKSPD) sections in parallel, or alternating their order in different documentation versions.
- Provide equally detailed parameter explanations for FIO as are given for DISKSPD.
- Add a summary table comparing DISKSPD and FIO usage for benchmarking across platforms.
- Explicitly state that both tools are recommended and supported for their respective OSes.
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 instructions and examples. However, there is mild evidence of Windows bias in the order and prominence of Azure PowerShell references: PowerShell is mentioned alongside Azure CLI in quickstart links and 'Next steps', and PowerShell cmdlets are listed in the terminology table, even though PowerShell is not a native Linux tool. Azure CLI is the primary Linux-native tool, but PowerShell is given equal visibility, which may create confusion or friction for Linux users.
Recommendations
- List Azure CLI examples and quickstarts before PowerShell in all sections, as CLI is more native to Linux.
- Clarify that PowerShell is optional and not required for Linux users, and that Azure CLI is the recommended tool for Linux environments.
- In the terminology table, note that PowerShell cmdlets are available for cross-platform use, but Azure CLI is the default for Linux.
- Consider adding a brief section explaining the difference between Azure CLI and PowerShell for Linux users, including installation and usage guidance.
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 examples and terminology are often presented first or with greater detail. PowerShell cmdlets are referenced in critical backup and encryption steps, sometimes before CLI equivalents. The documentation occasionally uses Windows-centric language (e.g., 'PowerShell session') and emphasizes PowerShell-specific requirements (like sequence version generation) more than CLI. However, Linux parity is generally maintained, and CLI examples are present throughout.
Recommendations
- Ensure Azure CLI and PowerShell examples are presented in parallel, with equal prominence and detail.
- Avoid Windows-centric terminology (e.g., 'PowerShell session') when referring to cross-platform tools; clarify that Azure CLI can be used in Bash, Zsh, etc.
- Where PowerShell-specific requirements are discussed (such as sequence version generation), provide equivalent CLI explanations or clarify differences.
- Consider starting sections with Azure CLI examples, as CLI is more native to Linux users.
- Explicitly mention that both Azure CLI and PowerShell are fully supported on Linux/macOS, and link to installation instructions for Bash/Zsh environments.
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 provides a balanced overview of Azure Managed Disks for both Linux and Windows VMs, with explicit applicability to both platforms. However, there are minor signs of Windows bias: Windows terminology and links are sometimes presented first or exclusively (e.g., references to Sysprep, MBR/GPT partitioning, and Windows drive letters), and some links point to Windows-specific documentation before Linux equivalents. The section on uploading VHDs does provide both Azure CLI (Linux) and PowerShell (Windows) links, but Windows terminology (drive letters, Sysprep) is more prominent in some explanations.
Recommendations
- Ensure Linux-specific terminology and examples are presented alongside Windows ones, not after or instead of them.
- When referencing partitioning (MBR/GPT), include links to Linux partitioning documentation (e.g., fdisk, parted) and explain Linux default behaviors.
- When discussing OS disk and drive letters, clarify Linux mount points and device names (e.g., /dev/sda, /dev/disk/azure/resource) in parallel to Windows drive letters.
- For image creation, mention Linux generalization methods (e.g., waagent -deprovision) alongside Sysprep.
- Where possible, provide links to Linux documentation before or alongside Windows links, especially in sections where Windows links are currently dominant.