Site Recovery

394
Total Pages
277
Linux-Friendly Pages
117
Pages with Bias
29.7%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

232 issues found
Showing 151-175 of 232 flagged pages
Site Recovery About using ExpressRoute with Azure Site Recovery ...e-recovery/concepts-expressroute-with-site-recovery.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
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 Windows bias in the section describing proxy bypass configuration for replication traffic. It exclusively references Windows tools (PsExec, Internet Explorer) and provides step-by-step instructions only for Windows environments, with no mention of Linux or macOS equivalents. The use of Windows-specific tools and patterns (PsExec, IE proxy settings) excludes Linux users from following the instructions directly. Additionally, Windows examples and tools are presented first and exclusively, with no parity for other platforms.
Recommendations
  • Add instructions for configuring proxy bypass on Linux and macOS servers, including relevant commands and configuration file locations (e.g., environment variables, /etc/environment, or browser/network settings).
  • Reference cross-platform tools for proxy configuration, such as curl, wget, or system-wide proxy settings.
  • Avoid reliance on Windows-only tools (PsExec, Internet Explorer) and provide alternatives for Linux (e.g., using sudo, editing configuration files directly).
  • Clearly indicate platform-specific steps and provide equivalent guidance for all supported operating systems.
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
Medium Priority View Details →
Scanned: 2026-01-11 06:20
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 notable Windows bias. The 'Prepare on-premises machines' section provides detailed, step-by-step instructions for Windows, including references to Windows-specific settings, services, PowerShell usage, and Windows Firewall configuration. In contrast, Linux preparation is covered in only two brief bullet points, lacking detail and omitting common Linux tasks (e.g., SELinux, iptables, SSH hardening, package updates). Windows tools and patterns (PowerShell, Windows Firewall, RDP) are mentioned exclusively or before Linux equivalents, and Windows examples precede Linux ones throughout.
Recommendations
  • Expand the 'Prepare Linux machines' section to include detailed steps equivalent to the Windows section, such as checking and configuring SELinux/AppArmor, managing iptables/firewalld rules, ensuring SSH key-based authentication, and verifying package updates.
  • Provide Linux-specific troubleshooting steps and links, similar to those given for Windows.
  • Include examples for enabling remote access on Linux (e.g., SSH configuration commands, firewall rules with iptables or firewalld).
  • Present Windows and Linux instructions in parallel, or clearly separate them, to avoid implicit prioritization.
  • Reference Linux tools and commands (e.g., systemctl, ufw, iptables) where appropriate.
  • Ensure parity in guidance for both OSes, including automation and scripting options (e.g., Bash scripts, Ansible for Linux).
GitHub Create Pull Request
Site Recovery Remove an Azure Site Recovery replication appliance ...s/blob/main/articles/site-recovery/delete-appliance.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates a moderate Windows bias. It references Windows-specific tools (e.g., Services.msc, World Wide Web Publishing Service), and browser instructions are tailored to Microsoft Edge. There are no Linux/macOS equivalents or instructions for managing services or clearing browser cache. All operational examples and steps assume a Windows environment, with no mention of Linux or macOS alternatives for appliance management.
Recommendations
  • Add instructions for managing services on Linux (e.g., using systemctl to restart web services).
  • Include browser cache clearing steps for Firefox and Chrome on Linux/macOS.
  • Clarify whether the appliance can run on Linux, and if so, provide Linux-specific reset/delete instructions.
  • When referencing tools like Services.msc, mention the Linux/macOS equivalent or note if the step is Windows-only.
  • Ensure parity in troubleshooting and post-delete steps for Linux/macOS users.
