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 576-600 of 864 flagged pages
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: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation exhibits a Windows bias in several areas: Windows and PowerShell are mentioned as deployment and management options, while equivalent Linux CLI or automation options are not provided. The replication appliance is required to run Windows Server, with no mention of Linux-based alternatives. PowerShell is referenced for VMware deployment, but there are no Linux shell or cross-platform CLI examples. Several configuration and management instructions reference Windows-specific tools, roles, and group policies, with no Linux equivalents or guidance. While Linux support matrices are comprehensive, Linux is often treated as a secondary consideration in deployment and management workflows.
Recommendations
  • Provide Linux-based deployment and management options where possible (e.g., Bash scripts, Azure CLI, Ansible).
  • Include Linux shell/CLI examples alongside or before PowerShell examples.
  • Document any limitations or roadmap for supporting the replication appliance on Linux.
  • Where Windows-specific tools or group policies are referenced, add equivalent Linux guidance or explicitly state if not applicable.
  • Ensure parity in automation and scripting guidance for both Windows and Linux administrators.
  • Clarify in each scenario whether Linux is fully supported, partially supported, or unsupported, and provide links to Linux-specific setup guides.
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: 2025-07-12 23:44
Reviewed by: Unknown
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 file paths, tools, and troubleshooting steps are frequently mentioned first or exclusively, such as referencing C:\ProgramData, using Windows-specific tools like PsExec and Internet Explorer, and providing more detailed instructions for Windows scenarios. Some sections lack Linux equivalents or provide less detail for Linux, and Windows command-line tools and patterns are prioritized over Linux alternatives.
Recommendations
  • Ensure that Linux examples are provided wherever Windows examples are given, with equal detail and clarity.
  • When referencing file paths or logs, include both Windows and Linux locations side by side.
  • List Linux commands and troubleshooting steps before or alongside Windows ones, not always after.
  • Replace or supplement Windows-only tools (e.g., PsExec, Internet Explorer) with Linux equivalents (e.g., sudo, appropriate browsers, or command-line proxy configuration).
  • For sections like 'vCenter discovery failures' and 'Remove the stale entries for protected items', provide explicit Linux instructions or clarify if the steps are Windows-only.
  • Where possible, use cross-platform language and avoid assuming the user is on Windows (e.g., avoid 'Open an elevated command prompt' without mentioning the Linux equivalent).
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: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation demonstrates a Windows bias by providing explicit instructions and tooling references for Windows environments (such as PowerShell cmdlets and compliance checks for Windows machines) while omitting equivalent Linux examples or guidance. Windows-specific preparation steps are described in detail, whereas Linux is only briefly mentioned, often as an afterthought. There are no Linux command-line examples or references to Linux-native tools for managing or monitoring disaster recovery processes.
Recommendations
  • Provide equivalent Linux command-line examples (e.g., using Azure CLI or shell scripts) alongside PowerShell cmdlets for tasks such as triggering failover.
  • Include detailed steps for preparing Linux machines for failover, similar to the compliance checks described for Windows.
  • Reference Linux-native tools or scripts for monitoring and managing replication and failover, not just Windows-based tools.
  • Ensure that Linux instructions are presented with equal prominence and detail as Windows instructions, rather than as secondary notes.
  • Where possible, use cross-platform tools (e.g., Azure CLI) in examples, or clearly indicate both Windows and Linux options.
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: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation exhibits a strong Windows bias: Windows-specific troubleshooting steps, tools, and examples are provided in detail and appear first, while Linux guidance is often minimal, generic, or relegated to secondary notes. Many sections (e.g., VSS, WMI, File and Printer Sharing, registry edits, service management) focus exclusively on Windows tools and concepts, with Linux equivalents either missing or only briefly mentioned. Visual aids and command examples are almost entirely Windows-centric.
Recommendations
  • Provide Linux-first or parallel Linux troubleshooting steps and examples alongside Windows instructions in each relevant section.
  • Include Linux command-line equivalents for all Windows command examples (e.g., service management, file sharing, network troubleshooting).
  • Add Linux-specific screenshots or terminal output where Windows GUI screenshots are used.
  • Document Linux equivalents for Windows tools and services (e.g., alternatives to WMI, VSS, File and Printer Sharing).
  • Ensure that Linux error codes and logs are referenced and troubleshooting steps are as detailed as for Windows.
  • Where registry edits are described for Windows, provide corresponding Linux configuration file changes if applicable.
  • Balance the order of presentation so that Linux and Windows are treated equally, or alternate which platform is described first.
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: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a Windows bias by providing PowerShell-based update instructions only for Windows, listing Windows uninstall and VSS provider installation steps in greater detail and before Linux equivalents, and referencing Windows-specific tools (Control Panel, MsiExec.exe, VSS provider scripts) without offering comparable Linux automation or parity. Linux instructions are present but less detailed and lack automation/scripted examples.
Recommendations
  • Provide equivalent Linux command-line or script-based examples for updating the Mobility agent, similar to the PowerShell example for Windows.
  • Ensure Linux uninstall instructions include both manual and automated/scripted methods, and offer parity in detail with Windows steps.
  • If there are Linux equivalents to the VSS provider or other Windows-specific tools, document their installation and management steps explicitly.
  • When listing procedures, present Windows and Linux instructions side-by-side or in parallel sections to avoid the impression of Windows-first priority.
  • Reference Linux tools and patterns (e.g., systemctl, rpm, deb, shell scripts) where appropriate, and avoid assuming familiarity only with Windows environments.
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: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation page demonstrates a strong Windows bias. All troubleshooting steps, file paths, service names, and tool usage (e.g., Task Manager, Resource Monitor, Control Panel, registry editing, Telnet client installation) are presented exclusively with Windows terminology and tools. There are no Linux-specific instructions, examples, or equivalent commands provided, despite the process server potentially running on Linux or interacting with Linux-based source machines. This could hinder Linux administrators or mixed-environment users from effectively following the guidance.
Recommendations
  • Provide equivalent Linux commands and procedures alongside Windows instructions (e.g., using systemctl for services, journalctl for logs, netcat or curl for connectivity checks, and Linux file paths).
  • Mention and demonstrate how to check process/server health, logs, and connectivity on Linux systems.
  • Include Linux-specific troubleshooting steps for common issues (e.g., checking firewall rules with iptables/nftables, using top/htop for resource monitoring).
  • Clarify in the introduction whether the process server is supported or expected to run only on Windows, or if Linux is also supported, and tailor the documentation accordingly.
  • Where Windows GUI tools are referenced (e.g., Task Manager, Resource Monitor), provide CLI alternatives suitable for Linux environments.
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: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 5 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Windows Path Examples Windows-Centric Instructions
Summary
The documentation exhibits a Windows-first bias in several areas: Windows examples, paths, and tools are consistently presented before Linux equivalents; Windows-specific tools and conventions (such as command prompt, C:\ paths, and UI screenshots) are emphasized; and instructions often default to Windows-centric language and directory structures, even when discussing Linux prerequisites. While Linux instructions are present, they are frequently secondary, less detailed, or require extra manual steps (such as downloading and placing installers).
Recommendations
  • Present Linux and Windows instructions in parallel, giving equal prominence to both platforms in each section.
  • When providing example commands or paths, show both Windows and Linux versions side by side.
  • Avoid using Windows-specific directory structures (e.g., C:\Program Files...) as the default; instead, clarify the equivalent Linux paths.
  • Include Linux UI screenshots where applicable, or clarify when a UI is Windows-only.
  • When referencing tools or services (e.g., Volume Shadow Copy Service), explain Linux equivalents or note if not applicable.
  • Ensure that manual steps for Linux (such as downloading and placing installers) are as streamlined as possible and clearly documented.
  • Use neutral language (e.g., 'on your server' instead of 'on your Windows machine') unless the instruction is truly platform-specific.
  • Add troubleshooting and antivirus exclusion guidance for Linux with the same detail as for Windows.
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-17 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation is generally cross-platform and covers both VMware VMs and physical servers, which can be Windows or Linux. However, there are subtle signs of Windows bias: the only explicit scripting example for triggering failover uses a PowerShell cmdlet, and compliance checks and preparation steps are described in more detail for Windows than Linux. Linux compliance is mentioned only briefly, and no Linux-native scripting or command-line examples are provided.
Recommendations
  • Provide equivalent Linux command-line examples (e.g., using Azure CLI or REST API) for tasks like triggering failover, not just PowerShell.
  • Expand on Linux compliance preparation steps, or link to detailed guidance for Linux machines, similar to the Windows-focused troubleshooting and preparation links.
  • When referencing automation (e.g., runbooks), clarify that both PowerShell and Bash/CLI scripts are supported and provide examples for both where possible.
  • Ensure that monitoring and setup instructions reference tools and workflows familiar to Linux administrators, not just those common in Windows environments.
