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 451-475 of 864 flagged pages
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/vmware-azure-troubleshoot-push-install.md ...ite-recovery/vmware-azure-troubleshoot-push-install.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a clear Windows bias: troubleshooting steps, examples, and tool references are predominantly Windows-centric, with detailed instructions and command-line examples for Windows, while Linux guidance is often less detailed, grouped at the end, or missing entirely for some scenarios. Windows tools and patterns (e.g., registry edits, net commands, Control Panel, Task Manager, Group Policy, WMI, VSS, DCOM) are described in depth, while Linux equivalents are either briefly mentioned or omitted. Linux troubleshooting is often summarized in a few steps, with less context and fewer examples.
Recommendations
  • For every Windows-specific troubleshooting step, provide an equivalent Linux example or procedure, including command-line instructions and file locations.
  • Where Windows tools (e.g., registry editor, net, Control Panel, Task Manager, Group Policy, WMI, VSS) are referenced, include Linux tools and commands (e.g., systemctl, journalctl, SSH configuration, system logs, package management, systemd services).
  • Avoid presenting Windows steps or tools first by default; instead, structure sections to address both platforms equally, or clearly separate Windows and Linux subsections.
  • Add Linux-specific troubleshooting for agent installation failures, privilege issues, login failures, connectivity checks (e.g., using ssh, sftp, systemctl status), and disk/driver issues.
  • Include screenshots or terminal output examples for Linux where Windows screenshots are provided.
  • Reference Linux documentation or official resources for advanced troubleshooting (e.g., SSH hardening, system logs, SELinux/AppArmor, package installation).
  • Ensure parity in detail and clarity between Windows and Linux troubleshooting instructions throughout the document.
GitHub Create Pull Request
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/hyper-v-deployment-planner-overview.md ...s/site-recovery/hyper-v-deployment-planner-overview.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation is heavily biased towards Windows environments. All examples, prerequisites, and operational steps assume the use of Windows Server (2012 R2/2016), PowerShell, and Windows-specific tools and frameworks (.NET Framework, Visual C++ Redistributable). There are no Linux equivalents or cross-platform instructions, and the tool appears to be designed exclusively for Windows, with no mention of Linux support or alternative workflows.
Recommendations
  • Clearly state in the introduction that the Deployment Planner tool is Windows-only, if that is the case. If not, provide explicit instructions for Linux environments.
  • If possible, develop and document a cross-platform version of the Deployment Planner tool that can run on Linux or macOS, or provide a containerized version.
  • Provide equivalent command-line examples for Linux (e.g., using SSH, OpenSSL, or other cross-platform tools) where possible.
  • If PowerShell is required, mention PowerShell Core (pwsh) and its cross-platform capabilities, and provide instructions for installing and running the tool on Linux.
  • List any limitations or lack of support for non-Windows environments explicitly in the prerequisites section.
  • For report generation, suggest open-source alternatives to Microsoft Excel (such as LibreOffice Calc) or provide CSV/JSON output options.
GitHub Create Pull Request
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/avs-tutorial-prepare-avs.md ...ain/articles/site-recovery/avs-tutorial-prepare-avs.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a Windows-first bias in several areas. Windows instructions and tools (such as registry edits and Windows Firewall) are described in greater detail and appear before Linux equivalents. The Windows RDP section is more comprehensive, mentioning specific firewall settings and SAN policy, while the Linux SSH section is brief and lacks comparable troubleshooting or configuration depth. There are also references to Windows-specific tools and patterns (e.g., registry, Windows Firewall) without Linux analogs or detailed Linux examples.
Recommendations
  • Provide Linux instructions with equivalent detail to Windows, such as specifying how to configure SSH, firewall (e.g., iptables, firewalld, ufw), and SELinux/AppArmor settings.
  • Include troubleshooting steps for Linux VMs after failover, similar to the Windows RDP troubleshooting section.
  • When listing steps for both OS types, alternate the order or present them in parallel sections to avoid always listing Windows first.
  • Where Windows-specific tools (e.g., registry, Windows Firewall) are mentioned, provide Linux equivalents (e.g., editing /etc/ssh/sshd_config, using systemctl to enable SSH, configuring firewall rules).
  • Add links to Linux-specific documentation for further reading, as is done for Windows.
