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 126-150 of 864 flagged pages
Site Recovery Prepare VMware VMs for reprotection and failback with Azure Site Recovery ...rticles/site-recovery/vmware-azure-prepare-failback.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Windows Heavy Examples
Summary
The documentation page demonstrates a Windows bias by frequently referencing Windows components and patterns first, such as the default master target server being Windows, and providing more detailed steps for Windows (e.g., retention drive setup). Windows terminology and tools (e.g., default retention volume 'R', Windows master target server) are mentioned before their Linux equivalents, and some instructions are more elaborate for Windows than Linux. Linux options are present but less emphasized and sometimes only referenced via links.
Recommendations
  • Present Linux and Windows options with equal prominence and detail in all sections, including setup and configuration steps.
  • Where possible, provide side-by-side examples or tables for both Windows and Linux, rather than referencing Linux as an alternative or via external links.
  • Ensure that instructions for Linux (e.g., retention drive setup, master target server creation) are as detailed and explicit as those for Windows.
  • Avoid language that implies Windows is the default or preferred option; instead, clarify that both Windows and Linux are supported and provide guidance for choosing between them.
  • Include troubleshooting and requirements sections for Linux with the same depth as those for Windows.
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-11 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 strong Windows bias. Windows-specific tools (PowerShell, DISM, reg.exe, net.exe, CSPSConfigtool.exe, genpassphrase.exe) are referenced throughout, often without Linux equivalents or alternatives. Command-line examples and administrative instructions are almost exclusively for Windows environments, with PowerShell commands provided for server management and deletion. The update and license management sections focus on Windows licensing and tools. There are no Linux shell (bash) examples, nor guidance for managing configuration servers deployed on Linux, even though Azure Site Recovery supports Linux physical servers.
Recommendations
  • Provide equivalent Linux command-line examples (bash, shell scripts) for all administrative tasks currently shown only with Windows tools or PowerShell.
  • Include instructions for updating and managing configuration servers running on Linux, including license management, certificate renewal, and server registration.
  • Reference Linux tools (e.g., systemctl, openssl, relevant config file paths) alongside Windows tools where applicable.
  • Clarify which steps are Windows-only and which apply to Linux, and add Linux-specific guidance where missing.
  • Ensure parity in troubleshooting and automation guidance for both Windows and Linux environments.
GitHub Create Pull Request
Site Recovery Automate Mobility Service for disaster recovery of installation in Azure Site Recovery ...ery/vmware-azure-mobility-install-configuration-mgr.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. Windows tools and patterns (such as Configuration Manager, administrative command prompt, and .bat scripts) are mentioned first and in more detail. The instructions and screenshots are primarily oriented toward Windows environments, with Linux guidance provided but often as a secondary consideration. Some steps (e.g., generating the passphrase file) use Windows-specific commands without clear Linux alternatives, and the overall workflow assumes familiarity with Windows tooling.
Recommendations
  • Provide equivalent Linux-native instructions for all steps, including generating the passphrase file and managing installation files.
  • Include Linux command-line examples and screenshots where appropriate, not just Windows.
  • Mention cross-platform or Linux-first deployment tools (e.g., Ansible, Puppet, Chef) alongside or before Windows-centric tools like Configuration Manager.
  • Ensure that Linux instructions are not always presented after Windows instructions; consider parallel presentation or Linux-first sections where appropriate.
  • Clarify any steps that are Windows-only and provide explicit Linux alternatives or workarounds.
  • Expand the troubleshooting and uninstallation sections to include Linux examples, not just Windows batch scripts.
