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 101-125 of 218 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
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools Windows First
Summary
The documentation page exclusively uses Azure PowerShell for all command-line examples and instructions, with no mention of Azure CLI, Bash, or Linux/macOS-specific workflows. References to PowerShell are present in both the main text and linked tutorials, and all code samples are in PowerShell syntax. There are no alternative examples or guidance for users on Linux or macOS platforms, nor any mention of cross-platform tooling. Additionally, the documentation links to Windows-specific pages and patterns before any Linux equivalents (if any exist).
Recommendations
  • Provide equivalent Azure CLI examples for all PowerShell commands, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Explicitly mention that Azure PowerShell is available on Linux/macOS, or provide installation instructions for those platforms.
  • Add notes or sections for Linux/macOS users, clarifying any differences in workflow, file paths, or prerequisites.
  • Include Bash script examples for template deployment and resource management tasks.
  • Link to Linux/macOS documentation where relevant, and avoid referencing Windows-specific guides exclusively.
GitHub Create Pull Request
Migrate Review SQL assessment with Azure Migrate | Microsoft Docs .../main/articles/migrate/how-to-review-sql-assessment.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias. It repeatedly references Windows-specific SQL Server migration scenarios, links only to Windows VM best practices, and omits mention of Linux-based SQL Server deployments or migration guidance. No examples, recommendations, or links are provided for Linux SQL Server instances, nor is there any discussion of Linux-specific considerations, tools, or patterns.
Recommendations
  • Include explicit guidance for migrating SQL Server instances running on Linux to Azure targets.
  • Provide links to Azure SQL on Linux VM best practices and performance guidelines.
  • Add examples and recommendations for both Windows and Linux SQL Server environments, ensuring parity in migration steps and assessment criteria.
  • Clarify any differences in assessment, sizing, or compatibility for Linux-based SQL Server workloads.
  • Mention supported Linux distributions and any Azure-specific requirements or limitations for Linux SQL Server migrations.
GitHub Create Pull Request
Migrate Discover software inventory on on-premises servers with Azure Migrate .../main/articles/migrate/how-to-discover-applications.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example Powershell Heavy
Summary
The documentation demonstrates a moderate Windows bias. Windows terminology, tools, and credential patterns are mentioned first or exclusively in several places. Examples and instructions for Windows (such as guest user accounts, local admin privileges, and File Server role) are detailed, while Linux equivalents are referenced only briefly or not at all. Some features (e.g., File Server discovery) are Windows-only, and credential instructions are more explicit for Windows than Linux. There are no Linux-specific command examples, and Windows-centric concepts (IIS, SCCM, RDP, Active Directory) are prominent throughout.
Recommendations
  • Provide Linux-specific examples and instructions for credential setup, permissions, and discovery steps (e.g., show how to add Linux credentials, what permissions are needed, and how to verify them).
  • Include Linux equivalents for Windows-only features, or clearly state limitations and suggest alternatives (e.g., for File Server discovery, mention support for Samba or NFS servers if possible, or clarify that only Windows is supported).
  • Balance the order of presentation: mention Linux alongside Windows in credential and discovery instructions, not after or as an aside.
  • Add explicit Linux command-line examples (e.g., for verifying user permissions, configuring PostgreSQL/MySQL access, etc.).
  • Highlight any differences in appliance behavior or requirements for Linux servers, and provide troubleshooting steps for Linux-specific issues.
