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 376-400 of 1657 flagged pages
Storage Zonal Placement for Azure File Shares ...cs/blob/main/articles/storage/files/zonal-placement.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools Windows First
Summary
The documentation page demonstrates a Windows bias by exclusively providing command-line examples using Azure PowerShell, a tool primarily associated with Windows environments. There are no examples using Azure CLI, which is cross-platform and preferred by many Linux users. The documentation also references the Azure portal (web UI) and PowerShell first and exclusively, omitting Linux-native tools and workflows. No Bash, shell, or Azure CLI commands are provided, and there is no mention of Linux-specific considerations or parity.
Recommendations
  • Add equivalent Azure CLI examples for all PowerShell commands, as Azure CLI is cross-platform and widely used on Linux.
  • Include Bash/shell script examples where appropriate, especially for automation scenarios.
  • Explicitly mention that the steps can be performed on Linux/macOS using Azure CLI, and provide links to relevant CLI documentation.
  • Ensure that any tool or workflow mentioned (e.g., PowerShell) is accompanied by its Linux-friendly equivalent, or clarify platform limitations.
  • Consider reordering examples so that cross-platform tools (Azure CLI) are presented before or alongside Windows-centric tools (PowerShell).
GitHub Create Pull Request
Storage Examples for Azure role assignment conditions for Queue Storage ...n/articles/storage/queues/queues-auth-abac-examples.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides detailed examples for Azure role assignment conditions for Queue Storage, but all command-line examples use Azure PowerShell, which is primarily a Windows-centric tool. There are no equivalent examples using cross-platform or Linux-native tools such as Azure CLI, Bash, or scripting languages commonly used on Linux. The documentation assumes the use of PowerShell for scripting and automation, which may disadvantage Linux users or those preferring non-Windows environments.
Recommendations
  • Add equivalent examples using Azure CLI, which is cross-platform and widely used on Linux and macOS.
  • Include Bash scripting examples for automation tasks, especially for Linux users.
  • Explicitly mention that Azure PowerShell is available cross-platform, but also provide alternatives for users who do not use PowerShell.
  • Where possible, provide side-by-side examples for both PowerShell and Azure CLI/Bash to ensure parity and inclusivity.
  • Review references to tools and workflows to ensure they do not implicitly prioritize Windows environments.
GitHub Create Pull Request
Storage Best practices for monitoring Azure Queue Storage .../storage/queues/queues-storage-monitoring-scenarios.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation shows a moderate Windows bias. PowerShell is presented as the first example for monitoring queue message counts, and there is no mention of Linux-specific tools or shell commands (e.g., Bash). While Azure CLI is included (which is cross-platform), the absence of explicit Linux or Bash examples, and the prioritization of PowerShell, may disadvantage Linux users. No Linux-native tools or patterns are discussed.
Recommendations
  • Provide Bash or shell script examples alongside PowerShell, especially for common monitoring tasks.
  • Alternate the order of examples so that Azure CLI or Bash appears before PowerShell, or present them side-by-side.
  • Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and provide any necessary shell syntax for Linux users.
  • Where SDK examples are given, consider including Python or JavaScript (which are popular on Linux) in addition to .NET/C#.
  • Reference Linux-native monitoring/logging tools or patterns if relevant, or clarify that the guidance is OS-agnostic where possible.
GitHub Create Pull Request
Storage Performance and scalability checklist for Queue Storage ...ticles/storage/queues/storage-performance-checklist.md
High Priority View Details →
Scanned: 2026-01-10 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. It references Windows-specific tools (Network Monitor), mentions .NET Framework configuration in detail (a Windows-centric technology), and omits Linux-specific equivalents or examples (e.g., only Wireshark is mentioned as a cross-platform tool, but Network Monitor is Windows-only; .NET configuration is discussed without parity for other platforms). There are no PowerShell-heavy examples, but Azure CLI is only mentioned in passing, and Linux patterns/tools are not highlighted.
Recommendations
  • When mentioning diagnostic tools, list Linux equivalents (e.g., tcpdump, iftop) alongside Windows tools like Network Monitor.
  • Provide configuration examples for other major platforms and languages (e.g., Java, Python) with Linux-specific guidance where appropriate.
  • When discussing .NET configuration, add a note or section for Linux/Unix environments and other runtimes, or link to relevant documentation.
  • Ensure Azure CLI usage is demonstrated with examples, especially for Linux/macOS users, not just mentioning its existence.
  • Review all tool and code examples to ensure Linux parity and avoid implying Windows is the default or preferred platform.
