Resource Mover

37
Total Pages
29
Linux-Friendly Pages
8
Pages with Bias
21.6%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

24 issues found
Showing 1-24 of 24 flagged pages
Resource Mover Move encrypted Azure VMs across regions by using Azure Resource Mover ...ver/tutorial-move-region-encrypted-virtual-machines.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example Windows First
Summary
The documentation demonstrates a notable Windows bias in the section on copying keys between key vaults, where only a PowerShell script is provided with no equivalent Bash, Azure CLI, or Linux-native instructions. The script requires PowerShell and specific modules, which are most easily available on Windows. Additionally, references to disk encryption link first to Windows VM guides, and Windows update instructions are given before Linux guidance. No Linux/macOS alternatives for the key copy step are described.
Recommendations
  • Provide equivalent instructions and scripts for Linux/macOS users, such as Bash or Azure CLI commands to copy keys between key vaults.
  • Explicitly mention how Linux/macOS users can install and use PowerShell Core, or offer a cross-platform script.
  • Ensure that documentation links and examples for disk encryption are balanced between Windows and Linux, or presented together.
  • Where possible, use Azure CLI examples, which are cross-platform, instead of PowerShell-only scripts.
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-13 06:17
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page references PowerShell as the only CLI example for managing managed identities and permissions with Azure Resource Mover, without mentioning or providing parity for Linux/macOS users (e.g., Azure CLI or Bash). Instructions for manual operations are PowerShell-centric, and there is no guidance for equivalent steps using cross-platform tools. This creates friction for non-Windows users.
Recommendations
  • Provide Azure CLI (az) examples alongside PowerShell cmdlets for all manual operations, especially for assigning managed identities and roles.
  • Explicitly mention that PowerShell is available cross-platform, but clarify when Windows-specific features are required.
  • Add Bash scripting examples or reference how Linux/macOS users can perform equivalent tasks.
  • Reorder examples so that cross-platform tools (Azure CLI) are presented before or alongside PowerShell.
  • Include a note on tool compatibility for different operating systems.
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-13 06:17
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides detailed instructions and examples for modifying destination settings using PowerShell, which is primarily a Windows-centric tool. There are no equivalent examples or guidance for Linux/macOS users, such as using Azure CLI, Bash, or REST API. The only automation example is PowerShell, and it is presented as the sole method for scripting these changes.
Recommendations
  • Add equivalent examples using Azure CLI commands for modifying destination settings.
  • Include Bash script snippets for Linux/macOS users.
  • Reference REST API methods for advanced users who may not use PowerShell.
  • Explicitly state cross-platform options and link to relevant documentation for non-Windows environments.
  • Ensure that automation and scripting sections do not assume PowerShell as the default or only option.
GitHub Create Pull Request
Resource Mover Remove resources from a move collection in Azure Resource Mover .../main/articles/resource-mover/remove-move-resources.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
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-based instructions for removing resources from Azure Resource Mover, with no mention of Linux/macOS command-line alternatives (such as Azure CLI or Bash). All automation examples use PowerShell cmdlets, which are native to Windows and less commonly used on Linux/macOS. There is no guidance for users who prefer or require cross-platform tools, and PowerShell is presented as the default/only scripting option.
Recommendations
  • Add equivalent Azure CLI examples for all PowerShell cmdlets shown, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Explicitly mention that PowerShell Core is available on Linux/macOS, and provide installation instructions or links.
  • Reorder or parallelize examples so that Azure CLI and PowerShell instructions are presented side-by-side or with equal prominence.
  • Include notes or links for Bash scripting or other automation options where appropriate.
  • Clarify any platform-specific limitations or differences in the tools.
