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 301-325 of 918 flagged pages
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-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation demonstrates a strong Windows bias. The Azure Migrate: App Containerization tool is only available for Windows, with explicit requirements for a Windows machine (Windows Server or Windows 10) to run the tool. All installation instructions use PowerShell, and there are no Linux equivalents or alternatives provided. Troubleshooting steps reference Windows file paths, and there is no mention of Linux-native installation, usage, or troubleshooting. The documentation assumes users have access to Windows environments even when migrating Linux-based Java applications.
Recommendations
  • Provide a Linux-native version of the Azure Migrate: App Containerization tool, or document how to run the tool on Linux (e.g., via containers or WSL).
  • Include installation and usage instructions for Linux environments, using bash and Linux-native tools.
  • Offer troubleshooting steps and log file locations for Linux installations.
  • Clearly state Windows-only limitations at the beginning and suggest alternatives for Linux-only users.
  • If Windows is a hard requirement, provide rationale and guidance for Linux users (e.g., using a VM or cloud-hosted Windows environment).
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-09 00:34
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 primarily in the context of ASP.NET app migration. It references Windows-specific requirements (such as the need for Windows node pools for ASP.NET apps), mentions optimizing Windows Dockerfiles, and does not provide Linux-based examples or guidance for Linux-hosted ASP.NET or Java apps. The focus on Windows environments and tooling is evident, while Linux scenarios and tools are not addressed or are missing.
Recommendations
  • Include explicit guidance and examples for migrating Linux-hosted ASP.NET Core and Java web apps, not just Windows-based ASP.NET.
  • Provide parity in Dockerfile optimization guidance by linking to Linux Dockerfile best practices alongside Windows Dockerfile optimization.
  • Clarify when Linux node pools are sufficient (e.g., for ASP.NET Core or Java apps) and provide examples or notes for Linux-based deployments.
  • Reference Linux-native tools and patterns (such as Bash scripts, Linux CLI commands) where appropriate, not just Windows/PowerShell.
  • Ensure screenshots and walkthroughs include both Windows and Linux scenarios where the experience differs.
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-09 00:34
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 through the exclusive mention of Windows Server Failover Clusters and Cloud Witness for high availability and disaster recovery in Azure VMs. The referenced best practices and configuration links are for Windows-based SQL Server deployments, with no mention of Linux-based SQL Server or Linux clustering technologies. There are no examples, instructions, or references for Linux SQL Server instances, migration scenarios, or Linux-specific high availability/disaster recovery patterns. The Azure Hybrid Benefit section briefly mentions RHEL/SLES but does not provide parity in guidance or examples for Linux environments.
Recommendations
  • Add explicit instructions and examples for assessing and migrating SQL Server instances running on Linux (e.g., Ubuntu, RHEL, SLES) in VMware VMs.
  • Include references and links to best practices for running SQL Server on Linux in Azure VMs, such as performance guidelines and sizing recommendations.
  • Provide guidance for high availability and disaster recovery for Linux-based SQL Server deployments, including supported clustering technologies (e.g., Pacemaker, Linux witness options).
  • Ensure parity in migration scenarios and readiness checks for both Windows and Linux SQL Server instances.
  • Clarify Azure Hybrid Benefit applicability and licensing for Linux SQL Server environments, with concrete examples.
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-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a mild Windows bias. Windows Server and its licensing are mentioned first and in more detail than Linux equivalents (RHEL and SLES), especially in the Azure Hybrid Benefit section. The 'Supportability' section highlights Windows Server version distribution, but does not mention Linux distributions. There are no explicit Linux-specific examples, troubleshooting steps, or references to Linux tools or patterns. All instructions and screenshots are generic, but the language and examples favor Windows environments.
Recommendations
  • Provide explicit examples and guidance for assessing Linux VMs, including common distributions (Ubuntu, CentOS, Debian, etc.), not just RHEL/SLES.
  • In the 'Supportability' section, include information and visuals about Linux OS license support status and distribution by Linux version.
  • Clarify how Azure Migrate handles Linux-specific configurations, such as disk partitioning, network settings, and licensing.
  • Mention Linux licensing options and cost estimation details with parity to Windows Server.
  • Add troubleshooting steps and common issues for Linux VMs in the 'Review issues' section.
  • Ensure that references to OS types (Windows, Linux) are balanced throughout the documentation.
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-09 00:34
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 them before Java/Tomcat (Linux) equivalents. There is a lack of Linux-specific examples, tools, or migration patterns, and no mention of Linux-native web servers (e.g., Apache, Nginx) or command-line tools commonly used in Linux environments. The tutorial steps and screenshots are generic but implicitly favor Windows-centric scenarios, with no parity in Linux migration guidance or examples.
Recommendations
  • Add explicit examples and instructions for assessing and migrating Linux-based web apps, such as those running on Apache or Nginx.
  • Include Linux command-line examples (e.g., Bash scripts) alongside any PowerShell or Windows GUI steps.
  • Ensure screenshots and UI references reflect both Windows and Linux server scenarios.
  • Mention Linux-specific migration considerations, such as file system differences, package management, and service management.
  • Provide parity in next steps and further reading for Linux web app migration, not just ASP.NET/IIS.
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-09 00:34
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: the Azure Migrate appliance is required to run on Windows Server (no Linux option is mentioned); all installer and setup instructions use PowerShell and Windows-specific tools (IIS, registry edits, Windows roles); Linux is only referenced for credential setup and SSH configuration, with no appliance installation or operational examples for Linux. Windows instructions and tools are presented first and in more detail, while Linux coverage is minimal and lacks parity.
Recommendations
  • Provide instructions and support for running the Azure Migrate appliance on Linux (e.g., Ubuntu, RHEL), including installation scripts and prerequisites.
  • Include Linux shell (bash) equivalents for all PowerShell commands and setup steps, or provide a cross-platform installer.
  • Document Linux-native tools and patterns (e.g., systemd services, Apache/Nginx for web apps, Linux file paths) where applicable.
  • Ensure examples and screenshots alternate or equally represent Linux environments.
  • Clarify any limitations or roadmap for Linux support if full parity is not yet available.
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-09 00:34
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. The setup and installation steps are exclusively described using PowerShell commands and Windows paths, with no Linux equivalents or instructions. Windows roles and tools (IIS, PowerShell ISE, registry edits) are mentioned, while Linux alternatives are absent. The appliance cannot be deployed on Linux, and all installer examples and troubleshooting paths are Windows-centric. Linux server discovery is covered only in terms of credential setup, not appliance deployment or management.
Recommendations
  • Add support for deploying the Azure Migrate appliance on Linux servers, or clarify if this is not possible.
  • Provide Linux-based installation instructions and examples (e.g., bash scripts, Linux service setup, Linux file paths).
  • Include troubleshooting steps and log file locations for Linux environments.
  • Mention Linux equivalents for Windows tools (e.g., Apache/Nginx instead of IIS, systemd instead of Windows services).
  • Ensure parity in examples and screenshots for both Windows and Linux environments.
  • Clearly state OS limitations and provide rationale if only Windows is supported for the appliance.
