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 826-850 of 918 flagged pages
Migrate Performance vs As-is on-premises assessments ...docs/blob/main/articles/migrate/target-right-sizing.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a subtle Windows bias by referencing Hyper-V and VMware as the only hypervisors for performance data collection, with no mention of Linux-native hypervisors (e.g., KVM, Xen) or Linux-specific tooling. There are no examples or guidance for Linux workloads, nor are Linux migration patterns, tools, or considerations discussed. The examples and terminology are generic but implicitly favor Windows-centric environments.
Recommendations
  • Explicitly mention support for Linux workloads and Linux-native hypervisors (such as KVM, Xen) in the performance data collection section.
  • Provide examples of right-sizing for Linux servers, including typical Linux workload scenarios.
  • Clarify whether the appliance supports performance data collection from Linux VMs and physical Linux servers, and describe any differences in process or requirements.
  • Include Linux-specific migration considerations, such as file system types, disk partitioning, and common Linux services.
  • Add references to Linux tools or commands that can be used to collect performance data for import-based discovery (e.g., top, vmstat, iostat).
GitHub Create Pull Request
Migrate Assess Hyper-V VMs for migration to Azure VMs with Azure Migrate .../blob/main/articles/migrate/tutorial-assess-hyper-v.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation is heavily focused on Hyper-V, a Windows-centric virtualization platform, and does not provide examples or guidance for Linux-based hypervisors (such as KVM or Xen) or Linux-specific migration scenarios. All instructions, terminology, and examples assume a Windows/Hyper-V environment, with no mention of Linux tools, commands, or migration patterns. Additionally, licensing and cost options are described with a Windows-first perspective (e.g., Azure Hybrid Benefit for Windows Server), with only a brief mention of Enterprise Linux subscriptions (RHEL and SLES) as an afterthought.
Recommendations
  • Add equivalent tutorials and examples for assessing Linux-based VMs from common Linux hypervisors (e.g., KVM, Xen, VirtualBox) for migration to Azure.
  • Include Linux-specific discovery and assessment steps, such as using Linux tools or command-line utilities.
  • Provide parity in cost estimation examples, including details for Linux licensing and Azure Hybrid Benefit for Linux, with equal prominence as Windows.
  • Ensure screenshots and UI walkthroughs are applicable to both Windows and Linux environments, or clearly indicate differences.
  • Mention and link to documentation for VMware and other non-Windows platforms where relevant, to provide a more balanced cross-platform perspective.
GitHub Create Pull Request
Migrate Assess physical servers for migration to Azure with Azure Migrate ...blob/main/articles/migrate/tutorial-assess-physical.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows-first bias. While it mentions that assessment is not supported for Windows Server 2003 or SUSE Linux, there are no Linux-specific examples, instructions, or tools referenced throughout the tutorial. The language and examples are generic, but all licensing and cost optimization features (e.g., Azure Hybrid Benefit) are described with Windows Server as the primary example, with Linux (RHEL/SLES) only mentioned as an aside. There are no explicit Linux command-line or workflow examples, and no mention of Linux-specific considerations or patterns.
Recommendations
  • Add explicit Linux examples and instructions, such as how to assess Linux servers (e.g., Ubuntu, CentOS) and any differences in the process or recommendations.
  • Include Linux-specific cost optimization features and licensing options, with equal detail to Windows Server.
  • Mention Linux tools or patterns where relevant (e.g., SSH, Linux performance monitoring tools) in the assessment workflow.
  • Ensure that any screenshots or UI references show both Windows and Linux server scenarios.
  • Clarify any differences in assessment outcomes or recommendations for Linux servers, including supported distributions and versions.
