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 276-300 of 818 flagged pages
Virtual Machines Create Virtual Machine restore points ...ain/articles/virtual-machines/create-restore-points.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
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 a moderate Windows bias. Windows-specific features (application consistency) are mentioned before Linux equivalents (file system consistency). PowerShell is referenced multiple times, both in the main text and in the 'Next steps' section, with no equivalent Bash or Linux CLI examples. The only tool specifically linked for scripting is PowerShell, and there are no Linux/macOS shell or CLI examples provided, nor is the Azure CLI highlighted equally. This creates friction for Linux/macOS users who may prefer Bash or cross-platform tools.
Recommendations
  • Add Azure CLI examples and links alongside PowerShell references.
  • Explicitly mention Linux/macOS compatibility and provide Bash or shell script examples where possible.
  • Ensure that references to scripting tools (PowerShell, CLI) are presented in parallel, not with PowerShell first or exclusively.
  • Highlight Linux-specific features and parity, such as file system consistency, with equal prominence as Windows features.
  • Include a section or note on how Linux users can perform these tasks using their preferred tools.
GitHub Create Pull Request
Virtual Machines Delete a VM and attached resources ...ute-docs/blob/main/articles/virtual-machines/delete.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation provides examples for Azure Portal, CLI, PowerShell, and REST API, but PowerShell (a Windows-centric tool) is given equal prominence to CLI, and is detailed throughout. REST API examples use Windows-centric values (e.g., Windows images, Windows-specific OS types). There is no explicit Linux/macOS shell scripting example (e.g., Bash), nor are Linux-specific considerations or patterns discussed. The FAQ and general guidance do not mention Linux-specific behaviors, and the only reference to Linux is a link in 'Next steps', which is not integrated into the main content.
Recommendations
  • Add explicit Bash examples for Linux/macOS users, especially for scripting VM deletion and resource cleanup.
  • In REST API examples, alternate between Windows and Linux VM configurations, or provide both.
  • Clarify that CLI commands work cross-platform and highlight any OS-specific differences.
  • Balance PowerShell and CLI coverage, and consider moving PowerShell examples after CLI/Bash to reduce Windows-first perception.
  • In the FAQ and general guidance, mention any Linux-specific considerations (e.g., differences in VM images, OS disk handling).
GitHub Create Pull Request
Virtual Machines Copy a snapshot to a new region ...ines/disks-copy-incremental-snapshot-across-regions.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
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 (cross-platform) and Azure PowerShell (Windows-centric) examples for copying snapshots, but the PowerShell section is detailed and includes installation instructions, while the CLI section assumes familiarity. There are no explicit Linux/macOS shell script examples, nor is there mention of Linux-specific considerations. The .NET sample code referenced is also Windows-oriented. The ordering of examples places Azure CLI first, but the PowerShell section is more verbose and instructional.
Recommendations
  • Add explicit Bash/Linux/macOS shell script examples for Azure CLI usage, including environment setup and authentication steps.
  • Include notes on cross-platform compatibility for all CLI commands, clarifying that Azure CLI works natively on Linux/macOS.
  • Provide sample code or links for Linux/macOS automation (e.g., Bash scripts, Python) for the manual copy process.
  • Reference cross-platform SDKs (e.g., Python, Java) in addition to .NET for sample code.
  • Balance instructional detail between PowerShell and CLI sections, ensuring Linux/macOS users have equal guidance.
GitHub Create Pull Request
Virtual Machines Migrate from Azure Disk Encryption to encryption at host ...n/articles/virtual-machines/disk-encryption-migrate.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation generally provides both Windows and Linux guidance, but there are several signs of Windows bias. Windows examples and considerations are often listed first, and PowerShell/Windows-specific tools are more prominently featured. Some sections, especially around domain-joined VM migration and disk operations, provide more detailed or explicit steps for Windows than for Linux. There are also places where Linux instructions are less detailed or refer users to external links for critical steps, while Windows instructions are more self-contained.
Recommendations
  • Alternate the order of Windows and Linux instructions to avoid always presenting Windows first.
  • Provide equally detailed, step-by-step Linux examples for all major operations, especially for domain join/removal and disk migration.
  • Where PowerShell is used for Windows, provide Bash or native Linux command alternatives for Linux users, not just Azure CLI.
  • Expand Linux-specific troubleshooting and verification steps to match the depth provided for Windows.
  • Ensure all sections (e.g., domain join, disk verification) have clear, in-place Linux examples rather than referring out to other docs.
  • Where possible, use cross-platform tools (like Azure CLI) as the primary example, and supplement with OS-specific tools as needed.
