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 51-75 of 918 flagged pages
Migrate Discover, assess, and migrate Amazon Web Services (AWS) EC2 VMs to Azure ...icles/migrate/tutorial-migrate-aws-virtual-machines.md
High Priority View Details →
Scanned: 2026-01-13 00:00
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 key areas. The replication appliance required for migration must be deployed 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 discussed before Linux equivalents, and screenshots and step-by-step instructions focus on Windows environments. While Linux migration steps are included, the central migration workflow is dependent on Windows infrastructure, creating friction for Linux/macOS users.
Recommendations
  • Provide clear guidance or alternatives for deploying the replication appliance on Linux, or explicitly state Windows-only requirements earlier in the documentation.
  • Offer Linux-first or parallel examples for all steps, including screenshots and command-line instructions.
  • Clarify which steps are OS-agnostic and which are Windows-specific, and provide Linux/macOS workarounds where possible.
  • If Windows is a hard requirement for the replication appliance, suggest containerized or cloud-hosted options to reduce friction for Linux users.
  • Add a summary table comparing Windows and Linux migration workflows, highlighting differences and required tools.
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-13 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 heavily focused on Windows environments, specifically Hyper-V on Windows Server. All setup, installation, and command-line instructions are Windows-centric, using .exe installers, Windows file paths, and tools like SetupDiag. There are no Linux/macOS equivalents, nor is there guidance for users running Hyper-V on non-Windows platforms (such as Hyper-V Server Core or potential Linux-based management). Troubleshooting and upgrade steps are also Windows-specific, and Windows terminology and tools are mentioned first and exclusively.
Recommendations
  • Clarify early that the migration process is only supported for Hyper-V running on Windows Server, and explicitly state any platform limitations.
  • If any steps can be performed from Linux/macOS (such as Azure portal operations), provide examples or mention compatibility.
  • If the migration tooling (Azure Site Recovery provider, etc.) is Windows-only, state this clearly and suggest alternatives for Linux-based virtualization (e.g., KVM, Xen) or refer users to VMware/Linux migration guides.
  • Include troubleshooting and post-migration steps for Linux VMs if supported, or clarify that only Windows VMs are covered.
  • Add parity in post-migration best practices, such as Linux-specific security and update management recommendations.
GitHub Create Pull Request
Migrate Agent-based Migration in the Migration and Modernization Tool ...articles/migrate/agent-based-migration-architecture.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Windows-specific tools and patterns (e.g., registry keys, MMC snap-in, Windows folder paths) for managing and optimizing agent-based migration. There are no Linux-specific examples, instructions, or equivalent tooling mentioned for Linux servers, despite the fact that agent-based migration supports both Windows and Linux workloads. Windows terminology and procedures are presented first and exclusively, leaving Linux users without guidance.
Recommendations
  • Provide explicit instructions and examples for installing and managing the Mobility service on Linux servers, including command-line installation steps and relevant file paths.
  • Document Linux-specific configuration options for throttling bandwidth, such as using tc, iptables, or other Linux-native tools, rather than only referencing Windows registry and MMC snap-in.
  • List antivirus exclusion paths for Linux (e.g., /var/lib/ASR, /opt/Microsoft/AzureRecoveryServiceAgent) alongside the Windows paths.
  • Clarify which steps or tools are Windows-only and offer Linux equivalents where possible.
  • Ensure that examples and instructions are presented in a platform-neutral way, or provide parallel guidance for both Windows and Linux environments.
GitHub Create Pull Request
Migrate Azure Migrate Application and Code Assessment for Java Version 7 ...docs/blob/main/articles/migrate/appcat/java-preview.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 Examples Windows Known Issues
Summary
The documentation provides parity between Windows and Linux/macOS in most areas, including download links, installation instructions, and CLI usage examples. However, there is a subtle Windows bias: Windows is often listed first in download tables and examples, and known issues sections frequently highlight Windows-specific problems. Additionally, script examples and folder structures explicitly differentiate Windows (.exe, .bat) and Linux/macOS, but Windows instructions and troubleshooting are sometimes more detailed.
Recommendations
  • Alternate the order of OS examples and download links so Linux/macOS are not always listed after Windows.
  • Ensure Linux/macOS troubleshooting and known issues are equally detailed and prominent as Windows.
  • Where possible, use generic CLI instructions or highlight cross-platform usage before OS-specific details.
  • Add more Linux/macOS-specific tips and troubleshooting, especially in the known issues section.
  • Consider grouping OS instructions together, or presenting Linux/macOS first in some sections to balance representation.
