Storage Mover

21
Total Pages
10
Linux-Friendly Pages
11
Pages with Bias
52.4%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues (17)

https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage-mover/status-code.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Windows First Powershell Heavy Missing Linux Example
Summary:
The documentation page demonstrates a mild Windows bias. It references PowerShell cmdlets and APIs for manual RBAC assignment, but does not mention or provide equivalent instructions for Linux users (such as Azure CLI or Bash). No Linux-specific tools or examples are provided, and the troubleshooting steps assume familiarity with Windows-centric patterns. There are no explicit Linux instructions or parity in command-line tooling.
Recommendations:
  • Include Azure CLI (az) command examples alongside or before PowerShell cmdlets for RBAC assignment and troubleshooting.
  • Explicitly mention that all steps can be performed from Linux, macOS, or Windows, and provide Bash/CLI equivalents where possible.
  • Add troubleshooting guidance for common Linux/NFS scenarios, not just SMB/Windows.
  • Where APIs or SDKs are referenced, clarify that these are cross-platform and provide links or examples for both PowerShell and CLI.
  • Review all troubleshooting steps to ensure they are not Windows-centric and are accessible to users on all platforms.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage-mover/job-definition-create.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Missing Linux Example Windows Tools
Summary:
The documentation provides detailed instructions for defining a migration job using the Azure Portal and PowerShell, with all CLI-based examples using PowerShell cmdlets. There are no examples or references for Linux-native tools, Bash, or Azure CLI, and PowerShell is presented as the only scripting/automation option. This creates a Windows-centric experience, potentially excluding Linux users or those who prefer cross-platform tools.
Recommendations:
  • Add equivalent Azure CLI examples for all PowerShell cmdlets shown, ensuring Linux and macOS users can follow along without needing PowerShell.
  • Explicitly mention that PowerShell examples are cross-platform if true, or clarify any Windows-specific requirements.
  • Include Bash script examples or guidance for Linux environments where appropriate.
  • Reference Linux-native tools or workflows (e.g., az CLI, shell scripting) alongside PowerShell, not just after or as an afterthought.
  • Ensure that any screenshots or UI instructions do not assume a Windows environment (e.g., file paths, UI conventions).
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage-mover/bandwidth-management.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Missing Linux Example Windows Tools Windows First
Summary:
The documentation page demonstrates a significant Windows bias, particularly in the command-line and scripting sections. All automation and scripting examples are provided exclusively using PowerShell, a tool primarily associated with Windows environments (despite its cross-platform support, it is still less common on Linux). There are no CLI, Bash, or Linux-native command examples, nor is there mention of using the Azure CLI or REST API, which are more typical in Linux workflows. The prerequisite and walkthrough sections also reference patterns and tools familiar to Windows users (e.g., Outlook-style calendar, PowerShell, and Windows-centric terminology), with no Linux-first or cross-platform parity.
Recommendations:
  • Provide equivalent examples using Azure CLI (az), which is widely used on Linux and macOS, alongside PowerShell.
  • Include Bash shell scripting examples for schedule management, or at least show how to use curl or other Linux-native tools to interact with the relevant Azure REST APIs.
  • Explicitly mention that PowerShell Core is cross-platform, but clarify installation steps for Linux and macOS users.
  • Balance screenshots and terminology to reference both Windows and Linux environments (e.g., compare Outlook calendar to common Linux calendar tools, or use more neutral language).
  • Add a section or callout for Linux users, outlining any differences or additional steps required.
  • Reference documentation for managing Storage Mover agents from Linux systems, if available.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage-mover/cloud-to-cloud-migration.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Missing Linux Example
