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 651-675 of 864 flagged pages
Site Recovery Troubleshoot Azure VM replication in Azure Site Recovery - VM errors ...site-recovery/azure-to-azure-virtual-machine-errors.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. While disk initialization is covered for both Windows and Linux, all cleanup scripts for stale Site Recovery configurations are provided only as PowerShell (.ps1) scripts, with no mention of Bash, Azure CLI, or Linux-native alternatives. The instructions for running these scripts assume a Windows environment and PowerShell usage, creating friction for Linux/macOS users who may not have access to PowerShell or prefer native tools.
Recommendations
  • Provide equivalent cleanup scripts in Bash or Azure CLI for Linux/macOS users.
  • Explicitly mention how Linux/macOS users can run the PowerShell script (e.g., via PowerShell Core on Linux, or provide step-by-step instructions for installation).
  • List both Windows and Linux approaches side by side for all tasks involving scripting or command-line operations.
  • Where possible, use cross-platform Azure CLI commands instead of PowerShell-only scripts.
GitHub Create Pull Request
Site Recovery About using ExpressRoute with Azure Site Recovery ...e-recovery/concepts-expressroute-with-site-recovery.md
Medium Priority View Details →
Scanned: 2026-01-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 provides a proxy bypass configuration example that exclusively uses Windows tools (PsExec and Internet Explorer) and omits Linux/macOS equivalents. The instructions and tooling are Windows-centric, with no guidance for Linux or macOS users on how to achieve the same configuration. This creates friction for non-Windows users attempting to configure proxy bypass for ExpressRoute replication traffic.
Recommendations
  • Add equivalent instructions for configuring proxy bypass on Linux and macOS servers, including relevant commands and configuration file locations.
  • Replace or supplement the PsExec/Internet Explorer example with cross-platform methods (e.g., using curl, wget, or browser settings on Linux/macOS).
  • Clearly indicate which steps are Windows-specific and provide parity for other operating systems.
  • Consider using platform-neutral language and examples where possible.
GitHub Create Pull Request
Site Recovery Connect to Azure VMs on-premises failover with Azure Site Recovery ...e-recovery/concepts-on-premises-to-azure-networking.md
Medium 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. The 'Prepare on-premises machines' section provides detailed, step-by-step instructions for Windows, referencing Windows-specific settings, services, PowerShell, and Windows Firewall. In contrast, Linux preparation is covered in only two brief bullet points, lacking detail and omitting common Linux tasks (e.g., SSH configuration, firewall commands, service management). Windows tools and patterns (PowerShell, Windows Firewall, RDP) are mentioned exclusively or first, with no Linux command-line equivalents or examples. This creates friction for Linux users, who must infer or research their own procedures.
Recommendations
  • Expand the 'Prepare Linux machines' section to match the detail of the Windows section. Include steps for checking and enabling SSH, configuring Linux firewalls (e.g., ufw, firewalld, iptables), and verifying required services.
  • Provide Linux command-line examples for each step, similar to the PowerShell examples given for Windows.
  • Mention Linux-specific remote access tools and patterns (e.g., SSH, xrdp if relevant), and clarify any differences in Azure VM connectivity for Linux.
  • Ensure that Linux instructions are presented with equal prominence and detail as Windows instructions.
  • Where scripts or automation are referenced, provide both PowerShell and Bash/CLI examples.
GitHub Create Pull Request
Site Recovery Remove an Azure Site Recovery replication appliance ...s/blob/main/articles/site-recovery/delete-appliance.md
Medium 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 page demonstrates a notable Windows bias. It references Windows-specific tools (e.g., Services.msc, World Wide Web Publishing Service), and browser instructions are tailored to Microsoft Edge. There are no Linux/macOS equivalents or examples for managing or resetting the appliance, nor are alternative commands or tools mentioned for non-Windows platforms. Windows terminology and steps are presented as the default, with no consideration for Linux or macOS users.
Recommendations
  • Add instructions for Linux/macOS users, such as how to restart relevant services (e.g., Apache/Nginx) instead of 'World Wide Web Publishing Service'.
  • Provide cross-platform browser cache clearing instructions, including Chrome, Firefox, and Safari.
  • Replace or supplement references to 'Services.msc' with Linux/macOS service management commands (e.g., systemctl, service).
  • Explicitly state any platform requirements for the Azure Site Recovery replication appliance and clarify if only Windows is supported.
  • Present steps for both Windows and Linux/macOS in parallel where appropriate.
