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 201-225 of 818 flagged pages
Virtual Machines SCSI to NVMe for Linux VMs ...docs/blob/main/articles/virtual-machines/nvme-linux.md
Medium Priority View Details →
Scanned: 2026-01-14 01:31
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page for converting SCSI to NVMe for Linux VMs on Azure exhibits a notable Windows bias. Most operational steps, examples, and scripts are presented using PowerShell, a Windows-centric tool, even though the target VMs are running Linux. Instructions for downloading and running the migration script are given exclusively in PowerShell, and PowerShell commands are shown before any Linux-native alternatives. There is minimal coverage of Linux-native CLI workflows for Azure management, and no Bash/Azure CLI script examples are provided for the migration process itself.
Recommendations
  • Provide equivalent Bash/Azure CLI examples for all PowerShell commands, especially for checking VM controller type, downloading scripts, and running migration steps.
  • Document how to run the migration script natively on Linux (e.g., via Azure CLI, Bash, or Python), including prerequisites and environment setup.
  • Clarify whether the migration script can be executed directly from Linux environments (local or Cloud Shell) and provide instructions for doing so.
  • Reorder examples so that Linux-native tools (Azure CLI, Bash) are presented first or alongside PowerShell.
  • Add troubleshooting steps and verification commands using Linux tools (e.g., systemctl, journalctl, dmesg) in addition to PowerShell/Azure Portal.
GitHub Create Pull Request
Virtual Machines Overview of virtual machines in Azure ...e-docs/blob/main/articles/virtual-machines/overview.md
Medium Priority View Details →
Scanned: 2026-01-14 01:31
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page generally aims for cross-platform coverage, but there are several instances of Windows bias. PowerShell is frequently mentioned and often listed before Azure CLI, which is more commonly used on Linux/macOS. Windows tools and terminology (e.g., PowerShell cmdlets) are referenced in tables and examples, sometimes before or without equivalent Linux commands. Some sections provide only Windows-centric instructions or examples, and the order of presentation often favors Windows tools first, creating friction for Linux/macOS users.
Recommendations
  • Ensure that Azure CLI examples are presented before or alongside PowerShell examples, as CLI is cross-platform.
  • Provide explicit Linux/macOS command examples where only PowerShell is shown.
  • Balance tables and lists to show both Windows and Linux tools, or clarify which tools are recommended for each OS.
  • Add more Linux-specific management and troubleshooting examples, especially in sections where only Windows tools are referenced.
  • Review ordering of examples and instructions to avoid consistently listing Windows tools first.
GitHub Create Pull Request
Virtual Machines Tutorial - Move Azure single instance Virtual Machines from regional to zonal availability zones ...achines/move-virtual-machines-regional-zonal-portal.md
Medium Priority View Details →
Scanned: 2026-01-14 01:31
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing Windows-specific documentation (e.g., PowerShell) for checking VM SKU availability and for next steps, without mentioning or providing equivalent Linux/macOS CLI examples or guidance. The 'Next steps' section links only to a PowerShell/CLI page, but the main tutorial does not show any command-line steps, and the only explicit example for checking VM SKU availability links to a Windows/PowerShell page. There are no Linux/macOS-specific instructions, nor is the Azure CLI (cross-platform) given equal prominence.
Recommendations
  • Include explicit Azure CLI examples and links for all steps where PowerShell is referenced, especially for checking VM SKU availability and performing the move.
  • In the prerequisites and next steps, mention both PowerShell and Azure CLI (with links to respective documentation) to ensure parity for Linux/macOS users.
  • If screenshots or UI steps differ between platforms, clarify any differences or provide platform-agnostic instructions.
  • Avoid referencing Windows/PowerShell documentation exclusively; always provide cross-platform alternatives.
