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 251-275 of 864 flagged pages
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/site-recovery-deployment-planner.md ...cles/site-recovery/site-recovery-deployment-planner.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exhibits a strong Windows bias. All instructions, prerequisites, and examples assume the use of Windows Server or Windows PC, with no mention of Linux-based alternatives for running the Deployment Planner tool. Required dependencies (such as .NET Framework and Visual C++ Redistributable) are Windows-specific, and the report generation process requires Excel on Windows. There are no examples or guidance for Linux users, nor is there any indication that the tool can be run on Linux systems.
Recommendations
  • Clarify whether the Deployment Planner tool can be run on Linux systems. If not, explicitly state Windows-only support and provide rationale.
  • If possible, develop and document a Linux-compatible version of the Deployment Planner tool.
  • Provide alternative instructions for Linux users, such as running the tool in a Windows VM or container on Linux hosts.
  • List Linux equivalents for required dependencies (e.g., Mono for .NET applications, LibreOffice for Excel reports) if feasible.
  • Include examples and step-by-step instructions for Linux environments, or at least acknowledge the lack of support and suggest workarounds.
GitHub Create Pull Request
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/replication-appliance-support-matrix.md .../site-recovery/replication-appliance-support-matrix.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exhibits a strong Windows bias: all operating system requirements, folder paths, and configuration instructions are exclusively for Windows Server. There are no Linux equivalents or examples, and all tooling and folder exclusions reference Windows-specific locations and patterns. The documentation does not mention or support Linux-based appliances, nor does it provide parity for Linux administrators.
Recommendations
  • Explicitly state whether Linux-based replication appliances are supported or not. If not supported, clarify this early in the documentation.
  • If Linux appliances are supported, provide equivalent requirements, folder paths, and antivirus exclusions for common Linux distributions.
  • Include Linux-specific examples and instructions where applicable, such as using Linux firewalls, SELinux/AppArmor, and Linux-based antivirus exclusions.
  • Mention Linux tools and patterns alongside Windows ones, or provide a comparison table for cross-platform administrators.
  • Ensure that any group policy or IIS references are either matched with Linux equivalents or clearly marked as Windows-only.
GitHub Create Pull Request
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/transport-layer-security.md ...ain/articles/site-recovery/transport-layer-security.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exclusively focuses on Windows environments, providing only Windows registry and KB article instructions, and references to Windows-specific components (SChannel, .NET Framework). There are no examples, instructions, or mentions of Linux or cross-platform scenarios, despite Azure Site Recovery supporting Linux workloads.
Recommendations
  • Add equivalent instructions for enabling and verifying TLS 1.2 on supported Linux distributions, including relevant configuration files (e.g., OpenSSL, libssl, system-wide TLS settings).
  • Include Linux-specific troubleshooting steps for TLS-related failures in Azure Site Recovery.
  • Reference Linux documentation and tools alongside Windows resources, ensuring parity in guidance.
  • Clearly indicate platform-specific sections and provide cross-links between Windows and Linux instructions.
  • Mention any Azure Site Recovery limitations or differences in TLS support for Linux workloads.
GitHub Create Pull Request
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/site-recovery-ipconfig-cmdlet-parameter-deprecation.md ...ttps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/site-recovery-ipconfig-cmdlet-parameter-deprecation.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 examples, which are primarily associated with Windows environments. There are no references to Linux-native tools, Bash, or cross-platform scripting alternatives. The guidance assumes users are working in PowerShell, and does not provide parity for Linux users or those using Azure CLI.
Recommendations
  • Include equivalent examples using Azure CLI commands, which are cross-platform and commonly used on Linux.
  • Add notes or sections clarifying how Linux users can perform the same operations, including any prerequisites or differences.
  • Mention that Azure PowerShell is available on Linux and macOS, but also provide Bash/CLI alternatives for users who prefer native Linux tooling.
  • Ensure that future documentation provides both PowerShell and CLI/Bash examples side-by-side, or links to Linux-specific guidance.
