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 101-125 of 918 flagged pages
Migrate Start here - Migrate VMware deployments to Azure ...e-docs/blob/main/articles/migrate/start-here-vmware.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a bias toward Windows environments by providing migration examples and automation steps primarily using Azure PowerShell, a Windows-centric tool. There is no mention of Linux-based alternatives (such as Azure CLI or Bash scripting), nor are Linux-specific tools or patterns referenced for migration or automation. The discovery step references RVTools, which is a Windows-only application, without suggesting Linux-compatible alternatives.
Recommendations
  • Include Azure CLI examples alongside or before Azure PowerShell examples to ensure Linux users have clear guidance.
  • Reference Linux-compatible discovery tools or methods, such as open-source scripts or tools that run on Linux, in addition to RVTools.
  • Explicitly mention cross-platform options for automation and migration, such as Bash scripts or REST API usage.
  • Ensure troubleshooting and preparation steps include guidance for both Windows and Linux environments.
  • Add a section or callout highlighting platform parity and cross-platform support for migration tooling.
GitHub Create Pull Request
Migrate Troubleshoot Azure Migrate appliance diagnostic .../articles/migrate/troubleshoot-appliance-diagnostic.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Windows file paths (e.g., C:\Users\Public\Desktop\DiagnosticsReport), mentioning Windows Server 2022 evaluation licenses, and omitting any Linux-specific instructions, examples, or file locations. There are no examples or guidance for running diagnostics or accessing reports on Linux-based appliances, nor are Linux tools or commands referenced.
Recommendations
  • Include instructions and examples for Linux-based Azure Migrate appliances, such as file paths (e.g., /home/public/Desktop/DiagnosticsReport or /var/lib/azuremigrate/diagnostics), and clarify where reports are saved on Linux.
  • Mention Linux equivalents for license checks, such as how appliance validity is determined for Linux VMs.
  • Provide screenshots or CLI examples for Linux environments, if supported.
  • Explicitly state OS support and any differences in diagnostic behavior between Windows and Linux appliances.
  • Ensure remediation steps and troubleshooting guidance are applicable to both Windows and Linux platforms.
GitHub Create Pull Request
Migrate Troubleshoot the Azure Migrate appliance ...s/blob/main/articles/migrate/troubleshoot-appliance.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits a moderate Windows bias. Troubleshooting steps and examples frequently reference Windows-specific tools (Control Panel, admin command prompt, PowerShell, Notepad, registry edits, WMI Control Panel) and provide Windows solutions first or exclusively. Linux troubleshooting is present but often appears after Windows instructions or is less detailed. Some remediation steps for Windows use PowerShell or command prompt, while Linux equivalents are less emphasized or missing.
Recommendations
  • Ensure Linux troubleshooting steps are presented with equal prominence and detail as Windows steps.
  • Provide Linux-first examples or parallel instructions for common tasks (e.g., time synchronization, editing hosts file, service management).
  • Include Linux command-line equivalents for all Windows command prompt or PowerShell instructions (e.g., for time sync, service restart, file editing).
  • Reference Linux tools (such as timedatectl, systemctl, nano/vi) alongside Windows tools.
  • Where registry edits or Windows-specific GUI steps are described, offer Linux configuration file or CLI alternatives.
  • Add explicit Linux examples for appliance management and validation steps, not just for physical server scenarios.
  • Review the order of presentation to avoid always listing Windows steps before Linux steps.