GitHub Create Pull Request
Site Recovery Trusted launch VMs with Azure Site Recovery ...lob/main/articles/site-recovery/concepts-trusted-vm.md
Medium Priority View Details →
Scanned: 2026-01-13 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 moderate Windows bias. Several features (shared disks, 'Create a new VM' flow) are explicitly supported only for Windows OS, with Linux support either absent or not yet available. The migration section references PowerShell and CLI channels but does not provide Linux-specific guidance or examples. Windows features and support are mentioned before Linux equivalents, and some steps (such as uninstalling the mobility service) lack Linux-specific instructions.
Recommendations
  • Provide Linux-specific examples and instructions for tasks such as uninstalling the mobility service and migration steps.
  • Clearly indicate Linux support status for all features, and offer alternative workflows or timelines for Linux parity.
  • Include CLI/bash examples alongside PowerShell, especially for migration and management tasks.
  • Ensure that Linux features are described with equal prominence and detail as Windows features.
GitHub Create Pull Request
Site Recovery Deploy Azure Site Recovery Replication Appliance - Modernized ...tps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/deploy-vmware-azure-replication-appliance-modernized.md
Medium 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 page demonstrates a notable Windows bias. PowerShell is presented as the only command-line method for manual appliance setup, with no Linux shell or cross-platform alternatives. Registry and group policy checks are exclusively Windows-centric, and all troubleshooting and configuration steps reference Windows tools and patterns. There are no Linux/macOS-specific instructions or examples for appliance deployment, and Windows terminology is used throughout, even when discussing credentials for Linux VMs.
Recommendations
  • Provide equivalent Linux/macOS command-line instructions for appliance setup, such as bash scripts or guidance for OVF deployment on Linux hosts.
  • Clarify whether the OVF template can be deployed on non-Windows hypervisors and provide steps for Linux-based environments.
  • Include troubleshooting steps and prerequisite checks for Linux/macOS hosts, such as verifying system requirements and connectivity.
  • Avoid referencing Windows registry and group policy exclusively; note which steps are only relevant for Windows and provide Linux alternatives where possible.
  • Present examples for both Windows and Linux in credential management and agent installation sections.
GitHub Create Pull Request
Site Recovery Deprecation of Azure Site Recovery data encryption feature ...ticles/site-recovery/encryption-feature-deprecation.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation focuses exclusively on Hyper-V VMs, which are a Windows technology, and does not mention Linux or cross-platform scenarios. All remediation steps and linked articles are tailored to Hyper-V (Windows), with no guidance for Linux-based disaster recovery or encryption migration.
Recommendations
  • Add equivalent guidance for Linux-based VMs and their disaster recovery scenarios.
  • Clarify whether the deprecation and remediation steps apply only to Hyper-V or also to other platforms (e.g., VMware, Linux VMs).
  • Provide links or references to documentation for Linux VM encryption and failover processes.
  • Explicitly state platform limitations or scope to help non-Windows users understand applicability.
GitHub Create Pull Request
Site Recovery Delete an Azure Site Recovery vault ...-docs/blob/main/articles/site-recovery/delete-vault.md
Medium 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 provides only PowerShell-based examples and references for deleting an Azure Site Recovery vault, with no mention of equivalent CLI commands for Linux/macOS users. The use of PowerShell and Windows-centric tooling is exclusive, and alternative cross-platform methods (such as Azure CLI or portal instructions) are omitted.
Recommendations
  • Add Azure CLI examples for all vault deletion steps, including force deletion.
  • Include instructions for using the Azure Portal, which is platform-agnostic.
  • Explicitly state that PowerShell commands can be run on Linux/macOS (if true), or provide guidance for non-Windows environments.
  • Reorder examples so that cross-platform methods (CLI, portal) are shown before or alongside PowerShell.
