Site Recovery

199
Total Pages
64
Linux-Friendly Pages
135
Pages with Bias
67.8%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

864 issues found
Showing 51-75 of 864 flagged pages
Site Recovery Enable replication for encrypted Azure VMs in Azure Site Recovery ...ry/azure-to-azure-how-to-enable-replication-ade-vms.md
High Priority View Details →
Scanned: 2026-01-11 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 demonstrates a Windows bias by providing PowerShell-based instructions and scripts for key operations (such as copying encryption keys), referencing the Windows PowerShell application explicitly, and omitting equivalent Linux shell or CLI examples. The only automation script provided is a PowerShell script, and there is no mention of Bash, Azure CLI, or cross-platform alternatives. This may hinder Linux users, especially since Azure Disk Encryption is supported for Linux VMs (with some limitations), but the documentation does not provide parity in guidance or tooling.
Recommendations
  • Provide equivalent Bash or Azure CLI examples for copying keys and managing permissions, especially for Linux users.
  • Clearly indicate cross-platform options for automation, such as using Azure CLI or REST API, and provide step-by-step instructions for those.
  • Avoid referencing 'Windows PowerShell application' exclusively; mention how to run scripts on Linux/macOS (e.g., via PowerShell Core or Azure CLI).
  • Where PowerShell scripts are provided, offer alternative scripts or commands for Linux environments.
  • Add explicit Linux-focused sections or callouts where process or tooling differs, ensuring Linux administrators have clear guidance.
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
High Priority View Details →
Scanned: 2026-01-11 00:00
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 managing replication of CMK-enabled disks, but does not offer equivalent CLI or Linux shell examples. The only code sample is Windows PowerShell, and there is no mention of Azure CLI, Bash, or Linux-specific workflows. This creates a bias toward Windows administrators and PowerShell users, potentially excluding Linux users or those who prefer cross-platform tools.
Recommendations
  • Add equivalent Azure CLI examples for all PowerShell code snippets, especially for disk replication tasks.
  • Explicitly mention that the procedures can be performed from Linux/macOS using Azure CLI or Bash, and provide links to relevant documentation.
  • Where screenshots show portal actions, clarify that these steps are platform-agnostic.
  • Ensure all automation and scripting guidance is available for both PowerShell and CLI users.
  • Include notes or sections for Linux users, such as prerequisites for running Azure CLI or Bash scripts.
GitHub Create Pull Request
Site Recovery Set up disaster recovery after migration to Azure with Azure Site Recovery ...e-recovery/azure-to-azure-replicate-after-migration.md
High Priority View Details →
Scanned: 2026-01-11 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 Windows bias by consistently presenting Windows instructions and tools before Linux equivalents. Windows-specific tools and file paths (e.g., Control Panel, MsiExec.exe, C:\WindowsAzure\Packages) are highlighted, while Linux instructions are less detailed and appear after Windows steps. Validation and troubleshooting examples are more thorough for Windows, and Linux instructions lack parity in depth and troubleshooting guidance.
Recommendations
  • Present Linux and Windows instructions in parallel, or alternate which platform is presented first.
  • Provide equally detailed validation and troubleshooting steps for Linux, including file paths, agent version checks, and log locations.
  • Include Linux-specific tools and commands (e.g., package manager commands for agent installation, log file locations) alongside Windows tools.
  • Avoid referencing Windows-only tools (e.g., Control Panel, MsiExec.exe) without providing Linux equivalents or alternatives.
  • Ensure that all examples and steps are provided for both platforms, and avoid assuming Windows as the default environment.
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
High Priority View Details →
Scanned: 2026-01-11 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 demonstrates a Windows bias in several ways: Windows troubleshooting steps and tools (such as COM+, VSS, Services console, Internet Explorer proxy detection) are described in detail, often before or instead of Linux equivalents. Some sections (e.g., COM+ or VSS errors) only provide Windows-specific instructions, omitting Linux guidance. Proxy troubleshooting mentions autodetection from Internet Explorer for Windows, while Linux instructions are less detailed. Windows update and certificate management processes are described with references to Windows documentation, while Linux guidance is more generic or less comprehensive.
Recommendations
  • For every Windows-specific troubleshooting step, provide equivalent Linux instructions or clarify when an issue is Windows-only.
  • Include Linux-specific tools and commands for troubleshooting (e.g., systemd service management for VSS-like functionality, alternatives to COM+).
  • When referencing Windows tools (e.g., Services console, Internet Explorer), also mention Linux equivalents (e.g., systemctl, environment variables, browser options).
  • Ensure examples and instructions for both platforms are equally detailed and placed side-by-side, rather than Windows-first.
  • Add links to Linux documentation and resources where Windows links are provided.
  • Explicitly state when an error or workaround applies only to Windows or only to Linux.
