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 676-700 of 864 flagged pages
Site Recovery Plan capacity for VMware disaster recovery with Azure Site Recovery ...es/site-recovery/site-recovery-plan-capacity-vmware.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page exhibits several Windows-centric biases. Key configuration and bandwidth control steps rely on Windows-specific tools (MMC snap-in, registry edits, PowerShell cmdlets), with no Linux equivalents or guidance provided. Windows procedures and examples are presented first and in detail, while Linux is only briefly mentioned in the context of master target server deployment, with no operational examples or parity in tooling. This creates friction for Linux users, who lack clear instructions for critical steps.
Recommendations
  • Provide Linux-specific instructions for controlling bandwidth and configuring replication, including equivalent commands, configuration files, or tools.
  • Include Linux examples alongside Windows ones, especially for registry/configuration changes and process server setup.
  • Clarify which steps are OS-agnostic and which require OS-specific actions; offer alternatives for Linux/macOS users.
  • Document any limitations or required workarounds for Linux environments explicitly.
  • Ensure parity in screenshots and step-by-step guides for both Windows and Linux platforms.
GitHub Create Pull Request
Site Recovery Add Azure Automation runbooks to Site Recovery recovery plans ...cles/site-recovery/site-recovery-runbook-automation.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools Windows First
Summary
The documentation page exclusively provides PowerShell-based examples and scripts for Azure Automation runbooks in Site Recovery recovery plans. All code samples, variable manipulation, and module references are specific to PowerShell and AzureRM modules, which are primarily used on Windows. There are no Bash, Python, or cross-platform CLI examples, nor any mention of Linux/macOS scripting alternatives. The guidance assumes users are familiar with PowerShell and Windows-centric tooling, creating friction for Linux/macOS users.
Recommendations
  • Add equivalent examples using Azure CLI (az) and Bash scripts, which are natively supported on Linux/macOS.
  • Include guidance on using Python runbooks, which are supported in Azure Automation and widely used across platforms.
  • Explicitly state platform requirements and provide links to cross-platform tooling setup.
  • Reorder examples to present cross-platform options first or alongside PowerShell.
  • Reference Azure Automation's support for hybrid workers on Linux and provide relevant examples.
GitHub Create Pull Request
Site Recovery Set up disaster recovery for SQL Server with Azure Site Recovery .../blob/main/articles/site-recovery/site-recovery-sql.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation page exhibits a notable Windows bias. It consistently references Windows-specific technologies (such as Windows Failover Clustering, Task Manager, and PowerShell procedures) and links to Windows-focused SQL Server documentation. Examples and instructions for monitoring, failover, and recovery are tailored to Windows environments, with no explicit guidance or examples for Linux-based SQL Server deployments. Linux tools, commands, and operational patterns are absent, making it difficult for Linux users to follow or adapt the procedures.
Recommendations
  • Add explicit instructions and examples for SQL Server on Linux, including monitoring disk write rates using Linux tools (e.g., iostat, sar, or atop) instead of Task Manager.
  • Include PowerShell alternatives for Linux, such as Bash scripts or native Linux commands, for failover automation and cluster management.
  • Reference SQL Server documentation for Linux (e.g., Always On availability groups on Linux, Linux clustering) alongside or before Windows equivalents.
  • Clarify which steps are platform-agnostic and which require platform-specific adaptations, providing links or notes for Linux users.
  • Provide screenshots or walkthroughs using Linux environments where applicable.
