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 76-100 of 918 flagged pages
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
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example Windows First
Summary
The documentation page exclusively uses Azure PowerShell for all command-line examples and instructions, with no mention or examples of Azure CLI, Bash, or Linux-native tooling. References to creating disk encryption sets and deploying Resource Manager templates link to Windows-specific PowerShell guides, and the only example provided for deploying templates uses a Windows file path. There is no guidance for users on Linux or macOS platforms, nor is there parity in example coverage for non-Windows environments.
Recommendations
  • Add equivalent Azure CLI examples for all PowerShell commands, including creating disk encryption sets, querying resources, and deploying Resource Manager templates.
  • Include notes or sections explicitly addressing Linux/macOS users, clarifying how to perform steps in Bash or other shells.
  • Use platform-neutral file paths in examples, or provide both Windows and Linux/macOS variants.
  • Reference Azure CLI documentation alongside PowerShell documentation, and avoid linking only to Windows-specific guides.
  • Where possible, provide screenshots or walkthroughs for portal actions that are not platform-dependent.
GitHub Create Pull Request
Migrate Review Discovered Inventory (Preview) in Azure Migrate ...articles/migrate/how-to-review-discovered-inventory.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in several ways. Windows servers and credentials are mentioned before Linux equivalents, and features such as installed roles and features are explicitly marked as 'Windows servers only.' There is a lack of Linux-specific examples, tools, or troubleshooting steps, and the documentation does not provide parity in describing Linux server inventory details or common Linux web/database platforms. The focus on Windows technologies (e.g., .NET, IIS, SQL Server) is more prominent than on Linux alternatives.
Recommendations
  • Provide Linux-specific examples and screenshots for credential setup, inventory review, and troubleshooting.
  • Include details and guidance for common Linux workloads (e.g., Apache, Nginx, MySQL, PostgreSQL) alongside Windows workloads.
  • Ensure that instructions and feature descriptions for Linux servers are as detailed as those for Windows servers, including inventory attributes and discovery issues.
  • Avoid listing Windows options before Linux options unless there is a technical reason; use neutral ordering or parallel presentation.
  • Add troubleshooting steps and permissions guidance for Linux environments, including common error scenarios.
  • Expand database and web app inventory sections to mention and support popular Linux-based platforms.
GitHub Create Pull Request
Migrate Review SQL assessment with Azure Migrate | Microsoft Docs .../main/articles/migrate/how-to-review-sql-assessment.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by consistently referencing Windows-based SQL Server deployments and migration strategies, such as SQL Server on Azure VM and Windows-specific best practices. All example links and recommendations point to Windows resources, with no mention of Linux-based SQL Server deployments, migration patterns, or Linux-specific tools. There are no examples or guidance for users running SQL Server on Linux, nor any parity in migration recommendations for Linux environments.
Recommendations
  • Include explicit guidance and examples for migrating SQL Server running on Linux to Azure SQL targets.
  • Reference Linux-specific best practices and performance guidelines for SQL Server on Azure VM (e.g., link to Linux VM sizing and configuration docs).
  • Provide parity in recommendations for both Windows and Linux SQL Server environments, including differences in feature support, migration steps, and security readiness.
  • Add notes or sections clarifying any differences in assessment, rightsizing, or migration for Linux-based SQL Server instances.
  • Ensure that all referenced documentation (e.g., performance guidelines, HADR best practices) includes or links to Linux equivalents where available.
GitHub Create Pull Request
Migrate Set up an Azure Migrate scale-out appliance for agentless VMware migration ...ain/articles/migrate/how-to-scale-out-for-migration.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Missing Linux Example Windows First
Summary
The documentation is strongly biased toward Windows environments. All setup instructions, installer scripts, and validation steps are designed for Windows Server (2019/2022) and rely exclusively on PowerShell scripts. Windows-specific tools (CertUtil, IIS, registry edits) are referenced, and there is no mention of Linux support or equivalent Linux-based procedures. The documentation assumes the appliance will run on Windows, with no guidance for Linux users.
Recommendations
  • Provide equivalent instructions and installer scripts for Linux-based servers, including supported distributions.
  • Offer Linux shell (bash) commands for checksum validation and configuration file handling.
  • Document any limitations or requirements for running the appliance on Linux, or explicitly state if Linux is unsupported.
  • Mention Linux alternatives to Windows tools (e.g., sha256sum instead of CertUtil, Apache/Nginx instead of IIS) where applicable.
  • Present cross-platform instructions, or clearly indicate OS-specific steps, to improve parity and accessibility for non-Windows users.