GitHub Create Pull Request
Migrate Tutorial to assess web apps in VMware VMs for migration to Azure App Service ...ain/articles/migrate/tutorial-assess-webapps-vmware.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation focuses on assessing ASP.NET (IIS) and Java (Tomcat) web apps for migration from VMware VMs to Azure App Service. While both Windows (ASP.NET/IIS) and Linux (Java/Tomcat) workloads are mentioned, the examples and instructions are generic and do not provide explicit Linux-specific guidance or parity. There are no Linux shell commands, nor are Linux migration patterns or tools discussed. The ASP.NET/IIS scenario is presented first, and there is no mention of other common Linux web servers (e.g., Apache, Nginx) or Linux-specific migration considerations.
Recommendations
  • Add explicit Linux-based examples, such as migrating web apps running on Apache or Nginx, in addition to Tomcat.
  • Include Linux shell command examples for discovery, assessment, or troubleshooting, where appropriate.
  • Discuss Linux-specific migration considerations, such as file system differences, permissions, and service management.
  • Ensure that Linux scenarios are presented with equal prominence and detail as Windows/IIS scenarios.
  • Reference Linux tools and patterns (e.g., systemd, package managers) where relevant to the migration process.
GitHub Create Pull Request
Migrate Tutorial to assess web apps for migration to Azure App Service .../blob/main/articles/migrate/tutorial-assess-webapps.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation provides parallel coverage for ASP.NET (IIS/Windows) and Java (Tomcat/Linux) web apps, but the structure and example flow prioritize Windows workloads. The ASP.NET/IIS scenario is presented first, and there are no concrete Linux command-line examples or references to Linux-native tools or patterns. The tutorial lacks explicit Linux-centric instructions or screenshots, and does not mention Linux-specific migration considerations.
Recommendations
  • Alternate the order of ASP.NET and Java pivots, or present them together to avoid implicit prioritization.
  • Include explicit Linux command-line examples (e.g., bash, systemctl, Linux file paths) for discovery and assessment steps.
  • Add screenshots and instructions for Linux environments (e.g., Tomcat on Ubuntu) alongside Windows/IIS examples.
  • Mention Linux-native tools or migration patterns (such as using SSH, SCP, or Linux package managers) where relevant.
  • Provide troubleshooting tips or prerequisites specific to Linux servers (e.g., required permissions, firewall settings, SELinux/AppArmor considerations).
GitHub Create Pull Request
Migrate Import on-premises servers in a VMware environment using RVTools XLSX (preview) ...s/migrate/tutorial-import-vmware-using-rvtools-xlsx.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation exclusively references RVTools, a Windows-only tool, for exporting VMware inventory data. There are no mentions of Linux-compatible alternatives, nor are there any examples or instructions for Linux users. The workflow assumes access to Windows environments and tools, potentially excluding users who operate primarily on Linux.
Recommendations
  • Mention Linux-compatible alternatives for exporting VMware inventory, such as using PowerCLI on Linux, govc, or custom scripts.
  • Provide example workflows for Linux users, including steps for exporting relevant data and importing into Azure Migrate.
  • Clarify platform requirements for RVTools and suggest cross-platform approaches where possible.
  • Consider including a comparison table of supported tools for both Windows and Linux environments.
GitHub Create Pull Request
Migrate https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/add-copilot-code-insights.md ...lob/main/articles/migrate/add-copilot-code-insights.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates Windows bias in several ways. References to AppCAT CLI and related quickstart guides consistently use Windows-specific instructions and links, such as 'tabs=windows' and 'windows#download-and-install'. There are no explicit Linux or cross-platform examples for installing or running AppCAT, nor are Linux CLI commands or patterns mentioned. The documentation assumes Windows as the default environment for .NET and Java assessment workflows, omitting Linux equivalents or parity guidance.
Recommendations
  • Add explicit instructions and examples for installing and running AppCAT CLI on Linux and macOS, including relevant shell commands.
  • Update links to quickstart guides to include Linux tabs or sections, ensuring parity in documentation.
  • Provide screenshots or walkthroughs that demonstrate the process on Linux environments, not just Windows.
  • Clarify any platform-specific requirements or limitations for both .NET and Java workflows.
  • Ensure troubleshooting and error messages include Linux-specific scenarios (e.g., file permissions, case sensitivity, shell differences).
