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 201-225 of 918 flagged pages
Migrate Support for physical discovery and assessment in Azure Migrate and Modernize ...in/articles/migrate/migrate-support-matrix-physical.md
High Priority View Details →
Scanned: 2026-01-10 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-specific tools and patterns (PowerShell, WinRM, WMI) are mentioned first and in detail, with Linux equivalents described briefly or as secondary. Examples and sample scripts are exclusively for Windows environments (e.g., SQL Server discovery, web apps), with Linux support often marked as 'not supported' or lacking equivalent guidance. Windows server requirements and access patterns are described in depth, while Linux instructions are minimal or refer to external links.
Recommendations
  • Provide Linux-first or Linux-parity examples alongside Windows examples, especially for setup, access, and permissions.
  • Include sample scripts or command-line instructions for Linux environments where possible (e.g., SQL Server on Linux, Tomcat web apps).
  • Explicitly document Linux-specific troubleshooting, requirements, and supported scenarios in the same detail as Windows.
  • Avoid referencing Windows tools (PowerShell, WinRM, WMI) without also describing Linux alternatives (SSH, shell commands) in equal detail.
  • Where features are not supported for Linux (e.g., SQL Server instance discovery), clarify roadmap or alternatives for Linux users.
GitHub Create Pull Request
Migrate Support for VMware vSphere migration in Azure Migrate ...les/migrate/migrate-support-matrix-vmware-migration.md
High Priority View Details →
Scanned: 2026-01-10 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 moderate Windows bias. Windows operating systems and tools (e.g., PowerShell) are mentioned first or exclusively in several sections. PowerShell is referenced as the main CLI for configuring replication, with no mention of Linux shell alternatives. Windows-specific requirements and troubleshooting steps (such as RDP and Windows Firewall) are described in detail, while Linux equivalents (e.g., SSH, firewall configuration) are covered more briefly and lack concrete command examples. Some sections provide detailed instructions for Windows but only general guidance for Linux, and there are no Linux shell script examples for appliance deployment.
Recommendations
  • Provide Linux shell (bash) script examples for appliance deployment and configuration, alongside PowerShell.
  • Include Linux-first or Linux-parity examples in sections describing VM preparation, agent installation, and connectivity (e.g., explicit firewall configuration commands for Linux).
  • Balance the order of presentation so that Linux and Windows instructions appear together, or alternate which is presented first.
  • Reference Linux tools (such as SSH, iptables, firewalld) with the same level of detail as Windows tools (e.g., RDP, Windows Firewall).
  • Add troubleshooting steps and links for common Linux migration issues, similar to those provided for Windows.
  • Explicitly mention support for Linux automation and scripting in migration workflows, not just PowerShell.
GitHub Create Pull Request
Migrate Onboard on-premises servers in VMware virtual environment to Azure Arc ...les/migrate/onboard-to-azure-arc-with-azure-migrate.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation exhibits a Windows bias in several ways: Windows-specific tools and commands (WinRM, PowerShell) are mentioned first and in more detail, with explicit instructions (e.g., 'winrm qc' command) and requirements (PowerShell version 3.0+). Windows connection patterns (WinRM, TrustedHosts) are described before Linux equivalents (SSH), and troubleshooting steps often reference Windows tools and error codes. Linux instructions are present but less detailed, and Linux-specific onboarding or troubleshooting examples are missing.
Recommendations
  • Provide Linux onboarding examples and command-line instructions (e.g., how to verify SSH access, required packages, or agent installation on Linux).
  • Mention Linux prerequisites (such as required SSH configuration, supported distributions, and package dependencies) with the same level of detail as Windows.
  • Include troubleshooting steps and error codes specific to Linux, not just SSH timeouts.
  • Present Windows and Linux instructions in parallel, or alternate which is mentioned first, to avoid 'windows_first' ordering.
  • Reference Linux tools and patterns (e.g., systemd, journalctl, SSH key management) where appropriate, alongside Windows tools.
