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 276-300 of 918 flagged pages
Migrate https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/migrate-support-matrix-hyper-v.md ...ain/articles/migrate/migrate-support-matrix-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 demonstrates a strong Windows bias. Windows and PowerShell tools and patterns are mentioned first and most prominently throughout, with requirements and examples tailored to Windows environments. PowerShell remoting and Windows-specific permissions/groups are emphasized, while Linux equivalents are only briefly mentioned or relegated to secondary status. SQL Server and ASP.NET web app discovery are supported only for Windows servers, with Linux support explicitly missing or limited. Example scripts and configuration steps are provided only for Windows authentication and SQL Server, with no Linux-specific examples or guidance. Linux support is often described as 'not supported' or only in passing, and Linux requirements are less detailed.
Recommendations
  • Provide Linux-first or Linux-parity examples and instructions alongside Windows ones, including sample scripts for Linux authentication and configuration.
  • Expand documentation of Linux server requirements, including supported distributions, versions, and integration service equivalents.
  • Offer detailed guidance for Linux-based SQL Server and web app discovery, or clearly state roadmap for Linux support.
  • Include Linux-specific troubleshooting, permissions, and connectivity instructions (e.g., SSH key setup, sudo configuration).
  • Balance the order of presentation so Linux and Windows requirements are described together, not with Windows always first.
  • Add explicit notes on feature parity and limitations for Linux users, and link to alternative tools or migration paths where Azure Migrate does not support Linux workloads.
GitHub Create Pull Request
Migrate https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/migrate-support-matrix-physical.md ...in/articles/migrate/migrate-support-matrix-physical.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 demonstrates a Windows bias in several ways: Windows tools and technologies (such as PowerShell, WinRM, WMI) are mentioned first and in greater detail than their Linux equivalents. PowerShell is the only script-based setup method described for the Azure Migrate appliance, with no Linux shell script alternative provided. SQL Server and IIS web app discovery are supported only on Windows, with Linux support explicitly missing or limited. Example scripts and configuration steps are provided only for Windows authentication and SQL Server, with no equivalent Linux database or web server examples. Linux instructions are generally brief, refer to external links, or are less detailed.
Recommendations
  • Provide Linux shell script examples for appliance setup, similar to the PowerShell script provided for Windows.
  • Include detailed instructions and examples for Linux server configuration, such as enabling SSH, required user permissions, and troubleshooting steps.
  • Add parity for SQL Server discovery on Linux, or explicitly document the roadmap and alternatives for Linux database assessment.
  • Offer examples for discovering and assessing Linux web servers (e.g., Apache, Nginx) and web apps, not just Tomcat.
  • Ensure that Linux commands and requirements are listed as prominently and in as much detail as Windows prerequisites.
  • Where features are Windows-only, clearly state the limitation and suggest alternative approaches for Linux environments.
GitHub Create Pull Request
Migrate https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/migrate-support-matrix-physical-migration.md ...s/migrate/migrate-support-matrix-physical-migration.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 exhibits Windows bias in several areas: Windows-specific tools and patterns (such as RDP and Windows Firewall) are described in greater detail and appear before Linux equivalents. The replication appliance is described as being set up with Windows Server 2016 by default, with no mention of Linux-based alternatives. Instructions for post-migration connectivity provide more detailed steps for Windows (RDP, firewall settings) than for Linux (SSH), and there are no Linux command examples or references to Linux-specific migration tooling. Some features (Multipath IO) are noted as supported only for Windows servers, while Linux support is not discussed.
Recommendations
  • Provide equal detail and step-by-step instructions for Linux post-migration connectivity, including example SSH configuration commands and firewall settings (e.g., using iptables, firewalld, or ufw).
  • Mention or provide guidance for setting up the replication appliance on Linux-based systems, if supported, or clarify if only Windows is supported.
  • Include Linux-specific troubleshooting steps and migration considerations, such as SELinux/AppArmor, systemd service management, and common Linux disk/filesystem issues.
  • List Linux tools and patterns (e.g., SSH, rsync, cron jobs, system logs) alongside Windows tools, and avoid presenting Windows tools first unless there is a technical reason.
  • If features are supported only on Windows (e.g., Multipath IO), explicitly state Linux support status and provide alternatives or workarounds for Linux users.
