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 251-275 of 818 flagged pages
Virtual Machines Restrict managed disks from being imported or exported ...tual-machines/disks-restrict-import-export-overview.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 First Missing Linux Example
Summary
The documentation shows a moderate Windows bias. Powershell and Windows-centric links/examples are referenced before Linux/CLI equivalents, especially in the custom RBAC role section. The custom role creation links only to a PowerShell page, with no Linux/CLI alternative. In other sections, both CLI and PowerShell are mentioned, but Windows tools or examples are often listed first. There is no explicit Linux example for custom role creation, and the overall flow assumes familiarity with Windows tooling.
Recommendations
  • Add links and examples for creating custom RBAC roles using Azure CLI or REST API, not just PowerShell.
  • Ensure that Linux/CLI documentation is referenced alongside or before Windows/PowerShell documentation in each section.
  • Provide explicit Linux/macOS command examples where possible, not just links.
  • Review the order of tool references to avoid Windows-first bias.
GitHub Create Pull Request
Virtual Machines Tenable One-Click Nessus Extension for Azure VMs ...b/main/articles/virtual-machines/extensions/tenable.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides only PowerShell command-line examples, which are primarily relevant for Windows users. There are no Linux shell (bash/CLI) examples, and the command-line section is explicitly described as 'available through PowerShell.' This creates friction for Linux users, who must adapt Windows-centric instructions to their environment. The UI instructions are platform-neutral, but the lack of Linux command-line guidance is a notable gap.
Recommendations
  • Add equivalent Linux CLI examples using Azure CLI (az) or bash scripts for deploying the extension to Linux VMs.
  • Clarify in the command-line section that PowerShell can be used cross-platform, or explicitly mention how Linux users should proceed.
  • Provide step-by-step instructions for Linux users, including any prerequisites or differences in extension deployment.
  • Ensure parameter examples and explanations are not Windows-centric and are applicable to both platforms.
GitHub Create Pull Request
Virtual Machines Customer intent: "As a cloud administrator, I want to create and manage incremental snapshots of virtual disks, so that I can efficiently utilize storage and ensure data integrity while complying with the snapshot limitations and performance impacts." ...tual-machines-disks-incremental-snapshots-restrictions.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 references Azure PowerShell samples before Azure CLI, and links to PowerShell-specific scripts for checking disk status and background copy progress. This ordering and emphasis may create friction for Linux/macOS users, as PowerShell is primarily a Windows tool, and the CLI is more cross-platform.
Recommendations
  • Present Azure CLI examples and links before or alongside PowerShell equivalents.
  • Ensure all referenced scripts and samples have Linux/macOS compatible CLI versions.
  • Explicitly mention cross-platform compatibility and provide guidance for non-Windows users.
  • Add Bash or shell script examples where appropriate.
GitHub Create Pull Request
Virtual Machines Customer intent: As a cloud administrator, I want to retrieve the encryption type of a specified disk in a resource group, so that I can ensure compliance with security standards for our virtual machines. ...ttps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/virtual-machines/includes/virtual-machines-disks-encryption-status-powershell.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides only a PowerShell example for retrieving the encryption type of a disk in Azure, which is primarily a Windows tool. There are no equivalent examples for Linux/macOS users (e.g., using Azure CLI or Bash), and the documentation implicitly assumes the user is on Windows or using PowerShell Core.
Recommendations
  • Add Azure CLI (az) example for retrieving disk encryption type, which works natively on Linux/macOS.
  • Explicitly mention cross-platform alternatives and clarify which tools are supported on each OS.
  • Consider presenting CLI/Bash examples before or alongside PowerShell to improve parity.
GitHub Create Pull Request
Virtual Machines Azure CLI - Enable customer-managed keys with SSE - managed disks ...chines/linux/disks-enable-customer-managed-keys-cli.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation is largely cross-platform and uses Azure CLI examples, which are suitable for both Linux and Windows. However, in the 'Next steps' section, disaster recovery scenarios are linked only to PowerShell-based guides (which are Windows-centric), and Hyper-V/VMware are Windows technologies. Additionally, Windows VM scenarios are referenced before Linux in some links and examples.
Recommendations
  • Provide equivalent Bash or Azure CLI-based guides for disaster recovery scenarios, especially for VMware and Hyper-V environments.
  • Include explicit Linux/macOS instructions or links where PowerShell is referenced.
  • Where possible, mention Linux alternatives or clarify cross-platform compatibility in linked guides.
  • Ensure Linux VM scenarios are given equal prominence in example sections and links.