GitHub Create Pull Request
Site Recovery Troubleshoot replication of Azure VMs with Azure Site Recovery ...te-recovery/azure-to-azure-troubleshoot-replication.md
High Priority View Details →
Scanned: 2026-01-11 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 Windows bias in several areas: PowerShell is referenced as the primary method for disk exclusion, Windows file paths and troubleshooting steps are described in detail, and Windows-specific tools and services (such as VSS and service restarts) are explained with commands and examples. Linux equivalents are mentioned only briefly or as afterthoughts, with fewer details and no command-line examples. Troubleshooting logs and service management are described for Windows, but Linux instructions are minimal or missing.
Recommendations
  • Provide equivalent Linux command-line examples (e.g., using Bash, systemctl, or relevant Linux tools) alongside PowerShell instructions.
  • Include Linux file paths and troubleshooting steps with the same level of detail as Windows (e.g., how to locate and analyze logs, restart services, reinstall agents).
  • Mention Linux tools and patterns (such as journalctl, grep, systemctl) explicitly and provide step-by-step instructions for common tasks.
  • Ensure that Linux solutions are presented with parity, not just as brief notes or links, and avoid presenting Windows-first in lists or examples.
  • Add screenshots or illustrations for Linux workflows where Windows screenshots are shown.
GitHub Create Pull Request
Site Recovery Tutorial to set up Azure VM disaster recovery with Azure Site Recovery ...recovery/azure-to-azure-tutorial-enable-replication.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Windows Heavy Missing Linux Example
Summary
The documentation demonstrates a mild Windows bias. In the 'Verify VM certificates' section, instructions for Windows VMs are detailed first and reference Windows Update, while Linux VMs are mentioned second with less specific guidance. No Linux-specific commands, examples, or distribution-specific instructions are provided throughout the tutorial. The overall flow and screenshots are OS-agnostic, but the only explicit OS-specific steps are for Windows, with Linux relegated to a generic statement.
Recommendations
  • Provide explicit Linux examples for certificate updates, referencing common distributions (e.g., Ubuntu, CentOS) and commands (such as 'update-ca-certificates').
  • Where OS-specific instructions are given, present Windows and Linux guidance in parallel, rather than listing Windows first.
  • Include screenshots or CLI snippets for Linux environments where relevant.
  • Add troubleshooting tips for common Linux issues with Azure Site Recovery (e.g., agent installation, network configuration).
