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 126-150 of 918 flagged pages
Migrate Discover, assess, and migrate Google Cloud Platform (GCP) VMs to Azure ...icles/migrate/tutorial-migrate-gcp-virtual-machines.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation exhibits Windows bias in several areas. The replication appliance required for migration must be hosted on a Windows Server (2012 R2 or 2016), with no mention of Linux alternatives. Instructions for downloading and installing the appliance are exclusively for Windows, and screenshots and step-by-step guidance assume a Windows environment. While Linux VM preparation and Mobility agent installation are covered, the core migration infrastructure is Windows-centric, and Linux users are left without parity for the replication appliance setup.
Recommendations
  • Provide instructions and support for deploying the replication appliance on Linux-based VMs, or clarify if this is not possible and explain the rationale.
  • Include Linux-based examples and screenshots for appliance setup and management, not just for agent installation.
  • Explicitly state Windows-only requirements early in the documentation, and offer alternative workflows or guidance for Linux-centric environments.
  • Ensure parity in troubleshooting and post-migration steps, including Linux-specific issues and solutions.
  • If Windows-only tooling is unavoidable, recommend best practices for integrating Linux systems into the migration workflow and minimizing disruption.
GitHub Create Pull Request
Migrate Migrate machines as physical servers to Azure with Azure Migrate and Modernize .../migrate/tutorial-migrate-physical-virtual-machines.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a Windows bias in several ways: Windows-specific tools (e.g., SetupDiag, registry policies) and PowerShell are referenced as the default or only method for appliance setup and troubleshooting. Windows Server is repeatedly used as the example OS for the replication appliance, with explicit instructions to copy files to a Windows Server 2016 machine. Registry and group policy checks are described only for Windows. OS upgrade instructions and troubleshooting focus on Windows, with no equivalent Linux upgrade or troubleshooting guidance. Linux is mentioned in credential requirements and supported scenarios, but step-by-step examples, troubleshooting, and appliance setup are overwhelmingly Windows-centric.
Recommendations
  • Provide explicit Linux-based examples for setting up the replication appliance, including supported distributions and step-by-step instructions (e.g., using shell scripts or native Linux tools).
  • Include troubleshooting steps and checks for Linux systems, such as verifying system requirements, connectivity, and permissions, analogous to the Windows registry/group policy checks.
  • Offer parity in OS upgrade instructions and troubleshooting for Linux VMs, including common issues and solutions.
  • Where PowerShell is referenced, also provide equivalent Bash/shell commands for Linux users.
  • When referencing Windows-specific utilities (e.g., SetupDiag), clarify their applicability and provide Linux alternatives or note when they are not needed.
  • Use neutral language and examples (e.g., 'copy the appliance setup file to the machine you created for the appliance') rather than defaulting to Windows Server as the example.
GitHub Create Pull Request
Migrate Migrate VMware VMs agentless the Migration and modernization tool .../blob/main/articles/migrate/tutorial-migrate-vmware.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page exhibits several forms of Windows bias. PowerShell is the only CLI tool shown for monitoring and managing migration status, with no Bash, Azure CLI, or Linux-native alternatives provided. Windows-specific tools and upgrade paths (e.g., SetupDiag, Windows Server OS upgrade) are mentioned explicitly, while Linux equivalents are omitted or referenced only in passing. Instructions and examples consistently prioritize Windows, and Linux scenarios are not covered in detail, especially for command-line operations and troubleshooting.
Recommendations
  • Provide equivalent Azure CLI or Bash examples for all PowerShell commands, and clarify how Linux users can perform migration monitoring and management.
  • Include troubleshooting steps and upgrade guidance for Linux VMs, not just Windows (e.g., handling kernel upgrades, activation issues, etc.).
  • Mention Linux-specific tools or patterns where relevant (e.g., cloud-init, SSH, Linux agent installation details).
  • Ensure that references to OS-specific features (like SetupDiag) are balanced with Linux alternatives or notes.
  • Add explicit instructions for running commands from Linux/macOS environments, including how to use Azure Cloud Shell with Bash.
  • Review screenshots and UI instructions to ensure they are OS-neutral or provide both Windows and Linux perspectives where applicable.
