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 701-725 of 918 flagged pages
Migrate Azure Migrate Collector virtual machine extension reference ...migrate/migrate-virtual-machine-extension-reference.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation generally maintains parity between Windows and Linux, providing separate extension types, installation, and troubleshooting instructions for both platforms. However, in several key command examples (such as viewing extension status, updating, and removing the extension), only the Windows extension name is shown, with no Linux equivalent provided. Additionally, in some sections, Windows examples or instructions appear before Linux ones, which may subtly reinforce a Windows-first perspective.
Recommendations
  • For all command examples (especially az connectedmachine extension show, update, and delete), provide both Windows and Linux extension name variants, or clarify that the command applies to both by substituting the extension name accordingly.
  • Where possible, alternate the order of Windows and Linux examples, or present them side-by-side to avoid implicit prioritization.
  • Explicitly state that all commands and procedures apply equally to both Windows and Linux, and highlight any platform-specific differences.
  • Ensure troubleshooting and log location instructions for both platforms are equally detailed and visible.
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-14 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits a moderate Windows bias. Windows-specific tools (PowerShell, WinRM, WMI) and configuration steps are described in detail, with explicit references to Windows ports, authentication, and permissions. PowerShell scripts are provided for appliance setup and SQL Server discovery, but there are no equivalent Linux shell scripts or examples. Windows requirements and procedures are often listed before Linux ones, and some features (SQL Server and ASP.NET web app discovery) are not supported for Linux. Linux instructions are present but less detailed, and some advanced features are Windows-only.
Recommendations
  • Provide equivalent Linux shell scripts or command examples for appliance setup and server discovery.
  • Include Linux-first or side-by-side examples for configuration steps, rather than listing Windows first.
  • Expand Linux documentation to match the detail level of Windows instructions, especially around permissions, ports, and troubleshooting.
  • Clarify Linux support limitations and offer alternative approaches or workarounds where features are Windows-only.
  • Add explicit references to Linux tools and patterns (e.g., SSH, systemd, SELinux) where relevant.
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-14 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 demonstrates several Windows biases. Windows tools and patterns (PowerShell, WMI, WinRM, Windows authentication) are mentioned and required in multiple sections, often before or instead of Linux equivalents. SQL Server and web app discovery are Windows-centric, with Linux support explicitly missing or limited. Example scripts and configuration details are provided only for Windows authentication and SQL Server, with no Linux database discovery or equivalent Linux-focused examples. Windows-specific requirements (such as PowerShell, WMI, WinRM, and domain accounts) are detailed, while Linux requirements are less thoroughly explained or omitted.
Recommendations
  • Provide Linux-focused examples and scripts for tasks such as SQL Server discovery, web app discovery, and credential setup.
  • Clarify Linux support limitations and offer alternative solutions or workarounds for Linux users where features are Windows-only.
  • Present Windows and Linux requirements in parallel, rather than listing Windows first or exclusively.
  • Include Linux-specific troubleshooting steps and tool recommendations (e.g., alternatives to WMI, WinRM, PowerShell).
  • Expand documentation for Linux server discovery, dependency analysis, and inventory, matching the detail given for Windows.
