Migrate

394
Total Pages
295
Linux-Friendly Pages
99
Pages with Bias
25.1%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

218 issues found
Showing 76-100 of 218 flagged pages
Migrate Support for physical discovery and assessment in Azure Migrate and Modernize ...in/articles/migrate/migrate-support-matrix-physical.md
Medium Priority View Details →
Scanned: 2026-01-12 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 page demonstrates a moderate Windows bias. Windows tools (PowerShell, WinRM, WMI) are referenced frequently and in detail, with explicit requirements and links for configuration. Examples and scripts for SQL Server discovery and web app discovery are Windows-centric, with Linux support often described generically or marked as unsupported (e.g., SQL Server and ASP.NET web apps). Windows prerequisites and troubleshooting steps are more thoroughly documented, while Linux instructions are less detailed or deferred to external links. Windows terminology and ports are often listed first.
Recommendations
  • Provide Linux-specific setup scripts and troubleshooting guidance, especially for appliance setup and connectivity.
  • Include Linux examples and step-by-step instructions for supported features (e.g., dependency analysis, software inventory).
  • Clarify Linux limitations and offer alternative approaches where features are Windows-only (e.g., SQL Server discovery).
  • Balance the order of presentation so Linux and Windows are treated equally in tables and lists.
  • Add direct links to Linux server preparation guides rather than generic references.
GitHub Create Pull Request
Migrate Customer intent: As a systems administrator, I want to download the latest version of VMware, so that I can ensure my infrastructure is up to date and secure. .../main/articles/migrate/includes/public-cloud-vmware.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
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 using a Microsoft URL (go.microsoft.com), which may suggest a Windows-centric approach. There are no instructions or examples for downloading or verifying the file on Linux or macOS systems (e.g., using wget/curl or sha256sum). No Linux-specific tools or commands are mentioned.
Recommendations
  • Add Linux/macOS download instructions using wget or curl.
  • Include SHA256 verification steps for Linux/macOS (e.g., using sha256sum or shasum).
  • Clarify whether the download is platform-specific and provide alternative links if needed.
  • Ensure parity by listing both Windows and Linux/macOS steps side by side.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation page for Hyper-V migration in Azure Migrate shows a moderate Windows bias. Windows Server versions and requirements are listed first and in detail, with explicit references to Windows tools (e.g., Windows Firewall, RDP, .NET Framework). Linux support is mentioned, but Linux-specific instructions are less detailed and often appear after Windows guidance. The URLs and software requirements are Windows-centric, and there is no mention of Linux-based Hyper-V hosts or management tools. Examples and troubleshooting steps are focused on Windows environments.
Recommendations
  • Add Linux-first or Linux-parity examples and troubleshooting steps where applicable.
  • Include explicit instructions for Linux VM preparation and post-migration connectivity, matching the detail given for Windows (e.g., SSH setup, firewall configuration).
  • Clarify whether Hyper-V hosts running on Linux (via KVM or other virtualization platforms) are supported or not, and provide guidance if they are.
  • Balance the order of presentation so that Linux and Windows requirements are presented together or in parallel, rather than Windows-first.
  • Mention Linux equivalents for Windows tools (e.g., alternatives to Windows Firewall, .NET Framework requirements for Linux VMs if any).
GitHub Create Pull Request
Migrate Redeploy servers to Azure using Infrastructure as Code ...ure-docs/blob/main/articles/migrate/server-redeploy.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page is primarily focused on Windows Server redeployment, as indicated by the customer intent and description. While it claims to support both Windows and Linux servers, all examples, scenarios, and scripts are described in generic terms without any explicit Linux-specific guidance, tools, or troubleshooting. The prerequisites, migration steps, and IaC generation are presented from a Windows-centric perspective, and there are no Linux-specific instructions or examples. Windows tools (e.g., Visual Studio Code) are mentioned, but no Linux alternatives or considerations are provided.
Recommendations
  • Add explicit Linux server migration examples, including common Linux distributions (e.g., Ubuntu, CentOS).
  • Include Linux-specific prerequisites, such as required packages or permissions.
  • Provide sample scripts or command-line instructions for Linux environments (e.g., bash, shell commands) alongside any PowerShell or Windows examples.
  • Mention Linux-friendly IDEs or editors (e.g., Vim, Nano, or VS Code on Linux).
  • Address Linux-specific migration issues, such as handling of disk formats, file system compatibility, and post-migration configuration steps.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation focuses primarily on assessing ASP.NET web apps running on IIS (a Windows technology) and Java web apps on Tomcat, but provides more detailed context and examples for the Windows/IIS scenario. There are no explicit Linux-specific instructions, examples, or screenshots, and the assessment workflow assumes discovery via the Azure Migrate appliance without clarifying Linux-specific steps or considerations. Windows terminology (IIS, ASP.NET) is presented first and more prominently, while Linux/Java (Tomcat) is secondary and lacks parity in detail.