GitHub Create Pull Request
Migrate Common issues in Azure Migrate assessments .../blob/main/articles/migrate/troubleshoot-assessment.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in several ways: Windows-specific tools and patterns (WinRM, WMI, Get-WmiObject cmdlet) are mentioned and explained in detail, often before or instead of Linux equivalents. Troubleshooting steps frequently reference Windows technologies (WinRM, WMI, applicationHost.config, IIS, ISAPI filters) and provide explicit instructions for Windows, while Linux troubleshooting is less detailed and lacks parity in example commands or tool references. Linux issues are sometimes grouped generically (e.g., SSHOperationTimeout) without the same depth of actionable steps or tool references as Windows. Web app migration errors focus almost exclusively on IIS and Windows-specific configurations, with no mention of common Linux web stacks (Apache, Nginx, Tomcat).
Recommendations
  • Provide Linux-specific troubleshooting steps and examples wherever Windows tools (WinRM, WMI, PowerShell cmdlets) are mentioned. For example, include SSH configuration, sudo permissions, and relevant Linux commands.
  • When listing port requirements or authentication methods, present Windows and Linux information side-by-side, rather than Windows first.
  • Expand web app migration error sections to include common Linux web servers (Apache, Nginx, Tomcat) and their configuration issues.
  • Where Windows configuration files (applicationHost.config, web.config) are referenced, include Linux equivalents (httpd.conf, nginx.conf, server.xml) and migration considerations.
  • Add Linux command-line examples for credential validation, performance data collection, and troubleshooting, similar to the PowerShell/WinRM examples for Windows.
  • Ensure parity in troubleshooting depth for both OS types, including permissions, service status checks, and error remediation steps.
GitHub Create Pull Request
Migrate Troubleshoot ongoing server discovery, software inventory, and SQL discovery ...s/blob/main/articles/migrate/troubleshoot-discovery.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits a Windows bias in several ways: troubleshooting steps and examples frequently use PowerShell and Windows-specific tools (e.g., WinRM, WMI, UAC, IIS), with Windows remediation steps and commands often presented before or in more detail than their Linux equivalents. Linux troubleshooting is generally limited to SSH connectivity and basic commands, with little coverage of Linux-specific errors, tools, or advanced remediation. Some sections, such as web apps discovery errors, are exclusively focused on Windows technologies (IIS), and Linux examples are sparse or missing in command walkthroughs.
Recommendations
  • Provide Linux-specific troubleshooting steps and examples alongside Windows ones, including common Linux errors and their remediation.
  • Include Linux-native commands and tools (e.g., systemctl, journalctl, package managers) in troubleshooting workflows, not just SSH connectivity.
  • For sections focused on Windows technologies (e.g., IIS), clarify Linux alternatives (e.g., Apache, Nginx) and document their discovery and error handling.
  • Ensure parity in example scripts and commands: where PowerShell is used for Windows, provide equivalent Bash or shell commands for Linux.
  • Expand error tables to include Linux-specific issues (e.g., permission errors, missing dependencies, SELinux/AppArmor restrictions) and their solutions.
  • Avoid presenting Windows steps first by default; alternate or parallelize instructions for both platforms.
  • Document Linux credential management and troubleshooting in equal detail to Windows (e.g., SSH key issues, PAM configuration, sudo permissions).
GitHub Create Pull Request
Migrate Troubleshoot assessments FAQ in Azure Migrate ...b/main/articles/migrate/troubleshoot-assessment-faq.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Windows Heavy
Summary
The documentation page exhibits a Windows bias by frequently referencing Windows-specific environments (Hyper-V, Windows servers), providing troubleshooting steps and examples primarily for Windows/Hyper-V scenarios, and mentioning Windows tools (Edge, Internet Explorer) before or instead of Linux alternatives. There is a lack of Linux-specific troubleshooting guidance, examples, and parity in license cost consideration. Linux environments and tools are rarely mentioned, and when they are, they are secondary to Windows.
Recommendations
  • Add troubleshooting examples and guidance for Linux environments (e.g., Linux VMs on VMware, physical Linux servers).
  • Include Linux-specific instructions for collecting performance data and network traffic (e.g., using tcpdump, Wireshark, or browser tools on Linux).
  • Provide parity in license cost assessment for Linux servers, or clarify the rationale for exclusion.
  • Mention Linux tools and browsers (e.g., Firefox, Chromium) in network traffic capture instructions.
  • Ensure that references to environments (Hyper-V, VMware, physical) include both Windows and Linux scenarios equally.
  • Add explicit troubleshooting steps for common Linux-specific issues in Azure Migrate assessments.
