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 51-75 of 218 flagged pages
Migrate Discover servers on GCP instances with Azure Migrate Discovery and assessment ...cs/blob/main/articles/migrate/tutorial-discover-gcp.md
High Priority View Details →
Scanned: 2026-01-11 06:20
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 notable Windows bias. The Azure Migrate appliance is described as requiring Windows Server 2019 or 2022, with no mention of Linux-based appliance deployment. All setup and installation steps rely on PowerShell scripts and Windows-specific tools (IIS, Windows Activation Service, registry edits), with no Linux equivalents or alternatives provided. Examples and instructions for running the installer are exclusively in PowerShell, and the appliance's file paths are Windows-style. Linux server discovery is supported, but only as a target for assessment, not as a platform for running the appliance. There are no Linux shell or cross-platform instructions for appliance setup.
Recommendations
  • Provide instructions and support for deploying the Azure Migrate appliance on Linux servers, or clarify if this is not possible.
  • Include Linux shell (bash) equivalents for installation, configuration, and troubleshooting steps.
  • Offer cross-platform installer scripts or containerized appliance options (e.g., Docker) to enable Linux/macOS users to participate fully.
  • Document Linux file paths and troubleshooting locations alongside Windows paths.
  • Present Linux examples and instructions with equal prominence to Windows, not only as targets but also as possible hosts for the appliance.
GitHub Create Pull Request
Migrate Discover physical servers with Azure Migrate discovery and assessment ...ob/main/articles/migrate/tutorial-discover-physical.md
High Priority View Details →
Scanned: 2026-01-11 06:20
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 notable Windows bias. Windows server setup instructions are presented first and in greater detail, including multiple account setup options, troubleshooting steps, and links to Windows-specific resources. The installer script section is entirely Windows/PowerShell-centric, with no mention of Linux or cross-platform alternatives for running or hosting the Azure Migrate appliance. Windows tools and patterns (PowerShell, WinRM, IIS, registry edits) are described in depth, while Linux instructions are limited to credential setup and sudoers configuration, with no guidance on running the appliance natively on Linux. Linux users are implicitly required to use a Windows host for the appliance, which is not stated directly but is clear from the instructions.
Recommendations
  • Explicitly state whether the Azure Migrate appliance can be hosted on Linux, and if not, clarify the requirement up front.
  • If Linux hosting is possible, provide equivalent installer instructions for Linux, including shell commands and troubleshooting steps.
  • Offer parity in example depth: include Linux troubleshooting, supported tools, and links to Linux-specific resources.
  • If only Windows hosting is supported, suggest alternatives for Linux-only environments (e.g., using a Windows VM for the appliance) and document limitations.
  • Present Windows and Linux instructions in parallel sections, rather than Windows-first ordering.
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
High 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 exhibits a Windows bias in several ways: Windows Server is the only supported OS for the replication appliance, with no mention of Linux alternatives; Windows-specific tools and ports (WinRM, WMI) are discussed before Linux equivalents; and critical steps (such as running the replication appliance) require Windows, making it impossible for Linux-only users to complete the migration. While Linux VM migration is supported, the infrastructure setup is Windows-centric.
Recommendations
  • Provide support and instructions for deploying the replication appliance on Linux (if possible), or clarify why Windows is required.
  • Offer Linux-first or parallel examples for all steps, especially for infrastructure setup and agent installation.
  • Explicitly state OS limitations early in the document so Linux users can plan accordingly.
  • Include troubleshooting and best practices sections tailored for Linux users.
  • Where Windows tools (WinRM, WMI) are mentioned, provide equivalent Linux commands and context side-by-side.