GitHub Create Pull Request
Storage Tutorial: Work with Azure Queue Storage queues in .NET ...ain/articles/storage/queues/storage-tutorial-queues.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in several ways. Console examples and output use Windows-specific paths (e.g., C:\Tutorials), and Windows shells (cmd, PowerShell) are mentioned before cross-platform alternatives. There are no explicit Linux or macOS terminal examples, nor any mention of Linux-specific considerations (such as file paths, shell differences, or permissions). The tutorial assumes familiarity with Windows conventions and does not provide parity for Linux users.
Recommendations
  • Include Linux/macOS terminal examples alongside Windows (e.g., show bash/zsh commands and output).
  • Use platform-neutral paths in code/output samples (e.g., ~/Tutorials/QueueApp or /home/user/Tutorials/QueueApp).
  • Mention and demonstrate usage in common Linux shells (bash, zsh) and clarify that dotnet CLI works cross-platform.
  • Explicitly state that all commands work on Linux/macOS and Windows, and note any platform-specific caveats.
  • Add screenshots or output samples from Linux/macOS terminals.
  • Avoid listing Windows shells (cmd, PowerShell) before cross-platform alternatives unless contextually necessary.
GitHub Create Pull Request
Storage Back up your data to Azure with Commvault ...isaster-recovery/commvault/commvault-solution-guide.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by exclusively referencing the Azure portal (a GUI-centric, Windows-preferred interface) for all setup and configuration steps, with no mention of Linux CLI, Azure CLI, or PowerShell alternatives. All operational guidance and troubleshooting instructions assume use of the portal, and there are no examples or instructions for Linux environments or tools. Additionally, network monitoring tool recommendations are Windows-centric, with no mention of Linux-native options.
Recommendations
  • Add equivalent instructions for Azure Storage setup using Azure CLI and PowerShell, with explicit Linux shell examples.
  • Include guidance for configuring Commvault with Azure from Linux environments, such as using CLI tools or REST APIs.
  • List Linux-native network monitoring tools (e.g., iftop, nload, vnstat, Netdata) alongside Windows tools.
  • Provide screenshots or walkthroughs for Linux terminal usage where appropriate.
  • Clarify that Commvault and Azure integration steps can be performed from Linux servers, and link to relevant Linux documentation.
GitHub Create Pull Request
Storage Analyze and migrate your file data to Azure with Data Dynamics StorageX ...partners/data-management/storagex-quick-start-guide.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation demonstrates a Windows bias by prioritizing Windows-centric deployment steps, tools, and terminology. Examples and instructions focus on Active Directory, SMB, and Windows file servers, with little to no guidance for Linux environments or NFS workflows. Windows tools (e.g., portqryui) are mentioned exclusively, and installation paths and procedures reference Windows file system conventions. There is a lack of Linux-specific examples, commands, or troubleshooting steps, and Windows/Active Directory integration is assumed as the default.
Recommendations
  • Add explicit Linux/NFS deployment examples, including installation and configuration steps for StorageX on Linux servers.
  • Include Linux-native tools for network port checking (e.g., netcat, nmap) alongside Windows tools.
  • Provide guidance for environments without Active Directory, such as LDAP or local authentication for NFS-only migrations.
  • Show file paths and installation procedures for Linux systems, not just Windows (e.g., /var/log/storagex, /opt/storagex).
  • Ensure migration policy creation and resource addition steps include NFS/Linux server screenshots and instructions.
  • Clarify which steps are OS-agnostic and which require Windows, and offer alternatives where possible.