Recommendations
  • Add explicit instructions and examples for assessing Java web apps running on Linux VMs, including any Linux-specific prerequisites, discovery steps, and troubleshooting tips.
  • Provide screenshots and walkthroughs for the Linux/Tomcat scenario, not just for Windows/IIS.
  • Clarify whether the Azure Migrate appliance supports agentless discovery for Linux VMs and how to configure it for Linux environments.
  • Ensure that Linux tools, commands, and patterns are mentioned where relevant (e.g., systemd, Linux file paths, SSH access).
  • Present Linux and Windows scenarios with equal prominence, possibly by alternating their order or using parallel examples.
GitHub Create Pull Request
Migrate Continuous Deployment for containerized applications with Azure DevOps ...igrate/tutorial-app-containerization-azure-pipeline.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a notable Windows bias, especially in the 'Locate the artifacts' section, which exclusively references Windows file paths (C:\ProgramData\...) and Windows File Explorer instructions. There are no Linux/macOS equivalents or examples for locating artifacts, despite the mention of Java/Tomcat apps (often deployed on Linux). The initial instructions and artifact locations assume a Windows environment, and Linux patterns/tools are not mentioned or provided.
Recommendations
  • Add instructions for locating artifacts on Linux/macOS systems, including typical Linux file paths and commands (e.g., /var/lib/... or using 'ls' in the terminal).
  • Provide Linux/macOS examples for navigating directories and handling hidden files (e.g., using 'ls -a').
  • Clarify whether the Azure Migrate App Containerization tool supports Linux hosts, and if so, describe the artifact locations and access patterns for those platforms.
  • Ensure parity in examples and instructions for both Windows and Linux users throughout the tutorial, especially in critical setup steps.
GitHub Create Pull Request
Migrate What's New in Azure Migrate ...ocs/azure-docs/blob/main/articles/migrate/whats-new.md
Medium Priority View Details →
Scanned: 2026-01-12 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 for Azure Migrate exhibits a moderate Windows bias. Windows Server and Windows-centric migration scenarios are frequently mentioned first or exclusively, with several features and examples (such as PowerShell usage, Windows OS upgrades, and Windows-specific tools) highlighted before or in greater detail than their Linux equivalents. While Linux support is present and referenced (e.g., SSH authentication, Sudo support, RHEL/SLES migration), examples and tooling are often Windows-focused, and Linux-specific migration patterns or troubleshooting steps are less visible or detailed.
Recommendations
  • Ensure Linux migration scenarios are described with equal detail and prominence as Windows scenarios.
  • Provide Linux-specific examples (e.g., Bash scripts, Linux CLI commands) alongside or before Windows/PowerShell examples.
  • Highlight Linux tools and authentication methods (such as SSH, Sudo, root, setcap) in relevant sections, not just as alternatives.
  • Add troubleshooting and migration guidance for common Linux distributions (Ubuntu, CentOS, RHEL, SLES, etc.) similar to Windows guidance.
  • Balance the order of presentation so that Linux and Windows are treated equally in feature announcements and examples.