GitHub Create Pull Request
Site Recovery Troubleshoot connectivity for Azure to Azure disaster recovery with Azure Site Recovery ...ry/azure-to-azure-troubleshoot-network-connectivity.md
High Priority View Details →
Scanned: 2026-01-11 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. Troubleshooting steps and examples frequently reference Windows-specific tools and workflows, such as Internet Explorer for proxy autodetection and Windows file paths. Linux equivalents are mentioned, but often after Windows instructions or with less detail. There are no command-line examples for Linux (e.g., using iptables, systemd-resolved, or Linux CLI tools), and screenshots or UI instructions are tailored to the Azure Portal, which is platform-agnostic but the proxy troubleshooting leans Windows-first. The NSG configuration examples do not show how to validate connectivity from a Linux VM, nor do they provide Linux-specific troubleshooting commands.
Recommendations
  • Provide Linux-specific troubleshooting steps and command-line examples (e.g., using curl, dig, or iptables) for network connectivity issues.
  • Include Linux screenshots or terminal output where appropriate, especially for DNS and proxy configuration validation.
  • When referencing proxy autodetection, explain how it works on both Windows (Internet Explorer) and Linux (/etc/environment), and provide parity in detail.
  • Add examples of how to check outbound connectivity from Linux VMs (e.g., using curl or wget to test access to required URLs/IPs).
  • Ensure that file path references and configuration instructions are given for both Windows and Linux, with equal prominence.
  • Avoid mentioning Windows tools or patterns first; present Linux and Windows instructions side-by-side or in parallel sections.
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
High Priority View Details →
Scanned: 2026-01-11 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 demonstrates a Windows bias in several ways: Windows operating systems are listed before Linux in all support matrices, and Windows-specific requirements (such as SSU/SHA-2 updates) are described in detail. Azure PowerShell is repeatedly referenced as the main automation tool, with no mention of Linux-native alternatives (e.g., Bash, shell scripts). The Azure CLI is explicitly marked as 'Not currently supported' for deployment, but no Linux-friendly workaround or example is provided. Disk exclusion and other advanced features are described with PowerShell or portal instructions, omitting Linux command-line or automation examples. Windows-specific features (like Azure Disk Encryption for Windows OS) are described before Linux equivalents.
Recommendations
  • Provide Linux-first and Linux-parity examples for all automation and deployment scenarios, including shell scripts or guidance for Linux users.
  • Add explicit instructions or workarounds for Linux users where Azure CLI is not supported, such as REST API usage from Bash.
  • List Linux operating systems before or alongside Windows in support matrices to avoid implicit prioritization.
  • Include Linux-native tools and patterns (e.g., Bash, Ansible, cloud-init) in documentation for features currently described only with PowerShell.
  • Where Windows-specific requirements are detailed (e.g., SSU/SHA-2), provide equivalent troubleshooting or update guidance for Linux distributions.
  • Ensure that advanced configuration examples (like disk exclusion) are available for Linux users, not just via PowerShell or portal.
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
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation demonstrates a Windows bias in several ways. In the 'Disk not found in VM' section, the Windows instructions are listed before Linux, and the link text is more explicit for Windows. For troubleshooting stale Site Recovery configurations, only a PowerShell script (.ps1) is provided, with no equivalent Bash or Linux-native instructions. There are no Linux CLI or shell script examples for cleanup tasks, and the documentation assumes use of PowerShell and Windows tooling for these operations.
Recommendations
  • Provide Linux/Bash equivalents for PowerShell scripts, or document how to perform the same cleanup using Azure CLI or Bash scripts.
  • Present Windows and Linux instructions in parallel, with equal prominence and detail.
  • Where possible, use cross-platform tools (such as Azure CLI) in examples, and clarify which steps are OS-agnostic.
  • Explicitly mention any OS-specific limitations or requirements for troubleshooting steps.
  • Ensure that troubleshooting steps for both Windows and Linux VMs are equally detailed and accessible.
GitHub Create Pull Request
Site Recovery About using ExpressRoute with Azure Site Recovery ...e-recovery/concepts-expressroute-with-site-recovery.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Missing Linux Example Windows First
Summary
The documentation demonstrates Windows bias by exclusively referencing Windows-specific tools (PsExec, Internet Explorer) and providing configuration instructions only for Windows environments. There are no Linux equivalents or examples for proxy configuration or bypass list setup, and the guidance assumes use of Windows servers and tools. This limits accessibility for users operating Linux-based infrastructure.
Recommendations
  • Provide equivalent instructions for Linux environments, including how to configure proxy bypass lists on Linux-based Configuration Servers and Process Servers.
  • Reference Linux tools (such as curl, wget, or relevant system utilities) for proxy configuration, and avoid exclusive reliance on Windows-only tools like PsExec and Internet Explorer.
  • Include examples and step-by-step guidance for both Windows and Linux platforms when describing operational procedures.
  • Ensure that documentation does not assume Windows as the default environment, and present cross-platform instructions in parallel or in a platform-neutral manner.
GitHub Create Pull Request
Site Recovery Trusted launch VMs with Azure Site Recovery ...lob/main/articles/site-recovery/concepts-trusted-vm.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exhibits Windows bias in several ways: Windows OS is mentioned first in support statements, some features (shared disks, 'Create a new VM flow') are supported only for Windows, and there are no Linux-specific examples or CLI commands. The migration section references PowerShell and CLI channels but does not provide Linux-specific guidance or parity in examples. Linux support is discussed separately and sometimes as an exception, rather than integrated equally.
Recommendations
  • Provide Linux-specific examples and step-by-step instructions where Windows-only guidance is currently given.
  • Ensure feature parity for Linux, or clearly document timelines and alternatives for missing Linux features.
  • Present Windows and Linux information in parallel, rather than listing Windows first or as the default.
  • Include CLI/bash commands for Linux users alongside PowerShell examples.
  • Explicitly call out any limitations for Linux and offer workarounds or guidance for affected users.