GitHub Create Pull Request
Migrate https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/migrate-support-matrix-vmware.md ...main/articles/migrate/migrate-support-matrix-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 Missing Linux Example Powershell Heavy 🔧 Windows Tools
Summary
The documentation exhibits several forms of Windows bias. Windows-specific tools and patterns (such as PowerShell and WMI) are mentioned more frequently and in greater detail than their Linux equivalents. Windows requirements and examples are often listed before Linux ones, and some features (such as SQL Server and IIS web app discovery) are supported only on Windows or have much more detailed instructions for Windows. Linux support is present but less emphasized, with fewer examples, less detail, and some features not supported at all.
Recommendations
  • Provide Linux-specific examples and scripts for tasks such as credential provisioning, permissions, and discovery, similar to the detailed Windows/PowerShell instructions.
  • Ensure Linux requirements and supported distributions are listed with equal prominence and detail as Windows versions.
  • Where features are not supported on Linux (e.g., SQL Server discovery, IIS web app discovery), clearly state limitations and provide guidance or alternatives for Linux users.
  • Include Linux command-line tools (e.g., Bash, SSH, ss/netstat) in examples and instructions, and avoid assuming Windows tools (PowerShell, WMI) are always available.
  • When listing requirements or supported platforms, alternate the order or present Windows and Linux together to avoid implicit prioritization.
  • Expand documentation for Linux-specific scenarios, such as dependency analysis, credential management, and troubleshooting, to match the depth provided for Windows.
GitHub Create Pull Request
Migrate https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/migrate-virtual-machine-extension-reference.md ...migrate/migrate-virtual-machine-extension-reference.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 displays a moderate Windows bias. In several sections, Windows examples, commands, and tools (such as PowerShell and Windows-specific paths) are presented before their Linux equivalents. PowerShell is used for both Windows and Linux installation examples, even though PowerShell is not the default or most common automation tool on Linux. In status and health checks, only the Windows extension name is shown in CLI examples, and update/removal commands reference only the Windows extension. Troubleshooting and log locations are provided for both OSes, but some CLI and management examples omit Linux-specific details.
Recommendations
  • Ensure all CLI examples and management commands are provided for both Windows and Linux extensions, not just Windows.
  • Present Linux examples and instructions alongside or before Windows examples in each section to avoid 'windows_first' ordering.
  • Use Linux-native automation tools (e.g., Bash, shell scripts) for Linux examples rather than PowerShell.
  • Explicitly mention and show Linux extension names in update and removal commands.
  • Provide parity in troubleshooting steps, including Linux-specific error messages and resolutions.
  • Review all references to tools and patterns to ensure Linux equivalents are included and not overshadowed by Windows-centric approaches.
GitHub Create Pull Request
Migrate https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/onboard-to-azure-arc-with-azure-migrate.md ...les/migrate/onboard-to-azure-arc-with-azure-migrate.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-specific tools and commands (WinRM, PowerShell) are mentioned first and in greater detail, with explicit instructions and command examples (e.g., 'winrm qc'). Linux instructions are present but less detailed, often limited to port numbers (SSH 22) without equivalent command-line examples or troubleshooting depth. Windows authentication and administrative patterns (Local Administrators group, WinRM TrustedHosts) are emphasized, while Linux equivalents (root, SSH key-based authentication) are mentioned but not elaborated. Troubleshooting steps and error codes frequently reference Windows-specific mechanisms and error codes, with Linux errors addressed in less detail.
Recommendations
  • Provide Linux-specific command examples (e.g., how to enable SSH, configure firewall rules, validate root access) alongside Windows instructions.
  • Expand troubleshooting steps for Linux, including common SSH errors, permission issues, and log locations.
  • Mention Linux tools and patterns (e.g., sudo, systemctl, SSH config) with the same prominence as Windows tools.
  • Ensure Linux instructions are presented with equal detail and order as Windows instructions, not as secondary notes.
  • Include parity in authentication methods, such as examples for SSH key setup and management on Linux.
  • Reference Linux administrative groups (e.g., wheel, sudoers) when discussing required permissions.