GitHub Create Pull Request
Site Recovery About disaster recovery for on-premises apps with Azure Site Recovery .../main/articles/site-recovery/site-recovery-workload.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by prioritizing Windows workloads and tools (Active Directory, IIS, Exchange, SharePoint, Dynamics AX, RDS) in both the workload summary and detailed sections. Windows-specific technologies are described in detail, while Linux is mentioned only briefly and generically, with no Linux-specific examples, tools, or application scenarios. The documentation lacks parity in guidance for Linux workloads and applications, making it less useful for Linux-focused users.
Recommendations
  • Add detailed sections for Linux-specific workloads and applications (e.g., Apache, NGINX, MySQL, PostgreSQL, Samba, etc.), similar to the coverage given to Windows workloads.
  • Provide Linux-specific disaster recovery examples, including scripts, tools, and best practices for common Linux enterprise applications.
  • Ensure that tables and summaries list Linux workloads and applications with the same granularity as Windows workloads.
  • Include references to Linux-native HA/DR technologies (e.g., Pacemaker, Corosync, DRBD, etc.) and how they integrate with Azure Site Recovery.
  • Present examples and instructions for both Windows and Linux equally, or alternate which platform is shown first.
GitHub Create Pull Request
Site Recovery Enable VMware VMs (Modernized) for disaster recovery using Azure Site Recovery ...icles/site-recovery/vmware-azure-enable-replication.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell is referenced as the primary automation tool for enabling replication and managing disaster recovery tasks, with no mention of Linux/macOS equivalents (such as Bash, CLI, or REST API usage from non-Windows platforms). Windows-specific features (e.g., Azure Hybrid Benefit for Windows Server) are highlighted, and Windows terminology appears before or instead of cross-platform alternatives. There are no examples or guidance for Linux/macOS users, and the documentation assumes familiarity with Windows-centric tools and licensing.
Recommendations
  • Add explicit instructions and examples for Linux/macOS users, such as using Azure CLI or REST API for replication and management tasks.
  • Provide sample Bash scripts or command-line steps for common operations, alongside PowerShell examples.
  • Clarify which steps are platform-agnostic and which are Windows-specific, especially in sections discussing licensing benefits and automation.
  • Reference Linux support in prerequisites and troubleshooting, and link to relevant documentation for non-Windows environments.
  • Ensure that REST API usage is demonstrated with curl or similar tools, not just PowerShell.
  • Mention cross-platform tools (e.g., Azure CLI) before or alongside Windows tools.
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-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation presents Windows instructions and tooling first, with detailed registry and firewall steps, including explicit command-line examples (REG ADD) and references to Windows-specific tools (cspsconfigtool.exe, GPO, Windows Firewall). Linux instructions are provided but lack equivalent command-line examples and omit details for Linux-specific security/firewall configuration. Windows ports (SMB, WMI) are listed in the note, but Linux-relevant ports (SSH, SFTP) are not. The anti-virus exclusion example is Windows-only.
Recommendations
  • Present Linux and Windows instructions in parallel or alternate order to avoid Windows-first bias.
  • Add Linux command-line examples for editing sshd_config, restarting sshd, and managing firewall rules (e.g., using ufw, firewalld, or iptables).
  • Include Linux-specific anti-virus exclusion paths and instructions.
  • List Linux-relevant ports (e.g., 22 for SSH, SFTP) in the port requirements note.
  • Clarify if cspsconfigtool.exe is available for Linux or provide Linux alternatives.
  • Provide examples for Linux account creation and permissions analogous to Windows steps.
GitHub Create Pull Request
Site Recovery Install a master target server for Linux VM failback with Azure Site Recovery ...e-recovery/vmware-azure-install-linux-master-target.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
🔧 Windows Tools
Summary
The documentation is focused on installing and configuring a Linux master target server for Azure Site Recovery failback, with detailed Linux-specific instructions. However, there is a notable Windows bias in the section describing how to obtain the installer and passphrase: users are instructed to copy files from Windows paths (e.g., C:\Program Files (x86)\Microsoft Azure Site Recovery\...) on the process/configuration server, implying that the process/configuration server is expected to be Windows-based. No Linux-based alternatives or instructions are provided for these steps.
Recommendations
  • Provide instructions for obtaining the installer and passphrase from a Linux-based process/configuration server, if supported.
  • Clarify whether the process/configuration server must be Windows, or document Linux alternatives if available.
  • If Windows is required for these components, explicitly state this requirement early in the prerequisites.
  • Offer guidance for Linux users on how to access Windows shares or files (e.g., using smbclient, mount.cifs, or scp from a Windows server).