GitHub Create Pull Request
Migrate Overview of Azure Migrate Assessment Report ...e-docs/blob/main/articles/migrate/assessment-report.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 demonstrates a Windows bias by referencing Windows Server as the primary example of conditional readiness, mentioning Hyper-V (a Windows-centric virtualization platform) before VMware, and omitting explicit Linux server or tool examples. There are no Linux-specific assessment scenarios, readiness issues, or remediation guidance provided, and no mention of Linux-native tools or considerations.
Recommendations
  • Include examples of Linux server readiness issues (e.g., unsupported kernel versions, disk formats, or specific Linux distributions).
  • Provide remediation guidance for common Linux migration blockers, similar to the Windows Server example.
  • Mention Linux-native virtualization platforms (such as KVM or Xen) alongside Hyper-V and VMware.
  • Add explicit Linux command-line or configuration examples where relevant, not just Windows-centric scenarios.
  • Ensure that references to tools, migration steps, and troubleshooting cover both Windows and Linux environments equally.
GitHub Create Pull Request
Migrate Assessment Best Practices in Azure Migrate Discovery and Assessment Tool ...lob/main/articles/migrate/best-practices-assessment.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 demonstrates a Windows bias by focusing assessment examples and migration scenarios on Windows-centric technologies such as IIS, ASP.NET, and SQL Server, with no mention of Linux workloads, tools, or migration patterns. Windows environments (Hyper-V, IIS) are referenced before or instead of Linux equivalents, and there are no examples or guidance for assessing or migrating Linux servers or applications.
Recommendations
  • Include explicit examples and guidance for assessing and migrating Linux servers (e.g., Ubuntu, CentOS) to Azure.
  • Add Linux-specific workloads (e.g., Apache, Nginx, MySQL, PostgreSQL) to the assessment types and examples.
  • Provide parity in migration tool recommendations for Linux VMs (e.g., Azure Migrate agent for Linux, rsync, SCP, etc.).
  • Mention Linux discovery and assessment patterns (e.g., SSH-based discovery, Linux performance counters) alongside Windows/Hyper-V.
  • Ensure documentation language and examples do not assume Windows-first environments; alternate or parallel Linux scenarios should be presented.
GitHub Create Pull Request
Migrate Security Best Practices for Deploying an Appliance .../blob/main/articles/migrate/best-practices-security.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 Missing Linux Example 🔧 Windows Tools
Summary
The documentation demonstrates a Windows bias by focusing almost exclusively on Windows Server for appliance deployment, recommending PowerShell scripts for installation, and referencing Windows-specific security tools and baselines. Linux is only mentioned in the context of network port access, with no guidance on deploying or hardening the appliance on Linux systems. There are no Linux installation or security hardening examples, and Windows tools (such as Group Policy and the Security Compliance Toolkit) are referenced without Linux equivalents.
Recommendations
  • Provide explicit instructions and examples for deploying the Azure Migrate appliance on supported Linux distributions, if applicable.
  • Include Linux-based installation methods (e.g., shell scripts, package managers) alongside PowerShell and Windows templates.
  • Reference Linux security hardening guides, such as CIS Benchmarks, and provide steps for applying them to the appliance.
  • Mention Linux credential storage and encryption mechanisms, such as libsecret or Gnome Keyring, if supported.
  • Ensure parity in vulnerability protection advice by including patching recommendations for Linux OS layers.
  • List Linux tools and patterns (e.g., SELinux, AppArmor, systemd services) where relevant, and provide links to official documentation.
