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 451-475 of 818 flagged pages
Virtual Machines How to Connect to the Azure Image Builder build VM ...al-machines/linux/image-builder-connect-to-build-vm.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. Windows terminology (RDP, WinRM) is frequently mentioned, and Windows examples or documentation links are often listed before or alongside Linux equivalents. Some sections, such as password reset instructions, reference the Azure portal's 'Reset Password' blade, which is primarily relevant for Windows VMs. The Azure Bastion section refers to connecting to a Windows VM using SSH or RDP, but does not provide explicit Linux SSH instructions or examples. The Serial Console documentation link points to a Windows-focused page. Linux-specific connection methods and troubleshooting steps are less detailed or referenced after Windows options.
Recommendations
  • Provide explicit Linux SSH connection instructions and examples alongside or before Windows RDP/WinRM examples.
  • Link to Linux-specific documentation for Azure Serial Console and Bastion, not just Windows-focused pages.
  • Clarify which instructions (such as password reset) apply to Linux VMs, and provide Linux-specific guidance if the process differs.
  • Ensure that Linux connection methods (SSH, etc.) are described with equal detail and prominence as Windows methods.
  • Avoid using Windows-centric terminology (e.g., RDP, WinRM) without also referencing Linux equivalents (SSH).
GitHub Create Pull Request
Virtual Machines Azure VM Image Builder service DevOps task (preview) ...es/virtual-machines/linux/image-builder-devops-task.md
Medium Priority View Details →
Scanned: 2026-01-12 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 demonstrates a moderate Windows bias. Windows-specific tools (PowerShell) and terminology are frequently mentioned, often before or in more detail than their Linux equivalents. Windows examples and instructions (e.g., PowerShell commands, Windows Update task, directory paths) are given first or exclusively in several sections, while Linux instructions are sometimes less detailed or presented as secondary. Some features (like Windows Restart or elevated commands) are noted as unsupported, but workarounds or Linux alternatives are not always explained. The overall structure and examples favor Windows users, creating friction for Linux/macOS users.
Recommendations
  • Present Linux and Windows examples side-by-side or alternate which is shown first.
  • Expand Linux-specific instructions and examples to match the detail given for Windows (e.g., more bash script samples, troubleshooting steps).
  • Include Linux/macOS tool references (e.g., bash, sh) wherever PowerShell is mentioned.
  • Clarify Linux-specific limitations and provide workarounds or alternatives.
  • Explicitly state Linux/macOS support and parity in feature lists and prerequisites.
  • Where features are Windows-only or unsupported, provide equivalent Linux guidance or note the absence.
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-12 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 exhibits moderate Windows bias. Windows tools (PowerShell, Sysprep, WinRM, Windows-specific error codes) are frequently mentioned, often with detailed examples and troubleshooting steps. Linux equivalents (waagent, SSH, shell scripts) are referenced but generally with less detail and sometimes only as secondary notes. Some troubleshooting sections and examples (e.g., Sysprep, Windows Update, restart errors) are Windows-centric, with Linux guidance either missing or less emphasized.
Recommendations
  • Ensure Linux troubleshooting examples are provided alongside Windows ones, with equal detail (e.g., show waagent errors, Linux restart issues, Linux-specific log analysis).
  • Present Linux and Windows commands in parallel, rather than Windows-first (e.g., show Azure CLI and shell examples before PowerShell).
  • Expand Linux-specific error scenarios and solutions, such as permissions, SSH connectivity, and customization failures.
  • Reference Linux documentation and support resources as prominently as Windows ones.
  • Where Windows tools (PowerShell, Sysprep) are explained in detail, provide similar depth for Linux tools (waagent, shell scripting, systemd, etc.).
