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 351-375 of 918 flagged pages
Migrate https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/best-practices-least-privileged-account.md ...les/migrate/best-practices-least-privileged-account.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation demonstrates a Windows bias in several ways: Windows examples and configuration steps are often presented first and in greater detail, especially for server and database discovery. Windows-specific tools (WMI Control, WinRM, user groups) are described with step-by-step instructions and screenshots, while Linux equivalents are covered more briefly and with less guidance. SQL Server (Windows-centric) configuration scripts are extensive, whereas MySQL (cross-platform) instructions are minimal. There is a lack of parity in example depth and troubleshooting guidance for Linux environments.
Recommendations
  • Provide Linux configuration steps with the same level of detail as Windows, including step-by-step instructions, screenshots, and troubleshooting tips.
  • Include Linux-first or side-by-side examples for credential setup, permissions, and discovery workflows.
  • Expand Linux database discovery instructions (e.g., for MySQL and PostgreSQL) to match the depth given for SQL Server.
  • Add Linux-specific troubleshooting and validation steps analogous to those provided for Windows (e.g., verifying sudoers, service status, log locations).
  • Ensure that cross-platform tools and commands are introduced together, rather than Windows tools being mentioned first or exclusively.
  • Where possible, use generic or cross-platform terminology and avoid assuming Windows as the default environment.
GitHub Create Pull Request
Migrate https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/best-practices-security.md .../blob/main/articles/migrate/best-practices-security.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exhibits a strong Windows bias: installation and hardening instructions focus exclusively on Windows Server, referencing PowerShell scripts and Windows-specific security tools (such as GPOs and the Windows Security Compliance Toolkit). Linux is only mentioned in passing (e.g., port 22 for communication), with no examples or guidance for deploying or securing the appliance on Linux systems. The credential storage mechanism (DPAPI) is also Windows-specific, and all operational recommendations assume a Windows domain environment.
Recommendations
  • Provide equivalent Linux deployment instructions, including supported distributions and installation steps.
  • Include Linux-specific hardening guidance, such as references to CIS benchmarks and tools like OpenSCAP.
  • Offer examples for securing credentials on Linux, e.g., using keyrings or encrypted files.
  • Mention Linux alternatives to PowerShell scripts, such as Bash scripts or Ansible playbooks.
  • Clarify whether the appliance can be deployed on Linux, and if not, state this explicitly.
  • Balance references to Windows tools (GPOs, DPAPI) with Linux equivalents (e.g., sudoers, SELinux, PAM).
GitHub Create Pull Request
Migrate https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/common-questions-discovery-assessment.md ...icles/migrate/common-questions-discovery-assessment.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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 Windows bias by consistently referencing Windows-centric technologies (Hyper-V, SQL Server, IIS), providing examples and troubleshooting steps only for Windows environments, and omitting explicit guidance or examples for Linux servers and workloads. Windows tools and patterns (e.g., dynamic memory in Hyper-V, IIS for web apps, SQL Server) are mentioned exclusively or before any Linux equivalents, and there are no Linux-specific troubleshooting steps or assessment scenarios.
Recommendations
  • Add explicit examples and troubleshooting steps for Linux servers (e.g., Ubuntu, CentOS) in assessment scenarios.
  • Include guidance for assessing Linux workloads, such as Apache, Nginx, MySQL, PostgreSQL, and other common Linux services.
  • Mention Linux-specific migration blockers, readiness checks, and remediation steps alongside Windows examples.
  • Clarify how the Azure Migrate appliance collects performance data from Linux servers, including any required agents or permissions.
  • Provide parity in documentation for web app assessments by including scenarios for Linux-based web servers (e.g., Apache, Nginx) in addition to IIS.
  • Ensure that references to tools and features (e.g., dynamic memory, SQL Server) are balanced with Linux equivalents or alternatives.
