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 776-800 of 864 flagged pages
Site Recovery
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/site-recovery-citrix-xenapp-and-xendesktop.md
...recovery/site-recovery-citrix-xenapp-and-xendesktop.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Summary
The documentation focuses exclusively on Citrix XenDesktop/XenApp, which are traditionally Windows-centric technologies, and does not mention or provide guidance for Linux-based deployments or alternatives. There are no examples or references to Linux tools, commands, or equivalent disaster recovery scenarios, indicating a Windows-first and Linux-omitting bias.
Recommendations
- Include explicit statements about the applicability (or lack thereof) of the guidance to Linux-based Citrix deployments, if any exist.
- If Linux-based Citrix solutions are supported or possible, provide parallel instructions or references for Linux environments.
- Mention alternative disaster recovery strategies or tools for Linux workloads, or clarify if the guidance is strictly limited to Windows.
- Ensure future documentation includes cross-platform considerations, even if the primary audience is Windows-focused.
Create Pull Request
Site Recovery
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/quickstart-create-vault-terraform.md
...les/site-recovery/quickstart-create-vault-terraform.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell instructions for verifying results, but the PowerShell tab is given equal prominence to the CLI, and PowerShell is a Windows-centric tool. There are no explicit Linux shell examples (e.g., Bash), nor is there mention of Linux-specific tooling or patterns. The CLI instructions are generic and cross-platform, but the inclusion and parity of PowerShell examples may suggest a slight Windows bias, especially for users unfamiliar with PowerShell or working primarily in Linux environments.
Recommendations
- Clarify that Azure CLI commands work on Windows, Linux, and macOS, and highlight Bash usage for Linux users.
- Add explicit Bash shell examples for Linux users, such as using export instead of variable assignment with $() for environment variables.
- Consider listing Azure CLI (cross-platform) instructions before PowerShell to emphasize platform neutrality.
- Note that PowerShell is available on Linux, but most Linux users prefer Bash; provide guidance accordingly.
- Where possible, avoid assuming the use of Windows-specific tools or shells unless necessary.
Site Recovery
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/vmware-azure-install-linux-master-target.md
...e-recovery/vmware-azure-install-linux-master-target.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows Reference
Summary
The documentation is focused on Linux master target installation, but it contains several references to Windows-specific tools and paths, such as copying installer files and passphrases from Windows directories (e.g., C:\Program Files (x86)\Microsoft Azure Site Recovery\... and C:\ProgramData\Microsoft Azure Site Recovery\...). There are no Linux-native alternatives or parity instructions for these steps, and the process server and configuration server are implicitly assumed to be running on Windows. This creates friction for Linux-centric environments and suggests a Windows-first operational bias.
Recommendations
- Provide instructions for accessing installer files and passphrases from a Linux-based process server or configuration server, if supported.
- Clarify whether the process server and configuration server must be Windows, or document Linux alternatives if available.
- Offer Linux-native paths and commands for all cross-server file transfers, not just Windows paths.
- Add explicit guidance for users operating in all-Linux environments, including troubleshooting and file access.
- Ensure parity in examples and screenshots for both Windows and Linux administrative workflows.
Site Recovery
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/site-recovery-whats-new.md
...main/articles/site-recovery/site-recovery-whats-new.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation page is generally balanced in listing both Windows and Linux support in update notes, especially for supported distros and kernels. However, Windows versions and appliances are often mentioned before Linux equivalents in update lists, and Windows-specific tooling (e.g., 'Site Recovery Provider', 'Recovery Services agent', 'Windows Server as appliance') is referenced without Linux equivalents or alternatives. There are no command-line examples, but the update tables and feature lists tend to prioritize Windows terminology and releases.
Recommendations
- Ensure that Linux appliances, agents, and tooling are described with equal detail and prominence as Windows equivalents.
- Where Windows versions or features are listed, ensure Linux equivalents are mentioned in parallel, not as a secondary note.
- Add explicit references to Linux management tools or agent installation/upgrade processes if applicable.
- If there are platform-specific configuration steps or tools, provide examples for both Windows and Linux environments.
- Review update tables and feature lists to alternate or balance the order of Windows and Linux entries, or group by platform for clarity.
Site Recovery
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/vmware-azure-set-up-process-server-azure.md
...e-recovery/vmware-azure-set-up-process-server-azure.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows Tools
Summary
The documentation page implicitly assumes the process server VM will be Windows-based, as it requests 'User name' and 'Password' with Admin permissions (a Windows-centric pattern), and does not mention Linux as a supported OS for the process server. There are no examples or instructions for deploying or managing a Linux-based process server, nor are Linux-specific tools or patterns referenced.
Recommendations
- Explicitly state whether Linux is supported as a process server OS. If so, provide parallel instructions for deploying a Linux-based process server.
- Include examples of both Windows and Linux process server deployments, with appropriate credential and permission guidance for each.
- Reference Linux-native tools and patterns (e.g., SSH keys for authentication, sudo for privilege escalation) where relevant.
- Clarify any OS-specific requirements or limitations in the prerequisites section.
- Ensure screenshots and UI instructions do not assume a Windows-only context if Linux is supported.
Site Recovery
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/vmware-azure-set-up-replication-tutorial-modernized.md
...ttps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/vmware-azure-set-up-replication-tutorial-modernized.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation mentions both Linux and Windows OS in the context of providing credentials for Mobility Service installation, but does not provide any Linux-specific examples, commands, or troubleshooting steps. Windows is referenced first and more explicitly (e.g., 'Windows OS, a user account with admin privileges'), while Linux is only mentioned as 'provide the root credentials.' There are no Linux CLI or shell commands, nor are there references to Linux-specific tools or patterns. The documentation does not show parity in examples or guidance for Linux environments.
Recommendations
- Provide explicit Linux examples for manual Mobility Service installation, such as shell commands or package installation steps.
- Include troubleshooting steps or common issues for Linux VMs, such as SELinux, firewall, or permissions.
- Mention Linux-specific deployment automation options (e.g., Ansible, shell scripts) alongside Configuration Manager.
- Ensure that Linux is referenced equally and not only as a secondary note to Windows.
- Add screenshots or walkthroughs for Linux VM configuration in the Azure Site Recovery process.
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
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation exhibits a subtle Windows bias by referencing Windows-specific concepts and links before or instead of Linux equivalents. For example, the 'Availability set' link points to a Windows VM tutorial, and the instructions for connecting to failed-over VMs mention RDP (Windows) before SSH (Linux) without providing explicit Linux connection examples or links. There are no Linux-specific instructions or examples, despite mentioning Linux VMs in the context of failover times.
Recommendations
- Provide parallel Linux examples and links where Windows-specific instructions or links are given (e.g., link to both Windows and Linux VM availability set documentation).
- When discussing connecting to failed-over VMs, include explicit SSH instructions and a link to the Azure Linux VM SSH connection documentation alongside the RDP/Windows link.
- Where relevant, clarify any differences in failover or recovery steps for Linux VMs, especially since Linux VMs are mentioned as potentially having longer failover times.
- Ensure that terminology and instructions are platform-neutral unless a step is truly Windows-specific, in which case, provide a Linux alternative or note.
Site Recovery
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/vmware-azure-tutorial-failover-failback-modernized.md
...https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/vmware-azure-tutorial-failover-failback-modernized.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation demonstrates subtle Windows bias by referencing Windows-centric connection methods (RDP) before Linux (SSH), and by linking only to Windows VM connection instructions. There are no explicit Linux-specific examples or guidance, and troubleshooting or validation steps do not mention Linux VMs or tools. The only mention of Linux is in the context of longer failover times, not in usage instructions.
Recommendations
- Provide equal prominence to Linux and Windows in connection instructions. For example, mention SSH for Linux VMs before or alongside RDP for Windows VMs.
- Include links to both Windows and Linux VM connection guides (e.g., /azure/virtual-machines/linux/ssh-from-windows).
- Add Linux-specific validation and troubleshooting steps, such as verifying SSH access, checking Linux services, or using Linux command-line tools.
- Where examples or screenshots are provided, ensure both Windows and Linux scenarios are covered.
- Explicitly mention any differences in failover or post-failover steps for Linux VMs, not just in performance notes.
Site Recovery
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/azure-to-azure-tutorial-migrate.md
...icles/site-recovery/azure-to-azure-tutorial-migrate.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation demonstrates a subtle Windows bias by providing explicit, detailed instructions for updating root certificates on Windows VMs, while the guidance for Linux VMs is less specific and refers users to external vendor documentation. No command-line or step-by-step examples are given for Linux, and Windows is mentioned first in the prerequisites section.
Recommendations
- Provide equally detailed, step-by-step instructions for updating root certificates on common Linux distributions (e.g., Ubuntu, CentOS, RHEL), including example commands.
- Alternate the order of Windows and Linux instructions, or present them in parallel, to avoid the perception of prioritizing Windows.
- Include troubleshooting tips or common issues for Linux VMs, similar to those provided for Windows.
- Where relevant, link to official Linux documentation or Azure-specific Linux guidance, not just generic distributor advice.
Site Recovery
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/vmware-azure-troubleshoot-failback-reprotect.md
...covery/vmware-azure-troubleshoot-failback-reprotect.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation provides troubleshooting steps for both Windows and Linux VMs but tends to offer more detailed or favorable solutions for Windows. For example, when discussing static IPs after failback, it notes that Windows VMs can reacquire their static IPs automatically, while Linux users are told to manually reconfigure the IP, with no command-line example provided. There are no PowerShell-specific commands or Windows-only tools, but Linux-specific troubleshooting is less detailed and lacks parity in guidance.
Recommendations
- Provide explicit Linux command-line examples (e.g., how to set a static IP on common distributions) alongside Windows guidance.
- Clarify any differences in process between Windows and Linux VMs, and ensure both are covered equally in troubleshooting steps.
- Where Windows behavior is described as automatic, explain if and how similar automation can be achieved for Linux (e.g., via cloud-init or network manager scripts).
- Include references to Linux tools (e.g., nmcli, ifconfig, systemctl) where relevant, not just generic instructions.
- Review all troubleshooting steps to ensure Linux users are not left with manual, less-detailed, or less-automated solutions.
Site Recovery
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/azure-to-azure-quickstart.md
...in/articles/site-recovery/azure-to-azure-quickstart.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a subtle Windows bias by linking to the Windows-specific VM creation guide in the prerequisites section and not mentioning or linking to equivalent Linux VM documentation. There are no examples or instructions tailored for Linux VMs, nor are Linux-specific considerations discussed. All instructions are generic, but the only explicit reference is to Windows.
Recommendations
- In the prerequisites section, provide links to both Windows and Linux VM creation guides (e.g., /azure/virtual-machines/linux/quick-create-portal).
- Explicitly mention that the process applies to both Windows and Linux VMs, and highlight any differences if applicable.
- Include Linux-specific notes or troubleshooting tips where relevant (e.g., extension removal, OS-specific replication considerations).
- Ensure that screenshots and terminology are OS-neutral or provide both Windows and Linux examples where interface or process differs.
Site Recovery
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/how-to-migrate-run-as-accounts-managed-identity.md
...ery/how-to-migrate-run-as-accounts-managed-identity.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Summary
The documentation page focuses exclusively on Azure portal and graphical workflows, which are typically more familiar to Windows users. There are no command-line examples (such as Azure CLI or PowerShell), and there is no mention of Linux-specific tools, workflows, or considerations. The step-by-step instructions and screenshots are all based on the Azure portal, which is platform-agnostic but often associated with Windows-centric usage patterns. There is no guidance for users who prefer or require Linux-based automation or command-line approaches.
Recommendations
- Add equivalent Azure CLI examples for each migration step, including commands to enable managed identities, assign roles, and update authentication types. This will help Linux users who rely on CLI tools.
- Explicitly mention that all steps can be performed from any OS using the Azure CLI or ARM templates, and provide links to relevant documentation.
- Include a section or callout for Linux administrators, highlighting any differences or additional considerations when performing these tasks from a Linux environment.
- Provide PowerShell examples as well, but ensure they are presented alongside (not before) Azure CLI examples to avoid Windows-first bias.
- Where screenshots are used, clarify that the Azure portal is accessible from any OS and that no Windows-specific tools are required.
Site Recovery
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/quickstart-create-vault-bicep.md
...rticles/site-recovery/quickstart-create-vault-bicep.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for all steps, but consistently lists PowerShell examples after CLI, and does not include any Linux- or Bash-specific guidance or context. While Azure CLI is cross-platform, the explicit inclusion of PowerShell (a Windows-centric tool, despite its recent cross-platform support) and the lack of any mention of Bash scripting or Linux shell environments may create a subtle Windows bias. There are no Linux-specific tools, patterns, or troubleshooting notes, and no explicit mention that all steps work identically on Linux/macOS.
Recommendations
- Explicitly state that Azure CLI commands work on Windows, Linux, and macOS, and can be run from Bash or other Unix shells.
- Add a short section or note confirming that all steps are cross-platform, and that PowerShell is optional.
- Consider including Bash-specific examples or notes for users who may be scripting in Bash.
- Where PowerShell is mentioned, clarify that it is available cross-platform, but not required for Linux/macOS users.
- If possible, provide troubleshooting tips or links for common issues encountered on Linux/macOS environments.
Site Recovery
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/azure-to-azure-move-overview.md
...articles/site-recovery/azure-to-azure-move-overview.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation exhibits a mild Windows bias by referencing Windows-specific resources before their Linux equivalents and mentioning Windows tools (such as SQL Server Always On) without Linux alternatives. For example, the link for availability sets points to a Windows VM tutorial, and the multi-tier architecture example uses SQL Server, which is traditionally associated with Windows environments.
Recommendations
- Provide equal prominence to Linux in documentation links, such as linking to both Windows and Linux VM availability set tutorials.
- Include examples or references to Linux-based database solutions (e.g., MySQL, PostgreSQL) alongside SQL Server in architecture diagrams and descriptions.
- Ensure that any tool or technology mentioned (such as SQL Server Always On) is accompanied by Linux-compatible alternatives or a note about Linux support.
- Review all example commands, screenshots, and walkthroughs to ensure they are not Windows-centric and, where possible, provide Linux equivalents.
Site Recovery
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/move-azure-VMs-AVset-Azone.md
...n/articles/site-recovery/move-azure-VMs-AVset-Azone.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation demonstrates Windows bias by providing explicit, step-by-step instructions and links for Windows virtual machines (e.g., converting unmanaged to managed disks, updating root certificates), while Linux guidance is minimal and generic (e.g., 'follow the guidance provided by your Linux distributor'). There are no Linux-specific examples or links, and Windows is mentioned first and in more detail.
Recommendations
- Provide equivalent, detailed instructions and official documentation links for Linux virtual machines, such as converting unmanaged to managed disks and updating root certificates.
- Include Linux-specific examples or references alongside Windows instructions, not just generic statements.
- When listing steps or requirements, alternate the order or present Windows and Linux guidance in parallel to avoid 'Windows first' bias.
- Reference official Azure documentation for Linux VM management tasks where possible, similar to the Windows links provided.
Site Recovery
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/tutorial-shared-disk.md
...ob/main/articles/site-recovery/tutorial-shared-disk.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation is heavily focused on Windows Server Failover Clusters (WSFC) and does not mention or provide guidance for Linux-based clustering solutions or workloads. All examples, prerequisites, and process steps assume a Windows environment, with no mention of Linux clusters, tools, or parity in supported scenarios.
Recommendations
- Explicitly state if Linux-based clusters (such as Pacemaker/Corosync) are supported or not. If not supported, clarify this early in the documentation.
- If Linux shared disk clustering is supported, add equivalent guidance, prerequisites, and step-by-step instructions for setting up disaster recovery for Linux clusters.
- Include Linux-specific examples, screenshots, and troubleshooting steps where applicable.
- If only Windows is supported, consider renaming the article or adding a prominent note to clarify the Windows-only scope to avoid misleading Linux users.
Site Recovery
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/site-recovery-vmware-deployment-planner-analyze-report.md
...site-recovery-vmware-deployment-planner-analyze-report.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page primarily describes the analysis of the Deployment Planner report for VMware disaster recovery to Azure, focusing on report fields and recommendations. While the content is generally platform-neutral, there are subtle signs of Windows bias: Windows Server EFI virtual machines are specifically mentioned as supported for EFI boot type, with explicit OS version details, while Linux EFI support is not mentioned. Additionally, there are no Linux-specific examples, notes, or parity details for features like EFI support or failover/failback, and no Linux command-line or tool usage is referenced.
Recommendations
- Explicitly state the support status for Linux EFI virtual machines, including any limitations or requirements, to match the detail given for Windows Server.
- Provide examples or notes relevant to both Windows and Linux VMs where applicable, especially in sections discussing OS types, boot types, and compatibility.
- If there are differences in failover/failback support or tooling for Linux VMs, document them clearly.
- Include Linux-specific considerations or troubleshooting steps where relevant, such as for the mobility service or agent versions.
- Ensure that any command-line or scripting examples (if added in future) include both Windows (PowerShell) and Linux (bash/CLI) equivalents.
Site Recovery
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/vmware-azure-set-up-process-server-azure.md
...e-recovery/vmware-azure-set-up-process-server-azure.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows Tools
Summary
The documentation page does not specify or provide examples for Linux-based process servers, nor does it mention Linux administration patterns or tools. It implicitly assumes a Windows environment by referencing 'User name' and 'Password' for Admin permissions and does not clarify whether Linux-based process servers are supported or how to set them up. No Linux-specific instructions, commands, or screenshots are provided.
Recommendations
- Explicitly state whether Linux-based process servers are supported or not. If supported, provide equivalent setup instructions for deploying and configuring a Linux process server VM in Azure.
- Include Linux-specific examples for credential setup (e.g., SSH key authentication), package installation, and registration steps.
- Mention any differences in process server requirements or capabilities between Windows and Linux.
- Provide screenshots or command-line examples relevant to Linux environments where applicable.
- Clarify any prerequisites or limitations for Linux process servers in the 'Before you start' section.
Site Recovery
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/vmware-troubleshoot-mobility-agent-health.md
...-recovery/vmware-troubleshoot-mobility-agent-health.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation generally presents file paths for both Linux and Windows, but in error logs and troubleshooting steps, Windows-specific paths, hostnames, and service names are mentioned first or exclusively. Error logs reference Windows-style paths (e.g., C:\...), and service names use Windows conventions (e.g., 'Microsoft Azure RCM Proxy Agent'). There are no Linux-specific troubleshooting commands, service names, or examples, and Linux is only mentioned in the context of log file locations.
Recommendations
- Provide Linux-specific troubleshooting steps, including relevant service names and commands (e.g., systemctl commands for restarting services).
- Include Linux log examples and error messages, not just Windows-style logs.
- When listing file paths or instructions, alternate the order or present Linux examples first in some sections.
- Mention Linux equivalents for all Windows tools and services referenced.
- Clarify if certain steps or services are only applicable to Windows, and provide Linux alternatives where possible.
Site Recovery
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/azure-to-azure-how-to-enable-replication-cmk-disks.md
...https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/azure-to-azure-how-to-enable-replication-cmk-disks.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Summary
The documentation provides a detailed walkthrough for enabling replication of encrypted Azure VMs, but the only command-line example is a PowerShell script. There are no CLI, Bash, or Linux-oriented instructions or examples, which may disadvantage users working from Linux or cross-platform environments.
Recommendations
- Provide equivalent Azure CLI (az) command examples alongside PowerShell scripts, as Azure CLI is cross-platform and works natively on Linux, macOS, and Windows.
- Explicitly mention that the procedure can be performed from any OS via the Azure Portal, and clarify any OS-specific requirements.
- If certain features are only available via PowerShell, state this clearly and provide workarounds or alternatives for Linux users where possible.
- Include Bash or shell script examples for common automation scenarios, or reference documentation for Linux users.
- Review screenshots and UI instructions to ensure terminology is not Windows-centric (e.g., avoid references to 'blades' if not universally used).
Site Recovery
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/azure-to-azure-autoupdate.md
...in/articles/site-recovery/azure-to-azure-autoupdate.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Summary
The documentation provides only Azure PowerShell script examples for managing Mobility service automatic updates, with no equivalent CLI or Linux-native instructions. All automation and scripting guidance is presented in PowerShell, which is primarily associated with Windows environments, and there are no Bash, Azure CLI, or cross-platform examples. This may disadvantage users managing Azure VMs from Linux or macOS systems.
Recommendations
- Provide equivalent Azure CLI (az) commands for all PowerShell script examples, as Azure CLI is cross-platform and widely used on Linux and macOS.
- Include Bash script examples for automating tasks where appropriate, or at least reference how to perform the same actions in Bash.
- Explicitly state that the PowerShell script can be run from Azure Cloud Shell, which is available in-browser and supports both Bash and PowerShell, to clarify cross-platform options.
- Add a section or note addressing Linux/macOS users, outlining how they can perform the same tasks without relying on Windows-specific tools.
- Where possible, use REST API examples or reference the REST API documentation for advanced automation scenarios, as these are platform-agnostic.
Site Recovery
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/azure-to-azure-move-overview.md
...articles/site-recovery/azure-to-azure-move-overview.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation demonstrates a mild Windows bias. In the architecture section, the link for 'availability sets' points specifically to the Windows VM tutorial, rather than a neutral or Linux equivalent. There are no explicit Linux examples or references, and the only database example given is SQL Server (a Microsoft/Windows-centric technology). However, there are no PowerShell-heavy examples or CLI commands, and the content is generally high-level and conceptual.
Recommendations
- When referencing availability sets or other Azure VM features, link to documentation that covers both Windows and Linux, or provide both links.
- Include examples or references for Linux-based workloads (e.g., mention MySQL/PostgreSQL as alternative database tiers, or reference Linux VM documentation).
- If providing architecture diagrams or walkthroughs, ensure at least one example uses Linux VMs or open-source stacks.
- Avoid using only Windows-centric technologies (like SQL Server) in examples; provide parity with common Linux/open-source solutions.
Site Recovery
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/azure-to-azure-quickstart.md
...in/articles/site-recovery/azure-to-azure-quickstart.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by linking to Windows-specific VM creation instructions in the prerequisites section and omitting any mention or example of Linux VM creation or management. No Linux-specific guidance or parity is provided throughout the page.
Recommendations
- In the prerequisites section, provide links to both Windows and Linux VM creation guides (e.g., include /azure/virtual-machines/linux/quick-create-portal alongside the Windows link).
- Where relevant, clarify that the steps apply equally to both Windows and Linux VMs, or note any differences.
- Include screenshots or examples that represent both Windows and Linux VMs, or use neutral imagery.
- Add a note or section addressing any Linux-specific considerations for Azure Site Recovery, if applicable.
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
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation consistently presents Windows instructions and tools before Linux equivalents, such as listing Windows agent installation and validation steps before Linux, and referencing Windows-specific tools (e.g., Control Panel, MsiExec.exe) in more detail. Linux instructions are present but generally follow Windows and sometimes lack the same level of detail or context.
Recommendations
- Alternate the order of Windows and Linux instructions in each section, or present them in parallel (side-by-side or tabbed) to avoid implying priority.
- Provide equal detail for Linux steps, including explicit file paths, validation commands, and troubleshooting tips, similar to the Windows sections.
- Reference Linux tools and package managers (e.g., apt, yum, zypper) explicitly and provide example commands for installation and validation.
- Where possible, use neutral language and structure (e.g., 'For Windows, do X. For Linux, do Y.') rather than always listing Windows first.
- Include links to both Windows and Linux agent documentation with equal prominence.
Site Recovery
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/azure-to-azure-tutorial-migrate.md
...icles/site-recovery/azure-to-azure-tutorial-migrate.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation demonstrates a subtle Windows bias in the prerequisites section: instructions for updating root certificates are detailed for Windows VMs, while Linux VMs are referenced generically without specific guidance or examples. No Linux-specific commands, tools, or step-by-step examples are provided, and Windows is mentioned first in the update instructions.
Recommendations
- Provide explicit, step-by-step instructions or references for updating root certificates on popular Linux distributions (e.g., Ubuntu, CentOS, RHEL), similar to the detail given for Windows.
- Ensure Linux is mentioned alongside Windows in all relevant sections, and consider alternating the order in which OSes are referenced.
- Include Linux-specific troubleshooting tips or commands where appropriate.
- Where possible, provide parity in examples, such as showing both Windows and Linux update processes or linking to authoritative Linux documentation.