GitHub Create Pull Request
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 →
Scanned: 2026-01-09 00:34
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. Hyper-V is inherently a Windows technology, but the tutorial and examples consistently prioritize Windows tooling and workflows. PowerShell commands and Windows-specific utilities (WinRM, CertUtil, Local Group Policy Editor) are used exclusively for setup, validation, and credential delegation. All scripting and automation instructions are provided in PowerShell, with no Bash or Linux shell equivalents. While Linux server discovery is mentioned as supported, there are no Linux-specific setup examples, troubleshooting steps, or parity in tooling guidance. Windows Server versions and features are referenced first and in detail, while Linux support is only briefly acknowledged.
Recommendations
  • Provide Linux-specific setup and troubleshooting steps for environments where Linux servers are discovered, including examples using SSH and Linux command-line tools.
  • Include Bash or shell script equivalents for key automation steps, such as validating appliance integrity, configuring network access, and credential management.
  • Clarify which steps are Windows-only (e.g., PowerShell, WinRM, Local Group Policy Editor) and offer alternative instructions for Linux hosts or appliances where possible.
  • Expand documentation on Linux credential types, permissions, and validation workflows, including error handling and troubleshooting for Linux authentication.
  • Add screenshots and walkthroughs for Linux server onboarding and discovery, matching the detail provided for Windows environments.
  • Explicitly state limitations or differences in feature support between Windows and Linux, and provide links to Linux-focused guides or support matrices.
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-09 00:34
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 areas: Windows-specific tools (PowerShell) are mentioned as an alternative to OVA deployment, but no equivalent Linux-based setup is described. Windows requirements (such as PowerShell version, Windows authentication, and SQL Server discovery) are detailed, while Linux instructions are less comprehensive and lack parity in example depth. Windows tools and patterns (e.g., file paths, credential setup) are referenced before or instead of Linux equivalents, and there are no Linux command-line examples or troubleshooting steps.
Recommendations
  • Provide a Linux-based alternative for appliance setup, such as a bash script or instructions for deploying on a Linux VM, with step-by-step examples.
  • Include Linux command-line examples for credential setup, troubleshooting, and verification, similar to the PowerShell instructions for Windows.
  • Clarify Linux-specific requirements and supported authentication mechanisms with equal detail as Windows (e.g., supported distributions, SSH configuration, SELinux/AppArmor considerations).
  • Add troubleshooting steps and common issues for Linux environments, including log file locations and permissions.
  • Ensure that Linux tools and patterns are mentioned alongside Windows equivalents, not only as secondary options.
  • Review and update screenshots and UI instructions to show Linux server scenarios where applicable.
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-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation exhibits 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. Instructions for downloading and installing the replication appliance exclusively reference Windows, and screenshots show Windows environments. Troubleshooting sections and migration steps often mention Windows-specific tools and issues (e.g., WinRM, Windows activation), with Linux guidance provided only for specific configuration changes (e.g., SSH settings). Linux examples are present for agent installation, but overall, Windows tools and patterns are prioritized and Linux parity is lacking, especially for the replication appliance setup.
Recommendations
  • Provide clear guidance or alternatives for deploying the replication appliance on Linux, or explicitly state its lack of support and suggest workarounds for Linux-only environments.
  • Ensure that all major steps (e.g., appliance setup, agent installation, troubleshooting) include Linux-specific instructions and examples where applicable.
  • Balance the order of presentation so that Linux instructions are given equal prominence to Windows instructions, rather than listing Windows steps first.
  • Include troubleshooting steps and post-migration guidance for common Linux issues (e.g., SELinux, systemd, networking) alongside Windows-specific advice.
  • Add screenshots and command-line examples from Linux environments to match those provided for Windows.
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-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation is heavily focused on Windows environments, specifically Hyper-V (a Windows-only hypervisor). All examples and instructions use Windows tools, file paths, and command syntax (e.g., .exe installers, %Programdata% paths, Windows registry keys, and Windows-specific utilities like SetupDiag). There are no Linux equivalents or alternative instructions for migrating Linux-based VMs or using Linux hosts. The documentation assumes the reader is operating in a Windows ecosystem and does not address scenarios involving Linux hypervisors or Linux guest VMs in any detail.
Recommendations
  • Add explicit guidance for migrating Linux guest VMs running on Hyper-V, including any special considerations for Linux OS activation, drivers, or post-migration steps.
  • Include examples of command-line operations using PowerShell and, where possible, equivalent Bash or cross-platform tools.
  • Clarify the scope: If the tool only supports Windows/Hyper-V, state this clearly at the beginning. If Linux VMs are supported, provide detailed instructions for those cases.
  • Reference Linux-based migration scenarios (e.g., KVM, Xen, or VMware on Linux) and link to relevant documentation for those platforms.
  • Where post-migration best practices are discussed, provide Linux-specific recommendations (e.g., for security, backup, and monitoring).
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-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation exhibits Windows bias in several ways: Windows Server is the only supported OS for the replication appliance, with no mention of a Linux alternative; Windows-specific tools and ports (WinRM, WMI) are referenced before Linux equivalents; and some procedures (such as appliance setup) are described only for Windows, with Linux options missing or relegated to secondary status. While Linux VM migration is supported, the documentation does not provide parity in examples, guidance, or tooling for Linux users.
Recommendations
  • Provide explicit instructions and support for deploying the replication appliance on Linux, if possible, or clarify its absence and suggest alternatives.
  • Include Linux-first examples and procedures alongside Windows ones, such as using SSH and Linux-native tools for discovery and migration steps.
  • List Linux prerequisites and configuration steps before or alongside Windows steps, rather than after.
  • Offer troubleshooting guidance specific to Linux VMs, not just Windows (e.g., SSH errors, SELinux, firewall settings).
  • If Windows-only tooling is required, clearly state this limitation and provide rationale, as well as alternative migration paths for Linux users.
  • Ensure that all screenshots, command-line examples, and step-by-step instructions are available for both Windows and Linux environments.
