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 51-75 of 85 flagged pages
Storage Mover https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage-mover/release-notes.md ...docs/blob/main/articles/storage-mover/release-notes.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, 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.
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-12 23:44
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
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.
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
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/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 How to manage Azure Mover projects ...ocs/blob/main/articles/storage-mover/project-manage.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides management instructions for Azure Storage Mover projects via the Azure portal and Azure PowerShell only. All CLI examples use PowerShell cmdlets, with installation instructions for PowerShell modules. There is no mention of Azure CLI, Bash, or cross-platform command-line alternatives, nor are Linux/macOS-specific instructions or examples provided. This creates friction for users on Linux or macOS who may not use PowerShell as their primary shell.
Recommendations
  • Add equivalent Azure CLI examples for all project management tasks (create, view/edit, delete).
  • Include installation and usage notes for Azure CLI on Linux/macOS.
  • Clarify whether PowerShell is required for these tasks or if Azure CLI is supported.
  • If PowerShell is required, provide explicit guidance for Linux/macOS users on installing and using PowerShell Core.
  • Consider reordering examples to present cross-platform options first, or side-by-side.
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-14 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 instructions for managing Azure Storage Mover endpoints using the Azure portal and Azure PowerShell. All command-line examples are exclusively in PowerShell, with no mention of Azure CLI, Bash, or Linux/macOS shell equivalents. Installation instructions and usage patterns assume PowerShell, which is native to Windows and less common on Linux/macOS. This creates friction for non-Windows users, who must install and adapt PowerShell to follow the examples.
Recommendations
  • Add equivalent Azure CLI examples for all endpoint management tasks, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Explicitly mention that PowerShell is available on Linux/macOS, and provide installation instructions or links for those platforms.
  • Where possible, provide Bash or shell script snippets for common tasks, or reference REST API documentation for advanced users.
  • Clarify in introductory sections that both PowerShell and CLI are supported, and link to relevant cross-platform tooling guides.
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-14 00:00
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 equivalent CLI or Bash examples for Linux/macOS users. The PowerShell module is presented as the primary (and only) automation method, and Windows/PowerShell terminology appears before any mention of cross-platform alternatives. There is no evidence that the Storage Mover agent or its management is Windows-only, so Linux/macOS users may experience friction or confusion.
Recommendations
  • Add Azure CLI examples for all PowerShell commands, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Clarify whether the Storage Mover agent and its management APIs are platform-agnostic, and explicitly mention any OS requirements.
  • If PowerShell is required, note that PowerShell 7+ is available on Linux/macOS and provide installation guidance for those platforms.
  • Include Bash/JSON manipulation examples for direct API calls, if supported.
  • Reorder sections so that cross-platform methods (Azure CLI, REST API) are presented before or alongside PowerShell.
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-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation for deploying an Azure Storage Mover agent is notably Windows-centric. It consistently references Windows Hyper-V first, provides step-by-step instructions and screenshots exclusively for Hyper-V (a Windows technology), and links to Windows Server documentation. VMware is mentioned as an alternative, but no detailed steps or screenshots are provided for it. There is no mention of Linux-based virtualization platforms (such as KVM or VirtualBox), nor any guidance for deploying the agent on Linux hosts. The agent image is described as compatible only with Hyper-V and VMware, and other environments are explicitly marked as unsupported.
Recommendations
  • Clarify in the prerequisites and introduction that only Windows Hyper-V and VMware are supported, and explicitly state that Linux-based virtualization platforms are not currently supported.
  • If future support for Linux virtualization platforms (e.g., KVM, VirtualBox) is planned, add a section outlining their status and any workarounds.
  • Provide parity in instructions for VMware users, including step-by-step guidance and screenshots, not just a reference to external documentation.
  • Consider adding a FAQ or note for Linux users explaining the lack of support and suggesting alternatives or future roadmap if applicable.
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-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides an SSH connection example using PowerShell syntax and does not mention Linux/macOS shell equivalents. The use of PowerShell for the SSH command may confuse Linux/macOS users, as their default shell environments differ.
Recommendations
  • Include SSH command examples using Bash syntax (e.g., for Linux/macOS users: `ssh admin@<AgentIpAddress>`).
  • Clarify that the SSH command works from any OS with an SSH client, not just Windows/PowerShell.
  • Present both Windows (PowerShell) and Linux/macOS (Bash) examples side by side.
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-14 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 defining a migration job, but does not offer equivalent CLI or scripting examples for Linux/macOS users (e.g., Azure CLI, Bash). The PowerShell section is the only programmatic example, and it appears after the Azure Portal instructions, which are platform-neutral but may not suffice for automation or scripting needs on non-Windows systems.
Recommendations
  • Add equivalent Azure CLI examples for all steps shown in PowerShell, including endpoint and job definition creation.
  • Include Bash scripting samples where appropriate, especially for Linux/macOS automation scenarios.
  • Explicitly mention cross-platform options and clarify that PowerShell Core is available on Linux/macOS, if relevant, but do not assume all users will use it.
  • Ensure that any references to tools or commands are balanced with Linux/macOS alternatives.
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-14 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 instructions for Azure Portal, Azure CLI, and Azure PowerShell. The PowerShell section is notably extensive, including environment setup and module installation steps, which are primarily relevant to Windows users. The CLI section uses variable syntax ($var) that is PowerShell-style, not standard Bash, and does not provide explicit Bash/Linux shell examples. There is no mention of Linux/macOS-specific considerations or examples, and the PowerShell instructions are more comprehensive than those for CLI.
Recommendations
  • Provide explicit Bash/Linux shell examples for Azure CLI commands, using standard Bash variable syntax (e.g., storageMoverName="..."), and clarify that Azure CLI works cross-platform.
  • Add a note or section for Linux/macOS users, highlighting any differences in environment setup or command usage.
  • Balance the detail level between PowerShell and CLI sections, ensuring Linux/macOS users have equally comprehensive guidance.
  • Avoid using PowerShell-style variable syntax in CLI examples; use syntax that is native to Bash when presenting CLI commands.
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-13 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 endpoint management, with no equivalent CLI or scripting guidance for Linux/macOS users. PowerShell is presented as the sole programmatic option, and installation instructions assume a Windows-centric environment. There are no Azure CLI, Bash, or cross-platform examples, which creates friction for users on non-Windows platforms.
Recommendations
  • Add equivalent Azure CLI examples for all endpoint management tasks.
  • Include Bash or shell script samples for common operations.
  • Clarify cross-platform support for PowerShell (e.g., PowerShell Core on Linux/macOS), and provide installation instructions for those platforms.
  • Explicitly mention that Azure portal is platform-agnostic and highlight any limitations.
  • Ensure all programmatic steps are covered for Linux/macOS users, not just Windows/PowerShell.
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-13 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 defining a migration job, but does not include equivalent CLI or shell examples for Linux/macOS users. The scripting section is Windows-centric, and there is no mention of Linux-native tools or workflows, which may create friction for non-Windows users.
Recommendations
  • Add Azure CLI examples for all steps shown in PowerShell, including endpoint and job definition creation.
  • Include bash/shell script snippets for Linux/macOS users, especially for tasks like path verification and resource management.
  • Explicitly mention cross-platform support and clarify which steps/tools are available on Linux/macOS.
  • Reorder scripting sections to present CLI or cross-platform options before or alongside PowerShell.
  • Reference Linux-specific troubleshooting or best practices where relevant.
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-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation exhibits a notable Windows bias. All step-by-step instructions and screenshots are for Windows Hyper-V, with explicit references to Windows Server documentation. VMware is mentioned as an alternative, but no detailed steps or screenshots are provided for it. There is no mention of Linux-based virtualization hosts (such as KVM, VirtualBox, or Proxmox), nor are Linux CLI or tool examples given. The prerequisites and supported environments are limited to Windows Hyper-V and VMware, excluding Linux-native options.
Recommendations
  • Add explicit support or guidance for deploying the agent VM on Linux-based virtualization platforms (e.g., KVM, VirtualBox, Proxmox) if technically feasible.
  • Provide step-by-step instructions and screenshots for VMware, not just a reference to external documentation.
  • If Linux hosts are not supported, clarify this limitation early and suggest alternatives or workarounds for Linux users.
  • Include Azure CLI examples alongside PowerShell for agent management tasks.
  • Consider parity in documentation structure: present VMware and (if possible) Linux options with equal detail and prominence as Windows Hyper-V.
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-13 00:00
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 configuring bandwidth schedules, with no mention of Linux/macOS CLI equivalents (such as Azure CLI or REST API usage). PowerShell is primarily a Windows tool, and its examples are given exclusively, creating friction for Linux/macOS users who may not have PowerShell installed or prefer native tools. The portal instructions are platform-neutral, but all scripting and automation guidance is Windows-centric.
Recommendations
  • Add equivalent Azure CLI examples for all PowerShell commands, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Include REST API examples for advanced users who may wish to automate via HTTP requests.
  • Explicitly state PowerShell requirements for Linux/macOS (e.g., installation instructions for PowerShell Core on non-Windows platforms).
  • Reorder scripting sections to present Azure CLI first, or side-by-side with PowerShell, to avoid Windows-first bias.
  • Mention that all portal-based steps are platform-neutral, but scripting options vary by OS.
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-13 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 module installation and usage, but does not mention or provide equivalent examples for Linux/macOS users (e.g., Azure CLI, Bash, or REST API). PowerShell is presented as the only command-line option, and installation instructions assume a Windows-centric environment. This creates friction for Linux/macOS users who may not use PowerShell or prefer native tools.
Recommendations
  • Add Azure CLI examples for all project management tasks (create, view/edit, delete).
  • Include Bash or shell script snippets where appropriate.
  • Clarify that PowerShell Core (pwsh) is cross-platform, but also provide instructions for installing and using it on Linux/macOS.
  • Mention and link to REST API documentation for users who prefer direct API calls.
  • Present CLI and PowerShell examples side-by-side, or alternate which is shown first.
  • Explicitly state platform compatibility for all tools mentioned.
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-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation provides detailed instructions for Azure Portal, Azure CLI, and Azure PowerShell. While Azure CLI is cross-platform, the CLI example uses variable syntax ($var) that is PowerShell-specific, not standard Bash, and does not show a Linux/macOS shell example. The PowerShell section is extensive and assumes Windows usage (e.g., execution policy, module installation), with no mention of Linux/macOS PowerShell or CLI usage. There is no explicit Linux/macOS shell example or guidance for non-Windows users.
Recommendations
  • Provide explicit Bash shell examples for Azure CLI usage on Linux/macOS, using standard Bash variable syntax (e.g., storageMoverName="..."), and clarify that Azure CLI works cross-platform.
  • Add notes or sections for using Azure PowerShell on Linux/macOS, including installation steps and any platform-specific considerations.
  • Reorder examples so that cross-platform tools (Azure CLI) are presented before Windows-centric tools (PowerShell), or clearly indicate platform applicability.
  • Explicitly state that all steps can be performed on Linux/macOS, and link to relevant cross-platform installation guides.