GitHub Create Pull Request
Virtual Machines Create and upload an Oracle Linux VHD ...les/virtual-machines/linux/oracle-create-upload-vhd.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page exhibits a Windows bias by exclusively referencing Hyper-V (a Windows virtualization tool) for VHD creation and management, providing links to Windows-specific instructions, and using Hyper-V Manager for VM operations. There are no examples or guidance for equivalent Linux tools (such as KVM, qemu-img, or VirtualBox) for creating or managing VHDs, nor are Linux workflows mentioned for tasks like shutting down the VM or converting disk formats. Windows/Hyper-V tools and patterns are mentioned first and exclusively, which may create friction for Linux users.
Recommendations
  • Add instructions and examples for creating and managing VHDs using Linux-native tools (e.g., KVM, qemu-img, VirtualBox).
  • Provide Linux command-line equivalents for VM operations such as shutdown, disk conversion, and management.
  • Include links to Linux-specific documentation for virtualization and VHD creation.
  • Present both Windows and Linux workflows in parallel, or prioritize Linux examples given the target audience (Oracle Linux on Azure).
GitHub Create Pull Request
Virtual Machines Quickstart: Create a Linux VM cluster in Azure using Terraform ...rtual-machines/linux/quick-cluster-create-terraform.md
Medium Priority View Details →
Scanned: 2026-01-12 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 verifying results, but Azure PowerShell (a Windows-centric tool) is presented as a primary tab alongside Azure CLI. The PowerShell example is included even though the scenario is focused on Linux VM clusters, and PowerShell is not natively available on most Linux distributions. There are no Linux shell-specific examples (e.g., Bash, SSH, SCP) for interacting with the deployed VMs, nor is there mention of Linux-native tooling for verification.
Recommendations
  • Prioritize Azure CLI and Bash examples over PowerShell in the verification steps, as these are more universally available across platforms.
  • Add Linux shell (Bash) commands for verifying VM status, such as using SSH to connect to the VMs or using az CLI from a Linux shell.
  • If PowerShell is included, clarify its cross-platform availability and provide installation guidance for Linux/macOS users.
  • Consider removing or de-emphasizing PowerShell examples in Linux-focused documentation unless there is a clear cross-platform rationale.
GitHub Create Pull Request
Virtual Machines Run scripts in a Linux VM in Azure using managed Run Commands ...articles/virtual-machines/linux/run-command-managed.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
While the documentation is focused on Linux VMs and provides Azure CLI examples for Linux shell scripts, there is a notable bias toward PowerShell and Windows-centric tooling. Many advanced examples and features (such as output streaming, SAS token generation, and parameter passing) are only demonstrated using PowerShell cmdlets, with little or no equivalent Azure CLI or Linux-native command coverage. REST and ARM template examples often use PowerShell script syntax (Write-Host, .ps1), and instructions for generating SAS tokens reference PowerShell tools first. Some sections (e.g., parameter passing, output blob streaming) lack Linux CLI parity, and Windows terminology (e.g., 'myscript.ps1', 'ipconfig') appears before or instead of Linux equivalents.
Recommendations
  • Provide Azure CLI examples for all advanced scenarios currently covered only by PowerShell (e.g., output/error blob streaming, parameter passing, long-running scripts).
  • Use Linux shell script syntax (e.g., .sh, echo) in REST and ARM template examples, or show both Windows and Linux script examples side by side.
  • Reference Linux-native tools for SAS token generation and blob management (e.g., az storage blob generate-sas) before or alongside PowerShell equivalents.
  • Ensure command IDs and examples use Linux-relevant commands (e.g., ifconfig, bash scripts) and avoid Windows-first terminology (e.g., ipconfig, .ps1) unless explicitly targeting Windows.
  • Clarify differences in parameter passing and script invocation between Linux and Windows, with explicit Linux examples.