GitHub Create Pull Request
Virtual Machines Customer intent: "As an IT administrator managing Azure IaaS virtual machines, I want to implement a backup and disaster recovery plan for unmanaged disks, so that I can ensure data durability and high availability in the event of localized or regional failures." ...al-machines/page-blobs-backup-and-disaster-recovery.md
Medium Priority View Details →
Scanned: 2026-01-14 01:31
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 moderate Windows bias. Windows-specific tools (e.g., PowerShell, Volume Shadow Service) are mentioned first or exclusively in several sections, and automation examples reference PowerShell before Azure CLI. Application-consistent backup details are richer for Windows (Volume Shadow Service) than Linux (fsfreeze, file-consistent only). Some references and links point to Windows-specific guides, while Linux equivalents are mentioned later or less prominently. There are few explicit Linux command examples, and Linux backup nuances are less detailed.
Recommendations
  • Provide Linux-first or parallel examples for backup and restore automation, using Azure CLI and shell scripts alongside PowerShell.
  • Expand on Linux application-consistent backup strategies, including tools like LVM snapshots, pre/post scripts, or third-party solutions.
  • Ensure all references to backup and restore guides include both Windows and Linux links, not just Windows-specific ones.
  • Add explicit Linux command-line examples for snapshot creation, copying, and recovery (e.g., using Azure CLI, shell commands).
  • Clarify differences in backup consistency between Windows and Linux, and offer best practices for Linux workloads.
GitHub Create Pull Request
Virtual Machines Azure premium storage: Design for high performance ...ticles/virtual-machines/premium-storage-performance.md
Medium Priority View Details →
Scanned: 2026-01-14 01:31
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Sqlserver Heavy
Summary
The documentation page demonstrates moderate Windows bias. Windows tools (PerfMon, Storage Spaces, PowerShell) are mentioned first or exclusively in several sections, and SQL Server (a Windows-centric workload) is used as the primary example throughout. Linux equivalents (iostat, MDADM) are mentioned, but often after Windows tools, and with less detail. The disk striping section provides more configuration detail for Windows (columns, PowerShell) than for Linux (just a link). Benchmarking and performance measurement tools are listed for both platforms, but Windows examples and terminology are more prominent.
Recommendations
  • Provide Linux examples and tools with equal detail and prominence as Windows (e.g., show MDADM configuration steps inline, not just as a link).
  • Use a more balanced set of workload examples (e.g., include Oracle, MySQL, or PostgreSQL on Linux alongside SQL Server).
  • List Linux tools and commands before or alongside Windows tools in tables and explanations.
  • Add more detail on Linux-specific performance tuning (e.g., kernel parameters, file system choices, driver updates).
  • Ensure that all configuration steps (e.g., disk striping, benchmarking) are described for both platforms, not just referenced.
  • Include sample commands and output for Linux tools (iostat, vmstat, MDADM) similar to the PerfMon and PowerShell examples.
GitHub Create Pull Request
Virtual Machines Troubleshoot restore point failures ...cles/virtual-machines/restore-point-troubleshooting.md
Medium Priority View Details →
Scanned: 2026-01-14 01:31
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example Powershell Heavy
Summary
The documentation demonstrates a moderate Windows bias. Windows-specific tools (services.msc, Event Viewer, COM+, VSS, Visual C++ Redistributable) are referenced frequently and often without Linux equivalents or alternatives. Troubleshooting steps and error resolutions for Windows are more detailed, with explicit instructions and tool usage, while Linux guidance is more generic and less tool-specific. Windows patterns (such as PowerShell, Control Panel, and .NET requirements) are mentioned before or instead of Linux alternatives. Some sections (e.g., COM+ and VSS troubleshooting) are Windows-only, with no Linux context or equivalent troubleshooting advice.
Recommendations
  • Add equivalent Linux troubleshooting steps for sections that currently only describe Windows tools (e.g., COM+, VSS, Visual C++ Redistributable).
  • Provide Linux-first or side-by-side examples for common operations, rather than listing Windows steps first.
  • Include Linux-specific error codes and troubleshooting for extension failures, disk issues, and agent problems.
  • Reference Linux tools (e.g., systemctl, journalctl, log file locations) where Windows tools (services.msc, Event Viewer) are mentioned.
  • Clarify which troubleshooting steps are OS-specific and provide parity in detail and actionable guidance for both platforms.