GitHub Create Pull Request
Migrate Set up an Azure Migrate appliance for Hyper-V ...in/articles/migrate/how-to-set-up-appliance-hyper-v.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation is heavily focused on Windows environments, specifically Hyper-V, and consistently prioritizes Windows tools and workflows. All examples and instructions use Windows-centric tools (Hyper-V Manager, PowerShell, CertUtil, Local Group Policy Editor), with no mention of Linux equivalents or cross-platform alternatives. Even when discussing credential types, Linux is only briefly referenced with no detailed guidance or examples. There are no Linux-based setup instructions, and all screenshots and step-by-step guides assume a Windows GUI and toolset.
Recommendations
  • Provide equivalent instructions for Linux environments, such as using KVM or other hypervisors, where applicable.
  • Include Linux command-line examples for tasks like file hashing (e.g., using sha256sum) and VM import.
  • Offer guidance for Linux administrators on how to deploy and configure the Azure Migrate appliance without relying on Windows-only tools.
  • Add screenshots and walkthroughs for Linux-based workflows, if supported.
  • Clarify platform requirements and limitations upfront, and direct Linux users to relevant resources or alternatives.
GitHub Create Pull Request
Migrate Set up an Azure Migrate appliance for physical servers ...n/articles/migrate/how-to-set-up-appliance-physical.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a strong Windows bias. All setup instructions for the Azure Migrate appliance rely exclusively on PowerShell scripts and Windows administrative tools (e.g., Registry Editor, IIS, Windows Activation Service). There are no Linux-specific setup instructions, examples, or alternative installer scripts for Linux hosts. Windows tools and patterns (e.g., registry keys, %ProgramData% paths, IIS modules) are mentioned exclusively and before any Linux equivalents, which are entirely absent. While discovery of Linux servers is supported, the appliance itself appears to require a Windows environment, and Linux administrators are not provided with guidance or parity in deployment or troubleshooting.
Recommendations
  • Provide explicit instructions and installer scripts for deploying the Azure Migrate appliance on Linux hosts, if supported.
  • Include Linux command-line examples (e.g., bash scripts, systemd service setup) alongside PowerShell instructions.
  • Document Linux equivalents for configuration steps, such as file paths, service management, and log locations.
  • Clarify OS requirements for the appliance and, if Windows-only, state this clearly at the beginning of the documentation.
  • If Linux deployment is not supported, offer guidance for integrating Linux server discovery from a Windows-based appliance, including network and authentication considerations.
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
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in several areas. The alternative to OVA deployment is described as a 'PowerShell installer script', with no mention of a Linux shell or bash equivalent. Installation instructions for the VMware VDDK specify extraction to a Windows path (C:\Program Files\...), with no Linux path or instructions. Credential examples and validation focus on domain and Windows credentials, with Linux credentials mentioned only in a dropdown list, and no Linux-specific guidance or troubleshooting. All configuration steps and screenshots are oriented toward Windows environments, with no Linux appliance deployment or management examples.
Recommendations
  • Provide Linux shell (bash) installer script instructions as an alternative to PowerShell, and link to them equally.
  • Include Linux-specific steps for installing and extracting the VMware VDDK, with appropriate Linux file paths and permissions.
  • Offer examples and troubleshooting for Linux server credentials, including validation and error handling.
  • Add screenshots and configuration manager instructions for Linux-based appliance deployments.
  • Ensure parity in documentation for both Windows and Linux environments, presenting options side-by-side where possible.
