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 101-125 of 864 flagged pages
Site Recovery Troubleshoot the Azure VM extension for disaster recovery with Azure Site Recovery .../site-recovery/site-recovery-extension-troubleshoot.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 listing Windows troubleshooting steps and examples before Linux equivalents, using Windows-specific tools (services.msc, Control Panel, MSI installers), and providing more detailed step-by-step instructions for Windows than for Linux. Linux instructions are less detailed and lack parity in troubleshooting depth and tool references.
Recommendations
  • Present Windows and Linux troubleshooting steps in parallel sections, or alternate which OS is listed first.
  • Provide equally detailed, step-by-step instructions for Linux, including commands for checking agent status, uninstalling/reinstalling the agent, and verifying dependencies.
  • Reference Linux-native tools (e.g., systemctl, package managers) with explicit commands for common distributions.
  • Include troubleshooting for Linux-specific issues (e.g., permission problems, log file locations) to match the depth given for Windows.
  • Avoid referencing Windows tools (services.msc, Control Panel) without Linux equivalents; provide analogous Linux instructions (e.g., checking services via systemctl, verifying installation via package manager).
GitHub Create Pull Request
Site Recovery Run a failover during disaster recovery with Azure Site Recovery .../main/articles/site-recovery/site-recovery-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 demonstrates Windows bias in several ways: Windows VM instructions are consistently listed before Linux VM instructions in tables and explanations. Windows-specific tools and settings (such as Windows Firewall, RDP, WinHTTP proxy, SAN policy, and Windows Update) are described in detail, while Linux instructions are minimal and lack equivalent depth (e.g., only mentioning SSH and firewall rules). There are no Linux-specific troubleshooting steps, nor are there examples of automating failover actions for Linux environments. The overall pattern prioritizes Windows use cases and tools, with Linux coverage being brief and secondary.
Recommendations
  • Alternate the order of Windows and Linux instructions in tables and sections to avoid implicit prioritization.
  • Expand Linux VM preparation steps to include common troubleshooting, security, and connectivity issues (e.g., SELinux, systemd services, SSH configuration, iptables/firewalld rules, cloud-init settings).
  • Provide Linux-specific examples for post-failover configuration, such as checking system logs, verifying SSH keys, and handling network interface changes.
  • Include links to Linux-focused troubleshooting guides, not just Windows RDP issues.
  • Mention Linux automation options (e.g., shell scripts, Ansible playbooks) alongside PowerShell and Windows-centric automation.
  • Clarify that both Windows and Linux environments are supported equally, and ensure parity in detail and guidance for both platforms.
GitHub Create Pull Request
Site Recovery Set up disaster recovery for an IIS web app using Azure Site Recovery .../blob/main/articles/site-recovery/site-recovery-iis.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 is heavily focused on Windows environments, specifically IIS on Windows Server, with all examples and scripts tailored for Windows (e.g., PowerShell scripts, IIS-specific instructions). There is no mention of Linux-based web servers (such as Apache or Nginx), nor are there examples or guidance for disaster recovery of Linux workloads. Windows tools and patterns (IIS, ARR, PowerShell) are referenced exclusively and before any Linux alternatives, which are not present.
Recommendations
  • Include equivalent disaster recovery guidance for Linux-based web servers (e.g., Apache, Nginx) and multi-tier applications running on Linux.
  • Provide Linux-specific examples, such as shell scripts for updating DNS, connection strings, and site bindings.
  • Reference Linux tools and patterns (e.g., systemd, Apache/Nginx config files, certbot for TLS/SSL) alongside Windows/IIS instructions.
  • Clarify which steps are OS-agnostic and which require platform-specific actions, and provide parity in automation examples (e.g., Bash scripts for Linux, PowerShell for Windows).
  • Add a section or links for users running web applications on Linux, describing how Azure Site Recovery supports those scenarios.
