Virtual Machines

1080
Total Pages
1005
Linux-Friendly Pages
75
Pages with Bias
6.9%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

815 issues found
Showing 276-300 of 815 flagged pages
Virtual Machines Create a VM from a generalized image in a gallery ...icles/virtual-machines/vm-generalized-image-version.md
Medium Priority View Details →
Scanned: 2026-01-24 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides both CLI and PowerShell examples for creating VMs from generalized images in an Azure Compute Gallery. However, the PowerShell examples are exclusively for Windows, with commands like Set-AzVMOperatingSystem -Windows and prompts for Windows credentials. There are no PowerShell examples for Linux VM creation, nor guidance for Linux-specific PowerShell usage. In CLI and REST sections, Linux is shown first, but PowerShell sections always default to Windows. This creates friction for Linux users who prefer PowerShell or need parity in automation scripts.
Recommendations
  • Add PowerShell examples for creating Linux VMs, using Set-AzVMOperatingSystem -Linux and appropriate credential handling.
  • Explicitly mention how to adapt PowerShell scripts for Linux VM creation, including SSH key configuration and Linux-specific parameters.
  • Ensure that both Windows and Linux scenarios are covered equally in PowerShell sections, similar to the parity shown in CLI and REST examples.
  • Consider adding a table or note summarizing differences in PowerShell usage for Windows vs. Linux VM creation.
GitHub Create Pull Request
Virtual Machines Create a VM from a specialized image version ...icles/virtual-machines/vm-specialized-image-version.md
Medium Priority View Details →
Scanned: 2026-01-24 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides both Azure CLI and PowerShell examples for creating VMs from specialized images, but the PowerShell examples are significantly more detailed and complex, including full network setup and VM configuration. CLI examples are much shorter and do not cover equivalent steps. PowerShell is a Windows-centric tool, and the lack of parity in example depth may disadvantage Linux/macOS users who rely on CLI or other scripting environments. Additionally, PowerShell examples are presented in every scenario, and in some sections, the PowerShell tab appears before CLI, reinforcing a Windows-first pattern. There are no Bash or Linux-native scripting examples for advanced scenarios.
Recommendations
  • Expand Azure CLI examples to include full VM creation workflows, including network setup and configuration, matching the detail of PowerShell examples.
  • Add Bash shell script examples for Linux/macOS users, especially for advanced scenarios.
  • Ensure CLI examples are presented before or alongside PowerShell examples to avoid a Windows-first impression.
  • Explicitly mention that PowerShell examples are primarily for Windows users and suggest CLI/Bash alternatives for Linux/macOS users.
GitHub Create Pull Request
Virtual Machines Create a VM from a generalized image in a gallery ...icles/virtual-machines/vm-generalized-image-version.md
Medium Priority View Details →
Scanned: 2026-01-23 00:00
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 creating VMs from generalized images in an Azure Compute Gallery. However, PowerShell examples are heavily Windows-centric, with explicit use of Windows-specific parameters (e.g., Set-AzVMOperatingSystem -Windows) and RDP-related networking rules. In several PowerShell code blocks, only Windows VM creation is shown, while Linux VM creation is not addressed. Additionally, PowerShell examples appear before REST and Portal instructions, and often before CLI in some sections, which may reinforce a Windows-first perspective. CLI and REST examples do include Linux scenarios, but PowerShell is presented as the default for Windows, with no Linux PowerShell parity.
Recommendations
  • Add PowerShell examples for creating Linux VMs, using Set-AzVMOperatingSystem -Linux and appropriate credential handling.
  • In PowerShell networking examples, show how to open SSH (port 22) for Linux VMs, not just RDP (port 3389) for Windows.
  • Clearly label CLI and PowerShell examples as Linux or Windows, and provide both where possible.
  • Ensure that Linux scenarios are equally represented in PowerShell sections, not only in CLI/REST.
  • Consider alternating the order of CLI and PowerShell tabs, or defaulting to CLI (cross-platform) first.