GitHub Create Pull Request
Migrate https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/azure-monitor-agent-migration.md ...main/articles/migrate/azure-monitor-agent-migration.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation describes migration from the Log Analytics agent (MMA) to Azure Monitor Agent (AMA) for both Windows and Linux, but all procedural steps, examples, and scripts are presented in a generic or Windows-centric manner. There are no explicit Linux-specific instructions, examples, or references to Linux tools or commands. The installation and management links default to the Azure portal, which is typically more familiar to Windows users, and there is no mention of Linux package managers or command-line installation methods.
Recommendations
  • Add explicit Linux installation instructions, including command-line examples using package managers (e.g., apt, yum, zypper) for AMA and Dependency agent.
  • Provide Linux-specific prerequisites and troubleshooting steps.
  • Include examples of running queries or scripts on Linux hosts, possibly using Bash or shell scripting.
  • Reference Linux documentation tabs or sections alongside Azure portal instructions.
  • Clarify any differences in migration steps or agent behavior between Windows and Linux environments.
GitHub Create Pull Request
Migrate https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/assessments-overview-migrate-to-azure-db-mysql.md ...rate/assessments-overview-migrate-to-azure-db-mysql.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing VMware and Microsoft Hyper-V environments first and exclusively in the context of on-premises migration sources, with no mention of Linux-native hypervisors (such as KVM or Xen) or Linux-specific migration scenarios. There are no examples or instructions tailored for Linux environments, nor any mention of Linux tools or command-line patterns. The guidance assumes the use of Azure Migrate appliances without clarifying their compatibility or deployment steps for Linux hosts, and omits Linux-centric migration considerations.
Recommendations
  • Explicitly mention Linux-native hypervisors (e.g., KVM, Xen) as supported on-premises environments for migration, and provide links or instructions for their assessment and migration.
  • Include examples and step-by-step instructions for deploying Azure Migrate appliances on Linux hosts, specifying prerequisites and supported distributions.
  • Add Linux command-line examples for discovery and assessment tasks, such as using SSH, systemd, or Linux monitoring tools to collect MySQL performance metrics.
  • Clarify compatibility and support for Linux environments throughout the documentation, ensuring Linux users have parity in guidance and tooling.
  • Where Windows tools or environments are referenced, provide Linux equivalents either alongside or before Windows examples to avoid implicit prioritization.
GitHub Create Pull Request
Migrate https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/how-to-review-discovered-inventory.md ...articles/migrate/how-to-review-discovered-inventory.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page exhibits a mild Windows bias. Windows servers and credentials are consistently mentioned before Linux equivalents, and examples or details for Linux are less thorough or absent. For instance, in credential setup and permissions, Windows instructions are more explicit, while Linux instructions are brief and lack concrete command examples. The 'Software inventory' feature is explicitly called out as 'Windows servers only', with no Linux feature parity or workaround described. There are no PowerShell-heavy examples or exclusive Windows tools, but the ordering and detail favor Windows.
Recommendations
  • Alternate the order of Windows and Linux instructions to avoid consistently listing Windows first.
  • Provide concrete Linux command examples and troubleshooting steps, similar to the detail given for Windows.
  • Clarify Linux feature parity for inventory features (e.g., software inventory) and document any limitations or workarounds.
  • Include explicit Linux-focused screenshots or walkthroughs where applicable.
  • Ensure all actions and attributes described for Windows servers are also covered for Linux servers, or clearly state any differences.
