Storage Actions

24
Total Pages
15
Linux-Friendly Pages
9
Pages with Bias
37.5%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

51 issues found
Showing 1-25 of 51 flagged pages
Storage Actions Create and manage a storage task assignment ...ctions/storage-tasks/storage-task-assignment-create.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell examples are given in detail and appear before Azure CLI examples, suggesting a preference for Windows tooling. The use of PowerShell-specific commands and terminology is prominent, and there is no mention of Linux-specific shell usage or considerations. While Azure CLI examples are present (which are cross-platform), the initial focus and depth of PowerShell coverage may disadvantage Linux users. There are no explicit Linux shell examples (e.g., bash scripts), nor are there notes about platform differences or Linux-specific patterns.
Recommendations
  • Provide Linux shell (bash) examples alongside PowerShell, especially for scripting scenarios.
  • Explicitly state that Azure CLI commands work on Linux, macOS, and Windows, and highlight any platform-specific considerations.
  • Reorder examples so that cross-platform tools (Azure CLI, ARM/Bicep templates) appear before platform-specific tools like PowerShell.
  • Include notes or links for Linux users regarding installation and usage of Azure CLI and scripting best practices.
  • Avoid assuming PowerShell as the default scripting environment; offer parity in documentation for bash/zsh users.
GitHub Create Pull Request
Storage Actions Quickstart: Create a storage task using Terraform ...ons/storage-tasks/storage-task-quickstart-terraform.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides verification instructions exclusively using Azure PowerShell, which is primarily a Windows-centric tool. There are no equivalent examples for Linux users, such as using Azure CLI or Bash scripts. This creates a bias toward Windows users and may hinder Linux users from following the verification steps easily.
Recommendations
  • Add verification instructions using Azure CLI, which is cross-platform and widely used on Linux.
  • Include Bash script examples for extracting Terraform outputs and verifying resources.
  • Present both PowerShell and CLI/Bash options side-by-side or in tabs, ensuring equal visibility.
  • Explicitly mention that Azure CLI can be used on Windows, Linux, and macOS, and provide links to relevant documentation.
GitHub Create Pull Request
Storage Actions Quickstart: Create a storage task by using an Azure Resource Manager template (ARM template) ...e-actions/storage-tasks/storage-task-quickstart-arm.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page demonstrates Windows bias by referencing Azure PowerShell before Azure CLI in deployment instructions, linking to a PowerShell-specific deployment guide, and providing PowerShell examples alongside CLI examples. There is no mention of Linux-specific tools or shell environments, and the documentation assumes familiarity with PowerShell and Windows-centric workflows.
Recommendations
  • Ensure Azure CLI instructions are presented before or alongside PowerShell instructions, as CLI is cross-platform.
  • Include explicit references to Linux and macOS environments, such as Bash or shell usage, especially in command examples.
  • Provide links to both PowerShell and CLI deployment guides, and clarify which tools are cross-platform.
  • Add notes or sections highlighting how Linux users can perform the same tasks, including any platform-specific considerations.
  • Avoid assuming PowerShell as the default scripting environment; mention alternatives where appropriate.
GitHub Create Pull Request
Storage Actions Create and run a storage task (.NET) ...ctions/storage-tasks/storage-task-quickstart-dotnet.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exhibits several signs of Windows bias. Visual Studio (a Windows-centric IDE) is presented first and in more detail than cross-platform alternatives. The setup and run instructions frequently reference Windows tools (Visual Studio, PowerShell, cmd) and provide screenshots only for Visual Studio. The clean-up step uses a PowerShell command without offering an equivalent Bash/Azure CLI example for Linux/macOS users. There are no Linux-specific instructions or screenshots, and the documentation assumes familiarity with Windows tooling.
Recommendations
  • Provide equal prominence and detail for cross-platform tools such as Visual Studio Code and JetBrains Rider, including screenshots and step-by-step instructions.
  • Include Linux/macOS-specific instructions for setup, package installation, and running the application (e.g., using Bash, zsh, etc.).
  • For resource clean-up, offer Azure CLI or Bash command examples alongside PowerShell, and clarify which commands work on which platforms.
  • Avoid assuming Visual Studio is the default IDE; mention and demonstrate alternatives that work on all platforms.
  • Add notes or troubleshooting tips relevant to Linux/macOS environments, such as file permissions, path differences, or .NET installation steps.
  • Ensure all code and command-line examples are tested and work on Linux/macOS as well as Windows.
