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 801-825 of 864 flagged pages
Site Recovery
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/azure-to-azure-tutorial-enable-replication.md
...recovery/azure-to-azure-tutorial-enable-replication.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation mentions both Windows and Linux VMs in the prerequisites, but when providing instructions for verifying VM certificates, it lists Windows guidance first and in more detail, while Linux guidance is generic and less actionable. No command-line or configuration examples are provided for Linux, and there are no Linux-specific screenshots or step-by-step instructions, whereas Windows is referenced explicitly and with more actionable steps.
Recommendations
- Provide explicit, actionable steps for Linux VMs, such as example commands to update root certificates for common distributions (e.g., Ubuntu, RHEL, CentOS).
- Include Linux-specific screenshots or terminal commands where appropriate, especially for certificate management and connectivity verification.
- When listing instructions for both Windows and Linux, alternate the order or present them in parallel to avoid Windows-first bias.
- Reference Linux documentation or official guides for certificate and network configuration, not just generic advice.
- If there are any differences in the Site Recovery Mobility agent installation or troubleshooting for Linux, document them explicitly.
Create Pull Request
Site Recovery
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/encryption-feature-deprecation.md
...ticles/site-recovery/encryption-feature-deprecation.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation exclusively discusses Azure Site Recovery in the context of Hyper-V virtual machines, which are a Windows-centric technology. There are no references to Linux-based VMs, their encryption options, or equivalent remediation steps for non-Windows environments. All examples and guidance assume a Windows/Hyper-V scenario, omitting Linux use cases entirely.
Recommendations
- Include information about how the deprecation affects Linux-based VMs, if applicable.
- Provide equivalent remediation steps or links for users protecting Linux VMs with Azure Site Recovery.
- Clarify whether the described steps are only relevant for Hyper-V (Windows) or if similar actions are needed for VMware or Linux-based scenarios.
- Add examples or references for managing encryption at rest for Linux VMs in Azure Site Recovery.
Site Recovery
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/how-to-migrate-run-as-accounts-managed-identity.md
...ery/how-to-migrate-run-as-accounts-managed-identity.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Summary
The documentation page focuses exclusively on Azure portal and graphical workflows, with no mention of Linux-specific tools, shell commands, or cross-platform CLI examples. There are no PowerShell-specific instructions, but the absence of Linux/Unix command-line examples or references to non-Windows environments suggests a bias toward Windows-centric workflows. The documentation assumes users interact via the Azure portal or Azure CLI, but does not provide explicit Linux shell or automation guidance.
Recommendations
- Add explicit Linux/Unix shell (bash) examples for relevant steps, especially for automation via Azure CLI.
- Include references to cross-platform tools and clarify that the Azure CLI commands can be run on Linux, macOS, and Windows.
- Provide sample scripts for both PowerShell and bash where automation is discussed.
- Mention any platform-specific considerations for Linux users (e.g., authentication, environment setup).
- Ensure that screenshots and instructions are not solely tailored to Windows environments or UI conventions.
Site Recovery
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/hyper-v-vmm-network-mapping.md
.../articles/site-recovery/hyper-v-vmm-network-mapping.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation is focused exclusively on Hyper-V and System Center Virtual Machine Manager (VMM), which are Windows-centric technologies. There are no references to Linux-based hypervisors, tools, or environments, nor are there any examples or guidance for non-Windows platforms. All terminology, examples, and workflows assume a Windows ecosystem.
Recommendations
- Include references or parallel guidance for Linux-based virtualization platforms (e.g., KVM, Xen) if supported by Azure Site Recovery.
- Provide examples or notes for network mapping in scenarios involving Linux VMs or non-Windows hypervisors.
- Clarify in the introduction that the guidance is specific to Hyper-V/VMM and suggest alternative documentation for Linux environments if available.
- If Azure Site Recovery supports Linux VMs or other hypervisors, add sections or links to relevant documentation to ensure Linux parity.
Site Recovery
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/hyper-v-deployment-planner-cost-estimation.md
...recovery/hyper-v-deployment-planner-cost-estimation.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation is heavily oriented toward Windows environments, specifically Hyper-V VMs, and consistently presents Windows concepts and features first. While Linux is mentioned as an OS type, there are no Linux-specific examples, scenarios, or considerations provided. The documentation assumes a Windows-centric deployment and does not address Linux-specific tools, patterns, or potential differences in cost estimation or DR processes.
Recommendations
- Include explicit Linux VM examples in cost estimation tables and walkthroughs, demonstrating any differences in cost calculation or configuration.
- Provide guidance or notes on Linux-specific considerations for DR planning, such as licensing, support for different Linux distributions, and any Azure Hybrid Use Benefit applicability.
- Clarify if there are any differences in the DR process, tooling, or supported features for Linux VMs compared to Windows VMs.
- Add references or links to documentation focused on Linux VM disaster recovery scenarios to ensure parity and inclusivity.
- If the Deployment Planner tool supports Linux VMs, explicitly state this and provide sample configurations or screenshots for Linux workloads.
Site Recovery
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/move-azure-VMs-AVset-Azone.md
...n/articles/site-recovery/move-azure-VMs-AVset-Azone.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation demonstrates a Windows-first bias in the 'Prepare the source virtual machines' section, where instructions for Windows VMs (converting unmanaged to managed disks and updating root certificates) are provided in detail with direct links, while Linux VM guidance is generic and lacks specific instructions or links. There are no Linux-specific examples or step-by-step instructions, and the only explicit example links are for Windows.
Recommendations
- Provide equivalent step-by-step instructions and direct links for Linux VMs, such as how to convert unmanaged to managed disks on Linux and how to update trusted root certificates on common distributions.
- Include Linux-specific examples or references alongside Windows examples, ensuring parity in detail and clarity.
- Where Windows update processes are mentioned, add parallel guidance for popular Linux distributions (e.g., Ubuntu, RHEL, CentOS) for updating root certificates and system updates.
- Review all sections for implicit prioritization of Windows and ensure Linux is equally represented in prerequisites, troubleshooting, and best practices.
Site Recovery
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/physical-server-enable-replication.md
...es/site-recovery/physical-server-enable-replication.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation mentions both Linux and Windows operating systems, but provides more detailed credential guidance for Windows (admin privileges) and Linux (root), without offering any concrete, OS-specific examples or command-line instructions. There are no Linux-specific examples, scripts, or troubleshooting steps, and no mention of Linux tools or shell commands. The documentation implicitly assumes a GUI/portal-driven workflow, which is more familiar to Windows administrators, and does not provide parity for Linux users who may prefer CLI or shell-based instructions.
Recommendations
- Include explicit Linux command-line examples for installing the Mobility Service, such as sample shell commands for manual installation.
- Provide parity in credential guidance, e.g., show how to create or use a service account on Linux with minimum required privileges, not just 'root'.
- Add troubleshooting steps or references for common Linux-specific issues (e.g., SELinux, firewall, systemd service management).
- Where GUI steps are described, offer equivalent CLI or script-based alternatives for both Windows (PowerShell) and Linux (Bash).
- List Linux and Windows instructions side-by-side where relevant, rather than only mentioning both in passing.
Site Recovery
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/quickstart-create-vault-bicep.md
...rticles/site-recovery/quickstart-create-vault-bicep.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for all operations, but consistently lists PowerShell as an equal alternative rather than a secondary option. However, there is a subtle Windows bias in the ordering and presentation: PowerShell is always presented alongside CLI, and never as a footnote or afterthought. There are no explicit Linux-specific instructions, nor is there mention of Bash or Linux shell environments, which may leave Linux users with questions about prerequisites or environment setup. The use of Azure CLI does provide cross-platform parity, but the documentation does not explicitly acknowledge or support Linux users beyond this.
Recommendations
- Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and that PowerShell examples are primarily for Windows or PowerShell Core users.
- Add a note or section about running Azure CLI in Bash or other Linux shells, including any environment setup steps if needed.
- If possible, provide Bash script examples or clarify that the CLI commands are intended for use in Bash or other Unix-like shells as well.
- Consider listing Azure CLI (cross-platform) examples first, and PowerShell (Windows-centric) examples second, to emphasize Linux parity.
- Include a brief statement in the prerequisites about supported operating systems and shells for each tool.
Site Recovery
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/physical-to-azure-failover-failback.md
...s/site-recovery/physical-to-azure-failover-failback.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows-first bias by referencing Windows concepts (such as 'Windows or Linux' in passing) but providing no Linux-specific examples, commands, or considerations. There are no Linux command-line examples, and all references to operating systems, tools, and procedures are either generic or assume familiarity with Windows-centric environments (e.g., vCenter, VMware, Windows Server 2008 R2 SP1). Linux is only mentioned as an afterthought, with no concrete guidance for Linux administrators.
Recommendations
- Include explicit Linux examples and considerations throughout the documentation, such as steps or screenshots for Linux-based physical servers.
- Provide parity in troubleshooting and requirements for both Windows and Linux operating systems, including supported distributions and any OS-specific prerequisites.
- Add Linux command-line examples (e.g., shell scripts) where automation or scripting is discussed, not just generic references to 'scripts'.
- Highlight any differences in failover/failback process for Linux servers, such as handling of network configuration, disk mounting, or post-failover validation.
- Ensure that references to OS-specific limitations (e.g., unsupported Windows Server 2008 R2 SP1) are matched with Linux equivalents, if any, or explicitly state that there are none.
Site Recovery
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/tutorial-shared-disk.md
...ob/main/articles/site-recovery/tutorial-shared-disk.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation exclusively references Windows Server Failover Clusters (WSFC) and does not mention or provide guidance for Linux-based clustering solutions (such as Pacemaker or Corosync). All instructions, terminology, and prerequisites are tailored to Windows environments, with no Linux equivalents or examples provided.
Recommendations
- Explicitly state whether Linux-based clusters (e.g., Pacemaker/Corosync) are supported or not. If not supported, clarify this limitation early in the documentation.
- If Linux shared disk clustering is supported, add equivalent sections and examples for configuring, replicating, and failing over Linux clusters using Azure Site Recovery.
- Include Linux-specific prerequisites, such as supported distributions, required packages, and configuration steps.
- Provide screenshots and step-by-step instructions for Linux cluster scenarios, ensuring parity with the Windows-focused content.
- Reference Linux documentation and best practices for shared disk clustering in Azure.
Site Recovery
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/site-recovery-extension-troubleshoot.md
.../site-recovery/site-recovery-extension-troubleshoot.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation consistently presents Windows troubleshooting steps before Linux ones, and provides more detailed, step-by-step instructions for Windows (including use of Windows-specific tools like services.msc and Control Panel). Linux instructions are less detailed and rely on external links for key steps. This ordering and level of detail may make Linux users feel like second-class citizens and could hinder their troubleshooting experience.
Recommendations
- Alternate the order of Windows and Linux troubleshooting steps, or present them in parallel sections to avoid always prioritizing Windows.
- Provide equally detailed, step-by-step instructions for Linux troubleshooting, including explicit commands for checking agent status, restarting services, and uninstalling/reinstalling the agent.
- Mention Linux tools and commands (e.g., systemctl, service, package managers) with the same prominence as Windows tools (services.msc, Control Panel).
- Where Windows-specific tools are referenced, provide the Linux equivalent immediately after or alongside.
- Ensure that all error messages and troubleshooting flows have Linux parity, not just links to external resources.
Site Recovery
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/vmware-azure-set-up-process-server-azure.md
...e-recovery/vmware-azure-set-up-process-server-azure.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows Tools
Summary
The documentation page assumes the process server VM will be set up using a Windows-based workflow, referencing 'User name' and 'Password' for admin permissions, but does not specify or provide examples for Linux-based deployments. There are no Linux-specific instructions, tools, or command-line examples, and the process server setup steps implicitly follow Windows conventions.
Recommendations
- Explicitly state whether the process server can be deployed as a Linux VM, and if so, provide equivalent instructions for Linux-based deployments.
- Include Linux command-line examples (e.g., SSH, Linux user creation) alongside or before Windows examples.
- Clarify any OS requirements or supported operating systems for the process server VM.
- If only Windows is supported, clearly state this limitation; if Linux is supported, ensure parity in documentation and tooling references.
Site Recovery
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/site-recovery-vmware-deployment-planner-analyze-report.md
...site-recovery-vmware-deployment-planner-analyze-report.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page primarily describes the analysis of the Deployment Planner report for VMware disaster recovery to Azure, focusing on report interpretation rather than command-line usage. However, there is a subtle Windows bias: Windows-specific scenarios (such as EFI support) are described in detail before Linux equivalents, and there are no explicit Linux-specific examples or notes. Where OS types are mentioned, Windows is listed first, and EFI support is only detailed for Windows Server, with no equivalent Linux guidance. There are no PowerShell or Windows command-line examples, but the lack of Linux-specific instructions or parity in EFI/failover support constitutes a bias.
Recommendations
- Explicitly document Linux EFI/UEFI support status for Azure Site Recovery, including any limitations or requirements.
- When listing OS types or features, present Windows and Linux options with equal prominence and detail.
- If there are differences in failover/failback support or prerequisites for Linux VMs, clearly state them.
- Add Linux-specific examples or notes where relevant (e.g., for disk partitioning, boot types, or supported distributions).
- Ensure that any references to OS-specific features (such as boot types or mobility service versions) include Linux details where applicable.
Site Recovery
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/vmware-azure-mobility-install-configuration-mgr.md
...ery/vmware-azure-mobility-install-configuration-mgr.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation demonstrates a mild Windows bias by consistently listing Windows-related instructions, tools, and examples before their Linux equivalents. Microsoft Configuration Manager (a Windows-centric tool) is emphasized as the primary automation solution, with Linux support presented as a secondary consideration. While Linux instructions and scripts are provided, the structure and flow of the documentation prioritize Windows environments and tools.
Recommendations
- Alternate the order of Windows and Linux instructions/examples throughout the documentation to avoid always listing Windows first.
- Highlight cross-platform or Linux-native deployment tools (such as Ansible, Puppet, or Chef) alongside Configuration Manager and JetPatch, providing equivalent automation instructions for those tools.
- Where possible, provide Linux-specific screenshots and UI walkthroughs, not just Windows-centric ones.
- Explicitly state parity of support and capabilities between Windows and Linux at the beginning of each section.
- Add a summary table or section at the top that clearly shows all supported platforms and tools, giving Linux equal prominence.
Site Recovery
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/vmware-azure-set-up-replication-tutorial-modernized.md
...ttps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/vmware-azure-set-up-replication-tutorial-modernized.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation provides general guidance for setting up VMware VM disaster recovery to Azure, but when mentioning OS-specific steps (such as credentials for Mobility Service installation), it lists Windows before Linux and provides more detail for Windows. There are no explicit command-line examples for either OS, but the only OS-specific note is that for Linux, root credentials are needed, while for Windows, admin privileges are required. There are no Linux-specific troubleshooting steps, examples, or parity in depth of explanation.
Recommendations
- Provide explicit Linux and Windows examples side by side for any manual steps, such as Mobility Service installation, credential requirements, or troubleshooting.
- When mentioning OS-specific requirements, list Linux and Windows in parallel (e.g., 'For Linux, provide root credentials; for Windows, provide an admin account') rather than always listing Windows first.
- Include links to Linux-specific documentation or troubleshooting guides where appropriate.
- If there are differences in agent installation or configuration between Linux and Windows, provide step-by-step instructions for both.
- Ensure screenshots and UI walkthroughs clarify any OS-specific differences, especially for Linux users.
Site Recovery
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/vmware-azure-install-linux-master-target.md
...e-recovery/vmware-azure-install-linux-master-target.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation is focused on Linux master target installation, but it contains several references to Windows tools and paths (e.g., copying files from C:\Program Files and C:\ProgramData on Windows servers). The process server and configuration server are assumed to be Windows-based, with no mention of Linux alternatives or parity. Windows paths and instructions are given without Linux equivalents, and the process for obtaining required files relies on Windows infrastructure.
Recommendations
- Provide instructions for environments where the process server and configuration server are running on Linux, if supported, or clarify if only Windows is supported.
- When referencing file paths (such as for the passphrase or installer), include Linux equivalents or note platform limitations.
- If Windows-only infrastructure is required for some components, make this explicit in the prerequisites and explain why.
- Consider offering a workflow or guidance for users who have a predominantly Linux environment, or at least acknowledge the limitation.
- Where possible, provide cross-platform examples or clarify which steps are Windows-specific and which are Linux-agnostic.
Site Recovery
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/vmware-azure-troubleshoot-failback-reprotect.md
...covery/vmware-azure-troubleshoot-failback-reprotect.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Summary
The documentation references both Windows and Linux VMs, but provides more detail and positive outcomes for Windows (e.g., static IP restoration), while Linux users are left with manual steps and less guidance. There are no command-line examples for either platform, but Windows is mentioned as regaining its static IP automatically, whereas Linux requires manual intervention. No Linux-specific troubleshooting tools or commands are suggested, and Windows is mentioned first in the static IP context.
Recommendations
- Provide equivalent, detailed troubleshooting steps for Linux VMs, including specific commands to set static IP addresses (e.g., using nmcli or editing /etc/network/interfaces).
- Include Linux command-line examples for common troubleshooting tasks (e.g., checking service status, network configuration).
- Mention Linux tools (such as systemctl, nmcli, ifconfig, ip) alongside Windows tools where relevant.
- Ensure that Linux and Windows scenarios are presented with equal depth and clarity, and avoid presenting Windows as the default or more seamless experience.
- Where possible, present Linux and Windows solutions in parallel, rather than mentioning Windows first or exclusively.
Site Recovery
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/vmware-azure-tutorial-failover-failback-modernized.md
...https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/vmware-azure-tutorial-failover-failback-modernized.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation shows a subtle Windows bias: when discussing how to connect to failed-over VMs, it mentions RDP (Windows) and SSH (Linux), but the subsequent link for connecting to a VM points only to Windows instructions. There are no Linux-specific connection or validation steps, and no Linux command-line or troubleshooting examples. Additionally, when referencing boot drivers that may impact failover time, only Windows-specific drivers are listed, with no mention of Linux equivalents or guidance.
Recommendations
- Provide explicit Linux examples and links alongside Windows ones, especially for connecting to VMs (e.g., link to both Windows RDP and Linux SSH connection guides).
- Include Linux-specific troubleshooting steps and validation procedures after failover.
- When listing boot drivers or prerequisites, mention both Windows and Linux drivers or provide guidance for Linux VMs.
- Ensure that any references to tools or procedures (such as command-line validation or post-failover checks) are given for both Windows and Linux environments.
- Consider a section or callout specifically for Linux VM considerations in failover scenarios.
Site Recovery
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/vmware-troubleshoot-mobility-agent-health.md
...-recovery/vmware-troubleshoot-mobility-agent-health.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation generally maintains parity between Linux and Windows in log file locations, but there are subtle signs of Windows bias. In error message examples, Windows file paths and hostnames (e.g., C:\ paths, WIN- hostnames) are used, and Windows service names are referenced without Linux equivalents. Service restart instructions mention only Windows service names, omitting Linux systemd/service commands or service names. No explicit Linux troubleshooting commands or service management steps are provided.
Recommendations
- For every mention of Windows service names (e.g., 'Process Server', 'Microsoft Azure RCM Proxy Agent'), include the equivalent Linux service names and instructions (e.g., systemctl restart servicename).
- When showing log file paths or error messages, provide both Linux and Windows examples, or clarify when examples are OS-specific.
- If referencing hostnames or file paths in error logs, alternate between Linux and Windows examples, or provide both.
- Include Linux-specific troubleshooting steps where relevant, such as commands to restart services or check logs on Linux systems.
- Ensure parity in all procedural steps, not just in file locations, but also in operational commands and terminology.
Site Recovery
Troubleshoot Azure VM replication in Azure Site Recovery - other issues
...es/site-recovery/azure-to-azure-troubleshoot-errors.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation generally maintains parity between Windows and Linux troubleshooting steps, especially in the 'Trusted root certificates' section, which provides detailed instructions for both platforms. However, there are several sections where Windows is prioritized or referenced first, such as service management (COM+ and VSS) and proxy autodetection (Internet Explorer), and Windows tools (Services console, Internet Explorer) are mentioned without Linux equivalents. Some examples and screenshots are Windows-centric, and instructions for Windows sometimes precede those for Linux, which may create minor friction for Linux/macOS users.
Recommendations
- Ensure that troubleshooting steps for both Windows and Linux are presented with equal prominence, ideally side-by-side or in parallel tabs.
- Where Windows tools (e.g., Services console, Internet Explorer) are referenced, provide Linux/macOS equivalents or clarify if the issue is Windows-specific.
- Add Linux/macOS screenshots or command-line examples where only Windows screenshots are shown.
- Avoid referencing Windows-specific patterns (like proxy autodetection from Internet Explorer) without noting the Linux alternative (e.g., environment variables, config files).
- In sections where Windows instructions are given first, consider alternating or grouping by OS to avoid implicit prioritization.
Site Recovery
Support Matrix for Azure VM Disaster Recovery with Azure Site Recovery
...rticles/site-recovery/azure-to-azure-support-matrix.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation generally provides parity between Windows and Linux, with detailed support matrices for both. However, there are minor signs of Windows bias: in the 'Deployment method support' and 'Cache storage' sections, Azure PowerShell is mentioned and linked as the primary automation method, with no equivalent Linux CLI support (Azure CLI is explicitly 'Not currently supported'). Additionally, PowerShell is referenced before REST API, and Linux users are directed to use the portal or REST API, which may be less familiar or convenient for automation. The order of operating systems in the support matrix lists Windows first, which is a common but minor bias.
Recommendations
- Clarify that Azure CLI is not supported for both Windows and Linux, and provide guidance for Linux users on using REST API or portal for automation.
- Where PowerShell is referenced as a method for automation (e.g., cross-subscription cache storage), explicitly state that PowerShell is cross-platform and can be used on Linux/macOS, or provide REST API examples for Linux users.
- Consider listing Linux operating systems before or alongside Windows in support matrices to avoid implicit prioritization.
- If possible, provide sample REST API calls or scripts for common operations currently only documented with PowerShell.
Site Recovery
Troubleshoot connectivity for Azure to Azure disaster recovery with Azure Site Recovery
...ry/azure-to-azure-troubleshoot-network-connectivity.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation generally describes troubleshooting steps for Azure-to-Azure disaster recovery in a platform-neutral way, focusing on Azure portal and NSG configuration. However, there are subtle Windows biases: proxy autodetection is described as using Internet Explorer on Windows, with Linux mentioned second; the proxy configuration file location is shown for both OSes, but the autodetection pattern is Windows-centric. No command-line examples (PowerShell, Bash) are given, but the only autodetection method described is Windows-first. There are no Linux-specific troubleshooting examples or screenshots.
Recommendations
- Describe proxy autodetection on Linux in more detail, including which environment variables or configuration files are used.
- Provide Linux-first or parallel examples/screenshots where OS-specific steps are needed.
- If command-line troubleshooting is relevant (e.g., checking DNS or connectivity), include both PowerShell and Bash examples.
- Clarify that the Mobility service agent supports autodetection on both platforms, and document any differences in behavior.
Site Recovery
Azure Virtual Machines disaster recovery - High Churn support
...recovery/concepts-azure-to-azure-high-churn-support.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation generally treats Windows and Linux VMs equally, but in the 'Support matrix' section for Enhanced Churn (500 MB/s preview), the operating system support is listed as 'Windows. Linux – RHEL 9, SLES 15, Ubuntu 24.04.' This places Windows first and lists only three Linux distributions, which may suggest a slight Windows-first bias. However, the rest of the documentation is generic and does not use Windows-specific tools, commands, or examples.
Recommendations
- Clarify Linux support by listing all supported distributions or linking to a comprehensive support matrix.
- Consider listing Windows and Linux support together (e.g., 'Supported operating systems: Windows, Linux (RHEL 9, SLES 15, Ubuntu 24.04)').
- If feature parity is not complete for Linux, explicitly state any limitations or differences for Linux VMs.
Site Recovery
Enable accelerated networking for Azure VM disaster recovery with Azure Site Recovery
...azure-vm-disaster-recovery-with-accelerated-networking.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation presents Windows VM instructions and supported OS lists before Linux equivalents, but both platforms are covered with parity. No PowerShell-heavy or Windows-only tooling is present, and Linux-specific links/examples are provided. The order of presentation is the only minor bias detected.
Recommendations
- Alternate the order of Windows and Linux sections in future revisions, or present them side-by-side to avoid implicit prioritization.
- Explicitly state that both Windows and Linux VMs are supported at the start of the relevant sections.
- Ensure that screenshots and UI references are equally applicable to both platforms, or clarify any platform-specific differences.
Site Recovery
About failover and failback in Azure Site Recovery - Modernized
...site-recovery/failover-failback-overview-modernized.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation provides both Windows and Linux guidance for connecting to Azure VMs after failover, but Windows instructions are listed first and are more detailed, mentioning specific Windows tools (Windows Firewall, Windows Update, SAN policy). Linux instructions are present but less detailed and do not mention equivalent Linux firewall or system configuration tools. The rest of the documentation is generally platform-neutral, with separate sections for VMware and Hyper-V where appropriate.
Recommendations
- Present Windows and Linux instructions in parallel or alternate order to avoid implicit prioritization.
- Expand Linux guidance to match the detail level of Windows instructions, e.g., mention specific Linux firewall configuration steps (such as using ufw, firewalld, or iptables), handling pending updates, and SAN policy equivalents if relevant.
- Where Windows-specific tools are mentioned (Windows Firewall, Windows Update), provide Linux equivalents or clarify if not applicable.
- Ensure troubleshooting links and tips are provided for both platforms.