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 26-50 of 864 flagged pages
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-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First Missing Linux Example
Summary
The documentation is heavily focused on Windows environments, with all examples, tools, and troubleshooting steps referencing Windows Server, Windows-specific registry keys, and command-line utilities (e.g., NET SHARE, dcdiag, nltest, dnscmd). There are no examples or guidance for Linux-based Active Directory alternatives (such as Samba AD DC), nor for DNS servers running on Linux. All instructions assume the use of Windows Server for domain controllers and DNS, and Windows tools are referenced exclusively and first.
Recommendations
  • Add explicit guidance for Linux-based Active Directory alternatives (e.g., Samba AD DC), including replication and failover steps.
  • Include examples for DNS servers running on Linux (e.g., BIND, dnsmasq), with equivalent commands for zone creation and updates.
  • Where registry edits are described, provide Linux configuration file equivalents or note if the step is not applicable.
  • Clarify which steps are Windows-only and provide parity instructions for Linux/macOS environments where possible.
  • Add troubleshooting steps for Linux-based domain controllers and DNS servers, including relevant commands and logs.
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-13 00:00
Reviewed by: LLM Analysis
Issues: 5 bias types
Detected Bias Types
Windows Only Missing Linux Example 🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation is heavily biased towards Windows environments. All prerequisites, installation steps, and command-line examples assume Windows Server as the operating system, with no mention of Linux or macOS support. Windows-specific tools (e.g., PowerShell, reg.exe, cspsconfigtool.exe, Control Panel) are referenced exclusively, and all example commands are for Windows. There are no Linux equivalents, nor any guidance for non-Windows users, making the documentation inaccessible for those attempting to use Linux or macOS as the configuration server platform.
Recommendations
  • Clarify whether Linux/macOS are supported as configuration server platforms. If not, state this explicitly in prerequisites.
  • If Linux is supported, provide equivalent installation, registration, and management instructions for Linux (e.g., shell commands, systemd/service management, file paths).
  • Include Linux/macOS-specific troubleshooting steps and common issues.
  • Where PowerShell is used, offer Bash or shell alternatives for Linux.
  • Reference Linux tools (e.g., systemctl, cron, package managers) where appropriate.
  • If only Windows is supported, add a prominent note at the top of the documentation to prevent confusion for non-Windows users.
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-13 00:00
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 support, Linux clustering solutions, or examples relevant to Linux or macOS users.
Recommendations
  • Explicitly state whether Linux virtual machines and Linux clustering solutions (e.g., Pacemaker, Corosync) are supported or not.
  • If Linux is unsupported, clarify this in the documentation to prevent confusion.
  • If Linux support exists or is planned, provide equivalent examples, supported scenarios, and guidance for Linux users.
  • Include a comparison table or section for both Windows and Linux platforms, highlighting differences and parity.
  • Reference Linux documentation or migration guides where relevant.
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-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation for the Azure Site Recovery Deployment Planner is heavily Windows-centric. All instructions, prerequisites, and examples assume the use of Windows Server or Windows PC, with no mention of Linux or macOS support. Required dependencies (.NET Framework, Visual C++ Redistributable, Excel) are Windows-only, and there are no alternative instructions or examples for Linux or macOS users.
Recommendations
  • Explicitly state whether the tool can or cannot be run on Linux or macOS, and if not, provide rationale.
  • If possible, develop and document a cross-platform version of the Deployment Planner tool, or provide a containerized (Docker) version that can run on Linux.
  • Offer alternative instructions for report generation that do not require Excel on Windows (e.g., CSV output, web-based report viewer).
  • List prerequisites and examples for both Windows and Linux/macOS platforms, or clarify platform limitations early in the documentation.
  • Provide guidance for VMware administrators who use Linux or macOS as their primary workstation.
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-13 00:00
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 and guidance assume Windows-based infrastructure, with no mention of Linux or cross-platform alternatives for disaster recovery, replication, or failover. There are no Linux-specific instructions, tools, or considerations provided.
Recommendations
  • Explicitly state the Windows-only nature of Dynamics AX and its dependencies early in the document.
  • If any components (e.g., SQL Server, VMware VMs) can run on Linux, provide parallel instructions or note Linux support.
  • Include guidance or links for disaster recovery of Linux-based workloads with Azure Site Recovery for broader context.
  • Add a section clarifying limitations for non-Windows environments and suggest alternatives for Linux users.
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-13 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 notable Windows bias. It exclusively references Windows Server, Windows PowerShell cmdlets, and Windows-centric tools (e.g., DFSR, Central Administration GUI, Restore-SPEnterpriseSearchServiceApplication). There are no examples, instructions, or guidance for Linux-based SharePoint deployments or for using Linux tools. All scripting and automation references are Windows/PowerShell-centric, and the recovery steps assume Windows environments throughout.
Recommendations
  • Add explicit guidance for SharePoint deployments on Linux (if supported), or clarify Windows-only support.
  • Include equivalent scripting and automation examples for Linux (e.g., Bash, Python) where possible.
  • Mention Linux-compatible tools for file replication and backup (e.g., rsync, scp) alongside Windows tools like DFSR and AzCopy.
  • If SharePoint is Windows-only, state this clearly at the beginning to set expectations for non-Windows users.
  • Provide parity in example ordering, showing Linux/macOS approaches where relevant.