GitHub Create Pull Request
Storage Actions Create and manage a storage task assignment ...ctions/storage-tasks/storage-task-assignment-create.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell examples are provided in detail, and the PowerShell tab appears before the Azure CLI tab, which is more cross-platform. The scripting examples and instructions are PowerShell-centric, and there is no mention of Bash or Linux-specific shell scripting patterns. The portal instructions are platform-neutral, but the command-line automation focus leans toward Windows tools and patterns.
Recommendations
  • Add explicit Bash examples alongside PowerShell, especially for scripting assignment creation and role assignment.
  • Reorder tabs so that Azure CLI (cross-platform) appears before PowerShell, or clarify that CLI is recommended for Linux/macOS users.
  • Include notes or sections on running Azure CLI commands in Bash on Linux/macOS, with sample commands and environment setup tips.
  • Reference Linux-native tools or workflows where appropriate, such as using environment variables, jq for JSON parsing, or cron for scheduling.
  • Ensure screenshots and instructions do not implicitly assume Windows environments (e.g., file paths, shell conventions).
GitHub Create Pull Request
Storage Actions Create and run a storage task (.NET) ...ctions/storage-tasks/storage-task-quickstart-dotnet.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
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 providing examples and screenshots specific to these environments. While the .NET CLI is mentioned and Bash is referenced as a possible shell, the instructions and visuals focus heavily on Windows-centric tools. The cleanup step uses only a PowerShell command, with no Linux or Bash equivalent. There are no explicit instructions or screenshots for Linux users or alternative editors beyond Visual Studio and Visual Studio Code.
Recommendations
  • Add explicit instructions and screenshots for Linux environments, such as using VS Code or JetBrains Rider on Linux.
  • Include Bash or Azure CLI equivalents for resource cleanup, e.g., 'az group delete --name <resource-group>' alongside the PowerShell command.
  • Present cross-platform instructions in parallel, ensuring that Linux and macOS users are equally supported and not relegated to secondary status.
  • Clarify that all .NET CLI commands work on Linux/macOS, and provide troubleshooting tips specific to those platforms.
  • Avoid referencing Windows-specific features (like Visual Studio menus) without offering alternatives for Linux/macOS users.
GitHub Create Pull Request
Storage Actions Quickstart: Create a storage task using Terraform ...ons/storage-tasks/storage-task-quickstart-terraform.md
High Priority View Details →
Scanned: 2026-01-10 00:00
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 bias towards Windows by providing only Azure PowerShell examples for verifying results, without any equivalent Linux or cross-platform CLI (e.g., Azure CLI, Bash) instructions. The use of PowerShell and references to Windows-centric tools are present, while Linux-friendly alternatives are missing. This may hinder Linux users or those using non-Windows environments from following the verification steps easily.
Recommendations
  • Add equivalent verification instructions using Azure CLI (az), which is cross-platform and widely used on Linux and macOS.
  • Provide Bash shell examples for extracting Terraform outputs and passing them to Azure CLI commands.
  • Explicitly mention that the verification steps can be performed on Linux/macOS using CLI tools, not just PowerShell.
  • Ensure that any referenced tools or commands (such as Get-AzStorageActionTask) have cross-platform alternatives documented and linked.
  • Consider reordering or presenting both Windows and Linux examples side-by-side to avoid implicit prioritization of Windows.
GitHub Create Pull Request
Storage Actions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage-actions/storage-tasks/storage-task-quickstart-terraform.md ...ons/storage-tasks/storage-task-quickstart-terraform.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page provides verification steps exclusively using Azure PowerShell, a Windows-centric tool, without offering equivalent instructions for Linux/macOS users (e.g., Azure CLI or REST API). This prioritizes Windows tooling and omits cross-platform alternatives, making it less accessible for non-Windows users.
Recommendations
  • Add verification steps using Azure CLI, which is cross-platform and widely used on Linux/macOS.
  • Present both PowerShell and CLI examples side-by-side, or default to CLI first for broader accessibility.
  • Explicitly mention that the verification can be performed on any platform, and link to relevant CLI or REST API documentation.
  • Ensure all critical steps (especially verification and resource management) have Linux/macOS-friendly instructions.