GitHub Create Pull Request
Migrate https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/concepts-assessment-calculation.md ...in/articles/migrate/concepts-assessment-calculation.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Windows Heavy Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by listing Windows operating systems first and in detail in readiness tables, providing extensive information about Windows versions and support status, while Linux is covered in a single row with a link to endorsed distributions. There are no Linux-specific examples, troubleshooting, or migration nuances discussed, and no Linux command-line or tooling references. The guest OS analysis section notes limitations in Linux version detection but does not provide guidance or examples for Linux users. Windows-specific scenarios (e.g., UEFI boot, OS upgrades) are described in detail, while Linux scenarios are generalized.
Recommendations
  • Expand the guest operating system readiness table to list major Linux distributions and versions explicitly, similar to the Windows breakdown.
  • Provide Linux-specific migration considerations, troubleshooting steps, and examples (e.g., handling kernel versions, disk partitioning, bootloader issues).
  • Include Linux command-line or scripting examples where relevant, such as preparing Linux servers for migration or collecting performance data.
  • Discuss common Linux migration challenges (e.g., SELinux, systemd, init systems, file system compatibility) and how Azure Migrate addresses them.
  • Ensure parity in guidance for both Windows and Linux environments, including detailed steps for both in tutorials and best practices.
GitHub Create Pull Request
Migrate https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/concepts-azure-sql-assessment-calculation.md ...s/migrate/concepts-azure-sql-assessment-calculation.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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 consistently referencing Windows-specific technologies (such as Windows Server Failover Clusters, IIS, and Windows licensing), providing links and examples that focus on Windows environments, and omitting equivalent Linux scenarios, tools, or migration guidance. There are no Linux/Powershell-neutral or Linux-specific examples, and Linux migration patterns (e.g., SQL Server on Linux, Linux-based HA/DR) are not addressed. Windows terminology and tooling are mentioned exclusively or before any Linux alternatives.
Recommendations
  • Add explicit guidance and examples for SQL Server instances running on Linux, including migration steps and readiness checks for Linux-based environments.
  • Include references and links to best practices for SQL Server on Linux in Azure VMs, alongside the existing Windows-focused links.
  • Document Linux licensing and Azure Hybrid Benefit scenarios (e.g., RHEL/SLES) with equal detail as Windows licensing.
  • Provide parity in high availability and disaster recovery guidance, covering Linux clustering solutions (e.g., Pacemaker) and their configuration in Azure.
  • Ensure that migration strategies and assessment logic are described for both Windows and Linux SQL Server deployments, not just Windows-first scenarios.
  • Where PowerShell or Windows tools are referenced, also mention Linux equivalents (e.g., Bash scripts, CLI commands) for appliance deployment and migration operations.
GitHub Create Pull Request
Migrate https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/concepts-business-case-calculation.md ...articles/migrate/concepts-business-case-calculation.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits a Windows bias by prioritizing Windows Server and SQL Server licensing and ESU costs in TCO calculations, referencing Microsoft System Center for management (applicable only to Windows/SQL scenarios), and omitting explicit Linux-specific examples or cost breakdowns. While Linux OS is mentioned in license amortization and support, there are no details or formulas provided for Linux licensing, management, or security costs, nor are Linux migration scenarios or tools discussed.
Recommendations
  • Add explicit examples and cost formulas for Linux server licensing, management, and security, including common Linux distributions (e.g., RHEL, SUSE, Ubuntu) and their support/subscription models.
  • Include Linux-specific management tools (e.g., Ansible, Puppet, Chef, Nagios) in the management software cost breakdown, and clarify how their costs are assessed.
  • Provide migration strategy examples for Linux workloads, including recommendations for PaaS/IaaS targets (e.g., Azure Linux VMs, Azure App Service for Linux, Azure Kubernetes Service with Linux nodes).
  • Ensure that Linux scenarios are presented alongside Windows scenarios in all relevant tables and sections, rather than only referencing Windows first or exclusively.
  • Clarify how security and monitoring costs are calculated for Linux servers, including Defender for Linux and any third-party solutions.
GitHub Create Pull Request
Migrate https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/concepts-migration-planning.md ...b/main/articles/migrate/concepts-migration-planning.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits a Windows bias by prioritizing Windows Server migration scenarios, highlighting Windows-specific features (such as free security updates for Windows Server 2008/2008 R2), and providing detailed guidance on Windows OS upgrades using Azure Migrate. There is a lack of equivalent Linux migration examples, Linux-specific tooling, or mention of Linux OS upgrade capabilities. Windows tools and patterns (e.g., Custom Script Extension for Windows) are described in detail, while Linux migration and upgrade processes are not addressed.
Recommendations
  • Add explicit examples and guidance for migrating Linux servers, including common Linux distributions (e.g., Ubuntu, CentOS, RHEL).
  • Provide details on Linux OS upgrade options during migration, or clarify if such features are unavailable.
  • Include information about Linux-specific migration blockers, readiness checks, and remediation steps.
  • Mention and describe Linux equivalents for tools and extensions (e.g., Custom Script Extension for Linux).
  • Ensure parity in cost-saving features, such as Azure Hybrid Benefit, by providing examples for Linux subscriptions.
  • Balance references to end-of-support scenarios by including Linux EOL cases and migration incentives.
  • Where Windows-specific features are highlighted, add corresponding Linux notes or alternatives.