GitHub Create Pull Request
Site Recovery Set up SAP NetWeaver disaster recovery with Azure Site Recovery .../blob/main/articles/site-recovery/site-recovery-sap.md
High Priority View Details →
Scanned: 2026-01-13 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 in several key areas. The reference SAP architecture is described as running in a Windows environment, and clustering recommendations exclusively mention Windows Server Failover Cluster, SIOS DataKeeper, and Windows-specific features like Scale Out File Server and Storage Spaces Direct. There are no examples or guidance for Linux-based SAP deployments, nor are Linux clustering tools (such as Pacemaker or Corosync) mentioned. All operational examples and scripts are generic or Azure-focused, but the underlying infrastructure and high availability recommendations are Windows-centric.
Recommendations
  • Include equivalent guidance and examples for SAP NetWeaver deployments on Linux, which are common in enterprise environments.
  • Mention and provide instructions for Linux clustering solutions (e.g., Pacemaker, Corosync, NFS for /sapmnt) alongside Windows Server Failover Cluster.
  • Clarify whether Site Recovery supports Linux-based clusters and provide any required configuration steps.
  • Add diagrams and reference architectures for SAP NetWeaver on Linux.
  • Ensure that recommendations for high availability and disaster recovery cover both Windows and Linux scenarios equally.
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-13 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 is heavily biased towards Windows environments. All examples for generating VM lists use VMware PowerCLI (a Windows/PowerShell tool), and instructions reference Windows-specific concepts (Notepad, UNC paths, Excel, Control Panel). The deployment planner tool itself is a Windows executable (.exe), and report generation requires Microsoft Excel on Windows. There are no Linux/macOS alternatives or examples provided, and Windows tools and patterns are mentioned exclusively and first throughout.
Recommendations
  • Provide instructions and examples for generating VM lists using Linux/macOS tools (e.g., using VMware's Python SDK, govc, or shell scripts).
  • Clarify whether the ASRDeploymentPlanner.exe tool can run under Wine or Mono on Linux/macOS, or provide a cross-platform version.
  • Offer alternatives for viewing and editing output files (e.g., using LibreOffice for Excel files on Linux/macOS).
  • Include notes or sections for Linux/macOS users, such as how to handle file paths, text editing, and prerequisites.
  • If PowerCLI is required, mention how it can be installed and used on Linux/macOS (PowerShell Core is cross-platform, but PowerCLI support should be clarified).
GitHub Create Pull Request
Site Recovery Transport Layer Security in Azure Site Recovery ...ain/articles/site-recovery/transport-layer-security.md
High Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation exclusively addresses Windows environments, focusing on Windows registry changes, KB articles, and .NET Framework configuration for enabling TLS 1.2. There are no references to Linux or macOS systems, nor are there instructions or examples for enabling or verifying TLS on non-Windows platforms. All troubleshooting and configuration guidance is Windows-centric.
Recommendations
  • Add a section describing how TLS 1.2 is handled on Linux and macOS systems, including relevant configuration files (e.g., OpenSSL, system-wide TLS settings).
  • Provide verification steps for TLS 1.2 support on Linux/macOS, such as using openssl or curl.
  • Include troubleshooting guidance for non-Windows platforms, especially for common issues with TLS negotiation.
  • Reference cross-platform resources and clarify which instructions apply to which operating systems.
  • If Azure Site Recovery components are supported on Linux/macOS, explicitly document their TLS requirements and configuration steps.
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-13 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 Server Failover Clusters (WSFC) and does not mention or provide guidance for Linux-based clustering solutions (such as Pacemaker or Corosync). All examples, prerequisites, and process descriptions assume a Windows environment, with no parity for Linux users. Windows terminology and tools are referenced exclusively, and there are no Linux-specific instructions or alternatives.
Recommendations
  • Explicitly state whether Linux-based clusters (e.g., Pacemaker, Corosync) are supported or not.
  • If Linux clusters are supported, add equivalent instructions and examples for setting up disaster recovery with Azure Site Recovery for Linux clusters.
  • Provide a support matrix or comparison table showing which cluster types and operating systems are supported.
  • If only Windows clusters are supported, clarify this limitation early in the documentation to avoid confusion for Linux users.
  • Include references to Linux documentation or migration guides if relevant.
GitHub Create Pull Request
Site Recovery Upgrade Mobility Service and appliance components - Modernized ...s/site-recovery/upgrade-mobility-service-modernized.md
High Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias. Windows-specific tools (Registry Editor, .msi installers, command prompt, Windows file paths, and references to Windows Server) are mentioned exclusively or before Linux equivalents. Manual update instructions for appliance components are Windows-only, with no Linux/macOS examples or guidance. Linux instructions are provided only for the mobility agent update, and appear after the Windows section. Appliance management and troubleshooting are described entirely in Windows terms, leaving Linux users without clear guidance.
Recommendations
  • Add equivalent Linux/macOS instructions for appliance component updates, including command-line examples and file paths.
  • Provide guidance on managing appliance autoupdate settings on Linux (e.g., config files, systemd, etc.), not just Windows Registry.
  • Include Linux-first or parallel examples for manual update procedures, not just Windows-first ordering.
  • Clarify which steps are Windows-only and offer alternatives or workarounds for Linux/macOS users.
  • Reference Linux troubleshooting steps for appliance upgrade failures.
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-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation is heavily biased towards Windows, providing only PowerShell script examples and referencing Windows-specific tools (e.g., registry paths, Windows services, Windows Cluster service). There are no Linux or macOS equivalents, nor any guidance for non-Windows environments. The instructions and script are not portable to Linux/macOS, and the entire workflow assumes a Windows VMM server.
Recommendations
  • Explicitly state that the procedure is only applicable to Windows-based VMM servers.
  • If Linux/macOS support is possible, provide equivalent scripts or instructions for those platforms.
  • Add a note clarifying the lack of Linux/macOS support and suggest alternatives for non-Windows users.
  • Consider providing cross-platform management options if available, or link to relevant documentation for Linux/macOS users.
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-13 00:00
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). There are no Linux or macOS equivalents, examples, or troubleshooting steps provided, making the instructions only applicable to Windows environments.
Recommendations
  • Add Linux/macOS troubleshooting steps if the Site Recovery Provider supports those platforms.
  • Include equivalent commands for Linux (e.g., using terminal, tar for extraction, monitoring processes with ps/top).
  • Clarify platform support early in the documentation; if Windows-only, explicitly state this.
  • If cross-platform support is intended, provide parity in examples and tool references.