GitHub Create Pull Request
Site Recovery Set up Azure Site Recovery for Azure VMware Solution VMs ...ain/articles/site-recovery/avs-tutorial-replication.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 for setting up Azure Site Recovery for Azure VMware Solution VMs shows a moderate Windows bias. The configuration server VM is based on Windows Server, and the registration and setup instructions are Windows-centric (e.g., Windows Server 2016 installation, administrator password, Windows activation). While Linux VMs are supported for replication, the core management and configuration workflow is Windows-focused, with no Linux/macOS alternatives for the configuration server setup or management tools. Linux is mentioned only as a target for replication, not as a platform for running the configuration server or management tools.
Recommendations
  • Clarify early in the documentation that the configuration server must run Windows Server and that Linux/macOS alternatives are not supported for this component.
  • Provide explicit guidance for Linux VM replication, including prerequisites and steps for Linux VMs (e.g., required accounts, agent installation specifics).
  • If possible, mention any future plans or alternatives for Linux-based configuration server deployments, or explicitly state that only Windows Server is supported.
  • Add a summary table of supported OSes for each component to help users quickly understand platform requirements.
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-14 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 account settings, with no equivalent Bash, CLI, or Linux/macOS shell instructions. This may create friction for users who prefer or require non-Windows environments, as PowerShell is not universally available or familiar on Linux/macOS systems.
Recommendations
  • Provide equivalent Azure CLI or REST API examples for managing automatic updates, suitable for Bash or other common Linux/macOS shells.
  • Explicitly note whether the PowerShell script can be run in Azure Cloud Shell (which supports PowerShell on Linux) or provide steps for using Cloud Shell.
  • Add guidance or links for installing and using PowerShell Core on Linux/macOS if PowerShell is required.
  • Clarify whether all management tasks can be performed via the Azure Portal or CLI, and provide those steps if possible.
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-14 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 exhibits several Windows biases: PowerShell is frequently referenced as the primary or sole automation method, and Windows-centric tools and patterns (such as VSS for app-consistent snapshots) are described in detail, while Linux equivalents are mentioned briefly or omitted. Some features (e.g., shared disks) are explicitly unsupported for Linux, and examples or instructions for Linux users are limited or missing in sections where parity is possible.
Recommendations
  • Provide CLI and Bash examples alongside PowerShell for automation tasks, such as selecting automation accounts or excluding disks from replication.
  • Explicitly document Linux support and limitations for all major features, and offer Linux-specific guidance where possible.
  • When describing app-consistent snapshots, detail the Linux custom script approach with example scripts or links to relevant documentation.
  • Ensure that Linux VM scenarios are covered in sections about failover, recovery plans, and disk/network configuration, including any differences or required steps.
  • Where features are Windows-only, clearly state this to avoid confusion.
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-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example Windows First
Summary
The documentation page demonstrates a notable Windows bias, primarily by providing only Windows PowerShell scripts and instructions for key management operations, without offering equivalent Linux/macOS CLI examples. The steps for copying disk encryption keys and updating target VM encryption settings rely exclusively on PowerShell, and the instructions explicitly mention opening the Windows PowerShell application. There is no mention of Bash, Azure CLI, or cross-platform alternatives, and Windows tooling is presented first and exclusively for critical steps.
Recommendations
  • Provide equivalent examples using Azure CLI (az) commands for key copying and management, which work on Linux/macOS/Windows.
  • Include instructions for running scripts on Linux/macOS, such as using PowerShell Core (pwsh) or Bash alternatives.
  • Clarify which steps are platform-agnostic (e.g., portal, REST API) and which require Windows-specific tools.
  • If the PowerShell script is required, note that PowerShell Core is available cross-platform and provide installation guidance.
  • Add explicit Linux/macOS workflow examples for key vault operations and VM replication steps.
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-14 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 provides several troubleshooting steps and examples that are Windows-centric, such as PowerShell usage, Windows file paths, and service names. Windows tools and patterns (e.g., VSS, specific service restarts, command scripts) are described in detail, while Linux equivalents are mentioned less frequently or only in passing. In some cases, Linux instructions are present but lack parity in detail or example commands.
Recommendations
  • Provide Linux-specific command-line examples (e.g., Bash commands) alongside PowerShell examples, especially for tasks like excluding disks or updating configuration files.
  • Include Linux file paths and service names consistently wherever Windows equivalents are listed.
  • Expand troubleshooting steps for Linux VMs, including how to check logs, restart relevant services, and handle app-consistency issues.
  • Where Windows tools (like VSS) are referenced, clarify the Linux alternatives or note if the step is Windows-only.
  • Ensure screenshots and UI instructions are applicable to both Windows and Linux VMs, or clearly indicate when they are not.
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-14 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 code example for adding a new CMK-enabled disk to a replicated item, with no equivalent Azure CLI, Bash, or Linux/macOS instructions. The rest of the guide is portal-driven and platform-agnostic, but the only automation example is Windows-centric.
Recommendations
  • Add equivalent Azure CLI or REST API examples for disk replication tasks, ensuring Linux/macOS users can automate the process without PowerShell.
  • Explicitly mention that the PowerShell example is one option, and link to cross-platform alternatives if available.
  • Clarify any prerequisites or limitations for Linux/macOS users in the FAQ section.
