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 501-525 of 818 flagged pages
Virtual Machines VM vCore Customization ...lob/main/articles/virtual-machines/vm-customization.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation provides both Azure CLI and PowerShell examples for configuring VM vCore customization, but the PowerShell example is more detailed and uses SDK objects directly. The CLI example uses Ubuntu as the image, but there are no Linux-specific configuration or verification steps shown. Windows/PowerShell tooling is given equal or greater prominence, and there are no bash or Linux-native command examples for post-deployment verification. The ARM template section is neutral, but overall, Windows/PowerShell patterns are slightly favored.
Recommendations
  • Add Linux-specific verification steps (e.g., how to check vCPU count and SMT status in Linux using lscpu or /proc/cpuinfo).
  • Provide bash or shell script examples for VM creation and configuration, not just Azure CLI.
  • Ensure parity in detail between PowerShell and CLI examples (e.g., show how to use CLI to set advanced properties, not just basic flags).
  • Explicitly mention how Linux users can perform equivalent post-deployment checks and troubleshooting.
  • Consider listing CLI (cross-platform) examples before PowerShell (Windows-centric) examples.
GitHub Create Pull Request
Virtual Machines VM watch Collectors Suite .../articles/virtual-machines/vm-watch-collector-suite.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page for VM watch Collectors Suite demonstrates a moderate Windows bias. Several collectors (e.g., system_error, hardware_health_monitor) are described as Windows-only, with explicit references to Windows EventLog and tools like w32tm. The default NTP server is time.windows.com, and fallback logic is described only for Windows. Linux equivalents (such as syslog, journalctl, or chrony/ntpd for time sync) are not mentioned, and some collectors are eligible only on Windows machines. In collector descriptions, Windows tools and patterns are referenced before Linux, and Linux-specific details are sparse or missing.
Recommendations
  • Add Linux/macOS equivalents for collectors that currently reference Windows-only tools (e.g., mention syslog/journalctl for system errors, chrony/ntpd for clock skew).
  • Provide explicit eligibility and behavior descriptions for Linux/macOS where currently only Windows is described.
  • Include Linux/macOS examples and tool references alongside or before Windows examples where applicable.
  • Clarify which collectors are cross-platform and which are platform-specific, and provide guidance or alternatives for Linux/macOS users.
  • Consider using neutral or cross-platform defaults (e.g., pool.ntp.org for NTP) instead of Windows-centric ones.
GitHub Create Pull Request
Virtual Machines Set up Oracle ASM on an Azure Linux virtual machine | Microsoft Docs ...tual-machines/workloads/oracle/configure-oracle-asm.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation is generally Linux-focused, as the main Oracle ASM setup is on a Linux VM. However, there is notable Windows bias in the setup of the X Server VM, which is exclusively described as a Windows 10 workstation using Xming, with no mention of Linux or macOS alternatives. The instructions for tunneling and file transfer use PowerShell and Windows-centric patterns first, and do not provide equivalent Linux/macOS shell examples. The documentation assumes the user's workstation is Windows for critical steps, which may create friction for Linux/macOS users.
Recommendations
  • Provide instructions for setting up X Server on Linux (e.g., using Xorg or X11) and macOS (e.g., XQuartz), including installation and launch steps.
  • Include Linux/macOS shell equivalents for all PowerShell commands, especially for Azure Bastion tunneling and SCP file transfer.
  • Mention cross-platform SSH and SCP usage, and clarify how Linux/macOS users can perform all steps without a Windows VM.
  • List X Server options for all major platforms and provide links to their documentation.
  • Reorder examples so that Linux/macOS options are presented alongside or before Windows-specific instructions, where appropriate.
