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 1276-1300 of 1657 flagged pages
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/file-sync/file-sync-scale-targets.md .../articles/storage/file-sync/file-sync-scale-targets.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 is heavily focused on Windows Server, explicitly stating that Azure File Sync extends Azure Files to Windows Server and that the agent runs on Windows Server. There are no mentions of Linux support, Linux equivalents, or cross-platform considerations. All examples, performance metrics, and deployment guidance are given exclusively for Windows environments, with no reference to Linux tools, patterns, or compatibility.
Recommendations
  • Clarify whether Azure File Sync supports only Windows Server or if there are plans for Linux support.
  • If Linux is supported or planned, provide equivalent examples, deployment guidance, and performance metrics for Linux environments.
  • Explicitly mention platform limitations and alternatives for Linux users, such as using Azure Files natively or other sync solutions.
  • Add a section comparing Windows and Linux support, including any differences in agent capabilities, performance, and deployment steps.
  • Ensure that cross-platform parity is addressed in future updates, with examples and documentation for both Windows and Linux where applicable.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/blob-storage-monitoring-scenarios.md ...les/storage/blobs/blob-storage-monitoring-scenarios.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page demonstrates mild Windows bias. While most examples are platform-neutral (Kusto queries, SQL, Azure portal), the only explicit code example for decoding a SAS token signature is given in PowerShell first, with the Linux equivalent (bash/python) mentioned second. No Linux-specific tools or workflows are highlighted, and the PowerShell example appears before the Linux alternative, suggesting a Windows-first approach.
Recommendations
  • Present Linux and Windows examples side-by-side, or alternate which comes first to avoid implicit prioritization.
  • Include CLI examples using cross-platform tools (e.g., Azure CLI, Python, Bash) wherever possible.
  • Explicitly mention that all examples are cross-platform unless otherwise noted.
  • Add references to Linux-native tools (e.g., openssl, sha256sum, curl) for relevant tasks.
  • Where PowerShell is used, clarify that PowerShell Core is available on Linux and macOS, or provide direct Linux shell alternatives.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/blob-inventory.md ...ocs/blob/main/articles/storage/blobs/blob-inventory.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 for Azure Storage blob inventory does not provide any explicit Windows or PowerShell command-line examples, nor does it mention Windows-specific tools or patterns. However, there is subtle Windows bias in the presentation: the only screenshot of an inventory CSV file is shown opened in Microsoft Excel, a Windows-centric application, and there are no equivalent examples or screenshots for Linux tools (such as viewing CSVs in LibreOffice Calc, using 'cat', 'head', or 'csvkit'). There are no references to Linux command-line usage, nor are Linux-friendly workflows (such as processing CSVs with shell utilities) discussed. The documentation implicitly assumes a Windows environment for viewing and interacting with inventory output files.
Recommendations
  • Add examples or screenshots showing how to view and process inventory CSV files using Linux tools (e.g., LibreOffice Calc, csvkit, awk, head, tail, cat).
  • Mention cross-platform options for viewing and analyzing CSV and Parquet files, such as Python pandas, Apache Arrow, or CLI utilities available on Linux.
  • Avoid referencing or showing only Windows-centric applications (like Microsoft Excel) without providing Linux alternatives.
  • Explicitly state that inventory output files can be processed on any OS and provide sample commands for both Windows and Linux environments.
  • Include a section on automating inventory report processing using shell scripts or Linux command-line tools.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/tables/assign-azure-role-data-access.md ...ticles/storage/tables/assign-azure-role-data-access.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation presents both PowerShell and Azure CLI examples for assigning Azure roles, but PowerShell is listed first and described in greater detail, including links to further PowerShell-specific documentation. This ordering and emphasis may subtly favor Windows users, as PowerShell is traditionally associated with Windows environments, while Azure CLI is more cross-platform. No Linux-specific tools or shell examples (e.g., bash) are provided, and there is no mention of Linux-specific considerations or parity.
