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 751-775 of 918 flagged pages
Migrate Azure VM assessments in Azure Migrate ...in/articles/migrate/concepts-assessment-calculation.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Windows Heavy Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. Windows operating systems are listed first and described in detail in readiness tables, with Linux and other OSes grouped together and referenced via external links. There are no concrete Linux-specific examples, walkthroughs, or troubleshooting steps, and the guest OS analysis section highlights a gap in Linux kernel version detection, requiring extra steps for Linux users. The documentation assumes familiarity with Windows environments and provides more granular information for Windows scenarios.
Recommendations
  • Provide Linux-specific examples and walkthroughs for common assessment scenarios, including troubleshooting and edge cases.
  • List Linux operating systems and their readiness statuses in the same detail as Windows, rather than referencing an external page.
  • Include explicit instructions or guidance for Linux users on how to ensure accurate OS version detection and assessment, especially for kernel version discovery.
  • Balance the order of presentation so that Linux and Windows are treated equally in tables and lists.
  • Add notes or sections addressing common Linux migration issues, such as disk partitioning, file system compatibility, and network adapter mapping.
GitHub Create Pull Request
Migrate Business case in Azure Migrate ...articles/migrate/concepts-business-case-calculation.md
Medium Priority View Details →
Scanned: 2026-01-13 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. Cost calculations, licensing, and management tooling are heavily focused on Windows Server, SQL Server, and Microsoft System Center. Windows licensing and ESU (Extended Security Update) costs are detailed, while Linux is only briefly mentioned in amortization and support cost tables, with no specifics or examples. Management software costs are described for Windows and SQL Server scenarios, but Linux management is not addressed. There are no Linux-specific migration, licensing, or management examples, and Windows tools/patterns are presented first and in detail.
Recommendations
  • Add explicit Linux server cost breakdowns, including licensing (if applicable), support, and management software options (e.g., Red Hat, SUSE, Ubuntu, etc.).
  • Include Linux-specific migration strategies and examples, such as recommendations for Linux workloads to Azure IaaS, Azure Linux VM, or Azure Kubernetes Service.
  • Describe management tooling and monitoring options for Linux (e.g., integration with Azure Monitor, Log Analytics, or third-party tools).
  • Present Linux cost and migration examples alongside Windows, not only as a footnote or in amortization tables.
  • Clarify how Azure Migrate handles Linux workloads in assessments and business case calculations.
GitHub Create Pull Request
Migrate Agentless Replication of VMware Virtual Machines ...rticles/migrate/concepts-vmware-agentless-migration.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in several areas. It provides only Windows-specific tooling and examples (e.g., PowerShell cmdlets like New-NetQosPolicy, references to Windows services and file paths such as C:\ProgramData\Microsoft Azure\Config), and does not mention or provide Linux/macOS equivalents for appliance management, bandwidth throttling, or configuration. The examples and instructions assume the appliance is running on Windows, with no guidance for Linux-based deployments or administration.
Recommendations
  • Provide equivalent Linux/macOS instructions and examples for appliance management, including file paths, service restart commands, and configuration file locations.
  • Offer Linux-native methods for bandwidth throttling (e.g., using tc, iptables, or other Linux QoS tools) alongside PowerShell examples.
  • Clarify whether the Azure Migrate appliance is supported on Linux, and if so, document the relevant procedures for Linux users.
  • When referencing configuration files, include both Windows and Linux file system paths.
  • Ensure that all operational examples (scripts, commands) are available for both Windows and Linux environments.
