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 126-150 of 818 flagged pages
Virtual Machines Enable MSP on an Existing Virtual Machine or Virtual Machine Scale Set ...tual-machines/metadata-security-protocol/brownfield.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 provides more detailed information and examples for Windows VMs, such as showing Windows extension status output and referencing Windows-specific tools and paths. Linux instructions are less explicit, requiring users to infer steps or perform additional REST API calls without concrete examples. Windows extensions and their status outputs are shown, but Linux equivalents are only mentioned in passing, with no example output or explicit validation steps.
Recommendations
  • Provide explicit example output for Linux extension status, similar to the Windows example.
  • Include step-by-step instructions or sample REST API calls for installing and validating the Proxy Agent extension on Linux VMs.
  • Mention Linux tools, file paths, and validation patterns where appropriate, not just Windows equivalents.
  • Ensure parity in troubleshooting and validation guidance for both Windows and Linux users.
GitHub Create Pull Request
Virtual Machines NV series migration guide ...-machines/migration/sizes/nv-series-migration-guide.md
Medium Priority View Details →
Scanned: 2026-01-14 01:31
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exhibits Windows bias by focusing exclusively on Windows guest OS support for NVv4 VMs, referencing only Windows-specific driver installation guides and extensions, and omitting Linux migration steps, driver instructions, or parity notes. Linux users are left without guidance for migrating NV-series VMs, especially regarding GPU driver installation and support.
Recommendations
  • Explicitly state Linux support status for each VM series, including any limitations.
  • Provide Linux-specific migration steps, including driver installation instructions and links to Linux driver documentation.
  • Include notes or alternatives for Linux users where Windows-only features/extensions are mentioned.
  • Add FAQ entries addressing common Linux migration scenarios.
  • Ensure extension and driver documentation links include Linux equivalents where available.
GitHub Create Pull Request
Virtual Machines Create and upload an Oracle Linux VHD ...les/virtual-machines/linux/oracle-create-upload-vhd.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 Windows bias by exclusively referencing Hyper-V (a Windows-only virtualization tool) for creating and managing VHDs, providing links only to Windows/Hyper-V instructions, and omitting Linux-native alternatives (such as KVM, qemu-img, or VirtualBox). All example workflows for VM creation and shutdown use Hyper-V Manager, with no mention of equivalent Linux tools or commands. This may create friction for Linux users who do not have access to Hyper-V.
Recommendations
  • Add instructions and examples for creating and managing VHDs using Linux-native tools such as KVM, qemu-img, or VirtualBox.
  • Provide Linux command-line examples for VM creation, shutdown, and disk conversion (e.g., using qemu-img to convert disk formats).
  • Include links to official documentation for Linux virtualization solutions and disk management tools.
  • Present both Windows and Linux workflows side by side, or clearly indicate which steps are platform-specific.
GitHub Create Pull Request
Virtual Machines Customer intent: As a cloud administrator, I want to retrieve the encryption type of a specified disk in a resource group, so that I can ensure compliance with security standards for our virtual machines. ...ttps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/virtual-machines/includes/virtual-machines-disks-encryption-status-powershell.md
Medium Priority View Details →
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 only a PowerShell example for retrieving disk encryption type, which is specific to Windows environments. There are no equivalent examples for Linux/macOS users (e.g., using Azure CLI or REST API), and the Windows-centric approach is presented first and exclusively.
Recommendations
  • Add equivalent Azure CLI example for Linux/macOS users.
  • Include REST API or SDK examples that are platform-agnostic.
  • Clearly indicate that PowerShell is Windows-specific and provide guidance for non-Windows platforms.
GitHub Create Pull Request
Virtual Machines Export Azure resource groups that contain VM extensions ...ticles/virtual-machines/extensions/export-templates.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 demonstrates a Windows bias by referencing Windows tools and patterns first, such as PowerShell scripts and the BGInfo extension, and by listing Windows extensions before Linux equivalents. The sample deployment scripts are described as 'PowerShell and Azure CLI', with PowerShell mentioned first and no explicit Bash or Linux shell examples provided. The 'ms.collection' metadata is set to 'windows', further reinforcing the bias. Linux-specific instructions, examples, or parity in extension support are not clearly presented.
Recommendations
  • Explicitly mention and provide Bash or Linux shell examples for template deployment, alongside PowerShell.
  • List Linux and Windows VM extensions in parallel or alphabetically, rather than Windows-first.
  • Clarify that Azure CLI is cross-platform and provide Linux/macOS usage notes.
  • Update metadata to reflect cross-platform applicability, not just 'windows'.
  • Include screenshots or instructions from Linux/macOS perspectives where relevant.
