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 326-350 of 864 flagged pages
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/vmware-azure-exclude-disk.md ...in/articles/site-recovery/vmware-azure-exclude-disk.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 Windows bias by providing specific details about Windows failback behavior before Linux, referencing 'Windows disks' and their handling, and omitting concrete Linux-specific examples or instructions. The failback section describes Windows behavior first and in more detail, while Linux is mentioned only in passing, and there are no Linux command-line or tool references. No Linux-specific troubleshooting, patterns, or examples are provided.
Recommendations
  • Provide Linux-specific examples and scenarios, including screenshots or step-by-step instructions for Linux VMs.
  • Include parity in failback documentation, describing Linux behavior with equal detail and clarity as Windows.
  • Reference Linux tools or commands where relevant, such as shell commands for disk management or Mobility service installation.
  • Ensure that both Windows and Linux are mentioned together in all relevant sections, rather than prioritizing Windows.
  • Add troubleshooting tips and best practices for Linux environments, matching those given for Windows.
GitHub Create Pull Request
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/vmware-azure-install-mobility-service.md ...site-recovery/vmware-azure-install-mobility-service.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 presents Windows instructions before Linux, uses Windows-specific tools and terminology (e.g., registry edits, GPO, cspsconfigtool.exe), and provides detailed Windows firewall and anti-virus steps while omitting equivalent Linux commands and security guidance. Linux instructions lack parity in example commands and troubleshooting details.
Recommendations
  • Present Linux and Windows instructions in parallel or alternate the order to avoid Windows-first bias.
  • Include Linux-specific examples for firewall configuration (e.g., using ufw, firewalld, or iptables) and anti-virus exclusions (e.g., for ClamAV or other common Linux AV tools).
  • Provide Linux command-line equivalents for steps such as adding accounts, restarting services, and verifying connectivity.
  • Clarify if cspsconfigtool.exe has a Linux-compatible version or provide alternative Linux-native tooling or commands.
  • List required ports for Linux systems and provide example commands to open them.
  • Expand troubleshooting and security guidance for Linux environments to match the detail given for Windows.
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-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 a strong Windows bias. All command-line examples use Windows-specific tools (cmd.exe, PowerShell), Windows environment variables (%PROGRAMDATA%), and Windows file paths (C:\...). There are no Linux equivalents or instructions for managing process servers on Linux, nor any mention of Linux-specific tools or patterns. Anti-virus exclusions and proxy settings are described only for Windows environments.
Recommendations
  • Provide equivalent Linux instructions for all command-line operations, including registration, proxy settings, and service management (e.g., using bash, systemctl, Linux file paths).
  • Include examples using Linux shell commands and environment variables.
  • Mention Linux anti-virus exclusion paths and patterns where relevant.
  • Clarify platform support for process servers (e.g., whether Linux is supported, and if not, state this explicitly).
  • Present instructions for both Windows and Linux environments side-by-side, or clearly indicate platform-specific sections.
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-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 by consistently referencing Windows tools (such as Configuration Manager/SMB shares), presenting Windows instructions and scripts before Linux equivalents, and relying on Windows-centric patterns (e.g., administrative command prompt, .bat scripts, registry edits). Linux instructions are present but often as secondary, and there is a lack of parity in some areas (e.g., uninstall instructions are only given for Windows, not Linux). The overall workflow assumes a Windows-centric environment for orchestration and deployment.
Recommendations
  • Present Linux and Windows instructions/examples in parallel or in alternating order to avoid always listing Windows first.
  • Include Linux-native deployment tools (e.g., Ansible, Puppet, Chef) as alternatives to Configuration Manager and JetPatch.
  • Provide explicit Linux uninstall instructions and scripts, not just for Windows.
  • Reference Linux file sharing solutions (e.g., NFS, SFTP) alongside SMB shares.
  • Avoid assuming the use of Windows administrative command prompts; provide equivalent Linux shell commands where relevant.
  • Where screenshots or UI steps are shown, clarify if/when they differ for Linux environments.
  • Expand on Linux-specific troubleshooting and automation scenarios to match the depth given for Windows.
