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 26-50 of 51 flagged pages
Storage Actions Create and run a storage task (.NET) ...ctions/storage-tasks/storage-task-quickstart-dotnet.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Visual Studio (Windows-centric) and .NET CLI (cross-platform) instructions for project setup and package installation, ensuring Linux/macOS users can follow along. However, in the 'Clean up resources' section, only a PowerShell example is given for deleting the resource group, with no equivalent Azure CLI or Bash command. Additionally, Visual Studio is presented first in most sections, which may subtly prioritize Windows workflows.
Recommendations
  • Add Azure CLI and/or Bash examples for resource cleanup (e.g., 'az group delete --name <resource-group>') alongside the PowerShell command.
  • Consider alternating the order of Visual Studio and .NET CLI instructions or explicitly noting that both approaches are valid on all platforms.
  • Where screenshots or instructions are Visual Studio-specific, clarify that VS Code or other editors are equally supported for cross-platform development.
Storage Actions Quickstart: Create a storage task using Terraform ...ons/storage-tasks/storage-task-quickstart-terraform.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 verification steps exclusively using Azure PowerShell, with no equivalent examples for Linux/macOS users (e.g., Azure CLI or REST API). The resource verification section assumes the use of PowerShell, which is primarily a Windows tool, and does not mention or demonstrate cross-platform alternatives.
Recommendations
  • Add verification examples using Azure CLI, which is cross-platform and widely used on Linux/macOS.
  • Include notes or tabs for both Azure PowerShell and Azure CLI, allowing users to choose their preferred tool.
  • Explicitly mention that PowerShell is available on Linux/macOS, or clarify if the cmdlet is Windows-only.
  • Provide REST API or portal-based verification steps for maximum platform neutrality.
Storage Actions Create and run a storage task (.NET) ...ctions/storage-tasks/storage-task-quickstart-dotnet.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 demonstrates a moderate Windows bias. Visual Studio (Windows-only) is presented first in setup and package installation instructions, with screenshots and detailed steps. The cleanup section provides only a PowerShell example, omitting Linux/macOS alternatives. While .NET CLI instructions are included and compatible with Linux/macOS, Windows tools and patterns are emphasized, and Linux-specific guidance is missing in some critical areas.
Recommendations
  • Present .NET CLI instructions before Visual Studio steps, or side-by-side, to avoid Windows-first ordering.
  • Add Linux/macOS-specific cleanup instructions, such as using Azure CLI (az group delete) or Bash scripts.
  • Include screenshots or guidance for popular Linux/macOS editors (e.g., VS Code, JetBrains Rider) alongside Visual Studio.
  • Explicitly mention cross-platform compatibility in prerequisites and setup sections.
  • Where PowerShell is used, provide equivalent Bash/Azure CLI commands.
Medium Priority View Details →
Scanned: 2026-01-13 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 creating a storage task in Azure using the Portal, PowerShell, Azure CLI, Bicep, and ARM templates. The PowerShell section is detailed and appears before Azure CLI, which is more commonly used on Linux/macOS. There are no Linux/macOS-specific examples, nor are there references to Bash scripting or Linux tools. The CLI section is present and functional, but PowerShell is given prominence and detail, which may create friction for non-Windows users.
Recommendations
  • Provide Bash shell examples alongside PowerShell, especially for scripting tasks.
  • List Azure CLI instructions before PowerShell, as CLI is cross-platform and preferred by many Linux/macOS users.
  • Explicitly mention that Azure CLI works on Linux/macOS and provide installation links.
  • Add notes or tips for Linux/macOS users, such as handling JSON, environment variables, or authentication differences.
  • Ensure parity in detail and troubleshooting between PowerShell and CLI sections.
Storage Actions Quickstart: Create a storage task using Terraform ...ons/storage-tasks/storage-task-quickstart-terraform.md
Medium Priority View Details →
Scanned: 2026-01-13 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 steps exclusively using Azure PowerShell, a tool most commonly used on Windows. There are no CLI (az), Bash, or Linux/macOS-specific instructions or examples for verifying the results, which may hinder users on non-Windows platforms. The use of PowerShell variables and cmdlets is Windows-centric, and no alternative verification method is offered.
Recommendations
  • Add equivalent verification instructions using Azure CLI (az) commands, which are cross-platform and commonly used on Linux/macOS.
  • Provide Bash shell examples for extracting Terraform outputs and passing them to Azure CLI commands.
  • Explicitly mention that Azure PowerShell is available on Linux/macOS, or link to installation instructions for non-Windows users.
  • Consider presenting CLI/Bash examples before or alongside PowerShell examples to ensure parity.