GitHub Create Pull Request
Site Recovery About Azure Site Recovery .../main/articles/site-recovery/site-recovery-overview.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 prioritizing Windows-centric technologies and scenarios. Windows tools and patterns (e.g., Windows Server Failover Clusters, SQL Server Always On, AWS Windows instances) are mentioned explicitly, while Linux equivalents are either absent or referenced only generically. Examples and feature highlights focus on Windows workloads and tools, with no concrete Linux-specific examples or guidance.
Recommendations
  • Add explicit Linux workload examples, such as replicating Linux VMs running common applications (e.g., Apache, MySQL, SAP on Linux).
  • Include references to Linux clustering solutions (e.g., Pacemaker, Corosync) and how Site Recovery supports them.
  • Provide step-by-step guides or links for Linux VM replication and failover, similar to those for Windows workloads.
  • Mention Linux-specific considerations for application consistency, recovery plans, and automation integration.
  • Balance references to Windows tools (e.g., SQL Server Always On, WSFC) with Linux alternatives (e.g., PostgreSQL replication, Linux HA clusters).
GitHub Create Pull Request
Site Recovery Troubleshoot failover to Azure failures ...covery/site-recovery-failover-to-azure-troubleshoot.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 demonstrates a Windows bias in several ways: troubleshooting steps for hydration errors are exclusively provided for Windows Guest OS using PowerShell scripts, with no equivalent Linux instructions. The use of Windows-specific tools (PsExec, Internet Explorer) is recommended for proxy troubleshooting, even in contexts involving Linux Master Targets. Windows troubleshooting steps and references (RDP, registry edits) are more detailed and appear before Linux equivalents, while Linux-specific guidance is limited and less comprehensive.
Recommendations
  • Add equivalent Linux troubleshooting steps for hydration errors, including commands/scripts to check and set required driver/service states.
  • Provide Linux-native methods for proxy troubleshooting (e.g., using curl, wget, or environment variable edits) instead of relying on Windows tools like PsExec and Internet Explorer.
  • Ensure that Linux examples are presented with equal detail and prominence as Windows examples, including step-by-step instructions and output samples.
  • Where possible, present cross-platform instructions together or in parallel tabs/sections, rather than focusing on Windows first.
  • Expand references to Linux-specific documentation and tools, such as SSH troubleshooting, systemd/service management, and network configuration.
GitHub Create Pull Request
Site Recovery Deprecation of IPConfig parameters for the cmdlet New-AzRecoveryServicesAsrVMNicConfig | Microsoft Docs ...ttps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/site-recovery-ipconfig-cmdlet-parameter-deprecation.md
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 exclusively provides examples using Azure PowerShell cmdlets, which are most commonly used on Windows and in Windows-centric environments. There are no references to Linux tools, Bash, Azure CLI, or cross-platform scripting alternatives. The guidance assumes users are working in PowerShell, and does not mention or illustrate how to perform equivalent operations on Linux or macOS systems.
Recommendations
  • Add equivalent examples using Azure CLI, which is cross-platform and commonly used on Linux and macOS.
  • Explicitly mention that the cmdlets can be run on PowerShell Core on Linux/macOS, if supported, and provide instructions for installation and usage.
  • Include Bash script examples for common operations, or at least reference how Linux users can achieve the same outcomes.
  • Add a section comparing PowerShell and CLI approaches, highlighting platform compatibility.
  • Clarify any platform-specific limitations or requirements for the cmdlets discussed.
GitHub Create Pull Request
Site Recovery Remove servers and disable protection ...ry/site-recovery-manage-registration-and-protection.md
High Priority View Details →
Scanned: 2026-01-11 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 environments, specifically focusing on Hyper-V, VMM, and PowerShell-based workflows. All provided scripts and automation steps use PowerShell and reference Windows-specific tools, registry paths, and services. There are no examples or instructions for Linux-based servers, agents, or environments, nor is there mention of equivalent Linux procedures or tools. The documentation assumes a Windows-centric infrastructure and omits Linux parity in both conceptual and practical guidance.
Recommendations
  • Add equivalent instructions and scripts for unregistering and cleaning up Linux-based servers, if supported by Site Recovery.
  • Include bash or shell script examples for Linux environments where applicable.
  • Explicitly mention whether certain procedures are Windows-only, and provide Linux alternatives or a statement about Linux support.
  • Balance the order of presentation by including Linux guidance alongside Windows steps, rather than focusing exclusively on Windows tools and patterns.
  • Reference Linux tools (e.g., systemctl, Linux file paths, Linux agent management) where relevant, and provide parity in troubleshooting and cleanup procedures.
