Storage Mover

25
Total Pages
9
Linux-Friendly Pages
16
Pages with Bias
64.0%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

85 issues found
Showing 1-25 of 85 flagged pages
Storage Mover How to deploy an Azure Storage Mover agent. ...-docs/blob/main/articles/storage-mover/agent-deploy.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 exhibits a Windows bias by prioritizing Windows Hyper-V in instructions, providing detailed step-by-step guidance and screenshots for Hyper-V only, and referencing Windows Server documentation. VMware is mentioned but not detailed. There is no mention of Linux-based virtualization platforms (e.g., KVM, VirtualBox), and no Linux-specific examples or instructions are provided. The agent image is described as Linux-based, but all deployment guidance is for Windows-centric tools.
Recommendations
  • Add explicit support statements and instructions for Linux-based virtualization platforms (e.g., KVM, VirtualBox, Proxmox) if technically feasible.
  • Provide step-by-step instructions and screenshots for deploying the agent VM on at least one popular Linux virtualization platform.
  • Include Linux CLI examples for agent management tasks where applicable, alongside PowerShell and Azure CLI.
  • Reference Linux documentation and tools (e.g., libvirt, virt-manager) in relevant sections.
  • Clarify any limitations or requirements for Linux hosts, and update prerequisites to mention Linux options if/when supported.
GitHub Create Pull Request
Storage Mover How to schedule bandwidth limitations of a Storage Mover agent ...ob/main/articles/storage-mover/bandwidth-management.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 page demonstrates a bias toward Windows environments by exclusively providing PowerShell examples for scripting and automation, with no mention of Linux-native tools or CLI alternatives. The instructions for agent console access are generic, but all automation and scripting guidance is Windows-centric, lacking parity for Linux users.
Recommendations
  • Provide equivalent examples using Azure CLI (az), which is cross-platform and commonly used on Linux and macOS.
  • Include instructions for configuring bandwidth limits using REST API calls or ARM templates, which are OS-agnostic.
  • Explicitly mention that PowerShell Core (pwsh) is available on Linux and macOS, and clarify any OS-specific requirements or limitations.
  • Add troubleshooting or setup notes for Linux environments, such as installing PowerShell Core or using native shell scripting.
  • Ensure screenshots and UI references do not assume Windows-only environments (e.g., avoid references to Outlook calendars unless relevant to all platforms).
GitHub Create Pull Request
Storage Mover How to Manage Azure Storage Mover Endpoints ...cs/blob/main/articles/storage-mover/endpoint-manage.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 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by exclusively providing PowerShell examples for endpoint management, referencing Windows-specific tools and patterns (such as PowerShell modules and execution policies), and omitting equivalent Linux CLI or scripting guidance. The only command-line examples are for PowerShell, with no mention of Azure CLI, Bash, or Linux-native workflows. Windows terminology and tools are introduced first and used throughout, with no Linux parity in automation or scripting sections.
Recommendations
  • Add equivalent Azure CLI examples for all endpoint management tasks, including creation, viewing, editing, and deletion.
  • Include Bash shell scripts or Linux command-line workflows for common operations, especially for users on Linux or macOS.
  • Reference cross-platform tools (e.g., Azure CLI) before or alongside PowerShell, and clarify platform compatibility for each example.
  • Explicitly mention support for Linux environments in agent deployment and endpoint management, and provide troubleshooting tips for non-Windows systems.
  • Review terminology to avoid Windows-centric language (e.g., avoid assuming PowerShell is the default shell for all users).
GitHub Create Pull Request
Storage Mover How to define a migration job ...b/main/articles/storage-mover/job-definition-create.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 page demonstrates a Windows bias by providing detailed PowerShell examples for job definition creation, referencing Windows-centric tools and patterns, and omitting equivalent Linux CLI or scripting examples. The PowerShell section is the only command-line example, and there is no mention of Linux-native tools (such as Bash, Azure CLI, or shell scripting). The structure and order of examples also prioritize Windows approaches, with no guidance for Linux users.
Recommendations
  • Add equivalent Linux command-line examples using Azure CLI (az) and Bash scripting for all operations shown in PowerShell.
  • Explicitly mention platform support and clarify that both Windows and Linux agents/endpoints are supported.
  • Provide guidance for Linux users on prerequisites, such as installing Azure CLI, authenticating, and managing endpoints.
  • Include troubleshooting notes relevant to Linux environments (e.g., file permissions, NFS mount issues).
  • Ensure that documentation images and walkthroughs do not assume a Windows-only environment.
