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 126-150 of 232 flagged pages
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-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 prioritizing Windows-specific instructions and tools, such as referencing Windows folders and registry keys extensively, and mentioning Windows licensing requirements for the configuration server. Linux-specific guidance is minimal and appears later in the document, with only a brief section on folder exclusions for Linux Master Target. There are no Linux-based setup or configuration examples, and the overall flow assumes a Windows-centric environment.
Recommendations
  • Provide Linux-specific setup instructions for the configuration server, including licensing and installation steps if supported.
  • Include Linux folder exclusion examples earlier and with equal prominence to Windows examples.
  • Clarify whether the configuration server can be run on Linux, and if not, explain the rationale and alternatives for Linux users.
  • Offer parity in troubleshooting and operational guidance for both Windows and Linux environments.
  • List Linux examples alongside Windows examples, not after them.
GitHub Create Pull Request
Site Recovery Support matrix for VMware/physical disaster recovery in Azure Site Recovery. .../site-recovery/vmware-physical-azure-support-matrix.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation page exhibits moderate Windows bias. Key deployment and management tasks (such as setting up the replication appliance for physical servers) are described as requiring Windows Server and PowerShell scripts, with no Linux alternatives or parity. Windows terminology, tools, and configuration details (e.g., IIS, Windows Server roles, group policies) are referenced exclusively or before Linux equivalents. Linux support is detailed in terms of supported distributions and kernel versions, but Linux-based deployment or management patterns are not described. The documentation assumes a Windows-centric on-premises infrastructure for critical components.
Recommendations
  • Provide Linux-based deployment options for the replication appliance, including supported distributions and setup instructions.
  • Offer equivalent Linux command-line examples (e.g., Bash scripts) for tasks currently described with PowerShell.
  • Document Linux alternatives for configuration server/process server roles, or clarify if Windows is strictly required.
  • Add explicit guidance for Linux-only environments, including any limitations and recommended workarounds.
  • Ensure that Linux and Windows instructions/examples are presented with equal prominence.
GitHub Create Pull Request
Site Recovery Scale VMware/physical disaster recovery with Azure Site Recovery ...cles/site-recovery/vmware-physical-large-deployment.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page exhibits moderate Windows bias, primarily through the use of Windows-specific terminology and tooling (e.g., PowerShell cmdlet for failover), and by providing compliance instructions only for Windows machines. Linux is mentioned, but only in passing and without actionable guidance or examples. No Linux-specific tools, commands, or step-by-step instructions are provided for critical operations such as failover, compliance checks, or automation.
Recommendations
  • Provide Linux-specific examples for key operations, such as triggering failover (e.g., using Azure CLI or REST API, with Linux shell commands).
  • Include instructions or scripts for proactively checking and ensuring Linux VM compliance with Azure requirements before failover, similar to the Windows guidance.
  • Mention Linux automation options (e.g., Bash scripts, Ansible playbooks) alongside Azure Automation runbooks.
  • Ensure that any referenced tools (e.g., Deployment Planner) are cross-platform, and clarify installation and usage steps for Linux environments.
  • Where PowerShell is referenced, offer equivalent Azure CLI or REST API commands, and show both Windows and Linux examples side-by-side.
GitHub Create Pull Request
Site Recovery Troubleshoot the Azure Site Recovery process server ...y/vmware-physical-azure-troubleshoot-process-server.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a notable Windows bias. Troubleshooting steps, file paths, service names, and tool usage (such as Telnet and Task Manager) are described exclusively with Windows conventions. All examples, logs, and screenshots reference Windows environments, with no mention of Linux or macOS equivalents. There are no instructions for performing these tasks on Linux-based process servers, nor are alternative tools or commands provided for non-Windows platforms.
Recommendations
  • Add Linux-specific troubleshooting steps, including equivalent log file locations, service management commands (e.g., systemctl), and process monitoring tools (e.g., top, htop, netstat).
  • Provide examples for checking connectivity using Linux tools such as nc (netcat) or curl, instead of only Telnet.
  • Include instructions for accessing and interpreting logs on Linux systems.
  • Mention how to manage firewall rules and proxy settings on Linux (e.g., using iptables, ufw, or editing configuration files).
  • Clarify whether Azure Site Recovery process server is supported on Linux, and if not, state this explicitly to avoid confusion.
