Site Recovery

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

Bias Trend Over Time

Pages with Bias Issues

232 issues found
Showing 101-125 of 232 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-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. Windows instructions and examples (e.g., diskpart, PowerShell commands, screenshots) are presented first and in greater detail, with explicit command-line steps and visual aids. Linux instructions are present and reasonably detailed, but lack equivalent step-by-step command-line examples for some tasks (e.g., DHCP configuration, agent verification), and do not provide screenshots or as many illustrative examples. Windows-specific tools (diskpart, PowerShell) are referenced without Linux equivalents, and Windows troubleshooting links are prioritized in the troubleshooting section.
Recommendations
  • Provide Linux command-line examples for all manual steps, including DHCP configuration, agent verification, and disk mounting.
  • Include screenshots or terminal output for Linux steps, similar to those provided for Windows.
  • Reference Linux-native tools (e.g., nmcli, systemctl, lsblk) where appropriate, and provide guidance for common distributions beyond RedHat.
  • Balance troubleshooting links to include Linux-specific error resolution and VM SKU allocation failures.
  • Present Windows and Linux instructions in parallel or side-by-side tabs, rather than listing Windows first.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation is focused on disaster recovery for Hyper-V VMs, which are inherently Windows-based. Throughout the page, examples, terminology, and references are centered on Windows environments, with only passing mention of Linux VMs. There are no Linux-specific examples, tools, or guidance, and Windows is consistently referenced first or exclusively in key sections.
