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 176-200 of 864 flagged pages
Site Recovery Configure Mobility Service Proxy Settings for Azure to Azure Disaster Recovery | Microsoft Docs ...-recovery/configure-mobility-service-proxy-settings.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation page demonstrates a Windows bias by presenting Windows-specific instructions and tools (such as Internet Explorer and psexec) before Linux equivalents. Windows methods are described in greater detail, and Windows paths are referenced first. Linux instructions are present but less detailed and appear after Windows guidance.
Recommendations
  • Provide Linux instructions with equal detail and prominence, including step-by-step guidance for setting proxy environment variables and editing ProxyInfo.conf.
  • Avoid referencing Windows tools (e.g., Internet Explorer, psexec) without offering Linux alternatives or equivalent commands (such as using export or editing /etc/environment).
  • List Linux and Windows instructions in parallel or in separate, equally prominent sections, rather than presenting Windows first.
  • Include example commands for both platforms (e.g., how to set environment variables or edit config files on Linux).
  • Clarify any platform-specific limitations or differences, ensuring Linux users have all necessary information.
GitHub Create Pull Request
Site Recovery Exclude disks from replication with Azure Site Recovery ...in/articles/site-recovery/exclude-disks-replication.md
High Priority View Details →
Scanned: 2026-01-10 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 demonstrates a Windows bias by focusing exclusively on Windows VM scenarios and examples, including SQL Server and paging file management, with no Linux VM examples or guidance. Windows-specific tools and patterns (diskmgmt.msc, drive letters, service console, screenshots of Windows dialogs) are used throughout, and all example walkthroughs are for Windows VMs. Linux scenarios are only briefly mentioned in passing (e.g., failback behavior), without any practical instructions or examples.
Recommendations
  • Add equivalent examples for Linux VMs, such as excluding disks containing swap partitions or temp directories, and handling failover/failback for Linux workloads.
  • Include Linux-specific instructions for disk management (e.g., using lsblk, parted, or fdisk), mounting disks, and updating fstab.
  • Provide sample commands for managing services and files on Linux (e.g., systemctl for service management, shell commands for file operations).
  • Include screenshots or terminal output relevant to Linux environments.
  • Clarify any differences in failover/failback behavior for Linux VMs, and provide troubleshooting steps.
  • Ensure that both Windows and Linux scenarios are presented in parallel where possible, or at least alternate examples.
GitHub Create Pull Request
Site Recovery Deploy Azure Site Recovery Replication Appliance - Modernized ...tps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/deploy-vmware-azure-replication-appliance-modernized.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in several ways: PowerShell is presented as the only command-line method for manual appliance setup, with no Linux shell or cross-platform alternatives. Registry and group policy checks are exclusively Windows-specific, and all troubleshooting and configuration steps reference Windows tools and concepts. The order of presentation also puts Windows-centric methods (PowerShell, registry, group policy) before any mention of Linux, which is only referenced in passing when discussing credentials for VMs. There are no Linux shell examples or instructions for deploying or managing the appliance from a Linux environment.
Recommendations
  • Provide equivalent Linux shell (bash) instructions for manual appliance setup, including any scripts or commands needed.
  • Document Linux-specific prerequisites and troubleshooting steps (e.g., SELinux/AppArmor, systemd services, firewall configuration) alongside Windows registry/group policy checks.
  • Clarify whether the appliance can be deployed or managed from Linux hosts, and if so, include explicit steps and examples.
  • Ensure parity in credential management instructions, showing how to securely provide credentials for Linux VMs using Linux-native tools.
  • Review the order of presentation to avoid Windows-first bias, and explicitly state platform requirements and limitations at the outset.
GitHub Create Pull Request
Site Recovery About failover and failback in Azure Site Recovery - Modernized ...site-recovery/failover-failback-overview-modernized.md
High Priority View Details →
Scanned: 2026-01-10 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 Windows bias in several ways: Windows VM connection instructions are presented first and in more detail, with explicit references to Windows Firewall, RDP, and Windows Update. Linux instructions are shorter and lack equivalent troubleshooting or configuration details. Windows-specific tools and patterns (Windows Firewall, SAN policy, Windows Update) are mentioned, while Linux equivalents (e.g., iptables, systemd, package updates) are omitted. Troubleshooting links and notes are Windows-centric, and there is no parity in examples or depth for Linux VMs.
Recommendations
  • Present Linux and Windows instructions in parallel, giving equal detail and prominence.
  • Include Linux-specific troubleshooting steps (e.g., SSH daemon status, firewall configuration with iptables or firewalld, SELinux/AppArmor issues).
  • Reference Linux tools and configuration patterns where Windows tools are mentioned (e.g., mention how to check/update SSH service, handle package updates, set disk policies).
  • Provide links to Linux-specific documentation and troubleshooting guides, similar to those given for Windows.
  • Ensure that notes and caveats (such as boot time issues) are provided for both Windows and Linux, or clarify when they are OS-specific.
  • Add examples for Linux environments where only Windows/PowerShell examples are given.
