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 426-450 of 864 flagged pages
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/site-recovery-runbook-automation.md ...cles/site-recovery/site-recovery-runbook-automation.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools Windows First
Summary
The documentation page demonstrates a strong Windows bias by exclusively providing PowerShell-based examples and scripts, referencing Windows-centric AzureRM modules, and omitting any Linux shell (e.g., Bash) or Python alternatives. All automation and scripting guidance assumes the use of PowerShell, which is native to Windows, and there is no mention of Linux tools, cross-platform scripting, or how to adapt these instructions for Linux-based environments. The documentation also references Windows patterns and tools first and exclusively, reinforcing the bias.
Recommendations
  • Provide equivalent Bash or Python examples for Linux users, especially for interacting with Azure Automation and recovery plan context.
  • Mention and document the use of Az CLI and REST API methods as cross-platform alternatives to PowerShell/AzureRM modules.
  • Clarify which steps or scripts are platform-agnostic and which require adaptation for Linux environments.
  • Include guidance on installing and using PowerShell Core on Linux, if PowerShell scripting is required, and note any differences.
  • Add explicit sections or notes for Linux users, including troubleshooting and best practices for integrating Azure Automation runbooks in Linux-based recovery scenarios.
GitHub Create Pull Request
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-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation for the Azure Site Recovery Deployment Planner for VMware disaster recovery demonstrates a strong Windows bias. All instructions, prerequisites, and examples assume the use of Windows Server or Windows PC, with no mention of Linux or cross-platform alternatives. The tool requires Windows-only dependencies (.NET Framework, Visual C++ Redistributable), and all usage scenarios and hardware recommendations are Windows-centric. There are no Linux usage examples, nor is there guidance for running the tool on Linux systems.
Recommendations
  • Provide explicit information on whether the tool can run on Linux systems, and if not, clarify this limitation early in the documentation.
  • If possible, develop and document a Linux-compatible version of the Deployment Planner tool.
  • Offer alternative instructions or workarounds for Linux users, such as running the tool in a Windows VM or container on a Linux host.
  • Include Linux-specific prerequisites, installation steps, and usage examples alongside Windows instructions.
  • Highlight any cross-platform capabilities or limitations in the overview and prerequisites sections.
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-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation exclusively provides PowerShell examples and references only PowerShell cmdlets (New-AzRecoveryServicesAsrVMNicConfig, New-AzRecoveryServicesAsrVMNicIPConfig), which are primarily used on Windows. There are no examples or guidance for Linux users, such as Bash, Azure CLI, or cross-platform scripting alternatives. The documentation assumes familiarity with Windows tooling and scripting patterns, and does not mention Linux equivalents or how to perform these operations outside of PowerShell.
Recommendations
  • Add equivalent examples using Azure CLI (az commands) for configuring IP settings for failover/test failover.
  • Explicitly state whether these operations can be performed from Linux/macOS environments, and provide guidance for cross-platform users.
  • Include Bash script samples or instructions for users who do not use PowerShell.
  • Clarify if the cmdlets are available in PowerShell Core (cross-platform) or only Windows PowerShell, and recommend alternatives for non-Windows users.
  • Provide a comparison table of PowerShell cmdlets and their Azure CLI equivalents for common disaster recovery tasks.
GitHub Create Pull Request
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/vmware-azure-manage-configuration-server.md ...e-recovery/vmware-azure-manage-configuration-server.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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 significant Windows bias. Windows-specific tools (PowerShell, DISM, registry editing, .exe utilities) are referenced exclusively or before any Linux alternatives. Many operational examples (certificate renewal, server registration, deletion, passphrase generation) rely on Windows paths, executables, and PowerShell commands, with no mention of Linux equivalents or guidance for Linux-based configuration servers. There are no bash or Linux CLI examples, and Linux-specific management patterns are absent.
Recommendations
  • Provide Linux-specific instructions and examples for all major tasks, including certificate renewal, server registration, deletion, and passphrase generation.
  • Include bash or shell command equivalents alongside PowerShell commands where applicable.
  • Clarify whether the configuration server can be deployed on Linux, and if so, document the Linux deployment and management workflow.
  • Reference Linux tools (e.g., systemctl, openssl, bash scripts) where Windows tools (e.g., net, PowerShell, .exe utilities) are mentioned.
  • Ensure parity in troubleshooting steps, file paths, and environment variables for both Windows and Linux.
  • Add explicit notes or sections for Linux users, especially for tasks currently described only with Windows-centric instructions.
