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 251-275 of 918 flagged pages
Migrate https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/concepts-azure-webapps-assessment-calculation.md ...grate/concepts-azure-webapps-assessment-calculation.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by focusing primarily on ASP.NET web apps running on IIS servers, with no explicit mention of Linux-based web servers (e.g., Apache, Nginx) or Linux hosting patterns. Examples and assessment flows are described for ASP.NET/IIS and Java/Tomcat, but there is no guidance for Java apps running on Linux servers, nor for other common Linux-based web stacks. The referenced pricing page is for 'App Service (Windows)', and there are no Linux-specific migration considerations or examples. Windows tools and environments (IIS, ASP.NET) are mentioned first and exclusively.
Recommendations
  • Add explicit examples and guidance for assessing Linux-based web apps (e.g., Java apps on Apache/Nginx, PHP, Node.js) and their migration to Azure App Service (Linux).
  • Reference and link to the Azure App Service (Linux) pricing and documentation pages alongside Windows equivalents.
  • Clarify whether the Azure Migrate appliance supports discovery and assessment of Linux-hosted web apps, and provide instructions for such scenarios.
  • Ensure that migration assessment steps and compatibility checks cover both Windows and Linux hosting environments equally.
  • Include best practices and remediation guidance for common Linux migration issues, not just Windows/IIS.
GitHub Create Pull Request
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 →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
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 OS upgrade and Azure Hybrid Benefit for Windows licenses) before Linux equivalents, and omitting explicit Linux migration or upgrade examples. Windows tools and patterns (e.g., Custom Script Extension for Windows OS upgrade) are described in detail, while Linux migration paths and tooling are not covered or referenced.
Recommendations
  • Add explicit examples and guidance for migrating Linux servers, including common Linux distributions and their specific considerations.
  • Include details on Linux OS upgrade options during migration, or clarify if/when such features are available.
  • When describing features like Azure Hybrid Benefit, provide equal detail for Linux subscriptions and licensing.
  • Reference and link to Linux-specific documentation, such as using Custom Script Extension for Linux VMs.
  • Ensure that migration tooling and assessment examples (screenshots, export instructions) include both Windows and Linux workloads.
  • Balance the prioritization of Windows and Linux scenarios throughout the documentation, avoiding Windows-first ordering.
GitHub Create Pull Request
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 →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a bias toward Windows environments by providing command-line instructions exclusively for PowerShell, referencing 'open PowerShell as Administrator', and omitting equivalent Linux shell examples. The installation instructions for Az CLI are linked, but subsequent usage is shown only in PowerShell context. No Linux terminal or shell commands are provided, and the workflow assumes a Windows user experience.
Recommendations
  • Provide equivalent Linux shell (bash) examples alongside PowerShell commands for Az CLI usage.
  • Clarify that Az CLI can be used on both Windows and Linux, and show how to open a terminal and run commands on Linux.
  • Avoid instructions that assume Windows-specific patterns (e.g., 'open PowerShell as Administrator'); instead, use cross-platform language like 'open your terminal'.
  • Include screenshots or instructions for Linux environments where relevant.
  • Explicitly mention platform compatibility for all tools and steps.
GitHub Create Pull Request
Migrate https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/concepts-vmware-agentless-migration.md ...rticles/migrate/concepts-vmware-agentless-migration.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates Windows bias by providing only Windows-specific tooling and examples for key management tasks, such as bandwidth throttling (using PowerShell cmdlets like New-NetQosPolicy and referencing GatewayWindowsService.exe), and configuration file locations (using Windows file paths like C:\ProgramData\Microsoft Azure\Config). There are no Linux equivalents or examples, nor is there mention of how to perform these operations on Linux-based appliances, despite Azure Migrate appliances supporting Linux. Windows terminology and tools are presented exclusively and first, with no parity for Linux users.
Recommendations
  • Provide equivalent Linux instructions for bandwidth throttling, such as using tc or other Linux network QoS tools, and reference the relevant Linux service/process names.
  • Include Linux file path examples (e.g., /var/lib/azure/config) for configuration files like GatewayDataWorker.json, and clarify how to restart the gateway service on Linux.
  • Explicitly state whether the Azure Migrate appliance supports Linux, and if so, offer step-by-step guidance for both platforms in all relevant sections.
  • When referencing scripts or sample commands, offer both PowerShell and Bash/shell script versions.
  • Review all examples and operational guidance to ensure Linux users are not excluded and can achieve parity with Windows users.
