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 676-700 of 918 flagged pages
Migrate Business case in Azure Migrate ...articles/migrate/concepts-business-case-calculation.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page exhibits a moderate Windows bias. Cost models, licensing, and management tooling are heavily focused on Windows Server, SQL Server, and Microsoft System Center. Windows licensing and ESU calculations are detailed, while Linux is only briefly mentioned in amortization and support cost tables, with no specific examples or cost breakdowns for Linux workloads. Management software costs are described only for Windows and SQL scenarios. There are no examples or guidance for Linux-specific migration, licensing, or management tools, and Windows-related tools and patterns are consistently mentioned first or exclusively.
Recommendations
  • Add explicit cost breakdowns and licensing details for Linux workloads, including common distributions and support models.
  • Include examples and recommendations for Linux migration strategies, such as moving to Azure Linux VMs, Azure Container Instances, or Azure Kubernetes Service with Linux nodes.
  • Describe management and monitoring options for Linux servers, such as integration with Azure Monitor, Log Analytics, and open-source tools.
  • Ensure parity in describing security solutions for Linux (e.g., Defender for Linux, third-party options).
  • Present Windows and Linux examples side-by-side where relevant, rather than focusing on Windows first.
  • Clarify how Linux licensing/support is handled in TCO and migration calculations.
GitHub Create Pull Request
Migrate Build a migration plan with Azure Migrate ...b/main/articles/migrate/concepts-migration-planning.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits a moderate Windows bias. Windows Server and SQL Server are referenced repeatedly, with specific migration scenarios and benefits (such as free security updates for Windows Server 2008/2008 R2) highlighted. The 'Upgrade Windows OS' section provides detailed steps and tooling for Windows in-place upgrades, but there is no equivalent guidance for Linux OS upgrades or migration nuances. Linux is mentioned only briefly in the context of Azure Hybrid Benefit, and there are no Linux-specific migration examples, blockers, or recommendations. The documentation assumes Windows-centric workloads and omits Linux/macOS-specific migration considerations.
Recommendations
  • Add explicit examples and guidance for migrating Linux workloads, including common Linux distributions and their migration blockers.
  • Include a section on Linux OS upgrades or migration strategies, similar to the Windows OS upgrade section.
  • Provide parity in tooling descriptions, such as mentioning Linux-compatible migration scripts or extensions.
  • Highlight Linux-specific Azure features (e.g., support for open-source databases, Linux VM SKUs) and cost-saving options.
  • Ensure that migration readiness and assessment examples include both Windows and Linux scenarios.
GitHub Create Pull Request
Migrate Agentless Replication of VMware Virtual Machines ...rticles/migrate/concepts-vmware-agentless-migration.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
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 primarily in the management and configuration sections. Examples for bandwidth throttling use Windows PowerShell cmdlets (New-NetQosPolicy) and reference Windows-specific services (GatewayWindowsService.exe). The configuration of blackout windows references a Windows file path (C:\ProgramData\Microsoft Azure\Config) and restarting a Windows service, with no mention of Linux equivalents or instructions. There are no Linux/macOS examples or alternative commands provided for these operational tasks, and Windows tooling is presented as the default or only option.
Recommendations
  • Provide equivalent Linux/macOS instructions for bandwidth throttling, such as using tc, iptables, or other Linux QoS tools.
  • Document the location and format of configuration files on Linux appliances, if supported, and how to restart relevant services (e.g., systemctl).
  • Include Linux/macOS command-line examples alongside PowerShell, or clarify if the appliance is Windows-only.
  • Explicitly state platform requirements and limitations for the Azure Migrate appliance, including whether Linux-based appliances are supported for agentless migration.
  • If Linux/macOS is not supported, clarify this early in the documentation to set expectations for non-Windows users.