GitHub Create Pull Request
Migrate Review a business case with Azure Migrate | Microsoft Docs ...b/main/articles/migrate/how-to-view-a-business-case.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page exhibits Windows bias by repeatedly referencing Windows Server, SQL Server, and Windows licensing costs and extended security updates as primary examples in cost and savings calculations. There is a lack of equivalent discussion or examples for Linux workloads, distributions, or licensing. Windows tools and features (such as Azure Hybrid Benefit and ESU for Windows Server) are mentioned exclusively or before any Linux alternatives, and Linux-specific migration scenarios, costs, or benefits are not addressed.
Recommendations
  • Include examples and cost breakdowns for Linux workloads (e.g., RHEL, Ubuntu, SUSE) alongside Windows Server and SQL Server.
  • Discuss Linux licensing models, support status, and migration benefits in parity with Windows examples.
  • Highlight Azure Hybrid Benefit or similar cost-saving features for Linux (if available), or clarify differences.
  • Add sections or cards that show migration strategies, cost, and savings for common Linux workloads (e.g., Apache, MySQL, PostgreSQL, Tomcat) and open source databases.
  • Ensure screenshots and sample reports show a mix of Windows and Linux servers/applications.
  • Mention security and management solutions for Linux workloads (e.g., integration with Microsoft Defender for Cloud for Linux, Azure Monitor for Linux VMs).
GitHub Create Pull Request
Migrate Hydration process ...e-docs/blob/main/articles/migrate/hydration-process.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in several ways. The Windows section is presented first and in greater detail, with step-by-step instructions, screenshots, and explicit PowerShell commands for manual configuration. Windows-specific tools (diskpart, PowerShell) are featured, while Linux instructions are less detailed, lack screenshots, and provide fewer concrete command examples. Linux manual steps are mostly illustrative and focused on RedHat, with limited coverage of other distributions and no parity in visual aids or troubleshooting guidance.
Recommendations
  • Provide Linux examples and commands for all major distributions (Ubuntu, Debian, SUSE, Oracle, etc.), not just RedHat.
  • Include screenshots or terminal output for Linux manual steps, similar to those provided for Windows.
  • Offer parity in troubleshooting guidance for Linux, such as how to verify agent installation, check DHCP status, or validate network configuration.
  • Present Windows and Linux sections in parallel structure, or alternate their order to avoid implicit prioritization.
  • Reference Linux-specific documentation and tools where appropriate, and avoid assuming familiarity with Windows-only utilities.
  • Add explicit instructions for manual preparation of Linux VMs for distributions other than RedHat, including common commands and file locations.
GitHub Create Pull Request
Migrate How does Hyper-V migration work in Azure Migrate? ...ain/articles/migrate/hyper-v-migration-architecture.md
High Priority View Details →
Scanned: 2026-01-11 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 is heavily focused on Windows environments, specifically Hyper-V. All examples, tools, and instructions reference Windows-specific components (MMC snap-in, registry edits, Windows Azure Backup), with no mention of Linux equivalents or guidance for non-Windows platforms. The workflow assumes the user is operating on Windows, and does not provide parity for Linux-based virtualization or migration scenarios.
Recommendations
  • Add sections or references for migrating Linux-based VMs (e.g., KVM, VMware on Linux) using Azure Migrate.
  • Provide examples for controlling upload throughput and efficiency on Linux hosts, if supported.
  • Mention Linux-compatible migration tools or clarify platform limitations.
  • Include a comparison table of supported platforms and features for both Windows and Linux environments.
  • Explicitly state if the described process is Windows-only, and link to Linux migration documentation if available.