GitHub Create Pull Request
Migrate https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/tutorial-migrate-physical-virtual-machines.md .../migrate/tutorial-migrate-physical-virtual-machines.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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-specific tools (e.g., PowerShell scripts, SetupDiag) are referenced as the primary or only method for appliance setup and troubleshooting; instructions and screenshots frequently assume Windows Server as the host OS for the replication appliance; registry and group policy checks are Windows-centric; and upgrade/test migration steps focus on Windows Server OS upgrades, with no equivalent Linux upgrade guidance. Linux is mentioned as supported, but Linux-specific examples, commands, or troubleshooting steps are missing, and Windows procedures are presented first or exclusively.
Recommendations
  • Add explicit Linux-based instructions for deploying and configuring the replication appliance, including supported Linux distributions and required packages.
  • Provide Linux shell (bash) script examples for appliance setup and agent installation, alongside PowerShell examples.
  • Include troubleshooting steps and checks relevant to Linux environments (e.g., systemd services, SELinux/AppArmor, firewall rules), not just Windows registry/group policy.
  • Offer guidance for Linux OS upgrades during migration, similar to the Windows Server upgrade instructions.
  • Ensure screenshots and walkthroughs include Linux scenarios (e.g., appliance running on Ubuntu or RHEL) as well as Windows.
  • Clarify which steps are OS-agnostic and which require OS-specific actions, and present both Windows and Linux options side-by-side where possible.
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-09 00:34
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 areas: Windows Server is the default OS for the replication appliance, with explicit instructions and screenshots for Windows setup, while Linux is only briefly mentioned as an alternative for VM accounts. PowerShell is referenced as the manual setup method for the appliance, with no Linux shell or automation alternatives provided. The Azure VM agent installation is automated for Windows but manual for Linux, and there are no detailed Linux-specific migration or troubleshooting steps. Windows-specific registry changes and activation troubleshooting are included, but Linux equivalents are not. VMware tools removal is mentioned for both, but only Windows details are given.
Recommendations
  • Provide step-by-step instructions for setting up the replication appliance on a Linux VM, including supported distributions and prerequisites.
  • Include Linux shell (bash) or Ansible script examples for manual appliance setup, not just PowerShell.
  • Offer parity in troubleshooting and post-migration steps for Linux VMs, such as activation, agent installation, and common issues.
  • Add Linux-specific examples for Mobility service installation, including sudo/root account usage, and clarify differences in process.
  • Ensure that all Windows-specific configuration steps (e.g., registry edits, activation) have Linux equivalents or explicitly state when not applicable.
  • Present Windows and Linux instructions side-by-side, or clearly label sections for each OS, to avoid implicit prioritization.
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-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Missing Linux Example Windows First
Summary
The documentation demonstrates a Windows bias by requiring Windows PowerShell 4.0 on IIS servers for migration, with no mention of Linux-based alternatives or support for migrating from Linux-hosted ASP.NET apps. All examples and prerequisites focus on Windows environments, and there are no Linux-specific instructions, tools, or parity considerations.
Recommendations
  • Clarify whether Linux-hosted ASP.NET Core apps are supported for migration, and if so, provide explicit instructions for Linux environments.
  • Offer Linux command-line alternatives (e.g., Bash scripts, Azure CLI) for any steps currently requiring PowerShell.
  • Include prerequisites and troubleshooting steps for Linux servers, such as supported distributions and required packages.
  • Add examples or notes for migrating web apps from Linux-based web servers (e.g., Apache, Nginx) if supported.
  • Explicitly state platform limitations and future roadmap for Linux parity if migration is currently Windows-only.