GitHub Create Pull Request
Storage Mover Cloud migration basics for file and folder storage ...s/blob/main/articles/storage-mover/migration-basics.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by mentioning Azure PowerShell before Azure CLI and Bicep as deployment tools, and by referencing NTFS permissions and alternate data streams (Windows-specific features) when discussing file metadata and fidelity. There are no explicit Linux or cross-platform examples, and Windows-centric terminology is used without equivalent Linux details.
Recommendations
  • Provide Linux-specific examples and terminology, such as referencing POSIX permissions and extended attributes alongside NTFS permissions and alternate data streams.
  • List Azure CLI before or alongside Azure PowerShell when suggesting deployment tools, as CLI is cross-platform.
  • Include migration scenarios and considerations for NFS shares and Linux filesystems, not just SMB/NTFS.
  • Add explicit examples or guidance for Linux environments, such as using Bash scripts or Linux-native tools for migration preparation.
  • Clarify that Azure Storage Mover supports both Windows and Linux sources, and provide parity in documentation for both platforms.
GitHub Create Pull Request
Storage Mover How to manage Azure Mover projects ...ocs/blob/main/articles/storage-mover/project-manage.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 Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates a strong Windows bias by providing only Azure PowerShell examples for command-line management, with no mention of Linux-native tools, Bash, Azure CLI, or cross-platform scripting. The setup instructions and code samples focus exclusively on PowerShell, which is traditionally a Windows tool, and installation steps assume a Windows environment. There are no Linux or macOS-specific instructions, nor are alternative command-line interfaces (such as Azure CLI) referenced. The PowerShell examples are presented before any mention of Linux alternatives, which are absent.
Recommendations
  • Add equivalent Azure CLI examples for all PowerShell commands, ensuring parity for Linux and macOS users.
  • Include Bash shell instructions and code samples where appropriate.
  • Explicitly mention that PowerShell Core is cross-platform, but also provide guidance for users who prefer native Linux tools.
  • Add installation instructions for Azure CLI and PowerShell Core on Linux and macOS.
  • Where possible, use generic, platform-agnostic language and avoid assuming a Windows environment.
  • Consider adding troubleshooting notes or tips for Linux/macOS users, such as permission issues or environment setup.
GitHub Create Pull Request
Storage Mover Azure Storage Mover service prerequisites ...b/main/articles/storage-mover/service-prerequisites.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by referencing Windows-centric virtualization platforms (Hyper-V, VMware) first and exclusively, omitting mention of Linux-based hypervisors (e.g., KVM, VirtualBox). There are no examples or instructions for Linux environments, such as deploying the agent on a Linux VM or using Linux tools for agent management. The agent deployment and registration sections assume familiarity with Windows/VMware workflows and do not provide Linux-specific guidance or parity.
Recommendations
  • Include instructions and examples for deploying the agent VM on Linux-based hypervisors (e.g., KVM, VirtualBox, Proxmox).
  • Provide Linux-specific agent registration steps, including shell commands and environment setup.
  • Mention Linux as a supported platform for agent deployment, and clarify any OS-specific requirements or limitations.
  • Add parity in tooling references (e.g., if PowerShell is mentioned, also mention Bash/CLI equivalents).
  • Ensure that prerequisites and troubleshooting steps cover both Windows and Linux environments.
GitHub Create Pull Request
Storage Mover Understanding the Azure Storage Mover resource hierarchy ...blob/main/articles/storage-mover/resource-hierarchy.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page shows evidence of Windows bias. It references Azure PowerShell and the Azure portal as management interfaces before mentioning Azure CLI, which is more cross-platform. There are no examples or mentions of Linux-specific deployment or management patterns, nor are Linux tools or commands referenced. The agent is described as a 'virtual machine' but there is no indication of support for Linux-based agents or instructions for Linux users. The documentation lacks parity in examples and guidance for Linux environments.
Recommendations
  • Explicitly mention and provide examples for Linux-based agent deployment and management.
  • Include Azure CLI commands before or alongside Azure PowerShell examples, emphasizing cross-platform compatibility.
  • Reference Linux tools and patterns where appropriate, such as shell scripting or Linux VM setup.
  • Clarify whether the migration agent can run on Linux VMs and provide instructions for both Windows and Linux environments.
  • Ensure that all management interfaces (portal, PowerShell, CLI) are presented in a neutral, cross-platform order.
