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 26-50 of 57 flagged pages
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-14 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 removing resources from an Azure Resource Mover move collection, but does not offer equivalent examples for Linux/macOS users (e.g., Azure CLI or Bash). PowerShell is a Windows-centric tool, and its exclusive use creates friction for users on other platforms. Additionally, PowerShell instructions are presented before any mention of cross-platform alternatives, and there is no guidance for Linux/macOS users.
Recommendations
  • Add Azure CLI examples for all resource removal operations, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Explicitly mention that PowerShell is available on Linux/macOS, but provide installation instructions or alternatives for users who may not have it.
  • Reorder sections or provide parallel instructions so that Linux/macOS users are not required to adapt Windows-centric examples.
  • Include Bash script samples where appropriate.
  • Add a note clarifying platform compatibility for each tool used.
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-14 00:00
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, especially in the section on copying keys between key vaults, where only a PowerShell script (.ps1) is provided and explicitly recommended. There are no equivalent instructions or scripts for Linux/macOS users (e.g., Bash, Azure CLI, or Python). Additionally, references to Windows VMs and Windows-specific encryption scenarios appear before Linux equivalents in some prerequisite sections.
Recommendations
  • Provide equivalent scripts or instructions for Linux/macOS users, such as Bash scripts, Azure CLI commands, or Python scripts for copying keys between key vaults.
  • Explicitly mention cross-platform alternatives and clarify which steps can be performed on any OS using Azure CLI or REST API.
  • Where possible, present Windows and Linux examples side-by-side, or clarify when a step is OS-agnostic.
  • Ensure that references to both Windows and Linux VMs are balanced and not presented with a Windows-first ordering.
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 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 for command-line operations (e.g., assigning managed identities and permissions) without mentioning or providing equivalent examples for Azure CLI or Bash, which are commonly used on Linux/macOS. Instructions for manual operations are described only for PowerShell, and the language implies PowerShell as the default non-portal automation tool. No Linux/macOS-specific tools or patterns are discussed.
Recommendations
  • Add Azure CLI examples alongside PowerShell for all command-line instructions, especially for identity and permission management.
  • Explicitly mention that Azure CLI and Bash are supported and provide links to relevant documentation.
  • Ensure that automation and scripting guidance is not Windows-centric by including cross-platform tool references.
  • Reorder 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-13 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 offer equivalent examples for Linux/macOS users (e.g., Azure CLI, Bash). PowerShell—a Windows-centric tool—is presented as the primary and only automation method, with no mention of cross-platform alternatives. This creates friction for users on Linux or macOS, who may not have access to PowerShell or prefer using Azure CLI.
Recommendations
  • Add equivalent Azure CLI (az) examples for all PowerShell commands shown.
  • Explicitly mention that PowerShell is available cross-platform, but also provide Bash/CLI alternatives for Linux/macOS users.
  • Reorder examples so that CLI and PowerShell are presented together, or alternate which is shown first.
  • Include a note or section on modifying destination settings via the Azure Portal, which is platform-agnostic.
  • Clarify any limitations or differences between PowerShell and CLI approaches.
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 00:00
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, with no mention of Linux/macOS-friendly alternatives such as Azure CLI or Bash scripting. All command-line examples use PowerShell cmdlets, which are native to Windows and less commonly used on Linux/macOS. There are no Azure CLI examples, and the documentation does not address cross-platform usage or provide parity for Linux/macOS users.
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 can be installed on Linux/macOS, if PowerShell must be used, and provide installation guidance.
  • Reorder or parallelize examples so that Azure CLI and PowerShell instructions are presented side-by-side, or at least Azure CLI is not always secondary.
  • Include notes or sections addressing Linux/macOS users, clarifying any differences or additional steps required.
  • Review screenshots and UI instructions to ensure they do not assume Windows-only environments.
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-13 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 a notable Windows bias, especially in the critical step of copying encryption keys between key vaults. Only a PowerShell script (.ps1) is provided, with explicit instructions to use PowerShell and required modules, but no equivalent Bash, Azure CLI, or Linux-native example is given. References to disk encryption also link to Windows-specific guides first. While Linux VM support is mentioned, Linux users are left without clear guidance for the key copy step, creating friction for non-Windows environments.
Recommendations
  • Provide a Bash or Azure CLI script for copying keys between key vaults, or document how to perform the operation using cross-platform tools.
  • Include explicit instructions or examples for Linux/macOS users, such as using Azure CLI commands or REST API calls.
  • Ensure references to disk encryption cover both Windows and Linux equally, and link to Linux guides alongside Windows guides.
  • When mentioning prerequisites or steps, avoid listing Windows tools or patterns first unless they are universally applicable.