GitHub Create Pull Request
Migrate https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/concepts-azure-webapps-assessment-calculation.md ...grate/concepts-azure-webapps-assessment-calculation.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates Windows bias by focusing exclusively on ASP.NET web apps running on IIS (a Windows technology) and referencing Windows-centric migration paths. There are no examples or explicit guidance for Linux-based web apps (such as those running on Apache, Nginx, or other Linux stacks), nor are Linux migration tools or patterns mentioned. The only Java example references Tomcat, but does not clarify platform parity or provide Linux-specific instructions.
Recommendations
  • Add explicit examples and instructions for assessing and migrating Linux-based web apps (e.g., those running on Apache, Nginx, or other Linux web servers).
  • Include Linux-specific migration patterns, considerations, and troubleshooting steps alongside Windows/IIS examples.
  • Mention Linux-compatible tools and clarify whether the Azure Migrate appliance supports discovery and assessment of Linux web apps.
  • Ensure that references to App Service SKUs and plans include both Windows and Linux hosting options, with links to relevant documentation.
  • Provide parity in assessment properties and readiness checks for Linux workloads, including feature compatibility and security tooling.
GitHub Create Pull Request
Migrate https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/concepts-migration-webapps.md ...ob/main/articles/migrate/concepts-migration-webapps.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation is heavily biased towards Windows environments. All migration options, requirements, and examples focus exclusively on Windows servers running IIS, with explicit statements that Linux servers are not supported. Windows PowerShell is mentioned as a required tool, with no mention of Linux alternatives or parity. There are no Linux migration examples, tools, or guidance provided.
Recommendations
  • Clearly state whether Linux support is planned and provide a roadmap if applicable.
  • If agentless migration for Linux web apps is not supported, offer guidance or alternatives for Linux users (e.g., manual migration steps, recommended tools).
  • Include a comparative table showing feature parity (or lack thereof) between Windows and Linux environments.
  • Add examples or documentation for Linux-based web app migration if/when support is available.
  • Mention Linux equivalents for tools and commands where possible, or explicitly note their absence.
GitHub Create Pull Request
Migrate https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/concepts-vmware-agentless-migration.md ...rticles/migrate/concepts-vmware-agentless-migration.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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 Windows bias in several areas. Bandwidth throttling is described exclusively using Windows PowerShell cmdlets (New-NetQosPolicy) and references to GatewayWindowsService.exe, with no mention of Linux equivalents. Configuration file paths and service management instructions use Windows conventions (C:\ProgramData\...), and there are no Linux-based examples or guidance for managing the Azure Migrate appliance on Linux. The documentation assumes the appliance runs on Windows, omitting Linux scenarios and tools.
Recommendations
  • Provide equivalent Linux examples for bandwidth throttling, such as using tc or iptables for traffic shaping.
  • Include instructions for managing configuration files and services on Linux, e.g., file paths (/etc/...), systemctl for service restarts.
  • Clarify whether the Azure Migrate appliance can run on Linux, and if so, provide parity in documentation for both platforms.
  • When referencing tools or scripts, offer both Windows (PowerShell) and Linux (shell script) versions.
  • Avoid assuming Windows as the default platform; structure examples and guidance to address both Windows and Linux users equally.
GitHub Create Pull Request
Migrate https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/create-manage-projects.md ...s/blob/main/articles/migrate/create-manage-projects.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates bias toward Windows environments by providing command-line examples exclusively in PowerShell, referencing 'open PowerShell as Administrator' for Az CLI usage, and omitting equivalent Linux shell instructions. There is no mention of Linux terminal usage, nor are Linux-specific examples or notes provided for cross-platform parity. The ordering and phrasing also assume a Windows-first experience when interacting with Azure Migrate via CLI.
Recommendations
  • Provide Az CLI examples for both Windows (PowerShell) and Linux/macOS (Bash), including explicit instructions for opening a terminal on Linux/macOS.
  • Add notes clarifying that Az CLI is cross-platform and can be run from Bash, Zsh, or other shells, not just PowerShell.
  • Where instructions say 'open PowerShell as Administrator', include the Linux/macOS equivalent (e.g., 'open a terminal with appropriate permissions').
  • Include screenshots or references that show the experience on Linux/macOS where relevant.
  • Review all command snippets and ensure they are not using Windows-specific syntax (e.g., backslashes in paths, angle brackets) unless necessary, and provide alternatives for Linux/macOS.
