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 226-250 of 864 flagged pages
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-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 exhibits a Windows bias by prioritizing Windows-specific instructions, tools, and examples. It frequently references Windows command-line utilities (e.g., PowerShell, DISM, net commands), Windows file paths, and Windows-centric procedures (such as updating Windows licenses and using .exe tools). PowerShell is the only scripting example provided for server management and deletion tasks. There are no equivalent Linux instructions, shell commands, or examples for managing configuration servers deployed on Linux, nor is there guidance for Linux-based environments where applicable.
Recommendations
  • Provide equivalent Linux instructions and examples for all management tasks, including command-line operations, file paths, and credential management.
  • Include Linux shell (bash) commands alongside PowerShell examples, especially for tasks like certificate renewal, server registration, and deletion.
  • Mention Linux tools and patterns (e.g., systemctl, openssl, bash scripts) where applicable, and clarify which procedures are OS-specific.
  • Add guidance for updating licenses and managing configuration servers on Linux, if supported.
  • Clearly indicate OS requirements and support in each section, and 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-10 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 Windows bias by consistently presenting Windows tools and workflows first, relying heavily on Microsoft Configuration Manager (a Windows-centric tool), and providing more detailed, step-by-step instructions and screenshots for Windows environments. Linux instructions are present but less emphasized, and there is a lack of parity in tooling recommendations and visual aids for Linux deployments.
Recommendations
  • Present Linux and Windows instructions in parallel, or alternate which OS is presented first in each section to avoid the impression of Windows being the default.
  • Include Linux-native deployment tool examples (e.g., Ansible, Puppet, Chef, or native package managers) alongside Configuration Manager, with equal detail and prominence.
  • Provide equivalent screenshots and visual aids for Linux deployment steps, not just for Windows/Configuration Manager.
  • Expand the 'Automated deployment' section to mention and link to Linux-focused automation tools and best practices.
  • Ensure that all code samples, troubleshooting steps, and uninstall instructions are provided for both Windows and Linux, with equal clarity and completeness.
  • Avoid using Windows-specific terminology (e.g., 'administrative command prompt', 'SMB share') without also providing Linux equivalents (e.g., 'root shell', 'NFS share').
GitHub Create Pull Request
Site Recovery Prepare source machines to install the Mobility Service through push installation for disaster recovery of VMware VMs and physical servers to Azure ...site-recovery/vmware-azure-install-mobility-service.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation presents Windows instructions before Linux, with detailed steps involving Windows-specific tools (e.g., registry edits, firewall UI, Group Policy Objects). Windows ports (SMB, WMI) are listed in the note section without Linux equivalents. The CSPSConfigtool is referenced as a Windows executable (.exe) for both platforms, but Linux-specific usage or alternatives are not described. Anti-virus exclusion guidance is only given for Windows paths, with no mention of Linux anti-virus configuration.
Recommendations
  • Alternate the order of Windows and Linux instructions, or present them in parallel sections to avoid Windows-first bias.
  • Provide Linux-specific examples for anti-virus exclusion, such as common Linux AV tools and relevant agent paths.
  • Clarify how to use CSPSConfigtool on Linux, or provide a Linux-native alternative if available.
  • List Linux-relevant ports (e.g., SSH, SFTP) in the note section alongside Windows ports.
  • Include Linux firewall configuration steps (e.g., using iptables, firewalld, or ufw) analogous to the Windows firewall instructions.
  • Mention Linux account management and privilege escalation methods (e.g., sudo) where appropriate.
GitHub Create Pull Request
Site Recovery Manage a process server for VMware VMs/physical server disaster recovery in Azure Site Recovery ...es/site-recovery/vmware-azure-manage-process-server.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Missing Linux Example Windows First
Summary
The documentation page demonstrates a strong Windows bias. All command-line instructions use Windows-specific tools (cmd.exe, PowerShell), Windows folder paths (%PROGRAMDATA%, C:\), and Windows anti-virus exclusion examples. There are no Linux shell commands, Linux file paths, or guidance for managing process servers on Linux systems. The use of PowerShell and Windows command prompt is assumed throughout, and Windows terminology is used exclusively.
Recommendations
  • Provide equivalent Linux instructions for all command-line operations, including shell commands and file paths.
  • Include examples for modifying proxy settings on Linux-based process servers, using bash or relevant Linux tools.
  • Add Linux anti-virus exclusion folder examples and clarify installation directory locations for Linux.
  • Explicitly state OS requirements and clarify if process servers can run on Linux; if not, explain why.
  • Where possible, use cross-platform commands or note platform-specific differences in procedures.
