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
missing_linux_example
windows_first
Summary
The documentation demonstrates a Windows bias in its operational guidance for managing replication. All command-line examples (e.g., for throttling replication) use PowerShell cmdlets (New-NetQosPolicy), and configuration file paths are given in Windows format (C:\ProgramData\...). There is no mention of Linux equivalents or how to perform these tasks on a Linux-based Azure Migrate appliance. The documentation assumes the appliance and administrative environment are Windows-based, with no Linux parity in examples or instructions.
Recommendations
- Provide equivalent Linux command-line examples (e.g., using tc or other Linux network QoS tools for bandwidth throttling).
- Document the location and format of configuration files on Linux appliances, if supported.
- Clarify whether the Azure Migrate appliance can run on Linux, and if so, provide Linux-specific operational guidance.
- When giving file paths or service names, include both Windows and Linux variants where applicable.
- Add a section or note explicitly addressing Linux support and any differences in management or configuration.
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: