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 26-50 of 85 flagged pages
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/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/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/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/job-definition-create.md ...b/main/articles/storage-mover/job-definition-create.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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 defining and starting a migration job, but does not include equivalent CLI or scripting examples for Linux environments (such as Bash, Azure CLI, or REST API). The use of PowerShell is presented as the primary programmatic method, and Windows-centric tools and patterns are referenced before any Linux alternatives (which are absent). This creates a bias toward Windows users and may hinder Linux users from easily following the instructions.
Recommendations
  • Add equivalent examples using Azure CLI (az), Bash scripts, and/or REST API calls for defining endpoints and job definitions.
  • Explicitly mention cross-platform support and clarify which steps/tools are available on Linux and macOS.
  • Provide guidance or links for Linux users on installing and using Azure CLI and other relevant tools.
  • Where PowerShell is used, note its availability on Linux and macOS, or suggest alternative approaches for those platforms.
  • Ensure that screenshots and UI instructions are not Windows-specific, or supplement with Linux/macOS alternatives where relevant.
GitHub Create Pull Request
Storage Mover https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage-mover/status-code.md ...e-docs/blob/main/articles/storage-mover/status-code.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation demonstrates a Windows bias in several ways: it references PowerShell cmdlets and APIs before mentioning alternatives, omits Linux-specific troubleshooting steps or examples, and uses terminology and error examples (such as invalid Windows directory names like 'con') that are specific to Windows environments. There is no mention of Linux tools, commands, or patterns for troubleshooting, and the documentation does not provide parity for Linux users in terms of examples or guidance.
Recommendations
  • Include Linux-specific troubleshooting steps and examples (e.g., using shell commands for network and permission checks).
  • Mention Linux equivalents for PowerShell cmdlets and APIs, such as Azure CLI or REST API usage from bash.
  • Add guidance for common Linux errors and patterns (e.g., file permissions, SELinux, systemd service status).
  • Provide examples of mounting SMB shares and checking connectivity on Linux (e.g., using 'mount', 'smbclient', 'curl', etc.).
  • Reference both Windows and Linux naming conventions and error cases, clarifying which apply to each OS.
  • Ensure that RBAC assignment instructions include Azure CLI and portal steps, not just PowerShell.
  • Add troubleshooting steps for agent installation and operation on Linux systems, including log locations and service management.
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-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates mild Windows bias. While it generally discusses migration concepts in a platform-neutral manner, it references Windows-centric tools and patterns (such as NTFS permissions and Azure PowerShell) before mentioning cross-platform or Linux alternatives. Examples and terminology (e.g., NTFS, PowerShell) are Windows-first, and there are no explicit Linux-specific examples or instructions (e.g., using Bash, Linux ACLs, or Linux file systems).
Recommendations
  • Include explicit Linux examples and instructions, such as using Bash or Linux CLI commands for Azure resource deployment.
  • Mention Linux file system permissions (e.g., POSIX ACLs) alongside NTFS permissions when discussing file fidelity.
  • List Azure CLI before or alongside Azure PowerShell when suggesting deployment tools, and clarify that both Windows and Linux users are supported.
  • Add examples or references for migrating from Linux-based file shares (e.g., NFS on Linux servers) and handling Linux-specific metadata.
  • Ensure terminology and examples are balanced between Windows and Linux environments throughout the documentation.
