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 601-625 of 864 flagged pages
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-14 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation provides detailed, step-by-step instructions and screenshots for Windows servers, including PowerShell commands and Windows-specific tools (diskpart, registry editing, driver lists), with Windows examples and screenshots shown first. Linux instructions are present and reasonably detailed, but lack equivalent screenshots, and some Linux steps are described in a more generic way (e.g., 'consult your distribution's documentation'), with fewer concrete command examples. Windows tooling and patterns (PowerShell, diskpart) are highlighted, while Linux equivalents (e.g., systemctl, parted, etc.) are not mentioned or shown.
Recommendations
  • Add Linux command-line examples for key steps, such as checking DHCP service status, mounting partitions, and validating agent installation (e.g., using systemctl, lsblk, etc.).
  • Include screenshots or terminal output examples for Linux steps, similar to those provided for Windows.
  • Present Windows and Linux instructions in parallel or in a more balanced way, rather than listing Windows first and in greater detail.
  • Reference Linux-specific troubleshooting articles and tools where appropriate.
  • Clarify any steps that require manual intervention for Linux users, and provide concrete commands or scripts where possible.
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-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation covers both Windows and Linux physical servers for Azure Site Recovery, but there is a notable Windows-first bias. Windows-specific instructions (such as registry edits and CLI commands using REG) are provided in detail, while Linux instructions are minimal (e.g., 'use root account'), with no equivalent Linux command-line examples or troubleshooting steps. Windows tools and patterns (registry, domain/local accounts) are described first and in more depth, and Linux users may need to infer steps or consult external resources.
Recommendations
  • Provide equivalent Linux command-line instructions for Mobility service installation and configuration (e.g., how to prepare the root account, required permissions, and any SELinux/AppArmor considerations).
  • Include troubleshooting steps for common Linux issues (e.g., time synchronization using ntpd/chrony, firewall configuration using iptables/firewalld/ufw).
  • Add explicit examples for Linux environments where Windows registry or domain/local account steps are described for Windows.
  • Ensure screenshots and walkthroughs show both Windows and Linux server scenarios where applicable.
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-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page exhibits moderate Windows bias in the section about configuring the Microsoft monitoring agent for churn and upload rate logs. Only Windows Server is mentioned as a supported platform for the agent, and all instructions and screenshots reference Windows-specific tools (Windows Agent, Windows Performance Counters). There are no instructions or examples for installing or configuring the monitoring agent on Linux-based Process Servers, nor is it clarified whether Linux is supported. The rest of the documentation (log queries, alerts, etc.) is platform-neutral, but the agent setup section creates friction for Linux users.
Recommendations
  • Clarify whether Linux-based Process Servers are supported for churn/upload rate monitoring. If supported, provide equivalent instructions and screenshots for Linux (e.g., agent installation, configuring performance counters, etc.).
  • If Linux is not supported, explicitly state this limitation to help users plan accordingly.
  • Where possible, mention cross-platform alternatives or note any differences in setup between Windows and Linux.
  • Consider listing both Windows and Linux agent download links and setup steps if both are supported.
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-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation presents Windows monitoring tools (Resource Monitor, Performance Monitor) in greater detail, with step-by-step instructions and screenshots, while Linux tools (iotop, iostat) are only briefly mentioned without usage examples or screenshots. Windows tools are described first and more thoroughly, creating a notable imbalance in guidance for Linux users.
Recommendations
  • Provide step-by-step instructions for using Linux tools (iotop, iostat), similar to the Windows sections.
  • Include screenshots or sample outputs for Linux tools to match the detail given for Windows.
  • Mention additional Linux monitoring tools (e.g., atop, dstat, sar) for broader coverage.
  • Ensure parity in troubleshooting guidance and actionable next steps for both platforms.
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-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides setup instructions for Azure Site Recovery configuration server for both Windows and Linux physical servers, but the actual installation steps and troubleshooting are written with a strong Windows focus. Examples, tool references, and links (such as time synchronization and .NET Framework requirements) are Windows-centric, with no Linux-specific guidance or examples for installation, prerequisites, or troubleshooting.
Recommendations
  • Add explicit instructions and examples for installing the configuration server on Linux physical servers, including supported distributions and required dependencies.
  • Provide Linux equivalents for system prerequisites (e.g., time synchronization, required packages, cryptography settings).
  • Include troubleshooting steps and common issues relevant to Linux environments.
  • Clarify whether the 'Unified Setup' installer is supported on Linux, and if not, provide alternative Linux setup steps or state Windows-only support.
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-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation presents Windows connection preparation steps first, with detailed instructions referencing Windows Firewall, RDP, and other Windows-specific settings. Linux instructions are present but less detailed, and some troubleshooting links and examples are Windows-focused. The overall pattern is to describe Windows steps before Linux, and Windows tools (like Windows Firewall) are mentioned explicitly, while Linux equivalents are not.
Recommendations
  • Provide equally detailed Linux instructions for preparing on-premises machines before failover, including common firewall configurations (e.g., iptables, firewalld, ufw) and SSH setup.
  • Include troubleshooting links or tips for Linux VMs post-failover, similar to the Windows RDP troubleshooting section.
  • Alternate the order of Windows and Linux sections, or present them in parallel tables to avoid Windows-first bias.
  • Reference Linux-specific tools and commands where appropriate, such as checking SSH service status, configuring SELinux/AppArmor, or reviewing Linux boot diagnostics.
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-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation provides troubleshooting steps for both Windows and Linux failover scenarios, but several sections show Windows bias. The hydration troubleshooting is exclusively for Windows Guest OS, with only PowerShell scripts and registry edits described. Windows tools like PsExec and Internet Explorer are referenced for proxy troubleshooting, even in a Linux context. Windows-specific instructions and terminology often appear before Linux equivalents, and Linux troubleshooting is sometimes less detailed or deferred to external links.
Recommendations
  • For hydration troubleshooting, add equivalent steps or scripts for Linux VMs, or clarify if hydration is not required for Linux.
  • In proxy troubleshooting, provide Linux-native methods for checking and modifying proxy settings, rather than relying on Windows tools like PsExec and Internet Explorer.
  • Ensure Linux troubleshooting steps are as detailed as Windows steps, especially for common failover errors.
  • Present Windows and Linux instructions in parallel where possible, rather than Windows-first.
  • Where external links are provided for SSH (Linux) and RDP (Windows) troubleshooting, ensure parity in detail and accessibility.
GitHub Create Pull Request
Site Recovery Deprecation of IPConfig parameters for the cmdlet New-AzRecoveryServicesAsrVMNicConfig | Microsoft Docs ...ttps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/site-recovery-ipconfig-cmdlet-parameter-deprecation.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation exclusively provides PowerShell examples and references PowerShell cmdlets, which are traditionally associated with Windows environments. There are no Bash, Azure CLI, or Linux/macOS shell examples, nor is there mention of equivalent workflows for non-Windows platforms. This may create friction for users who manage Azure resources from Linux or macOS systems.
Recommendations
  • Add equivalent Azure CLI examples for the described operations, if supported.
  • Clarify whether the cmdlets can be used cross-platform via PowerShell Core, and provide guidance for Linux/macOS users.
  • Explicitly state platform requirements and alternatives for non-Windows users.
  • If the functionality is only available via PowerShell, mention how to install and use PowerShell Core on Linux/macOS.
GitHub Create Pull Request
Site Recovery Remove servers and disable protection ...ry/site-recovery-manage-registration-and-protection.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation is heavily focused on Windows environments, specifically System Center VMM and Hyper-V, with all automation and cleanup examples provided exclusively in PowerShell. There are no Linux or macOS equivalents, nor any mention of Linux-based tooling or procedures for unregistering servers or disabling protection. VMware and physical server sections are generic and do not provide OS-specific guidance, but all scripting and automation is Windows-centric.
Recommendations
  • Clearly state at the beginning that the procedures and scripts are intended for Windows environments (Hyper-V, System Center VMM), and that Linux-based servers are not covered.
  • If Azure Site Recovery supports Linux-based servers or VMs, add equivalent instructions and scripts for unregistering and disabling protection for those platforms.
  • Provide guidance or links for Linux users on how to manually clean up replication settings, uninstall mobility service, or unregister servers if applicable.
  • Where PowerShell scripts are provided, note their Windows-only applicability and offer Bash or shell script alternatives if Linux is supported.
  • Add a section clarifying which steps are not relevant for Linux/macOS users, or link to Linux-specific documentation if available.
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-14 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits several Windows biases: examples for controlling bandwidth and registry modifications are exclusively Windows-centric (MMC snap-in, Windows registry, PowerShell cmdlets), and Windows tools are referenced without Linux equivalents or alternatives. Linux-specific guidance is only briefly mentioned in the context of master target server deployment, with no parity for process server management or bandwidth control. Windows instructions and tools are presented first and in detail, while Linux options are sparse or absent.
Recommendations
  • Provide Linux-specific examples for bandwidth throttling and process server management, including CLI commands or configuration file edits where applicable.
  • Clarify whether process server and configuration server components can run on Linux, and if so, document setup and management steps for Linux environments.
  • If registry-based configuration is required only on Windows, explicitly state this and offer Linux alternatives or note limitations.
  • Include Linux screenshots and walkthroughs for relevant management tasks, such as deploying and configuring master target servers.
  • Ensure parity in troubleshooting and scaling guidance for Linux-based deployments.
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-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias. The reference architecture and clustering recommendations are exclusively Windows-centric, focusing on Windows Server Failover Cluster, SIOS DataKeeper, and features like Scale Out File Server and Storage Spaces Direct. There is no mention of Linux-based SAP NetWeaver deployments, nor guidance for Linux clustering solutions (e.g., Pacemaker, NFS). All examples and recommendations assume Windows environments, leaving Linux users without clear instructions for disaster recovery setup.
Recommendations
  • Add explicit guidance and examples for SAP NetWeaver deployments on Linux VMs, including supported clustering and high availability patterns.
  • Document Linux equivalents for clustering (e.g., Pacemaker, Corosync, NFS for /sapmnt), and how to configure Site Recovery for these scenarios.
  • Clarify whether Site Recovery supports crash-consistent replication for Linux-based clusters and provide any required workarounds.
  • Include sample scripts and automation steps for Linux failover operations, not just Windows/PowerShell-based scripts.
  • Where recommendations are Windows-specific, note Linux alternatives or limitations.
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-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation exclusively provides PowerShell-based examples and instructions for Azure Automation runbooks in Site Recovery recovery plans. All code samples, module references, and variable manipulation are shown using PowerShell syntax and AzureRM/Az PowerShell modules, with no mention of Bash, Python, or cross-platform alternatives. There is no guidance for Linux/macOS users who may prefer or require non-PowerShell approaches, nor any reference to using Azure CLI or other scripting languages.
Recommendations
  • Add equivalent examples using Azure CLI and/or Python SDK for runbook integration and variable management.
  • Clarify whether PowerShell is a requirement for Azure Site Recovery runbook automation, or if cross-platform scripting is supported.
  • Provide guidance or links for Linux/macOS users on setting up and using Azure Automation runbooks with non-PowerShell scripts.
  • Explicitly state any platform limitations (e.g., if only PowerShell runbooks are supported for recovery plan integration).
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-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation is primarily focused on SQL Server disaster recovery scenarios that are Windows-centric, with examples and references to Windows-specific technologies (e.g., Failover Clustering, Always On Availability Groups, PowerShell scripts, Windows Task Manager). Linux-specific guidance, examples, or parity are missing, even though SQL Server is supported on Linux and Azure Site Recovery can protect Linux VMs. Windows tools and procedures (such as Task Manager and PowerShell) are mentioned exclusively or first, and there are no Linux equivalents provided.
Recommendations
  • Add explicit guidance and examples for SQL Server running on Linux, including supported disaster recovery scenarios and any differences in Site Recovery setup.
  • Where Windows tools (e.g., Task Manager for disk write rate) are referenced, provide Linux equivalents (e.g., iostat, atop, or other monitoring tools).
  • If PowerShell scripts are required for automation, provide Bash or shell script alternatives for Linux environments.
  • Clarify which steps or features are Windows-only and which are cross-platform, to help Linux users understand applicability.
  • Include links to Linux-specific SQL Server documentation and Azure Site Recovery support for Linux VMs.
GitHub Create Pull Request
Site Recovery About disaster recovery for on-premises apps with Azure Site Recovery .../main/articles/site-recovery/site-recovery-workload.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page predominantly references Windows workloads, tools, and patterns (e.g., Active Directory, IIS, Exchange, SharePoint, Dynamics AX, RDS) and provides detailed sections for these. While Linux is mentioned as supported and tested, there are no Linux-specific application examples, scenarios, or guidance. Windows technologies are described first and in greater detail, and Windows-centric tools and patterns (e.g., AD, IIS, Exchange DAGs) are emphasized. There is a lack of parity for Linux workloads beyond a brief mention in the workload summary table.
Recommendations
  • Add dedicated sections or examples for common Linux workloads and applications (e.g., Apache, NGINX, MySQL/PostgreSQL, Samba, LDAP).
  • Provide Linux-specific disaster recovery scenarios and guidance, similar to the detailed sections for Windows workloads.
  • Include Linux command-line examples and scripts for automation and recovery plan integration.
  • Clarify any differences in replication, failover, and recovery processes for Linux workloads compared to Windows.
  • Highlight third-party or open-source tools commonly used in Linux environments for disaster recovery.
GitHub Create Pull Request
Site Recovery Transport Layer Security in Azure Site Recovery ...ain/articles/site-recovery/transport-layer-security.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation is heavily focused on Windows environments, referencing Windows registry changes, KB articles, and .NET Framework configuration. There are no examples or guidance for Linux or macOS users, nor any mention of how TLS is managed in non-Windows environments for Azure Site Recovery. All instructions and troubleshooting steps are Windows-centric.
Recommendations
  • Clarify whether Azure Site Recovery supports Linux-based source or target machines and, if so, provide equivalent TLS configuration steps or references for Linux.
  • Add a section explaining TLS handling for Linux VMs, including how to verify or enforce TLS 1.2 usage (e.g., OpenSSL configuration, system-wide crypto policies).
  • If Azure Site Recovery is Windows-only, explicitly state this in the introduction to avoid confusion for non-Windows users.
GitHub Create Pull Request
Site Recovery Common questions about VMware disaster recovery with Azure Site Recovery ...rticles/site-recovery/vmware-azure-common-questions.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation provides both Windows and Linux examples in some areas (e.g., agent unregistration commands), but there is a tendency to mention Windows paths, tools, and PowerShell before Linux equivalents. PowerShell is referenced as a primary automation method, and some installation instructions (e.g., MySQL placement) use Windows file paths exclusively. Manual installation of the Mobility service mentions PowerShell and UI, but does not mention Linux CLI methods. The location of installers is given as a Windows path only. Overall, Linux parity is present but often secondary.
Recommendations
  • Provide Linux file paths alongside Windows paths when referencing installer locations or configuration steps.
  • Include Linux CLI examples for manual installation of the Mobility service, not just PowerShell/UI.
  • When referencing automation, mention Bash/CLI or scripting options for Linux users alongside PowerShell.
  • List Windows and Linux commands/examples together, or alternate which is shown first.
  • Clarify when instructions are OS-agnostic and when they are OS-specific.
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-14 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation provides both Windows and Linux instructions for updating the Mobility agent, but Windows examples and tools (e.g., Registry Editor, .msi installers, command prompt) are consistently presented first and in greater detail. Appliance component upgrade instructions are Windows-centric, with no Linux equivalents or guidance for non-Windows appliances. Some manual update steps and troubleshooting are described only for Windows environments, creating friction for Linux users.
Recommendations
  • Present Linux and Windows instructions in parallel or clearly separated sections, with equal detail and prominence.
  • Add explicit guidance for appliance component upgrades on Linux, if supported, or clarify if appliance components are Windows-only.
  • Where Windows tools (e.g., Registry Editor, .msi installers) are mentioned, provide Linux alternatives or note platform limitations.
  • Ensure troubleshooting and error resolution steps are applicable to both platforms, or specify platform-specific procedures.
  • Consider starting sections with a platform-neutral overview before diving into OS-specific instructions.
GitHub Create Pull Request
Site Recovery Enable VMware VMs (Modernized) for disaster recovery using Azure Site Recovery ...icles/site-recovery/vmware-azure-enable-replication.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides PowerShell examples and references for automating replication and managing Azure Site Recovery, with no equivalent CLI or Linux-native examples. PowerShell is mentioned as the primary automation tool, and REST API is referenced only in passing. There are no explicit Linux/macOS CLI instructions or parity for automation tasks, which may create friction for non-Windows users.
Recommendations
  • Add Azure CLI examples for enabling replication and managing Site Recovery, alongside PowerShell instructions.
  • Explicitly mention REST API usage with example requests for automation, especially for Linux/macOS users.
  • Clarify that PowerShell is available cross-platform, but provide installation guidance for Linux/macOS users.
  • Where possible, provide bash or shell script equivalents for common tasks.
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-14 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
🔧 Windows Tools
Summary
The documentation is focused on installing a Linux master target server for Azure Site Recovery failback, and provides thorough Linux-specific instructions. However, there are a few steps where Windows paths and tools are referenced, specifically when copying installer files and passphrases from the process server or configuration server, which are assumed to be running on Windows. These steps require Linux users to interact with Windows file systems or tools, potentially creating friction for those in Linux-only environments.
Recommendations
  • Provide alternative instructions for accessing installer files and passphrases if the process server or configuration server is running on Linux, or clarify that these components are Windows-only.
  • Explicitly state any platform requirements for the process server and configuration server up front, so Linux users understand the context.
  • If possible, offer guidance on using network shares, SCP, or other cross-platform file transfer methods for Linux users to obtain required files from Windows servers.
GitHub Create Pull Request
Site Recovery Manage a process server for VMware VMs/physical server disaster recovery in Azure Site Recovery ...es/site-recovery/vmware-azure-manage-process-server.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page consistently assumes the process server is running on Windows. All command-line examples use Windows-specific tools (cmd.exe, PowerShell), Windows paths (%PROGRAMDATA%), and Windows conventions. There are no Linux/macOS equivalents or guidance for managing process servers on non-Windows platforms, nor is it clarified that process servers must run on Windows. This creates friction for users who may expect Linux support or need to understand platform requirements.
Recommendations
  • Explicitly state in the introduction whether the process server is Windows-only, and clarify platform requirements.
  • If Linux is supported, provide equivalent Linux/macOS commands, paths, and procedures for all management tasks.
  • If process server is Windows-only, add a clear note to prevent confusion for Linux/macOS users.
  • Where PowerShell or Windows paths are referenced, offer alternative instructions or clarify platform limitations.
GitHub Create Pull Request
Site Recovery Prepare source machines to install the Mobility Service through push installation for disaster recovery of VMware VMs and physical servers to Azure ...site-recovery/vmware-azure-install-mobility-service.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation presents Windows instructions and tooling first, with detailed steps including registry edits, firewall configuration, and explicit use of Windows tools (e.g., cspsconfigtool.exe, Group Policy). Linux instructions are present but less detailed in some areas (e.g., anti-virus exclusions are only described for Windows), and Windows-specific ports and tools are referenced without Linux equivalents or clarifications. The use of 'cspsconfigtool.exe' for Linux is mentioned, but the tool's Windows-centric naming and pathing may cause confusion. Some steps (like anti-virus exclusions) are missing Linux-specific guidance.
Recommendations
  • Alternate the order of Windows and Linux sections, or provide a combined table for parity.
  • Provide Linux-specific anti-virus exclusion guidance (e.g., typical Linux agent paths, common AV tools).
  • Clarify that cspsconfigtool.exe is used for both Windows and Linux, and note any differences in usage or pathing on Linux hosts.
  • When referencing ports (e.g., SMB, WMI), clarify which are required for Windows, Linux, or both.
  • Include Linux equivalents for firewall configuration (e.g., iptables, firewalld, ufw) and provide example commands.
  • Add Linux-specific troubleshooting tips or common issues, similar to the Windows registry and firewall steps.
GitHub Create Pull Request
Site Recovery Manage VMware vCenter servers in Azure Site Recovery .../articles/site-recovery/vmware-azure-manage-vcenter.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation assumes the use of the configuration server tool (_cspsconfigtool.exe_) via a Desktop shortcut, which is a Windows executable and workflow. There are no instructions or examples for Linux-based configuration servers or command-line alternatives, nor is there any mention of Linux support or parity for these management actions.
Recommendations
  • Clarify whether the configuration server tool (_cspsconfigtool.exe_) is Windows-only, and if so, explicitly state this requirement early in the documentation.
  • If Linux-based configuration servers are supported, provide equivalent instructions for Linux users, including command-line alternatives or Linux-native tools.
  • Add a note about platform requirements for the configuration server, so users know whether they need a Windows environment.
  • If only Windows is supported for the configuration server, consider adding a brief explanation so Linux/macOS users understand the limitation.
GitHub Create Pull Request
Site Recovery Set up source settings for VMware disaster recovery to Azure with Azure Site Recovery ...n/articles/site-recovery/vmware-azure-set-up-source.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation page provides detailed instructions and examples for Windows environments, such as folder paths (C:\ProgramData\...), registry exclusions, and references to Windows-specific tools. Linux instructions are present but appear later and are less detailed. Windows examples and patterns are consistently shown first, and Windows-centric terminology dominates the antivirus exclusion sections.
Recommendations
  • Present Linux and Windows instructions in parallel, with equal detail and prominence.
  • Add Linux-specific examples and clarify Linux folder paths and configuration steps where applicable.
  • Where registry exclusions are mentioned, clearly state that these apply only to Windows, and provide Linux equivalents if relevant.
  • Consider grouping antivirus exclusions by OS, or using tabs/sections for Windows and Linux to improve clarity and parity.
GitHub Create Pull Request
Site Recovery Troubleshoot issues with the configuration server during disaster recovery of VMware VMs and physical servers to Azure by using Azure Site Recovery ...very/vmware-azure-troubleshoot-configuration-server.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation provides troubleshooting guidance for Azure Site Recovery configuration server, covering both Windows and Linux source machines. However, there is a notable Windows bias: Windows examples, paths, and tools are often presented first or exclusively (e.g., use of PsExec, Internet Explorer, Windows service names, and Windows file paths). Some troubleshooting steps reference Windows-only utilities and UI patterns (like File Explorer instructions), and certain sections lack equivalent Linux guidance (e.g., proxy configuration, service management, log file locations). Linux examples are present but less detailed and sometimes appear after Windows instructions.
Recommendations
  • Provide Linux equivalents for all troubleshooting steps, especially where Windows tools (PsExec, Internet Explorer, service management) are referenced.
  • Include Linux file paths and log locations alongside Windows paths in all relevant sections.
  • Offer Linux-specific commands for service management (e.g., systemctl, service) and proxy configuration.
  • Present Windows and Linux instructions in parallel, or clearly separate them by platform, to improve parity and reduce friction.
  • Avoid referencing Windows UI elements (like File Explorer) without Linux alternatives (e.g., using ls -a for hidden folders).
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-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation provides troubleshooting steps for both Windows and Linux VMs, but Windows VM behaviors and solutions are often described first or in more detail. Some Linux-specific issues are mentioned, but solutions are less detailed or require manual intervention, while Windows solutions are described as automatic. There are no Linux/macOS command-line examples or references to Linux tools for troubleshooting connectivity or services.
Recommendations
  • Provide Linux-specific troubleshooting steps and examples, such as commands to check and restart services (e.g., systemctl for NetworkManager or InMage Scout).
  • Include Linux command-line examples for connectivity checks (e.g., using ping, telnet, or netcat) alongside Windows equivalents.
  • Clarify differences in failback behavior between Windows and Linux VMs, and offer parity in solution detail.
  • Where manual intervention is required for Linux (e.g., resetting static IP), provide step-by-step instructions or scripts.
GitHub Create Pull Request
← Previous Page 25 of 35 Next →