Storage

1359
Total Pages
1162
Linux-Friendly Pages
197
Pages with Bias
14.5%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

392 issues found
Showing 176-200 of 392 flagged pages
Storage Authorize access to queues using Active Directory ...rage/queues/authorize-access-azure-active-directory.md
Medium Priority View Details →
Scanned: 2026-01-12 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 moderate Windows bias. It repeatedly references PowerShell and the Azure portal (both Windows-centric tools) before mentioning Azure CLI, and does not provide explicit Linux/macOS examples or guidance. There are no references to Linux-specific tools, shell environments, or cross-platform command-line usage patterns. The lack of Linux/macOS examples may create friction for non-Windows users.
Recommendations
  • Provide explicit Linux/macOS examples for command-line operations, including sample bash/zsh commands.
  • Clarify that Azure CLI is cross-platform and provide usage instructions for Linux/macOS environments.
  • Include screenshots or walkthroughs for Linux/macOS terminals where relevant.
  • Avoid listing PowerShell before Azure CLI, or present both equally with clear cross-platform guidance.
  • Mention installation and authentication steps for Azure CLI on Linux/macOS.
GitHub Create Pull Request
Storage Performance and scalability checklist for Queue Storage ...ticles/storage/queues/storage-performance-checklist.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation references Windows-centric tools (e.g., Network Monitor) and omits Linux/macOS equivalents. In the 'Networking' section, troubleshooting tools are listed as 'Wireshark or Network Monitor', with Network Monitor being a Windows-only tool and no mention of Linux alternatives like tcpdump or iftop. The checklist and examples do not provide Linux-specific guidance or parity for configuration and troubleshooting. Additionally, examples and configuration guidance are .NET/Windows-focused, with only generic advice for other platforms.
Recommendations
  • When mentioning troubleshooting tools, include Linux/macOS equivalents (e.g., tcpdump, iftop, netstat) alongside Windows tools.
  • Provide explicit examples or links for configuring connection limits and thread pools in popular Linux/macOS programming environments (e.g., Python, Java, Node.js).
  • Ensure that cross-platform tools (e.g., Azure CLI) are highlighted equally with PowerShell, and provide usage examples for both.
  • Avoid listing Windows tools or patterns first; present cross-platform options or alternate between platforms.
  • Add a section or callout for Linux/macOS users with relevant performance tips and configuration advice.
GitHub Create Pull Request
Storage Migrate data to Azure with Atempo Miria ...d-partners/data-management/atempo-quick-start-guide.md
Medium Priority View Details →
Scanned: 2026-01-12 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 notable Windows bias. The only example for source storage migration is from a Windows file server using SMB/CIFS, with no mention of Linux or NFS sources. Data Mover selection and configuration examples reference Windows platforms (e.g., WIN-H9K5NN91J0H), and the protocol selection is limited to Windows (CIFS). Additionally, the network monitoring tools listed (SolarWinds, Paessler PRTG, Cisco Network Assistant, WhatsUp Gold) are predominantly Windows-centric, with no Linux-native alternatives suggested. There are no Linux or macOS-specific instructions, examples, or parity in the migration workflow.
Recommendations
  • Add examples for migrating from Linux file servers, including NFS protocol configuration in Miria.
  • Show how to configure Miria Data Movers running on Linux platforms, with screenshots and step-by-step instructions.
  • Include Linux-native network monitoring tools (e.g., iftop, nload, vnstat, iperf) in the bandwidth assessment section.
  • Clarify platform support and provide links or references to Miria documentation for Linux/macOS deployments.
  • Present examples and screenshots for both Windows and Linux environments, or clearly indicate cross-platform applicability.
