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 26-50 of 918 flagged pages
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-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation exhibits a Windows bias by requiring Windows PowerShell 4.0 on IIS servers for migration, with no mention of Linux or cross-platform alternatives. There are no Linux-specific instructions, examples, or tools provided, and the migration flow appears to be designed exclusively for Windows/IIS environments.
Recommendations
  • Clarify whether Linux-hosted ASP.NET web apps (e.g., on Apache, Nginx, or Kestrel) are supported and provide instructions if so.
  • If migration is Windows/IIS-only, explicitly state this limitation early in the documentation.
  • If Linux migration is possible, add Linux-specific prerequisites, tooling, and step-by-step instructions.
  • Provide parity in examples and tooling for Linux environments, such as Bash scripts or cross-platform CLI commands.
  • Reference Linux-compatible migration tools if available, or suggest alternatives for Linux users.
GitHub Create Pull Request
Migrate Troubleshoot replication issues in agentless VMware VM migration ...ate/troubleshoot-changed-block-tracking-replication.md
High Priority View Details →
Scanned: 2026-01-13 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 consistently assumes the Azure Migrate appliance is a Windows system. Troubleshooting steps rely heavily on Windows-specific tools (PowerShell, MMC snap-in, services.msc, command prompt), and all command-line examples use PowerShell or Windows command syntax. There are no Linux/macOS equivalents or guidance for users running the appliance on non-Windows platforms, nor is there mention of cross-platform alternatives for key troubleshooting actions.
Recommendations
  • Provide Linux/macOS equivalents for all PowerShell and Windows command prompt examples (e.g., using bash, curl, or relevant Linux utilities).
  • Include instructions for checking and managing services on Linux (e.g., using systemctl or service commands) alongside Windows steps.
  • Mention cross-platform tools where possible (e.g., azcopy is available for Linux/macOS; show usage examples for those platforms).
  • Clarify whether the Azure Migrate appliance must be Windows-only, or update documentation to reflect support for Linux-based appliances if applicable.
  • Reorder examples so that cross-platform or OS-neutral steps appear before Windows-specific instructions.
  • Avoid assuming remote desktop access is only via Windows; mention SSH for Linux appliances.
GitHub Create Pull Request
Migrate Azure App Containerization ASP.NET; Containerization and migration of ASP.NET applications to Azure Kubernetes. ...ate/tutorial-app-containerization-aspnet-kubernetes.md
High 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 is heavily biased towards Windows environments for ASP.NET app containerization. All instructions, prerequisites, and tooling are Windows-specific, requiring Windows OS, PowerShell, and Microsoft Web Deploy. There are no Linux or macOS alternatives or examples for ASP.NET containerization, and all code samples and troubleshooting steps assume a Windows platform. Linux is only mentioned as a target for Java web apps, not ASP.NET.
Recommendations
  • Clarify early that ASP.NET containerization is only supported on Windows, and explicitly state lack of Linux/macOS support.
  • If possible, provide parity for Linux/macOS users by offering a cross-platform version of the tool or CLI.
  • Include alternative manual containerization steps for ASP.NET apps on Linux (e.g., using .NET Core, Docker, and standard Linux tools), or link to relevant guides.
  • Add troubleshooting and artifact location instructions for non-Windows platforms if/when support is added.
  • Present prerequisites and examples for both Windows and Linux/macOS where applicable, or clearly segregate them by platform.