GitHub Create Pull Request
Migrate Enhancing Web App Assessment With Code Scan Reports for Azure Migration ...lob/main/articles/migrate/add-copilot-code-insights.md
Medium Priority View Details →
Scanned: 2026-01-12 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 bias primarily in its references and examples for installing and running AppCAT, especially for Java projects. Instructions and links for Java assessment via AppCAT are explicitly tagged with '?tabs=windows', and no Linux/macOS equivalents or instructions are provided. The .NET tool installation uses the 'dotnet' CLI, which is cross-platform, but the Java instructions are Windows-centric. There are no explicit PowerShell commands or Windows-only tools, but the ordering and lack of Linux/macOS guidance create friction for non-Windows users.
Recommendations
  • Provide explicit instructions and links for Linux/macOS users for AppCAT installation and usage, especially for Java projects.
  • Ensure that quickstart and assessment guides include Linux/macOS tabs or sections where relevant.
  • Clarify that the .NET CLI commands are cross-platform and mention any platform-specific caveats.
  • Add troubleshooting notes for common Linux/macOS issues (e.g., permissions, file paths, CLI dependencies).
  • Where screenshots or UI instructions differ by OS, provide alternatives or notes.
GitHub Create Pull Request
Migrate Agent-based Migration in the Migration and Modernization Tool ...articles/migrate/agent-based-migration-architecture.md
Medium Priority View Details →
Scanned: 2026-01-12 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 a notable Windows bias. It references Windows-specific tools (such as registry keys and MMC snap-ins), provides examples and instructions only for Windows environments (e.g., registry editing, folder paths), and omits Linux/macOS equivalents for key operations like bandwidth throttling and antivirus exclusions. All examples and instructions are presented in a Windows-centric manner, with no mention of Linux commands, file paths, or management tools.
Recommendations
  • Add Linux/macOS equivalents for all Windows-specific instructions, such as bandwidth throttling (e.g., using tc, iptables, or systemd on Linux), antivirus exclusions (specify Linux paths and common AV tools), and agent installation commands (provide shell examples).
  • Include Linux file paths and process server management instructions alongside Windows examples.
  • Clarify whether the Mobility service and process server support Linux/macOS, and provide explicit guidance for those platforms.
  • Reorder examples so that Linux and Windows instructions are presented with equal prominence, or grouped by OS.
  • Reference cross-platform tools where possible, and avoid assuming Windows-only environments.
GitHub Create Pull Request
Migrate Set Up Least Privileged Accounts ...les/migrate/best-practices-least-privileged-account.md
Medium Priority View Details →
Scanned: 2026-01-12 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 shows a moderate Windows bias. Windows examples and instructions are often presented before Linux equivalents, especially in sections like 'Quick server discovery' and 'Database discovery'. Windows-specific tools and UI steps (e.g., WMI Control, WinRM service) are described in detail, while Linux instructions are more concise and sometimes lack step-by-step guidance. SQL Server (Windows-centric) is covered extensively, with no parity for Linux-based database platforms (e.g., PostgreSQL). Powershell and Windows UI tools are referenced, but Linux command-line alternatives are not always provided.
Recommendations
  • Present Linux and Windows instructions in parallel, or alternate which comes first in each section.
  • Provide step-by-step Linux instructions for tasks where Windows UI steps are given (e.g., configuring permissions, service restarts).
  • Include examples for Linux-based database platforms (e.g., PostgreSQL) if supported.
  • Where Windows tools (WMI, WinRM, Control Panel) are referenced, mention Linux equivalents (e.g., systemd, sudoers, netstat) and provide matching detail.
  • Avoid assuming Windows as the default environment; clarify when steps are OS-specific.
GitHub Create Pull Request
Migrate Azure Migrate Appliance FAQ ...ob/main/articles/migrate/common-questions-appliance.md
Medium Priority View Details →
Scanned: 2026-01-12 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 for the Azure Migrate Appliance FAQ demonstrates a notable Windows bias. Deployment and management instructions are centered around PowerShell scripts, Windows-specific tools (e.g., certificate manager, group policy editor), and Windows file paths. Troubleshooting and update procedures reference Windows UI elements and workflows exclusively. There are no Linux/macOS equivalents or examples provided for key operations, even though the appliance may run on physical or virtual servers that could be Linux-based.
Recommendations
  • Provide equivalent Linux/macOS instructions for deploying and managing the appliance, including shell script alternatives to PowerShell.
  • Include Linux-specific troubleshooting steps for certificate management and MSI validation, such as using OpenSSL or Linux certificate stores.
  • Add examples of file paths, commands, and UI navigation for Linux systems where applicable.
  • Clarify OS requirements and support for the appliance, and explicitly state if Linux/macOS is unsupported for certain operations.
  • Where PowerShell is required, note if PowerShell Core (cross-platform) is supported, and provide installation guidance for non-Windows systems.