GitHub Create Pull Request
Resource Mover Remove resources from a move collection in Azure Resource Mover .../main/articles/resource-mover/remove-move-resources.md
Medium Priority View Details →
Scanned: 2026-01-12 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-based instructions for removing resources from an Azure Resource Mover move collection, but does not include equivalent examples for Linux/macOS users (e.g., Azure CLI, Bash). The only automation examples use PowerShell cmdlets, which are native to Windows and less commonly used on Linux/macOS. There is no mention of Azure CLI or Bash alternatives, and PowerShell is presented as the primary (and only) scripting method after the portal UI steps.
Recommendations
  • Add equivalent Azure CLI examples for all resource removal scenarios, including single and bulk removal, and collection deletion.
  • Explicitly mention that PowerShell cmdlets can be run cross-platform (with PowerShell Core), but provide CLI/Bash alternatives for users who prefer native Linux/macOS tools.
  • Reorder or parallelize automation sections so that CLI and PowerShell examples are presented together, rather than PowerShell-only.
  • Clarify any platform-specific requirements or limitations for each method.
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-12 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 managing Azure Resource Mover, especially for tasks like assigning managed identities and permissions. There are no examples or mentions of equivalent Linux/macOS tools (such as Azure CLI or Bash), nor are cross-platform alternatives discussed. The instructions for manual operations are PowerShell-centric, which may create friction for Linux/macOS users.
Recommendations
  • Add Azure CLI (az) examples alongside PowerShell for all command-line instructions.
  • Explicitly mention that PowerShell Core is available on Linux/macOS, or clarify cross-platform support.
  • Provide Bash or shell script equivalents for common tasks.
  • Reorder examples so that cross-platform tools (Azure CLI) are presented before or alongside PowerShell.
  • Include a note on platform compatibility for all command-line instructions.
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-12 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 examples for modifying destination settings during Azure VM migration, but does not include equivalent examples for Linux/macOS users (e.g., Azure CLI, Bash). The only command-line instructions use PowerShell, which is traditionally associated with Windows environments. No mention is made of cross-platform tools or alternative workflows.
Recommendations
  • Add Azure CLI examples for all PowerShell commands shown, ensuring Linux/macOS users can follow along without installing PowerShell.
  • Explicitly mention that Azure CLI and PowerShell are both supported, and link to relevant cross-platform tool documentation.
  • Where possible, show both PowerShell and CLI/Bash examples side-by-side.
  • Clarify any platform-specific requirements for the commands (e.g., prerequisites for PowerShell on Linux/macOS).
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
Medium Priority View Details →
Scanned: 2026-01-12 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 demonstrates notable Windows bias, especially in the section on copying keys between key vaults, where only a PowerShell script is provided with no Linux/bash equivalent. References to disk encryption link to Windows-specific guides first, and the scripting instructions assume use of PowerShell and Windows modules. Linux users are left without direct guidance or parity for key operations, creating friction for non-Windows environments.
Recommendations
  • Provide a bash/CLI version of the key copy script, or document how Linux/macOS users can perform the same operation using Azure CLI or REST API.
  • Include Linux-focused examples and links alongside Windows ones, especially in encryption and key management sections.
  • Clarify that PowerShell can be installed on Linux/macOS, or offer instructions for cross-platform usage.
  • Reorder references so that Windows and Linux are treated equally, or present both options together.
  • Explicitly mention any limitations or required adaptations for Linux/macOS users.
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-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation references PowerShell as the only command-line method for managing Resource Mover via scripts, with no mention of Azure CLI or Bash examples. Instructions for assigning managed identity and permissions are given only for PowerShell, and the portal UI is described generically. There are no Linux/macOS-specific instructions or examples, and PowerShell is referenced before any cross-platform alternatives.
Recommendations
  • Add Azure CLI examples alongside PowerShell for all command-line instructions, especially for assigning managed identity and permissions.
  • Explicitly state that Azure CLI and Bash can be used on Linux/macOS, and provide equivalent steps.
  • Where PowerShell is mentioned, clarify its cross-platform availability or provide links to install/use PowerShell Core on Linux/macOS.
  • Ensure that all scripting and automation examples are available for both Windows and Linux/macOS users.
  • Consider reordering examples so that cross-platform tools (Azure CLI) are shown before or alongside 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-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides detailed instructions and code samples exclusively for PowerShell, which is primarily a Windows-centric tool. There are no equivalent examples for Azure CLI, Bash, or other cross-platform tools. The section on modifying settings in PowerShell is the only place where command-line automation is demonstrated, implicitly prioritizing Windows users and leaving Linux/macOS users without direct guidance.