GitHub Create Pull Request
Site Recovery Deploy the configuration server in Azure Site Recovery ...e-recovery/vmware-azure-deploy-configuration-server.md
High Priority View Details →
Scanned: 2026-01-13 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 in several key areas. The configuration server is deployed as a Windows Server 2016 VM, and all setup instructions, including MySQL installation, reference Windows paths (e.g., C:\Temp\ASRSetup) and Windows administrative patterns. There are no Linux-based deployment options or examples, and Linux users are only mentioned in the context of providing root credentials for mobility service installation. The documentation assumes the use of Windows tools and environments throughout, with no parity for Linux/macOS users.
Recommendations
  • Explicitly state that the configuration server must run Windows, and clarify if Linux-based deployment is unsupported.
  • If possible, provide guidance or alternatives for Linux-based environments, such as running the configuration server on a Linux VM or container.
  • Include Linux/macOS equivalents for steps involving file paths, administrative actions, and MySQL installation.
  • Add troubleshooting and FAQ sections specifically for Linux/macOS users, or clarify limitations.
  • Ensure that any scripts, tools, or downloads are cross-platform or provide platform-specific instructions.
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-13 00:00
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 and installation patterns (e.g., .exe installers, Windows-style file paths, and command-line examples using Windows conventions). There are no Linux-specific instructions, examples, or references, despite the fact that VMware and physical server environments often include Linux hosts. This creates friction for Linux users attempting to deploy or manage process servers.
Recommendations
  • Provide explicit instructions and examples for installing and configuring the process server on Linux systems, including supported distributions.
  • Include Linux command-line examples (e.g., using .sh installers, Linux file paths, and relevant environment variables).
  • Clarify OS compatibility for the process server and note any limitations or requirements for Linux deployments.
  • If the process server is Windows-only, state this clearly and provide guidance for Linux environments (e.g., alternatives, workarounds, or architectural notes).
  • Present examples for both Windows and Linux side-by-side, or alternate which OS is shown first.
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-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates Windows bias by exclusively referencing Windows tools (PsExec, Internet Explorer, Windows services), providing only Windows command-line examples, and omitting Linux/macOS equivalents for proxy configuration and troubleshooting. No guidance is given for Linux-based vCenter environments or how to perform similar tasks without Windows-specific utilities.
Recommendations
  • Provide Linux/macOS equivalents for proxy configuration steps, such as using environment variables or system proxy settings.
  • Offer alternative commands and tools for Linux (e.g., using 'sudo -u' or 'su' for system user context, and configuring proxies via command line or desktop environments).
  • Include instructions for restarting relevant services on Linux (e.g., systemctl commands).
  • Avoid referencing Internet Explorer and PsExec exclusively; suggest cross-platform tools or clarify platform requirements.
  • Clearly indicate which steps are Windows-only and provide parity for Linux users where possible.
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 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation exclusively provides troubleshooting steps and examples for Windows environments, referencing Windows command prompt, Registry Editor, Task Manager, and Windows file paths. There are no instructions, examples, or tool references for Linux environments, indicating a strong Windows bias.
Recommendations
  • Add equivalent troubleshooting steps for Linux environments, including relevant commands and file paths.
  • Provide Linux shell (bash) command examples alongside Windows command prompt examples.
  • Reference Linux tools (such as text editors for registry/configuration changes, process monitoring tools like 'top' or 'htop') where appropriate.
  • Clarify in the introduction if the instructions are only applicable to Windows, or explicitly state support for both platforms.
  • If Linux is not supported, clearly state this limitation to set user expectations.