GitHub Create Pull Request
Site Recovery New feature updates in Azure Site Recovery ...in/articles/site-recovery/feature-updates-whats-new.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by frequently referencing Windows Server Failover Clusters, Windows OS support, and PowerShell, while Linux equivalents are either missing or mentioned secondarily. Feature support and examples are often described for Windows first, with Linux support noted as preview or secondary. There is a lack of Linux-specific examples, tools, and parity in feature descriptions.
Recommendations
  • Include explicit Linux support details and examples for features currently described only for Windows (e.g., Shared Disk, Failover Clusters).
  • Provide Linux command-line (e.g., Bash, CLI) examples alongside PowerShell where relevant.
  • Mention Linux tools and patterns (such as Pacemaker clusters, mdadm, LVM, etc.) when discussing clustering and shared disk scenarios.
  • Ensure feature availability and status for Linux is described with equal prominence as Windows, not as an afterthought or only in preview.
  • Add documentation sections or links for Linux-specific disaster recovery scenarios and best practices.
GitHub Create Pull Request
Site Recovery Protect a file server by using Azure Site Recovery ...rticles/site-recovery/file-server-disaster-recovery.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a strong Windows bias. It focuses almost exclusively on Windows-centric technologies such as DFSR, Active Directory, and Azure File Sync (which is only supported on Windows servers). All step-by-step instructions and architectural recommendations are tailored to Windows environments, with no equivalent examples or guidance for Linux file servers. References to protocols (SMB) and mounting instructions link to Windows documentation, and Linux is only mentioned briefly as a client, not as a server or participant in replication or failover workflows.
Recommendations
  • Add explicit guidance and examples for protecting Linux-based file servers using Azure Site Recovery, including step-by-step instructions.
  • Include parity for Linux tools and patterns, such as rsync, NFS, or native Azure Files mounting from Linux VMs.
  • Provide links to Linux documentation for mounting Azure file shares and performing disaster recovery operations.
  • Clarify which features and workflows are Windows-only, and offer alternative approaches for Linux environments.
  • Add sample scripts or automation for Linux failover and recovery scenarios, similar to those provided for Windows.
GitHub Create Pull Request
Site Recovery Configure on-premise disks for Azure through Hydration .../blob/main/articles/site-recovery/hydration-process.md
High Priority View Details →
Scanned: 2026-01-10 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 demonstrates a Windows bias in several ways: Windows configuration steps and examples are presented first and in greater detail, including screenshots and explicit PowerShell commands. Windows-specific tools (diskpart, PowerShell, registry editing) are described with step-by-step instructions and visuals, while Linux instructions are less detailed, lack screenshots, and only provide illustrative examples for select distributions (mainly RedHat). There are no Linux equivalents for some Windows tools (e.g., diskpart), and Linux examples are less comprehensive, with fewer explicit commands or troubleshooting steps.
Recommendations
  • Present Windows and Linux instructions in parallel sections or tabs, ensuring equal prominence and detail.
  • Add Linux-specific screenshots and step-by-step commands for common distributions (e.g., Ubuntu, Debian, SUSE) where only RedHat examples are currently given.
  • Provide Linux equivalents for Windows tools (e.g., show how to check disk mount status, DHCP configuration, and agent installation using native Linux commands).
  • Include troubleshooting steps and error messages for Linux environments, similar to those provided for Windows.
  • Avoid using Windows-first ordering; alternate or group by OS type for clarity and parity.
  • Expand manual preparation instructions for Linux to cover more distributions and edge cases, matching the depth given to Windows.