GitHub Create Pull Request
Migrate https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/prepare-for-migration.md ...cs/blob/main/articles/migrate/prepare-for-migration.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 shows a moderate Windows bias. Windows-specific instructions and examples (such as configuring SAN policy using diskpart, enabling RDP via PowerShell, and Windows Firewall configuration) are detailed and appear before Linux equivalents. Windows tools and patterns (e.g., diskpart, RDP, Windows Firewall) are mentioned explicitly, while Linux instructions are more generic and lack detailed command-line examples. Linux preparation steps are summarized but do not provide concrete commands or troubleshooting guidance comparable to Windows. In several sections, Windows procedures are described first or in greater detail than Linux ones.
Recommendations
  • Provide Linux command-line examples for key steps (e.g., updating fstab, enabling SSH, modifying firewall rules with iptables/firewalld/ufw).
  • Include troubleshooting guidance for Linux connectivity issues similar to the Windows RDP and firewall sections.
  • Balance the order of presentation so that Linux and Windows instructions are given equal prominence, or alternate which is presented first.
  • Mention Linux-specific tools and patterns (e.g., systemctl, journalctl, SSH configuration files) alongside Windows tools.
  • Expand the Linux preparation section to match the detail of the Windows section, including step-by-step instructions for common distributions.
GitHub Create Pull Request
Migrate https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/prepare-for-agentless-migration.md ...in/articles/migrate/prepare-for-agentless-migration.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 demonstrates a Windows bias by consistently presenting Windows procedures and examples before Linux equivalents, providing detailed PowerShell and command prompt instructions for Windows but omitting similarly detailed Linux command-line examples, and referencing Windows-specific tools (e.g., diskpart, SYSTEM registry hive, PowerShell) without offering Linux alternatives or parity in example depth. Linux instructions are more generic and lack step-by-step command examples for manual preparation, especially for tasks like DHCP configuration and agent verification.
Recommendations
  • Present Linux and Windows instructions in parallel sections, or alternate which OS is described first to avoid implicit prioritization.
  • Provide detailed Linux command-line examples for manual steps, such as configuring DHCP, verifying agent installation, and other system changes, similar to the PowerShell and diskpart examples given for Windows.
  • Include Linux-specific troubleshooting steps and screenshots where Windows screenshots are provided.
  • Reference Linux tools and utilities (e.g., systemctl, nmcli, ifconfig/ip, journalctl) when describing configuration and verification steps.
  • Ensure that all manual preparation steps for Windows have a direct Linux equivalent described with equal detail and clarity.
  • Add links to Linux documentation and community resources alongside Windows references.
GitHub Create Pull Request
Migrate https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/quickstart-create-project.md ...lob/main/articles/migrate/quickstart-create-project.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 a bias toward Windows environments by providing command-line instructions specifically for PowerShell, referencing execution 'as Administrator', and omitting equivalent Linux/macOS shell examples. The Az CLI installation and usage steps are described only in the context of PowerShell, with no mention of Bash or other shells. This may hinder Linux users from following the quickstart effectively.
Recommendations
  • Provide Az CLI installation and usage instructions for Linux and macOS, including Bash shell examples.
  • When referencing command execution, avoid specifying 'PowerShell' or 'as Administrator' unless necessary, and include equivalent steps for Linux (e.g., using sudo).
  • Add explicit notes or sections for cross-platform usage, clarifying that Az CLI works on Windows, Linux, and macOS, and link to platform-specific installation guides.
  • Include example commands for both PowerShell and Bash where CLI usage is demonstrated.
  • Review screenshots and UI references to ensure they are not Windows-specific, or add notes if UI differs on other platforms.
GitHub Create Pull Request
Migrate https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/resources-faq.md ...azure-docs/blob/main/articles/migrate/resources-faq.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 for Azure Migrate FAQ demonstrates a Windows bias by referencing Windows-specific tools (MAP Toolkit), prioritizing Windows migration scenarios, and omitting Linux-specific migration examples or tools. The discussion of assessment and planning tools focuses on Windows environments, and there are no explicit Linux migration examples or mentions of Linux-specific issues, patterns, or tools. Scripting mentions PowerShell before Bash, and overall, the documentation assumes familiarity with Windows-centric migration approaches.
Recommendations
  • Include Linux migration scenarios and examples, such as migrating Linux VMs, applications, and workloads.
  • Reference Linux-specific tools or patterns (e.g., Linux Assessment tools, open-source migration utilities) alongside Windows tools like MAP Toolkit.
  • Provide Bash and Python scripting examples before or alongside PowerShell examples to ensure parity.
  • Explicitly mention support for Linux distributions and any unique considerations for Linux migrations.
  • Add FAQs addressing common Linux migration challenges and solutions.