GitHub Create Pull Request
Migrate Migrate VMware servers to Azure by using Private Link ...https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/migrate-vmware-servers-to-azure-using-private-link.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing Windows Server and Azure Hybrid Benefit specifically for Windows Server machines, and by suggesting manual DNS edits via the 'hosts file' on the Azure Migrate appliance (a Windows-centric pattern). There are no explicit Linux/macOS examples or instructions, and Windows terminology appears first or exclusively in several steps.
Recommendations
  • Include explicit instructions and examples for Linux-based Azure Migrate appliances, such as how to edit /etc/hosts for DNS overrides.
  • Clarify whether the Azure Migrate appliance can run on Linux and provide parity in setup, troubleshooting, and migration steps.
  • Mention licensing benefits or considerations for Linux VMs (e.g., Azure Hybrid Benefit applicability or alternatives).
  • Avoid Windows-centric terminology (e.g., 'hosts file') without also referencing Linux/macOS equivalents.
  • Provide troubleshooting steps and network validation commands for Linux (e.g., using dig, nslookup, or host).
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-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation focuses exclusively on deploying an Azure Migrate project using the Azure portal and ARM templates, with no mention of Linux/macOS command-line tools (e.g., Azure CLI, Bash) or cross-platform automation. All instructions and screenshots are tailored to the Azure portal GUI, which is platform-agnostic but often associated with Windows workflows. There are no PowerShell-specific examples, but the absence of Linux/macOS CLI alternatives or parity is notable.
Recommendations
  • Add instructions for deploying the ARM template using Azure CLI (az deployment group create) with example commands.
  • Include Bash script examples for Linux/macOS users.
  • Explicitly mention that the Azure portal is accessible from any OS/browser.
  • Provide links to cross-platform automation options (e.g., Terraform, Azure CLI) for advanced users.
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-14 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 exhibits moderate Windows bias. Windows-specific requirements (e.g., PowerShell version, WinRM, 'winrm qc' command) are described in detail and often appear before Linux equivalents. Windows tools and patterns (WinRM, TrustedHosts, PowerShell) are mentioned explicitly, while Linux instructions are less detailed and lack equivalent command-line examples. Troubleshooting steps and onboarding notes frequently reference Windows mechanisms, with Linux alternatives mentioned but not elaborated.
Recommendations
  • Provide equivalent Linux command-line examples (e.g., how to configure SSH, validate root access, check required ports).
  • Include Linux-specific troubleshooting steps with concrete commands and error codes.
  • Balance the order of presentation so Linux and Windows instructions appear together or alternate, rather than Windows-first.
  • Clarify Linux requirements (e.g., minimum SSH version, required packages) as is done for Windows (PowerShell version).
  • Mention Linux authentication and remote management patterns (e.g., sudo, SSH key setup) with the same detail as WinRM/PowerShell for Windows.
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-14 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 (e.g., diskpart, PowerShell commands, Task Manager) are presented first and in greater detail, with screenshots and explicit command-line steps. Linux instructions are present and reasonably detailed, but Windows tools and patterns (diskpart, PowerShell, Task Manager) are referenced exclusively, with no equivalent Linux commands or tools shown for similar tasks (e.g., checking agent status, network configuration validation). Linux examples are sometimes generic or distribution-specific (RedHat), and lack parity in visual aids and troubleshooting steps compared to Windows sections.
Recommendations
  • Provide Linux command-line examples for checking Azure agent installation and status (e.g., systemctl status waagent).
  • Add screenshots or terminal output examples for key Linux steps, similar to those provided for Windows.
  • Include Linux-first or at least parallel examples for manual network configuration, DHCP setup, and agent verification.
  • Reference Linux troubleshooting tools and patterns (e.g., journalctl, dmesg) where Windows uses Task Manager or PowerShell.
  • Balance the order of presentation so Linux and Windows instructions are interleaved or Linux is presented first in some sections.
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-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation demonstrates bias toward Windows environments, particularly in the section on using the Azure CLI. It instructs users to install the CLI and then explicitly directs them to use PowerShell as Administrator, with all example commands shown in a PowerShell context. There are no Linux/macOS-specific instructions or examples, and the workflow assumes a Windows user experience. This could create friction for Linux/macOS users who typically use Bash or other shells.
Recommendations
  • Provide explicit instructions for installing and using the Azure CLI on Linux and macOS, including links to relevant documentation.
  • Include example commands for Bash/zsh shells alongside PowerShell examples, noting any syntax differences.
  • Avoid language that assumes PowerShell or Windows as the default environment; use neutral phrasing such as 'open your terminal'.
  • Clarify that the Azure CLI can be used cross-platform and highlight any platform-specific considerations.
