Migrate

394
Total Pages
295
Linux-Friendly Pages
99
Pages with Bias
25.1%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

218 issues found
Showing 1-25 of 218 flagged pages
Migrate Support for Hyper-V assessment in Azure Migrate and Modernize ...ain/articles/migrate/migrate-support-matrix-hyper-v.md
High Priority View Details →
Scanned: 2026-01-13 06:17
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, with Windows Server versions and PowerShell remoting as core requirements for Hyper-V assessment. Windows tools and patterns (PowerShell, WinRM, WMI) are mentioned first and in detail, while Linux support is referenced but not elaborated with equivalent examples or tooling. Critical features such as SQL Server and ASP.NET web app discovery are not supported for Linux, and all sample scripts and configuration instructions are Windows-centric.
Recommendations
  • Provide Linux-specific examples and instructions where possible, especially for appliance deployment, credential setup, and dependency analysis.
  • Clarify Linux limitations up front and offer alternative solutions or workarounds for unsupported features (e.g., SQL Server discovery on Linux).
  • Balance the order of presentation so Linux requirements and patterns are described alongside Windows, not after.
  • Include sample scripts or configuration steps for Linux environments (e.g., SSH setup, sudo configuration, package manager commands).
  • Explicitly state which features are Windows-only and suggest Linux migration alternatives or roadmap if possible.
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 06:17
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 prerequisites, installation steps, and operational instructions require a Windows machine, PowerShell, and Windows-specific tools (Web Deploy). There are no Linux/macOS alternatives or instructions for running the containerization tool or migrating ASP.NET apps from non-Windows environments. The only Linux references are for Java/Tomcat scenarios, not ASP.NET.
Recommendations
  • Provide clear guidance on whether ASP.NET Core apps (which can run cross-platform) are supported, and if so, add Linux/macOS instructions.
  • If the tool is Windows-only, explicitly state this limitation at the top of the documentation.
  • Offer alternative manual containerization steps for ASP.NET apps on Linux/macOS (e.g., Dockerfile templates, migration guides).
  • Include troubleshooting and log location guidance for non-Windows environments if/when support is added.
  • Add parity in examples and prerequisites for Linux/macOS users where possible, or link to relevant resources.
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 06:17
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 toward Windows environments for ASP.NET app containerization. All instructions, prerequisites, and examples assume the use of a Windows machine, Windows Server, PowerShell, and Microsoft-specific tools (Web Deploy). There are no Linux/macOS alternatives or parity for ASP.NET scenarios, and all steps require Windows-only technologies. Linux is only mentioned in the context of Java/Tomcat apps, not ASP.NET.
Recommendations
  • Clarify early that ASP.NET containerization is currently Windows-only, and explicitly state Linux/macOS are unsupported for this scenario.
  • If possible, provide or link to guidance for containerizing ASP.NET apps from Linux/macOS environments (e.g., using .NET Core, cross-platform Dockerfiles, or remote Windows hosts).
  • Offer alternative instructions or tooling for Linux/macOS users where feasible, or suggest workarounds (such as using a Windows VM in Azure or locally).
  • Present prerequisites and examples for both platforms where applicable, or clearly segment Windows-only steps.
  • Consider adding a comparison table of supported platforms and scenarios for quick reference.
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 06:17
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/2022), with no mention of Linux as a host OS. All setup and installation instructions rely exclusively on PowerShell scripts and Windows tools (IIS, Windows Activation Service), with no Linux equivalents or alternatives provided. Examples and instructions for running the installer are Windows/PowerShell-only. Linux is only referenced as a target for discovery, not as a platform for hosting the appliance or running the installer.
Recommendations
  • Provide instructions and support for running the Azure Migrate appliance on Linux hosts, or clarify if this is not possible.
  • Offer Linux shell script equivalents for the installer and configuration steps, or document a Linux-native installation path.
  • Include Linux-first or side-by-side examples for setup, not just PowerShell/Windows.
  • Document any limitations or rationale for Windows-only appliance hosting to help Linux users understand their options.
  • If Windows hosting is required, make this explicit in the prerequisites and suggest workarounds for Linux-only environments (e.g., using a Windows VM).
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 06:17
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 oriented toward Windows environments, specifically Windows Server and Hyper-V. All setup, configuration, and scripting examples use PowerShell and Windows-native tools. Linux is mentioned only as a supported target OS for discovery, but there are no Linux-specific instructions, examples, or parity for appliance deployment, host preparation, or troubleshooting. Windows tools and patterns (WinRM, PowerShell, Hyper-V Manager, Local Group Policy Editor) are used exclusively, with no mention of Linux equivalents or alternative workflows for non-Windows users.
Recommendations
  • Provide explicit instructions and examples for Linux-based Hyper-V hosts (if supported), or clarify that only Windows-based Hyper-V hosts are supported.
  • Include Linux command-line alternatives where PowerShell or Windows tools are used, or state limitations if not possible.
  • Add parity in appliance deployment instructions for Linux environments, if supported (e.g., using KVM/QEMU, or instructions for deploying the appliance on a Linux VM).
  • Clarify in prerequisites and throughout the document which steps are Windows-only, and provide guidance for Linux/macOS administrators where relevant.
  • If Windows-only is a hard requirement, state this clearly at the top of the documentation.