GitHub Create Pull Request
Migrate Tutorial to assess web apps for migration ...lob/main/articles/migrate/create-web-app-assessment.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exhibits Windows bias by focusing primarily on ASP.NET web apps and Windows Server licensing, with no explicit mention of Linux-based web apps (e.g., Node.js, PHP, Python) or Linux migration scenarios. Examples and sizing details are provided for ASP.NET and Tomcat (Java), but there are no instructions or references for Linux-native environments, tools, or migration patterns. The 'Next steps' section links only to Windows Dockerfile optimization, omitting Linux container guidance.
Recommendations
  • Add explicit instructions and examples for assessing and migrating Linux-based web apps (e.g., Node.js, PHP, Python, Ruby).
  • Include Linux container optimization links and best practices alongside Windows Dockerfile references.
  • Clarify that Azure Migrate supports Linux workloads and provide guidance for Linux-specific migration scenarios.
  • Provide parity in performance data collection details for Linux web servers (e.g., Apache, Nginx) and not just Tomcat.
  • Mention Linux licensing considerations and Azure Hybrid Benefit applicability for Linux workloads.
GitHub Create Pull Request
Migrate Discovered Metadata ...docs/blob/main/articles/migrate/discovered-metadata.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. Windows-specific tools (WMI, PowerShell cmdlets, registry paths) are listed first and in greater detail, with Linux equivalents often grouped together or described more generically. Windows examples and tooling (PowerShell, registry, WMI) are consistently presented before Linux commands, and some sections (e.g., ASP.NET, Spring Boot, Java web app data) are described only in the context of Windows servers. Windows storage metadata is much more detailed, with extensive PowerShell cmdlet coverage, while Linux storage metadata is presented as a list of shell commands without as much explanation or parity in structure. There are also sections (e.g., SQL Server, web app data) that assume Windows as the host platform, with Linux only mentioned as a possible value, not as a first-class scenario.
Recommendations
  • Present Linux and Windows examples side-by-side in all sections, not just as an afterthought.
  • Provide Linux-specific details for web app discovery (e.g., Apache, Nginx, Tomcat on Linux) and storage features (e.g., LVM, RAID, NFS, Samba).
  • Expand Linux tooling explanations to match the depth given to Windows (e.g., explain what each Linux command does, provide context for output parsing).
  • Explicitly call out Linux support for SQL Server and web apps, with examples of Linux-based deployments and data collection.
  • Avoid listing Windows tools and cmdlets first; alternate ordering or group by scenario rather than OS.
  • Where Windows uses PowerShell or WMI, provide equivalent Linux shell commands or scripts with equal detail.
  • Clarify which features are Windows-only and which are cross-platform, and document Linux/macOS limitations or alternatives.
GitHub Create Pull Request
Migrate Create and manage projects ...s/blob/main/articles/migrate/create-manage-projects.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias, particularly in the section describing command-line operations after project creation. The instructions for installing and using the Azure CLI explicitly reference PowerShell and instruct users to open PowerShell as Administrator, with no mention of Linux/macOS terminals or shell environments. All command-line examples are shown in a Windows/PowerShell context, and there are no equivalent instructions or screenshots for Linux or macOS users. The ordering and phrasing suggest Windows as the default platform.
Recommendations
  • Provide explicit instructions and examples for Linux/macOS users, including terminal commands and environment notes.
  • Clarify that Azure CLI can be used on multiple platforms and show how to open a terminal on Linux/macOS.
  • Include screenshots or step-by-step guidance for Linux/macOS environments where relevant.
  • Avoid language that assumes PowerShell/Windows as the default (e.g., 'open PowerShell as Administrator'); instead, use platform-neutral phrasing.
  • Add a note or section highlighting cross-platform compatibility for all CLI steps.
GitHub Create Pull Request
Migrate Create project ...zure-docs/blob/main/articles/migrate/create-project.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page primarily describes project creation via the Azure portal and REST API, which are cross-platform. However, in the section on agentless dependency analysis enhancements, instructions for using the Azure CLI are explicitly given for PowerShell, with steps such as 'open PowerShell on your system as an Administrator' and no mention of Linux/macOS terminals or shell equivalents. This suggests a Windows-first approach and PowerShell-heavy bias, which may cause friction for Linux/macOS users.
Recommendations
  • Provide Azure CLI command examples for Bash/zsh (Linux/macOS) alongside PowerShell.
  • Replace 'open PowerShell on your system as an Administrator' with platform-neutral instructions like 'open your terminal of choice with appropriate privileges'.
  • Explicitly mention that Azure CLI works on Linux/macOS and link to installation instructions for those platforms.
  • If any commands require platform-specific syntax, clarify differences for Linux/macOS users.