GitHub Create Pull Request
Storage Actions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage-actions/storage-tasks/storage-task-quickstart-dotnet.md ...ctions/storage-tasks/storage-task-quickstart-dotnet.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 demonstrates a Windows bias by prioritizing Windows tools (Visual Studio, PowerShell), providing explicit instructions and screenshots for Visual Studio (a Windows-centric IDE), and using PowerShell for resource cleanup without offering Linux/bash equivalents. While the .NET CLI instructions are cross-platform, the overall tone and tooling guidance favor Windows environments, and Linux users are left to infer or adapt steps for their platforms.
Recommendations
  • Provide explicit Linux/bash equivalents for all PowerShell commands, especially for resource cleanup (e.g., use Azure CLI az group delete).
  • Include screenshots and step-by-step instructions for cross-platform editors like Visual Studio Code, not just Visual Studio.
  • When listing console options, mention Bash or Terminal before or alongside cmd/PowerShell to avoid Windows-first ordering.
  • Clarify that all .NET CLI commands work on Linux/macOS as well as Windows, and provide any necessary prerequisites for those platforms.
  • Add a section or callout for Linux/macOS users, highlighting any differences or additional steps required.
  • Avoid using Windows-specific terminology or tools (like Solution Explorer) without offering alternatives for other platforms.
GitHub Create Pull Request
Storage Actions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage-actions/storage-tasks/storage-task-quickstart-arm.md ...e-actions/storage-tasks/storage-task-quickstart-arm.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page demonstrates Windows bias by referencing Azure PowerShell before Azure CLI in deployment instructions, linking to a PowerShell-specific deployment guide, and providing both Azure CLI and PowerShell examples for resource cleanup, but not mentioning Linux-specific shell environments or tools. There is no explicit mention of Linux or cross-platform considerations, and PowerShell (traditionally Windows-centric) is given equal or greater prominence than CLI, which is more cross-platform.
Recommendations
  • Ensure Azure CLI examples are presented before or alongside PowerShell examples, as CLI is more universally available across platforms.
  • Include explicit references to Linux/macOS environments, such as mentioning Bash or shell usage, and clarify that Azure CLI works natively on these platforms.
  • Provide links to both PowerShell and CLI deployment guides, or a unified cross-platform guide.
  • Avoid language or links that imply PowerShell is the default or preferred method, unless justified by technical requirements.
  • Add notes or sections highlighting cross-platform compatibility and usage patterns for Linux users.
GitHub Create Pull Request
Storage Actions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage-actions/storage-tasks/storage-task-assignment-create.md ...ctions/storage-tasks/storage-task-assignment-create.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell is given its own dedicated section with detailed, step-by-step instructions and examples, reflecting a Windows-centric approach. The ordering of tabs places PowerShell before Azure CLI, which is more cross-platform and preferred by many Linux users. There is no mention of Bash scripting or Linux-specific shell examples, and the CLI examples use syntax that is compatible with Bash but do not explicitly reference Linux environments or provide guidance for Linux users. The portal instructions are platform-neutral, but the command-line guidance leans toward Windows tools and patterns.
Recommendations
  • Add explicit Bash examples and instructions for Linux users, especially for Azure CLI usage.
  • Reorder the tabs to place Azure CLI before PowerShell, reflecting cross-platform parity.
  • Include notes or sections highlighting Linux compatibility and any platform-specific considerations.
  • Mention that Azure CLI commands can be run on Linux, macOS, and Windows, and provide troubleshooting tips for non-Windows environments.
  • Where PowerShell is referenced, clarify that PowerShell Core is available cross-platform, or provide alternative Bash equivalents.
GitHub Create Pull Request
Storage Actions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage-actions/storage-tasks/storage-task-conditions.md ...orage-actions/storage-tasks/storage-task-conditions.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by mentioning Azure PowerShell before Azure CLI when discussing tools for creating storage tasks, and by referencing PowerShell as an environment for condition preview. There are no explicit Linux or bash examples, nor is there mention of Linux-specific tools or workflows. The examples and screenshots are platform-neutral, but the text prioritizes Windows-centric tools and patterns.
Recommendations
  • Mention Azure CLI before or alongside Azure PowerShell when listing tools for creating storage tasks.
  • Explicitly state that Azure CLI is cross-platform and provide CLI command examples where relevant.
  • Include references to Linux/macOS environments and workflows, such as using bash scripts or SDKs on non-Windows platforms.
  • Add sample commands or usage notes for Linux users to ensure parity with Windows/PowerShell instructions.
  • Avoid language that implies PowerShell is the primary or default environment for these operations.