GitHub Create Pull Request
Site Recovery Trusted launch VMs with Azure Site Recovery ...lob/main/articles/site-recovery/concepts-trusted-vm.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation demonstrates a moderate Windows bias. Several features (shared disks, 'Create a new VM flow' with Site Recovery) are explicitly supported only for Windows OS, with Linux support absent or deferred. Windows is mentioned first in support matrices and feature lists. There are no Linux-specific examples, troubleshooting steps, or parity notes for CLI tools, and PowerShell/CLI migration channels are referenced without clarifying Linux usability.
Recommendations
  • Add Linux-specific examples and instructions, especially for migration and agent uninstallation.
  • Clarify CLI tool compatibility and provide Linux/macOS command-line instructions where PowerShell is mentioned.
  • Explicitly state timelines or workarounds for unsupported Linux features (e.g., 'Create a new VM flow').
  • Present OS support in a neutral order or highlight Linux support equally.
  • Document any Linux-specific limitations or troubleshooting steps.
GitHub Create Pull Request
Site Recovery Delete an Azure Site Recovery vault ...-docs/blob/main/articles/site-recovery/delete-vault.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation provides only PowerShell examples for force-deleting the Azure Site Recovery vault, with no mention of equivalent CLI commands for Linux/macOS users. The use of PowerShell and references to Windows-centric tools (e.g., Hyper-V, VMM) are prevalent, and alternative cross-platform approaches are not discussed. This creates friction for users on non-Windows platforms.
Recommendations
  • Add Azure CLI examples for deleting the vault and its dependencies, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Explicitly mention that PowerShell Core is available on Linux/macOS, if PowerShell must be used, and provide installation guidance.
  • Where Windows-specific tools (Hyper-V, VMM) are referenced, clarify if there are Linux equivalents or note platform limitations.
  • Ensure that all critical operations (such as force delete) have cross-platform command examples.
  • Consider reordering examples so that cross-platform tools (Azure CLI) are presented before or alongside PowerShell.
GitHub Create Pull Request
Site Recovery Deploy Azure Site Recovery Replication Appliance - Modernized ...tps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/deploy-vmware-azure-replication-appliance-modernized.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
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 notable Windows bias. PowerShell is presented as the only command-line method for manual appliance setup, with no Linux shell or cross-platform alternatives. Registry and group policy checks are exclusively Windows-centric, and there is no mention of Linux equivalents or how to perform similar validation on Linux-based appliances. Windows terminology and tools (e.g., registry keys, group policies, PowerShell execution policy) are referenced without Linux parity. The order of presentation also favors Windows approaches and tools.
Recommendations
  • Provide Linux shell (bash) or cross-platform CLI instructions for manual appliance setup alongside PowerShell.
  • Clarify whether the appliance can be deployed on Linux-based VMs, and if so, include Linux-specific setup and validation steps.
  • Add documentation for Linux equivalents to registry and group policy checks, or explicitly state if these steps are Windows-only.
  • When listing OS-specific requirements (e.g., credentials for agent installation), offer parity in detail and troubleshooting for both Windows and Linux.
  • Consider reordering examples so that platform-neutral or Linux instructions are presented alongside or before Windows-specific steps.
GitHub Create Pull Request
Site Recovery Exclude disks from replication with Azure Site Recovery ...in/articles/site-recovery/exclude-disks-replication.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exhibits a Windows bias by providing only Windows VM examples (including SQL Server and paging file scenarios), referencing Windows-specific tools (diskmgmt.msc, service console), and omitting Linux VM walkthroughs or commands. Linux is mentioned only in passing within a limitation table, with no practical guidance or examples for Linux VM disk exclusion, failover, or recovery.
Recommendations
  • Add equivalent Linux VM examples for disk exclusion, failover, and recovery, including handling of swap partitions, temp files, and database temp directories (e.g., /tmp, /var/tmp, /var/lib/mysql/tmp).
  • Include Linux-specific instructions for adding and formatting disks (e.g., using fdisk, mkfs, mount), and updating system/database configuration files.
  • Reference Linux tools and commands (e.g., systemctl for service management, lsblk for disk identification) alongside Windows tools.
  • Present examples for both Windows and Linux VMs in parallel, or alternate their order to avoid Windows-first bias.
  • Clarify any differences in failback behavior for Linux VMs with concrete examples.
