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 376-400 of 864 flagged pages
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/exclude-disks-replication.md ...in/articles/site-recovery/exclude-disks-replication.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by providing examples and walkthroughs exclusively for Windows VMs, focusing on Windows-specific concepts (drive letters, pagefile.sys, diskmgmt.msc, SQL Server on Windows), and omitting equivalent Linux scenarios. There are no Linux VM examples, no mention of Linux disk management tools or patterns, and Windows terminology is used throughout. Linux is only referenced in passing in a failback limitation table, without any practical guidance or examples.
Recommendations
  • Add parallel examples for Linux VMs, such as excluding disks containing swap partitions or temp files, and handling failover/failback for Linux workloads.
  • Include Linux disk management instructions (e.g., using lsblk, parted, fdisk, or LVM) for adding/initializing disks after failover.
  • Provide SQL Server on Linux scenarios, or examples for other common Linux workloads (e.g., MySQL, PostgreSQL) and their temp file management.
  • Reference Linux-specific tools and commands (e.g., systemctl for service management, mount for disk mounting) alongside Windows tools.
  • Clarify differences in drive letter assignment and disk handling between Windows and Linux VMs in Azure.
  • Ensure that screenshots and walkthroughs include Linux equivalents where applicable.
GitHub Create Pull Request
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/hyper-v-deployment-planner-run.md ...ticles/site-recovery/hyper-v-deployment-planner-run.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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 Hyper-V and Windows environments. All examples use Windows-style paths (e.g., E:\), mention Windows tools (Notepad), and reference UNC paths and conventions specific to Windows. There are no Linux equivalents or examples, and the tool described (ASRDeploymentPlanner.exe) appears to be a Windows executable with no mention of Linux support or usage patterns.
Recommendations
  • Clarify whether the ASRDeploymentPlanner tool is available for Linux or only for Windows. If Linux is supported, provide equivalent Linux usage instructions and examples.
  • Include Linux-style path examples (e.g., /mnt/hyperv_profileddata/) alongside Windows paths.
  • Mention Linux text editors (e.g., nano, vim) in addition to Notepad for editing output files.
  • If the tool is Windows-only, explicitly state this limitation at the beginning of the documentation.
  • Provide guidance for users managing Hyper-V environments from Linux systems, if possible (e.g., via remote management, PowerShell Core, or other cross-platform tools).
  • Consider parity in terminology and instructions for file handling, directory structures, and command-line usage for Linux users.
GitHub Create Pull Request
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/azure-to-azure-troubleshoot-errors.md ...es/site-recovery/azure-to-azure-troubleshoot-errors.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation exhibits Windows bias in several areas: Windows troubleshooting steps and tools (such as Services console, COM+, VSS, Internet Explorer) are mentioned first or exclusively, while Linux equivalents are often less detailed or missing. Windows-specific patterns (e.g., update management, service management) are described before or instead of Linux approaches. Some sections lack Linux examples or troubleshooting steps, and Windows tools are referenced without Linux alternatives.
Recommendations
  • Ensure Linux troubleshooting steps are provided wherever Windows steps are given (e.g., for COM+/VSS errors, include Linux service troubleshooting or clarify if not applicable).
  • Present Windows and Linux guidance in parallel, not sequentially or with Windows first; use tabs or side-by-side formatting.
  • Where Windows tools (e.g., Services console, Internet Explorer) are referenced, provide Linux alternatives (e.g., systemctl, checking proxy settings via environment variables).
  • Include Linux-specific error codes and troubleshooting where relevant, not just Windows-centric issues.
  • Clarify when an issue or workaround is Windows-only, and provide explicit statements about Linux applicability.
  • Expand Linux examples to match the detail and step-by-step guidance given for Windows, especially in certificate and proxy configuration sections.
