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 351-375 of 864 flagged pages
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/hyper-v-azure-troubleshoot.md ...n/articles/site-recovery/hyper-v-azure-troubleshoot.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation page demonstrates a strong Windows bias. All troubleshooting steps, examples, and tool references are centered around Windows environments, specifically Hyper-V, Windows Server, and related Microsoft tools (Event Viewer, PowerShell, VMM, etc.). Linux is mentioned only once, with no concrete troubleshooting steps or examples provided for Linux-based VMs. All commands and UI instructions are for Windows tools, and PowerShell is used exclusively for scripting examples.
Recommendations
  • Add troubleshooting steps and examples for Linux-based VMs, including common issues and log locations relevant to Linux guests.
  • Provide parity in command-line examples, such as including Bash or shell commands for Linux environments where applicable.
  • Mention and explain Linux equivalents for monitoring, logging, and service management (e.g., systemd, journalctl, /var/log, etc.).
  • Clarify which steps are Windows-specific and which are applicable to Linux, and reorganize sections to avoid presenting Windows-first as the default.
  • Include references to Linux documentation and tools for Azure Site Recovery and Hyper-V integration on Linux guests.
  • Ensure that any requirements or prerequisites sections explicitly address Linux compatibility and configuration.
GitHub Create Pull Request
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/failover-failback-overview-modernized.md ...site-recovery/failover-failback-overview-modernized.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation exhibits a Windows bias in several ways. Windows VM instructions and troubleshooting steps are presented first and in greater detail, with explicit references to Windows Firewall, RDP, SAN policy, and Windows Update. Linux VM guidance is comparatively brief and lacks equivalent detail (e.g., no mention of SELinux, systemd, or Linux-specific troubleshooting). Windows-specific tools and concepts (Windows Firewall, RDP, SAN policy) are mentioned without Linux equivalents. Troubleshooting links and notes are focused on Windows scenarios, and there are no PowerShell or CLI examples for Linux. The VMware failover section disables VMware tools only for Windows VMs, with no Linux-specific notes.
Recommendations
  • Provide Linux instructions with equal detail, including firewall configuration (e.g., iptables, firewalld, ufw), SSH troubleshooting, and SELinux/AppArmor considerations.
  • Include Linux-specific troubleshooting links and guidance, similar to the Windows RDP troubleshooting resources.
  • Mention Linux boot diagnostics and common issues (e.g., fstab, LVM, systemd services) in failover scenarios.
  • Present Linux and Windows instructions in parallel, rather than listing Windows first.
  • Add CLI and scripting examples for Linux environments (e.g., Bash commands for network/firewall setup, systemctl usage).
  • Reference Linux update/patching considerations during failover, similar to Windows Update notes.
  • Clarify any differences in failover/failback processes for Linux VMs, especially regarding agent registration and post-failover steps.
GitHub Create Pull Request
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/feature-updates-whats-new.md ...in/articles/site-recovery/feature-updates-whats-new.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation page exhibits a Windows bias in several areas: Windows Server Failover Clusters (WSFC) are highlighted as the primary use case for shared disk support, with explicit OS support limited to Windows Server. PowerShell support is mentioned as a salient feature, but no equivalent Linux automation or scripting options are referenced. In multiple sections, Windows OS features (such as Trusted Launch VM support) are announced as generally available before Linux equivalents, which are only in preview. There are no examples or explicit mentions of Linux-based clustering or automation tools, and the documentation lacks parity in describing Linux scenarios or tools.
Recommendations
  • Include Linux-based clustering solutions (e.g., Pacemaker, Corosync) in shared disk protection scenarios and document their support status.
  • Provide Bash, CLI, or Ansible examples alongside PowerShell for automation and scripting tasks.
  • Ensure feature announcements and documentation equally highlight Linux support and availability, not just Windows.
  • Add explicit OS support matrices and examples for both Windows and Linux where relevant.
  • Reference Linux monitoring and management tools where Azure Monitor or other integrations are discussed.
