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 376-400 of 918 flagged pages
Migrate https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/how-to-scale-out-for-migration.md ...ain/articles/migrate/how-to-scale-out-for-migration.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation is strongly biased toward Windows environments. All instructions and examples assume the appliance is deployed on Windows Server 2019/2022, with exclusive use of PowerShell scripts for installation and configuration. Windows-specific tools (CertUtil, IIS, registry edits) are referenced, and there are no Linux equivalents or alternative instructions for deploying or managing the appliance on Linux systems. The documentation does not mention Linux support or provide parity for Linux administrators.
Recommendations
  • Explicitly state platform requirements and limitations at the beginning, clarifying if Linux is unsupported or providing guidance for Linux environments.
  • If Linux support is possible, provide equivalent instructions for deploying the appliance on Linux servers, including shell script alternatives to PowerShell and Linux-native tools for checksum validation (e.g., sha256sum).
  • Offer examples using Linux command-line tools for tasks such as file extraction, hash validation, and configuration management.
  • If the appliance is Windows-only, add a clear note explaining this limitation and suggest alternatives for Linux-based environments.
  • Consider developing and documenting a Linux-compatible installer or management workflow to improve cross-platform parity.
GitHub Create Pull Request
Migrate https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/how-to-set-up-appliance-hyper-v.md ...in/articles/migrate/how-to-set-up-appliance-hyper-v.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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 presents Windows-centric tools and workflows. Examples and instructions use Windows tools (Hyper-V Manager, PowerShell, CertUtil, Local Group Policy Editor) exclusively, with no Linux equivalents or parity. Even when mentioning Linux credentials, there are no Linux-specific setup or troubleshooting examples. The documentation assumes the appliance will be deployed and managed from a Windows system, and all command-line and GUI instructions are Windows-only.
Recommendations
  • Add equivalent instructions for deploying and managing the Azure Migrate appliance from Linux hosts, including CLI commands and GUI alternatives.
  • Provide hash verification examples using Linux tools (e.g., sha256sum, md5sum) alongside CertUtil and Get-FileHash.
  • Include guidance for credential delegation and proxy setup on Linux systems, if supported.
  • Clarify any limitations or differences when using Linux as the host or management system for the appliance.
  • Ensure all steps that use Windows-specific tools (Hyper-V Manager, PowerShell, Local Group Policy Editor) have Linux alternatives or explicitly state platform requirements.
  • Add troubleshooting and validation steps for Linux environments where applicable.
GitHub Create Pull Request
Migrate https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/how-to-set-up-appliance-physical.md ...n/articles/migrate/how-to-set-up-appliance-physical.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation for setting up an Azure Migrate appliance for physical servers demonstrates a strong Windows bias. All setup and installation instructions are provided exclusively using PowerShell and Windows-specific tools (e.g., IIS, Windows Activation Service, registry edits), with no mention of Linux equivalents or alternative workflows. The examples and screenshots focus on Windows environments, and Linux is only referenced in the context of credential types for discovery, not for appliance setup or management. There are no instructions for deploying or managing the appliance on Linux servers, nor are Linux shell commands or tools provided.
Recommendations
  • Provide equivalent setup instructions for Linux environments, including shell script examples and Linux-specific prerequisites.
  • Document how to deploy and manage the Azure Migrate appliance on Linux servers, if supported, or clarify platform limitations.
  • Include Linux tools and patterns (e.g., systemd, Apache/Nginx, cron, Linux file paths) where appropriate.
  • Offer parity in troubleshooting steps, such as log file locations and service management for Linux.
  • Ensure screenshots and examples alternate between Windows and Linux where both are supported.
  • Explicitly state platform support and limitations at the beginning of the documentation.