GitHub Create Pull Request
Site Recovery About failover and failback in Azure Site Recovery - Modernized ...site-recovery/failover-failback-overview-modernized.md
Medium 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 demonstrates a moderate Windows bias, particularly in the 'Connect to Azure after failover' section, where Windows VM instructions are more detailed, listed first, and reference Windows-specific tools (e.g., Windows Firewall, RDP, SAN policy, Windows Update). Linux instructions are present but less detailed, lacking parity in troubleshooting and pre/post-failover configuration guidance. Some notes and troubleshooting links are Windows-specific, with no Linux equivalents.
Recommendations
  • Provide Linux instructions before or alongside Windows instructions, ensuring equal prominence.
  • Expand Linux VM guidance to match the detail level of Windows (e.g., include steps for configuring SSH, firewall rules, SELinux/AppArmor considerations, and common troubleshooting tips).
  • Add Linux-specific troubleshooting links and references, similar to those provided for Windows (e.g., SSH connection troubleshooting after failover).
  • Mention Linux equivalents for Windows-specific tools and settings (e.g., clarify how to check and configure SAN policy or disk mounting on Linux, and how to handle pending updates or package manager locks).
  • Where Windows-only notes are given (e.g., boot time issues on Windows Server 2012), clarify if there are Linux-specific caveats or explicitly state if not applicable.
GitHub Create Pull Request
Site Recovery New feature updates in Azure Site Recovery ...in/articles/site-recovery/feature-updates-whats-new.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example Powershell Heavy
Summary
The documentation page demonstrates a moderate Windows bias. Several feature updates focus exclusively on Windows Server Failover Clusters, Windows OS, and Windows-centric technologies (e.g., PowerShell support, Hyper-V). Windows features are described in detail, often without Linux equivalents or examples. Linux support is mentioned, but typically as a secondary note or in preview, and there are no Linux-specific usage examples or tooling references.
Recommendations
  • Provide equivalent Linux examples and tooling references (e.g., bash scripts, Linux clustering technologies) where Windows/PowerShell are mentioned.
  • Ensure feature updates for Linux are described with the same detail and clarity as Windows features.
  • When listing OS support, explicitly mention Linux distributions and versions where applicable.
  • Avoid listing Windows features or tools first unless they are the only supported option; strive for parity in ordering and coverage.
  • Include guidance for Linux users on how to achieve similar outcomes (e.g., using Linux-based clusters, monitoring tools).
GitHub Create Pull Request
Site Recovery Protect a file server by using Azure Site Recovery ...rticles/site-recovery/file-server-disaster-recovery.md
Medium 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 page demonstrates a notable Windows bias. It heavily references Windows-specific technologies such as DFSR (Distributed File System Replication), Active Directory, and Azure File Sync, all of which are primarily Windows-centric. Step-by-step instructions and examples are almost exclusively for Windows Server environments, with no equivalent guidance for Linux-based file servers. While Azure Files and SMB are mentioned as cross-platform, all practical examples, deployment steps, and sync group configurations focus on Windows servers. Linux and macOS are only briefly referenced as clients capable of mounting SMB shares, but not as sources or targets for replication or disaster recovery.
Recommendations
  • Add explicit instructions and examples for protecting Linux-based file servers using Azure Site Recovery, including supported configurations and limitations.
  • Include guidance for setting up disaster recovery for Samba servers or NFS shares on Linux, and how these can be replicated or failed over to Azure.
  • Provide parity in step-by-step guides for deploying Azure File Sync or similar solutions on Linux file servers, or clarify alternative approaches for non-Windows environments.
  • List Linux/macOS options and tools alongside Windows ones in all decision tables and recommendations, not just as SMB clients.
  • Clarify which features (e.g., DFSR, File Sync) are Windows-only and suggest cross-platform alternatives where available.
