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 1-25 of 815 flagged pages
Virtual Machines Automatic Guest Patching for Azure Virtual Machines and Scale Sets ...ticles/virtual-machines/automatic-vm-guest-patching.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation page exhibits several signs of Windows bias. Windows-specific information, examples, and tooling (PowerShell, registry keys, Windows Update service) are presented more frequently and in greater detail than Linux equivalents. Windows patch orchestration modes are described first and in more depth, with Linux modes covered later and more briefly. PowerShell and CLI examples for Windows VMs are more numerous and detailed, while Linux examples are limited or missing in some sections (e.g., PowerShell usage for Linux VMs). Windows tools and concepts (registry keys, WSUS, KB IDs) are referenced without Linux analogs. The 'Next steps' section links only to Windows VM management, omitting Linux VM guidance.
Recommendations
  • Ensure Linux examples are provided for every API, CLI, and PowerShell scenario, including VM creation, update, patch assessment, and patch installation.
  • Present Linux and Windows instructions in parallel, or alternate their order to avoid Windows-first presentation.
  • Include Linux-specific tooling and concepts (e.g., package managers, configuration files) where Windows-specific tools (registry, WSUS, KB IDs) are mentioned.
  • Expand explanations of Linux patch orchestration modes to match the detail given for Windows.
  • Add 'Next steps' links for Linux VM management alongside Windows VM links.
  • Where PowerShell is used for Windows, clarify if and how PowerShell or other automation tools can be used for Linux VMs, or provide equivalent Bash/Ansible examples.
GitHub Create Pull Request
Virtual Machines Ddsv6 size series ...virtual-machines/sizes/general-purpose/ddsv6-series.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page exhibits mild Windows bias. Windows-specific tools and patterns are referenced before or exclusively (e.g., nested virtualization links to Hyper-V on Windows), and bandwidth testing references NTTTCP, a Windows-centric tool, without mentioning Linux equivalents. There are no command-line examples, but where platform-specific features are discussed, Windows is mentioned first or exclusively. Linux parity is not fully addressed in feature support or tooling guidance.
Recommendations
  • When referencing nested virtualization, include links to Linux/KVM documentation or clarify Linux support status.
  • For bandwidth/throughput testing, mention Linux tools such as iperf or provide guidance for both Windows and Linux users.
  • Where features are not supported for either platform (e.g., disk encryption), clarify the parity and provide links to both Windows and Linux documentation.
  • Review all external links and ensure Linux equivalents are present and referenced with equal prominence.
  • Consider adding example usage or optimization guidance for both Windows and Linux where relevant.
GitHub Create Pull Request
Virtual Machines Ddsv6 size series ...virtual-machines/sizes/general-purpose/ddsv6-series.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page shows mild Windows bias. It references Windows-specific technologies (e.g., Hyper-V nested virtualization, NTTTCP for bandwidth testing) and links to Windows documentation before or instead of Linux equivalents. There are no explicit Linux command-line examples, and some features/tools are described only in a Windows context. Linux support is mentioned for disk encryption, but only to note that it is not supported.
Recommendations
  • Provide Linux-specific examples and links alongside Windows ones, such as Linux nested virtualization guides and Linux bandwidth testing tools (e.g., iperf).
  • Mention Linux tools and patterns (e.g., KVM, QEMU, Linux disk/network utilities) when describing features or performance testing.
  • Ensure parity in documentation by including both Linux and Windows instructions for common VM management tasks.
  • Where features are unsupported for Linux, provide context or alternatives for Linux users.
  • Review and update resource links to include Linux documentation where available, not just Windows-centric guides.
GitHub Create Pull Request
Virtual Machines Automatic Guest Patching for Azure Virtual Machines and Scale Sets ...ticles/virtual-machines/automatic-vm-guest-patching.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits several signs of Windows bias. Windows-specific examples (PowerShell, CLI) are provided before or in greater detail than Linux equivalents, especially in sections on patch orchestration modes and enablement. PowerShell commands are only given for Windows VMs, with no Linux PowerShell examples. Windows registry keys and tools (e.g., WSUS, Windows Update service) are discussed in detail, while Linux equivalents (e.g., yum, apt, packagekit) are mentioned briefly or not at all. Some sections, such as patch orchestration modes, provide more options and explanation for Windows than Linux, and the 'Next steps' link is Windows-focused.
Recommendations
  • Provide Linux-specific PowerShell and CLI examples wherever Windows examples are given, including for enablement, assessment, and patch installation.
  • Discuss Linux patching tools and mechanisms (e.g., apt, yum, zypper, packagekit) with parity to Windows Update/WSUS, including how automatic updates are managed and disabled.
  • Ensure patch orchestration modes are explained with equal detail for Linux, including any limitations or differences.
  • Add 'Next steps' links for Linux VM management, not just Windows.
  • When listing supported images, present Linux and Windows lists with equal prominence and detail.
  • Avoid referencing Windows registry keys or tools without providing Linux configuration file or service equivalents.
  • Where possible, present examples for both OS types side-by-side, or alternate which OS is presented first.
