Storage

688
Total Pages
395
Linux-Friendly Pages
293
Pages with Bias
42.6%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

1657 issues found
Showing 276-300 of 1657 flagged pages
Storage How to migrate your classic storage accounts to Azure Resource Manager ...ain/articles/storage/common/classic-account-migrate.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by providing only PowerShell examples for command-line operations, referencing Windows-centric tools (PowerShell, Azure PowerShell Service Management module), and omitting equivalent Azure CLI or Bash examples that would be more familiar to Linux/macOS users. The structure consistently presents PowerShell before mentioning Azure CLI (and only in a general way), and does not provide step-by-step instructions or code samples for Linux-friendly tools.
Recommendations
  • Add Azure CLI examples alongside PowerShell for all command-line operations (listing accounts, deleting disk artifacts, migrating accounts).
  • Provide Bash script samples where appropriate, especially for automation tasks.
  • Explicitly mention cross-platform compatibility for tools and commands, clarifying which instructions apply to Linux/macOS.
  • Reorder sections or present PowerShell and Azure CLI examples in parallel tabs to avoid Windows-first bias.
  • Include troubleshooting guidance for Linux users (e.g., common CLI errors, environment setup).
GitHub Create Pull Request
Storage Configure network routing preference ...storage/common/configure-network-routing-preference.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 is featured prominently as a primary automation method, and the PowerShell tab is consistently listed before Azure CLI. The use of PowerShell commands and terminology (e.g., Set-AzStorageAccount, Get-AzStorageAccount) reflects a Windows-centric approach. There is no mention of Linux-specific tools, shell environments, or scripting patterns, and the Azure CLI instructions, while present, are often introduced as secondary or alternative options. The documentation does not address platform-specific nuances or provide parity for Linux users beyond the generic CLI examples.
Recommendations
  • Explicitly mention that Azure CLI commands work natively on Linux, macOS, and Windows, and provide shell-specific notes where relevant.
  • Add Bash scripting examples for common tasks, especially for automation scenarios.
  • Clarify that PowerShell Core is cross-platform, but also provide examples using Bash or other popular Linux shells.
  • Include troubleshooting notes or environment setup instructions for Linux users (e.g., installing Azure CLI on Ubuntu, using environment variables).
  • Reorder tabs or alternate the order between PowerShell and Azure CLI to avoid implicit prioritization of Windows tooling.
  • Reference Linux-native tools or patterns where appropriate, such as using curl for REST API calls, or jq for JSON parsing.
GitHub Create Pull Request
Storage Configure cross-tenant customer-managed keys for an existing storage account ...r-managed-keys-configure-cross-tenant-existing-account.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 Missing Linux Example
Summary
The documentation provides detailed instructions for configuring cross-tenant customer-managed keys using the Azure portal, PowerShell, and Azure CLI. However, the command-line examples are heavily focused on PowerShell (which is primarily associated with Windows) and Azure CLI, with PowerShell presented before Azure CLI. There are no explicit Linux shell (bash) examples, nor any mention of Linux-specific patterns or tools. The PowerShell example is given before the Azure CLI example, which may suggest a Windows-first bias. Additionally, there are no notes or guidance for Linux users regarding differences or considerations when using the CLI on Linux.
Recommendations
  • Add explicit bash shell examples for Azure CLI commands, showing usage in a typical Linux environment.
  • Include notes or guidance for Linux users, such as differences in environment variables, quoting, or command syntax.
  • Consider presenting Azure CLI examples before PowerShell, as Azure CLI is cross-platform and widely used on Linux.
  • If PowerShell is required, clarify that PowerShell Core is available on Linux and macOS, and provide installation guidance.
  • Ensure screenshots and UI instructions are platform-neutral or include notes for any platform-specific differences.
GitHub Create Pull Request
Storage We're retiring classic storage accounts on August 31, 2024 ...s/storage/common/classic-account-migration-overview.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 Tools Windows First
Summary
The documentation page demonstrates a moderate Windows bias, primarily through its repeated references to PowerShell cmdlets for management and migration tasks. The FAQ specifically discusses legacy and modern PowerShell usage, without mentioning Linux equivalents such as Azure CLI or Bash scripting. The support instructions and migration steps do not provide cross-platform command examples, and Windows-centric tools are referenced before any alternatives. There are no explicit Linux or macOS examples or guidance, and no mention of Azure CLI, which is the primary cross-platform tool for Azure management.
Recommendations
  • Add Azure CLI examples alongside or before PowerShell examples for all migration and management operations.
  • Explicitly mention that migration and management tasks can be performed from Linux/macOS using Azure CLI or REST API.
  • Provide Bash script samples for common migration tasks to demonstrate Linux parity.
  • Clarify that both PowerShell and Azure CLI are supported and link to relevant cross-platform documentation.
  • Review FAQ and guidance sections to ensure Linux users are not excluded, e.g., by referencing CLI commands and tools.