GitHub Create Pull Request
Migrate Discover, assess, and migrate Google Cloud Platform (GCP) VMs to Azure ...icles/migrate/tutorial-migrate-gcp-virtual-machines.md
High Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation exhibits a notable Windows bias, particularly in the replication appliance setup, which requires a Windows Server VM (2012 R2 or 2016) as the host. All appliance installation steps and screenshots are Windows-centric, with no mention of Linux alternatives for the replication appliance. While Linux VMs are supported as migration sources and Linux-specific instructions are provided for agent installation, the critical infrastructure (replication appliance) is Windows-only. Windows tools and patterns (e.g., WinRM, Windows firewall screenshots, Windows Server references) are mentioned first and exclusively in appliance setup sections.
Recommendations
  • Provide explicit guidance for deploying the replication appliance on Linux hosts, if supported, or clarify Windows-only requirements.
  • Include Linux-based examples and screenshots for firewall rule configuration and appliance installation steps.
  • Offer parity in troubleshooting sections, e.g., Linux-specific issues with appliance setup and agent registration.
  • Clearly state OS limitations for the replication appliance early in the documentation, and suggest alternatives for Linux-only environments.
  • Ensure that Linux instructions are presented with equal prominence and detail as Windows instructions throughout the guide.
GitHub Create Pull Request
Migrate Migrate Hyper-V VMs to Azure with the Migration and modernization tool ...blob/main/articles/migrate/tutorial-migrate-hyper-v.md
High Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First Missing Linux Example
Summary
The documentation is heavily biased toward Windows environments, specifically Hyper-V on Windows Server. All command-line examples use Windows paths and executables, and there is exclusive mention of Windows-specific tools (e.g., AzureSiteRecoveryProvider.exe, DRConfigurator.exe). There are no Linux or macOS equivalents, nor any guidance for users running Hyper-V on non-Windows platforms (which, while rare, is technically possible with nested virtualization or management from Linux/macOS). Troubleshooting and upgrade notes focus solely on Windows OS. The documentation assumes a Windows-centric workflow and does not address Linux/macOS users who may need to interact with the migration process, such as managing Hyper-V remotely or preparing VMs for migration.
Recommendations
  • Explicitly state that the migration process and tooling are Windows-only, if that is the case, and clarify any limitations for Linux/macOS users.
  • If possible, provide guidance or references for Linux/macOS users who need to manage Hyper-V hosts remotely (e.g., via PowerShell Core, Azure CLI, or RDP from non-Windows systems).
  • Include notes or links for Linux VM migration scenarios, or cross-reference Linux migration documentation for parity.
  • Where command-line instructions are given, clarify OS requirements and suggest alternatives for users who may be managing from non-Windows platforms.
  • Add troubleshooting and post-migration steps relevant to Linux VMs, if supported by the migration tool.
GitHub Create Pull Request
Migrate Create an Azure SQL assessment ...articles/migrate/how-to-create-azure-sql-assessment.md
Medium Priority View Details →
Scanned: 2026-01-23 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation is generally cross-platform, focusing on Azure SQL assessment via the Azure Migrate tool, which supports SQL Server on any OS. However, there are several instances where Windows-specific tools, features, or documentation are referenced first or exclusively (e.g., Windows Server Failover Clusters, Cloud Witness, and links to Windows-specific best practices). Linux equivalents or considerations are not mentioned, and the documentation assumes familiarity with Windows-based SQL Server deployments.
Recommendations
  • Wherever Windows-specific features (e.g., Cloud Witness, Windows Server Failover Clusters) are mentioned, add notes or links about Linux equivalents (e.g., Linux clustering, Pacemaker, or other HA/DR options for SQL Server on Linux).
  • When linking to best practices for SQL Server on Azure VMs, include both Windows and Linux documentation links.
  • Clarify in the 'Assessment settings' and 'High availability and disaster recovery properties' sections which options are Windows-only and provide guidance for Linux users.
  • Explicitly state that the assessment process applies to SQL Server on Linux as well, and note any limitations or differences.
  • Add examples or screenshots that include Linux-based SQL Server instances, if supported.