GitHub Create Pull Request
Site Recovery Add Azure Automation runbooks to Site Recovery recovery plans ...cles/site-recovery/site-recovery-runbook-automation.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools Windows First
Summary
The documentation page demonstrates a strong Windows bias by exclusively providing PowerShell-based examples and scripts, referencing Windows-centric Azure modules (AzureRM.*), and omitting any Linux shell (Bash, Python, etc.) or cross-platform scripting alternatives. All automation instructions and code samples use PowerShell syntax, which is native to Windows and only recently available on Linux. There is no mention of Linux-specific tools, patterns, or considerations, nor any guidance for users who may prefer or require Bash or Python for automation. The documentation assumes a Windows-centric workflow and does not address Linux parity.
Recommendations
  • Provide equivalent examples using Bash and/or Python for runbook automation, especially for users managing Linux VMs.
  • Mention and document the use of Azure CLI (az) commands as alternatives to PowerShell cmdlets.
  • Clarify cross-platform compatibility of Azure Automation runbooks, including any limitations or requirements for Linux-based automation.
  • Include guidance on installing and using PowerShell Core on Linux, if PowerShell is required, and highlight any differences from Windows PowerShell.
  • Reference Linux-specific modules or best practices for automating recovery plan tasks on Linux VMs.
  • Add a section comparing PowerShell and Bash/Python approaches for common recovery plan automation scenarios.
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-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 focusing exclusively on SAP NetWeaver deployments in a Windows environment, referencing Windows Server Failover Cluster, Storage Spaces Direct, and SIOS DataKeeper (Windows-centric tools) for high availability and clustering. There are no examples, recommendations, or guidance for SAP deployments on Linux, which is a common platform for SAP. Linux clustering tools and patterns are not mentioned, and all technical guidance assumes a Windows-based deployment.
Recommendations
  • Add equivalent guidance and examples for SAP NetWeaver deployments on Linux, including supported Linux distributions on Azure.
  • Include clustering and high availability recommendations for Linux, such as using Pacemaker/Corosync, NFS, or other Linux-native solutions.
  • Provide parity in disaster recovery steps and scripts for Linux-based SAP deployments, including automation examples using Bash or Ansible.
  • Mention both Windows and Linux options in architecture diagrams and reference sections.
  • Clarify any Azure Site Recovery limitations or differences for Linux VMs, and link to relevant documentation.
GitHub Create Pull Request
Site Recovery Disaster recovery for a multi-tier SharePoint app using Azure Site Recovery ...ain/articles/site-recovery/site-recovery-sharepoint.md
High Priority View Details →
Scanned: 2026-01-11 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 clear Windows bias. All examples and guidance are centered around Windows Server, Windows-based SharePoint, and SQL Server. The recovery steps, scripting, and tooling (e.g., PowerShell cmdlets, DFSR, AzCopy) are Windows-centric. There are no Linux equivalents, nor any mention of Linux-based SharePoint alternatives or recovery patterns. Windows terminology and tools are used exclusively, and scripting examples rely on PowerShell, with no Bash or Linux shell alternatives. The documentation assumes the reader is working in a Windows environment and does not address Linux scenarios.
Recommendations
  • Include examples and guidance for Linux-based deployments, such as SharePoint alternatives (e.g., Alfresco, Nextcloud) or SQL Server on Linux.
  • Provide equivalent scripting examples using Bash or other Linux shell environments alongside PowerShell.
  • Mention Linux-compatible tools for file copying and backup (e.g., rsync, scp) in addition to Windows tools like AzCopy and DFSR.
  • Clarify which steps are specific to Windows and offer Linux-specific instructions where applicable.
  • Add a section outlining disaster recovery considerations for Linux-based workloads, even if SharePoint itself is Windows-only, to improve cross-platform relevance.
