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 76-100 of 232 flagged pages
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-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell is the only CLI tool shown for scripting and automation, with no Bash, Azure CLI, or Linux-native examples. Windows terminology and links (e.g., proximity placement groups documentation under /windows/, PowerShell module installation) are presented first or exclusively. While the portal instructions are cross-platform, all automation and scripting guidance is Windows-centric, creating friction for Linux/macOS users.
Recommendations
  • Provide equivalent Azure CLI (az) commands for all PowerShell examples, especially for disk replication, resource group, and proximity placement group operations.
  • Include Bash script snippets for common tasks to support Linux/macOS automation.
  • Reference proximity placement group documentation under a neutral or Linux path, not just /windows/.
  • Clarify that PowerShell Core (pwsh) is cross-platform, and provide installation instructions for Linux/macOS.
  • Add explicit guidance for Linux administrators, such as using Azure CLI on Linux for disaster recovery setup.
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-12 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, with troubleshooting steps, tools, and examples almost exclusively referencing Windows features (Event Viewer, PowerShell, Windows logs, VSS, Integration Services). Linux is mentioned only briefly and without concrete troubleshooting guidance or examples, making it difficult for Linux users to follow or adapt the instructions.
Recommendations
  • Add explicit troubleshooting steps and log locations for Linux-based Hyper-V VMs, including relevant commands and tools (e.g., journalctl, systemd, Linux equivalents for VSS/app-consistency).
  • Provide Linux-specific examples for checking replication health, service status, and connectivity.
  • Include parity for PowerShell commands with Bash or shell commands where applicable.
  • Clarify which steps are Windows-only and offer Linux alternatives or note limitations.
  • Expand documentation on enabling and verifying app-consistency for Linux VMs, with links to detailed Linux guidance.
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
Medium Priority View Details →
Scanned: 2026-01-12 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 presents Windows instructions first, uses Windows-specific tools (e.g., registry edits, cspsconfigtool.exe), and provides explicit command-line examples for Windows (REG ADD) but omits equivalent Linux command-line examples. Windows firewall configuration is described in detail, while Linux firewall or security configuration is not mentioned. The anti-virus exclusion path is Windows-only. The use of cspsconfigtool.exe for Linux setup is described, but its availability and usage on Linux are not clarified.
Recommendations
  • Provide Linux shell command examples for editing /etc/ssh/sshd_config and restarting sshd.
  • Clarify whether cspsconfigtool.exe is available for Linux administrators or provide a Linux-native alternative/tool.
  • Include Linux firewall configuration steps (e.g., iptables, firewalld, ufw) analogous to Windows Firewall instructions.
  • Add anti-virus exclusion guidance for popular Linux anti-virus solutions.
  • Present Linux and Windows instructions in parallel or alternate order to avoid Windows-first bias.
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
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page shows a moderate Windows bias. While it covers VMware environments (which can host both Windows and Linux VMs), it repeatedly references Windows-specific features and support, such as detailed support for Windows Server EFI virtual machines and boot types, with limited or no equivalent detail for Linux EFI support. There are no examples or instructions specific to Linux, nor are Linux-specific tools or troubleshooting steps mentioned. Windows scenarios (e.g., Windows Server EFI support) are described in detail, while Linux is only referenced generically. No Linux/Powershell/CLI commands or examples are provided, and the documentation does not clarify Linux-specific limitations or best practices.
Recommendations
  • Add explicit examples and guidance for Linux virtual machines, especially regarding EFI boot support, failover, and failback.
  • Clarify any differences in Azure Site Recovery support or limitations for Linux VMs, including supported distributions, kernel versions, and disk/boot configurations.
  • Include troubleshooting steps and recommendations for Linux VMs, such as log file locations, common issues, and recovery procedures.
  • Provide parity in documentation for both Windows and Linux, ensuring that Linux users can follow all steps and understand any platform-specific caveats.
  • If there are CLI or script examples, include both Windows (PowerShell) and Linux (bash/CLI) variants.
