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 76-100 of 864 flagged pages
Site Recovery Fail back Hyper-V VMs from Azure with Azure Site Recovery .../main/articles/site-recovery/hyper-v-azure-failback.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation is heavily focused on Windows environments, specifically Hyper-V and System Center VMM, with all instructions and prerequisites referencing Windows tools and patterns. There are no examples or guidance for Linux hosts or KVM/QEMU environments, and the steps assume the use of Windows Server and Hyper-V exclusively.
Recommendations
  • Add equivalent instructions for Linux-based hypervisors (e.g., KVM, QEMU) if supported by Azure Site Recovery.
  • Include examples and prerequisites for failback to Linux hosts, such as supported distributions, required packages, and configuration steps.
  • Clarify whether Azure Site Recovery supports non-Windows environments for failback, and if not, explicitly state this limitation.
  • If only Windows/Hyper-V is supported, consider adding a section that addresses Linux users and provides alternative disaster recovery options or references.
GitHub Create Pull Request
Site Recovery Set up failover of Hyper-V VMs to Azure in Azure Site Recovery ...e-recovery/hyper-v-azure-failover-failback-tutorial.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation is heavily focused on Hyper-V, a Windows-centric virtualization platform, and references Windows-specific tools and patterns (e.g., Remote Desktop Protocol, System Center VMM). There are no examples or guidance for Linux-based hypervisors (such as KVM or VMware on Linux), nor are Linux failover scenarios or tools mentioned. The instructions and links prioritize Windows environments and tools, with no parity for Linux users.
Recommendations
  • Add equivalent guidance and examples for Linux-based hypervisors (e.g., KVM, VMware on Linux) where Azure Site Recovery supports them.
  • Include instructions for connecting to failed-over VMs using Linux tools (e.g., SSH from Linux, Linux RDP clients) and reference Linux documentation where appropriate.
  • Mention and link to Azure Site Recovery documentation for Linux VMs and failover scenarios.
  • Clarify in the introduction that the tutorial is specific to Hyper-V/Windows environments, and provide links to Linux failover documentation if available.
  • Where possible, provide parity in troubleshooting steps and connectivity validation for both Windows and Linux VMs.
GitHub Create Pull Request
Site Recovery Support for disaster recovery of Hyper-V VMs to Azure with Azure Site Recovery ...articles/site-recovery/hyper-v-azure-support-matrix.md
High Priority View Details →
Scanned: 2026-01-11 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 is heavily focused on Windows environments, specifically Hyper-V and System Center Virtual Machine Manager, with requirements and examples exclusively referencing Windows Server versions and PowerShell. There is no mention of Linux-based hypervisors, nor are there Linux CLI or tool examples. Windows terminology and tools are presented as the default or only supported scenario, and Linux is only referenced as a guest OS, not as a host or management platform.
Recommendations
  • Explicitly state that only Windows-based Hyper-V hosts are supported, and clarify the lack of Linux host support.
  • If Linux-based virtualization platforms (such as KVM, Xen, or VMware on Linux) are not supported, mention this in a 'Not Supported' section for transparency.
  • Where PowerShell is referenced for deployment, provide equivalent Azure CLI or REST API examples, which are cross-platform and usable from Linux.
  • Include guidance or links for Linux administrators who may be seeking disaster recovery solutions for Linux-based hypervisors.
  • Ensure parity in documentation by listing Linux guest OS requirements and supported features in detail, similar to Windows.
  • Add a comparison table or FAQ clarifying differences in support for Windows and Linux environments, both as hosts and guests.