GitHub Create Pull Request
Site Recovery Connect to Azure VMs on-premises failover with Azure Site Recovery ...e-recovery/concepts-on-premises-to-azure-networking.md
High Priority View Details →
Scanned: 2026-01-11 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 Windows bias in several ways. The 'Prepare on-premises machines' section provides detailed, step-by-step instructions for Windows, including references to PowerShell, Windows Firewall, RDP, and Windows Update, while the Linux section is brief and lacks comparable detail or examples. Windows tools and patterns (e.g., RDP, PowerShell, Windows Firewall) are mentioned exclusively or before their Linux equivalents (e.g., SSH, iptables). There are no Linux command examples, and guidance for Linux is minimal compared to Windows.
Recommendations
  • Provide equally detailed instructions for Linux machines, including step-by-step guidance for configuring SSH, firewall rules (e.g., using ufw, firewalld, or iptables), and checking for pending updates.
  • Include Linux command-line examples (e.g., systemctl, firewall-cmd, ufw) similar to the PowerShell examples given for Windows.
  • Mention Linux-specific remote access tools (e.g., SSH, xrdp) and how to configure them for Azure failover scenarios.
  • Ensure that Linux guidance appears alongside Windows guidance, rather than after or in summary form.
  • Reference Linux documentation pages for preparing VMs for Azure (e.g., links to Ubuntu, CentOS, or Red Hat guides).
  • Clarify any Azure-specific differences for Linux VMs (e.g., boot diagnostics, network configuration nuances).
GitHub Create Pull Request
Site Recovery Remove an Azure Site Recovery replication appliance ...s/blob/main/articles/site-recovery/delete-appliance.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Windows tools and workflows (e.g., Services.msc, Microsoft Edge, restarting the machine in a Windows context) and omitting Linux equivalents or examples. There are no instructions for Linux-based appliances, nor are Linux commands or tools mentioned. The guidance assumes the appliance is running on Windows, with no consideration for Linux-based deployments.
Recommendations
  • Include instructions for Linux-based replication appliances, if supported, such as how to restart relevant services (e.g., using systemctl) and clear browser cache on Linux browsers.
  • Provide Linux-specific examples alongside Windows steps, especially for service management and machine restart procedures.
  • Clarify whether the appliance is exclusively Windows-based or if Linux deployments are supported, and update prerequisites and steps accordingly.
  • Mention Linux tools and patterns (e.g., systemctl, service, Linux browser cache management) where appropriate.
  • Add screenshots or CLI examples for Linux environments if applicable.
GitHub Create Pull Request
Site Recovery Configure Mobility Service Proxy Settings for Azure to Azure Disaster Recovery | Microsoft Docs ...-recovery/configure-mobility-service-proxy-settings.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation demonstrates a Windows bias by presenting Windows-specific instructions and tools (such as Internet Explorer settings and psexec usage) before Linux equivalents. Windows configuration steps are described in greater detail and are listed first, while Linux instructions are brief and lack comparable detail. The use of Windows tools (Internet Explorer, psexec) is highlighted, with no mention of Linux alternatives or equivalent user context setup methods.
Recommendations
  • Present Linux and Windows instructions in parallel, giving equal detail and prominence to both.
  • Include Linux-specific methods for setting proxy settings for system services (e.g., using sudo, systemd service environment overrides, or user context switching).
  • Avoid referencing Windows-only tools (like Internet Explorer and psexec) without providing Linux equivalents or alternatives.
  • Where file paths or configuration steps differ, provide side-by-side examples for both platforms.
  • Add troubleshooting and verification steps for Linux environments, similar to those described for Windows.
GitHub Create Pull Request
Site Recovery Delete an Azure Site Recovery vault ...-docs/blob/main/articles/site-recovery/delete-vault.md
High Priority View Details →
Scanned: 2026-01-11 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 by providing only PowerShell examples for vault deletion, referencing Windows-centric tools (Hyper-V, System Center VMM), and omitting equivalent Linux CLI (Azure CLI) instructions. The use of PowerShell is presented as the default method for force deletion, with no mention of cross-platform alternatives. Additionally, Windows scenarios (Hyper-V, VMM) are described in detail, while Linux-based approaches are not addressed.
Recommendations
  • Add Azure CLI examples for vault deletion to provide a cross-platform alternative to PowerShell.
  • Explicitly mention that PowerShell instructions are Windows-centric and provide guidance for Linux/macOS users.
  • Include references to Linux tools and workflows where applicable, such as managing vaults via Azure CLI or REST API.
  • Balance scenario coverage by including steps for Linux-based environments or clarify platform applicability for each scenario.
