Resource Mover

19
Total Pages
9
Linux-Friendly Pages
10
Pages with Bias
52.6%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

57 issues found
Showing 1-25 of 57 flagged pages
Resource Mover Modify destination settings when moving Azure VMs between regions with Azure Resource Mover ...main/articles/resource-mover/modify-target-settings.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides detailed PowerShell-based instructions and examples 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/tooling example is for PowerShell, which is primarily a Windows tool, and there is no mention of Linux-native or cross-platform alternatives.
Recommendations
  • Add equivalent Azure CLI examples for all PowerShell commands shown, with Bash syntax where appropriate.
  • Explicitly mention that both PowerShell and Azure CLI can be used for these operations, and provide links to relevant CLI documentation.
  • Where possible, provide cross-platform instructions or note any differences in experience between Windows and Linux users.
  • Ensure screenshots and output examples are not specific to Windows environments (e.g., avoid PowerShell-only output).
GitHub Create Pull Request
Resource Mover Common questions about Azure Resource Mover .../blob/main/articles/resource-mover/common-questions.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation references PowerShell explicitly for command-line operations (e.g., assigning managed identities and permissions), without mentioning or providing examples for Linux-friendly alternatives such as Azure CLI, Bash, or cross-platform scripting. The only command-line example is PowerShell, which is primarily associated with Windows, and there is no mention of Linux or macOS workflows. This creates a bias toward Windows users and may hinder Linux users from easily following the documentation.
Recommendations
  • Provide equivalent Azure CLI examples alongside PowerShell instructions, as Azure CLI is cross-platform and widely used on Linux and macOS.
  • Explicitly mention that operations can be performed on Linux/macOS and provide guidance or links for those environments.
  • When referring to command-line operations, avoid assuming PowerShell as the default and present both PowerShell and Azure CLI options in parallel.
  • Add a section or note clarifying cross-platform support and listing tools available for Linux users.
GitHub Create Pull Request
Resource Mover Move encrypted Azure VMs across regions by using Azure Resource Mover ...ver/tutorial-move-region-encrypted-virtual-machines.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation exhibits Windows bias primarily in the key vault copy step, where only a PowerShell script is provided for copying encryption keys and secrets. There is no mention of a Linux/bash alternative or cross-platform script, and the instructions explicitly recommend PowerShell. Additionally, references to disk encryption link first to Windows VM guides, and the overall pattern is to present Windows-centric tooling and examples before Linux equivalents.
Recommendations
  • Provide a bash or Azure CLI script for copying keys and secrets between key vaults, or clarify if the PowerShell script can be run on Linux/macOS via PowerShell Core.
  • Explicitly mention cross-platform compatibility for scripts and modules, including installation instructions for Linux/macOS environments.
  • Add Linux-specific examples and references alongside Windows ones, especially in sections discussing disk encryption and prerequisites.
  • Ensure that documentation links and examples are balanced between Windows and Linux, or presented in parallel where possible.
GitHub Create Pull Request
Resource Mover Remove resources from a move collection in Azure Resource Mover .../main/articles/resource-mover/remove-move-resources.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides detailed instructions and examples for removing resources from a move collection in Azure Resource Mover using the Azure Portal and PowerShell. All command-line examples use PowerShell cmdlets, with no mention of Azure CLI, Bash, or Linux-native tooling. The PowerShell sections are extensive and presented as the sole automation option, which may disadvantage users on Linux or macOS platforms who typically use Azure CLI or Bash scripts. There are no Linux-specific instructions or parity examples.
Recommendations
  • Add equivalent Azure CLI examples for all resource removal operations, including single and bulk removals, and collection deletion.
  • Explicitly mention that PowerShell cmdlets can be run on Linux and macOS, but also provide Bash/Azure CLI syntax for cross-platform parity.
  • Include a section comparing PowerShell and Azure CLI usage for these tasks, helping users choose the best tool for their environment.
  • Ensure screenshots and walkthroughs are not Windows-centric (e.g., avoid showing only Windows PowerShell terminals).
  • Add notes or links to documentation for Linux/macOS users on installing and using Azure CLI.