GitHub Create Pull Request
Site Recovery Set up a process server VMware/physical failback in Azure Site Recovery ...e-recovery/vmware-azure-set-up-process-server-azure.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Missing Linux Example 🔧 Windows Tools Windows First
Summary
The documentation page focuses exclusively on deploying a process server VM in Azure for VMware/physical failback, but all references to OS, credentials, and admin permissions implicitly assume a Windows environment. There are no examples or instructions for deploying a Linux-based process server, nor are Linux-specific tools or patterns mentioned. The process server registration and deployment steps do not clarify OS options or provide parity for Linux users.
Recommendations
  • Explicitly state whether Linux is supported for the process server VM, and if so, provide step-by-step instructions for deploying a Linux-based process server.
  • Include examples of setting up credentials and admin permissions for both Windows and Linux VMs.
  • Mention Linux tools or commands (e.g., SSH, sudo) where relevant, alongside Windows equivalents.
  • Add screenshots or CLI examples for Linux VM deployment in Azure.
  • Clarify any OS-specific requirements or limitations for the process server role.
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-11 00:00
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 installation patterns (e.g., UnifiedSetup.exe, .exe installers, Windows-style file paths), and providing only Windows command-line examples. There is no mention of Linux equivalents, nor are Linux installation instructions or examples provided. The documentation implicitly assumes the process server is deployed on Windows, with no guidance for Linux users.
Recommendations
  • Provide explicit instructions and examples for installing and configuring the process server on Linux systems, if supported.
  • Include Linux command-line examples (e.g., using shell scripts, .sh installers, Linux file paths) alongside Windows examples.
  • Clarify platform support early in the documentation, and if Linux is not supported, state this clearly to avoid confusion.
  • If Linux is supported, mention Linux prerequisites and dependencies in the sizing and prerequisites sections.
  • Ensure parity in troubleshooting and configuration guidance for both Windows and Linux environments.
GitHub Create Pull Request
Site Recovery Set up source settings for VMware disaster recovery to Azure with Azure Site Recovery ...n/articles/site-recovery/vmware-azure-set-up-source.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by prioritizing Windows-specific instructions and tools. Most examples and folder paths for antivirus exclusions are Windows-centric (e.g., C:\ProgramData\ASR), with Linux instructions appearing only at the end and in less detail. Registry exclusions are mentioned only for Windows, and there are no PowerShell or Linux shell command examples. The configuration server setup references Windows licensing, implying a Windows OS, and does not clarify Linux alternatives or parity.
Recommendations
  • Provide Linux-specific setup instructions and examples alongside Windows steps, especially for configuration server deployment.
  • Include Linux shell command examples for relevant steps, such as folder exclusions or service registration.
  • List Linux antivirus exclusion paths before or alongside Windows paths, not after.
  • Clarify whether the configuration server can run on Linux, and if so, provide licensing and installation details for Linux.
  • Add registry exclusion equivalents for Linux (if applicable), or clarify their absence.
  • Ensure all steps and examples are presented in a cross-platform manner, with equal detail for both Windows and Linux environments.
GitHub Create Pull Request
Site Recovery Troubleshoot issues with the configuration server during disaster recovery of VMware VMs and physical servers to Azure by using Azure Site Recovery ...very/vmware-azure-troubleshoot-configuration-server.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation page exhibits a Windows bias in several ways: Windows paths, tools, and troubleshooting steps are presented first or exclusively in most sections. Windows-specific tools (e.g., PsExec, Internet Explorer) are referenced without Linux equivalents. Some troubleshooting steps and log file locations are only described for Windows, with Linux guidance appearing later or not at all. Powershell and Windows command-line examples are more detailed and prevalent than Linux shell equivalents.
Recommendations
  • Ensure Linux troubleshooting steps are presented alongside Windows steps, not only after or as an afterthought.
  • Provide Linux equivalents for all Windows-specific tools and actions (e.g., suggest Linux alternatives to PsExec, Internet Explorer, and Windows service management).
  • Include Linux log file locations and commands wherever Windows paths are mentioned.
  • Balance command examples by giving equal detail and prominence to Linux shell commands and procedures.
  • Avoid referencing Windows-only utilities (such as Internet Explorer or PsExec) without noting Linux alternatives or stating their lack of applicability.
  • Where service management is discussed, provide systemd or init-based instructions for Linux.
  • Review sections for implicit assumptions of Windows environments and clarify applicability to Linux systems.