GitHub Create Pull Request
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 →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by focusing primarily on ASP.NET web apps and Windows-specific migration scenarios. Examples and sizing details are provided for ASP.NET (Windows) and Java (Tomcat), but there is no mention of Linux-based web frameworks (e.g., Node.js, PHP, Python, Ruby) or Linux-specific migration considerations. The 'Next steps' section links only to Windows Dockerfile optimization, omitting Linux container guidance. There is also a lack of Linux command-line or tool references, and Windows licensing (Azure Hybrid Benefit) is discussed without Linux equivalents.
Recommendations
  • Include examples and sizing guidance for popular Linux-based web apps (Node.js, PHP, Python, Ruby, etc.) alongside ASP.NET and Java.
  • Add links and best practices for optimizing Linux Dockerfiles and containers in the 'Next steps' section.
  • Mention Linux licensing and migration considerations (e.g., bring-your-own-license, open source stack migration).
  • Provide parity in screenshots and instructions for Linux environments where applicable.
  • Reference Linux tools and command-line patterns (e.g., Bash, systemd, Apache/Nginx) in addition to Windows/Powershell.
  • Clarify that Azure App Service and AKS support both Windows and Linux workloads, and provide guidance for both.
GitHub Create Pull Request
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 →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits several types of Windows bias. Windows server examples, tools, and data collection patterns are consistently presented before Linux equivalents. Windows-specific technologies (WMI, PowerShell, Registry, Windows Features) are described in detail, often with explicit cmdlets and registry paths, while Linux sections rely on generic shell commands and sometimes lack equivalent detail or context. Some features (e.g., ASP.NET, Spring Boot, Java web app data) are described only for Windows servers, with no Linux-specific examples or parity. The documentation also uses Windows-centric terminology and tools (e.g., PowerShell, WMI, Registry) more extensively than Linux-native alternatives.
Recommendations
  • Present Linux and Windows examples side-by-side or in parallel sections to ensure parity and equal visibility.
  • Expand Linux sections to include more detailed explanations, equivalent commands, and context (e.g., for application/web app discovery, pending updates, feature data).
  • Where Windows-specific tools (PowerShell, WMI, Registry) are mentioned, provide Linux-native alternatives (e.g., systemd, journalctl, /etc, lsof, etc.) and explain their usage.
  • Add Linux-specific examples for web app discovery (e.g., Apache, Nginx, Tomcat on Linux) and clarify how Java/Spring Boot apps are discovered on Linux servers.
  • Avoid presenting Windows tools or examples first; alternate or group by platform to avoid implicit prioritization.
  • Ensure all features and metadata types described for Windows are also covered for Linux, or explicitly state if a feature is not supported on Linux.
GitHub Create Pull Request
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 →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page is heavily focused on Windows and PowerShell tooling for automating VMware migrations in Azure Migrate. All examples, instructions, and referenced scripts are exclusively PowerShell (.ps1), with no mention of Bash, Linux shell, or cross-platform alternatives. The prerequisites and installation steps assume the use of the Azure PowerShell module, and there is no guidance for users on Linux or macOS platforms. The documentation does not provide parity for Linux users or mention how to run these scripts outside of a Windows environment.
Recommendations
  • Provide equivalent Bash or cross-platform scripting examples for Linux/macOS users.
  • Document how to use Azure CLI for migration automation as an alternative to PowerShell.
  • Clarify whether the PowerShell scripts can be run on Linux/macOS using PowerShell Core, and provide installation instructions for those platforms.
  • List Linux prerequisites and environment setup steps alongside Windows instructions.
  • Add notes or sections highlighting cross-platform compatibility and limitations, if any.
  • Consider offering sample scripts in both PowerShell and Bash, or provide a wrapper for Azure CLI to achieve similar automation.
