Storage Mover

50
Total Pages
40
Linux-Friendly Pages
10
Pages with Bias
20.0%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

19 issues found
Showing 1-19 of 19 flagged pages
Storage Mover https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage-mover/includes/agent-shell-connect.md ...articles/storage-mover/includes/agent-shell-connect.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides an SSH command example using PowerShell syntax, which is specific to Windows. There is no mention of Linux or macOS terminal usage, nor are alternative command examples provided for those platforms. The example assumes familiarity with Windows tools and patterns.
Recommendations
  • Provide SSH command examples using standard Bash syntax (e.g., `ssh admin@<AgentIpAddress>`) for Linux/macOS users.
  • Clarify that the SSH command works across platforms and specify any platform-specific differences.
  • Include notes or examples for Linux/macOS terminal usage alongside the PowerShell example.
GitHub Create Pull Request
Storage Mover How to deploy an Azure Storage Mover agent. ...-docs/blob/main/articles/storage-mover/agent-deploy.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation is notably Windows-centric, with all detailed examples and step-by-step instructions provided for Windows Hyper-V. Windows terminology and tools (Hyper-V Manager, Windows Server documentation) are referenced first and exclusively, while VMware is mentioned only as an alternative with no detailed guidance. There is no mention of Linux-based virtualization platforms (such as KVM, VirtualBox, or Proxmox), nor are there any Linux-specific instructions or examples. The agent image is described as a 'Linux image', but only Windows/VMware deployment methods are covered.
Recommendations
  • Add explicit support statements or guidance for Linux-based virtualization platforms (e.g., KVM, VirtualBox, Proxmox), or clarify their lack of support.
  • Provide step-by-step instructions and screenshots for deploying the agent VM on VMware, not just a reference to external documentation.
  • If possible, expand support to include Linux virtualization environments and document the process for those platforms.
  • Include CLI-based instructions for VM creation that are platform-agnostic or provide parity for Linux users.
  • Reorder sections to avoid always presenting Windows tools and examples first, or provide parallel instructions for all supported platforms.
GitHub Create Pull Request
Storage Mover How to schedule bandwidth limitations of a Storage Mover agent ...ob/main/articles/storage-mover/bandwidth-management.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 page demonstrates a notable Windows bias in its command-line examples and tooling. All CLI instructions for configuring bandwidth schedules are provided exclusively using Azure PowerShell, with no mention of Linux/macOS alternatives such as Azure CLI or REST API usage. The PowerShell setup instructions assume a Windows environment (e.g., execution policy), and there are no examples or guidance for Linux users, even though Azure PowerShell is cross-platform. The portal instructions are platform-neutral, but the scripting/automation section is Windows-centric.
Recommendations
  • Add equivalent examples using Azure CLI, which is natively available on Linux/macOS and widely used for cross-platform automation.
  • Explicitly state that Azure PowerShell is available on Linux/macOS and provide installation instructions for those platforms.
  • Include REST API example calls for advanced users who may prefer direct API interaction.
  • Clarify any platform-specific prerequisites or limitations for agent console access and timezone configuration.
  • Present scripting examples for both PowerShell and Azure CLI, ideally side-by-side, to ensure parity.
GitHub Create Pull Request
Storage Mover How to define a migration job ...b/main/articles/storage-mover/job-definition-create.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 provides detailed PowerShell examples for creating migration jobs, with no equivalent CLI or Linux/macOS shell examples. The scripting section is Windows/Powershell-centric, and no Linux tools or commands are mentioned. This creates friction for Linux/macOS users who may not use PowerShell or prefer Bash/Azure CLI.
Recommendations
  • Add equivalent Azure CLI (az) examples for all PowerShell cmdlets shown.
  • Include Bash shell script examples for Linux/macOS users.
  • Explicitly mention cross-platform support and provide guidance for non-Windows environments.
  • Clarify if PowerShell Core (pwsh) is supported on Linux/macOS, and provide installation instructions if relevant.
