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 726-750 of 864 flagged pages
Site Recovery Azure Virtual Machines disaster recovery - High Churn support ...recovery/concepts-azure-to-azure-high-churn-support.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation mentions supported operating systems for Enhanced Churn (Windows, Linux – RHEL 9, SLES 15, Ubuntu 24.04), but Windows is listed first and there are no Linux-specific configuration examples, screenshots, or troubleshooting notes. All instructions and UI references are generic and do not address Linux-specific considerations, potentially leaving Linux users without guidance for platform-specific issues.
Recommendations
  • Explicitly include Linux in all supported OS lists and avoid listing Windows first unless alphabetical.
  • Provide Linux-specific configuration steps, screenshots, or notes where differences exist (e.g., agent installation, permissions, troubleshooting).
  • Add troubleshooting or FAQ sections for common Linux issues in high churn scenarios.
  • Clarify any differences in replication behavior or requirements between Windows and Linux VMs.
  • Ensure parity in example commands, logs, and error messages for both Windows and Linux environments.
GitHub Create Pull Request
Site Recovery Deprecation of Azure Site Recovery data encryption feature ...ticles/site-recovery/encryption-feature-deprecation.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation focuses exclusively on Hyper-V VMs, which are a Windows-centric virtualization technology. There are no examples, references, or guidance for Linux-based virtualization platforms (such as KVM or VMware on Linux), nor are Linux command-line tools or procedures mentioned. The steps and remediation actions are tailored to Windows environments, implicitly prioritizing Windows users and omitting Linux parity.
Recommendations
  • Include equivalent guidance for Linux-based virtualization platforms (e.g., KVM, VMware on Linux) if supported by Azure Site Recovery.
  • Add examples and remediation steps for Linux VMs, including how to transition to encryption at rest for those environments.
  • Mention any differences or limitations in encryption support for Linux VMs, if applicable.
  • Ensure that documentation titles and descriptions clarify if the guidance is Windows-specific, or broaden the scope to include Linux scenarios where possible.
GitHub Create Pull Request
Site Recovery Review the Azure Site Recovery Deployment Planner cost estimation report for disaster recovery of Hyper-V VMs to Azure| Microsoft Docs ...recovery/hyper-v-deployment-planner-cost-estimation.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page is focused on disaster recovery planning for Hyper-V VMs, which are inherently Windows-based. Throughout the page, examples, terminology, and instructions are tailored to Windows environments (e.g., Hyper-V, Windows VMs, Azure Hybrid Use Benefit for Windows). While Linux VMs are mentioned in passing (e.g., 'Windows and non-Windows VMs'), there are no Linux-specific examples, instructions, or considerations. Windows features and benefits (such as Azure Hybrid Use Benefit) are described in detail, but Linux equivalents or unique considerations are not addressed.
Recommendations
  • Add explicit examples and instructions for Linux VMs, including any differences in cost estimation, replication, or DR drills.
  • Clarify whether the Deployment Planner supports Linux VMs natively and describe any limitations or special steps required.
  • Include Linux-specific considerations, such as licensing, supported configurations, and any differences in Azure Site Recovery behavior.
  • Balance the coverage of Windows and Linux by providing parallel walkthroughs or tables for both OS types.
  • Mention any Linux tools or patterns relevant to disaster recovery planning alongside Windows/Hyper-V tools.
GitHub Create Pull Request
Site Recovery Migrate on-premises machines to Azure with Azure Migrate ...es/site-recovery/migrate-tutorial-on-premises-azure.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page focuses on migration of VMware and Hyper-V VMs, as well as physical servers, but does not provide explicit examples or guidance for Linux-specific migration scenarios. The order of presentation (VMware, Hyper-V, then physical servers) and lack of Linux tooling or command-line examples (e.g., Bash, SSH, Linux agent installation) suggest a Windows-first bias and missing Linux parity.
Recommendations
  • Add explicit examples and guidance for migrating Linux servers, including common Linux distributions.
  • Include Linux-specific migration considerations, such as handling SSH keys, Linux agent installation, and post-migration steps for Linux workloads.
  • Provide command-line examples using Bash or Linux-native tools alongside any PowerShell or Windows examples.
  • Clarify that Azure Migrate supports both Windows and Linux machines, and link to documentation or tutorials specifically for Linux migration.
  • Mention Linux-specific challenges (e.g., SELinux, systemd services, file permissions) and how Azure Migrate addresses them.
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-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation provides instructions for enabling replication of physical servers to Azure but demonstrates a subtle Windows bias. While both Windows and Linux are mentioned, the examples and screenshots do not show Linux-specific details, and credential instructions list Windows before Linux. There are no explicit Linux command-line examples or references to Linux tools, and the guidance for Linux is limited to a brief note about root credentials. The process and screenshots appear generic but do not illustrate Linux-specific scenarios, such as SSH key usage or Linux service management.
Recommendations
  • Add explicit Linux examples, such as how to provide SSH keys or use sudo/root credentials for agent installation.
  • Include screenshots or walkthroughs showing Linux server registration and replication steps.
  • Mention Linux-specific considerations, such as SELinux, firewall configuration, or service management (systemd).
  • Present Linux instructions before or alongside Windows instructions to avoid ordering bias.
  • Reference Linux command-line tools or scripts where relevant, and provide parity with any PowerShell/Windows tooling mentioned.