GitHub Create Pull Request
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-10 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, prerequisites, and examples tailored to Windows-based hosts. There is no mention of Linux-based hypervisors, tools, or failback scenarios, and all steps assume the use of Windows and Hyper-V. This creates a strong Windows bias and excludes Linux users from understanding or applying the failback process.
Recommendations
  • Add equivalent instructions and examples for Linux-based hypervisors (e.g., KVM, VMware on Linux) if supported by Azure Site Recovery.
  • Explicitly state whether failback is supported for Linux hosts, and if not, clarify the scope and limitations.
  • Include Linux-specific prerequisites, such as supported distributions, required packages, and configuration steps.
  • Provide parity in tooling and terminology, mentioning Linux alternatives to Windows tools (e.g., using native Linux commands or management interfaces).
  • If Azure Site Recovery does not support Linux failback, add a clear note at the beginning of the documentation to inform users.
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-10 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 related Microsoft technologies (Windows Server, System Center Virtual Machine Manager, PowerShell). Linux is only mentioned as a guest OS, with no guidance or examples for Linux-based Hypervisors or management tools. All deployment and management instructions reference Windows-centric tools and patterns, and PowerShell is the only scripting example mentioned. There are no Linux CLI or automation examples, nor references to Linux-based disaster recovery scenarios.
Recommendations
  • Explicitly state that Azure Site Recovery for Hyper-V is a Windows-only solution, or clarify Linux support limitations.
  • Add parity by including Linux-based hypervisor scenarios (e.g., KVM, Xen) if supported, or link to equivalent documentation for Linux environments.
  • Provide CLI examples using Azure CLI or Bash scripts alongside PowerShell, especially for deployment and configuration steps.
  • Mention Linux management tools (e.g., Ansible, SSH) if relevant, or clarify their applicability.
  • Ensure guest OS support tables and instructions are clear for both Windows and Linux, including any differences in failover, networking, and storage.
  • If Linux is not supported as a host, add a prominent note to avoid confusion for cross-platform administrators.
GitHub Create Pull Request
Site Recovery Replicate Azure virtual machines running in a proximity placement group ...tps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/how-to-enable-replication-proximity-placement-groups.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a strong Windows bias. All command-line examples are exclusively provided using PowerShell, a tool primarily associated with Windows environments. There are no Bash, Azure CLI, or Linux-native command examples. The prerequisites and instructions for scripting and automation focus on Azure PowerShell, with no mention of cross-platform alternatives. The referenced links and terminology (e.g., 'Hyper-V', 'PowerShell Az module') further reinforce a Windows-centric approach. Linux is only mentioned in passing, and there are no step-by-step examples for Linux users.
Recommendations
  • Add equivalent Azure CLI and Bash examples for all PowerShell commands, especially for core replication and failover operations.
  • Include instructions for installing and using Azure CLI on Linux and macOS, alongside PowerShell.
  • Reference Linux tools and workflows (e.g., Bash scripts, cron jobs) where appropriate.
  • Ensure that all automation and scripting sections provide parity between Windows and Linux environments.
  • Explicitly state platform compatibility for each tool or command, and provide guidance for cross-platform users.
  • Add screenshots and walkthroughs from Linux environments (e.g., Ubuntu terminal) in addition to Windows PowerShell.
  • Review and update terminology to be inclusive of both Windows and Linux users (e.g., avoid assuming PowerShell as the default).
