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 26-50 of 232 flagged pages
Site Recovery Disaster recovery of Dynamics AX with Azure Site Recovery ...ain/articles/site-recovery/site-recovery-dynamicsax.md
High Priority View Details →
Scanned: 2026-01-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 oriented toward Windows environments, specifically referencing Windows Server, Active Directory, SQL Server, and Dynamics AX components that are Windows-only. All examples and scenarios assume Windows-based infrastructure, with no mention of Linux or cross-platform alternatives. There are no Linux-specific instructions, examples, or considerations, and all tooling and recovery steps are described in terms of Windows technologies.
Recommendations
  • Explicitly state that Dynamics AX is a Windows-only application, if applicable, to clarify the scope for Linux users.
  • If any components (e.g., SQL Server, networking, VMware) can run on Linux, provide equivalent instructions or note Linux compatibility.
  • Add a section addressing disaster recovery considerations for environments with Linux servers, even if only for supporting infrastructure.
  • Where possible, mention cross-platform tools or alternatives (e.g., Azure CLI, PowerShell Core) for steps currently described only for Windows.
  • Clarify prerequisites and limitations for non-Windows environments to help Linux/macOS administrators understand applicability.
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-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 IIS on Windows Server, with all examples, scripts, and deployment patterns centered around Windows technologies. There are no Linux or cross-platform equivalents mentioned, and all automation scripts referenced are for Windows (e.g., PowerShell). Linux-based web applications, such as those running Apache or Nginx, are not addressed, nor are Linux failover or recovery steps provided.
Recommendations
  • Add equivalent guidance for disaster recovery of Linux-based web applications (e.g., Apache, Nginx) using Azure Site Recovery.
  • Provide Linux-specific examples for scripting post-failover actions (e.g., using Bash, Python) and updating configuration files.
  • Include references to Linux tools and patterns (such as systemd, network configuration, certificate management) where relevant.
  • Clarify in the prerequisites and introduction whether the guidance is Windows-only, or expand scope to include Linux scenarios.
  • Offer sample scripts and automation for Linux VMs, such as updating DNS, connection strings, and SSL bindings.
GitHub Create Pull Request
Site Recovery Disaster recovery for a multi-tier SharePoint app using Azure Site Recovery ...ain/articles/site-recovery/site-recovery-sharepoint.md
High Priority View Details →
Scanned: 2026-01-12 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 oriented toward Windows environments, with all examples and guidance referencing Windows Server, Windows PowerShell cmdlets, and Windows-centric tools (e.g., DFSR, Central Administration GUI). There are no Linux or cross-platform examples, and critical recovery steps (such as restoring SharePoint Search service) rely on Windows-only tools and commands. This creates significant friction for Linux users and those running SharePoint on non-Windows platforms.
Recommendations
  • Add explicit guidance for Linux-based environments, even if SharePoint itself is Windows-only, to cover supporting infrastructure (e.g., SQL Server on Linux, DNS on Linux).
  • Provide alternative examples for scripting and automation using cross-platform tools (e.g., Bash, Azure CLI) alongside PowerShell.
  • Clarify which steps are Windows-specific and offer workarounds or references for Linux/macOS users where possible.
  • Include notes or links to documentation for managing Azure Site Recovery and related networking from Linux/macOS systems.
  • If SharePoint recovery is fundamentally Windows-only, state this clearly at the outset to set expectations for cross-platform 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-12 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 demonstrates a strong Windows bias. All example commands for gathering VM lists use VMware vSphere PowerCLI (a Windows/PowerShell tool), and the main tool (ASRDeploymentPlanner.exe) is a Windows executable. Instructions reference Windows-specific concepts (Notepad, UNC paths, Control Panel, Excel XLSM output, etc.) and do not provide Linux/macOS alternatives or guidance. The report generation explicitly requires Windows and Excel. No Linux shell, cross-platform, or macOS instructions/examples are given.
Recommendations
  • Provide Linux/macOS alternatives for gathering VM lists, such as using VMware CLI tools (e.g., govc, pyvmomi, or vSphere API calls via Python/Perl).
  • Clarify whether ASRDeploymentPlanner.exe can run under Wine or Mono on Linux/macOS, or provide a cross-platform version if possible.
  • Offer instructions for viewing or converting the generated Excel report on non-Windows platforms (e.g., LibreOffice, Excel Online, or CSV export).
  • Include notes or examples for Linux/macOS users where file paths, text editors, or command-line usage differ.
  • Explicitly state platform requirements and limitations at the top of the document.