GitHub Create Pull Request
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/concepts-on-premises-to-azure-networking.md ...e-recovery/concepts-on-premises-to-azure-networking.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a Windows bias by providing detailed, step-by-step instructions and links for preparing Windows machines, including PowerShell usage and Windows Firewall configuration. In contrast, Linux preparation is covered in only two brief bullet points, lacking equivalent detail, examples, or links. Windows-specific tools and patterns (RDP, WinHTTP proxy, Windows updates, SAN policy) are mentioned exclusively or before Linux equivalents, and all remote access instructions focus on RDP and Windows Firewall before mentioning SSH for Linux.
Recommendations
  • Expand the Linux preparation section to match the detail of the Windows section, including step-by-step instructions for enabling SSH, configuring firewall rules (e.g., using UFW, firewalld, or iptables), and verifying required services.
  • Provide Linux-specific examples for remote access setup, such as configuring SSHD, opening ports in Linux firewalls, and handling SELinux/AppArmor if relevant.
  • Include links to official Azure documentation for preparing Linux VMs for upload and failover, similar to the Windows links.
  • Mention Linux update management (e.g., pending apt/yum/dnf updates) and its impact on failover, paralleling the Windows update guidance.
  • Ensure parity in troubleshooting steps and references to diagnostic tools (e.g., serial console, SSH troubleshooting) for Linux VMs.
  • Present Windows and Linux instructions in parallel, rather than Windows-first, to avoid implicit prioritization.
GitHub Create Pull Request
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/hyper-v-azure-failover-failback-tutorial.md ...e-recovery/hyper-v-azure-failover-failback-tutorial.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation demonstrates a Windows bias by focusing exclusively on Hyper-V (a Windows-centric virtualization platform), referencing Windows-specific tools and patterns (such as RDP and Windows VM connection guides), and omitting Linux-specific examples or guidance. There are no instructions or references for managing or connecting to Linux VMs, nor are there examples using Linux tools or workflows.
Recommendations
  • Include explicit instructions and examples for failing over and connecting to Linux VMs, such as SSH connection steps and links to Linux VM documentation.
  • Reference both Windows and Linux Azure VM documentation equally when discussing post-failover validation and management.
  • When mentioning tools like RDP, also mention SSH and provide parity in troubleshooting and connection guides for Linux-based VMs.
  • Clarify in the introduction or prerequisites whether Linux VMs on Hyper-V are supported, and if so, provide relevant guidance.
  • Where possible, use neutral language and examples that apply to both Windows and Linux environments, or provide parallel sections for each.
GitHub Create Pull Request
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/hydration-process.md .../blob/main/articles/site-recovery/hydration-process.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in several ways: Windows configuration steps and examples are presented first and in greater detail, including screenshots and explicit PowerShell commands. Windows-specific tools (diskpart, PowerShell, registry editor) are referenced and illustrated, while Linux instructions are less detailed, lack screenshots, and rely on generic bash commands without distribution-specific guidance. Some manual configuration examples (e.g., setting DHCP) are given only for Windows (via PowerShell), with no equivalent Linux commands shown. Troubleshooting links and references also prioritize Windows scenarios.
Recommendations
  • Alternate the order of Windows and Linux sections, or present them in parallel tabs to avoid Windows-first bias.
  • Provide Linux-specific command-line examples for all manual steps, such as setting DHCP to automatic, checking agent installation, and validating network configuration.
  • Include screenshots or terminal output examples for Linux steps, similar to those provided for Windows.
  • Reference Linux tools and utilities (e.g., nmcli, systemctl, network manager commands) where appropriate, and provide distribution-specific instructions where necessary.
  • Ensure troubleshooting links and references cover Linux scenarios equally, not just Windows.
  • Explicitly mention Linux equivalents for all Windows tools and commands used in manual preparation steps.
GitHub Create Pull Request
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/hyper-v-azure-tutorial.md .../main/articles/site-recovery/hyper-v-azure-tutorial.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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 on Windows Server. All examples, instructions, and tooling references (such as the Azure Site Recovery provider, MARS agent, and command-line steps) are tailored for Windows systems. There are no Linux equivalents, examples, or alternative instructions for Linux-based hypervisors or environments. Windows tools and patterns (e.g., .exe installers, CMD commands, Windows file paths) are used exclusively, and Linux is not mentioned at all.
Recommendations
  • Add explicit notes clarifying that the tutorial is for Windows/Hyper-V only, and link to Linux/KVM/VMware disaster recovery guides if available.
  • Provide parity documentation for Linux-based hypervisors (e.g., KVM, Xen, VMware on Linux), including setup, replication, and failback instructions.
  • Where possible, mention cross-platform alternatives or limitations (e.g., if MARS agent is Windows-only, state this and suggest Linux alternatives).
  • Include example commands and installation steps for Linux environments if supported by Azure Site Recovery.
  • Ensure that documentation navigation makes it easy for Linux users to find relevant guides.