GitHub Create Pull Request
Site Recovery Enable replication for on-premises machines with private endpoints ...https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/hybrid-how-to-enable-replication-private-endpoints.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits a Windows bias in several ways: Windows-related domains and tools are referenced first and exclusively (e.g., *.windows.net, Azure PowerShell), and there are no explicit Linux or cross-platform CLI examples. The guidance for creating private endpoints and managing resources is focused on the Azure portal and Azure PowerShell, with no mention of Azure CLI or Linux-specific workflows. The URLs to be allowed are almost entirely Windows-centric, and there is no parity in examples or instructions for Linux administrators.
Recommendations
  • Add Azure CLI examples alongside Azure PowerShell for all resource creation and management steps.
  • Explicitly mention Linux compatibility and provide instructions for Linux-based environments, including shell commands and screenshots from Linux systems.
  • Include references to Linux tools and patterns where applicable (e.g., Bash, curl, OpenSSL for connectivity checks).
  • Ensure that documentation for proxy configuration, DNS, and network setup includes Linux-specific guidance and troubleshooting.
  • Balance the order and prominence of Windows and Linux instructions/examples to avoid Windows-first presentation.
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-10 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, and System Center Virtual Machine Manager (VMM). All examples, prerequisites, and supported scenarios are described in terms of Windows tools and patterns, such as PowerShell, Hyper-V Replica, and VMM. There are no Linux equivalents or examples, and Linux-based hypervisors (e.g., KVM, Xen) are not mentioned. Automation is described only via PowerShell, with no reference to Bash, CLI, or Linux-native tooling.
Recommendations
  • Add explicit statements about Linux support or limitations for Azure Site Recovery in Hyper-V scenarios.
  • Provide examples or guidance for disaster recovery from Linux-based hypervisors if supported, or link to relevant documentation for Linux environments.
  • Include automation examples using Azure CLI or REST API from Linux environments, not just PowerShell.
  • Mention Linux guest OS support and any differences in replication or failover processes compared to Windows guests.
  • Clarify whether tools like the Recovery Services agent or Deployment Planner are available for Linux hosts, and provide installation instructions if so.
  • If only Windows/Hyper-V is supported, state this clearly at the beginning to set expectations for cross-platform users.
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-10 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 provides instructions and examples exclusively for Windows-based tools and workflows. All setup steps, installer instructions, and command-line examples use Windows executables and paths, with no mention of Linux equivalents or cross-platform alternatives. There is no guidance for Linux-based hypervisors or recovery agents, and all screenshots and walkthroughs assume a Windows context.
Recommendations
  • Add explicit statements clarifying that the tutorial is for Windows/Hyper-V only, and link to Linux/KVM/VMware disaster recovery documentation if available.
  • Provide parity by including steps or references for Linux-based hypervisors (e.g., KVM, Xen) where Azure Site Recovery supports them.
  • If Azure Site Recovery does not support Linux hosts for this scenario, state this limitation clearly in the prerequisites.
  • Where possible, mention cross-platform tools or alternatives to Windows-only utilities (e.g., PowerShell, .exe installers).
  • Include a comparison table or section outlining supported platforms and their respective setup guides.
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-10 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 centered around Windows environments. There is no mention of Linux-based hypervisors (such as KVM or VMware on Linux), nor are there any examples or recommendations for Linux administrators. Windows-specific concepts (e.g., VHD/VHDX, Hyper-V Replica Broker, drive letters like E:\) and tooling are used exclusively throughout the document.
Recommendations
  • Add equivalent guidance and examples for Linux-based virtualization platforms (e.g., KVM, VMware on Linux) where Azure Site Recovery supports them.
  • Explicitly state the scope of the documentation (e.g., 'This guide is for Hyper-V deployments; for Linux-based environments, see...').
  • Provide cross-platform comparison tables or links to Linux documentation for disaster recovery planning.
  • Avoid Windows-centric terminology (such as drive letters) when possible, or provide Linux equivalents.
  • Include references to Linux storage formats (e.g., QCOW2, raw) and Linux networking concepts where relevant.
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-10 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-based virtualization platform, and does not mention or provide guidance for equivalent scenarios on Linux platforms (e.g., KVM, VMware on Linux). All examples, terminology, and instructions are tailored to Windows environments, with no Linux parity or alternative tools/processes discussed.
Recommendations
  • Include guidance for excluding disks from replication for Linux-based hypervisors such as KVM or VMware running on Linux.
  • Add examples and screenshots for Linux environments where possible.
  • Reference Linux-native tools and workflows for disaster recovery and disk exclusion.
  • Clarify in the introduction that the procedure is specific to Hyper-V/Windows, and provide links to similar documentation for Linux platforms if available.
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-10 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 System Center VMM, with all examples and instructions tailored to Windows tools and workflows. Powershell commands are provided for installation steps, and there is no mention of Linux-based hypervisors, Linux command-line equivalents, or cross-platform considerations. The documentation assumes the reader is using Windows and does not offer guidance for Linux users or alternative virtualization platforms.
Recommendations
  • Add explicit statements clarifying that this guide is Windows/Hyper-V specific, and link to equivalent guides for Linux/KVM or VMware environments.
  • Include Linux-based disaster recovery scenarios or reference documentation for Linux hosts where possible.
  • Provide parity in examples, such as Bash or shell commands for agent installation on Linux, if supported.
  • Mention alternative tools and workflows for non-Windows environments, or clarify limitations if Azure Site Recovery does not support them.
  • Consider a cross-platform prerequisites section that helps users identify which guide is appropriate for their environment.
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-10 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, specifically Windows Server and PowerShell. All examples, prerequisites, and operational instructions are exclusively for Windows platforms. There is no mention of Linux support, Linux equivalents, or cross-platform usage. The tool itself appears to require Windows and Windows-specific components (e.g., .NET Framework, Visual C++ Redistributable, PowerShell remoting), and all operational steps (such as adding TrustedHosts) use PowerShell commands without alternatives for Linux or other platforms.
Recommendations
  • Clarify whether the tool is Windows-only or add explicit statements about platform support.
  • If possible, provide Linux equivalents or alternatives for prerequisites, installation, and operational steps.
  • Include examples for Linux environments (e.g., using SSH for remote profiling, Linux-based VM management).
  • Mention any limitations or lack of support for non-Windows platforms in the introduction and prerequisites.
  • If the tool cannot run on Linux, suggest alternative approaches for Linux users or link to relevant documentation.
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-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example Powershell Heavy
Summary
The documentation is heavily biased towards Windows environments. All examples use Windows-style paths (e.g., E:\Hyper-V_ProfiledData), reference Notepad for file editing, and assume the use of Hyper-V (a Windows-only hypervisor). The tool itself is a Windows executable (.exe), and there is no mention of Linux equivalents, cross-platform usage, or alternative tools for Linux environments. All operational instructions, file paths, and workflows are tailored to Windows conventions, with no guidance for Linux administrators.
Recommendations
  • Explicitly state OS requirements and limitations at the beginning of the documentation.
  • If the tool is Windows-only, provide guidance or links to equivalent Linux tools or workflows for similar Azure Site Recovery planning tasks.
  • Include examples of file editing and path usage for Linux environments (e.g., using nano or vi, and /home/user/ paths) if cross-platform support is possible.
  • Mention any prerequisites or compatibility notes for running the tool on non-Windows systems (e.g., via Wine, containers, or not supported).
  • If possible, develop and document a cross-platform version of the deployment planner tool.
  • Provide parity in documentation for VMware environments, which may be managed from Linux, and clarify any differences in workflow or tooling.
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-10 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, with all examples and instructions tailored to Windows tools and workflows. There are no Linux equivalents or guidance for Linux-based hypervisors, and connection instructions after failover only mention Windows VMs and RDP, with no mention of SSH or Linux firewall configuration.
Recommendations
  • Add guidance for disaster recovery scenarios involving Linux-based hypervisors (e.g., KVM, Xen) if supported by Azure Site Recovery.
  • Include examples for connecting to Linux VMs after failover, such as enabling SSH and configuring Linux firewalls (e.g., ufw, firewalld).
  • Mention Linux VM requirements and supported configurations alongside Windows requirements.
  • Provide troubleshooting steps for Linux VM connectivity after failover.
  • Clarify whether Azure Site Recovery supports non-Windows environments and, if not, explicitly state this limitation.
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-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits a Windows bias in several areas. The instructions for installing the monitoring agent on the Process Server exclusively reference Windows (e.g., 'Windows Servers', 'Download the Windows Agent'), and all screenshots and steps are Windows-centric. There is no mention of Linux-based Process Server setup, nor are Linux agent installation steps or screenshots provided. Additionally, the configuration of performance counters is described only for Windows, with no Linux equivalent or guidance. This creates a perception that only Windows environments are supported or prioritized, and Linux users are left without clear instructions.
Recommendations
  • Add explicit instructions and screenshots for installing and configuring the monitoring agent on Linux-based Process Servers, including download links and workspace setup.
  • Include Linux-specific steps for configuring performance counters, or clarify if and how Linux-based monitoring is supported for churn and upload rate logs.
  • Where agent installation is referenced, mention both Windows and Linux agents, and provide parity in documentation for both platforms.
  • Review all examples and UI references to ensure they are not Windows-exclusive, and add Linux equivalents where applicable.
  • Clearly state platform support and limitations at the start of the relevant sections, so Linux users understand what is and isn't 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-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example Powershell Heavy 🔧 Windows Tools
