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 301-325 of 864 flagged pages
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/physical-azure-set-up-source.md ...articles/site-recovery/physical-azure-set-up-source.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 a Windows bias by referencing Windows-specific requirements (such as .NET Framework and TLS settings), linking to Windows time service documentation, and omitting explicit Linux setup instructions or examples. All examples and tool references (Unified Setup, time synchronization) are Windows-centric, with no parity for Linux environments.
Recommendations
  • Add explicit instructions and examples for setting up the configuration server on Linux, including supported distributions and required dependencies.
  • Provide Linux equivalents for system requirements (e.g., alternative to .NET Framework, TLS configuration steps for Linux).
  • Include links to Linux time synchronization documentation (e.g., NTP setup) alongside the Windows time service link.
  • Clarify whether the 'Unified Setup' installer is supported on Linux, and if not, provide alternative installation methods for Linux environments.
  • Ensure screenshots and step-by-step guides include Linux scenarios where applicable.
GitHub Create Pull Request
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/physical-server-azure-architecture-modernized.md ...overy/physical-server-azure-architecture-modernized.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 discusses disaster recovery for both Windows and Linux servers, but exhibits Windows bias in several areas. Windows terminology and technologies (e.g., VSS, SQL Server) are described in detail, while Linux equivalents are not mentioned. Examples and technical details (such as app-consistent snapshot mechanisms) are Windows-centric, with no Linux-specific instructions or references to Linux tools (e.g., LVM snapshots, fsfreeze, etc.). The documentation does not provide parity in examples, troubleshooting, or architectural notes for Linux systems.
Recommendations
  • Add Linux-specific examples and instructions for installing and configuring the Mobility Service, including manual installation steps for common distributions.
  • Describe how app-consistent snapshots are achieved on Linux (e.g., use of pre/post scripts, LVM snapshots, fsfreeze), and clarify differences from Windows VSS.
  • Include troubleshooting steps and recommendations for Linux systems, such as handling disk resizing, force shutdown, or file system consistency.
  • Mention Linux-specific considerations for recovery, failover, and failback, including supported file systems and application consistency strategies.
  • Ensure that examples and technical details are presented for both Windows and Linux, or clearly indicate platform-specific differences where applicable.
GitHub Create Pull Request
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/region-move-cross-geos.md .../main/articles/site-recovery/region-move-cross-geos.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in several areas: registry modification instructions and CLI examples are provided only for Windows (using REG ADD), with no equivalent Linux commands or configuration details. Windows-specific setup steps (such as registry changes for Remote User Access control) are explained in detail, while Linux instructions are minimal and lack command-line examples. The order of presentation also places Windows instructions before Linux, and references to Windows tools (registry editor, REG ADD) are present, but no Linux tools (e.g., shell commands) are mentioned.
Recommendations
  • Provide equivalent Linux command-line instructions for required configuration changes (e.g., how to prepare the root account, any necessary SSH or sudo configuration).
  • Include Linux-specific examples and troubleshooting steps alongside Windows instructions, not just as a brief mention.
  • Ensure parity in detail and clarity for both Windows and Linux, including explicit commands, file locations, and configuration steps.
  • Where Windows registry changes are described, offer corresponding Linux configuration file edits or commands if applicable.
  • Avoid presenting Windows instructions first by grouping OS-specific steps together or presenting them in parallel.
GitHub Create Pull Request
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/site-recovery-active-directory.md ...ticles/site-recovery/site-recovery-active-directory.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 demonstrates a strong Windows bias. All examples, tools, and procedures are centered around Windows Server, Active Directory, and DNS as implemented on Windows. Only Windows-specific tools (e.g., ntdsutil.exe, dcdiag, nltest, dnscmd, registry edits) are mentioned, with no reference to Linux-based equivalents or scenarios. The documentation assumes the use of Windows domain controllers and does not provide guidance for Linux-based DNS or directory services. Windows terminology and links to Microsoft documentation are used exclusively, and there are no examples or instructions for Linux environments.
Recommendations
  • Add sections or examples for disaster recovery of Linux-based DNS servers (e.g., BIND, Unbound) and directory services (e.g., OpenLDAP, FreeIPA).
  • Include Linux command-line equivalents for DNS and directory service management (e.g., dig, nsupdate, ldapsearch).
  • Provide guidance for configuring Azure Site Recovery with Linux VMs hosting DNS or directory services.
  • Mention Linux-specific considerations for failover, network configuration, and test failover scenarios.
  • Balance references to Windows tools with Linux alternatives, and avoid assuming Windows-only environments.
  • Link to relevant Linux documentation and resources for further reading.
