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 1301-1325 of 1657 flagged pages
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/storage-use-azcopy-authorize-user-identity.md ...e/common/storage-use-azcopy-authorize-user-identity.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 provides both Linux and Windows examples for setting environment variables, but Windows/Powershell syntax is consistently presented alongside or immediately after Linux/bash, and PowerShell is given a dedicated section for authentication. Azure PowerShell is highlighted as a primary method for authentication, with no equivalent mention of Linux-native alternatives (e.g., bash scripting, other shells). The use of PowerShell examples and terminology may make the documentation feel Windows-centric, especially since PowerShell is not the default shell on most Linux systems.
Recommendations
  • Ensure Linux/bash examples are presented first or equally alongside Windows/PowerShell examples.
  • Add explicit instructions for common Linux shells (bash, zsh) and clarify PowerShell's availability on Linux.
  • Provide parity for Linux-native authentication workflows, such as using bash scripts or other Linux tools.
  • Clarify that Azure PowerShell is cross-platform, but also suggest alternatives for users who prefer not to install PowerShell on Linux.
  • Consider adding troubleshooting steps specific to Linux environments (e.g., handling secret stores, keyrings).
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/storage-use-azcopy-blobs-download.md ...es/storage/common/storage-use-azcopy-blobs-download.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
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 command examples and does not provide any Linux/macOS equivalents (such as '/home/user/myTextFile.txt'). While there are notes about quoting differences between shells, the examples themselves are exclusively Windows-centric, which may confuse or inconvenience Linux/macOS users.
Recommendations
  • Provide parallel examples using Linux/macOS path formats (e.g., '/home/user/myTextFile.txt') alongside Windows examples.
  • Explicitly mention and show how to run AzCopy commands in bash/zsh shells, including correct quoting and path conventions.
  • Include a section or table summarizing differences in path formats and quoting between Windows (cmd.exe, PowerShell) and Linux/macOS shells.
  • Ensure that all scenarios (single file, directory, wildcard, etc.) have both Windows and Linux/macOS command examples.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/storage-use-azcopy-blobs-upload.md ...cles/storage/common/storage-use-azcopy-blobs-upload.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
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, without providing equivalent Linux/macOS examples (e.g., '/home/user/myDirectory/myTextFile.txt'). The tips about quoting paths mention Linux shells, but all concrete command examples use Windows paths and syntax, implicitly prioritizing Windows users and omitting Linux parity.
Recommendations
  • For each example, provide both Windows and Linux/macOS versions side-by-side, using appropriate path formats (e.g., 'C:\myDirectory\file.txt' for Windows and '/home/user/myDirectory/file.txt' for Linux/macOS).
  • Explicitly state which shell each example is intended for (cmd.exe, PowerShell, bash, zsh, etc.), and clarify quoting requirements for each.
  • Add a section or note summarizing differences in path formats and shell usage across platforms.
  • Ensure that wildcard and recursive examples demonstrate Linux/macOS usage, including any differences in globbing or path separators.
  • Where relevant, mention platform-specific behaviors or limitations of AzCopy.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/storage-use-azcopy-blobs-synchronize.md ...storage/common/storage-use-azcopy-blobs-synchronize.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by exclusively using Windows-style paths (e.g., 'C:\myDirectory') in all examples and syntax sections, and by referencing Windows Command Shell (cmd.exe) specifically when discussing quoting conventions. There are no explicit Linux or macOS path examples (such as '/home/user/myDirectory'), nor is there mention of Linux-specific shell usage (e.g., bash, zsh). The guidance for quoting is Windows-centric, with Linux/Unix shells only referenced in passing.
Recommendations
  • Include Linux/macOS path examples alongside Windows examples in all relevant sections (e.g., use '/home/user/myDirectory' as an alternative to 'C:\myDirectory').
  • Explicitly mention Linux/macOS shells (bash, zsh) when discussing quoting conventions, and clarify that single quotes are standard for these environments.
  • Add a tip or note about running AzCopy on Linux/macOS, including installation and usage specifics if they differ.
  • Where possible, provide side-by-side command examples for both Windows and Linux/macOS to ensure parity and clarity for all users.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/storage-use-azcopy-v10.md ...main/articles/storage/common/storage-use-azcopy-v10.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows-first bias in its example usage and command syntax. The only explicit example command uses a Windows-style path (C:\local\path) and does not provide a Linux or macOS equivalent. Additionally, instructions for running AzCopy reference Windows command shell conventions (e.g., .\azcopy) before mentioning Linux alternatives. While installation instructions do mention Linux package managers and download links for all platforms, usage examples and command syntax are presented primarily from a Windows perspective.