GitHub Create Pull Request
Storage Back up your data to Azure with DobiProtect ...-disaster-recovery/datadobi/datadobi-solution-guide.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows/Azure portal bias by exclusively providing instructions and screenshots for the Azure Portal (a web GUI), with no mention of Linux/macOS command-line alternatives (such as Azure CLI, azcopy, or REST API usage). There are no examples or guidance for users who prefer or require CLI-based workflows, which are common in Linux environments. All operational and setup steps are described in terms of portal navigation, and no PowerShell or Windows-specific tools are mentioned, but the lack of Linux parity is notable.
Recommendations
  • Add equivalent instructions for performing all key steps (creating storage accounts, containers, managing access keys, etc.) using the Azure CLI and/or REST API.
  • Include example commands for azcopy, which is cross-platform and widely used for bulk data transfer to Azure Blob Storage.
  • Explicitly mention that all steps can be performed from Linux/macOS environments using CLI tools, and provide links to relevant documentation.
  • Where screenshots are used, consider including CLI output examples or terminal screenshots alongside portal images.
  • Clarify any platform-specific requirements or limitations, if any exist.
GitHub Create Pull Request
Storage Nasuni configuration guide for Microsoft Azure ...s/primary-secondary-storage/nasuni-deployment-guide.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation consistently uses Windows terminology (e.g., 'Windows Azure Platform'), shows screenshots from the Azure portal on Windows, and refers to Windows-specific naming conventions. There are no CLI, PowerShell, or Linux/macOS command-line examples, nor any mention of Linux tools or workflows. The guide assumes GUI usage and Windows-centric patterns, making it less accessible for Linux/macOS administrators who may prefer or require CLI or automation approaches.
Recommendations
  • Add equivalent Azure CLI and/or PowerShell examples for all major steps, including storage account creation, firewall configuration, and credential retrieval.
  • Include Linux/macOS-specific instructions or notes, such as how to perform tasks using the Azure CLI on those platforms.
  • Use more platform-neutral terminology (e.g., 'Azure Platform' instead of 'Windows Azure Platform') where possible.
  • Provide screenshots or walkthroughs for non-Windows environments, or clarify that the Azure portal is accessible from any OS.
  • Explicitly mention that all steps can be performed from Linux/macOS using the Azure CLI or portal, and link to relevant Azure CLI documentation.
GitHub Create Pull Request
Storage Considerations for running ISV file services in Azure ...artners/primary-secondary-storage/isv-file-services.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page exhibits a moderate Windows bias. Several ISV solutions (Tiger Technology, XenData) are described as relying on Windows Server or NTFS, and features like 'Windows Shell integration' are highlighted. The operating environment and failover features for some solutions are Windows-centric, with no equivalent Linux details or parity. Example use cases and management features (e.g., file locking, VDI, Windows cluster failover) are often described in Windows terms, and Linux-specific deployment or management patterns are not discussed. No Linux/macOS-specific examples, tools, or deployment instructions are provided, and Windows terminology appears first or exclusively in some sections.
Recommendations
  • Add explicit Linux/macOS deployment examples and management instructions for each ISV solution where supported.
  • Highlight Linux-compatible features and environments in the comparison tables (e.g., mention Linux clustering, Linux file systems, Linux shell integration, etc.).
  • Where Windows-specific features (e.g., NTFS tiering, Windows Shell integration, Windows cluster failover) are mentioned, clarify if and how similar functionality is available for Linux/macOS users.
  • Include Linux/macOS use cases and workflows in the example use cases section.
  • Ensure parity in terminology and ordering (e.g., mention Linux environments alongside Windows, and avoid listing Windows features first unless justified by market share).
GitHub Create Pull Request
Storage Known issues with Azure Data Lake Storage ...ticles/storage/blobs/data-lake-storage-known-issues.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 Tools Windows Terms
Summary
The documentation references PowerShell and Windows-specific terminology (e.g., WASB driver, Windows Azure Storage Blob) and tools (PowerShell, Azure Storage Explorer) without providing equivalent Linux/macOS examples or alternatives. PowerShell is mentioned for restoring soft-deleted blobs, but Linux/macOS alternatives (such as Bash or shell scripts) are not explicitly referenced. The WASB driver is discussed, which is Windows-centric, though the ABFS driver is recommended for Hadoop environments. Overall, the documentation assumes familiarity with Windows tools and patterns, potentially creating friction for Linux/macOS users.
Recommendations
  • Provide explicit Linux/macOS command-line examples (e.g., Bash, shell, or Azure CLI) wherever PowerShell is referenced.
  • Clarify that Azure Storage Explorer and AzCopy are cross-platform, and provide installation/use instructions for Linux/macOS.
  • When referencing drivers or APIs with Windows-centric names (e.g., WASB), clarify their relevance or alternatives for non-Windows environments.
  • Add a section or callouts for Linux/macOS users, highlighting any differences or additional steps required.
