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 426-450 of 918 flagged pages
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 demonstrates a Windows bias in several ways: Windows-specific tools and utilities (e.g., SetupDiag, registry policies) are mentioned exclusively or before Linux equivalents; PowerShell is the only scripting method described for appliance setup, with no Linux shell or automation alternatives; examples and screenshots reference Windows Server as the default environment for the replication appliance; and troubleshooting and upgrade steps focus on Windows OS, with limited or no Linux-specific guidance. Linux is referenced in credential requirements and some OS support statements, but practical instructions, examples, and troubleshooting for Linux environments are largely missing.
Recommendations
- Provide equivalent Linux shell (bash) instructions for appliance setup and agent installation, alongside PowerShell.
- Include Linux-specific troubleshooting steps, especially for agent installation, connectivity, and migration failures.
- Add examples and screenshots showing the process on Linux-based replication appliances, not just Windows Server.
- Mention and link to Linux migration limitations, known issues, and post-migration best practices (e.g., SELinux, systemd, kernel compatibility).
- Balance references to Windows tools/utilities (e.g., SetupDiag, registry policies) with Linux equivalents (e.g., log files, systemctl, dmesg).
- Ensure upgrade and activation steps include Linux OS upgrade paths and validation, not just Windows Server.
Create Pull Request
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
Powershell Heavy
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation demonstrates a Windows bias in several ways: all command-line examples for monitoring and managing migration use PowerShell, with no mention or examples for Linux CLI (such as Azure CLI or Bash). Windows terminology and tools (e.g., Windows PowerShell, SetupDiag, Windows Server OS upgrade) are referenced exclusively or before Linux equivalents. There are no Linux-specific instructions or parity in troubleshooting, monitoring, or automation steps. While Linux is mentioned in passing (e.g., VM agent installation), actionable guidance and examples are Windows-centric.
Recommendations
- Provide equivalent Azure CLI (az) or Bash examples for all PowerShell commands, especially for monitoring migration status and troubleshooting.
- Explicitly state that all migration and monitoring steps can be performed from Linux/macOS environments, and provide instructions for doing so.
- When referencing tools like SetupDiag or OS upgrades, clarify Linux alternatives or note when steps are Windows-specific.
- Ensure troubleshooting and post-migration steps include Linux-specific guidance (e.g., activation, agent installation, post-migration validation).
- Where possible, present cross-platform instructions together, or alternate the order in which Windows and Linux steps are presented.
- Add notes or links to Linux documentation for any referenced tools or processes that are Windows-only.
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
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation for Azure Migrate shows a moderate Windows bias. Windows-specific features (such as Windows Server redeployment, Windows OS upgrade, and Windows licensing/ESU savings) are highlighted prominently and frequently. PowerShell is often mentioned as the automation tool for migration tasks, with little or no mention of Linux-native alternatives. Windows tools and patterns (e.g., IIS, SCOM, PowerShell scripts) are referenced more often and sometimes before Linux equivalents. Linux support is mentioned, but Linux-specific examples, tools, or automation patterns are sparse or absent, and Windows scenarios are often described first or in greater detail.
Recommendations
- Add Linux-specific migration examples and walkthroughs (e.g., using Bash, Ansible, or native Linux tools) alongside PowerShell examples.
- Ensure parity in feature descriptions by explicitly mentioning Linux support and providing equivalent details for Linux scenarios (e.g., disk encryption, OS upgrades, agent installation).
- Highlight Linux migration benefits and scenarios (such as SELinux, systemd, or popular Linux distributions) with the same prominence as Windows features.
- Include references to Linux-native automation and orchestration tools (e.g., shell scripts, cloud-init, Ansible) in migration workflows.
- Where PowerShell is mentioned, also provide Bash or cross-platform CLI alternatives.
- Balance the order of presentation so that Linux and Windows scenarios are described together, rather than Windows-first.
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
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a strong Windows bias. All setup instructions, scripts, and tooling are targeted exclusively at Windows Server environments. Only PowerShell scripts are provided, and all examples, command-line instructions, and validation steps use Windows-specific tools (e.g., CertUtil, PowerShell, Windows roles like IIS). There is no mention of Linux-based deployment, nor are there any Bash or cross-platform alternatives. The appliance is required to run on Windows Server 2019/2022, and Linux users are not provided with equivalent guidance or support.
Recommendations
- Provide equivalent instructions and scripts for deploying the Azure Migrate appliance on supported Linux distributions, if possible.
- Include Bash or shell script alternatives for key steps such as installer execution, hash validation, and configuration.
- Mention Linux compatibility (or lack thereof) explicitly in the prerequisites, and provide guidance for Linux-only environments.
- If the appliance is Windows-only by design, clarify this early and suggest workarounds or alternatives for Linux users.
- Offer examples using Linux-native tools (e.g., sha256sum for hash validation) alongside Windows tools.
- Document any limitations or roadmap for Linux support to set user expectations.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/discovered-metadata.md
...docs/blob/main/articles/migrate/discovered-metadata.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: Windows examples, tools, and PowerShell cmdlets are often listed before Linux equivalents, and in some sections (such as ASP.NET, Java, and Spring Boot web app data), only Windows server discovery is described. There is heavy reliance on Windows-specific tools (WMI, PowerShell, Registry, etc.), and more detailed breakdowns for Windows features compared to Linux. Linux examples, while present, are sometimes less detailed or appear after Windows content.
Recommendations
- Ensure Linux and Windows sections are presented with equal prominence and detail, possibly by interleaving or parallelizing their presentation.
- Where Windows-specific tools (e.g., PowerShell, WMI) are mentioned, provide equivalent Linux commands or tools alongside, not just after.
- For sections like ASP.NET, Java, and Spring Boot web app data, clarify if Linux discovery is supported, and if so, provide Linux-specific details/examples. If not supported, explicitly state this.
- Balance the level of detail in Linux sections to match that of Windows, especially for software inventory, feature data, and storage metadata.
- Avoid using only Windows-centric terminology (e.g., 'cmdlet', 'WMI class') without Linux equivalents (e.g., 'command', 'proc file', 'systemd unit').
- In tables, present Windows and Linux data side by side where possible, rather than in separate, sequential sections.
- Review related content and links to ensure Linux scenarios are equally represented.
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
Powershell Heavy
Windows Tools
Summary
The documentation demonstrates a strong Windows bias: all deployment and configuration steps for the Azure Migrate scale-out appliance are exclusively described for Windows Server environments. Only PowerShell scripts and Windows command-line tools (e.g., CertUtil) are provided, with no mention of Linux-based deployment, tools, or equivalent commands. The appliance is required to run on Windows Server 2019/2022, and all examples, screenshots, and troubleshooting steps assume a Windows environment. There is no guidance for Linux users or for deploying the appliance on a Linux server.
Recommendations
- Provide explicit information about whether Linux-based deployment of the Azure Migrate appliance is supported. If not, state this clearly at the beginning of the documentation.
- If Linux deployment is supported, add parallel instructions, scripts, and examples for Linux environments (e.g., Bash scripts, Linux command-line equivalents for checksum validation such as sha256sum).
- Include guidance on how to perform prerequisite checks, appliance installation, and configuration on Linux servers if supported.
- Mention any limitations or differences in functionality between Windows and Linux deployments, if applicable.
- If only Windows is supported, consider providing rationale and possible workarounds for Linux-only environments.
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 detailed instructions for setting up the Azure Migrate appliance using a PowerShell script on Windows Server, but does not offer an equivalent Linux-based setup method. The installation path for required tools (e.g., VDDK) is specified using Windows file paths only. Windows authentication mechanisms and tools (such as PowerShell and Active Directory) are described in detail, while Linux alternatives are mentioned but not elaborated upon or exemplified. There are no Linux shell or command-line examples, and the documentation often lists Windows steps or tools before mentioning Linux support or alternatives.
Recommendations
- Provide a Linux-based method for setting up the Azure Migrate appliance, such as a shell script or instructions for deploying on a Linux VM, alongside the PowerShell/Windows Server method.
- Include Linux file paths and installation instructions for required components like the VDDK, not just Windows paths.
- Offer Linux command-line examples (e.g., using SSH, scp, or Linux-based configuration steps) wherever Windows/PowerShell examples are given.
- Ensure that Linux authentication mechanisms (such as SSH key-based authentication) are described with equal detail and step-by-step guidance as Windows authentication.
- List Linux and Windows options together, or alternate which is presented first, to avoid always prioritizing Windows.
- Clarify any limitations or differences in feature support between Windows and Linux, and provide workarounds or alternatives where possible.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/discover-and-assess-using-private-endpoints.md
...migrate/discover-and-assess-using-private-endpoints.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a strong Windows bias. All command-line and script examples use Windows tools (CertUtil, PowerShell), and all file paths and instructions assume a Windows environment. There are no Linux or cross-platform examples for verifying file hashes, running the installer, or managing the appliance. The documentation references Windows-specific tools and patterns (e.g., .ps1 scripts, C:\ paths, administrator command window) and does not mention or provide alternatives for Linux users.
Recommendations
- Provide equivalent Linux/bash commands for verifying file hashes (e.g., sha256sum).
- Include instructions for running the installer script on Linux-based hosts, if supported, or clarify platform support.
- Offer examples using Linux shell (bash) for script execution and file extraction.
- Document the location of log files and configuration steps for Linux-based appliances, if applicable.
- Explicitly state platform requirements and, if Windows-only, clearly indicate this early in the documentation.
- If the appliance supports Linux, ensure parity in screenshots and step-by-step instructions for both platforms.
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 demonstrates a Windows bias by prioritizing and exclusively providing Windows-based tools and instructions. PowerShell is the only script-based installer mentioned, and all command-line examples (such as hash verification) use Windows Command Prompt tools (CertUtil). File paths and instructions for installing dependencies (like VDDK) assume a Windows environment. There are no Linux equivalents or examples, and Linux-based deployment or verification methods are not discussed.
Recommendations
- Provide equivalent Linux-based instructions for all command-line operations, such as verifying OVA file hashes (e.g., using sha256sum).
- Include guidance for running the appliance installer script on Linux systems, if supported, or clarify platform limitations.
- Mention Linux file paths and installation steps for dependencies like VDDK, or explicitly state if only Windows is supported.
- Ensure that examples and screenshots reflect both Windows and Linux environments where possible.
- If PowerShell is the only supported installer, clearly state this limitation and provide rationale or alternatives for Linux users.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/discovered-metadata.md
...docs/blob/main/articles/migrate/discovered-metadata.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 metadata, tools, and PowerShell cmdlets are consistently presented first and in greater detail than Linux equivalents. Windows-specific tools (WMI, PowerShell, Registry, Get-WindowsFeature, etc.) are referenced throughout, while Linux examples, though present, are often grouped together and sometimes less detailed. Some sections (e.g., ASP.NET, Java, Spring Boot web app data) only mention Windows servers, omitting Linux scenarios. The documentation also uses Windows-centric terminology and patterns, and Linux parity is sometimes lacking in both depth and breadth.
Recommendations
- Present Linux and Windows examples side-by-side or in parallel tables/sections to ensure equal visibility.
- Where Windows PowerShell cmdlets or WMI classes are listed, provide equivalent Linux commands or tools (e.g., systemctl, lsof, etc.) where possible.
- Expand Linux sections to match the detail provided for Windows, especially for application and web server discovery (e.g., include Apache, NGINX, Tomcat on Linux).
- Explicitly state when a feature or data point is only available for Windows, and clarify Linux support status.
- Include Linux-specific application and feature discovery (e.g., systemd services, package managers, web servers) in the same detail as Windows features.
- Review and update sections like ASP.NET, Java, and Spring Boot web app data to include Linux scenarios or clarify if not supported.
- Avoid always listing Windows first; alternate order or use neutral grouping (e.g., 'On Windows:' / 'On Linux:').
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/troubleshoot-appliance.md
...s/blob/main/articles/migrate/troubleshoot-appliance.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows bias in several ways: troubleshooting steps and examples often reference Windows tools and commands first or exclusively (e.g., Control Panel, admin command prompt, PowerShell, Notepad, Windows file paths), and remediation steps for Windows are more detailed than for Linux. In some cases, Linux guidance is present but less prominent or appears after Windows instructions. There are also sections where only Windows-specific tools or patterns are mentioned, and Linux equivalents are missing or less detailed.
Recommendations
- Ensure that for every Windows-specific troubleshooting step (e.g., using Control Panel, PowerShell, Notepad, Windows file paths), an equivalent Linux step is provided, with equal detail and prominence.
- Where both Windows and Linux are supported, use parallel tabbed sections or side-by-side examples for commands and file locations.
- Avoid using Windows-first language (e.g., 'Open Notepad as an admin' or referencing C:\ paths) without providing the Linux equivalent (e.g., 'Open your preferred text editor as root' and '/etc/hosts').
- For sections that reference Windows tools (e.g., WMI, WinRM, Control Panel), include Linux equivalents (e.g., SSH, systemd, chrony/ntpd for time sync) and troubleshooting steps.
- When providing code samples, ensure both PowerShell and Bash/SSH examples are present where applicable.
- Review the order of presentation so that Linux and Windows are treated with parity, either by alternating order or using tabs, rather than always listing Windows first.
- Expand Linux troubleshooting guidance to match the depth and clarity of Windows instructions, especially for common issues like connectivity, authentication, and service management.
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
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation demonstrates a Windows bias in several areas: Windows tools and technologies (such as PowerShell and WMI) are mentioned as requirements, often without equivalent Linux details or alternatives. SQL Server discovery and web app discovery are supported only or primarily for Windows, with Linux support either missing or limited. Example scripts and configuration steps are provided only for Windows authentication scenarios, with no Linux-specific examples. Windows requirements and tools are often listed before Linux equivalents, and some features (like SQL Server discovery) are not supported for Linux at all.
Recommendations
- Provide equivalent Linux examples and instructions wherever Windows-specific tools or scripts are mentioned (e.g., sample scripts for Linux authentication and permissions).
- When listing requirements or supported OSes, alternate the order or group Windows and Linux together to avoid always listing Windows first.
- Expand support for Linux workloads where possible (e.g., SQL Server on Linux, web app discovery for Linux-based stacks). If not supported, clearly state the roadmap or alternatives.
- Where Windows tools (PowerShell, WMI) are required, specify the Linux equivalents (e.g., Bash, SSH, relevant Linux management tools) and provide configuration guidance.
- Ensure that all features and workflows are documented for both Windows and Linux, or clearly indicate any limitations or differences in parity.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/create-web-app-assessment.md
...lob/main/articles/migrate/create-web-app-assessment.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias primarily in the 'Next steps' section, where optimization and best practices links are exclusively for Windows Dockerfiles and Windows containers. There are no equivalent references or guidance for Linux-based web apps or Dockerfiles, despite Linux being a common platform for web applications and AKS workloads. No Linux-specific tools, patterns, or examples are provided throughout the tutorial.
Recommendations
- Include parallel links and guidance for optimizing Linux Dockerfiles and Linux container best practices in the 'Next steps' section.
- Reference both Windows and Linux container management documentation when discussing AKS or App Service deployment scenarios.
- Add explicit examples or notes for Linux-based web apps where applicable, ensuring parity in instructions and recommendations.
- Where Windows-specific terms or tools are mentioned, provide Linux equivalents (e.g., Dockerfile optimization for Linux, Linux-based VM/app discovery).
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/migrate-hyper-v-servers-to-azure-using-private-link.md
...ttps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/migrate-hyper-v-servers-to-azure-using-private-link.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation is heavily focused on migrating Hyper-V (a Windows-centric hypervisor) servers to Azure, with all examples, terminology, and tooling specific to Windows environments. There are no Linux or cross-platform migration instructions, examples, or tool references. The documentation assumes the use of Windows-based tools and patterns (e.g., Hyper-V Replication provider, Recovery Services agent), and does not mention or provide parity for Linux-based hypervisors or environments.
Recommendations
- Add equivalent migration documentation for Linux-based hypervisors (e.g., KVM, Xen, or VMware on Linux) to ensure parity.
- Include Linux-specific instructions or notes where applicable, such as DNS configuration, network connectivity verification, and agent installation.
- If the migration tooling supports Linux VMs or appliances, provide explicit examples and screenshots for Linux environments.
- Reference or link to documentation for migrating Linux VMs or workloads to Azure, even if on a separate page, to guide non-Windows users.
- Clarify in the introduction that this guide is specific to Hyper-V/Windows, and provide navigation to Linux migration resources.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/how-to-create-sql-assessment.md
.../main/articles/migrate/how-to-create-sql-assessment.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates Windows bias by referencing Windows-specific tools and best practices (such as optimizing Windows Dockerfiles) in the 'Next steps' section, without providing equivalent Linux guidance. There are no Linux-specific examples, tools, or references, and the only optimization and best practices links are for Windows containers. No PowerShell commands are present, but the overall guidance assumes a Windows-centric environment.
Recommendations
- Include Linux-specific examples and references, such as links to optimizing Linux Dockerfiles or best practices for Linux containers on AKS.
- Provide parity in 'Next steps' by offering both Windows and Linux container guidance for AKS.
- Mention Linux tools and workflows where relevant, ensuring that Linux users are equally supported in the migration and assessment process.
- Review all referenced links and ensure that for every Windows-specific link, a Linux equivalent is also provided.
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 demonstrates a Windows bias by providing PowerShell installer script instructions as the only alternative to the OVA method, using Windows-specific tools (e.g., CertUtil in Command Prompt) for file verification, referencing Windows file paths and conventions (e.g., C:\Program Files), and focusing on Windows authentication and IIS web server for discovery. There are no Linux command examples or explicit instructions for Linux-based appliance setup, verification, or credential types, and Linux tools are not mentioned for common tasks.
Recommendations
- Provide equivalent Linux-based instructions for deploying and configuring the appliance, including using Linux shell commands for file verification (e.g., sha256sum) and Linux file paths.
- Include Linux authentication and web server (e.g., Apache, Nginx) discovery examples and clarify support for Linux-based workloads.
- When referencing credential types, give Linux examples and clarify any differences in required permissions or setup steps.
- Where PowerShell or Windows tools are mentioned, offer side-by-side Linux alternatives.
- Avoid using Windows paths and tools exclusively; use cross-platform language or provide both Windows and Linux variants.
- Explicitly state if certain features are Windows-only, and provide guidance for Linux users where possible.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/concepts-migration-planning.md
...b/main/articles/migrate/concepts-migration-planning.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by prioritizing Windows Server scenarios, mentioning Windows-specific tools and upgrade paths, and omitting explicit Linux migration or upgrade examples. Windows Server end-of-support and upgrade processes are highlighted, while Linux equivalents are not discussed. There are no Linux-specific migration blockers, readiness checks, or tooling references, and no examples or guidance for Linux workloads are provided.
Recommendations
- Include explicit examples and guidance for migrating Linux servers, such as common distributions (Ubuntu, CentOS, RHEL) and their unique considerations.
- Add parity for Linux OS upgrades during migration, or clarify if such a feature is not available, and provide recommended upgrade paths for Linux workloads.
- Mention Linux-specific migration blockers, readiness checks, and compatibility issues alongside Windows ones.
- Reference Linux tools and patterns (e.g., shell scripts, Linux VM extensions) where Windows tools (like Custom Script Extension for Windows) are mentioned.
- Ensure that all tables and recommendations (such as end-of-support OS, quick wins, etc.) include Linux operating systems and scenarios.
- Balance the focus between Windows and Linux in all sections, especially in migration, assessment, and optimization guidance.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/how-to-automate-migration.md
...lob/main/articles/migrate/how-to-automate-migration.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a strong Windows bias by exclusively referencing PowerShell scripts and the Azure PowerShell module for automating VMware migrations. All example commands, script names, and installation instructions are PowerShell-centric, with no mention of Bash, Azure CLI, or cross-platform alternatives. There is no guidance for Linux or macOS users, nor any indication of how to run these automations outside a Windows/PowerShell environment.
Recommendations
- Provide equivalent Bash or Azure CLI scripts for Linux/macOS users, or clarify if such alternatives are not available.
- Explicitly state the platform requirements for the scripts (e.g., Windows, Linux, macOS) and, if possible, provide instructions for running PowerShell Core on Linux/macOS.
- Include installation and usage instructions for Azure PowerShell on Linux/macOS, or reference cross-platform documentation.
- If PowerShell is required, clarify whether PowerShell Core (pwsh) is supported and provide examples using cross-platform syntax.
- Mention and, if possible, provide links to any available REST API or SDK alternatives for users who wish to automate migrations without PowerShell.
- Add a section addressing common Linux/macOS user scenarios, such as running scripts in containers or using Azure Cloud Shell.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/migrate-vmware-servers-to-azure-using-private-link.md
...https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/migrate-vmware-servers-to-azure-using-private-link.md
High Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows Tools
Windows First
Summary
The documentation page demonstrates a bias toward Windows environments. It references Windows Server and Software Assurance in the Azure Hybrid Benefit section, and suggests editing the 'hosts file' on the Azure Migrate appliance without clarifying the process for Linux-based appliances. There are no explicit Linux command-line examples or references to Linux tools, and the documentation assumes familiarity with Windows-centric concepts and patterns.
Recommendations
- Provide explicit instructions for both Windows and Linux-based Azure Migrate appliances, especially for tasks like editing the hosts file (e.g., specify the file path and command for Linux: '/etc/hosts').
- Include examples or notes for Linux environments where relevant, such as verifying DNS resolution using 'nslookup' or 'dig' on Linux.
- Clarify that the Azure Migrate appliance can be deployed on both Windows and Linux, and provide parity in operational steps for both platforms.
- When mentioning Azure Hybrid Benefit for Windows Server, also note any relevant licensing or migration considerations for Linux VMs.
- Avoid assuming the administrator is using a Windows environment; use cross-platform language and examples where possible.
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 page demonstrates a Windows bias by prioritizing Windows-centric workloads (e.g., ASP.NET web apps, SQL Server), mentioning Windows environments (such as Hyper-V and VMware with Windows web apps) without equivalent Linux examples, and referencing tools and migration scenarios that are predominantly relevant to Windows or Microsoft technologies. There is a lack of explicit mention or examples for Linux workloads, Linux-based web apps, or open-source databases, and no Linux-specific migration guidance is provided.
Recommendations
- Include explicit examples and scenarios for migrating Linux servers, Linux-based web applications, and open-source databases (e.g., MySQL, PostgreSQL) to Azure.
- Add references to Linux tools and migration patterns, such as SSH-based discovery, Linux agent installation, and migration of workloads running on Apache, NGINX, or Tomcat.
- Ensure parity in documentation by providing step-by-step guides or links for both Windows and Linux environments in all relevant sections.
- Mention Linux support and compatibility in tool descriptions (e.g., clarify if Data Migration Assistant or App Service Migration Assistant supports Linux workloads).
- Highlight Linux-specific considerations, such as handling of file systems, package management, and service management during migration.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/agent-based-migration-architecture.md
...articles/migrate/agent-based-migration-architecture.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation page exhibits Windows bias by referencing Windows-specific paths, tools, and registry keys exclusively. All examples and instructions (such as antivirus exclusions, registry edits, and MMC snap-in usage) are given only for Windows environments, with no mention of Linux equivalents or guidance for Linux-based servers. This may hinder Linux administrators from effectively using or understanding the migration process.
Recommendations
- Provide Linux-specific instructions and examples alongside Windows ones, such as file paths for antivirus exclusions (e.g., /var/lib/...), and commands for installing and managing the Mobility service on Linux.
- Include guidance for bandwidth throttling and configuration on Linux servers, such as relevant configuration files or system settings, instead of only referencing Windows registry and MMC snap-ins.
- Mention Linux tools and management patterns (e.g., systemd, CLI commands) where appropriate, and ensure parity in troubleshooting and operational guidance.
- Clearly indicate which instructions apply only to Windows and provide equivalent steps for Linux where possible.
- Add a section or table summarizing differences and requirements for both Windows and Linux server migrations.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/create-project.md
...zure-docs/blob/main/articles/migrate/create-project.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by providing command-line instructions specifically for PowerShell, explicitly instructing users to open PowerShell as Administrator, and omitting equivalent instructions for Linux or macOS environments. All CLI examples assume a Windows context, and there are no references to Linux shells or cross-platform usage, despite the Azure CLI being available on multiple platforms.
Recommendations
- Provide equivalent command-line instructions for Linux and macOS users, including shell-agnostic commands or explicit bash/zsh examples.
- Avoid specifying 'open PowerShell as Administrator' as the only method; instead, mention that commands can be run in any terminal where Azure CLI is installed (e.g., PowerShell, Command Prompt, Bash).
- Add notes or callouts clarifying that Azure CLI commands are cross-platform and provide any necessary adjustments for Linux/macOS environments (e.g., use of sudo, differences in environment variables).
- Include screenshots or instructions for non-Windows environments where relevant, or at least acknowledge their usage.
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 demonstrates a Windows bias by exclusively referencing Windows-based SQL Server deployments and migration targets, such as SQL Server on Azure VM (with Windows), and by linking only to Windows-specific best practices and guidelines. There are no examples, guidance, or references for Linux-based SQL Server deployments or migrations, nor are Linux tools or patterns mentioned. This may leave Linux users without clear guidance for their scenarios.
Recommendations
- Include explicit references and guidance for SQL Server on Linux, both on-premises and as an Azure VM target.
- Provide links to best practices and performance guidelines for SQL Server on Linux VMs in Azure (e.g., https://learn.microsoft.com/azure/azure-sql/virtual-machines/linux/).
- Add examples and remediation guidance relevant to Linux-based SQL Server deployments, such as file system considerations, disk layout, and supported features.
- Clarify in all relevant sections that both Windows and Linux SQL Server sources and targets are supported, and highlight any differences in assessment or migration steps.
- Wherever a link or example is provided for Windows, provide a Linux equivalent in parallel.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/concepts-assessment-calculation.md
...in/articles/migrate/concepts-assessment-calculation.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Heavy
Missing Linux Example
Summary
The documentation page demonstrates a Windows-first and Windows-heavy bias. Throughout the assessment logic, Windows operating systems are listed first and in greater detail, with explicit version-by-version breakdowns, while Linux is referenced generically or as a single row. No Linux-specific examples, screenshots, or troubleshooting guidance are provided. The guidance for discovering Linux kernel versions is indirect and requires extra steps. There are no Linux command-line or tool references, and the documentation assumes familiarity with Windows environments.
Recommendations
- Provide Linux-specific examples and scenarios, such as how to assess readiness for common Linux distributions, including troubleshooting steps for Linux VMs.
- Include Linux command-line examples (e.g., how to collect performance data or check OS/kernel versions) alongside or before Windows/Powershell equivalents.
- Expand the 'Guest operating system' section to list major Linux distributions and versions explicitly, similar to the Windows breakdown.
- Offer guidance for Linux-specific issues (e.g., kernel modules, disk partitioning, network configuration) that may affect migration readiness.
- Ensure parity in detail and prominence for Linux and Windows throughout the documentation, including in tables, notes, and examples.
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
Powershell Heavy
Windows Tools
Summary
The documentation demonstrates a strong Windows bias. All setup instructions, installer scripts, and validation steps are explicitly designed for Windows Server environments. Only PowerShell scripts and Windows command-line tools (such as CertUtil) are provided, with no mention of Linux-based alternatives or support. The appliance is required to run on Windows Server 2019/2022, and all examples, screenshots, and troubleshooting steps assume a Windows environment. There are no instructions or parity for Linux-based deployments or administration.
Recommendations
- Provide equivalent instructions and supported tooling for deploying the scale-out appliance on Linux-based servers, if supported.
- Include Linux shell (bash) commands for tasks such as checksum validation (e.g., using sha256sum) alongside Windows examples.
- Offer Linux-compatible installer scripts or clarify if the appliance is Windows-only, and explicitly state the lack of Linux support if so.
- If Linux is not supported, add a clear note early in the documentation stating that only Windows Server is supported for the appliance, and consider providing a roadmap or alternatives for Linux users.
- Where PowerShell is used, provide bash or shell script equivalents if Linux support is available.
- Ensure that troubleshooting and log file paths are described in a cross-platform manner, or clarify their Windows-specific nature.