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 626-650 of 864 flagged pages
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-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation frequently references Windows-specific file paths, services, and command-line tools (e.g., C:\Program Files, %PROGRAMDATA%, cmd, net stop/start), and provides troubleshooting steps and log locations only for Windows environments. There are no Linux/macOS equivalents or examples, despite the fact that Azure Site Recovery supports replication of both VMware VMs and physical servers, which could include Linux systems. This creates friction for Linux users attempting to troubleshoot replication issues.
Recommendations
  • Add Linux-specific troubleshooting steps, including log file locations (e.g., /var/log/...), service names, and commands (systemctl, journalctl, etc.) where applicable.
  • Clarify which troubleshooting steps apply to Windows-only environments and which are relevant for Linux-based source machines.
  • Provide parallel examples for Linux/macOS systems when referencing file paths, permissions, and service management.
  • Explicitly state OS requirements or limitations for each troubleshooting step if certain features are Windows-only.
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-14 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 provides troubleshooting steps for both Windows and Linux, but there is a clear Windows-first bias. Windows examples, tools, and troubleshooting steps are presented before Linux equivalents in most sections. Many instructions and error resolutions are Windows-centric, referencing Windows tools (e.g., regedit, net user, netsh, Control Panel, Task Manager, Windows Services, registry keys, VSS, DCOM, COM+), and some troubleshooting steps lack Linux-specific guidance or examples. Linux instructions are present but often less detailed or appear after Windows content.
Recommendations
  • Present Windows and Linux troubleshooting steps in parallel, using tabs or side-by-side formatting, to avoid Windows-first ordering.
  • Add Linux-specific examples for troubleshooting network shares, service management, and agent installation (e.g., using systemctl, checking SSH/SFTP status, verifying file permissions, log locations).
  • Include Linux equivalents for commands and tools (e.g., show how to check and modify services, permissions, and logs on Linux).
  • Expand Linux troubleshooting for VSS-like functionality, disk/partition checks, and agent installation failures.
  • Reference Linux documentation and support articles where appropriate, similar to the Windows links provided.
  • Ensure screenshots and UI instructions are available for Linux desktop environments if relevant, or clarify CLI-only steps.
GitHub Create Pull Request
Site Recovery Troubleshoot VMware vCenter discovery failures in Azure Site Recovery ...tps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/vmware-azure-troubleshoot-vcenter-discovery-failures.md
Medium Priority View Details →
Scanned: 2026-01-14 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 for troubleshooting VMware vCenter discovery failures in Azure Site Recovery demonstrates notable Windows bias. All example procedures rely on Windows-specific tools (PsExec, Internet Explorer, Windows services), and there are no Linux or cross-platform alternatives provided for proxy configuration or service management. The instructions assume the administrator is working on a Windows environment, which creates friction for Linux users managing vCenter or Azure Site Recovery components.
Recommendations
  • Provide equivalent instructions for Linux environments, such as using 'sudo -u' or 'su' to access system context, and describe how to configure proxy settings for vCenter discovery on Linux.
  • Replace or supplement PsExec/Internet Explorer steps with cross-platform methods (e.g., using curl, wget, or editing configuration files directly).
  • Document how to restart relevant services on Linux (e.g., using systemctl or service commands).
  • Clarify which steps are Windows-only and offer Linux/macOS alternatives where possible.
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-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation for troubleshooting the Azure Site Recovery process server shows a notable Windows bias. Troubleshooting steps, log file paths, and tool usage (e.g., Task Manager, Resource Monitor, Control Panel, registry edits, .exe utilities, and Windows-style paths) are exclusively described for Windows environments. There are no Linux/macOS equivalents or instructions, even though physical servers and VMware VMs could be running Linux. Windows tools and patterns are mentioned first and exclusively.
Recommendations
  • Add troubleshooting steps and log file locations for Linux-based process servers, if supported.
  • Provide Linux/macOS equivalents for commands (e.g., using netcat or curl instead of telnet, checking services with systemctl, viewing logs in /var/log, etc.).
  • Clarify whether the process server software is Windows-only; if so, state this explicitly at the top of the article.
  • If Linux is supported, include Linux-specific examples and troubleshooting procedures alongside Windows instructions.
  • For generic network troubleshooting, mention cross-platform tools and approaches.