GitHub Create Pull Request
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/physical-azure-set-up-source.md ...articles/site-recovery/physical-azure-set-up-source.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates Windows bias by referencing Windows-specific requirements (such as .NET Framework and TLS settings), linking to Windows time service documentation, and omitting Linux-specific setup instructions or examples. All examples and troubleshooting steps are focused on Windows environments, with no mention of Linux commands, tools, or equivalent configuration steps.
Recommendations
  • Add explicit instructions and examples for setting up the configuration server on Linux, including supported distributions and required dependencies.
  • Provide Linux equivalents for system prerequisites, such as time synchronization (e.g., using ntpd or systemd-timesyncd), and clarify how to check and configure TLS settings on Linux.
  • Include Linux command-line examples for running the Unified Setup and registering the configuration server.
  • Reference Linux documentation and tools alongside Windows ones, ensuring parity in troubleshooting and setup guidance.
GitHub Create Pull Request
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/site-recovery-dynamicsax.md ...ain/articles/site-recovery/site-recovery-dynamicsax.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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 steps assume Windows-based infrastructure, with no mention of Linux equivalents or guidance for Linux-based workloads. Windows tools and patterns (e.g., Active Directory, Windows VMs, SQL Server) are referenced exclusively, and there are no Linux or cross-platform alternatives provided.
Recommendations
  • Explicitly state that the guidance is for Windows-only environments if Linux is unsupported, or clarify platform limitations.
  • If Linux-based workloads can be protected with Azure Site Recovery, add parallel examples and instructions for Linux VMs, including networking, failover, and recovery plan creation.
  • Include references to Linux-compatible disaster recovery tools and patterns (e.g., LDAP for directory services, PostgreSQL/MySQL for databases) where applicable.
  • Provide guidance or links for protecting non-Windows workloads with Azure Site Recovery, if supported.
  • Add a comparison table or section outlining differences and considerations for Linux vs. Windows disaster recovery with Azure Site Recovery.
GitHub Create Pull Request
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/vmware-azure-exclude-disk.md ...in/articles/site-recovery/vmware-azure-exclude-disk.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates Windows bias by providing more detailed information about Windows failback behavior before Linux, referencing Windows disks and their limitations, and omitting concrete Linux-specific examples or tools. The failback section describes Windows behavior first and in more detail, while Linux is mentioned second and with less explanation. There are no Linux command-line or tool examples, and the documentation does not provide parity in troubleshooting or automation guidance for Linux environments.
Recommendations
  • Present Windows and Linux failback behaviors with equal detail and in parallel, rather than describing Windows first.
  • Include Linux-specific examples, such as how to manually create disks on Linux VMs in Azure, or automate this process using Linux tools/scripts.
  • Reference Linux tools (e.g., shell scripts, cloud-init) for disk creation and automation, not just Azure Automation.
  • Provide troubleshooting steps and best practices for Linux environments, similar to those given for Windows.
  • Ensure screenshots and UI instructions are applicable to both Windows and Linux VMs, or clarify any differences.
GitHub Create Pull Request
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/region-move-cross-geos.md .../main/articles/site-recovery/region-move-cross-geos.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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 in several areas. Windows-specific instructions (such as registry edits and CLI commands) are provided in detail, while Linux instructions are minimal and lack equivalent examples. Windows tools and patterns (e.g., registry editing, use of REG CLI) are mentioned explicitly, with Linux alternatives only briefly referenced (e.g., 'the account should be root'), and no Linux command-line examples or troubleshooting steps are given. The order of presentation also places Windows instructions before Linux, reinforcing the bias.
Recommendations
  • Provide equivalent Linux command-line examples for steps such as Mobility service installation and account preparation.
  • Include troubleshooting steps and configuration details for Linux systems, similar to the registry and CLI instructions given for Windows.
  • Present Windows and Linux instructions in parallel or clearly separated sections to ensure parity and clarity.
  • Reference Linux-specific documentation and tools where appropriate (e.g., SELinux, systemd, sudoers configuration).
  • Ensure that any prerequisites or permissions checks are described for both Windows and Linux environments.
