Storage Actions

24
Total Pages
18
Linux-Friendly Pages
6
Pages with Bias
25.0%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues (9)

https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage-actions/storage-tasks/storage-task-quickstart-terraform.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Missing Linux Example Windows Tools
Summary:
The documentation provides only Azure PowerShell examples for verifying results, with no equivalent instructions for Linux-native tools, Azure CLI, or Bash scripting. This creates a bias toward Windows users and PowerShell environments, potentially making it harder for Linux or cross-platform users to follow the verification steps.
Recommendations:
  • Add equivalent verification instructions using Azure CLI (az storage-action-task show ...) and Bash shell commands.
  • Present both PowerShell and CLI/Bash examples side by side using tabs or clear sections.
  • Ensure that all steps that use PowerShell or Windows-specific tools have Linux-friendly alternatives.
  • Review other sections for implicit assumptions about the user's shell or environment, and clarify when instructions are cross-platform.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage-actions/storage-tasks/storage-task-quickstart-dotnet.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Windows First Powershell Heavy Windows Tools Missing Linux Example
Summary:
The documentation demonstrates a Windows bias by prioritizing Windows tools and workflows (Visual Studio, PowerShell), providing explicit instructions and screenshots for Visual Studio (a Windows-centric IDE), and using PowerShell for resource cleanup without offering equivalent Linux/bash alternatives. While the .NET CLI is mentioned and bash is referenced in passing, Linux-specific guidance, troubleshooting, or examples are missing, especially for resource cleanup and IDE/editor usage.
Recommendations:
  • Provide explicit Linux/bash alternatives for all command-line instructions, especially for resource cleanup (e.g., show az CLI or bash commands alongside PowerShell).
  • Include screenshots and instructions for cross-platform editors like Visual Studio Code, not just Visual Studio 2022.
  • When referencing opening the project, include Linux-friendly editors (e.g., code . for VS Code, or instructions for JetBrains Rider).
  • In the prerequisites, clarify that .NET Core/.NET 6+ is cross-platform and provide installation links for Linux and macOS, not just .NET Framework (which is Windows-only).
  • For package management, mention that the dotnet CLI is available on Linux and macOS, and provide troubleshooting steps relevant to those platforms.
  • Where PowerShell is used (e.g., resource cleanup), provide an equivalent az CLI command (e.g., az group delete) and show both side-by-side.
  • Ensure that all instructions, especially those involving file paths, environment variables, or shell commands, are cross-platform or have platform-specific notes.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage-actions/storage-tasks/storage-task-quickstart-arm.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 Windows-first bias by referencing Azure PowerShell before Azure CLI in the deployment methods, and by providing both Azure CLI and PowerShell commands for resource cleanup, but omitting explicit Linux shell (bash) or cross-platform examples. There are no Linux-specific instructions or examples, and the PowerShell method is mentioned alongside CLI without clarifying cross-platform compatibility.
Recommendations:
  • Present Azure CLI (which is cross-platform) examples before PowerShell, or clarify that Azure CLI works on all platforms including Linux and macOS.
  • Add explicit bash/shell examples for Linux users, especially for common tasks like resource group deletion.
  • When referencing deployment methods, include links or notes for Linux/macOS users (e.g., 'See how to deploy with Azure CLI on Linux').
  • Avoid implying PowerShell is the primary or default method; treat CLI and PowerShell equally, or lead with CLI for broader platform coverage.
  • Consider adding a section or callout for Linux/macOS users to ensure parity and inclusivity.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage-actions/storage-tasks/storage-task-conditions-operations-edit.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 examples for the Azure Portal, PowerShell, and Azure CLI. However, the scripting examples are heavily PowerShell-centric, with PowerShell always presented before Azure CLI. There are no explicit Linux/bash shell examples, and the CLI examples use Windows-style variable assignment and quoting, which may not work as expected in Linux shells. There is no mention of Linux-specific tools, shell syntax, or guidance for non-Windows users.
Recommendations:
  • Provide explicit bash/Linux shell examples for Azure CLI, using appropriate variable assignment and quoting (e.g., conditionclause="[[endsWith(Name,'.docx')]]").
  • Add a section or note clarifying differences in CLI usage between Windows (cmd/PowerShell) and Linux/macOS (bash/zsh), especially regarding quoting and environment variable syntax.
  • Present Azure CLI examples before or alongside PowerShell examples to avoid the impression of Windows-first bias.
  • Where possible, include references to Linux-native tools or scripting environments, or at least acknowledge their use.
  • Ensure screenshots and instructions are not exclusively tailored to Windows environments.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage-actions/storage-tasks/storage-task-create.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First