GitHub Create Pull Request
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/hyper-v-vmm-network-mapping.md .../articles/site-recovery/hyper-v-vmm-network-mapping.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation is heavily focused on Hyper-V and System Center Virtual Machine Manager (VMM), which are Windows-centric virtualization and management tools. There are no references to Linux-based hypervisors (such as KVM or Xen), nor are there examples or guidance for Linux environments. All terminology, examples, and scenarios assume a Windows infrastructure, and Windows tools are mentioned exclusively and first.
Recommendations
  • Add equivalent guidance for Linux-based hypervisors (e.g., KVM, Xen) and their integration with Azure Site Recovery.
  • Provide examples and scenarios for disaster recovery involving Linux VMs and management tools.
  • Mention Linux-compatible network mapping tools and patterns, and clarify any limitations or differences in support.
  • Include cross-platform comparison tables or notes to help administrators working in mixed environments.
GitHub Create Pull Request
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/delete-vault.md ...-docs/blob/main/articles/site-recovery/delete-vault.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates a Windows bias by exclusively providing PowerShell commands for vault deletion, referencing Windows-centric tools (Hyper-V, VMM), and omitting equivalent Linux/CLI examples. The use of PowerShell is presented as the primary or only automation method, with no mention of Azure CLI or Bash alternatives. The structure and examples prioritize Windows environments and tools, with no guidance for users on Linux or macOS platforms.
Recommendations
  • Add Azure CLI examples for vault deletion alongside PowerShell commands to support Linux/macOS users.
  • Include notes or sections on how to perform these operations from non-Windows environments.
  • Reference cross-platform tools and patterns (e.g., Bash, Azure CLI) before or alongside Windows-specific ones.
  • Ensure parity in instructions for unregistering servers and deleting resources, providing both Windows and Linux approaches where applicable.
  • Explicitly state platform requirements or limitations for each method, helping users choose the best fit for their environment.
GitHub Create Pull Request
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/concepts-trusted-vm.md ...lob/main/articles/site-recovery/concepts-trusted-vm.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates Windows bias in several ways: Windows OS is prioritized in feature support (e.g., shared disks, VM creation flow), with Linux support often described as unavailable or limited. Examples and instructions for migration reference PowerShell and CLI channels, but do not provide Linux-specific guidance or parity. Windows-centric features are mentioned before Linux equivalents, and some features are exclusive to Windows OS.
Recommendations
  • Add explicit Linux examples and instructions where only Windows or PowerShell/CLI are mentioned.
  • Clarify Linux support timelines and provide guidance for Linux users on alternative workflows when features are Windows-only.
  • Present Windows and Linux support information in parallel, rather than listing Windows features first or exclusively.
  • Include Linux-specific troubleshooting and migration steps, especially where agent uninstall or extension management is required.
  • Regularly review feature parity and update documentation as Linux support expands.
GitHub Create Pull Request
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/hyper-v-azure-failback.md .../main/articles/site-recovery/hyper-v-azure-failback.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation is heavily focused on Windows environments, specifically Hyper-V and System Center VMM, with all examples and instructions tailored to Windows tools and workflows. There is no mention of Linux-based hypervisors, Linux hosts, or equivalent failback procedures for non-Windows platforms. The steps assume the use of Windows Server and Hyper-V, and do not provide parity for Linux administrators or environments.
Recommendations
  • Add explicit statements clarifying platform support, including whether Linux-based hypervisors or hosts are supported for failback with Azure Site Recovery.
  • If Linux is supported, provide equivalent step-by-step instructions and examples for Linux environments, including any required tools, commands, or configuration steps.
  • Include references to Linux documentation or guides for similar scenarios, or link to alternative workflows for Linux-based disaster recovery.
  • If Linux is not supported, clearly state this limitation early in the documentation to set expectations for cross-platform users.