Summary:
The documentation is heavily oriented around the Azure Portal graphical interface and AWS Console, with all instructions and screenshots based on web UI workflows. There are no command-line examples provided for any platform (Windows, Linux, or macOS), nor are there references to platform-specific tools such as PowerShell, Windows Command Prompt, Bash, or Linux CLI utilities. As a result, there is no explicit Windows bias in terms of tools, commands, or ordering. However, the absence of any CLI or automation examples (such as Azure CLI, AWS CLI, or scripting) means that Linux users—who often prefer or require command-line workflows—are not served. This constitutes a 'missing_linux_example' bias, as the documentation does not provide parity for users who operate outside of graphical interfaces.
Recommendations:
  • Add step-by-step instructions for performing each major operation (connector creation, endpoint configuration, job creation, monitoring) using Azure CLI and, where applicable, AWS CLI.
  • Provide example scripts or command sequences for Linux/macOS environments, including authentication and resource management.
  • Include notes or sections on how to automate the migration process using shell scripts or cross-platform tools.
  • Ensure that any references to automation or scripting are not limited to PowerShell or Windows tools, but include Bash and other common Linux shells.
  • Where UI-only features exist, explicitly state their limitations and provide workarounds or alternatives for CLI users.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage-mover/project-manage.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Missing Linux Example Windows Tools Windows First
Summary:
The documentation provides management instructions for Azure Storage Mover projects using the Azure Portal and PowerShell exclusively. All command-line examples use PowerShell cmdlets, with no mention of cross-platform CLI tools (such as Azure CLI) or Linux shell equivalents. Installation instructions and prerequisites are PowerShell-specific, and there are no Bash or Linux-native command examples. This creates a bias towards Windows users and environments.
Recommendations:
  • Add equivalent Azure CLI (az) examples for all PowerShell cmdlets, as Azure CLI is cross-platform and widely used on Linux and macOS.
  • Include Bash shell script examples alongside PowerShell, especially for variable assignment and command execution.
  • Explicitly mention that PowerShell Core is available on Linux and macOS, but clarify that Azure CLI is often preferred on those platforms.
  • Reorder sections or provide tabs so that Azure CLI and Bash examples are presented alongside or before PowerShell, ensuring parity.
  • Review installation instructions to include Azure CLI installation steps for Linux/macOS users.
  • Avoid language or tool recommendations that assume a Windows environment unless absolutely necessary.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage-mover/troubleshooting.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Windows First Windows Tools Missing Linux Example
Summary:
The documentation demonstrates a Windows bias by referencing Windows tools and patterns first or exclusively. It mentions that a secure FTP client is installed on most typical Windows instances, and recommends WinRAR (a Windows tool) for extracting Zstandard archives, without mentioning Linux equivalents. There are no explicit Linux command examples or tool recommendations, and the documentation assumes a Windows-centric environment for host operations.
Recommendations:
  • Explicitly mention and provide examples for both Windows and Linux environments when discussing prerequisites and tools (e.g., recommend FileZilla or lftp for Linux as secure FTP clients).
  • Suggest Linux-native tools for extracting Zstandard archives, such as 'tar' with 'zstd' or the 'unzstd' command, alongside WinRAR.
  • Include example commands for retrieving and extracting the support bundle on Linux hosts, not just Windows.
  • Avoid language that assumes the user is on Windows (e.g., 'A secure FTP client is installed on most typical Windows instances') and instead provide parity for both platforms.
  • Where screenshots or command snippets are shown, provide both Windows and Linux variants if the process differs.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage-mover/bandwidth-management.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Missing Linux Example
Summary:
The documentation page demonstrates a Windows bias by providing only PowerShell-based CLI examples for configuring bandwidth schedules, with no mention of Linux-native tools, Bash, or cross-platform CLI alternatives. The PowerShell section is extensive and presented as the sole scripting/automation method, implying a preference for Windows environments. There are no Linux-specific instructions or parity in command-line guidance.
Recommendations:
  • Add equivalent Azure CLI (az) examples for all PowerShell commands, as Azure CLI is cross-platform and works natively on Linux, macOS, and Windows.
  • Explicitly mention that the Storage Mover agent and its management tools are supported on Linux, if applicable, and provide any Linux-specific prerequisites or notes.
  • Include Bash shell script examples for common tasks, or at least show how to use curl or az CLI to manipulate the bandwidth schedule JSON.
  • Clarify whether the agent console (for timezone changes) is accessible and behaves identically on Linux and Windows deployments, and provide OS-specific instructions if there are differences.
  • Review screenshots and UI instructions to ensure they are not overly tailored to a Windows/Outlook paradigm, or provide alternative references familiar to Linux users.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage-mover/endpoint-manage.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Missing Linux Example Windows Tools
Summary:
The documentation provides detailed instructions and code samples exclusively for Azure PowerShell, which is a Windows-centric tool, and does not include equivalent examples for Linux-native tools or CLI (such as Azure CLI or Bash scripts). There is no mention of Linux shell commands or cross-platform scripting options, and the only automation examples are in PowerShell. This creates a bias toward Windows users and may hinder Linux users from following the documentation effectively.
Recommendations:
  • Add equivalent Azure CLI (az) command examples for all PowerShell cmdlets, as Azure CLI is cross-platform and widely used on Linux.
  • Include Bash shell script examples for common tasks, especially for endpoint creation, management, and deletion.
  • Explicitly mention that PowerShell Core (v7+) is cross-platform, but also provide guidance for users who prefer native Linux tools.
  • Where possible, provide REST API examples (using curl or similar tools) for advanced users who may want to automate tasks outside of PowerShell.
  • Balance the order of examples: present Azure CLI or Bash examples before or alongside PowerShell to avoid the impression that Windows tools are the primary or only supported automation method.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage-mover/agent-deploy.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Windows First Windows Tools Missing Linux Example
Summary:
The documentation demonstrates a Windows bias by focusing exclusively on Windows Hyper-V and VMware as supported virtualization platforms, with all step-by-step instructions and screenshots provided only for Hyper-V (a Windows technology). There is no mention of Linux-based virtualization solutions (such as KVM, VirtualBox, or Linux-native Hyper-V management), nor are there any Linux command-line examples or guidance for deploying or managing the agent from a Linux environment. The documentation also references Windows Server documentation and tools before mentioning VMware, and does not provide parity for Linux users.
Recommendations:
  • Explicitly state whether Linux-based virtualization platforms (e.g., KVM, VirtualBox) are supported or not, and if not, provide a roadmap or rationale.
  • If the agent image is compatible with Linux-based hypervisors, add detailed, step-by-step instructions for deploying the agent using KVM/QEMU or VirtualBox on Linux hosts, including relevant command-line examples.
  • Include Linux-specific networking guidance (e.g., how to create a bridge or virtual switch using Linux tools such as nmcli, brctl, or virsh).
  • Provide parity in decommissioning and management instructions, including examples using Azure CLI from a Linux shell.
  • If only Windows and VMware are supported, clarify this early and prominently, and consider providing alternative solutions or workarounds for Linux-only environments.
  • Balance references to Windows Server documentation with links to VMware and, if possible, Linux virtualization documentation.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage-mover/cloud-to-cloud-migration.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Missing Linux Example
Summary:
The documentation page provides a comprehensive, step-by-step guide for configuring Azure Storage Mover's cloud-to-cloud migration feature, but it is entirely oriented around portal-based (GUI) workflows. There are no command-line examples, scripts, or references to platform-specific tools (such as PowerShell or Windows utilities), nor are there any Linux/Unix command-line instructions. As a result, the documentation implicitly assumes users will use the Azure Portal, which may disadvantage Linux users who prefer or require CLI-based automation or scripting.
Recommendations:
  • Add equivalent Azure CLI and/or Azure PowerShell instructions for each portal-based step, ensuring both Windows and Linux users can follow along using their preferred tools.
  • Where authentication or resource management is discussed (e.g., creating connectors, endpoints, or jobs), provide CLI examples using az storage-mover or az arc commands, and note any cross-platform requirements.
  • Include sample scripts or command sequences for common Linux shells (e.g., Bash) to automate migration tasks, alongside any PowerShell examples.
  • Explicitly mention platform compatibility for all tools and commands, and provide links to installation guides for both Windows and Linux environments.
  • If certain features are only available via the portal, clearly state this and, if possible, provide a roadmap or alternatives for CLI/automation users.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage-mover/job-definition-create.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Missing Linux Example