GitHub Create Pull Request
Storage Perform a point-in-time restore on block blob data ...articles/storage/blobs/point-in-time-restore-manage.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 🔧 Windows Tools
Summary
The documentation provides examples for Azure portal, PowerShell, and Azure CLI. PowerShell examples are detailed and prominent, and PowerShell is a Windows-centric tool. PowerShell examples are consistently presented before Azure CLI, which is more cross-platform. There are no Linux/macOS-specific shell examples (e.g., Bash), nor is there mention of Linux-specific tooling or considerations. The documentation assumes familiarity with PowerShell and Windows patterns, which may create friction for Linux/macOS users.
Recommendations
  • Present Azure CLI examples before PowerShell examples, as CLI is cross-platform and more familiar to Linux/macOS users.
  • Add explicit Bash shell examples for Azure CLI commands, including variable assignment and command chaining, to demonstrate usage in Linux/macOS environments.
  • Clarify that PowerShell is available cross-platform, but note that Azure CLI is often preferred on Linux/macOS.
  • Include troubleshooting or environment setup notes for Linux/macOS users (e.g., installation instructions for Azure CLI on Linux/macOS).
  • Avoid language or patterns that assume a Windows environment (e.g., referencing Windows-specific paths or behaviors).
GitHub Create Pull Request
Storage Enable and manage blob versioning .../blob/main/articles/storage/blobs/versioning-enable.md
Medium 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 PowerShell examples and references before Azure CLI in each section, and provides detailed PowerShell instructions. While Azure CLI examples are present (which are cross-platform), there are no explicit Linux/macOS shell examples or notes. The use of PowerShell as a primary scripting example may create friction for Linux/macOS users unfamiliar with it.
Recommendations
  • Present Azure CLI examples before PowerShell, as CLI is cross-platform and more familiar to Linux/macOS users.
  • Add explicit bash/shell script examples for Linux/macOS users, especially for variable assignment and command usage.
  • Include notes clarifying that Azure CLI works on Linux/macOS and provide installation links for those platforms.
  • Avoid assuming PowerShell as the default scripting environment; mention alternatives for non-Windows users.
GitHub Create Pull Request
Storage Change how a storage account is replicated ...b/main/articles/storage/common/redundancy-migration.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation consistently presents Windows-centric tools and patterns first, notably PowerShell, and provides detailed PowerShell scripts for batch operations. While Azure CLI examples are included (which are cross-platform), the scripting and automation guidance is richer for PowerShell, and CSV file paths use Windows-style syntax. There is no mention of Linux/macOS-specific shell scripting, nor are Bash or other Unix-native tools referenced. The portal instructions are platform-neutral, but the overall tone and example ordering favor Windows users.
Recommendations
  • Provide Bash shell script equivalents for batch operations using Azure CLI, with Unix-style CSV file paths and parsing.
  • Explicitly mention that Azure CLI is cross-platform and can be used on Linux/macOS.
  • Add notes or examples for Linux/macOS users, such as using Bash, zsh, or other common shells for scripting.
  • Ensure file path examples use both Windows and Unix formats, or use platform-neutral syntax.
  • Consider including a section or callout for Linux/macOS users to clarify parity and any platform-specific caveats.