GitHub Create Pull Request
Site Recovery Troubleshoot Azure VM replication in Azure Site Recovery - VM errors ...site-recovery/azure-to-azure-virtual-machine-errors.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example
Summary
The documentation provides parity for disk initialization steps by linking both Windows and Linux guides. However, for cleanup of stale Site Recovery configurations, only a PowerShell script is provided, with no mention of a Linux/bash alternative or guidance for non-Windows users. This creates friction for Linux/macOS administrators who may not have access to PowerShell or a Windows environment.
Recommendations
  • Provide a bash/CLI version of the cleanup script, or document how Linux/macOS users can perform the same cleanup using Azure CLI or REST API.
  • Explicitly state whether the PowerShell script can be run cross-platform (e.g., with PowerShell Core on Linux/macOS), and provide installation instructions if so.
  • Where scripts are referenced, clarify platform requirements and offer alternatives for non-Windows users.
GitHub Create Pull Request
Site Recovery About using ExpressRoute with Azure Site Recovery ...e-recovery/concepts-expressroute-with-site-recovery.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 Tools Missing Linux Example
Summary
The documentation includes a section on configuring proxy bypass for replication traffic that exclusively references Windows tools (PsExec, Internet Explorer) and provides only Windows-specific instructions. There are no equivalent instructions or examples for Linux-based Configuration Server or Process Server environments, nor is there mention of how to configure proxy bypass on Linux systems.
Recommendations
  • Add instructions for configuring proxy bypass on Linux-based Configuration Server and Process Server, including relevant commands and file locations (e.g., environment variables, /etc/environment, or proxy configuration files).
  • Provide Linux command-line examples for proxy configuration, such as using curl, wget, or system-wide proxy settings.
  • Clarify whether the Configuration Server and Process Server are supported on Linux, and if so, ensure parity in documentation for both platforms.
  • If the tools or steps are Windows-only due to product limitations, explicitly state this to inform Linux users.
