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 226-250 of 818 flagged pages
Virtual Machines Creating Virtual Machine Restore Points using Azure portal ...hines/virtual-machines-create-restore-points-portal.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 focuses exclusively on using the Azure portal for creating and restoring VM restore points, with references to alternative methods using Azure CLI and PowerShell. However, when it comes to restoring a VM from a restore point, the links provided for creating a new VM and attaching restored disks point to Windows-specific documentation, with no mention or links to equivalent Linux VM instructions. This creates friction for Linux users who may not know where to find the relevant steps for their platform.
Recommendations
  • Add links to Linux VM creation and disk attachment documentation alongside the Windows links.
  • Explicitly mention that the process applies to both Windows and Linux VMs, and provide guidance or examples for Linux users.
  • Ensure parity in examples and instructions for both Windows and Linux throughout the restore process.
  • Consider adding a note or section for platform-specific steps if any differences exist.
GitHub Create Pull Request
Virtual Machines Create and deploy VM Application on Azure ...in/articles/virtual-machines/vm-applications-how-to.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 exhibits a notable Windows bias in several areas. Windows and PowerShell examples are frequently presented first or exclusively (e.g., .EXE, .MSI, .PS install scripts), and Windows-specific tools and patterns (msiexec, powershell.exe, .exe/.msi packaging) are emphasized. In CI/CD pipeline samples (GitHub Actions, Azure DevOps, GitLab, Jenkins), the default application and config file names are always Windows-centric (.exe, .json), and the creation of VM Application definitions defaults to Windows OS type, with no parallel Linux example. While Linux install script examples are present for .tar, .deb, .rpm, and .sh, the overall flow and automation guidance prioritize Windows scenarios, and Linux parity is not consistently maintained.
Recommendations
  • Provide Linux-first or side-by-side examples for all install script types, especially for .deb, .rpm, .sh, and .tar.gz.
  • In CI/CD pipeline samples, alternate or parallelize examples for Linux apps (e.g., use app.sh, app.deb, app-config.yaml) and set --os-type Linux in at least half of the samples.
  • Explicitly show how to create and deploy Linux VM Applications in automation flows (GitHub Actions, DevOps, etc.), not just Windows.
  • Balance the order of presentation so Linux and Windows examples are equally visible and accessible.
  • Avoid defaulting to Windows file types (.exe, .msi, .json) in variable names and sample scripts; use generic or Linux-centric names where appropriate.
  • Add guidance for Linux-specific packaging and deployment nuances (e.g., SELinux, systemd integration, permissions).
GitHub Create Pull Request
Virtual Machines Overview of VM Applications in the Azure Compute Gallery ...blob/main/articles/virtual-machines/vm-applications.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 Windows and Linux guidance for packaging and deploying VM Applications, but several sections display Windows bias. Windows examples and tools (PowerShell, cmd.exe, msiexec) are often presented first or in more detail, and troubleshooting relies heavily on PowerShell commands. Linux instructions are present and reasonably thorough, but Windows-centric tools and patterns are emphasized, and some example scripts and troubleshooting steps are PowerShell-heavy.
Recommendations
  • Present Linux and Windows examples in parallel or alternate order, rather than Windows-first.
  • Expand troubleshooting guidance to include equivalent Linux CLI commands (e.g., Azure CLI, SSH, system logs) for extension status and error investigation.
  • Where PowerShell is referenced for deployment or status, provide Azure CLI or Bash alternatives for Linux/macOS users.
  • In packaging and install sections, ensure Linux examples are as detailed and prominent as Windows ones.
  • For file renaming and manipulation examples, include Linux shell commands alongside Windows cmd/powershell.
  • Clarify that all operations (deployment, management, troubleshooting) can be performed from Linux/macOS environments using Azure CLI or REST API.