GitHub Create Pull Request
Site Recovery Common questions for Hyper-V disaster recovery with Azure Site Recovery ...ticles/site-recovery/hyper-v-azure-common-questions.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation is heavily focused on Windows environments, specifically Hyper-V on Windows Server, with exclusive references to Windows tools (Hyper-V, VMM, PowerShell) and no mention of Linux equivalents or cross-platform scenarios. All examples and instructions assume Windows-based hosts and management tools, and automation is described only via PowerShell, with no Bash or Linux CLI alternatives. There is no guidance for Linux-based hypervisors or management, nor parity in example scripts or tooling.
Recommendations
  • Add explicit statements clarifying that Azure Site Recovery for Hyper-V is a Windows-only solution, and provide links to documentation for Linux-based disaster recovery options (e.g., Azure Site Recovery for VMware, or Azure Backup for Linux VMs).
  • Where automation is discussed (e.g., PowerShell), include equivalent examples for Bash/CLI, or clarify if PowerShell is required and provide guidance for Linux users.
  • Mention alternative hypervisors and their support status (e.g., KVM, Xen, VMware) and provide links to relevant documentation for Linux environments.
  • Add a section comparing Windows and Linux disaster recovery approaches in Azure, highlighting feature parity and differences.
  • Ensure that any tool or process described (e.g., Deployment Planner, Recovery Services agent) includes notes about platform compatibility and Linux alternatives if available.
GitHub Create Pull Request
Site Recovery Troubleshoot Hyper-V disaster recovery with Azure Site Recovery ...n/articles/site-recovery/hyper-v-azure-troubleshoot.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation is heavily focused on Windows environments, specifically Hyper-V and related Windows Server components. Troubleshooting steps, log locations, and tool usage are almost exclusively described for Windows, with PowerShell and Windows GUI tools (Event Viewer, Resource Monitor, Disk Management) featured throughout. Linux is mentioned only once, in passing, with no concrete troubleshooting steps or examples provided for Linux-based VMs or hosts.
Recommendations
  • Add troubleshooting steps and log locations for Linux-based VMs, including guidance for common Linux distributions.
  • Provide Linux command-line equivalents for PowerShell commands, such as using 'systemctl', 'journalctl', or 'lsblk' for service and disk checks.
  • Include examples of how to verify VSS/app-consistent snapshot status on Linux, referencing relevant Linux backup tools and integration services.
  • List Linux-specific requirements and prerequisites for Azure Site Recovery replication, and link to relevant documentation.
  • Ensure parity in error code explanations and remediation steps for Linux environments.
  • Present troubleshooting steps for both Windows and Linux in parallel, or clearly separate them into distinct sections.
GitHub Create Pull Request
Site Recovery Set up Hyper-V disaster recovery by using Azure Site Recovery .../main/articles/site-recovery/hyper-v-azure-tutorial.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation is heavily focused on Windows environments, specifically Hyper-V on Windows Server. All examples, instructions, and tooling references (such as the Azure Site Recovery provider, MARS agent, and command-line examples) are tailored to Windows systems. There are no Linux equivalents, nor is there any mention of how to achieve similar disaster recovery for Linux-based hypervisors (e.g., KVM, Xen) or Linux hosts. Windows-specific tools and patterns (setup wizards, .exe installers, Windows command prompt syntax) are used exclusively, and Linux is not referenced at all.
Recommendations
  • Add explicit statements clarifying that the tutorial is Windows/Hyper-V specific and provide links to Linux-based disaster recovery documentation if available.
  • Include equivalent guidance or links for disaster recovery of Linux-based hypervisors (e.g., KVM, Xen) to Azure, if supported.
  • Where possible, provide parity examples for Linux environments, such as using Azure Site Recovery with Linux VMs or alternative replication agents.
  • Mention any limitations or unsupported scenarios for Linux users up front, to help set expectations.
  • If Azure Site Recovery does not support Linux hypervisors, suggest alternative Azure solutions for Linux disaster recovery.
GitHub Create Pull Request
Site Recovery Deployment Planner for Hyper-V disaster recovery with Azure Site Recovery ...s/site-recovery/hyper-v-deployment-planner-overview.md
High Priority View Details →
Scanned: 2026-01-11 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 is heavily biased towards Windows environments. All examples, prerequisites, and instructions assume Windows Server (2012 R2/2016) as the operating system, with exclusive use of PowerShell commands and Windows-specific tools (e.g., .NET Framework, Visual C++ Redistributable, Microsoft Excel). There are no Linux equivalents or cross-platform instructions, and the deployment planner tool appears to be designed for Windows only, with no mention of Linux support or usage.
Recommendations
  • Clarify whether the deployment planner tool can run on Linux or provide a Linux-compatible version if possible.
  • Include Linux-specific instructions and examples for any steps that could be performed on Linux (e.g., trusted hosts configuration, report generation).
  • If PowerShell is required, mention PowerShell Core and its cross-platform capabilities, or provide Bash/CLI alternatives where feasible.
  • List Linux prerequisites and supported distributions if Linux support is available.
  • Provide parity in tooling (e.g., alternatives to Microsoft Excel for report viewing on Linux, such as LibreOffice or web-based viewers).
  • Explicitly state platform limitations and recommend workarounds for Linux users.