GitHub Create Pull Request
Storage Determine which encryption key model is in use for the storage account ...les/storage/common/storage-encryption-key-model-get.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides three methods to check the encryption key model: Azure portal, PowerShell, and Azure CLI. PowerShell is featured as a primary command-line example, which is Windows-centric. The PowerShell section appears before the Azure CLI section, which is more cross-platform friendly. No Linux/macOS-specific shell examples (e.g., Bash) are provided, and no mention is made of platform differences or requirements for PowerShell on non-Windows systems.
Recommendations
  • Present Azure CLI examples before PowerShell, as CLI is cross-platform and more accessible to Linux/macOS users.
  • Explicitly mention that PowerShell is primarily available on Windows, and provide guidance or links for installing PowerShell on Linux/macOS if relevant.
  • Add Bash or shell script examples for Linux/macOS users, or clarify that Azure CLI commands work natively in those environments.
  • Include a brief note about platform compatibility for each method.
GitHub Create Pull Request
Storage AzCopy v10 configuration setting (Azure Storage) ...ge/common/storage-ref-azcopy-configuration-settings.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
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 moderate Windows bias. Windows is frequently mentioned first in command tables, and PowerShell/CMD examples are given in detail, while Linux/macOS receive only basic 'export' examples. Proxy configuration and bypass instructions are detailed for Windows (CMD and PowerShell), but Linux/macOS instructions are minimal or absent. Several environment variable descriptions reference Windows-specific behavior or defaults, such as proxy auto-detection and event logging. There is limited discussion of Linux/macOS-specific patterns or troubleshooting.
Recommendations
  • Present Linux/macOS examples before or alongside Windows examples in command tables.
  • Provide equivalent detailed instructions for Linux/macOS, especially for proxy bypass (e.g., how to unset HTTPS_PROXY and NO_PROXY).
  • Include notes on Linux/macOS-specific logging and proxy behaviors, not just Windows Event Log/Syslog.
  • Clarify any platform-specific defaults or behaviors for all OSes, not just Windows.
  • Add troubleshooting tips for Linux/macOS environments where relevant.
GitHub Create Pull Request
Storage Synchronize with Azure Blob storage by using AzCopy v10 ...storage/common/storage-use-azcopy-blobs-synchronize.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page provides AzCopy sync examples using Windows-style paths (e.g., 'C:\myDirectory') and does not include equivalent Linux/macOS path examples (e.g., '/home/user/myDirectory'). The tips on quoting paths mention Windows Command Shell (cmd.exe) but do not provide explicit Linux/macOS shell examples or usage patterns. All local path examples use Windows conventions, which may confuse or inconvenience Linux/macOS users.
Recommendations
  • Include Linux/macOS path examples alongside Windows examples, such as '/home/user/myDirectory' or '~/myDirectory'.
  • Explicitly show command syntax and examples for Bash/zsh shells, including correct quoting and escaping practices.
  • Add a section or note clarifying cross-platform differences in path formats and shell usage.
  • Ensure that examples alternate or equally represent both Windows and Linux/macOS environments.
GitHub Create Pull Request
Storage Upload files to Azure Blob storage by using AzCopy v10 ...cles/storage/common/storage-use-azcopy-blobs-upload.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation consistently uses Windows-style paths (e.g., 'C:\myDirectory\myTextFile.txt') in all examples and does not provide any Linux/macOS path examples (e.g., '/home/user/myTextFile.txt'). While there are notes about quoting conventions for different shells, the actual examples are exclusively Windows-centric, which may confuse or inconvenience Linux/macOS users.
Recommendations
  • Provide equivalent Linux/macOS examples for each Windows example, using POSIX-style paths (e.g., '/home/user/myTextFile.txt').
  • Alternate the order of examples or present both Windows and Linux/macOS examples side-by-side.
  • Explicitly mention that the examples are Windows-specific and direct Linux/macOS users to adapt paths accordingly.
  • Include a section or table summarizing path and quoting differences across platforms.