GitHub Create Pull Request
Resource Mover Support matrix for moving Azure VMs to another region with Azure Resource Mover .../resource-mover/support-matrix-move-region-azure-vm.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates Windows bias by listing Windows VM support before Linux, providing detailed instructions and links for Windows-specific updates (servicing stack, SHA-2), and omitting equivalent troubleshooting or update guidance for Linux distributions. There are no Linux-specific examples or instructions for preparing older Linux VMs, and the troubleshooting section for password-based sign-in on Ubuntu refers only to Azure portal actions, not Linux-native methods. The page also references Windows tools and update patterns without Linux parity.
Recommendations
  • Present Windows and Linux VM support in parallel or alternate the order to avoid implicit prioritization.
  • Provide equivalent troubleshooting and update instructions for Linux distributions, such as kernel or package update steps for older supported releases.
  • Include Linux-native methods for common tasks (e.g., resetting passwords, preparing VMs for migration) alongside Azure portal instructions.
  • Add links to official Linux vendor documentation for supported distributions, similar to the Windows SSU/SHA-2 update links.
  • Explicitly mention any required Linux agent or extension updates and provide guidance for their installation.
  • Ensure examples and notes are balanced between Windows and Linux, especially in sections discussing prerequisites and migration steps.
GitHub Create Pull Request
Resource Mover Common questions about Azure Resource Mover .../blob/main/articles/resource-mover/common-questions.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page for Azure Resource Mover demonstrates a Windows bias by exclusively referencing PowerShell for command-line operations and role assignment tasks, without mentioning or providing examples for Linux-friendly alternatives such as Azure CLI or Bash. The instructions for manual operations and automation are centered around PowerShell, which is traditionally associated with Windows environments. No Linux-specific tools, commands, or examples are provided, and PowerShell is mentioned before any cross-platform alternatives.
Recommendations
  • Add Azure CLI examples alongside PowerShell for all command-line operations, especially for assigning managed identities and roles.
  • Explicitly mention that Azure CLI and Bash can be used from Linux, macOS, and Windows, and provide parity in instructions.
  • Where PowerShell is referenced, clarify its cross-platform availability, but also ensure CLI/Bash examples are present.
  • Include links to Azure CLI documentation and usage patterns for common Resource Mover tasks.
  • Review all procedural steps to ensure Linux users are not excluded and can follow along without needing PowerShell.
GitHub Create Pull Request
Resource Mover Move resources to another region with Azure Resource Mover ...es/resource-mover/move-region-within-resource-group.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates mild Windows bias. In the 'Check VM requirements' section, Windows VM support is listed before Linux VM support, and instructions for updating certificates explicitly mention installing Windows updates, while Linux guidance is generic and refers users to distributor documentation. No Linux-specific commands, tools, or examples are provided throughout the page, and there is an absence of parity in troubleshooting or operational steps for Linux VMs compared to the explicit mention of Windows update procedures.
Recommendations
  • Present Windows and Linux VM support information in parallel or alternate the order to avoid Windows-first bias.
  • Provide concrete Linux examples for updating certificates and CRLs, such as commands for common distributions (e.g., Ubuntu: 'sudo apt-get update && sudo apt-get upgrade ca-certificates').
  • Include troubleshooting steps or operational guidance specific to Linux VMs, similar to the explicit Windows update instructions.
  • Where Windows tools or patterns are mentioned, offer equivalent Linux commands or references (e.g., for certificate management, reference 'update-ca-certificates' or 'yum update ca-certificates').
  • Ensure that any screenshots or UI references do not implicitly favor Windows environments unless the process is identical for Linux.
GitHub Create Pull Request
Resource Mover Modify destination settings when moving Azure VMs between regions with Azure Resource Mover ...main/articles/resource-mover/modify-target-settings.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools Windows First
Summary
The documentation provides detailed PowerShell examples for modifying destination settings during Azure VM migration, but does not include equivalent examples for Linux users (e.g., Bash, Azure CLI). The only automation example uses PowerShell cmdlets, which are primarily Windows-centric, and there is no mention of Linux tools or cross-platform alternatives. This creates a bias towards Windows users and may hinder Linux administrators from following the guide effectively.
Recommendations
  • Add equivalent Azure CLI (az) examples for all PowerShell commands shown, ensuring Linux and macOS users can follow along.
  • Explicitly mention that both PowerShell and Azure CLI can be used for these operations, and provide links to both sets of documentation.
  • Include a section or note on how to perform these tasks using Bash scripts or in a Linux environment.
  • Ensure screenshots and output examples are not Windows-specific (e.g., avoid showing only PowerShell terminal output).
  • Review and update future documentation to provide parity between Windows and Linux tooling and workflows.