GitHub Create Pull Request
Migrate Migrate VMware vSphere VMs with agent-based the Migration and modernization tool ...main/articles/migrate/tutorial-migrate-vmware-agent.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation demonstrates a Windows bias in several areas: Windows Server is the default OS for the replication appliance, with explicit instructions for Windows installation and configuration. PowerShell is mentioned as the manual setup method for the appliance, with no Linux alternative. Steps for push installation of the Mobility service provide detailed Windows registry instructions, while Linux instructions are minimal. The Azure VM agent installation is automated for Windows but only recommended manually for Linux. Troubleshooting and post-migration steps reference Windows activation and tools, with limited Linux-specific guidance.
Recommendations
  • Provide explicit instructions and examples for setting up the replication appliance on Linux-based VMs, including supported distributions and configuration steps.
  • Offer Linux shell script alternatives alongside PowerShell for manual appliance setup.
  • Expand the Linux section in Mobility service installation to include common troubleshooting, permissions, and automation methods (e.g., using SSH keys, sudoers configuration).
  • Include Linux-specific post-migration steps, such as handling cloud-init, updating fstab, and verifying bootloader compatibility.
  • Reference the Azure VM agent for Linux with installation and verification steps, not just a recommendation.
  • Add troubleshooting guidance for common Linux migration issues (e.g., kernel drivers, network configuration, SSH access).
  • Ensure parity in examples and screenshots for both Windows and Linux VMs throughout the migration process.
GitHub Create Pull Request
Migrate What's New in Azure Migrate ...ocs/azure-docs/blob/main/articles/migrate/whats-new.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation for Azure Migrate demonstrates a moderate Windows bias. Windows-specific features (such as Windows Server redeployment, Windows OS upgrades, and Windows licensing benefits) are frequently highlighted, often before or in greater detail than Linux equivalents. PowerShell is repeatedly mentioned as the automation and scripting tool, with little to no reference to Bash or Linux-native automation. Windows-centric tools (e.g., System Center Operations Manager, IIS, ASP.NET, RVTools) are referenced, while Linux tools or patterns are rarely mentioned. Examples and migration scenarios for Linux are present but less detailed, and Linux-specific migration nuances (such as SELinux, systemd, or Linux disk formats) are not discussed. There are several updates focused on Windows Server, SQL Server, and related licensing, with fewer updates focused on Linux workloads.
Recommendations
  • Add Linux-first examples and scenarios, such as migrating Linux workloads with SELinux, systemd, or specific Linux distributions (beyond RHEL/SLES).
  • Include Bash and Linux-native automation examples alongside PowerShell, especially for scripting and automation steps.
  • Highlight Linux migration tools and patterns (e.g., Ansible, rsync, cron jobs) where appropriate.
  • Ensure parity in feature announcements and migration guidance for Linux workloads (e.g., disk encryption, agent installation, dependency analysis) with detailed Linux instructions.
  • Reference Linux-specific challenges and solutions (e.g., handling ext4/xfs filesystems, SSH key management, application discovery for Linux web servers like Apache/Nginx).
  • Balance the documentation by providing equal detail for both Windows and Linux migration scenarios, including troubleshooting and best practices.
GitHub Create Pull Request
Migrate Modernize ASP.NET web apps to Azure App Service code .../migrate/tutorial-modernize-asp-net-appservice-code.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by requiring Windows PowerShell 4.0 on IIS servers for migration, referencing only Windows-based tools and environments (IIS, PowerShell), and omitting any mention of Linux-based web servers or migration paths for non-Windows platforms. There are no examples or instructions for migrating Linux-hosted web apps or using Linux-native tools.
Recommendations
  • Explicitly state whether Linux-hosted web apps (e.g., Apache, Nginx) are supported or not in the migration flow.
  • If Linux migration is supported, provide equivalent instructions and tooling for Linux environments (e.g., Bash scripts, Linux CLI commands).
  • Include examples and prerequisites for Linux-based web servers, such as how to prepare and migrate apps running on Linux.
  • Clarify any platform limitations up front, and offer guidance or alternatives for users on Linux.
  • Ensure parity in documentation structure and detail for both Windows and Linux scenarios.