GitHub Create Pull Request
Storage Azure File Sync resource moves and topology changes .../articles/storage/file-sync/file-sync-resource-move.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 Tools Missing Linux Example
Summary
The documentation page provides a PowerShell-only example for reassigning managed identities after a resource move, with no equivalent CLI or Linux/macOS instructions. The use of PowerShell and references to Windows-centric tooling (e.g., PowerShell cmdlets) create friction for Linux/macOS administrators. No Bash, Azure CLI, or cross-platform alternatives are mentioned, and the example assumes access to PowerShell, which is most common on Windows.
Recommendations
  • Provide equivalent Azure CLI or Bash examples for all PowerShell commands, especially for managed identity and RBAC operations.
  • Explicitly mention that PowerShell Core is available cross-platform, or link to instructions for installing it on Linux/macOS if PowerShell is required.
  • Where possible, use Azure CLI as the primary example, as it is natively cross-platform.
  • Add notes or sections for Linux/macOS users, clarifying any differences in workflow or prerequisites.
  • Ensure screenshots and step-by-step instructions in the Azure portal do not assume a Windows environment.
GitHub Create Pull Request
Storage Migrate to SMB Azure file shares using Azure Storage Mover .../articles/storage/files/migrate-files-storage-mover.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page exhibits moderate Windows bias. Windows tools like Robocopy are mentioned as migration alternatives, and the examples and migration context focus on SMB shares, which are most commonly associated with Windows environments. There is no explicit Linux example or guidance, and Windows-centric migration tools are referenced before any Linux equivalents. While the documentation states that Linux SMB shares are supported, practical steps, troubleshooting, or examples for Linux users are missing.
Recommendations
  • Include explicit Linux SMB source examples, such as mounting SMB shares on Linux and configuring permissions.
  • Mention and compare Linux migration tools (e.g., rsync, smbclient) alongside Robocopy, even if only for context.
  • Add troubleshooting tips for common Linux SMB migration issues (e.g., SELinux, file permissions, character encoding).
  • Provide step-by-step instructions or screenshots for Linux environments where appropriate.
  • Clarify agent deployment requirements for Linux VMs, if supported, or state limitations.
GitHub Create Pull Request
Storage Analyze Azure Files metrics with Azure Monitor ...b/main/articles/storage/files/analyze-files-metrics.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation provides detailed PowerShell examples for metric analysis, with PowerShell presented before Azure CLI. While Azure CLI commands are included (which work cross-platform), there are no explicit Linux/macOS shell examples (e.g., Bash), nor any mention of Linux-specific tools or workflows. The troubleshooting link references Windows tabs, and screenshots and context often assume a Windows-centric environment (e.g., SMB focus, on-premises client examples). There is no discussion of Linux NFS scenarios or parity for Linux users in scripting or automation.
Recommendations
  • Add explicit Bash shell examples for metric queries using Azure CLI, demonstrating usage on Linux/macOS.
  • Include references to Linux-specific monitoring tools or workflows (e.g., integration with cron, systemd, or third-party Linux monitoring solutions).
  • Ensure troubleshooting links and examples include Linux/macOS tabs or instructions, not just Windows.
  • Discuss NFS scenarios and how Linux users can monitor NFS shares with Azure Monitor.
  • Balance the order of examples, presenting Azure CLI (cross-platform) before PowerShell, or side-by-side.
GitHub Create Pull Request
Storage Authorize access to blobs using Microsoft Entra ID ...orage/blobs/authorize-access-azure-active-directory.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. It repeatedly references PowerShell and the Azure portal (both Windows-centric tools) as primary methods for accessing blob data, often mentioning PowerShell before Azure CLI. There are no explicit Linux/macOS examples or references to platform-specific usage, and no mention of Linux-native tools or shell environments. The page does not provide parity in examples or guidance for Linux/macOS users, relying on Windows-oriented workflows.
Recommendations
  • Provide explicit Linux/macOS examples, such as bash shell commands using Azure CLI.
  • Mention cross-platform compatibility of Azure CLI and provide installation links for Linux/macOS.
  • Balance references to PowerShell and Azure CLI, ensuring CLI examples are shown first or equally.
  • Include notes about using the Azure portal from non-Windows platforms (browser-based access).
  • Add troubleshooting or environment setup guidance for Linux/macOS users.