GitHub Create Pull Request
Migrate Review Discovered Inventory (Preview) in Azure Migrate ...articles/migrate/how-to-review-discovered-inventory.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation generally treats Windows and Linux as supported platforms for Azure Migrate discovery and inventory review, but there is a subtle Windows bias. Windows servers and credentials are mentioned first in most places, and examples or detailed steps (such as permissions for agentless dependency analysis) are more elaborate for Windows than Linux. The 'Software inventory' tab is explicitly marked as '(Windows servers only)' for installed roles and features, with no equivalent Linux example or clarification. There are no PowerShell-heavy sections or exclusive Windows tools, but Linux users may find the guidance less detailed or secondary.
Recommendations
  • Alternate the order of Windows and Linux mentions/examples throughout the documentation to avoid 'Windows first' bias.
  • Provide equally detailed examples and instructions for Linux environments, including explicit steps for Linux credential setup, permissions, and troubleshooting.
  • Clarify which features are Windows-only and, where possible, offer Linux equivalents or workarounds (e.g., for software inventory).
  • Include screenshots or command-line examples for Linux where Windows examples are shown.
  • Add a table or section summarizing feature parity between Windows and Linux discovery and inventory capabilities.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias. The alternative to OVA deployment is a PowerShell installer script, with no mention of a Linux shell or Bash equivalent. The VDDK installation instructions specify a Windows path (C:\Program Files\VMware\VMware Virtual Disk Development Kit) and do not provide Linux installation guidance. Credential examples and validation focus on Windows/domain credentials, with Linux credentials mentioned only in passing and without detailed instructions or examples. The configuration steps and screenshots are oriented toward Windows environments, and there is no guidance for Linux-based appliance setup or management.
Recommendations
  • Provide Bash or shell script alternatives to the PowerShell installer for Linux-based appliances.
  • Include instructions and examples for installing VDDK on Linux (e.g., typical Linux paths, extraction commands).
  • Offer step-by-step guidance and screenshots for Linux-based appliance setup and configuration.
  • Ensure credential validation and mapping instructions cover Linux accounts in detail, not just Windows/domain accounts.
  • Present Linux examples and instructions alongside Windows ones, not only as an afterthought.
GitHub Create Pull Request
Migrate Hydration process ...e-docs/blob/main/articles/migrate/hydration-process.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. Windows instructions and examples are presented first and in greater detail, including screenshots and explicit PowerShell commands. Windows-specific tools (diskpart, PowerShell, Task Manager) are described with step-by-step guidance, while Linux instructions are less visual and rely on generic or illustrative examples, with fewer screenshots and less explicit command-line walkthroughs. Some manual steps for Linux are referenced only via external links, and certain Linux examples are limited to RedHat, with other distributions left to consult their own documentation.
Recommendations
  • Provide Linux examples and screenshots for key steps, such as verifying agent installation, DHCP configuration, and disk mounting.
  • Include explicit Linux command-line instructions for all major distributions (e.g., Ubuntu, Debian, SUSE), not just RedHat.
  • Balance the order of presentation by alternating or grouping Windows and Linux instructions, rather than always listing Windows first.
  • Add troubleshooting steps and manual preparation guidance for Linux VMs, similar to the detailed Windows section.
  • Reference Linux equivalents for Windows tools (e.g., use 'lsblk', 'systemctl', 'nmcli', etc.) and provide sample outputs.
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
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page exhibits a moderate Windows bias. It repeatedly references Windows Server, SQL Server, and extended security updates for Windows, with cost and licensing examples focused on Windows workloads. There is no mention of Linux-specific migration scenarios, licensing, or cost savings, nor are Linux distributions or open-source database options discussed. The examples and savings calculations are Windows-centric, and Linux users may find it difficult to map their scenarios to the guidance provided.
Recommendations
  • Include explicit examples and cost breakdowns for Linux workloads (e.g., Ubuntu, CentOS, Red Hat) and open-source databases (e.g., PostgreSQL, MySQL).
  • Discuss migration strategies and Azure cost estimations for Linux servers, including licensing considerations and security updates.
  • Add sections or cards that highlight savings and operational benefits for Linux-based environments, not just Windows.
  • Ensure that references to extended security updates, licensing, and hybrid benefits clarify applicability to both Windows and Linux workloads.
  • Present examples and reports in a platform-neutral order, or alternate between Windows and Linux scenarios.