GitHub Create Pull Request
Site Recovery Shared disks in Azure Site Recovery ...ob/main/articles/site-recovery/tutorial-shared-disk.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation is heavily focused on Windows Server Failover Clusters (WSFC) and does not mention Linux-based clustering solutions or provide guidance for Linux virtual machines. All examples, prerequisites, and references are specific to Windows environments, with no mention of Linux equivalents or cross-platform considerations.
Recommendations
  • Explicitly state whether Linux-based clusters (e.g., Pacemaker, Corosync) are supported or not.
  • If Linux clustering is supported, add equivalent instructions and examples for Linux clusters.
  • Include prerequisites and references for Linux environments, such as links to documentation for setting up Linux clusters on Azure.
  • Clarify any limitations regarding shared disk support for Linux VMs in Azure Site Recovery.
  • If only Windows is supported, make this clear early in the documentation to set user expectations.
GitHub Create Pull Request
Site Recovery Unregister a Virtual Machine Manager server script ...articles/site-recovery/unregister-vmm-server-script.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 provides only a PowerShell script for unregistering a Virtual Machine Manager (VMM) server, relying exclusively on Windows-specific tools (PowerShell, Windows registry, Windows services, Windows clustering). There are no Linux or macOS equivalents, nor any mention of how to perform similar operations on non-Windows platforms. The instructions and examples are tailored entirely for Windows environments, making it impossible for Linux/macOS users to follow or adapt the guidance.
Recommendations
  • Clearly state that the procedure is Windows-only, and explain why (e.g., VMM is a Windows-only product).
  • If any part of the process can be performed from Linux/macOS (e.g., database cleanup via SQL tools), provide equivalent command-line examples using bash, sqlcmd, or other cross-platform tools.
  • Where registry or service manipulation is required, clarify that these are Windows-specific and suggest any alternative approaches for non-Windows environments if applicable.
  • Add a note at the beginning of the documentation indicating platform requirements and limitations.
  • If possible, provide guidance for users managing hybrid environments, or link to related Linux/macOS documentation.
GitHub Create Pull Request
Site Recovery Manage a process server for VMware VMs/physical server disaster recovery in Azure Site Recovery ...es/site-recovery/vmware-azure-manage-process-server.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 page demonstrates a notable Windows bias. All command-line instructions use Windows-specific tools (cmd.exe, PowerShell), Windows environment variables (%PROGRAMDATA%), and Windows file paths (C:\...). There are no Linux or macOS equivalents or examples provided for any of the management tasks, despite the fact that VMware environments and physical servers may run Linux. Anti-virus exclusions and proxy settings are described only for Windows, and all screenshots and UI instructions reference Windows conventions.
Recommendations
  • Provide equivalent Linux/macOS instructions for command-line tasks, including file paths and commands.
  • Clarify whether the process server software is Windows-only, or if Linux is supported, and document accordingly.
  • Add Linux-specific anti-virus exclusion paths and proxy configuration steps.
  • Include notes or sections for Linux users, or explicitly state platform limitations if Linux is unsupported.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits a notable Windows bias. Critical management tasks, such as updating the OS license, renewing SSL certificates, reregistering servers, and deleting/unregistering configuration servers, are described using Windows-specific tools, paths, and PowerShell commands. References to Windows-only utilities (e.g., DISM, CSPSConfigtool.exe, genpassphrase.exe) and registry edits are prevalent, with no Linux equivalents or guidance for Linux-based deployments. PowerShell is the only CLI example provided, and all file paths and command syntax are Windows-centric. There is no mention of how to perform these tasks on Linux or macOS, nor any parity in example ordering or tool coverage.
