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 276-300 of 392 flagged pages
Storage Azure Elastic SAN configuration best practices ...cles/storage/elastic-san/elastic-san-best-practices.md
Low Priority View Details →
Scanned: 2026-01-13 21:56
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation demonstrates a mild Windows bias. Windows-specific tools (PowerShell, Registry Editor, iSCSI Initiator app) are often mentioned first or in more detail, and Windows command-line examples (PowerShell) are provided before Linux equivalents. However, Linux guidance and commands are also present and generally complete, allowing Linux users to follow along, though sometimes with less detail or prominence.
Recommendations
  • Present Linux and Windows examples in parallel or alternate the order to avoid always listing Windows first.
  • Provide equal detail for Linux tools and workflows (e.g., mention Linux equivalents to the iSCSI Initiator app and Registry Editor, such as using iscsiadm and editing config files).
  • Where possible, link to Linux-specific documentation for advanced configuration, similar to the Windows MPIO reference.
  • Clarify that all recommendations apply equally to Linux and Windows unless otherwise noted.
  • Add more screenshots or step-by-step instructions for Linux where only Windows visuals are provided.
GitHub Create Pull Request
Storage Connect Azure Elastic SAN to Azure Kubernetes over iSCSI ...rticles/storage/elastic-san/elastic-san-connect-aks.md
Low Priority View Details →
Scanned: 2026-01-13 21:56
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation shows a mild Windows bias by listing Azure PowerShell as the first method to retrieve volume information, and providing a PowerShell example before the Azure CLI example. It also refers to 'install the latest Azure PowerShell module' alongside Azure CLI in prerequisites, and uses the term 'Azure PowerShell command' explicitly. However, Azure CLI examples are present, and the rest of the workflow uses cross-platform tools (kubectl, YAML manifests).
Recommendations
  • List Azure CLI examples before Azure PowerShell examples, as Azure CLI is cross-platform and more commonly used on Linux/macOS.
  • Clarify that both Azure CLI and PowerShell are supported, and consider grouping their usage together rather than leading with PowerShell.
  • Explicitly mention that all steps after volume information retrieval are OS-agnostic.
  • If possible, provide bash/zsh shell command examples for common tasks, or note that Azure CLI is recommended for Linux/macOS users.
GitHub Create Pull Request
Storage Best practices for monitoring Azure Blob Storage ...les/storage/blobs/blob-storage-monitoring-scenarios.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page generally presents platform-neutral guidance for monitoring Azure Blob Storage, focusing on Azure portal, Kusto queries, and Azure services. However, in the section on identifying the SAS token used to authorize a request, the first code example for decoding the SAS signature uses PowerShell, with the Linux alternative given second. This ordering and inclusion of PowerShell as the primary example introduces a mild Windows-first and PowerShell-heavy bias.
Recommendations
  • Present Linux/macOS and Windows examples side-by-side, or alternate which platform is shown first.
  • Provide Bash or Python examples before or alongside PowerShell, especially for common tasks like string decoding and hashing.
  • Explicitly mention cross-platform tools and clarify that all steps can be performed on Linux/macOS as well as Windows.
  • Consider adding CLI or SDK-based examples that work identically across platforms.
GitHub Create Pull Request
Storage Known issues with Azure Data Lake Storage ...ticles/storage/blobs/data-lake-storage-known-issues.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page exhibits mild Windows bias, primarily through the mention of PowerShell and Windows Azure Storage Blob (WASB) driver, and by listing PowerShell before Azure CLI in the section on restoring soft-deleted blobs. There is also a focus on Windows-specific tools (WASB driver) and patterns, with less emphasis on Linux/macOS equivalents or parity.
Recommendations
  • Ensure that all command-line examples (e.g., restoring soft-deleted blobs) provide both PowerShell and Azure CLI examples, and present them in parallel or alternate their order.
  • Explicitly mention Linux/macOS compatibility for tools like AzCopy and Azure Storage Explorer, and provide installation or usage notes for those platforms.
  • Where Windows-specific drivers or tools (e.g., WASB) are discussed, clarify Linux/macOS alternatives and migration paths.
  • Add a section or note highlighting cross-platform support and any platform-specific caveats for major tools and SDKs.
