Site Recovery

394
Total Pages
277
Linux-Friendly Pages
117
Pages with Bias
29.7%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

232 issues found
Showing 1-25 of 232 flagged pages
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-12 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 Windows environments, specifically Hyper-V, and the use of a Windows-only executable (ASRDeploymentPlanner.exe). All examples use Windows file paths and tools (e.g., Notepad), and there are no Linux or macOS equivalents or instructions. The documentation assumes the user is operating in a Windows environment, which creates friction for Linux/macOS users and makes the tool inaccessible to them.
Recommendations
  • Clarify in the introduction that the tool is Windows-only and provide guidance for users on non-Windows platforms.
  • If possible, provide a cross-platform version of the deployment planner tool or document alternative methods for Linux/macOS users.
  • Include explicit statements about OS requirements and limitations.
  • Offer suggestions for running the tool in a Windows VM or container for Linux/macOS users.
  • Add notes on how to access and manipulate output files using Linux/macOS tools (e.g., using cat, grep, nano, etc.), if partial interoperability is possible.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Missing Linux Example Windows First
Summary
The documentation is heavily focused on Windows environments, specifically Hyper-V managed by System Center VMM. All examples and instructions reference Windows tools (VMM, Hyper-V, Recovery Services Agent), and PowerShell is used for command-line steps. There are no Linux or macOS equivalents or alternative instructions, and Windows-specific terminology and screenshots are used throughout. Linux users are unable to follow the tutorial, as no cross-platform options or parity are provided.
Recommendations
  • Clarify in the prerequisites and introduction that the tutorial is Windows/Hyper-V specific, and provide links to Linux/KVM or VMware disaster recovery guides if available.
  • Where possible, mention whether Azure Site Recovery supports Linux-based hypervisors or provide guidance for Linux VM replication.
  • If any steps (such as agent installation or Azure configuration) have Linux equivalents, add those instructions and examples.
  • Add a comparison table or section outlining differences and supported platforms for disaster recovery with Azure Site Recovery.
  • Ensure that alternative documentation exists for Linux users and is cross-linked from this page.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows Only Missing Linux Example 🔧 Windows Tools Windows First
Summary
The documentation exclusively specifies Windows Server as the required operating system for the replication appliance, with no mention of Linux or macOS support. All folder paths and antivirus exclusions reference Windows directories. Windows-specific roles, group policies, and IIS settings are discussed, with no Linux equivalents or alternatives provided. This creates a strong Windows bias, making the guide inapplicable for Linux users.
Recommendations
  • Clarify whether Linux-based appliances are supported or not. If not, explicitly state that only Windows Server is supported.
  • If Linux support is possible, provide equivalent requirements, examples, and folder paths for Linux systems.
  • Add guidance for Linux-based antivirus exclusions if Linux appliances are supported.
  • Include a section comparing Windows and Linux deployment options, or provide rationale for Windows-only support.
  • If Windows-only is a technical limitation, make this clear early in the documentation to set user expectations.
GitHub Create Pull Request
Site Recovery Transport Layer Security in Azure Site Recovery ...ain/articles/site-recovery/transport-layer-security.md
High Priority View Details →
Scanned: 2026-01-12 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 Windows-centric, focusing exclusively on Windows operating systems, registry modifications, and .NET Framework configuration. There are no instructions, examples, or references for enabling or verifying TLS 1.2 on Linux or macOS systems. All troubleshooting and configuration guidance is tailored to Windows environments, with no mention of equivalent steps or considerations for non-Windows platforms.
Recommendations
  • Add a section describing how to verify and enable TLS 1.2 on Linux and macOS, including relevant configuration files (e.g., OpenSSL, system-wide TLS settings).
  • Provide command-line examples for Linux (e.g., using openssl, curl, or systemctl to check TLS support).
  • Include troubleshooting steps for common Linux distributions (Ubuntu, CentOS, etc.) regarding TLS 1.2 compatibility.
  • Reference Linux/macOS documentation and best practices for TLS configuration.
  • Clarify whether Azure Site Recovery supports non-Windows agents, and if so, provide parity in documentation.