GitHub Create Pull Request
Storage Mover Troubleshooting Azure Storage Mover job run error codes ...e-docs/blob/main/articles/storage-mover/status-code.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a Windows bias in several ways: PowerShell cmdlets are mentioned as a primary method for RBAC assignments, with no mention of Linux CLI or Bash alternatives. Troubleshooting steps reference Windows-specific concepts (e.g., SMB, 'con' as an invalid directory name) and do not provide parity for Linux environments (e.g., NFS, Linux file naming conventions). The documentation lacks explicit Linux command examples or troubleshooting steps tailored for Linux agents, and Windows tools/patterns are referenced before or instead of Linux equivalents.
Recommendations
  • Include Azure CLI and Bash command examples for role assignments and troubleshooting, alongside or before PowerShell.
  • Add troubleshooting steps for Linux-specific scenarios, such as NFS mounts, Linux file permissions, and SELinux/AppArmor issues.
  • Reference Linux file naming conventions and errors (e.g., reserved names, case sensitivity) in addition to Windows-specific ones.
  • Mention Linux tools (e.g., mount, ls, chmod, systemctl) for diagnosing agent and network issues.
  • Ensure all examples and guidance are provided for both Windows and Linux environments, or explicitly state platform limitations.
GitHub Create Pull Request
Storage Mover How to create a storage mover resource ...ob/main/articles/storage-mover/storage-mover-create.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 🔧 Windows Tools
Summary
The documentation provides detailed instructions and examples for both Azure CLI and Azure PowerShell, but the PowerShell section is more extensive, including environment setup, execution policy, and module installation steps. PowerShell is a Windows-centric tool, and its prominence may indicate a Windows bias. Additionally, variable assignment in the Azure CLI example uses PowerShell syntax ($variable), which is not standard for Bash or Linux shells, further suggesting a Windows-first approach. There are no explicit Linux shell (bash) examples or instructions, and the CLI section does not clarify Linux-specific setup or usage.
Recommendations
  • Add explicit Bash/Linux shell examples for Azure CLI usage, using standard bash variable syntax (e.g., storageMoverName="..."), and clarify that Azure CLI works cross-platform.
  • Ensure variable assignment and scripting in CLI examples use syntax compatible with Linux/macOS shells.
  • Balance the detail level between PowerShell and CLI sections, providing equivalent environment setup instructions for Linux (e.g., installing Azure CLI on Ubuntu).
  • Mention that Azure PowerShell is available cross-platform, but highlight CLI as the preferred tool for Linux users.
  • Consider adding a table or note comparing usage on Windows vs. Linux/macOS, including any platform-specific considerations.
GitHub Create Pull Request
Storage Mover How to deploy an Azure Storage Mover agent. ...-docs/blob/main/articles/storage-mover/agent-deploy.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 a Windows bias by exclusively providing detailed instructions and screenshots for deploying the agent VM using Microsoft Hyper-V, a Windows-based virtualization platform. Windows Server documentation is referenced for networking setup, and the only supported environments listed are Windows Hyper-V and VMware, with no mention of Linux-based hypervisors (such as KVM, QEMU, or VirtualBox). There are no Linux CLI or tool examples, and PowerShell is featured as the only scriptable example for agent decommissioning, with no Bash or Linux-native alternatives.
Recommendations
  • Add explicit support or at least guidance for deploying the agent VM on popular Linux-based hypervisors (e.g., KVM, QEMU, VirtualBox).
  • Provide Linux-specific instructions and screenshots for VM creation, networking, and resource allocation.
  • Include Bash or Azure CLI examples for agent management tasks, such as decommissioning, alongside PowerShell.
  • Reference Linux documentation for virtual networking setup, in addition to Windows Server and VMware resources.
  • Clarify agent compatibility with Linux hosts and, if unsupported, document roadmap or alternatives for Linux users.
