Site Recovery

394
Total Pages
277
Linux-Friendly Pages
117
Pages with Bias
29.7%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

232 issues found
Showing 176-200 of 232 flagged pages
Site Recovery Enable VMware VMs (Modernized) for disaster recovery using Azure Site Recovery ...icles/site-recovery/vmware-azure-enable-replication.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
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. PowerShell is mentioned as the primary automation method, with REST API as an alternative, but no Linux-native CLI or scripting examples are provided. Windows-specific features (such as Azure Hybrid Benefit for Windows Server) are described in detail, while Linux equivalents or considerations are missing. Windows terminology and tools (PowerShell, Windows Server licensing) are referenced before or instead of Linux options.
Recommendations
  • Include Azure CLI and Bash scripting examples for enabling and automating replication, alongside PowerShell.
  • Explicitly mention Linux support and provide guidance for Linux VMs, including any OS-specific prerequisites or limitations.
  • Add documentation or links for automating replication from Linux/macOS environments, not just PowerShell.
  • Clarify which features (e.g., Azure Hybrid Benefit) are Windows-only and provide Linux alternatives or note their absence.
  • Ensure that references to supported operating systems and disk types include Linux details and examples.
GitHub Create Pull Request
Site Recovery Install a master target server for Linux VM failback with Azure Site Recovery ...e-recovery/vmware-azure-install-linux-master-target.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools 📁 Windows Paths Windows First
Summary
The documentation is focused on installing a Linux master target server, but several steps require users to access Windows-based components, such as copying installer files and passphrases from Windows paths (e.g., C:\Program Files, C:\ProgramData). The process server and configuration server are assumed to be Windows machines, and instructions reference Windows file paths and actions before Linux alternatives. There are no Linux-native alternatives or parity instructions for these steps, and Windows tooling is referenced without mention of Linux equivalents.
Recommendations
  • Provide instructions for accessing installer files and passphrases from a Linux-based process/configuration server, if supported.
  • Include Linux file path examples and clarify if the process/configuration server must be Windows or if Linux is supported.
  • Add explicit notes about platform requirements for process/configuration servers and offer Linux alternatives or workarounds where possible.
  • Where Windows paths are referenced, also show the equivalent Linux steps (if available) or clarify that only Windows is supported for those components.
GitHub Create Pull Request
Site Recovery Common questions about VMware disaster recovery with Azure Site Recovery ...rticles/site-recovery/vmware-azure-common-questions.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation displays a moderate Windows bias: Windows paths and tools (e.g., PowerShell, C:\Program Files, C:\Temp) are mentioned first or exclusively in several places, and scripting/automation examples reference PowerShell before REST API or other cross-platform tools. Linux equivalents are sometimes present but often appear after Windows instructions, and some deployment/installation instructions reference Windows-specific folders or patterns without Linux parity.
Recommendations
  • Provide Linux/macOS examples and instructions alongside Windows, ensuring parity in all sections (e.g., installation paths, commands, scripting).
  • When referencing automation, include Bash/CLI or cross-platform SDK examples, not just PowerShell.
  • List Linux instructions before or alongside Windows instructions to avoid implicit prioritization.
  • Clarify when a tool or method is Windows-only, and offer Linux/macOS alternatives where possible.
  • Ensure all referenced folders/paths have Linux equivalents documented.