GitHub Create Pull Request
Virtual Machines https://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/virtual-machines/automatic-vm-guest-patching.md ...ticles/virtual-machines/automatic-vm-guest-patching.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits several signs of Windows bias. Windows-specific examples (PowerShell, CLI) are provided before or in greater detail than Linux equivalents. PowerShell commands are given for Windows VMs but not for Linux VMs in some sections. Windows registry keys and Windows Update service are discussed in detail, while Linux-specific configuration and troubleshooting are less emphasized. The 'Next steps' section links only to Windows VM management, omitting Linux. Some CLI and PowerShell examples for Linux are missing or less detailed.
Recommendations
  • Provide PowerShell and CLI examples for Linux VMs wherever Windows examples are given.
  • Ensure Linux-specific configuration and troubleshooting steps are as detailed as Windows (e.g., agent requirements, disabling automatic updates).
  • Add a 'Next steps' link for Linux VM management alongside the Windows link.
  • Present Windows and Linux instructions in parallel, rather than Windows-first ordering.
  • Include Linux-specific tools and patterns (such as package managers, systemd, etc.) where relevant.
  • Review all sections for parity in depth and clarity between Windows and Linux content.
GitHub Create Pull Request
Virtual Machines https://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/virtual-machines/sizes/general-purpose/ddsv6-series.md ...virtual-machines/sizes/general-purpose/ddsv6-series.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page shows mild Windows bias. It references Windows-specific technologies (such as Hyper-V nested virtualization) and tools (NTTTCP for bandwidth testing) without mentioning Linux equivalents or alternatives. In the networking section, Windows is mentioned before Linux when discussing optimization, and only a Windows-centric tool (NTTTCP) is linked for bandwidth testing. There are no examples or instructions for either platform, but where platform-specific advice is given, Windows is prioritized or Linux is only mentioned secondarily.
Recommendations
  • When referencing bandwidth/throughput testing, include Linux-native tools (e.g., iperf, netperf) alongside NTTTCP, and provide links to their usage in Azure.
  • For nested virtualization, link to documentation for both Windows (Hyper-V) and Linux (KVM) nested virtualization, or clarify platform support.
  • When discussing optimization or performance tuning, provide parity in guidance for both Windows and Linux, and avoid listing Windows first unless there is a technical reason.
  • Where platform-specific features or restrictions are listed (e.g., disk encryption), ensure both Windows and Linux are equally described, and provide links to both sets of documentation.
GitHub Create Pull Request
Virtual Machines https://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/virtual-machines/sizes/general-purpose/ddsv6-series.md ...virtual-machines/sizes/general-purpose/ddsv6-series.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page shows mild Windows bias. It references Windows-specific technologies (such as Hyper-V for nested virtualization) and Windows tools (NTTTCP for network testing) without mentioning Linux equivalents or alternatives. In several places, Windows features are listed before Linux ones, and some links point to Windows documentation first. There are no Linux-specific command-line examples, tools, or optimization guidance, and Linux parity is not explicitly addressed.
Recommendations
  • Include Linux equivalents for referenced Windows tools (e.g., mention 'iperf' or 'nuttcp' for network testing alongside NTTTCP).
  • Provide links to Linux-specific documentation where Windows documentation is referenced (e.g., nested virtualization on KVM/QEMU).
  • Ensure Linux features and restrictions are listed before or alongside Windows ones, not after.
  • Add Linux command-line examples or optimization tips where relevant (e.g., disk performance tuning, network throughput testing).
  • Explicitly state Linux support and limitations in feature tables, not just in footnotes or restrictions.
  • Review all external links to ensure Linux documentation is equally discoverable.
GitHub Create Pull Request
Virtual Machines https://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/virtual-machines/automatic-vm-guest-patching.md ...ticles/virtual-machines/automatic-vm-guest-patching.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates several forms of Windows bias. Windows-specific examples (PowerShell, CLI) are provided before or in greater detail than Linux equivalents. PowerShell examples are given for Windows VMs but not for Linux VMs, and CLI examples for Windows VMs are more detailed. Windows registry keys and Windows Update service requirements are described explicitly, while Linux equivalents (such as disabling automatic updates) are less thoroughly explained. The 'Next steps' section links only to Windows VM management, omitting Linux VM guidance.
Recommendations
  • Provide Azure PowerShell examples for Linux VMs where applicable, or clarify PowerShell usage for Linux.
  • Ensure CLI examples for Linux VMs are as detailed as those for Windows VMs, including update and patching scenarios.
  • Mention Linux-specific tools and configuration patterns (e.g., apt, yum, zypper, systemctl) with equal prominence to Windows tools (e.g., registry keys, Windows Update).
  • Add a 'Next steps' link for Linux VM management, mirroring the Windows VM link.
  • Where requirements or behaviors differ (e.g., disabling automatic updates), provide step-by-step instructions for both Linux and Windows, not just Windows.
  • Present OS-specific information in parallel sections, or alternate the order between Windows and Linux to avoid implicit prioritization.
GitHub Create Pull Request
Virtual Machines Associate a virtual machine to a capacity reservation group .../virtual-machines/capacity-reservation-associate-vm.md
Medium Priority View Details →
Scanned: 2026-03-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
While the documentation states it applies to both Windows and Linux VMs and includes cross-platform Azure CLI and API examples, there are notable signs of Windows bias. PowerShell examples are always present, but there are no equivalent Bash or Linux shell script examples. The ARM template section defaults to Windows images and parameters, with no Linux image guidance. Windows terminology (e.g., password requirements, RDP port 3389) appears by default, and Windows is the only OS shown in ARM template allowed values. Linux is only referenced in the CLI example image parameter.
Recommendations
  • In ARM template examples, add a Linux image option (e.g., Ubuntu) and show how to parameterize for both Windows and Linux.
  • In sections referencing administrator credentials, clarify the differences for Linux VMs (e.g., SSH key vs. password).
  • In ARM template network security rules, include port 22 (SSH) for Linux, not just port 3389 (RDP).
  • Provide Bash or Linux shell script equivalents for PowerShell examples, or clarify that CLI commands are cross-platform.
  • When listing OS options or parameters, show both Windows and Linux choices.
  • Avoid defaulting to Windows terminology or requirements unless the step is truly Windows-specific.
GitHub Create Pull Request
Virtual Machines Deploy a Premium SSD v2 managed disk ...n/articles/virtual-machines/disks-deploy-premium-v2.md
Medium Priority View Details →
Scanned: 2026-03-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation provides both Azure CLI and PowerShell examples for deploying Premium SSD v2 disks, but all VM creation examples use a Windows image (Win2016Datacenter) and Windows-style admin credentials. There are no explicit Linux VM examples, and the CLI scripts do not show how to deploy or attach disks to Linux VMs. This may cause confusion or extra work for Linux users.
Recommendations
  • Add explicit Linux VM deployment examples in the Azure CLI sections (e.g., use Ubuntu or CentOS images, show SSH key authentication).
  • In CLI variable initialization, provide both Windows and Linux image options, and clarify how to set admin credentials for Linux VMs.
  • Add a note or section explaining any differences or considerations when deploying Premium SSD v2 disks to Linux VMs.
  • Ensure that the 'Next steps' links to Linux documentation are clearly visible and referenced earlier in the workflow.
GitHub Create Pull Request
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 →
Scanned: 2026-03-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation repeatedly references Windows Server Failover Cluster and links to Windows-specific clustering requirements, without mentioning Linux clustering solutions or their compatibility with Azure shared disks. The proximity placement groups section links to a Windows-specific URL, and no Linux equivalents or examples are provided. The focus on Windows clustering tools and documentation creates a Windows-first impression and omits Linux parity.
Recommendations
  • Add information about Linux-based clustering solutions (e.g., Pacemaker, Corosync) and their compatibility or limitations with Azure shared disks.
  • Provide links to Linux documentation for proximity placement groups and disk sharing scenarios.
  • Clarify whether the listed limitations apply equally to Linux VMs and clustering solutions, or specify any Linux-specific differences.
  • Include examples or references for Linux users where relevant, especially in sections discussing clustering and disk sharing.
