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 1601-1625 of 1657 flagged pages
Storage Quickstart: Azure Queue Storage client library - .NET ...les/storage/queues/storage-quickstart-queues-dotnet.md
Low Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation page is generally cross-platform, but there is a minor Windows bias in the 'Create the project' section, where Windows consoles (cmd, PowerShell) are mentioned before Bash. All commands shown (dotnet CLI) are cross-platform, and there are no Windows-only tools or examples. No critical steps are Windows-exclusive, and Linux/macOS users can follow the instructions without issue.
Recommendations
  • List Bash (Linux/macOS) alongside or before Windows consoles (cmd, PowerShell) when mentioning terminal options.
  • Explicitly state that all commands work on Linux/macOS as well as Windows.
  • Add a note or section confirming cross-platform compatibility, especially for environment variable setup and running the app.
  • If referencing environment variables, briefly mention how to set them on Linux/macOS (e.g., export AZURE_STORAGE_CONNECTION_STRING=...)
GitHub Create Pull Request
Storage Assign an Azure role for access to queue data ...ticles/storage/queues/assign-azure-role-data-access.md
Low Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides both PowerShell and Azure CLI examples for assigning Azure roles, but PowerShell (a Windows-centric tool) is presented before Azure CLI. There is no explicit Linux/macOS bias, but the ordering and emphasis on PowerShell may subtly favor Windows users. No examples are missing for Linux users, as Azure CLI is cross-platform and fully supported.
Recommendations
  • Present Azure CLI examples before PowerShell, as CLI is cross-platform and more accessible to Linux/macOS users.
  • Explicitly mention that Azure CLI works on Windows, Linux, and macOS.
  • Consider adding Bash or shell script snippets for common tasks, if relevant.
  • Clarify that PowerShell Core is available cross-platform, but Azure CLI is typically preferred on Linux/macOS.
GitHub Create Pull Request
Storage Quickstart: Azure Queue Storage client library for Java ...icles/storage/queues/storage-quickstart-queues-java.md
Low Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page demonstrates mild Windows bias in the project creation section, where Windows tools (cmd, PowerShell) are mentioned before Bash, and the PowerShell example is shown before the Bash example. The output example uses a Windows path (C:\quickstarts\queues\queues-quickstart), reinforcing the Windows-first perspective. However, Bash instructions are provided, and the rest of the documentation is platform-neutral, focusing on Java and Maven commands that work on all platforms.
Recommendations
  • Present Bash and PowerShell examples side-by-side or in a neutral order, or default to Bash first as it is more universal across platforms.
  • Use platform-neutral file paths in output examples (e.g., /quickstarts/queues/queues-quickstart or <project-path>).
  • Explicitly mention that all commands work on Linux, macOS, and Windows, and provide any platform-specific notes if needed.
  • Where console windows are referenced, use 'terminal' or 'command line' instead of 'cmd, PowerShell, or Bash' to avoid Windows-centric terminology.
GitHub Create Pull Request
Storage Migrate your block data to Azure with Cirrus Data ...artners/data-management/cirrus-data-migration-guide.md
Low Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a mild Windows bias. References to Azure VM creation and overview link to Windows-specific guides first, and there is no parity in providing Linux/macOS-specific instructions or examples for VM setup or migration. While the migration example does mention a Linux source host and uses Linux commands (e.g., iostat), the initial guidance and 'Next steps' section prioritize Windows resources, and there is no explicit Linux VM creation or management guidance.
Recommendations
  • Include direct links to Linux and macOS Azure VM creation guides alongside Windows guides.
  • Add explicit examples or instructions for Linux/macOS VM setup and migration, including relevant commands and screenshots.
  • Ensure parity in 'Next steps' and reference sections by mentioning both Windows and Linux resources.
  • Clarify that the migration process is OS-agnostic and provide troubleshooting tips for Linux/macOS users.