GitHub Create Pull Request
Site Recovery About failover and failback in Azure Site Recovery - Modernized ...site-recovery/failover-failback-overview-modernized.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. In sections describing how to connect to Azure VMs after failover, Windows instructions (RDP, Windows Firewall, Windows Update, SAN policy) are presented first and in greater detail, with Linux instructions (SSH, firewall) given later and more briefly. Windows-specific tools and concepts (Windows Firewall, RDP, SAN policy, Windows Update) are referenced without Linux equivalents or cross-platform alternatives. Some troubleshooting and operational notes are Windows-centric, and Linux guidance is minimal or absent in those areas.
Recommendations
  • Present Linux and Windows instructions in parallel, giving equal detail and prominence.
  • Include Linux-specific troubleshooting steps (e.g., SSH connectivity, SELinux, systemd service status, common firewall tools like iptables, firewalld, ufw).
  • Mention Linux equivalents for Windows concepts (e.g., SAN policy, update management, boot diagnostics).
  • Add notes for Linux users where Windows-specific advice is given (e.g., pending updates, firewall configuration).
  • Where possible, use generic, cross-platform language and examples.
GitHub Create Pull Request
Site Recovery Replicate Azure virtual machines running in a proximity placement group ...tps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/how-to-enable-replication-proximity-placement-groups.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation page demonstrates a notable Windows bias, primarily through its heavy reliance on PowerShell for automation and scripting examples. All CLI-based instructions are exclusively given using Azure PowerShell cmdlets, with no Bash, Azure CLI, or Linux-native scripting alternatives. The prerequisites and links for scripting reference only Azure PowerShell, which is most commonly used on Windows. Additionally, the proximity placement group concept is linked to Windows VM documentation first, and the overall structure presents Windows-centric tools and patterns before mentioning Linux or cross-platform equivalents.
Recommendations
  • Provide equivalent Azure CLI (az) examples for all PowerShell cmdlets, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Include Bash scripting samples for automation tasks, especially for disk and VM replication steps.
  • Reference proximity placement group documentation for both Windows and Linux VMs equally, or link to a neutral overview.
  • Clarify that Azure PowerShell can be installed and used on Linux/macOS, and provide installation instructions for those platforms.
  • Add a section or callouts for Linux/macOS users, highlighting any platform-specific considerations or differences.
GitHub Create Pull Request
Site Recovery New feature updates in Azure Site Recovery ...in/articles/site-recovery/feature-updates-whats-new.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation page shows a moderate Windows bias. Several feature updates focus on Windows-specific technologies (e.g., Windows Server Failover Clusters, Hyper-V, PowerShell support) and mention Windows OS support and tools before Linux equivalents. Linux support is present but often appears as a secondary note or is limited to previews, with less detail and fewer examples. There are no Linux-specific tooling or example sections, and Windows-centric patterns (WSFC, Hyper-V, PowerShell) are referenced without Linux alternatives.
Recommendations
  • Include Linux-specific examples and tooling (e.g., shell commands, Linux clustering solutions) alongside Windows examples.
  • When describing features, present Windows and Linux support in parallel, rather than listing Windows first or exclusively.
  • Add parity in feature descriptions, ensuring Linux scenarios are covered with equal detail (e.g., for clustering, monitoring, failover).
  • Avoid referencing Windows tools (like PowerShell) without mentioning Linux equivalents (such as Bash or CLI).
  • Explicitly state OS support for each feature, and provide links to Linux documentation where available.