GitHub Create Pull Request
Migrate Tutorial to assess SQL instances in VMware VMs for migration to SQL Server on Azure VM, Azure SQL Managed Instance and Azure SQL Database ...ob/main/articles/migrate/tutorial-assess-sql-vmware.md
Medium Priority View Details →
Scanned: 2026-01-23 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation is generally platform-neutral, focusing on assessing SQL Server instances in VMware VMs for migration to Azure SQL solutions. However, there are subtle signs of Windows bias: references to Windows Server Failover Clusters and Cloud Witness are made without mentioning Linux equivalents, and links to performance guidelines and high availability features are Windows-centric. The order and examples tend to prioritize Windows scenarios, with no explicit Linux/SQL Server on Linux references or examples.
Recommendations
  • Include explicit guidance or notes for SQL Server instances running on Linux VMs, clarifying any differences in assessment or migration steps.
  • Where high availability and disaster recovery options are discussed, mention Linux clustering solutions (e.g., Pacemaker) and provide relevant Azure documentation links.
  • Add references or links to performance guidelines for SQL Server on Linux VMs in Azure.
  • Clarify if the Azure Migrate assessment tool supports SQL Server on Linux and, if so, provide examples or screenshots for Linux-based scenarios.
  • Ensure terminology and screenshots do not implicitly assume Windows-only environments unless the feature is truly Windows-specific.
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-23 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. While the tutorial is about assessing SQL Server instances for migration to Azure SQL, which is relevant to both Windows and Linux environments, several examples and references (such as cluster quorum configuration and Cloud Witness) are Windows-centric. The documentation refers to Windows Server Failover Clusters and provides links to Windows-specific best practices and tools, without mentioning Linux equivalents (e.g., Pacemaker clusters, Linux witness options). There are no explicit Linux/PowerShell/Bash command examples, nor guidance for Linux-based SQL Server deployments.
Recommendations
  • Add explicit guidance or notes for users assessing SQL Server on Linux, including any differences in assessment, migration, or high availability/disaster recovery options.
  • Include references or links to Linux-based SQL Server clustering and witness configuration documentation (e.g., Pacemaker, Linux witness options).
  • Where Windows-specific features (like Cloud Witness) are mentioned, clarify their applicability and provide Linux alternatives or state if not applicable.
  • Provide examples or screenshots that reflect Linux environments, where relevant (e.g., SQL Server on Linux VMs).
GitHub Create Pull Request
Migrate Set up agent-based dependency analysis in Azure Migrate ...es/migrate/how-to-create-group-machine-dependencies.md
Medium Priority View Details →
Scanned: 2026-01-13 22:27
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation generally presents Windows instructions and tools first, with more detailed steps and links for Windows (e.g., GUI and automation options like Configuration Manager, Intigua, and a dedicated script), while Linux instructions are briefer and less detailed. Windows-specific tools and patterns are mentioned (e.g., double-click installer, Configuration Manager), and Windows is often described before Linux in parallel sections. However, Linux is supported and instructions are present, so Linux users can complete the tasks.
Recommendations
  • Provide Linux installation instructions with equal detail, including automation and scripting options (e.g., sample bash scripts, package manager commands).
  • Mention Linux tools (e.g., Ansible, shell scripts) for agent deployment, similar to Windows automation options.
  • Present Windows and Linux instructions in parallel or side-by-side, or alternate which comes first, to avoid implicit prioritization.
  • Expand on Linux troubleshooting and supported distributions, matching the depth given to Windows.
  • Include screenshots or terminal output for Linux steps where applicable.
GitHub Create Pull Request
Migrate Support for VMware vSphere migration in Azure Migrate ...les/migrate/migrate-support-matrix-vmware-migration.md
Medium Priority View Details →
Scanned: 2026-01-13 22:27
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation demonstrates a moderate Windows bias. PowerShell is the only command-line interface mentioned for automation, and Windows-specific tools and configuration steps are referenced before Linux equivalents. In several sections, Windows instructions or requirements are listed first, and Linux details are sometimes less explicit or referenced as an afterthought. However, Linux support is documented, and most requirements are covered for both OS types.
Recommendations
  • Provide CLI automation examples using Bash or Azure CLI alongside PowerShell, especially for Linux/macOS users.
  • When referencing automation or scripting, mention cross-platform tools (e.g., Azure CLI, Bash scripts) before or alongside PowerShell.
  • List Linux and Windows instructions in parallel or alternate the order to avoid always putting Windows first.
  • Expand Linux-specific troubleshooting and preparation steps to match the detail given for Windows.
  • Where possible, clarify if any steps are Windows-only or provide Linux/macOS equivalents.
GitHub Create Pull Request
Migrate Set up agent-based dependency analysis in Azure Migrate ...es/migrate/how-to-create-group-machine-dependencies.md
Medium Priority View Details →
Scanned: 2026-01-13 21:56
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation generally presents Windows instructions and tools first, with more detailed, step-by-step guidance for Windows (including GUI and automation options), while Linux instructions are more terse and lack equivalent detail. Windows tools and workflows (e.g., double-click installers, Configuration Manager) are mentioned and linked, but Linux equivalents (such as package managers or automation scripts) are not. This creates friction for Linux users, who must infer steps or seek external resources.
Recommendations
  • Provide Linux installation instructions with equivalent detail to Windows, including common automation methods (e.g., using package managers like apt/yum, or shell scripts).
  • List Linux and Windows instructions in parallel or in separate, clearly labeled sections, rather than always presenting Windows first.
  • Include links to Linux-specific documentation for agent installation, troubleshooting, and supported distributions.
  • Mention and provide examples for Linux automation and configuration management tools (e.g., Ansible, shell scripts) where Windows tools like Configuration Manager are referenced.
  • Ensure screenshots and UI references are relevant for both platforms, or clarify when steps are platform-specific.
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-13 06:17
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 notable Windows bias. Windows tools and patterns (PowerShell, WinRM, WMI) are mentioned first and in more detail, with explicit requirements and links. PowerShell scripts are referenced for appliance setup, and Windows prerequisites are described extensively. Linux support is present, but Linux instructions are less detailed, often summarized as 'ensure SSH and commands are available.' SQL Server discovery and ASP.NET web app assessment are Windows-only, with Linux explicitly not supported. Example scripts and troubleshooting links are Windows-centric, with no Linux equivalents provided.
Recommendations
  • Provide Linux-first or parallel examples for appliance setup (e.g., bash scripts or manual steps for Linux).
  • Include troubleshooting and configuration links for Linux (e.g., SSH hardening, required package installation).
  • Expand Linux server requirements with explicit command-line examples and permission setup instructions.
  • Clarify limitations for Linux (e.g., SQL Server discovery, ASP.NET web apps) and suggest alternative approaches or roadmap for parity.
  • Balance the order of presentation: alternate Windows and Linux instructions, or group by OS.
  • Where PowerShell is referenced, offer Linux shell alternatives or note equivalent steps.
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-13 06:17
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias primarily in the AppCAT CLI instructions and linked references. Java assessment instructions explicitly reference Windows tabs and do not provide Linux/macOS equivalents or examples. .NET tool installation is shown using the dotnet CLI, which is cross-platform, but all referenced quickstarts and guides for Java projects are linked with '?tabs=windows', suggesting Windows-centric instructions. There are no explicit Linux/macOS commands, troubleshooting steps, or screenshots.
Recommendations
  • Provide explicit Linux/macOS instructions and examples for AppCAT CLI usage, including installation and report generation for both .NET and Java projects.
  • Ensure referenced quickstart and guide links include Linux/macOS tabs or sections, not just Windows.
  • Add troubleshooting guidance for Linux/macOS users (e.g., file permissions, CLI path issues).
  • Include screenshots or terminal examples from Linux/macOS environments alongside Windows ones.
GitHub Create Pull Request
Migrate Migrate VMware virtual machines to Azure with server-side encryption(SSE) and customer-managed keys(CMK) using the Migration and modernization tool ...es/migrate/how-to-migrate-vmware-vms-with-cmk-disks.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page exclusively uses Azure PowerShell for all command-line examples and instructions, with no mention of Azure CLI, Bash, or cross-platform alternatives. All sample commands, references, and linked tutorials are PowerShell-based, which is primarily associated with Windows environments. There are no Linux/macOS-specific instructions or examples, and the workflow assumes familiarity with PowerShell, potentially creating friction for users on non-Windows platforms.
Recommendations
  • Add equivalent Azure CLI (az) examples for all PowerShell commands, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Explicitly mention that Azure PowerShell can be installed and used on Linux/macOS, and provide installation instructions or links.
  • Reorder or parallelize examples so that CLI and PowerShell instructions are presented together, or allow users to select their preferred shell.
  • Include notes or sections for Linux/macOS users, highlighting any platform-specific considerations or differences.
  • Link to cross-platform documentation where possible, rather than Windows-specific guides.