GitHub Create Pull Request
Migrate https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/scale-physical-assessment.md ...lob/main/articles/migrate/scale-physical-assessment.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 demonstrates a Windows bias by exclusively referencing the Azure Migrate appliance as being deployed on a Windows server, with no mention of Linux support or alternatives. There are no Linux-specific instructions, examples, or tools provided for assessment or appliance deployment, and Windows is the only platform discussed for the on-premises appliance.
Recommendations
  • Explicitly state whether the Azure Migrate appliance supports Linux hosts, and provide instructions/examples for Linux deployments if supported.
  • Include Linux-specific preparation steps and troubleshooting guidance for physical servers running Linux.
  • Offer parity in examples and screenshots, showing both Windows and Linux server scenarios.
  • If the appliance is Windows-only, clarify this limitation early and suggest alternative approaches for Linux environments (such as agent-based discovery or third-party tools).
GitHub Create Pull Request
Migrate https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/simplified-experience-for-azure-migrate.md ...les/migrate/simplified-experience-for-azure-migrate.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 Windows bias by exclusively referencing Windows Server 2022 as the replication appliance, without mentioning or providing alternatives for Linux-based replication appliances. The migration stack improvements and onboarding steps are described in a Windows-centric manner, and there are no Linux-specific setup instructions, examples, or tooling references, despite the stated focus on migrating newer Linux distributions.
Recommendations
  • Include examples and instructions for setting up the replication appliance on Linux-based systems, if supported.
  • Mention Linux-compatible tools or alternatives for replication and migration, or clarify if Windows Server is a hard requirement.
  • Provide parity in onboarding steps and automation examples for Linux environments (e.g., shell scripts, Linux CLI commands) alongside any Windows/Powershell instructions.
  • Explicitly state OS requirements and limitations for the replication appliance, and discuss implications for Linux-only environments.
GitHub Create Pull Request
Migrate https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/review-assessment.md ...e-docs/blob/main/articles/migrate/review-assessment.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 page exhibits Windows bias by referencing Windows Server as the primary example of conditional readiness, mentioning Windows-specific migration tools (robocopy), and omitting Linux-specific migration guidance or examples. There are no Linux or open-source tool references, and remediation guidance is only illustrated with Windows scenarios.
Recommendations
  • Include Linux-specific readiness scenarios and examples (e.g., what happens if migrating a CentOS or Ubuntu server).
  • Provide parity in migration tool recommendations, such as mentioning rsync or scp alongside robocopy and azcopy for disk/data migration.
  • Add troubleshooting and remediation guidance for common Linux migration issues (e.g., boot type, disk partitioning, supported distributions).
  • Reference Linux compatibility and support in Azure VM assessments, including links to documentation on supported Linux distributions.
  • Ensure examples and instructions are balanced between Windows and Linux environments throughout the documentation.
GitHub Create Pull Request
Migrate https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/troubleshoot-appliance.md ...s/blob/main/articles/migrate/troubleshoot-appliance.md
High Priority View Details →
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 moderate Windows bias. Troubleshooting steps and examples frequently reference Windows-specific tools (Control Panel, admin command prompt, PowerShell, Notepad, registry edits, WMI, WinRM, etc.) and often present Windows remediation steps before or in greater detail than Linux equivalents. Some sections provide only Windows examples or use Windows-centric terminology, while Linux instructions are sometimes less detailed or appear after Windows steps.
Recommendations
  • Ensure Linux troubleshooting steps are presented with equal prominence and detail as Windows steps, including command-line examples and configuration file locations.
  • Where Windows tools (e.g., Control Panel, Notepad, PowerShell, registry editor) are referenced, provide Linux equivalents (e.g., timedatectl, nano/vi, bash scripts, systemd services, etc.).
  • Avoid presenting Windows steps first by default; alternate or parallelize instructions for both platforms.
  • For sections that only mention Windows tools or commands (e.g., time sync, hosts file editing, service management), add corresponding Linux commands and file paths.
  • Where PowerShell scripts are given for Windows, provide bash or shell script equivalents for Linux.
  • Explicitly state platform applicability at the start of each troubleshooting section, and use tabbed or side-by-side formatting for Windows and Linux instructions where possible.