GitHub Create Pull Request
Migrate Azure Migrate appliance ...e-docs/blob/main/articles/migrate/migrate-appliance.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation for the Azure Migrate appliance is heavily biased towards Windows environments. All deployment and management instructions assume or require Windows Server (2019/2022/2025) as the host OS, with PowerShell installer scripts as the only supported method outside of OVA/VHD templates. Verification and upgrade steps use Windows-specific tools (CertUtil, Registry Editor, Control Panel), and all examples and screenshots are Windows-centric. Linux is only mentioned as a target for discovery, not as a supported platform for hosting the appliance or running management scripts. There are no Linux equivalents or parity in deployment, verification, or management instructions.
Recommendations
  • Document and support appliance deployment on Linux hosts, or clearly state Windows-only support up front.
  • Provide Linux shell (bash) equivalents for file hash verification (e.g., sha256sum, md5sum) alongside CertUtil examples.
  • Offer Linux-compatible installer scripts or containerized appliance options.
  • Include instructions for checking appliance versions and managing updates using Linux tools (e.g., dpkg, rpm, systemctl) if Linux support is added.
  • Add explicit examples and screenshots for Linux environments where applicable.
  • If PowerShell is required, clarify whether PowerShell Core on Linux is supported and provide relevant instructions.
  • Ensure parity in troubleshooting and configuration guidance for both Windows and Linux hosts.
GitHub Create Pull Request
Migrate Migrate Hyper-V servers to Azure by using Private Link ...ttps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/migrate-hyper-v-servers-to-azure-using-private-link.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation is heavily focused on migrating Hyper-V (a Windows-centric virtualization platform) servers to Azure. All examples, instructions, and tooling references are specific to Hyper-V and Windows environments. There are no Linux or cross-platform migration examples, nor are Linux virtualization platforms (such as KVM or Xen) mentioned. Windows tools and patterns (e.g., Recovery Services vault, Hyper-V Replication provider) are referenced exclusively, and there is no guidance for Linux-based hosts or VMs.
Recommendations
  • Add equivalent migration guides for Linux-based virtualization platforms (e.g., KVM, Xen, VirtualBox) to Azure using Private Link.
  • Include Linux-specific examples and tooling instructions, such as agent installation, DNS configuration, and network connectivity verification on Linux hosts.
  • Reference cross-platform or Linux-native tools where possible, and clarify which steps are Windows/Hyper-V specific.
  • Provide a comparison table or section outlining differences and similarities between Windows/Hyper-V and Linux migration workflows.
  • Ensure parity in troubleshooting guidance, including Linux command-line examples for DNS and network validation.
GitHub Create Pull Request
Migrate Create a custom account with minimal metadata for discovery and assessment. ...b/main/articles/migrate/least-privilege-credentials.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation is heavily oriented towards Windows environments. It references Windows-specific tools (e.g., MinimumPrivilegedUser.exe in %ProgramFiles%), assumes use of Windows command prompt, and only mentions Windows/Domain accounts and SQL authentication. There are no examples or guidance for Linux-based SQL Server deployments, nor is there mention of Linux command-line equivalents or cross-platform considerations.
Recommendations
  • Provide instructions and examples for provisioning least privileged accounts on SQL Server running on Linux, including relevant command-line tools and file paths.
  • Clarify whether the MinimumPrivilegedUser.exe utility is available or supported on Linux, or suggest alternative methods for Linux environments.
  • Include examples using Bash or Linux shell, and mention how to handle authentication and account creation for SQL Server on Linux.
  • Explicitly state platform requirements and offer guidance for both Windows and Linux users to ensure parity.
