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 51-75 of 232 flagged pages
Site Recovery Support for disaster recovery of Hyper-V VMs to Azure with Azure Site Recovery ...articles/site-recovery/hyper-v-azure-support-matrix.md
High 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 is heavily focused on Windows environments, specifically Hyper-V on Windows Server and System Center Virtual Machine Manager. All examples, requirements, and supported scenarios are Windows-centric, with no mention of Linux-based Hypervisors or management tools. Linux is only referenced as a guest OS, not as a platform for hosting or managing VMs. PowerShell is mentioned as the only CLI automation option, and Windows Server versions are listed exclusively. This creates friction for users on Linux or macOS, who cannot use Hyper-V or the described tooling.
Recommendations
  • Clarify early in the documentation that Hyper-V is a Windows-only technology and that Linux hosts are not supported for this scenario.
  • Provide links or references to equivalent disaster recovery solutions for Linux-based hypervisors (e.g., KVM, Xen) if available in Azure Site Recovery or elsewhere.
  • If Azure Site Recovery supports other platforms, add parity tables/examples for those.
  • Mention alternative CLI tools (e.g., Azure CLI, Bash scripts) where possible, not just PowerShell.
  • Explicitly state the lack of support for Linux/macOS hosts to help users avoid confusion.
GitHub Create Pull Request
Site Recovery Analyze the Hyper-V Deployment Planner report in Azure Site Recovery ...-recovery/hyper-v-deployment-planner-analyze-report.md
High 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-specific concepts, tools, and file formats (VHD/VHDX, Hyper-V Replica Broker, etc.) throughout. There are no examples, guidance, or references for Linux or macOS environments, nor for alternative virtualization platforms. All operational details, troubleshooting, and recommendations are tailored to Windows/Hyper-V users, with no mention of Linux equivalents or cross-platform considerations.
Recommendations
  • Explicitly state that the guide is for Hyper-V (Windows) environments and clarify its scope at the beginning.
  • Provide links or references to equivalent Azure Site Recovery documentation for Linux-based environments (e.g., VMware, physical Linux servers).
  • If possible, add a comparison table or section outlining differences and similarities between Hyper-V and Linux/VMware deployments in Azure Site Recovery.
  • Include notes or callouts for Linux users, such as supported disk formats, replication requirements, and tooling differences.
  • Ensure that related documentation for Linux/VMware is easily discoverable from this page.
GitHub Create Pull Request
Site Recovery Run the Hyper-V Deployment Planner in Azure Site Recovery ...ticles/site-recovery/hyper-v-deployment-planner-run.md
High 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 is heavily biased towards Windows environments. All examples use Windows-style paths (e.g., E:\...), reference Notepad for file editing, and the tool (ASRDeploymentPlanner.exe) is a Windows executable. There is no mention of running the tool on Linux or macOS, nor are there any Linux-specific instructions, examples, or alternatives. Windows conventions and tools are assumed throughout, with no parity for Linux users.
Recommendations
  • Explicitly state OS requirements and whether the tool can run on Linux/macOS (e.g., via Mono, Wine, or a native port).
  • If Linux/macOS is supported, provide equivalent command-line examples using Linux paths and editors (e.g., /home/user/..., nano, vi).
  • If the tool is Windows-only, suggest workarounds for Linux users (such as running in a VM or container) and clarify limitations.
  • Mention file format compatibility (e.g., Excel XLSM files) and how Linux/macOS users can view or process the reports.
  • Consider providing a cross-platform version of the tool or a web-based alternative.