GitHub Create Pull Request
Migrate https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/create-web-app-assessment.md ...lob/main/articles/migrate/create-web-app-assessment.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by focusing primarily on ASP.NET web apps and Windows Server licensing, with detailed sizing and performance collection examples for Windows workloads. There is a lack of Linux-specific examples, such as for PHP, Node.js, or Python web apps, and no mention of Linux tools or migration patterns. The only Docker optimization link provided is for Windows Dockerfiles, and Windows licensing (Azure Hybrid Benefit) is discussed in detail, while Linux equivalents are omitted.
Recommendations
  • Include explicit examples and guidance for Linux-based web apps (e.g., PHP, Node.js, Python) in the assessment process.
  • Provide parity in performance data collection and sizing details for common Linux web servers (e.g., Apache, Nginx) alongside Tomcat.
  • Add links and references to optimizing Linux Dockerfiles and best practices for Linux containers on AKS and App Service.
  • Discuss licensing and cost considerations for Linux workloads, such as open-source licensing and potential savings.
  • Ensure that screenshots and step-by-step instructions include Linux scenarios and not just Windows-centric environments.
  • Mention Linux migration tools or patterns where relevant, and avoid presenting Windows tools or options first or exclusively.
GitHub Create Pull Request
Migrate https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/discover-and-assess-using-private-endpoints.md ...migrate/discover-and-assess-using-private-endpoints.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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 strong Windows bias. All appliance installation and configuration instructions exclusively use PowerShell and Windows paths (e.g., C:\Program Files), with no mention of Linux equivalents or examples. The installer script is referenced as a PowerShell script (.ps1), and the process assumes the use of a Windows server for hosting the appliance. There are no instructions or guidance for deploying or managing the appliance on Linux systems, nor are Linux-specific tools or commands provided.
Recommendations
  • Provide equivalent Linux installation instructions, including shell script examples and Linux file paths.
  • Clarify whether the Azure Migrate appliance can be hosted on Linux, and if so, offer step-by-step guidance for Linux users.
  • Include Linux troubleshooting tips and log file locations.
  • Mention Linux prerequisites (e.g., required packages, permissions) alongside Windows prerequisites.
  • Offer parity in screenshots and UI walkthroughs for Linux environments if supported.
GitHub Create Pull Request
Migrate https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/discovered-metadata.md ...docs/blob/main/articles/migrate/discovered-metadata.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in several ways: Windows examples, tools, and PowerShell cmdlets are frequently listed first or exclusively, especially in sections on software inventory, features, pending updates, and storage metadata. Windows-specific technologies (WMI, PowerShell, registry locations) are described in detail, while Linux equivalents are often summarized as generic shell commands or grouped together. Some sections (e.g., ASP.NET, Java, Spring Boot web app data) only mention Windows servers, omitting Linux scenarios. Linux instructions are less detailed and lack parity in explanation and structure compared to Windows.
Recommendations
  • Ensure Linux examples and commands are presented with equal detail and structure as Windows examples, including explicit command outputs and sample data tables.
  • Present Windows and Linux instructions side-by-side or in parallel sections, rather than listing Windows first or exclusively.
  • Add Linux-specific application and feature inventory details, such as systemd units, installed services, and feature detection (e.g., using systemctl, service, or package managers).
  • Include Linux equivalents for PowerShell cmdlets and registry queries, such as using configuration files, system commands, or package manager queries.
  • Expand web app discovery sections to include Linux-hosted scenarios (e.g., Apache, Nginx, Tomcat on Linux) and provide Linux-specific metadata collection methods.
  • Review all sections for missing Linux examples and add them where only Windows is covered (e.g., pending updates, storage metadata, web app data).