GitHub Create Pull Request
Site Recovery Connect to Azure VMs on-premises failover with Azure Site Recovery ...e-recovery/concepts-on-premises-to-azure-networking.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation provides detailed, step-by-step instructions for preparing Windows machines for failover, including PowerShell-based configuration, Windows Firewall, and RDP setup. In contrast, Linux preparation is covered in only two brief bullet points, lacking equivalent detail or examples (e.g., SSH configuration, firewall setup commands). Windows instructions are presented first and are much more comprehensive, while Linux guidance is minimal.
Recommendations
  • Expand the Linux preparation section to include step-by-step instructions comparable to the Windows section, such as commands for enabling SSH, configuring firewall rules (e.g., using ufw, firewalld, or iptables), and checking for pending updates.
  • Provide example commands for Linux (e.g., systemctl enable ssh, ufw allow ssh) and reference relevant Azure documentation for Linux VM preparation.
  • Include troubleshooting tips for Linux connectivity (e.g., SELinux/AppArmor considerations, SSH key management).
  • Present Windows and Linux instructions in parallel sections or tables for parity.
  • Ensure that examples for configuring Azure VM network security group rules include both RDP (Windows) and SSH (Linux) ports explicitly.
GitHub Create Pull Request
Site Recovery Remove an Azure Site Recovery replication appliance ...s/blob/main/articles/site-recovery/delete-appliance.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 removing an Azure Site Recovery replication appliance shows a mild Windows bias. It references Windows-specific tools (e.g., Services.msc, World Wide Web Publishing Service) and browser instructions tailored to Microsoft Edge. There are no explicit Linux/macOS instructions or examples for equivalent steps, such as restarting services or clearing browser caches. The appliance itself is described as a VM, but the steps assume a Windows environment, potentially creating friction for users running the appliance on Linux or other platforms.
Recommendations
  • Clarify whether the Azure Site Recovery replication appliance can run on Linux or macOS. If so, provide equivalent instructions for service management (e.g., systemctl for Linux) and browser cache clearing for Chrome/Firefox on Linux/macOS.
  • When referencing tools like Services.msc or specific Windows services, note the Linux/macOS equivalents or state if the step is Windows-only.
  • Include cross-platform examples or a note about platform limitations if the appliance is strictly Windows-based.
  • List browser cache clearing instructions for multiple browsers and operating systems, not just Microsoft Edge on Windows.
