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 701-725 of 864 flagged pages
Site Recovery Move Azure VMs to a different Azure region with Azure Site Recovery ...icles/site-recovery/azure-to-azure-tutorial-migrate.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
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 OS updates for Windows VMs, while only referencing generic distributor guidance for Linux VMs. No Linux-specific commands, tools, or examples are provided, and Windows is mentioned first in the prerequisites section.
Recommendations
  • Provide explicit Linux update instructions, including common commands for popular distributions (e.g., Ubuntu, CentOS).
  • Include Linux-specific examples or references for certificate management and OS updates.
  • Ensure parity by listing Linux instructions before or alongside Windows instructions, not after.
  • Add troubleshooting steps or links for common Linux migration issues (e.g., SELinux, firewall, networking differences).
  • Reference Linux documentation for Azure VM migration where applicable.
GitHub Create Pull Request
Site Recovery Azure Virtual Machines disaster recovery - High Churn support ...recovery/concepts-azure-to-azure-high-churn-support.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page lists supported operating systems for Enhanced Churn (500 MB/s) as 'Windows. Linux – RHEL 9, SLES 15, Ubuntu 24.04', placing Windows first and Linux after, with specific Linux distros. Throughout the page, there are no OS-specific examples, commands, or instructions, but the only explicit OS mention is in the support matrix, and Windows is listed before Linux. There are no PowerShell-heavy sections, Windows-only tools, or examples, but Linux parity is limited to a brief mention of supported distros, with no further guidance or examples for Linux users.
Recommendations
  • List supported Linux distributions before or alongside Windows, or use alphabetical order to avoid perceived prioritization.
  • Provide explicit instructions, examples, or screenshots for both Windows and Linux VMs where relevant, especially for enabling High Churn support.
  • Clarify any differences in configuration or limitations for Linux VMs, including supported versions and troubleshooting steps.
  • If there are command-line or portal steps that differ for Linux, include those in the documentation.
  • Ensure parity in troubleshooting and operational guidance for both Windows and Linux environments.
GitHub Create Pull Request
Site Recovery Deprecation of Azure Site Recovery data encryption feature ...ticles/site-recovery/encryption-feature-deprecation.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation is focused exclusively on Hyper-V VMs, a Windows-centric virtualization platform, and does not mention Linux-based scenarios or provide examples for Linux environments. All remediation steps and references are tailored to Windows/Hyper-V users, with no guidance for customers using Linux VMs or other platforms.
Recommendations
  • Include equivalent guidance for Linux VM disaster recovery scenarios, such as steps for Azure Site Recovery with Linux-based hypervisors (e.g., KVM, VMware).
  • Provide examples and references for enabling encryption at rest for Linux VMs replicated to Azure.
  • Clarify whether the deprecation affects only Hyper-V or also Linux VM replication, and link to relevant documentation for Linux users.
  • Ensure future documentation covers both Windows and Linux environments, presenting them with parity and clear distinctions where necessary.
GitHub Create Pull Request
Site Recovery Review the Azure Site Recovery Deployment Planner cost estimation report for disaster recovery of Hyper-V VMs to Azure| Microsoft Docs ...recovery/hyper-v-deployment-planner-cost-estimation.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
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 technology) and provides detailed cost estimation guidance for disaster recovery of Windows VMs to Azure. While Linux VMs are mentioned in passing (e.g., in the VM type table and OS Type field), there are no Linux-specific examples, scenarios, or guidance. All examples, terminology, and default settings assume a Windows-centric environment, and Windows features (such as Azure Hybrid Use Benefit) are described in detail, whereas Linux equivalents are not discussed.
Recommendations
  • Add explicit Linux VM disaster recovery scenarios and examples, including cost estimation for common Linux workloads.
  • Provide guidance on Linux-specific considerations, such as licensing, support, and compatibility with Azure Site Recovery.
  • Clarify any differences in cost estimation or DR process for Linux VMs compared to Windows VMs.
  • Include references to Linux tools or patterns where relevant, and ensure parity in documentation structure and detail.
  • Consider renaming sections or adding notes to clarify applicability to both Windows and Linux VMs, not just Hyper-V/Windows environments.