GitHub Create Pull Request
Resource Mover Move Azure VMs to availability zones in another region with Azure Resource Mover ...ticles/resource-mover/move-region-availability-zone.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a mild Windows bias. Windows VMs are mentioned before Linux VMs in the support verification step, and Windows update instructions are more explicit than those for Linux (which simply refer to distributor guidance). There are no concrete Linux-specific examples or commands, and no mention of Linux tools or troubleshooting steps. The documentation references Windows updates and certificates directly, but does not provide equivalent detail for Linux systems.
Recommendations
  • Present Windows and Linux VM support verification in parallel, or mention Linux first in some sections.
  • Provide explicit instructions or links for updating certificates and CRLs on popular Linux distributions (e.g., Ubuntu, CentOS).
  • Include Linux-specific troubleshooting steps or considerations, such as common issues with kernel versions or agent installation.
  • Add example commands for both Windows (PowerShell) and Linux (bash/CLI) where applicable, especially for post-move cleanup or agent uninstallation.
  • Ensure parity in detail and clarity for both Windows and Linux throughout the documentation.
GitHub Create Pull Request
Resource Mover Remove resources from a move collection in Azure Resource Mover .../main/articles/resource-mover/remove-move-resources.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides detailed instructions and examples for removing resources from a move collection using the Azure portal and PowerShell. All command-line examples use PowerShell cmdlets, with no mention of Azure CLI or Bash equivalents. This approach prioritizes Windows tooling and patterns, potentially excluding Linux and macOS users who commonly use Azure CLI or Bash. The documentation does not offer Linux-specific guidance or parity in command-line examples.
Recommendations
  • Add equivalent Azure CLI examples for all PowerShell commands, demonstrating how to perform the same actions on Linux/macOS.
  • Explicitly mention that both PowerShell and Azure CLI can be used, and link to relevant Azure CLI documentation.
  • Include notes or sections for Linux/macOS users, clarifying any differences in workflow or tool availability.
  • Ensure screenshots and instructions are not Windows-centric, and consider including cross-platform visuals where appropriate.
GitHub Create Pull Request
Resource Mover Move encrypted Azure VMs across regions by using Azure Resource Mover ...ver/tutorial-move-region-encrypted-virtual-machines.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation demonstrates a bias towards Windows by providing only PowerShell scripts for key operations (such as copying keys between key vaults), referencing Windows-specific encryption documentation first, and omitting equivalent Linux command-line examples for critical steps. While Linux VM support is mentioned, actionable steps and tooling are exclusively Windows/PowerShell-focused, leaving Linux users without clear guidance for performing required operations.
Recommendations
  • Provide equivalent Linux command-line instructions (e.g., Bash/CLI/az commands) for copying keys between key vaults, or reference cross-platform scripts.
  • Include links to Linux disk encryption documentation alongside Windows references, and ensure both are equally visible.
  • Explicitly state whether the provided PowerShell script can be run on Linux (e.g., via PowerShell Core), or offer an alternative method for Linux users.
  • Add Linux-specific troubleshooting and preparation steps where Windows-specific instructions are given (e.g., updating certificates, running scripts).
  • Where modules or tooling are required, clarify installation and usage for both Windows and Linux environments.
GitHub Create Pull Request
Resource Mover https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/resource-mover/common-questions.md .../blob/main/articles/resource-mover/common-questions.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page for Azure Resource Mover demonstrates a Windows bias by providing explicit instructions and examples for using PowerShell to manage Resource Mover operations, such as assigning managed identities and permissions. There are no equivalent examples or guidance for Linux users, such as using Azure CLI or Bash. Windows tools and patterns (PowerShell cmdlets) are mentioned exclusively and before any cross-platform alternatives.
Recommendations
  • Add Azure CLI examples alongside PowerShell instructions for all resource management tasks.
  • Explicitly mention that Azure CLI and Bash can be used on Linux and macOS for Resource Mover operations.
  • Ensure that all manual steps (e.g., assigning managed identities, permissions) have cross-platform guidance.
  • Where PowerShell is referenced, provide a parallel Azure CLI command or script.
  • Review and update documentation to avoid assuming users are on Windows or using PowerShell by default.
GitHub Create Pull Request
Resource Mover https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/resource-mover/modify-target-settings.md ...main/articles/resource-mover/modify-target-settings.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides detailed instructions and examples exclusively using PowerShell, which is primarily a Windows-centric tool, for modifying destination settings when moving Azure VMs. There are no equivalent examples or guidance for Linux users, such as using Azure CLI, Bash, or other cross-platform tools. This creates a bias towards Windows users and may hinder Linux administrators from following the documentation effectively.
Recommendations
  • Add equivalent examples using Azure CLI commands for all PowerShell instructions, ensuring Linux and macOS users can follow along.
  • Explicitly mention that both PowerShell and Azure CLI can be used, and provide links to relevant CLI documentation.
  • Where possible, provide Bash script examples for common operations.
  • Clarify any platform-specific requirements or limitations for each method.
  • Ensure screenshots and output examples are not exclusively from Windows environments.