GitHub Create Pull Request
Virtual Machines Deploy a Premium SSD v2 managed disk ...n/articles/virtual-machines/disks-deploy-premium-v2.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation exhibits a moderate Windows bias. VM creation examples in both Azure CLI and PowerShell use Windows images (Win2016Datacenter) and Windows-centric parameters (adminPassword, adminUserName), with no Linux VM examples or Linux-specific configuration guidance. PowerShell examples (a Windows-only tool) are given equal prominence to Azure CLI, and in some cases, Windows patterns (like credential handling) are shown without Linux equivalents. There are no explicit Linux VM deployment examples, and the documentation does not mention Linux-specific considerations for disk attachment or sector size compatibility.
Recommendations
  • Add Linux VM deployment examples in both Azure CLI and PowerShell sections, using popular Linux images (e.g., UbuntuLTS, CentOS).
  • Include Linux-specific parameters and authentication patterns (e.g., SSH keys instead of passwords) in CLI examples.
  • Discuss any Linux-specific considerations for disk attachment, sector size, and compatibility.
  • Clarify that PowerShell is Windows-only and suggest cross-platform alternatives where appropriate.
  • Ensure Linux and Windows examples are presented with equal prominence, or alternate which is shown first.
GitHub Create Pull Request
Virtual Machines Enable on-demand disk bursting ...ain/articles/virtual-machines/disks-enable-bursting.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page provides detailed examples for enabling on-demand disk bursting using the Azure Portal, Azure PowerShell, Azure CLI, and ARM templates. PowerShell examples (a Windows-centric tool) are given prominent coverage and are mentioned before Azure CLI, which is more cross-platform. There is no mention of Linux-specific shell scripting or guidance for Linux/macOS users, and the use of PowerShell and references to Windows tools may create friction for non-Windows users.
Recommendations
  • Add explicit Bash shell examples for Linux/macOS users, especially for scripting with Azure CLI.
  • Reorder example sections to present Azure CLI before PowerShell, as CLI is cross-platform.
  • Clarify that Azure CLI commands work natively on Linux/macOS and provide installation links for those platforms.
  • Avoid referring to PowerShell as the primary scripting method; instead, present it as one of several options.
  • Include notes or tips for Linux/macOS users where workflows or prerequisites may differ.
GitHub Create Pull Request
Virtual Machines Deploy a ZRS managed disk ...lob/main/articles/virtual-machines/disks-deploy-zrs.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
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 notable Windows bias. PowerShell and Windows-centric tools (e.g., Register-AzProviderFeature, ConvertTo-SecureString) are used extensively, especially in the Resource Manager Template and PowerShell tabs. Windows VM images are the default in PowerShell examples, and Windows-specific configuration (e.g., -Windows flag, WindowsServer images) is shown without Linux alternatives. Feature registration and deployment steps are only shown with PowerShell, with no Bash/Azure CLI equivalent. The Azure CLI examples use Ubuntu images, but the PowerShell and ARM template examples are Windows-only. There are no Linux/macOS-specific instructions for feature registration or template deployment.
Recommendations
  • Provide Bash/Azure CLI equivalents for feature registration and template deployment steps.
  • Include Linux VM image examples in PowerShell and Resource Manager Template sections, or show both Windows and Linux options.
  • Avoid using Windows-specific flags (e.g., -Windows) without mentioning Linux alternatives.
  • Add notes or examples for macOS/Linux users where PowerShell commands are required, or reference cross-platform tools.
  • Ensure all critical steps (e.g., feature registration) have platform-neutral or cross-platform instructions.
GitHub Create Pull Request
Virtual Machines Convert a disk from LRS to ZRS ...ain/articles/virtual-machines/disks-migrate-lrs-zrs.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation page presents examples and instructions for Azure Portal, Azure PowerShell, and Azure CLI. While Azure CLI is cross-platform, the ordering consistently places Azure PowerShell (a Windows-centric tool) before CLI, and there is a notable absence of explicit Linux/macOS shell examples (e.g., bash, zsh). References to disk deletion link to a Windows-specific page. The documentation does not mention Linux/macOS-specific considerations, nor does it provide parity in example ordering or tool recommendations.
Recommendations
  • Present Azure CLI examples before Azure PowerShell, as CLI is cross-platform and more accessible to Linux/macOS users.
  • Include explicit bash/zsh shell examples where variable assignment or command chaining is shown, to clarify syntax differences for Linux/macOS users.
  • Replace or supplement links to Windows-specific documentation (e.g., disk deletion) with platform-neutral or Linux/macOS equivalents.
  • Add notes clarifying that Azure CLI works on Linux/macOS and provide installation links for those platforms.
  • Where PowerShell is referenced, clarify that PowerShell Core is available cross-platform, or recommend CLI for Linux/macOS users.