GitHub Create Pull Request
Virtual Machines Run scripts in a Linux VM in Azure using action Run Commands ...ob/main/articles/virtual-machines/linux/run-command.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation is focused on Linux VMs but includes several PowerShell examples and references to Windows-centric tooling (PowerShell cmdlets). PowerShell is not a native Linux tool, and its use may create friction for Linux users. The PowerShell example is presented alongside Azure CLI, but the CLI example is more prominent. There are references to differences between Linux and Windows logs, with Windows-specific log lines described first. The documentation does not provide any Bash or shell script examples for local execution, nor does it mention Linux-native tools for scripting or automation.
Recommendations
  • Replace or supplement PowerShell examples with Bash or shell script equivalents, especially for local execution scenarios.
  • Ensure Azure CLI examples are presented before PowerShell, as CLI is more common for Linux users.
  • Clarify that PowerShell is optional and not required for Linux VM management.
  • Provide troubleshooting steps using Linux-native tools and commands.
  • When discussing differences between Linux and Windows, describe Linux behavior first.
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
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation page consistently presents Hyper-V (a Windows technology) as the first and primary example for preparing RHEL VHDs for Azure. References to Windows tools (Hyper-V Manager, convert-vhd cmdlet) are prominent and appear before Linux alternatives. While Linux hypervisors (KVM, VMware, Kickstart) are covered in detail, the initial guidance and prerequisites direct users to Windows-centric workflows, and Windows tools are mentioned without equal Linux alternatives in some places.
Recommendations
  • Reorder sections so that Linux-native hypervisors (KVM, VMware, Kickstart) are presented before or alongside Hyper-V, not after.
  • In the prerequisites, mention Linux tools (e.g., qemu-img, virt-manager) for VHD creation and conversion before or alongside Windows tools.
  • Where Windows-specific tools (Hyper-V Manager, convert-vhd cmdlet) are referenced, provide direct Linux equivalents (e.g., qemu-img commands) in the same context.
  • Add explicit guidance for performing all steps on Linux-only environments, including VHD conversion, disk alignment, and VM creation.
  • Ensure that references to Windows documentation are balanced with links to Linux documentation or community resources.
GitHub Create Pull Request
Virtual Machines Run scripts in an Azure Linux VM ...n/articles/virtual-machines/linux/run-scripts-in-vm.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Windows First Powershell Heavy Missing Linux Example
Summary
The documentation, while titled and scoped for Linux VMs, repeatedly references Windows-specific tools and scripting languages (PowerShell) alongside Linux options. Several features (Run Command, Hybrid Runbook Worker) highlight PowerShell and Windows usage, sometimes before mentioning Bash or Python. The Hybrid Runbook Worker section links only to Windows installation instructions, omitting Linux setup guidance. No concrete Linux script examples or Linux-specific tool usage are provided.
Recommendations
  • Provide explicit Linux script examples (e.g., Bash, Python) for each feature, not just mention Bash generically.
  • Ensure Linux installation instructions for Hybrid Runbook Worker are included and linked.
  • Reorder lists and descriptions to mention Linux tools and scripting languages first, given the page's Linux focus.
  • Add Linux-specific troubleshooting tips and usage patterns for each feature.
  • Avoid referencing Windows-only tools (e.g., PowerShell Workflow, Graphical runbooks) unless Linux equivalents are also described.
GitHub Create Pull Request
Virtual Machines Overview of Azure Disk Storage ...in/articles/virtual-machines/managed-disks-overview.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation page exhibits mild Windows bias in several areas. Windows terminology, tools, and links are often presented first or exclusively, such as references to Sysprep, MBR/GPT partitioning with Windows links, and PowerShell. Some sections (e.g., image creation) link only to Windows-specific guides, and Windows drive letters are mentioned before Linux device paths. Linux equivalents are present in some places but are less prominent or relegated to secondary mentions.
Recommendations
  • Ensure all example links (e.g., image creation, disk upload) have both Linux and Windows versions, and present them side-by-side or in a neutral order.
  • When discussing partitioning (MBR/GPT), include Linux-specific links (e.g., to parted, gdisk, or relevant Linux documentation) and explain how partitioning works on Linux VMs.
  • Mention Linux device paths (e.g., /dev/sda) alongside Windows drive letters when describing disk roles and usage.
  • Avoid referencing Windows-specific tools (e.g., Sysprep, PowerShell) without also mentioning Linux equivalents (e.g., waagent, Azure CLI).
  • Where cluster managers are discussed, give equal prominence to Linux options (e.g., Pacemaker) as to Windows Server Failover Cluster.