GitHub Create Pull Request
Migrate Security Best Practices for Deploying an Appliance .../blob/main/articles/migrate/best-practices-security.md
High 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 exhibits a strong Windows bias. It exclusively references Windows Server as the supported OS for the Azure Migrate appliance, provides only PowerShell-based installation instructions, and recommends Windows-specific hardening tools (security baselines, compliance toolkit, GPOs). Linux is only mentioned in the context of network port access, with no guidance for deploying or securing the appliance on Linux or macOS platforms. There are no Linux/macOS installation or hardening examples, and all operational recommendations assume a Windows environment.
Recommendations
  • Clarify whether the Azure Migrate appliance can be deployed on Linux or macOS. If not, explicitly state Windows-only support.
  • If Linux deployment is supported, provide equivalent installation instructions (e.g., Bash scripts, Linux package formats).
  • Include Linux-specific hardening guidance, such as CIS benchmarks, SELinux/AppArmor, and relevant security tools.
  • Offer parity in credential management and OS patching recommendations for Linux (e.g., using keyrings, sudoers, package managers).
  • Present examples for both Windows and Linux environments, or clearly indicate platform limitations.
GitHub Create Pull Request
Migrate Support matrix for web apps migration ...ob/main/articles/migrate/concepts-migration-webapps.md
High 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 Windows-centric, focusing exclusively on migration of ASP.NET web apps from Windows IIS servers. Linux servers are explicitly marked as unsupported, and requirements such as Windows PowerShell 4.0 further reinforce the Windows-only approach. No Linux or cross-platform migration paths, examples, or tools are mentioned.
Recommendations
  • Clearly state Linux/macOS limitations at the top of the page to set expectations.
  • Provide a roadmap or guidance for Linux web app migration scenarios, even if not currently supported.
  • Include links to alternative migration strategies for Linux-based web apps (e.g., containerization, manual migration).
  • If possible, add parity for Linux environments in future releases and update documentation accordingly.
  • Offer contact or feedback channels for users needing Linux support.
GitHub Create Pull Request
Migrate Register Azure Migrate appliance using a preconfigured Microsoft Entra ID application ...s/migrate/how-to-register-appliance-using-entra-app.md
High Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation is heavily biased toward Windows environments. All command-line examples use PowerShell, certificate export instructions reference Windows file paths and GUI dialogs, and registry modification steps are Windows-specific. While certificate generation tools for Linux (OpenSSL, mkcert) are mentioned, no Linux/macOS commands or workflows are provided. The registry update and certificate installation steps are only described for Windows, leaving Linux/macOS users without guidance.
Recommendations
  • Provide Linux/macOS equivalents for certificate generation and export (e.g., OpenSSL commands).
  • Include instructions for installing certificates on Linux/macOS appliances, such as using 'openssl' and updating certificate stores.
  • Clarify whether the registry update step is required on Linux/macOS, and if so, provide the appropriate method (e.g., config file or environment variable updates).
  • Add notes or sections for cross-platform differences, ensuring parity in appliance registration steps.
  • Avoid using Windows file paths and GUI screenshots exclusively; include Linux/macOS alternatives.
GitHub Create Pull Request
Migrate Set up an Azure Migrate scale-out appliance for agentless VMware migration ...ain/articles/migrate/how-to-scale-out-for-migration.md
High Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Missing Linux Example Windows First
Summary
The documentation is heavily biased towards Windows environments. All instructions for deploying and configuring the Azure Migrate scale-out appliance assume the use of Windows Server (2019/2022), PowerShell scripts, and Windows-specific tools (CertUtil, IIS, registry keys, etc.). There are no examples or guidance for Linux-based deployments, nor are alternative methods or parity tools mentioned for non-Windows users. The documentation does not acknowledge or support Linux or macOS as viable platforms for appliance hosting or management.
Recommendations
  • Explicitly state Windows-only requirements early in the prerequisites section.
  • If possible, provide Linux-based deployment options or clarify why Linux is unsupported.
  • Offer parity examples for checksum validation using Linux tools (e.g., sha256sum).
  • Mention alternatives for PowerShell scripts (e.g., Bash scripts) if supported.
  • Clarify whether appliance management (browser-based config manager) can be accessed from non-Windows clients.
  • Add a section addressing Linux/macOS user scenarios, even if only to state limitations.
