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 401-425 of 918 flagged pages
Migrate https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/troubleshoot-appliance-diagnostic.md .../articles/migrate/troubleshoot-appliance-diagnostic.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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 license, and omitting any Linux-specific instructions, examples, or file locations. There are no references to Linux equivalents, nor are Linux troubleshooting steps or patterns provided, despite Azure Migrate appliances potentially running on Linux-based systems.
Recommendations
  • Include examples and instructions for Linux-based appliances, such as file paths (e.g., /home/public/Desktop/DiagnosticsReport) and report locations.
  • Mention Linux OS license considerations if applicable, or clarify OS support for the appliance.
  • Provide parity in troubleshooting steps for both Windows and Linux environments, including screenshots and remediation guidance.
  • Explicitly state platform requirements and supported operating systems for the appliance.
  • Add notes or sections for Linux-specific issues, such as permissions, SELinux/AppArmor, and service management (systemd, etc.).
GitHub Create Pull Request
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 →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example Powershell Heavy
Summary
The documentation page exhibits Windows bias in several ways: Windows/Hyper-V environments are referenced more frequently and in greater detail than Linux equivalents, especially in troubleshooting sections. Licensing cost calculations are only described for Windows servers, with Linux explicitly excluded. The network traffic capture instructions focus on Windows browsers (Edge, Internet Explorer) and omit Linux tools or browser variants. There are no Linux-specific troubleshooting examples, nor are Linux command-line tools (e.g., tcpdump, netstat) mentioned for diagnostics.
Recommendations
  • Include Linux-specific troubleshooting steps and examples, such as how to collect performance data from Linux VMs and physical servers.
  • Add instructions for capturing network traffic using Linux tools (e.g., tcpdump, Wireshark) and browser variants commonly used on Linux.
  • Clarify licensing cost considerations for Linux servers, or explain why they are omitted.
  • Balance references to Hyper-V and Windows environments with equivalent coverage for Linux and VMware environments.
  • Where agent or appliance installation is discussed, provide parity for Linux installation and configuration steps.
GitHub Create Pull Request
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 →
Scanned: 2026-01-08 00:53
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 tools and protocols (WinRM, WMI, WMICall, Get-WmiObject cmdlet) are mentioned before or more prominently than Linux equivalents, and troubleshooting steps often reference Windows-specific actions (such as modifying WinRM TrustedHosts or ensuring WinRM is running) with less detail or prominence given to Linux (e.g., SSH port 22 is mentioned but not expanded upon). Many error codes and recommended actions focus on Windows environments, with Linux guidance being less detailed or sometimes missing. The web apps discovery errors section is almost entirely focused on IIS and Windows-based web applications, with no equivalent guidance for Linux-based web servers (such as Apache or Nginx).
Recommendations
  • Provide Linux-specific troubleshooting steps and examples alongside Windows instructions, such as how to configure SSH, required permissions, and common issues for Linux servers.
  • Include Linux command-line examples (e.g., SSH, systemctl, journalctl) where Windows PowerShell or WinRM commands are given.
  • Ensure parity in error code explanations and recommended actions for both Windows and Linux environments.
  • Add troubleshooting guidance for common Linux web servers (Apache, Nginx, Tomcat) in the web apps discovery errors section.
  • Avoid mentioning Windows tools or protocols first unless they are more relevant; present Windows and Linux guidance in parallel where possible.
GitHub Create Pull Request
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 →
Scanned: 2026-01-08 00:53
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 bias in several ways: Windows tools (PowerShell, WinRM, WMI, Registry Editor, Control Panel, etc.) are referenced more frequently and often before their Linux equivalents. Troubleshooting steps and examples are predominantly PowerShell-based, with Linux commands provided less frequently and sometimes only as an afterthought. Many error codes and remediation steps are specific to Windows environments, and instructions for Linux are less detailed or missing in some cases. Windows-centric terminology and UI navigation (e.g., Control Panel, Registry Editor) are used without Linux equivalents, and PowerShell is the primary scripting language for validation and remediation, with Linux shell commands appearing less prominently.
Recommendations
  • Ensure Linux troubleshooting steps and examples are provided alongside Windows instructions for all relevant errors and scenarios.
  • Present Linux and Windows examples in parallel, rather than listing Windows first or exclusively.
  • Include Linux-specific tools and UI navigation (e.g., systemd, journalctl, /etc configs) where Windows tools like Registry Editor or Control Panel are mentioned.
  • Expand Linux error codes and remediation guidance to match the detail provided for Windows.
  • Use neutral language when referring to OS-specific commands and avoid assuming PowerShell as the default scripting environment.
  • Add more Linux command-line examples and clarify SSH troubleshooting steps, permissions, and common issues.
