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 226-250 of 918 flagged pages
Migrate
Continuous Deployment for containerized applications with Azure DevOps
...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 (e.g., C:\ProgramData\...), using Windows-specific navigation instructions (File Explorer, 'Hidden items'), and focusing on ASP.NET applications (typically Windows-based) in examples. 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 described only for Windows environments, and Linux equivalents are not mentioned or provided. The page also lists ASP.NET/Windows scenarios before Linux/Java scenarios in the 'Next steps' section.
Recommendations
- Add equivalent instructions and file paths for Linux environments (e.g., /var/lib/... or /opt/...) where the Azure Migrate App Containerization tool may store artifacts.
- Include navigation steps for Linux users (e.g., using terminal commands like ls, cd, or graphical file managers).
- Provide explicit examples for containerizing and deploying Java web apps on Linux in the main tutorial, not just in the 'Next steps' section.
- Ensure that references to application types (ASP.NET/Java) and operating systems (Windows/Linux) are balanced and presented together or in parallel, rather than Windows-first.
- Mention cross-platform compatibility of the Azure Migrate App Containerization tool, if applicable, and clarify any OS-specific limitations.
Create Pull Request
Migrate
Azure App Containerization Java; Containerization and migration of Java web applications to Azure Kubernetes.
...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 steps reference Windows-specific tools, paths, and PowerShell commands. There are no Linux or cross-platform installation examples, and the use of PowerShell is required for installation. The artifact and log locations are given as Windows file paths only. The documentation does not provide parity for Linux users, despite the fact that the applications being containerized are running on Linux servers.
Recommendations
- Provide instructions and support for installing and running the Azure Migrate: App Containerization tool on Linux (and optionally macOS), including equivalent shell commands and file paths.
- Offer Linux shell (bash) installation examples alongside PowerShell, and clarify any platform limitations.
- Document artifact and log locations for Linux installations, using Linux file system conventions.
- Explicitly state platform requirements and limitations at the beginning of the documentation.
- If the tool is Windows-only, suggest alternative approaches or tools for Linux users, or provide a roadmap for cross-platform support.
Migrate
Tutorial to assess SQL instances for migration to SQL Server on Azure VM, Azure SQL Managed Instance and Azure SQL Database
...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 shows a bias toward Windows environments. It references Windows Server Failover Clusters and Cloud Witness as recommended approaches for high availability in Azure VMs, with no mention of Linux clustering solutions or equivalent Linux tooling. The linked best practices for VM sizing point to Windows-specific guidance. There are no examples or instructions for Linux-based SQL Server deployments, nor any mention of Linux failover or high availability patterns. The Azure Hybrid Benefit section mentions RHEL and SLES, but only in the context of licensing, not operational guidance.
Recommendations
- Include examples and guidance for assessing Linux-based SQL Server instances, such as those running on Ubuntu, RHEL, or SLES.
- Provide parity in high availability and disaster recovery sections by mentioning Linux clustering solutions (e.g., Pacemaker, Corosync) and their configuration in Azure.
- Add links to Linux-specific performance guidelines and best practices for running SQL Server on Azure VMs.
- Where Windows tools or patterns are referenced (e.g., Cloud Witness, Windows Server Failover Clusters), add equivalent Linux options and describe their setup.
- Ensure screenshots and walkthroughs are not exclusively Windows-centric; include Linux UI or CLI examples where relevant.
Migrate
Assess VMware servers for migration to Azure VMs in Azure Migrate
...in/articles/migrate/tutorial-assess-vmware-azure-vm.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 and its licensing (Azure Hybrid Benefit) before mentioning Linux equivalents, and by focusing on Windows-specific readiness (e.g., Windows Server version distribution in supportability). There are no explicit Linux (e.g., RHEL, SLES) assessment examples, troubleshooting steps, or screenshots. Windows terminology and tools are referenced more prominently, with Linux options mentioned only as secondary alternatives.
Recommendations
- Add explicit examples and screenshots for assessing Linux VMs (e.g., RHEL, SLES, Ubuntu), including readiness and cost estimation.
- Ensure supportability and readiness sections discuss Linux distributions and versions with equal prominence to Windows Server.
- Provide troubleshooting steps and error examples relevant to common Linux migration issues.
- Mention Linux licensing and Azure Hybrid Benefit for Linux (RHEL/SLES) before or alongside Windows Server, not as an afterthought.
- Include references to Linux-specific migration considerations, such as kernel compatibility, disk formats, and agent installation.
- Balance terminology and examples so that Linux administrators feel equally supported.
Migrate
Discover AWS instances with Azure Migrate Discovery and assessment
...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 exhibits a Windows bias in several areas: Windows Server is the only OS explicitly required for the Azure Migrate appliance, with no mention of Linux support for the appliance itself. All setup and installation instructions (including running the installer script) are provided exclusively for Windows, using PowerShell and referencing Windows-specific tools (IIS, registry keys, etc.). There are no Linux-based examples or instructions for deploying or running the appliance, and Windows tools/patterns (PowerShell, IIS, registry edits) are mentioned exclusively. Linux is only referenced as a target for discovery, not as a platform for the appliance.
Recommendations
- Provide explicit instructions and examples for deploying and running the Azure Migrate appliance on Linux-based EC2 instances, if supported.
- Include Linux shell (bash) commands for installation and configuration steps, alongside PowerShell examples.
- Clarify whether the appliance can run on Linux, and if not, explain the limitation and suggest alternatives for Linux-only environments.
- Mention Linux equivalents for Windows tools (e.g., Apache/Nginx for IIS, systemd for Windows services) where relevant.
- Ensure parity in troubleshooting and log file locations for Linux systems.
- Present Windows and Linux instructions side-by-side or in separate sections, rather than Windows-first or Windows-only.
Migrate
Migrate Hyper-V VMs to Azure with the Migration and modernization tool
...blob/main/articles/migrate/tutorial-migrate-hyper-v.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation is heavily focused on Windows environments, specifically Hyper-V hosts running Windows Server. All examples, commands, and troubleshooting steps are tailored to Windows, with exclusive use of Windows tools (e.g., .exe installers, SetupDiag, Windows activation troubleshooting). There are no Linux equivalents or examples, and Windows-specific patterns (such as registry keys, Windows file paths, and Windows-only upgrade instructions) are presented without mention of Linux scenarios. The documentation assumes the reader is operating in a Windows ecosystem and does not address Linux-based Hyper-V hosts or migration of Linux VMs in detail.
Recommendations
- Add explicit guidance for migrating Linux VMs running on Hyper-V, including any OS-specific considerations and post-migration steps.
- Include Linux command-line examples (e.g., Bash, relevant CLI tools) for any steps that can be performed on Linux, such as copying files or interacting with Azure.
- Clarify whether the migration tool supports Linux-based Hyper-V hosts, and if not, provide alternatives or workarounds.
- Present troubleshooting steps for Linux VMs post-migration (e.g., activation, networking, disk mounting).
- Balance Windows-specific instructions with Linux equivalents, or clearly state the scope is limited to Windows environments if Linux is not supported.
Migrate
Discover servers on Hyper-V with Azure Migrate Discovery and assessment
...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 is heavily oriented towards Windows environments, specifically Hyper-V on Windows Server. PowerShell commands and Windows-specific tools (Hyper-V Manager, WinRM, Group Policy Editor) are used throughout, with no Linux equivalents or examples provided. Linux is mentioned only as a supported guest OS for discovery, but not as a platform for running the appliance or managing the environment. All setup, configuration, and troubleshooting steps assume a Windows Server/Hyper-V context, and PowerShell is the only scripting language referenced.
Recommendations
- Provide equivalent instructions and examples for Linux environments where possible, such as using Linux-based Hyper-V hosts (if supported) or alternative virtualization platforms.
- Include Linux command-line examples (e.g., bash, SSH) for tasks like credential management, appliance deployment, and connectivity verification.
- Clarify whether the Azure Migrate appliance can be deployed on Linux hosts, and if not, explicitly state the limitation.
- Mention Linux tools and patterns (e.g., systemd, iptables, SSH configuration) for network and credential setup, alongside Windows tools.
- Add troubleshooting steps and prerequisites for Linux guest OS discovery, including required permissions, firewall rules, and supported authentication methods.
- Ensure parity in documentation structure and detail for both Windows and Linux environments, including screenshots and step-by-step guides.
Migrate
Discover servers on GCP instances with Azure Migrate Discovery and assessment
...cs/blob/main/articles/migrate/tutorial-discover-gcp.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation exhibits a Windows bias in several areas: Windows Server is the only supported OS for the Azure Migrate appliance, with explicit requirements for Windows Server 2019/2022. All setup and installation instructions use PowerShell and Windows-specific tools (IIS, Windows Activation Service, registry edits), with no mention of Linux equivalents or alternatives. Examples and screenshots are Windows-centric, and there is no guidance for deploying or running the appliance on Linux. Linux instructions are limited to enabling SSH and root login for discovery, but not for appliance setup or management.
Recommendations
- Provide instructions and support for deploying the Azure Migrate appliance on Linux servers, including supported distributions and prerequisites.
- Include Linux-based installation steps, such as using Bash scripts or package managers, and alternatives to PowerShell for appliance setup.
- Offer parity in examples and screenshots for Linux environments, such as configuring the appliance via Linux terminal and managing logs/configuration files in Linux file paths.
- Clarify whether the appliance can be containerized or run in a cross-platform manner, and document any limitations or future plans for Linux support.
- Ensure that Linux server administrators have clear guidance for troubleshooting, log access, and service management on Linux systems.
Migrate
Discover, assess, and migrate Amazon Web Services (AWS) EC2 VMs to Azure
...icles/migrate/tutorial-migrate-aws-virtual-machines.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation exhibits a Windows bias in several areas: Windows Server is the only supported OS for the replication appliance, Windows-specific ports and protocols (WinRM, WMI) are mentioned before Linux equivalents, and some steps (such as replication appliance setup) lack Linux alternatives. While Linux migration steps are included, parity is not maintained throughout, and some Windows tools and troubleshooting are prioritized or exclusively mentioned.
Recommendations
- Provide Linux-based options for the replication appliance, or clearly state if only Windows is supported and explain the rationale.
- When discussing prerequisites and port requirements, present Linux and Windows instructions side by side, or in parallel sections, rather than listing Windows first.
- Include Linux-specific troubleshooting steps and examples, especially for common issues (e.g., SSH, cloud-init, disk drivers).
- If certain features (like the replication appliance) are Windows-only, suggest alternative approaches for Linux-heavy environments or clarify limitations up front.
- Ensure that all command-line examples and configuration steps are given for both Windows (PowerShell/WinRM) and Linux (SSH/terminal) where applicable.
- Balance the mention of Windows and Linux tools in post-migration best practices and monitoring sections.
Migrate
Discover physical servers with Azure Migrate discovery and assessment
...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 exhibits Windows bias in several ways. Windows server preparation is described first and in greater detail, with explicit instructions for account setup, permissions, and troubleshooting. The installer script section is entirely PowerShell-based, with no mention of Linux alternatives or cross-platform installation methods. Appliance installation steps and troubleshooting paths reference Windows-specific tools, roles (IIS, PowerShell ISE), registry keys, and file paths. Linux instructions are present but less detailed, and there is no Linux installer script example or parity in setup walkthroughs.
Recommendations
- Provide Linux-first or parallel instructions for appliance setup, including explicit steps for Linux server preparation before or alongside Windows.
- Offer a Linux-compatible installer script (e.g., Bash or Python) and document its usage, including example commands and troubleshooting steps.
- Include Linux-specific troubleshooting guidance, such as log file locations, service management, and package dependencies.
- Reference Linux equivalents for Windows tools (e.g., IIS vs. Apache/Nginx, registry vs. configuration files) where applicable.
- Balance the depth of examples and permissions setup between Windows and Linux, ensuring both platforms have clear, actionable instructions.
- Clarify any limitations or differences in appliance capabilities between Windows and Linux environments.
Migrate
Discover, assess, and migrate Google Cloud Platform (GCP) VMs to Azure
...icles/migrate/tutorial-migrate-gcp-virtual-machines.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation exhibits Windows bias in several areas: Windows Server is the only supported OS for the replication appliance, with no mention of Linux alternatives; Windows configuration steps (WinRM) are listed before Linux steps; and troubleshooting and migration steps often reference Windows-specific issues and tools. Linux examples are present but less detailed, and Linux is not supported for key infrastructure roles in the migration workflow.
Recommendations
- Provide support and instructions for deploying the replication appliance on Linux-based systems, or clarify why Linux is not supported.
- Present Linux and Windows configuration steps in parallel, giving equal prominence and detail to both.
- Include troubleshooting steps and examples for common Linux migration issues, not just Windows-specific problems.
- Where Windows tools (e.g., WinRM, Windows Server) are mentioned, offer Linux equivalents (e.g., SSH, supported Linux distros) and ensure parity in guidance.
- Expand Linux Mobility agent installation instructions to match the detail given for Windows, including automation and management options.
- Review and update screenshots and UI references to ensure they are not exclusively Windows-centric.
Migrate
Migrate machines as physical servers to Azure with Azure Migrate and Modernize
.../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 exhibits a Windows bias in several ways: Windows tools and patterns (e.g., PowerShell, Windows registry keys, SetupDiag, Windows Server 2016) are mentioned first or exclusively in appliance setup and troubleshooting. PowerShell is the only CLI method described for physical server appliance setup, with no Linux shell equivalent. Registry and group policy checks are Windows-specific, and troubleshooting steps reference Windows activation and upgrade utilities. Linux is referenced only in credential requirements and in passing, with no explicit Linux-based setup or migration examples provided.
Recommendations
- Provide explicit Linux-based instructions for deploying and configuring the replication appliance, including shell script or manual steps for common Linux distributions.
- Include Linux CLI examples (e.g., Bash, shell scripts) alongside PowerShell for appliance installation and agent deployment.
- Document Linux-specific prerequisites, troubleshooting steps, and post-migration checks (e.g., SELinux, systemd, networking, activation issues).
- Balance screenshots and walkthroughs to show both Windows and Linux server scenarios.
- Reference Linux tools/utilities where appropriate (e.g., system logs, package managers, OS upgrade tools) and clarify differences in agent installation and management.
- Ensure parity in migration and upgrade guidance for Linux VMs, not just Windows Server (e.g., mention supported distributions, kernel requirements, upgrade paths).
Migrate
Migrate VMware VMs agentless the Migration and modernization tool
.../blob/main/articles/migrate/tutorial-migrate-vmware.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias through heavy use of PowerShell for migration monitoring and management, explicit references to Windows tools (e.g., SetupDiag), and frequent mention of Windows-specific options (e.g., Windows OS upgrade, Windows activation troubleshooting, Azure Hybrid Benefit for Windows Server). All command-line examples are given in PowerShell, with no Linux CLI or Bash equivalents. Windows terminology and features are often mentioned before or instead of Linux alternatives, and Linux-specific guidance is minimal or absent.
Recommendations
- Provide equivalent Bash/CLI examples for monitoring and managing migrations, especially for Linux users who may not use PowerShell.
- Clarify that Azure Cloud Shell supports Bash and provide sample Bash commands where possible.
- Include troubleshooting steps and post-migration checks for Linux VMs, similar to those provided for Windows (e.g., activation issues, OS upgrades).
- Mention Linux-specific migration considerations, such as handling of Linux bootloaders, disk partitioning, and post-migration configuration.
- Balance references to Windows tools (e.g., SetupDiag) with Linux equivalents or note when a tool is Windows-only.
- Highlight Azure Hybrid Benefit applicability for Linux (if relevant) or clarify its Windows-only scope.
- Ensure that guidance for VM agent installation, updates, and management is equally detailed for Linux as for Windows.
Migrate
Modernize ASP.NET web apps to Azure App Service code
.../migrate/tutorial-modernize-asp-net-appservice-code.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 by requiring Windows PowerShell 4.0 for migration, referencing IIS web servers (Windows-only), and omitting any mention of Linux-based hosting or migration scenarios. There are no examples or instructions for migrating from Linux-based web servers, nor are Linux tools or commands referenced. The prerequisites and migration steps assume a Windows environment, with no parity for Linux users.
Recommendations
- Provide instructions and examples for migrating ASP.NET web apps hosted on Linux servers (e.g., Apache, Nginx, Kestrel).
- Include Linux-compatible migration tools or alternatives to Windows PowerShell, such as Bash scripts or Azure CLI commands.
- Explicitly state platform requirements and offer guidance for users running ASP.NET Core apps on Linux.
- Add notes or sections addressing differences in migration steps for Linux environments, including supported scenarios and limitations.
- Ensure that examples and tool references are balanced between Windows and Linux, or clearly indicate when a step is Windows-specific.
Migrate
Migrate VMware vSphere VMs with agent-based the Migration and modernization tool
...main/articles/migrate/tutorial-migrate-vmware-agent.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 is the default OS for the replication appliance, with explicit setup steps and registry modifications for Windows VMs, while Linux instructions are minimal and lack detail. PowerShell is mentioned as the manual setup method for the appliance, with no equivalent Linux scripting guidance. Windows-specific tools and troubleshooting (e.g., registry edits, Windows activation, Azure VM agent for Windows) are described in detail, whereas Linux equivalents are referenced briefly or omitted. Examples and step-by-step instructions consistently prioritize Windows, with Linux relegated to short notes or secondary mentions.
Recommendations
- Provide detailed, step-by-step instructions for Linux VM migration, including manual installation of the Mobility service and appliance setup using Linux-native tools/scripts.
- Include Linux-specific troubleshooting guidance, such as common post-migration issues (e.g., bootloader problems, agent installation) and their resolutions.
- Offer parity in examples: where Windows registry edits or PowerShell scripts are shown, provide equivalent Linux commands (e.g., shell scripts, system configuration steps).
- Clarify requirements and best practices for Linux VMs, such as agent installation, OS compatibility, and post-migration tasks (e.g., uninstalling Linux tools, configuring the Azure VM agent).
- Ensure that references to tools (e.g., Azure VM agent, Mobility service) include both Windows and Linux installation/management instructions.
- Balance the order of presentation so that Linux instructions are not consistently secondary to Windows, and highlight cross-platform considerations throughout the guide.
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation for Azure Migrate demonstrates a moderate Windows bias. Windows-specific features (such as Windows Server redeployment, Windows OS upgrades, and extended security updates) are frequently highlighted, often before or in greater detail than Linux equivalents. PowerShell is regularly referenced as the automation tool, with little mention of Linux-native alternatives (e.g., Bash scripts). Windows tools and patterns (e.g., IIS, Operations Manager, RVTools, PowerShell utilities) are referenced more often than Linux-native tools. Linux support is present and improving (e.g., SSH authentication, Sudo support, Enterprise Linux migration), but Linux examples and tooling are less prominent and sometimes missing.
Recommendations
- Provide Linux-specific examples and workflows alongside Windows ones, especially for automation (e.g., Bash scripts, Ansible, shell commands).
- Ensure parity in documentation for Linux migration scenarios, such as redeployment using Infrastructure as Code (IaC) for Linux servers.
- Highlight Linux-native tools and patterns (e.g., systemd, Apache, Nginx, SELinux) where relevant, not just Windows-centric ones (e.g., IIS, Operations Manager).
- Include explicit Linux migration and modernization case studies, especially for popular distributions (Ubuntu, CentOS, RHEL, SUSE).
- Reference cross-platform automation options (e.g., Azure CLI, Terraform, REST API) equally with PowerShell.
- When listing features, avoid consistently mentioning Windows scenarios first; alternate or group by platform.
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 exclusively referencing Windows file paths, registry keys, and management tools (such as MMC snap-ins) when describing configuration and management tasks. There are no examples or instructions for equivalent tasks on Linux servers, even though the Mobility service supports Linux. Antivirus exclusions, bandwidth throttling, and installation instructions are all presented using Windows conventions and tools, with no mention of Linux equivalents.
Recommendations
- Provide explicit instructions and examples for Linux servers, including file paths for antivirus exclusions (e.g., /var/opt/msazure/...), and command-line installation steps for the Mobility service on Linux.
- Describe how to throttle bandwidth or manage the Mobility service on Linux, referencing relevant configuration files or commands (such as systemd, config files, or Linux-native tools).
- When listing folders or registry keys, include both Windows and Linux paths, and clarify which applies to each OS.
- If a feature is not supported on Linux, explicitly state this to avoid confusion.
- Ensure that all management and troubleshooting steps have Linux parity, or provide links to Linux-specific documentation.
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 Examples
Windows Tools
Summary
The documentation page exhibits Windows bias by referencing Windows Server as the primary example of conditional readiness, mentioning Hyper-V before VMware in the next steps, and highlighting Hyper-V-specific configuration (dynamic memory) as a requirement for performance coverage. There are no Linux-specific examples, tools, or troubleshooting guidance, and Linux workloads are not mentioned in readiness or assessment scenarios.
Recommendations
- Include Linux-specific examples in readiness categories, such as referencing unsupported Linux distributions or kernel versions.
- Add troubleshooting guidance for Linux servers (e.g., ensuring required agents are installed, network configuration for Linux).
- Mention Linux assessment scenarios and parity in performance data collection (e.g., how to collect CPU, RAM, disk, and network data from Linux servers).
- List VMware before or alongside Hyper-V when discussing supported environments, or alternate the order to avoid Windows-first bias.
- Reference Linux tools or commands where relevant (e.g., for data collection, CSV import, or agent installation).
- Explicitly state that both Windows and Linux workloads are supported and provide links to Linux-specific documentation.
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 exhibits a strong Windows bias: installation instructions and tooling (PowerShell, OVA/VHD templates) are Windows-centric, with no Linux installation or hardening examples. Security baselines and compliance toolkit recommendations reference only Windows tools and GPOs. Network port guidance mentions Linux (TCP 22) but does not provide equivalent Linux OS security or deployment guidance. The credential encryption method (DPAPI) is Windows-specific, and patching advice focuses solely on Windows Server.
Recommendations
- Provide explicit Linux deployment instructions for the Azure Migrate appliance, including supported distributions and installation steps.
- Include Linux OS hardening guidance, referencing CIS benchmarks or similar Linux security baselines.
- Mention Linux-native credential encryption and management approaches, such as using LUKS, GnuPG, or other Linux security tools.
- Offer patching and update recommendations for Linux hosts, not just Windows Server.
- Balance PowerShell examples with Bash or shell script equivalents for Linux environments.
- Reference Linux domain integration (e.g., using SSSD, LDAP, or Kerberos) where appropriate.
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-specific instructions, tools, and configuration steps (such as WMI Control, WinRM, and user group assignments) are presented in greater detail and often before Linux equivalents. Windows examples are more verbose and step-by-step, while Linux instructions are more concise and sometimes lack equivalent depth (e.g., no screenshots or GUI steps for Linux). SQL Server (Windows-centric) is covered extensively with scripts, while MySQL (Linux-friendly) coverage is brief. Hyper-V (Windows-only) is described in detail, with no mention of KVM or other Linux hypervisors.
Recommendations
- Provide equally detailed, step-by-step instructions for Linux server configuration, including screenshots or terminal outputs where appropriate.
- Include Linux-first examples where possible, or alternate the order of Windows and Linux sections to avoid Windows-first bias.
- Expand coverage of Linux database discovery (e.g., PostgreSQL) and Linux hypervisors (e.g., KVM, Xen) to match the detail given to Windows/Hyper-V.
- Offer Linux-specific troubleshooting tips and GUI/CLI navigation instructions, similar to those provided for Windows.
- Ensure parity in privilege configuration examples, such as showing how to set up least privileged accounts using Linux tools (e.g., usermod, setfacl) with full command explanations.
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 Tools
Windows First
Missing Linux Example
Summary
The documentation for Azure Migrate Appliance is heavily oriented towards Windows environments. Deployment and management instructions consistently reference PowerShell scripts and Windows tools (e.g., certificate manager, group policy editor, Windows Update). Troubleshooting and update procedures are described exclusively with Windows UI screenshots and workflows. There are no Linux-specific examples or parity for common administrative tasks, and Linux deployment/management patterns are not mentioned.
Recommendations
- Provide Linux-specific deployment instructions, including shell script alternatives to PowerShell for appliance setup and management.
- Include troubleshooting steps for certificate validation and MSI updates using Linux tools (e.g., OpenSSL, Linux certificate stores).
- Add guidance for updating the appliance OS and agents on Linux, referencing package managers and update mechanisms.
- Offer parity in screenshots and UI walkthroughs for Linux environments where applicable.
- Clarify which steps are Windows-only and provide equivalent steps for Linux users, especially for credential management, certificate installation, and agent health checks.
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 page exhibits several signs of Windows bias. Powershell and Windows-specific tools (e.g., NetQosPolicy, Windows Scheduled Tasks) are used exclusively in example scripts for bandwidth throttling, with no Linux equivalents or alternatives provided. Windows terminology and migration scenarios (e.g., Active Directory, IIS, Windows OS upgrade) are described in detail, while Linux-specific migration scenarios and tools are less emphasized or omitted. In sections listing supported operating systems, Windows versions are listed first, and Windows migration/upgrade options are described before Linux. There are no Linux shell or tool examples for common migration tasks, and Linux-specific troubleshooting or migration nuances are not addressed.
Recommendations
- Provide equivalent Linux examples for bandwidth throttling, such as using tc, wondershaper, or iptables on Linux-based appliances.
- Include Linux shell script samples for scheduling bandwidth changes (e.g., using cron jobs) alongside Windows Scheduled Tasks.
- Add troubleshooting and migration guidance for common Linux workloads and applications (e.g., Apache, NGINX, Samba, etc.), similar to the detail given for Active Directory and IIS.
- Ensure that supported operating systems tables and migration options alternate or balance Windows and Linux entries, rather than listing Windows first.
- Clarify any differences in agent installation, migration process, or rollback for Linux systems.
- Highlight Linux-specific considerations, such as SELinux/AppArmor, kernel versions, and file system compatibility, where relevant.
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
Powershell Heavy
Summary
The documentation page demonstrates a Windows bias in several ways: Windows environments (VMware, Hyper-V, IIS) are mentioned first and most frequently, with little to no mention of Linux environments or tools. References to Windows Server Failover Clusters, Cloud Witness, and links to Windows-specific best practices are prevalent, while Linux equivalents (such as Pacemaker or Linux clustering) are absent. There are no examples or guidance for assessing or migrating Linux-based SQL Server instances, nor any mention of Linux-specific migration considerations. Powershell is referenced in links and tooling, but Linux command-line or automation options are not discussed.
Recommendations
- Add explicit support and examples for assessing and migrating SQL Server instances running on Linux (including RHEL, SLES, Ubuntu, etc.)
- Include references and links to Linux best practices for SQL Server on Azure VM, such as performance guidelines and clustering with Pacemaker.
- Provide parity in migration guidance for Linux environments, including steps for deploying the Azure Migrate appliance on Linux hosts.
- Mention Linux licensing and Azure Hybrid Benefit for Enterprise Linux subscriptions more prominently, with examples.
- Include Linux command-line (bash, shell) and automation options alongside Powershell references.
- Clarify which features and recommendations apply to both Windows and Linux SQL Server deployments, and highlight any differences.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/common-questions-discovery-assessment.md
...icles/migrate/common-questions-discovery-assessment.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page for Azure Migrate assessments demonstrates a Windows bias by consistently referencing Windows-centric technologies (Hyper-V, SQL Server, IIS), omitting Linux-specific examples and tools, and prioritizing Windows environments in explanations. There is a lack of parity in mentioning Linux workloads, migration scenarios, or troubleshooting steps, and no Linux-specific migration blockers or readiness checks are discussed.
Recommendations
- Include explicit examples and guidance for assessing and migrating Linux servers (e.g., Ubuntu, CentOS, RHEL) alongside Windows/Hyper-V/VMware examples.
- Add troubleshooting steps and readiness checks for common Linux services and workloads (e.g., Apache, Nginx, MySQL, PostgreSQL).
- Mention Linux-specific migration blockers and how Azure Migrate handles Linux OS discovery, performance data collection, and compatibility checks.
- Provide parity in documentation for both Windows and Linux environments, ensuring that Linux tools, patterns, and assessment nuances are covered.
- Reference Linux migration tools (e.g., rsync, scp, Azure Linux Agent) where appropriate, and clarify differences in agent installation or data collection between Windows and Linux.
- Add links to Linux migration tutorials and best practices in the 'Next steps' section.
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 page demonstrates a Windows bias by consistently referencing Windows Server and SQL Server licensing, Extended Security Updates (ESU), and System Center management software. Cost formulas and management scenarios are detailed for Windows environments, with Linux only briefly mentioned in license amortization and support, but lacking equivalent depth or examples. Windows-specific tools and benefits (e.g., Azure Hybrid Benefit, ESU, System Center) are discussed in detail, while Linux migration, licensing, and management scenarios are not covered with the same granularity.
Recommendations
- Provide explicit examples and cost formulas for Linux workloads, including common Linux distributions and their licensing/support models.
- Include Linux management and monitoring tool equivalents (e.g., integration with Ansible, Chef, Puppet, or open-source monitoring solutions) alongside System Center.
- Discuss migration strategies and cost optimization for Linux workloads, such as lift-and-shift to Azure VMs running Linux, modernization to Azure App Service for Linux, or AKS with Linux nodes.
- Detail Azure Hybrid Benefit and ESU applicability (or lack thereof) for Linux, and clarify cost differences.
- Ensure tables and formulas include Linux-specific components, such as Linux OS licensing/support, patch management, and security solutions.
- Add Linux-focused sustainability and emissions calculations if they differ from Windows workloads.