GitHub Create Pull Request
Site Recovery Plan capacity for VMware disaster recovery with Azure Site Recovery ...es/site-recovery/site-recovery-plan-capacity-vmware.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 Windows First Missing Linux Example
Summary
The documentation page exhibits a Windows bias in several areas: it provides examples and instructions primarily for Windows environments (e.g., registry edits, MMC snap-in usage, PowerShell cmdlets), references Windows-specific tools and paths, and omits equivalent Linux instructions or examples for key operations such as bandwidth throttling and registry modifications. Linux is mentioned only in the context of master target server deployment, with no parity in operational guidance for Linux-based process/configuration servers.
Recommendations
  • Provide Linux-specific examples for bandwidth throttling and process server configuration, including relevant commands and configuration file paths.
  • Include instructions for modifying replication settings on Linux servers, such as how to adjust thread counts or bandwidth limits using Linux tools or configuration files.
  • Offer parity in automation examples (e.g., Bash scripts or Linux CLI commands) alongside PowerShell for common administrative tasks.
  • Clarify which steps are OS-agnostic and which require OS-specific actions, and ensure both Windows and Linux procedures are documented where applicable.
  • Reference Linux equivalents for Windows tools (e.g., alternatives to MMC snap-in, registry, and PowerShell), or note limitations and workarounds for Linux environments.
GitHub Create Pull Request
Site Recovery Set up disaster recovery for SQL Server with Azure Site Recovery .../blob/main/articles/site-recovery/site-recovery-sql.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 page demonstrates a Windows bias by consistently referencing Windows-specific technologies, tools, and procedures. All examples and links for SQL Server high availability and disaster recovery reference Windows-based solutions (e.g., Windows Server Failover Clustering, Always On AGs for Windows), and there are no examples or guidance for Linux-based SQL Server deployments. Instructions for monitoring disk write rates reference Windows Task Manager only, and failover automation scripts are provided in PowerShell. There is no mention of Linux equivalents (e.g., Linux clustering, Linux monitoring tools, Bash scripts), nor are Linux scenarios or commands addressed.
Recommendations
  • Add explicit guidance and examples for SQL Server running on Linux, including supported BCDR technologies and any Azure Site Recovery limitations or differences.
  • Provide Linux-specific instructions for monitoring disk write rates (e.g., using iostat, atop, or other Linux tools).
  • Include automation scripts or runbook examples in Bash or Python for Linux environments, or clarify how PowerShell scripts can be adapted for Linux.
  • Reference Linux documentation for SQL Server high availability and disaster recovery (e.g., Always On AGs on Linux, Pacemaker clustering).
  • Ensure that all procedures, prerequisites, and troubleshooting steps include Linux variants where applicable, or clearly state any platform limitations.
GitHub Create Pull Request
Site Recovery Run the Deployment Planner for VMware disaster recovery with Azure Site Recovery ...ecovery/site-recovery-vmware-deployment-planner-run.md
High Priority View Details →
Scanned: 2026-01-11 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 command-line examples use Windows paths and syntax, and the only method provided for generating the VM list is via VMware vSphere PowerCLI (a Windows/PowerShell tool). The tool itself (ASRDeploymentPlanner.exe) is a Windows executable, and report generation explicitly requires a Windows PC or Server with Microsoft Excel. There are no Linux or cross-platform alternatives or examples provided, and Linux users are not addressed.
Recommendations
  • Provide instructions and examples for generating VM lists using Linux-compatible tools (e.g., VMware vSphere CLI, Python scripts, or REST APIs).
  • Clarify whether ASRDeploymentPlanner.exe can be run under Wine or in a Windows VM on Linux, and provide guidance if possible.
  • Offer alternative report formats (e.g., CSV, HTML, or PDF) that do not require Microsoft Excel on Windows.
  • Explicitly state platform requirements and limitations at the beginning of the documentation.
  • If possible, develop and document a cross-platform version of the Deployment Planner tool.
GitHub Create Pull Request
Site Recovery Analyze the Deployment Planner report for VMware disaster recovery with Azure Site Recovery ...site-recovery-vmware-deployment-planner-analyze-report.md
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-specific features (such as EFI support) are described in detail, with explicit mention of supported Windows Server versions, while Linux support is only briefly referenced. There are no Linux-specific examples, troubleshooting steps, or tool usage instructions. Windows terminology and tools (e.g., 'configuration server', 'process server', 'ExpressRoute', and references to Windows EFI) are mentioned exclusively or before Linux equivalents. The documentation does not provide parity in guidance or examples for Linux environments.
Recommendations
  • Add explicit Linux examples and troubleshooting steps, especially for common Linux distributions used in VMware environments.
  • Clarify which features and limitations apply to Linux VMs (e.g., EFI support, failover/failback capabilities, disk mapping, and compatibility checks).
  • Include Linux-specific tooling or command-line instructions where relevant, such as how to run the Deployment Planner tool on Linux or analyze reports using Linux-native tools.
  • Balance references to Windows and Linux throughout the documentation, ensuring that Linux is not only mentioned but also supported with actionable guidance.
  • Provide parity in screenshots and sample report data for both Windows and Linux VM scenarios.