GitHub Create Pull Request
Site Recovery Replicate Azure virtual machines running in a proximity placement group ...tps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/how-to-enable-replication-proximity-placement-groups.md
Medium 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 page demonstrates a notable Windows bias. All command-line examples are exclusively in PowerShell, with no Bash, Azure CLI, or Linux-native scripting alternatives. The prerequisites and instructions for scripting are centered around Azure PowerShell, a tool most commonly used on Windows, and there is no mention of Azure CLI or Bash equivalents. Additionally, references to creating proximity placement groups link to Windows-specific documentation. The order of presentation and example selection consistently favors Windows/PowerShell, with Linux options only mentioned as VM OS types, not as admin environments.
Recommendations
  • Add equivalent Azure CLI and Bash examples for all PowerShell cmdlets, especially for replication setup and monitoring.
  • Include installation and usage instructions for Azure CLI on Linux/macOS, alongside PowerShell.
  • Reference cross-platform documentation for proximity placement groups, not just Windows-specific pages.
  • Explicitly state that all steps can be performed from Linux/macOS using Azure CLI, and provide links to relevant guides.
  • Where screenshots or UI steps are shown, clarify any OS-specific differences or limitations.
GitHub Create Pull Request
Site Recovery Configure on-premise disks for Azure through Hydration .../blob/main/articles/site-recovery/hydration-process.md
Medium 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 moderate Windows bias. Windows instructions and examples are presented first, with detailed steps, screenshots, and PowerShell commands. Windows-specific tools (diskpart, PowerShell, registry editing) are described in detail, while Linux instructions are less visual, rely on generic bash commands, and often refer users to external documentation for distribution-specific steps. Some manual configuration examples for Linux are missing or less explicit compared to Windows. Windows troubleshooting links are also prioritized.
Recommendations
  • Alternate the order of Windows and Linux sections, or present both in parallel tabs to avoid Windows-first bias.
  • Provide equivalent screenshots and step-by-step visuals for Linux procedures (e.g., mounting partitions, editing network files, checking agent status).
  • Include explicit Linux commands for all steps where Windows commands are shown (e.g., setting DHCP, checking agent status, disabling VMware tools).
  • Reference Linux troubleshooting resources equally alongside Windows links.
  • Expand Linux manual preparation instructions to match the detail level of Windows, including more distribution-specific examples.
GitHub Create Pull Request
Site Recovery Troubleshoot Hyper-V disaster recovery with Azure Site Recovery ...n/articles/site-recovery/hyper-v-azure-troubleshoot.md
Medium 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 is heavily focused on Windows environments, specifically Hyper-V on Windows Server, and consistently references Windows tools (Event Viewer, PowerShell, Disk Management, Resource Monitor) and Windows-specific troubleshooting steps. Examples and instructions almost exclusively use Windows terminology and utilities, with only a brief mention of Linux-based servers in a single step, without any Linux-specific guidance or examples.
Recommendations
  • Provide Linux-specific troubleshooting steps for VMs running Linux, including equivalent commands and log locations.
  • Include examples using Linux tools (e.g., journalctl, systemctl, df, lsblk) for common tasks such as checking service status, disk configuration, and network connectivity.
  • Add parity for PowerShell commands by showing equivalent Bash or shell commands for Linux environments.
  • Clarify which steps apply to Windows-only scenarios and which are relevant for Linux VMs, possibly using tabs or callouts.
  • Reference Linux documentation for app-consistent snapshots and integration services, and link to Azure Site Recovery Linux support articles.