GitHub Create Pull Request
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-09 00:34
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 referencing Windows-specific file paths (e.g., C:\Users\Public\Desktop\DiagnosticsReport), mentioning Windows Server 2022 evaluation licenses exclusively, and omitting any Linux-based appliance or example. There are no instructions, screenshots, or references for running diagnostics or accessing reports on Linux-based appliances, nor is there mention of Linux file paths or OS-specific considerations outside Windows.
Recommendations
  • Include instructions and examples for Linux-based Azure Migrate appliances, such as file paths for diagnostics reports (e.g., /home/public/Desktop/DiagnosticsReport or similar).
  • Mention Linux OS license considerations if applicable, or clarify if the appliance is Windows-only.
  • Add screenshots and step-by-step guidance for Linux users, ensuring parity in troubleshooting steps.
  • Explicitly state OS requirements and supported platforms for the appliance, and provide links to Linux-specific troubleshooting resources if available.
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-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 in several ways: Windows tools and terminology (WinRM, WMI, Get-WmiObject, IIS, applicationHost.config, ISAPI filters) are mentioned first or exclusively in troubleshooting steps, with Linux equivalents (SSH, Linux permissions, etc.) referenced less frequently and often after Windows. Many examples and error codes focus on Windows-specific technologies, and Linux troubleshooting lacks parity in detail and actionable steps. Web app migration errors are almost entirely IIS/Windows-centric, with no mention of Apache, Nginx, or Linux-based web servers.
Recommendations
  • Provide Linux-first or Linux-parity troubleshooting steps and examples alongside Windows instructions, especially for connection, credential, and performance data errors.
  • Include Linux-specific tools and commands (e.g., systemd, journalctl, SSH configuration, Linux file permissions) where Windows tools like WinRM and WMI are referenced.
  • For web app migration errors, add equivalent guidance for common Linux web servers (Apache, Nginx, Tomcat), including configuration, authentication, and module/filter issues.
  • Ensure error codes and recommended actions are balanced between Windows and Linux, with clear, actionable steps for both platforms.
  • Avoid mentioning Windows tools or patterns first unless they are more common in the user base; strive for equal prominence for Linux scenarios.
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-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 strong Windows bias. Troubleshooting steps and examples are almost exclusively presented using Windows tools (PowerShell, MMC snap-in, Command Prompt), and instructions assume access to a Windows environment (e.g., remote desktop, editing C:\Windows\System32\drivers\etc\hosts). There are no Linux-specific commands, tools, or alternative workflows provided, even though Azure Migrate appliances can be deployed on Linux and many VMware admins use Linux systems. Linux equivalents for PowerShell commands, network tests, and file editing are missing.
Recommendations
  • Provide Linux equivalents for all PowerShell and Command Prompt commands (e.g., use curl, nc, dig, or systemctl where appropriate).
  • Include troubleshooting steps using Linux tools (e.g., checking services with systemctl, editing /etc/hosts, testing connectivity with netcat or telnet).
  • Mention Linux-based Azure Migrate appliance deployment and management explicitly, and clarify which steps are OS-agnostic.
  • Re-order examples to present both Windows and Linux approaches side-by-side, or clearly indicate when a step is Windows-specific.
  • Avoid assuming remote desktop or MMC snap-in access; suggest SSH and Linux-native tools where applicable.
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-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. Troubleshooting steps and examples frequently prioritize Windows tools (PowerShell, WinRM, Registry Editor, WMI), with Linux equivalents mentioned later or in less detail. Many error codes and remediation steps are Windows-centric, referencing PowerShell, Windows environment variables, and registry settings, while Linux troubleshooting is less comprehensive and often limited to basic SSH or command-line instructions. Some sections, such as mitigation verification and agent-based troubleshooting, provide detailed PowerShell and Windows GUI steps, but offer minimal or no Linux-specific guidance. The documentation assumes familiarity with Windows administrative patterns and tools, and Linux instructions are sometimes presented as an afterthought.
Recommendations
  • Ensure that Linux troubleshooting steps are provided with equal detail and clarity as Windows steps, including GUI and command-line workflows where applicable.
  • Present Linux and Windows examples side-by-side, rather than listing Windows first or exclusively.
  • Include Linux-specific error codes, troubleshooting scenarios, and remediation steps, especially for agent-based analysis and connectivity issues.
  • Expand Linux tool coverage beyond basic SSH, such as using systemd, journalctl, or other native Linux diagnostics for dependency analysis.
  • Avoid assuming the use of Windows-only tools (e.g., Registry Editor, WMI) and provide Linux alternatives or note when steps are OS-specific.
  • Where PowerShell is referenced for Windows, provide equivalent Bash or shell commands for Linux, and clarify OS applicability in each step.
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-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, with troubleshooting steps, error codes, and examples predominantly focused on Windows environments. PowerShell commands and Windows-specific tools (WinRM, WMI, UAC, IIS) are described in detail, often before or instead of Linux equivalents. Linux troubleshooting is generally limited to SSH connectivity checks or basic 'ls' commands, with little coverage of common Linux-specific errors, tools, or remediation steps. Several remediation sections and error tables provide Windows-centric instructions, while Linux guidance is sparse or absent.
Recommendations
  • Provide equivalent Linux troubleshooting steps and examples for each Windows-focused section, including common Linux errors and their remediation.
  • Include Linux command-line examples (e.g., using SSH, systemctl, journalctl, package managers) alongside PowerShell commands.
  • Expand error tables to include Linux-specific issues (e.g., SSH key problems, sudo permissions, SELinux/AppArmor restrictions, missing packages) and their solutions.
  • Document Linux-specific prerequisites and configuration steps (e.g., required packages, user/group permissions, firewall rules) in parity with Windows details.
  • Avoid presenting Windows steps or tools first; instead, structure instructions to treat Windows and Linux equally, or group them by OS.
  • Add troubleshooting guidance for popular Linux distributions (Ubuntu, CentOS, RHEL, SUSE), including references to their documentation where appropriate.
  • Where Windows tools (e.g., WMI, UAC, IIS) are mentioned, clarify their Linux equivalents or note when a feature is Windows-only.