GitHub Create Pull Request
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/vmware-azure-prepare-failback.md ...rticles/site-recovery/vmware-azure-prepare-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 Windows Heavy Examples
Summary
The documentation page demonstrates a Windows bias by consistently mentioning Windows master target servers first, providing more detail for Windows-specific steps (such as retention drive setup), and referencing Windows tools and conventions before their Linux equivalents. While Linux options are mentioned, they are often secondary and lack equivalent depth or step-by-step guidance. Windows-centric terminology and instructions (e.g., 'R volume' for retention, Windows-specific master target server creation) are more prominent, and Linux instructions are less detailed.
Recommendations
  • Present Windows and Linux options with equal prominence and detail, including step-by-step instructions for both platforms.
  • Avoid listing Windows examples or tools before Linux equivalents; alternate or group them together.
  • Expand Linux-specific instructions, such as retention drive setup, to match the detail provided for Windows.
  • Ensure that all references to master target server requirements, limitations, and configuration steps are equally covered for Linux.
  • Include explicit Linux command-line examples or configuration steps where Windows-specific instructions are given.
  • Add troubleshooting and best practices sections for Linux environments, similar to those for Windows.
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-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 page exhibits a clear Windows bias. Windows-specific licensing, tools, and command-line examples (such as PowerShell and Windows command paths) are presented exclusively or before any Linux alternatives. Windows tools like DISM, CSPSConfigtool.exe, and PowerShell commands are referenced throughout, with no Linux equivalents or instructions provided. Steps involving file paths, executables, and registry edits are all Windows-centric, and there are no bash, shell, or Linux-specific examples for managing the configuration server, despite the mention of Linux physical servers as supported workloads.
Recommendations
  • Add Linux-specific instructions and examples for all management tasks, including command-line operations, credential management, and certificate renewal.
  • Provide bash/shell command equivalents for PowerShell examples, especially for tasks like registration, deletion, and certificate renewal.
  • Include guidance for Linux file paths and tools (e.g., systemctl for service management, openssl for certificate handling) where Windows tools are referenced.
  • Clarify which steps are OS-agnostic and which require OS-specific procedures, and present both Windows and Linux options side-by-side.
  • Reference Linux licensing and activation considerations if relevant, or explicitly state 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-troubleshoot-configuration-server.md ...very/vmware-azure-troubleshoot-configuration-server.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 bias in several ways: Windows file paths, tools, and troubleshooting steps are consistently presented first or exclusively, with Linux equivalents sometimes missing or less detailed. Windows-specific tools (e.g., PsExec, Internet Explorer, IIS) are referenced without Linux alternatives. Some troubleshooting and service management instructions are tailored for Windows, and Linux guidance is often relegated to later sections or provided with less detail.