GitHub Create Pull Request
Migrate VMware server discovery support in Azure Migrate and Modernize ...main/articles/migrate/migrate-support-matrix-vmware.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation page exhibits several forms of Windows bias. Windows tools and technologies (PowerShell, WMI, WinRM, Windows authentication) are mentioned first and in greater detail than their Linux equivalents. SQL Server discovery and web app discovery are supported only or primarily for Windows, with Linux support explicitly missing or limited. Example scripts and configuration details are provided only for Windows authentication and SQL Server, with no equivalent Linux database discovery or configuration guidance. Windows-specific ports, permissions, and patterns (such as domain accounts, WMI, WinRM) are described in detail, while Linux instructions are minimal or absent.
Recommendations
  • Provide equivalent Linux examples and scripts for database discovery and permissions, especially for popular Linux databases like MySQL, PostgreSQL, or MariaDB.
  • Include Linux-first or Linux-parity instructions for appliance deployment, credential management, and agent installation.
  • Expand web app discovery documentation to cover Linux web servers (Apache, Nginx) and provide configuration steps for those environments.
  • Describe Linux-specific tools and patterns (e.g., SSH, sudoers configuration, systemd service management) with the same level of detail as Windows tools.
  • Ensure that port and protocol requirements are documented for both Windows and Linux environments, including alternatives to WinRM and WMI for Linux.
  • Add troubleshooting and best practices sections for Linux environments, matching the coverage given to Windows.
  • Explicitly state limitations for Linux support in all relevant sections, and provide a roadmap or guidance for future parity.
GitHub Create Pull Request
Migrate Prepare machines for migration with Azure Migrate ...cs/blob/main/articles/migrate/prepare-for-migration.md
High Priority View Details →
Scanned: 2026-01-10 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-specific instructions and tools (such as diskpart, SAN policy, Windows Firewall, RDP, and PowerShell) are described in detail, often with step-by-step guidance, while Linux instructions are more generic and less detailed. Windows examples and configuration steps are presented first and in greater depth, with Linux steps following and often lacking equivalent command-line examples or troubleshooting guidance. There is a reliance on Windows-centric tools and patterns, and Linux instructions are sometimes limited to 'check SSH' or 'update fstab', without concrete examples.
Recommendations
  • Provide Linux command-line examples for all steps where Windows commands are given (e.g., show how to update fstab, rebuild init image, configure firewall rules for SSH, and enable serial console logging with specific commands).
  • Include troubleshooting steps and links for Linux VMs equivalent to those given for Windows (e.g., boot diagnostics, serial console, agent installation).
  • Balance the order of presentation so that Linux and Windows instructions are given equal prominence, or alternate between them.
  • Reference Linux-native tools (e.g., iptables, firewalld, systemctl) where Windows tools (e.g., Windows Firewall, PowerShell) are mentioned.
  • Add explicit instructions for preparing Linux VMs for migration, including handling updates, persistent network configuration, and agent installation, with concrete shell commands.
  • Ensure that all configuration and connectivity steps for Linux are as detailed as those for Windows, including post-migration checks and troubleshooting.
GitHub Create Pull Request
Migrate Prepare machines for agentless migration with Azure Migrate ...in/articles/migrate/prepare-for-agentless-migration.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by presenting Windows-specific instructions and examples before Linux equivalents, using Windows tools (diskpart, PowerShell) and screenshots, and providing more detailed manual steps for Windows (including registry and service configuration). Linux instructions are present but less detailed, with fewer concrete command examples and less troubleshooting guidance. Windows PowerShell is used for service configuration, while Linux equivalents (systemctl, service) are not mentioned. Windows-centric terminology and tools (e.g., registry, diskpart) are emphasized.
Recommendations
  • Provide Linux command equivalents for all manual steps, such as using systemctl or service to configure DHCP and check agent status.
  • Include Linux screenshots or terminal output examples where Windows screenshots are given.
  • Balance the order of presentation: alternate or parallelize Windows and Linux instructions, rather than listing all Windows steps first.
  • Expand Linux troubleshooting guidance and manual preparation steps to match the detail given for Windows.
  • Reference Linux-specific documentation and tools (e.g., journalctl, dmesg, systemctl) alongside Windows tools.
  • Ensure that links to manual installation of agents and drivers for Linux are as prominent and detailed as those for Windows.