GitHub Create Pull Request
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/vmware-physical-azure-classic-deprecation.md ...-recovery/vmware-physical-azure-classic-deprecation.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page demonstrates a Windows bias by referencing PowerShell as a management tool and mentioning portal-based management, both of which are traditionally Windows-centric. There are no explicit Linux CLI or tool examples, and the mention of 'mobility agent support for new Linux distros' is secondary to the overall Windows-oriented management patterns. Windows tools and workflows (PowerShell, Azure portal) are referenced before any Linux alternatives, and Linux-specific instructions or parity are missing.
Recommendations
  • Include Linux CLI examples (such as Bash or Azure CLI) alongside or instead of PowerShell commands for migration and management tasks.
  • Explicitly mention Linux management workflows and tools where applicable, such as scripting migration steps using Linux shell commands.
  • Clarify whether all management actions (e.g., migration, replication enablement) can be performed from Linux environments and document any differences.
  • Add guidance for Linux administrators, including troubleshooting steps and agent installation instructions for common Linux distributions.
  • Ensure that references to tools (portal, PowerShell) are balanced with Linux-friendly alternatives and that Linux support is highlighted equally in all relevant sections.
GitHub Create Pull Request
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/vmware-azure-troubleshoot-failback-reprotect.md ...covery/vmware-azure-troubleshoot-failback-reprotect.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exhibits Windows bias by providing more detailed troubleshooting steps and outcomes for Windows VMs compared to Linux VMs. Windows-specific behaviors (such as reacquiring static IP addresses) are mentioned, while Linux requires manual intervention without further guidance. Windows Server is referenced as a protected physical server, but Linux equivalents are not discussed. Troubleshooting steps mention Windows tools (Telnet, ping) without referencing Linux alternatives. There are no Linux-specific command examples or troubleshooting patterns, and Windows scenarios are often described first or in more detail.
Recommendations
  • Provide equivalent Linux troubleshooting steps and examples, such as commands for checking connectivity (e.g., 'nc', 'curl', or 'ping' on Linux).
  • Include Linux-specific error scenarios and resolutions, especially for common issues like network configuration and service management.
  • Balance the coverage of Windows and Linux VM behaviors, ensuring both platforms are described with equal detail and actionable guidance.
  • Reference Linux tools and patterns alongside Windows tools, and avoid presenting Windows scenarios first unless contextually necessary.
  • Add explicit Linux command-line examples for tasks such as checking service status, restarting services, and configuring static IP addresses.
GitHub Create Pull Request
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/vmware-azure-failback.md ...b/main/articles/site-recovery/vmware-azure-failback.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates Windows bias by specifically mentioning Windows VMs and their interaction with VMware tools during failback, without providing equivalent details or examples for Linux VMs. There is no mention of Linux-specific considerations, behaviors, or troubleshooting steps, and the only OS-specific note is for Windows. This suggests a Windows-centric approach and a lack of Linux parity in guidance.
Recommendations
  • Add explicit guidance and notes for Linux VMs, including any differences in failback behavior, agent registration, and VMware tools handling.
  • Include troubleshooting steps or considerations unique to Linux VMs, such as handling of open-source VMware tools (open-vm-tools) or differences in shutdown/startup processes.
  • Provide examples or screenshots for both Windows and Linux VMs to ensure parity and inclusivity.
  • Clarify whether any steps or recommendations differ for Linux VMs, and if not, explicitly state that the process is identical for both OS types.
