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 1-25 of 864 flagged pages
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-17 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation for the 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 support or alternatives. The tool itself appears to require Windows, and report generation requires Excel on Windows. There are no Linux/macOS usage instructions, examples, or parity tools provided.
Recommendations
  • Clearly state in the prerequisites and introduction whether the Deployment Planner tool is Windows-only, and if so, explain the rationale.
  • If possible, provide a Linux-compatible version of the Deployment Planner tool, or document any workarounds for Linux/macOS users (e.g., running the tool in a Windows VM or via Wine).
  • Offer alternative report generation instructions for users who do not have access to Excel on Windows (e.g., using LibreOffice, or exporting to CSV).
  • Add a note about platform limitations early in the documentation to set expectations for non-Windows users.
GitHub Create Pull Request
Site Recovery Run the deployment Planner for VMware disaster recovery with Azure Site Recovery ...ecovery/site-recovery-vmware-deployment-planner-run.md
High Priority View Details →
Scanned: 2026-01-17 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 for running the Deployment Planner for VMware disaster recovery with Azure Site Recovery demonstrates a notable Windows bias. All examples for gathering VM lists use VMware vSphere PowerCLI (PowerShell), and instructions reference Windows-specific tools (ASRDeploymentPlanner.exe, Notepad, UNC paths). The report output requires Microsoft Excel on Windows, and there is no mention of Linux/macOS alternatives or guidance for running the tool or processing results on non-Windows platforms.
Recommendations
  • Provide equivalent Linux/macOS instructions for gathering VM lists (e.g., using VMware CLI tools, Python scripts, or bash commands).
  • Clarify whether ASRDeploymentPlanner.exe can be run under Wine or Mono on Linux/macOS, or explicitly state Windows-only requirements.
  • Suggest cross-platform alternatives for viewing and processing the report output (e.g., LibreOffice for Excel files, or provide CSV output options).
  • Add a section explicitly outlining platform requirements and limitations, so non-Windows users can plan accordingly.
  • If the tool is strictly Windows-only, recommend remote access or VM solutions for Linux/macOS users.
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-14 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 oriented toward Windows file server environments, referencing Windows-specific technologies such as DFSR, Active Directory, and Azure File Sync (which only supports Windows Server endpoints). Examples and step-by-step instructions are exclusively for Windows-based servers, with no guidance for Linux file servers. While Azure Files supports SMB access from Linux/macOS, the disaster recovery workflows and replication strategies described are Windows-centric, and Linux users are left without actionable steps.
Recommendations
  • Add a dedicated section for disaster recovery of Linux-based file servers, outlining supported Azure Site Recovery scenarios and alternatives.
  • Clarify which features (e.g., DFSR, Azure File Sync) are Windows-only and suggest Linux equivalents or workarounds (such as rsync, NFS, or third-party tools).
  • Provide example workflows for Linux file servers, including how to replicate, failover, and recover using Azure-native or cross-platform tools.
  • When mentioning mounting Azure Files, include Linux/macOS instructions (e.g., using SMB or NFS clients) alongside Windows examples.
  • Explicitly state limitations for non-Windows environments and link to relevant cross-platform documentation.
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-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation for the Azure Site Recovery Deployment Planner for VMware disaster recovery demonstrates a notable Windows bias. All instructions, prerequisites, and examples assume the use of Windows Server or Windows PC environments. The tool itself appears to be Windows-only, with requirements for Windows Server, .NET Framework, and Visual C++ Redistributable. There are no Linux or macOS examples, nor any mention of running the tool or generating reports on non-Windows platforms. Windows tools and patterns are referenced exclusively and before any alternatives (which are not provided).
Recommendations
  • Clearly state in the prerequisites and introduction that the Deployment Planner tool is Windows-only, if that is the case.
  • If the tool can be run on Linux (e.g., via Mono or Wine), provide instructions or examples for Linux users.
  • If a Linux or cross-platform version is planned, mention it and provide an expected timeline.
  • Offer guidance for Linux/macOS users on how to access the required functionality (e.g., running the tool in a Windows VM or container).
  • Consider providing alternative tools or scripts for Linux environments if possible.