GitHub Create Pull Request
Virtual Machines Connect Azure ExpressRoute with Oracle Cloud Infrastructure | Microsoft Docs ...nes/workloads/oracle/configure-azure-oci-networking.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. While the topic is cross-cloud and the audience includes Linux users (as indicated by the 'Applies to: Linux VMs' tag), most step-by-step instructions focus on Azure Portal GUI actions and PowerShell commands, with no equivalent CLI or Linux-native examples. References to automation mention Terraform and Azure CLI, but when describing manual configuration, only PowerShell is cited for advanced tasks (e.g., configuring ExpressRoute FastPath). There are no explicit Linux shell or Azure CLI command examples, and the order of presentation favors Windows-centric tools and workflows.
Recommendations
  • Add Azure CLI command examples alongside PowerShell for all configuration steps, especially for ExpressRoute FastPath and virtual network gateway setup.
  • Explicitly mention and provide Linux shell (bash) equivalents for verification steps, such as querying ARP records and route tables.
  • Ensure that automation and scripting sections include instructions for authenticating and running Terraform from Linux environments.
  • Where screenshots or UI instructions are given, clarify that these steps are platform-agnostic or provide CLI alternatives for headless/Linux users.
GitHub Create Pull Request
Virtual Machines Implement Oracle Golden Gate on an Azure Linux VM | Microsoft Docs ...hines/workloads/oracle/configure-oracle-golden-gate.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
Although the documentation is for deploying Oracle Golden Gate on Azure Linux VMs, there is notable Windows bias in the setup of the X Server component. The guide mandates the creation of a Windows VM (ggXServer) specifically to run Xming X Server for graphical installation, with detailed Windows instructions and screenshots. No equivalent Linux or macOS X Server setup is described. Additionally, PowerShell commands are used for Bastion tunneling and file transfer, with no Bash or Linux-native alternatives provided. The documentation assumes the user's local environment is Windows for critical steps, creating friction for Linux/macOS users.
Recommendations
  • Provide instructions for setting up an X Server on Linux (e.g., using Xorg, X11 forwarding via SSH, or XQuartz on macOS) as an alternative to the Windows Xming VM.
  • Include Bash-based examples for Bastion tunneling and SCP file transfer, not just PowerShell.
  • Add guidance for performing graphical Oracle installer steps from a Linux or macOS desktop, or document how to use SSH X11 forwarding from those platforms.
  • Present cross-platform options for all steps that currently assume Windows, and avoid Windows-first ordering in critical sections.
  • Where screenshots are used, provide Linux/macOS equivalents or clarify platform differences.
GitHub Create Pull Request
Virtual Machines Red Hat Enterprise Linux bring-your-own-subscription Azure images | Microsoft Docs ...ain/articles/virtual-machines/workloads/redhat/byos.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation provides both Azure CLI (cross-platform) and PowerShell examples for provisioning Red Hat Enterprise Linux BYOS images on Azure. However, the PowerShell section is notably more detailed, including full scripts for networking and VM setup, while the CLI section is more basic. Windows-specific tools (PowerShell, Az PowerShell modules) are featured, and the PowerShell example appears after the CLI but is more comprehensive, potentially implying a Windows-centric workflow. There are no Linux/macOS-specific automation examples (e.g., Bash scripts, cloud-init, Terraform, Ansible), and the CLI instructions do not cover advanced scenarios shown in PowerShell.
Recommendations
  • Expand the Azure CLI section to include full end-to-end deployment scripts, matching the detail of the PowerShell example (networking, SSH keys, etc.).
  • Add Linux/macOS-specific automation examples, such as Bash scripts, cloud-init, or Ansible playbooks for VM provisioning.
  • Include guidance for using cross-platform tools (e.g., Terraform, Ansible) with explicit Linux/macOS usage instructions.
  • Clarify that PowerShell is primarily a Windows tool and offer alternatives for Linux/macOS users.
  • Ensure parity in example depth and complexity between CLI and PowerShell sections.
GitHub Create Pull Request
Virtual Machines Deploy Ephemeral OS disks ...articles/virtual-machines/ephemeral-os-disks-deploy.md
Medium 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 provides both platform-neutral (ARM template, REST, Azure CLI) and Windows-specific (PowerShell) instructions, but there is a noticeable Windows bias. PowerShell examples are given their own section, with no equivalent for Linux shell scripting. VM template examples use Windows images and passwords, and admin credentials are Windows-style. Windows tools and patterns (PowerShell, Windows image references) are mentioned exclusively or before Linux equivalents, and Linux-specific examples (e.g., Bash scripting, Linux image references) are missing.
Recommendations
  • Add explicit Linux shell (Bash) scripting examples for deploying ephemeral OS disks, especially for tasks currently only shown in PowerShell.
  • In ARM template examples, provide both Windows and Linux image references, and use platform-neutral admin credential patterns (e.g., SSH keys for Linux).
  • In CLI examples, clarify Linux-specific options (e.g., --generate-ssh-keys) and show full Linux VM deployment flows.
  • Where PowerShell is mentioned, also mention Bash/Cloud Shell alternatives for Linux/macOS users.
  • Ensure screenshots and UI instructions are not Windows-centric.