GitHub 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 →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page exhibits a Windows bias in several ways: it references Windows-specific tools and patterns (such as Cloud Witness for Windows Server Failover Clusters), links to Windows-focused best practices, and omits Linux-specific examples or guidance. Windows terminology and scenarios are presented first or exclusively, with little to no mention of Linux equivalents, especially in high availability and disaster recovery sections.
Recommendations
  • Include Linux-specific examples and instructions, such as guidance for configuring high availability and disaster recovery for SQL Server on Linux VMs in Azure.
  • Reference Linux best practices for SQL Server on Azure VMs alongside Windows-focused links.
  • Mention Linux witness options (e.g., File Share Witness, or other supported quorum configurations) where Cloud Witness is discussed.
  • Clarify licensing and Azure Hybrid Benefit applicability for Linux environments, not just Windows Server.
  • Ensure parity in migration scenarios and readiness reporting for SQL Server running on Linux, including any unique considerations or limitations.
  • Add screenshots and walkthroughs that demonstrate the process for both Windows and Linux-based SQL Server instances.
GitHub Create Pull Request
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 →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation page exhibits a Windows bias by consistently presenting Windows instructions and tools before Linux equivalents, providing more detailed steps and links for Windows (e.g., double-click installer, Configuration Manager, Intigua, PowerShell script), and referencing Windows-specific installation methods and supported operating systems. Linux instructions are more terse, lack automation examples, and are generally presented after Windows steps.
Recommendations
  • Present Linux and Windows instructions in parallel, or alternate which comes first.
  • Provide equally detailed Linux installation steps, including automation options (e.g., using Ansible, shell scripts, or package managers).
  • Include links to Linux-specific documentation and supported operating systems, similar to Windows.
  • Offer sample scripts for Linux agent installation and configuration, not just for Windows/PowerShell.
  • Mention Linux tools (e.g., systemd, cron) for agent management where Windows tools (Configuration Manager, Intigua) are referenced.
  • Ensure troubleshooting and advanced configuration guidance is available for both platforms.
GitHub Create Pull Request
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 →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example Powershell Heavy
Summary
The documentation page demonstrates a Windows bias in several ways: Windows credentials and permissions are described first and in greater detail than Linux equivalents, with explicit mention of Windows/Domain accounts and tools like SCCM, Active Directory, and File Server roles. Linux is mentioned as 'non-domain' and with less detail, and examples for Linux-specific discovery (e.g., file servers) are missing. Windows-centric tools and patterns (IIS, RDP, SCCM, Exchange Server, Active Directory) are listed before or instead of Linux alternatives. There is a lack of Linux-specific examples, especially for roles/features and file server discovery, and no Linux command-line or shell examples are provided.
Recommendations
  • Provide Linux-specific examples and instructions for credential setup, permissions, and discovery, including shell commands and configuration file references.
  • Include Linux file server discovery details (e.g., Samba, NFS) and clarify support for Linux-based file servers.
  • Balance the order and detail of Windows and Linux instructions, mentioning Linux alternatives alongside Windows tools (e.g., Samba/NFS with Windows File Server, OpenLDAP with Active Directory).
  • Add explicit Linux role/feature discovery instructions and examples, similar to the Windows 'Roles and features' tab.
  • Where Windows tools (SCCM, RDP, IIS, Exchange) are mentioned, also list Linux equivalents (e.g., Landscape, SSH, Apache/Nginx, Postfix/Dovecot) and provide parity in guidance.
GitHub Create Pull Request
Migrate https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/how-to-create-group-machine-dependencies-agentless.md ...https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/how-to-create-group-machine-dependencies-agentless.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in several ways. PowerShell is the only CLI tool provided for managing agentless dependency analysis, with all command-line examples and automation instructions using PowerShell cmdlets. Windows credential patterns and permissions are described first and in more detail than Linux equivalents. The use of Windows-centric tools (PowerShell, Power BI) is pervasive, and there are no Linux shell or cross-platform CLI examples. Linux-specific instructions are minimal and lack parity with Windows in terms of examples and troubleshooting.
Recommendations
  • Provide equivalent Linux shell (bash) or cross-platform CLI examples for all PowerShell commands, using Azure CLI or REST API where possible.
  • Document Linux credential management and permissions with the same level of detail as Windows, including troubleshooting steps and examples.
  • Mention Linux tools (e.g., jq, csvkit, or other open-source data processing utilities) for exporting and manipulating dependency data.
  • Ensure that instructions for enabling/disabling dependency analysis are platform-neutral and do not assume PowerShell is available.
  • Include screenshots or walkthroughs from Linux environments where relevant.
  • Clarify any platform-specific limitations or requirements, and offer guidance for Linux-only environments.