Recommendations
  • Ensure Linux troubleshooting steps are presented alongside Windows instructions, with equal detail and clarity.
  • Provide Linux equivalents for Windows-only tools (e.g., suggest 'sudo' or 'systemctl' for service management, alternatives to PsExec, and browser usage on Linux).
  • Include Linux file paths and commands wherever Windows paths are mentioned, especially for log files and configuration changes.
  • Avoid referencing Windows tools (like Internet Explorer, IIS, PsExec) without mentioning Linux alternatives (e.g., Firefox, Apache/nginx, native Linux utilities).
  • Present Windows and Linux instructions in parallel, rather than Windows-first, to reinforce cross-platform parity.
  • Add explicit Linux examples for database access, service management, and agent registration where currently only Windows instructions are provided.
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-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 bias by consistently presenting Windows-specific troubleshooting steps, tools, and examples before Linux equivalents. Windows registry edits, firewall settings, and service management are described in detail, often with command-line instructions and references to Windows tools (e.g., regedit, netsh, net user, Netlogon, File Explorer, Control Panel). Linux troubleshooting is covered less thoroughly, with fewer step-by-step instructions and limited use of Linux-native tools. Some sections (e.g., VSS troubleshooting, network shares) lack Linux-specific guidance or examples entirely.
Recommendations
  • Provide Linux-first or parallel troubleshooting steps for each error, ensuring parity in detail and clarity.
  • Include Linux command-line equivalents for all Windows commands (e.g., registry edits, service management, network share access).
  • Add Linux-specific troubleshooting for areas currently focused on Windows, such as VSS installation, network shared folders, and driver issues.
  • Reference Linux documentation and tools (e.g., systemctl, journalctl, SSH/SFTP configuration, mount, blkid) alongside Windows tools.
  • Ensure screenshots and walkthroughs are available for both Windows and Linux environments.
  • Explicitly mention when a troubleshooting step is Windows-only, and provide alternative steps for Linux where applicable.
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-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 prioritizing Windows-specific instructions and folder paths, especially in the antivirus exclusions section, where Windows directories are listed first and in much greater detail than Linux equivalents. The configuration server setup also references Windows licensing requirements without mentioning Linux alternatives. Linux instructions are minimal and appear after extensive Windows guidance.
Recommendations
  • Provide Linux-specific setup instructions and examples alongside Windows steps, especially for configuration server deployment.
  • List Linux antivirus exclusion paths before or alongside Windows paths, and ensure parity in detail and explanation.
  • Clarify whether the configuration server can be deployed on Linux, and if so, provide licensing and setup details for Linux.
  • Include Linux registry/file system equivalents or note when certain steps are Windows-only.
  • Add PowerShell and Bash/CLI examples for any command-line steps, ensuring both platforms are represented.
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-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 demonstrates a Windows bias by mentioning Windows VM behavior before Linux equivalents, providing more detailed troubleshooting steps for Windows (e.g., static IP recovery), and referencing Windows-specific tools and scenarios (e.g., Windows Server 2008 R2 SP1 failback limitations) without equivalent Linux coverage. Linux troubleshooting is less detailed, and Linux-specific tools or patterns are not discussed.
Recommendations
  • Provide Linux-specific troubleshooting steps and examples, especially for common issues like static IP recovery and package management.
  • Include parity in error resolution instructions for both Windows and Linux VMs, such as how to check and restart services on Linux (systemd, service commands) and how to verify network settings.
  • Mention Linux tools and patterns (e.g., using SSH, systemctl, journalctl) alongside Windows tools (e.g., Telnet, PowerShell), and ensure examples are given for both platforms.
  • Avoid listing Windows scenarios or limitations before Linux equivalents; present both platforms equally or group by OS.
  • Add explicit Linux failback limitations if any exist, to match the detail provided for Windows.
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-09 00:34
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 step-by-step instructions tailored to Windows environments, and omitting any Linux equivalents or examples. The troubleshooting steps assume the administrator is using Windows, with no mention of how to perform similar tasks on Linux-based configuration servers or vCenter deployments.
Recommendations
  • Add equivalent troubleshooting steps for Linux environments, such as using 'sudo -u' or 'su' to access the system user context.
  • Provide instructions for modifying proxy settings on Linux (e.g., editing environment variables, system-wide proxy config files, or using desktop environments like GNOME/KDE).
  • Include Linux command-line examples for interacting with the configuration server and DRA provider.
  • Mention relevant Linux tools (such as 'curl', 'wget', or configuration file paths) alongside Windows tools.
  • Clarify whether the instructions apply only to Windows-based configuration servers, and if so, provide a separate section for Linux-based deployments.
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-09 00:34
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 primary management tool and mentioning portal-based actions before alternatives. There is no mention of Linux-native management tools or CLI examples, and the language assumes familiarity with Windows-centric workflows. Linux support is only referenced in passing (mobility agent support for new Linux distros), without actionable guidance or parity in examples.
Recommendations
  • Include Linux CLI (e.g., Bash, Azure CLI) examples alongside or before PowerShell commands.
  • Explicitly mention Linux management options for Azure Site Recovery, such as using shell scripts or Linux-based automation.
  • Provide guidance for Linux administrators, including steps for managing replication and migration from Linux environments.
  • Ensure that references to tools and workflows are platform-neutral or offer parallel instructions for both Windows and Linux users.
  • Highlight Linux support and compatibility in remediation steps, not just as a future feature.
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-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 page demonstrates a clear Windows bias. Troubleshooting steps and examples consistently reference Windows tools (e.g., Task Manager, Resource Monitor, Control Panel, registry keys, Windows file paths), and all command-line examples use Windows syntax. There are no Linux equivalents or instructions for users running the process server or source machines on Linux, nor are Linux troubleshooting tools or file paths mentioned.
Recommendations
  • Add Linux-specific troubleshooting steps and examples, including equivalent commands for checking services, logs, and network connectivity (e.g., using systemctl, journalctl, netstat, lsof, tail, etc.).
  • Include Linux file paths for logs and configuration files where relevant.
  • Provide instructions for using Linux tools (such as top, htop, df, iptables, curl, etc.) for monitoring resource usage, checking connectivity, and managing firewall settings.
  • Mention how to check and configure proxy settings on Linux (e.g., environment variables, configuration files).
  • Ensure parity in screenshots and UI references by including Linux desktop or command-line equivalents where possible.
  • Clarify which steps are OS-agnostic and which require OS-specific instructions, and organize troubleshooting sections to address both Windows and Linux environments.
