Virtual Machines
2112
Total Pages
1865
Linux-Friendly Pages
247
Pages with Bias
11.7%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
818 issues found
Showing 426-450 of 818 flagged pages
Virtual Machines
Customer intent: "As an IT administrator managing virtual machines, I want to aggregate OS update statuses and availability states across my machines, so that I can efficiently monitor and ensure the health of my infrastructure."
...es/virtual-machines/includes/azure-virtual-machines.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation presents both Azure CLI and Azure PowerShell examples for each query, with PowerShell (a Windows-centric tool) always included and often referenced in metadata and custom tags. Windows-specific terminology and tools (e.g., PowerShell, KB IDs for Windows updates) are present throughout. While Linux is supported (e.g., queries for Linux patching), Windows examples and terminology appear first and more frequently. There are no Linux/macOS-specific shell examples (e.g., bash, zsh), nor are there references to Linux-native tools or patterns outside of Azure CLI. The documentation does not provide parity for Linux/macOS users who may prefer native shell scripting or tools.
Recommendations
- Add bash/zsh shell script examples for Linux/macOS users alongside PowerShell.
- Ensure Linux-specific queries and terminology are presented with equal prominence and order as Windows examples.
- Reference Linux-native tools (e.g., curl, jq, grep) where appropriate for scripting and automation.
- Clarify that Azure CLI is cross-platform and highlight usage on Linux/macOS.
- Remove or balance Windows-centric metadata and custom tags (e.g., devx-track-azurepowershell) with Linux/macOS equivalents.
Create Pull Request
Virtual Machines
Create an encrypted image version with customer-managed keys
.../articles/virtual-machines/image-version-encryption.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell examples are presented first and in greater detail, with explicit references to Windows-centric tools and APIs (e.g., Cryptography API: Next Generation). While Azure CLI and Portal instructions are provided, the PowerShell section is more extensive, and Windows tools are mentioned before their Linux equivalents. There are no Linux-specific command-line examples or references to Linux-native tools or patterns.
Recommendations
- Present CLI examples before or alongside PowerShell examples to better support Linux/macOS users.
- Expand CLI instructions to match the detail and coverage of PowerShell examples.
- Include explicit notes or examples for Linux/macOS environments, such as shell scripting or integration with Linux-native tools.
- Replace or supplement references to Windows-specific cryptographic APIs with platform-neutral or Linux-relevant documentation.
- Clarify that Azure CLI works cross-platform and highlight any OS-specific considerations.
Virtual Machines
Customer intent: As a cloud storage administrator, I want to adjust the expiration settings of Shared Access Signatures for disks and snapshots, so that I can ensure compliance with the upcoming 60-day limit and maintain uninterrupted access for my users.
...articles/virtual-machines/includes/disks-sas-change.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation lists Azure PowerShell as a primary tool for managing SAS on disks and snapshots, alongside REST API and Azure CLI. PowerShell is a Windows-centric tool, and its mention in every example (with direct links) may suggest a Windows bias. Additionally, PowerShell is listed after REST API and Azure CLI, but its inclusion in all workflows may imply parity that doesn't exist for Linux/macOS users, as PowerShell is less commonly used or installed by default on those platforms.
Recommendations
- Explicitly state that Azure CLI and REST API are fully cross-platform and preferred for Linux/macOS users.
- Provide example commands for Azure CLI and REST API for each task, and clarify installation/usage instructions for non-Windows platforms.
- De-emphasize PowerShell as a primary tool, or provide equivalent bash/shell script examples.
- Add a note about PowerShell Core availability on Linux/macOS if PowerShell examples are retained.
Virtual Machines
Customer intent: "As an IT administrator, I want to troubleshoot common VM extension failures in Azure Resource Manager templates, so that I can ensure the proper deployment and functionality of IaaS infrastructure."
...des/virtual-machines-common-extensions-troubleshoot.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page references a Windows-specific template authoring guide and links to a Windows-focused TOC, without mentioning or providing equivalent Linux resources or examples. This suggests a bias toward Windows environments in both guidance and resource organization.
Recommendations
- Include links to Linux-specific template authoring documentation alongside Windows resources.
- Provide troubleshooting examples and guidance for both Windows and Linux VM extensions.
- Ensure TOC and navigation options are available for Linux users.
- Explicitly state when guidance applies to both platforms, or clarify differences.
Virtual Machines
Customer intent: As a system administrator, I want to hibernate and manage virtual machines using various tools, so that I can optimize resource usage and maintain system performance effectively.
...nes/includes/hibernate-resume-platform-instructions.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. PowerShell examples are provided for every operation, often with detailed output, while Linux/macOS-specific shell examples (e.g., Bash) are not shown. The only CLI examples use Azure CLI, which is cross-platform, but PowerShell (Windows-centric) is given equal or greater prominence, and Windows-specific requirements (e.g., page file on C:) are called out without Linux equivalents. There are no explicit Linux/macOS shell command examples, and the documentation assumes familiarity with Windows tools and patterns.
Recommendations
- Add explicit Bash or Linux/macOS shell examples for each operation, especially for viewing VM state and managing hibernation.
- Clarify that Azure CLI commands work on Linux/macOS, and provide sample outputs from those platforms.
- For OS configuration notes, include Linux-specific guidance (e.g., swap file or hibernation setup for Linux VMs).
- Balance PowerShell and CLI examples, and avoid giving PowerShell more detail or prominence than CLI.
- Where Windows-specific requirements are listed, add equivalent Linux/macOS requirements or explicitly state if none exist.
Virtual Machines
Customer intent: As a cloud security administrator, I want to configure Azure Key Vault and Disk Encryption Set so that I can securely manage encryption keys for our managed disks across multiple subscriptions in compliance with security policies.
...-machines-disks-encryption-create-key-vault-powershell.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation exclusively uses Azure PowerShell for all examples and instructions, with no mention of Azure CLI, Bash, or Linux/macOS workflows. All commands and setup steps assume the use of PowerShell, which is natively available only on Windows and less commonly used on Linux/macOS. There are no alternative examples or guidance for users on non-Windows platforms.
Recommendations
- Add equivalent Azure CLI examples for all steps, as Azure CLI is cross-platform and commonly used on Linux/macOS.
- Explicitly mention that PowerShell examples can be run on Linux/macOS if PowerShell Core is installed, but provide CLI/Bash alternatives for greater accessibility.
- Include a section or note on platform compatibility, clarifying which tools are available on which operating systems.
- Consider reordering examples so that cross-platform tools (Azure CLI) are presented first or alongside PowerShell.
Virtual Machines
Customer intent: As a cloud administrator, I want to retrieve the encryption type of a specified disk in a resource group, so that I can ensure compliance with security standards for our virtual machines.
...ttps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/virtual-machines/includes/virtual-machines-disks-encryption-status-powershell.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation provides only a PowerShell example for retrieving the encryption type of a disk in Azure, with no equivalent example for Linux/macOS users (e.g., Azure CLI or Bash). This creates a bias towards Windows environments and tools.
Recommendations
- Add an Azure CLI example for Linux/macOS users.
- Include Bash or shell script alternatives where possible.
- Clearly indicate platform requirements for each example.
Virtual Machines
Customer intent: "As a cloud administrator, I want to create and manage incremental snapshots of virtual disks, so that I can efficiently utilize storage and ensure data integrity while complying with the snapshot limitations and performance impacts."
...tual-machines-disks-incremental-snapshots-restrictions.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation page references Azure PowerShell samples before Azure CLI, and links to PowerShell scripts for critical operations like checking disk status and managing snapshots. While Azure CLI is mentioned, the primary example and link are PowerShell-focused, which may create friction for Linux/macOS users who typically use CLI or Bash scripts.
Recommendations
- Provide Linux/macOS-specific examples using Azure CLI and Bash where PowerShell is referenced.
- Ensure that CLI examples are given equal prominence and are linked directly, not only as secondary options.
- Explicitly mention cross-platform compatibility for all scripts and commands.
- Add a section or note clarifying how Linux/macOS users can perform all documented tasks without PowerShell.
Virtual Machines
Customer intent: As a cloud architect, I want to understand the limitations of shared disks across different disk types, so that I can effectively design and implement scalable virtual machine solutions in the cloud environment.
.../includes/virtual-machines-disks-shared-limitations.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation repeatedly references Windows Server Failover Cluster as the only clustering solution, linking exclusively to Windows Server documentation. There are no mentions of Linux clustering solutions (e.g., Pacemaker, Corosync), nor any Linux-specific limitations or guidance. All clustering examples and hardware requirements are Windows-centric, creating a perception that shared disk features are primarily for Windows users.
Recommendations
- Add references to Linux clustering solutions (such as Pacemaker or Corosync) and discuss their compatibility and limitations with Azure shared disks.
- Include links to Linux documentation for clustering and shared disk usage.
- Explicitly state whether shared disks are supported or unsupported for Linux-based clusters, and provide guidance for Linux users.
- Balance examples and references between Windows and Linux to ensure parity.
Virtual Machines
Use infrastructure automation tools
...articles/virtual-machines/infrastructure-automation.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation generally covers both Linux and Windows automation tools, but there are several instances of Windows bias. Windows-specific tools (PowerShell DSC, Windows Resource Manager template examples, Chef on Windows, Puppet install on Windows) are mentioned or linked before Linux equivalents, and some sections lack Linux examples or parity (e.g., Chef and Puppet). Windows tools like PowerShell DSC are highlighted, while Linux alternatives (cloud-init, Ansible) are sometimes presented later or with less detail. Some 'Learn how to' links are Windows-only or Windows-first.
Recommendations
- Ensure every Windows example or link has a Linux/macOS equivalent, especially for Chef and Puppet sections.
- Present Linux and Windows examples side-by-side or in parallel, rather than listing Windows first.
- Add more Linux-focused 'Learn how to' links for Chef and Puppet, not just Windows install guides.
- Where Windows tools (e.g., PowerShell DSC) are mentioned, also highlight Linux-native alternatives (e.g., Ansible, cloud-init) with equal prominence.
- Review ordering of examples and links to avoid Windows-first presentation.
- Clarify cross-platform support in each section, especially where only Windows is referenced.
Virtual Machines
Prepare Linux for imaging
...ticles/virtual-machines/linux/create-upload-generic.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page is focused on Linux preparation for Azure imaging, but references to Windows tools (Hyper-V Manager, PowerShell cmdlets) are given first and in more detail than Linux alternatives. For example, disk conversion and resizing instructions prioritize Hyper-V Manager and PowerShell (Convert-VHD, Resize-VHD) before mentioning Linux tools like qemu-img. This ordering and emphasis may create friction for Linux users, although Linux alternatives are provided.
Recommendations
- Present Linux-native tools (qemu-img, vbox-manage) before or alongside Windows tools when discussing disk conversion and resizing.
- Provide more detailed Linux-specific instructions for tasks currently described with Windows tools (e.g., converting VHDX to VHD using qemu-img).
- Include explicit examples for common Linux environments (e.g., KVM, VirtualBox) where only Hyper-V/Windows instructions are currently detailed.
- Clarify that Windows tools are optional and not required for Linux users.
- Ensure that all critical steps can be completed using Linux-native tools, with equal detail and prominence.
Virtual Machines
Create and upload a CentOS-based Linux VHD
...rticles/virtual-machines/linux/create-upload-centos.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias by exclusively referencing Hyper-V (a Windows virtualization tool) for creating and managing VHDs, providing links to Windows-centric instructions, and omitting equivalent Linux-based workflows (such as using KVM, qemu-img, or VirtualBox CLI). Windows tools and terminology (Hyper-V Manager, convert-vhd cmdlet) are mentioned first and sometimes exclusively, while Linux alternatives are only briefly referenced or not explained in detail.
Recommendations
- Add step-by-step instructions for creating and converting VHDs using Linux-native tools (e.g., qemu-img, KVM, VirtualBox CLI).
- Include links to official documentation for Linux virtualization solutions and disk conversion utilities.
- Present Linux and Windows options side-by-side, or provide separate sections for each platform.
- Clarify that Hyper-V is only one of several options and not a requirement.
- Provide parity in example commands and screenshots for Linux environments.
Virtual Machines
Create and upload an Ubuntu Linux VHD in Azure
...rticles/virtual-machines/linux/create-upload-ubuntu.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page is focused on creating and uploading an Ubuntu Linux VHD for Azure, but it repeatedly references Windows-specific tools (notably Hyper-V and PowerShell's Convert-VHD) for VHD creation and conversion. Instructions for using Hyper-V Manager and Convert-VHD are provided, but there are no equivalent examples or guidance for Linux-native virtualization and disk conversion tools (e.g., qemu-img, VirtualBox, KVM). Windows tools are mentioned first and exclusively in critical steps, creating friction for Linux/macOS users.
Recommendations
- Add instructions and examples for creating and converting VHDs using Linux-native tools such as qemu-img, VirtualBox, or KVM.
- Provide parity for disk conversion steps, e.g., show how to convert raw disks to fixed-size VHD using qemu-img.
- Include links to Linux/macOS virtualization guides alongside the Hyper-V references.
- Clarify which steps are platform-agnostic and which require platform-specific tooling, offering alternatives where needed.
Virtual Machines
Creating and configuring a key vault for Azure Disk Encryption with Microsoft Entra ID (previous release)
...irtual-machines/linux/disk-encryption-key-vault-aad.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation provides extensive PowerShell examples and scripts, including certificate handling paths using Windows conventions (e.g., C:\certificates), and relies heavily on Windows-centric tooling. While Azure CLI and portal instructions are included, PowerShell is often presented first and in greater detail. There are no Linux shell (bash) or macOS-specific examples, and certificate-based authentication is explicitly noted as unsupported on Linux VMs, but Windows patterns are still shown. The lack of Linux-native scripting or file path examples may create friction for Linux users.
Recommendations
- Add bash shell examples for all major steps, especially for certificate generation, file handling, and key vault operations.
- Include Linux file path conventions (e.g., /home/user/certs/mycert.pfx) in examples alongside Windows paths.
- Clarify which steps are cross-platform and which are Windows-only, especially for certificate-based authentication.
- Present Azure CLI examples before PowerShell when targeting Linux audiences.
- Explicitly mention Linux prerequisites and common tools (e.g., openssl for certificate generation) where relevant.
Virtual Machines
Creating and configuring a key vault for Azure Disk Encryption
...es/virtual-machines/linux/disk-encryption-key-vault.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Windows First
Summary
While the documentation is targeted at Linux VM administrators and references Linux-specific quickstarts, it repeatedly presents Azure PowerShell (a Windows-centric tool) alongside Azure CLI, and links to PowerShell scripts and quickstarts as primary resources. PowerShell examples and tools are mentioned as equally valid for Linux, but in practice, PowerShell is far less common on Linux. The documentation also lists PowerShell scripts before CLI scripts in several places, and does not clarify that CLI is the more typical tool for Linux users.
Recommendations
- Prioritize Azure CLI examples and scripts in the main text and quickstart listings, as CLI is the standard on Linux.
- Clearly indicate that Azure PowerShell is less commonly used on Linux and provide installation guidance only as a secondary option.
- List CLI scripts and quickstarts before PowerShell equivalents in all sections.
- Add explicit notes about tool suitability for Linux, e.g., 'Azure CLI is recommended for Linux users.'
- Remove or de-emphasize PowerShell references in sections specifically targeting Linux unless there is a compelling cross-platform reason.
Virtual Machines
Azure Disk Encryption scenarios on Linux VMs
...ticles/virtual-machines/linux/disk-encryption-linux.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Windows First
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for all major operations, but PowerShell (a Windows-centric tool) is given equal or greater prominence throughout. PowerShell cmdlets are referenced first in some critical backup instructions, and PowerShell-specific patterns (e.g., sequence version GUID generation) are explained in detail. There are multiple references to using PowerShell locally, and some instructions (such as Resource Manager template parameter retrieval) show PowerShell before CLI. The documentation assumes familiarity with PowerShell and its workflow, which may create friction for Linux/macOS users who prefer Bash and CLI tools.
Recommendations
- Prioritize Azure CLI examples and instructions before PowerShell, as CLI is cross-platform and native to Linux/macOS.
- Where PowerShell-specific steps are described (e.g., GUID generation for sequence version), provide equivalent Bash/CLI instructions or clarify that CLI handles these automatically.
- In Resource Manager template sections, show CLI commands before PowerShell, or present both together with equal prominence.
- Clarify that PowerShell is available on Linux/macOS, but recommend CLI for Linux users.
- Reduce references to Windows-centric workflows (e.g., local PowerShell installation) and highlight cross-platform alternatives.
- Add explicit Bash script examples for common tasks (e.g., variable initialization, disk mounting) where PowerShell scripts are shown.
Virtual Machines
Azure Disk Encryption sample scripts
...rtual-machines/linux/disk-encryption-sample-scripts.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation page, while focused on Azure Disk Encryption for Linux VMs, provides almost all automation and Azure interaction examples using PowerShell cmdlets and scripts. Key tasks such as listing encrypted VMs, uploading VHDs, managing Key Vault secrets, and attaching disks are shown exclusively with PowerShell, a Windows-centric tool. There are no az CLI, Bash, or Linux-native command examples for these Azure operations, and PowerShell is presented as the default/only method for interacting with Azure resources, which may create friction for Linux/macOS users who prefer or require non-Windows tooling.
Recommendations
- Provide equivalent az CLI and Bash script examples for all Azure resource management tasks (listing encrypted VMs, uploading VHDs, managing Key Vault secrets, attaching disks).
- Clearly indicate when PowerShell is required and offer guidance for installing and using PowerShell Core on Linux/macOS, or alternatives using native Linux tools.
- Where possible, link to or embed Linux-native workflows for Azure Disk Encryption tasks, ensuring parity in automation and scripting.
- Reorder examples so that Linux-native tools (az CLI, Bash) are presented before or alongside PowerShell, especially in documentation targeted at Linux users.
Virtual Machines
Azure Disk Encryption with Microsoft Entra App Linux IaaS VMs (previous release)
...es/virtual-machines/linux/disk-encryption-linux-aad.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation provides both Azure CLI and PowerShell examples for Linux VM disk encryption, but PowerShell is emphasized throughout, with more detailed scripts and explanations. Windows-centric tools and terminology (PowerShell cmdlets, Windows flags, references to BitLocker and Windows disk operations) are used extensively, sometimes even in Linux-specific contexts. In several places, PowerShell examples are presented before CLI, and some sections (e.g., pre-encrypted VHD) use Windows flags or lack explicit Linux CLI parity. There are also minor instances of Windows terminology in template instructions and backup/restore references.
Recommendations
- Ensure CLI examples are as detailed and prominent as PowerShell examples, especially for Linux scenarios.
- Remove or clarify Windows-specific flags (e.g., '-Windows' in Set-AzVMOSDisk) when describing Linux workflows.
- Add explicit Linux shell commands for disk operations (e.g., formatting, mounting) alongside PowerShell scripts.
- Review template instructions to ensure Linux terminology is used and avoid references to Windows VMs in Linux sections.
- Where PowerShell is referenced, clarify its cross-platform availability or provide equivalent bash/CLI instructions.
- Consider reordering sections so CLI examples appear before PowerShell for Linux-focused documentation.
Virtual Machines
Azure Disk Encryption with Microsoft Entra app prerequisites (previous release)
...virtual-machines/linux/disk-encryption-overview-aad.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page, while focused on Linux VMs, contains several instances of Windows bias. Windows-specific registry changes and BitLocker Group Policy settings are described in detail, with no equivalent Linux security or encryption configuration guidance. Windows tools (PowerShell scripts) are referenced explicitly, and Windows examples appear before or instead of Linux alternatives. There is little to no coverage of Linux-specific troubleshooting or configuration steps for disk encryption prerequisites.
Recommendations
- Add Linux-specific troubleshooting and configuration guidance, especially for network, TLS, and encryption prerequisites.
- Include Linux command-line examples (e.g., Bash, CLI) for verifying connectivity and configuring prerequisites.
- Provide parity in script references by highlighting Linux CLI scripts equally or before PowerShell scripts.
- If Windows-specific sections are necessary, clearly separate them and provide equivalent Linux sections.
- Mention Linux disk encryption mechanisms (e.g., dm-crypt, cryptsetup) if relevant, and clarify any differences in prerequisites.
Virtual Machines
How to upgrade Azure Disk Encryption on a disk
...cles/virtual-machines/linux/disk-encryption-upgrade.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page exhibits a notable Windows bias. The migration process is only documented using Azure PowerShell, with no Linux-specific CLI or script examples. The upgrade instructions and examples focus on PowerShell, a Windows-centric tool, and do not provide parity for Linux users. While the CLI is mentioned for version discovery, it is not offered for the migration step, and the migration process appears inaccessible to Linux-only environments.
Recommendations
- Provide Azure CLI-based migration instructions if supported, or clarify if migration is only possible via PowerShell.
- Include Bash or shell script examples for Linux users, or document how Linux administrators can perform the migration from non-Windows environments.
- Explicitly state platform requirements and offer guidance for Linux/macOS users on installing and using Azure PowerShell (e.g., via PowerShell Core on Linux).
- If migration is not possible outside PowerShell, add a clear note about this limitation and suggest alternatives or workarounds for Linux-only environments.
Virtual Machines
Azure CLI - Enable customer-managed keys with SSE - managed disks
...chines/linux/disks-enable-customer-managed-keys-cli.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation is primarily cross-platform and uses Azure CLI examples, which are suitable for both Linux and Windows. However, in the 'Next steps' section, PowerShell-based disaster recovery guides for VMware and Hyper-V are mentioned, which are Windows-centric tools. These are listed before any Linux-specific alternatives, and no Linux equivalents or parity guidance are provided for these scenarios.
Recommendations
- Add Linux/bash-based instructions or links for disaster recovery scenarios currently covered only by PowerShell.
- Explicitly mention if certain tasks (e.g., disaster recovery for VMware/Hyper-V) can be performed with Azure CLI or other cross-platform tools, or clarify Windows-only limitations.
- Reorder or balance the 'Next steps' section to present Linux-friendly options before or alongside Windows/PowerShell options.
- Where PowerShell is required, provide a note about Linux/macOS alternatives or workarounds, if any.
Virtual Machines
Enable end-to-end encryption using encryption at host - Azure CLI - managed disks
...chines/linux/disks-enable-host-based-encryption-cli.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation is primarily focused on Azure CLI usage, which is cross-platform and Linux-friendly. However, there are signs of Windows bias: references to PowerShell and Windows tools (especially in the 'Next steps' section, which links only to PowerShell samples), and important notes about breaking changes for 'PowerShell and Azure CLI' users, with PowerShell mentioned first. There are no explicit Linux/macOS examples, and the linked sample repository is PowerShell-centric, potentially leaving Linux users without parity for advanced scenarios.
Recommendations
- Add explicit Bash/Linux shell script samples alongside PowerShell samples in the linked repository.
- Provide links to Linux/macOS-specific documentation or sample repositories for managed disk encryption scenarios.
- When mentioning tooling, avoid listing PowerShell before CLI, or clarify cross-platform support.
- Include a note in 'Next steps' about where Linux/macOS users can find equivalent resources.
- Ensure that all example scripts in the documentation itself are tested and work on Linux/macOS (which is mostly true here, but the external samples are PowerShell-only).
Virtual Machines
Upload a VHD to Azure or copy a disk across regions - Azure CLI
...machines/linux/disks-upload-vhd-to-managed-disk-cli.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page exhibits moderate Windows bias. The primary upload example uses 'AzCopy.exe' with a Windows-style path, and does not provide a Linux/macOS equivalent (e.g., 'azcopy' or './azcopy' with POSIX paths). The only explicit file path example is Windows ('c:\somewhere\mydisk.vhd'), and there is no mention of Linux/macOS installation or usage patterns for AzCopy. The page also refers to preparing VHDs for Azure with a link to a Windows-specific guide, without referencing a Linux alternative. While most Azure CLI commands are cross-platform, the AzCopy section is Windows-centric, and Linux users may be left to infer how to adapt the instructions.
Recommendations
- Provide explicit AzCopy command examples for Linux/macOS, using POSIX paths (e.g., '/home/user/mydisk.vhd') and the correct executable name ('azcopy' or './azcopy').
- Include instructions or links for installing AzCopy on Linux/macOS, not just Windows.
- Reference or link to a guide for preparing VHDs for Azure from Linux, in addition to the Windows guide.
- Where file paths are shown, offer both Windows and Linux/macOS variants.
- Clarify that Azure CLI and AzCopy are cross-platform, and note any platform-specific differences.
Virtual Machines
Create an Azure Image Builder Bicep file or ARM template JSON template
.../articles/virtual-machines/linux/image-builder-json.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation provides both Windows and Linux coverage, but there is a notable Windows bias in several areas: PowerShell commands and tools are frequently referenced (sometimes exclusively), Windows-specific customizers (WindowsRestart, WindowsUpdate) exist without Linux equivalents, and Windows examples or notes often appear before Linux ones. Some instructions (e.g., generating SHA256 checksums, troubleshooting, Sysprep) are Windows-centric or use PowerShell as the default, with Linux alternatives mentioned later or not at all. The lack of a Linux restart customizer and the prioritization of Windows tools and patterns create friction for Linux/macOS users.
Recommendations
- Provide Linux/macOS command alternatives alongside PowerShell examples, especially for checksum generation and troubleshooting.
- Ensure Linux examples are presented with equal prominence and detail as Windows examples.
- Add a Linux restart customizer or document recommended Linux restart patterns for parity.
- Where Windows-only features exist (e.g., WindowsRestart, WindowsUpdate), clearly state Linux alternatives or workarounds.
- Avoid presenting Windows tools or patterns first unless they are universally applicable; alternate order or group by OS.
- Expand troubleshooting and operational examples to include Linux-native tools and commands.
Virtual Machines
Learn about hibernating your Linux virtual machine
...icles/virtual-machines/linux/hibernate-resume-linux.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation provides both Azure CLI and PowerShell examples for creating and managing Linux VMs with hibernation, but PowerShell examples are given equal prominence to CLI, despite PowerShell being a Windows-centric tool. The use of PowerShell is pervasive throughout, and in some cases, PowerShell is presented before or alongside CLI, which may create friction for Linux/macOS users who typically use Bash and CLI. There is also mention of 'git bash' for running Linux commands, which is a Windows tool, and may confuse native Linux users.
Recommendations
- Prioritize Azure CLI and Bash examples over PowerShell, as these are more native to Linux/macOS environments.
- Move PowerShell examples to a separate section or clearly mark them as relevant for Windows users managing Linux VMs remotely.
- Remove references to 'git bash' when instructing users to run commands on Linux; simply refer to the terminal or shell.
- Ensure all steps and examples can be completed using native Linux tools and workflows.
- Add explicit notes clarifying which examples are intended for Windows users and which for Linux/macOS users.