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 151-175 of 864 flagged pages
Site Recovery
Remove servers and disable protection
...ry/site-recovery-manage-registration-and-protection.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation is heavily focused on Windows environments, specifically System Center VMM and Hyper-V, and provides only PowerShell scripts and Windows-specific instructions. There are no Linux or cross-platform examples, and all automation and cleanup steps assume Windows tooling and registry/certificate management. VMware and physical server scenarios are mentioned, but no Linux-specific guidance or scripts are provided.
Recommendations
- Add equivalent instructions and scripts for Linux-based servers where applicable, especially for VMware or physical server scenarios that may run on Linux.
- Where PowerShell is used, provide Bash or shell script alternatives for Linux environments, or clarify when steps are Windows-only.
- Explicitly state OS requirements and limitations for each scenario, and provide links to Linux-specific documentation if available.
- Include examples or references for managing replication and cleanup on Linux-based VMs or physical servers.
- Review all sections for opportunities to mention Linux tools (e.g., SSH, Linux service management, Linux file paths) alongside Windows tools.
Create Pull Request
Site Recovery
Support matrix for shared disks in Azure VM disaster recovery
...n/articles/site-recovery/shared-disk-support-matrix.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page exclusively references Windows environments, specifically Windows virtual machines, Windows Server SKUs, and Windows Server Failover Clustering (WSFC). There are no examples, scenarios, or mentions of Linux workloads, Linux clustering solutions, or cross-platform support. This creates a strong Windows bias and leaves Linux users without guidance or clarity on support or alternatives.
Recommendations
- Explicitly state whether Linux workloads and clustering solutions (e.g., Pacemaker, Corosync) are supported or not.
- Add a section or table for Linux support, including supported distributions, clustering configurations, and any limitations.
- Provide Linux-specific examples and guidance for disaster recovery setup and shared disk usage.
- If Linux is not supported, clarify this early in the documentation to set expectations for cross-platform users.
Site Recovery
Enable VMware VMs (Modernized) for disaster recovery using Azure Site Recovery
...icles/site-recovery/vmware-azure-enable-replication.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation page exhibits Windows bias in several ways: Windows-specific requirements (e.g., UEFI-enabled VMs must be Windows), PowerShell is the only automation example mentioned, and Windows licensing features (Azure Hybrid Benefit) are highlighted without Linux equivalents. There are no Linux-specific examples, tools, or parity notes, and Windows terminology and tools are referenced first or exclusively.
Recommendations
- Include Linux-specific examples and guidance, such as how to replicate Linux VMs, handle Linux disk formats, and address common Linux issues.
- Provide automation examples using Bash, Azure CLI, or REST API, not just PowerShell.
- Mention Linux licensing considerations and clarify Azure Hybrid Benefit applicability for Linux workloads.
- Ensure that prerequisites and troubleshooting sections address Linux-specific scenarios (e.g., supported Linux distributions, kernel requirements, disk partitioning).
- Balance references to Windows and Linux tools, patterns, and terminology throughout the documentation.
Site Recovery
Scale VMware/physical disaster recovery with Azure Site Recovery
...cles/site-recovery/vmware-physical-large-deployment.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias in several ways: PowerShell is the only automation example given for triggering failover, Windows compliance is discussed in detail while Linux is mentioned only briefly, and troubleshooting/failover preparation steps focus on Windows tools and patterns. There are no Linux shell or automation examples, and Windows-specific instructions (such as compliance checks and runbooks) are provided before or instead of Linux equivalents.
Recommendations
- Provide equivalent Linux shell (bash) or CLI examples for automation tasks, such as triggering failover.
- Expand compliance preparation steps for Linux machines, including proactive checks and remediation instructions, not just at failover time.
- Include Linux-specific troubleshooting and monitoring guidance, alongside Windows instructions.
- Mention Linux tools and patterns (e.g., shell scripts, Ansible, Azure CLI) in parallel with Windows/PowerShell examples.
- Ensure that examples and instructions for both Windows and Linux are presented with equal prominence and detail.
Site Recovery
Transport Layer Security in Azure Site Recovery
...ain/articles/site-recovery/transport-layer-security.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation is heavily focused on Windows environments, providing only Windows-specific instructions (registry edits, KB articles, .NET Framework configuration) and examples. There is no mention of Linux systems, nor are there any Linux-specific steps, tools, or configuration guidance. All troubleshooting and configuration guidance is centered around Windows components and tools.
Recommendations
- Add equivalent instructions for enabling and verifying TLS 1.2 on Linux systems, such as updating OpenSSL, configuring stunnel, or modifying system-wide TLS settings.
- Include examples for common Linux distributions (e.g., Ubuntu, CentOS) showing how to check and enforce TLS 1.2 usage.
- Provide troubleshooting steps for TLS issues on Linux, including relevant log locations and commands.
- Reference Linux documentation and tools (e.g., openssl, systemd, configuration files) alongside Windows registry and KB articles.
- Clarify Azure Site Recovery support and requirements for Linux-based source or target machines, if applicable.
Site Recovery
Set up a scale-out process server during disaster recovery of VMware VMs and physical servers with Azure Site Recovery | Microsoft Docs
...e-recovery/vmware-azure-set-up-process-server-scale.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page demonstrates Windows bias by exclusively referencing Windows tools and installation patterns (e.g., UnifiedSetup.exe, .exe installers, Windows-style paths like C:\Temp\Extracted), and does not provide any Linux-specific instructions or examples for deploying or managing process servers. There are no bash commands, Linux package references, or guidance for Linux environments, despite the fact that many VMware and physical server environments may be Linux-based.
Recommendations
- Include Linux installation instructions, such as using shell scripts, RPM/DEB packages, or tarballs.
- Provide command-line examples for Linux (e.g., bash commands, Linux file paths).
- Clarify OS requirements and support for the process server, explicitly stating whether Linux is supported and, if so, how to deploy on Linux.
- Offer parity in troubleshooting and configuration guidance for both Windows and Linux environments.
- Add notes or sections that address differences in setup between Windows and Linux, if applicable.
Site Recovery
Troubleshoot VMware replication appliance health issues in Azure Site Recovery
...recovery/vmware-troubleshoot-appliance-health-issue.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page demonstrates a Windows bias by providing troubleshooting steps that exclusively use PowerShell commands and Windows file paths. There is no mention of Linux equivalents or alternative approaches for non-Windows environments. The use of Windows-specific tools (e.g., PowerShell, 'C:\Program Files') and the absence of Linux troubleshooting guidance suggest that the documentation is primarily targeted at Windows users, potentially excluding IT administrators who manage VMware appliances on Linux platforms.
Recommendations
- Add Linux-specific troubleshooting steps, including shell commands and file paths relevant to Linux deployments.
- Provide alternative instructions for running scripts on Linux, such as using Bash or Python equivalents.
- Include notes clarifying platform-specific procedures and explicitly state if certain steps are Windows-only.
- Ensure parity in examples by presenting both Windows and Linux options side-by-side where applicable.
Site Recovery
Troubleshoot the Azure Site Recovery process server
...y/vmware-physical-azure-troubleshoot-process-server.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Powershell Heavy
Summary
The documentation page exhibits a strong Windows bias. Troubleshooting steps and examples consistently reference Windows-specific tools (e.g., Task Manager, Resource Monitor, Control Panel, registry keys, Windows log file paths, Telnet installation via Windows instructions, and references to Windows services). There are no Linux-specific troubleshooting steps, commands, or log locations provided, despite the fact that process servers could be deployed on Linux or Linux source machines could be involved in VMware/physical server scenarios. The documentation assumes a Windows environment for both the process server and the source machine, omitting Linux equivalents and guidance.
Recommendations
- Add Linux-specific troubleshooting steps and examples for each major procedure (e.g., checking services, viewing logs, verifying network connectivity, checking resource usage).
- Include Linux command equivalents for tools like Task Manager (e.g., top, htop, systemctl, journalctl, netstat, ss, etc.).
- Document Linux log file locations and service names relevant to Azure Site Recovery process server deployments.
- Provide instructions for installing and using Telnet and other network troubleshooting tools on Linux.
- Mention Linux firewall configuration steps (e.g., iptables, firewalld, ufw) alongside Windows firewall instructions.
- Reference Linux proxy settings and configuration methods.
- Ensure that all examples and screenshots are provided for both Windows and Linux environments, or clarify platform-specific applicability.
Site Recovery
Fail back Azure VMware Solution VMsfrom Azure with Azure Site Recovery
...b/main/articles/site-recovery/avs-tutorial-failback.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates Windows bias by specifically mentioning Windows VMs and their interaction with VMware tools during failover/failback, without referencing Linux VMs or their equivalent processes. There are no examples or notes for Linux VMs, and the only OS-specific guidance is for Windows. This suggests a prioritization of Windows environments and tools, with Linux scenarios omitted.
Recommendations
- Add explicit guidance for Linux VMs, including any differences in failover/failback behavior and agent/tool handling.
- Include notes on how VMware tools interact with Linux VMs during failover/failback, or clarify if there are no changes.
- Provide troubleshooting steps or considerations specific to Linux VMs, such as agent registration or OS-specific error messages.
- Ensure parity in examples and notes by mentioning both Windows and Linux VMs where relevant.
Site Recovery
Fail over Azure VMware Solution VMs to Azure by using Site Recovery
...b/main/articles/site-recovery/avs-tutorial-failover.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page exhibits Windows bias by referencing Windows-specific concepts and links before Linux equivalents, such as linking to Windows availability sets and VM connection guides. There are no explicit Linux or cross-platform examples for connecting to VMs or configuring failover, and troubleshooting or validation steps are oriented toward Windows tools and patterns.
Recommendations
- Include Linux-specific examples and links alongside Windows references, such as connecting to VMs via SSH and managing Linux VM properties.
- Add references to Linux documentation for availability sets and VM connectivity.
- Provide troubleshooting steps and validation guidance for both Windows and Linux VMs after failover.
- Ensure that all instructions and links are platform-neutral or presented in parallel for Windows and Linux users.
Site Recovery
Prepare Azure VMware Solution for disaster recovery to Azure Site Recovery
...ain/articles/site-recovery/avs-tutorial-prepare-avs.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows-first bias in several sections. Windows-specific instructions (such as registry edits and firewall settings) are provided in greater detail and appear before Linux equivalents. Windows tools and patterns (like RDP, Windows Firewall, registry keys) are mentioned explicitly, while Linux instructions are brief and lack comparable detail or troubleshooting guidance. There are also missing Linux-specific examples for some steps, such as troubleshooting connectivity after failover.
Recommendations
- Provide Linux instructions and examples alongside Windows instructions, ensuring parity in detail and troubleshooting steps.
- Include Linux-specific troubleshooting guidance for SSH connectivity after failover, similar to the RDP troubleshooting provided for Windows.
- Mention Linux tools (such as firewalld, ufw, or iptables) when discussing firewall rules, and provide example commands.
- When discussing account preparation for Mobility service installation, offer more detailed Linux steps (e.g., required sudoers configuration, SSH key setup, or package prerequisites).
- Avoid always listing Windows steps first; alternate or present both OSes in parallel for each relevant section.
- Ensure that all references to tools (such as Boot diagnostics) clarify their applicability to both Windows and Linux VMs.
Site Recovery
Common questions about Azure virtual machine disaster recovery with Azure Site Recovery
...icles/site-recovery/azure-to-azure-common-questions.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in several ways: Windows-specific features and tools (such as PowerShell and VSS) are mentioned before or instead of Linux equivalents, examples and instructions often reference PowerShell without providing CLI or Linux alternatives, and Windows-centric terminology (e.g., ADE for Windows, SQL Server extensions) is prevalent. Linux support is referenced but not detailed, and Linux-specific instructions or examples are frequently missing.
Recommendations
- Provide Azure CLI and Bash examples alongside PowerShell instructions, especially for tasks like selecting automation accounts, excluding disks, and enabling replication.
- Explicitly mention and document Linux equivalents for features such as disk encryption, app-consistent snapshots, and extension management.
- Ensure that Linux support is described with equal detail, including limitations, supported scenarios, and step-by-step instructions.
- Add examples and links for Linux VM disaster recovery scenarios, including shared disk support, custom scripts for app-consistency, and failover automation.
- Avoid Windows-first ordering in lists and explanations; present Windows and Linux options side-by-side.
- Clarify when features are Windows-only and provide alternative recommendations for Linux users where possible.
Site Recovery
Replicate Azure virtual machines running Storage Spaces Direct with Azure Site Recovery
...ry/azure-to-azure-how-to-enable-replication-s2d-vms.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation is heavily focused on Windows-specific technologies, particularly Storage Spaces Direct (S2D) and Windows Failover Clustering. All examples, terminology, and referenced tools are Windows-centric, with no mention of Linux alternatives or guidance for Linux-based clusters. There are no Linux commands, patterns, or parity considerations, and the documentation assumes the use of Windows guest clusters exclusively.
Recommendations
- Include guidance for replicating Linux-based clusters or virtual machines using Azure Site Recovery.
- Provide examples and diagrams for Linux failover solutions (e.g., using Pacemaker, DRBD, or other Linux HA tools).
- Mention Linux-supported storage solutions and how they can be protected with Site Recovery.
- Clarify in the introduction whether the process is Windows-only, or add a section for Linux users.
- If Azure Site Recovery does not support Linux clusters in this scenario, explicitly state this limitation and link to alternative documentation for Linux disaster recovery.
Site Recovery
Set up Azure Site Recovery for Azure VMware Solution VMs
...ain/articles/site-recovery/avs-tutorial-replication.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by exclusively describing the configuration server VM as running Windows Server 2016, requiring Windows activation, and providing step-by-step instructions for Windows setup and credentials. Linux is only mentioned briefly as an alternative for VM credentials, with no Linux setup or examples provided. All screenshots and instructions are tailored to Windows environments, and there is no parity in guidance for Linux-based configuration servers or process servers.
Recommendations
- Provide explicit instructions and examples for setting up the configuration server and process server on Linux VMs, if supported.
- Include Linux-specific credential requirements, installation steps, and troubleshooting guidance alongside Windows instructions.
- Add screenshots and walkthroughs for Linux environments, such as Ubuntu or CentOS, where applicable.
- Clarify whether Linux-based configuration servers are supported, and if not, state this limitation clearly.
- Ensure parity in documentation for both Windows and Linux users, including activation, licensing, and network configuration steps.
Site Recovery
Replicate Azure Stack Hub to Azure using Azure Site Recovery
...in/articles/site-recovery/azure-stack-site-recovery.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in several ways: Windows operating systems and procedures are listed before Linux equivalents, with more detailed instructions and examples for Windows (e.g., registry edits, firewall configuration via GUI and GPO, references to Windows command prompt and tools like wf.msc). Linux instructions are present but less detailed, lacking command-line examples and step-by-step parity. The page references Windows-specific tools and patterns (e.g., RDP, registry edits, VSS) without Linux alternatives or equivalent depth.
Recommendations
- Provide Linux command-line examples for all steps where Windows commands are shown (e.g., registry edits, firewall configuration).
- Include Linux-specific tools and procedures (e.g., iptables or firewalld for firewall configuration, SSH for remote access) with equal detail and screenshots where appropriate.
- List Linux operating systems and instructions before or alongside Windows, rather than after.
- Offer parity in troubleshooting, prerequisites, and configuration steps for both platforms.
- Reference Linux equivalents for Windows-specific features (e.g., mention Linux snapshot tools if VSS is discussed).
- Ensure that all diagrams and screenshots include Linux scenarios, not just Windows.
Site Recovery
Enable replication for encrypted Azure VMs in Azure Site Recovery
...ry/azure-to-azure-how-to-enable-replication-ade-vms.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page demonstrates a Windows bias in several ways: all scripting examples for copying disk encryption keys use PowerShell, with explicit instructions to use the Windows PowerShell application. There are no equivalent examples or scripts for Linux users (e.g., Bash, Azure CLI). The CopyKeys script is provided only as a PowerShell (.ps1) file, and the workflow assumes a Windows environment. While the documentation mentions Linux support limitations, it does not provide Linux-specific guidance or parity in tooling or examples. Windows tools and patterns are referenced exclusively and before any Linux alternatives (which are absent).
Recommendations
- Provide equivalent Linux/Bash/Azure CLI examples for key copying and management, including sample scripts.
- Clarify whether the CopyKeys script can be run on Linux (e.g., via PowerShell Core), and if so, provide instructions; if not, offer alternative methods for Linux users.
- Include Azure CLI commands for relevant operations (e.g., key vault permissions, key copying, replication management) alongside PowerShell examples.
- Explicitly address Linux administrator workflows and highlight any differences or limitations, ensuring Linux users can follow the documentation without switching to Windows.
- Add troubleshooting steps and examples for Linux environments where appropriate.
Site Recovery
Support Matrix for Azure VM Disaster Recovery with Azure Site Recovery
...rticles/site-recovery/azure-to-azure-support-matrix.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation page exhibits moderate Windows bias. Azure PowerShell is repeatedly referenced as the primary automation tool for deployment and advanced scenarios, with no mention of Linux-native equivalents (e.g., Bash scripting, Ansible, or Terraform). Windows operating systems are listed first and in greater detail than Linux, and Windows-specific requirements (such as SSU/SHA-2 updates) are described at length. In several tables and instructions, PowerShell is the only automation method given for tasks like cross-subscription cache storage setup and disk exclusion, while Azure CLI is explicitly marked as 'not currently supported.'
Recommendations
- Add Linux-native automation examples (e.g., Bash scripts, Ansible, Terraform) for deployment and management tasks where PowerShell is referenced.
- Where Azure PowerShell is recommended, clarify if and when Azure CLI or other cross-platform tools will be supported, and provide parity in documentation when available.
- List Linux operating systems and features before or alongside Windows to avoid the perception of Windows-first bias.
- Include troubleshooting and upgrade instructions for Linux with the same level of detail as for Windows (e.g., agent installation, kernel compatibility issues).
- Where PowerShell is the only option, note any workarounds or alternatives for Linux users, and provide roadmap information if CLI or other tools are planned.
Site Recovery
Set up disaster recovery after migration to Azure with Azure Site Recovery
...e-recovery/azure-to-azure-replicate-after-migration.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by consistently presenting Windows instructions and tools first, providing more detailed steps and validation for Windows (e.g., navigating to folders, checking file properties), and referencing Windows-specific tools (Control Panel, MsiExec.exe). Linux instructions are less detailed, lack parity in validation steps, and do not provide troubleshooting or alternative package manager commands. There is also a lack of Linux-specific troubleshooting guidance and examples.
Recommendations
- Present Linux and Windows instructions in parallel, or alternate which platform is described first.
- Provide equally detailed validation steps for Linux, such as checking agent version and installation status.
- Include Linux-specific troubleshooting guidance and references.
- Offer alternative Linux package manager commands (e.g., yum, apt) for agent installation and removal.
- Avoid referencing Windows tools (Control Panel, MsiExec.exe) without Linux equivalents or explanations.
- Ensure all examples and instructions are provided for both platforms, with equal clarity and detail.
Site Recovery
Troubleshoot connectivity for Azure to Azure disaster recovery with Azure Site Recovery
...ry/azure-to-azure-troubleshoot-network-connectivity.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in several ways: Windows-specific tools and patterns (such as Internet Explorer for proxy autodetection) are mentioned before their Linux equivalents, and examples or troubleshooting steps often reference Windows paths and interfaces first. There is a lack of parity in example commands or screenshots for Linux environments, with most configuration guidance and UI references tailored to Windows users. Linux-specific troubleshooting is only briefly mentioned and lacks detailed guidance or examples.
Recommendations
- Provide Linux-specific examples and screenshots for tasks such as checking DNS settings, configuring NSG rules, and troubleshooting connectivity.
- Mention Linux tools and configuration files (e.g., resolv.conf, systemd-resolved, iptables) alongside Windows equivalents, and ensure they are given equal prominence.
- Include step-by-step instructions for common Linux distributions (Ubuntu, RHEL, etc.) where relevant, especially for proxy configuration and network troubleshooting.
- Clarify when guidance applies to both platforms, and avoid assuming Windows as the default environment.
- Add PowerShell and Azure CLI examples side-by-side, and include Bash commands for Linux users.
Site Recovery
Troubleshoot Azure VM replication in Azure Site Recovery - other issues
...es/site-recovery/azure-to-azure-troubleshoot-errors.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation displays Windows bias in several ways: Windows troubleshooting steps and tools (such as Services console, COM+, VSS, Internet Explorer) are described in detail, often before or instead of Linux equivalents. Windows-specific patterns (like referencing Internet Explorer for proxy autodetection) are mentioned without Linux alternatives. Some troubleshooting sections provide only Windows examples or tools, while Linux guidance is less detailed or missing. In some cases, Linux instructions are present but less comprehensive or appear after Windows instructions.
Recommendations
- Ensure Linux troubleshooting steps are provided with equal detail and prominence as Windows steps.
- Include Linux-specific tools and commands (e.g., systemctl for service management, alternatives to Internet Explorer for proxy detection) where Windows tools are referenced.
- Present Windows and Linux instructions side-by-side or in parallel tabs, rather than listing Windows first.
- Avoid referencing Windows-only tools (like Internet Explorer) without Linux alternatives; clarify how Linux users can perform equivalent actions.
- Where possible, provide explicit Linux examples for all troubleshooting scenarios, not just for certificate management or disk encryption.
- Review for any missing Linux error codes or scenarios and add them for parity.
Site Recovery
Troubleshoot replication of Azure VMs with Azure Site Recovery
...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 page demonstrates a Windows bias in several ways. Troubleshooting steps and examples frequently reference Windows-specific tools, file paths, and commands (e.g., PowerShell, VSS, Windows service names, and Windows file locations) before or instead of Linux equivalents. Instructions for excluding disks use PowerShell, and VSS troubleshooting is exclusively Windows-centric. Linux is only briefly mentioned in the context of app-consistency, with minimal guidance and no command-line examples. Most troubleshooting logs and service restart instructions are detailed for Windows, with Linux steps often omitted or less detailed.
Recommendations
- Provide equivalent Linux command-line examples (e.g., Bash, CLI) alongside PowerShell instructions.
- Include Linux-specific troubleshooting steps for disk exclusion, service management, and log file locations.
- Mention Linux tools (such as systemctl, journalctl, or relevant shell commands) where Windows services are referenced.
- Ensure parity in error code explanations and log file analysis for both Windows and Linux.
- Expand the Linux app-consistency section with concrete examples and step-by-step instructions.
- Where file paths or service names are given for Windows, always provide the Linux equivalents in parallel.
Site Recovery
Troubleshoot Azure VM replication in Azure Site Recovery - VM errors
...site-recovery/azure-to-azure-virtual-machine-errors.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page displays Windows bias in several ways: Windows instructions and links are consistently listed before Linux equivalents (e.g., disk initialization), and the only provided script for cleaning up stale Site Recovery configurations is a PowerShell script (.ps1), with no mention of a Linux/bash alternative. There are no Linux-specific troubleshooting scripts or command examples for common tasks, and the guidance assumes use of Windows tooling for automation and scripting.
Recommendations
- Present Windows and Linux instructions side-by-side or in parallel, rather than listing Windows first.
- Provide bash or Azure CLI script alternatives for tasks currently covered only by PowerShell scripts, such as cleaning up stale Site Recovery configurations.
- Include Linux-specific troubleshooting steps and examples where relevant, especially for automation tasks.
- Explicitly mention cross-platform tools (e.g., Azure CLI) and provide examples for both Windows and Linux environments.
- Review all linked resources to ensure Linux parity in guidance and examples.
Site Recovery
About using ExpressRoute with Azure Site Recovery
...e-recovery/concepts-expressroute-with-site-recovery.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Missing Linux Example
Windows First
Summary
The documentation page demonstrates Windows bias in several ways: it provides only Windows-specific instructions (such as using PsExec and Internet Explorer for proxy configuration), omits equivalent Linux guidance, and references Windows tools and patterns exclusively. There are no Linux or cross-platform examples for proxy bypass configuration, and the workflow assumes a Windows environment by default.
Recommendations
- Add Linux-specific instructions for configuring proxy bypass lists on Configuration Server and Process Servers, including relevant commands and file locations.
- Provide examples using Linux tools (e.g., curl, iptables, or relevant configuration files) alongside Windows tools.
- Reference cross-platform browsers or command-line utilities instead of only Internet Explorer.
- Ensure that all steps and examples are presented for both Windows and Linux environments, or clarify platform-specific requirements.
- Consider reordering examples so that Linux and Windows instructions are presented together, or Linux is not always secondary.
Site Recovery
Trusted launch VMs with Azure Site Recovery
...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 exhibits Windows bias by prioritizing Windows support and scenarios, such as shared disks and VM creation flows being available only for Windows OS, with Linux support lagging or missing. There are no Linux-specific examples or CLI commands, and Windows features are mentioned first or exclusively in several places.
Recommendations
- Provide Linux-specific examples and step-by-step instructions, especially for migration and agent uninstallation.
- Clarify CLI and PowerShell parity for both Windows and Linux, including explicit Linux command-line instructions.
- List Linux limitations alongside Windows ones, and update the support matrix to show equal detail for both OS types.
- Add troubleshooting and usage notes for Linux users, especially where features are Windows-only or Linux support is pending.
- Ensure that all workflows (e.g., VM creation, shared disks) mention Linux status and alternatives, not just Windows.
Site Recovery
Remove an Azure Site Recovery replication appliance
...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 a Windows bias by exclusively referencing Windows tools and workflows, such as 'Services.msc' and 'World Wide Web Publishing Service', and browser cache clearing instructions specific to Microsoft Edge. There are no Linux-specific instructions, examples, or references to equivalent Linux tools or processes for managing or resetting the appliance. The steps and terminology assume a Windows environment, omitting guidance for Linux-based deployments.
Recommendations
- Include Linux-specific instructions for managing and resetting the appliance, such as using systemctl to restart web services (e.g., 'systemctl restart apache2' or 'systemctl restart nginx').
- Provide examples for clearing browser cache in common Linux browsers (e.g., Firefox, Chromium).
- Reference Linux equivalents for Windows tools mentioned (e.g., instead of 'Services.msc', guide users to use 'systemctl' or 'service' commands).
- Add notes or sections clarifying steps for both Windows and Linux environments, ensuring parity and inclusivity for cross-platform users.
- Where screenshots or UI references are given, clarify if the appliance is Windows-only or provide alternative visuals for Linux-based appliances if supported.