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 376-400 of 818 flagged pages
Virtual Machines Create a VM from a specialized image version ...icles/virtual-machines/vm-specialized-image-version.md
Medium Priority View Details →
Scanned: 2026-01-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 all scenarios, but the PowerShell sections are significantly more detailed, with full resource creation steps and network configuration, while CLI examples are minimal. PowerShell is a Windows-centric tool, and the detailed guidance for it may disadvantage Linux/macOS users who rely on Bash or other shells. Additionally, network security examples focus on RDP (Windows remote access) rules, and PowerShell examples are always shown after CLI but are much more extensive, suggesting a bias toward Windows tooling and workflows.
Recommendations
  • Expand Azure CLI examples to include full resource creation and network configuration steps, matching the detail provided in PowerShell sections.
  • Add Bash shell script examples for Linux/macOS users, especially for multi-step VM and network setup.
  • Include explicit instructions or examples for configuring SSH (port 22) access in network security rules, not just RDP (port 3389).
  • Clarify that PowerShell examples are primarily for Windows users, and provide parity for Linux/macOS users.
  • Consider adding cross-platform scripting guidance (e.g., using Bash, Python, or Terraform) for advanced scenarios.
GitHub Create Pull Request
Virtual Machines Overview of VM Applications in the Azure Compute Gallery ...blob/main/articles/virtual-machines/vm-applications.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation provides both Windows and Linux guidance, but several sections show Windows bias. Windows tools (PowerShell, cmd.exe, msiexec) are referenced more frequently and sometimes before Linux equivalents. Troubleshooting and status-checking examples use PowerShell exclusively, with no Linux CLI or Bash alternatives. File renaming and installer command examples are shown for Windows first, and Windows-specific patterns (registry, batch scripting) are explained in detail, while Linux sections are less comprehensive. The Linux packaging section is robust, but Windows-centric tools and examples dominate in troubleshooting and command interpreter discussions.
Recommendations
  • Add Linux CLI (az CLI, Bash) equivalents for all PowerShell troubleshooting/status commands.
  • Provide Linux-first or side-by-side examples for file renaming, installer invocation, and troubleshooting.
  • Expand Linux troubleshooting guidance (e.g., using az CLI, checking extension status via Bash/SSH).
  • Ensure parity in depth of explanation for Linux installer scenarios (e.g., handling .deb/.rpm uninstall, error handling).
  • Reference Linux tools (e.g., dpkg, apt, yum, zypper) in troubleshooting and management sections where appropriate.
GitHub Create Pull Request
Virtual Machines VM watch Collectors Suite .../articles/virtual-machines/vm-watch-collector-suite.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page for VM watch Collectors Suite demonstrates a moderate Windows bias. Windows-specific tools (e.g., w32tm, Windows EventLog) are referenced exclusively or before Linux equivalents, and some collectors are only eligible or described for Windows environments. Linux-specific details are sparse or missing, with some collectors lacking Linux parity or examples.
Recommendations
  • Provide equivalent Linux/macOS examples and tool references (e.g., mention ntpd/chrony for clock skew checks, syslog/journalctl for system errors).
  • Clarify eligibility and behavior for all collectors on Linux/macOS, especially where currently only Windows is described.
  • Add Linux/macOS-specific configuration parameters and troubleshooting steps where relevant.
  • Ensure that collector descriptions and examples are presented for both platforms, not just Windows.
  • Where a collector is Windows-only, explicitly state the lack of Linux/macOS support and suggest alternatives if possible.
GitHub Create Pull Request
Virtual Machines Set up Oracle ASM on an Azure Linux virtual machine | Microsoft Docs ...tual-machines/workloads/oracle/configure-oracle-asm.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation is generally Linux-focused for the Oracle ASM setup, but there is notable Windows bias in the sections describing the X Server VM. The X Server is deployed on a Windows VM using Windows-only tools (Xming), and all graphical installer steps require a Windows workstation. PowerShell is used for Bastion tunnel setup, and SCP instructions are given in a Windows context. There are no instructions for using a Linux or macOS workstation for X server or tunneling, nor are Linux X server alternatives mentioned.
Recommendations
  • Provide instructions for setting up X server on Linux and macOS workstations (e.g., using XQuartz for macOS, native X11 for Linux).
  • Include Linux/macOS equivalents for Bastion tunnel setup (e.g., using az CLI in Bash, SSH port forwarding).
  • Offer SCP command examples for Linux/macOS shells.
  • Clarify that the X Server VM does not need to be Windows, and describe how to use Linux-based X server if preferred.
  • Reorder examples to present Linux/macOS options first or alongside Windows options.