GitHub Create Pull Request
Migrate Support for physical server migration in Azure Migrate and Modernize ...s/migrate/migrate-support-matrix-physical-migration.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation demonstrates a moderate Windows bias. Windows-specific details (such as RDP, Windows Firewall, and Windows Server 2016 for the replication appliance) are presented first or exclusively, while Linux instructions are less detailed or appear after Windows instructions. The replication appliance is described as being set up with Windows Server 2016, with no mention of a Linux-based alternative. Windows-specific networking and migration patterns (RDP, Windows Firewall) are explained in depth, while Linux connectivity (SSH) is covered more briefly.
Recommendations
  • Provide Linux-first or parallel examples for connectivity and firewall configuration, such as explicit iptables or firewalld instructions for SSH.
  • Clarify whether the replication appliance can be deployed on Linux, and if so, provide setup instructions.
  • Balance the detail level between Windows and Linux sections, ensuring Linux users have step-by-step guidance equivalent to Windows users.
  • Mention Linux-specific migration considerations (e.g., SELinux, systemd services, common distributions) where relevant.
GitHub Create Pull Request
Migrate Azure Migrate Collector virtual machine extension reference ...migrate/migrate-virtual-machine-extension-reference.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation generally maintains parity between Windows and Linux, providing examples and instructions for both platforms. However, there are several instances of Windows bias: Windows examples and terminology are often presented first (e.g., extension status commands, update/removal commands), PowerShell instructions are included (which are Windows-centric), and some CLI commands reference only the Windows extension name. Additionally, troubleshooting and log paths are shown for both OSes, but some command examples (e.g., extension status, update, and removal) only show the Windows extension name, omitting the Linux equivalent.
Recommendations
  • For every command example (especially az CLI), show both Windows and Linux extension names, or clarify that the same command applies to both by substituting the extension name.
  • Present Windows and Linux instructions side-by-side or in parallel sections, rather than listing Windows first throughout.
  • Where PowerShell is used, clarify its applicability to Linux (if any) or provide equivalent Bash or shell script examples for Linux users.
  • In troubleshooting and status sections, ensure Linux commands and paths are given equal prominence and detail.
  • Explicitly state that all commands and procedures apply to both OSes, or highlight any differences.
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
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias: Windows-specific tools (WinRM, PowerShell) are mentioned first and in greater detail, with explicit commands and port requirements. Linux equivalents (SSH, root account) are referenced but lack comparable depth, examples, or troubleshooting guidance. Some steps (e.g., enabling WinRM, PowerShell version requirements) are Windows-only, and Linux users are expected to infer their steps. Troubleshooting sections also favor Windows scenarios, with more detailed remediation for WinRM and credential issues than for SSH or Linux-specific problems.
Recommendations
  • Provide Linux-specific command examples (e.g., how to verify SSH access, required packages, or agent installation commands).
  • List Linux prerequisites (such as minimum SSH version, required packages, supported distributions) with the same detail as Windows (e.g., PowerShell version).
  • Offer troubleshooting steps for common Linux onboarding errors, including SSH configuration, permissions, and agent installation issues.
  • Present Windows and Linux instructions side-by-side or in parallel sections to ensure parity and clarity.
  • Include references to Linux tools (e.g., systemctl, journalctl, SSH key setup) where appropriate.