GitHub Create Pull Request
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/vmware-azure-manage-process-server.md ...es/site-recovery/vmware-azure-manage-process-server.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a strong Windows bias. All command-line instructions use Windows-specific tools (cmd.exe, PowerShell, Windows paths like %PROGRAMDATA%), and examples reference Windows conventions exclusively. There are no Linux or cross-platform equivalents provided for managing process servers, proxy settings, or anti-virus exclusions. The documentation assumes the process server is running on Windows, despite VMware and physical server environments often including Linux systems.
Recommendations
  • Provide equivalent Linux instructions for all command-line operations, including registering/reregistering process servers and modifying proxy settings.
  • Include Linux file paths and shell commands (e.g., bash, systemctl) alongside Windows examples.
  • Mention Linux anti-virus exclusion paths and directories.
  • Clarify platform support and prerequisites, specifying whether process servers can run on Linux and, if not, explain the limitation.
  • Present examples for both Windows and Linux environments in parallel, or indicate when a step is Windows-only.
GitHub Create Pull Request
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/vmware-azure-mobility-install-configuration-mgr.md ...ery/vmware-azure-mobility-install-configuration-mgr.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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 by consistently presenting Windows tools and workflows first (e.g., Configuration Manager, SMB shares, administrative command prompt), providing more detailed and visual guidance for Windows, and relying on Windows-centric scripting and tools. Linux instructions are present but are often secondary, less detailed, and lack parity in tool recommendations and visual aids. There is also a lack of Linux-native deployment tool examples, and the uninstall example is Windows-only.
Recommendations
  • Present Linux and Windows instructions in parallel, or alternate which platform is described first to avoid 'windows_first' bias.
  • Include Linux-native deployment tool examples (e.g., Ansible, Puppet, Chef) alongside Configuration Manager and JetPatch.
  • Provide Linux equivalents for all Windows-specific steps, such as using NFS shares instead of only SMB, and show how to generate the passphrase on Linux.
  • Add screenshots or detailed walkthroughs for Linux package creation and deployment, not just Windows/Configuration Manager.
  • Include Linux uninstall instructions and scripts, not just Windows examples.
  • Reference cross-platform or open-source tools where possible, not just Microsoft-centric solutions.
  • Ensure that all code samples, troubleshooting, and advanced scenarios are equally covered for both Windows and Linux.
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-08 00:53
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, using Windows-specific tools (Command Prompt, Registry Editor, Task Manager), file paths (C:\), and executable formats (.exe). There are no references to Linux equivalents, commands, or file system conventions, indicating a strong Windows bias.
Recommendations
  • Add equivalent troubleshooting steps for Linux environments, including commands for extracting and running installers.
  • Provide Linux shell (bash) command examples alongside Windows Command Prompt examples.
  • Reference Linux file paths and conventions (e.g., /tmp/Extracted) where appropriate.
  • Mention Linux tools (such as using 'ps' or 'htop' instead of Task Manager) for monitoring processes.
  • Clarify whether the Site Recovery Provider supports Linux installations, and if not, explicitly state the platform limitations.
GitHub Create Pull Request
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/vmware-physical-large-deployment.md ...cles/site-recovery/vmware-physical-large-deployment.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exhibits several signs of Windows bias. PowerShell is the only automation example given for triggering failover, with no Linux CLI or Bash alternatives. Compliance and preparation steps for failover are described in detail for Windows machines, while Linux compliance is mentioned only briefly and passively. Troubleshooting and configuration guidance, as well as references to tools and scripts, are focused on Windows environments, with Linux-specific instructions or parity missing. The overall structure and examples prioritize Windows tools and workflows, leaving Linux users with less actionable guidance.
Recommendations
  • Provide equivalent Linux CLI (az CLI, Bash) examples for key operations such as triggering failover, alongside PowerShell.
  • Include detailed steps for preparing Linux machines for failover, similar to the Windows compliance section.
  • Add troubleshooting and compliance check instructions for Linux environments, not just Windows.
  • Reference Linux tools and automation patterns (e.g., shell scripts, cron jobs) where appropriate.
  • Ensure that all configuration and setup instructions are platform-neutral or have clear Linux-specific sections.
  • Review and update links and references to include Linux documentation and best practices.