GitHub Create Pull Request
Migrate How to review the assessments created for migration to SQL Server on Azure VM, Azure SQL Managed Instance and Azure SQL Database ...cs/blob/main/articles/migrate/review-sql-assessment.md
High Priority View Details →
Scanned: 2026-01-10 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 consistently referencing SQL Server on Azure VM as the primary migration target, which is a Windows-centric deployment. There is no mention of Linux-based SQL Server deployments, nor are Linux-specific migration scenarios, readiness checks, or cost estimates discussed. The documentation omits examples or guidance for users migrating SQL Server instances running on Linux, and does not acknowledge Linux tools or patterns. All references to operating system support status focus on Windows support lifecycles.
Recommendations
  • Add explicit guidance and examples for SQL Server instances running on Linux, including migration scenarios to Azure SQL targets.
  • Include readiness and cost estimation details for Linux-based SQL Server deployments.
  • Mention Linux operating system support status in the supportability section, alongside Windows.
  • Reference Linux tools and patterns (e.g., Bash scripts, Linux-native monitoring/logging) where relevant.
  • Ensure parity in screenshots and step-by-step instructions for both Windows and Linux SQL Server sources.
GitHub Create Pull Request
Migrate Quickstart to create an Azure Migrate project using Portal ...lob/main/articles/migrate/quickstart-create-project.md
High Priority View Details →
Scanned: 2026-01-10 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 by providing command-line examples exclusively in PowerShell, referencing the use of PowerShell as Administrator, and omitting equivalent Linux shell instructions. The instructions for installing and using the Azure CLI are presented from a Windows/PowerShell perspective, with no mention of Linux or cross-platform usage. There are no examples or guidance for Linux users, and Windows-centric terminology and patterns are used throughout.
Recommendations
  • Include equivalent Azure CLI instructions for Linux/macOS users, specifying shell commands (bash/zsh) and installation steps for those platforms.
  • Present command-line examples in a cross-platform manner, indicating that Azure CLI works on Windows, Linux, and macOS, and showing both PowerShell and bash syntax where relevant.
  • Avoid referencing 'PowerShell as Administrator' as the default; instead, mention running commands in a terminal or shell appropriate to the user's OS.
  • Add notes or sections highlighting any OS-specific considerations, and ensure parity in guidance for both Windows and Linux environments.
GitHub Create Pull Request
Migrate Azure Migrate FAQ ...azure-docs/blob/main/articles/migrate/resources-faq.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates Windows bias by referencing Windows-specific tools (MAP Toolkit), prioritizing Windows migration scenarios, and omitting explicit Linux migration examples or tools. The FAQ discusses migration planning for Windows operating systems and tools like MAP Toolkit, which are Windows-centric, without mentioning equivalent Linux migration tools or providing Linux-specific guidance. Scripting mentions Bash, PowerShell, and Python, but PowerShell is listed before Bash, and no Linux command-line examples are provided.
Recommendations
  • Include examples and guidance for migrating Linux servers and workloads, such as common Linux distributions supported and any Linux-specific considerations.
  • Mention Linux-compatible migration assessment tools or alternatives to MAP Toolkit, and clarify which tools are cross-platform.
  • Provide Linux command-line examples (e.g., Bash scripts) alongside PowerShell for automation tasks.
  • Ensure that references to operating systems and tools are balanced, mentioning Linux and Windows together where relevant.
  • Add a FAQ entry specifically addressing Linux migration scenarios, challenges, and best practices.