GitHub Create Pull Request
Migrate https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/tutorial-migrate-vmware.md .../blob/main/articles/migrate/tutorial-migrate-vmware.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation demonstrates a Windows bias in several areas: all command-line examples for monitoring and managing migration are provided exclusively in PowerShell, with no mention of Bash, Azure CLI, or Linux-native alternatives. The instructions and notes repeatedly reference running commands on Windows or Windows PowerShell, and tools like SetupDiag (Windows-specific) are discussed without Linux equivalents. Windows-specific upgrade and troubleshooting steps are highlighted, while Linux migration scenarios and commands are not addressed. This creates an impression that the process is primarily designed for Windows users, with Linux support being secondary or assumed but not documented.
Recommendations
  • Provide equivalent Azure CLI (az) or Bash command examples for all PowerShell commands, especially for monitoring migration status, so Linux and cross-platform users are equally supported.
  • Explicitly state that all migration and monitoring steps can be performed from Linux/macOS using Azure CLI or Cloud Shell (Bash), and provide instructions or links.
  • When referencing tools like SetupDiag (Windows-only), add notes about how to troubleshoot or handle similar scenarios for Linux VMs, or link to relevant Linux documentation.
  • Include Linux-specific migration considerations, such as OS upgrade options, agent installation, and post-migration troubleshooting, to ensure parity with the detailed Windows guidance.
  • Review all screenshots and UI instructions to ensure they are not Windows-centric, and add Linux-relevant visuals or clarifications where appropriate.