GitHub Create Pull Request
Migrate https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/troubleshoot-network-connectivity.md .../articles/migrate/troubleshoot-network-connectivity.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by providing command-line examples (such as nslookup) in a Windows context (e.g., 'c:\ >nslookup'), referencing PowerShell-specific tools (Test-NetConnection), and omitting equivalent Linux/Unix commands and troubleshooting steps. All screenshots and command prompts are Windows-centric, and there are no Bash, Linux shell, or cross-platform instructions. The guidance for editing the hosts file and DNS troubleshooting is written as if the appliance is always Windows-based, with no mention of Linux paths or tools.
Recommendations
  • Include Linux/Unix command-line examples for DNS resolution (e.g., 'dig', 'host', 'nslookup' in Bash).
  • Provide troubleshooting steps for both Windows and Linux appliances, including file paths for hosts file (e.g., /etc/hosts for Linux).
  • Add Bash equivalents for PowerShell commands, such as using 'nc' or 'telnet' for port connectivity checks instead of only Test-NetConnection.
  • Show screenshots or terminal output from Linux environments alongside Windows examples.
  • Explicitly state that the instructions apply to both Windows and Linux, or clarify any platform-specific requirements.
  • Mention Linux-specific proxy and DNS configuration steps where relevant.
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-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 exclusively focused on troubleshooting Windows OS upgrade issues during VM migration, with all examples, terminology, and recommended actions centered around Windows. There are no references to Linux OS upgrades, Linux VM migration issues, or Linux-specific tools or workflows. Windows tools and Azure portal steps are described in detail, but there is no mention of equivalent Linux processes.
Recommendations
  • Add a parallel section for troubleshooting Linux OS upgrade issues during VM migration.
  • Include Linux-specific examples, such as handling disk expansion using Linux commands (e.g., fdisk, resize2fs) and addressing common Linux upgrade errors.
  • Mention Linux VM SKU limitations and how to resolve them in Azure.
  • Provide links to Linux documentation for in-place upgrades and disk management.
  • Ensure that both Windows and Linux migration scenarios are covered equally in troubleshooting guides.
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-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 is heavily biased toward Windows environments for ASP.NET app containerization. All instructions, prerequisites, and examples assume Windows OS, PowerShell, and Windows-specific tools (such as Microsoft Web Deploy). There is no mention of Linux-based workflows for ASP.NET apps, nor are Linux equivalents or alternatives provided. The documentation does mention Linux support for Java/Tomcat apps, but not for ASP.NET, and all example commands and troubleshooting steps are Windows-centric.
Recommendations
  • Add explicit statements about Linux support or limitations for ASP.NET containerization, clarifying whether Linux-based ASP.NET (.NET Core/5/6+) apps are supported.
  • If possible, provide Linux-based instructions for containerizing ASP.NET Core apps, including examples using Bash, Linux package managers, and Linux-compatible deployment tools.
  • Include alternative steps for environments where PowerShell or Microsoft Web Deploy are not available, such as using SSH or SCP for remote connectivity and file transfer.
  • Mention and document any cross-platform tools or approaches (e.g., Docker CLI, VS Code Remote Containers) that can be used from Linux or macOS.
  • Provide troubleshooting guidance for Linux environments, including log file locations and common issues.
  • Clearly indicate in the prerequisites and introduction that the current workflow is Windows-only for ASP.NET Framework apps, and suggest alternatives or workarounds for Linux users.