GitHub Create Pull Request
Migrate https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/how-to-use-azure-migrate-with-private-endpoints.md ...ate/how-to-use-azure-migrate-with-private-endpoints.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation page demonstrates a mild Windows bias by listing Microsoft Hyper-V and VMware vSphere as the first examples of supported platforms for discovery and migration, with Hyper-V (a Windows technology) mentioned before other platforms. The tools and scenarios focus on Azure Migrate, which is tightly integrated with Microsoft technologies. However, there are references to AWS, GCP, and bare-metal servers, and the page explicitly states agentless discovery works for 'any platform.' There is no evidence of PowerShell-heavy bias, and PowerShell is specifically called out as unsupported for this scenario.
Recommendations
  • Provide explicit Linux-based examples alongside Windows/Hyper-V examples, such as migration of Linux VMs or physical Linux servers.
  • Mention Linux-native tools or patterns where relevant, such as SSH or Linux-based automation for migration and assessment.
  • Ensure that documentation screenshots and walkthroughs include Linux scenarios, not just Windows-centric ones.
  • Clarify that agentless and agent-based migration supports both Windows and Linux operating systems, with links to Linux-specific guidance.
  • List non-Windows platforms (e.g., Linux, VMware, AWS, GCP) before or alongside Windows/Hyper-V in all examples to avoid Windows-first ordering.
GitHub Create Pull Request
Migrate https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/migrate-vmware-servers-to-azure-using-private-link-agent-based.md ...vmware-servers-to-azure-using-private-link-agent-based.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing Windows Server and Azure Hybrid Benefit specifically for Windows Server machines, without mentioning Linux equivalents or benefits. There are no examples or instructions tailored for Linux servers, nor is there guidance on Linux-specific migration considerations, tools, or credential handling. All references to OS types, migration steps, and benefits are either generic or Windows-centric, with no parity for Linux environments.
Recommendations
  • Include explicit instructions and examples for migrating Linux servers, such as handling SSH credentials, agent installation steps for Linux, and any Linux-specific prerequisites.
  • Mention Linux licensing and cost-saving options analogous to Azure Hybrid Benefit for Windows, if available.
  • Provide troubleshooting steps and network connectivity verification examples using Linux tools (e.g., dig, nslookup, curl) alongside any Windows-specific guidance.
  • Clarify whether the migration process and agent installation steps differ for Linux servers, and link to Linux-specific documentation where appropriate.
  • Ensure that references to OS types, migration settings, and post-migration best practices cover both Windows and Linux environments equally.
GitHub Create Pull Request
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
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing Windows-specific features (such as Azure Hybrid Benefit for Windows Server) and omitting Linux-specific migration considerations or examples. There are no Linux or cross-platform command-line examples, and the only OS-specific mention is for Windows licensing. The instructions and tips (such as editing the DNS hosts file) do not specify whether they apply to Windows, Linux, or both, and no Linux-specific guidance is provided for appliance setup, DNS configuration, or troubleshooting.
Recommendations
  • Add explicit Linux migration examples and considerations, such as handling Linux VM licensing, OS disk selection, and post-migration steps.
  • Clarify instructions for editing DNS hosts files by providing both Windows (C:\Windows\System32\drivers\etc\hosts) and Linux (/etc/hosts) paths and syntax.
  • Include troubleshooting steps and commands for both Windows (e.g., ipconfig, nslookup) and Linux (e.g., ifconfig/ip, dig, host) environments.
  • Mention Azure Hybrid Benefit applicability for Linux (if any) or clarify that it is Windows-only.
  • Ensure that appliance setup and network connectivity validation steps are described for both Windows and Linux hosts, including relevant commands and file locations.
GitHub Create Pull Request
Migrate https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/target-right-sizing.md ...docs/blob/main/articles/migrate/target-right-sizing.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page focuses on Azure Migrate's sizing assessments but demonstrates a Windows bias by only mentioning VMware, Hyper-V, and 'physical servers' without explicitly referencing Linux systems or providing Linux-specific examples. The data collection intervals and examples are tailored to Windows-centric hypervisors (Hyper-V) and generic 'physical servers', with no mention of Linux-native environments, tools, or migration patterns. There are no Linux command-line or tool references, nor examples illustrating Linux VM migration or assessment.
Recommendations
  • Explicitly mention Linux VMs and their assessment process alongside VMware and Hyper-V.
  • Provide examples of performance data collection for Linux environments (e.g., KVM, Xen, or other Linux hypervisors).
  • Include Linux-specific migration considerations, such as differences in disk partitioning, file systems, or resource utilization patterns.
  • Reference Linux tools or commands (e.g., top, vmstat, iostat) for gathering performance data for import-based discovery.
  • Add sample CSV import lines for Linux servers, clarifying any differences in metrics or terminology.
