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 1-25 of 918 flagged pages
Migrate Troubleshoot replication issues in agentless VMware VM migration ...ate/troubleshoot-changed-block-tracking-replication.md
High Priority View Details →
Scanned: 2026-01-14 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, with troubleshooting steps and examples almost exclusively using Windows-specific tools (PowerShell, MMC snap-in, services.msc, Command Prompt), and no Linux/macOS equivalents or guidance. All command-line examples and instructions assume the Azure Migrate appliance is Windows-based, and there are no alternative steps for users running Linux-based appliances or accessing via SSH. This creates friction for non-Windows users and may prevent them from completing tasks without significant adaptation.
Recommendations
  • Provide equivalent Linux/macOS commands for all PowerShell and Windows tool instructions (e.g., use curl, netcat, systemctl, etc.).
  • Include troubleshooting steps for Azure Migrate appliances running on Linux, if supported.
  • Add notes clarifying OS requirements for the Azure Migrate appliance and explicitly state if only Windows is supported.
  • Where tools like azcopy or Service Bus Explorer are used, provide installation and usage instructions for Linux/macOS.
  • Present examples for both Windows and Linux/macOS side by side, or alternate which OS is shown first.
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-14 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a notable Windows bias: it exclusively references Windows Server as the supported OS for the Azure Migrate appliance, recommends PowerShell scripts for deployment, and relies on Windows-specific security tools (Group Policy Objects, Windows Security Baselines, Security Compliance Toolkit). There are no Linux/macOS deployment examples, hardening guidelines, or tool recommendations, despite mentioning Linux servers in network connectivity. This creates friction for users wishing to deploy or secure the appliance on non-Windows platforms.
Recommendations
  • Clarify whether the Azure Migrate appliance can be deployed on Linux or macOS, and if so, provide equivalent deployment instructions and security hardening guidelines.
  • Include Linux/macOS-specific examples for appliance deployment, OS image hardening, and vulnerability management.
  • Reference Linux security tools (e.g., CIS benchmarks, SELinux, AppArmor) and provide guidance for securing Linux-based appliances.
  • If PowerShell is not available on Linux, offer Bash or shell script alternatives for deployment and management.
  • Present examples for both Windows and Linux platforms in parallel, or clearly state platform limitations up front.
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-14 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 IIS servers and Windows PowerShell. Linux servers are explicitly marked as unsupported, and there are no examples, requirements, or migration paths for Linux-based web apps. All tooling and prerequisites (IIS, PowerShell) are Windows-centric, with no mention of Linux equivalents or alternatives.
Recommendations
  • Clearly indicate in the introduction that Linux-based web apps are not supported, and provide guidance or links for Linux migration scenarios if available.
  • Add a roadmap or expected timeline for Linux support, if planned.
  • Include a comparison table or section outlining differences between Windows and Linux migration support.
  • If possible, provide alternative migration strategies or tools for Linux users, or direct them to relevant documentation.
  • Ensure future updates consider Linux parity in examples, tooling, and requirements.
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-14 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, with all automation examples and scripts provided only in PowerShell (.ps1) format. There is no mention of Bash, shell, or cross-platform alternatives, nor are Linux/macOS scripting options discussed. The instructions and prerequisites assume use of Windows tools and patterns, making it difficult for Linux/macOS users to follow or automate migration tasks without significant adaptation.
Recommendations
  • Provide equivalent Bash or shell script samples for Linux/macOS users.
  • Document how to run migration tasks using Azure CLI, which is cross-platform.
  • Explicitly mention compatibility or workarounds for running PowerShell scripts on Linux/macOS (e.g., via PowerShell Core).
  • Offer guidance on installing and using required Azure modules/tools on Linux/macOS.
  • Present examples for both Windows and Linux environments, or clarify platform requirements up front.
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-14 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 certificate generation, export, and registry update examples use PowerShell and Windows-specific tools and paths. There are no Linux/macOS command examples, nor is there guidance for performing equivalent steps on non-Windows platforms. The registry update step is inherently Windows-specific, and the certificate installation instructions reference Windows GUI dialogs and file paths.
Recommendations
  • Provide equivalent Linux/macOS instructions for certificate generation and export, using tools like OpenSSL and mkcert.
  • Clarify whether Azure Migrate appliance can be deployed on Linux, and if so, document the process for certificate installation and configuration (e.g., updating config files instead of Windows Registry).
  • Include Linux/macOS command examples alongside PowerShell, and avoid assuming Windows file paths or GUI dialogs.
  • Explicitly state platform requirements and limitations at the beginning of the documentation.
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-14 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 and examples assume the use of Windows Server (2019/2022) as the host OS for the Azure Migrate appliance, and all scripting and command-line steps use PowerShell. Windows-specific tools (CertUtil, IIS, registry keys, Windows roles) are referenced exclusively, with no mention of Linux or macOS alternatives or support. There are no Linux-based installer scripts, commands, or troubleshooting steps, and the appliance setup appears to require Windows-only components.
Recommendations
  • Clarify early in the documentation whether Linux-based hosts are supported for the Azure Migrate appliance. If not, explicitly state the Windows-only requirement.
  • If Linux support is possible, provide equivalent instructions for deploying the appliance on Linux (e.g., Bash scripts, Linux prerequisites, checksum validation using sha256sum, Linux service setup).
  • Include troubleshooting and validation steps for Linux environments, such as log file locations and service management.
  • Offer parity in examples and screenshots, showing both Windows and Linux workflows where applicable.
  • If PowerShell is required, note whether PowerShell Core (cross-platform) is supported, and provide installation instructions for Linux/macOS.
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-14 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page exhibits a strong Windows bias. All setup and deployment instructions rely exclusively on PowerShell, Windows administrative tools, and Windows-specific patterns (e.g., registry edits, IIS roles, Windows Activation Service). There are no Linux/macOS equivalents or alternative instructions, and the examples, screenshots, and file paths are all Windows-centric. Linux is only mentioned as a target for discovery, not as a platform for running the appliance.
Recommendations
  • Provide instructions for deploying and running the Azure Migrate appliance on Linux (and/or macOS), including supported distributions and prerequisites.
  • Offer Linux/macOS equivalents for script execution (e.g., Bash scripts, shell commands) and clarify if the installer script can be run in a cross-platform manner.
  • Document how to perform necessary configuration steps (such as registry edits, IIS setup) on Linux, or clarify if these steps are Windows-only.
  • Include Linux/macOS screenshots and file path examples where relevant.
  • Explicitly state platform limitations and offer guidance for Linux/macOS users if the appliance is Windows-only.
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-14 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation is heavily focused on Windows environments, specifically Hyper-V on Windows Server. All examples and instructions reference Windows-only tools (MMC snap-in, Regedit, Windows registry paths), and there are no Linux or macOS equivalents or alternatives provided. The steps for controlling upload throughput and efficiency are only applicable to Windows hosts, and there is no mention of how to perform similar actions on Linux-based Hyper-V hosts (if supported) or other platforms.
Recommendations
  • Clarify that the migration process and tooling are specific to Windows-based Hyper-V hosts, or explicitly state platform limitations.
  • If Linux-based Hyper-V hosts are supported, provide equivalent instructions and examples for Linux (e.g., using CLI tools, configuration files, or other Linux-native methods).
  • Add a section comparing Windows and Linux support for Hyper-V migration, including any feature gaps.
  • Where possible, provide cross-platform alternatives or note when a feature is Windows-only.
  • List prerequisites and supported platforms at the beginning of the article.