GitHub Create Pull Request
Migrate Create project ...zure-docs/blob/main/articles/migrate/create-project.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page demonstrates a moderate Windows bias, particularly in the section describing the use of Az CLI. It instructs users to install Az CLI and then specifically directs them to open PowerShell as Administrator to run commands, without mentioning Linux/macOS terminals or shell environments. There are no Linux/macOS-specific instructions or examples, and the only CLI workflow is shown in a Windows context. However, the core project creation workflow is portal-based and platform-agnostic.
Recommendations
  • Include instructions for running Az CLI commands on Linux/macOS terminals (e.g., bash, zsh), not just PowerShell.
  • Clarify that Az CLI is cross-platform and provide examples for both Windows (PowerShell) and Linux/macOS (bash/zsh).
  • Avoid language that assumes PowerShell is the default shell; use neutral phrasing like 'open your terminal'.
  • Add notes or links to Az CLI installation guides for Linux/macOS.
  • Where screenshots or steps differ by OS, provide alternatives or clarify any differences.
GitHub Create Pull Request
Migrate Tutorial to assess web apps for migration ...lob/main/articles/migrate/create-web-app-assessment.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias. Examples and terminology focus primarily on ASP.NET web apps and Windows-centric migration scenarios, with detailed sizing and performance guidance for ASP.NET and Tomcat (Java) only. There are no explicit Linux or open-source stack examples (e.g., PHP, Node.js, Python, Nginx/Apache), nor are Linux-specific migration considerations addressed. The 'Next steps' section links only to Windows Dockerfile optimization, omitting Linux container guidance.
Recommendations
  • Add explicit examples and guidance for Linux-based web apps (e.g., PHP, Node.js, Python, Ruby, Nginx, Apache) in both performance-based and as-on-premises sizing sections.
  • Include Linux container optimization links and best practices in the 'Next steps' section, alongside Windows Dockerfile guidance.
  • Clarify whether the assessment process and tooling support Linux workloads equally, and provide troubleshooting or migration tips for common Linux web stacks.
  • Ensure screenshots and UI descriptions do not imply Windows-only environments; mention Linux discovery and assessment flows where applicable.
GitHub Create Pull Request
Migrate Discovered Metadata ...docs/blob/main/articles/migrate/discovered-metadata.md
Medium Priority View Details →
Scanned: 2026-01-13 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 examples, tools, and PowerShell/WMI references are consistently presented first and in greater detail, especially for software inventory, feature, and update data. Windows-specific tools (WMI, PowerShell, Registry, COM objects) are described with full command references, while Linux equivalents are often summarized as 'commands' or grouped generically. Some sections (ASP.NET, Java, Spring Boot web app data) only mention Windows server discovery, omitting Linux scenarios. Storage metadata for Windows is more granular and PowerShell-centric, while Linux coverage is less detailed and more command-list oriented.
Recommendations
  • Present Linux and Windows examples side-by-side or in parallel tables, rather than Windows-first.
  • Expand Linux sections to match the detail level of Windows (e.g., provide explicit command outputs, example scripts, and configuration file locations).
  • For web app discovery, clarify Linux support and provide Linux-specific data collection details for Java/Spring Boot apps.
  • Where Windows uses PowerShell/WMI/Registry, explicitly map to Linux commands, config files, or APIs.
  • Add Linux/macOS-specific troubleshooting notes and caveats where relevant.
  • Ensure all features described for Windows are also covered for Linux, or explicitly note any platform limitations.
GitHub Create Pull Request
Migrate Set up Agentless Dependency Analysis in Azure Migrate ...https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/how-to-create-group-machine-dependencies-agentless.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell is the only automation/scripting method shown for managing agentless dependency analysis (enabling/disabling, exporting data), with no Linux/macOS CLI alternatives provided. Windows credential patterns and administrative permissions are described first and in more detail than Linux equivalents. The use of PowerShell and references to Windows domain/nondomain accounts are pervasive, while Linux instructions are limited to credential requirements. There are no bash, shell, or cross-platform CLI examples for Linux/macOS users.
Recommendations
  • Provide equivalent Linux/macOS CLI instructions (e.g., Azure CLI, Bash scripts) for all PowerShell-based management tasks, including enabling/disabling dependency analysis and exporting data.
  • Include Linux credential and permission setup examples before or alongside Windows instructions, with explicit command-line steps.
  • Reference cross-platform tools (e.g., Azure CLI) where possible, and clarify which steps are OS-agnostic.
  • Add screenshots or walkthroughs from Linux environments where relevant.
  • Clearly indicate which steps are applicable to Windows-only and which are cross-platform.
