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 876-900 of 918 flagged pages
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/tutorial-modernize-asp-net-appservice-code.md
.../migrate/tutorial-modernize-asp-net-appservice-code.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by explicitly requiring Windows PowerShell 4.0 on the source servers for migration, with no mention of Linux alternatives or support for migrating from Linux-based web servers. There are no examples or instructions for Linux environments, and the prerequisites and migration steps assume a Windows/IIS context exclusively.
Recommendations
- Clarify whether Linux-based ASP.NET (e.g., ASP.NET Core on Linux) web apps are supported or not. If not, state this explicitly.
- If Linux-based migrations are supported, provide equivalent instructions and tooling for Linux environments (e.g., Bash scripts, Linux CLI commands).
- Mention Linux prerequisites and tools alongside Windows requirements, or provide a comparison table.
- Include examples or notes for users running ASP.NET apps on Linux (such as those hosted on Apache, Nginx, or Kestrel).
- If migration from Linux is not supported, suggest alternative migration paths or tools for Linux users.
Create Pull Request
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 focuses on discovery methods in Azure Migrate but does not provide explicit examples or guidance for Linux environments. The guidance sections reference VMware and Hyper-V (the latter being Windows-centric) before mentioning 'physical & public Cloud servers,' which could include Linux but is not stated. There are no Linux-specific tools, commands, or scenarios discussed, and no mention of Linux workloads or discovery nuances.
Recommendations
- Include explicit references to Linux environments in the guidance sections, such as 'For Linux-based physical servers, follow these steps...'.
- Provide examples or notes on discovering Linux workloads (e.g., Apache, NGINX, PostgreSQL) alongside the existing SQL Server and ASP.NET examples.
- Clarify that the 'physical stack of appliance' supports Linux servers and describe any Linux-specific prerequisites or considerations.
- Add Linux-specific discovery and migration scenarios, including any required agents or tools.
- Ensure parity in workload lists by mentioning both Windows and Linux application types where relevant.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/how-to-build-a-business-case.md
.../main/articles/migrate/how-to-build-a-business-case.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation demonstrates a subtle Windows bias by referencing Windows-specific scenarios (such as end of support for Windows OS and SQL versions) and omitting explicit mention or examples for Linux workloads, tools, or migration considerations. There are no Linux-specific migration examples, nor are Linux tools or patterns discussed. The migration strategies and cost analyses are described in a way that implicitly assumes Windows-centric environments, with no parity for Linux-specific scenarios.
Recommendations
- Explicitly mention both Windows and Linux workloads throughout the documentation, including in feature descriptions and migration strategies.
- Provide examples or notes for Linux server discovery, assessment, and migration, including any differences in process or tooling.
- Highlight cost and modernization considerations for Linux workloads (e.g., migration to Azure Linux VMs, Azure Container Instances, or AKS for Linux).
- Reference end-of-support scenarios for popular Linux distributions alongside Windows, where relevant.
- Ensure screenshots and UI references show a mix of Windows and Linux workloads to reinforce cross-platform support.
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 consistently references Windows-centric virtualization platforms (VMware, Hyper-V) and Windows-based workloads (SQL Server, IIS/ASP.NET) without providing equivalent examples or guidance for Linux-based environments, workloads, or tools. There are no explicit Linux migration scenarios, tools, or troubleshooting steps, and Linux is not mentioned as a source OS or workload type, leading to a Windows-first and missing-Linux-example bias.
Recommendations
- Include explicit references to Linux servers as supported source environments in assessment scenarios.
- Add examples and troubleshooting steps for common Linux workloads (e.g., Apache, MySQL, PostgreSQL) in addition to Windows workloads (IIS, SQL Server).
- Mention Linux-specific considerations for performance data collection, such as required agents, permissions, or counters.
- Provide parity in documentation for Linux-based discovery, assessment, and migration, including links to relevant tutorials.
- Clarify that Azure Migrate supports both Windows and Linux servers, and provide guidance for mixed-environment assessments.
- Where agent or appliance installation is discussed, include Linux installation/requirements alongside Windows.
- Add FAQs or sections addressing common Linux migration blockers and how Azure Migrate handles them.
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
Missing Linux Example
Windows First
Summary
The documentation page provides detailed steps for migrating VMware servers to Azure using Private Link, but it implicitly assumes the Azure Migrate appliance is a Windows-based VM. There are no explicit Linux-specific instructions, examples, or troubleshooting steps. The only OS-specific mention is in the Azure Hybrid Benefit section, which refers to Windows Server. There are references to editing the 'hosts file' and running commands from 'the on-premises server hosting the Migrate appliance,' but no cross-platform (Linux) guidance is provided. No PowerShell or Windows tool commands are shown, but the lack of Linux parity is notable.
Recommendations
- Explicitly state whether the Azure Migrate appliance can be deployed on Linux, and if so, provide Linux-specific setup and troubleshooting instructions.
- When referencing editing the hosts file or verifying DNS resolution, include both Windows and Linux command examples (e.g., 'notepad C:\Windows\System32\drivers\etc\hosts' vs. 'sudo nano /etc/hosts'; 'nslookup' or 'dig' on Linux).
- In sections discussing Azure Hybrid Benefit, clarify applicability for Linux VMs (e.g., mention Azure Hybrid Benefit is only for Windows Server, and note any Linux migration licensing considerations).
- Add troubleshooting steps and connectivity verification commands for both Windows and Linux environments.
- If the Azure Migrate appliance is Windows-only, state this clearly at the beginning of the documentation.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/review-assessment.md
...e-docs/blob/main/articles/migrate/review-assessment.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows-first bias by referencing Windows Server as the only example of an unsupported OS and omitting any mention of Linux distributions or their compatibility. There are no Linux-specific examples, scenarios, or troubleshooting notes, and the language assumes Windows workloads by default.
Recommendations
- Include explicit examples and scenarios for both Windows and Linux servers throughout the documentation, such as referencing unsupported Linux distributions or kernel versions in the 'Conditionally ready for Azure' section.
- Add a table or list of supported and unsupported operating systems, including major Linux distributions (e.g., Ubuntu, CentOS, Red Hat, SUSE) and their versions.
- Provide Linux-specific remediation guidance and considerations, especially where Azure VM features (like Trusted Launch) have different requirements or support levels for Linux.
- Ensure that all sections discussing readiness, sizing, and security explicitly mention Linux alongside Windows, and clarify any differences in assessment or migration processes.
- Where examples are given (for instance, in CSV import or performance data), include Linux server names or properties to illustrate parity.
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 consistently refers to SQL Server migration scenarios and readiness in the context of 'SQL Server on Azure VM', 'Azure SQL Managed Instance', and 'Azure SQL Database', but does not mention or provide examples for SQL Server running on Linux or migration from Linux-based SQL Server deployments. There are no references to Linux-specific considerations, tools, or patterns, nor are there any examples or instructions that address Linux environments. The documentation implicitly assumes a Windows-based SQL Server source environment.
Recommendations
- Explicitly mention that SQL Server can run on both Windows and Linux, and clarify whether the assessment supports both platforms.
- Add examples or notes for users migrating SQL Server from Linux environments, including any differences in assessment, readiness, or migration steps.
- Include references to Linux-specific tools or commands where relevant (e.g., bash scripts, Linux authentication, file paths).
- If there are limitations or differences for Linux-based SQL Server migrations, document them clearly.
- Ensure screenshots and UI references do not assume only Windows-based SQL Server sources.
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, implicitly targeting Windows-centric environments. There are no Linux-specific examples, tools, or considerations provided, and the workflow assumes a Windows/Hyper-V context throughout. While there is a brief mention of Enterprise Linux subscriptions (RHEL and SLES) in the context of Azure Hybrid Benefit, there are no instructions or examples tailored for Linux VMs or administrators.
Recommendations
- Include explicit instructions or examples for assessing Linux VMs running on Hyper-V, highlighting any differences or additional considerations.
- Mention Linux-specific licensing and migration considerations earlier and more prominently, not just in the context of Azure Hybrid Benefit.
- Provide parity in examples, such as screenshots or command-line steps, that show both Windows and Linux VM scenarios.
- Clarify in the prerequisites or introduction that the process applies to both Windows and Linux VMs, and link to Linux-specific guidance if available.
- If any steps differ for Linux VMs (e.g., agent installation, performance data collection), document those differences clearly.
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 mention of ASP.NET/IIS (Windows) and Java/Tomcat (Linux/Java) web apps, but the actual step-by-step examples and screenshots are generic and do not show any Linux-specific tools, commands, or patterns. There is no explicit demonstration of Linux-based web app assessment workflows, and the documentation does not mention or show Linux-native environments, tools, or shell commands. The structure and terminology (e.g., 'Servers', 'Appliance') are platform-neutral, but the lack of Linux-specific examples or references constitutes a subtle Windows-first and missing Linux example bias.
Recommendations
- Add explicit step-by-step examples for assessing Linux-based web apps (e.g., Node.js, PHP, Python on Apache/Nginx) in addition to Java/Tomcat.
- Include screenshots and walkthroughs that show Linux server environments and Linux-native tools (e.g., bash commands, Linux file paths).
- Mention and demonstrate the assessment of web apps running on popular Linux web servers (Apache, Nginx) and frameworks.
- Ensure parity in the depth and clarity of instructions for both Windows (IIS/ASP.NET) and Linux (Tomcat/Apache/Nginx) scenarios.
- Where platform-specific steps differ (e.g., agent installation, prerequisites), provide clear, side-by-side instructions for both Windows and Linux.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/tutorial-modernize-asp-net-appservice-code.md
.../migrate/tutorial-modernize-asp-net-appservice-code.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by explicitly requiring Windows PowerShell 4.0 on the source servers for migration and makes no mention of Linux-based alternatives or scenarios. There are no examples or instructions for migrating from Linux-based web servers, nor is there guidance for users running ASP.NET Core apps on Linux. The documentation assumes a Windows/IIS environment throughout.
Recommendations
- Clarify whether Linux-based ASP.NET (Core) web apps are supported for migration using Azure Migrate, and if so, provide equivalent instructions or note any limitations.
- If Linux is not supported, explicitly state this in the prerequisites to set expectations for users.
- If Linux is supported, include examples or steps for Linux environments (e.g., using Bash, SSH, or Linux-native tools) alongside Windows/PowerShell instructions.
- Mention any Linux-specific requirements or tools (such as minimum supported distributions, required packages, or migration agents) if applicable.
- Ensure parity in post-migration steps by referencing Linux-specific configuration or troubleshooting resources where relevant.
Migrate
Support for VMware vSphere migration in Azure Migrate
...les/migrate/migrate-support-matrix-vmware-migration.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Windows and Linux support details for VMware vSphere migration in Azure Migrate, but there is a mild Windows bias. Windows examples and requirements are often listed before Linux equivalents, and PowerShell is mentioned as the primary scripting interface for appliance deployment and VM replication configuration, with no Linux CLI or automation alternatives referenced. However, Linux support is clearly documented and most requirements are covered for both platforms.
Recommendations
- Provide Linux CLI (e.g., Bash, Azure CLI) examples or mention automation options for Linux users alongside PowerShell references.
- Alternate the order of Windows and Linux instructions/examples to avoid consistently listing Windows first.
- Where PowerShell is referenced for appliance deployment or replication configuration, clarify if Linux users can use Azure CLI, Bash scripts, or other supported methods.
- Explicitly state cross-platform support for scripting and automation where applicable.
Migrate
Quickstart: Assess a Java Project using AppCAT 7
...ob/main/articles/migrate/appcat/appcat-7-quickstart.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides platform parity in download links, installation instructions, and usage examples for Windows, Linux, and macOS. However, there is a minor bias in listing Windows before Linux/macOS in the download table and in some explanatory text. All critical steps and examples are present for Linux/macOS, and there are no Windows-only tools or commands.
Recommendations
- Alternate the order of OSes in tables and instructions, or list Linux/macOS first in some sections to avoid implicit prioritization of Windows.
- Where possible, use neutral language (e.g., 'Extract the .zip or .tar.gz file as appropriate for your OS') rather than mentioning Windows first.
- Continue to provide explicit, parallel examples and instructions for all supported platforms.
Migrate
Migrate servers to Azure using Private Link through agent-based replications
...igrate-servers-to-azure-using-private-link-agent-based.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a mild Windows bias. Windows Server and Windows-specific licensing (Azure Hybrid Benefit) are mentioned explicitly, while Linux is not referenced in equivalent detail. There are no explicit Linux/macOS examples, nor are Linux-specific migration considerations or commands provided. The documentation assumes familiarity with Windows-centric concepts (e.g., Windows Server subscriptions, Azure Hybrid Benefit), and does not offer parity for Linux users in terms of examples or troubleshooting steps.
Recommendations
- Add explicit references to Linux server migration, including any differences in agent installation, prerequisites, or troubleshooting steps.
- Include Linux/macOS-specific examples for tasks such as DNS configuration, agent installation, and verification of network connectivity (e.g., using dig, nslookup, or /etc/hosts editing).
- Clarify whether features like Azure Hybrid Benefit have Linux equivalents or note their Windows-only applicability.
- Provide links to Linux-focused migration guides or documentation where relevant.
- Ensure that instructions for manual steps (e.g., MySQL installation) include Linux commands and package manager options.
Migrate
Support for VMware vSphere migration in Azure Migrate
...les/migrate/migrate-support-matrix-vmware-migration.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation demonstrates mild Windows bias, primarily by listing Windows operating systems and requirements before Linux equivalents, referencing Windows-specific tools (such as PowerShell) for appliance deployment, and providing more detailed instructions for Windows VM connectivity (e.g., RDP and Windows Firewall) compared to Linux. PowerShell is mentioned as an interface for configuring replication and for deploying appliances, with no mention of Linux CLI alternatives. However, Linux support is well documented and most requirements and supported distributions are listed.
Recommendations
- Provide Linux CLI/bash alternatives to PowerShell commands and scripts for appliance deployment and replication configuration.
- Present Linux and Windows instructions in parallel or alternate their order to avoid Windows-first bias.
- Expand Linux-specific troubleshooting and connectivity guidance to match the detail given for Windows (e.g., SSH setup, firewall configuration).
- Mention cross-platform tools or clarify which steps can be performed from Linux/macOS hosts.
- Explicitly state when PowerShell is required and offer alternatives if possible.
Migrate
Assess physical servers for migration to Azure with Azure Migrate
...blob/main/articles/migrate/tutorial-assess-physical.md
Low Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation is generally platform-neutral in its instructions, but exhibits subtle Windows bias. Windows is mentioned first in the list of unsupported OSes, and the Azure Hybrid Benefit section provides more detail for Windows Server licenses than for Linux equivalents. There are no explicit Linux-specific examples, tools, or troubleshooting steps, and no mention of Linux command-line usage or considerations. The documentation does not provide parity in examples or guidance for Linux users, especially regarding licensing and cost estimation.
Recommendations
- Explicitly mention Linux distributions supported for assessment and migration, not just those unsupported.
- Provide examples or notes for Linux-specific scenarios, such as handling RHEL/SLES subscriptions and cost estimation.
- Include troubleshooting tips or considerations for common Linux migration issues (e.g., disk formats, network settings).
- Ensure parity in licensing guidance, detailing how Enterprise Linux subscriptions interact with Azure Hybrid Benefit.
- Add links or references to Linux migration best practices and documentation.
Low Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates mild Windows bias by listing Microsoft Hyper-V and VMware vSphere as primary examples of supported platforms, with no explicit mention or examples for Linux-based hypervisors (e.g., KVM, Xen) or Linux-specific migration scenarios. The migration and discovery examples focus on Windows-centric virtualization technologies and do not provide parity for Linux users. However, there is no exclusive use of Windows tools or PowerShell, and the documentation does mention agentless and agent-based approaches that could apply to Linux servers.
Recommendations
- Include explicit examples and guidance for migrating Linux servers, including those running on Linux-based hypervisors (e.g., KVM, Xen).
- Add Linux-specific migration scenarios and troubleshooting steps.
- Ensure that references to supported platforms and tools mention Linux environments alongside Windows and VMware.
- Provide sample commands or workflows for Linux users where appropriate.
Migrate
Quickstart: Assess a Java Project using AppCAT 7
...ob/main/articles/migrate/appcat/appcat-7-quickstart.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides parallel instructions and examples for Windows, Linux, and macOS users throughout, including download links, extraction instructions, and script usage. However, there is a minor 'windows_first' bias: in the download table, Windows is listed before Linux and macOS, and in some file structure and path examples, Windows paths are mentioned before or alongside Linux/macOS equivalents. All critical steps and examples are present for Linux/macOS users.
Recommendations
- Rotate the order of OS listings in tables and examples, or list Linux/macOS first to balance visibility.
- When showing file paths or environment variables, consider listing Linux/macOS first or presenting all OSes in parallel.
- Continue to ensure that all scripts and instructions are available and clearly documented for Linux/macOS users.
Migrate
Enable additional data collection for Arc-enabled servers
...w-to-enable-additional-data-collection-for-arc-servers.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation provides both Windows and Linux instructions for enabling additional data collection on Arc-enabled servers. However, in several places, Windows is mentioned first (e.g., 'Azure Migrate Collector for Windows' before '...for Linux'), and the extension names and examples consistently list Windows before Linux. The endpoint for data collection uses a Windows-centric domain ('migration.windowsazure.com'), and the overall pattern is to present Windows options before Linux, which may subtly reinforce a Windows-first mindset.
Recommendations
- Alternate the order of Windows and Linux instructions/examples throughout the documentation, or present them in parallel tabs to avoid implicit prioritization.
- Use neutral language when referring to extensions, e.g., 'Azure Migrate Collector for Windows or Linux' rather than listing Windows first.
- Explicitly state that all features and instructions apply equally to Linux and Windows, and highlight any differences or parity gaps.
- Consider providing a summary table comparing Windows and Linux support/features at the top of the page.
- Review endpoint naming and clarify that Linux is fully supported despite the 'windowsazure.com' domain.
Migrate
Migrate VMware servers to Azure by using Private Link
...https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/migrate-vmware-servers-to-azure-using-private-link.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation page demonstrates a subtle Windows bias by referencing Windows Server and Azure Hybrid Benefit specifically for Windows Server machines, without mentioning Linux equivalents or considerations. There are no explicit PowerShell-heavy sections, Windows-only tools, or examples, but the documentation does not provide Linux-specific guidance or parity in areas where Windows is mentioned.
Recommendations
- Include information about Azure Hybrid Benefit applicability for Linux VMs, or clarify that it is Windows-specific.
- Add notes or examples for migrating Linux VMs, including any OS-specific considerations (e.g., disk selection, compatibility, post-migration steps).
- Ensure that references to OS-specific features (like Azure Hybrid Benefit) are clearly marked as Windows-only, and provide equivalent guidance for Linux users where applicable.
- If there are any steps that differ for Linux VMs (e.g., DNS configuration, agentless migration support), explicitly document them.
Migrate
View and enable Azure Arc for discovered servers in Azure Migrate
...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, nor does it mention Windows or Linux tools directly. However, there is a notable omission: the process for running the onboarding script is described generically, without clarifying whether the script is for Windows (e.g., PowerShell) or Linux (e.g., Bash), nor are examples for both platforms provided. This lack of Linux-specific guidance may leave Linux administrators uncertain about how to proceed, indicating a subtle bias toward Windows by omission.
Recommendations
- Explicitly state whether the onboarding script is platform-agnostic or provide separate instructions/examples for Windows (PowerShell) and Linux (Bash/Shell).
- Include screenshots or command-line examples for both Windows and Linux environments to demonstrate parity.
- Mention any prerequisites or dependencies for running the script on Linux (e.g., curl, bash, sudo) and Windows (e.g., PowerShell version).
- Clarify automation methods for both platforms, such as using Ansible for Linux or PowerShell Remoting for Windows.
Migrate
Create an Azure VM assessment with Azure Migrate Discovery and assessment tool | Microsoft Docs
...blob/main/articles/migrate/how-to-create-assessment.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation does not provide any platform-specific examples, commands, or tool references. However, it lacks explicit mention of Linux-specific workflows, tools, or considerations, and does not offer parity for Linux users in terms of examples or troubleshooting. The instructions are generic and do not show bias toward Windows, but the absence of Linux-specific guidance may leave Linux administrators without tailored support.
Recommendations
- Add explicit examples or notes for Linux environments, such as how to discover Linux servers, any required agent installation steps, or troubleshooting tips.
- Include references to Linux command-line tools or scripts where relevant, alongside any Windows/Powershell equivalents.
- Clarify if the Azure Migrate appliance or assessment process has any platform-specific requirements or limitations for Linux servers.
- Provide links to Linux-focused documentation or guides for common migration scenarios.
Migrate
Discover SAP systems with Azure Migrate Discovery and assessment
...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 OS-specific examples, commands, or tooling, but it also does not mention or show how to collect SAP inventory data from either Windows or Linux systems. There is no explicit Windows bias in terms of examples, tools, or ordering, but the lack of guidance for Linux users (e.g., how to export SAP system data from Linux hosts) means Linux parity is not addressed.
Recommendations
- Add explicit instructions or examples for collecting SAP inventory data from both Windows and Linux servers, including sample commands or scripts for each platform.
- Mention common tools or methods for exporting SAP system information on Linux (e.g., shell commands, SAP utilities) and Windows (e.g., PowerShell, SAP GUI).
- Clarify that the process is OS-agnostic, or provide links to platform-specific guidance for both Windows and Linux environments.
- Include screenshots or sample data exports from both Windows and Linux systems to illustrate the process.
Migrate
View and enable Azure Arc for discovered servers in Azure Migrate
...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 platform-specific examples, commands, or scripts for enabling Azure Arc on discovered servers. There is no mention of Windows, PowerShell, or Windows-specific tools, but equally, there are no Linux-specific instructions or examples. The onboarding script is referenced generically, with no indication of OS-specific steps or parity. This omission may hinder Linux users who need clarity on how to run the onboarding script or automate Arc enablement on Linux systems.
Recommendations
- Explicitly state whether the onboarding script supports both Windows and Linux platforms, and provide separate instructions/examples for each.
- Include sample commands for running the onboarding script on Linux (e.g., using bash or shell), alongside any PowerShell/Windows examples if relevant.
- Mention any prerequisites or dependencies for Linux systems (such as required packages or permissions) when enabling Azure Arc.
- If automation is discussed, reference Linux-native automation tools (e.g., cron, systemd, Ansible) in addition to Windows tools.
- Add troubleshooting tips or links specific to Linux onboarding issues.
Migrate
Assess AWS instances for migration to Azure with Azure Migrate
...docs/blob/main/articles/migrate/tutorial-assess-aws.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation does not display overt Windows bias in terms of command-line examples, tools, or terminology. However, it lacks any OS-specific examples or guidance, and does not provide parity for Linux users (e.g., no mention of Linux-specific considerations, commands, or screenshots). The only OS-specific mention is in prerequisites, where SUSE Linux and Windows Server 2003 are excluded from support. There are no PowerShell, Windows tools, or Windows-first patterns, but the absence of Linux-specific instructions or examples constitutes a subtle bias.
Recommendations
- Add explicit examples or notes for both Windows and Linux AWS instances, especially where assessment results or migration steps may differ.
- Include screenshots or walkthroughs that show Linux instance assessment results, not just generic or Windows-centric ones.
- Mention any Linux-specific considerations (e.g., licensing, Azure Hybrid Benefit for RHEL/SLES, agent installation differences, or post-migration steps for Linux VMs).
- If any command-line or script-based steps are needed, provide both Windows (PowerShell/Command Prompt) and Linux (Bash/shell) examples.
- Clarify in the assessment review sections how Linux VMs are handled, especially regarding readiness, cost estimation, and Azure Hybrid Benefit.
Migrate
Discover SAP systems with Azure Migrate Discovery and assessment
...main/articles/migrate/tutorial-discover-sap-systems.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation provides a generic workflow for discovering SAP systems with Azure Migrate, but it lacks any platform-specific examples or guidance. There is no mention of Windows or Linux tools, commands, or procedures. However, the absence of any Linux-specific instructions or examples (such as collecting inventory from Linux-based SAP systems, using Linux shell commands, or addressing Linux file formats) means Linux users may find the guidance less actionable. The documentation assumes users will know how to collect SAP inventory data regardless of OS, which can disadvantage Linux administrators.
Recommendations
- Add explicit instructions or examples for collecting SAP inventory from Linux servers, such as using shell commands (e.g., lscpu, free, df, etc.) to gather hardware details.
- Include sample scripts or command-line snippets for Linux environments to help users fill out the template file.
- Clarify whether the import process and template are OS-agnostic, and if not, specify any OS-specific considerations.
- Provide parity by mentioning both Windows and Linux methods for exporting SAP system data, ensuring administrators on either platform have clear guidance.