GitHub Create Pull Request
Site Recovery Troubleshoot replication issues for disaster recovery of VMware virtual machines and physical servers to Azure by using Azure Site Recovery ...site-recovery/vmware-azure-troubleshoot-replication.md
Medium Priority View Details →
Scanned: 2026-01-12 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. Troubleshooting steps and log file locations are consistently given using Windows paths (e.g., C:\Program Files...), and command-line instructions use Windows tools (cmd, net stop/start). There are no Linux-specific instructions, examples, or log locations, despite the fact that physical servers and VMware VMs may run Linux. Folder permission troubleshooting is described only for Windows (IUSR user, Windows-style paths).
Recommendations
  • Add Linux-specific troubleshooting steps, including log file locations (e.g., /var/log/...), service management commands (systemctl, service), and folder permission guidance (chown, chmod).
  • Provide parallel examples for Linux environments wherever Windows paths, commands, or user accounts are referenced.
  • Clarify which steps apply to Windows-only scenarios and which are relevant for Linux, to avoid confusion.
  • Include notes or sections for common Linux distributions (Ubuntu, CentOS, RHEL) where relevant.
GitHub Create Pull Request
Site Recovery About the Mobility service for disaster recovery of VMware VMs and physical servers with Azure Site Recovery | Microsoft Docs ...-recovery/vmware-physical-mobility-service-overview.md
Medium 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 frequently presents Windows examples and instructions before Linux equivalents, uses Windows-centric paths and tools (e.g., C:\Program Files, command prompt, .exe installers), and describes UI-based installation primarily for Windows. Linux instructions are present and reasonably detailed, but are often secondary and sometimes require manual steps or additional downloads. Some sections (e.g., antivirus exclusions, installer repository paths) use Windows paths and terminology even when describing Linux prerequisites.
Recommendations
  • Present Linux and Windows instructions in parallel, or alternate which OS is shown first in each section.
  • Provide Linux-specific UI installation guidance if available, or clarify if UI installation is Windows-only.
  • Use OS-neutral language and paths when describing shared concepts (e.g., installer repository locations, antivirus exclusions).
  • Ensure that all manual steps required for Linux (such as downloading installers) are clearly documented and as streamlined as possible.
  • Add explicit notes when a feature or step is Windows-only, and offer Linux alternatives or workarounds.
  • Include Linux-specific troubleshooting and best practices where relevant.
GitHub Create Pull Request
Site Recovery Fail back Azure VMware Solution VMsfrom Azure with Azure Site Recovery ...b/main/articles/site-recovery/avs-tutorial-failback.md
Medium 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 contains a notable Windows bias, specifically in the section discussing VMware tools management during failover/failback. Only Windows VMs are mentioned, with no reference to Linux VM behavior or requirements. There are no Linux-specific examples, notes, or troubleshooting steps, which may leave Linux users uncertain about the process or any differences they should be aware of.
Recommendations
  • Add a note clarifying the behavior of VMware tools for Linux VMs during failover and failback, including any differences or additional steps required.
  • Provide troubleshooting tips or considerations for Linux VMs, especially regarding agent registration and reprotection.
  • Ensure parity in documentation by including Linux-specific examples or explicitly stating when steps are identical for both Windows and Linux VMs.
GitHub Create Pull Request
Site Recovery Enable replication of encrypted Azure VMs in Azure Site Recovery ...https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/azure-to-azure-how-to-enable-replication-cmk-disks.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides a detailed walkthrough for enabling replication of encrypted Azure VMs, but the only command-line example is a PowerShell script. There are no Bash, Azure CLI, or Linux/macOS shell equivalents for managing replication or disks. The FAQ specifically instructs users to use PowerShell, which is a Windows-centric tool, and does not mention alternatives for Linux/macOS users. This creates friction for users on non-Windows platforms.
Recommendations
  • Add Azure CLI examples alongside PowerShell for all command-line instructions.
  • Explicitly mention cross-platform options (e.g., Bash, Azure CLI) where PowerShell is referenced.
  • Clarify whether the described tasks can be performed via the Azure Portal or REST API, and provide links or examples.
  • Include notes on how Linux/macOS users can install and use Azure CLI for these operations.
GitHub Create Pull Request
Site Recovery Replicate Azure Stack Hub to Azure using Azure Site Recovery ...in/articles/site-recovery/azure-stack-site-recovery.md
Medium 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 moderate Windows bias. Windows operating systems are listed first in compatibility tables, and Windows-specific instructions (such as registry edits, firewall configuration via GUI tools, and references to Volume Shadow Copy Service) are more detailed and appear before Linux equivalents. Windows tools and patterns (e.g., REG ADD, wf.msc, GPO) are mentioned explicitly, while Linux instructions are less detailed and lack example commands. There are no PowerShell scripts, but the overall pattern and detail favor Windows users.
Recommendations
  • Provide Linux command-line examples for steps such as opening firewall ports, editing sshd_config, and restarting services.
  • List Linux operating systems and instructions before or alongside Windows, not after.
  • Include parity in troubleshooting and automation guidance for Linux (e.g., using shell scripts, systemctl commands).
  • Reference Linux-specific backup and snapshot mechanisms where applicable, not only Windows VSS.
  • Ensure diagrams and screenshots include Linux scenarios where relevant.
