Document Details
Migrate Appliance
This page contains Windows bias
About This Page
This page is part of the Azure documentation. It contains code examples and configuration instructions for working with Azure services.
Bias Analysis
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation for the Azure Migrate appliance is heavily biased toward Windows environments. All deployment and management instructions assume or require Windows Server (2019/2022/2025) as the host OS, with no mention of Linux as a supported platform for the appliance itself. All examples for verification, upgrades, and manual operations use Windows-specific tools (PowerShell, Command Prompt, Registry Editor, Control Panel). Even when Linux servers are mentioned as discovery targets, there are no examples or instructions using Linux-native tools for appliance deployment, management, or verification. The documentation does not provide parity for Linux administrators who may wish to host or interact with the appliance outside of a Windows context.
Recommendations
- Clearly state OS requirements and limitations at the top of the documentation, including whether Linux hosting is supported or not.
- If Linux hosting is possible, provide equivalent instructions for deploying, verifying, and managing the appliance on Linux (e.g., using Bash, Linux hash utilities, Linux package managers).
- For verification steps (e.g., file hashes), include Linux command examples (e.g., sha256sum, md5sum) alongside Windows CertUtil.
- For upgrade and management tasks, offer Linux alternatives where possible (e.g., using systemd, cron, or Linux configuration files instead of Registry Editor and Control Panel).
- If the appliance is Windows-only, explicitly call out this limitation and provide guidance for Linux-centric environments (e.g., recommend running the appliance in a Windows VM if needed).
- Ensure that examples for interacting with discovered Linux servers (e.g., SSH, agent installation, troubleshooting) are included and given equal prominence.
Create Pull Request
Scan History
| Date | Scan | Status | Result |
|---|---|---|---|
| 2026-01-14 00:00 | #250 | in_progress |
Biased
|
| 2026-01-13 00:00 | #246 | completed |
Biased
|
| 2026-01-11 00:00 | #240 | completed |
Biased
|
| 2026-01-10 00:00 | #237 | completed |
Biased
|
| 2026-01-09 00:34 | #234 | completed |
Biased
|
| 2026-01-08 00:53 | #231 | completed |
Biased
|
| 2026-01-06 18:15 | #225 | cancelled |
 Clean
|
| 2025-09-16 00:00 | #113 | completed |
Clean
|
| 2025-09-15 00:00 | #112 | completed |
Clean
|
| 2025-09-14 00:00 | #111 | completed |
Clean
|
| 2025-09-13 00:00 | #110 | completed |
Clean
|
| 2025-09-12 00:00 | #109 | completed |
Clean
|
| 2025-09-11 00:00 | #108 | completed |
Clean
|
| 2025-09-10 00:00 | #107 | completed |
Clean
|
| 2025-09-09 00:00 | #106 | completed |
Clean
|
| 2025-09-08 00:00 | #105 | completed |
Clean
|
| 2025-09-07 00:00 | #104 | completed |
Clean
|
| 2025-09-06 00:00 | #103 | completed |
Clean
|
| 2025-09-05 00:00 | #102 | completed |
Clean
|
| 2025-09-04 00:00 | #101 | completed |
Clean
|
| 2025-09-03 00:00 | #100 | completed |
Clean
|
| 2025-08-17 00:01 | #83 | cancelled |
Clean
|
| 2025-07-17 00:00 | #53 | completed |
Clean
|
| 2025-07-13 21:37 | #48 | completed |
Clean
|
| 2025-07-12 23:44 | #41 | cancelled |
Biased
|
| 2025-07-09 13:09 | #3 | cancelled |
Clean
|
| 2025-07-08 04:23 | #2 | cancelled |
Biased
|