GitHub Create Pull Request
Virtual Machines FAQ Ephemeral OS disks ...in/articles/virtual-machines/ephemeral-os-disks-faq.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides a detailed PowerShell script as the only example for determining VM size support for ephemeral OS disks, with no equivalent CLI, Bash, or Linux-native example. Windows/PowerShell tooling is mentioned first and exclusively in the example, creating friction for Linux/macOS users who may prefer or require Azure CLI or Bash scripts.
Recommendations
  • Add equivalent Azure CLI and Bash examples for checking VM size support for ephemeral OS disks.
  • Present both PowerShell and CLI/Bash examples side-by-side, or alternate which is shown first.
  • Explicitly mention Linux/macOS compatibility and provide guidance for non-Windows users.
  • Clarify which tools are cross-platform and which are Windows-specific.
GitHub Create Pull Request
Virtual Machines Share an Azure managed disk across VMs ...cs/blob/main/articles/virtual-machines/disks-shared.md
Medium Priority View Details →
Scanned: 2026-01-10 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 demonstrates a moderate Windows bias. Windows clustering tools (WSFC) and workloads are described first and in greater detail, with explicit references to Windows-specific features (CSV, Scale-Out File Server, RDS UPD). Windows sample workloads are more numerous and detailed, including links to templates and migration guides. Linux equivalents (Pacemaker, Corosync, ocfs2/gfs2) are mentioned, but with less detail and fewer concrete examples or step-by-step guides. No Linux command-line or configuration examples are provided, while Windows receives more actionable guidance. The examples section also leads with Windows scenarios before Linux.
Recommendations
  • Provide Linux-specific step-by-step configuration examples, including commands for Pacemaker, Corosync, and SCSI PR utilities (e.g., sg_persist, fence_scsi).
  • Add parity in sample workloads for Linux, such as NFS server clustering, SAP on Linux, and general file server HA setups.
  • Include links to Linux templates, guides, or walkthroughs similar to those provided for Windows.
  • Present Linux and Windows sections in parallel, or alternate which platform is described first.
  • Expand on Linux-specific limitations, best practices, and troubleshooting tips.
GitHub Create Pull Request
Virtual Machines What's new in Azure Disk Storage ...blob/main/articles/virtual-machines/disks-whats-new.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page is primarily a changelog and summary of new features for Azure Disk Storage, but there are several instances of Windows bias. Windows documentation links are sometimes listed before Linux equivalents, and some feature references point only to Windows-specific documentation or tools (such as PowerShell). In a few cases, Linux examples or documentation are missing or less visible, which may create friction for Linux/macOS users.
Recommendations
  • Ensure all feature documentation links include both Windows and Linux/macOS examples and guides.
  • When referencing documentation, list Linux and Windows links together, or alternate which is listed first.
  • Avoid referencing Windows-specific tools (e.g., PowerShell) without mentioning or linking to equivalent Linux/macOS tools (e.g., Azure CLI, Bash scripts).
  • Audit linked articles to confirm Linux parity in examples and instructions.
  • Add explicit notes or sections for Linux/macOS users where workflows differ.
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-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. The primary upload example uses 'AzCopy.exe' with a Windows-style path (c:\somewhere\mydisk.vhd), and does not provide a Linux/macOS equivalent (e.g., 'azcopy' or './azcopy' with POSIX paths). The mention of preparing VHDs links to a Windows-specific guide, with no Linux preparation guidance. While most Azure CLI examples are cross-platform, the AzCopy usage and file path conventions are Windows-centric, and Linux usage is not explicitly shown.
Recommendations
  • Provide AzCopy example commands for Linux/macOS, using POSIX-style paths (e.g., '/home/user/mydisk.vhd') and the appropriate binary name ('azcopy' or './azcopy').
  • Add a link or section for preparing VHDs on Linux, not just Windows.
  • Explicitly mention that AzCopy is available for Linux/macOS and provide installation instructions or a reference.
  • Where file paths are shown, include both Windows and Linux/macOS variants, or use generic placeholders.
  • Clarify that all Azure CLI commands work on Linux/macOS, and highlight any OS-specific caveats if present.
GitHub Create Pull Request
Virtual Machines How to Connect to the Azure Image Builder build VM ...al-machines/linux/image-builder-connect-to-build-vm.md
Medium Priority View Details →
Scanned: 2026-01-10 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 exhibits moderate Windows bias. Windows terminology (RDP, WinRM) is frequently mentioned, sometimes before or instead of Linux equivalents (SSH). Examples and links for Windows are often listed first or exclusively, especially in Azure Bastion and Serial Console sections. The password reset instructions reference the Azure portal's 'Reset Password' blade, which is primarily relevant for Windows VMs. Linux-specific connection patterns and troubleshooting steps are less detailed or referenced secondarily.
Recommendations
  • Provide explicit Linux SSH examples and command-line instructions alongside Windows RDP/WinRM steps.
  • Ensure Linux connection documentation links are presented before or equally with Windows links.
  • Clarify which steps (e.g., password reset) apply to Linux VMs and provide Linux-specific guidance (such as SSH key management).
  • Avoid using Windows-centric terminology as the default (e.g., mention SSH before RDP/WinRM when discussing connection methods).
  • Include troubleshooting tips for Linux users, such as handling SSH connectivity issues or configuring Linux firewalls.
GitHub Create Pull Request
Virtual Machines Verify encryption status for Linux - Azure Disk Encryption ...tual-machines/linux/how-to-verify-encryption-status.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
Although the documentation is targeted at Linux VMs and includes Linux OS-level commands, it presents PowerShell examples before Azure CLI and Linux-native commands. The PowerShell section is extensive, with multiple detailed examples, while Linux-native commands (bash, lsblk, cryptsetup) are only covered at the end and in less detail. This ordering and emphasis may create friction for Linux users who are less familiar with PowerShell or prefer Linux-native tooling.
Recommendations
  • Present Azure CLI and Linux-native commands before PowerShell examples, as these are more commonly used by Linux administrators.
  • Expand the Linux OS-level section to include more detailed examples, such as checking encryption status for multiple disks, scripting checks, and interpreting output.
  • Clarify that PowerShell examples are optional and primarily for users who manage Azure resources from Windows or cross-platform PowerShell.
  • Add a summary table comparing methods (Portal, PowerShell, Azure CLI, Linux OS) with pros/cons for Linux users.
  • Ensure parity in depth and detail between PowerShell and CLI/Linux-native sections.
GitHub Create Pull Request
Virtual Machines Ev3-series and Esv3-series ...blob/main/articles/virtual-machines/ev3-esv3-series.md
Medium Priority View Details →
Scanned: 2026-01-09 19:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation page exhibits mild Windows bias. While it states applicability to both Linux and Windows VMs, the only external tool or feature referenced by OS is 'Nested Virtualization', which links to a Windows/Hyper-V specific guide. No Linux equivalents or examples are provided for nested virtualization or other features. Windows tools and patterns are mentioned exclusively or first where OS-specific features are discussed.
Recommendations
  • Provide Linux-specific guidance or examples for features like Nested Virtualization (e.g., KVM/QEMU).
  • Where OS-specific documentation is referenced, include links to both Windows and Linux guides.
  • Add explicit Linux usage notes or examples for features that differ between OSes.
  • Review all feature links to ensure Linux parity and avoid Windows-first presentation.
GitHub Create Pull Request
Virtual Machines Azure Disk Encryption for Linux ...es/virtual-machines/extensions/azure-disk-enc-linux.md
Medium Priority View Details →
Scanned: 2026-01-09 19:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation is focused on Azure Disk Encryption for Linux and generally maintains Linux-centric content. However, in the warning section about checking encryption progress, the PowerShell cmdlet (Get-AzVMDiskEncryptionStatus) is mentioned first, with the Azure CLI command referenced second. This ordering and inclusion of PowerShell (a Windows-centric tool) in a Linux-focused guide introduces a subtle Windows-first and Windows-tools bias.
Recommendations
  • List the Azure CLI command before the PowerShell cmdlet when describing how to check encryption status, as CLI is more commonly used on Linux.
  • Provide explicit Linux shell command examples (e.g., az vm encryption show) with sample output to improve clarity for Linux users.
  • Consider omitting PowerShell references or moving them to a separate section for cross-platform users, focusing the main instructions on Linux-native tools.
  • Ensure all troubleshooting and operational examples use Linux-native commands and patterns unless the context specifically requires cross-platform coverage.
GitHub Create Pull Request
Virtual Machines Best practices for virtual machine cost optimization ...s/virtual-machines/cost-optimization-best-practices.md
Medium Priority View Details →
Scanned: 2026-01-09 19:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page shows mild Windows bias. In the best practices section, recommendations for B-Series VM sizing specify 'at least B2 for Windows machines' but do not mention Linux equivalents or considerations. The cost-saving licensing benefit (Azure Hybrid Benefit) is discussed only for Windows Server, with no mention of Linux licensing or cost-saving features. Examples and recommendations are generally Windows-centric, with Linux mentioned only in pricing links and a next-steps link to Linux VM creation, but not in the main body of cost optimization advice.
Recommendations
  • Include equivalent recommendations for Linux VMs, such as optimal B-Series sizing for Linux workloads.
  • Discuss any Linux-specific cost optimization features, such as reserved instance savings, open-source licensing advantages, or relevant Azure Hybrid Benefit for Linux (if applicable).
  • When mentioning licensing benefits, clarify differences for Linux and Windows, and link to Linux cost-saving documentation where appropriate.
  • Ensure examples and advice are balanced between Windows and Linux, especially in sections on automation, disk selection, and policy enforcement.
GitHub Create Pull Request
Virtual Machines Increase performance of Premium SSDs and Standard SSD/HDDs .../articles/virtual-machines/disks-enable-performance.md
Medium Priority View Details →
Scanned: 2026-01-09 19:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI (cross-platform) and Azure PowerShell (Windows-centric) examples, but the PowerShell section is given equal prominence and detail, which can be interpreted as Windows bias. There are no explicit Linux shell (bash) or platform-specific examples, but the CLI examples use bash syntax, which is cross-platform. However, the documentation does not mention Linux-specific considerations, nor does it provide parity for Linux-native scripting or tools. The PowerShell examples may be less relevant for Linux users, and the documentation does not clarify platform differences or recommend best practices for Linux environments.
Recommendations
  • Add explicit bash examples and clarify that Azure CLI commands work natively on Linux, macOS, and Windows.
  • Include notes on platform compatibility, such as differences in environment variable syntax (e.g., export vs. $env:), file paths, and shell behaviors.
  • If PowerShell is mentioned, clarify that PowerShell Core is available on Linux and macOS, and provide guidance for Linux users who may prefer bash.
  • Add troubleshooting or tips specific to Linux environments (e.g., permissions, common errors, package installation).
  • Ensure that Linux users are not required to use Windows-centric tools or patterns, and highlight cross-platform approaches where possible.
GitHub Create Pull Request
Virtual Machines Use Azure Storage Explorer to manage Azure managed disks ...l-machines/disks-use-storage-explorer-managed-disks.md
Medium Priority View Details →
Scanned: 2026-01-09 19:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page describes using Azure Storage Explorer, a cross-platform GUI tool, to manage Azure managed disks. While the main instructions are platform-neutral, the 'Next steps' section exclusively links to Windows VM scenarios, such as creating a VM from a VHD and attaching a managed disk to a Windows VM, with no equivalent Linux VM guidance. There are no Linux-specific examples or follow-up links, which may lead Linux users to feel underserved.
Recommendations
  • Add 'Next steps' links for Linux VM scenarios, such as creating a VM from a VHD for Linux and attaching a managed disk to a Linux VM.
  • Ensure parity in example coverage by including Linux-specific instructions or references where relevant.
  • Review other related documentation to ensure both Windows and Linux users have clear, direct guidance for common disk management tasks.