GitHub Create Pull Request
Site Recovery Remove servers and disable protection ...ry/site-recovery-manage-registration-and-protection.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation is heavily focused on Windows environments, specifically System Center VMM and Hyper-V, with all scripts and command-line instructions provided exclusively in PowerShell. There are no examples or guidance for Linux or macOS users, nor are alternative tools or commands mentioned for non-Windows platforms. Windows-specific tools and registry paths are referenced throughout, and Windows procedures are described first and in detail, while Linux scenarios are absent.
Recommendations
  • Add equivalent instructions and scripts for Linux-based environments, especially for VMware and physical servers that may run Linux.
  • Provide bash or shell script examples where applicable, or clarify if certain steps are not relevant for Linux/macOS.
  • Explicitly state platform limitations and offer guidance for Linux/macOS users on how to achieve similar outcomes.
  • Include references to cross-platform tools or APIs (e.g., Azure CLI, REST API) that can be used from any OS.
  • Reorder sections or add parity so Linux/Unix scenarios are described alongside Windows ones, not only after.
GitHub Create Pull Request
Site Recovery Deploy the configuration server in Azure Site Recovery ...e-recovery/vmware-azure-deploy-configuration-server.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation exhibits a notable Windows bias. The configuration server is deployed as a Windows Server 2016 VM, with all setup, registration, and management steps referencing Windows-specific tools, paths (e.g., C:\Temp\ASRSetup), and user experiences. Linux is only mentioned briefly in the context of providing root credentials for VM replication, but there are no Linux-based deployment examples, instructions, or parity for configuration server setup. All examples and screenshots are Windows-centric, and there is no guidance for Linux or macOS users who may wish to interact with or manage the configuration server.
Recommendations
  • Provide explicit guidance or examples for Linux/macOS users where applicable, such as alternative ways to interact with the configuration server or manage files.
  • Clarify whether the configuration server must be Windows-based, and if so, offer workarounds or integration points for Linux environments (e.g., remote management, SSH, etc.).
  • Include Linux-specific instructions for tasks like downloading MySQL, managing credentials, or interacting with the configuration server, especially for environments where administrators may not have access to Windows.
  • If possible, offer a Linux-based configuration server template or document why this is not supported.
GitHub Create Pull Request
Site Recovery Troubleshoot VMware vCenter discovery failures in Azure Site Recovery ...tps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/vmware-azure-troubleshoot-vcenter-discovery-failures.md
High Priority View Details →
Scanned: 2026-01-12 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 page demonstrates Windows bias by exclusively referencing Windows tools (PsExec, Internet Explorer, Windows command prompt), providing only Windows-based procedures for proxy configuration, and omitting Linux/macOS equivalents. All troubleshooting steps assume a Windows environment, leaving Linux users without guidance for performing similar tasks.
Recommendations
  • Provide Linux/macOS equivalents for proxy configuration, such as using environment variables or network settings.
  • Suggest alternative tools for accessing system user context on Linux (e.g., sudo, su, or running browsers as root if needed).
  • Include instructions for modifying proxy settings on Linux systems (e.g., using GNOME/KDE network settings, or editing /etc/environment).
  • Offer DRA service management commands for Linux (e.g., systemctl or service commands).
  • Clarify platform requirements and explicitly state if steps are Windows-only, or provide parity for other OSes.
GitHub Create Pull Request
Site Recovery Manage VMware vCenter servers in Azure Site Recovery .../articles/site-recovery/vmware-azure-manage-vcenter.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation assumes the use of Windows for the configuration server, referencing a Windows-specific tool (_cspsconfigtool.exe_) and desktop shortcuts. There are no instructions or examples for Linux-based configuration servers, nor any mention of Linux equivalents or command-line alternatives. All steps for account management and server modification are described using Windows-centric UI and tools, with no Linux parity.
Recommendations
  • Clarify whether the configuration server can run on Linux, and if so, provide equivalent instructions for Linux environments.
  • If _cspsconfigtool.exe_ is Windows-only, mention this limitation explicitly and suggest alternatives for Linux users, such as command-line or web-based management.
  • Include Linux-specific examples or note if certain features are unavailable on Linux.
  • Present platform-agnostic instructions where possible, or clearly separate Windows and Linux steps.