Recommendations
  • Alternate the order of PowerShell and Azure CLI sections, or present Azure CLI first to avoid implicit Windows prioritization.
  • Provide explicit bash or Linux shell examples for Azure CLI commands to demonstrate cross-platform usage.
  • Add a note clarifying that both PowerShell and Azure CLI are available on Windows, Linux, and macOS, and link to installation guides for each platform.
  • Include troubleshooting or usage tips for Linux users (e.g., authentication, environment setup) where relevant.
  • Ensure that references to further documentation are balanced between PowerShell and Azure CLI, and include links to cross-platform resources.
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-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page exhibits Windows bias primarily in the way local environment examples and file paths are presented. The instructions for running Azure CLI locally mention Windows PowerShell as the example console application, and file path examples for upload and download operations use Windows-style paths (e.g., 'C:\myFolder\upload.txt') exclusively. There are no Linux or macOS equivalents shown for terminal usage or file paths, and no mention of Bash, zsh, or other common Linux shells.
Recommendations
  • Include Linux and macOS terminal examples alongside Windows PowerShell, such as referencing Bash or Terminal.
  • Provide file path examples using both Windows (e.g., 'C:\myFolder\upload.txt') and Linux/macOS (e.g., '/home/user/upload.txt') formats for upload/download commands.
  • Explicitly state that the Azure CLI works cross-platform and mention how to adapt commands for different operating systems.
  • Add notes or callouts for OS-specific behaviors, if any, especially regarding file paths and shell usage.
  • Consider alternating the order of examples or presenting both Windows and Linux/macOS examples together to avoid implicit prioritization.
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-09 00:34
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 sample code in PowerShell for establishing SSH connections, even though the context is an HDInsight Hadoop cluster on Linux. The SSH example is given in PowerShell syntax, which is native to Windows, rather than Bash or a generic shell. There are no Linux shell (Bash) examples for connecting via SSH, and the initial connection instructions reference PowerShell before any Linux alternatives. The rest of the HDFS CLI examples are platform-neutral, but the initial setup favors Windows users.
Recommendations
  • Provide SSH connection examples using Bash (e.g., `ssh sshuser@clustername-ssh.azurehdinsight.net`) alongside or before PowerShell examples.
  • Clarify that SSH commands can be run from any standard terminal (Linux, macOS, Windows) and show cross-platform usage.
  • If PowerShell is mentioned, also include equivalent Linux/macOS shell commands for parity.
  • Explicitly state that the HDFS CLI commands are platform-agnostic and can be run from any OS with the Hadoop CLI installed.
  • Consider reordering examples so that Linux/Bash usage is presented first, especially since HDInsight clusters run on Linux.
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-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page exhibits mild Windows bias by mentioning PowerShell before CLI in the context of Azure Key Vault soft-delete recovery. The only explicit tool references for key vault recovery are 'How to use soft-delete with PowerShell' and 'How to use soft-delete with CLI', with PowerShell listed first. No Linux-specific tools or examples (such as Bash scripts or Linux-native utilities) are provided, and there are no explicit Linux command-line examples for managing encryption scopes or keys.
Recommendations
  • Alternate the order of tool references so that CLI (cross-platform) is mentioned before PowerShell, or mention both together without preference.
  • Provide explicit Linux/Bash examples for key vault and encryption scope management, where applicable.
  • Include references to Linux-native tools or scripting approaches (e.g., Bash, Azure CLI in Linux environments) alongside PowerShell.
  • Clarify that Azure CLI is cross-platform and suitable for both Windows and Linux users.
  • Ensure parity in documentation by offering examples and guidance for both Windows and Linux users throughout the page.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/immutable-container-level-worm-policies.md ...orage/blobs/immutable-container-level-worm-policies.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 Windows bias by referencing PowerShell commands first and providing detailed examples for Windows-centric tools (PowerShell) before mentioning cross-platform alternatives (Azure CLI). There is no mention of Linux-specific tools, nor are Linux shell examples provided. The documentation assumes familiarity with Windows tooling, potentially disadvantaging Linux users.
Recommendations
  • Provide Linux shell (bash) examples alongside PowerShell commands, especially for operations like container deletion.
  • Explicitly mention that Azure CLI is cross-platform and show its usage in both Windows and Linux environments.
  • Include guidance or examples for using REST API calls via curl or similar Linux-native tools.
  • Avoid referencing Windows tools (PowerShell) before cross-platform alternatives; present them in parallel or start with the most platform-agnostic option.
  • Add a section or note clarifying platform compatibility for all command-line tools mentioned.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/monitor-blob-storage-reference.md ...ticles/storage/blobs/monitor-blob-storage-reference.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 page contains subtle Windows bias, most notably in the example 'userAgentHeader' field, which references a Windows-based browser user agent string ('Windows NT 10.0; Win64; x64'). There are no explicit platform-specific examples, but the only OS mentioned is Windows, and no Linux or cross-platform user agent strings are shown. There are no PowerShell-heavy examples or Windows-only tools referenced, but the presence of Windows in the example fields and lack of Linux parity is a mild form of bias.