GitHub Create Pull Request
Virtual Machines Create and upload an OpenBSD image ...ticles/virtual-machines/linux/create-upload-openbsd.md
Medium Priority View Details →
Scanned: 2026-01-14 01:31
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates bias toward Windows by exclusively mentioning Hyper-V and PowerShell for VHD creation and conversion, with no Linux or cross-platform alternatives provided. The only example for converting disk formats uses PowerShell, and instructions for creating the VHD reference Hyper-V and link to Windows-specific documentation. No Linux tools (such as qemu-img or VirtualBox) are mentioned for these steps.
Recommendations
  • Add instructions and examples for creating and converting VHD files using Linux tools such as qemu-img, VBoxManage (VirtualBox), or KVM.
  • Provide Linux/macOS command-line examples for disk conversion (e.g., qemu-img convert -f raw -O vpc ...).
  • Mention cross-platform alternatives to Hyper-V for virtualization and disk preparation.
  • Ensure that examples for critical steps (VHD creation/conversion) are shown for both Windows and Linux/macOS users, or at least link to relevant Linux documentation.
GitHub Create Pull Request
Virtual Machines Set up Azure HPC or AI VMs .../blob/main/articles/virtual-machines/set-up-hpc-vms.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 generally maintains parity between Linux and Windows, offering links to both Linux and Windows quickstarts, disk attachment guides, and GPU driver installation instructions. However, in the 'Set up VM' section, there is no link to an AMD GPU driver installation guide for Linux, while there is one for Windows. Additionally, in the driver installation section, Windows links are listed before Linux for AMD drivers, which may indicate a slight 'windows_first' bias.
Recommendations
  • Add a link or instructions for installing AMD GPU drivers on Linux VMs, if supported.
  • Ensure that Linux and Windows instructions are presented in parallel order (e.g., always list Linux first or alternate consistently).
  • Explicitly state if certain features (such as AMD GPU drivers) are not supported on Linux, to avoid confusion.
  • Where possible, provide example commands for both Linux (bash/ssh) and Windows (PowerShell/SSH) in sections that discuss connecting or configuring the VM.
GitHub Create Pull Request
Virtual Machines Creating and configuring a key vault for Azure Disk Encryption with Microsoft Entra ID (previous release) ...irtual-machines/linux/disk-encryption-key-vault-aad.md
Medium Priority View Details →
Scanned: 2026-01-14 01:31
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation provides extensive PowerShell-based examples and scripts, including advanced scenarios, and references Windows filesystem paths (e.g., C:\certificates\mycert.pfx) and Windows-centric tools. While Azure CLI examples are present for basic operations, advanced and end-to-end scenarios (such as certificate-based authentication and key encryption key setup) are only shown with PowerShell, with no Linux shell or cross-platform alternatives. There are no bash, shell, or Linux-native scripting examples, and some steps (like certificate handling) are described using Windows file paths and tools. Certificate-based authentication is explicitly noted as unsupported on Linux, but the documentation does not offer Linux alternatives or clarify Linux-specific workflows for these advanced tasks.
Recommendations
  • Provide bash or shell script equivalents for all PowerShell examples, especially for advanced scenarios such as KEK setup and certificate management.
  • Use cross-platform file paths and examples (e.g., /home/user/certificates/mycert.pfx) alongside Windows paths.
  • Clearly indicate which steps are Windows-only and provide Linux-specific guidance or workarounds where features are unsupported.
  • Expand Azure CLI coverage to include all advanced scenarios, not just basic key vault creation and policy setting.
  • Add explicit notes or sections for Linux users, detailing any limitations and alternative approaches.