GitHub Create Pull Request
Migrate Agentless Replication of VMware Virtual Machines ...rticles/migrate/concepts-vmware-agentless-migration.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page exhibits Windows bias in several areas. It provides only Windows PowerShell examples (e.g., NetQosPolicy), references Windows-specific tools and file paths (such as C:\ProgramData\Microsoft Azure\Config), and omits Linux/macOS equivalents or guidance. All configuration and management instructions assume a Windows environment for the Azure Migrate appliance, with no mention of Linux-based appliances or cross-platform alternatives.
Recommendations
  • Provide Linux/macOS equivalents for PowerShell commands, such as using tc, iptables, or other Linux-native bandwidth throttling tools.
  • Document the location and format of configuration files for Linux-based appliances, if supported (e.g., /etc/azure-migrate/config).
  • Clarify whether the Azure Migrate appliance can be deployed on Linux, and if so, provide parity in setup, configuration, and management instructions.
  • Include cross-platform scripting examples (e.g., Bash, Python) for automation tasks.
  • Explicitly state platform requirements and limitations at the beginning of the article.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation is heavily biased toward Windows environments. All instructions, prerequisites, and tooling are exclusively for Windows, including requirements for Windows OS, PowerShell, IIS, and Microsoft Web Deploy. There are no Linux/macOS alternatives or examples for containerizing ASP.NET apps, and the process cannot be completed on non-Windows platforms. The only Linux references are for Java/Tomcat apps, not ASP.NET.
Recommendations
  • Clearly state in the introduction and prerequisites that the tool and tutorial are Windows-only for ASP.NET apps.
  • Provide guidance or links for Linux/macOS users who may want to containerize ASP.NET apps using alternative methods (e.g., Docker CLI, .NET Core on Linux).
  • If possible, develop and document a cross-platform version of the tool, or provide manual steps for Linux/macOS users.
  • Add a comparison table showing platform support for ASP.NET vs. Java/Tomcat workflows.
  • Include troubleshooting notes for users attempting to run the tool on non-Windows platforms.
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-12 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 exhibits a strong Windows bias: the Azure Migrate: App Containerization tool must be installed and run on a Windows machine, with explicit requirements for Windows Server or Windows 10. All installation instructions use PowerShell, and there are no Linux/macOS installation or usage examples. Troubleshooting and log file locations are Windows-specific. Linux is only referenced as the target application server, not as a platform for running the migration tool itself.
Recommendations
  • Provide a Linux/macOS version of the Azure Migrate: App Containerization tool, or document alternative approaches for non-Windows users.
  • Include Linux/macOS installation instructions and command-line examples (e.g., Bash scripts) alongside PowerShell.
  • Clarify whether the tool can be run in a Windows VM/container on Linux/macOS hosts, and provide guidance if so.
  • Document log file locations and troubleshooting steps for non-Windows platforms if/when supported.
  • Consider offering a web-based or cross-platform version of the tool to reduce dependency on Windows.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias. It consistently references Windows Server as the supported OS for the Azure Migrate appliance, provides only PowerShell-based installation instructions, and exclusively mentions Windows security tools (such as Group Policy Objects and the Security Compliance Toolkit). There are no examples or guidance for deploying or hardening the appliance on Linux, nor are Linux security tools or patterns discussed. Even when Linux servers are mentioned as migration sources, the appliance itself is assumed to be Windows-based.