GitHub Create Pull Request
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-10 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 as the default or primary platform for master target servers, providing more detailed instructions and requirements for Windows than Linux, and mentioning Windows-specific tools and patterns before their Linux equivalents. Linux options are present but often appear as secondary or afterthoughts, with less detail and visibility.
Recommendations
  • Present Windows and Linux options equally in all tables and instructions, listing both platforms side-by-side.
  • Provide detailed, step-by-step examples for Linux master target server setup, matching the depth given for Windows.
  • Mention Linux tools (e.g., open-vm-tools) alongside VMware Tools for Windows, and clarify any Linux-specific requirements or caveats.
  • Ensure retention drive setup instructions for Linux are as detailed as those for Windows, including default mount points and filesystem recommendations.
  • Avoid language that implies Windows is the default or preferred platform; use neutral phrasing such as 'Windows or Linux' throughout.
  • Add troubleshooting and best practices sections specifically for Linux environments to achieve parity with Windows guidance.
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-10 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 areas: Windows examples and file paths are presented first and in more detail, Windows-specific tools (such as PsExec and Internet Explorer) are referenced without Linux equivalents, and troubleshooting steps often assume a Windows environment. Some sections lack Linux-specific instructions or examples, and Windows administrative patterns (like using elevated command prompts and referencing Windows services) are emphasized. Linux instructions are present but are generally secondary and less detailed.
Recommendations
  • Provide Linux-first or parallel examples for all troubleshooting steps, ensuring equal detail for both platforms.
  • Include Linux equivalents for Windows-only tools (e.g., alternatives to PsExec, Internet Explorer proxy settings).
  • Reference Linux file paths and service management commands (systemctl, service) alongside Windows services.
  • Ensure all command-line examples are available for both Windows and Linux, with clear differentiation.
  • Add troubleshooting steps for common Linux-specific issues (e.g., SELinux, iptables, systemd service management).
  • Where Windows administrative actions are described (e.g., elevated command prompt), provide the Linux equivalent (e.g., sudo).
  • Review all sections for implicit Windows assumptions and revise to be platform-neutral or explicitly cross-platform.
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-10 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 troubleshooting steps, tools, and commands (e.g., registry edits, net user, Netlogon, File Explorer, Control Panel, Group Policy, WMI, VSS, DCOM, COM+) are described in detail and appear first or exclusively. Linux instructions are present but less detailed, sometimes missing for equivalent scenarios (e.g., network shares, VSS, WMI). Many examples and screenshots are Windows-centric, and references to Microsoft/Windows documentation are frequent, while Linux equivalents are sparse or absent.
Recommendations
  • Provide Linux-first or side-by-side examples for all troubleshooting steps, especially for network shares, service management, and error resolution.
  • Include Linux-specific commands and tools (e.g., systemctl, journalctl, SSH, SFTP, Samba) where Windows tools (e.g., net user, regedit, File Explorer, Control Panel) are mentioned.
  • Add screenshots or terminal output for Linux procedures, similar to Windows screenshots.
  • Reference Linux documentation and troubleshooting guides alongside Microsoft/Windows links.
  • Ensure parity in error codes and troubleshooting depth for Linux scenarios (e.g., VSS equivalents, service failures, disk/partition issues).
  • Clarify when instructions are OS-specific and avoid assuming Windows as the default context.
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-10 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 exhibits a strong Windows bias by exclusively referencing Windows tools (PsExec, Internet Explorer, command prompt), providing only Windows-based procedures for proxy configuration, and omitting any Linux equivalents or guidance for environments where the configuration server or vCenter runs on Linux. All troubleshooting steps assume a Windows OS context, with no mention of Linux commands, tools, or UI paths.
Recommendations
  • Provide equivalent Linux troubleshooting steps, such as using 'sudo -u' or 'su' to access the system user context.
  • Suggest Linux-native tools for proxy configuration (e.g., editing /etc/environment, using 'export http_proxy', or configuring proxy settings in desktop environments).
  • Include instructions for modifying proxy settings for vCenter connectivity on Linux-based configuration servers.
  • Reference cross-platform browsers (e.g., Firefox, Chrome) instead of Internet Explorer, or provide steps for both Windows and Linux.
  • Clarify which steps are OS-specific and offer parity for both Windows and Linux users.
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-10 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, paths, and registry keys. Most examples and folder exclusions reference Windows directories first and in greater detail, with Linux instructions appearing only in a single section and lacking parity in detail. Windows tools and patterns (such as registry exclusions and drive letters) are mentioned exclusively or before their Linux equivalents.
Recommendations
  • Provide Linux-specific examples and instructions alongside Windows ones throughout the documentation, not just in antivirus exclusions.
  • Include Linux folder paths and configuration details in all relevant sections, such as configuration server setup and process server instructions.
  • Mention Linux tools and patterns (e.g., systemd services, SELinux/AppArmor configuration, Linux package locations) where applicable.
  • Ensure that Linux instructions are given equal prominence and detail as Windows instructions.
  • Avoid assuming Windows as the default environment; clarify when steps differ for Linux and provide both sets of instructions.
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-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page exhibits Windows bias by exclusively referencing Windows file paths (e.g., C:\Program Files), Windows-specific folders (e.g., %PROGRAMDATA%), and Windows command-line tools (cmd, net stop/start). There are no examples or troubleshooting steps for Linux-based source machines or process servers, nor are Linux file paths, services, or commands mentioned. The troubleshooting steps and error resolution instructions assume a Windows environment, omitting Linux equivalents.
Recommendations
  • Add troubleshooting steps and examples for Linux-based source machines and process servers, including relevant file paths (e.g., /var/log/...), services, and commands (systemctl, journalctl, etc.).
  • Include Linux-specific error codes and log locations for the Azure Site Recovery Mobility agent.
  • When referencing commands or file paths, provide both Windows and Linux equivalents side-by-side.
  • Clarify in each troubleshooting section whether the guidance applies to Windows, Linux, or both, and link to Linux-specific documentation where available.
  • Mention Linux user and permission requirements (e.g., chown, chmod) alongside Windows (IUSR) instructions.