GitHub Create Pull Request
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/site-recovery-extension-troubleshoot.md .../site-recovery/site-recovery-extension-troubleshoot.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation demonstrates a Windows bias by consistently listing Windows troubleshooting steps and examples before Linux equivalents, providing more detailed instructions for Windows (including use of Windows-specific tools like services.msc and Control Panel), and omitting comparable Linux troubleshooting details (e.g., how to check agent status or uninstall/reinstall the agent on Linux). Windows tools and patterns are referenced explicitly, while Linux instructions are more generic and less actionable.
Recommendations
  • Present Linux and Windows troubleshooting steps in parallel, or alternate which platform is listed first.
  • Provide Linux-specific instructions for checking agent status (e.g., using systemctl, ps, or service commands) and uninstalling/reinstalling the agent.
  • Include Linux command-line examples for all steps given for Windows, such as verifying installation, restarting services, and checking dependencies.
  • Reference Linux equivalents for Windows tools (e.g., instead of services.msc, show how to check service status on Linux).
  • Ensure parity in detail and actionable steps for both platforms throughout the documentation.
GitHub Create Pull Request
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/shared-disk-support-matrix.md ...n/articles/site-recovery/shared-disk-support-matrix.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 exclusively references Windows workloads, Windows Server SKUs, and Windows Server Failover Clustering (WSFC) as the supported platform and clustering solution for shared disks in Azure Site Recovery. There are no mentions of Linux virtual machines, Linux clustering solutions (such as Pacemaker or Corosync), or examples relevant to Linux environments. This demonstrates a clear Windows bias, both in the order of presentation and in the omission of Linux equivalents.
Recommendations
  • Explicitly state whether Linux virtual machines and Linux clustering solutions are supported or not for shared disks in Azure Site Recovery.
  • If Linux is supported, add equivalent examples and support matrices for Linux workloads, including supported distributions, clustering configurations (e.g., Pacemaker, Corosync), and disk partitioning types.
  • If Linux is not supported, clarify this in the documentation to help users plan accordingly.
  • Include references or links to Linux-specific disaster recovery documentation if available.
  • Consider adding a section that compares Windows and Linux support for shared disks in Azure Site Recovery to provide parity and transparency.
GitHub Create Pull Request
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/site-recovery-dynamicsax.md ...ain/articles/site-recovery/site-recovery-dynamicsax.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 oriented toward Windows environments, specifically referencing Windows Server, Active Directory, SQL Server, and Dynamics AX components that are Windows-only. All examples, prerequisites, and recovery steps assume Windows-based infrastructure, with no mention of Linux equivalents, alternative open-source tools, or cross-platform considerations. There are no Linux-specific instructions, examples, or references to Linux-compatible disaster recovery patterns.
Recommendations
  • Explicitly state platform requirements and limitations at the beginning, clarifying that Dynamics AX is Windows-only and that the guidance is not applicable to Linux environments.
  • If Azure Site Recovery supports Linux workloads, add a section or links to documentation for disaster recovery of Linux-based applications, including example scenarios, prerequisites, and recovery steps.
  • Provide parity in examples by including Linux VM protection and failover instructions where relevant, or reference equivalent documentation for Linux environments.
  • Mention open-source or Linux-native alternatives for components such as DNS, directory services, and database replication, where applicable.
  • Ensure that cross-platform customers are guided to appropriate resources for non-Windows workloads.