GitHub Create Pull Request
Site Recovery Prepare on-premises Hyper-V servers for disaster recovery by using Azure Site Recovery .../site-recovery/hyper-v-prepare-on-premises-tutorial.md
High Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation is heavily focused on Windows environments, specifically Hyper-V and System Center Virtual Machine Manager, with all examples and instructions tailored to Windows tools and patterns. There are no Linux or macOS examples, nor any mention of how non-Windows users might prepare or connect to VMs after failover. Remote access instructions are exclusively for Windows (RDP, Windows Firewall), and troubleshooting steps reference Windows-specific resources.
Recommendations
  • Clarify early that the tutorial is only applicable to Windows/Hyper-V environments, or add guidance for Linux-based hypervisors if supported.
  • Include instructions or references for connecting to Linux VMs after failover (e.g., SSH setup, Linux firewall configuration).
  • If Azure Site Recovery supports Linux guests, provide parity in post-failover access and troubleshooting steps.
  • Mention alternatives to Windows tools (such as SSH for Linux) where relevant.
  • Explicitly state any limitations regarding non-Windows hosts or guests.
GitHub Create Pull Request
Site Recovery Set up Hyper-V (with VMM) disaster recovery using Azure Site Recovery ...n/articles/site-recovery/hyper-v-vmm-azure-tutorial.md
High Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Missing Linux Example Windows First
Summary
The documentation is heavily focused on Windows environments, specifically Hyper-V hosts managed by System Center VMM. All examples and instructions reference Windows tools, installers, and PowerShell commands. There are no Linux or macOS equivalents or alternative instructions, and Windows-specific terminology and steps are used throughout. The only operating systems mentioned are Windows and Windows Core, with no guidance for non-Windows platforms.
Recommendations
  • Clarify early that this guide is intended only for Windows/Hyper-V environments, and provide links to Linux/KVM or VMware disaster recovery guides if available.
  • Where possible, mention whether any components (such as the Recovery Services agent) have Linux versions, and provide installation instructions for those.
  • If Azure Site Recovery supports Linux VMs or other hypervisors, add parity sections or cross-links to relevant documentation.
  • Avoid showing only PowerShell commands; if CLI or script-based steps exist for Linux, include them.
  • Explicitly state platform limitations and alternatives for non-Windows users.
GitHub Create Pull Request
Site Recovery Manage the configuration server for physical servers in Azure Site Recovery .../site-recovery/physical-manage-configuration-server.md
High Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows Only Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation is heavily biased toward Windows environments. All prerequisites, installation steps, command-line instructions, and troubleshooting are written for Windows Server only. The use of Windows-specific tools (Control Panel, registry edits, PowerShell, .exe installers) is pervasive, and there are no examples or instructions for Linux or macOS users. Linux is not mentioned as a supported platform, and no Linux equivalents or workarounds are provided.
Recommendations
  • Explicitly state platform support: If only Windows is supported, clarify this early in the documentation. If Linux/macOS support is planned or possible, add relevant sections.
  • Provide Linux/macOS parity: If the configuration server can be run on Linux, add installation, configuration, and management instructions for Linux (e.g., shell commands, package requirements, service management).
  • Offer alternative commands: Where PowerShell or Windows registry edits are required, provide equivalent bash or Linux commands if applicable.
  • Mention tool alternatives: For steps using Control Panel, .exe files, or Windows-specific utilities, suggest Linux alternatives (e.g., using systemctl, editing config files, using apt/yum for package management).
  • Clarify limitations: If Linux cannot be used, explain why and suggest supported alternatives for Linux-based environments.
GitHub Create Pull Request
Site Recovery Support matrix for shared disks in Azure VM disaster recovery ...n/articles/site-recovery/shared-disk-support-matrix.md
High Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation exclusively references Windows workloads, Windows Server SKUs, and Windows Server Failover Clustering (WSFC) as the supported platform and clustering solution for shared disks in Azure Site Recovery. There is no mention of Linux virtual machines, Linux clustering solutions, or parity in supported scenarios, which indicates a strong Windows bias.
Recommendations
  • Explicitly state whether Linux virtual machines and Linux clustering solutions (e.g., Pacemaker, Corosync) are supported or not.
  • If Linux is unsupported, provide guidance or a roadmap for future support.
  • If Linux is supported in any scenario, add equivalent examples and tables for Linux workloads.
  • Include a comparison table for both Windows and Linux platforms, listing supported and unsupported features for each.
  • Clarify limitations for non-Windows users in the introduction and scenario tables.
