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 776-800 of 918 flagged pages
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page focuses on Azure Migrate support for VMware and Hyper-V environments, with repeated references to Hyper-V (a Windows technology) and no explicit mention of Linux-based environments or migration scenarios. There are no examples, instructions, or references for Linux servers, tools, or migration patterns. The order of presentation consistently lists Windows-centric technologies (Hyper-V) alongside VMware, and omits Linux-specific details.
Recommendations
- Add explicit support matrix entries and examples for Linux physical servers and Linux-based VMs (both on-premises and cloud).
- Include instructions or references for assessing and migrating Linux workloads, such as supported distributions, agent installation, and migration caveats.
- Provide parity in documentation structure: list Linux alongside VMware and Hyper-V in all relevant tables and sections.
- Reference Linux-native tools or patterns where applicable (e.g., shell commands, Linux authentication/permissions).
Create Pull Request
Migrate
Prepare machines for migration with Azure Migrate
...cs/blob/main/articles/migrate/prepare-for-migration.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias. Windows-specific instructions (such as diskpart, SAN policy, and PowerShell for enabling RDP) are presented in detail, often before Linux equivalents. Windows configuration steps are more granular and tool-specific, while Linux instructions are more generic and less detailed. Windows tools and patterns (e.g., Windows Firewall, WinHTTP proxy, RDP, PowerShell) are mentioned explicitly, whereas Linux steps are summarized and lack command-line examples. In several sections, Windows instructions precede Linux, and Windows-specific tools are referenced without Linux alternatives.
Recommendations
- Provide Linux command-line examples (e.g., for updating fstab, enabling SSH, modifying firewall rules) similar to the Windows diskpart and PowerShell examples.
- Include Linux-specific troubleshooting steps and references to common Linux tools (e.g., iptables, firewalld, systemctl) alongside Windows tools.
- Present Windows and Linux instructions in parallel, rather than Windows-first, to improve parity and clarity for non-Windows users.
- Expand Linux sections to match the level of detail given to Windows, including step-by-step guides for manual configuration tasks.
- Reference Linux documentation and best practices for migration and connectivity as prominently as Windows resources.
Migrate
Quickstart to create an Azure Migrate project using an Azure Resource Manager template.
.../articles/migrate/quickstart-create-migrate-project.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation focuses exclusively on using the Azure portal and ARM templates via a web interface, with no mention of command-line deployment options. There are no examples for deploying the template using cross-platform tools like Azure CLI, nor any PowerShell examples. However, the workflow implicitly assumes a graphical interface, which is more common on Windows, and does not address Linux/macOS users who may prefer CLI-based deployment.
Recommendations
- Add instructions and examples for deploying the ARM template using Azure CLI (az deployment group create), which works on Windows, Linux, and macOS.
- Explicitly mention that the deployment can be performed from any OS using CLI tools.
- Provide links to documentation for both Azure CLI and PowerShell deployments, ensuring parity.
- Include screenshots or terminal output for CLI-based deployments alongside portal-based instructions.
Migrate
Assess large numbers of physical servers for migration to Azure with Azure Migrate | Microsoft Docs
...lob/main/articles/migrate/scale-physical-assessment.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by exclusively referencing the Azure Migrate appliance as being deployed on a Windows server, with no mention of Linux deployment options or examples. There are no Linux-specific instructions, examples, or parity in tooling discussed. This may lead Linux users to believe the solution is Windows-only or require additional research to determine Linux compatibility.
Recommendations
- Explicitly state whether the Azure Migrate appliance supports Linux hosts, and if not, clarify this limitation.
- If Linux deployment is possible, provide step-by-step instructions and examples for Linux environments alongside Windows instructions.
- Include notes or tables comparing Windows and Linux support for the Azure Migrate appliance and related tools.
- Add troubleshooting or FAQ sections for common Linux-specific issues in the migration process.
Migrate
Redeploy servers to Azure using Infrastructure as Code
...ure-docs/blob/main/articles/migrate/server-redeploy.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page is primarily focused on Windows Server migration, as indicated by the customer intent and the absence of explicit Linux-specific examples or instructions. While the introduction claims support for both Windows and Linux servers, all examples, scripts, and migration scenarios are described generically or with a Windows-centric context. There are no Linux-specific migration steps, troubleshooting notes, or references to Linux tools or patterns. The page also references IDEs like Visual Studio Code, which, while cross-platform, are more commonly associated with Windows environments.
Recommendations
- Add explicit Linux migration examples, including steps for common Linux distributions (e.g., Ubuntu, CentOS).
- Include Linux-specific prerequisites, such as required packages, permissions, or configuration nuances.
- Provide sample scripts or command-line instructions for Linux environments (e.g., bash scripts, Linux disk handling).
- Mention Linux-friendly tools and editors (e.g., Vim, nano) alongside Visual Studio Code.
- Address potential differences in agent-based vs. agentless migration for Linux servers.
- Clarify any limitations or special considerations for Linux server redeployment.
Migrate
Simplified experience for Azure Migrate
...les/migrate/simplified-experience-for-azure-migrate.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page for Azure Migrate's simplified experience demonstrates a Windows bias by exclusively referencing Windows Server 2022 as the replication appliance, without mentioning Linux-based alternatives or providing Linux-specific setup examples. Windows infrastructure is presented as the default and only option for core migration components, despite the stated goal of improved Linux migration support. There are no Linux command-line examples, nor guidance for Linux users on appliance setup or management.
Recommendations
- Explicitly mention whether Linux-based replication appliances are supported, and provide guidance if so.
- Include Linux-specific setup instructions or examples for the migration stack and replication appliance.
- Clarify if the reliance on Windows Server 2022 is a technical requirement, and offer alternatives or workarounds for Linux-only environments.
- Present Linux and Windows options side-by-side where possible, rather than defaulting to Windows-first language.
Migrate
Prepare machines for agentless migration with Azure Migrate
...in/articles/migrate/prepare-for-agentless-migration.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page presents Windows migration steps before Linux, provides detailed Windows-specific tooling and PowerShell commands, and includes screenshots and examples for Windows tools (diskpart, PowerShell) while Linux examples are fewer and less detailed. Windows instructions are more step-by-step, with explicit command-line examples and screenshots, whereas Linux instructions are more generic and lack equivalent visual aids or explicit commands for all steps.
Recommendations
- Present Linux and Windows sections in parallel or alternate order, rather than always listing Windows first.
- Provide Linux command-line examples for all manual steps, similar to the PowerShell and diskpart examples given for Windows.
- Include screenshots or terminal output for Linux steps where appropriate (e.g., verifying waagent status, editing network files).
- Reference Linux documentation and tools with the same prominence as Windows tools (e.g., mention systemctl, nmcli, or other relevant utilities).
- Ensure that troubleshooting and validation steps for Linux are as explicit and detailed as those for Windows.
Migrate
Quickstart to create an Azure Migrate project using Portal
...lob/main/articles/migrate/quickstart-create-project.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias, particularly in the section on using the Azure CLI. It instructs users to install the CLI and then explicitly directs them to use PowerShell as an Administrator, with all example commands shown in a PowerShell context. There are no equivalent instructions or examples for Linux/macOS users, nor is there mention of using Bash or other shells. The ordering and screenshots throughout the page are neutral, but the CLI usage section is notably Windows-centric.
Recommendations
- Provide explicit instructions for running Azure CLI commands on Linux/macOS, including using Bash or other common shells.
- Clarify that the Azure CLI can be used cross-platform and provide example commands for both Windows (PowerShell) and Linux/macOS (Bash).
- Avoid language that assumes PowerShell is the default shell; use neutral phrasing such as 'open your terminal' or 'run the following commands in your shell.'
- Include screenshots or references to Linux/macOS environments where relevant.
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page for Azure Migrate FAQ demonstrates a moderate Windows bias. Windows-specific tools such as the MAP Toolkit and Site Recovery Deployment Planner are mentioned exclusively, with no Linux equivalents or cross-platform alternatives referenced. The discussion of migration scenarios and skills lists PowerShell before Bash, and focuses on Windows-centric virtualization platforms (VMware, Hyper-V) without explicit mention of Linux-based environments or migration patterns. There are no Linux-specific examples, tools, or guidance provided.
Recommendations
- Include references to Linux migration tools and scenarios, such as guidance for migrating Linux VMs and workloads.
- Provide examples or mention of Linux-based assessment and planning tools, if available.
- Ensure scripting examples and recommendations give equal weight to Bash and PowerShell, possibly listing Bash first or side-by-side.
- Clarify support for Linux operating systems and applications in migration scenarios.
- Add FAQs or links addressing common Linux migration challenges and solutions.
Migrate
How to review the assessments created for migration to SQL Server on Azure VM, Azure SQL Managed Instance and Azure SQL Database
...cs/blob/main/articles/migrate/review-sql-assessment.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation consistently refers to 'SQL Server on Azure VM' as the primary migration target and uses Windows-centric terminology (e.g., 'SQL Server', 'SQL Server credentials'). There is no mention of Linux-based SQL Server deployments, nor examples or guidance for users running SQL Server on Linux. The migration strategies and readiness/cost reports are described in terms of Windows VM scenarios, with no explicit Linux parity or acknowledgement.
Recommendations
- Explicitly mention that SQL Server can run on both Windows and Linux, and clarify that Azure VM migration supports both OS types.
- Include examples or notes for users migrating SQL Server from Linux environments, including any differences in assessment or migration steps.
- Add guidance or links for Linux-specific migration considerations (e.g., authentication, file paths, service management).
- Ensure terminology is inclusive (e.g., 'SQL Server on Azure VM (Windows or Linux)') where appropriate.
Migrate
Troubleshoot assessments FAQ in Azure Migrate
...b/main/articles/migrate/troubleshoot-assessment-faq.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Powershell Heavy
Summary
The documentation page shows notable Windows bias, with frequent references to Hyper-V, Windows licensing, and Windows-centric troubleshooting steps. Examples and troubleshooting guidance often focus on Windows environments (Hyper-V, Windows VMs, Microsoft Edge/IE), with Linux-specific details either missing or mentioned secondarily. The section on capturing network traffic prioritizes Microsoft browsers and tools, with only brief mention of Chrome, and omits Linux-native browsers or CLI tools. Licensing guidance is Windows-only, and there are no Linux/Powershell parity examples for troubleshooting or data collection.
Recommendations
- Add Linux-specific troubleshooting steps and examples, especially for performance data collection and assessment issues.
- Include guidance for Linux environments (e.g., KVM, physical Linux servers) alongside Hyper-V and VMware.
- Provide parity in network traffic capture instructions for Linux browsers (e.g., Firefox) and CLI tools (e.g., tcpdump, Wireshark).
- Clarify licensing considerations for Linux servers in assessments, or explain why they are omitted.
- Ensure examples and instructions are presented in a platform-neutral order, or provide both Windows and Linux options side-by-side.
Migrate
Continuous Deployment for containerized applications with Azure DevOps
...igrate/tutorial-app-containerization-azure-pipeline.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a notable Windows bias, especially in the 'Locate the artifacts' section, where only Windows file paths and Windows-specific navigation instructions (File Explorer, hidden items) are provided. There are no Linux/macOS equivalents or instructions for users running the Azure Migrate App Containerization tool on non-Windows systems. The artifact upload steps also implicitly assume a Windows environment. While the tutorial mentions deploying Java apps on Linux containers in the 'Next steps', the core workflow is presented from a Windows perspective.
Recommendations
- Add instructions for locating artifacts on Linux/macOS systems, including typical file paths and shell commands.
- Provide examples for navigating directories and handling hidden files on Linux/macOS (e.g., using 'ls -a' or 'find').
- Clarify whether the Azure Migrate App Containerization tool is supported on Linux/macOS, and if so, provide parity in documentation.
- When listing file paths or steps, present both Windows and Linux/macOS versions side by side.
- Explicitly mention any platform limitations or requirements early in the prerequisites section.
Migrate
Troubleshoot the Azure Migrate appliance
...s/blob/main/articles/migrate/troubleshoot-appliance.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation frequently presents Windows-centric troubleshooting steps, often referencing Windows tools (Control Panel, admin command prompt, Notepad, registry editor, WMI Control Panel) and PowerShell commands for diagnostics and remediation. Windows examples and instructions are often given before or in more detail than Linux equivalents. Some steps, such as time sync and host file editing, only mention Windows methods, with Linux alternatives missing or less emphasized. Linux instructions are present for some errors, but overall, Windows is prioritized.
Recommendations
- Provide Linux/macOS equivalents for all troubleshooting steps that currently only mention Windows tools (e.g., time sync, editing hosts file, restarting services).
- Ensure Linux examples are given equal prominence and detail as Windows examples, ideally side-by-side or in tabs.
- Include Linux-specific commands for checking time sync (e.g., timedatectl, ntpdate), editing hosts file (/etc/hosts), and restarting services.
- Add macOS notes where relevant, especially for physical server migration scenarios.
- Avoid referencing Windows tools (Control Panel, Notepad, registry editor) without Linux alternatives.
- Where PowerShell is used, provide equivalent Bash or shell commands for Linux.
Migrate
Troubleshoot issues with agentless and agent-based dependency analysis
...lob/main/articles/migrate/troubleshoot-dependencies.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. Windows-specific tools (PowerShell, WinRM, Registry Editor, WMI, Control Panel) are frequently referenced, often with detailed step-by-step instructions and troubleshooting guidance. Windows examples and remediation steps are generally presented before Linux equivalents, and some troubleshooting sections (e.g., registry edits, WMI, UAC, PowerShell installation) are Windows-only or lack Linux parity. Linux troubleshooting is present but less detailed, and some Linux steps are only mentioned as alternatives or in later sections.
Recommendations
- Provide Linux-first or parallel examples and troubleshooting steps alongside Windows instructions.
- Expand Linux troubleshooting guidance to match the depth of Windows sections (e.g., for agentless errors, permissions, environment variables, and agent installation).
- Include Linux equivalents for Windows tools (e.g., registry edits, WMI, UAC) or clarify when steps are Windows-only.
- Where PowerShell is referenced, offer Bash or shell alternatives for Linux users.
- Ensure that Linux SSH connectivity troubleshooting is as detailed as WinRM/PowerShell guidance.
- Add more explicit Linux error codes and remediation steps where currently missing.
- Balance the order of presentation so Linux and Windows are treated equally.
Migrate
Troubleshoot ongoing server discovery, software inventory, and SQL discovery
...s/blob/main/articles/migrate/troubleshoot-discovery.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation exhibits a notable Windows bias. Many troubleshooting steps and remediation actions are described primarily or exclusively in terms of Windows tools (e.g., PowerShell, WMI, Windows environment variables, Windows-specific UI paths). PowerShell commands are used for both validation and remediation, with only minimal Linux command examples (often just 'ls'). Linux troubleshooting is generally less detailed, and Linux-specific error remediation is sparse or absent. In several places, Windows instructions or tools are mentioned before Linux equivalents, and some Linux steps are only described in the context of using Windows to connect to Linux (e.g., installing OpenSSH on Windows). Web app discovery errors are exclusively focused on IIS/Windows, with no mention of Linux web servers.
Recommendations
- Provide equivalent Linux troubleshooting steps and commands for each remediation, not just 'ls' but also for validating connectivity, permissions, and service status.
- Include Linux-native command examples (e.g., systemctl, journalctl, netstat, ss, checking SSH configuration) alongside PowerShell/WMI for Windows.
- For error codes and troubleshooting tables, ensure Linux-specific causes and actions are included where applicable.
- For web app discovery, mention support (or lack thereof) for Linux web servers (e.g., Apache, Nginx) and provide relevant troubleshooting steps if supported.
- Avoid assuming the user is operating from a Windows environment; include instructions for running commands directly on Linux servers.
- When listing steps for both OSes, alternate or parallelize the instructions rather than always listing Windows first.
Migrate
Assess ASP.NET/Java web apps for migration to Azure Kubernetes Service
...ob/main/articles/migrate/tutorial-assess-aspnet-aks.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Powershell Heavy
Summary
The documentation demonstrates a Windows bias, especially in the ASP.NET assessment flow. It references Windows-specific requirements (e.g., Windows node pools for ASP.NET apps), optimization of Windows Dockerfiles, and does not provide equivalent Linux-focused examples or guidance. The cost breakdown and node pool recommendations are Windows-centric for ASP.NET, with no mention of Linux containers or node pools for .NET Core or Java apps. Linux tools, patterns, or examples are missing, and Windows-specific guidance is presented first or exclusively.
Recommendations
- Add explicit guidance and examples for Linux-based ASP.NET Core apps, including assessment flows and AKS node pool recommendations.
- Include Linux container optimization resources alongside Windows Dockerfile optimization.
- Clarify when Windows nodes are required and when Linux nodes can be used, especially for .NET Core and Java workloads.
- Provide parity in screenshots and step-by-step instructions for Linux/macOS users.
- Reference Linux tools and command-line patterns where relevant, not just Windows-centric approaches.
Migrate
Tutorial to assess SQL instances for migration to SQL Server on Azure VM, Azure SQL Managed Instance and Azure SQL Database
...docs/blob/main/articles/migrate/tutorial-assess-sql.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page exhibits a moderate Windows bias. It references Windows-specific technologies and patterns (e.g., Windows Server Failover Clusters, Cloud Witness, and links to Windows-specific best practices), and does not provide equivalent guidance or examples for Linux-based SQL Server deployments. Linux options are mentioned only briefly (e.g., RHEL/SLES licensing in Azure Hybrid Benefit), but there are no instructions, examples, or links for Linux failover, clustering, or migration scenarios. Windows terminology and links are presented first and exclusively in critical high availability/disaster recovery sections.
Recommendations
- Add explicit guidance and examples for assessing and migrating SQL Server instances running on Linux (e.g., Ubuntu, RHEL, SLES).
- Include links to Linux-specific best practices for SQL Server on Azure VMs, similar to the Windows-focused link provided.
- Describe high availability and disaster recovery options for SQL Server on Linux, such as Pacemaker clusters, and provide relevant configuration and migration steps.
- Ensure parity in licensing and cost optimization explanations for Linux environments, not just Windows.
- Where Windows-specific tools (e.g., Cloud Witness) are referenced, offer Linux equivalents or alternatives.
Migrate
Tutorial to assess SQL instances in VMware VMs for migration to SQL Server on Azure VM, Azure SQL Managed Instance and Azure SQL Database
...ob/main/articles/migrate/tutorial-assess-sql-vmware.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. Key high availability and disaster recovery sections reference Windows Server Failover Clusters and Cloud Witness, with links and configuration guidance focused on Windows. There is no mention of Linux clustering equivalents (e.g., Pacemaker, Corosync) or guidance for Linux-based SQL Server deployments. The Azure Hybrid Benefit section references Windows Server and SQL Server licenses, with only a brief mention of Enterprise Linux subscriptions (RHEL/SLES) and no further Linux-specific details. All referenced best practices and configuration links for SQL Server on Azure VM point to Windows-focused documentation. No Linux or cross-platform examples, tools, or migration patterns are provided.
Recommendations
- Add explicit guidance and examples for Linux-based SQL Server deployments, including clustering and high availability options (e.g., Pacemaker, Corosync).
- Include links to Linux-specific best practices for SQL Server on Azure VM.
- Clarify Azure Hybrid Benefit applicability for Linux SQL Server workloads, with licensing and cost examples.
- Ensure parity in migration scenarios and readiness checks for both Windows and Linux SQL Server instances.
- Where Windows-specific tools (e.g., Cloud Witness) are mentioned, provide Linux alternatives or note differences.
Migrate
Tutorial to assess web apps in VMware VMs for migration to Azure App Service
...ain/articles/migrate/tutorial-assess-webapps-vmware.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation focuses on assessing ASP.NET (IIS) and Java (Tomcat) web apps for migration from VMware VMs to Azure App Service. While both Windows (ASP.NET/IIS) and Linux (Java/Tomcat) scenarios are mentioned, examples, screenshots, and instructions are generic and do not provide explicit Linux-specific guidance or parity for other web servers (e.g., Apache, Nginx). The ASP.NET/IIS (Windows) scenario is presented first, and there are no examples or references for Linux tools, commands, or migration patterns beyond Tomcat.
Recommendations
- Add explicit examples and screenshots for Linux-based web apps (e.g., Apache, Nginx, other Java servers) in addition to Tomcat.
- Provide parity in instructions for Linux environments, including any differences in assessment, discovery, or migration steps.
- Include references to Linux-specific troubleshooting, compatibility checks, and remediation guidance.
- Ensure that Linux scenarios are presented with equal prominence and detail as Windows/IIS scenarios.
Migrate
Discover servers running in a VMware environment with Azure Migrate Discovery and assessment
...blob/main/articles/migrate/tutorial-discover-vmware.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Windows First
Summary
The documentation page exhibits moderate Windows bias. While it claims support for both Windows and Linux servers, critical setup instructions for the Azure Migrate appliance (especially when OVA deployment is not possible) rely exclusively on Windows tools and PowerShell scripts, with no Linux alternative provided. The VDDK installation path is described only for Windows (C:\Program Files\...), and instructions for deploying the appliance via script are Windows-only. Windows-specific requirements (e.g., PowerShell version, Windows authentication for SQL Server) are mentioned before Linux equivalents. Linux users may face friction or be unable to complete certain steps without workarounds.
Recommendations
- Provide equivalent Linux-based instructions and scripts for deploying the Azure Migrate appliance when OVA deployment is not possible.
- Document the VDDK installation process for Linux hosts, including default paths and extraction steps.
- Offer parity in authentication mechanisms and examples for Linux (e.g., Kerberos, password, SSH key) where Windows authentication is described.
- Ensure all examples and tool references (such as PowerShell) are accompanied by Linux alternatives (e.g., Bash scripts).
- Present Windows and Linux instructions side-by-side or clearly indicate OS-specific steps.
Migrate
Migrate VMware vSphere VMs with agent-based the Migration and modernization tool
...main/articles/migrate/tutorial-migrate-vmware-agent.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation exhibits a moderate Windows bias. Windows-specific instructions, tools, and examples are presented before or in more detail than their Linux equivalents. Key setup steps for the replication appliance are described using Windows Server 2016 as the default OS, with PowerShell mentioned for manual setup, but no Linux-based appliance setup is described. Registry edits for Windows are explained, while Linux instructions are limited to 'prepare a root account.' The Azure VM agent installation is automated for Windows but only recommended for Linux, with no details. Troubleshooting and post-migration steps reference Windows activation issues and Windows agent documentation, with Linux guidance being minimal or absent.
Recommendations
- Provide explicit instructions for setting up the replication appliance on a Linux-based VM, or clarify if this is unsupported.
- Include Linux-specific examples for Mobility service installation, such as using SSH, sudo, or package managers.
- Offer parity in troubleshooting guidance for Linux VMs post-migration (e.g., boot issues, agent installation, activation).
- Document how to manually install the Azure VM agent on Linux, with links to relevant guides.
- Balance the order of presentation so Linux and Windows instructions appear together, or alternate which is shown first.
- Clarify any limitations or differences for Linux VMs throughout the migration process.
Migrate
Migrate machines as physical servers to Azure with Azure Migrate and Modernize
.../migrate/tutorial-migrate-physical-virtual-machines.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation exhibits a moderate Windows bias. Windows Server and PowerShell are referenced first and most frequently, especially in appliance setup and credential examples. Registry and group policy checks are described only for Windows, and the installer workflow is centered around PowerShell scripts. Linux-specific instructions (such as credential requirements and agent installation) are mentioned but lack detailed step-by-step guidance or parity with Windows examples. Windows tools like SetupDiag and registry policies are referenced without Linux equivalents.
Recommendations
- Provide explicit Linux setup instructions for the replication appliance, including supported distributions and required packages.
- Include Linux shell (bash) examples for agent installation and appliance registration alongside PowerShell instructions.
- Document Linux-specific prerequisites and troubleshooting steps, such as SELinux/AppArmor, systemd services, or firewall configuration.
- Offer parity in credential setup examples, showing both Windows (admin) and Linux (root/sudo) workflows.
- Reference Linux diagnostic tools or logs analogous to Windows SetupDiag for OS upgrade troubleshooting.
- Clarify which steps are OS-agnostic and which require OS-specific handling, ideally in a tabbed or side-by-side format.
Migrate
Migrate VMware VMs agentless the Migration and modernization tool
.../blob/main/articles/migrate/tutorial-migrate-vmware.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page exhibits a notable Windows bias, especially in the 'Track and monitor' section, where all command-line examples use PowerShell and explicitly mention running commands on Windows machines. There are no Bash, Linux CLI, or cross-platform alternatives provided for monitoring or managing migrations. Windows-specific tools (e.g., SetupDiag) and upgrade options are mentioned, with Linux equivalents either omitted or referenced only briefly. Windows scenarios (e.g., Azure Hybrid Benefit for Windows Server, troubleshooting Windows activation) are described in detail, while Linux-specific guidance is minimal or absent.
Recommendations
- Provide equivalent Bash/CLI examples for Linux/macOS users, especially for migration monitoring and management tasks.
- Clarify whether the PowerShell commands can be run using PowerShell Core on Linux/macOS, and provide installation guidance if so.
- Include troubleshooting steps and upgrade options for Linux VMs, not just Windows (e.g., kernel/agent updates, activation issues).
- Mention Linux-specific migration considerations (e.g., supported distributions, post-migration steps for Linux VMs).
- Balance references to Windows tools (e.g., SetupDiag) with Linux alternatives or note when they are not applicable.
- Explicitly state cross-platform support for Azure Cloud Shell and its PowerShell/Bash environments.
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation for Azure Migrate shows a moderate Windows bias. Windows-centric features (such as Windows Server redeployment, Windows OS upgrade, and integration with Windows-only tools like PowerShell) are highlighted, often before or without equivalent Linux examples. Windows terminology and tools (PowerShell, IIS, Windows Server, System Center Operations Manager) are frequently mentioned, sometimes without Linux alternatives or parity in example coverage. Linux support is present, but often referenced as an add-on or in later updates, and Linux-specific migration scenarios or tools are less emphasized.
Recommendations
- Ensure Linux migration features are described with equal prominence and detail as Windows features.
- Provide Linux-specific examples and workflows (e.g., Bash scripts, Linux-native tools) alongside or before Windows/PowerShell examples.
- Highlight Linux migration scenarios (such as SELinux, systemd, Apache/Nginx web apps) and their Azure equivalents.
- Mention Linux authentication and management tools (e.g., SSH, sudo, Ansible) where Windows tools (PowerShell, RDP) are referenced.
- Add parity in agentless/agent-based migration instructions for Linux and Windows, including troubleshooting and best practices.
- Include Linux-specific security and compliance considerations in security insights and recommendations.
Migrate
Enhancing Web App Assessment With Code Scan Reports for Azure Migration
...lob/main/articles/migrate/add-copilot-code-insights.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation demonstrates a Windows bias in several areas. Instructions and links for installing and running AppCAT for Java projects explicitly reference Windows (e.g., 'tabs=windows'), and there are no Linux or macOS-specific examples or guidance. The .NET CLI installation and usage are presented generically, but Java assessment steps and references are Windows-centric. There are no shell/bash examples, nor are Linux-specific installation or usage patterns mentioned.
Recommendations
- Provide explicit instructions and examples for Linux and macOS environments, including AppCAT CLI installation and usage for Java projects.
- Include bash/shell command equivalents alongside PowerShell or generic CLI commands.
- Update links and references to documentation to include Linux/macOS tabs or sections where available.
- Add troubleshooting notes for common Linux/macOS issues (e.g., permissions, path formats, ZIP file handling).
- Ensure screenshots and UI references are not Windows-only, or supplement with Linux/macOS visuals where relevant.