GitHub Create Pull Request
Site Recovery Troubleshoot upgrade of the Microsoft Azure Site Recovery Provider ...recovery/vmware-azure-troubleshoot-upgrade-failures.md
High Priority View Details →
Scanned: 2026-01-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 exclusively provides troubleshooting steps and examples for Windows environments. All commands use Windows paths and executables, and tools like Command Prompt, Registry Editor (regedit.exe), and Task Manager are referenced without any mention of Linux equivalents or scenarios. There are no Linux-specific instructions, commands, or troubleshooting guidance, indicating a strong Windows bias.
Recommendations
  • Add equivalent troubleshooting steps for Linux environments, if supported by Azure Site Recovery.
  • Provide Linux command-line examples (e.g., using bash, tar, or unzip for extraction) alongside Windows examples.
  • Reference Linux tools (such as text editors for config files, or Linux process monitoring tools like top/htop) where appropriate.
  • Clarify in the introduction if the product or troubleshooting steps are only applicable to Windows, or explicitly state the lack of Linux support.
  • If Linux is supported, include guidance for relevant file paths, environment variables, and installation procedures on Linux systems.
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-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page shows evidence of Windows bias, primarily through references to PowerShell as a management tool and the lack of Linux-specific examples or tooling. There is no mention of Linux command-line alternatives or parity in management workflows, and the only tool referenced for blocking is PowerShell. Additionally, while Linux support is mentioned in passing (mobility agent support for new Linux distros), there are no concrete Linux-centric instructions or examples.
Recommendations
  • Include Linux command-line alternatives (such as Bash scripts or CLI commands) alongside PowerShell references for managing Azure Site Recovery.
  • Explicitly mention Linux management tools and workflows where applicable, ensuring parity with Windows instructions.
  • Provide examples or links to documentation for Linux users, such as how to perform migration steps using Linux-based systems.
  • Clarify whether all remediation steps and portal actions are equally supported on Linux and Windows, and highlight any differences.
  • Add a section addressing Linux-specific considerations, especially for physical machines running Linux.
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-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 in several areas. Windows and PowerShell are mentioned as primary or exclusive options for deployment and management tasks, while Linux alternatives are either omitted or referenced after Windows. The replication appliance setup is described only with a PowerShell script for physical servers, with no Linux-specific instructions or tooling. The operating system requirements and configuration details for the replication appliance are exclusively Windows-centric, with no mention of Linux-based alternatives. Examples and instructions for disk/network/storage management often refer to Windows tools or features first, and Linux-specific guidance is limited or missing.
Recommendations
  • Provide Linux-specific deployment instructions and tooling (e.g., Bash scripts, Ansible playbooks) for setting up the replication appliance and managing disaster recovery tasks.
  • Include Linux CLI examples and workflows alongside PowerShell, especially for common operations such as appliance setup, failover, and disk/network management.
  • Document Linux-compatible alternatives for configuration server/process server roles, or clarify if Windows is strictly required and why.
  • Ensure parity in guidance for both Windows and Linux environments, including troubleshooting, prerequisites, and supported features.
  • Explicitly mention any limitations or requirements for Linux environments in all relevant sections, and provide links to Linux-focused resources.
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-10 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 moderate Windows bias. Windows instructions and examples are consistently presented before Linux equivalents, with Windows-specific paths, tools, and screenshots dominating the UI sections. Key installation and configuration steps reference Windows directories and command prompt usage, and even Linux instructions sometimes refer to Windows paths for repository locations. The use of Windows-centric terminology (e.g., C:\Program Files, command prompt, .exe files) is pervasive, and visual examples are almost exclusively Windows-based. Linux instructions are present and generally complete, but are often secondary in order and detail.
Recommendations
  • Alternate the order of Windows and Linux instructions so that Linux is sometimes presented first.
  • Provide Linux-specific screenshots for UI-based installation steps, not just Windows.
  • Use neutral terminology and directory examples (e.g., <InstallLocation>) rather than defaulting to Windows paths.
  • Ensure parity in troubleshooting guidance and prerequisites for both platforms.
  • Highlight Linux-specific considerations (e.g., SELinux, systemd, package dependencies) where relevant.
  • Include PowerShell and Bash examples side-by-side where applicable.
  • Clarify when instructions are platform-specific and avoid assuming Windows as the default environment.
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-10 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 their Linux equivalents, providing more detailed steps for Windows (such as registry edits and firewall configuration), referencing Windows-specific tools (e.g., Windows Firewall, RDP), and omitting comparable Linux command examples or troubleshooting steps. Linux instructions are generally less detailed and lack parity in troubleshooting guidance.
Recommendations
  • Present Linux and Windows instructions side-by-side, or alternate which OS is described first to avoid implicit prioritization.
  • Include detailed Linux examples for tasks such as firewall configuration (e.g., using iptables, firewalld, or ufw), SSH setup, and troubleshooting connectivity issues.
  • Provide Linux-specific troubleshooting steps comparable to those given for Windows (e.g., checking SSH service status, reviewing system logs, verifying SELinux/AppArmor settings).
  • Reference Linux tools and patterns explicitly (e.g., systemctl for service management, /etc/ssh/sshd_config for SSH configuration) where Windows tools are mentioned.
  • Ensure that all registry or Windows-specific steps have clear Linux equivalents or note when a step is not applicable.
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-10 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 demonstrates a Windows bias by providing PowerShell examples for updating the Mobility Service agent, detailing Windows-specific tools (Control Panel, MsiExec.exe, VSS provider scripts) and presenting Windows instructions before Linux equivalents. Linux update instructions are less detailed, lacking command-line examples for agent updates, and manual update guidance is generic rather than Linux-specific.
Recommendations
  • Provide equivalent Linux command-line examples for updating the Mobility Service agent, such as using shell scripts or package managers.
  • Include Linux-specific instructions for manual updates, detailing commands for common distributions (e.g., Ubuntu, RHEL, SUSE).
  • Present Windows and Linux instructions in parallel sections or side-by-side, rather than listing Windows first.
  • Mention Linux tools and patterns (e.g., systemctl, rpm, deb) where relevant, especially for installation, update, and uninstallation steps.
  • Offer PowerShell alternatives for Linux (such as Bash scripts) and clarify cross-platform automation options.
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-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page displays a Windows bias in several ways: Windows file paths and service names are mentioned before or more prominently than Linux equivalents, and troubleshooting steps reference Windows-specific tools and patterns (such as named services and file paths) without providing Linux alternatives or commands. There are missing Linux-specific troubleshooting examples, such as how to restart relevant services or check logs on Linux systems.
Recommendations
  • Provide Linux-specific troubleshooting steps alongside Windows instructions, such as systemctl/service commands for restarting services.
  • List Linux file paths and commands before or alongside Windows equivalents to avoid Windows-first ordering.
  • Include Linux service names and how to check their status, restart them, or view logs (e.g., journalctl, systemctl status).
  • Add examples of common Linux errors and resolutions, not just Windows-centric log messages and service names.
  • Ensure parity in guidance for both platforms, including references to Linux tools (e.g., curl, system logs) and not just Windows services.