GitHub Create Pull Request
Storage Understand storage account migration from classic to Azure Resource Manager ...es/storage/common/classic-account-migration-process.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 page demonstrates a Windows bias by referencing PowerShell and Windows-centric tools before mentioning Azure CLI, and by linking to migration guides that prioritize PowerShell usage. There are no explicit Linux or Bash examples, nor is there mention of Linux-specific patterns or tools. The documentation does not provide parity in example commands or workflows for Linux users.
Recommendations
  • Provide explicit Bash/Azure CLI examples alongside PowerShell examples for all migration steps.
  • Reference Linux-specific workflows and tools where applicable, such as shell scripting for automation.
  • Ensure that links to migration guides include both PowerShell and Azure CLI sections, with equal prominence.
  • Add notes or sections clarifying cross-platform support and any OS-specific considerations.
  • Avoid listing Windows/PowerShell tools before their Linux/Azure CLI equivalents; present both together or alternate order.
GitHub Create Pull Request
Storage Configure cross-tenant customer-managed keys for a new storage account ...stomer-managed-keys-configure-cross-tenant-new-account.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 Missing Linux Example
Summary
The documentation provides detailed instructions for configuring cross-tenant customer-managed keys using the Azure portal, PowerShell, and Azure CLI. The PowerShell example is given before the Azure CLI example, and there is no mention of Linux-specific shell environments or examples (e.g., Bash, zsh). The CLI instructions are generic but do not address Linux-specific nuances, and there are no references to Linux tools or patterns. The documentation implicitly prioritizes Windows/PowerShell by order and depth, and omits explicit Linux guidance.
Recommendations
  • Provide Linux/Bash-specific examples and notes, especially for Azure CLI usage (e.g., differences in quoting, environment variables, or shell behavior).
  • Include explicit guidance for running Azure CLI commands on Linux and macOS, such as installation instructions or troubleshooting tips for those platforms.
  • Balance the order of examples by presenting Azure CLI before PowerShell, or by alternating the order in different sections.
  • Mention cross-platform compatibility for both PowerShell (pwsh on Linux/macOS) and Azure CLI, clarifying any platform-specific considerations.
  • Add a note or section highlighting that all steps can be performed on Linux, macOS, and Windows, and link to platform-specific documentation where relevant.
GitHub Create Pull Request
Storage GPv1 ZRS standard account retirement FAQ ...-zone-redundant-storage-migration-freq-asked-questions.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation references upgrade procedures via the Azure portal, CLI, or PowerShell, but consistently mentions PowerShell alongside CLI, which may imply a Windows-first approach. There are no explicit Linux shell (bash) or macOS examples, nor are Linux-specific tools or patterns discussed. The upgrade guidance and troubleshooting sections mention PowerShell and CLI, but do not provide parity for Linux users or clarify cross-platform usage.
Recommendations
  • Include explicit examples for Azure CLI usage on Linux/macOS (e.g., bash commands), not just PowerShell.
  • Clarify that Azure CLI is cross-platform and provide instructions for installation and usage on Linux and macOS.
  • Avoid listing PowerShell before CLI, or alternate the order to avoid Windows-first perception.
  • Add troubleshooting steps or upgrade instructions specifically for Linux users, including common shell environments.
  • Where PowerShell is mentioned, provide equivalent bash or shell commands for Linux/macOS users.
GitHub Create Pull Request
Storage How to upgrade a General Purpose v1 (GPv1) with ZRS redundancy account to GPv2 ...rpose-version-1-zone-redundant-storage-upgrade-process.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 Missing Linux Example
Summary
The documentation provides upgrade instructions using the Azure portal, PowerShell, and Azure CLI. PowerShell is featured as a primary command-line example, which is Windows-centric, and is presented before the Azure CLI example. There are no explicit Linux shell (bash) examples or references to Linux-specific tools or workflows. The CLI example is generic but lacks context for Linux users (e.g., bash usage, environment setup).
Recommendations
  • Add explicit bash shell examples for Azure CLI usage, showing command execution in a Linux environment.
  • Clarify that Azure CLI works cross-platform and provide installation/setup instructions for Linux and macOS.
  • Consider including examples using other popular Linux tools (e.g., REST API via curl) if relevant.
  • Balance the order of examples so that CLI/bash instructions are presented before or alongside PowerShell, not after.
  • Explicitly mention platform compatibility for each tool (PowerShell, Azure CLI) to help users choose the best option for their OS.