Summary
The documentation page exhibits a strong Windows bias. All prerequisites, installation steps, and examples are tailored exclusively to Windows Server environments, with no mention of Linux support or equivalents. Command-line and PowerShell instructions are Windows-specific, and tools like Control Panel, registry editing, and PowerShell cmdlets are used throughout without alternatives for Linux. There are no examples or guidance for deploying or managing the configuration server on Linux systems, nor any references to Linux-compatible tools or patterns.
Recommendations
  • Clarify whether Linux is supported for the configuration server. If not, explicitly state this limitation at the beginning of the documentation.
  • If Linux support exists or is planned, provide equivalent instructions for Linux environments, including installation, configuration, and management steps.
  • Include Linux shell (bash) command examples alongside PowerShell, where applicable.
  • Reference Linux tools (e.g., systemctl, cron, package managers) for relevant tasks such as service management and software installation.
  • Provide guidance on handling prerequisites and dependencies on Linux (e.g., disk setup, network configuration, MySQL installation).
  • Ensure parity in troubleshooting and common issues sections for Linux users.
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-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page describes disaster recovery for both Windows and Linux physical servers to Azure, but exhibits Windows bias in several ways. Windows is mentioned first throughout, and technical details (such as VSS and app-consistent snapshots) are explained only for Windows, with no Linux equivalent or guidance. There are no Linux-specific examples, tools, or patterns described, and the snapshot consistency section is entirely focused on Windows technologies (VSS), omitting how app-consistent snapshots are handled for Linux workloads.
Recommendations
  • Provide Linux-specific examples and instructions alongside Windows ones, especially for manual Mobility Service installation and configuration.
  • Explain how app-consistent snapshots are achieved for Linux servers, including any supported mechanisms (e.g., pre/post scripts, fsfreeze, etc.), or clarify limitations.
  • Mention Linux tools and patterns where relevant, such as differences in agent installation, snapshot consistency, and failover behavior.
  • Ensure parity in troubleshooting and operational guidance for both Windows and Linux, including error handling and recovery steps.
  • Explicitly state any differences in support or features between Windows and Linux, so administrators can plan accordingly.