GitHub Create Pull Request
Migrate Azure Migrate appliance ...e-docs/blob/main/articles/migrate/migrate-appliance.md
High Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation for the Azure Migrate appliance demonstrates a strong Windows bias. All deployment scenarios, templates, and scripts are designed for Windows Server environments, with PowerShell as the exclusive automation tool. Examples for verifying downloads and performing upgrades use Windows-only tools (CertUtil, Get-FileHash, Registry Editor, Control Panel). There is no mention of Linux-based appliance deployment, nor are there any Linux/macOS equivalents for core operations. Linux is only referenced as a target for discovery, not as a platform for hosting or managing the appliance.
Recommendations
  • Clarify in the introduction that the appliance is Windows-only if that is a product limitation. If not, provide explicit instructions for deploying and managing the appliance on Linux (e.g., using Bash, Linux hash tools like sha256sum, Linux package management).
  • Include Linux/macOS equivalents for all command-line examples (e.g., hash verification, service management).
  • If PowerShell is required, note whether PowerShell Core (cross-platform) is supported, and provide installation instructions for Linux/macOS.
  • For registry and Control Panel steps, provide Linux alternatives or clarify that these steps are not applicable to non-Windows hosts.
  • Explicitly state OS requirements and limitations up front, and provide guidance for users in mixed-OS environments.