GitHub Create Pull Request
Migrate VMware server discovery support in Azure Migrate and Modernize ...main/articles/migrate/migrate-support-matrix-vmware.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation demonstrates a notable Windows bias. Windows-specific tools (PowerShell, WMI) and patterns are mentioned more frequently and in greater detail than Linux equivalents. Windows requirements and examples (such as PowerShell, WMI, WinRM, Windows authentication, and SQL Server discovery) are presented first or exclusively, while Linux support is often limited or omitted (e.g., SQL Server and ASP.NET web app discovery are not supported on Linux). Linux instructions are less detailed, and Linux-specific tools or patterns (such as Bash, SSH, sudo) are mentioned only briefly or as secondary options.
Recommendations
  • Provide Linux-first or Linux-parity examples and instructions alongside Windows examples, especially for appliance deployment and credential configuration.
  • Include detailed Linux-specific setup steps for features currently described only for Windows (e.g., SQL Server discovery, web app discovery).
  • Expand on Linux tools and patterns (e.g., Bash scripts, systemd, SSH key management) where PowerShell and Windows tools are described.
  • Clearly indicate feature gaps for Linux and provide workarounds or alternatives where possible.
  • Ensure that Linux requirements and supported distributions are listed as prominently and in as much detail as Windows versions.
  • Add troubleshooting and FAQ sections for common Linux migration issues.
GitHub Create Pull Request
Migrate Quickstart to create an Azure Migrate project using Portal ...lob/main/articles/migrate/quickstart-create-project.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias in the section describing command-line operations for Azure Migrate. It instructs users to install the Azure CLI and then explicitly directs them to use PowerShell as Administrator to execute commands, without mentioning Linux or macOS terminals. No Linux/macOS-specific instructions or examples are provided, and the workflow assumes a Windows environment. This may create friction for users on non-Windows platforms.
Recommendations
  • Include instructions for running Azure CLI commands on Linux and macOS terminals (e.g., bash, zsh).
  • Clarify that Azure CLI can be used on any supported OS, and provide OS-agnostic command examples.
  • Avoid specifying 'PowerShell as Administrator' unless necessary, and offer equivalent steps for Linux/macOS (e.g., using sudo if required).
  • Add a note or section highlighting cross-platform compatibility and any OS-specific 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-13 06:17
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 moderate Windows bias: Windows-specific instructions (such as WMI Control configuration and user group assignments) are presented in greater detail and often before Linux equivalents. Windows tools and workflows (WMI, WinRM, SQL Server with Windows authentication) are described step-by-step, while Linux instructions are more concise and sometimes lack equivalent depth (e.g., no GUI walkthroughs or troubleshooting for Linux). SQL Server examples are Windows-centric, with no parity for Linux-based SQL deployments. Hyper-V coverage is inherently Windows-only, and the page often lists Windows before Linux in tables and sections.
Recommendations
  • Provide equally detailed, step-by-step instructions for Linux server configuration, including troubleshooting and verification steps.
  • Include Linux-first examples in tables and sections to balance presentation order.
  • Offer parity for Linux-based SQL Server deployments, including authentication and permission setup.
  • Add more Linux-specific troubleshooting, screenshots, and tool references (e.g., SELinux, systemd, journalctl) where applicable.
  • Clarify when instructions are Windows-only and offer Linux alternatives or links.
  • For Hyper-V, explicitly state its Windows-only nature and suggest Linux virtualization equivalents if relevant.