Recommendations
  • Add equivalent examples using Azure CLI, which is cross-platform and widely used on Linux/macOS.
  • Explicitly mention that PowerShell Core is available on Linux/macOS, if PowerShell usage is necessary.
  • Provide Bash script examples for common tasks, or at least reference Azure CLI documentation.
  • Reorder or parallelize examples so that Windows and Linux/macOS approaches are presented together.
GitHub Create Pull Request
Resource Mover Remove resources from a move collection in Azure Resource Mover .../main/articles/resource-mover/remove-move-resources.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
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 PowerShell-based instructions for removing resources from an Azure Resource Mover move collection, but does not mention or provide examples for Linux/macOS users (e.g., Azure CLI, Bash). All automation examples use PowerShell cmdlets, which are native to Windows and less commonly used on Linux/macOS. There is no guidance for equivalent operations using cross-platform tools, and PowerShell is presented as the only scripting option.
Recommendations
  • Add equivalent Azure CLI examples for all resource removal operations, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Explicitly mention that PowerShell cmdlets can be run on Linux/macOS if PowerShell Core is installed, but recommend Azure CLI for native Linux/macOS workflows.
  • Reorder sections or provide parallel examples so that Windows and Linux/macOS users see relevant instructions for their platforms.
  • Include a note or table summarizing which tools are available on which platforms, and link to installation guides for Azure CLI and PowerShell Core.
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
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example Windows First
Summary
The documentation exhibits a notable Windows bias in the key vault copy step, where only a PowerShell script (.ps1) is provided for copying encryption keys and secrets between key vaults. There are no equivalent instructions or scripts for Linux/macOS users (e.g., Bash, Azure CLI, or Python). Additionally, references to disk encryption and key management link to Windows-centric guides first, and Windows update instructions are given before Linux guidance in VM preparation steps.
Recommendations
  • Provide an equivalent Bash or Azure CLI script for copying keys and secrets between key vaults, or document how to perform the operation using cross-platform tools.
  • Include explicit instructions for Linux/macOS users on how to run the key copy operation (e.g., using Azure CLI, REST API, or Python SDK).
  • Ensure that references to disk encryption and key management include both Windows and Linux guides, ideally presenting them together or in parallel.
  • In VM preparation steps, present Windows and Linux instructions side-by-side or in a neutral order.
GitHub Create Pull Request
Resource Mover Move resources to another region with Azure Resource Mover ...es/resource-mover/move-region-within-resource-group.md
Low Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation presents Windows VM requirements before Linux VM requirements and mentions installing Windows updates explicitly, while Linux instructions are more generic. No command-line examples (PowerShell, Bash, CLI) are given, and no Windows-only tools or patterns are referenced. The overall process is portal-centric and does not show significant platform bias beyond ordering.
Recommendations
  • List Linux VM requirements before or alongside Windows VM requirements to avoid implicit prioritization.
  • Provide explicit Linux update instructions or link to common distributor update guides.
  • Ensure parity in troubleshooting and prerequisites for both platforms.
  • If command-line examples are added in future, include both PowerShell (Windows) and Bash/Azure CLI (Linux/macOS) equivalents.