GitHub Create Pull Request
Storage Version-level WORM policies for immutable blob data ...storage/blobs/immutable-version-level-worm-policies.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation page demonstrates mild Windows bias in its examples and tool references. In the 'Deletion' section, PowerShell commands (Remove-AzRmStorageContainer and Remove-AzStorageContainer) are mentioned first and in detail, with explicit links to their documentation. The Azure CLI command is referenced, but only after the PowerShell examples. There is no mention of Linux/macOS-specific tooling or shell usage, and the PowerShell commands are presented as the primary method for control plane operations. No Linux shell (bash) or cross-platform scripting examples are provided.
Recommendations
  • Provide equivalent Linux/macOS shell (bash) examples for container deletion using Azure CLI.
  • List Azure CLI commands before or alongside PowerShell commands to avoid Windows-first ordering.
  • Explicitly state that Azure CLI is cross-platform and provide usage examples for Linux/macOS users.
  • Include guidance for using REST API calls directly, which are platform-agnostic.
  • Avoid presenting PowerShell as the default or primary method unless it is truly required.
GitHub Create Pull Request
Storage Quickstart: Deploy a static website on Azure Storage using Terraform ...e/blobs/storage-quickstart-static-website-terraform.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for verifying results, but PowerShell is given equal prominence despite being Windows-specific. There is no explicit Linux/macOS example (such as Bash), and PowerShell is listed as a main tab, which may create friction for non-Windows users.
Recommendations
  • Add explicit Bash/Linux/macOS command examples alongside Azure CLI and PowerShell.
  • List Azure CLI (cross-platform) examples first, and clarify that PowerShell is Windows-only.
  • Consider removing or demoting PowerShell examples unless there is a unique Windows-only step.
  • Add notes or links for Linux/macOS users where relevant.
GitHub Create Pull Request
Storage Configure customer-managed keys in the same tenant for a new storage account .../common/customer-managed-keys-configure-new-account.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation presents Azure portal instructions first, followed by PowerShell examples before Azure CLI examples in each section. PowerShell is a Windows-centric tool, and its precedence may subtly favor Windows users. However, Azure CLI examples are provided in full, and no steps are exclusive to Windows or PowerShell. There are no missing Linux/macOS examples, and all CLI commands are cross-platform.
Recommendations
  • Alternate the order of PowerShell and Azure CLI examples, or present CLI examples first to better serve Linux/macOS users.
  • Explicitly note that Azure CLI commands work on Linux/macOS and Windows, and provide any OS-specific caveats if relevant.
  • Consider adding a short section or note for users who prefer Bash scripting, highlighting cross-platform compatibility.
  • If possible, include screenshots or references for Azure CLI usage in addition to portal screenshots.
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
Low Priority View Details →
Scanned: 2026-01-12 00:00
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 presented as a primary command-line example, which is Windows-centric. Although Azure CLI is cross-platform and included, PowerShell is listed before CLI, and no Linux/macOS shell examples (e.g., Bash) are provided. There is a mild Windows-first bias and a reliance on PowerShell for scripting examples.
Recommendations
  • Present Azure CLI examples before PowerShell, as CLI is cross-platform.
  • Include explicit Bash or shell examples for Linux/macOS users, especially for scripting scenarios.
  • Clarify that PowerShell is primarily for Windows users, and Azure CLI is recommended for Linux/macOS.
  • Add notes or links to platform-specific guidance where relevant.
