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 326-350 of 818 flagged pages
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-13 06:17
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
While the documentation is focused on Linux VMs and provides extensive Azure CLI examples (which are cross-platform), the PowerShell section is much longer, more detailed, and introduces Windows-centric tools and terminology (e.g., New-AzStorageBlobSASToken, PowerShell script examples, references to Windows VM behaviors). Some examples and notes reference Windows-specific patterns before Linux equivalents, and certain explanations (such as parameter passing) discuss Windows first. REST and ARM template examples sometimes use PowerShell scripts (.ps1) as the default, even in Linux contexts.
Recommendations
  • Balance the depth of Azure CLI and PowerShell sections, ensuring Linux users have equally detailed CLI examples for all advanced scenarios (e.g., output streaming, parameter passing, long-running scripts).
  • Replace or supplement PowerShell-specific notes and examples with Bash or shell script equivalents, especially in REST and ARM template sections.
  • When discussing parameter passing, present Linux patterns first or side-by-side with Windows patterns.
  • Avoid referencing Windows-only tools (e.g., New-AzStorageBlobSASToken) without Linux alternatives or CLI equivalents.
  • Ensure all examples referencing scripts use .sh files for Linux contexts, not .ps1.
  • Add explicit Bash/shell script examples for advanced scenarios currently only shown in PowerShell.
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-13 06:17
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation page presents instructions for preparing a Red Hat Enterprise Linux VHD for Azure, covering multiple hypervisors (Hyper-V, KVM, VMware, Kickstart). However, there is a notable Windows bias: Hyper-V (a Windows-only hypervisor) is consistently presented first in all tabbed sections and referenced in the prerequisites and workflow steps. Windows-centric tools and links (such as Hyper-V Manager and PowerShell cmdlets like convert-vhd) are mentioned before Linux alternatives (like qemu-img). The prerequisites and initial guidance direct users to Windows documentation and tools, even though Linux-native workflows are fully supported and described later in the page.
Recommendations
  • Reorder tabbed sections so that Linux-native hypervisors (KVM, VMware, Kickstart) are presented before or alongside Hyper-V, especially since the target audience is preparing Linux VMs.
  • In the prerequisites, mention both Windows (Hyper-V) and Linux (KVM, qemu-img) tools and workflows equally, with direct links to Linux documentation and resources.
  • Where disk conversion is discussed, present qemu-img (Linux) and convert-vhd (Windows/PowerShell) side by side, rather than prioritizing Windows tools.
  • Clarify that all steps can be performed on Linux hosts, and provide explicit guidance for Linux-only environments.
  • Avoid language that assumes Windows as the default platform for virtualization or image preparation.
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-13 06:17
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page, while focused on Linux VMs, repeatedly references Windows-specific tools (PowerShell, PowerShell Workflow) and installation instructions for Windows (Hybrid Runbook Worker). In several sections, PowerShell and Windows scripting are mentioned before Bash/Linux equivalents. There are no concrete Linux script examples, and some features (like Hybrid Runbook Worker) link only to Windows installation guides, creating friction for Linux users.
Recommendations
  • Provide explicit Bash and Python script examples for Linux VMs in each section.
  • Ensure installation instructions for Hybrid Runbook Worker include Linux-specific steps and links.
  • Mention Linux tools and patterns (e.g., shell scripts, cron jobs) before or alongside Windows/PowerShell references.
  • Clarify which features are cross-platform and which are Windows-only, with clear guidance for Linux users.
  • Balance references to PowerShell with Bash and Python, especially in lists and feature descriptions.
GitHub Create Pull Request
Virtual Machines Time sync for Linux VMs in Azure ...blob/main/articles/virtual-machines/linux/time-sync.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 Reference Powershell Example
Summary
The documentation is focused on Linux VM time sync in Azure and provides comprehensive Linux-specific guidance, examples, and tooling. However, there is a notable Windows bias in the introductory sections, which discuss Windows Server 2016 time sync improvements in detail and link to Windows documentation before any Linux-specific technical content is introduced. Additionally, a PowerShell example is provided for base64 encoding cloud-init data, rather than a Linux shell equivalent, which may create friction for Linux users.
Recommendations
  • Move Windows-specific background information to a separate section or appendix, and begin the main content with Linux-relevant details.
  • Provide Linux shell (e.g., base64) examples alongside or instead of PowerShell for tasks like encoding cloud-init data.
  • Ensure that all external links in 'Next steps' and 'Notes' include Linux-relevant resources, not just Windows documentation.
  • If referencing Azure infrastructure, clarify its relevance to Linux users and avoid implying that Windows features directly affect Linux VM configuration.
  • Consider adding a brief comparison table of time sync mechanisms across platforms if cross-platform context is needed.