GitHub Create Pull Request
Virtual Machines Create a VM from a specialized image version ...icles/virtual-machines/vm-specialized-image-version.md
Medium Priority View Details →
Scanned: 2026-01-23 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides both Azure CLI and PowerShell examples for creating VMs from specialized images, but the PowerShell examples are significantly more detailed and complex, including full network setup, while CLI examples are minimal. PowerShell is a Windows-centric tool, and there are no equivalent Linux shell (bash) or cross-platform scripting examples for the detailed VM/network configuration steps. In several sections, PowerShell examples are presented immediately after CLI, and the CLI examples are much shorter. There are no explicit Linux-specific command-line examples beyond Azure CLI, nor any mention of Linux-native tools or scripting patterns.
Recommendations
  • Provide detailed bash (Linux shell) scripting examples for VM and network resource creation, matching the depth of the PowerShell examples.
  • Clarify that Azure CLI is fully cross-platform and can be used on Linux/macOS, and offer sample scripts for those environments.
  • Where PowerShell is used for complex resource setup, offer equivalent Azure CLI commands or bash scripts to ensure Linux users can follow along without needing PowerShell.
  • Add notes or links to Linux/macOS-specific guidance for users who do not use PowerShell.
GitHub Create Pull Request
Virtual Machines Create and upload a CentOS-based Linux VHD ...rticles/virtual-machines/linux/create-upload-centos.md
Medium Priority View Details →
Scanned: 2026-01-21 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation for creating and uploading a CentOS-based Linux VHD to Azure exhibits a moderate Windows bias. Hyper-V (a Windows-only virtualization tool) is mentioned first and most prominently as the example for creating VHDs, with detailed steps referencing Hyper-V Manager for VM operations (connect, shut down). There is minimal mention of Linux-native alternatives (e.g., KVM, VirtualBox, VMware), and no step-by-step instructions for those platforms. Conversion to VHD format is described using Hyper-V Manager or PowerShell's convert-vhd cmdlet, with only a brief note about VirtualBox. This may create friction for Linux/macOS users who do not have access to Hyper-V or Windows tools.
Recommendations
  • Provide equivalent step-by-step instructions for creating and managing VHDs using Linux-native tools such as KVM, QEMU, or VirtualBox.
  • Include commands for converting disk formats using Linux utilities (e.g., qemu-img) alongside or before Windows/Hyper-V examples.
  • Add instructions for shutting down and managing VMs using Linux tools (e.g., virsh for KVM, VBoxManage for VirtualBox) instead of only referencing Hyper-V Manager.
  • Reorder examples so that Linux-native tools are presented first or in parallel with Windows tools.
  • Clarify that Hyper-V is only one option and not a requirement for Linux users.
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 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation provides both Windows and Linux extension support and mentions compatibility for both OS types. However, in critical example sections (REST API, PowerShell, ARM template), the extension type used is 'DependencyAgentWindows', and PowerShell examples are Windows-centric. Linux equivalents (e.g., 'DependencyAgentLinux') are only shown in CLI examples, and not in PowerShell or ARM template samples. The ordering of examples and extension types generally favors Windows first, which may create friction for Linux users seeking parity.
Recommendations
  • For each example (REST API, PowerShell, ARM template), provide both Windows and Linux extension type samples side-by-side or clearly indicate how to adapt for Linux (e.g., use 'DependencyAgentLinux').
  • In PowerShell sections, include Linux extension examples or clarify that PowerShell can be used for Linux VMs with the appropriate extension type.
  • In ARM template samples, show both 'DependencyAgentWindows' and 'DependencyAgentLinux' or add a note on how to switch between them.
  • Consider alternating the order of Windows and Linux examples, or grouping them together for clarity.
  • Explicitly state that all shown operations are equally applicable to Linux VMs/VMSS when the extension type is changed.