GitHub Create Pull Request
Storage Manage block blobs with Azure CLI ...zure-docs/blob/main/articles/storage/blobs/blob-cli.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a subtle Windows bias in its code examples and instructions. Although all CLI examples use Bash syntax, file paths in upload, download, and XML parsing examples consistently use Windows-style paths (e.g., C:\temp\), and instructions for creating required files reference Windows directories. There are no explicit Linux/macOS file path examples, nor are Linux-specific considerations (such as permissions or alternate locations) mentioned. This may cause confusion or friction for Linux/macOS users, who must adapt the examples to their environments.
Recommendations
  • Provide both Windows and Linux/macOS file path examples in code snippets (e.g., use /tmp/ or ~/temp/ alongside C:\temp\).
  • Explicitly mention that file paths must be adapted to the user's OS, and provide guidance for Linux/macOS users.
  • When referencing file creation or manipulation (e.g., blob-list.xml), include Linux/macOS directory alternatives.
  • Add notes or callouts where OS-specific behavior may differ (e.g., path separators, permissions).
  • Ensure that sample code does not assume Windows-only conventions, especially in introductory or critical sections.
GitHub Create Pull Request
Storage Filter data by using Azure Data Lake Storage query acceleration ...e/blobs/data-lake-storage-query-acceleration-how-to.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 Tools Windows First
Summary
The documentation page provides PowerShell examples and instructions for Azure Data Lake Storage query acceleration, which are specific to Windows environments. PowerShell is presented as the only CLI scripting option, with no Bash, shell, or Linux-native CLI examples. Package installation instructions for .NET reference 'command prompt' without clarifying cross-platform support. The PowerShell tab is listed first in all code example sections, and there is no mention of Linux/macOS equivalents for scripting or CLI usage.
Recommendations
  • Add Bash or Azure CLI examples for Linux/macOS users alongside PowerShell, especially for scripting and command-line usage.
  • Clarify that .NET, Java, Python, and Node.js instructions are cross-platform, and provide explicit guidance for running these on Linux/macOS.
  • Reorder tabs so that PowerShell is not always first, or randomize tab order to avoid implicit prioritization.
  • Mention Linux/macOS alternatives for temporary file creation and content reading in scripting sections.
  • Include troubleshooting notes for common Linux/macOS issues (e.g., file permissions, path separators) where relevant.
GitHub Create Pull Request
Storage Using the HDFS CLI with Azure Data Lake Storage .../blobs/data-lake-storage-use-hdfs-data-lake-storage.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page presents a PowerShell-based SSH example for connecting to the HDInsight cluster, which is a Windows-centric approach. This example appears before any mention of Linux or macOS command-line usage, despite the fact that SSH is natively available on Unix-like systems. The remainder of the page is platform-neutral, focusing on HDFS CLI commands, but the initial connection instructions may create friction for Linux/macOS users.
Recommendations
  • Provide a Linux/macOS SSH example using native terminal commands (e.g., 'ssh sshuser@clustername-ssh.azurehdinsight.net') without referencing PowerShell.
  • Clarify that SSH is available by default on Linux/macOS and provide instructions for those platforms.
  • If mentioning PowerShell, do so after presenting the more universal SSH command, or in a dedicated Windows section.
  • Consider adding a table or section summarizing platform-specific prerequisites for HDFS CLI usage.