GitHub Create Pull Request
Site Recovery Prepare VMware VMs for reprotection and failback with Azure Site Recovery ...rticles/site-recovery/vmware-azure-prepare-failback.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation page shows a moderate Windows bias. Windows master target servers are mentioned first and described as the default. Instructions for adding a retention drive are detailed for Windows before Linux, and Windows-specific details (e.g., 'R volume') are given more prominence. The master target server is described as 'by default a Windows master target server,' and the process of adding a retention drive is more thoroughly explained for Windows. There is also mention of Windows tools and patterns before Linux equivalents. Linux instructions and references are present but less detailed and usually follow Windows examples.
Recommendations
  • Present Windows and Linux instructions in parallel, with equal detail and prominence.
  • Avoid language that implies Windows is the default or preferred option; clarify that both Windows and Linux are supported equally.
  • Expand Linux-specific instructions (e.g., for retention drive setup, disk formatting, and troubleshooting) to match the detail provided for Windows.
  • Where possible, provide examples for both platforms side-by-side, rather than listing Windows first.
  • Review and update any references to Windows-specific tools or patterns to ensure Linux equivalents are mentioned and explained.
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
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Missing Linux Example Windows First
Summary
The documentation page demonstrates a notable Windows bias. All command-line instructions use Windows-specific tools (cmd.exe, PowerShell, Windows paths like %PROGRAMDATA%), and anti-virus exclusions reference only Windows directories. There are no Linux or macOS equivalents or examples provided, despite the fact that VMware environments may include Linux servers. The documentation assumes the process server is always running on Windows, which may not be universally true.
Recommendations
  • Provide Linux/macOS equivalents for command-line instructions, including shell commands and file paths.
  • Clarify OS requirements for the process server, and explicitly state if only Windows is supported.
  • If Linux is supported, add anti-virus exclusion paths for common Linux distributions.
  • Offer PowerShell and Bash examples side-by-side where applicable.
  • Indicate whether tools like cdpcli.exe have Linux versions, and provide usage instructions if so.
GitHub Create Pull Request
Site Recovery Set up source settings for VMware disaster recovery to Azure with Azure Site Recovery ...n/articles/site-recovery/vmware-azure-set-up-source.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
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 primarily referencing Windows paths and tools, listing Windows-specific antivirus exclusions before Linux equivalents, and omitting Linux-specific instructions for several critical steps (such as configuration server setup and antivirus exclusions for non-Windows components). Linux examples are only provided for antivirus exclusions on the Linux Master Target, and even then, Windows registry exclusions are listed immediately after, with no Linux equivalent. The configuration server setup assumes a Windows VM and license activation, with no mention of Linux-based alternatives.
Recommendations
  • Provide parallel Linux instructions for configuration server setup, including any required dependencies, installation steps, and licensing considerations.
  • List Linux and Windows antivirus exclusions in separate, clearly labeled sections, and present them with equal prominence.
  • Include Linux-specific examples and paths for all relevant components, not just the Master Target.
  • Clarify whether the configuration server can be run on Linux, and if not, explain the limitation.
  • Add notes or links for Linux users regarding alternative tools or patterns where Windows-only steps are present.