GitHub Create Pull Request
Site Recovery Run the Hyper-V Deployment Planner in Azure Site Recovery ...ticles/site-recovery/hyper-v-deployment-planner-run.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation is heavily oriented toward Windows environments, specifically Hyper-V, and provides only Windows-centric examples and instructions. All command-line examples use Windows paths and conventions, and tools referenced (ASRDeploymentPlanner.exe) are Windows executables. There is no mention of Linux equivalents, nor are Linux-specific instructions, examples, or considerations provided.
Recommendations
  • Provide explicit information on whether the tool can be run on Linux (e.g., via Mono, Wine, or a native Linux version), or clarify Windows-only support.
  • Include Linux-specific examples for file paths, command-line usage, and text editors (e.g., using nano or vi instead of Notepad).
  • If the tool is Windows-only, suggest alternative approaches for Linux users or reference cross-platform tools where available.
  • Document any limitations or requirements for running the tool in non-Windows environments, and provide troubleshooting guidance for Linux users.
  • Consider adding a section comparing Hyper-V (Windows) and VMware (potentially Linux-hosted) scenarios, with parity in instructions and examples.
GitHub Create Pull Request
Site Recovery Prepare on-premises Hyper-V servers for disaster recovery by using Azure Site Recovery .../site-recovery/hyper-v-prepare-on-premises-tutorial.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation is heavily focused on Windows environments, specifically Hyper-V and System Center Virtual Machine Manager, which are Windows-only technologies. All examples and instructions pertain to Windows VMs, Windows Firewall, and RDP, with no mention of Linux VM preparation, Linux firewall configuration, or SSH access. The guidance for post-failover VM access is exclusively for Windows VMs, and there are no Linux equivalents or cross-platform considerations.
Recommendations
  • Add instructions for preparing Linux VMs for disaster recovery, including steps for enabling SSH access, configuring Linux firewalls (e.g., ufw, firewalld), and verifying connectivity after failover.
  • Include examples for both Windows and Linux VMs when discussing access methods post-failover (e.g., RDP for Windows, SSH for Linux).
  • Mention any Azure Site Recovery requirements or considerations specific to Linux VMs, such as supported distributions and agent installation.
  • When discussing firewall rules, provide guidance for both Windows Firewall and common Linux firewall tools.
  • Ensure troubleshooting tips cover common issues for Linux VMs as well as Windows VMs.
GitHub Create Pull Request
Site Recovery About Hyper-V (with VMM) network mapping with Site Recovery .../articles/site-recovery/hyper-v-vmm-network-mapping.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation is heavily focused on Hyper-V and System Center Virtual Machine Manager (VMM), which are Windows-centric virtualization and management tools. There are no references to Linux-based hypervisors (such as KVM, Xen, or VMware ESXi), nor any examples or guidance for non-Windows environments. All terminology, examples, and network mapping scenarios assume the use of Windows tools and infrastructure, with no mention of Linux equivalents or cross-platform considerations.
Recommendations
  • Add sections or examples for Linux-based hypervisors (e.g., KVM, Xen, VMware) and their network mapping processes with Azure Site Recovery.
  • Include guidance for organizations using mixed environments (Windows and Linux) and how network mapping works in such scenarios.
  • Reference Linux-compatible management tools or scripts for network mapping, if available, and provide parity in documentation structure and examples.
  • Clarify in the introduction that the guidance is specific to Hyper-V/VMM, and link to documentation for other platforms if available.
