Migrate

394
Total Pages
295
Linux-Friendly Pages
99
Pages with Bias
25.1%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

218 issues found
Showing 126-150 of 218 flagged pages
Migrate Troubleshoot network connectivity issues | Microsoft Docs .../articles/migrate/troubleshoot-network-connectivity.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
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) exclusively in Windows syntax, including Windows-style command prompts (e.g., 'c:\ >nslookup'), and referencing PowerShell-specific tools like Test-NetConnection without offering equivalent Linux/macOS commands or guidance. Screenshots and instructions are oriented toward Windows environments, and Linux troubleshooting steps are absent, making it less accessible for users operating on Linux or macOS appliances.
Recommendations
  • Include Linux/macOS equivalents for all command-line examples, such as using 'dig' or 'host' for DNS resolution and 'nc' or 'telnet' for connectivity checks.
  • Provide explicit instructions and sample outputs for Linux/macOS terminals alongside Windows/PowerShell examples.
  • Clarify that steps apply to both Windows and Linux appliances, and note any platform-specific differences.
  • Add troubleshooting guidance for Linux-based appliances, including how to edit /etc/hosts and check DNS settings.
  • Where PowerShell commands are mentioned (e.g., Test-NetConnection), offer alternatives for Linux (e.g., 'nc -zv <host> <port>').
GitHub Create Pull Request
Migrate Troubleshoot ongoing server discovery, software inventory, and SQL discovery ...s/blob/main/articles/migrate/troubleshoot-discovery.md
Medium Priority View Details →
Scanned: 2026-01-12 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 page demonstrates a notable Windows bias. Troubleshooting steps and error remediations frequently reference Windows-specific tools (PowerShell, WMI, Windows environment variables, IIS), and provide detailed instructions for Windows scenarios. PowerShell commands are shown extensively, often with minimal or less detailed Linux equivalents. In several places, Linux troubleshooting is limited to generic SSH connectivity checks or basic 'ls' commands, while Windows instructions are more comprehensive. Some remediation steps (e.g., for WMI, UAC, environment variables) are Windows-only, with no Linux alternatives. Windows examples and tools are often presented first or exclusively.
Recommendations
  • Provide equivalent Linux troubleshooting steps for each error, especially where Windows-specific tools (PowerShell, WMI, IIS) are referenced.
  • Include Linux command examples for validation and remediation, such as using systemctl, journalctl, or other relevant Linux utilities.
  • Expand Linux error documentation beyond SSH connectivity to cover common Linux-specific issues (e.g., permissions, SELinux, package installation).
  • Ensure Linux instructions are as detailed as Windows instructions, including step-by-step guides for credential validation, environment configuration, and service management.
  • Where possible, present Windows and Linux examples side-by-side, or alternate which platform is shown first.
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
Medium Priority View Details →
Scanned: 2026-01-12 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 a moderate Windows bias, especially in the ASP.NET assessment flow. It assumes ASP.NET apps require Windows node pools in AKS, references Windows Dockerfiles, and does not provide parity for Linux-based ASP.NET Core scenarios. Linux tools, patterns, or examples are not mentioned, and Windows-specific requirements (such as node pools) are presented as defaults. Java guidance is more neutral, but the ASP.NET path is Windows-centric.
Recommendations
  • Explicitly clarify when Windows node pools are required (e.g., only for ASP.NET Framework, not ASP.NET Core).
  • Add guidance and examples for Linux-based ASP.NET Core apps, including Linux node pool recommendations and Dockerfile optimization links.
  • Provide links to Linux container best practices and Dockerfile optimization for Linux containers.
  • Ensure that assessment flows and screenshots cover both Windows and Linux scenarios where applicable.
  • Avoid presenting Windows requirements as defaults unless strictly necessary; highlight Linux options equally.