GitHub Create Pull Request
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/vmware-azure-common-questions.md ...rticles/site-recovery/vmware-azure-common-questions.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits a moderate Windows bias. Windows-specific tools, paths, and instructions (e.g., PowerShell, C:\ paths, Configuration Manager, MySQL installer location) are mentioned first or exclusively in several places. PowerShell is referenced as the primary automation/scripting method, with REST API and Azure SDK mentioned but no Linux shell or Ansible examples. Manual installation instructions and examples often use Windows terminology and tools, with Linux equivalents provided only in a few cases and typically after the Windows instructions. There is a lack of parity in scripting and automation examples for Linux users, and Windows-centric deployment tools (e.g., Configuration Manager) are referenced without Linux alternatives.
Recommendations
  • Provide Linux shell (bash) and/or Ansible examples alongside PowerShell for automation and scripting tasks.
  • List Linux instructions and paths before or alongside Windows instructions, not only after.
  • Reference Linux-native deployment tools (e.g., cloud-init, Ansible, Puppet) where Configuration Manager is mentioned.
  • Ensure all manual installation steps include both Windows and Linux paths and commands.
  • Include Linux-specific troubleshooting and upgrade instructions, not just Windows-centric ones.
  • Add explicit examples for Linux users in sections about scripting, automation, and agent installation.
GitHub Create Pull Request
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/transport-layer-security.md ...ain/articles/site-recovery/transport-layer-security.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exclusively discusses enabling and verifying TLS 1.2 on Windows operating systems, with detailed instructions for Windows registry changes and references to Windows KB articles. There are no examples, instructions, or mentions of Linux systems, tools, or configuration patterns, despite Azure Site Recovery potentially being used in heterogeneous environments.
Recommendations
  • Add equivalent instructions for enabling and verifying TLS 1.2 on popular Linux distributions (e.g., Ubuntu, CentOS), including configuration of OpenSSL, stunnel, or other relevant components.
  • Provide Linux-specific troubleshooting steps for TLS connectivity issues in Azure Site Recovery.
  • Include references to Linux documentation and tools (such as openssl, update-ca-certificates, or systemd service configuration) alongside Windows registry and KB article references.
  • Ensure that examples and guidance are presented for both Windows and Linux platforms, or clarify platform scope at the beginning of the document.
GitHub Create Pull Request
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/site-recovery-sap.md .../blob/main/articles/site-recovery/site-recovery-sap.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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 in its SAP NetWeaver disaster recovery guidance. The reference architecture is exclusively described as running on Windows, with clustering solutions and high availability recommendations focused on Windows Server Failover Cluster, Storage Spaces Direct, and SIOS DataKeeper. There is no mention of Linux-based SAP deployments, nor are Linux clustering or high availability tools (e.g., Pacemaker, Corosync, NFS) discussed. All examples and recommendations assume a Windows environment, omitting Linux-specific guidance and parity.
Recommendations
  • Include explicit guidance and examples for SAP NetWeaver deployments on Linux, which are common in enterprise environments.
  • Describe Linux-based clustering and high availability solutions, such as Pacemaker/Corosync, NFS, and native Linux failover patterns.
  • Provide parity in disaster recovery steps and scripts for Linux VMs, including automation and post-failover operations.
  • Add diagrams and reference architectures for SAP NetWeaver on Linux in Azure.
  • Mention supported Linux distributions and their compatibility with Azure Site Recovery.
  • Ensure recommendations for database and directory services include Linux equivalents (e.g., Linux-based DNS, LDAP, or database servers).