GitHub Create Pull Request
Migrate Troubleshoot replication issues in agentless VMware VM migration ...ate/troubleshoot-changed-block-tracking-replication.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a strong Windows bias. Troubleshooting steps and command-line examples are almost exclusively provided for Windows environments, specifically using PowerShell, Command Prompt, and Windows tools (e.g., services.msc, MMC snap-ins, editing C:\Windows\System32\drivers\etc\hosts). There are no Linux shell equivalents or instructions for users running the Azure Migrate appliance on Linux. Tools and patterns (such as PowerShell cmdlets and Windows service management) are mentioned first and sometimes exclusively, with no parity for Linux users.
Recommendations
  • Provide equivalent Linux shell commands for all PowerShell/Command Prompt examples (e.g., use 'systemctl' or 'service' for service management, 'nslookup' and 'netcat' for network tests, and instructions for editing /etc/hosts).
  • Clarify whether the Azure Migrate appliance can run on Linux, and if so, include Linux-specific troubleshooting steps.
  • For commands like 'Test-NetConnection', offer alternatives such as 'nc', 'telnet', or 'curl' for Linux.
  • When referencing file paths (e.g., hosts file), include both Windows and Linux locations.
  • Mention cross-platform tools (e.g., azcopy, Service Bus Explorer) and provide installation/use instructions for both Windows and Linux.
  • Avoid assuming users are on Windows by default; structure troubleshooting steps so that Windows and Linux instructions are presented in parallel or with clear headings.
GitHub Create Pull Request
Migrate Troubleshoot slow replication or stuck migration in agentless VMware migration ...in/articles/migrate/troubleshoot-replication-vmware.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates Windows bias by providing remediation steps for the Azure Migrate appliance that exclusively use Windows tools and patterns (Remote Desktop, %programdata% path, PowerShell commands for service management). There are no Linux equivalents or examples for managing the appliance, and Windows-centric instructions are presented first and exclusively. No guidance is given for scenarios where the appliance might be running on Linux, nor are Linux service management commands or file paths mentioned.
Recommendations
  • Provide equivalent Linux instructions for managing the Azure Migrate appliance, including file paths (e.g., /var/lib/...), service management commands (systemctl, service), and remote access methods (SSH).
  • Include Linux-based examples alongside Windows/PowerShell examples for all steps involving appliance configuration and troubleshooting.
  • Clarify whether the appliance can run on Linux, and if so, ensure parity in documentation for both platforms.
  • Avoid using Windows-specific terminology and tools exclusively; present cross-platform alternatives where possible.
  • Explicitly state platform requirements and provide links to platform-specific guides if the appliance is Windows-only.
GitHub Create Pull Request
Migrate Troubleshoot Windows upgrade issues ...ocs/blob/main/articles/migrate/troubleshoot-upgrade.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation is exclusively focused on troubleshooting Windows OS upgrade issues during VM migration, with all examples, terminology, and links referencing Windows-specific processes, tools, and requirements. There is no mention of Linux OS upgrades, Linux disk management, or Linux migration troubleshooting, nor are equivalent Linux procedures or recommendations provided.
Recommendations
  • Add a parallel section for troubleshooting Linux OS upgrade issues during VM migration, including common problems and solutions.
  • Provide Linux-specific examples for disk management, such as expanding the OS disk using Linux commands or Azure portal steps for Linux VMs.
  • Include references and links to Linux documentation (e.g., Azure Linux VM upgrade guides, disk space requirements for Linux).
  • Mention Linux VM SKU limitations and how to address them during migration.
  • Ensure that recommendations and troubleshooting steps are presented for both Windows and Linux platforms, or clarify that the scope is intentionally limited to Windows if Linux is not supported.
GitHub Create Pull Request
Migrate Troubleshoot web apps migration issues ...ain/articles/migrate/troubleshoot-webapps-migration.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Missing Linux Example Windows First
Summary
The documentation page is heavily focused on troubleshooting migration issues for IIS web apps, which are Windows-centric. The troubleshooting steps repeatedly reference IIS (a Windows-only web server) and PowerShell (a Windows-native automation tool), with no mention of Linux-based web servers (e.g., Apache, Nginx) or Linux migration scenarios. All examples and error codes are specific to Windows tools and patterns, and there are no Linux equivalents or guidance for Linux-based web app migrations.
Recommendations
  • Add troubleshooting sections for common Linux web servers (e.g., Apache, Nginx) and their migration issues.
  • Include Linux-specific error codes and troubleshooting steps, such as permissions, SELinux/AppArmor issues, or package dependencies.
  • Provide examples using Linux-native tools (e.g., Bash scripts, rsync, SCP) for migration and troubleshooting, alongside PowerShell examples.
  • Clarify in the introduction that the guidance is Windows/IIS-specific, or restructure to provide parity for both Windows and Linux migration scenarios.
  • Reference Azure Migrate capabilities for Linux web apps, if available, and link to relevant documentation.