GitHub Create Pull Request
Site Recovery Set up failover of Hyper-V VMs to Azure in Azure Site Recovery ...e-recovery/hyper-v-azure-failover-failback-tutorial.md
Medium 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 oriented toward Windows environments, specifically Hyper-V, and consistently references Windows tools and patterns (such as RDP and Windows VM connection guides) without providing Linux or macOS equivalents. There are no examples or instructions for Linux-based Hyper-V hosts or for connecting to Linux VMs after failover, and all cross-references for VM connection point to Windows-specific documentation.
Recommendations
  • Include explicit instructions and examples for connecting to Linux VMs after failover, such as using SSH from Linux/macOS clients.
  • Reference both Windows and Linux/macOS guides for connecting to Azure VMs (e.g., link to /azure/virtual-machines/linux/ssh instead of only /azure/virtual-machines/windows/connect-logon).
  • Clarify whether the failover process supports Linux VMs running on Hyper-V, and if so, provide any Linux-specific considerations or troubleshooting steps.
  • Wherever RDP is mentioned, also mention SSH as a primary connection method for Linux VMs.
  • If any PowerShell or Windows-specific tools are required, provide equivalent Bash/CLI commands for Linux/macOS administrators.
GitHub Create Pull Request
Site Recovery Review the Azure Site Recovery Deployment Planner cost estimation report for disaster recovery of Hyper-V VMs to Azure| Microsoft Docs ...recovery/hyper-v-deployment-planner-cost-estimation.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation is focused on Azure Site Recovery for Hyper-V VMs, a Windows-centric virtualization platform. While the cost estimation report and tables mention both Windows and non-Windows (Linux) VMs, all examples, terminology, and scenarios are centered around Hyper-V and Windows environments. There are no explicit Linux/macOS-specific examples, tools, or workflows described, and the documentation assumes familiarity with Windows-based disaster recovery patterns.
Recommendations
  • Include explicit examples or scenarios for Linux VMs, such as cost estimation for Linux-based workloads or common Linux DR configurations.
  • Clarify whether the Deployment Planner tool and cost estimation process are equally applicable to Linux VMs, and if there are any differences in the workflow or considerations.
  • Provide references or links to documentation covering disaster recovery planning for Linux VMs (e.g., VMware or physical Linux servers) to Azure, if supported.
  • If the tool is Windows-only or Hyper-V-specific, state this clearly at the beginning, and suggest alternative tools or guidance for Linux/macOS users.
GitHub Create Pull Request
Site Recovery Monitor Azure Site Recovery with Azure Monitor Logs ...b/main/articles/site-recovery/monitor-log-analytics.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation exhibits a Windows bias in the section on configuring the Microsoft monitoring agent for churn and upload rate logs. It exclusively describes downloading and installing the Windows Agent, navigating Windows-specific UI (Windows Servers, Windows Performance Counters), and provides no instructions or parity for Linux-based Process Servers. There are no Linux agent installation steps, nor references to Linux equivalents for performance counter configuration. This could create friction or confusion for users running Linux-based Process Servers or seeking cross-platform guidance.
Recommendations
  • Add instructions for installing and configuring the monitoring agent on Linux-based Process Servers, including download links, workspace configuration, and performance counter setup.
  • Include screenshots or CLI commands relevant to Linux environments (e.g., using the OMS agent on Linux, configuring counters via command line).
  • Clearly indicate whether the churn/upload rate monitoring feature is Windows-only, or provide Linux alternatives if available.
  • Present both Windows and Linux setup options side-by-side, or at least mention Linux support status early in the section.
  • If Linux is not supported for this feature, explicitly state this limitation to avoid confusion.