GitHub Create Pull Request
Migrate https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/review-sql-assessment.md ...cs/blob/main/articles/migrate/review-sql-assessment.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation consistently refers to SQL Server migration scenarios using 'SQL Server on Azure VM', which is typically associated with Windows-based deployments. There is no mention of Linux-based SQL Server deployments, nor are there examples or guidance for users migrating SQL Server instances running on Linux. The language and recommendations assume Windows as the default platform for SQL Server, omitting Linux parity in assessment and migration strategies.
Recommendations
  • Explicitly mention and provide guidance for SQL Server instances running on Linux, including assessment and migration steps.
  • Include examples or notes for both Windows and Linux SQL Server deployments, clarifying any differences in readiness, support status, and migration recommendations.
  • Add references to Linux tools, patterns, or considerations where relevant (e.g., differences in support status, licensing, or migration issues).
  • Ensure that screenshots and UI references do not implicitly assume Windows-only environments.
  • Clarify whether 'SQL Server on Azure VM' supports both Windows and Linux, and provide links to documentation for Linux-based SQL Server on Azure VM.
GitHub Create Pull Request
Migrate https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/server-redeploy.md ...ure-docs/blob/main/articles/migrate/server-redeploy.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
Although the documentation claims to support both Windows and Linux server redeployment, the content, examples, and customer intent are heavily focused on Windows Server scenarios. There are no Linux-specific instructions, examples, or references to Linux tools or migration patterns. The customer intent and narrative center on Windows Server 2003 migration, and all steps and screenshots are generic or Windows-oriented, with no Linux parity demonstrated.
Recommendations
  • Add explicit Linux migration examples, including screenshots and step-by-step instructions for Linux server redeployment.
  • Include Linux-specific prerequisites, such as considerations for different Linux distributions (e.g., Ubuntu, CentOS, RHEL) and their migration nuances.
  • Reference Linux tools and patterns (e.g., SSH, cloud-init, Linux disk formats) where relevant in the migration and IaC generation steps.
  • Provide sample IaC templates and Terraform variable configurations tailored for Linux workloads.
  • Clarify any differences in the migration process between Windows and Linux servers, especially regarding disk handling, OS configuration, and post-migration steps.
GitHub Create Pull Request
Migrate https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/tutorial-assess-hyper-v.md .../blob/main/articles/migrate/tutorial-assess-hyper-v.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation is heavily focused on Hyper-V, a Windows-centric virtualization platform, and does not provide equivalent guidance or examples for Linux-based hypervisors (such as KVM or Xen). All instructions, terminology, and prerequisites assume a Windows/Hyper-V environment, with no mention of Linux tools, patterns, or migration scenarios. There are no Linux-specific examples, nor is there parity in the migration assessment process for Linux-based VMs or environments.
Recommendations
  • Add equivalent tutorials and examples for assessing Linux-based hypervisors (e.g., KVM, Xen, VirtualBox) for migration to Azure.
  • Include Linux-specific discovery and assessment steps, such as using Linux tools or scripts for inventory and performance data collection.
  • Provide parity in screenshots and UI walkthroughs for Linux environments where applicable.
  • Explicitly mention support for Linux VMs and environments in the prerequisites and throughout the assessment process.
  • Clarify how the Azure Migrate appliance or CSV import process works for Linux-based VMs and environments.