GitHub Create Pull Request
Migrate Tutorial to assess SQL instances for migration to SQL Server on Azure VM, Azure SQL Managed Instance and Azure SQL Database ...docs/blob/main/articles/migrate/tutorial-assess-sql.md
Medium Priority View Details →
Scanned: 2026-01-12 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 a moderate Windows bias. Key high availability and disaster recovery sections reference Windows Server Failover Clusters and Cloud Witness, with links and recommendations focused on Windows-specific technologies. There are no equivalent Linux clustering or HA/DR examples, nor are Linux-specific tools or patterns mentioned. The documentation also references Azure Hybrid Benefit for Windows Server and SQL Server licenses before mentioning Enterprise Linux subscriptions (RHEL/SLES), and links for performance guidelines point to Windows-specific resources. No explicit Linux or cross-platform examples are provided for critical migration or assessment steps.
Recommendations
  • Add Linux-specific examples and guidance for SQL Server deployments, including clustering and HA/DR scenarios (e.g., Pacemaker, Corosync, or Linux witness options).
  • Include links to Azure SQL performance guidelines for Linux-based VMs, not just Windows.
  • Clarify parity and differences in Azure Hybrid Benefit for Linux and Windows, and provide step-by-step instructions for both.
  • Ensure that any referenced tools or scripts (e.g., for discovery, assessment, migration) are available and documented for Linux environments.
  • Present Windows and Linux options side-by-side, or indicate when a feature is Windows-only.
GitHub Create Pull Request
Migrate Discover servers on Hyper-V with Azure Migrate Discovery and assessment ...lob/main/articles/migrate/tutorial-discover-hyper-v.md
Medium Priority View Details →
Scanned: 2026-01-12 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 oriented toward Windows environments, specifically Windows Server and Hyper-V. All examples, scripts, and tooling references are Windows-centric (e.g., PowerShell, WinRM, Hyper-V Manager, CertUtil), with no Linux/macOS equivalents or alternatives provided. Steps for appliance setup, host preparation, and credential delegation rely on Windows tools and patterns. While Linux servers are mentioned as supported for discovery, there are no Linux-specific instructions, examples, or troubleshooting guidance for users running the appliance or managing hosts from Linux/macOS platforms.
Recommendations
  • Provide Linux/macOS equivalents for key steps, such as validating script integrity (e.g., using sha256sum), managing virtual machines (e.g., via libvirt/virt-manager), and credential delegation.
  • Include Linux/macOS command-line examples alongside PowerShell and Windows tools.
  • Clarify whether the Azure Migrate appliance can be managed or set up from Linux/macOS hosts, and provide instructions if possible.
  • Add troubleshooting guidance for Linux users, especially around network connectivity, credential management, and SSH key formats.
  • Ensure parity in the order and prominence of Linux and Windows instructions/examples.
GitHub Create Pull Request
Migrate Discover servers running in a VMware environment with Azure Migrate Discovery and assessment ...blob/main/articles/migrate/tutorial-discover-vmware.md
Medium Priority View Details →
Scanned: 2026-01-12 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 exhibits a moderate Windows bias. Windows-specific tools (PowerShell) and patterns are mentioned before Linux equivalents, and some critical setup steps (such as appliance deployment via PowerShell) are described only for Windows Server. The VDDK installation path is given as a Windows filesystem path, with no Linux alternative. While Linux is referenced as supported, examples and instructions for Linux users (e.g., deploying the appliance on a Linux VM, VDDK installation on Linux, or Linux-based troubleshooting) are missing. Windows authentication and tooling are described in detail, whereas Linux SSH key-based authentication is mentioned but not elaborated with step-by-step guidance.
Recommendations
  • Provide explicit instructions and examples for deploying the Azure Migrate appliance on Linux VMs, including how to use the OVA template and/or script on Linux.
  • Include Linux-specific steps for installing and configuring the VMware VDDK, with correct Linux filesystem paths and commands.
  • Offer parity in troubleshooting and credential setup examples for Linux (e.g., SSH key generation, permissions, validation).
  • Ensure that any PowerShell-based instructions have Bash or shell script equivalents for Linux users.
  • List Linux examples alongside Windows examples, not after or omitted.
GitHub Create Pull Request
Migrate Discover, assess, and migrate Google Cloud Platform (GCP) VMs to Azure ...icles/migrate/tutorial-migrate-gcp-virtual-machines.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation exhibits a Windows bias in several key areas. The replication appliance required for migration must be deployed on a Windows Server (2012 R2 or 2016), with no mention of Linux support for this critical component. Installation and setup instructions for the appliance are exclusively Windows-focused. While Linux VM preparation and agent installation are covered, the overall workflow and tooling are centered around Windows environments, and Windows-specific troubleshooting is included. Linux users can complete the migration, but must rely on Windows infrastructure for the appliance, creating friction and dependency.
Recommendations
  • Provide options or guidance for deploying the replication appliance on Linux-based systems, if supported, or clarify platform limitations.
  • Include Linux-first or Linux-parity examples for appliance setup, not just for agent installation.
  • Explicitly state platform requirements and limitations at the beginning of the documentation.
  • Offer alternative migration approaches for organizations without Windows infrastructure.
  • Ensure troubleshooting and post-migration sections include Linux-specific guidance, not just Windows activation issues.