GitHub Create Pull Request
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 →
Scanned: 2026-01-08 00:53
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 appliance-side instructions exclusively for Windows environments (Remote Desktop, PowerShell commands, Windows file paths), while omitting Linux equivalents. All examples and tooling for the Azure Migrate appliance assume a Windows OS, with no mention of how to perform these steps on a Linux-based appliance. Windows tools and patterns (PowerShell, net stop/start, %programdata% paths) are used without alternatives or parity for Linux users.
Recommendations
  • Add instructions for performing appliance-side configuration and service restarts on Linux-based appliances (e.g., using SSH, systemctl/service commands, Linux file paths).
  • Provide Linux examples for editing configuration files and restarting services, alongside Windows instructions.
  • Clarify whether the Azure Migrate appliance supports Linux, and if so, ensure all troubleshooting steps are documented for both platforms.
  • Avoid using Windows-specific terminology and tools (e.g., PowerShell, Remote Desktop, %programdata%) without Linux equivalents.
  • Explicitly mention platform requirements and provide guidance for both Windows and Linux administrators.
GitHub Create Pull Request
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 →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Missing Linux Example Windows First
Summary
The documentation is heavily focused on IIS (a Windows web server) and PowerShell-based troubleshooting steps, with no mention of Linux-based web servers (such as Apache or Nginx), Linux migration scenarios, or equivalent Linux tools. All examples and error codes relate to Windows environments, and PowerShell is referenced as the primary automation/scripting tool. There is no guidance for users migrating Linux-hosted web apps.
Recommendations
  • Add troubleshooting steps and error codes for common Linux web servers (e.g., Apache, Nginx) and migration scenarios.
  • Include Linux-specific examples, such as using Bash scripts or Linux command-line tools for migration and troubleshooting.
  • Mention Linux migration prerequisites and common issues (e.g., file permissions, SELinux/AppArmor, systemd services).
  • Provide parity in documentation structure, ensuring Linux and Windows migration paths are equally represented.
  • Reference cross-platform tools where possible, or provide alternatives for PowerShell commands in Bash or other Linux shells.
GitHub Create Pull Request
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 →
Scanned: 2026-01-08 00:53
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 strong Windows bias. Troubleshooting steps and examples are almost exclusively provided for Windows environments, particularly for the Azure Migrate appliance running on Windows. PowerShell and Windows command prompt commands are used throughout, and tools like services.msc, Service Bus Explorer, and editing the Windows hosts file are referenced without Linux equivalents. There are no examples or instructions for performing these tasks on Linux-based appliances, nor is there guidance for using Linux-native tools or shell commands.
Recommendations
  • Provide equivalent troubleshooting steps for Linux-based Azure Migrate appliances, including commands for systemd/service management, network connectivity (e.g., using 'systemctl', 'service', 'netstat', 'ss', 'nc', or 'curl'), and file editing.
  • Include Linux shell command examples (e.g., bash) alongside PowerShell commands for tasks like network testing, DNS resolution, and file manipulation.
  • Reference Linux-compatible tools for interacting with Azure resources, such as Azure CLI, and clarify if tools like Service Bus Explorer or AzCopy are available and supported on Linux.
  • Explicitly state OS requirements and support for the Azure Migrate appliance, and if only Windows is supported, make this clear early in the documentation.
  • Where GUI steps are described (e.g., services.msc), provide CLI alternatives for Linux systems.
  • Add a section or callouts for Linux users, outlining any differences or limitations in troubleshooting and operation.
