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 451-475 of 918 flagged pages
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 →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by referencing Windows-specific tools, patterns, and best practices (e.g., Windows Server Failover Clusters, Cloud Witness, and links to Windows-specific performance guidelines) without mentioning or providing equivalent Linux guidance. There are no Linux-specific examples, instructions, or references for scenarios such as SQL Server on Linux, Linux-based failover clustering, or migration from Linux SQL Server environments. The documentation assumes a Windows-centric environment throughout.
Recommendations
- Include explicit guidance and examples for assessing and migrating SQL Server instances running on Linux, including supported distributions and any differences in data collection or assessment.
- Reference Linux-based high availability and disaster recovery patterns (e.g., Pacemaker clusters) alongside Windows Server Failover Clusters.
- Provide links to Linux-specific best practices for SQL Server on Azure VMs, such as /azure/azure-sql/virtual-machines/linux/performance-guidelines-best-practices-checklist.
- Clarify whether the Azure Migrate appliance supports discovery and assessment of SQL Server on Linux, and if so, provide setup instructions for Linux environments.
- When mentioning tools like Cloud Witness or Shared Disk for Windows clusters, also mention Linux alternatives or note any limitations.
- Ensure that all example links, especially those under 'Learn more' and 'best practices', have Linux equivalents or clearly state platform applicability.
Create Pull Request
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/troubleshoot-appliance-diagnostic.md
.../articles/migrate/troubleshoot-appliance-diagnostic.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation 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 mention of Linux-based appliances or examples. There are no Linux/Unix file paths, commands, or troubleshooting steps, and all instructions assume a Windows environment.
Recommendations
- Include equivalent instructions and file paths for Linux-based Azure Migrate appliances, if supported.
- Mention whether the diagnostic tool and appliance are available for Linux, and provide parity in troubleshooting steps.
- If Linux is not supported, explicitly state this early in the documentation to set user expectations.
- Add examples or screenshots for Linux environments where applicable.
- Reference Linux tools or patterns (e.g., systemd, /var/log, shell commands) alongside Windows ones.
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 →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by focusing exclusively on ASP.NET web apps running on IIS (a Windows technology) and omitting explicit mention or examples of Linux-based web app scenarios. There are no Linux-specific instructions, tools, or examples, and the only server technology mentioned for Java is Tomcat, without clarifying if Linux deployments are supported or how to assess them. The documentation also references Windows App Service SKUs and pricing, with no mention of Linux App Service plans or differences.
Recommendations
- Include explicit examples and instructions for assessing Linux-based web apps (e.g., Node.js, Python, PHP, Java on Linux).
- Mention and link to Azure App Service for Linux documentation and pricing details.
- Clarify whether the Azure Migrate appliance supports discovery and assessment of Linux web servers (e.g., Apache, Nginx, Tomcat on Linux) and provide steps if supported.
- Provide parity in assessment workflows and screenshots for both Windows and Linux scenarios.
- List both Windows and Linux App Service SKUs and note any differences in features, compatibility, or pricing.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/common-questions-appliance.md
...ob/main/articles/migrate/common-questions-appliance.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation for the Azure Migrate appliance demonstrates a strong Windows bias. Deployment and management instructions are centered around PowerShell scripts, with no mention of Bash or Linux-native alternatives. Troubleshooting and certificate management steps are exclusively shown using Windows UI tools (e.g., Certificate Manager, Group Policy Editor), and all screenshots are from Windows environments. There are no examples or instructions for deploying, managing, or troubleshooting the appliance from a Linux or cross-platform perspective, despite the appliance being able to discover Linux servers. Linux tools, commands, or workflows are not mentioned, and Windows-specific paths and patterns (e.g., %ProgramData%, C:\Program Files) are used throughout.
Recommendations
- Provide equivalent Bash or shell script instructions for deploying and managing the appliance on Linux-based hosts, or clarify if only Windows is supported for appliance management.
- Include troubleshooting steps and screenshots for certificate validation and MSI signature checking on Linux (e.g., using openssl, certutil, or other Linux tools).
- Document how to perform appliance updates, certificate management, and log collection on Linux-based appliances, if supported.
- When referencing file paths or environment variables, include Linux equivalents (e.g., /var/lib/, /opt/, $HOME) alongside Windows paths.
- Explicitly state OS requirements and clarify if the appliance or its management tools are Windows-only, or provide Linux support guidance if available.
- Add examples and guidance for Linux administrators, including how to provide Linux credentials, manage agent health, and troubleshoot common issues from a Linux perspective.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/appcat/dotnet.md
...azure-docs/blob/main/articles/migrate/appcat/dotnet.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by prioritizing Visual Studio (a Windows-only tool) and providing detailed installation and usage instructions for it before mentioning the cross-platform .NET CLI tool. The prerequisites for the Visual Studio extension explicitly require Windows, and there are no Linux-specific examples, troubleshooting tips, or mentions of Linux development environments. All screenshots and workflows are centered around Windows tools and UI.
Recommendations
- Add explicit instructions and examples for using the .NET CLI tool on Linux and macOS, including installation, usage, and troubleshooting steps relevant to those platforms.
- Reorganize the documentation to present the CLI tool (which is cross-platform) before or alongside the Visual Studio extension, emphasizing its suitability for Linux and macOS users.
- Include screenshots or terminal output examples from Linux environments to demonstrate parity.
- Mention any platform-specific considerations or limitations for Linux users, such as supported shells, file paths, or dependencies.
- Clarify that Visual Studio Code (which is cross-platform) can be used for editing .NET projects, and provide guidance for integrating the CLI tool into VS Code workflows.
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 →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by prioritizing Windows Server and SQL Server in cost calculations, licensing, and management tooling (e.g., System Center), with limited or no mention of Linux-specific scenarios, tools, or licensing. While Linux is briefly mentioned in license amortization and support, there are no detailed examples, cost breakdowns, or management considerations for Linux servers. Windows-centric tools and patterns (e.g., System Center, Windows ESU, Azure Hybrid Benefit for Windows) are described in detail, while Linux equivalents are absent.
Recommendations
- Include explicit examples and cost breakdowns for Linux servers, including common Linux distributions and their licensing/support models.
- Describe management tooling and monitoring options for Linux (e.g., integration with Azure Monitor, Update Management, and third-party tools commonly used in Linux environments).
- Add Linux-specific migration considerations, such as support for open-source databases, web servers, and application stacks.
- Ensure parity in describing extended support and security update options for Linux distributions (e.g., Ubuntu ESM, RHEL ELS) where applicable.
- Provide sample .csv import templates or appliance setup instructions that reference both Windows and Linux server scenarios.
- Balance the discussion of Windows and Linux in all tables and examples, ensuring Linux is not only mentioned but given equal detail.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/common-questions-server-migration.md
.../articles/migrate/common-questions-server-migration.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation demonstrates a Windows bias, particularly in operational examples and tooling. PowerShell and Windows-specific tools (e.g., NetQosPolicy, Windows Scheduled Tasks) are used exclusively in example scripts for bandwidth throttling, with no Linux equivalents provided. The guidance for operational tasks like scripting, automation, and bandwidth management is Windows-centric. Additionally, Windows OS upgrade during migration is supported and documented, while Linux OS upgrade is explicitly stated as unsupported, with no roadmap or workaround. In several sections, Windows scenarios and tools are mentioned before Linux, and Linux-specific migration nuances are less detailed.
Recommendations
- Provide equivalent Linux-based examples for operational tasks such as bandwidth throttling (e.g., using tc, wondershaper, or iptables on Linux).
- Include Linux shell script examples alongside PowerShell for automation and scheduled tasks (e.g., using cron jobs).
- Document any Linux-specific migration caveats, best practices, or troubleshooting steps with the same depth as Windows.
- Clarify Linux OS upgrade support status and, if unsupported, provide guidance or workarounds for Linux users.
- When listing supported operating systems or migration scenarios, alternate the order or present Linux and Windows options with equal prominence.
- Reference cross-platform tools where possible, or explicitly state when a feature is Windows-only and suggest alternatives for Linux.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/start-here-vmware.md
...e-docs/blob/main/articles/migrate/start-here-vmware.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by providing migration automation and command-line examples exclusively with Azure PowerShell, without mentioning or linking to equivalent Azure CLI or Linux-native tooling. The focus on PowerShell for automation and migration tasks, and the absence of Linux/CLI alternatives, may disadvantage users operating from Linux or cross-platform environments.
Recommendations
- Include Azure CLI examples and tutorials alongside PowerShell for all migration and automation steps.
- Explicitly mention that migration can be performed from Linux/macOS environments using Azure CLI, and provide links to relevant documentation.
- Where automation is discussed, offer both PowerShell and Bash/CLI scripts to ensure parity.
- Review referenced tutorials to ensure they are not Windows/PowerShell exclusive, or add Linux/CLI alternatives if missing.
- Add a section or note clarifying cross-platform support and tools for the migration process.
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 →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation consistently presents Windows-specific tools, commands, and patterns first or exclusively, especially in sections about software inventory, storage, and application discovery. Windows-centric technologies (WMI, PowerShell, Registry, Windows Features) are detailed with specific commands and properties, while Linux equivalents are sometimes grouped together or described in less detail. Some advanced features (e.g., ASP.NET, Spring Boot, Java web app data) are described only for Windows servers, with no mention of Linux support or parity.
Recommendations
- For each section that provides Windows-specific commands (e.g., PowerShell, WMI, Registry), ensure Linux equivalents are given with equal detail and prominence.
- Reorder sections so that Linux and Windows examples are presented together, or alternate which OS is presented first to avoid implicit prioritization.
- Where advanced application discovery (e.g., Java/Spring Boot web apps) is described only for Windows, clarify whether Linux is unsupported or provide Linux-specific collection details if available.
- For storage and feature discovery, provide Linux-specific commands (e.g., for NFS, SMB, disk enumeration) alongside Windows PowerShell cmdlets.
- In summary tables, ensure Linux and Windows data collection methods are described with similar granularity and clarity.
- Explicitly state any limitations or differences in Linux support, rather than omitting Linux details.
- Where only Windows tools (e.g., Get-WindowsFeature, Get-SmbShare) are mentioned, add corresponding Linux commands (e.g., systemctl, exportfs, showmount, etc.) or note if not applicable.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/troubleshoot-assessment.md
.../blob/main/articles/migrate/troubleshoot-assessment.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation exhibits a Windows-first bias, with troubleshooting steps and examples often referencing Windows technologies (WinRM, WMI, PowerShell cmdlets) before or instead of Linux equivalents. Windows-specific tools and patterns (such as WinRM TrustedHosts, Get-WmiObject, and application pool configuration) are mentioned explicitly, while Linux troubleshooting is less detailed and lacks parity in example commands or tool references. Linux instructions are present but less comprehensive, and Linux-specific troubleshooting steps are sometimes generalized or omitted.
Recommendations
- Provide Linux troubleshooting steps and examples with equal detail and prominence as Windows steps, including specific commands (e.g., SSH troubleshooting, systemd/service checks, relevant log file locations).
- When mentioning Windows tools (e.g., WinRM, WMI, PowerShell cmdlets), also mention Linux equivalents (e.g., SSH, systemctl, journalctl, relevant shell commands) in the same context.
- Avoid always listing Windows steps or tools first; alternate the order or present both OSes side by side.
- For web app migration errors, include equivalent checks and recommendations for common Linux-based web servers (e.g., Apache, Nginx, Tomcat) where relevant.
- Link to Linux-specific documentation or troubleshooting guides where possible, just as is done for Windows.
- Ensure that all error codes and troubleshooting sections address both Windows and Linux scenarios explicitly, not just by implication.
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 →
Detected Bias Types
Windows Tools
Powershell Heavy
Missing Linux Example
Windows First
Summary
The documentation page demonstrates a Windows bias primarily in the management and configuration sections. It provides only Windows-specific tooling and examples (e.g., PowerShell cmdlets like New-NetQosPolicy, references to Windows services such as GatewayWindowsService.exe, and configuration file paths like C:\ProgramData\Microsoft Azure\Config). There are no equivalent Linux commands, tools, or file paths mentioned, nor is there guidance for Linux-based appliances or environments. The documentation implicitly assumes the Azure Migrate appliance is running on Windows, and all operational instructions are Windows-centric.
Recommendations
- Provide equivalent Linux-based instructions for bandwidth throttling (e.g., using tc or similar Linux network QoS tools) and reference Linux services/processes if supported.
- Include Linux file path examples (e.g., /etc/ or /var/lib/...) for configuration files like GatewayDataWorker.json if the appliance can run on Linux.
- Clarify whether the Azure Migrate appliance is Windows-only or if Linux is supported; if Linux is not supported, state this explicitly.
- If Linux-based appliances are supported, add sample commands and configuration steps for Linux environments alongside Windows examples.
- Avoid using Windows-specific terminology (e.g., C:\ProgramData) without providing cross-platform alternatives or context.
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 →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. Windows examples, tools, and configuration steps are often presented before their Linux equivalents, and in greater detail. Windows-specific tools and UI instructions (e.g., WMI Control Panel, WinRM, Start menu) are described step-by-step, while Linux instructions are more concise and sometimes lack equivalent depth or screenshots. SQL Server (a Windows-centric technology) is covered extensively, while MySQL (more common on Linux) receives minimal coverage. Some sections (e.g., Hyper-V) are inherently Windows-only, but the overall pattern is to foreground Windows workflows.
Recommendations
- Ensure Linux instructions are as detailed as Windows ones, including step-by-step guides, screenshots, and troubleshooting tips.
- Present Linux and Windows examples in parallel, or alternate which comes first, to avoid the impression of Windows being the default.
- For every Windows-specific tool or UI step (e.g., WMI Control Panel), provide the Linux equivalent (e.g., relevant commands, config files, or tools).
- Expand MySQL/Linux database discovery instructions to match the depth of SQL Server/Windows coverage.
- Where possible, use cross-platform language and avoid assuming a Windows environment (e.g., avoid 'Start menu' as the default entry point).
- Include PowerShell and Bash (or shell) script examples side-by-side for automation tasks.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/how-to-set-up-appliance-hyper-v.md
...in/articles/migrate/how-to-set-up-appliance-hyper-v.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation is heavily oriented toward Windows environments, specifically Hyper-V, and consistently provides instructions, commands, and tooling references that are exclusive to Windows. PowerShell and Windows command-line tools are used for verification and configuration steps, and there is no mention of Linux equivalents or cross-platform alternatives. Linux is only referenced as a possible credential type, with no guidance or examples for Linux-based appliance setup, verification, or troubleshooting.
Recommendations
- Wherever command-line verification or configuration is shown (e.g., file hash verification), provide equivalent Linux commands (e.g., sha256sum) alongside Windows examples.
- Clarify whether the Azure Migrate appliance can be deployed or managed from Linux hosts, and if so, provide explicit instructions and examples for Linux users.
- If PowerShell scripts are required, note whether PowerShell Core (cross-platform) is supported, and provide Bash or shell script alternatives where possible.
- For steps involving Hyper-V Manager or other Windows-only tools, mention if there are CLI or cross-platform alternatives, or explicitly state the Windows requirement.
- Include troubleshooting and configuration guidance for Linux-based environments, especially for network/proxy configuration, credential delegation, and appliance access.
- Ensure parity in screenshots and UI walkthroughs for Linux users if a Linux-based workflow is supported.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/scale-hyper-v-assessment.md
...blob/main/articles/migrate/scale-hyper-v-assessment.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation is heavily focused on Hyper-V, a Windows-based virtualization platform, and only discusses assessment and migration scenarios for Windows environments. There are no references to Linux-based hypervisors (e.g., KVM, Xen), nor are there any Linux-specific instructions, examples, or tools mentioned. The guidance assumes the user is operating in a Windows/Hyper-V context, with no parity for Linux environments.
Recommendations
- Include equivalent guidance for assessing and migrating servers from Linux-based hypervisors (such as KVM or Xen) to Azure.
- Provide Linux-specific examples and instructions, including how to deploy and configure the Azure Migrate appliance on Linux platforms if supported.
- Mention and link to documentation for Linux environments where appropriate, or clearly state if the process is not supported for non-Windows hypervisors.
- Ensure that any prerequisites, limitations, and planning considerations are addressed for both Windows and Linux environments to promote parity.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/tutorial-migrate-physical-virtual-machines.md
.../migrate/tutorial-migrate-physical-virtual-machines.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows bias in several ways: Windows Server and PowerShell are referenced as defaults or primary examples, especially for the replication appliance setup and credential policies. Windows registry and group policy checks are detailed, while equivalent Linux checks are not. The process for installing the Mobility agent on Linux is present, but less detailed compared to Windows, and Windows tools (e.g., SetupDiag, registry, group policy) are mentioned without Linux equivalents. Some steps (e.g., OVA template setup) implicitly assume a Windows environment, and Linux-specific troubleshooting or configuration is less emphasized.
Recommendations
- Provide Linux-first or Linux-parity examples alongside Windows instructions, especially for appliance setup and agent installation.
- Include Linux equivalents for registry and group policy checks (e.g., systemd, sudoers, SELinux, firewall rules).
- Document Linux troubleshooting steps, such as log file locations, common permission issues, and required packages.
- Where PowerShell is referenced, provide Bash or shell script alternatives for Linux environments.
- Clarify when steps are OS-agnostic and when they are specific to Windows or Linux.
- Ensure all screenshots and UI references are applicable to both Windows and Linux scenarios, or provide alternatives.
- Expand on Linux-specific post-migration best practices and activation/troubleshooting steps.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/quickstart-create-project.md
...lob/main/articles/migrate/quickstart-create-project.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation demonstrates a Windows bias, particularly in the section instructing users to install and use the Azure CLI. It explicitly directs users to open PowerShell as Administrator and provides command-line instructions in a PowerShell context, with no mention of Linux/macOS terminals or shell equivalents. There are no Linux-specific instructions or screenshots, and the workflow assumes a Windows environment.
Recommendations
- Provide parallel instructions for Linux and macOS users, including how to open a terminal and run Azure CLI commands.
- Avoid specifying 'PowerShell' unless the instructions are truly Windows-specific; otherwise, use neutral language like 'terminal' or 'command prompt'.
- Include example commands and outputs as they would appear in Bash or other common Linux shells.
- Add notes or callouts where behavior or prerequisites differ between Windows and Linux/macOS (e.g., installation paths, permissions).
- Ensure screenshots and step-by-step instructions are not exclusively from Windows environments.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/migrate-support-matrix-hyper-v.md
...ain/articles/migrate/migrate-support-matrix-hyper-v.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a clear Windows bias. Windows tools and patterns (such as PowerShell remoting, WMI, and WinRM) are mentioned first and in detail, while Linux equivalents are often only briefly referenced or described as secondary. Many requirements and examples are specific to Windows (e.g., detailed PowerShell and SQL Server authentication scripts for Windows, explicit mention of Windows ports and permissions), and Linux support is sometimes missing or not supported (e.g., SQL Server discovery on Linux is not supported, ASP.NET web app discovery is Windows-only). Where Linux is supported, the documentation provides less detail, fewer examples, and less guidance compared to Windows.
Recommendations
- Provide Linux-first or at least Linux-equal examples and explanations alongside Windows ones, especially for setup, permissions, and troubleshooting.
- Include detailed Linux command-line examples (e.g., for configuring SSH, required permissions, and package installation) similar to the PowerShell examples provided for Windows.
- Where features are not supported on Linux (e.g., SQL Server discovery), clearly state roadmap or alternatives, and provide links to relevant Linux migration/discovery documentation.
- Balance the order of presentation so that Linux and Windows requirements are described in parallel, not always with Windows first.
- Expand on Linux-specific troubleshooting, error messages, and best practices, matching the depth provided for Windows.
- Where possible, provide parity in supported features for Linux and document any gaps transparently.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/migrate-support-matrix-physical.md
...in/articles/migrate/migrate-support-matrix-physical.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation demonstrates a Windows bias in several ways: Windows-specific tools and patterns (such as PowerShell remoting, WMI, and WinRM) are mentioned and described in detail, often before or instead of Linux equivalents. Windows permissions and account setup are explained with more granularity, and PowerShell is referenced as the primary method for many operations. In contrast, Linux instructions are present but less detailed, and some features (such as SQL Server discovery and ASP.NET web app discovery) are not supported on Linux at all. Example scripts and troubleshooting steps are provided for Windows but are missing or less comprehensive for Linux.
Recommendations
- Provide Linux-first or parallel Linux examples and instructions wherever Windows instructions are given, especially for permissions, account setup, and troubleshooting.
- Include Linux-specific troubleshooting guidance and example scripts for common setup and permission issues, similar to the detailed steps provided for Windows.
- Where features are not supported on Linux (e.g., SQL Server discovery, ASP.NET web app discovery), clearly state the roadmap or alternatives for Linux users, and consider parity where technically feasible.
- Balance the order of presentation so that Linux and Windows instructions are given equal prominence, rather than listing Windows first by default.
- Where PowerShell scripts are provided for Windows, offer Bash or shell script equivalents for Linux setup and management tasks.
- Ensure that all tables and matrices include Linux-specific details and not just Windows-centric requirements.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/tutorial-app-containerization-java-kubernetes.md
...grate/tutorial-app-containerization-java-kubernetes.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Powershell Heavy
Windows Tools
Summary
The documentation exhibits a strong Windows bias: the Azure Migrate: App Containerization tool must be installed and run on a Windows machine, with no mention of Linux or macOS support. All installation instructions and troubleshooting paths are Windows-specific (e.g., PowerShell commands, Windows file paths). There are no examples or guidance for using the tool from a Linux environment, despite the fact that the applications being containerized are running on Linux servers. The documentation assumes the user has access to a Windows environment and is familiar with Windows tools and conventions.
Recommendations
- Provide installation and usage instructions for Linux (and optionally macOS) environments, or clearly state if the tool is Windows-only and explain why.
- Offer Linux shell (bash) equivalents for PowerShell commands, or provide a CLI/installer that works cross-platform.
- Document file paths and log locations for Linux systems if/when supported.
- If the tool is Windows-only, suggest alternative approaches for Linux users (e.g., using Docker CLI, manual containerization steps, or other Azure-supported tools).
- Clarify in the prerequisites section that a Windows machine is mandatory, and consider linking to a feature request or roadmap for Linux support if available.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/tutorial-discover-aws.md
...cs/blob/main/articles/migrate/tutorial-discover-aws.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a significant Windows bias. The Azure Migrate appliance is only described as being installed on Windows Server (2019/2022), with no mention of Linux as a supported OS for the appliance. All installation and verification steps use Windows-specific tools (PowerShell, CertUtil, Windows command prompt), and the script provided is a PowerShell script (.ps1) with no Linux equivalent. The appliance setup instructions exclusively reference Windows roles and features (IIS, PowerShell ISE, Windows Activation Service), and there are no Linux-based installation or usage examples. While Linux server discovery is supported, the documentation assumes a Windows environment for all tooling and setup, omitting Linux alternatives.
Recommendations
- Provide explicit support and instructions for deploying the Azure Migrate appliance on Linux-based EC2 instances, if supported. If not supported, clearly state this limitation.
- Include Linux shell (bash) equivalents for all command-line steps, such as file hash verification (e.g., using sha256sum), and provide Linux-based installation and troubleshooting guidance.
- If the appliance is Windows-only, add a prominent note early in the documentation to inform users that Linux is not supported as a host OS for the appliance.
- Offer parity in examples: for every Windows-specific instruction (e.g., PowerShell script execution, CertUtil usage), provide a Linux alternative or clarify the absence thereof.
- Review and update the documentation to ensure Linux administrators can follow the process without needing access to a Windows environment, or clearly state the requirement for Windows.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/tutorial-assess-sql.md
...docs/blob/main/articles/migrate/tutorial-assess-sql.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing Windows-specific tools and patterns (e.g., Cloud Witness for Windows Server Failover Clusters, links to Windows-specific best practices), mentioning Windows scenarios before Linux equivalents, and omitting Linux-specific guidance or examples for SQL Server migrations. There are no Linux or cross-platform command-line examples, and Linux licensing (RHEL/SLES) is only briefly mentioned in the context of Azure Hybrid Benefit, without further guidance.
Recommendations
- Include explicit examples and guidance for assessing SQL Server instances running on Linux, such as Ubuntu or RHEL, alongside Windows examples.
- Provide parity in high availability and disaster recovery sections by describing Linux-based clustering and witness options (e.g., using Linux Pacemaker clusters or file share witness on Linux).
- Add links to Linux-specific best practices for SQL Server on Azure VMs, similar to the Windows link provided.
- Clarify any differences in the Azure Migrate appliance setup or assessment process for Linux-based SQL Server instances.
- Where licensing or Azure Hybrid Benefit is discussed, provide concrete steps or references for Linux (RHEL/SLES) subscriptions, not just Windows.
- Ensure screenshots and UI references are not Windows-centric and, where possible, show cross-platform applicability.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/troubleshoot-network-connectivity.md
.../articles/migrate/troubleshoot-network-connectivity.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a Windows bias by providing command-line examples (such as nslookup) with Windows-style prompts (e.g., 'c:\ >nslookup'), referencing PowerShell-specific tools like Test-NetConnection, and omitting equivalent Linux/macOS commands or instructions. The guidance for editing the hosts file and DNS troubleshooting is written from a Windows perspective, with no mention of Linux file paths or tools (e.g., /etc/hosts, dig, or host commands). This may hinder users operating Azure Migrate appliances on Linux or mixed environments.
Recommendations
- Provide Linux/macOS equivalents for all command-line examples (e.g., show both 'nslookup' and 'dig' or 'host' commands, with appropriate shell prompts).
- When referencing PowerShell-specific tools like Test-NetConnection, also mention cross-platform alternatives such as 'telnet', 'nc' (netcat), or 'curl' for port connectivity tests.
- Include instructions for editing the hosts file on Linux (/etc/hosts) and macOS, not just Windows (C:\Windows\System32\drivers\etc\hosts).
- Use neutral command prompts (e.g., '$' for shell, or generic 'command line') instead of Windows-specific prompts.
- Explicitly state that the troubleshooting steps apply to both Windows and Linux appliances, and clarify any differences in procedure.
- Add screenshots or terminal output examples from Linux environments where appropriate.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/troubleshoot-changed-block-tracking-replication.md
...ate/troubleshoot-changed-block-tracking-replication.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation demonstrates a significant Windows bias. All troubleshooting steps and command-line examples are provided exclusively for Windows environments, using PowerShell, Command Prompt, and Windows-specific tools (e.g., services.msc, MMC snap-ins, Windows file paths). There are no Linux or cross-platform alternatives, and the instructions assume the Azure Migrate appliance is accessed and managed via Windows tools. Linux users are not provided with equivalent commands or guidance.
Recommendations
- Provide Linux shell (bash) equivalents for all PowerShell/Command Prompt commands (e.g., using curl, nc, dig, systemctl).
- Document how to check and manage the Azure Migrate appliance if it is deployed on Linux, or clarify if only Windows is supported.
- Offer cross-platform tools or methods for connectivity checks (e.g., using telnet/nc for port checks, dig/nslookup for DNS, azcopy for Linux).
- Mention Linux file locations and configuration steps where relevant (e.g., /etc/hosts instead of only C:\Windows\System32\drivers\etc\hosts).
- Explicitly state OS requirements and, if Windows-only, provide rationale and alternatives for Linux-based environments.
- Include screenshots or CLI output examples from Linux terminals where possible.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/tutorial-discover-hyper-v.md
...lob/main/articles/migrate/tutorial-discover-hyper-v.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation is heavily oriented toward Windows environments, with exclusive use of Windows Server, PowerShell, and Windows-specific tools and patterns. All setup, configuration, and scripting instructions are provided for Windows/PowerShell, with no equivalent Linux-based examples or guidance. Linux is only mentioned as a supported guest OS for discovery, but not as a platform for running the appliance or performing administrative tasks.
Recommendations
- Provide explicit instructions and examples for deploying and managing the Azure Migrate appliance from a Linux host, if supported.
- Include Linux shell (bash) equivalents for PowerShell commands where possible, or clarify if Linux-based management is not supported.
- Document any Linux-based tooling or automation options for preparing environments, validating prerequisites, and managing credentials.
- Clarify early in the documentation whether the appliance and management workflows are Windows-only, and if so, suggest alternative approaches for Linux-centric environments.
- Ensure parity in examples and screenshots for both Windows and Linux, especially in sections covering credential management, connectivity validation, and troubleshooting.
- If Linux is not supported for appliance hosting or management, explicitly state this limitation to set user expectations.
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 →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a strong Windows bias. It provides installation instructions and security hardening guidance exclusively for Windows Server, referencing PowerShell scripts, Windows security baselines, and Windows-specific tools (such as the Security Compliance Toolkit and DPAPI). There are no equivalent examples or recommendations for deploying or securing the appliance on Linux, nor are Linux hardening or credential management practices discussed. Windows terminology and tools are mentioned first and often exclusively.
Recommendations
- Include explicit instructions and examples for deploying and securing the Azure Migrate appliance on Linux systems, including supported distributions.
- Provide Linux-based installation methods (e.g., shell scripts, package managers) alongside PowerShell/Windows instructions.
- Reference Linux security hardening guides (such as CIS Benchmarks or OS-specific security baselines) and tools (e.g., SELinux, AppArmor) in the OS image hardening section.
- Describe Linux credential storage and encryption mechanisms (such as GnuPG, LUKS, or kernel keyrings) if supported by the appliance.
- Balance the order of presentation so that Linux and Windows approaches are given equal prominence, or clarify if the appliance is only supported on Windows.
- If Linux is not supported, explicitly state this early in the documentation to set expectations.