GitHub Create Pull Request
Site Recovery Manage the Mobility agent for VMware/physical servers with Azure Site Recovery ...te-recovery/vmware-physical-manage-mobility-service.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 demonstrates a moderate Windows bias. Windows-specific tools (PowerShell, Control Panel, MSIExec, VSS provider) are described in detail, with examples and command lines. The PowerShell update method is shown only for Windows, with no Linux equivalent. In several sections, Windows instructions or tools are presented first or exclusively, while Linux instructions are less detailed or missing (e.g., no Linux command-line update example, no Linux VSS provider guidance).
Recommendations
  • Provide equivalent Linux command-line examples for updating the Mobility agent (e.g., using shell scripts or package managers).
  • Include Linux-first or side-by-side instructions where possible, rather than presenting Windows tools and examples first.
  • Add guidance for managing the Mobility agent on Linux using native tools (systemctl, bash scripts, etc.), not just manual installer execution.
  • If VSS provider is Windows-only, clarify this explicitly; if Linux has an equivalent, document its installation and management.
  • Ensure parity in troubleshooting, automation, and scripting examples for both platforms.
GitHub Create Pull Request
Site Recovery Troubleshoot VMware replication appliance health issues in Azure Site Recovery ...recovery/vmware-troubleshoot-appliance-health-issue.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 provides troubleshooting steps that rely exclusively on Windows tools and PowerShell scripts, with explicit instructions to use PowerShell and Windows file paths. No Linux or macOS equivalents or alternatives are mentioned, and all examples and tool references are Windows-centric. This creates friction for users running the replication appliance on Linux or macOS, or those who prefer cross-platform solutions.
Recommendations
  • Include equivalent troubleshooting steps for Linux-based appliances, such as shell script examples and Linux file paths.
  • Clarify whether the replication appliance is Windows-only, or provide guidance for non-Windows environments if supported.
  • Add notes or sections for macOS/Linux users, specifying any differences in procedure or tool usage.
  • Where PowerShell is used, offer Bash or shell script alternatives if possible.
GitHub Create Pull Request
Site Recovery Troubleshoot VMware mobility agent health errors in Azure Site Recovery ...-recovery/vmware-troubleshoot-mobility-agent-health.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 provides both Linux and Windows log file locations, but consistently lists Windows paths and service names first and exclusively uses Windows service names (e.g., 'Process Server', 'Microsoft Azure RCM Proxy Agent'). Troubleshooting steps reference restarting Windows-named services without mentioning equivalent Linux commands or service names, and examples of error logs include Windows-style paths and hostnames. There are no explicit Linux troubleshooting commands or service management instructions, which may create friction for Linux users.
Recommendations
  • Provide Linux service names and management commands (e.g., systemctl or service) alongside Windows instructions for restarting services.
  • List Linux and Windows log file paths together, alternating which is listed first.
  • Include Linux-specific troubleshooting steps and examples, such as how to check service status, restart services, and locate logs using Linux commands.
  • Reference Linux hostnames and file paths in error examples where applicable.
  • Clarify any differences in agent upgrade or re-registration processes between Windows and Linux.
