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 751-775 of 864 flagged pages
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 →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation is heavily focused on Hyper-V (a Windows-centric virtualization platform) and provides detailed instructions and examples for Windows VMs, including cost estimation and licensing benefits specific to Windows (Azure Hybrid Use Benefit). While Linux VMs are mentioned as 'non-Windows' and as an OS type, there are no Linux-specific examples, patterns, or considerations. Windows is always mentioned first, and the only concrete example of licensing benefit is for Windows VMs.
Recommendations
  • Provide explicit examples and cost estimation scenarios for Linux VMs, including any differences in licensing, storage, or compute costs.
  • Clarify whether any Azure Hybrid Use Benefit or similar cost-saving features exist for Linux VMs, or explicitly state that they do not.
  • Include Linux-specific considerations for disaster recovery, such as supported distributions, any required agent installation, or differences in failover behavior.
  • Ensure that instructions and tables do not default to Windows-first language; alternate the order or provide parallel examples for both OS types.
  • If there are Linux-specific tools or patterns for cost estimation or disaster recovery, mention them alongside Windows/Hyper-V tools.
GitHub Create Pull Request
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/migrate-tutorial-on-premises-azure.md ...es/site-recovery/migrate-tutorial-on-premises-azure.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation focuses on migration options for VMware, Hyper-V, and physical servers, but does not provide any explicit examples or guidance for Linux-specific migration scenarios. The order of presentation (VMware, Hyper-V, then physical servers) and lack of mention of Linux tools or patterns suggests a Windows-first bias. There are no Linux command-line examples, nor references to Linux migration considerations, tools, or best practices.
Recommendations
  • Add explicit examples and guidance for migrating Linux servers, including common Linux distributions.
  • Include Linux-specific migration considerations, such as handling SSH keys, Linux disk formats, and OS compatibility.
  • Provide parity in documentation by including Linux command-line examples (e.g., bash scripts) alongside any PowerShell or Windows examples.
  • Mention Linux migration tools or patterns (such as rsync, tar, or cloud-init) where relevant.
  • Clarify that Azure Migrate supports both Windows and Linux workloads, and link to Linux-focused migration tutorials if available.
GitHub Create Pull Request
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 →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
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 always presented alongside CLI, and sometimes CLI is listed first. There is no explicit mention of Linux-specific patterns, nor any guidance for Linux shell environments (e.g., Bash, zsh) beyond the use of Azure CLI, which is cross-platform. The documentation does not reference Windows-only tools, but the inclusion of PowerShell throughout may suggest a slight Windows bias.
Recommendations
  • Clarify that Azure CLI commands work natively on Linux, macOS, and Windows, and provide explicit instructions for running CLI commands in Bash or other Linux shells.
  • Consider adding a note that PowerShell Core is available cross-platform, but that Azure CLI is the recommended tool for Linux users.
  • If possible, provide example command lines for Linux shell environments (e.g., Bash), especially for file paths and environment variable usage.
  • Review the ordering of examples to ensure CLI (the cross-platform tool) is presented first, or clarify that both options are equivalent.
  • Avoid implying that PowerShell is required for any step, and ensure parity in troubleshooting or advanced usage notes for Linux users.
GitHub Create Pull Request
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/quickstart-create-vault-terraform.md ...les/site-recovery/quickstart-create-vault-terraform.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell instructions for verifying results, but the PowerShell tab is given equal prominence to the CLI, which can indicate a Windows-centric approach. There are no explicit Linux shell examples (e.g., Bash), and PowerShell is a Windows-first tool, even though it is now cross-platform. The documentation does not mention Linux-specific tools or workflows, nor does it clarify cross-platform compatibility for the commands. The order of tabs (CLI first, then PowerShell) is good, but the presence of PowerShell as a primary verification method can reinforce Windows bias.
Recommendations
  • Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and provide Bash-specific examples if there are differences.
  • Clarify that PowerShell commands are cross-platform, but note that Azure CLI is often the default on Linux.
  • Consider adding a Bash-only verification tab to demonstrate parity for Linux users.
  • Where file system operations are described (e.g., creating directories), provide both Windows (PowerShell/CMD) and Linux (Bash) examples.
  • Add notes about installing Azure CLI and Terraform on Linux, not just generic installation instructions.