GitHub Create Pull Request
Site Recovery Manage a process server for VMware VMs/physical server disaster recovery in Azure Site Recovery ...es/site-recovery/vmware-azure-manage-process-server.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First Missing Linux Example
Summary
The documentation demonstrates a notable Windows bias. All command-line instructions use Windows-specific tools (cmd.exe, PowerShell, Windows folder paths like %PROGRAMDATA%), and examples reference only Windows environments. There are no Linux or macOS equivalents provided for any tasks, and anti-virus exclusions reference only Windows directories. This creates friction for administrators running process servers on Linux or non-Windows platforms.
Recommendations
  • Provide equivalent Linux/macOS instructions for all command-line tasks, including folder paths, command syntax, and service management (e.g., using systemctl for service restart).
  • Include Linux-specific anti-virus exclusion paths and guidance.
  • Offer PowerShell alternatives for Linux (PowerShell Core) or bash examples where applicable.
  • Clearly state platform requirements and limitations at the start of the documentation.
  • If process servers can only run on Windows, make this explicit; if Linux is supported, ensure parity in documentation.
GitHub Create Pull Request
Site Recovery Manage the configuration server for disaster recovery with Azure Site Recovery ...e-recovery/vmware-azure-manage-configuration-server.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits a notable Windows bias. Many operational examples and instructions rely on Windows-specific tools (PowerShell, .exe utilities, Windows command prompt, Windows file paths), and Windows-centric procedures are presented without Linux/macOS equivalents. PowerShell is used for critical tasks such as certificate renewal, server registration, and deletion, with no mention of Linux alternatives. The configuration server management appears to assume a Windows environment, and Linux users are left without clear guidance for performing these tasks.
Recommendations
  • Provide Linux/macOS equivalents for all command-line instructions, including certificate renewal, registration, and deletion.
  • Include examples using Bash, shell scripts, or cross-platform CLI tools where possible.
  • Clarify whether the configuration server can be deployed and managed on Linux, and if not, explicitly state this limitation.
  • If Windows-only tools are required, offer guidance for Linux users (e.g., using remote desktop, running commands via SSH, or using Azure CLI).
  • Add notes or sections highlighting differences in management for Linux-based environments.
GitHub Create Pull Request
Site Recovery Manage VMware vCenter servers in Azure Site Recovery .../articles/site-recovery/vmware-azure-manage-vcenter.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation consistently references the use of a Windows-only tool (_cspsconfigtool.exe_) and instructs users to access it via a Desktop shortcut, implying a Windows GUI environment. There are no instructions or examples for Linux-based configuration servers, nor any mention of command-line alternatives or parity for Linux/macOS users. The order and language assume Windows as the default platform.
Recommendations
  • Add instructions for managing the configuration server on Linux, including command-line alternatives to _cspsconfigtool.exe_ if available.
  • Clarify whether the configuration server can be run on Linux, and if so, provide equivalent steps for Linux environments.
  • If the tool is Windows-only, explicitly state this limitation and provide guidance for Linux/macOS users (e.g., remote management options, supported platforms).
  • Include screenshots or examples for Linux environments if supported.
GitHub Create Pull Request
Site Recovery Set up source settings for VMware disaster recovery to Azure with Azure Site Recovery ...n/articles/site-recovery/vmware-azure-set-up-source.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits a Windows bias by prioritizing Windows-specific instructions, tools, and file paths. Windows folders and registry keys are listed extensively and before Linux equivalents. Linux instructions are limited to a single section, and there are no Linux-specific setup or troubleshooting examples. The use of Windows terminology (e.g., C:\ paths, registry keys) dominates, while Linux guidance is minimal and appears last.
Recommendations
  • Provide Linux-specific setup instructions for the configuration server and process server, including file paths, commands, and troubleshooting steps.
  • List Linux exclusions alongside Windows exclusions, rather than after them, to promote parity.
  • Include Linux examples for antivirus exclusions, such as common Linux antivirus tools (e.g., ClamAV, Sophos) and how to configure them.
  • Clarify which steps apply to both Windows and Linux, and explicitly note any differences.
  • Add troubleshooting tips for Linux environments, similar to those provided for Windows.