GitHub Create Pull Request
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/unregister-vmm-server-script.md ...articles/site-recovery/unregister-vmm-server-script.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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 scripts and instructions that rely on Windows-specific tools (e.g., registry paths, Windows services, Windows clustering, and SCVMM). There are no Linux or cross-platform examples, and all operational patterns and troubleshooting steps are described exclusively in the context of Windows environments.
Recommendations
  • Add equivalent Linux instructions or clarify that the script and process are only supported on Windows.
  • If possible, provide Bash or Python examples for similar cleanup operations on Linux-based virtualization managers.
  • Explicitly state platform requirements and limitations at the beginning of the documentation.
  • Reference Linux tools (e.g., systemctl, Linux clustering solutions) where applicable, or provide guidance for Linux administrators.
  • Consider including a table or section comparing Windows and Linux approaches to VMM cleanup and unregistration.
GitHub Create Pull Request
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/vmware-physical-manage-mobility-service.md ...te-recovery/vmware-physical-manage-mobility-service.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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 ways: PowerShell is the only scripting example provided for agent updates, Windows uninstall instructions are more detailed and presented before Linux, and Windows-specific tools (Control Panel, MSIExec, VSS provider) are described with no Linux equivalents or parity in detail. Linux instructions are present but less comprehensive, and there are no Linux scripting or automation examples for agent updates.
Recommendations
  • Provide equivalent Linux automation examples for agent updates, such as bash scripts or CLI commands.
  • Present Windows and Linux instructions in parallel sections or with equal prominence.
  • Include Linux-specific troubleshooting and management tools where Windows tools (e.g., Control Panel, MSIExec, VSS provider scripts) are mentioned.
  • Add more detail to Linux uninstall and update procedures, matching the step-by-step approach used for Windows.
  • Ensure that examples and screenshots are balanced between Windows and Linux environments.
GitHub Create Pull Request
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/vmware-azure-tutorial-prepare-on-premises.md ...-recovery/vmware-azure-tutorial-prepare-on-premises.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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 in several areas. Windows instructions and tools (such as registry edits and Windows Firewall) are described in greater detail and appear before Linux equivalents. The Windows RDP connection steps are more elaborate, referencing specific Windows features and troubleshooting resources, while Linux SSH instructions are brief and lack comparable troubleshooting guidance. There is also a lack of Linux-specific examples for advanced scenarios (e.g., handling SSH keys, SELinux, or common Linux firewall tools).
Recommendations
  • Provide Linux instructions with equal detail, including troubleshooting steps and references to common Linux tools (e.g., iptables, firewalld, SELinux).
  • Add examples for Linux account preparation, such as using sudoers or SSH key-based authentication.
  • Include Linux-specific guidance for post-failover connectivity, such as checking SSH service status, configuring network security groups, and handling common Linux boot issues.
  • Present Windows and Linux instructions in parallel, rather than listing Windows first, to avoid implicit prioritization.
  • Reference Linux documentation and community troubleshooting resources similar to those provided for Windows.
GitHub Create Pull Request
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/azure-to-azure-common-questions.md ...icles/site-recovery/azure-to-azure-common-questions.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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 areas. Windows-specific features (such as Volume Shadow Copy Service for app-consistent snapshots) are described in detail, while Linux equivalents are only briefly mentioned or omitted. PowerShell is frequently referenced as the primary automation method, with no mention of Bash, CLI, or Linux-native scripting. Windows tools and terminology (e.g., WSFC, ADE for Windows, SQL Server/SQL VM extensions) are discussed extensively, while Linux scenarios are less detailed or unsupported (e.g., shared disks). Examples and instructions often default to Windows or PowerShell, with Linux alternatives missing or relegated to secondary status.
Recommendations
  • Provide Linux CLI (az CLI) and Bash script examples alongside PowerShell instructions for all automation tasks.
  • Explicitly document Linux support and limitations for features such as disk encryption, shared disks, and app-consistent snapshots, with parity in detail to Windows sections.
  • Include references to Linux-native tools and patterns (e.g., cloud-init, systemd, LVM) where relevant.
  • Ensure that Linux scenarios are described with equal prominence and clarity as Windows scenarios, including troubleshooting and configuration steps.
  • Where features are unsupported for Linux, clearly state the roadmap or alternatives for Linux users.