GitHub Create Pull Request
Site Recovery Enable replication of encrypted Azure VMs in Azure Site Recovery ...https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/azure-to-azure-how-to-enable-replication-cmk-disks.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides a detailed PowerShell example for adding a CMK-enabled disk to a replicated VM, but does not offer equivalent CLI or Bash examples for Linux/macOS users. The FAQ section specifically instructs users to use PowerShell, and no mention is made of Azure CLI or other cross-platform tools. This creates friction for users on Linux or macOS who may not have access to PowerShell or prefer native tools.
Recommendations
  • Provide equivalent Azure CLI and/or Bash examples for all PowerShell code snippets, especially in critical workflows like disk replication.
  • Explicitly mention cross-platform alternatives (Azure CLI, REST API) wherever PowerShell is referenced.
  • Add a note clarifying tool availability and platform support for each example.
  • Consider reordering examples to present cross-platform options first, or side-by-side with PowerShell.
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-11 06:20
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 scenarios are centered on Windows VMs, with Linux VMs only mentioned as a possible OS type in cost tables. There are no Linux-specific examples, patterns, or guidance, and Windows concepts (such as Azure Hybrid Use Benefit) are described in detail before Linux is referenced. No Linux tooling or parity is discussed.
Recommendations
  • Add explicit examples and guidance for Linux VM disaster recovery scenarios, including any differences in cost estimation, licensing, or Azure Site Recovery features.
  • Clarify whether the Deployment Planner tool supports Linux VMs equally, and document any limitations or differences.
  • Include Linux-specific considerations (e.g., support for different distributions, licensing, backup/restore nuances) in relevant sections.
  • Provide sample cost estimation tables and walkthroughs for Linux VMs, not just Windows.
  • If there are Linux-specific Azure benefits or limitations, document them alongside Windows features like Azure Hybrid Use Benefit.
GitHub Create Pull Request
Site Recovery Set up failover of Hyper-V VMs to Azure in Azure Site Recovery ...e-recovery/hyper-v-azure-failover-failback-tutorial.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation is heavily focused on Hyper-V, a Windows-only virtualization platform, and references Windows-centric tools and patterns (e.g., Remote Desktop Protocol, Windows VM connection guides). There are no Linux or macOS equivalents or examples provided, and the connection instructions link to Windows VM documentation. This creates friction for users who may want to use Linux-based Hyper-V guests or connect from non-Windows platforms.
Recommendations
  • Include explicit instructions for connecting to Linux VMs after failover, such as using SSH from Linux/macOS clients.
  • Add links to Linux VM connection documentation alongside Windows guides.
  • Clarify whether Linux guest VMs are supported in the failover process and provide any necessary caveats or steps.
  • Mention cross-platform tools (e.g., OpenSSH, cross-platform RDP clients) for connecting to failed-over VMs.
  • If failover of Linux VMs is supported, provide examples or screenshots for Linux guest properties and failover validation.
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-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation is exclusively focused on Azure PowerShell cmdlets, with all examples and remediation steps provided in PowerShell syntax. There is no mention of Linux/macOS alternatives, such as Azure CLI or Bash scripting, nor any guidance for users who do not use PowerShell. This creates friction for Linux/macOS users who may prefer or require non-PowerShell tooling.
Recommendations
  • Add equivalent examples using Azure CLI commands for configuring IP settings and updating replication protected items.
  • Explicitly mention whether the cmdlets are supported on PowerShell Core (pwsh) on Linux/macOS, or if any limitations exist.
  • Provide Bash or shell script examples for common operations, or link to relevant cross-platform documentation.
  • Clarify if the remediation steps can be performed via the Azure Portal or REST API, and provide links or examples.
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-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by prioritizing Windows workloads, tools, and technologies throughout. Windows-centric applications (Active Directory, Exchange, SharePoint, IIS, Dynamics AX, RDS, SQL Server) are discussed in detail, with integration features and recovery plans described for each. Linux is mentioned only briefly and generically, without specific examples, guidance, or parity in coverage. Windows tools and patterns (e.g., IIS, RDS, Exchange DAGs, SQL Always On) are referenced exclusively, while Linux equivalents (such as Apache, Nginx, Samba, or Linux HA/DR solutions) are omitted.
Recommendations
  • Include concrete Linux workload examples (e.g., Apache, Nginx, MySQL, PostgreSQL, Samba, LDAP) and describe how Site Recovery supports them.
  • Provide detailed guidance and recovery plan templates for popular Linux applications and services, similar to the coverage for Windows workloads.
  • Mention Linux-specific HA/DR technologies (e.g., Pacemaker, Corosync, DRBD) and how they integrate with Site Recovery.
  • Ensure that Linux examples and tools are presented alongside Windows ones, not just as a generic catch-all.
  • Add links to Linux-focused disaster recovery documentation and walkthroughs.
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-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a Windows-first bias: Windows instructions are presented before Linux, Windows-specific tools (e.g., registry edits, firewall configuration, cspsconfigtool.exe) are described in detail, and examples (such as registry commands) are given only for Windows. Linux instructions lack equivalent command-line examples and troubleshooting details. Some configuration tool references (cspsconfigtool.exe) are Windows-centric, and anti-virus exclusions are only described for Windows paths.
Recommendations
  • Present Linux and Windows instructions in parallel or alternate order to avoid Windows-first bias.
  • Provide Linux command-line examples (e.g., for editing sshd_config, restarting sshd, checking openssh installation) similar to Windows registry commands.
  • Clarify whether cspsconfigtool.exe is available for Linux or provide Linux-native alternatives.
  • Include anti-virus exclusion guidance for common Linux anti-virus solutions and Linux agent paths.
  • List required ports for Linux as well as Windows, and clarify any Linux-specific firewall steps.
  • Add troubleshooting tips for Linux environments, matching the detail given for Windows.