GitHub Create Pull Request
Storage Enable infrastructure encryption for double encryption of data ...les/storage/common/infrastructure-encryption-enable.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 Tools Windows First
Summary
The documentation provides detailed instructions and examples for enabling infrastructure encryption using the Azure portal, PowerShell, Azure CLI, and ARM templates. PowerShell is given a dedicated section with full example commands, and references to installing the Az.Storage PowerShell module are included. This reflects a bias toward Windows-centric tools and workflows, as PowerShell is primarily a Windows technology (despite cross-platform support, its usage is still most common on Windows). The Azure CLI section is present and cross-platform, but PowerShell is listed before CLI, and there are no explicit Linux-specific examples or notes. The documentation does not mention Linux shell scripting, Bash, or OS-specific considerations, and the overall pattern prioritizes Windows tools and workflows.
Recommendations
  • Add explicit Bash/Linux shell examples for Azure CLI commands, including verification steps using jq or other common Linux tools.
  • Clarify that Azure CLI is cross-platform and provide installation/usage notes for Linux and macOS users.
  • Consider reordering sections so that cross-platform tools (Azure CLI) appear before Windows-centric tools (PowerShell).
  • Add a note about PowerShell Core being available on Linux/macOS, and provide guidance for those platforms if PowerShell examples are retained.
  • Include troubleshooting or verification steps that use Linux-native tools (e.g., curl, jq) where appropriate.
GitHub Create Pull Request
Storage Customer intent: "As a cloud administrator, I want to query storage accounts based on specific case-insensitive or case-sensitive tags, so that I can efficiently manage and locate resources in my environment." ...main/articles/storage/common/includes/azure-storage.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 Missing Linux Example
Summary
The documentation provides examples for Azure CLI, Azure PowerShell, and the Azure Portal. While Azure CLI is cross-platform, Azure PowerShell is primarily associated with Windows environments, and no explicit Linux shell (bash, zsh) or scripting examples are provided. The PowerShell examples are always present and sometimes listed before or alongside CLI, but never after a Linux-specific example. There is no mention of Linux-specific tools, nor any guidance for Linux users beyond the CLI, which could be improved for parity.
Recommendations
  • Add explicit bash or shell script examples for each scenario, demonstrating usage in a native Linux environment.
  • Clarify that Azure CLI commands work identically on Linux, macOS, and Windows, and provide any OS-specific notes if needed.
  • Consider adding a 'Linux' or 'macOS' tab alongside 'Azure CLI' and 'Azure PowerShell' to show parity and encourage cross-platform usage.
  • If PowerShell is shown, clarify that PowerShell Core is available on Linux and macOS, and provide installation or usage notes for non-Windows platforms.
  • Avoid listing PowerShell examples before CLI or Linux-native examples unless there is a clear reason.
GitHub Create Pull Request
Storage Enable and manage Azure Storage Analytics logs (classic) ...ticles/storage/common/manage-storage-analytics-logs.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by providing only PowerShell examples for command-line configuration, explicitly instructing users to open a Windows PowerShell command window, and referencing Windows file paths (e.g., C:\Logs\Storage) in AzCopy examples. There are no CLI, Bash, or Linux-native examples, nor are cross-platform alternatives (such as Azure CLI) mentioned. Windows tools and patterns (PowerShell, Windows paths) are presented exclusively and before any Linux equivalents, which are absent.
Recommendations
  • Add Azure CLI examples for enabling and managing Storage Analytics logs, including retention policy configuration.
  • Provide Bash shell script examples for Linux/macOS users.
  • Use platform-neutral file paths in AzCopy examples (e.g., ~/Logs/Storage or /home/user/Logs/Storage).
  • Clarify that AzCopy and Azure CLI are cross-platform and can be used on Linux/macOS as well as Windows.
  • Include instructions for using the REST API with curl or similar tools from Linux/macOS.
  • Avoid language that assumes the user is on Windows (e.g., 'Open a Windows PowerShell command window').
  • Mention and link to installation guides for Azure CLI and AzCopy on Linux/macOS.