GitHub Create Pull Request
Migrate Set up an Azure Migrate appliance for physical servers ...n/articles/migrate/how-to-set-up-appliance-physical.md
High 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 for setting up an Azure Migrate appliance for physical servers is heavily biased towards Windows environments. All setup and installation instructions rely on PowerShell, Windows administrative privileges, and Windows-specific tools (IIS, Windows Activation Service, Registry Editor, etc.). There are no Linux/macOS equivalents or alternative instructions, and Windows terminology and examples are presented exclusively and first throughout the guide.
Recommendations
  • Provide Linux/macOS installation instructions, including shell script alternatives to PowerShell.
  • Document Linux prerequisites and supported distributions for hosting the appliance.
  • Clarify whether the appliance can be hosted on non-Windows OS; if not, state this explicitly and provide rationale.
  • If Linux hosting is supported, offer step-by-step instructions for extraction, installation, and configuration using Linux-native tools.
  • Include troubleshooting steps and log file locations for Linux systems.
  • Present cross-platform examples side-by-side or in parallel sections to improve parity.
GitHub Create Pull Request
Migrate Set up an Azure Migrate appliance for Hyper-V ...in/articles/migrate/how-to-set-up-appliance-hyper-v.md
High 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 is heavily focused on Windows environments, specifically Hyper-V, and consistently provides Windows-centric instructions and tooling (e.g., Hyper-V Manager, PowerShell commands, CertUtil, Local Group Policy Editor). Linux equivalents are not mentioned, and Linux users are only referenced in the context of providing credentials for discovery, not for appliance setup or management. All example commands and screenshots are Windows-specific, and there is no guidance for Linux or macOS users who may wish to deploy or interact with the appliance.
Recommendations
  • Add explicit notes clarifying platform requirements and limitations (e.g., 'This appliance setup is only supported on Windows/Hyper-V hosts').
  • If possible, provide alternative instructions or tooling for Linux/KVM environments, or link to documentation for non-Hyper-V scenarios.
  • Include Linux/macOS command equivalents for steps like file hash verification (e.g., 'sha256sum' or 'openssl dgst') where relevant.
  • Clarify whether the appliance can be managed or accessed from non-Windows systems, and provide guidance for those scenarios.
  • Ensure parity in credential validation and discovery instructions for Linux servers, including required permissions and troubleshooting steps.
GitHub Create Pull Request
Migrate Azure Migrate appliance ...e-docs/blob/main/articles/migrate/migrate-appliance.md
High 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 for Azure Migrate appliance is heavily biased towards Windows environments. All deployment scenarios, hardware requirements, and examples assume or require Windows Server (2019/2022/2025) as the host OS. PowerShell is the only installer script mentioned, and all verification and upgrade instructions use Windows-specific tools (CertUtil, Registry Editor, Control Panel). There are no Linux/macOS deployment or management examples, and Linux is only mentioned as a target for discovery, not as a platform for hosting the appliance.
Recommendations
  • Provide explicit documentation for deploying and managing the appliance on Linux hosts, if supported.
  • Include Linux/macOS equivalents for file hash verification (e.g., sha256sum, openssl).
  • Offer Bash or cross-platform installer scripts, or clarify platform limitations.
  • List Linux deployment options and requirements alongside Windows in all relevant tables and sections.
  • Add screenshots and step-by-step instructions for Linux/macOS where applicable.
  • If appliance cannot run on Linux/macOS, clearly state this limitation early in the documentation.
GitHub Create Pull Request
Migrate How does Hyper-V migration work in Azure Migrate? ...ain/articles/migrate/hyper-v-migration-architecture.md
High 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 is heavily focused on Windows/Hyper-V environments, with all examples and instructions referencing Windows-specific tools (MMC snap-in, Regedit, Windows registry paths). There are no Linux or macOS equivalents or alternative instructions provided, and the workflow assumes a Windows administrative context throughout.
Recommendations
  • Clarify at the beginning that the migration process described is specific to Hyper-V (a Windows-only virtualization platform), and that the tooling and examples are not applicable to Linux hosts.
  • If Azure Migrate supports agentless migration from Linux-based hypervisors (e.g., KVM, VMware on Linux), provide parallel documentation or links for those scenarios.
  • Where possible, mention whether similar bandwidth throttling or upload thread controls exist for Linux-based migration appliances, and provide instructions if available.
  • Add a section explicitly stating platform requirements and limitations, so Linux/macOS administrators are aware of the scope.
  • If the migration tool has a cross-platform interface (e.g., web portal), highlight which steps are platform-agnostic.