GitHub Create Pull Request
Virtual Machines Share Resources in Azure Compute Gallery ...s/blob/main/articles/virtual-machines/share-gallery.md
Medium Priority View Details →
Scanned: 2026-01-14 01:31
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides examples for Azure Portal, Azure CLI, and PowerShell. While CLI examples are cross-platform, PowerShell is Windows-centric and is presented as a primary automation option. The order of examples places PowerShell before any Linux-specific shell scripting, and there are no Bash or Linux shell examples, nor is there mention of Linux-native tools or patterns. This may create friction for Linux/macOS users who do not use PowerShell.
Recommendations
  • Add Bash shell examples using Azure CLI to explicitly demonstrate Linux/macOS workflows.
  • Clarify that Azure CLI commands work on Linux/macOS and Windows, and provide sample shell scripts for Linux users.
  • Reorder examples so that cross-platform CLI instructions are presented before PowerShell.
  • Mention that PowerShell Core is available on Linux/macOS, but also provide native Bash alternatives for common tasks.
GitHub Create Pull Request
Virtual Machines Share Gallery Images Across Tenants by Using an App Registration ...icles/virtual-machines/share-using-app-registration.md
Medium Priority View Details →
Scanned: 2026-01-14 01:31
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation provides both Azure CLI and PowerShell examples for sharing gallery images across tenants, but the PowerShell section is significantly more detailed, using Windows-centric tools and patterns (e.g., New-AzNetworkSecurityRuleConfig for RDP, Set-AzVMOperatingSystem -Windows, Get-Credential for username/password). The PowerShell example is much longer and more comprehensive than the CLI example, which is brief and omits networking setup. Windows tools and concepts (RDP, Windows OS config) are prominent, and the PowerShell tab appears after the CLI tab, but the CLI example is minimal.
Recommendations
  • Expand the Azure CLI example to include networking setup and VM configuration steps, matching the detail of the PowerShell example.
  • Provide Linux-focused examples, such as configuring SSH access, Linux OS settings, and security rules for SSH (port 22) instead of RDP (port 3389).
  • Include explicit instructions for Linux/macOS users, such as using SSH keys and Linux-friendly credential management.
  • Balance the detail and complexity of CLI and PowerShell sections so Linux users are not disadvantaged.
  • Avoid Windows-specific terminology or provide Linux alternatives in parallel.
GitHub Create Pull Request
Virtual Machines Share VM images in a compute gallery ...in/articles/virtual-machines/shared-image-galleries.md
Medium Priority View Details →
Scanned: 2026-01-14 01:31
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. PowerShell examples are provided alongside CLI, but references to Windows tools (e.g., Sysprep) and Windows-specific documentation links are more prominent and often appear before Linux equivalents. In some cases, Linux instructions or links are present but less visible or secondary. There are also references to Windows upload guides before Linux ones, and some examples (e.g., image creation from specialized disks) link only to Windows-specific pages. Overall, Linux parity is present but not consistently prioritized or equally represented.
Recommendations
  • Ensure that Linux and Windows examples are presented side-by-side or in parallel tabs, rather than Windows first.
  • When referencing external guides (e.g., uploading VHDs, creating specialized images), always provide both Linux and Windows links together.
  • Expand CLI examples to include Linux-specific scenarios or commands where relevant, especially in troubleshooting and FAQs.
  • Avoid referencing Windows tools (like Sysprep) before Linux equivalents (like waagent); mention both together.
  • Review all linked pages to ensure Linux documentation is equally detailed and accessible.