GitHub Create Pull Request
Migrate Azure SQL assessments in Azure Migrate Discovery and assessment tool ...s/migrate/concepts-azure-sql-assessment-calculation.md
Medium Priority View Details →
Scanned: 2026-01-12 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 Windows bias by frequently referencing Windows-specific technologies (e.g., IIS, Windows Server Failover Clusters), linking to Windows-focused best practices, and omitting Linux-specific migration scenarios, examples, or guidance. The high availability and disaster recovery sections exclusively mention Windows Server Failover Clusters and Cloud Witness, with no mention of Linux clustering or HA/DR patterns. There are no Linux or cross-platform examples, and the documentation assumes Windows environments for most advanced scenarios.
Recommendations
  • Include Linux-specific migration scenarios and examples, such as migrating SQL Server running on Linux or Linux-based HA/DR configurations.
  • Reference and link to Linux best practices for SQL Server on Azure VM (e.g., performance guidelines for Linux VMs).
  • Provide parity in documentation for Linux tools, patterns, and supported features (e.g., Pacemaker for clustering, Linux-based witness options).
  • Clearly state which features and recommendations apply to both Windows and Linux, and highlight any differences.
  • Add explicit guidance for users migrating from Linux environments, including any prerequisites or limitations.
GitHub Create Pull Request
Migrate Questions about assessments in Azure Migrate ...icles/migrate/common-questions-discovery-assessment.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page for Azure Migrate assessments demonstrates a moderate Windows bias. It consistently references Windows-centric environments (VMware, Hyper-V, SQL Server, IIS), and omits explicit mention or examples for Linux servers, Linux web apps, or Linux database workloads. Windows technologies and patterns (Hyper-V, IIS, SQL Server) are discussed in detail, while Linux equivalents (e.g., Apache, MySQL, PostgreSQL) are not addressed. There are no PowerShell-specific examples, but Windows environments are prioritized and Linux scenarios are not covered, which may create friction for Linux users.
Recommendations
  • Add explicit guidance and examples for assessing Linux servers (e.g., Ubuntu, CentOS) in Azure Migrate.
  • Include instructions for discovering and assessing Linux workloads (e.g., Apache, Nginx, MySQL, PostgreSQL) alongside Windows workloads.
  • Clarify whether Azure Migrate supports Linux web apps and databases, and document any limitations or differences.
  • Provide parity in troubleshooting steps, ensuring Linux-specific issues (e.g., agent installation, performance counters) are addressed.
  • When listing supported environments or prerequisites, mention Linux distributions and their requirements.
  • Balance examples and terminology so Linux users can easily follow assessment and migration processes.
