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 276-300 of 864 flagged pages
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-09 00:34
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, while Linux instructions are minimal and lack comparable detail or example commands. Windows tools and patterns (RDP, WinHTTP proxy, Windows Firewall, Windows Update) are mentioned exclusively or before Linux equivalents, and Linux preparation is summarized in only two short bullet points without links or command examples.
Recommendations
  • Expand the Linux preparation section to include detailed steps comparable to the Windows section, such as commands for enabling SSH, configuring firewall rules (e.g., using ufw, firewalld, or iptables), and checking service status.
  • Provide links to relevant Azure documentation for Linux VM preparation, similar to those given for Windows.
  • Include example commands/scripts for Linux (e.g., systemctl enable ssh, ufw allow ssh) and troubleshooting tips.
  • Mention Linux-specific considerations (e.g., SELinux/AppArmor, package updates) and how to handle them before failover.
  • Ensure parity in guidance for remote access (e.g., SSH setup, public key authentication) and network configuration for Linux VMs.
  • Where Windows tools/patterns are mentioned, add Linux equivalents or alternatives (e.g., SSH instead of RDP, Linux firewall configuration).
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-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates Windows bias by exclusively referencing Windows tools and patterns (e.g., 'Services.msc', 'World Wide Web Publishing Service', Microsoft Edge), and omits Linux equivalents or instructions. There are no Linux-specific examples or guidance for users managing the appliance on Linux-based systems, and Windows terminology appears first and exclusively in relevant sections.
Recommendations
  • Provide Linux-specific instructions for resetting services (e.g., using systemctl to restart web services).
  • Include guidance for clearing browser cache on popular Linux browsers (e.g., Firefox, Chromium).
  • Mention Linux equivalents for managing services and restarting the machine.
  • Clarify whether the appliance can run on Linux, and if so, add parity for Linux management steps.
  • Avoid referencing only Windows tools (such as 'Services.msc') and instead offer cross-platform alternatives or note platform-specific steps.
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-09 00:34
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 providing only PowerShell examples for deleting an Azure Site Recovery vault, referencing Windows-centric tools (Hyper-V, System Center VMM), and omitting equivalent Linux/CLI examples. The use of PowerShell is presented as the primary or only method for force deletion, with no mention of Bash, Azure CLI, or cross-platform alternatives. Windows scenarios (Hyper-V, VMM) are described in detail, while Linux-based recovery or management scenarios are not addressed.
Recommendations
  • Add Azure CLI (az) command examples for vault deletion to provide cross-platform guidance.
  • Explicitly mention that PowerShell commands can be run on Linux/macOS via PowerShell Core, or provide Bash alternatives.
  • Include Linux-based replication/deletion scenarios if supported, or clarify platform limitations.
  • Balance references to Windows tools (Hyper-V, VMM) with equivalent Linux virtualization or backup solutions where applicable.
  • Reorder or parallelize instructions so that Windows and Linux methods are presented together, rather than Windows-first.
GitHub Create Pull Request
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/failover-failback-overview-modernized.md ...site-recovery/failover-failback-overview-modernized.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation demonstrates a Windows bias in several ways. Windows VM instructions are listed before Linux in connection steps, with more detailed guidance and troubleshooting for Windows (e.g., RDP, Windows Firewall, SAN policy, Windows Update). Windows-specific tools and concepts (RDP, Windows Firewall, SAN policy, Windows Update) are mentioned, while Linux instructions are brief and lack parity (e.g., no mention of SSH troubleshooting, Linux firewall specifics, or SAN policy equivalents). There are references to Windows Server versions and behaviors, but no similar detail for Linux distributions. VMware failover notes mention disabling VMware tools for Windows VMs, but do not provide Linux-specific details.
Recommendations
  • Provide Linux instructions with equal detail, including SSH troubleshooting, Linux firewall configuration (e.g., iptables, firewalld, ufw), and SAN policy or disk handling equivalents.
  • List Linux and Windows steps side-by-side or in parallel, rather than always listing Windows first.
  • Include guidance for common Linux distributions (e.g., Ubuntu, RHEL, CentOS) and their specific behaviors during failover/failback.
  • Mention Linux-specific update considerations (e.g., pending package updates, systemd services) similar to Windows Update advice.
  • Add troubleshooting links and resources for Linux remote access and failover issues, matching those provided for Windows.
  • Clarify any differences in failover/failback processing for Linux VMs, such as boot diagnostics, agent registration, and recovery point handling.
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-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates a strong Windows bias. It exclusively references Windows-centric technologies such as DFSR, Active Directory, and Azure File Sync with Windows server endpoints. All step-by-step instructions and architectural recommendations are tailored to Windows environments, with no examples or guidance for Linux-based file servers. Windows tools and patterns (DFSR, SMB, AD) are mentioned first and exclusively, while Linux equivalents or considerations are absent.
Recommendations
  • Add explicit guidance and examples for protecting Linux-based file servers using Azure Site Recovery, including supported configurations and any required agents.
  • Include instructions for using Azure File Sync or alternative solutions with Linux endpoints, if supported, or clarify limitations.
  • Discuss Linux file sharing protocols (e.g., NFS, Samba) and how they can be protected or replicated in Azure environments.
  • Provide parity in step-by-step walkthroughs for Linux file servers, including failover and recovery procedures.
  • Mention cross-platform considerations for authentication and directory services (e.g., integration with LDAP or Azure AD for Linux).