GitHub Create Pull Request
Site Recovery Analyze the Deployment Planner report for VMware disaster recovery with Azure Site Recovery ...site-recovery-vmware-deployment-planner-analyze-report.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. While the tool and report are designed to analyze VMware environments (which can host both Windows and Linux VMs), the documentation repeatedly references Windows-specific features and support (e.g., EFI boot support only for Windows Server versions), and does not provide Linux-specific guidance or examples. There is no mention of Linux-specific limitations, troubleshooting, or parity in features such as EFI support. The documentation also lacks examples or instructions tailored to Linux VMs, and Windows Server is mentioned first and exclusively in critical compatibility sections.
Recommendations
  • Add explicit guidance and examples for Linux VMs, including any unique considerations for Linux workloads.
  • Clarify EFI/BIOS support for Linux VMs and document any limitations or workarounds.
  • Where Windows Server versions are mentioned, also mention supported Linux distributions and versions.
  • Include troubleshooting steps and compatibility notes for Linux VMs, especially in sections discussing failover, replication, and disk types.
  • Ensure that examples and documentation are presented in a platform-neutral manner, or alternate between Windows and Linux examples.
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-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation assumes the use of Windows for managing the configuration server, referencing a Windows-specific tool (_cspsconfigtool.exe_) and instructing users to use a Desktop shortcut. There are no instructions or examples for Linux-based configuration servers, nor any mention of Linux-compatible tools or workflows. Windows terminology and patterns are presented exclusively and first, with no Linux parity.
Recommendations
  • Clarify whether the configuration server can be run on Linux, and if so, provide equivalent instructions for Linux users.
  • If _cspsconfigtool.exe_ is Windows-only, mention this explicitly and provide alternatives or workarounds for Linux environments.
  • Include Linux command-line examples or instructions for managing accounts and configuration server settings.
  • Avoid assuming the presence of a Desktop shortcut; provide guidance for launching tools from the command line or other environments.
  • Add a section addressing cross-platform support and limitations.