GitHub Create Pull Request
Storage Back up your data to Azure with DobiProtect ...-disaster-recovery/datadobi/datadobi-solution-guide.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates Windows bias by exclusively referencing the Azure portal (a GUI-centric, Windows-friendly tool) for all configuration steps, without mentioning CLI or automation alternatives commonly used on Linux (such as Azure CLI or PowerShell Core on Linux). All screenshots and step-by-step instructions are based on the Azure portal interface, with no examples for Linux command-line workflows. Additionally, network monitoring tool recommendations are heavily weighted toward Windows-centric or proprietary solutions, with no mention of open-source or Linux-native tools (e.g., iftop, nload, vnStat, or netstat). There are no Linux-specific instructions or parity for users who may prefer or require non-GUI, scriptable approaches.
Recommendations
  • Add equivalent instructions for configuring Azure Storage using Azure CLI and/or REST API, with example commands for Linux environments.
  • Include sample workflows for DobiSync integration using command-line tools or scripts, highlighting cross-platform compatibility.
  • Mention and provide examples of open-source, Linux-native network monitoring tools (such as iftop, vnStat, nload, or netstat) alongside proprietary solutions.
  • Clarify that Azure portal steps can be performed from any OS, but provide parity for users who prefer or require non-GUI, automated, or Linux-based workflows.
  • Where PowerShell is referenced, note that PowerShell Core is available cross-platform, and provide Linux usage examples if relevant.
GitHub Create Pull Request
Storage Migrate your file data to Azure with Datadobi DobiMigrate ...tners/data-management/dobimigrate-quick-start-guide.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates Windows bias by exclusively referencing Azure portal (a web GUI commonly used by Windows admins) for all configuration steps, omitting any CLI or Linux-based workflow. All examples and screenshots are based on the Azure portal GUI, with no mention of PowerShell, Azure CLI, or Linux shell commands. The network monitoring tools listed (SolarWinds, Paessler PRTG, Cisco Network Assistant, WhatsUp Gold) are primarily Windows-centric, with no mention of Linux-native alternatives. There are no examples or guidance for Linux users or administrators who may prefer command-line or automation-based approaches.
Recommendations
  • Add equivalent instructions for configuring Azure Files and storage accounts using Azure CLI and/or PowerShell, including sample commands.
  • Include Linux-native network monitoring tools (e.g., iftop, nload, vnstat, Netdata, Nagios) alongside Windows tools for bandwidth assessment.
  • Provide guidance for DobiMigrate deployment and configuration from Linux environments, including any prerequisites or differences.
  • Ensure screenshots and examples show both GUI and CLI workflows where possible.
  • Explicitly mention cross-platform compatibility and provide links to platform-specific documentation.
GitHub Create Pull Request
Storage Considerations for running ISV file services in Azure ...artners/primary-secondary-storage/isv-file-services.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page exhibits a moderate Windows bias. Several ISV solutions (Tiger Technology, XenData) are described as relying on Windows Server or NTFS, and features such as 'Windows Shell integration' and 'Disaster Recovery for Windows servers' are highlighted. The operating environment comparison lists 'Windows Server' for multiple solutions, with no mention of Linux equivalents or parity. There are no explicit Linux-focused examples, tools, or deployment patterns, and Windows-centric features are mentioned before or instead of Linux alternatives.
Recommendations
  • Include Linux-based deployment and management examples for each ISV solution, especially those currently described as Windows-centric.
  • Highlight Linux-compatible features and environments where available, such as support for ext4, XFS, or other Linux filesystems.
  • Add parity in feature descriptions, e.g., mention Linux desktop integration (Nautilus, KDE) alongside Windows Shell integration.
  • Where disaster recovery or backup is described for Windows servers, also describe equivalent Linux server scenarios.
  • Ensure that protocol and authentication support (e.g., LDAP, Kerberos) is described for both Windows and Linux environments.
  • Add explicit Linux usage patterns and best practices for Azure file services, including CLI and automation examples (e.g., Bash, Ansible, Terraform).
