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 326-350 of 918 flagged pages
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 →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page exclusively uses Azure PowerShell for all command-line examples and instructions, with no mention of Azure CLI, Bash, or Linux-native tooling. All example links and code blocks reference Windows-centric PowerShell usage, and there is no guidance for users working from Linux or macOS environments. The page assumes the use of Windows tools and patterns throughout, creating a Windows-first experience and omitting Linux parity.
Recommendations
- Add equivalent Azure CLI examples for all PowerShell commands, ensuring Linux and macOS users can follow along without needing PowerShell.
- Include explicit instructions or notes for running the migration steps from Linux or macOS, including any prerequisites or environment setup.
- Reference both Windows and Linux documentation for disk encryption set creation and template deployment, not just Windows-specific guides.
- Where possible, use cross-platform language in instructions (e.g., 'use your preferred shell or CLI tool') and avoid assuming a Windows environment.
- Provide sample commands for Bash or shell scripting where appropriate, especially for template editing and deployment.
Create Pull Request
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/migrate-support-matrix-vmware-migration.md
...les/migrate/migrate-support-matrix-vmware-migration.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page exhibits several signs of Windows bias. Windows operating systems and tools are frequently mentioned first or in greater detail, with explicit instructions and references to Windows-specific features (e.g., RDP, Windows Firewall, SAN policy). PowerShell is highlighted as an interface for migration configuration and appliance deployment, with no equivalent Linux CLI or automation examples. Linux requirements and post-migration steps are present but less detailed, and Linux-specific tooling (e.g., Bash scripts, Linux firewall configuration) is not covered. There are no Linux command-line examples for migration tasks, and Windows-centric terminology (such as C:\ drive, Windows Firewall) is used without Linux parity.
Recommendations
- Provide Linux CLI (e.g., Bash, shell script) examples for configuring migration and deploying appliances, alongside PowerShell examples.
- Mention Linux tools and configuration steps (e.g., iptables, firewalld, systemctl for SSH) with the same level of detail as Windows tools.
- Ensure Linux migration steps and troubleshooting guidance are as comprehensive as those for Windows, including automation options.
- List Linux operating systems and requirements before or alongside Windows, not after.
- Include parity in post-migration connection instructions, such as SSH key setup, Linux firewall configuration, and SELinux/AppArmor considerations.
- Avoid Windows-centric terminology or provide Linux equivalents in parallel (e.g., C:\ vs /, Windows Firewall vs iptables/firewalld).
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/how-to-scale-out-for-migration.md
...ain/articles/migrate/how-to-scale-out-for-migration.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a strong Windows bias. All deployment instructions and examples are exclusively for Windows Server (2019/2022), with no mention of Linux support or alternatives. The installer is a PowerShell script, and all command-line examples use PowerShell. Windows-specific tools and patterns (CertUtil, registry edits, IIS, Windows roles) are referenced throughout, with no Linux equivalents or parity. There is no guidance for deploying the appliance on Linux or using Bash/shell scripts.
Recommendations
- Provide instructions and examples for deploying the Azure Migrate appliance on Linux servers, if supported.
- Offer Bash or shell script alternatives to PowerShell installer scripts.
- Include Linux-native checksum validation commands (e.g., sha256sum) alongside CertUtil.
- Document Linux equivalents for required roles/services (e.g., Apache/Nginx instead of IIS, systemd services instead of Windows services).
- Clarify platform support in prerequisites, explicitly stating if Linux is not supported, or update the product to support Linux if feasible.
- Ensure parity in troubleshooting and log file locations for Linux systems.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/troubleshoot-webapps-migration.md
...ain/articles/migrate/troubleshoot-webapps-migration.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page is heavily focused on troubleshooting migration issues for IIS-based web apps, which are Windows-centric. All error codes and troubleshooting steps reference IIS, PowerShell, and Windows-specific concepts (e.g., IIS Management Console, PowerShell version requirements, UNC shares), with no mention of Linux web servers (such as Apache or Nginx) or Linux migration scenarios. PowerShell is referenced as the primary automation and troubleshooting tool, and all examples and error contexts are Windows-specific. There are no Linux equivalents or examples provided.
Recommendations
- Add troubleshooting sections for common Linux web server migration issues (e.g., Apache, Nginx).
- Include examples and error codes relevant to Linux-based web apps and their migration processes.
- Provide Linux command-line equivalents (e.g., Bash scripts, SSH usage) alongside PowerShell examples.
- Reference Linux tools and patterns (such as systemd, SELinux, file permissions) where appropriate.
- Clarify in the introduction or prerequisites if the documentation is intended only for Windows/IIS scenarios, or broaden its scope to include Linux web app migration.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/troubleshoot-assessment-faq.md
...b/main/articles/migrate/troubleshoot-assessment-faq.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation page exhibits several signs of Windows bias. Many troubleshooting scenarios and examples focus on Hyper-V (a Windows-centric virtualization platform) and Windows servers, with repeated references to Windows-specific features such as dynamic memory. Licensing cost calculations are only described for Windows servers, with Linux explicitly excluded. In the 'Capture network traffic' section, instructions are tailored to Microsoft browsers (Edge, Internet Explorer) and Chrome, with no mention of Linux-native tools or browsers (e.g., Firefox, curl, tcpdump, Wireshark). There are no Linux-specific troubleshooting examples, nor are Linux tools or patterns mentioned. The documentation generally assumes a Windows-first environment and omits Linux parity in examples and tool recommendations.
Recommendations
- Include troubleshooting examples and guidance for Linux environments, such as KVM, Xen, or other Linux-based hypervisors.
- Add instructions for capturing network traffic using Linux-native tools (e.g., tcpdump, Wireshark, Firefox Developer Tools) and provide export steps for these tools.
- Clarify how licensing costs are handled for Linux servers and update the documentation to reflect parity or explain the rationale for any differences.
- Balance references to Hyper-V and Windows with equivalent Linux scenarios, such as troubleshooting performance data collection on Linux VMs.
- Where browser-based instructions are given, include steps for Firefox and other browsers commonly used on Linux.
- Explicitly mention Linux support and limitations in relevant sections, and provide links to Linux-specific documentation where available.
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 Tools
Missing Linux Example
Summary
The documentation page exhibits a bias towards Windows environments by exclusively referencing Azure PowerShell for migration automation and scripting, without mentioning or providing equivalent examples for Linux users (e.g., Azure CLI or Bash). Additionally, the tools and workflows described (such as RVTools XLSX) are Windows-centric, and there are no Linux-specific instructions or parity in example commands.
Recommendations
- Include Azure CLI examples alongside Azure PowerShell for migration steps, especially for agentless migration and automation.
- Explicitly mention and provide instructions for Linux environments where applicable, such as running discovery or migration tools from Linux hosts.
- Highlight cross-platform compatibility of Azure Migration tools and clarify any OS-specific requirements or limitations.
- If RVTools is Windows-only, suggest or document alternative Linux-compatible discovery tools or methods.
- Ensure troubleshooting and preparation steps include guidance for both Windows and Linux users.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/troubleshoot-replication-vmware.md
...in/articles/migrate/troubleshoot-replication-vmware.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates Windows bias by providing appliance configuration steps that exclusively use Windows tools and patterns (Remote Desktop, PowerShell, Windows file paths, Windows service commands). There are no Linux equivalents or examples for managing the Azure Migrate appliance, and Windows instructions are presented first and exclusively. This may disadvantage users running the appliance on Linux or seeking cross-platform guidance.
Recommendations
- Provide equivalent Linux instructions for accessing and configuring the Azure Migrate appliance, such as SSH access, Linux file paths, and service management commands (e.g., systemctl).
- Include Linux-based examples for editing configuration files and restarting services.
- Clarify whether the Azure Migrate appliance can run on Linux, and if so, ensure parity in troubleshooting steps.
- When referencing tools (e.g., PowerShell, Remote Desktop), mention cross-platform alternatives (e.g., SSH, Linux text editors, Linux service management) where applicable.
- Structure troubleshooting steps so that Windows and Linux instructions are presented together or in parallel, rather than Windows-first or Windows-only.
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 Windows bias by referencing Windows-specific tools and patterns, such as Windows Server Failover Clusters and Cloud Witness, without mentioning Linux equivalents or providing Linux-specific guidance. The linked best practices and high availability sections focus on Windows, and there are no examples or instructions for Linux-based SQL Server deployments, nor mention of Linux failover clustering or witness options.
Recommendations
- Include explicit instructions and examples for assessing SQL Server instances running on Linux, such as those deployed on RHEL, SLES, or Ubuntu.
- Reference Linux clustering and high availability options (e.g., Pacemaker, Corosync) alongside Windows Server Failover Clusters.
- Provide parity in guidance for witness configuration in Linux environments (e.g., using shared disks, file-based witness, or other Linux-supported mechanisms).
- Add links to Linux-specific performance guidelines and best practices for SQL Server on Azure VMs.
- Clarify where Azure Hybrid Benefit applies to Enterprise Linux subscriptions and provide examples for both Windows and Linux licensing scenarios.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/tutorial-discover-physical.md
...ob/main/articles/migrate/tutorial-discover-physical.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in several ways. Windows server preparation instructions are presented before Linux, with more detailed steps and troubleshooting guidance. The installer script section exclusively references PowerShell and Windows tools (IIS, registry keys, Windows Activation Service), with no mention of Linux equivalents or instructions for running the appliance on Linux. The appliance setup and configuration examples, screenshots, and troubleshooting paths are all Windows-centric. Linux instructions are present but less detailed, and there are no Linux-specific installer or configuration examples.
Recommendations
- Provide parity in example order and detail: Present Linux and Windows preparation steps with equal prominence and detail.
- Add Linux installer instructions: Include clear steps and examples for installing and running the Azure Migrate appliance on Linux servers, including command-line examples (e.g., bash, systemd).
- Include Linux troubleshooting guidance: Offer troubleshooting steps and log file locations for Linux, similar to those provided for Windows.
- Clarify platform support: Explicitly state whether the appliance can be installed and run on Linux, or if it is Windows-only. If Windows-only, suggest alternatives or workarounds for Linux environments.
- Balance tool references: When mentioning Windows tools (PowerShell, IIS, registry), also reference Linux equivalents (shell scripts, Apache/Nginx, config files) where applicable.
- Add Linux screenshots: Include screenshots or terminal output examples for Linux setup and configuration steps.
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 FAQ demonstrates a strong Windows bias. Deployment and management instructions are centered around PowerShell scripts, with no mention of Bash or Linux-native tooling. Troubleshooting steps and screenshots exclusively reference Windows interfaces (e.g., certificate manager, group policy editor), and all examples for certificate management and MSI validation use Windows tools. There are no Linux-specific deployment, update, or troubleshooting examples, and Linux server scenarios are only mentioned in passing (e.g., as a credential type), not in operational guidance.
Recommendations
- Provide Linux-specific deployment instructions, including Bash scripts or CLI commands for appliance setup and management.
- Include troubleshooting steps for Linux environments, such as how to validate certificates and MSI packages using Linux tools (e.g., OpenSSL, GnuPG).
- Add screenshots and examples for Linux equivalents of certificate management and agent health checks.
- Clarify which steps are Windows-only and offer alternative guidance for Linux-based appliances.
- Ensure parity in update and maintenance instructions, such as how to keep the OS and appliance up to date on Linux.
- Explicitly mention supported Linux distributions and any prerequisites for running the appliance on Linux.
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 Windows bias in several areas: PowerShell and Windows-specific tools (NetQosPolicy, Windows Scheduled Tasks) are used exclusively for bandwidth throttling examples, with no Linux equivalents provided. Windows operating systems and migration scenarios are often listed first or receive more detailed coverage, while Linux instructions and tools are less prominent or missing. The agentless migration section focuses on Windows-centric mechanisms and examples, and there is a lack of parity for Linux-based migration appliance management and scripting.
Recommendations
- Provide equivalent Linux-based examples for bandwidth throttling (e.g., using tc, iptables, or Linux traffic control utilities) alongside PowerShell/Windows examples.
- Include instructions for managing the Azure Migrate appliance on Linux, such as using cron jobs or systemd timers for scheduled tasks.
- Ensure that Linux operating systems and migration scenarios are given equal prominence and detail in tables, lists, and explanations.
- Add Linux-specific troubleshooting steps and migration caveats where Windows-specific ones are present.
- Review the order of OS mentions in tables and lists to avoid consistently listing Windows first unless justified by usage statistics.
- Explicitly state when a feature or method is Windows-only, and offer alternative approaches for Linux users.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/common-questions-wave-planning.md
...ain/articles/migrate/common-questions-wave-planning.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a mild Windows bias by listing PowerShell as a primary example for exporting data, mentioning it before other cross-platform tools, and not providing any Linux-specific examples or command-line instructions. The focus on PowerShell and lack of explicit Linux or Bash examples may make it less approachable for Linux users.
Recommendations
- Provide explicit Linux/Bash command examples alongside PowerShell, especially for tasks like exporting data or querying Azure Resource Graph.
- List cross-platform tools (Azure CLI, REST APIs) before platform-specific ones like PowerShell to avoid the impression of Windows-first bias.
- Include screenshots or instructions that are relevant for both Windows and Linux environments.
- Clarify that Azure CLI and REST APIs are fully supported on Linux and macOS, and provide sample commands for those platforms.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/create-project.md
...zure-docs/blob/main/articles/migrate/create-project.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a bias toward Windows environments by providing command-line examples and instructions exclusively for PowerShell, with no mention of Linux shells or cross-platform usage. The installation and usage of Az CLI is described only in the context of PowerShell, and there are no Linux-specific instructions or screenshots. This may make it less accessible for users working on Linux or macOS systems.
Recommendations
- Provide equivalent command-line instructions for Linux/macOS (e.g., bash shell) alongside PowerShell examples.
- Clarify that Az CLI is cross-platform and can be used in bash, zsh, etc., not just PowerShell.
- Include screenshots or notes that demonstrate the process on Linux systems, if applicable.
- Explicitly mention OS-agnostic steps and avoid assuming the user is on Windows.
- Add a section or note for Linux users on how to install and run Az CLI commands.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/how-to-set-up-appliance-vmware.md
...ain/articles/migrate/how-to-set-up-appliance-vmware.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation demonstrates a Windows bias in several ways: the alternative to OVA deployment is exclusively a PowerShell installer script, with no mention of Linux shell or bash equivalents; installation instructions for the VMware VDDK specify a Windows path (C:\Program Files\VMware\VMware Virtual Disk Development Kit) and do not mention Linux installation; credential examples and authentication focus on Windows/domain credentials and Active Directory, with Linux credentials mentioned only as an option in a dropdown, and no Linux-specific guidance or examples. There are no Linux shell commands, nor is there parity in deployment or troubleshooting steps for Linux-based appliances.
Recommendations
- Provide a Linux shell (bash) installer script or instructions for deploying the appliance on Linux servers, alongside the PowerShell script.
- Include Linux-specific installation instructions for the VMware VDDK, with appropriate file paths and extraction commands.
- Offer examples and troubleshooting steps for Linux credentials, including guidance for non-domain Linux authentication and permissions.
- Ensure that all steps (deployment, configuration, prerequisites) have both Windows and Linux examples, and present them with equal prominence.
- Clarify OS compatibility for the appliance, and explicitly state whether Linux-based appliances are supported or not.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/migrate-support-matrix-vmware.md
...main/articles/migrate/migrate-support-matrix-vmware.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Powershell Heavy
Windows Tools
Summary
The documentation page exhibits several types of Windows bias. Windows tools and patterns (such as PowerShell, WMI, WinRM, and Windows authentication) are mentioned and required in multiple sections, often before or instead of Linux equivalents. SQL Server discovery is supported only for Windows servers, with Linux explicitly not supported. Example scripts and configuration details are provided only for Windows authentication and SQL Server authentication, with no equivalent Linux database examples. Web app discovery provides detailed requirements for Windows/IIS, but Linux/Java web app support is limited and less detailed. In several places, Windows requirements (such as PowerShell, WMI, WinRM, and specific user groups) are described in detail, while Linux requirements are summarized or omitted.
Recommendations
- Provide equivalent Linux examples and scripts for database discovery and permissions, such as for PostgreSQL or MySQL.
- Expand Linux support for SQL Server discovery, or clarify alternative approaches for Linux-based databases.
- Include Bash or shell script deployment options for the Azure Migrate appliance, not just PowerShell.
- List Linux tools and patterns (such as SSH, sudo, systemd, etc.) with the same level of detail as Windows tools.
- Ensure that Linux requirements (such as required user permissions, ports, and commands) are described as thoroughly as Windows requirements.
- Where features are Windows-only, explicitly state Linux alternatives or workarounds.
- Add more detailed examples for Linux web app discovery, including supported stacks and configuration steps.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/how-to-view-a-business-case.md
...b/main/articles/migrate/how-to-view-a-business-case.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by frequently referencing Windows-specific technologies (Windows Server, SQL Server, Extended Security Updates, Windows license costs) and Microsoft-centric management/security tools (Defender for Cloud, Azure Update Manager, Azure Backup). Cost and savings examples focus on Windows workloads, with no explicit mention of Linux equivalents, such as Linux licensing, support status, or migration strategies. There are no examples or cost breakdowns for Linux workloads, nor are Linux-specific migration or security considerations discussed.
Recommendations
- Include explicit examples and cost breakdowns for Linux workloads (e.g., Red Hat, Ubuntu, SUSE) alongside Windows examples.
- Discuss Linux license/support status, migration strategies, and cost savings, including scenarios for open-source databases and applications.
- Mention Linux-compatible security and management tools (e.g., Azure Monitor for Linux, Defender for Linux, Azure Backup for Linux) and provide parity in feature descriptions.
- Ensure that migration strategy sections reference Linux workloads and targets (e.g., Azure Linux VMs, AKS with Linux nodes, Azure Database for PostgreSQL/MySQL).
- Add screenshots and walkthroughs that include Linux server estates and mixed environments to illustrate broader applicability.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/migrate-virtual-machine-extension-reference.md
...migrate/migrate-virtual-machine-extension-reference.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation exhibits a Windows-first bias in several areas. Windows examples and tools (such as PowerShell) are presented before Linux equivalents, and some commands (e.g., extension status, update, removal) only show the Windows extension name, omitting the Linux variant. PowerShell instructions are included for both OSes, but PowerShell is a native Windows tool and less common on Linux. Troubleshooting and log paths are covered for both OSes, but overall, Windows terminology and examples are more prominent.
Recommendations
- Present Linux examples and extension names alongside Windows in all CLI and PowerShell command sections (e.g., show, update, delete).
- Where PowerShell is used, clarify its availability on Linux or provide Bash/Shell alternatives for Linux users.
- Ensure all instructions, troubleshooting steps, and log paths are equally detailed for Linux as for Windows.
- Avoid using Windows-centric terminology (e.g., 'migration.windowsazure.com') without noting Linux applicability.
- Consider alternating the order of Windows and Linux examples to avoid implicit prioritization.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/tutorial-app-containerization-azure-pipeline.md
...igrate/tutorial-app-containerization-azure-pipeline.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing Windows file paths (C:\ProgramData...), Windows-specific navigation instructions (File Explorer, Hidden items), and focusing on ASP.NET (Windows-centric) applications. There are no explicit Linux file path examples or instructions for users running the Azure Migrate App Containerization tool on Linux. The artifact location and navigation steps are exclusively described for Windows environments, and Linux alternatives are not provided. Linux containerization is only mentioned in the 'Next steps' section, not in the main workflow.
Recommendations
- Add parallel instructions for locating artifacts on Linux systems, including typical Linux file paths and navigation methods.
- Include examples for running the Azure Migrate App Containerization tool on Linux, if supported, and clarify platform support.
- Present both Windows and Linux instructions side-by-side or in separate sections to ensure parity.
- Ensure that examples for Java applications (often deployed on Linux) include Linux-specific details where relevant.
- Avoid assuming Windows as the default platform; clarify when instructions are platform-specific.
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
Summary
The documentation page demonstrates a Windows bias in several ways: command-line examples (such as nslookup) are shown exclusively with Windows-style prompts (e.g., 'c:\ >'), and PowerShell's Test-NetConnection is recommended for connectivity checks without mentioning Linux equivalents. There are no Linux shell or tool examples (e.g., dig, host, curl, netcat), nor are Linux troubleshooting patterns or file paths referenced. The guidance assumes the reader is using a Windows-based 'appliance' and does not provide parity for Linux environments.
Recommendations
- Provide Linux shell equivalents for all command-line examples, such as using 'dig', 'host', or 'nslookup' in bash, and 'nc' or 'curl' for connectivity tests.
- Mention Linux file paths and editing procedures for hosts file (e.g., '/etc/hosts') alongside Windows instructions.
- Include troubleshooting steps and screenshots for Linux-based appliances or environments.
- Reference cross-platform tools and commands where possible, and avoid assuming PowerShell or Windows CLI as the default.
- Explicitly state that the guidance applies to both Windows and Linux, and clarify any differences in procedure.
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 demonstrates 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 steps are Windows-specific (e.g., PowerShell installer, Windows file paths, Windows log locations). There are no Linux or cross-platform installation examples, and the use of PowerShell is assumed. The documentation does not provide parity for Linux users who may wish to run the tool natively.
Recommendations
- Provide instructions and support for installing and running the Azure Migrate: App Containerization tool on Linux (and possibly macOS), including shell script equivalents for installation.
- Offer Linux-specific examples for installation, troubleshooting, and artifact locations (e.g., Linux file paths, log locations).
- Clarify platform requirements early in the documentation and, if Windows-only is a technical limitation, explain the rationale and provide guidance for Linux users (e.g., using a VM or container).
- Include CLI alternatives to PowerShell commands, such as Bash or Azure CLI, for cross-platform usability.
- Consider developing and documenting a cross-platform version of the tool to improve accessibility for Linux-based development teams.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/tutorial-app-containerization-aspnet-kubernetes.md
...ate/tutorial-app-containerization-aspnet-kubernetes.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation is heavily biased toward Windows environments for ASP.NET containerization. All instructions, prerequisites, and tooling are Windows-centric, requiring Windows OS, PowerShell, and Microsoft Web Deploy. There are no Linux equivalents or cross-platform alternatives provided for ASP.NET scenarios. Linux is only mentioned in the context of Java/Tomcat apps, not for ASP.NET. Examples, scripts, and troubleshooting steps are exclusively Windows-based.
Recommendations
- Provide guidance for containerizing ASP.NET Core applications on Linux, including Dockerfile examples and deployment steps for Linux containers on AKS.
- Offer cross-platform installation instructions for the containerization tool, or clarify if/when Linux support will be available for ASP.NET workloads.
- Include Linux command-line alternatives (e.g., Bash, CLI) for steps currently shown only in PowerShell.
- Mention and document Linux-compatible tools for web app deployment and discovery, where possible.
- Add troubleshooting steps and artifact locations for Linux environments if/when supported.
- Clearly state Windows-only limitations at the start, and link to Linux-based ASP.NET containerization guides if available.
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
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page exhibits a strong Windows bias. It consistently prioritizes Windows Server and PowerShell-based workflows, especially for host preparation, appliance deployment, and credential delegation. Windows tools (Hyper-V Manager, PowerShell, CertUtil, Local Group Policy Editor) are referenced exclusively, with no Linux alternatives or parity for host management, scripting, or appliance setup. Linux is mentioned only as a supported guest OS for discovery, with minimal guidance for Linux-specific scenarios and no Linux host or management examples.
Recommendations
- Add explicit guidance and examples for environments where Hyper-V hosts run on Windows Server Core or are managed remotely from Linux/macOS clients.
- Provide Linux-based alternatives for script execution, credential validation, and appliance deployment (e.g., Bash scripts, OpenSSH, Linux management tools).
- Include parity for credential delegation and appliance setup using Linux tools (such as SSH, Ansible, or other cross-platform automation frameworks).
- Reference cross-platform management options (e.g., Azure CLI, REST API) where possible, and clarify which steps are Windows-only.
- Add troubleshooting and validation steps for Linux-based guest discovery, including common issues and log locations.
- Clearly indicate Windows-only requirements and suggest workarounds or alternatives for users in mixed-OS environments.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/agent-based-migration-architecture.md
...articles/migrate/agent-based-migration-architecture.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page demonstrates a Windows bias by referencing Windows-specific tools (such as the Windows registry and MMC snap-in), providing only Windows file paths and configuration instructions, and omitting Linux equivalents or examples. There are no instructions or examples for Linux-based process servers or Mobility service installation on Linux, and all operational details (such as antivirus exclusions and bandwidth throttling) are described exclusively for Windows environments.
Recommendations
- Include Linux-specific instructions and examples for installing and managing the Mobility service, including command-line installation and service management.
- Provide Linux file paths for antivirus exclusions and clarify which folders need to be excluded on Linux servers.
- Describe how to throttle bandwidth on Linux-based process servers, including relevant configuration files or commands.
- If registry keys or MMC snap-ins are not available on Linux, document alternative methods for Linux environments.
- Ensure all operational guidance (such as port usage, scaling, and monitoring) includes Linux-specific details where applicable.
- Present examples for both Windows and Linux environments side by side, or clearly indicate when a feature is Windows-only.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/assessment-report.md
...e-docs/blob/main/articles/migrate/assessment-report.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing Windows Server as the primary example of conditional readiness, mentioning Hyper-V (a Windows-centric virtualization platform) before VMware and physical servers, and omitting any explicit mention or examples of Linux servers, Linux-specific readiness issues, or Linux tooling. There are no Linux or cross-platform command-line examples, nor are Linux-specific migration considerations discussed.
Recommendations
- Include examples of readiness issues for Linux servers (e.g., unsupported kernel versions, disk formats, etc.) alongside Windows examples.
- Mention Linux environments explicitly when discussing assessment types, performance data collection, and migration guidance.
- Provide parity in tooling references, such as mentioning Linux-based virtualization platforms (e.g., KVM) and how Azure Migrate assesses them.
- Add Linux-specific remediation guidance and migration best practices.
- Ensure that examples and notes alternate or balance Windows and Linux scenarios to avoid implicit prioritization.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/best-practices-assessment.md
...lob/main/articles/migrate/best-practices-assessment.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by focusing primarily on Windows-centric workloads (such as ASP.NET on IIS), referencing Windows tools and patterns (e.g., IIS, Hyper-V), and omitting explicit Linux or open-source workload examples. There are no Linux-specific migration scenarios, tools, or assessment types mentioned, and the only application migration example is for ASP.NET on IIS, a Windows technology. Additionally, the order of presentation and examples consistently prioritize Windows environments and tools.
Recommendations
- Include explicit examples and guidance for assessing and migrating Linux workloads (e.g., Apache, NGINX, Tomcat, MySQL/PostgreSQL servers).
- Add Linux-specific assessment types or clarify how the tool supports Linux servers and workloads.
- Provide parity in application migration scenarios by including open-source and Linux-native applications alongside Windows/IIS/ASP.NET.
- Mention Linux-based migration tools or patterns where relevant, and ensure that Linux environments (e.g., KVM, bare metal Linux servers) are referenced alongside VMware and Hyper-V.
- Reorder sections or examples to alternate or balance between Windows and Linux scenarios, rather than always listing Windows first.