GitHub Create Pull Request
Migrate ASP.NET app containerization and migration to App Service ...te/tutorial-app-containerization-aspnet-app-service.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation is heavily biased towards Windows environments for ASP.NET app containerization. All instructions, prerequisites, and tooling are Windows-centric, requiring a Windows machine, PowerShell remoting, and Microsoft Web Deployment tool. There are no Linux-based examples or guidance for containerizing ASP.NET apps from Linux servers, and all operational steps assume Windows-only patterns and tools.
Recommendations
  • Add instructions and examples for containerizing ASP.NET Core apps running on Linux servers, including prerequisites and supported environments.
  • Provide parity for Linux users by supporting installation and usage of the App Containerization tool on Linux machines, or document alternative workflows for Linux.
  • Include Linux shell (bash) commands alongside PowerShell examples where applicable.
  • Mention and support Linux-native tools (such as SSH for remote connectivity, rsync for file transfer) as alternatives to Windows tools like PowerShell remoting and Web Deploy.
  • Clarify in the prerequisites and introduction that the current workflow is Windows-only, and provide links or guidance for Linux-based ASP.NET scenarios if available.
  • Expand troubleshooting and log file locations to include Linux paths if/when Linux support is added.
GitHub Create Pull Request
Migrate Continuous Deployment for containerized applications with Azure DevOps ...igrate/tutorial-app-containerization-azure-pipeline.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits Windows bias by referencing Windows file paths (C:\ProgramData...), Windows-specific navigation instructions (File Explorer, Hidden items), and focusing on ASP.NET applications (typically Windows-based) before mentioning Linux/Java equivalents. There are no explicit Linux file path examples or instructions for locating artifacts on Linux systems, and the artifact location steps assume a Windows environment. Linux tools, conventions, or navigation patterns are not discussed, and Linux parity is only referenced in the 'Next steps' section.
Recommendations
  • Add explicit instructions for locating artifacts on Linux systems, including Linux file paths and navigation commands (e.g., using the terminal, ls, cd).
  • Provide examples for both Windows and Linux environments side-by-side, especially in sections describing artifact locations and uploads.
  • Mention Linux tools (such as Nautilus, terminal commands) where Windows tools (File Explorer) are referenced.
  • Ensure that Linux-based application scenarios (e.g., Java on Tomcat/Linux) are given equal prominence and detail as Windows/ASP.NET scenarios throughout the tutorial, not just in 'Next steps'.
  • Clarify that the Azure Migrate App Containerization tool can be run on both Windows and Linux, if applicable, and describe any differences in artifact generation or location.
GitHub Create Pull Request
Migrate Azure App Containerization ASP.NET; Containerization and migration of ASP.NET applications to Azure Kubernetes. ...ate/tutorial-app-containerization-aspnet-kubernetes.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation is heavily biased toward Windows environments for ASP.NET containerization. All instructions, prerequisites, and tooling are Windows-specific, requiring Windows OS, PowerShell, and Microsoft Web Deploy. There are no Linux equivalents or examples for ASP.NET containerization, and all code samples and operational steps use Windows tools and patterns. Linux is only mentioned as a platform for Java/Tomcat apps, not for ASP.NET workloads.
Recommendations
  • Provide guidance and tooling for ASP.NET containerization from Linux environments, including support for .NET Core/ASP.NET Core apps on Linux.
  • Include Linux-based examples and instructions for containerizing ASP.NET applications, such as using Bash, SSH, and Linux-native tools.
  • Offer parity in prerequisites and troubleshooting steps for Linux users, e.g., log file locations, installation commands, and environment setup.
  • Clarify in the introduction that the current tool and tutorial are Windows-only, and link to Linux-compatible alternatives for .NET/ASP.NET workloads.
  • Add a comparison table or section outlining differences and supported scenarios for Windows vs. Linux containerization of ASP.NET apps.
