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 76-85 of 85 flagged pages
Storage Mover
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage-mover/azure-to-azure-migration.md
...ain/articles/storage-mover/azure-to-azure-migration.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides step-by-step instructions for Azure portal, Azure PowerShell, and Azure CLI for all major operations. However, PowerShell examples are consistently presented before CLI examples, and PowerShell is a Windows-centric tool. There is no explicit mention of Linux-specific tools or shell scripting, nor are there any Bash script examples beyond basic CLI usage. The documentation does not reference Linux environments, nor does it discuss cross-platform considerations, which may implicitly favor Windows users due to the prominence and ordering of PowerShell instructions.
Recommendations
- Alternate the order of PowerShell and CLI examples, or present CLI examples first to avoid implicit Windows-first bias.
- Explicitly mention that Azure CLI works natively on Linux, macOS, and Windows, and provide guidance for Linux users where relevant.
- Include sample Bash scripts or automation workflows for Linux users, especially for multi-step operations.
- Add a brief section or note on cross-platform usage, clarifying that all CLI commands are fully supported on Linux and macOS.
- Where PowerShell is used for scripting, offer equivalent Bash or shell script snippets for Linux users.
- Reference Linux-specific troubleshooting tips or environment setup where appropriate.
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 →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides the SSH command exclusively in PowerShell syntax, which is specific to Windows environments. There are no examples or references for running the SSH command from Linux or macOS terminals, nor is there mention of equivalent Linux shell usage. This suggests a Windows-first approach and a bias towards Windows tooling.
Recommendations
- Include SSH command examples in Bash syntax for Linux/macOS users (e.g., `ssh admin@<AgentIpAddress>`).
- Clarify that the SSH command can be run from any standard terminal, not just PowerShell.
- Add a note or section on Linux/macOS usage to ensure parity and inclusivity for non-Windows users.
Storage Mover
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage-mover/cloud-to-cloud-migration.md
...ain/articles/storage-mover/cloud-to-cloud-migration.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation consistently provides Azure PowerShell examples alongside Azure CLI and portal instructions for every major step. PowerShell is a Windows-centric tool, and its inclusion as a primary automation example reflects a Windows bias. In most sections, PowerShell examples are listed before CLI examples, which are more cross-platform and preferred by Linux users. There are no Linux-specific shell script examples, nor is there mention of Linux-native tools or patterns. The documentation does not reference Windows-only tools, but the prioritization and prominence of PowerShell throughout the page indicate a subtle Windows bias.
Recommendations
- List Azure CLI examples before PowerShell examples to prioritize cross-platform usage.
- Explicitly mention that Azure CLI commands work natively on Linux and macOS, and provide installation links for those platforms.
- Add Linux shell script examples for common automation scenarios (e.g., using bash for looping over endpoints or jobs).
- Where PowerShell is referenced, clarify that it is available cross-platform, but highlight CLI as the preferred choice for Linux users.
- Include troubleshooting and validation steps using Linux-native tools (e.g., using 'awscli' and 'azcopy' for validation).
- Add a section or note on running migrations and monitoring from Linux environments, including best practices for Linux users.
Storage Mover
Cloud migration basics for file and folder storage
...s/blob/main/articles/storage-mover/migration-basics.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation mentions Azure PowerShell before Azure CLI and other deployment methods when discussing how to deploy Azure storage resources. This ordering may subtly suggest a Windows-first approach, and the mention of PowerShell as a primary tool can be seen as favoring Windows users, even though Azure CLI and Bicep are also referenced. No explicit Linux/macOS examples or tools are provided, and there are no Linux-specific instructions or parity notes.
Recommendations
- List Azure CLI before or alongside Azure PowerShell when mentioning deployment tools, as CLI is cross-platform and widely used on Linux/macOS.
- Include explicit examples or references for Linux/macOS users, such as shell commands or notes about tool compatibility.
- Add a brief statement clarifying that all deployment methods (Azure CLI, PowerShell, Bicep) are supported on Windows, Linux, and macOS, and provide links to platform-specific installation guides.
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
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation presents the SSH command in a PowerShell code block, which may imply a Windows-centric approach. There are no explicit Linux/macOS examples or mentions, and the use of PowerShell syntax may be unfamiliar to non-Windows users.
Recommendations
- Provide SSH command examples in a generic shell format (e.g., Bash) or clarify that the command works in any terminal.
- Use neutral code block formatting (e.g., 'bash' or no language tag) instead of 'powershell' for cross-platform commands.
- Explicitly mention that the SSH command can be run from Linux/macOS terminals as well as Windows (e.g., using Terminal, iTerm, etc.).
- If there are platform-specific considerations (e.g., SSH client installation), note them for each OS.
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 →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation consistently provides Azure PowerShell examples alongside Azure CLI and portal instructions, with PowerShell examples always presented before CLI examples. This ordering subtly prioritizes Windows tooling and patterns, as PowerShell is most commonly used on Windows. However, Azure CLI examples are present for all major steps, ensuring Linux/macOS users are not blocked. No steps are Windows-only, and no critical functionality is missing for Linux/macOS users.
Recommendations
- Alternate the order of PowerShell and CLI examples, or present CLI examples first to better reflect cross-platform usage.
- Explicitly mention that Azure CLI is fully supported on Linux/macOS and is recommended for those platforms.
- Where possible, add notes about cross-platform compatibility for both CLI and PowerShell.
- Consider adding Bash script snippets for common automation scenarios to further support Linux users.
- Avoid language that implies PowerShell is the default or preferred method unless justified by feature parity.
Storage Mover
Cloud migration basics for file and folder storage
...s/blob/main/articles/storage-mover/migration-basics.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page shows mild Windows bias by mentioning Azure PowerShell before Azure CLI and not providing explicit Linux/macOS examples or guidance. While it references Azure CLI and Bicep (which are cross-platform), the lack of Linux-specific instructions or examples may create friction for non-Windows users. No critical migration steps are Windows-only, but the documentation implicitly prioritizes Windows tools and patterns.
Recommendations
- Provide explicit Linux/macOS examples for key steps, such as deploying Azure resources and running migration agents.
- List cross-platform tools (Azure CLI, Bicep) before Windows-specific tools (Azure PowerShell) when suggesting deployment options.
- Include notes or links for installing and using Azure CLI and Bicep on Linux/macOS.
- Clarify that Azure Storage Mover and its agents can be operated from Linux/macOS environments, if applicable.
- Add troubleshooting or environment-specific guidance for Linux/macOS users where relevant.
Storage Mover
Troubleshooting Azure Storage Mover job run error codes
...e-docs/blob/main/articles/storage-mover/status-code.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates mild Windows bias. While the troubleshooting steps are mostly OS-agnostic, there are notable instances where Windows-centric tools, terminology, and examples are referenced without Linux/macOS equivalents. For example, RBAC assignment guidance references PowerShell and portal workflows, and error explanations use Windows-specific file naming conventions (e.g., 'con' as an invalid directory name). There is no mention of Linux-specific troubleshooting commands, nor are Linux/macOS command-line tools (such as Bash, CLI, or shell commands) provided as alternatives. The documentation also refers to SMB and file shares in a way that assumes familiarity with Windows environments.
Recommendations
- Add Linux/macOS-specific troubleshooting steps and examples, such as using Azure CLI or Bash commands for RBAC assignments.
- Include references to Linux tools (e.g., mount, smbclient) when discussing SMB or file share access errors.
- Provide parity in error code explanations, e.g., mention Linux reserved filenames or path limitations alongside Windows examples.
- Explicitly state that the agent and troubleshooting steps apply to both Windows and Linux environments, and clarify any OS-specific differences.
- Where PowerShell or portal instructions are given, also provide equivalent Azure CLI commands.
Storage Mover
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage-mover/cloud-to-cloud-migration.md
...ain/articles/storage-mover/cloud-to-cloud-migration.md
Low Priority
View Details →
Detected Bias Types
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.
Storage Mover
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage-mover/cloud-to-cloud-migration.md
...ain/articles/storage-mover/cloud-to-cloud-migration.md
Low Priority
View Details →
Detected Bias Types
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.