GitHub Create Pull Request
Site Recovery Migrate on-premises machines to Azure with Azure Migrate ...es/site-recovery/migrate-tutorial-on-premises-azure.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation focuses on migration of VMware, Hyper-V, and physical servers, but does not provide explicit examples or guidance for Linux-specific scenarios. The listed migration paths and walkthroughs reference technologies commonly associated with Windows environments (Hyper-V, Site Recovery), and there are no Linux command-line or tool examples, nor is there mention of Linux-specific migration considerations.
Recommendations
  • Add explicit examples and guidance for migrating Linux servers, including common Linux distributions.
  • Include Linux-specific migration steps, such as preparing Linux machines for Azure Migrate, handling SSH keys, and post-migration validation.
  • Provide parity in troubleshooting and FAQ sections for Linux users.
  • Reference Linux-native tools and commands where appropriate, and clarify any differences in agent installation or migration process for Linux systems.
GitHub Create Pull Request
Site Recovery Move from classic to modernized VMware disaster recovery ...ve-from-classic-to-modernized-vmware-disaster-recovery.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
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 in a single bullet point, but Windows is listed before Linux. There are no examples, instructions, or troubleshooting steps specific to Linux systems, nor are Linux tools or commands referenced. The page does not provide parity in examples or guidance for Linux users, focusing on generic or Windows-centric infrastructure and requirements.
Recommendations
  • Provide explicit Linux-specific setup and troubleshooting instructions, including references to relevant Linux commands and tools.
  • Include examples for both Windows and Linux environments when discussing agent installation, supported versions, and migration steps.
  • List Linux before or alongside Windows when mentioning supported operating systems to avoid implicit prioritization.
  • Add links to Linux-focused documentation or FAQs where appropriate.
  • Clarify any differences in process or requirements for Linux-based machines in migration scenarios.
GitHub Create Pull Request
Site Recovery Quickstart to create an Azure Recovery Services vault using Bicep. ...rticles/site-recovery/quickstart-create-vault-bicep.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
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 is given equal prominence to CLI, despite CLI being cross-platform and PowerShell being primarily associated with Windows. There is no mention of Linux-specific patterns, nor is there any guidance for Linux users regarding shell environments or prerequisites. The documentation does not explicitly favor Windows tools, but the inclusion of PowerShell throughout and its parity with CLI may subtly reinforce Windows-centric workflows.
Recommendations
  • Clearly indicate that Azure CLI is cross-platform and preferred for Linux/macOS users, while PowerShell is primarily for Windows.
  • Add a note or section for Linux/macOS users, confirming that all CLI commands work natively in Bash/Zsh/etc.
  • Consider listing CLI examples before PowerShell examples to reinforce platform neutrality.
  • If PowerShell is included, clarify its availability on Linux/macOS, or link to installation instructions for non-Windows platforms.
  • Avoid using Windows-specific terminology (e.g., 'local computer') and instead use 'local machine' or specify OS-neutral language.
GitHub Create Pull Request
Site Recovery Enable replication for a physical server – Modernized ...es/site-recovery/physical-server-enable-replication.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation provides instructions for enabling replication for physical servers to Azure, but exhibits subtle Windows bias. While both Windows and Linux are mentioned in credential requirements, Windows is listed first and receives more explicit guidance (e.g., 'add a user account with admin privileges'), whereas Linux is only briefly referenced ('provide the root credentials'). No Linux-specific examples, screenshots, or troubleshooting steps are provided, and all UI references and images are generic, lacking parity for Linux-specific scenarios. There are no PowerShell-heavy or Windows tool references, but the overall pattern favors Windows in order and detail.
Recommendations
  • Provide Linux-specific examples and screenshots, such as adding Linux credentials, installing the mobility agent on Linux, and troubleshooting common Linux issues.
  • Ensure equal detail for both Windows and Linux in instructions, including explicit steps for Linux user account requirements and permissions.
  • Where credential requirements are mentioned, alternate the order or present both OSes with equal prominence.
  • Add notes or links to Linux-specific documentation for manual installation, agent configuration, and best practices.
  • Include troubleshooting tips for common Linux replication issues, such as SELinux, firewall, or SSH configuration.