GitHub Create Pull Request
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/azure-to-azure-replicate-after-migration.md ...e-recovery/azure-to-azure-replicate-after-migration.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation demonstrates a mild Windows bias by consistently presenting Windows instructions and tools before Linux equivalents. Windows-specific tools and folder paths (e.g., Control Panel, C:\WindowsAzure\Packages) are mentioned in detail, while Linux instructions are less detailed and sometimes less prominent. The validation steps for Windows are more GUI-oriented, while Linux steps are more generic. There is also a lack of parity in troubleshooting and validation detail between platforms.
Recommendations
  • Alternate the order of Windows and Linux instructions, or present them in parallel sections to avoid always listing Windows first.
  • Provide equivalent detail and validation steps for Linux as for Windows, including specific file paths, log locations, and version checks.
  • Include Linux-specific troubleshooting links and resources, similar to those provided for Windows.
  • Where possible, use cross-platform language and avoid assuming a Windows-centric workflow (e.g., mention both Control Panel and Linux package managers in the same prominence).
  • Ensure that command-line examples are provided for both platforms, and avoid GUI-only instructions for Windows.
GitHub Create Pull Request
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/hyper-v-azure-tutorial.md .../main/articles/site-recovery/hyper-v-azure-tutorial.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation is heavily focused on Windows environments, specifically Hyper-V, and provides only Windows-based instructions and tooling (e.g., .exe installers, CMD commands, Windows file paths). There are no examples or references for Linux environments, tools, or equivalent processes, and all command-line instructions are Windows-centric. The documentation assumes the user is operating in a Windows ecosystem, with no mention of Linux-based Hypervisors or cross-platform considerations.
Recommendations
  • Explicitly state that the tutorial is only applicable to Windows/Hyper-V environments, and provide links to equivalent Linux/KVM/VMware documentation if available.
  • Where possible, mention whether Azure Site Recovery supports Linux-based hypervisors, and if so, provide parallel instructions or links.
  • If cross-platform support is not available, clarify this early in the prerequisites or introduction to set user expectations.
  • If any steps can be performed from a Linux environment (e.g., using Azure CLI or REST APIs), provide Linux shell examples alongside Windows examples.
  • Consider adding a comparison table or section outlining support and steps for different hypervisor platforms (Windows/Hyper-V, Linux/KVM, VMware, etc.).
GitHub Create Pull Request
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/region-move-cross-geos.md .../main/articles/site-recovery/region-move-cross-geos.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a Windows bias by providing detailed registry and CLI instructions specifically for Windows (including registry key changes and REG ADD command), referencing Windows-specific tools and patterns (such as the Windows registry and Local Administrator), and linking to Windows Time Server documentation. Linux is only briefly mentioned (e.g., 'the account should be root'), with no equivalent step-by-step instructions or CLI examples for Linux systems. No Linux-specific troubleshooting, commands, or configuration guidance is provided, and Windows procedures are presented first and in more detail.
Recommendations
  • Provide equivalent step-by-step instructions and CLI commands for Linux systems, such as how to prepare the Linux environment for Mobility service installation (e.g., required packages, firewall configuration, SELinux/AppArmor considerations).
  • Include Linux-specific troubleshooting steps, such as checking system time synchronization (e.g., using timedatectl or ntpd/chrony), and reference relevant Linux documentation instead of only Windows Time Server.
  • When describing account preparation, give explicit Linux commands or configuration file changes (e.g., ensuring root SSH access, sudoers configuration) alongside the Windows registry steps.
  • Balance the order of presentation so that Linux and Windows instructions are given equal prominence, or clearly separate them into distinct subsections.
  • Reference Linux tools and patterns (e.g., systemd, journalctl, SSH configuration) where appropriate, not just Windows tools and registry.
  • Add examples of common issues and solutions for Linux VMs during the migration process, similar to the detail given for Windows.