GitHub Create Pull Request
Migrate Containerization and migration of Java web applications to Azure App Service. ...rate/tutorial-app-containerization-java-app-service.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation exhibits a strong Windows bias. The Azure Migrate: App Containerization tool is only installable and runnable on Windows machines, with explicit requirements for Windows Server or Windows 10. All installation instructions and examples use PowerShell, and there is no mention of Linux alternatives for running the tool or using Linux-native commands. Troubleshooting instructions reference Windows file paths, and the workflow assumes a Windows environment for all steps, despite the target applications being Java web apps on Linux servers.
Recommendations
  • Provide a Linux version of the Azure Migrate: App Containerization tool, or document how to run the tool in a Linux environment (e.g., via container or cross-platform scripting).
  • Include installation and usage instructions for Linux, using Bash or shell commands alongside PowerShell examples.
  • Offer troubleshooting guidance for Linux environments, such as log file locations and permissions.
  • Clarify whether the tool can be run from a Linux VM or container, and if not, explain the roadmap for Linux support.
  • Ensure parity in examples and instructions for both Windows and Linux users, especially since the target applications are hosted on Linux.
GitHub Create Pull Request
Migrate Azure App Containerization Java; Containerization and migration of Java web applications to Azure Kubernetes. ...grate/tutorial-app-containerization-java-kubernetes.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example Powershell Heavy 🔧 Windows Tools
Summary
The documentation exhibits a strong Windows bias: the Azure Migrate: App Containerization tool must be installed and run on a Windows machine, with explicit requirements for Windows Server or Windows 10. All installation instructions and troubleshooting steps are Windows-specific, including use of PowerShell for installation and references to Windows file paths for artifacts and logs. There are no instructions or examples for running the tool on Linux or macOS, nor are alternative Linux-native workflows or tools mentioned. The documentation assumes the user is operating from a Windows environment, even though the target applications are Java web apps running on Linux servers.
Recommendations
  • Provide instructions and support for installing and running the Azure Migrate: App Containerization tool on Linux (and possibly macOS), including prerequisites, installation steps, and troubleshooting.
  • Offer Linux shell (bash) equivalents for installation and operational commands, in addition to PowerShell examples.
  • Document storage locations and log paths for Linux environments, if supported.
  • Clarify whether the tool is Windows-only, and if so, explain the rationale and suggest alternative approaches for Linux users.
  • Consider developing or highlighting cross-platform or Linux-native migration/containerization tools for Java applications.
  • Ensure parity in documentation structure and examples for both Windows and Linux users, especially given the target workload is Linux-based.
GitHub Create Pull Request
Migrate Assess VMware servers for migration to Azure VMs in Azure Migrate ...in/articles/migrate/tutorial-assess-vmware-azure-vm.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits a Windows bias by referencing Windows Server and its licensing benefits before Linux equivalents, focusing on Windows-specific cost optimization features, and omitting Linux-specific examples or troubleshooting details. The 'Azure Hybrid Benefit' section mentions Windows Server licenses first, with Linux (RHEL/SLES) as a secondary note. The 'Supportability' section highlights Windows Server version distribution, but does not mention Linux distributions. No Linux-specific assessment examples, screenshots, or troubleshooting are provided.
Recommendations
  • Include explicit examples and screenshots for assessing Linux VMs (e.g., Ubuntu, CentOS, RHEL, SLES) alongside Windows VMs.
  • Add troubleshooting steps and supportability details for common Linux distributions, not just Windows Server.
  • Present Azure Hybrid Benefit information for Windows and Linux equally, with parallel explanations and links.
  • Ensure cost estimation and readiness review sections mention Linux licensing/subscription scenarios (e.g., bring-your-own subscription for RHEL/SLES, Ubuntu support).
  • In the Supportability section, show OS license support status and version distribution for both Windows and Linux VMs.
  • Where possible, avoid listing Windows tools, features, or options before Linux equivalents; present them side-by-side.