GitHub Create Pull Request
Migrate Azure Migrate Appliance FAQ ...ob/main/articles/migrate/common-questions-appliance.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 Tools Windows First Missing Linux Example
Summary
The documentation for the Azure Migrate appliance demonstrates a strong Windows bias. Deployment and management instructions are centered around PowerShell scripts and Windows tools (e.g., certificate manager, group policy editor, Windows Update). Troubleshooting steps and examples are exclusively Windows-based, with screenshots and instructions referencing Windows UI and utilities. There are no Linux-specific deployment, management, or troubleshooting examples, nor are Linux equivalents mentioned for key operations. The documentation assumes the appliance is running on Windows, even though Linux is referenced as a supported credential type.
Recommendations
  • Provide Linux-specific deployment instructions, including shell script or CLI alternatives to PowerShell for appliance setup and management.
  • Include troubleshooting steps for certificate validation and MSI installation on Linux-based appliances, referencing relevant Linux tools (e.g., openssl, update-ca-certificates).
  • Add examples and screenshots for Linux environments where applicable (e.g., managing certificates, checking agent health, updating the OS).
  • Clearly state OS requirements and support for the appliance, and if Linux is supported, ensure parity in documentation for both Windows and Linux.
  • Mention Linux equivalents for Windows tools (e.g., group policy editor, certificate manager) or clarify if certain steps are Windows-only.
  • Ensure that credential management and SQL Server discovery instructions include Linux scenarios and authentication methods.
GitHub Create Pull Request
Migrate Questions about Wave Planning in Azure Migrate ...ain/articles/migrate/common-questions-wave-planning.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 Missing Linux Example 🔧 Windows Tools
Summary
The documentation page on Wave Planning in Azure Migrate demonstrates a Windows bias by referencing PowerShell and Windows-centric tools (Azure CLI, PowerShell, Azure portal) for exporting and querying data, without providing Linux-specific examples or mentioning Linux-native tools. The order of tool presentation also places Windows tools (PowerShell) before alternatives, and there are no explicit Linux shell (bash) or cross-platform command examples.
Recommendations
  • Include Linux shell (bash) examples alongside PowerShell for common operations, such as querying Azure Resource Graph.
  • Mention cross-platform tools (e.g., az CLI) before platform-specific ones like PowerShell.
  • Provide explicit instructions for Linux users, such as using curl for REST APIs or jq for JSON parsing.
  • Clarify that Azure CLI and REST APIs are cross-platform and can be used on Linux, macOS, and Windows.
  • Add screenshots or walkthroughs from Linux environments where applicable.
GitHub Create Pull Request
Migrate Azure VM assessments in Azure Migrate ...in/articles/migrate/concepts-assessment-calculation.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 Heavy Missing Linux Example
Summary
The documentation demonstrates a Windows bias by listing Windows operating systems first and in detail in readiness tables, providing extensive guidance and remediation for Windows versions, and referencing Windows-specific scenarios (e.g., UEFI boot support for Windows Server versions). Linux is mentioned only as a single row with a link to endorsed distributions, without examples or detailed guidance. There are no Linux-specific migration scenarios, troubleshooting steps, or parity in example coverage.
Recommendations
  • Provide detailed Linux operating system readiness guidance, including common migration issues, supported kernel versions, and troubleshooting steps.
  • Include Linux-specific examples and scenarios in assessment tables, such as handling different Linux distributions, filesystems, and boot types.
  • Offer parity in remediation guidance for Linux servers, similar to the detailed steps given for Windows Server versions.
  • Add links to Linux migration best practices and documentation, not just a list of endorsed distros.
  • Ensure that examples and instructions for application discovery and performance data collection include Linux-specific steps and tools (e.g., SSH, Linux agent installation), not just vCenter or Windows-centric approaches.
GitHub Create Pull Request
Migrate Azure SQL assessments in Azure Migrate Discovery and assessment tool ...s/migrate/concepts-azure-sql-assessment-calculation.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 Missing Linux Example Powershell Heavy
Summary
The documentation page exhibits a Windows bias in several ways: Windows environments (VMware, Hyper-V, IIS) are mentioned first and most prominently; migration scenarios and best practices are linked to Windows-specific resources; high availability and disaster recovery guidance focuses on Windows Server Failover Clusters and Cloud Witness, with no mention of Linux clustering or witness options; and example links and references (such as performance guidelines and cluster configuration) are exclusively for Windows, with no Linux equivalents or examples provided. There are no Linux-specific migration scenarios, tools, or guidance, and Linux SQL Server deployments are not addressed.
Recommendations
  • Include explicit examples and guidance for assessing and migrating SQL Server instances running on Linux (e.g., Ubuntu, RHEL, SLES).
  • Add links to Azure SQL performance guidelines and best practices for Linux-based SQL Server deployments.
  • Provide parity in high availability and disaster recovery guidance, including Linux clustering solutions (e.g., Pacemaker) and witness options.
  • Mention and document Linux-based migration tools and patterns alongside Windows tools (e.g., shell scripts, Linux agents, Linux-native backup/restore).
  • Ensure that references to PowerShell are balanced with Bash or shell script examples for Linux environments.
  • Clarify which features and recommendations apply to both Windows and Linux, and highlight any differences.