GitHub Create Pull Request
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 →
Scanned: 2026-01-08 00:53
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/Powershell tools and troubleshooting steps are presented first and in greater detail, with many remediation steps and error codes focused on Windows-specific technologies (PowerShell, WinRM, WMI, IIS). Linux troubleshooting is often mentioned only briefly or as a secondary note, and Linux-specific examples or commands are sparse or missing. For instance, PowerShell commands are used for both Windows and Linux validation, and Linux remediation steps are less detailed. Windows tools (WMI, IIS, PowerShell) are referenced extensively, while Linux equivalents (such as systemd, SSH, package managers) are not discussed.
Recommendations
  • Provide Linux-first or Linux-parity examples and troubleshooting steps alongside Windows instructions.
  • Include Linux-specific commands and tools (e.g., systemctl, journalctl, package manager commands) for error diagnosis and remediation.
  • Expand Linux error codes and remediation details to match the depth given to Windows (e.g., troubleshooting SSH, sudo, file permissions, SELinux/AppArmor issues).
  • Avoid assuming PowerShell is available for Linux troubleshooting; use native Linux shell commands and workflows.
  • For web app discovery, mention and support common Linux web servers (Apache, Nginx) and provide equivalent troubleshooting steps.
  • Clarify which steps are OS-agnostic and which are OS-specific, and ensure both Windows and Linux paths are equally documented.
  • Add more Linux-focused screenshots and UI references where applicable.
GitHub Create Pull Request
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 →
Scanned: 2026-01-08 00:53
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, recommendations, and linked resources pertaining to Windows. There is no mention of Linux OS upgrades, Linux-specific migration issues, or parity in troubleshooting steps for non-Windows platforms. The use of Windows-centric tools and terminology (e.g., Azure VM SKU, Windows disk expansion, Windows OS upgrade links) further reinforces the Windows bias.
Recommendations
  • Add equivalent troubleshooting sections for Linux OS upgrades during VM migration, including common issues and recommended actions.
  • Provide examples and links for expanding Linux OS disks and verifying disk space requirements on Linux VMs.
  • Include guidance for Linux VM SKU selection and migration steps, ensuring parity in documentation structure and detail.
  • Reference Linux-specific migration tools or commands (e.g., using SSH, Linux disk utilities) alongside Windows tools.
  • Clarify in the introduction that the article is Windows-specific, or create a parallel article for Linux OS upgrade troubleshooting.
GitHub Create Pull Request
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 →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example Powershell Heavy 🔧 Windows Tools
Summary
The documentation is heavily biased toward Windows environments for ASP.NET app containerization. All instructions, prerequisites, and tooling are centered on Windows machines, PowerShell, and Windows-specific tools (such as Microsoft Web Deploy). There are no Linux-based examples or guidance for containerizing ASP.NET apps from Linux servers, nor are Linux equivalents for required steps or tools mentioned. The tutorial assumes the reader is using Windows throughout, and Linux is only referenced in the context of Java/Tomcat apps.
Recommendations
  • Provide guidance and examples for containerizing ASP.NET apps from Linux environments, if supported.
  • Mention and document Linux-compatible alternatives to PowerShell remoting and Microsoft Web Deploy, or clarify platform limitations.
  • Explicitly state platform support and limitations at the beginning of the tutorial.
  • If the tool is Windows-only, suggest alternative approaches for Linux users (e.g., manual Dockerfile creation, use of cross-platform tools).
  • Where possible, offer parity in troubleshooting steps and prerequisites for Linux environments.
  • Add a comparison table of supported platforms and scenarios for ASP.NET and Java apps.
GitHub Create Pull Request
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 →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation demonstrates a Windows bias by emphasizing ASP.NET (a Windows-centric technology) and referencing Windows node pools as a requirement for ASP.NET apps. There are no explicit Linux or cross-platform examples, and the optimization guidance specifically points to Windows Dockerfiles. Linux equivalents, such as Linux node pools or Dockerfile optimization for Linux, are not mentioned or are omitted from the 'Next steps' and cost breakdown sections.
Recommendations
  • Include explicit Linux examples and guidance, especially for Java web apps, such as optimizing Linux Dockerfiles and Linux node pool recommendations.
  • In the cost details section, clarify when Linux node pools are recommended (e.g., for Java apps) and provide parallel examples for Linux-based workloads.
  • Balance the 'Next steps' by linking to both Windows and Linux container best practices and optimization guides.
  • Wherever Windows-specific requirements are mentioned (such as for ASP.NET), add corresponding notes for Linux-based apps (such as Java) to ensure parity and clarity.
  • Ensure screenshots and walkthroughs include both Windows and Linux scenarios where applicable.