GitHub Create Pull Request
Migrate Support for physical server migration in Azure Migrate and Modernize ...s/migrate/migrate-support-matrix-physical-migration.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation demonstrates a Windows bias by referencing Windows Server as the default OS for the replication appliance, providing more detailed instructions for Windows connectivity (RDP and firewall), and mentioning Windows-specific features (BitLocker, Windows Firewall, Device-Specific Module for multipath IO) before or in greater detail than their Linux equivalents. Linux instructions are present but less detailed, and there are no explicit Linux command examples or parity in troubleshooting steps.
Recommendations
  • Provide explicit Linux-based examples for appliance setup, including supported distributions and installation steps.
  • Include Linux-specific troubleshooting and connectivity instructions (e.g., SELinux, iptables, systemd service management for SSH).
  • Offer parity in detail for Linux features (e.g., encrypted disks, multipath IO, firewall configuration) and clarify support for common Linux tools.
  • List Linux requirements and steps before or alongside Windows instructions to avoid 'Windows first' ordering.
  • Add examples for connecting to migrated Linux VMs using SSH, including command-line steps and security group configuration.
  • Clarify support for Linux disk encryption (e.g., LUKS) and provide guidance for migration scenarios involving encrypted Linux volumes.
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
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing Windows Server and Windows licensing benefits before any mention of Linux. It also omits explicit Linux migration examples, focusing on Windows-centric features such as Azure Hybrid Benefit (which applies only to Windows Server). There are no Linux-specific instructions, troubleshooting, or examples, and the documentation does not mention Linux tools or patterns for agent installation, DNS configuration, or migration steps.
Recommendations
  • Include explicit Linux migration examples, such as migrating Ubuntu, CentOS, or other Linux distributions, with step-by-step instructions.
  • Add Linux-specific instructions for installing and configuring the replication appliance and Mobility service agent (e.g., using shell commands, systemd, or package managers like apt/yum).
  • Provide troubleshooting guidance for common Linux networking and DNS resolution issues, including sample commands (e.g., dig, nslookup, /etc/hosts editing).
  • Clarify which steps or features are Windows-only (such as Azure Hybrid Benefit) and provide equivalent Linux options or note their absence.
  • Ensure that examples and screenshots show both Windows and Linux environments where applicable.
GitHub Create Pull Request
Migrate Support for Hyper-V assessment in Azure Migrate and Modernize ...ain/articles/migrate/migrate-support-matrix-hyper-v.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits a clear Windows bias. Windows-specific tools and patterns (such as PowerShell remoting, WinRM, and Windows authentication) are mentioned first and in detail, with Linux alternatives only briefly referenced. PowerShell is required for many operations, and examples/scripts are exclusively for Windows environments. SQL Server discovery and web app assessment are not supported for Linux, and there are no Linux-specific configuration or troubleshooting examples. Linux support is mentioned but lacks parity in depth and actionable guidance.
Recommendations
  • Provide Linux-first or Linux-parity examples and instructions alongside Windows ones, especially for appliance deployment, server access, and dependency analysis.
  • Include Linux-specific troubleshooting steps, configuration scripts, and sample commands for common operations (e.g., appliance deployment via Linux tools, SSH setup, sudo configuration).
  • Expand SQL Server discovery support to Linux environments or clearly document alternative approaches for Linux-based SQL workloads.
  • Offer equivalent detail for Linux web app discovery (e.g., Apache, Nginx) and configuration, not just Tomcat.
  • Balance the order of presentation so Linux methods are described before or alongside Windows methods, not only as addenda.
  • Where PowerShell is required, provide Bash or shell script alternatives for Linux environments.
  • Document any limitations for Linux explicitly and provide workarounds or roadmap for future parity.
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-11 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 in several ways: Windows operating systems and tools are often mentioned before Linux equivalents, PowerShell is referenced as the primary scripting method for appliance deployment, and examples or instructions for Linux command-line or automation are missing. While Linux support is described, actionable steps and tooling are less explicit compared to Windows, and PowerShell is suggested for bulk VM replication configuration without mention of Linux alternatives.
Recommendations
  • Provide Linux shell (bash) or cross-platform CLI examples alongside PowerShell instructions for appliance deployment and bulk VM replication configuration.
  • When listing supported operating systems or requirements, alternate the order or present Linux and Windows equally, rather than always listing Windows first.
  • Include explicit Linux command-line instructions for tasks such as preparing VMs for migration, configuring replication, and deploying appliances.
  • Reference cross-platform tools (such as Azure CLI) where possible, and clarify which steps can be performed from Linux environments.
  • Add troubleshooting and preparation guidance for Linux VMs that is as detailed as for Windows VMs, including common issues and solutions.
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-11 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 page demonstrates a Windows bias in several areas. Windows tools and patterns (PowerShell, WMI, WinRM, Windows authentication) are mentioned first or exclusively, with detailed instructions and examples provided for Windows environments. Linux equivalents are often missing, less detailed, or relegated to secondary status. For SQL Server and web app discovery, Linux support is limited or absent, and no Linux-specific configuration scripts or examples are provided. The appliance deployment references PowerShell scripts but does not mention Linux deployment methods or scripts. Port and credential requirements are heavily focused on Windows protocols and permissions, with Linux requirements described briefly and without examples.
Recommendations
  • Provide Linux-specific deployment instructions and scripts for the Azure Migrate appliance, such as Bash or shell script examples.
  • Include Linux authentication and privilege configuration examples for SQL Server discovery, or clarify Linux support status and alternatives.
  • Offer parity in web app discovery by detailing supported Linux web servers (e.g., Apache, Nginx) and providing configuration steps for those environments.
  • Expand Linux credential and port requirements with concrete examples, such as sample sudoers file entries or SSH key setup.
  • Where Windows tools (PowerShell, WMI, WinRM) are referenced, include Linux equivalents (Bash, SSH, etc.) and ensure both platforms are covered equally in instructions and troubleshooting.
  • Clarify limitations for Linux environments and provide guidance or workarounds where features are Windows-only.