Recommendations
  • Add equivalent Linux/macOS instructions for all CLI and management tasks, including license activation, certificate renewal, server registration, and deletion.
  • Provide Bash or shell script examples alongside PowerShell, and clarify which steps are OS-specific.
  • Document Linux file paths and tool usage (e.g., for certificate renewal, passphrase generation, and configuration changes).
  • Explicitly state OS requirements and limitations for the configuration server, and if Windows is mandatory, clarify this early in the documentation.
  • If Linux is supported, ensure all screenshots, examples, and tool references are provided for both platforms.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation exclusively references Windows tools and installation patterns, such as running .exe installers and specifying Windows-style paths (e.g., C:\Temp\Extracted). There are no Linux/macOS equivalents or examples provided, nor is there any mention of how to perform these steps on non-Windows platforms. This creates friction for Linux users who may need to deploy or manage process servers in heterogeneous environments.
Recommendations
  • Clarify whether the process server installer is Windows-only or provide explicit Linux/macOS support information.
  • If Linux is supported, add installation instructions and command-line examples for Linux (e.g., .sh scripts, Linux paths, package dependencies).
  • If only Windows is supported, state this clearly at the start of the article to set expectations for non-Windows users.
  • Include a section comparing Windows and Linux deployment steps if both are supported.
  • Mention any Linux-specific prerequisites or troubleshooting tips.
GitHub Create Pull Request
Site Recovery Troubleshoot upgrade of the Microsoft Azure Site Recovery Provider ...recovery/vmware-azure-troubleshoot-upgrade-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 Missing Linux Example Windows First Powershell Heavy
Summary
The documentation exclusively references Windows tools (Command Prompt, Registry Editor, Task Manager), Windows file paths (C:\), and Windows-specific executable files. There are no examples, instructions, or notes for Linux or macOS users, nor any mention of equivalent Linux troubleshooting steps or commands. All examples and troubleshooting flows assume a Windows environment.
Recommendations
  • Add explicit notes clarifying platform support (e.g., whether Linux is supported for Site Recovery Provider upgrades).
  • If Linux/macOS upgrades are supported, provide equivalent troubleshooting steps for those platforms, including command-line examples (e.g., using bash, Linux file paths, and Linux equivalents for registry/configuration changes).
  • Mention Linux tools (such as grep, systemd, or relevant package managers) where appropriate.
  • If the product is Windows-only, state this clearly at the beginning of the documentation to set expectations for non-Windows users.
GitHub Create Pull Request
Site Recovery About Hyper-V (with VMM) network mapping with Site Recovery .../articles/site-recovery/hyper-v-vmm-network-mapping.md
High Priority View Details →
Scanned: 2026-01-11 06:20
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 (such as KVM or Xen), nor are there examples or guidance for Linux environments. All scenarios, terminology, and examples assume a Windows-centric infrastructure.
Recommendations
  • Include guidance or links for equivalent disaster recovery scenarios involving Linux-based hypervisors (e.g., KVM, Xen, VMware on Linux).
  • Clarify early in the documentation that the guidance is specific to Windows/Hyper-V, and provide references to Azure Site Recovery documentation for Linux environments.
  • If Azure Site Recovery supports Linux VM replication, add examples and mapping instructions for Linux VMs and networks.
  • Consider providing a comparison table or section outlining differences and similarities for Linux and Windows environments in Azure Site Recovery.