GitHub Create Pull Request
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/hybrid-how-to-enable-replication-private-endpoints.md ...https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/hybrid-how-to-enable-replication-private-endpoints.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits a Windows bias by listing Windows-related domains and tools first (e.g., *.windows.net, *.msftauth.net), referencing Azure PowerShell as a primary automation method, and omitting Linux-specific command-line examples (such as Azure CLI or Bash). The guidance and screenshots are focused on the Azure Portal and PowerShell, with no mention of Linux-native tools or workflows. There are no explicit instructions or examples for Linux administrators, and Windows-centric terminology and patterns are used throughout.
Recommendations
  • Add equivalent Azure CLI (az) commands for all steps currently shown with PowerShell or portal screenshots.
  • Include Linux-specific examples and workflows, such as Bash scripts or automation via shell.
  • List Linux-related domains and endpoints (if applicable) alongside or before Windows ones in allowlists.
  • Reference cross-platform tools and clarify that steps can be performed from Linux systems as well.
  • Provide screenshots or terminal outputs from Linux environments where relevant.
  • Explicitly mention support for Linux-based configuration servers and appliances, and link to relevant setup guides.
GitHub Create Pull Request
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/physical-azure-disaster-recovery.md ...cles/site-recovery/physical-azure-disaster-recovery.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page, while claiming to cover both Windows and Linux physical servers, demonstrates a Windows bias. Windows-specific instructions (such as registry edits and CLI commands) are provided in detail, while Linux instructions are minimal and lack equivalent examples. Windows tools and patterns (like registry editing and domain/local accounts) are mentioned explicitly, with Linux guidance limited to stating that 'root' should be used. No Linux-specific commands, configuration steps, or troubleshooting are provided, and Windows instructions are presented first and in more detail.
Recommendations
  • Provide Linux-specific examples for all steps where Windows instructions are given (e.g., show how to prepare the Linux account, any required configuration changes, or commands to run).
  • Include Linux CLI commands or configuration file edits where relevant, similar to the Windows registry example.
  • Ensure that Linux instructions are presented with equal detail and prominence as Windows instructions, possibly side-by-side.
  • Mention Linux-specific considerations for time synchronization (e.g., using ntpd or systemd-timesyncd) instead of only referencing Windows Time Service.
  • Add troubleshooting steps and tips for Linux environments, such as SELinux/AppArmor configuration, firewall settings, and log file locations.
  • Review all sections to ensure Linux is not only mentioned but actively supported with actionable guidance.
GitHub Create Pull Request
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/file-server-disaster-recovery.md ...rticles/site-recovery/file-server-disaster-recovery.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates a Windows bias by focusing almost exclusively on Windows-centric technologies and workflows, such as DFSR, Active Directory, and Azure File Sync (which is described only for Windows servers). Examples, configuration steps, and references are all tailored to Windows environments, with no equivalent Linux file server disaster recovery guidance, tools, or examples. The SMB protocol is mentioned as cross-platform, but all operational instructions and sync endpoints are Windows-specific. Linux is mentioned only in passing, with no actionable content for Linux administrators.
Recommendations
  • Add explicit guidance and examples for protecting Linux-based file servers using Azure Site Recovery, including supported replication methods and failover procedures.
  • Include instructions for configuring Azure File Sync or alternative cloud sync solutions for Linux servers, or clarify limitations and recommend best practices for Linux environments.
  • Provide parity in step-by-step walkthroughs for Linux file server disaster recovery scenarios, such as using NFS shares, rsync, or other Linux-native tools with Azure.
  • Mention and link to relevant Azure documentation for Linux file server DR, and ensure Linux tools and patterns are presented alongside Windows equivalents.
  • Clarify in tables and decision trees which recommendations apply to Linux, and add Linux-specific considerations where appropriate.