GitHub Create Pull Request
Migrate https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/how-to-automate-migration.md ...lob/main/articles/migrate/how-to-automate-migration.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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 strong Windows bias by exclusively referencing PowerShell scripts and modules for automating VMware migrations with Azure Migrate. All examples, instructions, and tooling are centered around PowerShell (.ps1 scripts, Az PowerShell module), with no mention of Bash, Linux shell equivalents, or cross-platform scripting approaches. Installation and execution instructions assume a Windows or PowerShell environment, and there is no guidance for users on Linux or macOS systems.
Recommendations
  • Provide equivalent Bash or shell script samples for Linux/macOS users, or clarify if PowerShell Core (pwsh) is supported cross-platform.
  • Explicitly document how to run these scripts on Linux (e.g., using PowerShell Core), including installation steps for PowerShell on Linux.
  • Add notes or sections for Linux users, including troubleshooting tips and environment setup instructions.
  • Reference Azure CLI alternatives where possible, or explain why PowerShell is required.
  • Ensure that examples and instructions are not exclusively Windows-centric; present Linux options in parallel or before Windows-specific guidance.
GitHub Create Pull Request
Migrate https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/how-to-create-azure-sql-assessment.md ...articles/migrate/how-to-create-azure-sql-assessment.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in several ways: references to Windows-specific tools and patterns (such as Cloud Witness and Windows Server Failover Clusters), links to Windows-centric best practices, and a lack of Linux-specific examples or parity in high availability/disaster recovery scenarios. Linux equivalents (e.g., Linux clustering, witness options, migration patterns) are not mentioned or are relegated to licensing notes only.
Recommendations
  • Include Linux-specific examples and guidance for SQL Server on Linux, such as clustering and high availability/disaster recovery options (e.g., Pacemaker, Linux witness options).
  • Provide links to best practices for running SQL Server on Azure VMs with Linux, similar to the Windows-focused link currently present.
  • Clarify and expand on Azure Hybrid Benefit for Linux (RHEL/SLES), including migration/licensing scenarios and technical steps.
  • Ensure that migration strategies and readiness reports explicitly address both Windows and Linux SQL Server deployments, with clear instructions for each.
  • Add screenshots and walkthroughs for Linux-based SQL Server assessments and migrations where applicable.
GitHub Create Pull Request
Migrate https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/how-to-create-group-machine-dependencies-agentless.md ...https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/how-to-create-group-machine-dependencies-agentless.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page exhibits a notable Windows bias. PowerShell is the only command-line tool provided for managing agentless dependency analysis, with no Linux shell or cross-platform CLI alternatives. Windows-centric tools and patterns (such as PowerShell modules and cmdlets) are referenced exclusively for enabling/disabling features and exporting data. Instructions for credential requirements and permissions mention Windows accounts before Linux equivalents, and the overall flow assumes familiarity with Windows administration. There are no Linux shell (bash/ssh) examples, nor guidance for Linux-native management approaches.
Recommendations
  • Provide equivalent Linux shell (bash/ssh) command examples for managing agentless dependency analysis, including enabling/disabling features and exporting data.
  • Document cross-platform CLI alternatives (such as Azure CLI or REST API) for all PowerShell-based operations.
  • Present credential and permission requirements for Windows and Linux servers in parallel, rather than listing Windows first.
  • Include guidance for Linux administrators, such as using sudo, SSH keys, and Linux-native automation tools.
  • Clarify which steps are platform-agnostic and which require platform-specific tooling, ensuring Linux parity throughout.
GitHub Create Pull Request
Migrate https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/how-to-discover-applications.md .../main/articles/migrate/how-to-discover-applications.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example Powershell Heavy
Summary
The documentation demonstrates a Windows bias in several ways: Windows credentials and tools are mentioned first or exclusively in multiple sections, especially for SQL Server and File Server discovery. Windows-specific roles (IIS, File Server) and tools (Active Directory, SCCM, RDP, Exchange Server) are highlighted, often with limited or no Linux equivalents or examples. Linux credentials and requirements are mentioned but lack detailed guidance or parity in examples, especially for roles/features discovery and server management. There are no Linux-specific tool examples for file server discovery, and the documentation does not provide Linux command-line or shell examples, focusing instead on Windows and PowerShell-centric workflows.
Recommendations
  • Provide Linux-specific examples and workflows for all major discovery scenarios, including file server and web server roles (e.g., Samba, NFS, Apache, Nginx).
  • Include Linux command-line or shell script examples for credential provisioning and server management, alongside PowerShell/Windows examples.
  • Ensure Linux tools and patterns (e.g., SSH, systemd, SELinux, Linux package managers) are mentioned with equal prominence to Windows tools.
  • Clarify support for Linux file servers and web servers, including supported distributions and versions, and document any limitations.
  • Add guidance for discovering Linux-specific roles and features, such as system services, daemons, and package inventories.
  • Balance the order of presentation so that Linux and Windows are treated equally, rather than Windows-first.
  • Explicitly state any feature gaps or limitations for Linux environments, and provide workarounds or roadmap information where possible.