GitHub Create Pull Request
Migrate Migrate VMware vSphere VMs with agent-based the Migration and modernization tool ...main/articles/migrate/tutorial-migrate-vmware-agent.md
Medium Priority View Details →
Scanned: 2026-01-12 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 a moderate Windows bias. Critical setup steps, such as deploying the replication appliance, are described as creating a Windows Server 2016 VM, with no mention of Linux-based alternatives. Registry edits for Mobility service installation are detailed only for Windows, while Linux instructions are minimal and lack example commands. PowerShell is referenced as the manual setup method for the replication appliance, with no Linux shell or automation alternatives provided. Throughout, Windows-specific tools and troubleshooting steps are mentioned first or exclusively, and Linux guidance is often brief or missing.
Recommendations
  • Provide explicit instructions and example commands for Linux VMs, including shell commands for Mobility service installation and troubleshooting.
  • Clarify whether the replication appliance can be deployed on Linux, or state its Windows-only requirement upfront.
  • Offer Linux-based alternatives to PowerShell scripts for appliance setup, such as Bash or Python scripts.
  • Ensure parity in troubleshooting and post-migration steps, including activation and agent installation guidance for Linux VMs.
  • Present Windows and Linux instructions side-by-side where possible, rather than focusing on Windows first.
GitHub Create Pull Request
Migrate Discover physical servers with Azure Migrate discovery and assessment ...ob/main/articles/migrate/tutorial-discover-physical.md
Medium Priority View Details →
Scanned: 2026-01-12 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 moderate Windows bias. Windows server setup instructions are presented first and in greater detail, including specific group memberships, UAC filtering, and links to Windows-specific troubleshooting. The installer script section exclusively references PowerShell and Windows tools (IIS, registry, Windows Activation Service), with no mention of Linux installation or alternatives. Linux instructions are present and reasonably detailed for credential setup, but there is no guidance for running the appliance or installer on Linux, nor examples for Linux-based appliance deployment. All screenshots and step-by-step instructions assume a Windows environment.
Recommendations
  • Provide explicit instructions and examples for deploying and running the Azure Migrate appliance on Linux servers, if supported.
  • If the appliance is Windows-only, state this clearly and offer guidance for Linux users (e.g., using a Windows VM as a jump host).
  • Include Linux-first or parallel examples for credential setup, troubleshooting, and server discovery steps.
  • Balance the order and detail of Windows and Linux sections to avoid Windows-first presentation.
  • Clarify which steps are OS-specific and which are universal, possibly with separate sub-sections for each OS.
GitHub Create Pull Request
Migrate Discover, assess, and migrate Amazon Web Services (AWS) EC2 VMs to Azure ...icles/migrate/tutorial-migrate-aws-virtual-machines.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a Windows bias in several key areas. The replication appliance required for migration must run on Windows Server (2012 R2 or 2016), with no mention of Linux support for this role. Instructions for downloading and installing the appliance are exclusively for Windows. Windows-specific tools (WinRM, WMI) are mentioned before Linux equivalents, and screenshots and step-by-step guides focus on Windows environments. While Linux migration steps are included (such as enabling SSH password authentication and installing the Mobility agent), the overall workflow and tooling are centered around Windows, and Linux users must adapt to a Windows-based appliance for migration.
Recommendations
  • Provide explicit guidance for Linux users, including whether a Linux-based replication appliance is supported or alternative approaches if not.
  • If the replication appliance must be Windows-only, clearly state this limitation early in the documentation and suggest workarounds for Linux-only environments (e.g., using a temporary Windows VM).
  • Offer Linux-first or Linux-parity examples for key steps (e.g., preparing the appliance, installing agents, troubleshooting).
  • Balance the order of instructions and examples so that Linux and Windows users are equally represented.
  • Include a table summarizing OS-specific requirements and limitations for migration.