GitHub Create Pull Request
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/hyper-v-vmm-azure-tutorial.md ...n/articles/site-recovery/hyper-v-vmm-azure-tutorial.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation is heavily focused on Windows environments, specifically Hyper-V managed by System Center VMM. All examples, installation instructions, and command-line snippets use Windows tools and PowerShell, with no mention of Linux equivalents or alternative platforms. The tutorial assumes the reader is using Windows and does not provide guidance for Linux-based virtualization or management tools.
Recommendations
  • Add sections or links for disaster recovery setup for Linux-based hypervisors (e.g., KVM, Xen) or management tools.
  • Provide Linux command-line examples (e.g., Bash scripts) for agent installation and configuration.
  • Clarify in the prerequisites and introduction that the tutorial is Windows-specific, and point to Linux/other platform guides if available.
  • Include parity in troubleshooting and deployment planning tools for Linux environments.
  • Mention Azure Site Recovery support for non-Windows platforms, if applicable, and provide cross-references.
GitHub Create Pull Request
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/configure-mobility-service-proxy-settings.md ...-recovery/configure-mobility-service-proxy-settings.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a Windows bias by presenting Windows-specific instructions and tools (such as Internet Explorer and psexec) before Linux equivalents, and by providing detailed steps for Windows (including launching IE for proxy configuration) while Linux instructions are less detailed. Windows paths and tools are mentioned explicitly, whereas Linux instructions are more generic and lack step-by-step guidance. There are no Linux-specific examples for setting environment variables or editing ProxyInfo.conf, and Windows-centric terminology (e.g., Local System account) is used.
Recommendations
  • Provide Linux-specific step-by-step instructions for configuring proxy settings, including commands to edit /etc/profile or /etc/environment.
  • Include examples of setting environment variables on Linux (e.g., using export in bash or editing files with nano/vi).
  • Present Linux and Windows instructions in parallel, giving equal detail and prominence to both platforms.
  • Avoid referencing Windows-only tools (such as Internet Explorer and psexec) without offering Linux alternatives.
  • Clarify Linux file paths and permissions for ProxyInfo.conf, and provide sample commands for creating and editing the file.
GitHub Create Pull Request
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/hyper-v-azure-architecture.md ...n/articles/site-recovery/hyper-v-azure-architecture.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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-specific technologies, particularly Hyper-V and System Center VMM, with no mention of Linux-based hypervisors or cross-platform alternatives. All examples, architectural components, and process descriptions are tailored to Windows environments, and Windows terminology and tools are used exclusively. There are no Linux equivalents or examples provided, and the documentation assumes a Windows-centric infrastructure throughout.
Recommendations
  • Include information about disaster recovery for Linux-based hypervisors (e.g., KVM, Xen) and how they can integrate with Azure Site Recovery.
  • Provide parallel examples and architectural diagrams for Linux environments where possible.
  • Mention Linux tools and processes for replication, failover, and failback, or clarify the scope is limited to Windows/Hyper-V.
  • Add a section explicitly stating platform support and limitations, including whether Linux VMs or hosts are supported.
  • If Azure Site Recovery does not support Linux hypervisors, provide links or references to alternative solutions for Linux environments.
GitHub Create Pull Request
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/azure-to-azure-troubleshoot-replication.md ...te-recovery/azure-to-azure-troubleshoot-replication.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits several Windows-centric biases. Troubleshooting steps and examples frequently reference Windows tools, file paths, and services (e.g., VSS, PowerShell, Windows service names) with limited or less detailed Linux equivalents. Windows commands and patterns are often presented first or exclusively, while Linux instructions are brief or missing. The use of PowerShell and Windows-specific troubleshooting (such as VSS provider installation and service restarts) dominates the guidance, with Linux steps only occasionally mentioned and not elaborated.
Recommendations
  • Provide Linux-specific troubleshooting steps in equal detail to Windows, including commands and service management instructions.
  • Include Linux shell (bash) examples alongside PowerShell, especially for API calls and file edits.
  • List Linux file paths and service names with the same prominence as Windows equivalents.
  • Offer guidance for common Linux issues (e.g., troubleshooting application consistency, agent installation, service restarts) with step-by-step instructions.
  • Ensure that examples and instructions are presented in parallel for both platforms, rather than Windows-first or Windows-only.
  • Reference Linux tools (such as curl, systemctl, journalctl) where appropriate, not just Windows tools.