GitHub Create Pull Request
Migrate Set up an Azure Migrate appliance for server assessment in a VMware environment ...ain/articles/migrate/how-to-set-up-appliance-vmware.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page exhibits a moderate Windows bias. The PowerShell installer script is mentioned as the only alternative to the OVA template, with no Linux shell or bash equivalent provided. The VDDK installation instructions specify a Windows file path (C:\Program Files\VMware\VMware Virtual Disk Development Kit) and do not mention Linux installation steps or paths. Credential examples and validation focus on Windows domain and non-domain accounts, with Linux credentials mentioned only in passing and no Linux-specific guidance or troubleshooting. Most configuration and troubleshooting steps assume Windows environments, and screenshots show Windows-centric interfaces.
Recommendations
  • Provide Linux shell/bash installer script examples and instructions alongside PowerShell.
  • Include Linux-specific steps for installing and configuring the VDDK, including default Linux paths and permissions.
  • Offer parity in credential setup and validation for Linux servers, with troubleshooting tips for common Linux authentication issues.
  • Add screenshots and configuration manager examples from Linux environments.
  • Explicitly state OS requirements and supported platforms for the appliance, and clarify any limitations for Linux users.
GitHub Create Pull Request
Migrate Troubleshoot issues with agentless and agent-based dependency analysis ...lob/main/articles/migrate/troubleshoot-dependencies.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
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, WinRM, Registry Editor, WMI, Control Panel) are frequently mentioned, often with detailed step-by-step instructions and troubleshooting guidance. PowerShell and Windows error remediation steps are more thorough and appear before Linux equivalents. Linux troubleshooting is present but less detailed, and some sections (e.g., registry edits, WMI, UAC, PowerShell language mode) are Windows-only, with no Linux alternatives or parity guidance. Linux examples are sometimes present but are less emphasized and often follow Windows instructions.
Recommendations
  • Ensure Linux troubleshooting steps are as detailed as Windows, including step-by-step instructions for common errors.
  • Provide Linux-first or parallel examples for all commands and remediation steps, especially in sections where Windows tools (PowerShell, Registry Editor, WMI) are used.
  • Where Windows-specific tools are referenced, add equivalent Linux tools or commands (e.g., for registry edits, suggest Linux config file changes if relevant).
  • Balance the order of examples so that Linux and Windows are presented together or alternately, not always Windows first.
  • Expand Linux error codes and remediation guidance, including more context for SSH, permissions, and agent installation issues.
  • Add troubleshooting screenshots or walkthroughs for Linux environments, similar to those provided for Windows.
GitHub Create Pull Request
Migrate Troubleshoot the Azure Migrate appliance ...s/blob/main/articles/migrate/troubleshoot-appliance.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
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 several signs of Windows bias. Troubleshooting steps and examples often reference Windows tools (Control Panel, admin command prompt, Notepad, PowerShell, WMI, WinRM, registry edits) and provide Windows-specific instructions first or exclusively. Linux guidance is present in some sections, but is less detailed and sometimes appears after Windows instructions. Some remediation steps for appliance/server issues are Windows-only or assume familiarity with Windows environments, creating friction for Linux/macOS users.
Recommendations
  • Ensure Linux troubleshooting steps are provided with equal detail and prominence as Windows steps.
  • Where Windows tools (e.g., Control Panel, Notepad, PowerShell) are referenced, offer Linux/macOS equivalents (e.g., timedatectl, nano/vim, Bash scripts).
  • Present Linux and Windows examples side-by-side or in parallel tabs, rather than Windows-first.
  • Expand Linux-specific remediation guidance, especially for time sync, hosts file edits, and service management.
  • Clarify which steps are OS-agnostic and which require OS-specific commands, and provide alternatives for macOS where relevant.
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-13 06:17
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 moderate Windows bias. Critical setup steps (such as deploying the Azure Migrate appliance without OVA) are described only for Windows (PowerShell script on Windows Server 2019/2022), with no Linux alternative. Windows tools (PowerShell, Windows authentication, IIS) are mentioned first or exclusively in several places. Linux support is referenced, but Linux-specific setup instructions, troubleshooting, and parity for appliance deployment are missing.
Recommendations
  • Provide explicit instructions for deploying the Azure Migrate appliance on Linux hosts, including supported distributions and setup scripts.
  • Offer Linux shell (bash/ssh) examples alongside PowerShell for appliance setup and management.
  • Clarify whether the PowerShell script method is Windows-only, and if so, provide a Linux equivalent or state Linux limitations.
  • Include troubleshooting and configuration steps for Linux environments (e.g., SELinux, firewalls, systemd services).
  • Ensure Linux tools and patterns (such as systemd, SSH, Linux authentication) are described with equal prominence as Windows tools.
  • Add parity for application discovery examples (e.g., Apache/Tomcat for Linux, not just IIS/ASP.NET for Windows).
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
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page exhibits 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/macOS-specific instructions, examples, or parity in tooling. The documentation implicitly assumes Windows as the default platform for assessment, which may exclude or create friction for organizations with Linux-based infrastructure.
Recommendations
  • Explicitly state whether the Azure Migrate appliance supports Linux or provide alternatives for Linux environments.
  • Include instructions or examples for preparing Linux servers for assessment, if supported.
  • If the appliance is Windows-only, suggest workarounds or third-party tools for Linux/macOS users.
  • Clarify platform requirements early in the documentation to help users plan accordingly.
