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 576-600 of 918 flagged pages
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/how-to-create-group-machine-dependencies-agentless.md
...https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/how-to-create-group-machine-dependencies-agentless.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by providing only PowerShell-based examples and instructions for managing dependency analysis (enabling/disabling, exporting data), with no equivalent CLI or scripting guidance for Linux users. Windows terminology and tools (PowerShell, Connect-AzAccount, select-azsubscription) are used exclusively, and Windows credential requirements are described before Linux. There is no mention of Bash, Azure CLI, or Linux-native automation, making it harder for Linux administrators to follow or automate these tasks.
Recommendations
- Provide equivalent instructions and examples using Azure CLI and/or Bash scripts for all PowerShell-based operations (enabling/disabling dependency analysis, exporting data, etc.).
- Explicitly mention and demonstrate how Linux users can authenticate and interact with Azure Migrate (e.g., using az login and az account set commands).
- List Linux credential requirements before or alongside Windows requirements to avoid 'windows_first' ordering.
- If PowerShell is required for some operations, clarify cross-platform support (e.g., PowerShell Core on Linux/macOS) and provide installation instructions.
- Include screenshots or terminal outputs from Linux environments where applicable.
- Reference Linux-native tools and patterns (e.g., cron jobs, shell scripting) for automation scenarios.
Create Pull Request
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/how-to-create-group-machine-dependencies.md
...es/migrate/how-to-create-group-machine-dependencies.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by consistently presenting Windows instructions, tools, and screenshots before Linux equivalents. Windows installation steps are more detailed and include multiple installation options (GUI, command line, automation tools), while Linux instructions are brief and lack comparable detail. References to Windows-specific tools (e.g., Configuration Manager, Intigua) and the absence of Linux automation or package manager examples further reinforce this bias.
Recommendations
- Present Windows and Linux instructions in parallel or in clearly separated, equally detailed sections.
- Provide Linux installation options using common package managers (e.g., apt, yum, zypper) and automation tools (e.g., Ansible, shell scripts), similar to the Windows automation examples.
- Include Linux-specific screenshots or terminal output where Windows screenshots are provided.
- Mention Linux prerequisites and supported distributions with the same level of detail as Windows OS support.
- Reference Linux equivalents for Windows tools (e.g., suggest using configuration management tools like Ansible or Puppet for Linux agent deployment).
- Avoid always listing Windows steps first; alternate or group by OS to give equal prominence.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/how-to-create-sql-assessment.md
.../main/articles/migrate/how-to-create-sql-assessment.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-specific tools and patterns (such as optimizing Windows Dockerfiles) in the 'Next steps' section, without mentioning Linux equivalents. There are no Linux or cross-platform examples, and the guidance for Dockerfile optimization and best practices is explicitly Windows-focused, despite AKS and App Service supporting Linux workloads. No Linux-specific tools, commands, or considerations are provided.
Recommendations
- Include Linux-focused examples and links, such as optimizing Linux Dockerfiles and best practices for Linux containers on AKS.
- Balance references to Windows and Linux in the 'Next steps' section, ensuring both are covered equally.
- Add notes or sections that highlight any differences or considerations for Linux-based SQL workloads and web apps.
- Wherever Windows-specific guidance is given, provide a parallel Linux example or link to Linux documentation.
- Review all referenced links to ensure Linux users are not excluded from further reading or optimization guidance.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/how-to-discover-applications.md
.../main/articles/migrate/how-to-discover-applications.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a Windows-first bias: Windows terminology and tools (such as 'File Server role', 'IIS web server', and 'local admin privileges') are mentioned explicitly and in detail, while Linux equivalents are either omitted or only briefly referenced. Several discovery features (e.g., File Server discovery) are Windows-only, and there are no concrete Linux command examples or explicit Linux tool references. Linux is mentioned in passing, often as an afterthought, and there is a lack of parity in examples and guidance for Linux environments.
Recommendations
- Provide explicit Linux examples and instructions alongside Windows ones, such as how to identify file server roles or web server roles on Linux (e.g., using Samba, NFS, Apache, or Nginx).
- When mentioning Windows-specific tools or roles (like 'File Server role' or 'IIS'), also mention and document the Linux equivalents (e.g., Samba/NFS for file servers, Apache/Nginx for web servers).
- Add Linux command-line examples (e.g., shell commands for credential setup, service discovery, or permissions) wherever Windows or PowerShell instructions are given.
- Clarify which features are supported on Linux, and if not supported, provide a roadmap or alternatives.
- Ensure that credential and permission requirements are described in detail for both Windows and Linux, not just Windows (e.g., what Linux user/group permissions are needed for discovery).
- Where features are Windows-only (such as File Server discovery), explicitly state this limitation and suggest possible workarounds or future support for Linux.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/review-web-app-assessment.md
...lob/main/articles/migrate/review-web-app-assessment.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-centric environments (VMware, Hyper-V, physical servers) in prerequisites, and by linking to Windows Dockerfile optimization and best practices in the 'Next steps' section. There are no explicit Linux or cross-platform examples, nor are Linux-specific tools, patterns, or migration considerations mentioned. The guidance and links focus on Windows workloads and tools, with no parity for Linux-based web apps or Dockerfiles.
Recommendations
- Include explicit guidance and links for Linux-based environments (e.g., Linux VMs, Linux web servers) in the prerequisites and discovery steps.
- Provide examples or references for optimizing Linux Dockerfiles and managing Linux containers, alongside the Windows Dockerfile optimization link.
- Mention Linux migration considerations and best practices for App Service and AKS targets, ensuring parity with Windows guidance.
- Balance references to Windows and Linux tools, patterns, and migration strategies throughout the documentation.
- Add sample scenarios or walkthroughs for both Windows and Linux web apps to illustrate cross-platform support.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/how-to-discover-sql-existing-project.md
...ticles/migrate/how-to-discover-sql-existing-project.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing PowerShell and Windows OS credentials exclusively, requiring PowerShell and VMware Tools for discovery, and providing no examples or instructions for Linux-based environments. The credential and discovery instructions focus on Windows authentication patterns, and there is no mention of Linux tools, authentication methods, or discovery steps for Linux servers.
Recommendations
- Include explicit instructions and examples for discovering SQL Server instances running on Linux servers, including supported authentication methods (e.g., SQL authentication, Linux user credentials).
- Mention any required tools or prerequisites for Linux-based appliances (e.g., bash, SSH, required packages) alongside PowerShell and VMware Tools.
- Provide parity in credential management instructions, such as how to add Linux credentials or handle discovery on non-Windows OS.
- Add notes or sections clarifying support (or limitations) for SQL Server on Linux and how the discovery process differs, if at all.
- Ensure screenshots and UI references are not exclusively Windows-centric, or provide Linux-specific alternatives where applicable.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/how-to-migrate-at-scale.md
.../blob/main/articles/migrate/how-to-migrate-at-scale.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation exclusively references PowerShell scripts and provides only PowerShell (.ps1) examples for automating VM migration. There is no mention of Bash, shell scripts, or cross-platform scripting alternatives, nor any guidance for Linux or macOS users. The documentation assumes a Windows-centric workflow, both in tool choice and script format.
Recommendations
- Provide equivalent Bash or shell script examples for Linux/macOS users, or clarify if the scripts are compatible with PowerShell Core on Linux.
- Explicitly mention cross-platform compatibility if the PowerShell scripts work with PowerShell Core on Linux/macOS, and provide installation/setup guidance for those platforms.
- Include references to Azure CLI or REST API alternatives for users who prefer or require non-PowerShell automation.
- Reorder or supplement examples so that Linux and cross-platform options are presented alongside or before Windows-specific instructions.
- Add a section addressing common Linux automation patterns and how they can be used in conjunction with Azure Migrate.
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
Missing Linux Example
Windows Tools
Windows First
Summary
The documentation page demonstrates a strong Windows bias by exclusively using Azure PowerShell for all command-line examples and automation steps. There are no CLI (az), Bash, or Linux-native instructions or examples provided. References to documentation for creating disk encryption sets and double encryption also point to Windows/PowerShell-specific guides. The workflow assumes a Windows environment (e.g., file paths like C:\Users\Administrator\Downloads\template.json) and does not mention or illustrate how to perform these tasks from a Linux or cross-platform perspective.
Recommendations
- Provide equivalent examples using the Azure CLI (az) in addition to PowerShell, especially for key steps like creating disk encryption sets, retrieving VM details, and deploying ARM templates.
- Include Bash shell command examples and Linux file path conventions where relevant (e.g., ~/Downloads/template.json).
- Link to both Windows/PowerShell and Linux/Azure CLI documentation for referenced tasks (such as disk encryption set creation).
- Explicitly state that the process can be performed from Linux/macOS environments and highlight any differences or prerequisites.
- Consider adding a section or callout for cross-platform users, summarizing which tools and commands are supported on which OS.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/how-to-review-discovered-inventory.md
...articles/migrate/how-to-review-discovered-inventory.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. Windows terminology, tools, and patterns are often mentioned first or exclusively (e.g., 'roles and features (Windows servers only)', SQL Server, .NET/IIS web apps). Linux is referenced, but with less detail and fewer examples. There are no Linux-specific database or web app examples, and the documentation does not provide parity in describing Linux workloads or tools. The credential and permissions section for Linux is more technical, but lacks practical examples or guidance compared to Windows.
Recommendations
- Provide Linux-specific examples for database and web application discovery and inventory (e.g., MySQL, PostgreSQL, Apache, Nginx).
- When listing workload types, alternate the order or explicitly mention both Windows and Linux equivalents (e.g., 'a server can be a Linux or Windows server').
- Expand the 'Software inventory' section to clarify what is collected on Linux servers and provide examples.
- Include more details and examples for Linux credential setup, troubleshooting, and permissions, similar to the Windows guidance.
- In tables and attribute lists, ensure Linux workloads and technologies are represented equally alongside Windows ones.
- Add screenshots or walkthroughs that show Linux server discovery and inventory views, not just Windows-centric ones.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/how-to-review-sql-assessment.md
.../main/articles/migrate/how-to-review-sql-assessment.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by consistently referencing Windows-specific SQL Server deployment patterns (such as SQL Server on Azure VM with Windows), linking exclusively to Windows-based best practices, and omitting any mention of Linux-based SQL Server deployments or examples. There are no Linux or cross-platform scenarios, tools, or migration considerations discussed, despite SQL Server's support for Linux.
Recommendations
- Include explicit references to SQL Server on Linux as a supported source and target for Azure Migrate assessments.
- Provide parallel guidance and examples for migrating SQL Server workloads running on Linux, including any differences in assessment, readiness, or sizing.
- Link to best practices and performance guidelines for SQL Server on Linux VMs in Azure, not just Windows.
- Clarify whether the assessment tool supports both Windows and Linux SQL Server sources, and highlight any platform-specific considerations.
- Add examples or notes for Linux-specific configurations (e.g., file system layouts, disk mapping, or high availability patterns like Pacemaker clusters).
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
Missing Linux Example
Powershell Heavy
Windows Tools
Summary
The documentation demonstrates a strong Windows bias. All setup instructions, installer scripts, and validation steps are exclusively for Windows Server environments. Only PowerShell scripts and Windows command-line tools (such as CertUtil) are referenced, with no mention of Linux equivalents or support. The appliance is described as being installed on Windows Server 2019/2022, and all examples and screenshots are Windows-centric. There are no instructions or even references for deploying or managing the scale-out appliance on Linux systems.
Recommendations
- Provide explicit information on whether Linux-based deployment of the Azure Migrate appliance is supported. If not, state this clearly at the beginning.
- If Linux deployment is supported, add parallel instructions for Linux environments, including shell script equivalents, Linux prerequisites, and command-line examples (e.g., using sha256sum for checksum validation).
- Include Linux-based examples for downloading, installing, and running the appliance, as well as for exporting/importing configuration files.
- Mention Linux tools and commands alongside Windows ones (e.g., bash, curl, openssl, etc.), and provide screenshots from Linux desktops where appropriate.
- If only Windows is supported, briefly explain the rationale and suggest alternatives or workarounds for Linux users.
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 Tools
Missing Linux Example
Windows First
Summary
The documentation is heavily oriented toward Windows environments, specifically Hyper-V and Windows-based tools. All command-line examples use Windows commands (CertUtil, PowerShell), and instructions reference Windows-only tools (Hyper-V Manager, Local Group Policy Editor). There are no Linux equivalents or alternative instructions for Linux hosts or appliances, and Windows terminology and patterns are used exclusively or presented first throughout.
Recommendations
- Provide equivalent Linux-based instructions or clarify if Linux is unsupported for this scenario.
- Where PowerShell or Windows commands are given (e.g., CertUtil, Get-FileHash, Enable-WSManCredSSP), offer Linux alternatives (e.g., sha256sum for hashing).
- If the appliance can be run on Linux (or if a Linux-based appliance is available), include setup instructions for Linux hosts (e.g., using KVM, QEMU, or VirtualBox).
- Clarify in the introduction that the instructions are Windows/Hyper-V specific, and link to Linux/KVM/VMware documentation if available.
- When discussing credential types, provide more detailed Linux-specific guidance and permissions, not just mention Linux in a list.
- If the appliance is Windows-only, explicitly state this limitation early in the documentation.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/how-to-set-up-appliance-physical.md
...n/articles/migrate/how-to-set-up-appliance-physical.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a strong Windows bias. All setup and deployment instructions are written for Windows environments, using PowerShell, Windows command prompt, and referencing Windows-specific tools (e.g., CertUtil, Registry Editor, IIS, Windows Activation Service). There are no Linux equivalents or alternative instructions for deploying or running the Azure Migrate appliance on Linux servers. Even when Linux servers are mentioned (for discovery), the appliance itself is assumed to be running on Windows, and no Linux-based installation or management steps are provided.
Recommendations
- Provide parallel instructions for deploying and running the Azure Migrate appliance on Linux-based hosts, including supported distributions.
- Include Linux shell (bash) equivalents for all PowerShell and Windows command prompt steps (e.g., extracting files, verifying hashes with sha256sum, running installer scripts).
- Reference Linux-native tools (e.g., systemd for services, Apache/Nginx for web apps if supported, Linux file paths) alongside Windows tools.
- Clarify OS requirements and explicitly state if the appliance can only run on Windows, or provide guidance for Linux users if a Linux appliance is not supported.
- Ensure all screenshots and code snippets have Linux alternatives where applicable.
- Mention Linux-specific troubleshooting steps and log file locations.
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 First
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows bias in several areas: it provides only Windows/PowerShell-based installer instructions as an alternative to the OVA method, uses Windows-specific tools (e.g., CertUtil in Command Prompt) for security verification, and references Windows file paths and conventions. There are no Linux equivalents or examples for these steps, and Linux tooling or commands are not mentioned. The documentation assumes the user is operating from a Windows environment when interacting with the appliance or verifying files.
Recommendations
- Provide Linux-based instructions and examples alongside Windows ones, such as using sha256sum or openssl for hash verification of the OVA file.
- Include a Linux shell script or manual steps for setting up the appliance on a Linux server, not just a PowerShell script.
- When referencing file paths or commands, offer both Windows and Linux variants.
- Explicitly mention Linux support and provide parity in troubleshooting, validation, and configuration steps.
- Clarify if the PowerShell script is cross-platform (PowerShell Core) or Windows-only, and offer a bash alternative if possible.
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
Missing Linux Example
Windows First
Summary
The documentation page demonstrates a Windows bias by repeatedly referencing Windows Server, SQL Server, and related licensing and security update scenarios, without providing equivalent details or examples for Linux-based workloads. The cost and savings calculations, as well as security and management features, are described primarily in the context of Windows technologies. There are no explicit Linux examples or mentions of Linux-specific migration considerations, tools, or licensing, and Windows-specific features (such as Extended Security Updates and Azure Hybrid Benefit) are discussed in detail before or instead of Linux equivalents.
Recommendations
- Include explicit examples and cost/savings breakdowns for Linux workloads, such as common Linux distributions (e.g., Ubuntu, Red Hat, SUSE) and open-source databases (e.g., MySQL, PostgreSQL).
- Describe how Azure Migrate handles Linux licensing, support status, and migration scenarios, including any unique benefits or challenges.
- Mention Linux security and management options (e.g., Azure Defender for Linux, Azure Monitor for Linux VMs) alongside Windows-focused features.
- Ensure that sections referencing Windows Server and SQL Server also provide parallel information for Linux servers and databases.
- Add screenshots or report samples that include Linux workloads to demonstrate parity in the assessment and reporting process.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/hydration-process.md
...e-docs/blob/main/articles/migrate/hydration-process.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 by presenting Windows-specific instructions, tools, and screenshots before Linux equivalents. Windows examples are detailed with PowerShell commands, screenshots, and explicit tool references (e.g., diskpart, Windows Azure Guest Agent), while Linux sections are less detailed, with fewer explicit command examples and no screenshots. Linux instructions often refer users to external documentation for distribution-specific steps, and some manual steps for Linux are described only in general terms or for specific distributions (e.g., RedHat), leaving out parity for other Linux distributions.
Recommendations
- Provide Linux command-line examples for all manual steps, similar to the detailed PowerShell examples given for Windows.
- Include screenshots or terminal output for key Linux steps (e.g., checking waagent status, editing network configuration files).
- Present Linux and Windows instructions in parallel or side-by-side, rather than always listing Windows first.
- Expand Linux instructions to cover a broader range of distributions, not just RedHat (e.g., include Ubuntu/Debian equivalents for network and initrd steps).
- Reference Linux tools/utilities (e.g., systemctl, nmcli, update-initramfs) explicitly where appropriate, just as Windows tools are referenced.
- Ensure that all steps described for Windows (such as agent installation verification) have clear, equivalent Linux instructions.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/hyper-v-migration-architecture.md
...ain/articles/migrate/hyper-v-migration-architecture.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation is heavily focused on Windows/Hyper-V environments, with all examples, tools, and instructions tailored exclusively to Windows systems. There are no references to Linux environments, tools, or migration scenarios, and all operational steps (e.g., registry edits, MMC snap-ins) are Windows-specific.
Recommendations
- Include equivalent guidance for migrating Linux-based VMs (e.g., KVM, Xen) to Azure using Azure Migrate.
- Provide examples and instructions for controlling upload throughput and tuning replication performance on Linux hosts, if supported.
- Mention or link to Linux migration documentation where relevant, clarifying the scope of Hyper-V (Windows) vs. Linux migrations.
- If agentless migration is not supported for Linux, explicitly state this and suggest alternative approaches for Linux workloads.
- Balance the order of presentation by including Linux scenarios or clearly stating that the page is Windows/Hyper-V specific in the introduction.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/add-server-credentials.md
...s/blob/main/articles/migrate/add-server-credentials.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a Windows-first bias by consistently listing Windows credential types and features before Linux equivalents, providing more detailed guidance for Windows scenarios, and referencing Windows-specific tools and authentication (e.g., Active Directory, DPAPI, Windows authentication for SQL Server). Linux support is often mentioned as 'not supported' or with minimal detail, and there are no Linux-specific examples or walkthroughs.
Recommendations
- Provide Linux-specific examples and walkthroughs for adding credentials, including screenshots or command-line instructions where applicable.
- List Linux and Windows credential types and required permissions in parallel, rather than always listing Windows first.
- Expand documentation on Linux support, including supported discovery features, limitations, and best practices.
- Offer guidance for common Linux authentication scenarios (e.g., SSH key-based authentication, integration with LDAP or other directory services).
- Clarify the roadmap or plans for supporting currently unsupported Linux features (e.g., SQL Server discovery, web app discovery) to set user expectations.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/least-privilege-credentials.md
...b/main/articles/migrate/least-privilege-credentials.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation is heavily oriented towards Windows environments. It references Windows-specific paths (e.g., %ProgramFiles%), tools (MinimumPrivilegedUser.exe), and patterns (command prompt navigation), with no mention of Linux equivalents or instructions for non-Windows environments. There are no examples or guidance for Linux-based SQL Server instances or how to perform these steps from a Linux system.
Recommendations
- Add explicit instructions and examples for provisioning least privileged accounts on SQL Server instances running on Linux.
- Provide cross-platform command-line examples, including bash or shell commands for Linux environments.
- Clarify whether the provisioning utility is available for Linux, and if not, suggest alternative approaches for Linux users (e.g., manual SQL scripts).
- Replace or supplement Windows-specific paths and environment variables with Linux equivalents where applicable.
- Include a section or note addressing Linux users, outlining any differences or additional steps required.
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
Powershell Heavy
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Windows file paths, registry keys, and tools (such as MMC snap-in and Windows registry), without providing equivalent instructions or examples for Linux environments. All examples and operational details (e.g., antivirus exclusions, bandwidth throttling) are Windows-centric, and there is no mention of Linux commands, tools, or file paths, despite the Mobility service supporting Linux servers as well.
Recommendations
- Provide Linux-specific instructions for installing and managing the Mobility service, including relevant file paths and commands (e.g., systemd service management, Linux package installation).
- List antivirus exclusion paths for common Linux distributions alongside Windows paths.
- Describe how to throttle upload bandwidth on Linux process servers, including configuration file locations or relevant Linux utilities.
- Mention Linux equivalents for Windows tools (e.g., instead of MMC snap-in, reference CLI or config files for Linux).
- Ensure that all operational guidance (such as port usage, scaling, and monitoring) includes Linux-specific details where applicable.
- When referencing registry keys or Windows-specific settings, clarify if and how these apply to Linux, or provide alternative Linux instructions.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/migrate-appliance.md
...e-docs/blob/main/articles/migrate/migrate-appliance.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation for the Azure Migrate appliance demonstrates a strong Windows bias. All deployment and operational instructions assume or require Windows Server (2019/2022) as the host OS for the appliance, with no mention of Linux-based deployment options. All deployment scripts and manual steps use PowerShell, and all troubleshooting and configuration references are for Windows tools (e.g., Registry Editor, Control Panel). Even in scenarios where Linux servers are discovered, the appliance itself must run on Windows. There are no Linux-based installation, management, or upgrade instructions, and Linux tooling is not addressed for any administrative tasks.
Recommendations
- Provide explicit documentation on whether the Azure Migrate appliance can be deployed on Linux hosts. If not supported, clarify this limitation early in the documentation.
- If technically feasible, develop and document a Linux-based deployment option for the appliance, including equivalent shell scripts and management instructions.
- For all deployment and management steps (installation, upgrades, service checks), provide Linux equivalents (e.g., bash scripts, systemd/service management, file hash verification with sha256sum, etc.) alongside Windows/PowerShell instructions.
- Where Windows tools (e.g., Registry Editor, Control Panel) are referenced, offer Linux alternatives (e.g., config files, systemctl, journalctl) if/when a Linux appliance is supported.
- Ensure that examples and instructions for discovering and managing Linux servers are as detailed and prominent as those for Windows servers.
- Clearly state OS requirements and limitations in the prerequisites section, and consider a comparison table for Windows vs. Linux support.
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 First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a Windows bias by focusing on Windows-centric workloads (e.g., ASP.NET on IIS), omitting explicit Linux workload examples, and referencing Windows tools and patterns (such as IIS and Hyper-V) without mentioning Linux equivalents. There is no discussion of Linux-based web apps, databases, or migration considerations, and no Linux-specific tooling or assessment scenarios are presented.
Recommendations
- Include examples and guidance for assessing and migrating Linux-based workloads, such as Apache/Nginx web servers, MySQL/PostgreSQL databases, and Linux VMs.
- Mention Linux environments (e.g., KVM, bare metal Linux servers) alongside VMware and Hyper-V in assessment scenarios.
- Provide parity in migration tool recommendations for Linux workloads, such as Azure Migrate agentless/agent-based migration for Linux, or third-party Linux migration tools.
- Add Linux-specific troubleshooting tips and common issues (e.g., SSH connectivity, Linux disk partitioning, OS detection nuances).
- Ensure that all sections referencing Windows tools or patterns also mention Linux equivalents where applicable.
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 and tools are often presented first, with more detailed step-by-step instructions and screenshots for Windows (e.g., WMI Control Panel configuration), while Linux instructions are more concise and sometimes lack equivalent detail or visual aids. Windows-specific tools and patterns (WMI, WinRM, Windows authentication, SQL Server) receive more attention, and some sections (like database discovery) focus almost exclusively on Windows technologies, with Linux or open-source alternatives only briefly mentioned or omitted.
Recommendations
- Ensure Linux instructions are as detailed as Windows ones, including step-by-step guides, command-line examples, and screenshots where appropriate.
- Present Linux and Windows examples in parallel or alternate their order to avoid always listing Windows first.
- Include Linux-native tools and authentication methods (e.g., SSH, Linux-based SQL authentication) with equal prominence.
- Expand database discovery sections to cover common Linux database scenarios (e.g., PostgreSQL, MariaDB) with least-privilege setup instructions.
- Where Windows-specific tools (like WMI or WinRM) are discussed, provide Linux equivalents (e.g., SSH, systemd, or other monitoring tools) and explain how to configure them for Azure Migrate.
- Add troubleshooting and permission validation steps for Linux environments similar to those provided for Windows.
- Review all tables and code blocks to ensure Linux and Windows examples are equally represented and easy to follow.
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 demonstrates a strong Windows bias. All deployment and hardening instructions are focused on Windows Server, with explicit references to PowerShell scripts, Windows security baselines, and Windows-specific tools (such as the Security Compliance Toolkit and DPAPI). There are no equivalent instructions, tools, or examples provided for deploying or securing the appliance on Linux systems, nor is there mention of Linux-based installation or hardening procedures. Even when Linux servers are referenced (e.g., port 22), the appliance itself is always assumed to be Windows-based.
Recommendations
- Provide explicit guidance for deploying and securing the Azure Migrate appliance on Linux-based systems, if supported.
- Include Linux command-line examples (e.g., Bash scripts) alongside PowerShell for installation and configuration.
- Reference Linux security hardening resources (e.g., CIS Benchmarks, SELinux, AppArmor) in the OS image hardening section.
- Describe how credentials are protected on Linux (e.g., using keyrings, encrypted files) if Linux appliances are supported.
- Ensure that all tooling and automation instructions are cross-platform or clearly indicate platform limitations.
- If the appliance is Windows-only, state this explicitly at the start of the documentation to set expectations.
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 almost exclusively reference PowerShell scripts and Windows tools (e.g., certificate manager, group policy editor, Windows Update). Troubleshooting and certificate management steps are described only for Windows environments, with screenshots and instructions specific to Windows UI. There are no Linux-specific deployment, management, or troubleshooting examples, and Linux tooling is not mentioned except in passing (credentials).
Recommendations
- Provide equivalent Linux-based deployment instructions, including shell script alternatives to PowerShell where possible.
- Include Linux-specific troubleshooting steps for certificate management, such as using OpenSSL or Linux certificate stores.
- Add examples and screenshots for managing the appliance on Linux-based systems (e.g., Ubuntu, CentOS).
- Clarify whether the appliance can be run on Linux hosts, and if not, explicitly state this limitation.
- When discussing credential types and agent support, include explicit instructions for Linux server discovery and management.
- Ensure that all UI and command-line instructions are provided for both Windows and Linux environments, or clearly indicate OS-specific requirements.