GitHub Create Pull Request
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/azure-to-azure-how-to-enable-replication-s2d-vms.md ...ry/azure-to-azure-how-to-enable-replication-s2d-vms.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 Windows-specific technologies, such as Storage Spaces Direct (S2D), Windows Failover Clustering, and related tools. All examples, terminology, and referenced features are Windows-centric, with no mention of Linux equivalents or guidance for Linux-based clusters. There are no Linux examples or alternative disaster recovery scenarios for non-Windows platforms.
Recommendations
  • Include guidance or links for disaster recovery of Linux-based clusters or virtual machines using Azure Site Recovery.
  • Provide examples or references for setting up multi-VM consistency groups and recovery plans for Linux VMs.
  • Mention alternative storage clustering solutions available for Linux (e.g., DRBD, Pacemaker, Corosync) and how they can be protected using Azure Site Recovery.
  • Clarify in the introduction that the article is specific to Windows clusters, and provide links to Linux documentation if available.
  • Add a section comparing Windows and Linux disaster recovery approaches in Azure, highlighting feature parity and differences.
GitHub Create Pull Request
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/feature-updates-whats-new.md ...in/articles/site-recovery/feature-updates-whats-new.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 page for Azure Site Recovery feature updates demonstrates a notable Windows bias. Windows Server Failover Clusters (WSFC) and related Windows-only features are highlighted, with explicit OS support for Windows Server and PowerShell mentioned as a supported tool. Linux support is referenced less frequently and often as a preview or secondary to Windows. There are no Linux-specific examples or equivalent tooling mentioned, and Windows features are generally presented first or exclusively.
Recommendations
  • Include Linux-specific examples and scenarios, especially for features that support both Windows and Linux.
  • Mention Linux clustering technologies (e.g., Pacemaker, Corosync) when discussing shared disk and failover cluster features.
  • Provide parity in tooling references, such as including Bash or CLI commands alongside PowerShell.
  • Clearly indicate OS support for both Windows and Linux where applicable, and avoid presenting Windows features or tools as the default.
  • Add documentation sections or examples for Linux-based disaster recovery scenarios, including monitoring and failover processes.
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-09 00:34
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 support is mentioned before Linux, and certain features (shared disks, VM creation flow) are explicitly stated as Windows-only. There are no Linux-specific examples or CLI commands, and PowerShell/CLI migration channels are referenced without Linux parity. The documentation lacks Linux-focused guidance and examples, and Windows scenarios are prioritized or exclusively supported in some cases.
Recommendations
  • Provide Linux-specific examples and step-by-step instructions, especially for migration and agent uninstall processes.
  • Include CLI commands and scripts for Linux environments, not just PowerShell or portal-based instructions.
  • Clearly indicate feature parity and limitations for Linux, and update the documentation as Linux support expands.
  • Ensure that Linux support is mentioned alongside Windows in all relevant sections, not as an afterthought.
  • Add troubleshooting and best practices sections for Linux users, similar to what is available for Windows.
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-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 Windows environments, specifically Hyper-V, and exclusively references Windows tools and workflows (e.g., .exe installers, Windows directory paths, Windows command-line syntax, and MARS agent). There are no Linux equivalents, examples, or guidance for disaster recovery of Linux-based hypervisors (such as KVM or Xen), nor any mention of cross-platform considerations. All instructions, screenshots, and commands are tailored to Windows/Hyper-V administrators.
Recommendations
  • Add guidance or links for disaster recovery of Linux-based hypervisors (e.g., KVM, Xen, VMware on Linux).
  • Include Linux-specific examples and instructions where possible, such as agent installation on Linux hosts, or clarify that the tutorial is Windows-only if no Linux support exists.
  • Mention alternative tools or workflows for Linux environments, or provide a comparison table of supported platforms and their respective disaster recovery setup steps.
  • If Azure Site Recovery does not support Linux-based hypervisors, state this explicitly and direct Linux users to relevant documentation or alternatives.