GitHub Create Pull Request
Migrate Support for Hyper-V assessment in Azure Migrate and Modernize ...ain/articles/migrate/migrate-support-matrix-hyper-v.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation is heavily focused on Windows environments, with Windows-specific tools (PowerShell, WinRM, WMI) and patterns mentioned first or exclusively. Examples and requirements for PowerShell remoting, Windows authentication, and Windows user groups are detailed, while Linux equivalents are often mentioned briefly or as secondary. SQL Server discovery and web app discovery are not supported for Linux servers in Hyper-V environments, and there are no Linux-specific configuration examples or scripts provided.
Recommendations
  • Provide Linux-first or Linux-parity examples and instructions where possible, especially for appliance deployment, credential setup, and dependency analysis.
  • Include Linux-specific troubleshooting and configuration guidance alongside Windows sections, not just as brief notes.
  • Offer sample scripts or step-by-step instructions for Linux server onboarding, permissions, and connectivity (e.g., SSH key setup, sudo configuration).
  • Clarify limitations for Linux support in SQL Server and web app discovery, and suggest alternative approaches or roadmap for future support.
  • Balance the order of presentation so Linux and Windows requirements are presented together, rather than Windows-first.
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-12 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 exhibits several forms of Windows bias. Windows-specific tools (PowerShell, WMI) and authentication mechanisms are referenced frequently and sometimes exclusively. Examples and scripts for SQL Server discovery are only provided for Windows authentication and SQL Server authentication, with no Linux database discovery support. Windows requirements (such as PowerShell and WMI) are detailed, while Linux equivalents are either missing or less emphasized. In several sections, Windows servers are discussed first or in more detail, and Linux support is limited or absent (e.g., SQL Server and ASP.NET web apps discovery).
Recommendations
  • Provide Linux-specific examples and scripts where applicable, especially for database discovery and authentication.
  • Include parity in tooling requirements, such as mentioning Bash and Linux-native tools alongside PowerShell and WMI.
  • Clearly state limitations for Linux and offer alternative approaches or workarounds where support is missing.
  • Present Windows and Linux requirements side-by-side in tables for equal visibility.
  • Expand support for Linux workloads (e.g., SQL Server on Linux, ASP.NET Core on Linux) where possible, or link to migration alternatives.
GitHub Create Pull Request
Migrate Prepare machines for migration with Azure Migrate ...cs/blob/main/articles/migrate/prepare-for-migration.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits a moderate Windows bias. Windows-specific instructions, tools, and examples (such as diskpart, SAN policy, RDP, Windows Firewall, and PowerShell) are presented in detail and often before Linux equivalents. Linux instructions are less detailed, sometimes lacking explicit command examples, and are generally presented after Windows sections. Windows tools and configuration steps (e.g., enabling RDP via PowerShell, configuring Windows Firewall) are described with links and step-by-step guidance, while Linux steps (e.g., enabling SSH, updating fstab) are summarized without command-level detail. This creates friction for Linux users, who may need to seek additional resources to complete migration preparation tasks.
Recommendations
  • Provide Linux command-line examples for all manual steps (e.g., updating fstab, enabling SSH, rebuilding init image, updating firewall rules).
  • Include links to Linux-specific documentation for migration preparation tasks, similar to the Windows links provided.
  • Present Windows and Linux instructions in parallel or side-by-side where possible, rather than Windows-first.
  • Expand Linux troubleshooting and post-migration connectivity guidance to match the detail given for Windows (e.g., SSH configuration, Linux firewall rules, SELinux considerations).
  • Add explicit instructions for Linux users on verifying required services and updates before migration, analogous to the Windows guidance.
GitHub Create Pull Request
Migrate Quickstart to create an Azure Migrate project using an Azure Resource Manager template. .../articles/migrate/quickstart-create-migrate-project.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation exclusively describes deploying an ARM template via the Azure portal, with no mention of command-line alternatives such as Azure CLI, PowerShell, or Bash. There are no examples or instructions for Linux/macOS users, nor is there guidance for deploying via cross-platform tools. The workflow assumes use of the Azure portal, which is platform-agnostic but omits parity for users who prefer or require CLI-based automation, common in Linux environments.
Recommendations
  • Add instructions and examples for deploying the ARM template using Azure CLI (az deployment group create), which works on Linux, macOS, and Windows.
  • Include Bash and PowerShell script examples for template deployment.
  • Explicitly mention cross-platform options and tools for template deployment.
  • Ensure screenshots and step-by-step guides are not solely focused on the portal, or clarify that the portal is accessible from any OS.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias, especially in the section describing command-line operations. It instructs users to install the Azure CLI and then specifically directs them to use PowerShell as Administrator, with all example commands shown in PowerShell context. There is no mention of Linux/macOS terminals, nor are equivalent Bash or shell instructions provided. The ordering and phrasing assume a Windows environment, which may create friction for Linux/macOS users.
