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 476-500 of 864 flagged pages
Site Recovery
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/vmware-azure-set-up-source.md
...n/articles/site-recovery/vmware-azure-set-up-source.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation predominantly provides Windows-centric instructions and examples, especially in the antivirus exclusions section, where Windows paths and registry keys are listed extensively before Linux equivalents. Linux-specific guidance is minimal and appears only after several Windows-focused sections. There are also references to Windows licensing and tools without mentioning Linux alternatives or parity.
Recommendations
- Present Linux and Windows instructions in parallel sections or tables, ensuring equal prominence.
- Include Linux-specific examples and paths wherever Windows examples are provided, not just as an afterthought.
- If registry exclusions are mentioned for Windows, clarify whether similar steps are needed or possible on Linux, or explicitly state if not applicable.
- When discussing licensing or activation (e.g., Windows evaluation license), mention any Linux-specific considerations or clarify if not relevant.
- Review all steps to ensure that Linux administrators have clear, actionable instructions, not just Windows users.
Create Pull Request
Site Recovery
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/site-recovery-active-directory.md
...ticles/site-recovery/site-recovery-active-directory.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation is heavily focused on Windows environments, specifically Active Directory and DNS as implemented on Windows Server. All examples, tools, and troubleshooting steps reference Windows-specific utilities (e.g., dcdiag, nltest, dnscmd, registry edits), and there is no mention of Linux-based domain controllers (such as Samba AD DC) or DNS servers. The guidance assumes the use of Windows Server roles and tools, with no Linux equivalents or cross-platform considerations provided.
Recommendations
- Add explicit notes about support (or lack thereof) for Linux-based Active Directory alternatives (e.g., Samba AD DC) and DNS servers.
- Provide parallel instructions and examples for Linux-based domain controllers and DNS servers, if supported by Azure Site Recovery.
- Include Linux command-line equivalents for diagnostic and recovery steps (e.g., using samba-tool, systemctl, or BIND utilities).
- Clarify early in the documentation that the instructions are specific to Windows Server environments if Linux is not supported, or provide a section on cross-platform considerations.
- Mention Linux tools and patterns (e.g., systemd, /etc/krb5.conf, /etc/bind) where relevant, and provide links to Linux documentation for AD/DNS disaster recovery.
Site Recovery
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/unregister-vmm-server-script.md
...articles/site-recovery/unregister-vmm-server-script.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation and provided script are entirely focused on Windows environments, specifically using PowerShell, Windows registry paths, Windows services, and Windows clustering tools. There are no examples, instructions, or references for performing similar tasks on Linux-based systems or with cross-platform tools. The documentation assumes the user is operating in a Windows environment from the outset.
Recommendations
- Provide equivalent instructions or scripts for Linux environments, if VMM or similar functionality is supported on Linux.
- If the operation is inherently Windows-only (e.g., due to VMM being a Windows-only product), clearly state this limitation at the beginning of the documentation.
- Where possible, mention cross-platform alternatives or tools, or provide guidance for users managing hybrid environments.
- Include a section that addresses Linux administrators, even if only to clarify that the script and procedure are not applicable to Linux.
- If any cleanup or unregister operations are possible via REST APIs or other cross-platform interfaces, provide examples for those as well.
Site Recovery
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/site-recovery-overview.md
.../main/articles/site-recovery/site-recovery-overview.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows-first bias by frequently mentioning Windows technologies (such as Windows Server Failover Clusters, SQL Server Always On, and Windows physical servers) before or more prominently than Linux equivalents. There are no Linux-specific examples, tools, or scenarios described, and the only explicit mention of Linux is in a parenthetical note. Windows tools and patterns (e.g., shared disk for WSFC, SQL FCI) are discussed in detail, while Linux disaster recovery scenarios are not addressed.
Recommendations
- Include explicit Linux-based disaster recovery scenarios and examples, such as replicating Linux VMs or physical servers, and protecting Linux-based clustered applications (e.g., Pacemaker, Corosync).
- Provide parity in workload examples by mentioning common Linux workloads (e.g., MySQL, PostgreSQL, Apache, NGINX) alongside Windows workloads like SQL Server.
- Add Linux-specific guidance or links for scripting, automation, and failover testing (e.g., using Bash scripts, Ansible, or Linux-native tools) in recovery plans.
- Balance the discussion of Windows and Linux tools and patterns, ensuring that Linux equivalents are introduced wherever Windows-specific technologies are described.
- Where shared disk or clustering is discussed, mention Linux clustering solutions and how Site Recovery supports them, if applicable.
Site Recovery
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/site-recovery-dynamicsax.md
...ain/articles/site-recovery/site-recovery-dynamicsax.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation is heavily oriented towards Windows environments, specifically referencing Windows Server, Active Directory, SQL Server, and Windows-based Dynamics AX components. There are no Linux examples or mentions of Linux-based equivalents for any of the steps, tools, or patterns. All technical guidance, screenshots, and recommendations assume a Windows-centric deployment.
Recommendations
- Include explicit statements about Linux support or lack thereof for Dynamics AX and Azure Site Recovery in this context.
- If Linux-based deployments are possible (e.g., for SQL Server or other components), provide parallel instructions and examples for Linux environments.
- Mention Linux-compatible tools or approaches for disaster recovery, such as using Linux-based domain controllers (e.g., Samba) if supported, or alternative database engines.
- Clarify in prerequisites and throughout the document whether the guidance is Windows-only or if there are cross-platform considerations.
- Provide at least one end-to-end example or scenario for a mixed or Linux-based environment, if supported by the product.
Site Recovery
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/site-recovery-sap.md
.../blob/main/articles/site-recovery/site-recovery-sap.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by focusing exclusively on SAP NetWeaver deployments on Windows, referencing Windows Server Failover Cluster, Storage Spaces Direct, and SIOS DataKeeper, and omitting Linux-based deployment guidance or examples. No Linux clustering or high availability solutions (such as Pacemaker or NFS) are mentioned, and all technical recommendations and examples assume a Windows environment.
Recommendations
- Add explicit guidance and examples for SAP NetWeaver deployments on Linux, including supported Linux distributions on Azure.
- Include Linux-based high availability and clustering solutions (e.g., Pacemaker, Corosync, NFS, GlusterFS) as alternatives to Windows Server Failover Cluster and Storage Spaces Direct.
- Provide parity in disaster recovery steps, scripts, and automation for Linux-based SAP environments, including references to relevant Azure Automation scripts or runbooks.
- Mention and link to SAP and Azure documentation for Linux-based SAP deployments and disaster recovery best practices.
- Ensure diagrams and architectural references include both Windows and Linux deployment patterns where applicable.
Site Recovery
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/site-recovery-failover-to-azure-troubleshoot.md
...covery/site-recovery-failover-to-azure-troubleshoot.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows-first bias in several areas. Troubleshooting steps for hydration failures provide detailed, step-by-step PowerShell scripts and registry instructions for Windows Guest OS, but do not offer equivalent Linux guidance. Windows tools like PsExec and Internet Explorer are referenced for proxy troubleshooting, with no Linux alternatives. In some sections, Windows-specific errors and solutions are described in detail before Linux is mentioned, and Linux troubleshooting is often limited or absent. Only one Linux-specific command is provided (for serial console issues), and even there, the context is minimal compared to the Windows sections.
Recommendations
- For every Windows-specific troubleshooting script or step (e.g., hydration, registry changes), provide equivalent Linux commands or scripts (e.g., systemd service checks, driver/module configuration).
- When referencing Windows tools like PsExec and Internet Explorer, also describe how to achieve the same outcome on Linux (e.g., using curl, wget, or editing environment variables directly).
- Ensure Linux troubleshooting examples are as detailed as Windows ones, including command-line steps, expected outputs, and error interpretation.
- When listing troubleshooting steps, avoid always presenting Windows first; alternate or group by OS, or clearly label sections for each OS.
- Expand Linux coverage in sections where only Windows is discussed (e.g., hydration, proxy settings, unexpected shutdowns), or explicitly state if an issue is Windows-only.
- Provide links to relevant Linux documentation and tools alongside Windows references.
Site Recovery
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/site-recovery-sql.md
.../blob/main/articles/site-recovery/site-recovery-sql.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation demonstrates a strong Windows bias. All examples, references, and linked resources are focused on Windows-based SQL Server deployments. There are no instructions, examples, or considerations for Linux-based SQL Server, despite its support. Windows-specific tools (e.g., Task Manager, PowerShell scripts) are referenced exclusively, and all high availability/disaster recovery patterns are described in the context of Windows. Linux equivalents are not mentioned or provided.
Recommendations
- Include explicit guidance and examples for SQL Server running on Linux, including supported BCDR technologies and any Azure Site Recovery considerations.
- Provide Linux-specific instructions for monitoring (e.g., using iostat, vmstat, or other Linux tools instead of Task Manager).
- Offer PowerShell alternatives or equivalent Bash/shell scripts for automation steps, or clarify if only Windows is supported.
- Reference and link to documentation for SQL Server on Linux high availability and disaster recovery options.
- Clearly state any limitations or lack of support for Linux scenarios, if applicable, to avoid confusion.
- Balance the order of presentation so that Linux and Windows are treated equally where both are supported.
Site Recovery
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/site-recovery-workload.md
.../main/articles/site-recovery/site-recovery-workload.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Powershell Heavy
Summary
The documentation demonstrates a Windows bias by prioritizing Windows workloads (Active Directory, SQL Server, SharePoint, Exchange, IIS, Dynamics AX, RDS) in both structure and detail. Windows tools and technologies are mentioned exclusively or in greater depth, while Linux and open-source equivalents are only briefly referenced or grouped generically. There are no Linux-specific examples, tools, or application scenarios, and the documentation lacks parity in describing Linux disaster recovery workflows.
Recommendations
- Add Linux-first sections or examples, such as protecting common Linux workloads (e.g., Apache, NGINX, MySQL/PostgreSQL, Samba, LDAP).
- Include Linux-specific disaster recovery workflows, tools, and best practices, such as integration with systemd, cron, rsync, or native Linux clustering solutions.
- Provide example scripts or automation for Linux environments (e.g., bash scripts) alongside or before Windows/PowerShell examples.
- Highlight open-source and cross-platform applications (e.g., PostgreSQL, MariaDB, Tomcat) with the same level of detail as Windows workloads.
- Ensure parity in technical depth and guidance for both Windows and Linux scenarios, including references to relevant Linux documentation and community best practices.
Site Recovery
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/vmware-azure-common-questions.md
...rticles/site-recovery/vmware-azure-common-questions.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation exhibits a moderate Windows bias. Windows tools, paths, and PowerShell are mentioned more frequently and often before Linux equivalents. Some instructions and examples (e.g., installation paths, manual installation, MySQL placement) are Windows-centric or only mention Windows locations. PowerShell is highlighted as a primary automation method, with less emphasis on Linux scripting or CLI alternatives. In a few cases, Linux equivalents are provided, but often as a secondary note or with less detail.
Recommendations
- Provide Linux examples and paths alongside Windows ones in all relevant sections (e.g., installer locations, MySQL placement).
- When mentioning PowerShell, also reference Bash/CLI or scripting options for Linux users.
- Ensure that automation and scripting guidance includes examples for Linux environments (e.g., Azure CLI, shell scripts).
- List Linux instructions before or alongside Windows instructions to avoid 'Windows-first' ordering.
- Where Windows tools or patterns are referenced (e.g., Configuration Manager), mention Linux alternatives (e.g., Ansible, shell scripts) if applicable.
- Review all sections for implicit Windows assumptions and clarify cross-platform applicability.
Site Recovery
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/vmware-physical-mobility-service-overview.md
...-recovery/vmware-physical-mobility-service-overview.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation demonstrates a Windows-first bias in several areas: Windows paths, tools, and examples are consistently presented before their Linux equivalents, and some sections (such as UI-based installation) focus almost exclusively on Windows. Windows-specific tools, directories, and patterns (e.g., C:\Program Files, command prompt, .exe installers) are referenced throughout, sometimes with Linux instructions only appended or less detailed. In some cases, Linux instructions are present but less prominent, and the overall structure and examples assume a Windows-centric environment.
Recommendations
- Present Linux and Windows instructions in parallel or in clearly separated, equally detailed sections, rather than always listing Windows first.
- Include Linux-specific screenshots and UI walkthroughs where applicable, not just Windows UI images.
- Use neutral language and file paths in general guidance (e.g., 'installation directory' instead of 'C:\Program Files...').
- Where Windows-specific tools or services (e.g., VSS) are mentioned, provide equivalent Linux information or clarify if not applicable.
- Ensure Linux command examples are as detailed and prominent as Windows examples, including troubleshooting and advanced options.
- Highlight any differences in agent behavior or requirements between Windows and Linux explicitly, rather than assuming Windows as the default.
- Where possible, provide a summary table or matrix showing parity and differences between Windows and Linux installation and configuration steps.
Site Recovery
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/vmware-azure-enable-replication.md
...icles/site-recovery/vmware-azure-enable-replication.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing PowerShell as the primary automation tool, mentioning Windows-specific features (such as Azure Hybrid Benefit for Windows Server), and omitting Linux-specific instructions or examples. Windows terminology and tools are introduced before or instead of Linux equivalents, and there are no explicit Linux automation or troubleshooting examples.
Recommendations
- Provide equivalent CLI (az CLI) and/or Bash scripting examples alongside PowerShell for automation and management tasks.
- Include Linux-specific considerations, such as supported Linux distributions, requirements for Linux VMs, and troubleshooting steps for common Linux issues.
- Mention Linux licensing and cost-saving options (if any) in parity with the Azure Hybrid Benefit section for Windows.
- Ensure that all references to tools (e.g., PowerShell, Windows Server) are balanced with Linux alternatives or clarifications where applicable.
- Add explicit examples or links for automating replication and failover for Linux VMs, not just Windows.
- Clarify any steps or requirements that differ for Linux VMs, especially regarding agent installation, disk requirements, and failover behavior.
Site Recovery
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/site-recovery-manage-registration-and-protection.md
...ry/site-recovery-manage-registration-and-protection.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation is heavily biased towards Windows environments, specifically focusing on Hyper-V, System Center VMM, and PowerShell scripts. All command-line and scripting examples are provided exclusively in PowerShell, with no mention of Linux-based tools, shell commands, or procedures for unregistering or disabling protection on Linux servers. Windows tools and patterns (e.g., registry edits, Windows services, VMM/Hyper-V management) are referenced throughout, and there is no guidance for Linux-based disaster recovery scenarios.
Recommendations
- Add parallel instructions and examples for unregistering and disabling protection on Linux-based servers, including shell (bash) commands where applicable.
- Include guidance for managing replication and cleanup on Linux VMs, such as how to uninstall the Mobility Service on Linux, or how to clean up configuration files and services.
- Where PowerShell scripts are provided, offer equivalent bash or Python scripts for Linux environments, or explicitly state if certain actions are not required/applicable for Linux.
- Clarify in each section whether the steps are Windows-specific, and provide links or references to Linux-specific documentation if available.
- Ensure that Linux tools and procedures are mentioned alongside Windows tools, not only in separate sections but also in summary tables or comparison charts for parity.
Site Recovery
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/vmware-azure-troubleshoot-vcenter-discovery-failures.md
...tps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/vmware-azure-troubleshoot-vcenter-discovery-failures.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Missing Linux Example
Windows First
Summary
The documentation demonstrates a strong Windows bias by exclusively referencing Windows tools (PsExec, Internet Explorer, Windows command prompt, Windows service names), providing only Windows-based procedures and command examples, and omitting any Linux equivalents or guidance for non-Windows environments. There is no mention of how to perform these troubleshooting steps on Linux-based configuration servers, nor are cross-platform alternatives suggested.
Recommendations
- Provide equivalent troubleshooting steps for Linux-based configuration servers, including relevant commands and tools (e.g., using sudo, systemctl, Linux browsers, or CLI-based proxy configuration).
- Mention and document how to configure proxy settings and service restarts on Linux systems.
- Avoid referencing Windows-only tools (such as PsExec and Internet Explorer) without offering alternatives for other platforms.
- Structure the documentation to address both Windows and Linux environments, or clearly state if only Windows is supported and why.
- Include examples and screenshots for both Windows and Linux where applicable.
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 →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation demonstrates a moderate Windows bias. In sections where both Windows and Linux are mentioned, Windows instructions and troubleshooting steps are presented first and in greater detail. Windows-specific tools and registry modifications are described explicitly, while Linux guidance is brief and lacks equivalent detail or troubleshooting resources. There is also a focus on Windows-specific firewall and RDP configuration, with less emphasis on Linux SSH/firewall specifics.
Recommendations
- Present Linux and Windows instructions in parallel, giving equal detail and prominence to both.
- Include Linux-specific troubleshooting steps and links, similar to the Windows RDP troubleshooting resources.
- Expand Linux guidance for firewall configuration, SSH setup, and post-failover connectivity, including examples for common distributions (e.g., Ubuntu, RHEL).
- Where Windows registry edits are described, provide equivalent Linux commands or configuration file changes if applicable.
- Avoid always listing Windows instructions before Linux; alternate or group by OS for parity.
- Reference Linux tools (e.g., firewalld, ufw, systemctl) where appropriate, not just Windows tools and settings.
Site Recovery
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/avs-tutorial-failback.md
...b/main/articles/site-recovery/avs-tutorial-failback.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by specifically mentioning the behavior of VMware tools for Windows VMs during failover/failback, without addressing Linux VMs or their tooling. There are no examples or notes about Linux VMs, and the only OS-specific guidance is for Windows. This may lead Linux users to feel unsupported or uncertain about the process for their workloads.
Recommendations
- Add explicit information about Linux VMs, including whether VMware tools are handled differently for Linux during failover/failback.
- Include notes or examples for both Windows and Linux VMs where OS-specific behavior may differ.
- If there are no differences for Linux VMs, state this clearly to reassure Linux users.
- Review all OS-specific notes and ensure Linux parity in documentation coverage and troubleshooting guidance.
Site Recovery
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/avs-tutorial-failover.md
...b/main/articles/site-recovery/avs-tutorial-failover.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a subtle Windows bias by referencing Windows-specific tools and documentation before or instead of Linux equivalents. For example, the link to 'Availability set' points to a Windows VM tutorial, and the 'connect to VM' step links to Windows RDP instructions without mentioning or linking to Linux/SSH guidance. There are no explicit Linux command examples or references, and Linux-specific considerations are only mentioned in passing (e.g., longer failover times for Linux VMs) without actionable guidance.
Recommendations
- Provide parallel links and instructions for both Windows and Linux VMs, especially for connectivity (e.g., link to SSH connection documentation for Linux VMs).
- When referencing features like 'Availability set', link to general or Linux-specific documentation as well, not just Windows VM tutorials.
- Include explicit examples or notes for Linux VMs where relevant, such as SSH connectivity, Linux disk/driver considerations, or troubleshooting steps.
- Ensure that any troubleshooting or validation steps cover both Windows (RDP) and Linux (SSH) scenarios equally.
- Review all referenced documentation to ensure Linux parity and avoid defaulting to Windows-first patterns.
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 →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation is heavily focused on Windows-based solutions, specifically referencing Storage Spaces Direct (S2D), Windows Failover Clustering, and related Microsoft technologies. There are no examples, instructions, or considerations for Linux-based clusters or storage solutions. All terminology, diagrams, and operational steps assume a Windows environment, with no mention of Linux equivalents or cross-platform scenarios.
Recommendations
- Include a section addressing whether Linux-based clusters or storage solutions (e.g., Linux MD RAID, LVM, or Pacemaker/Corosync clusters) are supported with Azure Site Recovery, and if so, provide parallel guidance.
- If Linux is not supported for this scenario, explicitly state this limitation early in the documentation.
- Where possible, provide Linux-specific examples or alternatives for cluster setup, storage configuration, and disaster recovery steps.
- Ensure that terminology and diagrams are inclusive of both Windows and Linux environments, or clarify the Windows-specific scope in the introduction.
- Reference Azure documentation for Linux high availability and disaster recovery solutions, if available.
Site Recovery
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/avs-tutorial-replication.md
...ain/articles/site-recovery/avs-tutorial-replication.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by defaulting to a Windows Server 2016 VM for the configuration server, requiring Windows activation, and providing detailed steps for Windows (such as administrator password setup). Linux is only mentioned briefly as an alternative for Mobility Service credentials, with no equivalent setup or activation instructions. There are no Linux-based examples or guidance for using a Linux-based configuration server, and the documentation assumes a Windows environment throughout the setup process.
Recommendations
- Provide explicit instructions and examples for setting up the configuration server on a Linux VM, if supported, or clarify if only Windows is supported.
- Include Linux-specific steps for Mobility Service installation, activation, and troubleshooting, matching the detail given for Windows.
- When referencing user accounts or permissions, provide parallel Linux commands and best practices (e.g., using sudo/root, managing SSH keys).
- If Windows is a strict requirement for the configuration server, state this clearly at the beginning and explain why, but still offer Linux parity for all other steps where possible.
- Ensure screenshots and UI walkthroughs do not assume only Windows environments, and add Linux-relevant visuals or notes where applicable.
Site Recovery
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/azure-stack-site-recovery.md
...in/articles/site-recovery/azure-stack-site-recovery.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation demonstrates a Windows-first bias in several areas: Windows operating systems and procedures are consistently listed before Linux equivalents, Windows-specific tools and registry edits are described in detail (including command prompt and firewall configuration), and there is a heavier emphasis on Windows administrative patterns (e.g., GPO, registry edits, Windows Firewall). While Linux steps are present, they are generally less detailed and appear after Windows instructions. There are also references to Windows-specific tools (e.g., REG ADD, wf.msc) and concepts (GPO) without Linux equivalents or parity in explanation.
Recommendations
- Present Linux and Windows instructions in parallel or side-by-side, rather than always listing Windows first.
- Provide equally detailed Linux examples and commands (e.g., show how to open required firewall ports on Linux using ufw/firewalld/iptables, not just Windows Firewall).
- When referencing Windows tools (e.g., registry edits, GPO), provide Linux equivalents or note when not applicable.
- Include Linux command-line examples for all steps where Windows command-line or GUI steps are given.
- Ensure that screenshots and walkthroughs are balanced between Windows and Linux environments.
- Explicitly mention any differences in process or requirements between Windows and Linux, rather than focusing on Windows defaults.
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 →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows bias in several ways: Windows and PowerShell are mentioned as primary or exclusive methods for tasks (e.g., selecting automation accounts, excluding disks from replication, triggering failover), while Linux equivalents are not provided or are only briefly mentioned. Windows-specific tools and services (such as VSS, ADE for Windows, WSFC-based shared disks, and SQL Server extensions) are described in detail, whereas Linux support is either omitted, less detailed, or explicitly not supported (e.g., no Linux shared disk support). Linux examples and automation methods are largely missing.
Recommendations
- Provide equivalent Linux CLI (az CLI, Bash) examples alongside PowerShell for all automation and scripting tasks.
- Ensure Linux support is clearly documented for all features, or explicitly state limitations with context and alternatives.
- Include Linux-specific guidance and examples for disk encryption, app-consistent snapshots, and failover automation.
- Balance the order of presentation so that Linux and Windows are treated equally (e.g., mention both in feature support lists, not just Windows first).
- Where Windows tools (like VSS or PowerShell) are referenced, add Linux alternatives or note if none exist.
- Add more detail and examples for Linux scenarios, such as using custom scripts for app-consistency, and clarify support for Linux shared disks.
Site Recovery
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/azure-to-azure-how-to-enable-replication-ade-vms.md
...ry/azure-to-azure-how-to-enable-replication-ade-vms.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation exhibits a Windows bias by providing only PowerShell-based scripting examples (which are native to Windows), referencing the use of the Windows PowerShell application explicitly, and not offering equivalent instructions or scripts for Linux environments (such as Bash or Azure CLI). The only automation script provided is a PowerShell script, and there are no Linux-specific examples or guidance for users managing Azure VMs from Linux systems. Additionally, the documentation notes feature limitations for Linux (ADE without Microsoft Entra ID), but does not provide Linux-centric workflows or troubleshooting.
Recommendations
- Provide equivalent Bash or Azure CLI scripts for key management and replication tasks, alongside the PowerShell examples.
- Explicitly mention how Linux administrators can perform the same operations, including command-line steps that work on Linux/macOS.
- Where automation scripts are referenced (e.g., CopyKeys), offer a cross-platform version or alternative (such as an Azure CLI script or REST API example).
- Include screenshots or walkthroughs from Linux environments (e.g., Azure Cloud Shell in Bash mode) where relevant.
- Clarify any differences in workflow or requirements for Linux VMs, and ensure Linux parity in step-by-step instructions.
Site Recovery
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/delete-vault.md
...-docs/blob/main/articles/site-recovery/delete-vault.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation provides only PowerShell-based command-line instructions for deleting a Recovery Services vault, with no equivalent examples or guidance for Linux users (e.g., using Azure CLI or Bash). The focus on PowerShell and lack of cross-platform command-line options demonstrates a Windows-centric bias.
Recommendations
- Add equivalent Azure CLI (az) command examples for deleting a Recovery Services vault, as Azure CLI is cross-platform and widely used on Linux and macOS.
- Explicitly mention that PowerShell examples are for Windows and provide Bash/Azure CLI alternatives for Linux/macOS users.
- Where possible, structure command-line sections to present both PowerShell and Azure CLI examples side by side.
- Review referenced links to ensure they also provide cross-platform instructions, or add notes if they are Windows-specific.
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 →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation is heavily biased toward Windows environments. All examples and instructions are provided exclusively for Windows Server (2012 R2/2016), with explicit requirements for Windows-only tools (PowerShell, .NET Framework, Visual C++ Redistributable, Microsoft Excel). There are no Linux equivalents or cross-platform instructions, and the documentation assumes the user is operating in a Windows ecosystem throughout.
Recommendations
- Provide explicit statements about platform support (e.g., clarify if the tool is Windows-only or if Linux/MacOS are unsupported).
- If possible, develop and document a cross-platform version of the deployment planner tool, or provide alternatives for Linux users.
- Include Linux-based examples or instructions, or clearly state that Linux is not supported.
- Offer guidance for users who may be managing mixed environments (e.g., how to export/import data for analysis on non-Windows systems).
- If PowerShell is required, mention if PowerShell Core (cross-platform) is supported, and provide examples for Linux/macOS if applicable.
- For report generation, suggest open-source alternatives to Microsoft Excel (e.g., LibreOffice Calc) if possible, or provide output in formats that are not Excel-dependent.
Site Recovery
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/azure-to-azure-troubleshoot-network-connectivity.md
...ry/azure-to-azure-troubleshoot-network-connectivity.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by referencing Windows tools and patterns first (e.g., Internet Explorer for proxy autodetection), providing detailed steps or context for Windows before Linux, and omitting Linux-specific troubleshooting examples (such as command-line checks or Linux-native tools). While Linux paths are mentioned for proxy configuration, there is a lack of parity in example depth and troubleshooting steps for Linux environments.
Recommendations
- Provide Linux-first or parallel Linux examples alongside Windows instructions, especially for troubleshooting steps (e.g., how to check DNS connectivity using Linux commands like dig or nslookup).
- Include Linux-native tools and patterns (e.g., mention /etc/resolv.conf for DNS, use curl or wget for connectivity tests, reference Linux firewall tools like iptables or firewalld).
- When referencing proxy autodetection, explain the Linux mechanism in equal detail as Windows (e.g., how the agent reads /etc/environment, and how to verify or set it).
- Add screenshots or command-line snippets for Linux environments where Windows GUI screenshots are provided.
- Ensure that all configuration file examples (like ProxyInfo.conf) include both Linux and Windows file paths and context, and clarify any OS-specific differences in behavior or troubleshooting.