GitHub Create Pull Request
Site Recovery Archive for What's new in Azure Site Recovery ...icles/site-recovery/site-recovery-whats-new-archive.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 page generally provides parity between Windows and Linux support announcements for Azure Site Recovery, listing new supported Linux distributions alongside Windows versions. However, there are several instances of Windows bias: Windows operating systems are often mentioned first in lists, and Windows-specific tools (such as PowerShell) are referenced for certain features (e.g., firewall-enabled storage accounts, accelerated networking) before or instead of Linux equivalents. In some cases, features are described with explicit PowerShell support, while CLI or Linux-native tooling is not mentioned. The servicing stack/SHA-2 section is Windows-only, and Windows features (e.g., Storage Spaces Direct) are referenced with links to Windows documentation.
Recommendations
  • Ensure that Linux examples and tooling (e.g., Azure CLI, Bash scripts) are provided alongside or before PowerShell/Windows examples.
  • When listing supported operating systems, alternate the order or group by platform to avoid always listing Windows first.
  • Where features are described as supported via PowerShell, clarify if Azure CLI or other Linux-native methods are also supported, and provide equivalent instructions.
  • For sections referencing Windows-only features (e.g., servicing stack/SHA-2), clarify Linux requirements or explicitly state if not applicable.
  • Add more links to Linux documentation and troubleshooting guides where relevant.
  • Review all feature tables and ensure Linux support is described with equal detail and prominence as Windows support.