GitHub Create Pull Request
Migrate Assess large numbers of physical servers for migration to Azure with Azure Migrate | Microsoft Docs ...lob/main/articles/migrate/scale-physical-assessment.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by exclusively referencing the Azure Migrate appliance as being deployed on a Windows server, without mentioning Linux support or providing Linux-specific instructions or examples. There are no Linux or cross-platform alternatives discussed for the assessment appliance, and no Linux command-line or tool usage is shown.
Recommendations
  • Explicitly state whether the Azure Migrate appliance supports Linux hosts, and if so, provide instructions for Linux deployment.
  • Include Linux-specific examples and steps for preparing physical servers for assessment.
  • Mention any Linux-compatible tools or scripts that can be used for discovery and assessment.
  • If Windows-only support is a product limitation, clarify this early and suggest alternative approaches for Linux environments.
GitHub Create Pull Request
Migrate Simplified experience for Azure Migrate ...les/migrate/simplified-experience-for-azure-migrate.md
High Priority View Details →
Scanned: 2026-01-10 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 exclusively referencing Windows Server 2022 as the required replication appliance, without mentioning any Linux-based alternatives or providing Linux-specific setup instructions. While the page highlights improved support for newer Linux distributions as a benefit, it does not provide Linux-centric examples, tools, or parity in appliance options. The documentation positions Windows tooling as the default and only supported path for core migration infrastructure.
Recommendations
  • Explicitly state whether a Linux-based replication appliance is supported or planned; if not, explain the rationale.
  • Provide Linux-specific setup, configuration, or troubleshooting examples where relevant, especially since the target audience includes those migrating Linux workloads.
  • If Windows Server is a hard requirement for the replication appliance, offer guidance for Linux administrators on how to deploy and manage this component in mixed environments.
  • Include references to Linux-native tools or workflows where possible, or clarify integration points for Linux environments.
  • Ensure future documentation updates include Linux-first or at least Linux-equal examples and guidance, especially in sections discussing agent installation, migration steps, and troubleshooting.
GitHub Create Pull Request
Migrate Start here - Migrate VMware deployments to Azure ...e-docs/blob/main/articles/migrate/start-here-vmware.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a bias towards Windows environments by providing migration instructions and automation examples primarily using Azure PowerShell, with no mention of Linux CLI equivalents (such as Azure CLI or bash scripting). Additionally, the use of RVTools—a Windows-only tool—for discovery further reinforces Windows-centric tooling. There are no Linux-specific examples or guidance for users operating in non-Windows environments.
Recommendations
  • Include Azure CLI (cross-platform) examples alongside or before Azure PowerShell instructions for migration and automation steps.
  • Mention and provide guidance for Linux-compatible discovery tools or methods, such as using open-source scripts or native VMware utilities accessible from Linux.
  • Add explicit instructions or links for performing migration tasks from Linux/macOS environments, ensuring parity in documentation.
  • Clearly indicate platform compatibility for each tool and step, helping users choose appropriate methods for their operating system.
GitHub Create Pull Request
Migrate Troubleshoot Azure Migrate appliance diagnostic .../articles/migrate/troubleshoot-appliance-diagnostic.md
High Priority View Details →
Scanned: 2026-01-10 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 referencing Windows-specific paths (e.g., C:\Users\Public\Desktop\DiagnosticsReport), mentioning Windows Server 2022 evaluation license exclusively, and omitting any mention of Linux-based appliances or examples. There are no Linux file paths, commands, or troubleshooting instructions, and all operational details assume a Windows environment.
Recommendations
  • Include instructions and examples for Linux-based Azure Migrate appliances, such as file paths, report locations, and relevant commands.
  • Mention Linux equivalents for license checks, agent status, and resource availability.
  • Clarify whether the appliance supports Linux hosts and, if so, provide parity in troubleshooting steps and diagnostic report handling for Linux.
  • Add screenshots and step-by-step guides for Linux environments where applicable.
