Storage Discovery

28
Total Pages
25
Linux-Friendly Pages
3
Pages with Bias
10.7%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

6 issues found
Showing 1-6 of 6 flagged pages
Storage Discovery Create and manage an Azure Storage Discovery Workspace ...ob/main/articles/storage-discovery/create-workspace.md
Medium Priority View Details →
Scanned: 2026-01-12 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 is featured prominently as a primary automation example, and the PowerShell tab appears before the Azure CLI tab. The scripting example is written for PowerShell, a Windows-centric tool, with no Bash or Linux shell equivalent. Although Azure CLI is included, the order and emphasis favor Windows tools and patterns.
Recommendations
  • Add Bash/Linux shell examples alongside PowerShell, especially for scripting tasks.
  • Present Azure CLI examples before or alongside PowerShell to emphasize cross-platform parity.
  • Explicitly mention that Azure CLI works on Linux/macOS and provide installation links for non-Windows platforms.
  • If PowerShell is shown, clarify that PowerShell Core is available cross-platform, or provide Bash alternatives.
  • Include screenshots or instructions for Linux/macOS users where relevant.
GitHub Create Pull Request
Storage Discovery Create and manage an Azure Storage Discovery Workspace ...ob/main/articles/storage-discovery/create-workspace.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
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 creating an Azure Storage Discovery workspace using the Azure portal, Azure PowerShell, and Azure CLI. The PowerShell example is given in full script form, while the CLI example is provided as a single command. There is a notable emphasis on PowerShell, which is primarily a Windows tool, and the PowerShell example is more elaborate than the CLI example. No Linux/macOS-specific guidance, troubleshooting, or environment notes are provided. The ordering also places PowerShell before CLI, which is more commonly used on Linux/macOS.
Recommendations
  • Provide Bash shell examples alongside PowerShell, especially for scripting tasks.
  • Add notes or troubleshooting tips for Linux/macOS users (e.g., CLI installation, environment setup).
  • Ensure CLI examples are as detailed as PowerShell ones, including variable usage and multi-step workflows.
  • Consider reordering examples to present CLI first, or clarify cross-platform support.
  • Explicitly mention that both CLI and PowerShell are cross-platform, and link to installation guides for each OS.
GitHub Create Pull Request
Storage Discovery Bicep template for creating an Azure Storage Discovery workspace ...n/articles/storage-discovery/create-workspace-bicep.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation presents both Azure PowerShell and Azure CLI examples for deployment and resource review, but consistently lists Azure PowerShell (a Windows-centric tool) before Azure CLI. There is no mention of Linux/macOS-specific considerations, nor are there any examples using Bash or shell scripting, which are common on non-Windows platforms. The use of PowerShell tabs and examples first may subtly signal Windows as the primary environment.
Recommendations
  • Alternate the order of examples so that Azure CLI (cross-platform) is shown before Azure PowerShell, or present CLI as the default.
  • Explicitly mention that Azure CLI works on Windows, Linux, and macOS, and provide Bash/shell script examples where appropriate.
  • Add a note clarifying that PowerShell is available on Linux/macOS, or link to installation instructions for non-Windows platforms.
  • Consider adding a 'Platform considerations' section to highlight cross-platform compatibility.
GitHub Create Pull Request
Storage Discovery Planning for an Azure Storage Discovery deployment ...main/articles/storage-discovery/deployment-planning.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation lists Azure PowerShell as a primary method for registering the resource provider namespace, and mentions Azure portal and PowerShell before Azure CLI. This ordering and emphasis may subtly favor Windows users, as PowerShell is most commonly associated with Windows environments. However, Azure CLI is mentioned and linked, providing Linux/macOS users with a viable alternative.
Recommendations
  • Present Azure CLI examples and links before or alongside PowerShell, as CLI is cross-platform and preferred by many Linux/macOS users.
  • Explicitly state that Azure CLI works on Linux/macOS and provide example commands for both CLI and PowerShell.
  • Consider adding a table or section that shows equivalent commands for Azure Portal, PowerShell, and CLI, clarifying platform compatibility.
  • Avoid language that implies PowerShell is the default or primary method unless there is a technical reason.
GitHub Create Pull Request
Storage Discovery Bicep template for creating an Azure Storage Discovery workspace ...n/articles/storage-discovery/create-workspace-bicep.md
Low Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation presents both Azure PowerShell and Azure CLI examples for deployment and resource review, but PowerShell (a Windows-centric tool) is consistently listed first in all sections. There are no Linux/macOS-specific notes or examples, and no mention of Bash, shell scripting, or platform-specific considerations. While Azure CLI is cross-platform, the ordering and emphasis may subtly favor Windows users.
Recommendations
  • Alternate the order of examples, sometimes listing Azure CLI first to avoid implicit prioritization of Windows tools.
  • Explicitly mention that Azure CLI works on Linux/macOS and provide links or notes for installation on those platforms.
  • Add a short section or note confirming that all steps are cross-platform and can be performed on Linux/macOS using Azure CLI.
  • Consider including Bash script examples for automation, or at least mention that Bash is commonly used on Linux/macOS.
GitHub Create Pull Request
Storage Discovery Planning for an Azure Storage Discovery deployment ...main/articles/storage-discovery/deployment-planning.md
Low Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation lists Azure PowerShell as a primary method for registering the resource provider namespace, with Azure CLI mentioned after. The Azure portal (GUI, cross-platform) is listed first, but among command-line options, PowerShell is mentioned before CLI. No explicit Linux/macOS examples or considerations are provided, and there is no mention of platform-specific differences or requirements for Linux/macOS users.
Recommendations
  • List Azure CLI before Azure PowerShell when presenting command-line options, as CLI is cross-platform and more commonly used on Linux/macOS.
  • Provide explicit examples or notes for Linux/macOS users, especially for command-line tasks.
  • Clarify that both Azure CLI and PowerShell are available on all major platforms, but CLI is native to Linux/macOS.
  • Consider adding a 'Platform considerations' section to address any OS-specific nuances.
GitHub Create Pull Request