GitHub Create Pull Request
Storage Considerations for running ISV file services in Azure ...artners/primary-secondary-storage/isv-file-services.md
Low Priority View Details →
Scanned: 2026-01-13 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 mild Windows bias, primarily through repeated references to Windows Server as the operating environment for several ISV solutions (Tiger Technology, XenData), and features such as Windows Shell integration and Windows clustering for high availability and failover. Example use cases and feature tables mention Windows-specific deployment scenarios (e.g., disaster recovery for Windows servers) and management tools, while Linux-specific environments or management patterns are not highlighted or are only mentioned generically. There are no explicit Linux/macOS usage examples, nor are Linux management tools or deployment patterns described.
Recommendations
  • Add explicit examples and use cases for Linux and macOS environments, such as disaster recovery for Linux servers, or integration with Linux desktop environments.
  • Highlight Linux-compatible management tools and deployment patterns, including CLI and automation options (e.g., systemd, Ansible, Terraform).
  • Clarify whether features like clustering, failover, and file locking are available and supported on Linux/macOS, and provide parity details.
  • Include Linux-specific integration features (e.g., FUSE, Linux shell integration) where relevant.
  • Balance example scenarios to include both Windows and Linux/macOS workflows, especially in tables and feature lists.
GitHub Create Pull Request
Storage Performance and scalability checklist for Table storage ...ticles/storage/tables/storage-performance-checklist.md
Low Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page exhibits mild Windows bias, primarily through references to Windows-centric tools (WireShark, NetMon), and by mentioning PowerShell before Azure CLI when discussing client libraries and tools. The .NET configuration section is Windows/.NET-focused, with no equivalent examples for Linux or other platforms. There are no explicit Linux/macOS examples or tool recommendations, and Windows tools are mentioned without alternatives. However, most of the guidance is platform-agnostic and does not prevent Linux/macOS users from following the checklist.
Recommendations
  • Include Linux/macOS equivalents for network diagnostic tools (e.g., tcpdump, iftop) alongside WireShark and NetMon.
  • Mention Azure CLI before or alongside PowerShell when discussing supported tools, and provide example commands for both.
  • Provide configuration examples for popular non-.NET languages (e.g., Python, Java) and platforms, especially for connection/thread pool settings.
  • Explicitly state that the checklist applies to all platforms and highlight any platform-specific considerations.
  • Add links to cross-platform documentation or guides where relevant.
GitHub Create Pull Request
Storage Use Azure CLI to manage ACLs in Azure Data Lake Storage ...in/articles/storage/blobs/data-lake-storage-acl-cli.md
Low Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation page demonstrates a mild Windows bias by mentioning Windows PowerShell as the example local command console before any Linux or macOS alternatives. No Linux-specific tools, shells, or patterns are referenced, and no explicit Linux/macOS examples are provided for opening a terminal or running the Azure CLI. However, all command-line examples use the cross-platform Azure CLI, and there are no PowerShell-specific commands or Windows-only tools shown.
Recommendations
  • Mention Linux/macOS terminal applications (e.g., 'open a terminal such as Terminal on macOS or GNOME Terminal on Linux') alongside or before Windows PowerShell in the prerequisites and setup sections.
  • Explicitly state that Azure CLI commands work on Windows, Linux, and macOS, and provide links to installation instructions for all platforms.
  • Include screenshots or output examples from Linux/macOS terminals in addition to Windows, if applicable.
  • Avoid listing Windows tools first unless there is a technical reason; use neutral language such as 'open a command-line terminal' or 'open your preferred shell'.
GitHub Create Pull Request
Storage Monitoring data reference for Azure Blob Storage ...ticles/storage/blobs/monitor-blob-storage-reference.md
Low Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
🔧 Windows Tools
Summary
The documentation page is generally platform-neutral and does not provide command-line examples or tooling instructions specific to Windows or Linux. However, there is a subtle Windows bias in the sample 'userAgentHeader' field, which references a Windows-based browser environment (Windows NT 10.0; Win64; x64; Edge). No Linux or cross-platform user agent examples are given, and there are no explicit Linux command-line or tooling references.
Recommendations
  • When providing sample data (such as user agent strings), include examples from Linux and macOS environments (e.g., Chrome on Ubuntu, Firefox on macOS) to illustrate cross-platform usage.
  • If future documentation includes command-line or scripting examples, ensure parity by providing both PowerShell/Windows CMD and Bash/Linux equivalents.
  • Explicitly mention that Azure Blob Storage monitoring features and logs are accessible and usable from all major platforms, including Linux and macOS, to reinforce platform neutrality.
  • Review any referenced tools or patterns in included content to ensure Linux tools (such as Azure CLI in Bash) are represented alongside Windows tools.