GitHub Create Pull Request
Virtual Machines Benchmark your application on Azure Disk Storage ...lob/main/articles/virtual-machines/disks-benchmarks.md
Medium Priority View Details →
Scanned: 2026-03-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation mentions both Windows and Linux VMs are supported and introduces DiskSpd (Windows) and FIO (Linux) as benchmarking tools. However, DiskSpd (Windows) is mentioned first, and the overall tone and example setup (e.g., host caching terminology) may be more familiar to Windows users. There is no explicit Linux example or command shown, and the inclusion of PowerShell/Windows terminology is slightly more prominent.
Recommendations
  • Provide explicit Linux command examples using FIO, alongside Windows DiskSpd examples.
  • Ensure Linux terminology and disk configuration steps are equally described (e.g., how to stripe disks and set caching on Linux).
  • Alternate the order of tool presentation or clarify parity between Windows and Linux throughout.
  • Add links or references to Linux-specific documentation for disk management and benchmarking.
GitHub Create Pull Request
Virtual Machines Deploy a ZRS managed disk ...lob/main/articles/virtual-machines/disks-deploy-zrs.md
Medium Priority View Details →
Scanned: 2026-03-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for deploying ZRS managed disks, but PowerShell (a Windows-centric tool) is heavily featured, especially in the Resource Manager Template section and for feature registration. PowerShell examples are more verbose and detailed, and some critical steps (like feature registration) are only shown in PowerShell. Additionally, the Resource Manager Template examples use PowerShell for deployment, with no equivalent Bash or cross-platform scripting shown. The PowerShell examples use Windows VM images and Windows-specific parameters, while CLI examples use Ubuntu images, but the PowerShell sections are more prominent and detailed.
Recommendations
  • Add Bash or cross-platform shell examples for feature registration and Resource Manager Template deployment (e.g., using Azure CLI or ARM template deployment via CLI).
  • Provide parity in example detail for Azure CLI and PowerShell, ensuring that Linux/macOS users can follow all steps without switching to PowerShell.
  • Clearly indicate that PowerShell examples are for Windows users and provide alternative instructions for Linux/macOS users where possible.
  • Include examples for deploying Windows and Linux VMs in both CLI and PowerShell sections to avoid implicit OS bias.
GitHub Create Pull Request
Virtual Machines Ultra Disks for VMs - Azure Managed Disks ...in/articles/virtual-machines/disks-enable-ultra-ssd.md
Medium Priority View Details →
Scanned: 2026-03-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example Powershell Heavy
Summary
The documentation provides both Azure CLI and PowerShell examples for deploying and managing Ultra Disks, but all VM creation examples use Windows VM images (e.g., Win2016Datacenter) and do not show Linux equivalents. PowerShell examples are prominent, and there are no Linux-specific instructions or examples for attaching, formatting, or using Ultra Disks. This creates friction for Linux users, who must adapt Windows-centric examples to their needs.
Recommendations
  • Add Linux VM image examples (e.g., --image UbuntuLTS) alongside or in place of Windows images in Azure CLI and PowerShell commands.
  • Include Linux-specific instructions for partitioning, formatting, and mounting Ultra Disks after attachment.
  • Where PowerShell is used, provide equivalent Bash or shell scripting examples for Linux users.
  • Explicitly state that the examples apply to both Linux and Windows, and clarify any OS-specific differences.
  • In the portal instructions, link to both Linux and Windows VM creation quickstarts, not just the Windows one.
GitHub Create Pull Request
Virtual Machines Azure Write Accelerator ...es/virtual-machines/how-to-enable-write-accelerator.md
Medium Priority View Details →
Scanned: 2026-03-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation is generally cross-platform and explicitly states applicability to both Linux and Windows VMs. Most command-line instructions are provided for both Azure PowerShell (which is cross-platform but Windows-centric in usage and syntax) and Azure CLI (which is cross-platform). However, the REST API section instructs users to install 'armclient' via Chocolatey, a Windows-only package manager, and provides installation steps only for Windows (cmd.exe and PowerShell), with no mention of Linux/macOS alternatives. Additionally, PowerShell-based instructions and examples are presented before CLI examples, which may create a slight 'Windows-first' impression.
Recommendations
  • For the REST API/armclient section, provide installation instructions for Linux/macOS users, such as using .NET Core global tools, manual download, or alternative package managers (e.g., Homebrew for macOS, apt/yum for Linux), or clarify if armclient is Windows-only.
  • Where possible, present Azure CLI examples before or alongside PowerShell examples, as CLI is more universally cross-platform and familiar to Linux/macOS users.
  • Explicitly state that PowerShell Core (pwsh) is available on Linux/macOS if those examples are intended to be cross-platform.
  • Consider mentioning or linking to alternative REST API tooling (e.g., curl, Postman, or az rest) that works natively on all platforms.
  • Add a note clarifying that Chocolatey is Windows-only and provide equivalent Linux/macOS installation steps or alternatives.