GitHub Create Pull Request
Migrate Azure Migrate replication appliance ...main/articles/migrate/migrate-replication-appliance.md
High Priority View Details →
Scanned: 2026-01-14 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 are for Windows Server (2016/2012 R2). There are no references to Linux or macOS as supported platforms for the replication appliance, nor are there any examples or instructions for deploying, configuring, or managing the appliance on non-Windows systems. Windows tools, file paths (e.g., C:\Temp\ASRSetup), and concepts (Windows Server roles, group policies, IIS settings) are mentioned exclusively, with no Linux equivalents or alternatives provided.
Recommendations
  • Explicitly state whether Linux-based deployment of the replication appliance is supported or not. If not supported, clarify this early in the documentation.
  • If Linux deployment is possible, provide equivalent instructions, requirements, and examples for Linux systems (e.g., supported distributions, required packages, file paths, service management).
  • Include Linux-specific guidance for MySQL installation, such as using apt/yum/zypper, and relevant file locations.
  • Mention Linux equivalents for Windows Server roles, group policies, and IIS settings, or clarify which steps are not applicable to Linux.
  • If only Windows is supported, add a prominent note for Linux/macOS users, and suggest alternative migration approaches if available.
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-14 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-specific tools and patterns, such as using a command prompt, referencing %ProgramFiles% paths, and running a Windows executable (MinimumPrivilegedUser.exe). There are no instructions or examples for Linux or macOS environments, nor mention of cross-platform alternatives. The steps and prerequisites assume a Windows environment throughout.
Recommendations
  • Provide instructions for running the utility on Linux/macOS, if supported, or clarify platform limitations.
  • Offer Linux/macOS equivalents for file paths and command-line usage (e.g., /opt/... instead of %ProgramFiles%).
  • If the utility is Windows-only, explicitly state this and suggest alternative methods for Linux users (such as manual SQL scripts or cross-platform tools).
  • Include examples using Bash or other non-Windows shells where appropriate.
  • Mention any platform-specific requirements or limitations up front.
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-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation is focused exclusively on migrating Hyper-V servers (a Windows-centric virtualization platform) to Azure, with all examples, instructions, and tooling centered around Windows environments. There are no Linux or cross-platform migration scenarios, nor are Linux equivalents or alternatives mentioned. Windows terminology, tools, and patterns (e.g., Hyper-V Replication provider, Recovery Service agent) are used throughout, and steps assume a Windows server context.
Recommendations
  • Add guidance or links for migrating Linux-based virtualization platforms (e.g., KVM, Xen, or VMware on Linux) to Azure using Private Link.
  • Include examples or references for agent installation and DNS configuration on Linux hosts, where applicable.
  • Clarify in the introduction that the process is specific to Hyper-V/Windows, and provide pointers to Linux migration documentation for parity.
  • If Azure Migrate supports agentless migration for Linux VMs, include instructions or a section for Linux hosts.
  • Ensure terminology and steps are inclusive of non-Windows environments where possible, or explicitly state limitations.