GitHub Create Pull Request
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/site-recovery-deployment-planner-history.md ...e-recovery/site-recovery-deployment-planner-history.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Windows Heavy
Summary
The documentation page lists Windows operating systems and features more frequently and often before Linux equivalents. Windows versions are mentioned explicitly in multiple releases, sometimes with more detail than Linux distributions. Linux support is present but less emphasized, and there are no examples or usage patterns specific to Linux environments. There is no evidence of PowerShell-specific bias or exclusive mention of Windows tools, but the overall pattern prioritizes Windows compatibility and updates.
Recommendations
  • Ensure Linux distributions are listed alongside Windows versions in all relevant release notes, with equal detail.
  • Include examples or guidance for Linux environments where applicable (e.g., running the Deployment Planner on Linux, handling Linux-specific errors).
  • Highlight Linux compatibility improvements with the same prominence as Windows updates.
  • Add troubleshooting notes or known limitations for Linux environments, not just Windows.
  • Consider a summary table showing OS support parity across Windows and Linux for each version.
GitHub Create Pull Request
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 →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation is heavily focused on Windows Server Failover Clusters (WSFC) and does not mention or provide guidance for Linux-based clustering solutions (e.g., Pacemaker, Corosync). All examples, terminology, and prerequisites are centered on Windows environments, with no Linux equivalents discussed or referenced.
Recommendations
  • Add explicit support statements for Linux-based clusters if applicable, or clarify that only Windows clusters are supported.
  • Include examples and instructions for configuring shared disk replication and failover for Linux clusters (e.g., Pacemaker/Corosync).
  • Mention Linux tools and patterns where relevant, and provide parity in prerequisites and walkthrough steps.
  • If Azure Site Recovery does not support Linux clusters with shared disks, state this limitation clearly at the beginning of the documentation.
GitHub Create Pull Request
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 →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows Reference
Summary
The documentation is focused on Linux master target server installation and configuration, but there are several references to Windows-specific tools and paths (e.g., copying installer files and passphrases from Windows servers using Windows file paths). These references assume the presence of Windows infrastructure and do not provide Linux-native alternatives for these steps. No PowerShell examples or Windows-first ordering are present, but the reliance on Windows servers for key files and configuration introduces a subtle Windows bias.
Recommendations
  • Provide Linux-native alternatives for obtaining installer files and passphrases, such as using SMB/CIFS mounts, SCP, or other cross-platform file transfer methods.
  • Document the process for environments where the process server or configuration server is running on Linux, if supported.
  • Clearly indicate if Windows-only steps are unavoidable, and suggest best practices for Linux administrators to interact with Windows servers (e.g., using Samba, WinSCP, etc.).
  • Add troubleshooting tips for Linux users who may not have direct access to Windows file paths.
  • Consider including a section on fully Linux-based deployments if supported by Azure Site Recovery.
GitHub Create Pull Request
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 →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a subtle Windows bias. While it mentions both Linux and Windows OS in the context of credentials for Mobility Service installation, it provides more explicit instructions for Windows (e.g., 'user account with admin privileges') and does not offer Linux-specific examples, commands, or troubleshooting steps. There are no Linux CLI or shell examples, nor are Linux-specific tools or patterns discussed. The documentation generally assumes a GUI/portal workflow, which is more familiar to Windows administrators, and omits parity for Linux-centric automation or command-line approaches.
Recommendations
  • Provide explicit Linux examples for manual Mobility Service installation, including shell commands and package management instructions.
  • Include Linux CLI (e.g., Bash, SSH) workflows for relevant steps, such as credential setup, agent deployment, and troubleshooting.
  • Add troubleshooting tips for common Linux issues (e.g., SELinux, firewall configuration, systemd service management) during replication setup.
  • Ensure that Linux-specific permissions and user management patterns are described alongside Windows equivalents.
  • Where possible, offer parity in screenshots or step-by-step guides for both Windows and Linux environments.