GitHub Create Pull Request
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 →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates Windows bias in several ways. It references Windows-specific tools and patterns, such as Windows Server Failover Clusters and Cloud Witness, without mentioning Linux equivalents or alternatives. The linked best practices for VM sizing point to Windows-specific guidance. There are no examples or instructions for Linux-based SQL Server deployments, nor is there mention of Linux failover clustering or witness configurations. The Azure Hybrid Benefit section mentions RHEL and SLES, but the licensing and migration guidance is focused on Windows environments.
Recommendations
  • Include explicit instructions and examples for assessing SQL Server instances running on Linux (e.g., Ubuntu, RHEL, SLES).
  • Reference Linux-specific clustering and high availability options, such as Pacemaker or Corosync, and provide links to relevant Azure documentation.
  • Add parity in guidance for witness configuration in failover clusters on Linux, such as using file share or cloud-based witnesses.
  • Ensure that VM sizing and performance best practices link to both Windows and Linux SQL Server documentation.
  • Clarify licensing and Azure Hybrid Benefit applicability for Linux SQL Server deployments, including any differences from Windows licensing.
GitHub Create Pull Request
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 →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in several ways. Windows Server and its licensing are mentioned first and more prominently than Linux equivalents (RHEL and SLES) in the Azure Hybrid Benefit section. The Supportability section in assessment review focuses on Windows Server version distribution, with no mention of Linux distributions. There are no Linux-specific examples, troubleshooting steps, or references to Linux tools or patterns, and the documentation does not provide parity in guidance for Linux VMs (e.g., readiness checks, licensing, or migration caveats).
Recommendations
  • Include explicit examples and guidance for Linux VMs (e.g., readiness checks, licensing, migration caveats for common distributions such as Ubuntu, CentOS, Debian, etc.).
  • In the Azure Hybrid Benefit section, mention Linux licensing and eligibility before or alongside Windows Server, and clarify the process for both.
  • Expand the Supportability and readiness review sections to include Linux OS versions and support status, not just Windows Server.
  • Add troubleshooting steps and common issues for Linux VMs in the assessment report section.
  • Ensure screenshots and UI references show both Windows and Linux VM scenarios where applicable.
GitHub Create Pull Request
Migrate https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/tutorial-assess-webapps.md .../blob/main/articles/migrate/tutorial-assess-webapps.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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 by focusing primarily on ASP.NET web apps running on IIS (Windows) servers, mentioning Windows-centric tools and patterns first, and lacking equivalent Linux-specific examples or guidance. While there is a mention of Java web apps on Tomcat (Linux), the overall structure, examples, and terminology are Windows-first, with no explicit Linux command-line or migration tool examples provided.
Recommendations
  • Provide explicit Linux-based examples, such as migration steps for Apache/Nginx web servers or Linux-hosted Java applications.
  • Include screenshots and walkthroughs for Linux environments alongside Windows/IIS examples.
  • Mention and document Linux-native tools and commands (e.g., Bash, SSH, systemd) where appropriate, not just Windows/Powershell.
  • Ensure parity in prerequisites and assessment steps for both Windows and Linux web apps, including discovery, grouping, and migration.
  • Add troubleshooting and best practices sections for common Linux migration scenarios.
GitHub Create Pull Request
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 →
Scanned: 2026-01-08 00:53
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 available for Windows, with installation instructions and prerequisites focused exclusively on Windows machines (Windows Server/Windows 10). All setup and usage examples use PowerShell and Windows-specific paths. There are no instructions or examples for installing or running the tool on Linux or macOS, nor are alternative Linux-native tools or workflows mentioned. Troubleshooting is limited to Windows file paths. This creates a barrier for users who primarily use Linux environments, despite the fact that the applications being containerized are running on Linux servers.
Recommendations
  • Provide a Linux version of the Azure Migrate: App Containerization tool, or clarify platform limitations early in the documentation.
  • Include installation and usage instructions for Linux (and macOS, if possible), using native shell commands and file paths.
  • Offer troubleshooting guidance for Linux environments, or suggest alternative approaches for Linux users.
  • If the tool is Windows-only, suggest open-source or Azure-supported alternatives for Linux users to achieve similar containerization and migration workflows.
  • Clearly state platform requirements and limitations in the prerequisites section to set expectations for cross-platform users.