GitHub Create Pull Request
Virtual Machines Resize a virtual machine ...blob/main/articles/virtual-machines/sizes/resize-vm.md
Medium Priority View Details →
Scanned: 2026-01-14 01:31
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits a moderate Windows bias. PowerShell is given a prominent, detailed section with multiple scripts and explanations, while Linux-native tooling (e.g., Bash, shell) is not mentioned outside of Azure CLI. The Terraform example references Windows VM quickstart, and the CLI examples use Bash syntax but do not explicitly address Linux-specific considerations. Windows terminology and tools (PowerShell, Windows VM resource blocks) are introduced before Linux equivalents, and the workaround for temp disk migration links to a Windows-specific article. There are no explicit Linux shell or macOS Terminal examples, and Linux users may need to infer steps from the CLI section.
Recommendations
  • Add explicit Linux/macOS shell examples for resizing VMs using Azure CLI, including notes on environment setup and differences (e.g., quoting, variable syntax).
  • Provide parity in Terraform examples by referencing both Windows and Linux VM quickstarts, or showing a generic example.
  • Ensure workaround and migration links include Linux VM scenarios, not just Windows.
  • Balance PowerShell and CLI coverage, and introduce CLI examples before or alongside PowerShell to avoid Windows-first impression.
  • Clarify that Azure CLI commands work cross-platform and highlight any OS-specific caveats.
GitHub Create Pull Request
Virtual Machines Av1-series retirement ...ual-machines/sizes/retirement/av1-series-retirement.md
Medium Priority View Details →
Scanned: 2026-01-14 01:31
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example Windows First
Summary
The documentation provides detailed instructions for resizing VMs using the Azure portal and Azure PowerShell, but omits examples for Azure CLI (which is cross-platform and preferred by many Linux/macOS users). The PowerShell example is given, but no equivalent Azure CLI or Bash example is shown. The ordering also places Windows-centric tools (portal, PowerShell) before mentioning CLI, despite CLI being referenced in the introductory sentence.
Recommendations
  • Add an Azure CLI example for resizing VMs, including listing available sizes and performing the resize.
  • Explicitly mention that Azure CLI works on Linux/macOS and Windows.
  • Consider reordering the examples so that CLI instructions are presented before or alongside PowerShell, or at least equally.
  • Where possible, provide Bash script snippets for common tasks to further support Linux users.
GitHub Create Pull Request
Virtual Machines DCsv2-series retirement ...l-machines/sizes/retirement/dcsv2-series-retirement.md
Medium Priority View Details →
Scanned: 2026-01-14 01:31
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. In the migration steps, examples are given for the Azure portal (which is platform-agnostic but often associated with Windows users), followed by Azure PowerShell, and then Azure CLI. The PowerShell example is detailed and comes before the CLI example, and the CLI authentication example incorrectly uses PowerShell syntax (variables with $), which may confuse Linux/macOS users. There are no explicit Bash or Linux shell examples, nor are Linux-specific considerations (such as shell differences or package installation instructions for Azure CLI) mentioned. The support instructions reference both Windows and Linux VMs, but all command-line examples are Windows-centric or ambiguous.
Recommendations
  • Provide Bash/Linux shell examples for Azure CLI commands, using correct syntax for variable assignment and command chaining.
  • Clarify that Azure CLI is cross-platform and give installation instructions for Linux/macOS.
  • List Azure CLI examples before PowerShell, or present both side-by-side.
  • Explicitly mention that all steps can be performed on Linux/macOS, and note any differences (e.g., authentication methods, environment setup).
  • Correct the CLI authentication example to use Bash syntax (e.g., export, variable assignment without $ prefix).
GitHub Create Pull Request
Virtual Machines Create SSH keys in the Azure portal ...blob/main/articles/virtual-machines/ssh-keys-portal.md
Medium Priority View Details →
Scanned: 2026-01-14 01:31
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates Windows bias primarily in the 'Connect to the VM' section, where only a PowerShell prompt is mentioned for running the SSH command, with no reference to Linux/macOS terminals. Additionally, the example command uses a Windows-style path (/Downloads/...), and there are no Linux/macOS-specific instructions or screenshots. The page also refers users to a guide for connecting to Linux VMs from Windows, further reinforcing a Windows-first perspective. Linux and macOS users are left to infer that the same SSH command applies to their platforms, but this is not made explicit.
Recommendations
  • Add explicit instructions and examples for connecting from Linux and macOS terminals, including typical shell environments (e.g., Bash, Terminal.app).
  • Include screenshots or terminal prompts from Linux/macOS alongside PowerShell examples.
  • Clarify that the SSH command works across platforms and note any path differences (e.g., ~/Downloads/ on Linux/macOS vs. C:\Users\...\Downloads on Windows).
  • Reference Linux/macOS documentation for SSH usage, not only Windows guides.