GitHub Create Pull Request
Site Recovery Troubleshoot issues with the configuration server during disaster recovery of VMware VMs and physical servers to Azure by using Azure Site Recovery ...very/vmware-azure-troubleshoot-configuration-server.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation page exhibits a moderate Windows bias. Windows paths, tools, and troubleshooting steps are frequently mentioned first or exclusively, such as referencing Windows file locations, using Windows-specific tools (PsExec, Internet Explorer), and providing Windows command examples before Linux equivalents. Some troubleshooting steps and service names are Windows-centric, and certain procedures (e.g., vCenter proxy configuration) lack Linux alternatives or guidance. Linux instructions are present but often secondary or less detailed.
Recommendations
  • Provide Linux/macOS equivalents for all troubleshooting steps, especially where Windows tools (PsExec, Internet Explorer) are referenced.
  • List Linux and Windows examples side-by-side, or alternate which OS is presented first.
  • Include Linux file paths and service names wherever Windows paths/services are mentioned.
  • Clarify when steps are OS-specific and offer parity in detail and guidance for Linux/macOS users.
  • Add Linux-specific troubleshooting for proxy settings, service management, and log file locations.
GitHub Create Pull Request
Site Recovery Prepare VMware VMs for reprotection and failback with Azure Site Recovery ...rticles/site-recovery/vmware-azure-prepare-failback.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. Windows is mentioned first in several critical sections, such as the default master target server being Windows, and the retention drive instructions are more detailed for Windows than Linux. There is a focus on Windows-specific patterns (e.g., default retention drive is 'R' for Windows, Linux equivalent is mentioned but less detailed). Steps for adding drives and formatting are described in a Windows-centric way, and Linux instructions are less explicit. The documentation refers to Windows tools and patterns before Linux equivalents, and some Linux-specific steps are only briefly mentioned or linked, not described inline.
Recommendations
  • Provide Linux examples and instructions alongside Windows steps, not just as links.
  • Ensure parity in detail for Linux and Windows (e.g., formatting and mounting retention drives, default paths, and requirements).
  • Avoid assuming Windows as the default; clarify that either OS can be used and structure instructions accordingly.
  • Include explicit Linux command-line examples for tasks like adding and formatting retention drives.
  • List Linux and Windows options together in tables and step lists, rather than Windows first.
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-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page exhibits a notable Windows bias. Troubleshooting steps and log file paths are exclusively provided using Windows conventions (e.g., C:\Program Files, C:\ProgramData), and command-line instructions reference Windows tools (cmd, net stop/start). There are no Linux or macOS equivalents or examples, despite the possibility of running VMware VMs or physical servers on non-Windows platforms. This can create friction for Linux users attempting to troubleshoot replication issues, as they must adapt instructions without guidance.
Recommendations
  • Include Linux/macOS equivalents for log file locations and service management commands (e.g., systemctl, journalctl, /var/log paths).
  • Provide troubleshooting steps for common Linux distributions, especially for agent/service management and permissions.
  • Clarify whether the Azure Site Recovery Mobility agent and process server components are supported on Linux, and if so, link to relevant Linux documentation.
  • Present examples for both Windows and Linux platforms side-by-side, or clearly indicate platform-specific instructions.
  • Avoid using only Windows-specific folder paths and commands; use generic or platform-neutral language where possible.