GitHub Create Pull Request
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 →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a subtle Windows bias. In the 'Connect to failed-over VM' section, Remote Desktop Protocol (RDP) is mentioned before Secure Shell (SSH), and the link provided for connecting to the VM points to Windows-specific instructions. There are no explicit Linux connection examples or references to Linux tools, despite the mention that VMware Linux VMs may require longer failover times. The documentation does not provide parity in guidance for Linux users, such as SSH connection steps or troubleshooting for Linux VMs.
Recommendations
  • Provide explicit Linux connection instructions, including SSH usage and links to Linux VM documentation.
  • Balance references to RDP and SSH, mentioning both equally and linking to both Windows and Linux VM connection guides.
  • Include troubleshooting steps and considerations specific to Linux VMs, especially since they are called out as having longer failover times.
  • Add examples or notes for Linux-specific scenarios, such as handling network configuration or disk drivers after failover.
GitHub Create Pull Request
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/azure-to-azure-quickstart.md ...in/articles/site-recovery/azure-to-azure-quickstart.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation demonstrates Windows bias by linking to Windows VM creation instructions in the prerequisites section, without mentioning or providing equivalent guidance for Linux VMs. No Linux-specific examples, screenshots, or references are present throughout the page, despite Azure supporting both Windows and Linux VMs equally.
Recommendations
  • Add links to Linux VM creation documentation alongside the Windows VM link in the prerequisites.
  • Include notes or examples clarifying that the disaster recovery process applies to both Windows and Linux VMs.
  • Provide screenshots or instructions that demonstrate the process for Linux VMs, if there are any differences.
  • Explicitly mention Linux support in relevant sections to assure parity and inclusivity.
GitHub 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 →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation focuses exclusively on Hyper-V VMs, which are a Windows technology, and does not mention or provide guidance for Linux-based disaster recovery scenarios or non-Hyper-V platforms. All examples and remediation steps are tailored to Windows environments, with no Linux parity or alternative instructions.
Recommendations
  • Include equivalent guidance for Linux-based VMs and disaster recovery scenarios, such as those using Azure Site Recovery for VMware or native Linux hosts.
  • Provide examples and remediation steps for Linux environments, including references to relevant tools and commands.
  • Clarify in the introduction that the instructions are specific to Hyper-V/Windows, and link to Linux/VMware documentation for parity.
  • Ensure future documentation covers both Windows and Linux use cases where applicable, or explicitly states the scope.
GitHub Create Pull Request
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 →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation mentions both Windows and Linux operating systems, but provides more explicit instructions and examples for Windows (e.g., specifying admin account requirements), while Linux is only briefly referenced (root credentials). There are no Linux-specific examples, screenshots, or command-line instructions, and Windows terminology (admin privileges) is presented first. No Linux tools or patterns are discussed, and there is a lack of parity in guidance for Linux users.
Recommendations
  • Provide explicit Linux examples and screenshots alongside Windows ones, such as showing how to add Linux credentials and what the process looks like for Linux servers.
  • Include Linux-specific instructions for installing the mobility service, such as relevant shell commands or package manager usage.
  • Mention Linux patterns and tools (e.g., SSH key-based authentication, sudo usage) where appropriate.
  • Ensure that instructions for both operating systems are presented with equal detail and prominence, ideally side-by-side or in clearly separated sections.
  • Clarify any differences in the replication process or requirements between Windows and Linux, so Linux administrators are fully informed.
GitHub Create Pull Request
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 →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation focuses exclusively on Windows Server Failover Clusters (WSFC) and does not mention or provide guidance for Linux-based clustering solutions (such as Pacemaker or Corosync). All examples, prerequisites, and terminology are Windows-centric, with no Linux parity in instructions, supported scenarios, or screenshots.
Recommendations
  • Explicitly state whether Linux-based clusters (e.g., Pacemaker, Corosync) are supported or not for shared disk replication in Azure Site Recovery.
  • If Linux is supported, add equivalent instructions and examples for configuring disaster recovery for Linux clusters using shared disks.
  • Include Linux-specific prerequisites, supported distributions, and any required agents or configuration steps.
  • Add screenshots and UI references relevant to Linux clusters where applicable.
  • If Linux is not supported, clarify this limitation early in the documentation to set expectations for cross-platform users.