GitHub Create Pull Request
Site Recovery Quickstart to create an Azure Recovery Services vault using Bicep. ...rticles/site-recovery/quickstart-create-vault-bicep.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for all steps, but PowerShell is given equal prominence to CLI, despite PowerShell being primarily a Windows tool. There is no mention of Linux-specific patterns, shell environments, or considerations. The examples and instructions do not clarify that Azure CLI is cross-platform and more native to Linux/macOS, while PowerShell is Windows-centric. No Linux-specific guidance or troubleshooting is provided.
Recommendations
  • Explicitly state that Azure CLI is cross-platform and works natively on Linux/macOS, while PowerShell is primarily for Windows.
  • List Azure CLI examples first, as it is the default for Linux/macOS users.
  • Add a note or section for Linux users, including installation instructions for Azure CLI on Linux.
  • Clarify that PowerShell examples are for users who prefer or require Windows tooling.
  • Provide troubleshooting tips or links for common Linux issues (e.g., file permissions, shell differences).
  • Avoid implying parity between PowerShell and CLI unless both are equally supported on all platforms.
GitHub Create Pull Request
Site Recovery Azure Site Recovery Deployment Planner Version History ...e-recovery/site-recovery-deployment-planner-history.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Windows Heavy
Summary
The documentation frequently lists Windows operating systems before Linux equivalents and provides more granular details about Windows support (e.g., specific versions, boot types, compatibility fixes). Linux support is mentioned, but often as a secondary note or in grouped lists, with less detail. There are no Linux-specific examples or troubleshooting notes, and Windows compatibility issues are addressed more directly.
Recommendations
  • List supported Linux distributions and versions with the same granularity as Windows (e.g., specific versions, boot types, compatibility fixes).
  • Include Linux-specific troubleshooting notes and limitations where relevant.
  • Where Windows is mentioned first, alternate ordering or group OS types together to avoid implicit prioritization.
  • Add examples or notes for Linux environments, such as common issues or configuration tips.
  • Ensure parity in known limitations and fixes for both Windows and Linux platforms.
GitHub Create Pull Request
Site Recovery Enable replication for VMware VM disaster recovery to Azure with Azure Site Recovery ...rticles/site-recovery/quickstart-enable-replication.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation mentions both Linux and Windows credentials requirements, but provides more detail for Windows (admin privileges) and does not offer any Linux-specific examples, troubleshooting, or guidance beyond stating 'provide root credentials.' There are no Linux command-line examples, nor are Linux-specific patterns or tools referenced. Windows is mentioned first in the credential note, and there is no parity in example depth for Linux users.
Recommendations
  • Provide explicit Linux credential requirements and examples, such as supported authentication methods (root, sudo, SSH key, etc.), and troubleshooting steps for common Linux issues.
  • Include Linux-specific screenshots or walkthroughs where the process may differ from Windows.
  • Reference Linux command-line tools or patterns (e.g., how to verify agent installation on Linux, relevant log file locations, systemctl/service commands).
  • Ensure Linux is mentioned equally or first when listing OS-specific instructions, or provide parallel instructions for both OSes.
  • Add a section for Linux users covering agent installation, permissions, and best practices.
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-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation provides explicit instructions and command-line examples for Windows (registry modification via REG ADD), but does not offer equivalent Linux commands or detailed steps for Linux systems. Windows-specific steps are described first and in more detail, while Linux is only briefly mentioned ("the account should be root on the source Linux server") without further guidance. No Linux CLI commands or troubleshooting steps are provided.
Recommendations
  • Add equivalent Linux instructions for preparing the source VM, such as commands for configuring necessary permissions or settings.
  • Provide Linux-specific troubleshooting tips, especially for Mobility service installation and connectivity.
  • Include example shell commands (e.g., bash) for Linux where Windows registry or CLI commands are given.
  • Ensure that both Windows and Linux procedures are described with equal detail and clarity, possibly in parallel sections or tables.
  • Mention any Linux-specific requirements or caveats for Azure Site Recovery in this scenario.