GitHub Create Pull Request
Site Recovery Set up Active Directory/DNS disaster recovery with Azure Site Recovery ...ticles/site-recovery/site-recovery-active-directory.md
High 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 is heavily oriented toward Windows environments, with all examples, tools, and troubleshooting steps referencing Windows Server, Windows command-line utilities (NET SHARE, dcdiag, nltest, dnscmd), Windows registry edits, and Windows-specific concepts (FSMO, SYSVOL, DFSR, FRS). There are no Linux or macOS equivalents provided, nor is there any mention of how to accomplish Active Directory/DNS disaster recovery in non-Windows environments. The documentation assumes the use of Windows-based domain controllers and DNS servers, and does not address scenarios where Samba or BIND might be used.
Recommendations
  • Add guidance for environments using Samba as an Active Directory domain controller on Linux, including replication and failover steps.
  • Include DNS disaster recovery instructions for BIND or other Linux-based DNS servers.
  • Provide Linux/macOS command equivalents for troubleshooting (e.g., alternatives to dcdiag, nltest, dnscmd).
  • Clarify Windows-specific steps and offer parallel instructions for non-Windows setups where possible.
  • Explicitly state platform limitations if Azure Site Recovery only supports Windows-based AD/DNS, and suggest alternatives for Linux users.
GitHub Create Pull Request
Site Recovery Disaster recovery of Dynamics AX with Azure Site Recovery ...ain/articles/site-recovery/site-recovery-dynamicsax.md
High 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 oriented towards Windows environments, specifically referencing Windows Server, Active Directory, SQL Server, and Dynamics AX components that are Windows-only. All examples, prerequisites, and recovery steps assume Windows-based infrastructure. There is no mention of Linux or macOS alternatives, nor are any cross-platform considerations or examples provided. The guidance is not applicable to Linux users, as Dynamics AX and its components are Windows-only.
Recommendations
  • Explicitly state that Dynamics AX and its disaster recovery process are Windows-centric, and clarify platform limitations early in the documentation.
  • If any components (e.g., Azure Site Recovery, SQL Server) have Linux support, provide parallel examples or links to Linux-specific guidance.
  • Add a section addressing cross-platform scenarios, even if only to note that Linux/macOS are not supported for Dynamics AX disaster recovery.
  • Where possible, mention alternatives for Linux-based ERP solutions and their disaster recovery strategies.
GitHub Create Pull Request
Site Recovery Azure Site Recovery Deployment Planner for VMware disaster recovery ...cles/site-recovery/site-recovery-deployment-planner.md
High Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First Powershell Heavy
Summary
The documentation for the Azure Site Recovery Deployment Planner is heavily biased towards Windows environments. All instructions, prerequisites, and examples assume the use of Windows Server or Windows PC, with no mention of Linux or macOS alternatives. The tool itself appears to be Windows-only, requiring Windows-specific dependencies such as .NET Framework and Visual C++ Redistributable. There are no examples or guidance for running the tool on Linux or macOS, nor any discussion of cross-platform support.
Recommendations
  • Explicitly state platform limitations at the top of the documentation, clarifying that the tool is Windows-only if that is the case.
  • If possible, provide or develop a cross-platform version of the tool, or offer guidance for Linux/macOS users (e.g., running the tool in a VM or container).
  • Include alternative instructions or workarounds for Linux/macOS users, such as using Azure CLI, PowerShell Core (if supported on Linux), or other platform-agnostic methods.
  • Add a FAQ or troubleshooting section addressing common issues for non-Windows users.
  • Consider providing a roadmap or feedback channel for users requesting Linux/macOS support.
