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 601-625 of 818 flagged pages
Virtual Machines
Share a Capacity Reservation Group in Azure
...s/virtual-machines/capacity-reservation-group-share.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Windows First
Summary
The documentation provides examples for API, Azure CLI, PowerShell, and ARM templates for all major operations. PowerShell is featured as a primary automation tool, and PowerShell examples are present for every operation, sometimes with more detail than CLI. References to PowerShell commands and modules are frequent, and links to PowerShell documentation are provided before or alongside CLI links. There is no explicit Linux shell scripting (e.g., Bash) or macOS-specific guidance, and PowerShell is a Windows-native tool (though cross-platform now), which may signal a Windows-centric approach. However, Azure CLI is cross-platform and is included for all tasks, mitigating the bias somewhat.
Recommendations
- Add explicit Bash shell script examples for Linux/macOS users, especially for automation scenarios.
- Clarify that Azure CLI commands work equally on Linux, macOS, and Windows, and provide platform-specific notes if there are differences.
- Reorder examples to present CLI (cross-platform) before PowerShell, or alternate the order to avoid implicit prioritization.
- Include troubleshooting or environment setup notes for Linux/macOS users (e.g., installing Azure CLI, using Bash, etc.).
- Mention that PowerShell Core is available cross-platform, but provide Bash alternatives for users who prefer native Linux/macOS tools.
Create Pull Request
Virtual Machines
Migrate from Azure Disk Encryption to encryption at host
...n/articles/virtual-machines/disk-encryption-migrate.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Minor Example Ordering
Summary
The documentation generally provides parity for both Windows and Linux, with clear callouts for OS-specific limitations and steps. However, there is a subtle Windows bias in the ordering of examples and instructions: Windows steps and PowerShell commands are often listed before Linux equivalents, and Windows-specific tools (e.g., manage-bde, Remove-Computer) are mentioned first. PowerShell is used heavily for both OSes, but Linux-specific shell commands are present. There are no critical missing Linux instructions, but the structure and ordering may create minor friction for Linux users.
Recommendations
- Alternate the order of Windows and Linux instructions/examples to avoid always presenting Windows first.
- Where possible, provide Bash/shell script examples for Linux tasks alongside PowerShell for Windows, especially in verification and management steps.
- Highlight Linux-specific tools and commands with equal prominence as Windows tools (e.g., give 'cryptsetup' and 'lsblk' the same emphasis as 'manage-bde').
- Consider adding a summary table or section at the top outlining the differences and steps for both OSes, so Linux users can quickly find relevant information.
- Ensure that all PowerShell-based instructions for Linux are complemented with native Bash/SSH alternatives where appropriate.
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
Windows Tools
Minor Windows Reference
Summary
The documentation generally maintains parity between Windows and Linux, referencing both Azure PowerShell and Azure CLI for most tasks. However, there are several instances of Windows bias: Windows/PowerShell links and examples are consistently listed before Linux/CLI equivalents, PowerShell is mentioned more frequently (e.g., for revoking access), and Windows-specific tools (BitLocker, CNG API) are referenced with less emphasis on Linux equivalents (DM-Crypt). Some conceptual sections link to Windows documentation or tools first, and the automatic key rotation walkthrough is only linked to a Windows/PowerShell guide.
Recommendations
- Alternate the order of Windows and Linux examples/links so Linux is not always second.
- Ensure every PowerShell example or link is paired with an equivalent CLI/bash example or link.
- Add explicit references to Linux tools (e.g., DM-Crypt) wherever Windows tools (BitLocker, CNG API) are mentioned.
- Provide a Linux/CLI guide for automatic key rotation, not just a Windows/PowerShell version.
- Where possible, use neutral language (e.g., 'Azure CLI or PowerShell') rather than listing Windows tools first.
- Include Linux/macOS-specific troubleshooting or caveats if any exist.
Virtual Machines
Benchmark your application on Azure Disk Storage
...lob/main/articles/virtual-machines/disks-benchmarks.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation mentions both Windows and Linux VMs are supported, and references both DiskSpd (Windows) and FIO (Linux) as benchmarking tools. However, DiskSpd (Windows) is mentioned first, and the introductory text gives slightly more prominence to Windows by listing its tool before Linux. There are no explicit examples shown for either platform, but the ordering and tool references suggest a mild Windows-first bias.
Recommendations
- Alternate the order of tool mentions (e.g., 'FIO and DiskSpd') or mention both together to avoid implicit prioritization.
- Provide explicit example commands for both Windows (DiskSpd) and Linux (FIO) to ensure parity.
- Include links to installation and usage guides for both tools, not just their homepages.
- Consider a table or side-by-side comparison of benchmarking steps for Windows and Linux.
Virtual Machines
Convert managed disks storage between different disk types
.../main/articles/virtual-machines/disks-convert-types.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Windows First
Summary
The documentation provides both Azure PowerShell and Azure CLI examples for all major disk conversion tasks, ensuring cross-platform coverage. However, PowerShell (a Windows-centric tool) is consistently presented first in code example tabs, and PowerShell scripts are shown before CLI scripts in every section. There are references to converting unmanaged disks with 'CLI' (Linux) or 'PowerShell' (Windows), but the links are clearly separated. The documentation does not use Windows-only tools or patterns in the actual conversion steps, but the ordering and prominence of PowerShell may subtly favor Windows users.
Recommendations
- Alternate the order of example tabs so that Azure CLI is shown first in some sections, especially for tasks commonly performed on Linux.
- Explicitly state that both PowerShell and CLI are fully supported on Windows, Linux, and macOS, and clarify that CLI is cross-platform.
- Add a short note at the top explaining that the examples are equivalent and users should choose the tool that matches their environment.
- Consider including Bash or shell script snippets for common Linux workflows if relevant.
- Ensure parity in documentation links for converting unmanaged disks, perhaps by grouping them together and clarifying platform applicability.
Virtual Machines
Use a disk encryption set across Microsoft Entra tenants
...l-machines/disks-cross-tenant-customer-managed-keys.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation page demonstrates mild Windows bias by referencing PowerShell and Windows installation instructions before Linux alternatives, and by linking specifically to 'Install Azure PowerShell on Windows with PowerShellGet'. However, all major tasks are also covered with Azure CLI and ARM/REST API examples, which are cross-platform. No critical functionality is locked to Windows-only tools.
Recommendations
- Add explicit instructions or links for installing Azure PowerShell on Linux/macOS alongside the Windows instructions.
- Clarify that both Azure PowerShell and Azure CLI are cross-platform, and provide parity in example ordering (e.g., alternate which is shown first or present both together).
- Where installation instructions are referenced, link to the general Azure PowerShell installation page, not just the Windows-specific guide.
- Consider adding a note that all shown CLI/PowerShell commands work on Linux/macOS unless otherwise stated.
Virtual Machines
Create an incremental snapshot
...ticles/virtual-machines/disks-incremental-snapshots.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI (cross-platform) and Azure PowerShell (Windows-centric) examples for all major tasks, but consistently presents PowerShell examples immediately after CLI and with equal prominence. There is no explicit Linux shell scripting or macOS-specific guidance, and PowerShell examples are detailed and assume familiarity with Windows tooling. No Linux-specific tools or troubleshooting are mentioned, and the CLI examples use Bash syntax, which is cross-platform but not explicitly called out as Linux/macOS friendly.
Recommendations
- Add explicit Linux/macOS shell scripting notes, such as mentioning that Azure CLI commands work natively in Bash/Zsh on Linux/macOS.
- Provide troubleshooting or environment setup notes for Linux/macOS users (e.g., permissions, package managers, etc.).
- Clarify that PowerShell examples are primarily for Windows users, and suggest alternatives for Linux/macOS users where appropriate.
- Consider adding example scripts using other popular Linux tools (e.g., curl, jq) for querying Azure APIs.
- Where possible, present CLI examples before PowerShell, or clearly mark CLI as the recommended cross-platform approach.
Virtual Machines
Enable end-to-end encryption using encryption at host - Azure portal - managed disks
...-machines/disks-enable-host-based-encryption-portal.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation demonstrates mild Windows bias by listing Azure PowerShell (commonly used on Windows) examples before Azure CLI in command sections, referencing PowerShell in links and resource samples, and providing links to PowerShell-based guides and samples. However, Azure CLI examples are present for all commands, and the portal instructions are platform-neutral. No critical Linux functionality is missing.
Recommendations
- Alternate the order of PowerShell and CLI examples, or present CLI examples first to better support Linux/macOS users.
- Include direct links to Linux/macOS-specific guides and samples alongside PowerShell resources.
- Clarify that Azure CLI is cross-platform and highlight its usage for Linux/macOS users.
- Ensure parity in referenced sample repositories (e.g., provide CLI-based sample templates).
Virtual Machines
Change the performance of Azure managed disks
...n/articles/virtual-machines/disks-performance-tiers.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Windows First
Summary
The documentation provides parallel examples for Azure CLI and Azure PowerShell, with PowerShell being a Windows-centric tool. While Azure CLI is cross-platform, the presence of PowerShell examples and terminology throughout the page reflects a Windows bias. There is no explicit mention of Linux/macOS shell usage (e.g., bash, zsh), and PowerShell instructions are given equal prominence to CLI, which may not be relevant for Linux users. The documentation does not provide Linux-specific command-line nuances or highlight Linux shell scripting patterns. However, Azure CLI examples are present and shown first in each section, which helps mitigate the bias.
Recommendations
- Add explicit notes clarifying that Azure CLI commands work on Linux/macOS and Windows, while PowerShell is primarily for Windows.
- Include Linux/macOS shell-specific instructions or troubleshooting tips where relevant (e.g., environment variable syntax differences).
- Consider adding bash/zsh script examples for common tasks, or at least mention that Azure CLI commands can be run in those shells.
- Clarify that PowerShell is optional and not required for Linux/macOS users.
- Ensure parity in troubleshooting and advanced usage sections for Linux users.
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
Missing Linux Example
Summary
The documentation page is mostly a changelog and summary of new features, but there are several instances where Windows-specific links, terminology, or examples are presented before or instead of Linux equivalents. For example, links to Windows documentation (e.g., /azure/virtual-machines/windows/expand-disks) are given before Linux links, and some references point only to Windows-specific tools (PowerShell, Windows portal) or documentation. There are also cases where Linux parity is implied but not directly addressed, and some links or examples are missing Linux-specific guidance.
Recommendations
- Ensure that every feature or example referencing Windows has a corresponding Linux/macOS example or documentation link.
- When listing links for expanding disks or other operations, present Linux and Windows options together, or alternate which is listed first.
- Avoid referencing Windows-specific tools (e.g., PowerShell) without mentioning equivalent Linux/macOS tools (e.g., Azure CLI, Bash scripts).
- Audit linked documentation to ensure Linux/macOS users can complete all tasks described.
- Add explicit notes when a feature is Windows-only or has different instructions for Linux/macOS.
Virtual Machines
Azure Disk Encryption for Linux
...es/virtual-machines/extensions/azure-disk-enc-linux.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation is focused on Azure Disk Encryption for Linux and provides Linux-centric schema and deployment examples. However, in the warning section, the PowerShell cmdlet (Get-AzVMDiskEncryptionStatus) is mentioned before the Azure CLI equivalent (az vm encryption show) for checking encryption status. PowerShell is primarily a Windows tool, and listing it first may suggest a Windows-centric approach, even though the CLI is cross-platform. No Linux-specific command-line examples (e.g., bash, shell scripts) are provided for interacting with the extension or troubleshooting, and the troubleshooting/support sections do not reference Linux-native tools.
Recommendations
- List Azure CLI commands before PowerShell cmdlets when describing cross-platform tasks, as CLI is natively supported on Linux/macOS.
- Provide Linux-native command-line examples (e.g., bash, shell scripts) for interacting with the extension and troubleshooting.
- Explicitly mention that PowerShell Core is available on Linux, if PowerShell examples are retained.
- Reference Linux troubleshooting tools (e.g., journalctl, dmesg, systemctl) for diagnosing extension issues.
Virtual Machines
Enable InfiniBand on HPC VMs - Azure Virtual Machines | Microsoft Docs
...icles/virtual-machines/extensions/enable-infiniband.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Windows First
Summary
The documentation provides both Linux and Windows guidance for enabling InfiniBand on Azure HPC VMs. However, there is a mild Windows bias in the VM extension section, where Azure PowerShell is mentioned as the tool for adding extensions without an equivalent Linux CLI example (such as Azure CLI or ARM template). Windows tools and deployment models are referenced before Linux alternatives. Linux manual installation and configuration steps are well-covered, but Windows users are directed to download drivers without detailed installation steps.
Recommendations
- Provide Azure CLI and/or ARM template examples for adding VM extensions alongside PowerShell.
- Mention Linux tools (e.g., az CLI) before or alongside Windows tools when discussing VM extension management.
- Add more detailed Windows installation steps for Mellanox OFED drivers, similar to the Linux section.
- Ensure parity in troubleshooting and operational guidance for both platforms.
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 Linux and Windows in most CLI and REST examples, but there is a subtle Windows bias in the PowerShell section, where Windows is used as the default example and Linux is mentioned only as an alternative. Additionally, PowerShell examples are given equal prominence to CLI, which is more cross-platform, but PowerShell is primarily a Windows tool. In the 'Before you begin' section, Linux guidance is more extensive, but Windows instructions are presented as a single block, potentially implying Windows as the default. The ordering of examples sometimes places Windows first.
Recommendations
- Alternate the order of Linux and Windows examples so neither is always first.
- Provide explicit Linux PowerShell (pwsh) compatibility notes, or clarify that CLI is recommended for Linux/macOS users.
- In PowerShell examples, use Linux as the default in at least one example, or provide parallel Linux and Windows examples.
- Add a note at the start of the PowerShell section clarifying its platform support and recommending CLI for Linux/macOS.
- Ensure that all example code blocks and parameter tables clearly indicate which OS they apply to, and provide Linux/macOS equivalents where relevant.
Virtual Machines
Dedicated hosts include file
...es/virtual-machines/includes/dedicated-hosts-resize.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides examples for three interfaces: Portal, CLI, and PowerShell. The PowerShell section is given its own tab and detailed example, which is a Windows-centric tool. The CLI instructions use Azure CLI, which is cross-platform, but the PowerShell example is included as a primary method, potentially suggesting Windows as a first-class platform. There are no Linux/macOS-specific shell examples (e.g., Bash), nor is there mention of platform-specific considerations for non-Windows users.
Recommendations
- Add explicit Bash or shell examples for Linux/macOS users, especially for scripting resize operations.
- Clarify that Azure CLI commands work identically on Linux, macOS, and Windows.
- If PowerShell is mentioned, note that PowerShell Core is available cross-platform, or provide Bash alternatives.
- Consider reordering tabs or examples so that cross-platform methods (CLI) are presented before Windows-specific ones (PowerShell).
Virtual Machines
Customer intent: As a system administrator, I want to restrict uploads and downloads for Azure managed disks using identity verification, so that I can enforce security policies and ensure only authorized users can access sensitive data.
...ines/includes/disks-azure-ad-upload-download-portal.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation page presents PowerShell examples and references before Azure CLI, and mentions PowerShell as a primary method for role assignment and disk configuration. While Azure CLI examples are provided, the ordering and emphasis suggest a Windows-first approach, which may create friction for Linux/macOS users who typically prefer CLI or Bash-based workflows.
Recommendations
- Present Azure CLI examples before or alongside PowerShell examples, as CLI is cross-platform.
- Explicitly mention Linux/macOS compatibility for CLI commands.
- Add Bash or shell script examples where appropriate.
- Clarify that PowerShell is available on Linux/macOS, or link to installation instructions if PowerShell is required.
- Ensure screenshots and UI references are not Windows-specific.
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 Windows (DISKSPD) benchmarking instructions and examples before Linux (FIO) equivalents, but both platforms are covered with detailed, parallel guidance. No critical Linux omissions or Windows-only tooling are present.
Recommendations
- Reorder sections to present Linux (FIO) examples before or alongside Windows (DISKSPD) examples.
- Add a brief comparison table summarizing tool usage for both platforms at the top.
- Explicitly mention cross-platform alternatives for each tool where relevant.
- Clarify that both DISKSPD and FIO are platform-specific and provide links to installation guides for both.
Low Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Windows First
Summary
The documentation provides both Linux/macOS and Windows instructions for connecting to a Linux VM via SSH. However, in the Windows tab, the example for validating the SSH fingerprint uses Azure PowerShell (Invoke-AzVMRunCommand), while the Linux tab uses a direct SSH command. The Windows section also references PowerShell and Windows-specific paths. The main page and prerequisites mention Windows tools (WSL, Win32 OpenSSH) and provide guidance for Windows users before Linux/macOS equivalents. The overall structure does not exclude Linux users, but Windows tools and patterns are mentioned first or in more detail in some places.
Recommendations
- Provide parity in fingerprint validation: Offer a direct Azure CLI example for Windows users, not just PowerShell.
- When referencing SSH clients, mention Linux/macOS tools first or equally alongside Windows tools.
- Ensure that troubleshooting and next steps include Linux/macOS-specific guidance where relevant.
- Balance the order of examples so Linux/macOS instructions are not always after Windows-specific notes.
- Where possible, avoid assuming the user is on Windows when describing general Azure portal steps.
Virtual Machines
Azure Instance Metadata Service for virtual machines
...articles/virtual-machines/instance-metadata-service.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation provides both Windows (PowerShell) and Linux (bash/curl) examples for all core usage scenarios, including requests and responses. However, in several places, Windows/PowerShell examples are presented before Linux equivalents, and some troubleshooting and advanced scenarios (e.g., routing table checks, Azure CLI usage) use PowerShell syntax or Windows tools first, with Linux instructions following. There is a slight emphasis on Windows tools and PowerShell, but Linux parity is generally maintained.
Recommendations
- Alternate the order of Windows and Linux examples, or present them side-by-side to avoid implicit prioritization.
- Ensure troubleshooting steps and CLI examples are equally detailed for Linux (e.g., use Azure CLI and bash for interface and routing checks, not just PowerShell).
- Where Windows-specific tools (e.g., route print, ipconfig) are mentioned, ensure Linux equivalents (e.g., ip, netstat, ifconfig) are listed with equal prominence.
- Consider adding macOS-specific notes or examples where applicable, especially for curl/jq usage.
- Review the language in troubleshooting and FAQs to avoid assuming Windows as the default platform.
Virtual Machines
Prepare a Debian Linux VHD
...les/virtual-machines/linux/debian-create-upload-vhd.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation mentions Windows-specific tools (Hyper-V, convert-vhd cmdlet) for VHD creation and conversion before introducing Linux alternatives. While the main workflow is Linux-centric, Windows tools are referenced first and exclusively in some places, which may create confusion or friction for Linux users.
Recommendations
- Explicitly mention Linux-native tools for VHD creation and conversion (e.g., qemu-img, VBoxManage) alongside or before Windows tools.
- Provide links or brief instructions for using Linux tools to create and convert VHDs.
- Reorder sections so Linux methods are presented first, given the page's Linux focus.
- Clarify that Hyper-V is only one option and highlight Linux alternatives for each step.
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 PowerShell examples for all major operations, but PowerShell (a Windows-centric tool) is frequently mentioned first, and some backup/encryption workflows are described primarily in terms of PowerShell cmdlets. Resource Manager template parameter retrieval also shows PowerShell before CLI. There is no evidence of missing Linux examples or exclusive use of Windows tools, but the ordering and emphasis may create friction for Linux/macOS users.
Recommendations
- Present Azure CLI examples before PowerShell examples, as CLI is cross-platform and more natural for Linux/macOS users.
- Where PowerShell is referenced for parameter retrieval or scripting, ensure equivalent Azure CLI commands are shown first or side-by-side.
- Clarify that both CLI and PowerShell are supported on Linux/macOS, and recommend CLI for Linux users.
- Audit for any workflow steps that are described only in PowerShell and add CLI equivalents if missing.
- In tables and lists, show CLI commands before PowerShell, or group by platform.
Virtual Machines
Enable Azure Disk Encryption for Linux VMs
...les/virtual-machines/linux/disk-encryption-overview.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation is focused on enabling Azure Disk Encryption for Linux VMs and is generally Linux-centric. However, there is evidence of Windows bias: PowerShell is referenced multiple times as a primary tool for managing Azure resources, and PowerShell examples/scripts are given equal prominence to Azure CLI (which is more native to Linux). The terminology table includes 'PowerShell cmdlets' as a core concept, while no Linux-specific shell tools (e.g., Bash, Shell scripts) are mentioned. In the 'Next steps' section, PowerShell is listed alongside CLI, and the PowerShell script is referenced before the CLI script in the quickstart links. This may create friction for Linux users who expect Bash or CLI-first workflows.
Recommendations
- Prioritize Azure CLI and Bash examples/scripts over PowerShell for Linux documentation, as CLI is more native to Linux environments.
- Move PowerShell references and scripts after CLI/Bash examples in lists and quickstart links.
- Clarify that PowerShell is cross-platform, but recommend CLI/Bash for Linux users.
- Add a note in the terminology table about Bash/shell scripting for Linux users.
- Ensure that all critical workflows have CLI/Bash equivalents and are presented first.
Virtual Machines
Azure CLI - Restrict import/export access to managed disks with Private Links
...achines/linux/disks-export-import-private-links-cli.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation is primarily focused on Azure CLI, which is cross-platform and suitable for Linux, macOS, and Windows. However, in the 'Next steps' section, Windows and PowerShell resources are mentioned before Linux equivalents, and PowerShell is given as an alternative to Azure CLI for uploading VHDs, suggesting a Windows-centric approach. Additionally, the download VHD links list Windows before Linux. No Linux-specific tools or shell examples are provided, but the CLI examples themselves are platform-neutral.
Recommendations
- List Linux/macOS resources and examples before or alongside Windows equivalents in 'Next steps'.
- Provide Bash or Linux-specific command examples where appropriate, especially for tasks like downloading VHDs.
- Include references to Linux-native tools (e.g., dd, wget, azcopy) where relevant.
- Clarify that Azure CLI commands work on Linux, macOS, and Windows equally, and provide explicit instructions for Linux users if any steps differ.
- Balance PowerShell references with Bash or shell script alternatives.
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
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page exhibits mild Windows bias in the upload example, where only a Windows-style AzCopy.exe command is shown (with a Windows path and executable), and no explicit Linux/macOS AzCopy usage is demonstrated. The AzCopy tool is referenced using its Windows executable and path format, and Linux/macOS command-line equivalents are not provided. However, most Azure CLI examples use bash syntax and variables, which are cross-platform.
Recommendations
- Add explicit Linux/macOS AzCopy example, e.g., `azcopy copy /home/user/mydisk.vhd "sas-URI" --blob-type PageBlob`.
- Mention that AzCopy is available on Linux/macOS and provide installation instructions or a link.
- Use generic command syntax (e.g., `azcopy` instead of `AzCopy.exe`) and file paths in examples.
- Clarify that the process is identical on Linux/macOS, and note any OS-specific considerations.
Virtual Machines
Learn about hibernating your Linux virtual machine
...icles/virtual-machines/linux/hibernate-resume-linux.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and PowerShell examples for enabling hibernation on Linux VMs, but PowerShell examples are always present and shown alongside CLI, sometimes with more detail. In some sections, PowerShell is listed before REST or other Linux-native tools, and the use of PowerShell for Linux VM management is emphasized, which may not be the preferred or most familiar tool for Linux users. However, Linux-specific instructions (bash, package installation) are present and detailed for guest OS configuration.
Recommendations
- Prioritize Azure CLI and bash examples before PowerShell in all sections, as CLI is more platform-neutral and familiar to Linux users.
- Clearly indicate that PowerShell is optional and primarily for users who prefer it, rather than presenting it as a default or primary method.
- Add explicit bash-only examples for VM creation and management where possible, especially for steps that can be completed outside Azure CLI/PowerShell.
- Consider adding a summary table comparing CLI, PowerShell, and REST options, with recommendations for Linux users.
- Where REST API is mentioned, include curl/bash examples for Linux users.
- Remove references to 'git bash' for Ubuntu/Debian instructions, as native bash is standard.
Virtual Machines
Azure VM Image Builder networking options
...les/virtual-machines/linux/image-builder-networking.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation page presents both Windows and Linux options, but there is a subtle Windows bias. Windows examples and links are often listed before Linux equivalents, and PowerShell is given equal prominence to Azure CLI, despite CLI being more cross-platform. Some sections (e.g., permissions and checklist) consistently show PowerShell examples alongside CLI, but do not provide Bash or Linux-native alternatives. The 'IMPORTANT' note specifically addresses Windows WinRM configuration, with no equivalent Linux SSH note.
Recommendations
- List Linux/Azure CLI examples before Windows/PowerShell examples to reduce perceived Windows-first bias.
- Add Bash or Linux-native command examples where only PowerShell is shown.
- Include notes about Linux-specific configuration changes (e.g., SSH) if Windows-specific notes (WinRM) are present.
- Clarify that Azure CLI is cross-platform and preferred for Linux/macOS users.
- Ensure parity in troubleshooting and configuration notes for both OS types.