GitHub Create Pull Request
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/site-recovery-iis.md .../blob/main/articles/site-recovery/site-recovery-iis.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 IIS on Windows Server and related Windows-centric tools and patterns. All examples, deployment patterns, and scripts are tailored for IIS (a Windows-only web server), with no mention of Linux-based web servers (such as Apache or Nginx) or Linux disaster recovery scenarios. The scripting examples reference PowerShell scripts and IIS-specific operations, further reinforcing the Windows bias. There is no guidance for Linux VMs, web apps, or cross-platform parity.
Recommendations
  • Add equivalent disaster recovery guidance for Linux-based web applications (e.g., Apache, Nginx) running on Linux VMs.
  • Include examples and scripts for updating configuration files, bindings, and certificates on Linux web servers.
  • Mention Linux tools and scripting options (such as Bash, sed, systemctl) alongside PowerShell and Windows tools.
  • Clarify whether Azure Site Recovery supports Linux VMs and provide links to relevant documentation.
  • Present deployment patterns and recovery plan steps for both Windows and Linux environments, or explicitly state the Windows-only scope.
GitHub Create Pull Request
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/site-recovery-failover.md .../main/articles/site-recovery/site-recovery-failover.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias 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 instructions are comparatively brief and lack equivalent detail or troubleshooting guidance. Examples and troubleshooting links are Windows-centric, and Linux scenarios are not covered with the same depth or parity.
Recommendations
  • Present Linux and Windows instructions side-by-side, or alternate which comes first to avoid implicit prioritization.
  • Expand Linux guidance to match the detail given for Windows, including troubleshooting steps, firewall configuration, and common connectivity issues.
  • Include Linux-specific tools and patterns (e.g., SSH configuration, iptables/firewalld, systemd services, proxy settings) where Windows tools are mentioned.
  • Provide links to Linux troubleshooting resources, similar to those given for Windows (e.g., SSH connectivity troubleshooting after failover).
  • Clarify any OS-specific requirements for failover and failback processes, such as handling updates, persistent routes, or SAN policies for Linux.
  • Ensure automation and scripting examples include Linux shell scripts or Ansible playbooks, not just Windows-centric approaches.
GitHub Create Pull Request
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/site-recovery-plan-capacity-vmware.md ...es/site-recovery/site-recovery-plan-capacity-vmware.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 exhibits a Windows bias in several areas. Windows-specific tools (MMC snap-in, registry keys, PowerShell cmdlets) are referenced exclusively or before Linux alternatives. Examples for bandwidth throttling and configuration changes are provided only for Windows (MMC, registry, PowerShell), with no equivalent Linux instructions. The documentation discusses deploying master target servers for Linux, but operational examples and configuration steps are primarily Windows-centric.
Recommendations
  • Provide Linux-specific instructions for bandwidth throttling and configuration changes, such as relevant commands, config files, or scripts.
  • Include Linux equivalents for registry-based settings (e.g., config files or environment variables used by the replication agent on Linux).
  • Offer CLI or shell script examples for Linux environments alongside PowerShell examples.
  • Mention Linux tools or utilities (e.g., systemd, cron, network configuration commands) where applicable.
  • Ensure that operational steps (such as installing or configuring process/master target servers) are documented for both Windows and Linux, with screenshots and step-by-step guidance.
  • Clearly indicate when a procedure is OS-specific and provide parity in documentation structure and detail.
GitHub Create Pull Request
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/site-recovery-runbook-automation.md ...cles/site-recovery/site-recovery-runbook-automation.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 Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a strong Windows bias. All code samples and automation instructions use PowerShell, with no mention of Bash, Python, or Linux-native scripting. Azure PowerShell modules and cmdlets are referenced exclusively, and there are no examples or guidance for Linux users or cross-platform scripting. The documentation assumes familiarity with Windows tooling and does not address how to perform equivalent tasks from Linux environments.
Recommendations
  • Provide equivalent examples using Bash, Python, or Azure CLI to demonstrate cross-platform automation.
  • Mention and link to Azure CLI documentation and usage for runbook scripting, especially for Linux users.
  • Clarify whether Azure Automation runbooks can be authored in languages other than PowerShell, and provide examples if so.
  • Add a section discussing considerations for Linux-based VMs and recovery plan automation.
  • Ensure that instructions for module installation and script deployment include both Windows and Linux environments.