GitHub Create Pull Request
Site Recovery Troubleshoot issues with the configuration server during disaster recovery of VMware VMs and physical servers to Azure by using Azure Site Recovery ...very/vmware-azure-troubleshoot-configuration-server.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. Windows paths, tools, and troubleshooting steps are frequently mentioned first or exclusively, such as references to C:\ProgramData, Internet Explorer, PsExec, and Windows licensing. Some troubleshooting instructions and examples are either Windows-only or presented before Linux equivalents. Linux steps are present in some sections, but not all, and Windows-specific tools (PsExec, Internet Explorer) are used without Linux alternatives. Some log file locations and service names are only described for Windows, and Linux users may need to infer or adapt steps.
Recommendations
  • Provide Linux/macOS equivalents for all Windows-specific tools and steps (e.g., alternatives to PsExec and Internet Explorer for proxy configuration).
  • List Linux log file locations and service names wherever Windows paths are mentioned.
  • Ensure Linux examples are presented alongside Windows examples, not only after or in separate sections.
  • Add explicit instructions for Linux/macOS users in all troubleshooting steps, especially where only Windows paths or commands are given.
  • Avoid using Windows-only terminology (e.g., 'elevated command prompt') without Linux equivalents (e.g., 'sudo' or root shell').
GitHub Create Pull Request
Site Recovery Troubleshoot Mobility Service push installation with Azure Site Recovery ...ite-recovery/vmware-azure-troubleshoot-push-install.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
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 notable Windows bias. Windows troubleshooting steps, registry edits, and service management are described in detail and often appear first. Windows-specific tools (e.g., regedit, net user, netsh, Task Manager, File Explorer, Group Policy) are referenced extensively, with step-by-step instructions and command-line examples. In contrast, Linux guidance is less detailed, sometimes only mentioning configuration file edits or service restarts without equivalent depth or examples. Some troubleshooting sections (e.g., VSS, WMI, network shares) are almost entirely Windows-centric, with minimal or no Linux-specific troubleshooting advice.
Recommendations
  • Provide Linux-first or side-by-side examples for every troubleshooting step, especially for credential, connectivity, and service management errors.
  • Include Linux equivalents for Windows tools (e.g., use 'id', 'sudo', 'systemctl', 'ss', 'firewalld', 'ufw', 'smbclient', etc.) and explain how to check and modify permissions, services, and network shares on Linux.
  • Expand Linux troubleshooting for agent installation failures, including log file locations, common error messages, and recovery steps.
  • Add parity for VSS and WMI sections by clarifying their Linux equivalents or noting if those steps are Windows-only.
  • Where Windows registry edits are described, provide Linux configuration file or command alternatives if applicable.
  • Ensure that Linux troubleshooting is as detailed and actionable as Windows guidance.
GitHub Create Pull Request
Site Recovery Troubleshoot failback in VMware VM disaster recovery with Azure Site Recovery ...covery/vmware-azure-troubleshoot-failback-reprotect.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation provides troubleshooting steps for both Windows and Linux VMs, but Windows scenarios are described with more detail and favorability. For example, Windows VMs are noted to reacquire static IPs automatically, while Linux users must manually reconfigure static IPs after failback. There are no Linux-specific troubleshooting commands or examples, and Windows scenarios (e.g., Windows Server 2008 R2 SP1) are mentioned explicitly, while Linux troubleshooting is less comprehensive.
Recommendations
  • Provide Linux-specific troubleshooting steps and examples, such as commands for checking/restarting services, restoring static IP configuration, and verifying network connectivity.
  • Include parity in examples for both Windows and Linux VMs when describing common issues and resolutions.
  • Mention Linux tools (e.g., systemctl, nmcli, ifconfig/ip) alongside Windows tools where relevant.
  • Clarify any differences in failback behavior between Windows and Linux VMs, and offer guidance for both platforms equally.
GitHub Create Pull Request
Site Recovery Troubleshoot VMware mobility agent health errors in Azure Site Recovery ...-recovery/vmware-troubleshoot-mobility-agent-health.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation page generally maintains parity between Windows and Linux, especially in log file locations and error messages. However, there is a subtle Windows bias: Windows paths are often listed after Linux, but error logs and examples frequently reference Windows-style paths and hostnames (e.g., C:\ paths, WIN- hostnames). Service names and restart instructions use Windows-centric terminology (e.g., 'Microsoft Azure RCM Proxy Agent'), with no explicit Linux service equivalents or commands. There are no PowerShell-only examples, but the troubleshooting steps and error logs lean toward Windows environments.
Recommendations
  • Explicitly include Linux/macOS service names and restart instructions alongside Windows equivalents.
  • Provide Linux command-line examples (e.g., systemctl, service) for restarting relevant services.
  • Balance error log examples to include both Linux and Windows scenarios.
  • Clarify any OS-specific steps, especially where service management differs.
GitHub Create Pull Request
Site Recovery Support matrix for VMware/physical disaster recovery in Azure Site Recovery. .../site-recovery/vmware-physical-azure-support-matrix.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits several Windows biases: Windows deployment options (PowerShell) are mentioned before or exclusively compared to Linux equivalents; the replication appliance is required to run Windows Server 2022, with no Linux alternative; configuration and management tasks reference Windows tools and roles (IIS, Active Directory, Group Policy) without Linux parallels; and example scripts or automation are PowerShell-only. Linux support is present for replicated workloads, but Linux administrators lack parity in deployment, management, and automation options.
Recommendations
  • Provide Linux-based deployment and management options for the replication appliance, or clarify why Windows-only is required.
  • Offer Linux shell (bash) or Ansible examples alongside PowerShell for automation and scripting tasks.
  • Document Linux equivalents for configuration steps (e.g., web server setup, service management) where Windows tools like IIS are referenced.
  • Explicitly state limitations for Linux users in sections where only Windows tools or OS are supported, and suggest workarounds or alternatives.
  • Ensure that Linux-related instructions are presented with equal prominence and detail as Windows instructions.
GitHub Create Pull Request
Site Recovery Scale VMware/physical disaster recovery with Azure Site Recovery ...cles/site-recovery/vmware-physical-large-deployment.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation demonstrates a Windows bias in several ways: PowerShell is the only automation example provided for triggering failover, Windows compliance is discussed in detail while Linux is only briefly mentioned, and troubleshooting and preparation steps focus on Windows tools and patterns. There are no Linux-specific examples or guidance for automation, compliance, or failover preparation, which may create friction for Linux users.
Recommendations
  • Provide equivalent Linux automation examples, such as using Azure CLI or REST API for triggering failover.
  • Expand compliance preparation guidance for Linux machines, including proactive steps and tools.
  • Include troubleshooting and best practices sections tailored for Linux environments.
  • Ensure that examples and instructions are presented in a cross-platform manner, not defaulting to Windows-first.
  • Reference Linux-specific documentation and tools where applicable.
GitHub Create Pull Request
Site Recovery Manage the Mobility agent for VMware/physical servers with Azure Site Recovery ...te-recovery/vmware-physical-manage-mobility-service.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page shows a moderate Windows bias. Windows-specific tools (PowerShell, Control Panel, MSIExec, VSS provider) are described in detail, with examples and scripts. The PowerShell update method is only shown for Windows, with no Linux equivalent. Uninstallation instructions are given for both platforms, but Windows instructions are more detailed and appear first. Manual update instructions are generic, but lack Linux-specific commands or examples. The VSS provider section is Windows-only, with no mention of Linux consistency mechanisms.
Recommendations
  • Add Linux-specific update instructions, including example commands for agent upgrade (e.g., using rpm, dpkg, or shell scripts).
  • Provide parity for automation: show how to update the Mobility agent on Linux via shell script or configuration management tools.
  • Include Linux-first or side-by-side examples for common tasks, not just Windows-first.
  • Clarify whether VSS provider or equivalent is needed/available for Linux, and provide relevant instructions.
  • Where Windows tools (PowerShell, MSIExec) are mentioned, offer Linux alternatives (bash, systemctl, package managers).
GitHub Create Pull Request
Site Recovery Azure Virtual Machines disaster recovery - High Churn support ...recovery/concepts-azure-to-azure-high-churn-support.md
Low Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation mentions supported operating systems for Enhanced Churn (Windows, then Linux distros), but does not provide any OS-specific examples, commands, or guidance. There is a subtle 'Windows first' bias in the support matrix, listing Windows before Linux and not specifying Linux versions for the standard High Churn (only for Enhanced Churn preview). No PowerShell or Windows tool bias is present, but Linux parity could be improved by clarifying supported Linux versions and providing OS-specific troubleshooting or configuration notes.
Recommendations
  • Explicitly list supported Linux distributions and versions for all churn support levels, not just Enhanced Churn preview.
  • Provide OS-specific guidance or troubleshooting steps for both Windows and Linux VMs, especially if there are differences in agent installation, configuration, or performance.
  • Ensure examples and screenshots are applicable to both Windows and Linux VMs, or clarify when steps differ.
  • Avoid listing Windows before Linux in support matrices unless there is a technical reason.
GitHub Create Pull Request
Site Recovery Manage Azure role-based access control in Azure Site Recovery ...very/site-recovery-role-based-linked-access-control.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation lists PowerShell (a Windows-centric tool) before Azure CLI and REST API in the 'Next steps' section, which subtly prioritizes Windows workflows. However, the main content is platform-neutral, focusing on Azure roles and permissions without OS-specific instructions or examples.
Recommendations
  • List Azure CLI before PowerShell in the 'Next steps' section, as CLI is cross-platform and more commonly used on Linux/macOS.
  • Explicitly state that all management tasks can be performed equally on Linux/macOS using Azure CLI or REST API.
  • Where examples are provided in future revisions, ensure parity by including both PowerShell and Azure CLI commands.
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
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation presents Windows failback behavior before Linux, and provides more detail for Windows disks in the failback section. However, both platforms are mentioned, and the core exclusion workflow is platform-neutral. No platform-specific commands or tools are referenced.
Recommendations
  • Present Linux and Windows failback information in parallel, with equal detail and clarity.
  • Add explicit examples or clarifications for Linux disk exclusion and failback, if there are unique steps or considerations.
  • Ensure that any screenshots or UI references are applicable to both Windows and Linux VMs, or note differences.
GitHub Create Pull Request
Site Recovery Enable accelerated networking for Azure VM disaster recovery with Azure Site Recovery ...azure-vm-disaster-recovery-with-accelerated-networking.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation presents Windows VM instructions and supported OS lists before Linux equivalents, but otherwise maintains parity in content and links. No Windows-specific tools (e.g., PowerShell) or examples are shown directly; both platforms are referenced with equal detail and external links for enabling Accelerated Networking.
Recommendations
  • Alternate the order of Windows and Linux sections, or present them in parallel to avoid implicit prioritization.
  • Explicitly state that both Windows and Linux are equally supported at the beginning of the relevant sections.
  • Ensure that any future examples or screenshots include both Windows and Linux scenarios if platform-specific tools are demonstrated.
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
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation demonstrates a mild Windows bias. In sections describing how to prepare accounts for Mobility service installation and how to connect to VMs after failover, Windows instructions and tooling (e.g., registry edits, Windows Firewall, RDP) are described first and in greater detail, with Linux instructions presented second and more briefly. Windows-specific tools and patterns (registry, firewall UI) are mentioned, while Linux instructions are less detailed and lack equivalent troubleshooting guidance.
Recommendations
  • Present Linux and Windows instructions in parallel, with equal detail and troubleshooting steps.
  • Include Linux-specific troubleshooting links and guidance for SSH connectivity after failover, similar to the Windows RDP troubleshooting section.
  • Provide examples of Linux account preparation (e.g., sudoers configuration, SSH key setup) with step-by-step instructions.
  • Mention Linux firewall configuration commands (e.g., ufw, firewalld) for enabling SSH, analogous to Windows Firewall steps.
  • Ensure that Linux examples are not always presented after Windows examples; alternate or present both together.
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
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page exhibits minor Windows bias by referencing Windows-specific concepts and links before Linux equivalents, and by omitting explicit Linux examples for key tasks such as connecting to failed-over VMs. For instance, the link to VM connection instructions points to a Windows-specific page, and there is no mention of Linux SSH connection steps or troubleshooting. The page does mention Linux VMs in the context of failover timing, but does not provide Linux-specific guidance for post-failover operations.
Recommendations
  • Include explicit instructions and links for connecting to Linux VMs via SSH after failover, alongside RDP instructions for Windows VMs.
  • Provide troubleshooting steps and references for common Linux connectivity issues post-failover.
  • Ensure that links to connection guides cover both Windows and Linux VM scenarios, or provide parallel links for each.
  • Review terminology and examples to ensure parity between Windows and Linux VM management tasks.
GitHub Create Pull Request
Site Recovery Set up disaster recovery after migration to Azure with Azure Site Recovery ...e-recovery/azure-to-azure-replicate-after-migration.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation presents Windows instructions and tools before Linux equivalents in several sections, such as agent installation and Mobility service removal. Windows-specific paths, GUI steps, and command-line tools (like MsiExec.exe) are described in detail, while Linux instructions are provided afterwards. The order and detail may create a perception that Windows is the primary or default platform.
Recommendations
  • Present Linux and Windows instructions in parallel or grouped sections, rather than listing Windows first.
  • Provide equal detail for Linux steps, including validation commands and troubleshooting tips.
  • Where possible, use cross-platform terminology and highlight differences only when necessary.
  • Include links to both Windows and Linux agent documentation in all relevant sections.
  • Consider a summary table for commands and steps for both platforms.
GitHub Create Pull Request
Site Recovery Troubleshoot connectivity for Azure to Azure disaster recovery with Azure Site Recovery ...ry/azure-to-azure-troubleshoot-network-connectivity.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation generally avoids OS-specific commands, but in the proxy troubleshooting section, Windows (Internet Explorer) is mentioned before Linux (/etc/environment) for proxy autodetection, and the Windows path is listed before the Linux path for ProxyInfo.conf. There are no explicit Linux shell or Windows PowerShell examples, but the ordering and references show a subtle Windows-first bias. No critical steps are Windows-only, and Linux users are given equivalent information, though sometimes after the Windows details.
Recommendations
  • Present Linux and Windows instructions in parallel or alternate the order to avoid implicit prioritization.
  • Where both OSes are supported, use neutral phrasing (e.g., 'On Linux, ... On Windows, ...') and avoid listing Windows first by default.
  • Add explicit Linux troubleshooting steps or screenshots where Windows-specific tools (like Internet Explorer) are referenced.
  • Consider including command-line examples for both platforms if relevant (e.g., checking proxy settings).
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
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation mentions credential requirements for both Linux and Windows OS, but lists Linux (root) credentials first, followed by Windows (admin) credentials. No examples, commands, or tooling are specific to Windows or Linux; the process is described in a platform-neutral way. There are no PowerShell-heavy sections, Windows-only tools, or missing Linux examples. The only minor bias is the order in which credential requirements are listed.
Recommendations
  • Consider listing credential requirements for both Linux and Windows OS in parallel or clarify that either is acceptable depending on the source VM.
  • If platform-specific steps are required (e.g., manual Mobility Service installation), provide explicit instructions for both Linux and Windows.
  • Add links to platform-specific troubleshooting or best practices for both Linux and Windows VMs.
GitHub Create Pull Request
Site Recovery Set up failover and failback for physical servers with Site Recovery ...s/site-recovery/physical-to-azure-failover-failback.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a mild Windows bias. While it mentions that both Windows and Linux operating systems are supported in replication groups, the examples, terminology, and linked resources predominantly reference Windows environments (e.g., Windows Server, Windows-specific Azure documentation, and vCenter/ESXi scenarios). There are no explicit Linux-specific instructions, examples, or troubleshooting steps, and Windows terminology is used first or exclusively in several places.
Recommendations
  • Add explicit Linux examples and instructions for common failover/failback scenarios, such as connecting to Linux VMs after failover.
  • Include troubleshooting steps or notes for Linux-specific issues (e.g., disk UUID conflicts, networking configuration).
  • Reference Linux documentation and tools where appropriate, such as linking to Azure Linux VM guides alongside Windows guides.
  • Ensure parity in terminology and ordering, mentioning Linux wherever Windows is mentioned, and providing examples for both.
  • Clarify any differences in process or requirements for Linux VMs, especially in sections about master target servers and reprotection.
GitHub Create Pull Request
Site Recovery Quickstart to create an Azure Recovery Services vault using Bicep. ...rticles/site-recovery/quickstart-create-vault-bicep.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for all key steps, but PowerShell is given equal prominence to CLI, and no Linux/macOS-specific shell examples (e.g., Bash scripts) or notes are provided. The CLI examples are cross-platform, but PowerShell is Windows-centric, and its inclusion may suggest a Windows-first audience. There is no explicit mention of Linux/macOS environments or their nuances.
Recommendations
  • Clarify that Azure CLI commands work on Windows, Linux, and macOS, and recommend CLI for cross-platform usage.
  • Add a note for Linux/macOS users, highlighting that PowerShell examples are Windows-centric and that CLI is preferred for non-Windows platforms.
  • Consider including Bash script snippets or terminal screenshots for Linux/macOS users to reinforce parity.
  • Explicitly mention prerequisites for Linux/macOS (e.g., installing Azure CLI) if relevant.
GitHub Create Pull Request
Site Recovery Quickstart: Use Terraform to create an Azure Recovery Services vault ...les/site-recovery/quickstart-create-vault-terraform.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell instructions for verifying results, but PowerShell is given equal prominence as CLI, and the CLI instructions use syntax compatible with Bash (Linux/macOS) but do not explicitly mention Linux or macOS. There are no explicit Linux/macOS-specific examples or troubleshooting steps, and PowerShell (a Windows-centric tool) is featured as a primary method. No Linux-specific tools or shell examples (e.g., zsh, fish) are provided, and the documentation does not clarify cross-platform compatibility for commands.
Recommendations
  • Explicitly state that Azure CLI commands work on Linux, macOS, and Windows, and provide example shell environments (e.g., Bash, zsh).
  • Add a note clarifying that PowerShell is available on Linux/macOS, or provide Bash-only instructions for Linux/macOS users.
  • Include troubleshooting steps or links relevant to Linux/macOS environments.
  • If possible, order the verification tabs with Azure CLI (cross-platform) first, and PowerShell second.
  • Mention any OS-specific considerations for Terraform usage, such as file permissions or environment setup.
GitHub Create Pull Request
← Previous Page 8 of 10 Next →