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 151-175 of 218 flagged pages
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation for Azure Migrate Appliance FAQ demonstrates a notable Windows bias. Deployment and management instructions rely heavily on PowerShell scripts, with no Linux shell or macOS alternatives provided. Troubleshooting and update procedures reference Windows-specific tools (e.g., certificate manager, group policy editor, Windows Update), and all screenshots and examples are Windows-centric. There is no guidance for Linux-based appliance management, nor are Linux equivalents for certificate or update management discussed.
Recommendations
- Provide Linux/macOS shell script alternatives for appliance deployment and management, or clarify if the appliance must run on Windows.
- Include troubleshooting steps for certificate validation and MSI updates using Linux tools (e.g., OpenSSL, update-ca-certificates).
- Add explicit statements about OS requirements and support, including whether Linux-based appliances are supported.
- Offer parity in examples and screenshots, showing Linux equivalents where possible.
- Document how to keep the appliance OS updated if running on Linux, and clarify update mechanisms for non-Windows environments.
Create Pull Request
Migrate
Common Questions About the Migration and Modernization Tool
.../articles/migrate/common-questions-server-migration.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page exhibits several forms of Windows bias. Bandwidth throttling and scheduling examples are provided exclusively using Windows PowerShell and Windows scheduled tasks, with no Linux equivalents or cross-platform alternatives. Windows-centric tools and commands (e.g., NetQosPolicy, scheduled tasks) are referenced without mention of Linux-native approaches. Windows operating systems and migration scenarios are described in greater detail and often appear first in lists and tables. There are no Linux shell or tool examples for common migration tasks, and Linux-specific migration limitations (e.g., OS upgrade during migration) are noted but not addressed with alternatives.
Recommendations
- Provide Linux equivalents for PowerShell and scheduled task examples, such as using tc, iptables, or cron for bandwidth throttling and scheduling.
- Include cross-platform instructions or note differences for both Windows and Linux appliances where relevant.
- Offer bash or shell script examples for migration-related automation and bandwidth management.
- Present OS support tables and migration scenarios in a neutral order or alternate which OS is listed first.
- Clarify Linux-specific limitations and suggest alternative migration strategies or tools for Linux users.
Migrate
Azure VM assessments in Azure Migrate
...in/articles/migrate/concepts-assessment-calculation.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Heavy
Missing Linux Example
Summary
The documentation page exhibits a Windows bias by listing Windows operating systems and readiness details first, providing exhaustive information about Windows versions and their support status, while Linux is covered in a single, less detailed row with a link out for specifics. There are no Linux-specific examples, troubleshooting steps, or detailed readiness tables, and macOS/other OSes are mentioned only briefly. The appliance's data collection and assessment logic are described generically, but Windows scenarios dominate the narrative and examples.
Recommendations
- Provide a detailed table for Linux distributions, including common readiness issues, support status, and migration caveats, similar to the Windows OS table.
- Include Linux-specific examples and troubleshooting steps for assessment and migration, such as handling kernel versions, disk partitioning, and network adapter compatibility.
- Mention Linux tools or commands (e.g., for gathering performance data, verifying readiness) alongside or before Windows equivalents.
- Clarify how the appliance collects Linux metadata and performance data, including any required permissions or agent installations.
- Add parity for macOS and other non-Windows OSes, even if only to clarify limitations or provide migration alternatives.
Migrate
Azure SQL assessments in Azure Migrate Discovery and assessment tool
...s/migrate/concepts-azure-sql-assessment-calculation.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Powershell Heavy
Summary
The documentation page demonstrates a notable Windows bias. Windows-centric concepts, such as Windows Server Failover Clusters, Cloud Witness, and references to Windows-specific best practices, are mentioned exclusively or before any Linux equivalents. Links and examples for SQL Server on Azure VM sizing and migration consistently point to Windows-focused resources. There is no mention of Linux-based SQL Server deployments, nor are there examples or guidance for Linux users. The documentation assumes Windows as the default environment for SQL Server, clustering, and migration scenarios.
Recommendations
- Include explicit guidance and examples for SQL Server deployments on Linux, including migration steps and best practices.
- Reference Linux-specific clustering and high availability options (e.g., Pacemaker, Corosync) alongside Windows Failover Clusters.
- Provide parity in links and documentation for both Windows and Linux SQL Server environments, including performance guidelines and migration checklists.
- Clarify which features and recommendations apply to Linux-based SQL Server instances, and note any differences or limitations.
- Add Linux command-line examples (e.g., Bash, systemctl) where PowerShell is referenced.
- Mention Linux licensing options and Azure Hybrid Benefit applicability for Enterprise Linux subscriptions more prominently.
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by focusing heavily on Windows Server and SQL Server licensing, extended security updates, and management tools (e.g., System Center). Linux is mentioned only in passing, with no details on Linux-specific licensing, management, or security costs. Most examples, formulas, and cost breakdowns are tailored to Windows environments, and Windows-related components are listed before Linux equivalents. There are no examples or guidance for Linux workloads, tools, or migration scenarios.
Recommendations
- Add explicit examples and cost breakdowns for Linux workloads, including licensing, management, and security costs.
- Include Linux-first or Linux-parity scenarios in migration strategies and TCO calculations.
- Describe management and monitoring options for Linux servers, such as integration with Azure Monitor, Update Manager, and Defender for Cloud.
- Provide guidance for migrating Linux-based applications and databases (e.g., PostgreSQL, MySQL) to Azure PaaS/IaaS offerings.
- Ensure Linux licensing and support costs are detailed alongside Windows costs in tables and formulas.
- Balance the order of presentation so Linux is not always listed after Windows.
Migrate
Build a migration plan with Azure Migrate
...b/main/articles/migrate/concepts-migration-planning.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page exhibits a moderate Windows bias. Windows Server and SQL Server are referenced repeatedly, with specific migration and upgrade guidance for Windows OS. The only OS upgrade example is for Windows Server, and the Azure Hybrid Benefit is explained first in terms of Windows licenses. There are no explicit Linux migration/upgrade examples, nor are Linux-specific blockers or patterns discussed. Windows operating systems are mentioned before Linux in cost-saving options, and the only detailed OS upgrade workflow is for Windows.
Recommendations
- Add explicit examples and guidance for migrating Linux servers, including common distributions (e.g., Ubuntu, RHEL, CentOS).
- Include Linux OS upgrade scenarios, or clarify if/when Azure Migrate supports in-place upgrades for Linux VMs.
- Discuss Linux-specific blockers, readiness checks, and remediation guidance alongside Windows examples.
- When listing cost-saving options (e.g., Azure Hybrid Benefit), present Windows and Linux options with equal prominence.
- Ensure that tables and quick-win recommendations include Linux operating systems reaching end-of-support.
- Reference Linux database migration scenarios (e.g., MySQL, PostgreSQL) in addition to SQL Server.
Migrate
Agentless Replication of VMware Virtual Machines
...rticles/migrate/concepts-vmware-agentless-migration.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page exhibits a Windows bias in several areas. It provides only Windows PowerShell examples (e.g., NetQosPolicy for bandwidth throttling), references Windows-specific services and file paths (such as C:\ProgramData\Microsoft Azure\Config), and omits Linux/macOS equivalents or instructions. The configuration and management sections assume the Azure Migrate appliance is running on Windows, with no mention of Linux support or alternative commands and file locations. This bias may create friction for users operating in Linux environments or seeking cross-platform guidance.
Recommendations
- Include Linux/macOS equivalents for all PowerShell commands, such as using tc, iptables, or other Linux-native tools for bandwidth throttling.
- Document alternative file paths and configuration steps for Linux-based Azure Migrate appliances, if supported (e.g., /etc/azure-migrate/).
- Clarify whether the Azure Migrate appliance can run on Linux, and if so, provide parity in examples and instructions.
- Present cross-platform examples side-by-side or indicate platform-specific steps clearly.
- Reference Linux backup tools (e.g., rsync, Borg, etc.) alongside VEEAM when discussing snapshot conflicts.
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias, especially in the section describing how to use the Az CLI. It instructs users to open PowerShell as Administrator and execute CLI commands, without mentioning Linux/macOS terminals or providing equivalent instructions. The CLI examples are presented in a Windows-centric context, and there is no guidance for Linux/macOS users regarding terminal usage, privilege elevation, or command syntax differences. The rest of the documentation is largely portal-based and platform-agnostic, but the CLI section creates friction for non-Windows users.
Recommendations
- Explicitly mention that Az CLI can be used on Linux, macOS, and Windows, and provide instructions for opening a terminal on each platform.
- Replace 'open PowerShell on your system as an Administrator' with platform-neutral language such as 'open your terminal (PowerShell on Windows, Terminal on Linux/macOS)'.
- Clarify privilege elevation steps for Linux/macOS (e.g., using 'sudo' if required) alongside Windows instructions.
- Provide example CLI commands in a platform-agnostic format, and note any differences in command syntax or environment.
- Add links to Az CLI installation instructions for Linux and macOS, not just Windows.
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias: Windows examples, tools, and PowerShell cmdlets are frequently listed first and in greater detail, especially for software inventory, features, pending updates, and storage metadata. Windows-specific technologies (WMI, PowerShell, registry) are described with explicit keys and cmdlets, while Linux equivalents are often summarized as 'commands' or generic file accesses, sometimes lacking parity in detail or explanation. Some sections (ASP.NET, Java, Spring Boot web app data) only mention Windows servers, omitting Linux scenarios. The overall structure and depth favor Windows, creating friction for Linux/macOS users.
Recommendations
- Present Linux and Windows examples side-by-side or alternate which is shown first.
- Expand Linux sections to match the detail of Windows (e.g., list specific commands for feature discovery, pending updates, and storage metadata).
- For web app discovery, clarify Linux support or add equivalent Linux scenarios (e.g., Apache, Nginx, Tomcat on Linux).
- Where Windows registry or PowerShell is referenced, provide Linux config file paths or shell commands.
- Explicitly state platform limitations or parity in each section.
- Add macOS notes if supported or clarify lack of support.
Migrate
Discover and assess using Azure Private Link
...migrate/discover-and-assess-using-private-endpoints.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page exhibits a notable Windows bias. All appliance installation and configuration instructions are provided exclusively for Windows environments, specifically referencing PowerShell and Windows file paths. There are no examples or instructions for Linux or macOS users, nor is there mention of Linux-compatible installer scripts or alternative deployment methods. The use of Windows-centric tools (PowerShell, C:\ paths) and the absence of Linux equivalents create friction for non-Windows users.
Recommendations
- Provide Linux/macOS installation instructions for the Azure Migrate appliance, including shell script examples and relevant commands.
- Clarify whether the installer script is compatible with Linux and, if not, offer a Linux-specific installer or containerized deployment option.
- Include Linux file path examples and troubleshooting steps for common Linux environments.
- Mention prerequisites and steps for running the appliance on Linux (e.g., required packages, permissions, service management).
- Add screenshots or CLI examples for Linux where applicable.
Migrate
Automate agentless VMware migrations in Azure Migrate
...lob/main/articles/migrate/how-to-automate-migration.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation is heavily focused on PowerShell-based automation, with all examples, instructions, and tooling centered around PowerShell scripts (.ps1) and the Azure PowerShell module. There is no mention of Bash, Linux/macOS-compatible scripting, or cross-platform alternatives. The installation instructions and script execution syntax assume a Windows/PowerShell environment, creating friction for Linux/macOS users.
Recommendations
- Provide Bash or cross-platform (e.g., Azure CLI, Python) equivalents for key automation steps.
- Clarify whether the PowerShell scripts are compatible with PowerShell Core on Linux/macOS and provide installation guidance for those platforms.
- Include explicit instructions for running the scripts on Linux/macOS, including prerequisites and troubleshooting tips.
- Offer sample scripts or automation workflows using Azure CLI or REST API for users who prefer non-PowerShell environments.
- Reorder or balance examples so that Linux/macOS options are presented alongside or before Windows-specific instructions.
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias. It references Windows-specific tools and patterns, such as Windows Server Failover Clusters and Cloud Witness, without mentioning Linux equivalents or alternatives. Links to performance guidelines and high availability documentation are Windows-focused, and there are no examples or guidance for Linux-based SQL Server deployments. The Azure Hybrid Benefit section mentions RHEL and SLES, but only in the context of licensing, not migration or assessment specifics. Overall, Linux users are left without clear instructions or parity in migration scenarios, especially for high availability and disaster recovery configurations.
Recommendations
- Add explicit guidance and examples for assessing and migrating Linux-based SQL Server deployments.
- Include links to Linux-specific performance and high availability best practices for SQL Server on Azure VMs.
- When discussing high availability and disaster recovery, mention Linux clustering options (e.g., Pacemaker) and how to configure them in Azure.
- Provide parity in screenshots and step-by-step instructions for Linux environments where applicable.
- Clarify any differences in assessment or migration steps for Linux SQL Server instances.
Migrate
Set up agent-based dependency analysis in Azure Migrate
...es/migrate/how-to-create-group-machine-dependencies.md
Medium Priority
View Details →
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 tools (Configuration Manager, Intigua, a Windows-focused install script). Linux instructions are more terse, lacking equivalent detail, automation options, or troubleshooting guidance. Windows-centric terminology (OMS, MMA) is used throughout, and Windows tools are mentioned without Linux alternatives. Linux users may need to infer steps or seek external resources.
Recommendations
- Present Linux and Windows instructions with equal detail and prominence, alternating order or grouping by OS.
- Provide Linux automation options (e.g., sample install scripts, Ansible, shell commands) similar to Windows Configuration Manager/Intigua references.
- Include troubleshooting steps and supported OS lists for Linux as done for Windows.
- Reference Linux-native tools or package managers (e.g., apt, yum) for agent installation.
- Clarify terminology and ensure that cross-platform compatibility is explicitly addressed.
- Add screenshots or step-by-step guides for Linux where Windows GUI steps are shown.
Migrate
Migrate VMware virtual machines to Azure with server-side encryption(SSE) and customer-managed keys(CMK) using the Migration and modernization tool
...es/migrate/how-to-migrate-vmware-vms-with-cmk-disks.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation exclusively uses Azure PowerShell for all command-line examples, with no mention of Azure CLI, Bash, or cross-platform alternatives. All example scripts and referenced tutorials are PowerShell-based, and the instructions assume a Windows-centric workflow. There are no Linux/macOS-specific notes, nor are Linux-friendly tools or commands provided.
Recommendations
- Provide equivalent Azure CLI examples for all PowerShell commands, as Azure CLI is cross-platform and widely used on Linux/macOS.
- Explicitly mention that the steps can be performed on Linux/macOS and provide guidance for those environments.
- Add Bash script examples or instructions for editing/deploying Resource Manager templates from Linux/macOS.
- Reference Azure CLI documentation links alongside PowerShell links.
- Clarify any platform-specific requirements or limitations, if present.
Migrate
Review Discovered Inventory (Preview) in Azure Migrate
...articles/migrate/how-to-review-discovered-inventory.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates a mild Windows bias. Windows servers, tools, and patterns are mentioned first or exclusively in several places, such as credential requirements, software inventory, and workload types. Windows-specific features (like installed roles and features) are called out, while Linux equivalents are less detailed or omitted. Examples and terminology often prioritize Windows, with Linux mentioned as an alternative rather than an equal. There are no explicit Linux command examples or detailed Linux-specific troubleshooting steps.
Recommendations
- Provide Linux-specific examples and troubleshooting steps where Windows details are given (e.g., software inventory, credential setup).
- Include parity in descriptions of features for Linux servers, such as installed packages, services, and configuration details.
- Ensure that Linux tools, permissions, and patterns are described with the same depth as Windows (e.g., clarify how to gather dependency data and inventory on Linux).
- Alternate the order of Windows and Linux mentions to avoid Windows-first bias.
- Add explicit Linux/macOS screenshots and walkthroughs where only Windows UI is shown.
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 →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias, primarily through heavy reliance on PowerShell for management tasks and examples, and by mentioning Windows credentials and permissions before Linux equivalents. Windows tools (PowerShell, Power BI) are used exclusively for scripting and visualization, with no Linux/macOS CLI or tool alternatives provided. Linux instructions are present but less detailed and always secondary.
Recommendations
- Provide equivalent Linux/macOS CLI examples for managing dependencies, such as using Azure CLI or REST API calls.
- Include instructions for installing and using the Azure Migrate PowerShell module on Linux/macOS (via PowerShell Core), or suggest alternative management methods.
- Offer guidance for exporting and visualizing dependency data using open-source tools available on Linux/macOS, not just Power BI.
- When discussing credentials and permissions, present Linux and Windows requirements in parallel rather than Windows-first.
- Add troubleshooting and validation steps specific to Linux environments.
Migrate
Discover SQL Server instances in an existing Azure Migrate project
...ticles/migrate/how-to-discover-sql-existing-project.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias. It references PowerShell and Windows credentials as prerequisites for discovery, and all examples and instructions are tailored to Windows environments. There is no mention of Linux-specific discovery steps, tools, or credential formats, nor are Linux/macOS equivalents provided. The documentation assumes the use of Windows servers and Active Directory, and does not address scenarios where SQL Server may be running on Linux or where the appliance is deployed on a Linux host.
Recommendations
- Add explicit instructions and examples for discovering SQL Server instances on Linux hosts, including supported authentication methods and credential formats.
- Clarify whether the Azure Migrate appliance supports Linux-based deployments and, if so, provide setup and troubleshooting steps for Linux environments.
- Include Linux/macOS command-line alternatives to PowerShell where relevant, such as Bash scripts or CLI commands.
- Mention any Linux-specific requirements (e.g., SSH keys, sudo privileges) for discovery and assessment.
- Ensure screenshots and walkthroughs include Linux scenarios where applicable.
Migrate
Review SQL assessment with Azure Migrate | Microsoft Docs
.../main/articles/migrate/how-to-review-sql-assessment.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias. It consistently references SQL Server on Azure VM (a Windows-centric deployment), links only to Windows-specific best practices, and omits any mention of Linux-based SQL Server deployments or migration scenarios. All referenced guidance and examples are tailored to Windows environments, with no Linux parity or alternative instructions.
Recommendations
- Include explicit guidance and examples for migrating SQL Server running on Linux to Azure SQL targets.
- Reference and link to Linux-specific best practices for SQL Server on Azure VM (e.g., /azure/azure-sql/virtual-machines/linux/).
- Clarify whether Azure Migrate supports SQL Server on Linux and, if so, provide parity in assessment and migration steps.
- Add notes or sections that address differences in migration, sizing, and readiness for Linux-based SQL Server instances.
- Ensure that recommendations and remediation guidance are not exclusively tailored to Windows environments.
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. Windows migration steps are presented first and in greater detail, with explicit command-line and PowerShell examples, screenshots, and references to Windows-specific tools (diskpart, registry editor, PowerShell). Linux instructions are present but less detailed, with fewer explicit command examples, less visual guidance, and some steps (e.g., rebuilding initrd) left to distribution documentation. Windows tooling and patterns (e.g., PowerShell, diskpart) are shown before Linux equivalents, and Linux examples are less comprehensive.
Recommendations
- Alternate the order of Windows and Linux sections or present both in parallel for each step.
- Provide Linux command-line examples for all manual steps, including network configuration, DHCP setup, and agent installation, similar to the Windows PowerShell examples.
- Add screenshots or terminal output examples for Linux steps, matching the visual guidance given for Windows.
- Reference Linux-specific documentation and troubleshooting guides as prominently as Windows ones.
- Clarify distribution-specific instructions for common Linux distros (e.g., Ubuntu, RHEL, SUSE) where procedures differ.
Migrate
Set up an Azure Migrate appliance for server assessment in a VMware environment
...ain/articles/migrate/how-to-set-up-appliance-vmware.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation demonstrates a moderate Windows bias. The PowerShell installer script is mentioned as an alternative to the OVA template, but no Linux shell or bash equivalent is referenced. The VDDK installation instructions specify a Windows path (C:\Program Files\VMware\VMware Virtual Disk Development Kit) and do not mention Linux installation steps or paths. Credential examples and validation focus on Windows domain and non-domain accounts, with Linux credentials mentioned only in passing and without detailed guidance. Windows authentication and IIS web server discovery are described in detail, while Linux-specific scenarios (such as Apache/Nginx web server discovery or Linux authentication) are not covered.
Recommendations
- Provide Linux shell (bash) installer script instructions alongside PowerShell, or clarify Linux support and limitations.
- Include VDDK installation steps and default paths for Linux systems.
- Offer detailed examples for Linux credential setup and validation, including troubleshooting steps.
- Expand discovery instructions to cover common Linux scenarios (e.g., Apache/Nginx web server discovery, Linux authentication methods).
- Ensure parity in screenshots and UI descriptions for Linux-based appliances where applicable.
Migrate
Review a business case with Azure Migrate | Microsoft Docs
...b/main/articles/migrate/how-to-view-a-business-case.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page exhibits a moderate Windows bias. Cost and licensing examples focus heavily on Windows Server and SQL Server, with extended security updates and Azure Hybrid Benefit discussed only in the context of Windows workloads. Licensing cost breakdowns and savings calculations reference Windows licenses and SQL licenses, with no mention of Linux or open-source equivalents. There are no examples or cost models for Linux workloads, nor is there guidance for users migrating Linux servers. The documentation assumes Windows-centric infrastructure and tools, and does not provide parity for Linux or non-Microsoft environments.
Recommendations
- Include explicit examples and cost breakdowns for Linux workloads (e.g., Ubuntu, Red Hat, CentOS) in all relevant sections.
- Discuss licensing, migration strategies, and security/management benefits for Linux servers, including open-source databases.
- Add references to Linux-specific Azure migration tools and patterns (e.g., Azure Migrate appliance for Linux, Linux VM migration guides).
- Clarify which features (such as Azure Hybrid Benefit, Extended Security Updates) are Windows-only and provide Linux alternatives or note their irrelevance.
- Ensure screenshots and report breakdowns show both Windows and Linux server distributions and costs.
Migrate
Support for Hyper-V migration in Azure Migrate
...es/migrate/migrate-support-matrix-hyper-v-migration.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Summary
The documentation page exhibits a moderate Windows bias. Hyper-V migration is inherently a Windows-centric scenario, but the documentation consistently lists Windows requirements and tools first, such as Windows Server versions, .NET Framework, and Windows-specific firewall/RDP instructions. Linux instructions are present but less detailed and often follow Windows guidance. URL access examples reference Windows time servers and domains. There are no explicit PowerShell examples, but the overall pattern prioritizes Windows environments and tooling.
Recommendations
- Provide Linux-specific examples and troubleshooting steps with equal detail, especially for firewall, SSH, and disk partitioning requirements.
- List Linux and Windows requirements side-by-side in tables where possible, rather than Windows-first.
- Include references to Linux equivalents for system prerequisites (e.g., .NET alternatives, Linux host requirements if relevant).
- Clarify any steps that differ for Linux VMs, such as boot partition handling, and provide links to Linux migration guides.
- If PowerShell or Windows tools are referenced, offer Bash or Linux command alternatives.
Migrate
Troubleshoot Azure Migrate appliance diagnostic
.../articles/migrate/troubleshoot-appliance-diagnostic.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by referencing Windows-specific file paths (e.g., C:\Users\Public\Desktop\DiagnosticsReport), mentioning Windows Server evaluation licenses, and omitting any Linux-based examples or instructions. There is no mention of Linux or macOS equivalents for running diagnostics, saving reports, or license checks, which may confuse or exclude users running the appliance on non-Windows platforms.
Recommendations
- Explicitly state platform requirements for the Azure Migrate appliance (e.g., if only Windows is supported, clarify this early).
- If Linux-based appliances are supported, provide equivalent instructions and file paths for Linux (e.g., where reports are saved, how to access them).
- Include examples or screenshots for Linux/macOS environments if applicable.
- Clarify whether OS license checks apply only to Windows-based appliances, and provide guidance for Linux-based deployments if supported.
- Avoid using Windows-specific terminology or tools without mentioning alternatives for other platforms.
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 →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation is focused exclusively on Hyper-V environments, which are Windows-centric. There are no Linux or cross-platform examples, and all instructions assume the use of Windows-based tools and workflows. Linux alternatives or parity considerations are not mentioned, and the documentation does not address scenarios for Linux-based hypervisors or management tools.
Recommendations
- Clarify in the introduction that the tutorial is specific to Hyper-V (Windows) environments, and provide links to equivalent guides for Linux-based virtualization platforms (e.g., KVM, Xen, VMware on Linux).
- Add a section or cross-reference for users managing Linux VMs or using Linux-based hypervisors, outlining how to assess and migrate those workloads with Azure Migrate.
- Where possible, mention any Linux-specific considerations (such as licensing, Azure Hybrid Benefit for Enterprise Linux, or agent installation on Linux VMs) to improve parity.
- Ensure that future documentation for Azure Migrate covers both Windows and Linux scenarios equally, with examples and screenshots for each.
Migrate
Assess ASP.NET/Java web apps for migration to Azure Kubernetes Service
...ob/main/articles/migrate/tutorial-assess-aspnet-aks.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias, particularly in the ASP.NET assessment flow. It references Windows-based node pools as a requirement for ASP.NET apps, and optimization guidance is focused on Windows Dockerfiles. There is no mention of Linux node pools or Linux containerization for ASP.NET, nor are Linux-specific tools or patterns discussed. Examples and screenshots are generic, but the cost breakdown and next steps emphasize Windows environments, with no Linux parity guidance for ASP.NET users.
Recommendations
- Add explicit guidance for ASP.NET Core apps that can run on Linux node pools, including cost and readiness assessment examples.
- Include references and links to optimizing Linux Dockerfiles and containerization best practices for both ASP.NET and Java apps.
- Clarify when Windows node pools are required (e.g., for ASP.NET Framework) and when Linux node pools are supported (e.g., for ASP.NET Core), with examples.
- Ensure that next steps and optimization links include Linux-focused resources and best practices.
- Provide parity in screenshots and instructions for Linux-based environments where applicable.