GitHub Create Pull Request
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/site-recovery-deployment-planner-history.md ...e-recovery/site-recovery-deployment-planner-history.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Windows Heavy
Summary
The documentation page demonstrates a moderate Windows bias. Windows operating systems are consistently listed first when enumerating supported platforms, and Windows versions are mentioned in more detail and frequency than Linux equivalents. While Linux support is present and improving in recent versions, Windows examples and terminology (such as Windows Server versions and EFI/BIOS checks) are more prominent, and Linux distributions are often grouped together or mentioned after Windows. There are no explicit PowerShell examples or Windows-only tools referenced, but the pattern of listing Windows first and in greater detail is evident.
Recommendations
  • Alternate the order of OS listings to avoid always placing Windows first.
  • Provide equal detail for supported Linux distributions, including specific versions and features.
  • Where possible, include Linux-specific terminology and examples (e.g., boot types, disk formats) alongside Windows equivalents.
  • Ensure that limitations and fixes affecting Linux are described with the same granularity as those for Windows.
  • Add explicit examples or notes for Linux usage where Windows examples are given.
GitHub Create Pull Request
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 →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates subtle Windows bias by referencing Windows-centric connection methods (RDP) before Linux equivalents (SSH), and by linking only to Windows VM connection instructions. There are no Linux-specific examples, troubleshooting steps, or direct links to Linux VM documentation, despite mentioning VMware Linux VMs in performance notes. The page does not provide parity in guidance for Linux VM users.
Recommendations
  • Include explicit instructions and links for connecting to Linux VMs in Azure (e.g., SSH, Linux VM documentation).
  • Provide troubleshooting steps and validation guidance for Linux VMs after failover, similar to what is offered for Windows VMs.
  • Ensure that examples and references do not prioritize Windows tools or workflows; present Windows and Linux options side-by-side.
  • Add notes or sections addressing common Linux-specific issues (e.g., boot drivers, network configuration) with actionable guidance.
  • Review all external links to ensure Linux parity, such as linking to both Windows and Linux VM connection guides.
GitHub Create Pull Request
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
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation consistently presents instructions and screenshots using the Azure portal and references Azure PowerShell for automation, but does not provide equivalent CLI examples (such as Azure CLI) or Linux-specific guidance. There are no references to Linux tools, shell commands, or considerations for Linux environments, and all examples and UI screenshots are oriented toward Windows-centric workflows.
Recommendations
  • Add Azure CLI examples alongside or before Azure PowerShell examples for all resource creation and management steps.
  • Include notes or sections addressing Linux-specific considerations, such as command-line usage from Linux environments and any differences in DNS or networking setup.
  • Provide sample scripts or walkthroughs using bash or shell environments for common tasks (e.g., creating private endpoints, DNS zones, and role assignments).
  • Ensure that automation guidance is not limited to PowerShell and covers cross-platform tools.
  • Add screenshots or instructions for using the Azure portal from non-Windows platforms if relevant.
GitHub Create Pull Request
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/concepts-azure-to-azure-high-churn-support.md ...recovery/concepts-azure-to-azure-high-churn-support.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation mentions supported operating systems for Enhanced Churn (Windows, Linux – RHEL 9, SLES 15, Ubuntu 24.04), but Windows is listed first and there are no Linux-specific configuration examples, screenshots, or troubleshooting notes. The instructions and UI screenshots are generic and do not address any OS-specific steps or considerations, which may leave Linux users without guidance for their particular needs.
Recommendations
  • Explicitly include Linux in all supported OS lists and avoid listing Windows first unless alphabetically.
  • Add Linux-specific configuration steps or notes if any differences exist (e.g., agent installation, permissions, troubleshooting).
  • Provide screenshots or CLI examples for Linux environments (e.g., using Azure CLI or shell commands, not just portal UI).
  • Include troubleshooting tips or known issues for Linux VMs, especially for supported distributions.
  • Clarify any OS-specific limitations or requirements in the support matrix.