GitHub Create Pull Request
Storage Container-level WORM policies for immutable blob data ...orage/blobs/immutable-container-level-worm-policies.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 Tools Windows First
Summary
The documentation page demonstrates a moderate Windows bias in its examples and tool references. PowerShell commands (Remove-AzRmStorageContainer, Remove-AzStorageContainer) are mentioned first and described in detail, with only brief mention of Azure CLI as an alternative. There is no explicit Linux/macOS example or guidance, and the focus on PowerShell and Windows-centric tools may create friction for non-Windows users.
Recommendations
  • Provide explicit Azure CLI examples for all operations, especially deletion, alongside PowerShell commands.
  • Clarify cross-platform compatibility for all command-line tools mentioned (e.g., note that Azure CLI works on Linux/macOS).
  • Include bash or shell script examples where appropriate.
  • Avoid listing PowerShell commands first; alternate or parallel presentation with CLI commands improves parity.
  • Add a section or note for Linux/macOS users, highlighting any differences or confirming parity.
GitHub Create Pull Request
Storage Version-level WORM policies for immutable blob data ...storage/blobs/immutable-version-level-worm-policies.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation page exhibits a moderate Windows bias, particularly in the 'Deletion' section, where PowerShell commands (Remove-AzRmStorageContainer, Remove-AzStorageContainer) are mentioned first and in detail. While Azure CLI commands are also referenced, the PowerShell examples and terminology are presented before CLI equivalents, and no Linux/macOS-specific shell examples (e.g., Bash) are provided. The documentation does not mention platform-specific considerations for Linux/macOS users, nor does it provide parity in example scripts or command-line usage.
Recommendations
  • Provide example commands using Bash and Azure CLI for Linux/macOS users alongside PowerShell examples.
  • Explicitly state that Azure CLI is cross-platform and can be used on Windows, Linux, and macOS.
  • Avoid listing PowerShell commands before CLI commands; consider presenting CLI examples first or in parallel.
  • Include notes or links for installing and using Azure CLI on Linux/macOS.
  • Where possible, add screenshots or instructions showing the process on Linux/macOS terminals.
GitHub Create Pull Request
Storage Configure a lifecycle management policy ...storage/blobs/lifecycle-management-policy-configure.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 🔧 Windows Tools
Summary
The documentation provides detailed PowerShell examples and command breakdowns, while the Azure CLI section is much shorter and less instructive. PowerShell is presented before Azure CLI, and the PowerShell workflow is described step-by-step with variable initialization and object creation, which is typical of Windows environments. There is no mention of Linux/macOS-specific considerations, nor are shell scripting examples (bash/zsh) provided. The documentation assumes familiarity with PowerShell and Windows tooling, which may create friction for Linux/macOS users.
Recommendations
  • Provide equally detailed Azure CLI examples, including step-by-step instructions and variable usage.
  • Include bash/zsh scripting examples for Linux/macOS users, demonstrating how to build and apply lifecycle policies.
  • Explicitly mention cross-platform compatibility for CLI commands and clarify any OS-specific prerequisites.
  • Consider presenting CLI examples before PowerShell, or side-by-side, to avoid Windows-first bias.
  • Add troubleshooting notes or tips relevant to Linux/macOS environments.
GitHub Create Pull Request
Storage Monitor Azure Blob Storage ...ob/main/articles/storage/blobs/monitor-blob-storage.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides detailed examples for Azure Portal, PowerShell, Azure CLI, and .NET SDK. PowerShell examples are given before Azure CLI, which may suggest a Windows-first approach. There are no explicit Linux/macOS-specific examples or notes, but the Azure CLI commands are cross-platform. The documentation does not mention Linux tools or shell scripting, nor does it provide guidance for Bash or other Linux-native environments. The PowerShell section is more extensive, with advanced filtering examples, while the Azure CLI section is more basic.
Recommendations
  • Add Bash/shell scripting examples for metric and log queries, demonstrating usage on Linux/macOS.
  • Ensure Azure CLI examples cover advanced scenarios (e.g., metric filtering with dimensions) at parity with PowerShell.
  • Explicitly state that Azure CLI commands work on Linux/macOS and provide any necessary environment setup instructions.
  • Consider reordering examples to show Azure CLI before PowerShell, or present them side-by-side.
  • Include troubleshooting notes or tips relevant to Linux/macOS users (e.g., authentication, environment variables).
GitHub Create Pull Request
← Previous Page 8 of 16 Next →