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 601-625 of 918 flagged pages
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/common-questions-discovery-dependency-analysis.md
...rate/common-questions-discovery-dependency-analysis.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by referencing Windows tools and patterns first or exclusively in several places. Agent installation and automation examples mention PowerShell scripts and Microsoft Configuration Manager, with no explicit Linux command-line or automation examples. The Microsoft Monitoring Agent (MMA) is linked primarily to its Windows documentation, and Linux support is only mentioned as a secondary note. There are no Linux-specific examples or guidance for agent installation, automation, or troubleshooting.
Recommendations
- Provide explicit Linux command-line examples for agent installation and automation (e.g., bash scripts, systemd service setup).
- Mention Linux tools (such as Ansible, shell scripts, or native package managers) alongside Windows tools like PowerShell and Configuration Manager.
- Ensure that links to agent documentation include both Windows and Linux installation guides, and present them in parallel.
- Include troubleshooting steps and prerequisites for Linux environments, not just Windows.
- Balance the order of presentation so that Linux and Windows are treated equally, rather than listing Windows first or exclusively.
Create Pull Request
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/migrate-hyper-v-servers-to-azure-using-private-link.md
...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 First
Missing Linux Example
Windows Tools
Summary
The documentation is heavily focused on migrating Hyper-V (a Windows-centric virtualization platform) VMs to Azure, with all examples, instructions, and tooling references specific to Windows environments. There are no Linux or cross-platform examples, and all operational steps assume the use of Windows tools and patterns (e.g., Hyper-V Replication provider, Recovery Services agent, Windows Server licensing). Linux environments, tools, or migration scenarios are not mentioned or addressed.
Recommendations
- Include parallel documentation or references for migrating Linux-based virtual machines (e.g., KVM, Xen, or other hypervisors) to Azure using Private Link.
- Provide examples and instructions for agent installation, DNS configuration, and network validation on Linux systems.
- Mention and link to equivalent migration guides for VMware and Linux-based hypervisors, if available.
- Clarify in the introduction that this guide is specific to Hyper-V/Windows environments and direct users to Linux/VMware migration documentation as appropriate.
- Where possible, use cross-platform terminology and highlight any steps that are Windows-specific, offering Linux alternatives or noting limitations.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/common-questions-server-migration.md
.../articles/migrate/common-questions-server-migration.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. While it covers both Windows and Linux migration scenarios in general descriptions and OS support tables, practical examples and tooling guidance are almost exclusively Windows-centric. Powershell and Windows-specific tools are used for bandwidth throttling, with no Linux equivalents provided. Windows migration scenarios, features, and upgrades are often discussed first or in more detail, and some advanced features (like in-place OS upgrade during migration) are only available for Windows, with Linux explicitly excluded. There are no Linux command-line or tooling examples for common administrative tasks, and Linux users are left to infer or research their own solutions.
Recommendations
- Provide Linux-equivalent examples for operational tasks, such as bandwidth throttling (e.g., using tc, wondershaper, or firewalld on Linux appliances).
- When showing Powershell or Windows command-line examples, include a corresponding Linux shell (bash) example if the appliance can run on Linux, or clarify if only Windows is supported.
- Balance the order of presentation: alternate or parallelize Windows and Linux examples and feature descriptions, rather than listing Windows first or exclusively.
- Document any limitations or differences for Linux-based appliances or migrations, and provide links to Linux-specific guidance where available.
- If certain features (such as in-place OS upgrade during migration) are Windows-only, explicitly state this and provide a roadmap or workaround for Linux users.
- Add troubleshooting and operational guidance for common Linux distributions in parity with Windows.
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, while highlighting improved Linux support, demonstrates Windows bias by mandating the use of Windows Server 2019 as the replication appliance and not mentioning any Linux-based alternatives. There are no Linux-specific examples or guidance for Linux administrators, and Windows tooling is presented as the default and only option.
Recommendations
- Provide information on whether a Linux-based replication appliance is supported or planned, or clarify why only Windows Server is used.
- Include step-by-step examples or guidance for Linux administrators, especially for common migration scenarios.
- Mention any Linux-native tools or scripts that can be used in conjunction with the migration stack, or explicitly state if none are available.
- Ensure parity in documentation structure by presenting Linux and Windows options side by side where applicable.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/concepts-assessment-calculation.md
...in/articles/migrate/concepts-assessment-calculation.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Heavy
Missing Linux Example
Summary
The documentation demonstrates a Windows-first and Windows-heavy bias. Windows operating systems are listed in detail and always before Linux, with extensive version-specific guidance and support notes. Linux is mentioned only generically, with a single reference to a link for supported distributions and no detailed breakdown or examples. There are no Linux-specific examples, troubleshooting, or migration caveats, and the documentation does not provide parity in OS-level detail or guidance for Linux environments.
Recommendations
- Provide a detailed table of supported Linux distributions and versions, similar to the Windows OS table, including migration caveats and support notes.
- Include Linux-specific examples, such as how to collect kernel version information, common migration issues, or best practices for Linux VMs.
- List Linux operating systems before or alongside Windows in all tables and lists to avoid the perception of Windows primacy.
- Add troubleshooting guidance for Linux VMs, such as handling unsupported distributions, kernel modules, or disk/boot compatibility.
- Ensure all instructions and recommendations (e.g., for security readiness, disk sizing, and network configuration) explicitly address both Windows and Linux scenarios.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/concepts-azure-sql-assessment-calculation.md
...s/migrate/concepts-azure-sql-assessment-calculation.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 technologies (e.g., IIS, Windows Server Failover Clusters, Windows-specific best practices links) and omitting Linux-specific examples or guidance. References to high availability, disaster recovery, and migration scenarios are framed around Windows tools and patterns, with no mention of Linux-based SQL Server deployments or their migration nuances. Where links to best practices are provided, they point to Windows-specific documentation. There are no Linux or cross-platform PowerShell/Bash/CLI examples, and the documentation assumes a Windows-centric environment throughout.
Recommendations
- Add explicit guidance and examples for assessing and migrating SQL Server instances running on Linux (including supported distributions).
- Include links to best practices for SQL Server on Linux in Azure, not just Windows.
- When discussing high availability and disaster recovery, mention Linux-based clustering and failover options (e.g., Pacemaker, Linux witness options) alongside Windows Server Failover Clusters.
- Provide parity in migration steps, screenshots, and configuration options for both Windows and Linux SQL Server sources.
- Where PowerShell or Windows-specific tools are referenced, also provide equivalent Bash/CLI/Linux-native commands and workflows.
- Clarify in each section whether the guidance applies to both Windows and Linux SQL Server deployments, or specify differences as needed.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/migrate-replication-appliance.md
...main/articles/migrate/migrate-replication-appliance.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation for the Azure Migrate replication appliance demonstrates a strong Windows bias. The appliance is described as running exclusively on Windows Server (2016 or 2012 R2), with no mention of Linux support or examples. All instructions, requirements, and file paths (e.g., C:\Temp\ASRSetup) are Windows-specific. Windows tools and settings (such as Group Policies, IIS, .NET Framework, and Windows Server roles) are referenced exclusively, and there are no Linux equivalents or guidance for Linux-based deployments. MySQL installation instructions are tailored to Windows (MSI installer, Windows file paths).
Recommendations
- Explicitly state whether Linux-based replication appliances are supported or not. If not, clarify this early in the documentation.
- If Linux support is available or planned, provide equivalent instructions, requirements, and examples for Linux deployments (e.g., supported distributions, package installation commands, file paths, service management).
- For MySQL installation, include Linux installation steps (e.g., using apt, yum, or other package managers) and Linux file paths.
- Reference Linux equivalents for configuration (e.g., SELinux/AppArmor, systemd services, firewall configuration) where Windows-specific settings are discussed.
- Where only Windows is supported, provide a rationale for the lack of Linux support and suggest alternatives for Linux users if possible.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/concepts-azure-webapps-assessment-calculation.md
...grate/concepts-azure-webapps-assessment-calculation.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by focusing primarily on ASP.NET web apps running on IIS (a Windows technology), mentioning Windows-based SKUs (I1, P1v2, P1v3), and linking to Windows-specific App Service pricing. There are no explicit examples or guidance for Linux-based web apps (such as those running on Apache, Nginx, or Java on Linux), nor are Linux migration scenarios or tools discussed. The documentation implicitly assumes a Windows/IIS environment as the default for web app migration.
Recommendations
- Include explicit examples and guidance for migrating Linux-based web apps (e.g., Java apps on Tomcat/Apache/Nginx on Linux).
- Mention Linux App Service plans and provide links to Linux-specific App Service pricing and documentation.
- Clarify that Azure App Service supports both Windows and Linux, and provide parity in assessment steps and recommendations for both platforms.
- Add references to Linux migration tools or patterns where applicable, and ensure that Linux scenarios are not omitted.
- Avoid using Windows/IIS as the default or only example; present both Windows and Linux scenarios side by side where possible.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/concepts-business-case-calculation.md
...articles/migrate/concepts-business-case-calculation.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by focusing heavily on Windows Server, SQL Server, Hyper-V, and Microsoft management tools (e.g., System Center, Windows ESU). Linux is only briefly mentioned in passing (e.g., in license amortization and support), with no detailed examples, cost breakdowns, or migration scenarios specific to Linux workloads. There are no Linux-specific tools, patterns, or parity in the discussion of migration, management, or security. All detailed examples, cost models, and management scenarios are centered on Windows environments.
Recommendations
- Include explicit examples and cost breakdowns for Linux workloads, such as common Linux distributions and open-source database/application stacks.
- Discuss Linux-specific migration scenarios, including considerations for licensing, support, and open-source management tools.
- Mention and provide parity for Linux management and monitoring tools (e.g., integration with Azure Monitor for Linux, Linux patch management, open-source backup solutions).
- Clarify how the Azure Migrate appliance discovers and assesses Linux servers, and provide links to Linux-specific guidance.
- Ensure that Linux is referenced alongside Windows in all relevant tables, cost models, and migration strategies, not just as an afterthought.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/concepts-migration-planning.md
...b/main/articles/migrate/concepts-migration-planning.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by specifically highlighting Windows Server scenarios (such as end-of-support and OS upgrade), mentioning Windows-specific tools and features (like the Custom Script Extension for Windows), and omitting equivalent Linux migration or upgrade workflows. There are no Linux-specific examples, recommendations, or parity in migration/upgrade tooling discussed, despite mentioning Linux in passing (e.g., Azure Hybrid Benefit for Linux subscriptions).
Recommendations
- Include explicit Linux migration scenarios, such as guidance for migrating Linux VMs, handling end-of-support Linux distributions, and any Azure Migrate features specific to Linux.
- Provide examples or references for Linux OS upgrades during migration, or clarify if such functionality is not available.
- When discussing tools like the Custom Script Extension, mention both Windows and Linux variants (e.g., link to both Windows and Linux documentation for custom scripts).
- Balance references to Windows and Linux in tables and examples (e.g., when filtering for end-of-support OS, include major Linux distributions that are EOL).
- Add Linux-specific troubleshooting, best practices, and links to relevant Azure Migrate documentation for Linux workloads.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/concepts-migration-webapps.md
...ob/main/articles/migrate/concepts-migration-webapps.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation is heavily focused on Windows environments, specifically requiring Windows Server, IIS, and PowerShell for web app migration. Linux servers are explicitly not supported, and there are no examples or guidance for Linux-based web apps or tools. All migration requirements and instructions are tailored to Windows-only scenarios.
Recommendations
- Add support and documentation for migrating Linux-based web apps to Azure App Service, if technically feasible.
- Include equivalent Linux migration tools and workflows (e.g., Bash scripts, Linux web servers like Apache/Nginx) alongside Windows/PowerShell examples.
- Clearly state future plans or alternatives for Linux users if support is not currently available.
- Provide parity in documentation structure and detail for both Windows and Linux scenarios to ensure inclusivity.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/migrate-services-overview.md
...lob/main/articles/migrate/migrate-services-overview.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a Windows bias by prioritizing Windows-centric workloads (e.g., Hyper-V, Windows-hosted web apps), mentioning Windows tools and environments (such as ASP.NET and SQL Server) without equivalent Linux examples, and omitting explicit guidance or examples for Linux servers, databases, or web applications. Linux migration scenarios and tools are not addressed, and the only web app migration example is for 'Web apps hosted on Windows in a VMware environment.'
Recommendations
- Add explicit examples and guidance for migrating Linux-based servers (e.g., Ubuntu, CentOS) and workloads, including discovery, assessment, and migration steps.
- Include Linux database migration scenarios (e.g., MySQL, PostgreSQL) and reference relevant tools or Azure services.
- Provide examples for migrating Linux-hosted web applications (e.g., Apache, Nginx, Node.js, Python) to Azure App Service or Azure Kubernetes Service.
- Ensure that tables and feature lists mention both Windows and Linux workloads where applicable, and avoid language that implies Windows is the default or only supported platform.
- Reference Linux-compatible tools and scripts, and provide parity in documentation for both Windows and Linux environments.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/migrate-support-matrix-hyper-v-migration.md
...es/migrate/migrate-support-matrix-hyper-v-migration.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by prioritizing Windows Server and related tools in requirements and examples. Windows-specific tools and patterns (e.g., Windows Firewall, RDP, .NET Framework) are mentioned explicitly and in detail, while Linux equivalents are either missing, less detailed, or only referenced generically. Instructions for post-migration connectivity are more comprehensive for Windows (with step-by-step firewall and RDP guidance), whereas Linux instructions are briefer and lack equivalent detail (e.g., no mention of SELinux, UFW/iptables, or SSH hardening). The documentation also lists Windows URLs and services (e.g., time.windows.com) before Linux-relevant alternatives, and does not provide Linux-specific troubleshooting or preparation steps.
Recommendations
- Provide Linux-specific examples and instructions alongside Windows ones, such as how to configure SSH, firewall (e.g., UFW, firewalld, iptables), and SELinux/AppArmor settings for migration.
- List Linux and Windows requirements in parallel, rather than always listing Windows first.
- Include Linux-specific troubleshooting steps and preparation guidance, similar to the detailed steps given for Windows (e.g., integration services, SAN policy).
- Reference Linux time synchronization sources (e.g., ntp.ubuntu.com, pool.ntp.org) in addition to or instead of time.windows.com.
- Where Windows tools or patterns are mentioned (e.g., .NET Framework, Windows Firewall), provide Linux equivalents or clarify when they are not required for Linux hosts.
- Ensure that all examples, especially for connectivity and post-migration steps, are equally detailed for both Windows and Linux VMs.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/migrate-support-matrix-hyper-v.md
...ain/articles/migrate/migrate-support-matrix-hyper-v.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page exhibits a strong Windows bias, as expected for Hyper-V scenarios, but with several areas where Linux parity is lacking or Linux is treated as an afterthought. Windows tools and patterns (e.g., PowerShell remoting, WinRM, WMI) are mentioned first and in detail, with Linux alternatives (SSH, Linux commands) often appearing later or with less detail. SQL Server and web app discovery are either unsupported or only partially supported for Linux. Example scripts and detailed instructions are provided only for Windows authentication and SQL Server, with no equivalent Linux database or web server examples. Some features (e.g., SQL Server instance discovery, ASP.NET web apps) are not supported for Linux at all.
Recommendations
- Where possible, provide Linux-first or at least Linux-equal examples and instructions, especially for discovery, permissions, and connectivity (e.g., sample SSH configuration, Linux user setup).
- Explicitly state limitations for Linux support up front and provide guidance or workarounds if available.
- For SQL Server and web app discovery, clarify Linux support status and, if unsupported, suggest alternative approaches or roadmap.
- Include Linux command-line examples and configuration steps alongside PowerShell/Windows instructions (e.g., for enabling required ports, setting up user permissions).
- Ensure that all tables and requirement lists mention Linux and Windows in parallel, not just as an afterthought.
- If a feature is Windows-only, explain why and provide links to relevant Linux migration/assessment tools if possible.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/concepts-vmware-agentless-migration.md
...rticles/migrate/concepts-vmware-agentless-migration.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page exhibits a Windows bias in several areas. PowerShell cmdlets (e.g., New-NetQosPolicy) are used exclusively for bandwidth throttling examples, and the configuration file paths (e.g., C:\ProgramData\Microsoft Azure\Config) are Windows-specific. There are no Linux or cross-platform equivalents provided for these operations, and the documentation assumes the Azure Migrate appliance is running on Windows without mentioning Linux deployment or management options. This may hinder Linux users or those deploying the appliance on non-Windows platforms.
Recommendations
- Provide equivalent Linux-based examples for bandwidth throttling, such as using 'tc' or 'iptables' for traffic shaping.
- Document the location and format of configuration files on Linux-based appliances, if supported (e.g., /var/lib/ or /etc/ paths).
- Clarify whether the Azure Migrate appliance can be deployed on Linux, and if so, provide Linux-specific instructions for management tasks (e.g., restarting services, editing config files).
- Where PowerShell or Windows tools are mentioned, add parallel Linux shell commands or scripts.
- Adopt more neutral language that does not assume a Windows environment by default, and explicitly call out platform-specific steps.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/migrate-support-matrix-physical-migration.md
...s/migrate/migrate-support-matrix-physical-migration.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by presenting Windows-specific tools, requirements, and connection instructions before or in more detail than their Linux equivalents. Windows terminology (such as BitLocker, Windows Firewall, RDP) is used extensively, and Linux instructions are less detailed or appear after Windows instructions. There is also a lack of parity in troubleshooting and configuration guidance for Linux systems.
Recommendations
- Provide Linux connection instructions with equal detail and prominence as Windows (e.g., include firewall configuration commands for common Linux distributions, not just a generic SSH mention).
- When listing requirements or steps, alternate the order or present Windows and Linux instructions side-by-side to avoid always listing Windows first.
- Include examples for both Windows and Linux for tasks like enabling remote access, configuring firewalls, and preparing disks.
- Mention Linux-specific tools and scenarios (e.g., SELinux, iptables, firewalld, LUKS encryption) where Windows-specific tools (like BitLocker or Windows Firewall) are referenced.
- Expand on Linux filesystem and bootloader support, and provide troubleshooting steps for common Linux migration issues.
- Ensure parity in post-migration steps for both Windows and Linux, such as guidance for fixing boot issues, network configuration, and user access.
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
Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. PowerShell and Windows-centric tools are referenced for appliance deployment and replication configuration, with no equivalent Linux CLI or automation examples. Windows requirements and instructions are often listed before Linux, and some sections (such as appliance OS requirements) assume or require Windows Server. There is a lack of Linux-native deployment or management options, and Linux guidance is less detailed or appears as an afterthought.
Recommendations
- Provide Linux CLI (e.g., Bash, shell script) examples for deploying and managing the Azure Migrate appliance, alongside or before PowerShell examples.
- Offer guidance for deploying the appliance from Linux workstations or automation pipelines, not just from Windows/PowerShell environments.
- Where possible, support and document Linux-based appliances or provide instructions for running the appliance on Linux VMs.
- Ensure that Linux requirements and instructions are presented with equal prominence and detail as Windows, and avoid always listing Windows first.
- Include troubleshooting and preparation steps for Linux VMs that are as comprehensive as those for Windows (e.g., firewall, SSH, agent installation).
- Clarify any limitations or differences for Linux users up front, and provide workarounds or alternatives where Windows-only tooling is referenced.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/migrate-support-matrix-vmware.md
...main/articles/migrate/migrate-support-matrix-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 areas: Windows tools and technologies (PowerShell, WMI, WinRM) are mentioned more prominently and with more detail than their Linux equivalents. Windows requirements and examples (such as SQL Server discovery and authentication) are provided in depth, while Linux support is often limited, less detailed, or explicitly not supported (e.g., SQL Server discovery on Linux). Where both platforms are supported, Windows is usually listed first and with more comprehensive instructions. There are also missing Linux-specific examples, particularly for tasks like SQL Server discovery and web app discovery.
Recommendations
- Provide equivalent Linux-focused examples and instructions wherever Windows examples are given, especially for authentication, credential setup, and agent installation.
- When listing supported operating systems or requirements, alternate the order or group Windows and Linux together to avoid always listing Windows first.
- Expand documentation for Linux-specific tools and patterns (e.g., Bash, SSH, Linux package requirements) to match the detail given for Windows (e.g., PowerShell, WMI).
- Where a feature is not supported on Linux (e.g., SQL Server discovery), clearly state the limitation and, if possible, provide workarounds or roadmap information.
- Include Linux-specific troubleshooting, configuration, and permission guidance (e.g., sudoers configuration, SELinux/AppArmor considerations, systemd service requirements) alongside Windows guidance.
- For web app discovery, provide parity in instructions and examples for Linux-based stacks (e.g., Apache, Nginx, Tomcat) similar to the detail for IIS/ASP.NET on Windows.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/onboard-to-azure-arc-with-azure-migrate.md
...les/migrate/onboard-to-azure-arc-with-azure-migrate.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 consistently mentioning Windows tools (WinRM, PowerShell) before Linux equivalents, providing detailed Windows-specific instructions (such as running 'winrm qc'), and referencing Windows authentication and permissions patterns. Linux instructions are present but less detailed, and Linux-specific tooling or command examples are largely absent. There are also references to using PowerShell for Azure tasks without equivalent Linux/CLI alternatives.
Recommendations
- Provide Linux/Unix command examples (e.g., SSH configuration, firewall rules) with equal detail and prominence as Windows examples.
- When referencing Azure service principal creation, include Azure CLI and Bash examples alongside PowerShell and portal instructions.
- Avoid always listing Windows steps first; alternate or present both OS instructions in parallel where possible.
- Clarify Linux authentication and permissions requirements with concrete examples (e.g., sudo usage, SSH key setup).
- Include troubleshooting steps and error messages specific to Linux environments, not just Windows/WinRM.
- Mention and link to Linux-specific documentation or tools where relevant, ensuring parity in guidance.
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 server preparation steps and examples before Linux, providing detailed PowerShell and Windows command-line instructions (with screenshots), and referencing Windows-specific tools (e.g., diskpart, registry, PowerShell) without equivalent Linux command-line examples or screenshots. Linux instructions are less detailed, with fewer concrete command examples and no screenshots, and some steps refer users to external documentation for specifics.
Recommendations
- Alternate the order of Windows and Linux sections or present both in parallel to avoid a Windows-first impression.
- Provide Linux command-line examples and screenshots for key steps (e.g., checking/setting DHCP, verifying agent installation), similar to the detailed Windows examples.
- Include Linux-specific troubleshooting tips and manual validation steps, not just references to external documentation.
- Where Windows tools (e.g., diskpart, PowerShell) are shown, provide direct Linux equivalents (e.g., nmcli, systemctl, ip, etc.) with commands and output.
- Ensure that all steps described for Windows (such as verifying agent installation, checking service status, or modifying boot/network settings) have clear, actionable Linux equivalents.
- Add a summary table comparing manual steps for Windows and Linux to highlight parity and differences.
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 by consistently presenting Windows-specific instructions, tools, and examples before their Linux equivalents. Windows tools (such as PowerShell, diskpart, and Windows Firewall) are mentioned explicitly, while Linux instructions are less detailed or lack equivalent command-line examples. The 'Prepare to connect after migration' section provides step-by-step instructions for Windows (including PowerShell usage) but offers only brief, high-level guidance for Linux. Additionally, the documentation provides more granular troubleshooting and configuration steps for Windows than for Linux.
Recommendations
- Provide Linux command-line examples (e.g., for enabling SSH, updating firewall rules with iptables/firewalld/ufw, checking required services, and verifying agent installation) alongside Windows examples.
- Present Windows and Linux instructions in parallel or in a more balanced order, rather than consistently listing Windows first.
- Include Linux-specific troubleshooting steps and configuration details (such as how to check for pending updates, or how to enable serial console access) similar to the Windows sections.
- Reference common Linux tools (e.g., systemctl, iptables, ufw, firewalld) where Windows tools like PowerShell or diskpart are mentioned.
- Expand the 'Prepare to connect with Linux Azure VMs' section with detailed steps and links, matching the depth provided for Windows.
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 (e.g., MAP Toolkit), mentioning Windows migration scenarios, and omitting Linux-specific examples or tools. Scripting skills are listed in a cross-platform way (Bash, PowerShell, Python), but concrete migration examples, tool references, and assessment tools are Windows-focused. There are no Linux-specific migration scenarios, tools, or examples provided.
Recommendations
- Include references to Linux migration tools or scenarios, such as guidance for migrating Linux servers or workloads.
- Mention Linux assessment and planning tools (e.g., Azure Migrate's support for Linux, or third-party Linux migration tools) alongside Windows tools like MAP Toolkit.
- Provide example migration workflows or FAQs specifically for Linux environments, including common challenges and solutions.
- Ensure that when listing skills, Linux administration and scripting (e.g., shell scripting, Linux networking) are explicitly mentioned.
- Balance tool and scenario descriptions so that Linux and Windows are treated with parity, or at least clarify cross-platform support where applicable.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/scale-hyper-v-assessment.md
...blob/main/articles/migrate/scale-hyper-v-assessment.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation is heavily focused on Hyper-V environments, which are exclusive to Windows. All examples, instructions, and tool references are centered around Hyper-V and Windows-based workflows, with no mention of Linux-based hypervisors (such as KVM or Xen), nor any Linux-specific instructions or parity guidance. The Azure Migrate appliance is only described as a Hyper-V VM, and there are no Linux or cross-platform alternatives or examples provided.
Recommendations
- Include parallel documentation or references for assessing Linux-based virtualization environments (e.g., KVM, Xen, VMware on Linux).
- Provide examples or links for deploying the Azure Migrate appliance on Linux-based hypervisors, if supported.
- Explicitly state if the described process is only applicable to Windows/Hyper-V, and provide guidance for Linux users or link to relevant Linux documentation.
- Add a comparison table or section outlining differences and supported features between Windows/Hyper-V and Linux-based environments in Azure Migrate.
- Ensure that future documentation includes Linux command-line examples or workflows where applicable, not just Windows/Hyper-V scenarios.
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 specifying that the Azure Migrate appliance must be deployed on a Windows server, with no mention of Linux support or alternatives. There are no Linux-specific instructions, examples, or considerations, and Windows is the only platform discussed for the on-premises appliance. This may give the impression that Linux environments are not supported or are an afterthought.
Recommendations
- Explicitly state whether the Azure Migrate appliance supports Linux hosts, and if not, clarify this limitation.
- If Linux support exists, provide parallel instructions for deploying the appliance on Linux servers, including prerequisites and setup steps.
- Include Linux-specific considerations or troubleshooting steps for heterogeneous environments.
- When mentioning deployment requirements, list both Windows and Linux options (if available), or clearly explain the rationale for Windows-only support.
- Add examples or references for assessing Linux physical servers, including any differences in process or requirements.
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 exhibits 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 examples. There are no Linux/Unix-specific instructions, tools, or file paths, and all operational guidance assumes a Windows environment.
Recommendations
- Include equivalent instructions and file paths for Linux-based Azure Migrate appliances, if supported (e.g., /home/public/Desktop/DiagnosticsReport or similar).
- Clarify whether the Azure Migrate appliance is only supported on Windows, or provide parity documentation for Linux deployments if available.
- Mention Linux-specific considerations for time sync, file permissions, and agent/service management.
- Provide screenshots or command-line examples for Linux environments (e.g., using systemctl, journalctl, or Linux file explorers).
- Explicitly state OS requirements and supported platforms at the beginning of the documentation.