GitHub Create Pull Request
Site Recovery Troubleshoot Mobility Service push installation with Azure Site Recovery ...ite-recovery/vmware-azure-troubleshoot-push-install.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in several ways: Windows troubleshooting steps, tools, and registry modifications are presented first and in greater detail; Windows-specific tools (e.g., regedit, netsh, net user, File Explorer, Task Manager, Group Policy) are referenced without Linux equivalents; PowerShell and command prompt examples are given for Windows, while Linux commands are less frequent and less detailed; some troubleshooting sections (e.g., VSS errors, WMI, network shares) focus almost exclusively on Windows, with minimal or missing Linux guidance.
Recommendations
  • Ensure Linux troubleshooting steps are presented alongside Windows steps, with equal detail and prominence.
  • Provide Linux equivalents for all Windows tools and commands (e.g., registry edits, service management, file sharing, driver checks).
  • Include Linux-specific error codes and logs, and reference common Linux troubleshooting tools (e.g., systemctl, journalctl, sshd, Samba).
  • Add examples for managing user accounts, permissions, and services on Linux (e.g., usermod, systemctl start/enable, chown/chmod).
  • Where screenshots or UI instructions are given for Windows (e.g., File Explorer), provide CLI or GUI alternatives for Linux.
  • Review all sections for parity, ensuring Linux users have clear, actionable steps for each error scenario.
GitHub Create Pull Request
Site Recovery Troubleshoot replication issues for disaster recovery of VMware virtual machines and physical servers to Azure by using Azure Site Recovery ...site-recovery/vmware-azure-troubleshoot-replication.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page shows a Windows bias by exclusively referencing Windows file paths (e.g., C:\Program Files, C:\ProgramData), Windows-specific folders (e.g., %PROGRAMDATA%), and Windows command-line tools (cmd, net stop/start). There are no Linux-specific troubleshooting steps, file paths, or command examples, despite the fact that physical servers could be running Linux. All examples and instructions assume a Windows environment, and there is no mention of Linux equivalents or parity.
Recommendations
  • Add Linux-specific troubleshooting instructions, including file paths (e.g., /var/log/...), service management commands (systemctl, service), and agent locations.
  • Provide command-line examples for both Windows (cmd/PowerShell) and Linux (bash/shell) where relevant.
  • Explicitly state which steps apply to Windows, Linux, or both, and clarify any OS-specific requirements.
  • Include guidance for setting permissions on Linux (e.g., chown, chmod) alongside Windows ACL instructions.
  • Reference Linux tools and patterns (e.g., journalctl, systemctl) for monitoring and troubleshooting services.
GitHub Create Pull Request
Site Recovery Troubleshoot VMware vCenter discovery failures in Azure Site Recovery ...tps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/vmware-azure-troubleshoot-vcenter-discovery-failures.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Windows tools (PsExec, Internet Explorer, command prompt), providing step-by-step instructions that assume a Windows environment, and omitting any Linux equivalents or examples. All troubleshooting steps and commands are tailored for Windows users, with no mention of how to perform these tasks on Linux-based configuration servers or environments.
Recommendations
  • Include Linux-specific troubleshooting steps and examples, such as using Linux command-line tools to check and modify proxy settings.
  • Provide alternatives to PsExec for Linux (e.g., using sudo or su to access root/system context).
  • Replace or supplement Internet Explorer instructions with guidance for configuring proxy settings on Linux (e.g., editing /etc/environment or using network manager tools).
  • Add instructions for restarting relevant services on Linux (e.g., using systemctl or service commands).
  • Ensure parity by listing both Windows and Linux procedures side-by-side, or clearly indicating which steps apply to each platform.
GitHub Create Pull Request
Site Recovery Prepare for VMware VM disaster recovery with Azure Site Recovery ...-recovery/vmware-azure-tutorial-prepare-on-premises.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by consistently presenting Windows instructions and tools before Linux equivalents, providing more detailed steps for Windows (such as registry edits and firewall configuration), and referencing Windows-specific tools and settings (e.g., Windows Firewall, SAN policy, Boot diagnostics for Windows). Linux instructions are present but less detailed, and there are missing Linux-specific troubleshooting examples and parity in guidance.
Recommendations
  • Present Linux and Windows instructions in parallel, giving equal detail and prominence to both.
  • Include Linux-specific troubleshooting steps and examples, such as common SSH connection issues, SELinux/AppArmor considerations, and log file locations.
  • Reference Linux firewall tools (e.g., iptables, firewalld, ufw) when discussing firewall configuration for SSH.
  • Provide explicit guidance for Linux VM preparation, such as required packages, recommended user/group permissions, and systemd service checks.
  • Add parity in Boot diagnostics troubleshooting for Linux VMs, including links to relevant documentation.
  • Avoid using Windows terminology (e.g., 'Windows Firewall', 'SAN policy') without Linux equivalents or explanations.