GitHub Create Pull Request
Storage Actions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage-actions/overview.md ...re-docs/blob/main/articles/storage-actions/overview.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page lists PowerShell before Azure CLI and other cross-platform tools when describing how to create storage task definitions. It also mentions REST, SDKs, Bicep, Terraform, and ARM templates, but PowerShell is the only shell scripting environment called out by name, which may imply a Windows-centric approach. There are no explicit Linux examples or references to Linux-specific tooling or workflows, and no mention of Bash or Linux shell environments.
Recommendations
  • List Azure CLI before PowerShell when enumerating supported automation tools, as Azure CLI is cross-platform.
  • Provide explicit examples for both PowerShell and Azure CLI (and Bash where relevant) in quickstart and how-to guides.
  • Mention Linux and macOS compatibility where applicable, especially in sections discussing automation and scripting.
  • Include references to Bash scripts or Linux shell environments alongside PowerShell to ensure parity.
  • Clarify that all listed tools (CLI, SDKs, REST, etc.) are supported on Linux, Windows, and macOS.
GitHub Create Pull Request
Storage Actions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage-actions/storage-tasks/storage-task-conditions.md ...orage-actions/storage-tasks/storage-task-conditions.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page exhibits a mild Windows bias. It mentions Azure PowerShell as the primary example of a tool for creating storage tasks, with Azure CLI listed as a secondary option. There are no explicit Linux or cross-platform command-line examples, nor references to Linux-native tools or scripting patterns. The preview functionality is described as available in PowerShell, Azure CLI, and SDKs, but the easiest method is stated to be via the Azure portal, which is platform-agnostic. No Linux-specific instructions or examples are provided.
Recommendations
  • Provide explicit examples using Azure CLI commands, especially for condition creation and preview, to demonstrate Linux parity.
  • Mention cross-platform compatibility of Azure CLI and SDKs, and clarify that these tools work on Linux, macOS, and Windows.
  • Include references to Linux shell scripting (e.g., Bash) where relevant, and offer sample scripts for common tasks.
  • Avoid listing Windows tools (e.g., PowerShell) before cross-platform alternatives unless there is a technical reason.
  • Add a section or note highlighting how Linux users can perform all described actions using CLI or SDKs.
GitHub Create Pull Request
Storage Actions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage-actions/storage-tasks/storage-task-quickstart-arm.md ...e-actions/storage-tasks/storage-task-quickstart-arm.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates bias toward Windows environments by listing Azure PowerShell as a primary deployment method, referencing PowerShell before Azure CLI in the deployment methods link, and providing explicit PowerShell examples alongside Azure CLI. There is no mention of Linux-specific tools or shell environments, and no examples using Bash or Linux-native scripting. The documentation does not address platform differences or provide parity for Linux users.
Recommendations
  • Ensure Azure CLI examples are presented before or alongside PowerShell examples, as Azure CLI is cross-platform.
  • Include explicit Bash/Linux shell examples for resource management commands, such as az group delete.
  • Avoid referencing PowerShell as the default or primary method; clarify that both CLI and PowerShell are available and cross-platform.
  • Add notes or sections addressing platform differences, if any, and confirm that all steps work equally on Linux, macOS, and Windows.
  • Where possible, provide screenshots or terminal output from Linux environments to demonstrate parity.
GitHub Create Pull Request
Storage Actions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage-actions/storage-tasks/storage-task-quickstart-dotnet.md ...ctions/storage-tasks/storage-task-quickstart-dotnet.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 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a Windows bias by prioritizing Windows tools and workflows (such as Visual Studio and PowerShell), providing detailed instructions and screenshots for Visual Studio, and using PowerShell for resource cleanup without offering equivalent Linux/bash alternatives. While the .NET CLI is mentioned and bash is briefly referenced, Linux-specific guidance and parity in examples (especially for cleanup and tooling) are missing.
Recommendations
  • Provide equivalent Linux/bash commands for all PowerShell examples, especially for resource cleanup (e.g., use Azure CLI az group delete).
  • Include Linux/VS Code workflows and screenshots alongside Visual Studio instructions, or at least ensure parity in detail and guidance.
  • Explicitly mention and show how to use the .NET CLI and code editors (such as VS Code) on Linux/macOS, not just Windows.
  • Avoid assuming Visual Studio is the default or only environment; clarify cross-platform options in all sections.
  • Where Windows-specific tools are referenced (e.g., Visual Studio, PowerShell), always provide a Linux/macOS alternative in the same section, not just in a separate tab.