GitHub Create Pull Request
Storage Change how a storage account is replicated ...b/main/articles/storage/common/redundancy-migration.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation demonstrates a Windows bias by consistently listing PowerShell examples before Azure CLI, providing more detailed PowerShell scripts, and referencing Windows-centric tools and workflows (such as PowerShell and CSV handling in Windows style). Portal instructions are also Windows-oriented, and there is little to no mention of Linux-specific patterns, shell scripting, or alternative Linux tools. While Azure CLI examples are present, they are always secondary, and the scripting guidance is less detailed than for PowerShell.
Recommendations
  • Alternate the order of PowerShell and Azure CLI examples, sometimes presenting CLI first.
  • Provide Bash shell scripting examples with Linux-specific idioms (e.g., using awk, grep, or jq for JSON parsing).
  • Explicitly mention Linux and macOS compatibility for CLI commands and scripts.
  • Include guidance for using CLI on Linux, such as installation, environment setup, and troubleshooting.
  • Add examples using Linux-native tools for CSV handling (e.g., csvkit, cut, awk) and scripting.
  • Reference cross-platform editors and environments (e.g., VS Code, nano, vim) when discussing script editing.
  • Clarify that all Azure CLI commands are supported on Linux, macOS, and Windows, and provide links to platform-specific documentation.
GitHub Create Pull Request
Storage Configure passwordless connections between multiple services ...articles/storage/common/multiple-identity-scenarios.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a subtle Windows bias by referencing Windows-centric tools (Visual Studio) and patterns (Azure portal UI, role assignment via portal), and by mentioning Windows development environments and tools before Linux equivalents. There are no explicit Linux-specific examples or CLI instructions for role assignment, and local development guidance is focused on Windows tools. The documentation does not provide parity for Linux users in terms of command-line or automation approaches, nor does it mention Linux-specific developer environments.
Recommendations
  • Add Azure CLI and/or PowerShell command examples for role assignment and managed identity configuration, alongside portal instructions.
  • Explicitly mention and provide examples for Linux-based local development environments (e.g., VS Code, Azure CLI on Linux, Bash shell).
  • Include instructions for configuring environment variables and credentials in Linux shells (e.g., Bash, Zsh), not just through Windows tools.
  • Ensure that references to developer tools (e.g., Visual Studio) are balanced with Linux-friendly alternatives (e.g., VS Code, JetBrains Rider).
  • Where screenshots are used, consider including both Windows and Linux UI variants, or clarify that the portal is OS-agnostic.
  • Add troubleshooting tips for Linux users, such as permissions, environment setup, and differences in credential handling.
GitHub Create Pull Request
Storage Create an Azure storage account ...main/articles/storage/common/storage-account-create.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation demonstrates a moderate Windows bias. PowerShell is consistently presented as a primary method for scripting and automation, with detailed examples and instructions. References to PowerShell modules, installation, and usage are prominent throughout, often before or alongside Azure CLI (which is cross-platform but Windows-centric in some explanations). The documentation refers to 'local installation' without clarifying platform differences, and PowerShell is treated as a default scripting environment. There is little explicit mention of Linux-specific tools, shell environments, or platform nuances, and no examples using native Linux tools or shell scripting beyond Azure CLI.
Recommendations
  • Clarify that Azure CLI is fully supported on Linux and macOS, and provide explicit instructions for installing and running CLI commands on those platforms.
  • Add examples using Bash shell scripting for Linux/macOS users, especially for automation tasks currently shown only in PowerShell.
  • Where PowerShell is referenced, note its availability on Linux and macOS, or provide alternative Bash equivalents.
  • Avoid language that implies PowerShell is the default or preferred scripting tool; present Azure CLI and PowerShell as equal options.
  • Include troubleshooting or environment setup notes for Linux users, such as file permissions, shell differences, or package manager instructions.
  • Where 'local installation' is discussed, specify platform-specific steps (e.g., apt-get/yum for Linux, Homebrew for macOS, MSI for Windows).