GitHub Create Pull Request
Site Recovery Fail back Azure VMware Solution VMsfrom Azure with Azure Site Recovery ...b/main/articles/site-recovery/avs-tutorial-failback.md
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 Windows bias by specifically mentioning Windows VMs and their interaction with VMware tools during failover and failback, without providing equivalent details or examples for Linux VMs. There are no Linux-specific instructions, troubleshooting notes, or examples, and the only OS-specific behavior described is for Windows. The documentation also references VMware tools in the context of Windows VMs, but does not clarify the behavior for Linux VMs, which may use open-vm-tools or have different requirements.
Recommendations
  • Add explicit instructions and notes for Linux VMs, including any differences in failover/failback behavior, agent registration, and VMware/open-vm-tools handling.
  • Provide troubleshooting steps or caveats for Linux VMs, similar to those given for Windows VMs.
  • Include examples or screenshots that show both Windows and Linux VM workflows.
  • Clarify whether the described process and tool interactions apply equally to Linux VMs, and if not, specify the differences.
  • Ensure parity in documentation by mentioning Linux considerations wherever Windows-specific notes are given.
GitHub Create Pull Request
Site Recovery Set up Azure Site Recovery for Azure VMware Solution VMs ...ain/articles/site-recovery/avs-tutorial-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 Tools Missing Linux Example
Summary
The documentation demonstrates a 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 setup and credential requirements. Linux is mentioned only briefly and generically (e.g., 'provide details for the root account'), with no Linux-specific setup instructions, examples, or troubleshooting guidance. Windows tools and patterns (e.g., Windows Server installation, administrator credentials) are referenced exclusively or before Linux equivalents.
Recommendations
  • Provide detailed instructions and examples for deploying the configuration server VM with a Linux OS, if supported, including activation/licensing requirements and step-by-step setup.
  • Include Linux-specific credential requirements and troubleshooting steps, similar to those provided for Windows.
  • Clarify whether the OVA template supports Linux-based configuration servers, and if not, explicitly state the limitation.
  • Offer parity in examples and screenshots for Linux environments, such as command-line steps or UI walkthroughs.
  • Add notes or sections highlighting differences and considerations for Linux users throughout the tutorial.
GitHub Create Pull Request
Site Recovery Prepare Azure VMware Solution for disaster recovery to Azure Site Recovery ...ain/articles/site-recovery/avs-tutorial-prepare-avs.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 🔧 Windows Tools
Summary
The documentation demonstrates a moderate Windows bias. Windows-specific instructions and tools (such as registry edits and Windows Firewall) are described in greater detail and appear before Linux equivalents. The section on preparing accounts for Mobility service installation provides step-by-step Windows registry instructions, while the Linux guidance is minimal. Similarly, the section on connecting after failover gives more detailed, stepwise guidance for Windows (RDP, firewall, SAN policy) than for Linux (SSH, firewall). Windows tools and terminology (e.g., Windows Firewall, RDP, registry) are mentioned explicitly, while Linux alternatives are referenced more generally.
Recommendations
  • Provide equally detailed, step-by-step instructions for Linux scenarios, such as specifying commands to create a root account or configure SSH and firewall rules.
  • When listing OS-specific steps, alternate the order or present both Windows and Linux instructions in parallel to avoid 'windows_first' bias.
  • Include Linux-specific troubleshooting resources and links, similar to those provided for Windows (e.g., troubleshooting SSH connectivity after failover).
  • Mention Linux tools and configuration files explicitly (e.g., /etc/ssh/sshd_config, iptables, firewalld) where Windows tools are named.
  • Where Windows registry changes are described, provide equivalent Linux configuration steps (e.g., sudoers file, systemd service management) if applicable.