GitHub Create Pull Request
Storage Enforce a Minimum Required Version of Transport Layer Security (TLS) ...https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/transport-layer-security-configure-minimum-version.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation page displays mild Windows bias, notably by referencing Windows-specific implementation details and mentioning PowerShell before Azure CLI in the configuration section. The page states that Azure Storage relies on the Windows implementation of SSL, and links to PowerShell-based configuration and troubleshooting before CLI and template methods. However, Azure CLI examples are provided and are cross-platform, and no critical steps are Windows-only.
Recommendations
  • Clarify that Azure CLI is fully supported on Linux/macOS and provide explicit instructions for installing and using it on those platforms.
  • Avoid language that implies Windows is the default or preferred platform (e.g., 'Windows implementation of SSL') unless strictly necessary for technical accuracy; consider mentioning OpenSSL or platform differences where relevant.
  • Present Azure CLI examples before PowerShell, as CLI is cross-platform and more accessible to Linux/macOS users.
  • Where screenshots or instructions reference the Azure portal, note that it is accessible from any OS.
  • If any troubleshooting or advanced configuration is Windows-specific, provide Linux/macOS equivalents or note limitations.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation provides AzCopy command examples using single quotes for path arguments, with a recurring tip that Windows Command Shell (cmd.exe) users should use double quotes instead. This tip is presented before any mention of Linux or macOS shells, subtly prioritizing Windows users. However, all command examples themselves use single quotes, which are correct for Linux/macOS shells, and no PowerShell- or Windows-only tools are used. No Linux examples are missing, and Linux/macOS users can follow all instructions without issue.
Recommendations
  • Rephrase the quoting tip to mention Linux/macOS shells first, or present both quoting styles side-by-side for parity.
  • Explicitly state that the examples are ready to use in Linux/macOS shells, and provide a Windows/cmd.exe variant for each example if possible.
  • Consider adding a short section clarifying cross-platform usage and shell differences up front.
GitHub Create Pull Request
Storage Configure a Site-to-Site VPN for Azure Files ...icles/storage/files/storage-files-configure-s2s-vpn.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation page exhibits mild Windows bias by explicitly recommending Windows Server RRAS as a network appliance in the prerequisites section, mentioning it before any Linux alternatives. No Linux appliances or configuration guides are referenced or linked, and the only concrete appliance example is Windows. However, the main configuration steps (Azure Portal, PowerShell, CLI) are cross-platform and do not depend on Windows-specific tools. Mounting instructions for Windows, macOS, and Linux are provided via links, and CLI examples are platform-agnostic.
Recommendations
  • Mention and link to common Linux VPN appliances (e.g., strongSwan, OpenVPN, libreswan) in the prerequisites section alongside Windows RRAS.
  • Provide or link to configuration guides for Linux-based VPN appliances, similar to the Windows RRAS link.
  • Clarify that the choice of on-premises VPN appliance is agnostic and provide parity in examples and references for Linux and Windows.
  • Consider listing Linux appliances before or alongside Windows RRAS to avoid ordering bias.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation provides both PowerShell and Bash examples for project creation, but lists PowerShell first, which is a subtle form of Windows-first bias. All other instructions and code samples are platform-neutral and do not favor Windows tools or patterns. No critical steps are Windows-only, and Linux/macOS users can follow the quickstart without friction.
Recommendations
  • Present Bash and PowerShell examples side-by-side or alternate which is shown first to avoid implicit prioritization.
  • Explicitly state that all commands work equally on Windows, Linux, and macOS.
  • Consider adding a short note in the prerequisites or setup section confirming cross-platform compatibility.
GitHub Create Pull Request
Storage Access control lists in Azure Data Lake Storage ...cles/storage/blobs/data-lake-storage-access-control.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page demonstrates mild Windows bias. In the 'How to set ACLs' section, Windows-centric tools (Azure Storage Explorer, PowerShell) are listed before cross-platform or Linux-native options (Azure CLI, REST API). PowerShell is given its own row, while no equivalent is provided for Bash or Linux shell scripting. Azure Storage Explorer, a GUI tool primarily used on Windows, is also highlighted. There are no explicit Linux command-line examples (e.g., Bash, setfacl), and no mention of Linux-specific patterns for managing ACLs, though Azure CLI is included (which is cross-platform). The page does reference POSIX and Linux in conceptual sections and links to Linux resources, but practical guidance and examples skew toward Windows tools and workflows.
Recommendations
  • Add explicit Linux/Bash examples for managing ACLs, such as using Azure CLI from a Linux shell.
  • Include references to Linux-native tools or scripting patterns where applicable.
  • Reorder the 'How to set ACLs' table to list cross-platform tools (Azure CLI, REST API) before Windows-specific tools (PowerShell, Storage Explorer).
  • Add a note clarifying that Azure CLI and REST API are fully supported on Linux/macOS.
  • Consider including a section or FAQ entry for Linux/macOS users outlining best practices for managing ACLs from those platforms.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation page is generally cross-platform, focusing on Azure CLI commands that work on Windows, Linux, and macOS. However, in the 'Ensure that you have the correct version of Azure CLI installed' section, Windows PowerShell is mentioned as the example console application before any Linux/macOS alternatives, and no explicit mention is made of Linux/macOS terminal applications. No PowerShell-specific commands or Windows-only tools are used, and all CLI commands are platform-agnostic.