GitHub Create Pull Request
Migrate Migrate machines as physical servers to Azure with Azure Migrate and Modernize .../migrate/tutorial-migrate-physical-virtual-machines.md
Medium Priority View Details →
Scanned: 2026-01-12 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 moderate Windows bias. Windows-specific tools (e.g., PowerShell scripts, registry policies, SetupDiag utility) are referenced frequently, often without Linux equivalents or with Linux instructions relegated to brief mentions. Key setup steps for the replication appliance and agent installation are described primarily using Windows-centric methods (PowerShell, Windows Server), with minimal detail for Linux alternatives. Registry and Group Policy checks are Windows-only. OS upgrade instructions and troubleshooting focus on Windows. Linux is mentioned, but examples and step-by-step guidance are sparse or absent.
Recommendations
  • Provide explicit Linux setup instructions for the replication appliance, including supported distributions and required commands.
  • Include Linux shell script equivalents for PowerShell-based installation and configuration steps.
  • Document Linux-specific prerequisites, troubleshooting, and agent installation workflows in detail.
  • Add parity for OS upgrade and error handling for Linux VMs, including references to relevant Linux tools/logs.
  • Ensure all steps referencing Windows tools (e.g., registry, SetupDiag) are paired with Linux alternatives or clearly state their applicability.
GitHub Create Pull Request
Migrate Migrate VMware VMs agentless the Migration and modernization tool .../blob/main/articles/migrate/tutorial-migrate-vmware.md
Medium Priority View Details →
Scanned: 2026-01-12 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 page demonstrates a notable Windows bias, especially in the 'Track and monitor' section, where all command-line examples use PowerShell and reference Windows/Windows PowerShell explicitly. There are no Bash, Linux CLI, or cross-platform alternatives provided for monitoring migration status, and Windows tooling (e.g., SetupDiag, Windows activation troubleshooting) is mentioned without Linux equivalents. Windows-specific options (like OS upgrade) are highlighted, and Windows terminology appears before Linux in several places.
Recommendations
  • Provide equivalent Bash or Azure CLI examples for monitoring migration status, especially for Linux/macOS users.
  • Clarify that Azure Cloud Shell supports both Bash and PowerShell, and show how to use Bash for migration monitoring.
  • Mention Linux troubleshooting steps and tools where Windows-specific ones (e.g., SetupDiag, activation) are referenced.
  • Ensure parity in examples and instructions for both Windows and Linux VMs, including OS upgrade and agent installation.
  • Where possible, use neutral terminology (e.g., 'any machine with Azure CLI/Cloud Shell access') rather than 'Windows PC'.
GitHub Create Pull Request
Migrate Tutorial to assess web apps for migration ...lob/main/articles/migrate/create-web-app-assessment.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. It references Windows-centric technologies (ASP.NET, Windows Dockerfiles, Windows Server licensing) and optimization guides for Windows containers, while Linux equivalents (e.g., Linux Dockerfiles, Linux web frameworks) are not mentioned or linked. Examples and sizing details are provided for ASP.NET and Tomcat, but the focus is on Windows environments and tools, with Linux scenarios not explicitly addressed.
Recommendations
  • Include examples and guidance for Linux-based web apps (e.g., Node.js, PHP, Python, Ruby) in the assessment process.
  • Add links and references to optimizing Linux Dockerfiles and managing Linux containers on AKS.
  • Clarify how the assessment applies to Linux environments, including licensing, sizing, and migration specifics.
  • Provide parity in best practices documentation for both Windows and Linux workloads on AKS and App Service.
  • Mention Linux server licensing and cost considerations where Windows Server licensing is discussed.
GitHub Create Pull Request
Migrate Create project ...zure-docs/blob/main/articles/migrate/create-project.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page primarily provides instructions for creating Azure Migrate projects via the Azure portal and REST API, which are cross-platform. However, in the section describing agentless dependency analysis enhancements, it instructs users to install the Azure CLI and then explicitly directs them to open PowerShell as Administrator to run CLI commands, without mentioning Linux/macOS terminals or shell alternatives. This creates a Windows-first impression and may confuse non-Windows users. No Linux/macOS-specific examples or instructions are provided, and PowerShell is referenced as the default shell for CLI usage.
Recommendations
  • Explicitly mention that Azure CLI commands can be run in Bash, zsh, or other shells on Linux/macOS, not just PowerShell.
  • Provide example CLI commands in both Windows (PowerShell) and Linux/macOS (Bash) contexts.
  • Avoid language that assumes PowerShell is the default shell for all users.
  • Add notes or links for installing and using Azure CLI on Linux/macOS.
  • Where administrator privileges are required, clarify the equivalent steps for Linux/macOS (e.g., using sudo).