GitHub Create Pull Request
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/vmware-azure-set-up-process-server-scale.md ...e-recovery/vmware-azure-set-up-process-server-scale.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates Windows bias by exclusively referencing Windows-based installation tools (UnifiedSetup.exe, MicrosoftAzureSiteRecoveryUnifiedSetup.exe), providing only Windows command-line examples (using .exe files and Windows-style paths), and omitting any mention of Linux equivalents or instructions for deploying process servers on Linux. There is no guidance for Linux administrators, nor are Linux commands, file paths, or installation methods discussed.
Recommendations
  • Add explicit instructions and examples for installing and configuring process servers on Linux systems, including supported distributions.
  • Provide Linux command-line examples (e.g., using shell scripts, .sh installers, or package managers) alongside Windows examples.
  • Mention Linux prerequisites and requirements in the sizing and prerequisites sections.
  • Clarify whether process servers can be deployed on Linux, and if not, state this limitation clearly.
  • Ensure parity in proxy configuration examples by including Linux file path conventions and authentication mechanisms.
GitHub Create Pull Request
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/vmware-azure-common-questions.md ...rticles/site-recovery/vmware-azure-common-questions.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates several Windows biases: Windows tools and paths are mentioned first or exclusively (e.g., PowerShell, C:\ paths, Configuration Manager), examples and instructions often prioritize Windows (e.g., manual installation via PowerShell, MySQL install in C:\Temp), and scripting/automation references focus on PowerShell with no Linux shell equivalents. Linux examples are present in some cases (e.g., agent unregistration), but are generally secondary or missing, and Linux-native tools or patterns (such as bash scripting, Ansible, or Linux package managers) are not discussed.
Recommendations
  • Provide Linux-first or Linux-parity examples for all commands and procedures, including manual installation, scripting, and automation.
  • Include Linux-native automation options (e.g., bash scripts, Ansible, cloud-init) alongside PowerShell.
  • Mention Linux file paths and conventions before or alongside Windows paths.
  • Reference Linux deployment tools (e.g., apt/yum, systemd services) where Configuration Manager or Windows tools are mentioned.
  • Ensure that all instructions and troubleshooting steps have clear, tested Linux equivalents.
  • Add explicit Linux support statements and links to Linux-specific documentation where appropriate.
GitHub Create Pull Request
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/vmware-azure-troubleshoot-replication.md ...site-recovery/vmware-azure-troubleshoot-replication.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page exhibits Windows bias by exclusively referencing Windows file paths (e.g., C:\Program Files, C:\ProgramData), Windows-specific folder structures, and command-line tools (cmd, net stop/start). There are no examples, troubleshooting steps, or log locations provided for Linux-based source machines or process servers, despite Azure Site Recovery supporting physical servers that may run Linux. The documentation assumes Windows environments for permissions (IUSR user), service management, and log file locations, omitting Linux equivalents.
Recommendations
  • Add troubleshooting steps and log file locations for Linux-based source machines and process servers (e.g., /var/log/azure-site-recovery/agent/).
  • Include Linux-specific commands for service management (e.g., systemctl restart asr-agent) alongside Windows examples.
  • Document required permissions and user accounts for Linux (e.g., asr-agent user, chown/chmod commands) in addition to IUSR for Windows.
  • Clearly indicate when a step or path is Windows-specific and provide the Linux equivalent where applicable.
  • Ensure parity in examples, showing both Windows and Linux scenarios for common tasks such as checking agent status, modifying permissions, and locating logs.
GitHub Create Pull Request
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/vmware-azure-troubleshoot-upgrade-failures.md ...recovery/vmware-azure-troubleshoot-upgrade-failures.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation exclusively provides troubleshooting steps and examples for Windows environments. All commands use Windows command prompt syntax, Windows-specific tools (regedit.exe, Task Manager), and Windows file paths (C:\). There are no Linux or cross-platform instructions, nor any mention of Linux equivalents or considerations.
Recommendations
  • Add parallel troubleshooting steps for Linux environments, if supported by Azure Site Recovery.
  • Provide Linux shell command examples for extracting and running installers.
  • Mention Linux equivalents for tools like Registry Editor (e.g., editing configuration files or using relevant Linux commands).
  • Use neutral or cross-platform language and file paths where possible, or clearly indicate if the product is Windows-only.
  • If Linux is not supported, explicitly state this at the beginning of the documentation to set expectations.