GitHub Create Pull Request
Storage Mover https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage-mover/service-prerequisites.md ...b/main/articles/storage-mover/service-prerequisites.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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 (such as KVM or VirtualBox). There are no examples or instructions for deploying or managing the agent VM on Linux environments. The agent registration process is described generically, but the setup and deployment steps assume familiarity with Windows tools and patterns, with no Linux-specific guidance or parity.
Recommendations
  • Include explicit instructions and examples for deploying the agent VM on Linux-based hypervisors (e.g., KVM, VirtualBox, Proxmox).
  • Add Linux-specific prerequisites, such as required packages, shell commands, and configuration steps for agent deployment and registration.
  • Provide parity in examples for Azure CLI and PowerShell, ensuring both are presented equally and with platform-specific notes where relevant.
  • Reference Linux tools and patterns alongside Windows ones, and avoid assuming Windows as the default environment.
  • Clarify any OS-specific requirements or limitations for the agent VM image (e.g., compatibility with Linux hosts, extraction and mounting procedures).
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-08 00:53
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 command-line examples using PowerShell and the Az PowerShell module, which are primarily Windows-centric tools. There are no examples or guidance for Linux users, such as using Azure CLI, Bash, or cross-platform scripting. The PowerShell examples are detailed and given equal prominence to the Azure Portal, but Linux-native tools and workflows are entirely absent. Additionally, installation instructions and prerequisites focus on PowerShell-specific requirements, further reinforcing the Windows-first approach.
Recommendations
  • Add equivalent Azure CLI examples for all operations (create, view, edit, delete project) to support Linux and macOS users.
  • Include Bash scripting samples where appropriate, demonstrating cross-platform automation.
  • Mention that Azure CLI is available on Windows, Linux, and macOS, and provide installation instructions for non-Windows platforms.
  • Clarify that PowerShell Core (pwsh) is cross-platform, but also provide CLI alternatives for users who prefer native Linux tools.
  • Ensure that any prerequisites or environment setup steps include Linux/macOS instructions, not just PowerShell/Windows-specific guidance.
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-08 00:53
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 Windows bias by exclusively providing PowerShell examples for endpoint management, referencing Windows tools and patterns (e.g., PowerShell, execution policy, resource naming conventions tied to Windows), and omitting equivalent Linux CLI or scripting examples (such as Azure CLI, Bash, or REST API usage). Windows/PowerShell instructions are presented as the only programmatic option, with no mention of Linux-native workflows or tools. Additionally, the narrative and examples often assume a Windows-centric environment, such as referencing NTFS file properties and Windows authentication concepts before Linux/NFS equivalents.
Recommendations
  • Add Azure CLI examples for all endpoint management tasks, including creation, viewing, editing, and deletion, to provide parity for Linux users.
  • Include Bash scripting examples and instructions for using the REST API directly, which are common on Linux systems.
  • Explicitly mention Linux support and workflows in introductory sections, clarifying that all operations can be performed from Linux environments.
  • Reference Linux-native authentication and file system concepts alongside Windows/NTFS, ensuring equal coverage and order.
  • Review and update screenshots and UI references to ensure they do not assume a Windows environment (e.g., avoid showing only Windows-style paths or tools).
  • Where PowerShell is referenced, provide equivalent commands for Bash/Azure CLI, and clarify cross-platform compatibility.
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-08 00:53
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 managing bandwidth schedules using Azure PowerShell, which is primarily associated with Windows environments. There are no equivalent CLI (az cli), Bash, or Linux-native examples, nor is there any mention of Linux tools or workflows for agent management. The only command-line automation guidance is Windows-centric, and PowerShell is presented as the default and only scripting option.
Recommendations
  • Add equivalent examples using Azure CLI (az cli), which is cross-platform and commonly used on Linux.
  • Include Bash script snippets for manipulating the JSON schedule, demonstrating how Linux users can automate agent configuration.
  • Explicitly mention that PowerShell Core is available on Linux and macOS, and provide installation instructions or links.
  • Provide guidance for managing agent schedules via REST API calls, with curl examples for Linux users.
  • Ensure that screenshots and UI instructions do not assume Windows-only environments (e.g., referencing Outlook calendars or Windows-specific UI metaphors).
