Migrate
203
Total Pages
70
Linux-Friendly Pages
133
Pages with Bias
65.5%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
918 issues found
Showing 176-200 of 918 flagged pages
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates several forms of Windows bias. Windows-specific tools (WMI, PowerShell, Registry, COM objects) are referenced extensively and often before Linux equivalents. Windows examples and data collection methods are described in greater detail and with more explicit tooling references (e.g., PowerShell cmdlets, registry paths), while Linux methods are presented mainly as shell commands, sometimes with less explanation or context. Some sections (ASP.NET, Java, Spring Boot web app data) mention only Windows server discovery, omitting Linux scenarios. Storage metadata and application inventory are more detailed for Windows, with Linux coverage being more command-centric and less descriptive.
Recommendations
- Ensure Linux examples and tooling are presented with equal detail and clarity as Windows, including explicit command outputs and context.
- Where Windows-specific tools (e.g., PowerShell, WMI, Registry) are listed, provide Linux equivalents (e.g., systemd, /proc, config files) in parallel, not as an afterthought.
- For sections that mention only Windows server discovery (e.g., web app data), clarify Linux support or explicitly state limitations.
- Add more Linux-centric examples for application inventory, feature detection, and pending updates, with sample outputs and explanations.
- Structure documentation so that Windows and Linux instructions/examples are presented side-by-side, rather than Windows-first.
- Review and expand Linux storage metadata collection to match the granularity and explanation given for Windows.
Create Pull Request
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page exhibits a Windows bias primarily through its exclusive mention of Windows-specific tools and patterns, such as Windows Server Failover Clusters and Cloud Witness, without providing equivalent Linux guidance or examples. References to migration best practices link to Windows-specific documentation, and there are no Linux or cross-platform examples for high availability, disaster recovery, or licensing scenarios. The documentation also prioritizes Windows terminology and solutions, omitting Linux-specific migration considerations and tools.
Recommendations
- Add equivalent Linux guidance for high availability and disaster recovery scenarios, such as using Pacemaker or Corosync clusters for SQL workloads on Linux VMs.
- Include links to Linux-specific performance guidelines and best practices for running SQL Server on Azure Virtual Machines (e.g., /azure/azure-sql/virtual-machines/linux/performance-guidelines-best-practices-checklist).
- Provide examples and instructions for configuring SQL Server on Azure VM using Linux-based operating systems, including licensing and Azure Hybrid Benefit for RHEL/SLES.
- Mention Linux-specific witness options (such as File Share Witness or other quorum solutions) for failover clusters.
- Ensure parity in migration strategy descriptions by including Linux scenarios and clarifying where steps or recommendations differ for Linux-based SQL deployments.
Migrate
Discover and assess using Azure Private Link
...migrate/discover-and-assess-using-private-endpoints.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias in several ways: all appliance installation instructions and examples are given using PowerShell, with no mention of Linux shell equivalents; the installer script is a PowerShell script (.ps1), and the instructions explicitly require launching PowerShell with administrative privileges. File paths and tool references (e.g., C:\ProgramData, C:\Program Files) are Windows-specific. There is no guidance or examples for deploying or running the appliance on Linux servers, nor are Linux tools or shell commands referenced.
Recommendations
- Provide Linux-specific installation instructions, including shell commands for extracting and running the installer.
- Clarify whether the appliance installer supports Linux hosts, and if so, include examples for Bash or other Linux shells.
- Offer parity in troubleshooting steps, such as log file locations and permissions, for Linux environments.
- Reference Linux file paths and tools where applicable, or explicitly state platform limitations.
- If the appliance is Windows-only, clearly state this limitation early in the documentation.
Migrate
Set up Agentless Dependency Analysis in Azure Migrate
...https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/how-to-create-group-machine-dependencies-agentless.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation demonstrates a Windows bias by providing extensive PowerShell-based instructions for managing agentless dependency analysis, enabling/disabling features, and exporting data. Windows-centric tools (PowerShell, Windows credentials) are mentioned first and in greater detail, while Linux management is limited to credential requirements and lacks equivalent command-line or automation examples. The documentation assumes users are familiar with Windows administrative patterns and does not offer parity for Linux environments.
Recommendations
- Provide Linux CLI (e.g., Bash, shell script) equivalents for all PowerShell commands and workflows, including enabling/disabling dependency analysis and exporting data.
- Include examples using native Linux tools (such as SSH, SCP, or Azure CLI) for managing Azure Migrate appliances and dependency analysis.
- Balance credential management instructions by detailing Linux-specific best practices and automation (e.g., using SSH keys, sudoers configuration) alongside Windows methods.
- Ensure that screenshots and UI instructions highlight both Windows and Linux server scenarios equally.
- Add troubleshooting and validation steps specific to Linux environments, not just Windows.
- Explicitly mention cross-platform support and clarify any differences in feature availability or management between Windows and Linux servers.
Migrate
Discover software inventory on on-premises servers with Azure Migrate
.../main/articles/migrate/how-to-discover-applications.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in several ways: Windows credentials and patterns are mentioned first or exclusively in multiple sections (e.g., SQL Server, File Server, ASP.NET web apps), Windows-specific tools and roles (IIS, SCCM, RDP, Active Directory, Exchange Server) are highlighted, and some features (like File Server discovery) are limited to Windows Server only. Linux equivalents are either mentioned after Windows or omitted entirely in certain cases, such as File Server discovery and ASP.NET web apps. Examples and instructions often prioritize Windows scenarios, with Linux support described in less detail.
Recommendations
- Provide Linux-first or Linux-parity examples and instructions alongside Windows ones, especially for credential setup, permissions, and discovery workflows.
- Expand File Server discovery to include common Linux file server solutions (e.g., Samba, NFS) and document their discovery process.
- Include Linux web server and app discovery examples (e.g., Apache, Nginx, Tomcat) with step-by-step credential and configuration guidance.
- List Linux tools and patterns (e.g., SSH, systemd, cron, SELinux) in relevant categories and examples, not just Windows tools.
- Clarify support for Linux roles and features in all sections, and avoid language that implies Windows is the default or only supported platform.
- Ensure that tables and software examples include Linux-native applications and utilities where appropriate.
Migrate
Set up agent-based dependency analysis in Azure Migrate
...es/migrate/how-to-create-group-machine-dependencies.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in several ways: Windows installation instructions and tools are presented first and in greater detail, with references to Windows-specific installation methods (Configuration Manager, Intigua, scripts), while Linux instructions are brief and lack comparable detail or automation options. There are more screenshots and step-by-step instructions for Windows, and Windows tools are mentioned explicitly. Linux examples are minimal and lack parity in guidance and troubleshooting.
Recommendations
- Provide Linux installation instructions with equal detail, including automation options (e.g., using Ansible, shell scripts, or package managers).
- Include screenshots or terminal output examples for Linux agent installation and verification.
- Mention Linux tools and patterns (such as systemd service management, package installation via apt/yum/zypper) alongside Windows equivalents.
- Present Windows and Linux instructions in parallel sections, or alternate which platform is described first.
- Add troubleshooting steps and supported OS lists for Linux with the same prominence as for Windows.
- Reference community or official scripts for Linux agent deployment, similar to the Windows script link.
Migrate
Discover SQL Server instances in an existing Azure Migrate project
...ticles/migrate/how-to-discover-sql-existing-project.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page exhibits a Windows bias by referencing Windows/Domain credentials, PowerShell requirements, and Windows OS patterns exclusively. There are no examples or instructions for Linux-based environments, nor are Linux authentication or discovery methods discussed. Windows tools and credential formats are mentioned first and exclusively, with no parity for Linux systems.
Recommendations
- Add explicit instructions and examples for discovering SQL Server instances on Linux servers, including authentication methods and credential formats.
- Mention Linux prerequisites (e.g., required packages, supported distributions) alongside PowerShell and Windows tools.
- Provide parity in credential provisioning utilities for Linux environments, or clarify cross-platform support.
- Include screenshots or walkthroughs from Linux-based appliances or servers, if supported.
- Clarify whether the Azure Migrate appliance supports agentless discovery on Linux and, if so, detail the process.
- List Linux-specific troubleshooting steps and requirements in the 'Before you start' section.
Migrate
Automate migration of machines in Azure Migrate
.../blob/main/articles/migrate/how-to-migrate-at-scale.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation exclusively references PowerShell scripts (.ps1), links only to PowerShell sample repositories, and does not mention or provide examples for Linux shell scripting or cross-platform automation tools. The use of PowerShell and Windows-centric scripting is assumed throughout, with no guidance for Linux users or alternative approaches for non-Windows environments.
Recommendations
- Provide equivalent Bash or shell script examples for Linux environments.
- Mention and link to cross-platform tools (e.g., Azure CLI, Python SDK) that can be used for automation.
- Clarify whether the PowerShell scripts can be run on Linux (via PowerShell Core), and provide instructions if so.
- Include Linux-specific prerequisites and setup steps where relevant.
- Reorganize examples to present both Windows and Linux approaches side-by-side, or indicate platform compatibility up front.
Migrate
Migrate VMware virtual machines to Azure with server-side encryption(SSE) and customer-managed keys(CMK) using the Migration and modernization tool
...es/migrate/how-to-migrate-vmware-vms-with-cmk-disks.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Windows First
Summary
The documentation page demonstrates a strong Windows bias by exclusively using Azure PowerShell for all command-line examples and automation steps. There are no references to Azure CLI, Bash, or Linux-native tooling, and all example links and code blocks use PowerShell syntax. The instructions for creating disk encryption sets and deploying Resource Manager templates are Windows-centric, with file paths and command usage tailored to Windows environments. There is no mention of Linux or cross-platform alternatives, nor guidance for users working from non-Windows systems.
Recommendations
- Provide equivalent Azure CLI examples for all PowerShell commands, ensuring Linux and macOS users can follow the steps without needing PowerShell.
- Include Bash script snippets or instructions for common tasks, such as editing JSON templates and deploying them.
- Reference cross-platform tools (e.g., Azure CLI, VS Code) and avoid Windows-specific file paths in examples.
- Add a section or callout noting that all steps can be performed from Linux, macOS, or Windows, and link to relevant cross-platform documentation.
- Ensure that links to further reading or tutorials include both Windows and Linux options where available.
Migrate
Review Discovered Inventory (Preview) in Azure Migrate
...articles/migrate/how-to-review-discovered-inventory.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page exhibits a moderate Windows bias. Windows terminology and features (such as Windows credentials, installed roles and features, .NET/IIS web apps, SQL Server databases) are mentioned first or exclusively in several places. Linux equivalents are referenced, but often as secondary options, and there are no Linux-specific examples or detailed guidance for Linux workloads, web apps, or databases. The documentation assumes familiarity with Windows environments and tools, and does not provide parity in Linux-focused instructions or examples.
Recommendations
- Provide Linux-specific examples and walkthroughs for credential setup, discovery, and inventory review, similar to those given for Windows.
- Include explicit guidance for common Linux workloads (e.g., Apache, Nginx web servers, MySQL/PostgreSQL databases) in inventory and assessment sections.
- Ensure that instructions for permissions, dependency analysis, and troubleshooting are equally detailed for Linux as for Windows.
- List Linux options and terminology before or alongside Windows, rather than after.
- Add screenshots and sample output for Linux server discovery and inventory review.
- Clarify support for Linux tags, features, and software inventory, and provide examples.
Migrate
Set up an Azure Migrate scale-out appliance for agentless VMware migration
...ain/articles/migrate/how-to-scale-out-for-migration.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a strong Windows bias: all deployment and configuration instructions are for Windows Server (2019/2022), exclusively using PowerShell scripts and Windows-specific tools (CertUtil, IIS, registry edits). There are no examples or guidance for deploying the appliance on Linux, nor are Linux equivalents for commands or tools mentioned. The installer script and prerequisites are tailored to Windows environments, with no mention of Linux support or alternatives.
Recommendations
- Provide instructions and installer scripts for deploying the Azure Migrate appliance on supported Linux distributions, if possible.
- Include Linux equivalents for command-line operations (e.g., checksum validation using sha256sum or openssl).
- Mention whether the appliance can be run in a Linux VM, and if not, clarify the platform limitation up front.
- Offer parity in troubleshooting steps and log locations for Linux environments.
- If PowerShell is required, note whether PowerShell Core (cross-platform) is supported and provide Linux installation steps.
- Explicitly state any platform restrictions in the prerequisites section.
Migrate
Set up an Azure Migrate appliance for server assessment in a VMware environment
...ain/articles/migrate/how-to-set-up-appliance-vmware.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page exhibits a Windows bias in several ways: it offers a PowerShell installer script as the only alternative to the OVA template, references Windows-specific paths and tools (e.g., installation of VDDK to C:\Program Files), and consistently presents Windows authentication and tooling before Linux equivalents. Linux setup instructions and examples are missing or only mentioned in passing, with no parity in detailed steps or troubleshooting.
Recommendations
- Provide a Linux shell script installer alternative to the PowerShell script, with explicit instructions for Linux-based appliances.
- Include Linux-specific examples for credential setup, file paths, and troubleshooting, such as installing VDDK in a Linux environment.
- Present Linux and Windows authentication options side-by-side, with equal detail and prominence.
- Add screenshots and step-by-step guides for Linux appliance configuration and management.
- Clarify support for Linux-based appliances and document any differences in prerequisites, setup, or operation.
Migrate
Review a business case with Azure Migrate | Microsoft Docs
...b/main/articles/migrate/how-to-view-a-business-case.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page exhibits a Windows bias by frequently referencing Windows Server, SQL Server, and Windows-specific licensing and security update scenarios. Cost and savings calculations are repeatedly tied to Windows licensing models (e.g., Azure Hybrid Benefit, Extended Security Updates), with no mention of Linux equivalents or open-source workloads. Examples and cost breakdowns focus on Windows tools and patterns, and there are no Linux-specific migration, licensing, or security scenarios provided.
Recommendations
- Include examples and cost breakdowns for Linux workloads, such as migration scenarios for common Linux distributions (e.g., Ubuntu, Red Hat, CentOS) and open-source databases (e.g., MySQL, PostgreSQL).
- Discuss Azure Hybrid Benefit and Extended Security Updates in the context of Linux, clarifying which benefits apply and what alternatives exist for Linux workloads.
- Add sections or cards that address security, management, and licensing for Linux servers, including integration with Azure services (e.g., Azure Monitor, Azure Security Center) for Linux.
- Ensure that cost estimation and savings reports explicitly mention how Linux workloads are assessed and migrated, and provide parity in reporting and recommendations.
- Balance references to Windows-specific tools and licensing with equivalent Linux/open-source solutions and patterns.
Migrate
Review SQL assessment with Azure Migrate | Microsoft Docs
.../main/articles/migrate/how-to-review-sql-assessment.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by consistently referencing Windows-based SQL Server deployments, VM sizing guidelines linked to Windows documentation, and best practices for Windows environments. There are no examples, guidance, or references for Linux-based SQL Server deployments or migration scenarios, nor are Linux tools or patterns mentioned. All technical links and recommendations are for Windows-specific resources.
Recommendations
- Include explicit guidance and examples for migrating SQL Server workloads running on Linux to Azure SQL targets.
- Reference and link to Azure SQL documentation for Linux-based VM deployments and best practices, such as /azure/azure-sql/virtual-machines/linux.
- Provide parity in sizing, storage, and compute recommendations for Linux environments, including supported VM series and disk types.
- Add notes or sections clarifying differences in migration steps, compatibility checks, and remediation guidance for Linux-based SQL Server instances.
- Ensure that recommendations and readiness checks cover both Windows and Linux SQL Server scenarios, and present them with equal prominence.
Migrate
Set up an Azure Migrate appliance for Hyper-V
...in/articles/migrate/how-to-set-up-appliance-hyper-v.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page is heavily oriented toward Windows environments, specifically Hyper-V, with exclusive use of Windows tools (Hyper-V Manager, PowerShell, CertUtil, Local Group Policy Editor) and Windows-centric patterns. All examples and instructions assume a Windows host and administrative workflow, with no mention of Linux equivalents or cross-platform alternatives. Even where Linux credentials are referenced, there are no Linux-side setup or management instructions.
Recommendations
- Add explicit notes clarifying that the appliance setup is only for Hyper-V (Windows) and provide links to equivalent Linux/KVM/VMware documentation if available.
- Where PowerShell or Windows tools (CertUtil, Local Group Policy Editor) are used, offer Linux alternatives or clarify that these steps are not applicable for Linux hosts.
- Include a section or cross-reference for Linux-based appliance deployment, if supported, or guidance for users managing mixed environments.
- When discussing credential types (Windows, Linux), provide Linux-specific discovery, validation, and troubleshooting instructions.
- If the appliance or Azure Migrate supports Linux hosts, add parity in examples, screenshots, and step-by-step instructions for Linux environments.
Migrate
Set up an Azure Migrate appliance for physical servers
...n/articles/migrate/how-to-set-up-appliance-physical.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation is heavily biased towards Windows environments. All setup and deployment instructions are centered around PowerShell scripts, Windows roles (IIS, Windows Activation Service, PowerShell ISE), and Windows-specific paths and registry keys. There are no Linux-specific setup instructions, installer scripts, or examples for deploying the appliance on Linux servers. Windows tools and patterns are mentioned exclusively and before any Linux equivalents, which are largely absent.
Recommendations
- Provide equivalent Linux setup instructions, including shell script examples for installer execution and configuration.
- Document Linux prerequisites and dependencies (e.g., required packages, services) for running the appliance.
- Offer guidance for extracting and running the installer on Linux (e.g., using bash, chmod, etc.).
- Clarify whether the appliance can be hosted on Linux, and if so, provide step-by-step instructions.
- Include troubleshooting steps and log file locations for Linux environments.
- Mention Linux equivalents for Windows-specific components (e.g., IIS alternatives, registry settings, service management).
- Ensure that credential and discovery examples for Linux servers are as detailed as those for Windows servers.
Migrate
How does Hyper-V migration work in Azure Migrate?
...ain/articles/migrate/hyper-v-migration-architecture.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 Hyper-V, and provides examples and instructions exclusively for Windows tools and workflows (MMC snap-in, registry edits, Windows paths). There is no mention of Linux equivalents, nor are Linux migration scenarios or tools discussed. The guidance assumes the administrator is working in a Windows environment, with no parity for Linux-based hypervisors or migration processes.
Recommendations
- Add sections or references for migrating Linux-based hypervisors (e.g., KVM, Xen) using Azure Migrate.
- Provide equivalent examples for controlling upload throughput and efficiency on Linux hosts, if supported.
- Mention Linux-compatible tools or workflows, or clarify if the process is Windows-only.
- Include a comparison table showing feature parity and differences between Windows (Hyper-V) and Linux migration scenarios.
- Explicitly state platform limitations and recommend alternative migration paths for Linux workloads.
Migrate
Create a custom account with minimal metadata for discovery and assessment.
...b/main/articles/migrate/least-privilege-credentials.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page demonstrates Windows bias by exclusively referencing Windows tools and patterns. The provisioning utility is located in a Windows-specific directory (%ProgramFiles%), and only Windows/Domain Account and SQL Account credential types are mentioned. There are no Linux-specific instructions, examples, or references to Linux authentication mechanisms or file paths. The documentation assumes a Windows environment for SQL Server management and omits guidance for Linux-based SQL Server deployments.
Recommendations
- Include instructions and examples for provisioning least privileged accounts on SQL Server running on Linux, including Linux file paths and command-line usage.
- Mention Linux authentication mechanisms (such as local Linux users or Active Directory integration on Linux) where relevant.
- Provide parity in tooling or suggest alternative methods for Linux environments if the provided utility is Windows-only.
- Clarify any limitations or requirements for using the utility on non-Windows platforms.
- Add a section or note addressing Linux support and linking to relevant resources for Linux-based SQL Server management.
Migrate
Migrate Hyper-V servers to Azure by using Private Link
...ttps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/migrate-hyper-v-servers-to-azure-using-private-link.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation is heavily focused on migrating Hyper-V (a Windows-centric virtualization technology) servers to Azure, with all examples, instructions, and tooling centered around Windows environments. There is no mention of Linux equivalents, such as KVM or other Linux-based hypervisors, nor are there any Linux-specific migration steps, tools, or considerations. Windows terminology and tools (Hyper-V, Recovery Services vault, Azure Site Recovery provider) are used exclusively, and the Azure Hybrid Benefit section is only relevant for Windows Server licenses.
Recommendations
- Add equivalent migration documentation for Linux-based hypervisors (e.g., KVM, Xen, VMware on Linux) and provide parity in migration tooling and steps.
- Include Linux-specific examples, such as how to prepare Linux hosts for migration, agent installation on Linux, and DNS configuration on Linux systems.
- Clarify in the introduction that the guide is specific to Hyper-V/Windows, and provide links or references to Linux migration guides if available.
- Ensure that any Azure features or benefits mentioned (such as Hybrid Benefit) are contextualized for both Windows and Linux workloads, or note their applicability.
- Where DNS or network configuration is discussed, provide instructions for both Windows and Linux systems (e.g., editing /etc/hosts on Linux).
Migrate
Azure Migrate replication appliance
...main/articles/migrate/migrate-replication-appliance.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation for the Azure Migrate replication appliance exhibits a strong Windows bias. All operating system requirements, examples, and instructions are centered around Windows Server (2016/2012 R2), with no mention of Linux support or deployment. Software installation paths, licensing, and configuration details are Windows-specific (e.g., C:\Temp\ASRSetup, .msi installers, Windows Server roles and group policies). There are no Linux equivalents or instructions for deploying the appliance on Linux-based systems, nor are Linux tools or patterns referenced.
Recommendations
- Explicitly state whether Linux-based deployment of the replication appliance is supported or not. If not supported, clarify this limitation.
- If Linux deployment is possible, provide equivalent instructions for Linux (e.g., supported distributions, installation steps, required packages, service configuration).
- Include Linux-specific examples for MySQL installation, such as using apt, yum, or rpm, and appropriate file paths (e.g., /tmp/ASRSetup).
- Reference Linux system requirements and configuration settings alongside Windows equivalents.
- Avoid Windows-only terminology and provide parity in documentation for both platforms.
- If only Windows is supported, add a rationale for this choice and guidance for Linux users (e.g., recommend using a Windows VM for the appliance).
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation for the Azure Migrate appliance is heavily biased toward Windows environments. All deployment and management instructions assume or require Windows Server (2019/2022/2025) as the host OS, with no mention of Linux as a supported platform for the appliance itself. All examples for verification, upgrades, and manual operations use Windows-specific tools (PowerShell, Command Prompt, Registry Editor, Control Panel). Even when Linux servers are mentioned as discovery targets, there are no examples or instructions using Linux-native tools for appliance deployment, management, or verification. The documentation does not provide parity for Linux administrators who may wish to host or interact with the appliance outside of a Windows context.
Recommendations
- Clearly state OS requirements and limitations at the top of the documentation, including whether Linux hosting is supported or not.
- If Linux hosting is possible, provide equivalent instructions for deploying, verifying, and managing the appliance on Linux (e.g., using Bash, Linux hash utilities, Linux package managers).
- For verification steps (e.g., file hashes), include Linux command examples (e.g., sha256sum, md5sum) alongside Windows CertUtil.
- For upgrade and management tasks, offer Linux alternatives where possible (e.g., using systemd, cron, or Linux configuration files instead of Registry Editor and Control Panel).
- If the appliance is Windows-only, explicitly call out this limitation and provide guidance for Linux-centric environments (e.g., recommend running the appliance in a Windows VM if needed).
- Ensure that examples for interacting with discovered Linux servers (e.g., SSH, agent installation, troubleshooting) are included and given equal prominence.
Migrate
Migrate servers to Azure using Private Link through agent-based replications
...igrate-servers-to-azure-using-private-link-agent-based.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing Windows Server-specific features (e.g., Azure Hybrid Benefit for Windows Server), using terminology and patterns familiar to Windows administrators (e.g., 'dummy account', 'guest credentials'), and omitting explicit Linux migration examples or instructions. Windows-related options (such as Azure Hybrid Benefit) are described in detail, while Linux equivalents (e.g., RHEL, SUSE licensing) are not mentioned. There are no Linux-specific migration steps, troubleshooting, or credential guidance, and no PowerShell or CLI examples are provided for either platform.
Recommendations
- Add explicit Linux migration examples, including steps for migrating common Linux distributions (e.g., Ubuntu, CentOS, RHEL, SUSE).
- Include instructions for handling Linux credentials and service accounts during migration (e.g., SSH keys, sudo privileges).
- Mention Linux licensing options and benefits (e.g., Azure Hybrid Benefit for RHEL/SUSE) alongside Windows Server options.
- Provide troubleshooting guidance specific to Linux environments (e.g., DNS resolution using dig/nslookup, SELinux considerations).
- Offer CLI examples using Bash and Azure CLI for Linux users, and clarify any platform-specific requirements for the replication appliance.
- Ensure parity in terminology and examples so Linux administrators can follow the documentation without ambiguity.
Migrate
Support for Hyper-V migration in Azure Migrate
...es/migrate/migrate-support-matrix-hyper-v-migration.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by prioritizing Windows Server versions and tools (such as .NET Framework and Windows Firewall) in requirements and examples. Windows-specific instructions (e.g., enabling RDP, SAN policy) are more detailed and appear before Linux equivalents. Linux guidance is present but less detailed, often referencing generic SSH setup without specific commands or troubleshooting. There are no Linux command-line examples, and Windows tooling (e.g., Windows Firewall, RDP) is mentioned exclusively or first.
Recommendations
- Provide Linux-specific command-line examples for migration preparation and troubleshooting, such as firewall configuration using iptables, ufw, or firewalld.
- Include parity in detail for Linux post-migration connectivity (e.g., SSH key setup, SELinux/AppArmor considerations, systemd service checks).
- Mention Linux equivalents for Windows tools (e.g., alternatives to .NET Framework, Linux integration services).
- Ensure that Linux migration requirements and limitations are described with the same level of detail as Windows, including common issues and solutions.
- Add examples for both Windows and Linux in all relevant sections, and avoid listing Windows instructions before Linux unless contextually justified.
Migrate
Support for Hyper-V assessment in Azure Migrate and Modernize
...ain/articles/migrate/migrate-support-matrix-hyper-v.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation exhibits a clear Windows bias, with Windows-specific tools (PowerShell, WinRM, WMI) and patterns mentioned first and in detail, while Linux equivalents are referenced only briefly or as secondary. PowerShell remoting is a prerequisite for many features, and examples/scripts are exclusively for Windows environments. SQL Server discovery and web app discovery are not supported for Linux servers, and there are no Linux-specific configuration or troubleshooting examples. Windows terminology and tooling dominate throughout, with Linux support described only in passing.
Recommendations
- Provide Linux-first or Linux-parity examples and instructions where possible, especially for appliance deployment, server discovery, and dependency analysis.
- Include Linux-specific troubleshooting steps and configuration details (e.g., SSH setup, required packages, SELinux/AppArmor considerations).
- Offer sample scripts or commands for Linux environments (e.g., Bash scripts for credential setup, dependency analysis configuration).
- Clarify limitations for Linux support upfront and provide guidance or alternatives for unsupported features (e.g., SQL Server discovery on Linux).
- Balance the order of presentation so that Linux and Windows requirements are described together, rather than Windows first.
- Expand documentation for Linux web app discovery, including supported stacks and configuration requirements.
- Where PowerShell is required, offer equivalent Bash/SSH instructions for Linux environments.
Migrate
Support for physical server migration in Azure Migrate and Modernize
...s/migrate/migrate-support-matrix-physical-migration.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by prioritizing Windows-specific requirements, tools, and instructions. Windows Server is the default OS for the replication appliance, and connection instructions for migrated VMs provide more detail for Windows (RDP, Windows Firewall) than for Linux (SSH). Multipath IO support is explicitly listed for Windows servers, while Linux equivalents are not mentioned. There are no Linux-specific tooling or step-by-step examples, and Windows terminology (e.g., BitLocker, Windows Firewall) is used without Linux parity.
Recommendations
- Provide equal detail for Linux migration scenarios, including step-by-step instructions for configuring SSH, firewall rules (e.g., using iptables, firewalld, or ufw), and post-migration connectivity.
- List Linux-specific tools and patterns (e.g., SELinux, LUKS encryption, multipath IO for Linux) alongside Windows equivalents.
- Offer replication appliance setup instructions for Linux-based appliances, or clarify if only Windows Server is supported and why.
- Include examples of troubleshooting and configuration for both Windows and Linux environments.
- Review terminology to ensure Linux concepts (e.g., systemd, Linux firewalls, disk encryption) are mentioned where relevant.