GitHub Create Pull Request
Virtual Machines Maintenance Configurations for Azure Virtual Machines using Bicep ...s/virtual-machines/maintenance-configurations-bicep.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation provides a single example of template execution using PowerShell syntax (with Windows-style paths and backslashes), and does not offer a Linux/macOS equivalent (e.g., Bash or CLI with forward slashes). The only command-line example is Windows-centric, which may cause friction for Linux/macOS users. The Bicep templates themselves are cross-platform, but the operational instructions favor Windows.
Recommendations
  • Include equivalent Azure CLI example using Bash syntax (forward slashes, suitable for Linux/macOS terminals).
  • Add a note clarifying that the az CLI works on all platforms and provide platform-specific command examples.
  • Show both Windows and Linux/macOS command-line examples side-by-side for template deployment.
  • Avoid using only backslashes in file paths; show both .\ds.bicep (Windows) and ./ds.bicep (Linux/macOS).
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-13 06:17
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 are presented first and in greater detail. The allowlist generator tool is only available as a Windows executable, and sample schemas and identities are Windows-centric. PowerShell instructions are extensive, while Linux/macOS alternatives (such as Bash or cross-platform scripting) are not provided. CLI instructions do include Linux, but the overall workflow and examples favor Windows.
Recommendations
  • Provide a cross-platform version of the allowlist generator tool (e.g., a Python script or .NET Core binary).
  • Add Bash or shell script examples for Linux/macOS users, especially for tasks currently covered only by PowerShell.
  • Include Linux-specific sample identities and process names in the rules schema examples.
  • Present CLI instructions before or alongside PowerShell instructions to emphasize platform neutrality.
  • Explicitly mention macOS support and provide relevant examples if applicable.
GitHub Create Pull Request
Virtual Machines Manage Virtual Machine restore points ...ain/articles/virtual-machines/manage-restore-points.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools Windows First
Summary
The documentation page exclusively provides Azure PowerShell examples for managing VM restore points, with no CLI, Bash, or Linux/macOS-specific instructions. All code samples use PowerShell syntax, and there is no mention of cross-platform tools or alternative workflows for non-Windows users. This creates friction for Linux/macOS users, who must translate or research equivalent commands themselves.
Recommendations
  • Add Azure CLI examples alongside PowerShell for all operations (e.g., creating restore point collections, restore points, tracking status).
  • Explicitly mention that Azure CLI and REST API are cross-platform and provide sample commands for Linux/macOS users.
  • Where possible, provide Bash script snippets for common workflows.
  • Clarify tool requirements and installation steps for both Windows and Linux/macOS environments.
  • Consider reordering examples so that cross-platform tools (CLI/REST) are presented before or alongside PowerShell.
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-13 06:17
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Windows Heavy Linking
Summary
The documentation is generally cross-platform, but there are several instances of Windows bias. Windows terminology and links are often presented first or exclusively (e.g., MBR/GPT partitioning, Sysprep, drive letters, and Windows-centric links). Windows tools and concepts (Sysprep, drive C/D, Windows Server Failover Cluster) are mentioned before or more prominently than Linux equivalents. Some links and examples are Windows-specific, with Linux alternatives referenced but not always equally detailed.
Recommendations
  • Ensure Linux examples and terminology are presented alongside Windows, not after or as an afterthought.
  • Provide equal detail and linking for Linux workflows (e.g., partitioning, imaging, cluster managers like Pacemaker).
  • Use neutral language where possible (e.g., 'OS disk' instead of 'drive C').
  • Where Windows-specific tools are mentioned (Sysprep, MBR/GPT links), include Linux equivalents (cloud-init, parted, fdisk, etc.) and relevant documentation.
  • In sections like 'Upload your VHD', ensure Linux and Windows guides are equally visible and detailed.
  • For cluster management, give equal prominence to Linux options like Pacemaker, with links to setup guides.
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-13 06:17
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation exclusively uses Azure PowerShell for all examples, including resource creation and plan specification. No Azure CLI, Bash, or Linux-native command examples are provided, despite the page stating applicability to Linux VMs. The referenced 'Find and use Azure Marketplace images' link also points to a Windows/PowerShell-specific page. This creates friction for Linux/macOS users who typically use Azure CLI or Bash scripts.
Recommendations
  • Add equivalent Azure CLI examples for all major steps (getting VM info, creating image definitions, creating VMs, etc.).
  • Include Bash script snippets for Linux users where appropriate.
  • Reference both Windows/PowerShell and Linux/CLI documentation in 'Next steps' and throughout the page.
  • Clearly indicate when a step is platform-agnostic or provide platform-specific instructions side-by-side.
  • Ensure ARM template examples are accompanied by CLI deployment instructions (e.g., using 'az deployment').