GitHub Create Pull Request
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/avs-tutorial-failback.md ...b/main/articles/site-recovery/avs-tutorial-failback.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits Windows bias by specifically mentioning Windows VMs and their interaction with VMware tools, while omitting any reference to Linux VMs or their failback nuances. The only OS-specific note is about Windows VMs, and there are no examples or guidance for Linux VM failback, nor mention of Linux-specific tools or considerations.
Recommendations
  • Add explicit guidance and notes for Linux VMs, including any differences in failback behavior, agent handling, and VMware tools management.
  • Include examples or troubleshooting steps relevant to Linux VMs, such as how VMware tools are handled or any OS-specific requirements.
  • Ensure parity in documentation by mentioning both Windows and Linux VMs where OS-specific behavior is relevant, ideally in the same section.
  • If there are no differences for Linux VMs, state this explicitly to reassure Linux users.
GitHub Create Pull Request
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/avs-tutorial-prepare-avs.md ...ain/articles/site-recovery/avs-tutorial-prepare-avs.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation demonstrates a Windows bias in several ways: Windows instructions and tools (such as registry edits and Windows Firewall) are described in greater detail and appear before Linux equivalents. Windows-specific troubleshooting and configuration steps are more comprehensive, while Linux instructions are brief and lack comparable detail (e.g., no mention of SELinux, SSH key setup, or Linux firewall configuration tools). The documentation references Windows tools and patterns (registry, firewall, RDP) without mentioning Linux alternatives (such as iptables, firewalld, or SSH configuration).
Recommendations
  • Provide equally detailed Linux instructions for Mobility service installation, including steps for configuring SSH, handling sudo/root permissions, and managing Linux firewalls (e.g., iptables, firewalld, ufw).
  • When describing connectivity after failover, offer troubleshooting tips for Linux (e.g., checking SSH logs, SELinux/AppArmor status, and common SSH connection issues).
  • Mention Linux-specific tools and patterns (such as systemctl for service management, SSH key authentication, and Linux firewall configuration) alongside Windows tools.
  • Ensure that Linux examples are presented with parity to Windows examples, both in order and in depth, to avoid the perception of Windows-first bias.
  • Include references to Linux documentation or community resources for further troubleshooting and configuration.
GitHub Create Pull Request
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/azure-to-azure-common-questions.md ...icles/site-recovery/azure-to-azure-common-questions.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation exhibits a Windows bias in several areas: Windows-specific features and tools (such as PowerShell and VSS) are mentioned first or exclusively, with Linux equivalents either omitted or referenced only briefly. Many automation and scripting examples rely on PowerShell, and Windows-centric terminology and extension references (e.g., ADE for Windows, SQL Server extensions) are prevalent. Linux support is mentioned but lacks detailed guidance or parity in examples and tooling.
Recommendations
  • Provide Linux-specific examples and guidance alongside Windows instructions, especially for scripting and automation tasks.
  • Include CLI (az) and Bash examples wherever PowerShell is referenced, ensuring both platforms are covered equally.
  • Explicitly mention Linux-compatible tools and patterns (e.g., cloud-init, Linux disk encryption methods) where Windows tools like VSS or ADE are discussed.
  • Clarify limitations and supported features for Linux VMs in all relevant sections, not just as exclusions.
  • Add links to Linux documentation and troubleshooting guides, matching the depth provided for Windows topics.
  • Ensure that references to extensions (e.g., SQL IaaS Extension) include Linux alternatives or state their applicability.