GitHub Create Pull Request
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/exclude-disks-replication.md ...in/articles/site-recovery/exclude-disks-replication.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation page demonstrates a strong Windows bias. All detailed examples focus exclusively on Windows VMs, with disk layouts, drive letters (C:, D:, etc.), and screenshots from Windows interfaces. Instructions reference Windows-specific tools (diskmgmt.msc, service console, command prompt, Net start/stop). SQL Server examples assume Windows as the guest OS. There are no Linux VM examples, nor are Linux-specific tools, filesystems, or commands mentioned. Even when Linux is referenced (e.g., in failback behavior), it is only in passing, not as a worked example.
Recommendations
  • Add parallel Linux VM examples for disk exclusion, failover, and failback, including typical Linux disk layouts (e.g., /, /var, /tmp, /mnt/data) and relevant files (e.g., swap, tempdb for SQL Server on Linux, etc.).
  • Include Linux-specific instructions for adding and formatting disks (e.g., using fdisk, mkfs, mount, and updating /etc/fstab).
  • Show how to manage SQL Server tempdb on Linux (e.g., using systemctl for service management, Linux file paths, and sqlcmd usage on Linux).
  • Reference Linux tools and commands (e.g., lsblk, parted, systemctl) alongside Windows tools.
  • Provide screenshots or terminal output from Linux environments where appropriate.
  • Clarify any differences in behavior or limitations for Linux VMs, not just Windows.
  • Ensure that all tables and scenarios include both Windows and Linux perspectives where relevant.
GitHub Create Pull Request
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/azure-to-azure-common-questions.md ...icles/site-recovery/azure-to-azure-common-questions.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation exhibits several forms of Windows bias. Windows-specific features, tools, and examples (such as PowerShell and Volume Shadow Copy Service) are mentioned prominently, often without equivalent Linux guidance or examples. In some sections, Linux support is only briefly referenced or explicitly excluded (e.g., shared disks), and Windows terminology or tools are used as the default or only example. PowerShell is frequently suggested for advanced tasks, with no mention of Bash, CLI, or Linux-native alternatives.
Recommendations
  • Provide Linux-specific examples and guidance alongside Windows examples, especially for scripting and automation (e.g., show Azure CLI or Bash scripts in addition to PowerShell).
  • When referencing Windows tools or features (such as VSS), include Linux equivalents or explain how similar functionality can be achieved on Linux (e.g., using pre/post scripts for app-consistency).
  • Avoid presenting Windows options or tools first by default; instead, present both Windows and Linux options in parallel or clarify applicability.
  • Where features are unsupported for Linux (e.g., shared disks), clearly state this early and provide links to feature requests or workarounds if available.
  • Expand documentation for Linux-specific scenarios, such as encrypted disk replication, app-consistent snapshots, and automation using non-Windows tools.
  • Include troubleshooting and best practices sections 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-manage-configuration-server.md ...e-recovery/vmware-azure-manage-configuration-server.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a strong Windows bias. All command-line examples, administrative tasks, and tool references are Windows-centric, relying heavily on PowerShell, Windows paths, and Windows-specific executables. There are no Linux-specific instructions, examples, or tool alternatives provided, despite mentioning support for Linux physical servers. The use of Windows tools and patterns is pervasive, and Linux parity is not addressed.
Recommendations
  • Provide equivalent Linux command-line instructions for tasks such as certificate renewal, passphrase generation, and server registration/unregistration.
  • Include examples using Bash or shell commands where appropriate, especially for Linux-based configuration servers or physical servers.
  • Document the location of relevant files and executables for Linux systems (e.g., paths, required permissions, dependencies).
  • Clarify whether tools like cspsconfigtool.exe or genpassphrase.exe are available or have alternatives on Linux, and provide installation or usage guidance.
  • When referencing PowerShell or Windows tools, always follow with Linux alternatives or note if a feature is Windows-only.
  • Explicitly state any limitations or differences in managing configuration servers on Linux versus Windows.
  • Add screenshots or walkthroughs for Linux environments where GUI or CLI actions are described.
GitHub Create Pull Request
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/configure-mobility-service-proxy-settings.md ...-recovery/configure-mobility-service-proxy-settings.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a Windows-first bias by presenting Windows-specific tools and instructions (such as Internet Explorer settings and psexec usage) before Linux equivalents. It provides detailed steps for Windows (including tool usage) but omits comparable Linux command-line examples or tools. The Linux section is less detailed and lacks parity in guidance, particularly for configuring environment variables or editing the ProxyInfo.conf file.
Recommendations
  • Provide Linux configuration steps with the same level of detail as Windows, including example commands for editing /etc/profile or /etc/environment (e.g., using nano or vi).
  • Include Linux-specific tools or methods for setting environment variables for system services, such as using 'export' or editing systemd service files.
  • Present Windows and Linux instructions in parallel, rather than listing Windows first, to avoid the perception of prioritizing one platform.
  • Offer example commands for creating and editing ProxyInfo.conf on Linux, similar to the Windows file path instructions.
  • Avoid referencing Windows-only tools (like psexec and Internet Explorer) without Linux equivalents or alternatives.