Storage Actions About Azure Storage Actions ...re-docs/blob/main/articles/storage-actions/overview.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation lists PowerShell as an example tool before Azure CLI and other cross-platform options, and does not provide explicit Linux-specific examples or mention Linux shell usage. The ordering and emphasis on PowerShell may suggest a Windows-centric approach, even though Azure CLI, REST, SDKs, Bicep, Terraform, and ARM templates are cross-platform.
Recommendations
  • Explicitly mention Linux and macOS compatibility for all tools listed (Azure CLI, REST, SDKs, Bicep, Terraform, ARM templates).
  • Provide example commands for both PowerShell and Bash (or other Linux shells) where applicable.
  • When listing tools, alternate or randomize the order, or start with Azure CLI (which is cross-platform) instead of PowerShell.
  • Add a section or note highlighting cross-platform support and usage patterns for Linux users.
  • Ensure that linked articles (e.g., quickstarts, how-tos) include Linux/Bash examples alongside PowerShell.
Storage Actions Storage task conditions ...orage-actions/storage-tasks/storage-task-conditions.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page demonstrates a mild Windows bias. It mentions Azure PowerShell before Azure CLI when discussing tools for creating storage tasks outside the portal, and it refers to PowerShell first when describing condition preview capabilities. No Linux-specific tools or examples are provided, and the CLI is only mentioned as an alternative to PowerShell, not as an equal or primary option. There are no explicit Linux examples, nor are Linux shell patterns or tools referenced.
Recommendations
  • Present Azure CLI before or alongside Azure PowerShell when listing tools, to avoid implying Windows-first workflows.
  • Include explicit examples using Azure CLI commands for creating and previewing storage task conditions, demonstrating parity with PowerShell.
  • Mention that Azure CLI is cross-platform and suitable for Linux and macOS users.
  • If relevant, add references to scripting with Bash or other Linux shells for advanced automation.
  • Ensure screenshots and instructions do not assume a Windows environment (e.g., avoid showing only PowerShell terminals).
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page presents examples for creating storage tasks in the Azure Portal, PowerShell, Azure CLI, Bicep, and ARM templates. However, there is a noticeable Windows bias: PowerShell (a Windows-centric tool) is presented before Azure CLI, and there are no explicit Linux shell (bash) examples or references to Linux-specific tooling. The PowerShell section is more detailed, with step-by-step instructions and command explanations, while the Azure CLI section is less comprehensive. There is no mention of Linux or cross-platform considerations, and no guidance for users on Linux systems (e.g., bash scripting, environment setup).
Recommendations
  • Add explicit bash examples for Linux users, especially for scripting storage task creation and assignment.
  • Present Azure CLI examples before PowerShell, or at least in parallel, to avoid implying Windows/Powershell primacy.
  • Include notes or sections on cross-platform usage, clarifying that Azure CLI works natively on Linux and macOS.
  • Balance the depth of instructions between PowerShell and Azure CLI, ensuring Linux users have equally detailed guidance.
  • Reference installation and usage of Azure CLI on Linux, and provide troubleshooting tips for common Linux environments.
Storage Actions Define storage task conditions & operations ...orage-tasks/storage-task-conditions-operations-edit.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 examples and instructions for three interfaces: Azure Portal, PowerShell, and Azure CLI. PowerShell is given equal prominence to Azure CLI, with detailed examples and explicit cmdlets. However, there is a notable absence of Linux-specific shell (e.g., Bash) examples, and PowerShell is traditionally associated with Windows environments. The documentation does not mention or provide parity for Linux-native scripting or tools, and PowerShell examples are presented before Azure CLI in every section, suggesting a Windows-first bias.
Recommendations
  • Add explicit Bash shell examples for Linux users, especially for JSON manipulation and Azure CLI usage.
  • Clarify that Azure CLI examples are cross-platform and can be run in Bash, Zsh, or other Linux shells.
  • Consider reordering examples so that Azure CLI (the most cross-platform tool) appears before PowerShell.
  • Mention that PowerShell is available on Linux, but provide guidance for users who prefer native Linux shells.
  • Include troubleshooting or tips for Linux environments, such as handling JSON strings or environment variables in Bash.
  • Ensure that screenshots and instructions do not assume a Windows environment (e.g., file paths, UI conventions).
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 presents Windows-centric tooling and patterns before Linux equivalents. The PowerShell section is given prominence before Azure CLI, which is more cross-platform. There are no explicit Linux shell or scripting examples, and no mention of Linux-specific considerations or tools. The portal instructions are platform-neutral, but the command-line examples favor Windows-first patterns (PowerShell before CLI).
Recommendations
  • Present Azure CLI examples before PowerShell, as CLI is cross-platform and preferred on Linux.
  • Add explicit Linux shell (bash) examples where relevant, such as using environment variables or piping JSON.
  • Include notes or tips for Linux users, such as installation instructions for Azure CLI on Linux.
  • Clarify that PowerShell is available on Linux, but Azure CLI is often the default choice for Linux environments.
  • Ensure screenshots and instructions do not assume Windows-only environments (e.g., avoid referencing Windows paths or UI elements that differ on Linux).