GitHub Create Pull Request
Virtual Machines Attach an existing OS disk to a VM .../blob/main/articles/virtual-machines/attach-os-disk.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page focuses exclusively on creating a new Windows VM by attaching an existing OS disk, with all command-line examples provided only in PowerShell. There are no Bash, Azure CLI, or Linux/macOS shell examples, nor is there any mention of Linux VM scenarios. The portal instructions are generic, but the command-line workflow is Windows-centric and omits Linux parity.
Recommendations
  • Add equivalent Azure CLI or Bash examples for attaching an OS disk to a Linux VM.
  • Clarify in the introduction whether the process is applicable to Linux VMs, or explicitly state if it is Windows-only.
  • If the process is supported for Linux VMs, provide Linux-specific notes (e.g., SSH access, disk attachment flags, OS type selection).
  • Ensure references to VM creation, disk attachment, and networking cover both Windows and Linux scenarios.
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 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation covers both Windows and Linux VMs for automatic guest patching, but there is a notable Windows bias in example ordering, tooling, and detail. PowerShell and Windows CLI examples are more detailed and appear first, while Linux-specific CLI and PowerShell examples are less prominent or missing. Windows tools and registry keys are discussed in detail, whereas Linux equivalents (such as disabling automatic updates) are mentioned briefly and without parity in example depth.
Recommendations
  • Provide Linux-specific PowerShell and CLI examples with equal detail and visibility as Windows examples.
  • Ensure that Linux examples (e.g., REST API, CLI, PowerShell) are presented alongside Windows examples, not after them.
  • Expand Linux tooling documentation, such as showing how to verify patching status, disable automatic updates, and manage patch modes using Linux-native tools.
  • Add parity in troubleshooting and operational guidance for Linux VMs, matching the depth given to Windows.
  • Consider alternating example order or grouping by OS to avoid Windows-first presentation.
GitHub Create Pull Request
Virtual Machines Associate a virtual machine to a capacity reservation group .../virtual-machines/capacity-reservation-associate-vm.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation provides parity for both Windows and Linux virtual machines in terms of supported features and CLI/API usage. However, there is a notable Windows bias in the ARM template section, which only demonstrates Windows VM image deployment and omits any Linux image example or parameter. Additionally, the PowerShell examples (a Windows-centric tool) are given equal prominence as CLI, but CLI examples do use Linux images. The order of examples sometimes places PowerShell before ARM template, and the ARM template itself is Windows-only, which may create friction for Linux users seeking infrastructure-as-code guidance.
Recommendations
  • Add a Linux VM ARM template example or include parameters for both Windows and Linux images in the ARM template section.
  • Clarify in the ARM template section that the example is for Windows and provide a link or guidance for Linux VM ARM template usage.
  • Consider alternating the order of CLI and PowerShell examples, or explicitly state that both are supported on Windows, macOS, and Linux (where applicable).
  • Ensure that infrastructure-as-code examples (ARM templates, Bicep, Terraform) demonstrate both Windows and Linux VM scenarios.
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 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation provides cross-platform instructions for associating a VM scale set with a capacity reservation group, including API, CLI, PowerShell, ARM template, and Portal methods. However, several sections—especially the ARM template example—are strongly Windows-centric, with parameters and variables focused exclusively on Windows Server images and PowerShell DSC/IIS deployment. There is no equivalent Linux-focused ARM template example, and Windows-specific deployment artifacts (PowerShell DSC, IIS) are referenced. PowerShell is given equal prominence to CLI, but CLI examples do use Ubuntu images, showing some Linux consideration. The ARM template and supporting text, however, assume Windows workloads by default.
Recommendations
  • Add a Linux-focused ARM template example, using a popular Linux image (e.g., Ubuntu) and removing Windows-specific parameters, variables, and deployment artifacts.
  • Provide guidance or links for deploying Linux workloads (e.g., using cloud-init or custom script extensions) in ARM templates.
  • Balance PowerShell and CLI coverage, ensuring CLI examples are not just present but also highlighted as the primary cross-platform method.
  • Clarify in the ARM template section that the example is for Windows workloads and offer a parallel Linux example.
  • Remove or generalize references to Windows-only deployment artifacts (PowerShell DSC, IIS, WebDeploy) in generic capacity reservation documentation.
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-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation provides both Azure CLI and PowerShell examples for deploying Premium SSD v2 managed disks, but all CLI and PowerShell code samples use Windows VM images (e.g., 'Win2016Datacenter') and Windows-centric authentication (username/password), with no Linux VM image or SSH authentication examples. This creates a subtle Windows bias, as Linux users must adapt the examples themselves. Additionally, the VM creation examples consistently use Windows images first, and do not mention Linux-specific considerations or provide parity for Linux VM deployment.
Recommendations
  • Include Linux VM deployment examples alongside Windows examples in CLI and PowerShell sections (e.g., use 'UbuntuLTS' or other Linux images, and demonstrate SSH key authentication).
  • Explicitly mention that the CLI and PowerShell commands work for both Windows and Linux VMs, and highlight any differences in disk attachment or sector size compatibility.
  • Alternate or parallel example blocks for Windows and Linux VM creation, making it clear how to adapt for either OS.
  • Add notes or links to Linux-specific documentation where relevant (e.g., disk formatting, mounting, sector size compatibility).
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-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation provides parity between Azure CLI (Linux/macOS friendly) and Azure PowerShell (Windows-centric) examples for deploying ZRS managed disks. However, PowerShell examples are extensive and use Windows-specific VM images and patterns, while Linux examples (via Azure CLI) are present but less detailed. Resource Manager template instructions and next steps reference PowerShell and Windows images first, and registration commands are only shown in PowerShell. There is a subtle Windows-first bias in example ordering and depth, but Linux users can complete all tasks using the CLI examples provided.
Recommendations
  • Add equivalent Bash or Azure CLI commands for feature registration (currently only PowerShell is shown).
  • Ensure Resource Manager template deployment examples include CLI/Bash alternatives, not just PowerShell.
  • Balance example depth and detail between CLI (Linux/macOS) and PowerShell (Windows) sections.
  • When showing VM creation, alternate between Linux and Windows images, or provide both in each example.
  • In 'Next steps', link to both PowerShell and CLI sample repositories if available.