GitHub Create Pull Request
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/avs-tutorial-failover.md ...b/main/articles/site-recovery/avs-tutorial-failover.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 concepts and links before Linux equivalents, such as linking to Windows availability sets and VM connection guides. There are no explicit Linux or cross-platform examples for VM connection or configuration, and troubleshooting steps do not mention Linux-specific guidance. The documentation also references Windows boot drivers and RDP before SSH, further indicating a Windows-centric approach.
Recommendations
  • Include Linux-specific examples and links, such as connecting to Linux VMs via SSH and troubleshooting Linux VM failover scenarios.
  • Provide parity in documentation for both Windows and Linux, e.g., link to Linux availability set documentation and connection guides.
  • Mention Linux boot drivers and services explicitly alongside Windows drivers when discussing prerequisites and troubleshooting.
  • Ensure that troubleshooting and validation steps cover common Linux issues and solutions, not just Windows.
  • Use neutral language and ordering (e.g., 'RDP or SSH') when listing connection methods, and provide equal detail for both.
GitHub Create Pull Request
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/avs-tutorial-replication.md ...ain/articles/site-recovery/avs-tutorial-replication.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a Windows bias by exclusively describing the configuration server VM as running Windows Server 2016, requiring Windows activation, and guiding users through a Windows installation experience. Linux is only mentioned briefly as an option for Mobility Service credentials, with no examples or guidance for Linux-based configuration servers. All setup and registration steps assume a Windows environment, and there are no Linux-specific instructions or parity in examples.
Recommendations
  • Provide explicit instructions for setting up the configuration server on a Linux VM, if supported, including prerequisites, installation, and registration steps.
  • Include Linux-specific examples for Mobility Service installation, user credential requirements, and troubleshooting.
  • Clarify whether the configuration server must run Windows, or if Linux is supported, and document both paths equally.
  • Ensure parity in screenshots, wizard steps, and command-line instructions for both Windows and Linux environments.
  • Add troubleshooting and FAQ sections for common Linux-specific issues encountered during setup and replication.
GitHub Create Pull Request
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/azure-stack-site-recovery.md ...in/articles/site-recovery/azure-stack-site-recovery.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates Windows bias in several ways: Windows operating systems are listed first and in greater detail than Linux equivalents; Windows-specific tools and patterns (such as registry edits, firewall configuration via GUI, and references to Windows command prompt) are described with step-by-step instructions, while Linux instructions are more generic and lack concrete command examples. There are references to Windows-specific features (e.g., Volume Shadow Copy Service) without Linux alternatives, and screenshots and walkthroughs often use Windows-centric terminology and UI. Linux instructions are present but less detailed, and there are missing Linux command-line examples for key steps.
Recommendations
  • Provide Linux command-line examples for all steps where Windows commands are shown (e.g., registry edits, firewall configuration, service restarts).
  • List supported operating systems in alphabetical order or group by type, rather than listing Windows first.
  • Include Linux equivalents for Windows-specific features (e.g., mention Linux snapshot tools or application consistency mechanisms alongside VSS).
  • Add screenshots and walkthroughs using Linux environments where appropriate.
  • Ensure parity in troubleshooting and configuration guidance for both Windows and Linux, including error messages and remediation steps.
  • Explicitly mention any limitations or differences for Linux VMs in the replication and failover process.
GitHub Create Pull Request
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/azure-to-azure-how-to-enable-replication-cmk-disks.md ...https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/azure-to-azure-how-to-enable-replication-cmk-disks.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page provides a detailed walkthrough for enabling replication of encrypted Azure VMs, but the only code example given is in PowerShell, which is primarily a Windows-centric tool. There are no CLI (az), Bash, or Linux-native examples or instructions, and the FAQ explicitly instructs users to use PowerShell for disk replication tasks. This creates a bias toward Windows users and administrators, making it less accessible for those working on Linux or cross-platform environments.
Recommendations
  • Add equivalent Azure CLI (az) and Bash examples for all PowerShell code snippets, especially for disk replication and management tasks.
  • Explicitly mention that all steps can be performed from Linux/macOS using Azure CLI, and provide links or references to relevant CLI documentation.
  • Where PowerShell is referenced, clarify its cross-platform availability, but still offer native Linux/Bash alternatives for parity.
  • Review screenshots and UI instructions to ensure they do not assume a Windows environment (e.g., avoid references to Windows-only tools or UI patterns).