GitHub Create Pull Request
Site Recovery Analyze the Hyper-V Deployment Planner report in Azure Site Recovery ...-recovery/hyper-v-deployment-planner-analyze-report.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation is heavily focused on Hyper-V, a Windows-only virtualization platform, and all examples, terminology, and tooling are specific to Windows environments. There is no mention of Linux-based hypervisors (such as KVM or VMware on Linux), nor are there any examples, instructions, or considerations for Linux hosts or VMs. Windows tools and patterns (such as Excel reports, VHD/VHDX disk formats, and Hyper-V Replica Broker) are referenced exclusively, with no Linux equivalents or alternatives provided.
Recommendations
  • Add sections or references for Linux-based virtualization platforms (e.g., KVM, VMware on Linux) and how to use Azure Site Recovery Deployment Planner in those environments, if supported.
  • Include examples and terminology relevant to Linux hosts and VMs, such as disk formats (QCOW2, VMDK), Linux storage paths, and Linux-specific replication considerations.
  • If the tool is Windows-only, explicitly state this limitation and provide guidance or alternatives for Linux users.
  • Where possible, provide parity in tooling and instructions for Linux environments (e.g., CLI commands, report formats compatible with Linux tools).
  • Mention any Azure Site Recovery features or limitations that are specific to Linux VMs or hosts.
GitHub Create Pull Request
Site Recovery Exclude Hyper-V VM disks from disaster recovery to Azure with Azure Site Recovery ...ob/main/articles/site-recovery/hyper-v-exclude-disk.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation is focused exclusively on Hyper-V, a Windows virtualization platform, and does not mention Linux-based hypervisors (such as KVM or VMware on Linux), nor does it provide examples or guidance for excluding disks from replication for Linux VMs or using Linux tools. The instructions and scenarios are tailored to Windows environments, with no parity for Linux users.
Recommendations
  • Include guidance for excluding disks from replication for Linux-based hypervisors (e.g., KVM, VMware on Linux).
  • Provide examples and screenshots for Linux environments where applicable.
  • Mention any differences or limitations when working with Linux VMs in Azure Site Recovery.
  • Add references to Linux tools or commands that can be used to manage disk exclusion, if supported.
  • Clarify whether the described process is exclusive to Hyper-V or if similar functionality exists for other platforms, and link to relevant documentation.
GitHub Create Pull Request
Site Recovery Set up Hyper-V (with VMM) disaster recovery using Azure Site Recovery ...n/articles/site-recovery/hyper-v-vmm-azure-tutorial.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation is heavily focused on Windows environments, specifically Hyper-V managed by System Center VMM. All examples, installation instructions, and command-line snippets use Windows tools (e.g., PowerShell, Windows installers) and reference Windows-specific components. There are no Linux equivalents or cross-platform guidance, and Windows terminology and steps are presented exclusively and first throughout the tutorial.
Recommendations
  • Add explicit statements clarifying that the tutorial is Windows-specific, and link to Linux/KVM/VMware alternatives if available.
  • Provide parity by including Linux-based disaster recovery scenarios, or at minimum, reference documentation for Linux environments.
  • Where possible, mention cross-platform Azure Site Recovery capabilities and tools, and provide examples for Linux hosts (e.g., using shell commands or Linux agents).
  • Include a comparison table or section outlining differences and similarities between Windows and Linux disaster recovery setups with Azure Site Recovery.
  • Ensure that prerequisites and environment setup sections acknowledge non-Windows platforms and guide users to relevant resources.
GitHub Create Pull Request
Site Recovery Monitor Azure Site Recovery with Azure Monitor Logs ...b/main/articles/site-recovery/monitor-log-analytics.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation page exhibits a Windows bias, especially in the section on configuring the Microsoft monitoring agent for churn and upload rate logs. Instructions and screenshots focus exclusively on Windows Server and the Windows agent, with no mention of Linux equivalents or guidance for Linux-based Process Servers. The agent installation steps, workspace connection, and performance counter configuration are all described only for Windows. There are no examples or instructions for Linux-based monitoring agents, nor is there any mention of Linux tools or patterns. The log query and alerting examples are platform-neutral, but the prerequisite and agent setup sections are Windows-centric.
Recommendations
  • Add instructions and screenshots for installing and configuring the Microsoft monitoring agent on Linux-based Process Servers, including links to Linux agent documentation.
  • Include guidance for configuring performance counters or equivalent metrics collection on Linux, if supported.
  • Mention Linux support explicitly in prerequisites and agent setup sections, clarifying any limitations or differences.
  • Provide parity in examples and troubleshooting steps for both Windows and Linux environments.
  • Reference Linux tools and patterns (such as systemd, syslog, or Linux-specific monitoring agents) where relevant.
