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 526-550 of 918 flagged pages
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/migrate-support-matrix.md
...s/blob/main/articles/migrate/migrate-support-matrix.md
High Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Windows Tools
Summary
The documentation page focuses exclusively on VMware, Hyper-V, and physical servers, with no mention of Linux-specific scenarios, tools, or examples. The migration and assessment tools referenced (e.g., Data Migration Assistant, Azure Database Migration Service) are traditionally Windows-centric, and there are no Linux command-line or workflow examples. The structure and examples implicitly assume Windows-based environments, omitting Linux-native tools, patterns, or guidance.
Recommendations
- Include explicit guidance and examples for assessing and migrating Linux servers, including supported Linux distributions and any unique considerations.
- Add Linux-specific tooling or workflow examples (e.g., using SSH, Linux command-line, or automation scripts) alongside or before Windows/PowerShell examples.
- Reference Linux-native migration tools or integration points, if available, and clarify support for Linux workloads in the assessment and migration matrices.
- Ensure parity in documentation structure by providing Linux-focused 'Next steps' and tutorial links, similar to those for VMware and Hyper-V.
Create Pull Request
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/migrate-support-matrix-vmware-migration.md
...les/migrate/migrate-support-matrix-vmware-migration.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation demonstrates a moderate Windows bias. PowerShell is mentioned as the only scripting interface for scaling migration operations, and the deployment of the Azure Migrate appliance is described using a PowerShell script, with no mention of Linux shell alternatives. In several places, Windows-specific instructions or requirements are listed before Linux equivalents, and the replication appliance for agent-based migration is stated to run Windows Server 2016, with no Linux-based option. Windows tools and patterns (e.g., RDP, Windows Firewall, PowerShell) are referenced more prominently than Linux equivalents.
Recommendations
- Provide CLI/bash examples alongside PowerShell for Linux users, especially for appliance deployment and bulk VM operations.
- Clarify if the Azure Migrate appliance and replication appliance can be deployed or managed from Linux environments, and provide instructions if possible.
- List Linux and Windows requirements and instructions in parallel, rather than always listing Windows first.
- Reference Linux-native tools (e.g., SSH, iptables/firewalld) equally when discussing connectivity and firewall configuration.
- If PowerShell is the only supported scripting interface, state this explicitly and provide rationale, or consider supporting cross-platform scripting options.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/hydration-process.md
...e-docs/blob/main/articles/migrate/hydration-process.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by providing more detailed, step-by-step instructions and screenshots for Windows, including explicit PowerShell commands and Windows-specific tools (e.g., diskpart, Task Manager). Windows procedures are described first and in greater depth, while Linux instructions are less detailed, lack screenshots, and often refer users to external distribution documentation for critical steps. Some Linux steps are described only in general terms or as 'illustrative examples' for specific distributions, without the breadth of explicit, actionable examples seen for Windows.
Recommendations
- Provide Linux examples with the same level of detail as Windows, including explicit commands for common distributions (e.g., Ubuntu, RHEL, SUSE) for each step.
- Include screenshots or terminal output for key Linux steps, such as checking agent installation or modifying network settings.
- Offer Linux shell command equivalents for all Windows PowerShell/command prompt examples.
- List Linux and Windows procedures in parallel or side-by-side, or alternate which OS is described first to avoid 'windows_first' ordering.
- Reference Linux tools/utilities (e.g., systemctl, nmcli, lsblk) as directly as Windows tools (e.g., diskpart, PowerShell).
- Expand on manual preparation steps for Linux with concrete, distribution-specific commands and troubleshooting tips.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/migrate-vmware-servers-to-azure-using-private-link.md
...https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/migrate-vmware-servers-to-azure-using-private-link.md
High Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows Tools
Windows First
Summary
The documentation implicitly assumes the Azure Migrate appliance is a Windows-based VM, as seen in instructions like editing the 'hosts file' (a Windows convention) and referencing Windows Server and Software Assurance for Azure Hybrid Benefit. There are no explicit Linux-based examples or guidance for Linux-based appliances, and the only OS-specific benefit mentioned is for Windows Server. Additionally, the documentation refers to editing the DNS hosts file without clarifying Linux equivalents, and does not provide Linux command-line or configuration examples.
Recommendations
- Provide explicit instructions for both Windows and Linux-based Azure Migrate appliances, including how to edit the hosts file on Linux (e.g., /etc/hosts).
- Include examples or notes for Linux-based environments where relevant, such as DNS resolution and network validation commands (e.g., using 'nslookup', 'dig', or 'ping' on Linux).
- Clarify that the Azure Migrate appliance can be deployed on Linux, if supported, or state OS requirements explicitly.
- When discussing Azure Hybrid Benefit, mention Linux licensing or migration considerations, or clarify that the benefit is Windows-specific.
- Ensure parity in troubleshooting and validation steps for both Windows and Linux environments.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/migrate-vmware-servers-to-azure-using-private-link-agent-based.md
...vmware-servers-to-azure-using-private-link-agent-based.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 Azure Hybrid Benefit (which applies only to Windows), and by omitting any Linux-specific instructions or examples. All instructions are generic but implicitly assume Windows environments (e.g., 'dummy account', 'guest credentials', and 'mobility service' installation) without clarifying Linux-specific steps or differences. There are no PowerShell commands, but the lack of Linux parity in examples and terminology is evident.
Recommendations
- Explicitly include Linux-specific instructions for agent installation, credential requirements, and troubleshooting.
- Clarify whether the 'mobility service' installation process differs for Linux and provide a link to Linux-specific guidance if so.
- In sections referencing Azure Hybrid Benefit, mention that this is Windows-only and clarify licensing considerations for Linux VMs.
- Provide examples or notes for Linux environments where steps or terminology differ (e.g., service account creation, DNS configuration).
- Where applicable, include Linux command-line examples (e.g., for DNS resolution or editing hosts file) alongside any Windows instructions.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/prepare-for-migration.md
...cs/blob/main/articles/migrate/prepare-for-migration.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: Windows-specific instructions and tools (e.g., diskpart, PowerShell, RDP, Windows Firewall) are described in detail, often with step-by-step guidance, while Linux instructions are less detailed and sometimes only referenced generically. Windows procedures and troubleshooting are often presented first or in greater depth, and Linux examples or equivalent commands are missing or less emphasized.
Recommendations
- Provide equivalent, step-by-step Linux command-line instructions (e.g., for updating fstab, enabling SSH, rebuilding initramfs, checking required services) alongside Windows examples.
- Include Linux-specific troubleshooting steps and common issues, similar to the detailed Windows sections.
- When referencing tools (e.g., diskpart, PowerShell, Windows Firewall), also mention and provide examples for Linux equivalents (e.g., parted/fdisk, iptables/firewalld/ufw, systemctl).
- Balance the order of presentation so that Linux and Windows instructions are given equal prominence, or clearly separate them into parallel sections.
- Expand the 'Prepare to connect' section for Linux to include more detailed steps (e.g., how to check SSH status, open firewall ports, verify required packages/services).
- Where Windows-specific links are provided (e.g., enabling RDP via PowerShell), provide direct links to Linux equivalents (e.g., enabling SSH, configuring firewall rules).
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/review-web-app-assessment.md
...lob/main/articles/migrate/review-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-centric environments (VMware, Hyper-V, physical servers) and linking to Windows Dockerfile optimization and best practices, without mentioning or providing equivalent Linux examples or guidance. There are no Linux-specific migration, optimization, or best practice references, and the only Dockerfile optimization links are for Windows containers.
Recommendations
- Include Linux-based discovery and migration scenarios, such as guidance for Linux web apps running on Apache/Nginx or Linux VMs.
- Add references and links to Linux Dockerfile optimization and best practices, especially for AKS and App Service on Linux.
- Provide examples and remediation steps for common Linux migration issues alongside Windows examples.
- Balance the 'Next steps' section by including Linux container and app modernization resources.
- Mention and link to Linux appliance requirements and URL access documentation where applicable.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/resources-faq.md
...azure-docs/blob/main/articles/migrate/resources-faq.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-centric tools (such as the MAP Toolkit), mentioning Windows migration scenarios, and omitting explicit Linux or open-source tool examples. While scripting skills mention Bash, PowerShell, and Python, the overall focus and tool references prioritize Windows environments and tools, with little to no mention of Linux-specific migration considerations or examples.
Recommendations
- Include Linux-specific migration tools or references, such as open-source assessment and planning tools commonly used in Linux environments.
- Provide examples or scenarios for migrating Linux servers and workloads, not just VMware, Hyper-V, or Windows-centric tools.
- Mention Linux distributions and their support in Azure Migrate, and clarify any differences or considerations for Linux migrations.
- Balance tool references by including both Windows and Linux tools, and avoid mentioning Windows tools first or exclusively.
- Add sample scripts or automation examples using Bash or Python for Linux migrations, alongside PowerShell for Windows.
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 the use of PowerShell as Administrator, and omitting equivalent instructions for Linux or macOS environments. The Az CLI installation and usage steps are described only in the context of PowerShell, with no mention of Bash or other shells. There are no Linux-specific examples or clarifications, and the workflow assumes a Windows-centric user experience.
Recommendations
- Provide parallel command-line instructions for Linux/macOS users, including Bash shell equivalents for all Az CLI commands.
- When referencing Az CLI installation, link to both Windows and Linux/macOS installation guides, and clarify that Az CLI can be used cross-platform.
- Avoid specifying 'open PowerShell as Administrator' unless a Windows-specific step is required; instead, use neutral language such as 'open your terminal with appropriate permissions.'
- Include screenshots or notes that reflect cross-platform usage where applicable.
- Explicitly state that the steps apply to all supported operating systems, and highlight any OS-specific differences.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/scale-physical-assessment.md
...lob/main/articles/migrate/scale-physical-assessment.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a Windows bias by exclusively referencing the Azure Migrate appliance as being deployed on a Windows server, with no mention of Linux-based deployment options or instructions. There are no examples or guidance for Linux environments, and Windows tooling is assumed as the default for on-premises discovery and assessment.
Recommendations
- Explicitly state whether the Azure Migrate appliance supports Linux hosts, and if so, provide parallel instructions for deploying and managing the appliance on Linux servers.
- Include examples and preparation steps for both Windows and Linux physical servers, such as required permissions, firewall rules, and agent installation.
- If Linux is not supported, clearly document this limitation and suggest alternative approaches for Linux environments.
- Ensure that any scripts, screenshots, or command-line instructions are provided for both Windows (e.g., PowerShell) and Linux (e.g., Bash) where applicable.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/simplified-experience-for-azure-migrate.md
...les/migrate/simplified-experience-for-azure-migrate.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by mandating the use of Windows Server 2019 as the replication appliance, without mentioning any Linux-based alternatives or providing Linux-specific tooling or examples. Despite highlighting improved Linux migration support, the documentation centers the migration process around Windows infrastructure and omits Linux-first or cross-platform approaches.
Recommendations
- Explicitly state whether a Linux-based replication appliance is supported or planned, and provide guidance for Linux-only environments.
- Include examples or workflows for Linux administrators, such as using Linux-based tools or command-line instructions relevant to Linux.
- Clarify if the reliance on Windows Server 2019 is a technical requirement or a current limitation, and discuss any roadmap for Linux parity.
- Provide a comparison table or section that addresses both Windows and Linux administrator experiences equally, ensuring Linux users are not left with unanswered questions.
- If possible, offer alternative migration paths or tools for customers who cannot or do not wish to deploy Windows Server.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/troubleshoot-appliance-diagnostic.md
.../articles/migrate/troubleshoot-appliance-diagnostic.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 file paths (e.g., C:\Users\Public\Desktop\DiagnosticsReport), mentioning Windows Server evaluation licenses, and omitting any mention of Linux-based appliances or instructions for Linux users. There are no Linux command-line examples, file paths, or troubleshooting steps, and all operational context assumes a Windows environment.
Recommendations
- Include equivalent instructions and file paths for Linux-based appliances, if supported (e.g., /home/public/Desktop/DiagnosticsReport or similar).
- Clarify whether the Azure Migrate appliance can run on Linux, and if so, provide Linux-specific troubleshooting steps and examples.
- Mention Linux OS license considerations if relevant, or explicitly state if only Windows appliances are supported.
- Provide parity in screenshots and walkthroughs for both Windows and Linux environments.
- If the appliance is Windows-only, clearly state this at the beginning of the documentation to set user expectations.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/prepare-for-agentless-migration.md
...in/articles/migrate/prepare-for-agentless-migration.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 by presenting Windows-specific instructions, tools, and screenshots before Linux equivalents, providing detailed PowerShell/Command Prompt examples for Windows but only generic or Red Hat-centric examples for Linux. Windows tools (diskpart, PowerShell) are highlighted, while Linux instructions are less detailed, lack parity in example coverage, and sometimes refer users to external documentation for distribution-specific steps.
Recommendations
- Present Linux and Windows instructions in parallel sections or alternate their order to avoid always listing Windows first.
- Provide Linux command-line examples for all major distributions (e.g., Ubuntu, Debian, SUSE) where Windows-specific commands (like diskpart or PowerShell) are given.
- Include screenshots or terminal outputs for Linux steps, similar to the Windows screenshots.
- Expand Linux instructions to cover common scenarios, not just Red Hat-based distributions, and avoid referring users to external docs for critical steps.
- Where Windows tools are mentioned (e.g., diskpart, PowerShell), mention and demonstrate the Linux equivalents (e.g., lsblk, systemctl, nmcli, etc.) in equal detail.
- Ensure that all manual preparation steps for Windows have clear, step-by-step Linux equivalents, including troubleshooting and validation commands.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/troubleshoot-assessment-faq.md
...b/main/articles/migrate/troubleshoot-assessment-faq.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by frequently referencing Windows-specific technologies (e.g., Hyper-V, Windows Server licensing) and providing examples or troubleshooting steps primarily for Windows environments. Linux is mentioned only in passing, often as an exception or with less detail. There are no Linux-specific troubleshooting steps, examples, or parity in licensing considerations. Additionally, the 'Capture network traffic' section focuses on browser tools available on Windows (Edge, Internet Explorer) and omits Linux-specific browsers or tools.
Recommendations
- Include Linux-specific troubleshooting steps and examples, especially for common Linux migration scenarios.
- Provide parity in licensing information, such as how Linux OS licensing is handled or costed in assessments.
- In sections discussing Hyper-V or Windows-specific issues, add equivalent guidance for Linux-based hypervisors (e.g., KVM, Xen) or bare-metal Linux servers.
- In the 'Capture network traffic' section, add instructions for capturing network traffic using Linux browsers (e.g., Firefox) and CLI tools (e.g., tcpdump, Wireshark).
- When listing steps or issues, avoid always mentioning Windows/Hyper-V first; alternate or parallelize with Linux/VMware/KVM where relevant.
- Clarify any product limitations or gaps for Linux environments, not just for Windows/Hyper-V.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/troubleshoot-discovery.md
...s/blob/main/articles/migrate/troubleshoot-discovery.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation demonstrates a Windows bias in several ways: troubleshooting steps and remediation commands are predominantly given for Windows (using PowerShell, WMI, and Windows-specific tools), with Linux examples being minimal or secondary. Many error remediations and validation steps focus on Windows tools (PowerShell, WMI, Windows environment variables, Windows services), and Linux troubleshooting is often limited to SSH connectivity or a simple 'ls' command. In some sections, Windows procedures are described in detail before or instead of Linux equivalents, and Linux-specific troubleshooting guidance is sparse or missing.
Recommendations
- Provide equivalent, detailed Linux troubleshooting steps and commands wherever Windows/PowerShell examples are given (e.g., commands to check OS info, installed packages, running processes, etc., on Linux).
- Include Linux-specific error remediation steps for issues like SSH failures, missing packages, or permissions, similar to the depth provided for Windows/PowerShell/WMI issues.
- When listing error codes or troubleshooting steps, present Windows and Linux solutions in parallel, rather than focusing on Windows first or exclusively.
- Expand Linux examples beyond basic SSH and 'ls' commands; include common troubleshooting commands (e.g., 'uname -a', 'cat /etc/os-release', 'systemctl status', etc.) and configuration file locations.
- For sections that reference Windows environment variables or tools (e.g., %SystemRoot%, WMI, PowerShell), add Linux equivalents (e.g., $HOME, /etc/os-release, systemd services) where applicable.
- Ensure that web app discovery troubleshooting covers Linux-based web servers (e.g., Apache, Nginx) if supported, not just IIS/Windows.
- Instruct users on how to validate connectivity and permissions on Linux systems as thoroughly as for Windows systems.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/troubleshoot-assessment.md
.../blob/main/articles/migrate/troubleshoot-assessment.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 tools and protocols (WinRM, WMI, PowerShell cmdlets) are mentioned first or exclusively in troubleshooting steps, with Linux alternatives (SSH) often mentioned secondarily or with less detail. Several error codes and recommended actions focus on Windows-specific technologies (e.g., WMI, Get-WmiObject, WinRM TrustedHosts) without providing equivalent Linux command examples or troubleshooting steps. The web apps discovery errors section is heavily IIS/Windows-centric, with no mention of Linux-based web servers or migration scenarios.
Recommendations
- For every troubleshooting step involving Windows tools (e.g., WinRM, WMI, PowerShell), provide equivalent Linux commands and troubleshooting steps (e.g., SSH, systemd, journalctl, relevant Linux commands).
- When listing protocols or ports (e.g., WinRM and SSH), present Linux and Windows options in parallel, not always with Windows first.
- Include Linux-specific error codes and troubleshooting guidance where applicable, such as common SSH or Linux service issues.
- For web app migration errors, add examples and troubleshooting steps for Linux-based web servers (e.g., Apache, Nginx, Tomcat) and clarify which steps are Windows/IIS-specific.
- Where PowerShell cmdlets are referenced (e.g., Get-WmiObject), provide equivalent Linux shell commands or scripts for parity.
- Review all sections to ensure Linux scenarios are not only mentioned but are given equal detail and prominence as Windows scenarios.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/troubleshoot-appliance.md
...s/blob/main/articles/migrate/troubleshoot-appliance.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: troubleshooting steps and examples often reference Windows tools (e.g., Control Panel, Notepad, admin command prompt, PowerShell, WMI, WinRM) either exclusively or before Linux equivalents. Some sections, such as time synchronization and hosts file editing, only provide Windows instructions. PowerShell scripts are provided for Windows, while Linux examples are less detailed or missing in some cases. Linux guidance is sometimes present but often less prominent or detailed than Windows guidance.
Recommendations
- For every troubleshooting step that references a Windows tool or command (e.g., Control Panel, Notepad, admin command prompt, PowerShell), provide equivalent Linux instructions (e.g., timedatectl, nano/vi, terminal commands).
- When giving file path examples (e.g., hosts file), include both Windows (C:\...) and Linux (/etc/hosts) locations and editing instructions.
- For time synchronization, include Linux commands (e.g., timedatectl, ntpdate) alongside Windows w32tm instructions.
- Where PowerShell scripts are provided for Windows, offer equivalent Bash or shell scripts for Linux scenarios.
- In sections where only Windows troubleshooting is described (e.g., WMI/WinRM errors, registry edits), clarify if/how these apply to Linux, or explicitly state if not applicable.
- Ensure Linux examples are as detailed and prominent as Windows examples, using tabbed or side-by-side formatting where appropriate.
- Review the order of examples and instructions to avoid always listing Windows first; alternate or use neutral ordering.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/troubleshoot-replication-vmware.md
...in/articles/migrate/troubleshoot-replication-vmware.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: configuration changes on the Azure Migrate appliance are described exclusively using Windows paths (e.g., %programdata%\Microsoft Azure\Config), and the instructions for restarting services use PowerShell and Windows service commands (net stop/start). There are no Linux-based examples or instructions for scenarios where the appliance might be running on Linux, nor is there mention of Linux equivalents for remote access or file editing. The documentation assumes the appliance is a Windows system, omitting guidance for Linux-based deployments.
Recommendations
- Provide parallel instructions for Linux-based appliances, including file paths (e.g., /etc/ or /var/lib/...), service management commands (e.g., systemctl restart servicename), and text editors (e.g., nano, vi).
- When referencing remote access, mention both Remote Desktop (Windows) and SSH (Linux) as options.
- Avoid assuming the appliance is always Windows; clarify OS-specific steps or provide a decision point based on the appliance's operating system.
- Include Linux shell command examples alongside PowerShell/Windows commands.
- Document any differences in configuration file locations, formats, or service names between Windows and Linux deployments.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/troubleshoot-upgrade.md
...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 Windows OS upgrade issues, providing only Windows-specific examples, terminology, and links. There are no references to Linux systems, tools, or equivalent troubleshooting steps for non-Windows environments. The guidance and linked resources are all Windows-centric, and the patterns described (such as in-place upgrades, disk expansion, and error states) are tailored to Windows VMs.
Recommendations
- Add equivalent troubleshooting sections for Linux OS upgrades, including common issues and recommended actions.
- Provide examples and links for Linux VM disk management and upgrade procedures (e.g., using Azure CLI or Linux-native tools).
- Clarify in the introduction that the guidance is Windows-specific, or create a parallel documentation page for Linux OS upgrade troubleshooting.
- Include cross-platform notes or tables comparing Windows and Linux upgrade workflows and potential issues.
- Reference Linux documentation where appropriate, such as for disk expansion or OS version checks.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/troubleshoot-changed-block-tracking-replication.md
...ate/troubleshoot-changed-block-tracking-replication.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation demonstrates a strong Windows bias. All command-line examples and troubleshooting steps are provided exclusively for Windows environments, using PowerShell, Command Prompt, and Windows-specific tools (e.g., services.msc, Net Start/Stop, editing C:\Windows\System32\drivers\etc\hosts). There are no Linux or cross-platform instructions, despite the fact that Azure Migrate appliances can be deployed on both Windows and Linux. Tools like azcopy and Service Bus Explorer are referenced only in the context of Windows usage, and even basic network troubleshooting (e.g., Test-NetConnection, nslookup) is shown only with Windows commands. This limits the documentation's usefulness for Linux users.
Recommendations
- Provide equivalent Linux command-line instructions for all PowerShell/Windows Command Prompt commands (e.g., use curl/nc/telnet for network tests, systemctl/service for service management, and editing /etc/hosts for host resolution).
- Mention and demonstrate how to use azcopy and Service Bus Explorer on Linux, including installation and usage examples.
- Clarify whether the Azure Migrate appliance is supported on Linux, and if so, include Linux-specific troubleshooting steps throughout.
- When referencing file paths or system utilities, include both Windows and Linux equivalents (e.g., hosts file location, service management commands).
- Avoid assuming the user is on Windows by default; structure instructions to present both Windows and Linux options side-by-side or in parallel sections.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/tutorial-app-containerization-aspnet-kubernetes.md
...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, requiring a Windows machine for the Azure Migrate: App Containerization tool, mandating PowerShell remoting, and relying on Windows-specific tools like Microsoft Web Deploy. All code and operational examples are Windows/Powershell-centric, with no Linux or cross-platform alternatives provided for ASP.NET containerization. Linux is only mentioned in the context of Java/Tomcat apps, not for ASP.NET workloads.
Recommendations
- Provide guidance and tooling for running the App Containerization tool on Linux or in a cross-platform manner (e.g., via Docker or WSL).
- Include Linux-based examples for ASP.NET Core apps, which are commonly deployed on Linux containers.
- Offer alternative instructions for environments where PowerShell remoting and Microsoft Web Deploy are not available (e.g., SSH for Linux).
- Clarify early in the documentation that the tool and process are Windows-only for ASP.NET, and suggest alternative migration/containerization paths for Linux users.
- Where possible, use cross-platform CLI tools (e.g., Azure CLI, Docker CLI) in examples, and provide both Windows and Linux command-line snippets.
- Highlight any roadmap or plans for Linux support for ASP.NET containerization, if applicable.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/troubleshoot-spring-boot-discovery.md
...articles/migrate/troubleshoot-spring-boot-discovery.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation demonstrates a Windows bias by providing only PowerShell-based instructions for interacting with Azure resources (e.g., opening PowerShell, using ARMClient in a PowerShell window), and does not mention or provide equivalent steps for Linux or macOS users. The ARMClient tool is introduced with a Windows-centric installation process (downloading and unzipping a .zip, running in PowerShell), and there are no Bash or cross-platform CLI alternatives shown. This may hinder users on non-Windows platforms from following the troubleshooting steps effectively.
Recommendations
- Provide equivalent Linux/macOS instructions, such as using Bash or Azure CLI commands for authentication and resource queries.
- Mention and demonstrate how to install and use ARMClient (or an equivalent tool) on Linux/macOS, or suggest cross-platform alternatives (e.g., Azure CLI az rest).
- When listing steps, avoid assuming the user is on Windows; present cross-platform options or indicate which steps are OS-specific.
- If PowerShell is required, clarify if PowerShell Core (pwsh) can be used on Linux/macOS, and provide relevant instructions.
- Consider reordering or parallelizing instructions so that Linux/macOS methods are presented alongside Windows methods, rather than after or not at all.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/troubleshoot-network-connectivity.md
.../articles/migrate/troubleshoot-network-connectivity.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation page exhibits a Windows-centric bias. Command-line examples (such as nslookup) are shown exclusively with Windows-style prompts (e.g., 'c:\ >'), and PowerShell-specific tools like Test-NetConnection are referenced without Linux or cross-platform alternatives. There are no explicit Linux shell or command examples, nor any mention of Linux-specific troubleshooting steps or tools. Instructions for editing the hosts file and other system operations implicitly assume a Windows environment, and no guidance is provided for Linux users.
Recommendations
- Provide equivalent Linux shell command examples (e.g., use 'dig' or 'host' alongside 'nslookup', and show Linux shell prompts such as '$').
- When referencing PowerShell-specific tools like Test-NetConnection, also mention Linux alternatives (e.g., 'nc', 'telnet', or 'curl').
- Include instructions for editing the hosts file on Linux systems (e.g., '/etc/hosts') in addition to Windows.
- Use neutral or cross-platform language in command examples and screenshots (avoid only showing 'c:\ >' prompts).
- Explicitly state that the troubleshooting steps apply to both Windows and Linux appliances, and call out any differences where relevant.
- Add a section or callouts for Linux-specific troubleshooting considerations, especially for common network and DNS tools.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/troubleshoot-webapps-migration.md
...ain/articles/migrate/troubleshoot-webapps-migration.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-based web app migrations, specifically IIS servers. Troubleshooting steps and error messages repeatedly reference IIS, PowerShell, and Windows-specific configurations, with no mention of Linux-based web servers (such as Apache or Nginx) or Linux migration scenarios. All examples and troubleshooting guidance assume a Windows/IIS/PowerShell environment, excluding Linux users.
Recommendations
- Add equivalent troubleshooting steps and error codes for common Linux web servers (e.g., Apache, Nginx) and migration scenarios.
- Include Linux-specific examples and commands (such as bash scripts or relevant Linux tools) alongside or in place of PowerShell examples.
- Clearly indicate in the introduction if the documentation is only applicable to Windows/IIS migrations, or expand its scope to cover Linux-based migrations.
- Provide parity in error handling and troubleshooting guidance for both Windows and Linux environments.
- Reference Linux migration tools and patterns (such as rsync, tar, SCP, or Azure Migrate's Linux capabilities) where appropriate.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/tutorial-app-containerization-azure-pipeline.md
...igrate/tutorial-app-containerization-azure-pipeline.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by referencing only Windows file paths (e.g., C:\ProgramData\...), using Windows-specific navigation instructions (File Explorer, 'Hidden items'), and omitting equivalent instructions for Linux environments. The artifact location and navigation steps are exclusively described for Windows, with no mention of Linux file paths or terminal commands. This may confuse or exclude users running the App Containerization tool on Linux servers or workstations.
Recommendations
- Provide parallel instructions for locating artifacts on Linux systems, including typical Linux file paths (e.g., /var/lib/...) and relevant shell commands (ls, cd, etc.).
- When describing navigation steps, include both Windows (File Explorer) and Linux (terminal) methods.
- Explicitly state whether the Azure Migrate App Containerization tool is supported only on Windows, or clarify Linux support status.
- Ensure that all example commands, paths, and screenshots are provided for both Windows and Linux environments where applicable.
- In the prerequisites and artifact upload sections, mention Linux equivalents for file selection and upload processes (e.g., using the terminal, SCP, or Linux GUI file managers).