GitHub Create Pull Request
Site Recovery Support Requirements for Azure Site Recovery Replication Appliance .../site-recovery/replication-appliance-support-matrix.md
High Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows Only Missing Linux Example 🔧 Windows Tools Windows First
Summary
The documentation is heavily biased towards Windows environments. All operating system requirements, folder paths, and configuration instructions are specific to Windows Server (2022/2019), with no mention of Linux or macOS support or equivalents. Antivirus exclusions and folder paths are Windows-only, and all referenced tools and roles are Windows-centric. There are no Linux examples, requirements, or alternatives provided, making it unclear if Linux-based appliances are supported or how Linux users should proceed.
Recommendations
  • Clarify whether Linux-based replication appliances are supported. If not, explicitly state Windows-only support.
  • If Linux is supported, add equivalent Linux requirements (OS versions, folder paths, antivirus exclusions, etc.).
  • Provide Linux-specific instructions or examples for deployment, configuration, and troubleshooting.
  • Include a comparison table of supported operating systems and highlight any feature gaps.
  • Mention Linux alternatives for Windows-specific roles, tools, or settings where applicable.
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-11 06:20
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, providing only Windows-specific instructions (registry edits, KB articles, .NET Framework configuration) and omitting any guidance for Linux or macOS systems. All examples, troubleshooting, and configuration steps are Windows-centric, with no mention of how TLS 1.2 is managed or verified on non-Windows platforms.
Recommendations
  • Add a section describing how TLS 1.2 is handled on Linux and macOS, including verification steps and configuration guidance.
  • Include examples for checking and enforcing TLS 1.2 usage on Linux (e.g., OpenSSL, system-wide crypto policies, application-specific settings).
  • Clarify whether Azure Site Recovery supports Linux/macOS clients/agents and, if so, provide parity in documentation for those platforms.
  • Reference Linux/macOS equivalents for troubleshooting TLS issues (e.g., log locations, error messages, relevant configuration files).
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-11 06:20
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 IIS web applications running on Windows Server, with all examples and scenarios assuming Windows-based deployments. There are no references to Linux-based web servers (such as Apache or Nginx), nor are there examples or guidance for disaster recovery of Linux workloads. Scripts referenced are Windows-centric (e.g., PowerShell), and all deployment patterns, screenshots, and recovery steps are tailored to Windows environments.
Recommendations
  • Add equivalent guidance and examples for Linux-based web applications (e.g., Apache, Nginx) and their disaster recovery using Azure Site Recovery.
  • Include sample scripts for post-failover operations on Linux VMs (e.g., Bash scripts for updating DNS, site bindings, and certificates).
  • Mention Linux-supported scenarios explicitly in the 'Site Recovery support' section, including supported distributions and web server types.
  • Provide screenshots and walkthroughs for Linux VM configuration in Azure Site Recovery.
  • Clarify in the prerequisites and introduction that the guidance is Windows/IIS-specific, or expand scope to include Linux scenarios.
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-11 06:20
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 VMware VM that boots into a Windows Server 2016 environment, and all post-deployment instructions (such as signing in, running the Azure Site Recovery Configuration tool, installing MySQL, and managing the server) are Windows-centric. Examples and instructions reference Windows tools, file paths (e.g., C:\Temp\ASRSetup), and administrator accounts, with Linux mentioned only briefly and without detailed guidance or parity in examples. No Linux or macOS alternatives are provided for any step, and the documentation assumes the use of Windows throughout the process.
Recommendations
  • Provide explicit guidance for Linux-based configuration server deployment if supported, or clarify that only Windows is supported.
  • Include Linux/macOS-specific instructions for tasks such as MySQL installation, file paths, and user account requirements.
  • If the configuration server must be Windows-based, state this clearly at the beginning of the documentation to set expectations for non-Windows users.
  • Offer troubleshooting and FAQ sections that address common issues for Linux/macOS administrators, or clarify limitations.
  • Where possible, present examples for both Windows and Linux environments, especially for credential management and mobility service installation.