GitHub Create Pull Request
Resource Mover Move resources to another region with Azure Resource Mover ...es/resource-mover/move-region-within-resource-group.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 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 are explicit for Windows ('install the latest Windows updates') but vague for Linux ('follow the Linux distributor guidance'). No Linux-specific commands, examples, or troubleshooting steps are provided, while Windows is referenced directly. There are no PowerShell-heavy or Windows tools examples, but the ordering and detail favor Windows.
Recommendations
  • Provide explicit Linux update instructions, including common commands for popular distributions (e.g., Ubuntu, CentOS) to update certificates and CRLs.
  • Ensure Linux VM support is mentioned with equal prominence and detail as Windows, possibly alternating the order or grouping them together.
  • Add Linux-specific troubleshooting steps or examples where relevant, such as verifying kernel versions or updating packages.
  • Include links to Linux documentation or distributor-specific guides for certificate management.
  • Review other sections for implicit assumptions about Windows and ensure parity in guidance for Linux users.
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
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page exhibits mild Windows bias. In the 'Check VM requirements' section, Windows VM support is listed before Linux VM support, and explicit instructions are given for Windows (install latest updates), while Linux instructions are generic ('follow distributor guidance'). There are no Linux-specific command examples or troubleshooting steps, and no Linux tool references. All examples and screenshots are platform-neutral (Azure portal), but the narrative and ordering favor Windows slightly.
Recommendations
  • Provide explicit Linux instructions for updating certificates and CRL, including common commands for popular distributions (e.g., Ubuntu, CentOS).
  • List Linux VM support before or alongside Windows VM support to avoid ordering bias.
  • Include troubleshooting tips or example commands for Linux VMs where relevant.
  • Reference Linux tools or patterns (e.g., shell commands, package managers) in parity with Windows update instructions.
  • Ensure that any future CLI or script examples include both PowerShell and Bash/Azure CLI variants.
GitHub Create Pull Request
Resource Mover Choose a tool for moving Azure resources across regions .../blob/main/articles/resource-mover/select-move-tool.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Missing Linux Example 🔧 Windows Tools
Summary
The documentation page does not provide any platform-specific command-line examples or tooling guidance, but references Azure Site Recovery—a tool historically associated with Windows environments. There is no mention of Linux-specific tools, patterns, or parity, nor are any Linux CLI or automation examples provided. The absence of platform-neutral or Linux-specific guidance may disadvantage Linux administrators.
Recommendations
  • Explicitly mention that Azure Resource Mover and Site Recovery support both Windows and Linux workloads, if applicable.
  • Provide examples or links for moving Linux-based resources, including any considerations or differences in process.
  • Include CLI (az CLI) and automation (Bash, PowerShell) examples side-by-side where relevant.
  • Clarify whether any steps or tools have platform-specific requirements or limitations.
  • Add documentation links or guidance for Linux VM migration scenarios, especially for Azure Site Recovery.
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
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by listing Windows VM support before Linux VM support, providing more detailed requirements and links for Windows (e.g., servicing stack update, SHA-2 update), and mentioning Windows-specific update tools and patterns. Linux support is listed second, and while kernel versions and distributions are covered, there are fewer detailed troubleshooting steps or links compared to Windows. No PowerShell examples or commands are present, and Linux file systems and storage are mentioned, but not in the same detail as Windows prerequisites.
Recommendations
  • Present Windows and Linux VM support in parallel sections or in alphabetical order to avoid implicit prioritization.
  • Provide equally detailed troubleshooting steps and update requirements for Linux distributions (e.g., links to required kernel updates, common issues during migration).
  • Include Linux-specific tools and patterns (such as cloud-init, package managers, or systemd) where relevant, and offer parity in guidance for both platforms.
  • Add more Linux-focused examples and links for common migration issues, similar to the Windows SSU/SHA-2 update guidance.
  • Ensure that any update or configuration steps for Windows have Linux equivalents or a note if not applicable.
