Site Recovery

199
Total Pages
64
Linux-Friendly Pages
135
Pages with Bias
67.8%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

864 issues found
Showing 826-850 of 864 flagged pages
Site Recovery Quickstart to create an Azure Recovery Services vault using Bicep. ...rticles/site-recovery/quickstart-create-vault-bicep.md
Low Priority View Details →
Scanned: 2026-01-14 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 all deployment, verification, and cleanup steps. However, PowerShell examples are given equal prominence to CLI, and PowerShell is a Windows-centric tool. There is a slight 'windows_first' bias in the ordering of tabs and examples, but Linux/macOS users can fully complete all tasks using Azure CLI, which is cross-platform.
Recommendations
  • Explicitly mention that Azure CLI works on Linux/macOS and Windows, while Azure PowerShell is primarily for Windows (with limited cross-platform support).
  • Consider listing Azure CLI examples first, as it is the most cross-platform tool.
  • Add a short note clarifying that all tasks can be completed on Linux/macOS using Azure CLI, and link to Azure CLI installation instructions for those platforms.
  • If possible, clarify PowerShell's cross-platform status or recommend CLI for non-Windows users.
GitHub Create Pull Request
Site Recovery Quickstart: Use Terraform to create an Azure Recovery Services vault ...les/site-recovery/quickstart-create-vault-terraform.md
Low Priority View Details →
Scanned: 2026-01-14 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 instructions for verifying results, but the PowerShell example is given equal prominence and detail as the CLI example. The CLI instructions are cross-platform, but PowerShell is primarily a Windows-centric tool (though available on Linux/macOS). There is no explicit Linux/macOS bias, but the presence of PowerShell instructions and terminology may signal a slight Windows-first approach. No Windows-only tools or patterns are used, and all critical steps can be completed on Linux/macOS using the CLI.
Recommendations
  • Explicitly mention that Azure CLI commands work on Windows, Linux, and macOS, and recommend CLI for cross-platform users.
  • Add a note clarifying that PowerShell is available on Linux/macOS, but CLI is generally preferred for cross-platform scenarios.
  • Consider listing Azure CLI instructions before PowerShell, or marking CLI as the recommended/default approach for non-Windows users.
  • Ensure that all examples and instructions are tested and confirmed to work on Linux/macOS.
GitHub Create Pull Request
Site Recovery Move Azure virtual machines between government and public regions with Azure Site Recovery .../main/articles/site-recovery/region-move-cross-geos.md
Low Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Windows and Linux guidance for preparing accounts for Mobility service installation, but Windows instructions (including registry edits and CLI commands) are presented first and in more detail. The registry edit example uses Windows-specific tools (REG ADD), while Linux is only mentioned briefly as 'use root'. No Linux CLI examples or troubleshooting steps are provided, and some connectivity verification steps reference Windows Time Service documentation. However, the overall process is platform-agnostic and does not prevent Linux users from completing the task.
Recommendations
  • Provide equivalent Linux CLI commands and troubleshooting steps for Mobility service installation (e.g., how to verify root access, recommended best practices for Linux VMs).
  • When listing steps for both Windows and Linux, alternate the order or present them in parallel to avoid Windows-first bias.
  • Reference cross-platform time synchronization documentation (e.g., NTP for Linux) alongside Windows Time Service.
  • Add links to Linux-specific documentation for common issues encountered during replication setup.
GitHub Create Pull Request
Site Recovery Prepare VMware VMs for reprotection and failback with Azure Site Recovery ...rticles/site-recovery/vmware-azure-prepare-failback.md
Low Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation provides both Windows and Linux options for master target servers, but Windows is mentioned first and in more detail. The retention drive instructions are Windows-centric, with Linux details provided as a secondary note. There is a focus on Windows-specific tools and patterns, such as default retention volume (R: drive) and Windows master target server running by default. Linux equivalents are present but less emphasized.
Recommendations
  • Present Windows and Linux instructions in parallel, giving equal prominence to both.
  • Include Linux-specific examples and screenshots where applicable.
  • Clarify Linux requirements and steps with the same level of detail as Windows.
  • Ensure that Linux terminology (e.g., /mnt/retention) is explained as thoroughly as Windows concepts.
  • Add explicit Linux troubleshooting steps and caveats where relevant.