GitHub Create Pull Request
Migrate https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/whats-new.md ...ocs/azure-docs/blob/main/articles/migrate/whats-new.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation for Azure Migrate demonstrates a Windows bias in several ways. Windows Server and related technologies (PowerShell, IIS, SCOM, Windows Virtual Desktop) are frequently mentioned first or exclusively, with Linux-specific examples and tools appearing less often and sometimes only as secondary notes. Many migration scenarios, tool integrations, and feature highlights focus on Windows environments, and PowerShell is often referenced as the automation method, with little mention of Bash or Linux-native alternatives. Some features (e.g., OS upgrades, redeployment, dependency analysis) provide detailed Windows workflows but lack equivalent Linux guidance or examples.
Recommendations
  • Ensure Linux migration scenarios are described with equal detail, including examples for common Linux distributions (e.g., Ubuntu, CentOS, RHEL, SLES).
  • Provide Bash or shell script examples alongside PowerShell for automation tasks, especially for agentless migration, dependency analysis, and onboarding.
  • Highlight Linux-specific tools and patterns (e.g., systemd, SSH, sudo, SELinux) where relevant, and mention them before or alongside Windows tools.
  • Add explicit Linux application migration examples (e.g., Apache, Nginx, PostgreSQL, MySQL, Java apps on Tomcat) in feature announcements and tutorials.
  • Balance the order of presentation so that Linux and Windows environments are both covered in introductions, feature lists, and summaries.
  • Include troubleshooting and best practices sections for Linux migrations, not just Windows.
  • Review RBAC and security recommendations to ensure Linux-specific concerns (e.g., file permissions, sudo access) are addressed.
GitHub Create Pull Request
Migrate https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/best-practices-assessment.md ...lob/main/articles/migrate/best-practices-assessment.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 focusing on Windows-centric technologies and migration scenarios, such as IIS/ASP.NET web apps and SQL Server, without mentioning Linux workloads or providing Linux-specific examples. The only web app migration scenario discussed is for ASP.NET on IIS, and there are no references to Linux-based web servers (e.g., Apache, Nginx) or databases (e.g., MySQL, PostgreSQL). Additionally, the migration tool guidance and troubleshooting steps do not address Linux-specific considerations or tools.
Recommendations
  • Include examples and assessment scenarios for Linux workloads, such as migrating Apache/Nginx web servers or MySQL/PostgreSQL databases.
  • Mention Linux distributions supported by Azure Migrate and provide parity in documentation for both Windows and Linux server migrations.
  • Add troubleshooting and best practices sections specific to Linux environments (e.g., agent installation, performance data collection, common issues).
  • When listing migration tools or patterns, include those relevant for Linux workloads (e.g., rsync, Azure Migrate agent for Linux, database migration tools for open-source databases).
  • Avoid presenting Windows scenarios (e.g., IIS, SQL Server) exclusively or before Linux equivalents; strive for balanced coverage.