GitHub Create Pull Request
Site Recovery Support matrix for VMware/physical disaster recovery in Azure Site Recovery. .../site-recovery/vmware-physical-azure-support-matrix.md
High Priority View Details →
Scanned: 2026-01-11 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 several signs of Windows bias. Windows and PowerShell are mentioned first or exclusively in deployment scenarios and tooling. The replication appliance setup is described only with a PowerShell script for physical servers, with no Linux equivalent or example. The appliance itself requires Windows Server and Windows-specific roles and settings, with no mention of Linux-based alternatives. Many operational details (such as disk management, storage, and networking) reference Windows features and tools before or instead of Linux equivalents. There are no Linux shell or automation examples, and guidance for Linux users is limited to compatibility lists and requirements, not operational instructions.
Recommendations
  • Provide Linux-based deployment and management examples, such as Bash scripts or CLI commands, alongside PowerShell.
  • Document any Linux-compatible alternatives for the replication appliance, or clarify if Windows Server is a hard requirement.
  • Include Linux-first or parallel examples for operational tasks (e.g., disk management, agent installation, network configuration).
  • Reference Linux tools and patterns (such as systemd, SELinux, iptables, etc.) where relevant, not just Windows roles and group policies.
  • Ensure that Linux-specific troubleshooting and configuration steps are as detailed as Windows equivalents.
  • Explicitly state when features are Windows-only, and offer guidance or workarounds for Linux users where possible.
GitHub Create Pull Request
Site Recovery Deprecation of classic experience to protect VMware and physical machines using Azure Site Recovery | Microsoft Docs ...-recovery/vmware-physical-azure-classic-deprecation.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page references PowerShell as a method for enabling replication, with explicit mention that PowerShell access will be blocked after a certain date. There are no equivalent Linux command-line tools or examples (such as Bash, CLI, or Linux-native automation) mentioned. The page also lacks any Linux-specific migration steps or parity in tooling, despite referencing support for new Linux distros in the modernized experience.
Recommendations
  • Include Linux CLI (az CLI, Bash) examples for migration and management alongside PowerShell references.
  • Explicitly mention Linux-native tools or automation options for managing Azure Site Recovery, where applicable.
  • Provide parity in step-by-step instructions for both Windows and Linux administrators, especially for tasks like enabling replication, managing vaults, and triggering migration.
  • Clarify whether any features or steps are Windows-only, and offer Linux alternatives or workarounds where possible.
GitHub Create Pull Request
Site Recovery Scale VMware/physical disaster recovery with Azure Site Recovery ...cles/site-recovery/vmware-physical-large-deployment.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates Windows bias in several ways: PowerShell is the only automation example provided for triggering failover, Windows compliance is discussed in detail while Linux is mentioned only briefly, and troubleshooting/failover preparation steps are Windows-centric. There are no Linux command-line examples or equivalent tooling references, and Windows patterns (such as compliance checks and automation) are described before or instead of Linux equivalents.
Recommendations
  • Provide Linux CLI examples (e.g., Azure CLI, Bash scripts) for key operations such as triggering failover, monitoring, and automation.
  • Include detailed steps for preparing Linux machines for failover, similar to the Windows compliance section.
  • Reference Linux tools and patterns (e.g., cloud-init, systemd services) where relevant, and describe how to automate tasks for Linux workloads.
  • Ensure troubleshooting and compliance guidance covers Linux scenarios with equal depth and clarity.
  • Present Windows and Linux instructions side-by-side or in parallel sections to avoid Windows-first ordering.