GitHub Create Pull Request
Site Recovery Analyze the Deployment Planner report for VMware disaster recovery with Azure Site Recovery ...site-recovery-vmware-deployment-planner-analyze-report.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias primarily in its treatment of EFI virtual machines, where support is explicitly stated for Windows Server EFI VMs (2012, 2012 R2, 2016) but not for Linux EFI VMs. There are no Linux-specific examples, troubleshooting steps, or parity notes, and Windows support is mentioned first and exclusively in relevant sections. The documentation does not provide Linux-specific guidance or examples for analyzing the Deployment Planner report, nor does it clarify limitations or support for Linux EFI VMs.
Recommendations
  • Explicitly state the support status for Linux EFI virtual machines, including any limitations or future plans.
  • Provide Linux-specific examples or troubleshooting steps where relevant, especially in sections discussing VM compatibility and boot types.
  • Ensure that OS-specific instructions (e.g., for mobility service versions, failover/failback support) are provided for both Windows and Linux VMs.
  • Add parity notes or tables summarizing feature support for both Windows and Linux VMs to help administrators plan accordingly.
GitHub Create Pull Request
Site Recovery Shared disks in Azure Site Recovery ...ob/main/articles/site-recovery/tutorial-shared-disk.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation exclusively discusses configuring disaster recovery for Windows Server Failover Clusters (WSFC) on Azure VMs using shared disks. There are no references to Linux-based clustering solutions, nor are there any examples or guidance for Linux environments. All prerequisites, terminology, and linked resources are Windows-centric, indicating a strong Windows-first bias and a lack of Linux parity.
Recommendations
  • Add explicit statements about support (or lack thereof) for Linux-based clusters (e.g., Pacemaker, Corosync) with Azure shared disks and Site Recovery.
  • If Linux clustering is supported, provide equivalent step-by-step instructions and screenshots for setting up disaster recovery for Linux clusters.
  • Include Linux-specific prerequisites, such as supported distributions, required packages, and configuration steps.
  • Reference Linux documentation and tools where appropriate, and ensure that both Windows and Linux scenarios are covered in the support matrix and examples.
  • If only Windows is supported, clearly state this at the beginning of the article to set user expectations.
GitHub Create Pull Request
Site Recovery Install a master target server for Linux VM failback with Azure Site Recovery ...e-recovery/vmware-azure-install-linux-master-target.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation is focused on Linux master target installation, but several steps require access to Windows-based servers and tools. For example, the process server and configuration server paths are given as Windows file paths (e.g., C:\Program Files...), and the passphrase needed for Linux registration is retrieved from a Windows directory. There are no equivalent instructions for Linux-based process/configuration servers, and Windows terminology and paths are presented first and exclusively.
Recommendations
  • Provide instructions for retrieving necessary files (such as installers and passphrases) from Linux-based process/configuration servers, if supported.
  • Clarify whether the process/configuration server must be Windows, or if Linux alternatives exist. If Linux is supported, add parity steps and examples.
  • Where Windows file paths are referenced, offer Linux equivalents or note platform restrictions explicitly.
  • Add a section summarizing platform dependencies and alternatives to ensure Linux administrators understand any Windows requirements.
  • If Windows-only components are required, explain why and suggest workarounds or roadmap for Linux parity.
GitHub Create Pull Request
Site Recovery Set up VMware VM disaster recovery to Azure with Azure Site Recovery - Modernized ...ttps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/vmware-azure-set-up-replication-tutorial-modernized.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a subtle Windows bias. While it mentions both Linux and Windows OS in the context of providing credentials for Mobility Service installation, it gives more detailed instructions for Windows (admin privileges) and only briefly notes Linux (root credentials) without further guidance. There are no Linux-specific examples, commands, or troubleshooting steps, and no mention of Linux deployment patterns or tools. Windows terminology and patterns (such as 'admin privileges') are presented first and in more detail.
Recommendations
  • Provide explicit Linux examples and instructions alongside Windows ones, such as steps for manual Mobility Service installation on Linux (e.g., using shell commands).
  • Include Linux-specific troubleshooting tips and common issues.
  • Mention Linux deployment tools (e.g., Ansible, shell scripts) as alternatives to Configuration Manager for automated agent deployment.
  • Ensure parity in credential requirements by clarifying Linux user requirements and possible security considerations.
  • Where OS-specific instructions are needed, present Linux and Windows options side-by-side, rather than Windows-first.