GitHub Create Pull Request
Virtual Machines Enable MSP on an Existing Virtual Machine or Virtual Machine Scale Set ...tual-machines/metadata-security-protocol/brownfield.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 more detailed information and examples for Windows VMs, including explicit extension names, status messages, and sample output. Linux instructions are less detailed, lacking concrete examples or output samples. Windows extension details and validation steps are shown first and in greater depth, while Linux equivalents are only mentioned briefly.
Recommendations
  • Add explicit examples and sample output for Linux VMs, similar to the Windows section.
  • Provide step-by-step instructions for installing and validating the Proxy Agent extension on Linux, including REST API payloads and expected status messages.
  • Present Windows and Linux instructions in parallel sections or tables to ensure equal visibility.
  • Include troubleshooting tips specific to Linux environments.
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-13 06:17
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page generally avoids platform-specific examples, but in the section about provisioning Linux VMs with MSP, it frames the limitation in terms of Windows philosophy and does not provide parity guidance for Linux users. There are no explicit Linux or Windows command-line examples, but the explanation prioritizes Windows deployment patterns and omits step-by-step Linux instructions for GPA installation or MSP enablement.
Recommendations
  • Provide explicit Linux instructions or examples for enabling MSP, including GPA installation steps.
  • Avoid framing Linux limitations in terms of Windows philosophy; instead, clarify the technical differences objectively.
  • Add parity examples for Linux users, such as using cloud-init, shell scripts, or VM extensions for GPA deployment.
  • Include troubleshooting or verification steps specific to Linux environments.
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-13 06:17
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 a simpler, single-step process for enabling GuestProxyAgent (GPA) on Windows, while noting that Linux requires a more complex, two-step process. However, no Linux-specific example or guidance is provided for the Linux workflow, and the main example uses a Windows VM name ('GPAWinVM'), further reinforcing the Windows-centric approach.
Recommendations
  • Add explicit, step-by-step instructions for enabling GPA on Linux, including any required post-provisioning configuration.
  • Provide Linux-specific ARM template or REST API examples, using Linux VM names and images.
  • Clarify any differences in validation steps for Linux VMs, if applicable.
  • Ensure parity in troubleshooting and advanced configuration guidance for Linux environments.