Recommendations
  • Explicitly mention Linux/macOS terminal applications (e.g., Terminal, Bash, zsh) alongside Windows PowerShell when instructing users to open a command console.
  • Add a note clarifying that all Azure CLI commands shown work equally on Linux, macOS, and Windows.
  • Consider providing a screenshot or example output from a Linux/macOS terminal in addition to (or instead of) Windows environments if any are shown.
  • Where possible, avoid listing Windows tools first unless there is a technical reason.
GitHub Create Pull Request
Storage Use Azure CLI to manage data (Azure Data Lake Storage) ...rage/blobs/data-lake-storage-directory-file-acl-cli.md
Low 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 exhibits mild Windows bias by referencing Windows PowerShell as the example local console and using Windows-style file paths (e.g., C:\myFolder\upload.txt) in upload/download commands. There are no explicit Linux/macOS examples or mentions of equivalent Linux terminals or file path formats. This may cause minor confusion or friction for Linux/macOS users, though the Azure CLI commands themselves are cross-platform.
Recommendations
  • Explicitly mention Linux/macOS terminal options (e.g., Bash, Terminal.app) alongside Windows PowerShell.
  • Provide Linux/macOS file path examples (e.g., /home/user/upload.txt) in upload/download commands, either in parallel or as alternatives.
  • Add a note clarifying that file paths should be adapted to the user's OS.
  • Ensure that instructions and examples are OS-neutral or include both formats where relevant.
GitHub Create Pull Request
Storage Encryption scopes for Blob storage ...in/articles/storage/blobs/encryption-scope-overview.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page displays minor Windows bias in the section discussing Azure Key Vault recovery, where PowerShell is mentioned before CLI, and the link text for PowerShell is more prominent. No Linux-specific tools or examples are provided, and there is no mention of Bash, Linux shell, or macOS-specific guidance. However, the overall content is mostly conceptual and platform-neutral, with only a small section referencing Windows tooling.
Recommendations
  • Present CLI and PowerShell examples side-by-side, or mention CLI first to avoid Windows-first bias.
  • Add explicit references to Bash or Linux/macOS shell usage where relevant.
  • Ensure that all command-line instructions are available for both Windows (PowerShell) and Linux/macOS (CLI/Bash).
  • Where possible, provide cross-platform code snippets or clarify platform compatibility.
GitHub Create Pull Request
Storage Known issues with NFS 3.0 in Azure Blob Storage ...age/blobs/network-file-system-protocol-known-issues.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation mentions Windows in the client support section, noting that Windows NFS clients are not supported and suggesting a workaround via WSL2. Additionally, enabling static websites is described as only possible via PowerShell or Azure CLI, with PowerShell mentioned first. There are no explicit Linux/macOS examples, but the overall focus is on platform limitations rather than usage examples.
Recommendations
  • Provide explicit Linux and macOS usage examples for mounting NFS shares and managing ACLs.
  • List Azure CLI before PowerShell or present both equally when describing feature enablement.
  • Clarify Linux/macOS compatibility for all features and workarounds, not just Windows.
  • Include Linux-specific commands (e.g., mount, showmount) with example usage.
  • Add a table summarizing client support for Windows, Linux, and macOS.