GitHub Create Pull Request
Site Recovery Run the Deployment Planner for VMware disaster recovery with Azure Site Recovery ...ecovery/site-recovery-vmware-deployment-planner-run.md
High Priority View Details →
Scanned: 2026-01-14 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 running the Deployment Planner for VMware disaster recovery with Azure Site Recovery demonstrates a notable Windows bias. All examples and instructions assume the use of Windows tools (ASRDeploymentPlanner.exe), Windows file paths, and PowerShell/PowerCLI for VM discovery. There is no mention of Linux or macOS equivalents, nor guidance for running the tool or generating reports from non-Windows environments. The report output requires Microsoft Excel (Windows-only), and the instructions for file manipulation reference Notepad and UNC paths, further reinforcing the Windows-centric approach.
Recommendations
  • Clarify in the introduction that the Deployment Planner tool and report generation are Windows-only, if this is an intentional product limitation.
  • If the tool can run on Linux (e.g., via Mono or Wine), provide instructions and tested examples for Linux/macOS users.
  • Offer alternative methods for VM discovery (e.g., using VMware CLI tools available on Linux) and file manipulation (e.g., using cat, grep, or text editors on Linux/macOS).
  • Explicitly state the OS requirements and limitations for both the tool and report analysis.
  • If possible, provide a cross-platform version of the Deployment Planner tool or a web-based report viewer.
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-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation is notably Windows-focused: the configuration server is deployed as a Windows Server 2016 VM, and all setup, registration, and management instructions assume a Windows environment. Steps such as MySQL installation reference Windows file paths (C:\Temp\ASRSetup) and do not provide Linux alternatives. There are no Linux/macOS examples or instructions, and the configuration server itself appears to require Windows, creating friction for Linux-centric administrators.
Recommendations
  • Explicitly state that the configuration server must run Windows Server, and clarify that Linux/macOS deployment is not supported if that is the case.
  • If possible, provide guidance for Linux administrators (e.g., remote management from Linux, or clarify which steps can be performed from non-Windows systems).
  • Where possible, offer cross-platform alternatives for tasks such as MySQL installation, or clarify that only Windows is supported.
  • Add a note early in the documentation indicating the Windows-only nature of the configuration server deployment to set expectations for non-Windows users.
GitHub Create Pull Request
Site Recovery Manage the configuration server for disaster recovery with Azure Site Recovery ...e-recovery/vmware-azure-manage-configuration-server.md
High Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation for managing the configuration server with Azure Site Recovery is notably Windows-centric. Most operational instructions, command-line examples, and tooling references (PowerShell, .exe utilities, Windows file paths) assume the configuration server is running on Windows. PowerShell is used for several critical tasks, and Windows tools (CSPSConfigtool.exe, genpassphrase.exe, UnifiedSetup.exe) are referenced exclusively. Linux equivalents, if any, are not mentioned, and Linux users may struggle to follow or adapt these instructions.
Recommendations
  • Explicitly state in the introduction that the configuration server appliance is Windows-based, if that is a product constraint.
  • If Linux-based configuration servers are supported, provide equivalent Linux instructions and tooling references (e.g., bash commands, Linux paths, alternative utilities).
  • Clarify which steps are Windows-only and which are applicable to Linux deployments.
  • Where PowerShell is used, offer Bash or shell script alternatives if possible.
  • Add notes or links for Linux users about supported scenarios and limitations.
GitHub Create Pull Request
Site Recovery Set up a scale-out process server during disaster recovery of VMware VMs and physical servers with Azure Site Recovery | Microsoft Docs ...e-recovery/vmware-azure-set-up-process-server-scale.md
High Priority View Details →
Scanned: 2026-01-14 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 exclusively describes installation and usage of the Azure Site Recovery Process Server using Windows-centric tools and patterns. All command-line examples use Windows executables and Windows file paths, with no mention of Linux equivalents or support. The installation steps, parameters, and examples assume a Windows environment, and there is no guidance for deploying or managing process servers on Linux or macOS.
Recommendations
  • Clarify whether the Process Server component is Windows-only. If Linux is supported, provide equivalent installation and usage instructions for Linux environments.
  • Include Linux-specific command-line examples, such as shell commands and Linux file paths.
  • Explicitly state OS requirements and limitations at the beginning of the article.
  • If Linux is not supported, add a note to inform users that only Windows is supported for Process Server deployment.
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-13 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 installation instructions use Windows tools and PowerShell commands. There are no Linux or macOS equivalents, nor any mention of how to perform similar tasks on non-Windows platforms. The tutorial assumes the user is working with Windows servers and Windows-only software.
Recommendations
  • Clarify early in the documentation that the tutorial is only applicable to Windows/Hyper-V environments, and provide links to Linux/KVM or VMware disaster recovery guides if available.
  • Add a comparison table or section outlining disaster recovery options for Linux-based hypervisors (e.g., KVM, Xen) and how to use Azure Site Recovery or alternative solutions.
  • Where possible, include notes or links for Linux users, such as how to set up disaster recovery for Linux VMs or Linux-based virtualization platforms.
  • If Azure Site Recovery supports Linux hosts or VMs, provide parallel instructions or reference documentation for those scenarios.
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-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
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 use Windows conventions, and all referenced system roles, group policies, and IIS settings are Windows-specific. There are no examples or requirements for Linux-based appliances, nor any guidance for Linux administrators.
Recommendations
  • Clarify whether Linux-based replication appliances are supported. If not, explicitly state Windows-only support to set expectations.
  • If Linux support is possible, provide equivalent requirements, folder paths, and antivirus exclusions for Linux systems.
  • Include Linux-specific instructions or examples where relevant, such as service configuration, firewall rules, and folder exclusions.
  • Consider providing a comparison table for Windows and Linux requirements if both are supported.
  • Mention any alternative approaches for Linux users if the appliance must run on Windows.
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-13 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-only virtualization platform. All instructions, terminology, and examples are tailored to Windows environments, with no mention of Linux or cross-platform alternatives. There are no Linux/macOS examples, nor are equivalent Linux tools or workflows discussed.
Recommendations
  • Clarify early in the documentation that the procedure is specific to Hyper-V (Windows-only), and provide links or references to equivalent disaster recovery procedures for Linux-based virtualization platforms (e.g., KVM, VMware on Linux).
  • If Azure Site Recovery supports Linux VMs or other hypervisors, add sections or links for excluding disks from replication in those environments.
  • Include a comparison table or FAQ addressing cross-platform support and limitations.
  • Explicitly state platform requirements and limitations in the 'Before you start' section.
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-13 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 is heavily biased towards Windows environments, specifically Hyper-V on Windows Server. All examples use Windows-style paths, Windows tools (ASRDeploymentPlanner.exe), and reference Windows conventions (UNC paths, Notepad). There are no Linux/macOS equivalents, nor any mention of running the tool or accessing data from non-Windows platforms. The documentation assumes the user is operating in a Windows ecosystem and does not address cross-platform scenarios.
Recommendations
  • Clarify platform requirements for ASRDeploymentPlanner.exe (e.g., is it Windows-only?)
  • If Linux/macOS support is possible, provide instructions and examples for those platforms (e.g., using Wine, or alternative tools/scripts)
  • Mention alternative text editors (e.g., nano, vim) instead of only Notepad
  • Use platform-neutral file path examples where possible
  • Explicitly state any limitations or requirements for non-Windows users at the beginning of the documentation
  • If the tool is Windows-only, suggest alternative planning approaches for Linux environments
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-13 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 is heavily biased towards Windows environments. All examples, prerequisites, and instructions are Windows-specific, with exclusive reliance on Windows Server, PowerShell commands, and Windows-only tools (such as .NET Framework and Visual C++ Redistributable). There is no mention of Linux or macOS support, nor are alternative instructions or examples provided for non-Windows platforms. The tool itself appears to require Windows, and even report generation requires Microsoft Excel on Windows.
Recommendations
  • Clarify explicitly if the tool is Windows-only, and mention lack of Linux/macOS support in the prerequisites.
  • If possible, provide a cross-platform version of the tool or document alternatives for Linux/macOS users.
  • Include a section addressing Linux/macOS users, with guidance on how to approach Hyper-V disaster recovery planning from those platforms.
  • Offer example commands or workflows for Linux environments if any part of the process can be performed from Linux.
  • Consider providing web-based or platform-agnostic reporting options instead of requiring Microsoft Excel.
GitHub Create Pull Request
Site Recovery Set up disaster recovery for an IIS web app using Azure Site Recovery .../blob/main/articles/site-recovery/site-recovery-iis.md
High Priority View Details →
Scanned: 2026-01-13 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 IIS on Windows Server, with all examples, scripts, and recovery scenarios tailored to Windows. There are no Linux or cross-platform equivalents mentioned, and all automation scripts referenced are for Windows tools (PowerShell, IIS, ARR). Linux-based web applications (e.g., Apache, Nginx) and their disaster recovery patterns are not addressed.
Recommendations
  • Add equivalent disaster recovery guidance for Linux-based web applications (e.g., Apache, Nginx) running on Azure.
  • Include Linux-specific examples for scripting post-failover actions (e.g., using Bash, Python, or Ansible).
  • Mention Linux-compatible tools and patterns for web farm deployment and recovery.
  • Provide parity in documentation structure, ensuring Linux scenarios are described alongside Windows ones.
  • Reference cross-platform automation options (e.g., Azure CLI, REST API) where possible.
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-13 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 biased towards Windows environments, specifically System Center VMM, Hyper-V, and PowerShell. All provided scripts and automation steps are Windows/PowerShell-based, with no equivalent instructions or scripts for Linux or macOS users. Windows-centric tools and workflows (e.g., registry edits, Windows services, VMM, Hyper-V) are referenced exclusively, and Linux scenarios are not addressed, even for VMware or physical server cases.
Recommendations
  • Provide equivalent command-line or script examples for Linux environments, especially for VMware and physical server scenarios.
  • Clarify which steps are Windows-only and offer alternative guidance for Linux-based servers where possible.
  • Include bash or shell script examples for cleanup and unregistration tasks relevant to Linux systems.
  • Explicitly state OS requirements and limitations at the beginning of each section.
  • For VMware and physical server sections, add Linux-specific instructions for uninstalling the mobility service and cleaning up replication artifacts.
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-13 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 exclusively describing the configuration server VM as running Windows Server 2016, requiring Windows activation, and guiding users through Windows-specific setup steps. There are no Linux-based configuration server options or examples, and Windows credentials/setup are described before Linux equivalents. The process server and Mobility Service installation instructions prioritize Windows accounts and only briefly mention Linux (root) credentials, with no further Linux-specific guidance.
Recommendations
  • Provide explicit instructions or examples for deploying the configuration server on Linux-based VMs if supported, or clarify platform limitations.
  • Include Linux/macOS command-line examples and credential setup steps alongside Windows instructions.
  • Clearly state platform requirements and alternatives early in the documentation.
  • If only Windows is supported, add a prominent note explaining the limitation and suggest workarounds or alternatives for Linux users.
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-13 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 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/macOS examples or instructions, and Windows tools/patterns are presented exclusively.
Recommendations
  • Clarify early in the documentation that Storage Spaces Direct and guest clustering are Windows-only features, and note any Linux alternatives if available.
  • Provide guidance or links for disaster recovery of Linux-based clusters or virtual machines using Azure Site Recovery.
  • Include examples or references for setting up multi-VM consistency groups and recovery plans for Linux VMs.
  • If Azure Site Recovery supports Linux clusters, add parity instructions and screenshots for Linux scenarios.
  • Explicitly state limitations for non-Windows users to avoid confusion.
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-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation is heavily focused on Hyper-V, a Windows-only virtualization platform, and references Windows-specific tools, APIs, and workflows throughout. All examples and architectural components are centered on Windows environments (Hyper-V, VMM, Windows APIs), with no mention of Linux or cross-platform alternatives. This creates a strong Windows bias, making the documentation irrelevant for Linux/macOS users seeking disaster recovery solutions for non-Windows hypervisors.
Recommendations
  • Clarify in the introduction that the solution is specific to Hyper-V (Windows) and not applicable to Linux/macOS hosts.
  • Provide links or references to equivalent Azure Site Recovery documentation for Linux-based hypervisors (e.g., VMware, KVM) if available.
  • Add a comparison table or section outlining supported platforms and alternatives for Linux users.
  • If Azure Site Recovery supports Linux VMs or other hypervisors, include examples and architectural diagrams for those scenarios.
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-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Windows First Powershell Heavy Missing Linux Example
Summary
The documentation is heavily focused on Windows environments, specifically Hyper-V on Windows Server. All examples, prerequisites, and tooling references are Windows-centric, with exclusive mention of Windows tools (Hyper-V, VMM, PowerShell) and no Linux/macOS equivalents or guidance. PowerShell is the only automation example provided, and there is no mention of Linux-based virtualization platforms or how non-Windows users might interact with Azure Site Recovery in similar scenarios.
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 solutions (e.g., Azure Site Recovery for VMware or Linux physical servers).
  • Include parity examples for automation using Azure CLI or REST API, which are cross-platform and usable on Linux/macOS.
  • Mention alternative virtualization platforms and their support status, or provide guidance for users running Linux-based hypervisors.
  • Reorder sections or add notes so that Windows-specific instructions do not implicitly suggest Windows is the only supported platform for disaster recovery with Azure Site Recovery.
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-13 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 instructions and prerequisites referencing Windows tools and patterns. There are no examples, instructions, or mentions of Linux or macOS environments, nor guidance for users running non-Windows hypervisors. Windows-specific requirements (such as installing the Hyper-V role and using VMM) are presented as the only supported options, and Windows terminology is used exclusively throughout.
Recommendations
  • Clarify early in the document that the procedure is specific to Hyper-V (Windows) environments, and note any limitations for Linux/macOS users.
  • If Azure Site Recovery supports failback for Linux-based hypervisors (e.g., KVM, VMware on Linux), provide equivalent instructions or link to relevant documentation.
  • Where possible, mention alternatives or workarounds for Linux environments, or explicitly state that Linux is not supported for this scenario.
  • Consider adding a comparison table or section outlining supported platforms and failback procedures for each, including Linux if applicable.
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-13 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 on Windows Server and System Center Virtual Machine Manager. All examples, requirements, and supported scenarios are for Windows Server versions and Windows-centric management tools (SCVMM, PowerShell). There are no Linux/macOS equivalents, examples, or guidance for non-Windows platforms. Linux is only mentioned as a guest OS, not as a host or management environment.
Recommendations
  • Explicitly state that Azure Site Recovery for Hyper-V is a Windows-only solution, if that is the case, to avoid confusion for Linux/macOS users.
  • If Linux-based Hypervisors (e.g., KVM, Xen) or management tools are supported, add equivalent documentation and examples.
  • Provide parity in examples and instructions for PowerShell and Bash/CLI where possible, especially for Azure-side operations.
  • Include a comparison table or section outlining support for non-Windows platforms, or link to relevant documentation for Linux-based disaster recovery solutions.
  • Clarify in the prerequisites and support matrix that all host-side requirements are Windows-only, and suggest alternatives for Linux environments.
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-13 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 are no references to Linux or macOS equivalents, nor guidance for users running non-Windows platforms. The documentation assumes the reader is operating in a Windows ecosystem, with no mention of cross-platform considerations.
Recommendations
  • Add a section clarifying that the Deployment Planner and associated tooling are Windows/Hyper-V specific, and provide guidance for users of Linux-based virtualization platforms (e.g., KVM, VMware on Linux).
  • If Azure Site Recovery supports Linux VMs or other hypervisors, include links or references to equivalent documentation for those scenarios.
  • Explicitly state platform requirements and limitations at the beginning of the article.
  • Consider providing parity documentation for disaster recovery planning for Linux VMs, including example reports, tooling, and workflows.
  • If possible, mention any cross-platform tools or APIs that could be used for similar analysis on Linux/macOS.
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-13 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 oriented toward Windows environments, specifically Hyper-V on Windows Server. All setup and command-line instructions are for Windows tools (e.g., .exe installers, CMD commands), and there are no Linux or macOS equivalents or guidance. The documentation assumes the use of Windows-only components (Hyper-V, MARS agent, .exe installers), and all examples and screenshots are from Windows environments. There is no mention of how to perform similar tasks from Linux or macOS, nor any cross-platform alternatives.
Recommendations
  • Explicitly state early in the documentation that the process is only supported on Windows/Hyper-V, and clarify if Linux/macOS hosts are unsupported.
  • If any steps can be performed from Linux/macOS (e.g., Azure portal operations, scripting via Azure CLI), provide equivalent instructions or note compatibility.
  • Where possible, provide PowerShell and CMD examples alongside any available cross-platform CLI (e.g., Azure CLI) commands.
  • If the MARS agent or Site Recovery provider is Windows-only, clearly state this and link to Linux disaster recovery documentation for parity.
  • Consider adding a section for Linux-based hypervisors or linking to relevant documentation for non-Windows environments.
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-13 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 for VM access after failover reference Windows tools (RDP, Windows Firewall), with no mention of Linux VMs, SSH, or Linux firewall configuration. There are no Linux/macOS-specific instructions or parity examples, and the guidance assumes Windows as the default operating system.
Recommendations
  • Add explicit guidance for Linux VMs, including instructions for enabling SSH access and configuring Linux firewalls (e.g., ufw, firewalld) before failover.
  • Include troubleshooting steps for connecting to Linux VMs after failover, such as checking Boot diagnostics for Linux and resolving common SSH issues.
  • Mention Linux VM requirements and supported scenarios in the prerequisites section.
  • Provide examples for both Windows and Linux VM access, listing them side by side or in separate sections.
  • Clarify that Hyper-V is a Windows-only hypervisor, but note any Azure Site Recovery support for other platforms if applicable.
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-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation is focused exclusively on Hyper-V and System Center Virtual Machine Manager (VMM), which are Windows-only technologies. There are no references to Linux-based hypervisors (e.g., KVM, Xen), nor are there examples or guidance for Linux environments. All terminology, examples, and workflows assume a Windows ecosystem, leaving Linux users without actionable information.
Recommendations
  • Add a section clarifying platform requirements and limitations, explicitly stating that the guide is for Windows/Hyper-V environments.
  • Provide links or references to equivalent disaster recovery/network mapping documentation for Linux-based hypervisors (e.g., Azure Site Recovery for VMware/KVM).
  • If Azure Site Recovery supports Linux VMs or other hypervisors, include examples and mapping instructions for those platforms.
  • Consider including a comparison table showing feature parity and differences between Windows (Hyper-V/VMM) and Linux-based solutions.
GitHub Create Pull Request
← Previous Page 1 of 35 Next →