GitHub Create Pull Request
Site Recovery Troubleshoot the Azure Site Recovery process server ...y/vmware-physical-azure-troubleshoot-process-server.md
High Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exhibits a Windows bias by exclusively referencing Windows tools, file paths, and troubleshooting steps. All examples use Windows conventions (e.g., C:\ paths, Task Manager, Resource Monitor, Control Panel, Windows Registry, and Telnet from Windows documentation). There are no Linux/macOS equivalents or guidance for users running process servers or source machines on those platforms.
Recommendations
  • Provide Linux/macOS equivalents for all troubleshooting steps, including service management, log file locations, and network connectivity checks.
  • Include examples using Linux commands (e.g., systemctl, journalctl, netstat, telnet, curl) and file paths (/var/log, /etc).
  • Document how to check and manage process server services on Linux, including how to verify service status and configure startup behavior.
  • Add instructions for checking resource usage on Linux (e.g., using top, htop, or system resource monitors).
  • Clarify whether the process server and agent software are supported on Linux/macOS, and if not, state this explicitly.
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-11 06:20
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 requiring the configuration server VM to run Windows Server 2016, describing a Windows installation experience, and providing detailed steps for Windows credential requirements. Linux is mentioned only briefly for credential input, with no equivalent setup or example for a Linux-based configuration server. All screenshots and step-by-step instructions assume Windows environments, and there are no Linux/macOS-specific instructions or parity in tooling.
Recommendations
  • Provide instructions and examples for setting up the configuration server on Linux, if supported.
  • Include Linux/macOS credential requirements and installation steps in equal detail to Windows.
  • Add screenshots and walkthroughs for Linux-based environments where applicable.
  • Clarify OS requirements up front and, if Windows is mandatory, explain why and suggest alternatives or workarounds for Linux/macOS 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-11 06:20
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 Windows technologies, specifically 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-specific instructions, examples, or considerations, making the content inaccessible for users managing non-Windows workloads.
Recommendations
  • Add a section clarifying that Storage Spaces Direct and guest clustering are Windows-only features, and specify if Azure Site Recovery supports similar disaster recovery scenarios for Linux-based clusters.
  • Provide guidance or links for disaster recovery of Linux virtual machines or clusters, if supported.
  • Include examples or references to Linux failover technologies (e.g., Pacemaker, Corosync) and how they can be protected with Azure Site Recovery, if applicable.
  • Explicitly state limitations for non-Windows users at the beginning of the document.
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-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First Powershell Heavy
Summary
The documentation page exhibits a notable Windows bias. It focuses almost exclusively on Windows-centric technologies such as DFSR, Active Directory, and Azure File Sync (which only supports Windows servers as endpoints). Step-by-step instructions and architectural recommendations are tailored to Windows environments, with no concrete examples or guidance for Linux or macOS file servers. References to mounting Azure Files on Linux/macOS are limited to brief mentions, and all detailed procedures, sync group configurations, and failover scripts assume Windows. Linux and macOS users are left without actionable steps for disaster recovery using Azure Site Recovery.
Recommendations
  • Add explicit guidance and examples for protecting Linux-based file servers, including supported replication and failover strategies.
  • Include instructions for mounting Azure Files on Linux and macOS, with sample scripts and troubleshooting steps.
  • Clarify limitations and alternatives for non-Windows environments in each major section.
  • Present cross-platform options and parity in decision trees and tables, not just Windows-centric solutions.
  • Reference Linux-native tools (e.g., rsync, NFS, SMB mounting on Linux) where appropriate.
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-11 06:20
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 tools, APIs, and workflows throughout. All examples, terminology, and process descriptions are tailored to Windows environments, with no mention of Linux or macOS equivalents, nor guidance for users running non-Windows hypervisors. This creates a strong Windows bias, making the content inaccessible to Linux/macOS users or those using other virtualization technologies.
Recommendations
  • Clearly state at the beginning that the guidance is specific to Hyper-V (Windows-only), and provide links or references to equivalent disaster recovery documentation for Linux-based hypervisors (e.g., KVM, VMware on Linux).
  • Where possible, mention Azure Site Recovery support for Linux VMs and provide cross-references to relevant documentation.
  • If Azure Site Recovery can be used with Linux-based VMs or hosts, add sections or links describing those workflows.
  • Include a comparison table or FAQ addressing support for non-Windows platforms, and clarify limitations.
  • Avoid using Windows-specific terminology (e.g., PowerShell, Windows APIs) without context or alternatives for other platforms.
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-11 06:20
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 are no references to Linux or macOS equivalents, nor are alternative platforms or tools mentioned. Steps such as installing Windows and the Hyper-V role are presented as prerequisites, and no Linux-based failback scenarios or guidance are provided.
Recommendations
  • Add explicit statements clarifying that the process is only applicable to Windows/Hyper-V environments, and mention alternatives for Linux/KVM users if available.
  • Provide links or references to documentation for Linux-based disaster recovery or failback solutions using Azure Site Recovery or other Azure services.
  • If Azure Site Recovery supports Linux VMs or KVM hosts, include parallel instructions or examples for those platforms.
  • Consider a section outlining limitations for non-Windows environments, so Linux/macOS users can quickly determine applicability.