GitHub Create Pull Request
Virtual Machines Implement Oracle Golden Gate on an Azure Linux VM | Microsoft Docs ...hines/workloads/oracle/configure-oracle-golden-gate.md
Medium Priority View Details →
Scanned: 2026-01-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, while focused on deploying Oracle Golden Gate on Azure Linux VMs, demonstrates notable Windows bias in several areas. The X Server setup is exclusively described using a Windows VM and Windows-only tools (Xming), with no Linux or macOS alternatives mentioned. Bastion tunnel and SCP file transfer examples use PowerShell commands, with no Bash or Linux-native equivalents. The workflow assumes access to Windows for critical steps, potentially blocking Linux/macOS-only users.
Recommendations
  • Provide instructions for setting up X Server on Linux (e.g., using Xorg, X11 forwarding via SSH) and macOS (e.g., XQuartz).
  • Include Bash/Linux-native commands for Bastion tunnel setup and SCP file transfers, not just PowerShell.
  • Mention cross-platform alternatives for X Server and clarify that Windows VM is optional, not required.
  • Reorder examples so Linux-native approaches are presented first or alongside Windows methods.
  • Explicitly state any platform requirements and offer parity guidance for non-Windows users.
GitHub Create Pull Request
Virtual Machines Connect Azure ExpressRoute with Oracle Cloud Infrastructure | Microsoft Docs ...nes/workloads/oracle/configure-azure-oci-networking.md
Medium Priority View Details →
Scanned: 2026-01-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 moderate Windows bias. While the page claims applicability to Linux VMs and references Terraform (a cross-platform tool), it consistently presents Azure portal and PowerShell workflows for critical steps, such as configuring ExpressRoute FastPath, without providing equivalent Linux CLI (Azure CLI) examples. PowerShell is mentioned as an automation option, but Azure CLI is only referenced in the context of Terraform authentication, not for core network configuration tasks. The ordering of examples and instructions generally favors Windows-centric tools and workflows, with Linux alternatives either omitted or mentioned later.
Recommendations
  • Add Azure CLI command examples alongside PowerShell for all configuration steps, especially for ExpressRoute FastPath and network gateway setup.
  • Explicitly mention that all steps can be performed from Linux/macOS using Azure CLI and provide links to relevant CLI documentation.
  • Where screenshots are shown of the Azure portal, clarify that the portal is accessible from any OS/browser.
  • Ensure Terraform scripts are highlighted as the primary automation method for cross-platform parity.
  • Review and update any references to Windows-only tools to include Linux/macOS equivalents.
GitHub Create Pull Request
Virtual Machines Architectures for Oracle applications with database on Azure Virtual Machines ...ads/oracle/deploy-application-oracle-database-azure.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 discusses deploying Oracle applications on Azure Virtual Machines but does not provide explicit examples, instructions, or considerations for Linux environments. Windows is mentioned directly in the PeopleSoft section as a required OS for certain components, and there are no Linux-specific recommendations, examples, or parity notes. The general guidance and architecture are OS-agnostic, but the lack of Linux examples and the explicit mention of Windows create a subtle bias.
Recommendations
  • Add explicit examples and guidance for deploying Oracle applications on Linux-based Azure VMs, including OS-specific considerations for RHEL, Oracle Linux, or Ubuntu.
  • Where Windows is mentioned as a requirement (e.g., PeopleSoft Process Scheduler), clarify if Linux alternatives exist or provide instructions for Linux-based deployments.
  • Include sample architecture diagrams and migration steps for both Windows and Linux environments.
  • List common Linux administration tools and patterns alongside Windows ones (e.g., SSH, SELinux, systemd, Linux patching tools).
  • Ensure that any references to OS-specific features (such as Azure Disk Encryption or patch management) include both Windows and Linux options.