GitHub Create Pull Request
Migrate Customer intent: As a systems administrator, I want to download the latest version of VMware, so that I can ensure my infrastructure is up to date and secure. .../main/articles/migrate/includes/public-cloud-vmware.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Missing Linux Example Windows First
Summary
The documentation provides a download link for VMware via a Microsoft URL (go.microsoft.com), which may suggest a Windows-centric approach. There are no instructions or examples for downloading or verifying the file on Linux or macOS systems, nor are any Linux-specific tools or commands mentioned.
Recommendations
  • Include Linux/macOS-specific download instructions, such as using wget or curl.
  • Provide SHA256 verification steps for Linux/macOS (e.g., using sha256sum or shasum).
  • Clarify whether the download link is platform-agnostic or Windows-specific.
  • If the product is cross-platform, mention any platform-specific installation steps.
GitHub Create Pull Request
Migrate Discover software inventory on on-premises servers with Azure Migrate .../main/articles/migrate/how-to-discover-applications.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example Powershell Heavy
Summary
The documentation demonstrates a moderate Windows bias. Windows terminology, tools, and patterns (such as Windows credentials, guest user accounts, and Windows-specific roles/features) are mentioned first or exclusively in several sections. Examples and instructions for Windows (e.g., SQL Server, File Server, IIS/ASP.NET) are detailed, while Linux equivalents are either less detailed or missing (e.g., File Server discovery is Windows-only, no Linux web server discovery steps, no Linux-specific credential/role guidance). Linux is referenced, but with less depth and fewer examples, creating friction for non-Windows users.
Recommendations
  • Provide Linux-specific examples and step-by-step instructions for all major discovery scenarios (e.g., Linux file servers, Linux web servers such as Apache/Nginx, Linux database servers).
  • Include credential and permission requirements for Linux in equal detail to Windows (e.g., specify required Linux user/group memberships, sudo/non-sudo requirements, and sample commands for credential setup).
  • Add explicit guidance for Linux server roles/features discovery, analogous to the Windows 'Roles and features' tab.
  • Ensure that Linux tools and patterns (such as SSH, systemd services, package managers) are mentioned alongside or before Windows equivalents where appropriate.
  • Where Windows tools/utilities (e.g., PowerShell, SCCM) are referenced, provide Linux alternatives (e.g., Bash scripts, Ansible, Linux patch management tools).
  • Clarify any limitations or differences in support for Linux servers (e.g., if Linux file server discovery is not supported, state this clearly and provide roadmap or alternatives).
GitHub Create Pull Request
Migrate Automate migration of machines in Azure Migrate .../blob/main/articles/migrate/how-to-migrate-at-scale.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page exclusively references PowerShell scripts and provides only .ps1 script examples for automating VM migration in Azure Migrate. There is no mention of Bash, shell, or cross-platform alternatives, nor are Linux/macOS scripting environments or tools discussed. The guidance and downloadable samples are Windows-centric, creating friction for users on Linux or macOS who may not have access to PowerShell or prefer native tools.
Recommendations
  • Provide equivalent Bash or shell script samples for Linux/macOS users.
  • Explicitly mention PowerShell Core compatibility and how to run scripts on Linux/macOS, if applicable.
  • Include instructions for installing and using Azure CLI for migration tasks as an alternative to PowerShell.
  • Reorder examples or add parallel sections so Linux/macOS approaches are presented alongside Windows ones.
  • Clarify any platform-specific limitations or requirements for the scripts.
GitHub Create Pull Request
Migrate Support for physical discovery and assessment in Azure Migrate and Modernize ...in/articles/migrate/migrate-support-matrix-physical.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
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 moderate Windows bias. Windows tools and concepts (PowerShell, WinRM, WMI, Windows authentication, IIS, SQL Server on Windows) are described in detail, often with explicit instructions, scripts, and links. Linux support is mentioned, but Linux-specific examples, troubleshooting, and parity in features (e.g., SQL Server and ASP.NET web app discovery) are missing or less detailed. Windows terminology and tools are often listed first or exclusively, with Linux equivalents referenced briefly or as secondary.
Recommendations
  • Provide Linux-specific setup and troubleshooting examples, especially for appliance deployment and connectivity (e.g., sample SSH configuration, firewall rules, SELinux/AppArmor notes).
  • Include Linux-first or parallel examples for critical tasks (e.g., how to set up the appliance using Bash scripts or Ansible, not just PowerShell).
  • Clarify feature parity and limitations for Linux (e.g., explicitly state why SQL Server and ASP.NET web app discovery are not supported on Linux, and suggest alternatives or workarounds).
  • Add Linux command-line snippets for common operations (e.g., software inventory, dependency analysis) and reference Linux tools before or alongside Windows tools.
  • Balance the order of presentation so Linux and Windows instructions/examples are given equal prominence.
  • Expand troubleshooting and requirements sections for Linux environments, including common issues (permissions, package managers, SSH configuration).