GitHub Create Pull Request
Migrate Business case in Azure Migrate ...articles/migrate/concepts-business-case-calculation.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 for Azure Migrate Business Case exhibits a Windows bias. Windows Server and SQL Server licensing, ESU, and management tooling (System Center) are discussed in detail, while Linux is only briefly mentioned in cost tables and not elaborated upon. There are no Linux-specific examples, cost breakdowns, or management tool discussions, and Windows-related patterns and tools (e.g., System Center, ESU, AHUB) are prioritized and described first and in greater detail.
Recommendations
  • Add explicit Linux server examples and cost breakdowns, including licensing, support, and management costs.
  • Discuss Linux management and monitoring tools (e.g., Azure Monitor for Linux, open-source alternatives) alongside System Center.
  • Provide parity in describing Extended Security Update (ESU) or equivalent lifecycle/support for Linux distributions.
  • Include Linux-specific migration strategies and recommendations, such as migration to Azure Linux VMs, Azure Container Instances, or AKS with Linux nodes.
  • Ensure Linux is mentioned equally in all tables and narrative sections, not just as a footnote or in aggregate.
  • Add examples and formulas for Linux licensing and support costs, including common enterprise distributions (e.g., Red Hat, SUSE, Ubuntu).
GitHub Create Pull Request
Migrate Azure App Service assessments in Azure Migrate Discovery and assessment tool ...grate/concepts-azure-webapps-assessment-calculation.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 on ASP.NET web apps running on IIS (a Windows-only technology) and referencing Windows-centric migration scenarios and SKUs. There are no explicit examples or guidance for Linux-based web apps (such as those running on Apache or Nginx), nor is there mention of Linux-specific migration considerations or tooling. The App Service pricing link points to Windows plans, and the assessment process is described primarily for Windows environments, with no parity for Linux scenarios.
Recommendations
  • Include explicit examples and guidance for assessing Linux-based web apps (e.g., Java apps on Apache/Nginx, PHP, Node.js, Python).
  • Reference both Windows and Linux App Service plans and pricing, and clarify differences in migration and assessment.
  • Mention Linux-compatible migration tools and patterns alongside Windows tools, ensuring equal visibility.
  • Provide parity in assessment steps and troubleshooting for Linux environments, including discovery and compatibility checks.
  • Add links to Linux-focused documentation and best practices for App Service migration.
GitHub Create Pull Request
Migrate Support matrix for web apps migration ...ob/main/articles/migrate/concepts-migration-webapps.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 heavily focused on Windows environments, specifically IIS servers and PowerShell, with explicit statements that Linux servers are not supported and no Linux migration examples or tools mentioned. All requirements and instructions are tailored to Windows, and there is no guidance for users with Linux-based web apps.
Recommendations
  • Clearly state future plans or alternatives for Linux support in the migration process.
  • Provide equivalent migration guidance or tooling for Linux-based web apps, if available.
  • Include examples or references for migrating web apps from Linux environments, or link to relevant resources.
  • Avoid exclusive reliance on Windows tools (e.g., PowerShell) by mentioning cross-platform alternatives where possible.
  • Add a section addressing Linux users, outlining current limitations and possible workarounds or migration paths.
GitHub Create Pull Request
Migrate Agentless Replication of VMware Virtual Machines ...rticles/migrate/concepts-vmware-agentless-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 Windows First Missing Linux Example
Summary
The documentation page exhibits Windows bias in several areas: bandwidth throttling is demonstrated exclusively using Windows PowerShell (`New-NetQosPolicy`) and references a Windows service executable (`GatewayWindowsService.exe`). Configuration examples and file paths (e.g., `C:\ProgramData\Microsoft Azure\Config`) are Windows-centric, with no mention of Linux equivalents or alternative methods for Linux-based appliances. There are no Linux shell, configuration, or tool examples provided, and Windows tools and patterns are presented first and exclusively.
Recommendations
  • Provide Linux-based examples for bandwidth throttling, such as using `tc`, `iptables`, or other Linux-native QoS tools.
  • Include instructions and file paths for configuring blackout windows on Linux appliances (e.g., `/etc/azure-migrate/config` or similar).
  • Clarify whether the Azure Migrate appliance can run on Linux, and if so, provide parity in documentation for both platforms.
  • Offer sample scripts and service management instructions for Linux (e.g., using `systemctl` to restart services).
  • Ensure all configuration and operational guidance is available for both Windows and Linux environments, or explicitly state platform limitations.