GitHub Create Pull Request
Site Recovery Remove servers and disable protection ...ry/site-recovery-manage-registration-and-protection.md
High 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 heavily biased towards Windows environments, specifically System Center VMM, Hyper-V, and PowerShell. All example scripts and procedures use Windows-only tools and PowerShell commands, with no mention of Linux or macOS equivalents. There are no instructions or examples for unregistering or disabling protection for Linux-based servers, nor any guidance for users managing Site Recovery from non-Windows platforms.
Recommendations
  • Add explicit instructions and examples for unregistering and disabling protection for Linux servers, including any required shell scripts or CLI commands.
  • Provide parity for cleanup operations on Linux-based Configuration Servers, including how to remove mobility service and unregister from the vault.
  • Include notes or sections for macOS users if relevant, or clarify platform limitations.
  • Where PowerShell scripts are shown, offer Bash or Python alternatives for Linux environments.
  • Clearly indicate which procedures are Windows-specific and provide links or references to Linux documentation where available.
GitHub Create Pull Request
Site Recovery Disaster recovery for a multi-tier SharePoint app using Azure Site Recovery ...ain/articles/site-recovery/site-recovery-sharepoint.md
High 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 is heavily oriented towards Windows environments, specifically Windows Server and SharePoint on Windows. All examples, scripts, and recovery steps reference Windows tools (e.g., PowerShell cmdlets, DFSR, Central Administration GUI), and there are no Linux or cross-platform alternatives provided. The prerequisites, architecture, and recovery plan steps assume a Windows-based SharePoint deployment, with no mention of Linux-based workloads or equivalent tooling.
Recommendations
  • Add explicit guidance for Linux-based SharePoint alternatives (e.g., SharePoint on Docker, or guidance for similar multi-tier Linux web apps).
  • Include Linux/macOS equivalents for scripting and automation steps (e.g., Bash scripts, Azure CLI commands).
  • Reference cross-platform tools for file replication and backup (e.g., rsync, scp) alongside Windows tools like DFSR and AzCopy.
  • Clarify which steps are Windows-specific and provide alternative instructions or links for Linux environments.
  • Where PowerShell is used, provide Azure CLI or REST API equivalents for automation tasks.
GitHub Create Pull Request
Site Recovery Shared disks in Azure Site Recovery ...ob/main/articles/site-recovery/tutorial-shared-disk.md
High 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 exclusively describes disaster recovery for Windows Server Failover Clusters (WSFC) on Azure virtual machines using shared disks. There is no mention of Linux-based clustering solutions (e.g., Pacemaker, Corosync), nor are any Linux examples, tools, or patterns provided. The prerequisites and all workflow steps assume a Windows environment, creating a strong Windows bias.
Recommendations
  • Clarify in the introduction whether Linux-based clusters are supported or not. If not supported, state this explicitly.
  • If Linux clustering is supported, add equivalent instructions for configuring disaster recovery for Linux clusters (e.g., Pacemaker/Corosync) using Azure shared disks.
  • Include Linux-specific prerequisites and examples, such as commands for managing shared disks and failover procedures on Linux.
  • Provide parity in screenshots and step-by-step guides for Linux environments where applicable.
GitHub Create Pull Request
Site Recovery Run the Deployment Planner for VMware disaster recovery with Azure Site Recovery ...ecovery/site-recovery-vmware-deployment-planner-run.md
High Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias. All command-line examples for gathering VM lists use VMware vSphere PowerCLI (PowerShell), with no mention of Linux alternatives (such as using the vSphere CLI, govc, or pyVmomi). The ASRDeploymentPlanner.exe tool itself is a Windows executable, and all example file paths and instructions use Windows conventions (e.g., drive letters, UNC paths, Notepad). Report generation explicitly requires a Windows PC or Server with Microsoft Excel. No Linux or macOS usage patterns, tools, or workarounds are provided.
Recommendations
  • Provide Linux/macOS alternatives for gathering VM lists, such as using govc, pyVmomi, or vSphere CLI, with example commands.
  • Clarify whether ASRDeploymentPlanner.exe can be run under Wine or in a Windows VM on Linux/macOS, or provide a cross-platform version if possible.
  • Include instructions for viewing and editing text files using Linux tools (e.g., cat, nano, vim) instead of Notepad.
  • Mention file path conventions for Linux/macOS and clarify UNC path usage.
  • Explicitly state Windows-only requirements up front, and suggest workarounds for non-Windows users (e.g., running the tool in a Windows VM or container).
  • If possible, provide a method to generate reports without requiring Microsoft Excel on Windows (e.g., CSV or web-based report).