GitHub Create Pull Request
Virtual Machines Upgrade Gen1 VMs to Trusted launch ...s/virtual-machines/trusted-launch-existing-vm-gen-1.md
Medium Priority View Details →
Scanned: 2026-01-14 01:31
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation exhibits several Windows biases: Windows-specific tools (MBR2GPT.exe, BitLocker, Defrag) are discussed in detail, with Linux alternatives mentioned briefly or not at all. Windows instructions and troubleshooting steps are more comprehensive and appear first. The PowerShell example is more detailed than the CLI, and ARM template deployment uses PowerShell. Linux upgrade scenarios are limited to certain distros, with unsupported cases redirected to a registration form rather than providing guidance. There is less troubleshooting and fewer step-by-step instructions for Linux users.
Recommendations
  • Provide Linux-first or parallel examples for disk conversion (MBR to GPT) and EFI partition creation, including common tools (e.g., gdisk, parted, efibootmgr) and step-by-step instructions.
  • Expand troubleshooting sections for Linux, covering common errors and recovery steps.
  • Include parity in backup/encryption guidance for Linux (e.g., LUKS, cryptsetup).
  • Offer ARM template deployment examples using Azure CLI or bash, not just PowerShell.
  • Ensure Linux instructions are as detailed and actionable as Windows, including validation and rollback steps.
  • List Linux tools and commands before or alongside Windows tools where applicable.
GitHub Create Pull Request
Virtual Machines Enable Trusted launch on existing Uniform scale set ...icles/virtual-machines/trusted-launch-existing-vmss.md
Medium Priority View Details →
Scanned: 2026-01-14 01:31
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation page exhibits several Windows biases. Windows examples (e.g., OS image references, ARM template samples) are shown first or exclusively, with Linux equivalents only mentioned in passing (e.g., extension publisher name table). The ARM template and CLI/PowerShell examples use Windows-centric image SKUs and do not provide parallel Linux image examples. PowerShell is featured heavily, and Windows tools/patterns (e.g., WindowsServer image, Azure PowerShell) are prioritized. Linux users are left to infer the correct parameters and images for their scenarios.
Recommendations
  • Provide explicit Linux OS image examples and parameters in ARM template, CLI, and PowerShell sections.
  • Show Linux extension publisher usage in sample code, not just in a table.
  • Alternate or parallelize Windows and Linux examples in all code blocks.
  • Clarify any differences in Trusted launch support or configuration for Linux scale sets.
  • Include links to Linux-specific documentation where relevant.
GitHub Create Pull Request
Virtual Machines Deploy a Trusted Launch VM ...ain/articles/virtual-machines/trusted-launch-portal.md
Medium Priority View Details →
Scanned: 2026-01-14 01:31
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation provides both Linux and Windows guidance for deploying Trusted Launch VMs, but there is a notable Windows bias in several areas. PowerShell examples are exclusively for Windows VMs, with no Linux PowerShell or Bash equivalents. Windows-centric tools and patterns (e.g., RDP, BitLocker, Windows-specific image generalization) are referenced more frequently and in greater detail. In multi-step PowerShell sections, only Windows VM creation is shown, while CLI examples are Linux-focused. In some cases, Windows instructions or terminology appear first or are more detailed, and Linux-specific nuances (such as SSH configuration or Linux image generalization) are less emphasized or referenced only via external links.
Recommendations
  • Provide PowerShell examples for Linux VM deployment, or clarify that PowerShell is Windows-only and offer Bash or shell script alternatives for Linux users.
  • Balance CLI and PowerShell examples: for every Windows-focused example, include a Linux equivalent (e.g., show both Windows and Linux VM creation in PowerShell).
  • When discussing VM configuration (network, security, disk), include Linux-specific considerations (e.g., SSH, Linux disk encryption, SELinux/AppArmor).
  • Avoid Windows-first ordering in examples and instructions; alternate or group by OS where possible.
  • Expand on Linux image generalization and deployment steps within the documentation, not just via external links.
  • Clarify when a step or tool is Windows-only, and provide Linux/macOS alternatives or guidance.