GitHub Create Pull Request
Site Recovery Run VMware VMs failover to Azure ...https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/vmware-azure-tutorial-failover-failback-modernized.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation provides generic instructions for failing over VMware VMs to Azure, referencing both Windows and Linux VMs in some troubleshooting notes. However, connection instructions and validation steps primarily link to Windows-specific guides (e.g., connecting via RDP), with no direct Linux/macOS connection examples or links. The documentation does not mention Linux tools or SSH connection steps explicitly, and Windows-centric links appear before any Linux alternatives.
Recommendations
  • Add explicit instructions or links for connecting to failed-over Linux VMs using SSH, including a reference to the official Azure Linux VM connection documentation.
  • Where connection validation is discussed, provide parity by mentioning both RDP (for Windows) and SSH (for Linux/macOS) methods, with appropriate links.
  • Ensure troubleshooting and validation steps reference both Windows and Linux VMs equally, and avoid defaulting to Windows-first examples.
  • Include examples or screenshots for both Windows and Linux VM failover scenarios where relevant.
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-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation provides a comprehensive support matrix for both Windows and Linux disaster recovery scenarios in Azure Site Recovery. However, there is a mild Windows bias in the deployment and appliance setup sections: PowerShell is mentioned as a deployment method for VMware VMs, and the replication appliance is required to run Windows Server 2022 with Desktop Experience. The appliance setup is described as being performed via PowerShell scripts, with no mention of Linux-based alternatives. Windows Server roles and group policies are discussed in detail, while equivalent Linux security/configuration guidance is absent. The documentation does, however, thoroughly cover supported Linux distributions, kernel versions, and file systems, ensuring Linux users can determine compatibility and requirements.
Recommendations
  • Clarify if the replication appliance must be Windows-only, or if a Linux-based alternative is possible. If Windows is required, explicitly state this is by design.
  • If PowerShell is the only supported automation method for appliance setup, clarify that Linux users must use a Windows host for this step.
  • Provide Linux-specific configuration and security guidance for the replication appliance if a Linux option exists or is planned.
  • Consider listing Linux deployment options (if any) alongside Windows/PowerShell methods, or explicitly state their absence.
  • In sections discussing group policies and server roles, add equivalent Linux security best practices or note that these are Windows-specific.
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-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides a generally cross-platform overview for disaster recovery of VMware and physical servers to Azure, with most instructions applicable to both Windows and Linux. However, there is a notable Windows bias in the failover preparation and automation sections: Windows compliance is discussed in detail, with proactive steps and links, while Linux compliance is described as automatic and less actionable. The only explicit command-line example for triggering failover uses a PowerShell cmdlet, with no Linux CLI or Azure CLI equivalent shown.
Recommendations
  • Provide equivalent Azure CLI or REST API examples for triggering failover, alongside the PowerShell cmdlet.
  • Expand guidance for Linux machines, including proactive compliance checks or preparation steps if available.
  • Clarify any differences in failover preparation steps for Linux vs. Windows, and link to Linux-specific troubleshooting or best practices.
  • When mentioning automation (e.g., Azure Automation runbooks), include examples or references for both Windows and Linux post-failover tasks.
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-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation provides both Windows and Linux guidance for uninstalling the Mobility agent, but update instructions are notably Windows-biased: PowerShell examples are given only for Windows, and manual update instructions do not include Linux-specific commands or examples. The VSS provider section is Windows-only, but this is appropriate as VSS is a Windows technology. Windows tools and UI patterns are described first and in more detail, while Linux update scenarios are less explicit.
Recommendations
  • Provide equivalent Linux command-line examples for updating the Mobility agent, such as shell scripts or package manager instructions.
  • Clarify manual update steps for Linux, including example commands for running the installer and verifying the update.
  • When presenting update methods, alternate or parallelize Windows and Linux instructions to avoid Windows-first ordering.
  • Explicitly state when a feature or step is Windows-only (e.g., VSS provider), to help Linux users understand scope.