GitHub Create Pull Request
Virtual Machines Troubleshoot MSP ...hines/metadata-security-protocol/troubleshoot-guide.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 frequently presents Windows-specific tools, services, and troubleshooting steps before their Linux equivalents. Windows service names and commands (e.g., 'sc query', 'C:\WindowsAzure\ProxyAgent\Logs') are shown first or exclusively, while Linux examples are sometimes missing or less detailed. Some troubleshooting steps reference Windows-only tools (e.g., 'sc query' for eBPF services), and Linux instructions are less explicit or require more manual setup.
Recommendations
  • Provide Linux command equivalents wherever Windows commands are shown (e.g., use 'systemctl status' for Linux eBPF services instead of only 'sc query').
  • Present Linux and Windows instructions side-by-side or in parallel sections, rather than Windows-first.
  • Expand Linux troubleshooting steps with concrete examples, such as how to check service status, logs, and install required components.
  • Clarify installation and setup steps for Linux, including how to add the GPA extension and verify its health.
  • Ensure error code explanations and recovery steps are equally detailed for both platforms.
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-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 exhibits a moderate Windows bias. Several log tables and data collection methods reference Windows-specific tools (e.g., Windows Event Log, IIS logs, Windows DNS servers, Windows Security Events, Windows Firewall) and mention Windows services and patterns before or more prominently than Linux equivalents. While Linux is supported in some areas (e.g., Syslog, Linux Daemons), Windows-centric examples and terminology appear more frequently, and some log types are Windows-only. The only explicit example link provided is for Linux, but the overall reference material leans toward Windows-first presentation and tool coverage.
Recommendations
  • Ensure Linux and macOS equivalents are mentioned alongside Windows tools in all tables (e.g., highlight Linux audit logs, Linux firewall logs, Linux DNS server monitoring where applicable).
  • Add explicit Linux/macOS examples for data collection, especially for tables currently referencing only Windows sources.
  • Balance the order and prominence of Windows and Linux references in tables and descriptions.
  • Clarify which features are Windows-only and provide alternative guidance for Linux/macOS users.
  • Include more cross-platform agent and log collection scenarios, not just Windows-centric ones.
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-13 06:17
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 examples are presented first and in detail, with CLI examples following. The migration instructions link to a Windows-specific tutorial (toc/breadcrumb paths reference Windows), potentially confusing Linux users. While CLI examples are provided, the overall flow and references favor Windows tools and patterns.
Recommendations
  • Ensure migration instructions link to OS-neutral or Linux-specific tutorials where appropriate.
  • Alternate the order of PowerShell and CLI examples, or present CLI examples first to better support Linux/macOS users.
  • Explicitly state that CLI commands work on Linux/macOS and provide any necessary environment setup notes.
  • Add troubleshooting notes for Linux/macOS users if there are differences in error messages or command behavior.
  • Review linked resources to ensure they are not Windows-centric unless necessary.
GitHub Create Pull Request
Virtual Machines Metadata Security Protocol (MSP) ...irtual-machines/metadata-security-protocol/overview.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation lists Windows operating systems first in the compatibility section and provides a warning that Windows users can enable GuestProxyAgent (GPA) directly from an ARM template, while Linux users must follow a more complex, two-step process. No Linux-specific examples or guidance are provided for the Linux configuration workflow, and no Linux tools or commands are mentioned.
Recommendations
  • Provide step-by-step instructions or examples for enabling GPA on Linux, including relevant commands and configuration files.
  • List supported operating systems in alphabetical order or group by platform to avoid implicit prioritization.
  • Explicitly mention Linux tools or automation options for GPA configuration, such as cloud-init or shell scripts.
  • Clarify any differences in the process for Linux users and provide troubleshooting guidance specific to Linux environments.
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-13 06:17
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation provides three migration methods: Portal, CLI, and PowerShell. The CLI example uses Azure CLI, which is cross-platform, but the PowerShell example is Windows-centric and presented as a primary tab. The use of PowerShell and the 'devx-track-azurepowershell' custom tag indicate a Windows bias. There are no explicit Linux/macOS-specific instructions or troubleshooting tips, and the PowerShell example may not be as accessible to Linux/macOS users. The Portal section is platform-neutral, but the overall structure and emphasis favor Windows tools.
Recommendations
  • Clarify that Azure CLI commands work on Linux, macOS, and Windows, and consider making CLI the first or default example tab.
  • Add explicit notes or troubleshooting for Linux/macOS users, especially for authentication steps.
  • Reduce emphasis on PowerShell unless there are unique capabilities not available in CLI.
  • Ensure all screenshots and UI references are platform-neutral or provide Linux/macOS variants if relevant.
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-13 06:17
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing Windows-specific documentation (e.g., PowerShell) for checking VM SKU availability and for next steps, while not providing equivalent Linux/macOS CLI examples or links. The page also mentions PowerShell before CLI in the 'Next steps' section, and does not include any Linux/macOS-specific instructions or screenshots.
Recommendations
  • Include Azure CLI examples and links alongside PowerShell references, especially for tasks like checking VM SKU availability and performing the move.
  • Ensure that 'Next steps' and prerequisite links reference both PowerShell and CLI documentation, or provide a combined page with parity for both platforms.
  • Add explicit instructions or notes for Linux/macOS users where workflows or commands differ.
  • Balance screenshots and UI instructions to clarify that the Azure Portal is cross-platform, and avoid language that implies Windows-only usage.
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-13 06:17
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a subtle Windows bias by focusing its main example on testing RDP (Remote Desktop Protocol) connectivity, which is relevant only for Windows VMs. There are no equivalent Linux-specific connectivity examples (such as SSH), and the step-by-step instructions for testing inbound connections exclusively reference RDP. Although the prerequisites mention both Linux and Windows VMs, the actual test scenarios and screenshots are Windows-centric.
Recommendations
  • Add a parallel example for Linux VMs, such as testing SSH (port 22) connectivity, alongside the RDP example.
  • Explicitly state that the inbound connection test can be used for other protocols/services, and provide a table or section with common Linux scenarios.
  • Ensure screenshots and walkthroughs include both Windows and Linux VM contexts.
  • Present Windows and Linux examples with equal prominence, or alternate which is shown first.
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-13 06:17
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page, while focused on Linux VMs, relies heavily on PowerShell-based workflows and examples for the migration process. The main migration script is a PowerShell script, and most step-by-step instructions (checking controller type, preparing environment, running the script, reverting changes, checking results) are given using PowerShell commands. There is minimal coverage of Linux-native tooling or shell scripting, and the use of PowerShell is presented as the default, even for Linux users. Azure CLI is mentioned briefly, but not as a primary workflow. Windows-centric tools and patterns (e.g., Set-ExecutionPolicy, PowerShell installation, Windows-style paths) are referenced before any Linux alternatives.
Recommendations
  • Provide equivalent Bash/shell script workflows for Linux users, including migration, verification, and rollback steps.
  • Offer Azure CLI-based examples for all major tasks, especially for checking VM properties and running migration scripts.
  • Document how to run the migration script natively on Linux (e.g., via Azure Cloud Shell, or using pwsh on Linux), and clarify prerequisites for Linux environments.
  • Reorder examples so that Linux-native commands and workflows are shown first or in parallel with PowerShell/Windows examples.
  • Explicitly note any limitations or differences when running the migration process on Linux vs. Windows.