GitHub Create Pull Request
Migrate Discover and assess using Azure Private Link ...migrate/discover-and-assess-using-private-endpoints.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a notable Windows bias. All appliance installation and configuration instructions are provided exclusively for Windows environments, using PowerShell and Windows file paths. There are no Linux/macOS equivalents or examples, nor any mention of how to run the installer or configure the appliance on non-Windows systems. The VDDK installation instructions also reference only Windows locations. This creates friction for users on Linux or macOS, who may not be able to follow the documented steps without significant adaptation.
Recommendations
  • Provide Linux/macOS-specific instructions for downloading, extracting, and running the installer script, including shell commands and file paths.
  • Clarify whether the appliance installer script is supported on Linux/macOS, and if so, document the prerequisites and steps.
  • Include examples for running the installer script in Bash or other common Linux shells.
  • Document VDDK installation steps for Linux, including default installation paths and any required permissions.
  • Add troubleshooting and log file location details for Linux/macOS environments.
GitHub Create Pull Request
Migrate Automate agentless VMware migrations in Azure Migrate ...lob/main/articles/migrate/how-to-automate-migration.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation is heavily biased towards Windows and PowerShell environments. All automation instructions, examples, and tooling references are exclusively for PowerShell scripts (.ps1), with no mention of Bash, Linux, or cross-platform alternatives. Installation and usage instructions assume a Windows/PowerShell context, and there are no Linux/macOS-specific notes or guidance.
Recommendations
  • Provide equivalent Bash or cross-platform scripting examples for Linux/macOS users.
  • Clarify whether the PowerShell scripts are compatible with PowerShell Core (pwsh) on Linux/macOS, and provide installation instructions for those platforms.
  • Explicitly mention any limitations or requirements for running the scripts on non-Windows systems.
  • Include troubleshooting tips or known issues for Linux/macOS environments.
  • Consider providing Docker containers or other packaging to ease cross-platform usage.
GitHub Create Pull Request
Migrate Set up Agentless Dependency Analysis in Azure Migrate ...https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/how-to-create-group-machine-dependencies-agentless.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page exhibits a moderate Windows bias. PowerShell is the only CLI tool provided for managing agentless dependency analysis, with no Linux/macOS shell alternatives or cross-platform CLI guidance. Windows credential patterns and administrative permissions are described first and in more detail than Linux equivalents. The use of PowerShell for all automation and export tasks, including integration with Power BI, further centers the experience around Windows tooling. However, Linux servers are supported for agentless analysis and are mentioned in credential requirements and visualizations.
Recommendations
  • Provide equivalent Linux/macOS shell (e.g., Bash) commands for managing dependency analysis, including enabling/disabling and exporting data.
  • Document how to perform these tasks using Azure CLI or REST API, which are cross-platform.
  • Include examples of Linux credential setup and troubleshooting alongside Windows examples.
  • Mention and demonstrate open-source visualization alternatives to Power BI for Linux/macOS users.
  • Ensure screenshots and UI instructions show parity for Linux servers where applicable.
GitHub Create Pull Request
Migrate Discover SQL Server instances in an existing Azure Migrate project ...ticles/migrate/how-to-discover-sql-existing-project.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page exhibits a notable Windows bias. It references PowerShell and Windows credentials as prerequisites for discovery, and discusses Windows/Domain accounts and Active Directory validation extensively. Linux-specific tools, credentials, or discovery patterns are not mentioned, nor are examples for Linux environments provided. The instructions and terminology are Windows-centric, which may create friction for users operating Linux servers.
Recommendations
  • Add explicit instructions and examples for discovering SQL Server instances on Linux-based servers.
  • Clarify whether the Azure Migrate appliance supports Linux hosts and, if so, detail the credential requirements and discovery process for Linux.
  • Include Linux command-line alternatives to PowerShell where applicable.
  • Mention Linux authentication patterns (e.g., SSH keys, local Linux users) and how they can be used for discovery.
  • Ensure screenshots and step-by-step guides include Linux scenarios where relevant.