GitHub Create Pull Request
Resource Mover Move Azure VMs across regions with Azure Resource Mover ...esource-mover/tutorial-move-region-virtual-machines.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a subtle Windows bias in the 'Prepare VMs' section, where instructions for updating certificates are given for Windows VMs first and in more detail, while Linux VMs are mentioned second and only generically. There are no explicit Linux command examples or distributor-specific guidance, and no Linux-specific troubleshooting or patterns are discussed elsewhere. The page does not provide PowerShell-heavy examples or Windows-only tools, but the order and detail favor Windows.
Recommendations
  • Provide distributor-specific instructions or examples for updating certificates and CRLs on popular Linux distributions (e.g., Ubuntu, CentOS, RHEL).
  • Include Linux command-line examples (such as using apt, yum, or update-ca-certificates) alongside Windows Update instructions.
  • Ensure that troubleshooting steps and post-move configuration guidance cover both Windows and Linux VMs equally, with explicit mention of Linux tools and patterns where relevant.
  • Consider alternating the order of Windows and Linux instructions, or presenting them in parallel, to avoid implicit prioritization.
GitHub Create Pull Request
Resource Mover https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/resource-mover/move-region-availability-zone.md ...ticles/resource-mover/move-region-availability-zone.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page mentions both Windows and Linux VMs in the requirements section, but provides more explicit instructions for Windows (e.g., 'install the latest Windows updates') while referring Linux users to distributor guidance without specifics. There are no command-line examples (PowerShell, Bash, CLI) for either platform, but where OS-specific instructions are given, Windows is mentioned first and in more detail. No Linux-specific tools or step-by-step examples are provided.
Recommendations
  • Provide explicit Linux instructions for updating certificates and CRLs, including common commands for popular distributions (e.g., Ubuntu, CentOS).
  • Ensure parity in troubleshooting and preparation steps for Linux VMs, such as listing required packages or update commands.
  • When listing OS-specific requirements, alternate the order or present Windows and Linux instructions side-by-side.
  • Add CLI examples (Azure CLI, Bash) for common operations, ensuring both Windows and Linux users have clear guidance.
  • Include references to Linux-specific documentation or tools where appropriate.
GitHub Create Pull Request
Resource Mover https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/resource-mover/move-region-within-resource-group.md ...es/resource-mover/move-region-within-resource-group.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation demonstrates a subtle Windows bias. In the 'Check VM requirements' section, Windows VM support is listed before Linux VM support, and instructions for updating certificates are more explicit for Windows (install Windows updates) than for Linux (refer to distributor guidance). There are no command-line examples or tooling references, but where OS-specific guidance is given, Windows is mentioned first and in more detail, while Linux guidance is less direct and lacks concrete steps.
Recommendations
  • Present Windows and Linux guidance in parallel, giving equal detail and prominence to both.
  • Provide explicit Linux update instructions or link to common distributor documentation (e.g., Ubuntu, Red Hat) for updating certificates and CRLs.
  • When listing supported VM types or requirements, alternate or group Windows and Linux information together, rather than listing Windows first.
  • Include example commands or scripts for both Windows (PowerShell) and Linux (bash/CLI) where relevant, especially for preparatory steps.
  • Review all OS-specific instructions to ensure Linux users are not left with vague or incomplete guidance.
GitHub Create Pull Request
Resource Mover https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/resource-mover/support-matrix-move-region-azure-vm.md .../resource-mover/support-matrix-move-region-azure-vm.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation page presents Windows VM support before Linux VM support, listing Windows operating systems and related requirements (such as SSU and SHA-2 updates) in detail. Windows-specific tools and update patterns are referenced (servicing stack update, SHA-2 update), while Linux support is presented second and focuses on kernel versions and distributions. No PowerShell or command-line examples are present, but the ordering and depth of Windows-specific requirements indicate a subtle Windows bias.
Recommendations
  • Present Linux and Windows VM support in parallel sections or alternate the order between documentation pages to avoid implicit prioritization.
  • Include equivalent details for Linux VMs, such as required packages, update procedures, or troubleshooting steps, similar to the Windows SSU/SHA-2 guidance.
  • Reference Linux-specific tools or update mechanisms (e.g., apt, yum, zypper) where relevant, to match the specificity given to Windows update requirements.
  • Explicitly state that both Windows and Linux VMs are first-class citizens in Azure Resource Mover support, and provide parity in troubleshooting and preparation guidance.