Summary:
The documentation provides detailed step-by-step instructions for creating and managing migration jobs using the Azure Portal and PowerShell, with all CLI-based examples exclusively using PowerShell cmdlets. There are no examples or references for performing these tasks using cross-platform tools such as Azure CLI, Bash, or Linux-native scripting. The PowerShell section assumes the user is familiar with PowerShell and does not mention Linux or macOS usage, nor does it provide equivalent commands for those environments. This creates a Windows-centric bias and may hinder Linux users from following the documentation effectively.
Recommendations:
  • Add equivalent Azure CLI examples for all PowerShell cmdlets shown, ensuring Linux and macOS users can follow along without needing PowerShell.
  • Explicitly mention cross-platform compatibility where possible, and clarify if any features are Windows-only.
  • Include Bash script examples or notes for Linux users, especially for common automation scenarios.
  • Reorder or parallelize the documentation sections so that PowerShell and Azure CLI (or Bash) examples are presented side-by-side, rather than PowerShell-only.
  • Reference any platform-specific prerequisites or differences (e.g., installation of Azure CLI on Linux) to ensure parity.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage-mover/migration-basics.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Missing Linux Example
Summary:
The documentation page demonstrates a Windows bias by referencing Azure PowerShell before Azure CLI when listing deployment tools, and by not providing any explicit Linux or cross-platform examples or guidance. The mention of file permissions focuses on NTFS and ACLs, which are Windows-centric, without equivalent discussion of Linux file permissions or tools. There are no concrete examples or instructions for Linux users, and the documentation implicitly assumes a Windows environment.
Recommendations:
  • When listing deployment tools, mention Azure CLI before or alongside Azure PowerShell to avoid implying PowerShell is the primary or preferred method.
  • Include explicit examples for both Windows (PowerShell) and Linux (Bash/Azure CLI) when demonstrating commands or migration steps.
  • Discuss Linux file permission models (e.g., POSIX permissions) alongside NTFS/ACLs when talking about file metadata and fidelity.
  • Reference Linux-compatible tools and workflows (such as rsync, NFS, or Linux SMB clients) where relevant.
  • Add a section or callout for Linux users, highlighting any platform-specific considerations or steps.
  • Ensure that screenshots, code snippets, and instructions are cross-platform or clearly indicate which OS they apply to.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage-mover/release-notes.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Windows First Windows Tools Missing Linux Example
Summary:
The documentation demonstrates a Windows bias, especially in the initial release notes, where the Storage Mover agent appliance VM is stated as only tested and supported as a Windows Hyper-V VM. There is no mention of Linux-based hypervisors (such as KVM or native Linux VMs) in the early releases, and no Linux-specific instructions or examples are provided. Windows tools and patterns (such as Hyper-V and administrative shell) are referenced without Linux equivalents. Later, VMware ESXi support is mentioned, but Linux-native deployment scenarios and examples remain absent.
Recommendations:
  • Explicitly document support for Linux-based hypervisors (e.g., KVM, native Linux VMs) if available, or clarify roadmap for such support.
  • Provide Linux-specific deployment and management instructions, including shell/CLI commands for agent installation, registration, and log retrieval.
  • Ensure that examples and troubleshooting steps include both Windows and Linux environments, or clearly state platform limitations.
  • Reference Linux-native tools (e.g., bash, systemd, journalctl) alongside Windows tools where applicable.
  • If the agent is cross-platform, add parity in documentation for both Windows and Linux users, including screenshots or shell output where relevant.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage-mover/status-code.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Windows First Powershell Heavy Missing Linux Example