GitHub Create Pull Request
Site Recovery Prepare for VMware VM disaster recovery with Azure Site Recovery ...-recovery/vmware-azure-tutorial-prepare-on-premises.md
Low Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation provides guidance for both Windows and Linux VMs, but Windows instructions and troubleshooting steps are presented first and in greater detail. Windows-specific tools and registry modifications are described, while Linux instructions are more concise and lack equivalent troubleshooting depth.
Recommendations
  • Present Windows and Linux instructions in parallel sections, or alternate which comes first to avoid implicit prioritization.
  • Expand Linux troubleshooting guidance to match the detail provided for Windows (e.g., SSH connection issues, common boot problems).
  • Provide explicit Linux command examples for tasks like checking SSH service status and configuring firewall rules.
  • Include links to Linux-specific resources for post-failover connectivity and diagnostics.
GitHub Create Pull Request
Site Recovery About the Mobility service for disaster recovery of VMware VMs and physical servers with Azure Site Recovery | Microsoft Docs ...-recovery/vmware-physical-mobility-service-overview.md
Low Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation provides both Windows and Linux instructions for installing and configuring the Mobility service for Azure Site Recovery. However, Windows examples, folder paths, and screenshots are consistently presented first and in more detail. Windows-centric tools and patterns (e.g., use of C:\Program Files, command prompt, UI screenshots) are emphasized, with Linux instructions often following as secondary. Some prerequisite and workflow descriptions use Windows paths as the primary example, even when Linux is supported. Linux instructions are present and technically complete, but the overall presentation favors Windows.
Recommendations
  • Alternate the order of Windows and Linux instructions so that Linux is sometimes presented first, or present both side-by-side where feasible.
  • Include Linux-specific screenshots where UI is referenced, or clarify if UI is Windows-only.
  • Use neutral language and folder paths in generic instructions (e.g., 'copy to a local folder' instead of 'copy to C:\Program Files').
  • Ensure parity in troubleshooting and workflow examples for Linux, not just Windows.
  • Add explicit notes when a step or tool is Windows-only, and provide Linux alternatives if available.
GitHub Create Pull Request
Site Recovery Configure Mobility Service Proxy Settings for Azure to Azure Disaster Recovery | Microsoft Docs ...-recovery/configure-mobility-service-proxy-settings.md
Low Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation demonstrates a mild Windows bias: Windows-specific tools (Internet Explorer, psexec) are mentioned first and in detail, while Linux instructions are brief and generic. Windows paths and procedures are described before Linux equivalents, and Windows-centric patterns (IE proxy settings, psexec usage) are referenced without Linux analogs.
Recommendations
  • Provide Linux-specific step-by-step instructions for setting proxy environment variables, including example commands for popular shells (e.g., bash, systemd service overrides).
  • Mention Linux tools or configuration methods (such as using export in .bashrc, or configuring /etc/environment) with concrete examples.
  • Balance the order of instructions so that Linux and Windows are presented with equal prominence, or alternate which OS is described first.
  • Avoid referencing Windows-only tools (like Internet Explorer and psexec) without offering Linux alternatives or clarifying their irrelevance to Linux users.
GitHub Create Pull Request
Site Recovery Automate Mobility Service for disaster recovery of installation in Azure Site Recovery ...ery/vmware-azure-mobility-install-configuration-mgr.md
Low Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation generally provides parity between Windows and Linux, with dedicated sections and scripts for both platforms. However, there is a subtle Windows bias: Windows examples and instructions are consistently presented before Linux equivalents, and the tooling focus (Configuration Manager) is a Microsoft/Windows-centric solution. Some terminology and screenshots also prioritize Windows workflows.
Recommendations
  • Alternate the order of Windows and Linux instructions/examples to avoid always presenting Windows first.
  • Explicitly mention and provide guidance for Linux-native deployment tools (e.g., Ansible, Puppet, Chef) alongside Configuration Manager and JetPatch.
  • Include Linux-specific screenshots and UI flows where relevant, not just Windows-centric ones.
  • Clarify that Configuration Manager can deploy to Linux but is primarily a Windows tool, and suggest alternatives for organizations with Linux-heavy environments.
  • Ensure all scripts and steps are equally detailed for both platforms.