GitHub Create Pull Request
Site Recovery Common questions about Azure virtual machine disaster recovery with Azure Site Recovery ...icles/site-recovery/azure-to-azure-common-questions.md
Medium Priority View Details →
Scanned: 2026-01-12 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 exhibits several forms of Windows bias: Windows-specific features (such as ADE and VSS) are described in detail, often before or instead of Linux equivalents. PowerShell is frequently referenced as the primary automation method, with no mention of Bash, CLI, or Linux-native tooling. Examples and instructions for Linux users are sparse or absent, and some features (e.g., shared disks) are explicitly unsupported for Linux VMs. Windows-centric terminology and tools are prioritized throughout, creating friction for Linux/macOS users.
Recommendations
  • Provide equivalent Linux CLI or Bash examples alongside PowerShell instructions.
  • Explicitly document Linux support and limitations for all major features, including disk encryption and shared disks.
  • Reference Azure CLI and REST API methods where possible, not just PowerShell.
  • Clarify when features are Windows-only, and suggest alternative approaches for Linux users.
  • Include Linux-specific troubleshooting and automation guidance.
  • Ensure that Linux-related documentation is as detailed and prominent as Windows guidance.
GitHub Create Pull Request
Site Recovery Enable replication for private endpoints in Azure Site Recovery ...e-to-azure-how-to-enable-replication-private-endpoints.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias by exclusively referencing the Azure portal and Azure PowerShell for configuration steps, without mentioning or providing examples for Linux/macOS command-line tools (such as Azure CLI). All screenshots and step-by-step instructions are based on the Azure portal UI, which is consistent across platforms but often assumes a Windows-centric workflow. There are no Linux-specific instructions, nor is Azure CLI usage suggested, which may create friction for users who prefer or require command-line automation on Linux/macOS.
Recommendations
  • Add equivalent Azure CLI commands for each major configuration step (e.g., creating private endpoints, DNS zones, role assignments).
  • Explicitly mention that all steps can be performed on Linux/macOS using Azure CLI, and provide links to relevant CLI documentation.
  • Include at least one example workflow using Azure CLI for Linux/macOS users.
  • Where PowerShell is referenced, provide a parallel Azure CLI example.
  • Clarify that the Azure portal is accessible from any OS, but command-line automation is available for all platforms.
GitHub Create Pull Request
Site Recovery Enable replication for encrypted Azure VMs in Azure Site Recovery ...ry/azure-to-azure-how-to-enable-replication-ade-vms.md
Medium Priority View Details →
Scanned: 2026-01-12 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 page demonstrates a notable Windows bias, particularly in the sections related to copying disk encryption keys. The only provided script for key copying is a PowerShell script, with explicit instructions to use Windows PowerShell. There are no Linux/macOS shell or CLI examples, nor is there mention of cross-platform alternatives. The instructions and troubleshooting steps assume use of Windows tools and patterns, making it harder for Linux/macOS users to follow the guide.
Recommendations
  • Provide equivalent Bash/CLI scripts or Azure CLI commands for copying disk encryption keys, ensuring Linux/macOS users can perform the task without needing Windows PowerShell.
  • Explicitly state cross-platform options for all automation steps, including REST API and CLI alternatives.
  • Reorder examples so that platform-neutral methods (e.g., Azure Portal, REST API, Azure CLI) are presented before or alongside Windows-specific methods.
  • Add troubleshooting steps relevant to Linux/macOS environments, such as permissions issues encountered when using Azure CLI or Bash scripts.
GitHub Create Pull Request
Site Recovery Support Matrix for Azure VM Disaster Recovery with Azure Site Recovery ...rticles/site-recovery/azure-to-azure-support-matrix.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. Windows operating systems are listed first and in more detail. Azure PowerShell is referenced repeatedly as the main automation method, with no Linux CLI or Bash alternatives provided. Key instructions (such as cross-subscription cache storage setup and disk exclusion) are PowerShell-centric, and there are no Linux-specific command examples or guidance for equivalent workflows. While Linux support is described in detail for OS/kernel compatibility, operational steps and tooling are Windows/PowerShell-focused.
Recommendations
  • Provide Azure CLI (az) examples for all PowerShell-based instructions, especially for disk exclusion and cross-subscription cache storage setup.
  • Include Bash or shell script equivalents where automation is discussed.
  • List Linux operating systems and workflows before or alongside Windows in relevant sections.
  • Add explicit guidance for Linux users on how to perform common tasks (e.g., agent upgrades, disk management) using Linux-native tools.
  • Clarify any limitations or workarounds for Linux users where Azure CLI is not supported.