GitHub Create Pull Request
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/avs-tutorial-replication.md ...ain/articles/site-recovery/avs-tutorial-replication.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits Windows bias by focusing on Windows Server as the default OS for the configuration server VM, requiring Windows activation, and providing step-by-step instructions for Windows installation and credential setup. Linux is only briefly mentioned as an alternative for Mobility Service credentials, with no Linux-specific setup or examples. The process server and configuration server setup, registration, and management are described exclusively in terms of Windows tools and workflows, with no parity for Linux environments.
Recommendations
  • Provide explicit instructions and examples for setting up the configuration server VM with a Linux OS, if supported.
  • Include Linux-specific steps for registration, credential setup, and Mobility Service installation.
  • Clarify OS requirements and alternatives early in the documentation, listing both Windows and Linux options side by side.
  • Offer troubleshooting and management guidance for Linux-based configuration/process servers.
  • Ensure that any required tools or scripts (e.g., for MySQL installation, agent deployment) have Linux-compatible versions and document their usage.
GitHub Create Pull Request
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/avs-tutorial-prepare-avs.md ...ain/articles/site-recovery/avs-tutorial-prepare-avs.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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 in several ways: Windows instructions (such as registry edits and firewall settings) are presented first and in greater detail, with explicit references to Windows-specific tools and patterns (e.g., Windows Firewall, RDP, registry keys). Linux instructions are brief, lack detailed steps or troubleshooting guidance, and do not mention equivalent Linux tools or commands. Troubleshooting and connectivity sections focus on Windows scenarios and resources, with less parity for Linux users.
Recommendations
  • Provide Linux examples and instructions with equal detail, including specific commands for configuring SSH, firewall (e.g., iptables, firewalld, ufw), and user permissions.
  • Include troubleshooting steps and links for Linux connectivity issues after failover, similar to the Windows RDP troubleshooting section.
  • Mention Linux tools and configuration files (e.g., /etc/ssh/sshd_config, SELinux/AppArmor settings) where appropriate.
  • Present Windows and Linux instructions side-by-side or in parallel sections to avoid implicit prioritization of Windows.
  • Ensure that all steps (such as preparing accounts, configuring firewalls, and checking diagnostics) have Linux equivalents and are described with actionable detail.
GitHub Create Pull Request
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/avs-tutorial-failback.md ...b/main/articles/site-recovery/avs-tutorial-failback.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates Windows bias by specifically mentioning Windows VMs and their interaction with VMware tools during failover/failback, while omitting any reference to Linux VMs or their equivalent processes. There are no Linux-specific instructions, notes, or troubleshooting guidance. The only VM OS explicitly referenced is Windows, and the behavior of VMware tools is described solely for Windows VMs.
Recommendations
  • Add equivalent notes and instructions for Linux VMs, including how VMware tools behave during failover/failback for Linux guests.
  • Provide troubleshooting steps or caveats for Linux VMs, such as agent registration, service dependencies, or differences in shutdown/startup behavior.
  • Ensure examples and notes are presented for both Windows and Linux VMs, or clarify when instructions apply to all OS types.
  • Mention any Linux-specific requirements or considerations for Azure Site Recovery and Azure VMware Solution failback processes.
GitHub Create Pull Request
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/avs-tutorial-failover.md ...b/main/articles/site-recovery/avs-tutorial-failover.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing Windows-specific concepts and links before Linux equivalents, such as linking to Windows availability sets and connection instructions. There is a lack of explicit Linux examples or instructions, and Windows tools/patterns (e.g., RDP, Windows VM connection guides) are mentioned or linked before or instead of Linux alternatives.
Recommendations
  • Provide explicit Linux VM connection instructions and links (e.g., SSH guides for Linux VMs) alongside or before Windows RDP instructions.
  • Include references and links to Linux-specific documentation (such as Linux availability sets, if relevant) in parallel with Windows links.
  • Add examples or notes for common Linux failover scenarios, including troubleshooting steps specific to Linux VMs.
  • Ensure that any referenced guides or tutorials include both Windows and Linux VM management steps, or clearly indicate differences.
  • Review all links to ensure parity between Windows and Linux documentation, avoiding Windows-first ordering unless justified by usage statistics.