GitHub Create Pull Request
Site Recovery Archive for What's new in Azure Site Recovery ...icles/site-recovery/site-recovery-whats-new-archive.md
Low Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation provides a comprehensive archive of Azure Site Recovery updates, with clear inclusion of Linux support milestones. However, there is a subtle Windows bias: Windows Server versions and features are often mentioned first or in more detail, and some tooling references (e.g., PowerShell) are given without Linux CLI equivalents. In a few places, Windows features (such as servicing stack updates, SHA-2 requirements, and Storage Spaces Direct) are described with direct links to Microsoft KB articles, while Linux equivalents are less emphasized or omitted. PowerShell is referenced as the method for certain operations (e.g., firewall-enabled storage accounts), with no mention of Azure CLI or Bash alternatives.
Recommendations
  • When referencing tooling (e.g., PowerShell), also provide Azure CLI or Bash equivalents for Linux/macOS users.
  • Ensure that examples and feature lists mention Linux distributions and features with equal prominence and detail as Windows.
  • Where KB articles or guides are linked for Windows, provide corresponding Linux documentation or troubleshooting guides.
  • Avoid listing Windows features or requirements before Linux ones unless there is a technical reason.
  • Add explicit notes or tables for Linux-specific requirements, limitations, and update procedures.
GitHub Create Pull Request
Site Recovery What's new in Azure Site Recovery ...main/articles/site-recovery/site-recovery-whats-new.md
Low Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation is generally balanced in listing both Windows and Linux support for Azure Site Recovery updates. However, there are mild signs of Windows bias: Windows-specific tools (e.g., 'Site Recovery Provider', 'Recovery Services agent') are listed in update tables, and Windows versions (e.g., Windows 2025, Windows 11 server, Windows Server 2019) are sometimes mentioned before or alongside Linux distros. There are no command-line examples or step-by-step instructions, so the bias is limited to the ordering and presence of Windows-specific tooling.
Recommendations
  • Ensure Linux equivalents for all Windows tools are mentioned or clarified if not applicable.
  • When listing supported OSes, alternate the order or group by platform to avoid always listing Windows first.
  • Add explicit notes or links for Linux-specific installation or troubleshooting where Windows tools are referenced.
  • Consider a dedicated section summarizing Linux support and tooling for parity.
GitHub Create Pull Request
Site Recovery Fail back VMware VMs/physical servers from Azure with Azure Site Recovery ...b/main/articles/site-recovery/vmware-azure-failback.md
Low Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation page exhibits minor Windows bias by specifically mentioning Windows VMs and their interaction with VMware tools during failover/failback. There is no equivalent note or guidance for Linux VMs, and Windows is referenced first and exclusively in the context of VMware tools management.
Recommendations
  • Add equivalent notes for Linux VMs, clarifying how VMware tools are handled during failover/failback for Linux guests.
  • Provide explicit guidance or troubleshooting steps for Linux VMs, if any differences exist in the failback process.
  • Ensure that examples and notes do not exclusively reference Windows, or that Linux/macOS scenarios are mentioned with equal prominence.
GitHub Create Pull Request
Site Recovery Manage Azure role-based access control in Azure Site Recovery ...very/site-recovery-role-based-linked-access-control.md
Low Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation references PowerShell before Azure CLI and REST API in the 'Next steps' section, suggesting a Windows-first approach. There are no explicit Linux/macOS examples or tools highlighted, and PowerShell is mentioned before cross-platform alternatives.
Recommendations
  • List Azure CLI before PowerShell in example links, as CLI is natively cross-platform.
  • Explicitly mention that Azure CLI and REST API are available and supported on Linux/macOS.
  • Provide example commands for both PowerShell and Azure CLI in relevant sections.
  • Add a note clarifying platform compatibility for each tool (PowerShell, CLI, REST API).