GitHub Create Pull Request
Site Recovery Troubleshoot Azure VM replication in Azure Site Recovery - other issues ...es/site-recovery/azure-to-azure-troubleshoot-errors.md
Medium Priority View Details →
Scanned: 2026-01-12 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 displays a moderate Windows bias in several areas. Windows solutions and tools (such as Services console, Internet Explorer, and Windows update processes) are often mentioned first or exclusively, with Linux equivalents provided later or in less detail. Some troubleshooting steps (e.g., COM+ and VSS errors) are Windows-specific without Linux alternatives. Proxy detection references Internet Explorer for Windows, while Linux guidance is less detailed. In certificate troubleshooting, Windows instructions precede Linux, and external links are Windows-centric.
Recommendations
  • Present Windows and Linux troubleshooting steps side-by-side or in parallel tabs, rather than Windows first.
  • Include Linux/macOS equivalents for all Windows-specific instructions, especially for service management (e.g., systemctl commands for COM+ and VSS equivalents).
  • Avoid referencing Windows-only tools (like Internet Explorer) without mentioning Linux alternatives (such as checking proxy settings in /etc/environment or using curl/wget for connectivity tests).
  • Provide links to Linux documentation for certificate management, service management, and update processes.
  • Ensure all error codes and workarounds have both Windows and Linux guidance, or explicitly state if an issue is Windows-only.
GitHub Create Pull Request
Site Recovery Troubleshoot replication of Azure VMs with Azure Site Recovery ...te-recovery/azure-to-azure-troubleshoot-replication.md
Medium Priority View Details →
Scanned: 2026-01-12 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 demonstrates a moderate Windows bias. Many troubleshooting steps and examples reference Windows-specific tools, paths, and commands (e.g., PowerShell, VSS, Windows service names, and Windows file paths) before or instead of Linux equivalents. Instructions for disk exclusion explicitly mention PowerShell, while Linux alternatives are not provided. Troubleshooting logs and service restarts are described in detail for Windows, with Linux steps often mentioned only briefly or as an afterthought. Some error resolution steps (e.g., VSS troubleshooting) are Windows-only, and Linux users may need to infer or research their own solutions.
Recommendations
  • Provide Linux-specific command-line examples (e.g., Bash, CLI) alongside PowerShell instructions.
  • Include Linux file paths and service names in troubleshooting steps, not just Windows equivalents.
  • Offer parity in error troubleshooting for Linux (e.g., alternatives to VSS, common Linux replication issues).
  • Ensure that instructions for tasks like disk exclusion or service restarts are given for both Windows and Linux, with equal detail.
  • Where third-party tools are referenced (e.g., AzCopy), clarify usage for both platforms.
GitHub Create Pull Request
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-12 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, especially in the sections addressing stale Site Recovery configurations. The only provided script for cleanup is a PowerShell (.ps1) script, with no Linux/bash equivalent or instructions for Linux/macOS users. While disk initialization is covered for both Windows and Linux, critical troubleshooting steps (removing stale configurations) rely solely on Windows tooling and scripting.
Recommendations
  • Provide bash or Azure CLI equivalents for the PowerShell cleanup script, or document how Linux/macOS users can perform the same operation.
  • Explicitly mention how Linux/macOS users can run the provided PowerShell script (e.g., using Azure Cloud Shell, PowerShell Core on Linux/macOS, or alternative methods).
  • Ensure all troubleshooting steps include both Windows and Linux/macOS instructions where applicable.
  • Add links to Linux/macOS documentation for resource lock management and other Azure operations.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by providing detailed, step-by-step instructions and links for preparing Windows machines, including PowerShell usage and Windows Firewall configuration, while Linux preparation is covered in only two brief bullet points. Windows tools and patterns (RDP, WinHTTP proxy, Windows Firewall, Windows Update) are mentioned explicitly and in detail, whereas Linux equivalents (SSH, firewall configuration) are not elaborated. Windows examples and instructions are presented first and in greater depth, with Linux guidance lacking parity.