GitHub Create Pull Request
Site Recovery Set up Azure Site Recovery for Azure VMware Solution VMs ...ain/articles/site-recovery/avs-tutorial-replication.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by exclusively describing the configuration server VM as running Windows Server 2016, requiring Windows activation, and guiding users through Windows-specific installation and setup steps. There are no Linux-based configuration server options or examples, and Windows credentials and patterns are described first and in detail, with only brief mention of Linux credentials for Mobility Service installation.
Recommendations
  • Clarify whether the configuration server can run on Linux, and if so, provide Linux-based setup instructions and examples.
  • If Windows is required, explicitly state this early in the prerequisites and explain why Linux is not supported.
  • Provide parity in credential setup instructions, including step-by-step guidance for Linux VMs (e.g., root account setup, SSH key usage).
  • Include troubleshooting and monitoring examples for Linux VMs, not just Windows.
  • List Linux requirements and considerations alongside Windows ones, not only as a secondary note.
GitHub Create Pull Request
Site Recovery Replicate Azure virtual machines running Storage Spaces Direct with Azure Site Recovery ...ry/azure-to-azure-how-to-enable-replication-s2d-vms.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation is heavily focused on Windows-specific technologies, particularly Storage Spaces Direct (S2D) and Windows Failover Clustering. All examples, terminology, and referenced tools are Windows-centric, with no mention of Linux equivalents or guidance for Linux-based clusters. There are no Linux-specific instructions, examples, or parity notes, making the content inaccessible for users managing Linux VMs or clusters.
Recommendations
  • Add explicit statements clarifying that the instructions are only applicable to Windows-based clusters, and provide links to Linux disaster recovery documentation if available.
  • Include guidance or references for setting up disaster recovery for Linux-based clusters or VMs using Azure Site Recovery.
  • Offer examples or notes on how similar scenarios would be handled for Linux VMs, including any differences in failover, recovery plans, and automation scripts.
  • If Linux support is not available for S2D, state this clearly at the beginning of the documentation.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First Powershell Heavy
Summary
The documentation page demonstrates a notable Windows bias. It focuses almost exclusively on Windows-centric technologies such as DFSR (Distributed File System Replication), Active Directory, and Azure File Sync, all of which are Windows Server features. Step-by-step instructions and architectural recommendations are tailored for Windows environments, with explicit references to Windows Server, DFSR, and SMB. There are no examples, instructions, or guidance for Linux or macOS file servers, nor are Linux-native replication tools (e.g., rsync, NFS, GlusterFS) mentioned. Even when Azure Files is described as cross-platform, all operational steps and sync group configurations are Windows-specific, and mounting instructions link to Windows guides. The documentation assumes Active Directory is present and required, further excluding Linux environments that may use LDAP or other directory services.
Recommendations
  • Add explicit guidance and examples for protecting Linux-based file servers, including supported replication and failover strategies.
  • Mention Linux-native file server technologies (e.g., Samba, NFS, rsync, GlusterFS) and how they can be integrated with Azure Site Recovery or Azure Files.
  • Provide instructions for mounting Azure Files on Linux and macOS clients, including links to relevant documentation.
  • Clarify which features (e.g., DFSR, Active Directory) are Windows-only and offer Linux/macOS alternatives or workarounds.
  • Include parity in step-by-step guides for Linux file servers, such as preparing Linux VMs, configuring replication, and performing failover.
  • Reference Azure Files documentation for Linux and macOS, not just Windows.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation is heavily focused on Windows environments, specifically Hyper-V running on Windows Server. All examples, prerequisites, and tooling references are Windows-centric, with repeated mentions of Windows Server, Hyper-V, System Center VMM, and PowerShell. There are no Linux or macOS equivalents, examples, or guidance, and the documentation assumes the reader is operating in a Windows ecosystem.
Recommendations
  • Explicitly state that Azure Site Recovery for Hyper-V is a Windows-only solution and clarify Linux/macOS limitations.
  • Provide links or references to disaster recovery solutions for Linux-based virtualization platforms (e.g., KVM, VMware on Linux).
  • Add a comparison section outlining how Linux users can achieve similar disaster recovery with Azure, or direct them to relevant Azure documentation.
  • If possible, include SDK/API examples using cross-platform tools (e.g., Azure CLI, REST API) alongside PowerShell.
  • Mention alternative Azure Site Recovery scenarios for physical Linux servers, if supported.