GitHub Create Pull Request
Migrate Discover and assess using Azure Private Link ...migrate/discover-and-assess-using-private-endpoints.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a notable Windows bias. The appliance installation and configuration instructions exclusively use PowerShell, with no Linux shell or macOS alternatives. File paths, script execution, and troubleshooting steps are all Windows-centric (e.g., C:\ paths, .ps1 scripts, running PowerShell as administrator). There are no examples or guidance for deploying or managing the Azure Migrate appliance on Linux or macOS hosts, nor any mention of Linux tools or shell commands. The VDDK installation instructions also reference only Windows default locations.
Recommendations
  • Provide equivalent Linux/macOS installation instructions, including shell script examples and file paths.
  • Clarify whether the Azure Migrate appliance can be hosted on Linux/macOS, and if so, offer guidance for those platforms.
  • Include troubleshooting steps and log file locations for Linux/macOS.
  • Offer both PowerShell and Bash (or other shell) script examples for cross-platform parity.
  • Explicitly state platform requirements and limitations at the beginning of the documentation.
GitHub Create Pull Request
Migrate Create an Azure SQL assessment ...articles/migrate/how-to-create-azure-sql-assessment.md
Medium Priority View Details →
Scanned: 2026-01-13 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 references Windows Server Failover Clusters and Cloud Witness as recommended high availability solutions, with links and examples focused on Windows-specific patterns. There is no mention of Linux-based clustering or high availability solutions (e.g., Pacemaker, Corosync), nor any Linux-specific migration or assessment considerations. The documentation also refers to Azure Hybrid Benefit for Windows Server and SQL Server licenses before mentioning Enterprise Linux (RHEL/SLES), and links to Windows-specific best practices for SQL Server on Azure VMs. No Linux or cross-platform command-line examples or tools are provided.
Recommendations
  • Include Linux-specific high availability and disaster recovery options (e.g., Pacemaker, Corosync, Linux witness configurations) alongside Windows Server Failover Cluster guidance.
  • Provide parity in documentation for SQL Server on Linux, including migration scenarios, readiness checks, and cost estimation.
  • Add links to Linux best practices for SQL Server on Azure VMs, similar to the Windows-focused link provided.
  • Clarify Azure Hybrid Benefit applicability for Linux workloads and provide examples for RHEL/SLES licensing and migration.
  • Ensure that examples and recommendations are presented in a cross-platform manner, or explicitly call out differences for Linux users.
GitHub Create Pull Request
Migrate Set up agent-based dependency analysis in Azure Migrate ...es/migrate/how-to-create-group-machine-dependencies.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation generally presents Windows instructions and tools before Linux equivalents, with more detailed steps and options for Windows (e.g., GUI, command line, automation tools). Linux instructions are concise and lack parity in detail and alternative installation methods. Windows-specific tools and patterns (e.g., double-click installer, Configuration Manager, Intigua, script links) are mentioned, while Linux alternatives are not discussed.
Recommendations
  • Provide Linux installation instructions with equal detail, including automation options (e.g., using package managers, scripts, or configuration management tools like Ansible).
  • List Linux instructions before or alongside Windows instructions, not after.
  • Mention Linux-specific tools or patterns for agent installation and management.
  • Include troubleshooting steps and supported OS lists for Linux as is done for Windows.
  • Ensure all screenshots and examples are cross-platform or provide Linux/macOS equivalents.
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-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. Windows terminology, tools, and credential types are mentioned first or exclusively in several places (e.g., guest user account for Windows, File Server role only for Windows, SQL Server discovery focused on Windows authentication). Linux is supported but often described secondarily, and some features (like File Server discovery) are Windows-only. There are no Linux-specific examples or detailed instructions for Linux server roles, and some sections lack Linux parity.
Recommendations
  • Provide Linux-specific examples and instructions for credential setup, discovery, and troubleshooting, similar to the Windows sections.
  • Clarify which features are Windows-only and offer Linux alternatives or workarounds where possible.
  • Add explicit support matrices or tables showing feature parity between Windows and Linux environments.
  • Include Linux server role discovery (e.g., Samba, NFS) in the File Server section, or clearly state limitations.
  • Ensure examples and terminology are presented in a platform-neutral order, or alternate which platform is described first.
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-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation references Azure PowerShell for migration tasks and automation, but does not mention or provide examples for Linux/macOS users or alternative CLI tools. There is an implicit assumption that users will use PowerShell, which is traditionally a Windows-centric tool, and no parity is shown for Bash, Azure CLI, or cross-platform scripting.
Recommendations
  • Include equivalent Azure CLI (az) commands and tutorials alongside PowerShell examples for migration and automation tasks.
  • Explicitly state that Azure PowerShell is cross-platform if that is the case, and provide installation instructions for Linux/macOS.
  • Add references or links to Bash scripting or Linux/macOS-specific workflows where applicable.
  • Ensure that all automation and migration steps have cross-platform examples, not just PowerShell.
