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 1151-1175 of 1657 flagged pages
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation exhibits a moderate Windows bias. Windows-specific tools (Robocopy, File Explorer 'Previous Versions') are described in detail, with step-by-step instructions and screenshots. These Windows workflows are presented before Linux equivalents, and some features (such as browsing snapshots via File Explorer) are only available on Windows. Linux instructions for mounting SMB snapshots are present but less detailed, and there are no Linux/macOS examples for restoring individual files from SMB snapshots outside of mounting. PowerShell is emphasized as a management tool, with limited mention of Linux-native alternatives. NFS snapshot workflows are Linux-focused, but overall, Windows users receive more comprehensive guidance.
Recommendations
- Provide parity in example depth and screenshots for Linux workflows, especially for SMB shares (e.g., show how to restore individual files from a mounted snapshot using Linux file managers or command line).
- Include macOS-specific instructions for accessing SMB snapshots, if supported.
- Mention and provide examples for Linux-native tools (e.g., rsync, cp) for copying/restoring files from SMB snapshots.
- Clarify feature availability and limitations for each platform in a dedicated section.
- Avoid presenting Windows workflows before Linux equivalents unless there is a technical reason.
Create Pull Request
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Windows Heavy Examples
Summary
The documentation page for Azure Files billing is generally cross-platform in its technical content, but there are subtle signs of Windows bias. Windows terminology and tools (such as VSS, Windows File Server, and Windows properties dialog) are referenced more frequently and with more detail than their Linux/macOS equivalents. Examples and analogies (e.g., snapshots 'similar to volume shadow copies (VSS) on Windows File Server') are Windows-centric. The integration section highlights Azure File Sync, which is only for Windows file servers, without mentioning Linux alternatives. There are no explicit Linux/macOS command-line examples, and references to operating system behaviors (e.g., storage unit labeling) discuss Windows first and in more detail.
Recommendations
- Add Linux/macOS-specific examples and references where appropriate, such as how to view file share properties, mount NFS shares, or interpret storage units on those platforms.
- When discussing features like snapshots, provide analogies or references relevant to Linux/macOS (e.g., LVM snapshots, ZFS snapshots) alongside Windows VSS.
- In the value-added services section, mention or link to third-party or open-source solutions for Linux/macOS file servers if available.
- Balance OS references in tables and explanations, listing Linux/macOS before or alongside Windows, and avoid Windows-first ordering.
- Include CLI examples using Bash/Azure CLI, not just PowerShell, and clarify cross-platform support for management tasks.
Storage
Zonal Placement for Azure File Shares
...cs/blob/main/articles/storage/files/zonal-placement.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Windows First
Summary
The documentation provides command-line examples exclusively using Azure PowerShell, a tool most commonly used on Windows and less natively integrated on Linux/macOS. There are no CLI examples using Azure CLI (az), which is cross-platform and preferred by many Linux/macOS users. The structure presents PowerShell as the only scripting option, creating friction for non-Windows users. Additionally, the documentation refers to the Azure portal (web-based, cross-platform) and PowerShell, but omits Bash, Azure CLI, or ARM template examples.
Recommendations
- Add equivalent Azure CLI (az) command examples for all PowerShell instructions.
- Include Bash scripting examples where appropriate.
- Clarify that Azure PowerShell can be installed and used on Linux/macOS, but recommend Azure CLI for those platforms.
- Consider adding ARM template or Bicep examples for infrastructure-as-code parity.
- Present Azure CLI examples before or alongside PowerShell to avoid Windows-first perception.
Storage
Performance and scalability checklist for Queue Storage
...ticles/storage/queues/storage-performance-checklist.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation references Windows-centric tools (e.g., Network Monitor), mentions PowerShell and Azure CLI together but does not provide Linux/macOS-specific examples or alternatives, and lists Windows tools before cross-platform ones. There are no explicit Linux/macOS examples or tool recommendations, and the .NET configuration section is Windows/.NET Framework-focused without parity for other platforms.
Recommendations
- Include Linux/macOS equivalents for diagnostic tools (e.g., suggest tcpdump alongside Wireshark and Network Monitor).
- Provide explicit examples for Azure CLI usage, especially for Linux/macOS users, and clarify cross-platform support.
- Add configuration guidance for popular Linux/macOS languages and frameworks (e.g., Python, Java) regarding connection limits and thread pools.
- Mention cross-platform tools first or equally when listing options (e.g., 'Wireshark or tcpdump' before 'Network Monitor').
- Clarify that PowerShell is available on Linux/macOS, or provide Bash examples where relevant.
Storage
Authorize access to queues using Active Directory
...rage/queues/authorize-access-azure-active-directory.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell is mentioned repeatedly and is listed alongside Azure CLI as a primary method for accessing queue data, but there are no explicit Linux/macOS-specific examples or references to Bash, shell scripting, or Linux tools. The structure and language often place Windows-centric tools (PowerShell) before cross-platform options (Azure CLI), and there are no examples or guidance for Linux/macOS users beyond mentioning Azure CLI, which is cross-platform but not highlighted as such.
Recommendations
- Add explicit examples for Linux/macOS environments, such as Bash or shell scripting, especially for authentication and queue access.
- Clarify that Azure CLI is cross-platform and provide usage instructions for Linux/macOS terminals.
- Include screenshots or walkthroughs for Linux/macOS users where appropriate.
- Avoid listing PowerShell before Azure CLI, or alternate the order to avoid implicit prioritization.
- Mention installation and usage differences for Azure CLI and PowerShell on Linux/macOS.
Storage
Examples for Azure role assignment conditions for Queue Storage
...n/articles/storage/queues/queues-auth-abac-examples.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation provides detailed examples for Azure portal and Azure PowerShell, but does not include equivalent instructions or code samples for Linux/macOS users (e.g., Azure CLI, Bash, or cross-platform scripting). All command-line examples use PowerShell, which is primarily associated with Windows, and there is no mention of Linux tools or workflows.
Recommendations
- Add Azure CLI examples for all tasks currently shown with PowerShell.
- Include Bash or shell script equivalents where applicable.
- Explicitly mention cross-platform support for Azure tools and clarify which steps work on Linux/macOS.
- Reorder or parallelize examples so that Linux/macOS options are presented alongside Windows/PowerShell options.
- Add notes or links to documentation for setting up Azure CLI on Linux/macOS.
Storage
Best practices for monitoring Azure Queue Storage
.../storage/queues/queues-storage-monitoring-scenarios.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page provides monitoring examples for Azure Queue Storage using PowerShell and Azure CLI, but the PowerShell example is presented first and in detail, which may indicate a Windows-first bias. There are no explicit Linux/macOS shell (e.g., Bash) or SDK examples outside of .NET/C#, and no mention of Linux-specific tools or workflows. The reliance on PowerShell and the absence of Linux/macOS command-line examples may create friction for non-Windows users.
Recommendations
- Provide Bash or shell script examples for monitoring metrics, especially for querying with Azure CLI on Linux/macOS.
- Include cross-platform SDK examples (e.g., Python, JavaScript) for queue message count retrieval.
- Alternate the order of examples so that Azure CLI (which is cross-platform) appears before PowerShell.
- Explicitly mention that Azure CLI commands work on Linux/macOS and Windows.
- Add notes or links to Linux/macOS-specific documentation or troubleshooting tips.
Storage
Back up your data to Azure with Commvault
...isaster-recovery/commvault/commvault-solution-guide.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation exclusively provides instructions and screenshots for using the Azure Portal GUI and Commvault Command Center, both of which are platform-agnostic but implicitly assume a graphical environment. There are no examples or guidance for Linux/macOS users, such as CLI-based workflows (e.g., Azure CLI, Bash scripts) or PowerShell alternatives. The documentation does not mention Linux-specific tools, nor does it provide parity for command-line or automation scenarios common in Linux environments.
Recommendations
- Add examples for Azure CLI and/or REST API workflows for storage account and container creation, credential management, and monitoring, which are platform-neutral and widely used on Linux/macOS.
- Include references to Commvault command-line tools or scripts for Linux environments, if available.
- Provide guidance for headless/server environments where GUI access is unavailable, such as using SSH and CLI tools.
- Explicitly mention Linux compatibility for Commvault Media Agent and other components, and link to relevant Linux installation/configuration documentation.
- If PowerShell is referenced, ensure Bash or shell script equivalents are provided.
Storage
Back up your data to Azure with DobiProtect
...-disaster-recovery/datadobi/datadobi-solution-guide.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page exclusively uses Azure Portal (web UI) instructions and does not provide any command-line examples, such as Azure CLI, PowerShell, or REST API. While this avoids explicit Windows tool bias, it implicitly favors Windows users by relying on graphical workflows typical of Windows environments and omits Linux/macOS-friendly CLI instructions. There are no Linux-specific tools, shell commands, or CLI examples, and no mention of how to perform the same tasks outside the portal. This creates friction for Linux/macOS users who often prefer or require command-line automation.
Recommendations
- Add Azure CLI examples for all major steps, such as creating storage accounts, containers, and managing access keys.
- Include PowerShell examples for parity, but ensure CLI (bash) instructions are presented first or alongside.
- Mention REST API options for advanced/automated scenarios.
- Clarify that all steps can be performed via CLI on Linux/macOS, and link to relevant Azure CLI documentation.
- Add a section comparing portal vs CLI workflows, highlighting cross-platform options.
Storage
Migrate data to Azure with Atempo Miria
...d-partners/data-management/atempo-quick-start-guide.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by providing migration examples and configuration steps exclusively for Windows file servers (SMB/CIFS shares), referencing Windows-specific Data Movers, and omitting equivalent Linux/NFS migration scenarios. Network monitoring tool recommendations are also Windows-centric, with no mention of Linux-native alternatives. This creates friction for Linux/macOS users seeking parity.
Recommendations
- Add explicit examples for migrating from Linux/NFS shares, including configuration steps in Miria for NFS as a source.
- Include screenshots and instructions for setting up Miria Data Movers on Linux platforms.
- List Linux-native network monitoring tools (e.g., iftop, nload, vnStat, netstat, iperf) alongside Windows options.
- Clarify platform support in all relevant sections, and provide parity in step-by-step guides for Linux/macOS environments.
- Ensure that references to 'Windows Data Mover' are balanced with Linux Data Mover options, or use neutral language.
Storage
Analyze and migrate your file data to Azure with Data Dynamics StorageX
...partners/data-management/storagex-quick-start-guide.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation exhibits a notable Windows bias. Windows-centric concepts, tools, and procedures (Active Directory, SMB, Windows file servers, Microsoft portqryui, installation paths like C:\ProgramData, and 'Run as administrator') are presented as defaults or prerequisites. There are no Linux/macOS-specific instructions, examples, or troubleshooting steps, and Linux equivalents (e.g., NFS, Linux service accounts, Linux CLI install, Linux port checking tools) are either mentioned briefly or omitted entirely.
Recommendations
- Add explicit Linux/macOS deployment instructions, including installation paths, service account setup, and privilege requirements for non-Windows environments.
- Include Linux/macOS examples for network port checking (e.g., using netcat, nmap, or ss) alongside Windows tools like portqryui.
- Provide guidance for NFS migrations from Linux servers, including sample export rules and security best practices.
- Clarify whether StorageX can be installed and operated on Linux/macOS, and if not, state this limitation up front.
- Present examples for both Windows and Linux environments in parallel, rather than defaulting to Windows-first.
- Include troubleshooting steps and support contacts relevant to Linux/macOS users.
Storage
Nasuni configuration guide for Microsoft Azure
...s/primary-secondary-storage/nasuni-deployment-guide.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation consistently refers to Azure as 'Windows Azure Platform', uses 'Windows' terminology, and presents all examples and screenshots from the Azure portal UI, which is platform-agnostic but the naming and references are Windows-centric. There are no CLI or automation examples (e.g., Azure CLI, PowerShell, Bash), nor any Linux/macOS-specific guidance. The documentation does not mention or provide parity for Linux tools or workflows, such as using Azure CLI on Linux/macOS, or integrating with Linux-based automation. This creates friction for Linux/macOS users who may prefer or require command-line or scriptable approaches.
Recommendations
- Add Azure CLI examples for all major steps (creating storage account, configuring firewalls, managing credentials, etc.), as Azure CLI is cross-platform and widely used on Linux/macOS.
- Avoid using 'Windows Azure Platform' as the only selectable option; clarify if this is a legacy naming or provide equivalent instructions for Linux/macOS users.
- Include screenshots or instructions for Linux/macOS environments where relevant, especially for credential management and automation.
- Explicitly mention that all steps can be performed from Linux/macOS using the Azure portal and Azure CLI, and link to relevant Azure CLI documentation.
- Provide PowerShell examples only as an alternative, not as the primary or sole method.
Storage
Encryption scopes for Blob storage
...in/articles/storage/blobs/encryption-scope-overview.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation page demonstrates mild Windows bias by listing PowerShell before CLI in the section on Azure Key Vault soft-delete recovery. No Linux-specific tools or examples are provided, and PowerShell is mentioned first, which may suggest a preference for Windows environments. However, the overall content is mostly platform-neutral and does not rely heavily on Windows-only tools or patterns.
Recommendations
- Present CLI and PowerShell instructions in parallel, or list CLI first to avoid implicit Windows preference.
- Explicitly mention that both CLI and PowerShell are cross-platform, and provide links to Bash/Linux shell usage where relevant.
- Add examples or references for Linux/macOS users, such as Bash scripts or usage in non-Windows environments.
- Review other related documentation to ensure Linux parity in tooling and instructions.
Storage
Manage blob containers using the Azure portal
.../main/articles/storage/blobs/blob-containers-portal.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page exclusively describes how to manage Azure blob containers using the Azure portal, with all instructions and screenshots focused on the portal UI. While it briefly mentions Azure PowerShell and Azure CLI as options for creating a storage account, it does not provide any command-line examples, nor does it reference Linux-specific tools or workflows. The only cross-platform reference is in the 'See also' section, which links to a PowerShell guide but omits direct links to CLI or Linux-native documentation. This results in a 'windows_first' bias (portal and PowerShell are traditionally Windows-centric) and a 'missing_linux_example' bias (no CLI/bash examples or Linux tool references).
Recommendations
- Add parallel instructions and examples for managing blob containers using Azure CLI, including bash commands that work on Linux and macOS.
- Include references and links to documentation for Linux-native tools (e.g., azcopy, Azure CLI) in the 'See also' section.
- Where screenshots are used, consider including CLI output or terminal screenshots alongside portal UI images.
- Explicitly mention that the Azure portal is cross-platform, but also highlight command-line alternatives for users who prefer Linux environments.
- Ensure parity in step-by-step guides for common operations (create, delete, manage metadata, access policies, leases) using CLI/bash commands.
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a subtle Windows bias in its example paths and file references. Throughout the article, file paths use Windows-style (e.g., C:\temp\), and instructions for creating sample files reference Windows directories. There are no explicit Linux or macOS path examples, nor is there guidance for users on those platforms. While all CLI examples use Bash syntax (which is cross-platform), the file path conventions and sample file locations are Windows-centric, potentially causing confusion or extra work for Linux/macOS users.
Recommendations
- Provide parallel examples using Linux/macOS path conventions (e.g., /tmp/, ~/temp/, /mnt/c/temp/).
- Add notes clarifying that file paths should be adapted to the user's operating system.
- When referencing sample files (such as blob-list.xml), offer both Windows and Linux/macOS creation instructions and default locations.
- Explicitly mention cross-platform compatibility of Azure CLI and Bash scripts, and encourage users to adjust paths and commands as needed.
- Consider including a table or section summarizing common path differences and environment setup for Windows, Linux, and macOS.
Storage
Access control lists in Azure Data Lake Storage
...cles/storage/blobs/data-lake-storage-access-control.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation page demonstrates mild Windows bias by listing Windows-centric tools (Azure Storage Explorer, Azure portal, PowerShell) before cross-platform or Linux-native options (Azure CLI, REST API) in the 'How to set ACLs' section. PowerShell is included as a primary method, but there is no mention of Linux shell commands or native POSIX/Linux ACL management tools. The guidance for obtaining service principal Object IDs uses Azure CLI, which is cross-platform, but there are no examples using Linux command-line utilities for ACL management. No explicit Linux or bash examples are provided.
Recommendations
- Add examples using Linux shell commands (e.g., setfacl, getfacl) to demonstrate POSIX ACL management on Linux systems.
- Include guidance for managing ACLs via bash scripts or Linux command-line tools where appropriate.
- Reorder the 'How to set ACLs' table to list cross-platform tools (Azure CLI, REST API) before Windows-specific tools (PowerShell, Storage Explorer).
- Explicitly mention Linux compatibility and provide parity in examples for both Windows and Linux environments.
- Reference Linux-native documentation or tutorials for ACL management in addition to Azure-specific tools.
Storage
Using the HDFS CLI with Azure Data Lake Storage
.../blobs/data-lake-storage-use-hdfs-data-lake-storage.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation page exhibits mild Windows bias. The only explicit code example for connecting to the cluster via SSH is provided in PowerShell syntax, which is native to Windows. There are no equivalent Linux shell (bash) examples, and the use of PowerShell is mentioned before any reference to Linux command-line patterns, despite the context being HDInsight on Linux. The rest of the HDFS CLI examples are platform-agnostic, but the initial connection instructions may confuse or disadvantage Linux users.
Recommendations
- Provide Linux bash shell examples for SSH connections alongside or before PowerShell examples.
- Clarify that SSH commands are identical on Linux and macOS, and provide sample commands in those contexts.
- Avoid presenting Windows-specific tools or syntax (such as PowerShell) as the default or only method, especially when the service runs on Linux.
- Add a note or section explicitly addressing cross-platform usage, highlighting any differences or similarities in command syntax.
Storage
Use Azure CLI to manage data (Azure Data Lake Storage)
...rage/blobs/data-lake-storage-directory-file-acl-cli.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a mild Windows bias. In the prerequisites and instructions, Windows PowerShell is mentioned as the example console application for running Azure CLI locally, with no mention of Linux terminals (e.g., Bash, Terminal, etc.). File path examples for upload and download operations use Windows-style paths (e.g., 'C:\myFolder\upload.txt'), with no Linux/Mac equivalents (e.g., '/home/user/upload.txt'). There are no explicit Linux or Mac terminal examples or references.
Recommendations
- Mention Linux and Mac terminal applications (e.g., Bash, Terminal, zsh) alongside Windows PowerShell when discussing running Azure CLI locally.
- Provide file path examples using both Windows ('C:\myFolder\upload.txt') and Linux/Mac ('/home/user/upload.txt') formats for upload and download commands.
- Add a note clarifying that Azure CLI works on Windows, Linux, and Mac, and that commands are identical across platforms except for file path syntax.
- Consider including screenshots or terminal prompts from multiple platforms to reinforce cross-platform usability.
Storage
Limitations & known issues with SFTP in Azure Blob Storage
...ge/blobs/secure-file-transfer-protocol-known-issues.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page exhibits mild Windows bias by providing a client configuration example only for WinSCP, a popular Windows SFTP client, without mentioning or providing equivalent guidance for Linux-native SFTP clients (such as OpenSSH's sftp, lftp, or FileZilla). No Linux tools or patterns are referenced, and troubleshooting steps do not mention Linux-specific considerations or commands.
Recommendations
- Add configuration examples for common Linux SFTP clients (e.g., OpenSSH sftp, lftp, FileZilla), including any relevant settings or flags for compatibility with Azure Blob Storage.
- Include troubleshooting steps or notes relevant to Linux environments, such as command-line error messages or log file locations.
- Present client examples in a cross-platform manner, listing both Windows and Linux clients side-by-side, or in separate sections.
- Reference Linux tools and patterns where appropriate, ensuring parity with Windows client guidance.
Storage
SSH File Transfer Protocol (SFTP) performance considerations in Azure Blob storage
...age/blobs/secure-file-transfer-protocol-performance.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation page demonstrates a Windows bias by mentioning Windows-specific tools (WinSCP) first and providing configuration details for them, while Linux equivalents are not discussed in the same detail. In the section on increasing message size, Windows/OpenSSH is described before Linux/OpenSSH, and the Windows example uses a smaller buffer size than the Linux example, but both are present. There are no PowerShell-heavy examples, but Windows tools and patterns are prioritized.
Recommendations
- Include equivalent Linux SFTP client examples (e.g., lftp, Nautilus, or command-line usage) alongside WinSCP and FileZilla.
- Provide configuration details for popular Linux SFTP clients, similar to the WinSCP logging instructions.
- Alternate the order of Windows and Linux examples to avoid implicit prioritization.
- Add troubleshooting or performance tips specific to Linux environments, such as tuning SSH/SFTP settings or using different file managers.
- Ensure that all recommendations and examples are presented with equal detail for both Windows and Linux platforms.
Storage
Enable or disable SFTP support in Azure Blob Storage
.../blobs/secure-file-transfer-protocol-support-how-to.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides examples for enabling and disabling SFTP support in Azure Blob Storage using the Azure Portal, PowerShell, and Azure CLI. PowerShell examples are given equal prominence to Azure CLI, but PowerShell is a Windows-centric tool, and its tab appears before the Azure CLI tab, which is more cross-platform. There are no explicit Linux shell or Bash examples, and no mention of Linux-specific tools or workflows. The documentation does not reference Windows-only tools outside of PowerShell, but the ordering and inclusion of PowerShell may signal a slight Windows bias.
Recommendations
- List Azure CLI examples before PowerShell examples, as Azure CLI is cross-platform and more familiar to Linux/macOS users.
- Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows.
- Consider adding Bash shell script examples or notes for Linux users, especially for automation scenarios.
- If referencing PowerShell, clarify that PowerShell Core is available cross-platform, or provide a note for Linux/macOS users.
- Ensure that any screenshots or UI references do not assume a Windows environment unless unavoidable.
Storage
Tutorial - Simulate a failure in reading data from the primary region
...icles/storage/blobs/simulate-primary-region-failure.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation demonstrates some Windows bias, particularly in the 'Simulate a failure with Fiddler' section, where only Fiddler (a Windows-only tool) is described for simulating failures via HTTP interception. Additionally, in the static route section, Windows commands and terminology are often mentioned before Linux equivalents, and the instructions for opening an elevated command prompt reference Windows first.
Recommendations
- Provide equivalent instructions for HTTP interception on Linux and macOS, such as using mitmproxy or similar cross-platform tools, alongside Fiddler.
- When listing commands or instructions, alternate the order or present Linux and Windows instructions in parallel to avoid always prioritizing Windows.
- Explicitly mention cross-platform alternatives to Fiddler and provide example scripts or steps for those tools.
- Clarify that Fiddler is a Windows-only tool and suggest alternatives for users on other operating systems.
- Ensure that terminology (e.g., 'elevated command prompt') is inclusive of all platforms, such as 'open a terminal as administrator/root on your OS'.
Storage
Reacting to Azure Blob storage events
.../articles/storage/blobs/storage-blob-event-overview.md
Medium Priority
View Details →
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). There are no explicit Linux-specific examples or mentions of Linux tools, and PowerShell is highlighted as a primary automation method. No Bash, shell script, or Linux-native patterns are referenced.
Recommendations
- List Azure CLI before PowerShell in quickstart tables and examples, as CLI is cross-platform and preferred for Linux users.
- Add explicit Bash or shell script examples for common event subscription and filtering tasks.
- Reference Linux-native automation patterns (e.g., cron jobs, systemd services) where relevant.
- Clarify that Azure CLI works on Linux/macOS/Windows, and provide installation links for non-Windows platforms.
- Avoid implying PowerShell is the default or primary automation tool; present it as one of several options.
Storage
Blob Storage feature support in Azure storage accounts
...e/blobs/storage-feature-support-in-storage-accounts.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Summary
The documentation page lists both Azure CLI and PowerShell command support for Blob Storage, but only explicitly calls out PowerShell (a Windows-centric tool) in the feature tables. There is no mention of Linux-specific command-line tools (other than Blobfuse, which is listed alongside PowerShell and CLI), nor are Linux shell examples or patterns highlighted. PowerShell is given equal prominence to Azure CLI, but the lack of Bash/shell or Linux-native tool references (such as azcopy, curl, or REST API usage from Linux) suggests a mild Windows/PowerShell bias.
Recommendations
- Include explicit references to Linux-native tools and workflows, such as azcopy, curl, or REST API usage from Bash.
- Provide example links or documentation for using Blob Storage from Linux shells, not just PowerShell and Azure CLI.
- Clarify that Azure CLI is cross-platform and provide usage examples for both Windows (PowerShell) and Linux (Bash).
- Consider adding a 'Linux commands' row to the feature tables, similar to 'PowerShell commands', to highlight parity.
- Ensure that documentation does not assume PowerShell as the default scripting environment.
Storage
Performance checklist for Azure Blob Storage
...rticles/storage/blobs/storage-performance-checklist.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates mild Windows bias by mentioning network monitoring tools (WireShark and NetMon) where NetMon is a Windows-specific tool, and by not providing Linux equivalents or examples. Additionally, while AzCopy is cross-platform, there is no explicit mention of Linux usage or alternative Linux-native tools, nor are command-line examples shown for Linux environments.
Recommendations
- When listing network monitoring tools, include Linux equivalents such as tcpdump or iftop alongside WireShark.
- Explicitly state that AzCopy is available for Linux and provide example usage or installation instructions for Linux environments.
- If referencing offline data import tools, clarify platform compatibility and provide guidance for Linux users.
- Avoid mentioning Windows-only tools (like NetMon) without Linux alternatives, or list them after cross-platform options.
- Consider adding a section or notes on how to optimize performance from Linux clients, including relevant tools and best practices.