Storage Actions Storage task conditions ...orage-actions/storage-tasks/storage-task-conditions.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 exhibits mild Windows bias by mentioning Azure PowerShell before Azure CLI when discussing tools for creating storage tasks outside the portal. Additionally, the portal-based examples and screenshots reflect a GUI experience typical of Windows environments. Although Azure CLI and SDKs are mentioned, there are no explicit Linux-specific examples or references to Linux-native tools or workflows.
Recommendations
  • List Azure CLI before Azure PowerShell when mentioning cross-platform tools, or mention both together to avoid implying priority.
  • Include explicit examples using Azure CLI commands to demonstrate parity with PowerShell examples.
  • Add notes or examples for Linux users, such as how to edit JSON conditions using common Linux editors or workflows.
  • Mention that Azure CLI is cross-platform and provide links or guidance for Linux users.
  • Ensure that screenshots and instructions do not assume a Windows environment (e.g., avoid referencing Windows-only features or UI elements).
Storage Actions About Azure Storage Actions ...re-docs/blob/main/articles/storage-actions/overview.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 lists PowerShell before Azure CLI and other cross-platform tools when describing ways to create storage task definitions. This ordering may subtly prioritize Windows-centric tooling. There are no explicit Linux examples or references to Linux-specific patterns, but the mention of PowerShell before CLI can be perceived as a Windows-first bias.
Recommendations
  • List Azure CLI before PowerShell when enumerating automation options, as CLI is cross-platform and widely used on Linux.
  • Provide explicit Linux and macOS examples or usage notes where relevant, especially in sections discussing command-line tools.
  • Clarify that all listed tools (CLI, PowerShell, SDKs, Bicep, Terraform, ARM templates) are cross-platform, and link to platform-specific setup guides.
  • Consider including example workflows or screenshots from Linux environments in quickstart or tutorial articles.
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
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 Windows bias by listing Azure PowerShell as a primary deployment method and referencing PowerShell before Linux alternatives. Although Azure CLI is mentioned and examples are provided, the link to 'Deploy templates' points to a PowerShell-focused page, and PowerShell is given equal prominence to CLI, which may not reflect the usage patterns of Linux users. There are no Linux-specific shell examples (e.g., Bash), and Windows tools/patterns are mentioned at least as prominently as cross-platform alternatives.
Recommendations
  • Ensure that Azure CLI (which is cross-platform) is listed before Azure PowerShell in all instructions and links.
  • Provide explicit Bash shell examples for Linux users where relevant.
  • Include links to documentation pages for deploying ARM templates using Bash and other Linux-native tools, not just PowerShell.
  • Clarify that both Azure CLI and PowerShell are available on all platforms, but highlight CLI as the default for cross-platform scenarios.
  • Avoid referencing Windows-specific tools or patterns unless a Linux equivalent is also provided and described.
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
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 examples for the Azure Portal, PowerShell, and Azure CLI, but omits direct examples for Linux shell environments (e.g., Bash). PowerShell examples are consistently presented before Azure CLI, which is more cross-platform. There is an implicit Windows bias in the ordering and choice of command-line tooling, as PowerShell is primarily associated with Windows, while Bash or other Linux-native shells are not mentioned.
Recommendations
  • Add explicit Bash shell examples for all command-line operations, demonstrating how to use Azure CLI in a Linux environment.
  • Reorder the command-line sections to present Azure CLI examples before PowerShell, reflecting Azure CLI's cross-platform nature.
  • Clarify that Azure CLI commands work natively on Linux, macOS, and Windows, and provide guidance for Linux users where appropriate.
  • Avoid exclusive reliance on PowerShell-specific cmdlets; where possible, use Azure CLI or REST API examples that are platform-agnostic.
  • Include notes or tips for Linux users, such as differences in quoting or environment setup, to ensure parity.