GitHub Create Pull Request
Virtual Machines Red Hat Enterprise Linux bring-your-own-subscription Azure images | Microsoft Docs ...ain/articles/virtual-machines/workloads/redhat/byos.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation provides both Azure CLI (cross-platform) and PowerShell examples for provisioning Red Hat Enterprise Linux BYOS images on Azure. However, the PowerShell section is extensive, with a full script for VM creation, while the CLI section is more concise and lacks equivalent depth (e.g., no full end-to-end Linux shell script). Windows-specific tools (PowerShell, Az PowerShell module) are featured, and the PowerShell example is given after the CLI but is much more detailed. There is no explicit Linux shell (bash) or macOS Terminal example for automation, and no mention of Linux-native tools for scripting beyond Azure CLI.
Recommendations
  • Add a full Linux shell (bash) script example for end-to-end VM provisioning, matching the detail of the PowerShell script.
  • Explicitly mention that Azure CLI works on Linux/macOS and provide links to installation instructions for those platforms.
  • Balance the depth of CLI and PowerShell sections so Linux/macOS users have parity in automation guidance.
  • Consider adding Terraform or Ansible examples, which are popular in Linux automation.
  • Clarify that PowerShell Core is cross-platform, but most users on Linux/macOS will prefer bash/CLI.
GitHub Create Pull Request
Virtual Machines Azure Key Vault VM Extension for Linux ...rticles/virtual-machines/extensions/key-vault-linux.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 is focused on Linux, but several sections show Windows bias. PowerShell examples are presented before Azure CLI equivalents, and PowerShell is referenced as a primary deployment and troubleshooting tool. Windows-centric patterns (e.g., PowerShell, ARM template notes referencing Windows VM portal guides) appear before or in place of Linux-native alternatives, even though the extension is Linux-specific.
Recommendations
  • Present Azure CLI examples before PowerShell, as CLI is cross-platform and native to Linux/macOS.
  • Minimize references to Windows-specific tools and guides (e.g., avoid linking to Windows VM portal instructions in Linux docs).
  • Add explicit Bash shell examples for common tasks (e.g., troubleshooting, file manipulation) to complement or replace PowerShell snippets.
  • Clarify that PowerShell is optional and not required for Linux users; highlight CLI and Bash as primary tools.
  • Ensure troubleshooting and support sections provide parity for Linux-native workflows (e.g., using journalctl, tail, grep for logs).
GitHub Create Pull Request
Virtual Machines Troubleshooting Azure Disk Encryption for Linux VMs ...tual-machines/linux/disk-encryption-troubleshooting.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 is focused on Linux VMs and provides Linux-specific troubleshooting steps. However, when discussing how to check encryption status and disable disk encryption, it consistently presents Azure PowerShell (Windows-centric) commands first and in greater detail, with CLI commands mentioned only briefly and after PowerShell. No Linux-native tools or shell examples are provided for these Azure management tasks.
Recommendations
  • Provide Azure CLI examples alongside or before PowerShell examples, as Azure CLI is cross-platform and preferred by many Linux users.
  • Explicitly mention that Azure CLI can be used from Linux/macOS and provide full command output examples.
  • Where possible, include Bash shell or Linux-native commands for local disk status checks, not just Azure management commands.
  • Ensure that instructions for disabling or checking encryption are not PowerShell-centric and offer parity for Linux users.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page is focused on creating and sharing Linux VM images using the Azure portal, but in the 'Before you begin' section, it references a tutorial for creating a managed image using Azure PowerShell and links to a snapshot creation guide under a Windows-specific path. There are no explicit Linux CLI (e.g., Bash, Azure CLI) examples or links, and the initial instructions for image creation reference Windows-oriented resources before Linux equivalents.
Recommendations
  • Include links to Linux-specific tutorials for creating managed images, such as using Azure CLI or Bash scripts.
  • Reference cross-platform guides or clarify that the PowerShell tutorial is applicable to Linux/macOS (if true), or provide alternatives.
  • Ensure snapshot creation links point to Linux-relevant documentation or provide both Windows and Linux options.
  • Add explicit Azure CLI examples for common tasks, especially for Linux users who may not use PowerShell.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides only Azure PowerShell examples for managing VM restore points, with no equivalent CLI (az), Bash, or Linux/macOS-specific instructions. All code samples use PowerShell syntax, which is native to Windows and less common on Linux/macOS. There is no mention of cross-platform tools or alternative workflows for non-Windows users.