GitHub Create Pull Request
Site Recovery Configure on-premise disks for Azure through Hydration .../blob/main/articles/site-recovery/hydration-process.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. Windows instructions and examples are presented first and in greater detail, including screenshots and explicit PowerShell commands, while Linux instructions are less visual and rely on generic bash commands. Windows-specific tools (diskpart, PowerShell, registry editor) are referenced with screenshots and step-by-step guidance, whereas Linux instructions are more distribution-dependent and lack equivalent visual aids or explicit commands for some steps. Some manual configuration steps for Linux are described only in general terms, with fewer concrete examples compared to Windows.
Recommendations
  • Alternate the order of Windows and Linux sections, or present both in parallel where possible.
  • Provide equivalent screenshots and step-by-step command-line examples for Linux (e.g., using lsblk, blkid, systemctl, etc.).
  • Include explicit Linux commands for DHCP configuration and service management, similar to the PowerShell examples for Windows.
  • Reference Linux tools (e.g., parted, fdisk, systemctl) with concrete usage examples.
  • Expand troubleshooting and manual preparation instructions for Linux to match the detail given for Windows.
  • Add links to Linux-specific documentation and community resources, similar to those provided for Windows.
GitHub Create Pull Request
Site Recovery Monitor Azure Site Recovery with Azure Monitor Logs ...b/main/articles/site-recovery/monitor-log-analytics.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation demonstrates a Windows bias in the section on configuring the Microsoft monitoring agent for churn and upload rate logs. It exclusively describes downloading and installing the Windows Agent, navigating Windows-specific UI (Windows Servers, Windows Performance Counters), and provides no instructions or examples for Linux-based Process Servers. There is no mention of Linux agent installation, configuration, or equivalent Linux monitoring workflows, even though Linux-based servers may be used in VMware or physical environments.
Recommendations
  • Add instructions for installing and configuring the Microsoft monitoring agent on Linux-based Process Servers, including download links, workspace configuration, and performance counter setup.
  • Include screenshots or CLI examples for Linux agent setup (e.g., using shell commands or Linux UI).
  • Clarify whether churn/upload rate monitoring is supported on Linux Process Servers, and if not, explicitly state this limitation.
  • Present both Windows and Linux agent setup steps side-by-side, or clearly indicate platform-specific procedures.
  • Where possible, provide Kusto query examples that reference Linux-based machines or counters.
GitHub Create Pull Request
Site Recovery Monitoring churn patterns on virtual machines ...b/main/articles/site-recovery/monitoring-high-churn.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation presents Windows monitoring tools (Resource Monitor, Performance Monitor) in much greater detail, including step-by-step instructions and screenshots, while Linux tools (iotop, iostat) are only briefly mentioned with single-line descriptions and no usage examples or visuals. Windows tools are listed first and receive more attention, creating a notable bias toward Windows users.
Recommendations
  • Provide step-by-step instructions for using iotop and 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) for parity.
  • Present Windows and Linux sections with equal depth and clarity, possibly interleaving examples or using parallel structure.
  • Consider listing Linux tools first or alternating order in future documentation to avoid implicit prioritization.
GitHub Create Pull Request
Site Recovery Set up disaster recovery of physical on-premises servers with Azure Site Recovery ...cles/site-recovery/physical-azure-disaster-recovery.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation provides more detailed instructions and examples for Windows servers, including registry edits and command-line usage, while Linux instructions are minimal and lack equivalent detail. Windows-specific tools and patterns (e.g., registry edits, use of REG ADD) are described, but Linux alternatives are not shown. Windows is often mentioned first, and Linux guidance is brief or missing in several sections.
Recommendations
  • Provide equivalent step-by-step instructions for Linux servers, including example commands for required configuration changes.
  • Include Linux-specific troubleshooting tips and prerequisites (e.g., SELinux, firewall, time synchronization using ntpd/chrony).
  • When describing account preparation, offer explicit Linux CLI commands (e.g., usermod, sudoers configuration) and clarify any OS-specific requirements.
  • Ensure that examples and instructions for both Windows and Linux are presented in parallel, or alternate which OS is shown first.
  • Add screenshots or CLI output examples for Linux where Windows screenshots are provided.