GitHub Create Pull Request
Storage Nasuni configuration guide for Microsoft Azure ...s/primary-secondary-storage/nasuni-deployment-guide.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation consistently uses Windows terminology and patterns, such as referring to 'Windows Azure Platform', and all screenshots and UI instructions are based on the Azure portal (which is platform-agnostic but often associated with Windows environments). There are no CLI examples (such as Azure CLI, PowerShell, or Bash), nor any Linux-specific guidance or parity for credential management, storage account creation, or firewall configuration. The documentation refers to 'Windows Azure Platform' in dropdowns and selections, and does not mention Linux or cross-platform command-line alternatives, nor does it provide examples for configuring Nasuni from Linux or via automation tools commonly used in Linux environments.
Recommendations
  • Add Azure CLI and/or Bash examples for all major steps (storage account creation, firewall configuration, credential retrieval) alongside portal instructions.
  • Clarify that the Azure portal is accessible from any OS and is not Windows-specific.
  • Replace or supplement 'Windows Azure Platform' terminology with 'Microsoft Azure' or 'Azure' to avoid Windows-centric language.
  • Provide guidance or examples for configuring Nasuni Edge Appliances from Linux environments, including credential management and DNS configuration.
  • Include references to automation tools (e.g., Terraform, Ansible) that are commonly used in Linux/cloud-native workflows.
  • Ensure screenshots and instructions do not imply a Windows-only workflow, and add notes or sections for Linux users where relevant.
GitHub Create Pull Request
Storage Performance and scalability checklist for Table storage ...ticles/storage/tables/storage-performance-checklist.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a mild Windows bias. It references Windows-centric tools (WireShark, NetMon), mentions PowerShell before Azure CLI when discussing supported tools, and links to a blog hosted on 'windowsazurestorage'. There are no explicit Linux or cross-platform command-line examples, and .NET configuration guidance is Windows/.NET Framework-centric, with only brief notes about other languages. No Linux-specific troubleshooting tools or patterns are mentioned, and Windows tools are referenced without Linux alternatives.
Recommendations
  • When mentioning network troubleshooting tools, include Linux equivalents such as tcpdump or iftop alongside WireShark and NetMon.
  • When listing supported client libraries and tools, mention Azure CLI before or alongside PowerShell, and clarify cross-platform support.
  • Provide configuration and performance tuning examples for other languages and platforms (e.g., Python, Java, Node.js), including Linux-specific guidance where relevant.
  • Avoid referencing Windows-specific blogs or resources unless Linux/cross-platform alternatives are also provided.
  • Explicitly state that the recommendations apply to both Windows and Linux environments, and highlight any platform-specific differences.
  • Add examples or links for Linux-based deployment, monitoring, and troubleshooting patterns.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/secure-file-transfer-protocol-support-how-to.md .../blobs/secure-file-transfer-protocol-support-how-to.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell examples are provided alongside Azure CLI, and PowerShell is listed before Azure CLI in each section. The use of PowerShell (a Windows-centric tool) and references to Set-AzStorageAccount command reinforce Windows patterns. There are no explicit Linux shell or Bash examples, nor any mention of Linux-specific tools or workflows, despite Azure CLI being cross-platform.
Recommendations
  • Add explicit Bash/Linux shell examples for Azure CLI usage, showing commands as they would be run in a typical Linux environment.
  • Clarify that Azure CLI commands work on Linux, macOS, and Windows, and provide installation guidance for non-Windows platforms.
  • Consider reordering examples to present Azure CLI before PowerShell, as CLI is cross-platform and more common in Linux environments.
  • Mention alternative Linux-native tools (such as curl for REST API calls) where appropriate.
  • Add notes or sections on how to perform these actions from Linux or macOS terminals, including any platform-specific considerations.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/secure-file-transfer-protocol-support-connect.md ...blobs/secure-file-transfer-protocol-support-connect.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by presenting only a Windows PowerShell example for connecting to Azure Blob Storage via SFTP, referencing Windows-specific tools first (PowerShell and OpenSSH for Windows), and omitting equivalent Linux/macOS command-line examples. No Linux or cross-platform connection instructions are provided, which may hinder accessibility for non-Windows users.