GitHub Create Pull Request
Site Recovery Quickstart: Use Terraform to create an Azure Recovery Services vault ...les/site-recovery/quickstart-create-vault-terraform.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
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 PowerShell is given equal prominence and detail as Azure CLI. There is no explicit Linux shell example (e.g., bash), and PowerShell, which is traditionally associated with Windows, is featured as a primary verification method. The order of tabs places Azure CLI before PowerShell, but the presence of PowerShell examples and lack of explicit Linux-specific instructions or troubleshooting can be interpreted as a mild Windows bias.
Recommendations
  • Add explicit bash or Linux shell examples for verification steps, especially for users on Linux or macOS.
  • Clarify that Azure CLI commands work cross-platform and provide any necessary Linux-specific notes (e.g., environment variable syntax differences).
  • Include troubleshooting steps or notes relevant to Linux environments.
  • Consider adding a note about PowerShell Core availability on Linux, if PowerShell examples are retained.
  • Ensure parity in instructions for both Windows and Linux users throughout the quickstart, especially in sections involving command-line operations.
GitHub Create Pull Request
Site Recovery Azure Site Recovery Deployment Planner Version History ...e-recovery/site-recovery-deployment-planner-history.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Windows Heavy
Summary
The documentation consistently lists Windows operating systems before Linux equivalents when describing new support in each version. Windows versions are mentioned in detail and often individually, while Linux distributions are grouped or listed after Windows. There are no examples, usage instructions, or tool references that are specific to Linux, and the overall pattern prioritizes Windows environments in both fixes and feature descriptions.
Recommendations
  • List supported Linux distributions before or alongside Windows versions to avoid implicit prioritization.
  • Provide equal detail for Linux support (e.g., specify minor versions, features, and limitations for each distro as is done for Windows).
  • Include usage notes, examples, or troubleshooting steps specific to Linux environments where relevant.
  • Explicitly mention Linux compatibility in feature descriptions, not just as an afterthought.
  • Add a summary table showing parity between Windows and Linux support for each version.
GitHub Create Pull Request
Site Recovery What's new in Azure Site Recovery ...main/articles/site-recovery/site-recovery-whats-new.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation page provides a changelog for Azure Site Recovery, listing supported OS versions and features added in each update. While Linux distributions are well-represented and often listed in detail, there is evidence of Windows bias: Windows versions are sometimes mentioned before Linux equivalents (e.g., 'Windows 2025' listed before Linux distros in May 2025), and Windows-specific tools (e.g., 'Site Recovery Provider', 'Recovery Services agent', 'Windows Server 2019 as replication appliance') are referenced without Linux equivalents or alternatives. There are no Linux-specific tooling examples or parity notes for agent installation or management, and no Linux command-line or automation examples are provided.
Recommendations
  • When listing supported OS versions, alternate or randomize the order so Linux distributions are not always listed after Windows.
  • Provide explicit mention of Linux equivalents for Windows-specific tools (e.g., clarify if 'Site Recovery Provider' or 'Recovery Services agent' have Linux versions or alternatives).
  • Add Linux-specific examples, such as agent installation or update commands (e.g., using shell scripts or package managers), alongside any Windows instructions.
  • Include parity notes or tables showing which features/tools are available for both Windows and Linux, and highlight any differences.
  • Reference Linux troubleshooting or diagnostics tools if available, or clarify if the diagnostics collection tool supports Linux environments.
GitHub Create Pull Request
Site Recovery Troubleshoot failback in VMware VM disaster recovery with Azure Site Recovery ...covery/vmware-azure-troubleshoot-failback-reprotect.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation demonstrates a Windows bias by providing more complete troubleshooting guidance for Windows VMs, such as automatic restoration of static IP addresses, while Linux VM issues require manual intervention. Windows-specific scenarios (e.g., Windows Server 2008 R2 SP1 failback limitations) are mentioned, but Linux equivalents are not discussed. There are no Linux-specific troubleshooting commands or examples, and generic troubleshooting steps (e.g., using Telnet/ping) do not mention Linux alternatives or commands.
Recommendations
  • Provide Linux-specific troubleshooting commands and examples (e.g., using 'nc' or 'ss' instead of Telnet/ping).
  • Include parity in guidance for restoring static IP addresses on Linux VMs, such as example commands or scripts.
  • Discuss Linux-specific failback limitations or scenarios, similar to the Windows Server 2008 R2 SP1 example.
  • Ensure that troubleshooting steps and error resolutions offer both Windows and Linux approaches where applicable.