GitHub Create Pull Request
Migrate Create a custom account with minimal metadata for discovery and assessment. ...b/main/articles/migrate/least-privilege-credentials.md
High 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 exclusively references Windows tools and patterns, such as the use of %ProgramFiles% paths, Windows/Domain Account credentials, and a Windows-specific executable (MinimumPrivilegedUser.exe). There are no examples or instructions for Linux or macOS environments, nor any mention of Linux authentication methods or file paths. The guidance assumes a Windows environment throughout.
Recommendations
  • Provide instructions for running the utility on Linux/macOS, or clarify if it is Windows-only.
  • Include Linux-specific examples, such as file paths, authentication methods, and command-line usage.
  • If the utility is not compatible with Linux, explicitly state this limitation and suggest alternative methods for Linux users.
  • Mention Linux equivalents for SQL Server authentication and account provisioning, if available.
  • Ensure parity in documentation structure and example order (e.g., show Linux/macOS examples alongside Windows).
GitHub Create Pull Request
Migrate Azure Migrate replication appliance ...main/articles/migrate/migrate-replication-appliance.md
High 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 for the Azure Migrate replication appliance is heavily Windows-centric. All operating system requirements, examples, and instructions reference Windows Server (2016/2012 R2) exclusively, with no mention of Linux or macOS support. Software installation paths and instructions (e.g., MySQL installer in C:\Temp\ASRSetup) are Windows-specific, and all references to system configuration, licensing, and roles are for Windows Server. There are no Linux equivalents, examples, or guidance, and the documentation does not clarify if Linux-based appliances are supported or possible.
Recommendations
  • Clarify whether Linux-based replication appliances are supported. If not, explicitly state Windows-only support.
  • If Linux is supported, provide equivalent Linux instructions, including OS requirements, installation steps, and configuration paths.
  • Offer Linux-specific examples for MySQL installation and other required software.
  • List Linux system requirements and configuration recommendations alongside Windows ones.
  • Include notes on cross-platform limitations and alternatives for non-Windows users.
GitHub Create Pull Request
Migrate Troubleshoot Windows upgrade issues ...ocs/blob/main/articles/migrate/troubleshoot-upgrade.md
High 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 exclusively addresses Windows OS upgrade issues and provides troubleshooting steps tailored to Windows environments. All examples, recommendations, and linked resources are Windows-specific, with no mention of Linux or macOS upgrade scenarios, tools, or parity. The guidance assumes the user is working with Windows VMs and Windows disk management, and does not offer Linux equivalents or considerations.
Recommendations
  • Add sections or notes for Linux VM upgrade troubleshooting, including common issues and solutions.
  • Provide parity in disk management instructions for Linux VMs, such as expanding disks using Linux tools (e.g., fdisk, parted, resize2fs).
  • Include links to Linux-specific documentation for in-place upgrades and disk space requirements.
  • Clarify whether the migration and modernization tool supports Linux OS upgrades, and if not, explicitly state the limitation.
  • Present examples for both Windows and Linux environments, or clearly indicate Windows-only applicability in the title and introduction.
