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 901-918 of 918 flagged pages
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/how-to-arc-enable-inventory.md
...b/main/articles/migrate/how-to-arc-enable-inventory.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation does not provide any OS-specific onboarding script examples or mention of automation methods, but also does not specify Windows or PowerShell as the default. However, it lacks explicit Linux (bash, shell) examples or references, which may leave Linux users uncertain about parity or support.
Recommendations
- Include explicit examples for both Windows (PowerShell) and Linux (bash/shell) when referencing onboarding scripts.
- Clarify that the onboarding script can be run on both Windows and Linux machines, and provide links or references to OS-specific instructions.
- Mention common Linux automation tools (e.g., cron, systemd) alongside Windows tools when discussing automation methods.
- Add screenshots or walkthroughs showing the onboarding process on a Linux server.
Create Pull Request
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/tutorial-discover-sap-systems.md
...main/articles/migrate/tutorial-discover-sap-systems.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation does not provide any platform-specific examples, but it also does not mention or demonstrate how to collect SAP inventory data from either Windows or Linux systems. There is no explicit Windows bias in terms of examples, tools, or instructions, but the absence of guidance for Linux users (such as recommended commands or tools for exporting SAP inventory) may disadvantage Linux administrators.
Recommendations
- Add explicit instructions or examples for collecting SAP inventory data from both Windows and Linux SAP hosts.
- Include sample commands (e.g., PowerShell for Windows, shell scripts or SAP commands for Linux) for exporting the required inventory fields.
- Clarify that the process is platform-agnostic, or provide links to SAP documentation for both Windows and Linux environments.
- If there are differences in how SAP inventory is exported on Windows vs. Linux, document these differences and provide guidance for both platforms.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/migrate-support-matrix.md
...s/blob/main/articles/migrate/migrate-support-matrix.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation focuses exclusively on VMware and Hyper-V environments, which are typically associated with Windows-centric infrastructures. There are no examples, instructions, or references for Linux-based environments, Linux-specific migration scenarios, or Linux tools. The absence of Linux parity is notable, especially given the prevalence of Linux workloads in enterprise and cloud contexts.
Recommendations
- Add explicit sections or examples for assessing and migrating Linux physical servers and Linux VMs (e.g., KVM, Xen, or other hypervisors).
- Include references to Linux-native tools or commands for discovery, assessment, and migration (such as SSH-based discovery, Linux agent installation, or integration with Linux package managers).
- Provide step-by-step guides for Linux server onboarding, permissions setup, and troubleshooting, similar to those given for VMware and Hyper-V.
- Mention Linux-specific limitations, support matrices, and best practices for Azure Migrate.
- Ensure that Linux scenarios are presented with equal prominence to Windows/VMware/Hyper-V examples, ideally in parallel tables or sections.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/concepts-azure-vmware-solution-assessment-calculation.md
...ps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/concepts-azure-vmware-solution-assessment-calculation.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation does not display overt Windows bias in terms of examples, tools, or patterns. However, there is a subtle bias in the lack of explicit Linux-specific guidance or examples. The documentation references migration of ASP.NET apps running on IIS (a Windows technology) and SQL Server (commonly Windows-based), but does not provide parallel examples for Linux workloads or mention Linux-specific migration considerations. All instructions and examples are generic or VMware-centric, with no mention of Linux tools, Linux server assessment, or Linux-specific migration patterns.
Recommendations
- Add explicit examples of assessing and migrating Linux workloads (e.g., Apache, NGINX, MySQL, PostgreSQL) to Azure VMware Solution.
- Include guidance on how to handle Linux-specific OS compatibility issues, licensing, and readiness checks.
- Mention Linux distributions (e.g., RHEL, Ubuntu, CentOS) in assessment scenarios and clarify how the tool handles their metadata and performance data.
- Provide parity in migration tool guidance, such as considerations for Linux VMs when using VMware HCX or other migration solutions.
- Ensure that documentation covers both Windows and Linux environments equally in all assessment and migration steps.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/how-to-arc-enable-inventory.md
...b/main/articles/migrate/how-to-arc-enable-inventory.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation describes how to view and enable Azure Arc for servers discovered via Azure Migrate, but does not provide any OS-specific examples or mention of Windows or Linux tools. However, it lacks explicit examples or instructions for Linux systems, such as shell scripts or Linux-specific onboarding steps, and does not clarify whether the onboarding script is cross-platform or tailored for Windows (e.g., PowerShell). This omission may leave Linux users uncertain about the process.
Recommendations
- Explicitly state whether the onboarding script supports both Windows and Linux, and provide separate instructions or examples for each platform.
- Include sample commands for Linux (e.g., bash, shell) alongside any PowerShell or Windows instructions.
- Mention Linux-specific considerations (such as required dependencies or permissions) when running the onboarding script.
- Add screenshots or walkthroughs showing the onboarding process on a Linux server.
- Clarify automation options for Linux environments (e.g., using cron, systemd, or Ansible) in addition to any Windows automation methods.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/concepts-assessment-overview.md
.../main/articles/migrate/concepts-assessment-overview.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation provides a general overview of Azure Migrate assessment types and prerequisites, but it does not mention or provide examples specific to Linux workloads, tools, or discovery methods. The focus is on general concepts and on-premises environments (VMware, Hyper-V, physical servers), with no explicit Windows bias in terms of tools or commands, but there is a lack of Linux-specific guidance or parity.
Recommendations
- Include explicit references to Linux workloads in assessment types and discovery sources, clarifying support and any special considerations.
- Add examples or notes about assessing Linux servers, including any differences in data collection, prerequisites, or agent requirements.
- Mention Linux-specific tools or commands where relevant, or clarify that the Azure Migrate appliance supports both Windows and Linux equally.
- Provide links to Linux-focused tutorials or documentation for assessing and migrating Linux workloads.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/includes/scenario-banner.md
...blob/main/articles/migrate/includes/scenario-banner.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation page does not provide any platform-specific examples or instructions, but it also does not mention or demonstrate Linux tools, commands, or scenarios. This omission could lead to a perception of bias if future content only includes Windows-centric information or omits Linux-specific guidance.
Recommendations
- Ensure that future documentation includes explicit Linux migration scenarios and examples alongside Windows ones.
- Provide parity in tooling and command-line examples (e.g., include both PowerShell and Bash/CLI instructions where applicable).
- Reference Linux-specific considerations or tools (such as SSH, rsync, or Linux VM migration best practices) in addition to Windows tools.
- Clearly indicate when instructions are platform-agnostic, and call out any platform-specific steps for both Windows and Linux environments.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/azure-monitor-agent-migration.md
...main/articles/migrate/azure-monitor-agent-migration.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation discusses migrating from the Log Analytics agent (MMA) to Azure Monitor Agent (AMA) for both Windows and Linux machines, but does not provide any OS-specific examples, commands, or instructions. There are no explicit Windows-only tools or PowerShell scripts, but there is also a lack of Linux-specific guidance or examples, which may leave Linux users without clear instructions.
Recommendations
- Add explicit Linux installation and migration examples, including relevant shell commands or package manager instructions.
- Where scripts or commands are referenced, provide both Windows (PowerShell/Command Prompt) and Linux (Bash/shell) variants.
- Clarify any OS-specific prerequisites or steps, such as differences in agent installation or service management between Windows and Linux.
- Include links to Linux-specific documentation or troubleshooting guides alongside Windows equivalents.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/how-to-arc-enable-inventory.md
...b/main/articles/migrate/how-to-arc-enable-inventory.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation does not provide any OS-specific examples or scripts, but it also does not mention or show any Windows-specific tools, commands, or PowerShell usage. However, there is a lack of explicit Linux (or cross-platform) onboarding script examples, automation methods, or references to Linux-specific considerations. The onboarding script is referenced generically, with no indication if it is Windows-only, Linux-only, or cross-platform, which may leave Linux users uncertain about parity.
Recommendations
- Explicitly state whether the onboarding script is cross-platform, or provide separate instructions for Windows and Linux servers if needed.
- Include example commands or screenshots for running the onboarding script on both Windows (e.g., PowerShell) and Linux (e.g., Bash) systems.
- Mention any OS-specific prerequisites or troubleshooting tips for Linux environments.
- If automation methods differ by OS, provide guidance for both (e.g., using Ansible for Linux, PowerShell for Windows).
- Clarify in the prerequisites or overview that both Windows and Linux servers are supported, and link to relevant documentation for each.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/how-to-modify-assessment.md
...blob/main/articles/migrate/how-to-modify-assessment.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation does not display overt Windows bias in terms of mentioning Windows-specific tools, PowerShell, or Windows-first patterns. However, it lacks any explicit mention of Linux-specific considerations, examples, or parity in the assessment customization process. There are no examples or guidance for Linux workloads, nor are there references to Linux-specific migration scenarios, tools, or challenges. This omission may implicitly bias the documentation toward Windows-centric users or scenarios.
Recommendations
- Add explicit examples or notes about customizing assessments for Linux workloads, including any unique considerations for Linux VMs or physical servers.
- Mention support for Linux operating systems in the assessment process, and clarify if there are differences in data collection or recommendations for Linux vs. Windows.
- Include references or links to documentation about migrating Linux workloads, tools for Linux discovery/assessment, and any known limitations or best practices.
- If command-line or script examples are added, ensure both Windows (PowerShell/Command Prompt) and Linux (Bash/shell) examples are provided.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/troubleshoot-general.md
...ocs/blob/main/articles/migrate/troubleshoot-general.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation does not provide any OS-specific troubleshooting steps or examples, but it also does not mention Linux or Linux-specific issues, tools, or commands. This omission may leave Linux users without clear guidance, especially since Azure Migrate supports both Windows and Linux workloads.
Recommendations
- Include troubleshooting steps or examples specific to Linux environments where applicable.
- Explicitly mention if certain features or troubleshooting steps differ between Windows and Linux.
- Provide parity in documentation by referencing both Windows and Linux tools, commands, or logs when discussing troubleshooting.
- Add links to Linux-specific troubleshooting guides if they exist.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/tutorial-discover-sap-systems.md
...main/articles/migrate/tutorial-discover-sap-systems.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation provides a platform-neutral workflow for discovering SAP systems with Azure Migrate, but it lacks any OS-specific examples or guidance. There are no references to Windows, PowerShell, or Windows-only tools, but there is also no mention of Linux-specific commands, tools, or considerations. This omission may disadvantage Linux administrators, as SAP is commonly deployed on Linux, and the absence of Linux-centric examples or notes could be perceived as a bias of omission.
Recommendations
- Add explicit guidance for both Windows and Linux environments when collecting SAP inventory data, such as example commands for exporting system information from Linux servers (e.g., using shell scripts or SAP tools on Linux).
- Include notes or examples for filling out the template using data collected from Linux-based SAP systems, possibly referencing common Linux utilities (e.g., lscpu, free, df) for gathering hardware details.
- If any step requires OS-specific actions (such as exporting data from the SAP system), provide both Windows and Linux command-line examples.
- Clarify that the process is platform-agnostic if that is the case, and explicitly state that both Windows and Linux SAP systems are supported.
- Consider adding a troubleshooting section for common issues encountered on Linux-based SAP systems during the discovery process.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/quickstart-create-migrate-project.md
.../articles/migrate/quickstart-create-migrate-project.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation focuses exclusively on using the Azure Portal and ARM templates for deploying an Azure Migrate project, without providing any command-line examples. There are no references to Windows-specific tools, but there is also a lack of parity for Linux users: no CLI (Azure CLI, Bash) or PowerShell examples are provided, and no Linux-specific instructions or considerations are mentioned.
Recommendations
- Add Azure CLI examples for deploying the ARM template, which are cross-platform and work on Linux, macOS, and Windows.
- Include Bash shell commands for users who prefer scripting on Linux.
- Explicitly mention that the ARM template can be deployed using Azure CLI or PowerShell, and provide both sets of instructions.
- Ensure screenshots and instructions are not portal-only; provide equivalent command-line steps.
- Highlight any platform-specific considerations if they exist (e.g., authentication differences between Windows and Linux environments).
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/how-to-arc-enable-inventory.md
...b/main/articles/migrate/how-to-arc-enable-inventory.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation does not provide any OS-specific examples or instructions, but it also does not mention or show any examples for Linux systems, command-line interfaces, or automation methods. There are no explicit references to Windows, PowerShell, or Windows-only tools, but the lack of Linux-specific guidance or examples may leave Linux users uncertain about the onboarding process.
Recommendations
- Explicitly mention that the onboarding script supports both Windows and Linux servers, if applicable.
- Provide example commands or screenshots for running the onboarding script on both Windows (e.g., PowerShell or Command Prompt) and Linux (e.g., Bash).
- Clarify any OS-specific prerequisites or steps, such as required permissions or dependencies for Linux systems.
- Include links to Linux-specific onboarding documentation or troubleshooting guides.
- If automation methods are referenced, give parity between Windows and Linux automation tools (e.g., PowerShell and Bash scripts, Ansible, etc.).
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/migrate-support-matrix.md
...s/blob/main/articles/migrate/migrate-support-matrix.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation page focuses exclusively on virtualization platforms (VMware, Hyper-V, and physical servers) and does not provide any OS-level examples, commands, or tooling. However, there is a notable absence of Linux-specific guidance, examples, or references—especially regarding permissions, agent installation, or migration scenarios. There are no Windows-specific tools or PowerShell examples, but the lack of Linux parity (e.g., Linux command-line, sudo, or Linux migration nuances) is evident.
Recommendations
- Include explicit references to Linux servers in assessment and migration scenarios, clarifying support and any limitations.
- Add Linux-specific guidance for permissions, agent installation, and troubleshooting (e.g., using sudo, systemd, or relevant Linux commands).
- Provide Linux command-line examples alongside any Windows or PowerShell instructions in future documentation updates.
- Clarify whether physical server migration guidance applies equally to Linux and Windows, and highlight any OS-specific considerations.
- Link to or create documentation that addresses common Linux migration scenarios, including application and service discovery on Linux.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/concepts-assessment-overview.md
.../main/articles/migrate/concepts-assessment-overview.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation provides a general overview of Azure Migrate assessment types and prerequisites but does not include any OS-specific examples or instructions. However, it lacks explicit mention or examples for Linux workloads, tools, or considerations, focusing instead on generic terms like 'servers', 'VMware', 'Hyper-V', and 'physical servers'. There are no PowerShell or Windows-specific commands, but the absence of Linux-specific guidance or examples constitutes a subtle bias.
Recommendations
- Explicitly mention support for both Windows and Linux workloads in the assessment types and prerequisites.
- Include examples or notes on assessing Linux servers, such as supported Linux distributions, any required agents or configurations, and common migration considerations.
- Provide links to Linux-specific documentation or troubleshooting guides where relevant.
- Clarify in the discovery and assessment sections that both Windows and Linux operating systems are supported, and highlight any differences in data collection or assessment for Linux workloads.
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
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation does not provide any OS-specific examples, commands, or screenshots, but it implicitly assumes a Windows environment by omitting any mention of Linux-specific steps, tools, or considerations. There are no references to Linux shell commands, Linux-based replication appliances, or guidance for Linux administrators. The only OS-specific mention is in the context of Azure Hybrid Benefit for Windows Server, with no equivalent discussion for Linux systems.
Recommendations
- Add explicit instructions or notes for deploying and managing the replication appliance on Linux-based systems, if supported.
- Include Linux-specific examples for DNS configuration (e.g., editing /etc/hosts instead of 'hosts file' terminology, which is ambiguous).
- Clarify whether the replication appliance and Mobility service support Linux hosts, and provide links to Linux installation guides if available.
- Mention any Linux-specific prerequisites, troubleshooting steps, or differences in the migration process.
- Balance the Azure Hybrid Benefit section by noting any relevant licensing or migration considerations for Linux VMs.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/troubleshoot-general.md
...ocs/blob/main/articles/migrate/troubleshoot-general.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation page does not provide any OS-specific troubleshooting examples or instructions, but it also does not mention Linux or provide Linux-specific guidance. The absence of Linux examples or references may make Linux users feel unsupported, especially since Azure Migrate can be used for both Windows and Linux migrations.
Recommendations
- Add explicit troubleshooting sections or examples for Linux-based appliances and workloads.
- Ensure that links to troubleshooting guides include Linux-specific issues and solutions where applicable.
- Mention Linux support in the context of app discovery, assessment, and migration, clarifying any differences or limitations.
- Provide parity in troubleshooting steps for both Windows and Linux environments, or clearly state if a feature is Windows-only.