GitHub Create Pull Request
Site Recovery Manage the Mobility agent for VMware/physical servers with Azure Site Recovery ...te-recovery/vmware-physical-manage-mobility-service.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by providing PowerShell script examples only for Windows, listing Windows uninstall instructions before Linux, and referencing Windows-specific tools (Control Panel, MsiExec.exe, VSS provider scripts) without equivalent Linux details or parity. Linux instructions are present but less detailed and appear after Windows instructions, and there is no Linux automation example comparable to the PowerShell script.
Recommendations
  • Provide equivalent Linux automation examples, such as bash scripts for agent update and management.
  • Present Windows and Linux instructions in parallel sections or with equal prominence, rather than listing Windows first.
  • Include Linux-specific tools and patterns (e.g., systemd service management, package managers) where relevant.
  • Expand manual update instructions for Linux to match the detail level of Windows, including troubleshooting steps.
  • Add guidance for updating the Mobility service on Linux using command-line automation or configuration management tools.
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 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First Missing Linux Example
Summary
The documentation is heavily oriented toward Windows environments: all troubleshooting steps, logs, service names, and tool usage (e.g., Telnet, Task Manager, Resource Monitor, Control Panel, registry edits) are Windows-specific. There are no Linux equivalents or examples provided, despite the process server supporting replication for physical servers and VMware VMs, which may run Linux. The documentation assumes the process server and source machines are Windows, omitting guidance for Linux-based deployments.
Recommendations
  • Add Linux-specific troubleshooting steps, including log file locations, relevant services/daemons, and commands (e.g., systemctl, journalctl, netstat, lsof, tail).
  • Provide Linux equivalents for tools mentioned, such as using nc or curl instead of Telnet, and top/htop/iotop for performance monitoring.
  • Include examples for checking firewall rules and proxy settings on Linux (e.g., iptables, firewalld, ufw, /etc/environment, /etc/proxy.conf).
  • Document how to verify process server health and connectivity on Linux, including service management and log analysis.
  • Explicitly state which steps are OS-specific and provide parallel instructions for both Windows and Linux environments.
  • Reference Linux documentation for time synchronization (e.g., chrony, ntpd) instead of only linking to Windows Time Service.
GitHub Create Pull Request
Site Recovery About the Mobility service for disaster recovery of VMware VMs and physical servers with Azure Site Recovery | Microsoft Docs ...-recovery/vmware-physical-mobility-service-overview.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 5 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Windows Path Examples Windows-Centric Instructions
Summary
The documentation demonstrates a Windows bias in several ways: Windows installation instructions and examples are consistently presented before Linux equivalents, with Windows-specific tools, paths, and UI screenshots dominating the walkthroughs. Linux instructions are present and reasonably detailed, but often follow after Windows steps, and some directory references (e.g., installer repository paths) use Windows conventions even when describing Linux agent deployment. UI and command-line examples default to Windows, and troubleshooting or configuration steps frequently reference Windows tools and locations first.
Recommendations
  • Present Linux and Windows instructions side-by-side or in parallel sections, rather than always listing Windows first.
  • Use OS-neutral language and directory paths when describing steps that apply to both platforms (e.g., use <InstallLocation> or platform-specific examples).
  • Include Linux screenshots and UI walkthroughs where applicable, not just Windows.
  • Ensure troubleshooting and configuration guidance includes Linux-specific details and references, not just Windows paths or tools.
  • Add explicit parity checks to ensure all Windows examples have corresponding Linux instructions, and vice versa.
  • Consider a summary table or quickstart guide that highlights both Windows and Linux installation flows equally.
GitHub Create Pull Request
Site Recovery Troubleshoot VMware replication appliance health issues in Azure Site Recovery ...recovery/vmware-troubleshoot-appliance-health-issue.md
High Priority View Details →
Scanned: 2026-01-11 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 page demonstrates a Windows bias by providing troubleshooting steps that exclusively use PowerShell commands and Windows file paths. All examples and instructions reference Windows tools (e.g., PowerShell, Microsoft Azure Appliance Configuration Manager) without mentioning Linux equivalents or offering alternative steps for Linux-based environments. There are no Linux shell commands or guidance for non-Windows administrators, and the troubleshooting workflow assumes a Windows operating system.
Recommendations
  • Include Linux-specific troubleshooting steps and examples, such as Bash commands and Linux file paths.
  • Mention whether the replication appliance supports Linux and clarify any OS-specific limitations.
  • Provide parity in instructions for both Windows and Linux environments, ensuring administrators on either platform can follow the guidance.
  • Reference Linux tools or scripts where applicable, and offer alternative methods for certificate renewal and error resolution on Linux.
  • Add notes or sections that explicitly address Linux users and their troubleshooting process.
GitHub Create Pull Request
Site Recovery Troubleshoot VMware mobility agent health errors in Azure Site Recovery ...-recovery/vmware-troubleshoot-mobility-agent-health.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates Windows bias by listing Windows file paths before Linux equivalents, referencing Windows-specific services and tools (such as 'Microsoft Azure RCM Proxy Agent'), and omitting Linux-specific troubleshooting steps or service names. There are no Linux command examples or references to Linux service management, and the troubleshooting instructions focus on Windows-centric patterns.
Recommendations
  • Present Linux and Windows paths/examples in parallel, or alternate which is listed first.
  • Include Linux-specific service names and commands (e.g., systemctl, service) for restarting relevant services.
  • Add troubleshooting steps tailored for Linux environments, such as checking system logs, using journalctl, or verifying service status.
  • Reference Linux tools (such as curl, systemctl) explicitly where Windows tools/services are mentioned.
  • Ensure parity in error message analysis, showing how to interpret and resolve issues on both platforms.
GitHub Create Pull Request
Site Recovery Delete an Azure Site Recovery vault ...-docs/blob/main/articles/site-recovery/delete-vault.md
High Priority View Details →
Scanned: 2026-01-10 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 page demonstrates a Windows bias by providing only PowerShell examples for vault deletion, referencing Windows-centric tools (Hyper-V, VMM), and omitting equivalent Linux CLI or automation examples. The PowerShell method is presented as the sole scripting approach, with no mention of Azure CLI or Bash alternatives, which are more common in Linux environments.
Recommendations
  • Add Azure CLI examples for vault deletion alongside PowerShell, showing parity for Linux users.
  • Include references to Bash scripting and Linux automation patterns where appropriate.
  • Mention cross-platform tools and approaches before or alongside Windows-specific ones.
  • Clarify which steps or tools are applicable to both Windows and Linux environments.
  • Provide links to Linux-focused documentation or guides for managing Azure Site Recovery vaults.
GitHub Create Pull Request
Site Recovery Connect to Azure VMs on-premises failover with Azure Site Recovery ...e-recovery/concepts-on-premises-to-azure-networking.md
High Priority View Details →
Scanned: 2026-01-10 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 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 references. Windows tools and patterns (RDP, WinHTTP proxy, Windows updates, Windows Firewall) are mentioned exclusively or before Linux equivalents, and remote access setup is described only for Windows (RDP) with no SSH configuration guidance for Linux.
Recommendations
  • Expand the Linux section to include detailed steps for preparing Linux machines, such as configuring SSH, managing firewall rules (e.g., using ufw, firewalld, or iptables), and handling common Linux networking settings.
  • Provide example commands for Linux (e.g., systemctl enable ssh, firewall-cmd/ufw rules) similar to the PowerShell examples given for Windows.
  • Include troubleshooting tips for Linux connectivity issues after failover, such as SELinux/AppArmor considerations, SSH key management, and package updates.
  • Add links to relevant Azure documentation for Linux VM preparation, remote access, and firewall configuration.
  • Ensure parity in describing remote access: mention both RDP (Windows) and SSH (Linux) in all relevant sections, and clarify how to enable/configure each.
  • Avoid listing Windows instructions before Linux unless contextually necessary; consider parallel structure for both OS types.
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-10 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-centric technologies, specifically Hyper-V and System Center VMM, with no mention of Linux-based hypervisors or disaster recovery scenarios for Linux VMs. All examples, tools, and architectural components are Windows-specific, and Windows terminology and references (such as PowerShell cmdlets, Windows URLs, and Hyper-V Replica logs) are used exclusively. There are no Linux equivalents or cross-platform guidance provided.
Recommendations
  • Add sections or references for disaster recovery architectures involving Linux-based hypervisors (e.g., KVM, VMware on Linux) and Linux VMs.
  • Provide parity by including Linux-specific examples, tools, and processes for replication and failover to Azure.
  • Mention cross-platform alternatives and clarify which steps are Windows-specific versus generally applicable.
  • Include links to documentation for Linux VM disaster recovery in Azure Site Recovery, if available.
  • Explicitly state the scope of the documentation (e.g., 'This article applies only to Hyper-V on Windows') to avoid confusion for Linux users.