GitHub Create Pull Request
Site Recovery Install a master target server for Linux VM failback with Azure Site Recovery ...e-recovery/vmware-azure-install-linux-master-target.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation is focused on Linux master target installation, but there is evidence of Windows bias. Windows tools and paths (e.g., C:\Program Files, C:\ProgramData) are referenced as sources for required files (installer, passphrase), and instructions assume access to a Windows-based process/configuration server. The mention of Windows master target for Windows VMs appears before Linux instructions, and no Linux-only alternatives for these steps are provided.
Recommendations
  • Provide Linux-native alternatives for accessing required files (installer, passphrase) from the process/configuration server, such as using SMB/NFS shares, SCP, or other cross-platform methods.
  • Document the process for retrieving necessary files from a Linux-based process/configuration server, if supported.
  • Ensure parity in example ordering: present Linux instructions first when the page is Linux-focused, and avoid referencing Windows tools/paths unless strictly necessary.
  • Clarify whether the process/configuration server must be Windows, or if Linux is supported, and provide guidance for both scenarios.
  • Where Windows paths are referenced, offer equivalent Linux paths or methods if available.
GitHub Create Pull Request
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
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation mentions both Windows and Linux OS support for Mobility Service agent installation, but provides more detail for Windows (admin privileges) and only briefly notes Linux (root credentials). There are no Linux-specific examples, commands, or troubleshooting steps. The documentation does not mention any Linux tools or provide parity in example depth, and the general pattern is to mention Windows first or in more detail.
Recommendations
  • Provide explicit Linux examples for Mobility Service agent installation, including command-line instructions (e.g., using SSH, shell scripts, or package managers).
  • Include troubleshooting steps or common issues for Linux environments, such as SELinux, firewall configuration, or systemd service management.
  • List Linux prerequisites and permissions in equal detail as Windows, including supported distributions and required packages.
  • Ensure that screenshots and UI instructions clarify any differences for Linux VMs (e.g., credential prompts, agent status).
  • Add a section or callout for Linux-specific best practices in disaster recovery scenarios.
GitHub Create Pull Request
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
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias primarily by referencing Windows-centric connection methods (RDP) before Linux equivalents (SSH), and by linking only to Windows VM connection instructions. There are no explicit Linux-specific examples, troubleshooting steps, or references to Linux tools or patterns, despite mentioning VMware Linux VMs in passing. The documentation does not provide parity in guidance for Linux VM users.
Recommendations
  • Include explicit Linux VM connection instructions and link to the official Azure Linux VM SSH documentation alongside the Windows RDP link.
  • Provide troubleshooting steps and tips specific to Linux VMs, especially for common issues encountered during failover (e.g., network configuration, boot drivers, SSH access).
  • Add examples or screenshots that show the process for both Windows and Linux VMs to ensure equal representation.
  • Mention Linux-specific requirements or considerations (e.g., cloud-init, supported distributions, firewall settings) where relevant.
  • Ensure that any references to tools, commands, or validation steps are provided for both Windows and Linux environments.
GitHub Create Pull Request
Site Recovery Moving Azure VMs to another region with Azure Site Recovery ...articles/site-recovery/azure-to-azure-move-overview.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
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 generic or Linux equivalent. The example database tier uses SQL Server Always On, a Windows-centric technology, without mentioning Linux alternatives. No explicit Linux examples, tools, or patterns are provided, and Windows terminology appears first or exclusively in some cases.
Recommendations
  • Provide equivalent links and examples for Linux VMs, such as linking to Linux VM availability set documentation.
  • Mention Linux-supported database high availability options (e.g., MySQL/MariaDB/PostgreSQL replication) alongside SQL Server Always On.
  • Ensure terminology and examples are platform-neutral or include both Windows and Linux scenarios.
  • Add explicit notes or sections for Linux VM migration considerations, including any differences in process or prerequisites.
GitHub Create Pull Request
Site Recovery About Hyper-V (with VMM) network mapping with Site Recovery .../articles/site-recovery/hyper-v-vmm-network-mapping.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation focuses exclusively on Hyper-V and System Center Virtual Machine Manager (VMM), which are Windows-centric virtualization and management technologies. There are no references to Linux-based hypervisors (such as KVM or Xen), nor are there examples or guidance for Linux environments. All terminology, examples, and workflows assume a Windows infrastructure, with no mention of Linux equivalents or cross-platform considerations.
Recommendations
  • Include references to Linux-based hypervisors (e.g., KVM, Xen) and how network mapping would work in those environments, if supported.
  • Provide examples or guidance for disaster recovery scenarios involving Linux VMs or mixed Windows/Linux environments.
  • Clarify whether Azure Site Recovery supports Linux-based virtualization platforms and, if not, explicitly state this limitation.
  • If possible, add parity documentation for Linux tools and workflows, or link to relevant resources for Linux users.