GitHub Create Pull Request
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/site-recovery-plan-capacity-vmware.md ...es/site-recovery/site-recovery-plan-capacity-vmware.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in several areas: it provides registry key and PowerShell cmdlet instructions specific to Windows, references Windows-specific tools (MMC snap-in, registry, Windows Azure Backup), and gives detailed step-by-step instructions for Windows-based master target server installation, while Linux instructions are limited to a single link. There are no Linux command-line examples or parity in configuration guidance, and Windows tools and patterns are mentioned first and in greater detail.
Recommendations
  • Provide equivalent Linux command-line examples for bandwidth throttling and process server configuration (e.g., using sysctl, tc, or other Linux-native tools).
  • Include Linux-specific instructions for altering replication settings, not just a link to a separate article.
  • Mention Linux tools and configuration patterns alongside Windows ones, not only as an afterthought or in a separate section.
  • Ensure that all registry or PowerShell-based instructions have clear Linux alternatives (such as configuration files or commands).
  • Balance the depth of guidance for Linux and Windows, including screenshots and step-by-step instructions for both platforms.
  • Where Windows tools (MMC, registry, PowerShell) are referenced, clarify their Linux equivalents or state if a feature is not available on Linux.
GitHub Create Pull Request
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/azure-to-azure-how-to-enable-replication-s2d-vms.md ...ry/azure-to-azure-how-to-enable-replication-s2d-vms.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation is heavily oriented towards Windows environments, specifically referencing Windows Failover Clustering and Storage Spaces Direct (S2D), which are Windows-only technologies. All examples, terminology, and linked resources are Windows-centric, with no mention of Linux-based clustering, storage, or disaster recovery solutions. There are no Linux equivalents or guidance for users running Linux VMs or open-source clustering/storage stacks.
Recommendations
  • Explicitly state that the guide is only applicable to Windows-based clusters and provide a reference or link to equivalent guidance for Linux-based clusters if available.
  • Add a section or note addressing disaster recovery for Linux VMs, including supported clustering and storage technologies (e.g., Pacemaker, DRBD, LVM, etc.), or clarify current limitations if Linux clustering is not supported.
  • Where possible, provide parallel examples or documentation links for Linux environments to ensure parity and inclusivity.
  • Avoid assuming the use of Windows-specific tools and patterns (e.g., Failover Cluster, Storage Spaces Direct) without mentioning alternatives or the scope of applicability.
GitHub Create Pull Request
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/monitor-log-analytics.md ...b/main/articles/site-recovery/monitor-log-analytics.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a Windows bias in the section on configuring the Microsoft monitoring agent for churn and upload rate logs. It exclusively provides instructions and screenshots for installing and configuring the Windows agent, with no mention of Linux agents or instructions for Linux-based Process Servers. The 'Connected Sources' setup, agent download, and performance counter configuration are all Windows-specific, and there are no Linux equivalents or guidance for Linux-based environments.
Recommendations
  • Add equivalent instructions for installing and configuring the Microsoft monitoring agent on Linux-based Process Servers, including download links, configuration steps, and screenshots.
  • Include guidance on setting up Linux performance counters or their equivalents, and how to collect churn/upload rate metrics from Linux Process Servers.
  • Wherever agent installation is discussed, mention both Windows and Linux options, or clarify if Linux is not supported.
  • Ensure that all steps and screenshots are provided for both platforms, or explicitly state platform limitations.
  • Review all examples and instructions to ensure Linux parity, and add Linux-specific troubleshooting or notes where relevant.
GitHub Create Pull Request
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/deploy-vmware-azure-replication-appliance-modernized.md ...tps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/deploy-vmware-azure-replication-appliance-modernized.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation demonstrates a Windows bias by providing PowerShell-based setup instructions as the only command-line/manual alternative to the OVF template, referencing Windows registry and group policy settings, and omitting Linux-based setup or troubleshooting examples. Windows-specific tools and configuration patterns are mentioned exclusively, and Linux is only referenced in the context of VM credentials, not as a platform for the appliance or for management tasks.
Recommendations
  • Provide equivalent Linux-based setup instructions for deploying and configuring the replication appliance, including command-line examples using Bash or shell scripts.
  • Include Linux-specific troubleshooting steps and configuration checks (e.g., for connectivity, permissions, or required packages) alongside Windows registry and group policy checks.
  • Clarify whether the replication appliance can be deployed on Linux-based VMs, and if so, provide guidance for those scenarios.
  • When referencing PowerShell, also mention or link to Linux-compatible alternatives (such as Azure CLI or shell scripts) where possible.
  • Ensure that examples and screenshots are balanced between Windows and Linux environments, or explicitly state platform limitations if Windows is the only supported OS.