GitHub Create Pull Request
Migrate https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/hydration-process.md ...e-docs/blob/main/articles/migrate/hydration-process.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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 Windows bias by presenting Windows-specific instructions, screenshots, and PowerShell examples before Linux equivalents. Windows tools (e.g., diskpart, PowerShell, Task Manager) are described in detail, while Linux instructions are less visual and lack parity in example depth. Linux steps are often generic, with fewer illustrative commands and no screenshots, making the Windows experience more accessible and complete.
Recommendations
  • Provide Linux command-line examples for each manual step, similar to the PowerShell examples given for Windows (e.g., checking DHCP service status, verifying agent installation).
  • Include screenshots or terminal outputs for key Linux steps (e.g., mounting partitions, rebuilding initrd, checking waagent status), matching the visual guidance given for Windows.
  • List Linux instructions before or alongside Windows instructions to avoid 'windows_first' ordering bias.
  • Reference Linux-specific documentation and troubleshooting articles as prominently as Windows ones.
  • Expand on Linux tool usage (e.g., systemctl, lsblk, grub configuration) with concrete examples and step-by-step guidance.
  • Ensure parity in detail and clarity between Windows and Linux sections, especially for manual preparation steps.
GitHub Create Pull Request
Migrate https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/hyper-v-migration-architecture.md ...ain/articles/migrate/hyper-v-migration-architecture.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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, and exclusively references Windows tools and workflows. All examples and instructions assume the use of Windows-based management tools (MMC snap-in, Regedit, Windows registry paths), with no mention of Linux equivalents or cross-platform scenarios. There are no examples or guidance for Linux-based hypervisors or migration from non-Windows platforms.
Recommendations
  • Add sections or links for migrating Linux-based VMs (e.g., KVM, VMware on Linux) using Azure Migrate.
  • Provide parity in examples by including Linux command-line tools and configuration steps where applicable.
  • Mention cross-platform alternatives or clarify the scope is Windows-only if Linux is not supported.
  • If agentless migration is available for Linux hosts, document the process and tools involved.
  • Include a comparison table of supported platforms and migration workflows to clarify differences.
GitHub Create Pull Request
Migrate https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/least-privilege-credentials.md ...b/main/articles/migrate/least-privilege-credentials.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation is heavily biased towards Windows environments. It exclusively references Windows tools (e.g., .exe utilities, %ProgramFiles% paths), assumes use of Windows command prompt, and does not mention or provide any guidance for Linux-based SQL Server instances or cross-platform scenarios. There are no Linux or PowerShell Core examples, and all instructions are tailored for Windows users.
Recommendations
  • Provide equivalent instructions and tooling for Linux environments, including how to provision least-privileged accounts on SQL Server running on Linux.
  • Mention and demonstrate cross-platform command-line usage (e.g., bash, PowerShell Core) where possible.
  • Clarify whether the MinimumPrivilegedUser.exe utility is available or supported on Linux, or provide alternative scripts/tools for Linux users.
  • Include Linux file path examples and environment variables alongside Windows ones.
  • Explicitly state any platform limitations and offer guidance for mixed-environment (Windows and Linux) SQL Server deployments.
GitHub Create Pull Request
Migrate https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/migrate-hyper-v-servers-to-azure-using-private-link.md ...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-08 00:53
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, with all examples, instructions, and tooling specific to Windows environments. There are no Linux or cross-platform migration examples, and all references are to Windows tools and patterns (Hyper-V, Recovery Services vault, Azure Site Recovery provider, etc.). The documentation assumes the reader is operating in a Windows ecosystem and does not mention Linux-based virtualization platforms or provide parity for Linux users.
Recommendations
  • Add equivalent migration guides for Linux-based virtualization platforms (e.g., KVM, Xen, VMware on Linux hosts).
  • Include examples and instructions for agentless and agent-based migration from Linux environments.
  • Reference Linux-compatible migration tools and patterns, or clarify cross-platform support where applicable.
  • Provide troubleshooting and DNS configuration steps tailored for Linux systems (e.g., editing /etc/hosts, using dig/nslookup).
  • Explicitly state platform limitations and direct Linux users to relevant documentation or alternatives.
GitHub Create Pull Request
Migrate https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/migrate-replication-appliance.md ...main/articles/migrate/migrate-replication-appliance.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation for the Azure Migrate replication appliance demonstrates a strong Windows bias. All operating system requirements, examples, and instructions are exclusively for Windows Server (2016/2012 R2), with no mention of Linux support or alternatives. Software installation paths, licensing, and configuration details are Windows-centric (e.g., C:\Temp\ASRSetup, .msi installers, Windows Server roles, group policies, IIS settings). There are no Linux deployment instructions, examples, or parity notes, and the appliance appears to require Windows Server, excluding Linux-based environments.
Recommendations
  • Explicitly state whether Linux-based replication appliances are supported or not. If not supported, clarify this early in the documentation.
  • If Linux support is possible, provide equivalent instructions for deploying and configuring the appliance on Linux (e.g., supported distributions, required packages, installation paths, service management).
  • Include Linux-specific examples for MySQL installation, file placement, and network configuration.
  • Mention Linux alternatives for Windows-specific tools and settings (e.g., group policies, IIS, .NET Framework).
  • If only Windows is supported, add a rationale and guidance for Linux users seeking migration solutions.