GitHub Create Pull Request
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/azure-to-azure-protection-errors.md ...cles/site-recovery/azure-to-azure-protection-errors.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Linux First Linux Heavy Missing Windows Example
Summary
The documentation page focuses almost exclusively on Linux-specific troubleshooting, especially around GRUB and LVM configuration, and provides shell commands and Linux file paths. There are no PowerShell examples, Windows tools, or Windows-specific troubleshooting steps. The only bias present is toward Linux, with missing parity for Windows VM replication scenarios.
Recommendations
  • Add troubleshooting steps and examples for common Windows VM replication errors, such as issues with Windows Boot Manager, BitLocker, or VSS.
  • Include PowerShell commands or screenshots for Windows-based workflows where relevant.
  • Mention Windows-specific disk or extension issues if applicable, and provide guidance for resolving them.
  • Ensure that both Linux and Windows scenarios are covered in each error section, or clearly indicate when an issue is Linux-specific.
GitHub Create Pull Request
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/azure-to-azure-how-to-enable-replication-ade-vms.md ...ry/azure-to-azure-how-to-enable-replication-ade-vms.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 Windows bias by providing only PowerShell-based scripts and instructions for key operations (such as copying disk encryption keys), referencing the Windows PowerShell application explicitly, and omitting equivalent Linux shell or CLI examples. The use of Windows-centric tools and terminology is prevalent, and Linux alternatives are not mentioned or prioritized, despite partial support for Linux VMs. This may hinder Linux administrators from following the guidance effectively.
Recommendations
  • Provide equivalent Bash/CLI scripts for copying disk encryption keys, and include instructions for running these on Linux or macOS systems.
  • Reference Azure CLI commands and examples alongside PowerShell, especially for key vault and replication operations.
  • Explicitly state any differences or limitations for Linux VMs, and offer step-by-step Linux-specific guidance where applicable.
  • Avoid referencing Windows tools (such as 'Windows PowerShell application') exclusively; use cross-platform terminology like 'PowerShell' or 'terminal'.
  • Add troubleshooting steps and examples relevant to Linux environments, including permission management and error resolution.
GitHub Create Pull Request
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/azure-to-azure-troubleshoot-errors.md ...es/site-recovery/azure-to-azure-troubleshoot-errors.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates several types of Windows bias. Windows troubleshooting steps and tools (such as Services console, Internet Explorer, and Windows Update) are mentioned first or exclusively in multiple sections. Some error resolutions (e.g., COM+ or VSS errors) only provide Windows-specific instructions, with no Linux equivalent or explanation. Proxy autodetection references Internet Explorer for Windows, while Linux instructions are less detailed. Windows terminology and tools are often presented before or instead of Linux alternatives.
Recommendations
  • Ensure troubleshooting steps for errors (e.g., COM+/VSS) include Linux equivalents or explicitly state if not applicable.
  • Present Windows and Linux instructions in parallel, giving equal prominence to both platforms.
  • Replace or supplement Windows-specific tools (e.g., Services console, Internet Explorer) with Linux alternatives (e.g., systemctl, journalctl, relevant config files).
  • Provide Linux-specific examples for all error codes and scenarios, not just for certificate management.
  • Avoid referencing Windows tools or patterns (e.g., Windows Update, IE proxy settings) without mentioning Linux equivalents.
  • Where an issue is Windows-only, clearly state its platform specificity.