GitHub Create Pull Request
Storage Quickstart: Azure Blob storage library v12 - JS Browser ...s/storage/blobs/quickstart-blobs-javascript-browser.md
Low 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 demonstrates a mild Windows bias by listing Windows tools (cmd, PowerShell) before Bash when referring to the console window, and by recommending Visual Studio Code as the editor without mentioning alternatives. There are no explicit Linux/macOS-specific instructions or examples, and the setup steps (such as running npm commands and opening the editor) are shown in a way that may be more familiar to Windows users. However, the core instructions and code samples are cross-platform and do not depend on Windows-only tools.
Recommendations
  • Explicitly mention Bash and terminal usage for Linux/macOS users alongside cmd and PowerShell.
  • Include a note that Visual Studio Code is available on Linux/macOS, or suggest alternative editors.
  • Add a brief section or callout for Linux/macOS users, confirming that all commands work on their platforms.
  • Show example commands for installing Node.js via package managers (apt, brew, etc.) for Linux/macOS.
  • Clarify that the npm and bundler steps are platform-agnostic.
GitHub Create Pull Request
Storage SSH File Transfer Protocol (SFTP) performance considerations in Azure Blob storage ...age/blobs/secure-file-transfer-protocol-performance.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation demonstrates a mild Windows bias by mentioning Windows-specific tools (WinSCP) first and providing Windows OpenSSH examples before Linux equivalents. The use of WinSCP and FileZilla as primary client examples may also favor Windows users, as these are most commonly associated with Windows environments. However, Linux usage is acknowledged with an OpenSSH example, and no critical functionality is missing for Linux/macOS users.
Recommendations
  • Alternate the order of Windows and Linux examples, or present them together for parity.
  • Include explicit Linux/macOS client recommendations (e.g., lftp, Nautilus, or command-line sftp).
  • Provide configuration examples for popular Linux/macOS SFTP clients.
  • Avoid assuming WinSCP/FileZilla as default; mention cross-platform alternatives.
  • Clarify that all recommendations apply equally to Linux/macOS unless noted.
GitHub Create Pull Request
Storage Authorize access to Azure Blob Storage for an SFTP client ...secure-file-transfer-protocol-support-authorize-access.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
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, and Azure CLI, but the PowerShell examples are extensive and shown before Azure CLI. PowerShell is primarily a Windows tool, and its prominence may create friction for Linux/macOS users. However, Azure CLI examples are present and cover all major steps, and references to Linux tools (e.g., ssh-keygen) are included. There are no sections that are Windows-only, but the ordering and depth of PowerShell coverage indicate a mild Windows bias.
Recommendations
  • Present Azure CLI examples before PowerShell, as CLI is cross-platform and preferred by many Linux/macOS users.
  • Ensure CLI examples are as detailed as PowerShell examples, including all relevant parameters and output.
  • Add explicit notes or sections for Linux/macOS users, such as common shell commands or troubleshooting tips.
  • Consider adding bash script examples for common tasks to further improve parity.
GitHub Create Pull Request
Storage Map a custom domain to an Azure Blob Storage endpoint ...n/articles/storage/blobs/storage-custom-domain-name.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation consistently presents Windows-centric tools and patterns first, notably listing Azure Portal and PowerShell before Azure CLI in all procedural tabs. PowerShell examples are provided for every operation, and the CLI examples are sometimes labeled as 'PowerShell command' (even though they are CLI), which may confuse Linux/macOS users. There are no explicit Linux/macOS-specific instructions or screenshots, and the Azure Portal UI is described without noting platform differences. However, Azure CLI is included for all tasks, so Linux/macOS users can complete the procedures.
Recommendations
  • Present Azure CLI examples before PowerShell examples, or at least alternate the order to avoid Windows-first bias.
  • Correct labeling so CLI commands are not described as 'PowerShell command'.
  • Add notes or screenshots indicating that Azure Portal is web-based and platform-agnostic.
  • Explicitly mention that Azure CLI works on Linux/macOS and provide installation links.
  • Consider including bash shell snippets for common DNS tasks or validation steps, where appropriate.