GitHub Create Pull Request
Site Recovery Set up disaster recovery of physical on-premises servers with Azure Site Recovery ...cles/site-recovery/physical-azure-disaster-recovery.md
Medium 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 provides steps for both Windows and Linux physical servers, but several sections show Windows bias. Windows-specific instructions (e.g., registry edits, CLI commands) are given in detail, while Linux instructions are minimal or absent. Windows tools and patterns (like registry editing and use of admin/domain accounts) are described first and in more depth. Linux users are told to use 'root' but receive no equivalent command-line examples or troubleshooting guidance.
Recommendations
  • Provide Linux-specific command-line examples for tasks like preparing the Mobility service account (e.g., how to ensure root SSH access, required permissions, or SELinux/AppArmor considerations).
  • Include troubleshooting steps for Linux servers similar to the detailed Windows registry instructions.
  • Present Windows and Linux instructions in parallel, rather than listing Windows steps first and Linux as an afterthought.
  • Reference Linux time synchronization tools (e.g., ntpd, chrony) alongside Windows Time Server.
  • Clarify any Linux-specific prerequisites, such as required packages, firewall rules, or supported distributions.
GitHub Create Pull Request
Site Recovery Set up the configuration server for disaster recovery of physical servers to Azure using Azure Site Recovery ...articles/site-recovery/physical-azure-set-up-source.md
Medium 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 by referencing Windows-specific requirements (such as .NET Framework and TLS settings), linking to Windows-only resources, and omitting Linux-specific setup instructions or troubleshooting. Examples and tips (e.g., time synchronization) reference Windows tools and documentation, with no Linux alternatives or parity.
Recommendations
  • Add explicit instructions for Linux configuration server setup, including prerequisites and installation steps.
  • Provide Linux equivalents for system requirements (e.g., required packages, time synchronization methods like ntpd/chrony).
  • Include troubleshooting steps and links relevant to Linux environments.
  • Ensure that examples and screenshots are balanced between Windows and Linux, or clarify when steps apply to both.
GitHub Create Pull Request
Site Recovery Enable replication for VMware VM disaster recovery to Azure with Azure Site Recovery ...rticles/site-recovery/quickstart-enable-replication.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation mentions both Linux and Windows OS in the context of credentials required for agent installation, but provides more detail for Windows (specifying admin privileges) and less for Linux (simply 'root credentials'). There are no explicit Linux-specific examples, screenshots, or troubleshooting steps, and Windows terminology (admin privileges) is mentioned first. No PowerShell or Windows-only tools are referenced, but the lack of Linux parity in examples and instructions is notable.
Recommendations
  • Provide explicit Linux examples and screenshots where relevant (e.g., showing credential entry for Linux VMs).
  • Clarify Linux requirements (e.g., SSH key vs. password, supported distributions, SELinux/AppArmor considerations).
  • Mention Linux-specific troubleshooting steps or logs for agent installation.
  • Ensure Linux terminology is used alongside Windows (e.g., 'root or sudo user' instead of just 'root').
  • Present Linux and Windows instructions in parallel or with equal prominence.
GitHub Create Pull Request
Site Recovery Enable replication for a physical server – Modernized ...es/site-recovery/physical-server-enable-replication.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation references both Windows and Linux operating systems, but provides more explicit guidance for Windows (e.g., specifying admin account requirements) and omits concrete Linux examples or details. Windows is mentioned before Linux in credential instructions, and there are no Linux-specific walkthroughs or troubleshooting tips. No PowerShell or Windows-only tools are referenced, but the lack of Linux parity in examples and instructions may cause friction for Linux users.
Recommendations
  • Provide explicit Linux credential examples (e.g., root vs. sudo user, SSH key usage).
  • Include Linux-specific screenshots or command-line instructions for manual Mobility Service installation.
  • Add troubleshooting tips for common Linux replication issues.
  • Ensure Linux instructions are presented with equal prominence as Windows instructions.
GitHub Create Pull Request
Site Recovery Move Azure virtual machines between government and public regions with Azure Site Recovery .../main/articles/site-recovery/region-move-cross-geos.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation shows a Windows bias in the 'Prepare an account for Mobility service installation' section, where detailed registry instructions and CLI commands are provided for Windows, while Linux instructions are minimal and lack equivalent detail or examples. Windows-specific configuration steps (registry edit, REG ADD command) are explained, but Linux users are only told to use the root account, with no further guidance or CLI examples.
Recommendations
  • Provide equivalent step-by-step instructions for Linux, including any necessary configuration changes, commands, or prerequisites for Mobility service installation.
  • Include Linux CLI examples for installing and configuring the Mobility service, similar to the Windows registry and REG ADD command.
  • Clarify any OS-specific requirements or troubleshooting steps for Linux, ensuring parity with Windows documentation.
  • Where possible, present Windows and Linux instructions side-by-side or in clearly separated sections to avoid implicit prioritization.