GitHub Create Pull Request
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/vmware-physical-manage-mobility-service.md ...te-recovery/vmware-physical-manage-mobility-service.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 demonstrates a Windows bias in several ways: PowerShell is the only scripting example given for agent updates, Windows uninstall instructions are more detailed and presented first, and Windows-specific tools (Control Panel, MsiExec.exe, VSS provider scripts) are described in depth. Linux instructions are present but less detailed and lack parity in scripting examples for agent updates. The manual update section is generic and does not provide Linux-specific command-line examples.
Recommendations
  • Provide equivalent Linux shell script examples for updating the Mobility agent, similar to the PowerShell example for Windows.
  • Present uninstall instructions for Windows and Linux in parallel, with equal detail and prominence.
  • Include Linux-specific tools and patterns (e.g., systemd service management, package manager commands) where relevant.
  • Add guidance for manual agent updates on Linux, including example commands for common distributions.
  • Ensure that instructions for both platforms are equally detailed and easy to follow, avoiding Windows-first ordering.
GitHub Create Pull Request
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/vmware-azure-tutorial-prepare-on-premises.md ...-recovery/vmware-azure-tutorial-prepare-on-premises.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 consistently presenting Windows instructions and tools before Linux equivalents, providing more detailed steps for Windows (such as registry edits and firewall settings), and referencing Windows-specific tools (e.g., Windows Firewall, RDP, registry keys) without offering Linux-specific command examples or tool references. Linux instructions are generally less detailed and lack parity in troubleshooting and configuration guidance.
Recommendations
  • Present Linux and Windows instructions in parallel, giving equal detail and prominence to both.
  • Include Linux-specific troubleshooting steps and configuration examples (e.g., SELinux, iptables, systemd service management, SSH configuration).
  • Reference Linux tools and commands explicitly (e.g., show how to open SSH port using firewalld or ufw, how to check SSH service status, how to handle pending updates on Linux).
  • Provide example commands for Linux account preparation and Mobility service installation, similar to the Windows registry example.
  • Ensure that troubleshooting links and tips are available for both platforms, not just Windows.
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-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 bias in several areas: deployment and appliance setup instructions prioritize Windows and PowerShell, requirements for the replication appliance are exclusively Windows-based, and Windows tools and patterns (such as IIS, AD DS, and PowerShell scripts) are referenced without Linux equivalents or alternatives. Linux support is present and detailed for OS/kernel compatibility, but operational and deployment guidance is Windows-centric, with no Linux-specific setup examples or instructions.
Recommendations
  • Provide Linux-based deployment and configuration examples alongside PowerShell, such as Bash scripts or CLI commands for appliance setup.
  • Document how to set up the replication appliance on a Linux host, or clarify if this is unsupported.
  • List Linux alternatives for required Windows roles/tools (e.g., IIS, AD DS) or explicitly state their necessity and lack of Linux support.
  • Add Linux-specific troubleshooting, operational, and management guidance to match the detail given for Windows.
  • Where PowerShell is referenced, include Azure CLI or other cross-platform alternatives for Linux administrators.
  • Clarify in the documentation whether the replication appliance can only run on Windows, and if so, provide rationale and guidance for Linux environments.
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-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation demonstrates several Windows biases: PowerShell is the only automation example provided 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 machines are only briefly mentioned and lack proactive guidance. Troubleshooting and automation references focus on Windows tools and patterns. There are no Linux-specific examples or parity in scripting, monitoring, or compliance preparation.
Recommendations
  • Provide equivalent Linux CLI (az CLI, Bash) examples for key operations such as triggering failover, alongside PowerShell.
  • Add proactive compliance preparation steps for Linux machines, similar to those described for Windows, including links to relevant troubleshooting and configuration guides.
  • Include Linux-specific automation and scripting references (e.g., sample Bash scripts, Ansible playbooks) for disaster recovery tasks.
  • Ensure troubleshooting and monitoring sections include Linux-centric guidance and examples.
  • When listing steps or tools, present Windows and Linux options together, or alternate their order to avoid implicit prioritization.
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-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 troubleshooting steps that exclusively use PowerShell commands and Windows file paths. There is no mention of Linux equivalents, nor are alternative instructions provided for Linux-based environments. The use of Windows-specific tools (e.g., Microsoft Appliance configuration manager, PowerShell scripts in C:\Program Files) further reinforces this bias, and Windows instructions are presented as the default and only method.
Recommendations
  • Include troubleshooting steps for Linux-based replication appliances, if supported.
  • Provide equivalent Bash or shell script examples for Linux environments.
  • Mention and document Linux-compatible tools or interfaces for managing the replication appliance.
  • Clearly state platform requirements and limitations at the beginning of the article.
  • If the appliance is Windows-only, explicitly clarify this to avoid confusion for Linux administrators.
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-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 consistently listing Windows file paths and tools before Linux equivalents, referencing Windows-specific services and error logs, and omitting Linux-specific troubleshooting steps (such as service names or restart commands). Linux guidance is limited to log file locations, with no parity in troubleshooting commands or service management instructions.
Recommendations
  • Present Linux and Windows instructions in parallel, giving equal prominence to both platforms.
  • Include Linux-specific service names and commands (e.g., systemctl restart <service>) where Windows services are mentioned.
  • Provide troubleshooting examples for Linux environments, such as checking service status, restarting services, and handling certificates using Linux tools.
  • When listing file paths or commands, alternate the order or present both together to avoid Windows-first ordering.
  • Reference Linux equivalents for all Windows tools and patterns (e.g., mention journalctl/logrotate for logs, systemd for services).
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-09 00:34
Reviewed by: LLM Analysis
Issues: 5 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Windows Path Examples Powershell Heavy Windows Ui Focus
Summary
The documentation demonstrates a moderate Windows bias. Windows examples, paths, and UI screenshots are consistently presented first and in greater detail. Windows-centric tools, folder structures (e.g., C:\Program Files), and installation instructions dominate, with Linux equivalents often appearing after or in less detail. UI-based installation instructions and screenshots are almost exclusively Windows-focused. Some sections, such as antivirus exclusions and installer repository paths, use Windows paths and terminology without Linux parity. While Linux instructions are present and reasonably complete, the overall structure and emphasis favor Windows environments.
Recommendations
  • Alternate the order of Windows and Linux instructions/examples to avoid always presenting Windows first.
  • Provide Linux UI screenshots where applicable, or clarify if UI is Windows-only.
  • Include Linux-specific notes for antivirus exclusions and repository paths (e.g., /usr/local/ASR).
  • Ensure all command-line examples for Windows have direct Linux equivalents and vice versa.
  • Use neutral language and folder naming in generic instructions (e.g., 'local folder' instead of 'C:\Program Files').
  • Add parity in troubleshooting and prerequisite sections, ensuring Linux issues and solutions are equally covered.
  • Where Windows-specific tools or patterns (e.g., VSS) are mentioned, clarify Linux alternatives or note if not applicable.
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-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 demonstrates a Windows bias in several ways. Windows operating systems are listed first and in more detail than Linux equivalents. Instructions for preparing Windows VMs include explicit registry edits and firewall configuration using Windows-specific tools (e.g., REG ADD, wf.msc), while Linux instructions are less detailed and lack command-line examples. The use of Windows-centric terminology (e.g., RDP, GPO) is prevalent, and references to Windows services (like VSS) are made without Linux alternatives. Linux steps are present but less comprehensive, and there are missing Linux command-line examples for key actions.
Recommendations
  • Provide Linux command-line examples for all steps, such as editing /etc/ssh/sshd_config, restarting sshd, and verifying network connectivity.
  • List Linux operating systems and requirements before or alongside Windows, not after.
  • Include Linux equivalents for Windows-specific tools and patterns (e.g., show how to open firewall ports using ufw or firewalld).
  • Reference Linux snapshot and consistency mechanisms (e.g., fsfreeze, LVM snapshots) when discussing app-consistent snapshots, or clarify their absence.
  • Avoid using Windows-centric terminology exclusively; provide Linux alternatives (e.g., SSH instead of RDP for remote access).
  • Ensure parity in troubleshooting and advanced configuration guidance for both platforms.
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-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page exhibits a Windows bias by providing only PowerShell-based scripting examples for key operations (such as copying disk encryption keys), referencing the use of 'Windows PowerShell application' explicitly, and omitting equivalent Linux shell or CLI instructions. The guidance and troubleshooting steps are written with a Windows-centric approach, and there are no Linux-specific examples or parity for key management tasks, despite mentioning limited support for Linux VMs.
Recommendations
  • Provide equivalent Bash/CLI examples for copying disk encryption keys, using Azure CLI or REST API from Linux/macOS environments.
  • Explicitly mention and demonstrate how Linux administrators can perform key vault operations, including permissions management and key copying.
  • Clarify any OS-specific limitations and offer alternative procedures for Linux VMs where PowerShell is not available or practical.
  • Ensure that all scripting and automation steps are cross-platform, or provide clear guidance for both Windows and Linux users.
  • Add troubleshooting steps and examples relevant to Linux environments, such as common permission errors encountered via Azure CLI.
GitHub Create Pull Request
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/azure-to-azure-autoupdate.md ...in/articles/site-recovery/azure-to-azure-autoupdate.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page provides only Azure PowerShell script examples for managing Mobility service updates, with no mention of Linux shell equivalents (such as Bash/CLI). The scripting and troubleshooting sections are heavily oriented toward Windows-centric tools and patterns, such as PowerShell and Run As accounts, without guidance for Linux administrators or cross-platform automation. There is no indication of how to perform these actions using Azure CLI, Bash, or other Linux-native tools.
Recommendations
  • Provide equivalent Azure CLI (az) or Bash script examples for managing Mobility service updates, alongside PowerShell.
  • Clarify whether the PowerShell script can be run on Linux (e.g., via PowerShell Core), or provide platform-agnostic instructions.
  • Include troubleshooting steps and automation guidance relevant to Linux environments, such as using cron jobs or shell scripts.
  • Explicitly mention cross-platform support and direct Linux users to appropriate tools and documentation.
  • Add a section comparing Windows and Linux approaches for managing Mobility service updates, highlighting any differences.
GitHub Create Pull Request
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/how-to-enable-replication-proximity-placement-groups.md ...tps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/how-to-enable-replication-proximity-placement-groups.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 Windows First Missing Linux Example
Summary
The documentation page demonstrates a strong Windows bias. All command-line examples are provided exclusively using Azure PowerShell, which is most commonly used on Windows and is less native to Linux environments. There are no CLI (az CLI) or Bash examples, which are preferred by Linux users. The documentation references Windows-centric tools and patterns (e.g., PowerShell, Hyper-V) and links to Windows-specific pages before Linux equivalents. Linux is only mentioned in passing, such as in the caution about CentOS EOL, and not in example commands or workflows.
Recommendations
  • Add equivalent Azure CLI (az CLI) and Bash examples for all PowerShell commands, especially for replication setup and monitoring.
  • Include explicit instructions and screenshots for Linux users, such as using the Azure portal from Linux browsers or running CLI commands in Bash.
  • Reference both Windows and Linux documentation pages equally, and avoid linking to Windows-specific guides before Linux ones.
  • Highlight any OS-specific considerations (e.g., differences in disk handling, failover behavior) for both Windows and Linux VMs.
  • Clarify that Azure PowerShell can be used cross-platform, but provide guidance for installing and using it on Linux and macOS, or suggest CLI alternatives.
GitHub Create Pull Request
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/hyper-v-deployment-planner-overview.md ...s/site-recovery/hyper-v-deployment-planner-overview.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 is heavily biased towards Windows environments. All examples, prerequisites, and instructions are specific to Windows Server (2012 R2/2016), PowerShell, and Windows-based tools. There is no mention of Linux support, Linux equivalents, or cross-platform usage. The deployment planner tool appears to require Windows, and all operational guidance assumes a Windows-only environment.
Recommendations
  • Explicitly state platform limitations at the beginning of the documentation, clarifying if Linux is unsupported.
  • If possible, provide Linux-compatible tooling or document alternative approaches for Linux environments.
  • Include examples and instructions for Linux-based management (e.g., using SSH, Bash, or cross-platform .NET tools) if the tool supports it.
  • Mention VMware scenarios with Linux hosts if relevant, and clarify any differences in usage or requirements.
  • If the tool is Windows-only, suggest workarounds for Linux users (such as running the tool in a Windows VM or container).
GitHub Create Pull Request
← Previous Page 14 of 35 Next →