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 851-875 of 918 flagged pages
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/azure-monitor-agent-migration.md
...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 Azure Monitor Agent (AMA) for both Windows and Linux machines, but all procedural steps, examples, and scripts are presented generically or with a Windows-centric perspective. There are no explicit Linux-specific instructions, examples, or references to Linux tools or commands. The installation and management links default to Azure Portal instructions, which are typically more Windows-oriented, and there is no mention of Linux package managers or shell commands.
Recommendations
- Add explicit Linux installation instructions, including commands for common distributions (e.g., apt, yum, systemctl).
- Provide Linux-specific examples for running scripts and managing agents, such as bash commands or references to shell environments.
- Include screenshots or CLI steps for Linux environments, not just Azure Portal or Windows-based workflows.
- Mention and link to Linux troubleshooting guides or documentation for agent migration.
- Clarify any differences in agent behavior, prerequisites, or limitations between Windows and Linux systems.
Create Pull Request
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/assessments-overview-migrate-to-azure-db-mysql.md
...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 context of on-premises migration scenarios, with no mention of Linux-specific environments or tooling. There are no examples or guidance for Linux-native deployments, nor are Linux-specific migration considerations or tools discussed. The appliance deployment and discovery steps do not clarify Linux compatibility or provide Linux-centric instructions.
Recommendations
- Explicitly mention support for Linux-based environments (e.g., bare-metal Linux servers, KVM, Xen) in the assessment overview and migration scenarios.
- Provide examples or tutorials for deploying the Azure Migrate appliance on Linux hosts, including prerequisites and installation steps.
- Clarify whether the assessment tool supports Linux-native MySQL instances and detail any differences in data collection or compatibility checks.
- Include Linux-specific troubleshooting steps and considerations for performance data collection and connectivity.
- Balance references to Windows and Linux environments/tools throughout the documentation, ensuring Linux users are equally supported.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/migrate-vmware-servers-to-azure-using-private-link-agent-based.md
...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. The documentation does not provide parity in examples or instructions for Linux-based VMs, focusing instead on generic or Windows-centric migration steps.
Recommendations
- Include explicit examples and instructions for migrating Linux VMs, such as handling Linux guest credentials, agent installation steps for Linux, and troubleshooting Linux-specific issues.
- Mention Azure Hybrid Benefit alternatives or licensing considerations for Linux VMs (e.g., Red Hat, SUSE, Ubuntu), or clarify that the benefit is Windows-specific.
- Add references to Linux tools, patterns, and best practices (e.g., SSH, systemd services, Linux firewall configuration) where relevant.
- Provide parity in screenshots, CLI commands, and step-by-step guides for both Windows and Linux environments.
- Clarify any differences in agent installation, replication, or post-migration steps for Linux VMs.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/migrate-vmware-servers-to-azure-using-private-link.md
...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 Windows bias by referencing Windows-specific features (such as Azure Hybrid Benefit for Windows Server) and omitting Linux-specific migration considerations or examples. There are no explicit Linux or cross-platform command-line examples, and the only OS-specific benefit mentioned is for Windows Server. The instructions and tips (such as editing the hosts file) are generic but do not provide Linux-specific guidance (e.g., /etc/hosts).
Recommendations
- Add explicit Linux migration examples and considerations, such as handling Linux VM replication, OS disk selection, and post-migration steps for Linux workloads.
- Include Linux-specific instructions for tasks like DNS resolution (e.g., editing /etc/hosts instead of only referencing 'hosts file').
- Mention Azure Hybrid Benefit applicability or alternatives for Linux VMs, or clarify that it is Windows-only.
- Provide parity in troubleshooting steps, such as verifying network connectivity using Linux tools (e.g., dig, nslookup, curl) alongside any Windows tools.
- Ensure that any OS-specific features or benefits are clearly labeled as such, and provide equivalent guidance for Linux where possible.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/review-sql-assessment.md
...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 demonstrates a Windows bias by exclusively referencing SQL Server migration scenarios involving SQL Server on Azure VM, Azure SQL Managed Instance, and Azure SQL Database, all of which are traditionally associated with Windows environments. There is no mention of Linux-based SQL Server deployments, nor are there examples or guidance for users migrating SQL Server instances running on Linux. The documentation also omits any discussion of Linux-specific considerations, tools, or migration patterns, focusing solely on Windows-centric scenarios.
Recommendations
- Explicitly mention support for SQL Server running on Linux and clarify whether Azure Migrate assessments apply to Linux-based SQL Server instances.
- Add examples and guidance for assessing and migrating SQL Server instances deployed on Linux, including any differences in readiness checks, cost estimation, or migration issues.
- Include information about Linux-specific migration considerations, such as supported distributions, authentication methods, and any required configuration steps.
- If there are limitations or differences in assessment or migration for Linux-based SQL Server, document these clearly to inform users.
- Ensure screenshots and UI references do not imply Windows-only support, and update visuals to reflect Linux parity where applicable.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/target-right-sizing.md
...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 referencing Hyper-V and VMware as the primary hypervisors for performance data collection, with no mention of Linux-specific hypervisors (such as KVM or Xen) or Linux-native tooling. All examples and processes are described in terms of generic 'servers' or 'VMs', but the only explicit hypervisor references are Windows-centric. There are no Linux-specific examples, nor are Linux migration or assessment tools mentioned.
Recommendations
- Include examples and instructions for Linux environments, such as KVM or Xen hypervisors.
- Mention Linux-native tools or commands for performance data collection and migration.
- Provide explicit Linux server assessment scenarios alongside Windows/Hyper-V/VMware examples.
- Ensure parity in documentation by listing Linux options and patterns before or alongside Windows equivalents.
- Clarify whether the appliance supports Linux workloads and, if so, how performance data is collected from Linux systems.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/server-redeploy.md
...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 heavily focused on Windows Server redeployment, as indicated by the customer intent and the overall narrative. While the introduction claims to support both Windows and Linux servers, all examples, scenarios, and migration steps are described in generic terms or with explicit reference to Windows (e.g., 'Windows Server 2003'). There are no Linux-specific migration examples, tools, or considerations provided, and no mention of Linux-specific patterns or challenges. The documentation assumes familiarity with Windows-centric workflows and does not provide parity for Linux users.
Recommendations
- Add explicit Linux migration scenarios, including examples for common Linux distributions (e.g., Ubuntu, CentOS).
- Include Linux-specific prerequisites, such as assessment steps for Linux workloads and application configurations.
- Provide sample IaC templates and code snippets tailored for Linux server redeployment.
- Mention Linux-specific migration tools or scripts, and highlight any differences in the migration process compared to Windows.
- Ensure screenshots and walkthroughs include Linux server examples alongside Windows.
- Clarify any platform-specific limitations or considerations in the IaC generation and deployment process.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/tutorial-assess-hyper-v.md
.../blob/main/articles/migrate/tutorial-assess-hyper-v.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation is heavily focused on assessing Hyper-V VMs, which are a Windows-centric virtualization technology. There are no Linux-specific examples, tools, or patterns mentioned. The only mention of Linux is in the context of licensing (Azure Hybrid Benefit for RHEL/SLES), and Windows Server is referenced first. All instructions, screenshots, and terminology are tailored to Windows/Hyper-V environments, with no guidance for Linux-based hypervisors or VMs.
Recommendations
- Add parallel documentation or examples for assessing Linux-based VMs (e.g., KVM, Xen, or VMware running Linux guests).
- Include Linux-specific considerations, such as differences in performance data collection, disk types, and migration readiness.
- Provide sample CSV import files or appliance setup instructions for Linux environments.
- Mention Linux tools or commands where relevant (e.g., for collecting performance data or preparing Linux VMs for migration).
- Ensure that licensing and cost estimation examples include Linux scenarios equally and not just as a secondary note.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/tutorial-assess-physical.md
...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. While it mentions assessment support for both Windows and Linux servers, examples, terminology, and feature explanations are generic or Windows-centric. There are no explicit Linux-specific instructions, examples, or references to Linux tools or patterns. The only Linux mention is in the context of unsupported SUSE Linux servers and Azure Hybrid Benefit for RHEL/SLES licenses. No Linux command-line, configuration, or migration nuances are addressed.
Recommendations
- Add explicit Linux-based examples and instructions, such as how to assess Linux servers, including any differences in metadata or performance data collection.
- Include references to Linux tools or command-line patterns where relevant (e.g., how to collect performance data from Linux servers prior to migration).
- Clarify any differences in assessment properties or migration steps for Linux servers, such as licensing, disk types, or VM series recommendations.
- Provide troubleshooting tips or caveats specific to Linux server migration and assessment.
- Ensure parity in screenshots and UI walkthroughs by showing both Windows and Linux server scenarios.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/tutorial-assess-webapps-vmware.md
...ain/articles/migrate/tutorial-assess-webapps-vmware.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by focusing primarily on ASP.NET web apps running on IIS (Windows) and providing detailed steps and examples for assessing these workloads. While Java web apps on Tomcat (Linux) are mentioned, there are no Linux-specific instructions, examples, or screenshots. The tutorial omits any mention of Linux tools, commands, or patterns, and all examples are generic or Windows-centric, with Windows scenarios (ASP.NET/IIS) presented first.
Recommendations
- Add explicit Linux/Tomcat examples, including screenshots and step-by-step instructions for assessing Java web apps running on Linux VMs.
- Include Linux-specific prerequisites, such as required permissions, firewall settings, or agent installation steps for Linux VMs.
- Provide parity in troubleshooting and remediation guidance for Linux-based web apps, not just Windows/IIS scenarios.
- Ensure that both Windows and Linux migration scenarios are presented with equal detail and visibility, possibly alternating the order or using side-by-side comparisons.
- Reference Linux tools and commands where relevant, such as shell commands for discovery or assessment, and clarify any platform-specific differences in the assessment process.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/tutorial-import-vmware-using-rvtools-xlsx.md
...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 inventory export and does not mention any Linux alternatives or provide instructions for Linux users. All steps assume access to the Azure portal via a web browser, with no mention of CLI or cross-platform methods. There are no examples or guidance for Linux environments or users who may not have access to Windows tools.
Recommendations
- Mention and provide instructions for Linux-compatible inventory export tools, such as govc or PowerCLI on Linux, or other open-source alternatives.
- Clarify that RVTools is Windows-only and suggest steps for Linux users, such as running RVTools in a Windows VM or using alternative tools.
- Provide CLI-based import instructions (e.g., using Azure CLI or REST API) for users who may not use the Azure portal GUI.
- Add a section comparing RVTools with Linux-compatible tools, highlighting pros and cons and guiding users to choose the best fit for their environment.
- Include troubleshooting or FAQ for Linux users who cannot use RVTools directly.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/azure-monitor-agent-migration.md
...main/articles/migrate/azure-monitor-agent-migration.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Summary
The documentation claims support for both Windows and Linux, but all examples, instructions, and referenced scripts are generic or implicitly Windows-focused. There are no explicit Linux-specific instructions, examples, or troubleshooting notes. The prerequisites and installation steps do not mention Linux-specific commands, package managers, or differences, and the only mention of OS support is in the context of deprecation, with Windows listed before Linux.
Recommendations
- Add explicit Linux installation instructions, including package manager commands (e.g., apt, yum, zypper) for installing the Azure Monitor Agent and Dependency Agent.
- Provide Linux-specific examples for running scripts, managing services, and troubleshooting common issues.
- Include a section or notes highlighting any differences in migration steps or agent behavior between Windows and Linux.
- Ensure that all references to OSes alternate or list Linux first in some cases to avoid 'windows_first' ordering.
- Reference Linux tools (e.g., systemctl, journalctl, log file locations) where relevant, alongside or before Windows tools.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/best-practices-assessment.md
...lob/main/articles/migrate/best-practices-assessment.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by focusing exclusively on Windows-centric workloads and migration scenarios, such as ASP.NET web apps running on IIS and SQL Server, without mentioning or providing examples for Linux-based workloads or open-source databases/web servers. There are no Linux-specific migration scenarios, tools, or examples, and the only application migration scenario described is for IIS/ASP.NET, with no mention of Linux web servers (e.g., Apache, Nginx) or databases (e.g., MySQL, PostgreSQL).
Recommendations
- Include examples and guidance for migrating Linux-based workloads, such as web apps running on Apache or Nginx, and open-source databases like MySQL or PostgreSQL.
- Add explicit mention of Linux server discovery, assessment, and migration processes, including any differences or considerations compared to Windows.
- Provide parity in application migration scenarios by describing how to assess and migrate common Linux workloads to Azure (e.g., LAMP/LEMP stacks, Tomcat, Java apps).
- Reference Linux-compatible migration tools and patterns where relevant, and clarify any limitations or special steps for Linux environments.
- Ensure that all examples and best practices are inclusive of both Windows and Linux platforms, or clearly state if a feature is Windows-only.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/discovery-methods-modes.md
.../blob/main/articles/migrate/discovery-methods-modes.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Summary
The documentation does not provide explicit examples or guidance for Linux environments or tools. It mentions discovery of SQL Server and ASP.NET (typically Windows workloads) before MySQL, and does not clarify Linux-specific discovery steps or considerations. No Linux command-line or tooling examples are provided, and the guidance for physical/public cloud servers is generic, lacking Linux context.
Recommendations
- Add explicit examples and guidance for discovering Linux workloads (e.g., Linux VMs, Apache, NGINX, PostgreSQL).
- Include Linux-specific prerequisites or considerations for appliance deployment and import-based discovery.
- Provide parity in workload examples, such as mentioning Linux web servers and databases alongside Windows ones.
- If command-line or scripting is referenced, include Bash/Linux shell examples in addition to any PowerShell or Windows examples.
- Clarify support for Linux operating systems in each discovery method section.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/migrate-support-matrix.md
...s/blob/main/articles/migrate/migrate-support-matrix.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Summary
The documentation page focuses on Azure Migrate support for VMware and Hyper-V VMs, which are predominantly associated with Windows environments. There is no mention of Linux-specific migration scenarios, tools, or examples, nor are Linux-native patterns or permissions discussed. The content implicitly assumes a Windows-centric infrastructure by prioritizing VMware and Hyper-V, with no parity for Linux-based or open-source virtualization platforms (e.g., KVM, Xen).
Recommendations
- Include explicit references to Linux-based workloads and migration scenarios, such as support for KVM, Xen, or other open-source hypervisors.
- Provide examples or documentation links for migrating Linux servers (both physical and virtual) to Azure, including any Linux-specific considerations or limitations.
- Mention Linux-native tools or command-line patterns where relevant, and ensure that instructions are not solely tailored to Windows administrators.
- Clarify support for Linux guest operating systems in the assessment and migration process, including any differences in agent installation or data collection.
- Balance the order of presentation so that Linux and Windows scenarios are given equal prominence, or at least mention Linux scenarios alongside Windows/VMware/Hyper-V.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/migrate-servers-to-azure-using-private-link-agent-based.md
...igrate-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 describes the process of migrating servers to Azure using Private Link with agent-based replication. While it mentions migrating various types of servers (including VMware, Hyper-V, physical, AWS, and GCP VMs), it does not provide any explicit examples, commands, or instructions specific to Linux systems. The only OS-specific reference is to the Azure Hybrid Benefit, which is only applicable to Windows Server. There are no Linux-specific migration considerations, commands, or troubleshooting steps, and no mention of Linux authentication, service installation, or OS nuances. The documentation implicitly assumes a Windows-centric environment.
Recommendations
- Include explicit Linux migration examples, such as how to install and configure the Mobility Service on Linux servers.
- Provide Linux-specific troubleshooting steps (e.g., DNS resolution using dig/nslookup, editing /etc/hosts, systemd service management for the Mobility Service).
- Clarify any differences in agent installation, permissions, or prerequisites between Windows and Linux servers.
- Mention Linux-specific Azure Hybrid Benefit or licensing considerations, if any, or clarify that it is Windows-only.
- Add sample commands or scripts for both Windows (PowerShell/Command Prompt) and Linux (Bash/shell) environments where relevant.
- Ensure that references to OS-specific features (such as Windows Server licensing) are clearly marked as such, and provide equivalent Linux guidance where possible.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/migrate-vmware-servers-to-azure-using-private-link-agent-based.md
...vmware-servers-to-azure-using-private-link-agent-based.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Summary
The documentation does not provide any OS-specific examples or commands, but it references Windows Server and Azure Hybrid Benefit for Windows Server specifically, without mentioning Linux equivalents or considerations. There are no explicit Linux or cross-platform instructions, nor are there examples for Linux-based replication appliances or agent installation. The only OS-specific benefit (Azure Hybrid Benefit) is described for Windows Server, and no mention is made of Linux licensing or migration nuances. The documentation implicitly assumes a Windows-centric environment.
Recommendations
- Add explicit instructions or notes for Linux-based replication appliances, including any differences in setup or agent installation.
- Include examples or references for migrating Linux servers, such as handling Linux-specific OS disk selection, agent installation, or post-migration steps.
- Mention Azure Hybrid Benefit alternatives or considerations for Linux (e.g., bring-your-own-subscription, support for RHEL/SUSE, or other licensing models).
- Ensure that any OS-specific features or benefits are described for both Windows and Linux, or clarify when a feature is Windows-only.
- Provide links to Linux migration documentation or best practices alongside Windows references.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/appcat/appcat-7-release-notes.md
...main/articles/migrate/appcat/appcat-7-release-notes.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Heavy
Summary
The documentation page references Windows-specific issues and error messages more frequently and in greater detail than Linux or macOS. Known issues sections consistently highlight Windows-specific errors, such as the 'Watcher Error' and file handling problems, while Linux and macOS are only briefly mentioned (e.g., in a bug fix about file executability). There are no Linux- or macOS-specific troubleshooting steps, error messages, or parity checks, and no command-line examples for either platform.
Recommendations
- Include Linux and macOS-specific known issues, if any, or explicitly state if there are none.
- Provide troubleshooting steps and error message examples for Linux/macOS where relevant.
- Add parity checks or notes confirming that features and flags work as expected on Linux/macOS.
- Where Windows-specific errors are described, consider adding a comparative note about expected behavior on other platforms.
- Include example commands or usage patterns for Linux/macOS shells (e.g., bash/zsh) alongside any Windows or PowerShell examples.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/common-questions-discovery-assessment.md
...icles/migrate/common-questions-discovery-assessment.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by consistently referencing Microsoft-centric virtualization platforms (Hyper-V, VMware) and Windows-specific technologies (IIS, ASP.NET) without providing equivalent Linux examples or guidance. There is a lack of explicit mention or support for Linux workloads, tools, or migration scenarios, and no Linux-specific troubleshooting or assessment guidance is provided.
Recommendations
- Include explicit examples and guidance for assessing and migrating Linux servers (e.g., Ubuntu, CentOS, RHEL) alongside Windows/Hyper-V/VMware scenarios.
- Add troubleshooting steps and performance data collection guidance for Linux-based workloads, including common Linux performance counters and how to enable them.
- Mention Linux web application scenarios (e.g., Apache, Nginx, Java apps) in Azure App Service assessment sections, not just ASP.NET/IIS.
- Provide parity in documentation for agent installation, discovery, and assessment steps for Linux servers, not just Windows.
- Reference Linux tools and commands where relevant (e.g., systemd, top, sar, etc.) for performance troubleshooting.
- Clarify support for Linux distributions in all relevant assessment types and ensure Linux is mentioned wherever Windows/Hyper-V is discussed.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/discovery-methods-modes.md
.../blob/main/articles/migrate/discovery-methods-modes.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Summary
The documentation describes Azure Migrate discovery methods but does not provide explicit examples or guidance for Linux environments. The focus is on VMware, Hyper-V, and physical/public cloud servers, with no mention of Linux-specific tools, patterns, or discovery nuances. Hyper-V (a Windows-centric technology) is given equal prominence to VMware, and there are no Linux command-line or configuration examples. This may leave Linux users unclear about the process or requirements for their platforms.
Recommendations
- Add explicit references to Linux environments in the 'Physical & public Cloud servers' section, clarifying support for Linux OS and any special considerations.
- Include examples or notes on discovering Linux workloads, such as supported Linux distributions, required permissions, or agent installation steps.
- Mention Linux-specific tools or logs that may be relevant for discovery or troubleshooting.
- If applicable, provide sample CSV templates or inventory exports for Linux systems in the import-based discovery section.
- Ensure parity in documentation by including Linux-focused guidance alongside Windows/Hyper-V instructions.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/includes/public-cloud-vmware.md
.../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 using a Microsoft (go.microsoft.com) URL, which may suggest a Windows-centric approach. There are no Linux-specific instructions, examples, or alternative download methods (such as wget/curl commands or package manager references), nor is there mention of Linux compatibility or installation steps.
Recommendations
- Add Linux-specific download instructions, such as wget or curl commands.
- Include information about verifying the SHA256 hash using Linux tools (e.g., sha256sum).
- Mention Linux compatibility and provide installation steps for Linux systems.
- If possible, provide direct download links not tied to Microsoft infrastructure.
- Ensure parity by offering both Windows and Linux command-line examples for downloading and verifying the file.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/migrate-servers-to-azure-using-private-link-agent-based.md
...igrate-servers-to-azure-using-private-link-agent-based.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation provides a detailed, platform-agnostic overview of migrating servers to Azure using Private Link, but it implicitly prioritizes Windows environments. It references Windows Server and Azure Hybrid Benefit (which is Windows-specific) and omits explicit Linux or non-Windows OS examples, commands, or considerations. There are no Linux-specific instructions, shell commands, or troubleshooting tips, and the only OS-specific benefit mentioned is for Windows Server. This creates a subtle Windows-first and missing-Linux-example bias.
Recommendations
- Include explicit examples and instructions for migrating Linux servers, such as any differences in agent installation, prerequisites, or troubleshooting steps.
- Mention Linux-specific considerations, such as SELinux, systemd services, or common Linux distributions supported.
- Provide sample commands for Linux environments (e.g., shell commands for DNS resolution, editing /etc/hosts, or installing required packages).
- Clarify whether the Azure Hybrid Benefit step is only relevant for Windows and, if so, add a note about licensing for Linux VMs.
- Add troubleshooting tips or links relevant to common Linux migration issues.
- Ensure parity in terminology and examples so that Linux administrators feel equally supported.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/tutorial-assess-hyper-v.md
.../blob/main/articles/migrate/tutorial-assess-hyper-v.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation is focused exclusively on assessing Hyper-V VMs for migration to Azure, which inherently targets Windows environments. There are no Linux-specific examples, tools, or considerations provided, and the workflow assumes a Windows/Hyper-V context throughout. Linux VMs running on Hyper-V are not mentioned, nor are there any references to Linux-specific migration nuances or tools.
Recommendations
- Explicitly mention support for Linux VMs running on Hyper-V, if applicable, and provide examples or notes on any differences in assessment or migration steps for Linux guests.
- Include references or links to documentation for assessing and migrating Linux VMs, especially if there are additional considerations (e.g., licensing, Azure Hybrid Benefit for RHEL/SLES, agent installation).
- Where assessment properties mention Windows Server licenses (e.g., Azure Hybrid Benefit), ensure parity by also describing the process for Enterprise Linux subscriptions, and clarify any differences.
- If certain features or recommendations differ for Linux VMs (e.g., agent requirements, supported distributions), call these out in the relevant steps.
- Consider adding a section or callout for common Linux migration scenarios, or link to a Linux-focused migration guide for users with mixed environments.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/tutorial-assess-physical.md
...blob/main/articles/migrate/tutorial-assess-physical.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation is generally neutral in tone but exhibits subtle Windows bias. It references Windows Server versions explicitly in prerequisites and provides detailed guidance for Windows licensing (Azure Hybrid Benefit), while Linux is only mentioned in passing (SUSE Linux exclusion, RHEL/SLES licensing). There are no platform-specific command-line or tool examples, but the absence of Linux-specific considerations, examples, or troubleshooting steps results in a lack of parity.
Recommendations
- Include explicit examples or notes for both Windows and Linux server assessments, such as common considerations or known issues for each platform.
- Provide guidance or links for Linux-specific migration scenarios, such as handling different distributions, filesystems, or licensing models.
- Balance licensing discussions by elaborating on Linux licensing/subscription options (beyond just RHEL/SLES), and clarify how assessments differ for various Linux distributions.
- If there are platform-specific limitations or best practices (e.g., for performance data collection or agent installation), document them for both Windows and Linux.
- Add troubleshooting or FAQ sections that address common Linux migration/assessment issues, not just Windows-centric ones.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/tutorial-assess-webapps.md
.../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 ASP.NET (IIS/Windows) and Java (Tomcat/Linux) web apps, but the walkthrough and screenshots are generic and do not show any Linux-specific tools, commands, or examples. There is no explicit mention of Linux-based web servers (e.g., Apache, Nginx) or Linux-specific migration considerations. The structure and examples implicitly favor Windows/IIS scenarios by listing ASP.NET first and not providing Linux command-line or tooling details.
Recommendations
- Include explicit examples and screenshots for Linux-based web app assessments, such as Apache or Nginx servers.
- Provide Linux command-line instructions (e.g., Bash scripts) for discovery and assessment steps, where relevant.
- Alternate the order of ASP.NET and Java pivots, or provide a neutral introduction that does not prioritize Windows workloads.
- Mention Linux-specific considerations or prerequisites for migration (e.g., required packages, firewall rules, or service management differences).
- Add references or links to Linux migration best practices and troubleshooting guides.