Storage Actions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage-actions/storage-tasks/storage-task-create.md ...s/storage-actions/storage-tasks/storage-task-create.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation presents Windows-centric tooling (PowerShell) before cross-platform alternatives (Azure CLI), and provides detailed PowerShell instructions and examples. While Azure CLI is included, PowerShell is given precedence, which may suggest a Windows-first bias. No explicit Linux-only tools or shell examples are provided, but the CLI section is present and reasonably complete.
Recommendations
  • Present Azure CLI examples before PowerShell, as Azure CLI is cross-platform and more accessible to Linux and macOS users.
  • Explicitly mention that both PowerShell and Azure CLI are available on all major platforms, and provide guidance for Linux/macOS users where relevant.
  • Where possible, add Bash shell script examples alongside PowerShell, especially for common automation scenarios.
  • Ensure that screenshots and UI walkthroughs do not assume a Windows environment (e.g., avoid Windows-specific UI elements or terminology).
  • Consider adding a section or callout for Linux/macOS users, highlighting any differences or tips for those platforms.
Storage Actions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage-actions/storage-tasks/storage-task-create.md ...s/storage-actions/storage-tasks/storage-task-create.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation presents Windows-centric tooling and patterns first, specifically by listing PowerShell instructions before Azure CLI. PowerShell is a Windows-native shell, and its prominence may signal a Windows-first bias. However, the documentation does provide Azure CLI examples, which are cross-platform, and does not exclusively mention Windows tools or omit Linux equivalents.
Recommendations
  • Present Azure CLI examples before PowerShell, as Azure CLI is cross-platform and more inclusive for Linux and macOS users.
  • Explicitly state that both PowerShell and Azure CLI are supported on Windows, Linux, and macOS, and provide links to installation instructions for each platform.
  • If possible, include Bash shell examples (where relevant) to further support Linux users.
  • Avoid implying that PowerShell is the default or preferred automation tool unless there is a technical reason.
  • Ensure screenshots and UI descriptions do not reference Windows-specific elements unless unavoidable.
Storage Actions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage-actions/overview.md ...re-docs/blob/main/articles/storage-actions/overview.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation lists PowerShell before Azure CLI and other cross-platform tools when describing how to create storage task definitions. This ordering, along with explicit mention of PowerShell, suggests a subtle Windows-first bias. There are no explicit Linux-only examples or tools, and the documentation does not provide parity in example ordering or highlight Linux workflows.
Recommendations
  • List Azure CLI before PowerShell when enumerating supported tools, as CLI is cross-platform.
  • Provide explicit Linux shell examples (e.g., Bash) alongside PowerShell where relevant.
  • Add a note clarifying that all SDKs and tools (CLI, REST, Terraform, Bicep, ARM templates) are cross-platform and suitable for Linux, macOS, and Windows.
  • Ensure that examples and walkthroughs include both PowerShell and Bash/CLI commands.
  • Avoid using 'PowerShell' as a generic example unless parity is provided for Linux users.
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
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides examples and instructions for three interfaces: Azure Portal, PowerShell, and Azure CLI. PowerShell examples are given equal prominence to Azure CLI, but PowerShell is a Windows-centric tool, and its examples are presented before Azure CLI in every section. There are no examples for Bash, Linux shell scripting, or other Linux-native tools. The documentation assumes familiarity with PowerShell-specific cmdlets and patterns, which may disadvantage Linux users who typically use Bash or other shells. Azure CLI is cross-platform, but its examples are always secondary to PowerShell, and no explicit Linux-specific guidance is provided.
Recommendations
  • Add Bash/Linux shell examples alongside PowerShell and Azure CLI, especially for condition and operation definitions.
  • Present Azure CLI examples before PowerShell, as Azure CLI is cross-platform and more widely used on Linux.
  • Explicitly mention that Azure CLI commands work natively on Linux/macOS and provide any necessary environment setup instructions.
  • Avoid assuming PowerShell as the default scripting environment; clarify that PowerShell is primarily for Windows users.
  • Consider including links or references to Linux-specific documentation or troubleshooting guides.
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
Medium Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
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.
Storage Actions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage-actions/storage-tasks/storage-task-create.md ...s/storage-actions/storage-tasks/storage-task-create.md
Medium Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
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.
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
Low Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation presents both Azure CLI and Azure PowerShell commands for resource cleanup, but PowerShell is mentioned alongside CLI as a primary method and is referenced in the deployment methods link before Linux equivalents. The link to 'Deploy templates' points to a PowerShell-focused page, which may create friction for Linux/macOS users. However, Azure CLI examples are present and shown first in the cleanup section.
Recommendations
  • Ensure that deployment method links include both Azure CLI and PowerShell documentation, or link to a page that covers all major platforms equally.
  • Explicitly mention that Azure CLI works cross-platform and is recommended for Linux/macOS users.
  • Where multiple command-line options are presented, clarify platform compatibility and provide parity in example depth and order.
  • Consider listing CLI examples before PowerShell throughout for better Linux/macOS parity.