GitHub Create Pull Request
Migrate https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/concepts-migration-webapps.md ...ob/main/articles/migrate/concepts-migration-webapps.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation is heavily Windows-centric, focusing exclusively on ASP.NET web apps running on Windows IIS servers. All requirements, examples, and tooling (such as PowerShell) are Windows-specific, with explicit statements that Linux servers are not supported and no mention of Linux migration paths, tools, or examples.
Recommendations
  • Clearly indicate the roadmap or plans for Linux support, if any, to inform non-Windows users.
  • Add a section comparing Windows and Linux migration support, even if Linux is not currently supported, to set expectations.
  • Provide alternative migration guidance or links for Linux-based web apps (e.g., PHP, Node.js, Java) to Azure App Service.
  • Mention Linux equivalents for tools (such as Bash scripts or CLI commands) where possible, or clarify that PowerShell is only required for Windows environments.
  • Ensure future updates include Linux migration scenarios and examples as soon as they are supported.
GitHub Create Pull Request
Migrate https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/common-questions-wave-planning.md ...ain/articles/migrate/common-questions-wave-planning.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page references PowerShell as a primary example for interacting with Azure Migrate data, and does not provide Linux-specific examples or mention Linux-native tools (such as Bash or Azure CLI on Linux) with equal prominence. The ordering of tools (Azure portal, Azure CLI, PowerShell, REST APIs, Power BI) also places PowerShell before REST APIs and does not clarify cross-platform parity. No Linux-specific workflows or screenshots are provided.
Recommendations
  • Add explicit examples for Linux users, such as Azure CLI commands run in Bash.
  • Ensure that PowerShell and Azure CLI examples are presented side-by-side, or alternate their order to avoid Windows-first impression.
  • Mention that Azure CLI and REST APIs are fully cross-platform and provide sample queries for both Windows and Linux environments.
  • Include screenshots or terminal output from Linux environments where applicable.
  • Clarify that PowerShell Core is cross-platform, if referenced, and provide installation guidance for Linux if needed.
GitHub Create Pull Request
Migrate https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/discover-and-assess-using-private-endpoints.md ...migrate/discover-and-assess-using-private-endpoints.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exhibits a strong Windows bias. All appliance installation and configuration instructions are provided exclusively for Windows environments, using PowerShell and Windows file paths (e.g., C:\Users, C:\Program Files). There are no examples or guidance for Linux-based hosts, nor are Linux shell commands or tools mentioned. The use of Windows-centric tools and terminology (PowerShell, .ps1 scripts, Windows file locations) is pervasive, and Linux equivalents are absent.
Recommendations
  • Provide parallel instructions for deploying and configuring the Azure Migrate appliance on Linux hosts, including shell script examples and Linux file paths.
  • Include Linux-specific prerequisites and troubleshooting steps, such as permissions, package dependencies, and service management.
  • Offer guidance for running the installer script in a Linux environment, or clarify if Linux is unsupported and suggest alternatives.
  • Mention cross-platform compatibility for the appliance and clarify supported operating systems early in the documentation.
  • Add examples for DNS configuration and proxy setup using Linux tools (e.g., /etc/hosts, systemd-resolved, iptables, curl/wget for downloads).
GitHub Create Pull Request
Migrate https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/concepts-assessment-calculation.md ...in/articles/migrate/concepts-assessment-calculation.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Windows Heavy Missing Linux Example
Summary
The documentation page exhibits a Windows bias in several ways. Windows operating systems are listed first and in detail in readiness tables, with Linux relegated to a single row referencing an external list. The guest OS readiness section provides extensive specifics for various Windows versions, but Linux is treated generically. There are no Linux-specific examples, patterns, or troubleshooting guidance; most examples and recommendations are either Windows-centric or omit Linux details. The documentation also lacks parity in describing how to assess Linux VMs, especially regarding version discovery and readiness nuances.
Recommendations
  • Provide Linux-specific examples and troubleshooting steps, especially for common distributions (e.g., Ubuntu, RHEL, SUSE).
  • List Linux operating systems and their readiness/support status in detail, similar to the Windows OS table.
  • Include guidance for discovering Linux kernel versions and handling edge cases (e.g., unsupported distros, custom kernels).
  • Ensure that Linux tools, patterns, and assessment nuances are described alongside Windows equivalents, not just referenced externally.
  • Add explicit instructions for Linux environments in all relevant sections, including appliance deployment, data collection, and performance analysis.