GitHub Create Pull Request
Virtual Machines Customer intent: "As an IT administrator managing Azure IaaS virtual machines, I want to implement a backup and disaster recovery plan for unmanaged disks, so that I can ensure data durability and high availability in the event of localized or regional failures." ...al-machines/page-blobs-backup-and-disaster-recovery.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation generally covers both Windows and Linux VMs, but there is a noticeable Windows bias in several areas. Windows tools and patterns (e.g., PowerShell, Volume Shadow Service, SQL Server Always On) are mentioned first or exclusively, while Linux equivalents are referenced later or in less detail. Automation and scripting examples focus on PowerShell, with Azure CLI only briefly mentioned. Some linked guides and examples (e.g., incremental snapshots) point to Windows-specific pages, and Linux-specific instructions are less prominent or missing.
Recommendations
  • Provide Linux-first or Linux-parity examples for backup and restore operations, especially for scripting and automation (e.g., Bash, Azure CLI, cron).
  • Include explicit Linux tooling and patterns (e.g., fsfreeze, LVM snapshots, application-consistent backup strategies for Linux workloads) alongside Windows tools like Volume Shadow Service.
  • Ensure all referenced guides (such as incremental snapshots) have clear Linux equivalents and links.
  • Add Linux-specific database backup and DR examples (e.g., PostgreSQL, MySQL, MongoDB) in addition to SQL Server.
  • Where PowerShell is mentioned for automation, also provide Azure CLI and Bash script examples, and clarify cross-platform compatibility.
  • Review and update links to ensure Linux documentation is as discoverable as Windows documentation.