GitHub Create Pull Request
Site Recovery Unregister a Virtual Machine Manager server script ...articles/site-recovery/unregister-vmm-server-script.md
High 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 heavily biased towards Windows, providing only PowerShell script examples and instructions that rely on Windows-specific tools (e.g., registry paths, Windows services, Windows clustering, and SCVMM). There are no Linux or macOS equivalents, nor any mention of how to perform similar operations on non-Windows platforms. All examples and instructions assume a Windows environment.
Recommendations
  • Clearly state in the introduction that the script and instructions are Windows-only and not applicable to Linux/macOS.
  • If Linux or macOS support is possible, provide equivalent cleanup instructions or scripts for those platforms.
  • Add a section explaining the limitations for non-Windows users and suggest alternative approaches if available.
  • Consider providing cross-platform management guidance or links to relevant Linux/macOS documentation if VMM or Azure Site Recovery supports those platforms.
GitHub Create Pull Request
Site Recovery Manage the configuration server for disaster recovery with Azure Site Recovery ...e-recovery/vmware-azure-manage-configuration-server.md
High 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 page exhibits a notable Windows bias. Many operational examples and instructions reference Windows-specific tools (PowerShell, .exe utilities, Windows file paths), and Windows-centric procedures are described in detail. There is little to no mention of Linux/macOS equivalents, and steps for critical tasks (such as certificate renewal, server registration, and credential management) rely on Windows-only tools or PowerShell commands. Linux users are left without guidance for performing these tasks, despite the product supporting replication of Linux physical servers.
Recommendations
  • Provide Linux/macOS-specific instructions and examples for all major tasks, especially those currently described only with Windows tools.
  • Include shell (bash) command equivalents for PowerShell examples, and clarify how to perform tasks on Linux-based configuration servers (if supported).
  • Document the location and usage of configuration server utilities on Linux, or clarify if certain tasks must be performed from a Windows machine.
  • Explicitly state OS requirements and limitations for each procedure, so Linux/macOS users know what is and isn't possible.
  • Add parity in screenshots and file path references (e.g., show both Windows and Linux paths where relevant).
GitHub Create Pull Request
Site Recovery Set up a scale-out process server during disaster recovery of VMware VMs and physical servers with Azure Site Recovery | Microsoft Docs ...e-recovery/vmware-azure-set-up-process-server-scale.md
High 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 exclusively describes installation and command-line usage of the process server using Windows executables (UnifiedSetup.exe, MicrosoftAzureSiteRecoveryUnifiedSetup.exe), with all examples and instructions referencing Windows paths, conventions, and tools. There is no mention of Linux installation methods, Linux-compatible binaries, or examples for Linux/macOS environments, despite the fact that VMware and physical servers may run on non-Windows platforms.
Recommendations
  • Clarify whether the process server can be installed on Linux or macOS, and if so, provide equivalent installation instructions and command-line examples for those platforms.
  • If the process server is Windows-only, explicitly state this limitation early in the prerequisites section.
  • Provide guidance for Linux users on how to participate in the replication process, or alternative approaches if direct installation is not supported.
  • Include Linux file path and shell command examples where applicable, or note differences in usage.