GitHub Create Pull Request
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/azure-to-azure-replicate-after-migration.md ...e-recovery/azure-to-azure-replicate-after-migration.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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 presenting Windows instructions and validation steps before Linux equivalents, referencing Windows-specific tools and patterns (e.g., Control Panel, MSIExec), and providing more detailed validation steps for Windows (such as checking file properties) than for Linux. Linux instructions are less detailed and lack parity in troubleshooting and validation examples.
Recommendations
  • Present Linux and Windows instructions in parallel or alternate their order to avoid Windows-first bias.
  • Provide equally detailed validation steps for Linux, such as checking agent version and status using Linux commands.
  • Include Linux-specific troubleshooting links and examples, similar to those provided for Windows.
  • Reference Linux tools and patterns (e.g., package managers, systemctl) with the same prominence as Windows tools.
  • Ensure that all examples and instructions are available for both platforms, avoiding missing Linux equivalents.
GitHub Create Pull Request
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/azure-to-azure-how-to-enable-replication-s2d-vms.md ...ry/azure-to-azure-how-to-enable-replication-s2d-vms.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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 Windows environments, specifically referencing Windows Failover Clustering and Storage Spaces Direct (S2D), which are Windows-only technologies. All examples, terminology, and referenced tools are Windows-centric, with no mention of Linux equivalents or guidance for Linux-based clusters. There are no Linux examples, and the documentation assumes the use of Windows guest clusters and related Windows tools.
Recommendations
  • Add a section clarifying that Storage Spaces Direct and Windows Failover Clustering are Windows-only, and explicitly state whether Linux-based clusters are supported or not.
  • If Azure Site Recovery supports Linux-based clusters or similar high-availability setups, provide equivalent examples and guidance for Linux environments (e.g., using Pacemaker, DRBD, or other Linux clustering technologies).
  • Include links to documentation for disaster recovery of Linux VMs and clusters, if available.
  • Where possible, use neutral terminology (e.g., 'guest cluster') and provide parallel instructions for both Windows and Linux platforms.
  • Add a comparison table showing feature parity and limitations between Windows and Linux cluster disaster recovery in Azure.
GitHub Create Pull Request
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/azure-to-azure-how-to-enable-replication-cmk-disks.md ...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-08 00:53
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 in PowerShell, which is primarily used on Windows. There is no mention of Azure CLI, Bash, or Linux-specific workflows, and the documentation assumes use of Windows-centric tools.
Recommendations
  • Add equivalent Azure CLI and Bash examples for all PowerShell code snippets, especially for disk replication and management tasks.
  • Explicitly mention that the steps can be performed from Linux/macOS environments using Azure CLI, and provide guidance for those platforms.
  • Include a section comparing PowerShell and Azure CLI usage for cross-platform administrators.
  • Review screenshots and UI instructions to ensure they do not assume Windows-only environments (e.g., referencing Windows file paths or UI elements that differ on other platforms).
GitHub Create Pull Request
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/azure-to-azure-support-matrix.md ...rticles/site-recovery/azure-to-azure-support-matrix.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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 moderate Windows bias. Windows and PowerShell are consistently mentioned first or exclusively in deployment and configuration scenarios. Azure PowerShell is referenced repeatedly as the main automation tool, with no Linux CLI alternatives (Azure CLI is explicitly marked as unsupported). Windows-specific requirements (such as SSU/SHA-2 updates) are described in detail, while Linux instructions are less prominent and lack parity in example depth. There are no Linux shell or automation examples, and troubleshooting steps for Linux (e.g., password reset) are only described via the portal, not via command line.
Recommendations
  • Add Linux CLI (bash, Azure CLI) examples for all deployment and configuration steps, especially where PowerShell is referenced.
  • Where Azure PowerShell is suggested, clarify Linux alternatives or workarounds, or note if/when Azure CLI support is planned.
  • Present Windows and Linux instructions in parallel, rather than listing Windows first or exclusively.
  • Include troubleshooting and operational examples for Linux VMs using shell commands, not just portal steps.
  • Explicitly document any limitations or differences for Linux users, and provide guidance on how to achieve parity where possible.