GitHub Create Pull Request
Storage Mover Get started with cloud-to-cloud migration in Azure Storage Mover ...ain/articles/storage-mover/cloud-to-cloud-migration.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides step-by-step instructions for Azure Storage Mover cloud-to-cloud migration, consistently offering Azure portal, PowerShell, and Azure CLI examples for all operations. PowerShell examples are given equal prominence to CLI, and in some sections (such as endpoint creation and RBAC assignment), PowerShell is listed before CLI. This ordering and the inclusion of detailed PowerShell commands reflect a subtle Windows bias, as PowerShell is primarily a Windows-native tool (though available cross-platform). There are no Linux-specific shell or scripting examples, and no mention of Linux tools or patterns outside of Azure CLI. The documentation does not reference Linux environments, nor does it provide guidance for Linux users beyond the CLI.
Recommendations
  • Ensure Azure CLI examples are listed before PowerShell in each tabbed section, as CLI is more universally available across platforms.
  • Explicitly mention that Azure CLI commands work natively on Linux, macOS, and Windows, while PowerShell may require additional installation on non-Windows systems.
  • Add notes or sections for Linux users, such as troubleshooting tips for common Linux environments or shell integration.
  • Where relevant, provide bash script examples for automating multi-step operations, demonstrating Linux-friendly workflows.
  • Clarify prerequisites for PowerShell usage on Linux/macOS (e.g., installation steps, compatibility notes).
  • Consider referencing or linking to Linux-specific documentation or best practices for cloud migrations.
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
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides step-by-step instructions for Azure portal, PowerShell, and Azure CLI. PowerShell examples are given equal prominence to CLI, but PowerShell is a Windows-centric tool and is listed before CLI in all code sections. There are no Linux-specific shell examples (e.g., Bash scripts outside of Azure CLI), and no mention of Linux tools or patterns. The documentation assumes familiarity with PowerShell and presents it as a primary automation method, which may disadvantage Linux users who prefer Bash or other shells.
Recommendations
  • List Azure CLI examples before PowerShell examples to reflect cross-platform parity and reduce Windows-first bias.
  • Explicitly mention that Azure CLI commands work natively on Linux, macOS, and Windows, while PowerShell is primarily Windows-centric (unless using PowerShell Core).
  • Add Bash script examples for common tasks, such as looping over containers or endpoints, to demonstrate Linux-native automation.
  • Include notes or links for Linux users on installing and using Azure CLI, and clarify any platform-specific differences.
  • Consider adding troubleshooting steps or validation commands using Bash or other Linux tools where appropriate.
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-10 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 environments. There is no mention of Linux or macOS terminal usage, nor are there equivalent examples for those platforms. The use of Powershell for a standard SSH command may imply a Windows-first or Windows-only context.
Recommendations
  • Provide SSH command examples using generic shell syntax (e.g., bash) or explicitly show both Windows (Powershell/CMD) and Linux/macOS (bash/zsh) examples.
  • Clarify that the SSH command can be run from any OS with an SSH client, not just Windows.
  • Avoid using syntax or formatting that is specific to one platform unless all major platforms are covered equally.