GitHub Create Pull Request
Site Recovery Fail back Azure VMware Solution VMsfrom Azure with Azure Site Recovery ...b/main/articles/site-recovery/avs-tutorial-failback.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page contains a notable Windows bias: it provides a specific operational note for Windows VMs regarding VMware Tools, but does not mention Linux VM behavior or provide Linux-specific guidance. No Linux examples, troubleshooting, or parity notes are present, and Windows is referenced first and exclusively in the operational notes.
Recommendations
  • Add a corresponding note for Linux VMs, describing how VMware Tools are handled during failover/failback.
  • Include troubleshooting steps or behavioral differences for Linux VMs, if any exist.
  • Ensure examples and operational notes cover both Windows and Linux VMs, or clarify when instructions are OS-agnostic.
  • Consider listing both Windows and Linux in notes, or providing links to OS-specific documentation.
GitHub Create Pull Request
Site Recovery Replicate Azure Stack Hub to Azure using Azure Site Recovery ...in/articles/site-recovery/azure-stack-site-recovery.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation demonstrates a moderate Windows bias. Windows operating systems and tools (e.g., registry edits, Windows Firewall, RDP) are described first and in greater detail, with step-by-step instructions and command-line examples. Linux instructions are present but less detailed, with fewer command examples and less troubleshooting guidance. Windows-specific tools (e.g., wf.msc, GPO, registry editing) are mentioned without Linux equivalents, and remote access setup is described only for Windows (RDP), not for Linux (SSH is mentioned only for the Mobility service).
Recommendations
  • Provide Linux examples and troubleshooting steps with equal detail, including command-line instructions for firewall configuration and service management.
  • Include Linux-first or side-by-side examples for all steps, especially where Windows tools (e.g., registry, wf.msc) are referenced.
  • Add guidance for remote access setup on Linux (e.g., SSH configuration, firewall rules) similar to the RDP instructions for Windows.
  • Ensure parity in describing permissions, account setup, and service installation for both platforms.
  • Where Windows-specific tools are mentioned, offer Linux alternatives (e.g., ufw/firewalld for firewall, systemctl for service management).
GitHub Create Pull Request
Site Recovery Automatic update of the Mobility service in Azure Site Recovery ...in/articles/site-recovery/azure-to-azure-autoupdate.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example
Summary
The documentation provides only Azure PowerShell script examples for customizing automation account settings, with no equivalent Bash, Azure CLI, or Linux-native instructions. The script is written in PowerShell, which is most familiar and available by default on Windows systems. There is no mention of how to perform these tasks from Linux/macOS environments, nor are alternative tools or commands (such as Azure CLI or Bash) referenced.
Recommendations
  • Provide equivalent Azure CLI or Bash script examples for managing automation account settings and enabling/disabling automatic updates.
  • Explicitly state whether the PowerShell script can be run on Linux/macOS (e.g., via PowerShell Core), and provide installation guidance if so.
  • Add a section or note for Linux/macOS users, outlining any differences or prerequisites for running the automation tasks.
  • Where possible, use cross-platform tools (e.g., Azure CLI) for examples, or present both PowerShell and CLI/Bash alternatives side-by-side.
GitHub Create Pull Request
Site Recovery Common questions about Azure virtual machine disaster recovery with Azure Site Recovery ...icles/site-recovery/azure-to-azure-common-questions.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits moderate Windows bias. PowerShell is frequently referenced as the primary or only automation method, with no mention of Bash, Azure CLI, or Linux-native tooling. Windows-specific technologies (e.g., Volume Shadow Copy Service, ADE for Windows, SQL Server extensions) are described in detail, while Linux equivalents are either missing or briefly mentioned. Examples and instructions often assume Windows environments, and Linux scenarios (such as shared disk support) are explicitly unsupported or given less detail.
Recommendations
  • Provide Azure CLI and Bash examples alongside PowerShell for all automation steps.
  • Explicitly document Linux support and limitations in each relevant section, including parity for features like disk encryption, shared disks, and app-consistent snapshots.
  • Include Linux-specific instructions and troubleshooting steps, especially for tasks currently described only for Windows (e.g., extension installation, automation account selection).
  • Mention Linux tools and patterns (e.g., shell scripts, cron jobs) where automation is discussed.
  • Ensure that Linux scenarios are covered with equal detail and clarity as Windows scenarios.