GitHub Create Pull Request
Migrate Common Questions About the Migration and Modernization Tool .../articles/migrate/common-questions-server-migration.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in several ways: Windows operating systems and migration scenarios are listed before Linux equivalents, PowerShell and Windows-specific tools (e.g., NetQosPolicy, Windows scheduled tasks) are used exclusively in example scripts for bandwidth throttling, and there are no Linux shell or tool examples for similar tasks. Windows migration scenarios (Active Directory, IIS/ASP.NET) are described in detail, while Linux-specific migration scenarios and troubleshooting are less emphasized or missing.
Recommendations
  • Provide Linux shell (bash) equivalents for bandwidth throttling and scheduled task automation, such as using 'tc' for traffic control and 'cron' for scheduling.
  • List Linux operating systems and migration scenarios alongside Windows, not after them, and ensure parity in detail and troubleshooting guidance.
  • Include examples for migrating Linux workloads and applications (e.g., Apache, Nginx, MySQL/PostgreSQL) similar to the detail given for Windows workloads (IIS/ASP.NET, Active Directory).
  • Add troubleshooting steps and migration caveats specific to Linux distributions, not just Windows Server versions.
  • Avoid using Windows-specific terminology or tools exclusively; when mentioning PowerShell or Windows tools, also mention or link to Linux alternatives.
GitHub Create Pull Request
Migrate Create project ...zure-docs/blob/main/articles/migrate/create-project.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in several ways: all command-line examples for Az CLI are shown in PowerShell, with explicit instructions to 'open PowerShell as Administrator'; there are no Linux or macOS shell examples or instructions; and the workflow assumes familiarity with Windows tools and patterns, such as PowerShell and the concept of running as Administrator. There is no mention of Linux equivalents, nor are Linux-specific considerations addressed.
Recommendations
  • Provide Az CLI examples for Bash/zsh shells, including instructions for Linux and macOS users.
  • Replace or supplement 'open PowerShell as Administrator' with cross-platform guidance, such as 'open your terminal with appropriate privileges'.
  • Explicitly mention that Az CLI works on Linux, macOS, and Windows, and link to installation instructions for all platforms.
  • Add screenshots or instructions that reflect Linux/macOS environments where relevant.
  • Review and update any terminology or steps that are Windows-specific to ensure cross-platform applicability.
GitHub Create Pull Request
Migrate Questions about assessments in Azure Migrate ...icles/migrate/common-questions-discovery-assessment.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page for Azure Migrate assessments demonstrates a Windows bias by consistently referencing Windows-centric technologies (Hyper-V, SQL Server, IIS), providing examples and troubleshooting steps that are specific to Windows environments, and omitting explicit Linux server or workload examples. Windows tools and patterns (e.g., dynamic memory in Hyper-V, IIS for web apps, SQL Server) are mentioned exclusively or before any Linux equivalents, and there is a lack of guidance for Linux-based workloads, such as Apache, Nginx, or MySQL/MariaDB. This may make the documentation less accessible or useful for users migrating Linux servers and applications.
Recommendations
  • Add explicit examples and troubleshooting steps for Linux servers and workloads (e.g., Apache, Nginx, MySQL, PostgreSQL) in assessment scenarios.
  • Include Linux-specific migration considerations, such as differences in performance counters, agent installation, and readiness checks for common Linux distributions.
  • Provide parity in documentation by mentioning Linux environments alongside Windows/Hyper-V/SQL Server/IIS in all relevant sections.
  • Reference Linux tools and patterns (e.g., systemd, cron, Linux disk and memory management) where appropriate.
  • Clarify whether Azure Migrate supports discovery and assessment of Linux workloads and provide links to Linux-specific tutorials or guides.