Low 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 step-by-step instructions for creating a storage task in Azure using the Portal, PowerShell, Azure CLI, Bicep, and ARM templates. The PowerShell section is detailed and prominent, reflecting a Windows-centric approach. The PowerShell tab appears before Azure CLI, and the PowerShell examples use Windows-specific tooling. However, Azure CLI, Bicep, and ARM template examples are also provided, supporting cross-platform usage. No Linux/macOS-specific friction is present, but the ordering and depth of PowerShell coverage indicate mild Windows bias.
Recommendations
  • Ensure parity in example depth and clarity between PowerShell and Azure CLI sections.
  • Consider listing Azure CLI before PowerShell to reflect cross-platform priorities.
  • Add explicit notes that both PowerShell and Azure CLI are cross-platform, and clarify any OS-specific prerequisites if relevant.
  • Where possible, provide Bash shell example snippets for Azure CLI usage.
  • Review for any assumptions about Windows environments in PowerShell instructions and clarify cross-platform compatibility.
Storage Actions Define storage task conditions & operations ...orage-tasks/storage-task-conditions-operations-edit.md
Low 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 examples for the Azure Portal, PowerShell, and Azure CLI. PowerShell is featured prominently and is presented before Azure CLI in all code example tabs and sections. There are no explicit Linux/macOS-specific examples, and the CLI examples use generic syntax without platform-specific notes. The PowerShell focus and ordering may create friction for Linux/macOS users, but the Azure CLI is well-supported and documented throughout.
Recommendations
  • Add explicit notes clarifying that Azure CLI works cross-platform (Windows, Linux, macOS), and that PowerShell examples are primarily for Windows users.
  • Consider presenting Azure CLI examples before PowerShell, or at least alternating their order, to avoid implicit prioritization of Windows tooling.
  • Include brief instructions or links for installing and using Azure CLI on Linux/macOS.
  • If there are any platform-specific caveats for CLI or PowerShell, call them out in the documentation.
  • Where possible, add Bash shell examples for common tasks to further improve Linux parity.
Storage Actions Create and manage a storage task assignment ...ctions/storage-tasks/storage-task-assignment-create.md
Low Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides detailed PowerShell examples for creating and managing storage task assignments, which are specific to Windows environments. The PowerShell tab appears before the Azure CLI tab, and the CLI examples use Bash syntax, which is cross-platform but not explicitly highlighted as Linux/macOS friendly. There are no Linux shell or macOS-specific examples, nor is there mention of platform-specific differences or considerations. The documentation does not reference Windows-only tools outside of PowerShell, and the Azure CLI and template/Bicep sections are platform-neutral.
Recommendations
  • Add explicit notes clarifying that Azure CLI examples work on Linux/macOS as well as Windows.
  • Provide Linux/macOS shell examples (e.g., Bash, zsh) for common tasks, especially for role assignment and date/time handling.
  • Reorder tabs so that cross-platform tools (Azure CLI) appear before PowerShell, or clarify the intended audience for each.
  • Include troubleshooting or environment setup notes for Linux/macOS users where relevant (e.g., installing Azure CLI, handling date formatting).
Storage Actions Storage task operations ...orage-actions/storage-tasks/storage-task-operations.md
Low Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation mentions Azure PowerShell as the primary example of a tool for creating storage tasks outside the portal, listing it before Azure CLI. No Linux/macOS-specific tools or patterns are referenced, and there are no platform-specific examples or guidance. However, the core content (JSON format and operations) is platform-neutral.
Recommendations
  • Mention Azure CLI before or alongside Azure PowerShell when listing tools, as CLI is cross-platform.
  • Explicitly state that the JSON format and operations are platform-agnostic and can be used from any OS.
  • Add examples or references for using these operations with Linux/macOS environments (e.g., via Azure CLI or REST API).
  • Avoid implying PowerShell is the default or preferred method for non-portal usage.