GitHub Create Pull Request
Resource Mover Move Azure VMs across regions with Azure Resource Mover ...esource-mover/tutorial-move-region-virtual-machines.md
Low Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation provides both Windows and Linux prerequisites, but Windows is mentioned first in the VM preparation section. No command-line examples (PowerShell, Bash, CLI) are given, and the tutorial is entirely portal-based, so there are no Windows-only tools or examples. The only minor bias is listing Windows before Linux when discussing certificate updates.
Recommendations
  • List Linux and Windows instructions in parallel or alternate order to avoid implicit prioritization.
  • Explicitly state that the portal-based workflow is OS-agnostic and does not require Windows-specific tools.
  • If command-line alternatives are added in the future, ensure both PowerShell and Bash/Azure CLI examples are provided.
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
Low Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page generally maintains parity between Windows and Linux, but there is a subtle Windows bias. In the 'Check VM requirements' section, Windows is mentioned first when verifying supported VMs and when discussing certificate updates. For Windows, explicit instructions are given ('install the latest Windows updates'), while for Linux, users are told to 'follow the Linux distributor guidance' without further detail or example. No command-line examples (PowerShell, Bash, CLI) are present, so there is no overt tooling bias, but Windows is consistently referenced before Linux.
Recommendations
  • Provide explicit Linux guidance or examples for updating certificates and CRLs, similar to the Windows instructions.
  • Alternate the order of Windows and Linux references to avoid always listing Windows first.
  • Where possible, link to or include Linux-specific documentation or commands for common tasks.
  • Ensure that any future command-line examples include both PowerShell and Bash/Azure CLI equivalents.
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
Low Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation presents Windows VM support before Linux VM support, listing Windows operating systems and requirements first. However, both Windows and Linux platforms are covered in detail, with no exclusive Windows tools, examples, or instructions that would prevent Linux users from completing the task. There are no PowerShell-heavy sections, Windows-only patterns, or missing Linux examples.
Recommendations
  • Reorder sections to present Windows and Linux support in parallel or alternate order, or combine into a single 'Supported Operating Systems' table to avoid implicit prioritization.
  • Explicitly mention that instructions and requirements apply equally to both Windows and Linux unless otherwise stated.
  • Ensure parity in notes and troubleshooting guidance for both platforms (e.g., password reset instructions for Linux are present, but check for similar parity in other areas).
GitHub Create Pull Request
Resource Mover Move resources to another region with Azure Resource Mover ...es/resource-mover/move-region-within-resource-group.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates mild Windows bias by mentioning Windows VM requirements and update procedures before Linux equivalents, and by providing more explicit instructions for Windows (e.g., 'install the latest Windows updates') while referring Linux users to distributor guidance without concrete steps. No command-line examples (PowerShell, Bash, CLI) are present, and the overall process is portal-driven, reducing the impact of platform bias. However, Windows is referenced first and with more detail in critical prerequisite steps.
Recommendations
  • Present Windows and Linux instructions in parallel, or alternate which is listed first.
  • Provide concrete steps or links for updating Linux certificates and CRLs, similar to the Windows update guidance.
  • Where possible, include explicit Linux examples or commands, not just distributor guidance.
  • Review all sections to ensure Linux users have equal clarity and actionable steps.
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
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates mild Windows bias. In sections discussing VM requirements, Windows is mentioned first and given explicit instructions (install latest Windows updates), while Linux guidance is generic ('follow distributor guidance') and lacks concrete steps or examples. No command-line examples (PowerShell, Bash, CLI) are shown, but Windows is prioritized in explanatory text. There are no Windows-only tools or instructions, and the process is primarily portal-based, which is cross-platform.
Recommendations
  • Provide explicit Linux instructions for updating certificates and CRLs, including example commands for common distributions (e.g., Ubuntu, CentOS).
  • Ensure Linux VM support is described with equal detail as Windows, possibly linking to distributor-specific documentation.
  • When listing OS types, alternate the order or mention both equally (e.g., 'On Windows or Linux VMs...').
  • If command-line instructions are added, include both PowerShell and Bash/Azure CLI examples.
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
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation presents Windows VM support before Linux VM support, listing Windows operating systems and requirements first. However, both platforms are covered in detail, with no exclusive Windows tools, examples, or instructions. No PowerShell or Windows-specific command-line patterns are present, and Linux support is comprehensive, including kernel and file system details.
Recommendations
  • Reorder the sections so that Windows and Linux VM support are presented in parallel or alternate order, or combine them into a single table for parity.
  • Explicitly mention that instructions and requirements apply equally to both platforms where relevant.
  • Add a short introductory note affirming equal support for both Windows and Linux VMs to reassure users.
  • If there are platform-specific steps (e.g., password reset for Ubuntu), consider providing equivalent guidance for Windows VMs.