GitHub Create Pull Request
Virtual Machines Advanced Configuration for MSP ...s/metadata-security-protocol/advanced-configuration.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation provides a Windows-specific example (with a Windows file path and SYSTEM user) before any Linux example, and does not offer equivalent Linux/macOS examples for process identity rules. Windows tools and patterns (e.g., C:\Windows\OEM\Unattend.wsf.exe, SYSTEM user) are mentioned exclusively in the WireServer schema example, while Linux process identity examples are limited to generic paths and group names. No explicit Linux/macOS-specific guidance or parity is provided for configuring RBAC rules based on Linux process metadata.
Recommendations
  • Add Linux/macOS-specific examples for process identity rules, such as using /usr/bin/nginx, user 'root', or group 'www-data'.
  • Provide parallel examples for both Windows and Linux in all schema expansions, especially for WireServer.
  • Explicitly mention how Linux/macOS users can determine process names, executable paths, and user/group names for rule authoring.
  • Avoid presenting Windows examples first or exclusively; alternate or combine with Linux/macOS examples.
  • Clarify any platform-specific differences in process metadata handling.
GitHub Create Pull Request
Virtual Machines Specify Marketplace purchase plan information using Azure PowerShell ...b/main/articles/virtual-machines/marketplace-images.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page is heavily focused on Azure PowerShell, with all CLI examples provided in PowerShell syntax. There are no equivalent examples using Azure CLI (az), Bash, or Linux-native tools, despite the page stating applicability to Linux VMs. Windows-centric tools and patterns (e.g., PowerShell cmdlets, Windows networking conventions) are used exclusively and referenced first. The linked resources also point to Windows/PowerShell documentation. This creates friction for Linux/macOS users who may not have or use PowerShell.
Recommendations
  • Add equivalent Azure CLI (az) and Bash examples for all major steps, including retrieving VM plan info, creating image definitions, and deploying VMs.
  • Explicitly mention cross-platform alternatives and clarify which steps can be performed on Linux/macOS.
  • Update references and links to include both Windows/PowerShell and Linux/CLI documentation.
  • Consider reordering examples so that cross-platform (CLI/Bash) instructions appear before or alongside PowerShell examples.
GitHub Create Pull Request
Virtual Machines Deploy a VM or Virtual Machine Scale Set with MSP ...tual-machines/metadata-security-protocol/greenfield.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page exhibits Windows bias by explicitly describing the Windows provisioning process for GuestProxyAgent (GPA) as simpler and not providing equivalent Linux-specific examples or guidance. The warning highlights a difference in procedure but does not offer step-by-step instructions or ARM template samples for Linux users, nor does it mention Linux tooling or commands. All examples and references are generic or Windows-centric.
Recommendations
  • Add explicit Linux provisioning steps, including how to configure GPA after VM/VMSS creation.
  • Provide ARM template or REST API examples tailored for Linux VMs, clarifying any differences.
  • Include Linux command-line (e.g., Bash, Azure CLI) examples alongside Windows/PowerShell where appropriate.
  • Clarify any limitations or required manual steps for Linux users, and link to detailed Linux guidance if available.
GitHub Create Pull Request
Virtual Machines Frequently Asked Questions About MSP ...les/virtual-machines/metadata-security-protocol/faq.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation displays a Windows bias in its explanation of provisioning and agent installation. It references the 'Windows philosophy' as the default model, discusses GPA installation as a step available in Windows but not Linux, and does not provide Linux-specific examples or guidance for checking MSP status or installing GPA. The lack of Linux command-line examples and the framing of Windows patterns as normative create friction for Linux users.
Recommendations
  • Provide explicit Linux command-line examples (e.g., using curl, jq, or bash) for checking MSP status and component health.
  • Describe Linux-native workflows for GPA installation and MSP enablement, including any supported VM extension mechanisms.
  • Avoid framing Windows patterns as the default or preferred model; present both Windows and Linux approaches equally.
  • Clarify any differences in agent management between Windows and Linux, and offer guidance for Linux users to achieve parity.