GitHub Create Pull Request
Virtual Machines How to upgrade Azure Disk Encryption on a disk ...cles/virtual-machines/linux/disk-encryption-upgrade.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 exhibits notable Windows bias. The migration process is only documented and supported via Azure PowerShell, with no CLI or Linux-native instructions. All upgrade examples use PowerShell, and the migration section does not mention Linux-specific steps or alternatives, despite referencing Linux ADE versions earlier. This creates friction for Linux users who may not use PowerShell or Windows environments.
Recommendations
  • Provide equivalent Azure CLI instructions for migration, or clearly state if CLI is not supported for this operation.
  • Document Linux-specific considerations or limitations for ADE migration, including any required tools or workarounds.
  • If migration is truly only possible via PowerShell, offer guidance for Linux users on installing and using PowerShell Core on Linux, or accessing Azure Cloud Shell.
  • Present examples for both Windows and Linux platforms, or clarify platform restrictions early in the article.
GitHub Create Pull Request
Virtual Machines Troubleshooting Azure Disk Encryption for Linux VMs ...tual-machines/linux/disk-encryption-troubleshooting.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 is focused on Linux VMs and provides Linux-specific troubleshooting steps. However, when discussing how to check encryption status and disable disk encryption, PowerShell commands are presented first and in greater detail, with Linux/Azure CLI equivalents mentioned only briefly or after the PowerShell examples. This ordering and emphasis may create friction for Linux users who are more likely to use Azure CLI or Bash.
Recommendations
  • Provide Azure CLI examples alongside or before PowerShell examples, especially in sections relevant to Linux users.
  • Include Bash script examples for common troubleshooting tasks, such as checking encryption status.
  • Clarify which commands are platform-agnostic (e.g., Azure CLI) and which are Windows-specific (e.g., PowerShell), and guide Linux users to the most appropriate tools.
  • Ensure parity in detail and explanation between PowerShell and CLI/Bash instructions.
GitHub Create Pull Request
Virtual Machines Create SSH keys with the Azure CLI ...b/main/articles/virtual-machines/ssh-keys-azure-cli.md
Medium Priority View Details →
Scanned: 2026-01-14 01:31
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Linux First Missing Windows Example
Summary
The documentation is strongly Linux-oriented, with all command-line examples using Linux paths, Bash commands, and Linux file permission patterns. There are no Windows-specific instructions, examples, or PowerShell/CMD equivalents for generating, storing, or using SSH keys. Windows users may struggle to follow the steps as written.
Recommendations
  • Add Windows-specific examples using PowerShell or CMD, including file paths (e.g., C:\Users\username\.ssh\...) and permission management.
  • Provide guidance on using SSH from Windows (e.g., via PowerShell, Windows Terminal, or PuTTY), especially for connecting to VMs.
  • Include notes about differences in file system paths and permission handling between Linux/macOS and Windows.
  • Ensure parity by presenting both Linux and Windows workflows side-by-side where relevant.
GitHub Create Pull Request
Virtual Machines Tenable One-Click Nessus Extension for Azure VMs ...b/main/articles/virtual-machines/extensions/tenable.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 exhibits a notable Windows bias in its command-line deployment section. Only PowerShell examples are provided, with no equivalent Bash/CLI examples for Linux users. The command-line workflow is described exclusively in PowerShell syntax, and Windows-centric tooling is referenced before any Linux alternatives (which are not mentioned at all). While the UI workflow is cross-platform, Linux users are left without clear CLI guidance.
Recommendations
  • Add Bash/Azure CLI examples for deploying the Nessus Agent extension on Linux VMs.
  • Explicitly mention and demonstrate Linux-compatible command-line tools (e.g., az CLI) alongside PowerShell.
  • Ensure parameter descriptions and workflows are not PowerShell-specific and clarify cross-platform applicability.
  • Present Windows and Linux examples side-by-side or alternate which is shown first.
GitHub Create Pull Request
Virtual Machines Azure support for Generation 2 VMs ...cs/blob/main/articles/virtual-machines/generation-2.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 examples (especially PowerShell) are provided in detail, while Linux equivalents are less prominent or missing in some sections. Windows tools and patterns (e.g., PowerShell, Windows-specific image SKUs) are mentioned first or exclusively in several places, and Linux users may need to infer or search for their own workflows.
Recommendations
  • Provide Linux-specific CLI or scripting examples alongside PowerShell, especially for tasks like creating managed disks from .vhd files and setting Hyper-V Generation property.
  • Ensure that Linux examples are presented with equal prominence and detail as Windows examples, including step-by-step instructions.
  • Reference Linux documentation links directly in relevant sections, not just in 'Next steps'.
  • When listing commands or workflows, alternate the order or present both Windows and Linux options together.
  • Clarify any differences or limitations for Linux users in FAQ and procedural sections.