GitHub Create Pull Request
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/azure-to-azure-troubleshoot-network-connectivity.md ...ry/azure-to-azure-troubleshoot-network-connectivity.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 mild Windows bias. While most troubleshooting steps are platform-neutral, several sections reference Windows tools and patterns first (e.g., Internet Explorer for proxy detection, Windows file paths), and provide screenshots or instructions that are Windows-centric. Linux equivalents are mentioned but often after Windows, and there are no explicit Linux command-line examples or screenshots. The NSG configuration examples are GUI-based and do not show CLI or Linux-native workflows.
Recommendations
  • Provide Linux-first or parallel examples for proxy detection and configuration, such as referencing /etc/environment and Linux browsers.
  • Include Linux command-line examples (e.g., using Azure CLI or shell commands) for NSG rule creation and troubleshooting.
  • Add screenshots or step-by-step instructions for Linux environments where applicable.
  • Avoid referencing Windows tools (like Internet Explorer) without mentioning Linux alternatives (such as Firefox, Chromium, or system proxy settings).
  • Ensure file paths and configuration instructions are presented for both Windows and Linux, with equal prominence.
  • Consider adding a table or section explicitly comparing Windows and Linux troubleshooting steps for common issues.
GitHub Create Pull Request
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/azure-to-azure-replicate-after-migration.md ...e-recovery/azure-to-azure-replicate-after-migration.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a Windows-first bias by presenting Windows instructions and validation steps before Linux equivalents, referencing Windows-specific tools and file paths (e.g., Control Panel, C:\WindowsAzure\Packages), and providing more detailed validation steps for Windows than for Linux. The Linux section lacks parity in example depth and troubleshooting, and does not mention common Linux troubleshooting tools or provide equivalent validation details.
Recommendations
  • Present Windows and Linux instructions in parallel, or alternate which platform is described first.
  • Provide equally detailed validation steps for Linux, such as checking agent version, log file locations, and service status.
  • Include Linux-specific troubleshooting links and examples, such as journalctl/systemctl commands for service status and logs.
  • Reference Linux package management tools (apt, yum, zypper) explicitly, and provide example commands for installation and updates.
  • Avoid using Windows-specific terminology (e.g., Control Panel, right-click) without Linux equivalents.
  • Ensure that all steps and recommendations for Windows have clear, matching instructions for Linux users.
GitHub Create Pull Request
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/azure-to-azure-support-matrix.md ...rticles/site-recovery/azure-to-azure-support-matrix.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates several forms of Windows bias. Windows and PowerShell are mentioned first and more frequently in deployment method support and operational instructions. Azure PowerShell is referenced as the main automation tool, with no equivalent Linux CLI or shell scripting alternatives provided. In several places, only Windows-specific tools and update requirements are described in detail (e.g., SSU/SHA-2 for Windows 7/2008), while Linux instructions are less explicit or missing. There are no Linux CLI or shell script examples for tasks such as setting up disaster recovery, managing cache storage, or excluding disks. The documentation also references Windows-specific features (like Azure Disk Encryption for Windows OS) before Linux equivalents.
Recommendations
  • Provide Azure CLI (Linux-friendly) examples and workflows for all operations currently described only with PowerShell.
  • Mention Linux automation and management tools (e.g., bash scripts, cloud-init, Ansible) alongside or before Windows/PowerShell tools.
  • Ensure Linux-specific instructions (such as agent installation, upgrades, and troubleshooting) are as detailed as their Windows counterparts.
  • Add parity in operational guidance, such as how to exclude disks or manage cache storage, with Linux-native commands and procedures.
  • Present Linux and Windows support information in parallel tables or sections to avoid Windows-first ordering.
  • Include troubleshooting and update instructions for Linux agents and kernels with the same level of detail as Windows update requirements.