GitHub Create Pull Request
Site Recovery Support matrix for VMware/physical disaster recovery in Azure Site Recovery. .../site-recovery/vmware-physical-azure-support-matrix.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation page exhibits Windows bias in several areas. The replication appliance for physical servers is only described as being set up via a PowerShell script, with no mention of a Linux alternative. The required OS for the replication appliance is Windows Server 2022 (English locale), with no Linux-based option. In deployment scenarios, PowerShell is explicitly mentioned for VMware VM disaster recovery, but not for Linux or cross-platform equivalents. Windows-specific tools and patterns (IIS, group policies, AD DS, etc.) are referenced in detail, while Linux equivalents are not discussed. Windows sections and requirements are often presented before Linux ones.
Recommendations
  • Provide instructions or alternatives for setting up the replication appliance on Linux, or explicitly state if this is not supported.
  • Include Linux-based automation examples (e.g., Bash scripts, CLI commands) alongside PowerShell for deployment and management tasks.
  • Clarify whether the replication appliance can only run on Windows, and if so, explain the rationale and possible workarounds for Linux environments.
  • Balance the order of presentation so Linux and Windows are treated equally in examples and requirements.
  • Where Windows tools (IIS, AD DS, group policies) are referenced, mention Linux equivalents or note their irrelevance for Linux users.
GitHub Create Pull Request
Site Recovery Scale VMware/physical disaster recovery with Azure Site Recovery ...cles/site-recovery/vmware-physical-large-deployment.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias. Windows-specific tools and patterns (such as PowerShell cmdlets and compliance preparation) are mentioned explicitly and given as actionable steps, while Linux equivalents are either omitted or referenced only in passing. Windows compliance is discussed in detail, with Linux compliance described as automatic and not actionable. The only example of automation for failover uses a Windows PowerShell cmdlet, with no Linux CLI or automation alternatives provided.
Recommendations
  • Include Linux/macOS CLI examples (e.g., Azure CLI, Bash scripts) alongside PowerShell for critical operations such as triggering failover.
  • Provide actionable steps for Linux VM compliance preparation, not just stating that it is automatic.
  • Mention Linux-specific tools or patterns where relevant (e.g., how to automate tasks on Linux VMs during failover).
  • Ensure that instructions for setting up configuration and process servers are platform-agnostic or provide both Windows and Linux procedures.
  • Where automation is discussed (e.g., Azure Automation runbooks), clarify how Linux users can integrate their scripts or tools.
GitHub Create Pull Request
Site Recovery Troubleshoot Mobility Service push installation with Azure Site Recovery ...ite-recovery/vmware-azure-troubleshoot-push-install.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation page exhibits a notable Windows bias. Troubleshooting steps and examples are frequently presented for Windows first, with detailed instructions using Windows-specific tools (e.g., registry editor, netsh, net user, Control Panel, Task Manager, Windows Services, VSS, DCOM, COM+). Linux instructions are present but often less detailed, sometimes missing entirely (e.g., for network shares, VSS, and some error codes), or relegated to secondary notes. Windows tools and patterns (registry edits, firewall rules, service management) are described in depth, while Linux equivalents are not always provided or are brief.
Recommendations
  • Ensure every troubleshooting step and example has a Linux equivalent, presented with equal detail and clarity.
  • Present Linux and Windows instructions side-by-side or in parallel tabs, rather than Windows-first.
  • Include Linux-specific troubleshooting for network shares, service management, firewall configuration, and agent installation errors.
  • Provide Linux command-line examples (e.g., using systemctl, firewall-cmd/ufw, SSH/SFTP configuration, checking disk space and memory) wherever Windows commands are given.
  • Reference Linux logs and error locations, and provide guidance for common Linux issues (e.g., SELinux/AppArmor, systemd service failures, package dependencies).
  • Avoid referencing only Windows documentation or support articles; include links to Linux resources.
GitHub Create Pull Request
Site Recovery Prepare for VMware VM disaster recovery with Azure Site Recovery ...-recovery/vmware-azure-tutorial-prepare-on-premises.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation displays a moderate Windows bias: Windows instructions and tools (such as registry edits, Windows Firewall, RDP, and update management) are described in greater detail and appear before Linux equivalents. Linux steps are present but less detailed, and Windows-specific troubleshooting and configuration (e.g., registry, SAN policy, firewall) are emphasized.
Recommendations
  • Provide Linux instructions with equal detail, including troubleshooting steps and configuration (e.g., SELinux, iptables/firewalld, SSH configuration).
  • List Linux and Windows steps side-by-side or in parallel sections, rather than Windows first.
  • Include Linux-specific caveats (e.g., handling pending updates, boot diagnostics, mount point issues) similar to Windows.
  • Reference Linux tools and commands (e.g., systemctl, ufw, journalctl) where appropriate.
  • Add links to Linux troubleshooting resources, not just Windows.
  • Clarify that both OS types are supported and highlight any differences in process.