GitHub Create Pull Request
Virtual Machines Ultra disks for VMs - Azure managed disks ...in/articles/virtual-machines/disks-enable-ultra-ssd.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation provides both Azure CLI and PowerShell examples for deploying and managing Ultra Disks, but all VM creation and disk attachment examples use Windows VM images (e.g., Win2016Datacenter) and do not show Linux VM image equivalents. The portal instructions link only to the Windows VM quickstart, and there are no explicit Linux VM creation or disk attachment examples, despite Ultra Disks supporting Linux VMs.
Recommendations
  • Add Linux VM creation examples in Azure CLI and PowerShell sections (e.g., using Ubuntu or CentOS images).
  • In portal instructions, link to both Windows and Linux VM quickstarts, or clarify that the process is identical for Linux VMs.
  • Show example commands for attaching Ultra Disks to existing Linux VMs, including any OS-specific considerations (e.g., partitioning and formatting disks on Linux).
  • Ensure that documentation language and examples are balanced between Windows and Linux, reflecting the stated support for both.
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-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits moderate Windows bias. Windows-specific examples (PowerShell, CLI) are presented before Linux equivalents, and Windows tooling (PowerShell cmdlets, registry keys, WSUS) is referenced more frequently and in greater detail. Linux-specific examples are present but sometimes less detailed or appear after Windows instructions. Some sections (e.g., patch orchestration modes) provide more options and explanations for Windows than Linux. The 'Next steps' link is Windows-focused.
Recommendations
  • Present Linux and Windows examples side-by-side or alternate their order to avoid Windows-first bias.
  • Expand Linux-specific instructions and examples, especially for CLI and PowerShell usage.
  • Add parity for Linux in sections where only Windows options are described (e.g., patch orchestration modes, disabling automatic updates).
  • Include Linux-focused 'Next steps' links, such as guides for managing Linux VMs.
  • Where Windows registry keys or services are mentioned, provide equivalent Linux configuration details (e.g., for disabling automatic updates).
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 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation provides both Azure CLI (cross-platform) and Azure PowerShell (Windows-centric) examples for creating instant access snapshots, but omits explicit Linux/macOS shell examples and does not mention platform-specific nuances. PowerShell instructions are given equal prominence to CLI, and there are no bash-specific or Linux/macOS workflow notes. The order of examples sometimes places PowerShell before or alongside CLI, and there is no mention of Linux tools or troubleshooting. No Linux/macOS-specific issues or guidance are discussed.
Recommendations
  • Add explicit bash/Linux/macOS shell examples, clarifying that Azure CLI commands work natively on these platforms.
  • Include notes about installing and using Azure CLI on Linux/macOS, and clarify that PowerShell is Windows-centric (though cross-platform PowerShell exists).
  • Highlight any platform-specific differences in disk attachment or hydration processes, if applicable.
  • Provide troubleshooting tips for Linux/macOS users, e.g., permissions, environment variables, or shell compatibility.
  • Consider listing Azure CLI (cross-platform) examples before PowerShell to reduce perceived Windows bias.