GitHub Create Pull Request
Site Recovery Set up the configuration server for disaster recovery of physical servers to Azure using Azure Site Recovery ...articles/site-recovery/physical-azure-set-up-source.md
High Priority View Details →
Scanned: 2026-01-10 00:00
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 referencing Windows-specific tools and requirements (such as .NET Framework, TLS settings, and Windows Time Service) without providing equivalent guidance for Linux environments. There are no Linux-specific setup instructions or troubleshooting steps, and all examples and notes assume a Windows host for the configuration server.
Recommendations
  • Include explicit instructions for setting up the configuration server on Linux, if supported, or clearly state if only Windows is supported.
  • Provide Linux equivalents for prerequisites, such as required packages, time synchronization methods (e.g., using ntpd or chrony), and any dependencies analogous to .NET Framework.
  • Add command-line installation and troubleshooting examples for Linux environments.
  • Ensure that screenshots and step-by-step instructions are platform-agnostic or provide parallel Linux examples where applicable.
  • Clarify in the prerequisites section whether the configuration server must run on Windows, and if so, explain the rationale.
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-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation is heavily focused on Windows environments, specifically Hyper-V and related Windows Server components. Troubleshooting steps, examples, and tool references are almost exclusively for Windows, with PowerShell commands and Windows GUI instructions given throughout. Linux is mentioned only briefly and without concrete troubleshooting steps or examples, and there are no Linux-specific tool or log references. Windows tools and patterns (Event Viewer, Resource Monitor, diskmgmt.msc, PowerShell) are used exclusively.
Recommendations
  • Add equivalent troubleshooting steps and examples for Linux-based VMs, including log locations, commands, and common errors.
  • Include Linux command-line examples (e.g., using journalctl, systemctl, or relevant Linux tools) for checking services, VSS equivalents, and integration services.
  • Provide parity in log collection instructions for Linux environments, referencing appropriate Linux logs and diagnostic tools.
  • Explicitly mention differences in troubleshooting between Windows and Linux, and provide links to Linux-specific documentation where available.
  • Ensure that Linux examples are presented alongside Windows examples, not only as a footnote or afterthought.
GitHub Create Pull Request
Site Recovery Set up failover of Hyper-V VMs to Azure in Azure Site Recovery ...e-recovery/hyper-v-azure-failover-failback-tutorial.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation is heavily focused on Hyper-V, a Windows-centric virtualization platform, and references Windows-specific tools and patterns (e.g., Remote Desktop Protocol, System Center VMM, Windows VM connection guides). There are no Linux-specific examples, instructions, or references to Linux-based hypervisors or management tools. The connection instructions and links prioritize Windows VM scenarios, and Linux failover or recovery patterns are not mentioned.
Recommendations
  • Include equivalent instructions and examples for Linux-based hypervisors (e.g., KVM, Xen) where Azure Site Recovery supports them.
  • Provide connection instructions for Linux VMs, such as SSH access, with direct links to Linux VM documentation.
  • Reference Linux management tools or patterns alongside System Center VMM, or clarify the scope if only Hyper-V is supported.
  • Add troubleshooting steps and validation instructions specific to Linux VMs after failover.
  • Explicitly state platform limitations or supported scenarios to avoid implying Windows-only support if Linux is not supported.
GitHub Create Pull Request
← Previous Page 6 of 35 Next →