GitHub Create Pull Request
Site Recovery Exclude disks from replication with Azure Site Recovery ...in/articles/site-recovery/exclude-disks-replication.md
High Priority View Details →
Scanned: 2026-01-11 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 Windows bias by providing examples and walkthroughs exclusively for Windows VMs, particularly focusing on SQL Server and paging file scenarios. All disk exclusion, failover, and recovery steps use Windows-specific tools (diskmgmt.msc, service console, drive letters like C:\, D:\, etc.), and there are no Linux VM examples or instructions. Windows terminology and screenshots are used throughout, and Linux-specific disk management or failover considerations are not addressed.
Recommendations
  • Add equivalent examples for Linux VMs, such as excluding disks containing swap partitions or temp directories (e.g., /swap, /tmp).
  • Include instructions for disk management and failover on Linux, using Linux tools (e.g., lsblk, parted, mount) and Linux file system paths.
  • Provide SQL Server on Linux scenarios, or examples for other common Linux workloads (e.g., MySQL, PostgreSQL) and how to handle excluded disks during failover.
  • Mention differences in drive letter assignment and disk mounting between Windows and Linux, and clarify how Azure assigns device names (e.g., /dev/sdX) for Linux VMs after failover.
  • Add screenshots or CLI examples for Linux disk management and service control (e.g., systemctl for database services).
GitHub Create Pull Request
Site Recovery New feature updates in Azure Site Recovery ...in/articles/site-recovery/feature-updates-whats-new.md
High Priority View Details →
Scanned: 2026-01-11 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 noticeable Windows bias. Windows Server Failover Clusters (WSFC) are mentioned as the primary use case for shared disk support, with explicit OS support listed only for Windows Server. PowerShell support is highlighted, but there is no mention of equivalent Linux tools or commands. Windows OS features (Trusted Launch, shared disk, failover clustering) are described in detail and appear before Linux equivalents, which are only briefly mentioned (e.g., Trusted Launch for Linux in preview, with Windows already GA). No Linux-specific examples, tools, or patterns are provided for disaster recovery scenarios.
Recommendations
  • Include Linux-specific examples and scenarios for shared disk and failover clustering (e.g., support for Pacemaker, Corosync, or other Linux clustering solutions).
  • Provide parity in tooling by mentioning and giving examples for Linux command-line tools (such as Bash scripts, Azure CLI, or Ansible) alongside PowerShell.
  • Explicitly list supported Linux distributions and versions where OS support is discussed.
  • Ensure that feature announcements and documentation sections present Windows and Linux support together, rather than Windows first.
  • Add troubleshooting and monitoring guidance for Linux workloads, including integration with Linux-native monitoring tools.
GitHub Create Pull Request
Site Recovery Deploy Azure Site Recovery Replication Appliance - Modernized ...tps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/deploy-vmware-azure-replication-appliance-modernized.md
High Priority View Details →
Scanned: 2026-01-11 00:00
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 Windows bias in several areas. PowerShell is presented as the only command-line method for appliance setup, with no equivalent Linux shell or cross-platform scripting examples. Registry and group policy checks are exclusively Windows-specific, and the troubleshooting/configuration steps reference Windows tools and patterns (e.g., registry keys, group policies, PowerShell execution policies). Linux is only mentioned in the context of credential requirements for source VMs, not for appliance deployment or management. There are no bash, shell, or Linux-native deployment instructions, and Windows-centric terminology and tooling are used throughout.
Recommendations
  • Provide Linux-based deployment instructions for the replication appliance, including bash or shell script equivalents to the PowerShell setup.
  • Include examples for Linux-based management and troubleshooting, such as checking prerequisites, proxy configuration, and agent installation.
  • Reference Linux system policies and configuration files (e.g., systemd, sudoers, firewall rules) alongside Windows registry/group policy checks.
  • Clarify platform requirements and explicitly state if the appliance must run on Windows, or provide guidance for Linux-based alternatives if supported.
  • Ensure parity in examples and screenshots for both Windows and Linux environments where applicable.