GitHub Create Pull Request
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/vmware-azure-troubleshoot-vcenter-discovery-failures.md ...tps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/vmware-azure-troubleshoot-vcenter-discovery-failures.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Windows tools (PsExec, Internet Explorer, command prompt), providing only Windows-based procedures for proxy configuration, and omitting any Linux or cross-platform alternatives. All troubleshooting steps assume a Windows environment, with no mention of Linux equivalents or guidance for users running the configuration server on Linux.
Recommendations
  • Provide Linux-specific troubleshooting steps for proxy configuration, including how to check and modify proxy settings on Linux systems.
  • Include alternative tools and commands for Linux environments (e.g., using 'sudo -u' or 'su' for system context, modifying proxy settings via environment variables or configuration files).
  • Mention cross-platform approaches where possible, such as using browser-independent methods for proxy configuration.
  • Clarify whether the configuration server can run on Linux, and if so, add relevant instructions for Linux users.
  • Avoid referencing Windows-only tools (PsExec, Internet Explorer) without offering Linux alternatives.
GitHub Create Pull Request
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/vmware-physical-mobility-service-overview.md ...-recovery/vmware-physical-mobility-service-overview.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 5 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Windows Path Examples Windows-Centric Instructions
Summary
The documentation page demonstrates a moderate Windows bias. Windows instructions, examples, and paths are consistently presented first in installation sections, with Windows-centric tools and folder structures (e.g., C:\Program Files (x86)\...) used as defaults. UI screenshots and step-by-step guides are primarily for Windows environments, with Linux instructions often appearing after Windows or in less detail. Windows-specific concepts (e.g., VSS provider, antivirus exclusions in C:\ProgramData) are highlighted, while Linux equivalents are not discussed or are less emphasized. The use of Windows command prompt and folder paths as the primary example throughout the document reinforces a Windows-first perspective.
Recommendations
  • Present Linux and Windows instructions in parallel, giving equal prominence and detail to both platforms.
  • Include Linux UI screenshots and step-by-step guides where applicable, not just Windows.
  • Use neutral language and folder paths in generic instructions, or provide both Windows and Linux examples side-by-side.
  • Discuss Linux-specific considerations (e.g., SELinux, systemd services, antivirus exclusions for Linux paths) with the same depth as Windows topics.
  • Where Windows tools or concepts (e.g., VSS, C:\ProgramData) are mentioned, provide Linux equivalents or clarify platform-specific differences.
  • Ensure that tables and lists of supported operating systems do not default to Windows at the top, but are sorted alphabetically or by usage.
GitHub Create Pull Request
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/vmware-troubleshoot-mobility-agent-health.md ...-recovery/vmware-troubleshoot-mobility-agent-health.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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 listing Windows log file locations before Linux, referencing Windows paths and hostnames in error messages, and mentioning Windows-specific services and tools (e.g., 'Microsoft Azure RCM Proxy Agent'). There are no explicit Linux troubleshooting commands, service names, or examples, and Linux-specific steps are missing or not described in parity with Windows.
Recommendations
  • List Linux and Windows log file locations in parallel, or alternate which is mentioned first.
  • Include Linux-specific troubleshooting steps, such as relevant systemctl/service commands for restarting services, and mention Linux service names if different.
  • Provide Linux command-line examples (e.g., using systemctl, journalctl, or service commands) for agent/service management.
  • Reference Linux hostnames and file paths in error message examples where applicable.
  • Ensure all resolutions and steps are described for both platforms, not just Windows.
  • Clarify any platform-specific differences in agent installation, configuration, or error handling.