Recommendations
  • Add Linux and macOS connection examples using standard terminal commands (e.g., 'sftp' from bash/zsh).
  • Present platform-agnostic instructions first, or provide parallel examples for Windows, Linux, and macOS.
  • Reference OpenSSH generically, not just the Windows Server documentation, and link to cross-platform OpenSSH resources.
  • Explicitly state that the instructions apply to all platforms where SFTP is available, and clarify any platform-specific differences if relevant.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/secure-file-transfer-protocol-performance.md ...age/blobs/secure-file-transfer-protocol-performance.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates Windows bias by mentioning WinSCP (a Windows-centric SFTP client) first and exclusively, providing configuration details only for it, and referencing OpenSSH on Windows before OpenSSH on Linux in performance tuning examples. There is a lack of parity in client tool recommendations and configuration guidance for Linux users, and no Linux-specific SFTP client (such as lftp or Nautilus) is mentioned.
Recommendations
  • Include Linux-specific SFTP client examples (e.g., lftp, Nautilus, command-line sftp) alongside WinSCP and FileZilla.
  • Provide configuration guidance for popular Linux SFTP clients, similar to the WinSCP instructions.
  • Present OpenSSH examples for Linux and Windows together or alternate the order to avoid Windows-first bias.
  • Add notes about logging and performance settings for Linux tools where applicable.
  • Ensure all recommendations and examples are cross-platform or clearly indicate platform-specific differences.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/upgrade-to-data-lake-storage-gen2.md ...les/storage/blobs/upgrade-to-data-lake-storage-gen2.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page exhibits mild Windows bias. It references Windows-specific tools (AzCopy, PowerShell), and mentions the Windows Azure Storage Blob (WASB) driver before its successor (ABFS), without providing equivalent Linux or cross-platform examples. References to SDKs, PowerShell, and Azure CLI are grouped together, but PowerShell is listed first, and there are no explicit Linux shell or scripting examples. The documentation does not provide parity in examples or tool recommendations for Linux users.
Recommendations
  • Provide explicit Linux shell (bash) and scripting examples alongside PowerShell commands.
  • Mention Linux-friendly tools (such as Azure CLI, SDKs for Python, Java, etc.) before or alongside Windows tools.
  • Clarify that AzCopy and Azure CLI are cross-platform, and provide usage examples for both Windows and Linux environments.
  • Reference the WASB driver as 'legacy' and highlight ABFS as the recommended cross-platform solution, with configuration examples for Linux-based Hadoop clusters.
  • Include links to documentation or guides for Linux users performing upgrades and managing Data Lake Storage.
  • Avoid listing PowerShell before CLI or SDKs unless contextually relevant; strive for neutral ordering.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/storage-quickstart-blobs-python.md ...icles/storage/blobs/storage-quickstart-blobs-python.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation demonstrates mild Windows bias. In authentication instructions, PowerShell is presented as a sign-in option alongside Azure CLI and Visual Studio Code, but is listed last. The environment variable setup instructions present Windows (setx) before Linux (export), and provide more detail for Windows (such as needing to restart the command window). The initial project setup mentions 'console window (such as PowerShell or Bash)', listing PowerShell before Bash. There is no explicit Linux example missing, but Windows tools and patterns are referenced throughout, and Windows-specific instructions are sometimes more detailed.
Recommendations
  • Present Linux and Windows instructions in parallel, or alternate which is listed first.
  • Provide equal detail for Linux and Windows steps (e.g., mention that new shells may be needed for Linux after setting environment variables).
  • Include Bash and Linux terminal examples wherever PowerShell is mentioned, and avoid implying PowerShell as the default.
  • Where possible, use cross-platform terminology (e.g., 'terminal' instead of 'console window such as PowerShell or Bash').
  • Ensure that any tool-specific instructions (e.g., Visual Studio Code, Azure CLI) clarify their cross-platform availability.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/security-restrict-copy-operations.md ...es/storage/common/security-restrict-copy-operations.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides configuration instructions for the 'Permitted scope for copy operations' feature in Azure Storage. It presents PowerShell examples before Azure CLI, and relies heavily on PowerShell for scripting, which is most commonly used on Windows. There are no explicit Linux shell (bash) or cross-platform scripting examples, nor is there mention of Linux-specific tools or workflows. The CLI instructions are present, but PowerShell is given prominence and detail first, which may signal a Windows-centric bias.