GitHub Create Pull Request
Site Recovery Enable replication for encrypted Azure VMs in Azure Site Recovery ...ry/azure-to-azure-how-to-enable-replication-ade-vms.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page exhibits a notable Windows bias. Key operational steps, such as copying disk encryption keys, are provided only via a Windows PowerShell script, with instructions explicitly referencing 'Windows PowerShell application.' There are no equivalent Linux/macOS CLI or shell script examples, nor guidance for running these tasks on non-Windows platforms. The page also references PowerShell cmdlets for updating replication settings, without mentioning Azure CLI or Bash alternatives. This creates friction for Linux/macOS users, who must find their own workarounds.
Recommendations
  • Provide equivalent instructions and scripts for Linux/macOS users, such as Bash or Azure CLI examples for copying keys and updating replication settings.
  • Clarify whether the PowerShell script can be run cross-platform (e.g., via PowerShell Core on Linux/macOS), and provide installation guidance if so.
  • Add Azure CLI commands for all PowerShell-only steps, especially for key vault operations and replication management.
  • Explicitly mention Linux/macOS compatibility in all scripting/tooling sections, and avoid assuming a Windows environment.
  • Reorder examples so that platform-neutral or Linux/macOS steps are presented alongside or before Windows-specific instructions.
GitHub Create Pull Request
Site Recovery Support Matrix for Azure VM Disaster Recovery with Azure Site Recovery ...rticles/site-recovery/azure-to-azure-support-matrix.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a Windows-first bias in several areas. Windows operating systems are listed before Linux, and Windows-specific requirements (such as SSU and SHA-2 updates) are described in detail, while Linux instructions are less explicit. Azure PowerShell is repeatedly referenced as the primary automation tool, with Azure CLI explicitly marked as unsupported, which disadvantages Linux/macOS users. Disk and storage encryption features are described with Windows examples first, and troubleshooting/known issues are more detailed for Windows. There are no Linux shell or CLI examples, and Linux-specific automation or troubleshooting steps are less visible.
Recommendations
  • Provide Linux shell (bash) and Azure CLI examples for all automation steps currently shown only with PowerShell.
  • List Linux operating systems and features before or alongside Windows, rather than after.
  • Include troubleshooting and upgrade instructions for Linux with the same level of detail as Windows.
  • Clarify or expand support for Linux-native tools and workflows, such as Azure CLI, and document any workarounds for unsupported features.
  • Ensure parity in documentation for encryption, disk management, and networking features between Windows and Linux.
  • Add explicit guidance for Linux/macOS users where PowerShell is referenced, including alternatives or installation instructions.
GitHub Create Pull Request
Site Recovery Troubleshoot Azure VM replication in Azure Site Recovery - other issues ...es/site-recovery/azure-to-azure-troubleshoot-errors.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation shows some Windows bias, notably in the ordering and detail of troubleshooting steps. Windows solutions (such as using Windows Update, Services console, Internet Explorer proxy detection) are often described first or in more detail, while Linux guidance is sometimes less specific or relies on users to consult their OS distributor. Some sections (COM+ or VSS errors) are Windows-only, with no Linux equivalent or workaround described. Proxy troubleshooting mentions autodetection from Internet Explorer for Windows, but only briefly notes Linux uses /etc/environment. The documentation does provide Linux-specific instructions for certificate management and ADE disk issues, but overall, Windows patterns and tools are referenced more prominently.
Recommendations
  • Ensure Linux and macOS troubleshooting steps are presented with equal detail and clarity as Windows steps.
  • Where Windows tools (e.g., Services console, Internet Explorer) are mentioned, provide equivalent Linux/macOS commands or GUI steps (e.g., systemctl for services, environment variable configuration for proxies).
  • For sections that are Windows-only (e.g., COM+ or VSS), clarify if these errors are not applicable to Linux/macOS, or provide analogous Linux troubleshooting if relevant.
  • Present OS-specific guidance in parallel tabs or sections, and avoid consistently listing Windows first.
  • Include explicit Linux/macOS examples for proxy configuration, service management, and certificate updates, not just references to distributor documentation.