GitHub Create Pull Request
Migrate https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/tutorial-assess-physical.md ...blob/main/articles/migrate/tutorial-assess-physical.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows-first bias. While it mentions that assessment is not supported for Windows Server 2003 and SUSE Linux, it does not provide any Linux-specific guidance, examples, or considerations. The tutorial and examples are generic and do not address Linux-specific migration concerns, tools, or patterns. There are no Linux command-line examples, nor any mention of Linux assessment nuances, even though Linux servers are a common migration scenario.
Recommendations
  • Include explicit examples and guidance for assessing Linux servers, such as considerations for different distributions (e.g., Ubuntu, CentOS, RHEL).
  • Add Linux-specific migration notes, such as handling of SELinux, systemd services, and disk partitioning.
  • Provide parity in screenshots and step-by-step instructions for Linux environments where applicable.
  • Mention and link to Linux tools or scripts that can assist with data collection or migration readiness.
  • Clarify any differences in assessment outcomes or recommendations for Linux versus Windows servers.
GitHub Create Pull Request
Migrate https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/tutorial-assess-webapps-vmware.md ...ain/articles/migrate/tutorial-assess-webapps-vmware.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation focuses on assessing ASP.NET (IIS) and Java (Tomcat) web apps for migration, but provides more explicit detail and context for Windows-based workloads (ASP.NET on IIS). There are no examples, screenshots, or instructions for Linux-based web servers (such as Apache, Nginx, or Java on Linux), nor is there mention of Linux-specific migration considerations or tools. The tutorial implicitly assumes Windows environments are primary, with Linux parity lacking in examples and guidance.
Recommendations
  • Add explicit examples and instructions for assessing Java web apps running on Linux (e.g., Tomcat on Linux, Apache, Nginx).
  • Include screenshots and walkthroughs for Linux-based server environments in the assessment process.
  • Mention and link to Linux-specific migration tools, troubleshooting steps, and considerations (such as file system differences, service management, and security).
  • Ensure parity in guidance for both Windows and Linux workloads, including prerequisites, assessment steps, and post-assessment recommendations.
  • Clarify in the prerequisites and overview sections that both Windows and Linux workloads are supported, and highlight any differences in assessment or migration.
GitHub Create Pull Request
Migrate https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/includes/public-cloud-vmware.md .../main/articles/migrate/includes/public-cloud-vmware.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Missing Linux Example Windows First
Summary
The documentation page provides a download link for VMware but does not specify platform-specific instructions or examples. The link uses a Microsoft URL shortener, suggesting a Windows-centric approach. There are no Linux-specific download instructions, verification commands, or parity in tooling examples.
Recommendations
  • Add Linux-specific download and installation instructions, such as using wget or curl.
  • Provide SHA256 verification examples for both Windows (e.g., certutil) and Linux (e.g., sha256sum).
  • Include notes about platform compatibility and any differences in installation steps.
  • Avoid using only Microsoft-branded links or tools; offer alternatives or clarify cross-platform support.
GitHub Create Pull Request
Migrate https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/migrate-support-matrix.md ...s/blob/main/articles/migrate/migrate-support-matrix.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Missing Linux Example Windows First
Summary
The documentation page focuses on Azure Migrate support for VMware and Hyper-V VMs, which are primarily associated with Windows environments. There is no mention of Linux-specific migration scenarios, tools, or examples. The structure and examples prioritize Windows-centric virtualization platforms, with no parity for Linux-native environments or migration patterns.
Recommendations
  • Add explicit sections or examples for migrating Linux servers, including common Linux distributions and workloads.
  • Mention Linux-specific considerations, such as agent installation, permissions, and supported file systems.
  • Include references to Linux migration tools or patterns (e.g., rsync, SSH, Linux-based appliances) alongside Windows/Hyper-V/VMware examples.
  • Clarify support for physical Linux servers and provide step-by-step guidance for their assessment and migration.
  • Ensure that Linux scenarios are presented with equal prominence to Windows/VMware/Hyper-V scenarios.