GitHub Create Pull Request
Migrate Automate agentless VMware migrations in Azure Migrate ...lob/main/articles/migrate/how-to-automate-migration.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a strong Windows bias by exclusively using PowerShell scripts and modules for automation, referencing only Windows-centric tools (Azure PowerShell, .ps1 scripts), and omitting any mention of Linux-compatible alternatives (such as Bash, Azure CLI, or cross-platform scripting). All examples, installation instructions, and execution steps are tailored to Windows/PowerShell environments, with no guidance for Linux users or those preferring non-PowerShell automation.
Recommendations
  • Provide equivalent automation examples using Azure CLI and Bash scripts, which are natively supported on Linux and macOS.
  • Include installation and usage instructions for Azure CLI alongside Azure PowerShell, highlighting cross-platform compatibility.
  • Offer sample scripts or templates in Bash or Python for key migration steps, and document how to use them with the CSV input file.
  • Explicitly state platform requirements and clarify which steps/tools are Windows-only, while suggesting alternatives for Linux users.
  • Reference cross-platform documentation and repositories, ensuring Linux users can follow the migration process without needing PowerShell.
GitHub Create Pull Request
Migrate Set Up Least Privileged Accounts ...les/migrate/best-practices-least-privileged-account.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation demonstrates a Windows bias by frequently presenting Windows examples and instructions before Linux equivalents, providing detailed step-by-step GUI instructions for Windows tools (e.g., WMI Control) while offering more generic or less detailed instructions for Linux. Windows-specific tools and patterns (such as WinRM, WMI, and Windows authentication for SQL Server) are described in depth, while Linux instructions are often condensed or lack parity in detail and troubleshooting guidance. SQL Server examples are exclusively Windows-centric, with no mention of Linux-based SQL Server deployments. The Hyper-V section is Windows-only, and PowerShell or Windows command-line patterns are referenced without Linux alternatives.
Recommendations
  • Provide Linux examples and instructions alongside Windows, ensuring equal detail and troubleshooting guidance (e.g., step-by-step for configuring sudoers, ACLs, and service restarts).
  • Include Linux-based SQL Server deployment instructions and authentication examples, or clarify if only Windows SQL Server is supported.
  • Offer parity in troubleshooting steps for Linux (e.g., how to verify permissions, restart relevant services, check logs), similar to the Windows WMI/WinRM guidance.
  • Where Windows tools (such as WMI Control) are referenced, provide Linux equivalents (e.g., commands to check DMI, system info, or permissions).
  • Avoid presenting Windows instructions first by interleaving or grouping Windows and Linux guidance together.
  • Expand the Hyper-V section to clarify Linux support or alternatives if applicable, or explicitly state platform limitations.
GitHub Create Pull Request
Migrate Automate migration of machines in Azure Migrate .../blob/main/articles/migrate/how-to-migrate-at-scale.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation exclusively references PowerShell scripts for automating Azure Migrate tasks, with all script examples and tooling based on .ps1 files. There is no mention of Bash, shell, or cross-platform alternatives, nor are Linux-specific instructions or examples provided. The use of PowerShell and Windows-centric scripting is assumed throughout, which may exclude Linux administrators or environments.
Recommendations
  • Provide equivalent Bash or shell script samples for Linux users, or clarify how to run the migration tasks from Linux/macOS environments.
  • Document prerequisites and installation steps for PowerShell Core on Linux/macOS, if PowerShell is required cross-platform.
  • Include explicit notes about cross-platform compatibility of the scripts, and test them on Linux environments.
  • Offer guidance or links to Azure CLI-based migration automation, if available, as an alternative to PowerShell.
  • Reorder or balance examples so that Linux and Windows approaches are presented equally, rather than Windows/PowerShell first and exclusively.