GitHub Create Pull Request
Virtual Machines Create and upload a Red Hat Enterprise Linux VHD for use in Azure ...les/virtual-machines/linux/redhat-create-upload-vhd.md
Low Priority View Details →
Scanned: 2026-03-10 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation provides comprehensive instructions for preparing and uploading a Red Hat Enterprise Linux VHD for Azure, covering multiple hypervisors (Hyper-V, KVM, VMware, Kickstart). However, in several sections, Windows/Hyper-V tools and workflows are mentioned first or given prominence (e.g., Hyper-V Manager, convert-vhd cmdlet), before Linux-native alternatives. Linux workflows are fully documented, but Windows/Hyper-V is often presented as the primary or default option.
Recommendations
  • Reorder sections so that Linux-native hypervisors (KVM, VMware, Kickstart) are presented before Hyper-V/Windows tools, or at least equally.
  • When mentioning disk conversion tools, list Linux-native options (qemu-img, VirtualBox) before Windows tools (Hyper-V Manager, convert-vhd).
  • Clarify that Hyper-V steps are only required if using Windows as the host, and highlight Linux-native workflows for users on Linux/macOS.
  • Ensure that references to PowerShell or Windows tools are always accompanied by Linux equivalents, and that Linux instructions are not dependent on Windows tooling.
GitHub Create Pull Request
Virtual Machines Best practices for virtual machine cost optimization ...s/virtual-machines/cost-optimization-best-practices.md
Low Priority View Details →
Scanned: 2026-03-10 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation is generally cross-platform and references both Windows and Linux VM options, but there is a minor bias in the ordering and phrasing: Windows VM considerations (e.g., 'Use at least B2 for Windows machines') are mentioned before Linux equivalents, and Windows pricing links are listed before Linux pricing links. No Windows-only tools or examples are given, and Linux is referenced throughout. No critical sections are Windows-only.
Recommendations
  • When mentioning VM sizing or pricing, present Windows and Linux options together or alternate the order to avoid Windows-first bias.
  • Where specific recommendations are made for Windows (e.g., 'Use at least B2 for Windows machines'), consider adding equivalent guidance for Linux VMs if applicable.
  • Ensure parity in links and examples, such as listing Linux pricing alongside Windows pricing, and referencing automation tools that work for both platforms.
GitHub Create Pull Request
Virtual Machines Customer intent: "As a cloud architect, I want to develop a robust backup and disaster recovery strategy for my Azure VMs and their managed disks, so that my organization can ensure data availability and minimize downtime during outages or data loss incidents." ...s/backup-and-disaster-recovery-for-azure-iaas-disks.md
Low Priority View Details →
Scanned: 2026-03-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation provides backup and disaster recovery guidance for Azure Managed Disks on both Linux and Windows VMs. However, there are minor signs of Windows bias: Windows tools (such as Volume Shadow Service for application-consistent backups) are mentioned first and in more detail, while Linux equivalents (like fsfreeze) are referenced briefly and described as less capable. SQL Server (a Windows-centric workload) is highlighted with links to Windows-specific backup articles, and Windows is mentioned before Linux in some consistency descriptions.
Recommendations
  • Expand Linux backup tooling guidance: Provide more detail on Linux tools (e.g., fsfreeze, LVM snapshots, application-specific backup solutions) for achieving file and application consistency.
  • Balance example order: When describing backup consistency, mention Linux and Windows approaches equally, and avoid always listing Windows first.
  • Include links to Linux-specific documentation: Add references to Linux backup strategies (such as PostgreSQL, MySQL, MongoDB, Cassandra) and their Azure integration.
  • Clarify parity: Explicitly state where Azure backup features offer equivalent support for Linux and Windows, or note any limitations.
  • Add Linux-focused scenarios: Include examples of Linux workloads (e.g., web servers, open-source databases) and their backup strategies.