Recommendations
  • Provide example commands using Linux/macOS path syntax (e.g., /home/user/path) alongside Windows examples.
  • When showing command usage, alternate or parallel Windows and Linux/macOS conventions (e.g., .\azcopy vs ./azcopy).
  • Explicitly mention Linux/macOS shell usage where relevant, such as decompressing tar files or adding executables to PATH.
  • Ensure that all example commands and instructions are platform-agnostic or include platform-specific notes.
  • Consider a table or side-by-side examples for common operations, showing both Windows and Linux/macOS syntax.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/elastic-san/elastic-san-configure-private-endpoints.md ...elastic-san/elastic-san-configure-private-endpoints.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 provides configuration examples for Azure Elastic SAN private endpoints using the Azure Portal, PowerShell, and Azure CLI. The PowerShell example is presented before the Azure CLI example, which may suggest a Windows-first bias. The PowerShell section is detailed and uses Windows-centric tooling, while the CLI section is more cross-platform. No Linux-specific tools or shell examples (e.g., bash scripts) are provided, and there is no mention of Linux-specific patterns or considerations in the configuration steps themselves. However, the CLI example is present, which mitigates some bias. The prerequisites mention both PowerShell and CLI, but PowerShell is listed first.
Recommendations
  • Present Azure CLI examples before PowerShell examples to prioritize cross-platform usage.
  • Add explicit bash script examples or notes for Linux users, especially for automation scenarios.
  • Include a brief section or note highlighting that Azure CLI works natively on Linux/macOS and is recommended for non-Windows environments.
  • Ensure that any troubleshooting or advanced configuration steps include Linux-relevant commands or considerations.
  • Balance the order and depth of PowerShell and CLI examples to avoid implying Windows is the default or preferred platform.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/elastic-san/elastic-san-delete.md ...ain/articles/storage/elastic-san/elastic-san-delete.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 demonstrates a mild Windows bias by presenting Windows/Powershell instructions and scripts before Linux equivalents in the 'Disconnect volumes from clients' section. Additionally, PowerShell examples are consistently listed before Azure CLI examples in all deletion command sections, reinforcing a Windows-first pattern. However, Linux/CLI examples are present and reasonably detailed, so parity is not severely lacking.
Recommendations
  • Alternate the order of examples so that Linux/Azure CLI instructions are presented first in some sections.
  • Explicitly state that both Windows and Linux are equally supported at the beginning of the page.
  • Where possible, provide combined or unified instructions that highlight cross-platform usage.
  • Ensure that script and command explanations are equally detailed for both platforms.
  • Consider adding a table or summary comparing Windows and Linux approaches for each major step.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/elastic-san/elastic-san-shared-volumes.md ...cles/storage/elastic-san/elastic-san-shared-volumes.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation mentions Windows Server Failover Cluster (WSFC) before Pacemaker when listing cluster managers, suggesting a Windows-first perspective. There are no concrete examples, scripts, or tool references for either Windows or Linux, but the ordering and lack of Linux-specific guidance (e.g., Pacemaker configuration, Linux SCSI-3 PR tooling) indicate a subtle Windows bias. No PowerShell commands or Windows-only tools are referenced, but Linux parity is lacking in practical guidance.
Recommendations
  • Provide explicit configuration examples for both Windows (WSFC) and Linux (Pacemaker) cluster managers.
  • Include references to Linux tools (e.g., sg_persist, scsi-reserve) for managing SCSI-3 Persistent Reservations.
  • Balance the order of cluster manager mentions or alternate between Windows and Linux in examples.
  • Add troubleshooting and best practices sections for Linux environments.
  • Ensure that any scripts or automation guidance are available for both PowerShell and Bash/shell.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/elastic-san/elastic-san-connect-aks.md ...rticles/storage/elastic-san/elastic-san-connect-aks.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 lists both Azure PowerShell and Azure CLI as prerequisites, but presents the PowerShell example before the Azure CLI example for retrieving volume information. This ordering and inclusion of PowerShell may indicate a subtle Windows-first bias, as PowerShell is primarily a Windows tool (though cross-platform now), and many Linux users would expect CLI examples to be primary. No Linux-specific tools or patterns are missing, and the rest of the instructions use platform-neutral Kubernetes and YAML manifests.
