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 726-750 of 918 flagged pages
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 page exhibits a moderate Windows bias. Windows Server and PowerShell are referenced first and most frequently in appliance setup instructions, credential examples, registry and group policy checks, and OS upgrade steps. Windows-specific tools (e.g., SetupDiag) and registry policies are discussed in detail, while Linux equivalents are either briefly mentioned or omitted. Linux instructions (e.g., for credentials, agent installation) are present but less detailed, and Linux-specific migration issues or troubleshooting are not covered. PowerShell is the only CLI method described for appliance setup, with no Bash or Linux shell alternatives.
Recommendations
- Provide Linux-specific step-by-step instructions for appliance setup, including Bash/shell alternatives to PowerShell scripts.
- Include Linux credential examples (e.g., using SSH keys or root/password) alongside Windows examples.
- Add troubleshooting guidance for common Linux migration issues (e.g., bootloader problems, SELinux/AppArmor, kernel compatibility).
- Document Linux registry/group policy equivalents, or clarify which steps are Windows-only.
- Ensure parity in OS upgrade instructions, including how to upgrade Linux distributions during migration.
- Reference Linux tools/utilities (e.g., log analysis, package managers) where relevant.
Create Pull Request
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 demonstrates a moderate Windows bias. Windows-specific instructions (such as registry edits and Windows Server deployment) are presented before or in more detail than Linux equivalents. The replication appliance setup is described as a Windows Server 2016 VM, with no alternative for Linux. PowerShell is mentioned as the manual setup method, with no Linux shell equivalent. Steps for Mobility service installation provide detailed Windows registry instructions, while Linux instructions are minimal (just 'prepare a root account'). Post-migration best practices discuss the Azure VM agent for Windows in detail, but only briefly mention Linux. There are no Linux-specific examples or troubleshooting steps, and Windows activation troubleshooting is called out explicitly.
Recommendations
- Provide equivalent Linux-based instructions for replication appliance setup, including shell script or manual setup steps for Linux VMs.
- Include Linux-specific examples for Mobility service installation (e.g., required packages, commands, troubleshooting).
- Add troubleshooting steps for common Linux migration issues (e.g., bootloader, kernel modules, networking).
- Ensure post-migration best practices include detailed guidance for Linux VMs (e.g., Azure VM agent installation, removing Linux-specific tools).
- Present Windows and Linux instructions in parallel, rather than Windows-first.
- Reference Linux documentation links for further reading, similar to Windows activation troubleshooting.
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 demonstrates a notable Windows bias, especially in sections related to monitoring and managing migration status. All command-line examples use PowerShell, with explicit references to running commands on Windows PCs and Windows PowerShell. There are no Bash, Linux CLI, or cross-platform alternatives provided. Windows-specific tools (e.g., SetupDiag, Windows Server OS upgrade) are mentioned without Linux equivalents. Windows options and terminology (e.g., Azure Hybrid Benefit for Windows Server) are described in detail, often before or instead of Linux options.
Recommendations
- Provide equivalent Bash/CLI examples for Linux/macOS users, especially for migration status monitoring (e.g., using Azure CLI commands).
- Clarify that Azure Cloud Shell supports both Bash and PowerShell, and show how to use Bash for migration tasks.
- Include Linux-specific migration and troubleshooting steps (e.g., activation, agent installation, OS upgrade guidance).
- Mention Linux tools or patterns where Windows tools (like SetupDiag) are referenced.
- Ensure parity in describing benefits and options for Linux VMs (e.g., Azure Hybrid Benefit, post-migration steps).
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Summary
The documentation page for Azure Migrate shows a moderate Windows bias. Windows Server and Windows-specific migration scenarios (including PowerShell usage and Windows OS upgrade features) are frequently mentioned, often before Linux equivalents. Windows tools and patterns (such as PowerShell scripts, Windows Server appliance setup, and IIS web app migration) are referenced more explicitly and in greater detail than Linux alternatives. Linux support is present, but typically as a secondary mention, and Linux-specific migration examples, troubleshooting, or tool references are less prominent.
Recommendations
- Ensure Linux migration scenarios (e.g., SSH authentication, Sudo/root setup, Linux web app migration) are described with equal detail and visibility as Windows scenarios.
- Provide Linux-first or Linux-parity examples for appliance setup, migration steps, and troubleshooting (e.g., Bash scripts, Linux CLI commands, SELinux/AppArmor considerations).
- Include explicit references to Linux tools and patterns (such as systemd, journalctl, Linux package management) where relevant.
- Balance PowerShell references with Bash or other Linux-native scripting examples.
- Highlight Linux-specific migration blockers, remediation steps, and best practices alongside Windows ones.
Migrate
Questions about Wave Planning in Azure Migrate
...ain/articles/migrate/common-questions-wave-planning.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation page lists PowerShell and Power BI as primary tools for exporting wave data, and mentions PowerShell before Azure CLI and REST APIs. There are no Linux/macOS-specific examples or tool recommendations, and the examples provided (e.g., PowerShell, Power BI) are more commonly associated with Windows environments.
Recommendations
- Provide explicit Linux/macOS examples for exporting wave data, such as using Azure CLI or REST APIs from Bash.
- List cross-platform tools (Azure CLI, REST APIs) before Windows-centric tools (PowerShell, Power BI) when describing options.
- Include sample commands for Azure CLI and REST API usage alongside PowerShell examples.
- Mention platform compatibility for each tool, clarifying which are available on Linux/macOS.
Migrate
Automate agentless VMware migrations in Azure Migrate
...lob/main/articles/migrate/how-to-automate-migration.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation is heavily biased towards Windows environments by exclusively using PowerShell scripts and Azure PowerShell modules for automation, with no mention of Bash, Linux, or cross-platform scripting alternatives. All examples, installation instructions, and workflow steps assume the use of PowerShell (.ps1 scripts), which is natively available only on Windows (though PowerShell Core is cross-platform, this is not clarified). There are no Linux/macOS-specific instructions or examples, and Windows tools and patterns are presented as the default and only option.
Recommendations
- Explicitly state whether the provided PowerShell scripts are compatible with PowerShell Core on Linux/macOS, and document any limitations or required modifications.
- Provide equivalent Bash or shell script examples for Linux/macOS users, or clarify if such automation is not supported.
- Include installation instructions for Azure PowerShell on Linux/macOS, and mention prerequisites such as PowerShell Core.
- Add notes or sections addressing Linux/macOS users, including troubleshooting tips or known issues.
- Consider providing cross-platform automation samples (e.g., using Azure CLI, Python, or REST API) where feasible.
Migrate
Automate migration of machines in Azure Migrate
.../blob/main/articles/migrate/how-to-migrate-at-scale.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation exclusively references PowerShell scripts (.ps1), provides links only to PowerShell sample repositories, and does not mention or provide examples for Bash, shell scripts, or cross-platform alternatives. All automation steps are described using PowerShell, which is natively available only on Windows (and optionally on Linux/macOS with extra setup). No Linux/macOS-specific instructions, tools, or parity examples are given.
Recommendations
- Provide equivalent Bash or shell script samples for Linux/macOS users.
- Explicitly mention PowerShell Core (pwsh) compatibility and provide installation instructions for non-Windows platforms.
- Include notes or sections on how Linux/macOS users can execute these scripts, including prerequisites and any required environment setup.
- Offer cross-platform CLI alternatives (e.g., Azure CLI) for key migration steps.
- Present examples for both Windows and Linux/macOS users, or clarify platform requirements up front.
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias, particularly in the section describing the use of Az CLI. It instructs users to open PowerShell as Administrator and run CLI commands, without mentioning Linux/macOS terminals or providing equivalent instructions for those platforms. The CLI examples are presented in a Windows-centric manner, and there is no explicit guidance for Linux or macOS users, which may cause friction for non-Windows users.
Recommendations
- Explicitly mention that Az CLI can be used on Linux/macOS terminals as well as Windows PowerShell.
- Provide example commands for Linux/macOS (e.g., using bash/zsh), or clarify that the commands are identical across platforms.
- Replace 'open PowerShell as Administrator' with platform-neutral language such as 'open your terminal with appropriate permissions'.
- Add notes or links to Az CLI installation instructions for Linux/macOS.
- Ensure screenshots and instructions do not assume a Windows environment unless strictly necessary.
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
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation exclusively uses Azure PowerShell for all command-line examples and references, with no mention of Azure CLI or Bash alternatives. All example links and code blocks are PowerShell-centric, and the instructions assume a Windows environment (e.g., file paths like C:\Users\Administrator\Downloads). There is no guidance for Linux/macOS users, nor are cross-platform tools or patterns discussed.
Recommendations
- Add equivalent Azure CLI (az) examples for all PowerShell commands, including resource creation, querying, and deployment.
- Include Bash shell examples and note any OS-specific considerations (e.g., file paths, authentication methods).
- Reference cross-platform documentation pages (e.g., Azure CLI guides) alongside PowerShell links.
- Explicitly state that the process can be completed on Linux/macOS and provide troubleshooting tips for non-Windows environments.
- Use neutral file paths in examples or clarify path differences for Linux/macOS.
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation presents Windows examples and instructions before Linux ones, with detailed command-line steps and screenshots for Windows (e.g., diskpart, PowerShell), while Linux instructions are less visual and rely on generic bash commands. Windows-specific tools and patterns (diskpart, PowerShell, registry editing) are highlighted, and Linux examples are less comprehensive, with fewer screenshots and less step-by-step guidance. Linux instructions often refer users to external distribution documentation for critical steps.
Recommendations
- Provide Linux examples and screenshots with equal detail and prominence as Windows, including step-by-step guidance for common distributions (e.g., Ubuntu, RHEL, SUSE).
- Include Linux-specific troubleshooting steps and visual aids (e.g., screenshots of terminal commands, config files).
- Present Windows and Linux instructions in parallel sections or side-by-side, rather than Windows-first.
- Offer explicit Linux command examples for all manual preparation steps, not just for select distributions.
- Reference Linux tools and patterns (e.g., systemctl, network configuration files) as directly as Windows tools.
Migrate
Support for physical server migration in Azure Migrate and Modernize
...s/migrate/migrate-support-matrix-physical-migration.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. Windows-specific tools and patterns (such as RDP and Windows Firewall) are described in greater detail and appear before Linux equivalents. The instructions for post-migration connectivity provide step-by-step guidance for Windows (including firewall and policy settings), while the Linux section is less detailed and omits common troubleshooting or configuration steps. Additionally, the replication appliance is described as being set up with Windows Server 2016 by default, with no mention of a Linux-based alternative.
Recommendations
- Provide Linux-first or side-by-side examples for all connectivity and firewall configuration steps (e.g., include iptables/firewalld/ufw commands for SSH).
- Clarify whether the replication appliance can be deployed on Linux, and if not, state this explicitly and consider providing a Linux-based option.
- Balance the level of detail between Windows and Linux sections, especially for post-migration access and troubleshooting.
- Include references to Linux tools and commands (e.g., systemctl for SSH service, SELinux/AppArmor considerations, etc.).
- Avoid presenting Windows instructions before Linux unless there is a technical reason.
Migrate
Support for Hyper-V migration in Azure Migrate
...es/migrate/migrate-support-matrix-hyper-v-migration.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Summary
The documentation page demonstrates a Windows bias by focusing exclusively on Hyper-V hosts running Windows Server, listing only Windows Server versions as supported host OS, and referencing Windows-specific tools and URLs (e.g., time.windows.com, Windows Firewall, RDP). Windows connection instructions are given before Linux, and Windows terminology (e.g., .NET Framework, Windows Firewall) is used throughout. There are no Linux/macOS host-side examples or instructions, and all migration tooling is described as being installed on Windows-based Hyper-V hosts.
Recommendations
- Explicitly state that Hyper-V migration tooling is only supported on Windows hosts, and clarify lack of Linux/macOS host support.
- If any Linux-based Hyper-V management or migration is possible, provide equivalent instructions and examples.
- Present Linux connection instructions before or alongside Windows instructions for parity.
- Where possible, use neutral terminology (e.g., 'firewall' instead of 'Windows Firewall') and provide cross-platform guidance.
- Add a section addressing Linux/macOS users who may be seeking migration options or clarify alternative approaches.
Migrate
Troubleshoot network connectivity issues | Microsoft Docs
.../articles/migrate/troubleshoot-network-connectivity.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a notable Windows bias. Command-line examples (such as nslookup) are shown exclusively with Windows-style prompts (e.g., 'c:\ >nslookup'), and PowerShell-specific tools like Test-NetConnection are referenced without Linux/macOS equivalents. There are no explicit Linux/macOS shell examples, and instructions for editing the hosts file are described in a Windows-centric manner. The documentation assumes a Windows environment for troubleshooting steps, potentially creating friction for Linux/macOS users.
Recommendations
- Provide equivalent Linux/macOS shell commands alongside Windows examples (e.g., use 'nslookup' or 'dig' with bash/zsh prompts).
- For PowerShell-specific commands like Test-NetConnection, offer alternatives such as 'nc' (netcat), 'telnet', or 'curl' for Linux/macOS.
- When referencing file edits (like the hosts file), include Linux/macOS file paths (e.g., /etc/hosts) and editing instructions.
- Use neutral command prompts (e.g., '$' or '#') or show both Windows and Unix-style prompts in code blocks.
- Explicitly mention that the steps apply to both Windows and Linux/macOS, and highlight any OS-specific differences.
Migrate
Azure Migrate Collector virtual machine extension reference
...migrate/migrate-virtual-machine-extension-reference.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation generally provides parity between Windows and Linux, with separate sections and examples for each OS. However, in several command examples (such as extension status, update, and removal), only the Windows extension name is shown, and Linux equivalents are omitted. Additionally, in some sections, Windows examples or references appear before Linux, indicating a subtle 'Windows-first' ordering bias.
Recommendations
- For every CLI or PowerShell example referencing the Windows extension, include the Linux equivalent (using AzureMigrateCollectorForLinux).
- In sections like 'Extension status and health', 'Update and removal', and 'Troubleshooting', provide both Windows and Linux commands/examples side by side or in parallel subsections.
- When listing OS-specific instructions, alternate the order or present both OSes together to avoid implicit prioritization.
- Explicitly state when a command or path applies to both Windows and Linux, or clarify differences.
Migrate
Onboard on-premises servers in VMware virtual environment to Azure Arc
...les/migrate/onboard-to-azure-arc-with-azure-migrate.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 and patterns (WinRM, PowerShell) are mentioned first and in greater detail, with explicit commands (e.g., 'winrm qc') and troubleshooting steps focused on Windows. Linux equivalents (SSH, root account) are referenced but with less detail, and Linux-specific commands or troubleshooting are not provided. Windows examples and requirements are consistently listed before Linux, and some steps (e.g., WinRM TrustedHosts) are only relevant to Windows, with no Linux parallel.
Recommendations
- Provide Linux-specific command examples (e.g., how to configure SSH for remote access, required SSH settings).
- Include troubleshooting steps and error codes specifically for Linux scenarios, such as SSH authentication failures.
- List Windows and Linux instructions side-by-side or in parallel sections to ensure equal visibility.
- Clarify which steps are Windows-only and provide Linux alternatives where possible (e.g., TrustedHosts for SSH known_hosts).
- Expand on Linux prerequisites (e.g., required shell, supported distributions, minimum SSH version).
Migrate
Common issues in Azure Migrate assessments
.../blob/main/articles/migrate/troubleshoot-assessment.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. Windows-specific tools and patterns (WinRM, WMI, Get-WmiObject cmdlet, application pools, IIS, ISAPI filters) are referenced frequently and often before or instead of Linux equivalents. Troubleshooting steps for Windows (e.g., WinRM TrustedHosts, WMI) are detailed, while Linux troubleshooting is less specific and lacks parity in example commands or tool references. Web app assessment errors focus almost exclusively on IIS/ASP.NET scenarios, with little mention of Java/Tomcat or other Linux-based web stacks.
Recommendations
- Provide Linux-specific troubleshooting steps and examples alongside Windows instructions (e.g., SSH configuration, relevant Linux commands for connectivity and permissions).
- Include Linux tool references (such as systemd, journalctl, SSH config, etc.) where Windows tools like WinRM and WMI are mentioned.
- Add parity for web app migration errors by including common issues and solutions for Java/Tomcat and other Linux-based web servers.
- Ensure that Linux examples are presented with equal prominence and detail as Windows examples.
- Where Windows commands (e.g., PowerShell, Get-WmiObject) are given, provide equivalent Linux shell commands or scripts.
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 by referencing Windows-specific instructions and links (e.g., 'tabs=windows' in URLs), and by omitting explicit Linux/macOS commands or examples for installing and running AppCAT CLI. The .NET tool installation is shown generically, but Java instructions and examples are only linked with Windows tabs, and there are no Linux/macOS equivalents or troubleshooting notes. The documentation does not mention platform-specific differences or provide parity for Linux/macOS users.
Recommendations
- Add explicit instructions and examples for installing and running AppCAT CLI on Linux and macOS, including any required dependencies or environment setup.
- Update all linked quickstarts and guides to include Linux/macOS tabs or sections, not just Windows.
- Where screenshots or step-by-step instructions reference Windows UI elements or file paths, provide Linux/macOS equivalents.
- Include troubleshooting notes for common Linux/macOS issues (e.g., permissions, path differences, CLI usage).
- Ensure that all referenced tools and extensions are confirmed to work cross-platform, and note any limitations.
Migrate
Overview of Azure Migrate Assessment Report
...e-docs/blob/main/articles/migrate/assessment-report.md
Medium 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 as the primary example of conditional readiness, mentioning Hyper-V (a Windows-centric hypervisor) before VMware, and omitting explicit Linux or macOS server examples or considerations. There are no Linux-specific readiness issues, tools, or migration patterns discussed, and no examples or guidance for Linux workloads are provided.
Recommendations
- Include examples of Linux server readiness issues (e.g., unsupported kernel versions, disk partitioning schemes).
- Mention Linux-specific migration considerations, such as differences in disk formats, network adapters, or OS support in Azure.
- Provide parity in examples by alternating or balancing Windows and Linux scenarios when discussing readiness, sizing, and performance coverage.
- Reference Linux hypervisors (e.g., KVM, Xen) where relevant, and clarify support for Linux workloads in assessment types.
- Add explicit notes or sections for Linux/macOS users, including troubleshooting tips and remediation guidance.
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. Windows-specific instructions (such as WMI Control configuration and user group assignments) are detailed with step-by-step GUI guidance and screenshots, while Linux instructions are more concise and command-line oriented. Windows examples and procedures are often presented before Linux equivalents, and SQL Server discovery is covered in depth with Windows authentication and T-SQL scripts, but there are no equivalent MySQL or PostgreSQL Linux database discovery scripts. Windows tools and patterns (WMI, WinRM, user group assignments) are described in detail, whereas Linux steps are summarized and lack parity in depth and troubleshooting guidance.
Recommendations
- Provide Linux instructions with equivalent detail, including troubleshooting steps, screenshots, and explanations for permissions and user setup.
- Present Linux and Windows examples side-by-side or in parallel sections to avoid Windows-first ordering.
- Include Linux database discovery scripts and examples for common platforms (e.g., PostgreSQL, MariaDB) to match the depth of SQL Server coverage.
- Add more context and guidance for Linux-specific tools and patterns (e.g., sudoers, systemd, SELinux/AppArmor considerations).
- Ensure that all critical tasks (such as guest user setup, permissions assignment, and troubleshooting) have Linux equivalents and are not Windows-only.
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation for the Azure Migrate appliance demonstrates a notable Windows bias. Deployment and management instructions rely heavily on PowerShell scripts, with no mention of Bash, shell, or Linux-native alternatives. Troubleshooting and certificate management steps are exclusively described using Windows tools (e.g., certificate manager, group policy editor, Windows Update), and all screenshots and UI references are Windows-centric. There are no Linux/macOS-specific examples or guidance for appliance deployment, management, or troubleshooting, even though Linux credentials are supported for discovery.
Recommendations
- Provide Linux/macOS-specific deployment instructions, including Bash or shell script alternatives to PowerShell.
- Include troubleshooting steps for certificate validation and MSI signature checks using Linux tools (e.g., openssl, certutil, update-ca-certificates).
- Add guidance for managing appliance updates and certificates on Linux-based hosts, including equivalent commands and UI navigation.
- Ensure parity in screenshots and examples, showing both Windows and Linux environments where relevant.
- Clarify OS requirements and support for running the appliance on Linux or macOS, or explicitly state if only Windows is supported.
Migrate
Agent-based Migration in the Migration and Modernization Tool
...articles/migrate/agent-based-migration-architecture.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Powershell Heavy
Windows First
Summary
The documentation exhibits a notable Windows bias. It references Windows-specific tools and paths (e.g., registry keys, MMC snap-ins, C:\Program Files), and provides instructions only for Windows environments when discussing bandwidth throttling and antivirus exclusions. There are no Linux/macOS equivalents or examples, and the documentation assumes the use of Windows for administrative tasks.
Recommendations
- Provide equivalent instructions for Linux-based replication appliances and process servers, including relevant file paths and commands.
- Document how to install and manage the Mobility service on Linux servers, including command-line examples.
- Offer guidance on configuring bandwidth throttling and antivirus exclusions for Linux environments (e.g., using systemd, iptables, or Linux backup tools).
- Clearly indicate which features or tools are Windows-only, and suggest alternatives or workarounds for Linux/macOS users.
- When listing file paths or tools, include both Windows and Linux examples side by side.
Migrate
Questions about assessments in Azure Migrate
...icles/migrate/common-questions-discovery-assessment.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page for Azure Migrate assessments demonstrates a moderate Windows bias. It consistently references Windows-centric technologies (Hyper-V, IIS, SQL Server) and patterns, often mentioning Windows environments and tools before Linux equivalents. There are no explicit Linux-specific examples, troubleshooting steps, or mentions of Linux migration nuances. The documentation assumes familiarity with Windows server roles and does not provide parity for Linux scenarios, such as migrating Apache/Nginx web apps or Linux-based SQL databases.
Recommendations
- Add explicit examples and troubleshooting steps for Linux-based servers, such as Ubuntu, CentOS, or Red Hat.
- Include guidance for assessing and migrating Linux workloads (e.g., Apache, Nginx, MySQL, PostgreSQL) alongside Windows workloads.
- Mention Linux-specific discovery and assessment considerations, such as agent installation, performance counter collection, and readiness checks.
- Provide parity in documentation for web app migration by including scenarios for Linux-hosted web servers.
- Clarify any limitations or differences in assessment for Linux environments compared to Windows (e.g., supported counters, agent requirements).
Migrate
Common Questions About the Migration and Modernization Tool
.../articles/migrate/common-questions-server-migration.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page exhibits several instances of Windows bias. PowerShell and Windows-specific tools (NetQosPolicy, Windows Scheduled Tasks) are exclusively used in example scripts for throttling replication bandwidth, with no Linux equivalents or alternatives provided. Windows OS upgrade is explicitly supported, while Linux is not. Windows operating systems and scenarios are often listed first in tables and explanations. There are no Linux shell or tool examples for tasks like bandwidth throttling, nor guidance for Linux-based Azure Migrate appliances.
Recommendations
- Provide equivalent Linux shell (bash) examples for bandwidth throttling, such as using 'tc' or 'iptables' for traffic shaping.
- Mention and document Linux-native tools and approaches for managing replication bandwidth and scheduled tasks (e.g., cron jobs).
- Ensure Linux operating systems and scenarios are presented with equal prominence in tables and explanations.
- Clarify OS upgrade limitations for Linux and provide guidance or alternatives for Linux users.
- Add explicit instructions for deploying and managing the Azure Migrate appliance on Linux systems, if supported.
Migrate
Azure SQL assessments in Azure Migrate Discovery and assessment tool
...s/migrate/concepts-azure-sql-assessment-calculation.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page displays a moderate Windows bias. It frequently references Windows-centric technologies (such as IIS, Windows Server Failover Clusters, and Windows licensing), links to Windows-specific best practices, and omits explicit Linux migration scenarios or examples. Linux equivalents (e.g., Linux SQL Server, Linux-based clustering, or migration from Linux hosts) are not mentioned, and guidance is tailored to Windows environments. While some settings acknowledge Enterprise Linux subscriptions (RHEL/SLES) for licensing, practical migration steps, readiness checks, and high availability/disaster recovery guidance are focused on Windows tools and patterns.
Recommendations
- Add explicit examples and guidance for assessing and migrating SQL Server instances running on Linux (including Ubuntu, RHEL, SLES, etc.).
- Include links to best practices for SQL Server on Linux in Azure VMs, not just Windows.
- Provide parity in high availability/disaster recovery guidance for Linux-based SQL Server clusters (e.g., Pacemaker, Linux witness options).
- Clarify whether the Azure Migrate appliance supports discovery and assessment of SQL Server on Linux hosts, and document any limitations.
- Ensure that migration scenarios and readiness checks cover both Windows and Linux source environments equally.
Migrate
Build a migration plan with Azure Migrate
...b/main/articles/migrate/concepts-migration-planning.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. Windows Server and SQL Server are mentioned repeatedly, with specific migration and upgrade paths detailed for Windows workloads. The only OS upgrade example provided is for Windows Server, using Windows-specific Azure VM extensions and scripts. There is no equivalent guidance or tooling mentioned for Linux server upgrades or Linux-specific migration blockers. Cost optimization examples reference Windows licensing (Azure Hybrid Benefit) before Linux. No Linux-specific migration scenarios, blockers, or tools are described, and Linux is only briefly mentioned in the context of licensing.
Recommendations
- Add explicit examples and guidance for migrating Linux servers, including common blockers, readiness assessment, and post-migration steps.
- Provide details on how to upgrade Linux OS versions during migration, or clarify if this is unsupported.
- Include Linux-specific Azure VM extensions or migration tooling, if available.
- Balance cost optimization guidance by including Linux subscription migration details and parity with Windows licensing options.
- Ensure that migration prioritization and quick-win examples include Linux workloads, not just Windows Server and SQL Server.