GitHub Create Pull Request
Migrate Migrate VMware virtual machines to Azure with server-side encryption(SSE) and customer-managed keys(CMK) using the Migration and modernization tool ...es/migrate/how-to-migrate-vmware-vms-with-cmk-disks.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation exclusively uses Azure PowerShell for all command-line examples and instructions, with no mention of Azure CLI, Bash, or Linux/macOS-specific workflows. All example scripts and referenced guides are PowerShell-based, and links point to Windows-centric documentation. There are no Linux/macOS command-line equivalents or notes on cross-platform usage, making the instructions difficult to follow for users on non-Windows systems.
Recommendations
  • Provide equivalent Azure CLI examples for all PowerShell commands, as Azure CLI is cross-platform and works natively on Linux/macOS.
  • Add notes or sections clarifying how Linux/macOS users can perform each step, including template editing and deployment.
  • Reference Azure CLI documentation alongside PowerShell documentation, especially for resource creation and deployment tasks.
  • Explicitly state platform requirements or limitations if any steps are Windows-only, and suggest alternatives for other platforms.
  • Ensure that links to disk encryption set creation and template deployment include both PowerShell and CLI options.
GitHub Create Pull Request
Migrate Create an Azure SQL assessment ...articles/migrate/how-to-create-azure-sql-assessment.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page exhibits a moderate Windows bias. It references Windows-specific tools and patterns (such as Cloud Witness and Windows Server Failover Clusters), links to Windows-focused best practices, and omits Linux-specific migration scenarios and examples. Licensing and cost optimization sections mention Windows Server licenses and Enterprise Linux (RHEL/SLES) but provide more detail for Windows. There are no explicit Linux or macOS command-line examples, nor guidance for Linux-based SQL deployments.
Recommendations
  • Add explicit examples and guidance for assessing and migrating SQL Server instances running on Linux (e.g., SQL Server on Ubuntu, RHEL, SLES).
  • Include references and links to Linux-specific best practices for SQL Server on Azure VMs (e.g., /azure/azure-sql/virtual-machines/linux/performance-guidelines-best-practices-checklist).
  • Clarify high availability and disaster recovery options for Linux-based clusters (e.g., Pacemaker, Linux witness options) alongside Windows options.
  • Ensure licensing and cost optimization guidance is equally detailed for Linux (including open-source and commercial Linux distributions).
  • Where screenshots or UI elements are shown, note any differences for Linux-based appliances or deployments.
GitHub Create Pull Request
Migrate Set up agent-based dependency analysis in Azure Migrate ...es/migrate/how-to-create-group-machine-dependencies.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
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 mild Windows bias. Windows installation instructions are presented first and in greater detail, including GUI and command-line options, while Linux instructions are brief and lack equivalent detail. References to Windows-specific tools (Configuration Manager, Intigua) are made without Linux alternatives. Some installation scripts and automation options are only linked for Windows. Overall, Linux users can complete the tasks, but may encounter friction due to less comprehensive guidance.
Recommendations
  • Present Windows and Linux instructions in parallel or alternate order to avoid Windows-first bias.
  • Expand Linux installation instructions to include automation options (e.g., using Ansible, shell scripts) similar to those provided for Windows.
  • Provide links to Linux-specific agent installation scripts and management tools.
  • Include troubleshooting steps and supported OS lists for Linux as is done for Windows.
  • Reference Linux package managers (e.g., apt, yum) for agent installation where applicable.
GitHub Create Pull Request
Migrate Discover software inventory on on-premises servers with Azure Migrate .../main/articles/migrate/how-to-discover-applications.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. Windows terminology, tools, and patterns (such as guest user accounts, local admin privileges, File Server role, IIS/ASP.NET, and SCCM) are referenced more frequently and in greater detail than Linux equivalents. Windows authentication and credential patterns are described first and in more depth, while Linux instructions are less explicit. Some features (e.g., File Server discovery) are Windows-only, and Linux-specific examples or guidance are sparse or missing.
Recommendations
  • Provide explicit Linux credential setup instructions and examples, including supported authentication methods and required permissions.
  • Clarify Linux support for features like file server discovery, or explicitly state limitations and alternatives (e.g., Samba/NFS discovery for Linux).
  • Include Linux-first or Linux-parity examples for credential provisioning, software inventory, and role/feature discovery.
  • Balance references to Windows tools (e.g., SCCM, IIS) with Linux equivalents (e.g., Samba, Apache, Nginx, package managers).
  • Add troubleshooting guidance for Linux-specific discovery issues.
  • Clearly indicate which features are Windows-only and suggest workarounds or alternatives for Linux users.