GitHub Create Pull Request
Migrate https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/migrate-appliance.md ...e-docs/blob/main/articles/migrate/migrate-appliance.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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 scenarios, prerequisites, and examples focus on Windows Server (2019/2022/2025) as the host OS for the appliance, with PowerShell as the exclusive installation method outside of OVA/VHD templates. Verification and upgrade instructions use Windows-specific tools (CertUtil, Registry Editor, Control Panel), and there are no instructions or examples for deploying or managing the appliance on Linux hosts. Even in sections mentioning Linux (e.g., discovery of Linux servers), the appliance itself must run on Windows, and no Linux-based deployment or management patterns are provided.
Recommendations
  • Provide explicit instructions and examples for deploying the Azure Migrate appliance on Linux hosts, if supported, or clarify the lack of support.
  • Include Linux equivalents for all command-line operations (e.g., hash verification using sha256sum or openssl, service management, upgrades).
  • Offer installation scripts or methods for Linux environments (e.g., Bash scripts, systemd service setup) alongside PowerShell.
  • Document how to perform appliance upgrades, configuration, and verification using Linux-native tools.
  • If appliance deployment on Linux is not supported, clearly state this limitation early in the documentation and provide guidance for Linux users.
  • Ensure that any references to Windows tools (Registry Editor, Control Panel, etc.) are paired with Linux alternatives or explicit notes about platform requirements.
GitHub Create Pull Request
Migrate https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/migrate-servers-to-azure-using-private-link-agent-based.md ...igrate-servers-to-azure-using-private-link-agent-based.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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 prioritizing Windows Server scenarios (e.g., Azure Hybrid Benefit for Windows Server), referencing Windows-specific licensing features, and omitting explicit Linux migration examples, tools, or considerations. The instructions and options (such as Azure Hybrid Benefit) are described primarily for Windows Server, with no mention of Linux-specific migration nuances, agent installation, or troubleshooting. There are no Linux command-line examples, nor are Linux authentication or service management patterns discussed.
Recommendations
  • Add explicit examples and instructions for migrating Linux servers, including agent installation steps for common Linux distributions.
  • Include Linux-specific considerations, such as SELinux/AppArmor, systemd/init differences, and common troubleshooting steps for Linux environments.
  • Provide parity in licensing and benefit options, clarifying what applies to Linux (e.g., mention that Azure Hybrid Benefit is Windows-specific and note Linux licensing differences).
  • Offer Linux command-line examples for DNS configuration, connectivity checks, and agent installation (e.g., using curl, dig, systemctl, etc.).
  • Reference Linux authentication and service management patterns alongside Windows equivalents.
  • Ensure that any references to Windows-specific tools or features are balanced with Linux alternatives or clarifications.
GitHub Create Pull Request
Migrate https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/migrate-support-matrix-hyper-v-migration.md ...es/migrate/migrate-support-matrix-hyper-v-migration.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by listing Windows Server versions and requirements first and in detail, referencing Windows-specific tools (e.g., .NET Framework, Windows Firewall, RDP), and providing more granular instructions for Windows migration steps (such as enabling RDP and configuring Windows Firewall). Linux instructions are present but less detailed, often grouped together, and lack specific examples or parity in troubleshooting and configuration guidance. There are no Linux-specific tool references or step-by-step examples comparable to those for Windows (e.g., SSH setup is mentioned but not detailed).
Recommendations
  • Provide Linux-first or parallel examples and instructions alongside Windows steps, especially for migration preparation and post-migration connectivity.
  • Include Linux-specific troubleshooting and configuration details, such as SELinux, firewalld, and SSH configuration commands.
  • Reference Linux equivalents for Windows tools (e.g., mention required Python or OpenSSH versions, or alternatives to .NET Framework where relevant).
  • Offer step-by-step Linux migration preparation guides, including firewall rule setup, SSH key management, and disk partitioning checks.
  • Balance the granularity of instructions for both Windows and Linux, ensuring that Linux users have equally comprehensive guidance.