GitHub Create Pull Request
Site Recovery Quickstart: Use Terraform to create an Azure Recovery Services vault ...les/site-recovery/quickstart-create-vault-terraform.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
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 example is given equal prominence and detail as the CLI example, despite PowerShell being primarily a Windows tool. There is no explicit mention of Linux-specific tools or shell environments (e.g., Bash), nor is there guidance for Linux users beyond the Azure CLI, which is cross-platform. The order of presentation (CLI first, then PowerShell) is neutral, but the inclusion of PowerShell may imply a Windows-centric audience.
Recommendations
  • Explicitly state that Azure CLI commands work on Linux, macOS, and Windows, and provide example shell environments (e.g., Bash, zsh) for Linux users.
  • Add a note clarifying that PowerShell is available cross-platform, but is most commonly used on Windows.
  • Consider including Linux-specific verification steps, such as using Bash scripts or native Linux tools, if relevant.
  • Ensure that troubleshooting and cleanup instructions mention any OS-specific considerations (e.g., file permissions, environment variables) for Linux users.
  • Review the documentation for any implicit assumptions about the user's operating system and make instructions OS-agnostic where possible.
GitHub Create Pull Request
Site Recovery Move from classic to modernized VMware disaster recovery ...ve-from-classic-to-modernized-vmware-disaster-recovery.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
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 for the modernized Recovery Services vault. There are no explicit examples, commands, or instructions tailored for Linux environments, and no Linux-specific tooling or migration steps are described. The page does not provide parity in examples or guidance for Linux users, focusing on generic or Windows-first patterns.
Recommendations
  • List Linux before or alongside Windows when describing supported operating systems to avoid implicit prioritization.
  • Provide explicit Linux-specific migration steps, examples, or considerations where applicable (e.g., agent installation, troubleshooting, supported distributions).
  • Include references to Linux tools or commands relevant to the migration process, not just generic or Windows-centric instructions.
  • Ensure that any screenshots, sample commands, or walkthroughs include both Linux and Windows environments where possible.
GitHub Create Pull Request
Site Recovery Set up a process server VMware/physical failback in Azure Site Recovery ...e-recovery/vmware-azure-set-up-process-server-azure.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page describes the process of setting up a process server for Azure Site Recovery failback, but it does not specify or provide examples for Linux-based process servers. All instructions assume a generic VM setup, but references to 'User name' and 'Password' with Admin permissions, and lack of mention of SSH keys or Linux-specific configuration, suggest a Windows-centric approach. There are no Linux-specific deployment steps, nor are Linux authentication methods (e.g., SSH) mentioned.
Recommendations
  • Explicitly state whether Linux-based process servers are supported and provide equivalent setup instructions if so.
  • Include examples for deploying a process server VM running Linux, including authentication via SSH keys and relevant configuration steps.
  • Clarify OS requirements and provide parity in screenshots and step-by-step instructions for both Windows and Linux process server deployments.
  • Mention any differences in process server functionality or requirements between Windows and Linux, if applicable.
GitHub Create Pull Request
Site Recovery Enable replication of encrypted Azure VMs in Azure Site Recovery ...https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/azure-to-azure-how-to-enable-replication-cmk-disks.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example
Summary
The documentation provides a detailed PowerShell example for adding a new CMK-enabled disk to a replicated VM, but does not offer equivalent CLI or Linux shell examples. There is no mention of Linux-specific tools or cross-platform alternatives, and the only code snippet is Windows PowerShell-centric. This may disadvantage Linux users or those who prefer Azure CLI or Bash.
Recommendations
  • Add equivalent Azure CLI and Bash examples for all PowerShell code snippets.
  • Explicitly mention that the procedure can be performed on Linux/macOS using Azure CLI, and provide links or references.
  • Where possible, use cross-platform commands first (e.g., Azure CLI), or present them alongside PowerShell examples.
  • Clarify any steps that are platform-agnostic, and highlight any platform-specific requirements.
  • Include a note about tool availability on different operating systems.