GitHub Create Pull Request
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/concepts-expressroute-with-site-recovery.md ...e-recovery/concepts-expressroute-with-site-recovery.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Missing Linux Example Windows First
Summary
The documentation demonstrates Windows bias by exclusively referencing Windows-specific tools (PsExec, Internet Explorer) and providing configuration steps only for Windows environments. There are no equivalent instructions or examples for Linux-based servers, nor is there mention of Linux tools or patterns for proxy configuration or bypass list management. The order of presentation also assumes Windows as the default environment for on-premises configuration.
Recommendations
  • Provide equivalent proxy bypass configuration steps for Linux servers, including commands for common shells (bash, etc.) and configuration files (e.g., /etc/environment, /etc/proxy.conf).
  • Reference cross-platform tools or alternatives to PsExec for Linux (such as sudo, su, or using systemd-run).
  • Include examples for configuring proxy settings and bypass lists in popular Linux browsers or CLI tools (e.g., curl, wget, Firefox).
  • Explicitly mention that the instructions apply to Windows and add parallel Linux sections where applicable.
  • Avoid assuming Windows as the default; present both Windows and Linux options side-by-side or indicate platform-specific steps clearly.
GitHub Create Pull Request
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/hyper-v-deployment-planner-analyze-report.md ...-recovery/hyper-v-deployment-planner-analyze-report.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation is heavily focused on Hyper-V, a Windows-centric virtualization platform, and all examples, terminology, and tooling are specific to Windows environments. There are no references to Linux-based hypervisors (such as KVM or VMware on Linux), nor are there any examples or guidance for users running Linux workloads or using Linux management tools. The documentation assumes the reader is working in a Windows ecosystem, with exclusive mention of Hyper-V hosts, VHD/VHDX files, and Windows storage paths (e.g., E:\VHDpath).
Recommendations
  • Add equivalent documentation and examples for Linux-based hypervisors (e.g., KVM, VMware on Linux) where Azure Site Recovery supports them.
  • Include Linux-specific terminology, such as disk formats (e.g., QCOW2), storage paths (/mnt/vms), and relevant Linux commands or tools.
  • Provide parity in guidance for Linux VM disaster recovery scenarios, including profiling, storage requirements, and replication batching.
  • Clarify in the introduction that the guide is specific to Hyper-V/Windows, and link to Linux-focused documentation if available.
  • If Azure Site Recovery does not support Linux hypervisors for this scenario, explicitly state this limitation to avoid confusion.
GitHub Create Pull Request
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/hyper-v-exclude-disk.md ...ob/main/articles/site-recovery/hyper-v-exclude-disk.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation is focused exclusively on Hyper-V, a Windows-based virtualization platform, and does not mention or provide guidance for equivalent scenarios on Linux-based hypervisors such as KVM or VMware. All examples, terminology, and instructions are tailored to Windows environments, with no Linux parity or cross-platform considerations.
Recommendations
  • Add equivalent instructions for excluding disks from replication for Linux-based hypervisors (e.g., KVM, VMware).
  • Include examples and screenshots for Linux environments where Azure Site Recovery is supported.
  • Clarify in the introduction that the guide is specific to Hyper-V/Windows, and link to documentation for other platforms if available.
  • Mention Linux disk types and considerations for exclusion, if supported by Azure Site Recovery.
GitHub Create Pull Request
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/delete-appliance.md ...s/blob/main/articles/site-recovery/delete-appliance.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates a Windows bias by referencing Windows-specific tools and patterns, such as 'Services.msc' and 'World Wide Web Publishing Service', and browser instructions focused on Microsoft Edge. There are no Linux-specific instructions or parity for managing or resetting the appliance from Linux environments, nor are Linux equivalents (e.g., systemctl, service commands) mentioned. The steps and troubleshooting guidance assume a Windows environment, leaving out Linux users who may also host the replication appliance.
Recommendations
  • Include Linux-specific instructions for managing and resetting the replication appliance, such as using 'systemctl' or 'service' commands to restart relevant services.
  • Mention Linux equivalents for 'Services.msc' and 'World Wide Web Publishing Service', e.g., Apache or Nginx, if applicable.
  • Provide browser cache clearing instructions for popular Linux browsers (e.g., Firefox, Chrome) alongside Microsoft Edge.
  • Add explicit notes or sections for Linux users, ensuring steps are platform-agnostic or offer alternatives.
  • Review all troubleshooting and operational steps to ensure Linux parity and avoid assuming a Windows-only environment.