GitHub Create Pull Request
Storage Mover How to manage Azure Mover projects ...ocs/blob/main/articles/storage-mover/project-manage.md
Medium Priority View Details →
Scanned: 2026-01-12 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 examples for managing Azure Storage Mover projects, including installation steps for PowerShell modules. There are no CLI (az), Bash, or Linux/macOS-specific instructions or examples. The PowerShell approach is presented as the sole command-line method, implicitly favoring Windows environments and tools. This creates friction for Linux/macOS users who may prefer or require cross-platform solutions.
Recommendations
  • Add equivalent examples using Azure CLI (az) commands, which are cross-platform and work natively on Linux/macOS.
  • Include Bash or shell script snippets for common tasks, or clarify that PowerShell Core (pwsh) can be used on Linux/macOS if CLI is not available.
  • Explicitly mention platform compatibility for PowerShell examples, and provide installation instructions for PowerShell Core on Linux/macOS.
  • Reorder examples so that cross-platform methods (Azure CLI) are presented before or alongside PowerShell.
  • Note any limitations or differences in functionality between PowerShell and CLI, if applicable.
GitHub Create Pull Request
Storage Mover How to create a storage mover resource ...ob/main/articles/storage-mover/storage-mover-create.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides examples for Azure Portal, Azure CLI, and Azure PowerShell. While the CLI section is cross-platform, the PowerShell section is Windows-centric and includes detailed setup instructions, such as execution policy changes and module installation, which are specific to Windows environments. Additionally, PowerShell examples and setup steps are presented in detail, whereas Linux/macOS-specific shell examples (e.g., Bash) are not provided. The CLI variable assignment uses `$` syntax, which is PowerShell-style and not compatible with Bash, potentially confusing Linux/macOS users. There is no explicit mention or example for Linux/macOS shell usage.
Recommendations
  • Add explicit Bash (Linux/macOS) examples for Azure CLI commands, using appropriate variable syntax (e.g., export storageMoverName="..."), and clarify cross-platform compatibility.
  • Include notes or sections highlighting differences in environment setup for Linux/macOS users, such as module installation and authentication.
  • Avoid using PowerShell variable syntax in CLI examples; use syntax that works in Bash and other shells.
  • If PowerShell is mentioned, clarify its availability and usage on Linux/macOS, or provide alternative instructions.
GitHub Create Pull Request
Storage Mover How to Manage Azure Storage Mover Endpoints ...cs/blob/main/articles/storage-mover/endpoint-manage.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 page provides detailed instructions for managing Azure Storage Mover endpoints using the Azure portal and PowerShell. All command-line examples are exclusively in PowerShell, with no mention of Linux/macOS CLI alternatives (such as Azure CLI or Bash). The installation instructions and usage patterns assume a Windows environment (PowerShell 7, execution policy, PSGallery), and there is no guidance for Linux/macOS users on how to perform equivalent tasks. This creates friction for non-Windows users and may hinder their ability to follow the documentation efficiently.
Recommendations
  • Add equivalent Azure CLI examples for all endpoint management tasks, including creation, viewing, editing, and deletion.
  • Provide installation instructions for Azure CLI and PowerShell on Linux/macOS, including any prerequisites or differences.
  • Explicitly state cross-platform support and note any differences in behavior or requirements between Windows, Linux, and macOS.
  • Include Bash script examples where appropriate, or reference official Azure CLI documentation for Linux/macOS users.
  • Clarify whether all functionality is available via Azure CLI or REST API, and provide links or examples if so.
GitHub Create Pull Request
Storage Mover Troubleshooting Azure Storage Mover job run error codes ...e-docs/blob/main/articles/storage-mover/status-code.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits mild Windows bias. References to PowerShell cmdlets and RBAC assignment via APIs, PowerShell, or SDKs are made without mentioning Linux equivalents (CLI, Bash, etc.). Troubleshooting steps and examples prioritize Windows-centric tools and patterns (e.g., SMB, 'con' as an invalid directory name), and do not provide Linux-specific guidance or examples. No explicit Linux troubleshooting commands or patterns are offered, and the documentation does not mention Linux file system or permission troubleshooting, nor does it provide parity for role assignment using Azure CLI or Bash.
Recommendations
  • Include Azure CLI and Bash examples for RBAC role assignment alongside PowerShell.
  • Add troubleshooting steps for Linux environments, such as checking NFS mounts, Linux file permissions, and SELinux/AppArmor issues.
  • Provide Linux-specific error patterns (e.g., invalid filenames, permission errors) and clarify differences from Windows (e.g., reserved names like 'con' are not relevant on Linux).
  • Mention Linux tools (e.g., ls, chmod, chown, mount) and how to use them for diagnosing agent issues.
  • Ensure examples and guidance are presented for both Windows and Linux environments, or clarify when steps are OS-agnostic.
GitHub Create Pull Request
Storage Mover How to Manage Azure Storage Mover Endpoints ...cs/blob/main/articles/storage-mover/endpoint-manage.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 Tools Windows First
Summary
The documentation provides extensive PowerShell examples for managing Azure Storage Mover endpoints, with no mention of Linux/macOS CLI alternatives (such as Azure CLI or Bash). The installation instructions and usage patterns are PowerShell-centric, implicitly assuming a Windows environment. This creates friction for Linux/macOS users who may not have PowerShell installed or prefer native tools. Additionally, PowerShell examples are presented before any discussion of cross-platform options.
Recommendations
  • Add equivalent Azure CLI (az) examples for all endpoint management tasks, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Explicitly state that PowerShell is available on Linux/macOS, and provide installation instructions for those platforms.
  • Include Bash script examples where appropriate, especially for common automation scenarios.
  • Clarify which commands/tools are platform-agnostic and which are Windows-specific.
  • Present cross-platform options (Azure CLI, REST API) before or alongside PowerShell examples, not after.
GitHub Create Pull Request
Storage Mover How to schedule bandwidth limitations of a Storage Mover agent ...ob/main/articles/storage-mover/bandwidth-management.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 extensive PowerShell-based instructions for managing bandwidth schedules, with no mention of Linux/macOS CLI equivalents (such as Azure CLI or REST API). The PowerShell examples and environment setup are presented as the primary or only method for scripting/automation, which may create friction for Linux and macOS users. There is no guidance or examples for non-Windows platforms, nor any indication of cross-platform alternatives.
Recommendations
  • Add equivalent Azure CLI examples for all PowerShell commands, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Explicitly mention REST API options for advanced users, including a sample JSON payload and endpoint reference.
  • Clarify that PowerShell is available on Linux/macOS, but also provide installation/setup instructions for those platforms.
  • Reorder scripting sections to present Azure CLI first or side-by-side with PowerShell, to avoid Windows-first bias.
  • Include a note or table summarizing all supported management interfaces (Portal, PowerShell, Azure CLI, REST API) and their platform compatibility.
GitHub Create Pull Request
Storage Mover How to deploy an Azure Storage Mover agent. ...-docs/blob/main/articles/storage-mover/agent-deploy.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation page demonstrates a notable Windows bias. All VM creation instructions and screenshots are for Windows Hyper-V, with only passing mention of VMware. There is no support or guidance for Linux-based virtualization platforms (e.g., KVM, VirtualBox), and the prerequisites explicitly state only Windows Hyper-V and VMware are supported. Network configuration examples and links are Windows-centric. PowerShell is featured as a primary automation method, with no Bash or Linux CLI equivalents provided.
Recommendations
  • Explicitly state platform limitations at the top, and clarify if Linux-based virtualization (KVM, VirtualBox, etc.) is unsupported or provide guidance if possible.
  • Add parity by including VMware instructions and screenshots, not just referencing external documentation.
  • If possible, expand support to Linux virtualization platforms and provide step-by-step instructions for those environments.
  • Provide CLI examples using Bash/Azure CLI for agent management and decommissioning, not just PowerShell.
  • Include network configuration guidance for Linux hosts (e.g., creating bridges with netplan or NetworkManager).