GitHub Create Pull Request
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/vmware-azure-set-up-source.md ...n/articles/site-recovery/vmware-azure-set-up-source.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates Windows bias by listing Windows-specific folders and registry keys for antivirus exclusions before Linux equivalents, focusing heavily on C: drive paths and Windows program directories. Linux instructions are limited to a single section, and there are no Linux-specific setup or troubleshooting examples. Windows tools and patterns (e.g., registry keys, drive letters, Windows program folders) are mentioned exclusively or first, with Linux coverage appearing as an afterthought.
Recommendations
  • Provide Linux-specific setup and troubleshooting steps alongside Windows instructions, especially for configuration server deployment and antivirus exclusions.
  • List Linux and Windows antivirus exclusions together, or alternate their order to avoid Windows-first bias.
  • Include examples of Linux command-line operations (e.g., shell commands for folder exclusions) and clarify how to perform equivalent tasks on Linux systems.
  • Reference Linux tools and patterns where appropriate, such as systemd services, log locations, and package management.
  • Ensure parity in documentation depth and clarity for both Windows and Linux environments.
GitHub Create Pull Request
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/vmware-azure-troubleshoot-push-install.md ...ite-recovery/vmware-azure-troubleshoot-push-install.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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 by consistently presenting Windows troubleshooting steps, tools, and examples before or in greater detail than Linux equivalents. Windows-specific tools (e.g., registry editor, net user, netlogon, File Explorer, Control Panel, Windows Firewall, WMI, VSS, COM+, DCOM, Windows drivers) are referenced extensively, often with step-by-step instructions and command-line examples. Linux troubleshooting is present but less detailed, and some sections (e.g., network shared folders, VSS errors, driver checks) lack Linux-specific guidance or examples.
Recommendations
  • Ensure that troubleshooting steps for Linux are presented with equal detail and prominence as Windows steps, including command-line examples and configuration file locations.
  • Provide Linux equivalents for Windows tools and patterns (e.g., show how to check network shares using smbclient or NFS, how to manage services and permissions, how to check and install drivers/modules).
  • Include Linux-specific error codes and troubleshooting scenarios where applicable, especially for sections currently focused on Windows (e.g., VSS, WMI, driver issues).
  • Where Windows registry or GUI steps are described, offer corresponding Linux configuration file edits or CLI commands.
  • Add screenshots or terminal output examples for Linux alongside Windows GUI screenshots.
  • Review all troubleshooting sections to ensure Linux users are not required to infer steps from Windows instructions.
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-08 00:53
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 tools (e.g., UnifiedSetup.exe, .exe installers, Windows-style paths), providing only Windows command-line examples, and omitting any Linux installation or usage instructions. There is no mention of Linux equivalents or cross-platform considerations, and all examples use Windows conventions and terminology.
Recommendations
  • Add Linux installation instructions, including supported distributions and prerequisites.
  • Provide Linux command-line examples (e.g., using bash, shell scripts, Linux file paths).
  • Clarify whether the process server can be installed on Linux, and if not, explicitly state Windows-only support.
  • If cross-platform support exists, mention Linux-specific requirements, troubleshooting, and configuration steps.
  • Ensure parity in screenshots and UI instructions for Linux environments if applicable.
GitHub Create Pull Request
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/vmware-physical-azure-support-matrix.md .../site-recovery/vmware-physical-azure-support-matrix.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates several forms of Windows bias. Windows-specific tools and deployment methods (such as PowerShell) are mentioned before or exclusively compared to Linux alternatives. The replication appliance is required to run Windows Server, with no Linux option. Deployment instructions and automation scripts are referenced as PowerShell scripts, with no mention of Bash or Linux-native tooling. Windows server roles and group policies are discussed in detail, while Linux equivalents are omitted. Examples and configuration details are often provided for Windows first, with Linux relegated to later sections or only as a list of supported distributions and kernel versions. There are no Linux-specific setup or automation examples, and no mention of Linux-native management or monitoring tools.
Recommendations
  • Provide Linux-based deployment options for the replication appliance, or clarify if Windows is strictly required and why.
  • Include Bash or shell script equivalents for automation tasks currently described as PowerShell scripts.
  • Offer Linux-native configuration and management guidance, such as SELinux/AppArmor, systemd services, or relevant Linux security practices.
  • Ensure that Linux examples and instructions are presented alongside Windows examples, not only as lists of supported versions.
  • Reference Linux monitoring and troubleshooting tools (e.g., journalctl, dmesg, syslog) where Windows tools (Event Viewer, group policies) are discussed.
  • Clarify any limitations or differences in feature parity between Windows and Linux, and provide workarounds or alternatives where possible.