Recommendations
  • Present Azure CLI examples before Azure PowerShell examples, as CLI is more commonly used on Linux and macOS.
  • Explicitly mention that both Azure CLI and PowerShell are cross-platform, but Azure CLI is the default on Linux.
  • Consider providing only Azure CLI examples in main instructions, with PowerShell as an optional note for Windows users.
  • Add a note clarifying that all kubectl and YAML steps are platform-agnostic and work equally on Linux, macOS, and Windows.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/file-sync/file-sync-monitor-cloud-tiering.md ...s/storage/file-sync/file-sync-monitor-cloud-tiering.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation assumes the use of Windows servers and Windows-centric tools (e.g., Azure File Sync, server endpoint properties in Azure portal) without mentioning Linux support or providing Linux-specific guidance or examples. There are no references to Linux equivalents, commands, or monitoring patterns, and all terminology is oriented toward Windows environments.
Recommendations
  • Clarify platform support: Explicitly state whether Azure File Sync and cloud tiering are available for Linux servers, and if not, mention this limitation.
  • Provide Linux parity: If Linux is supported, add examples and instructions for monitoring cloud tiering from Linux servers, including relevant CLI commands, log file locations, or integration with Linux monitoring tools.
  • Mention cross-platform tools: Reference cross-platform monitoring solutions (such as Azure CLI, REST API, or third-party tools) and provide examples for both Windows and Linux.
  • Avoid Windows-only terminology: Where possible, use platform-neutral language and explain any Windows-specific concepts in terms of their Linux equivalents.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/files/files-data-protection-overview.md ...ticles/storage/files/files-data-protection-overview.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 page demonstrates a mild Windows bias by listing Azure PowerShell examples before Azure CLI and REST API, and by referencing Azure File Sync—a tool primarily designed for Windows Server environments. There is no explicit Linux example or mention of Linux-specific backup or sync tools, and the documentation does not address Linux SMB/NFS client scenarios for backup and recovery. However, Azure CLI and REST API options are included, which are cross-platform.
Recommendations
  • Add explicit Linux usage examples for backup and restore operations, such as using Azure CLI from a Linux shell.
  • Clarify Azure File Sync's Windows-centric nature and suggest Linux alternatives or note limitations for Linux file servers.
  • Include guidance for Linux administrators on mounting Azure Files via SMB/NFS and performing backup/restore operations.
  • Ensure parity in example ordering by listing CLI and REST API options before or alongside PowerShell, not after.
  • Mention any Linux-compatible third-party backup tools or scripts that integrate with Azure Files.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/files/storage-dotnet-how-to-use-files.md ...icles/storage/files/storage-dotnet-how-to-use-files.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in its examples and patterns. In the 'Work with Azure Files using System.IO' section, all code samples use Windows-style paths (e.g., Z:\file-share) and reference mounting SMB shares on Windows first, with Linux mounting links provided but not exemplified. There are no Linux-specific code examples (e.g., using /mnt/file-share or NFS paths), and all file system operations are shown with Windows conventions. The initial example for mounting and accessing shares is Windows-centric, and Linux parity is not demonstrated in code.
Recommendations
  • Add Linux-specific code examples using Linux-style paths (e.g., '/mnt/file-share') alongside Windows examples.
  • Explicitly show how to mount Azure Files shares on Linux (SMB and NFS) with example commands and code.
  • Present Windows and Linux mounting instructions and code samples side-by-side, or in parallel tabs, to avoid Windows-first ordering.
  • Discuss any platform-specific differences in file locking, ACLs, and path handling between Windows and Linux.
  • Ensure all examples referencing file shares include both Windows and Linux path formats, and clarify applicability.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/files/storage-files-identity-auth-linux-kerberos-enable.md ...s/storage-files-identity-auth-linux-kerberos-enable.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation is focused on enabling Kerberos authentication for Linux clients with Azure Files and provides thorough Linux-specific instructions and examples. However, there is evidence of Windows bias: Windows-centric terminology and tools (such as NT ACLs, DACLs, and references to updating ACLs through Windows) are used, and Windows/Active Directory concepts are presented as the default or primary model. The documentation mentions that Linux tools for updating NT ACLs are minimal and recommends updating ACLs through Windows, without providing Linux alternatives or parity. Additionally, some configuration steps reference Windows AD DS as the primary directory service, with Microsoft Entra Domain Services as a secondary option.