GitHub Create Pull Request
Site Recovery Troubleshoot VMware replication appliance health issues in Azure Site Recovery ...recovery/vmware-troubleshoot-appliance-health-issue.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation provides troubleshooting steps for the Azure Site Recovery VMware replication appliance, but the only command-line example given is via PowerShell, referencing Windows file paths and scripts. There is no mention of Linux/macOS equivalents, nor guidance for users running the appliance on non-Windows platforms. The appliance configuration manager and script locations are described in a Windows-centric manner, which may create friction for Linux users.
Recommendations
  • Clarify whether the replication appliance is Windows-only or if Linux deployments are supported.
  • If Linux is supported, provide equivalent troubleshooting steps for Linux environments, including shell commands and Linux file paths.
  • Indicate whether the PowerShell scripts can be run via PowerShell Core on Linux/macOS, or provide Bash alternatives.
  • Add notes or sections specifying platform requirements and limitations.
GitHub Create Pull Request
Site Recovery Enable replication for on-premises machines with private endpoints ...https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/hybrid-how-to-enable-replication-private-endpoints.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page exhibits a moderate Windows bias. Examples for creating private endpoints reference Azure PowerShell and the Azure portal, both of which are more familiar to Windows users. There are no explicit CLI or Linux-native instructions (e.g., Azure CLI, Bash), nor are Linux/macOS-specific tools or workflows mentioned. The URLs and terminology (e.g., *.windows.net, PowerShell links) reinforce a Windows-centric perspective. Linux users may need to adapt instructions or seek out equivalent CLI commands.
Recommendations
  • Add Azure CLI (az) command examples for all major steps, especially for creating private endpoints and DNS zones.
  • Explicitly mention cross-platform tools and workflows (e.g., Bash, Azure CLI) alongside PowerShell and portal instructions.
  • Include notes or links for Linux/macOS users on how to perform equivalent operations.
  • Ensure screenshots and step-by-step instructions are not exclusively tied to Windows environments.
  • List Linux/macOS prerequisites or caveats where relevant.
GitHub Create Pull Request
Site Recovery Exclude disks from replication with Azure Site Recovery ...in/articles/site-recovery/exclude-disks-replication.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a notable Windows bias. All practical examples, walkthroughs, and screenshots are based on Windows VMs, with explicit references to Windows file paths (e.g., C:\, pagefile.sys), Windows disk management tools (diskmgmt.msc), and Windows-specific SQL Server service management (Net start/stop). There are no Linux-based examples, instructions, or screenshots, even though Azure Site Recovery supports Linux VMs. Linux-specific disk exclusion scenarios, file paths, and service management are not addressed.
Recommendations
  • Add parallel Linux VM examples for disk exclusion, including typical Linux disk layouts (e.g., /, /var, /tmp, swap partitions).
  • Demonstrate how to exclude disks containing Linux swap or temp files, with Linux-specific file paths and disk naming conventions.
  • Provide Linux command-line instructions for adding and formatting disks after failover (e.g., using fdisk, mkfs, mount, systemctl for service management).
  • Include screenshots or terminal output relevant to Linux environments.
  • Clarify any differences in failover/failback behavior for Linux VMs, especially regarding manually created disks and service recovery.
  • Reference Linux SQL Server or other common Linux workloads where appropriate.
