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 251-275 of 1657 flagged pages
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation provides extensive PowerShell examples alongside Azure CLI and portal instructions. PowerShell is a Windows-centric tool, and its usage is described in detail, including installation and file path examples using Windows-style paths (e.g., C:\temp\json.txt). There is no mention of Linux-specific shell usage (such as Bash) or cross-platform scripting alternatives. PowerShell examples are given equal or greater prominence than CLI, and Windows file system conventions are used in code samples. There are no explicit Linux-only examples or guidance for Linux users.
Recommendations
- Add Bash shell examples for all CLI commands, demonstrating usage on Linux/macOS.
- Use platform-neutral file paths in examples (e.g., /tmp/json.txt or ./policy.json) or provide both Windows and Linux path variants.
- Explicitly mention that Azure CLI works on Linux/macOS and provide installation links for those platforms.
- Include notes or sections for Linux users, such as using az CLI in Bash, handling JSON files, and alternative scripting approaches.
- Avoid assuming PowerShell as the default scripting environment; clarify its cross-platform availability or suggest alternatives.
- Where PowerShell is used for scripting, provide equivalent Bash scripts for Linux users.
Create Pull Request
Storage
Deploy Tiger Bridge Continuous Data Protection, Archive and Disaster Recovery with Azure Blob Storage
...up-archive-disaster-recovery/tiger-bridge-cdp-guide.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation page exhibits a strong Windows bias throughout. All deployment and configuration instructions assume a Windows environment, specifically requiring a Windows file server. Native integration and examples are exclusively with Windows tools (e.g., Volume Shadow Copy Service, Windows Explorer, Windows DFSR, Tiger Bridge Shell Extension for Windows). There are no Linux or cross-platform deployment instructions, nor any mention of Linux equivalents or alternative tools. No PowerShell scripts are present, but the reliance on Windows-native features and GUI tools further excludes Linux users.
Recommendations
- Add explicit instructions for deploying Tiger Bridge on Linux servers, if supported, or clarify platform limitations.
- Provide Linux-based examples for backup, restore, and archive operations (e.g., using CLI tools, shell scripts, or file managers like Nautilus or Dolphin).
- Mention Linux equivalents for features like file versioning, undelete, and disaster recovery (e.g., integration with Linux snapshot tools, rsync, or LVM snapshots).
- If Tiger Bridge is Windows-only, state this clearly at the beginning of the documentation to set user expectations.
- Include cross-platform considerations for Azure Blob Storage integration, such as using azcopy, Azure CLI, or REST API from Linux environments.
- Ensure screenshots and step-by-step guides are available for both Windows and Linux (where applicable).
Storage
Deploy hybrid data infrastructure with Tiger Bridge and Azure Blob Storage
...ary-secondary-storage/tiger-bridge-deployment-guide.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation page exhibits a strong Windows bias. It focuses almost exclusively on Windows environments, NTFS/ReFS file systems, and Windows Server for Tiger Bridge deployment. All deployment instructions, screenshots, and examples are Windows-centric, with no Linux-specific guidance or examples. Windows tools and patterns (e.g., Windows Explorer shell extension, NTFS/ReFS, C:\ paths) are mentioned exclusively and before any mention of Linux or cross-platform alternatives. There is no mention of Linux installation, configuration, or command-line examples, nor any parity for Linux file systems or management tools.
Recommendations
- Add explicit instructions and examples for deploying Tiger Bridge on Linux servers, including supported distributions and file systems (e.g., ext4, XFS).
- Provide Linux-specific installation steps, including command-line examples and screenshots.
- Include guidance for managing Linux file systems and integrating with Azure Blob Storage using Tiger Bridge.
- Mention Linux equivalents for features such as shell integration (e.g., Nautilus extensions) and command-line management.
- Clarify Tiger Bridge's support for NFS and SMB from a Linux perspective, including configuration and best practices.
- Ensure parity in troubleshooting and support sections for Linux users.
Storage
Perform a point-in-time restore on block blob data
...articles/storage/blobs/point-in-time-restore-manage.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell is featured prominently as a primary automation example, with detailed command sequences and explanations. Windows-specific tooling (PowerShell, Az.Storage module) is presented before cross-platform alternatives (Azure CLI), and the PowerShell tab is consistently listed before Azure CLI in all code example sections. There are no Linux-specific examples, nor any mention of Linux shell patterns, and no guidance for Bash scripting or Linux-native tools. The documentation assumes familiarity with PowerShell and Windows-centric workflows.
Recommendations
- Add explicit Bash/Linux shell examples for all CLI commands, including environment variable usage and scripting patterns.
- Include notes or sections on running Azure CLI commands in Linux/macOS terminals, addressing differences in quoting, environment variables, and installation.
- Reorder code example tabs so that Azure CLI (cross-platform) appears before PowerShell, or at least alternate the order to avoid implicit prioritization.
- Mention that PowerShell Core is available cross-platform, but clarify that examples are written for Windows PowerShell unless otherwise stated.
- Provide troubleshooting tips for common Linux/macOS issues (e.g., path separators, permissions) when using Azure CLI or PowerShell Core.
Storage
Host keys for SFTP support for Azure Blob Storage
...orage/blobs/secure-file-transfer-protocol-host-keys.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation page exhibits mild Windows bias. While it does mention the cross-platform 'known_hosts' file (used by OpenSSH on Linux/macOS/Windows), it gives Windows-specific examples and tools (WinSCP, Windows registry) more prominence and detail. The registry example is only for Windows, and the troubleshooting output uses Windows-style paths (C:\Users\<user>/.ssh/known_hosts) without showing Linux equivalents. There are no explicit Linux-specific client/tool examples (e.g., FileZilla, Linux CLI workflows), and no Linux-specific troubleshooting paths or instructions.
Recommendations
- Add Linux-specific SFTP client examples (e.g., FileZilla, OpenSSH CLI) alongside Windows tools.
- Include Linux-style paths (e.g., /home/<user>/.ssh/known_hosts) in troubleshooting and examples.
- Provide troubleshooting output examples from Linux terminals (e.g., typical OpenSSH error messages).
- Mention Linux GUI SFTP clients (e.g., Nautilus, GNOME Files) and how host keys are managed there.
- Balance the order of presentation so Linux/OpenSSH examples appear before or alongside Windows/WinSCP examples.
- Clarify that the 'known_hosts' file location and format is identical across Linux/macOS/Windows, and show both path styles.
Storage
SSH File Transfer Protocol (SFTP) performance considerations in Azure Blob storage
...age/blobs/secure-file-transfer-protocol-performance.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by mentioning Windows-specific tools (WinSCP) first and providing detailed configuration steps for them, while Linux equivalents are not discussed in detail. In the section on increasing message size, the Windows example is presented before the Linux example, and the Linux example is less detailed. There is also a lack of Linux-specific client recommendations or configuration guidance, with Windows tools and patterns being prioritized.
Recommendations
- Provide equivalent Linux client examples (e.g., lftp, Nautilus, or command-line SFTP) with detailed configuration steps.
- List Linux tools alongside Windows tools (e.g., mention FileZilla and lftp together with WinSCP) and avoid presenting Windows tools first.
- Balance example order by alternating or grouping Windows and Linux instructions.
- Include specific guidance for configuring logging and concurrency in popular Linux SFTP clients.
- Add troubleshooting tips and performance recommendations relevant to Linux environments.
Storage
Connect to Azure Blob Storage from an SFTP client
...blobs/secure-file-transfer-protocol-support-connect.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by presenting the only explicit SFTP connection example as a Windows PowerShell session, referencing Windows-specific OpenSSH documentation, and omitting equivalent Linux/macOS command-line examples. The initial example positions Windows tooling and patterns as the default, potentially making Linux users feel less supported.
Recommendations
- Add a Linux/macOS example for connecting to Azure Blob Storage via SFTP, e.g., using the standard 'sftp' command in a bash shell.
- Reference Linux and macOS OpenSSH documentation alongside the Windows version.
- Present connection examples for multiple platforms in parallel, or use platform-neutral syntax first.
- Explicitly state that the instructions apply to all major operating systems, and highlight any platform-specific differences if relevant.
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation demonstrates a Windows bias by frequently referencing Windows-specific tools (PowerShell), mentioning Windows PowerShell as a default console for Azure CLI, and listing PowerShell instructions before Azure CLI equivalents. There is an implicit prioritization of Windows workflows and terminology, with no explicit mention of Linux shells or cross-platform alternatives in introductory or instructional text. While Azure CLI examples are provided (which are cross-platform), the narrative and instructions often assume a Windows environment.
Recommendations
- Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and provide example shell environments (e.g., bash, zsh) alongside PowerShell.
- Avoid referring to 'Windows PowerShell' as the default console for CLI; instead, suggest 'your preferred command-line shell (e.g., bash, PowerShell, zsh)'.
- Where PowerShell is referenced, add equivalent instructions for bash or other popular Linux shells, especially for authentication and context setup.
- Add notes or sections highlighting Linux/macOS usage, including installation and environment setup for Azure CLI and PowerShell.
- Ensure that CLI examples use syntax compatible with both Windows and Linux shells (e.g., avoid backslashes for line continuation, or provide both styles).
Storage
SFTP support for Azure Blob Storage
...storage/blobs/secure-file-transfer-protocol-support.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation demonstrates a mild Windows bias. In the only SFTP command example, the code block is marked as 'powershell', and the text references OpenSSH documentation specifically for Windows Server. There is no explicit Linux example or mention of Linux-native tools or workflows, and the only linked SSH overview is for 'SSH from Windows'. While the SFTP protocol itself is cross-platform and the client list includes both Windows and Linux tools, the documentation's examples and references prioritize Windows environments.
Recommendations
- Provide SFTP command examples in a neutral shell format (e.g., bash) or include both Windows (PowerShell/CMD) and Linux (bash) examples side by side.
- Reference both Windows and Linux OpenSSH documentation, or provide a generic OpenSSH link.
- Explicitly mention that SFTP and SSH key management steps are the same on Linux/macOS, and provide links to relevant Linux documentation.
- Avoid marking generic SFTP command blocks as 'powershell' unless they use PowerShell-specific syntax.
- Include Linux-native tools (e.g., sftp, scp, ssh-keygen) in examples and tool recommendations where appropriate.
Storage
Use blob index tags to manage and find data on Azure Blob Storage
...in/articles/storage/blobs/storage-blob-index-how-to.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation page demonstrates a Windows bias by consistently referencing Windows PowerShell as the default local shell for Azure CLI usage, providing PowerShell examples in detail, and using Windows-style file paths (e.g., C:\demo-file.txt) in all CLI and PowerShell code samples. There is no mention of Linux shells (bash, zsh) or Linux file path conventions, and instructions for local CLI usage default to Windows PowerShell, potentially excluding or confusing Linux users.
Recommendations
- Provide explicit examples for Linux/macOS users, including bash/zsh shell instructions and Linux-style file paths (e.g., /home/user/demo-file.txt).
- When referencing local CLI usage, mention both Windows PowerShell and common Linux/macOS shells (e.g., bash, zsh) to ensure inclusivity.
- Add notes or tabs for platform-specific differences, such as file path formats and shell commands.
- Ensure that AzCopy instructions and references are platform-agnostic or include platform-specific guidance where relevant.
- Review and update screenshots and instructions to avoid exclusive use of Windows environments.
Storage
Enable and manage soft delete for containers
...articles/storage/blobs/soft-delete-container-enable.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by providing detailed PowerShell instructions (which are Windows-centric), listing PowerShell before Azure CLI (which is cross-platform), and omitting explicit Linux shell examples (e.g., Bash). There are no references to Linux-specific tools or patterns, and the CLI examples do not clarify shell compatibility or usage nuances for Linux users.
Recommendations
- Add explicit Bash/Linux shell examples for Azure CLI commands, including installation and usage notes relevant to Linux environments.
- Reorder the command-line sections to present Azure CLI before PowerShell, emphasizing cross-platform compatibility.
- Clarify that Azure CLI commands work on Windows, Linux, and macOS, and provide troubleshooting tips for common Linux issues (e.g., authentication, environment variables).
- Include links or references to Linux documentation or guides for Azure Storage management.
- Consider adding a table comparing command-line options (PowerShell, CLI, REST API) and their platform compatibility.
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates Windows bias in several ways: PowerShell is given its own dedicated section with detailed step-by-step instructions, while there is no equivalent for Bash or Linux shell scripting. The enable/disable instructions mention PowerShell before Azure CLI, and there are no Linux-specific command examples or references to Linux tools. The Azure CLI example is present, but lacks parity in detail compared to PowerShell. No mention is made of using Bash, shell scripts, or Linux-native tools for managing change feed settings.
Recommendations
- Add Bash/Linux shell scripting examples for enabling/disabling change feed, matching the detail of the PowerShell section.
- Ensure Azure CLI examples are as detailed as PowerShell, including authentication and module installation steps if relevant.
- Explicitly mention cross-platform compatibility for CLI commands and tools.
- Consider including references to Linux-native tools (e.g., azcopy, curl, jq) for interacting with Blob Storage and change feed.
- Reorder sections so that platform-neutral or cross-platform tools (Azure CLI, ARM templates) are presented before platform-specific ones (PowerShell).
Storage
Host a static website in Azure Storage
...es/storage/blobs/storage-blob-static-website-how-to.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page exhibits several signs of Windows bias. Windows tools and terminology (e.g., PowerShell, Windows PowerShell, C:\ paths) are mentioned first or exclusively in command examples and instructions. PowerShell is given a dedicated section, and instructions often reference Windows-specific consoles and file paths. There is a lack of explicit Linux or macOS examples, especially for local CLI usage, and no mention of Linux-specific shell environments or file path formats. The documentation assumes familiarity with Windows tools and patterns, which may hinder Linux users.
Recommendations
- Include explicit instructions and examples for Linux/macOS users, such as using Bash or Terminal instead of Windows PowerShell.
- Provide file path examples using Linux/macOS formats (e.g., /home/user/index.html) alongside Windows paths.
- Clarify that Azure CLI commands can be run from any OS and show how to open a terminal on Linux/macOS.
- Add notes or sections for installing and using Azure CLI and AzCopy on Linux/macOS.
- Balance the order of examples so that Linux/macOS instructions are presented alongside or before Windows-specific ones.
- Avoid assuming the use of Windows tools (e.g., PowerShell) as the default for all users.
Storage
Performance tuning for uploads and downloads with Azure Storage client library for .NET
...es/storage/blobs/storage-blobs-tune-upload-download.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by referencing .NET-specific APIs and patterns, such as ServicePointManager and ThreadPool, which are primarily relevant to Windows environments. All code examples are in C# and tailored to .NET, with no mention of Linux-specific considerations, alternative runtimes, or cross-platform differences. There is no guidance or examples for Linux users, such as how connection limits or thread pools are managed on Linux, or how to tune performance in Mono/.NET Core on Linux. The documentation assumes a Windows-centric development environment and omits Linux parity.
Recommendations
- Add explicit notes or sections describing how StorageTransferOptions and connection/thread pool settings behave on Linux, including .NET Core and Mono environments.
- Provide equivalent code examples or configuration guidance for Linux environments, such as how to adjust connection limits and thread pools on Linux.
- Mention any differences in default values, performance characteristics, or limitations between Windows and Linux when using the Azure Storage client library for .NET.
- Include troubleshooting tips or links for Linux-specific performance issues, such as file descriptor limits or network stack differences.
- Clarify which APIs and settings are cross-platform and which are Windows-specific, to help developers on Linux avoid confusion.
Storage
Encrypt and decrypt blobs using Azure Key Vault
...orage/blobs/storage-encrypt-decrypt-blobs-key-vault.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in several areas: Windows tools and patterns (Visual Studio, PowerShell, setx) are mentioned first or exclusively, with Linux alternatives often appearing later or in less detail. PowerShell is given its own example sections, and Visual Studio is the primary editor referenced. Some steps, such as package installation and environment variable setup, provide Windows-first instructions or use Windows-specific tools. There is limited coverage of Linux-native workflows, and no mention of cross-platform editors beyond Visual Studio Code.
Recommendations
- Present Linux and Windows instructions in parallel, or alternate which is listed first.
- Include Bash and Linux-native commands wherever PowerShell or Windows CMD is shown.
- Reference cross-platform editors (e.g., JetBrains Rider, VS Code) equally with Visual Studio.
- Add explicit instructions for Linux package installation (e.g., using dotnet CLI, not just PowerShell).
- Ensure all steps (role assignment, environment variables, project setup) have clear Linux equivalents.
- Avoid assuming Visual Studio is the default IDE; mention alternatives for Linux users.
- Where screenshots are used, provide both Windows and Linux UI examples if relevant.
Storage
Static website hosting in Azure Storage
.../articles/storage/blobs/storage-blob-static-website.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page lists several tools for uploading content to Azure Storage, including Azure CLI, Azure PowerShell, AzCopy, Azure Storage Explorer, Azure portal, Azure Pipelines, and Visual Studio Code extension. While Azure CLI and AzCopy are cross-platform, the inclusion and ordering of Azure PowerShell and Windows-centric tools (Storage Explorer, VS Code extension, Channel 9 video) suggest a Windows-first approach. There are no explicit Linux or macOS-specific examples, nor are Linux-native tools or shell scripting patterns mentioned. PowerShell is highlighted as a primary method, but Bash or other Linux shell examples are missing. The documentation does not provide parity in examples or guidance for Linux users, and the ordering of tools tends to favor Windows environments.
Recommendations
- Add explicit Bash and Linux shell examples for common tasks (e.g., uploading files, finding URLs).
- Clarify that AzCopy and Azure CLI are cross-platform and provide sample commands for Linux/macOS.
- Include Linux-native tools or workflows (e.g., using curl, wget, or scripting with Bash) where appropriate.
- Balance the ordering of tool recommendations to avoid Windows-first bias (e.g., list CLI and AzCopy before PowerShell and Storage Explorer).
- Provide screenshots or instructions for Linux/macOS environments in addition to Windows.
- Mention installation instructions for Azure CLI and AzCopy on Linux/macOS.
- Avoid referencing Windows-specific video resources (such as Channel 9) without Linux alternatives.
Storage
Map a custom domain to an Azure Blob Storage endpoint
...n/articles/storage/blobs/storage-custom-domain-name.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell is featured prominently as a scripting example, and in several places, the instructions and command examples are labeled as 'PowerShell' even when Azure CLI is also provided. The PowerShell tab is consistently listed before the Azure CLI tab, and the CLI examples are sometimes incorrectly labeled as 'PowerShell command'. There is no mention of Linux-specific shell environments (e.g., Bash), nor are there any examples tailored for Linux users (such as shell scripting, environment variables, or platform-specific notes). The documentation assumes familiarity with Windows-centric tools and patterns, potentially making it less approachable for Linux users.
Recommendations
- Correctly label Azure CLI examples as 'Bash' or 'Shell' where appropriate, and clarify that Azure CLI commands can be run on Linux, macOS, and Windows.
- Provide explicit Bash or shell script examples for Linux users, including notes on environment variable usage and command syntax differences.
- Alternate the order of PowerShell and Azure CLI tabs, or default to Azure CLI, which is cross-platform.
- Add notes or sections highlighting platform parity, such as how to perform steps on Linux, macOS, and Windows.
- Avoid referring to Azure CLI commands as 'PowerShell commands' and ensure accurate terminology throughout.
- Consider including screenshots or instructions for Linux terminal environments where relevant.
Storage
Quickstart: Azure Blob Storage library - Java
...rticles/storage/blobs/storage-quickstart-blobs-java.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Summary
The documentation generally provides both Windows and Linux (Bash) examples for command-line operations, but there are several instances where Windows-specific tools, paths, or instructions are mentioned first or exclusively. PowerShell is explicitly referenced as a console option, and Windows paths (e.g., C:\QuickStarts\blob-quickstart) are shown in output examples. In authentication instructions, PowerShell is given its own tab, and Windows environment variable setup is described before Linux. The documentation does not omit Linux examples, but Windows is often prioritized or receives more detailed attention.
Recommendations
- Alternate the order of Windows and Linux examples/tabs to avoid always listing Windows first.
- When showing output or file paths, provide both Windows and Linux examples, or use platform-neutral paths.
- Avoid referencing PowerShell as the primary or default console; mention Bash and other shells equally.
- In environment variable setup, present Linux and Windows instructions side by side or in parallel, rather than always listing Windows first.
- Ensure that all instructions, screenshots, and sample outputs are inclusive of both Windows and Linux environments.
- Where possible, use language such as 'in your terminal or command prompt' rather than 'console window (such as PowerShell or Bash)' to avoid implying a Windows default.
Storage
Quickstart: Azure Blob Storage library - .NET
...icles/storage/blobs/storage-quickstart-blobs-dotnet.md
High Priority
View Details →
Detected Bias Types
Windows First
Visual Studio Heavy
Powershell In Examples
Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. Visual Studio (Windows-only) is presented as the first and primary IDE option, with detailed step-by-step instructions and screenshots. While the .NET CLI is mentioned as an alternative and Bash is referenced, most setup and workflow examples (project creation, package installation) default to Visual Studio and Windows-centric patterns. PowerShell and cmd are listed as console options alongside Bash, but there are no explicit Linux desktop environment or editor instructions (e.g., for JetBrains Rider, GNOME Terminal, etc.), nor are there screenshots or troubleshooting tips for Linux users. The troubleshooting steps for NuGet sources do not mention Linux-specific issues (e.g., permissions, mono, etc.).
Recommendations
- Present .NET CLI and Visual Studio Code instructions before or alongside Visual Studio, emphasizing cross-platform parity.
- Include Linux-specific setup instructions and screenshots (e.g., Ubuntu terminal, VS Code on Linux, file paths).
- Add troubleshooting tips for common Linux issues (e.g., permissions, package manager differences, mono/.NET compatibility).
- Explicitly mention that all CLI commands work on Linux and macOS, and provide example terminal commands for those platforms.
- Reference Linux editors (e.g., Vim, Emacs, JetBrains Rider) and desktop environments where appropriate.
- Ensure that all screenshots and UI instructions have Linux/macOS equivalents or alternatives.
Storage
Quickstart: Azure Blob Storage client library for Python
...icles/storage/blobs/storage-quickstart-blobs-python.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation page demonstrates subtle Windows bias in several areas. Windows-specific tools (PowerShell, setx) are mentioned before or alongside Linux equivalents, and authentication instructions include PowerShell as a primary option. The environment variable setup instructions list Windows first, and PowerShell is called out as a console option before Bash. There is also a general tendency to mention Windows tools and patterns before Linux alternatives, though Linux instructions are present.
Recommendations
- Present Linux and Windows instructions in parallel, or alternate which comes first to avoid implicit prioritization.
- When listing console options, use 'Bash or PowerShell' or 'your preferred shell' rather than defaulting to PowerShell first.
- In environment variable setup, list Linux and Windows instructions side-by-side, or start with the more platform-neutral Bash example.
- Ensure authentication instructions give equal prominence to Azure CLI (cross-platform) and PowerShell, and clarify that Azure CLI works on both Windows and Linux.
- Add explicit notes that all steps work on Linux, macOS, and Windows, and provide troubleshooting tips for common Linux issues if applicable.
Storage
Upgrade Azure Blob Storage with Azure Data Lake Storage capabilities
...rage/blobs/upgrade-to-data-lake-storage-gen2-how-to.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation demonstrates a Windows bias in several ways: PowerShell is presented as a primary automation method, with instructions to 'Open a Windows PowerShell command window' and references to Windows-specific tools before mentioning cross-platform alternatives. The Azure CLI section suggests using Windows PowerShell as a console application, even though CLI is cross-platform. There are no explicit Linux shell (bash) examples, nor are Linux-specific considerations or instructions provided. The documentation assumes a Windows environment for scripting and automation, and references to Linux or macOS are absent.
Recommendations
- Add explicit bash examples for Azure CLI commands, demonstrating usage in Linux/macOS terminals.
- Replace or supplement 'Open a Windows PowerShell command window' with cross-platform instructions, e.g., 'Open your preferred terminal (PowerShell, Command Prompt, bash, etc.)'.
- Clarify that Azure CLI is available on Windows, Linux, and macOS, and provide installation and usage guidance for each platform.
- Include notes or sections on Linux/macOS-specific considerations, such as file paths, permissions, or shell differences.
- Ensure parity in scripting examples by providing bash shell scripts alongside PowerShell scripts where automation is discussed.
- Review references to 'Windows Azure Storage Blob driver' and clarify cross-platform Hadoop driver support.
Storage
Quickstart: Azure Blob storage library - JavaScript
...icles/storage/blobs/storage-quickstart-blobs-nodejs.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation page shows mild Windows bias. Windows-specific consoles (cmd, PowerShell) are mentioned first when listing console options, and PowerShell is given its own authentication instructions alongside Azure CLI and VS Code. Visual Studio Code is recommended as the editor, which is more common on Windows. The instructions for setting environment variables list Windows (setx) before Linux (export), and provide a separate PowerShell authentication example. There is no explicit omission of Linux equivalents, but Windows tools and patterns are often mentioned first or given more prominence.
Recommendations
- List Bash or Linux terminal options before or alongside Windows cmd/PowerShell when describing console usage.
- Provide authentication instructions for Bash/Linux shells at the same level of detail as PowerShell.
- When recommending editors, mention cross-platform options (e.g., VS Code, Vim, Sublime) or clarify that VS Code is available on Linux and macOS.
- In environment variable setup, present Linux/macOS instructions before or alongside Windows, and clarify differences in shell behavior.
- Ensure all CLI commands and examples are tested and described for Linux/macOS environments, not just Windows.
- Consider adding a section or note explicitly confirming Linux/macOS compatibility for all steps.
Storage
Upgrading Azure Blob Storage to Azure Data Lake Storage
...les/storage/blobs/upgrade-to-data-lake-storage-gen2.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Powershell Heavy
Summary
The documentation page demonstrates a moderate Windows bias. Windows-specific tools (such as PowerShell and AzCopy) are mentioned as primary ways to interact with Azure Data Lake Storage, and references to PowerShell and Windows Azure Storage Blob driver (WASB) appear before Linux or cross-platform alternatives. There are no explicit Linux shell or scripting examples, and Windows-centric terminology and tools are presented without Linux parity.
Recommendations
- Include Linux/Unix shell examples (e.g., Bash, curl, az CLI) alongside or before PowerShell examples.
- Mention cross-platform tools (such as Azure CLI and AzCopy) with explicit notes about Linux usage and installation.
- Reference Linux equivalents for drivers and SDKs, such as Hadoop ABFS usage on Linux clusters.
- Add documentation links or sections for Linux-specific workflows and troubleshooting.
- Ensure tool and command documentation is platform-neutral or provides parallel instructions for both Windows and Linux environments.
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page provides examples for enabling and managing blob versioning using the Azure portal, PowerShell, Azure CLI, and ARM templates. PowerShell is given a dedicated section and example, which is inherently Windows-centric. There are no explicit Linux shell (bash) or scripting examples, and PowerShell is mentioned before Azure CLI in both enabling and listing blob versions. No Linux-specific tools or patterns are referenced, and the CLI examples do not clarify their cross-platform compatibility or provide bash-specific context.
Recommendations
- Add explicit bash (Linux shell) examples for Azure CLI commands, including variable assignment and usage in bash syntax.
- Clarify that Azure CLI commands work cross-platform and provide notes or examples for both Windows (cmd/PowerShell) and Linux (bash).
- Consider including examples using Azure SDKs in Python or other languages commonly used on Linux.
- Balance the order of examples so that Azure CLI (cross-platform) is presented before PowerShell, or alternate the order to avoid Windows-first bias.
- Add a note indicating that PowerShell is available on Linux, but provide bash alternatives for users who prefer native Linux shells.
Storage
Use the Azure Storage resource provider to access management resources
...cles/storage/common/authorization-resource-provider.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates Windows bias by listing Windows-centric tools (PowerShell, Azure classic CLI) before mentioning platform-neutral options (REST API), and omits explicit Linux or cross-platform CLI examples. PowerShell is referenced as a primary management tool, with no mention of Azure CLI (az), which is more commonly used on Linux. There are no Linux-specific instructions or examples, and the code samples section does not clarify platform compatibility.
Recommendations
- Include Azure CLI (az) as a primary management tool alongside PowerShell, with example commands for assigning roles and managing resources.
- Explicitly mention cross-platform compatibility for code samples and management tools.
- Provide Linux-specific instructions or examples where relevant, such as shell commands or environment setup.
- Reorder tool mentions to present platform-neutral or cross-platform options (e.g., Azure CLI, REST API) before Windows-specific tools.
- Clarify that all management operations can be performed from Linux, macOS, and Windows, and provide guidance for each.