GitHub Create Pull Request
Migrate Azure Migrate Collector virtual machine extension reference ...migrate/migrate-virtual-machine-extension-reference.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation demonstrates several types of Windows bias. In multiple sections, Windows examples, commands, and extension names are presented before their Linux equivalents (windows_first). PowerShell is used for both Windows and Linux installation instructions, which is not typical for Linux users (powershell_heavy). In the 'Extension status and health', 'Update and removal', and other operational commands, only Windows extension names are shown in CLI examples, with no Linux equivalent (missing_linux_example). Troubleshooting and log paths are provided for both OSes, but operational commands and update/removal instructions only reference Windows extension names (windows_tools).
Recommendations
  • Present Linux examples and extension names alongside Windows in all CLI and operational command sections.
  • Provide Linux-native command examples (e.g., Bash scripts or shell commands) instead of PowerShell for Linux scenarios.
  • Ensure update and removal instructions include both Windows and Linux extension names and examples.
  • Review the ordering of sections and examples to avoid consistently listing Windows first, and alternate or group by OS where appropriate.
  • Clarify OS-specific steps and tools, especially where user experience or commands differ significantly.
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-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a Windows bias by frequently mentioning Windows-specific tools (WinRM, PowerShell), providing Windows instructions before Linux equivalents, and lacking detailed Linux command examples. Windows prerequisites and commands (e.g., 'winrm qc') are described in detail, while Linux instructions are minimal (e.g., only mentioning SSH port 22). Troubleshooting and onboarding steps reference Windows tools and patterns more extensively than Linux, and PowerShell is highlighted for service principal creation without equivalent Linux/CLI guidance.
Recommendations
  • Provide Linux command-line examples (e.g., SSH configuration, agent installation) alongside Windows/PowerShell instructions.
  • Include instructions for creating service principals using Azure CLI or Bash, not just Azure PowerShell.
  • Balance the order of presentation so that Linux and Windows steps are given equal prominence, or group them by OS.
  • Expand troubleshooting sections to include Linux-specific error codes, logs, and diagnostic steps.
  • Reference Linux tools (e.g., systemctl, journalctl) where appropriate for agent installation and troubleshooting.
  • Clarify authentication options for Linux (e.g., SSH key setup) with step-by-step examples.
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-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in several ways: Windows-specific instructions and examples (such as using diskpart and PowerShell) are provided in detail, often before or in greater depth than Linux equivalents. Windows tools and patterns (e.g., RDP, Windows Firewall, WinHTTP proxy) are mentioned explicitly, while Linux instructions are more generic and lack concrete command-line examples. There is a lack of parity in troubleshooting and configuration guidance for Linux, with some steps for Linux described only at a high level or as 'check that' rather than providing step-by-step instructions.
Recommendations
  • Provide Linux command-line examples (e.g., for enabling SSH, updating firewall rules, checking required services) similar to the detailed Windows instructions.
  • Include troubleshooting steps and configuration details for Linux VMs, such as how to verify and enable required services, update network settings, and handle device mapping.
  • Balance the order of presentation so that Linux and Windows instructions are given equal prominence, or group OS-specific steps together for clarity.
  • Mention Linux tools (e.g., iptables, firewalld, systemctl) explicitly where Windows tools (e.g., diskpart, PowerShell) are referenced.
  • Add links to Linux-specific migration and preparation guides, similar to those provided for Windows.
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-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates bias towards Windows environments by providing command-line instructions specifically for PowerShell, referencing execution 'as Administrator', and omitting equivalent instructions for Linux/macOS users. The Az CLI installation and usage steps are described only in the context of PowerShell, with no mention of Bash or other shells. There is no guidance for Linux users on how to perform the same tasks, and Windows terminology is used by default.
Recommendations
  • Add parallel examples for Linux/macOS users, including Bash shell instructions for Az CLI installation and usage.
  • Avoid referencing PowerShell or 'Administrator' exclusively; instead, provide cross-platform instructions (e.g., 'Open your terminal' or 'Run as a user with appropriate permissions').
  • Explicitly mention that Az CLI can be used on Windows, Linux, and macOS, and link to installation guides for all platforms.
  • Where command examples are given, provide both PowerShell and Bash syntax, or note any differences.
  • Review screenshots and UI references to ensure they are not Windows-specific unless necessary.