GitHub Create Pull Request
Virtual Machines Overview of Maintenance control for OS image upgrades on Azure Virtual Machine Scale Sets ...ines/virtual-machine-scale-sets-maintenance-control.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 a Windows bias by emphasizing Azure PowerShell as the primary management option, listing it first among alternatives, and featuring a PowerShell-specific 'Next steps' link. There is no explicit mention or prioritization of Linux-native tools or examples, such as Bash or shell scripting, nor is there guidance tailored for Linux/macOS users.
Recommendations
  • Provide Linux/macOS-specific examples using Azure CLI and Bash scripting.
  • Alternate the order of management options to avoid always listing PowerShell first.
  • Include 'Next steps' links for both PowerShell and Azure CLI to ensure parity.
  • Explicitly mention that Azure CLI is cross-platform and suitable for Linux/macOS users.
  • Add a section or note highlighting differences or considerations for Linux/macOS environments.
GitHub Create Pull Request
Virtual Machines Customer intent: "As an IT administrator, I want to troubleshoot common VM extension failures in Azure Resource Manager templates, so that I can ensure the proper deployment and functionality of IaaS infrastructure." ...des/virtual-machines-common-extensions-troubleshoot.md
Medium Priority View Details →
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 references authoring extension templates specifically for Windows, with a link to a Windows-focused template description. There is no mention of Linux or cross-platform equivalents, nor are Linux troubleshooting steps or examples provided.
Recommendations
  • Include links to Linux-specific template authoring documentation alongside the Windows link.
  • Provide examples and troubleshooting steps for both Windows and Linux VM extensions.
  • Clarify when instructions apply to all platforms, or specify platform differences where relevant.
GitHub Create Pull Request
Virtual Machines Use virtual machine restore points ...ual-machines/virtual-machines-create-restore-points.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 demonstrates a subtle Windows bias by describing application consistency primarily in terms of Windows (VSS writers) and only briefly mentioning Linux (pre- and postscripts) without providing equivalent detail or examples. There are no Linux-specific instructions, examples, or tool references, while Windows mechanisms (VSS) are named and explained first.
Recommendations
  • Provide explicit Linux examples for implementing application-consistent restore points, such as sample pre- and post-script templates.
  • Include references to common Linux backup tools or patterns that can be used with Azure VM restore points.
  • Ensure parity in explanation depth for both Windows and Linux, describing how Linux users can achieve application consistency step-by-step.
  • Consider listing Linux and Windows mechanisms side-by-side, or alternating which is mentioned first.
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-14 01:31
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation presents Azure Storage Explorer as a cross-platform GUI tool, which is available for both Windows and Linux. However, the 'Next steps' section exclusively links to Windows-specific guides, and there are no Linux/macOS-specific follow-up resources or examples. The documentation does not mention or show parity for Linux workflows after disk operations, nor does it provide Linux-specific guidance for common post-upload/download tasks.
Recommendations
  • Add 'Next steps' links for Linux workflows, such as creating or attaching disks to Linux VMs.
  • Ensure parity in follow-up documentation for both Windows and Linux users.
  • Explicitly mention that Storage Explorer is available for Linux and macOS, and provide installation instructions or links for those platforms.
  • Include examples or references for managing disks with Linux VMs after upload/download, such as mounting or formatting disks on Linux.
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-14 01:31
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation provides both CLI and PowerShell examples, but PowerShell (a Windows-centric tool) is given a dedicated section with multiple examples, while Linux-native scripting (e.g., Bash) is not mentioned. In ARM template examples, Windows image references are used by default. The ordering of sections places PowerShell after CLI, but the template example for VMs uses a Windows image, and there is no explicit Linux template example.
Recommendations
  • Add explicit Linux template examples (e.g., using Ubuntu image references) alongside the Windows ones.
  • Clarify that Azure CLI commands work cross-platform and consider providing Bash shell script examples where appropriate.
  • Balance PowerShell examples with equivalent Bash or shell script snippets for Linux/macOS users.
  • In ARM template examples, show both Windows and Linux imageReference blocks or note how to adapt for Linux.
  • Mention that PowerShell Core is cross-platform, or clarify when examples are Windows-only.