GitHub Create Pull Request
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/site-recovery-manage-registration-and-protection.md ...ry/site-recovery-manage-registration-and-protection.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation is heavily focused on Windows environments, specifically System Center VMM, Hyper-V, and PowerShell scripts. All example scripts and procedures use Windows-specific tools and commands, with no mention of Linux equivalents or scenarios. There are no examples for unregistering or disabling protection for Linux servers, nor are there any bash or shell script examples. Windows tools and workflows are presented exclusively and first throughout the document.
Recommendations
  • Add equivalent instructions and examples for Linux servers, including how to unregister and disable protection for Linux-based VMs and physical servers.
  • Provide bash or shell script examples for cleanup and unregistration tasks on Linux systems.
  • Include references to Linux tools (such as systemctl, cron, etc.) where applicable, and clarify any differences in workflows between Windows and Linux environments.
  • Structure the documentation to present both Windows and Linux procedures in parallel, or clearly indicate which steps apply to each platform.
  • Explicitly state platform limitations or support (e.g., if certain features are Windows-only), and provide guidance for Linux users.
GitHub Create Pull Request
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/site-recovery-overview.md .../main/articles/site-recovery/site-recovery-overview.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by prioritizing Windows-centric technologies and scenarios. Windows tools and patterns (e.g., Windows Server Failover Clusters, SQL Server Always On, shared disk for Windows workloads) are mentioned explicitly and in detail, while Linux equivalents are either absent or referenced only generically. Replication scenarios and workload examples consistently list Windows first, and there are no specific examples or guidance for Linux workloads, clustering, or automation integration.
Recommendations
  • Add explicit examples and guidance for Linux workloads, such as replicating Linux VMs and physical servers, including supported distributions and any special considerations.
  • Include Linux clustering technologies (e.g., Pacemaker, Corosync) in the shared disk and failover cluster sections, with instructions for protecting and failing over Linux-based clusters.
  • Provide parity in automation integration by referencing Linux-compatible scripting and automation tools (e.g., Bash, Python, Ansible) alongside PowerShell and Azure Automation.
  • Ensure that replication scenarios and workload lists alternate or balance Windows and Linux mentions, rather than listing Windows first or exclusively.
  • Add links to Linux-specific support matrices, best practices, and troubleshooting guides for disaster recovery and failover in Azure Site Recovery.
GitHub Create Pull Request
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/site-recovery-sap.md .../blob/main/articles/site-recovery/site-recovery-sap.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by focusing exclusively on SAP NetWeaver deployments in Windows environments, referencing Windows Server Failover Cluster, SIOS DataKeeper, and Windows-specific clustering features (SOFS, S2D). There are no examples, guidance, or recommendations for SAP deployments on Linux, nor are Linux clustering or replication tools mentioned. The documentation assumes Windows as the default platform for SAP NetWeaver on Azure.
Recommendations
  • Add explicit guidance and examples for SAP NetWeaver deployments on Linux, including supported disaster recovery architectures.
  • Include references to Linux clustering solutions (e.g., Pacemaker, Corosync, DRBD) and how they integrate with Azure Site Recovery.
  • Provide parity in instructions for failover, recovery plans, and scripting for Linux-based SAP environments.
  • Mention any Azure Site Recovery limitations or considerations specific to Linux VMs.
  • Ensure diagrams and reference architectures include both Windows and Linux deployment scenarios.
GitHub Create Pull Request
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/site-recovery-sharepoint.md ...ain/articles/site-recovery/site-recovery-sharepoint.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example Powershell Heavy 🔧 Windows Tools
Summary
The documentation page exhibits a Windows bias by exclusively referencing Windows Server, SharePoint, and SQL Server—all Windows-only products. All examples and instructions assume Windows environments, with no mention of Linux-based SharePoint alternatives or guidance for Linux VMs. Script automation relies on SharePoint PowerShell cmdlets and Windows-specific tools (e.g., DFSR, Restore-SPEnterpriseSearchServiceApplication), and there are no Linux shell or cross-platform script examples. The documentation also refers to Windows tools (DFSR, Central Administration GUI) and patterns before any Linux equivalents, which are not mentioned at all.
Recommendations
  • Include guidance for disaster recovery of SharePoint alternatives or similar multi-tier applications running on Linux (e.g., Alfresco, Nextcloud, or other open-source collaboration platforms).
  • Provide examples for replicating Linux-based VMs and handling failover, including automation scripts using Bash, Python, or Azure CLI.
  • Mention Linux-compatible backup and restore tools and procedures, such as rsync, cron jobs, or native database backup utilities.
  • Clarify which steps are Windows-specific and offer Linux equivalents where possible (e.g., updating DNS records, configuring load balancers, restoring databases).
  • Add references to Linux documentation and best practices for Azure Site Recovery with Linux workloads.