GitHub 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 →
Scanned: 2026-03-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation provides both PowerShell and Azure CLI examples, but PowerShell (a Windows-centric tool) is presented first and in greater detail, with more verbose and step-by-step scripting. References to enabling customer-managed keys and double encryption in the prerequisites link to PowerShell guides before CLI or Linux-native alternatives. There is also a reference to the Windows-specific Cryptography API: Next Generation for cryptographic modules. However, Azure CLI (cross-platform) examples are present and complete, and the feature itself is not Windows-only.
Recommendations
  • Present Azure CLI examples before PowerShell, as CLI is cross-platform and more accessible to Linux/macOS users.
  • Ensure all prerequisite links include Azure CLI or REST API options, not just PowerShell and portal.
  • Reference cross-platform cryptography documentation (such as Azure Key Vault or Managed Disks general docs) rather than Windows-specific APIs.
  • Clarify that PowerShell examples can be run on Linux/macOS using Azure PowerShell Core, if applicable.
  • Add explicit notes or links for Linux/macOS users where workflows or commands may differ.
GitHub Create Pull Request
Virtual Machines Customer intent: As a cloud administrator, I want to expand virtual machine disks efficiently, so that I can manage storage capacity without downtime and ensure optimal performance in my infrastructure. ...al-machines-disks-expand-without-downtime-restrictions.md
Medium Priority View Details →
Scanned: 2026-03-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation mentions Azure PowerShell and Windows rescan functions prominently, and provides links to Windows-specific tools and procedures. While Linux is referenced, Linux-specific examples or commands are not provided directly in the text, and Windows tools are mentioned before Linux equivalents. The Azure CLI is listed, but PowerShell is emphasized, and Linux disk expansion steps are only linked, not described.
Recommendations
  • Provide explicit Linux command-line examples (e.g., using Azure CLI and Linux disk rescan commands) alongside Windows/PowerShell examples.
  • Mention Linux tools and procedures with equal prominence to Windows tools.
  • Ensure Linux disk expansion steps are described in the documentation, not just linked.
  • List Azure CLI and Linux options before or alongside PowerShell and Windows options to avoid 'windows_first' bias.
GitHub Create Pull Request
Virtual Machines Create and upload an Ubuntu Linux VHD in Azure ...rticles/virtual-machines/linux/create-upload-ubuntu.md
Medium Priority View Details →
Scanned: 2026-03-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation, while focused on Ubuntu Linux VHD creation for Azure, frequently references Windows-specific tools (Hyper-V, Convert-VHD PowerShell cmdlet) and provides Windows-centric instructions (e.g., Hyper-V Manager steps) without offering Linux-native alternatives or mentioning Linux tools first. Linux users may struggle to find equivalent guidance for creating or converting VHDs, as the documentation assumes Windows as the primary platform for virtualization and disk conversion.
Recommendations
  • Add instructions for creating and converting VHDs using Linux-native tools (e.g., qemu-img, VirtualBox, KVM).
  • Mention Linux alternatives to Hyper-V and PowerShell (such as qemu-img for disk conversion, virt-manager for VM creation).
  • Provide step-by-step examples for extracting, preparing, and converting VHDs on Linux systems, not just referencing Windows/Hyper-V.
  • Reorder sections to present Linux-native workflows first, or at least in parallel with Windows options.
  • Clarify that Hyper-V and Convert-VHD are Windows-specific, and link to Linux-focused guides where possible.