GitHub Create Pull Request
Virtual Machines Azure boot diagnostics ...lob/main/articles/virtual-machines/boot-diagnostics.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 🔧 Windows Tools
Summary
The documentation provides both Linux and Windows coverage in its scope and screenshots, but there is a subtle Windows bias. PowerShell is given its own section for enabling boot diagnostics, while the CLI section is not explicitly labeled as 'Linux' or 'cross-platform'. References to troubleshooting and configuration (such as the Serial Console link) point to Windows-specific documentation first. Windows screenshot is shown after Linux, but the overall pattern prioritizes Windows tools and workflows (PowerShell, Windows-centric links) over Linux equivalents.
Recommendations
  • Explicitly label the Azure CLI section as cross-platform and highlight its use for Linux/macOS users.
  • Provide Bash or shell script examples alongside PowerShell for enabling boot diagnostics.
  • Ensure links to troubleshooting guides include both Linux and Windows versions, or point to neutral, cross-platform resources.
  • Add a section or note on using boot diagnostics from Linux/macOS environments, including relevant tools and commands.
  • Avoid referencing Windows-specific documentation (e.g., Serial Console) before Linux equivalents.
GitHub Create Pull Request
Virtual Machines Configure VM watch ...b/main/articles/virtual-machines/configure-vm-watch.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 ARM templates, Azure CLI, and PowerShell, with PowerShell (a Windows-centric tool) given its own section and example. While the CLI example is cross-platform, the PowerShell example is Windows-specific and is presented alongside CLI rather than, for example, Bash or shell scripting for Linux. The documentation refers to Visual Studio Code as an IDE, which is cross-platform, but does not mention Linux-specific editors or tools. The instructions for the <application health extension type> do clarify the difference between Windows and Linux, but the overall pattern is to present Windows/PowerShell options as primary.
Recommendations
  • Add explicit Bash or shell scripting examples for Linux users alongside PowerShell.
  • Ensure that CLI examples highlight Linux/macOS compatibility.
  • Mention Linux-native editors (e.g., Vim, Nano) as alternatives to Visual Studio Code.
  • Where PowerShell is referenced, clarify its availability on Linux/macOS or provide alternative commands.
  • Consider ordering examples so that cross-platform or Linux options are presented before or equally with Windows/PowerShell.
GitHub Create Pull Request
Virtual Machines Automatic Extension Upgrade for VMs and scale sets in Azure ...ticles/virtual-machines/automatic-extension-upgrade.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 Missing Linux Example 🔧 Windows Tools
Summary
The documentation exhibits a moderate Windows bias. In code examples for enabling Automatic Extension Upgrade, the 'DependencyAgentWindows' extension type is used in REST, PowerShell, and ARM template samples, while the CLI examples use 'DependencyAgentLinux'. PowerShell examples are provided, but no Bash or Linux shell script equivalents are shown. Windows extension types are shown first in most code blocks, and PowerShell is presented as the only scripting option. There is no explicit mention of Linux-specific considerations or troubleshooting, and Windows-centric tools (PowerShell) are featured without Linux alternatives.
Recommendations
  • Provide parallel examples for both Windows and Linux extension types in all code blocks (REST, PowerShell, CLI, ARM templates), e.g., show both 'DependencyAgentWindows' and 'DependencyAgentLinux' in each section.
  • Include Bash or shell script examples for Linux users, especially in scripting sections.
  • Add explicit notes or troubleshooting tips for Linux users where extension behavior may differ.
  • When listing supported extensions, alternate the order or group by OS to avoid Windows-first presentation.
  • Mention Linux-native tools or commands where relevant, not just PowerShell.