Recommendations
  • Add bash shell examples using Azure CLI to demonstrate parity for Linux users.
  • Explicitly mention that Azure CLI is cross-platform and can be used on Linux, macOS, and Windows.
  • Consider providing examples using REST API calls with curl, which are platform-agnostic and familiar to Linux users.
  • Reorder the configuration sections to present Azure CLI before PowerShell, or present both side-by-side.
  • Include notes or links for Linux users on installing and using Azure CLI and AzCopy.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/includes/azure-storage.md ...main/articles/storage/common/includes/azure-storage.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides examples for Azure CLI, Azure PowerShell, and the Azure Portal. While Azure CLI is cross-platform, the inclusion of Azure PowerShell (which is historically Windows-centric, though now available on Linux/macOS) and the absence of explicit Linux shell (bash/zsh) or scripting examples (such as piping az output to jq or grep) demonstrates a mild Windows bias. PowerShell examples are given equal prominence to CLI, and there are no Linux-specific command-line patterns or notes. No mention is made of Linux-specific tools or usage patterns, nor is there guidance for Linux users on how to adapt the examples.
Recommendations
  • Add explicit bash/zsh examples using Azure CLI, demonstrating output parsing with jq, grep, or awk for Linux users.
  • Clarify that Azure CLI is cross-platform and provide usage notes for Linux/macOS environments.
  • Include a note that PowerShell is available on Linux/macOS, or link to installation instructions for non-Windows users.
  • Consider providing examples of automating these queries in Linux shell scripts.
  • Where relevant, mention differences in shell quoting or environment variables between Windows and Linux.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/infrastructure-encryption-enable.md ...les/storage/common/infrastructure-encryption-enable.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation provides examples for Azure Portal, PowerShell, Azure CLI, and ARM templates. PowerShell is given a dedicated section with detailed instructions and examples, and references to installing PowerShell modules are included. The Azure CLI section is present and provides parity, but PowerShell (a Windows-centric tool) is featured prominently and before CLI. There are no Linux-specific shell examples (e.g., Bash scripts), nor is there mention of Linux-native tools or workflows. The documentation assumes familiarity with PowerShell and Windows tools, which may disadvantage Linux users.
Recommendations
  • Add explicit Bash shell examples for Linux users, especially for verification steps.
  • Clarify that Azure CLI works cross-platform and provide OS-specific installation instructions or links.
  • Consider reordering sections so that cross-platform tools (Azure CLI, ARM templates) are presented before Windows-centric tools like PowerShell.
  • Mention that PowerShell Core is available on Linux, if PowerShell usage is necessary, and provide installation guidance for Linux.
  • Add notes or tips for Linux users regarding any differences in workflow or environment setup.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/storage-encryption-key-model-get.md ...les/storage/common/storage-encryption-key-model-get.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides three methods for checking the encryption key model: Azure portal, PowerShell, and Azure CLI. PowerShell is presented as a primary command-line example, which is Windows-centric. There is no mention of Linux-specific tools or shell examples (e.g., Bash), and the PowerShell example appears before the Azure CLI example, which is more cross-platform. No Linux-specific nuances or troubleshooting are discussed.
Recommendations
  • Add explicit Bash shell examples for Azure CLI usage, showing how Linux users would run and process the command.
  • Clarify that Azure CLI works on Windows, Linux, and macOS, and provide platform-agnostic instructions.
  • Consider listing Azure CLI before PowerShell to emphasize cross-platform support.
  • If relevant, mention any differences or considerations for Linux users (e.g., authentication, environment setup).
  • Avoid assuming PowerShell as the default scripting environment; provide parity for Linux shell users.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/storage-network-security-virtual-networks.md ...ge/common/storage-network-security-virtual-networks.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation page provides detailed instructions for creating virtual network rules for Azure Storage, with examples for the Azure Portal, PowerShell, and Azure CLI. The PowerShell section is prominent and detailed, reflecting a Windows-centric approach. PowerShell (a Windows-native tool) is presented before Azure CLI, and there are no explicit Linux shell or scripting examples (e.g., Bash). The CLI examples use Azure CLI, which is cross-platform, but there is no mention of Linux-specific usage patterns or considerations. The documentation assumes familiarity with PowerShell and Windows tools, which may disadvantage Linux users.