GitHub Create Pull Request
Site Recovery About disaster recovery for on-premises apps with Azure Site Recovery .../main/articles/site-recovery/site-recovery-workload.md
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 exhibits a Windows bias by prioritizing Windows workloads and tools (Active Directory, Exchange, SharePoint, IIS, Dynamics AX, SQL Server, Remote Desktop Services) in both the workload summary and detailed sections. Windows-specific technologies are described in detail, with references to Windows Server documentation and features like Exchange DAGs, IIS, and RDS. Linux is mentioned only briefly and generically, without specific examples, guidance, or parity in coverage. There are no Linux-specific application examples, tools, or patterns provided, and no references to Linux disaster recovery best practices or documentation.
Recommendations
  • Add detailed Linux workload examples, such as Apache, NGINX, MySQL, PostgreSQL, Samba, and other common Linux-based applications.
  • Include Linux-specific disaster recovery patterns, tools, and integrations (e.g., systemd, cron, rsync, LVM snapshots, native clustering solutions like Pacemaker/Corosync).
  • Provide parity in documentation depth for Linux workloads, including step-by-step guides, recovery plan scripting examples (using Bash or Python), and references to Linux documentation.
  • Reference Linux vendor documentation (e.g., Red Hat, Ubuntu, SUSE) for best practices in disaster recovery.
  • Ensure that Linux examples and guidance appear alongside Windows examples, not only as a generic mention.
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-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 exclusively covers Windows operating systems and tools, providing registry and KB article instructions for enabling TLS 1.2 on Windows versions. There are no examples, instructions, or references for enabling or verifying TLS on Linux systems, nor any mention of Linux-specific tools or configuration patterns. All technical details and troubleshooting steps are Windows-centric.
Recommendations
  • Add equivalent instructions for enabling and verifying TLS 1.2 on common Linux distributions (e.g., Ubuntu, CentOS), including configuration file changes (such as for OpenSSL or stunnel).
  • Include Linux command-line examples for checking TLS protocol support (e.g., using openssl s_client).
  • Reference Linux-specific documentation or KB articles where appropriate.
  • Clarify whether Azure Site Recovery supports Linux-based source/target machines and, if so, provide parity in troubleshooting and configuration guidance.
  • Present Windows and Linux instructions side-by-side or in separate, clearly labeled sections to improve cross-platform accessibility.
GitHub Create Pull Request
Site Recovery Unregister a Virtual Machine Manager server script ...articles/site-recovery/unregister-vmm-server-script.md
High Priority View Details →
Scanned: 2026-01-11 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. All code examples are in PowerShell, using Windows-specific cmdlets and registry paths. The script relies on Windows services (SCVMMService, ClusSvc), Windows registry, and Windows clustering tools. There is no mention of Linux equivalents, nor are any Linux/bash examples provided. The instructions and tooling are exclusively for Windows environments.
Recommendations
  • Add a section clarifying platform support and limitations, explicitly stating if Linux is unsupported or providing Linux alternatives if possible.
  • If Linux support is feasible, provide equivalent bash scripts or instructions for Linux-based VMM management.
  • Reference cross-platform tools or APIs (e.g., REST, SDKs) where available, and show examples for both Windows and Linux.
  • Reorder documentation to mention platform requirements up front, and avoid assuming Windows as the default.
  • If the functionality is Windows-only, make this clear in the introduction and consider linking to Linux-based virtualization management documentation for parity.