GitHub Create Pull Request
Migrate Azure Migrate FAQ ...azure-docs/blob/main/articles/migrate/resources-faq.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page shows moderate Windows bias. It references Windows-specific tools (MAP Toolkit), describes migration planning for Windows operating systems, and lists PowerShell before Bash in scripting skills. There are no Linux-specific migration tools or examples mentioned, and Windows-centric tools are referenced without Linux alternatives or parity.
Recommendations
  • Include examples or references for Linux migration tools and processes alongside Windows tools.
  • Mention Linux assessment and planning tools (e.g., open-source inventory or migration utilities) when discussing MAP Toolkit.
  • List Bash before or alongside PowerShell in scripting skills, and clarify support for Linux/macOS automation.
  • Add explicit guidance or links for migrating Linux workloads, including common challenges and solutions.
  • Ensure that migration scenarios and supported platforms are described with equal detail for Linux and Windows.
GitHub Create Pull Request
Migrate Review SQL assessment with Azure Migrate | Microsoft Docs .../main/articles/migrate/how-to-review-sql-assessment.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
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-specific SQL Server scenarios, linking only to Windows-based best practices, and omitting any mention of Linux-based SQL Server deployments or migration considerations. There are no examples, recommendations, or links for Linux SQL Server environments, which may leave Linux users without clear guidance.
Recommendations
  • Include explicit guidance and links for SQL Server on Linux, such as migration best practices and performance tuning for Linux-based Azure VMs.
  • Provide parity in documentation by referencing both Windows and Linux SQL Server scenarios where applicable.
  • Add notes or sections clarifying any differences or additional steps required for Linux-based SQL Server migrations.
  • Link to Linux-specific Azure SQL documentation (e.g., /azure/azure-sql/virtual-machines/linux/...) alongside Windows links.
  • Ensure that any PowerShell or Windows tool recommendations are accompanied by Bash/CLI/Linux tool equivalents.
GitHub Create Pull Request
Migrate Set up an Azure Migrate appliance for Hyper-V ...in/articles/migrate/how-to-set-up-appliance-hyper-v.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
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 oriented towards Windows environments, specifically Hyper-V. All examples and instructions use Windows tools (Hyper-V Manager, PowerShell, CertUtil, Local Group Policy Editor), and commands are shown only for Windows. Linux equivalents for verification, credential delegation, or appliance setup are not mentioned, and Windows-specific patterns (e.g., NTLM, Group Policy) are referenced without Linux alternatives. Even when Linux credentials are mentioned, no Linux-specific setup or troubleshooting guidance is provided.
Recommendations
  • Add Linux-specific instructions for verifying downloaded files (e.g., using sha256sum or openssl).
  • Include guidance for deploying and configuring the appliance on Linux hosts, if supported.
  • Provide Linux command-line alternatives for credential delegation and appliance management, or clarify if these steps are not applicable to Linux.
  • Explicitly state platform limitations and offer parity where possible, such as agentless discovery for Linux VMs.
  • Reorder examples to avoid always presenting Windows tools first, or provide parallel Linux/macOS instructions.
  • Clarify which steps are Windows-only and provide links to Linux/macOS documentation for similar tasks.