GitHub Create Pull Request
Virtual Machines VM vCore Customization ...lob/main/articles/virtual-machines/vm-customization.md
Medium Priority View Details →
Scanned: 2026-01-14 01:31
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation provides both Azure CLI and PowerShell examples for configuring VM vCore customization, but the PowerShell example is detailed and uses Windows-specific SDK objects, while the CLI example is brief and lacks Linux/macOS-specific context. The PowerShell section is given equal prominence to CLI, and there is no explicit mention of Linux/macOS shell usage or examples beyond the CLI. The documentation refers to PowerShell without clarifying cross-platform support, and does not provide bash or shell script equivalents for Linux users. The ordering of examples (CLI, then PowerShell) is reasonable, but the PowerShell example is more verbose and detailed, potentially favoring Windows users.
Recommendations
  • Add explicit bash or shell script examples for Linux/macOS users, especially for ARM template deployment and Azure CLI usage.
  • Clarify that Azure CLI commands work on Linux/macOS and provide sample commands for those environments (e.g., with SSH key handling, environment variables).
  • Note that PowerShell Core is cross-platform, but provide guidance or examples for Linux/macOS users who may not use PowerShell.
  • Ensure parity in example detail: expand CLI examples to match the depth of the PowerShell section, including object manipulation if relevant.
  • Consider adding a table or section comparing the steps for Windows, Linux, and macOS environments.
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-14 01:31
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation provides both Azure CLI and PowerShell examples for most scenarios, but the PowerShell sections are heavily Windows-centric, with all example scripts using Windows-specific parameters (e.g., Set-AzVMOperatingSystem -Windows) and password authentication. There are no PowerShell examples for Linux VM creation, nor any mention of Linux-specific PowerShell patterns. Additionally, network security rules in PowerShell examples focus on RDP (port 3389), which is Windows-specific, and password authentication is shown before SSH key authentication. While CLI and REST examples do show Linux VM creation and SSH, PowerShell coverage is notably biased toward Windows. The order of presentation also often places Windows-centric tools and patterns before Linux equivalents.
Recommendations
  • Add PowerShell examples for creating Linux VMs, including use of Set-AzVMOperatingSystem -Linux and SSH key authentication.
  • In PowerShell networking examples, include rules for SSH (port 22) alongside or before RDP (port 3389).
  • Ensure parity in authentication methods: demonstrate both password and SSH key authentication for both Windows and Linux in all tool examples.
  • When presenting examples, alternate or randomize the order of Windows and Linux scenarios, or explicitly provide both side-by-side.
  • Review and update documentation to avoid implicit prioritization of Windows tools and patterns.
GitHub Create Pull Request
Virtual Machines VM watch Collectors Suite .../articles/virtual-machines/vm-watch-collector-suite.md
Medium Priority View Details →
Scanned: 2026-01-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 VM watch Collectors Suite demonstrates a moderate Windows bias. Several collectors reference Windows-specific tools (e.g., Windows EventLog, w32tm command, time.windows.com), and Windows eligibility is often described before Linux equivalents. Some collectors are Windows-only (e.g., system_error, hardware_health_monitor), while Linux support is limited or only mentioned in passing (e.g., hardware_health_nvidia_smi for Ubuntu only). There are missing Linux/macOS examples for event log collection and time synchronization, and the default URLs and NTP servers are Windows-centric.
Recommendations
  • Provide equivalent Linux/macOS examples and tooling for collectors that currently reference only Windows tools (e.g., describe how system errors and hardware health can be collected on Linux, such as using syslog, journalctl, or SMART tools).
  • Include Linux-first or cross-platform examples for time synchronization (e.g., use pool.ntp.org or OS-agnostic NTP servers instead of time.windows.com).
  • Clarify eligibility and default behaviors for Linux/macOS in all collectors, not just Windows.
  • Add explicit documentation for macOS support or clarify its limitations.
  • Where a collector is Windows-only, suggest Linux alternatives or note the gap.
  • Reorder examples and descriptions so that Linux and Windows are given equal prominence.