GitHub Create Pull Request
Migrate https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/migrate-support-matrix-hyper-v.md ...ain/articles/migrate/migrate-support-matrix-hyper-v.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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 (PowerShell, WinRM, WMI, Windows authentication) and patterns are mentioned first and in detail, while Linux equivalents are referenced only as secondary options. Examples and scripts are exclusively for Windows environments (e.g., SQL Server login provisioning), with no Linux-specific code samples or detailed guidance. Windows requirements (such as enabling PowerShell remoting) are described in depth, whereas Linux requirements are summarized briefly. Some features (e.g., SQL Server discovery, ASP.NET web apps) are not supported for Linux, and this is stated without offering alternatives or workarounds.
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 code samples (e.g., shell scripts for credential provisioning, SQL Server discovery alternatives for Linux environments).
  • Expand on Linux requirements with step-by-step guidance, similar to the detail given for Windows (e.g., how to configure SSH, required permissions, troubleshooting).
  • Where features are unsupported on Linux (e.g., SQL Server discovery, ASP.NET web apps), suggest alternative approaches or clarify roadmap for Linux support.
  • Avoid listing Windows tools and patterns before Linux equivalents; present both platforms equally in tables and instructions.
  • Explicitly document any limitations for Linux and provide links to feature requests or community workarounds.
GitHub Create Pull Request
Migrate https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/migrate-support-matrix-physical-migration.md ...s/migrate/migrate-support-matrix-physical-migration.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by presenting Windows-specific instructions and requirements before Linux equivalents, referencing Windows tools and patterns (such as RDP and Windows Firewall) in greater detail, and providing more granular guidance for Windows connectivity than for Linux. There is a lack of parity in example depth and troubleshooting steps for Linux systems, and the replication appliance is described as being set up with Windows Server 2016 by default, with no mention of a Linux-based alternative.
Recommendations
  • Provide Linux-first or Linux-parallel examples and instructions, especially for connectivity and firewall configuration (e.g., show how to configure SSH and iptables/firewalld in detail).
  • Include troubleshooting steps and best practices for Linux migrations, matching the depth given to Windows (e.g., SELinux, SSH hardening, common Linux migration issues).
  • Offer a Linux-based replication appliance option or document how to set up the appliance on a Linux VM.
  • Balance the order of presentation so that Linux and Windows instructions are given equal prominence and detail.
  • Reference Linux tools and patterns (e.g., systemd, ufw, iptables) alongside Windows tools.
  • Clarify filesystem and boot support for Linux with more examples and edge cases, similar to the NTFS note for Windows.
GitHub Create Pull Request
Migrate https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/migrate-support-matrix-physical.md ...in/articles/migrate/migrate-support-matrix-physical.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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 forms of Windows bias. Windows tools and patterns (such as PowerShell, WinRM, and Windows authentication) are mentioned first and in greater detail than their Linux equivalents. Many examples and scripts are provided for Windows (e.g., PowerShell setup, SQL Server authentication), while Linux instructions are either brief, referenced externally, or missing. SQL Server and IIS web app discovery are only supported on Windows, with Linux support explicitly absent or limited. Linux requirements are often summarized or deferred to other links, and there are no Linux-specific example scripts or detailed walkthroughs.
Recommendations
  • Provide Linux-first or Linux-parity examples and instructions alongside Windows, especially for appliance setup, server access, and software inventory.
  • Include detailed Linux authentication and access configuration steps, not just brief lists of required commands.
  • Offer example scripts or command-line walkthroughs for Linux environments (e.g., SSH setup, user permissions, package manager queries).
  • Clarify or expand support for Linux-based SQL Server (if/when available), or provide guidance for alternative database discovery on Linux.
  • Ensure all references to external Linux documentation are summarized or included inline for parity with Windows instructions.
  • Explicitly state limitations for both platforms in all relevant sections, and avoid presenting Windows as the default or primary platform.
