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 551-575 of 918 flagged pages
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/tutorial-app-containerization-java-app-service.md
...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 exhibits a strong Windows bias: it requires the Azure Migrate: App Containerization tool to be installed and run exclusively on a Windows machine, with explicit instructions for Windows Server and Windows 10. All installation and usage steps are Windows-centric, including PowerShell-based installation commands and references to Windows file paths for logs. There are no instructions or examples for running the tool from Linux or macOS environments, nor are there alternative CLI or cross-platform approaches provided. The documentation assumes the user's administrative environment is Windows, even though the applications being containerized are running on Linux servers.
Recommendations
- Provide installation and usage instructions for Linux and macOS environments, or clearly state if the tool is Windows-only and explain the rationale.
- Offer cross-platform alternatives (e.g., Docker-based installer, CLI tools) for users who do not have access to a Windows machine.
- Include Linux shell (bash) equivalents for installation and management steps, not just PowerShell.
- Document any plans or limitations regarding cross-platform support for the App Containerization tool.
- If Windows is a hard requirement, highlight this early and suggest workarounds (e.g., using a Windows VM or cloud-hosted Windows environment) for Linux/macOS users.
Create Pull Request
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/tutorial-app-containerization-aspnet-app-service.md
...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 towards Windows environments. All prerequisites, instructions, and tooling are centered on Windows OS, requiring a Windows machine to run the Azure Migrate App Containerization tool. Steps involve PowerShell, Windows authentication, and Microsoft Web Deploy, with no mention of Linux alternatives or cross-platform support for ASP.NET app containerization. There are no Linux-based examples or guidance for users who may want to containerize ASP.NET apps from Linux servers.
Recommendations
- Provide explicit information about Linux support or lack thereof for ASP.NET app containerization. If not supported, state this clearly at the beginning.
- If possible, develop and document a Linux-compatible version of the App Containerization tool or alternative workflows for Linux users.
- Include Linux-based examples and instructions for containerizing ASP.NET Core applications running on Linux, if supported.
- Offer PowerShell alternatives (such as Bash scripts) where feasible, or clarify that the process is Windows-only.
- Mention cross-platform tools (like Docker CLI, VS Code, or Azure CLI) where appropriate, and provide parity in documentation structure and examples.
- Add a comparison table summarizing OS/tooling requirements for each supported scenario (ASP.NET on Windows, Java on Linux, etc.) to set clear expectations.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/tutorial-app-containerization-java-kubernetes.md
...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 demonstrates 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/11. All installation and operational instructions (including PowerShell commands and file paths) are Windows-centric, with no equivalent instructions or support for Linux or macOS environments. The use of PowerShell for installation, Windows-specific file paths for artifacts and logs, and the lack of Linux-native installation or usage examples further reinforce this bias. While the tool targets containerizing Java apps running on Linux servers, the management and orchestration are exclusively tied to Windows.
Recommendations
- Provide a Linux-native version of the Azure Migrate: App Containerization tool, or at least document how to run it on Linux (e.g., via Wine, Docker, or a cross-platform .NET runtime).
- Include installation and usage instructions for Linux and macOS environments, including shell (bash) equivalents for PowerShell commands.
- Document file paths and log locations for non-Windows systems, or clarify if the tool is Windows-only.
- If Windows is a hard requirement, clearly state this limitation at the top of the documentation and provide rationale and alternatives for Linux users.
- Consider offering a web-based or containerized version of the tool that can be run from any OS.
- Add troubleshooting and artifact download instructions for Linux environments if/when supported.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/tutorial-assess-aspnet-aks.md
...ob/main/articles/migrate/tutorial-assess-aspnet-aks.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows bias primarily in the ASP.NET assessment flow. It references Windows-specific requirements (such as the need for Windows node pools for ASP.NET apps), and the 'Next steps' section highlights optimizing Windows Dockerfiles without mentioning Linux equivalents. There are no Linux or cross-platform command-line examples, and the documentation does not provide parity in discussing Linux-based deployments or optimizations, especially for Java workloads that are commonly Linux-based.
Recommendations
- Include explicit Linux-based assessment and deployment guidance, especially for Java workloads, such as mentioning Linux node pools and their configuration.
- Provide examples or references for optimizing Linux Dockerfiles alongside Windows Dockerfiles in the 'Next steps' section.
- Clarify when Windows node pools are required (e.g., only for ASP.NET Framework apps) and highlight that Linux node pools are the default/recommended for .NET Core and Java apps.
- Add parity in troubleshooting, cost, and readiness explanations for Linux-based web apps.
- Wherever Windows-specific tools or patterns are mentioned, provide Linux equivalents or note when they are not required for Linux workloads.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/troubleshoot-dependencies.md
...lob/main/articles/migrate/troubleshoot-dependencies.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows bias in several ways: Windows tools and PowerShell commands are frequently mentioned first or exclusively, with Linux equivalents either appearing later or being less detailed. Troubleshooting steps and remediation instructions often focus on Windows-specific tools (e.g., PowerShell, WMI, Registry Editor) and GUI workflows, while Linux instructions are sometimes missing, less prominent, or require more manual intervention. Some error resolutions are only described for Windows, and Linux guidance is less comprehensive or absent in certain cases.
Recommendations
- Ensure that for every Windows/Powershell example or troubleshooting step, a Linux equivalent is provided with equal detail and prominence.
- When listing connection methods, tools, or commands, present Windows and Linux options together, or alternate which is presented first.
- Expand Linux troubleshooting sections to match the depth and clarity of Windows instructions, including step-by-step guides and command-line examples.
- For error codes and remediation steps that currently focus on Windows (e.g., WMI, PowerShell, Registry, UAC), provide parallel Linux-focused guidance (e.g., systemd, SSH, sudoers, file permissions).
- Where GUI-based instructions are given for Windows (e.g., Control Panel, Registry Editor), offer CLI-based alternatives for Linux (e.g., editing config files, using systemctl, etc.).
- Review all error tables and ensure Linux-specific errors and resolutions are as visible and detailed as Windows ones.
- Consider adding a summary table mapping Windows tools/concepts to their Linux equivalents for quick reference.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/tutorial-assess-sql-vmware.md
...ob/main/articles/migrate/tutorial-assess-sql-vmware.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by referencing Windows-specific tools and patterns (such as Cloud Witness and Windows Server Failover Clusters) without mentioning Linux equivalents. The only linked performance guidelines are for Windows, and there are no Linux-specific instructions, examples, or references to Linux-based SQL Server deployments. The documentation assumes a Windows-centric environment, omitting guidance for users running SQL Server on Linux VMs.
Recommendations
- Include explicit guidance and examples for assessing SQL Server instances running on Linux VMs, including any differences in discovery, assessment, or migration steps.
- Reference and link to performance guidelines and best practices for SQL Server on Linux VMs, not just Windows.
- When discussing high availability and disaster recovery, mention Linux clustering options (such as Pacemaker) and provide relevant Azure documentation links.
- Clarify whether the Azure Migrate appliance and assessment process supports both Windows and Linux SQL Server instances, and note any limitations.
- Add Linux-specific screenshots or CLI examples where appropriate, and ensure parity in step-by-step instructions for both platforms.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/tutorial-migrate-vmware-agent.md
...main/articles/migrate/tutorial-migrate-vmware-agent.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows bias in several areas: the replication appliance is described as a Windows Server 2016 VM, setup steps and screenshots are Windows-centric, and registry edits for push installation are only detailed for Windows. The installation and management of the Azure VM agent is automated for Windows but manual for Linux, and there are no concrete Linux command examples or detailed Linux-specific troubleshooting steps. Windows tools and patterns (e.g., registry edits, PowerCLI, Windows Server installation) are mentioned first and in more detail, while Linux equivalents are only briefly referenced.
Recommendations
- Provide parallel, step-by-step Linux examples for all major procedures, including Mobility service installation, agent management, and troubleshooting.
- Include Linux command-line examples (e.g., SSH, sudo, package installation) where Windows registry or PowerShell commands are given.
- Clarify whether the replication appliance can run on Linux, and if not, state this explicitly and provide rationale.
- Offer Linux-specific troubleshooting guidance, such as common SELinux, firewall, or permissions issues.
- Ensure that post-migration steps (such as agent installation and removal) are equally detailed for Linux, including supported distributions and commands.
- Balance the order of presentation so that Linux and Windows instructions are presented together or in parallel sections, rather than Windows-first.
- Reference Linux documentation and tools (e.g., cloud-init, systemd services) where appropriate, not just Windows tools.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/tutorial-discover-hyper-v.md
...lob/main/articles/migrate/tutorial-discover-hyper-v.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a strong Windows bias. All setup, configuration, and troubleshooting steps are presented exclusively using Windows tools (Hyper-V Manager, PowerShell, Windows Server), with no Linux-based alternatives or examples. PowerShell commands are used throughout for automation and configuration, and there is no mention of how to perform equivalent actions from a Linux environment. Even when Linux servers are mentioned as supported for discovery, all operational instructions and examples are Windows-centric, and Linux-specific guidance is minimal or absent.
Recommendations
- Provide equivalent instructions and examples for performing discovery and appliance setup from a Linux host, where possible (e.g., using Linux KVM or other virtualization platforms).
- Include Linux command-line alternatives for steps currently shown only with PowerShell or Windows tools.
- Clarify any limitations or requirements for Linux users (e.g., if appliance setup is only supported on Windows, state this explicitly and suggest workarounds or alternatives).
- Add troubleshooting steps and examples relevant to Linux environments, especially for network connectivity, credential management, and agentless discovery.
- Ensure that Linux and Windows examples are presented with equal prominence, or at least provide clear cross-references.
- Where only Windows is supported (e.g., Hyper-V-specific steps), clearly state this and link to equivalent Linux documentation for similar scenarios (e.g., VMware or KVM discovery).
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/tutorial-assess-vmware-azure-vm.md
...in/articles/migrate/tutorial-assess-vmware-azure-vm.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing Windows Server and its licensing options (Azure Hybrid Benefit) before Linux equivalents, and by focusing on Windows Server versions in the assessment review. There is a lack of Linux-specific examples, guidance, or parity in the explanations, especially regarding licensing, supportability, and readiness reporting. Linux is only briefly mentioned in the context of RHEL and SLES licensing, with no further details or examples for other distributions or Linux-specific migration considerations.
Recommendations
- Provide explicit Linux examples and guidance throughout the documentation, such as how assessments handle common Linux distributions (Ubuntu, CentOS, Debian, etc.), not just RHEL and SLES.
- Ensure that supportability and readiness sections discuss both Windows and Linux VMs equally, including how different Linux distributions are assessed for Azure compatibility.
- Include Linux-specific licensing and cost optimization options, and clarify how Azure Hybrid Benefit applies to Linux beyond RHEL/SLES.
- Add screenshots and walkthroughs that show Linux VMs being assessed, not just Windows Server.
- Wherever Windows Server is mentioned, ensure Linux is mentioned with equal detail and prominence.
- Clarify any differences in migration or assessment steps for Linux VMs, such as agent requirements, support for agentless assessment, or common issues unique to Linux workloads.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/tutorial-discover-aws.md
...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 demonstrates a Windows bias in several ways: Windows is the only supported OS for the Azure Migrate appliance, with explicit requirements for Windows Server 2019/2022. All setup and verification steps (e.g., running the installer, verifying hashes) use Windows-specific tools (PowerShell, CertUtil, Windows command prompt), and there are no equivalent instructions or examples for Linux. The appliance installation and operation rely on Windows features (IIS, PowerShell ISE, Windows Activation Service), and Linux is only mentioned as a discovery target, not as a platform for running the appliance itself. This results in missing Linux parity for users who may want to deploy or manage the appliance from a Linux environment.
Recommendations
- Provide a Linux-based version of the Azure Migrate appliance, or clarify if it is not supported.
- Include Linux shell (bash) equivalents for all command-line steps, such as verifying file hashes (e.g., using sha256sum).
- Offer instructions for running the installer and managing the appliance from a Linux environment, if possible.
- Mention Linux tools and patterns alongside Windows tools, or at least acknowledge the lack of Linux support and suggest workarounds.
- Ensure that all examples and screenshots are balanced between Windows and Linux where applicable, or clearly state OS limitations up front.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/tutorial-discover-physical.md
...ob/main/articles/migrate/tutorial-discover-physical.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows bias in several ways: Windows setup instructions and tooling (PowerShell, CertUtil, IIS, registry edits) are presented in greater detail and appear before Linux equivalents. The installer script and appliance setup are described almost exclusively in terms of Windows commands and tools, with no Linux-specific installation or verification examples. There is also a lack of parity in troubleshooting/logging guidance and command-line examples for Linux environments.
Recommendations
- Provide parallel Linux instructions for downloading, verifying, and running the installer script (e.g., using wget/curl, sha256sum, bash).
- Include Linux-specific examples for verifying the hash of the installer (e.g., 'sha256sum AzureMigrateInstaller.zip').
- Clarify whether the Azure Migrate appliance can be installed on Linux, and if so, provide step-by-step Linux installation and configuration instructions.
- Offer troubleshooting and log file location guidance for Linux environments.
- Balance the order of presentation so that Linux and Windows instructions are given equal prominence, or group them under clear OS-specific headings.
- If the appliance is Windows-only, state this clearly at the outset and provide guidance for Linux server discovery from a Windows-based appliance.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/tutorial-discover-gcp.md
...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 demonstrates a Windows bias in several ways: Windows Server is the only supported OS for running the Azure Migrate appliance, with explicit requirements for Windows Server 2019 or 2022. All setup and verification steps (e.g., running installer scripts, verifying file hashes) use Windows-specific tools (PowerShell, CertUtil, Windows command prompt), with no mention of Linux equivalents or alternatives. The appliance installation process is entirely PowerShell-based, and there are no instructions or examples for deploying or running the appliance on Linux. While Linux server discovery is supported, the documentation assumes a Windows environment for all core setup tasks, and Linux examples are limited to configuring SSH for discovery, not for appliance deployment or management.
Recommendations
- Provide instructions and supported options for running the Azure Migrate appliance on Linux servers, or explicitly state if Linux is not supported.
- Include Linux-based examples for verifying downloaded files (e.g., using sha256sum or openssl) alongside CertUtil.
- Offer alternative installation and management steps using Bash or shell scripts if possible, or clarify the Windows-only nature of the appliance.
- Balance the order of presentation: mention Linux and Windows requirements together, and provide parallel examples for both platforms where applicable.
- If the appliance is Windows-only, clearly state this limitation early in the documentation and suggest workarounds or alternatives for Linux-centric environments.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/tutorial-migrate-vmware.md
.../blob/main/articles/migrate/tutorial-migrate-vmware.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Powershell Heavy
Summary
The documentation demonstrates a Windows bias by providing specific details and options for Windows Server (such as OS upgrade and troubleshooting activation), referencing PowerShell as a setup method, and mentioning Windows tools (like SetupDiag) without equivalent Linux guidance. There are no Linux-specific migration, troubleshooting, or upgrade instructions, and Windows scenarios are often mentioned first or exclusively.
Recommendations
- Provide equivalent Linux migration and troubleshooting steps, such as how to handle common Linux post-migration issues (e.g., bootloader repair, network configuration).
- When mentioning Windows-specific tools (e.g., SetupDiag), also mention or link to Linux equivalents (such as log file locations or diagnostic tools for Linux OS upgrades).
- If offering a PowerShell script for appliance setup, also provide a Bash/shell script or instructions for Linux environments.
- Include explicit examples or notes for migrating Linux VMs, including any special considerations (e.g., kernel versions, supported distributions, post-migration agent installation).
- Balance references to Windows and Linux throughout the documentation, ensuring both are addressed in parallel where relevant.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/whats-new.md
...ocs/azure-docs/blob/main/articles/migrate/whats-new.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation for Azure Migrate demonstrates a moderate Windows bias. Windows-specific tools (e.g., PowerShell, Windows Server, IIS) and features are frequently mentioned, often before or instead of Linux equivalents. Many examples and feature highlights focus on Windows workloads (Windows Server, SQL Server, ASP.NET, IIS), and automation or scripting references are almost exclusively to PowerShell, with little to no mention of Bash or Linux-native tools. While Linux support is mentioned (e.g., SSH authentication, RHEL/SLES migration), Linux-specific guidance, examples, or parity in tooling references are often missing or less detailed.
Recommendations
- Provide Linux-specific examples and workflows alongside Windows ones, especially for automation (e.g., Bash scripts, Linux CLI commands).
- Mention Linux-native tools (e.g., shell scripts, systemd, cron) where PowerShell or Windows tools are referenced.
- Ensure that Linux migration scenarios (e.g., Apache, NGINX, MySQL, Tomcat) are given equal prominence and detail as Windows scenarios (e.g., IIS, SQL Server, ASP.NET).
- Add explicit Linux-focused tutorials or quickstarts where only Windows examples are currently present.
- Clarify when features or tools are Windows-only, and provide Linux alternatives or workarounds where possible.
- Include references to Linux distributions and their specific requirements or best practices in migration contexts.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/tutorial-migrate-physical-virtual-machines.md
.../migrate/tutorial-migrate-physical-virtual-machines.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows-first bias in several areas: Windows and PowerShell are mentioned or used as the default or primary example for appliance setup, registry and group policy checks, and agent installation. Windows-specific tools and troubleshooting steps (e.g., SetupDiag, registry keys, group policies) are detailed, while Linux equivalents are either missing or only briefly referenced. Linux instructions are present but less prominent, and some steps (like agent installation) provide more detail for Windows than Linux.
Recommendations
- Ensure Linux instructions are given equal prominence and detail as Windows instructions, especially for critical steps like appliance setup, agent installation, and troubleshooting.
- Provide explicit Linux command-line examples for all steps where Windows/PowerShell examples are given (e.g., appliance setup, agent registration, prerequisite validation).
- Include Linux-specific troubleshooting guidance, such as relevant log file locations, systemd/service management, and SELinux/AppArmor considerations.
- When referencing Windows tools (e.g., SetupDiag, registry, group policy), also mention or link to Linux equivalents (e.g., log files, system configuration files, relevant commands).
- Avoid assuming the replication appliance or management host is always Windows; clarify Linux support and provide setup instructions for both platforms.
- In checklists and summary tables, list Linux and Windows steps side by side to reinforce parity.
- Review all screenshots and UI walkthroughs to ensure they are not exclusively Windows-centric if Linux is supported.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/tutorial-migrate-hyper-v.md
...blob/main/articles/migrate/tutorial-migrate-hyper-v.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a strong Windows bias. All command-line examples and tooling instructions are Windows-centric, focusing exclusively on Windows executables, file paths, and patterns (e.g., .exe installers, %Programdata% variables, C:\Program Files). There are no Linux or cross-platform command-line examples, and the documentation assumes the use of Windows-based Hyper-V hosts and management environments. Even in sections discussing post-migration best practices, Windows is mentioned first or exclusively in several places, and Linux is only briefly referenced in a generic context.
Recommendations
- Explicitly state that the Migration and modernization tool for Hyper-V is only supported on Windows, if that is the case. If Linux-based Hyper-V management or migration is possible, provide equivalent Linux/Bash command-line examples.
- Where possible, use cross-platform language and avoid hardcoding Windows-specific paths or tools in the main flow. If Windows-only, clarify this early in the prerequisites.
- In post-migration sections, provide parity for Linux VMs, such as troubleshooting, activation, and security recommendations specific to Linux.
- If the migration process or tooling is fundamentally Windows-only (due to Hyper-V's architecture), make this limitation clear at the top of the documentation, and link to Linux migration guides for other scenarios.
- Where Linux is supported (e.g., as a guest OS), include explicit notes or steps for Linux VMs, such as post-migration configuration, agent installation, or troubleshooting.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/create-manage-projects.md
...s/blob/main/articles/migrate/create-manage-projects.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by providing command-line examples specifically for PowerShell, referencing the use of PowerShell as the default shell, and omitting equivalent instructions for Linux or macOS environments. The instructions for installing and using the Azure CLI are explicitly tied to PowerShell, and there are no examples or notes for users on Linux or macOS platforms. Additionally, the documentation does not mention or show screenshots from non-Windows environments, reinforcing a Windows-centric approach.
Recommendations
- Provide parallel command-line examples for Linux/macOS shells (e.g., Bash) alongside PowerShell instructions.
- Clarify that the Azure CLI can be used on Windows, Linux, and macOS, and provide installation and usage instructions for each platform.
- Include notes or callouts for cross-platform compatibility, highlighting any differences in steps or commands between Windows and Linux/macOS.
- Add screenshots or terminal snippets from non-Windows environments to demonstrate parity.
- Avoid assuming PowerShell as the default shell; instead, refer to 'your terminal' or 'command prompt' and specify platform-specific instructions where relevant.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/create-project.md
...zure-docs/blob/main/articles/migrate/create-project.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by providing command-line examples specifically for PowerShell, referencing PowerShell explicitly, and omitting equivalent instructions for Linux/macOS environments. The Az CLI installation and usage steps are described as being performed in PowerShell, with no mention of Bash or other shells. There are no Linux-specific screenshots, instructions, or clarifications, and the workflow assumes a Windows-centric user environment.
Recommendations
- Provide parallel command-line examples for both PowerShell (Windows) and Bash (Linux/macOS) when demonstrating Az CLI usage.
- Clarify that Az CLI can be used on Windows, Linux, and macOS, and provide installation links or instructions for each platform.
- Avoid referencing PowerShell exclusively; instead, use neutral language such as 'open your terminal' and specify both PowerShell and Bash where appropriate.
- Include notes or sections for Linux/macOS users, especially where file paths, environment variables, or command syntax may differ.
- Add screenshots or step-by-step instructions from Linux/macOS environments where relevant to ensure parity.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/create-web-app-assessment.md
...lob/main/articles/migrate/create-web-app-assessment.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing Windows-specific optimization and best practices in the 'Next steps' section, specifically linking to Windows Dockerfile optimization and Windows container management. There are no equivalent Linux or cross-platform examples or references, and Linux containerization or migration scenarios are not mentioned. The focus on Windows tools and the absence of Linux-specific guidance or parity in examples suggest a bias toward Windows environments.
Recommendations
- Include links and references to Linux Dockerfile optimization and best practices for Linux containers, especially for AKS and App Service scenarios.
- Add examples or guidance for assessing and migrating Linux-based web apps, not just Windows-based ones.
- Ensure that any optimization or best practices documentation referenced covers both Windows and Linux platforms, or provide parallel links for each.
- Explicitly mention that Azure Migrate supports both Windows and Linux workloads, and provide steps or considerations unique to Linux migrations where applicable.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/discover-and-assess-using-private-endpoints.md
...migrate/discover-and-assess-using-private-endpoints.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by providing only Windows/PowerShell-based instructions and examples for setting up and verifying the Azure Migrate appliance. All command-line examples use Windows tools (e.g., CertUtil), and the installer script is run via PowerShell with Windows-style paths. There are no Linux or cross-platform alternatives or guidance for users deploying the appliance on Linux servers, nor are Linux verification or scripting methods mentioned.
Recommendations
- Provide parallel instructions and examples for Linux environments, including how to verify file hashes using common Linux tools (e.g., sha256sum, md5sum).
- Clarify whether the Azure Migrate appliance can be hosted on Linux, and if so, include Linux-specific setup steps and script execution instructions (e.g., bash commands).
- If the appliance is Windows-only, state this explicitly early in the documentation to set expectations for Linux users.
- When referencing command-line instructions, offer both Windows (PowerShell/CMD) and Linux (bash) equivalents where possible.
- Include troubleshooting and log file locations for Linux, if supported.
- Review screenshots and UI references to ensure they are not exclusively Windows-centric if the product supports Linux.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/migrate-support-matrix-physical.md
...in/articles/migrate/migrate-support-matrix-physical.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation demonstrates a Windows bias in several ways: Windows server instructions and requirements are consistently presented before Linux equivalents, with more detailed guidance and troubleshooting for Windows (e.g., PowerShell remoting, WMI, WinRM, domain/local accounts). Windows-specific tools and patterns (PowerShell, WinRM, WMI) are emphasized, and setup scripts are referenced as PowerShell scripts. For SQL Server and web app discovery, Windows is prioritized or exclusively supported, with Linux support limited or absent (e.g., SQL Server discovery not supported on Linux). Example scripts and troubleshooting are provided only for Windows authentication, with no equivalent Linux examples for database or web app discovery.
Recommendations
- Present Linux and Windows instructions in parallel, or alternate which OS is described first in each section.
- Provide equivalent detail for Linux, including troubleshooting steps and example commands/scripts for common scenarios (e.g., database discovery, permissions).
- Where setup scripts are referenced (e.g., PowerShell), offer Bash or cross-platform alternatives for Linux users.
- Explicitly call out feature gaps (such as lack of SQL Server discovery on Linux) and provide roadmap or workarounds if possible.
- Balance the use of Windows-specific terminology (e.g., domain accounts, WMI, WinRM) with Linux equivalents (e.g., SSH, sudoers, PAM), and provide links to relevant Linux documentation.
- For sections where only Windows is supported (e.g., ASP.NET web apps, SQL Server discovery), clearly state this early and suggest alternative approaches for Linux users if available.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/quickstart-create-project.md
...lob/main/articles/migrate/quickstart-create-project.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by providing command-line instructions specifically for PowerShell, referencing PowerShell as the environment to run Azure CLI commands, and omitting equivalent instructions for Linux/macOS users. There are no Linux shell (bash) examples or explicit mention of cross-platform compatibility for the CLI steps.
Recommendations
- Provide Azure CLI command examples in both PowerShell and Bash syntax, or clarify that the commands are cross-platform.
- Explicitly mention that Azure CLI can be used on Windows, Linux, and macOS, and provide links to installation instructions for all platforms.
- Avoid instructing users to open PowerShell specifically; instead, use neutral language such as 'open your terminal' or 'command prompt or terminal'.
- Include notes or callouts for any platform-specific differences in command usage or prerequisites.
- Add screenshots or references that reflect both Windows and Linux environments where applicable.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/discovered-metadata.md
...docs/blob/main/articles/migrate/discovered-metadata.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation exhibits a Windows-first bias in both structure and content. Windows and Windows-centric tools (WMI, PowerShell, Registry, Windows-specific cmdlets) are consistently presented before Linux equivalents, and in some sections (e.g., web app discovery, storage metadata), only Windows examples or tools are described in detail. Linux coverage is often grouped at the end of sections, sometimes with less detail or with generic command references. There is heavy reliance on Windows-native tools and patterns, with Linux alternatives sometimes missing or less thoroughly explained.
Recommendations
- Reorganize sections to present Windows and Linux information in parallel (side-by-side tables or subsections), rather than always listing Windows first.
- Where PowerShell or Windows-specific tools are referenced, provide equivalent Linux commands or scripts with equal detail.
- For sections like ASP.NET, Java, and Spring Boot web app data, clarify if Linux is supported and, if so, provide Linux-specific collection details or explicitly state limitations.
- In the storage metadata section, add equivalent Linux storage metadata collection commands (e.g., using lsblk, df, lsscsi, etc.) and describe how NFS, SMB, and iSCSI are discovered on Linux.
- Ensure that all examples, especially for dependency data and software inventory, include both Windows and Linux command references with similar depth.
- Review the order of presentation throughout the document to avoid reinforcing a Windows-centric perspective.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/how-to-automate-migration.md
...lob/main/articles/migrate/how-to-automate-migration.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation is heavily biased toward Windows environments, as it exclusively references PowerShell scripts and the Azure PowerShell module for automation. There are no examples or instructions for Linux or cross-platform scripting (e.g., Bash, Azure CLI). All script examples use Windows/PowerShell conventions, and there is no mention of how to perform these tasks on Linux or macOS systems.
Recommendations
- Provide equivalent automation scripts using Azure CLI and/or Bash to support Linux and macOS users.
- Include instructions for installing and using the Azure CLI as an alternative to Azure PowerShell.
- Add examples of running migration automation from a Linux shell, including script execution syntax.
- Clearly state the platform requirements and, if scripts are Windows/PowerShell-only, offer guidance or links for Linux users.
- Consider offering cross-platform PowerShell Core (pwsh) compatibility and document any differences or requirements.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/how-to-create-azure-sql-assessment.md
...articles/migrate/how-to-create-azure-sql-assessment.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing Windows-specific tools and patterns (such as Cloud Witness and Windows Server Failover Clusters), linking to Windows-focused best practices, and omitting equivalent Linux guidance or examples. There are no Linux-specific instructions, screenshots, or references to Linux-based SQL Server deployments, and the high availability/disaster recovery sections focus exclusively on Windows clustering technologies.
Recommendations
- Include explicit guidance and examples for assessing SQL Server instances running on Linux, including any differences in discovery, assessment, or migration steps.
- Add references and links to Linux-specific best practices for SQL Server on Azure Virtual Machines, such as performance tuning and high availability options for Linux.
- When discussing high availability and disaster recovery, mention Linux clustering solutions (e.g., Pacemaker) and provide links to relevant documentation.
- Ensure that any tool or feature (such as Cloud Witness or Shared Disk) is described with both Windows and Linux applicability, or clarify if it is Windows-only.
- Provide screenshots and walkthroughs that include Linux-based SQL Server environments, not just Windows.
- Balance references to Windows and Linux in all sections, especially when discussing licensing (e.g., mention RHEL/SLES subscriptions in parity with Windows Server licenses).