GitHub Create Pull Request
Storage Mover Get started with cloud-to-cloud migration in Azure Storage Mover ...ain/articles/storage-mover/cloud-to-cloud-migration.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 🔧 Windows Tools
Summary
The documentation consistently presents Azure PowerShell examples before Azure CLI examples in each technical section, reflecting a 'Windows-first' approach. PowerShell is a Windows-centric tool, and its prominence throughout the page (with detailed examples and parameter breakdowns) demonstrates a bias toward Windows users. While Azure CLI examples are provided, there are no Linux-specific shell or scripting examples (e.g., Bash scripts beyond CLI usage), nor is there any mention of Linux-native tools or patterns. The portal instructions are platform-neutral, but the command-line guidance leans toward Windows/PowerShell paradigms.
Recommendations
  • Present Azure CLI examples before PowerShell examples in each section to better support Linux and cross-platform users.
  • Explicitly mention that Azure CLI is cross-platform and suitable for Linux, macOS, and Windows.
  • Add Bash scripting examples for common tasks (e.g., looping over endpoints, automating validation) to demonstrate Linux-native workflows.
  • Include troubleshooting tips relevant to Linux environments (e.g., shell environment variables, file permissions).
  • Where PowerShell is used, clarify how Linux users can achieve the same results (e.g., using Azure CLI or Bash).
  • Consider adding a section on using the REST API directly, which is platform-agnostic.
GitHub Create Pull Request
Storage Mover How to schedule bandwidth limitations of a Storage Mover agent ...ob/main/articles/storage-mover/bandwidth-management.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 demonstrates a Windows bias by exclusively providing PowerShell examples for managing bandwidth schedules, referencing Windows-centric tools (PowerShell 7, execution policy), and omitting equivalent Linux command-line instructions or examples. There is no mention of how to perform these tasks using Bash, Azure CLI, or other Linux-native tools, nor any guidance for Linux users on agent console access or scripting.
Recommendations
  • Add Azure CLI examples for all PowerShell commands, showing how to manage bandwidth schedules from Linux/macOS environments.
  • Include Bash script snippets for manipulating the JSON schedule, especially for agent management tasks.
  • Clarify whether the agent console is accessible via SSH on Linux and provide Linux-specific instructions for timezone changes and other configuration steps.
  • Explicitly mention cross-platform support and provide links or references to Linux/macOS documentation where available.
  • Ensure screenshots and UI references do not assume a Windows environment (e.g., avoid Outlook calendar analogies unless also referencing Linux alternatives).
GitHub Create Pull Request
Storage Mover Cloud migration basics for file and folder storage ...s/blob/main/articles/storage-mover/migration-basics.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a mild Windows bias. While it discusses general migration concepts and Azure Storage Mover features, it references Windows-centric tools (Azure PowerShell) before Linux-friendly alternatives (Azure CLI, Bicep). There are no explicit Linux or Unix examples, and file system concepts such as NTFS permissions and alternate data streams are described without mention of Linux equivalents (e.g., POSIX ACLs, extended attributes). The documentation does not provide Linux-specific migration patterns or examples, nor does it mention Linux tools or commands for preparing or migrating shares.
Recommendations
  • Add explicit Linux/Unix examples for migration steps, such as using Azure CLI or shell scripts.
  • Mention Linux file system concepts (e.g., POSIX permissions, extended attributes) alongside NTFS and alternate data streams.
  • Provide guidance for NFS shares and Linux-based source environments, including common migration patterns and tools.
  • Ensure that references to deployment tools (Azure PowerShell, Azure CLI, Bicep) do not prioritize Windows tools; list CLI and Bicep first or equally.
  • Include troubleshooting or configuration notes for Linux environments, such as SELinux, systemd, or common Linux networking considerations.
GitHub Create Pull Request
Storage Mover How to manage Azure Mover projects ...ocs/blob/main/articles/storage-mover/project-manage.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 page demonstrates a strong Windows bias by exclusively providing command-line examples using PowerShell and referencing Windows-centric tools and patterns. There are no CLI or scripting examples for Linux/macOS users (e.g., Bash, Azure CLI), and the installation instructions and troubleshooting steps focus on PowerShell modules and execution policies, which are specific to Windows environments. The documentation does not mention or prioritize Linux or cross-platform alternatives, making it less accessible to non-Windows users.
Recommendations
  • Add equivalent examples using Azure CLI (az) commands, which are cross-platform and widely used on Linux/macOS.
  • Include Bash shell scripting examples for common tasks, such as project creation, viewing, editing, and deletion.
  • Clarify that PowerShell Core (pwsh) is available on Linux/macOS, and provide installation instructions for those platforms.
  • Mention and demonstrate usage of REST API or ARM templates for users who prefer platform-agnostic automation.
  • Reorder examples so that cross-platform solutions (Azure CLI, REST API) are presented before or alongside PowerShell examples.
  • Explicitly state platform compatibility for each tool and example, helping users understand which instructions apply to their environment.