GitHub Create Pull Request
Site Recovery About failover and failback in Azure Site Recovery - Modernized ...site-recovery/failover-failback-overview-modernized.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a Windows bias in several ways. In the 'Connect to Azure after failover' section, Windows VM instructions are listed before Linux, and Windows-specific tools (such as Windows Firewall, RDP, and SAN policy) are mentioned in detail, while Linux instructions are brief and lack equivalent depth (e.g., no mention of Linux firewall configuration tools or troubleshooting steps). There are multiple notes and troubleshooting tips specific to Windows (e.g., boot time on Windows Server 2012, Windows Update issues), but similar Linux-specific guidance is missing. Additionally, references to VMware tools disabling are only contextualized for Windows VMs.
Recommendations
  • Alternate the order of Windows and Linux instructions, or present them in parallel to avoid Windows-first presentation.
  • Expand Linux VM connection instructions to include details on configuring common Linux firewalls (e.g., ufw, firewalld, iptables), troubleshooting SSH connectivity, and handling SELinux/AppArmor.
  • Provide Linux-specific troubleshooting notes similar to those given for Windows (e.g., what to check if SSH fails after failover, handling pending package updates).
  • Mention Linux equivalents for Windows tools and policies (e.g., SAN policy, boot diagnostics, update management).
  • Include references to Linux-specific documentation or community resources for failover/failback scenarios.
GitHub Create Pull Request
Site Recovery Protect a file server by using Azure Site Recovery ...rticles/site-recovery/file-server-disaster-recovery.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation demonstrates a clear bias toward Windows environments. It exclusively references Windows-centric technologies such as DFSR and Active Directory, and all step-by-step examples and instructions are tailored for Windows servers. There are no Linux-specific examples or guidance, and Windows tools and patterns are mentioned first and exclusively throughout the document. Azure File Sync is described primarily in the context of Windows servers, with only passing mention that Azure file shares can be mounted by Linux or macOS clients.
Recommendations
  • Add explicit guidance and examples for protecting Linux-based file servers using Azure Site Recovery, including step-by-step instructions.
  • Include Linux-specific disaster recovery scenarios, such as using rsync, NFS, or native Linux file replication tools, and how these integrate with Azure Site Recovery.
  • Provide parity in instructions for mounting Azure file shares on Linux (e.g., using SMB or NFS), including sample scripts and troubleshooting tips.
  • Clarify which features and recommendations apply to Linux environments and highlight any limitations or differences.
  • Where Windows tools (DFSR, Active Directory) are referenced, offer Linux equivalents or alternatives (e.g., Samba, LDAP, GlusterFS) and describe how to use them with Azure Site Recovery.
GitHub Create Pull Request
Site Recovery Enable replication for on-premises machines with private endpoints ...https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/hybrid-how-to-enable-replication-private-endpoints.md
High Priority View Details →
Scanned: 2026-01-11 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 listing URLs and domains that are predominantly Microsoft/Windows-centric (e.g., *.windows.net, *.microsoft.com), referencing Azure PowerShell as the only CLI example for creating private endpoints, and omitting Linux-specific or cross-platform CLI instructions (such as Azure CLI or Bash). There are no examples or guidance for Linux administrators, and the documentation assumes familiarity with Windows tools and patterns throughout.
Recommendations
  • Provide Azure CLI (az) examples alongside or before PowerShell instructions for creating and managing private endpoints.
  • Explicitly mention Linux support and provide step-by-step instructions for Linux environments, including relevant screenshots and terminal commands.
  • Include references to Linux-compatible tools and workflows (e.g., Bash, SSH, Linux package managers) when discussing prerequisites and setup steps.
  • Balance the order of presentation so that Windows and Linux approaches are given equal prominence.
  • Add troubleshooting and caveats specific to Linux environments (e.g., SELinux, iptables, DNS configuration differences).
GitHub Create Pull Request
Site Recovery Replicate Azure virtual machines running in a proximity placement group ...tps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/how-to-enable-replication-proximity-placement-groups.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page exhibits a strong Windows bias, primarily through the exclusive use of PowerShell for all CLI examples, reliance on Windows-centric tools and patterns, and the absence of Linux CLI equivalents (such as Bash or Azure CLI). Windows/PowerShell tooling is presented as the default for scripting and automation, with no parity for Linux users. Additionally, proximity placement group links and references often point to Windows-specific documentation, and the PowerShell module is assumed as the standard interface for automation tasks.
Recommendations
  • Provide equivalent Azure CLI (az) examples for all PowerShell commands, ensuring Linux users can follow along without needing PowerShell.
  • Include Bash shell scripting examples where appropriate, especially for automation tasks.
  • Reference both Windows and Linux documentation for proximity placement groups and related Azure features.
  • Explicitly mention Linux support and requirements in prerequisites and setup sections.
  • Add guidance for installing and using Azure CLI on Linux, and clarify when PowerShell is required versus when Azure CLI can be used.
  • Ensure screenshots and UI references are platform-neutral or provide both Windows and Linux variants where differences exist.