GitHub Create Pull Request
Resource Mover https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/resource-mover/tutorial-move-region-virtual-machines.md ...esource-mover/tutorial-move-region-virtual-machines.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a mild Windows bias. In the 'Prepare VMs' section, instructions for ensuring VMs have the latest trusted root certificates and CRL are given with explicit steps for Windows ('install the latest Windows updates'), while Linux guidance is generic ('follow distributor guidance') and lacks concrete examples or commands. No Linux-specific commands, tools, or step-by-step instructions are provided throughout the tutorial, whereas Windows is mentioned first and more specifically.
Recommendations
  • Provide explicit Linux instructions for updating trusted root certificates and CRL, including example commands for popular distributions (e.g., Ubuntu, CentOS).
  • Ensure Linux and Windows guidance are presented with equal specificity and detail.
  • Alternate the order of Windows and Linux mentions, or present them together, to avoid implicit prioritization.
  • Include screenshots or CLI examples for Linux where relevant, not just generic guidance.
  • Reference Linux-specific documentation or best practices alongside Windows equivalents.
GitHub Create Pull Request
Resource Mover https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/resource-mover/move-region-availability-zone.md ...ticles/resource-mover/move-region-availability-zone.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
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 the 'Check VM requirements' section, Windows VM support is listed before Linux VM support, and instructions for updating trusted root certificates are explicit for Windows (install Windows updates), while Linux guidance is generic ('follow the Linux distributor guidance') with no concrete steps or examples. No command-line examples (PowerShell, Bash, CLI) are present, but when platform-specific details are mentioned, Windows is prioritized or described in more detail.
Recommendations
  • Present Windows and Linux VM support information in parallel, or alternate the order in which they are listed.
  • Provide explicit Linux instructions for updating trusted root certificates and CRLs, including example commands for popular distributions (e.g., Ubuntu, CentOS).
  • Where Windows-specific steps are given, ensure Linux equivalents are described with similar detail.
  • Include CLI or script examples for both Windows (PowerShell) and Linux (Bash/Azure CLI) where relevant.
  • Review other sections for subtle platform prioritization and ensure equal coverage for Linux users.
GitHub Create Pull Request
Resource Mover https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/resource-mover/move-region-within-resource-group.md ...es/resource-mover/move-region-within-resource-group.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a subtle Windows bias. In the 'Check VM requirements' section, Windows VM support is mentioned before Linux VM support, and Windows update instructions are provided explicitly, while Linux users are referred to generic distributor guidance without concrete steps or examples. No Linux-specific commands, tools, or troubleshooting steps are provided, and the documentation lacks parity in actionable guidance for Linux users.
Recommendations
  • Present Windows and Linux VM support information in parallel, or alternate the order to avoid implicit prioritization.
  • Provide explicit Linux update instructions, including example commands for popular distributions (e.g., Ubuntu, CentOS) to update certificates and CRLs.
  • Include troubleshooting steps or common issues for Linux VMs, similar to what is provided for Windows.
  • Ensure that any references to OS-specific requirements or actions are equally detailed for both Windows and Linux.
  • Add example scripts or commands for both Windows (PowerShell) and Linux (Bash/CLI) where relevant.
GitHub Create Pull Request
Resource Mover https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/resource-mover/support-matrix-move-region-azure-vm.md .../resource-mover/support-matrix-move-region-azure-vm.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation page presents Windows VM support before Linux VM support, listing Windows operating systems and related requirements first. Windows-specific update tools and requirements (servicing stack update, SHA-2 update) are described in detail, with links to Microsoft support articles. In contrast, Linux support is listed after Windows, and while kernel versions and distributions are covered, there are fewer details about troubleshooting, required updates, or Linux-specific migration caveats. No PowerShell or CLI examples are present, but the ordering and depth of Windows information indicate a subtle Windows bias.
Recommendations
  • Present Linux and Windows support in parallel sections or alternate the order to avoid implicit prioritization.
  • Provide equivalent troubleshooting and update guidance for Linux distributions, such as links to kernel update instructions or common migration issues.
  • Include Linux-specific caveats or best practices for migration, similar to the detailed Windows update requirements.
  • Ensure that any references to tools or update processes are balanced between Windows and Linux, with links to official documentation for both.
  • If examples or step-by-step instructions are added, provide both Windows and Linux variants.