GitHub Create Pull Request
Migrate https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/tutorial-app-containerization-azure-pipeline.md ...igrate/tutorial-app-containerization-azure-pipeline.md
High Priority View Details →
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 by referencing Windows file paths (C:\ProgramData...), Windows-specific navigation instructions (File Explorer, Hidden items), and focusing on ASP.NET (a Windows-centric technology) in its examples. There is no mention of equivalent Linux file paths or instructions for users running the Azure Migrate App Containerization tool on Linux. The artifact location and navigation steps are exclusively Windows-oriented, and Linux alternatives are not provided. While the 'Next steps' section mentions Linux scenarios, the main tutorial does not provide parity for Linux users.
Recommendations
  • Add instructions for locating artifacts on Linux systems, including typical Linux file paths and navigation commands.
  • Include examples and navigation steps for users running the Azure Migrate App Containerization tool on Linux, such as using the terminal and Linux commands (e.g., ls, cd).
  • Ensure artifact upload steps mention Linux file/folder conventions and tools (e.g., using the terminal, SCP, or rsync for uploads).
  • Provide parity in examples for both ASP.NET (Windows) and Java/Tomcat (Linux), including screenshots or command-line snippets for both environments.
  • Clarify in the prerequisites whether the tutorial is intended for Windows, Linux, or both, and provide guidance accordingly.
GitHub Create Pull Request
Migrate https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/tutorial-app-containerization-java-kubernetes.md ...grate/tutorial-app-containerization-java-kubernetes.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example Powershell Heavy 🔧 Windows Tools
Summary
The documentation exhibits a strong Windows bias: the Azure Migrate: App Containerization tool 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 file paths/logs are referenced using Windows conventions. There are no instructions or examples for running the tool on Linux or macOS, nor alternatives for non-Windows users. The documentation assumes the user has access to a Windows environment, even when containerizing Java apps running on Linux servers.
Recommendations
  • Provide a Linux (and optionally macOS) version of the Azure Migrate: App Containerization tool, or document how to run the tool in a Linux environment (e.g., via Wine, Docker, or a VM).
  • Include installation and usage instructions for Linux users, using Bash and Linux-native commands.
  • Reference Linux file paths and troubleshooting steps alongside Windows equivalents.
  • If Windows is a hard requirement, clearly state this upfront and suggest workarounds (such as using a Windows VM or cloud-hosted Windows environment) for Linux-only users.
  • Offer parity in examples and screenshots, showing both Windows and Linux workflows where possible.
GitHub Create Pull Request
Migrate https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/tutorial-app-containerization-aspnet-kubernetes.md ...ate/tutorial-app-containerization-aspnet-kubernetes.md
High Priority View Details →
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 containerizing and migrating ASP.NET applications to Azure Kubernetes Service is heavily biased towards Windows environments. All prerequisites, installation steps, and operational instructions require a Windows machine, PowerShell, and Windows-specific tools such as Microsoft Web Deploy. There are no Linux-based instructions, examples, or alternatives for running the containerization tool or managing ASP.NET apps. The documentation assumes the reader is using Windows Server/Client OS and IIS, and does not provide parity for Linux users wishing to containerize ASP.NET apps.
Recommendations
  • Provide instructions and support for running the Azure Migrate: App Containerization tool on Linux machines, or clarify if this is not possible.
  • Include Linux-based examples for ASP.NET Core applications, which are cross-platform and commonly deployed on Linux.
  • Offer alternatives to PowerShell remoting, such as SSH or other remote management tools available on Linux.
  • Document how to containerize ASP.NET applications hosted on Linux (e.g., via Kestrel or Apache/Nginx reverse proxy), if supported.
  • List Linux prerequisites and installation steps alongside Windows instructions, or clearly state platform limitations up front.
  • If the tool is Windows-only, suggest open-source or Azure-supported Linux alternatives for ASP.NET containerization.
GitHub Create Pull Request
← Previous Page 12 of 37 Next →