GitHub Create Pull Request
Storage Mover https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage-mover/storage-mover-create.md ...ob/main/articles/storage-mover/storage-mover-create.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation provides detailed instructions for both Azure CLI and Azure PowerShell, but the PowerShell section is notably more extensive, with additional setup steps and troubleshooting advice. PowerShell is a Windows-centric tool, and its prominence, along with references to execution policy and module installation, suggests a Windows bias. There are no explicit Linux shell (bash) examples, nor is there mention of Linux-specific considerations, even though Azure CLI is cross-platform. The CLI example uses variable syntax ($var) that is PowerShell-style, not bash, which may confuse Linux users.
Recommendations
  • Add explicit bash/Linux shell examples for Azure CLI, using Linux-style variable syntax (e.g., export storageMoverName="..."), and clarify cross-platform usage.
  • Balance the detail level between PowerShell and CLI sections, ensuring Linux users receive equivalent troubleshooting/setup guidance.
  • Mention that Azure CLI works natively on Linux/macOS and provide any OS-specific notes if needed.
  • Avoid using PowerShell variable syntax in CLI examples; use syntax appropriate for the shell.
  • If there are any platform-specific limitations or requirements, call them out clearly for both Windows and Linux users.
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-08 00:53
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 on Microsoft Hyper-V (a Windows technology), referencing Windows Server documentation, and mentioning Windows Hyper-V before VMware. There are no examples or instructions for deploying the agent on Linux-based virtualization platforms (such as KVM, VirtualBox, or Proxmox), nor any guidance for Linux users. The prerequisites and supported environments are limited to Windows Hyper-V and VMware, with no mention of Linux alternatives.
Recommendations
  • Add explicit statements about Linux support status and plans, if any.
  • If technically feasible, provide instructions for deploying the agent VM on popular Linux-based virtualization platforms (e.g., KVM, VirtualBox, Proxmox).
  • Include Linux CLI examples and troubleshooting steps where applicable.
  • Balance references to Windows tools with equivalent Linux tools or documentation.
  • If Linux is not supported, clarify this early in the documentation and suggest workarounds or alternatives for Linux users.
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-06 18:15
Reviewed by: Unknown
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 providing only Azure PowerShell examples for command-line operations, with no mention of Linux-native tools, Bash, or Azure CLI. All automation and scripting instructions use PowerShell cmdlets and installation steps, which are primarily Windows-centric. There are no Linux or cross-platform command-line examples, and PowerShell is presented as the default/only scripting option, despite Azure CLI being widely used on Linux and macOS.
Recommendations
  • Add equivalent Azure CLI examples for all PowerShell cmdlets, showing how to create, view, edit, and delete Storage Mover projects using az commands.
  • Include Bash shell scripting examples where appropriate, especially for variable assignment and command chaining.
  • Explicitly state cross-platform support for Azure CLI and PowerShell, and clarify installation steps for Linux and macOS users.
  • Reorder examples to present Azure CLI (cross-platform) before PowerShell, or provide both side-by-side.
  • Mention that Azure PowerShell is available on Linux/macOS, but highlight Azure CLI as the more native choice for those platforms.
GitHub Create Pull Request
Storage Mover https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage-mover/troubleshooting.md ...cs/blob/main/articles/storage-mover/troubleshooting.md
High Priority View Details →
Scanned: 2026-01-06 18:15
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates Windows bias by referencing Windows tools and patterns first and 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 examples or instructions for Linux users, such as using native Linux tools (e.g., scp, sftp, tar, zstd), nor is there guidance for Linux environments, despite the agent logs referencing Linux-style commands and file structures.
Recommendations
  • Include instructions and examples for Linux users, such as using scp or sftp to retrieve the support bundle.
  • Recommend Linux-native tools for extracting Zstandard archives, such as the 'zstd' and 'tar' command-line utilities.
  • Avoid assuming the host is Windows; provide parity for Linux and macOS hosts.
  • List both Windows and Linux tools side-by-side when discussing prerequisites.
  • Explicitly mention how to perform each step on Linux, including command syntax and package installation if needed.
GitHub Create Pull Request
Storage Mover https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage-mover/status-code.md ...e-docs/blob/main/articles/storage-mover/status-code.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
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.
GitHub Create Pull Request
Storage Mover https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage-mover/troubleshooting.md ...cs/blob/main/articles/storage-mover/troubleshooting.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
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.
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: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
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.
GitHub Create Pull Request
Storage Mover https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage-mover/job-definition-create.md ...b/main/articles/storage-mover/job-definition-create.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
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).
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: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
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.
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: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
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.
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: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
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.
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: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
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.
GitHub Create Pull Request
Storage Mover https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage-mover/storage-mover-create.md ...ob/main/articles/storage-mover/storage-mover-create.md
High Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
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.
GitHub Create Pull Request
Storage Mover https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage-mover/troubleshooting.md ...cs/blob/main/articles/storage-mover/troubleshooting.md
High Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
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.
GitHub Create Pull Request
← Previous Page 2 of 4 Next →