GitHub Create Pull Request
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 →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by primarily referencing Windows OS credentials, PowerShell requirements, and Windows-centric tools and patterns. There are no explicit Linux or cross-platform examples, and prerequisites such as PowerShell and VMware Tools are mentioned without Linux alternatives. The credential instructions and discovery steps focus on Windows domain/non-domain accounts, with no mention of Linux authentication or discovery methods.
Recommendations
  • Include explicit instructions and examples for discovering SQL Server instances on Linux servers, including authentication methods and required permissions.
  • Mention Linux equivalents for PowerShell (such as Bash scripts or Azure CLI) and clarify if the Azure Migrate appliance supports Linux-based environments for discovery.
  • Add Linux-specific prerequisites and troubleshooting steps, such as required packages or services for the appliance to function on Linux.
  • Provide sample commands or screenshots for Linux environments alongside Windows examples.
  • Clarify whether the agentless discovery process works for Linux servers and, if so, detail any differences in setup or credential requirements.
GitHub Create Pull Request
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 →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page exclusively references PowerShell scripts (.ps1), provides only PowerShell-based automation examples, and links to Azure PowerShell samples. There is no mention of Bash, shell scripts, or Linux-native tooling. The scripting workflow and prerequisites are presented from a Windows-centric perspective, implicitly assuming the user is operating in a Windows environment.
Recommendations
  • Provide equivalent Bash or shell script samples for Linux users, or clarify cross-platform compatibility of the PowerShell scripts (e.g., with PowerShell Core on Linux).
  • Include instructions for running the migration scripts on Linux and macOS, including any required dependencies or setup steps.
  • Mention and link to any Azure CLI-based alternatives for migration automation, if available.
  • Explicitly state platform requirements and limitations for the provided scripts.
  • Add examples or references to Linux-native automation tools or workflows where applicable.
GitHub Create Pull Request
Migrate https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/how-to-enable-additional-data-collection-for-arc-servers.md ...w-to-enable-additional-data-collection-for-arc-servers.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Windows Example First
Summary
The documentation generally maintains parity between Windows and Linux, providing instructions and examples for both platforms. However, there is a subtle Windows bias: Windows is consistently mentioned before Linux in lists, examples, and extension names (e.g., 'Azure Migrate Collector for Windows' is listed before '...for Linux'). The endpoint for network connectivity uses a Windows-branded domain ('migration.windowsazure.com'). In step-by-step instructions and policy creation, the Windows example or policy is presented before the Linux equivalent, reinforcing a Windows-first perspective.
Recommendations
  • Alternate the order of Windows and Linux instructions/examples throughout the documentation to avoid consistently prioritizing Windows.
  • Use neutral or platform-agnostic phrasing when listing extension names or steps (e.g., 'Azure Migrate Collector for Windows or Linux').
  • If possible, clarify that the endpoint domain ('migration.windowsazure.com') is not Windows-specific and is used for both platforms.
  • Ensure that any screenshots, code blocks, or UI references are equally balanced between Windows and Linux.
  • Consider providing a combined example or table for both platforms where appropriate, rather than separate sections.
  • Explicitly state that all features and steps apply equally to both Windows and Linux, unless there are platform-specific limitations.