GitHub Create Pull Request
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 →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation demonstrates a Windows bias in several ways. It references Windows-specific tools and patterns, such as Windows Server Failover Clusters and Cloud Witness, and links to Windows-focused best practices. There are no Linux-specific examples, instructions, or equivalent tooling mentioned for Linux SQL Server deployments. The Azure Hybrid Benefit section briefly mentions RHEL and SLES, but the overall tutorial and high availability guidance are Windows-centric, with no parity for Linux scenarios.
Recommendations
  • Add explicit guidance and examples for assessing and migrating SQL Server instances running on Linux VMs, including screenshots and step-by-step instructions.
  • Include references to Linux-specific high availability and disaster recovery patterns, such as Pacemaker clusters or Linux-based witness options.
  • Provide links to Azure SQL performance guidelines and best practices for Linux, not just Windows.
  • Clarify where features or recommendations differ for Linux-based SQL Server deployments, especially in areas like licensing, storage, and failover.
  • Ensure parity in documentation structure, so Linux users can follow equivalent steps and understand any platform-specific caveats.
GitHub Create Pull Request
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 →
Scanned: 2026-01-08 00:53
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 Windows bias in several areas: 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 use PowerShell and reference Windows-specific tools (IIS, Windows Activation Service, registry keys, etc.), with no Linux alternatives or examples. The appliance installer script is a PowerShell script, and there are no instructions for running or deploying the appliance on Linux. Linux is only mentioned in the context of being a discovery target, not as a platform for the appliance itself.
Recommendations
  • Provide parity by supporting and documenting the Azure Migrate appliance on Linux (e.g., Ubuntu, CentOS), including prerequisites, installation steps, and troubleshooting.
  • Offer Linux shell (bash) examples for setup and configuration, alongside PowerShell instructions.
  • Document Linux equivalents for Windows tools used (e.g., alternatives to IIS, registry, etc.), or clarify cross-platform requirements.
  • Explicitly state OS limitations and roadmap for Linux support, if not currently available.
  • Ensure that discovery and assessment features are equally available and documented for Linux hosts, not just Windows.
GitHub Create Pull Request
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 →
Scanned: 2026-01-08 00:53
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 bias in several ways: Windows server preparation is described first and in greater detail, with explicit PowerShell and Windows-specific tooling (WinRM, IIS, registry, Windows roles) referenced throughout. The installer script is only described as a PowerShell script to be run on Windows, with no mention of a Linux-native installation or script. Linux instructions are present but less detailed, and there are no Linux-specific installer or configuration examples. Windows tools and patterns (PowerShell, WinRM, registry, IIS) are mentioned exclusively or before their Linux equivalents.
Recommendations
  • Provide parity in installer instructions for Linux servers, including a Linux-native installation script or process.
  • Include Linux-specific examples for running and configuring the Azure Migrate appliance, not just Windows/PowerShell.
  • Mention Linux tools and patterns (e.g., systemd, SSH, Linux file paths) where relevant, and describe their equivalents to Windows tools.
  • Ensure Linux server preparation steps are as detailed and prominent as Windows steps, possibly presenting both side-by-side.
  • Clarify whether the Azure Migrate appliance can be installed and run natively on Linux, and if not, provide guidance for Linux users (e.g., via containers, VMs, or alternative approaches).
  • Avoid presenting Windows instructions first by default; consider parallel or OS-neutral organization.