Recommendations
  • Add Azure CLI (az) examples alongside PowerShell for all major operations.
  • Explicitly mention that PowerShell Core is available on Linux/macOS, or link to installation instructions.
  • Provide Bash script examples for common tasks where appropriate.
  • Ensure that instructions do not assume the user is on Windows; clarify cross-platform compatibility.
  • List both PowerShell and CLI options in parallel, or indicate which is recommended for each OS.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a Windows bias by providing detailed extension status examples and output for Windows VMs only, referencing Windows-specific tools and paths, and omitting equivalent Linux extension output or validation examples. Windows extension installation is described as automatic, while Linux requires a separate explicit API call, but no Linux output or validation details are shown.
Recommendations
  • Add example output and validation details for the Linux Proxy Agent extension, similar to the Windows example.
  • Include Linux-specific extension status codes, messages, and file paths to demonstrate parity.
  • Present Windows and Linux instructions and examples side-by-side or in parallel sections.
  • Clarify the Linux installation process with explicit REST API call examples and expected results.
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-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 provides both Windows and Linux coverage in its scope, but there are several instances of Windows bias. Windows tools (e.g., PowerShell, Volume Shadow Service) are mentioned first and in more detail, with Linux alternatives (e.g., fsfreeze) referenced briefly or as less capable. Examples and links for backup automation and snapshot management often point to Windows-specific resources or PowerShell, with Linux CLI or scripting alternatives less emphasized or missing. Some backup consistency features are described as unavailable for Linux, and Linux-specific guidance is sometimes relegated to notes or external links.
Recommendations
  • Provide Linux CLI and shell script examples alongside PowerShell for all backup and snapshot operations.
  • Mention Linux tools (e.g., fsfreeze, Azure CLI, AzCopy) with equal prominence and detail as Windows tools.
  • Ensure Linux-specific documentation links are included and referenced in the main text, not just in 'Next steps' or notes.
  • Describe application-consistent backup strategies for Linux in more detail, including third-party options or best practices.
  • Avoid presenting Windows tools or workflows first; alternate or parallelize Windows and Linux instructions.
  • Clarify limitations and workarounds for Linux users where Windows features (e.g., VSS) are unavailable.
GitHub Create Pull Request
Virtual Machines MSP via CLI ...hines/metadata-security-protocol/other-examples/cli.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
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 users, and the documentation implicitly assumes Windows as the default platform.
Recommendations
  • Include equivalent examples using popular Linux images (e.g., UbuntuLTS, CentOS, Debian) alongside Windows examples.
  • Add notes clarifying MSP support for Linux VMs and any platform-specific considerations.
  • Where screenshots are provided, show both Windows and Linux VM deployment scenarios.
  • Explicitly mention that the commands work for both Windows and Linux VMs, or note any differences.
GitHub Create Pull Request
Virtual Machines Share VM images in a compute gallery ...in/articles/virtual-machines/shared-image-galleries.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 shows a moderate Windows bias. PowerShell examples are provided alongside CLI, but references to Windows tools (like Sysprep) and Windows-specific links appear before or more prominently than Linux equivalents. Some sections (e.g., image generalization, uploading VHDs) mention Windows first or link to Windows-specific guides before Linux ones. There are also references to Azure PowerShell and .NET SDK, which are more commonly used on Windows, with less emphasis on cross-platform or Linux-native tooling. Linux examples are present but sometimes secondary.
Recommendations
  • Ensure CLI examples are shown before or alongside PowerShell, as Azure CLI is cross-platform.
  • When mentioning OS-specific tools (e.g., Sysprep for Windows, waagent for Linux), present both equally and in parallel, not Windows first.
  • Provide direct links to Linux documentation and examples wherever Windows links are given.
  • Highlight cross-platform SDKs and tools (Python, Go, Node.js) more prominently.
  • Add explicit Linux/macOS command-line examples where only PowerShell is shown.
  • Review and balance the order of OS references in tables and lists.
GitHub Create Pull Request
Virtual Machines Ev5 size series .../virtual-machines/sizes/memory-optimized/ev5-series.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation page is mostly platform-neutral, but there is a subtle Windows bias in the 'Feature support' section, where 'Nested Virtualization' links exclusively to a Windows/Hyper-V guide. In the networking section, bandwidth/throughput testing references NTTTCP, a Microsoft tool primarily associated with Windows, without mentioning Linux alternatives or providing parity. Windows terminology and tools are mentioned before Linux equivalents (if any), and Linux-specific guidance is minimal.
Recommendations
  • Include links or references to Linux-specific nested virtualization documentation (e.g., KVM/QEMU).
  • Mention and provide examples of Linux-compatible bandwidth/throughput testing tools (e.g., iperf, netperf) alongside NTTTCP.
  • Where Windows tools are referenced, add Linux alternatives and usage notes to ensure parity.
  • Review all feature support links to ensure Linux documentation is equally represented.