GitHub Create Pull Request
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 →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by consistently referencing Windows-based SQL Server deployments, migration strategies, and best practices. It exclusively links to Windows-specific guidance (such as performance guidelines for SQL Server on Azure VMs running Windows), omits Linux-based SQL Server migration scenarios, and does not provide examples or recommendations for SQL Server on Linux or cross-platform migration tools. There are no Linux-specific instructions, nor any mention of PowerShell or CLI examples, but the overall guidance assumes a Windows environment.
Recommendations
  • Include explicit guidance and examples for migrating SQL Server instances running on Linux to Azure targets.
  • Reference and link to Azure SQL migration best practices for Linux-based VMs, not just Windows.
  • Add parity in documentation for storage and compute sizing for SQL Server on Linux VMs.
  • Mention cross-platform migration tools (such as Azure CLI, azdata, or SQL Server tools available on Linux) alongside any Windows-specific tools.
  • Clarify whether recommendations and assessment logic apply equally to SQL Server on Linux, and note any differences.
  • Provide sample migration steps or scripts for Linux environments, where applicable.
GitHub Create Pull Request
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 →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation is heavily focused on Windows environments, specifically Hyper-V, and consistently presents Windows-centric tools and patterns. PowerShell commands and Windows GUI tools (Hyper-V Manager, Local Group Policy Editor) are used exclusively for appliance setup, credential delegation, and verification steps. Examples and instructions for Linux hosts or Linux-based management tools are absent, and Windows methods are always presented first or exclusively. Linux credentials are mentioned only briefly and without procedural detail.
Recommendations
  • Add equivalent instructions and examples for Linux environments, such as how to deploy and manage the Azure Migrate appliance on Linux hosts.
  • Provide Linux command-line alternatives (e.g., using Bash, OpenSSL for hash verification) alongside PowerShell examples.
  • Include guidance for credential delegation and appliance configuration using Linux tools and patterns.
  • Clarify which steps are Windows-specific and offer Linux-specific documentation where applicable.
  • Ensure parity in screenshots and walkthroughs for Linux-based management consoles or remote access methods.
GitHub Create Pull Request
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 →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page exhibits a strong Windows bias. All setup instructions and examples use PowerShell, with no mention of Linux shell equivalents. The installer script is a PowerShell script (.ps1), and deployment steps reference Windows-specific tools and concepts (Registry Editor, Windows roles like IIS, Windows Activation Service, PowerShell ISE). There is no guidance for Linux-based appliance deployment, nor are Linux commands or tools referenced. Windows terminology and patterns (e.g., HKLM registry keys, %ProgramData% paths) are used exclusively, and Linux alternatives are not provided.
Recommendations
  • Provide Linux-based deployment instructions, including shell commands and installer scripts compatible with bash/sh.
  • Offer examples for running the appliance setup on Linux servers, including agent installation, configuration, and troubleshooting.
  • Reference Linux equivalents for Windows-specific tools (e.g., use systemd or init scripts instead of Windows services, /etc or /var/log paths instead of %ProgramData%).
  • Include screenshots and walkthroughs for Linux environments alongside Windows examples.
  • Clarify OS requirements and whether the appliance can be hosted on Linux, and if not, explain the limitation and suggest alternatives.
GitHub Create Pull Request
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 →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by repeatedly referencing Windows Server, SQL Server, and Windows-specific licensing and extended security updates. Cost calculations and savings examples are focused on Windows workloads, with no mention of Linux workloads, distributions, or licensing. All examples and cost breakdowns assume Windows-centric environments, and tools such as RVTools (a Windows-based tool) are referenced for VM imports. There is no discussion of Linux migration scenarios, Linux licensing, or parity in security/management features for Linux servers.
Recommendations
  • Include explicit examples and cost breakdowns for Linux workloads (e.g., Ubuntu, CentOS, Red Hat) alongside Windows workloads.
  • Discuss Linux licensing models and how Azure Migrate handles cost estimation for Linux servers.
  • Highlight security and management features for Linux servers (e.g., integration with Microsoft Defender for Cloud, Azure Monitor) and compare them with Windows equivalents.
  • Reference Linux-compatible migration tools and patterns, and provide guidance for importing Linux VMs.
  • Ensure that all sections mentioning extended security updates, hybrid benefits, and Arc-enabled features address Linux scenarios where applicable.
  • Add screenshots and sample reports that include Linux server data and migration paths.