GitHub Create Pull Request
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/site-recovery-whats-new-archive.md ...icles/site-recovery/site-recovery-whats-new-archive.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 Powershell Heavy
Summary
The documentation page for Azure Site Recovery updates generally lists Windows features and support before Linux equivalents, especially in tables and feature lists. Windows-specific tools and patterns (e.g., PowerShell, servicing stack updates, SHA-2 requirements) are referenced without Linux alternatives or parity in explanation. Some features (like firewall-enabled storage) are described as supported via PowerShell, with no mention of Linux CLI or cross-platform tooling. Although Linux support is regularly mentioned, examples and tooling references are often Windows-centric or Windows-first.
Recommendations
  • Ensure that examples and tooling references (such as PowerShell) are accompanied by Linux equivalents (e.g., Azure CLI, Bash scripts) where possible.
  • When listing supported operating systems or features, alternate the order or explicitly state Linux and Windows parity, rather than listing Windows first.
  • Add cross-platform instructions and examples for common tasks (e.g., configuring storage, failover, updates) to avoid implying Windows-only workflows.
  • Where Windows-specific requirements (servicing stack, SHA-2) are mentioned, clarify Linux requirements or state if not applicable.
  • Review feature tables and update notes to ensure Linux features are described with equal detail and prominence as Windows features.
GitHub Create Pull Request
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/site-recovery-workload.md .../main/articles/site-recovery/site-recovery-workload.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by prioritizing Windows workloads, tools, and technologies (e.g., Active Directory, Exchange, SharePoint, IIS, SQL Server, Dynamics AX, Remote Desktop Services) in both the workload summary and detailed sections. Windows-centric applications are described in detail, with integration and recovery features highlighted. Linux is mentioned only briefly and generically, without specific examples, tools, or application guidance. There are no Linux-specific application scenarios, nor are open-source equivalents to Windows tools discussed.
Recommendations
  • Add detailed Linux application examples (e.g., Apache, NGINX, PostgreSQL, MySQL, Samba, OpenLDAP) and describe how Site Recovery supports their disaster recovery.
  • Provide parity in guidance for Linux-based workloads, including step-by-step instructions and integration details similar to those given for Windows workloads.
  • Include references to Linux-specific tools and patterns (e.g., systemd, cron, shell scripts) for automation and recovery plan integration.
  • Highlight open-source alternatives to Windows technologies and explain how Site Recovery can be used with them.
  • Ensure that Linux workloads are not grouped generically, but receive the same level of detail and attention as Windows workloads throughout the documentation.
GitHub Create Pull Request
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/site-recovery-sql.md .../blob/main/articles/site-recovery/site-recovery-sql.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation page demonstrates a Windows bias by referencing Windows-specific SQL Server features (e.g., Always On availability groups, Failover Clustering) and linking primarily to Windows documentation. Examples and instructions (such as PowerShell scripts and Task Manager usage) are Windows-centric, with no mention of Linux equivalents or guidance for SQL Server on Linux. There are no Linux-specific disaster recovery instructions, tools, or examples, and Windows terminology and tools (e.g., Task Manager, PowerShell) are used exclusively.
Recommendations
  • Include explicit guidance and examples for SQL Server running on Linux, such as using Pacemaker for high availability and disaster recovery.
  • Provide Linux-specific instructions for monitoring disk write rates (e.g., using iostat or atop) instead of referencing Windows Task Manager.
  • Offer PowerShell alternatives for Linux environments, such as Bash scripts or Ansible playbooks, for automation steps.
  • Link to SQL Server on Linux documentation for features like Always On availability groups, and clarify any differences in setup or failover procedures.
  • Add parity in screenshots and walkthroughs for Linux-based deployments, including cluster setup and failover testing.
  • Clearly state platform-specific limitations or differences in Azure Site Recovery support for SQL Server on Linux.