GitHub Create Pull Request
Virtual Machines Enable shared disks for Azure managed disks .../main/articles/virtual-machines/disks-shared-enable.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
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 disk types and operations, but PowerShell (a Windows-centric tool) is given equal prominence to Azure CLI, and in some sections (such as 'Share an existing disk' and 'Using Azure shared disks with your VMs'), PowerShell examples are listed first. There are no Linux-specific shell examples (e.g., Bash), nor are there any notes about Linux-specific considerations or parity for command-line usage. The documentation assumes PowerShell is equally available to all users, which is not the case for many Linux/macOS environments.
Recommendations
  • List Azure CLI examples before PowerShell, as CLI is cross-platform and native to Linux/macOS.
  • Add explicit Bash shell examples for common operations, especially for mounting disks to VMs.
  • Include notes or links about installing and using Azure PowerShell on Linux/macOS, or clarify when PowerShell is required.
  • Provide Linux-specific guidance for post-attach steps (e.g., mounting disks, SCSI PR usage) where relevant.
  • Ensure screenshots and portal instructions do not assume Windows conventions (e.g., file paths, UI terminology).
GitHub Create Pull Request
Virtual Machines Create an incremental snapshot ...ticles/virtual-machines/disks-incremental-snapshots.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
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 for all major operations. However, PowerShell examples are given equal prominence and detail as CLI, and in some sections, PowerShell is presented before or alongside CLI without clarifying platform relevance. There are no Linux-specific shell examples (e.g., Bash), and no mention of Linux-native tools or patterns. The documentation does not explicitly favor Windows-only tools, but the heavy inclusion of PowerShell may create friction for Linux/macOS users.
Recommendations
  • Clarify that Azure PowerShell is primarily for Windows users, and recommend CLI for Linux/macOS.
  • Present Azure CLI examples first in each section, as it is cross-platform.
  • Add explicit Bash script examples where appropriate, especially for Linux users.
  • Include notes on platform compatibility for each tool (CLI, PowerShell, Portal).
  • Consider adding troubleshooting or usage notes for Linux/macOS environments.
GitHub Create Pull Request
Virtual Machines Instantly access managed disk snapshots ...les/virtual-machines/disks-instant-access-snapshots.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation provides examples for Azure CLI, Azure PowerShell, Azure Portal, and Resource Manager templates, but omits explicit Linux/macOS shell examples and does not mention Linux-specific tools or workflows. PowerShell examples are given equal prominence to CLI, and Windows-centric terminology (PowerShell, Portal) is used throughout. No bash-specific or Linux-native scripting guidance is provided, and Windows/PowerShell examples are not clearly marked as Windows-only.
Recommendations
  • Add explicit bash/Linux shell examples for all CLI commands, including variable declarations and usage.
  • Clarify that PowerShell examples are for Windows users, and provide equivalent bash scripts for Linux/macOS.
  • Mention Linux-native tools (e.g., curl, jq) where relevant for API or data inspection.
  • Ensure that CLI examples use cross-platform syntax and note any OS-specific differences.
  • Add a section or note on how Linux/macOS users can perform snapshot operations, including troubleshooting tips for those platforms.
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-13 06:17
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation page exhibits a moderate Windows bias. Windows clustering tools (WSFC) and workloads are described first and in greater detail, with specific references to Windows features (CSV, Scale-Out File Server, RDS UPD) and links to Windows-centric guides. Linux equivalents are mentioned, but with less detail and fewer concrete examples. Windows sample workloads are listed before Linux, and the examples section provides more detailed Windows scenarios (including CSV/non-CSV) versus a single Linux example. No command-line examples (e.g., PowerShell or Bash) are present, but Windows tools and patterns are referenced more prominently.
Recommendations
  • Provide Linux sample workloads with equal detail and specificity, including links to step-by-step guides for setting up Pacemaker/Corosync clusters with Azure shared disks.
  • Add concrete Linux configuration examples, such as using sg_persist or fence_scsi, and reference Linux-specific clustering patterns (e.g., OCFS2/GFS2 setup).
  • Present Windows and Linux sample workloads in parallel, or alternate their order to avoid Windows-first bias.
  • Include Linux/macOS command-line examples for disk management and reservation flows, not just Windows tools.
  • Reference Linux documentation and templates as prominently as Windows equivalents.