GitHub Create Pull Request
Migrate Tutorial to assess web apps in VMware VMs for migration to Azure App Service ...ain/articles/migrate/tutorial-assess-webapps-vmware.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by focusing primarily on ASP.NET web apps running on IIS (Windows-centric) and providing detailed steps for assessing these workloads. While Java/Tomcat (Linux-friendly) is mentioned, there are no explicit Linux server examples, commands, or screenshots. Windows tools and patterns (IIS, ASP.NET) are referenced first and in more detail, with no equivalent coverage for Linux-based web servers (e.g., Apache, Nginx) or Linux-specific migration considerations.
Recommendations
  • Add explicit examples and screenshots for assessing Java web apps on Linux servers (e.g., Ubuntu, CentOS) to match the detail given for ASP.NET/IIS.
  • Include Linux-specific prerequisites, such as commands for installing the Azure Migrate appliance on Linux, and troubleshooting tips for common Linux environments.
  • Reference Linux web server types (e.g., Apache, Nginx) in addition to Tomcat, and provide guidance for their migration assessment.
  • Ensure parity in step-by-step instructions, showing both Windows and Linux server workflows where applicable.
  • Clarify any differences in discovery, assessment, or migration steps between Windows and Linux platforms.
GitHub Create Pull Request
Migrate Tutorial to assess SQL instances in VMware VMs for migration to SQL Server on Azure VM, Azure SQL Managed Instance and Azure SQL Database ...ob/main/articles/migrate/tutorial-assess-sql-vmware.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page exhibits Windows bias primarily by referencing Windows-specific tools and patterns, such as Windows Server Failover Clusters and Cloud Witness, without mentioning Linux equivalents or alternatives. The high availability and disaster recovery section exclusively discusses Windows clustering approaches and does not provide guidance for Linux-based SQL deployments. There are no examples or instructions tailored for Linux environments, and Windows licensing (Azure Hybrid Benefit) is described before mentioning Linux (RHEL/SLES) support, which is only referenced briefly.
Recommendations
  • Include examples and guidance for assessing SQL Server instances running on Linux VMs, such as those using Pacemaker or other Linux clustering solutions.
  • Add documentation for high availability and disaster recovery options for Linux-based SQL Server deployments in Azure, including witness configuration and failover strategies.
  • Provide parity in licensing and cost optimization explanations for Linux (RHEL/SLES) alongside Windows, with clear instructions for applying Azure Hybrid Benefit to Linux subscriptions.
  • Ensure screenshots, step-by-step instructions, and configuration options are relevant for both Windows and Linux environments.
  • Explicitly mention any limitations or differences in assessment features for Linux SQL Server instances, if applicable.
GitHub Create Pull Request
Migrate Tutorial to assess SQL instances for migration to SQL Server on Azure VM, Azure SQL Managed Instance and Azure SQL Database ...docs/blob/main/articles/migrate/tutorial-assess-sql.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
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 or alternatives. The linked best practices for VM sizing point to Windows-focused guidance. There are no examples or instructions for Linux-based SQL Server deployments or high availability configurations, and Windows licensing is discussed before Linux licensing. No Linux/Powershell command-line examples or Linux-specific migration considerations are provided.
Recommendations
  • Include examples and guidance for assessing and migrating SQL Server instances running on Linux, such as SQL Server on Ubuntu or RHEL.
  • Reference Linux high availability solutions (e.g., Pacemaker, Corosync) alongside Windows Server Failover Clusters.
  • Provide links to Linux-specific best practices for SQL Server on Azure VMs.
  • Discuss Azure Hybrid Benefit for Enterprise Linux subscriptions in equal detail as for Windows Server.
  • Add screenshots and walkthroughs for Linux-based SQL Server deployments in the assessment workflow.
  • Clarify any differences in migration, licensing, or cost estimation for Linux-based SQL Server instances.