GitHub Create Pull Request
Storage Copy blobs between Azure storage accounts with AzCopy v10 ...ticles/storage/common/storage-use-azcopy-blobs-copy.md
Low Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation consistently references Windows Command Shell (cmd.exe) in every example tip, instructing users to use double quotes on Windows and single quotes elsewhere. Windows-specific instructions are always mentioned first, and there are no Linux-specific command examples or shell-specific notes (e.g., bash, zsh). No PowerShell-specific commands or Windows-only tools are present, but the pattern of mentioning Windows first and not providing explicit Linux shell examples indicates a subtle Windows bias.
Recommendations
  • Alternate the order of shell instructions so that Linux/macOS shells (bash, zsh) are mentioned first in some sections.
  • Explicitly provide example commands for Linux/macOS shells, including notes about escaping, quoting, and environment variable usage.
  • Add a section or table summarizing quoting and escaping differences across common shells (bash, zsh, PowerShell, cmd.exe).
  • Include troubleshooting tips for Linux/macOS environments (e.g., permissions, path formats) where relevant.
  • Use inclusive language such as 'on Linux/macOS, use single quotes; on Windows cmd.exe, use double quotes' rather than always leading with Windows.
GitHub Create Pull Request
Storage Replace Azure Blob Storage properties & metadata with AzCopy ...common/storage-use-azcopy-blobs-properties-metadata.md
Low Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation repeatedly mentions Windows Command Shell (cmd.exe) in tips about quoting conventions, always listing Windows-specific instructions before Linux/macOS equivalents. However, all command examples use single quotes (the Linux/macOS convention) and do not provide explicit PowerShell or cmd.exe examples. No Windows-only tools or patterns are present, and Linux examples are not missing, but the ordering and emphasis on Windows instructions indicate a subtle 'windows_first' bias.
Recommendations
  • Present quoting conventions for Linux/macOS and Windows in parallel, or list Linux/macOS first to balance historical bias.
  • Include explicit command examples for both Linux/macOS and Windows shells (e.g., show one example with single quotes and one with double quotes).
  • Clarify that AzCopy is cross-platform and provide shell-specific guidance where relevant.
  • Consider a table or section summarizing differences in command syntax across platforms.
GitHub Create Pull Request
Storage Quickstart: Azure Queue Storage client library for Python ...les/storage/queues/storage-quickstart-queues-python.md
Low Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation page demonstrates a subtle Windows bias by listing Windows consoles (cmd, PowerShell) before Bash when instructing users to create a directory for the project. No explicit Linux or macOS examples are provided, but the instructions and code samples are generally cross-platform and do not rely on Windows-specific tools or patterns.
Recommendations
  • List Bash (Linux/macOS) first or equally alongside cmd and PowerShell when mentioning console options.
  • Explicitly state that all commands and code samples work on Linux, macOS, and Windows.
  • Where environment variables are discussed, mention platform-specific methods for setting them (e.g., 'export' for Bash, 'set' for cmd, '$env:' for PowerShell).
  • Include a note or section confirming Linux/macOS compatibility and any platform-specific considerations.
GitHub Create Pull Request
Storage Use Azure CLI to manage ACLs in Azure Data Lake Storage ...in/articles/storage/blobs/data-lake-storage-acl-cli.md
Low Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation page demonstrates a mild Windows bias by mentioning Windows PowerShell as the primary example of a local command console application before any Linux or macOS alternatives. No Linux-specific tools, shells, or examples are referenced, and the guidance does not explicitly mention Linux or macOS terminals, despite the Azure CLI being cross-platform.
Recommendations
  • Explicitly mention Linux and macOS terminals (e.g., Bash, Terminal, zsh) alongside Windows PowerShell when instructing users to open a command console.
  • Add a note clarifying that all Azure CLI commands work equally on Windows, Linux, and macOS.
  • Include example screenshots or outputs from Linux/macOS terminals in addition to Windows, if images are used.
  • Avoid listing Windows tools or shells first; use neutral language such as 'open your preferred command-line interface (e.g., PowerShell, Bash, Terminal)'.
GitHub Create Pull Request
Storage Copy blobs between Azure storage accounts with AzCopy v10 ...ticles/storage/common/storage-use-azcopy-blobs-copy.md
Low Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation repeatedly mentions Windows Command Shell (cmd.exe) in tips about quoting conventions, always referencing Windows first and Linux/macOS second. However, all command examples use single quotes (Linux/macOS style) and do not provide explicit Windows (double-quoted) command examples. There is no evidence of Powershell-heavy content, exclusive use of Windows tools, or missing Linux examples. The only bias is the consistent prioritization of Windows shell instructions before Linux/macOS equivalents.
Recommendations
  • Provide explicit command examples for both Windows (using double quotes) and Linux/macOS (using single quotes) side-by-side, especially in sections where quoting conventions are discussed.
  • When giving shell-specific instructions, alternate the order or present both platforms equally (e.g., 'For Linux/macOS, use single quotes; for Windows cmd.exe, use double quotes').
  • Consider adding a brief section or table summarizing platform-specific command syntax differences for AzCopy usage.
  • Ensure that references to shell environments do not always prioritize Windows first, but instead treat all major platforms equally.
