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 526-550 of 864 flagged pages
Site Recovery
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/hyper-v-deployment-planner-run.md
...ticles/site-recovery/hyper-v-deployment-planner-run.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation is heavily biased towards Windows environments. All examples use Windows-style paths (e.g., E:\...), reference Windows-native tools (Notepad), and assume the use of the ASRDeploymentPlanner.exe executable, which is a Windows binary. There is no mention of running the tool or equivalent operations on Linux, nor are there any Linux shell or PowerShell alternatives. The documentation assumes the user is operating in a Windows/Hyper-V ecosystem, with no guidance for Linux administrators.
Recommendations
- Explicitly state if the tool is only supported on Windows. If cross-platform support exists, add Linux-specific instructions and examples.
- Provide Linux/Unix path examples (e.g., /home/user/Hyper-V_ProfiledData) alongside Windows paths.
- If the tool can be run under Wine or Mono on Linux, document the process.
- Replace or supplement references to Notepad with cross-platform editors (e.g., nano, vim, gedit) or generic instructions (e.g., 'open the file in a text editor').
- Clarify any prerequisites or limitations for non-Windows users.
- If the tool is Windows-only, suggest alternative approaches or tools for Linux environments where possible.
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 →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates a Windows-first bias by presenting Windows tools (Resource Monitor, Performance Monitor) in greater detail, with step-by-step instructions and screenshots, before mentioning Linux tools. The Linux section is brief, lacks screenshots, and does not provide equivalent depth or usage examples. Windows-specific tools are highlighted, and there is an absence of parity in the guidance for Linux users.
Recommendations
- Provide step-by-step instructions for using Linux tools (iotop, iostat), including example command outputs and explanations of key metrics.
- Include screenshots or terminal output for Linux tools, similar to the visuals provided for Windows tools.
- Mention additional Linux tools that can be used for churn monitoring, such as 'dstat', 'glances', or 'atop', to match the breadth of Windows tool coverage.
- Ensure that the order of presentation alternates or is parallel (e.g., present Windows and Linux tools side-by-side) to avoid a Windows-first impression.
- Add links to official documentation or tutorials for the Linux tools, similar to the 'Learn more' link for Performance Monitor.
Site Recovery
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/physical-azure-set-up-source.md
...articles/site-recovery/physical-azure-set-up-source.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by referencing Windows-specific requirements (such as .NET Framework and Windows Time Service), providing only Windows-centric instructions and links, and omitting Linux-specific setup steps or troubleshooting. There are no examples or guidance tailored for Linux-based configuration servers, despite the article's claim to support both Windows and Linux physical servers.
Recommendations
- Include explicit instructions and examples for setting up the configuration server on Linux, if supported.
- Provide Linux-specific prerequisites (e.g., required packages, system services, time synchronization methods like chrony or ntpd).
- Reference Linux equivalents for tools and concepts (e.g., instead of only linking to Windows Time Service, mention how to sync time on Linux).
- Clarify whether the configuration server can be installed on Linux or if it is Windows-only; if the latter, state this clearly at the beginning.
- Add troubleshooting steps and common issues relevant to Linux environments.
Site Recovery
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/site-recovery-deployment-planner-history.md
...e-recovery/site-recovery-deployment-planner-history.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation shows a mild Windows bias: Windows operating systems are often mentioned first or exclusively in version notes, and Windows-specific tools or patterns (such as Excel reports) are referenced without Linux alternatives. While Linux support is mentioned and expanded over time, there are no Linux-specific usage examples, tools, or guidance, and the documentation assumes familiarity with Windows environments.
Recommendations
- When listing supported operating systems, alternate the order or group Windows and Linux together to avoid always listing Windows first.
- Provide equivalent Linux tooling or usage guidance (e.g., mention how to view or process reports on Linux, such as using LibreOffice or command-line tools).
- Include Linux-specific examples or notes where relevant, such as how to run the Deployment Planner or interpret its output on Linux systems.
- Explicitly mention any Linux limitations or workarounds, not just Windows ones.
- If the Deployment Planner is Windows-only, clearly state this early and provide recommendations or alternatives for Linux users.
Site Recovery
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/physical-manage-configuration-server.md
.../site-recovery/physical-manage-configuration-server.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation is heavily biased towards Windows environments. All operating system requirements, installation instructions, command-line examples, and troubleshooting steps are exclusively for Windows Server. There are no references to Linux support, tools, or equivalent commands. PowerShell is used for scripting and automation, and Windows-specific tools such as Control Panel and Registry Editor are referenced throughout. No Linux installation, management, or command-line examples are provided.
Recommendations
- Clearly state if Linux is unsupported for the configuration server; if it is supported, add equivalent Linux prerequisites, installation, and management instructions.
- Provide Linux command-line examples (e.g., bash scripts) for installation, registration, and proxy configuration.
- Include Linux-specific troubleshooting steps and references to Linux tools (e.g., systemctl, cron, /etc configuration files) where applicable.
- If only Windows is supported, add a prominent note at the top of the documentation clarifying this to avoid confusion.
- Where PowerShell is used, provide bash or shell script equivalents for Linux environments if supported.
- Reference Linux package management and service management tools where relevant (e.g., apt, yum, systemctl).
Site Recovery
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/physical-azure-disaster-recovery.md
...cles/site-recovery/physical-azure-disaster-recovery.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page, while claiming to cover both Windows and Linux physical servers, demonstrates a Windows-first bias. Windows-specific instructions (such as registry edits and use of REG CLI commands) are provided in detail, while equivalent Linux instructions are either missing or only briefly mentioned (e.g., 'the account should be root'). There are no Linux command-line examples or troubleshooting steps, and Windows tools and patterns (like registry edits) are described without Linux parity.
Recommendations
- Provide equivalent Linux command-line instructions and examples wherever Windows-specific steps (such as registry edits or CLI commands) are given.
- Include Linux-specific troubleshooting tips, such as how to verify or configure required settings (e.g., SSH configuration, sudo/root access, time synchronization with ntpd/chrony).
- When describing account preparation, detail the steps for Linux (e.g., ensuring root SSH access, required permissions, and any SELinux/AppArmor considerations).
- Mention Linux tools and patterns (such as editing /etc/sudoers, using systemctl for service management, or checking logs in /var/log) alongside Windows tools.
- Ensure that all screenshots and UI walkthroughs clarify any differences or additional steps required for Linux servers, if applicable.
- Structure instructions so that Linux and Windows steps are presented with equal prominence, ideally side-by-side or in clearly separated sections.
Site Recovery
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/physical-server-azure-architecture-modernized.md
...overy/physical-server-azure-architecture-modernized.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page, while stating support for both Windows and Linux physical servers, demonstrates a Windows bias. Windows terminology (such as VSS and app-consistent snapshots) is used exclusively in technical explanations, and there are no Linux-specific examples or equivalent tooling/processes described. The documentation assumes Windows patterns (e.g., VSS for snapshots), and does not mention how app-consistent snapshots or similar features are handled on Linux. There are no Linux command-line or process examples, and Windows-centric tools and concepts are referenced without Linux parity.
Recommendations
- Explicitly describe how app-consistent snapshots are handled for Linux servers, including any limitations or alternative mechanisms (e.g., pre/post scripts, fsfreeze, LVM snapshots).
- Provide Linux-specific examples or instructions where relevant, such as manual installation of the Mobility Service on Linux, or how to monitor replication health from a Linux perspective.
- Clarify any differences in failover/failback, snapshotting, or recovery processes between Windows and Linux servers.
- Include references to Linux tools or commands (e.g., shell commands, systemd services) where Windows tools or concepts (like VSS) are mentioned.
- Ensure that all technical explanations and tables include both Windows and Linux perspectives, or clearly state when a feature is Windows-only.
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 →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows bias, particularly in the section on configuring the Microsoft monitoring agent for collecting churn and upload rate logs. Only Windows agent installation steps are provided, and the instructions and screenshots reference Windows-specific tools and UI paths (e.g., 'Windows Servers', 'Windows Agent', 'Windows Performance Counters'). There is no mention of Linux agent installation or equivalent steps for Linux-based Process Servers, nor are Linux-specific monitoring scenarios or examples provided.
Recommendations
- Add parallel instructions and screenshots for installing and configuring the Microsoft monitoring agent on Linux-based Process Servers, including download links, workspace configuration, and any required dependencies.
- Include steps for configuring performance counters or their equivalents on Linux, referencing the appropriate object and counter names for Linux environments.
- Explicitly state whether Linux-based Process Servers are supported for churn/upload rate monitoring; if not, clarify this limitation.
- Provide example queries and troubleshooting tips for Linux-based replicated machines, ensuring parity with the Windows-focused examples.
- Where UI navigation is described (e.g., 'Connected Sources > Windows Servers'), add the equivalent Linux navigation or clarify the differences.
- Ensure that all monitoring and alerting scenarios are covered for both Windows and Linux workloads, or clearly document any feature gaps.
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 →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a Windows bias by providing detailed registry modification instructions and CLI commands only for Windows systems, while Linux instructions are minimal and lack equivalent detail or examples. Windows-specific tools and patterns (e.g., registry edits, references to Windows Time Service) are mentioned explicitly, while Linux alternatives are not described. The order of presentation also prioritizes Windows instructions before Linux, and there are no Linux command-line examples or troubleshooting tips.
Recommendations
- Provide equivalent Linux command-line examples for all steps where Windows registry or CLI commands are given (e.g., show how to prepare the Linux system for Mobility service installation, such as required user/group permissions or configuration changes).
- Include Linux-specific troubleshooting steps and references (e.g., how to check and synchronize time on Linux using ntpd or chrony, not just referencing Windows Time Service).
- When describing account preparation, detail the steps for both Windows and Linux equally, including any required sudoers configuration or SSH setup for Linux.
- Present Windows and Linux instructions in parallel or in clearly separated sections, rather than always listing Windows first.
- Reference Linux documentation and tools (e.g., systemd, journalctl, SSH, Linux firewall configuration) where appropriate, alongside Windows equivalents.
Site Recovery
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/shared-disk-support-matrix.md
...n/articles/site-recovery/shared-disk-support-matrix.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page exclusively references Windows workloads, specifically Windows Server Failover Clustering (WSFC), and does not mention or provide examples for Linux-based clustering solutions or workloads. There is no information about Linux support, tools, or equivalent clustering patterns, despite the 'linux-related-content' tag.
Recommendations
- Explicitly state whether Linux workloads and clustering solutions (e.g., Pacemaker, Corosync) are supported or unsupported for shared disk disaster recovery.
- If Linux is supported, add a dedicated section outlining supported Linux distributions, clustering configurations, and any required tools or patterns.
- Provide parity in examples and tables by including Linux alongside Windows where applicable.
- If Linux is not supported, clearly document this limitation to avoid ambiguity for Linux users.
Site Recovery
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/replication-appliance-support-matrix.md
.../site-recovery/replication-appliance-support-matrix.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation exclusively references Windows Server as the supported operating system for the replication appliance, with all configuration, folder paths, and group policy settings specific to Windows. There are no mentions of Linux support, Linux equivalents, or cross-platform considerations. All antivirus exclusions and operational details are Windows-centric, and Windows administrative tools and patterns (e.g., group policies, IIS, Windows folder paths) are referenced without Linux alternatives.
Recommendations
- Explicitly state if Linux-based appliances are unsupported; if Linux is supported, add equivalent requirements, folder paths, and configuration steps for Linux systems.
- Provide Linux-specific examples for antivirus exclusions, such as typical installation paths and exclusion syntax for common Linux antivirus solutions.
- If only Windows is supported, clarify this early in the documentation to set expectations for non-Windows users.
- If future support for Linux is planned, include a roadmap or note for cross-platform parity.
- Where possible, use neutral language (e.g., 'the appliance OS must be Windows Server 2022') and avoid implying Windows is the only platform unless that is a hard requirement.
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-based Active Directory and DNS disaster recovery, with all examples, tools, and troubleshooting steps referencing Windows Server, Windows command-line tools (e.g., dcdiag, nltest, dnscmd), Windows registry edits, and Windows-specific concepts (FSMO, SYSVOL, DFSR, FRS). There are no examples or guidance for Linux-based domain controllers (e.g., Samba AD DC) or DNS servers, nor are cross-platform considerations addressed. The documentation assumes the use of Windows Server throughout.
Recommendations
- Add sections or notes for environments using Samba Active Directory Domain Controllers on Linux, including replication and failover considerations.
- Provide equivalent Linux-based DNS server disaster recovery steps (e.g., BIND, dnsmasq), including example commands for zone backup and restoration.
- Include Linux command-line equivalents for key operations (e.g., checking DNS/AD health, updating DNS records) where possible.
- Clarify early in the document that the guidance is specific to Windows Server AD/DNS, and provide links or references for Linux-based alternatives.
- If Azure Site Recovery supports Linux-based AD/DNS, explicitly document the supported scenarios and any differences in procedure.
Site Recovery
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/site-recovery-create-recovery-plans.md
...s/site-recovery/site-recovery-create-recovery-plans.md
High Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows Tools
Windows First
Summary
The documentation page demonstrates a bias toward Windows environments by focusing on Windows-centric tools (such as System Center VMM and Windows file share paths), providing script integration examples only for VMM (a Windows technology), and omitting explicit Linux or cross-platform scripting examples. There is no mention of Linux-based automation, shell scripts, or Linux-specific considerations, and the only scripting example uses a Windows UNC path and PowerShell script (.PS1).
Recommendations
- Include examples of integrating Linux scripts (e.g., Bash scripts) into recovery plans, especially for VMware and physical machine scenarios.
- Document how to use Linux-based automation tools (such as Azure Automation with Python or Bash runbooks) in recovery plans.
- Provide explicit instructions or examples for adding scripts located on Linux servers, including path formats and authentication considerations.
- Mention Linux support and any differences in scripting or automation for Linux VMs in recovery plans.
- Ensure parity in documentation by listing both Windows and Linux options where applicable, and avoid presenting Windows tools or patterns exclusively or first.
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
Windows Tools
Missing Linux Example
Summary
The documentation is heavily oriented towards Windows environments, specifically referencing Windows Server, Active Directory, SQL Server, and Dynamics AX components that are Windows-only. All examples, prerequisites, and recovery steps assume a Windows-based deployment, with no mention of Linux-based alternatives or guidance for non-Windows environments. Tools and patterns (e.g., Azure Virtual Machine Readiness Assessment, Active Directory replication, SQL Server replication) are exclusively Windows-centric.
Recommendations
- Explicitly state that Dynamics AX is a Windows-only application, if that is the case, to clarify the scope for readers.
- If Linux-based deployments or components are possible (e.g., for supporting services), provide equivalent guidance or explicitly mention their (lack of) support.
- Add notes or sections addressing what steps, if any, are applicable for Linux VMs or mixed-OS environments, especially for networking, failover, and recovery plan configuration.
- Include examples or links for disaster recovery of Linux-based workloads with Azure Site Recovery, to provide parity and context for Linux administrators.
- Where Windows-specific tools or patterns are mentioned (e.g., Active Directory, SQL Server), suggest Linux-compatible alternatives if available, or clarify that only Windows is supported for these components.
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 →
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, with all examples, scripts, and terminology centered around Windows tools and patterns. There are no Linux equivalents or cross-platform considerations, and all automation and scripting references (such as DNS update scripts) are provided only in PowerShell. The article does not mention or provide guidance for Linux-based web servers or cross-platform disaster recovery scenarios.
Recommendations
- Include equivalent guidance and examples for Linux-based web applications (e.g., Apache, Nginx) and their disaster recovery using Azure Site Recovery.
- Provide Linux shell script examples for automation tasks such as DNS updates, connection string changes, and site binding updates.
- Mention and link to Azure Site Recovery documentation for Linux workloads, if available.
- Clarify in the introduction that the article is specific to Windows/IIS, and provide references or links to Linux-focused disaster recovery documentation.
- When discussing scripting and automation, offer both PowerShell and Bash (or Python) script samples where applicable.
- Discuss Linux-specific considerations for network configuration, certificate management, and application failover.
Site Recovery
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/site-recovery-deployment-planner.md
...cles/site-recovery/site-recovery-deployment-planner.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation exhibits a strong Windows bias: all instructions, requirements, and examples assume the use of Windows Server or Windows PC. There is no mention of Linux support, nor are any Linux equivalents or alternatives provided for running the Deployment Planner tool, installing prerequisites, or generating reports. The tool itself appears to be Windows-only, and all references to system requirements, file paths, and dependencies are Windows-specific.
Recommendations
- Explicitly state in the prerequisites and download sections whether Linux is supported or not. If not, clarify this limitation early in the documentation.
- If feasible, provide a Linux-compatible version of the Deployment Planner tool, or offer guidance for running the tool on Linux (e.g., via Wine or a container).
- Include Linux-based examples for downloading, extracting, and running the tool, or clearly state that such workflows are not supported.
- List Linux system requirements and dependencies if/when a Linux version becomes available.
- Where possible, use cross-platform language (e.g., 'machine' instead of 'Windows server') and provide parity in instructions for both Windows and Linux environments.
Site Recovery
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/site-recovery-ipconfig-cmdlet-parameter-deprecation.md
...ttps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/site-recovery-ipconfig-cmdlet-parameter-deprecation.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation exclusively uses Azure PowerShell cmdlets and provides only PowerShell script examples, which are native to Windows environments. There are no examples or guidance for users who may use Azure CLI, Bash, or other cross-platform tools commonly preferred on Linux or macOS. The documentation assumes the user is operating in a Windows-centric scripting environment.
Recommendations
- Include equivalent Azure CLI (az) commands and examples for all remediation steps and scenarios.
- Provide Bash script examples alongside PowerShell to support Linux and macOS users.
- Explicitly mention cross-platform options and clarify whether the cmdlets can be used from non-Windows environments (e.g., PowerShell Core on Linux/macOS).
- Reference documentation or guides for performing the same tasks using Azure Portal or REST API for broader accessibility.
Site Recovery
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/site-recovery-sharepoint.md
...ain/articles/site-recovery/site-recovery-sharepoint.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Powershell Heavy
Windows Tools
Summary
The documentation demonstrates a strong Windows bias. All examples and guidance assume SharePoint is running on Windows Server, with explicit references to Windows Server, SharePoint PowerShell cmdlets, and Windows-centric tools (e.g., DFSR, AzCopy). There are no examples or mentions of Linux-based SharePoint deployments or equivalent Linux tools/workflows. PowerShell is the only scripting environment referenced for automation, and all recovery steps are described in the context of Windows environments.
Recommendations
- Include explicit statements about whether Linux-based SharePoint deployments are supported or not, and provide guidance for Linux if applicable.
- If SharePoint on Linux is not supported, clarify this early in the documentation to set expectations.
- Where possible, provide cross-platform alternatives for automation (e.g., Azure CLI, Bash scripts) alongside PowerShell examples.
- Mention Linux equivalents for tools like DFSR (e.g., rsync, lsyncd) and AzCopy (which is cross-platform, but show Linux usage).
- If any steps are Windows-only (such as using SharePoint PowerShell cmdlets), clearly indicate this and suggest alternative approaches for non-Windows environments if feasible.
- Ensure that any references to file paths, scripts, or administrative tools are inclusive of both Windows and Linux conventions where possible.
Site Recovery
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/site-recovery-failover.md
.../main/articles/site-recovery/site-recovery-failover.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation exhibits a Windows-first bias, particularly in the 'Prepare on-premises to connect after failover' section, where Windows VM instructions are more detailed and appear before Linux instructions. Windows-specific tools and settings (e.g., Windows Firewall, RDP, WinHTTP proxy, SAN policy) are mentioned, while Linux instructions are brief and lack equivalent detail. There are also missing Linux-specific troubleshooting steps and configuration examples compared to the Windows sections.
Recommendations
- Provide Linux instructions with equal detail and prominence as Windows instructions, including firewall configuration (e.g., iptables, firewalld, ufw), SSH service management, and handling of static routes or proxies on Linux.
- Include Linux-specific troubleshooting steps for post-failover connectivity, similar to the linked Windows RDP troubleshooting guide.
- Present Windows and Linux instructions in parallel or side-by-side tables to avoid the perception of prioritizing one platform over the other.
- Mention Linux equivalents for Windows-specific terms (e.g., explain how to check for pending updates or SAN policy equivalents on Linux, if relevant).
- Ensure that automation and scripting examples (if any) are provided for both PowerShell (Windows) and Bash/Shell (Linux) environments.
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 subtle Windows bias. While it mentions support for both Windows and Linux, Windows-centric technologies (such as Windows Server Failover Clusters, SQL Server Always On, and AWS Windows instances) are highlighted with specific examples and features. Linux is only mentioned generically, with no Linux-specific workloads, tools, or scenarios detailed. There are no Linux command-line or tool examples, and Windows technologies are described first or exclusively in several sections.
Recommendations
- Include Linux-specific examples and scenarios, such as protecting Linux-based clustered applications (e.g., Pacemaker, Corosync) or open-source databases (e.g., MySQL, PostgreSQL) in the 'Workload replication' and 'Shared disk' sections.
- Provide parity in feature descriptions by mentioning Linux equivalents where Windows technologies are referenced (e.g., discuss Linux HA clusters alongside Windows Server Failover Clusters).
- Add links to documentation or quickstarts for Linux VM replication and recovery, not just Windows or VMware scenarios.
- Where scripts or automation are referenced, include examples or notes for Bash/shell scripts in addition to PowerShell.
- Explicitly state support for and provide guidance on Linux-specific disaster recovery best practices and tools.
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 in a Windows environment, referencing Windows Server Failover Cluster, Storage Spaces Direct, and SIOS DataKeeper (Windows-centric tools), and omitting any mention or examples for Linux-based SAP deployments or clustering solutions. No Linux-specific guidance, tools, or parity examples are provided.
Recommendations
- Include equivalent guidance and examples for SAP NetWeaver deployments on Linux (e.g., SUSE or Red Hat), which are common in SAP environments.
- Mention and provide instructions for Linux-based clustering solutions such as Pacemaker/Corosync, and NFS for /sapmnt shares.
- When discussing high availability and disaster recovery, present both Windows and Linux options side by side, or clarify applicability to both platforms.
- Reference Linux-based tools and patterns (e.g., native Linux file shares, Linux HA clusters) where appropriate.
- If certain features are only supported on Windows, explicitly state this and provide a roadmap or alternatives for Linux users.
Site Recovery
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/site-recovery-test-failover-to-azure.md
.../site-recovery/site-recovery-test-failover-to-azure.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by providing more detailed and prioritized instructions for Windows VMs, including explicit references to Windows Firewall, RDP, and SAN policy settings. Windows-specific tools and troubleshooting steps are mentioned before their Linux equivalents, and Linux guidance is less detailed. There are no command-line examples for Linux (e.g., SSH configuration), and the troubleshooting section links to Windows-centric resources.
Recommendations
- Provide Linux instructions and examples alongside Windows instructions, not after them.
- Include Linux-specific troubleshooting links and resources, similar to those provided for Windows.
- Offer parity in detail for Linux VM preparation (e.g., systemd/service commands to enable SSH, firewall-cmd/iptables examples).
- Mention Linux tools and patterns (e.g., SSH, UFW/firewalld) explicitly, not just generically as 'firewall rules'.
- Add example commands for both Windows (PowerShell) and Linux (bash/CLI) where configuration is required.
- Ensure that Linux and Windows sections are equally detailed and visible, possibly using side-by-side or tabbed formatting.
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 bias in several areas: troubleshooting steps and scripts are provided only for Windows (not Linux) in critical sections, PowerShell scripts are referenced without Linux equivalents, and Windows tools (such as PsExec and Internet Explorer) are suggested for resolving issues even in Linux-related scenarios. Linux troubleshooting steps are either missing or only briefly mentioned, and Windows is often addressed before Linux, even in mixed or Linux-specific contexts.
Recommendations
- Provide equivalent Linux command-line instructions and scripts wherever Windows PowerShell scripts are referenced (e.g., for driver/service startup type changes).
- When referencing tools like PsExec or Internet Explorer for proxy troubleshooting, offer Linux-native alternatives (such as using curl, wget, or editing proxy settings via command line).
- Ensure that Linux troubleshooting steps are as detailed and actionable as Windows steps, especially in sections that currently only mention Windows.
- Where both Windows and Linux are supported, present both sets of instructions side-by-side or clearly labeled, rather than defaulting to Windows-first.
- Include more Linux-specific error scenarios and their resolutions, matching the depth provided for Windows.
- Review and update screenshots and UI navigation steps to clarify any differences for Linux VMs where applicable.
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 →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation page exclusively provides PowerShell-based examples and scripts for integrating Azure Automation runbooks into Site Recovery recovery plans. There are no examples or guidance for users who may prefer or require Linux-based scripting (e.g., Bash, Python) or cross-platform approaches. All module references and code samples are tailored to the Azure PowerShell module ecosystem, which is most familiar to Windows users. There is no mention of Linux tools, shell scripting, or how to achieve similar automation using non-Windows environments.
Recommendations
- Provide equivalent examples using Bash or Python runbooks, especially for common automation tasks.
- Mention and link to documentation for cross-platform Azure Automation runbooks (e.g., Python, PowerShell Core).
- Clarify which steps or scripts are Windows-specific and offer Linux alternatives where possible.
- Include guidance on using Azure CLI (az) commands in runbooks for users on Linux or macOS.
- Reference the ability to use hybrid worker groups that can run scripts on Linux machines, and provide examples.
Site Recovery
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/vmware-azure-deploy-configuration-server.md
...e-recovery/vmware-azure-deploy-configuration-server.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a Windows bias by exclusively describing deployment and configuration steps for a Windows Server-based configuration server. All instructions, screenshots, and file paths (e.g., C:\Temp\ASRSetup) are Windows-specific. There are no Linux-based deployment options, examples, or guidance, despite the fact that VMware environments can support both Windows and Linux VMs. The documentation assumes the configuration server VM runs Windows Server 2016, and all tooling and manual steps (such as MySQL installation) are described only for Windows environments.
Recommendations
- Provide explicit guidance or clarify whether a Linux-based configuration server is supported or not. If supported, add parallel Linux deployment instructions.
- Include Linux-specific examples for steps such as credential entry, MySQL installation, and file paths.
- If only Windows is supported for the configuration server, state this clearly at the beginning of the documentation to set expectations for Linux users.
- Wherever possible, mention both Windows and Linux procedures for tasks like mobility service installation on source VMs.
- Add troubleshooting and FAQ entries relevant to Linux environments if supported.