Recommendations
  • Expand the Linux preparation section to include detailed steps, such as configuring SSH, setting up Linux firewall rules (e.g., using ufw, firewalld, or iptables), and verifying required services.
  • Provide links to relevant Azure documentation for Linux VM preparation, similar to those given for Windows.
  • Include Linux-specific troubleshooting tips (e.g., SELinux/AppArmor, SSH key management, package updates) analogous to the Windows update advice.
  • Offer example commands for Linux (e.g., systemctl enable ssh, ufw allow ssh) and clarify how to enable remote access.
  • Ensure parity in the depth and order of instructions for both Windows and Linux, possibly by presenting OS sections side-by-side or in parallel structure.
GitHub Create Pull Request
Site Recovery Configure Mobility Service Proxy Settings for Azure to Azure Disaster Recovery | Microsoft Docs ...-recovery/configure-mobility-service-proxy-settings.md
Medium 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 page demonstrates a Windows-first bias in several areas: Windows examples and tools (Internet Explorer, psexec) are described before Linux equivalents, and Windows-specific instructions are more detailed. The use of Windows tools (Internet Explorer, psexec) is mentioned explicitly, while Linux instructions are more generic and lack step-by-step detail. There is also a slight emphasis on Windows environment variables and file paths before Linux ones.
Recommendations
  • Provide step-by-step instructions for configuring proxy settings on Linux, similar to the Windows example (e.g., how to edit /etc/environment or /etc/profile for proxy variables).
  • Include Linux-specific tools or commands (such as export commands, nano/vim usage, or systemctl reload instructions) where Windows tools like psexec and Internet Explorer are referenced.
  • Present Windows and Linux instructions in parallel sections or side-by-side, rather than listing Windows first.
  • Clarify any differences in proxy configuration behavior between Windows and Linux Mobility Service agents.
  • Add troubleshooting steps or common issues for Linux users, as is often done for Windows.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exhibits a moderate Windows bias. Several features (shared disks, 'Create a new VM' flow) are explicitly supported only for Windows OS, with Linux support missing or deferred. Windows is mentioned first in support matrices and feature lists. There are no Linux-specific examples or guidance for migration, and tooling references (PowerShell, CLI) are generic, not showing parity for Linux users. The lack of Linux examples and the prioritization of Windows features create friction for Linux users.
Recommendations
  • Provide Linux-specific examples and step-by-step instructions for migration and configuration tasks.
  • Clarify CLI commands and workflows for Linux environments, especially where PowerShell is referenced.
  • Explicitly state timelines or workarounds for missing Linux support in critical features (e.g., 'Create a new VM' flow).
  • List Linux and Windows support equally in matrices and feature lists, avoiding Windows-first ordering.
  • Add troubleshooting and guidance for Linux users where features are Windows-only.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation demonstrates a Windows bias by referencing Windows-specific tools (e.g., Services.msc, World Wide Web Publishing Service), browser instructions focused on Microsoft Edge, and omitting Linux/macOS equivalents for appliance management and service operations. No Linux or macOS commands or patterns are provided for tasks such as restarting services or clearing browser cache, and Windows terminology appears first and exclusively.
Recommendations
  • Provide Linux/macOS equivalents for service management (e.g., systemctl or service commands for restarting web services).
  • Include instructions for clearing cache in popular Linux/macOS browsers (e.g., Firefox, Chrome, Safari).
  • Mention cross-platform alternatives to Services.msc and clarify how Linux users can perform necessary operations.
  • Ensure examples and instructions are presented in a platform-neutral manner or include both Windows and Linux/macOS steps side-by-side.
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-12 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 demonstrates a notable Windows bias. PowerShell is presented as the only CLI method for manual appliance setup, with no Linux shell or cross-platform alternatives. Registry and group policy checks are exclusively Windows-specific, and all troubleshooting and configuration steps reference Windows tools and patterns. There are no Linux/macOS command-line examples or instructions for users who may wish to deploy or manage the appliance from non-Windows environments. The order of presentation also places Windows-centric methods and requirements first.
Recommendations
  • Provide equivalent Linux/macOS shell scripts or CLI instructions for appliance setup and registration.
  • Clarify whether the OVF template can be deployed and managed from Linux-based hypervisors or environments, and include relevant steps.
  • Document Linux/macOS-specific prerequisites, troubleshooting, and configuration checks (e.g., system requirements, agent installation, proxy configuration).
  • Where registry or group policy checks are mentioned, add notes or alternatives for Linux-based appliances (if supported), or explicitly state Windows-only requirements.
  • Offer parity in examples and screenshots for Linux environments where applicable.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a Windows bias in several areas. Windows VM connection instructions are listed first and in greater detail, with explicit references to Windows Firewall, RDP, and Windows Update, while Linux instructions are brief and lack comparable troubleshooting or configuration detail. Windows-specific tools and patterns (e.g., SAN policy, Windows Firewall, RDP) are mentioned without Linux equivalents. There are also notes and troubleshooting links that are Windows-centric, and Linux users are not provided with parity in example depth or guidance.