GitHub Create Pull Request
Migrate Support for physical discovery and assessment in Azure Migrate and Modernize ...in/articles/migrate/migrate-support-matrix-physical.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in several ways: Windows tools and patterns (such as PowerShell, WinRM, and WMI) are referenced first and in more detail than their Linux equivalents. Example scripts and configuration instructions are provided only for Windows authentication and SQL Server on Windows, with Linux support often mentioned as 'not supported' or lacking equivalent detail. Windows-specific requirements (such as user groups and file paths) are listed explicitly, while Linux requirements are referenced via external links or summarized briefly. SQL Server and ASP.NET web app discovery are supported only on Windows, with Linux support missing or limited.
Recommendations
  • Provide Linux-specific example scripts and configuration instructions where possible, especially for authentication, permissions, and supported workloads.
  • Ensure Linux requirements are described in equal detail to Windows, including explicit command examples, user/group requirements, and file paths.
  • Where features are Windows-only (e.g., SQL Server discovery, ASP.NET web apps), clarify the roadmap for Linux parity or offer alternative solutions for Linux users.
  • Avoid referencing Windows tools (PowerShell, WinRM, WMI) before Linux equivalents; present both platforms in parallel where possible.
  • Include troubleshooting and setup guides for Linux environments directly in the documentation, rather than linking out.
  • Explicitly state limitations for Linux support and provide guidance or workarounds for Linux users.
GitHub Create Pull Request
Migrate Azure Migrate replication appliance ...main/articles/migrate/migrate-replication-appliance.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation for the Azure Migrate replication appliance demonstrates a strong Windows bias. All operating system requirements, examples, and instructions are centered around Windows Server (2016/2012 R2). There is no mention of Linux as a supported OS for the replication appliance, nor are there any Linux-specific deployment instructions, examples, or requirements. All paths, installer references, and configuration details (e.g., C:\Temp\ASRSetup, .msi installers, Windows Server roles, group policies, IIS settings) are Windows-centric. Even for physical server deployments, only Windows is referenced, with no parity for Linux environments.
Recommendations
  • Explicitly state whether Linux is supported as a replication appliance OS. If not, clarify this limitation.
  • If Linux is supported, provide equivalent instructions for deploying the replication appliance on Linux, including supported distributions, required packages, and configuration steps.
  • Include Linux-specific examples for MySQL installation, directory paths, and service management.
  • Mention Linux alternatives for Windows-specific tools and settings (e.g., group policies, IIS, .NET Framework).
  • Provide parity in troubleshooting, upgrade, and maintenance instructions for Linux environments.
  • If only Windows is supported, consider adding a rationale and guidance for Linux-only environments (e.g., alternatives, workarounds, or roadmap for future support).
GitHub Create Pull Request
Migrate Prepare machines for agentless migration with Azure Migrate ...in/articles/migrate/prepare-for-agentless-migration.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in several ways: Windows configuration steps and tooling (e.g., diskpart, PowerShell) are presented first and in greater detail, with screenshots and explicit command examples. Windows-specific tools and patterns (diskpart, registry editing, PowerShell) are highlighted, while Linux equivalents are less emphasized or omitted. Linux instructions are more generic, with fewer concrete command examples and less step-by-step guidance, especially for distributions other than RedHat. There is a lack of parity in illustrative examples and troubleshooting steps for Linux compared to Windows.
Recommendations
  • Provide Linux command-line examples for all major steps, similar to the detailed Windows examples (e.g., for DHCP configuration, agent installation, network setup) and include screenshots where possible.
  • Include troubleshooting guidance and verification steps for Linux (e.g., how to check agent status, validate driver installation, confirm network configuration) in parity with Windows.
  • Present Linux and Windows instructions in parallel sections or side-by-side, rather than listing Windows first and in more detail.
  • Reference Linux tools and patterns (e.g., systemctl, nmcli, /etc/network/interfaces, journalctl) where appropriate, and provide distribution-specific instructions for common distros (Ubuntu, Debian, SUSE, etc.).
  • Expand manual preparation instructions for Linux to match the depth and clarity of the Windows section, including more explicit steps for less common distributions.