GitHub Create Pull Request
Migrate https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/hydration-process.md ...e-docs/blob/main/articles/migrate/hydration-process.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in several ways: Windows server instructions and examples are presented first and in greater detail, with explicit PowerShell and command prompt screenshots and commands. Windows-specific tools (diskpart, PowerShell, Task Manager) are referenced and illustrated, while Linux instructions are less detailed, lack screenshots, and provide fewer concrete command examples. Linux configuration steps are described more generically, with only RedHat-specific commands shown, and no parity for Ubuntu, Debian, or SUSE. There are also more references to Windows troubleshooting and agent installation, with links to Windows-specific articles and tools.
Recommendations
  • Present Linux and Windows instructions in parallel, or alternate which OS is described first.
  • Add Linux command-line examples and screenshots for common distributions (e.g., Ubuntu, Debian, SUSE) to match the detail given for Windows.
  • Provide equivalent troubleshooting steps and agent verification commands for Linux, including graphical and CLI methods.
  • Reference Linux-specific documentation and tools with the same prominence as Windows tools.
  • Ensure manual preparation steps for Linux are as detailed and actionable as those for Windows, including explicit commands for DHCP/network configuration, agent installation, and driver verification.
  • Include more distribution-specific examples for Linux (not just RedHat), and clarify differences where necessary.
GitHub Create Pull Request
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 →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation demonstrates a Windows bias by exclusively referencing Windows tools, paths, and patterns (e.g., use of %ProgramFiles%, .exe utilities, and Windows/Domain Account terminology). There are no examples or instructions for Linux environments, and all steps assume a Windows-based Azure Migrate appliance and SQL Server configuration. Linux equivalents, if any, are not mentioned or provided.
Recommendations
  • Provide equivalent instructions and tooling for Linux-based environments, including Linux-compatible utilities or scripts for provisioning least privileged accounts.
  • Include examples for running the process on Linux, such as using bash, Linux file paths, and authentication methods relevant to Linux SQL Server deployments.
  • Clarify whether the utility is Windows-only or if there are alternative methods for Linux users, and link to those alternatives if available.
  • Mention Linux authentication/account types (e.g., local Linux users, Active Directory integration on Linux) where relevant.
  • Ensure that documentation sections and examples are clearly labeled for both Windows and Linux, or explicitly state if only Windows is supported.
GitHub Create Pull Request
Migrate https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/hyper-v-migration-architecture.md ...ain/articles/migrate/hyper-v-migration-architecture.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation is heavily focused on Windows and Hyper-V environments, with all examples, tools, and instructions tailored to Windows systems. It references Windows-specific tools (MMC snap-in, Regedit, Windows Azure Backup), provides step-by-step instructions only for Windows, and omits any mention of Linux-based hypervisors or migration scenarios. There are no Linux equivalents or parity in examples, and Windows terminology and tooling are presented exclusively and first throughout.
Recommendations
  • Add equivalent instructions and examples for Linux-based hypervisors (e.g., KVM, Xen) if supported by Azure Migrate.
  • Include Linux tooling and commands for bandwidth throttling and upload thread configuration, or clarify if these features are unavailable on Linux.
  • Provide a comparison table of supported platforms and note any feature gaps between Windows and Linux migrations.
  • Explicitly state platform limitations and direct Linux users to relevant documentation or alternative migration paths.
  • Ensure that future documentation includes both Windows and Linux migration scenarios, with examples and tooling for each.
GitHub Create Pull Request
Migrate https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/migrate-servers-to-azure-using-private-link-agent-based.md ...igrate-servers-to-azure-using-private-link-agent-based.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing Windows Server-specific features (such as Azure Hybrid Benefit for Windows Server), using terminology and patterns familiar to Windows administrators (e.g., Recovery Services vault, managed identities, and Azure Migrate appliance), and omitting Linux-specific migration details or examples. There are no explicit Linux command-line examples, nor is there guidance for Linux-specific migration concerns (such as SELinux, systemd, or Linux disk layouts). The documentation assumes familiarity with Windows-centric migration workflows and does not provide parity for Linux users.
Recommendations
  • Add explicit Linux migration examples, including steps for common Linux distributions (Ubuntu, CentOS, RHEL, etc.), such as agent installation and verification.
  • Include Linux-specific considerations (e.g., handling of Linux disk partitions, bootloaders, SELinux/AppArmor, systemd services) during migration.
  • Provide sample commands for DNS and network connectivity verification using Linux tools (e.g., dig, nslookup, systemctl) alongside any Windows equivalents.
  • Clarify whether the Mobility service agent and replication appliance support Linux, and provide troubleshooting steps for Linux environments.
  • Balance references to Windows features (like Azure Hybrid Benefit) with equivalent Linux licensing or support notes, if applicable.
  • Ensure that all migration steps and UI screenshots are applicable to both Windows and Linux servers, or clearly indicate differences.