GitHub Create Pull Request
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/site-recovery-vmware-deployment-planner-run.md ...ecovery/site-recovery-vmware-deployment-planner-run.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation exhibits a strong Windows bias. All command-line examples use Windows paths and syntax, and the only method provided for listing VMware VMs is via VMware vSphere PowerCLI (PowerShell), with no mention of Linux alternatives. The tool itself (ASRDeploymentPlanner.exe) is a Windows executable, and report generation explicitly requires a Windows PC or Server with Microsoft Excel. There are no Linux or cross-platform instructions, examples, or tool support mentioned.
Recommendations
  • Provide Linux-compatible instructions for listing VMware VMs, such as using 'govc', 'vim-cmd', or 'pyvmomi' scripts.
  • Clarify whether the ASRDeploymentPlanner tool can run under Wine or on Linux, or provide a Linux-native version if possible.
  • Offer examples using Linux file paths and shell syntax alongside Windows examples.
  • Document any prerequisites or limitations for non-Windows users, and suggest workarounds or alternatives.
  • Consider supporting report output formats that do not require Microsoft Excel (e.g., CSV, HTML, or open document formats).
GitHub Create Pull Request
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/site-recovery-whats-new.md ...main/articles/site-recovery/site-recovery-whats-new.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a mild Windows bias. Windows versions and appliances are mentioned explicitly and sometimes before Linux equivalents (e.g., 'Windows 2025', 'Windows 2022 appliance OVA', 'Windows 11 server', 'Windows Server 2019 as the replication appliance'). Windows-specific tooling (e.g., 'Microsoft Edge as default browser', 'Recovery Services agent') is referenced, while Linux equivalents are not described. There are no command-line examples, but the update tables and feature lists often highlight Windows support and tools, with Linux support mostly listed as new distro/kernel additions. Linux-specific tools, patterns, or troubleshooting steps are not covered, and there is no parity in examples or operational guidance for Linux users.
Recommendations
  • Add Linux-specific operational examples, such as update installation steps for agents on Linux systems.
  • Include parity for tooling references (e.g., mention Linux browsers, Linux-based configuration managers, or troubleshooting tools).
  • When listing supported platforms, alternate the order between Windows and Linux, or group by scenario rather than OS.
  • Provide explicit guidance for Linux users, such as troubleshooting steps, agent management, or configuration workflows.
  • Ensure that any Windows-specific features/tools are matched with Linux equivalents or note their absence.
GitHub Create Pull Request
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/unregister-vmm-server-script.md ...articles/site-recovery/unregister-vmm-server-script.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation is heavily biased towards Windows, with the only example provided being a large PowerShell script that relies on Windows-specific features such as the registry (HKLM), Windows services (SCVMMService, ClusSvc), Windows Failover Clustering, and Windows authentication. There is no mention of Linux equivalents, nor are there any examples or guidance for running similar operations on Linux-based VMM servers or environments.
Recommendations
  • Clarify in the introduction whether the procedure is only supported on Windows, and if so, explicitly state that Linux is not supported.
  • If Linux-based VMM servers are supported, provide equivalent scripts or instructions for Linux environments (e.g., Bash, Python, or Ansible), including how to interact with the VMM database and perform cleanup.
  • Mention any Linux tools or patterns that could be used for similar tasks, such as systemd for service management, or alternatives to registry manipulation.
  • If the product is Windows-only, add a note explaining the platform limitation to avoid confusion for Linux users.
  • Consider providing a table or section comparing Windows and Linux approaches (if applicable), or linking to Linux-specific documentation if available.