GitHub Create Pull Request
Migrate Troubleshoot assessments FAQ in Azure Migrate ...b/main/articles/migrate/troubleshoot-assessment-faq.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation page exhibits a Windows bias in several ways: Windows/Hyper-V scenarios and troubleshooting steps are described in detail and often referenced first, while Linux-specific guidance is minimal or absent. Licensing cost is only considered for Windows servers, with Linux explicitly excluded. Troubleshooting examples and network capture instructions focus on Windows-centric browsers and tools (Edge, Internet Explorer), with no mention of Linux alternatives. There are no Linux command-line or tool examples, and the documentation does not provide parity for Linux environments in assessment, troubleshooting, or migration scenarios.
Recommendations
  • Add Linux-specific troubleshooting steps and examples, especially for performance data collection and assessment issues.
  • Include guidance for collecting network traffic/logs on Linux systems (e.g., using tcpdump, Wireshark, or browser tools on Linux).
  • Clarify how licensing costs for Linux servers are handled or provide guidance for Linux licensing considerations.
  • Provide parity in examples and instructions for both Windows and Linux environments, including command-line and tool usage.
  • Reference Linux tools and patterns alongside Windows/Hyper-V, and avoid presenting Windows scenarios first unless contextually necessary.
GitHub Create Pull Request
Migrate Troubleshoot slow replication or stuck migration in agentless VMware migration ...in/articles/migrate/troubleshoot-replication-vmware.md
High Priority View Details →
Scanned: 2026-01-10 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: instructions for modifying the Azure Migrate appliance configuration and restarting services are given exclusively for Windows environments (using Remote Desktop, editing files in %programdata%, and restarting services via PowerShell commands). There are no equivalent Linux instructions or examples, despite the possibility of running the appliance on Linux. Windows tools and patterns (Remote Desktop, PowerShell, Windows file paths) are mentioned first and exclusively, with no mention of Linux alternatives.
Recommendations
  • Provide Linux-specific instructions for accessing and editing the appliance configuration (e.g., SSH, nano/vim, Linux file paths).
  • Include commands for restarting the Azure Migrate gateway service on Linux (e.g., systemctl, service).
  • Mention both Windows and Linux environments when discussing appliance management, and ensure parity in troubleshooting steps.
  • Use platform-neutral language where possible, or clearly indicate when steps are platform-specific.
  • Add examples for both Windows and Linux users for all relevant steps.
GitHub Create Pull Request
Migrate Troubleshoot the Azure Migrate appliance ...s/blob/main/articles/migrate/troubleshoot-appliance.md
High Priority View Details →
Scanned: 2026-01-10 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 moderate Windows bias. Troubleshooting steps and examples frequently reference Windows-specific tools (Control Panel, admin command prompt, Notepad, PowerShell, Windows registry, WMI, WinRM) and provide Windows instructions first or exclusively in many sections. Linux instructions are present but often appear after Windows steps or are less detailed. Some troubleshooting flows (e.g., time sync, host file editing, credential validation) only mention Windows methods or tools, with Linux alternatives missing or less emphasized.
Recommendations
  • Ensure Linux troubleshooting steps are provided wherever Windows steps are given, including parity in detail and order.
  • Include Linux-first examples or alternate flows where appropriate, especially for common tasks like time synchronization, host file editing, and credential validation.
  • Add Linux equivalents for Windows-specific tools (e.g., show how to edit /etc/hosts, use timedatectl/ntp for time sync, check SSH and sudo configuration for permissions).
  • Balance PowerShell and Windows command prompt examples with Bash and Linux shell commands.
  • Where possible, use cross-platform language (e.g., 'edit the hosts file' instead of 'open Notepad as admin and edit C:\Windows\System32\Drivers\etc\hosts').
  • Explicitly call out differences in troubleshooting steps for Linux and Windows appliances, especially in sections that currently only mention Windows.