GitHub Create Pull Request
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/deploy-vmware-azure-replication-appliance-modernized.md ...tps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/deploy-vmware-azure-replication-appliance-modernized.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in several areas. PowerShell is the only CLI method described for manual appliance setup, with no Linux shell or cross-platform alternatives. Registry and group policy checks are exclusively Windows-specific, and all examples for appliance configuration and troubleshooting reference Windows tools and patterns. There is no mention of Linux-based deployment or management steps, nor are Linux equivalents for core operations (such as shell scripts or configuration validation) provided. The order of presentation also places Windows-centric methods and requirements before any mention of Linux, which is only referenced in passing for VM credential requirements.
Recommendations
  • Provide Linux shell (bash) or cross-platform CLI examples for manual appliance setup, alongside PowerShell.
  • Document Linux-specific prerequisites, such as required packages, system settings, and configuration validation methods.
  • Include troubleshooting steps and checks for Linux environments, not just Windows registry and group policy.
  • Clarify whether the appliance can be deployed on Linux hosts, and if so, provide step-by-step instructions.
  • Ensure that examples and instructions for both Windows and Linux are presented in parallel, or explicitly state platform limitations.
  • Reference Linux tools (e.g., systemctl, journalctl, /etc configurations) where appropriate for monitoring and management.
GitHub Create Pull Request
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-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation page demonstrates a Windows bias in several ways. All detailed examples and walkthroughs focus exclusively on Windows VMs, with no Linux VM scenarios or examples provided. Windows-specific tools and concepts (e.g., diskmgmt.msc, drive letters, pagefile.sys, SQL Server on Windows, service console, screenshots of Windows dialogs) are used throughout, and instructions assume familiarity with Windows administration. Linux equivalents, such as handling swap partitions or tempdb on Linux, are not mentioned or illustrated. Although Linux is referenced briefly in a table, it is not covered in any practical example or guidance.
Recommendations
  • Add parallel examples for Linux VMs, including exclusion of swap disks/partitions and tempdb on SQL Server running on Linux.
  • Include instructions for disk management on Linux (e.g., using lsblk, parted, or fdisk) instead of only referencing diskmgmt.msc.
  • Provide guidance for managing SQL Server services and tempdb paths on Linux (e.g., using systemctl, editing configuration files).
  • Replace or supplement Windows-specific screenshots with Linux equivalents (e.g., screenshots of GNOME Disks, CLI output).
  • Clarify differences in failover and failback behavior for Linux VMs, including drive naming conventions and disk mounting.
  • Ensure that all steps and recommendations are applicable to both Windows and Linux environments, or clearly indicate when instructions are OS-specific.
