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 151-175 of 918 flagged pages
Migrate
Enable additional data collection for Arc-enabled servers
...w-to-enable-additional-data-collection-for-arc-servers.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Windows Naming Priority
Summary
The documentation provides parity between Windows and Linux in terms of instructions and examples for enabling additional data collection on Arc-enabled servers. However, there is a subtle Windows bias: Windows is consistently mentioned first in extension names, CLI examples, and policy definitions. The extension naming convention ('AzureMigrateCollectorForWindows' and 'AzureMigrateCollectorForLinux') and the order of presentation (Windows before Linux in several places) may reinforce a perception of Windows as the primary or default platform. Additionally, the endpoint URL uses 'migration.windowsazure.com', which is Windows-centric, though this is an Azure branding artifact rather than a technical limitation.
Recommendations
- Alternate the order of Windows and Linux instructions/examples to avoid implicit prioritization.
- Explicitly state that both Windows and Linux are fully supported and treated equally.
- Where possible, use neutral language (e.g., 'AzureMigrateCollector extension for Windows or Linux') rather than always listing Windows first.
- Consider providing a summary table at the top showing parity of features and steps for both platforms.
- If possible, clarify that the endpoint naming ('windowsazure.com') is historical and does not imply Windows-only support.
Create Pull Request
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias primarily through its use of PowerShell for command-line examples and instructions, such as installing and using the Azure CLI. All CLI instructions are given in the context of PowerShell, with no mention of Linux shells (bash, zsh) or macOS equivalents. There are no Linux-specific examples, nor are Linux tools or patterns referenced. The instructions and screenshots focus on the Azure portal, which is cross-platform, but command-line usage is presented exclusively from a Windows/PowerShell perspective.
Recommendations
- Provide CLI examples for both PowerShell (Windows) and bash (Linux/macOS), including syntax differences where relevant.
- Explicitly mention that Azure CLI can be used on Linux, macOS, and Windows, and link to installation instructions for all platforms.
- Include sample commands and screenshots from Linux terminals (e.g., Ubuntu bash) alongside PowerShell examples.
- Where file paths or environment specifics are referenced, clarify differences between Windows and Linux/macOS.
- Add notes or sections highlighting Linux-specific considerations for Azure Migrate projects, if any.
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in several ways. The Windows section is presented first and in greater detail, with step-by-step instructions, screenshots, and explicit PowerShell commands. Windows-specific tools (diskpart, PowerShell, Task Manager) are referenced and illustrated, while Linux instructions are less detailed, lack screenshots, and rely on generic or RedHat-centric examples. There are no Linux command-line screenshots, and manual steps for Linux are less explicit, with some instructions referring users to external documentation.
Recommendations
- Present Windows and Linux instructions in parallel, or alternate the order to avoid Windows-first bias.
- Add Linux command-line screenshots and explicit step-by-step instructions for manual preparation, similar to the Windows section.
- Provide examples for multiple Linux distributions (e.g., Ubuntu, SLES, Debian), not just RedHat.
- Include Linux equivalents for all Windows tools and commands (e.g., show how to check DHCP service status, agent installation, etc. on Linux).
- Ensure external links for Linux are as comprehensive and accessible as those for Windows.
- Balance the level of detail and troubleshooting guidance between Windows and Linux sections.
Migrate
Azure Migrate Collector virtual machine extension reference
...migrate/migrate-virtual-machine-extension-reference.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows-first bias in several areas. Windows examples and tools (such as PowerShell) are presented before Linux equivalents, and some CLI commands (e.g., for viewing, updating, and removing the extension) only show the Windows extension name, omitting the Linux variant. Troubleshooting and log paths are provided for both OSes, but PowerShell instructions are included for Linux servers, which is not a native tool for most Linux environments. There is a lack of parity in examples and command references for Linux users.
Recommendations
- Provide all CLI and PowerShell commands for both Windows and Linux extensions, showing both extension names in each example.
- Add native Linux shell (bash) or scripting examples for Linux servers instead of PowerShell for Linux.
- Ensure troubleshooting, update, and removal instructions explicitly include Linux extension names and paths.
- Alternate the order of Windows and Linux sections, or present them side-by-side, to avoid implicit prioritization.
- Clarify when PowerShell is required on Linux and provide guidance for installing or using it, or prefer native tools.
Migrate
Troubleshoot issues with agentless and agent-based dependency analysis
...lob/main/articles/migrate/troubleshoot-dependencies.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows bias in several ways: Windows tools and troubleshooting steps (e.g., PowerShell, Registry Editor, WMI, Control Panel) are frequently mentioned first or exclusively, with Linux equivalents often less detailed or omitted. Many error codes and remediation steps focus on Windows-specific technologies (PowerShell, WinRM, WMI), and examples for Linux are fewer and less comprehensive. Some troubleshooting flows (e.g., registry edits, WMI namespace configuration) have no Linux counterpart. Even in cross-platform scenarios, Windows commands and tools are presented before Linux ones.
Recommendations
- Ensure all troubleshooting steps and examples are provided for both Windows and Linux, with equal detail and prominence.
- When listing commands or tools, alternate the order or present Windows and Linux instructions side-by-side.
- Provide Linux equivalents for Windows-specific steps (e.g., registry edits, WMI configuration) or clarify when a step is not applicable to Linux.
- Expand Linux troubleshooting guidance, including common issues, commands, and remediation steps, matching the depth given to Windows.
- Review error tables and ensure Linux-specific errors and solutions are equally documented.
- Avoid assuming PowerShell or Windows tools are available on Linux; use native Linux tools and commands where appropriate.
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
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation demonstrates a Windows bias primarily through its exclusive references to Windows Server Failover Clusters, Cloud Witness, and Windows licensing (Azure Hybrid Benefit for Windows Server and SQL Server). High availability and disaster recovery sections only mention Windows-specific clustering and witness options, with no mention of Linux-based clustering or migration scenarios. There are no examples or guidance for Linux SQL Server instances, nor are Linux tools or patterns referenced. The documentation assumes Windows as the default environment for SQL Server migration and assessment.
Recommendations
- Include explicit guidance and examples for assessing and migrating SQL Server instances running on Linux (e.g., SQL Server on Ubuntu, RHEL, SLES).
- Reference Linux clustering and high availability options (such as Pacemaker, Corosync, or Linux witness configurations) in the high availability and disaster recovery sections.
- Clarify Azure Hybrid Benefit applicability for Linux (RHEL/SLES) and provide parity in licensing and cost optimization guidance.
- Add links to best practices for running SQL Server on Azure VMs with Linux OS, similar to the Windows performance guidelines referenced.
- Ensure screenshots and UI instructions are not Windows-centric and mention any differences for Linux-based SQL Server deployments.
- Provide troubleshooting and support status guidance for Linux operating systems in the assessment review sections.
Migrate
Discover servers running in a VMware environment with Azure Migrate Discovery and assessment
...blob/main/articles/migrate/tutorial-discover-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-specific tools and patterns (such as PowerShell scripts for appliance setup) are mentioned before or instead of Linux equivalents. The instructions for manual appliance setup reference only Windows Server 2019/2022 and PowerShell, with no Linux alternative. Windows requirements (e.g., PowerShell version, Windows authentication, IIS/ASP.NET discovery) are described in detail, while Linux instructions (e.g., SSH key-based authentication) are less prominent and lack step-by-step examples. There are no Linux-based setup scripts or appliance deployment instructions, and Windows tools/paths (e.g., C:\Program Files) are referenced exclusively.
Recommendations
- Provide equivalent Linux-based setup instructions for the Azure Migrate appliance, including shell script options and supported Linux distributions.
- Include Linux examples and screenshots for credential provisioning, appliance configuration, and troubleshooting.
- Mention Linux tools and paths (e.g., /opt, /usr/local) alongside Windows paths when referencing installation locations.
- Ensure parity in authentication mechanisms, describing both Windows and Linux workflows in equal detail.
- Offer guidance for Linux-only environments, including how to perform agentless discovery and dependency analysis without Windows components.
- Add troubleshooting steps and FAQs for common Linux issues encountered during appliance setup and discovery.
Migrate
Overview of Azure Migrate Assessment Report
...e-docs/blob/main/articles/migrate/assessment-report.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 as the primary example of conditional readiness, mentioning Hyper-V (a Windows-centric virtualization platform) before VMware, and omitting explicit Linux server examples or Linux-specific considerations. There are no examples or guidance tailored to Linux workloads, and remediation guidance is only illustrated for Windows scenarios.
Recommendations
- Include examples of Linux server readiness issues (e.g., unsupported Linux distributions or kernel versions) alongside Windows Server examples.
- Provide remediation guidance for common Linux migration challenges, such as unsupported file systems or missing drivers.
- Mention Linux virtualization platforms (e.g., KVM, Xen) in addition to Hyper-V and VMware, or clarify how assessments apply to Linux workloads running on these platforms.
- Ensure that examples and guidance are balanced between Windows and Linux, or explicitly state parity where applicable.
- Add notes or links to Linux-specific migration documentation or best practices.
Migrate
Agent-based Migration in the Migration and Modernization Tool
...articles/migrate/agent-based-migration-architecture.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Windows-specific tools, paths, and configuration patterns (e.g., registry keys, MMC snap-ins, C:\Program Files paths) for managing and optimizing agent-based migration. There are no Linux equivalents or examples provided for installation, configuration, or performance tuning, and Windows terminology appears first and exclusively throughout the article.
Recommendations
- Include Linux-specific instructions for installing and managing the Mobility service, such as relevant commands, file paths, and service management.
- Provide Linux equivalents for configuration and performance tuning, e.g., how to throttle bandwidth or monitor replication on Linux servers.
- Add examples of antivirus exclusions for common Linux distributions (e.g., /opt/msazure/ or /var/log/asr/).
- Reference Linux tools and patterns (systemd, cron, config files) alongside Windows tools (MMC, registry).
- Ensure all steps and tables mention both Windows and Linux environments where applicable, or clarify OS-specific differences.
Migrate
Azure Migrate Application and Code Assessment for Java Version 7
...docs/blob/main/articles/migrate/appcat/java-preview.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Examples
Windows Known Issues
Summary
The documentation provides parity between Windows and Linux/macOS in most areas, including download links, installation instructions, and command examples. However, Windows is frequently listed first in download tables and examples, and known issues are disproportionately focused on Windows-specific problems. There are no PowerShell-heavy sections or exclusive use of Windows tools, but the ordering and emphasis may subtly prioritize Windows users.
Recommendations
- Alternate the order of OS examples and download links so Linux/macOS are sometimes listed first.
- Provide equal detail for Linux/macOS-specific known issues, or explicitly state when there are none.
- Add troubleshooting sections for Linux/macOS, even if only to confirm absence of major issues.
- Ensure that all sample scripts and instructions are equally detailed for Linux/macOS and Windows, and avoid using Windows as the default reference.
- Highlight cross-platform compatibility in the introduction to reinforce parity.
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation exhibits a strong Windows bias: deployment and management of the Azure Migrate appliance are centered around PowerShell scripts and Windows tooling, with instructions and troubleshooting steps exclusively referencing Windows interfaces (e.g., certificate manager, group policy editor, Windows Update). There are no Linux-specific deployment, management, or troubleshooting examples, and Windows patterns/tools are mentioned first and exclusively throughout the page.
Recommendations
- Provide equivalent Linux shell (bash) deployment and management instructions, including how to run installer scripts, manage certificates, and troubleshoot updates on Linux-based appliances.
- Include examples and screenshots for Linux environments (e.g., using openssl or certtool for certificate management, Linux package managers for updates).
- Explicitly state OS requirements and clarify if Linux is supported for appliance deployment; if not, document the limitation.
- Offer troubleshooting steps for common Linux issues (e.g., permissions, firewall configuration, certificate stores).
- Ensure parity in credential management instructions for Linux (e.g., how to add Linux server credentials, handle SSH keys, etc.).
Migrate
Register Azure Migrate appliance using a preconfigured Microsoft Entra ID application
...s/migrate/how-to-register-appliance-using-entra-app.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page exhibits a strong Windows bias. All command-line examples for certificate generation, export, and registry modification use PowerShell, with file paths and procedures tailored to Windows environments. Windows-specific tools and concepts (e.g., Registry Editor, HKLM registry paths, double-clicking .pfx files for installation) are used exclusively, with no Linux or cross-platform alternatives provided. While OpenSSL and mkcert are briefly mentioned as certificate generation options, no Linux or bash examples are given, and the step-by-step instructions always default to Windows/PowerShell. There is no guidance for Linux-based Azure Migrate appliances or for users operating in non-Windows environments.
Recommendations
- Provide equivalent Linux/bash command examples for certificate generation and export using OpenSSL or mkcert.
- Include instructions for installing certificates on Linux appliances (e.g., using openssl, update-ca-certificates, or keytool).
- Document how to configure appliance settings on Linux, including where to store certificate files and how to update configuration (since registry editing is Windows-specific).
- Clarify which steps are Windows-only and provide cross-platform alternatives where possible.
- Ensure screenshots and file paths are not exclusively Windows-centric; include Linux file system examples.
- Explicitly state platform requirements and support for Azure Migrate appliance (Windows vs. Linux) at the beginning of the documentation.
Migrate
Assessment Best Practices in Azure Migrate Discovery and Assessment Tool
...lob/main/articles/migrate/best-practices-assessment.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 Windows-centric workloads and migration scenarios, such as ASP.NET apps running on IIS and SQL Server, with no mention of Linux workloads or migration paths. Examples and assessment types are centered around Windows technologies, and there are no Linux-specific examples, tools, or guidance. The migration tool guidance also omits Linux migration considerations.
Recommendations
- Include explicit examples and assessment guidance for Linux workloads (e.g., Apache, Nginx, MySQL, PostgreSQL) in addition to Windows workloads.
- Add Linux-specific migration scenarios and best practices, such as migrating Linux VMs or containers to Azure.
- Mention Linux-compatible tools and agent requirements for discovery and assessment, and clarify any differences in data collection or sizing for Linux servers.
- Provide parity in troubleshooting and common issues for Linux environments, including OS-specific considerations.
- Ensure that examples and assessment types do not exclusively reference Windows technologies, and present Linux options alongside Windows ones.
Migrate
Security Best Practices for Deploying an Appliance
.../blob/main/articles/migrate/best-practices-security.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by focusing almost exclusively on Windows Server deployment, PowerShell installation scripts, and Windows-specific security hardening tools (such as GPOs and the Security Compliance Toolkit). Linux is only mentioned in passing (e.g., port 22 for communication), with no examples or guidance for deploying or hardening the appliance on Linux systems. Windows tools and patterns are presented first and exclusively, with no Linux alternatives or parity.
Recommendations
- Provide explicit instructions and examples for deploying the Azure Migrate appliance on supported Linux distributions, if applicable.
- Include Linux-specific hardening guidance, such as using CIS Benchmarks, SELinux/AppArmor, and Linux-native security tools.
- Offer installation and configuration examples using Linux shell scripts (e.g., Bash) alongside PowerShell.
- Mention Linux credential storage and encryption mechanisms, such as using keyrings or encrypted files.
- List Linux equivalents for Windows tools (e.g., alternatives to GPOs for policy management).
- Ensure that network and firewall configuration examples include Linux-based tools and commands (e.g., iptables, firewalld).
Migrate
Questions about assessments in Azure Migrate
...icles/migrate/common-questions-discovery-assessment.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page for Azure Migrate assessments demonstrates a Windows bias by consistently referencing Windows-centric technologies (Hyper-V, IIS, SQL Server) and tools, while omitting Linux-specific examples, patterns, or troubleshooting steps. Windows environments (Hyper-V, IIS, SQL Server) are mentioned explicitly and repeatedly, whereas Linux environments (e.g., Linux VMs, Apache/Nginx web servers, MySQL/PostgreSQL databases) are not addressed in assessment types, readiness checks, or error resolution. The documentation assumes Windows server roles and migration scenarios, and does not provide parity for Linux workloads or tools.
Recommendations
- Add explicit examples and guidance for assessing Linux VMs, including common distributions (Ubuntu, CentOS, RHEL, SUSE).
- Include troubleshooting steps and readiness checks for Linux environments, such as agent connectivity, performance counter collection, and supported configurations.
- Document assessment types and migration paths for Linux-based workloads (e.g., Apache/Nginx web servers, MySQL/PostgreSQL databases) alongside Windows equivalents.
- Reference Linux tools and commands where relevant (e.g., systemd, top, sar, lsof) for performance and readiness data collection.
- Ensure that all instructions, error messages, and remediation steps are applicable to both Windows and Linux environments, or clearly indicate platform-specific differences.
- Provide parity in examples, tutorials, and links for Linux environments, not just VMware/Hyper-V/Windows-centric scenarios.
Migrate
Tutorial to assess web apps for migration
...lob/main/articles/migrate/create-web-app-assessment.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 on ASP.NET web apps (Windows-centric technology) before mentioning Java web apps, omitting Linux/PHP/Node.js examples, and referencing Windows-specific tools and optimization guides (e.g., Windows Dockerfiles) in the 'Next steps' section. There are no Linux-specific instructions, examples, or references to Linux-native web app frameworks or containerization patterns.
Recommendations
- Include examples and guidance for Linux-based web apps (e.g., PHP, Node.js, Python) alongside ASP.NET and Java.
- Provide parity in performance data collection and sizing for common Linux web servers (e.g., Apache, Nginx) and application runtimes.
- Add links to Linux Dockerfile optimization guides and best practices for Linux containers in AKS and App Service.
- Reference Linux tools and patterns (e.g., Bash scripts, systemd, Linux monitoring tools) where relevant.
- Ensure screenshots and walkthroughs demonstrate both Windows and Linux scenarios, including discovery and assessment of Linux workloads.
Migrate
Common Questions About the Migration and Modernization Tool
.../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. PowerShell and Windows-specific tools (NetQosPolicy, Windows Scheduled Tasks) are used exclusively in the bandwidth throttling example, with no Linux equivalents or cross-platform alternatives provided. Windows operating systems are listed first in support matrices and migration scenarios, and Windows-centric migration use cases (Active Directory, IIS/ASP.NET) are described in detail, while Linux-specific migration scenarios and tools are less emphasized or omitted. There are no Linux shell or tool examples for common operational tasks, such as bandwidth throttling or automation.
Recommendations
- Provide equivalent Linux examples for operational tasks, such as bandwidth throttling (e.g., using tc, wondershaper, or iptables on Linux).
- Include Linux shell script examples alongside PowerShell for automation and scheduled tasks.
- Present operating system support tables in a neutral order (e.g., alphabetical or grouped by OS family) rather than listing Windows first.
- Expand migration scenarios and troubleshooting guidance for popular Linux workloads (e.g., Apache, Nginx, PostgreSQL, MySQL) and mention Linux-specific migration considerations.
- Explicitly state cross-platform support and highlight any differences or limitations for Linux users.
- Reference Linux-native tools and patterns where appropriate, and provide links to relevant documentation for Linux users.
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page for Azure Migrate's Business Case shows a clear Windows bias. Windows Server and SQL Server licensing, ESU, and management tooling (System Center) are discussed in detail, while Linux is only briefly mentioned in a few cost formulas and never described in terms of licensing, security, or management. There are no Linux-specific examples, tools, or migration strategies, and Windows scenarios are consistently presented first and in greater depth.
Recommendations
- Add explicit examples and cost breakdowns for Linux workloads, including common Linux distributions and their licensing/support models.
- Discuss Linux management and monitoring tools (e.g., integration with Azure Monitor, Update Manager for Linux, or third-party tools) alongside System Center for Windows.
- Include Linux security scenarios, such as Defender for Linux, SELinux, or other Linux-native security solutions.
- Present migration strategies and sizing/costing for Linux workloads (e.g., Apache, MySQL, PostgreSQL, Tomcat) with parity to Windows workloads.
- Ensure that Linux is mentioned equally and not just as an afterthought in cost tables and formulas.
- Provide Linux-specific sustainability and emissions calculations if they differ from Windows workloads.
Migrate
Support matrix for web apps migration
...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 IIS on Windows Server, and requires Windows PowerShell for migration. Linux servers are explicitly marked as unsupported, and there are no examples, instructions, or references for Linux-based web app migration. All tooling and requirements are Windows-centric.
Recommendations
- Clearly state future plans or timelines for Linux support if applicable.
- Add a section comparing Windows and Linux migration support, even if Linux is not currently supported, to set expectations.
- Provide alternative migration paths or recommendations for Linux-based web apps (e.g., manual migration, third-party tools, or links to relevant documentation).
- Include a FAQ addressing Linux scenarios and why they are not supported, with guidance for affected users.
- Ensure that future updates include Linux parity in both tooling and documentation examples.
Migrate
Azure VM assessments in Azure Migrate
...in/articles/migrate/concepts-assessment-calculation.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Heavy
Missing Linux Example
Summary
The documentation page exhibits a Windows bias by listing Windows operating systems in detail and first in readiness tables, providing extensive guidance for Windows versions, and referencing Windows-specific scenarios (e.g., boot types, support agreements). Linux is mentioned only generically or as a single line, with no breakdown of supported distributions or readiness nuances. There are no Linux-specific examples, troubleshooting steps, or migration caveats, and the documentation does not mention Linux tools or provide parity in guidance for Linux environments.
Recommendations
- Expand the guest operating system readiness table to list major Linux distributions and versions, including specific readiness statuses and migration caveats.
- Provide Linux-specific examples and troubleshooting steps, such as handling kernel versions, disk partitioning, and bootloader issues.
- Include guidance on collecting Linux performance data, e.g., using native Linux tools or scripts, and clarify how the appliance interacts with Linux VMs.
- Add links to Linux migration best practices and documentation, similar to those provided for Windows.
- Ensure that Linux scenarios (e.g., UEFI boot, disk sizing, security readiness) are described with the same level of detail as Windows scenarios.
- Mention Linux tools or commands where relevant, and provide parity in examples for both Windows and Linux environments.
Migrate
Azure SQL assessments in Azure Migrate Discovery and assessment tool
...s/migrate/concepts-azure-sql-assessment-calculation.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Powershell Heavy
Summary
The documentation page demonstrates a Windows bias in several ways: Windows tools and patterns (such as Windows Server Failover Clusters, Cloud Witness, and PowerShell) are mentioned exclusively or before Linux equivalents. References to migration best practices and sizing link to Windows-specific documentation, and examples or guidance for Linux-based SQL Server deployments (such as on RHEL or SLES) are missing. The documentation assumes Windows environments as the default and does not provide parity for Linux scenarios.
Recommendations
- Include explicit examples and guidance for assessing and migrating SQL Server instances running on Linux (RHEL, SLES, Ubuntu, etc.), including configuration, performance data collection, and migration steps.
- Provide links to Linux-specific best practices for SQL Server on Azure VMs, similar to those given for Windows.
- Mention and describe Linux clustering and high availability options (such as Pacemaker, Corosync, or Linux witness options) alongside Windows Server Failover Clusters.
- Add PowerShell alternatives for Linux (such as Bash scripts or Azure CLI commands) where relevant.
- Ensure references to documentation (such as performance guidelines) include both Windows and Linux versions, or clarify applicability.
- Review all default settings and recommendations to ensure they are not Windows-centric and are equally applicable to Linux environments.
Migrate
Azure App Service assessments in Azure Migrate Discovery and assessment tool
...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 exhibits a Windows bias by focusing primarily on ASP.NET web apps running on IIS servers, with no mention of Linux-based web app scenarios (such as Apache, Nginx, or Java apps on Linux). Examples and references are Windows-centric, and Windows tools/patterns (IIS, ASP.NET) are mentioned exclusively or before any Linux equivalents. There are no Linux-specific instructions, examples, or references to Linux-based web servers or migration considerations.
Recommendations
- Add explicit examples and guidance for assessing Linux-based web apps (e.g., Java apps running on Apache Tomcat on Linux, PHP apps on Apache/Nginx).
- Include references to Linux web server environments and how the Azure Migrate appliance discovers and assesses them.
- Provide parity in documentation by listing both Windows and Linux scenarios when describing supported platforms and migration paths.
- Clarify any differences in assessment, readiness, and cost calculations for Linux-based web apps.
- Add links to tutorials or guides for Linux web app migration to Azure App Service.
Migrate
Build a migration plan with Azure Migrate
...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 prioritizing Windows Server migration scenarios, mentioning Windows-specific features (such as Azure Hybrid Benefit for Windows Server licenses and the Windows OS upgrade process), and providing detailed guidance and tooling for Windows workloads. There is a lack of explicit Linux migration examples, Linux-specific tooling, or parity in OS upgrade guidance for Linux servers. Windows tools and patterns (e.g., Custom Script Extension for Windows, Windows Server end-of-support incentives) are described in detail, while Linux equivalents are either omitted or mentioned only briefly.
Recommendations
- Add explicit examples and guidance for migrating Linux servers, including common Linux distributions and their specific considerations.
- Provide parity in OS upgrade documentation for Linux (e.g., guidance for in-place upgrades or migration of Linux VMs, including supported distributions and tooling).
- Mention Linux-specific migration blockers, compatibility checks, and remediation steps alongside Windows examples.
- Include references to Linux tools and extensions (e.g., Custom Script Extension for Linux, supported automation scripts) where relevant.
- Ensure cost optimization guidance covers Linux licensing/subscription scenarios with equal detail as Windows.
- Balance the order of presentation so that Linux and Windows scenarios are introduced together, rather than Windows-first.
Migrate
Agentless Replication of VMware Virtual Machines
...rticles/migrate/concepts-vmware-agentless-migration.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in several areas. The only example for bandwidth throttling uses a Windows PowerShell cmdlet (New-NetQosPolicy) and references a Windows executable (GatewayWindowsService.exe). Configuration file paths and instructions (e.g., C:\ProgramData\Microsoft Azure\Config) are Windows-specific, with no mention of Linux equivalents. There are no Linux shell or tool examples, nor guidance for Linux-based appliances or environments. Windows tools and patterns are mentioned exclusively and before any Linux alternatives (which are absent).
Recommendations
- Provide Linux equivalents for all configuration steps, such as file paths and service management (e.g., /etc/azure-migrate/config, systemctl restart gateway).
- Include Linux shell examples for bandwidth throttling (e.g., using tc, wondershaper, or firewalld) alongside PowerShell examples.
- Clarify whether the Azure Migrate appliance supports Linux and, if so, document Linux-specific installation, configuration, and management steps.
- Reference both Windows and Linux service names and restart commands when instructing users to restart services.
- Add notes or sections highlighting differences or parity between Windows and Linux environments for agentless migration.
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates Windows bias by providing command-line instructions exclusively in PowerShell, referencing opening PowerShell as Administrator, and omitting equivalent Linux/macOS shell examples. The installation instructions for Az CLI link to general documentation, but all usage examples assume a Windows environment. There is no mention of Linux terminal usage, nor are bash or shell commands provided alongside PowerShell examples.
Recommendations
- Provide equivalent Linux/macOS instructions for Az CLI usage, including bash/zsh shell commands.
- Explicitly mention that Az CLI can be used on Linux/macOS and provide examples for those platforms.
- Avoid assuming the user is on Windows (e.g., 'open PowerShell as Administrator'); instead, use neutral phrasing like 'open your terminal'.
- Include screenshots or instructions that are platform-agnostic or offer both Windows and Linux/macOS variants.
- Add a note clarifying cross-platform support for all tools and commands referenced.