GitHub Create Pull Request
Virtual Machines Create a Gallery for Sharing Resources .../blob/main/articles/virtual-machines/create-gallery.md
Low Priority View Details →
Scanned: 2026-03-10 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation provides examples for Azure Portal, Azure CLI, PowerShell, and REST API. While PowerShell is included, it is not the only example, and it is presented after CLI examples. The CLI examples use Azure CLI, which is cross-platform and works on Windows, Linux, and macOS. PowerShell is shown as an additional option, but not exclusively or first. There are no Windows-only tools or patterns, and Linux users are not excluded from any critical workflow. However, PowerShell is included as a distinct example, which may be seen as a minor bias toward Windows users, but the CLI is always shown first.
Recommendations
  • Continue to provide Azure CLI examples first, as it is cross-platform.
  • Clarify that Azure CLI commands work on Linux, macOS, and Windows.
  • Optionally, add a note that PowerShell examples are for users who prefer PowerShell, typically on Windows, but PowerShell Core is also available cross-platform.
  • Ensure screenshots and portal instructions do not reference Windows-specific UI elements.
  • Consider adding a short section highlighting cross-platform support for all tools used.
GitHub Create Pull Request
Virtual Machines Server-side encryption of Azure Managed Disks ...blob/main/articles/virtual-machines/disk-encryption.md
Low Priority View Details →
Scanned: 2026-03-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation generally maintains parity between Windows and Linux, providing links to both PowerShell (Windows) and CLI (Linux) guides for enabling encryption features. However, there is a mild 'windows_first' bias, as PowerShell/Windows links and references are consistently listed before their Linux/CLI counterparts. Additionally, in some places, PowerShell is mentioned as the primary tool for certain operations (e.g., revoking access to customer-managed keys), with CLI mentioned second.
Recommendations
  • Alternate the order of Windows/PowerShell and Linux/CLI references throughout the documentation to avoid consistently prioritizing Windows.
  • Where both PowerShell and CLI are mentioned, explicitly state that both are equally supported and provide parallel examples or links.
  • In sections where only PowerShell is referenced first (e.g., revoking access), ensure CLI is given equal prominence, or consider combining into a single sentence referencing both tools.
  • Consider adding brief inline CLI and PowerShell command examples for common tasks, rather than only linking out, to improve parity and user experience.
GitHub Create Pull Request
Virtual Machines Instantly access managed disk snapshots ...les/virtual-machines/disks-instant-access-snapshots.md
Low Priority View Details →
Scanned: 2026-03-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for creating instant access snapshots, but the PowerShell example is given equal prominence to the CLI example, and is not clearly marked as Windows-specific. The CLI example is cross-platform, but there are no explicit Linux/macOS shell examples (e.g., Bash) or clarifications about platform compatibility. The PowerShell example may create friction for Linux/macOS users, as Azure PowerShell is primarily used on Windows. The documentation does not mention Linux tools or patterns, nor does it clarify that Azure CLI is the recommended cross-platform approach.
Recommendations
  • Clearly indicate that Azure PowerShell examples are Windows-centric and recommend Azure CLI for Linux/macOS users.
  • Add explicit Bash shell examples or clarify that Azure CLI commands are cross-platform and can be run on Linux/macOS terminals.
  • Consider showing Azure CLI examples first, or labeling them as the default for cross-platform usage.
  • Add a note explaining that Azure PowerShell can be used on Linux/macOS via PowerShell Core, but Azure CLI is generally preferred for cross-platform scenarios.