GitHub Create Pull Request
Migrate ASP.NET app containerization and migration to App Service ...te/tutorial-app-containerization-aspnet-app-service.md
High 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 is heavily biased towards Windows environments for ASP.NET app containerization. All instructions, prerequisites, and tooling are Windows-specific, requiring Windows OS, PowerShell, and Windows-only tools (Web Deploy). There are no Linux/macOS alternatives or examples for ASP.NET containerization, and the workflow cannot be completed on non-Windows platforms. Linux is only mentioned in the context of Java/Tomcat apps, not ASP.NET.
Recommendations
  • Provide Linux/macOS-compatible tooling or document alternative workflows for ASP.NET app containerization.
  • Include Linux/macOS examples for installing and running the containerization process, or clarify platform limitations early.
  • Offer guidance for users who have ASP.NET apps hosted on Linux (e.g., via Mono or .NET Core) if supported.
  • Document manual containerization steps for ASP.NET apps on Linux/macOS, such as Dockerfile creation and deployment to Azure App Service.
  • Clearly state platform limitations in the introduction and prerequisites, and link to Linux/macOS alternatives where possible.
GitHub Create Pull Request
Migrate Troubleshoot slow replication or stuck migration in agentless VMware migration ...in/articles/migrate/troubleshoot-replication-vmware.md
High Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation page demonstrates Windows bias in the troubleshooting steps for the Azure Migrate appliance. Configuration changes on the appliance are described using Windows-specific tools and paths (e.g., '%programdata%', Remote Desktop, PowerShell commands), with no mention of Linux equivalents or guidance for non-Windows environments. Windows tools and patterns (Remote Desktop, PowerShell, Windows service control commands) are presented exclusively and before any consideration of Linux or cross-platform alternatives.
Recommendations
  • Provide equivalent instructions for Linux-based appliances, including file paths, service management commands (e.g., systemctl), and remote access methods (e.g., SSH).
  • Clarify whether the Azure Migrate appliance can run on Linux, and if so, include Linux-specific troubleshooting steps.
  • When giving examples, present both Windows and Linux approaches side-by-side, or indicate platform-specific sections.
  • Avoid assuming Remote Desktop and PowerShell are universally available; mention alternatives like SSH and bash for Linux/macOS users.
GitHub Create Pull Request
Migrate Troubleshoot web apps migration issues ...ain/articles/migrate/troubleshoot-webapps-migration.md
High Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Missing Linux Example Windows First
Summary
The documentation page is heavily focused on troubleshooting migration of IIS-based web apps using Azure Migrate, with repeated references to Windows-specific technologies such as IIS and PowerShell. All error codes and troubleshooting steps pertain to Windows environments, with no mention of Linux-based web servers (e.g., Apache, Nginx) or Linux migration scenarios. PowerShell is referenced as the primary tool for packaging and troubleshooting, and Windows roles/features (IIS Management Console) are assumed. There are no Linux/macOS examples, nor guidance for non-Windows users.
Recommendations
  • Add troubleshooting sections for Linux-based web app migrations (e.g., Apache, Nginx).
  • Include examples and error codes relevant to Linux environments.
  • Provide parity in tooling, such as Bash or shell script examples for Linux users.
  • Clarify in the introduction that the guidance is specific to Windows/IIS migrations, and link to Linux migration documentation if available.
  • List Linux troubleshooting steps alongside Windows steps where applicable.
GitHub Create Pull Request
Migrate Containerization and migration of Java web applications to Azure App Service. ...rate/tutorial-app-containerization-java-app-service.md
High Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example Powershell Heavy 🔧 Windows Tools
Summary
The documentation demonstrates a strong Windows bias: the Azure Migrate: App Containerization tool can only be installed and run on Windows machines, with no support or examples for Linux or macOS hosts. All installation instructions and troubleshooting steps are Windows-specific, including the use of PowerShell for installation and references to Windows file paths for logs. There are no Linux/macOS alternatives or parity in the tool's usage, despite the fact that the applications being containerized are running on Linux servers.
Recommendations
  • Develop and document a Linux/macOS version of the Azure Migrate: App Containerization tool, or provide a supported containerized version that can be run cross-platform.
  • Provide installation instructions and examples for Linux/macOS environments, including shell commands and file paths.
  • Offer troubleshooting guidance for non-Windows hosts.
  • Clearly state Windows-only limitations at the top of the documentation and link to alternative migration/containerization approaches for Linux/macOS users.
  • If Windows is required, suggest using a Windows VM in Azure or locally as a workaround, and provide guidance for setting this up.