GitHub Create Pull Request
Virtual Machines Troubleshoot Azure VM Image Builder ...s/virtual-machines/linux/image-builder-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 demonstrates a moderate Windows bias. Windows-specific tools (PowerShell, WinRM, Sysprep) and troubleshooting steps are frequently mentioned, often before or in more detail than their Linux equivalents. Examples and error logs for Windows (e.g., PowerShell commands, Windows Update, Sysprep) are more extensive, while Linux instructions (e.g., waagent, SSH) are present but less detailed. Some troubleshooting sections and DevOps logs focus on Windows paths and tools, with Linux alternatives either briefly mentioned or omitted.
Recommendations
  • Ensure Linux examples are provided alongside Windows ones, especially for troubleshooting steps and command-line instructions.
  • Present Linux and Windows instructions in parallel, rather than Windows-first ordering.
  • Expand Linux-specific troubleshooting guidance (e.g., common waagent issues, SSH connectivity problems, Linux log file locations).
  • Include Linux error log samples and solutions where only Windows examples are shown.
  • Balance the use of PowerShell and Bash/shell script examples for customizations and automation.
  • Reference Linux documentation and support resources as prominently as Windows ones.
GitHub Create Pull Request
Virtual Machines Create shared Azure Linux VM images using the portal ...rticles/virtual-machines/linux/shared-images-portal.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 is focused on Linux VM images, but in the 'Before you begin' section, it references a tutorial for creating a managed image using Azure PowerShell (which is Windows-centric) and links to a snapshot guide under a Windows-specific path. No explicit Linux CLI or shell examples are provided, and Windows/PowerShell tools are mentioned before any Linux alternatives.
Recommendations
  • Provide explicit Linux CLI (e.g., Bash, Azure CLI) examples for creating managed images and snapshots.
  • Reference Linux-specific documentation for creating snapshots and images, rather than Windows paths.
  • Include parity in tooling instructions, such as showing both PowerShell and Bash/Azure CLI commands side-by-side.
  • Clarify that Azure PowerShell is cross-platform, or suggest Azure CLI as an alternative for Linux/macOS users.
GitHub Create Pull Request
Virtual Machines MSP via CLI ...hines/metadata-security-protocol/other-examples/cli.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
All CLI examples use the Windows Server image ('Win2022DataCenter') and do not mention or provide examples for Linux VM images. There is no guidance for Linux-specific configuration, nor any mention of Linux image names or considerations. This may cause confusion or friction for users deploying Linux VMs.
Recommendations
  • Include parallel examples using popular Linux images (e.g., 'UbuntuLTS', 'CentOS', 'Debian') alongside Windows examples.
  • Add notes clarifying whether MSP configuration steps differ for Linux VMs, or explicitly state if the process is identical.
  • Provide guidance on selecting Linux images and any Linux-specific flags or considerations.
  • Ensure screenshots and references are not Windows-centric, or provide Linux equivalents.
GitHub Create Pull Request
Virtual Machines Overview of Maintenance Configurations for Azure virtual machines ...rticles/virtual-machines/maintenance-configurations.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 🔧 Windows Tools
Summary
The documentation mentions both Linux and Windows VMs are supported, and most content is platform-neutral. However, there is evidence of Windows bias: management options list Azure PowerShell before CLI, and the only code sample referenced is a PowerShell-based Azure Functions sample. No Linux-specific tools or shell examples are provided, and PowerShell is mentioned before CLI in several places. This may create friction for Linux users who prefer bash or native Linux tools.
Recommendations
  • Provide Linux/bash examples alongside or before PowerShell examples.
  • Reference CLI-based samples and repositories, not just PowerShell.
  • Explicitly mention that Azure CLI is cross-platform and provide links to Linux/macOS installation guides.
  • Ensure that management options and code samples are presented in a platform-neutral or Linux-first order.
  • Include troubleshooting steps or examples relevant to Linux environments.