Recommendations
  • Add explicit examples and guidance for Linux VMs, including cost estimation scenarios and any differences in licensing (e.g., Azure Hybrid Use Benefit applicability).
  • Clarify whether the Deployment Planner tool supports Linux VMs for DR to Azure, and provide instructions or caveats for Linux users.
  • Include Linux-specific considerations in tables and workflows, such as OS type selection, licensing, and DR drill procedures.
  • Ensure parity in terminology and ordering (e.g., mention Linux before or alongside Windows 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-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First Missing Linux Example
Summary
The documentation demonstrates a notable Windows bias, especially in the section on configuring the Microsoft monitoring agent for churn and upload rate logs. Instructions and screenshots focus exclusively on Windows Server and the Windows agent, with no mention of Linux or macOS equivalents. The process for adding performance counters is described only for Windows, and the 'Connected Sources' workflow is Windows-centric. There are no examples or guidance for Linux-based Process Servers, nor is there discussion of Linux agent installation or configuration. This creates friction for users running Linux or non-Windows environments.
Recommendations
  • Add explicit instructions and examples for installing and configuring the monitoring agent on Linux-based Process Servers, including links to the Linux agent documentation.
  • Provide screenshots and workflow steps for Linux environments, such as using the 'Linux Servers' tab in Log Analytics workspace.
  • Describe how to add and query relevant performance counters on Linux, or clarify any limitations.
  • Ensure that all agent download and configuration steps are presented for both Windows and Linux, ideally side-by-side.
  • Mention any differences in supported features or limitations for Linux/macOS users.
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-12 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 monitoring tools (Resource Monitor, Performance Monitor) in detail, with step-by-step instructions and screenshots, while Linux tools (iotop, iostat) are only briefly mentioned without usage examples, screenshots, or further guidance. Windows tools are described first and more thoroughly, creating a notable disparity in guidance quality.
Recommendations
  • Provide step-by-step instructions for Linux tools (iotop, iostat), including example commands and output interpretation.
  • Include screenshots or sample outputs for Linux tools, similar to the Windows sections.
  • Mention additional Linux monitoring tools (e.g., atop, dstat, sar) for broader coverage.
  • Present Windows and Linux sections with equal detail and in parallel structure, possibly interleaving them or using side-by-side comparisons.
  • Ensure that introductory and summary sections explicitly address Linux as well as Windows users.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing Windows-specific requirements (such as .NET Framework and TLS settings), linking to Windows time service documentation, and omitting Linux-specific installation steps or troubleshooting. All examples and instructions assume a Windows environment, with no mention of Linux equivalents or guidance for Linux users.
Recommendations
  • Add explicit instructions and prerequisites for Linux-based configuration servers, including supported distributions and required packages.
  • Provide Linux-specific installation steps, including command-line examples for running the Unified Setup on Linux.
  • Reference Linux time synchronization tools (e.g., ntpd, chrony) alongside Windows time service.
  • Clarify whether .NET Framework requirements apply to Linux, or specify alternative dependencies for Linux systems.
  • Include troubleshooting steps and common issues relevant to Linux installations.
GitHub Create Pull Request
Site Recovery Physical server to Azure disaster recovery architecture – Modernized ...overy/physical-server-azure-architecture-modernized.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation claims to cover both Windows and Linux physical servers, but throughout the page, examples, technical details, and process descriptions are either generic or implicitly Windows-focused. The only explicit mention of OS-specific technology is the use of VSS (Volume Shadow Copy Service) for app-consistent snapshots, which is a Windows-only feature. There are no Linux-specific instructions, examples, or references to equivalent Linux snapshot or consistency mechanisms. This creates ambiguity for Linux users regarding how app-consistent snapshots are handled and whether parity exists.
Recommendations
  • Add explicit Linux examples and instructions throughout the documentation, especially for app-consistent snapshots and recovery points.
  • Clarify how app-consistent snapshots are performed on Linux servers (e.g., mention if pre/post scripts, fsfreeze, or other mechanisms are used).
  • Include references to Linux-specific tools, commands, or requirements where relevant.
  • Provide a comparison table or section outlining differences and similarities in the disaster recovery process for Windows vs. Linux servers.
  • Ensure that any OS-specific limitations (such as VSS only for Windows) are clearly stated, and Linux alternatives are described.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation claims to support both Windows and Linux physical servers, but provides detailed instructions and command-line examples only for Windows (e.g., registry modification via REG ADD). Windows-specific tools and patterns (registry editing, domain/local accounts, disabling Remote User Access control) are described in detail, while Linux instructions are minimal, only mentioning the need for a root account without further guidance or examples. No Linux-specific commands, troubleshooting, or configuration steps are provided.
Recommendations
  • Provide equivalent Linux command-line examples (e.g., how to prepare the root account, required permissions, or configuration steps for the Mobility service installation).
  • Include Linux-specific troubleshooting steps, such as SELinux/AppArmor considerations, firewall configuration, or time synchronization using chrony/ntpd.
  • Balance the depth of Windows and Linux instructions, ensuring both platforms have clear, actionable steps.
  • Explicitly mention any Linux-specific requirements or caveats, such as supported distributions, package dependencies, or log file locations.
  • Add screenshots or CLI output examples for Linux where relevant.
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-12 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 operating systems, but provides more explicit instructions for Windows (e.g., specifying admin privileges) and generally lists Windows before Linux. There are no concrete examples or screenshots showing Linux-specific steps, commands, or credential formats. The process for Linux (e.g., root credentials, manual mobility service installation) is referenced but not illustrated, while Windows instructions are more direct. No Linux command-line or tool examples are given.
Recommendations
  • Provide step-by-step screenshots and examples for Linux systems, including credential formats and manual mobility service installation.
  • Include Linux-specific troubleshooting tips and common issues.
  • Present Linux and Windows instructions in parallel, rather than listing Windows first.
  • Add CLI or shell command examples for Linux where applicable.
  • Clarify any differences in process or requirements between Linux and Windows servers.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation provides detailed instructions for preparing Windows virtual machines, including registry edits and CLI commands, but offers minimal guidance for Linux systems. The Windows-specific steps (e.g., registry changes, REG ADD command) are described first and in detail, while Linux instructions are limited to a brief mention that the account should be root, with no equivalent example or troubleshooting advice.
Recommendations
  • Provide equivalent, step-by-step instructions for Linux VMs, including any necessary configuration changes or commands.
  • Include Linux CLI examples for installing the Mobility service and troubleshooting common issues.
  • Present Windows and Linux instructions in parallel, or clearly separate them to avoid Windows-first bias.
  • Add links to Linux-specific documentation or troubleshooting guides where relevant.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits several forms of Windows bias. Troubleshooting steps for hydration failures provide only Windows PowerShell scripts and registry instructions, with no equivalent Linux guidance. Windows-specific tools (PsExec, Internet Explorer) are referenced for proxy troubleshooting, while Linux alternatives are not described. Windows guest OS instructions are detailed and prioritized, whereas Linux troubleshooting is limited to a single UEFI/serial console scenario and lacks parity in example depth. In most sections, Windows solutions are presented first or exclusively, and Linux users may need to infer or research their own solutions.
Recommendations
  • Provide equivalent Linux troubleshooting steps for hydration failures, including commands to check and set required driver/service states.
  • Include Linux-specific examples and scripts where PowerShell is used for Windows.
  • When referencing Windows tools (e.g., PsExec, Internet Explorer), offer Linux alternatives (e.g., sudo, curl, environment variable configuration) and step-by-step instructions.
  • Ensure that Linux troubleshooting is as detailed and visible as Windows, with examples for common failover errors.
  • Present Windows and Linux instructions side-by-side or in clearly separated tabs to improve parity.
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-12 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 is heavily focused on Azure PowerShell cmdlets, with all examples and remediation steps provided exclusively in PowerShell syntax. There is no mention of Linux/macOS alternatives, cross-platform scripting, or Azure CLI equivalents. This creates friction for users on Linux or macOS who may not use PowerShell as their primary automation tool.
Recommendations
  • Provide equivalent examples using Azure CLI, which is natively supported on Linux/macOS.
  • Clarify whether the cmdlets can be used in PowerShell Core on Linux/macOS, and provide installation guidance if so.
  • Add notes or links for Bash scripting or other cross-platform automation approaches.
  • Explicitly mention platform compatibility for the cmdlets discussed.
GitHub Create Pull Request
Site Recovery Troubleshoot the Azure VM extension for disaster recovery with Azure Site Recovery .../site-recovery/site-recovery-extension-troubleshoot.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation consistently presents Windows troubleshooting steps before Linux ones, and uses Windows-specific tools (services.msc, Control Panel, MSI installer) in detail. Linux instructions are present and reasonably complete, but are listed after Windows and lack parity in step-by-step detail. Windows tools and patterns (services.msc, .NET dependency) are described exclusively for Windows, with no Linux equivalents mentioned.
Recommendations
  • Alternate the order of Windows and Linux troubleshooting sections, or present them in parallel for each error.
  • Provide equally detailed, step-by-step instructions for Linux agent troubleshooting (e.g., commands to check agent status, uninstall/reinstall agent, verify dependencies).
  • Explicitly mention Linux equivalents for steps like checking service status (e.g., systemctl status waagent), uninstalling/reinstalling the agent, and required dependencies.
  • Add notes clarifying which steps are OS-specific and provide links to both Windows and Linux agent update guides.
  • Consider a summary table comparing steps for Windows and Linux for each common error.
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-12 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 moderate Windows bias. Windows VM instructions are consistently presented before Linux VM instructions in connection preparation and troubleshooting tables. Windows-specific tools and settings (e.g., Windows Firewall, RDP, WinHTTP proxy, SAN policy) are described in detail, while Linux instructions are minimal and lack equivalent depth (e.g., only mentioning SSH and firewall rules). There are references to Windows update and other Windows-specific behaviors, but no similar coverage for Linux update or service management. Troubleshooting links and examples are Windows-centric, and Linux users may need to infer or research additional steps.
Recommendations
  • Present Linux and Windows instructions in parallel, giving equal detail and prominence.
  • Expand Linux VM preparation steps to include common issues (e.g., SELinux, iptables, cloud-init, SSH key management, OS update behaviors).
  • Provide Linux-specific troubleshooting links and examples, similar to those offered for Windows.
  • Mention Linux equivalents for Windows tools/settings (e.g., firewall-cmd/iptables for firewall, systemctl for service management, update/upgrade procedures).
  • Avoid listing Windows instructions first by default; alternate or group by OS type.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page exhibits a notable Windows bias. Key configuration and bandwidth control steps rely on Windows-specific tools (MMC snap-in, registry edits, PowerShell cmdlets), with no Linux equivalents or alternatives provided. Windows instructions and tools are presented first and in detail, while Linux is only mentioned in the context of deploying a master target server, with no operational or configuration examples. This creates friction for Linux users, especially for tasks like bandwidth throttling and process server management.
Recommendations
  • Provide equivalent instructions and tooling for Linux-based process servers, such as how to throttle bandwidth or adjust replication settings using Linux utilities or configuration files.
  • Include Linux command-line examples (e.g., shell scripts, systemd service management) alongside PowerShell examples.
  • Clarify which steps are Windows-only and offer alternative approaches for Linux environments, or explicitly state platform limitations.
  • Document how to manage registry-like settings or configuration for replication on Linux-based servers.
  • Ensure screenshots and UI instructions are platform-agnostic or provide Linux-specific visuals where applicable.
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-12 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 is exclusively described as running SAP NetWeaver in a Windows environment, with no mention of Linux-based deployments. Critical disaster recovery patterns, such as clustering, are explained only using Windows Server Failover Cluster, SIOS DataKeeper, and Windows-specific features like Storage Spaces Direct and Scale Out File Server. There are no examples or guidance for equivalent Linux clustering solutions (e.g., Pacemaker, Corosync, NFS, GlusterFS), nor is there mention of Linux-based SAP deployments, which are common in enterprise environments.
Recommendations
  • Add explicit guidance and examples for SAP NetWeaver deployments on Linux, including supported disaster recovery patterns.
  • Describe how to implement clustering and high availability for SAP Central Services on Linux (e.g., using Pacemaker, Corosync, NFS, or GlusterFS).
  • Include Linux-specific instructions for configuring failover, recovery plans, and automation scripts.
  • Clarify which features and recommendations apply to both Windows and Linux, and note any limitations or differences.
  • Provide parity in diagrams and reference architectures by showing both Windows and Linux scenarios.
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-12 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 exhibits a Windows bias by referencing Windows-specific tools (Task Manager, PowerShell), linking to Windows-centric SQL Server features (Always On, Failover Clustering), and providing automation scripts only in PowerShell. There are no explicit Linux examples, nor are Linux-specific monitoring or failover instructions provided. Windows terminology and links appear first or exclusively throughout the document.
Recommendations
  • Include equivalent instructions and examples for SQL Server running on Linux, such as monitoring disk write rates using Linux tools (e.g., iostat, sar, atop).
  • Provide automation scripts in Bash or Python for Linux environments, or reference cross-platform alternatives.
  • Link to SQL Server on Linux documentation for features like Always On availability groups and failover clustering.
  • Clarify which steps are applicable to Linux deployments and note any differences or limitations.
  • Add screenshots and walkthroughs using Linux-based VMs where appropriate.
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-12 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 is heavily focused on PowerShell and Windows-centric tooling. All code examples, automation instructions, and variable management are provided exclusively in PowerShell, with no mention of Bash, Python, or cross-platform alternatives. There is no guidance for Linux/macOS users on how to interact with Azure Automation runbooks or manage recovery plan context using non-Windows tools. Windows/PowerShell patterns are presented first and exclusively, creating friction for users on other platforms.
Recommendations
  • Add equivalent examples using Azure CLI, Bash, or Python to demonstrate cross-platform automation.
  • Explicitly mention platform requirements and alternatives for Linux/macOS users.
  • Provide guidance on installing and using Azure Automation modules from Linux/macOS environments.
  • Include sample scripts and variable management using Azure CLI or REST API.
  • Reorder examples to present cross-platform options alongside or before PowerShell.
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-12 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. Windows workloads and Microsoft applications (Active Directory, Exchange, SharePoint, IIS, Dynamics AX, SQL Server, Remote Desktop Services) are described in detail, with dedicated sections and examples. Linux is mentioned only briefly and generically, without specific Linux application examples, tools, or recovery patterns. Windows tools and technologies (e.g., SQL Always On, Exchange DAGs, IIS, RDS) are referenced exclusively or before any Linux equivalents. There are no Linux-specific disaster recovery scenarios, nor are open-source Linux tools or patterns discussed.
Recommendations
  • Add dedicated sections for popular Linux workloads (e.g., Apache, NGINX, MySQL, PostgreSQL, Samba, LDAP) and describe how Site Recovery supports their disaster recovery.
  • Provide Linux-specific examples and recovery plans, including scripting patterns (e.g., Bash, systemd, cron) and integration with Linux-native HA/DR tools (e.g., Pacemaker, Corosync, DRBD).
  • Mention open-source alternatives and how Site Recovery interacts with them, ensuring parity with Windows features.
  • Ensure that Linux is referenced alongside Windows in all relevant sections, not just as a generic 'Linux (operating system and apps)' entry.
  • Include links to Linux-focused documentation and guides.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias. Windows-specific tools (Registry Editor, .msi installers, command prompt, Windows file paths) are mentioned and explained in detail, often before or exclusively compared to Linux equivalents. Appliance update procedures and troubleshooting steps are almost entirely Windows-centric, with Linux instructions only present for the mobility agent update and not for appliance components. Windows command-line examples and registry modifications are described, while Linux alternatives are missing or underrepresented.
Recommendations
  • Provide Linux-specific instructions for appliance component updates, including command-line examples and package management guidance (e.g., .rpm, .deb, systemctl).
  • Include Linux troubleshooting steps for appliance upgrades and component status checks.
  • Present Windows and Linux instructions in parallel sections, or clearly label and order them to avoid Windows-first bias.
  • Mention Linux equivalents for tools like Registry Editor (e.g., config files, systemd services) and clarify which steps are OS-specific.
  • Ensure all manual update and error resolution procedures are documented for both platforms.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits a moderate Windows bias. PowerShell is mentioned as the primary automation tool, with no reference to Linux-native equivalents (such as Bash or Azure CLI). Windows-specific features (e.g., Azure Hybrid Benefit for Windows Server, UEFI/Gen2 VM requirements for Windows OS) are highlighted, and Windows terminology is used first or exclusively in several places. There are no explicit Linux/macOS examples or guidance for users managing non-Windows VMs or environments.
Recommendations
  • Include automation examples using Azure CLI and Bash scripts alongside PowerShell, especially for enabling replication and managing VMs.
  • Clarify which steps or features are applicable to Linux VMs and provide Linux-specific guidance where necessary (e.g., disk requirements, OS support).
  • Mention Linux/macOS management tools or workflows where relevant, and avoid assuming Windows as the default environment.
  • Add notes or sections about replicating Linux VMs, including any OS-specific caveats or best practices.
  • Balance references to Windows features (like Azure Hybrid Benefit) with information about licensing or benefits for Linux workloads, if available.
GitHub Create Pull Request
Site Recovery Troubleshoot Mobility Service push installation with Azure Site Recovery ...ite-recovery/vmware-azure-troubleshoot-push-install.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias. Windows troubleshooting steps, tools, and examples are presented first and in greater detail, with explicit references to Windows-specific utilities (e.g., registry edits, net user, Netlogon, File Explorer, WMI, VSS, DCOM, Windows Services, and Group Policy). Linux instructions are present but less detailed, sometimes only mentioned as an afterthought or in a single bullet. Some troubleshooting sections (e.g., VSS, WMI, network shares) are exclusively Windows-focused, with no Linux equivalents or guidance. The use of Windows command-line tools and registry modifications is pervasive, while Linux commands and troubleshooting patterns are sparse.
Recommendations
  • Provide Linux troubleshooting steps and examples for each error, especially where only Windows instructions are given (e.g., network shares, VSS, WMI, driver issues).
  • Include Linux tools and commands (e.g., systemctl, journalctl, SSH/SFTP troubleshooting, Linux equivalents for service and firewall management) alongside Windows tools.
  • Present Windows and Linux instructions in parallel tabs or sections, ensuring equal detail and prominence.
  • Add Linux-specific error codes and log file locations where relevant.
  • Avoid referencing Windows tools (e.g., File Explorer, regedit, Group Policy) without offering Linux alternatives (e.g., CLI commands, config file edits).
  • Ensure that all critical troubleshooting steps are covered for both platforms.
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-12 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 exhibits moderate Windows bias. Windows tools and paths (e.g., C:\Program Files, C:\Temp) are mentioned first or exclusively in several sections, such as Mobility service installation and configuration server setup. PowerShell is frequently referenced as the primary automation/scripting method, with Linux equivalents (shell scripts, CLI) rarely mentioned or described in less detail. Some instructions (e.g., manual MySQL installation, agent unregistration) provide Windows examples first, and Linux examples are present but less emphasized. There is little mention of Linux-native tools or automation approaches, and some steps (e.g., downloading installers) assume Windows file paths.
Recommendations
  • Present Linux and Windows instructions side-by-side, giving equal prominence to both.
  • Include Linux-native automation examples (e.g., Bash scripts, Azure CLI) alongside PowerShell.
  • Reference Linux file paths and conventions wherever Windows paths are mentioned.
  • Clarify when a step is OS-specific and provide explicit guidance for both platforms.
  • Review all sections for assumptions of Windows environments and add Linux/macOS alternatives where relevant.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools 📁 Windows Paths Windows Reference
Summary
The documentation is focused on installing and configuring a Linux master target server for Azure Site Recovery failback, and the instructions are almost entirely Linux-centric. However, there are several instances where Windows tools, file paths, and references are used as the default or only example for tasks such as copying installers and retrieving passphrases. Specifically, users are instructed to obtain files from Windows directories (e.g., C:\Program Files (x86)\...) and configuration files (e.g., C:\ProgramData\...), with no Linux alternatives or parity for process server or configuration server roles. This creates friction for Linux-only environments or users who prefer Linux-based management servers.
Recommendations
  • Provide Linux-based examples for accessing the installer and passphrase files, especially for environments where the process server or configuration server is running on Linux.
  • Clarify whether the process server and configuration server must be Windows-based, or provide instructions for Linux equivalents if supported.
  • Add notes or alternative steps for users who do not have access to Windows servers, including how to retrieve necessary files and credentials from Linux systems.
  • Where Windows paths are referenced, include the corresponding Linux paths if the product supports Linux-based management components.
GitHub Create Pull Request
Site Recovery Prepare VMware VMs for reprotection and failback with Azure Site Recovery ...rticles/site-recovery/vmware-azure-prepare-failback.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation page demonstrates a moderate Windows bias. Windows master target servers are described as the default, and instructions for adding a retention drive are Windows-centric, with Linux details mentioned second or as an aside. Windows-specific tools and patterns (e.g., default retention volume 'R', Windows master target server running on the configuration server) are highlighted before Linux equivalents. The documentation refers to Windows master target servers as the default and provides more detailed steps for Windows than for Linux, with Linux instructions often parenthetical or secondary.
Recommendations
  • Present Linux and Windows instructions in parallel, giving equal prominence to both.
  • Explicitly document Linux-specific steps for adding retention drives, including formatting and mounting instructions.
  • Avoid referring to Windows master target servers as the default; clarify that both Windows and Linux are supported and provide guidance for choosing between them.
  • Provide example commands for both Windows (PowerShell/GUI) and Linux (shell/CLI) where relevant.
  • Ensure that all requirements and limitations are described for both platforms, not just Windows.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation page exhibits several forms of Windows bias. Windows-specific paths, tools, and troubleshooting steps are frequently mentioned first or exclusively (e.g., use of PsExec, Internet Explorer, Windows file paths, and service names). Some troubleshooting steps and examples are provided only for Windows, or Windows instructions are more detailed than Linux equivalents. Linux-specific guidance is present but less comprehensive and sometimes appears as an afterthought.
Recommendations
  • Provide Linux/macOS equivalents for all Windows-only tools and steps (e.g., alternatives to PsExec and Internet Explorer for proxy configuration).
  • Ensure Linux troubleshooting steps are as detailed and prominent as Windows steps.
  • List Linux and Windows examples side-by-side or in parallel sections, rather than Windows-first.
  • Include Linux file paths and service names wherever Windows paths/services are mentioned.
  • Where Windows-specific commands are given (e.g., stopping services, viewing logs), provide the corresponding Linux commands (e.g., systemctl, journalctl, grep, etc.).
  • Clarify which steps apply to both platforms and which are platform-specific.
GitHub Create Pull Request
← Previous Page 5 of 10 Next →