GitHub Create Pull Request
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/how-to-enable-replication-proximity-placement-groups.md ...tps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/how-to-enable-replication-proximity-placement-groups.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page exhibits a strong Windows bias, primarily through its exclusive use of PowerShell for all CLI examples and automation, which is a Windows-centric tool. There are no Bash, Azure CLI, or Linux shell examples provided, and all scripting guidance assumes the reader is using PowerShell. The page also references Windows-specific concepts (e.g., Hyper-V, Windows VM OS types) before their Linux equivalents, and links to Windows-focused documentation (such as proximity placement groups under the Windows VM path). While Linux is mentioned (e.g., CentOS), there is no parity in example scripts or tooling for Linux users.
Recommendations
  • Add equivalent Azure CLI (az) and Bash script examples for all PowerShell commands, especially for VM replication and proximity placement group operations.
  • Include explicit instructions and code samples for Linux administrators, such as using Bash or shell scripts for automation.
  • Reference both Windows and Linux documentation paths equally, and avoid linking only to Windows-specific guides.
  • Clarify which steps or tools are cross-platform, and note any platform-specific limitations.
  • Where VM OS type is specified, provide examples for both Windows and Linux VMs, not just Windows.
  • Consider a section or callouts for Linux-specific considerations, especially for disaster recovery scenarios.
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-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates Windows bias by presenting Windows instructions, screenshots, and PowerShell examples before Linux equivalents. Windows-specific tools (diskpart, PowerShell, registry editing) are described in detail, with screenshots and step-by-step guidance, while Linux instructions are less visual and rely on generic bash commands. Some manual configuration steps for Windows (e.g., SAN policy, DHCP) are shown with explicit commands and screenshots, whereas Linux steps are described more abstractly, with fewer concrete examples and no screenshots. Windows troubleshooting links and references appear before Linux ones in some sections.
Recommendations
  • Provide Linux command-line examples for all manual steps, including network and disk configuration, similar to the detailed Windows PowerShell and diskpart instructions.
  • Include screenshots or terminal output for Linux steps, such as mounting partitions, editing fstab, and verifying agent installation.
  • Ensure troubleshooting links and references for Linux are presented with equal prominence and detail as Windows.
  • Add explicit bash or shell script snippets for common Linux distributions (e.g., Ubuntu, RHEL, SUSE) for steps like DHCP configuration, agent installation, and driver verification.
  • Balance the structure so that Linux and Windows instructions are presented in parallel, rather than Windows first, to avoid perceived prioritization.
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-09 00:34
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 references Windows-specific tools and APIs (e.g., VMM, Hyper-V Replica, Windows Management Instrumentation methods). There are no examples, mentions, or guidance for Linux-based hypervisors or VMs, nor are Linux tools, patterns, or equivalents discussed. The architecture, process, and troubleshooting sections all assume a Windows environment.
Recommendations
  • Add sections or links describing disaster recovery for Linux-based hypervisors (e.g., KVM, VMware on Linux) and Linux VMs.
  • Provide parity in examples and process descriptions for Linux environments, including agent installation, replication, and failover steps.
  • Mention Linux tools and patterns where relevant (e.g., how to replicate or recover Linux VMs, supported file systems, agent compatibility).
  • Clarify in the introduction that the guide is specific to Hyper-V/Windows, and link to Linux/other hypervisor documentation if available.
  • Include troubleshooting and monitoring guidance for Linux VMs, if supported by Azure Site Recovery.
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-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exhibits a Windows bias in several ways. Azure PowerShell is mentioned as the only CLI method for creating private endpoints, with no reference to Azure CLI or Linux shell examples. The URLs to be allowed are heavily Windows-centric (e.g., *.windows.net), and there is no mention of Linux-specific tools or commands throughout the step-by-step instructions. All screenshots and UI references are based on the Azure portal, which is platform-agnostic, but command-line automation is only shown for PowerShell, a Windows-first tool. There are no explicit Linux or cross-platform CLI examples, nor are there references to Linux patterns or tools for automation.
Recommendations
  • Add Azure CLI examples alongside PowerShell for all command-line instructions, especially for creating private endpoints.
  • Explicitly mention Linux support and provide Linux shell (bash) commands where automation is discussed.
  • Include references to Linux-based tools and workflows (e.g., using curl, jq, or bash scripts for DNS or network configuration).
  • Balance the documentation by listing Linux equivalents for any Windows-specific URLs, tools, or patterns.
  • Where screenshots are used, consider including terminal examples for both Windows (PowerShell) and Linux (bash/Azure CLI).
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-09 00:34
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 for Windows). Examples and instructions are provided only for Windows/PowerShell, with no mention of Linux equivalents, Linux-based hypervisors, or cross-platform scenarios. PowerShell is the only automation example given, and Windows terminology and patterns are used throughout, with no parity for Linux administrators.
Recommendations
  • Include explicit statements clarifying that Azure Site Recovery for Hyper-V is Windows-centric, and provide guidance or links for Linux-based disaster recovery scenarios (e.g., for KVM, VMware on Linux, or physical Linux servers).
  • Add Linux-based examples and instructions where relevant, such as automating with Azure CLI or REST API from Linux environments.
  • Mention Linux-compatible tools and patterns for replication, failover, and failback, or provide links to documentation for Linux disaster recovery with Azure Site Recovery.
  • Where PowerShell is referenced, also provide Azure CLI or Bash script equivalents for cross-platform automation.
  • Clarify prerequisites and supported platforms, including any support for Linux guest VMs or hosts, and provide a comparison table for Windows vs. Linux support.
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-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation is heavily oriented toward Windows environments, specifically Hyper-V and Windows-based Azure VMs. It references Windows-specific technologies (Hyper-V, System Center VMM), and links to Windows VM documentation (e.g., connecting to Azure VMs via Windows-specific guides). There are no examples or guidance for Linux-based Hyper-V VMs or for connecting to Linux VMs after failover. Linux tools and patterns are not mentioned.
Recommendations
  • Include explicit guidance and examples for Linux-based VMs running on Hyper-V, if supported by Azure Site Recovery.
  • When discussing connecting to failed-over VMs, provide links and instructions for both RDP (Windows) and SSH (Linux), including a link to the Linux VM connection documentation.
  • Avoid linking only to Windows-specific Azure documentation (e.g., /azure/virtual-machines/windows/connect-logon); instead, provide parallel links for Linux VMs (e.g., /azure/virtual-machines/linux/ssh-from-windows).
  • Clarify whether the procedures and requirements apply equally to Linux VMs, and note any differences.
  • If Linux VMs are not supported, explicitly state this to avoid ambiguity.
