Document Details
Concepts Vmware Agentless Migration
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
powershell_heavy
windows_tools
windows_first
missing_linux_example
Summary
The documentation page exhibits a Windows bias in several areas. PowerShell cmdlets (e.g., New-NetQosPolicy) are used exclusively for bandwidth throttling examples, and the configuration file paths (e.g., C:\ProgramData\Microsoft Azure\Config) are Windows-specific. There are no Linux or cross-platform equivalents provided for these operations, and the documentation assumes the Azure Migrate appliance is running on Windows without mentioning Linux deployment or management options. This may hinder Linux users or those deploying the appliance on non-Windows platforms.
Recommendations
- Provide equivalent Linux-based examples for bandwidth throttling, such as using 'tc' or 'iptables' for traffic shaping.
- Document the location and format of configuration files on Linux-based appliances, if supported (e.g., /var/lib/ or /etc/ paths).
- Clarify whether the Azure Migrate appliance can be deployed on Linux, and if so, provide Linux-specific instructions for management tasks (e.g., restarting services, editing config files).
- Where PowerShell or Windows tools are mentioned, add parallel Linux shell commands or scripts.
- Adopt more neutral language that does not assume a Windows environment by default, and explicitly call out platform-specific steps.
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-09 00:00 | #106 | completed |
Clean
|
| 2025-08-09 00:00 | #75 | completed |
Clean
|
| 2025-07-13 21:37 | #48 | completed |
Biased
|
| 2025-07-12 23:44 | #41 | cancelled |
Biased
|
| 2025-07-09 13:09 | #3 | cancelled |
Clean
|
| 2025-07-08 04:23 | #2 | cancelled |
Biased
|
Flagged Code Snippets
> [!NOTE] > This is applicable to all the replicating VMs from the Azure Migrate appliance simultaneously. You can also increase and decrease replication bandwidth based on a schedule using the [sample script](common-questions-server-migration.md). ### Blackout window Azure Migrate provides a configuration-based mechanism through which customers can specify the time interval during which they don't want any replications to proceed. This time interval is called the blackout window. The need for a blackout window can arise in multiple scenarios such as when the source environment is resource constrained or when customers want replication to go through only during non-business hours, etc. > [!NOTE] > - The existing replication cycles at the start of the blackout window will complete before the replication pauses. > - For any migration initiated during the blackout window, the final replication won't run, causing the migration to fail. A blackout window can be specified for the appliance by creating/updating the file GatewayDataWorker.json in C:\ProgramData\Microsoft Azure\Config. A typical file would be of the form: