Migrate
394
Total Pages
295
Linux-Friendly Pages
99
Pages with Bias
25.1%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
218 issues found
Showing 201-218 of 218 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 demonstrates a moderate Windows bias. Windows Server and PowerShell are mentioned first and most frequently for appliance setup and migration steps. Key instructions, such as copying installer files and running configuration wizards, reference Windows Server 2016 explicitly, with no parallel Linux instructions. Registry and group policy checks are Windows-specific, and the use of PowerShell scripts is emphasized for both VMware and physical server scenarios. Linux is mentioned in credential requirements and OS support, but there are no Linux-specific setup or troubleshooting examples, nor guidance for running the appliance or installer on Linux hosts.
Recommendations
- Provide explicit instructions and examples for deploying the replication appliance on Linux hosts, including supported distributions and prerequisites.
- Offer Linux shell script equivalents for PowerShell-based installation and configuration steps.
- Document Linux-specific troubleshooting steps and requirements (e.g., SELinux, firewall, systemd services).
- Ensure that references to Windows tools (e.g., SetupDiag, registry, group policy) are paired with Linux alternatives or clarify their applicability.
- Present examples for both Windows and Linux side-by-side, or clearly indicate when instructions are OS-specific.
Create Pull Request
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, particularly in its reliance on PowerShell for command-line examples and monitoring tasks. All CLI examples use PowerShell cmdlets, with explicit references to running them in Windows PowerShell or on Windows PCs. There are no Bash, Azure CLI, or Linux-native command examples provided, nor is there guidance for Linux/macOS users on how to perform equivalent monitoring or automation tasks. Windows-specific tools (e.g., SetupDiag) are mentioned, and Windows upgrade options are highlighted, while Linux-specific migration or troubleshooting steps are absent. The order of presentation and language also tends to prioritize Windows scenarios.
Recommendations
- Provide equivalent Azure CLI or Bash examples for all PowerShell commands, especially for monitoring migration status and troubleshooting.
- Explicitly state that Azure Cloud Shell supports Bash and show how Linux/macOS users can run migration monitoring commands using Azure CLI.
- Include troubleshooting steps and upgrade guidance for Linux VMs, not just Windows (e.g., handling Linux activation, OS upgrades, or agent installation issues).
- Mention cross-platform compatibility for tools and scripts, and clarify which steps are OS-agnostic.
- Balance references to Windows-specific tools (like SetupDiag) with Linux equivalents or note when they are not applicable.
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation for Azure Migrate demonstrates a moderate Windows bias. Windows Server and related technologies (PowerShell, IIS, System Center Operations Manager, Windows OS upgrade, Windows Server licensing, etc.) are frequently mentioned, often before Linux equivalents. Many examples and feature highlights focus on Windows-centric scenarios, and PowerShell is referenced as the primary automation tool. Linux support is present (e.g., SSH authentication, RHEL/SLES migration, Sudo for discovery), but Linux-specific examples, tools, and workflows are less prominent and often appear as secondary notes rather than primary guidance.
Recommendations
- Provide Linux-first or Linux-parity examples for migration, automation, and troubleshooting (e.g., Bash scripts, Ansible, Linux CLI commands).
- Highlight Linux migration scenarios (such as Apache, NGINX, Tomcat, PostgreSQL, MySQL) with equal detail as Windows/IIS/ASP.NET.
- Include explicit instructions for Linux users in sections referencing PowerShell, offering Bash/CLI alternatives.
- Ensure that feature announcements and walkthroughs mention Linux applicability and limitations alongside Windows.
- Add more Linux-focused troubleshooting and best practices content, especially for agent/appliance setup and authentication.
- Balance the order of examples and feature highlights so Linux and Windows are presented equally.
Migrate
Support for VMware vSphere migration in Azure Migrate
...les/migrate/migrate-support-matrix-vmware-migration.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation generally provides parity between Windows and Linux migration scenarios, listing supported Linux distributions and requirements in detail. However, there are minor signs of Windows bias: PowerShell is mentioned as the primary automation interface for configuring replication, and in several places, Windows instructions or references appear before Linux equivalents. Appliance deployment is described as possible via OVA or PowerShell script, but Linux CLI or automation alternatives are not mentioned. No critical migration steps are Windows-only, and Linux users can complete all tasks, but the prominence of Windows/PowerShell may create mild friction.
Recommendations
- When mentioning automation interfaces (e.g., PowerShell), also reference Azure CLI or Bash scripting alternatives for Linux/macOS users.
- Provide Linux/macOS command-line examples or instructions where PowerShell is referenced, especially for appliance deployment and bulk VM replication.
- Alternate the order of Windows and Linux instructions/examples, or present them side-by-side, to avoid implicit prioritization.
- Explicitly state that all migration steps can be performed from Linux/macOS environments, and link to relevant cross-platform tooling.
Migrate
Support for VMware vSphere migration in Azure Migrate
...les/migrate/migrate-support-matrix-vmware-migration.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides both Windows and Linux coverage for VMware vSphere migration to Azure, including supported OS versions, requirements, and post-migration steps. However, there is a mild Windows bias: PowerShell is mentioned as the only CLI automation method for configuring replication, and in some tables and sections, Windows instructions or details are listed before Linux equivalents. All critical Linux information is present, but Linux automation and tooling parity could be improved.
Recommendations
- When referencing automation or scripting (e.g., configuring replication), mention cross-platform tools such as Azure CLI or REST API if available, not just PowerShell.
- Where PowerShell is referenced for appliance deployment or configuration, clarify if PowerShell Core (pwsh) on Linux/macOS is supported, or provide equivalent Bash/CLI instructions.
- In tables and instructional sections, alternate the order of Windows and Linux details, or present them in parallel, to avoid the perception of Windows-first bias.
- Explicitly mention Linux/macOS support for any scripts or tools where applicable, and provide links to Linux-specific guidance if it exists.
Migrate
Support for VMware vSphere migration in Azure Migrate
...les/migrate/migrate-support-matrix-vmware-migration.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation exhibits mild Windows bias. PowerShell is the only CLI tool mentioned for scripting or automation, and Windows-specific tools and firewall instructions are often referenced before or instead of Linux equivalents. While Linux support is generally well-documented, Linux automation options (e.g., Bash, CLI) are not mentioned, and some instructions (like configuring the appliance or connecting after migration) give more detail for Windows scenarios or list them first.
Recommendations
- Include Bash/CLI examples or references for Linux/macOS users wherever PowerShell is mentioned, such as for deploying the appliance or automating replication.
- When listing post-migration connection steps, provide Linux instructions before or alongside Windows, not after.
- Mention Linux-native tools (e.g., iptables, firewalld) for firewall configuration, not just Windows Firewall.
- Where automation or scripting is referenced, clarify cross-platform options (e.g., Azure CLI, Bash scripts) and provide links or examples.
- Ensure that all sections referencing Windows tools or patterns have Linux/macOS equivalents or explicit notes if not applicable.
Migrate
Migrate VMware servers to Azure by using Private Link
...https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/migrate-vmware-servers-to-azure-using-private-link.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a mild Windows bias. Windows terminology (e.g., 'Windows Server', 'Windows Server subscriptions', 'hosts file') is used preferentially, and the Azure Hybrid Benefit section is explicitly focused on Windows Server. Instructions for manually updating DNS records reference editing the 'hosts file' on the Azure Migrate appliance, which is a Windows-centric pattern and does not mention Linux equivalents (e.g., /etc/hosts). No PowerShell commands are present, but there are no Linux/macOS-specific examples or clarifications, and Windows concepts are presented first or exclusively.
Recommendations
- When referencing manual DNS record updates, include instructions for both Windows (hosts file) and Linux (/etc/hosts) environments.
- Clarify whether the Azure Migrate appliance can run on Linux and, if so, provide Linux-specific setup or troubleshooting steps.
- In sections mentioning Azure Hybrid Benefit, note that it applies only to Windows Server and clarify options for Linux VMs.
- Where relevant, provide CLI examples for both Windows and Linux/macOS (e.g., Azure CLI, shell commands).
- Explicitly state platform requirements and supported operating systems for the Azure Migrate appliance.
Migrate
Quickstart: Assess a Java Project using AppCAT 7
...ob/main/articles/migrate/appcat/appcat-7-quickstart.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation presents Windows examples and terminology before Linux/macOS equivalents in several places, such as archive formats (.zip for Windows, .tar.gz for Linux/macOS), binary naming (appcat.exe vs appcat), and home directory paths (%USERPROFILE% vs ~/.appcat). However, Linux/macOS instructions and examples are present and complete, and parity is maintained in commands and download links.
Recommendations
- Present Linux/macOS and Windows instructions in parallel or in separate, clearly labeled tabs/sections to avoid implicit prioritization.
- List Linux/macOS examples first, or alternate the order in different sections.
- Use neutral language when referring to platform-specific details (e.g., 'On Windows, use .zip; on Linux/macOS, use .tar.gz').
- Ensure all examples and commands are provided for both platforms, and avoid assuming Windows as the default.
Migrate
Questions about Wave Planning in Azure Migrate
...ain/articles/migrate/common-questions-wave-planning.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation page references PowerShell and the Azure CLI as options for exporting Wave data, but PowerShell is mentioned explicitly and first, which may suggest a Windows-centric approach. There are no Linux/macOS-specific examples or clarifications, and PowerShell is a Windows-native tool, although it is available cross-platform. No Linux-specific tools or shell examples are provided.
Recommendations
- Explicitly mention that Azure CLI and PowerShell are cross-platform, and provide example commands for both.
- Include Linux/macOS shell examples (e.g., bash) for exporting Wave data.
- Clarify that REST APIs and Azure CLI can be used from any OS, and provide sample usage for Linux/macOS environments.
- Avoid listing PowerShell first, or alternate the order with Azure CLI to avoid implicit prioritization.
Low Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a mild Windows bias by listing Microsoft Hyper-V and VMware as primary examples of supported platforms, with no explicit mention or examples for Linux-based hypervisors or Linux server migration. There are no Linux-specific tools or command-line examples, and the migration scenarios focus on Windows-centric virtualization technologies. However, the page does state that agentless discovery and assessment works for 'servers running on any platform,' which partially mitigates the bias.
Recommendations
- Add explicit examples and documentation for migrating Linux servers, including common Linux hypervisors (e.g., KVM, Xen).
- Include Linux/macOS command-line examples where relevant (e.g., using Azure CLI or REST API from Linux).
- Clarify support for Linux server migration and provide links to Linux-specific migration guides.
- Ensure that Linux tools and patterns are mentioned alongside or before Windows-centric ones when describing supported scenarios.
Migrate
Support for VMware vSphere migration in Azure Migrate
...les/migrate/migrate-support-matrix-vmware-migration.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation demonstrates mild Windows bias in several areas. Windows examples and instructions (such as RDP, Windows Firewall, and SAN policy) are presented before Linux equivalents. PowerShell is mentioned as the primary automation interface for configuring replication, with no mention of Linux CLI alternatives. Appliance deployment instructions reference PowerShell scripts and OVA templates, but do not provide Linux shell or cross-platform automation examples. Windows-specific tools and patterns (RDP, Windows Firewall, SAN policy) are described in detail, while Linux instructions are more generic and less detailed.
Recommendations
- Provide Linux CLI (bash, shell script) examples for configuring replication, alongside PowerShell.
- When mentioning automation interfaces, clarify cross-platform options (e.g., Azure CLI, REST API) and provide usage examples for Linux/macOS.
- Present Linux and Windows instructions in parallel, rather than listing Windows steps first.
- Expand Linux-specific troubleshooting and configuration guidance to match the detail given for Windows (e.g., provide sample SSH configuration commands, SELinux handling, firewall setup).
- Include references to Linux-native tools and patterns where applicable (e.g., iptables, firewalld, systemd).
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
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page demonstrates a mild Windows bias, primarily through references to Windows-specific tools and patterns. For example, high availability and disaster recovery settings mention 'Cloud Witness' and 'Windows Server Failover Clusters' as recommended approaches, with links and configuration guidance focused on Windows environments. Linux equivalents (such as Pacemaker clusters or Linux witness options) are not mentioned. Additionally, the VM performance guidelines link points to a Windows-specific best practices page, and the Azure Hybrid Benefit section prioritizes Windows Server and SQL Server licenses, mentioning Enterprise Linux only as an aside. No explicit Linux/Powershell examples are present, but the overall framing and linked resources favor Windows scenarios first.
Recommendations
- Add explicit references and guidance for Linux-based SQL Server deployments, including high availability and disaster recovery options (e.g., Pacemaker, Linux witness configuration).
- Include links to Linux-specific performance guidelines for SQL Server on Azure VMs.
- Clarify Azure Hybrid Benefit applicability for Linux SQL Server scenarios and provide examples.
- Ensure that any referenced tools or patterns (e.g., Cloud Witness) are accompanied by Linux alternatives or a note about Linux support.
- Where possible, present Windows and Linux options side-by-side in relevant sections.
Migrate
Quickstart: Assess a Java Project using AppCAT 7
...ob/main/articles/migrate/appcat/appcat-7-quickstart.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides clear parity between Windows, Linux, and macOS in terms of downloads, installation instructions, and usage examples. However, there is a minor Windows bias in the ordering of file types and folder structure descriptions, where Windows (.zip, .exe) is mentioned before Linux/macOS (.tar.gz, no extension). The Linux/macOS script example is shown before the Windows batch file, but overall, the bias is minimal and does not impact usability for Linux/macOS users.
Recommendations
- Alternate the order of platform mentions so that Linux/macOS is sometimes listed first.
- Explicitly state that all platforms are equally supported and tested.
- Ensure that instructions for Linux/macOS are as detailed as those for Windows, including troubleshooting tips (e.g., file permissions).
- Consider grouping platform-specific instructions under clear tabs or headings to avoid perceived prioritization.
Migrate
Questions about Wave Planning in Azure Migrate
...ain/articles/migrate/common-questions-wave-planning.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation page for Wave Planning in Azure Migrate demonstrates mild Windows bias. While it mentions multiple cross-platform tools (Azure portal, Azure CLI, REST APIs, Power BI connector), PowerShell is listed explicitly and appears before Linux-friendly alternatives like Azure CLI. There are no Linux/macOS-specific examples or explicit parity notes, and PowerShell is referenced without clarifying its platform limitations.
Recommendations
- List Azure CLI before PowerShell when mentioning cross-platform options.
- Provide explicit examples for both Azure CLI and PowerShell commands for common tasks.
- Add notes clarifying PowerShell's platform support and recommend Bash/CLI alternatives for Linux/macOS users.
- Include screenshots or walkthroughs using Linux/macOS environments where relevant.
Migrate
Migrate VMware servers to Azure by using Private Link
...https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/migrate-vmware-servers-to-azure-using-private-link.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page exhibits mild Windows bias. Windows terminology (e.g., Azure Hybrid Benefit for Windows Server, references to Windows Server subscriptions) is present, and Windows-specific licensing options are discussed before any mention of Linux. There are no explicit Linux/macOS examples or instructions, and manual steps (such as editing the hosts file for DNS) are described generically but implicitly assume familiarity with Windows conventions. No Linux-specific commands, tools, or troubleshooting steps are provided.
Recommendations
- Include explicit instructions or examples for Linux-based Azure Migrate appliances, such as how to edit /etc/hosts for DNS resolution.
- Clarify that the Azure Migrate appliance can run on Linux and provide parity in setup and troubleshooting steps.
- Mention Linux licensing options (e.g., Azure Hybrid Benefit for Linux, if applicable) alongside Windows options.
- Provide screenshots or CLI examples for both Windows and Linux environments where manual configuration is required.
- Ensure that references to Windows-specific features (like Windows Server subscriptions) are balanced with Linux equivalents or a note if not applicable.
Migrate
Prepare machines for agentless migration with Azure Migrate
...in/articles/migrate/prepare-for-agentless-migration.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation page presents Windows-specific instructions and examples before Linux equivalents, uses Windows tools (diskpart, PowerShell) with screenshots and commands, and provides more detailed manual steps for Windows (e.g., registry hive, SAN policy, DHCP service) than for Linux. Linux instructions are present and reasonably detailed, but Windows examples are shown first and with more visual aids, and PowerShell is used for service management without Linux command equivalents.
Recommendations
- Alternate the order of Windows and Linux sections, or present both OS types in parallel for each step.
- Provide equivalent Linux command-line examples (e.g., for checking DHCP status, agent installation verification) alongside Windows PowerShell commands.
- Add screenshots or visual aids for Linux steps, such as verifying agent installation or network configuration.
- Ensure manual preparation instructions are equally detailed for both Windows and Linux, including troubleshooting tips.
- Reference Linux-specific documentation and tools where appropriate, not just Windows tools.
Migrate
Tutorial to assess web apps in VMware VMs for migration to Azure App Service
...ain/articles/migrate/tutorial-assess-webapps-vmware.md
Low Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a mild Windows bias. While it covers both ASP.NET (Windows/IIS) and Java (Tomcat) web apps, the examples and terminology are oriented toward Windows-centric environments. There are no explicit Linux-specific instructions, screenshots, or references to Linux-based web servers (e.g., Apache, Nginx) or Linux tools. The tutorial assumes the use of Azure Migrate appliance for VMware, but does not clarify Linux VM discovery or assessment nuances, nor does it provide parity for Linux-specific migration scenarios.
Recommendations
- Add explicit examples and screenshots for assessing Linux-based web apps (e.g., Java apps on Apache/Nginx, PHP, Node.js).
- Clarify whether the Azure Migrate appliance supports Linux VMs equally, and document any Linux-specific steps or limitations.
- Include references to Linux tools, commands, or migration patterns where relevant.
- Ensure that instructions for both Windows and Linux environments are presented side-by-side or in parallel pivots, not just Windows/IIS and Java/Tomcat.