Recommendations
  • Provide explicit guidance and examples for deploying the Azure Migrate appliance on Linux, if supported.
  • Include Linux-based installation instructions (e.g., Bash scripts, Linux package managers) alongside PowerShell.
  • Reference Linux security hardening tools and frameworks (such as CIS benchmarks, SELinux, AppArmor) in the OS image hardening section.
  • Clarify whether the appliance can run on Linux, and if not, explain the rationale and provide alternative approaches for Linux-centric environments.
  • When discussing credential management and security baselines, include Linux equivalents (e.g., sudoers configuration, PAM, SSH key management).
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-12 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 Windows environments, specifically requiring Windows Server and IIS, and mandates the use of Windows PowerShell. Linux servers are explicitly not supported, and there are no examples or guidance for Linux or macOS users. All requirements, tools, and supported platforms are Windows-centric.
Recommendations
  • Clearly state in the introduction that only Windows/IIS web apps are supported, and provide guidance or links for Linux-based web app migration scenarios if available.
  • If Linux support is planned, add a roadmap or expected timeline.
  • Include a comparison table or section outlining migration options for Linux web apps (e.g., using containerization, App Service for Linux, or other Azure services).
  • Provide alternative migration guidance for users running web apps on Linux or macOS platforms, or direct them to relevant Azure documentation.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation is heavily biased towards Windows environments. All command-line examples use PowerShell, certificate export instructions reference Windows file paths and tools, and registry modification steps are Windows-specific. There are no Linux/macOS equivalents or guidance for performing these steps on non-Windows platforms, despite mentioning cross-platform appliance scenarios.
Recommendations
  • Provide equivalent certificate generation and export instructions using OpenSSL or mkcert for Linux/macOS.
  • Include steps for installing certificates on Linux (e.g., using openssl, certutil, or update-ca-certificates) and macOS (Keychain Access or security CLI).
  • Offer guidance for storing appliance configuration outside the Windows registry, such as using environment variables or configuration files for Linux/macOS.
  • Clearly indicate which steps are Windows-only and offer alternative instructions for Linux/macOS users.
  • Reorder examples so that cross-platform tools (OpenSSL, mkcert) are presented before or alongside PowerShell.
GitHub Create Pull Request
Migrate Azure Migrate appliance ...e-docs/blob/main/articles/migrate/migrate-appliance.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation for the Azure Migrate appliance is heavily biased toward Windows environments. All deployment methods, prerequisites, and examples reference Windows Server (2019/2022/2025) and PowerShell scripts. There is no mention of deploying the appliance on Linux or macOS, nor are there any Linux shell commands or tools provided. Even for physical servers, only Windows is supported for hosting the appliance. Verification steps and upgrade instructions use Windows-specific tools (CertUtil, Registry Editor, Control Panel), with no Linux alternatives. Linux is only referenced as a target for discovery, not as a platform for appliance deployment or management.
Recommendations
  • Clearly state in the prerequisites and supported platforms section that the appliance cannot be hosted on Linux or macOS, if that is the case. If Linux hosting is possible, provide equivalent deployment instructions and examples for Linux environments.
  • For verification steps (hash checking), provide Linux shell command equivalents (e.g., sha256sum, md5sum) alongside CertUtil.
  • For upgrade and management instructions, note Linux alternatives or clarify Windows-only requirements.
  • If PowerShell is required, mention cross-platform PowerShell Core (pwsh) support, or clarify that only Windows PowerShell is supported.
  • Add a table or section comparing Windows and Linux support for appliance deployment, management, and discovery.
  • If Linux hosting is not supported, provide rationale and guidance for Linux users who may need to participate in migration projects.
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-12 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 environments, specifically Hyper-V. All examples, instructions, and tooling references are Windows-centric, including use of Hyper-V Manager, PowerShell commands, and Windows-specific utilities like CertUtil and Local Group Policy Editor. Linux is only mentioned as a credential type, with no guidance or examples for Linux hosts or tools. This creates friction for users who may want to run the appliance or related tasks on Linux or macOS, or who need parity in cross-platform environments.
Recommendations
  • Provide equivalent instructions for deploying and managing the Azure Migrate appliance on Linux hosts, if supported.
  • Include hash verification examples using Linux tools (e.g., sha256sum, openssl) alongside CertUtil and Get-FileHash.
  • Clarify whether the appliance can be run on non-Windows hypervisors or physical servers, and provide steps for those platforms.
  • Add Linux/macOS alternatives for credential delegation and proxy configuration, if applicable.
  • Explicitly state platform limitations and offer links to Linux/macOS documentation where relevant.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation is heavily biased towards Windows environments. All setup and deployment instructions exclusively use PowerShell and reference Windows-specific tools and patterns (e.g., Registry Editor, IIS, Windows Activation Service, HKLM registry keys, %ProgramData% paths). There are no instructions or examples for deploying or configuring the appliance on Linux or macOS systems, nor are alternative shell or tool options provided. Windows terminology and steps are presented first and exclusively, leaving Linux users without guidance for critical setup steps.