GitHub Create Pull Request
Site Recovery Common questions about VMware disaster recovery with Azure Site Recovery ...rticles/site-recovery/vmware-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 page demonstrates several instances of Windows bias. Windows tools and paths (e.g., PowerShell, C:\Program Files, %ProgramData%, C:\Temp) are mentioned first or exclusively in installation and configuration instructions. PowerShell is referenced as a primary automation method, with less emphasis on Linux-native alternatives. Some examples and instructions (such as manual MySQL installation and agent unregistration) provide Windows commands and paths before Linux equivalents, and in some cases, Linux instructions are less detailed or appear as an afterthought. There is limited mention of Linux-specific tools or scripting approaches, and the overall pattern prioritizes Windows environments.
Recommendations
  • Provide Linux examples and instructions alongside Windows, with equal detail and prominence.
  • Include Linux-native automation and scripting options (e.g., Bash, shell scripts, Ansible) in addition to PowerShell.
  • List Linux commands and paths before or alongside Windows equivalents, not only after.
  • Reference Linux filesystem paths and conventions where relevant, and avoid assuming Windows as the default environment.
  • Highlight cross-platform compatibility and clarify any differences in process or tooling between Windows and Linux.
  • Where third-party tools (like MySQL) are involved, include Linux installation steps and locations, not just Windows (e.g., /tmp/ASRSetup).
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-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation exhibits a Windows bias by exclusively describing the configuration server as a Windows Server 2016 VM, with all setup, registration, and management steps assuming a Windows environment. Examples and instructions (e.g., MySQL installation, folder paths, administrator credentials) are Windows-centric, with Linux only briefly mentioned in the context of VM credentials. There are no Linux-based deployment options, examples, or parity in tooling or process.
Recommendations
  • Provide explicit instructions or alternatives for deploying the configuration server on Linux-based VMs, if supported.
  • Include Linux-specific examples for steps such as MySQL installation, file paths, and credential requirements.
  • Clarify whether the configuration server must be Windows-only, and if so, explain the rationale and suggest Linux-compatible alternatives for related tasks.
  • Add parity in troubleshooting and FAQ sections for Linux users, including common issues and solutions.
  • If Windows is a hard requirement, make this clear early in the documentation and link to Linux-based disaster recovery options where available.
GitHub Create Pull Request
Site Recovery Exclude VMware VM disks from disaster recovery to Azure with Azure Site Recovery ...in/articles/site-recovery/vmware-azure-exclude-disk.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 by providing specific details and examples for Windows failback before Linux, mentioning Windows disks and their behavior in failback with more nuance, and referencing Windows tools and patterns (such as Azure automation and disk creation on Azure VMs) without equivalent Linux examples or instructions. Linux failback is described only briefly and lacks parity in example depth and guidance.
Recommendations
  • Provide Linux-specific examples and instructions for disk exclusion, failover, and failback, matching the detail given for Windows.
  • Include parity in guidance for Azure automation integration for Linux VMs, not just Windows.
  • Ensure that any references to disk creation, failback, and reprotection include both Windows and Linux scenarios with equal detail.
  • Add screenshots or walkthroughs for Linux VM disk exclusion and failback processes.
  • Review and update terminology to avoid Windows-first phrasing and ensure equal prominence for Linux workflows.
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-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 update procedures and tools (e.g., Registry Editor, .msi installers, command prompt, Windows-specific paths) are described in detail and appear first in most sections. Linux instructions are present for the mobility agent update, but are less detailed and not provided for appliance component updates. Windows tools and patterns (Registry Editor, .msi, Windows Settings) are mentioned exclusively for appliance management, with no Linux equivalents or parity. Powershell or command prompt examples are used heavily, while Linux shell examples are minimal. There are missing Linux examples for appliance component updates and registry/configuration management.
Recommendations
  • Provide Linux-specific instructions for appliance component updates, including update commands, package management, and configuration changes.
  • Include Linux equivalents for registry/configuration changes (e.g., config files, systemd, environment variables) where Registry Editor is referenced.
  • Ensure Linux examples are given equal prominence and detail as Windows examples, including troubleshooting and verification steps.
  • Add notes or tables summarizing platform-specific differences and required tools for both Windows and Linux.
  • Where possible, use cross-platform tools or scripts, or document both Windows and Linux procedures side-by-side.