GitHub Create Pull Request
Migrate Common Questions About the Migration and Modernization Tool .../articles/migrate/common-questions-server-migration.md
Medium Priority View Details →
Scanned: 2026-01-12 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. PowerShell and Windows-specific tools (NetQosPolicy, Scheduled Tasks) are used exclusively for bandwidth throttling examples, with no Linux equivalents or cross-platform alternatives provided. Windows OS upgrade is mentioned as supported, while Linux is explicitly excluded. Windows operating systems are listed first in support matrices, and some migration scenarios (such as ASP.NET/IIS web apps) are described only for Windows environments. There are no Linux shell or tool examples for operational tasks, and Linux migration nuances are less detailed.
Recommendations
  • Provide Linux-based examples for bandwidth throttling (e.g., using tc, iptables, or systemd timers for scheduling).
  • Include cross-platform or Linux-native commands/scripts alongside PowerShell examples.
  • Mention Linux migration limitations and workarounds with the same level of detail as Windows.
  • List Linux operating systems first or in parallel in support matrices to avoid implicit prioritization.
  • Add migration examples for common Linux workloads (e.g., Apache, Nginx, Tomcat) similar to the ASP.NET/IIS example for Windows.
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-12 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-specific migration scenarios (such as upgrading Windows Server OS during migration) are described in detail, including references to Windows-only tools (Custom Script Extension for Windows). Windows Server end-of-support is highlighted as a migration driver, and Windows licensing benefits (Azure Hybrid Benefit) are discussed before Linux equivalents. There are no explicit Linux migration or upgrade examples, nor are Linux-specific tools or patterns mentioned. Linux is referenced only briefly in the context of licensing/subscriptions, and there is no guidance for Linux OS upgrades or migration blockers unique to Linux workloads.
Recommendations
  • Add explicit examples and guidance for migrating Linux servers, including common Linux distributions (e.g., Ubuntu, CentOS, RHEL).
  • Include details on how to handle Linux-specific migration blockers, such as kernel compatibility, SELinux/AppArmor, and package management.
  • Provide parity for OS upgrade scenarios, such as guidance or tooling for in-place or side-by-side Linux OS upgrades during migration.
  • Mention Linux-specific Azure VM extensions and automation options, such as Custom Script Extension for Linux.
  • Balance cost optimization guidance by discussing Linux licensing/subscription migration in equal detail to Windows.
  • Ensure that migration prioritization tables and examples include Linux workloads and end-of-support Linux distributions.
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-12 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 how to install and use the Azure CLI. It instructs users to install Az CLI and then explicitly says 'open PowerShell on your system as an Administrator' and provides only PowerShell-based instructions for running CLI commands. There are no Linux/macOS terminal examples, nor is it mentioned that Az CLI can be used on Bash or other shells. The overall flow and screenshots are platform-neutral (Azure Portal), but command-line instructions assume Windows/PowerShell by default.
Recommendations
  • Explicitly state that Az CLI can be used on Linux/macOS and in Bash, Zsh, or other shells.
  • Provide equivalent command-line instructions for Linux/macOS users (e.g., 'Open your terminal and run these commands').
  • Avoid specifying 'PowerShell' unless the commands are genuinely PowerShell-specific; use 'terminal' or 'command prompt' for cross-platform clarity.
  • If there are platform-specific steps (e.g., running as Administrator), clarify how Linux/macOS users can achieve the same (e.g., using 'sudo').
  • Add a note or section for Linux/macOS users to ensure parity and inclusivity.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation demonstrates a moderate Windows bias. Examples and sizing guidance focus primarily on ASP.NET web apps (Windows), with only brief mention of Java/Tomcat (Linux) scenarios. The 'Next steps' section links exclusively to Windows Dockerfile optimization and Windows container best practices, omitting Linux equivalents. There are no explicit Linux/Python/Node.js web app examples, nor references to Linux container optimization or migration patterns.
Recommendations
  • Add explicit examples and sizing guidance for common Linux web stacks (e.g., Node.js, Python, PHP, Ruby) alongside ASP.NET and Java.
  • Include links to Linux container optimization guides (e.g., optimizing Dockerfiles for Ubuntu/Alpine, Linux container security best practices).
  • Reference Linux migration patterns and tooling (e.g., Apache/Nginx migration, Linux-specific Azure App Service features).
  • Ensure that 'Next steps' and best practices sections provide parity for Linux and open-source technologies, not just Windows.
  • Clarify that Azure Migrate supports both Windows and Linux workloads, and provide step-by-step instructions or screenshots for Linux scenarios.