GitHub Create Pull Request
Migrate Set up an Azure Migrate appliance for server assessment in a VMware environment ...ain/articles/migrate/how-to-set-up-appliance-vmware.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation demonstrates a notable Windows bias. The alternative to OVA deployment is exclusively a PowerShell installer script, with no mention of Bash, shell, or Linux-native installation methods. The VDDK installation instructions specify a Windows file path (C:\Program Files\VMware\VMware Virtual Disk Development Kit) and do not provide Linux/macOS equivalents. Credential examples and validation focus on Windows domain and non-domain credentials, with Linux mentioned only as a credential type, lacking further details or examples. The documentation does not provide Linux/macOS-specific guidance for appliance setup, configuration, or troubleshooting.
Recommendations
  • Provide Linux/macOS installation instructions for the appliance, including Bash or shell script alternatives to PowerShell.
  • Include VDDK installation steps for Linux (e.g., typical Linux file paths, extraction commands, and permissions).
  • Offer Linux/macOS-specific troubleshooting and configuration guidance, such as firewall rules, proxy setup, and service management.
  • Present credential examples for Linux servers, including SSH key-based authentication and required permissions.
  • Ensure screenshots and UI references clarify cross-platform compatibility or differences.
GitHub Create Pull Request
Migrate Review Discovered Inventory (Preview) in Azure Migrate ...articles/migrate/how-to-review-discovered-inventory.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation generally treats Windows and Linux as supported platforms, but there is a subtle bias toward Windows. Windows servers and credentials are mentioned first in most lists and examples, and some features (like installed roles and features) are explicitly marked as 'Windows servers only' without equivalent Linux details. There are no Linux-specific examples, screenshots, or troubleshooting steps, and database/web app examples focus on Windows technologies (.NET, IIS, SQL Server) without mentioning Linux alternatives (e.g., Apache, MySQL, PostgreSQL).
Recommendations
  • Alternate the order of Windows and Linux mentions to avoid Windows-first bias.
  • Provide explicit Linux examples, including screenshots and step-by-step instructions for Linux credential setup, discovery, and troubleshooting.
  • Include Linux-specific details for features like software inventory (e.g., installed packages, services) and web/database platforms (e.g., Apache, Nginx, MySQL, PostgreSQL).
  • Clarify which features are available or limited for Linux servers, and offer parity where possible.
  • Add troubleshooting and permissions guidance for Linux environments, not just Windows.
  • Mention Linux web app and database types in examples and attribute tables.
GitHub Create Pull Request
Migrate Review a business case with Azure Migrate | Microsoft Docs ...b/main/articles/migrate/how-to-view-a-business-case.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page exhibits a moderate Windows bias. Windows Server and SQL Server are repeatedly referenced as the primary workloads, especially in sections discussing extended security updates, licensing, and cost calculations. Windows-specific features (e.g., Azure Hybrid Benefit, ESU licensing) are highlighted, while Linux workloads, distributions, or licensing models are not mentioned or exemplified. Cost breakdowns and migration strategies focus on Windows-centric scenarios, and there are no Linux-specific examples, cost considerations, or migration notes.
Recommendations
  • Include explicit references to Linux workloads, distributions, and licensing models in cost and migration strategy sections.
  • Add examples or notes about how Linux servers are assessed, migrated, and costed in Azure Migrate business cases.
  • Clarify whether features like Azure Hybrid Benefit, ESU, and Arc-enabled management apply to Linux workloads, and if so, how.
  • Provide parity in reporting and savings calculations for Linux (e.g., mention support status, security update costs, and management tooling for Linux).
  • Add screenshots or sample reports that include Linux workloads alongside Windows workloads.
GitHub Create Pull Request
Migrate Hydration process ...e-docs/blob/main/articles/migrate/hydration-process.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
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 a moderate Windows bias. Windows instructions and examples are presented first and in greater detail, including screenshots and explicit PowerShell commands. Windows-specific tools (diskpart, PowerShell, Task Manager) are referenced, while Linux instructions are less visual and rely on generic bash commands without screenshots. Some manual steps for Linux are described only for RedHat, with fewer illustrative examples for other distributions. Linux users may need to consult external documentation for distribution-specific procedures.
Recommendations
  • Alternate the order of Windows and Linux sections, or present them in parallel for each step.
  • Provide equivalent screenshots and command-line examples for Linux (e.g., using systemctl for DHCP, waagent status checks, etc.).
  • Include distribution-specific instructions and examples for popular Linux variants (Ubuntu, Debian, SUSE, etc.), not just RedHat.
  • Reference Linux tools and patterns (e.g., systemctl, nmcli, ifup/ifdown) alongside Windows tools.
  • Add troubleshooting notes and manual preparation steps for Linux with the same level of detail as Windows.
  • Ensure links to Linux agent documentation are as prominent as those for Windows VM Agent.