GitHub Create Pull Request
Virtual Machines Convert Audit Logs to an Allowlist ...ecurity-protocol/other-examples/audit-logs-to-rules.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools Windows Examples In Schema
Summary
The documentation demonstrates a moderate Windows bias. Windows-specific tools (PowerShell, .exe allowlist generator) and examples (sample identities, schema) are presented first or exclusively, and the PowerShell workflow is far more detailed than the CLI (Linux/macOS-friendly) workflow. The allowlist generator tool is only available as a Windows executable. Sample schemas and identities are Windows-centric, with little parity for Linux processes. Linux instructions are present but less detailed and less emphasized.
Recommendations
  • Provide equal depth and step-by-step guidance for Linux/macOS users using Azure CLI and ARM templates.
  • Offer a cross-platform version of the allowlist generator tool (e.g., Python, .NET Core, or containerized).
  • Include Linux process examples and sample identities in the rules schema.
  • List CLI instructions before or alongside PowerShell instructions, not after.
  • Explicitly mention macOS compatibility where relevant.
  • Ensure screenshots and sample outputs include both Windows and Linux cases.
GitHub Create Pull Request
Virtual Machines Metadata Security Protocol (MSP) ...irtual-machines/metadata-security-protocol/overview.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation lists Windows operating systems first in compatibility, and provides a warning that Windows users can enable GuestProxyAgent (GPA) from an ARM template, while Linux users must follow a more complex, two-step process. No Linux-specific example or workaround is provided for GPA configuration, and the documentation does not elaborate on Linux tooling or patterns for MSP setup.
Recommendations
  • Provide explicit Linux configuration steps for enabling GPA, including example commands and tooling.
  • Offer ARM template snippets or automation guidance for Linux users, if possible.
  • List supported Linux distributions before or alongside Windows in compatibility sections to avoid Windows-first perception.
  • Clarify any differences in process for Linux and Windows, and offer parity where feasible.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation demonstrates a Windows bias by referencing only Windows guest OS support for NVv4 VMs, linking exclusively to Windows-specific driver installation guides and extensions, and omitting Linux migration steps, driver instructions, or parity notes. Linux users are left without guidance for migration, driver setup, or troubleshooting, especially for NVsv3, which does support Linux.
Recommendations
  • Include explicit Linux migration steps and considerations for supported VM series (e.g., NVsv3).
  • Provide links to Linux-specific GPU driver installation guides and extension documentation.
  • Clarify which VM series support Linux and which are Windows-only, ideally in a summary table.
  • Add FAQ entries addressing Linux scenarios, such as driver compatibility and extension support.
  • Ensure parity in example commands, instructions, and troubleshooting for both Windows and Linux users.
GitHub Create Pull Request
Virtual Machines Move resources associated with a maintenance configuration to another region ...nes/move-region-maintenance-configuration-resources.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell commands are presented first and in more detail, with variable examples using PowerShell syntax. The main migration instructions link to a Windows-specific tutorial (toc/breadcrumb paths include 'windows'), and PowerShell is mentioned before CLI throughout. While CLI examples are provided, Linux/macOS users may find the ordering and emphasis on PowerShell and Windows navigation patterns less intuitive.
Recommendations
  • Provide Bash variable examples alongside PowerShell examples for variable setup.
  • Alternate the order of PowerShell and CLI instructions, or present CLI first to balance platform emphasis.
  • Ensure migration instruction links point to platform-neutral or Linux/macOS-specific guides where possible.
  • Clarify that CLI commands work on Linux/macOS and provide any OS-specific caveats.
  • Add explicit notes or sections for Linux/macOS users, especially in navigation and troubleshooting.