GitHub Create Pull Request
Migrate Assess large numbers of physical servers for migration to Azure with Azure Migrate | Microsoft Docs ...lob/main/articles/migrate/scale-physical-assessment.md
High Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates Windows bias by exclusively referencing the Azure Migrate appliance as being deployed on a Windows server, with no mention of Linux or macOS deployment options or examples. There are no Linux-specific instructions, tools, or examples provided, and the documentation implicitly assumes a Windows environment for critical setup steps.
Recommendations
  • Explicitly state whether the Azure Migrate appliance supports Linux or macOS hosts. If not, clarify the limitation.
  • If Linux/macOS support exists, provide equivalent setup instructions and examples for those platforms.
  • Include a comparison table or section outlining platform-specific requirements and limitations.
  • Add troubleshooting or workaround guidance for Linux/macOS users if Windows is required.
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-14 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 by providing appliance configuration and service restart instructions exclusively for Windows environments. It references Windows-specific tools (Remote Desktop, PowerShell, net stop/start commands, Windows file paths) without offering Linux equivalents or acknowledging cross-platform scenarios. All appliance-side examples and steps are Windows-centric, with no mention of how to perform these tasks on a Linux-based appliance.
Recommendations
  • Include instructions for configuring the appliance on Linux, such as file locations, service management commands (e.g., systemctl), and remote access methods (e.g., SSH).
  • Provide Linux/macOS equivalents for PowerShell and net stop/start commands, such as systemctl or service commands.
  • Clarify whether the Azure Migrate appliance supports Linux, and if so, add parallel steps for Linux users.
  • Present examples for both Windows and Linux environments, or clearly state platform limitations if the appliance is Windows-only.
GitHub Create Pull Request
Migrate Troubleshoot web apps migration issues ...ain/articles/migrate/troubleshoot-webapps-migration.md
High Priority View Details →
Scanned: 2026-01-14 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 troubleshooting migration of IIS-based web apps, with repeated references to IIS, PowerShell, and Windows-specific tools and patterns. All error codes and troubleshooting steps assume a Windows environment, specifically IIS servers and PowerShell scripting, with no mention of Linux-based web servers (e.g., Apache, Nginx) or Linux migration scenarios. There are no Linux/macOS examples, nor guidance for users migrating non-Windows web apps.
Recommendations
  • Add troubleshooting sections for Linux-based web apps (e.g., Apache, Nginx) and their migration issues.
  • Include examples and error codes relevant to Linux environments, such as common file permission or connectivity issues.
  • Provide parity in migration tooling and scripts for Linux, including Bash or shell script equivalents to PowerShell commands.
  • Clarify in the introduction that the guidance is specific to IIS/Windows migrations, or expand scope to cover Linux scenarios.
  • List Linux troubleshooting steps alongside Windows ones, not after or omitted.
GitHub Create Pull Request
Migrate Troubleshoot Windows upgrade issues ...ocs/blob/main/articles/migrate/troubleshoot-upgrade.md
High Priority View Details →
Scanned: 2026-01-14 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 troubleshooting Windows OS upgrade issues during Azure VM migration. All examples, recommendations, and linked resources pertain to Windows environments, with no mention of Linux or macOS upgrade scenarios, tools, or troubleshooting steps. The article assumes the user is working with Windows VMs and Windows-specific Azure features, omitting Linux equivalents entirely.
Recommendations
  • Add a parallel section for troubleshooting Linux OS upgrade issues during VM migration.
  • Include examples and links for expanding disks, verifying free space, and handling migration errors for Linux VMs (e.g., using Azure CLI, Linux disk management tools).
  • Reference Linux-specific documentation for in-place upgrades and disk management in Azure.
  • Clarify in the introduction that the article is Windows-specific, or broaden the scope to include Linux/macOS where 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-14 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 is strongly biased towards Windows environments for ASP.NET app containerization. All instructions, prerequisites, and tooling are Windows-specific, requiring a Windows machine, PowerShell, and Windows-only tools (Web Deploy). There are no Linux/macOS alternatives or examples for ASP.NET containerization, and the use of Windows terminology and tools is pervasive throughout the tutorial.