GitHub Create Pull Request
Migrate https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/how-to-create-group-machine-dependencies.md ...es/migrate/how-to-create-group-machine-dependencies.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation demonstrates a Windows bias in several ways: Windows installation instructions and tools are presented before Linux equivalents, with more detail and options (e.g., GUI, command line, scripts, and automation tools like Configuration Manager). Windows-specific tools and patterns (double-click installers, Configuration Manager, Intigua) are mentioned, while Linux instructions are minimal and lack parity in automation or scripting examples. There are no Linux-specific troubleshooting tips or advanced automation guidance, and references to supported operating systems focus more on Windows.
Recommendations
  • Present Windows and Linux instructions in parallel, giving equal detail and visibility to both platforms.
  • Include Linux automation options (e.g., Ansible, shell scripts, package managers) and provide example scripts for agent installation.
  • Mention Linux-specific tools and troubleshooting steps, such as systemd service checks, log file locations, or SELinux/AppArmor considerations.
  • Ensure that all references to supported operating systems and installation methods are equally detailed for Linux.
  • Provide links to Linux documentation and community resources, similar to those given for Windows.
  • Avoid Windows-first ordering; alternate or group instructions by platform for clarity.
GitHub Create Pull Request
Migrate https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/how-to-discover-sql-existing-project.md ...ticles/migrate/how-to-discover-sql-existing-project.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by prioritizing Windows-centric tools and patterns. PowerShell is mentioned as a requirement for discovery in VMware environments, and Windows/Domain credentials are referenced exclusively for authentication. There are no examples or instructions for Linux-based servers, nor is there mention of Linux-specific tools or credential patterns. The documentation assumes the use of Windows OS and Active Directory, with no guidance for Linux environments or non-Windows authentication methods.
Recommendations
  • Include explicit instructions and examples for discovering SQL Server instances on Linux-based servers.
  • Mention Linux-compatible tools and credential patterns (e.g., SSH, sudo, Linux user accounts) alongside Windows/Domain credentials.
  • Clarify whether the Azure Migrate appliance supports agentless discovery on Linux servers, and if so, provide steps for Linux environments.
  • Add references to Linux prerequisites (e.g., required packages, permissions) and troubleshooting steps.
  • Ensure parity in screenshots and walkthroughs by showing both Windows and Linux server scenarios.
GitHub Create Pull Request
Migrate https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/how-to-migrate-at-scale.md .../blob/main/articles/migrate/how-to-migrate-at-scale.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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 for automating Azure Migrate operations, with all example scripts using the .ps1 extension and no mention of Bash, shell, or Linux-native tooling. The script repository and usage instructions are Windows-centric, and there is no guidance or parity for Linux users or cross-platform scripting. The documentation implicitly assumes a Windows environment, which may exclude or hinder Linux administrators.
Recommendations
  • Provide equivalent Bash or shell script examples for Linux users, or clarify cross-platform compatibility of the PowerShell scripts (e.g., via PowerShell Core on Linux).
  • Explicitly mention how Linux users can run these scripts, including prerequisites for PowerShell on Linux and any platform-specific considerations.
  • Include links to Linux-native tools or Azure CLI alternatives where possible.
  • Reorder or balance examples so that Linux and Windows approaches are presented equally, or at least clarify that the documentation is Windows-focused and point Linux users to appropriate resources.