GitHub Create Pull Request
Site Recovery Fail over Azure VMware Solution VMs to Azure by using Site Recovery ...b/main/articles/site-recovery/avs-tutorial-failover.md
Low Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation page shows minor Windows bias: Windows terminology and links (such as the availability set tutorial and VM connection instructions) are referenced before or instead of Linux equivalents. The connection instructions mention RDP and SSH but link only to Windows VM connection documentation. No explicit Linux examples or tools are provided, and Linux-specific considerations (e.g., boot drivers) are mentioned only in passing.
Recommendations
  • Provide explicit Linux/macOS examples for connecting to failed-over VMs, including SSH instructions and links to Linux VM documentation.
  • Reference both Windows and Linux availability set documentation, or clarify that the linked tutorial applies to both OS types.
  • Include troubleshooting steps or links for Linux VM connectivity issues after failover.
  • Ensure that all referenced documentation covers both Windows and Linux scenarios, or provide parallel instructions.
GitHub Create Pull Request
Site Recovery Fail back Azure VMware Solution VMsfrom Azure with Azure Site Recovery ...b/main/articles/site-recovery/avs-tutorial-failback.md
Low Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates mild Windows bias. Windows-specific behavior (VMware tools handling) is explicitly called out, while Linux VM failback details are omitted. No Linux-specific examples, troubleshooting, or tool mentions are provided, and the only OS-specific note is for Windows VMs.
Recommendations
  • Add a note describing the behavior for Linux VMs during failover and failback (e.g., how VMware tools are handled, any differences in process or troubleshooting).
  • Include examples or troubleshooting steps relevant to Linux VMs, such as agent installation or common issues.
  • Ensure parity in OS-specific guidance, so Linux/macOS users know what to expect and how to resolve issues.
GitHub Create Pull Request
Site Recovery Prepare Azure VMware Solution for disaster recovery to Azure Site Recovery ...ain/articles/site-recovery/avs-tutorial-prepare-avs.md
Low Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation page shows a mild Windows bias in several areas. Windows instructions (such as registry edits and firewall configuration) are described in more detail and presented before Linux equivalents. Windows-specific tools and terminology (e.g., Windows Firewall, RDP, registry settings) are mentioned explicitly, while Linux instructions are more generic and less detailed. Linux examples are present but less comprehensive.
Recommendations
  • Provide equally detailed Linux instructions, including specific commands for configuring SSH and firewall rules (e.g., using ufw, firewalld, or iptables).
  • Include step-by-step Linux examples for preparing accounts and permissions, similar to the Windows registry edit example.
  • Mention Linux tools and configuration files (e.g., /etc/ssh/sshd_config, SELinux, AppArmor) where relevant.
  • Present Windows and Linux instructions side-by-side or in parallel sections, rather than listing Windows first.
  • Add troubleshooting tips for Linux connectivity after failover, similar to the Windows RDP troubleshooting section.
GitHub Create Pull Request
Site Recovery Set up disaster recovery after migration to Azure with Azure Site Recovery ...e-recovery/azure-to-azure-replicate-after-migration.md
Low Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation presents Windows instructions and tooling before Linux equivalents in several sections. Windows-specific paths, tools (Control Panel, MsiExec.exe), and validation steps are described in detail, while Linux instructions are provided after Windows and are less detailed in some areas. The page does include Linux steps, but the ordering and emphasis favor Windows users.
Recommendations
  • Present Linux and Windows instructions in parallel or in separate, clearly labeled sections to avoid implicit prioritization.
  • Provide equally detailed validation steps for Linux, such as checking agent versions and log locations.
  • Include Linux-specific troubleshooting links and references where Windows equivalents are given.
  • Use neutral language and avoid Windows-first ordering unless justified by usage statistics.
GitHub Create Pull Request
Site Recovery Move Azure VMs to a different Azure region with Azure Site Recovery ...icles/site-recovery/azure-to-azure-tutorial-migrate.md
Low Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page exhibits mild Windows bias in the prerequisites section, where Windows update and certificate instructions are provided in detail, while Linux guidance is generic and refers users to their distributor. No command-line examples (PowerShell, Bash) are present, and the rest of the tutorial is platform-agnostic, focusing on Azure portal steps.
Recommendations
  • Provide specific instructions or links for updating root certificates on popular Linux distributions (e.g., Ubuntu, CentOS, RHEL) to match the detail given for Windows.
  • Include troubleshooting tips or common issues for Linux VMs during migration, similar to those for Windows.
  • Ensure parity in guidance for both OS types in all prerequisite and preparation steps.