GitHub Create Pull Request
Migrate Common issues in Azure Migrate assessments .../blob/main/articles/migrate/troubleshoot-assessment.md
High Priority View Details →
Scanned: 2026-01-10 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 demonstrates a Windows bias in several areas: Windows-specific tools and terminology (WinRM, WMI, Get-WmiObject, IIS, applicationHost.config) are mentioned first or exclusively, with Linux equivalents either omitted or referenced secondarily. Troubleshooting steps and examples often focus on Windows (e.g., WinRM TrustedHosts, WMI calls, IIS migration errors) without providing parallel Linux commands or guidance. Linux troubleshooting is less detailed, and Linux-specific migration issues are summarized more briefly.
Recommendations
  • Provide Linux-first or Linux-parallel troubleshooting steps and examples wherever Windows tools (WinRM, WMI, PowerShell) are mentioned.
  • Include Linux command-line examples (e.g., SSH troubleshooting, permissions checks, service status commands) alongside Windows/PowerShell instructions.
  • Expand Linux migration error explanations to match the detail given for Windows (e.g., common Apache/Nginx migration issues, SELinux/AppArmor configuration).
  • Reference Linux configuration files (e.g., /etc/ssh/sshd_config, /etc/passwd) and common Linux admin patterns where relevant.
  • For web app migration, include guidance for Java/Tomcat/Apache/Nginx apps, not just ASP.NET/IIS.
  • Balance the order of presentation so Linux and Windows are treated equally, not with Windows first or exclusively.
GitHub Create Pull Request
Migrate Troubleshoot replication issues in agentless VMware VM migration ...ate/troubleshoot-changed-block-tracking-replication.md
High Priority View Details →
Scanned: 2026-01-10 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 demonstrates a strong Windows bias: troubleshooting steps and commands are almost exclusively presented using Windows tools (PowerShell, Command Prompt, MMC snap-in, services.msc), and instructions assume the Azure Migrate appliance is accessed via Windows Remote Desktop. There are no Linux shell or cross-platform alternatives provided, and all example commands (e.g., nslookup, Test-NetConnection, Net Start/Stop, azcopy usage, editing hosts file) are given in Windows-centric syntax. Linux-based administration is not addressed.
Recommendations
  • Provide Linux equivalents for all troubleshooting steps, including shell commands (e.g., use 'systemctl' or 'service' for service management, 'nc' or 'telnet' for connectivity tests, 'dig' for DNS resolution, and instructions for editing /etc/hosts).
  • Clarify whether the Azure Migrate appliance can be deployed on Linux, and if so, include Linux-specific guidance.
  • Where PowerShell is used, offer Bash or shell alternatives for scripting and automation.
  • Mention cross-platform tools (e.g., azcopy is available for Linux; show Linux installation and usage).
  • Avoid assuming Remote Desktop or MMC snap-in access; suggest SSH and Linux-native tools where applicable.
  • Explicitly state OS requirements and provide parity in troubleshooting instructions for both Windows and Linux environments.
GitHub Create Pull Request
Migrate Troubleshoot ongoing server discovery, software inventory, and SQL discovery ...s/blob/main/articles/migrate/troubleshoot-discovery.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits a Windows bias in several ways: troubleshooting steps and error remediation frequently reference Windows tools (PowerShell, WMI, WinRM, IIS), and provide detailed, step-by-step instructions for Windows environments, often before or in greater detail than for Linux. Many examples and commands are PowerShell-centric, and Linux troubleshooting is typically limited to basic SSH connectivity or generic 'ls' commands, with little parity in depth or specificity. Some Linux steps are missing or less detailed, and Windows-specific issues (UAC, environment variables, registry, IIS) are covered extensively, while Linux equivalents are not discussed.
Recommendations
  • Provide Linux-specific troubleshooting steps and examples with equal detail, including common Linux errors and their remediation.
  • Include Linux command-line examples (e.g., using SSH, systemctl, journalctl, package managers) for verification and remediation, not just 'ls'.
  • Document Linux equivalents for Windows tools (e.g., alternatives to WMI, PowerShell, IIS), such as systemd, Apache/Nginx, and relevant configuration paths.
  • Ensure error tables and remediation steps cover Linux-specific scenarios (e.g., SELinux/AppArmor, sudo permissions, SSH configuration issues).
  • Avoid presenting Windows steps first or exclusively; structure sections to address both platforms in parallel.
  • Add troubleshooting guidance for Linux web servers and applications, not just IIS.
  • Clarify when steps are OS-specific, and provide links to Linux documentation where appropriate.