GitHub Create Pull Request
Virtual Machines Enable Trusted launch on existing Gen2 VMs ...rticles/virtual-machines/trusted-launch-existing-vm.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 provides parity for both Linux and Windows VMs in terms of Azure CLI, Portal, and ARM template instructions. However, there is a notable bias towards Windows/PowerShell tooling: PowerShell examples are given equal prominence to CLI, and ARM template deployment steps use PowerShell exclusively. The documentation references RDP for Windows and SSH for Linux, but PowerShell is presented as a primary automation tool, which is Windows-centric. There are no Linux shell (bash) equivalents for ARM template deployment, and PowerShell is referenced in places where cross-platform alternatives exist.
Recommendations
  • Add bash (Linux shell) examples for ARM template deployment, using Azure CLI or native bash commands.
  • Clarify that PowerShell examples are for users on Windows, and provide equivalent instructions for Linux/macOS users.
  • Where PowerShell is used for automation, offer Azure CLI or bash alternatives, especially for template deployments.
  • Ensure that cross-platform tools (Azure CLI, REST API) are mentioned before or alongside Windows-specific tools.
  • Explicitly state that all steps can be performed from Linux/macOS using Azure CLI and provide links to relevant installation guides.
GitHub Create Pull Request
Virtual Machines List, update, and delete resources ...in/articles/virtual-machines/update-image-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 provides both Azure CLI and Azure PowerShell examples for all major operations. However, PowerShell examples are given equal prominence and detail as CLI, despite PowerShell being primarily a Windows tool. In some sections, PowerShell examples appear immediately after CLI, and REST examples are included only for listing shared galleries, not for update or delete operations. There are no Linux-specific shell examples (e.g., bash scripting), and PowerShell is presented as a cross-platform option, which may not reflect typical Linux/macOS usage patterns.
Recommendations
  • Clarify that PowerShell is available cross-platform, but most Linux/macOS users prefer bash or shell scripting with Azure CLI.
  • Add explicit bash/zsh shell script examples for common Linux/macOS workflows, especially for tasks involving variables, loops, or output parsing.
  • Consider including REST API examples for update and delete operations to provide a platform-neutral alternative.
  • Where PowerShell is presented, note its installation and usage on Linux/macOS, or link to guidance for non-Windows users.
  • If possible, show CLI examples using both Windows (cmd/PowerShell) and Linux/macOS (bash/zsh) syntax for variable assignment and command chaining.
GitHub Create Pull Request
Virtual Machines Manage, Update, and Delete VM Applications on Azure ...in/articles/virtual-machines/vm-applications-manage.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 provides parity across Azure Portal, REST, CLI, and PowerShell for managing VM Applications, but PowerShell examples (which are Windows-centric) are always present and sometimes referenced in CLI scripting notes. In scripting sections, PowerShell is used for advanced CLI scripting, and PowerShell tabs are always included, suggesting a Windows-first approach. However, Azure CLI examples are present and suitable for Linux/macOS, and REST API usage is platform-neutral. No critical steps are Windows-only, but the prominence of PowerShell and its use in scripting guidance may create friction for Linux/macOS users.
Recommendations
  • Where scripting is shown with PowerShell for CLI, provide equivalent Bash examples for Linux/macOS users.
  • Explicitly note that Azure CLI commands work on Linux/macOS and provide sample Bash scripting for multi-instance operations.
  • Consider alternating the order of CLI and PowerShell tabs, or defaulting to CLI in documentation targeting cross-platform users.
  • Add a short section clarifying tool parity and platform support, reassuring Linux/macOS users they can perform all tasks.
  • Review any advanced scripting examples to ensure Bash alternatives are present and clear.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation demonstrates a moderate Windows bias. In code examples (REST API, PowerShell, ARM template), the extension type is consistently set to 'DependencyAgentWindows' and the publisher to 'Microsoft.Azure.Monitoring.DependencyAgent', even when the CLI examples use 'DependencyAgentLinux'. PowerShell examples are provided only for Windows extensions, and the use of PowerShell itself is inherently Windows-centric. ARM template and REST API samples also default to Windows extension types. There is no explicit Linux-focused PowerShell or ARM template example, and the documentation does not alternate or balance Windows and Linux examples. The supported extensions table does list both Windows and Linux extensions, but example usage is Windows-first and lacks Linux parity in several critical sections.