GitHub Create Pull Request
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/hyper-v-prepare-on-premises-tutorial.md .../site-recovery/hyper-v-prepare-on-premises-tutorial.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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) and do not mention Linux VMs or SSH access. There is no guidance for preparing or accessing Linux VMs, nor are Linux firewall or connectivity patterns discussed.
Recommendations
  • Add sections for preparing Linux VMs for disaster recovery, including steps for enabling SSH and configuring Linux firewalls (e.g., ufw, firewalld).
  • Include examples for accessing Linux VMs after failover, such as SSH setup and troubleshooting.
  • Mention Linux VM requirements and supported configurations alongside Windows requirements.
  • Clarify that Azure Site Recovery can replicate both Windows and Linux VMs, and provide parity in documentation for both platforms.
  • Where Windows tools (e.g., RDP, Windows Firewall) are referenced, provide equivalent Linux tools and instructions.
GitHub Create Pull Request
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/hyper-v-azure-support-matrix.md ...articles/site-recovery/hyper-v-azure-support-matrix.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation is heavily focused on Windows environments, specifically Hyper-V on Windows Server and System Center Virtual Machine Manager (VMM). All examples, requirements, and supported scenarios are Windows-centric, with no mention of Linux-based Hypervisors or management tools. PowerShell is referenced as the primary automation/deployment method, and Windows Server versions are listed exclusively. Linux is only referenced as a guest OS, not as a host or management platform.
Recommendations
  • Add explicit statements clarifying that only Windows-based Hyper-V hosts are supported, and consider mentioning alternatives for Linux-based virtualization (e.g., KVM, Xen) if relevant.
  • Provide parity in deployment and management examples by including Azure CLI or REST API instructions alongside PowerShell, especially for scenarios where PowerShell is referenced.
  • Include a section comparing Hyper-V/Windows-centric disaster recovery with Linux-based virtualization solutions, or link to relevant documentation for Linux environments.
  • Clarify support for Linux guest VMs, including any limitations or best practices, and ensure that Linux-specific features (e.g., static IP configuration, LVM) are documented with equal detail as Windows features.
  • If Linux-based management is not supported, state this explicitly to avoid confusion for cross-platform administrators.
GitHub Create Pull Request
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/hyper-v-azure-common-questions.md ...ticles/site-recovery/hyper-v-azure-common-questions.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation is heavily focused on Windows environments, specifically Hyper-V on Windows Server, with exclusive references to Windows tools (VMM, Hyper-V Replica, Recovery Services agent, PowerShell). There are no Linux equivalents or examples provided, and automation is only described using PowerShell. The documentation assumes the reader is using Windows Server and does not mention or provide guidance for Linux-based hypervisors or management tools.
Recommendations
  • Add explicit statements clarifying that Azure Site Recovery for Hyper-V is Windows-centric, and provide links or references to disaster recovery solutions for Linux-based environments (e.g., KVM, VMware on Linux).
  • Include Linux-based examples or mention alternative tooling for Linux hosts where applicable, or clarify that such scenarios are not supported.
  • When discussing automation, mention cross-platform options such as Azure CLI or REST API usage, and provide example commands for Linux/macOS environments.
  • If possible, provide a comparison table showing supported features and limitations for both Windows and Linux environments in Azure Site Recovery.
  • Ensure that references to tools (e.g., PowerShell, VMM) are balanced with mentions of their cross-platform or Linux alternatives, or clarify their Windows-only nature.
GitHub Create Pull Request
← Previous Page 16 of 35 Next →