GitHub Create Pull Request
Migrate Azure App Containerization Java; Containerization and migration of Java web applications to Azure Kubernetes. ...grate/tutorial-app-containerization-java-kubernetes.md
High 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 exhibits a strong Windows bias: the Azure Migrate: App Containerization tool is only available for Windows, all installation and operational steps require a Windows machine, and only PowerShell is used for installation. There are no instructions or alternatives for Linux or macOS users to run the tool natively, nor are there examples for installing or operating the tool on non-Windows platforms. Linux is only referenced as the target application server, not as a platform for running the migration tooling itself.
Recommendations
  • Provide a Linux-native version of the Azure Migrate: App Containerization tool, or document how to run the tool in a Linux environment (e.g., via container, VM, or Wine).
  • Include installation instructions for Linux/macOS, such as using Bash or shell scripts instead of PowerShell.
  • Offer guidance for users who do not have access to a Windows machine, including cloud-based or containerized options.
  • Clarify in prerequisites and introduction that a Windows machine is strictly required, and suggest alternatives or workarounds for Linux/macOS users.
  • Where possible, present cross-platform examples (e.g., Azure CLI commands) before or alongside Windows/PowerShell instructions.
GitHub Create Pull Request
Migrate Discover AWS instances with Azure Migrate Discovery and assessment ...cs/blob/main/articles/migrate/tutorial-discover-aws.md
High 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 a notable Windows bias. The Azure Migrate appliance is required to run on Windows Server (2019/2022), with no mention of Linux as a host OS. All setup and installation instructions rely exclusively on PowerShell scripts and Windows-specific tools (IIS, Windows Activation Service, registry edits), with no Linux equivalents or alternatives. Examples and screenshots are Windows-centric, and Linux instructions are limited to configuring SSH for discovery, not for appliance setup or management. This creates friction for users in Linux environments and may prevent Linux-only users from completing the tutorial.
Recommendations
  • Provide a Linux-based Azure Migrate appliance option (e.g., Ubuntu, RHEL) or clarify if Windows is strictly required.
  • Include Linux shell (bash) equivalents for installation and management steps, such as running installer scripts, configuring services, and troubleshooting.
  • Offer Linux-first or parallel examples for appliance setup, not just for target server discovery.
  • Document any limitations or rationale for Windows-only appliance deployment, and suggest alternatives for Linux-centric environments.
  • Ensure screenshots and walkthroughs include both Windows and Linux perspectives where applicable.
GitHub Create Pull Request
Migrate Discover servers on GCP instances with Azure Migrate Discovery and assessment ...cs/blob/main/articles/migrate/tutorial-discover-gcp.md
High 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 exhibits a notable Windows bias. The Azure Migrate appliance is required to run on Windows Server 2019 or 2022, with no mention of Linux-based appliance deployment. All setup and installation instructions rely exclusively on PowerShell scripts and Windows-specific tools (IIS, Windows Activation Service, registry edits), with no Linux alternatives or parity. Examples and screenshots are Windows-centric, and Linux instructions are limited to enabling SSH and root login, with no guidance for Linux-based appliance setup or troubleshooting.
Recommendations
  • Provide instructions and support for deploying the Azure Migrate appliance on Linux servers, including required dependencies and installation steps.
  • Offer Linux shell script equivalents for the PowerShell installer, or a cross-platform installer.
  • Include Linux-first or parallel examples for appliance setup, configuration, and troubleshooting.
  • Document Linux-specific requirements and troubleshooting steps for the appliance, such as log file locations, service management, and network configuration.
  • Clarify if Windows-only appliance deployment is a technical limitation, and if so, recommend alternative approaches for Linux-centric environments.
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
High 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 is heavily focused on Windows environments, specifically Windows Server and Hyper-V. All setup, preparation, and scripting examples use Windows tools (PowerShell, WinRM, CertUtil, Hyper-V Manager), with no Linux/macOS alternatives or parity. While Linux servers are supported for discovery, the appliance and all operational steps are Windows-centric, and Linux users are left without guidance for equivalent tasks.
Recommendations
  • Provide explicit guidance for deploying and managing the Azure Migrate appliance from Linux/macOS hosts, if supported.
  • Include Linux/macOS command-line alternatives for tasks like hash verification (e.g., sha256sum), remote management, and credential delegation.
  • Clarify whether the appliance can be run on non-Windows hypervisors or hosts, and document any limitations.
  • Add Linux/macOS-specific troubleshooting and setup instructions where relevant.
  • If Windows-only is a hard requirement, state this clearly at the top of the documentation.