GitHub Create Pull Request
Site Recovery Enable replication for a physical server – Modernized ...es/site-recovery/physical-server-enable-replication.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation mentions both Windows and Linux operating systems, but provides more explicit instructions for Windows (e.g., specifying admin privileges) and lists Windows before Linux in credential requirements. There are no concrete Linux-specific examples, commands, or troubleshooting steps, and no mention of Linux tools or patterns. The process for Linux is only briefly referenced (e.g., 'provide root credentials'), with no further guidance or parity in example detail.
Recommendations
  • Provide explicit Linux examples and step-by-step instructions, including screenshots or CLI commands where relevant.
  • Include troubleshooting steps or common issues for Linux systems, such as SELinux, firewall, or SSH configuration.
  • Mention Linux-specific patterns or tools (e.g., systemd, sudo) where applicable.
  • Ensure Linux instructions are presented with equal prominence and detail as Windows instructions.
  • Add parity in credential requirements, such as specifying if sudoers or SSH keys can be used for Linux.
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
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exhibits Windows bias by referencing Windows-specific requirements (such as .NET Framework and TLS settings), linking to Windows-only resources, and providing system clock synchronization instructions using a Windows time service link. There are no Linux-specific setup instructions, examples, or troubleshooting steps, despite the article stating support for both Windows and Linux physical servers.
Recommendations
  • Add explicit Linux prerequisites, such as required packages, dependencies, and supported distributions.
  • Provide Linux-specific setup instructions, including how to run the Unified Setup installer on Linux (if supported), or clarify if a Windows host is required.
  • Include Linux command-line examples for installation, registration, and troubleshooting.
  • Reference Linux time synchronization methods (e.g., using ntpd or systemd-timesyncd) alongside or before Windows equivalents.
  • Clarify any limitations or differences for Linux users in the setup process.
GitHub Create Pull Request
Site Recovery Move Azure virtual machines between government and public regions with Azure Site Recovery .../main/articles/site-recovery/region-move-cross-geos.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation provides detailed instructions for preparing Windows virtual machines, including registry edits and CLI commands, but offers only minimal guidance for Linux systems (simply stating 'the account should be root'). No Linux-specific steps, commands, or troubleshooting are provided, and Windows instructions (including registry and CLI) are presented first and in detail.
Recommendations
  • Add explicit Linux preparation steps, such as required packages, services, or configuration changes for the Mobility service.
  • Provide Linux CLI commands or scripts analogous to the Windows registry edit (e.g., using 'sudo' or modifying configuration files).
  • Include troubleshooting tips or common issues for Linux VMs during replication and failover.
  • Present Windows and Linux instructions in parallel, or clearly separate them with headings for each OS.
  • Ensure that all steps mentioning accounts, permissions, or service installation specify requirements for both Windows and Linux.
GitHub Create Pull Request
Site Recovery Troubleshoot the Azure VM extension for disaster recovery with Azure Site Recovery .../site-recovery/site-recovery-extension-troubleshoot.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation presents troubleshooting steps for both Windows and Linux VMs, but consistently lists Windows solutions and errors before Linux equivalents. Windows-specific tools (services.msc, Control Panel, MSI installer, .NET Framework) are described in detail, while Linux instructions are more generic and rely on external links. This ordering and tool emphasis may create friction for Linux users.
Recommendations
  • Alternate the order of Windows and Linux sections, or present them in parallel where possible.
  • Provide equally detailed, step-by-step instructions for Linux troubleshooting (e.g., commands to check agent status, uninstall/reinstall agent, check dependencies).
  • Include Linux-specific error messages and troubleshooting scenarios where relevant.
  • Reference Linux tools and patterns (systemctl, package managers) with the same clarity as Windows tools.
  • Ensure that Linux examples are not relegated to external links, but are included directly in the documentation.