GitHub Create Pull Request
Virtual Machines SCSI to NVMe for Linux VMs ...docs/blob/main/articles/virtual-machines/nvme-linux.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation, while focused on Linux VMs, relies heavily on PowerShell-based workflows and examples for migration, controller checks, and script execution. Windows-centric tools (PowerShell, Azure CLI in PowerShell syntax) are used for critical steps, and PowerShell instructions are presented before any Linux-native alternatives. There is minimal guidance for performing these tasks using native Linux tools or shell commands, creating friction for Linux/macOS users who may not use PowerShell.
Recommendations
  • Provide equivalent Linux shell (bash) commands for all PowerShell examples, especially for checking VM controller types and running migration scripts.
  • Offer instructions for using Azure CLI in bash (native Linux syntax), not just PowerShell.
  • Include guidance for downloading and running migration scripts directly from a Linux terminal, without requiring PowerShell.
  • Clarify whether the migration script can be run in Azure Cloud Shell (bash) or on a local Linux system, and provide steps for both.
  • Move Linux-native instructions and examples before PowerShell/Windows-centric ones, or present them side-by-side.
  • Explicitly state any prerequisites or limitations for Linux/macOS users regarding the migration process.
GitHub Create Pull Request
Virtual Machines Troubleshoot MSP ...hines/metadata-security-protocol/troubleshoot-guide.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation page exhibits a moderate Windows bias. Windows troubleshooting steps and service names are frequently presented first, and Windows-specific tools (such as 'sc query') are used in examples. Some troubleshooting commands for Windows (e.g., checking service status) are shown, but equivalent Linux commands (e.g., 'systemctl status') are missing or less detailed. In some sections, only Windows service checks are provided, or the Windows example is shown before the Linux one, even when both platforms are supported.
Recommendations
  • Provide Linux equivalents for all Windows troubleshooting commands (e.g., show 'systemctl status' for Linux services alongside 'sc query' for Windows).
  • Present Windows and Linux instructions in parallel, or alternate which platform is shown first to avoid implicit prioritization.
  • Include explicit Linux command examples for checking eBPF and GPA status, such as 'systemctl status azure-proxy-agent', 'lsmod', or 'journalctl'.
  • Ensure all troubleshooting steps are equally detailed for both platforms, including log locations, error codes, and service management.
  • Where Windows-specific tools or patterns are mentioned, add notes or alternatives for Linux users.
GitHub Create Pull Request
Virtual Machines Migrate Managed image to Compute gallery ...igration/migration-managed-image-to-compute-gallery.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation provides migration instructions for both Linux and Windows VMs, but example scripts are given for Azure CLI and PowerShell, with PowerShell (a Windows-centric tool) featured as a dedicated tab. The CLI example uses Azure CLI, which is cross-platform, but the PowerShell example is Windows-focused and presented equally. There are no Linux shell-specific examples (e.g., Bash), nor is there mention of Linux-native scripting or tools. The ordering of examples (CLI, then PowerShell) is neutral, but the presence of PowerShell as a primary method may signal Windows bias.
Recommendations
  • Add explicit Bash shell examples for Linux users, showing equivalent steps using Azure CLI in a Linux shell context.
  • Clarify that Azure CLI commands are cross-platform and provide any Linux-specific nuances (such as authentication differences).
  • Consider adding a note or tab for Linux/macOS users, highlighting any differences or confirming parity.
  • If PowerShell is shown, also show Bash or other Linux-native scripting examples for parity.
GitHub Create Pull Request
Virtual Machines Monitoring data reference for Azure Virtual Machines ...main/articles/virtual-machines/monitor-vm-reference.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. Several log tables and data collection methods are described with explicit references to Windows-specific tools (e.g., Windows Event Log, IIS logs, Windows DNS servers, Windows Security Events, Windows Firewall). These Windows-centric tables and collection methods are listed before or more prominently than their Linux equivalents. While Linux support is present (e.g., Syslog, Linux Daemons), Linux examples and tools are less detailed, and some sections lack parity in Linux-specific instructions or examples. The only explicit example link provided is for Linux (collecting Percentage CPU metric), but most references and log tables are Windows-first or Windows-only.
Recommendations
  • Add equivalent Linux examples and instructions wherever Windows tools or logs are mentioned (e.g., provide examples for collecting Linux audit logs, firewall logs, and DNS events).
  • Ensure Linux-specific monitoring tables and data collection methods are described with equal detail and prominence.
  • Where Windows-only features are listed (e.g., IIS logs, Windows Event Log), clarify Linux alternatives or note limitations.
  • Present examples and tables in a way that alternates or balances Windows and Linux content, rather than listing Windows first.
  • Include explicit Linux/macOS usage scenarios and troubleshooting tips alongside Windows ones.