GitHub Create Pull Request
Site Recovery Monitoring churn patterns on virtual machines ...b/main/articles/site-recovery/monitoring-high-churn.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation presents Windows monitoring tools (Resource Monitor, Performance Monitor) in greater detail, with step-by-step instructions and screenshots, while Linux tools (iotop, iostat) are only briefly mentioned without usage examples or visuals. Windows tools are described first and more comprehensively, indicating a bias towards Windows environments.
Recommendations
  • Provide step-by-step instructions for Linux tools (iotop, iostat), including example command outputs and screenshots where possible.
  • Mention additional Linux monitoring tools (such as 'dstat', 'glances', 'atop', or 'sar') to match the breadth of Windows coverage.
  • Structure the documentation so that Windows and Linux sections are presented with equal detail and in parallel, rather than Windows first.
  • Include troubleshooting tips and interpretation guidance for Linux tool outputs, similar to what is provided for Windows.
  • Ensure that links to further reading or official documentation are provided for both Windows and Linux tools.
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-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation claims to cover both Windows and Linux physical servers, but most specific examples and instructions are Windows-centric. Registry edits, account preparation, and troubleshooting steps are described in detail for Windows, with Linux mentioned only briefly and without equivalent step-by-step guidance or examples. Windows tools and patterns (e.g., registry edits, domain/local accounts) are explained, while Linux procedures are not. This creates a bias toward Windows users and leaves Linux administrators with less actionable information.
Recommendations
  • Provide detailed Linux-specific instructions for all steps where Windows procedures are given (e.g., account preparation, troubleshooting, service installation).
  • Include CLI examples for Linux (such as commands to check prerequisites, install the Mobility service, and verify connectivity).
  • Offer parity in troubleshooting steps, such as time synchronization (e.g., using ntpd or systemd-timesyncd on Linux) and permissions setup.
  • Add screenshots or walkthroughs from Linux environments where Windows screenshots are shown.
  • Explicitly mention Linux tools and patterns alongside Windows ones, rather than only referencing Windows registry or account types.
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-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits a Windows bias by referencing Windows-specific features and tools (such as resource groups, availability sets, and Windows Server versions) before or exclusively over Linux equivalents. There are no explicit Linux command-line or configuration examples, and the guidance for multi-VM consistency only briefly mentions Linux as an option, without providing parity in instructions or examples. Additionally, the documentation references Windows Server limitations and issues, but does not provide comparable details for Linux systems.
Recommendations
  • Include explicit Linux examples and instructions alongside Windows ones, such as configuration steps, troubleshooting, and failback scenarios.
  • Reference Linux-specific Azure VM settings (e.g., SSH access, Linux disk UUID management) where appropriate.
  • Provide parity in troubleshooting and limitations for Linux servers, not just Windows Server versions.
  • When discussing multi-VM consistency, offer detailed steps for both Windows and Linux replication groups.
  • Avoid referencing Windows tools and patterns (e.g., availability sets, resource groups) without also mentioning their relevance or equivalents for Linux workloads.
GitHub Create Pull Request
← Previous Page 8 of 35 Next →