GitHub Create Pull Request
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/azure-to-azure-move-overview.md ...articles/site-recovery/azure-to-azure-move-overview.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation page exhibits mild Windows bias. In the 'Typical architectures for a multi-tier deployment' section, the link for 'Availability sets' points specifically to the Windows VM tutorial, rather than a general or Linux-specific equivalent. There are no explicit Linux examples, nor is there mention of Linux-specific considerations, tools, or patterns. The database tier example uses SQL Server Always On, a Windows-centric technology, without mentioning Linux alternatives. No PowerShell examples are present, but the overall framing and references favor Windows environments.
Recommendations
  • Include links to both Windows and Linux VM documentation when referencing features like availability sets.
  • Mention Linux VM support explicitly in architecture and migration scenarios.
  • Provide examples or notes for Linux-specific considerations (e.g., OS-level replication, database technologies like MySQL/PostgreSQL).
  • Balance technology examples (e.g., include a Linux-based database tier alongside SQL Server).
  • Clarify that Azure Site Recovery and Resource Mover support both Windows and Linux VMs, and highlight any differences in process or prerequisites.
GitHub Create Pull Request
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/azure-to-azure-tutorial-migrate.md ...icles/site-recovery/azure-to-azure-tutorial-migrate.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates Windows bias by providing explicit instructions for updating root certificates and system updates for Windows VMs, while only referencing generic Linux distributor guidance for Linux VMs. The Windows instructions are more detailed and appear first, whereas Linux guidance is minimal and lacks concrete examples or links. No Linux-specific commands, tools, or step-by-step instructions are provided throughout the page.
Recommendations
  • Provide detailed, step-by-step instructions for updating root certificates and system packages on popular Linux distributions (e.g., Ubuntu, CentOS, RHEL), including example commands.
  • Include links to official documentation for Linux certificate management and update processes.
  • Present Windows and Linux instructions in parallel, ensuring equal detail and prominence for both platforms.
  • Add troubleshooting steps or common issues for Linux VMs during migration, similar to what is described for Windows.
  • Reference Linux-specific Azure documentation where applicable.
GitHub Create Pull Request
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/migrate-tutorial-on-premises-azure.md ...es/site-recovery/migrate-tutorial-on-premises-azure.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation focuses on migration scenarios for VMware VMs, Hyper-V VMs, and physical servers, but does not provide explicit examples or guidance for Linux-specific migration patterns, tools, or considerations. Hyper-V (a Windows-centric hypervisor) is mentioned alongside VMware, and there is no mention of Linux-native hypervisors (e.g., KVM) or Linux-specific migration steps. The absence of Linux command-line examples or references to Linux migration tooling suggests a Windows-first bias.
Recommendations
  • Add explicit examples and guidance for migrating Linux-based machines, including common Linux distributions.
  • Include references to Linux-native hypervisors (e.g., KVM, Xen) and how to migrate VMs from these platforms.
  • Provide Linux command-line examples for agent installation, migration initiation, and troubleshooting.
  • Mention Linux-specific considerations, such as handling of SSH keys, file system compatibility, and post-migration configuration.
  • Ensure parity in documentation structure by presenting Linux migration scenarios alongside Windows/Hyper-V examples.
GitHub Create Pull Request
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/move-from-classic-to-modernized-vmware-disaster-recovery.md ...ve-from-classic-to-modernized-vmware-disaster-recovery.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation mentions both Linux and Windows support matrices, but Windows is listed before Linux in the prerequisites. There are no concrete examples, commands, or instructions specific to Linux environments, such as shell commands or Linux-specific tooling. The page does not provide parity in examples or guidance for Linux users, focusing on generic infrastructure steps that may implicitly favor Windows-centric environments.
Recommendations
  • Provide explicit Linux-based examples and instructions, such as shell commands for agent installation or troubleshooting.
  • List Linux and Windows support information with equal prominence, or alternate their order to avoid implicit prioritization.
  • Include references to Linux-specific tools, logs, or troubleshooting steps where relevant.
  • Ensure that any screenshots, walkthroughs, or step-by-step guides include both Linux and Windows scenarios.