GitHub Create Pull Request
Storage Upgrade to a general-purpose v2 storage account ...ain/articles/storage/common/storage-account-upgrade.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 Windows bias by providing PowerShell instructions and references before Azure CLI examples, and by mentioning PowerShell as a primary upgrade method. The PowerShell section includes installation guidance, while the Azure CLI section is less detailed. There is no mention of Linux-specific tools, shell environments, or parity for Linux users beyond the CLI. The documentation assumes familiarity with Windows tooling and patterns, potentially disadvantaging Linux users.
Recommendations
  • Provide Bash and Linux shell examples alongside PowerShell, especially for Azure CLI usage.
  • Explicitly mention that Azure CLI commands work cross-platform (Windows, Linux, macOS) and provide shell-specific instructions if needed.
  • Include installation instructions for Azure CLI on Linux and macOS, not just a generic link.
  • Avoid listing PowerShell before CLI unless there is a technical reason; consider presenting CLI first for broader platform compatibility.
  • Reference Linux-native tools or environments where appropriate, and clarify that all steps are platform-agnostic unless otherwise stated.
GitHub Create Pull Request
Storage Permitted scope for copy operations (preview) ...es/storage/common/security-restrict-copy-operations.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation provides configuration instructions for the Azure portal, PowerShell, and Azure CLI, but the PowerShell section is presented before the Azure CLI section. PowerShell is primarily a Windows tool, and no explicit Linux shell examples (such as Bash or scripting with curl) are given. The CLI section does not mention Linux usage or provide Linux-specific notes, and there are no examples using Linux-native tools or workflows. This ordering and tool selection may signal a Windows-centric bias.
Recommendations
  • Present Azure CLI instructions before PowerShell, as CLI is cross-platform and more commonly used on Linux.
  • Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows.
  • Add Linux/Bash examples for REST API calls (e.g., using curl) to configure AllowedCopyScope.
  • Include notes or examples for Linux administrators, such as using AzCopy on Linux or scripting with Bash.
  • Clarify that PowerShell Core is available on Linux, if PowerShell examples are retained, and provide installation guidance for Linux users.
GitHub Create Pull Request
Storage Get storage account configuration information ...in/articles/storage/common/storage-account-get-info.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation consistently presents PowerShell examples alongside Azure CLI and portal instructions, with PowerShell often mentioned before Azure CLI. PowerShell is a Windows-centric tool, and there are no explicit Linux shell (bash) or cross-platform scripting examples. The documentation does not mention Linux-specific tools or patterns, nor does it clarify the cross-platform nature of Azure CLI. This results in a subtle bias toward Windows users and workflows, potentially making the content less accessible to Linux administrators.
Recommendations
  • Add explicit bash (Linux shell) examples for each operation, demonstrating use of Azure CLI in a Linux environment.
  • Clarify that Azure CLI is cross-platform and can be used on Windows, Linux, and macOS.
  • Where PowerShell is presented, also show equivalent bash scripting for Linux users.
  • Avoid presenting PowerShell before Azure CLI unless there is a technical reason; consider alternating or prioritizing CLI for cross-platform parity.
  • Mention Linux tools or scripting environments where relevant, and provide guidance for Linux users (e.g., installation instructions for Azure CLI on Linux).
GitHub Create Pull Request
Storage Azure Storage Analytics logging ...n/articles/storage/common/storage-analytics-logging.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates a bias toward Windows environments. PowerShell is the only command-line example provided for interacting with Storage Analytics logs, with no equivalent Bash, Azure CLI, or Linux shell example. References to tools and user agents in log samples (e.g., 'win32', 'Windows_NT') and mentions of 'PowerShell' and Windows-based tools (Azure Storage Explorer, AzCopy for Windows) are prevalent. There is no explicit guidance or examples for Linux users, and Windows-centric tools and patterns are mentioned before any cross-platform alternatives.
Recommendations
  • Add Azure CLI and Bash examples for listing and filtering log blobs, alongside PowerShell.
  • Include references and examples for Linux and macOS environments, such as using AzCopy on Linux, or using REST API calls via curl.
  • Ensure that tool mentions (Azure Storage Explorer, AzCopy) clarify their cross-platform availability and provide usage instructions for Linux/macOS.
  • Balance log entry examples to include user agents from Linux/macOS environments, not just Windows.
  • Explicitly state that all operations can be performed from Linux and macOS, and provide links to relevant cross-platform documentation.