GitHub Create Pull Request
Storage Mover Planning for an Azure Storage Mover deployment ...lob/main/articles/storage-mover/deployment-planning.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page demonstrates mild Windows bias by listing Azure PowerShell as a primary method for resource provider registration, and mentioning Azure portal (which is most commonly used on Windows) before Azure CLI. The CLI is mentioned, but PowerShell is listed first, and there are no explicit Linux-specific instructions or examples. No Linux tools or shell commands are referenced, and the agent deployment section does not clarify Linux support or provide parity details.
Recommendations
  • List Azure CLI before Azure PowerShell when presenting command-line options, as CLI is cross-platform and more commonly used on Linux.
  • Explicitly mention Linux compatibility for agent deployment, including supported distributions and any required dependencies.
  • Provide example commands for both Windows (PowerShell) and Linux (Bash/CLI) environments where relevant.
  • Clarify whether the Azure portal and agent installation steps have any OS-specific considerations.
  • Add troubleshooting or best-practices sections for Linux environments to ensure parity.
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-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
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 is no mention of Linux or macOS terminal usage, nor are alternative command examples provided for those platforms. The use of PowerShell as the default example suggests a Windows-first approach.
Recommendations
  • Include SSH command examples for Linux/macOS terminals (e.g., bash/zsh).
  • Clarify that the SSH command works across platforms and provide syntax for each major OS.
  • Avoid using PowerShell syntax exclusively; use generic or platform-neutral command examples where possible.
  • Add notes or sections addressing Linux/macOS users to ensure parity and inclusivity.