GitHub Create Pull Request
Migrate https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/migrate-hyper-v-servers-to-azure-using-private-link.md ...ttps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/migrate-hyper-v-servers-to-azure-using-private-link.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation is focused exclusively on migrating Hyper-V (a Windows-based hypervisor) servers to Azure, with all examples, instructions, and tooling centered around Windows environments. There are no Linux or cross-platform migration examples, nor are Linux-based hypervisors (such as KVM or Xen) mentioned. Windows-specific tools and terminology (e.g., Hyper-V Replication provider, Recovery Services vault, Windows Server, Azure Hybrid Benefit for Windows Server) are used throughout, with no Linux equivalents or parity.
Recommendations
  • Add equivalent migration guides for Linux-based hypervisors (e.g., KVM, Xen, VMware on Linux) to Azure using Private Link.
  • Include Linux-specific instructions, examples, and troubleshooting steps where applicable.
  • Reference cross-platform tools or clarify when steps are Windows-specific, and provide links to Linux migration documentation.
  • Mention Azure Hybrid Benefit applicability for Linux workloads (if any), or clarify its Windows-only scope.
  • Ensure parity in terminology and process descriptions for both Windows and Linux environments.
GitHub Create Pull Request
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 →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation for the Azure Migrate replication appliance demonstrates a clear Windows bias. All operating system requirements, examples, and instructions are focused exclusively on Windows Server (2016/2012 R2). There are no references to Linux as a supported OS for the replication appliance, nor are there Linux-specific instructions or examples (e.g., for MySQL installation, system requirements, or deployment steps). Windows tools and patterns (such as .msi installers, C:\Temp paths, Windows Server roles, and group policies) are mentioned exclusively, with no Linux equivalents or alternatives provided.
Recommendations
  • Explicitly state whether Linux is supported as a host OS for the replication appliance. If not, clarify this limitation early in the documentation.
  • If Linux is supported, provide Linux-specific instructions for appliance deployment, including system requirements, package installation (e.g., MySQL via apt/yum), and configuration steps.
  • Include Linux examples for MySQL installation, such as commands for Ubuntu (apt-get install mysql-server) or RHEL/CentOS (yum install mysql-server), and specify Linux file paths.
  • Mention Linux equivalents for Windows-specific concepts (e.g., group policies, IIS roles) or clarify that these are not applicable on Linux.
  • Ensure parity in troubleshooting and upgrade instructions for both Windows and Linux environments, if Linux is supported.
GitHub Create Pull Request
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 →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation page exhibits a Windows bias by prioritizing Windows Server versions and requirements, referencing Windows-specific tools and services (e.g., .NET Framework, Windows Firewall, RDP), and providing detailed instructions for Windows connectivity and migration steps before Linux equivalents. Linux requirements and examples are present but less detailed and often listed after Windows instructions. There is a lack of parity in example depth and troubleshooting guidance for Linux scenarios.
Recommendations
  • Provide Linux-specific migration examples and troubleshooting steps with equal detail as Windows, including common distributions and edge cases.
  • List Linux and Windows requirements side-by-side or in parallel sections to avoid prioritizing Windows.
  • Include Linux-native tools and patterns (e.g., iptables, systemd, SELinux) where relevant, not just Windows tools like Windows Firewall and RDP.
  • Expand on Linux post-migration connectivity (e.g., SSH, firewall configuration) with step-by-step instructions similar to those given for Windows.
  • Reference both Windows and Linux documentation links equally and ensure Linux links are as prominent and detailed.
  • Add explicit guidance for Linux-specific migration challenges, such as handling different filesystems, bootloader configurations, and security policies.
GitHub Create Pull Request
← Previous Page 11 of 37 Next →