Recommendations
  • Provide equivalent Linux setup instructions, including shell script examples (e.g., Bash) and Linux-specific prerequisites.
  • Clarify whether the appliance can be deployed on Linux or macOS, and if not, state this explicitly.
  • If Linux deployment is supported, include instructions for installing required dependencies (e.g., web server, agents) on Linux.
  • Offer troubleshooting and log file locations for Linux systems.
  • Present Windows and Linux instructions side-by-side or clearly indicate platform-specific steps.
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-12 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 biased towards Windows environments. All instructions, examples, and tooling (installer script, configuration steps, validation commands) are designed for Windows Server 2019/2022, using PowerShell scripts and Windows-specific utilities (CertUtil, IIS, registry edits). There is no mention of Linux or macOS support, nor are alternative instructions or parity examples provided for non-Windows platforms. This creates a significant barrier for users who wish to deploy or manage the Azure Migrate appliance from Linux or macOS systems.
Recommendations
  • Explicitly state Windows-only support at the start of the documentation if Linux/macOS are not supported.
  • If possible, provide equivalent installer scripts and instructions for Linux-based servers (e.g., bash scripts, Linux prerequisites, Linux service setup).
  • Include parity examples for checksum validation using Linux tools (e.g., sha256sum) and clarify if the appliance can be run on Linux.
  • Document any limitations or alternatives for non-Windows users, such as using a Windows VM for appliance setup.
  • Add a comparison table of supported OS platforms for the appliance and clarify any future plans for Linux/macOS support.
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-12 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 environments, specifically Hyper-V on Windows Server. All operational examples and tooling references (MMC snap-in, registry edits, Windows file paths) are Windows-specific, with no mention of Linux or cross-platform alternatives. The instructions for controlling upload throughput and efficiency rely on Windows-only tools and patterns, such as the Windows Azure Backup MMC snap-in and Windows Registry edits. There are no Linux or macOS equivalents or guidance provided, making the documentation inaccessible to users running Hyper-V on non-Windows platforms (if supported) or those seeking parity for similar migration scenarios.
Recommendations
  • Clarify that the documented process is specific to Windows-based Hyper-V environments, and note any platform limitations.
  • If Linux-based Hyper-V hosts are supported, provide equivalent instructions and tooling for Linux (e.g., CLI commands, config file edits).
  • Offer cross-platform alternatives for bandwidth throttling and upload thread management, or explicitly state if these features are unavailable on non-Windows platforms.
  • Include a section comparing Windows and Linux/macOS support for Azure Migrate Hyper-V migration, and link to relevant documentation for other platforms.
  • If only Windows is supported, make this clear at the start to set expectations for non-Windows users.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Windows tools and paths (e.g., %ProgramFiles%, .exe utility), and by not providing any Linux or macOS equivalents or instructions. All examples and steps assume a Windows environment, with no mention of cross-platform alternatives or considerations for Linux users.
Recommendations
  • Provide instructions for running the provisioning utility on Linux and macOS, or clarify if it is Windows-only.
  • If the tool is Windows-only, suggest alternative manual steps or scripts for Linux environments.
  • Include Linux-specific examples, such as using bash, Linux file paths, and authentication methods.
  • Explicitly state platform requirements and limitations at the beginning of the documentation.
  • Offer guidance for Linux users on how to provision least privileged accounts using native SQL Server tools or scripts.