GitHub Create Pull Request
Migrate Support for Hyper-V migration in Azure Migrate ...es/migrate/migrate-support-matrix-hyper-v-migration.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by listing Windows Server versions and requirements first and in detail, referencing Windows-specific tools and patterns (such as RDP, Windows Firewall, .NET Framework), and providing more granular instructions for Windows than Linux. Linux requirements and post-migration steps are described in less detail, and Linux-specific migration nuances are less emphasized. There are no Linux command-line examples or references to Linux-native tools, and the documentation assumes familiarity with Windows-centric administration.
Recommendations
  • Provide Linux-specific examples and instructions with equal detail, including command-line steps (e.g., SSH setup, firewall configuration using iptables or firewalld).
  • List Linux and Windows requirements in parallel, not with Windows first or in more detail.
  • Reference Linux-native tools and patterns (e.g., SELinux, systemd, ufw) where relevant.
  • Include troubleshooting steps and migration caveats for popular Linux distributions, similar to the Windows Server 2003 integration services note.
  • Ensure parity in post-migration connectivity instructions, including details for configuring SSH, public keys, and Linux firewalls.
  • Add links to Linux-specific migration guides and best practices.
GitHub Create Pull Request
Migrate Troubleshoot network connectivity issues | Microsoft Docs .../articles/migrate/troubleshoot-network-connectivity.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by providing command-line examples (such as nslookup) exclusively in Windows syntax, referencing Windows paths (e.g., c:\>), and recommending the use of PowerShell's Test-NetConnection for connectivity checks. There are no Linux-specific examples, tools, or instructions (e.g., using dig, host, or netcat), and troubleshooting steps assume a Windows environment for the on-premises appliance. Windows tools and patterns are mentioned first and exclusively, with no parity for Linux users.
Recommendations
  • Add Linux-specific command-line examples for DNS resolution (e.g., dig, host) alongside nslookup.
  • Include Linux equivalents for connectivity testing, such as nc (netcat), curl, or telnet, in addition to PowerShell's Test-NetConnection.
  • Clarify that the appliance may be hosted on Linux and provide troubleshooting steps for both Windows and Linux environments.
  • Show file paths and editing instructions for Linux (e.g., /etc/hosts) as well as Windows (e.g., C:\Windows\System32\drivers\etc\hosts).
  • Explicitly mention cross-platform support and provide screenshots or terminal outputs from Linux systems where appropriate.
GitHub Create Pull Request
Migrate Troubleshoot issues with agentless and agent-based dependency analysis ...lob/main/articles/migrate/troubleshoot-dependencies.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a Windows bias in several ways: Windows tools and troubleshooting steps (PowerShell, WinRM, WMI, Registry Editor, Control Panel) are mentioned first and in greater detail than their Linux equivalents. Many error codes and remediation steps focus on Windows-specific technologies, with Linux guidance often appearing later or in less detail. Some troubleshooting and validation examples are provided only for Windows (e.g., Registry Editor, WMI configuration), and Linux instructions are sometimes missing or less emphasized.
Recommendations
  • Ensure Linux troubleshooting steps are provided alongside Windows steps for all error codes, especially where only Windows tools (e.g., Registry Editor, WMI, PowerShell) are referenced.
  • Present Linux and Windows instructions in parallel, rather than listing Windows first or in more detail.
  • Include Linux-specific error codes and remediation steps where applicable, such as SELinux/AppArmor, systemd, SSH configuration, and file permissions.
  • Provide Linux command-line examples and configuration steps for all scenarios where Windows commands (PowerShell, Registry Editor) are given.
  • Clarify when a step is Windows-only and offer equivalent Linux guidance or explicitly state if not applicable.
  • Expand Linux troubleshooting for agent-based analysis, including guidance for common Linux agent installation and connectivity issues.
  • Review and balance the depth of examples and explanations for both platforms to ensure parity.