GitHub Create Pull Request
Virtual Machines Advanced Configuration for MSP ...s/metadata-security-protocol/advanced-configuration.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 Missing Linux Example
Summary
The documentation provides examples and references that prioritize Windows environments. For instance, the WireServer schema example uses Windows-specific paths (e.g., 'C:\Windows\OEM\Unattend.wsf.exe') and process names ('winpa.exe', 'SYSTEM'), without offering equivalent Linux examples. The Linux-oriented example is limited to a generic Apache process, and there is no parity for common Linux provisioning agents or system users. Windows terminology and tooling are mentioned explicitly, while Linux equivalents are absent or less detailed.
Recommendations
  • Add Linux-specific examples for WireServer schema, such as using Linux provisioning agents (e.g., 'cloud-init', '/usr/bin/cloud-init', 'root' user).
  • Ensure that examples for process metadata, identities, and privileges include both Windows and Linux scenarios side-by-side.
  • Reference Linux system paths, users, and processes where applicable, not just Windows ones.
  • Clarify any platform-specific differences in GPA behavior or RBAC enforcement between Windows and Linux.
  • Avoid using Windows paths and process names exclusively in critical configuration examples.
GitHub Create Pull Request
Virtual Machines NV series migration guide ...-machines/migration/sizes/nv-series-migration-guide.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation displays a notable Windows bias. NVv4 VMs are stated to support only Windows guest OS, and all driver installation/setup links point to Windows-specific guides. There are no Linux migration steps, examples, or references to Linux driver installation or compatibility. FAQ and extension links are all Windows-focused, and Linux users are not provided with guidance or parity.
Recommendations
  • Explicitly state Linux support status for each VM series, including any limitations.
  • Provide Linux-specific migration steps, including driver installation and troubleshooting.
  • Add links to Linux GPU driver setup guides and extension documentation.
  • Include notes or tables comparing Windows and Linux support for each VM series.
  • If NVv4 does not support Linux, clarify this early and suggest alternatives for Linux users.
GitHub Create Pull Request
Virtual Machines Secure and use policies ...blob/main/articles/virtual-machines/security-policy.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 demonstrates some Windows bias, notably by referencing Windows tools (PowerShell) before Linux equivalents (CLI), and by occasionally presenting Windows examples or terminology first. In the Key Vault section, Azure PowerShell is mentioned for Windows VMs before Azure CLI for Linux VMs. The Azure RBAC section lists the Azure portal and PowerShell before CLI. Some links and examples are Windows-first or Windows-only, and antimalware coverage is discussed only for Windows, with Linux support explicitly excluded.
Recommendations
  • Present Linux and Windows examples side-by-side, or alternate which is listed first.
  • When mentioning tools, list Azure CLI and PowerShell together, or highlight CLI for cross-platform parity.
  • Where features are Windows-only (e.g., antimalware), provide Linux alternatives or clarify Linux best practices.
  • Ensure all linked guides and walkthroughs have Linux equivalents and are equally visible.
  • Avoid language that implicitly prioritizes Windows (e.g., 'for Windows VMs, use PowerShell; for Linux, use CLI').
GitHub Create Pull Request
Virtual Machines Create SSH keys with the Azure CLI ...b/main/articles/virtual-machines/ssh-keys-azure-cli.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Linux First Missing Windows Example
Summary
The documentation is strongly Linux-oriented, with all examples using Linux paths, Bash commands, and Linux file permission patterns. There are no Windows-specific examples, nor guidance for Windows users on how to generate, store, or use SSH keys (e.g., using PowerShell, Windows file paths, or PuTTY). This creates friction for Windows users who may not have Bash or native SSH tools available.
Recommendations
  • Add Windows-specific instructions and examples, such as using PowerShell or Windows Command Prompt to generate and use SSH keys.
  • Include guidance for using Windows-native tools like PuTTY or Windows OpenSSH client.
  • Show Windows file path formats in examples (e.g., C:\Users\username\.ssh\...).
  • Clarify any differences in workflow or prerequisites for Windows users (e.g., installing OpenSSH, using chmod alternatives).
  • Provide parity in example order, alternating or grouping by OS.