GitHub Create Pull Request
Site Recovery Troubleshoot the Azure Site Recovery process server ...y/vmware-physical-azure-troubleshoot-process-server.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits a notable Windows bias. Troubleshooting steps, tool references, and file paths are almost exclusively Windows-centric (e.g., Telnet client installation instructions reference Windows Server, logs and agent paths use Windows directory conventions, and troubleshooting steps rely on Windows tools like Task Manager and Resource Monitor). There are no explicit Linux/macOS examples or guidance, despite the process server potentially running on non-Windows platforms in some scenarios.
Recommendations
  • Add equivalent troubleshooting steps and examples for Linux-based process servers, including log file locations, service management commands (e.g., systemctl), and network troubleshooting tools (e.g., netcat, ss, lsof).
  • Provide Linux/macOS commands for checking connectivity (e.g., nc or curl instead of Telnet), and clarify how to interpret results on those platforms.
  • Include instructions for viewing and managing services on Linux (e.g., systemctl status <service>), and mention where relevant logs are located on Linux.
  • When referencing file paths, provide both Windows and Linux paths, or clarify platform-specific differences.
  • Ensure that any screenshots or UI instructions (e.g., Task Manager, Resource Monitor) have Linux/macOS equivalents or note their absence.
GitHub Create Pull Request
Site Recovery Manage the Mobility agent for VMware/physical servers with Azure Site Recovery ...te-recovery/vmware-physical-manage-mobility-service.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation shows a moderate Windows bias. Powershell-based update instructions are provided only for Windows, with no equivalent Linux command-line example. Windows uninstall instructions are more detailed and presented first, including both UI and command-line methods, while Linux uninstall instructions are simpler and shown after Windows. The VSS provider section is Windows-only, with no mention of Linux alternatives or clarification that it's not applicable. Linux users may need to refer to other pages for parity, and may experience friction due to missing or less detailed Linux-specific guidance.
Recommendations
  • Provide equivalent Linux command-line examples for updating the Mobility agent (e.g., shell script or CLI commands).
  • Present Windows and Linux instructions in parallel sections, or alternate which is shown first.
  • Clarify applicability of VSS provider installation for Linux (e.g., explicitly state if not required or provide Linux steps if available).
  • Ensure manual update instructions for Linux are as detailed as those for Windows, including example commands.
  • Add troubleshooting or common issues for Linux environments.
