Resource Mover

18
Total Pages
13
Linux-Friendly Pages
5
Pages with Bias
27.8%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues (7)

https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/resource-mover/remove-move-resources.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Missing Linux Example Windows Tools Windows First
Summary:
The documentation page provides detailed instructions and examples for removing resources from a move collection in Azure Resource Mover, but all command-line examples use PowerShell cmdlets, which are primarily associated with Windows environments. There are no examples using Azure CLI, Bash, or other cross-platform tools, and no mention of Linux or macOS workflows. The exclusive use of PowerShell and lack of alternative examples creates a Windows-centric bias.
Recommendations:
  • Add equivalent Azure CLI examples for all PowerShell commands, as Azure CLI is cross-platform and widely used on Linux and macOS.
  • Explicitly mention that the operations can be performed on any OS using Azure CLI or REST API, not just via PowerShell.
  • Include Bash shell examples where relevant, especially for bulk or scripting operations.
  • Reorganize sections so that cross-platform tools (Azure CLI) are presented before or alongside PowerShell, rather than only after or not at all.
  • Add a note clarifying that PowerShell is available on Linux and macOS, but provide guidance for users who prefer native Linux tools.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/resource-mover/tutorial-move-region-virtual-machines.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Windows First
Summary:
The documentation generally maintains parity between Windows and Linux, but in the 'Prepare VMs' section, instructions for updating certificates are presented with Windows guidance first, followed by Linux. No command-line examples are given for either OS, and no PowerShell or Windows-specific tooling is used elsewhere. However, the order of presentation subtly prioritizes Windows.
Recommendations:
  • Present Windows and Linux instructions in parallel or alternate the order in which they are mentioned to avoid implicit prioritization.
  • Where possible, provide explicit, concrete examples for both Windows (e.g., using Windows Update) and Linux (e.g., using apt, yum, or update-ca-certificates) to ensure clarity and parity.
  • Review all sections to ensure that Linux is not consistently mentioned after Windows, and that both platforms receive equal prominence in prerequisites and procedural steps.
  • If screenshots or UI elements are OS-specific, include examples for both Windows and Linux VMs where relevant.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/resource-mover/modify-target-settings.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Missing Linux Example Windows Tools
Summary:
The documentation provides detailed PowerShell-based instructions for modifying destination settings when moving Azure VMs, but does not include equivalent examples for Linux users (e.g., Azure CLI, Bash scripting). The only command-line automation example is in PowerShell, which is primarily a Windows tool, and there is no mention of Linux-native tools or cross-platform alternatives.
Recommendations:
  • Add equivalent Azure CLI examples for all PowerShell-based instructions, demonstrating how to perform the same tasks using az commands.
  • Explicitly mention that both PowerShell and Azure CLI can be used for these operations, and provide guidance for users on Linux/macOS.
  • Where possible, provide Bash scripting examples or note any differences in workflow for Linux users.
  • Ensure screenshots and output examples are not PowerShell-specific, or provide parallel examples for CLI.
  • Consider restructuring the 'Modify settings in PowerShell' section to a more general 'Modify settings using command-line tools', with subsections for PowerShell and Azure CLI.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/resource-mover/common-questions.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Missing Linux Example
Summary:
The documentation references PowerShell explicitly as the only command-line interface for performing Resource Mover operations outside the portal, with no mention of Azure CLI or Linux/macOS workflows. Instructions for assigning managed identities and permissions are given only for PowerShell, and there are no Linux or cross-platform examples or guidance. This creates a Windows-centric impression and may exclude or confuse users on Linux or macOS.
Recommendations:
  • Add Azure CLI examples alongside or instead of PowerShell for all command-line operations, especially for assigning managed identities and permissions.
  • Explicitly mention that Azure CLI can be used on Linux, macOS, and Windows, and provide equivalent commands.
  • Where PowerShell is referenced, clarify that it is available cross-platform, or provide Bash/Azure CLI alternatives.
  • Review all procedural steps to ensure Linux users are not excluded, and add notes or links to relevant Linux/macOS documentation where appropriate.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/resource-mover/move-region-availability-zone.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example
Summary:
The documentation mentions both Windows and Linux VMs in the prerequisites and requirements, but when discussing updating trusted root certificates and CRLs, it provides explicit instructions for Windows ("install the latest Windows updates") while only referring Linux users to generic distributor guidance. No command-line examples (PowerShell, Bash, CLI) are present, but where OS-specific actions are mentioned, Windows is addressed first and more concretely. There are no Linux-specific examples or detailed steps, and Windows is consistently mentioned before Linux.
Recommendations:
  • Provide explicit Linux instructions or examples for updating trusted root certificates and CRLs, such as common commands for popular distributions (e.g., apt-get update/upgrade ca-certificates for Ubuntu/Debian, yum update ca-certificates for RHEL/CentOS).
  • When listing supported VM types or requirements, alternate the order or mention Linux first in some sections to avoid a consistent 'Windows first' pattern.
  • Where possible, include parity in troubleshooting or post-move steps for both Windows and Linux (e.g., how to uninstall the Mobility service on Linux).
  • If referencing OS-specific actions, provide equal detail and actionable steps for both Windows and Linux users.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/resource-mover/modify-target-settings.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Missing Linux Example Windows Tools
Summary:
The documentation provides detailed PowerShell-based instructions for modifying destination settings when moving Azure VMs, but does not include equivalent examples for Linux users (e.g., Azure CLI, Bash). The only automation example uses PowerShell cmdlets, which are most familiar and accessible to Windows users. There is no mention of cross-platform tools or Linux-first workflows.
Recommendations:
  • Add equivalent Azure CLI examples for all PowerShell commands shown, demonstrating how to perform the same actions using cross-platform tools.
  • Explicitly mention that both PowerShell and Azure CLI can be used for these operations, and provide guidance for Linux/macOS users.
  • Where possible, use neutral terminology (e.g., 'command line' instead of 'PowerShell') and link to both PowerShell and CLI documentation.
  • Consider including Bash script snippets or references for common Linux automation patterns.
  • Ensure screenshots and output examples are not specific to Windows-only environments.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/resource-mover/tutorial-move-region-virtual-machines.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Windows First
Summary:
The documentation generally maintains parity between Windows and Linux, but in the 'Prepare VMs' section, instructions for updating certificates are presented with Windows guidance first and more detail ('install the latest Windows updates'), while Linux guidance is less explicit ('follow distributor guidance'). No command-line examples are given for either OS, and no Windows-specific tools or PowerShell commands are used elsewhere. However, the ordering and specificity of the Windows instruction indicate a subtle 'windows_first' bias.
Recommendations:
  • Provide equally detailed instructions for Linux VMs as for Windows VMs, such as specifying common commands (e.g., 'sudo apt update && sudo apt upgrade' for Ubuntu) to update certificates.
  • When listing OS-specific instructions, alternate the order or present both together to avoid implying priority (e.g., 'On Windows VMs... On Linux VMs...').
  • If referencing OS-specific requirements, link to authoritative documentation for both Windows and Linux procedures.
  • Consider adding example commands or scripts for both Windows and Linux where applicable, to ensure parity and clarity.