GitHub Create Pull Request
Migrate How to review the assessments created for migration to SQL Server on Azure VM, Azure SQL Managed Instance and Azure SQL Database ...cs/blob/main/articles/migrate/review-sql-assessment.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation consistently refers to SQL Server migration scenarios involving 'SQL Server on Azure VM', which is a Windows-based deployment, and does not mention Linux-based SQL Server deployments or provide guidance/examples for Linux users. There are no references to Linux-specific migration patterns, tools, or considerations, and the assessment support status only discusses Windows OS support lifecycles. This creates a subtle but notable Windows bias, as Linux users running SQL Server are not addressed.
Recommendations
  • Explicitly mention and provide guidance for SQL Server deployments on Linux, including migration scenarios to Azure SQL targets from Linux hosts.
  • Clarify whether the assessment and migration recommendations apply to SQL Server running on Linux, and note any differences or limitations.
  • Include examples or notes for Linux users, such as how to assess readiness, cost, and support status for SQL Server on Linux.
  • Add references to Linux support status and lifecycle in the 'Review support status' section.
  • If there are limitations for Linux-based SQL Server migrations, document them clearly.
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-14 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. Troubleshooting steps and examples often reference Windows tools (Control Panel, admin command prompt, PowerShell, Notepad, registry editor) and Windows-specific commands (w32tm, winrm, net stop/start, editing C:\Windows\System32\Drivers\etc\hosts) before or instead of Linux equivalents. In several sections, remediation steps for Windows are detailed, while Linux instructions are either brief, appear later, or are missing entirely. PowerShell scripts are provided for Windows, but comparable Linux scripts are not. Some troubleshooting for physical servers does include Linux steps, but overall, Windows-centric patterns dominate.
Recommendations
  • Provide Linux-first or side-by-side examples for all troubleshooting steps, especially where only Windows tools or commands are mentioned.
  • Include Linux equivalents for commands such as time synchronization, service management, and host file editing (e.g., using timedatectl, systemctl, /etc/hosts).
  • Add Bash or shell script examples for Linux where PowerShell scripts are provided for Windows.
  • Reference Linux configuration tools (e.g., systemd, crontab, nano/vi) alongside Windows tools like Control Panel and Notepad.
  • Ensure troubleshooting steps for Linux are as detailed as those for Windows, including error codes, log locations, and common issues.
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-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits a moderate Windows bias. Many troubleshooting scenarios and examples focus on Hyper-V and Windows environments, with repeated references to Windows-specific features (e.g., dynamic memory, Hyper-V virtualization). Licensing cost calculations are only described for Windows servers, and there is no mention of Linux licensing. The 'Capture network traffic' section prioritizes Microsoft browsers and Chrome, omitting Linux-native tools (like tcpdump or Wireshark). There are no explicit Linux/Powershell command examples, but the overall troubleshooting guidance is tailored to Windows-centric environments, with Linux-specific issues and tools rarely mentioned.
Recommendations
  • Add troubleshooting examples and guidance for Linux environments, such as common issues with Linux VMs and physical servers.
  • Include Linux licensing cost considerations in the assessment cost calculations.
  • In the 'Capture network traffic' section, add instructions for using Linux-native tools (e.g., tcpdump, Wireshark) and browser options available on Linux.
  • Balance references to Hyper-V and Windows with equivalent coverage for VMware and Linux-based virtualization platforms.
  • Explicitly mention how the Azure Migrate appliance collects data from Linux servers, including any limitations or differences compared to Windows.
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-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates Windows bias by exclusively referencing Windows Server 2022 as the replication appliance, with no mention of Linux-based alternatives or parity. The migration stack improvements are described in terms of leveraging Windows technologies, and there are no examples or guidance for Linux-based replication appliances or tooling. Although the page highlights improved support for newer Linux distributions as migration targets, the infrastructure and process remain Windows-centric.
Recommendations
  • Explicitly mention whether a Linux-based replication appliance is supported or possible, and provide guidance for Linux users if available.
  • Include examples or workflows for Linux/macOS administrators, such as Linux-native tools or commands for migration setup and management.
  • Clarify if the reliance on Windows Server 2022 is a technical requirement or if alternatives exist for organizations preferring Linux-only environments.
  • Provide parity in documentation structure by listing Linux options and examples alongside Windows ones, not just as migration targets.
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-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation references Azure PowerShell for migration tasks and automation, but does not mention or provide examples for equivalent Linux/macOS tools (such as Azure CLI or Bash scripting). There is an implicit assumption that users will use PowerShell, which is more common on Windows, and no explicit guidance for Linux/macOS users is provided.
Recommendations
  • Add equivalent Azure CLI (az) examples for migration steps currently documented only with Azure PowerShell.
  • Explicitly mention that Azure CLI can be used from Linux/macOS and provide links to relevant tutorials.
  • Where automation is discussed, include Bash scripting or cross-platform automation examples alongside PowerShell.
  • Clarify in each step which tools are cross-platform and which are Windows-specific.