Recommendations
  • Provide guidance for running the Azure Migrate App Containerization tool on Linux/macOS, if possible, or clarify platform limitations early.
  • Offer Linux/macOS equivalents for prerequisites (e.g., remote access, deployment tooling) or suggest alternative workflows for non-Windows users.
  • Include Linux/macOS command-line examples alongside PowerShell, where relevant.
  • Explicitly state in the introduction and prerequisites that ASP.NET containerization is currently Windows-only, and link to cross-platform alternatives for .NET Core/ASP.NET Core apps.
  • Add troubleshooting and log file location details for Linux/macOS if/when support is added.
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-14 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 demonstrates a strong Windows bias: the Azure Migrate: App Containerization tool is only installable and runnable on Windows machines, with explicit requirements for Windows Server or Windows 10/11. All installation instructions use PowerShell, and troubleshooting references Windows file paths. There are no instructions or examples for Linux or macOS users to install or run the tool, nor are alternative workflows provided for non-Windows environments. This creates a significant barrier for users on Linux or macOS, despite the fact that the applications being containerized are running on Linux servers.
Recommendations
  • Provide a Linux-compatible version of the Azure Migrate: App Containerization tool, or document alternative workflows for Linux/macOS users.
  • Include installation and usage instructions for Linux (e.g., bash scripts, .deb/.rpm packages, Docker images) alongside Windows/PowerShell examples.
  • Offer troubleshooting steps for Linux/macOS environments, or clarify platform limitations early in the documentation.
  • Consider providing a web-based or containerized version of the tool that can be run cross-platform.
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-14 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 for Azure App Containerization for Java web apps is heavily biased toward Windows. The tool itself must be installed and run on a Windows machine, with explicit requirements for Windows Server or Windows 10/11. Installation instructions are provided only for PowerShell, with no mention of Linux or macOS alternatives. All artifact and troubleshooting paths reference Windows file system locations. There are no examples or instructions for using the tool from Linux or macOS, nor any mention of CLI or cross-platform alternatives.
Recommendations
  • Provide a Linux/macOS version of the Azure Migrate: App Containerization tool, or clarify if none exists.
  • If possible, offer installation instructions for Linux (e.g., Bash script, .deb/.rpm packages) and macOS.
  • Document alternative workflows for Linux/macOS users, such as using Azure CLI or containerizing manually.
  • Explicitly state platform limitations early in the documentation, so non-Windows users can plan accordingly.
  • Consider storing artifacts in a cross-platform-accessible location or provide instructions for accessing them from non-Windows systems.
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-14 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 is heavily biased towards Windows environments for ASP.NET app containerization. All instructions, prerequisites, and tooling are Windows-only, requiring Windows OS, PowerShell, and Microsoft Web Deploy. There are no Linux/macOS alternatives or examples for ASP.NET containerization, and all code samples use PowerShell. Linux is only mentioned in the context of Java/Tomcat apps, not ASP.NET.
Recommendations
  • Clarify early in the documentation that ASP.NET containerization is currently Windows-only, and explicitly state the lack of Linux/macOS support.
  • If possible, provide or link to alternative workflows for ASP.NET containerization from Linux/macOS (e.g., manual Dockerfile creation, use of cross-platform tools).
  • Offer guidance for users who may want to run the tool in a Windows VM from Linux/macOS hosts.
  • Add a comparison table showing platform support for different app types (ASP.NET vs Java) to set expectations.
  • If future support for Linux/macOS is planned, mention it and provide a feedback channel.
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-14 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation exhibits a notable Windows bias. The Azure Migrate appliance is required to run on Windows Server 2019 or 2022, with no option for Linux-based deployment. All installer instructions and examples use PowerShell, and the appliance installation process involves Windows-specific tools (IIS, Windows Activation Service, registry edits). Linux server discovery is supported, but only as a target for assessment, not as a platform for running the appliance. There are no Linux shell or cross-platform installation examples, and Windows terminology and tools are presented first and exclusively.
Recommendations
  • Provide a Linux-based appliance option, or clarify if/why it is not possible.
  • Include Linux shell (bash) equivalents for installation and troubleshooting steps.
  • Offer parity in examples: show Linux commands and workflows alongside Windows/PowerShell ones.
  • Explicitly state platform limitations early in the document to set expectations for Linux/macOS users.
  • Consider supporting containerized or cross-platform deployment of the appliance.
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-14 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a notable Windows bias. Windows server setup instructions are presented first and in greater detail, including specific group memberships, permissions, and troubleshooting steps. The installer script section exclusively references PowerShell and Windows tools (IIS, Windows Activation Service, registry keys), with no mention of Linux equivalents or support for running the appliance natively on Linux. The Linux section is present and provides user account setup guidance, but there are no examples or instructions for running the appliance installer or configuration on Linux. The appliance appears to be Windows-only, which is not explicitly stated, potentially causing confusion for Linux users.
Recommendations
  • Explicitly state that the Azure Migrate appliance must be installed on Windows and cannot run natively on Linux.
  • Provide parity in example order and detail: present Linux setup instructions before or alongside Windows instructions.
  • If possible, offer a Linux-native version of the appliance or document supported workarounds (e.g., running the appliance in a Windows VM for Linux environments).
  • Clarify in the prerequisites and installer sections that PowerShell and Windows roles are required, and Linux users must use a Windows host for the appliance.
  • Add troubleshooting and FAQ sections specifically for Linux users, including common issues when discovering Linux servers from a Windows-based appliance.
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-14 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a notable Windows bias. The Azure Migrate appliance is required to run on Windows Server (2019/2022) only, with no mention of Linux support for hosting the appliance. All setup and installation instructions use PowerShell scripts and Windows-specific tools (IIS, Windows Activation Service, registry edits), with no Linux equivalents or alternatives provided. Examples and instructions for running the installer are exclusively Windows/PowerShell-based. While Linux server discovery is supported, the documentation does not provide parity in appliance setup or usage for Linux environments.
Recommendations
  • Provide a Linux-based Azure Migrate appliance option, or clarify if/why it is not supported.
  • Include Linux shell (bash) installation and setup instructions alongside PowerShell examples.
  • Document Linux equivalents for required services (e.g., web server setup, agent installation) if possible.
  • Explicitly state OS limitations for the appliance early in the prerequisites section.
  • If Windows-only is a technical requirement, offer rationale and guidance for Linux-centric environments.
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-14 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example Windows Heavy
Summary
The documentation exhibits notable Windows bias. Critical steps such as setting up the replication appliance require a Windows Server VM, with no Linux alternative provided. Windows-specific tools and configuration steps (e.g., WinRM, Windows ports, Windows Server versions) are mentioned first or exclusively, while Linux instructions are present but less detailed. The replication appliance setup and installer instructions are Windows-only, meaning Linux users cannot complete the migration without provisioning a Windows VM.
Recommendations
  • Provide instructions for deploying the replication appliance on Linux-based VMs, or clarify if Windows is strictly required and why.
  • Offer parity in example commands and troubleshooting steps for both Windows and Linux environments.
  • Include Linux-first or side-by-side examples for all configuration steps, not just authentication setup.
  • Explicitly state OS requirements and alternatives for users who do not have access to Windows Server licenses.
  • Add guidance for Linux users on preparing, monitoring, and troubleshooting migrations, including equivalent tools and commands.
