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 501-525 of 864 flagged pages
Site Recovery
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/azure-to-azure-troubleshoot-replication.md
...te-recovery/azure-to-azure-troubleshoot-replication.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by prioritizing Windows tools, file paths, and troubleshooting steps. Powershell and Windows-specific commands are referenced without equivalent Linux examples. Troubleshooting logs and service restart instructions are detailed for Windows, but Linux instructions are minimal or absent. Windows tools and patterns (such as VSS, Windows service names, and file paths) are mentioned first or exclusively, with Linux alternatives only briefly noted or omitted.
Recommendations
- Provide equivalent Linux command-line examples (e.g., bash commands) wherever Powershell or Windows commands are shown.
- Include Linux file paths and log locations alongside Windows paths in troubleshooting sections.
- List Linux services and their restart commands (e.g., systemctl) alongside Windows service instructions.
- When referencing tools like VSS (which are Windows-specific), clarify the Linux equivalent or note the absence and provide Linux-specific troubleshooting steps.
- Ensure that Linux examples and instructions are given equal prominence and detail as Windows examples.
- Where a step is not applicable to Linux, explicitly state this and provide alternative guidance for Linux users.
Create Pull Request
Site Recovery
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/concepts-trusted-vm.md
...lob/main/articles/site-recovery/concepts-trusted-vm.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a Windows-first bias by highlighting Windows support and features before Linux, omitting Linux-specific examples or guidance in several key areas, and referencing Windows-only tools and flows. Linux support is mentioned but often as an afterthought or with limitations, and there are no Linux-specific instructions or parity in feature support explanations.
Recommendations
- Provide Linux-specific examples and instructions wherever Windows workflows are described (e.g., for uninstalling the mobility service, include Linux command-line steps).
- Ensure that feature support statements (such as 'Create a new VM flow' and 'Shared disks') clarify Linux support status and, if unsupported, provide timelines or alternatives.
- Avoid listing Windows features or support before Linux unless there is a technical reason; consider parallel presentation (Windows and Linux together) for parity.
- Where PowerShell or Windows tools are mentioned, also reference equivalent Linux tools or CLI commands.
- Add troubleshooting and migration guidance specific to Linux VMs, not just generic or Windows-centric steps.
Site Recovery
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/concepts-expressroute-with-site-recovery.md
...e-recovery/concepts-expressroute-with-site-recovery.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by providing only Windows-specific tooling and instructions (e.g., PsExec, Internet Explorer) for configuring proxy bypass on the Configuration Server and Process Servers. There are no equivalent instructions or examples for Linux-based environments, nor is there mention of Linux tools or browsers. This may hinder users operating in Linux or mixed-OS environments.
Recommendations
- Provide equivalent instructions for Linux-based Configuration Server and Process Server setups, including how to configure proxy bypass using Linux tools (e.g., editing environment variables, using curl/wget, or updating system proxy settings).
- Mention cross-platform or browser-agnostic methods for configuring proxy settings, rather than referencing Internet Explorer exclusively.
- Where Windows-specific tools (like PsExec) are referenced, offer Linux alternatives (e.g., sudo, su, or systemd-run) and clarify which instructions apply to which OS.
- Explicitly state OS prerequisites or limitations if certain features or steps are only supported on Windows.
- Include example commands and configuration steps for both Windows and Linux environments to ensure parity and inclusivity.
Site Recovery
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/deploy-vmware-azure-replication-appliance-modernized.md
...tps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/deploy-vmware-azure-replication-appliance-modernized.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation demonstrates a Windows bias by providing only PowerShell-based manual setup instructions for the replication appliance, referencing Windows registry and group policy settings, and omitting any Linux-based setup or troubleshooting examples. The use of Windows-specific tools and patterns is prevalent, and there is no mention of Linux alternatives or parity in the appliance deployment or configuration process.
Recommendations
- Provide equivalent Linux-based setup instructions for the replication appliance, including supported distributions and required commands/scripts.
- Include Linux shell (bash) examples for manual installation and configuration, alongside PowerShell.
- Document Linux-specific prerequisites and troubleshooting steps (e.g., systemd services, firewall settings, SELinux/AppArmor considerations).
- Clarify whether the OVF template can be deployed on Linux-based hypervisors or if the appliance itself supports Linux OS.
- Explicitly state OS support and limitations for the replication appliance, and provide guidance for mixed-OS environments.
- Where Windows registry or group policy settings are referenced, provide analogous Linux configuration steps if applicable, or clarify if these steps are not relevant for Linux deployments.
Site Recovery
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/concepts-on-premises-to-azure-networking.md
...e-recovery/concepts-on-premises-to-azure-networking.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a Windows bias by providing detailed, step-by-step instructions and references for preparing Windows machines, including PowerShell usage and Windows Firewall configuration, while Linux instructions are minimal and lack equivalent detail. Windows tools and patterns (such as RDP, Windows Firewall, and Windows Update) are mentioned explicitly, and Windows preparation steps are listed before Linux, with more comprehensive guidance and links. There are no Linux-specific examples or references to common Linux tools (e.g., iptables, SSH configuration details), nor parity in troubleshooting or automation guidance.
Recommendations
- Provide equally detailed preparation steps for Linux machines, including references to configuring SSH, managing Linux firewalls (e.g., iptables, firewalld, ufw), and checking required services.
- Include Linux command-line examples (e.g., systemctl commands to enable/start sshd, firewall-cmd or ufw commands to open SSH ports).
- Add troubleshooting guidance for Linux connectivity issues (e.g., checking SSH logs, SELinux/AppArmor considerations).
- Mention Linux automation options (e.g., using shell scripts or cloud-init) alongside PowerShell/Azure Automation.
- Ensure that for every Windows-specific tool or step, a Linux equivalent is described and referenced.
- Present Windows and Linux instructions in parallel sections or tables to emphasize equal support.
Site Recovery
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/configure-mobility-service-proxy-settings.md
...-recovery/configure-mobility-service-proxy-settings.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation demonstrates a Windows-first bias by presenting Windows-specific instructions and tools (such as Internet Explorer and psexec) before Linux equivalents. The auto-detection section details Windows steps and tools in greater depth, while Linux instructions are more generic. Windows file paths and configuration steps are described in detail, whereas Linux steps are less explicit.
Recommendations
- Provide Linux configuration steps with equal detail, including explicit commands for editing /etc/profile or /etc/environment.
- Mention Linux tools (such as nano, vi, or export commands) for setting environment variables, similar to how psexec and Internet Explorer are referenced for Windows.
- Present Windows and Linux instructions in parallel sections or tables to ensure parity and clarity.
- Avoid referencing deprecated or Windows-only tools (like Internet Explorer) without Linux equivalents or alternatives.
- Include example commands for both platforms to set and verify proxy settings.
Site Recovery
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/azure-to-azure-troubleshoot-errors.md
...es/site-recovery/azure-to-azure-troubleshoot-errors.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation generally presents Windows solutions and tools before Linux equivalents, and in some cases, provides more detailed or tool-specific guidance for Windows (such as referencing PowerShell scripts and the Windows Services console). Some troubleshooting steps and downloadable scripts are only described for Windows/PowerShell, with no mention of Linux alternatives. Linux guidance is present and sometimes detailed, but Windows is often prioritized in ordering and tooling.
Recommendations
- Ensure that for every Windows-specific tool or script (e.g., PowerShell scripts for stale configuration cleanup), an equivalent Linux-compatible solution or script is provided, or explicitly state if not available.
- When listing troubleshooting steps or solutions, present both Windows and Linux instructions in parallel, or alternate the order to avoid always listing Windows first.
- For sections referencing Windows-specific tools (e.g., Services console, Internet Explorer proxy detection), provide Linux equivalents (e.g., systemctl/service commands, Linux proxy configuration files) and example commands.
- Where downloadable scripts are provided for Windows, consider providing Bash or Python scripts for Linux, or at least guidance on how to perform the same operation manually.
- Review all sections for parity in detail and clarity between Windows and Linux instructions, ensuring Linux users are not left with vague or generic advice compared to Windows users.
Site Recovery
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/hyper-v-prepare-on-premises-tutorial.md
.../site-recovery/hyper-v-prepare-on-premises-tutorial.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation is heavily focused on Windows environments, specifically Hyper-V and System Center Virtual Machine Manager, which are Windows-only technologies. All examples and instructions for post-failover VM access reference Windows tools and patterns (e.g., RDP, Windows Firewall), with no mention of Linux VMs, SSH, or Linux firewall configuration. There are no Linux-specific instructions or parity in the guidance.
Recommendations
- Add explicit guidance for preparing and accessing Linux VMs after failover, including enabling SSH, configuring Linux firewalls (e.g., ufw, firewalld, iptables), and verifying SSH connectivity.
- Include troubleshooting steps for Linux VMs post-failover, similar to the Windows RDP troubleshooting provided.
- Reference both Windows and Linux VM requirements and supported scenarios in the prerequisites section.
- When discussing network and firewall configuration, provide parallel instructions for both Windows and Linux environments.
- Clarify that the guidance applies to both Windows and Linux VMs where appropriate, or explicitly state if the process is Windows-only.
Site Recovery
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/hyper-v-vmm-azure-tutorial.md
...n/articles/site-recovery/hyper-v-vmm-azure-tutorial.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation is heavily oriented toward Windows environments, specifically focusing on Hyper-V with System Center VMM, and provides only Windows-based instructions and tooling. All examples, installation steps, and command-line snippets are for Windows (including Windows Core), with no mention of Linux equivalents or cross-platform considerations. Windows tools and patterns (e.g., PowerShell, Windows directories, Windows installers) are used exclusively.
Recommendations
- Clearly state in the prerequisites or introduction that the tutorial is specific to Windows/Hyper-V environments, and provide links to equivalent Linux/KVM or VMware documentation if available.
- If Azure Site Recovery supports Linux-based hypervisors (such as KVM or VMware on Linux), add parallel sections or links for those scenarios.
- Where possible, provide cross-platform guidance or note that certain steps are Windows-specific.
- Include a comparison table or matrix showing supported platforms and relevant documentation for each, to help users quickly find Linux-related guidance.
- If Linux-based management or agent installation is possible, provide corresponding shell commands and instructions.
Site Recovery
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/delete-appliance.md
...s/blob/main/articles/site-recovery/delete-appliance.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page demonstrates Windows bias by referencing Windows-specific tools (e.g., 'Services.msc', 'World Wide Web Publishing Service', Microsoft Edge) and omitting equivalent instructions for Linux-based appliances. There are no Linux-specific examples or guidance for users managing the replication appliance on Linux systems. The instructions and troubleshooting steps assume a Windows environment, which may not be applicable to all users.
Recommendations
- Provide equivalent instructions for Linux-based appliances, such as how to restart relevant services (e.g., using systemctl) and clear browser cache on popular Linux browsers.
- When referencing tools like 'Services.msc' or 'World Wide Web Publishing Service', include Linux alternatives or note if these steps are only applicable to Windows-based appliances.
- Avoid assuming the use of Microsoft Edge; mention other browsers and provide platform-agnostic cache clearing steps.
- Explicitly state if the Azure Site Recovery replication appliance is only supported on Windows, or clarify support for Linux to guide users appropriately.
- Structure instructions so that both Windows and Linux users can easily find relevant steps, possibly with separate sections or callouts.
Site Recovery
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/feature-updates-whats-new.md
...in/articles/site-recovery/feature-updates-whats-new.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation demonstrates a Windows-first bias, particularly in the coverage of features such as Shared Disk support, which is described exclusively for Windows Server Failover Clusters (WSFC) with no mention of Linux-based clustering solutions. OS support lists only Windows Server versions, and PowerShell support is highlighted without mention of equivalent Linux automation tools. Linux support is mentioned later and only in the context of a specific preview feature, rather than as a primary scenario. There are no Linux command-line or tool examples, and Windows-centric technologies (e.g., Hyper-V, WSFC) are described in detail, while Linux equivalents are absent.
Recommendations
- Include equivalent Linux examples and scenarios wherever Windows features are described, such as support for Linux clustering solutions (e.g., Pacemaker/Corosync) when discussing shared disks.
- List Linux OS support alongside Windows in feature tables and descriptions, or explicitly state if a feature is Windows-only.
- Provide Linux command-line examples (e.g., Bash, Azure CLI) in addition to or instead of PowerShell where automation is discussed.
- Mention Linux-native tools and patterns (such as systemd, shell scripts, or Linux DR tools) where relevant.
- Ensure that Linux support is given equal prominence in update summaries and not relegated to secondary or preview status unless truly not available.
Site Recovery
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/failover-failback-overview-modernized.md
...site-recovery/failover-failback-overview-modernized.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows-first bias in several areas. In the 'Connect to Azure after failover' section, Windows VM instructions are presented before Linux, with more detailed steps and references to Windows-specific tools (e.g., Windows Firewall, Windows Update, SAN policy). Linux instructions are comparatively brief and lack equivalent troubleshooting or configuration details. There are also references to Windows-specific concepts (e.g., RDP, Windows Update) without Linux parallels. In troubleshooting and notes, Windows Server versions are specifically mentioned, while Linux equivalents are not discussed.
Recommendations
- Provide Linux instructions with parity to Windows, including detailed steps for configuring SSH, firewall (e.g., iptables, firewalld, ufw), and handling pending updates or common issues after failover.
- When listing connection steps, alternate the order or present both Windows and Linux instructions together for each scenario.
- Include Linux-specific troubleshooting tips, such as checking SSH service status, SELinux/AppArmor considerations, and logs for failed connections.
- Reference Linux equivalents for all Windows tools mentioned (e.g., mention Linux firewall configuration alongside Windows Firewall).
- Add notes about potential issues with specific Linux distributions or kernel versions, similar to the notes about Windows Server 2012.
- Where Windows-specific policies (like SAN policy) are discussed, mention whether similar considerations apply to Linux, or state explicitly if not applicable.
Site Recovery
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/hybrid-how-to-enable-replication-private-endpoints.md
...https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/hybrid-how-to-enable-replication-private-endpoints.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by referencing Windows-centric domains and tools (e.g., *.windows.net, PowerShell), providing only Azure Portal and PowerShell-based instructions (with no CLI or Linux-native alternatives), and listing Windows-related URLs and patterns before any Linux or cross-platform equivalents. There are no explicit Linux command-line examples or guidance for Linux administrators, and the documentation assumes a Windows-oriented environment throughout.
Recommendations
- Include Azure CLI examples alongside or before PowerShell instructions for creating and managing private endpoints, as Azure CLI is cross-platform and widely used on Linux.
- Explicitly mention and provide steps for Linux-based environments, such as how to perform required tasks from a Linux workstation or server.
- List cross-platform tools (e.g., Azure CLI, REST API) before or alongside Windows-specific tools (e.g., PowerShell).
- Add Linux-specific caveats or troubleshooting steps where relevant (e.g., DNS configuration, firewall rules, MySQL installation).
- Ensure that URLs and domain patterns are described in a platform-neutral way, and avoid using Windows-centric terminology unless necessary.
- Provide example scripts or commands for both Windows and Linux environments, especially for common administrative tasks.
Site Recovery
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/hyper-v-azure-failover-failback-tutorial.md
...e-recovery/hyper-v-azure-failover-failback-tutorial.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation is heavily oriented toward Windows environments, specifically Hyper-V, and references Windows-centric tools and patterns. There are no Linux-specific examples or guidance, and links to further documentation (such as connecting to VMs) default to Windows instructions. The workflow assumes a Windows-based on-premises environment and does not mention or provide parity for Linux-based Hyper-V hosts or Linux guest VMs.
Recommendations
- Include explicit guidance and examples for Linux guest VMs, such as SSH connection instructions and Linux-specific post-failover validation steps.
- When referencing connection methods, provide both RDP (for Windows) and SSH (for Linux) links and examples, and ensure the documentation does not default to Windows-only resources.
- Clarify whether the process supports Linux-based Hyper-V hosts or Linux guest VMs, and if so, provide any additional steps or considerations for those scenarios.
- Where possible, avoid linking exclusively to Windows documentation (e.g., /azure/virtual-machines/windows/connect-logon) and instead link to cross-platform or Linux-specific resources as well.
- Add troubleshooting steps and tips relevant to Linux VMs, such as common SSH connectivity issues after failover.
Site Recovery
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/exclude-disks-replication.md
...in/articles/site-recovery/exclude-disks-replication.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a clear Windows bias. All detailed examples focus exclusively on Windows VMs, specifically referencing Windows file paths (C:\, D:\, etc.), Windows-specific files (pagefile.sys), and Windows-based applications (Microsoft SQL Server). Instructions for disk management reference Windows tools (diskmgmt.msc, service console, command prompt), with no mention of Linux equivalents. There are no examples or walkthroughs for excluding disks on Linux VMs, nor are there any Linux-specific considerations or commands provided.
Recommendations
- Add equivalent examples for Linux VMs, such as excluding swap partitions or temp directories (e.g., /swap, /tmp, /var/tmp) from replication.
- Include Linux-specific disk management instructions, such as using lsblk, parted, or fdisk for disk operations, and systemctl for service management.
- Provide SQL Server on Linux scenarios, including how to handle tempdb or other database files on Linux-based SQL Server VMs.
- Reference Linux file system paths and conventions (e.g., /mnt/data, /var/lib/mysql) in examples and tables.
- Where Windows tools are mentioned (e.g., diskmgmt.msc, command prompt), provide the Linux equivalent commands or utilities.
- Ensure that tables and limitations sections explicitly address both Windows and Linux VMs, highlighting any differences in behavior or support.
Site Recovery
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/hyper-v-azure-common-questions.md
...ticles/site-recovery/hyper-v-azure-common-questions.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation is heavily focused on Windows environments, specifically Hyper-V on Windows Server, and consistently references Windows tools and concepts (e.g., VMM, PowerShell, Windows Server OS requirements). There are no Linux-specific examples, tools, or alternative workflows provided, and automation examples are only given for PowerShell. The documentation assumes the reader is operating in a Windows-centric environment and does not address Linux hosts or management tools.
Recommendations
- Include explicit statements about Linux support or lack thereof for Hyper-V to Azure Site Recovery scenarios.
- If Linux-based Hyper-V management or guest OS scenarios are possible, provide equivalent Linux command-line (e.g., Bash, Azure CLI) examples alongside PowerShell.
- Mention and document any Linux-compatible tools or APIs for automation (e.g., Azure CLI, REST API) and provide sample usage.
- Clarify in prerequisites and requirements whether only Windows Server Hyper-V hosts are supported, and if so, suggest alternative disaster recovery solutions for Linux-based virtualization environments.
- Ensure that any references to tools (e.g., VMM, Recovery Services agent) clarify their platform compatibility and, where possible, provide Linux alternatives or workarounds.
Site Recovery
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/hyper-v-azure-troubleshoot.md
...n/articles/site-recovery/hyper-v-azure-troubleshoot.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation is heavily oriented towards Windows environments, with all troubleshooting steps, logs, and examples referencing Windows tools, services, and interfaces (e.g., Event Viewer, PowerShell, Hyper-V Manager, Windows event logs, VSS, Integration Services). There is only a single brief mention of Linux, with no concrete troubleshooting steps or examples for Linux-based VMs. All command-line examples use Windows commands or PowerShell, and all UI navigation is for Windows tools. Linux equivalents, if any, are absent.
Recommendations
- Provide parallel troubleshooting steps and examples for Linux-based VMs where applicable, especially for app-consistent snapshots and replication health.
- Include Linux command-line examples (e.g., using systemctl, journalctl, or relevant Linux tools) for checking service status, logs, and integration services.
- Document log file locations and diagnostic steps for Linux guests, including how to check for issues with Azure Site Recovery agents on Linux.
- Where PowerShell or Windows-specific tools are referenced, add equivalent Bash or Linux-native commands.
- Clarify which troubleshooting steps are Windows-only and which are applicable to Linux, and structure sections so Linux guidance is not an afterthought.
- If certain features or troubleshooting steps are not supported on Linux, explicitly state this and provide links to Linux-specific documentation or limitations.
Site Recovery
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/file-server-disaster-recovery.md
...rticles/site-recovery/file-server-disaster-recovery.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation demonstrates a strong Windows bias by focusing almost exclusively on Windows-based tools and patterns (e.g., DFSR, Active Directory, Azure File Sync with Windows Server), and by omitting practical guidance or examples for Linux file servers. All step-by-step instructions, architectural diagrams, and tool references are Windows-centric, with no equivalent Linux workflows or commands provided. While Azure Files is mentioned as being accessible from Linux, the actual disaster recovery procedures, sync setup, and failover instructions are only detailed for Windows environments.
Recommendations
- Add equivalent disaster recovery workflows and examples for Linux-based file servers, including how to replicate, failover, and recover Linux file shares using Azure Site Recovery or other Azure-native tools.
- Include Linux-specific instructions for mounting Azure Files (e.g., using SMB or NFS from Linux clients), and provide sample scripts or commands (such as mount.cifs or mount.nfs usage).
- Reference and document open-source or cross-platform alternatives to DFSR and Active Directory for environments that do not use Windows Server.
- Clearly indicate in each section whether the guidance applies to Windows, Linux, or both, and ensure Linux parity in all step-by-step guides and architectural diagrams.
- Provide troubleshooting notes and port requirements relevant to Linux clients (e.g., SELinux, firewall-cmd, systemd mount units) when accessing Azure Files or participating in failover scenarios.
Site Recovery
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/hyper-v-azure-failback.md
.../main/articles/site-recovery/hyper-v-azure-failback.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation is heavily focused on Windows environments, specifically Hyper-V and System Center VMM, with all instructions and prerequisites referencing Windows-only tools and workflows. There are no examples or guidance for Linux-based hypervisors or environments, and the only operating system mentioned for on-premises hosts is Windows. This creates a strong Windows bias and excludes Linux administrators from the documented failback process.
Recommendations
- Include explicit statements clarifying whether Linux-based hypervisors (such as KVM or Xen) are supported or not for Azure Site Recovery failback scenarios.
- If Linux-based hypervisors are supported, provide equivalent instructions and examples for Linux environments, including any required tools, commands, or configuration steps.
- If only Windows/Hyper-V is supported, add a clear note at the beginning of the documentation to set expectations for Linux users.
- Where possible, mention cross-platform alternatives or tools, and avoid assuming the reader is using Windows exclusively.
- Consider providing a comparison table or section outlining support and steps for both Windows and Linux on-premises environments, if applicable.
Site Recovery
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/hyper-v-azure-tutorial.md
.../main/articles/site-recovery/hyper-v-azure-tutorial.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation is heavily focused on Windows environments, specifically Hyper-V on Windows Server. All setup instructions, tool references, and command-line examples are tailored to Windows, with no mention of Linux-based Hyper-V management, alternatives, or parity. Only Windows tools (e.g., .exe installers, CMD commands, Windows file paths) are referenced, and there are no Linux equivalents or guidance for cross-platform scenarios.
Recommendations
- Explicitly state that the tutorial is intended for Windows-based Hyper-V environments, and clarify platform limitations up front.
- If Linux-based Hyper-V management is supported, provide parallel instructions and examples for Linux hosts (e.g., using Wine, or native Linux tools if available).
- Include notes or links for users seeking disaster recovery for Linux-based hypervisors (such as KVM or Xen) or for managing Hyper-V from non-Windows platforms.
- Where possible, use platform-agnostic language and highlight any cross-platform tools or APIs.
- If only Windows is supported, add a clear note to avoid confusion for Linux users.
Site Recovery
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/hyper-v-azure-architecture.md
...n/articles/site-recovery/hyper-v-azure-architecture.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation is heavily focused on Windows environments, specifically Hyper-V and related Microsoft tooling (e.g., System Center VMM, Hyper-V Replica, Windows APIs). There are no examples or mentions of Linux-based hypervisors, Linux tools, or cross-platform considerations. All technical details, processes, and troubleshooting are described exclusively in the context of Windows/Hyper-V, with references to Windows APIs and Microsoft documentation. This creates a strong Windows bias and excludes Linux administrators or mixed-environment scenarios.
Recommendations
- Clearly state in the introduction that the guide is specific to Hyper-V (a Windows-only hypervisor), and provide links or references to equivalent documentation for Linux-based disaster recovery scenarios (e.g., Azure Site Recovery for VMware or Linux KVM).
- Where possible, mention if any components (such as the Recovery Services agent) have Linux support, or clarify that they are Windows-only.
- If Azure Site Recovery supports Linux VMs running on Hyper-V, include explicit notes or examples about any Linux-specific considerations (e.g., guest agent installation, file system consistency, supported distributions).
- Provide a comparison table or section outlining disaster recovery options for both Windows and Linux environments, with links to relevant documentation for each.
- Avoid assuming the reader is only using Windows tools; acknowledge mixed environments and direct users to appropriate resources.
Site Recovery
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/hyper-v-azure-support-matrix.md
...articles/site-recovery/hyper-v-azure-support-matrix.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation is heavily focused on Windows environments, specifically Hyper-V on Windows Server and System Center Virtual Machine Manager. All examples, requirements, and supported scenarios are Windows-centric, with no mention of Linux-based Hyper-V hosts or cross-platform management tools. PowerShell is referenced as the only scripting/automation interface, and Windows Server versions are listed exclusively. Linux is only mentioned as a guest OS, not as a management or host platform.
Recommendations
- Explicitly state that Hyper-V is only available on Windows, or clarify if Linux-based Hyper-V management is unsupported.
- If any cross-platform management tools (e.g., Azure CLI, REST API) are supported for deployment or management, provide examples alongside or before PowerShell.
- Where PowerShell is referenced, add equivalent Azure CLI or REST API instructions if available.
- Clarify support or lack thereof for Linux-based management hosts in the requirements section.
- In network and storage configuration sections, provide parity in documentation for Linux guest OS features and limitations.
- Add a section summarizing Linux admin considerations, if any, for environments with mixed OS workloads.
Site Recovery
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/hyper-v-deployment-planner-analyze-report.md
...-recovery/hyper-v-deployment-planner-analyze-report.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation is heavily focused on Hyper-V environments, which are exclusive to Windows. All terminology, examples, and operational details assume a Windows/Hyper-V context. There is no mention of Linux-based hypervisors (such as KVM or VMware on Linux), nor are there any examples or guidance for analyzing reports generated from non-Windows environments. All tooling, storage paths, and operational patterns (e.g., VHD/VHDX, E:\ paths, Hyper-V Replica Broker) are Windows-centric, and there is no parity or reference to Linux equivalents.
Recommendations
- If Azure Site Recovery Deployment Planner supports Linux-based hypervisors (e.g., KVM, VMware on Linux), add equivalent documentation sections for those environments, including examples, terminology, and screenshots.
- If the tool is Windows/Hyper-V only, explicitly state this limitation at the top of the documentation to set expectations for Linux users.
- Where possible, provide cross-references or links to documentation for Linux-based disaster recovery scenarios in Azure Site Recovery.
- If future support for Linux-based environments is planned, include a roadmap or note for users.
- Ensure that any scripts, file paths, or operational steps are either cross-platform or clearly marked as Windows-specific, and provide Linux equivalents where applicable.
Site Recovery
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/hyper-v-exclude-disk.md
...ob/main/articles/site-recovery/hyper-v-exclude-disk.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation is focused exclusively on Hyper-V, a Windows-based virtualization platform, and does not mention or provide guidance for Linux-based hypervisors (such as KVM or Xen) or cross-platform scenarios. All instructions, terminology, and examples assume a Windows/Hyper-V environment, with no Linux equivalents or alternatives referenced.
Recommendations
- Include a section or note clarifying whether similar disk exclusion functionality is available for Linux-based hypervisors (e.g., KVM, Xen) when using Azure Site Recovery.
- If supported, provide parallel instructions or links for excluding disks from replication for Linux VMs or non-Hyper-V environments.
- Reference any Azure Site Recovery features or documentation relevant to Linux workloads to ensure parity and help Linux administrators.
- Consider adding a comparison table or FAQ addressing differences and feature parity between Hyper-V (Windows) and Linux-based disaster recovery scenarios.
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 →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a strong Windows bias, particularly in its reliance on PowerShell for scripting and automation examples. All command-line instructions are provided exclusively via Azure PowerShell, with no mention of Azure CLI or Bash alternatives that are more common in Linux environments. The structure and navigation of the page also prioritize Windows-centric tools and workflows, and there is a lack of Linux-specific guidance or parity in automation examples. The only Linux mention is a caution about CentOS EOL, not a usage example.
Recommendations
- Provide equivalent Azure CLI (az) command examples alongside PowerShell for all automation and scripting steps, especially for Linux users.
- Include Bash shell script examples where appropriate, or at least reference how to perform the same actions in a Linux environment.
- Balance the order of presentation so that Linux and cross-platform tools (like Azure CLI) are mentioned before or alongside Windows/PowerShell tools.
- Add explicit guidance or links for Linux administrators, such as how to install and use Azure CLI, and how to automate Site Recovery tasks from Linux.
- Clarify in the prerequisites and throughout the document that all actions can be performed from Linux/macOS as well as Windows, and specify any differences.
- Consider adding a dedicated section or callout for Linux users, summarizing the cross-platform options and any caveats.