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 851-864 of 864 flagged pages
Site Recovery
Analyze the Deployment Planner report for VMware disaster recovery with Azure Site Recovery
...site-recovery-vmware-deployment-planner-analyze-report.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page exhibits mild Windows bias. While the main content is platform-neutral and focused on VMware and Azure, there are several instances where Windows-specific features, tools, or support are mentioned before Linux equivalents. For example, EFI boot support is described only for Windows Server versions, and there is no mention of Linux EFI support. Additionally, there are no explicit Linux-specific examples, troubleshooting steps, or tool usage instructions, and Windows terminology (such as 'Process Server', 'configuration server', and 'ExpressRoute') is used without clarifying cross-platform applicability.
Recommendations
- Add explicit examples and guidance for Linux virtual machines, especially regarding EFI boot support and failover/failback scenarios.
- Clarify whether tools and recommendations (e.g., configuration server, process server, ExpressRoute) apply equally to Linux environments, and provide Linux-specific instructions where necessary.
- Include troubleshooting steps and recommendations for Linux users, such as supported distributions, required agent versions, and known limitations.
- Ensure parity in documentation by mentioning Linux support/features alongside Windows, rather than focusing on Windows first.
Create Pull Request
Site Recovery
Exclude VMware VM disks from disaster recovery to Azure with Azure Site Recovery
...in/articles/site-recovery/vmware-azure-exclude-disk.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation page shows mild Windows bias by mentioning Windows failback behavior before Linux, and by referencing 'Windows disks' and Windows-specific failback scenarios. Linux is discussed separately and after Windows, with less detail. No Linux-specific tools or examples are provided, and the failback section is Windows-centric.
Recommendations
- Present Windows and Linux failback behaviors in parallel, rather than Windows first.
- Provide Linux-specific examples or clarify Linux disk handling in more detail.
- Include any Linux-specific considerations or tooling if applicable.
- Ensure that instructions and terminology are equally clear for both Windows and Linux users.
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
Windows Tools
Summary
The documentation page exhibits mild Windows bias. Windows-specific scenarios (e.g., Windows Server 2008 R2 SP1 failback limitations) are mentioned explicitly, while Linux troubleshooting steps are less detailed. Windows VM behavior is described as more seamless (e.g., static IP restoration), whereas Linux users are told to manually intervene. No Linux command-line examples or Linux-specific troubleshooting tools are provided, and generic troubleshooting steps (e.g., using Telnet, ping) are presented without platform-specific guidance. Windows tools and behaviors are referenced more often, and Windows scenarios are sometimes described before Linux equivalents.
Recommendations
- Provide Linux-specific troubleshooting commands and examples (e.g., how to check service status, network connectivity, etc. on Linux VMs).
- Include parity in IP address restoration steps for Linux VMs, possibly with example commands for setting static IPs.
- List Linux scenarios and solutions alongside Windows ones, rather than after or with less detail.
- Mention Linux equivalents for any Windows tools referenced (e.g., alternatives to Telnet, service management commands).
- Ensure troubleshooting steps are platform-neutral or provide parallel guidance for both Windows and Linux users.
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 shows a mild Windows bias: when discussing how to connect to failed-over VMs, it mentions RDP (Windows) and SSH (Linux/macOS), but the link provided for connection instructions points only to Windows VM connection documentation. There are no explicit Linux/macOS connection examples or troubleshooting steps, and Windows-centric connection patterns are mentioned first.
Recommendations
- Provide direct links and examples for connecting to Linux VMs in Azure using SSH, alongside the Windows RDP instructions.
- Ensure troubleshooting guides cover both RDP and SSH connectivity issues, with platform-specific advice.
- When listing connection methods, alternate the order or explicitly mention both Windows and Linux/macOS use cases.
- Include references to Azure documentation for Linux VM management and connectivity.
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, both in section order and in the details. Windows links and references (e.g., Powershell) are mentioned first, and the Windows section precedes Linux throughout. However, Linux examples and links are present, and there is no exclusive use of Windows tools or missing Linux content.
Recommendations
- Alternate the order of Windows and Linux sections, or combine them where possible to avoid implicit prioritization.
- Present both Windows and Linux links/examples side-by-side when describing how to enable Accelerated Networking.
- Explicitly state that both Windows and Linux are equally supported at the start of relevant sections.
- Ensure parity in detail and clarity between Windows and Linux instructions and supported OS lists.
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
Missing Linux Example
Summary
The documentation provides a general workflow for enabling replication of VMware VMs to Azure using Azure Site Recovery, but lacks parity in examples and instructions for Linux systems. The only mention of Linux is a brief note about providing root credentials, whereas Windows is referenced with more detail regarding admin privileges. There are no Linux-specific commands, screenshots, or troubleshooting steps, and no mention of Linux tools or patterns.
Recommendations
- Include explicit Linux examples, such as screenshots of Linux VM selection and credential entry.
- Provide guidance on installing the Mobility Service manually on Linux, including relevant commands and prerequisites.
- Add troubleshooting steps or common issues specific to Linux VMs.
- Clarify any differences in replication behavior or requirements between Linux and Windows VMs.
- Ensure that instructions for credential management and agent installation are equally detailed for both operating systems.
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, indicating a 'windows_first' bias. However, both Windows and Linux are covered with parity in examples, links, and details. No PowerShell-heavy, Windows-only tools, or missing Linux examples are present.
Recommendations
- Alternate the order of Windows and Linux sections in future documentation, or present them in parallel to avoid implicit prioritization.
- Add a summary table at the top listing both Windows and Linux supported OSes and links to respective enablement guides for quick parity reference.
- Explicitly state that all instructions and features apply equally to both Windows and Linux unless noted, to reinforce cross-platform support.
Site Recovery
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/azure-vm-disaster-recovery-with-accelerated-networking.md
...azure-vm-disaster-recovery-with-accelerated-networking.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation presents Windows VM guidance before Linux VM guidance in both structure and links, listing Windows operating systems and VM sizes first. However, Linux parity is generally maintained, with equivalent sections and links for both platforms. No exclusive use of Windows tools (e.g., PowerShell) is present in the main instructions, and Linux examples are provided via CLI links. There is no evidence of missing Linux examples or Windows-only tooling in the core content.
Recommendations
- Alternate the order of Windows and Linux sections in future documentation, or combine them where possible to avoid implicit prioritization.
- Explicitly state that both Windows and Linux are equally supported at the beginning of the document.
- Ensure that example links for enabling Accelerated Networking are presented together or in parallel, rather than Windows first.
- Consider adding a summary table comparing supported OSes and VM sizes for both platforms to reinforce parity.
Site Recovery
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/quickstart-enable-replication.md
...rticles/site-recovery/quickstart-enable-replication.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation provides general instructions for enabling replication of VMware VMs to Azure using Azure Site Recovery, with a brief mention of credential requirements for Linux and Windows OS. However, there are no explicit examples, commands, or screenshots tailored for Linux environments, and no Linux-specific tools or patterns are discussed. The instructions and screenshots are platform-neutral, but lack Linux parity in terms of step-by-step guidance or troubleshooting.
Recommendations
- Add explicit Linux-focused examples, such as CLI commands for Linux environments or screenshots showing Linux VM configuration.
- Include troubleshooting steps or common issues specific to Linux VMs (e.g., SELinux, firewall settings, agent installation problems).
- Provide parity in credential guidance, such as best practices for securing root credentials and alternative authentication methods for Linux.
- Mention any Linux-specific prerequisites or considerations (e.g., supported distributions, required packages for Mobility Service).
Site Recovery
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/azure-vm-disaster-recovery-with-accelerated-networking.md
...azure-vm-disaster-recovery-with-accelerated-networking.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation presents Windows VM information before Linux VM information in both the structure and external links. Windows operating systems and VM sizes are listed first, and the link to enabling Accelerated Networking for Windows VMs precedes the Linux equivalent. However, both platforms are covered with similar detail, and Linux examples and links are present.
Recommendations
- Alternate the order of Windows and Linux sections or present them in parallel to avoid implicit prioritization.
- Explicitly state that instructions apply equally to both Windows and Linux VMs where possible.
- Ensure that external links for enabling Accelerated Networking are presented together or in a neutral order.
- Consider adding a summary table or section that covers both Windows and Linux prerequisites and steps side-by-side.
Site Recovery
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/quickstart-enable-replication.md
...rticles/site-recovery/quickstart-enable-replication.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation provides general instructions for enabling replication of VMware VMs to Azure using Azure Site Recovery, but it lacks parity in examples and guidance for Linux systems. While it briefly mentions that root credentials are needed for Linux OS and admin privileges for Windows OS, there are no Linux-specific examples, screenshots, or troubleshooting steps. The documentation does not show bias towards Windows tools or PowerShell, nor does it prioritize Windows over Linux in ordering, but it does not provide Linux-centric guidance beyond a single credential note.
Recommendations
- Add explicit Linux VM examples, including screenshots of the process for Linux VMs.
- Include troubleshooting steps or common issues specific to Linux VMs (e.g., agent installation, permissions).
- Provide guidance on preparing Linux VMs for replication, such as required packages or configuration.
- Clarify any differences in the replication process or agent behavior between Linux and Windows VMs.
- Ensure parity in documentation depth for both Linux and Windows, including post-replication steps and failover testing.
Site Recovery
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/azure-to-azure-how-to-enable-replication-private-endpoints.md
...e-to-azure-how-to-enable-replication-private-endpoints.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation page provides step-by-step instructions for enabling replication for private endpoints in Azure Site Recovery, but all operational guidance is given exclusively through the Azure Portal UI and Azure PowerShell references. There are no CLI (az CLI) or Linux-native command examples, nor is there mention of Linux-specific considerations or tooling. This may disadvantage users who prefer or require Linux-based automation or command-line workflows.
Recommendations
- Add equivalent Azure CLI (az CLI) commands for all major steps, such as creating private endpoints, configuring managed identities, and managing DNS zones and records. The Azure CLI is cross-platform and commonly used on Linux.
- Where PowerShell is referenced, provide parallel az CLI examples, or at least mention that the same actions can be performed via CLI with a link to relevant documentation.
- Explicitly state that all steps can be performed from Linux environments using the Azure CLI, and provide links to relevant Linux/CLI documentation.
- Include a section or note on Linux compatibility, especially for automation scenarios, and clarify any differences or caveats for Linux users.
- If screenshots are only from the Azure Portal, consider adding CLI output examples or terminal screenshots to support Linux users.
Site Recovery
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/disaster-recovery-for-edge-zone-via-vm-flow-tutorial.md
...tps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/disaster-recovery-for-edge-zone-via-vm-flow-tutorial.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation provides a step-by-step tutorial for setting up disaster recovery using the Azure portal UI, but does not include any command-line examples or references for either Windows (PowerShell/Command Prompt) or Linux (Bash/CLI). However, it implicitly assumes a GUI workflow, which is more familiar to Windows users, and does not mention or provide parity for Linux-centric workflows (such as using the Azure CLI in Bash). There is no explicit Windows bias in terms of tools or examples, but the lack of Linux command-line guidance represents a gap.
Recommendations
- Add Azure CLI (az) command-line examples for enabling VM replication, suitable for both Linux and Windows users.
- Include references or links to documentation on how to perform the same disaster recovery setup using Bash or other Linux shells.
- Clarify that the process can be completed via both the Azure portal and command-line tools, and provide parity in instructions.
- If PowerShell examples are added in the future, ensure equivalent Bash/Azure CLI examples are also provided.
Site Recovery
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/azure-vm-disaster-recovery-with-accelerated-networking.md
...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 in all relevant sections. While Linux content is present and reasonably complete, the ordering consistently prioritizes Windows, which may subtly reinforce a Windows-centric perspective.
Recommendations
- Alternate the order of Windows and Linux sections in different articles, or present them in parallel (side-by-side tabs or tables) to avoid implicit prioritization.
- Explicitly state that both Windows and Linux are equally supported at the start of the document.
- Ensure that any referenced links (such as how to enable Accelerated Networking) are equally prominent for both Windows (PowerShell) and Linux (CLI), possibly by grouping them together.
- If possible, provide a unified section for steps that are identical across platforms, only splitting out platform-specific details as needed.