GitHub Create Pull Request
Site Recovery Set up the configuration server for disaster recovery of physical servers to Azure using Azure Site Recovery ...articles/site-recovery/physical-azure-set-up-source.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by referencing Windows-specific requirements (such as .NET Framework and Windows Time Service), providing no Linux-specific setup instructions or examples, and mentioning Windows tools and patterns without Linux equivalents. Although the article claims to support both Windows and Linux physical servers, all concrete steps and troubleshooting are framed in a Windows context.
Recommendations
  • Add explicit instructions and examples for setting up the configuration server on Linux physical servers, including any prerequisites, dependencies, and command-line steps.
  • Include Linux-specific requirements (e.g., required packages, time synchronization methods such as chrony or ntpd) alongside Windows requirements.
  • Reference Linux equivalents for tools and concepts (e.g., instead of only mentioning the Windows Time Service, mention how to synchronize time on Linux).
  • Provide command-line installation and troubleshooting examples for both Windows (PowerShell/cmd) and Linux (bash/shell).
  • Ensure screenshots and UI references are supplemented with CLI or Linux-native alternatives where possible.
GitHub Create Pull Request
Site Recovery Manage the configuration server for physical servers in Azure Site Recovery .../site-recovery/physical-manage-configuration-server.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation page exhibits a strong Windows bias. All prerequisites, installation steps, and examples are focused exclusively on Windows Server environments. Only Windows Server OS versions are listed as supported, and all command-line and automation examples use Windows tools (e.g., PowerShell, reg.exe, cspsconfigtool.exe). There are no references to Linux equivalents, nor any guidance for deploying or managing the configuration server on Linux or other non-Windows platforms.
Recommendations
  • Explicitly state whether Linux is supported or not. If not, clarify the Windows-only requirement early in the documentation.
  • If Linux support is possible, add Linux prerequisites and supported distributions to the prerequisites table.
  • Provide Linux-specific installation and management instructions, including command-line examples using bash, systemctl, and relevant Linux tools.
  • Offer parity for automation and scripting by including bash scripts or CLI commands alongside PowerShell examples.
  • Reference Linux equivalents for system management tasks (e.g., uninstalling packages, managing services, editing configuration files).
  • If certain tools (e.g., cspsconfigtool.exe) are Windows-only, suggest or provide alternatives for Linux environments.
GitHub Create Pull Request
Site Recovery Set up disaster recovery of physical on-premises servers with Azure Site Recovery ...cles/site-recovery/physical-azure-disaster-recovery.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation mentions both Windows and Linux servers in the introduction, but throughout the page, examples and instructions are predominantly Windows-centric. Registry edits and CLI commands are provided only for Windows, with no equivalent Linux commands or configuration details. Windows-specific tools and patterns (e.g., registry edits, domain/local accounts) are described in detail, while Linux instructions are minimal and lack parity. The order of presentation and depth of detail favors Windows, and Linux users are left to infer steps or consult external resources.
Recommendations
  • Provide explicit Linux examples alongside Windows instructions, such as commands for configuring root access, installing the Mobility service, and verifying prerequisites.
  • Include Linux-specific troubleshooting steps and configuration details (e.g., SELinux, firewall, time synchronization using ntpd/chrony).
  • Ensure that instructions for both platforms are presented in parallel, with equal detail and clarity.
  • Add sample CLI commands for Linux (e.g., using sudo, modifying config files) where Windows registry or PowerShell commands are given.
  • Reference Linux documentation and tools (e.g., systemctl, journalctl) where appropriate.
