Sad Tux - Windows bias detected
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
windows_tools
missing_linux_example
Summary
The documentation demonstrates a Windows bias by focusing exclusively on Windows Hyper-V and VMware as supported virtualization platforms, with all step-by-step instructions and screenshots provided only for Hyper-V (a Windows technology). There is no mention of Linux-based virtualization solutions (such as KVM, VirtualBox, or Linux-native Hyper-V management), nor are there any Linux command-line examples or guidance for deploying or managing the agent from a Linux environment. The documentation also references Windows Server documentation and tools before mentioning VMware, and does not provide parity for Linux users.
Recommendations
  • Explicitly state whether Linux-based virtualization platforms (e.g., KVM, VirtualBox) are supported or not, and if not, provide a roadmap or rationale.
  • If the agent image is compatible with Linux-based hypervisors, add detailed, step-by-step instructions for deploying the agent using KVM/QEMU or VirtualBox on Linux hosts, including relevant command-line examples.
  • Include Linux-specific networking guidance (e.g., how to create a bridge or virtual switch using Linux tools such as nmcli, brctl, or virsh).
  • Provide parity in decommissioning and management instructions, including examples using Azure CLI from a Linux shell.
  • If only Windows and VMware are supported, clarify this early and prominently, and consider providing alternative solutions or workarounds for Linux-only environments.
  • Balance references to Windows Server documentation with links to VMware and, if possible, Linux virtualization documentation.
GitHub Create Pull Request

Scan History

Date Scan Status Result
2026-01-14 00:00 #250 in_progress Biased Biased
2026-01-13 00:00 #246 completed Biased Biased
2026-01-11 00:00 #240 completed Biased Biased
2026-01-10 00:00 #237 completed Biased Biased
2026-01-09 00:34 #234 completed Biased Biased
2026-01-08 00:53 #231 completed Biased Biased
2026-01-06 18:15 #225 cancelled Clean Clean
2025-08-19 00:01 #85 completed Clean Clean
2025-07-13 21:37 #48 completed Clean Clean
2025-07-12 23:44 #41 cancelled Biased Biased

Flagged Code Snippets

Select the option **4) Unregister**. You're prompted for confirmation.

> [!WARNING]
> Unregistration stops any running migration job on the agent and permanently removes the agent from the pool of available migration agents. Re-registration of a previously registered agent VM isn't supported. If you need a new agent you should register a new, previously unregistered agent VM. Don't reuse a previously unregistered agent VM.

# [Azure portal](#tab/azure-portal)

You can unregister an agent in the Azure portal by navigating to your storage mover resource the agent is registered with.

- Select **Registered agents** in the main navigation menu.
- Select the agent to be decommissioned. The agent details pane opens.
- Select **Unregister agent** and wait for the operation to complete.

> [!WARNING]
> Unregistration stops any running migration job on the agent and permanently removes the agent from the pool of available migration agents. Re-registration of a previously registered agent VM isn't supported. If you need a new agent, you must use a new agent image that was never registered before and register this new agent VM. Don't reuse a previously unregistered agent VM.

# [PowerShell](#tab/powershell)

You can unregister an agent using the Az PowerShell. As a prerequisite, ensure that you have the latest version of PowerShell on your machine, and also the latest versions of the Az and Az.StorageMover PowerShell modules installed.