GitHub Create Pull Request
Migrate Assess Hyper-V VMs for migration to Azure VMs with Azure Migrate .../blob/main/articles/migrate/tutorial-assess-hyper-v.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation is heavily focused on assessing Hyper-V VMs, which are a Windows-centric virtualization technology. There are no Linux-specific examples, tools, or migration scenarios mentioned. Windows licensing options (Azure Hybrid Benefit for Windows Server) are described before Linux equivalents (RHEL/SLES), and the overall workflow assumes a Windows/Hyper-V environment. There is no mention of Linux-based hypervisors (such as KVM or Xen), nor are there examples or guidance for assessing Linux VMs or environments.
Recommendations
  • Add equivalent tutorials and examples for assessing Linux-based VMs and environments (e.g., KVM, Xen, or other Linux hypervisors).
  • Provide Linux-specific migration considerations, such as licensing, disk formats, and compatibility issues.
  • Ensure that Linux licensing options (RHEL/SLES) are described with equal prominence and detail as Windows Server options.
  • Include cross-platform discovery and assessment workflows, showing both Windows and Linux VM scenarios.
  • Add explicit examples and screenshots for Linux VM assessment and migration, not just Hyper-V/Windows.
GitHub Create Pull Request
Migrate Discover, assess, and migrate Amazon Web Services (AWS) EC2 VMs to Azure ...icles/migrate/tutorial-migrate-aws-virtual-machines.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation exhibits a Windows bias in several areas: Windows Server is the only supported OS for the required replication appliance, and Windows-specific ports and protocols (WinRM, WMI) are mentioned before Linux equivalents. There are more detailed instructions and references for Windows (e.g., troubleshooting, activation issues, Azure Hybrid Benefit for Windows), while Linux guidance is less prominent or missing in some steps. Some sections lack Linux-specific examples or parity in troubleshooting and post-migration steps.
Recommendations
  • Provide parity in instructions and examples for Linux environments, especially in troubleshooting and post-migration steps.
  • Offer a Linux-based option for the replication appliance, or clearly state if this is not possible and explain the rationale.
  • List Linux and Windows steps together, or alternate which OS is mentioned first to avoid a 'Windows-first' impression.
  • Include Linux-specific troubleshooting guidance (e.g., activation, networking, common migration issues) similar to the Windows sections.
  • Expand on post-migration best practices for Linux VMs, such as SELinux/AppArmor adjustments, cloud-init deactivation, and Linux-specific security recommendations.
  • Clarify any limitations or differences in feature support between Windows and Linux migrations up front.
GitHub Create Pull Request
Migrate Assess ASP.NET/Java web apps for migration to Azure Kubernetes Service ...ob/main/articles/migrate/tutorial-assess-aspnet-aks.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by prioritizing ASP.NET (Windows-centric) scenarios, referencing Windows node pools as a requirement for ASP.NET apps, and linking to Windows Dockerfile optimization. There is a lack of Linux-specific examples, guidance, or parity for Java apps, which typically run on Linux. The documentation does not mention Linux node pools, Linux container best practices, or provide Linux-centric migration steps.
Recommendations
  • Add explicit guidance and examples for Linux node pools, especially for Java web apps, including cost breakdowns and readiness assessments.
  • Include links to Linux Dockerfile optimization and best practices for Linux containers in AKS.
  • Clarify when to use Windows vs. Linux node pools based on app type, and provide migration steps for both environments.
  • Ensure screenshots and instructions show both Windows and Linux scenarios where applicable.
  • Balance references to Windows tools with equivalent Linux tools and patterns, such as referencing Linux container management and troubleshooting resources.
GitHub Create Pull Request
Migrate Troubleshoot network connectivity issues | Microsoft Docs .../articles/migrate/troubleshoot-network-connectivity.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by consistently providing command-line examples (such as nslookup and Test-NetConnection) using Windows syntax and PowerShell, referencing Windows-style file paths (e.g., c:\>), and omitting equivalent Linux or cross-platform instructions. There is no mention of Linux tools (such as dig, host, or netcat), nor are Linux-specific troubleshooting steps or screenshots included. The guidance for editing the hosts file and running commands is tailored to Windows environments, with no parity for Linux users.
Recommendations
  • Include Linux equivalents for all command-line examples, such as using 'dig' or 'host' for DNS resolution and 'nc' or 'telnet' for connectivity tests.
  • Provide instructions for editing the /etc/hosts file on Linux systems alongside Windows hosts file guidance.
  • Add screenshots or terminal output examples from Linux environments where relevant.
  • Explicitly mention that the troubleshooting steps apply to both Windows and Linux appliances, and clarify any OS-specific differences.
  • Where PowerShell is referenced (e.g., Test-NetConnection), also provide the corresponding Linux command (e.g., 'nc -zv <host> <port>').