Recommendations
  • Provide Linux-native methods or tools for managing NT ACLs and DACLs, or explicitly document any available open-source alternatives.
  • Include more details or references for Linux tools that can update NT ACLs, even if limited, and clarify their capabilities and limitations.
  • Where Windows tools or patterns are referenced (e.g., updating ACLs), offer Linux equivalents or workarounds, or acknowledge the gap and suggest future improvements.
  • Present both Windows and Linux approaches in parallel when discussing directory services, access control, and file permissions, rather than defaulting to Windows terminology.
  • Expand the documentation to include more Linux-centric troubleshooting, best practices, and integration patterns for hybrid environments.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/queues/storage-queues-introduction.md ...articles/storage/queues/storage-queues-introduction.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page exhibits subtle Windows bias, primarily in the 'Next steps' section. The quickstart links for .NET, Java, Python, and Node.js all include tabs or references to 'environment-variable-windows' and, in the Java example, 'powershell' as a tab, but there is no mention of Linux or cross-platform equivalents. This suggests that Windows environments and tools are prioritized or assumed as the default, with no explicit parity for Linux users.
Recommendations
  • Add Linux-specific or cross-platform tabs (e.g., 'environment-variable-linux', 'bash') to all quickstart links and examples.
  • Ensure that any references to environment variables, shell commands, or setup steps include both Windows (PowerShell, CMD) and Linux (bash, sh) equivalents.
  • Review all quickstart and tutorial pages linked from this overview to ensure Linux users are equally supported and not required to adapt Windows-specific instructions.
  • Consider reordering or balancing the presentation of Windows and Linux instructions so that neither is implicitly prioritized.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/queues/storage-quickstart-queues-nodejs.md ...les/storage/queues/storage-quickstart-queues-nodejs.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation page demonstrates mild Windows bias in the 'Create the project' section, where Windows consoles (cmd, PowerShell) are mentioned before Bash, and Visual Studio Code is suggested as the editor without alternatives. No PowerShell-specific commands or Windows-only tools are used, and most instructions are cross-platform. There are no Linux-specific examples, nor is Linux tooling or workflow highlighted.
Recommendations
  • List Bash (Linux/macOS) before Windows consoles (cmd, PowerShell) or mention all platforms equally.
  • Explicitly state that all commands work in Bash, zsh, or other Linux/macOS shells.
  • Suggest alternative editors (e.g., 'Open the project in your preferred code editor, such as Visual Studio Code, Sublime Text, or Vim').
  • Add a note clarifying that the instructions are platform-agnostic and work on Windows, Linux, and macOS.
  • Where environment variables are discussed, mention platform-specific syntax (e.g., 'export' for Linux/macOS, 'set' for Windows).
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/solution-integration/validated-partners/backup-archive-disaster-recovery/commvault/commvault-solution-guide.md ...isaster-recovery/commvault/commvault-solution-guide.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by exclusively referencing the Azure portal UI for all configuration and operational steps, without mentioning or providing examples for Linux CLI tools (such as Azure CLI or PowerShell Core on Linux). All step-by-step instructions assume a graphical interface typical of Windows environments, and no Linux-specific guidance or parity is offered for users who may prefer or require command-line or automation approaches on Linux systems.
Recommendations
  • Add equivalent instructions using Azure CLI commands for all steps involving Azure portal actions, ensuring Linux users can follow along without a graphical interface.
  • Include examples of configuring Commvault integration with Azure Storage using command-line tools available on Linux (e.g., Bash scripts, Azure CLI, REST API calls).
  • Explicitly mention that Commvault and Azure integration can be performed from Linux environments and provide links to relevant Linux documentation.
  • Where monitoring and operational guidance is given, include references to Linux-compatible tools (e.g., az CLI, open-source monitoring solutions) alongside Azure Monitor.
  • Ensure that any references to authentication (such as Entra ID Application setup) include CLI-based steps and note platform compatibility.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/data-lake-storage-use-hdfs-data-lake-storage.md .../blobs/data-lake-storage-use-hdfs-data-lake-storage.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 page demonstrates a Windows bias by providing SSH connection examples using PowerShell syntax and referencing PowerShell code for connecting to HDInsight clusters. There are no equivalent Linux shell (bash) examples, and the PowerShell example is presented first and exclusively, despite the context being HDInsight on Linux. This may confuse or disadvantage Linux users who expect bash or standard shell examples.