GitHub Create Pull Request
Site Recovery Troubleshoot failback in VMware VM disaster recovery with Azure Site Recovery ...covery/vmware-azure-troubleshoot-failback-reprotect.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation demonstrates Windows bias by providing more detailed troubleshooting steps and outcomes for Windows VMs compared to Linux VMs. For example, the static IP address issue is described as automatically resolved for Windows VMs, while Linux VMs require manual intervention. There are no Linux-specific troubleshooting commands or examples, and Windows scenarios (e.g., Windows Server 2008 R2 SP1) are mentioned explicitly, while Linux equivalents are not. No Linux tools or patterns are referenced, and troubleshooting steps do not include Linux command-line examples.
Recommendations
  • Provide Linux-specific troubleshooting examples, such as commands to check or restore static IP configuration (e.g., using nmcli or ifconfig).
  • Include parity in troubleshooting steps for both Windows and Linux VMs, detailing how to resolve common issues for each OS.
  • Reference Linux tools (e.g., systemctl, journalctl) when discussing service status checks, alongside Windows equivalents.
  • Explicitly mention Linux distributions and versions where relevant, similar to how Windows Server versions are referenced.
  • Add examples of how to check connectivity and service status on Linux VMs (e.g., using ping, telnet, systemctl) in addition to Windows.
GitHub Create Pull Request
Site Recovery Run VMware VMs failover to Azure ...https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/vmware-azure-tutorial-failover-failback-modernized.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a subtle Windows bias. In the 'Connect to failed-over VM' section, RDP (Windows) is mentioned before SSH (Linux), and the link provided for connecting to a VM after failover points to Windows-specific instructions. There are no explicit Linux or cross-platform examples for connecting to failed-over VMs, nor are Linux-specific troubleshooting steps or considerations provided, despite mentioning that VMware Linux VMs may experience longer failover times.
Recommendations
  • Provide equal prominence to SSH (Linux) and RDP (Windows) when discussing VM connectivity after failover, including links to both Windows and Linux connection guides.
  • Add Linux-specific examples and troubleshooting steps, especially in sections discussing connectivity and failover issues.
  • Include references to Linux tools and commands where relevant, such as using SSH from Linux/macOS terminals.
  • Clarify any differences in failover or recovery steps for Linux VMs, especially where longer failover times are mentioned.
  • Ensure that all instructions and links are platform-neutral or provide alternatives for both Windows and Linux users.
GitHub Create Pull Request
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/azure-to-azure-quickstart.md ...in/articles/site-recovery/azure-to-azure-quickstart.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by linking to Windows-specific VM creation instructions in the prerequisites section and omitting any mention or examples for Linux VMs. All steps and references assume a generic VM but do not provide parity for Linux users, such as links to Linux VM creation or notes about Linux-specific considerations.
Recommendations
  • Include links to both Windows and Linux VM creation guides in the prerequisites section.
  • Add notes or examples that clarify any differences or additional steps required for Linux VMs (e.g., extension installation, OS-specific settings).
  • Ensure screenshots and instructions are OS-agnostic or provide parallel examples for Linux VMs where relevant.
  • Mention any Linux-specific limitations or considerations in the disaster recovery process.
GitHub Create Pull Request
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/azure-to-azure-how-to-enable-replication-private-endpoints.md ...e-to-azure-how-to-enable-replication-private-endpoints.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation consistently references the Azure portal and Azure PowerShell for configuration steps, but does not provide any Linux-specific CLI (az CLI) examples or mention Linux tools or workflows. All step-by-step instructions and screenshots are based on the Azure portal UI, which is platform-agnostic but often more familiar to Windows users. The only command-line reference is to Azure PowerShell, with no mention of Bash, az CLI, or Linux shell equivalents. There are no examples or guidance for users working from Linux environments.
Recommendations
  • Add equivalent az CLI commands for all major steps, such as creating private endpoints, DNS zones, and role assignments.
  • Explicitly mention that all steps can be performed from Linux/macOS using az CLI, and provide links to relevant CLI documentation.
  • Where PowerShell is referenced, offer side-by-side examples for az CLI.
  • Include screenshots or terminal output from Linux environments where appropriate.
  • Clarify that the Azure portal is accessible from any OS, but provide parity for users who prefer command-line workflows on Linux.