GitHub Create Pull Request
Virtual Machines Enable Trusted launch on existing Gen2 VMs ...rticles/virtual-machines/trusted-launch-existing-vm.md
Medium Priority View Details →
Scanned: 2026-01-14 01:31
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation provides parity for both Linux and Windows VMs at a high level, but there is a notable bias toward Windows tools and patterns. PowerShell is heavily featured in both the main and template sections, and Windows-specific tools (RDP, PowerShell) are mentioned before their Linux equivalents (SSH, CLI). The CLI examples are cross-platform, but PowerShell is Windows-centric. In several places, PowerShell is presented as the default scripting option, and instructions for tasks like deallocation and template deployment use PowerShell syntax, with no Bash or Linux shell alternatives. The documentation also references Windows tools (RDP, PowerShell) before Linux ones (SSH, CLI) when discussing VM access.
Recommendations
  • Provide Bash or Linux shell script examples alongside PowerShell for template deployments and VM operations.
  • Explicitly mention that Azure CLI is cross-platform and can be run on Linux/macOS, and provide Linux/macOS installation links.
  • When listing access methods, mention SSH (Linux) before or alongside RDP (Windows), or alternate their order.
  • Where PowerShell is used for template deployment, provide equivalent Bash/CLI commands for Linux/macOS users.
  • Clarify that all steps can be performed on Linux VMs, and link to Linux-specific troubleshooting or validation guides.
GitHub Create Pull Request
Virtual Machines FAQ for Trusted Launch ...b/main/articles/virtual-machines/trusted-launch-faq.md
Medium Priority View Details →
Scanned: 2026-01-14 01:31
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation shows a moderate Windows bias. Windows terminology and tools (e.g., Hyper-V, Secure Boot, PowerShell) are frequently mentioned first or exclusively. CLI and PowerShell examples are provided for both Windows and Linux, but PowerShell (a Windows-centric tool) is often shown alongside CLI, and some examples (such as image validation) use Windows images first. Linux-specific troubleshooting and validation are covered, but Windows examples and links (e.g., Secure Boot, Hyper-V) are referenced before Linux equivalents. Some sections lack explicit Linux parity, such as troubleshooting vTPM states and certificate inspection, which do not mention Linux-specific tools.
Recommendations
  • Ensure Linux examples are presented alongside or before Windows examples, especially in command sections.
  • Include Linux-native tooling (e.g., Bash scripts, Linux certificate inspection commands) where PowerShell is used.
  • Reference Linux documentation and tools (e.g., Linux boot troubleshooting, TPM tools) as prominently as Windows/Hyper-V links.
  • Add explicit Linux troubleshooting steps for vTPM and Secure Boot failures, not just generic or Windows-focused advice.
  • Balance terminology: avoid using Windows/Hyper-V terms as the default, and clarify when features/tools are cross-platform.
GitHub Create Pull Request
Virtual Machines Secure Boot UEFI keys ...ual-machines/trusted-launch-secure-boot-custom-uefi.md
Medium Priority View Details →
Scanned: 2026-01-14 01:31
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation frequently mentions Windows tools and patterns (e.g., PowerShell, MicrosoftWindowsTemplate) before or alongside Linux equivalents. PowerShell is listed as a primary method for creating resources, and signature templates include Windows-specific options. However, Linux verification commands and useful links for Linux distributions are provided, mitigating some bias.
Recommendations
  • Provide explicit Linux CLI (e.g., Bash, Azure CLI) examples alongside or before PowerShell examples for resource creation and management.
  • Clarify that all steps can be performed on Linux/macOS, and highlight any platform-specific differences.
  • Include Linux-specific signature template examples if available.
  • Ensure that Linux tools (e.g., OpenSSL, mokutil) are referenced equally or before Windows tools.
  • Add step-by-step Linux/macOS instructions for certificate/key creation and image management.