GitHub Create Pull Request
Migrate Discover SQL Server instances in an existing Azure Migrate project ...ticles/migrate/how-to-discover-sql-existing-project.md
Medium Priority View Details →
Scanned: 2026-01-13 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. It references PowerShell and Windows credentials as prerequisites for discovery, and mentions Windows/Domain accounts and Windows OS credentials exclusively for authentication. There are no examples or instructions for Linux-based environments, nor are Linux tools or credential patterns discussed. The order and language suggest Windows as the primary or default platform, with Linux and macOS users left to infer equivalence or workaround steps.
Recommendations
  • Add explicit instructions and examples for Linux-based environments, including how to provide credentials and perform discovery from Linux servers.
  • Mention Linux authentication patterns (e.g., SSH keys, local Linux users) and clarify how the appliance interacts with non-Windows operating systems.
  • If PowerShell is required, provide alternatives or note how Linux users can install and use PowerShell Core, or offer Bash/Shell script equivalents.
  • Clarify whether the appliance supports discovery from Linux hosts and, if so, detail any differences in setup or requirements.
  • Present Linux/macOS examples alongside Windows, or at least note their parity, rather than referencing Windows tools and patterns first.
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-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation generally presents Windows and Linux as supported platforms, but there is a subtle bias toward Windows. Windows servers and credentials are mentioned first in most lists and tables, and examples of installed roles and features are only given for Windows servers. There are no concrete Linux-specific examples (e.g., installed packages, discovery issues, or troubleshooting steps). The documentation does not provide parity in examples or troubleshooting guidance for Linux users.
Recommendations
  • Alternate the order of Windows and Linux mentions in tables and lists, or present them together where possible.
  • Provide Linux-specific examples for software inventory, such as common packages or services discovered.
  • Include troubleshooting steps and discovery issues for Linux servers, similar to those provided for Windows.
  • Add explicit examples of Linux credentials and permissions, including sample sudoers configuration.
  • Clarify that all actions and features are equally available for Linux servers, and note any differences if they exist.
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-13 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 consistently references Windows-specific SQL Server deployments (e.g., SQL Server on Azure VM with Windows), links exclusively to Windows-based best practices, and omits any mention of Linux-based SQL Server deployments or migration scenarios. There are no examples or guidance for users running SQL Server on Linux, nor are Linux tools or patterns discussed.
Recommendations
  • Include explicit guidance and examples for SQL Server on Linux, both as a source and as a target for migration.
  • Add links to Linux-specific best practices for SQL Server on Azure VMs (e.g., https://learn.microsoft.com/azure/azure-sql/virtual-machines/linux/).
  • Clarify in each section whether the recommendations apply to both Windows and Linux SQL Server instances, or provide separate instructions where they differ.
  • Mention and provide examples of Linux-based tools or commands where relevant (e.g., bash scripts, Linux file paths, system resource monitoring).
  • Ensure that migration scenarios and readiness checks are described for both Windows and Linux environments.
GitHub Create Pull Request
Migrate Set up an Azure Migrate appliance for server assessment in a VMware environment ...ain/articles/migrate/how-to-set-up-appliance-vmware.md
Medium Priority View Details →
Scanned: 2026-01-13 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 moderate Windows bias. The alternative to OVA deployment is exclusively 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 instructions. Credential examples and validation focus on domain/Windows credentials, with Linux mentioned only as a credential type, lacking further detail or parity in examples. Windows authentication and IIS web server discovery are described in detail, while Linux equivalents (e.g., Apache, Nginx, Linux authentication) are not covered.
Recommendations
  • Provide a Linux/Bash installer script or instructions for appliance setup on Linux servers.
  • Include Linux-specific VDDK installation steps and default paths.
  • Offer parity in credential examples and validation for Linux servers, including details on supported authentication methods.
  • Document discovery and inventory for common Linux web servers (e.g., Apache, Nginx) and databases (e.g., MySQL, PostgreSQL).
  • Present Windows and Linux examples side-by-side or in separate sections to ensure equal visibility.
GitHub Create Pull Request
Migrate Customer intent: As a systems administrator, I want to download the latest version of VMware, so that I can ensure my infrastructure is up to date and secure. .../main/articles/migrate/includes/public-cloud-vmware.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Missing Linux Example Windows First
Summary
The documentation provides a download link for VMware via a Microsoft (windows.com) URL, with no mention of Linux/macOS installation steps, verification commands, or alternative download methods. There are no examples for Linux users (e.g., wget/curl usage, sha256sum verification), and the Microsoft-hosted link implies a Windows-centric approach.
Recommendations
  • Add Linux/macOS download instructions, including command-line examples (e.g., wget/curl).
  • Provide SHA256 verification steps for Linux/macOS (e.g., using sha256sum).
  • Include alternative download sources if available, or clarify cross-platform compatibility.
  • Ensure parity in example ordering (present Linux/macOS instructions alongside or before Windows).
GitHub Create Pull Request
Migrate Migrate servers to Azure using Private Link through agent-based replications ...igrate-servers-to-azure-using-private-link-agent-based.md
Medium Priority View Details →
Scanned: 2026-01-13 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 moderate Windows bias. Windows terminology (e.g., 'Windows Server', 'Azure Hybrid Benefit') is mentioned explicitly, and Windows-specific licensing benefits are described in detail, while Linux equivalents are not discussed. Examples and instructions do not provide Linux/macOS-specific steps for agent installation, DNS configuration, or troubleshooting. The documentation assumes familiarity with Windows-centric concepts and tools, and does not offer parity for Linux server migration scenarios.
Recommendations
  • Include explicit instructions and examples for migrating Linux servers, including agent installation and troubleshooting steps specific to Linux/macOS.
  • Mention Linux licensing and migration considerations, such as Azure Hybrid Benefit equivalents or differences for Linux workloads.
  • Provide sample commands for DNS configuration and network validation using Linux tools (e.g., dig, nslookup, /etc/hosts editing), not just generic 'edit hosts file' advice.
  • Clarify whether the Mobility service agent and replication appliance support Linux/macOS, and link to relevant documentation.
  • Add Linux/macOS-specific troubleshooting guidance for network connectivity and agent registration.
GitHub Create Pull Request
Migrate Troubleshoot Azure Migrate appliance diagnostic .../articles/migrate/troubleshoot-appliance-diagnostic.md
Medium Priority View Details →
Scanned: 2026-01-13 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 file paths (e.g., C:\Users\Public\Desktop\DiagnosticsReport), mentioning Windows Server evaluation licenses, and omitting any Linux or macOS-specific instructions or examples. There is no mention of Linux file paths, tools, or procedures for accessing diagnostic reports or running the appliance on non-Windows platforms.
Recommendations
  • Add instructions and examples for accessing the diagnostics report on Linux-based appliances, including typical file paths and commands.
  • Clarify whether the appliance and its diagnostic features are supported on Linux/macOS, and if not, state this explicitly.
  • If Linux is supported, provide parity in troubleshooting steps, including how to run diagnostics and locate reports on Linux systems.
  • Mention Linux equivalents for OS license checks or clarify licensing requirements for Linux appliances.
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-13 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 frequently references Windows Server, SQL Server, and extended security updates for Windows, with no mention of Linux-specific workloads, licensing, or migration scenarios. Cost and savings examples are centered around Windows technologies, and there are no Linux or open-source alternatives discussed. The documentation assumes Windows-centric environments and tools, potentially creating friction for Linux/macOS users seeking parity in migration assessments.
Recommendations
  • Include examples and cost breakdowns for Linux workloads (e.g., migrating Red Hat, Ubuntu, CentOS servers).
  • Discuss licensing, support status, and extended security updates for Linux distributions where relevant.
  • Highlight Azure migration strategies and benefits for open-source databases (e.g., PostgreSQL, MySQL) and workloads.
  • Add sections or cards that address Linux-specific migration scenarios, including Azure-native Linux VM options and management tools.
  • Ensure screenshots and sample reports show a mix of Windows and Linux workloads.
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
Medium Priority View Details →
Scanned: 2026-01-13 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 servers, which are Windows-based, to Azure using Private Link. All examples, instructions, and tooling references are specific to Hyper-V and Windows environments. There is no mention of Linux-based hypervisors (such as KVM, Xen, or even VMware in this context), nor are there any Linux command-line examples or instructions for Linux-based migration appliances. Windows terminology and tools (e.g., Hyper-V Replication provider, Recovery Service agent) are used exclusively, and there is no guidance for Linux users or parity for Linux-based migration scenarios.
Recommendations
  • Add a section or cross-reference for migrating Linux-based hypervisors (e.g., KVM, Xen, VMware) to Azure using Private Link.
  • Provide Linux-specific instructions or examples for agent-based migration, including how to configure DNS, network connectivity, and permissions from Linux appliances.
  • Include parity in troubleshooting steps, such as Linux command-line tools (e.g., dig, nslookup) for DNS resolution verification.
  • Clarify in the introduction that the guide is specific to Hyper-V/Windows, and link to equivalent Linux migration documentation if available.
  • Ensure that permissions and network configuration steps are described for both Windows and Linux environments.
GitHub Create Pull Request
Migrate Support for physical discovery and assessment in Azure Migrate and Modernize ...in/articles/migrate/migrate-support-matrix-physical.md
Medium Priority View Details →
Scanned: 2026-01-13 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 several Windows biases: Windows examples and requirements are often presented first, with more detail and explicit instructions (e.g., PowerShell scripts, WinRM configuration, SQL Server discovery). Windows-specific tools and patterns (PowerShell, WinRM, WMI) are referenced throughout, while Linux equivalents are mentioned only briefly or generically (e.g., 'ensure SSH connectivity' and list of commands). Critical features such as SQL Server instance/database and ASP.NET web app discovery are not supported on Linux, and there are no Linux-specific setup scripts or detailed walkthroughs. Linux support is described in general terms, with fewer actionable examples and less guidance.
Recommendations
  • Provide Linux-first or parallel examples for setup, configuration, and troubleshooting, including sample scripts for Linux environments.
  • Expand Linux documentation to match the depth of Windows instructions, especially for appliance setup, port configuration, and software inventory.
  • Clearly indicate feature parity gaps (e.g., SQL Server and ASP.NET web app discovery not supported on Linux) and suggest alternative approaches or workarounds for Linux users.
  • Include links to Linux-specific resources and troubleshooting guides.
  • Where PowerShell is referenced, offer equivalent Bash/SSH command examples for Linux.
  • List Linux requirements and steps before or alongside Windows, not after.
GitHub Create Pull Request
Migrate VMware server discovery support in Azure Migrate and Modernize ...main/articles/migrate/migrate-support-matrix-vmware.md
Medium Priority View Details →
Scanned: 2026-01-13 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 exhibits several types of Windows bias. Windows tools and technologies (PowerShell, WMI, WinRM, IIS, Windows authentication) are referenced frequently and often before or instead of Linux equivalents. SQL Server and ASP.NET web app discovery are supported only on Windows, with Linux explicitly not supported. Example scripts and configuration instructions are provided only for Windows authentication and SQL Server, with no equivalent for Linux-based databases. Windows-specific ports and permissions are detailed, while Linux requirements are less thoroughly described. In some sections, Linux support is mentioned but lacks parity in examples, tooling, and guidance.
Recommendations
  • Provide equivalent Linux examples and scripts where possible, especially for database discovery and authentication.
  • Expand documentation for Linux server requirements, including supported tools, authentication mechanisms, and troubleshooting steps.
  • List Linux options and examples before or alongside Windows ones to avoid 'Windows first' presentation.
  • Clarify limitations for Linux users and offer alternative approaches or workarounds.
  • Include guidance for Linux web server discovery (e.g., Apache, Nginx) if supported, or clearly state limitations.
  • Offer Bash or shell script alternatives to PowerShell where applicable.
  • Ensure parity in port, credential, and permission documentation for Linux environments.
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-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation page exhibits a notable Windows bias. Windows tools and patterns (PowerShell remoting, WinRM, WMI, Windows authentication) are mentioned first and in detail throughout, with Linux equivalents (SSH, Linux commands) described only as secondary options. Many examples and requirements focus on Windows-specific technologies, such as PowerShell scripts and Windows user groups, while Linux instructions are brief and lack parity in detail. Critical features like SQL Server instance and ASP.NET web app discovery are not supported for Linux, and no Linux-specific configuration examples are provided.
Recommendations
  • Provide Linux-first or Linux-parity examples for all major steps, including appliance deployment, credential setup, and agent installation.
  • Include detailed Linux configuration instructions (e.g., required user/group memberships, sample SSH setup, sudoers configuration).
  • Offer Linux-specific troubleshooting steps and best practices.
  • Clarify feature gaps (e.g., SQL Server and ASP.NET web app discovery not supported on Linux) and suggest alternatives or workarounds.
  • Balance the order of presentation so Linux and Windows are treated equally, rather than Windows-first.
  • Where features are Windows-only, explicitly state this early and provide links to roadmap or alternatives for Linux users.
GitHub Create Pull Request
Migrate Support for VMware vSphere migration in Azure Migrate ...les/migrate/migrate-support-matrix-vmware-migration.md
Medium Priority View Details →
Scanned: 2026-01-13 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 concepts and examples (such as RDP, Windows Firewall, PowerShell deployment, and SAN policy) are mentioned before or in more detail than their Linux equivalents. PowerShell is referenced as a primary automation tool for appliance deployment, with no mention of Bash or Linux-native alternatives. Linux instructions are present but often less detailed or appear after Windows instructions. Some sections (e.g., appliance deployment, post-migration connectivity) provide explicit Windows steps or tool references, while Linux steps are more generic or lack command-line examples.
Recommendations
  • Provide Bash or shell script alternatives for appliance deployment and management, not just PowerShell.
  • When listing post-migration connectivity steps, give Linux instructions (e.g., SSH, firewall configuration) equal detail and visibility as Windows (RDP, Windows Firewall).
  • List Linux and Windows operating systems and requirements side-by-side or in parallel, rather than Windows-first.
  • Include Linux-specific troubleshooting steps and examples, such as SELinux handling, systemd service checks, or iptables/firewalld configuration.
  • Reference Linux-native tools and patterns (e.g., cloud-init, systemctl, SSH key management) where relevant.
GitHub Create Pull Request
← Previous Page 31 of 37 Next →