GitHub Create Pull Request
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 →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides both Azure PowerShell and Azure CLI examples for all major operations, but PowerShell examples are consistently listed before CLI examples. This ordering, along with the detailed PowerShell command usage, reflects a subtle Windows-first bias. There are no Linux-specific tools or shell patterns (e.g., Bash scripting, environment variables) beyond the CLI, and no explicit mention of Linux environments or considerations. The documentation does not provide examples using Linux-native tools, nor does it discuss platform-specific differences or troubleshooting for Linux users.
Recommendations
  • Alternate the order of PowerShell and CLI examples, or present CLI examples first to better support Linux users.
  • Explicitly mention that Azure CLI commands work natively on Linux, macOS, and Windows, and provide guidance for installing and using Azure CLI on Linux.
  • Add notes or sections addressing platform-specific considerations, such as file path formats, shell environments, or troubleshooting steps for Linux users.
  • Where possible, include Bash scripting examples for automation, and reference Linux-native tools or workflows.
  • Clarify that PowerShell Core is cross-platform, but distinguish between Windows PowerShell and PowerShell Core if relevant.
GitHub Create Pull Request
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 →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides step-by-step instructions for Azure Storage Mover cloud-to-cloud migration, with examples for Azure portal, PowerShell, and Azure CLI. However, in each technical section, PowerShell examples are consistently presented before Azure CLI (bash) examples, and PowerShell is referenced as a primary automation tool. This ordering and emphasis may reflect a subtle Windows bias, as PowerShell is most commonly used on Windows systems, while CLI/bash is more typical for Linux and cross-platform environments. No Linux-specific tools, shell scripts, or explicit Linux patterns are mentioned, and no alternative Linux-native approaches are suggested.
Recommendations
  • Alternate the order of PowerShell and CLI examples, or present CLI/bash examples first in some sections to avoid implicit prioritization of Windows tooling.
  • Explicitly mention that Azure CLI is cross-platform and can be used on Linux, macOS, and Windows, while PowerShell is available on Windows and, with PowerShell Core, on Linux/macOS.
  • Add notes or links for Linux users, such as installation instructions for Azure CLI and PowerShell Core on Linux.
  • Where appropriate, provide sample shell scripts or automation patterns using bash for Linux environments.
  • Clarify that all operations shown in PowerShell can also be performed using Azure CLI/bash, and encourage users to choose the tool that best fits their platform.
GitHub Create Pull Request
← Previous Page 3 of 4 Next →