GitHub Create Pull Request
Virtual Machines Tutorial - Move Azure single instance Virtual Machines from regional to zonal availability zones ...achines/move-virtual-machines-regional-zonal-portal.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page primarily describes how to move Azure VMs using the Azure Portal, which is cross-platform. However, in the prerequisites and next steps, it references Windows-specific documentation and PowerShell, with no mention of Linux/macOS equivalents or Azure CLI examples. The link to check VM SKU availability points to a Windows/PowerShell-specific page, and the 'Next steps' section only references PowerShell or CLI, but the main page does not provide any CLI examples or parity guidance for Linux/macOS users.
Recommendations
  • Include Azure CLI examples alongside PowerShell for all steps, especially in 'Next steps' and any referenced guides.
  • Ensure links to prerequisite tasks (e.g., checking VM SKU availability) point to both Windows/PowerShell and Azure CLI/Linux documentation.
  • Explicitly mention that all steps can be performed via CLI on Linux/macOS and provide direct links or inline examples.
  • Add a note clarifying platform parity and guiding users to platform-appropriate tools.
GitHub Create Pull Request
Virtual Machines Network security group test ...ticles/virtual-machines/network-security-group-test.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by exclusively using RDP (Remote Desktop Protocol) as the example for testing inbound connections, which is only relevant to Windows VMs. There are no equivalent Linux examples (such as SSH) provided, and the inbound test walkthrough implicitly prioritizes Windows scenarios. Although both Linux and Windows VM creation links are mentioned in prerequisites, the actual test instructions and screenshots focus solely on Windows use cases.
Recommendations
  • Add a parallel example for Linux VMs, such as testing inbound SSH (port 22) connections, with step-by-step instructions and screenshots.
  • Explicitly state that the inbound test can be used for other protocols/services (e.g., SSH for Linux, HTTP/HTTPS for web servers) and provide example values.
  • Ensure that both Windows and Linux scenarios are covered equally in all sections, including troubleshooting advice.
  • Consider alternating the order of examples or providing a combined table for common protocols (RDP, SSH, HTTP, etc.) to avoid Windows-first presentation.
GitHub Create Pull Request
Virtual Machines Troubleshoot restore point failures ...cles/virtual-machines/restore-point-troubleshooting.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Windows First Powershell Heavy Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. Windows-specific tools (services.msc, Control Panel, Event Viewer, COM+, VSS, Visual C++ Redistributable) are referenced frequently, often without Linux equivalents or alternatives. Troubleshooting steps and error resolutions for Windows are more detailed and provided first, while Linux instructions are shorter and sometimes lack direct analogs (e.g., for COM+, VSS, Visual C++ Redistributable). Some troubleshooting steps reference PowerShell and Windows portal workflows before mentioning CLI or Linux methods.
Recommendations
  • Provide Linux equivalents for all troubleshooting steps involving Windows-only tools (e.g., services.msc, Event Viewer, COM+, VSS).
  • Add Linux-specific error codes and troubleshooting guidance where only Windows errors are described.
  • Ensure CLI and Linux commands/examples are presented alongside or before Windows/PowerShell instructions.
  • Clarify which steps are OS-specific and offer parity in depth and clarity for both platforms.
  • Reference Linux package managers and system tools (e.g., systemctl, journalctl, dmesg) where appropriate.
GitHub Create Pull Request
← Previous Page 19 of 33 Next →