GitHub Create Pull Request
Virtual Machines Ephemeral OS disks ...b/main/articles/virtual-machines/ephemeral-os-disks.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. Windows-specific details (such as page file placement and image sizing) are often mentioned before Linux equivalents. PowerShell is referenced before CLI in the customer-managed key section, and some links point to Windows/PowerShell docs first. There are more detailed examples for Windows (e.g., cache sizing), while Linux examples are less emphasized or absent. The documentation does mention Linux support and provides some Linux-specific information, but parity in examples and tool references is lacking.
Recommendations
  • Provide Linux examples alongside Windows examples, especially in sections discussing image sizing and disk placement.
  • When referencing tools for configuration (e.g., enabling customer-managed keys), mention Azure CLI and PowerShell together, or list CLI first for neutrality.
  • Ensure that Linux-specific details (such as swap file placement, common distributions, or image sizes) are given equal prominence.
  • Add explicit Linux walkthroughs or code snippets where only Windows/PowerShell is currently referenced.
  • Review all links to ensure Linux and Windows documentation are equally accessible.
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-13 06:17
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation is generally cross-platform, focusing on Azure Storage Explorer, which is available for Windows, Linux, and macOS. However, the 'Next steps' section exclusively links to Windows VM guides, and there are no Linux-specific follow-up links or examples. There is also no mention of Linux-specific considerations or parity in workflows, which may leave Linux users without clear guidance for subsequent steps.
Recommendations
  • Add Linux-specific links in the 'Next steps' section, such as guides for creating VMs from VHDs or attaching managed disks to Linux VMs.
  • Ensure parity by including references to both Windows and Linux workflows wherever relevant, especially in follow-up resources.
  • Explicitly mention that Azure Storage Explorer is available on Linux/macOS and provide installation instructions or links for those platforms.
  • If there are any platform-specific behaviors or requirements (e.g., file paths, permissions), document these for Linux/macOS users.
GitHub Create Pull Request
Virtual Machines Azure Backup for SQL Server running in Azure VM ...extensions/backup-azure-sql-server-running-azure-vm.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation page exhibits a notable Windows bias. The extension discussed is named AzureBackupWindowsWorkload, with no mention of a Linux equivalent or support for SQL Server on Linux VMs. All deployment and registration instructions use PowerShell and Windows-centric tooling, with no CLI, Bash, or Linux-native examples. The documentation does not clarify whether Linux VMs or SQL Server on Linux are supported, nor does it provide guidance for non-Windows environments.
Recommendations
  • Clarify whether Azure Backup supports SQL Server running on Linux VMs, and if so, document the process and any required extensions.
  • Provide Azure CLI, Bash, or REST API examples for registering and managing backups, alongside PowerShell.
  • If Linux is not supported, explicitly state this in the prerequisites or introduction.
  • If Linux is supported, add equivalent instructions and examples for Linux users, including any differences in extension names or deployment steps.
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-13 06:17
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing Windows tools and patterns first, such as PowerShell scripts and the BGInfo extension. The sample deployment scripts are described as 'PowerShell and Azure CLI scripts', listing PowerShell first and not mentioning Bash or Linux shell scripts. The supported extensions list places Windows extensions before Linux equivalents in several cases. There are no explicit Linux/macOS command-line examples, and the documentation does not provide parity for Linux users in terms of deployment or scripting guidance.
Recommendations
  • List Azure CLI and Bash examples before or alongside PowerShell, and clarify cross-platform usage.
  • Explicitly mention Linux/macOS compatibility for export and deployment steps.
  • Provide sample Bash or shell scripts for template deployment, not just PowerShell.
  • Ensure supported extensions are listed in a neutral or alphabetical order, not Windows-first.
  • Add a section or note for Linux/macOS users on how to perform the export and deployment steps.
  • Reference Linux tools and patterns where relevant, such as using Azure CLI in Bash.