Summary:
The documentation provides detailed instructions and examples for creating a storage task using the Azure Portal, PowerShell, Azure CLI, Bicep, and ARM templates. However, the scripting example order places PowerShell (a Windows-centric tool) before Azure CLI, and the PowerShell section is more verbose and detailed. There are no explicit Linux shell (bash) examples, and the PowerShell module is referenced as the primary scripting interface, which may disadvantage Linux users. There is no mention of Linux-specific tooling or considerations.
Recommendations:
  • Provide bash shell examples using Azure CLI, including command-line usage and environment setup, to ensure Linux users have parity.
  • Consider placing Azure CLI examples before PowerShell, as Azure CLI is cross-platform and more common on Linux/macOS.
  • Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and provide any Linux-specific notes if needed.
  • If PowerShell is referenced, clarify that PowerShell Core is cross-platform, or provide equivalent bash examples where possible.
  • Add a section or note about installing and using the Azure CLI on Linux, including package manager instructions.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage-actions/storage-tasks/storage-task-quickstart-arm.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Windows First Powershell Heavy
Summary:
The documentation presents Azure PowerShell and Azure CLI as deployment options, but the link to 'Deploy templates' points to a PowerShell-specific page first. In the clean-up section, both Azure CLI and Azure PowerShell examples are provided, but PowerShell is given equal prominence, which can be seen as a subtle bias since PowerShell is more associated with Windows environments. No explicit Linux tools or shell examples (e.g., Bash) are provided, and the documentation does not mention Linux environments or workflows.
Recommendations:
  • Ensure that links to deployment methods either go to a neutral landing page or present Azure CLI (cross-platform) before PowerShell.
  • Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and provide Bash examples where appropriate.
  • Add a note or section about running these commands in a Linux shell or in the Azure Cloud Shell (which is cross-platform).
  • Where PowerShell is shown, clarify that it is available on Linux and macOS as well, or provide Bash equivalents if possible.
  • Consider including a table or tabs for common OS environments (Windows, Linux, macOS) to show parity in instructions.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage-actions/storage-tasks/storage-task-assignment-create.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows Tools Windows First
Summary:
The documentation provides detailed PowerShell examples and instructions, which are primarily Windows-centric, before presenting Azure CLI examples. The PowerShell section is more prominent and detailed, and there is no mention of Linux-native tools or shell scripting alternatives. While Azure CLI is cross-platform, the scripting examples (e.g., variable assignment) use Bash syntax, but the overall flow and depth favor PowerShell. There are no explicit Linux-specific instructions or parity notes for Linux users.
Recommendations:
  • Ensure that Azure CLI examples are as detailed and prominent as PowerShell examples, and clarify that Azure CLI is fully supported on Linux, macOS, and Windows.
  • Add explicit Bash and/or shell scripting examples for common Linux environments, especially for variable assignment and command chaining.
  • Where PowerShell is mentioned, note that PowerShell Core is cross-platform and provide installation instructions for Linux/macOS if relevant.
  • Consider adding a 'Linux/macOS' tab or section with native shell examples, or at least a note on how to adapt the steps for Linux users.
  • Review the ordering of sections so that cross-platform tools (Azure CLI, Bicep, ARM templates) are presented before or alongside Windows-specific tools like PowerShell.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage-actions/storage-tasks/storage-task-quickstart-terraform.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 only Azure PowerShell instructions for verifying the results, without offering equivalent examples for Linux-native tools, Bash, or Azure CLI. This creates a bias toward Windows users and PowerShell environments, potentially making it less accessible for users on Linux or macOS.
Recommendations:
  • Add equivalent verification steps using Azure CLI (az commands), which are cross-platform and commonly used on Linux and macOS.
  • Provide Bash shell examples for retrieving Terraform outputs and using them with Azure CLI.
  • If PowerShell is shown, present it alongside Bash/Azure CLI examples, not as the only or primary method.
  • Explicitly mention that the steps work on all platforms, or clarify any platform-specific requirements.
  • Ensure that all referenced tools (such as Get-AzStorageActionTask) have cross-platform alternatives or note their platform limitations.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage-actions/storage-tasks/storage-task-quickstart-dotnet.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Windows First Powershell Heavy Windows Tools Missing Linux Example
Summary:
The documentation demonstrates a Windows bias by prioritizing Windows tools and workflows, such as Visual Studio and PowerShell, and by omitting Linux-specific or cross-platform alternatives in several key areas. Visual Studio is presented as the primary IDE, and PowerShell is used exclusively for resource cleanup, with no Bash or Azure CLI alternatives. While the .NET CLI instructions mention Bash, the overall guidance and screenshots are Windows-centric, and Linux/macOS users are not given equal consideration or examples.
Recommendations:
  • Provide explicit Linux/macOS alternatives for all steps, especially for resource cleanup (e.g., show Azure CLI or Bash commands alongside PowerShell).
  • Include screenshots or instructions for popular cross-platform editors (such as Visual Studio Code) and clarify that the .NET CLI works on all major operating systems.
  • Avoid presenting Windows tools (Visual Studio, PowerShell) before cross-platform options; instead, present them in parallel or clarify platform applicability.
  • Add a section or callouts for Linux/macOS users, including package installation, environment setup, and any OS-specific considerations.
  • Where possible, use Azure CLI commands for resource management, as these are cross-platform, and provide both PowerShell and Bash examples for shell commands.