GitHub Create Pull Request
Site Recovery Troubleshoot failover to Azure failures ...covery/site-recovery-failover-to-azure-troubleshoot.md
Medium Priority View Details →
Scanned: 2026-01-13 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 notable Windows bias. Troubleshooting steps for hydration failures are exclusively provided for Windows Guest OS, with downloadable PowerShell scripts and registry edits, but there are no equivalent instructions or scripts for Linux VMs. The use of Windows tools like PsExec and Internet Explorer is described in detail for proxy troubleshooting, while Linux alternatives are mentioned only briefly or not at all. Windows-specific issues (e.g., Event ID 6008) are covered with dedicated guidance, whereas Linux troubleshooting is limited to a single UEFI/serial console example and a brief mention of SSH. In most sections, Windows solutions and tools are presented first or exclusively, with Linux guidance either missing or minimal.
Recommendations
  • Provide equivalent troubleshooting scripts and step-by-step instructions for Linux VMs, especially for hydration/startup driver issues.
  • Include Linux-specific examples and commands for proxy troubleshooting, such as using curl, wget, or editing environment variables, rather than focusing on Windows tools like PsExec and Internet Explorer.
  • Ensure that for each error scenario, both Windows and Linux guidance are given, with parity in detail and clarity.
  • Where Windows tools are referenced, mention Linux alternatives (e.g., using systemctl, journalctl, or modifying /etc files).
  • Present Windows and Linux solutions side-by-side or in parallel tabs, rather than Windows-first or Windows-only.
GitHub Create Pull Request
Site Recovery Run a failover during disaster recovery with Azure Site Recovery .../main/articles/site-recovery/site-recovery-failover.md
Medium 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 demonstrates a moderate Windows bias. Windows-specific instructions (such as enabling RDP, configuring Windows Firewall, and handling Windows updates) are more detailed and appear first in tables and sections. Linux guidance is present but less detailed, often limited to basic SSH and firewall setup. Windows tools and patterns (like WinHTTP proxy, SAN policy, and drive letter retention) are mentioned without Linux equivalents or alternatives. Troubleshooting and connectivity tips are more comprehensive for Windows, with Linux coverage being minimal.
Recommendations
  • Provide equally detailed Linux instructions, including common firewall configurations (e.g., iptables, firewalld, ufw), SSH hardening, and troubleshooting steps for connectivity issues.
  • Include Linux-specific post-failover checks, such as verifying cloud-init status, checking disk mounts, and handling persistent network interface naming.
  • Offer parity in troubleshooting resources, linking to Linux-specific guides for SSH and network issues.
  • Present Windows and Linux examples side-by-side or in parallel, rather than listing Windows first.
  • Mention Linux equivalents for Windows-specific tools and settings (e.g., alternatives to SAN policy, handling persistent routes, and proxy settings).
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
Medium 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 exclusively uses Azure PowerShell cmdlets and provides only PowerShell-based script examples, which are native to Windows environments. There is no mention of Linux/macOS equivalents, such as Azure CLI, nor are there any bash or cross-platform scripting examples. This creates friction for users on Linux or macOS who may not use PowerShell as their primary automation tool.
Recommendations
  • Add equivalent Azure CLI examples for all remediation steps and tasks.
  • Explicitly mention cross-platform support for PowerShell Core, if applicable, and clarify any limitations.
  • Provide bash script samples or guidance for Linux/macOS users.
  • Include a section comparing PowerShell and CLI approaches, helping users choose the best tool for their platform.
GitHub Create Pull Request
← Previous Page 27 of 35 Next →