GitHub Create Pull Request
Virtual Machines Deploy a Trusted Launch VM ...ain/articles/virtual-machines/trusted-launch-portal.md
Medium Priority View Details →
Scanned: 2026-01-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 both Linux and Windows coverage for Azure Trusted Launch VMs, but there are several signs of Windows bias. PowerShell examples are exclusively for Windows (no Linux PowerShell Core parity), and Windows-specific tools and patterns (like RDP, BitLocker, and Windows image generalization) are mentioned more frequently and in greater detail. In PowerShell sections, only Windows VM creation is shown, with no Linux VM PowerShell example. In several places, Windows terminology and workflows are described first or in more depth than Linux equivalents.
Recommendations
  • Add PowerShell examples for Linux VM deployment (using PowerShell Core on Linux/macOS).
  • In PowerShell code samples, provide both Windows and Linux VM creation flows, or clarify which OS is being targeted.
  • When discussing image generalization, provide equal detail for Linux and Windows (currently, Windows is described more thoroughly).
  • Avoid Windows-first ordering in lists and examples; alternate or group by OS.
  • Where Windows-specific features (e.g., BitLocker, RDP) are mentioned, provide Linux equivalents or clarify their applicability.
  • Explicitly note when a tool or workflow is Windows-only, and suggest Linux/macOS alternatives where possible.
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-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 exhibits a moderate Windows bias. Many code samples, especially in CI/CD pipeline sections (GitHub Actions, Azure DevOps, GitLab, Jenkins), default to Windows application file types (e.g., app.exe, app-config.json) and set --os-type Windows by default, even when running on Linux agents. PowerShell examples are abundant and sometimes precede or outnumber Linux/bash equivalents. Some install script examples for Windows (.exe, .msi, .ps1) are more detailed than their Linux counterparts. In multi-platform sections, Windows tools and patterns (msiexec, powershell.exe, .exe installers) are mentioned first or exclusively, while Linux equivalents (e.g., .deb, .rpm, .sh) are present but less emphasized. There are cases where Linux-specific examples or instructions are missing or less detailed, especially in automation pipelines.
Recommendations
  • In CI/CD pipeline examples (GitHub Actions, Azure DevOps, GitLab, Jenkins), provide parallel Linux-centric samples (e.g., using .sh, .deb, .rpm files and --os-type Linux) and clarify how to deploy Linux applications.
  • When showing install script examples, ensure Linux formats (.sh, .tar, .deb, .rpm) are given equal prominence and detail as Windows formats.
  • Avoid defaulting to Windows file types (app.exe, app-config.json) in generic examples; use neutral or alternate Linux file types (app.sh, app-config.yaml) or show both.
  • In sections where --os-type is set, explain how to set for Linux and Windows, and provide both examples.
  • Balance PowerShell and bash examples, and avoid placing Windows/PowerShell instructions before Linux/bash unless contextually justified.
  • Explicitly call out Linux prerequisites, tools, and patterns where Windows tools are mentioned (e.g., mention unzip/tar for Linux when msiexec/tar for Windows is shown).
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-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 Azure CLI and PowerShell examples for creating VMs from gallery images, but PowerShell examples are significantly more detailed and tailored to Windows workflows. Windows-specific parameters and patterns (e.g., Set-AzVMOperatingSystem -Windows, RDP security rules, password creation dialogs) are prominent in PowerShell sections, and Windows VM creation is shown before Linux in several places. Linux examples are present, especially in CLI and REST, but PowerShell guidance is almost exclusively Windows-oriented, with little mention of Linux-specific PowerShell usage.
Recommendations
  • Add PowerShell examples for creating Linux VMs, including use of Set-AzVMOperatingSystem -Linux and SSH key authentication.
  • Ensure parity in parameter explanations for both Windows and Linux in PowerShell sections.
  • When showing VM creation steps, alternate or parallelize Windows and Linux examples, rather than presenting Windows first.
  • Clarify in PowerShell sections how to adapt commands for Linux VMs, not just Windows.
  • Review security group rules to include SSH (port 22) alongside RDP (port 3389) in PowerShell networking examples.
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-13 06:17
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 areas. In code examples for enabling Automatic Extension Upgrade, the extension type shown is 'DependencyAgentWindows' in REST API, PowerShell, and ARM template samples, with Linux equivalents either omitted or shown only in CLI examples. PowerShell examples are provided, but Bash or Linux-native scripting is not. Windows extension types and tools (PowerShell cmdlets) are mentioned first or exclusively in several sections, and Linux examples are less prominent or missing, especially in PowerShell and template sections.
Recommendations
  • Provide parallel examples for both Windows and Linux extension types in all code samples (REST API, PowerShell, ARM templates), not just CLI.
  • Include Bash or Linux-native scripting examples alongside PowerShell for automation tasks.
  • Alternate the order of Windows and Linux examples to avoid Windows-first presentation.
  • Explicitly mention Linux support in all procedural steps, not just in summary tables.
  • Where PowerShell is used, add equivalent instructions for Linux users (e.g., Azure CLI, Bash scripts).