GitHub Create Pull Request
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/vmware-azure-troubleshoot-configuration-server.md ...very/vmware-azure-troubleshoot-configuration-server.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in several ways: Windows examples and instructions are consistently presented first, Windows-specific tools (such as PsExec, Internet Explorer, and Windows services) are referenced without Linux equivalents, and some troubleshooting steps and log file paths are only described for Windows. Linux instructions are sometimes present but are often secondary, less detailed, or omitted entirely in sections where Windows steps are explicit.
Recommendations
  • Present Linux and Windows instructions in parallel, giving equal prominence to both platforms.
  • Include Linux equivalents for all Windows tools and commands (e.g., suggest Linux alternatives to PsExec, Internet Explorer, and Windows service management).
  • Provide Linux-specific troubleshooting steps and log file paths wherever Windows examples are given.
  • Ensure that all examples, commands, and file paths are available for both platforms, and avoid assuming Windows as the default environment.
  • Add explicit guidance for Linux firewall configuration, service management, and agent registration where only Windows steps are described.
  • Review and update sections that reference Windows-only licensing or support issues to clarify Linux applicability or provide Linux-specific notes.
GitHub Create Pull Request
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/vmware-physical-azure-troubleshoot-process-server.md ...y/vmware-physical-azure-troubleshoot-process-server.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation page exhibits a strong Windows bias. Troubleshooting steps, examples, and tool references are almost exclusively Windows-centric. All file paths, service names, and troubleshooting commands (e.g., telnet, Task Manager, Resource Monitor, Control Panel, registry edits) are Windows-specific. There are no Linux equivalents or instructions for process servers running on Linux, nor any mention of Linux troubleshooting tools, logs, or service management commands. The only time system time sync is referenced, it links to Windows documentation. No parity is provided for Linux administrators.
Recommendations
  • Add Linux-specific troubleshooting steps, including file paths, service management commands (systemctl, journalctl), and log locations.
  • Provide Linux equivalents for tools such as Task Manager (e.g., top, htop, nload), Resource Monitor (e.g., netstat, iftop), and registry edits (e.g., config files).
  • Include examples of checking services and network connectivity on Linux (e.g., systemctl status, netstat, curl, telnet).
  • Reference Linux time synchronization documentation (e.g., chrony, ntpd) alongside Windows time service.
  • Mention antivirus and firewall configuration steps for common Linux distributions.
  • Ensure all troubleshooting procedures are presented for both Windows and Linux environments, or clearly state platform limitations.
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-08 00:53
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 services, and command-line instructions (cmd, net stop/start). There are no examples, troubleshooting steps, or log locations provided for Linux-based source machines or process servers, despite the fact that Azure Site Recovery supports replication from Linux servers. All examples and instructions assume a Windows environment, and Windows tools and conventions are used throughout.
Recommendations
  • Add troubleshooting steps, log file locations, and service management instructions for Linux source machines and process servers (e.g., systemctl commands, Linux file paths like /var/log/).
  • Include examples for both Windows and Linux environments when referencing agent installation, service restarts, and permission settings.
  • Explicitly mention Linux support and provide parity in documentation structure, so Linux users can follow equivalent steps.
  • Where commands or paths differ, use tabbed or side-by-side examples for Windows and Linux.
  • Reference Linux-specific error messages, common issues, and solutions relevant to Azure Site Recovery replication.