GitHub Create Pull Request
Migrate Support for Hyper-V assessment in Azure Migrate and Modernize ...ain/articles/migrate/migrate-support-matrix-hyper-v.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
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, with Windows Server versions and PowerShell remoting consistently mentioned first or exclusively. Many requirements and examples (such as permissions, authentication, and sample scripts) are Windows-centric, with little to no equivalent Linux guidance. SQL Server discovery and ASP.NET web app discovery are not supported for Linux, and most technical instructions and examples are tailored for Windows users. Linux support is mentioned but often as an afterthought, and some features are outright unavailable for Linux servers.
Recommendations
  • Provide Linux-first or Linux-parity examples and instructions where possible, especially for permissions, authentication, and appliance deployment.
  • Explicitly document Linux limitations and offer alternative workflows or tools for Linux users.
  • Include sample scripts and step-by-step instructions for Linux environments where Windows scripts are provided.
  • Clarify which features are Windows-only and suggest Linux-compatible alternatives or workarounds.
  • Ensure that Linux requirements are described with equal detail and prominence as Windows requirements.
GitHub Create Pull Request
Migrate Migrate servers to Azure using Private Link through agent-based replications ...igrate-servers-to-azure-using-private-link-agent-based.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. Windows Server and Windows-specific licensing (Azure Hybrid Benefit) are mentioned explicitly, while Linux-specific scenarios, tools, or instructions are not addressed. Examples, terminology, and benefit options prioritize Windows, and there is no guidance for Linux-specific migration steps, agent installation, or troubleshooting. The documentation assumes familiarity with Windows-centric concepts and omits parity for Linux/macOS users.
Recommendations
  • Add explicit instructions and examples for migrating Linux servers, including agent installation and troubleshooting steps for common Linux distributions.
  • Include Linux-specific considerations for DNS configuration, service dependencies, and permissions.
  • Clarify whether the Mobility Service agent and replication appliance support Linux, and provide links to Linux documentation.
  • Mention licensing and benefit options relevant to Linux (e.g., RHEL, SUSE, Ubuntu) alongside Windows Hybrid Benefit.
  • Ensure that all steps, especially those involving manual installation or configuration, have Linux equivalents or note any limitations.
GitHub Create Pull Request
Migrate Support for physical server migration in Azure Migrate and Modernize ...s/migrate/migrate-support-matrix-physical-migration.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation page demonstrates a Windows bias by referencing Windows Server as the default OS for the replication appliance, listing Windows connection steps before Linux, and describing Windows-specific tools and configurations (e.g., RDP, Windows Firewall) in more detail than their Linux equivalents. Linux instructions are present but less detailed and appear after Windows instructions.
Recommendations
  • Provide equal detail and step-by-step instructions for Linux connection and firewall configuration, similar to the Windows RDP section.
  • Offer examples of setting up the replication appliance on Linux-based VMs or clarify if Windows Server is strictly required.
  • List Linux connection instructions before or alongside Windows instructions to avoid 'Windows first' ordering.
  • Include references to Linux tools (e.g., iptables, firewalld) and SSH configuration commands.
  • Clarify any limitations or requirements for Linux appliances, not just Windows.
GitHub Create Pull Request
Migrate Agent-based Migration in the Migration and Modernization Tool ...articles/migrate/agent-based-migration-architecture.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
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 referencing Windows-specific tools (e.g., registry keys, MMC snap-in, Windows file paths) for managing and configuring agent-based migration. There are no Linux/macOS equivalents or examples provided for key operations such as throttling bandwidth or antivirus exclusions. Windows terminology and instructions are presented exclusively or before any mention of Linux, creating friction for non-Windows users.
Recommendations
  • Provide Linux/macOS equivalents for all configuration steps, such as bandwidth throttling (e.g., systemd, tc, or other Linux network management tools).
  • Include Linux-specific file paths for antivirus exclusions and clarify how to locate and install the Mobility service on Linux servers.
  • Offer command-line examples for Linux (bash, system utilities) alongside Windows examples (registry, MMC).
  • Explicitly state platform differences and link to platform-specific guides where available.
  • Ensure that instructions for manual installation, monitoring, and troubleshooting cover Linux and macOS environments.