GitHub Create Pull Request
Migrate Discover physical servers with Azure Migrate discovery and assessment ...ob/main/articles/migrate/tutorial-discover-physical.md
High 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 exhibits a notable Windows bias. Windows server setup instructions and account configuration details are presented first and in greater depth, including explicit PowerShell and Windows-specific tool usage. The installer script is described as requiring PowerShell and installs several Windows-only components (IIS, Windows Activation Service, registry keys), with no mention of Linux or cross-platform alternatives for appliance deployment. Linux instructions are limited to credential setup and sudoers configuration, with no guidance on running or installing the appliance on Linux. This creates friction for Linux users and may prevent them from completing the setup if they do not have access to a Windows environment.
Recommendations
  • Provide explicit instructions and examples for deploying and running the Azure Migrate appliance on Linux, including supported distributions and required dependencies.
  • Offer Linux shell (bash) equivalents for installer script execution, or clarify if appliance installation is Windows-only.
  • If the appliance cannot be installed on Linux, state this limitation clearly at the beginning of the documentation.
  • Balance the order and detail of Windows and Linux sections, presenting both platforms with equal prominence.
  • Include troubleshooting steps and log file locations for Linux deployments, similar to those provided for Windows.
GitHub Create Pull Request
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-13 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, particularly in the setup of the replication appliance, which requires a Windows Server VM. Instructions and screenshots for appliance setup are exclusively for Windows, with no Linux alternative or parity. Some sections (such as Mobility service installation) do provide Linux-specific steps, but the critical replication appliance component is Windows-only, creating a significant barrier for Linux-only environments.
Recommendations
  • Provide clear guidance on whether a Linux-based replication appliance is supported. If not, explicitly state that only Windows Server is supported and explain the rationale.
  • If possible, develop and document a Linux-based replication appliance option to support organizations that do not use Windows Server.
  • Wherever possible, offer Linux-first or Linux-parallel examples, especially for critical infrastructure components.
  • Ensure that all screenshots and step-by-step instructions are available for both Windows and Linux environments, or clarify limitations.
  • In troubleshooting and best practices, include Linux-specific issues and solutions alongside Windows ones.
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-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates Windows bias by explicitly requiring Windows PowerShell 4.0 on servers hosting IIS web servers for migration, with no mention of Linux or cross-platform alternatives. There are no examples or instructions for migrating from Linux-based ASP.NET hosting environments, nor any guidance for users who do not use Windows/IIS.
Recommendations
  • Clarify whether migration is supported only for IIS/Windows-hosted ASP.NET apps, or provide instructions/examples for Linux-hosted ASP.NET apps (e.g., on Apache, Nginx, or Kestrel).
  • If Linux migration is supported, add equivalent steps and tooling for Linux environments, such as Bash scripts or CLI commands.
  • Explicitly state platform limitations in prerequisites, so Linux/macOS users are aware of support boundaries.
  • Consider referencing cross-platform migration tools or approaches if available.
GitHub Create Pull Request
← Previous Page 2 of 37 Next →