GitHub Create Pull Request
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/encryption-feature-deprecation.md ...ticles/site-recovery/encryption-feature-deprecation.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation focuses exclusively on Hyper-V virtual machines, which are a Windows technology, and does not mention or provide guidance for Linux-based VMs or other cross-platform scenarios. All examples and remediation steps are tailored to Windows environments, with no reference to Linux tools, patterns, or equivalent processes.
Recommendations
  • Include information about how the deprecation affects Linux-based VMs or other non-Hyper-V platforms supported by Azure Site Recovery.
  • Provide equivalent remediation steps and examples for Linux VMs, including relevant commands or tools.
  • Clarify whether the deprecation is specific to Hyper-V or if similar actions are needed for other platforms.
  • Add links to documentation for Linux disaster recovery scenarios and encryption at rest for Linux VMs.
GitHub Create Pull Request
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/physical-server-enable-replication.md ...es/site-recovery/physical-server-enable-replication.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
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 when discussing credential requirements, but Windows is listed first and receives slightly more detailed instructions (e.g., 'add a user account with admin privileges' for Windows, versus 'provide the root credentials' for Linux). There are no explicit Linux-specific examples, commands, or screenshots, and no mention of Linux tooling or patterns. The documentation does not provide parity in examples or troubleshooting for Linux environments.
Recommendations
  • Provide explicit Linux examples, such as screenshots of Linux credential entry, or command-line installation instructions for the mobility service on Linux.
  • Include troubleshooting steps or notes specific to Linux environments, such as SELinux, firewall, or SSH configuration considerations.
  • List Linux before or alongside Windows when mentioning supported operating systems to avoid implicit prioritization.
  • Reference Linux tools or patterns (e.g., using sudo, systemd services) where relevant, and ensure parity in guidance for both OS types.
GitHub Create Pull Request
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/site-recovery-vmware-deployment-planner-analyze-report.md ...site-recovery-vmware-deployment-planner-analyze-report.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page references both Windows and Linux virtual machines, but provides more detailed support and examples for Windows (e.g., EFI boot support is described only for Windows Server versions). There are no Linux-specific examples, troubleshooting steps, or parity notes for Linux VMs. Windows features and requirements are mentioned first and in more detail, while Linux is only referenced generically as an OS type.
Recommendations
  • Add explicit Linux support details, including supported distributions, kernel versions, and any limitations for Linux EFI/BIOS VMs.
  • Provide Linux-specific examples for report generation, VM compatibility, and troubleshooting (e.g., how to check disk/IOPS/churn on Linux VMs).
  • Clarify any differences in failover/failback support between Windows and Linux VMs.
  • Include parity notes or tables comparing Windows and Linux support for all relevant features.
  • Mention Linux tools or commands (e.g., for performance profiling or disk checks) alongside any Windows-specific instructions.
GitHub Create Pull Request
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/vmware-azure-set-up-process-server-azure.md ...e-recovery/vmware-azure-set-up-process-server-azure.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Missing Linux Example 🔧 Windows Tools
Summary
The documentation page implicitly assumes the process server VM will be Windows-based, as it requests 'User name' and 'Password' with Admin permissions, and does not mention Linux as a supported OS or provide any Linux-specific guidance. There are no Linux examples, nor is there mention of Linux tools or patterns. The steps and terminology (e.g., 'Admin permissions') are Windows-centric, and there is no indication that deploying a Linux-based process server is possible or supported.
Recommendations
  • Explicitly state whether Linux-based process servers are supported or not. If supported, provide parallel instructions for deploying and configuring a Linux process server VM.
  • Include Linux-specific terminology (e.g., 'root' or 'sudo' privileges) alongside 'Admin permissions' when discussing credentials.
  • If only Windows is supported, clarify this early in the documentation to set expectations.
  • Provide example screenshots and command-line instructions for both Windows and Linux where applicable.
  • Reference Linux tools or patterns (such as SSH key authentication, Linux VM images, or package installation commands) if Linux is supported.