GitHub Create Pull Request
Migrate Discover and assess using Azure Private Link ...migrate/discover-and-assess-using-private-endpoints.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 Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exhibits a strong Windows bias. The only example provided for running the Azure Migrate installer script uses PowerShell on Windows, with explicit instructions to launch PowerShell with administrative privileges. There are no Linux or cross-platform shell examples, nor is there mention of Linux-based deployment or tools. The instructions for installing third-party dependencies (VDDK) reference Windows file paths exclusively. The troubleshooting and log file locations are also given in Windows format. Overall, the documentation assumes the appliance host is a Windows server and does not address Linux alternatives.
Recommendations
  • Provide equivalent instructions and examples for Linux hosts, including shell commands (e.g., bash) for running the installer script.
  • Clarify whether the installer script is cross-platform and, if so, document the steps for Linux deployment.
  • Include Linux file paths and log locations where applicable.
  • Mention prerequisites and troubleshooting steps for Linux environments.
  • Add screenshots or terminal output examples for Linux where relevant.
  • Explicitly state OS requirements and supported platforms for the Azure Migrate appliance.
GitHub Create Pull Request
Migrate Build a migration plan with Azure Migrate ...b/main/articles/migrate/concepts-migration-planning.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 prioritizing Windows-specific migration scenarios, tools, and features. Windows Server is mentioned explicitly and repeatedly (e.g., end-of-support, OS upgrade), with detailed guidance and features (such as in-place OS upgrade using Custom Script Extension for Windows). There is little to no mention of Linux-specific migration considerations, tools, or examples, and Linux is only referenced in passing (e.g., Azure Hybrid Benefit for Linux subscriptions) without substantive guidance or parity in migration features.
Recommendations
  • Add explicit examples and guidance for migrating Linux servers, including common Linux distributions and their unique migration challenges.
  • Highlight Linux-specific tools, features, and extensions available in Azure Migrate, such as support for in-place upgrades or recommended migration paths for Linux workloads.
  • Include parity for OS upgrade scenarios for Linux (if available), or clarify limitations and alternative approaches for Linux server upgrades during migration.
  • Provide sample assessment and migration reports/screenshots for Linux workloads to match the Windows examples.
  • Ensure that references to end-of-support operating systems include major Linux distributions (e.g., CentOS, Ubuntu LTS, RHEL) and their migration implications.
  • Balance the documentation by mentioning both Windows and Linux migration blockers, remediation guidance, and compatibility considerations.
GitHub Create Pull Request
Migrate Create and manage projects ...s/blob/main/articles/migrate/create-manage-projects.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 First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias primarily through its use of PowerShell for command-line examples, explicit instructions to open PowerShell as Administrator, and the absence of Linux-specific shell or tool examples. All CLI instructions are presented in the context of PowerShell, with no mention of Bash or Linux terminal usage. There is no guidance for Linux users on how to perform equivalent actions, nor are Linux-specific patterns or tools referenced.
Recommendations
  • Provide equivalent command-line instructions for Linux users, using Bash syntax and conventions.
  • Explicitly mention that Az CLI can be used on Linux and macOS, and provide examples for those platforms.
  • Avoid language that assumes the user is on Windows (e.g., 'open PowerShell as Administrator'); instead, use platform-neutral phrasing such as 'open your terminal'.
  • Include screenshots or instructions for Linux environments where relevant.
  • Add a section or note clarifying cross-platform support for all tools and commands referenced.