Recommendations
  • Provide Linux shell (bash) examples alongside or before PowerShell examples for SSH connections.
  • Clarify that the SSH connection can be made from any OS and provide platform-agnostic instructions.
  • If PowerShell is mentioned, also include the equivalent bash command (e.g., 'ssh sshuser@clustername-ssh.azurehdinsight.net') in a separate code block.
  • Review other sections for OS-specific terminology and ensure parity in instructions and examples for both Windows and Linux users.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/last-sync-time-get.md ...lob/main/articles/storage/common/last-sync-time-get.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 both PowerShell and Azure CLI examples for checking the Last Sync Time property, but it presents the PowerShell (Windows-centric) example first and in greater detail (including module installation instructions). There are no explicit Linux shell or Bash examples, and the CLI example, while cross-platform, is not specifically tailored for Linux users.
Recommendations
  • Present Azure CLI (cross-platform) examples before PowerShell examples to avoid implying Windows is the primary or preferred environment.
  • Include explicit Bash/Linux shell examples or notes, such as using the Azure CLI in a Bash shell, to reinforce Linux parity.
  • If mentioning module installation for PowerShell, consider adding analogous setup notes for CLI usage on Linux (e.g., how to install Azure CLI on Linux).
  • Clarify that Azure CLI commands work identically on Windows, Linux, and macOS, and provide sample outputs or troubleshooting tips relevant to Linux environments.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/storage-network-security-manage-exceptions.md ...e/common/storage-network-security-manage-exceptions.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 PowerShell (a Windows-centric tool) examples before Azure CLI (cross-platform) examples, and provides detailed step-by-step instructions for PowerShell. This ordering and emphasis may suggest a Windows bias, as Linux users typically prefer Azure CLI or Bash examples. No explicit Linux-only tools or shell examples (e.g., Bash) are provided.
Recommendations
  • Present Azure CLI examples before PowerShell examples, as Azure CLI is cross-platform and preferred by many Linux users.
  • Add Bash shell script examples for common tasks to improve accessibility for Linux users.
  • Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows.
  • Consider adding a section for managing exceptions using REST API or ARM templates, which are platform-neutral.
  • Review and balance the depth of instructions for both PowerShell and Azure CLI to ensure parity.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/storage-network-security-resource-instances.md .../common/storage-network-security-resource-instances.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 detailed PowerShell examples for managing Azure Storage resource instance network rules, with PowerShell presented before Azure CLI. This ordering and emphasis may favor Windows users, as PowerShell is primarily associated with Windows environments, while Azure CLI is cross-platform and more commonly used on Linux and macOS. No Linux-specific tools or shell examples (such as Bash scripts) are provided, and there is no mention of platform differences or parity.
Recommendations
  • Present Azure CLI examples before PowerShell to prioritize cross-platform usage.
  • Include Bash script examples for common operations, highlighting Linux usage.
  • Explicitly state that Azure CLI is available on Windows, Linux, and macOS, and provide installation links for each platform.
  • Add notes or sections addressing platform-specific considerations, such as differences in authentication or environment setup between Windows and Linux.
  • Ensure parity in example depth and coverage between PowerShell and Azure CLI, so Linux users have equally comprehensive guidance.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/storage-use-azcopy-blobs-download.md ...es/storage/common/storage-use-azcopy-blobs-download.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation consistently uses Windows-style local paths (e.g., 'C:\myDirectory\myTextFile.txt') in all examples and does not provide equivalent Linux/macOS examples (e.g., '/home/user/myTextFile.txt'). Windows path syntax is shown exclusively and first, which may confuse or exclude Linux/macOS users. While there are notes about quoting differences between shells, the examples themselves remain Windows-centric.