GitHub Create Pull Request
Migrate Business case in Azure Migrate ...articles/migrate/concepts-business-case-calculation.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. Cost calculations and management tooling are heavily focused on Windows Server, SQL Server, and Microsoft System Center, with explicit formulas and licensing details for Windows products. Linux is mentioned only in passing (e.g., 'Linux OS' in license amortization and support), with no detailed cost breakdowns, examples, or management tooling equivalents. All management software examples are Microsoft-centric, and security/patching/monitoring defaults are tied to Windows scenarios. There are no Linux-specific examples, cost formulas, or references to common Linux management or security tools.
Recommendations
  • Add explicit cost calculation examples for Linux servers, including licensing, support, and management software (e.g., Red Hat, SUSE, Ubuntu, etc.).
  • Include Linux-specific management tooling (e.g., Ansible, Nagios, Zabbix) in the management software cost breakdown.
  • Provide examples or formulas for Linux extended support scenarios (e.g., ELS, vendor support), not just Windows ESU.
  • Clarify how patching, monitoring, and backup costs differ for Linux workloads, and reference Azure-native or third-party Linux management solutions.
  • Ensure Linux is represented in migration strategy recommendations and cost modeling, with parity to Windows examples.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates a notable Windows bias. All appliance installation and configuration instructions exclusively reference PowerShell, Windows file paths, and Windows administrative privileges. There are no examples or guidance for running the installer script on Linux or macOS hosts, nor any mention of Bash, shell, or cross-platform alternatives. The VDDK installation instructions also specify a Windows directory. This creates friction for users attempting to deploy the Azure Migrate appliance on non-Windows systems.
Recommendations
  • Provide explicit instructions and examples for running the installer script on Linux (and macOS, if supported), including shell commands and file paths.
  • Clarify whether the appliance installer script is cross-platform or Windows-only; if cross-platform, document prerequisites and steps for Linux/macOS.
  • Include Linux/macOS equivalents for file extraction, script execution, and log file locations.
  • Mention any limitations or requirements for non-Windows environments early in the documentation.
  • If the appliance is Windows-only, state this clearly at the beginning and suggest alternatives for Linux users.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page demonstrates a moderate Windows bias, primarily through heavy reliance on PowerShell for management tasks (enabling/disabling dependency analysis, exporting data, Power BI integration), and by referencing Windows tools and patterns (PowerShell, Power BI) without offering Linux/macOS CLI alternatives. Windows credential patterns and permissions are described before Linux equivalents, and PowerShell is presented as the default automation method. There are no Bash, shell script, or Linux-native tool examples for managing Azure Migrate dependency analysis.
Recommendations
  • Provide equivalent Linux/macOS CLI examples using Azure CLI, Bash, or Python for all PowerShell-based instructions.
  • Explicitly mention and document how Linux and macOS users can perform enable/disable/export operations without PowerShell (e.g., via Azure CLI, REST API, or SDKs).
  • Include Linux/macOS credential management patterns and permissions before or alongside Windows instructions.
  • Offer guidance for visualizing dependency data using open-source tools (e.g., Grafana, Kibana) in addition to Power BI.
  • Clarify cross-platform support for the AzMig.Dependencies module and provide installation/usage instructions for Linux/macOS environments.
GitHub Create Pull Request
Migrate Discovered Metadata ...docs/blob/main/articles/migrate/discovered-metadata.md
Medium Priority View Details →
Scanned: 2026-01-12 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, registry, COM objects) are described in detail and often presented before Linux equivalents. Windows examples and metadata are frequently listed first, and Windows-centric features (like ASP.NET/IIS, Windows Feature discovery, registry queries) are covered in depth, while Linux coverage is more generic and sometimes lacks parity (e.g., no Linux web app section, less detail on Linux feature discovery). Some sections (e.g., pending updates, application inventory, storage) use Windows tools and cmdlets with more explanation than Linux commands. There are also features described only for Windows (ASP.NET, IIS, Windows Features) with no Linux counterpart.
Recommendations
  • Present Linux and Windows examples side-by-side or alternate which is listed first.
  • Ensure all Windows-specific features (e.g., web app discovery, feature inventory) have Linux equivalents or clearly state if not supported.
  • Expand Linux sections to match the detail of Windows sections, especially for application inventory, feature discovery, and pending updates.
  • Add examples of Linux web app discovery (e.g., Apache, Nginx, Tomcat) and clarify support for Java/Spring Boot on Linux.
  • Where PowerShell or Windows registry is referenced, provide equivalent Linux commands or configuration file paths.
  • Explicitly state feature parity and limitations for Linux/macOS users in each section.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation exclusively references PowerShell scripts and the Azure PowerShell module for automating VMware migrations, with no mention of Bash, Linux shell, or cross-platform alternatives. All examples, installation instructions, and script execution syntax are Windows/PowerShell-centric, creating friction for Linux/macOS users who may not have native PowerShell environments or prefer Bash/shell scripting.