GitHub Create Pull Request
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/hyper-v-azure-troubleshoot.md ...n/articles/site-recovery/hyper-v-azure-troubleshoot.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation is heavily focused on Windows environments, specifically Hyper-V and related Microsoft tools. Troubleshooting steps, examples, and log locations are almost exclusively for Windows Server, Hyper-V Manager, PowerShell, and Windows event logs. Linux is mentioned only once, with no concrete troubleshooting steps or examples provided for Linux-based VMs. All command-line and GUI instructions use Windows tools, and PowerShell is the only scripting environment referenced.
Recommendations
  • Add equivalent troubleshooting steps for Linux-based VMs, including how to check replication health, VSS/app-consistent snapshot status, and service states on Linux.
  • Provide Linux command-line examples (e.g., using bash, systemctl, journalctl) for relevant operations such as checking service status, logs, and disk configuration.
  • Include guidance for collecting and analyzing logs on Linux systems, such as locations of relevant logs and recommended tools.
  • Mention Linux-specific limitations and requirements for Azure Site Recovery, and provide links to Linux documentation.
  • Ensure that troubleshooting steps are presented in a cross-platform manner, with parallel instructions for both Windows and Linux where applicable.
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-09 00:34
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 System Center Virtual Machine Manager. All examples, requirements, and supported scenarios are Windows-centric, with PowerShell and Windows tools mentioned as primary management options. Linux is only referenced as a guest OS, with no guidance for Linux-based Hypervisors or management tools. There are no Linux CLI or management examples, and Windows terminology and patterns are used exclusively.
Recommendations
  • Clarify early that Azure Site Recovery for Hyper-V is a Windows-centric solution, but provide links or references to equivalent disaster recovery solutions for Linux-based hypervisors (e.g., KVM, Xen) if available.
  • Include Linux CLI (az CLI) examples for deployment and management alongside PowerShell, where possible.
  • Mention and compare Linux-based management tools or processes for disaster recovery to Azure, if supported.
  • Add a section explicitly stating the lack of support for Linux-based Hyper-V hosts, and provide guidance for Linux admins on alternative approaches.
  • Ensure parity in documentation by listing Linux guest OS requirements and limitations with the same detail as Windows.
  • Where features or actions are only available via PowerShell, note if az CLI or REST API alternatives exist, and provide examples.
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-09 00:34
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 all examples, terminology, and tooling are specific to Windows environments. There is no mention of Linux-based virtualization solutions (such as KVM, VMware on Linux, or Xen), nor are there any examples or guidance for analyzing reports from non-Windows platforms. Windows-specific concepts (like VHD/VHDX, Hyper-V Replica Broker, and Windows file paths) are used throughout, with no Linux equivalents or cross-platform considerations.
Recommendations
  • Add sections or examples for analyzing deployment planner reports for Linux-based virtualization platforms (e.g., KVM, Xen, VMware on Linux).
  • Include Linux file path examples and terminology alongside Windows paths.
  • Reference Linux-compatible tools and commands for report generation and analysis.
  • Clarify whether the Deployment Planner supports non-Hyper-V environments, and if so, provide parity in documentation.
  • If the tool is Windows-only, explicitly state this limitation at the beginning of the documentation.