GitHub Create Pull Request
Site Recovery Troubleshoot Azure VM replication in Azure Site Recovery - VM errors ...site-recovery/azure-to-azure-virtual-machine-errors.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation exhibits a Windows bias in several ways. For disk initialization, the Windows instructions and link are listed first, with Linux as a secondary note. For cleanup of stale Site Recovery configurations, only a PowerShell script (.ps1) is provided, with no mention of a Bash, CLI, or Linux-native alternative. This assumes users have access to Windows or PowerShell environments, creating friction for Linux/macOS users. There are no explicit Linux/macOS examples or scripts for key troubleshooting steps.
Recommendations
  • Provide Bash or Azure CLI script equivalents for the stale Site Recovery configuration cleanup, or document how Linux/macOS users can perform the same operation.
  • List Linux instructions/examples alongside Windows, or alternate which is presented first to avoid implicit prioritization.
  • Explicitly state platform requirements for provided scripts and offer guidance for users on other platforms.
  • Where possible, use cross-platform tools (e.g., Azure CLI) in examples, or provide both PowerShell and CLI versions.
GitHub Create Pull Request
Site Recovery Troubleshoot replication of Azure VMs with Azure Site Recovery ...te-recovery/azure-to-azure-troubleshoot-replication.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits several Windows-centric biases. Many troubleshooting steps, especially those involving disk exclusion and VSS-related errors, provide only Windows/Powershell commands or reference Windows file paths and services. Linux equivalents are either missing, mentioned after Windows, or referenced only briefly. Windows tools and patterns (e.g., VSS, .cmd scripts, Windows service names) are described in detail, while Linux troubleshooting is less explicit and lacks step-by-step guidance.
Recommendations
  • Provide Linux-specific commands and examples alongside Windows/Powershell instructions, especially for disk exclusion and service management.
  • Include Linux file paths and log locations wherever Windows paths are mentioned.
  • Offer troubleshooting steps for Linux app-consistency issues with detailed command-line instructions, not just a link.
  • Describe how to restart relevant services on Linux (e.g., systemctl commands for vxagent, appservice) in parity with Windows service instructions.
  • When referencing configuration files (e.g., RCMInfo.conf), show Linux editing steps and commands.
  • Ensure that all error codes and log analysis steps are applicable to both Windows and Linux, or clarify differences.
GitHub Create Pull Request
Site Recovery Azure Virtual Machines disaster recovery - High Churn support ...recovery/concepts-azure-to-azure-high-churn-support.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page generally avoids platform-specific instructions, focusing on Azure portal workflows. However, in the support matrix for Enhanced Churn (500 MB/s preview), 'Operating System: Windows' is listed first, and Linux support is limited to specific distributions (RHEL 9, SLES 15, Ubuntu 24.04). No Linux/macOS command-line or tooling examples are provided, nor is there discussion of Linux-specific considerations. This creates a subtle Windows-first bias and leaves Linux users with less clarity about broader compatibility.
Recommendations
  • Explicitly list all supported Linux distributions and versions, or clarify if only the named ones are supported.
  • Provide parity in examples or instructions for Linux VMs, including any differences in configuration or troubleshooting.
  • If there are OS-specific requirements or limitations, document them in detail for both Windows and Linux.
  • Avoid listing Windows before Linux in support matrices unless there is a technical reason.
  • Add a section addressing Linux-specific disaster recovery considerations, if any.
GitHub Create Pull Request
← Previous Page 6 of 10 Next →