GitHub Create Pull Request
Storage Mover https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage-mover/includes/agent-shell-connect.md ...articles/storage-mover/includes/agent-shell-connect.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides an SSH example using PowerShell syntax and formatting, which is specific to Windows. There is no mention of Linux or macOS terminal usage, nor are equivalent examples for those platforms provided. This may cause confusion or friction for users on non-Windows systems.
Recommendations
  • Include SSH command examples for Linux/macOS terminals (e.g., bash/zsh).
  • Clarify that the SSH command works across platforms and provide platform-specific syntax if there are differences.
  • Avoid using PowerShell formatting for cross-platform commands unless necessary, or provide alternatives.
GitHub Create Pull Request
Storage Mover How to define a migration job ...b/main/articles/storage-mover/job-definition-create.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 examples for creating migration jobs using the Azure portal and PowerShell, both of which are primarily Windows-centric. There are no CLI, Bash, or Linux-native examples, nor any mention of Linux/macOS-specific tools or workflows. PowerShell is presented as the only scripting option, and Windows patterns (e.g., PowerShell cmdlets) are shown before any Linux alternatives, which are absent.
Recommendations
  • Add equivalent examples using Azure CLI (az) commands, which are cross-platform and commonly used on Linux/macOS.
  • Include Bash script snippets for endpoint and job creation, especially for NFS sources, to demonstrate Linux-native workflows.
  • Explicitly mention that PowerShell Core is available on Linux/macOS, and clarify any platform-specific differences.
  • Provide guidance for Linux users on prerequisites, such as agent VM OS compatibility and any required tools.
  • Ensure that screenshots and UI instructions are not Windows-specific (e.g., avoid showing only Windows-style file paths or UI elements).
GitHub Create Pull Request
Storage Mover How to manage Azure Mover projects ...ocs/blob/main/articles/storage-mover/project-manage.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 examples for managing Azure Storage Mover projects using the Azure portal and PowerShell, with all CLI examples exclusively using PowerShell cmdlets. There are no examples or guidance for Linux/macOS users (e.g., Azure CLI, Bash, or cross-platform scripting). The installation instructions and usage patterns are tailored to PowerShell, which is primarily associated with Windows environments, though PowerShell Core is available cross-platform. The absence of Azure CLI or Bash examples creates friction for Linux/macOS users.
Recommendations
  • Add equivalent Azure CLI examples for all PowerShell cmdlets (e.g., az storagemover project create, update, delete).
  • Include installation and usage instructions for Azure CLI on Linux/macOS.
  • Explicitly mention cross-platform compatibility for PowerShell Core, and clarify any differences in usage on Linux/macOS.
  • Where possible, provide Bash script snippets or generic REST API calls for advanced users.
  • Ensure that examples are presented in a way that does not prioritize Windows tools over Linux/macOS equivalents.
GitHub Create Pull Request
Storage Mover How to create a storage mover resource ...ob/main/articles/storage-mover/storage-mover-create.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides examples for Azure CLI and Azure PowerShell, with PowerShell instructions and prerequisites included in detail. PowerShell is a Windows-centric tool, and its section is presented with extensive setup steps. There is no explicit mention of Linux/macOS-specific shell usage (e.g., Bash), nor are there examples tailored for those platforms. The CLI section uses variable assignment syntax ($var = ...) that is PowerShell-style, not Bash, which may confuse Linux/macOS users. The order of examples places Azure CLI before PowerShell, but the CLI example itself uses Windows/PowerShell conventions.
Recommendations
  • Provide Bash-style variable assignment and command examples in the Azure CLI section for Linux/macOS users.
  • Clarify that Azure CLI is cross-platform and provide explicit instructions for Linux/macOS environments (e.g., installation, login).
  • Add a note or tab for Bash/Zsh usage, showing equivalent commands and variable usage.
  • Ensure that variable assignment and scripting examples in CLI sections use syntax compatible with all platforms, or clearly distinguish between PowerShell and Bash.
  • Consider reordering or balancing the prominence of PowerShell and CLI examples to avoid implicit Windows-first bias.