GitHub Create Pull Request
Migrate https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/tutorial-discover-vmware.md ...blob/main/articles/migrate/tutorial-discover-vmware.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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 (e.g., PowerShell scripts, references to Windows Server versions, and Windows authentication mechanisms) are mentioned before or more prominently than their Linux equivalents. The option to set up the Azure Migrate appliance using a PowerShell script on Windows Server is highlighted, while no equivalent Linux-based setup method is described. Windows requirements (such as PowerShell installation) are called out explicitly, whereas Linux instructions are less detailed and lack example commands. Windows tools (like VMware Tools and VDDK installation paths using Windows file system conventions) are referenced without Linux alternatives. There are no Linux shell command examples or detailed Linux setup instructions, and Windows authentication mechanisms are discussed in more depth than Linux (SSH) authentication.
Recommendations
  • Provide equivalent Linux-based setup instructions for the Azure Migrate appliance, including shell script or manual deployment steps.
  • Include Linux command-line examples (e.g., SSH key generation, file extraction, service management) alongside Windows/PowerShell examples.
  • Clarify Linux requirements (such as minimum SSH version, required packages, or configuration steps) with the same level of detail as Windows prerequisites.
  • Reference Linux file system paths and conventions when discussing installation steps (e.g., VDDK extraction location).
  • Discuss Linux authentication mechanisms (such as SSH password and key-based authentication) with examples and troubleshooting tips.
  • Balance the coverage of Windows and Linux tools, ensuring that Linux-specific tools and patterns are mentioned with equal prominence.
  • Add troubleshooting sections for common Linux issues encountered during discovery and assessment.
GitHub Create Pull Request
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 →
Scanned: 2026-01-08 00:53
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 or 2022. The installation and configuration steps rely exclusively on PowerShell scripts and Windows-specific tools (IIS, Windows Activation Service, registry edits), with no mention of Linux equivalents or support for running the appliance on Linux. Examples and instructions for running scripts, managing files, and troubleshooting are all Windows-centric, and Linux is only referenced as a target for discovery, not as a platform for hosting the appliance or running the migration tooling.
Recommendations
  • Add support and documentation for running the Azure Migrate appliance on Linux servers, including prerequisites, installation, and configuration steps using Bash or shell scripts.
  • Provide Linux-based examples for script execution, file management, and troubleshooting, alongside PowerShell/Windows instructions.
  • Mention Linux tools and patterns (e.g., systemd, journalctl, SSH, Apache/Nginx) where relevant, and ensure parity in troubleshooting and validation steps.
  • Clarify any limitations or roadmap for Linux appliance support if not currently available, and link to alternative solutions for Linux users.
  • Ensure that examples and instructions for both Windows and Linux are presented in parallel, rather than Windows-first.
GitHub Create Pull Request
Migrate https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/tutorial-migrate-gcp-virtual-machines.md ...icles/migrate/tutorial-migrate-gcp-virtual-machines.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a Windows bias in several areas. The replication appliance required for migration must run on Windows Server (2012 R2 or 2016), with no mention of Linux support for this critical component. Windows-specific tools and ports (WinRM, WMI) are referenced before Linux equivalents, and screenshots and step-by-step instructions focus on Windows environments. While Linux instructions are present for VM preparation and agent installation, the overall workflow and tooling are centered around Windows, with Linux support appearing as an add-on rather than a first-class citizen.
Recommendations
  • Provide parity for Linux by supporting the replication appliance on Linux distributions, or clearly document any limitations and alternatives for Linux users.
  • Include Linux-first examples and instructions where possible, such as using SSH and Linux-native tools for discovery and migration steps.
  • Balance the order of instructions and examples so that Linux and Windows are treated equally (e.g., mention Linux and Windows prerequisites together, not Windows first).
  • Add screenshots and step-by-step guides for Linux environments, not just Windows.
  • Explicitly state any limitations or differences in the migration process for Linux VMs, and offer workarounds or alternative workflows.
  • Ensure troubleshooting and FAQ sections address Linux-specific issues as thoroughly as Windows ones.