GitHub Create Pull Request
Resource Mover https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/resource-mover/remove-move-resources.md .../main/articles/resource-mover/remove-move-resources.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools Windows First
Summary
The documentation provides detailed instructions and examples for removing resources from an Azure Resource Mover move collection using the Azure Portal and PowerShell. All command-line examples use PowerShell cmdlets, which are primarily Windows-centric. There are no examples or mentions of Azure CLI, Bash, or Linux-native tools. The PowerShell section is extensive and appears before any mention of alternative command-line interfaces, and there is no guidance for Linux or macOS users.
Recommendations
  • Add equivalent Azure CLI examples for all PowerShell commands, with syntax and output screenshots.
  • Explicitly mention that PowerShell is available cross-platform, but provide Bash/Azure CLI alternatives for Linux/macOS users.
  • Reorganize sections so that command-line examples are presented in parallel: PowerShell and Azure CLI side-by-side.
  • Include notes or links for Linux/macOS users on how to perform these tasks without PowerShell.
  • Ensure tool-agnostic language in introductory sections, clarifying that multiple command-line options exist.
GitHub Create Pull Request
Resource Mover https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/resource-mover/tutorial-move-region-encrypted-virtual-machines.md ...ver/tutorial-move-region-encrypted-virtual-machines.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation demonstrates a Windows bias in several ways: the only provided script for copying keys between key vaults is a PowerShell script, with no mention of a Linux-friendly alternative (such as Bash or Azure CLI); references to VM encryption point first to Windows documentation; and instructions for preparing VMs provide detailed steps for Windows but only generic guidance for Linux. There are no concrete Linux command examples or parity in tooling recommendations.
Recommendations
  • Provide equivalent Bash or Azure CLI scripts for key vault operations, or explicitly document how Linux users can perform these steps.
  • Reference both Windows and Linux VM encryption documentation equally and in parallel, rather than listing Windows first.
  • Include Linux-specific examples and commands (e.g., using Azure CLI in Bash) for all steps where PowerShell is recommended.
  • Clarify any platform-specific requirements or limitations, and ensure Linux users are not required to use Windows tools.
  • Add screenshots or walkthroughs from Linux environments where relevant.
GitHub Create Pull Request
Resource Mover https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/resource-mover/common-questions.md .../blob/main/articles/resource-mover/common-questions.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page for Azure Resource Mover demonstrates a Windows bias by exclusively mentioning PowerShell for command-line operations, with no references to Linux-native tools (such as Azure CLI or Bash). Instructions for manual operations (e.g., assigning managed identities and permissions) are given only for PowerShell, and there are no Linux or cross-platform examples. The documentation assumes familiarity with Windows-centric tooling and does not provide parity for Linux users.
Recommendations
  • Include Azure CLI examples alongside PowerShell for all command-line instructions, especially for identity and permissions management.
  • Explicitly mention that Azure Resource Mover operations can be performed from Linux, macOS, and Windows, and provide platform-agnostic guidance.
  • Add Bash script examples for common tasks, or reference relevant Azure CLI documentation.
  • Clarify any differences in experience or prerequisites for Linux users (e.g., installation steps for Azure CLI).
  • Ensure that all portal instructions are described in a way that is not specific to any operating system.
GitHub Create Pull Request
Resource Mover https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/resource-mover/modify-target-settings.md ...main/articles/resource-mover/modify-target-settings.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides detailed PowerShell examples for modifying Azure Resource Mover destination settings, but does not include equivalent examples for Linux users (e.g., Bash, Azure CLI). The only scripting/tooling guidance is for PowerShell, which is primarily a Windows tool, and there is no mention of Linux-native tools or cross-platform alternatives. This creates a bias toward Windows users and may hinder Linux administrators from easily following the instructions.
Recommendations
  • Add equivalent Azure CLI (az) examples for all PowerShell commands shown, with clear instructions for Linux/macOS users.
  • Explicitly mention that PowerShell Core is cross-platform, but also provide Bash/CLI alternatives for common operations.
  • Include a section or note on how to perform these tasks using the Azure Portal, Azure CLI, or REST API, highlighting platform neutrality.
  • Review all scripting/tooling guidance to ensure Linux parity and avoid exclusive reliance on Windows-centric tools.