GitHub Create Pull Request
Site Recovery Troubleshoot upgrade of the Microsoft Azure Site Recovery Provider ...recovery/vmware-azure-troubleshoot-upgrade-failures.md
High 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 exclusively references Windows tools (Command Prompt, Registry Editor, Task Manager), Windows file paths (C:\), and Windows executables (.exe), with no mention of Linux/macOS equivalents or guidance. All examples and troubleshooting steps are Windows-centric, leaving Linux users without actionable instructions.
Recommendations
  • Add Linux/macOS-specific instructions for upgrading the Site Recovery Provider, including relevant commands and file paths.
  • Provide examples using Linux shell commands (e.g., tar, unzip) for extracting setup files.
  • Clarify whether the Site Recovery Provider is supported on Linux/macOS, and if not, explicitly state this in the documentation.
  • If supported, include troubleshooting steps for common Linux/macOS upgrade issues, such as permissions, package management, and log file locations.
  • List Windows and Linux/macOS steps in parallel sections, or clearly indicate platform-specific instructions.
GitHub Create Pull Request
Site Recovery Troubleshoot replication issues for disaster recovery of VMware virtual machines and physical servers to Azure by using Azure Site Recovery ...site-recovery/vmware-azure-troubleshoot-replication.md
High Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example Powershell Heavy
Summary
The documentation page demonstrates a notable Windows bias. All file paths, log locations, service names, and command-line instructions are given in Windows format (e.g., C:\Program Files, %PROGRAMDATA%, cmd, net stop/start). There are no Linux or macOS equivalents or examples, despite Azure Site Recovery supporting physical servers that could run Linux. Troubleshooting steps and permissions guidance are exclusively Windows-centric, and there is no mention of Linux tools, commands, or log locations.
Recommendations
  • Add equivalent Linux/macOS instructions for all troubleshooting steps, including log locations, service management, and agent installation.
  • Provide Linux file path examples (e.g., /var/log/...) alongside Windows paths.
  • Include Linux commands for service management (e.g., systemctl, service) and agent registration.
  • Clarify which steps are Windows-only and which apply to Linux, and provide parity where possible.
  • Mention Linux-specific issues or considerations in relevant troubleshooting sections.
GitHub Create Pull Request
Site Recovery Troubleshoot VMware vCenter discovery failures in Azure Site Recovery ...tps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/vmware-azure-troubleshoot-vcenter-discovery-failures.md
High Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias. Troubleshooting steps rely on Windows-specific tools (PsExec, Internet Explorer), Windows command-line conventions, and do not mention Linux/macOS equivalents or alternatives. All examples and instructions assume a Windows environment, making it difficult for Linux/macOS users to follow or replicate the procedures.
Recommendations
  • Provide Linux/macOS equivalents for proxy configuration troubleshooting, such as using 'sudo -u' or 'su' to switch user context, and instructions for modifying proxy settings via command line or relevant desktop environments.
  • Replace or supplement PsExec/Internet Explorer steps with platform-agnostic methods or Linux-native tools (e.g., using 'env' or 'sudo' to run commands as another user, editing proxy settings in configuration files).
  • Clarify which steps are Windows-only and offer alternative guidance for non-Windows environments.
  • Include explicit Linux/macOS command examples for DRA proxy configuration and service management (e.g., systemctl commands, file locations).
GitHub Create Pull Request
Site Recovery Troubleshoot VMware replication appliance health issues in Azure Site Recovery ...recovery/vmware-troubleshoot-appliance-health-issue.md
High 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 provides troubleshooting steps that rely exclusively on Windows tools and PowerShell scripts, with file paths and commands specific to Windows environments. There are no Linux or macOS equivalents, nor any mention of how to perform these tasks on non-Windows platforms. The examples and instructions assume the user is operating within a Windows OS, creating friction for Linux/macOS users.
Recommendations
  • Include equivalent troubleshooting steps for Linux-based replication appliances, if supported.
  • Provide Bash or shell script alternatives to PowerShell commands.
  • Clarify OS requirements and explicitly state if only Windows is supported for these operations.
  • If Linux/macOS are not supported, add a note at the beginning to inform users.
  • If Linux is supported, add file paths, commands, and screenshots for Linux environments.