GitHub Create Pull Request
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/azure-to-azure-troubleshoot-replication.md ...te-recovery/azure-to-azure-troubleshoot-replication.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits a Windows bias in several ways: PowerShell is referenced as the primary method for excluding disks, troubleshooting steps and log file locations are described in detail for Windows (with explicit file paths and service names), and VSS (Volume Shadow Copy Service) troubleshooting is exclusively Windows-centric. Linux is mentioned only briefly, with minimal guidance and no concrete examples or commands. Windows tools and patterns (e.g., VSS, specific service restarts, .cmd scripts) are described in detail, while Linux equivalents are missing or underexplained.
Recommendations
  • Provide Linux-specific examples and commands for key troubleshooting steps, such as excluding disks and checking data churn.
  • Include detailed instructions for locating and interpreting relevant log files on Linux systems.
  • Offer parity in troubleshooting for Linux VMs, such as guidance for app-consistency, service management, and error resolution.
  • Reference Linux-native tools (e.g., shell commands, systemctl/service management) alongside Windows tools, and avoid presenting Windows methods first unless both are given equal prominence.
  • Expand the documentation for Linux environments to match the depth and clarity provided for Windows, including step-by-step procedures and screenshots where applicable.
GitHub Create Pull Request
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/azure-to-azure-virtual-machine-errors.md ...site-recovery/azure-to-azure-virtual-machine-errors.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation demonstrates Windows bias in several ways: Windows instructions and links are presented before Linux equivalents, especially in disk initialization. The cleanup steps for stale Site Recovery configurations exclusively reference a PowerShell script (.ps1) with no mention of a Linux/bash alternative, implying that only Windows users are supported for these operations. There are no Linux-specific examples or scripts for key troubleshooting tasks, and the use of Windows-centric tooling (PowerShell) is prevalent.
Recommendations
  • Provide Linux/bash script equivalents for the cleanup of stale Site Recovery configurations, or document how Linux users can perform these steps using Azure CLI.
  • Present Windows and Linux instructions in parallel, or alternate which platform is listed first to avoid implicit prioritization.
  • Include explicit Linux examples for all troubleshooting steps, especially those currently covered only by PowerShell scripts.
  • Reference cross-platform tools (such as Azure CLI) where possible, and clarify which steps are platform-agnostic.
GitHub Create Pull Request
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/configure-mobility-service-proxy-settings.md ...-recovery/configure-mobility-service-proxy-settings.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates Windows bias by presenting Windows-specific details and tools (such as Internet Explorer and psexec) before Linux equivalents, focusing on Windows environment variables and file paths first, and referencing Windows-only configuration steps. Linux instructions are less detailed and lack equivalent step-by-step guidance, especially for setting environment variables and editing configuration files.
Recommendations
  • Provide Linux configuration steps with equal detail, including commands for setting environment variables and editing ProxyInfo.conf.
  • Mention Linux tools (e.g., nano, vi) for editing configuration files, similar to how psexec is referenced for Windows.
  • Present Windows and Linux instructions in parallel sections or tables to ensure parity and clarity.
  • Avoid referencing Windows-only tools (like Internet Explorer and psexec) without Linux equivalents or alternatives.
  • Include explicit Linux examples for checking and creating ProxyInfo.conf, not just Windows file paths.
GitHub Create Pull Request
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/concepts-expressroute-with-site-recovery.md ...e-recovery/concepts-expressroute-with-site-recovery.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 Windows bias by exclusively referencing Windows-specific tools (PsExec, Internet Explorer) and providing configuration steps that only apply to Windows environments. There are no Linux equivalents or examples for proxy configuration or bypass list setup, and the instructions assume a Windows-based Configuration Server and Process Server. The use of Windows tools is presented first and exclusively, without mention of how to perform similar tasks on Linux systems.
Recommendations
  • Provide equivalent instructions for Linux-based Configuration Servers and Process Servers, including how to configure proxy bypass lists using Linux tools and browsers.
  • Include examples using Linux command-line utilities (e.g., curl, wget, or configuration file edits) for proxy settings.
  • Reference cross-platform tools or clarify OS-specific requirements for each step.
  • Avoid assuming Internet Explorer is available; suggest alternatives like Firefox or Chromium for Linux.
  • Clearly state OS prerequisites for each procedure and offer parity in guidance for both Windows and Linux environments.
GitHub Create Pull Request
← Previous Page 11 of 35 Next →