GitHub Create Pull Request
Virtual Machines Restrict managed disks from being imported or exported ...tual-machines/disks-restrict-import-export-overview.md
Low Priority View Details →
Scanned: 2026-03-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides both Azure CLI and Azure PowerShell options for configuring disk restrictions, but references to PowerShell and Windows-centric links (e.g., custom RBAC roles via PowerShell) are presented first or exclusively in some sections. The custom RBAC role section links only to a PowerShell-based guide, and PowerShell is mentioned before CLI in the NetworkAccessPolicy section. Linux-specific guidance is present but not always prioritized.
Recommendations
  • Add or link to Linux/CLI-based guides for creating custom RBAC roles, not just PowerShell.
  • Present Azure CLI examples and links before or alongside PowerShell examples, especially in sections relevant to all platforms.
  • Ensure that all referenced articles (e.g., for private links) have clear Linux/CLI equivalents and are equally visible.
  • Where possible, clarify that both Azure CLI and PowerShell can be used, and provide examples for each.
GitHub Create Pull Request
Virtual Machines Enable shared disks for Azure Managed Disks .../main/articles/virtual-machines/disks-shared-enable.md
Low Priority View Details →
Scanned: 2026-03-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides parity between Azure CLI and Azure PowerShell for all disk operations, but PowerShell examples are given equal prominence and sometimes shown before CLI. Azure PowerShell is a Windows-centric tool, and its heavy usage may create friction for Linux/macOS users. However, Azure CLI examples are present for every operation, and the documentation explicitly states applicability to both Linux and Windows VMs. No Windows-only tools or patterns are used, and Linux is not missing from any critical example.
Recommendations
  • Consider listing Azure CLI examples before PowerShell in each section, as Azure CLI is cross-platform and more accessible for Linux/macOS users.
  • Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, while PowerShell is primarily for Windows (with limited cross-platform support).
  • Add brief notes or links for Linux/macOS users on how to install and use Azure CLI.
  • Where possible, clarify that all steps are OS-agnostic unless a specific OS is required.
GitHub Create Pull Request
Virtual Machines Share an Azure Managed Disk across VMs ...cs/blob/main/articles/virtual-machines/disks-shared.md
Low Priority View Details →
Scanned: 2026-03-10 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation covers both Windows and Linux platforms for Azure shared disks, but Windows examples and explanations are consistently presented before Linux equivalents. The 'Sample workloads' section starts with Windows, and performance throttling examples also begin with Windows scenarios. However, Linux information is present and detailed, including supported distributions, cluster managers, and relevant utilities.
Recommendations
  • Alternate the order of Windows and Linux sections, or present Linux examples first in some cases.
  • Ensure parity in example detail: provide equally detailed Linux workload examples, including step-by-step guides or links to Linux-specific templates (similar to the Windows SoFS and SAP templates).
  • Add explicit Linux sample configurations or walkthroughs for clustered file servers and database workloads, matching the depth of Windows examples.
  • Where possible, include links to Linux-focused documentation or templates for common workloads.
GitHub Create Pull Request
Virtual Machines What's new in Azure Disk Storage ...blob/main/articles/virtual-machines/disks-whats-new.md
Low Priority View Details →
Scanned: 2026-03-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation is generally neutral and focused on Azure Disk Storage features, which are cross-platform. However, there are minor instances where Windows-specific links or references are given before Linux equivalents, such as linking to Windows documentation first for disk expansion, and referencing Windows tools (Azure PowerShell) alongside Azure CLI. No critical features are described in a Windows-only manner, and Linux parity is mostly maintained.
Recommendations
  • When referencing how to expand disks, ensure both Windows and Linux documentation links are presented together, or Linux is not consistently listed second.
  • Where Azure PowerShell is mentioned, explicitly note Azure CLI and Bash alternatives for Linux/macOS users.
  • Review linked articles (e.g., expand-disks, find-unattached-disks) to ensure Linux/macOS examples are present and not secondary.
  • Consider adding a short statement clarifying that all features are available for both Windows and Linux unless otherwise noted.
GitHub Create Pull Request
← Previous Page 12 of 33 Next →