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 26-50 of 218 flagged pages
Migrate
Assess Hyper-V VMs for migration to Azure VMs with Azure Migrate
.../blob/main/articles/migrate/tutorial-assess-hyper-v.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation is focused exclusively on assessing Hyper-V VMs for migration to Azure, which inherently targets Windows environments. There are no Linux-specific examples, tools, or instructions, and the tutorial assumes the reader is working with Hyper-V (a Windows-only hypervisor). Linux alternatives, such as KVM or VMware, are not mentioned, nor are Linux command-line tools or workflows. The only Linux reference is in the context of licensing (RHEL/SLES for Azure Hybrid Benefit), not in migration or assessment steps.
Recommendations
- Provide parallel documentation for assessing Linux-based VMs (e.g., KVM, VMware) for migration to Azure.
- Include examples and instructions for Linux environments, such as how to collect performance data from Linux VMs.
- Mention Linux-specific migration considerations, such as differences in disk formats, networking, and OS compatibility.
- Clarify in the prerequisites or introduction that this tutorial is Windows/Hyper-V specific, and link to Linux/KVM/VMware migration guides.
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 →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page exhibits a notable Windows bias. The Azure Migrate appliance is required to run on Windows Server 2019/2022, with no Linux deployment option mentioned. All installation and configuration steps are presented exclusively using PowerShell and Windows tools (IIS, Windows Activation Service, registry edits), with no Linux equivalents or alternatives. The appliance setup, troubleshooting, and file paths are Windows-centric. While Linux server discovery is supported, the documentation provides only basic instructions for enabling SSH and root login, lacking detailed Linux-centric guidance or examples for appliance deployment, installation, or troubleshooting.
Recommendations
- Provide instructions for deploying and running the Azure Migrate appliance on Linux servers, if supported, or clarify platform limitations.
- Include Linux shell (bash) equivalents for installation, configuration, and troubleshooting steps, alongside PowerShell commands.
- Mention Linux alternatives for required components (e.g., web server, service management, file paths) and provide guidance for Linux users.
- If the appliance is Windows-only, clearly state this limitation at the start and offer guidance for Linux-only environments (such as using a Windows VM for the appliance).
- Ensure examples and instructions for both Windows and Linux are presented in parallel, not Windows-first.
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 →
Detected Bias Types
Windows Tools
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation is heavily oriented toward Windows environments, specifically Hyper-V on Windows Server. All command-line examples use Windows paths and executables (.exe files), and instructions reference Windows-specific tools and conventions (e.g., SetupDiag, %Programdata%, C:\Program Files). There are no Linux or macOS equivalents, nor any mention of how to perform similar tasks on non-Windows platforms. Even in sections about post-migration management, Windows is referenced first or exclusively (e.g., Windows activation troubleshooting, Windows Server OS upgrade).
Recommendations
- Clarify early in the documentation that the migration process is only applicable to Hyper-V hosts running on Windows, and explicitly state that Linux/macOS hosts are not supported.
- If any part of the migration tooling or process can be run from Linux/macOS (e.g., Azure CLI, portal operations), provide examples and instructions for those platforms.
- Where post-migration steps reference Windows-specific actions (e.g., activation, OS upgrades), provide equivalent guidance for Linux VMs, such as troubleshooting Linux boot issues, updating kernel/initrd, or configuring SSH.
- In sections about monitoring, security, and management, ensure that Linux-specific best practices and tools are mentioned alongside Windows ones (e.g., Linux patching, SELinux/AppArmor, Linux disk encryption).
- If the process is fundamentally Windows-only, make this clear in the prerequisites and throughout the documentation to avoid confusion for Linux/macOS users.
Migrate
Modernize ASP.NET web apps to Azure App Service code
.../migrate/tutorial-modernize-asp-net-appservice-code.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation page exhibits Windows bias by requiring Windows PowerShell 4.0 on source servers for migration, with no mention of Linux or cross-platform alternatives. There are no examples or instructions for migrating ASP.NET apps from Linux environments, nor is there guidance for Linux-based web servers. The prerequisites and migration steps are tailored exclusively to Windows/IIS scenarios.
Recommendations
- Clarify whether migration of ASP.NET apps from Linux environments is supported, and if so, provide equivalent instructions and tooling.
- If migration is Windows/IIS-only, explicitly state this limitation early in the documentation.
- Offer guidance or links for Linux-based web app migration to Azure App Service, if possible.
- Provide cross-platform migration tooling or alternatives to Windows PowerShell, or note their absence.
- Include a comparison table or section outlining differences in migration approaches for Windows vs. Linux hosts.
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 →
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 for certificate generation, export, and registry modification use PowerShell and Windows-specific tools and paths. There are no Linux/macOS equivalents provided for certificate creation (e.g., OpenSSL), certificate installation, or registry/configuration updates. The instructions for installing certificates and updating registry values are Windows-centric, assuming the appliance runs on Windows and uses Windows Registry. Linux tools are only mentioned in passing, with no actionable guidance.
Recommendations
- Provide equivalent Linux/macOS instructions for certificate generation and export using OpenSSL or mkcert.
- Include steps for installing certificates on Linux-based appliance machines (e.g., using openssl, update-ca-certificates, or keytool).
- Clarify how appliance configuration should be updated on Linux (e.g., via config files or environment variables instead of Windows Registry).
- Offer platform detection guidance to help users follow the correct steps for their OS.
- Present examples for both Windows and Linux/macOS side-by-side or in separate sections.
Migrate
Set up an Azure Migrate appliance for physical servers
...n/articles/migrate/how-to-set-up-appliance-physical.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation is heavily biased towards Windows environments. All setup and installation steps rely exclusively on PowerShell and Windows-specific tools (IIS, Windows Activation Service, Registry Editor). There are no instructions or examples for deploying the appliance on Linux or macOS servers, nor any mention of equivalent Linux commands or prerequisites. The documentation assumes the appliance host is a Windows machine and does not provide parity for Linux users.
Recommendations
- Provide Linux-based installation instructions, including shell script equivalents for the installer.
- Clarify whether the appliance can be hosted on Linux, and if so, detail the steps and requirements.
- List Linux prerequisites (e.g., required packages, services) alongside Windows roles.
- Include Linux command-line examples for extracting the installer, running scripts, and troubleshooting.
- If the appliance is Windows-only, explicitly state this limitation at the beginning of the documentation.
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 →
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, validation, and file paths) are exclusively for Windows Server (2019/2022) and PowerShell. There is no mention of Linux or macOS support, nor are alternative instructions or parity examples provided for non-Windows platforms. Windows-specific tools (CertUtil, PowerShell, IIS, registry edits) are required, and the appliance must be installed on Windows Server. This creates a significant barrier for Linux/macOS users.
Recommendations
- Explicitly state Windows-only support at the beginning of the documentation if Linux/macOS are not supported.
- If possible, provide a Linux-based installer and instructions for deploying the appliance on Linux servers.
- Offer parity examples for common tasks (e.g., checksum validation, script execution) using Linux tools (e.g., sha256sum, bash).
- Clarify whether the appliance or migration process can be containerized or run in a cross-platform manner.
- If Windows is a hard requirement, provide rationale and guidance for Linux/macOS users (e.g., using a Windows VM for the appliance).
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 →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation is focused exclusively on migrating Hyper-V servers (a Windows-centric virtualization platform) to Azure. All instructions, terminology, and tooling (e.g., Hyper-V Replication provider, Azure Site Recovery provider) are specific to Windows environments. There are no Linux or cross-platform migration examples, and the workflow assumes the reader is operating in a Windows/Hyper-V context. Linux alternatives (such as KVM, VMware on Linux, or physical Linux servers) are not mentioned, nor are there references to Linux-specific migration steps or considerations.
Recommendations
- Add explicit statements clarifying that this guide is for Hyper-V (Windows) only, and link to equivalent guides for Linux/KVM/VMware migrations.
- Provide cross-references or a comparison table showing migration workflows for Linux-based hypervisors and physical Linux servers.
- Include a section or links for Linux users on how to migrate their workloads to Azure using agentless or agent-based methods.
- Ensure parity in troubleshooting steps, especially for DNS/network connectivity, by providing Linux command-line examples (e.g., dig, nslookup) alongside any Windows-specific instructions.
- If possible, add a brief note on how Linux VMs can be discovered and migrated using Azure Migrate, and link to relevant documentation.
High Priority
View Details →
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 require Windows Server (2019, 2022, or 2025), and PowerShell is the only scripting/automation method provided. Examples for verifying downloads and performing administrative tasks use Windows-specific tools (CertUtil, Registry Editor, Control Panel), with no mention of Linux equivalents. While the appliance can discover Linux servers, there are no instructions or examples for deploying or managing the appliance on Linux or macOS. This creates significant friction for users in non-Windows environments.
Recommendations
- Explicitly state Windows-only support in the prerequisites and deployment sections if Linux/macOS are not supported.
- If Linux deployment is possible, provide equivalent instructions for Linux (e.g., using Bash, sha256sum, Linux package managers, etc.).
- Offer Linux/macOS alternatives for file verification (e.g., sha256sum, openssl), registry/configuration management, and service management.
- Clarify whether the appliance can be run in a Linux VM or container, and provide guidance if so.
- Add a section addressing Linux/macOS user needs, even if only to explain limitations and suggest workarounds.
- If PowerShell is required, mention cross-platform PowerShell Core and its compatibility, or provide Bash alternatives.
Migrate
Azure Migrate replication appliance
...main/articles/migrate/migrate-replication-appliance.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation for the Azure Migrate replication appliance is heavily Windows-centric. All operating system requirements, examples, and instructions assume Windows Server (2016/2012 R2) as the only supported OS for the appliance. MySQL installation instructions reference only the Windows MSI installer and Windows file paths. There are no examples, instructions, or requirements for deploying or operating the appliance on Linux or macOS, nor is there mention of Linux equivalents for tools or processes. Windows terminology and tools (IIS, Windows Server roles, Group Policies) are referenced exclusively and in detail.
Recommendations
- Clearly state if Linux-based appliances are unsupported. If Linux is supported, add equivalent instructions for deploying and configuring the appliance on Linux (e.g., supported distributions, package requirements, service management).
- Provide MySQL installation instructions for Linux, including package manager commands (apt, yum, etc.) and Linux file paths.
- If possible, offer parity for appliance deployment and management on Linux, including examples for Linux CLI, systemd services, and configuration.
- Reference Linux equivalents for Windows-specific requirements (e.g., IIS alternatives, group policy analogs, locale settings).
- If Windows-only support is intentional, clarify this early in the documentation to set user expectations.
Migrate
Create a custom account with minimal metadata for discovery and assessment.
...b/main/articles/migrate/least-privilege-credentials.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation exclusively references Windows tools and patterns, such as using a command prompt and navigating to a Windows-specific folder path (%ProgramFiles%), and launching a Windows executable (MinimumPrivilegedUser.exe). There are no Linux or macOS equivalents, examples, or guidance provided. The instructions assume a Windows environment throughout, creating friction for users on Linux or macOS platforms.
Recommendations
- Provide instructions for running the utility on Linux/macOS, if supported, or clarify platform limitations.
- If the utility is Windows-only, suggest alternative methods or scripts for Linux users to provision least privileged SQL accounts.
- Include cross-platform examples, such as using Bash or PowerShell Core, and specify file paths and commands for non-Windows environments.
- Explicitly state platform requirements at the beginning of the documentation.
Migrate
Security Best Practices for Deploying an Appliance
.../blob/main/articles/migrate/best-practices-security.md
High Priority
View Details →
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 recommends Windows-specific hardening tools (security baselines, security compliance toolkit, GPOs). There is no mention of Linux-based appliance deployment, nor are Linux hardening or credential management practices discussed. Windows terminology and tools are used exclusively, with Linux only referenced as a migration target, not as a platform for the appliance itself.
Recommendations
- Clarify whether the Azure Migrate appliance can be deployed on Linux. If so, provide equivalent Linux installation instructions (e.g., shell scripts, package requirements).
- Include Linux-specific OS hardening guidance (e.g., CIS benchmarks, SELinux/AppArmor, SSH configuration).
- Mention Linux credential management and encryption practices if supported.
- If PowerShell is not available on Linux, offer Bash or Python alternatives for automation.
- Present examples for both Windows and Linux platforms, or explicitly state Windows-only support if that is the case.
Migrate
Support matrix for web apps migration
...ob/main/articles/migrate/concepts-migration-webapps.md
High Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows Tools
Powershell Heavy
Windows First
Summary
The documentation is heavily biased towards Windows environments, specifically IIS on Windows Server, and requires Windows PowerShell for migration. Linux servers are explicitly not supported, and there are no examples or guidance for Linux or cross-platform users. All requirements and supported scenarios are Windows-centric.
Recommendations
- Clearly state in the introduction that only Windows/IIS environments are supported, and provide a roadmap or alternatives for Linux users.
- If possible, add support for Linux web servers (e.g., Apache, Nginx) in the migration tool and document the process.
- Provide parity by including Linux migration scenarios or explicitly link to alternative migration paths for Linux-based web apps.
- Mention cross-platform tools or scripts if available, or suggest manual migration steps for Linux users.
- Reorder requirements to clarify platform limitations up front, reducing confusion for non-Windows users.
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 →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation is heavily focused on Windows environments, specifically Hyper-V, with exclusive use of Windows tools (Hyper-V Manager, PowerShell commands, CertUtil, Local Group Policy Editor) and examples. 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 step-by-step instructions and screenshots are Windows-centric, creating friction for Linux/macOS users.
Recommendations
- Explicitly state platform requirements and limitations at the beginning of the document (e.g., 'This guide is for Windows/Hyper-V environments only').
- If possible, provide alternative instructions for deploying and managing the appliance from Linux/macOS hosts, or clarify that such options are not supported.
- Include Linux/macOS equivalents for file hash verification (e.g., using sha256sum or shasum).
- Mention remote management options for users who may not have direct access to Windows/Hyper-V hosts.
- Where PowerShell or Windows tools are used, note if there are cross-platform alternatives or if the steps are Windows-only.
- Add a section on limitations for non-Windows users, and link to resources for VMware or physical server migration guides that may be more Linux-friendly.
Migrate
How does Hyper-V migration work in Azure Migrate?
...ain/articles/migrate/hyper-v-migration-architecture.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation is heavily focused on Windows environments, specifically Hyper-V hosts, and exclusively references Windows tools and workflows (MMC snap-in, Regedit, Windows registry paths). All examples and instructions assume a Windows OS, with no mention of Linux or macOS equivalents, nor guidance for cross-platform scenarios. This creates friction for users who may have mixed environments or wish to automate/manage migration from non-Windows platforms.
Recommendations
- Clarify early in the documentation that the migration process and tooling are Windows/Hyper-V specific, and note any limitations for Linux/macOS users.
- If Linux-based Hyper-V management or migration is possible, provide equivalent instructions and tooling for Linux hosts (e.g., CLI commands, configuration file edits, bandwidth throttling methods).
- Offer guidance or links for users migrating from Linux-based hypervisors (such as KVM, Xen) to Azure, or direct them to relevant Azure Migrate documentation.
- Where possible, abstract instructions to platform-neutral language, or provide parallel steps for Linux/macOS users.
- Explicitly state that registry edits and MMC snap-ins are Windows-only, and suggest alternatives or workarounds for non-Windows environments if available.
Migrate
Discover AWS instances with Azure Migrate Discovery and assessment
...cs/blob/main/articles/migrate/tutorial-discover-aws.md
High Priority
View Details →
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-based appliance deployment. 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 screenshots are Windows-centric, and Linux instructions are limited to enabling SSH access and authentication, with no guidance on Linux-based appliance setup or troubleshooting.
Recommendations
- Provide instructions and support for deploying the Azure Migrate appliance on Linux servers, or clarify if Windows is a strict requirement.
- Include Linux shell (bash) equivalents for installation, configuration, and troubleshooting steps, not just PowerShell.
- Offer Linux-specific examples and screenshots for key steps, such as script execution, log file locations, and service management.
- Document any Linux-compatible tools or patterns for agent installation and server discovery.
- Clearly state platform limitations early in the prerequisites section, and offer alternative approaches for Linux-only environments.
Migrate
Modernize ASP.NET web apps to Azure App Service code
.../migrate/tutorial-modernize-asp-net-appservice-code.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation exhibits Windows bias by requiring Windows PowerShell 4.0 on IIS servers for migration, with no mention of Linux-based alternatives or migration paths for non-Windows environments. There are no Linux/macOS-specific instructions, examples, or tools referenced, and the migration process appears tailored exclusively for Windows/IIS workloads.
Recommendations
- Clarify whether the migration flow supports only Windows/IIS web apps, or if Linux-based ASP.NET Core apps are also supported.
- If Linux-based migration is possible, provide equivalent instructions and tooling for Linux environments (e.g., Bash scripts, CLI commands, or guidance for Apache/Nginx).
- Explicitly state platform limitations and offer alternative migration strategies for Linux/macOS users.
- Add examples and prerequisites for Linux-based web servers if supported.
Migrate
Troubleshoot replication issues in agentless VMware VM migration
...ate/troubleshoot-changed-block-tracking-replication.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page exhibits a strong Windows bias. Troubleshooting steps and examples almost exclusively reference Windows tools (PowerShell, Command Prompt, MMC snap-in, services.msc), and all command-line instructions use PowerShell or Windows-specific utilities. There are no Linux or macOS equivalents provided for key operations such as service management, network connectivity tests, or file editing. The instructions assume the Azure Migrate appliance is accessed via Windows Remote Desktop and managed with Windows-native tools, creating friction for users running the appliance on Linux or preferring cross-platform solutions.
Recommendations
- Provide equivalent Linux/macOS commands for service management (e.g., systemctl for services, netcat/curl for connectivity tests).
- Include azcopy usage examples for Linux/macOS environments.
- Offer guidance for editing host files on Linux (/etc/hosts) and performing DNS lookups (nslookup/dig).
- Clarify whether the Azure Migrate appliance can run on Linux, and if so, provide Linux-specific troubleshooting steps.
- Where PowerShell is used, offer Bash or shell script alternatives.
- Avoid assuming Remote Desktop access; mention SSH for Linux appliances.
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 →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page exhibits a Windows bias by exclusively referencing the Azure Migrate appliance as being deployed on a Windows server, with no mention of Linux deployment options or examples. There are no Linux-specific instructions, examples, or parity in tooling discussed. Windows is presented as the default and only supported platform for the appliance, which may exclude Linux/macOS users from following the documented process.
Recommendations
- Explicitly state whether Linux-based appliances are supported or not. If not supported, clarify this limitation for users.
- If Linux deployment is possible, provide equivalent instructions and examples for Linux servers.
- Include a section addressing assessment of Linux servers, even if the appliance must run on Windows, to guide Linux users through the process.
- Offer alternative methods or third-party tools for Linux environments if Azure Migrate appliance is Windows-only.
Migrate
Troubleshoot Windows upgrade issues
...ocs/blob/main/articles/migrate/troubleshoot-upgrade.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation is exclusively focused on troubleshooting Windows OS upgrade issues during VM migration, with all examples, terminology, and linked resources specific to Windows. There are no references to Linux or macOS upgrade scenarios, tools, or troubleshooting steps, and all recommended actions and links are Windows-centric.
Recommendations
- Include equivalent troubleshooting guidance for Linux VM OS upgrades, such as handling disk limits, expanding disks, and addressing migration errors.
- Provide examples and links for Linux-specific upgrade processes (e.g., using cloud-init, shell scripts, or distribution-specific tools).
- Clarify in the introduction that the scope is Windows-only, or expand the article to cover Linux and macOS migration scenarios if relevant.
- Add cross-references to Linux migration documentation where appropriate.
Migrate
ASP.NET app containerization and migration to App Service
...te/tutorial-app-containerization-aspnet-app-service.md
High Priority
View Details →
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 Windows-specific, requiring a Windows machine to run the Azure Migrate App Containerization tool. PowerShell and Windows-specific tools (like Microsoft Web Deploy) are required, and all examples and steps assume Windows servers and administrative patterns. There are no Linux/macOS alternatives or examples for ASP.NET containerization, and Linux is only mentioned in the context of Java/Tomcat apps.
Recommendations
- Provide parity for Linux/macOS users by offering a version of the Azure Migrate App Containerization tool that runs on Linux/macOS, or document alternative workflows for those platforms.
- Include Linux-based examples for ASP.NET Core apps, which can run cross-platform, and clarify the limitations for .NET Framework apps.
- Document any CLI or Docker-based alternatives for users who cannot use Windows or PowerShell.
- Explicitly state platform limitations earlier in the documentation, and link to Linux/macOS alternatives where possible.
- Consider supporting SSH-based discovery and deployment for Linux servers, not just PowerShell remoting for Windows.
Migrate
Troubleshoot web apps migration issues
...ain/articles/migrate/troubleshoot-webapps-migration.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Missing Linux Example
Windows First
Summary
The documentation is heavily focused on IIS web servers and PowerShell-based troubleshooting steps, which are Windows-specific. All error codes and troubleshooting guidance assume the migration source is a Windows/IIS environment, with no mention of Linux-based web servers (e.g., Apache, Nginx) or Linux migration scenarios. PowerShell is referenced as the primary automation and troubleshooting tool, with no Bash or Linux command alternatives. This creates friction for users migrating from Linux environments or seeking parity in troubleshooting steps.
Recommendations
- Include troubleshooting steps and error codes relevant to Linux-based web servers (e.g., Apache, Nginx).
- Provide Linux/Bash command examples alongside PowerShell commands where applicable.
- Clarify in the introduction or prerequisites that the guidance is specific to IIS/Windows migrations, and link to Linux migration documentation if available.
- Add parity for Linux migration scenarios, including common errors, troubleshooting steps, and supported features.
- Mention Linux tools (such as SSH, SCP, rsync) where remote connectivity or file transfer is discussed.
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 →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation is heavily biased towards Windows environments for ASP.NET containerization. All instructions, prerequisites, and tooling are Windows-specific, requiring a Windows machine, PowerShell, and Microsoft Web Deploy. There are no Linux/macOS alternatives or examples for ASP.NET, 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 alternatives for running the Azure Migrate: App Containerization tool, or clarify platform limitations up front.
- Offer Dockerfile and containerization instructions that can be executed on Linux/macOS for ASP.NET Core apps (where feasible).
- Include cross-platform CLI examples (e.g., Bash, Azure CLI) alongside PowerShell commands.
- Document any manual containerization steps for ASP.NET apps that can be performed without the Windows-only tool.
- Explicitly state platform support and limitations in the prerequisites section.
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 →
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, with all installation and usage instructions requiring a Windows machine and PowerShell. There are no instructions or alternatives for running the tool on Linux or macOS, nor are there examples using Linux-native tools or shell commands. This creates a significant barrier for users who do not have access to a Windows environment.
Recommendations
- Provide a Linux-compatible version of the Azure Migrate: App Containerization tool, or document how to run it on Linux (e.g., via Wine, containers, or WSL).
- Include installation and usage instructions for Linux and macOS users, using Bash or shell commands where appropriate.
- Clearly state platform limitations at the top of the documentation and suggest workarounds or alternatives for non-Windows users.
- Offer downloadable artifacts (Dockerfile, YAML, etc.) independently of the tool, so users can manually complete steps on any platform.
- Consider providing a web-based or containerized version of the tool that is platform-agnostic.
Migrate
Containerization and migration of Java web applications to Azure App Service.
...rate/tutorial-app-containerization-java-app-service.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation is heavily biased towards Windows, requiring a Windows machine to run the Azure Migrate: App Containerization tool, with all installation and operational instructions given for Windows and PowerShell only. There are no instructions or examples for running the tool on Linux or macOS, nor are alternative methods or parity tools mentioned for non-Windows users. Troubleshooting and log file locations are also Windows-specific.
Recommendations
- Provide instructions and support for running the Azure Migrate: App Containerization tool on Linux and macOS, or clarify if this is not possible.
- Include Linux/macOS installation steps, such as using shell scripts or package managers, alongside PowerShell examples.
- Offer troubleshooting guidance for non-Windows environments, or explicitly state platform limitations.
- If the tool is Windows-only, suggest alternative containerization workflows for Linux/macOS users (e.g., manual Dockerfile creation, use of Azure CLI, or other Azure migration tools).
- Clearly indicate platform requirements at the start of the documentation and link to Linux/macOS alternatives if available.