GitHub Create Pull Request
Storage Quickstart: Azure Queue Storage client library for Python ...les/storage/queues/storage-quickstart-queues-python.md
Low Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation page demonstrates a mild Windows bias in the 'Create the project' section, where Windows consoles (cmd, PowerShell) are mentioned before Bash, and in the environment variable setup instructions, which reference Visual Studio and console shells in a Windows-centric manner. However, the code examples and instructions themselves are cross-platform and do not rely on Windows-specific tools or patterns.
Recommendations
  • List Bash before or alongside cmd/PowerShell when mentioning console windows to avoid implying Windows primacy.
  • Add explicit instructions or notes for setting environment variables on Linux/macOS (e.g., using 'export' in Bash), not just referencing Visual Studio or Windows consoles.
  • Where environment variables are discussed, clarify how to reload shells or apply changes on Linux/macOS (e.g., 'source ~/.bashrc') as well as on Windows.
  • Ensure all references to editors, consoles, and shell environments are inclusive of Linux/macOS options (e.g., mention VS Code, nano, vim, etc.).
GitHub Create Pull Request
Storage Quickstart: Azure Queue Storage client library - .NET ...les/storage/queues/storage-quickstart-queues-dotnet.md
Low Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation page demonstrates a subtle Windows bias by listing Windows consoles (cmd, PowerShell) before Bash when describing how to run commands. However, all commands and instructions are cross-platform and do not rely on Windows-specific tools or patterns. No PowerShell-specific examples or Windows-only tooling are present, and Linux users are not excluded from any steps.
Recommendations
  • List Bash (or 'terminal') before Windows consoles when describing command-line usage, or mention all platforms equally (e.g., 'in a terminal or command prompt such as Bash, cmd, or PowerShell').
  • Explicitly state that all commands work on Windows, Linux, and macOS, and provide links or notes for platform-specific considerations if any exist.
  • If referencing editors, mention cross-platform options (e.g., VS Code, Vim, etc.) in addition to Visual Studio.
  • Ensure screenshots, if present, show cross-platform environments or are neutral.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/data-lake-storage-acl-cli.md ...in/articles/storage/blobs/data-lake-storage-acl-cli.md
Low Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation page demonstrates a subtle Windows bias by mentioning Windows PowerShell as the primary example of a 'command console application' for running the Azure CLI locally, without referencing Linux or macOS terminal alternatives. No Linux-specific tools, shell examples, or platform-specific notes are provided, and the ordering places Windows terminology before cross-platform or Linux equivalents.
Recommendations
  • Explicitly mention Linux and macOS terminal applications (e.g., 'open a terminal on Linux or macOS, or Windows PowerShell/Command Prompt on Windows') when describing how to run Azure CLI locally.
  • Add a note clarifying that all Azure CLI commands shown work identically on Linux, macOS, and Windows.
  • Provide links or brief instructions for installing Azure CLI on Linux and macOS alongside the Windows instructions.
  • Avoid listing Windows tools or terminology first unless there is a technical reason; use neutral, cross-platform language where possible.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/queues/storage-quickstart-queues-python.md ...les/storage/queues/storage-quickstart-queues-python.md
Low Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation page exhibits mild Windows bias in the 'Create the project' section, where Windows consoles (cmd, PowerShell) are mentioned before Bash, and in the environment variable setup instructions, which reference Visual Studio and console windows but do not provide explicit Linux/macOS guidance. No PowerShell-specific commands or Windows-only tools are used, and all code examples are OS-agnostic Python. However, the instructions and context lean toward Windows-first terminology and workflow.
Recommendations
  • List Bash (Linux/macOS) before Windows consoles (cmd, PowerShell) when describing command-line steps, or mention all platforms equally.
  • Explicitly provide instructions for setting environment variables on Linux/macOS (e.g., export AZURE_STORAGE_CONNECTION_STRING=...) alongside Windows instructions.
  • Avoid referencing Visual Studio or Windows-specific shells without also mentioning common Linux/macOS alternatives (e.g., Terminal, VS Code on Linux).
  • Add a short note confirming that all steps and code work equally on Linux/macOS, and link to platform-specific setup guides if available.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/security-recommendations.md ...ain/articles/storage/blobs/security-recommendations.md