GitHub Create Pull Request
Site Recovery Delete an Azure Site Recovery vault ...-docs/blob/main/articles/site-recovery/delete-vault.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 Missing Linux Example
Summary
The documentation provides only Azure PowerShell examples for force-deleting the vault, without mentioning or demonstrating equivalent steps using Azure CLI or Bash. PowerShell is typically associated with Windows environments, and the lack of Azure CLI/Bash examples creates friction for Linux/macOS users. Additionally, PowerShell commands and references are presented as the default/primary method for scripting, with no parity for cross-platform tools.
Recommendations
  • Add equivalent Azure CLI examples for deleting a Recovery Services vault, including force deletion if supported.
  • Clearly indicate whether the PowerShell commands can be run on Linux/macOS (via PowerShell Core), or provide guidance for non-Windows users.
  • Wherever PowerShell is used, offer Azure CLI/Bash alternatives in parallel to ensure cross-platform accessibility.
  • Update 'Next steps' to include links to Azure CLI documentation for Recovery Services vault management, if available.
GitHub Create Pull Request
Site Recovery Trusted launch VMs with Azure Site Recovery ...lob/main/articles/site-recovery/concepts-trusted-vm.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 covers both Windows and Linux support for trusted launch VMs with Azure Site Recovery, but certain features and flows are Windows-only or Windows-first. For example, shared disks and the 'Create a new VM flow' with Site Recovery are currently supported only for Windows OS. Linux support is mentioned but sometimes as a limitation or after Windows. There are no explicit Linux-specific configuration or migration examples, and some steps (like uninstalling the mobility service) do not provide Linux command examples.
Recommendations
  • Provide Linux-specific examples and commands, especially for steps like uninstalling the mobility service.
  • Clarify any differences in process for Linux VMs, including any required manual steps or alternative tooling.
  • Where features are Windows-only, clearly indicate roadmap or alternatives for Linux users.
  • Ensure parity in example coverage (e.g., show both Windows and Linux flows where applicable).
GitHub Create Pull Request
Site Recovery Configure Mobility Service Proxy Settings for Azure to Azure Disaster Recovery | Microsoft Docs ...-recovery/configure-mobility-service-proxy-settings.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation provides both Windows and Linux guidance for configuring proxy settings for the Mobility Service in Azure Site Recovery. However, Windows-specific tools and patterns (such as Internet Explorer settings and psexec usage) are described in detail and appear before Linux equivalents. Windows paths and instructions are often mentioned first, and the use of Windows-centric tools (Internet Explorer, psexec) may not be familiar or applicable to Linux users. Linux instructions are present but less detailed, and there are no Linux command examples or troubleshooting tips.
Recommendations
  • Provide Linux command-line examples for setting environment variables (e.g., export https_proxy) and editing /etc/profile or /etc/environment.
  • Include troubleshooting steps or verification commands for Linux (e.g., how to check if ProxyInfo.conf is being used).
  • Balance the order of instructions so Linux and Windows are presented equally, or group OS-specific instructions under clear subheadings.
  • Avoid referencing Windows-only tools (like Internet Explorer and psexec) without Linux equivalents or alternatives.