GitHub Create Pull Request
Migrate Discover servers on GCP instances with Azure Migrate Discovery and assessment ...cs/blob/main/articles/migrate/tutorial-discover-gcp.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
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 requirements for Windows Server 2019/2022. All setup and installation instructions rely on PowerShell, and the installer script installs Windows-specific roles and features (IIS, PowerShell ISE, Windows Activation Service). There are no Linux equivalents or examples for appliance deployment, nor is there guidance for running the appliance on Linux. Linux is only mentioned as a target for discovery, not as a platform for the appliance itself.
Recommendations
  • Provide instructions and support for deploying the Azure Migrate appliance on Linux servers, including supported distributions and prerequisites.
  • Include Linux shell (bash) examples for installation and configuration, alongside PowerShell instructions.
  • Clarify whether the appliance can be run in a Linux VM or container, and if not, explain the technical limitations.
  • Offer parity in troubleshooting and log file locations for Linux environments.
  • Ensure that all features (such as agentless dependency analysis and SQL Server discovery) are documented for Linux hosts where applicable.
  • List Linux tools and patterns (e.g., systemd services, SELinux/AppArmor considerations, firewall-cmd/iptables) where relevant.
GitHub Create Pull Request
Migrate Migrate Hyper-V VMs to Azure with the Migration and modernization tool ...blob/main/articles/migrate/tutorial-migrate-hyper-v.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation is strongly Windows-centric, focusing exclusively on migrating Hyper-V VMs (a Windows technology) and providing only Windows-based tooling, commands, and troubleshooting steps. All command-line examples use Windows paths and executables, and there is no mention of Linux equivalents, Linux-based Hyper-V hosts, or migration scenarios involving Linux guest VMs. Windows tools and patterns (e.g., SetupDiag, Windows activation troubleshooting) are referenced, and Linux is only mentioned in passing in post-migration best practices.
Recommendations
  • Clarify whether Linux guest VMs on Hyper-V are supported and provide guidance for their migration, including any OS-specific caveats.
  • Include examples or notes for migrating Linux-based VMs, such as handling Linux bootloaders, disk formats, and post-migration configuration.
  • If command-line automation is supported, offer Linux shell (bash) equivalents for relevant steps, or explicitly state that only Windows hosts are supported.
  • Add troubleshooting steps and references for common Linux migration issues (e.g., SSH key handling, network configuration, activation/licensing differences).
  • Balance references to Windows tools (e.g., SetupDiag) with Linux alternatives or clarify their applicability.
  • In post-migration best practices, provide more detail on securing and updating Linux VMs, not just Windows.
GitHub Create Pull Request
Migrate Discover AWS instances with Azure Migrate Discovery and assessment ...cs/blob/main/articles/migrate/tutorial-discover-aws.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example Powershell Heavy 🔧 Windows Tools
Summary
The documentation demonstrates a Windows bias by requiring the Azure Migrate appliance to run on Windows Server, providing only PowerShell-based installation instructions, and referencing Windows-specific tools and patterns (IIS, registry keys, Windows roles). Linux instructions are limited to connectivity and authentication setup, with no Linux-based appliance deployment or installation examples. The documentation does not offer parity for Linux administrators wishing to deploy or manage the appliance natively on Linux.
Recommendations
  • Provide instructions and support for deploying the Azure Migrate appliance on Linux-based hosts, including supported distributions and system requirements.
  • Include Linux shell (bash) installation and configuration examples alongside PowerShell instructions.
  • Document Linux-native tools and patterns for appliance management, such as systemd service setup, log file locations, and package dependencies.
  • Clarify whether the appliance can be containerized or run in a cross-platform manner, and provide guidance for non-Windows environments.
  • Ensure all steps (download, install, configure, troubleshoot) have Linux equivalents, with screenshots and command-line examples.
  • Explicitly state OS limitations and roadmap for Linux support if Windows-only deployment is a current constraint.
