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 501-525 of 918 flagged pages
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/how-to-discover-sql-existing-project.md
...ticles/migrate/how-to-discover-sql-existing-project.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing PowerShell requirements, Windows OS credentials, and Windows authentication patterns exclusively. There are no examples or instructions for Linux-based environments, tools, or authentication methods. The documentation assumes the use of Windows-centric tools and patterns, and does not provide parity for Linux users.
Recommendations
- Include explicit instructions and examples for discovering SQL Server instances on Linux-based servers, if supported.
- Mention and provide guidance for using Linux authentication methods (e.g., SSH, Linux user credentials) where applicable.
- Reference Linux tools or command-line utilities (e.g., Bash, shell scripts) alongside PowerShell requirements.
- Clarify whether the Azure Migrate appliance supports Linux-based discovery, and if so, provide steps and screenshots relevant to Linux environments.
- Avoid assuming Windows OS as the default; use inclusive language and parallel instructions for both Windows and Linux platforms.
Create Pull Request
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/how-to-create-azure-sql-assessment.md
...articles/migrate/how-to-create-azure-sql-assessment.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by referencing Windows-specific tools and patterns (e.g., Cloud Witness, Windows Server Failover Clusters), linking to Windows-focused best practices, and omitting Linux-specific instructions or examples. There are no Linux or cross-platform command-line examples, and Linux migration scenarios or considerations are not mentioned, despite Azure SQL supporting Linux-based SQL Server workloads.
Recommendations
- Include Linux-specific migration scenarios, such as assessing SQL Server instances running on Linux.
- Provide parity in documentation by referencing both Windows and Linux tools for high availability and disaster recovery (e.g., mention Linux clustering or Pacemaker alternatives).
- Add links to Linux best practices for SQL Server on Azure VMs, not just Windows.
- Where Windows-specific features (like Cloud Witness) are mentioned, add equivalent Linux guidance or note the differences.
- Include screenshots or walkthroughs that show Linux-based environments where applicable.
- Explicitly state support and any limitations for Linux-based SQL Server migrations in the assessment process.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/how-to-migrate-at-scale.md
.../blob/main/articles/migrate/how-to-migrate-at-scale.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page demonstrates a strong Windows bias by exclusively referencing PowerShell scripts for automation, providing only PowerShell (.ps1) script names and usage instructions, and linking to PowerShell sample repositories. There are no examples or guidance for Linux users, such as Bash scripts or cross-platform CLI alternatives. The documentation assumes the use of Windows-centric tools and scripting environments, which may limit accessibility for Linux administrators.
Recommendations
- Provide equivalent Bash or shell script examples for Linux users, or clarify if the scripts are cross-platform and how to run them on Linux (e.g., via PowerShell Core).
- Include instructions for installing and using PowerShell on Linux, if PowerShell scripts are the only automation method.
- Mention and demonstrate Azure CLI alternatives where possible, as Azure CLI is cross-platform and familiar to Linux users.
- Reorganize sections to present cross-platform or Linux options alongside Windows/PowerShell options, rather than only referencing Windows tools.
- Explicitly state any platform limitations or requirements for the provided scripts.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/start-here-vmware.md
...e-docs/blob/main/articles/migrate/start-here-vmware.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a bias towards Windows environments by exclusively referencing Azure PowerShell for automation and migration examples, and by omitting any mention of Linux-based tools or CLI alternatives. There are no Linux command-line examples or references to Bash/CLI workflows, which may disadvantage users operating from Linux or cross-platform environments.
Recommendations
- Provide equivalent Azure CLI (az) examples alongside PowerShell for all migration and automation steps.
- Explicitly mention that migration and automation can be performed from Linux or macOS environments, not just Windows.
- Include links to documentation or tutorials that use Linux-based tools or scripts for migration tasks.
- Where PowerShell is referenced, add a note or section for Bash/CLI users, ensuring parity in instructions and examples.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/how-to-discover-applications.md
.../main/articles/migrate/how-to-discover-applications.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a moderate Windows bias. While it mentions both Windows and Linux servers in credential requirements and MySQL discovery, most detailed examples, tool mentions, and feature support are Windows-centric. Windows authentication and tools (e.g., File Server role, IIS/ASP.NET) are described in detail, while Linux equivalents are either not mentioned or only briefly referenced. Some features, such as File Server discovery, are explicitly limited to Windows. There are no Linux command-line or tool examples, and Windows terminology (e.g., 'local admin privileges', 'domain credentials') is used predominantly.
Recommendations
- Provide explicit Linux examples for credential setup, discovery, and supported roles (e.g., show how to add Linux credentials, what permissions are needed, and how to verify them).
- Include Linux-native tools and roles (e.g., Apache/Nginx for web servers, Samba/NFS for file servers) in the discovery documentation, or clarify their support status.
- Balance the order of presentation: mention Linux and Windows equally, and avoid always listing Windows first.
- If certain features (like File Server discovery) are Windows-only, clearly state this and, if possible, provide guidance or roadmap for Linux support.
- Add sample outputs or screenshots for Linux scenarios, not just Windows.
- Use neutral terminology where possible (e.g., 'administrator/root privileges' instead of 'local admin privileges').
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/how-to-migrate-vmware-vms-with-cmk-disks.md
...es/migrate/how-to-migrate-vmware-vms-with-cmk-disks.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a strong Windows bias by exclusively using Azure PowerShell for all command-line examples and automation steps. There are no CLI or Bash examples, and all referenced scripts and instructions assume a Windows/PowerShell environment. Even when linking to further resources, the documentation points to Windows/PowerShell-specific guides. There is no mention of Linux, Bash, or cross-platform alternatives, which may hinder users on non-Windows platforms.
Recommendations
- Provide equivalent Azure CLI (az) and Bash examples alongside PowerShell scripts for all automation and scripting steps.
- Reference both Windows and Linux guides for creating and managing resources such as Disk Encryption Sets.
- Explicitly state that the process can be performed from Linux/macOS environments using Azure CLI, and provide instructions or links for those workflows.
- Where possible, use cross-platform tools and commands (e.g., Azure CLI) as the primary example, or present both PowerShell and CLI in parallel.
- Clarify any steps that are platform-specific, and offer alternatives for users on different operating systems.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/how-to-create-group-machine-dependencies.md
...es/migrate/how-to-create-group-machine-dependencies.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 ways. Installation instructions for the MMA and Dependency agents provide more detailed, step-by-step guidance for Windows (including GUI and command-line/scripted options), while Linux instructions are brief and lack equivalent detail. Windows tools and installation patterns (such as double-clicking installers, Configuration Manager, and Intigua) are mentioned, but Linux alternatives (like package managers or automation tools) are not. There are no Linux-specific troubleshooting tips or automation examples, and the order of presentation consistently puts Windows before Linux.
Recommendations
- Provide equally detailed, step-by-step instructions for Linux agent installation, including common automation methods (e.g., using shell scripts, Ansible, or package managers).
- Include Linux-specific troubleshooting tips and links to relevant documentation, similar to the Windows references.
- When listing platforms, alternate the order or present Windows and Linux instructions in parallel to avoid the perception of Windows being primary.
- Mention Linux-native tools or patterns (such as systemd service management, log file locations, or SELinux/AppArmor considerations) where relevant.
- Offer example scripts for bulk installation on Linux, analogous to the provided Windows script link.
- Ensure that all features, options, and caveats are covered for both Windows and Linux environments.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/how-to-set-up-appliance-physical.md
...n/articles/migrate/how-to-set-up-appliance-physical.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation demonstrates a strong Windows bias. All setup and installation instructions use Windows-specific tools and commands (PowerShell, CertUtil, Registry Editor, Windows roles like IIS), with no equivalent Linux instructions or examples. The process assumes the appliance is being set up on a Windows server, and there is no mention of Linux-based deployment or commands for Linux environments. Linux is only referenced as a discovery target, not as a platform for running the appliance.
Recommendations
- Provide equivalent setup instructions for deploying the Azure Migrate appliance on Linux servers, including shell script examples and Linux package dependencies.
- Include Linux commands for verifying file hashes (e.g., sha256sum) alongside CertUtil.
- Document how to run the installer script and configure the appliance using Bash or compatible Linux shells.
- List Linux prerequisites (e.g., required packages, services) and describe how to install/configure them.
- If the appliance cannot be run on Linux, state this limitation explicitly at the beginning of the documentation.
- Ensure all steps that reference Windows tools (PowerShell, Registry Editor, IIS) have Linux alternatives or clarifications where applicable.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/how-to-review-sql-assessment.md
.../main/articles/migrate/how-to-review-sql-assessment.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page exhibits a Windows bias by exclusively referencing Windows-based SQL Server deployments and migration scenarios. All examples, best practices, and links are tailored to Windows environments (e.g., Windows-based SQL Server on Azure VM, Windows-specific performance guidelines, and cluster best practices). There is no mention of Linux-based SQL Server deployments, migration considerations for Linux, or links to Linux-specific documentation. The absence of Linux examples and guidance may lead Linux users to feel unsupported or unclear about their migration path.
Recommendations
- Include explicit references to SQL Server on Linux, both on-premises and as a migration target, where applicable.
- Provide parallel examples and best practices for Linux-based SQL Server deployments (e.g., storage and compute sizing, cluster configurations, and high availability).
- Add links to Linux-specific documentation, such as performance guidelines and cluster best practices for SQL Server on Linux VMs.
- Clarify in each section whether the guidance applies to both Windows and Linux, or specify differences where relevant.
- Ensure that migration guidance covers both Windows and Linux source environments, including any unique considerations or prerequisites for Linux.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/how-to-scale-out-for-migration.md
...ain/articles/migrate/how-to-scale-out-for-migration.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation demonstrates a strong Windows bias. All deployment and configuration steps for the Azure Migrate scale-out appliance are based on Windows Server (2019/2022), with explicit requirements for Windows-only tools and environments. All scripting and command-line examples use PowerShell, and Windows-specific tools like CertUtil are referenced. There is no mention of Linux-based deployment, tools, or equivalent instructions, nor are any Linux shell or cross-platform alternatives provided.
Recommendations
- Provide equivalent instructions and supported workflows for deploying the Azure Migrate appliance on Linux-based systems, if technically feasible.
- Include Linux shell (bash) examples for tasks such as checksum validation (e.g., using sha256sum) alongside Windows examples.
- Document any platform limitations explicitly, and clarify if the appliance is only supported on Windows. If so, state this early and prominently.
- Where PowerShell scripts are required, indicate whether PowerShell Core (cross-platform) is supported, and provide installation guidance for Linux if applicable.
- Offer troubleshooting and configuration steps relevant to Linux environments, or provide rationale for Windows-only support.
- Consider referencing cross-platform tools or approaches (e.g., using OpenSSL for hashing) to improve accessibility for non-Windows administrators.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/how-to-review-discovered-inventory.md
...articles/migrate/how-to-review-discovered-inventory.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a subtle Windows bias. Windows servers and tools are often mentioned first or exclusively (e.g., 'installed roles and features (Windows servers only)'), and Windows credential requirements are described in more detail and before Linux equivalents. There are no concrete Linux command-line examples, and Linux-specific discovery nuances are less elaborated. The documentation refers to Windows-centric technologies (e.g., .NET, IIS, SQL Server) without equal mention of Linux alternatives (e.g., Apache, NGINX, MySQL/PostgreSQL).
Recommendations
- Provide Linux-specific examples and screenshots alongside Windows ones, especially for credential setup, permissions, and discovery troubleshooting.
- List Linux and Windows options in parallel, not always with Windows first.
- Expand on Linux discovery requirements and troubleshooting, including common Linux distributions and their nuances.
- Include examples of Linux web applications (e.g., Apache, NGINX, Tomcat) and databases (e.g., MySQL, PostgreSQL) in inventory and assessment sections.
- Clarify that features like software inventory and dependency analysis are supported equally on Linux, and provide any Linux-specific limitations or steps.
- Where Windows tools or technologies are mentioned (e.g., .NET, IIS), provide Linux equivalents or note support for open-source stacks.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/how-to-set-up-appliance-hyper-v.md
...in/articles/migrate/how-to-set-up-appliance-hyper-v.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation is heavily oriented towards Windows environments, specifically Hyper-V, and consistently uses Windows tools and patterns. All command-line examples use Windows commands (CertUtil, Get-FileHash, PowerShell cmdlets), and GUI instructions reference Windows-only tools (Hyper-V Manager, Local Group Policy Editor). There are no Linux equivalents or examples provided, and Linux is only mentioned as a possible credential type, not as a platform for appliance deployment or management.
Recommendations
- Provide equivalent instructions and examples for deploying and managing the Azure Migrate appliance on Linux hosts, if supported.
- Include Linux command-line examples for tasks like file hash verification (e.g., using sha256sum or openssl).
- Mention and document any Linux-based management tools or scripts, or clarify if only Windows is supported.
- If the appliance can only be deployed on Windows/Hyper-V, explicitly state this limitation early in the documentation.
- For credential delegation and other advanced configuration, provide Linux alternatives or note the lack of support.
- Ensure parity in screenshots and walkthroughs for both Windows and Linux environments where possible.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/how-to-view-a-business-case.md
...b/main/articles/migrate/how-to-view-a-business-case.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by focusing on Windows Server and SQL Server in cost and licensing examples, referencing extended security updates (ESU) specifically for Windows workloads, and mentioning Windows licensing and management tools. There are no explicit examples or considerations for Linux workloads, distributions, or licensing, and no Linux-specific migration scenarios or cost factors are discussed. The documentation assumes Windows-centric environments and tools, omitting parity for Linux users.
Recommendations
- Include explicit references to Linux workloads, distributions, and licensing considerations in cost and migration reports.
- Provide examples and scenarios for migrating Linux servers and open-source databases, including cost estimation for Linux VMs and workloads.
- Discuss extended security update policies (or lack thereof) for Linux distributions, and clarify how Azure handles end-of-support for Linux OSes.
- Mention Azure management and security tools as they apply to Linux (e.g., Azure Monitor, Defender for Linux, Update Manager for Linux).
- Balance references to Windows and SQL Server with equivalent Linux technologies (e.g., PostgreSQL, MySQL, Apache, NGINX) in migration and cost estimation sections.
- Add screenshots or report examples that include both Windows and Linux server distributions to reflect diverse customer environments.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/how-to-set-up-appliance-vmware.md
...ain/articles/migrate/how-to-set-up-appliance-vmware.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation exhibits a Windows bias in several ways: PowerShell is the only script-based installation method mentioned, and all command-line examples (such as hash verification) use Windows tools (CertUtil, Command Prompt). File paths and installation instructions reference Windows conventions (e.g., C:\Program Files). There are no Linux shell or tool equivalents provided for key steps such as hash verification or appliance setup, and Windows authentication is emphasized for discovery features. Linux is mentioned only as a credential type, with no further guidance or examples.
Recommendations
- Provide equivalent Linux shell commands for verifying OVA file hashes (e.g., using sha256sum or openssl).
- Include instructions for running the installer script on Linux-based systems, if supported, or clarify if only Windows is supported.
- Show Linux file paths and conventions where relevant (e.g., for VDDK installation).
- Offer examples of Linux authentication and discovery workflows, not just Windows/SQL Server/IIS.
- Balance the order of presentation so Linux options are not always listed after or as an afterthought to Windows.
- Explicitly state OS support limitations where applicable, and provide parity in troubleshooting and validation steps for both Windows and Linux environments.
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 focused exclusively on migrating Hyper-V (a Windows-centric virtualization platform) servers to Azure, with all instructions, terminology, and tooling centered around Windows environments. There are no Linux or cross-platform examples, and the tools and patterns described (such as the Hyper-V Replication provider, Azure Site Recovery provider, and Recovery Service agent) are specific to Windows/Hyper-V. No mention is made of Linux-based hypervisors or how to perform similar migrations from Linux environments.
Recommendations
- Include parallel documentation or clear links for migrating from Linux-based hypervisors (e.g., KVM, Xen, or VMware on Linux) to Azure using Private Link.
- Where possible, provide cross-platform examples or clarify which steps/tools are Windows-specific and offer Linux alternatives if available.
- Explicitly state the scope of the documentation at the beginning, clarifying that it is for Hyper-V/Windows environments, and direct users to Linux migration resources if their scenario differs.
- If agent-based migration is supported for Linux VMs, provide a section or references on how to use it with Private Link.
- Review terminology and instructions to ensure they do not assume a Windows-only audience unless truly unavoidable.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/least-privilege-credentials.md
...b/main/articles/migrate/least-privilege-credentials.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Windows tools, file paths, and patterns (e.g., %ProgramFiles%, .exe utilities, Windows/Domain Account authentication). There are no examples or instructions for Linux environments, and the steps assume a Windows-based Azure Migrate appliance and SQL Server setup. Linux equivalents for discovery, authentication, or account provisioning are not mentioned or provided.
Recommendations
- Add instructions and examples for provisioning least privileged accounts on SQL Server instances running on Linux, including relevant command-line utilities and file paths.
- Clarify whether the Azure Migrate appliance and its utilities are supported on Linux, and if not, explicitly state this limitation.
- If possible, provide cross-platform tools or scripts (e.g., PowerShell Core, Bash scripts) that work on both Windows and Linux environments.
- Include authentication and account creation steps for Linux-based SQL Server deployments, referencing Linux user management and SQL authentication.
- Rephrase steps and notes to avoid assuming a Windows-only environment (e.g., replace %ProgramFiles% with a platform-agnostic description or provide both Windows and Linux paths).
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 connection instructions before Linux, referencing Windows tools (such as Windows Firewall and RDP) in detail, and providing more granular steps for Windows than for Linux. There is also a lack of parity in example depth and troubleshooting guidance for Linux systems, and some features (like Multipath IO) are only mentioned as supported for Windows servers.
Recommendations
- Present Linux and Windows instructions in parallel or in separate, equally detailed sections, rather than listing Windows first.
- Expand Linux-specific guidance for post-migration connectivity, including common troubleshooting steps, firewall configuration examples (e.g., using ufw, firewalld, or iptables), and SSH hardening tips.
- Where Windows tools or patterns are mentioned (e.g., Windows Firewall, RDP), provide equivalent Linux commands or tools (e.g., SSH, firewall-cmd, ufw).
- Clarify support for advanced Linux features (e.g., multipath IO, encrypted disks, SELinux/AppArmor) to match the detail given for Windows features.
- Add explicit Linux command-line examples for agent installation, service checks, and post-migration validation.
- Review all feature support tables to ensure Linux and Windows are treated with equal specificity and prominence.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/migrate-appliance.md
...e-docs/blob/main/articles/migrate/migrate-appliance.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Powershell Heavy
Windows Tools
Summary
The documentation for the Azure Migrate appliance demonstrates a strong Windows bias. All deployment and management instructions assume or require Windows Server as the host OS, with no mention of Linux-based appliance deployment or Linux-native tooling. PowerShell scripts are the only supported/manual deployment method, and all configuration, update, and troubleshooting steps reference Windows tools (e.g., Registry Editor, Control Panel, MSI installers). Even in scenarios where Linux servers are discovered, the appliance itself must run on Windows, and Linux admin workflows are not addressed.
Recommendations
- Provide parity by supporting and documenting deployment of the Azure Migrate appliance on Linux-based hosts (e.g., Ubuntu, RHEL) where feasible.
- Include Linux-native deployment instructions (e.g., bash scripts, systemd services) alongside PowerShell/Windows instructions.
- Document how to manage, update, and troubleshoot the appliance using Linux tools (e.g., systemctl, journalctl, dpkg/rpm) if/when Linux support is available.
- If Windows-only deployment is a technical limitation, clearly state this early in the documentation and provide guidance or alternatives for Linux-centric environments.
- For discovery and management of Linux servers, provide examples and best practices from a Linux admin perspective (e.g., SSH key management, required Linux packages, SELinux/AppArmor considerations).
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 and tools. Examples and migration scenarios focus on VMware, Hyper-V, and Windows-hosted web apps (e.g., ASP.NET), with no explicit mention of Linux servers, Linux web apps, or Linux-specific migration considerations. The tools and migration assistants highlighted are primarily designed for Windows environments, and there is a lack of parity in Linux guidance or examples.
Recommendations
- Add explicit examples and guidance for migrating Linux servers (both physical and virtual) to Azure, including supported distributions and any unique considerations.
- Include Linux web app migration scenarios (e.g., Apache, Nginx, Java, Node.js) alongside Windows/ASP.NET examples.
- Mention Linux-compatible tools and provide parity in tool descriptions (e.g., clarify if Data Migration Assistant, App Service Migration Assistant, etc., support Linux workloads).
- Ensure that migration steps, troubleshooting, and assessment guidance are not Windows-centric and address cross-platform needs.
- Where Windows-specific tools or patterns are mentioned, provide Linux equivalents or alternatives, and present both platforms equally in tables and lists.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/migrate-support-matrix-physical.md
...in/articles/migrate/migrate-support-matrix-physical.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows-first bias in several areas: Windows server requirements and permissions are described before Linux, with more detailed steps and troubleshooting. PowerShell remoting and Windows-specific tools (WMI, WinRM, domain accounts) are emphasized, and setup scripts for the Azure Migrate appliance are provided only as PowerShell scripts. SQL Server discovery is only supported on Windows, with no Linux support or examples. Web app discovery for ASP.NET is Windows-only, while Linux support is limited and less detailed. Linux instructions are present but often less detailed, with some advanced permission setups but lacking parity in troubleshooting and examples.
Recommendations
- Provide Linux setup scripts (e.g., Bash) for appliance deployment, not just PowerShell.
- Present Linux and Windows instructions in parallel, giving equal detail and order.
- Add troubleshooting steps and permission configuration examples for Linux, matching the depth given to Windows (e.g., UAC/WMI troubleshooting equivalents for Linux sudo/capabilities).
- Clarify feature parity: explicitly state when features are Windows-only and provide roadmaps or alternatives for Linux (e.g., SQL Server discovery on Linux).
- Include Linux examples for web app discovery (e.g., Apache/Nginx/PHP), not just Tomcat, and provide more detailed steps for supported Linux scenarios.
- Where possible, avoid assuming domain environments or Windows authentication as the default; provide equivalent Linux authentication and access patterns.
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 exhibits a Windows bias in several areas: Windows tools and technologies (such as PowerShell and WMI) are mentioned more prominently and in greater detail than their Linux counterparts. Some features (notably SQL Server and ASP.NET web app discovery) are supported only on Windows, with Linux support either absent or limited. Example scripts and configuration details are provided exclusively for Windows environments (e.g., SQL Server login creation), with no equivalent Linux database examples. Windows-specific requirements (like PowerShell and WMI) are detailed, while Linux requirements are less emphasized or missing. In some sections, Windows is listed before Linux, reinforcing the bias.
Recommendations
- Provide parity in examples and instructions for Linux environments. For example, include sample scripts or guidance for discovering and assessing Linux-based databases (such as MySQL, PostgreSQL) if supported, or clearly state the lack of support.
- Where Windows tools (e.g., PowerShell, WMI) are mentioned, also specify the required Linux tools (e.g., Bash, SSH, relevant utilities) with equal detail.
- In tables and lists, alternate or randomize the order of Windows and Linux to avoid always listing Windows first.
- For features not supported on Linux (e.g., SQL Server instance discovery), explicitly state this and, if possible, provide a roadmap or alternatives for Linux users.
- Expand Linux-specific troubleshooting, credential, and permission guidance (e.g., provide sudo configuration examples, explain required Linux capabilities, and offer sample commands).
- For web app discovery, provide more detail and examples for supported Linux stacks (e.g., Tomcat), and clarify any limitations or workarounds for unsupported scenarios.
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. All operating system requirements, installation instructions, and examples are exclusively for Windows Server (2016/2012 R2). There is no mention of Linux support, Linux-based deployment, or Linux-specific instructions. Tools and paths (e.g., C:\Temp\ASRSetup, .msi installers) are Windows-specific, and there are no Linux equivalents or alternatives provided. The documentation assumes the appliance will always run on Windows, even when deployed on physical hardware.
Recommendations
- Explicitly state whether Linux-based replication appliances are supported or not. If not supported, clarify this early in the documentation.
- If Linux is supported, provide equivalent instructions for deploying and configuring the appliance on Linux (supported distributions, package requirements, installation steps, service management, etc.).
- Include Linux-specific examples for MySQL installation (e.g., using apt, yum, or tarballs), file paths, and permissions.
- Mention Linux-compatible tools and commands where appropriate, or provide cross-platform alternatives.
- If only Windows is supported, add a rationale for this limitation and guidance for Linux-only environments.
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 frequently mentioning Windows-specific tools (such as WinRM and PowerShell) before their Linux equivalents, providing detailed instructions for Windows (e.g., running 'winrm qc'), and referencing Windows authentication and permissions patterns. Linux instructions are present but are often less detailed, and Linux-specific tools or commands are not equally emphasized. There are also references to adding IPs to WinRM TrustedHosts and using PowerShell for service principal creation, with no equivalent Linux command-line examples. Linux authentication methods are mentioned but not demonstrated with examples.
Recommendations
- Provide Linux command-line examples (e.g., using SSH or shell commands) wherever Windows/PowerShell commands are given.
- When referencing prerequisites or steps, alternate the order or provide parallel instructions for Windows and Linux, rather than listing Windows first.
- Include Linux-specific troubleshooting steps and error codes, not just Windows/WinRM-centric ones.
- Where PowerShell or WinRM is referenced, add equivalent Linux commands or clarify the Linux process (e.g., how to enable SSH, how to check root permissions).
- For service principal creation, include Azure CLI examples for Linux alongside PowerShell/portal instructions.
- Clarify any differences in agent installation or onboarding process between Windows and Linux, and provide explicit steps for both.
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 demonstrates a clear Windows bias. Windows tools and patterns (such as PowerShell remoting, WMI, and WinRM) are mentioned first and in detail, with Linux alternatives only briefly described. PowerShell is required for many operations, and all code samples for SQL Server discovery are Windows-centric, with no Linux-specific examples or guidance. Some features (like SQL Server discovery and ASP.NET web app discovery) are not supported on Linux at all. Where Linux is supported, requirements are listed after Windows, and Linux instructions are less detailed.
Recommendations
- Provide Linux-first or at least Linux-parity examples and instructions, especially for common operations such as enabling required services, configuring permissions, and troubleshooting.
- Include sample scripts or command lines for Linux environments where possible (e.g., for setting up SSH, required user permissions, or package installation).
- Where features are not supported on Linux, clearly state this early and provide a roadmap or alternatives if possible.
- Balance the order of presentation: alternate or parallelize Windows and Linux requirements, rather than always listing Windows first.
- Expand Linux troubleshooting and configuration sections to match the depth provided for Windows.
- For SQL Server discovery, clarify the lack of Linux support and, if/when support is planned, provide guidance or workarounds.
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 operating systems and tools (such as Windows Firewall, RDP, and .NET Framework) are mentioned first or exclusively in several sections, while Linux-specific instructions are less detailed or provided after Windows ones. There are also references to Windows-centric URLs and services (e.g., time.windows.com, backup.windowsazure.com) and a lack of parity in troubleshooting or preparation steps for Linux VMs compared to Windows VMs.
Recommendations
- Provide Linux-first or parallel Linux examples and instructions alongside Windows ones, especially in sections about firewall configuration, remote access, and VM preparation.
- Include Linux equivalents for all Windows tools and patterns mentioned (e.g., suggest using firewalld/iptables/ufw for Linux firewall configuration, and SSH for remote access).
- List Linux operating systems and requirements before or alongside Windows ones in tables and support matrices.
- Offer detailed, step-by-step Linux preparation and troubleshooting guidance, matching the detail given for Windows (e.g., how to enable SSH, check firewall rules, and verify disk/partition layout).
- Reference Linux time synchronization options (e.g., chrony, ntpd) alongside Windows time services.
- Where URLs or services are Windows-specific, clarify Linux alternatives or note cross-platform applicability.