GitHub Create Pull Request
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/hyper-v-deployment-planner-overview.md ...s/site-recovery/hyper-v-deployment-planner-overview.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation for the Azure Site Recovery Deployment Planner for Hyper-V disaster recovery is heavily biased towards Windows environments. All examples, prerequisites, and operational instructions are centered on Windows Server (2012 R2, 2016), with explicit requirements for Windows-only tools (PowerShell, .NET Framework, Visual C++ Redistributable, Microsoft Excel). There are no Linux equivalents or instructions, and all command-line examples use PowerShell. The documentation does not mention or support running the tool from Linux or provide parity for Linux-based Hyper-V management.
Recommendations
  • Clearly state Windows-only support at the top of the documentation, if Linux is not supported.
  • If possible, provide Linux-compatible versions of the tool or clarify cross-platform limitations.
  • Add a section addressing Linux/Unix users, including any workarounds or alternatives for similar disaster recovery planning.
  • Include examples or notes for VMware environments that may be managed from Linux, if relevant.
  • If future support for Linux is planned, mention it and provide a roadmap or feedback channel.
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-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example Powershell Heavy
Summary
The documentation is heavily biased toward Windows environments, specifically Hyper-V. All examples use Windows-style paths (e.g., E:\), reference Windows tools (ASRDeploymentPlanner.exe), and mention using Notepad for file editing. There is no mention of Linux equivalents, nor are there any Linux/Unix command-line examples, file path formats, or tooling. The documentation assumes a Windows administrative context throughout, with no guidance for Linux users or cross-platform scenarios.
Recommendations
  • Provide explicit information about platform support (e.g., whether the tool runs on Linux, or only on Windows).
  • If Linux is supported, add Linux/Unix command-line examples, including path formats and file editing instructions (e.g., using nano or vi instead of Notepad).
  • Mention Linux equivalents for administrative tasks (e.g., using sudo, Linux file permissions, etc.).
  • Clarify any Windows-only requirements early in the documentation, and suggest alternatives or workarounds for Linux users if possible.
  • If the tool is Windows-only, add a note stating this limitation and suggest alternative planning tools for Linux environments.
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-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation focuses exclusively on Hyper-V, a Windows virtualization technology, and provides instructions only for excluding disks from replication in Hyper-V VMs. There are no examples, guidance, or mentions of equivalent Linux virtualization platforms (such as KVM or VMware on Linux), nor are Linux-specific tools or patterns discussed. The workflow and terminology are tailored to Windows environments, with no consideration for Linux administrators or cross-platform scenarios.
Recommendations
  • Add equivalent instructions for excluding disks from replication for Linux-based virtualization platforms (e.g., KVM, VMware on Linux).
  • Include examples and screenshots for Linux environments where possible.
  • Mention Linux-specific considerations, such as disk types and management tools.
  • Clarify in the introduction that the guidance is specific to Hyper-V/Windows, and provide links to documentation for Linux-based disaster recovery scenarios.
  • Ensure parity in terminology and workflow descriptions for both Windows and Linux users.
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-09 00:34
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, both of 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-specific examples or parity guidance for disaster recovery scenarios involving Linux VMs hosted on Hyper-V.
Recommendations
  • Add explicit guidance for preparing Linux VMs on Hyper-V for disaster recovery, including steps 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 SSH connectivity and relevant diagnostics.
  • Mention that Hyper-V can host Linux VMs and provide links to official documentation for supported Linux distributions and their requirements.
  • Where instructions reference Windows tools (e.g., RDP, Windows Firewall), add equivalent Linux instructions (e.g., SSH, iptables/ufw/firewalld).
  • Clarify that the guidance applies to both Windows and Linux VMs where relevant, or specify when steps are Windows-specific.
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-09 00:34
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-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 terminology, examples, and workflows assume a Windows-centric infrastructure, with no mention of Linux equivalents or cross-platform considerations.
Recommendations
  • Add a section describing how network mapping and disaster recovery can be performed for Linux-based hypervisors (e.g., KVM, Xen) or with Azure Site Recovery in Linux environments.
  • Provide examples and tables that include Linux VM network mapping scenarios, or clarify if Azure Site Recovery supports only Windows/Hyper-V environments.
  • Explicitly state platform limitations and offer links to Linux-specific disaster recovery documentation if available.
  • If possible, mention open-source or cross-platform tools that can be used for similar network mapping and failover tasks in Linux environments.