GitHub Create Pull Request
Migrate https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/create-manage-projects.md ...s/blob/main/articles/migrate/create-manage-projects.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates Windows bias by providing command-line examples exclusively in PowerShell, referencing the use of PowerShell as the default shell for Az CLI commands, and omitting equivalent instructions for Linux or macOS environments. The guidance for installing and running Az CLI is specifically stated for PowerShell, with no mention of Bash or other shells. There are no Linux-specific examples, nor is there any mention of cross-platform considerations for command execution.
Recommendations
  • Provide Az CLI command examples for both PowerShell (Windows) and Bash (Linux/macOS), or clarify that commands work in any shell.
  • Include installation instructions for Az CLI on Linux and macOS, not just Windows.
  • Avoid referencing PowerShell as the default shell for Az CLI commands; use neutral language or mention multiple shells.
  • Add notes or sections highlighting cross-platform compatibility for all command-line steps.
  • Where screenshots or instructions reference Windows-specific UI elements, clarify any differences for Linux/macOS users if applicable.
GitHub Create Pull Request
Migrate https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/how-to-set-up-appliance-vmware.md ...ain/articles/migrate/how-to-set-up-appliance-vmware.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 Windows bias in several ways. The alternative to the OVA deployment is exclusively a PowerShell installer script, with no mention of a Linux shell or Bash equivalent. File paths and instructions for installing the VMware VDDK reference only Windows locations (e.g., C:\Program Files\VMware\...), and there are no Linux-specific instructions or examples for deployment, configuration, or troubleshooting. Credential validation and examples prioritize Windows/domain credentials, with Linux credentials mentioned only as an option in a dropdown, and no further details or examples provided. The documentation does not provide parity for Linux administrators who may wish to deploy or manage the appliance on Linux-based servers.
Recommendations
  • Provide a Bash or shell script alternative to the PowerShell installer for Linux environments.
  • Include Linux-specific instructions for installing and configuring the VMware VDDK, including default Linux file paths.
  • Offer explicit examples for Linux credential types, including validation and troubleshooting steps.
  • Clarify whether the appliance can be deployed on Linux-based VMs and, if so, provide step-by-step guidance.
  • Ensure all prerequisites, troubleshooting, and configuration steps have both Windows and Linux variants where applicable.
GitHub Create Pull Request
Migrate https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/migrate-appliance.md ...e-docs/blob/main/articles/migrate/migrate-appliance.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation for the Azure Migrate appliance exhibits a strong Windows bias. All deployment methods, configuration, and management instructions are centered around Windows Server (2019, 2022, 2025) and PowerShell scripts. There are no examples or instructions for deploying or managing the appliance on Linux hosts, nor are Linux-native tools or patterns mentioned. Even in scenarios where Linux servers are discovered, the appliance itself must run on Windows. Verification and upgrade steps rely on Windows tools (CertUtil, Registry Editor, Control Panel), and all screenshots and walkthroughs are Windows-centric.
Recommendations
  • Provide explicit guidance for deploying and managing the appliance on Linux hosts, if supported.
  • Include Linux shell command equivalents for file verification (e.g., sha256sum, md5sum) alongside CertUtil and PowerShell examples.
  • Document upgrade and configuration steps using Linux-native tools (e.g., systemd for service management, configuration files instead of Windows Registry).
  • Clarify OS support for the appliance and, if Windows-only, state this up front and provide rationale.
  • If Linux deployment is not supported, suggest alternatives or workarounds for Linux-centric environments.
  • Ensure that discovery and management of Linux servers is covered with parity to Windows, including troubleshooting and prerequisites.
GitHub Create Pull Request
← Previous Page 13 of 37 Next →