GitHub Create Pull Request
Storage Quickstart: Azure Blob storage library - JavaScript ...icles/storage/blobs/storage-quickstart-blobs-nodejs.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page demonstrates mild Windows bias in several areas. Windows-specific tools (cmd, PowerShell, Visual Studio Code) are mentioned first or exclusively in some instructions, such as opening the project in VS Code and signing in with PowerShell. Examples for setting environment variables are shown for Windows (cmd) before Linux (bash), and PowerShell is given its own sign-in instructions. Visual Studio Code is referenced as the default editor, which is more common on Windows. However, Linux equivalents (bash, export, .env files) are present, and most commands are cross-platform.
Recommendations
  • Present cross-platform instructions in parallel, or default to platform-neutral tools (e.g., 'terminal' instead of 'cmd/PowerShell').
  • List Linux/macOS instructions before or alongside Windows instructions to avoid Windows-first ordering.
  • Include explicit instructions for popular Linux/macOS editors (e.g., 'Open the project in your preferred editor, such as VS Code, Vim, or Sublime Text').
  • When referencing sign-in methods, mention Azure CLI and bash first, and clarify PowerShell is optional for Windows users.
  • Ensure all environment variable instructions are equally detailed for Linux/macOS and Windows.
GitHub Create Pull Request
Storage Blob Storage feature support in Azure storage accounts ...e/blobs/storage-feature-support-in-storage-accounts.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation references both Azure CLI and PowerShell commands for Blob Storage, but explicitly lists PowerShell (a Windows-centric tool) as a primary supported interface, with a dedicated row for 'Blob Storage PowerShell commands'. While Azure CLI is cross-platform, PowerShell is traditionally associated with Windows, and its mention alongside CLI may suggest a Windows-first mindset. No explicit Linux/macOS examples or tools (other than Blobfuse, which is correctly included) are highlighted. The order of tools in the tables (CLI then PowerShell) is neutral, but the presence of PowerShell as a first-class citizen may indicate mild Windows bias.
Recommendations
  • Add explicit mention of Linux/macOS equivalents for PowerShell commands, such as Bash scripts or Python SDK usage.
  • Clarify that Azure CLI is cross-platform and provide example commands for Linux/macOS environments.
  • Consider including sample usage for Blobfuse and other Linux-native tools in parity with PowerShell examples.
  • If PowerShell is referenced, note that it is available cross-platform, or link to installation instructions for Linux/macOS.
GitHub Create Pull Request
Storage Quickstart: Azure Blob Storage library - Java ...rticles/storage/blobs/storage-quickstart-blobs-java.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation provides both Windows (PowerShell, CMD) and Linux (Bash) examples for most commands, but Windows tools and patterns (PowerShell, setx, Connect-AzAccount) are often mentioned first or exclusively. In authentication instructions, PowerShell is given its own tab, and Windows environment variable setup is described before Linux. Output examples use Windows-style paths (C:\QuickStarts\blob-quickstart). Some instructions and screenshots are Windows-centric, which may create minor friction for Linux/macOS users.
Recommendations
  • Present Linux/macOS and Windows instructions side-by-side or alternate which is shown first.
  • Include explicit macOS instructions where applicable (e.g., environment variable setup).
  • Use platform-neutral language and examples (e.g., generic 'console window' instead of 'PowerShell').
  • Provide output examples using both Windows and Linux path formats.
  • Add notes clarifying any platform-specific differences, especially for file paths and environment variables.
GitHub Create Pull Request
Storage Enable and manage blob versioning .../blob/main/articles/storage/blobs/versioning-enable.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides examples for enabling and managing blob versioning using the Azure portal, PowerShell, Azure CLI, and ARM templates. PowerShell is given a dedicated section with detailed examples, and is listed before Azure CLI in both major tasks. There are no explicit Linux/macOS shell examples (e.g., Bash), nor is there mention of platform-specific considerations for Linux users. The Azure CLI examples are generic and could be run on any platform, but the prominence and detail of PowerShell coverage, and its placement before CLI, indicate a mild Windows bias.
Recommendations
  • Add explicit Bash examples for Azure CLI commands, showing usage in Linux/macOS terminals.
  • Clarify that Azure CLI commands work cross-platform and provide any necessary platform-specific notes (e.g., environment variable syntax differences).
  • Consider alternating the order of PowerShell and CLI examples, or presenting CLI first to reflect its cross-platform nature.
  • Mention that PowerShell Core is available on Linux/macOS if users prefer PowerShell, and provide installation guidance.
GitHub Create Pull Request
← Previous Page 12 of 16 Next →