GitHub Create Pull Request
Site Recovery Hyper-V disaster recovery architecture in Azure Site Recovery ...n/articles/site-recovery/hyper-v-azure-architecture.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation is focused exclusively on Hyper-V, a Windows-only virtualization platform, and references Windows-specific tools, APIs, and workflows throughout. All examples and architectural descriptions assume a Windows environment, with no mention of Linux or macOS alternatives, nor any guidance for users operating outside Windows. The documentation also references Windows APIs (e.g., CreateReplicationRelationship, StartReplication) and file formats (.hrl) specific to Hyper-V, and all screenshots and instructions are tailored to Windows tools and the Azure portal.
Recommendations
  • Explicitly state that the guidance is only applicable to Windows/Hyper-V environments and provide links to equivalent disaster recovery documentation for Linux-based virtualization platforms (e.g., KVM, VMware on Linux).
  • If Azure Site Recovery supports Linux-based hypervisors or VMs, include sections or links describing the architecture and setup for those platforms.
  • Add a comparison table or FAQ clarifying support and differences for Linux/macOS users.
  • Ensure that any referenced APIs, tools, or file formats are explained in terms of their platform specificity, and suggest alternatives or workarounds for non-Windows environments if possible.
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-12 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 Windows environments, specifically Hyper-V and System Center VMM, with all examples and instructions assuming Windows hosts. There is no mention of Linux or macOS equivalents, nor guidance for users running non-Windows platforms. Windows tools and installation steps (e.g., Hyper-V role, VMM) are referenced exclusively, and no Linux failback scenarios or commands are provided.
Recommendations
  • Clarify in the introduction that the guide is specific to Windows Hyper-V environments and Azure Site Recovery's current limitations.
  • If Azure Site Recovery supports Linux-based hypervisors or VM failback, add equivalent Linux instructions and examples.
  • Provide links or references to documentation for Linux failback scenarios, if available.
  • Explicitly state platform requirements and alternatives for non-Windows users.
  • Consider adding a comparison table of supported platforms and failback scenarios.
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-12 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 Hyper-V, a Windows-only virtualization platform. All examples, terminology, and referenced tools are specific to Windows environments. There are no Linux or cross-platform alternatives mentioned, nor are Linux-specific instructions or considerations provided. Even in sections about connecting to failed-over VMs, the documentation references Windows-centric guides and tools first (RDP, Windows VM connection documentation), with only a brief mention of SSH.
Recommendations
  • Explicitly state that the tutorial is intended for Windows/Hyper-V environments and clarify Linux support limitations.
  • Provide links or references to equivalent disaster recovery solutions for Linux-based virtualization platforms (e.g., KVM, VMware on Linux).
  • Include examples or notes for connecting to Linux VMs after failover, such as SSH instructions, and reference Linux VM documentation.
  • Add a section discussing Azure Site Recovery support for non-Windows workloads, if applicable, or direct users to relevant resources.
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-12 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 Windows environments, specifically Hyper-V running on Windows Server and System Center Virtual Machine Manager. All examples, requirements, and supported scenarios are Windows-centric, with no mention of Linux-based Hypervisors, Linux management tools, or cross-platform alternatives. Where Linux is referenced, it is only as a guest OS within Windows Hyper-V VMs, not as a host or management platform. PowerShell is mentioned as a deployment method, with no equivalent Bash or CLI examples. The documentation assumes the reader is operating in a Windows ecosystem.
Recommendations
  • Explicitly state that Azure Site Recovery for Hyper-V is only supported on Windows platforms, if that is the case. If Linux-based Hyper-V hosts or management tools are not supported, clarify this early in the documentation.
  • If any cross-platform management options exist (e.g., Azure CLI, REST API), provide equivalent examples and instructions for Linux/macOS users.
  • Where PowerShell is referenced, add Azure CLI/Bash examples or note their absence.
  • Add a section addressing Linux/macOS admins, clarifying what is and is not supported, and providing guidance for alternative disaster recovery solutions if applicable.
  • Ensure that references to guest OS support for Linux are clear and provide links to relevant Linux documentation.
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-12 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 Hyper-V, a Windows-only virtualization platform, and references Windows-specific concepts, tools, and file formats (e.g., VHD/VHDX, Hyper-V Replica Broker, Windows-style paths like E:\VHDpath). There are no examples, guidance, or references for equivalent Linux or cross-platform scenarios, nor any mention of how Linux users or KVM/VMware environments might use or interpret the report. All operational details, recommendations, and troubleshooting are described exclusively in terms of Windows/Hyper-V infrastructure.
Recommendations
  • Add a section clarifying platform support and limitations, explicitly stating that the Deployment Planner and its reports are designed for Hyper-V (Windows) environments.
  • If the tool or process can be adapted for Linux-based hypervisors (e.g., KVM, VMware), provide equivalent examples, terminology, and operational guidance.
  • Include notes or links for users of non-Windows platforms about alternative Azure Site Recovery planning tools or methods.
  • Where possible, use platform-neutral language for concepts like storage, networking, and VM compatibility.
  • If the Excel report can be generated or analyzed on Linux/macOS (e.g., via Office Online or LibreOffice), mention this and provide instructions.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Powershell Heavy