GitHub Create Pull Request
Virtual Machines Azure VM Watch .../blob/main/articles/virtual-machines/azure-vm-watch.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page for Azure VM Watch demonstrates some Windows bias. Several health signals and checks are described as Windows-only (e.g., System Errors from Windows event log, Hardware Health Monitor via Windows event log), while their Linux equivalents are either missing or less detailed. In the Clock section, the fallback check for time sync is described specifically for Windows (w32tm), with no Linux equivalent mentioned. Windows tools and event logs are referenced directly, while Linux alternatives (such as syslog, journalctl, or chrony/ntpd for time sync) are not discussed. Although the page claims compatibility with both Linux and Windows, some critical monitoring features appear to be Windows-centric or lack Linux parity.
Recommendations
  • Add equivalent Linux examples and details for system error/event log collection (e.g., using syslog, journalctl, or /var/log/messages).
  • Describe how clock skew is checked on Linux VMs (e.g., using chrony, ntpd, or timedatectl), not just Windows (w32tm).
  • For hardware health monitoring, specify how disk and hardware events are collected on Linux (e.g., using SMART tools, dmesg, or syslog), not only via Windows event logs.
  • Ensure that all monitoring signals and checks have Linux equivalents or clearly state any platform limitations.
  • Present examples and tool references for both platforms side-by-side, rather than focusing on Windows tools first.
GitHub Create Pull Request
Virtual Machines Overview backup options for VMs ...blob/main/articles/virtual-machines/backup-recovery.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation generally presents backup options for both Windows and Linux VMs, but in the 'Managed snapshots' section, the only example link provided is for Windows ('Create copy of VHD stored as a Managed Disk'), with no equivalent Linux example or guidance. This creates a subtle bias, as Linux users may not find direct instructions or parity in example coverage.
Recommendations
  • Add a Linux-specific example or documentation link for creating managed disk snapshots, ensuring parity with the Windows example.
  • Explicitly mention that the snapshot process applies equally to Linux VMs, or clarify any differences if they exist.
  • Review other sections for example parity and ensure both platforms are equally represented in hands-on guides and references.
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 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 demonstrates a moderate Windows bias. Windows examples (especially PowerShell and CLI) are more detailed and appear first in several sections. There are multiple PowerShell examples for Windows, but no equivalent Bash or Linux-native scripting examples. CLI examples for Linux are present but less emphasized. Windows-specific tools and registry keys are mentioned in detail, while Linux equivalents (such as disabling automatic updates) are less thoroughly covered. The 'Next steps' section links only to Windows VM management.
Recommendations
  • Add Linux-native scripting examples (e.g., Bash) for enabling/disabling patching and for on-demand patch assessment/installation.
  • Present Linux and Windows examples in parallel, or alternate which OS is shown first in each section.
  • Expand coverage of Linux-specific patching tools and configuration steps (e.g., how to disable automatic updates for various distros, not just RHEL).
  • Include 'Next steps' links for both Linux and Windows VM management.
  • Where registry keys or Windows Update settings are discussed, provide Linux equivalents (e.g., apt/yum/dnf/zypper settings).
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
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 mild Windows bias by mentioning Windows-specific backup mechanisms (Volume Shadow Service, SQL Server Always On) before Linux equivalents, and linking to Windows-focused SQL Server articles. Linux tools (like fsfreeze) are referenced but with less detail and after Windows solutions. There are no Linux/Powershell command examples, but Windows technologies are described more thoroughly. No explicit Linux backup workflows or application-consistent backup examples are provided.
Recommendations
  • Provide equal detail for Linux backup tools and workflows (e.g., describe how to use fsfreeze or LVM snapshots for application-consistent backups on Linux).
  • Include links to Linux-focused documentation for database backup and disaster recovery (e.g., Oracle on Linux, PostgreSQL, MySQL).
  • Add example backup/restore commands for both Windows (PowerShell) and Linux (bash/CLI) environments.
  • Mention Linux-first solutions and tools in parallel with Windows ones, not after.
  • Clarify application-consistent backup options for Linux workloads, with practical guidance.
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-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 demonstrates a moderate Windows bias, especially in the ARM template section, which is heavily Windows-centric (Windows images, PowerShell DSC, Windows admin credentials). PowerShell examples are provided alongside CLI, but there is no equivalent Bash scripting or Linux-specific automation. The ARM template does not show how to deploy a Linux VMSS, and Windows terminology/tools (PowerShell DSC, WebDeploy) are referenced without Linux alternatives. CLI examples do use Ubuntu images, but the template and supporting text focus on Windows.
Recommendations
  • Add ARM template examples for Linux VMSS deployments, including Linux image references and configuration.
  • Provide Bash shell scripting examples for automation tasks, not just PowerShell.
  • In ARM template parameters, include both Windows and Linux OS options, with documentation on how to select and configure each.
  • Mention Linux equivalents for configuration management (e.g., cloud-init, custom script extension) instead of only PowerShell DSC.
  • Ensure examples and explanations are OS-neutral or show both Windows and Linux options side-by-side.
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-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 provides both Windows and Linux parity in CLI/API/Portal instructions, but there are notable signs of Windows bias. PowerShell examples (Windows-only) are given equal prominence as Azure CLI (cross-platform), and ARM template examples focus exclusively on Windows VM images and parameters. The ARM template omits any Linux image or configuration, and the password complexity guidance is tailored to Windows. In several places, Windows terminology and tools (PowerShell, Windows images) are mentioned before or instead of Linux equivalents.
Recommendations
  • Add ARM template examples for Linux VMs, including imageReference for popular Linux distributions (e.g., Ubuntu, CentOS).
  • In ARM template parameters, include both Windows and Linux OS options, with clear documentation for each.
  • Where password complexity is discussed, clarify differences for Linux VMs (e.g., SSH keys vs. passwords).
  • Ensure examples and instructions alternate or balance Windows and Linux references, rather than defaulting to Windows first.
  • Consider adding Bash shell examples for common operations, especially for Linux users.
  • Review terminology and ensure it is inclusive of both Windows and Linux workflows.