GitHub Create Pull Request
Migrate Troubleshoot Azure Migrate appliance diagnostic .../articles/migrate/troubleshoot-appliance-diagnostic.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits a Windows bias by referencing Windows-specific file paths (e.g., C:\Users\Public\Desktop\DiagnosticsReport), mentioning Windows Server 2022 evaluation license, and omitting any Linux or macOS equivalents or instructions. All examples and operational details assume a Windows environment, with no guidance for users running the appliance on Linux or macOS.
Recommendations
  • Provide equivalent instructions and file paths for Linux-based appliances (e.g., /home/public/Desktop/DiagnosticsReport or similar).
  • Clarify whether the appliance can run on Linux or macOS, and if so, include relevant diagnostic steps and remediation instructions for those platforms.
  • Mention licensing implications for Linux appliances, if applicable, or explicitly state Windows-only requirements.
  • Add screenshots and examples for Linux environments where possible.
  • Reorder or parallelize instructions so that Linux and Windows users are equally addressed.
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-14 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. Windows-specific tools and troubleshooting steps (WinRM, WMI, Get-WmiObject, application pools, IIS, ISAPI filters) are mentioned explicitly and often before Linux equivalents. Linux troubleshooting is present but less detailed, and examples or commands for Linux are referenced via links rather than shown inline. Web app migration errors focus almost exclusively on IIS/ASP.NET scenarios, with little mention of Java or Linux-based web servers.
Recommendations
  • Provide Linux troubleshooting steps and commands inline, not only via external links.
  • Include Linux/SSH examples alongside Windows/WinRM examples, especially in error resolution steps.
  • Balance coverage of web app migration errors to include common Linux/Java web server scenarios (e.g., Apache, Nginx, Tomcat).
  • Mention Linux tools and patterns (e.g., systemd, SSH config) explicitly where relevant.
  • Ensure parity in detail and clarity for both Windows and Linux troubleshooting sections.
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-14 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, Control Panel, WMI) are frequently referenced, often with detailed step-by-step instructions and troubleshooting guidance. PowerShell commands and remediation steps are provided before or in greater detail than their Linux equivalents. Some troubleshooting sections (e.g., registry edits, WMI access, UAC settings) are Windows-specific, with limited or no Linux alternatives. Linux instructions are present but generally less detailed, and often appear after Windows guidance.
Recommendations
  • Provide Linux-specific troubleshooting steps and examples alongside Windows instructions, especially for error codes and remediation.
  • Include parity in command-line examples, e.g., show Linux shell commands before or alongside PowerShell commands.
  • Expand Linux troubleshooting for agentless and agent-based analysis, including common issues (permissions, SSH, package installation) and their resolutions.
  • Where Windows tools (Registry Editor, Control Panel, WMI) are referenced, offer equivalent Linux guidance (e.g., config files, systemctl, journalctl, package managers).
  • Balance the order of presentation so Linux and Windows are treated equally in examples and troubleshooting tables.