Recommendations
  • Provide parallel examples for both Windows and Linux extension types in all code samples (REST API, PowerShell, ARM template, etc.), not just CLI.
  • Alternate the order of Windows and Linux examples, or present both together, to avoid Windows-first bias.
  • Include notes or guidance for Linux users where PowerShell is referenced, such as using Azure CLI or REST API.
  • Explicitly show how to enable automatic extension upgrade for a Linux VM/VMSS in PowerShell and ARM template sections.
  • Add a section clarifying cross-platform support and tooling for both Windows and Linux users.
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-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 for Azure VM Watch demonstrates moderate Windows bias. Several health signals and checks are Windows-specific (e.g., System Errors from Windows event log, Hardware Health Monitor via Windows event log, fallback to w32tm for clock sync on Windows). Windows tools and patterns (event log, w32tm) are mentioned explicitly, while Linux equivalents are either absent or less detailed. In some cases, Windows checks are described first or exclusively, and Linux-specific metrics are less prominent or only briefly mentioned.
Recommendations
  • Add equivalent Linux examples and tooling references for all Windows-specific checks (e.g., describe how system errors are collected on Linux, such as via syslog or journald).
  • For hardware health, provide Linux methods (e.g., SMART monitoring, dmesg parsing) alongside Windows event log collection.
  • For clock skew, specify the Linux fallback mechanism (e.g., ntpd, chrony status) when NTP server is inaccessible.
  • Ensure all tables and descriptions mention both Linux and Windows approaches where applicable, and avoid listing Windows methods first unless they are more widely applicable.
  • Where a metric or check is Windows-only, clearly state the Linux equivalent or note its absence.
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-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 provides comprehensive coverage for both Windows and Linux VMs, but there is a notable Windows bias: Windows examples and tools (PowerShell, CLI) are presented first and in greater detail, with multiple PowerShell and CLI examples for Windows but fewer for Linux. Several patch orchestration modes are Windows-only, and Windows-specific tools and registry settings are described in detail, while Linux equivalents are less emphasized. The 'Next steps' section links only to Windows VM management.
Recommendations
  • Present Linux and Windows examples in parallel, or alternate which comes first in each section.
  • Add equivalent PowerShell and CLI examples for Linux where missing, especially for patch mode changes and VM creation/update.
  • Include more detail on disabling/enabling automatic updates for Linux distributions (beyond Ubuntu and RHEL).
  • Provide 'Next steps' links for Linux VM management alongside Windows.
  • Clarify Linux-specific requirements and troubleshooting steps, matching the depth given to Windows.
  • Where Windows registry keys are mentioned, explain the Linux configuration file equivalents.
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-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 demonstrates a moderate Windows bias. Windows-specific tools and patterns (e.g., Volume Shadow Service, SQL Server Always On) are mentioned before their Linux equivalents, and Windows examples (such as SQL Server) are more detailed. Linux alternatives (like fsfreeze) are referenced briefly and with less explanation. There are no concrete Linux command examples or detailed Linux application backup scenarios, while Windows tools and workflows are described in greater depth.
Recommendations
  • Provide equal detail for Linux backup coordination tools (e.g., expand on fsfreeze usage, mention LVM snapshots, etc.)
  • Include Linux application examples (e.g., PostgreSQL, MySQL, MongoDB) with backup and disaster recovery strategies
  • Add step-by-step Linux command examples for snapshot coordination and restore operations
  • Mention Linux-native backup solutions and patterns alongside Windows ones, not after
  • Balance references to Windows and Linux in tables and scenario descriptions
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-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation generally covers 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 mention. This prioritizes Windows and may leave Linux users unclear about their workflow.
Recommendations
  • Add a Linux-specific example or documentation link for creating managed disk snapshots on Linux VMs.
  • Ensure that examples and references are provided for both Windows and Linux platforms in all sections.
  • Where platform-specific instructions exist, present them side-by-side or clearly indicate differences.
GitHub Create Pull Request
← Previous Page 16 of 33 Next →