Recommendations
  • Add explicit Bash shell examples for Azure CLI commands, including variable assignment and command chaining.
  • Clarify that Azure CLI commands work identically on Linux, macOS, and Windows, and provide notes on installation for Linux.
  • Consider presenting Azure CLI examples before PowerShell, as CLI is cross-platform and more widely used on Linux.
  • Include troubleshooting or usage notes relevant to Linux environments (e.g., permissions, environment variables, shell differences).
  • Avoid assuming PowerShell as the default scripting environment; mention alternatives like Bash or Zsh for Linux users.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/storage-redundancy-priority-replication.md ...rage/common/storage-redundancy-priority-replication.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation demonstrates a moderate Windows bias. PowerShell is featured prominently and always before Azure CLI in code examples. The CLI examples use Windows-style variable assignment and login commands (Connect-AzAccount), which are PowerShell-specific and not applicable to Bash or Linux shells. There are no Linux/Bash-specific instructions, and the documentation does not mention Linux tools or shell patterns, nor does it provide parity for Linux users in example scripts.
Recommendations
  • Provide Bash/Linux-native CLI examples, using standard Bash variable assignment (e.g., rgname="<resource-group-name>") and Azure CLI login (az login) instead of Connect-AzAccount.
  • Clearly distinguish between PowerShell and CLI examples, and ensure CLI examples are platform-agnostic.
  • Add explicit instructions for Linux users, including installation and usage notes for Azure CLI on Linux.
  • Avoid using Windows/PowerShell-specific commands or syntax in CLI sections; use cross-platform commands.
  • Consider listing CLI (Bash) examples before PowerShell to balance platform representation.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/archive-rehydrate-handle-event.md ...ticles/storage/blobs/archive-rehydrate-handle-event.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a significant Windows bias. It exclusively uses Visual Studio (a Windows-centric IDE) for all development, debugging, and publishing steps, and instructs users to select Windows as the operating system for the Function App. There are no examples or instructions for Linux or cross-platform development environments (such as VS Code, CLI, or other OS options). Package installation is shown only via the Visual Studio NuGet Package Manager Console (PowerShell-based), and publishing is demonstrated only through Visual Studio's GUI. The documentation does not mention or provide parity for Linux or macOS users.
Recommendations
  • Add instructions for developing and debugging Azure Functions using cross-platform tools such as Visual Studio Code and the Azure Functions Core Tools CLI.
  • Include examples for creating and publishing Azure Functions from Linux/macOS environments, using command-line tools (e.g., dotnet CLI, func CLI, az CLI).
  • When describing the creation of a Function App, mention and show how to select Linux as the operating system, and clarify any differences in deployment or runtime.
  • Provide package installation commands using dotnet CLI (dotnet add package ...) in addition to NuGet Package Manager Console.
  • Ensure screenshots and step-by-step instructions are not exclusively tied to Windows/Visual Studio, or clearly mark them as one option among several.
  • Add a section or callouts for Linux/macOS users, linking to relevant guides for non-Windows development environments.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/authorize-access-azure-active-directory.md ...orage/blobs/authorize-access-azure-active-directory.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by repeatedly referencing PowerShell and the Azure portal (which is most commonly used on Windows) before mentioning Azure CLI. There are no explicit Linux-specific examples, nor are Linux tools or patterns discussed. The phrase 'portal, PowerShell, or Azure CLI' is used multiple times, consistently listing PowerShell before Azure CLI, and there are no Bash or Linux shell examples provided. The documentation does not mention Linux authentication workflows, nor does it reference Linux-specific tooling or usage patterns.
Recommendations
  • Add explicit Linux/Bash shell examples for accessing Azure Blob Storage with Microsoft Entra ID, using Azure CLI.
  • Where PowerShell is mentioned, provide parallel Bash or Linux shell commands and usage patterns.
  • Include a section or note on Linux authentication workflows, such as using managed identities or service principals from Linux environments.
  • When listing tools, alternate the order (e.g., 'Azure CLI, PowerShell, or portal') or clarify cross-platform support.
  • Reference Linux desktop tools (such as azcopy on Linux) where relevant, and provide guidance for Linux users.
GitHub Create Pull Request
← Previous Page 16 of 67 Next →