GitHub Create Pull Request
Migrate Azure Migrate FAQ ...azure-docs/blob/main/articles/migrate/resources-faq.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing Windows-centric tools (MAP Toolkit, Site Recovery Deployment Planner) and migration scenarios focused on Windows environments (e.g., Windows client and server OS). Linux migration tools, patterns, or examples are not mentioned, and Windows tools are introduced without Linux equivalents or parity. Scripting skills are listed as Bash, PowerShell, or Python, but no Linux-specific migration guidance or examples are provided.
Recommendations
  • Include references to Linux migration tools and patterns (e.g., guidance for migrating Linux VMs, using Linux-native tools).
  • Provide Linux-specific examples alongside Windows examples, especially in sections discussing migration planning and assessment.
  • Mention open-source or cross-platform alternatives to Windows-only tools like MAP Toolkit.
  • Clarify support and best practices for migrating Linux workloads, including any differences in agentless/agent-based migration for Linux VMs.
  • Add links to documentation or tutorials for Linux migration scenarios.
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-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation demonstrates a Windows bias by exclusively referencing the Azure Migrate appliance as being deployed on a Windows server, with no mention of Linux deployment options or examples. There are no Linux-specific instructions, examples, or parity in tooling discussed for the assessment process. The documentation assumes Windows as the default platform for the appliance and omits Linux alternatives.
Recommendations
  • Explicitly state whether the Azure Migrate appliance supports Linux servers for deployment. If not, clarify the limitation.
  • If Linux deployment is supported, add parallel instructions and examples for deploying the appliance on Linux.
  • Include Linux-specific considerations, commands, or troubleshooting steps where relevant.
  • Mention any Linux-compatible tools or third-party ISV offerings for assessment and migration.
  • Ensure that examples and instructions are provided for both Windows and Linux environments, or clarify platform limitations early in the documentation.
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-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Windows Server 2022 as the replication appliance, without mentioning any Linux-based alternatives or providing Linux-specific tooling or setup examples. While the page highlights improved support for newer Linux distributions as a benefit, all infrastructure and process examples are centered around Windows technologies, and there are no Linux-first or cross-platform instructions.
Recommendations
  • Provide information on whether a Linux-based replication appliance is supported or planned, and document setup steps if available.
  • Include examples or guidance for Linux administrators, such as Linux command-line steps or integration with Linux-native tools.
  • Clarify if the reliance on Windows Server 2022 for the replication appliance is a hard requirement, and if so, explain the rationale and any workarounds for Linux-centric environments.
  • Ensure parity in documentation by presenting Linux and Windows options side-by-side where possible, especially in onboarding and configuration workflows.
GitHub Create Pull Request
← Previous Page 4 of 37 Next →