GitHub Create Pull Request
Storage Azure storage disaster recovery planning and failover ...s/storage/common/storage-disaster-recovery-guidance.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias primarily through its repeated mention of Windows-centric tools (AzCopy, Azure PowerShell) for data copy and disaster recovery operations, without providing equivalent Linux or cross-platform examples. References to Azure PowerShell are made before or alongside AzCopy, but there is no mention of CLI commands or scripts for Linux users (e.g., Azure CLI, Bash). This may make the documentation less accessible or actionable for users operating in Linux environments.
Recommendations
  • Include Azure CLI examples for all operations currently shown with Azure PowerShell, as Azure CLI is cross-platform and widely used on Linux.
  • Explicitly mention that AzCopy is available for Linux, macOS, and Windows, and provide installation and usage instructions for Linux.
  • Add Bash script examples for common tasks, such as copying data or checking sync status, to complement PowerShell examples.
  • When listing tools, present cross-platform options first (e.g., AzCopy, Azure CLI), and clarify platform-specific details where relevant.
  • Review all references to PowerShell and ensure that equivalent Linux instructions (Azure CLI, Bash) are present and easy to find.
GitHub Create Pull Request
Storage Install and run the Azurite emulator for Azure Storage ...ain/articles/storage/common/storage-install-azurite.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by prioritizing Windows-centric tools (Visual Studio, Visual Studio Code), referencing Windows file paths (e.g., c:\azurite), and providing examples and instructions almost exclusively for Windows environments. There is a lack of explicit Linux/macOS instructions, examples, or file path formats, and no mention of Linux-specific considerations for running Azurite (such as permissions, typical installation directories, or shell commands). The Visual Studio section is entirely Windows-focused, and even Docker examples use Windows-style paths.
Recommendations
  • Add Linux/macOS-specific instructions and examples for installing and running Azurite, including shell commands and typical file paths (e.g., /home/user/azurite).
  • Include screenshots or terminal outputs from Linux/macOS environments where appropriate.
  • For Docker examples, show both Windows (c:/azurite) and Linux (-v ~/azurite:/data) volume mount syntax.
  • Clarify that Visual Studio is Windows-only and provide equivalent workflows for Linux/macOS users (e.g., using VS Code, npm, or Docker).
  • Ensure all command-line examples use cross-platform path formats or provide alternatives for each OS.
  • Explicitly mention OS-specific prerequisites and troubleshooting tips (e.g., permissions, firewall, port usage) for Linux/macOS.
GitHub Create Pull Request
Storage Initiate a storage account failover ...es/storage/common/storage-initiate-account-failover.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 demonstrates a moderate Windows bias: PowerShell is given a prominent and detailed section, with step-by-step installation and troubleshooting guidance, while Linux-specific considerations are not addressed. The PowerShell section precedes the Azure CLI section, and installation instructions reference Windows-centric tools and workflows. There is no mention of Bash, Linux shell, or cross-platform scripting nuances, and no explicit Linux command-line examples or troubleshooting tips are provided.
Recommendations
  • Add explicit Linux/Bash installation and usage instructions for the Azure CLI, including common package managers (apt, yum, etc.) and troubleshooting tips for Linux environments.
  • Include notes on cross-platform compatibility for both PowerShell (e.g., PowerShell Core on Linux/macOS) and Azure CLI, clarifying any differences or prerequisites.
  • Provide example commands and troubleshooting steps for Linux users, such as verifying CLI extension installation paths, handling permissions, or using environment variables.
  • Reorder the command-line sections to present Azure CLI before PowerShell, as Azure CLI is platform-agnostic and more commonly used on Linux.
  • Where PowerShell is discussed, mention that it is available cross-platform, and provide links or examples for installing PowerShell Core on Linux/macOS.
  • Add a brief section or callout highlighting that all command-line operations can be performed from Linux, macOS, or Windows, and link to relevant cross-platform documentation.
GitHub Create Pull Request
Storage Introduction to Azure Storage - Cloud storage on Azure ...b/main/articles/storage/common/storage-introduction.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 page demonstrates a moderate Windows bias. Windows tools and patterns (such as PowerShell and SMB) are mentioned before their Linux equivalents, and scripting examples reference Azure PowerShell and CLI together, but PowerShell is listed first throughout. The SMB protocol (Windows-centric) is described in detail, with NFS (Linux-centric) mentioned secondarily. There are no explicit Linux shell or scripting examples, nor are Linux-specific tools or workflows highlighted. The documentation references mounting file shares on Windows, Linux, and macOS, but examples and instructions are not provided for Linux. The tools section lists PowerShell first, and AzCopy and Storage Explorer are described as cross-platform, but no Linux command-line examples are given.
Recommendations
  • Provide explicit Linux shell (bash) examples alongside PowerShell, especially for common tasks such as mounting shares, scripting with Azure CLI, and data transfer.
  • List Azure CLI before PowerShell when describing cross-platform scripting, as CLI is natively cross-platform.
  • Offer Linux-specific instructions for mounting Azure Files (e.g., using mount.cifs or mount.nfs), including sample commands.
  • Highlight Linux-compatible tools and workflows, such as AzCopy usage in bash, and provide sample commands.
  • Ensure protocol documentation (SMB/NFS) gives equal detail and prominence to Linux/NFS scenarios.
  • Where authentication and identity integration are discussed, include Linux Active Directory integration and Kerberos instructions.