GitHub Create Pull Request
Virtual Machines Trusted Launch for Azure VMs .../blob/main/articles/virtual-machines/trusted-launch.md
Medium Priority View Details →
Scanned: 2026-01-14 01:31
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation page for Trusted Launch for Azure VMs demonstrates a moderate Windows bias. Windows-specific technologies (Secure Boot, vTPM, VBS, HVCI, Credential Guard) are described in detail, often referencing Windows documentation and tools. Example ARM templates for Trusted Launch reference Windows VM deployments first, and Windows-centric features (like driver installation) are discussed before Linux equivalents. Linux-specific instructions (e.g., for Secure Boot and driver installation) are mentioned but are less detailed and sometimes only referenced via external links. There are no direct Linux CLI or shell examples, and Windows tools and patterns (such as Windows Defender, Credential Guard, and PowerShell) are referenced without Linux parity.
Recommendations
  • Provide Linux-specific examples and instructions alongside Windows examples, especially for enabling Trusted Launch, Secure Boot, and vTPM.
  • Include direct Linux CLI or shell commands (e.g., az CLI, bash) for common tasks, not just ARM templates or Windows-centric tools.
  • Reference Linux documentation and troubleshooting guides with equal prominence to Windows resources.
  • Discuss Linux security features (such as kernel module signing, integrity measurement, and alternatives to Credential Guard) in comparable detail.
  • Ensure that Linux driver installation and Secure Boot instructions are as detailed and accessible as Windows equivalents.
GitHub Create Pull Request
Virtual Machines Guest updates and host maintenance overview ...icles/virtual-machines/updates-maintenance-overview.md
Medium Priority View Details →
Scanned: 2026-01-14 01:31
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation generally aims for parity between Windows and Linux, but there are several areas where Windows is prioritized or Linux details are less visible. Windows-specific tools and features (like Hotpatching) are described in detail, while Linux equivalents are not mentioned or are less prominent. In some sections, Windows links/examples are listed before Linux, and PowerShell is mentioned as a primary tool, with less emphasis on Bash/Cloud Shell. Some features (like maintenance control for extensions) mention CLI and PowerShell, but do not clarify Linux support or provide Linux-specific examples.
Recommendations
  • Ensure that Linux and Windows examples/links are always presented together, or alternate their order to avoid implicit prioritization.
  • For every Windows-specific feature (e.g., Hotpatching), explicitly state Linux alternatives or clarify if not available.
  • When referencing tools (e.g., PowerShell, CLI), provide equal emphasis and examples for Bash/Cloud Shell and Linux-native tools.
  • Add explicit Linux examples or links where only Windows ones are present, such as in the 'Scheduled events' section.
  • Clarify in each section which features are Windows-only, Linux-only, or cross-platform, to set user expectations.
  • Where features are not available for Linux, provide workarounds or guidance for Linux users.
GitHub Create Pull Request
Virtual Machines Deploying disks with Azure Resource Manager templates ...l-machines/using-managed-disks-template-deployments.md
Medium Priority View Details →
Scanned: 2026-01-14 01:31
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page consistently uses Windows-centric examples, such as referencing the 'vm-simple-windows' template and showing JSON snippets with Windows-specific image references. There are no Linux-specific template examples or image references in the main body, and all code samples use Windows images. Linux parity is only mentioned in the 'Next steps' section, which links to a Linux template, but no Linux examples are shown directly in the documentation.
Recommendations
  • Include Linux VM examples alongside Windows VM examples in each code snippet, using appropriate image references (e.g., Ubuntu, CentOS).
  • Reference both 'vm-simple-windows' and 'vm-simple-linux' templates in the introduction and throughout the document.
  • Add explicit notes or sections highlighting differences or considerations for Linux VMs when deploying disks.
  • Ensure that all sample JSON includes both Windows and Linux image references, or alternate between them.
  • Provide links to Linux-specific documentation and quickstart templates earlier in the document, not just in 'Next steps'.