GitHub Create Pull Request
Storage Mover Get started with azureblobcontainer-to-azureblobcontainer migration in Azure Storage Mover ...ain/articles/storage-mover/azure-to-azure-migration.md
Low 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 provides both Azure PowerShell and Azure CLI examples for all major operations, ensuring command-line parity for Windows and Linux/macOS users. However, PowerShell examples are consistently presented before CLI examples, and the portal UI instructions are platform-neutral but visually resemble Windows environments. There are no Linux-specific shell or scripting examples, nor any mention of Linux/macOS tools or patterns. All command-line examples are limited to Azure CLI and PowerShell, with PowerShell (Windows-centric) always listed first.
Recommendations
  • Alternate the order of PowerShell and CLI examples, or present CLI examples first to avoid implicit Windows prioritization.
  • Explicitly state that Azure CLI commands work on Linux, macOS, and Windows, and provide guidance for installing Azure CLI on non-Windows platforms.
  • Add notes or examples for using Bash scripting and automation for Linux/macOS users where relevant.
  • Include troubleshooting tips or references for Linux/macOS environments, such as shell differences or permission handling.
  • Consider adding a section or callout for Linux/macOS users to clarify any platform-specific nuances.
GitHub Create Pull Request
Storage Mover Cloud migration basics for file and folder storage ...s/blob/main/articles/storage-mover/migration-basics.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation mentions Azure PowerShell before Azure CLI and other deployment methods, and references NTFS permissions and alternate data streams (Windows-centric features) when discussing file metadata. No Linux-specific examples, tools, or patterns are provided, and Linux file system features (such as POSIX ACLs) are not mentioned. However, the overall guidance is mostly platform-neutral and does not prevent Linux/macOS users from completing the migration.
Recommendations
  • Mention Linux/macOS equivalents (e.g., POSIX ACLs, ext4/xfs file attributes) alongside NTFS permissions and alternate data streams.
  • Provide explicit Linux/macOS examples for migration steps, such as using Azure CLI from Bash or referencing NFS shares.
  • List Azure CLI before or alongside Azure PowerShell when suggesting deployment tools.
  • Clarify that Azure Storage Mover supports both SMB (Windows) and NFS (Linux/UNIX) sources, and provide examples for both.
GitHub Create Pull Request
Storage Mover Cloud migration basics for file and folder storage ...s/blob/main/articles/storage-mover/migration-basics.md
Low Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page exhibits mild Windows bias by listing Azure PowerShell before Azure CLI as a deployment tool and referencing NTFS permissions as an example of file permissions. There are no explicit Linux/macOS examples, and Windows terminology (NTFS, PowerShell) is mentioned before or more prominently than Linux equivalents. However, the page does mention NFS and does not exclude Linux users from completing any tasks.
Recommendations
  • List Azure CLI before or alongside Azure PowerShell when mentioning deployment tools.
  • Include Linux/macOS-specific examples or terminology, such as POSIX permissions, in discussions of file metadata and permissions.
  • Explicitly mention that Azure Storage Mover supports both SMB (Windows) and NFS (Linux/UNIX) sources, and provide examples for each.
  • Add references to Linux tools and workflows where appropriate (e.g., shell commands, Linux file systems).
GitHub Create Pull Request
Storage Mover Troubleshooting Azure Storage Mover job run error codes ...e-docs/blob/main/articles/storage-mover/status-code.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 Tools Missing Linux Example
Summary
The documentation demonstrates mild Windows bias: it references Windows-specific concepts (e.g., SMB, 'con' as an invalid directory name), mentions PowerShell cmdlets as a method for RBAC assignment, and omits explicit Linux/macOS command-line examples or troubleshooting steps. The troubleshooting steps and examples are generic but tend to assume familiarity with Windows environments and tools, with no parity for Linux/macOS users in terms of commands or error patterns.
Recommendations
  • Add Linux/macOS-specific troubleshooting steps and examples, such as using CLI tools (az CLI, Bash) for RBAC assignments.
  • Include Linux/macOS equivalents for file system errors and naming conventions (e.g., reserved names, path length limits).
  • Provide explicit instructions for verifying network connectivity and permissions using Linux/macOS tools (e.g., curl, openssl, ls, chmod).
  • Mention Linux/macOS error messages and how they may differ from Windows (e.g., permission denied, bad file descriptor).
  • Avoid referencing PowerShell or Windows tools exclusively; offer cross-platform alternatives in parallel.
GitHub Create Pull Request