GitHub Create Pull Request
Migrate https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/tutorial-migrate-aws-virtual-machines.md ...icles/migrate/tutorial-migrate-aws-virtual-machines.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation page exhibits Windows bias in several areas. Windows Server is the only supported OS for the replication appliance, with no mention of Linux alternatives. Windows-specific tools and ports (WinRM, WMI) are referenced before Linux equivalents, and troubleshooting focuses on Windows management services. While some Linux instructions are present, they are less detailed and secondary to Windows steps. There is a lack of parity in examples and supported tooling for Linux users.
Recommendations
  • Provide Linux-based options for hosting the replication appliance, or clarify if only Windows is supported and explain why.
  • Include Linux-first examples and troubleshooting steps alongside Windows ones, especially for common tasks like authentication and agent installation.
  • Mention Linux tools (e.g., SSH, systemd) before or alongside Windows tools (WinRM, WMI) when discussing prerequisites and network configuration.
  • Expand the agent installation section with more detailed Linux instructions, including automation options (e.g., Ansible, shell scripts).
  • Add troubleshooting guidance for Linux-specific migration issues, such as SELinux, systemd, or common Linux distributions.
  • Ensure parity in screenshots and UI walkthroughs for both Windows and Linux scenarios.
GitHub Create Pull Request
Migrate https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/tutorial-migrate-hyper-v.md ...blob/main/articles/migrate/tutorial-migrate-hyper-v.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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 strong Windows bias. All examples, instructions, and tooling are focused exclusively on Windows environments (Hyper-V, Windows Server, Windows-specific utilities like SetupDiag). Command-line examples use Windows paths and executables, and there is no mention of Linux-based Hyper-V hosts, Linux guest VMs, or Linux-specific migration considerations. Windows tools and upgrade scenarios are described in detail, while Linux equivalents are absent or only mentioned in passing (e.g., Azure Update Manager).
Recommendations
  • Add explicit guidance for migrating Linux guest VMs running on Hyper-V, including any special considerations or limitations.
  • Include Linux-specific troubleshooting steps and post-migration best practices, such as activation, networking, and OS compatibility.
  • Provide command-line examples for Linux environments where applicable, or clarify that the process is Windows-only if Linux is unsupported.
  • Mention Linux tools and patterns (e.g., SSH, Linux disk formats, Linux VM sizing) alongside Windows tools, or provide links to relevant Linux migration documentation.
  • Clarify in prerequisites and throughout the document whether Linux Hyper-V hosts are supported, and if not, state this explicitly to avoid confusion.
GitHub Create Pull Request
Migrate https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/tutorial-migrate-vmware-agent.md ...main/articles/migrate/tutorial-migrate-vmware-agent.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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 areas: Windows Server is the default OS for the replication appliance, with explicit instructions for Windows installation and configuration, while Linux is only briefly mentioned. PowerShell is referenced as the manual setup method for the appliance, with no equivalent Linux scripting guidance. Windows-specific registry changes and activation troubleshooting are detailed, but Linux post-migration steps are minimal. The Azure VM agent installation is automated for Windows but only recommended (and manual) for Linux. Examples and step-by-step instructions consistently prioritize Windows, with Linux relegated to short notes or secondary mentions.
Recommendations
  • Provide explicit, step-by-step instructions for setting up the replication appliance on a Linux VM, including supported distributions and required packages.
  • Offer Linux shell script equivalents for manual appliance setup, mirroring the PowerShell instructions.
  • Include detailed Linux-specific troubleshooting steps for post-migration issues, similar to the Windows activation section.
  • Expand the guidance for preparing Linux VMs, including common configuration changes, security considerations, and agent installation procedures.
  • Ensure parity in examples and screenshots, showing both Windows and Linux scenarios where applicable.
  • Clarify which features and steps apply to both OS types, and highlight any differences in process or requirements.
GitHub Create Pull Request
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
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates Windows bias by requiring Windows PowerShell 4.0 for migration, referencing IIS web servers (Windows-specific), and omitting any mention of Linux-based web app migration or equivalent Linux tooling. There are no examples or guidance for migrating from Linux environments, nor are Linux command-line tools or procedures discussed.
Recommendations
  • Add explicit guidance and examples for migrating ASP.NET web apps hosted on Linux (e.g., with Apache, Nginx, or Kestrel).
  • Include Linux-compatible migration tooling or alternatives to Windows PowerShell, such as Bash scripts or Azure CLI commands.
  • Clarify whether the migration flow supports Linux-based ASP.NET Core apps and document any differences or limitations.
  • Mention Linux prerequisites and provide parity in instructions for both Windows and Linux environments.
  • If migration from Linux is not supported, state this limitation clearly and suggest alternative approaches for Linux users.
GitHub Create Pull Request
← Previous Page 17 of 37 Next →