GitHub Create Pull Request
Virtual Machines Implement Oracle Golden Gate on an Azure Linux VM | Microsoft Docs ...hines/workloads/oracle/configure-oracle-golden-gate.md
Medium Priority View Details →
Scanned: 2026-01-14 01:31
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Powershell Heavy
Summary
While the documentation is focused on deploying Oracle Golden Gate on Azure Linux VMs, there is a notable Windows bias in the sections related to X Server setup and file transfer. The instructions require users to create a Windows VM (ggXServer) specifically to run Xming X Server for graphical installation, with no mention of Linux or macOS alternatives (such as X11 forwarding or native X servers). Additionally, PowerShell commands are used for Bastion tunneling and file transfer, with no equivalent Bash or Linux-native instructions provided. The documentation lists Windows paths before Linux ones and assumes Windows tools for critical steps.
Recommendations
  • Provide instructions for running X Server natively on Linux and macOS clients (e.g., using XQuartz on macOS, X11 on Linux, or X11 forwarding via SSH).
  • Include Bash equivalents for Bastion tunneling and SCP file transfer, using az CLI and standard Linux/macOS tools.
  • Offer alternative steps for graphical installer invocation using SSH X11 forwarding, avoiding the need for a dedicated Windows VM.
  • List Linux/macOS paths and tools before or alongside Windows ones when discussing SSH keys and file locations.
  • Clarify that the Windows VM is optional and only needed if users lack access to a local X server.
GitHub Create Pull Request
Virtual Machines Connect Azure ExpressRoute with Oracle Cloud Infrastructure | Microsoft Docs ...nes/workloads/oracle/configure-azure-oci-networking.md
Medium Priority View Details →
Scanned: 2026-01-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 page demonstrates a moderate Windows bias. While it claims applicability to Linux VMs and references Terraform (a cross-platform tool), most step-by-step instructions and screenshots are based on the Azure Portal UI, which is platform-agnostic but often associated with Windows workflows. Notably, when scripting is mentioned, only PowerShell is referenced for ExpressRoute FastPath configuration, with no Bash or Azure CLI example provided. Monitoring is described using Azure Network Performance Monitor, a Windows-centric tool, with no mention of Linux-native alternatives. There is a lack of explicit Linux command-line examples, and PowerShell is presented before any Linux-friendly options.
Recommendations
  • Add Azure CLI and Bash examples alongside PowerShell commands for configuration steps, especially for ExpressRoute FastPath.
  • Include Linux-centric monitoring options or clarify Network Performance Monitor's cross-platform capabilities.
  • Provide explicit Linux command-line instructions for key steps (e.g., resource creation, verification).
  • Ensure screenshots and UI references are supplemented with CLI or script-based alternatives for Linux users.
GitHub Create Pull Request
Virtual Machines Set up Oracle ASM on an Azure Linux virtual machine | Microsoft Docs ...tual-machines/workloads/oracle/configure-oracle-asm.md
Medium Priority View Details →
Scanned: 2026-01-14 01:31
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation is focused on setting up Oracle ASM on Azure Linux VMs, but exhibits notable Windows bias in several areas. The X Server VM is created as a Windows machine, and all instructions for running X Server use Windows-only tooling (Xming, Windows Firewall). The PowerShell example for Bastion tunneling is given, with no Linux/macOS equivalent. SCP instructions are shown in a Windows context. There are no instructions for using a Linux or macOS workstation for X Server or Bastion tunneling, nor are cross-platform alternatives mentioned.
Recommendations
  • Provide instructions for creating the X Server VM as a Linux machine (e.g., Ubuntu with X11), or explain how to use a local Linux/macOS workstation for X11 forwarding.
  • Include Linux/macOS equivalents for Bastion tunneling (e.g., using az network bastion tunnel from bash/zsh, or using SSH ProxyCommand).
  • Offer guidance for running X Server on Linux (e.g., Xorg, XQuartz for macOS) and connecting to the VM using native SSH/X11 forwarding.
  • Show SCP examples for Linux/macOS, not just Windows/PowerShell.
  • Mention cross-platform tools and patterns before or alongside Windows-specific ones, or clearly mark Windows-only steps.