GitHub Create Pull Request
Storage Mover Azure Storage Mover service prerequisites ...b/main/articles/storage-mover/service-prerequisites.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates Windows bias by referencing Windows-centric virtualization platforms (Hyper-V, VMware) first and exclusively, omitting mention of Linux-based hypervisors (such as KVM or VirtualBox). The agent deployment instructions do not provide Linux-specific guidance or examples, and there are no references to Linux tools or patterns for agent management. The documentation also lacks parity in examples for Linux environments, such as shell commands or Linux VM setup steps.
Recommendations
  • Include Linux-based hypervisors (e.g., KVM, VirtualBox, Proxmox) in the agent deployment instructions alongside Hyper-V and VMware.
  • Provide Linux-specific examples for agent VM creation, registration, and management (e.g., using shell commands, cloud-init, or Linux CLI tools).
  • Add explicit instructions or references for extracting and deploying the agent image on Linux hosts.
  • Ensure networking and firewall configuration examples include Linux environments (e.g., iptables, firewalld).
  • Balance references to Windows and Linux tools throughout the documentation to improve cross-platform parity.
GitHub Create Pull Request
Storage Mover How to Manage Azure Storage Mover Endpoints ...cs/blob/main/articles/storage-mover/endpoint-manage.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 page demonstrates a bias towards Windows environments by exclusively providing PowerShell examples for command-line operations, referencing Windows-specific tools and patterns (e.g., PowerShell, Azure PowerShell modules, execution policy), and omitting equivalent Linux/Unix shell (e.g., Bash, CLI) examples. Windows terminology and tools are mentioned first or exclusively, with no guidance for Linux users on how to perform the same tasks using Bash, Azure CLI, or other cross-platform tools.
Recommendations
  • Add equivalent Azure CLI (az) examples for all PowerShell cmdlets, showing how to create, view, edit, and delete endpoints using Bash or other shells.
  • Include installation instructions for Azure CLI on Linux and macOS, alongside PowerShell instructions.
  • Explicitly mention cross-platform compatibility and provide guidance for Linux/Unix users where Windows-specific concepts (e.g., execution policy) are referenced.
  • Ensure screenshots and UI instructions do not assume a Windows environment (e.g., avoid references to Windows-only features or terminology).
  • Where file system concepts differ (e.g., NTFS vs. POSIX), clarify the Linux/Unix equivalents and migration implications.
GitHub Create Pull Request
Storage Mover How to define a migration job ...b/main/articles/storage-mover/job-definition-create.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 page provides detailed instructions for defining and starting a migration job using the Azure portal and PowerShell. The only CLI example given is for PowerShell, which is a Windows-centric tool. There are no examples for Linux-native tools (such as Bash, Azure CLI, or REST API), nor are Linux workflows or commands mentioned. The documentation assumes the use of PowerShell for automation, and does not provide parity for Linux users who may prefer Bash or Azure CLI. Additionally, the order of presentation puts PowerShell before any mention of Linux alternatives, reinforcing a Windows-first approach.
Recommendations
  • Add equivalent examples using Azure CLI (az) commands for all steps shown in PowerShell.
  • Provide Bash script examples for Linux users, including environment variable setup and endpoint creation.
  • Include REST API sample calls for job definition creation, source/target endpoint setup, and job start.
  • Explicitly mention Linux support and workflows in the prerequisites and throughout the guide.
  • Reorder sections or provide tabs for both Windows (PowerShell) and Linux (CLI/Bash) approaches, ensuring equal visibility.
  • Reference Linux-specific troubleshooting or considerations where relevant.