GitHub Create Pull Request
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 →
Scanned: 2026-03-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation provides a Windows-centric AzCopy example (using AzCopy.exe and Windows file paths) for uploading a VHD, but does not offer a Linux/macOS equivalent. The AzCopy command is shown only in Windows syntax, and the file path example uses Windows conventions. There is no explicit Linux/macOS AzCopy command or mention of how to run AzCopy on those platforms, despite the page targeting both Linux and Windows VMs. The rest of the CLI commands are cross-platform, but the critical upload step is Windows-biased.
Recommendations
  • Add a Linux/macOS AzCopy example, e.g., 'azcopy copy "/home/user/mydisk.vhd" "sas-URI" --blob-type PageBlob'
  • Mention that AzCopy is available for Linux/macOS and provide installation instructions or a link for those platforms.
  • Clarify file path conventions for both Windows and Linux/macOS users.
  • Consider showing both Windows and Linux/macOS AzCopy commands side-by-side for parity.
GitHub Create Pull Request
Virtual Machines Run scripts in a Linux VM in Azure using managed Run Commands ...articles/virtual-machines/linux/run-command-managed.md
Medium Priority View Details →
Scanned: 2026-03-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation is focused on running scripts in Linux VMs using Azure managed Run Commands. While the primary examples are for Linux (shell scripts), there is notable bias in the tooling and example ordering: PowerShell cmdlets (Set-AzVMRunCommand, Get-AzVMRunCommand, etc.) are heavily featured, and Windows-specific tools (PowerShell, New-AzStorageBlobSASToken) are referenced throughout. In several sections, PowerShell examples are given equal or greater prominence than Azure CLI, despite CLI being more native to Linux. REST API and ARM template examples sometimes use Windows-style scripts (e.g., Write-Host, .ps1 files) or reference Windows-specific command IDs (ipconfig), and Windows-specific notes are interspersed in Linux-focused sections. The documentation assumes familiarity with PowerShell tooling for tasks like generating SAS tokens, which may create friction for Linux users.
Recommendations
  • Provide Azure CLI examples for all tasks where PowerShell examples are given, especially for SAS token generation and blob operations.
  • Ensure that shell script examples (.sh) are used in REST API and ARM template sections, not PowerShell (.ps1), unless explicitly discussing Windows.
  • Clarify when a command or tool is Windows-only, and provide Linux alternatives or note Linux limitations.
  • Reorder examples so that Azure CLI (or Bash) is presented before PowerShell in Linux-focused documentation.
  • Add guidance for Linux-native tools (e.g., azcopy, Azure CLI) for blob SAS token generation and management.
GitHub Create Pull Request
Virtual Machines Associate a virtual machine to a capacity reservation group .../virtual-machines/capacity-reservation-associate-vm.md
Medium Priority View Details →
Scanned: 2026-03-09 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation provides both Windows and Linux coverage in the CLI and API sections, but there are notable signs of Windows bias. PowerShell examples and references are consistently present and detailed, while there is no mention of Bash or Linux-native scripting. The ARM template example is Windows-centric, with only Windows Server images and parameters. Windows-specific terminology (e.g., password complexity, RDP port 3389) appears in portal and ARM template instructions. Linux parity is present in CLI examples (e.g., Ubuntu image), but overall, Windows tools and patterns are more prominent and detailed.
Recommendations
  • Add Linux-specific ARM template examples, including imageReference for popular Linux distributions (e.g., Ubuntu, CentOS).
  • Provide Bash or shell script equivalents for PowerShell commands, or clarify that CLI commands are cross-platform.
  • In portal instructions, mention Linux-specific options (e.g., SSH authentication, Linux username requirements) alongside Windows password guidance.
  • In ARM template parameters, include Linux OS versions and adjust security rules to show SSH (port 22) as well as RDP (port 3389).
  • Balance PowerShell and CLI coverage, ensuring CLI examples are as detailed as PowerShell and clearly marked as cross-platform.
GitHub Create Pull Request
Virtual Machines Deploy a Premium SSD v2 managed disk ...n/articles/virtual-machines/disks-deploy-premium-v2.md
Medium Priority View Details →
Scanned: 2026-03-09 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation provides deployment instructions for Premium SSD v2 managed disks using Azure CLI, PowerShell, and the Azure portal. However, all CLI and PowerShell examples use Windows-centric VM images (e.g., 'Win2016Datacenter') and do not show Linux VM image values or mention Linux-specific deployment considerations. PowerShell is inherently Windows-focused, but the CLI examples could easily be adapted for Linux users. The documentation does not provide explicit Linux VM deployment examples or highlight Linux parity, despite the feature being cross-platform.
Recommendations
  • Add CLI example scripts that use a Linux VM image (e.g., 'UbuntuLTS', 'CentOS', etc.) and clarify any Linux-specific parameters or considerations.
  • Explicitly mention that the Azure CLI commands work on Linux, macOS, and Windows, and provide sample shell syntax for Bash (e.g., export variables instead of using $var assignments).
  • In the PowerShell section, note that PowerShell Core is cross-platform, but most Linux users will use Azure CLI.
  • In the 'Next steps' section, link to Linux-specific disk attachment documentation more prominently and clarify Linux support.
  • Consider alternating the order of examples (show Linux/CLI first, then Windows/PowerShell) or provide parallel examples for both OS types.