GitHub Create Pull Request
Virtual Machines Red Hat Enterprise Linux bring-your-own-subscription Azure images | Microsoft Docs ...ain/articles/virtual-machines/workloads/redhat/byos.md
Medium Priority View Details →
Scanned: 2026-01-14 01:31
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation provides both Azure CLI (cross-platform) and PowerShell examples for provisioning Red Hat Enterprise Linux BYOS images on Azure. However, the PowerShell section is significantly more detailed, with a full end-to-end script, while the CLI section is more concise and lacks equivalent depth (e.g., full VM creation with networking, SSH keys, etc.). The PowerShell example uses Windows-specific tools and patterns, and appears after the CLI section, but is more comprehensive. There is no explicit Linux/macOS bias, but the richer PowerShell example may create friction for non-Windows users seeking parity.
Recommendations
  • Expand the Azure CLI section to include a full, step-by-step example covering resource group, network, public IP, NSG, NIC, VM creation, and SSH key configuration, matching the PowerShell script's completeness.
  • Add explicit notes or links for Linux/macOS users on how to generate SSH keys and use them in Azure CLI.
  • Ensure that all automation examples (including Terraform) are platform-neutral and provide parity in detail.
  • Consider providing bash shell scripts or guidance for Linux/macOS users where appropriate.
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:01
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 Windows bias in several ways: Windows extension types are consistently used in code examples (REST, PowerShell, ARM templates), with 'DependencyAgentWindows' shown as the default even when Linux equivalents exist. PowerShell examples are prominent and use Windows-centric extension types. Linux examples are present only in CLI tabs, and Linux extension types are not shown in REST, PowerShell, or ARM template samples. Windows extension types are listed first in supported extensions and examples, and Windows tools (PowerShell) are emphasized over Linux-native alternatives.
Recommendations
  • Provide parallel examples for both Windows and Linux extension types in all code samples (REST, PowerShell, ARM template), not just CLI.
  • Alternate the order of Windows and Linux extension types in tables and examples, or group them together to avoid Windows-first presentation.
  • Include Bash or shell scripting examples for Linux users where PowerShell is used.
  • Explicitly mention Linux support and provide guidance for Linux-specific scenarios in enabling automatic extension upgrades.
  • Clarify that CLI commands work cross-platform and highlight Linux usage where relevant.
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 00:01
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation provides examples for ARM templates, Azure CLI, and PowerShell, with PowerShell (a Windows-centric tool) given its own section and example. The CLI example is generic, but PowerShell is highlighted as a distinct method, which may suggest a Windows-first approach. There is no explicit Linux shell example (e.g., Bash), nor is there parity for Linux-specific command-line tools. The documentation mentions Visual Studio Code as an IDE, which is cross-platform, but does not suggest Linux-native editors. The only Linux-specific guidance is in a note about the extension type parameter, not in the main workflow or examples.
Recommendations
  • Add explicit Bash or Linux shell command examples alongside PowerShell, especially for tasks like viewing or configuring extensions.
  • Clarify that Azure CLI commands work identically on Linux/macOS and Windows, and provide platform-specific notes if there are differences.
  • Include Linux-native editor suggestions (e.g., Vim, Nano) when recommending IDEs for editing JSON.
  • Ensure that Linux-specific extension types and configuration steps are shown in examples, not just mentioned in notes.
  • Consider reordering examples so that cross-platform tools (ARM template, CLI) appear before Windows-specific tools (PowerShell).
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:01
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation displays a moderate Windows bias, particularly in the ARM template section, which is heavily oriented toward Windows VM deployment and configuration. Windows-specific parameters, images, and PowerShell DSC are emphasized, while Linux equivalents are not mentioned. PowerShell examples are provided alongside CLI, but Windows tooling and terminology (e.g., DSC, WebDeploy) are referenced without Linux alternatives. However, Azure CLI examples do use Ubuntu images, and the overall workflow is cross-platform, so Linux users can complete the tasks but may need to adapt Windows-centric instructions.
Recommendations
  • Add ARM template parameters and examples for Linux VM images (e.g., Ubuntu, CentOS) alongside Windows options.
  • Include Linux configuration options (e.g., cloud-init, shell scripts) in the ARM template instead of only PowerShell DSC.
  • Provide explicit Linux/macOS command-line examples where PowerShell is referenced, or clarify cross-platform compatibility.
  • Balance references to Windows-specific tooling (DSC, WebDeploy) with Linux equivalents (cloud-init, custom script extension).
  • Ensure documentation language and examples do not assume a Windows-first environment.
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:01
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation, while claiming applicability to both Windows and Linux VMs, demonstrates a moderate Windows bias. Windows tools (PowerShell) are given equal or greater prominence than Linux-native approaches, and ARM template examples are exclusively for Windows images. Password requirements and example parameters are tailored for Windows VMs, with no Linux-specific ARM template or parameterization. CLI examples use Ubuntu images but do not provide parity in ARM template or configuration details for Linux VMs.
Recommendations
  • Add ARM template examples for Linux VMs, including Linux image references and SSH key authentication.
  • Include Linux-specific configuration parameters and guidance (e.g., SSH, cloud-init) in ARM templates.
  • Ensure password/account requirements are described for both Windows and Linux, or clarify differences.
  • Balance PowerShell and CLI coverage, and consider Bash or other Linux-native scripting examples where appropriate.
  • Present examples for both Windows and Linux side-by-side, especially in critical sections like VM creation and configuration.
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:01
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 moderate Windows bias. PowerShell examples are provided for all advanced scenarios, with Windows-centric tools and patterns (e.g., ConvertTo-SecureString, PSCredential, Windows images) used throughout. Resource Manager Template instructions and examples are exclusively shown using PowerShell, with no Linux shell or cross-platform alternatives. In PowerShell sections, only Windows VM images are used, while Azure CLI examples use Ubuntu images. The feature registration step for ARM templates is only shown in PowerShell, with no az CLI equivalent. The 'Next steps' section links only to PowerShell-based samples.
Recommendations
  • Add bash/az CLI equivalents for all PowerShell-only steps, especially for ARM template feature registration and deployments.
  • Show Linux VM image examples in PowerShell sections, or clarify how to deploy Linux VMs with ZRS disks using PowerShell.
  • Include links to cross-platform or bash-based ARM template samples in the 'Next steps' section.
  • Where possible, use generic terminology and avoid Windows-specific constructs (e.g., ConvertTo-SecureString) in examples, or provide Linux/macOS alternatives.
  • Ensure that both Windows and Linux workflows are covered equally in all tabs and examples.
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-14 00:01
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation provides parity between Azure Portal, CLI, PowerShell, and REST API for VM deletion options. However, there is a notable Windows bias: PowerShell examples are given equal prominence to CLI, and REST examples use Windows-centric values (e.g., Windows images, osType: Windows). There are no explicit Linux-specific examples (e.g., using a Linux image, osType: Linux, or Linux-specific adminUsername patterns). The FAQ and walkthroughs do not mention Linux-specific considerations, and PowerShell (a Windows-first tool) is featured as a primary automation method, which may not be available or preferred on Linux/macOS. The only Linux reference is in the 'Next steps' link, which is not integrated into the main content.
Recommendations
  • Add explicit Linux examples in CLI and REST sections, such as using a Linux image (e.g., Ubuntu) and osType: Linux.
  • In REST examples, alternate between Windows and Linux VM configurations to show parity.
  • Clarify that PowerShell is cross-platform, but recommend CLI for Linux/macOS users and provide Bash shell examples where appropriate.
  • In the FAQ, add notes about Linux VM deletion behaviors, if any differences exist.
  • Ensure that Linux and Windows examples are presented with equal prominence, alternating or grouping by OS where possible.
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-14 00:01
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation provides step-by-step instructions for copying incremental snapshots using Azure CLI, Azure PowerShell, Azure Portal, and ARM templates. While Azure CLI is cross-platform, the PowerShell example is Windows-centric and given equal prominence. There are no explicit Linux/macOS shell examples (e.g., Bash), nor are there notes about platform-specific differences. The CLI example uses Bash syntax, but this is not clarified, and no Linux-specific considerations (such as authentication, environment setup, or troubleshooting) are mentioned. The manual copy section references .NET sample code, which is more common on Windows, and does not mention Linux alternatives.
Recommendations
  • Explicitly state that Azure CLI commands are cross-platform and provide Bash and PowerShell variants where syntax differs.
  • Add Linux/macOS-specific notes for authentication, environment setup, and troubleshooting.
  • Include sample scripts or references for manual copy using Linux tools (e.g., curl, azcopy, Bash).
  • Offer parity in programming language samples (e.g., Python or Bash for manual copy, not just .NET).
  • Clarify when examples are Windows-specific and provide Linux/macOS equivalents where relevant.
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:01
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation exhibits several signs of Windows bias. VM creation examples consistently use Windows images (e.g., 'Win2016Datacenter') in both Azure CLI and PowerShell scripts, with no Linux equivalents shown. The variable names and authentication methods (password-based, not SSH keys) are tailored to Windows scenarios. PowerShell is given equal prominence to Azure CLI, despite being Windows-centric. There are no explicit Linux VM creation examples, nor are there instructions or code samples for Linux-specific deployment patterns (e.g., using SSH keys, specifying a Linux image, or Linux admin username conventions).
Recommendations
  • Add Linux VM creation examples alongside Windows ones in all CLI and PowerShell sections (e.g., use Ubuntu or CentOS images, SSH authentication).
  • Show how to specify SSH keys for Linux VMs in CLI and PowerShell scripts.
  • Include Linux-specific variable naming and admin username conventions.
  • Explicitly mention that Azure CLI works cross-platform and provide Linux/macOS installation guidance.
  • Where PowerShell is referenced, clarify its availability on Linux/macOS, or suggest Bash alternatives.
  • In portal instructions, show screenshots or steps for Linux VM creation and disk attachment.
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:01
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation exhibits a notable Windows bias. Windows-specific examples (e.g., Win2016Datacenter image) are given exclusively in CLI and PowerShell sections, with no Linux VM deployment examples. References and links to Windows VM quickstarts are present, while Linux equivalents are omitted. All scripting examples use Windows-centric tools (PowerShell), and the CLI examples also default to Windows images. There is no guidance for Linux disk partitioning/formatting, nor any mention of Linux-specific considerations.
Recommendations
  • Add Linux VM deployment examples alongside Windows (e.g., use Ubuntu or CentOS images in CLI/PowerShell snippets).
  • Provide links to both Windows and Linux VM quickstart guides.
  • Include Linux-specific instructions for partitioning and formatting Ultra Disks after attachment.
  • Ensure CLI and PowerShell examples alternate or show both Windows and Linux usage.
  • Mention any Linux-specific limitations, requirements, or troubleshooting steps for Ultra Disks.
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-14 00:01
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 does not offer explicit Linux shell (bash) or macOS-specific guidance. PowerShell examples are given equal prominence to CLI, and no Linux/macOS-specific nuances or troubleshooting are mentioned. There is a slight Windows-first bias in the ordering and tool selection, and Linux users may need to infer usage from CLI examples without tailored advice.
Recommendations
  • Add explicit bash examples for Linux/macOS users, including variable declaration and command usage.
  • Clarify that Azure CLI commands work on Linux/macOS and provide troubleshooting tips for common platform-specific issues (e.g., authentication, environment variables).
  • Mention installation steps for Azure CLI on Linux/macOS, or link to relevant documentation.
  • If PowerShell is mentioned, note that PowerShell Core is available cross-platform, but provide bash alternatives for Linux/macOS.
  • Ensure that any screenshots or portal instructions are not Windows-centric (e.g., avoid showing Windows-only UI elements).
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 22:27
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 does not offer explicit Linux/macOS shell examples (e.g., Bash), nor does it mention Linux-specific considerations. PowerShell examples are given equal prominence to CLI, and the CLI examples use Bash syntax but do not clarify Linux compatibility. There are no references to Linux tools or patterns, and the order of examples sometimes places PowerShell before CLI. No Linux-specific troubleshooting or parity notes are present.
Recommendations
  • Explicitly state that Azure CLI examples are compatible with Linux/macOS and provide sample Bash commands where appropriate.
  • Add a dedicated Bash example tab for Linux users, clarifying environment setup and shell differences.
  • Include notes on any Linux/macOS-specific considerations, such as authentication, file permissions, or environment variables.
  • Ensure CLI examples appear before PowerShell to emphasize cross-platform support.
  • Mention that PowerShell Core is available on Linux/macOS if PowerShell is referenced.
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 21:56
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 (bash-style) and Azure PowerShell examples for creating instant access snapshots, but does not include explicit Linux/macOS shell examples (e.g., bash, zsh) or mention Linux-specific considerations. PowerShell examples are given equal prominence, and there is no discussion of Linux tools or patterns. The CLI examples use bash syntax, which is compatible with Linux/macOS, but this is not clarified. No Linux-specific troubleshooting or alternative workflows are described.
Recommendations
  • Explicitly state that Azure CLI examples are compatible with Linux/macOS shells and provide sample commands using bash/zsh syntax.
  • Add a section or tab labeled 'Linux/macOS Shell' to clarify usage on non-Windows platforms.
  • Include troubleshooting tips or notes for Linux users (e.g., installation of Azure CLI, environment variables, file permissions).
  • Ensure that PowerShell is not presented as the default or primary method, and clarify cross-platform parity.
  • Mention any OS-specific caveats if they exist (e.g., differences in authentication, file paths, or environment setup).