Recommendations
  • Provide Linux connection instructions with equal detail, including troubleshooting steps (e.g., SSH service status, SELinux/AppArmor, Linux firewall configuration, common SSH issues).
  • Include Linux-first or at least parallel examples for configuration and failover/failback steps, not just Windows-first ordering.
  • Mention Linux equivalents for Windows-specific tools and settings (e.g., explain how to check and configure firewall rules for SSH, how to handle disk mounting and boot diagnostics on Linux).
  • Add troubleshooting links and resources for Linux VMs similar to those provided for Windows.
  • Avoid Windows-centric notes unless a Linux equivalent is also provided.
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-12 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 explicit PowerShell commands for force-deleting the vault, with no equivalent Azure CLI or Bash examples for Linux/macOS users. The only programmatic example is Windows-centric, and references to PowerShell modules and cmdlets are given in the 'Next steps' section. No Linux-native tools or cross-platform alternatives are mentioned, and the structure implicitly prioritizes Windows/PowerShell approaches.
Recommendations
  • Add Azure CLI examples for deleting the vault and its dependencies, as Azure CLI is cross-platform.
  • Include Bash script snippets for Linux/macOS users where appropriate.
  • Reference Azure CLI documentation alongside PowerShell cmdlet documentation in the 'Next steps' section.
  • Clarify that PowerShell Core is available on Linux/macOS, if PowerShell must be used, and provide installation guidance.
  • Reorder or parallelize examples so that Windows and Linux/macOS approaches are presented equally.
GitHub Create Pull Request
Site Recovery Exclude disks from replication with Azure Site Recovery ...in/articles/site-recovery/exclude-disks-replication.md
Medium Priority View Details →
Scanned: 2026-01-12 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. All detailed examples use Windows VMs, Windows disk naming conventions, and Windows-specific tools (e.g., diskmgmt.msc, drive letters like C:\, D:\, F:\, and references to pagefile.sys and SQL Server on Windows). There are no Linux VM examples, no Linux disk management instructions, and no mention of Linux-specific patterns (e.g., mount points, /dev/sdX, or Linux swap files). Even when Linux is mentioned (e.g., failback behavior), it is only in passing and not illustrated with practical steps or screenshots.
Recommendations
  • Add parallel examples for Linux VMs, including disk exclusion, failover, and failback scenarios.
  • Show Linux disk management steps (e.g., using lsblk, parted, or fdisk) for adding and formatting disks after failover.
  • Include Linux-specific file system and swap file exclusion scenarios (e.g., excluding /swapfile or /var/tmp).
  • Provide SQL Server on Linux instructions (if supported), or examples for other common Linux workloads.
  • Use generic terminology alongside Windows-specific terms (e.g., 'mount point' as well as 'drive letter').
  • Add screenshots or command-line examples relevant to Linux (e.g., using Azure CLI, SSH, etc.).
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-12 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 for Azure Site Recovery feature updates demonstrates a moderate Windows bias. Several updates and features are described exclusively for Windows Server environments, such as Windows Server Failover Clusters (WSFC) and PowerShell support, with no equivalent Linux clustering or automation examples. Windows OS support is often mentioned first or exclusively, while Linux support is only referenced in preview or as a secondary note. There are no Linux-specific tools, patterns, or examples provided for key features, and PowerShell is highlighted as a supported automation method without mention of Bash, CLI, or Linux-native alternatives.
Recommendations
  • Provide Linux-specific examples and guidance for feature parity, especially for clustering and automation scenarios.
  • Mention Linux tools (e.g., Bash, shell scripts, Ansible) and Azure CLI usage alongside PowerShell.
  • Ensure that OS support matrices and salient features explicitly list Linux support where available.
  • When introducing new features, present Windows and Linux support status together, rather than Windows-first.
  • Add documentation or links for Linux equivalents to Windows Server Failover Clusters, such as Pacemaker or Corosync clusters.
GitHub Create Pull Request
← Previous Page 4 of 10 Next →