GitHub Create Pull Request
Migrate Troubleshoot Windows upgrade issues ...ocs/blob/main/articles/migrate/troubleshoot-upgrade.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation is exclusively focused on troubleshooting Windows OS upgrade issues during VM migration, with all examples, terminology, and linked resources pertaining to Windows. There are no Linux-specific troubleshooting steps, examples, or references to Linux tools or upgrade processes. The guidance assumes the use of Windows VMs and Windows-centric Azure features, omitting Linux parity.
Recommendations
  • Add a parallel section for troubleshooting Linux OS upgrade issues during VM migration, including common problems and solutions.
  • Provide examples and links for expanding Linux OS disks (e.g., using Azure CLI, Linux partitioning tools) alongside the Windows instructions.
  • Reference Linux-specific documentation for in-place upgrades (e.g., Ubuntu release upgrades, Red Hat upgrade tools) where appropriate.
  • Clarify in the introduction that the guidance is Windows-specific, and link to Linux migration/upgrade documentation if available.
  • Ensure that Azure Migrate documentation includes both Windows and Linux VM scenarios, with equal prominence and detail.
GitHub Create Pull Request
Migrate ASP.NET app containerization and migration to App Service ...te/tutorial-app-containerization-aspnet-app-service.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example Powershell Heavy 🔧 Windows Tools
Summary
The documentation is heavily biased toward Windows environments for ASP.NET app containerization. All instructions, prerequisites, and examples assume Windows servers, Windows OS, and Windows-specific tools (PowerShell, Web Deploy). There are no Linux-based instructions or parity for ASP.NET apps, and all operational steps (discovery, installation, deployment) require Windows. Linux is only mentioned as a target for Java apps, not for ASP.NET.
Recommendations
  • Add guidance and examples for containerizing ASP.NET Core applications running on Linux servers, including prerequisites and discovery steps.
  • Provide Linux-based installation instructions for the App Containerization tool, or clarify if/when Linux support will be available for ASP.NET workloads.
  • Include examples using Bash or Linux-native tools for remote management and discovery, alongside PowerShell instructions.
  • Document how to containerize ASP.NET apps hosted on Linux (if supported), or explicitly state limitations and roadmap for Linux parity.
  • Where possible, mention Linux alternatives to Windows tools (e.g., alternatives to Web Deploy, PowerShell remoting) for ASP.NET workloads.
GitHub Create Pull Request
Migrate Troubleshoot web apps migration issues ...ain/articles/migrate/troubleshoot-webapps-migration.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Missing Linux Example Windows First
Summary
The documentation page is heavily focused on troubleshooting migration issues for IIS-based web apps, which are Windows-centric. It repeatedly references Windows-specific tools and patterns, such as IIS, PowerShell, and Windows file system concepts, without mentioning Linux equivalents or providing troubleshooting steps for Linux-based web apps (e.g., Apache, Nginx). All examples and error codes are related to Windows environments, and there is no guidance for users migrating from Linux platforms.
Recommendations
  • Add troubleshooting sections for Linux-based web apps (e.g., Apache, Nginx) and their migration issues.
  • Include examples and error codes relevant to Linux environments, such as permissions, file system differences, and common migration pitfalls.
  • Provide parity in tooling references, such as Bash scripts or Linux-native migration tools, alongside PowerShell.
  • Explicitly state the scope of the documentation (e.g., 'Windows/IIS only') if Linux is not supported, or link to Linux-specific migration guidance.
  • Ensure that troubleshooting steps and recommendations are inclusive of both Windows and Linux scenarios, or clearly differentiate them.