Recommendations
  • Provide Bash or shell script equivalents for the migration automation tasks, or clarify PowerShell Core (pwsh) compatibility on Linux/macOS.
  • Include installation instructions for PowerShell Core on Linux/macOS and note any differences in script execution.
  • Explicitly state platform requirements and limitations, and offer guidance for Linux/macOS users to run the scripts (e.g., using pwsh).
  • Consider offering sample scripts or modules in Python or other cross-platform languages if feasible.
  • Present examples for both Windows and Linux/macOS environments, or at least clarify that the scripts are cross-platform if true.
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-12 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 Windows Server Failover Clusters and Cloud Witness, and links to Windows-focused best practices for SQL Server on Azure VMs. Linux equivalents (e.g., Pacemaker for HA, Linux disk witness) are not mentioned, and examples or guidance for Linux-based SQL deployments are absent. The documentation assumes Windows environments in high availability/disaster recovery scenarios and in licensing discussions, with only brief mention of Enterprise Linux subscriptions (RHEL/SLES) for Azure Hybrid Benefit. No Linux-specific migration patterns, readiness checks, or cost considerations are provided.
Recommendations
  • Add explicit guidance and examples for Linux-based SQL Server deployments, including migration, assessment, and readiness checks.
  • Include references and links to Linux best practices for SQL Server on Azure VMs (e.g., performance guidelines for Linux, disk witness setup, Pacemaker cluster configuration).
  • When discussing high availability and disaster recovery, mention Linux clustering options and how to configure them in Azure.
  • Provide parity in licensing and cost estimation examples for Linux environments, not just Windows.
  • Ensure screenshots and walkthroughs include both Windows and Linux scenarios where applicable.
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-12 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 demonstrates a moderate Windows bias. Windows installation instructions are presented first and in greater detail, including GUI steps and references to Windows-specific automation tools (Configuration Manager, Intigua, PowerShell scripts). Linux instructions are more concise, lacking equivalent automation guidance and troubleshooting details. Windows tools and patterns (double-click installers, GUI wizards) are mentioned before Linux equivalents, and some links reference Windows operating systems specifically. Linux users may find the instructions less comprehensive and may need to infer steps or seek external resources.
Recommendations
  • Present Linux and Windows instructions in parallel, or alternate which is shown first.
  • Expand Linux installation guidance to include automation options (e.g., using Ansible, shell scripts) and troubleshooting steps.
  • Reference Linux package managers (apt, yum, zypper) and provide example commands for agent installation.
  • Include links to Linux-specific documentation and supported distributions.
  • Mention Linux equivalents for Windows tools (e.g., systemd for service management, CLI-based configuration).
  • Add screenshots or terminal output for Linux installation steps, similar to Windows GUI screenshots.
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-12 00:00
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 notable Windows bias. It references PowerShell and Windows credentials as prerequisites, focuses on Windows/Domain accounts for SQL Server discovery, and mentions Windows tools (PowerShell, AD validation) without providing Linux/macOS equivalents or examples. There is no mention of Linux authentication patterns, nor guidance for Linux-based SQL Server deployments. Windows terminology and tools are presented first and exclusively, creating friction for Linux users.
Recommendations
  • Add explicit instructions and examples for discovering SQL Server instances running on Linux servers, including authentication methods and required permissions.
  • Clarify whether the Azure Migrate appliance supports Linux-based SQL Server and web app discovery, and document any limitations.
  • Provide Linux/macOS command-line alternatives to PowerShell where relevant (e.g., Bash scripts, SSH usage).
  • Include Linux-specific troubleshooting tips and credential formats.
  • Reorder sections or add parallel guidance so Linux and Windows users are equally supported.
GitHub Create Pull Request
← Previous Page 4 of 9 Next →