GitHub Create Pull Request
Migrate Enhancing Web App Assessment With Code Scan Reports for Azure Migration ...lob/main/articles/migrate/add-copilot-code-insights.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing Windows-specific instructions and links, especially in the AppCAT CLI section. Java assessment instructions explicitly point to Windows tabs, and there are no explicit Linux/macOS examples or commands shown for installing or running AppCAT or related tools. The documentation assumes familiarity with Windows environments and does not provide parity for Linux/macOS users.
Recommendations
  • Add explicit instructions and examples for installing and running AppCAT CLI on Linux and macOS, including shell commands.
  • Update links to reference both Windows and Linux/macOS tabs where available.
  • Include screenshots or terminal outputs from Linux/macOS environments.
  • Clarify any platform-specific requirements or limitations for the tools mentioned.
  • Ensure troubleshooting steps cover Linux/macOS scenarios (e.g., file permissions, zip creation commands).
GitHub Create Pull Request
Migrate Questions about assessments in Azure Migrate ...icles/migrate/common-questions-discovery-assessment.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page for Azure Migrate assessments demonstrates a moderate Windows bias. Throughout the article, examples and instructions frequently mention Windows-centric technologies (Hyper-V, SQL Server, IIS), and discovery/assessment scenarios are described primarily for VMware, Hyper-V, and 'Physical/Bare metal' servers, but do not explicitly address Linux-specific scenarios or provide parity for Linux tools and environments. The documentation references Windows features (e.g., dynamic memory in Hyper-V, IIS web server) without mentioning Linux equivalents (e.g., KVM/QEMU, Apache/Nginx). There are no Linux command-line or tool examples, and troubleshooting steps do not consider Linux-specific performance counters or agent issues. The assessment types and readiness checks focus on Windows workloads (SQL Server, ASP.NET/IIS), with no mention of Linux workloads (e.g., MySQL, Apache, Tomcat).
Recommendations
  • Include explicit examples and instructions for Linux-based servers and workloads (e.g., Ubuntu, CentOS, RHEL).
  • Add troubleshooting steps and performance counter guidance for Linux environments (e.g., how to check agent status, collect memory/CPU metrics on Linux).
  • Mention Linux web servers (Apache, Nginx) and application stacks (e.g., Java/Tomcat, PHP) in assessment types and readiness checks.
  • Provide parity in migration scenarios for Linux workloads, including database options (MySQL, PostgreSQL) and application servers.
  • Ensure that documentation for discovery and assessment covers Linux-specific nuances (e.g., SSH-based discovery, Linux authentication, SELinux/AppArmor considerations).
GitHub Create Pull Request
Migrate Set Up Least Privileged Accounts ...les/migrate/best-practices-least-privileged-account.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
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 moderate Windows bias. Windows-specific instructions, tools, and examples (such as WMI Control, WinRM, and SQL Server authentication) are often presented first or in greater detail than their Linux counterparts. Windows procedures are described step-by-step with GUI references, while Linux instructions are more concise and command-line focused. SQL Server discovery is covered extensively with Windows authentication examples, whereas MySQL (more common on Linux) receives less detailed coverage. Some sections (e.g., Hyper-V) are inherently Windows-centric, but Linux discovery steps are present and reasonably described.
Recommendations
  • Present Linux and Windows instructions in parallel, with equal detail and prominence.
  • Provide Linux-specific GUI or command-line examples where Windows GUI steps are given (e.g., for permissions).
  • Expand Linux database discovery instructions, including examples for PostgreSQL and other common Linux databases.
  • Ensure Linux commands are explained as thoroughly as Windows steps (e.g., add screenshots or step-by-step guides for Linux permissions).
  • Include troubleshooting steps for Linux environments similar to those provided for Windows.
  • Avoid always listing Windows examples first; alternate or group by OS.
GitHub Create Pull Request
← Previous Page 6 of 9 Next →