GitHub Create Pull Request
Site Recovery Physical server to Azure disaster recovery architecture – Modernized ...overy/physical-server-azure-architecture-modernized.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page, while mentioning both Windows and Linux servers in its scope, demonstrates a Windows bias in several ways. Windows-specific technologies (such as VSS for app-consistent snapshots) are described in detail, with no equivalent Linux mechanisms or examples provided. The replication and snapshot processes are explained using Windows terminology and tools, and there are no Linux-specific instructions, examples, or references to Linux snapshot/consistency tools. The documentation also refers to Windows-centric recovery scenarios and does not provide parity for Linux environments.
Recommendations
  • Add explicit examples and instructions for Linux servers, including how app-consistent snapshots are achieved (e.g., using fsfreeze, LVM snapshots, or application-specific hooks).
  • Describe the differences in replication and failover processes for Linux systems, including any limitations or required configurations.
  • Include Linux-specific troubleshooting steps, error messages, and recovery recommendations.
  • Mention Linux tools and patterns (such as systemd, cron, or native Linux backup utilities) where relevant, and provide parity with Windows examples.
  • Ensure that all process descriptions and tables include both Windows and Linux perspectives, not just Windows-centric details.
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
High Priority View Details →
Scanned: 2026-01-11 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 referencing Windows-specific features (e.g., availability sets), mentioning Windows operating systems before Linux, and omitting Linux-specific examples or instructions. There is no parity in examples or guidance for Linux physical servers, and Windows terminology and tools are prioritized throughout the page.
Recommendations
  • Include explicit instructions and examples for Linux physical servers, such as post-failover connectivity, OS-specific settings, and troubleshooting steps.
  • Reference Linux equivalents alongside Windows features (e.g., availability sets, disk settings) and provide links to relevant Linux documentation.
  • Ensure that any mention of operating systems lists Linux and Windows together, or alternates the order to avoid implicit prioritization.
  • Add Linux-specific automation and scripting examples (e.g., Bash scripts) in sections discussing automation during failover.
  • Clarify any differences in failover/failback processes for Linux servers, and provide troubleshooting steps for common Linux scenarios.
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
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation demonstrates a Windows bias in several areas: registry modification instructions and CLI examples are provided only for Windows (using REG and registry paths), with no equivalent Linux commands or configuration steps. Windows-specific tools and patterns (such as registry editing and references to Windows Time Service) are mentioned explicitly, while Linux instructions are minimal and lack detail. Windows steps are described first and in more depth than Linux steps.
Recommendations
  • Provide equivalent Linux command-line instructions for required configuration changes (e.g., how to prepare the root account, any necessary SSH or sudo configuration).
  • Include Linux-specific troubleshooting steps and references (e.g., NTP configuration for time sync, relevant systemd or service commands).
  • When mentioning Windows registry changes, also describe any analogous Linux configuration requirements (if applicable), and provide sample commands.
  • Ensure examples and instructions for both Windows and Linux are presented with equal detail and prominence, ideally side-by-side.
  • Reference Linux documentation and tools (such as chrony/ntpd for time sync, firewall-cmd/iptables for firewall rules) where appropriate.
GitHub Create Pull Request
Site Recovery Set up Active Directory/DNS disaster recovery with Azure Site Recovery ...ticles/site-recovery/site-recovery-active-directory.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First Missing Linux Example
Summary
The documentation is heavily oriented toward Windows environments, specifically Windows Server-based Active Directory and DNS. All examples, troubleshooting steps, and commands use Windows tools (e.g., NET SHARE, dcdiag, nltest, dnscmd) and reference Windows registry edits. There are no examples or guidance for Linux-based domain controllers (such as Samba AD DC) or DNS servers, nor any mention of cross-platform considerations. Windows terminology and tools are used exclusively and are presented first and only.
Recommendations
  • Add guidance for disaster recovery of Samba-based Active Directory domain controllers running on Linux, including replication and failover steps.
  • Include examples for managing DNS on Linux (e.g., BIND, dnsmasq), such as zone file updates and service management.
  • Provide parity in troubleshooting steps for Linux-based domain controllers and DNS servers, including equivalent commands and log locations.
  • Reference cross-platform tools and patterns where applicable, and clarify which steps are Windows-specific.
  • Explicitly state platform requirements and limitations at the beginning of the document, and link to Linux-specific documentation if available.