GitHub Create Pull Request
Migrate Migrate Hyper-V VMs to Azure with the Migration and modernization tool ...blob/main/articles/migrate/tutorial-migrate-hyper-v.md
High Priority View Details →
Scanned: 2026-01-14 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 examples and instructions assume the use of Windows tools (e.g., .exe installers, Windows file paths, Windows-specific utilities like SetupDiag), and command-line instructions use Windows syntax. There is no mention of Linux or macOS hosts, nor are there alternative instructions for non-Windows platforms. The migration workflow is designed for Hyper-V, which is a Windows-only virtualization technology, but the documentation also assumes Windows as the host OS for all steps, including troubleshooting and post-migration tasks.
Recommendations
  • Explicitly state that the migration tool and process are only supported on Windows/Hyper-V hosts, if that is the case.
  • If Linux/macOS hosts or management are possible, provide equivalent instructions, tools, and examples for those platforms.
  • Clarify any steps that are Windows-specific and offer alternatives or workarounds for Linux/macOS users where possible (e.g., remote management, using Azure CLI, or PowerShell Core on non-Windows platforms).
  • Add notes about limitations for non-Windows users and link to relevant cross-platform migration guides if available.
  • Ensure post-migration best practices include Linux-specific recommendations where appropriate (e.g., troubleshooting Linux VM activation, security hardening for Linux VMs).
GitHub Create Pull Request
← Previous Page 1 of 37 Next →