GitHub Create Pull Request
Site Recovery Configure on-premise disks for Azure through Hydration .../blob/main/articles/site-recovery/hydration-process.md
High Priority View Details →
Scanned: 2026-01-11 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 demonstrates Windows bias by presenting Windows configuration steps and examples before Linux, providing detailed PowerShell and command prompt instructions and screenshots for Windows but omitting equivalent Linux shell examples and screenshots. Windows-specific tools (diskpart, PowerShell) are highlighted, while Linux steps are more generic and lack concrete command-line walkthroughs for common tasks (e.g., DHCP configuration, agent installation verification). Troubleshooting links also prioritize Windows VM allocation failures before Linux.
Recommendations
  • Provide Linux shell command examples and screenshots for manual steps (e.g., checking DHCP configuration, verifying agent installation, mounting partitions).
  • Present Windows and Linux instructions in parallel or side-by-side tabs, ensuring equal detail and visibility.
  • Include troubleshooting links and examples for Linux VM allocation failures and other Linux-specific issues.
  • Reference Linux tools and utilities (e.g., systemctl, nmcli, ip, dhclient) where appropriate, not just Windows tools.
  • Ensure that manual preparation steps for both OS types are equally comprehensive and actionable.
GitHub Create Pull Request
Site Recovery Monitoring churn patterns on virtual machines ...b/main/articles/site-recovery/monitoring-high-churn.md
High Priority View Details →
Scanned: 2026-01-11 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 demonstrates Windows bias by presenting Windows-specific tools (Resource Monitor, Performance Monitor) in detail, with step-by-step instructions and screenshots, before mentioning Linux equivalents. The Linux section is brief, listing only iotop and iostat without detailed usage, examples, or screenshots. Windows tools are described more thoroughly, and the documentation structure prioritizes Windows content over Linux.
Recommendations
  • Provide step-by-step instructions for Linux tools (iotop, iostat), including example commands and output interpretation.
  • Include screenshots of Linux tools in use, similar to the Windows section.
  • Mention additional Linux monitoring tools (e.g., atop, dstat, sar) to match the breadth of Windows coverage.
  • Ensure the order of presentation is balanced, or alternate between Windows and Linux examples.
  • Add links to official documentation or tutorials for Linux tools, as done for Windows tools.
GitHub Create Pull Request
Site Recovery Hyper-V disaster recovery architecture in Azure Site Recovery ...n/articles/site-recovery/hyper-v-azure-architecture.md
High Priority View Details →
Scanned: 2026-01-11 00:00
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 related Microsoft tools (System Center VMM). All examples, architectural descriptions, and process explanations are tailored exclusively to Windows-based virtualization and management tools. There are no references to Linux-based hypervisors (such as KVM, Xen, or VMware ESXi), nor are there examples or guidance for disaster recovery involving Linux VMs or non-Windows platforms. Windows terminology and tools (e.g., Hyper-V Replica, VMM, .hrl files, Windows-specific URLs) are used throughout, with no mention of Linux equivalents or cross-platform considerations.
Recommendations
  • Add a section or cross-reference for disaster recovery architectures involving Linux-based hypervisors (e.g., KVM, Xen, VMware ESXi) and their integration with Azure Site Recovery.
  • Provide examples and process explanations for replicating and recovering Linux VMs, including any differences in agent installation, replication mechanisms, and failover/failback procedures.
  • Include parity in tooling references, such as mentioning Linux command-line tools or management interfaces where relevant.
  • Clarify in the introduction that the scope is limited to Hyper-V/Windows environments, and provide links to documentation for Linux or other platforms if available.
  • Where possible, use neutral terminology (e.g., 'on-premises virtualization hosts') and specify when instructions are Windows-specific.
GitHub Create Pull Request
← Previous Page 3 of 35 Next →