GitHub Create Pull Request
Migrate https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/tutorial-import-vmware-using-rvtools-xlsx.md ...s/migrate/tutorial-import-vmware-using-rvtools-xlsx.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation exclusively references RVTools, a Windows-only tool, for exporting VMware inventory data. There are no mentions of Linux alternatives, nor are there instructions or examples for performing similar tasks on Linux systems. All guidance assumes access to Windows environments and tools, with no parity for Linux users.
Recommendations
  • Mention and provide instructions for Linux-compatible alternatives to RVTools, such as using VMware's PowerCLI (which can run on Linux via PowerShell Core), govmomi, or direct vSphere API queries.
  • Include examples or steps for exporting VMware inventory data using Linux tools or scripts.
  • Clarify platform requirements for RVTools and suggest cross-platform workflows where possible.
  • Add a section comparing RVTools with Linux-compatible tools, highlighting pros and cons for each.
GitHub Create Pull Request
Migrate https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/how-to-use-azure-migrate-with-private-endpoints.md ...ate/how-to-use-azure-migrate-with-private-endpoints.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation page demonstrates a mild Windows bias by listing Microsoft Hyper-V alongside VMware as primary hypervisor platforms, and by referencing Windows-centric migration scenarios (Hyper-V, VMware) before mentioning Linux or other platforms. The tools and examples focus on Azure Migrate's support for Windows environments, with little explicit mention of Linux-specific migration patterns, tools, or examples. There is no evidence of PowerShell-heavy instructions, and PowerShell is explicitly noted as unsupported for this scenario.
Recommendations
  • Add explicit examples and references for Linux server migration, including supported Linux distributions and any platform-specific considerations.
  • Include Linux-specific migration scenarios and links to relevant tutorials (e.g., migrating Ubuntu, CentOS, or RHEL servers).
  • Mention Linux tools or command-line patterns where appropriate, such as using SSH or Linux-native agents.
  • Ensure parity in documentation structure by listing Linux migration options alongside Windows/Hyper-V/VMware, rather than after or as an afterthought.
  • Provide troubleshooting guidance for common Linux migration issues, similar to what is offered for Windows environments.
GitHub Create Pull Request
Migrate https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/includes/public-cloud-vmware.md .../main/articles/migrate/includes/public-cloud-vmware.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Missing Linux Example Windows First
Summary
The documentation provides a download link for VMware via a Microsoft URL (go.microsoft.com), which suggests a Windows-centric approach. There are no instructions or examples for Linux users, such as how to verify the SHA256 checksum or install VMware on Linux. The absence of Linux-specific guidance or parity in download sources indicates a bias towards Windows.
Recommendations
  • Include Linux-specific instructions for downloading and verifying the VMware installer, such as using wget/curl and sha256sum.
  • Provide alternative download links not tied to Microsoft infrastructure, if available.
  • Add installation steps for both Windows and Linux platforms.
  • Ensure examples for checksum verification are shown for both PowerShell (Windows) and Bash (Linux).
GitHub Create Pull Request
Migrate https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/add-copilot-code-insights.md ...lob/main/articles/migrate/add-copilot-code-insights.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates Windows bias by providing installation and usage instructions for AppCAT CLI and Java assessment that reference Windows-specific tabs and links, but does not offer equivalent Linux instructions or examples. The .NET CLI installation and usage is described generically, but Java assessment references only Windows tabs. There are no explicit Linux or cross-platform command examples, and no mention of Linux-specific considerations for AppCAT or zip file handling.
Recommendations
  • Add explicit Linux instructions and examples for installing and running AppCAT CLI, including package manager commands (e.g., apt, yum) and shell usage.
  • Ensure all referenced quickstart and installation links include both Windows and Linux tabs, or clarify cross-platform compatibility.
  • Provide Linux-specific troubleshooting tips for zip file creation and upload, such as using 'zip' command-line tools.
  • Include screenshots or terminal examples from Linux environments alongside Windows examples.
  • Clarify any platform-specific limitations or requirements for AppCAT and related tools.
GitHub Create Pull Request
← Previous Page 34 of 37 Next →