GitHub Create Pull Request
Site Recovery Monitoring churn patterns on virtual machines ...b/main/articles/site-recovery/monitoring-high-churn.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 presents Windows monitoring tools (Resource Monitor, Performance Monitor) in greater detail, with step-by-step instructions and screenshots, while Linux tools (iotop, iostat) are mentioned briefly without usage examples, output samples, or guidance. Windows tools are described first and more thoroughly, creating a notable imbalance.
Recommendations
  • Provide step-by-step instructions for Linux tools (iotop, iostat), including installation commands and example outputs.
  • Include screenshots or sample terminal output for Linux tools, similar to the Windows section.
  • Mention additional Linux monitoring utilities (e.g., dstat, atop, sar) for parity.
  • Present Windows and Linux sections with equal detail and structure, possibly interleaving examples or using parallel headings.
  • Consider listing both Windows and Linux tools together in a comparative table before diving into OS-specific details.
GitHub Create Pull Request
Site Recovery Common questions about VMware disaster recovery with Azure Site Recovery ...rticles/site-recovery/vmware-azure-common-questions.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 shows a moderate Windows bias. Windows tools and paths are often mentioned first or exclusively (e.g., MySQL installer location, Mobility service installer path). PowerShell is frequently referenced for automation and advanced tasks, with limited mention of Linux equivalents. Some instructions (e.g., manual installation, scripting) focus on Windows tools or provide Windows examples before Linux ones. Linux commands are present in some places, but not consistently, and Linux-specific guidance is less detailed.
Recommendations
  • Provide Linux/macOS equivalents for all Windows-specific instructions, such as file paths, installer locations, and manual setup steps.
  • Include Bash/CLI examples alongside PowerShell for automation and scripting sections.
  • Ensure Linux commands and procedures are presented with equal prominence and detail as Windows ones.
  • Reference cross-platform tools (e.g., Azure CLI) where possible, not just PowerShell.
  • Clarify when instructions are OS-specific and provide links or sections for both Windows and Linux/macOS users.
GitHub Create Pull Request
Site Recovery Set up VMware VM disaster recovery to Azure with Azure Site Recovery - Modernized ...ttps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/vmware-azure-set-up-replication-tutorial-modernized.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation generally maintains OS neutrality, but there is a subtle Windows-first bias: when mentioning credentials for Mobility Service installation, Windows is listed before Linux, and only minimal Linux-specific guidance is provided (e.g., 'provide root credentials'). No explicit Linux command-line examples or troubleshooting steps are given, and there are no references to Linux-specific tools or patterns. The documentation does not provide parity in example depth or troubleshooting for Linux users.
Recommendations
  • Provide explicit Linux command-line examples for manual Mobility Service installation, including common package managers and service management commands.
  • Include troubleshooting steps or links for common Linux-specific issues (e.g., SELinux, firewall configuration, systemd service status).
  • Mention Linux patterns/tools (such as SSH, sudo, systemctl) where relevant, and ensure Linux instructions are as detailed as Windows ones.
  • List Linux instructions before or alongside Windows instructions to avoid Windows-first ordering.
  • Clarify any differences in agent behavior or requirements between Linux and Windows VMs.
GitHub Create Pull Request
Site Recovery Troubleshoot VMware replication appliance health issues in Azure Site Recovery ...recovery/vmware-troubleshoot-appliance-health-issue.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 Tools Missing Linux Example Windows First
Summary
The documentation provides troubleshooting steps that rely exclusively on Windows tools and PowerShell scripts, with all command-line examples using Windows paths and PowerShell syntax. There are no Linux or macOS equivalents, nor any mention of how to perform these tasks on non-Windows platforms. The appliance management instructions assume a Windows environment, creating friction for Linux users.
Recommendations
  • Add equivalent troubleshooting steps for Linux-based appliances, including shell commands and relevant file paths.
  • Clarify whether the replication appliance supports Linux and, if so, provide parity in examples and instructions.
  • If PowerShell scripts are required, offer guidance on running them via PowerShell Core on Linux/macOS, or provide alternative scripts (e.g., Bash) for non-Windows platforms.
  • Explicitly state platform requirements and limitations at the start of the article.