Recommendations
  • For each example, provide both Windows and Linux/macOS versions, showing appropriate local path formats (e.g., 'C:\myDirectory\myTextFile.txt' and '/home/user/myTextFile.txt').
  • Alternate or parallelize examples so that Linux/macOS syntax is shown alongside Windows syntax.
  • Add a section explicitly describing path conventions for Linux/macOS users.
  • Where shell differences are discussed, provide concrete Linux/macOS shell command examples (e.g., bash/zsh).
  • Ensure that documentation language and examples are inclusive of all supported platforms, not just Windows.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/files/storage-dotnet-how-to-use-files.md ...icles/storage/files/storage-dotnet-how-to-use-files.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in several areas. In the 'Work with Azure Files using System.IO' section, all code examples use a Windows-style SMB path (e.g., Z:\file-share) and do not provide Linux path equivalents or examples. The mounting instructions reference both Windows and Linux, but the code and narrative consistently default to Windows conventions. There are no Linux-specific code samples or guidance for using NFS mounts or Linux file paths with System.IO, despite Azure Files supporting NFS and Linux clients.
Recommendations
  • Provide parallel code examples using Linux-style paths (e.g., '/mnt/file-share') and demonstrate System.IO usage with NFS-mounted shares on Linux.
  • Explicitly mention and show how to mount Azure Files shares on Linux, including sample mount commands and .NET code using Linux paths.
  • Where examples use Windows-specific conventions (such as drive letters), add equivalent Linux examples and clarify platform differences.
  • Ensure that instructions and examples for mounting and accessing shares do not default to Windows, but present both platforms equally.
  • Add troubleshooting notes or platform-specific caveats for both Windows and Linux to help developers avoid common issues.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/blob-cli.md ...zure-docs/blob/main/articles/storage/blobs/blob-cli.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page exhibits Windows bias primarily through the use of Windows-style file paths (e.g., C:\temp\) in all code examples, and by referencing Windows directories for sample files and XML data. There are no Linux or macOS path examples, nor any mention of Linux-specific considerations, despite the Azure CLI being cross-platform. The instructions and examples implicitly assume a Windows environment, which may confuse or inconvenience users on Linux or macOS.
Recommendations
  • Provide parallel examples using Linux/macOS file paths (e.g., /tmp/, /home/user/, /mnt/c/temp/) alongside Windows paths.
  • Add notes clarifying that file paths should be adapted to the user's operating system.
  • Mention that the Azure CLI works on Linux, macOS, and Windows, and highlight any OS-specific considerations (such as path separators, permissions, or shell differences).
  • Where sample files are referenced (such as blob-list.xml), suggest equivalent locations for Linux/macOS users.
  • Consider alternating between Windows and Linux/macOS examples or providing both in code blocks, especially for file operations.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/data-lake-storage-directory-file-acl-cli.md ...rage/blobs/data-lake-storage-directory-file-acl-cli.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation demonstrates a mild Windows bias. In the prerequisites and setup sections, Windows PowerShell is mentioned as the example console application for running Azure CLI locally, with no mention of Linux or macOS terminal alternatives. Additionally, file path examples for upload and download operations use Windows-style paths (e.g., 'C:\myFolder\upload.txt'), with no equivalent Linux/macOS examples (e.g., '/home/user/upload.txt'). There are no references to Linux-specific tools or shell environments, and all examples assume a Windows-centric context.
Recommendations
  • Mention Linux/macOS terminal applications (e.g., Bash, Terminal, zsh) alongside Windows PowerShell when instructing users to open a command console.
  • Provide Linux/macOS file path examples (e.g., '/home/user/upload.txt') in upload/download commands, either alongside or alternating with Windows paths.
  • Add a note clarifying that Azure CLI works equally well on Linux/macOS and provide links to installation instructions for those platforms.
  • Where relevant, mention cross-platform considerations for file paths and shell environments.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/encryption-scope-overview.md ...in/articles/storage/blobs/encryption-scope-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 page exhibits mild Windows bias by referencing PowerShell before CLI when discussing Azure Key Vault soft-delete recovery. No Linux-specific tools or examples are provided, and the only command-line references are to PowerShell and CLI, with PowerShell mentioned first. There are no explicit examples or instructions for Linux environments, nor are Linux tools or patterns discussed.
Recommendations
  • Present CLI and PowerShell references in parallel, or mention CLI first to avoid implicit prioritization of Windows tools.
  • Include explicit Linux examples or instructions where command-line operations are discussed.
  • Reference cross-platform tools (such as Azure CLI, Bash scripts) alongside PowerShell to ensure parity.
  • Add notes clarifying that all operations can be performed on Linux, macOS, and Windows, and link to platform-specific guides if available.
GitHub Create Pull Request
← Previous Page 53 of 67 Next →