GitHub Create Pull Request
Site Recovery Deploy Azure Site Recovery Replication Appliance - Modernized ...tps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/deploy-vmware-azure-replication-appliance-modernized.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 Tools Windows First
Summary
The documentation provides two methods to deploy the Azure Site Recovery replication appliance: via OVF template (recommended) and via PowerShell. The PowerShell method is described as an alternative for organizational restrictions, but all scripting and registry references are Windows-centric. Registry and group policy checks are exclusively for Windows, and PowerShell is the only CLI example provided. There is no mention of Linux/macOS equivalents for scripting, configuration, or troubleshooting, and Windows-specific tools and patterns (registry, group policy, PowerShell execution policy) are referenced without Linux alternatives.
Recommendations
  • Clarify whether the appliance VM is strictly Windows-based, and if so, explicitly state that Linux/macOS deployment is not supported.
  • If Linux-based deployment is possible, provide equivalent instructions for Linux (e.g., Bash scripts, Linux system configuration, SELinux/AppArmor policies, etc.).
  • If PowerShell is required, note any cross-platform support (PowerShell Core) or provide alternatives for Linux users.
  • For registry and group policy checks, explain their relevance or provide Linux equivalents if applicable.
  • Add troubleshooting steps for Linux/macOS environments if the appliance can be deployed there.
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-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation provides detailed, step-by-step examples and screenshots exclusively for Windows VMs, focusing on Windows-specific files (pagefile.sys, SQL Server tempdb) and Windows disk management tools. While Linux VMs are mentioned in a single table row regarding failback behavior, there are no Linux-specific examples, instructions, or screenshots. All walkthroughs, screenshots, and disk management references are Windows-centric, with no parity for Linux VM scenarios.
Recommendations
  • Add Linux VM examples for excluding disks from replication, including typical Linux disk layouts and files (e.g., swap partitions, /tmp, database temp files).
  • Provide step-by-step instructions for handling excluded disks during failover and failback for Linux VMs, including how to re-create or re-attach disks and update mount points.
  • Include screenshots or command-line examples relevant to Linux (e.g., using lsblk, parted, or cloud-init for disk management).
  • Clarify any differences in Azure Site Recovery behavior for Linux VMs, especially regarding drive letter assignment, mount points, and failback.
  • Ensure that tables and examples consistently include both Windows and Linux scenarios where supported.
GitHub Create Pull Request
Site Recovery New feature updates in Azure Site Recovery ...in/articles/site-recovery/feature-updates-whats-new.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page covers new features in Azure Site Recovery, a cross-platform disaster recovery service. While most updates are presented in a platform-neutral way, there is a notable Windows bias in several sections: Windows Server Failover Clusters (WSFC) and Windows OS features are described before their Linux equivalents, and PowerShell support is explicitly mentioned for Windows scenarios. Linux support is mentioned for Trusted Launch VMs, but the Windows version is described as generally available, while Linux is only in preview. There are no Linux-specific examples, tools, or parity notes for features like Shared Disk or WSFC, and PowerShell is referenced without mention of Linux alternatives.
Recommendations
  • When describing new features, explicitly mention Linux support status and provide equivalent Linux examples or tooling where possible.
  • If PowerShell is referenced, also mention or provide examples for Bash/CLI or other Linux-native tools if supported.
  • For features that are Windows-only (e.g., WSFC), clarify their platform specificity to avoid confusion.
  • Ensure Linux features (such as Trusted Launch VM support) are given equal prominence and detail as Windows features.
  • Add notes or links to Linux documentation where relevant, especially for cross-platform features.
GitHub Create Pull Request
Site Recovery Replicate Azure virtual machines running in a proximity placement group ...tps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/how-to-enable-replication-proximity-placement-groups.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 Missing Linux Example
Summary
The documentation provides extensive PowerShell-based instructions and examples for replicating Azure VMs in proximity placement groups, with all CLI automation shown exclusively using Azure PowerShell. There are no Bash, Azure CLI, or Linux-native scripting examples. The prerequisites and guidance for scripting focus on installing and using the Azure PowerShell module, which is most commonly used on Windows. While the portal-based steps are cross-platform, the automation and scripting sections lack Linux parity. Additionally, PowerShell examples are presented before any mention of alternatives, and no Linux-specific tools or patterns are discussed.
Recommendations
  • Add equivalent Azure CLI (az) examples for all automation steps, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Include Bash script snippets for common tasks, such as resource group and disk management.
  • Explicitly note that Azure PowerShell can be installed and used on Linux/macOS, and provide installation instructions for those platforms.
  • Where possible, mention Linux/macOS considerations (e.g., authentication, environment setup) for scripting and automation.
  • Ensure screenshots and UI instructions do not assume Windows-only environments.
GitHub Create Pull Request
← Previous Page 24 of 35 Next →