GitHub Create Pull Request
Site Recovery About the Mobility service for disaster recovery of VMware VMs and physical servers with Azure Site Recovery | Microsoft Docs ...-recovery/vmware-physical-mobility-service-overview.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 5 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Minor Windows Pathing Windows-Centric Examples
Summary
The documentation demonstrates a moderate Windows bias. Windows examples, paths, and tools are consistently presented first, and UI-based installation instructions are primarily Windows-centric. While Linux instructions are present and generally complete, they often appear after Windows instructions and sometimes lack the same level of detail or visual aids. Windows-specific tools and paths (e.g., C:\Program Files, command prompt, Windows service names) are referenced as defaults, and some prerequisite and troubleshooting steps are described in a Windows context before mentioning Linux equivalents.
Recommendations
  • Present Linux and Windows instructions in parallel or in clearly separated, equally detailed sections.
  • Provide Linux-first or at least side-by-side examples, especially for command-line installation and configuration.
  • Include Linux-specific screenshots or UI walkthroughs where applicable, not just Windows UI images.
  • When referencing file paths or system services, provide both Windows and Linux equivalents together.
  • Ensure troubleshooting and prerequisite sections explicitly address Linux scenarios with equal prominence.
  • Avoid assuming Windows as the default environment in examples, paths, and explanations.
GitHub Create Pull Request
Site Recovery Replicate Azure Stack Hub to Azure using Azure Site Recovery ...in/articles/site-recovery/azure-stack-site-recovery.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation demonstrates a moderate Windows bias. Windows operating systems are listed first in compatibility tables, and Windows-specific instructions (such as registry edits, firewall configuration via GUI tools, and references to Windows services like VSS) are more detailed and appear before Linux equivalents. Windows tools and patterns (e.g., REG ADD, wf.msc, GPO) are described with step-by-step instructions, while Linux steps are more generic and lack equivalent command-line examples or automation guidance. There are no PowerShell scripts, but the overall pattern prioritizes Windows workflows.
Recommendations
  • Present Linux and Windows instructions in parallel, with equal detail and prominence.
  • Include Linux command-line examples for tasks like firewall configuration, SSH setup, and service management (e.g., using ufw, systemctl).
  • Add automation guidance for Linux environments, such as shell scripts or Ansible playbooks, similar to Windows GPO or registry automation.
  • List supported operating systems in alphabetical order or grouped by platform, rather than Windows first.
  • Reference Linux equivalents for Windows-specific technologies (e.g., mention LVM snapshots or fsfreeze as alternatives to VSS for app-consistent snapshots).
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-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation exclusively uses Azure Portal and Azure PowerShell for examples and guidance, with no mention of Linux/macOS CLI tools (such as Azure CLI) or cross-platform automation. All screenshots and step-by-step instructions are based on the Azure Portal UI, which is platform-agnostic but often more familiar to Windows users. The only command-line reference is to Azure PowerShell, with no equivalent Azure CLI or Bash examples for Linux/macOS users.
Recommendations
  • Add Azure CLI (az) command examples alongside Azure PowerShell for all automation steps, especially for creating private endpoints and DNS zones.
  • Explicitly mention that all steps can be performed from Linux/macOS using Azure CLI or portal.
  • Provide Bash script snippets for common tasks (e.g., role assignment, DNS record creation) to improve parity.
  • Where screenshots are used, clarify that the portal is accessible from any OS/browser.
  • Include links to cross-platform automation guides or reference documentation.
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-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example
Summary
The documentation provides only Azure PowerShell script examples for customizing automation accounts, with no equivalent Bash, CLI, or Linux-native instructions. All scripting guidance is Windows-centric, assuming use of PowerShell and Windows authentication patterns. There is no mention of how to perform these tasks from Linux/macOS environments or using cross-platform tools.
Recommendations
  • Provide equivalent Azure CLI and Bash script examples for managing automation accounts and enabling/disabling automatic updates.
  • Explicitly state whether the PowerShell script can be run on PowerShell Core on Linux/macOS, or if there are platform limitations.
  • Add troubleshooting steps and manual update instructions relevant to Linux/macOS environments.
  • Clarify any prerequisites or differences for users operating from non-Windows systems.
