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 51-75 of 1657 flagged pages
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 provides detailed PowerShell examples for enabling and managing container soft delete, which are specific to Windows environments. PowerShell instructions are given before Azure CLI, and there are no explicit Linux shell or Bash examples. The use of PowerShell and the absence of Linux-specific instructions or parity in example ordering suggest a Windows bias.
Recommendations
- Add Bash and Linux shell examples alongside PowerShell, especially for common tasks.
- Present Azure CLI examples before or alongside PowerShell to emphasize cross-platform support.
- Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows.
- Include notes or sections for Linux users, such as installation instructions for Azure CLI on Linux.
- Balance screenshots and walkthroughs to include non-Windows environments where possible.
Create Pull Request
Storage
Run an Azure Function in response to a blob rehydration event
...ticles/storage/blobs/archive-rehydrate-handle-event.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation demonstrates a strong Windows bias by exclusively referencing Windows tools and workflows, such as Visual Studio and PowerShell, and by instructing 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, nor are alternative tools (e.g., VS Code, Azure CLI) mentioned. The documentation assumes a Windows development environment throughout and omits Linux-specific guidance or parity.
Recommendations
- Add instructions and examples for developing and deploying Azure Functions using cross-platform tools such as VS Code and Azure CLI.
- Include steps for creating and configuring a Function App with Linux as the operating system, and discuss differences or considerations.
- Provide equivalent package installation commands for Linux/macOS environments (e.g., dotnet CLI instead of PowerShell).
- Mention and link to documentation for developing Azure Functions on non-Windows platforms.
- Ensure screenshots and UI instructions are not Windows-specific, or provide Linux equivalents where applicable.
Storage
Authorize access to blobs using Microsoft Entra ID
...orage/blobs/authorize-access-azure-active-directory.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by consistently mentioning PowerShell before Azure CLI when discussing command-line access, and by referencing PowerShell as a primary example for scripting and automation. There are no explicit Linux-specific examples, nor is there mention of Linux-native tools or workflows. The documentation does not provide parity for Linux users in terms of examples or guidance, and the ordering of tools (PowerShell before CLI) further reinforces a Windows-centric approach.
Recommendations
- Provide explicit Linux examples, such as bash shell commands and usage of Azure CLI on Linux.
- When listing command-line tools, alternate the order or mention Azure CLI before PowerShell to avoid implicit prioritization of Windows tools.
- Include guidance for Linux users, such as installation instructions for Azure CLI on Linux, and troubleshooting tips for common Linux environments.
- Reference cross-platform scripting approaches (e.g., Python, bash) alongside PowerShell.
- Add notes or sections clarifying that all Azure CLI commands are fully supported on Linux and macOS.
- Where possible, provide screenshots or walkthroughs from Linux environments in addition to Windows.
Storage
Best practices for monitoring Azure Blob Storage
...les/storage/blobs/blob-storage-monitoring-scenarios.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation page demonstrates mild Windows bias, primarily by providing a PowerShell example for decoding SAS tokens before mentioning Linux alternatives. Windows tools and patterns (PowerShell, Azure portal screenshots) are referenced first or exclusively in some sections, while Linux equivalents are mentioned later or less prominently. There is no explicit Linux example for some tasks, and the overall flow assumes familiarity with Windows-centric tools.
Recommendations
- Provide Linux/bash examples alongside or before PowerShell examples for tasks such as decoding SAS tokens.
- Include screenshots or instructions for cross-platform tools (e.g., Azure CLI, Storage Explorer on Linux/macOS) where applicable.
- Ensure that references to platform-specific tools (PowerShell, Azure portal) are balanced with alternatives (Azure CLI, REST API, etc.).
- Explicitly state that most operations can be performed on any OS using cross-platform tools and SDKs.
- Add a section or callouts for Linux/macOS users, highlighting platform-agnostic approaches.
Storage
Best practices for using Azure Data Lake Storage
...cles/storage/blobs/data-lake-storage-best-practices.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias. Windows-centric tools (PowerShell, Azure portal, Storage Explorer) are frequently mentioned first in tool lists and examples, especially for ingestion, download, and monitoring tasks. PowerShell is highlighted as a primary method for several operations, and Windows GUI tools (Azure portal, Storage Explorer) are emphasized. While Azure CLI and REST are included, Linux-native patterns and tools (e.g., Bash scripting, Linux file utilities) are not discussed, and there are no explicit Linux command-line examples. The documentation does mention cross-platform tools like AzCopy and DistCp, but Windows tools and patterns are generally presented before their Linux equivalents.
Recommendations
- Provide explicit Linux/Bash command-line examples alongside PowerShell, especially for common tasks like data ingestion, download, and monitoring.
- Include references to Linux-native tools and workflows, such as scripting with Bash, using cron for automation, or leveraging Linux file utilities.
- When listing tools, alternate or balance the order so that Linux-friendly options (Azure CLI, REST, AzCopy) are not always listed after Windows-centric tools.
- Add guidance for using Azure Data Lake Storage from Linux environments, including authentication, automation, and integration with Linux-based data pipelines.
- Clarify cross-platform compatibility of tools (e.g., AzCopy, Azure CLI) and provide installation instructions for Linux systems.
- Where PowerShell is mentioned, also provide equivalent Azure CLI or Bash examples to ensure parity for Linux users.
Storage
Known issues with Azure Data Lake Storage
...ticles/storage/blobs/data-lake-storage-known-issues.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation page exhibits mild Windows bias. PowerShell is mentioned as a primary tool for managing soft-deleted blobs and directories, and Windows Azure Storage Blob (WASB) driver is referenced with no Linux-specific alternatives or parity discussion. Windows tools and terminology (e.g., PowerShell, WASB) are presented before or more prominently than Linux equivalents. While Azure CLI is mentioned, there is little explicit guidance for Linux users, and examples or tool recommendations are not balanced.
Recommendations
- Provide explicit Linux and macOS examples alongside PowerShell, especially for operations like restoring soft-deleted blobs.
- Mention Linux-native tools (e.g., Bash, shell scripts) and show how to use Azure CLI in a Linux environment.
- Clarify cross-platform compatibility for tools like AzCopy and Azure Storage Explorer, including installation and usage notes for Linux.
- When referencing drivers (e.g., WASB, ABFS), note their compatibility with both Windows and Linux Hadoop environments.
- Avoid using Windows-specific terminology (e.g., 'Windows Azure Storage Blob') without also referencing Linux or cross-platform alternatives.
- Add a section or note summarizing parity and differences for Linux users, ensuring they are equally supported.
Storage
Use the Azure portal to manage ACLs in Azure Data Lake Storage
...es/storage/blobs/data-lake-storage-acl-azure-portal.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by primarily referencing Windows-centric tools (Azure Storage Explorer, PowerShell) and listing them before cross-platform or Linux-friendly alternatives (Azure CLI, SDKs). There are no explicit Linux or bash examples, and the guidance does not mention Linux desktop tools or command-line patterns, nor does it provide parity in example commands for Linux users.
Recommendations
- Include explicit Linux/bash command examples for managing ACLs using Azure CLI.
- Mention Linux desktop alternatives to Azure Storage Explorer, if available, or clarify cross-platform support.
- List Azure CLI before PowerShell when suggesting command-line tools, or present them together to avoid order bias.
- Add a section or note highlighting how Linux users can perform the same tasks, including installation and usage tips for Azure CLI and SDKs on Linux.
- Clarify that Azure Storage Explorer and Azure CLI are cross-platform, and provide links to Linux installation guides.
Storage
Filter data by using Azure Data Lake Storage query acceleration
...e/blobs/data-lake-storage-query-acceleration-how-to.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation provides PowerShell examples and instructions for every scenario, but does not offer equivalent Linux shell (bash, CLI) examples. The installation and usage instructions for PowerShell (Az module) are Windows-centric, and PowerShell is presented as the default scripting interface for command-line usage. There is no mention of Linux/Unix shell alternatives, nor are cross-platform command-line tools (such as Azure CLI or bash scripts) provided. PowerShell is listed first in each code tab, reinforcing a Windows-first approach.
Recommendations
- Add Azure CLI (az) examples for each scenario alongside PowerShell, ensuring parity for Linux/macOS users.
- Include bash shell script examples where appropriate, especially for installation and environment setup.
- Explicitly mention cross-platform compatibility for SDKs and tools, and clarify which instructions apply to Linux/macOS.
- Reorder code tabs so that PowerShell is not always first; consider alphabetical or usage-based ordering.
- Add notes or sections on how to perform tasks on Linux/macOS, including package installation and environment setup.
- Reference Linux tools (e.g., curl, jq) where relevant for data manipulation and querying.
Storage
Container-level WORM policies for immutable blob data
...orage/blobs/immutable-container-level-worm-policies.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation page demonstrates Windows bias by referencing PowerShell commands (Remove-AzRmStorageContainer, Remove-AzStorageContainer) as primary examples for container deletion, mentioning them before Azure CLI equivalents. The use of PowerShell and Windows-centric tools is emphasized, while Linux-specific patterns, shell commands, or examples are absent. No Bash or Linux-native command-line examples are provided, and the documentation does not mention Linux environments or considerations.
Recommendations
- Add Linux/Bash shell examples for container deletion and management, using Azure CLI and REST API calls.
- Present Azure CLI examples before or alongside PowerShell examples to ensure platform neutrality.
- Explicitly state that all commands are cross-platform where applicable, and note any platform-specific limitations.
- Include guidance or links for Linux users, such as installing and using Azure CLI on Linux.
- Avoid referencing Windows tools (PowerShell) exclusively; provide parity for Linux and macOS users.
Storage
Configure a lifecycle management policy
...storage/blobs/lifecycle-management-policy-configure.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation page demonstrates a Windows bias by providing detailed PowerShell examples and command breakdowns, while the Azure CLI (more common on Linux/macOS) receives only a brief example. PowerShell is presented before Azure CLI, and Windows-centric tools (PowerShell) are described in greater detail. There are no Linux-specific shell examples (e.g., Bash), nor is there mention of Linux/macOS environments or considerations.
Recommendations
- Provide equally detailed Azure CLI examples, including step-by-step breakdowns similar to the PowerShell section.
- Include Bash script examples for Linux/macOS users, showing how to construct and apply lifecycle management policies.
- Alternate the order of PowerShell and Azure CLI sections, or present CLI first to avoid Windows-first bias.
- Explicitly mention cross-platform compatibility for CLI commands and provide notes for Linux/macOS environments.
- Reference Linux-native tools or patterns where relevant, and avoid assuming PowerShell as the default scripting environment.
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell examples are presented before Azure CLI, and PowerShell is highlighted as a primary automation tool. The .NET SDK examples, which are more common in Windows environments, are also included. There are no explicit Linux shell (bash) or cross-platform scripting examples, and Windows-centric tools (PowerShell, .NET) are given prominence over Linux-native alternatives.
Recommendations
- Add bash and shell scripting examples using Azure CLI to demonstrate Linux-native workflows.
- Explicitly mention that Azure CLI commands work on both Windows and Linux, and provide sample usage in a Linux terminal.
- Include Python SDK examples, which are widely used in cross-platform and Linux environments.
- Balance the order of examples: present Azure CLI before PowerShell or side-by-side, to avoid implying Windows-first workflows.
- Reference cross-platform editors/tools (e.g., VS Code) when discussing SDK usage, rather than assuming .NET/Visual Studio.
- Clarify that all monitoring features are available regardless of OS, and link to platform-specific setup guides if needed.
Storage
Version-level WORM policies for immutable blob data
...storage/blobs/immutable-version-level-worm-policies.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation page demonstrates a Windows bias by referencing PowerShell commands (Remove-AzRmStorageContainer, Remove-AzStorageContainer) as primary examples for control/data plane operations, and mentioning them before Azure CLI equivalents. The use of PowerShell-specific cmdlets and terminology suggests a preference for Windows tooling, with no mention of Linux-specific shell examples or patterns. The CLI example is provided but is secondary to PowerShell, and there are no bash or Linux-native command examples.
Recommendations
- Provide Linux/bash shell examples alongside or before PowerShell examples, especially for common operations like container deletion.
- Use Azure CLI as the primary example, as it is cross-platform, and supplement with PowerShell only as an alternative.
- Explicitly state that all operations can be performed from Linux/macOS environments using Azure CLI or REST API, and provide sample commands.
- Avoid referencing Windows-specific tools or patterns unless there is a clear reason, and always offer Linux equivalents.
- Add a section or note clarifying cross-platform support and listing tools available for both Windows and Linux users.
Storage
Known issues with NFS 3.0 in Azure Blob Storage
...age/blobs/network-file-system-protocol-known-issues.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Powershell Heavy
Summary
The documentation page exhibits mild Windows bias. It mentions PowerShell and Azure CLI as the only methods for enabling static websites, without referencing Linux-specific tools or examples. The workaround for Windows NFS clients is highlighted before any Linux client guidance, and the use of PowerShell is mentioned before Azure CLI, which is cross-platform but often associated with Windows. There are no explicit Linux command examples or references to Linux tools for NFS mounting, and the documentation does not provide parity in examples or instructions for Linux users.
Recommendations
- Add explicit Linux command-line examples (e.g., mount commands) for NFS 3.0 usage.
- Reference Linux tools (such as mount, showmount, etc.) alongside or before Windows/PowerShell tools.
- Clarify that Azure CLI is cross-platform and provide example usage on Linux and macOS.
- Include instructions for enabling static websites using Linux shell commands or scripts.
- Balance the order of client guidance by mentioning Linux NFS clients before Windows workarounds.
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 extensively as a primary automation example, with detailed scripts and explanations. File paths in PowerShell examples use Windows-style (e.g., C:\temp\json.txt), and instructions for saving and loading files assume a Windows environment. The use of PowerShell as a main scripting tool and the lack of explicit Linux shell (bash) or cross-platform scripting examples may disadvantage Linux users. Although Azure CLI is included and is cross-platform, there are no bash-specific or Linux-native command examples, nor are there notes about adapting PowerShell steps for Linux environments.
Recommendations
- Add bash shell examples alongside PowerShell, especially for scripting tasks such as file manipulation and JSON processing.
- Use platform-neutral file paths in examples, or provide both Windows and Linux/Mac equivalents.
- Explicitly mention that Azure CLI works on Linux and Mac, and provide guidance for installation and usage on those platforms.
- Where PowerShell is referenced, clarify its availability on Linux and Mac, or suggest alternatives for users who prefer bash.
- Avoid assuming Windows as the default environment in explanations and screenshots; include notes or visuals for Linux/Mac users where relevant.
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 Windows bias by providing extensive PowerShell examples and referencing PowerShell-specific modules and commands. PowerShell is a Windows-centric tool, and its usage is highlighted alongside the Azure CLI, which is cross-platform. The page also references Windows tooling (PowerShell) before Azure CLI in each example section, and does not mention or provide Linux shell (bash) equivalents or usage patterns, nor does it discuss platform-specific considerations for Linux users.
Recommendations
- Add explicit bash shell examples for Azure CLI commands, showing usage in a Linux environment (e.g., variable assignment, date handling).
- Clarify that Azure CLI is cross-platform and provide guidance for Linux/macOS users, including installation and environment setup.
- Balance the order of examples: alternate or randomize the presentation order of PowerShell and Azure CLI, or lead with Azure CLI to avoid implicit Windows-first bias.
- Mention platform-specific considerations (e.g., date formatting, shell syntax differences) for Linux/macOS users.
- If PowerShell is required for certain advanced scenarios, note its availability on Linux/macOS and provide installation instructions.
Storage
Quickstart: Azure Blob storage library v12 - JS Browser
...s/storage/blobs/quickstart-blobs-javascript-browser.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation demonstrates a subtle Windows bias. In the 'Create the JavaScript project' section, the console window examples list 'cmd, PowerShell, or Bash', but the ordering puts Windows shells first. The instructions for opening the project use 'code .' (Visual Studio Code), which is cross-platform, but the overall workflow and tool recommendations (Visual Studio Code, Node.js) are presented without explicit Linux parity notes. There are no explicit Linux-specific instructions or examples, and no mention of Linux package managers or terminal environments beyond 'Bash'. The 'Run the code' section refers to the 'Visual Studio Code terminal', which may imply a Windows-centric workflow. No Linux-specific troubleshooting or alternative instructions are provided.
Recommendations
- Explicitly mention Linux and macOS as supported platforms in the prerequisites and throughout the setup instructions.
- Provide example commands for common Linux distributions (e.g., Ubuntu) and macOS, including package manager instructions (apt, brew) for installing Node.js and Visual Studio Code.
- When listing console environments, alternate or randomize the order (e.g., 'Bash, cmd, or PowerShell') or explicitly state that any terminal can be used.
- Include notes or links for Linux/macOS users regarding file system paths, permissions, and potential differences in running npm scripts.
- Add troubleshooting tips for Linux/macOS environments, such as handling permissions or installing dependencies.
- Ensure that all instructions and screenshots are platform-neutral or provide platform-specific alternatives where necessary.
Storage
Quickstart: Azure Blob Storage library - C++
...articles/storage/blobs/quickstart-blobs-c-plus-plus.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a Windows bias in several areas: project creation is described exclusively using Visual Studio for Windows, with screenshots and instructions specific to Windows. The initial example for installing packages uses the Windows-style 'vcpkg.exe' command, and the project setup assumes a Visual Studio solution (.sln) and Windows console app. Linux equivalents for project creation, IDEs, or build instructions are not provided. While setting environment variables does mention both Windows and Linux, the overall flow and tooling are Windows-centric.
Recommendations
- Add instructions and examples for creating and building C++ projects on Linux (e.g., using CMake, g++/clang, and editors like VS Code or CLion).
- Provide Linux/macOS equivalents for project setup, including screenshots or terminal commands for common workflows.
- Show 'vcpkg' usage with cross-platform commands (e.g., 'vcpkg install ...' instead of 'vcpkg.exe install ...'), and clarify platform differences.
- Include guidance for running and debugging the sample on Linux, such as terminal commands and troubleshooting tips.
- Balance screenshots and step-by-step instructions between Windows and Linux environments.
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 Windows bias in several ways: Windows-specific tools (WinSCP, Windows registry) are mentioned and explained in detail, often before or instead of Linux equivalents. The registry example is Windows-only, and there is no corresponding example for Linux GUI SFTP clients. The troubleshooting output uses Windows file paths (C:\Users\<user>/.ssh/known_hosts) rather than Linux paths (~/.ssh/known_hosts), and the instructions reference Windows locations first. There is a lack of parity in examples for Linux desktop SFTP clients, and no mention of Linux-specific GUI tools (e.g., FileZilla, Nautilus, etc.), nor is there a Linux registry equivalent discussed.
Recommendations
- Add examples for Linux GUI SFTP clients (e.g., FileZilla, Nautilus, GNOME Files) and how they store trusted host keys.
- When showing troubleshooting output, use both Windows and Linux file paths, or default to the cross-platform ~/.ssh/known_hosts.
- Provide parity in instructions for adding host keys for Linux users, including steps for popular Linux SFTP clients.
- Avoid mentioning Windows registry and WinSCP before Linux equivalents; present both platforms equally.
- Include a note that the .ssh/known_hosts file location is the same on Linux and macOS, and clarify any OS-specific differences.
- If referencing library-based clients, include examples for Python (paramiko), Go, or other popular cross-platform libraries.
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 only a Windows PowerShell example for connecting to Azure Blob Storage via SFTP, mentioning Windows tools (PowerShell, OpenSSH for Windows) first and exclusively, and omitting equivalent Linux/macOS command-line examples. No Linux-specific instructions or screenshots are provided, and the initial example assumes a Windows environment.
Recommendations
- Add Linux and macOS command-line examples for connecting to Azure Blob Storage via SFTP (e.g., using the standard 'sftp' command in a Bash shell).
- Present cross-platform instructions side-by-side or in parallel, rather than Windows-first.
- Mention Linux and macOS OpenSSH clients explicitly, and clarify that the connection syntax is the same across platforms.
- Include screenshots or terminal output from Linux/macOS environments where appropriate.
- Add notes about installing OpenSSH or SFTP clients on Linux/macOS if relevant.
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation page exhibits a mild Windows bias by frequently referencing Windows-specific tools (PowerShell) and patterns, and by mentioning Windows PowerShell as a default console application for Azure CLI usage. PowerShell examples are given equal prominence to Azure CLI, but the CLI instructions reference Windows PowerShell as the example console. There is no explicit Linux example or mention of Linux shells (e.g., Bash, zsh), nor are Linux-specific instructions or screenshots provided.
Recommendations
- Explicitly mention that Azure CLI commands can be run in Bash, zsh, or other Linux shells, not just Windows PowerShell.
- Provide example commands for both Windows PowerShell and Linux Bash where applicable, especially for Azure CLI usage.
- Avoid referencing Windows PowerShell as the default console for CLI usage; instead, use neutral language such as 'open a command-line shell' or specify both Windows and Linux options.
- Include screenshots or instructions for enabling soft delete using Linux environments if relevant.
- Add a note or section clarifying cross-platform compatibility for all command-line instructions.
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
Missing Linux Example
Summary
The documentation page demonstrates a mild Windows bias. In the 'Home directory' section, SFTP command-line examples are shown with a 'powershell' code block tag, and the only explicit SFTP example references OpenSSH documentation for Windows. There are no Linux-specific SFTP usage examples or references to Linux tools, and the ordering and framing of examples implicitly assume a Windows-first audience.
Recommendations
- Provide SFTP command-line examples using a generic shell or explicitly include both Windows (PowerShell/CMD) and Linux (bash) code block tags.
- Reference both Windows and Linux OpenSSH documentation, or link to cross-platform OpenSSH resources.
- Include explicit Linux usage examples (e.g., sftp command from a Linux terminal) alongside Windows examples.
- Avoid using 'powershell' code block tags for generic SFTP commands; use 'bash' or 'shell' where appropriate.
- Mention common Linux SFTP clients (e.g., lftp, sftp, Nautilus, etc.) in the 'Known supported clients' section if applicable.
Storage
Example Azure role assignment conditions for Blob Storage
...n/articles/storage/blobs/storage-auth-abac-examples.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation page provides detailed examples for Azure role assignment conditions for Blob Storage, but all CLI/script examples are exclusively in Azure PowerShell. There are no examples using cross-platform tools such as Azure CLI, Bash, or Linux shell scripting. This creates a Windows bias, as PowerShell is primarily a Windows-centric tool, and Linux users are not provided with equivalent guidance or examples.
Recommendations
- Add equivalent Azure CLI examples for each PowerShell script, demonstrating how to perform the same role assignment and testing actions using az commands.
- Include Bash or shell script snippets for common tasks, especially for testing access to blobs, to support Linux and macOS users.
- Explicitly mention cross-platform options and tools (e.g., Azure CLI, REST API) alongside PowerShell, and provide links to relevant documentation.
- Where PowerShell is used, clarify that it is available cross-platform, but still provide alternatives for users who prefer native Linux tools.
- Add a section or callout highlighting Linux/macOS usage patterns and considerations for Azure Storage ABAC scenarios.
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 a dedicated section with detailed installation and usage steps, while Linux-specific instructions (such as Bash or shell scripting) are absent. The order of examples places PowerShell before ARM templates, and the Azure CLI example is generic, lacking any Linux-specific context or troubleshooting. There are no references to Linux tools or patterns, and no mention of Linux-specific considerations for enabling or consuming the change feed.
Recommendations
- Add explicit Linux/Bash shell examples for enabling the change feed, including installation and authentication steps relevant to Linux environments.
- Provide troubleshooting tips for common Linux issues (e.g., az CLI authentication, permissions, environment variables).
- Include references to Linux-native tools (such as curl, jq, or bash scripts) for interacting with Azure Blob Storage and processing Avro files.
- Reorder the examples so that cross-platform (CLI, REST API) instructions appear before platform-specific ones (PowerShell), or present them side-by-side.
- Clarify that Azure CLI commands work on both Windows and Linux, and provide any necessary platform-specific flags or environment setup instructions.
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 demonstrates a Windows bias by frequently referencing Windows-specific tools and patterns. Examples include consistently suggesting Windows PowerShell as the default local shell for Azure CLI, using Windows file paths (e.g., C:\demo-file.txt) in CLI and PowerShell examples, and prioritizing PowerShell instructions. There is little to no mention of Linux shells (e.g., Bash) or Linux file path conventions, and no explicit Linux-specific guidance is given.
Recommendations
- Provide explicit examples for Linux/macOS users, including Bash shell commands and POSIX-style file paths (e.g., /home/user/demo-file.txt).
- When referencing local shells for Azure CLI, mention Bash, zsh, or other common Linux/macOS shells alongside Windows PowerShell.
- Add notes or tabs for Linux/macOS environments where command syntax or file paths differ.
- Avoid using only Windows-style file paths in examples; show both Windows and Linux/macOS equivalents.
- Ensure parity in tool recommendations and instructions, e.g., mention that AzCopy and Azure CLI are cross-platform and provide usage examples for each OS.
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 Windows-centric biases. PowerShell is featured prominently as a primary automation method, with instructions explicitly referencing 'Windows PowerShell' and examples using Windows-style paths (e.g., C:\temp\index.html). In several places, Windows tools and terminology are mentioned first or exclusively (e.g., suggesting 'Windows PowerShell' as the console for Azure CLI, using Windows file paths in examples, and referencing Windows-specific installation instructions). There is a lack of explicit Linux or macOS examples, and Linux shell conventions (such as bash, zsh, or POSIX paths) are not shown, which may lead Linux users to feel unsupported or confused.
Recommendations
- Provide explicit Linux/macOS instructions and examples alongside Windows ones, especially for CLI and PowerShell sections.
- Use platform-neutral terminology when referring to command consoles (e.g., 'terminal' or 'command line'), and clarify that Azure CLI can be used from any OS.
- Include Linux-style file path examples (e.g., /home/user/index.html) in CLI and PowerShell sections.
- Mention alternative shells (bash, zsh) and tools where relevant, and avoid implying that PowerShell is required or preferred for CLI usage.
- Add notes or tabs for Linux/macOS users where installation or usage steps differ, ensuring parity in guidance and examples.