GitHub Create Pull Request
Site Recovery Enable VMware VMs (Modernized) for disaster recovery using Azure Site Recovery ...icles/site-recovery/vmware-azure-enable-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 exhibits a Windows bias in several ways. PowerShell is mentioned as the primary or only scripting/automation interface for enabling replication and managing disaster recovery, with no equivalent Linux CLI or shell examples. Windows-specific features, such as Azure Hybrid Benefit for Windows Server licenses, are highlighted without mention of Linux licensing or benefits. The prerequisites and troubleshooting sections refer to Windows disk types and UEFI requirements, with no equivalent Linux-specific guidance. Throughout, Windows terminology and tools are presented first or exclusively, while Linux alternatives are absent.
Recommendations
  • Include Azure CLI and Bash examples alongside PowerShell for all automation steps, especially for enabling replication and managing VMs.
  • Add guidance for Linux VMs, such as supported Linux distributions, disk types, and boot requirements, in the prerequisites and troubleshooting sections.
  • Mention Linux licensing considerations and any benefits or caveats for disaster recovery scenarios, similar to the Azure Hybrid Benefit for Windows.
  • Ensure that references to VM properties, disk types, and network configuration include Linux-specific details where relevant.
  • Provide links to Linux-focused documentation or best practices for disaster recovery with Azure Site Recovery.
GitHub Create Pull Request
Site Recovery Fail back VMware VMs/physical servers from Azure with Azure Site Recovery ...b/main/articles/site-recovery/vmware-azure-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 🔧 Windows Tools Missing Linux Example
Summary
The documentation page displays Windows bias by specifically mentioning Windows VMs and their interaction with VMware tools, while omitting any equivalent details or considerations for Linux VMs. There are no Linux-specific instructions, examples, or notes, and the only OS-specific guidance is for Windows. This suggests a lack of parity in guidance for Linux environments.
Recommendations
  • Add explicit instructions and notes for Linux VMs, including any differences in failback behavior, agent registration, and interaction with VMware tools.
  • Include examples or troubleshooting steps relevant to Linux VMs, such as handling Linux-specific drivers or services during failback.
  • Clarify whether the process and recommendations apply equally to both Windows and Linux VMs, or highlight any OS-specific steps.
  • If VMware tools behave differently on Linux, document those differences and provide guidance for Linux users.
GitHub Create Pull Request
Site Recovery Prepare source machines to install the Mobility Service through push installation for disaster recovery of VMware VMs and physical servers to Azure ...site-recovery/vmware-azure-install-mobility-service.md
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 presents Windows instructions before Linux, with detailed registry and firewall configuration steps specific to Windows. Windows tools (e.g., cspsconfigtool.exe) are referenced with Windows paths and usage patterns. Linux instructions are present but less detailed, and some steps (e.g., anti-virus exclusions) only mention Windows paths. There is also a focus on Windows-specific ports (SMB, WMI) in the notes, with no mention of Linux equivalents.
Recommendations
  • Alternate the order of Windows and Linux instructions or present them in parallel sections to avoid Windows-first bias.
  • Provide Linux-specific examples for anti-virus exclusions, such as typical agent installation paths on Linux systems.
  • Clarify whether cspsconfigtool.exe is available for Linux or provide Linux-native alternatives or usage instructions.
  • Include Linux-specific firewall configuration steps (e.g., using iptables, firewalld, or ufw) and mention relevant ports for Linux.
  • Add examples for Linux account creation and management, not just root usage, to match the detail given for Windows accounts.
  • Mention Linux equivalents for SMB and WMI ports, or clarify which ports are relevant for Linux push installations.
GitHub Create Pull Request
Site Recovery Manage a process server for VMware VMs/physical server disaster recovery in Azure Site Recovery ...es/site-recovery/vmware-azure-manage-process-server.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 Windows First Missing Linux Example
Summary
The documentation page demonstrates a strong Windows bias. All command-line instructions use Windows-specific tools (cmd.exe, PowerShell), Windows environment variables (%PROGRAMDATA%), and Windows file paths (C:\...). There are no Linux-specific instructions, examples, or mentions of Linux equivalents for process server management, despite the fact that VMware environments are often managed from Linux systems as well.
Recommendations
  • Provide equivalent Linux instructions for all command-line operations, including registering/reregistering process servers and modifying proxy settings.
  • Include Linux file paths and environment variable references alongside Windows ones.
  • Offer bash shell and Linux tool examples (e.g., using systemctl instead of net stop/start, using $HOME or /var/lib instead of %PROGRAMDATA%).
  • Clarify OS requirements and support for process servers, and explicitly state if Linux is unsupported or provide parity where possible.
  • List anti-virus exclusion paths for Linux-based process servers, if supported.
GitHub Create Pull Request
← Previous Page 5 of 35 Next →