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 801-825 of 918 flagged pages
Migrate
Overview of Assessments for Migration to Azure Database for MySQL (preview)
...rate/assessments-overview-migrate-to-azure-db-mysql.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing VMware and Microsoft Hyper-V environments first and exclusively in the migration context, with no mention of Linux-native hypervisors (such as KVM or Xen) or Linux-specific migration scenarios. There are no examples or instructions tailored for Linux environments, nor are Linux tools or command-line patterns referenced. The appliance deployment and discovery steps do not clarify Linux compatibility or provide Linux-specific guidance.
Recommendations
- Explicitly mention support for Linux-based hypervisors (e.g., KVM, Xen) and physical Linux servers in the assessment overview and migration scenarios.
- Provide Linux-specific examples and instructions for deploying the Azure Migrate appliance, including command-line steps and troubleshooting for common Linux distributions.
- Clarify compatibility and requirements for running the Azure Migrate appliance on Linux hosts, including supported OS versions and dependencies.
- Include references to Linux-native tools and patterns where relevant, such as system metrics collection (e.g., using top, vmstat, sar) and service management.
- Ensure parity in documentation structure by listing Linux environments alongside Windows/VMware/Hyper-V, rather than only after or not at all.
Create Pull Request
Migrate
Migrate to Azure Monitor Agent from Log Analytics agent
...main/articles/migrate/azure-monitor-agent-migration.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page describes migration from the Log Analytics agent (MMA) to Azure Monitor Agent (AMA) for both Windows and Linux, but all example steps and instructions are generic or implicitly Windows-focused. There are no explicit Linux-specific instructions, examples, or command-line references (such as shell commands or Linux package managers). The installation and management links default to Azure Portal instructions, which typically favor Windows environments, and there is no mention of Linux-specific patterns or troubleshooting.
Recommendations
- Add explicit Linux installation and migration examples, including shell commands and package manager instructions (e.g., apt, yum).
- Provide Linux-specific troubleshooting steps and notes about supported distributions.
- Include examples of running the migration and data collection scripts on Linux hosts, with sample commands.
- Clarify any differences in agent behavior or prerequisites between Windows and Linux environments.
- Ensure that links to installation guides include both Windows and Linux tabs or sections, and reference them directly in the migration steps.
Migrate
Overview of Azure Migrate assessment types
.../main/articles/migrate/concepts-assessment-overview.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page focuses on Azure Migrate assessment types and prerequisites but demonstrates a Windows-first bias. Examples and terminology prioritize Windows-centric virtualization platforms (VMware, Hyper-V, physical servers) and do not mention Linux-specific environments or provide Linux-specific examples. There is no reference to Linux tools, distributions, or considerations for Linux workloads, nor are there examples of Linux command-line usage or integration.
Recommendations
- Add explicit references to Linux workloads, including common Linux distributions and scenarios (e.g., migrating Ubuntu, CentOS, or Red Hat servers).
- Include examples or guidance for Linux-specific discovery and assessment, such as using SSH, Linux agents, or integration with Linux-native tools.
- Clarify that the Azure Migrate appliance supports both Windows and Linux servers, and provide parity in instructions and troubleshooting for both OS types.
- Mention Linux-specific considerations in performance data collection, such as differences in metrics or collection intervals.
- Provide sample assessment workflows for Linux environments alongside Windows/VMware/Hyper-V examples.
Migrate
Migrate VMware servers to Azure using Private Link through agent-based replications
...vmware-servers-to-azure-using-private-link-agent-based.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing Windows Server and Azure Hybrid Benefit specifically for Windows Server machines, without mentioning Linux equivalents. There are no explicit examples or instructions for Linux-based servers, nor any mention of Linux-specific migration considerations, tools, or patterns. The documentation assumes Windows environments in several places (e.g., Azure Hybrid Benefit, disk encryption references) and does not provide parity for Linux users.
Recommendations
- Include explicit instructions and examples for migrating Linux-based servers, such as guidance for installing the Mobility service on Linux VMs.
- Mention Linux-specific considerations, such as supported distributions, required packages, or differences in agent installation and operation.
- Clarify whether features like disk encryption, availability sets/zones, and Azure Hybrid Benefit have Linux equivalents or limitations.
- Provide troubleshooting steps and network connectivity verification commands for Linux (e.g., using dig, nslookup, or editing /etc/hosts), not just generic references.
- Add notes or sections that address common Linux migration scenarios, such as SELinux/AppArmor, systemd services, or file system compatibility.
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
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page focuses on migrating VMware servers to Azure using Private Link but demonstrates a Windows bias. It references Windows Server specifically in the Azure Hybrid Benefit section and does not provide any Linux-specific examples, instructions, or considerations. All operational guidance (such as editing the hosts file for DNS) is generic but implicitly assumes a Windows environment (e.g., Azure Migrate appliance, which is often Windows-based). There are no Linux command-line examples, nor is there mention of Linux-specific migration concerns or steps.
Recommendations
- Include explicit instructions and examples for Linux-based Azure Migrate appliances, such as how to edit /etc/hosts for DNS resolution.
- Mention Linux VM migration scenarios and any differences in process or requirements compared to Windows VMs.
- Provide parity in the Azure Hybrid Benefit section by referencing Linux licensing/subscription options if applicable, or clarify that it is Windows-specific.
- Add troubleshooting steps and verification commands for both Windows (PowerShell, CMD) and Linux (bash, nslookup, dig) environments.
- Ensure that any references to VM requirements, disk encryption, and availability options address both Windows and Linux VMs.
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing Windows Server as the primary example of conditional readiness and by omitting explicit Linux examples or guidance throughout. The only concrete example of an unsupported OS is 'an old version of Windows Server', and remediation guidance is described only for Windows. Additionally, tools mentioned for disk migration include 'robocopy' (Windows-specific) before 'azcopy' (cross-platform), and no Linux-native alternatives (e.g., rsync, dd) are discussed. There are no Linux-specific scenarios, issues, or recommendations, and no mention of common Linux migration patterns or challenges.
Recommendations
- Include explicit Linux examples in readiness categories, such as unsupported Linux distributions or kernel versions.
- Provide remediation guidance for Linux servers, e.g., steps for upgrading unsupported Linux OS or handling boot types (BIOS/UEFI) common in Linux.
- Mention Linux-native migration tools (e.g., rsync, dd, tar) alongside or before Windows tools like robocopy.
- Discuss common Linux migration challenges, such as handling LVM, different file systems (ext4, xfs), and SSH-based migration.
- Ensure that examples and guidance are balanced between Windows and Linux, or presented in a platform-neutral way.
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
Missing Linux Example
Summary
The documentation page consistently refers to SQL Server migration scenarios and readiness in terms of 'SQL Server on Azure VM', which is typically associated with Windows-based deployments. There is no mention of Linux-based SQL Server deployments, nor are there examples or guidance for users migrating SQL Server running on Linux. The terminology and recommendations assume Windows as the default platform for SQL Server, and there are no Linux-specific migration patterns, issues, or cost considerations discussed.
Recommendations
- Explicitly mention and provide guidance for SQL Server running on Linux, including migration scenarios and readiness checks.
- Add examples and screenshots that show assessments for SQL Server on Linux VMs.
- Discuss any differences in migration steps, issues, or cost estimates for Linux-based SQL Server deployments.
- Include notes or sections on platform-specific considerations (Windows vs. Linux) for SQL Server migration to Azure.
- Ensure parity in documentation by listing both Windows and Linux migration strategies and tooling where applicable.
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 demonstrates a Windows-first bias. The customer intent, examples, and migration scenarios focus primarily on Windows Server redeployment, with no explicit Linux-specific instructions, examples, or tool references. While the introduction mentions both Windows and Linux servers, all step-by-step guidance, screenshots, and migration tool references are generic or Windows-centric, and there are no Linux-specific migration patterns or examples provided.
Recommendations
- Add explicit Linux migration scenarios and examples, such as redeploying Ubuntu or CentOS servers.
- Include Linux-specific prerequisites, such as SSH key handling, package management, and configuration file differences.
- Provide screenshots and walkthroughs using Linux tools and environments (e.g., Bash, Linux terminal, Linux disk management commands).
- Mention Linux-specific considerations for disk detachment, application configuration, and post-migration validation.
- Ensure parity in documentation by alternating or balancing Windows and Linux examples throughout the guide.
Migrate
Performance vs As-is on-premises assessments
...docs/blob/main/articles/migrate/target-right-sizing.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Windows-centric virtualization platforms (VMware, Hyper-V, and 'physical servers') without mentioning Linux-specific hypervisors (such as KVM or Xen) or providing Linux command-line examples. There are no Linux-specific tools, patterns, or examples given, and the terminology and examples are oriented toward Windows environments.
Recommendations
- Include references to Linux hypervisors (e.g., KVM, Xen) and describe how performance data is collected from these platforms.
- Provide Linux-specific examples, such as how to prepare CSV files using Linux tools or how to gather performance metrics on Linux systems.
- Mention Linux-native storage types and considerations alongside Azure disk types.
- Clarify whether the appliance supports Linux workloads and, if so, detail any differences in data collection or assessment for Linux servers.
- Add sample commands or scripts for Linux environments where relevant (e.g., using top, vmstat, iostat for performance data collection).
Migrate
Assess physical servers for migration to Azure with Azure Migrate
...blob/main/articles/migrate/tutorial-assess-physical.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows-first bias: Windows Server is mentioned before Linux (specifically SUSE Linux) in prerequisites, and the only licensing/cost optimization example given is for Windows Server licenses, with Linux (RHEL/SLES) mentioned as a secondary note. There are no Linux-specific examples, screenshots, or guidance, and no mention of Linux tools, patterns, or considerations for assessment. The tutorial steps and assessment options are generic, but lack parity in Linux-specific details or troubleshooting.
Recommendations
- Add explicit Linux examples and screenshots, such as assessing RHEL, Ubuntu, or CentOS servers.
- Include Linux-specific considerations, such as handling different distributions, disk formats, or performance metrics.
- Provide guidance on licensing and cost optimization for Linux workloads (e.g., Ubuntu, Debian, CentOS), not just RHEL/SLES.
- Mention Linux-specific limitations or troubleshooting steps, if any, in the assessment process.
- Ensure that Linux is referenced equally alongside Windows throughout the documentation, not only as a secondary note.
Migrate
Tutorial to assess web apps for migration to Azure App Service
.../blob/main/articles/migrate/tutorial-assess-webapps.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation provides parallel coverage for both ASP.NET (Windows/IIS) and Java (Tomcat/Linux) web apps, but the ASP.NET/IIS scenario is presented first in the pivot and in examples. There are no explicit Linux command-line examples, nor are Linux-specific tools or patterns mentioned. The tutorial is generic and does not show platform-specific steps, but the ordering and lack of Linux-specific details indicate a subtle Windows-first bias.
Recommendations
- Alternate the order of ASP.NET and Java pivots or present them together to avoid Windows-first perception.
- Include explicit examples or screenshots for Linux/Tomcat environments, such as how to discover Java web apps on Linux servers.
- Add references to Linux-native tools or commands where relevant (e.g., shell commands for discovery, Tomcat configuration locations).
- Clarify any platform-specific prerequisites or differences in the assessment process for Linux-based web apps.
- Ensure parity in next steps and migration guides for both ASP.NET and Java/Tomcat scenarios.
Migrate
Import on-premises servers in a VMware environment using RVTools XLSX (preview)
...s/migrate/tutorial-import-vmware-using-rvtools-xlsx.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation exclusively references RVTools, a Windows-only tool, for exporting VMware inventory data. There are no mentions of Linux-compatible alternatives or instructions for Linux users. All examples and screenshots are based on workflows that require RVTools and the Azure portal, with no consideration for Linux-native tools or command-line options.
Recommendations
- Mention Linux-compatible alternatives to RVTools, such as open-source tools (e.g., govc, pyvmomi scripts) for exporting VMware inventory data.
- Provide instructions or examples for Linux users to generate compatible XLSX files, possibly via Python scripts or other cross-platform utilities.
- Clarify RVTools platform requirements and suggest workarounds for users who do not have access to Windows environments.
- Include a section comparing RVTools with Linux-native options, highlighting pros and cons for each platform.
- Add guidance for importing data from Linux-generated files, ensuring parity in the import workflow.
Migrate
Customer intent: As a systems administrator, I want to download the latest version of VMware, so that I can ensure my infrastructure is up to date and secure.
.../main/articles/migrate/includes/public-cloud-vmware.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Summary
The documentation page provides a download link for VMware and a SHA256 hash, but does not include any platform-specific instructions or examples. However, the download link is hosted on a Microsoft domain (go.microsoft.com), which may imply a Windows-first approach. There are no examples or instructions for verifying the SHA256 hash on Linux, nor any mention of Linux-specific tools or patterns.
Recommendations
- Provide platform-specific instructions for verifying the SHA256 hash, including examples for both Windows (e.g., PowerShell) and Linux (e.g., sha256sum).
- Include download instructions or links that are not exclusively hosted on Microsoft domains, or clarify cross-platform compatibility.
- Explicitly mention Linux support and provide parity in examples and tool references.
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, which are predominantly Windows-centric virtualization platforms. There is no mention of Linux-specific migration scenarios, tools, or examples, nor are Linux-native hypervisors (such as KVM or Xen) referenced. The examples and guidance are tailored to Windows-based infrastructure, with no parity for Linux environments.
Recommendations
- Add explicit support details and examples for migrating Linux servers, including common Linux distributions and workloads.
- Include information about migrating from Linux-native hypervisors (e.g., KVM, Xen) to Azure.
- Provide Linux command-line examples and tooling references where relevant (e.g., shell scripts, Linux agent installation).
- Clarify whether the Azure Migrate appliance and assessment tools support Linux servers and how to configure them.
- Ensure documentation covers both Windows and Linux migration scenarios equally, with parallel instructions and troubleshooting guidance.
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation page demonstrates a mild Windows bias by listing Microsoft Hyper-V and VMware vSphere as primary examples of supported platforms before mentioning AWS, GCP, and bare-metal servers. The migration scenarios and integrated tools focus heavily on Microsoft-centric technologies. There is no explicit Linux or open-source tooling mentioned, nor are Linux-specific examples provided. However, the page does state that agentless discovery works for 'servers running on any platform,' which is inclusive, and it explicitly notes that PowerShell is not supported for Private Link in Azure Migrate, recommending the portal or REST APIs instead.
Recommendations
- Add explicit Linux server examples and migration scenarios, such as migrating Ubuntu or CentOS servers.
- Include references to Linux-native tools or command-line patterns (e.g., Bash, SSH) where relevant.
- Present platform examples in a neutral order (e.g., 'VMware vSphere, AWS, GCP, Hyper-V, bare-metal') to avoid Windows-first perception.
- Provide sample REST API or CLI usage for Linux environments.
- Clarify support for Linux workloads and tools in agentless and agent-based migration scenarios.
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 providing installation and usage instructions for AppCAT CLI and Java assessment steps primarily or exclusively for Windows environments. References to installation and running AppCAT for Java projects link to pages with Windows-specific tabs, and there are no explicit Linux or cross-platform examples or commands. The .NET tool installation uses the dotnet CLI, which is cross-platform, but the Java instructions lack Linux parity. There are no PowerShell-specific commands, but the overall flow assumes Windows as the default environment.
Recommendations
- Add explicit Linux/macOS instructions and examples for installing and running AppCAT CLI, including relevant shell commands.
- Ensure linked quickstart and installation guides have Linux/macOS tabs or sections, and reference them directly.
- Include screenshots or terminal output from Linux environments where applicable.
- Clarify that the process is cross-platform where possible, and highlight any platform-specific differences or requirements.
- Provide troubleshooting steps for Linux/macOS users, such as file permission issues or CLI path differences.
Migrate
Migrate VMware servers to Azure using Private Link through agent-based replications
...vmware-servers-to-azure-using-private-link-agent-based.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing Windows Server and Azure Hybrid Benefit specifically for Windows Server machines, without mentioning Linux equivalents or benefits. There are no explicit Linux migration examples, nor are Linux-specific considerations (such as SELinux, systemd, or Linux guest credentials) discussed. All instructions and terminology assume a Windows-centric environment, with no parity for Linux users.
Recommendations
- Include explicit Linux migration examples, such as steps for migrating Linux VMs and handling Linux-specific configurations.
- Mention Linux guest credentials and any differences in installing the Mobility service on Linux machines.
- Clarify Azure Hybrid Benefit applicability for Linux (e.g., RHEL/SUSE subscriptions) or state if it is Windows-only.
- Add troubleshooting steps and network validation commands for Linux (e.g., using dig, nslookup, or editing /etc/hosts).
- Reference Linux tools and patterns alongside Windows ones, ensuring parity in instructions and terminology.
Migrate
Customer intent: As a systems administrator, I want to download the latest version of VMware, so that I can ensure my infrastructure is up to date and secure.
.../main/articles/migrate/includes/public-cloud-vmware.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Summary
The documentation provides a download link for VMware but does not specify platform-specific instructions or examples. The link is hosted on a Microsoft domain, which may imply a Windows-first approach. There are no Linux-specific download instructions, verification commands, or parity in tooling (e.g., PowerShell vs. Bash).
Recommendations
- Add explicit instructions for downloading and verifying the VMware package on Linux systems, including example commands (e.g., using wget/curl and sha256sum).
- Clarify platform compatibility and provide separate sections for Windows and Linux users.
- If PowerShell or Windows tools are mentioned elsewhere, ensure equivalent Bash/Linux commands are provided.
- Consider hosting or referencing downloads on platform-neutral domains if possible.
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Summary
The documentation focuses on VMware and Hyper-V scenarios, which are predominantly Windows-centric virtualization platforms. There is no mention of Linux-specific migration scenarios, tools, or examples, nor are Linux-native hypervisors (such as KVM or Xen) referenced. The examples and instructions are tailored to environments commonly associated with Windows, and there is an absence of Linux-first or Linux-specific guidance.
Recommendations
- Add explicit support information and examples for migrating Linux workloads, including details about supported Linux distributions and versions.
- Include instructions and examples for Linux-native hypervisors (e.g., KVM, Xen) and physical Linux servers.
- Provide parity in documentation by listing Linux migration tools and patterns alongside Windows/VMware/Hyper-V equivalents.
- Ensure that permissions, onboarding, and appliance setup steps include Linux-specific guidance, such as command-line instructions for Linux environments.
- Add links to Linux migration tutorials and troubleshooting guides in the Related content section.
Migrate
Overview of Assessments for Migration to Azure Database for MySQL (preview)
...rate/assessments-overview-migrate-to-azure-db-mysql.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing VMware and Microsoft Hyper-V environments first and exclusively when describing supported on-premises platforms for assessment. There is no mention of Linux-native hypervisors (such as KVM, Xen, or bare-metal Linux servers) or Linux-specific tooling. Additionally, there are no Linux command-line examples, nor is there guidance for deploying the Azure Migrate appliance on Linux systems, which are common for MySQL workloads.
Recommendations
- Explicitly mention support for Linux-based environments, including KVM, Xen, and bare-metal Linux servers, in the assessment overview and supported platforms.
- Provide Linux-specific instructions and examples for deploying and configuring the Azure Migrate appliance, including command-line steps and troubleshooting tips for Linux users.
- Include parity in examples and references, such as showing both Windows and Linux deployment scenarios, and avoid listing Windows platforms first unless they are the majority use case.
- Reference Linux-native tools and patterns where relevant, and clarify any limitations or differences in the assessment process for Linux environments.
Migrate
Migrate to Azure Monitor Agent from Log Analytics agent
...main/articles/migrate/azure-monitor-agent-migration.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page discusses migration from the Log Analytics agent (MMA) to the Azure Monitor Agent (AMA) for both Windows and Linux, but examples and instructions are generic and do not provide Linux-specific guidance or examples. There is a tendency to mention Windows and Windows-centric tools (e.g., Service Map, workspace navigation) without explicit parity for Linux environments, and no Linux command-line or configuration examples are provided.
Recommendations
- Include explicit Linux installation and migration steps, such as shell commands for agent installation and workspace association.
- Provide Linux-specific examples for querying data, such as using the Azure CLI or shell scripts.
- Clarify any differences in agent behavior or prerequisites between Windows and Linux environments.
- Add troubleshooting steps or notes relevant to common Linux distributions.
- Ensure that references to tools and navigation (e.g., Azure portal, Service Map) are accompanied by Linux-relevant instructions or alternatives.
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation page exhibits mild Windows bias by listing Microsoft Hyper-V alongside VMware as primary hypervisor platforms, and by referencing Windows-centric migration scenarios (Hyper-V, agent-based migration of physical servers, etc.) before Linux-specific examples. There is an absence of explicit Linux migration or tool examples, and the integrated tools section focuses on Azure and Microsoft offerings. However, the page does mention agentless discovery for 'any platform' and includes AWS/GCP migration, which broadens the scope beyond Windows.
Recommendations
- Add explicit examples and links for migrating Linux servers, including common Linux distributions and workloads.
- Include references to Linux-native tools or scripts for migration and assessment, where applicable.
- Balance the order of examples so that Linux and open-source platforms are mentioned alongside or before Windows/Hyper-V scenarios.
- Clarify that agentless and agent-based approaches support Linux servers, and provide documentation links for those workflows.
- If screenshots or UI instructions are given, ensure parity for Linux users (e.g., CLI examples using Bash or Azure CLI).
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
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing Windows-specific features (such as Azure Hybrid Benefit for Windows Server) and omitting Linux-specific migration considerations or examples. Steps and options related to Windows (e.g., Software Assurance, Windows Server subscriptions) are described in detail, while there is no mention of Linux VM migration nuances, Linux-specific tooling, or example commands for Linux environments. There are no PowerShell-heavy instructions, but the overall flow assumes Windows as the primary workload and environment.
Recommendations
- Add explicit instructions and examples for migrating Linux VMs, including any differences in process, prerequisites, or post-migration steps.
- Include Linux-specific considerations, such as handling SSH keys, OS disk selection for Linux, and post-migration validation steps (e.g., verifying Linux services).
- Provide sample commands for Linux environments (e.g., using Bash or Linux CLI tools) where manual steps are required, such as DNS configuration or connectivity validation.
- Clarify whether Azure Hybrid Benefit or other licensing options apply to Linux workloads, and mention any relevant Linux licensing or support details.
- Ensure that references to OS-specific features (like Windows Server Software Assurance) are balanced with Linux equivalents or a note that they are Windows-only.
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing Windows Server as the primary example of conditional readiness, and by mentioning Windows-specific tools (robocopy) for disk migration. There are no explicit Linux examples, nor is there mention of Linux-specific migration issues, tools, or readiness considerations. The remediation and migration guidance is focused on Windows scenarios, and Linux is not referenced in operating system compatibility, migration steps, or examples.
Recommendations
- Add explicit examples and guidance for Linux VMs, including common distributions (e.g., Ubuntu, CentOS, Red Hat) in readiness categories and remediation steps.
- Include Linux-specific migration tools (e.g., rsync, scp) alongside Windows tools like robocopy and azcopy when describing disk migration.
- Discuss Linux-specific compatibility issues (e.g., kernel versions, boot types, disk partitioning) in the Azure readiness section.
- Provide sample assessment results for both Windows and Linux VMs to illustrate parity.
- Reference Azure support for Linux operating systems and link to documentation on Linux VM migration best practices.
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 strongly oriented toward Windows Server migration, as evidenced by the customer intent, which specifically mentions Windows Server 2003. While the introduction claims support for both Windows and Linux servers, all examples, scenarios, and instructions are generic and do not provide any Linux-specific guidance, tools, or examples. There is no mention of Linux migration nuances, Linux disk handling, or Linux-specific IaC considerations. The documentation implicitly prioritizes Windows by focusing on Windows migration scenarios and omitting Linux parity.
Recommendations
- Add explicit Linux migration examples, including disk detachment and IaC generation for Linux servers.
- Include Linux-specific prerequisites, such as considerations for different filesystems, OS versions, and agent installation.
- Provide sample Terraform variable configurations and IaC templates for common Linux distributions (e.g., Ubuntu, CentOS).
- Mention Linux tools or scripts where relevant, and clarify any differences in the migration process for Linux versus Windows.
- Balance customer intent and scenario descriptions to include Linux migration use cases.