GitHub Create Pull Request
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/vmware-troubleshoot-appliance-health-issue.md ...recovery/vmware-troubleshoot-appliance-health-issue.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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 clear Windows bias by providing troubleshooting steps that exclusively use PowerShell commands and reference Windows file paths and tools (e.g., 'Microsoft Azure Appliance Configuration Manager'). There are no examples or instructions for Linux environments, nor is there any mention of Linux equivalents or cross-platform alternatives. The troubleshooting workflow assumes the administrator is working on a Windows system, with no guidance for those using Linux-based management or shell environments.
Recommendations
  • Add Linux-specific troubleshooting steps, including equivalent Bash or shell commands for certificate renewal and appliance management.
  • Provide examples using Linux file paths and tools, such as referencing common Linux directories and using shell scripts.
  • Explicitly state platform requirements and, if possible, offer cross-platform instructions or note any limitations for Linux users.
  • Reorder instructions to present both Windows and Linux options side-by-side, or clarify which steps are platform-specific.
  • Include a section addressing Linux compatibility and how to perform key operations on Linux systems.
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: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by specifically mentioning the handling of VMware tools for Windows VMs during failover/failback, without referencing Linux VMs or their equivalent tooling. There are no examples or notes about Linux VMs, their requirements, or any differences in the failback process. The only OS-specific guidance is for Windows, and Linux scenarios are omitted.
Recommendations
  • Add equivalent notes or guidance for Linux VMs, such as how VMware tools or open-vm-tools are handled during failover/failback.
  • Explicitly mention if the process is the same or different for Linux VMs, and highlight any OS-specific considerations.
  • Include troubleshooting tips or common issues for Linux VMs, similar to the note provided for Windows.
  • Ensure parity in examples and notes by providing both Windows and Linux perspectives wherever OS-specific behavior is relevant.
GitHub Create Pull Request
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/site-recovery-failover.md .../main/articles/site-recovery/site-recovery-failover.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a Windows-first bias, especially in the 'Prepare on-premises to connect after failover' section, where Windows instructions are more detailed and appear before Linux instructions. Windows-specific tools and settings (e.g., Windows Firewall, WinHTTP proxy, SAN policy) are mentioned, while Linux guidance is minimal and lacks equivalent detail. There are also missing Linux examples for some troubleshooting and configuration steps.
Recommendations
  • Provide Linux instructions with equal detail and prominence as Windows, including firewall configuration (e.g., iptables, firewalld, ufw), SSH service management, and handling of persistent routes or proxies.
  • List Linux and Windows procedures side-by-side or in parallel sections, rather than always listing Windows first.
  • Include Linux-specific troubleshooting resources and links, similar to the Windows RDP troubleshooting tips provided.
  • Mention Linux equivalents for Windows-specific settings (e.g., SAN policy, pending updates) or clarify if not applicable.
  • Ensure all automation and scripting examples (if any) are cross-platform or provide both PowerShell and Bash/Shell script samples.
GitHub Create Pull Request
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/concepts-on-premises-to-azure-networking.md ...e-recovery/concepts-on-premises-to-azure-networking.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation demonstrates a Windows bias by providing detailed, step-by-step instructions and references for preparing Windows machines, including PowerShell usage and Windows Firewall configuration, while Linux preparation is covered only briefly. Windows tools and patterns (e.g., RDP, Windows Firewall, PowerShell) are mentioned exclusively or before their Linux equivalents, and there are no Linux-specific examples or command references.
Recommendations
  • Provide equally detailed steps for preparing Linux machines, including example commands for configuring SSH, managing firewall rules (e.g., using ufw, firewalld, or iptables), and checking required services.
  • Include references or links to official Linux documentation for preparing VMs for Azure, similar to the Windows links provided.
  • Mention Linux tools and access patterns (e.g., SSH, Linux firewalls) alongside Windows tools, not just as a secondary note.
  • Add example scripts or automation runbooks for Linux environments, not just PowerShell/Windows.
  • Ensure that all sections referencing RDP or Windows Firewall also mention SSH and Linux firewall configuration where appropriate.
GitHub Create Pull Request
← Previous Page 18 of 35 Next →