GitHub Create Pull Request
Resource Mover https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/resource-mover/move-region-availability-zone.md ...ticles/resource-mover/move-region-availability-zone.md
Medium Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
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.
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-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation mentions both Windows and Linux VMs in the prerequisites and requirements, but when discussing certificate updates, it provides explicit instructions for Windows ('install the latest Windows updates') while for Linux it only refers users to 'Linux distributor guidance' without examples or specifics. No command-line examples (PowerShell, Bash, CLI) are provided, but where OS-specific guidance is given, Windows is mentioned first and in more detail.
Recommendations
  • Provide explicit Linux instructions or examples for updating certificates and CRLs, similar to the Windows update guidance.
  • Ensure parity in troubleshooting and preparation steps for both Windows and Linux VMs, possibly linking to or including common Linux commands or scripts.
  • When listing OS-specific steps, alternate the order or present both Windows and Linux guidance together.
  • Add CLI or script examples for both Windows (PowerShell) and Linux (Bash/Azure CLI) where relevant, especially for automation scenarios.
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-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Windows Heavy
Summary
The documentation demonstrates mild Windows bias, particularly in the 'Check VM requirements' section, where Windows VM support and update instructions are listed before Linux equivalents. Windows update instructions are explicit, while Linux guidance is generic ('follow distributor guidance'). No command-line examples (PowerShell, Bash) are present, and all steps use the Azure Portal, so direct tooling bias is minimal.
Recommendations
  • Present Windows and Linux instructions in parallel or with equal detail, rather than listing Windows first.
  • Provide explicit Linux update instructions or reference common distributions (e.g., Ubuntu, RHEL) for certificate updates.
  • Where possible, include CLI (az, Bash) examples for all steps, not just portal walkthroughs.
  • Ensure that any troubleshooting or validation steps are equally detailed for Linux and Windows VMs.
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-14 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. There are no PowerShell-heavy sections or missing Linux equivalents.
Recommendations
  • Reorder the operating system support sections so that Windows and Linux are presented in parallel or alternate the order in different documentation pages.
  • Add a short introductory note clarifying that both Windows and Linux VMs are equally supported, and the order does not imply priority.
  • Ensure future updates provide equal prominence to Linux-specific requirements and troubleshooting steps.
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-14 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation demonstrates minor Windows bias in the 'Prepare VMs' section, where Windows instructions (installing Windows updates) are mentioned before Linux instructions (follow distributor guidance for certificates/CRL). Both platforms are covered, and there are no Windows-only examples, tools, or commands. The rest of the tutorial is platform-neutral and focuses on Azure portal workflows.
Recommendations
  • Present Windows and Linux instructions in parallel or in alphabetical order to avoid implicit prioritization.
  • Expand Linux guidance to include specific commands or links for common distributions (e.g., Ubuntu, CentOS) for updating certificates/CRL.
  • Explicitly state that all steps apply equally to both Windows and Linux VMs unless otherwise noted.
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 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Windows Examples Missing Linux Example
Summary
The documentation shows mild Windows bias in the 'Check VM requirements' section, where Windows VM support and update instructions are listed before Linux equivalents. Windows update instructions are explicit, while Linux instructions are generic ('follow distributor guidance'). No PowerShell or Windows-only tool examples are present, and the rest of the documentation is platform-neutral, focusing on Azure portal workflows.
Recommendations
  • Present Windows and Linux VM support links together or in alphabetical order to avoid Windows-first ordering.
  • Provide explicit Linux update instructions or link to common Linux certificate update procedures for popular distributions (e.g., Ubuntu, RHEL).
  • Where instructions differ for Windows and Linux, ensure both are equally detailed and actionable.
  • Consider adding CLI or script examples for both Windows (PowerShell) and Linux (Bash/Azure CLI) if relevant.
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 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 and certificate updates, Windows instructions are provided explicitly ("install the latest Windows updates"), while Linux users are directed to generic distributor guidance without concrete steps or examples. Windows VM support is listed before Linux VM support. No command-line examples (PowerShell, Bash, CLI) are present, but the guidance is slightly more detailed for Windows users.
Recommendations
  • Provide explicit Linux instructions or examples for updating certificates and CRLs, similar to the Windows update guidance.
  • List Linux VM support alongside or before Windows VM support to avoid ordering bias.
  • Where possible, include Linux-specific troubleshooting tips or references.
  • Ensure parity in detail and clarity for both Windows and Linux users throughout the documentation.
GitHub Create Pull Request
← Previous Page 2 of 3 Next →