GitHub Create Pull Request
Virtual Machines Share a Capacity Reservation Group in Azure ...s/virtual-machines/capacity-reservation-group-share.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation provides examples for API, Azure CLI, PowerShell, and ARM templates. PowerShell is featured as a primary automation tool throughout, and PowerShell examples are included in every tabbed section, sometimes with explicit links to Windows-specific modules. While Azure CLI is cross-platform, PowerShell is a Windows-centric tool (though it is available on Linux, usage is far less common among Linux users). There is no mention of Linux-native scripting or automation patterns (e.g., Bash, shell scripts), nor are Linux-specific considerations or examples provided. In several places, PowerShell is referenced before CLI, and links to PowerShell modules are given more prominence. No Linux/macOS-specific tools or workflows are discussed.
Recommendations
  • Add Bash/shell script examples for key operations, especially for Linux users who may prefer native scripting over PowerShell.
  • Clarify that Azure CLI is fully cross-platform and provide explicit instructions for Linux/macOS environments (e.g., installation, usage tips).
  • Where PowerShell is referenced, note its availability on Linux/macOS and provide guidance for those platforms.
  • Ensure CLI examples are shown before PowerShell, or at least alternate the order to avoid Windows-first perception.
  • Include troubleshooting or environment setup notes for Linux/macOS users, such as file path conventions, authentication, or package installation.
  • Consider referencing Linux-native automation tools (e.g., Ansible, Terraform) if relevant to the audience.
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-13 06:17
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation consistently provides examples using Windows images (Win2016Datacenter) for VM creation in both Azure CLI and PowerShell sections, with no equivalent Linux VM examples. The only quickstart linked for portal deployment is for Windows VMs. There are no Linux-specific instructions or examples for deploying or managing Ultra Disks, despite the feature being available for Linux VMs. This creates friction for Linux users, who must adapt Windows-centric instructions to their own environments.
Recommendations
  • Add Linux VM creation examples (e.g., using Ubuntu or CentOS images) alongside Windows examples in CLI and PowerShell sections.
  • Provide links to Linux VM quickstart guides in the portal deployment section.
  • Explicitly mention any Linux-specific considerations for Ultra Disk usage, partitioning, and formatting.
  • Ensure all code snippets and walkthroughs are presented for both Windows and Linux scenarios, or clarify when instructions are OS-agnostic.
GitHub Create Pull Request
Virtual Machines FAQ Ephemeral OS disks ...in/articles/virtual-machines/ephemeral-os-disks-faq.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page provides a detailed PowerShell script for checking VM SKU support for ephemeral OS disks, but does not offer equivalent examples or scripts for Linux/macOS users (e.g., Bash, Azure CLI). The only code sample is in PowerShell, and Windows tooling is referenced exclusively for critical tasks.
Recommendations
  • Add equivalent Azure CLI and/or Bash script examples for checking VM SKU support for ephemeral OS disks.
  • Present cross-platform instructions and scripts side-by-side, or indicate which tools are available on all platforms.
  • Explicitly mention how Linux/macOS users can perform the same tasks, including installation or usage notes for Azure CLI.
  • Where PowerShell is referenced, clarify if it can be used on Linux/macOS, or provide alternatives.
GitHub Create Pull Request
← Previous Page 10 of 33 Next →