GitHub Create Pull Request
Virtual Machines Use Azure Policy to restrict VM extension installation (Windows) ...al-machines/extensions/extensions-rmpolicy-howto-ps.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation is heavily focused on Windows environments, using Azure PowerShell and Windows-specific paths and examples throughout. There are no Linux or Bash examples, and all instructions assume the user is working with Windows VMs and PowerShell, both in Cloud Shell and locally. The page title and customer intent reinforce a Windows-centric approach, and there is no mention of Linux VM extension management or equivalent CLI commands.
Recommendations
  • Add equivalent examples for Linux VMs, including how to restrict extensions on Linux VMs using Azure Policy.
  • Provide Azure CLI (az) and Bash examples alongside PowerShell, especially for policy creation, assignment, and testing.
  • Clarify which steps are universal and which are Windows-specific; add notes or sections for Linux/macOS users.
  • Include Linux file path examples and instructions for editing files in Linux environments.
  • Update the page title and customer intent to reflect cross-platform applicability if the policy applies to both Windows and Linux VMs.
GitHub Create Pull Request
Virtual Machines Enable InfiniBand on HPC VMs - Azure Virtual Machines | Microsoft Docs ...icles/virtual-machines/extensions/enable-infiniband.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation provides both Linux and Windows instructions for enabling InfiniBand, but there is a notable Windows bias in several areas. The use of Azure PowerShell cmdlets is mentioned as the primary method for adding VM extensions, with no equivalent CLI or Linux-native tooling referenced. Windows-specific tools and extensions are described in greater detail, and the Windows installation section, while brief, is present. In the VM extension section, Windows is discussed first and at greater length than Linux. However, Linux examples are present and detailed, especially for manual driver installation.
Recommendations
  • Include Azure CLI examples for adding VM extensions, especially for Linux users.
  • Mention Linux-native tools (e.g., cloud-init, shell scripts) for extension management alongside PowerShell.
  • Balance the order and detail of Windows and Linux instructions, presenting Linux examples first or in parallel.
  • Provide more detailed Windows installation steps, or link to equivalent Linux installation guides for parity.
GitHub Create Pull Request
Virtual Machines Azure VM Extensions and Features for Linux ...articles/virtual-machines/extensions/features-linux.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation is generally focused on Linux VM extensions, but there is a consistent pattern of presenting both Azure CLI and Azure PowerShell examples side-by-side, with PowerShell (a Windows-centric tool) given equal prominence. In some cases, links and references point to Windows documentation first (e.g., ARM template reference). There are no explicit Linux shell or native Linux tool examples beyond Azure CLI, and PowerShell is not natively available on most Linux distributions. The documentation does not provide guidance for Linux-native workflows outside Azure CLI and ARM templates.
Recommendations
  • Prioritize Azure CLI examples, as it is cross-platform and more commonly used on Linux.
  • Provide native Bash or shell script examples where possible, especially for troubleshooting and automation tasks.
  • Avoid referencing Windows documentation (such as ARM template docs under Windows) when describing Linux workflows; link to Linux-specific docs instead.
  • Clarify that PowerShell is optional and not required for Linux users, and provide alternatives.
  • Add troubleshooting steps using native Linux tools (e.g., journalctl, systemctl) in addition to Azure CLI.
  • Ensure that all example outputs and screenshots are from Linux environments.
GitHub Create Pull Request
Virtual Machines Salt Minion for Linux or Windows Azure VMs ...in/articles/virtual-machines/extensions/salt-minion.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Linux First Linux Examples Only Missing Windows Example
Summary
The documentation page demonstrates a bias towards Linux by providing detailed examples for Linux VM extension installation using ARM templates and Terraform, while omitting equivalent examples for Windows. The Azure CLI section does mention both Linux and Windows, but the ARM template and Terraform sections only show Linux usage. There is no evidence of Windows tools or PowerShell-specific instructions, and Linux is consistently presented first.
Recommendations
  • Add ARM template examples for installing the Salt Minion extension on Windows VMs (using 'salt-minion.windows').
  • Include Terraform resource examples for Windows VM extensions, mirroring the Linux example.
  • Ensure both Linux and Windows are equally represented in all code samples and instructions.
  • Consider alternating the order of examples or grouping them by OS for parity.
GitHub Create Pull Request
Virtual Machines Troubleshooting Windows VM extension failures ...n/articles/virtual-machines/extensions/troubleshoot.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation is heavily focused on Windows VM extension troubleshooting, with most examples, error messages, and solutions tailored to Windows environments. PowerShell commands and Windows-specific tools (Task Manager, Control Panel, certmgr.msc) are used exclusively or presented first, while Linux troubleshooting steps and examples are minimal or absent. Linux users may find it difficult to follow some procedures due to lack of equivalent instructions.
Recommendations
  • Add Linux-specific troubleshooting examples and commands (e.g., using Bash, systemctl, journalctl, etc.) alongside PowerShell examples.
  • Present Azure CLI commands before or alongside PowerShell to ensure cross-platform parity.
  • Include Linux error messages and log file locations with sample outputs.
  • Provide Linux equivalents for Windows tools (e.g., how to restart the Linux Guest Agent, check environment variables, manage certificates).
  • Clearly separate Windows and Linux instructions, or provide parallel sections for each OS.