GitHub Create Pull Request
Virtual Machines Automatic Guest Patching for Azure Virtual Machines and Scale Sets ...ticles/virtual-machines/automatic-vm-guest-patching.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 extensive coverage for both Windows and Linux VMs, but there is a notable Windows bias in several areas. Windows examples (especially PowerShell and CLI) are more detailed and appear first, with Linux examples often missing or less emphasized. PowerShell commands are provided only for Windows, and Windows-specific tools and registry keys are discussed in detail, while Linux equivalents are less prominent or omitted. The 'Next steps' section links only to Windows VM management.
Recommendations
  • Provide Linux-specific PowerShell/CLI examples where possible, especially in sections where only Windows commands are shown.
  • Ensure Linux examples are presented alongside Windows examples, not after or omitted.
  • Add links to Linux VM management tutorials in the 'Next steps' section.
  • Balance the discussion of OS-specific tools and configuration (e.g., registry keys for Windows, systemd/services for Linux).
  • Where Windows-specific behaviors or limitations are described, include equivalent Linux details or explicitly state differences.
GitHub Create Pull Request
Virtual Machines Azure VM Watch .../blob/main/articles/virtual-machines/azure-vm-watch.md
Medium Priority View Details →
Scanned: 2026-01-14 01:31
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page for Azure VM Watch demonstrates some Windows bias. Several health signals and checks are Windows-specific (e.g., System Errors from Windows event log, Hardware Health Monitor from Windows event log, and fallback to w32tm for clock sync on Windows). Windows tools and patterns (event log, w32tm) are mentioned explicitly, while Linux equivalents are not described or referenced. In some cases, Linux-only metrics are called out, but Windows-only checks are more prevalent and described with more detail. There are no explicit Linux command or tool references (e.g., journalctl, systemd, ntpd), and Windows-specific fallback mechanisms are described without Linux parity.
Recommendations
  • Add Linux equivalents for Windows-specific checks, such as describing how system errors can be collected from Linux logs (e.g., journalctl, /var/log/syslog).
  • Provide Linux-specific fallback mechanisms for clock sync checks (e.g., ntpd, chrony status commands) similar to the Windows w32tm fallback.
  • Balance the documentation by mentioning Linux tools and commands where Windows tools are referenced.
  • Include example commands or references for both platforms when describing health checks or troubleshooting steps.
  • Clarify which signals are platform-specific and provide parity where possible.
GitHub Create Pull Request
Virtual Machines Overview backup options for VMs ...blob/main/articles/virtual-machines/backup-recovery.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 generally presents backup options in a platform-neutral way, but there is a notable bias in the 'Managed snapshots' section: the only example link provided is for Windows ('Create copy of VHD stored as a Managed Disk'), with no equivalent Linux example or mention. This may cause friction for Linux users seeking parity in snapshot operations.
Recommendations
  • Add a Linux-specific example or documentation link for creating managed disk snapshots (e.g., 'Create copy of VHD stored as a Managed Disk on Linux').
  • Ensure that example links and walkthroughs are provided for both Windows and Linux platforms, or clarify when procedures are identical.
  • Review other sections for subtle platform prioritization and explicitly mention Linux support where relevant.
GitHub Create Pull Request
Virtual Machines Associate a virtual machine scale set with Uniform Orchestration to a capacity reservation group. ...pacity-reservation-associate-virtual-machine-scale-set.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 🔧 Windows Tools
Summary
The documentation page exhibits moderate Windows bias, particularly in the ARM template section, which is heavily oriented toward Windows VM deployment (Windows OS images, PowerShell DSC, Windows-specific artifacts). PowerShell examples are provided alongside CLI, but Linux-specific scripting or configuration is not addressed. The ARM template parameters and variables default to Windows-centric values and tooling, with no parallel Linux example or guidance. The CLI examples do use Ubuntu images, but the template and scripting guidance are Windows-first.
Recommendations
  • Add ARM template examples and parameters for Linux VM images (e.g., Ubuntu, CentOS) alongside Windows examples.
  • Include Linux-specific configuration options (such as cloud-init or custom script extensions) in ARM templates.
  • Balance PowerShell examples with Bash or shell scripting examples for Linux/macOS users.
  • Clarify in the documentation that both Windows and Linux VMs are supported, and provide explicit guidance for Linux deployments.
  • Provide links to Linux VM scale set quickstarts or reference architectures.
GitHub Create Pull Request
← Previous Page 6 of 33 Next →