Recommendations
  • Provide explicit instructions and examples for Linux/macOS users, including Bash shell equivalents for all CLI commands.
  • Clarify that Azure CLI can be used on multiple platforms and link to installation guides for Linux/macOS as well as Windows.
  • Avoid language that assumes PowerShell or Windows as the default; use neutral phrasing such as 'open your terminal' or 'use your preferred shell'.
  • Where administrator privileges are required, explain how to achieve this on Linux/macOS (e.g., using sudo).
GitHub Create Pull Request
Migrate Azure Migrate FAQ ...azure-docs/blob/main/articles/migrate/resources-faq.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page for Azure Migrate FAQ demonstrates a moderate Windows bias. Windows-specific tools such as the MAP Toolkit are mentioned exclusively, and migration scenarios focus on Windows-centric virtualization platforms (VMware, Hyper-V) without explicit mention of Linux-based alternatives. Scripting examples list PowerShell before Bash, and there are no Linux-specific migration tool references or examples. This may create friction for Linux users seeking parity in migration guidance.
Recommendations
  • Include references to Linux-based migration tools or assessment utilities where relevant.
  • Provide examples or guidance for migrating Linux servers and workloads, not just Windows VMs.
  • Mention Bash and Linux scripting equally alongside PowerShell, and provide sample scripts for both.
  • Clarify support for Linux distributions in migration scenarios and assessment tools.
  • Add links to documentation or tutorials specifically for Linux migration use cases.
GitHub Create Pull Request
Migrate Prepare machines for agentless migration with Azure Migrate ...in/articles/migrate/prepare-for-agentless-migration.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page presents Windows-specific instructions and examples before Linux equivalents, uses Windows tools (diskpart, PowerShell) and screenshots, and provides more detailed manual steps for Windows (including registry and service configuration) than for Linux. Linux instructions are present and reasonably detailed, but Windows examples (e.g., PowerShell for DHCP, diskpart for SAN policy) are shown first and exclusively, with no Linux command-line parity for similar steps (e.g., DHCP configuration).
Recommendations
  • Provide Linux command-line examples for equivalent steps (e.g., checking/enabling DHCP, verifying agent installation) alongside Windows PowerShell commands.
  • Alternate the order of Windows and Linux sections, or present both OS types in parallel for each step.
  • Include Linux screenshots or terminal output where Windows screenshots are shown.
  • Reference Linux tools and patterns (e.g., systemctl, nmcli, /etc/network/interfaces) where appropriate.
  • Ensure manual preparation steps for Linux are as detailed as those for Windows, including troubleshooting tips.
GitHub Create Pull Request
Migrate Start here - Migrate VMware deployments to Azure ...e-docs/blob/main/articles/migrate/start-here-vmware.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell is referenced as the primary automation and CLI tool for migration tasks, with no mention of Linux/macOS alternatives (such as Bash, Azure CLI, or cross-platform scripting). Examples and tutorials focus on Azure PowerShell, and there are no Linux-specific instructions or parity for non-Windows environments. The page assumes familiarity with Windows-centric tools and patterns, which may create friction for Linux/macOS users.
Recommendations
  • Add equivalent examples and tutorials using Azure CLI (az), which is cross-platform and widely used on Linux/macOS.
  • Explicitly mention that Azure PowerShell is available on Linux/macOS, or provide installation instructions for those platforms.
  • Include Bash or shell script examples for automation tasks, or reference third-party tools commonly used in Linux environments.
  • Clarify any platform-specific requirements or limitations for agent-based and agentless migration steps.
  • Ensure troubleshooting and preparation guides cover Linux/macOS scenarios, not just Windows/PowerShell.