GitHub Create Pull Request
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/monitor-log-analytics.md ...b/main/articles/site-recovery/monitor-log-analytics.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 in several areas. The section on configuring the Microsoft monitoring agent for churn and upload rate logs exclusively details steps for Windows Servers, including downloading the Windows Agent and configuring Windows Performance Counters. There is no mention of Linux equivalents, nor are Linux-specific instructions or examples provided. The screenshots and step-by-step instructions focus solely on Windows environments, and Linux monitoring agent setup is omitted. This may hinder Linux users from achieving parity in monitoring scenarios.
Recommendations
  • Add explicit instructions for installing and configuring the monitoring agent on Linux servers, including download links, workspace configuration, and performance counter setup.
  • Include Linux-specific examples and screenshots for configuring diagnostic settings and performance counters.
  • Clarify whether churn and upload rate monitoring is supported on Linux, and if so, provide equivalent steps and queries.
  • Ensure that references to 'Windows Servers' are balanced with 'Linux Servers' where applicable, and avoid presenting Windows steps first or exclusively.
  • Provide troubleshooting tips and common issues for Linux environments alongside Windows.
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-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page, while stating support for both Windows and Linux physical servers, demonstrates Windows bias in several areas. Windows-specific instructions (such as registry edits and CLI commands) are provided in detail, while Linux instructions are minimal or generic (e.g., 'use root account'). Windows tools and patterns (registry, domain/local accounts) are mentioned explicitly, and Windows configuration steps are described before Linux equivalents. There are no concrete Linux command examples or troubleshooting steps, and Windows terminology is used more frequently.
Recommendations
  • Provide equivalent Linux-specific instructions and examples, such as commands for preparing the Linux server for Mobility service installation (e.g., required packages, SELinux/AppArmor settings, firewall rules).
  • Include Linux troubleshooting steps (e.g., log file locations, systemd service status checks) alongside Windows registry and account configuration.
  • Explicitly mention Linux prerequisites, such as supported distributions, kernel versions, and required dependencies.
  • Balance the order of presentation so that Linux and Windows steps are described in parallel, or clearly separated, rather than Windows-first.
  • Add screenshots or CLI output examples for Linux where Windows screenshots or commands are shown.
GitHub Create Pull Request
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/physical-manage-configuration-server.md .../site-recovery/physical-manage-configuration-server.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 towards Windows environments. All prerequisites, installation steps, and command-line examples assume Windows Server as the operating system. There are no references to Linux support or examples. Windows-specific tools (Control Panel, PowerShell, registry editing, Windows services) are used throughout, and PowerShell commands are provided for key operations without any Linux shell equivalents. The documentation does not mention or provide guidance for deploying or managing the configuration server on Linux systems.
Recommendations
  • Explicitly state OS support: Clarify whether Linux is supported for the configuration server, and if not, explain why.
  • Add Linux prerequisites: If Linux is supported, include Linux OS versions and requirements in the prerequisites table.
  • Provide Linux installation steps: Add instructions for downloading, installing, and registering the configuration server on Linux, including relevant shell commands.
  • Include Linux command-line examples: Offer bash or shell script equivalents for all PowerShell commands and registry edits.
  • Reference Linux tools: Where Windows tools (Control Panel, registry, services) are mentioned, provide Linux alternatives (e.g., systemctl, config files).
  • Balance examples: Present both Windows and Linux examples side-by-side where applicable, or clearly indicate platform-specific steps.
GitHub Create Pull Request
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/physical-to-azure-failover-failback.md ...s/site-recovery/physical-to-azure-failover-failback.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing Windows-specific features (such as availability sets with a Windows URL), mentioning Windows operating systems before Linux in multi-VM consistency instructions, and listing Windows Server 2008 R2 SP1 as a specific unsupported failback scenario. There are no explicit Linux or cross-platform command examples, and no Linux-specific instructions or considerations are provided. The documentation assumes familiarity with Windows-centric concepts and tools, while Linux parity is not addressed.
Recommendations
  • Add explicit Linux examples and instructions where relevant, such as connecting to Azure VMs after failover or configuring network settings.
  • Reference both Windows and Linux documentation links for features like availability sets and VM requirements.
  • List Linux operating systems alongside Windows in all relevant instructions, and provide parity in troubleshooting and unsupported scenarios.
  • Include cross-platform automation examples (e.g., Bash scripts) in addition to or instead of Windows-centric approaches.
  • Clarify any differences in failover/failback behavior or requirements for Linux physical servers.
GitHub Create Pull Request
← Previous Page 12 of 35 Next →