Summary:
The documentation demonstrates a Windows bias by referencing PowerShell cmdlets and APIs for manual RBAC assignment, without mentioning or providing equivalent Linux/CLI examples. The troubleshooting steps and mitigation guidance assume the use of Windows-centric tools and patterns, such as PowerShell, and do not provide parity for Linux users. There are no explicit Linux command-line (e.g., Azure CLI) examples or instructions, and the documentation does not acknowledge Linux environments.
Recommendations:
  • Include Azure CLI examples alongside or before PowerShell cmdlet references for tasks such as RBAC assignment.
  • Explicitly mention that both Windows and Linux environments are supported, and provide troubleshooting steps relevant to both.
  • Where PowerShell is referenced, add equivalent Bash/Azure CLI commands for Linux users.
  • Add notes or sections that address common issues or patterns specific to Linux environments (e.g., file permissions, mounting NFS shares).
  • Ensure that screenshots and UI instructions are not Windows-specific, or provide Linux/CLI alternatives where applicable.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage-mover/troubleshooting.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Windows First Windows Tools Missing Linux Example
Summary:
The documentation page demonstrates a Windows bias by referencing Windows tools and patterns first or exclusively. It mentions that a secure FTP client is installed on most typical Windows instances and recommends WinRAR (a Windows tool) for extracting Zstandard archives, without mentioning Linux equivalents. There are no explicit Linux command examples or tool recommendations, and the instructions assume a Windows-centric environment.
Recommendations:
  • Include Linux tool recommendations for extracting Zstandard archives, such as 'zstd' and 'tar' commands.
  • Mention that most Linux distributions include SFTP/SCP clients by default, and provide example commands for retrieving the bundle on Linux.
  • Avoid recommending only Windows-specific tools (e.g., WinRAR); instead, provide cross-platform alternatives or mention both Windows and Linux options.
  • Add example retrieval and extraction commands for both Windows (e.g., PowerShell) and Linux (e.g., bash).
  • Clarify that the instructions apply to both Windows and Linux hosts, and structure the documentation to present both options equally.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage-mover/storage-mover-create.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Windows Tools
Summary:
The documentation provides detailed, step-by-step instructions for both Azure CLI and Azure PowerShell, but the PowerShell section is more extensive, including environment setup, module installation, and additional context. PowerShell is a Windows-centric tool, and its prominence (with more setup detail and troubleshooting tips) suggests a bias toward Windows users. There is no mention of Linux-specific shell usage (e.g., Bash), and variable assignment in the Azure CLI example uses PowerShell syntax ($var = ...), which is not valid in Bash or most Linux shells. The documentation does not provide Linux shell (Bash) examples or address Linux-specific considerations, despite Azure CLI being cross-platform.
Recommendations:
  • Add explicit Bash/Linux shell examples for Azure CLI usage, including correct variable assignment (e.g., storageMoverName="..." instead of $storageMoverName = "...").
  • Clarify that Azure CLI commands are cross-platform and provide setup instructions for Linux/macOS environments.
  • Balance the detail level between PowerShell and CLI sections, ensuring Linux users receive equivalent guidance (e.g., how to install Azure CLI on Linux, troubleshooting tips, etc.).
  • Avoid using PowerShell variable syntax in CLI examples; use syntax appropriate for the shell being targeted.
  • If PowerShell is included, also provide Bash alternatives for all relevant steps, especially for environment preparation and variable setup.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage-mover/project-manage.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Missing Linux Example Windows Tools Windows First
Summary:
The documentation provides detailed instructions and examples for managing Azure Storage Mover projects using the Azure Portal and PowerShell. All command-line examples are exclusively in PowerShell, with installation steps referencing PowerShell 7 and the Az PowerShell modules. There are no examples or guidance for using Azure CLI, Bash, or other cross-platform tools. This creates a bias toward Windows environments and users familiar with PowerShell, while Linux and macOS users are not provided with equivalent command-line instructions.
Recommendations:
  • Add equivalent Azure CLI (az) examples for all PowerShell command-line operations, including project creation, viewing/editing properties, and deletion.
  • Include installation instructions for Azure CLI on Linux/macOS, alongside PowerShell installation steps.
  • When listing command-line options, present Azure CLI (cross-platform) examples before or alongside PowerShell examples to avoid Windows-first bias.
  • Explicitly mention that all operations can be performed from Linux/macOS using Azure CLI, and provide links to relevant documentation.
  • Consider adding Bash script snippets or notes for Linux users where appropriate.