GitHub Create Pull Request
Migrate Discover servers on Hyper-V with Azure Migrate Discovery and assessment ...lob/main/articles/migrate/tutorial-discover-hyper-v.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits a strong Windows bias. It consistently presents Windows and PowerShell-based instructions and tools first, and often exclusively, especially in setup, scripting, and troubleshooting steps. The use of Windows-specific tools (Hyper-V Manager, PowerShell, CertUtil, WinRM, Group Policy Editor) is pervasive, with little to no mention of Linux equivalents or alternative workflows. While Linux servers are mentioned as supported targets for discovery, there are no Linux-based examples, scripts, or guidance for deploying or managing the Azure Migrate appliance from a Linux environment.
Recommendations
  • Provide Linux-based instructions for deploying and managing the Azure Migrate appliance, including command-line examples for common Linux hypervisors (e.g., KVM, QEMU) where applicable.
  • Include Linux shell script equivalents for steps currently covered only by PowerShell scripts (e.g., validating file hashes, enabling remote management).
  • Mention and document Linux tools and patterns (such as SSH, systemd, firewall-cmd/iptables) alongside Windows tools for appliance setup and connectivity.
  • Offer troubleshooting and validation steps for Linux environments, including how to verify connectivity, permissions, and prerequisites using Linux commands.
  • Clarify which steps are Windows-specific and provide alternative guidance for Linux administrators where possible.
  • Add screenshots or walkthroughs showing the appliance setup and credential management from a Linux admin perspective.
GitHub Create Pull Request
Migrate Discover physical servers with Azure Migrate discovery and assessment ...ob/main/articles/migrate/tutorial-discover-physical.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits a Windows-first bias in several areas: Windows server preparation is described before Linux, with more detailed steps and troubleshooting guidance; the installer script is exclusively run via PowerShell with no mention of a Linux alternative; appliance installation and configuration steps reference Windows-specific tools (IIS, PowerShell ISE, registry keys) and file paths; troubleshooting and logs are described only for Windows; and there is no example or guidance for running the appliance installer or managing the appliance on Linux. Linux instructions are limited to credential setup and sudoers configuration, with no parity for appliance installation or troubleshooting.
Recommendations
  • Provide Linux-based installation instructions for the Azure Migrate appliance, including how to run the installer script on Linux servers.
  • Offer Linux equivalents for appliance management, such as log file locations, troubleshooting steps, and required packages/services.
  • Include Linux-first or parallel examples for credential setup, server discovery, and agentless dependency analysis.
  • Clarify whether the appliance can be installed and operated on Linux, and if not, state this explicitly and suggest alternatives for Linux environments.
  • Balance the order and detail of Windows and Linux sections to ensure equal guidance and visibility for both platforms.
GitHub Create Pull Request
Migrate Discover servers running in a VMware environment with Azure Migrate Discovery and assessment ...blob/main/articles/migrate/tutorial-discover-vmware.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits several signs of Windows bias. Windows-specific tools and patterns (such as PowerShell scripts and references to Windows authentication) are mentioned before or more prominently than Linux equivalents. The option to set up the Azure Migrate appliance using a PowerShell script on Windows Server is highlighted, while no analogous Linux-based setup method is described. Examples and instructions for credential provisioning and server access are more detailed for Windows (domain, non-domain, PowerShell, Active Directory) than for Linux (SSH key-based), and some features (such as SQL Server and IIS web app discovery) are described only in the context of Windows. Linux instructions are present but less detailed, and there are no Linux-first or Linux-only setup examples.
Recommendations
  • Provide explicit instructions and examples for setting up the Azure Migrate appliance on Linux servers, including a Linux-based installation method analogous to the PowerShell script for Windows.
  • Ensure that Linux credential provisioning (SSH key, password-based) is described with equal detail and step-by-step guidance as Windows credential provisioning.
  • Include Linux-first examples and screenshots where appropriate, such as using Linux tools to validate connectivity, configure the appliance, or troubleshoot issues.
  • Mention Linux tools and patterns (such as shell scripts, systemd services, or Linux package managers) alongside or before Windows tools when describing appliance setup and management.
  • Expand documentation for discovery and assessment of Linux-specific workloads and applications, not just SQL Server and IIS web apps.
  • Clarify any feature parity or limitations for Linux servers, and provide guidance for Linux administrators to achieve equivalent outcomes.
GitHub Create Pull Request
← Previous Page 5 of 37 Next →