GitHub Create Pull Request
Site Recovery Troubleshoot connectivity for Azure to Azure disaster recovery with Azure Site Recovery ...ry/azure-to-azure-troubleshoot-network-connectivity.md
Low Priority View Details →
Scanned: 2026-01-13 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 page exhibits mild Windows bias. While most troubleshooting steps and NSG configuration instructions are platform-neutral and focus on Azure portal actions, some sections reference Windows-specific tools or patterns first (e.g., proxy autodetection via Internet Explorer), and proxy configuration paths for Windows are mentioned before Linux equivalents. There is a lack of Linux/macOS-specific troubleshooting examples, such as command-line checks for DNS or network connectivity, and no mention of Linux-native tools (e.g., dig, curl, iptables) for diagnostics. The documentation assumes familiarity with Windows environments and tools, potentially creating friction for Linux users.
Recommendations
  • Provide Linux/macOS-specific troubleshooting steps, such as using dig or nslookup for DNS checks, and curl/wget for connectivity tests.
  • Include examples of configuring NSG and proxy settings using Azure CLI or PowerShell, with explicit Linux/macOS command syntax.
  • Mention Linux-native proxy autodetection mechanisms (e.g., environment variables, GNOME/KDE settings) alongside Windows/IE references.
  • Ensure that file paths and configuration instructions for Linux are presented with equal prominence as Windows equivalents.
  • Add screenshots or terminal output examples from Linux systems where relevant.
GitHub Create Pull Request
Site Recovery Enable accelerated networking for Azure VM disaster recovery with Azure Site Recovery ...azure-vm-disaster-recovery-with-accelerated-networking.md
Low Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation presents Windows VM information before Linux VM information in both the OS support and enabling instructions sections. However, both platforms are covered with equivalent detail, and Linux-specific links and examples are provided. There are no Windows-only instructions, tools, or examples; parity is maintained except for the ordering.
Recommendations
  • Alternate the order of Windows and Linux sections in future revisions, or present them in parallel to avoid implicit prioritization.
  • Explicitly state that both Windows and Linux are supported at the beginning of the relevant sections.
  • Ensure that any screenshots or examples are balanced between Windows and Linux where applicable.
GitHub Create Pull Request
Site Recovery Set up failover and failback for physical servers with Site Recovery ...s/site-recovery/physical-to-azure-failover-failback.md
Low Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a mild Windows bias. References to Azure VM settings link specifically to Windows documentation first (e.g., availability sets), and there are no explicit Linux-specific instructions or examples for failover/failback scenarios. While the text mentions that replication groups can use Windows or Linux, all operational steps and links default to Windows terminology and resources, with no parity for Linux users.
Recommendations
  • Include explicit Linux examples and instructions for failover/failback, such as screenshots or command-line steps relevant to Linux environments.
  • Provide links to Linux-specific Azure documentation (e.g., Linux VM availability sets, disk management, network configuration).
  • Clarify any differences in process or requirements for Linux servers, especially in sections discussing VM properties, reprotection, and failback.
  • Ensure that terminology and UI references are inclusive of both Windows and Linux environments.
GitHub Create Pull Request
Site Recovery Quickstart to create an Azure Recovery Services vault using Bicep. ...rticles/site-recovery/quickstart-create-vault-bicep.md
Low Priority View Details →
Scanned: 2026-01-13 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 all steps, but PowerShell is given equal prominence and is presented immediately after CLI in each section. There are no Linux/macOS-specific instructions or notes, and PowerShell is a Windows-centric tool, which may create friction for non-Windows users. However, the Azure CLI examples are cross-platform and always shown first, mitigating most bias.
Recommendations
  • Explicitly mention that Azure CLI works on Linux/macOS and is recommended for cross-platform use.
  • Add a note clarifying that PowerShell examples are primarily for Windows users, while CLI is suitable for all platforms.
  • Consider adding a brief section or callout for Linux/macOS users, confirming that all CLI commands work natively.
  • If relevant, mention installation instructions for Azure CLI on Linux/macOS.