GitHub Create Pull Request
Migrate Azure Migrate replication appliance ...main/articles/migrate/migrate-replication-appliance.md
High Priority View Details →
Scanned: 2026-01-12 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), with no mention of Linux or macOS support for the appliance itself. Software installation paths, MySQL installer links, and configuration details are all tailored to Windows environments (e.g., C:\Temp\ASRSetup, .msi installer). Windows-specific tools and roles (IIS, Windows Server roles, Group Policies) are referenced, while Linux equivalents are absent. This creates significant friction for users who may wish to deploy or manage the appliance on Linux or non-Windows platforms.
Recommendations
  • Clarify whether the replication appliance can only run on Windows Server, or if Linux is supported for physical server deployments. If Linux is supported, provide explicit instructions and requirements for Linux installations.
  • Include Linux-based examples for MySQL installation, such as using apt, yum, or rpm, and specify installation paths and permissions relevant to Linux.
  • If the appliance is Windows-only by design, state this clearly at the beginning of the documentation to set expectations for non-Windows users.
  • Reference Linux equivalents for configuration tasks (e.g., disabling services, managing ports, setting up static IPs) where applicable.
  • Provide troubleshooting or workaround guidance for users in non-Windows environments, or link to migration alternatives for Linux workloads.
GitHub Create Pull Request
Migrate Migrate Hyper-V servers to Azure by using Private Link ...ttps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/migrate-hyper-v-servers-to-azure-using-private-link.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation is heavily focused on migrating Hyper-V VMs, a Windows-centric virtualization technology. All examples, instructions, and tooling references are specific to Hyper-V and Windows environments, with no mention of Linux-based hypervisors (such as KVM, Xen, or even VMware in this context) or Linux-specific migration steps. Windows tools and patterns (e.g., Hyper-V Replication provider, Recovery Service agent) are referenced exclusively, and there are no Linux or cross-platform CLI examples. The documentation assumes the reader is operating in a Windows ecosystem, creating friction for Linux users or those with heterogeneous environments.
Recommendations
  • Add sections or links for migrating Linux-based VMs or from Linux hypervisors (e.g., KVM, Xen, VMware) to Azure using Private Link.
  • Provide parity in examples, including Linux CLI commands (e.g., Bash, Azure CLI) for DNS configuration, network connectivity checks, and agent installation.
  • Clarify whether the described process is exclusive to Hyper-V/Windows or if similar workflows exist for Linux-based environments.
  • Reference or link to documentation for agent-based migration from Linux hosts, if supported.
  • Explicitly state platform limitations and alternatives for Linux 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-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation is exclusively focused on Windows OS upgrade issues and troubleshooting steps, with no mention of Linux or macOS scenarios, tools, or examples. All instructions, links, and recommendations are tailored to Windows environments, and Windows-specific Azure documentation is referenced throughout. This creates a strong Windows bias and leaves Linux users without guidance for similar migration or upgrade issues.
Recommendations
  • Add equivalent troubleshooting sections for Linux VM upgrades, including common issues and recommended actions.
  • Provide links to Linux-specific Azure documentation (e.g., in-place upgrade, disk expansion, SKU selection for Linux VMs).
  • Include examples and step-by-step instructions for Linux VM migration and upgrade workflows.
  • Clarify in the introduction that the article is Windows-specific, or broaden the scope to cover both Windows and Linux OS upgrades.
GitHub Create Pull Request
Migrate Troubleshoot web apps migration issues ...ain/articles/migrate/troubleshoot-webapps-migration.md
High Priority View Details →
Scanned: 2026-01-12 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 focused on migration scenarios involving IIS web servers and PowerShell, both of which are Windows-centric technologies. All troubleshooting steps and error codes relate to IIS and PowerShell, with no mention of Linux-based web servers (e.g., Apache, Nginx) or Linux-specific migration issues. The examples and guidance assume a Windows environment, making it difficult for Linux users to apply the instructions or troubleshoot their own migration scenarios.
Recommendations
  • Add troubleshooting steps and error codes relevant to Linux-based web servers (Apache, Nginx, etc.) and common Linux migration issues.
  • Include Linux-specific examples and commands (e.g., Bash scripts, Linux file permissions, systemd services) alongside PowerShell examples.
  • Clarify in the introduction that the guidance is currently Windows/IIS-specific, and provide links or references to Linux migration documentation if available.
  • If Azure Migrate supports Linux web app migration, document the process and troubleshooting steps for those scenarios.
  • Present examples for both Windows and Linux platforms in parallel, or at least alternate which platform is shown first.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates Windows bias in several areas. Configuration changes on the Azure Migrate appliance are described using Windows-specific tools and paths (e.g., Remote Desktop, %programdata%, PowerShell commands), with no mention of Linux equivalents. Service restart instructions use Windows commands exclusively, and there are no Linux or cross-platform examples for appliance management. The documentation assumes the appliance is running on Windows, omitting guidance for Linux deployments.