GitHub Create Pull Request
Virtual Machines List, update, and delete resources ...in/articles/virtual-machines/update-image-resources.md
Medium Priority View Details →
Scanned: 2026-01-14 01:31
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides both Azure CLI and PowerShell examples for all major operations, but PowerShell is given equal prominence as CLI, despite being primarily a Windows tool. There are no Linux-specific examples, and PowerShell examples may not be directly usable on Linux/macOS. In some sections, PowerShell examples are presented immediately after CLI, which can subtly reinforce a Windows-centric workflow. No Linux/macOS shell scripting or tool references are present.
Recommendations
  • Clarify that PowerShell examples are primarily for Windows users, and note cross-platform PowerShell Core support if applicable.
  • Add explicit Bash or shell script examples for Linux/macOS users where scripting is shown for PowerShell.
  • Include notes on installing and using Azure CLI on Linux/macOS, and highlight its cross-platform nature.
  • Where variables or scripting are shown, use POSIX-compliant syntax in CLI examples (e.g., export region=westus instead of region=westus).
  • Consider adding a 'Platform compatibility' section to clarify tool support and usage on different OSes.
GitHub Create Pull Request
Virtual Machines Use Premium SSD v2 with VMs in availability set ...l-machines/use-premium-ssd-v2-with-availability-set.md
Medium Priority View Details →
Scanned: 2026-01-14 01:31
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 Azure CLI and PowerShell examples for deploying Premium SSD v2 disks with VMs in an availability set, but the VM creation examples use a Windows image ('Win2016Datacenter') and PowerShell is presented as a primary automation option. There are no explicit Linux VM image examples, nor are there any bash scripting or Linux-specific instructions. The use of Windows-centric tools and examples may create friction for Linux/macOS users.
Recommendations
  • Include Linux VM image examples (e.g., UbuntuLTS) alongside Windows in CLI and PowerShell sections.
  • Add bash scripting examples for common tasks, especially for disk attachment and VM creation.
  • Clarify that Azure CLI is cross-platform and provide guidance for Linux/macOS users where relevant.
  • Explicitly mention that the instructions apply to both Windows and Linux VMs unless there are platform-specific limitations.
  • Balance the order of examples so that Linux and Windows are presented equally (e.g., alternate or show both in parallel).
GitHub Create Pull Request
Virtual Machines User data for Azure Virtual Machine ...-docs/blob/main/articles/virtual-machines/user-data.md
Medium Priority View Details →
Scanned: 2026-01-14 01:31
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits a Windows bias in several ways: JSON examples for VM creation and updates consistently use Windows OS images and Windows-specific configuration fields (e.g., 'osType': 'Windows', 'windowsConfiguration', 'timeZone', 'MicrosoftWindowsServer'), with no equivalent Linux examples. Windows-centric fields are shown first and exclusively in code samples. There are no explicit Linux VM configuration examples, nor is there guidance for Linux-specific patterns or fields. While the page references a Linux IMDS sample in a link, the main content and examples are Windows-focused.
Recommendations
  • Add parallel JSON examples for Linux VM creation and updates, using Linux OS images and relevant configuration fields (e.g., 'osType': 'Linux', 'linuxConfiguration').
  • Include Linux-specific fields and patterns in code samples, such as SSH key configuration and Linux image references.
  • Alternate the order of examples or provide both Windows and Linux examples side-by-side.
  • Explicitly mention Linux support and provide guidance for Linux users in each relevant section.
  • Ensure links to Linux documentation are prominent and not just in 'Next steps'.
GitHub Create Pull Request
← Previous Page 9 of 33 Next →