GitHub Create Pull Request
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 →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation is focused on disaster recovery planning for Hyper-V VMs, which are inherently Windows-based. Throughout the page, examples, terminology, and scenarios are centered on Windows environments, with only brief mentions of Linux (e.g., in VM OS type selection). There are no Linux-specific examples, patterns, or guidance, and Windows is always referenced first. No Linux tools or parity considerations are discussed.
Recommendations
  • Include explicit examples and guidance for Linux VMs, such as cost estimation for common Linux workloads (e.g., Apache, MySQL).
  • Clarify whether the Deployment Planner supports Linux VMs and any limitations or differences in cost estimation for Linux versus Windows.
  • Provide parity in documentation sections, ensuring Linux is mentioned alongside Windows in all relevant scenarios (e.g., Hybrid Use Benefit applicability, DR drills).
  • Add a section or FAQ addressing Linux-specific disaster recovery considerations, such as licensing, support, and best practices.
  • If the tool is Windows-only, state this clearly and provide alternative recommendations for Linux environments.
GitHub Create Pull Request
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 →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for all operations (deployment, review, cleanup), but consistently lists PowerShell as an equal alternative to CLI, rather than as a secondary option. There is a subtle Windows bias in that PowerShell is presented alongside CLI in every section, even though PowerShell is primarily a Windows tool and less commonly used on Linux. No Linux-specific shell examples (e.g., Bash scripts) or platform notes are given, and PowerShell is not explicitly marked as Windows-only.
Recommendations
  • Clarify that Azure PowerShell is primarily for Windows and note cross-platform availability if relevant.
  • Explicitly mention that Azure CLI commands work natively on Linux, macOS, and Windows.
  • Consider listing Azure CLI examples first, as CLI is the default cross-platform tool.
  • Add a note or section for Linux/macOS users, confirming that all CLI commands work on those platforms.
  • Remove or de-emphasize PowerShell examples unless there is a specific Windows audience, or provide Bash equivalents if scripting is discussed.
  • If PowerShell is included, add installation/use instructions for Linux/macOS if cross-platform support is intended.
GitHub Create Pull Request
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 →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing Windows-specific features (such as availability sets), mentioning Windows before Linux in multi-VM consistency instructions, and omitting explicit Linux-specific examples or guidance. There are no Linux command-line examples, nor are Linux-specific networking or failover considerations discussed. The documentation assumes familiarity with Windows-centric concepts and tools, and does not provide parity for Linux administrators.
Recommendations
  • Include explicit Linux examples and instructions, such as how to connect to failed-over Linux VMs, and any Linux-specific configuration steps.
  • Mention Linux equivalently alongside Windows when discussing multi-VM consistency, not after Windows.
  • Provide guidance for Linux administrators on post-failover configuration, such as SSH access, cloud-init, and network settings.
  • Reference Linux documentation and troubleshooting resources where appropriate.
  • Clarify any differences in failover/failback behavior or requirements for Linux servers.
GitHub Create Pull Request
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/site-recovery-role-based-linked-access-control.md ...very/site-recovery-role-based-linked-access-control.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page demonstrates mild Windows bias by listing PowerShell as the first method for managing access, ahead of Azure CLI and REST API. This ordering may suggest a preference for Windows-centric tools. However, the page does mention Azure CLI and REST API, which are cross-platform, and does not provide command-line examples that are exclusive to Windows or PowerShell. There are no explicit Windows-only tools or patterns, nor are Linux examples missing entirely, but the prioritization of PowerShell may subtly reinforce Windows as the default environment.
Recommendations
  • List Azure CLI before PowerShell when presenting management options, as CLI is cross-platform and more commonly used on Linux.
  • Explicitly mention that both PowerShell and Azure CLI are available on Windows, Linux, and macOS.
  • Provide example commands for both PowerShell and Azure CLI in relevant sections, ensuring parity.
  • Include a note or section highlighting Linux usage scenarios or considerations for Azure Site Recovery and RBAC.
GitHub Create Pull Request
← Previous Page 31 of 35 Next →