GitHub Create Pull Request
Storage Create an IP network rule for Azure Storage ...ge/common/storage-network-security-ip-address-range.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 Tools Windows First
Summary
The documentation provides detailed instructions for creating IP network rules for Azure Storage using the Azure Portal, PowerShell, and Azure CLI. PowerShell, a Windows-centric tool, is given a dedicated section with extensive examples, and is presented before the Azure CLI, which is cross-platform. There are no explicit Linux shell or scripting examples, nor is there mention of Linux-specific tools or patterns. The documentation implicitly prioritizes Windows tooling and patterns, which may disadvantage Linux users.
Recommendations
  • Add Bash shell script examples for Azure CLI commands to demonstrate usage on Linux/macOS.
  • Explicitly mention that Azure CLI is cross-platform and provide installation instructions for Linux/macOS alongside Windows.
  • Consider including examples using REST API or SDKs (Python, Java, etc.) that are platform-agnostic.
  • Reorder the command-line sections to present Azure CLI before PowerShell, emphasizing cross-platform accessibility.
  • Add a note clarifying that PowerShell Core is available on Linux/macOS, if PowerShell examples are retained.
GitHub Create Pull Request
Storage Use private endpoints ...n/articles/storage/common/storage-private-endpoints.md
High Priority View Details →
Scanned: 2026-01-10 00:00
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 referencing PowerShell and Azure CLI as the only command-line options for creating private endpoints, with PowerShell mentioned before CLI. There are no explicit Linux shell (bash) examples, nor are Linux-specific tools or patterns discussed. The documentation does not mention cross-platform command-line usage or provide parity for Linux users, such as bash scripts or Linux-native tools.
Recommendations
  • Provide explicit bash examples for creating private endpoints using Azure CLI, demonstrating usage on Linux and macOS.
  • Mention that Azure CLI is cross-platform and can be used on Windows, Linux, and macOS, and provide installation instructions for each.
  • Add references to Linux-native tools (e.g., curl for REST API calls) where appropriate.
  • Ensure that PowerShell is not presented as the default or primary automation tool; alternate examples should be given equal prominence.
  • Clarify that AzCopy and Storage Explorer are available on multiple platforms, and provide usage examples for Linux.
  • Where portal instructions are given, note that the Azure portal is accessible from any OS with a web browser.
GitHub Create Pull Request
Storage Azure Storage migration tools selection guide ...ain/articles/storage/common/storage-migration-tools.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 page exhibits a Windows bias in several areas: Windows-centric tools and scenarios (such as Azure File Sync for Windows file servers) are described in detail and introduced before Linux/NFS equivalents. Windows protocols (SMB) and tools (Robocopy, PowerShell) are mentioned more frequently and with more context than Linux alternatives (Rsync, NFS), which are only briefly referenced in tables or as secondary options. Example workflows and migration scenarios are focused on Windows environments, with limited guidance for Linux users. There is a lack of Linux-specific migration walkthroughs, troubleshooting, or parity in example scripts.
Recommendations
  • Provide equal, detailed examples for Linux/NFS migration scenarios, including step-by-step guides and troubleshooting.
  • Introduce Linux tools (e.g., Rsync, DistCP) and Linux-based migration patterns earlier and with the same prominence as Windows tools.
  • Add example scripts and workflows using Bash, Linux CLI, and Linux-native tools for common migration scenarios.
  • Explicitly mention Linux server support and best practices for hybrid and cloud migrations, including metadata and permission handling.
  • Ensure parity in protocol coverage (NFS, POSIX) and clarify limitations or differences for Linux users.
  • Include references to Linux documentation, community tools, and open-source migration utilities where appropriate.
GitHub Create Pull Request
← Previous Page 12 of 67 Next →