GitHub Create Pull Request
Virtual Machines Proximity placement groups ...ocs/blob/main/articles/virtual-machines/co-location.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First Missing Linux Example
Summary
The documentation references both Linux and Windows VMs as supported, but there are several signs of Windows bias. PowerShell is mentioned explicitly and described before CLI in sections about checking colocation status, and the PowerShell cmdlet is given with more detail than the CLI equivalent. There are no explicit Linux-specific examples or commands, and the CLI is mentioned only after PowerShell. The best practices section links to both Linux and Windows accelerated networking guides, but the Windows (PowerShell) link is listed second. There are no Bash or Linux-native command examples, and no mention of Linux-specific tooling or workflows.
Recommendations
  • Provide Linux/Bash command examples alongside PowerShell, especially for common tasks like checking colocation status.
  • Mention Azure CLI before or alongside PowerShell to avoid Windows-first bias.
  • Include explicit Linux workflow guidance (e.g., using Bash, cloud-init, or Linux-native tools) where relevant.
  • Ensure parity in detail and clarity between CLI and PowerShell instructions.
  • Add Linux-specific troubleshooting tips if any exist.
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-13 06:17
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides examples for ARM templates, Azure CLI, and PowerShell, with PowerShell (a Windows-centric tool) given equal prominence to Azure CLI. The mention of Visual Studio Code as the IDE is neutral, but PowerShell is listed as a primary method for accessing vmWatchSettings, which may create friction for Linux/macOS users who typically use Bash or shell scripting. There are no explicit Bash or Linux shell examples, and PowerShell is referenced before any Linux-specific alternatives.
Recommendations
  • Add explicit Bash or shell examples for Linux/macOS users alongside PowerShell examples.
  • Clarify that Azure CLI commands work cross-platform and provide sample Linux/macOS shell usage (e.g., with environment variables, piping, etc.).
  • If PowerShell is mentioned, also mention Bash or other common Linux shells to ensure parity.
  • Consider listing CLI (cross-platform) examples before PowerShell (Windows-centric) examples.
  • Note any platform-specific differences in command syntax or required tools.
GitHub Create Pull Request
← Previous Page 11 of 33 Next →