GitHub Create Pull Request
Site Recovery Common questions about Azure virtual machine disaster recovery with Azure Site Recovery ...icles/site-recovery/azure-to-azure-common-questions.md
Medium Priority View Details →
Scanned: 2026-01-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 displays a moderate Windows bias. Windows-specific features and examples (such as PowerShell usage, ADE for Windows, VSS for app-consistent snapshots, and SQL Server extension instructions) are mentioned before or instead of Linux equivalents. PowerShell is referenced as the main automation method, with no Bash/CLI alternatives. Linux support is sometimes mentioned only as an aside, and some features (e.g., shared disks) are explicitly unsupported for Linux. There are few, if any, Linux/macOS-specific instructions or examples.
Recommendations
  • Provide Azure CLI and Bash examples alongside PowerShell for all automation tasks.
  • Explicitly document Linux support and limitations for features like disk encryption, shared disks, and app-consistent snapshots.
  • Mention Linux-specific tools and patterns (e.g., cloud-init, Linux disk encryption) where relevant.
  • Ensure Linux instructions are presented with equal prominence and detail as Windows instructions.
  • Clarify when features are Windows-only and suggest Linux alternatives or workarounds if available.
GitHub Create Pull Request
Site Recovery Enable replication for encrypted Azure VMs in Azure Site Recovery ...ry/azure-to-azure-how-to-enable-replication-ade-vms.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation demonstrates a notable Windows bias. The only provided script for copying disk encryption keys is a PowerShell script, with explicit instructions to use Windows PowerShell. There are no Linux/macOS shell (Bash, CLI) equivalents or examples, and the script is referenced repeatedly as the required method for both initial replication and updating encryption settings. The documentation does not mention cross-platform alternatives or clarify how Linux users should perform these steps, despite Azure CLI and REST API support. Windows terminology and tools are presented first and exclusively in critical steps.
Recommendations
  • Provide Bash/Azure CLI examples for copying disk encryption keys, or clarify how Linux/macOS users can perform the same tasks.
  • Explicitly state platform requirements for scripts and offer cross-platform alternatives or containerized solutions.
  • When referencing scripts, indicate whether they can be run on Linux/macOS (e.g., via PowerShell Core) and provide installation guidance if needed.
  • Add parity in troubleshooting and update sections by including Linux/macOS workflows.
  • Where possible, use REST API or Azure CLI as the primary example, or present them alongside PowerShell.
GitHub Create Pull Request
Site Recovery Enable replication of encrypted Azure VMs in Azure Site Recovery ...https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/azure-to-azure-how-to-enable-replication-cmk-disks.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example
Summary
The documentation provides a PowerShell-only example for adding a new CMK-enabled disk to a replicated item, with no equivalent CLI, Bash, or Linux-native instructions. The rest of the guide is GUI-based and platform-neutral, but the only code sample assumes a Windows/PowerShell environment.
Recommendations
  • Provide equivalent Azure CLI (az) commands for all PowerShell examples, as Azure CLI is cross-platform and works natively on Linux/macOS.
  • Explicitly mention that the PowerShell example is for Windows users, and link to Azure CLI documentation for Linux/macOS users.
  • Where possible, include Bash shell scripts or step-by-step instructions for Linux/macOS environments.
  • Clarify any platform dependencies or prerequisites for scripting tasks.