GitHub Create Pull Request
Migrate Troubleshoot network connectivity issues | Microsoft Docs .../articles/migrate/troubleshoot-network-connectivity.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation consistently provides command-line examples and screenshots using Windows conventions (e.g., 'c:\>', PowerShell's Test-NetConnection, editing the Windows hosts file), without offering equivalent Linux/macOS commands or guidance. All DNS resolution and connectivity validation steps are shown with Windows tools, and there is no mention of Linux-specific commands or file paths, which may hinder non-Windows users.
Recommendations
  • For every command-line example (e.g., nslookup, Test-NetConnection), provide equivalent Linux/macOS commands (e.g., dig, host, curl, nc, ping).
  • When referencing file paths (such as the hosts file), include both Windows (C:\Windows\System32\drivers\etc\hosts) and Linux/macOS (/etc/hosts) locations.
  • If screenshots are shown from Windows, consider adding Linux/macOS terminal output as well.
  • Mention Linux/macOS tools and troubleshooting steps (e.g., systemd-resolve, resolvectl, checking /etc/resolv.conf) where appropriate.
  • Clarify that the Azure Migrate appliance can run on both Windows and Linux (if true), and provide OS-specific instructions where steps differ.
GitHub Create Pull Request
Migrate Troubleshoot ongoing server discovery, software inventory, and SQL discovery ...s/blob/main/articles/migrate/troubleshoot-discovery.md
Medium Priority View Details →
Scanned: 2026-01-14 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 demonstrates a notable Windows bias. Troubleshooting steps, error remediations, and validation commands are predominantly presented using Windows tools and PowerShell, with Linux alternatives either missing, less detailed, or presented after Windows instructions. Several remediation steps and error codes focus on Windows-specific technologies (e.g., WinRM, WMI, UAC, PowerShell), and Linux guidance is often limited to generic SSH or 'ls' commands. In some sections, Linux users are required to use Windows tools (e.g., PowerShell or OpenSSH installed via Windows) to connect to Linux servers, rather than providing native Linux command-line examples.
Recommendations
  • Provide Linux-native command-line examples (e.g., using SSH, bash, or relevant Linux utilities) alongside or before Windows/PowerShell examples.
  • For each troubleshooting step involving PowerShell or Windows tools, include equivalent Linux commands (e.g., using 'ssh', 'systemctl', 'journalctl', or other standard Linux utilities).
  • Clarify when a step is Windows-only and offer alternative guidance for Linux users.
  • Expand Linux error remediation guidance to match the detail and specificity given to Windows.
  • Avoid requiring Linux users to install or use Windows tools (such as PowerShell or OpenSSH via Windows) for tasks that can be accomplished natively on Linux.
GitHub Create Pull Request
Migrate Continuous Deployment for containerized applications with Azure DevOps ...igrate/tutorial-app-containerization-azure-pipeline.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows-first bias, especially in the 'Locate the artifacts' section, where only Windows filesystem paths (C:\ProgramData...) and Windows-specific navigation instructions (File Explorer, Hidden items) are provided. There are no equivalent instructions for locating artifacts on Linux or macOS systems, nor are Linux filesystem paths or CLI commands mentioned. This omission creates friction for users running the Azure Migrate App Containerization tool on non-Windows platforms.
Recommendations
  • Add instructions for locating artifacts on Linux and macOS, including typical default paths and relevant shell commands (e.g., using 'ls', 'find', or 'cat').
  • Clarify whether the Azure Migrate App Containerization tool can run on Linux/macOS, and if so, provide parity in navigation steps.
  • Where file navigation is described, offer both GUI (Windows Explorer) and CLI (Linux/macOS terminal) methods.
  • Explicitly mention any platform limitations or requirements for the tool.
  • Ensure examples and screenshots (if any) represent both Windows and Linux environments.
GitHub Create Pull Request
Migrate Tutorial to assess SQL instances for migration to SQL Server on Azure VM, Azure SQL Managed Instance and Azure SQL Database ...docs/blob/main/articles/migrate/tutorial-assess-sql.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page exhibits Windows bias primarily in its references to Windows Server Failover Clusters and Cloud Witness, with links and recommendations focused on Windows-specific high availability patterns. There are no examples or guidance for Linux-based SQL Server deployments, nor are Linux clustering or witness options discussed. The documentation also links to Windows-specific best practices for Azure SQL VMs, and does not mention Linux alternatives or parity.
Recommendations
  • Include explicit guidance for assessing SQL Server instances running on Linux, including any differences in data collection, migration, or assessment steps.
  • Add examples or references for Linux-based SQL Server deployments, such as Pacemaker clusters, Linux witness options, or relevant high availability patterns.
  • Where high availability and disaster recovery are discussed, provide Linux equivalents (e.g., Pacemaker, DRBD, etc.) and link to Azure documentation for SQL Server on Linux.
  • Ensure that links to best practices and configuration guides include both Windows and Linux versions, or clarify when guidance is OS-specific.
  • Add a note clarifying which steps or features are OS-agnostic and which require Windows-specific tooling or configuration.
GitHub Create Pull Request
Migrate Tutorial to assess SQL instances in VMware VMs for migration to SQL Server on Azure VM, Azure SQL Managed Instance and Azure SQL Database ...ob/main/articles/migrate/tutorial-assess-sql-vmware.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example Windows Heavy Links
Summary
The documentation page exhibits Windows bias primarily through its references to Windows-specific tools and patterns, such as Windows Server Failover Clusters and Cloud Witness, and by linking to Windows-centric best practices and configuration guides. There are no explicit Linux or cross-platform examples, and Linux equivalents (such as Pacemaker or Corosync for clustering) are not mentioned. The Azure Hybrid Benefit section mentions RHEL and SLES, but only in passing, and does not provide guidance or examples for Linux-based SQL deployments. The clustering and high availability sections exclusively discuss Windows approaches and do not address Linux scenarios.
Recommendations
  • Add explicit examples and guidance for Linux-based SQL Server deployments, including clustering and high availability (e.g., Pacemaker, Corosync).
  • Provide links to Linux best practices for SQL Server on Azure VMs, in addition to Windows guides.
  • Ensure that all configuration and migration steps are described in a cross-platform manner, or provide parallel instructions for Linux environments.
  • Clarify Azure Hybrid Benefit applicability and licensing for Linux SQL Server scenarios, with concrete examples.
  • Include screenshots or references to Linux management tools where relevant.
GitHub Create Pull Request
Migrate Tutorial to assess web apps in VMware VMs for migration to Azure App Service ...ain/articles/migrate/tutorial-assess-webapps-vmware.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation focuses primarily on assessing ASP.NET (IIS) and Java (Tomcat) web apps for migration, but examples and terminology are Windows-centric. ASP.NET/IIS (Windows) is mentioned first, and there are no explicit Linux-specific instructions, examples, or references to Linux web servers (e.g., Apache, Nginx) or Linux VM nuances. The tutorial assumes the use of the Azure Migrate appliance but does not clarify Linux support or provide Linux-specific guidance, potentially leaving Linux users uncertain about applicability.
Recommendations
  • Add explicit examples and instructions for assessing Linux-based web apps (e.g., Apache, Nginx, or Java apps running on Linux VMs).
  • Clarify whether the Azure Migrate appliance supports Linux VMs and how discovery/assessment differs for Linux workloads.
  • Include screenshots or walkthroughs showing Linux VM assessment flows.
  • Mention Linux-specific migration considerations (e.g., file system, OS compatibility, service management differences).
  • Present ASP.NET/IIS and Java/Tomcat examples in parallel, with equal prominence for Windows and Linux scenarios.
GitHub Create Pull Request
Migrate Discover servers on Hyper-V with Azure Migrate Discovery and assessment ...lob/main/articles/migrate/tutorial-discover-hyper-v.md
Medium Priority View Details →
Scanned: 2026-01-14 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 notable Windows bias. All example commands and automation scripts are provided in PowerShell, with explicit references to Windows Server versions and Windows tools (Hyper-V Manager, Local Group Policy Editor, CertUtil). Steps for appliance deployment and host preparation are exclusively described using Windows-centric methods, with no Linux equivalents or alternative tooling mentioned. Linux is acknowledged as a supported guest OS for discovery, but there are no examples or instructions for Linux administrators or environments. The documentation assumes the administrator is working in a Windows ecosystem, creating friction for Linux users.
Recommendations
  • Provide equivalent instructions and examples for Linux environments, such as how to deploy and manage the Azure Migrate appliance on Linux-based Hyper-V hosts (if supported), or clarify limitations.
  • Include Linux command-line alternatives where PowerShell or Windows tools are used (e.g., hash verification, credential delegation).
  • Add explicit guidance for Linux administrators, including troubleshooting steps and supported management tools.
  • Clearly state any limitations or requirements for Linux users up front, and link to Linux-specific documentation where available.
  • Reorder examples to present Windows and Linux instructions side-by-side or in parallel sections, rather than Windows-first.
GitHub Create Pull Request
Migrate Discover servers running in a VMware environment with Azure Migrate Discovery and assessment ...blob/main/articles/migrate/tutorial-discover-vmware.md
Medium Priority View Details →
Scanned: 2026-01-14 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 several forms of Windows bias. Windows-specific tools and patterns (such as PowerShell scripts and Windows Server requirements) are mentioned before or instead of Linux equivalents. The only alternative to OVA deployment is a PowerShell script on Windows Server, with no Linux-based setup option described. Instructions for installing the VMware VDDK reference a Windows file path exclusively. SQL Server discovery and authentication examples focus on Windows mechanisms, with Linux alternatives less detailed. While Linux is mentioned as supported, practical steps and examples for Linux users are sparse or missing.
Recommendations
  • Provide a Linux-based alternative for appliance deployment (e.g., bash script or instructions for setting up on a Linux VM).
  • Include Linux file paths and installation steps for VDDK, not just Windows (e.g., /opt/vmware/vddk).
  • Offer example commands and troubleshooting steps for Linux users (e.g., SSH setup, firewall configuration).
  • Clarify SQL Server discovery options for Linux-hosted SQL Server instances, if supported.
  • Ensure parity in credential setup examples for Linux (not just SSH keys, but also password-based and domain integration where applicable).
  • Explicitly state any limitations or differences for Linux users in each relevant section.
GitHub Create Pull Request
Migrate Discover, assess, and migrate Google Cloud Platform (GCP) VMs to Azure ...icles/migrate/tutorial-migrate-gcp-virtual-machines.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation exhibits a notable Windows bias. The replication appliance required for migration must run on Windows Server (2012 R2 or 2016), with no Linux alternative mentioned. Instructions for downloading and installing the appliance are Windows-specific, and several steps (such as copying files and running the installer) assume a Windows environment. While Linux VMs are supported as migration sources and there are Linux-specific instructions for enabling SSH and installing the Mobility agent, the core migration infrastructure is Windows-only. This creates friction for users who prefer or require Linux-based management hosts.
Recommendations
  • Provide a Linux-based replication appliance option or clearly state if only Windows is supported, including rationale and possible workarounds.
  • Include Linux command-line examples for any steps that can be performed on Linux (e.g., copying installer files, running scripts).
  • Clarify in the prerequisites that the replication appliance must be Windows, and suggest best practices for Linux-centric environments (e.g., using a minimal Windows VM solely for the appliance).
  • Wherever possible, present Linux and Windows instructions in parallel, rather than focusing on Windows first.
  • If Linux support for the appliance is not possible, provide guidance for automating or managing the Windows appliance from Linux-based orchestration tools.
GitHub Create Pull Request
← Previous Page 29 of 37 Next →