GitHub Create Pull Request
Migrate Set Up Least Privileged Accounts ...les/migrate/best-practices-least-privileged-account.md
High Priority View Details →
Scanned: 2026-01-10 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 examples, tools, and configuration steps are frequently presented first and in greater detail, especially for server discovery and database setup. Windows-specific tools (WMI Control, WinRM, user group memberships) are described with step-by-step instructions and screenshots, while Linux equivalents are covered more briefly and sometimes lack comparable detail or visual aids. SQL Server (Windows-centric) is given extensive coverage, whereas MySQL (Linux-friendly) is treated more succinctly. Powershell and Windows GUI steps are included, but Linux command-line alternatives are less emphasized.
Recommendations
  • Provide Linux configuration steps with the same level of detail as Windows, including screenshots or command outputs where appropriate.
  • Include Linux-first examples in sections where Windows is currently presented first, or alternate the order to balance coverage.
  • Expand Linux database discovery instructions, including step-by-step guides for MySQL and other common Linux databases.
  • Add troubleshooting tips and best practices for Linux environments, similar to those provided for Windows (e.g., permissions, service restarts).
  • Ensure parity in sample commands, showing both Windows (Powershell/GUI) and Linux (shell/CLI) approaches side by side.
  • Reference Linux tools and patterns (e.g., systemd, journalctl, SELinux) where relevant, not just Windows tools.
GitHub Create Pull Request
Migrate Questions about Wave Planning in Azure Migrate ...ain/articles/migrate/common-questions-wave-planning.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page for Wave Planning in Azure Migrate demonstrates a Windows bias by listing PowerShell as a primary example for exporting data, mentioning Windows-centric tools before Linux alternatives, and omitting explicit Linux command-line examples. The Azure CLI is mentioned, but PowerShell is listed first and no Linux-specific guidance is provided.
Recommendations
  • Include explicit Linux command-line examples (e.g., bash scripts, Linux shell usage) for tasks such as exporting data.
  • List Azure CLI before PowerShell to avoid Windows-first ordering, or present both equally.
  • Mention cross-platform compatibility for all tools, clarifying which commands work on Linux, macOS, and Windows.
  • Add examples using Linux-native tools (e.g., curl, jq) for interacting with REST APIs.
  • Provide screenshots or instructions from Linux environments where applicable.
GitHub Create Pull Request
Migrate Automate agentless VMware migrations in Azure Migrate ...lob/main/articles/migrate/how-to-automate-migration.md
High Priority View Details →
Scanned: 2026-01-10 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 exclusively describes automation of VMware migrations in Azure Migrate using PowerShell scripts and modules, with all examples, instructions, and tooling focused on PowerShell (.ps1 scripts, Az PowerShell module). There is no mention of Bash, Linux shell, Azure CLI, or cross-platform scripting alternatives. Prerequisites and installation steps assume a Windows/PowerShell environment, and there are no Linux-specific instructions or parity examples.
Recommendations
  • Provide equivalent automation examples using Azure CLI and Bash scripts for Linux/macOS users.
  • Explicitly state platform compatibility for the PowerShell scripts (e.g., whether they work with PowerShell Core on Linux/macOS).
  • Add installation instructions for PowerShell Core on Linux/macOS, if supported.
  • Include troubleshooting notes for running scripts on non-Windows platforms.
  • Offer sample scripts or guidance for users who prefer Bash or Python for automation.
  • Mention any limitations or differences when running Azure Migrate automation from Linux/macOS environments.
GitHub Create Pull Request
← Previous Page 6 of 37 Next →