GitHub Create Pull Request
Storage Actions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage-actions/storage-tasks/storage-task-quickstart-terraform.md ...ons/storage-tasks/storage-task-quickstart-terraform.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 Windows bias by providing only Azure PowerShell examples for verifying results, with no equivalent instructions for Linux-native tools (such as Azure CLI or Bash). The verification steps use PowerShell syntax and reference a PowerShell-specific cmdlet, which is not cross-platform. There is no mention of Linux or macOS workflows, nor are alternative command-line tools or shell environments suggested.
Recommendations
  • Add equivalent verification instructions using Azure CLI (az) with Bash syntax, which is cross-platform and native to Linux/macOS.
  • Present both PowerShell and CLI/Bash examples side-by-side or in tabs, ensuring parity for users on all platforms.
  • Explicitly mention that the verification steps can be performed on Linux/macOS and provide guidance for those environments.
  • Avoid referencing Windows-specific tools (such as PowerShell cmdlets) exclusively; always provide alternatives when possible.
  • Review other steps for subtle Windows-first language or assumptions, and clarify where instructions are platform-agnostic.
GitHub Create Pull Request
Storage Actions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage-actions/storage-tasks/storage-task-assignment-create.md ...ctions/storage-tasks/storage-task-assignment-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 examples for Azure Portal, PowerShell, Azure CLI, Bicep, and ARM templates. However, the PowerShell section is prominent and detailed, which may favor Windows users. There are no explicit Linux shell (bash) examples, and the CLI section uses syntax that is compatible with bash but does not clarify Linux usage or mention platform-specific considerations. The documentation does not mention Linux tools or patterns, nor does it provide parity for Linux users in terms of troubleshooting, environment setup, or alternative scripting approaches.
Recommendations
  • Add explicit bash examples for Linux users, especially in the Azure CLI section, including environment setup and troubleshooting tips for Linux.
  • Clarify that Azure CLI commands are cross-platform and provide notes on any platform-specific differences (e.g., quoting, environment variables).
  • Include a section or note on using these tools from Linux/macOS environments, such as installing Azure CLI on Linux, and provide links to relevant installation guides.
  • Balance PowerShell and CLI coverage by ensuring CLI examples are as detailed as PowerShell, and consider including bash scripts for common workflows.
  • Mention alternative Linux-native tools or scripting approaches where relevant, or explicitly state platform compatibility for all commands.
GitHub Create Pull Request
Storage Actions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage-actions/storage-tasks/storage-task-quickstart-arm.md ...e-actions/storage-tasks/storage-task-quickstart-arm.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 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.
GitHub Create Pull Request
Storage Actions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage-actions/storage-tasks/storage-task-quickstart-dotnet.md ...ctions/storage-tasks/storage-task-quickstart-dotnet.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
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.
GitHub Create Pull Request
Storage Actions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage-actions/storage-tasks/storage-task-quickstart-terraform.md ...ons/storage-tasks/storage-task-quickstart-terraform.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
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.
GitHub Create Pull Request
Storage Actions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage-actions/storage-tasks/storage-task-assignment-create.md ...ctions/storage-tasks/storage-task-assignment-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 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.
GitHub Create Pull Request
Storage Actions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage-actions/storage-tasks/storage-task-conditions-operations-edit.md ...orage-tasks/storage-task-conditions-operations-edit.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 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.
GitHub Create Pull Request
Storage Actions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage-actions/storage-tasks/storage-task-quickstart-dotnet.md ...ctions/storage-tasks/storage-task-quickstart-dotnet.md
High Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
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.
GitHub Create Pull Request
Storage Actions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage-actions/storage-tasks/storage-task-quickstart-terraform.md ...ons/storage-tasks/storage-task-quickstart-terraform.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 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.
GitHub Create Pull Request
← Previous Page 1 of 3 Next →