GitHub Create Pull Request
Site Recovery Common questions for Hyper-V disaster recovery with Azure Site Recovery ...ticles/site-recovery/hyper-v-azure-common-questions.md
High Priority View Details →
Scanned: 2026-01-11 06:20
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 on Windows Server, and uses Windows-centric tools and terminology throughout. Examples and automation references are exclusively for PowerShell, with no mention of Linux or macOS equivalents. There are no Linux/macOS-specific instructions, examples, or considerations, 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 guidance or links for disaster recovery of Linux-based hypervisors (e.g., KVM, Xen) to Azure, if supported.
  • Include parity examples for automation using Azure CLI, REST API, or other cross-platform tools, not just PowerShell.
  • Mention alternative approaches for Linux/macOS users, such as replicating physical Linux servers or using Azure Migrate.
  • Add a section comparing Hyper-V/Windows and Linux-based DR scenarios, with links to relevant documentation.
GitHub Create Pull Request
Site Recovery Troubleshoot Hyper-V disaster recovery with Azure Site Recovery ...n/articles/site-recovery/hyper-v-azure-troubleshoot.md
High Priority View Details →
Scanned: 2026-01-11 06:20
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 on Windows Server, with troubleshooting steps, logs, and tools that are almost exclusively Windows-centric. Examples and instructions use Windows tools (Event Viewer, PowerShell, Disk Management), and references to Linux are minimal and lack actionable detail. Linux scenarios are mentioned only briefly, with no concrete troubleshooting steps or parity in examples.
Recommendations
  • Add explicit troubleshooting steps for Linux-based Hyper-V guests, including log locations, relevant commands, and common issues.
  • Provide Linux command-line equivalents for PowerShell and Windows GUI steps (e.g., checking VSS status, disk types, service health).
  • Include examples and screenshots for Linux environments where applicable.
  • Clarify which steps are Windows-only and offer Linux alternatives or note limitations.
  • Ensure references to Linux documentation are actionable and detailed, not just links.
GitHub Create Pull Request
Site Recovery Set up Hyper-V disaster recovery by using Azure Site Recovery .../main/articles/site-recovery/hyper-v-azure-tutorial.md
High Priority View Details →
Scanned: 2026-01-11 06:20
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 or Windows Core. All installation, configuration, and command-line instructions reference Windows executables, Windows file paths, and Windows-specific tools (e.g., .exe installers, %Programdata% paths, and cmd commands). There are no examples, instructions, or mentions of Linux or macOS equivalents, nor is there guidance for users running Hyper-V on non-Windows platforms (which, while rare, is technically possible via nested virtualization or management scenarios). The use of MARS agent and Site Recovery provider is described only for Windows, and all screenshots and UI flows are Windows-centric.
Recommendations
  • Explicitly state that the tutorial is intended for Windows-based Hyper-V hosts, and clarify platform requirements early in the prerequisites.
  • If Linux-based Hyper-V management or nested virtualization scenarios are supported, provide equivalent instructions or note limitations.
  • Add a section addressing cross-platform considerations, such as how to manage Hyper-V VMs from Linux/macOS (e.g., via Azure CLI, REST API, or remote management tools).
  • Where possible, offer PowerShell and CLI alternatives, and clarify which steps are Windows-only.
  • Include a note or link to Linux disaster recovery documentation for parity and to guide non-Windows users.
GitHub Create Pull Request
Site Recovery Deployment Planner for Hyper-V disaster recovery with Azure Site Recovery ...s/site-recovery/hyper-v-deployment-planner-overview.md
High Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation is heavily biased towards Windows environments. All examples, prerequisites, and instructions are specific to Windows Server (2012 R2/2016), with exclusive use of PowerShell commands and Windows-specific tools. There is no mention of Linux or macOS support, nor any alternative instructions or examples for non-Windows platforms. The deployment planner tool itself appears to require Windows, and even report generation requires Microsoft Excel on Windows.
Recommendations
  • Clarify in the introduction that the tool is Windows-only, and explicitly state lack of Linux/macOS support.
  • If possible, develop and document cross-platform alternatives or versions of the tool that can run on Linux/macOS.
  • Provide equivalent instructions or guidance for users in mixed environments, such as how to profile Hyper-V from a Linux management host (if feasible).
  • Offer non-PowerShell alternatives for relevant steps, or at least note that PowerShell is not available on Linux/macOS for these operations.
  • Consider providing a web-based or Azure-hosted version of the planner that does not require a Windows client.
GitHub Create Pull Request
← Previous Page 2 of 10 Next →