Recommendations
  • Provide equivalent instructions for Linux-based appliances, including file paths (e.g., /var/lib/...), service management (systemctl or service commands), and remote access (SSH instead of Remote Desktop).
  • Include both Windows and Linux examples side-by-side for configuration and troubleshooting steps.
  • Clarify whether the Azure Migrate appliance can run on Linux, and if so, link to relevant Linux setup and management documentation.
  • Avoid using Windows-specific terminology (e.g., PowerShell, %programdata%) without Linux alternatives.
  • Add notes or sections for macOS users if relevant.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation is heavily biased toward Windows environments for ASP.NET app containerization. All instructions, prerequisites, and tooling are Windows-centric, requiring a Windows machine, PowerShell, and Windows-only tools (Web Deploy). There are no Linux/macOS equivalents or alternatives provided for ASP.NET scenarios, and all examples and steps assume Windows as the host and management platform. Linux is only mentioned in the context of Java/Tomcat apps, not ASP.NET.
Recommendations
  • Clarify early that ASP.NET containerization is only supported on Windows hosts, and provide a roadmap or alternatives for Linux/macOS users.
  • If possible, provide Linux/macOS-compatible tooling or document manual containerization steps for ASP.NET apps on non-Windows platforms.
  • Offer PowerShell alternatives (e.g., Bash scripts) or cross-platform instructions where feasible.
  • Explicitly state the lack of support for Linux/macOS in ASP.NET scenarios, and link to relevant resources for those platforms.
  • Consider adding a comparison table outlining platform support for each app type and scenario.
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-12 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 exhibits a strong Windows bias: the Azure Migrate: App Containerization tool must be installed and run on a Windows machine, with all installation instructions and troubleshooting steps referencing Windows-specific tools, paths, and PowerShell scripts. There are no instructions or support for running the tool on Linux or macOS, nor are alternative workflows provided for non-Windows users. This creates a significant barrier for users who primarily use Linux or macOS environments.
Recommendations
  • Provide a Linux/macOS version of the Azure Migrate: App Containerization tool, or clarify if it is Windows-only and suggest alternative approaches for non-Windows users.
  • Include installation and usage instructions for Linux and macOS platforms, including equivalent shell commands and file paths.
  • If the tool is fundamentally Windows-only, add a prominent note at the top of the documentation to inform users and suggest using a Windows VM if necessary.
  • Offer guidance on accessing the tool from Linux/macOS clients (e.g., via browser) and clarify any limitations.
  • Add troubleshooting and artifact location instructions for Linux/macOS if/when supported.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation exhibits a notable Windows bias: the Azure Migrate appliance is required to run on Windows Server (no Linux option is mentioned), and all setup instructions (including running the installer script) are exclusively PowerShell-based. Windows roles and tools (IIS, Windows Activation Service, registry edits) are referenced without Linux equivalents. Linux instructions are limited to enabling SSH and root login, with no guidance on running the appliance or installer script on Linux. There are no Linux-based examples or parity in appliance deployment.
Recommendations
  • Provide instructions and support for deploying the Azure Migrate appliance on Linux-based hosts (e.g., Ubuntu, CentOS).
  • Include Linux shell (bash) equivalents for all PowerShell commands and script execution steps.
  • Offer a Linux-compatible installer script or containerized appliance option.
  • Mention Linux alternatives for Windows-specific tools (e.g., IIS, registry edits) or clarify if they are not required on Linux.
  • Present examples for both Windows and Linux side-by-side, or alternate the order to avoid Windows-first bias.
GitHub Create Pull Request
← Previous Page 1 of 9 Next →