GitHub Create Pull Request
Migrate Azure App Containerization ASP.NET; Containerization and migration of ASP.NET applications to Azure Kubernetes. ...ate/tutorial-app-containerization-aspnet-kubernetes.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation is heavily biased toward Windows environments for ASP.NET app containerization. All instructions, prerequisites, and tooling are Windows-centric, requiring Windows OS, PowerShell, and Microsoft Web Deploy. There are no Linux equivalents or examples for ASP.NET containerization, and all operational steps (installation, discovery, build, troubleshooting) assume Windows-only workflows. Linux is only mentioned in the context of Java/Tomcat apps, not ASP.NET.
Recommendations
  • Provide Linux-based instructions and tooling for ASP.NET app containerization, such as support for running the containerization tool on Linux hosts.
  • Include Linux shell (bash) examples alongside PowerShell commands where possible.
  • Document how to containerize ASP.NET Core apps running on Linux, or clarify Windows-only support for ASP.NET Framework.
  • Offer alternatives to Microsoft Web Deploy for Linux environments, or note cross-platform deployment strategies.
  • Explicitly state platform limitations and future roadmap for Linux parity in ASP.NET containerization.
  • Add troubleshooting and artifact location instructions for Linux hosts if/when supported.
GitHub Create Pull Request
Migrate Containerization and migration of Java web applications to Azure App Service. ...rate/tutorial-app-containerization-java-app-service.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation exhibits a strong Windows bias. The Azure Migrate: App Containerization tool is only installable and runnable on Windows machines, with explicit requirements for Windows Server or Windows 10. All installation and usage instructions (including PowerShell commands) are Windows-specific, with no mention of Linux or cross-platform alternatives. Troubleshooting steps reference Windows file paths, and there are no examples or guidance for Linux users wishing to run the tool natively. The documentation assumes Windows as the default platform for orchestration, even though the applications being containerized are Java web apps running on Linux servers.
Recommendations
  • Provide a Linux-native version of the Azure Migrate: App Containerization tool, or document how to run it on Linux (e.g., via Wine, containers, or a VM).
  • Include installation and usage instructions for Linux environments, with equivalent shell commands (e.g., bash) and file paths.
  • Offer troubleshooting guidance for Linux users, including log file locations and common issues.
  • Clarify platform limitations early in the documentation and suggest alternatives for users who do not have access to Windows machines.
  • If the tool is fundamentally Windows-only, consider providing a web-based or containerized version to improve accessibility for Linux users.
GitHub Create Pull Request
Migrate Assess ASP.NET/Java web apps for migration to Azure Kubernetes Service ...ob/main/articles/migrate/tutorial-assess-aspnet-aks.md
High Priority View Details →
Scanned: 2026-01-10 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 in several ways: Windows node pools are emphasized for ASP.NET apps, with no mention of Linux node pools or Linux containerization for .NET Core apps. The 'Optimize Windows Dockerfiles' link is featured in 'Next steps', while no equivalent Linux Dockerfile guidance is provided. There are no Linux-specific examples, tools, or migration patterns discussed, and the assessment process assumes Windows as the default for ASP.NET workloads, omitting Linux migration scenarios.
Recommendations
  • Add guidance and examples for migrating ASP.NET Core apps to Linux node pools on AKS, including Linux Dockerfile optimization.
  • Include links to Linux container best practices and Dockerfile optimization in the 'Next steps' section.
  • Clarify when Windows node pools are required (e.g., for ASP.NET Framework only), and highlight Linux as the preferred/default for .NET Core workloads.
  • Provide parity in screenshots and instructions for Linux-based assessments and deployments.
  • Mention and link to Linux migration tools and documentation where relevant.
GitHub Create Pull Request
← Previous Page 9 of 37 Next →