GitHub Create Pull Request
Storage Mover Troubleshooting Azure Storage Mover job run error codes ...e-docs/blob/main/articles/storage-mover/status-code.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First Missing Linux Example
Summary
The documentation demonstrates a Windows bias in several ways: it references PowerShell cmdlets and APIs for RBAC assignments without mentioning CLI or Linux-native alternatives, uses Windows-specific terminology (e.g., SMB, 'con' as an invalid directory name), and omits Linux-specific troubleshooting steps or examples. The troubleshooting steps and examples are written in a way that assumes familiarity with Windows environments and tools, with no parity for Linux or cross-platform scenarios.
Recommendations
  • Include Azure CLI and REST API examples for RBAC assignments alongside PowerShell, and clarify which commands work on Linux/macOS.
  • Add troubleshooting steps and examples for Linux environments, such as mounting SMB shares using Linux commands (e.g., mount.cifs), checking permissions with chmod/chown, and verifying network connectivity with Linux tools (e.g., curl, ping, netcat).
  • Explicitly mention Linux-specific error messages and their remediation (e.g., 'permission denied', 'input/output error') and how to resolve them using Linux commands.
  • Provide parity in documentation by listing both Windows and Linux methods for common tasks, such as role assignment, network troubleshooting, and file system operations.
  • Avoid Windows-centric terminology (e.g., referencing 'con' as an invalid directory name) without noting Linux equivalents or differences.
GitHub Create Pull Request
Storage Mover How to create a storage mover resource ...ob/main/articles/storage-mover/storage-mover-create.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation provides examples for Azure CLI and Azure PowerShell, with the PowerShell section being notably detailed and including Windows-specific setup steps (e.g., execution policy, PowerShell version). The CLI example uses variable syntax ($var) that is PowerShell-specific and not valid in bash, which is the default shell on Linux/macOS. There are no explicit Linux/macOS shell examples, nor is there mention of Linux-specific considerations or parity in the setup instructions.
Recommendations
  • Provide explicit bash shell examples for Azure CLI, using Linux/macOS-compatible variable syntax (e.g., storageMoverName="..." instead of $storageMoverName).
  • Clarify that Azure CLI works cross-platform and show both Windows (cmd/PowerShell) and Linux/macOS (bash/zsh) example blocks.
  • Add notes or sections for Linux/macOS users regarding environment setup, such as installing Azure CLI via package managers (apt, yum, brew) and any OS-specific prerequisites.
  • Avoid using PowerShell variable syntax in CLI examples unless explicitly targeting PowerShell; use generic syntax for broader compatibility.
  • Ensure that instructions for installing modules/tools are not Windows-centric and mention Linux/macOS equivalents where relevant.
GitHub Create Pull Request
Storage Mover https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage-mover/agent-deploy.md ...-docs/blob/main/articles/storage-mover/agent-deploy.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits a clear Windows bias. It exclusively provides step-by-step instructions and screenshots for deploying the agent VM using Microsoft Hyper-V, a Windows virtualization technology. VMware is mentioned only as an alternative, with no detailed steps or examples. There is no mention of Linux-based virtualization platforms (such as KVM, VirtualBox, or Proxmox), nor are there any Linux-specific deployment instructions or examples. The network configuration guidance references Windows Server documentation, and PowerShell is the only command-line example given for agent decommissioning, with no equivalent Bash or Linux CLI example.
Recommendations
  • Add explicit support statements for Linux-based virtualization platforms (e.g., KVM, VirtualBox, Proxmox) if possible, or clarify their status.
  • Provide detailed, step-by-step instructions for deploying the agent VM on VMware, including screenshots and CLI examples.
  • If the agent image is Linux-based, include instructions for creating and managing the VM on Linux hosts using common tools (e.g., virt-manager, virsh, qemu).
  • Include Linux CLI examples (e.g., using Azure CLI in Bash) for agent registration, decommissioning, and other management tasks.
  • Reference Linux documentation for network configuration and troubleshooting, not just Windows Server resources.
  • Ensure parity in troubleshooting and administrative shell access instructions for both Windows and Linux environments.
GitHub Create Pull Request
Storage Mover https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage-mover/migration-basics.md ...s/blob/main/articles/storage-mover/migration-basics.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in several ways. Windows tools and patterns (such as Azure PowerShell) are mentioned before Linux equivalents (Azure CLI), and there is a lack of explicit Linux-specific examples or instructions. File system terminology and migration fidelity examples focus on NTFS permissions and alternate data streams, which are Windows-centric, without mentioning Linux file permissions or attributes. The deployment phase lists Azure PowerShell before Azure CLI, and does not provide parity in Linux command-line examples or guidance.
Recommendations
  • Provide Linux-specific examples and instructions alongside Windows ones, such as using Azure CLI commands for resource deployment.
  • Mention Linux file system concepts (e.g., POSIX permissions, extended attributes) when discussing file fidelity, not just NTFS and alternate data streams.
  • Ensure that references to tools (e.g., PowerShell, CLI) are presented in a neutral order or grouped together, rather than listing Windows tools first.
  • Include guidance for Linux environments in agent deployment and migration steps, such as shell commands or configuration notes.
  • Add explicit examples or links for Linux users where only Windows-centric instructions are given.