GitHub Create Pull Request
Site Recovery Quickstart: Use Terraform to create an Azure Recovery Services vault ...les/site-recovery/quickstart-create-vault-terraform.md
Low Priority View Details →
Scanned: 2026-01-13 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 instructions for verifying results, but the PowerShell tab is present and given equal prominence, which may suggest a Windows bias. There are no explicit Linux/macOS-specific instructions or troubleshooting notes, and PowerShell is primarily a Windows tool (though now cross-platform). No Linux-specific tools or shell examples (e.g., bash scripts) are provided, and Windows/PowerShell is mentioned before Linux alternatives in some places.
Recommendations
  • Add explicit notes clarifying that Azure CLI commands work on Linux, macOS, and Windows, and that PowerShell Core is cross-platform.
  • Provide bash script examples for common verification and automation tasks, especially for Linux/macOS users.
  • Include troubleshooting steps or environment setup notes for Linux/macOS users (e.g., installing Azure CLI on Ubuntu, handling file permissions).
  • Consider listing Azure CLI (the most cross-platform tool) first in all example sections.
  • If PowerShell is shown, clarify its cross-platform status and provide links to install PowerShell Core on Linux/macOS.
GitHub Create Pull Request
Site Recovery Azure Site Recovery Deployment Planner Version History ...e-recovery/site-recovery-deployment-planner-history.md
Low Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Windows Heavy
Summary
The documentation lists Windows operating systems prominently and frequently, often before Linux equivalents. Windows versions are mentioned in nearly every release, sometimes with more detail than Linux, and Windows support is called out explicitly in fixes. Linux support is present but less emphasized, and there are no examples or instructions that are Windows-only. No PowerShell or Windows tool bias is present, but the ordering and detail favor Windows.
Recommendations
  • List Linux distributions alongside Windows in all relevant sections, and alternate the order to avoid Windows-first bias.
  • Provide equal detail for Linux support, including minor versions and specific features, where applicable.
  • Add explicit notes or examples for Linux users if there are differences in usage or limitations.
  • Ensure that any instructions, recommendations, or limitations are equally clear for both Windows and Linux environments.
GitHub Create Pull Request
Site Recovery Troubleshoot the Azure VM extension for disaster recovery with Azure Site Recovery .../site-recovery/site-recovery-extension-troubleshoot.md
Low Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation consistently lists Windows troubleshooting steps and error causes before Linux equivalents, and Windows-specific tools (services.msc, Control Panel, MSI installers, .NET) are described in detail. Linux instructions are present and reasonably complete, but are always secondary and less detailed in comparison.
Recommendations
  • Alternate the order of Windows and Linux sections so Linux is sometimes presented first.
  • Provide equally detailed step-by-step instructions for Linux troubleshooting, including common commands for checking agent status, uninstalling/reinstalling agents, and verifying dependencies.
  • Mention Linux tools (e.g., systemctl, package managers) with the same prominence as Windows tools.
  • Add explicit parity notes to assure users that all major troubleshooting steps are covered for both platforms.
  • Where possible, unify troubleshooting steps that apply to both OSes before splitting into platform-specific details.
GitHub Create Pull Request
Site Recovery About Azure Site Recovery .../main/articles/site-recovery/site-recovery-overview.md
Low Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page for Azure Site Recovery demonstrates mild Windows bias. Windows-specific technologies (e.g., Windows Server Failover Clusters, SQL Server Always On, AWS Windows instances) are mentioned explicitly, while Linux equivalents are not. Windows workloads and features are often listed first, and there is a lack of concrete Linux-focused examples or references to Linux-specific disaster recovery scenarios or tooling. Although Linux is mentioned as supported, details and examples are sparse compared to Windows.
Recommendations
  • Add explicit examples and references for Linux disaster recovery scenarios, such as protecting Linux clusters or common Linux workloads (e.g., Apache, MySQL, PostgreSQL).
  • Include Linux-specific tooling and patterns where applicable, such as integration with Linux-native automation or backup solutions.
  • Balance the mention of Windows and Linux technologies/features, ensuring Linux is not only listed as 'supported' but also described in detail.
  • Provide parity in documentation for advanced features (e.g., shared disk, application-consistent snapshots) for Linux workloads if supported, or clarify limitations.
GitHub Create Pull Request
← Previous Page 34 of 35 Next →