GitHub Create Pull Request
Site Recovery Automatic update of the Mobility service in Azure Site Recovery ...in/articles/site-recovery/azure-to-azure-autoupdate.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example
Summary
The documentation provides only Azure PowerShell script examples for managing automatic updates of the Mobility service, with no equivalent Bash, CLI, or Linux-native instructions. The troubleshooting and manual update sections focus on portal actions and Azure-specific tools, but scripting guidance is exclusively Windows/PowerShell-centric. There is no mention of how Linux administrators might perform these tasks or adapt the script for Bash/CLI environments.
Recommendations
  • Provide equivalent Azure CLI (az) commands and Bash script examples for managing automatic updates, alongside PowerShell.
  • Explicitly mention Linux support and any platform-specific considerations for running automation scripts.
  • Clarify whether the PowerShell script can be run on Linux (e.g., via PowerShell Core), and provide instructions for doing so if possible.
  • Add troubleshooting steps relevant to Linux environments, including permissions and authentication issues.
  • Ensure that examples and instructions are presented in a cross-platform manner, or at least include both Windows and Linux approaches.
GitHub Create Pull Request
Site Recovery Enable replication for private endpoints in Azure Site Recovery ...e-to-azure-how-to-enable-replication-private-endpoints.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
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 exclusively referencing the Azure portal and Azure PowerShell for configuration steps, without mentioning or providing examples for Linux tools (such as Azure CLI or Bash scripting). All procedural guidance and screenshots are based on the Azure portal, which is most commonly used by Windows administrators. There are no Linux-specific instructions, nor is the Azure CLI mentioned as an alternative to PowerShell for creating or managing private endpoints.
Recommendations
  • Add Azure CLI examples alongside PowerShell and portal instructions for all major steps (e.g., creating private endpoints, configuring DNS zones, assigning roles).
  • Explicitly mention that all steps can be performed from Linux, macOS, or Windows using Azure CLI, and provide command-line snippets.
  • Include screenshots or terminal output from Linux environments where relevant.
  • Reference Bash scripting for automation, and provide sample scripts for common tasks.
  • Ensure parity in tool recommendations, listing Azure CLI before or alongside PowerShell, not after.
  • Add a section or note for cross-platform users, clarifying that the guidance is applicable regardless of OS, and linking to official Azure CLI documentation.
GitHub Create Pull Request
Site Recovery Set up Azure VM disaster recovery to a secondary region with Azure Site Recovery ...in/articles/site-recovery/azure-to-azure-quickstart.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page exhibits Windows bias by linking only to Windows VM creation instructions and omitting Linux-specific guidance or examples. All steps and references assume a generic VM, but the only explicit reference for creating a VM points to Windows instructions, with no mention of Linux VMs or their unique considerations.
Recommendations
  • Include links to both Windows and Linux VM creation guides in the prerequisites section.
  • Add notes or examples highlighting any differences in disaster recovery setup for Linux VMs (e.g., extension installation, supported OS versions).
  • Ensure screenshots and UI references are applicable to both Windows and Linux VMs, or clarify if there are differences.
  • Explicitly state that the process applies to both Windows and Linux VMs, and mention any Linux-specific requirements or troubleshooting steps.
GitHub Create Pull Request
Site Recovery Move Azure VMs to a different Azure region with Azure Site Recovery ...icles/site-recovery/azure-to-azure-tutorial-migrate.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
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 prerequisites section, where guidance for updating root certificates is more detailed for Windows VMs (explicit instructions to install Windows updates) and less so for Linux VMs (generic advice to follow distributor guidance). No Linux-specific examples, commands, or troubleshooting steps are provided throughout the tutorial, and Windows is mentioned before Linux in the prerequisites. There are no PowerShell-heavy examples or exclusive use of Windows tools, but the lack of Linux parity in instructions and examples is evident.
Recommendations
  • Provide equally detailed instructions for Linux VMs, including common commands for updating root certificates (e.g., using apt, yum, or update-ca-certificates).
  • Include troubleshooting steps or links for common Linux distributions (Ubuntu, CentOS, RHEL) regarding certificate management and connectivity.
  • Ensure that Linux is mentioned alongside Windows in all relevant sections, not as an afterthought.
  • Add Linux-specific examples or screenshots where applicable, especially in steps that may differ between Windows and Linux VMs.
  • Consider a table or section summarizing OS-specific steps for both Windows and Linux to improve clarity and parity.
GitHub Create Pull Request
← Previous Page 29 of 35 Next →