GitHub Create Pull Request
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/hyper-v-azure-architecture.md ...n/articles/site-recovery/hyper-v-azure-architecture.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation is heavily focused on Windows environments, specifically Hyper-V and related Microsoft tools (e.g., System Center VMM, Recovery Services agent, Hyper-V Replica). There are no examples, references, or guidance for Linux-based hypervisors or management tools. All technical details, commands, and processes are described in terms of Windows technologies, with no mention of Linux equivalents or cross-platform considerations.
Recommendations
  • Clearly state at the beginning that the guide is specific to Hyper-V (a Windows-only hypervisor) and does not apply to Linux-based virtualization platforms.
  • Provide links or references to equivalent Azure Site Recovery documentation for Linux-based environments (e.g., VMware, physical Linux servers, or Linux KVM).
  • If possible, add a comparison table or section outlining how disaster recovery architecture and processes differ for Linux-based hypervisors or workloads.
  • Ensure that related documentation for Azure Site Recovery covers Linux scenarios with equal depth and visibility, and cross-link these resources.
  • If any Linux guest VM considerations exist (e.g., agent installation, supported distributions), mention them explicitly.
GitHub Create Pull Request
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/azure-to-azure-troubleshoot-replication.md ...te-recovery/azure-to-azure-troubleshoot-replication.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a Windows bias by prioritizing Windows-specific tools, paths, and troubleshooting steps. PowerShell and Windows file paths are provided explicitly, while Linux equivalents are either missing or only briefly mentioned. Troubleshooting steps and error log locations are described in detail for Windows, with Linux guidance often relegated to a single line or omitted. Windows services and commands are listed first and in greater detail, and Windows tools (like VSS) are discussed extensively without Linux alternatives.
Recommendations
  • Provide Linux-specific troubleshooting steps and examples alongside Windows instructions, including equivalent commands and log file locations.
  • Include Linux command-line examples (e.g., bash, systemctl) where PowerShell or Windows CMD commands are given.
  • When referencing file paths or configuration files, always provide both Windows and Linux locations and formats.
  • Discuss Linux-specific tools or mechanisms (e.g., LVM snapshots, systemd services) where Windows tools like VSS are mentioned.
  • Ensure that Linux error messages, service names, and restart procedures are as detailed as their Windows counterparts.
  • Avoid listing Windows steps or tools first by default; present both platforms with equal prominence.
GitHub Create Pull Request
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/hyper-v-vmm-azure-tutorial.md ...n/articles/site-recovery/hyper-v-vmm-azure-tutorial.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation is heavily oriented towards Windows environments, specifically focusing on Hyper-V and System Center VMM, both of which are Windows-only technologies. All setup and installation instructions, including command-line examples, use Windows tools and PowerShell commands. There are no Linux equivalents or alternative instructions for non-Windows environments, and the documentation assumes the use of Windows throughout.
Recommendations
  • Clearly state early in the documentation that this guide is specific to Windows/Hyper-V environments, and provide links to equivalent guides for Linux/KVM or VMware environments if available.
  • Where possible, mention if similar disaster recovery workflows exist for Linux-based hypervisors (e.g., KVM, Xen) and link to relevant documentation.
  • If Azure Site Recovery supports Linux-based hosts or VMs, include parallel instructions or at least reference documentation for those scenarios.
  • Avoid using only PowerShell or Windows command-line examples; if cross-platform tools or REST APIs are available, provide examples for Linux/bash as well.
  • Add a comparison table or section outlining supported platforms and any differences in setup between Windows and Linux environments.
