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 651-675 of 918 flagged pages
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/tutorial-discover-vmware.md
...blob/main/articles/migrate/tutorial-discover-vmware.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows bias in several areas: it provides explicit PowerShell-based setup instructions for the Azure Migrate appliance only for Windows Server (with no equivalent Linux-based script or VM option), references Windows tools (e.g., PowerShell, Windows authentication, IIS) more frequently and in greater detail than their Linux counterparts, and often lists Windows procedures or requirements before Linux ones. While Linux is mentioned as supported, practical Linux setup examples and parity in tooling are lacking.
Recommendations
- Provide a Linux-based script or VM option for setting up the Azure Migrate appliance, or clarify if only OVA import is supported for Linux environments.
- Include explicit Linux command-line examples (e.g., using SSH, scp, or Linux-native automation) for appliance setup and configuration, not just PowerShell/Windows.
- Balance the order of presentation: when listing supported OSes, tools, or procedures, alternate or group Windows and Linux equally, rather than defaulting to Windows-first.
- Offer detailed Linux authentication and troubleshooting guidance, similar to the depth provided for Windows (e.g., for SSH key setup, permissions, and validation).
- When referencing tools like VMware VDDK, clarify installation paths and procedures for both Windows and Linux hosts.
- Expand documentation on discovering and assessing Linux-specific workloads (e.g., Apache, Nginx, PostgreSQL) to match the detail given for Windows workloads (IIS, SQL Server).
Create Pull Request
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/tutorial-migrate-aws-virtual-machines.md
...icles/migrate/tutorial-migrate-aws-virtual-machines.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows bias in several areas: Windows-specific tools and requirements are mentioned first or exclusively (e.g., the replication appliance must run on Windows Server 2012 R2/2016), and some steps and troubleshooting sections focus on Windows management services or activation issues. While Linux instructions are present, they are sometimes less detailed or appear after Windows instructions. There is no mention of using a Linux-based replication appliance, and some examples (e.g., screenshots, troubleshooting) are Windows-centric.
Recommendations
- Provide parity by offering Linux-based options for the replication appliance, if supported, or clearly state if only Windows is supported and why.
- When listing steps for both Windows and Linux, alternate the order or present them in parallel to avoid always putting Windows first.
- Expand Linux-specific troubleshooting and post-migration guidance to match the detail given for Windows (e.g., mention common Linux boot or driver issues, not just Windows activation).
- Include Linux-specific screenshots or examples where appropriate, not just Windows-centric visuals.
- If certain features or tools are Windows-only, explicitly note the lack of Linux support and suggest workarounds or alternatives for Linux users.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/tutorial-migrate-gcp-virtual-machines.md
...icles/migrate/tutorial-migrate-gcp-virtual-machines.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows bias in several areas. The replication appliance required for migration must be a Windows Server (2012 R2 or 2016) VM, with no mention of a Linux-based alternative. In step-by-step instructions, Windows prerequisites and ports (WinRM) are listed before Linux, and some troubleshooting steps reference Windows management services. While Linux VM migration is supported and some Linux-specific instructions are present, the overall workflow and tooling are centered around Windows environments, and there is no parity in appliance OS support or in-depth Linux automation examples.
Recommendations
- Provide a Linux-based replication appliance option, or clearly state if only Windows is supported and explain the rationale.
- When listing prerequisites or configuration steps, present Linux and Windows instructions in parallel or in separate, equally detailed sections.
- Include Linux-specific troubleshooting steps and examples, not just Windows-centric ones (e.g., errors related to SSH, systemd, or Linux firewalls).
- Offer automation examples for Linux environments (e.g., using shell scripts or Ansible) for agent installation and configuration, similar to Windows examples.
- Avoid assuming Windows as the default environment for appliance deployment or management tasks; clarify OS requirements early and provide alternatives where possible.
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 exhibits a Windows-first bias in several areas. Windows Server is consistently referenced as the default or primary environment for the replication appliance, with explicit instructions to copy files to a Windows Server 2016 machine. PowerShell is the only command-line automation method detailed for appliance setup, with no Bash or Linux-native alternatives. Registry and Group Policy checks are described exclusively for Windows, and troubleshooting/upgrade notes focus on Windows tools (e.g., SetupDiag). While Linux is mentioned as a supported OS and some Linux agent installation steps are provided, Linux-specific guidance is less detailed, and Linux automation or appliance deployment methods are not covered. There are also more links and troubleshooting steps for Windows than for Linux.
Recommendations
- Provide parallel Linux-based instructions for deploying the replication appliance, including supported Linux distributions and setup steps (e.g., using a Linux VM or container as the appliance host).
- Include Bash or shell script examples for automation alongside PowerShell, especially for agent installation and appliance setup.
- Document Linux-specific prerequisites and troubleshooting steps (e.g., SELinux, firewall, systemd services) in parity with Windows registry and Group Policy checks.
- Ensure that all references to Windows tools (e.g., SetupDiag, registry keys) are matched with Linux equivalents or clearly marked as Windows-only, with Linux alternatives provided where possible.
- Balance the order of presentation so that Linux and Windows instructions/examples are given equal prominence, or clearly separate them into OS-specific sections.
- Expand the Linux agent installation section to include automation options (e.g., Ansible, shell scripts) and troubleshooting tips.
- Add more Linux-focused post-migration best practices and links, such as integration with Azure Update Manager for Linux, and guidance for securing and monitoring Linux VMs.
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: Windows-specific instructions and tools (e.g., registry edits, Windows Server 2016 appliance, Azure VM agent auto-installation on Windows but not Linux) are presented first or exclusively, while Linux instructions are minimal or secondary. PowerShell/Windows-centric patterns are assumed (e.g., VMware PowerCLI, registry changes), and Linux alternatives or detailed examples are often missing or less emphasized.
Recommendations
- Provide parallel, detailed Linux instructions and examples wherever Windows-specific steps are given (e.g., registry edits for Windows, provide equivalent Linux configuration steps).
- When describing the setup of the replication appliance, clarify if a Linux-based appliance is supported or provide guidance for Linux-based environments.
- For agent installation, include explicit Linux command-line examples (e.g., using SSH and package managers) alongside Windows instructions.
- When referencing tools like PowerCLI or Windows Server, mention Linux-compatible alternatives or clarify cross-platform support.
- In post-migration steps, give equal detail for Linux (e.g., how to install the Azure VM agent on Linux, how to remove Linux-specific tools).
- Avoid always listing Windows steps or tools first; alternate or group by OS to show parity.
- Ensure all troubleshooting and best practices sections include Linux-specific guidance, not just Windows.
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
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation is heavily oriented toward Windows environments, specifically Hyper-V on Windows Server. All command-line examples use Windows paths, executables, and conventions (e.g., .exe files, %Programdata% variables, C:\ paths). There are no Linux equivalents or cross-platform instructions for any step, and the only OS-specific troubleshooting or upgrade guidance is for Windows. The documentation assumes the use of Windows-native tools and does not mention or provide parity for Linux-based Hyper-V hosts or management via Linux shells.
Recommendations
- Explicitly state that the documented process is only supported on Windows-based Hyper-V hosts, or clarify if Linux-based Hyper-V management is unsupported.
- If any steps can be performed from a Linux environment (e.g., using Azure CLI, REST API, or PowerShell Core on Linux), provide equivalent Linux/bash examples.
- Where possible, use cross-platform tools (such as Azure CLI) for steps like registration, monitoring, or automation, and provide corresponding examples.
- Add a section addressing migration of Linux VMs running on Hyper-V, including any special considerations or differences in the process.
- Ensure that post-migration steps and best practices include Linux-specific guidance (e.g., troubleshooting, activation, security, and update management for Linux VMs).
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
Windows Tools
Powershell Heavy
Summary
The documentation demonstrates a Windows bias by prioritizing Windows-specific tools, upgrade paths, and troubleshooting steps. Windows OS upgrade options and tools (e.g., SetupDiag, Windows Server upgrade) are mentioned explicitly, while equivalent Linux migration, upgrade, or troubleshooting guidance is absent. The only script-based appliance setup method references PowerShell, with no mention of Bash or Linux-native alternatives. Linux is only briefly mentioned in passing, with no concrete examples or instructions.
Recommendations
- Provide parallel Linux-specific instructions and examples wherever Windows-specific steps are detailed (e.g., OS upgrades, troubleshooting).
- Include Linux migration/upgrade best practices, such as guidance for common distributions (Ubuntu, RHEL, etc.), and reference tools like cloud-init or distribution-specific upgrade methods.
- When referencing script-based setup, clarify if the PowerShell installer script is compatible with Linux (e.g., via PowerShell Core), or provide a Bash/shell script alternative.
- Add troubleshooting steps and post-migration checks for Linux VMs, similar to the Windows activation troubleshooting section.
- Ensure screenshots and UI references are OS-neutral or provide both Windows and Linux perspectives where relevant.
- Explicitly state any differences or limitations for Linux VMs in agentless migration scenarios.
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 Windows bias in several ways. Windows-specific tools (PowerShell, Windows Server, IIS, SCOM) are frequently mentioned, often without Linux equivalents or with Windows examples appearing first. PowerShell is referenced as the primary automation/scripting tool, and Windows-centric migration scenarios (e.g., ASP.NET on IIS, Windows OS upgrades) are highlighted more prominently than Linux scenarios. Linux support is mentioned, but often as an afterthought or in less detail, and Linux-specific tooling or automation examples are largely absent.
Recommendations
- Provide Linux-specific examples alongside Windows examples, especially for automation (e.g., Bash scripts, Ansible, or shell commands for appliance setup and migration tasks).
- Mention Linux tools and workflows (e.g., systemd, SSH, Linux package managers) where relevant, not just PowerShell or Windows tools.
- Ensure Linux migration scenarios (e.g., Apache, NGINX, Tomcat, Java apps) are given equal prominence and detail as Windows/IIS/ASP.NET scenarios.
- When referencing automation or scripting, include both PowerShell and Bash (or other Linux scripting) examples.
- Highlight Linux-specific features or challenges (such as SELinux, sudo/root access, package dependencies) in migration guidance.
- Avoid always listing Windows/PowerShell options first; alternate the order or present both together.
- Add troubleshooting and best practices sections for Linux migrations, not just for Windows environments.
Migrate
Azure SQL assessments in Azure Migrate Discovery and assessment tool
...s/migrate/concepts-azure-sql-assessment-calculation.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation for Azure SQL assessments in Azure Migrate Discovery and assessment tool displays a moderate Windows bias. While the tool itself is cross-platform and supports assessment of SQL Server instances from VMware, Hyper-V, and physical environments (which can include Linux), the documentation repeatedly references Windows-specific patterns, tools, and best practices. Examples and links for SQL Server on Azure VM sizing and migration consistently point to Windows-focused resources, such as Windows Server Failover Clusters and PowerShell-based configuration. There is little to no mention of Linux-based SQL Server deployments, nor guidance for Linux-specific migration scenarios, tools, or best practices. Linux SQL Server users may find it challenging to map the guidance to their environments.
Recommendations
- Add explicit examples and guidance for assessing and migrating SQL Server instances running on Linux (RHEL, Ubuntu, SUSE, etc.), including any differences in discovery, sizing, and migration steps.
- Include links to Linux-specific best practices for SQL Server on Azure VM (e.g., /azure/azure-sql/virtual-machines/linux/).
- Clarify which steps, recommendations, or features are Windows-only and which are applicable to Linux SQL Server deployments.
- Provide parity in documentation for high availability and disaster recovery scenarios on Linux (e.g., Pacemaker clusters, Linux witness options).
- Where PowerShell or Windows tools are referenced, offer equivalent Bash/CLI/Linux-native alternatives if available.
Migrate
Tutorial to assess SQL instances in VMware VMs for migration to SQL Server on Azure VM, Azure SQL Managed Instance and Azure SQL Database
...ob/main/articles/migrate/tutorial-assess-sql-vmware.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation is generally platform-neutral regarding the assessment of SQL Server instances in VMware VMs for migration to Azure SQL solutions. However, there are several subtle signs of Windows bias: references to Windows Server Failover Clusters and Cloud Witness (Windows-only), links to Windows-specific performance guidelines, and no mention of Linux SQL Server scenarios or Linux-specific migration considerations. Examples and screenshots do not clarify whether Linux-based SQL Server instances are supported or how their migration might differ.
Recommendations
- Explicitly state whether Linux-based SQL Server instances in VMware VMs are supported for assessment and migration.
- Provide examples or notes for Linux SQL Server instances, including any differences in assessment, migration, or Azure SQL configuration.
- Where Windows-specific features (e.g., Cloud Witness, Windows Server Failover Clusters) are mentioned, clarify alternatives or limitations for Linux environments.
- Add links to Linux SQL Server performance guidelines and best practices for running SQL Server on Linux in Azure VMs.
- Ensure screenshots and instructions are inclusive of both Windows and Linux SQL Server scenarios, or clearly state any platform limitations.
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation for 'Create an Azure SQL assessment' demonstrates a moderate Windows bias. Several sections reference Windows-specific tools and patterns, such as Windows Server Failover Clusters and Cloud Witness, without mentioning Linux equivalents or alternatives. Links and examples for performance guidelines and high availability reference Windows-focused documentation. There are no Linux-specific examples or guidance for scenarios like cluster quorum or disk witness configuration. The documentation assumes familiarity with Windows environments and does not provide parity for Linux-based SQL Server deployments.
Recommendations
- Add explicit guidance for Linux-based SQL Server deployments, including how to configure high availability and disaster recovery in Azure VMs running Linux.
- Include links to Linux-specific performance guidelines and best practices for SQL Server on Azure VMs.
- Provide examples or notes for configuring cluster quorum and witness options for Linux environments, such as using shared disk or file share witness.
- Clarify which features or recommendations are Windows-only and suggest Linux alternatives where applicable.
Migrate
Tutorial to assess SQL instances for migration to SQL Server on Azure VM, Azure SQL Managed Instance and Azure SQL Database
...docs/blob/main/articles/migrate/tutorial-assess-sql.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page generally describes the assessment process for migrating SQL Server instances to Azure SQL, which is relevant for both Windows and Linux SQL Server deployments. However, there is a notable bias towards Windows in the high availability and disaster recovery section, where only Windows Server Failover Clusters and related tooling (Cloud Witness, Shared Disk) are mentioned. The linked best practices for VM sizing also point to Windows-specific guidance. Linux equivalents (such as Pacemaker clusters or Linux witness options) are not referenced, and Windows patterns are described first and exclusively in relevant sections.
Recommendations
- Add guidance or references for high availability and disaster recovery for SQL Server on Linux, such as Pacemaker clusters or Linux-based witness options.
- Include links to performance best practices for SQL Server on Azure VMs running Linux, not just Windows.
- Clarify in relevant sections whether the described features and recommendations apply to both Windows and Linux SQL Server deployments, or specify any limitations.
- Where Windows-specific tooling is mentioned (e.g., Cloud Witness), provide Linux alternatives or note if none exist.
Migrate
Discover, assess, and migrate Amazon Web Services (AWS) EC2 VMs to Azure
...icles/migrate/tutorial-migrate-aws-virtual-machines.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation exhibits moderate Windows bias. The replication appliance required for migration must be hosted on Windows Server 2022, with no Linux alternative mentioned. Windows-specific instructions and screenshots are provided first and in more detail, while Linux steps (such as Mobility agent installation) are present but less emphasized. The appliance setup and management rely on Windows tools and patterns, and Linux users must adapt by using a Windows VM for the appliance, which may create friction.
Recommendations
- Clearly state early in the documentation that the replication appliance must run on Windows Server, and explain why no Linux alternative exists.
- Provide guidance for Linux-only environments, such as how to provision a temporary Windows Server VM for the appliance if needed.
- Where possible, offer parity in example commands, screenshots, and troubleshooting steps for both Windows and Linux VMs.
- Highlight any Linux-specific considerations or limitations (e.g., Amazon Linux migration restrictions) in a dedicated section.
- If future Azure Migrate releases support Linux-based appliances, update documentation to reflect this.
Migrate
Prepare machines for migration with Azure Migrate
...cs/blob/main/articles/migrate/prepare-for-migration.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page exhibits a moderate Windows bias. Windows-specific instructions, tools, and examples (such as diskpart, SAN policy, RDP, Windows Firewall, and PowerShell) are given in detail, often before or with more depth than Linux equivalents. Linux instructions are present but less detailed, and some steps for Linux (such as enabling SSH or configuring network interfaces) are described only briefly, without explicit command examples. Windows tools and patterns (like PowerShell and diskpart) are mentioned exclusively, while Linux command-line equivalents are omitted.
Recommendations
- Provide Linux command-line examples for key steps (e.g., updating fstab, enabling SSH, modifying firewall rules) similar to the detailed Windows instructions.
- Include Linux-specific troubleshooting steps and links, matching the depth given to Windows (e.g., how to check required services, how to verify agent installation).
- Present Windows and Linux instructions in parallel sections, or alternate which OS is described first, to avoid implicit prioritization.
- Reference Linux tools (e.g., iptables, systemctl, nmcli) where Windows tools (diskpart, PowerShell) are mentioned.
- Add explicit instructions for preparing Linux VMs for remote access, including example commands for common distributions.
Migrate
Redeploy servers to Azure using Infrastructure as Code
...ure-docs/blob/main/articles/migrate/server-redeploy.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page is written with a clear Windows-centric perspective, as evidenced by the customer intent, which focuses on Windows Server 2003 migration. While the introduction claims support for both Windows and Linux servers, all examples, scenarios, and instructions are generic and do not provide Linux-specific guidance, examples, or troubleshooting. There are no references to Linux tools, shell commands, or Linux migration nuances. Windows tools (e.g., Visual Studio Code) are mentioned, but not Linux equivalents.
Recommendations
- Add explicit Linux migration scenarios and examples, including any differences in assessment, code generation, and disk handling.
- Include Linux-specific instructions for using the disk migration script, such as shell commands and permissions.
- Mention Linux-friendly IDEs (e.g., Vim, Emacs, GNOME Builder) alongside Visual Studio Code.
- Clarify any differences in agent-based/agentless migration for Linux VMs.
- Provide troubleshooting tips for common Linux migration issues.
Migrate
Assess ASP.NET/Java web apps for migration to Azure Kubernetes Service
...ob/main/articles/migrate/tutorial-assess-aspnet-aks.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation displays a moderate Windows bias, especially in the ASP.NET assessment workflow. It references Windows-specific requirements (e.g., Windows node pools for ASP.NET apps) and optimization of Windows Dockerfiles, without offering equivalent guidance for Linux-based ASP.NET Core or Java apps. Linux tools, patterns, or examples are not mentioned, and the cost assessment for ASP.NET apps is Windows-centric. The order of presentation and screenshots also tend to prioritize Windows scenarios.
Recommendations
- Include explicit guidance and examples for Linux-based ASP.NET Core apps, which are commonly containerized and run on Linux nodes in AKS.
- Add Linux Dockerfile optimization links and best practices alongside Windows Dockerfile references.
- Clarify when Windows node pools are required (e.g., only for legacy ASP.NET Framework apps) and highlight that ASP.NET Core and Java apps can run on Linux node pools.
- Provide cost assessment examples for Linux node pools and compare with Windows node pool costs.
- Ensure screenshots and step-by-step instructions show parity between Windows and Linux scenarios.
Migrate
Enhancing Web App Assessment With Code Scan Reports for Azure Migration
...lob/main/articles/migrate/add-copilot-code-insights.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in several areas. References to installation and usage of AppCAT for Java projects consistently point to Windows-specific instructions (e.g., '/azure/migrate/appcat/appcat-7-quickstart?tabs=windows'), and there are no explicit Linux/macOS commands or examples for installing or running AppCAT. The .NET CLI example is platform-agnostic, but the Java guidance is Windows-centric. There are no screenshots or step-by-step instructions for Linux/macOS users, and troubleshooting does not mention platform-specific issues outside of Windows.
Recommendations
- Add explicit Linux/macOS instructions and examples for installing and running AppCAT CLI for both .NET and Java projects.
- Provide links to Linux/macOS tabs in referenced quickstarts (e.g., '/azure/migrate/appcat/appcat-7-quickstart?tabs=linux').
- Include screenshots or terminal examples from Linux/macOS environments.
- Mention any platform-specific considerations or troubleshooting steps for Linux/macOS users.
Migrate
Agent-based Migration in the Migration and Modernization Tool
...articles/migrate/agent-based-migration-architecture.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Powershell Heavy
Summary
The documentation demonstrates a notable Windows bias. It references Windows-specific paths (e.g., C:\Program Files), registry keys, and tools like the Azure Backup MMC snap-in, with no mention of Linux equivalents or instructions for Linux-based process servers or Mobility service installations. There are no Linux command examples or guidance for Linux environments, which may cause confusion or block Linux users.
Recommendations
- Include explicit instructions and examples for installing and managing the Mobility service on Linux servers, including relevant file paths and commands.
- Document how to configure bandwidth throttling and other settings on Linux-based process servers, or clarify if these features are Windows-only.
- Provide Linux-specific antivirus exclusion paths and guidance.
- If certain features (e.g., MMC snap-in, registry keys) are Windows-only, clearly state this and offer alternative methods for Linux.
- Ensure parity in examples and troubleshooting steps for both Windows and Linux environments.
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation exhibits moderate Windows bias. Windows examples and instructions (such as WMI Control steps, Windows authentication SQL scripts, and Windows user group assignments) are often presented first and in greater detail. Windows-specific tools and UI steps (e.g., Control Panel, WinRM, WMI) are described with screenshots and step-by-step instructions, while Linux equivalents are less detailed and sometimes missing (e.g., no Linux screenshot, less explanation of Linux permission configuration). SQL Server discovery is exclusively Windows-centric, with no mention of Linux-hosted SQL Server. MySQL instructions are more platform-neutral, but overall, Windows patterns dominate the documentation structure.
Recommendations
- Provide Linux instructions and examples with equal detail and clarity, including screenshots or terminal output where appropriate.
- Add Linux-first or side-by-side examples for credential setup, permissions, and troubleshooting.
- Include explicit steps for Linux-based SQL Server discovery and permissions if supported.
- Balance the order of presentation so Linux and Windows instructions are given equal prominence.
- Avoid assuming Windows as the default platform in examples and tool references.
Migrate
Questions about assessments in Azure Migrate
...icles/migrate/common-questions-discovery-assessment.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page for Azure Migrate assessments demonstrates a Windows bias by consistently referencing Windows-centric technologies (Hyper-V, IIS, SQL Server) and environments (VMware, Hyper-V, Physical/Bare metal) without providing explicit examples, guidance, or parity for Linux servers or workloads. There are no Linux-specific instructions, troubleshooting steps, or mentions of Linux migration scenarios, and Windows technologies (e.g., IIS, SQL Server) are referenced exclusively when discussing App Service and SQL assessments. The documentation also omits Linux tools, patterns, or considerations, and does not address common Linux migration blockers or readiness checks.
Recommendations
- Add explicit examples and guidance for Linux server discovery, assessment, and migration, including supported Linux distributions and versions.
- Include troubleshooting steps and readiness checks specific to Linux workloads (e.g., Apache, Nginx, MySQL, PostgreSQL).
- Mention Linux-specific migration blockers, compatibility checks, and assessment nuances.
- Provide parity in examples and instructions for both Windows and Linux environments, including command-line tools and agent installation steps.
- Clarify whether features and limitations apply equally to Linux servers, or highlight any differences.
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation for Azure Migrate Appliance FAQ demonstrates a notable Windows bias. Deployment and management instructions rely heavily on PowerShell scripts and Windows-specific tools (e.g., Windows certificate manager, group policy editor, Windows Update). Troubleshooting and update procedures exclusively reference Windows interfaces and workflows, with no Linux/macOS equivalents or guidance. Examples and screenshots are all Windows-centric, and Linux is only mentioned as a type of credential, not as a platform for appliance deployment or management.
Recommendations
- Provide equivalent instructions and examples for Linux-based deployments, including how to run installer scripts, manage certificates, and troubleshoot updates on Linux.
- Include Linux/macOS screenshots and command-line examples (e.g., using bash, OpenSSL, or Linux certificate stores) where applicable.
- Clarify whether the appliance can be deployed or managed on Linux hosts, and if not, explicitly state the platform requirements.
- Offer guidance for certificate management and MSI validation on Linux, or note cross-platform limitations.
- Reorder examples so that platform-neutral or Linux instructions are presented alongside or before Windows-specific ones.
Migrate
Common Questions About the Migration and Modernization Tool
.../articles/migrate/common-questions-server-migration.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. PowerShell and Windows-specific tools (NetQosPolicy, Windows Scheduled Tasks) are used exclusively in bandwidth throttling examples, with no Linux equivalents or alternatives provided. Windows OS upgrade is supported and documented, while Linux upgrade is explicitly noted as unsupported. Windows operating systems and scenarios are often listed first in tables and explanations. There are no Linux shell or tool examples for operational tasks, and Linux users are left to infer or research their own solutions for several steps.
Recommendations
- Provide Linux-specific examples for bandwidth throttling, such as using 'tc', 'iptables', or other Linux traffic control tools.
- Include Linux shell script equivalents for scheduled bandwidth changes, e.g., using 'cron' and shell scripts.
- Document Linux OS upgrade support roadmap or provide guidance for Linux upgrade scenarios.
- Alternate the order of Windows and Linux in tables and lists to avoid implicit prioritization.
- Explicitly mention Linux/macOS alternatives wherever Windows tools or PowerShell are referenced.
- Add troubleshooting and operational examples for Linux-based Azure Migrate appliances.
Migrate
Azure SQL assessments in Azure Migrate Discovery and assessment tool
...s/migrate/concepts-azure-sql-assessment-calculation.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page exhibits a moderate Windows bias. Windows-specific technologies (e.g., IIS, Windows Server Failover Clusters, Windows licensing) are referenced exclusively or before Linux equivalents. Several links and best practices are focused on Windows (e.g., performance guidelines for Windows VMs, cluster quorum configuration for Windows), and there are no explicit Linux migration examples or guidance. While Linux is mentioned in licensing contexts (RHEL/SLES), practical migration steps, sizing, and high availability guidance are Windows-centric.
Recommendations
- Add explicit examples and migration guidance for Linux-based SQL Server deployments (e.g., SQL Server on RHEL/SLES/Ubuntu).
- Include links to performance guidelines and best practices for SQL Server on Linux VMs in Azure.
- Provide parity in high availability and disaster recovery documentation for Linux clusters (e.g., Pacemaker, Linux witness options).
- Clarify any differences in assessment logic or supported features for Linux SQL Server instances.
- Ensure that references to cluster configuration, storage, and compute sizing include Linux scenarios.
Migrate
Questions about Wave Planning in Azure Migrate
...ain/articles/migrate/common-questions-wave-planning.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation mentions PowerShell and Azure CLI as options for exporting wave data, but lists PowerShell before CLI and does not provide any Linux/macOS-specific guidance or examples. There are no explicit Linux/macOS command examples, and Windows-centric tools (PowerShell, Power BI) are referenced without Linux alternatives.
Recommendations
- Provide explicit Linux/macOS command examples using Azure CLI and REST APIs.
- List Azure CLI before PowerShell when describing cross-platform options.
- Mention Linux-compatible reporting tools (e.g., jq, csvkit, or open-source BI tools) alongside Power BI.
- Clarify that Azure CLI and REST APIs work on Linux/macOS and provide sample commands.
Migrate
Azure VM assessments in Azure Migrate
...in/articles/migrate/concepts-assessment-calculation.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Heavy
Missing Linux Example
Summary
The documentation page exhibits a moderate Windows bias. Windows operating systems are listed first and in detail in readiness tables, with Linux and other OSes grouped together and referenced via external links. Examples and explanations focus on Windows versions, with Linux support mentioned but not elaborated. There are no Linux-specific examples, troubleshooting, or patterns, and the documentation does not provide parity in guidance for Linux users (e.g., how to collect kernel version information is only briefly mentioned).
Recommendations
- Provide Linux-specific examples and troubleshooting steps, especially for common scenarios such as kernel version discovery and readiness issues.
- List Linux distributions and readiness details in the same level of detail as Windows versions, rather than referencing an external link.
- Include guidance for Linux users on preparing their servers for migration, including best practices, common pitfalls, and supported tools.
- Ensure that examples and tables alternate or balance Windows and Linux content, rather than listing Windows first and in detail.
- Add explicit instructions for Linux environments in sections discussing appliance deployment, data collection, and assessment logic.