GitHub Create Pull Request
Site Recovery Set up SAP NetWeaver disaster recovery with Azure Site Recovery .../blob/main/articles/site-recovery/site-recovery-sap.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias. The reference architecture is explicitly described as running SAP NetWeaver in a Windows environment, with clustering guidance focused on Windows Server Failover Cluster, Storage Spaces Direct, and SIOS DataKeeper—all Windows-centric technologies. There is no mention of Linux-based SAP deployments, nor are Linux clustering or high availability solutions (e.g., Pacemaker, NFS, DRBD) discussed. All examples and recommendations assume Windows as the operating system, leaving Linux users without guidance for equivalent disaster recovery setups.
Recommendations
  • Include guidance and examples for SAP NetWeaver deployments on Linux, which are common in enterprise environments.
  • Describe Linux-supported clustering and high availability solutions, such as Pacemaker, Corosync, DRBD, and NFS for /sapmnt shares.
  • Provide parity in disaster recovery steps and tooling for Linux-based SAP deployments, including supported Azure Site Recovery scenarios.
  • Explicitly state OS-specific limitations and provide links to Linux documentation where applicable.
  • Add sample scripts and automation guidance for Linux VMs, not just Windows-based scripts.
GitHub Create Pull Request
Site Recovery Run a failover during disaster recovery with Azure Site Recovery .../main/articles/site-recovery/site-recovery-failover.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a Windows bias in several areas: Windows VM instructions are presented first and in greater detail, with explicit references to Windows-specific tools (RDP, Windows Firewall, WinHTTP proxy, SAN policy, Windows Update). Linux VM instructions are brief and lack comparable detail or troubleshooting guidance. Some sections (e.g., troubleshooting connectivity, post-failover configuration) link to Windows-centric resources or provide more comprehensive steps for Windows than Linux.
Recommendations
  • Provide Linux instructions and troubleshooting steps with equal detail, including common issues (e.g., SSH configuration, firewall troubleshooting, SELinux/AppArmor, cloud-init, network interface naming).
  • Include Linux-specific tools and configuration guidance (e.g., iptables, firewalld, systemd services, network manager) alongside Windows tools.
  • Present Windows and Linux examples side-by-side or in parallel tables, rather than listing Windows first.
  • Add links to Linux-focused resources for post-failover connectivity and troubleshooting.
  • Ensure parity in pre-failover and post-failover checklists for both OS types.
GitHub Create Pull Request
Site Recovery Plan capacity for VMware disaster recovery with Azure Site Recovery ...es/site-recovery/site-recovery-plan-capacity-vmware.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
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 notable Windows bias, especially in sections related to bandwidth control and process server management. Windows-specific tools (MMC snap-in, registry edits, PowerShell cmdlets) are referenced exclusively, with no Linux equivalents or guidance. Examples and instructions for configuration changes are provided only for Windows environments, and Windows terminology and tools are introduced before any mention of Linux. Linux is only referenced in the context of deploying a master target server, with no parity for other operational tasks.
Recommendations
  • Provide Linux-specific instructions for bandwidth throttling and process server configuration, including relevant commands and configuration file paths.
  • Offer examples using Linux tools (e.g., systemd, cron, shell scripts) for automation and monitoring tasks.
  • Include guidance for managing registry-like settings on Linux, or clarify if such settings are not applicable.
  • Ensure that all operational steps (e.g., process server setup, bandwidth management) have Linux/macOS equivalents or explicitly state platform limitations.
  • Present examples for both Windows and Linux side-by-side, or clearly label platform-specific instructions.