GitHub Create Pull Request
Migrate https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/migrate-support-matrix-vmware-migration.md ...les/migrate/migrate-support-matrix-vmware-migration.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exhibits several signs of Windows bias. Windows operating systems and tools are frequently mentioned first, with more detailed instructions and examples provided for Windows scenarios. PowerShell is referenced as the primary scripting interface for appliance deployment and VM replication configuration, with no equivalent Linux CLI or automation examples. Windows-specific configuration steps (e.g., RDP, Windows Firewall, SAN policy) are described in detail, while Linux instructions are more generic and lack step-by-step guidance. There is an absence of Linux-native tooling or automation references, and Linux examples are less comprehensive.
Recommendations
  • Provide Linux CLI (e.g., Bash, Azure CLI) examples for appliance deployment, replication configuration, and automation tasks alongside PowerShell instructions.
  • Ensure Linux operating systems and scenarios are described with equal detail and prominence as Windows, including step-by-step instructions for pre- and post-migration tasks.
  • Include references to Linux-native tools and patterns (e.g., systemd, iptables, SSH configuration) where relevant, not just Windows tools.
  • Present Windows and Linux instructions in parallel, or alternate which is listed first, to avoid implicit prioritization.
  • Expand troubleshooting and configuration guidance for Linux VMs, matching the specificity provided for Windows (e.g., handling SELinux, SSH keys, network/firewall setup).
GitHub Create Pull Request
Migrate https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/onboard-to-azure-arc-with-azure-migrate.md ...les/migrate/onboard-to-azure-arc-with-azure-migrate.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits a Windows bias in several ways: Windows-specific tools and commands (WinRM, PowerShell) are mentioned first and in greater detail, while Linux equivalents (SSH) are referenced briefly and often as secondary. Windows prerequisites and patterns (e.g., running 'winrm qc', PowerShell version requirements, WinRM TrustedHosts) are described with explicit commands and troubleshooting steps, whereas Linux instructions are less detailed and lack example commands. Troubleshooting and onboarding flows are centered around Windows mechanisms, with Linux support mentioned but not equally elaborated.
Recommendations
  • Provide Linux-specific onboarding and troubleshooting examples, including explicit commands for SSH configuration and agent installation.
  • Include parity in prerequisites, such as required SSH versions or Linux package dependencies, similar to the PowerShell version requirement for Windows.
  • Offer step-by-step Linux onboarding instructions, matching the detail given for Windows (e.g., how to enable SSH, validate root access, check agent status).
  • Balance troubleshooting guidance by including Linux-specific error codes, log file locations, and remediation steps.
  • Present Windows and Linux instructions in parallel, rather than listing Windows first, to avoid implicit prioritization.
GitHub Create Pull Request
Migrate https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/quickstart-create-project.md ...lob/main/articles/migrate/quickstart-create-project.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation demonstrates bias towards Windows environments by providing command-line instructions exclusively for PowerShell, referencing 'PowerShell on your system as an Administrator', and omitting equivalent Linux/bash examples. The installation instructions for Az CLI do not clarify cross-platform usage, and all CLI examples are presented in a Windows-centric context.
Recommendations
  • Provide equivalent bash/Linux shell examples alongside PowerShell instructions for Az CLI usage.
  • Clarify that Az CLI is cross-platform and can be used on Linux, macOS, and Windows.
  • Avoid phrases like 'go to PowerShell on your system as an Administrator' and instead use neutral language such as 'open your command-line interface'.
  • Include screenshots or instructions that demonstrate usage on Linux systems, where relevant.
  • Explicitly mention platform differences or requirements when steps may vary between Windows and Linux.