GitHub Create Pull Request
Migrate Tutorial to assess web apps for migration ...lob/main/articles/migrate/create-web-app-assessment.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 exhibits Windows bias by focusing on ASP.NET web apps and Windows-specific migration scenarios, mentioning Windows Server licensing and hybrid benefits, and referencing Windows Dockerfile optimization in the 'Next steps'. There are no explicit Linux or open-source stack examples (e.g., Node.js, PHP, Python web apps), nor are Linux migration patterns or tools discussed. The only non-Windows example is Java on Tomcat, but it is treated similarly to ASP.NET and lacks broader Linux context.
Recommendations
  • Add explicit examples and guidance for migrating Linux-based web apps (e.g., Node.js, PHP, Python, Ruby) alongside ASP.NET and Java.
  • Include Linux-specific migration considerations, such as differences in containerization, file system, and security settings.
  • Reference Linux Dockerfile optimization and best practices in the 'Next steps', not just Windows Dockerfiles.
  • Discuss licensing and cost estimation for Linux workloads, not just Windows Server and hybrid benefits.
  • Ensure screenshots and UI walkthroughs are not exclusively tailored to Windows-centric environments.
GitHub Create Pull Request
Migrate Discovered Metadata ...docs/blob/main/articles/migrate/discovered-metadata.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 demonstrates a Windows bias in several ways: Windows examples, tools, and PowerShell cmdlets are consistently presented first and in greater detail than Linux equivalents. Windows-specific technologies (WMI, PowerShell, Registry, Windows Features) are described with full command and property breakdowns, while Linux coverage is often limited to command-line snippets without deeper explanation or parity in tooling. Some sections (e.g., ASP.NET, Java, Spring Boot web app data) focus exclusively on Windows servers, omitting Linux scenarios. Storage metadata and application inventory sections provide more comprehensive Windows tooling and examples, with Linux relegated to command lists. Overall, the documentation prioritizes Windows approaches and tools, with Linux support presented as secondary.
Recommendations
  • Present Linux and Windows examples side-by-side in all sections, ensuring equal detail and clarity.
  • Include Linux-specific tooling and configuration details (e.g., systemd, SELinux, package managers) where Windows tools (PowerShell, Registry) are highlighted.
  • Expand Linux application and web app discovery sections to cover common Linux stacks (e.g., Apache, Nginx, Tomcat on Linux) and provide equivalent metadata breakdowns.
  • In storage metadata, offer Linux examples for NFS/SMB/iSCSI configuration and discovery, matching the depth of Windows PowerShell cmdlets.
  • Avoid presenting Windows examples or tools first by default; alternate ordering or group by platform.
  • Add explicit notes or tables clarifying feature parity and limitations for Linux vs. Windows, especially in areas where only Windows is supported.
  • Where Windows-only features are described (e.g., Windows Feature discovery), clarify Linux alternatives or state lack of support.
GitHub Create Pull Request
Migrate Create an Azure SQL assessment ...articles/migrate/how-to-create-azure-sql-assessment.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 through its exclusive mention of Windows-specific tools and patterns, such as Windows Server Failover Clusters and Cloud Witness, without referencing Linux equivalents. The linked best practices and configuration guides are for Windows, and there are no examples or guidance for Linux-based SQL deployments. Linux licensing (RHEL/SLES) is mentioned only as an aside in the context of Azure Hybrid Benefit, and there are no instructions or examples for Linux SQL Server migration scenarios.
Recommendations
  • Include examples and guidance for assessing and migrating SQL Server instances running on Linux (e.g., Ubuntu, RHEL, SLES).
  • Reference Linux-specific high availability and disaster recovery options, such as Pacemaker clusters, and provide links to relevant Azure documentation.
  • Add parity in documentation for storage, VM sizing, and performance guidelines for Linux-based SQL Server on Azure VMs.
  • Ensure that migration strategies and readiness reports explicitly address Linux SQL Server scenarios, including licensing and support status.
  • Provide links to Linux best practices for SQL Server on Azure, similar to those given for Windows.