GitHub Create Pull Request
Site Recovery Troubleshoot VMware mobility agent health errors in Azure Site Recovery ...-recovery/vmware-troubleshoot-mobility-agent-health.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation provides both Linux and Windows log file locations, but error messages and troubleshooting steps frequently reference Windows-style paths, hostnames, and service names (e.g., 'C:\', 'WIN-xxxx', 'Microsoft Azure RCM Proxy Agent'). Service restart instructions only mention Windows service names, with no Linux equivalents or commands (such as systemctl) provided. Windows hostnames and paths appear first in error logs and examples, and Linux-specific troubleshooting commands or service names are missing.
Recommendations
  • Include Linux service names and restart instructions (e.g., systemctl restart <service>) alongside Windows service steps.
  • Provide Linux-specific error message examples and troubleshooting commands where relevant.
  • Alternate the order of Windows and Linux examples, or present them side-by-side for parity.
  • Clarify which steps apply to Linux, Windows, or both, especially when referencing service names and log locations.
  • Add explicit Linux troubleshooting guidance for agent/service restart and configuration.
GitHub Create Pull Request
Site Recovery Shared disks in Azure Site Recovery ...ob/main/articles/site-recovery/tutorial-shared-disk.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation is heavily focused on Windows Server Failover Clusters (WSFC) and does not mention or provide guidance for Linux-based clustering solutions or scenarios. All examples, prerequisites, and terminology are centered around Windows, with no reference to Linux equivalents or support.
Recommendations
  • Explicitly state whether Linux-based clusters (e.g., Pacemaker, Corosync) are supported or not. If not supported, clarify this early in the documentation.
  • If Linux shared disk clustering is supported, add equivalent instructions, prerequisites, and examples for Linux clusters.
  • Include references to Linux documentation or guides for setting up shared disks and disaster recovery with Azure Site Recovery.
  • Balance the language and examples so that both Windows and Linux administrators can follow the steps relevant to their environments.
  • If only Windows is supported, consider renaming the article or adding a scope note to avoid misleading Linux users.
GitHub Create Pull Request
Site Recovery Automatic update of the Mobility service in Azure Site Recovery ...in/articles/site-recovery/azure-to-azure-autoupdate.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example
Summary
The documentation page provides only Azure PowerShell script examples for managing automatic updates of the Mobility service in Azure Site Recovery. There are no equivalent examples or instructions for Linux-based automation (such as Bash, Azure CLI, or Python), nor is there any mention of Linux-specific tools or patterns. The troubleshooting and manual update instructions are also presented in a platform-neutral way, but the only script provided is Windows/PowerShell-centric.
Recommendations
  • Add equivalent Azure CLI and Bash script examples for managing automatic updates, targeting Linux administrators.
  • Explicitly mention that the PowerShell script can be run on Linux (if supported via PowerShell Core), or provide alternative instructions for Linux environments.
  • Include guidance for using Python SDKs or REST API calls for automation, which are platform-agnostic.
  • Clarify any platform dependencies or limitations for the provided scripts and tools.
  • Ensure that examples for both Windows and Linux are presented side-by-side or in separate sections for parity.
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-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation consistently references Azure portal and PowerShell for configuration steps, with no mention of Linux-specific tools or CLI commands (such as Azure CLI on bash). All examples and screenshots are based on the Azure portal, which is platform-agnostic but often associated with Windows workflows. There are no Linux shell or cross-platform command-line examples, nor any references to Linux-specific considerations for DNS, networking, or permissions. The documentation implicitly assumes a Windows-centric approach by omitting Linux alternatives.
Recommendations
  • Add Azure CLI (az) command examples for all major steps, especially for creating private endpoints, DNS zones, and role assignments.
  • Explicitly mention that all steps can be performed from Linux, macOS, or Windows, and provide parity in instructions for each platform.
  • Include references to Linux-specific networking and DNS tools (e.g., dig, nslookup) for verification steps.
  • Provide guidance on scripting these operations in bash or other Linux shells, and link to relevant cross-platform automation documentation.
  • Clarify that PowerShell is available cross-platform, but also offer bash/CLI alternatives for users who prefer Linux environments.
GitHub Create Pull Request
Site Recovery Moving Azure VMs to another region with Azure Site Recovery ...articles/site-recovery/azure-to-azure-move-overview.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation page exhibits mild Windows bias. In the 'Typical architectures for a multi-tier deployment' section, the link for 'Availability sets' points specifically to the Windows VM documentation, rather than a general or Linux-specific equivalent. The example database tier uses SQL Server Always On, a Windows-centric technology, without mentioning Linux alternatives. No explicit Linux VM examples, tools, or patterns are provided, and Windows terminology appears first or exclusively in some cases.
Recommendations
  • Provide parallel examples and links for Linux VMs, such as linking to Linux availability set documentation.
  • Mention Linux-supported database solutions (e.g., MySQL, PostgreSQL with high availability) alongside SQL Server Always On.
  • Ensure terminology and examples are platform-neutral or include both Windows and Linux scenarios.
  • Add notes or sections highlighting any differences or considerations for Linux VM moves with Azure Site Recovery.
GitHub Create Pull Request
← Previous Page 28 of 35 Next →