GitHub Create Pull Request
Migrate https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/resources-faq.md ...azure-docs/blob/main/articles/migrate/resources-faq.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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-specific tools (MAP Toolkit), focusing on Windows migration scenarios, and omitting Linux-specific migration tools or examples. The discussion of assessment and planning tools centers on Windows environments, and scripting mentions PowerShell before Bash, with no Linux migration workflows or tools highlighted.
Recommendations
  • Include examples and references for Linux migration scenarios, such as migrating Linux VMs or workloads.
  • Mention Linux-specific assessment and planning tools (e.g., Azure Migrate's support for Linux, or open-source alternatives).
  • Provide parity in scripting examples, giving Bash and PowerShell equal prominence.
  • Add FAQs or sections addressing common Linux migration questions and challenges.
  • Reference documentation or tutorials for migrating Linux servers and applications to Azure.
GitHub Create Pull Request
Migrate https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/prepare-for-agentless-migration.md ...in/articles/migrate/prepare-for-agentless-migration.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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 configuration steps and examples are presented first and in greater detail, including screenshots and explicit PowerShell commands. Windows-specific tools (diskpart, PowerShell, registry editing) are described with step-by-step instructions, while Linux instructions are more generic and lack distribution-specific examples or screenshots. Linux configuration steps rely on illustrative examples for RedHat but do not provide equivalent detail for other distributions. There are also missing Linux command examples for some steps (e.g., checking agent status), and Windows tooling is referenced more frequently and prominently.
Recommendations
  • Alternate the order of Windows and Linux sections, or present both in parallel to avoid 'Windows first' bias.
  • Provide Linux command-line examples for all manual steps, including agent status checks and network configuration, for multiple distributions (e.g., Ubuntu, SUSE, Debian), not just RedHat.
  • Include screenshots or terminal output examples for Linux steps, similar to those provided for Windows.
  • Reference Linux equivalents for Windows tools (e.g., use 'lsblk', 'systemctl', 'nmcli', etc.) and avoid assuming familiarity with Windows-only utilities.
  • Expand Linux instructions to cover common troubleshooting scenarios and manual preparation steps for distributions other than RedHat.
  • Ensure that links to Linux documentation are as prominent and detailed as those for Windows.
GitHub Create Pull Request
Migrate https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/prepare-for-migration.md ...cs/blob/main/articles/migrate/prepare-for-migration.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. Windows-specific instructions, tools, and examples (such as diskpart, SAN policy, and PowerShell for enabling RDP) are presented in detail and often before Linux equivalents. Windows configuration steps are more granular and tool-specific, while Linux instructions are more generic and lack command-line examples. Windows tools and patterns (e.g., Windows Firewall, WinHTTP proxy, RDP) are referenced explicitly, whereas Linux steps (e.g., enabling SSH, updating fstab) are described briefly and without concrete command examples. In several sections, Windows steps are listed first or in greater detail, and Linux guidance is sometimes missing or less actionable.
Recommendations
  • Provide Linux command-line examples for each configuration step (e.g., commands to enable SSH, update firewall rules, rebuild init image, update fstab, remove udev rules).
  • Ensure Linux instructions are as detailed and actionable as Windows instructions, including troubleshooting steps and references to common Linux tools (e.g., iptables, firewalld, systemctl).
  • Present Windows and Linux steps in parallel, or alternate which OS is described first, to avoid implicit prioritization.
  • Include links to Linux-specific documentation for migration preparation, similar to the Windows links provided.
  • Add examples for popular Linux distributions (e.g., Ubuntu, RHEL, SUSE) for common migration preparation tasks.
  • Explicitly mention Linux equivalents for Windows tools and patterns (e.g., SSH for RDP, Linux firewall configuration for Windows Firewall).
GitHub Create Pull Request
Migrate https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/review-assessment.md ...e-docs/blob/main/articles/migrate/review-assessment.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates Windows bias by referencing Windows Server as the primary example of conditional readiness, mentioning Windows-specific migration issues, and listing Windows-native tools (robocopy) for disk migration. There are no explicit Linux examples, nor are Linux-specific migration challenges or tools discussed. The assessment logic and remediation guidance are described in general terms, but the only concrete OS mentioned is Windows, and the only migration tool examples are Windows-centric.
Recommendations
  • Include explicit Linux examples in readiness categories (e.g., mention common Linux distributions and their compatibility issues).
  • Discuss Linux-specific migration challenges, such as differences in boot types (BIOS/UEFI), disk formats, or kernel compatibility.
  • Provide Linux-native migration tool alternatives (e.g., rsync, dd, tar) alongside robocopy and azcopy, and explain their usage in the migration context.
  • Reference Linux-specific remediation guidance where applicable (e.g., handling unsupported filesystems, updating kernel versions).
  • Ensure that examples and troubleshooting steps are balanced between Windows and Linux, or presented in a platform-neutral way.
GitHub Create Pull Request
Migrate https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/scale-physical-assessment.md ...lob/main/articles/migrate/scale-physical-assessment.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exhibits Windows bias by exclusively referencing the Azure Migrate appliance as being deployed on a Windows server, with no mention of Linux support or alternatives. There are no Linux-specific instructions, examples, or parity in tooling discussed. The steps and planning sections implicitly assume a Windows environment for the assessment process.
Recommendations
  • Explicitly state whether the Azure Migrate appliance can be deployed on Linux servers, and provide instructions if supported.
  • Include Linux-specific examples and steps for preparing physical servers for assessment.
  • Mention any Linux-compatible tools or scripts for discovery and assessment, or clarify if only Windows is supported.
  • Add a comparison table or section outlining differences and requirements for Windows vs. Linux server assessment.
  • Ensure that planning and deployment guidance does not assume Windows as the default or only platform.
GitHub Create Pull Request
Migrate https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/simplified-experience-for-azure-migrate.md ...les/migrate/simplified-experience-for-azure-migrate.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates Windows bias by exclusively mentioning Windows Server 2022 as the replication appliance, with no mention of Linux-based alternatives or equivalent tooling. The migration stack is described as supporting newer Linux distributions, but all infrastructure examples and tooling references are Windows-centric. There are no Linux-specific setup instructions, examples, or parity in tooling recommendations.
Recommendations
  • Provide examples and instructions for setting up the replication appliance on Linux-based systems, if supported.
  • Mention Linux-based alternatives or clarify if Windows Server is a strict requirement for the replication appliance.
  • Include Linux command-line examples or workflows alongside any Windows/Powershell instructions.
  • Explicitly document any limitations or differences for Linux users in the migration process.
  • Ensure that Linux tooling and patterns are referenced with equal prominence as Windows equivalents.
GitHub Create Pull Request
Migrate https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/troubleshoot-appliance.md ...s/blob/main/articles/migrate/troubleshoot-appliance.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits a moderate Windows bias. Troubleshooting steps and examples frequently reference Windows-specific tools (Control Panel, admin command prompt, PowerShell, Notepad, registry editor, WMI Control Panel, WinRM, etc.) and provide Windows remediation steps first or exclusively. Linux instructions are sometimes present, but often appear after Windows steps or are less detailed. Some troubleshooting sections lack Linux equivalents or parity in depth, especially for time sync, credential validation, and appliance configuration tasks.
Recommendations
  • Ensure every troubleshooting step that references a Windows tool or command also provides the Linux equivalent (e.g., for time sync, use 'timedatectl' or 'ntpdate' on Linux).
  • Present Linux and Windows examples side-by-side or in parallel tabs, rather than listing Windows first.
  • Expand Linux troubleshooting guidance to match the detail given for Windows (e.g., for credential validation, provide steps for checking SSH keys, PAM config, sudoers, etc.).
  • When referencing file edits (like hosts file), include Linux paths and commands (e.g., '/etc/hosts' with 'sudo vi /etc/hosts').
  • For appliance service management, provide Linux service commands (e.g., 'systemctl restart dra') alongside 'net stop/start dra'.
  • Where PowerShell is used for Windows, provide Bash or shell script equivalents for Linux where possible.
  • Review all sections for missing Linux examples and add them to ensure parity.
GitHub Create Pull Request
Migrate https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/start-here-vmware.md ...e-docs/blob/main/articles/migrate/start-here-vmware.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a bias towards Windows environments by providing migration automation and command-line examples exclusively with Azure PowerShell, and referencing RVTools (a Windows-only tool) for discovery. There are no Linux CLI (e.g., Bash, Azure CLI) equivalents or examples, nor are Linux-native tools for inventory or automation mentioned.
Recommendations
  • Add Azure CLI (cross-platform) examples for migration steps alongside PowerShell examples.
  • Mention and provide guidance for using Linux-compatible tools for VMware inventory, such as govc or open-source alternatives, in addition to RVTools.
  • Ensure troubleshooting and automation sections include Linux/Bash scripting options where possible.
  • Clearly indicate platform requirements for each tool or script, and suggest alternatives for non-Windows users.
  • Consider parity in step-by-step tutorials, so Linux users can follow along without needing Windows-specific tools.
GitHub Create Pull Request
← Previous Page 16 of 37 Next →