GitHub Create Pull Request
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/monitoring-high-churn.md ...b/main/articles/site-recovery/monitoring-high-churn.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 presents Windows monitoring tools (Resource Monitor, Performance Monitor) in greater detail and with screenshots, while Linux tools (iotop, iostat) are mentioned briefly without usage examples, screenshots, or further guidance. Windows tools are described first and in depth, indicating a Windows-first and Windows-tools bias. There is also a lack of parity in example depth and visual aids for Linux.
Recommendations
  • Provide step-by-step usage instructions for Linux tools (iotop, iostat), similar to the Windows section.
  • Include screenshots or sample outputs for Linux tools to match the visual guidance given for Windows.
  • Mention additional Linux monitoring tools (e.g., atop, dstat, sar) to broaden options.
  • Ensure equal detail and troubleshooting tips for both platforms.
  • Consider alternating the order of Windows and Linux sections or presenting them in parallel for each tool type.
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-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 VMM, with all examples and instructions assuming the use of Windows servers and Hyper-V roles. There are no references to Linux hosts, KVM, or other non-Windows virtualization platforms, nor are there any Linux-specific instructions, tools, or parity notes. The steps for failback exclusively mention Windows installation and configuration patterns.
Recommendations
  • Add explicit statements clarifying that the documented process is specific to Hyper-V/Windows environments, and note the lack of Linux support if applicable.
  • If Azure Site Recovery supports Linux-based hypervisors or VMs, provide equivalent failback instructions and examples for those platforms.
  • Include a comparison table or section outlining differences and limitations between Windows and Linux failback scenarios.
  • Reference Linux tools or commands for VM management where relevant, or provide links to Linux-specific documentation.
  • If Linux is not supported, clearly state this at the beginning of 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/hyper-v-vmm-azure-tutorial.md ...n/articles/site-recovery/hyper-v-vmm-azure-tutorial.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 managed by System Center VMM. All examples, installation instructions, and command-line snippets use Windows tools (e.g., PowerShell, Windows installers). There are no references to Linux-based Hyper-V hosts, nor are Linux equivalents or alternatives mentioned. The documentation assumes a Windows-centric workflow throughout.
