Site Recovery
394
Total Pages
277
Linux-Friendly Pages
117
Pages with Bias
29.7%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
232 issues found
Showing 201-225 of 232 flagged pages
Site Recovery
Azure Site Recovery Deployment Planner Version History
...e-recovery/site-recovery-deployment-planner-history.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Heavy
Summary
The documentation lists Windows operating systems and features prominently and often before Linux equivalents in version histories. Windows OS support is called out in detail, with Linux distributions mentioned less frequently and sometimes grouped together. There are no explicit examples, but Windows support and issues are described more granularly than Linux. No Linux-specific tools, patterns, or troubleshooting are discussed.
Recommendations
- List Linux distributions and versions with the same granularity and prominence as Windows OSes.
- Ensure Linux support is mentioned alongside Windows in each relevant version, not as an afterthought.
- Include known limitations, fixes, and troubleshooting steps specific to Linux environments.
- If Windows-specific issues are described, provide equivalent Linux details where applicable.
- Consider adding a summary table showing OS support parity across versions.
Create Pull Request
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page for Azure Site Recovery demonstrates a mild Windows bias. Windows technologies (e.g., Windows Server Failover Clusters, SQL Server Always On, AWS Windows instances) are mentioned explicitly, and Windows-centric workloads and features (shared disk, SQL FCI, SAP ASCS) are highlighted. Linux is referenced only in passing (e.g., 'physical servers (Windows and Linux)'), with no Linux-specific examples, scenarios, or tools described. There are no PowerShell-heavy sections or Windows-only instructions, but Windows workloads and tools are consistently mentioned first and in greater detail.
Recommendations
- Add explicit Linux workload examples (e.g., protecting Linux-based databases, web servers, or SAP workloads).
- Include references to Linux failover clustering technologies (e.g., Pacemaker, Corosync) and how they integrate with Site Recovery.
- Provide parity in describing both Windows and Linux replication scenarios, including supported features and limitations.
- List Linux-specific automation or scripting options (e.g., Bash, Python) alongside Azure Automation runbooks.
- Highlight any differences or considerations for Linux users in the replication and failover process.
Site Recovery
Archive for What's new in Azure Site Recovery
...icles/site-recovery/site-recovery-whats-new-archive.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation provides a comprehensive archive of Azure Site Recovery updates, with frequent mention of both Windows and Linux support. However, there are several instances where Windows features, updates, and tools (such as PowerShell) are mentioned before their Linux equivalents, and some features are described as being supported via PowerShell only, with no mention of Linux CLI alternatives. Windows operating systems and tooling are often listed first in tables and feature summaries, which may subtly reinforce a Windows-centric perspective.
Recommendations
- Ensure that Linux CLI (az, bash) equivalents are mentioned wherever PowerShell is referenced, especially in sections like firewall-enabled storage accounts.
- When listing supported operating systems or features, alternate the order or group by platform to avoid consistently listing Windows first.
- Where features are described as 'supported using PowerShell only,' clarify if and when Linux CLI support will be available, or provide workarounds for Linux/macOS users.
- Add explicit examples or links for Linux/macOS users where Windows-specific tools or procedures are referenced.
- Review tables and feature lists to ensure parity in detail and prominence for Linux and macOS platforms.
Site Recovery
Fail back VMware VMs/physical servers from Azure with Azure Site Recovery
...b/main/articles/site-recovery/vmware-azure-failback.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation page exhibits minor Windows bias, primarily through a note that specifically discusses the behavior of VMware tools for Windows VMs during failover and failback, without mentioning Linux VMs or their equivalent tooling. No Linux-specific examples, caveats, or parity notes are provided, and Windows is referenced first and exclusively in the context of VM guest OS behavior.
Recommendations
- Add equivalent information for Linux VMs, such as how VMware tools are handled during failover/failback for Linux guests.
- Include any Linux-specific considerations, troubleshooting steps, or differences in the failback process.
- Explicitly state if the process is identical for Linux VMs, or highlight any differences.
- Provide examples or notes for both Windows and Linux VMs where guest OS behavior is relevant.
Site Recovery
Set up VMware VM disaster recovery to Azure with Azure Site Recovery - Modernized
...ttps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/vmware-azure-set-up-replication-tutorial-modernized.md
Low Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation generally avoids platform-specific tooling, but there is a subtle Windows bias in the order and detail of OS-specific instructions. For example, when specifying credentials for Mobility Service installation, Windows instructions (admin account) are mentioned before Linux (root credentials), and no Linux-specific example or troubleshooting is provided. There are no PowerShell or Windows-only tool references, but Linux users receive less guidance and no explicit example commands or screenshots.
Recommendations
- Provide explicit Linux walkthroughs or screenshots for steps involving Mobility Service installation, including manual installation commands and troubleshooting tips.
- List Linux instructions before or alongside Windows instructions when both are supported.
- Include links to Linux-specific documentation or FAQs for common issues (e.g., SELinux, firewall, agent permissions).
- Clarify any differences in agent deployment or permissions between Linux and Windows VMs.
Site Recovery
Automate Mobility Service for disaster recovery of installation in Azure Site Recovery
...ery/vmware-azure-mobility-install-configuration-mgr.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Summary
The documentation demonstrates a mild Windows bias: Windows examples and instructions are consistently presented before Linux equivalents, and Windows-centric tools (Configuration Manager, SMB shares, .bat scripts, DOS commands) are emphasized. The use of Windows command-line and scripting paradigms is more detailed, and screenshots are all from Windows tools. Linux instructions are present and reasonably complete, but are always secondary and lack parity in visual aids and troubleshooting guidance.
Recommendations
- Alternate the order of Windows and Linux instructions/examples, or present them side-by-side.
- Include screenshots or UI walkthroughs for Linux deployments where applicable (e.g., JetPatch on Linux).
- Provide troubleshooting and uninstall instructions for Linux, not just Windows.
- Reference Linux-native deployment tools (e.g., Ansible, Puppet) as alternatives to Configuration Manager.
- Clarify that SMB shares can be replaced with NFS or other Linux-friendly file sharing methods.
- Ensure parity in detail and guidance for both platforms, including error handling and logs.
Site Recovery
Troubleshoot failback in VMware VM disaster recovery with Azure Site Recovery
...covery/vmware-azure-troubleshoot-failback-reprotect.md
Low Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation shows mild Windows bias by describing Windows VM behavior before Linux VM behavior in IP address failback scenarios, and by providing more detailed guidance for Windows VMs (e.g., static IP restoration happens automatically for Windows, but Linux users must manually intervene). Linux-specific troubleshooting is mentioned but lacks parity in detail and automation compared to Windows. No PowerShell or Windows-only tools are referenced, but Windows is often mentioned first or with more complete solutions.
Recommendations
- Provide step-by-step instructions or scripts for restoring static IP addresses on Linux VMs after failback, similar to the automatic restoration described for Windows VMs.
- Ensure Linux troubleshooting steps are as detailed and actionable as those for Windows, including automation where possible.
- Present Linux and Windows examples side-by-side, or alternate which OS is described first to avoid implicit prioritization.
- Include references to Linux tools (e.g., nmcli, ifconfig, systemctl) where relevant, not just generic manual steps.
Site Recovery
Prepare for VMware VM disaster recovery with Azure Site Recovery
...-recovery/vmware-azure-tutorial-prepare-on-premises.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Summary
The documentation page demonstrates a mild Windows bias. Windows instructions and troubleshooting steps are presented first and in greater detail, with explicit registry edits and firewall settings. Windows-specific tools and concepts (e.g., Windows Firewall, registry edits, RDP, SAN policy) are mentioned, while Linux instructions are shorter and less detailed. Linux examples are present but generally follow Windows ones and lack parity in troubleshooting depth.
Recommendations
- Present Linux and Windows instructions in parallel, giving equal detail and prominence.
- Include Linux-specific troubleshooting steps and configuration examples (e.g., SELinux, iptables/firewalld, SSH configuration).
- Provide explicit Linux command-line examples for required actions (e.g., enabling SSH, configuring firewall rules).
- Add links to Linux documentation for advanced scenarios, similar to Windows links provided.
- Avoid presenting Windows instructions first by alternating or grouping by OS.
Site Recovery
Run VMware VMs failover to Azure
...https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/vmware-azure-tutorial-failover-failback-modernized.md
Low Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a mild Windows bias. While it mentions connecting to failed-over VMs via both RDP (Windows) and SSH (Linux), the explicit connection example links only to Windows VM instructions. There are no Linux-specific connection or validation steps, and troubleshooting is not differentiated by OS. Additionally, the order of mention and example favors Windows (RDP before SSH), and there is no guidance for Linux users on connecting to or validating Linux VMs after failover.
Recommendations
- Add explicit instructions and links for connecting to Linux VMs after failover, such as SSH connection steps and validation.
- Provide troubleshooting guidance specific to Linux VMs, especially since the documentation notes that Linux VMs may experience longer failover times.
- Ensure parity in example links: where a Windows connection guide is linked, also link to the equivalent Linux guide.
- When listing connection options, alternate or balance the order (e.g., mention SSH before RDP in some sections) to avoid subtle prioritization.
Site Recovery
Move Azure VMs to a different Azure region with Azure Site Recovery
...icles/site-recovery/azure-to-azure-tutorial-migrate.md
Low Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates mild Windows bias in the prerequisites section, where guidance for Windows VMs (installing Windows updates for root certificates) is given first and in more detail, while Linux instructions are brief and generic. No specific Linux commands, distributions, or troubleshooting steps are provided, and no Linux/macOS-specific examples or tools are mentioned throughout the tutorial.
Recommendations
- Provide explicit Linux instructions for updating root certificates, including example commands for common distributions (e.g., Ubuntu, CentOS).
- Include troubleshooting steps or references for Linux VMs, such as handling certificate issues or network configuration nuances.
- Ensure parity in detail and order between Windows and Linux guidance, presenting both equally and with actionable steps.
- Add notes or links for macOS users if relevant, especially for cross-platform administrators.
Site Recovery
Configure Mobility Service Proxy Settings for Azure to Azure Disaster Recovery | Microsoft Docs
...-recovery/configure-mobility-service-proxy-settings.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Summary
The documentation demonstrates a mild Windows bias: Windows instructions and tools (Internet Explorer, psexec) are described first and in more detail, with explicit steps for setting proxy settings for the Local System account. Linux instructions are present but less detailed, and no Linux-specific tool or example is provided for setting environment variables. The use of Windows-specific tools (Internet Explorer, psexec) is mentioned without Linux equivalents.
Recommendations
- Provide Linux-specific step-by-step instructions for setting proxy environment variables, including example commands.
- Mention Linux tools or methods for editing /etc/profile or /etc/environment, such as using nano or vi.
- Present Windows and Linux instructions in parallel sections or with equal detail.
- Avoid referencing Windows tools (like Internet Explorer and psexec) without offering Linux alternatives or equivalents.
Site Recovery
Quickstart to create an Azure Recovery Services vault using Bicep.
...rticles/site-recovery/quickstart-create-vault-bicep.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for all steps, but PowerShell (a Windows-centric tool) is given equal prominence to Azure CLI, and is presented immediately after CLI in every section. There are no Linux/macOS-specific notes or clarifications, and no mention of shell environments or platform differences. The CLI examples are cross-platform, but the inclusion of PowerShell throughout may signal a slight Windows bias.
Recommendations
- Clearly state that Azure CLI commands work on Windows, Linux, and macOS, and recommend CLI for cross-platform users.
- Add a note clarifying that PowerShell examples are primarily for Windows users, while CLI is suitable for all platforms.
- Consider listing CLI examples first in each section, and grouping PowerShell examples as 'Windows only' where appropriate.
- Mention any platform-specific prerequisites (e.g., installing Azure CLI on Linux/macOS).
Site Recovery
Set up failover and failback for physical servers with Site Recovery
...s/site-recovery/physical-to-azure-failover-failback.md
Low Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a mild Windows bias. While it mentions that both Windows and Linux operating systems are supported for replication groups, the examples, terminology, and linked resources predominantly reference Windows environments (e.g., Windows Server, Windows availability sets). There are no explicit Linux-specific instructions, examples, or references to Linux tools, and Windows terminology appears first or exclusively in several sections.
Recommendations
- Include explicit Linux examples and instructions, such as how to prepare Linux physical servers for failover and failback.
- Reference Linux-specific Azure documentation (e.g., availability sets for Linux VMs) alongside Windows links.
- Clarify any differences in process or requirements for Linux servers, such as supported distributions, required agents, or troubleshooting steps.
- Add notes or sections addressing common Linux scenarios, such as SSH connectivity after failover, or handling Linux disk UUIDs.
Site Recovery
Fail over Azure VMware Solution VMs to Azure by using Site Recovery
...b/main/articles/site-recovery/avs-tutorial-failover.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation shows a mild Windows bias: Windows concepts and links are presented before or instead of Linux equivalents. For example, the link to 'Availability set' points to a Windows-specific tutorial, and the VM connection instructions link to a Windows-centric page. While SSH is mentioned as a connection method, there are no explicit Linux/macOS examples or references, and troubleshooting/connectivity guidance is not platform-specific.
Recommendations
- Provide explicit Linux/macOS examples for connecting to failed-over VMs (e.g., SSH from Linux/macOS terminals).
- Link to platform-neutral or Linux-specific documentation for features like 'Availability set' and VM connection.
- Clarify any differences in failover or connectivity steps for Linux VMs, especially regarding drivers and network configuration.
- Ensure troubleshooting guides include Linux/macOS scenarios and tools.
Site Recovery
Prepare Azure VMware Solution for disaster recovery to Azure Site Recovery
...ain/articles/site-recovery/avs-tutorial-prepare-avs.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Summary
The documentation page shows a mild Windows bias. In sections about preparing accounts for Mobility service installation and connecting to VMs after failover, Windows instructions and tools (such as registry edits and Windows Firewall) are described in more detail and appear before Linux equivalents. Windows-specific troubleshooting and configuration steps are more explicit, while Linux instructions are brief and less detailed.
Recommendations
- Provide equally detailed Linux instructions, such as step-by-step guidance for preparing SSH access and configuring firewalls (e.g., using iptables, firewalld, or ufw).
- Include troubleshooting tips for Linux VM connectivity after failover, similar to those given for Windows (e.g., checking SSH logs, SELinux/AppArmor, etc.).
- Offer parity in example commands and configuration steps for both Windows and Linux, and alternate the order in which OS-specific instructions are presented.
- Reference Linux tools and patterns (such as systemd for service management) alongside Windows tools.
- Add links to Linux-specific documentation for advanced scenarios.
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 throughout the page. However, both platforms are covered with parity in terms of guidance, supported VM series, and links to platform-specific enablement instructions. No exclusive use of Windows tools or missing Linux examples is detected.
Recommendations
- Alternate the order of Windows and Linux sections in future updates, or present them side-by-side to avoid implicit prioritization.
- Explicitly state that both Windows and Linux are equally supported at the start of relevant sections.
- Consider a combined table for supported VM sizes and instance types to reduce duplication and reinforce parity.
Site Recovery
Set up disaster recovery after migration to Azure with Azure Site Recovery
...e-recovery/azure-to-azure-replicate-after-migration.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation page presents Windows instructions and validation steps before Linux equivalents in several sections. Windows-specific tools and patterns (e.g., Control Panel, MsiExec.exe) are described in detail, while Linux instructions are less detailed and appear after Windows steps. The overall structure and example order favor Windows users, though Linux instructions are present.
Recommendations
- Present Windows and Linux instructions in parallel or in separate, clearly labeled sections to avoid implicit prioritization.
- Provide equivalent detail and validation steps for Linux, such as specific file locations, agent version checks, and troubleshooting commands.
- Include Linux-specific troubleshooting links and resources alongside Windows ones.
- Avoid Windows-centric terminology (e.g., 'Control Panel', 'Add/Remove Programs') without Linux equivalents.
- Consider starting with a platform-neutral overview before diving into OS-specific instructions.
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
Windows Tools
Missing Linux Example
Summary
The documentation exhibits mild Windows bias. Windows-specific tools (Internet Explorer) are referenced before Linux equivalents, and proxy autodetection is described for Windows first. While Linux paths and configuration files are mentioned, examples and troubleshooting steps often reference Windows tools or patterns (such as Internet Explorer) without equal detail for Linux. No command-line examples (PowerShell, Bash) are provided, but the narrative and troubleshooting steps tend to mention Windows first or exclusively.
Recommendations
- Provide Linux/macOS-specific troubleshooting steps and examples alongside Windows instructions, especially for proxy and DNS configuration.
- Include explicit Bash/CLI commands for checking DNS and proxy settings on Linux.
- Reference Linux tools (e.g., curl, dig, resolvectl) for network diagnostics.
- Ensure that all screenshots and UI instructions are either OS-neutral or have Linux equivalents.
- When mentioning autodetection mechanisms, clarify the process for both Windows and Linux, giving equal detail.
Site Recovery
Quickstart: Use Terraform to create an Azure Recovery Services vault
...les/site-recovery/quickstart-create-vault-terraform.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for verifying results, but the PowerShell tab is present and detailed, which can be seen as Windows-centric. The Azure CLI is cross-platform, but PowerShell is traditionally associated with Windows, and its inclusion may suggest a Windows-first mindset. There are no explicit Linux/macOS examples (such as bash scripts or shell commands beyond Azure CLI), nor are there troubleshooting or environment setup instructions specific to Linux/macOS. However, the main workflow uses Terraform, which is cross-platform, and the CLI examples are sufficient for Linux/macOS users.
Recommendations
- Clarify that Azure CLI commands work on Linux/macOS and Windows equally.
- Add explicit bash/shell examples for Linux/macOS users where environment variables are set (e.g., using 'export' instead of PowerShell syntax).
- Include troubleshooting notes or links for Linux/macOS users, especially for common issues with Terraform or Azure CLI on those platforms.
- Consider reordering tabs so that Azure CLI (cross-platform) appears before PowerShell, or make CLI the default.
- Mention that PowerShell Core is available cross-platform, if relevant.
Site Recovery
Enable replication for VMware VM disaster recovery to Azure with Azure Site Recovery
...rticles/site-recovery/quickstart-enable-replication.md
Low Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation mentions both Linux and Windows OS in the context of credentials required for agent installation, but provides more detail for Windows (admin privileges) and does not offer any Linux-specific examples, troubleshooting, or patterns. There are no explicit Linux commands, screenshots, or guidance, and Windows terminology (admin privileges) is mentioned first. No PowerShell or Windows-only tools are referenced, but Linux parity is not fully addressed.
Recommendations
- Provide explicit Linux examples for credential setup, agent installation, and troubleshooting.
- Include Linux-specific screenshots or CLI commands where relevant.
- Clarify Linux requirements (e.g., supported distributions, SSH key usage, sudo/root requirements) in parity with Windows details.
- Ensure that Linux terminology is used alongside Windows terminology, not as a secondary note.
Site Recovery
Azure Site Recovery Deployment Planner Version History
...e-recovery/site-recovery-deployment-planner-history.md
Low Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation lists Windows operating systems first in most version updates and provides more granular details for Windows support (e.g., specific versions, boot types). Linux support is mentioned but less prominently, and there are no examples or details specific to Linux usage or troubleshooting. No explicit Windows-only tooling or PowerShell bias is present, but the ordering and level of detail favor Windows environments.
Recommendations
- List Linux distributions before or alongside Windows versions where supported.
- Provide equivalent detail for Linux support, including specific troubleshooting notes and compatibility clarifications.
- Include examples or notes relevant to Linux deployment scenarios, such as common issues or configuration steps.
- Add parity in known limitations and fixes for Linux environments where applicable.
Site Recovery
Manage Azure role-based access control in Azure Site Recovery
...very/site-recovery-role-based-linked-access-control.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation lists PowerShell before Azure CLI and REST API in the 'Next steps' section, which may subtly prioritize Windows tooling. However, the main content is platform-neutral, focusing on Azure roles and permissions without OS-specific instructions or examples.
Recommendations
- List Azure CLI before PowerShell in 'Next steps', as CLI is cross-platform and more commonly used on Linux/macOS.
- Explicitly state that all management operations can be performed equally via Azure CLI, PowerShell, or REST API.
- Add example commands for both Azure CLI and PowerShell in relevant sections to demonstrate parity.
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a mild Windows bias. Windows-specific technologies (e.g., Windows Server Failover Clusters, SQL Server Always On, shared disk for Windows workloads) are mentioned explicitly and in detail, while Linux equivalents are either omitted or referenced only generically. Replication scenarios and workload support mention Windows and Linux, but examples, integrations, and advanced features (such as shared disk and application consistency) are described only for Windows technologies. No Linux-specific disaster recovery patterns, tools, or examples are provided.
Recommendations
- Add explicit examples and guidance for Linux workloads, such as application-consistent replication for common Linux apps (e.g., MySQL, PostgreSQL, Apache).
- Include Linux-specific disaster recovery scenarios, such as clustering (e.g., Pacemaker, Corosync) and how Site Recovery integrates with them.
- Provide parity in advanced features (e.g., shared disk, failover orchestration) for Linux workloads, or clearly state limitations.
- Ensure that examples and feature descriptions mention Linux alongside Windows, not just as a generic 'supported' OS.
Site Recovery
Archive for What's new in Azure Site Recovery
...icles/site-recovery/site-recovery-whats-new-archive.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation generally lists both Windows and Linux support for Azure Site Recovery features and updates. However, there are instances where Windows operating systems and features are mentioned first, and some tooling references (such as PowerShell) are Windows-centric. There are also sections where Windows-specific requirements (servicing stack update/SHA-2) are detailed, while Linux equivalents are not discussed. No critical tasks appear to be Windows-only, and Linux support is consistently updated and referenced.
Recommendations
- Ensure that examples and tooling references (such as PowerShell) are paired with Linux/macOS equivalents (e.g., Azure CLI, Bash scripts) where applicable.
- When listing supported operating systems or features, alternate or randomize the order so Linux is not always listed after Windows.
- Where Windows-specific requirements (such as servicing stack update/SHA-2) are discussed, provide equivalent information for Linux distributions if relevant.
- Add explicit Linux/macOS instructions or links in sections that reference Windows tools or patterns.
- Review and update any sections that only mention Windows tools (e.g., PowerShell) to include cross-platform alternatives.
Site Recovery
What's new in Azure Site Recovery
...main/articles/site-recovery/site-recovery-whats-new.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation provides a changelog-style summary of Azure Site Recovery updates, with a focus on supported OS distros and agent versions. While Linux distributions are well-represented and frequently mentioned, there is a mild Windows bias: Windows versions and tools (e.g., Windows Server as appliance, Microsoft Edge as default browser) are called out explicitly, sometimes before Linux equivalents. There are no command-line examples, but references to Windows-specific appliances and browser defaults are present. The documentation does not provide Linux-specific tooling or examples, but also does not provide Windows command-line examples, so the bias is moderate.
Recommendations
- When mentioning appliance OS support, list Linux and Windows options together or alternate which is listed first.
- If referencing tools (e.g., browser defaults, configuration managers), clarify Linux compatibility or alternatives.
- Add explicit notes on Linux support for configuration and management tasks where Windows tools are mentioned.
- Ensure parity in examples and troubleshooting guidance for both Windows and Linux environments in linked KB articles.