GitHub Create Pull Request
Migrate Support for Hyper-V assessment in Azure Migrate and Modernize ...ain/articles/migrate/migrate-support-matrix-hyper-v.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
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 notable Windows bias. Windows tools and patterns (such as PowerShell remoting, WinRM, and Windows authentication) are mentioned first and in more detail than their Linux equivalents. Many requirements and examples are Windows-centric, with Linux support often described as secondary or limited. SQL Server discovery is not supported for Linux servers, and all sample scripts for SQL Server login provisioning are Windows-oriented. PowerShell is referenced repeatedly, and Linux-specific instructions are minimal or absent in critical sections.
Recommendations
  • Provide Linux-first or Linux-parity examples and instructions alongside Windows ones, especially for credential provisioning and server access.
  • Clarify Linux support and limitations in each relevant section, and offer alternative workflows or tools where Windows-only features are present.
  • Include Linux-specific sample scripts and troubleshooting steps, particularly for software inventory, dependency analysis, and appliance deployment.
  • Explicitly document any features not supported on Linux and suggest workarounds or alternatives where possible.
  • Balance the order of presentation so that Linux and Windows instructions appear together or in parallel, rather than Windows-first.
GitHub Create Pull Request
Migrate Support for Hyper-V migration in Azure Migrate ...es/migrate/migrate-support-matrix-hyper-v-migration.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
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 primarily due to its focus on Hyper-V (a Windows-centric virtualization platform), repeated references to Windows Server versions, and detailed instructions for Windows-specific tasks (e.g., enabling RDP, Windows Firewall settings, SAN policy). Windows examples and requirements are presented before Linux equivalents, and Windows tools and terminology (e.g., .NET Framework, Windows Firewall, RDP) are mentioned exclusively or in greater detail. Linux instructions are present but less detailed and often refer users to other articles for manual changes, with fewer concrete examples.
Recommendations
  • Provide equally detailed Linux migration instructions, including common troubleshooting steps and configuration examples.
  • Include Linux-specific tooling or commands (e.g., how to check SSH service status, configure firewalls like ufw or firewalld) directly in the documentation.
  • Balance the order of presentation so that Linux and Windows requirements/examples are given equal prominence.
  • Clarify any platform-specific steps for both Windows and Linux, especially where manual changes are required.
  • Add explicit examples for Linux VM preparation, similar to the Windows RDP/SAN policy guidance.
GitHub Create Pull Request
Migrate Support for physical server migration in Azure Migrate and Modernize ...s/migrate/migrate-support-matrix-physical-migration.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page shows a moderate Windows bias. Windows-specific tools, patterns, and terminology (such as RDP, Windows Firewall, BitLocker, and Multipath IO for Windows) are mentioned first or exclusively in several sections. The 'Connect after migration' section provides more detailed, step-by-step instructions for Windows (including firewall and RDP configuration), while the Linux section is less detailed. There are references to Windows-specific features (e.g., BitLocker, Windows Firewall) without Linux equivalents or guidance. Powershell or Windows-centric terminology appears before Linux alternatives, and some features are described as 'supported for Windows' without clarifying Linux support.
Recommendations
  • Provide equally detailed Linux instructions for post-migration connectivity, including common firewall configuration commands (e.g., using ufw, firewalld, or iptables) and SSH setup.
  • When mentioning Windows-specific tools (e.g., BitLocker, Windows Firewall), include Linux equivalents (e.g., LUKS/dm-crypt for encryption, iptables/ufw for firewall) and clarify support or limitations.
  • Avoid listing Windows features or steps before Linux ones, or alternate the order to avoid perceived prioritization.
  • Clarify support for features like Multipath IO and disk encryption for Linux, or explicitly state if unsupported.
  • Where possible, provide example commands for both Windows (Powershell/GUI) and Linux (bash/CLI) environments.
GitHub Create Pull Request
← Previous Page 28 of 37 Next →