Summary
The documentation is heavily focused on Windows environments, specifically Hyper-V hosts running on Windows Server. All setup, installation, and command-line instructions reference Windows executables, Windows file paths, and Windows-specific tools (e.g., AzureSiteRecoveryProvider.exe, DRConfigurator.exe, MARS agent). There are no examples, instructions, or notes for Linux or macOS users, nor any mention of cross-platform alternatives. The documentation assumes the administrator is working in a Windows ecosystem.
Recommendations
  • Clarify that Hyper-V is a Windows-only technology, but explicitly state platform requirements early in the documentation.
  • If any components (such as the MARS agent or Azure Site Recovery provider) have Linux/macOS versions or equivalents, provide instructions or links for those platforms.
  • Add a section addressing cross-platform scenarios, such as disaster recovery for Linux-based hypervisors (e.g., KVM, Xen) or VMs.
  • Include a note for users on non-Windows platforms about alternative Azure Site Recovery workflows or supported configurations.
  • If PowerShell is required, mention if PowerShell Core (cross-platform) is supported, and provide relevant examples.
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-12 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 for the Azure Site Recovery Deployment Planner for Hyper-V disaster recovery is heavily biased towards Windows environments. All examples, prerequisites, and operational instructions are Windows-specific, requiring Windows Server, PowerShell, and Windows-only tools (e.g., .NET Framework, Visual C++ Redistributable, Microsoft Excel). There is no mention of Linux or macOS support, nor are alternative instructions or examples provided for non-Windows platforms.
Recommendations
  • Clarify whether the tool can run on Linux or macOS, and if not, explicitly state Windows-only support in the introduction.
  • If possible, develop and document a cross-platform version of the tool, or provide alternative Linux/macOS-compatible utilities for similar planning tasks.
  • Include example workflows or guidance for VMware users running on Linux hosts, if relevant.
  • Offer guidance on how non-Windows users can access or interpret the output (e.g., using open-source spreadsheet tools instead of Excel).
  • List any limitations for non-Windows environments prominently in the prerequisites section.
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-12 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 reference Windows tools (e.g., Windows Firewall, RDP, SAN policy), and there are no Linux or macOS equivalents or guidance. The steps for preparing VMs for failover only mention Windows-specific configuration and troubleshooting, with no mention of Linux VM preparation or access methods.
Recommendations
  • Add explicit guidance for Linux-based VMs, including how to prepare them for failover and access them post-failover (e.g., SSH setup, Linux firewall configuration).
  • Include examples for connecting to Linux VMs after failover, such as enabling SSH and configuring relevant ports.
  • Clarify whether Azure Site Recovery supports Linux VMs in Hyper-V environments, and if so, provide parity in documentation for their setup and recovery.
  • Where troubleshooting steps are provided for Windows VMs, add analogous steps for Linux VMs (e.g., checking boot diagnostics, resolving SSH connectivity issues).
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-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation is heavily focused on Hyper-V and System Center Virtual Machine Manager (VMM), which are Windows-only technologies. There are no references to Linux-based hypervisors, tools, or examples. All scenarios, terminology, and workflows assume a Windows environment, leaving Linux/macOS users without guidance or parity.
Recommendations
  • Add equivalent guidance for Linux-based hypervisors (e.g., KVM, VMware on Linux) and their integration with Azure Site Recovery.
  • Include examples and mapping scenarios for Linux environments, such as using Azure Site Recovery with Linux VMs or open-source virtualization platforms.
  • Clearly state the Windows-only scope at the beginning, or provide links to Linux/macOS documentation if available.
  • If Azure Site Recovery supports Linux VMs or other platforms, document the network mapping process for those use cases.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows Only Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation is heavily biased towards Windows environments. All prerequisites, installation steps, command-line instructions, and troubleshooting are exclusively for Windows Server (2012 R2/2016). All examples use Windows tools (Control Panel, Registry Editor, PowerShell), and there are no instructions or examples for Linux or macOS users. The use of PowerShell and Windows-specific utilities is pervasive, and Linux equivalents are not mentioned.