GitHub Create Pull Request
Site Recovery Troubleshoot failover to Azure failures ...covery/site-recovery-failover-to-azure-troubleshoot.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
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 notable Windows bias, especially in troubleshooting hydration failures (Error ID 170010), where only Windows PowerShell scripts are provided and registry manipulation is described for Windows Guest OS. Windows tools like PsExec and Internet Explorer are referenced for proxy troubleshooting, with no Linux equivalents or alternatives. In several sections, Windows-specific instructions and terminology appear before or instead of Linux guidance. Linux troubleshooting is present but less detailed and often relegated to later sections or external links.
Recommendations
  • Provide equivalent Linux troubleshooting steps for hydration failures, including shell commands or scripts for driver/service startup configuration.
  • Include Linux-specific examples and tools (e.g., using systemctl, modifying /etc files) alongside Windows PowerShell instructions.
  • When referencing Windows tools like PsExec or Internet Explorer, offer Linux alternatives (such as sudo, curl, or direct config file editing).
  • Ensure Linux and macOS instructions are presented with equal prominence and detail, ideally side-by-side with Windows steps.
  • Expand Linux troubleshooting sections to match the depth and clarity of Windows guidance, especially for common failover errors.
GitHub Create Pull Request
Site Recovery Add Azure Automation runbooks to Site Recovery recovery plans ...cles/site-recovery/site-recovery-runbook-automation.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page exclusively uses PowerShell for all code examples, variable manipulation, and runbook scripting. There are no references to Bash, Python, or cross-platform scripting options. All module and tool references are for PowerShell/AzureRM, which are most commonly used on Windows. No Linux/macOS-specific guidance or parity examples are provided, and Windows-centric terminology and workflows are presented first and exclusively.
Recommendations
  • Add equivalent examples using Bash, Python, or Azure CLI to demonstrate how Linux/macOS users can interact with Azure Automation and recovery plan contexts.
  • Explicitly mention cross-platform compatibility for Azure Automation runbooks, and provide guidance on authoring runbooks in languages other than PowerShell.
  • Reference Azure CLI modules and commands alongside PowerShell, and clarify which steps/tools are available or recommended for Linux/macOS users.
  • Include a section or note on how Linux/macOS users can set up and manage Azure Automation accounts and variables, including any platform-specific considerations.
GitHub Create Pull Request
Site Recovery Upgrade Mobility Service and appliance components - Modernized ...s/site-recovery/upgrade-mobility-service-modernized.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation page exhibits a moderate Windows bias. Windows-specific tools (Registry Editor, .msi installers, command prompt, Windows Settings) are referenced exclusively for appliance component updates, with no Linux equivalents or instructions. Windows update instructions and examples are presented before Linux ones in the agent update section. Some manual update procedures (e.g., registry changes, .msi installation) are only described for Windows, with no mention of how to perform similar actions on Linux-based appliances, if supported.
Recommendations
  • Add explicit instructions and examples for updating appliance components on Linux-based servers, if supported.
  • Where registry edits are required for Windows, clarify if/how equivalent configuration can be performed on Linux (e.g., config files, environment variables).
  • Present Windows and Linux agent update instructions in parallel, or alternate which platform is shown first.
  • If appliance management is only supported on Windows, state this clearly at the beginning of relevant sections.
  • Include troubleshooting steps and update verification for Linux appliances, if applicable.
GitHub Create Pull Request
Site Recovery Set up disaster recovery for SQL Server with Azure Site Recovery .../blob/main/articles/site-recovery/site-recovery-sql.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation page exhibits a Windows bias by referencing Windows-specific tools (Task Manager, PowerShell), linking primarily to Windows-focused SQL Server features, and omitting explicit Linux examples or guidance. Windows terminology and procedures are presented first or exclusively, with no mention of Linux equivalents for monitoring, clustering, or scripting failover operations.
Recommendations
  • Add explicit examples and guidance for SQL Server deployments on Linux, including supported BCDR technologies and failover procedures.
  • Reference Linux tools (e.g., iotop, atop, sar) for monitoring disk write rates instead of only mentioning Windows Task Manager.
  • Provide Linux-compatible scripts or instructions for automating failover (e.g., Bash scripts, systemd units) alongside PowerShell examples.
  • Include links to SQL Server on Linux documentation for clustering, availability groups, and disaster recovery.
  • Clarify which steps and features are supported or differ on Linux, especially for Site Recovery integration.
GitHub Create Pull Request
← Previous Page 7 of 10 Next →