GitHub Create Pull Request
Resource Mover Move Azure VMs across regions with Azure Resource Mover ...esource-mover/tutorial-move-region-virtual-machines.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation provides both Windows and Linux prerequisites for VM preparation, but Windows is mentioned first and with more explicit instructions (install Windows updates), while Linux guidance is generic ('follow distributor guidance'). No PowerShell, CLI, or OS-specific tooling examples are present; the tutorial is portal-centric and does not show command-line steps for either platform. There is a slight ordering bias towards Windows, but Linux is not excluded.
Recommendations
  • Provide equally detailed instructions for Linux VM preparation, such as example commands to update certificates and CRLs (e.g., using 'update-ca-certificates' or 'yum update ca-certificates').
  • Alternate the order of Windows and Linux instructions, or present them in parallel to avoid perceived prioritization.
  • Where possible, include Azure CLI or REST API steps for cross-platform automation, not just portal walkthroughs.
  • Link to distributor-specific Linux guidance for updating certificates and CRLs.
GitHub Create Pull Request
Resource Mover Move resources to another region with Azure Resource Mover ...es/resource-mover/move-region-within-resource-group.md
Low Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Windows Examples Missing Linux Example
Summary
The documentation page exhibits minor Windows bias, primarily in the 'Check VM requirements' section. Windows VM requirements and update instructions are listed before Linux equivalents, and explicit update steps are provided for Windows (install latest Windows updates), while Linux guidance is generic ('follow the Linux distributor guidance'). No command-line examples (PowerShell, Bash, etc.) are present, and the rest of the documentation is platform-neutral, focusing on Azure portal UI steps.
Recommendations
  • Provide equally detailed instructions for Linux VMs, such as common commands to update certificates and CRLs (e.g., update-ca-certificates for Debian/Ubuntu, or update-ca-trust for RHEL/CentOS).
  • List Linux VM requirements before or alongside Windows requirements to avoid 'Windows first' ordering.
  • If mentioning Windows update procedures, offer equivalent Linux update procedures (with example commands or links to distributor documentation).
  • Explicitly state that all steps are applicable to both Windows and Linux unless otherwise noted.
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
Low Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation mentions both Windows and Linux VM support, but in the 'Check VM requirements' section, Windows update instructions are given explicitly, while Linux instructions are generic and refer users to distributor guidance. No Linux-specific examples, commands, or troubleshooting steps are provided, and Windows is mentioned first in most cases. There are no PowerShell or Windows tool-specific examples, but the pattern of mentioning Windows before Linux and lack of Linux-specific detail indicates a mild Windows bias.
Recommendations
  • Provide explicit Linux update instructions or link to common Linux certificate update commands (e.g., for Ubuntu, CentOS, etc.).
  • Include Linux-specific troubleshooting tips or examples where relevant.
  • Alternate the order of Windows and Linux mentions, or group instructions by OS for parity.
  • Add screenshots or CLI examples for Linux environments if applicable.
GitHub Create Pull Request
Resource Mover Move Azure VMs across regions with Azure Resource Mover ...esource-mover/tutorial-move-region-virtual-machines.md
Low Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation mentions both Windows and Linux VMs in the prerequisites, but when discussing preparation steps, it lists Windows instructions first ("On Windows VMs, install the latest Windows updates"), followed by a generic Linux statement. No PowerShell, Windows-only tools, or exclusive Windows patterns are present, and Linux is referenced with parity in support checks. All examples and instructions are platform-neutral and focus on the Azure portal UI.
Recommendations
  • Alternate the order in which Windows and Linux instructions are presented, or present them in parallel to avoid implicit prioritization.
  • Provide more specific Linux guidance, such as example commands for updating certificates or CRLs on common distributions (e.g., Ubuntu, CentOS).
  • Ensure that any future CLI or scripting examples include both PowerShell (Windows) and Bash (Linux/macOS) equivalents.
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
Low Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation presents Windows VM support before Linux VM support, listing Windows operating systems and requirements first. However, both platforms receive detailed, parity-focused coverage of supported versions, prerequisites, and limitations. No Windows-specific tools, PowerShell examples, or exclusive Windows patterns are present, and Linux support is comprehensive with kernel and filesystem details.
Recommendations
  • Consider presenting Windows and Linux support sections in parallel or alternating order, or explicitly stating that both platforms are equally supported.
  • Add a brief introductory note clarifying that both Windows and Linux VMs are supported and that the documentation covers both platforms in detail.
  • If possible, provide cross-platform troubleshooting steps or examples for common issues (e.g., password reset, agent installation) for both Windows and Linux.
GitHub Create Pull Request