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 626-650 of 918 flagged pages
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/start-here-vmware.md
...e-docs/blob/main/articles/migrate/start-here-vmware.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a bias towards Windows environments by providing migration automation and command-line examples exclusively with Azure PowerShell, without mentioning or linking to equivalent Azure CLI or Linux-native tooling. There are no Linux-specific instructions or examples, and the use of PowerShell is assumed for automation, which may not be familiar or available to Linux users.
Recommendations
- Include Azure CLI examples alongside or in place of Azure PowerShell examples, especially for automation and command-line migration steps.
- Explicitly mention that migration steps can be performed from Linux or macOS environments, and provide relevant instructions.
- Where PowerShell is referenced, add notes or links to documentation on using Azure CLI or Bash scripts for users on non-Windows platforms.
- Ensure that any downloadable tools or scripts are cross-platform or provide alternatives for Linux users.
- Review linked tutorials to ensure Linux parity and update this overview page to reflect that parity.
Create Pull Request
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/tutorial-app-containerization-azure-pipeline.md
...igrate/tutorial-app-containerization-azure-pipeline.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by referencing only Windows file paths (e.g., C:\ProgramData\...), using Windows-specific navigation instructions (File Explorer, 'Hidden items'), and omitting equivalent Linux instructions or file paths. There are no examples or guidance for users running the App Containerization tool or accessing artifacts on Linux systems, despite mentioning Linux deployments in the 'Next steps' section. The focus on Windows tools and patterns may hinder Linux users from following the tutorial effectively.
Recommendations
- Include Linux file paths and navigation instructions alongside Windows examples (e.g., /var/lib/azure-migrate-app-containerization or similar).
- Provide guidance for accessing hidden directories and files on Linux (e.g., using ls -a or similar commands).
- Explicitly state whether the Azure Migrate App Containerization tool is supported on Linux, and if so, provide Linux-specific steps for locating artifacts.
- Balance the order of presentation by mentioning Linux and Windows artifact locations together, or in parallel sections.
- Where screenshots or UI instructions are given (e.g., File Explorer), offer Linux equivalents (e.g., Nautilus, command line).
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/troubleshoot-appliance.md
...s/blob/main/articles/migrate/troubleshoot-appliance.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. Troubleshooting steps and examples often reference Windows tools, commands, and patterns first or exclusively (e.g., Control Panel, admin command prompt, PowerShell, Notepad, Windows file paths, WMI, WinRM, registry edits). Linux examples are sometimes present, but are less detailed, appear later, or are missing in some sections. Some remediation steps are only described for Windows, with Linux equivalents omitted or less emphasized.
Recommendations
- For every troubleshooting step involving Windows-specific tools (e.g., Control Panel, Notepad, PowerShell), provide equivalent Linux commands or GUI steps where applicable.
- When giving command-line examples, present both Windows and Linux commands side-by-side or in parallel tabs, not just in separate sections or as an afterthought.
- Avoid assuming the appliance or troubleshooting host is always Windows; clarify when steps are OS-specific.
- For file edits (e.g., hosts file), include Linux file paths and editing instructions (e.g., /etc/hosts with nano or vi).
- For time synchronization, provide Linux commands (e.g., timedatectl, ntpdate) alongside Windows w32tm commands.
- For service management (e.g., restarting services), include Linux systemctl/service commands as well as Windows net stop/start.
- Ensure all error scenarios (e.g., connectivity, authentication, permissions) have both Windows and Linux remediation steps where relevant.
- Review for any missing Linux-specific troubleshooting (e.g., SELinux, firewall-cmd, system logs) and add as needed.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/troubleshoot-assessment-faq.md
...b/main/articles/migrate/troubleshoot-assessment-faq.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page exhibits a Windows bias primarily by referencing Windows-specific technologies (e.g., Hyper-V, Windows licensing), mentioning Windows scenarios before Linux ones, and omitting Linux-specific troubleshooting examples or considerations. There is a lack of parity in details for Linux environments, especially regarding licensing, performance data collection, and troubleshooting steps.
Recommendations
- Include explicit troubleshooting steps and examples for Linux servers and distributions, especially in sections discussing performance data collection and assessment confidence.
- Address Linux licensing considerations in cost assessments, or clearly state the current limitations and provide guidance for Linux users.
- Balance the order of presentation by alternating or grouping Windows and Linux scenarios, rather than consistently mentioning Windows/Hyper-V first.
- Provide Linux-specific guidance for common issues (e.g., missing performance counters, network adapter discovery) and reference relevant Linux tools or commands.
- Where Windows tools or patterns are mentioned (such as Hyper-V or Windows licensing), add equivalent Linux context or note if a feature is not applicable.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/troubleshoot-discovery.md
...s/blob/main/articles/migrate/troubleshoot-discovery.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a noticeable Windows bias. Troubleshooting steps, error remediations, and validation commands are predominantly presented using Windows tools (PowerShell, WMI, Windows environment variables, IIS), with detailed, step-by-step instructions for Windows scenarios. Linux is mentioned, but Linux-specific troubleshooting commands and examples are sparse or missing. Where Linux is referenced, it is often as an afterthought or in a secondary position to Windows. Several error codes and their remediations are Windows-centric, and Linux troubleshooting is not given equal depth or clarity.
Recommendations
- For every PowerShell or Windows-specific command or remediation, provide an equivalent Linux shell (bash) command or procedure where applicable.
- Include Linux-specific troubleshooting steps for common errors (e.g., how to check SSH connectivity, required packages, permissions, or logs on Linux).
- When describing prerequisites or port requirements, present Linux and Windows information in parallel, not with Windows first.
- Expand error tables to include Linux-specific causes and actions, not just Windows (e.g., for errors involving PowerShell, also describe what happens on Linux and what to check).
- For validation and mitigation verification, provide Linux-native commands (e.g., using SSH, systemctl, journalctl, etc.) alongside PowerShell.
- For web app discovery, mention and provide guidance for common Linux web servers (Apache, Nginx) if supported, or clearly state if only IIS/Windows is supported.
- Review all examples and ensure Linux is treated as a first-class platform, with equal detail and clarity as Windows.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/troubleshoot-assessment.md
.../blob/main/articles/migrate/troubleshoot-assessment.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation demonstrates a Windows bias in several ways: Windows-specific tools and protocols (WinRM, WMI, PowerShell cmdlets) are mentioned explicitly and often before their Linux equivalents. Troubleshooting steps and error codes reference Windows technologies in detail, while Linux guidance is less specific or missing. For example, adding IPs to WinRM TrustedHosts is described, but no equivalent SSH configuration for Linux is provided. Several error codes and fixes focus on Windows (e.g., WMI, application pools, ISAPI filters) with little or no Linux context or examples.
Recommendations
- Provide equivalent Linux troubleshooting steps and examples wherever Windows-specific instructions are given (e.g., SSH configuration, sudoers, firewall rules).
- When mentioning Windows tools or protocols (WinRM, WMI), also mention the Linux equivalents (SSH, relevant Linux services or commands) and provide parallel instructions.
- Avoid listing Windows steps or tools first by default; alternate or present both Windows and Linux guidance together.
- For error codes and scenarios that are Windows-specific (e.g., WMI, application pools), clarify if there are Linux equivalents or explicitly state that the issue is Windows-only.
- Include Linux-specific error codes, troubleshooting steps, and common issues to ensure parity.
- Where PowerShell or Windows cmdlets are referenced, provide corresponding Bash or Linux command-line examples where applicable.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/troubleshoot-changed-block-tracking-replication.md
...ate/troubleshoot-changed-block-tracking-replication.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation is heavily oriented toward Windows environments, with all troubleshooting steps, command-line examples, and tool references assuming the Azure Migrate appliance is running on Windows. Only PowerShell, Windows command prompt, and Windows-specific tools (e.g., services.msc, MMC snap-in, Windows hosts file path) are mentioned. There are no examples or instructions for performing equivalent tasks on Linux-based appliances, nor is there any mention of Linux shell commands or tools. This creates a bias that may exclude users running the appliance on Linux or those more comfortable with Linux tooling.
Recommendations
- Provide equivalent Linux shell (bash) commands for all PowerShell and Windows command prompt examples, such as using 'curl', 'nc', or 'telnet' for connectivity tests.
- Include instructions for managing services on Linux (e.g., using 'systemctl' or 'service' commands) alongside Windows service management steps.
- Reference Linux file paths and hosts file locations (e.g., /etc/hosts) when discussing DNS resolution and static host entries.
- Clarify whether the Azure Migrate appliance is only supported on Windows, or if Linux-based appliances are also supported; if so, ensure parity in documentation.
- Mention cross-platform tools where possible, or provide links to platform-specific documentation for both Windows and Linux.
- Add screenshots or terminal output examples from Linux environments where applicable.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/troubleshoot-dependencies.md
...lob/main/articles/migrate/troubleshoot-dependencies.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows bias in several ways: Windows tools and PowerShell commands are frequently mentioned first or exclusively, with Linux equivalents sometimes missing or less detailed. Troubleshooting steps and error remediations often focus on Windows-specific tools (e.g., PowerShell, WMI, Registry Editor), and Windows-centric terminology and instructions are more comprehensive. Linux guidance, where present, is sometimes less detailed or appears after Windows instructions.
Recommendations
- Ensure Linux troubleshooting steps are as detailed and prominent as Windows steps, including explicit Linux command examples and error resolutions.
- Where PowerShell or Windows-specific tools are referenced, provide equivalent Linux commands (e.g., bash, systemctl, journalctl) and clarify when steps differ between OSes.
- Avoid listing Windows instructions before Linux ones by default; consider parallel structure (Windows and Linux side-by-side) or alternating order.
- For error codes and remediation tables, ensure Linux-specific errors and solutions are equally represented and not grouped as afterthoughts.
- Where registry edits or WMI/PowerShell steps are given for Windows, provide corresponding Linux configuration file or command-line steps (e.g., editing /etc files, using systemctl, etc.) where applicable.
- Expand Linux agent and dependency troubleshooting sections to match the depth and clarity of Windows sections, including links to relevant Linux documentation.
- Review all examples and ensure that for every Windows-centric example, a Linux equivalent is provided, unless the feature is truly Windows-only (in which case, state this explicitly).
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/troubleshoot-replication-vmware.md
...in/articles/migrate/troubleshoot-replication-vmware.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by providing appliance-side instructions exclusively for Windows environments (e.g., using Remote Desktop, referencing Windows file paths, and using PowerShell commands to restart services). There are no equivalent instructions or examples for Linux-based appliances, nor is there any mention of how to perform these steps on Linux. This may hinder users operating the Azure Migrate appliance on Linux or in mixed environments.
Recommendations
- Provide equivalent instructions for Linux-based appliances, including file paths (e.g., /etc or /var locations), service management commands (e.g., systemctl or service), and text editors (e.g., nano or vi).
- When referencing remote access, mention SSH or console access for Linux in addition to Remote Desktop for Windows.
- Include both PowerShell and Bash (or shell) command examples for service restarts and file editing.
- Clearly state whether the Azure Migrate appliance is only supported on Windows, or if Linux is supported, and provide parity in documentation.
- Avoid assuming the use of Windows tools and patterns (e.g., %programdata%, PowerShell) as the default; always provide cross-platform alternatives.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/troubleshoot-spring-boot-discovery.md
...articles/migrate/troubleshoot-spring-boot-discovery.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation demonstrates a Windows bias by exclusively providing PowerShell-based instructions for interacting with Azure resources (steps 4-8), including the use of ARMClient, a tool distributed as a Windows zip file. There are no equivalent instructions or examples for Linux or macOS users, nor are cross-platform CLI alternatives (such as Azure CLI) mentioned. The documentation assumes the user is on a Windows workstation and does not address Linux environments.
Recommendations
- Provide equivalent Linux/macOS instructions for finding the Principal ID, including commands using Azure CLI (az) or bash.
- Mention and demonstrate cross-platform tools (e.g., Azure CLI) before or alongside Windows-specific tools like ARMClient.
- Clarify that PowerShell steps are for Windows, and offer alternative steps for Linux/macOS users.
- Ensure screenshots and examples are not exclusively from Windows environments.
- Review all troubleshooting steps to ensure they are applicable and accessible for users on non-Windows platforms.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/troubleshoot-network-connectivity.md
.../articles/migrate/troubleshoot-network-connectivity.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a Windows bias by providing command-line examples (such as nslookup) in a Windows context (e.g., 'c:\ >nslookup ...'), referencing PowerShell-specific tools (Test-NetConnection), and using Windows terminology (editing the 'hosts file' on the 'on-premises appliance') without offering equivalent Linux or cross-platform instructions. There are no explicit Linux/Bash examples or mentions of Linux tools for network troubleshooting, and the default context for command-line operations is Windows.
Recommendations
- Provide Linux/Bash equivalents for all command-line examples (e.g., show both 'nslookup' and 'dig' commands, and show Linux shell prompts like '$').
- Include instructions for editing the hosts file on Linux systems (e.g., '/etc/hosts') alongside Windows instructions.
- For PowerShell-specific tools like 'Test-NetConnection', offer cross-platform alternatives such as 'telnet', 'nc' (netcat), or 'curl' for port testing on Linux.
- Use neutral or cross-platform language when referring to the command line or appliance OS (e.g., 'on the command line' instead of 'on the on-premises appliance').
- Add screenshots or terminal outputs from Linux environments where appropriate.
- Explicitly state that the troubleshooting steps apply to both Windows and Linux appliances, and call out any OS-specific differences.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/troubleshoot-upgrade.md
...ocs/blob/main/articles/migrate/troubleshoot-upgrade.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation is exclusively focused on Windows OS upgrade issues, with all examples, terminology, and troubleshooting steps tailored to Windows environments. There are no references to Linux, Linux-based VMs, or cross-platform considerations. The tools, links, and workflows described are all Windows-specific, and there is no mention of equivalent Linux upgrade or migration scenarios.
Recommendations
- Include parallel documentation or sections addressing Linux VM upgrade issues during migration, with Linux-specific troubleshooting steps.
- Provide examples and recommended actions for both Windows and Linux VMs, or clarify early in the document that this page is Windows-specific and link to Linux documentation.
- Reference Linux tools and commands (e.g., using SSH, Linux disk management commands) where appropriate.
- Ensure that migration workflows and prerequisites are described for both Windows and Linux environments, or provide clear navigation to Linux-focused resources.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/troubleshoot-webapps-migration.md
...ain/articles/migrate/troubleshoot-webapps-migration.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation is heavily focused on Windows-based web app migrations, specifically those involving IIS and PowerShell. All troubleshooting steps, error codes, and examples are tailored to IIS servers and PowerShell scripting, with no mention of Linux-based web servers (such as Apache or Nginx) or Linux migration scenarios. There are no Linux-specific troubleshooting steps, tools, or commands provided.
Recommendations
- Add equivalent troubleshooting steps and error codes for common Linux web servers (e.g., Apache, Nginx) and migration scenarios.
- Include Linux-based examples and commands (such as Bash scripts or relevant Linux tools) alongside or before Windows/PowerShell examples.
- Clarify in the introduction that the guide is specific to IIS/Windows migrations, or provide separate sections for Linux and Windows migrations.
- Reference Linux migration documentation or tools if available, and provide links to relevant resources.
- Ensure parity in troubleshooting guidance for both Windows and Linux environments to support a broader range of users.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/tutorial-app-containerization-aspnet-kubernetes.md
...ate/tutorial-app-containerization-aspnet-kubernetes.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation is heavily biased toward Windows environments. All prerequisites, installation steps, and operational instructions are centered on Windows OS, PowerShell, and Microsoft-specific tools (e.g., Web Deploy). There are no Linux equivalents or examples for containerizing ASP.NET applications, and Linux is only mentioned in the context of Java/Tomcat workloads. The documentation assumes the user has access to and is operating from a Windows machine, with no guidance for Linux users wishing to containerize ASP.NET apps.
Recommendations
- Provide equivalent instructions and tooling support for running the App Containerization tool on Linux (or clarify if not supported).
- Include Linux shell (bash) examples alongside PowerShell commands where applicable.
- If the tool is Windows-only, explicitly state this limitation early and suggest alternative approaches for Linux users (e.g., using Docker CLI, manual Dockerfile creation, or other open-source tools).
- Offer guidance or links for containerizing ASP.NET Core applications on Linux, which is a common cross-platform scenario.
- Balance the mention/order of Windows and Linux tools and patterns, ensuring Linux is not always secondary or omitted.
- Where possible, provide troubleshooting and artifact locations for both Windows and Linux environments.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/tutorial-app-containerization-aspnet-app-service.md
...te/tutorial-app-containerization-aspnet-app-service.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Powershell Heavy
Windows Tools
Summary
The documentation is heavily biased towards Windows environments. All instructions, prerequisites, and tooling are centered on Windows OS, with explicit requirements for Windows machines, PowerShell, and Windows-specific tools (e.g., Microsoft Web Deploy). There are no Linux-based examples or alternatives for containerizing ASP.NET apps, and Linux is only mentioned in the context of Java/Tomcat scenarios. The documentation assumes the user is operating in a Windows environment and does not provide parity for Linux users.
Recommendations
- Provide equivalent instructions and tooling for Linux environments, such as supporting the installation and execution of the App Containerization tool on Linux machines.
- Include Linux shell (bash) examples alongside PowerShell commands for all relevant steps.
- Offer guidance for containerizing ASP.NET Core applications running on Linux, and clarify the support matrix for .NET Framework vs. .NET Core/5+/6+.
- Mention and, where possible, support Linux-native deployment and discovery tools (e.g., SSH-based discovery, Linux package managers).
- Clearly state any platform limitations up front and provide links to alternative workflows for Linux users.
- Where Windows-only tools are required, suggest open-source or cross-platform alternatives if available, or provide a roadmap for Linux support.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/tutorial-app-containerization-java-app-service.md
...rate/tutorial-app-containerization-java-app-service.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a strong Windows bias. The Azure Migrate: App Containerization tool is only available for Windows, and all installation and usage instructions assume a Windows environment (including PowerShell commands and references to Windows file paths). There are no instructions or examples for installing or running the tool from a Linux or macOS machine, nor are there alternative workflows for non-Windows users. The troubleshooting section also only references Windows-specific log locations.
Recommendations
- Provide a Linux-compatible version of the Azure Migrate: App Containerization tool, or clearly state its unavailability and suggest alternative approaches for Linux users.
- Include installation and usage instructions for Linux (and optionally macOS), with corresponding shell commands and file paths.
- Offer troubleshooting guidance for Linux environments if/when a Linux version is available.
- If the tool is fundamentally Windows-only, add a prominent note at the top of the documentation clarifying this limitation and linking to alternative migration/containerization approaches for Linux users.
- Where possible, avoid assuming the user's workstation is Windows—present cross-platform instructions or alternatives.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/tutorial-app-containerization-java-kubernetes.md
...grate/tutorial-app-containerization-java-kubernetes.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Powershell Heavy
Windows Tools
Summary
The documentation demonstrates a strong Windows bias: the Azure Migrate: App Containerization tool can only be installed and run on Windows machines, with explicit requirements for Windows Server or Windows 10/11. All installation and usage instructions (including PowerShell commands and file paths) are Windows-specific, with no mention of Linux or macOS alternatives for running the tool. Troubleshooting and artifact storage paths are also Windows-centric. While the tool targets containerizing Java apps running on Linux servers, the management and orchestration are exclusively Windows-based, and there are no Linux-native usage examples or instructions.
Recommendations
- Provide a Linux version of the Azure Migrate: App Containerization tool, or clarify if it is not available.
- If the tool is Windows-only, explicitly state this limitation at the start of the documentation.
- Offer equivalent installation and usage instructions for Linux (e.g., bash scripts, Linux file paths) if/when the tool supports it.
- Include troubleshooting and artifact location instructions for Linux environments if supported.
- Consider providing a containerized version of the tool itself, so it can be run cross-platform.
- If Windows is required only for the tool, suggest using a lightweight Windows VM or container for Linux users, and provide guidance on how to set this up.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/tutorial-assess-aspnet-aks.md
...ob/main/articles/migrate/tutorial-assess-aspnet-aks.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias, particularly in the ASP.NET assessment flow. It references Windows-specific requirements (e.g., ASP.NET apps needing a Windows node pool), and the 'Next steps' section highlights optimizing Windows Dockerfiles without mentioning Linux equivalents. There are no Linux-specific examples, tools, or guidance for users running Java or .NET apps on Linux, and the documentation does not provide parity in Linux containerization or migration scenarios.
Recommendations
- Include explicit guidance and examples for Linux-based ASP.NET Core and Java web apps, covering both Windows and Linux containerization paths.
- In the 'Cost details' and assessment sections, clarify when Linux node pools are recommended (e.g., for Java or ASP.NET Core apps) and provide cost breakdowns for both Windows and Linux scenarios.
- In the 'Next steps' section, add links to resources on optimizing Linux Dockerfiles and best practices for Linux containers on AKS.
- Ensure that any references to Dockerfile optimization, node pool selection, or migration steps are presented for both Windows and Linux, or clarify the applicability to each platform.
- Wherever Windows-specific requirements are mentioned (such as the need for a Windows node pool), provide parallel information for Linux-based workloads.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/tutorial-assess-sql-vmware.md
...ob/main/articles/migrate/tutorial-assess-sql-vmware.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation shows a Windows bias by referencing Windows-specific tools and patterns (such as Windows Server Failover Clusters and Cloud Witness), linking to Windows-specific best practices, and omitting Linux-specific guidance or examples. There are no Linux or cross-platform examples for SQL Server deployments, high availability, or licensing, and Windows terminology is used exclusively in several key sections.
Recommendations
- Include Linux-specific examples and guidance, such as SQL Server on Linux VM migration scenarios and high availability configurations (e.g., Pacemaker clusters).
- Reference both Windows and Linux best practices for SQL Server on Azure VMs, providing links to both sets of documentation.
- When discussing features like Azure Hybrid Benefit, clarify how it applies to both Windows and Enterprise Linux (RHEL/SLES) subscriptions, and provide examples for each.
- In sections discussing high availability and disaster recovery, include Linux-supported options (e.g., Pacemaker, witness disk configurations) and not just Windows Server Failover Clusters.
- Ensure screenshots and step-by-step instructions are platform-neutral or provide parallel instructions for both Windows and Linux environments.
- Review terminology to avoid assuming Windows as the default (e.g., replace 'Windows Server Failover Clusters' with 'Failover Clusters (Windows or Linux)').
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/tutorial-assess-vmware-azure-vm.md
...in/articles/migrate/tutorial-assess-vmware-azure-vm.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing Windows Server licensing and Azure Hybrid Benefit for Windows Server before mentioning Linux equivalents. The 'Supportability' section highlights Windows Server versions specifically, and there are no Linux-specific examples or screenshots. Additionally, there are no Linux command-line or OS-specific instructions, and the only Linux mention is in the context of licensing (RHEL and SLES), not operational guidance or parity in examples.
Recommendations
- Include Linux-specific examples and screenshots, such as assessing VMs running popular Linux distributions (e.g., Ubuntu, CentOS, RHEL).
- In the 'Supportability' and 'Assessment properties' sections, provide equal detail for Linux OS support and licensing, not just Windows Server.
- Add notes or sections on how to interpret assessment results for Linux VMs, including common issues and remediation steps.
- Ensure that any references to Azure Hybrid Benefit or cost optimization mention Linux options (RHEL, SLES) with equal prominence and detail as Windows Server.
- Where possible, provide command-line or operational examples relevant to Linux environments, not just GUI-based workflows.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/tutorial-assess-sql.md
...docs/blob/main/articles/migrate/tutorial-assess-sql.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing Windows-specific tools and patterns (such as Cloud Witness and Windows Server Failover Clusters) without mentioning Linux equivalents. There are no Linux-specific instructions, examples, or references to Linux-based SQL Server deployments or high availability patterns. The only mention of Linux is in the context of licensing (RHEL and SLES), not in operational or migration steps.
Recommendations
- Include explicit instructions and examples for assessing SQL Server instances running on Linux, including supported distributions and any differences in the assessment process.
- Mention and link to Linux-based high availability and disaster recovery options (such as Pacemaker or Linux clustering solutions) alongside Windows Server Failover Clusters.
- Provide parity in tooling references, such as how to configure or assess SQL Server on Linux VMs, and clarify any differences in Azure Migrate appliance setup or data collection for Linux environments.
- Where Windows-specific features (like Cloud Witness) are mentioned, add corresponding Linux alternatives or note if they are not applicable.
- Add screenshots or command-line examples relevant to Linux environments, not just Windows GUIs or PowerShell.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/tutorial-discover-aws.md
...cs/blob/main/articles/migrate/tutorial-discover-aws.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a significant Windows bias. The Azure Migrate appliance is only described as running on Windows Server, with no mention of Linux as a supported OS for the appliance itself. All setup and verification steps (e.g., running PowerShell scripts, using CertUtil for hash verification, installing Windows roles like IIS and PowerShell ISE) are Windows-centric. There are no Linux equivalents or instructions for running the appliance or scripts on Linux. While Linux server discovery is supported, all operational and administrative examples and tooling are Windows-only.
Recommendations
- Provide explicit instructions for deploying and running the Azure Migrate appliance on Linux-based EC2 instances, if supported.
- Include Linux shell (bash) equivalents for all PowerShell and Windows command-line examples, such as verifying file hashes (e.g., using sha256sum).
- Document Linux-native prerequisites and installation steps (e.g., required packages, services, and permissions) for the appliance, or clearly state if Linux is not supported as a host for the appliance.
- If the appliance is Windows-only, clarify this early in the prerequisites and suggest alternatives or workarounds for Linux-only environments.
- Ensure that all operational steps (such as extracting files, running scripts, and troubleshooting) have Linux equivalents or clear guidance for Linux administrators.
- Balance the order of presentation so that Linux and Windows instructions are given equal prominence where both are supported.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/tutorial-discover-hyper-v.md
...lob/main/articles/migrate/tutorial-discover-hyper-v.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a strong Windows bias. All setup, deployment, and configuration instructions are written for Windows Server and Hyper-V environments, with exclusive use of Windows tools (PowerShell, WinRM, Hyper-V Manager, Local Group Policy Editor) and commands. PowerShell scripts and commands are provided throughout, with no equivalent Linux shell or cross-platform alternatives. While Linux servers are mentioned as supported for discovery, there are no Linux-based examples or instructions for deploying or managing the Azure Migrate appliance, nor for preparing Linux-based Hyper-V hosts (if such exist). The documentation assumes the reader is operating entirely within a Windows ecosystem.
Recommendations
- Provide explicit instructions or references for deploying and managing the Azure Migrate appliance from a Linux or cross-platform environment, if supported.
- Include Linux shell (bash) equivalents for PowerShell commands where applicable, or clarify if such operations are Windows-only.
- Where Windows tools (e.g., Hyper-V Manager, Local Group Policy Editor) are referenced, note whether there are cross-platform or web-based alternatives, or explicitly state the requirement for Windows.
- Add Linux-based examples for credential management, appliance configuration, and connectivity validation.
- Clarify any limitations or requirements for Linux users, and provide guidance for mixed-OS environments.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/tutorial-discover-gcp.md
...cs/blob/main/articles/migrate/tutorial-discover-gcp.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows bias in several ways: Windows Server is the only supported OS for the Azure Migrate appliance, with explicit instructions and examples using Windows tools (PowerShell, CertUtil, IIS, registry edits). The setup and installation process is described exclusively with Windows commands and patterns, with no equivalent Linux instructions or support. While Linux server discovery is mentioned, there are no examples or guidance for running the appliance or installer on Linux, nor are Linux-native tools referenced.
Recommendations
- Provide parity by supporting and documenting installation of the Azure Migrate appliance on Linux hosts, or explicitly state if this is not possible.
- Include Linux shell (bash) equivalents for all PowerShell and Windows command-line examples, or clarify that the appliance is Windows-only.
- Reference Linux-native tools (e.g., sha256sum for hash verification) alongside Windows tools like CertUtil.
- If the appliance cannot run on Linux, explain the rationale and suggest best practices for mixed-OS environments.
- Ensure that all steps involving Windows-specific features (IIS, registry, PowerShell ISE) are either accompanied by Linux alternatives or clearly marked as Windows-only requirements.
- Consider restructuring sections so that Linux and Windows instructions are presented in parallel where possible, rather than Windows-first.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/tutorial-discover-physical.md
...ob/main/articles/migrate/tutorial-discover-physical.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation exhibits a Windows-first bias in several areas. Windows setup instructions and examples are presented before Linux, with more detailed steps and troubleshooting for Windows accounts, permissions, and tools. The installer script and appliance setup are described using PowerShell and Windows command-line tools (e.g., CertUtil), and the installation process assumes a Windows environment (e.g., references to IIS, registry keys, and Windows file paths). There are no equivalent Linux command-line examples or explicit instructions for running the installer or verifying hashes on Linux. Linux instructions are present but less detailed, and Linux-specific troubleshooting or parity for installer setup is missing.
Recommendations
- Provide Linux-first or parallel instructions where possible, ensuring Linux setup steps are as detailed and prominent as Windows steps.
- Include Linux command-line examples for verifying file hashes (e.g., using sha256sum) alongside CertUtil for Windows.
- Clarify whether the Azure Migrate appliance can be installed and run on Linux, and if so, provide explicit installation and troubleshooting steps for Linux environments.
- When referencing tools or commands (e.g., PowerShell, IIS, registry keys), note their Windows specificity and offer Linux alternatives or state if not applicable.
- Balance the troubleshooting and permission guidance for both Windows and Linux, ensuring Linux users have equivalent support and clarity.
- Where screenshots or UI steps are shown, indicate any differences for Linux users or note if the process is identical.