GitHub Create Pull Request
Migrate Create project ...zure-docs/blob/main/articles/migrate/create-project.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page demonstrates a moderate Windows bias. Command-line instructions for post-project creation (Az CLI usage) are explicitly shown only for PowerShell, with no mention of Linux/macOS terminals or shell environments. The instructions direct users to open PowerShell as Administrator, which is a Windows-specific pattern. There are no Linux/macOS-specific examples or guidance, and the CLI installation link does not clarify cross-platform usage. However, the main project creation workflow is portal-based and platform-agnostic.
Recommendations
  • Provide explicit instructions for running Az CLI commands on Linux/macOS terminals (e.g., Bash, zsh), including any differences in command syntax or environment setup.
  • Clarify that Az CLI is cross-platform and link to installation instructions for Linux/macOS.
  • Replace 'open PowerShell as Administrator' with platform-neutral language, such as 'open your terminal with appropriate permissions'.
  • Add notes or examples for Linux/macOS users where command-line steps are shown.
  • Ensure screenshots and UI instructions do not assume a Windows environment.
GitHub Create Pull Request
Migrate Azure VM assessments in Azure Migrate ...in/articles/migrate/concepts-assessment-calculation.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 Heavy Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. Windows operating systems are listed first and in detail in readiness tables, with Linux and other OSes grouped together and referenced via external links. The assessment logic and examples focus heavily on Windows versions and their support status, while Linux is treated generically and lacks specific examples or detailed guidance. There are no Linux-specific assessment examples, troubleshooting steps, or parity in discussion of OS support nuances.
Recommendations
  • Provide Linux-specific examples and assessment scenarios, including common distributions and edge cases.
  • List Linux operating systems and their support status in the readiness tables, not just as a reference link.
  • Include troubleshooting steps and guidance for Linux VMs, such as kernel version detection and migration caveats.
  • Balance the order of OS presentation so that Linux is not always after Windows, and highlight Linux-specific features or considerations.
  • Add examples or references for macOS and other non-Windows platforms where relevant.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation exclusively references PowerShell scripts for automating Azure Migrate tasks, with all example scripts using the .ps1 extension and no mention of Bash, shell, or cross-platform alternatives. The script repository and documentation links are PowerShell-specific, and there are no Linux/macOS command-line examples or guidance. This creates friction for users on Linux or macOS, who may not have access to PowerShell by default or may prefer native tools.
Recommendations
  • Provide equivalent Bash or shell script examples for Linux/macOS users.
  • Document how to run PowerShell Core on Linux/macOS, including installation steps.
  • Clarify cross-platform compatibility of the provided PowerShell scripts.
  • Offer guidance or links for Linux-native automation tools (e.g., Azure CLI) where possible.
  • Present examples for both Windows and Linux/macOS environments, or note any limitations.
GitHub Create Pull Request
← Previous Page 3 of 9 Next →