GitHub Create Pull Request
Migrate https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/how-to-register-appliance-using-entra-app.md ...s/migrate/how-to-register-appliance-using-entra-app.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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 strong Windows bias. All command-line examples for certificate generation, export, and registry modification use PowerShell, which is native to Windows. File paths and instructions reference Windows conventions (e.g., C:\Users\admin\Desktop), and certificate installation steps are described using Windows GUI dialogs. There are no equivalent Linux or cross-platform instructions, nor are Linux tools (e.g., OpenSSL) demonstrated, despite being mentioned as options. Registry modification is described using Windows Registry Editor and PowerShell, with no mention of Linux configuration methods.
Recommendations
  • Provide Linux-specific examples for certificate generation and export using OpenSSL and mkcert, including sample commands.
  • Include instructions for installing certificates on Linux appliances, referencing common distributions and certificate stores (e.g., /etc/ssl/certs, update-ca-certificates).
  • Describe how to configure appliance settings on Linux, such as using configuration files or environment variables instead of Windows Registry.
  • Use cross-platform file path examples and clarify steps that differ between Windows and Linux.
  • Ensure that Linux instructions are presented alongside Windows instructions, not only as an afterthought.
GitHub Create Pull Request
Migrate https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/how-to-migrate-vmware-vms-with-cmk-disks.md ...es/migrate/how-to-migrate-vmware-vms-with-cmk-disks.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools Windows First
Summary
The documentation page demonstrates a strong Windows bias. All command-line examples use Azure PowerShell, with no mention of Azure CLI, Bash, or Linux-native tools. References to creating disk encryption sets and deploying Resource Manager templates link to Windows-specific PowerShell guides. There are no Linux or cross-platform instructions, and the workflow assumes a Windows environment (e.g., file paths like C:\Users\Administrator\Downloads\template.json). The use of PowerShell is presented as the default and only option, with no parity for Linux users.
Recommendations
  • Provide equivalent Azure CLI and Bash examples for all PowerShell commands.
  • Include instructions and screenshots for Linux and macOS environments, especially for file paths and command execution.
  • Link to cross-platform documentation for creating disk encryption sets and deploying Resource Manager templates.
  • Clarify that Azure PowerShell is available on Linux and macOS, but also highlight Azure CLI as a fully supported alternative.
  • Add a section comparing PowerShell and Azure CLI usage for common migration tasks, helping users choose their preferred tool.
  • Avoid using Windows-specific file paths in examples; use generic or platform-agnostic paths.
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
High Priority View Details →
Scanned: 2026-01-08 00:53
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 frequently mentioning Windows servers, tools, and patterns before Linux equivalents. Examples and details for Windows (such as installed roles and features) are more explicit, while Linux instructions are less detailed and sometimes missing. Windows credential and permission requirements are described first and in more depth, and Windows-centric workloads (SQL Server, IIS, .NET) are highlighted, with limited mention of Linux alternatives or open-source stacks.
Recommendations
  • Provide equal detail and step-by-step examples for Linux server discovery, including credential setup and permissions.
  • Include Linux-specific inventory attributes and examples (e.g., Apache/Nginx web apps, MySQL/PostgreSQL databases) alongside Windows workloads.
  • List Linux instructions and requirements before or alongside Windows instructions, not after.
  • Expand documentation of software inventory for Linux servers, including installed packages and services, not just Windows roles/features.
  • Add troubleshooting and remediation steps for common Linux discovery issues, similar to those provided for Windows.
  • Ensure screenshots and UI examples show both Windows and Linux scenarios.
GitHub Create Pull Request
Migrate https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/how-to-review-sql-assessment.md .../main/articles/migrate/how-to-review-sql-assessment.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits a Windows bias by exclusively referencing Windows-based SQL Server deployments and migration scenarios. All examples, best practices, and links are tailored to Windows environments (e.g., SQL Server on Azure VM with Windows, Windows-specific performance guidelines, and cluster best practices). There is no mention of Linux-based SQL Server deployments, migration from Linux servers, or Linux-specific considerations, tools, or examples.
Recommendations
  • Include explicit guidance and examples for migrating SQL Server instances running on Linux to Azure targets.
  • Reference and link to Linux-specific best practices for SQL Server on Azure VM (e.g., /azure/azure-sql/virtual-machines/linux/performance-guidelines-best-practices-checklist).
  • Clarify whether the assessment and recommendations apply to both Windows and Linux SQL Server sources, and note any differences.
  • Add sections or notes on Linux-specific storage, compute, and high availability configurations (e.g., Pacemaker clusters, Linux disk mapping).
  • Provide parity in migration steps and remediation guidance for Linux environments.
GitHub Create Pull Request
← Previous Page 15 of 37 Next →