GitHub Create Pull Request
Virtual Machines Azure premium storage: Design for high performance ...ticles/virtual-machines/premium-storage-performance.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 Sql Server Bias
Summary
The documentation page demonstrates a moderate Windows bias. Windows-centric examples (notably SQL Server) are used throughout, and Windows tools (PerfMon, Storage Spaces, PowerShell) are mentioned first or in greater detail than their Linux equivalents. Linux alternatives (iostat, MDADM) are present but often referenced after Windows, and some sections (e.g., disk striping) provide more step-by-step detail for Windows than Linux. The overall guidance is applicable to both platforms, but Windows users receive slightly more direct support and examples.
Recommendations
  • Provide Linux-first or side-by-side examples for key operations, such as disk striping and performance monitoring.
  • Include more detailed Linux guidance for disk striping (e.g., MDADM usage, recommended RAID levels, and stripe size configuration).
  • Balance SQL Server examples with equivalent Linux-first database workloads (e.g., PostgreSQL, MySQL) and their configuration tips.
  • Expand on Linux benchmarking and monitoring tools (e.g., explain vmstat, sar, atop, etc.) alongside iostat.
  • Ensure that Linux tools and commands are given equal prominence and detail as Windows tools.
  • Add links to Linux-specific best practices for disk performance and caching.
  • Consider using neutral, cross-platform examples where possible, or alternate between Windows and Linux in illustrative scenarios.
GitHub Create Pull Request
Virtual Machines Troubleshoot restore point failures ...cles/virtual-machines/restore-point-troubleshooting.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example Powershell Heavy
Summary
The documentation page demonstrates a moderate Windows bias. Windows-specific tools (services.msc, Event Viewer, COM+, MSDTC, VSS, Visual C++ Redistributable, .NET) are referenced frequently and often without Linux equivalents or alternatives. Troubleshooting steps and error resolutions for Windows are more detailed, with explicit instructions and tool usage, while Linux guidance is more generic and less tool-oriented. Windows examples and terminology (such as PowerShell, Control Panel, regsvr32.exe) are presented first or exclusively in several sections. Some troubleshooting steps (e.g., COM+ and VSS writer issues) are only applicable to Windows, with no mention of Linux analogs.
Recommendations
  • Provide equivalent Linux troubleshooting steps and examples where Windows tools are referenced (e.g., suggest systemctl, journalctl, or Linux log file paths instead of services.msc/Event Viewer).
  • Add Linux-specific error codes and resolutions for common extension/agent failures, matching the detail given for Windows.
  • Where PowerShell or Windows portal steps are given, include Azure CLI or Linux shell alternatives, and present them side-by-side.
  • Clarify which troubleshooting steps are Windows-only and provide Linux alternatives or explicitly state when no Linux equivalent exists.
  • Expand Linux troubleshooting for extension failures, agent issues, and network/DHCP configuration, with concrete commands and log locations.
GitHub Create Pull Request
Virtual Machines PowerShell Sample - Export/Copy snapshot as VHD to a storage account in different region ...nes-powershell-sample-copy-snapshot-to-storage-account.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 is heavily focused on PowerShell, providing only Windows/PowerShell-based examples and commands. There are no Bash, Azure CLI, or Linux-native instructions for exporting/copying snapshots as VHDs. All tooling and workflow are described in terms of PowerShell cmdlets, which are most familiar and accessible to Windows users. Linux alternatives are not mentioned or linked.
Recommendations
  • Add equivalent Azure CLI or Bash script examples for exporting/copying snapshots as VHDs.
  • Include a section describing how to perform the same task on Linux/macOS, using native tools or cross-platform Azure CLI.
  • Reference Linux/macOS documentation and provide links to relevant guides.
  • Clarify platform requirements and note PowerShell Core compatibility on Linux/macOS if relevant.
GitHub Create Pull Request
Virtual Machines Share Gallery Images Across Tenants by Using an App Registration ...icles/virtual-machines/share-using-app-registration.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 sharing Azure Compute Gallery images across tenants. However, the PowerShell section is significantly more detailed, including steps for networking and VM configuration, while the CLI section is minimal and omits these details. The PowerShell examples use Windows-centric patterns (e.g., RDP port, Windows OS configuration), and the networking setup is only shown in PowerShell. PowerShell is a Windows-native tool, and its prominence and detail suggest a bias toward Windows environments. Additionally, the PowerShell tab appears after the CLI tab, but the CLI example is much less comprehensive.
Recommendations
  • Expand the Azure CLI example to include all steps shown in the PowerShell section, such as networking setup, credential creation, and VM configuration.
  • Provide Linux/macOS-specific guidance, such as using SSH instead of RDP, and show examples for creating Linux VMs.
  • Ensure parity in detail and completeness between CLI and PowerShell sections.
  • Mention cross-platform compatibility explicitly, and avoid Windows-centric terminology where possible.
GitHub Create Pull Request
← Previous Page 14 of 33 Next →