GitHub Create Pull Request
Site Recovery Fail over Azure VMware Solution VMs to Azure by using Site Recovery ...b/main/articles/site-recovery/avs-tutorial-failover.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 exhibits Windows bias in several ways. Windows terminology and links are presented before or instead of Linux equivalents (e.g., the availability set link points to a Windows-specific tutorial). The 'Connect to a failed-over VM' section mentions RDP and SSH but links only to Windows connection instructions, omitting Linux-specific guidance. There are no explicit Linux or cross-platform examples for VM connection, troubleshooting, or configuration, and references to boot drivers are Windows-centric.
Recommendations
  • Provide equal visibility and links to Linux documentation, such as connecting to Linux VMs via SSH.
  • Include examples and instructions for both Windows and Linux VM failover scenarios, including OS-specific considerations.
  • Reference both Windows and Linux availability set documentation, or use a neutral link.
  • Mention Linux-specific troubleshooting steps and tools where applicable.
  • Ensure terminology and examples are cross-platform, not Windows-centric.
GitHub Create Pull Request
Site Recovery Replicate Azure Stack Hub to Azure using Azure Site Recovery ...in/articles/site-recovery/azure-stack-site-recovery.md
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 first and in more detail than Linux equivalents; Windows-specific tools and patterns (such as registry edits, firewall configuration via GUI, and references to Windows command prompt) are described with explicit commands and steps, while Linux instructions are less detailed and lack command-line examples. There is a reliance on Windows-centric terminology and tools (e.g., RDP, VSS, registry edits), and Linux steps are presented after Windows ones and are less comprehensive.
Recommendations
  • Provide Linux command-line examples for all steps, such as configuring SSH, SFTP, and firewall rules.
  • List Linux operating systems and requirements with equal prominence and detail as Windows.
  • Include Linux-specific troubleshooting steps and automation options (e.g., using Ansible or shell scripts for Mobility service installation).
  • Avoid Windows-first ordering; alternate or parallelize instructions for Windows and Linux.
  • Reference Linux equivalents for Windows tools (e.g., use 'ssh' instead of RDP, describe how to check time synchronization on Linux).
  • Clarify any differences in failover and failback for Linux VMs, and provide parity in guidance for post-failover connectivity.
GitHub Create Pull Request
Site Recovery Common questions about Azure virtual machine disaster recovery with Azure Site Recovery ...icles/site-recovery/azure-to-azure-common-questions.md
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-specific features (such as ADE, VSS, and WSFC) are discussed in detail, often before or instead of Linux equivalents. PowerShell is frequently referenced as the primary automation method, with little mention of CLI or Bash alternatives. Windows-centric tooling and terminology (e.g., Volume Shadow Copy Service, WSFC shared disks) are used, and Linux examples or guidance are often missing or relegated to brief mentions. Some features are described as unsupported for Linux (e.g., shared disks), and instructions for Linux users are sparse compared to Windows.
Recommendations
  • Provide equivalent CLI/Bash examples alongside PowerShell for all automation tasks.
  • Explicitly document Linux support and limitations for all features, not just where unsupported.
  • Include Linux-specific instructions and examples for disk encryption, app-consistent snapshots, and failover scenarios.
  • Reference Linux tools and patterns (e.g., cloud-init, shell scripts) where appropriate.
  • Ensure that Linux and Windows are given equal prominence in feature support matrices and examples.
  • Clarify when features are Windows-only, and suggest Linux alternatives or workarounds where possible.
GitHub Create Pull Request
Site Recovery Replicate Azure virtual machines running Storage Spaces Direct with Azure Site Recovery ...ry/azure-to-azure-how-to-enable-replication-s2d-vms.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 is heavily focused on Windows-specific technologies, particularly Storage Spaces Direct (S2D) and Windows Failover Clustering. 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 or cross-platform examples, and the documentation assumes the use of Windows guest clusters and related Windows features.
Recommendations
  • Include information about disaster recovery for Linux-based clusters or virtual machines, such as those using MDADM, LVM, or other Linux storage solutions.
  • Provide parallel examples and guidance for setting up replication and failover for Linux VMs, including any differences in process or supported features.
  • Reference Linux clustering technologies (e.g., Pacemaker, Corosync) where appropriate, and clarify whether Azure Site Recovery supports these scenarios.
  • Add notes or sections that explicitly state the scope of support (Windows-only or cross-platform), and link to relevant Linux documentation if available.
  • Ensure that terminology and screenshots do not exclusively reference Windows tools and interfaces; include Azure portal views for Linux VMs if applicable.
GitHub Create Pull Request
← Previous Page 2 of 35 Next →