GitHub Create Pull Request
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/vmware-azure-enable-replication.md ...icles/site-recovery/vmware-azure-enable-replication.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits Windows bias in several ways: Windows operating system requirements and features are mentioned explicitly and prominently (e.g., UEFI support only for Windows), PowerShell is referenced as the primary automation tool with no mention of Linux CLI or scripting alternatives, and Windows-specific licensing benefits (Azure Hybrid Benefit) are described in detail. There are no Linux-specific examples, tools, or considerations, and Windows patterns/tools are presented first or exclusively.
Recommendations
  • Add equivalent Linux automation examples, such as using Azure CLI or REST API from Linux environments, alongside PowerShell instructions.
  • Explicitly document support and requirements for Linux VMs, including any differences in replication, disk formats, or boot methods.
  • Include Linux-specific troubleshooting steps and considerations, especially for process server setup and agent installation.
  • Mention Linux licensing or cost-saving options if available, or clarify that Azure Hybrid Benefit is Windows-only.
  • Ensure that examples and screenshots include both Windows and Linux VMs where applicable, not just Windows-centric scenarios.
GitHub Create Pull Request
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/vmware-azure-failback.md ...b/main/articles/site-recovery/vmware-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 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits Windows bias by specifically mentioning Windows VMs in its notes (e.g., handling of VMware tools during failover/failback for Windows VMs), while omitting equivalent details or considerations for Linux VMs. There are no Linux-specific examples, troubleshooting steps, or notes about differences in failback behavior or tooling for Linux VMs. The only OS-specific guidance is for Windows, and Windows tools are referenced without Linux parity.
Recommendations
  • Add explicit guidance for Linux VMs, including any differences in failback behavior, agent registration, and handling of VMware tools.
  • Include troubleshooting notes and examples for Linux VMs, similar to those provided for Windows VMs.
  • If there are no differences for Linux, state this explicitly to reassure Linux users.
  • Reference Linux-specific tools or commands where relevant, and ensure parity in documentation coverage for both Windows and Linux environments.
GitHub Create Pull Request
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/upgrade-mobility-service-modernized.md ...s/site-recovery/upgrade-mobility-service-modernized.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation demonstrates a Windows bias in several areas: Windows update instructions and tools (e.g., Registry Editor, .msi installers, command prompt) are presented first and in greater detail, with Linux instructions often appearing later or being less comprehensive. Appliance component update procedures and troubleshooting are almost exclusively described using Windows tools and patterns, with little to no mention of Linux equivalents or parity. Some manual update examples and troubleshooting steps are missing for Linux environments.
Recommendations
  • Present Linux and Windows instructions side-by-side or in parallel sections to ensure equal visibility.
  • Include Linux-specific procedures for appliance component updates, such as using shell commands, package managers, or configuration files instead of Windows Registry Editor and .msi installers.
  • Add troubleshooting steps and examples for Linux environments, including how to check versions, resolve blocking issues, and verify updates.
  • Avoid using Windows terminology (e.g., Registry Editor, command prompt) exclusively; provide Linux equivalents (e.g., editing config files, using terminal commands).
  • Ensure that all command-line examples and update procedures are equally detailed for both platforms.
GitHub Create Pull Request
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/vmware-azure-deploy-configuration-server.md ...e-recovery/vmware-azure-deploy-configuration-server.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 a Windows bias in several ways. The configuration server is deployed as a Windows Server 2016 VM, and all setup instructions, screenshots, and tool references are Windows-centric. Steps for installing required software (e.g., MySQL) reference Windows file paths and installation methods, with no Linux equivalents or examples. The documentation does not mention or provide guidance for deploying the configuration server on Linux, nor does it offer Linux-specific troubleshooting or management instructions.
Recommendations
  • Provide explicit guidance for deploying the configuration server on Linux-based VMs if supported, or clarify platform limitations.
  • Include Linux-specific examples for steps such as software installation (e.g., MySQL), file paths, and credential requirements.
  • Add troubleshooting and management instructions relevant to Linux environments.
  • If the configuration server is Windows-only by design, state this clearly at the beginning of the documentation to set expectations for Linux users.
  • Ensure parity in examples and screenshots for both Windows and Linux where applicable.
GitHub Create Pull Request
← Previous Page 13 of 35 Next →