GitHub Create Pull Request
Migrate Troubleshoot Azure Migrate appliance diagnostic .../articles/migrate/troubleshoot-appliance-diagnostic.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page for Azure Migrate appliance diagnostics demonstrates a Windows bias. All file paths and report locations are given in Windows format (e.g., C:\Users\Public\Desktop\DiagnosticsReport), and references to OS licensing are specific to Windows Server 2022. There are no examples, instructions, or clarifications for Linux-based appliances or non-Windows environments. The documentation implicitly assumes the appliance server is running Windows, with no mention of Linux equivalents or how diagnostics would work on Linux or macOS.
Recommendations
  • Add explicit instructions and examples for Linux-based appliance servers, including file paths (e.g., /home/public/Desktop/DiagnosticsReport) and report locations.
  • Clarify whether the diagnostic tool and its features are supported on Linux appliances, and if not, state the limitation clearly.
  • Provide OS license check details for Linux appliances, or clarify that this step is Windows-specific.
  • Ensure screenshots and step-by-step instructions include Linux UI or CLI examples where applicable.
  • Consider listing both Windows and Linux instructions side-by-side or in separate sections for parity.
GitHub Create Pull Request
Migrate Common issues in Azure Migrate assessments .../blob/main/articles/migrate/troubleshoot-assessment.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. Windows-specific tools and troubleshooting steps (WinRM, WMI, Get-WmiObject, applicationHost.config, IIS, ISAPI filters) are mentioned explicitly and often before or instead of Linux equivalents. Linux troubleshooting is present but less detailed, and examples or instructions for Linux are often missing or less prominent. Web app migration errors focus on IIS and Windows-centric configurations, with little mention of Linux-based web servers or Java app migration specifics.
Recommendations
  • Provide Linux-specific troubleshooting steps and examples wherever Windows tools (WinRM, WMI, PowerShell) are mentioned.
  • Include parity for Linux server discovery and assessment errors, such as common SSH issues, sudo/root permissions, and SELinux/AppArmor restrictions.
  • Add examples for Linux web app migration (e.g., Apache, Nginx, Tomcat) alongside IIS-focused errors.
  • When listing port requirements or authentication methods, present Linux and Windows options equally and in parallel.
  • Expand documentation for Linux server metadata commands and troubleshooting, linking to relevant Linux admin guides.
  • Balance the order of presentation so Linux and Windows are treated equally, not Windows-first.
GitHub Create Pull Request
Migrate Simplified experience for Azure Migrate ...les/migrate/simplified-experience-for-azure-migrate.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page for Azure Migrate's simplified experience demonstrates a Windows bias by exclusively referencing Windows Server 2022 as the required platform for the replication appliance, without mentioning Linux-based alternatives or providing Linux-specific setup instructions. Although the page highlights improved support for migrating newer Linux distributions, all infrastructure and tooling examples are Windows-centric, and Linux users are not given parity in appliance deployment or operational guidance.
Recommendations
  • Explicitly state whether Linux-based replication appliances are supported or not. If not, clarify the rationale and provide guidance for Linux users.
  • If possible, offer Linux-based alternatives for the replication appliance, or document workarounds for Linux-only environments.
  • Include examples and instructions for Linux system administrators, such as agent installation, migration steps, and troubleshooting on Linux platforms.
  • Present OS-neutral or Linux-first examples where relevant, especially in sections discussing onboarding, configuration, and automation.
  • Add a FAQ or dedicated section addressing common Linux migration scenarios and challenges.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits moderate Windows bias. Troubleshooting steps and examples frequently reference Windows tools (Control Panel, admin command prompt, PowerShell, Notepad, Windows registry, WMI Control Panel) and provide Windows-specific instructions before or in greater detail than Linux equivalents. Some sections, such as time synchronization and host file editing, only mention Windows methods, omitting Linux/macOS alternatives. Linux troubleshooting is present but less comprehensive, and examples for Linux are sometimes given after Windows ones or only in specific error cases.
Recommendations
  • Provide Linux/macOS equivalents for all troubleshooting steps (e.g., time sync, host file editing, service management).
  • Include Linux/macOS command-line examples alongside Windows/PowerShell ones, ideally in parallel tabs or sections.
  • Avoid referencing Windows tools (Control Panel, Notepad, admin command prompt) exclusively; mention cross-platform alternatives (e.g., timedatectl, nano/vi, sudo).
  • Ensure Linux troubleshooting steps are as detailed and prominent as Windows ones.
  • Consider a section or table summarizing common troubleshooting actions for both Windows and Linux/macOS appliances.