GitHub Create Pull Request
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/deploy-vmware-azure-replication-appliance-modernized.md ...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-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation demonstrates a Windows bias in several ways: PowerShell is the only CLI method described for manual setup, with no Linux shell or cross-platform alternatives. Registry and group policy checks are exclusively Windows-centric, and all troubleshooting steps reference Windows tools and patterns. The order of presentation and examples assume a Windows environment, with Linux only mentioned as a target OS for credentials, not for appliance setup or management.
Recommendations
  • Provide equivalent Linux shell (bash) or cross-platform CLI instructions for appliance setup, not just PowerShell.
  • Include Linux-specific troubleshooting steps and configuration checks (e.g., systemd, SELinux, firewall, time sync) alongside Windows registry/group policy checks.
  • Explicitly state OS requirements and clarify if the appliance can be deployed on Linux-based VMs or only Windows.
  • Offer parity in examples and screenshots for Linux environments, not just Windows.
  • If PowerShell is required, explain why and offer alternatives or workarounds for Linux administrators.
GitHub Create Pull Request
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/azure-to-azure-troubleshoot-network-connectivity.md ...ry/azure-to-azure-troubleshoot-network-connectivity.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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 moderate Windows bias. Windows tools and patterns (such as Internet Explorer for proxy autodetection) are mentioned before their Linux equivalents. Proxy configuration instructions reference Windows paths and tools first, with Linux mentioned second. There are no command-line examples (e.g., PowerShell or Bash), but the troubleshooting steps and screenshots are oriented toward the Azure Portal, which is platform-neutral. However, the lack of explicit Linux-specific troubleshooting examples (such as checking DNS or NSG rules from a Linux VM) and the absence of Linux command-line instructions contribute to the bias.
Recommendations
  • Provide Linux-specific troubleshooting steps, such as using dig/nslookup for DNS checks or iptables/nftables for firewall diagnostics.
  • Include Bash command-line examples alongside any PowerShell or Windows command-line instructions.
  • When referencing proxy autodetection, mention Linux methods (such as environment variables or common desktop environments) before or alongside Windows methods.
  • Add screenshots or instructions for configuring network settings from a Linux VM perspective.
  • Ensure all file paths and configuration examples are given for both Windows and Linux, with equal prominence.
GitHub Create Pull Request
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/azure-to-azure-virtual-machine-errors.md ...site-recovery/azure-to-azure-virtual-machine-errors.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation demonstrates Windows bias in several ways: Windows instructions and links are consistently listed before Linux equivalents (e.g., disk initialization), and the only provided automation script for cleaning up stale Site Recovery configurations is a PowerShell (.ps1) script, with no mention of a Linux/bash alternative. This leaves Linux users without parity for key troubleshooting steps and automation.
Recommendations
  • Present Windows and Linux instructions side-by-side, or alternate which is listed first to avoid implicit prioritization.
  • Provide equivalent bash or Azure CLI scripts for Linux users, especially for tasks currently covered only by PowerShell scripts.
  • Explicitly mention Linux troubleshooting steps wherever automation or scripting is referenced, and link to Linux-specific resources.
  • Clarify whether provided scripts (e.g., Cleanup-Stale-ASR-Config-Azure-VM.ps1) can be run from Azure Cloud Shell (which supports both bash and PowerShell), and offer guidance for Linux users.
  • Audit all troubleshooting steps to ensure Linux users have clear, actionable instructions matching those for Windows.
GitHub Create Pull Request
← Previous Page 15 of 35 Next →