GitHub Create Pull Request
Virtual Machines Chef extension for Azure VMs ...blob/main/articles/virtual-machines/extensions/chef.md
Medium Priority View Details →
Scanned: 2026-01-09 19:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation generally maintains parity between Linux and Windows, but there is subtle Windows bias. The extension publisher is named 'Chef.Bootstrap.WindowsAzure', which is Windows-centric. In the extension schema, the Windows type ('ChefClient') is listed before the Linux type ('LinuxChefClient'). The logging paths and troubleshooting sections mention both platforms, but the Windows path is given in Powershell syntax and the Linux path in bash, with no further Linux troubleshooting commands or examples. The Azure CLI deployment example only shows Linux ('LinuxChefClient') and omits a Windows example. The documentation references Windows tools and patterns (e.g., publisher naming, resource types) before Linux equivalents.
Recommendations
  • Provide explicit Windows deployment examples alongside Linux examples in CLI sections.
  • Clarify that the publisher name is historical and applies to both platforms.
  • List Linux and Windows extension types in parallel, or alternate the order to avoid Windows-first bias.
  • Include Linux-specific troubleshooting commands (e.g., 'cat' or 'tail' for log files) as well as Windows equivalents (e.g., 'Get-Content').
  • Ensure that documentation sections do not default to Windows terminology or patterns unless necessary.
GitHub Create Pull Request
Virtual Machines Qualys Cloud Agent Extension for Azure VMs ...ob/main/articles/virtual-machines/extensions/qualys.md
Medium Priority View Details →
Scanned: 2026-01-09 19:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page generally presents Windows examples and tools before Linux equivalents, especially in the 'Golden Machine Image' and 'Azure Deployment Policy' sections, where Windows links are listed before Linux links. The 'Deploy Cloud Agent via PowerShell' section emphasizes PowerShell as a cross-platform tool, but PowerShell is natively a Windows-centric technology, and Linux users may prefer bash or shell script examples. There are no explicit Linux tool examples (e.g., bash, cloud-init) provided, and the documentation does not offer Linux-first or Linux-native patterns.
Recommendations
  • Alternate the order of Windows and Linux examples/links to avoid consistently listing Windows first.
  • Provide Linux-native command-line examples (e.g., bash, cloud-init) alongside or instead of PowerShell for Linux deployments.
  • Explicitly mention Linux-specific tools and patterns where relevant, such as using shell scripts or cloud-init for automation.
  • Ensure parity in detail and clarity between Windows and Linux sections, including troubleshooting and advanced configuration guidance.
  • Review and update headings and content to avoid implicit prioritization of Windows tools and workflows.
GitHub Create Pull Request
Virtual Machines Project Flash - Advancing Azure Virtual Machine availability monitoring .../blob/main/articles/virtual-machines/flash-overview.md
Medium Priority View Details →
Scanned: 2026-01-09 19:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page exhibits subtle Windows bias, primarily through the use of Windows-centric links and examples. For instance, the reference to scheduled events points to a Windows-specific documentation page ('../virtual-machines/windows/scheduled-event-service.md'), and activity log instructions default to PowerShell tabs. There are no explicit Linux examples, nor are Linux-specific tools or patterns mentioned, which may leave Linux users without clear guidance.
Recommendations
  • Include parallel Linux documentation links (e.g., '../virtual-machines/linux/scheduled-event-service.md') wherever Windows links are referenced.
  • Provide Linux CLI examples (such as Azure CLI or Bash) alongside PowerShell examples in all code samples and instructions.
  • Mention Linux-specific monitoring considerations or tools if they differ from Windows, ensuring parity in troubleshooting and observability guidance.
  • Review referenced tabs and ensure that Linux/Bash/CLI options are presented before or alongside PowerShell, not exclusively or first.