GitHub Create Pull Request
Storage Mover https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage-mover/project-manage.md ...ocs/blob/main/articles/storage-mover/project-manage.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 examples for managing Azure Storage Mover projects using the Azure portal and PowerShell, but omits any guidance or examples for Linux users, such as Bash, Azure CLI, or cross-platform scripting. The PowerShell instructions assume a Windows-centric environment, mentioning execution policy and module installation steps that are specific to Windows/PowerShell. No Linux or macOS equivalents or alternatives are discussed.
Recommendations
  • Add Azure CLI examples for all operations (create, view/edit, delete projects) alongside PowerShell examples.
  • Include Bash shell instructions for variable handling and scripting where appropriate.
  • Clarify that PowerShell Core (pwsh) is available cross-platform, and provide installation steps for Linux/macOS users.
  • Mention platform-agnostic tools and patterns first, or at least in parallel with Windows-specific instructions.
  • Review and update any references to execution policy or module installation to note differences or requirements on Linux/macOS.
GitHub Create Pull Request
Storage Mover https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage-mover/bandwidth-management.md ...ob/main/articles/storage-mover/bandwidth-management.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates a Windows bias by exclusively providing PowerShell examples and instructions for managing bandwidth schedules for Storage Mover agents. There are no CLI, Bash, or Linux-native examples, nor is there mention of Linux tools or workflows. The only scripting interface described is Azure PowerShell, which is most commonly used on Windows, and the setup instructions reference Windows-centric concepts (execution policy, PowerShell 7). The documentation does not address how Linux users can perform equivalent tasks, nor does it mention Azure CLI or REST API alternatives.
Recommendations
  • Add equivalent examples using Azure CLI commands for managing bandwidth schedules, which are cross-platform and commonly used on Linux.
  • Include Bash script snippets or instructions for Linux users, especially for tasks like forming and updating JSON schedules.
  • Explicitly mention REST API endpoints and provide curl or httpie examples for direct schedule management, which would benefit Linux and automation users.
  • Clarify that PowerShell is available on Linux, but also provide installation and usage notes for Linux environments.
  • Reorder sections or add notes to ensure Linux and cross-platform methods are presented alongside or before Windows/PowerShell approaches.
  • Reference Linux-friendly tools and workflows where applicable, such as using jq for JSON manipulation.
GitHub Create Pull Request
Storage Mover https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage-mover/endpoint-manage.md ...cs/blob/main/articles/storage-mover/endpoint-manage.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exhibits a Windows bias by exclusively providing PowerShell examples for all command-line operations, referencing Windows tools and patterns (e.g., execution policy, PowerShell 7), and omitting equivalent Linux or cross-platform CLI instructions. The use of PowerShell is assumed for all programmatic tasks, with no mention of Bash, Azure CLI, or Linux-native workflows. Windows terminology and concepts (such as NTFS, ACLs, and Key Vault integration for SMB) are foregrounded, while Linux/NFS details are secondary and lack practical example parity.
Recommendations
  • Add Azure CLI (az) examples for all endpoint management operations alongside PowerShell, ensuring both Windows and Linux users have clear guidance.
  • Include Bash shell script samples for common tasks, such as creating, viewing, editing, and deleting endpoints.
  • Explicitly document any Linux prerequisites or differences, such as authentication, agent installation, or file system semantics.
  • Where PowerShell-specific instructions are given (e.g., execution policy), provide Linux equivalents or note that these steps are not required on Linux.
  • Reference Linux tools and patterns (e.g., curl, jq, bash scripting) where appropriate, especially for programmatic access.
  • Ensure screenshots and UI instructions are platform-neutral or clarify any platform-specific behaviors.
  • Review terminology to balance Windows-centric concepts (NTFS, ACLs) with Linux/NFS equivalents, and provide links to relevant Linux documentation.
GitHub Create Pull Request
← Previous Page 1 of 4 Next →