Recommendations
  • Include example user agent strings from Linux and macOS clients alongside Windows examples to demonstrate cross-platform usage.
  • Explicitly mention that monitoring and logging applies equally to Linux, macOS, and Windows environments.
  • If relevant, provide sample log entries or client interactions from Linux-based tools (e.g., curl, wget, Azure CLI on Linux) to ensure parity.
  • Review all example fields and ensure they do not exclusively reference Windows unless necessary for the context.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/quickstart-blobs-javascript-browser.md ...s/storage/blobs/quickstart-blobs-javascript-browser.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 subtle Windows bias in its instructions for creating and running the JavaScript project. Console examples mention 'cmd' and 'PowerShell' before 'Bash', and the editor recommendation is exclusively 'Visual Studio Code', which is most popular on Windows. There are no explicit Linux-specific instructions or examples, and no mention of Linux-native editors or terminal environments. Additionally, the steps for running the app and opening the project do not address Linux-specific nuances (such as alternative editors or terminal commands).
Recommendations
  • Present console/terminal options in a platform-neutral order (e.g., 'Bash, cmd, or PowerShell') or provide separate instructions for Windows and Linux users.
  • Include explicit Linux examples for project setup, such as using 'touch' to create files, or referencing Linux-native editors (e.g., Vim, Nano, GNOME Text Editor) alongside Visual Studio Code.
  • Clarify that all commands work on both Windows and Linux, and note any platform-specific differences (such as file path separators or permissions).
  • Add a note or section for Linux users, highlighting any potential differences or considerations when following the quickstart.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/secure-file-transfer-protocol-known-issues.md ...ge/blobs/secure-file-transfer-protocol-known-issues.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 Windows bias by providing a client configuration example only for WinSCP, a Windows-focused SFTP client, without mentioning or providing equivalent guidance for popular Linux/macOS SFTP clients (such as OpenSSH's sftp, FileZilla, or lftp). The ordering and selection of examples prioritize Windows tools, and there is a lack of Linux-specific troubleshooting or configuration advice.
Recommendations
  • Add configuration examples and troubleshooting steps for common Linux/macOS SFTP clients (e.g., OpenSSH sftp, FileZilla, lftp).
  • Include notes about client settings or performance considerations for Linux tools where relevant.
  • Present client examples in a platform-neutral or parallel fashion (e.g., 'WinSCP (Windows), sftp (Linux/macOS)').
  • Explicitly mention any Linux/macOS-specific limitations or workarounds if applicable.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/simulate-primary-region-failure.md ...icles/storage/blobs/simulate-primary-region-failure.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 demonstrates a moderate Windows bias. Fiddler, a Windows-centric tool, is presented as a primary method for simulating failures, with no mention of Linux alternatives (such as mitmproxy or similar). In the static route section, both Windows and Linux commands are provided, but Windows instructions and tools (e.g., ipconfig, Fiddler) are mentioned first or exclusively, and the prerequisite for an 'elevated command prompt' is a Windows-specific concept. The tutorial does not provide Linux equivalents for all tools and patterns, especially in the Fiddler section.
Recommendations
  • Include Linux-friendly alternatives to Fiddler, such as mitmproxy, with equivalent instructions and code samples.
  • Present platform instructions in parallel (side-by-side or grouped by OS) rather than listing Windows first.
  • Clarify prerequisites for both Windows and Linux (e.g., 'elevated command prompt or root terminal').
  • Provide Linux equivalents for all tools mentioned (e.g., mention 'ifconfig' and 'ip a' alongside 'ipconfig').
  • Where screenshots or UI instructions are given for Windows tools, offer comparable guidance for Linux alternatives.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/storage-blob-event-overview.md .../articles/storage/blobs/storage-blob-event-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 presents quickstart links for three tools: Azure portal, PowerShell, and Azure CLI. PowerShell (a Windows-centric tool) is listed before Azure CLI (which is cross-platform and preferred on Linux/macOS). No Linux-specific shell examples (e.g., Bash) or explicit mention of Linux environments is provided. The page does not include Linux-first instructions or examples, and PowerShell is given prominence by being listed before CLI.
Recommendations
  • List Azure CLI before PowerShell in quickstart tables and instructions, as CLI is cross-platform and widely used on Linux.
  • Add explicit Bash or Linux shell examples where relevant, especially for event subscription and filtering tasks.
  • Include notes or sections clarifying that all features and instructions are supported on Linux and macOS, not just Windows.
  • Avoid giving Windows-centric tools (like PowerShell) priority in documentation structure unless there is a technical reason.
  • Where PowerShell is referenced, consider also providing equivalent Bash/CLI commands for parity.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/storage-blobs-tune-upload-download.md ...es/storage/blobs/storage-blobs-tune-upload-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 page focuses exclusively on .NET and C# examples, with all code samples and configuration instructions tailored to Windows environments (e.g., ServicePointManager, ThreadPool). There are no references to Linux-specific considerations, tools, or code samples. The guidance assumes a Windows/.NET developer context and omits mention of cross-platform differences or Linux best practices.
Recommendations
  • Include explicit notes or sections on Linux/Unix environments, such as differences in connection pooling, threading, or file system behavior.
  • Provide equivalent code samples for .NET Core/.NET 6+ running on Linux, and clarify any platform-specific behaviors.
  • Mention any relevant Linux tools or patterns (e.g., ulimit, system resource limits) that may affect performance tuning.
  • Discuss how the Azure Storage client library behaves on Linux, including any caveats or optimizations.
  • Ensure that examples and recommendations are not Windows-centric and highlight cross-platform compatibility.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/customer-managed-keys-overview.md ...icles/storage/common/customer-managed-keys-overview.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 page is largely platform-neutral, focusing on Azure services and concepts. However, there are subtle signs of Windows bias: (1) In the section on Azure managed disks, the link for Windows is listed before Linux, suggesting a 'windows_first' ordering; (2) The mention of using PowerShell to revoke access is explicit, while Azure CLI is also mentioned but not given equal prominence or example parity. No Linux-specific tools, shell examples, or cross-platform command examples are provided, and there is no explicit mention of Linux workflows or tools.
Recommendations
  • Ensure that Azure CLI examples are provided and given equal prominence to PowerShell, especially in sections discussing operational tasks like revoking access.
  • Where possible, include bash/shell script examples alongside PowerShell to demonstrate Linux parity.
  • When referencing platform-specific documentation (e.g., disk encryption), alternate the order of Windows and Linux links or present them together to avoid implicit prioritization.
  • Explicitly mention that all operations can be performed from Linux, macOS, and Windows environments, and link to cross-platform tooling guides.
  • Audit linked articles to ensure Linux examples and workflows are present and up-to-date.
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-09 00:34
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. However, the PowerShell example is presented first, which may suggest a Windows-first or PowerShell-preferred approach. There is no explicit Linux shell (bash) example, but the Azure CLI example is cross-platform. No exclusive mention of Windows-only tools or patterns is present, but the ordering and emphasis on PowerShell may indicate a subtle Windows bias.
Recommendations
  • Alternate the order of examples, sometimes presenting Azure CLI (bash) first to avoid implicit prioritization of PowerShell/Windows.
  • Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows to reinforce cross-platform parity.
  • Consider providing a bash shell example (if different from Azure CLI usage) to further support Linux users.
  • Add a note clarifying that PowerShell is available cross-platform, or link to installation instructions for non-Windows systems if PowerShell is emphasized.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/lock-account-resource.md .../main/articles/storage/common/lock-account-resource.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides step-by-step instructions for applying a Resource Manager lock via the Azure Portal, PowerShell, and Azure CLI. The PowerShell example is given before the Azure CLI example, which may suggest a Windows-first approach. The PowerShell instructions reference the Az PowerShell module, a Windows-centric tool, and provide a detailed example. While the Azure CLI example is present and cross-platform, there are no explicit Linux shell or scripting examples, nor is there mention of Linux-specific considerations or tools.
Recommendations
  • Present Azure CLI examples before PowerShell examples, as CLI is cross-platform and more commonly used on Linux.
  • Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows.
  • Include Linux shell scripting examples (e.g., bash) for automation scenarios.
  • Reference installation instructions for Azure CLI on Linux.
  • Avoid implying PowerShell is the default or preferred automation tool; clarify parity between PowerShell and CLI.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/sas-expiration-policy.md .../main/articles/storage/common/sas-expiration-policy.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 PowerShell instructions before Azure CLI, and providing detailed PowerShell examples. The Azure portal (GUI) instructions are platform-neutral but are commonly associated with Windows environments. There are no explicit Linux shell examples (e.g., Bash), nor is there mention of Linux-specific tools or patterns. However, the inclusion of Azure CLI instructions does provide cross-platform parity, as Azure CLI is available on both Windows and Linux.
Recommendations
  • Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and consider providing Bash shell examples or notes for Linux users.
  • Add a note clarifying that PowerShell is available cross-platform, but that Bash users can use Azure CLI for equivalent functionality.
  • Consider listing Azure CLI instructions before PowerShell, or side-by-side, to avoid implying Windows-first workflows.
  • Include troubleshooting tips or environment setup notes for Linux users (e.g., installing Azure CLI on Ubuntu).
  • Where screenshots are shown, clarify that the Azure portal is accessible from any OS via a web browser.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/storage-choose-data-transfer-solution.md ...torage/common/storage-choose-data-transfer-solution.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 mild Windows bias by listing Azure PowerShell before Azure CLI in the 'scripted or programmatic transfer' section and by providing a PowerShell quickstart link before the CLI equivalent in the 'Next steps'. While Linux-compatible tools (AzCopy, Azure CLI) are mentioned, PowerShell is given precedence, and there are no explicit Linux-specific examples or guidance. No Windows-only tools are referenced, but the ordering and emphasis favor Windows users.
Recommendations
  • Alternate the order of PowerShell and CLI examples to avoid implicit prioritization.
  • Provide explicit Linux usage examples, such as shell scripts or command-line instructions for AzCopy and Azure CLI.
  • Include a note clarifying cross-platform compatibility for all tools mentioned.
  • Add references to Linux-specific documentation or troubleshooting guides where relevant.
  • Ensure graphical tools (like Storage Explorer) are described as cross-platform.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/storage-explorer-network.md ...in/articles/storage/common/storage-explorer-network.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 describes proxy configuration in Azure Storage Explorer but omits explicit examples or instructions for Linux environments. It references 'system proxy' settings and the Chromium networking stack, but does not detail how to configure system proxies on Linux or macOS, nor does it mention Linux-specific tools or patterns. The guidance to 'first try using system proxy' implicitly assumes familiarity with Windows proxy configuration, and no Linux or cross-platform parity is provided.
Recommendations
  • Add explicit instructions or examples for configuring system proxy settings on Linux (e.g., using GNOME/KDE network settings, environment variables, or CLI tools like 'gsettings' or 'network-manager').
  • Include references to macOS proxy configuration for completeness.
  • Provide parity in troubleshooting steps and proxy authentication details for Linux and macOS environments.
  • Mention common Linux proxy tools (e.g., 'cntlm', 'proxychains') and how they interact with Storage Explorer.
  • Clarify if NTLM/Negotiate authentication is supported on non-Windows platforms and provide guidance if limitations exist.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/storage-network-security-ip-address-range.md ...ge/common/storage-network-security-ip-address-range.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides detailed instructions for both Azure PowerShell and Azure CLI, but the PowerShell section is presented before the CLI section, which may suggest a Windows-first approach. The PowerShell examples are extensive, and there is no mention of Linux-specific tools or shell patterns (such as Bash scripting or Linux package managers for installation). While Azure CLI is cross-platform and included, the ordering and emphasis on PowerShell may indicate a subtle Windows bias.
Recommendations
  • Present Azure CLI instructions before PowerShell, as CLI is natively cross-platform and preferred by many Linux users.
  • Explicitly mention that Azure CLI works on Linux, macOS, and Windows, and provide installation instructions for Linux (e.g., using apt, yum, or zypper).
  • Include example commands using Bash scripting or note how to use Azure CLI in Linux shell environments.
  • Consider adding a note about PowerShell Core availability on Linux, if PowerShell examples are retained, to clarify cross-platform support.
  • Review other documentation pages for similar ordering or emphasis and standardize to prioritize cross-platform tools.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/storage-network-security-set-default-access.md .../common/storage-network-security-set-default-access.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides step-by-step instructions for configuring Azure Storage network access via the Portal, PowerShell, and Azure CLI. The PowerShell section is given before the Azure CLI section, and PowerShell is a Windows-centric tool, which may indicate a subtle Windows-first bias. There are no explicit Linux shell examples (e.g., Bash), nor is there mention of Linux-specific tools or patterns. However, the Azure CLI examples are cross-platform, which partially mitigates the bias.
Recommendations
  • Present Azure CLI instructions before PowerShell, as CLI is cross-platform and more commonly used on Linux.
  • Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows.
  • Add Bash shell scripting examples or usage notes for Linux users.
  • Consider including a table comparing PowerShell and CLI usage across platforms.
  • Clarify that PowerShell Core is available on Linux, but CLI is generally preferred for Linux environments.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/storage-solution-small-dataset-low-moderate-network.md ...ttps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/storage-solution-small-dataset-low-moderate-network.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation lists scripting/programmatic tools as 'AzCopy/PowerShell/Azure CLI', placing PowerShell before Azure CLI, which is more cross-platform. PowerShell is mentioned as a primary scripting option, despite being Windows-centric (though now available on Linux, its usage is still more common on Windows). No explicit Linux shell or bash examples are given, and no Linux-specific patterns or tools (such as bash scripts or Linux file utilities) are mentioned. The examples and recommendations subtly prioritize Windows tools and workflows.
Recommendations
  • Provide explicit Linux/bash shell examples alongside PowerShell, such as using AzCopy from bash or integrating with Linux scripting.
  • Mention Azure CLI before PowerShell in lists, as it is more cross-platform and commonly used on Linux.
  • Clarify that PowerShell is available on Linux, but also suggest bash or other Linux-native scripting approaches.
  • Include references or links to Linux-specific documentation or tutorials for Azure data transfer.
  • Add examples of using AzCopy in Linux environments, including installation instructions and sample commands.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/storage-srp-dotnet-get-started.md ...icles/storage/common/storage-srp-dotnet-get-started.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 Windows bias by referencing Azure PowerShell and Azure CLI as registration methods, but does not provide explicit Linux-specific instructions or examples. The setup instructions use the 'dotnet' CLI, which is cross-platform, but there are no examples or guidance for Linux-specific authentication patterns, environment variable setup, or troubleshooting. Windows tools (Azure PowerShell) are mentioned before Linux equivalents (Azure CLI), and there is no mention of Linux shell commands or environment setup.
Recommendations
  • Add explicit Linux shell examples for environment variable setup and authentication (e.g., export commands for bash/zsh).
  • Provide parity in registration instructions by including Linux-specific CLI commands and troubleshooting steps.
  • Mention cross-platform compatibility of the .NET SDK and clarify any OS-specific differences in authentication flows.
  • Ensure that Azure CLI is presented before or alongside Azure PowerShell, and clarify that both are available on Linux and Windows.
  • Include notes or links to Linux-specific documentation for common developer scenarios.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/storage-require-secure-transfer.md ...cles/storage/common/storage-require-secure-transfer.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 Windows bias by presenting PowerShell examples before Azure CLI examples and providing more detailed instructions for PowerShell, including module installation and connection steps. The CLI section is present but less detailed, and there are no explicit Linux shell or Bash examples, nor is there mention of Linux-specific tooling or workflows.
Recommendations
  • Present Azure CLI examples before or alongside PowerShell examples, as Azure CLI is cross-platform and widely used on Linux.
  • Include Bash shell examples for Linux users, demonstrating how to use Azure CLI in typical Linux environments.
  • Add notes or sections highlighting Linux compatibility and usage patterns, such as running Azure CLI commands in a Linux terminal.
  • Ensure installation instructions for Azure CLI are clear for Linux users, possibly linking to Linux-specific install guides.
  • Avoid assuming PowerShell as the default scripting environment; clarify that both PowerShell and CLI are supported and provide parity in example depth.
GitHub Create Pull Request
← Previous Page 52 of 67 Next →