Low Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Missing Linux Example
Summary
The documentation provides security recommendations for Azure Blob storage but does not include any platform-specific command-line examples, scripts, or tooling references. However, there is a notable absence of Linux-specific guidance, examples, or references to Linux-native tools or patterns. The documentation is written in a platform-neutral way, but it also omits any mention of Linux or cross-platform command-line usage, which may leave Linux users without clear operational guidance.
Recommendations
  • Add example commands for common security tasks using both PowerShell (for Windows) and Bash/CLI (for Linux/macOS), such as enabling soft delete, configuring firewalls, or managing keys.
  • Reference Azure CLI commands alongside any PowerShell or portal instructions, as Azure CLI is cross-platform and widely used on Linux.
  • Include links or sections about using Azure Storage security features from Linux environments, such as scripting with Bash, using curl, or leveraging open-source tools.
  • Explicitly mention cross-platform support for all features and clarify any differences in implementation or tooling between Windows and Linux.
  • Provide sample automation scripts for both Windows and Linux environments to demonstrate security best practices.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/storage-use-azcopy-blobs-copy.md ...ticles/storage/common/storage-use-azcopy-blobs-copy.md
Low Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation consistently mentions Windows Command Shell (cmd.exe) as an exception for quoting conventions before mentioning Linux or macOS shells. All examples use single quotes, with a repeated tip that Windows users should use double quotes. No Linux-specific tools, patterns, or troubleshooting steps are provided, nor are Linux or macOS shells named explicitly. The focus is on AzCopy, which is cross-platform, but the guidance for shell quoting is Windows-centric and always presented first.
Recommendations
  • Explicitly mention Linux and macOS shells (e.g., Bash, Zsh) when discussing quoting conventions, not just 'all command shells except Windows Command Shell'.
  • Provide example commands using both single and double quotes, showing side-by-side how a Linux/macOS user would run the command versus a Windows user.
  • Add troubleshooting tips or notes for common Linux/macOS issues (e.g., permissions, environment variables, path conventions) when using AzCopy.
  • Consider listing Linux/macOS instructions before or alongside Windows instructions to avoid implicit prioritization.
  • Reference Linux/macOS tools or patterns where relevant (e.g., using export for environment variables, using chmod for permissions).
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/queues/storage-quickstart-queues-dotnet.md ...les/storage/queues/storage-quickstart-queues-dotnet.md
Low Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation page demonstrates a mild Windows bias in the 'Create the project' section, where Windows-specific consoles (cmd, PowerShell) are mentioned before Bash, and the overall language and instructions subtly prioritize Windows environments. However, most commands and instructions (dotnet CLI, environment variables) are cross-platform and do not rely on Windows-only tools or patterns. No PowerShell-specific examples, Windows-only tools, or missing Linux examples are present.
Recommendations
  • List Bash (Linux/macOS) first or equally alongside cmd and PowerShell when mentioning console options.
  • Explicitly state that all commands work on Windows, Linux, and macOS, and provide links or notes for platform-specific differences if any exist.
  • Include a brief note or example for setting environment variables on Linux/macOS (e.g., export AZURE_STORAGE_CONNECTION_STRING=...) alongside the Windows example (set AZURE_STORAGE_CONNECTION_STRING=...).
  • Ensure that any references to editors or tools are platform-neutral or mention popular Linux/macOS options (e.g., VS Code, Vim, etc.).
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/queues/storage-quickstart-queues-java.md ...icles/storage/queues/storage-quickstart-queues-java.md
Low Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation mentions Windows-specific consoles (cmd, PowerShell) before Bash when describing how to create the project. The example output uses a Windows file path (C:\quickstarts\queues\queues-quickstart), and references to Visual Studio are present when discussing environment variables. However, Bash examples are provided alongside PowerShell, and most instructions are cross-platform. There are no PowerShell-heavy commands, exclusive Windows tools, or missing Linux examples in the main workflow.
Recommendations
  • List Bash (Linux/macOS) consoles before Windows (cmd, PowerShell) to avoid implicit prioritization.
  • Provide example output using both Windows and Linux file paths, or use a neutral path format.
  • Replace or supplement references to Visual Studio with cross-platform IDEs or editors (e.g., VS Code, IntelliJ IDEA).
  • Clarify that environment variable instructions apply to all platforms, and provide platform-specific guidance where necessary.
  • Ensure that all steps and troubleshooting notes explicitly mention Linux/macOS equivalents if any Windows-specific behavior is described.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/queues/storage-quickstart-queues-python.md ...les/storage/queues/storage-quickstart-queues-python.md