GitHub Create Pull Request
Migrate Troubleshoot assessments FAQ in Azure Migrate ...b/main/articles/migrate/troubleshoot-assessment-faq.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example Powershell Heavy
Summary
The documentation page exhibits a moderate Windows bias. Many troubleshooting scenarios and examples focus on Hyper-V (Windows virtualization), Windows licensing, and Windows-centric environments. The 'Capture network traffic' section prioritizes Microsoft browsers (Edge, IE) and Chrome, with no mention of Linux tools or workflows (e.g., tcpdump, Wireshark, or browser instructions for Linux). Licensing cost calculations are only described for Windows, with Linux explicitly excluded. There are no Linux-specific troubleshooting examples, and Windows/Hyper-V scenarios are consistently described first or exclusively.
Recommendations
  • Add Linux-specific troubleshooting examples and guidance, especially for common Linux virtualization platforms (e.g., KVM, Xen).
  • Include instructions for capturing network traffic on Linux (e.g., using tcpdump, Wireshark, or browser developer tools on Linux).
  • Clarify how licensing costs are handled for Linux servers, or provide guidance for estimating Linux licensing costs.
  • Balance examples between Windows and Linux environments, and avoid presenting Windows scenarios first or exclusively.
  • Mention Linux-specific issues or product gaps where relevant, not just Hyper-V/Windows gaps.
GitHub Create Pull Request
Migrate Troubleshoot replication issues in agentless VMware VM migration ...ate/troubleshoot-changed-block-tracking-replication.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 is heavily biased toward Windows environments, with troubleshooting steps and commands almost exclusively referencing Windows tools (PowerShell, MMC snap-in, services.msc, Command Prompt), and providing examples only for Windows. There are no Linux/macOS equivalents for key operations such as service management, network connectivity checks, or file editing. This creates friction for users running the Azure Migrate appliance on Linux or those who prefer cross-platform tooling.
Recommendations
  • Provide Linux/macOS equivalents for all PowerShell and Windows-specific commands (e.g., use systemctl/service for service management, curl/nc for network tests, and appropriate file paths for hosts file edits).
  • Include CLI examples using Bash or cross-platform tools alongside PowerShell commands.
  • Clarify whether the Azure Migrate appliance is Windows-only; if Linux is supported, ensure parity in instructions.
  • Reference cross-platform tools (e.g., azcopy, Service Bus Explorer) with installation and usage instructions for Linux/macOS.
  • Avoid assuming remote desktop or Windows GUI access; offer alternatives for headless or non-Windows environments.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits a moderate Windows bias. Windows tools (PowerShell, WinRM, Registry Editor, WMI) are referenced frequently and often before Linux equivalents. Troubleshooting steps and error remediations for Windows servers are more detailed, with step-by-step instructions and screenshots, while Linux guidance is present but less extensive and sometimes appears after Windows instructions. Some examples and commands are Windows-specific (e.g., Registry Editor, PowerShell cmdlets) with Linux alternatives given less prominence or detail. In a few cases, Linux troubleshooting is covered, but overall, Windows users are better supported.
Recommendations
  • Ensure Linux troubleshooting steps are as detailed and explicit as Windows steps, including command-line examples and screenshots where appropriate.
  • Present Linux and Windows instructions in parallel or side-by-side, rather than listing Windows first.
  • Expand Linux error remediation guidance, especially for issues like SSH connectivity, permissions, and agent installation.
  • Include Linux-specific tools and troubleshooting patterns (e.g., systemctl, journalctl, /var/log, SELinux/AppArmor notes) where relevant.
  • Add more Linux command examples for verification and mitigation, matching the depth of PowerShell examples.
  • Where Windows registry or GUI steps are given, provide equivalent Linux configuration file or CLI steps.
GitHub Create Pull Request
← Previous Page 5 of 9 Next →