GitHub Create Pull Request
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/site-recovery-runbook-automation.md ...cles/site-recovery/site-recovery-runbook-automation.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools Windows First
Summary
The documentation is heavily biased towards Windows and PowerShell environments. All code examples are in PowerShell, with no mention or examples for Linux, Bash, or Python. The required modules and scripting patterns are specific to PowerShell and the AzureRM/Az modules, which are primarily used in Windows-centric automation. There is no guidance for users managing Linux VMs or those who prefer cross-platform scripting languages. The documentation assumes a Windows-first approach, both in tooling and in the order of presentation.
Recommendations
  • Add equivalent examples using Azure CLI (bash) and/or Python SDK for runbook automation, especially for Linux-based recovery scenarios.
  • Explicitly mention support for Linux VMs and provide guidance or links for automating recovery steps on Linux workloads.
  • Include sample runbooks written in Python or Bash, and show how to use them in Azure Automation.
  • Clarify which features or modules are cross-platform and which are Windows/PowerShell-specific.
  • Provide a comparison table or section outlining scripting options for both Windows and Linux environments.
GitHub Create Pull Request
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/hyper-v-deployment-planner-analyze-report.md ...-recovery/hyper-v-deployment-planner-analyze-report.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation is heavily focused on Hyper-V, a Windows-centric virtualization technology, and exclusively discusses concepts, tools, and workflows relevant to Windows environments. There are no references to Linux-based hypervisors (such as KVM or VMware on Linux), nor are there any examples, commands, or considerations for Linux users. All terminology, examples, and requirements are tailored to Windows/Hyper-V administrators, with no Linux parity.
Recommendations
  • Add a section clarifying the scope of the tool and documentation, explicitly stating if it is only for Hyper-V (Windows) environments, and provide links to equivalent tools or documentation for Linux/KVM/VMware environments if available.
  • If Azure Site Recovery supports Linux-based hypervisors or Linux VMs, include examples, requirements, and report analysis guidance for those scenarios.
  • Where possible, generalize terminology (e.g., 'on-premises hypervisor' instead of 'Hyper-V server') and provide parallel Linux/KVM/VMware instructions or notes.
  • Include a comparison table or FAQ addressing differences in deployment planner usage and report analysis between Windows/Hyper-V and Linux-based environments.
  • If the tool is Windows-only, suggest alternative planning/reporting tools for Linux users, or provide guidance on how Linux VMs can be assessed for Azure Site Recovery readiness.
GitHub Create Pull Request
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/hyper-v-exclude-disk.md ...ob/main/articles/site-recovery/hyper-v-exclude-disk.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation is focused exclusively on Hyper-V, a Windows-based virtualization platform, and does not mention or provide examples for Linux-based hypervisors (such as KVM or VMware on Linux). All instructions, terminology, and scenarios are tailored to Windows environments, with no Linux equivalents or cross-platform considerations discussed.
Recommendations
  • Include guidance or references for excluding disks from replication for Linux-based hypervisors (e.g., KVM, VMware on Linux) if supported by Azure Site Recovery.
  • Add examples or notes for administrators managing non-Windows environments, clarifying whether similar functionality is available and how to achieve it.
  • Explicitly state if the feature is only available for Hyper-V (Windows) and provide links to equivalent documentation for Linux platforms if applicable.
  • Consider a section comparing the process for Windows (Hyper-V) and Linux-based virtualization platforms to improve cross-platform parity.
GitHub Create Pull Request
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/monitoring-high-churn.md ...b/main/articles/site-recovery/monitoring-high-churn.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a Windows-first bias by presenting Windows-specific tools (Resource Monitor, Performance Monitor) in greater detail and before Linux equivalents. The Windows section includes step-by-step instructions and screenshots, while the Linux section only briefly mentions iotop and iostat without detailed usage, examples, or visuals. No Linux-native graphical tools or monitoring workflows are described, and the Linux section lacks parity in depth and guidance.
Recommendations
  • Provide step-by-step instructions for using iotop and iostat, including example command outputs and explanations.
  • Include screenshots or sample outputs for Linux tools, similar to the Windows section.
  • Mention additional Linux monitoring tools (e.g., dstat, atop, glances, GNOME System Monitor) to match the breadth of Windows tool coverage.
  • Present Windows and Linux sections in parallel structure, ensuring equal depth and clarity for both.
  • Consider introducing the Linux section before or alongside the Windows section to avoid a Windows-first impression.