GitHub Create Pull Request
Virtual Machines HBv3-series virtual machine (VM) overview, architecture, topology - Azure Virtual Machines | Microsoft Docs ...main/articles/virtual-machines/hbv3-series-overview.md
Medium Priority View Details →
Scanned: 2026-01-09 19:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page provides a balanced technical overview of HBv3-series VMs, but there is evidence of Windows bias in the 'Recommended OS for Performance' row, which lists Windows Server 2019+ before any Linux recommendation. Additionally, while Linux is referenced (e.g., lstopo output, supported OSes), there are no explicit Linux performance recommendations or examples for Linux-specific tuning, and the only OS recommendation for performance is Windows. The page also includes a note about unsupported Windows versions, but does not provide equivalent Linux caveats or guidance.
Recommendations
  • Add explicit Linux performance recommendations alongside Windows Server 2019+, e.g., 'Recommended OS for Performance: Windows Server 2019+, RHEL 8+, Ubuntu 20.04+'.
  • Provide Linux-specific tuning guidance or references, such as kernel parameters or NUMA optimization tips.
  • Include Linux caveats or notes similar to the Windows Server 2012 R2 support note, e.g., minimum kernel versions for high core counts.
  • Ensure that examples and recommendations are presented in parallel for both Windows and Linux, rather than listing Windows first.
GitHub Create Pull Request
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
Medium Priority View Details →
Scanned: 2026-01-09 19:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation introduces Windows tooling (DISKSPD) first, with detailed command examples and parameter explanations, before mentioning the Linux equivalent (FIO). The Windows tool is described in greater detail and appears to be the default or primary recommendation, while the Linux tool is introduced later and with less context. There is a clear ordering preference for Windows tools and patterns, and the Windows example is more prominent.
Recommendations
  • Present Linux and Windows benchmarking tools in parallel, giving equal prominence to both.
  • Provide equivalent parameter explanations and example commands for FIO as are given for DISKSPD.
  • Consider starting with a cross-platform introduction, then split into Windows and Linux sections.
  • Include notes on tool availability and installation for both platforms at the start.
  • Ensure images and sample outputs are balanced between Windows and Linux examples.
GitHub Create Pull Request
Virtual Machines What's New in Azure VM Image Builder ...ual-machines/image-builder-api-update-release-notes.md
Medium Priority View Details →
Scanned: 2026-01-09 19:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides examples for HTTP, Azure CLI, and Azure PowerShell, with PowerShell (Windows) examples given equal prominence to CLI and HTTP. There is a slight Windows-first bias in the ordering and explicit mention of PowerShell, while Linux-specific tools (such as Bash scripts or shell commands) are not shown in the main example tabs. Additionally, some features and improvements are described with Windows-specific terminology (e.g., PowerShell, Windows Update, Windows restart) before or alongside Linux equivalents, but Linux features are generally present. There are no outright missing Linux examples, but the documentation could do more to highlight Linux parity and provide Linux-first or Linux-specific usage patterns.
Recommendations
  • Add explicit Bash or shell script examples alongside PowerShell in code tabs, especially for Linux users.
  • When listing features or improvements, alternate or balance the order between Windows and Linux terminology, or group them by OS for clarity.
  • Provide Linux-specific troubleshooting examples and error messages where relevant.
  • Ensure that Linux tools and patterns (e.g., cloud-init, shell scripting) are mentioned with equal prominence as Windows tools.
  • Consider adding a section or callout for Linux users summarizing best practices and common patterns for VM Image Builder on Linux.
GitHub Create Pull Request
Virtual Machines Customer intent: As a cloud administrator, I want to understand the limitations and requirements of using customer-managed keys for disk encryption, so that I can ensure compliance and optimize the management of storage solutions in my Azure environment. ...hines-managed-disks-customer-managed-keys-restrictions.md
Medium Priority View Details →
Scanned: 2026-01-09 19:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation mentions both Azure CLI and Azure PowerShell as tools for copying managed disks, but it lists the Azure CLI (typically used on Linux/macOS) after referencing the Azure PowerShell module (primarily used on Windows). The example links provided are platform-specific, with the PowerShell (Windows) link appearing to be more prominent. There are no explicit Linux shell or bash examples, and the documentation does not mention Linux-specific tools or workflows beyond the Azure CLI.
Recommendations
  • Present Azure CLI (cross-platform) examples before or alongside PowerShell examples to avoid implying Windows is the primary platform.
  • Include explicit bash or Linux shell command examples where relevant.
  • Ensure documentation links for both Linux and Windows are equally prominent and accessible.
  • Add a note clarifying that Azure CLI is available on all major platforms, and provide guidance for Linux/macOS users.
  • Review other sections for similar patterns and ensure Linux parity throughout.
GitHub Create Pull Request
← Previous Page 21 of 33 Next →