GitHub Create Pull Request
Site Recovery Disaster recovery of Dynamics AX with Azure Site Recovery ...ain/articles/site-recovery/site-recovery-dynamicsax.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation is heavily oriented toward Windows environments, specifically referencing Windows Server, Active Directory, and SQL Server, with no mention of Linux-based alternatives or examples. All technical guidance and examples assume Windows-based deployments, and there is no coverage of Linux equivalents or cross-platform considerations.
Recommendations
  • Include examples and guidance for Linux-based deployments, such as using Samba for domain services or PostgreSQL/MySQL for the database tier.
  • Mention and provide parity for Linux-based disaster recovery scenarios, including how Azure Site Recovery supports Linux VMs and any differences in configuration.
  • Add references to Linux tools and patterns where applicable, such as using Linux DNS servers, and provide step-by-step instructions for protecting Linux workloads.
  • Ensure that documentation does not assume Windows-only environments and explicitly state support for both Windows and Linux platforms.
GitHub Create Pull Request
Site Recovery Support Requirements for Azure Site Recovery Replication Appliance .../site-recovery/replication-appliance-support-matrix.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows Only Missing Linux Example 🔧 Windows Tools Windows Heavy
Summary
The documentation page exclusively references Windows Server as the supported operating system for the replication appliance, with no mention of Linux or other OS options. All folder paths and antivirus exclusions use Windows conventions (e.g., C:\Program Files), and requirements such as group policies, IIS settings, and Windows Server roles are specific to Windows environments. There are no Linux equivalents, examples, or guidance provided, indicating a strong Windows bias.
Recommendations
  • Clearly state whether Linux-based appliances are supported or not. If not, explain the rationale.
  • If Linux support is possible, provide equivalent requirements, folder paths, and antivirus exclusions for Linux systems.
  • Include examples and instructions for Linux environments where applicable (e.g., using Linux-based VMs for the appliance, Linux firewall configuration, Linux antivirus exclusions).
  • Mention Linux tools or patterns (e.g., systemd services, SELinux/AppArmor configuration) if relevant.
  • If Windows-only support is intentional, add a note at the top clarifying that Linux is not supported, to avoid confusion for cross-platform administrators.
GitHub Create Pull Request
Site Recovery Support matrix for shared disks in Azure VM disaster recovery ...n/articles/site-recovery/shared-disk-support-matrix.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exclusively describes support for Windows virtual machines, Windows Server SKUs, and Windows Server Failover Clustering (WSFC) in the context of Azure Site Recovery shared disks. There is no mention of Linux workloads, Linux clustering solutions, or examples relevant to Linux users. The clustering configuration and supported scenarios are all Windows-centric, and no Linux equivalents or guidance are provided.
Recommendations
  • Explicitly state whether Linux virtual machines and Linux clustering solutions (e.g., Pacemaker, Corosync) are supported or unsupported.
  • Add a section or table detailing support for Linux workloads, including any limitations or requirements.
  • Provide examples and guidance for disaster recovery scenarios involving Linux VMs and clusters.
  • If Linux is not supported, clarify this early in the documentation to help users plan accordingly.
  • Include references to Linux documentation or migration strategies for users with Linux workloads.
GitHub Create Pull Request
Site Recovery Azure Site Recovery Deployment Planner for VMware disaster recovery ...cles/site-recovery/site-recovery-deployment-planner.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation for the Azure Site Recovery Deployment Planner for VMware disaster recovery demonstrates a strong Windows bias. All instructions, requirements, and examples assume the use of Windows Server or Windows PC environments. There is no mention of Linux support, Linux-based prerequisites, or examples for running the tool on Linux systems. The tool itself appears to be Windows-only, and all references to operating systems, dependencies (.NET Framework, Visual C++ Redistributable), and report generation (Excel on Windows) are Windows-centric.
Recommendations
  • Explicitly state if the tool is Windows-only, and if so, provide rationale and alternatives for Linux users.
  • If possible, develop and document a Linux-compatible version of the Deployment Planner tool.
  • Provide guidance for running the tool in a Linux environment (e.g., via Wine, containers, or cross-platform .NET if supported).
  • Include Linux-specific examples and instructions for download, extraction, and execution.
  • List Linux equivalents for prerequisites (e.g., Mono/.NET Core, LibreOffice for Excel reports) if feasible.
  • Clarify any limitations for non-Windows users and suggest workarounds or alternative tools.
GitHub Create Pull Request
← Previous Page 4 of 35 Next →