GitHub Create Pull Request
Resource Mover https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/resource-mover/remove-move-resources.md .../main/articles/resource-mover/remove-move-resources.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation provides detailed instructions and examples for removing resources from a move collection in Azure Resource Mover using the Azure Portal and PowerShell. All command-line examples use PowerShell cmdlets, with no mention of Azure CLI, Bash, or Linux-native tooling. This creates a bias toward Windows users, as PowerShell is primarily a Windows tool (despite cross-platform support, it's less common on Linux). The documentation does not provide equivalent Linux/Unix command-line examples or guidance, nor does it mention Azure CLI as an alternative. The PowerShell sections are extensive and presented before any mention of other automation or scripting options.
Recommendations
  • Add equivalent Azure CLI examples for all PowerShell commands, showing how to remove resources and collections using az resource-mover commands.
  • Explicitly mention that PowerShell is available cross-platform, but also provide Bash/Azure CLI instructions for Linux users.
  • Include a section on automating resource removal using Azure CLI, with sample scripts and output.
  • Where possible, provide parity in screenshots and walkthroughs for Linux/macOS environments (e.g., terminal screenshots, CLI usage).
  • Consider reordering or balancing the documentation so that Windows and Linux command-line options are presented together or in parallel, rather than PowerShell-first.
GitHub Create Pull Request
Resource Mover https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/resource-mover/tutorial-move-region-encrypted-virtual-machines.md ...ver/tutorial-move-region-encrypted-virtual-machines.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation exhibits Windows bias by providing only PowerShell scripts for key operations (such as copying keys between key vaults), referencing Windows VM encryption guides before Linux equivalents, and lacking Linux-specific command-line examples or parity for key tasks. While Linux VM support is mentioned, actionable steps and tooling are centered on Windows and PowerShell, with no Bash, CLI, or Linux-native alternatives provided.
Recommendations
  • Provide equivalent Bash or Azure CLI scripts for key operations, such as copying keys between key vaults, to support Linux administrators.
  • Reference both Windows and Linux guides equally when discussing VM encryption, ideally linking to Linux documentation alongside Windows.
  • Explicitly mention how Linux users can perform required tasks (e.g., running scripts, managing permissions) using Linux-native tools.
  • Ensure that prerequisites and instructions are not Windows-centric; include Linux-specific steps where appropriate.
  • Add notes or sections clarifying cross-platform compatibility for provided scripts and tools.
GitHub Create Pull Request
Resource Mover https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/resource-mover/remove-move-resources.md .../main/articles/resource-mover/remove-move-resources.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
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.
GitHub Create Pull Request
Resource Mover https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/resource-mover/modify-target-settings.md ...main/articles/resource-mover/modify-target-settings.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
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.
GitHub Create Pull Request
Resource Mover https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/resource-mover/common-questions.md .../blob/main/articles/resource-mover/common-questions.md
High Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
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.
GitHub Create Pull Request
Resource Mover https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/resource-mover/modify-target-settings.md ...main/articles/resource-mover/modify-target-settings.md
High Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
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.
GitHub Create Pull Request
Resource Mover Common questions about Azure Resource Mover .../blob/main/articles/resource-mover/common-questions.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation references PowerShell multiple times as the primary CLI for performing Resource Mover tasks, such as assigning managed identities and permissions. There are no examples or mentions of equivalent Linux/macOS tools (e.g., Azure CLI, Bash), and PowerShell is presented as the only non-portal automation method. This creates friction for Linux/macOS users who may not use PowerShell.
Recommendations
  • Add Azure CLI (az) examples alongside PowerShell for all command-line operations.
  • Explicitly mention that PowerShell commands can be run on Linux/macOS, or provide Bash script equivalents.
  • Reorder examples so that portal and cross-platform CLI methods are presented before or alongside PowerShell.
  • Clarify that automation can be done with Azure CLI, REST API, or ARM templates, not just PowerShell.
GitHub Create Pull Request
Resource Mover Modify destination settings when moving Azure VMs between regions with Azure Resource Mover ...main/articles/resource-mover/modify-target-settings.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides detailed PowerShell examples for modifying destination settings when moving Azure VMs, but does not offer equivalent CLI (az), Bash, or Linux/macOS instructions. The only code samples are in PowerShell, and there is no mention of cross-platform alternatives or parity. This creates friction for Linux/macOS users who do not use PowerShell.
Recommendations
  • Add equivalent Azure CLI (az) examples for all PowerShell commands shown, with clear instructions for Bash/shell usage.
  • Explicitly mention that these operations can be performed using Azure CLI or REST API, and link to relevant documentation.
  • Reorder sections so that cross-platform tools (Azure CLI) are presented before or alongside PowerShell.
  • Include notes on platform compatibility for each example, clarifying which OSes are supported.
GitHub Create Pull Request
← Previous Page 1 of 3 Next →