GitHub Create Pull Request
Site Recovery Support Matrix for Azure VM Disaster Recovery with Azure Site Recovery ...rticles/site-recovery/azure-to-azure-support-matrix.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation exhibits a moderate Windows bias. In sections describing deployment methods and cache storage, Azure PowerShell (a Windows-centric tool) is emphasized, with no mention of Linux equivalents or parity for Azure CLI (which is cross-platform). Windows operating systems are consistently listed before Linux, and additional details and troubleshooting steps are provided for Windows versions. There is a lack of Linux command-line examples or explicit guidance for Linux/macOS users in areas where PowerShell is referenced.
Recommendations
  • Add explicit Azure CLI support or guidance where only Azure PowerShell is mentioned, or clarify CLI limitations and provide workarounds for Linux/macOS users.
  • When listing supported operating systems, alternate the order or present Windows and Linux in parallel to avoid 'Windows first' perception.
  • Where PowerShell is referenced for configuration (e.g., setting up cache storage from the target subscription), provide equivalent Azure CLI commands or note if not possible.
  • Include Linux/macOS-specific notes or examples where relevant, especially in sections that currently only mention Windows tools or update processes.
  • Clarify any limitations for Linux users up front, and provide links to Linux/macOS documentation where available.
GitHub Create Pull Request
Site Recovery Troubleshoot Azure VM replication in Azure Site Recovery - other issues ...es/site-recovery/azure-to-azure-troubleshoot-errors.md
Medium Priority View Details →
Scanned: 2026-01-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 generally provides guidance for both Windows and Linux, but several sections display Windows bias. In the 'Trusted root certificates' section, Windows instructions are presented first and are more detailed, referencing Windows-specific update processes and tools. Linux instructions are present but less detailed and rely on distributor guidance, with some explicit steps only for SUSE/RedHat. In the 'COM+ or VSS' section, only Windows services and tools are mentioned, with no Linux equivalent or clarification that the issue is Windows-only. Proxy troubleshooting mentions autodetection via Internet Explorer (Windows) before Linux's /etc/environment, and the file paths for configuration are listed for both OSes, but Windows is mentioned first. Some sections lack Linux-specific troubleshooting or examples, especially for service-related errors.
Recommendations
  • Present Windows and Linux instructions in parallel, or clearly label OS-specific sections.
  • Provide Linux troubleshooting steps or clarify when an issue is Windows-only (e.g., COM+/VSS).
  • Include Linux-first or at least balanced examples and tool references.
  • Expand Linux guidance beyond distributor references, offering concrete steps for common distributions.
  • Avoid referencing Windows tools (e.g., Internet Explorer) without Linux equivalents or alternatives.
  • Ensure parity in detail and clarity between Windows and Linux instructions.
GitHub Create Pull Request
Site Recovery Troubleshoot replication of Azure VMs with Azure Site Recovery ...te-recovery/azure-to-azure-troubleshoot-replication.md
Medium Priority View Details →
Scanned: 2026-01-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 page demonstrates a moderate Windows bias. Troubleshooting steps frequently reference Windows-specific tools, file paths, and commands (e.g., PowerShell, VSS, Windows service names, and Windows file locations) before or instead of Linux equivalents. Linux solutions are mentioned but often lack detailed, step-by-step guidance or parity in examples. Windows terminology and instructions are generally presented first, and some troubleshooting sections (especially VSS-related) are almost entirely Windows-centric.
Recommendations
  • Provide equivalent Linux command-line examples (e.g., Bash, CLI) alongside PowerShell commands.
  • Include Linux-specific troubleshooting steps for common issues, especially for disk exclusion and service management.
  • Offer detailed guidance for Linux file paths, service names, and log locations wherever Windows paths are mentioned.
  • Ensure parity in error code explanations and solutions for both Windows and Linux environments.
  • Where Windows tools (like VSS) are referenced, clarify Linux alternatives or note if the issue is Windows-only.
GitHub Create Pull Request
← Previous Page 26 of 35 Next →