Recommendations
  • Explicitly state that Hyper-V and System Center VMM are Windows-only technologies, and clarify platform requirements early in the document.
  • If Linux-based virtualization or management is supported by Azure Site Recovery, provide parallel instructions or links for those scenarios.
  • Where possible, mention alternatives for Linux environments (e.g., Azure Site Recovery support for VMware or Linux KVM hosts) and link to relevant documentation.
  • Add a section that addresses cross-platform considerations, including limitations or guidance for users on non-Windows platforms.
  • Ensure that command-line examples and tooling references are balanced or clearly marked as Windows-specific.
GitHub Create Pull Request
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/site-recovery-failover-to-azure-troubleshoot.md ...covery/site-recovery-failover-to-azure-troubleshoot.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 First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates several forms of Windows bias. Troubleshooting steps for hydration failures provide only Windows PowerShell scripts and registry modification instructions, with no Linux equivalent or mention of how to perform similar actions for Linux VMs. Windows-specific tools (PsExec, Internet Explorer) are referenced for proxy troubleshooting, even in a Linux context. Windows troubleshooting steps and references (RDP, registry, domain join) are presented before or in more detail than Linux equivalents. Linux troubleshooting is limited to a single command for UEFI console issues and basic SSH references, with no parity for deeper troubleshooting steps or automation scripts.
Recommendations
  • Provide equivalent Linux troubleshooting steps and scripts for hydration failures, including instructions for verifying and modifying required drivers and services on Linux VMs.
  • When referencing tools for proxy troubleshooting, offer Linux-native alternatives (e.g., using curl, wget, or modifying /etc/environment directly) and avoid requiring Windows-only utilities like PsExec and Internet Explorer.
  • Ensure that troubleshooting steps for both Windows and Linux VMs are presented in parallel, with equal detail and visibility.
  • Expand Linux troubleshooting sections to include common issues (e.g., network configuration, driver compatibility, SSH key problems) and provide automation scripts or commands where possible.
  • Review and update examples and screenshots to include both Windows and Linux scenarios, ensuring users of both platforms are equally supported.
GitHub Create Pull Request
← Previous Page 10 of 35 Next →