GitHub Create Pull Request
Site Recovery Trusted launch VMs with Azure Site Recovery ...lob/main/articles/site-recovery/concepts-trusted-vm.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation exhibits moderate Windows bias. Several features (shared disks, 'Create a new VM' flow) are explicitly supported only for Windows OS, with Linux support either missing or not yet available. Windows is mentioned first in support matrices and feature lists. There are no Linux-specific examples or CLI commands, and migration instructions reference PowerShell and CLI channels but do not provide Linux-specific guidance or parity. The documentation does list supported Linux distributions and kernels, but practical Linux usage scenarios and examples are lacking.
Recommendations
  • Provide Linux-specific examples and CLI commands, especially for migration and agent uninstallation.
  • Clarify timelines or workarounds for Linux support in features currently limited to Windows (e.g., shared disks, VM creation flow).
  • Present OS support in a neutral order or highlight Linux parity where available.
  • Add troubleshooting and usage notes for Linux users, especially where steps differ from Windows.
  • Explicitly state when a feature is unavailable for Linux and suggest alternatives or expected availability.
GitHub Create Pull Request
Site Recovery Move Azure VMs to a different Azure region with Azure Site Recovery ...icles/site-recovery/azure-to-azure-tutorial-migrate.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 page provides explicit instructions for Windows VMs regarding root certificates and updates, while Linux VMs are only briefly mentioned with a reference to distributor guidance. Windows instructions are more detailed and appear first, with no concrete Linux commands or examples provided. There are no PowerShell-specific commands or Windows-only tools, but the guidance is more complete for Windows users.
Recommendations
  • Provide step-by-step instructions or links for updating root certificates on popular Linux distributions (e.g., Ubuntu, CentOS, RHEL).
  • Include Linux-specific troubleshooting tips for certificate issues, similar to the Windows update guidance.
  • Ensure parity in detail and clarity for both Windows and Linux VM preparation steps.
  • Consider listing Linux instructions before or alongside Windows instructions to avoid implicit prioritization.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example
Summary
The documentation provides a detailed PowerShell script for customizing automation accounts, but does not offer equivalent instructions or examples for Linux/macOS users (e.g., Bash, Azure CLI). All scripting guidance is Windows-centric, assuming use of PowerShell, which may create friction for users on non-Windows platforms.
Recommendations
  • Provide equivalent Azure CLI or Bash script examples for managing automation accounts and extension update settings.
  • Clarify whether the PowerShell script can be run cross-platform (e.g., in Azure Cloud Shell, which supports PowerShell Core on Linux/macOS), or offer platform-agnostic alternatives.
  • Explicitly mention Linux/macOS compatibility and provide guidance for those environments where possible.
  • Add troubleshooting steps relevant to Linux/macOS users, if any differences exist.
GitHub Create Pull Request
Site Recovery About using ExpressRoute with Azure Site Recovery ...e-recovery/concepts-expressroute-with-site-recovery.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 page demonstrates a Windows bias, especially in the section describing proxy bypass configuration for ExpressRoute replication traffic. It exclusively references Windows tools (PsExec, Internet Explorer) and provides step-by-step instructions only for Windows environments, with no mention of Linux or macOS equivalents. The use of Windows-specific tools and patterns (PsExec, IE proxy settings) excludes Linux users from following the documented procedure directly. Additionally, Windows-centric terminology and examples appear before any consideration of cross-platform scenarios.
Recommendations
  • Add equivalent instructions for configuring proxy bypass on Linux (and macOS) servers, including relevant commands and configuration file locations.
  • Reference cross-platform tools (e.g., curl, wget, or browser-independent proxy settings) instead of or in addition to Windows-only tools like PsExec and Internet Explorer.
  • Explicitly state platform requirements and provide links to platform-specific guidance where procedures differ.
  • Where possible, use platform-neutral language and examples, or present Windows and Linux/macOS examples side-by-side.
GitHub Create Pull Request
← Previous Page 3 of 10 Next →