GitHub Create Pull Request
Migrate Set up Agentless Dependency Analysis in Azure Migrate ...https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/how-to-create-group-machine-dependencies-agentless.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 several forms of Windows bias. PowerShell is the only command-line interface shown for managing agentless dependency analysis, with no Linux shell or cross-platform CLI alternatives. Windows credentials and permissions are described before Linux equivalents, and Windows-specific tools (PowerShell, Power BI) are referenced exclusively. There are no Linux shell (bash/ssh) examples for managing dependencies, nor are Linux-native visualization or export tools mentioned.
Recommendations
  • Provide equivalent Linux shell (bash/ssh) command examples for managing dependencies, such as using Azure CLI or REST API from Linux.
  • Include instructions for installing and using the AzMig.Dependencies module or Azure CLI on Linux systems.
  • Mention and demonstrate Linux-native visualization options (e.g., using open-source tools or direct CSV manipulation in Linux environments) alongside Power BI.
  • Present credential and permission requirements for Linux servers before or alongside Windows, ensuring parity in explanation and emphasis.
  • Clarify that PowerShell Core is cross-platform, and provide explicit instructions for Linux/macOS users where relevant.
  • Add troubleshooting and usage notes specific to Linux environments (e.g., handling sudo/NOPASSWD, file permissions, SELinux/AppArmor considerations).
GitHub Create Pull Request
Migrate Set up agent-based dependency analysis in Azure Migrate ...es/migrate/how-to-create-group-machine-dependencies.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 exhibits Windows bias in several ways. Installation instructions for agents and tools are presented with Windows steps first, including GUI-based and Windows-specific automation options (Configuration Manager, Intigua, Windows script links). Linux instructions are brief, command-line only, and lack parity in automation guidance. References to supported operating systems and installation methods are more detailed for Windows. No Linux-specific troubleshooting, automation, or tool integration examples are provided.
Recommendations
  • Present Linux and Windows instructions in parallel, or alternate which comes first.
  • Expand Linux installation guidance to include automation options (e.g., Ansible, shell scripts), troubleshooting, and supported distributions.
  • Provide equivalent links or scripts for Linux agent installation and management.
  • Include Linux-specific examples for querying, monitoring, and integrating with Azure Migrate.
  • Mention Linux tools and patterns (e.g., systemd, package managers) where relevant.
  • Ensure that screenshots and step-by-step instructions are balanced between Windows and Linux environments.
GitHub Create Pull Request
Migrate Discover software inventory on on-premises servers with Azure Migrate .../main/articles/migrate/how-to-discover-applications.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 Missing Linux Example Powershell Heavy
Summary
The documentation page demonstrates a Windows bias in several ways: Windows credentials and tools are mentioned first or exclusively in key sections, such as SQL Server and File Server discovery. Windows-specific roles (e.g., File Server, IIS, SCCM) are described in detail, while equivalent Linux examples, tools, or patterns are missing or only briefly referenced. The instructions and examples tend to prioritize Windows environments, with Linux support often described as secondary or in passing.
Recommendations
  • Provide explicit Linux examples and instructions alongside Windows ones, especially for credential provisioning, role discovery, and permissions.
  • Include Linux equivalents for Windows-specific tools and roles (e.g., Samba for file servers, Apache/Nginx for web servers, Linux patch management tools).
  • Ensure that Linux authentication and configuration steps are described with equal detail, including sample commands and configuration file references.
  • List Linux and Windows options together, or alternate their order, to avoid 'Windows first' presentation.
  • Add troubleshooting and permissions guidance for Linux environments, matching the depth given to Windows/SQL Server.
  • Clarify support for Linux file servers and web apps, and expand on limitations or future roadmap if parity is not yet achieved.
GitHub Create Pull Request
Migrate Discover SQL Server instances in an existing Azure Migrate project ...ticles/migrate/how-to-discover-sql-existing-project.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 demonstrates a Windows bias by primarily referencing Windows OS credentials, PowerShell requirements, and Windows-specific tools (such as Appliance Configuration Manager and credential formats). There is no mention of Linux-based discovery, Linux authentication methods, or examples for non-Windows environments. The prerequisites and instructions focus on Windows-centric patterns, with Linux parity missing throughout.
Recommendations
  • Include explicit instructions and examples for discovering SQL Server instances on Linux servers, covering authentication and credential requirements for Linux environments.
  • Mention Linux equivalents for PowerShell (such as Bash scripts or CLI commands) and clarify if the Azure Migrate appliance supports Linux-based discovery.
  • Provide guidance on required permissions and credential formats for Linux systems, including sudo or service accounts.
  • Add troubleshooting steps and screenshots for Linux-based appliances and environments.
  • Clarify whether the appliance can discover SQL Server instances running on Linux, and if so, detail any differences in process or requirements.
GitHub Create Pull Request
← Previous Page 3 of 37 Next →