Low Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation page demonstrates a mild Windows bias by listing Windows consoles (cmd, PowerShell) before Bash when instructing users to create a project directory. However, all code examples and instructions are platform-agnostic Python and do not rely on Windows-specific tools or patterns. No PowerShell-specific commands, Windows-only tools, or missing Linux examples are present.
Recommendations
  • List Bash (Linux/macOS) before Windows consoles (cmd, PowerShell) when mentioning terminal options, or mention all platforms equally.
  • Explicitly state that all instructions and code samples work on Linux, macOS, and Windows.
  • Add a note or section confirming cross-platform compatibility, especially for environment variable setup and running Python scripts.
  • If referencing environment variable setup, provide both Windows (set/setx) and Linux/macOS (export) examples.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/data-lake-storage-acl-cli.md ...in/articles/storage/blobs/data-lake-storage-acl-cli.md
Low Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation page exhibits a mild Windows bias by mentioning Windows PowerShell as the example local command console before any Linux or macOS alternatives. No Linux-specific tools, shells, or patterns are referenced, and the only explicit local shell mentioned is Windows PowerShell. All command examples use the Azure CLI, which is cross-platform, and do not use Windows-specific syntax, but the introductory guidance prioritizes Windows environments.
Recommendations
  • When suggesting local command consoles, mention Linux/macOS terminals (e.g., Bash, Terminal) alongside Windows PowerShell, or use neutral phrasing such as 'open a command-line terminal (e.g., Bash, PowerShell, Terminal)'.
  • Explicitly state that Azure CLI commands work on Windows, Linux, and macOS, and provide links or brief instructions for installing Azure CLI on all major platforms.
  • Add a note or section confirming that all examples are platform-agnostic and can be run in any standard shell environment.
  • If screenshots or output images are shown, ensure they are not Windows-specific (e.g., avoid showing Windows-only terminal UI).
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/storage-use-azcopy-blobs-copy.md ...ticles/storage/common/storage-use-azcopy-blobs-copy.md
Low Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation consistently references Windows Command Shell (cmd.exe) in every example tip, specifying that double quotes should be used on Windows and single quotes elsewhere. Windows is mentioned first and more prominently than Linux or macOS, but there are no explicit PowerShell examples, Windows-only tools, or missing Linux examples. The guidance is cross-platform, but the ordering and emphasis favor Windows users.
Recommendations
  • Alternate the order of shell guidance, sometimes mentioning Linux/macOS first or equally.
  • Explicitly state that AzCopy works identically on Linux, macOS, and Windows, and provide example commands for bash/zsh/fish shells where quoting or escaping differs.
  • Add a dedicated section or note for Linux/macOS users highlighting any platform-specific considerations (such as environment variable syntax, file paths, or permissions).
  • Where quoting is discussed, provide a table or summary for all major shells (cmd.exe, PowerShell, bash, zsh, etc.) rather than only Windows vs. 'all others'.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/queues/storage-quickstart-queues-dotnet.md ...les/storage/queues/storage-quickstart-queues-dotnet.md
Low Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation page demonstrates a mild Windows bias in its instructions for creating a .NET project. Specifically, it lists Windows-specific consoles (cmd, PowerShell) before Bash when describing how to run commands, subtly prioritizing Windows environments. However, all commands shown (dotnet CLI) are cross-platform, and there are no PowerShell-specific scripts, Windows-only tools, or missing Linux examples. The instructions and code samples are generally platform-neutral, but the ordering of console examples and references could be more inclusive.
Recommendations
  • List Bash before or alongside cmd and PowerShell when referencing console windows to avoid implying Windows primacy.
  • Explicitly state that all commands work on Windows, Linux, and macOS, and provide links to platform-specific .NET installation guides.
  • Include a brief note or section confirming Linux/macOS compatibility, especially for environment variable setup and running the app.
  • Where possible, provide screenshots or terminal output examples from both Windows and Linux/macOS environments.
GitHub Create Pull Request
← Previous Page 65 of 67 Next →