GitHub Create Pull Request
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/vmware-azure-troubleshoot-upgrade-failures.md ...recovery/vmware-azure-troubleshoot-upgrade-failures.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation exclusively provides troubleshooting steps and examples for Windows environments, referencing Windows-specific tools (Command Prompt, Registry Editor, Task Manager), file paths (C:\), and executable formats (.exe). There are no Linux equivalents, commands, or guidance, indicating a strong Windows bias.
Recommendations
  • Add parallel troubleshooting steps for Linux environments, if supported by the product.
  • Include Linux shell command examples (e.g., using bash, tar, or unzip for extraction).
  • Reference Linux file paths and conventions alongside Windows examples.
  • Mention Linux equivalents for tools like Registry Editor (e.g., editing configuration files), and Task Manager (e.g., using top, htop, or ps).
  • Clarify in the introduction if the product or troubleshooting steps are only applicable to Windows, or explicitly state Linux is not supported if that is the case.
GitHub Create Pull Request
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/hyper-v-azure-troubleshoot.md ...n/articles/site-recovery/hyper-v-azure-troubleshoot.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation is heavily focused on Windows environments, specifically Hyper-V on Windows Server. Troubleshooting steps, log locations, and example commands are almost exclusively Windows-centric, with PowerShell and Windows GUI tools (Event Viewer, Task Manager, Resource Monitor, Disk Management) being referenced throughout. Linux is only briefly mentioned in a single bullet point, with no concrete troubleshooting steps or examples provided for Linux-based VMs or environments.
Recommendations
  • Provide parallel troubleshooting steps and log locations for Linux-based guest VMs, especially for scenarios where Linux VMs are protected or replicated via Hyper-V.
  • Include Linux command-line equivalents for checking service status, disk configuration, and VSS/app-consistent snapshot status (e.g., systemctl, journalctl, lsblk, etc.).
  • When referencing PowerShell or Windows GUI tools, also mention or link to Linux tools and commands where applicable.
  • Add explicit Linux examples for common troubleshooting tasks, such as checking integration services, verifying app-consistency, and collecting logs.
  • Clarify which steps are Windows-only and which apply to Linux guests, and ensure Linux parity in troubleshooting guidance.
GitHub Create Pull Request
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/hyper-v-azure-common-questions.md ...ticles/site-recovery/hyper-v-azure-common-questions.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation is heavily focused on Windows environments, specifically Hyper-V on Windows Server, and consistently references Windows-centric tools and workflows (e.g., VMM, PowerShell) without providing Linux equivalents or examples. There are no Linux-specific instructions, examples, or considerations, and all automation and scripting references are to PowerShell. The documentation assumes the reader is operating in a Windows ecosystem, with no mention of Linux-based Hypervisors or management tools.
Recommendations
  • Add explicit statements clarifying that Azure Site Recovery for Hyper-V is only supported on Windows, and provide links to equivalent documentation for Linux-based disaster recovery scenarios (e.g., for KVM, VMware on Linux, or physical Linux servers).
  • Where PowerShell is referenced for automation, provide equivalent Azure CLI or REST API examples that are cross-platform and can be run from Linux or macOS.
  • If possible, mention or link to tools and workflows for managing disaster recovery for Linux VMs or workloads, including how to replicate and failover Linux VMs to Azure.
  • Include a section addressing common questions or considerations for Linux administrators, such as supported guest OSes, agent installation on Linux VMs, and any differences in failover/failback processes.
  • Ensure that any references to management tools (e.g., VMM, Hyper-V Manager) are accompanied by notes on their platform specificity and alternatives for non-Windows environments.
GitHub Create Pull Request
Site Recovery https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/site-recovery-iis.md .../blob/main/articles/site-recovery/site-recovery-iis.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation is heavily focused on Windows environments, specifically IIS on Windows Server. All examples, scripts, and recovery scenarios are centered around Windows tools and patterns (e.g., IIS, PowerShell scripts, web.config, ARR, SQL Server). There are no Linux equivalents or mentions of cross-platform scenarios, and Linux-based web servers (such as Apache or Nginx) are not addressed at all.
Recommendations
  • Include parallel guidance for Linux-based web applications (e.g., Apache, Nginx) and their disaster recovery using Azure Site Recovery.
  • Provide Linux-specific examples for updating DNS, connection strings, site bindings, and certificate management (e.g., using Bash scripts, systemd, or relevant Linux tools).
  • Reference Linux-based scripting (Bash, Python) alongside PowerShell for automation steps.
  • Mention and link to Azure Site Recovery support for Linux VMs, including any prerequisites or limitations.
  • Clarify in the introduction that the article is specific to Windows/IIS, and provide links or references to Linux documentation if available.
GitHub Create Pull Request
← Previous Page 19 of 35 Next →