GitHub Create Pull Request
Virtual Machines Deploy a ZRS managed disk ...lob/main/articles/virtual-machines/disks-deploy-zrs.md
Medium Priority View Details →
Scanned: 2026-03-09 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation provides parity between Azure CLI (Linux/macOS-friendly) and Azure PowerShell (Windows-centric) examples for deploying ZRS managed disks. However, PowerShell and Windows-centric tools are heavily featured, especially in the Resource Manager Template section, where PowerShell is used for deployment commands. Windows/PowerShell examples are shown before Linux equivalents in some sections, and the 'Next steps' link points to a PowerShell-focused sample repository. There are no Linux-specific shell examples for ARM template deployment (e.g., Bash with az CLI), and PowerShell is used for feature registration and template deployment, which may create friction for Linux/macOS users.
Recommendations
  • Add Bash/az CLI examples for ARM template deployment and feature registration, so Linux/macOS users can follow without PowerShell.
  • Provide explicit instructions or links for Linux/macOS users on how to perform feature registration and template deployment using Azure CLI.
  • Ensure that CLI examples are presented before or alongside PowerShell examples to avoid Windows-first bias.
  • Include links to cross-platform sample repositories, not just PowerShell-centric ones.
GitHub Create Pull Request
Virtual Machines Ultra Disks for VMs - Azure Managed Disks ...in/articles/virtual-machines/disks-enable-ultra-ssd.md
Medium Priority View Details →
Scanned: 2026-03-09 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation is intended for both Linux and Windows VMs, but consistently uses Windows VM images (e.g., Win2016Datacenter) in all CLI and PowerShell examples. There are no Linux VM image examples (such as Ubuntu, CentOS, etc.), nor any Linux-specific guidance for disk partitioning or formatting. The Quickstart link in the Portal section points only to Windows VM creation. This creates friction for Linux users, who must adapt the examples themselves.
Recommendations
  • Provide Linux VM image examples (e.g., Ubuntu, CentOS) alongside Windows examples in CLI and PowerShell sections.
  • Add links to Linux VM Quickstart documentation in the Portal section.
  • Include Linux-specific guidance for partitioning and formatting Ultra Disks after attachment.
  • Ensure that all sample scripts and commands are presented for both Windows and Linux VM scenarios, or clarify how to adapt them for Linux.
  • When referencing VM creation, mention both Windows and Linux options equally.
GitHub Create Pull Request
Virtual Machines Azure Write Accelerator ...es/virtual-machines/how-to-enable-write-accelerator.md
Medium Priority View Details →
Scanned: 2026-03-09 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation provides extensive Azure PowerShell examples and scripts, which are primarily Windows-centric. The REST API section recommends installing 'armclient' via Chocolatey, a Windows-only package manager, and gives installation instructions using cmd.exe and PowerShell. Windows tools and patterns are mentioned before Linux equivalents, and there are no explicit Linux shell (bash) or macOS instructions for REST API tooling. However, Azure CLI examples are included, which are cross-platform, and the feature itself is not Windows-only.
Recommendations
  • Add bash/Linux/macOS instructions for installing REST API tooling (e.g., armclient or alternatives), or clarify cross-platform options.
  • Provide example scripts using Azure CLI for all scenarios currently covered by PowerShell, ensuring parity for Linux/macOS users.
  • Mention cross-platform alternatives to Chocolatey (such as Homebrew for macOS, apt/yum for Linux) when describing tool installation.
  • Where PowerShell is used, clarify that Azure CLI is fully supported and provide equivalent CLI examples.
  • Reorder sections so that cross-platform tools (Azure CLI) are presented before Windows-specific tools (PowerShell).
GitHub Create Pull Request
← Previous Page 1 of 33 Next →