GitHub Create Pull Request
Virtual Machines Azure FPGA Attestation Service ...machines/field-programmable-gate-arrays-attestation.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation provides both PowerShell and Bash examples for running attestation scripts, but the PowerShell example is presented first and is more detailed. Monitoring attestation status is only described using a PowerShell script, with no equivalent Bash or Linux-native example. The documentation references PowerShell scripts and tools more frequently, and some steps (like monitoring) lack Linux-specific guidance.
Recommendations
  • Provide Bash or Linux-native examples for monitoring attestation status, similar to the PowerShell Monitor-Validation.ps1 script.
  • Present Bash and PowerShell examples side-by-side or alternate which is shown first to avoid implicit prioritization.
  • Clarify that all scripts and tools are cross-platform where applicable, and explicitly mention Linux/macOS compatibility for each step.
  • If a Bash/Linux script for monitoring does not exist, provide instructions for using the HTTP endpoint from Bash (e.g., using curl or httpie) to check status.
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-13 06:17
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page shows a subtle Windows bias by referencing Windows-specific scheduled events documentation and linking to activity log tabs that default to PowerShell (a Windows-centric tool). There is no explicit mention of Linux or macOS equivalents, nor are Linux-specific examples or guidance provided. The scheduled events link points to a Windows documentation page, and activity log examples default to PowerShell, with no clear parity for Linux users.
Recommendations
  • Include links to both Windows and Linux scheduled events documentation, or clarify applicability to all platforms.
  • Provide Linux/macOS command-line examples (e.g., Azure CLI, Bash) alongside PowerShell examples for activity logs and other monitoring tasks.
  • Explicitly mention platform support for each monitoring solution and clarify any differences in implementation or usage between Windows and Linux VMs.
  • Ensure that documentation navigation (tabs, links) does not default to Windows tools, but offers equal visibility for Linux/macOS options.
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-13 06:17
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation exhibits a moderate Windows bias. Windows examples and PowerShell commands are presented before Linux equivalents, and Windows-centric tools (PowerShell, WindowsServer SKUs) are referenced more frequently and in greater detail. Linux instructions are present but often less detailed or appear after Windows examples. Some advanced tasks (e.g., bringing a .vhd from on-premises) are only shown with Windows PowerShell, with no Linux CLI or Bash equivalent.
Recommendations
  • Provide Linux/Bash/Azure CLI examples alongside PowerShell for all major workflows, especially for importing .vhd files and setting VM properties.
  • Ensure Linux images and instructions are presented with equal prominence and detail as Windows examples.
  • Where PowerShell is used, offer equivalent Azure CLI or Bash commands for Linux/macOS users.
  • Explicitly mention Linux-specific considerations or differences in advanced scenarios (e.g., disk import, managed disk creation).
  • Balance the order of examples so Linux and Windows are alternated or grouped, rather than consistently leading with Windows.
GitHub Create Pull Request
Virtual Machines Azure Write Accelerator ...es/virtual-machines/how-to-enable-write-accelerator.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page exhibits a moderate Windows bias. The PowerShell method is presented first and in greatest detail, with multiple example scripts and cmdlet explanations. Windows-specific tooling (Chocolatey, cmd.exe, PowerShell) is referenced exclusively for installing armclient, with no mention of Linux/macOS alternatives. While Azure CLI and REST API methods are included, the CLI section is brief and the REST API instructions assume Windows environments for installation. There are no Linux/macOS-specific command-line examples or installation instructions for armclient.
Recommendations
  • Provide Linux/macOS installation instructions for armclient (e.g., via dotnet, npm, or manual download).
  • Include Bash shell examples for Azure CLI usage, showing Linux/macOS command syntax.
  • Present Azure CLI examples before PowerShell, or in parallel, to avoid Windows-first ordering.
  • Clarify that PowerShell cmdlets can be run on Linux/macOS via PowerShell Core, if applicable.
  • Add notes or examples for Linux disk/volume managers (LVM, MDADM) in scripting sections.
  • Ensure all tooling references (e.g., Chocolatey) have cross-platform alternatives or links.
GitHub Create Pull Request
← Previous Page 12 of 33 Next →