Recommendations
  • Clearly state that only Windows is supported, or add Linux/macOS support if possible.
  • If Linux/macOS can be used as configuration servers, provide equivalent prerequisites, installation steps, and command-line examples for those platforms.
  • For command-line operations, offer Bash or shell script alternatives where applicable.
  • Mention any limitations or workarounds for non-Windows users.
  • If the product is Windows-only, make this explicit in the introduction and prerequisites.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation exclusively references Windows workloads, Windows Server Failover Clustering (WSFC), and Windows Server SKUs. There are no mentions of Linux workloads, Linux clustering solutions (such as Pacemaker or Corosync), or Linux-specific support. All examples and supported scenarios are Windows-centric, with no guidance for Linux users.
Recommendations
  • Explicitly state whether Linux workloads and clustering solutions are supported or not.
  • If Linux is unsupported, clarify this early in the document and provide links to alternative disaster recovery solutions for Linux.
  • If Linux support exists or is planned, add equivalent tables and examples for Linux, including supported distributions, clustering solutions (e.g., Pacemaker, Corosync), and disk partitioning types.
  • Include parity in terminology and guidance for both Windows and Linux users.
  • Consider adding a section on future roadmap or workarounds for Linux users.
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-12 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, with exclusive references to Windows Server, Windows-specific tools (e.g., ntdsutil.exe, dcdiag, nltest, dnscmd), and registry edits. All command-line examples and troubleshooting steps use Windows commands, and there are no Linux/macOS equivalents or guidance for non-Windows domain controllers or DNS servers. The documentation assumes Active Directory and DNS are running on Windows, and does not address scenarios where Linux-based Samba AD DC or BIND DNS might be used.
Recommendations
  • Add explicit guidance for environments using Samba as an Active Directory Domain Controller on Linux, including replication and failover steps.
  • Provide equivalent examples for DNS management using BIND or other Linux DNS servers, including zone creation and updates.
  • Include Linux/macOS command-line equivalents for diagnostic and troubleshooting steps (e.g., using samba-tool, systemctl, dig, nsupdate, etc.).
  • Clarify which steps are Windows-specific and offer alternative instructions for Linux-based domain controllers and DNS servers.
  • Consider reordering examples so that platform-neutral or Linux examples are presented alongside or before Windows examples.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First Powershell Heavy
Summary
The documentation for Azure Site Recovery Deployment Planner for VMware disaster recovery is heavily Windows-centric. All instructions, prerequisites, and examples assume the use of Windows Server or Windows PC, with no mention of Linux or macOS alternatives. Required dependencies (.NET Framework, Visual C++ Redistributable, Excel) are Windows-only, and the tool itself appears to be a Windows executable. There are no Linux/macOS usage instructions, nor are cross-platform equivalents or workarounds discussed.
Recommendations
  • Clarify explicitly that the tool is Windows-only, and note the lack of Linux/macOS support.
  • If possible, provide a cross-platform version of the tool or document alternative approaches for Linux/macOS users.
  • Offer guidance on running the tool in a Windows VM or container for users on non-Windows platforms.
  • List platform requirements at the top of the documentation to set expectations early.
  • Include a FAQ or troubleshooting section for non-Windows users.
GitHub Create Pull Request
← Previous Page 1 of 10 Next →