GitHub Create Pull Request
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/azure-to-azure-autoupdate.md ...in/articles/site-recovery/azure-to-azure-autoupdate.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example
Summary
The documentation provides only Azure PowerShell script examples for managing Mobility service automatic updates, with no equivalent examples for Linux shell (bash/CLI) or cross-platform automation. The troubleshooting and management instructions are generic, but all code samples and automation references are Windows/PowerShell-centric, which may disadvantage Linux administrators or those using Azure CLI/bash.
Recommendations
  • Add equivalent Azure CLI (az) and bash script examples for managing Mobility service updates, especially for automation scenarios.
  • Explicitly mention that the automation and update process is supported for both Windows and Linux VMs, and clarify any OS-specific requirements or differences.
  • Provide troubleshooting steps and repair instructions that include Linux-specific guidance, such as using SSH or Linux-native tools.
  • Where PowerShell is used, note its cross-platform availability, but also offer bash/CLI alternatives for Linux users.
  • Include links or references to Linux-focused documentation for Azure Site Recovery and Mobility service management.
GitHub Create Pull Request
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/azure-to-azure-move-overview.md ...articles/site-recovery/azure-to-azure-move-overview.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation page shows mild Windows bias, notably by referencing Windows-specific concepts and links before Linux equivalents. For example, the availability sets section links to a Windows VM tutorial, and the database tier example uses SQL Server Always On, a Windows-centric technology. There are no explicit Linux or cross-platform examples, nor are Linux tools or patterns mentioned.
Recommendations
  • Include examples and links for both Windows and Linux VM scenarios, such as referencing Linux VM availability set documentation.
  • Mention database technologies common on Linux (e.g., MySQL, PostgreSQL) alongside SQL Server in architecture examples.
  • Ensure that cross-platform patterns and tools are described, and avoid linking only to Windows-specific tutorials.
  • Add explicit Linux VM migration steps or considerations if any differ from Windows.
  • Balance references to Windows and Linux in diagrams, examples, and further reading sections.
GitHub Create Pull Request
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/concepts-azure-to-azure-high-churn-support.md ...recovery/concepts-azure-to-azure-high-churn-support.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation mentions supported operating systems for Enhanced Churn (Windows, Linux – RHEL 9, SLES 15, Ubuntu 24.04), but Windows is listed first and there are no Linux-specific instructions, screenshots, or examples. All configuration steps and UI screenshots are generic and do not address Linux-specific considerations, such as agent installation, permissions, or troubleshooting. There is no mention of Linux command-line tools or patterns, nor any PowerShell bias, but the lack of Linux parity in examples and guidance constitutes a bias.
Recommendations
  • Explicitly include Linux-specific instructions or considerations for enabling High Churn support, such as agent installation, required packages, or permissions.
  • Add Linux-focused screenshots or CLI examples (e.g., using Azure CLI or Bash) for configuring Site Recovery and High Churn, alongside portal steps.
  • Clarify any differences in behavior, limitations, or troubleshooting steps for supported Linux distributions (RHEL 9, SLES 15, Ubuntu 24.04).
  • Ensure that any OS-specific requirements (e.g., kernel versions, disk formatting, etc.) are documented for Linux VMs.
  • List supported operating systems in alphabetical order or group them together to avoid implicit prioritization.
GitHub Create Pull Request
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/azure-to-azure-tutorial-migrate.md ...icles/site-recovery/azure-to-azure-tutorial-migrate.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates Windows bias by providing explicit instructions for updating root certificates on Windows VMs, including references to Windows Update and certificate update processes, while only briefly mentioning Linux VMs and deferring to distributor guidance without concrete steps or examples. No Linux-specific commands, tools, or update patterns are provided, and Windows instructions appear first and in greater detail.
Recommendations
  • Provide step-by-step guidance for updating root certificates on popular Linux distributions (e.g., Ubuntu, CentOS, RHEL), including example commands.
  • Include parity in troubleshooting steps for Linux VMs, such as how to verify certificate installation and update status.
  • List Linux-specific considerations for Azure Site Recovery, such as handling SELinux, firewalls, or common Linux networking patterns.
  • Ensure that instructions for both Windows and Linux VMs are presented with equal detail and visibility, ideally side-by-side or in clearly separated sections.
  • Reference official Linux documentation for certificate management and updates, and link to relevant Azure Linux VM documentation.
GitHub Create Pull Request
← Previous Page 30 of 35 Next →