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 1401-1425 of 1657 flagged pages
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/storage-quickstart-blobs-nodejs.md
...icles/storage/blobs/storage-quickstart-blobs-nodejs.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation generally maintains cross-platform parity but exhibits subtle Windows bias in a few areas. In the project setup section, Windows tools like Visual Studio Code ('code .') are referenced without mentioning alternatives. In authentication instructions, Windows-centric tools (PowerShell) are listed alongside cross-platform options, but Windows is often mentioned first. When setting environment variables, Windows instructions precede Linux, and the Windows-specific 'setx' command is shown before the Linux 'export' command.
Recommendations
- When referencing code editors, mention alternatives to Visual Studio Code or clarify that 'code .' is optional and VS Code is cross-platform.
- For environment variable instructions, present Linux/macOS and Windows commands side by side or in separate tabs, without always listing Windows first.
- In authentication sections, avoid listing PowerShell before cross-platform tools, or group instructions by OS with equal prominence.
- Explicitly state that all commands and steps work on Linux, macOS, and Windows, and provide Bash or zsh examples where relevant.
- Where possible, use neutral language like 'terminal' or 'shell' instead of 'console window (such as cmd, PowerShell, or Bash)'.
Create Pull Request
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/files/storage-files-netapp-comparison.md
...icles/storage/files/storage-files-netapp-comparison.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation page lists several migration tools that are Windows-centric (e.g., Robocopy, Storage Migration Service, Azure File Sync) without mentioning Linux-native equivalents or providing Linux usage examples. There are no explicit Linux command-line examples or references to Linux tools, despite both services supporting NFS and Linux workloads.
Recommendations
- Include Linux-native migration tools (e.g., rsync, NFS copy, scp, or Linux-based data movers) in the migration tools lists.
- Provide example commands or workflows for both Windows (e.g., Robocopy, AzCopy) and Linux (e.g., rsync, cp, mount) environments.
- Mention Linux authentication and integration options (e.g., LDAP, Kerberos for NFS) more explicitly and provide links to relevant Linux setup guides.
- Ensure that documentation and linked resources cover both SMB (Windows) and NFS (Linux/UNIX) scenarios equally, including setup and troubleshooting.
- Where tools are cross-platform (e.g., AzCopy), clarify their usage on both Windows and Linux.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/queues/assign-azure-role-data-access.md
...ticles/storage/queues/assign-azure-role-data-access.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides detailed instructions and examples for both PowerShell and Azure CLI, but the PowerShell (Windows-centric) section is presented before the Azure CLI (cross-platform) section. There are no Linux-specific examples or references to Linux tools, but Azure CLI is inherently cross-platform. No explicit Windows-only tools are mentioned, but the ordering and emphasis on PowerShell may signal a Windows-first bias.
Recommendations
- Present Azure CLI examples before PowerShell, as Azure CLI is cross-platform and more accessible to Linux and macOS users.
- Explicitly mention that both PowerShell and Azure CLI are available on Windows, Linux, and macOS, and provide installation links for each platform.
- Consider adding a short section or note highlighting that all examples work on Linux and macOS, not just Windows.
- If possible, provide bash shell examples or clarify that Azure CLI commands are intended for use in bash/zsh as well as Windows command prompt or PowerShell.
- Review other documentation pages for similar ordering and ensure parity in example prominence for cross-platform tools.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/files/storage-python-how-to-use-file-storage.md
...torage/files/storage-python-how-to-use-file-storage.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows-first bias in its examples and guidance for mounting Azure file shares and using file paths. Specifically, the only concrete file path examples use Windows-style paths (e.g., 'Z:\\file-share'), and all code samples for file I/O reference these Windows paths. While links to both Windows and Linux mounting instructions are provided, there are no Linux or cross-platform code examples or file path usages. This may make it less approachable for Linux developers or those working in cross-platform environments.
Recommendations
- Provide Linux-specific or cross-platform file path examples alongside Windows examples (e.g., '/mnt/file-share' for Linux).
- Include at least one code example using a Linux-style mounted path, or demonstrate how to write code that works on both platforms (e.g., using os.path.join and platform detection).
- When referencing mounting instructions, alternate the order or present both Windows and Linux options equally, rather than listing Windows first.
- Add notes or code comments clarifying how to adapt examples for Linux environments.
- Consider including a section or callout on cross-platform compatibility and best practices for supporting both Windows and Linux in Python applications using Azure Files.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/solution-integration/validated-partners/data-management/cirrus-data-migration-guide.md
...artners/data-management/cirrus-data-migration-guide.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation exhibits a mild 'Windows-first' bias by linking to Windows-specific Azure VM quickstart and overview pages before or instead of Linux equivalents. While the main migration example uses a Linux source host and Linux commands (e.g., iostat), there are no explicit Linux-focused Azure VM setup links or parity in 'Next steps' resources. There are no PowerShell-heavy sections or exclusive use of Windows tools, but Linux users may find the guidance less discoverable.
Recommendations
- In the 'Implementation guide', provide links to both Windows and Linux Azure VM quickstart guides, or a neutral landing page that covers both.
- In the 'Next steps' section, include links to both Windows and Linux Azure VM overview pages.
- Wherever VM setup is referenced, clarify that the process applies to both Windows and Linux, and provide OS-agnostic or parallel instructions.
- Consider adding a brief section or callout for Linux users, summarizing any OS-specific considerations or linking to relevant Azure Linux documentation.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/storage-explorer/vs-azure-tools-storage-explorer-accessibility.md
...lorer/vs-azure-tools-storage-explorer-accessibility.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Summary
The documentation page demonstrates bias by omitting Linux support for screen readers and not providing any Linux-specific accessibility guidance or keyboard shortcuts. Windows is listed first in the screen reader table, and only Windows and Mac are mentioned as supported platforms. All shortcut keys use Windows-style notation, with no mention of Linux alternatives or differences.
Recommendations
- Clarify whether Linux support is planned or possible for screen readers, and provide updates if/when it becomes available.
- If Storage Explorer is available on Linux, explicitly state the accessibility limitations and suggest any possible workarounds (e.g., using Wine with Windows screen readers, or community-supported tools).
- Include Linux-specific instructions or notes for keyboard shortcuts, especially if they differ from Windows/Mac.
- List platforms in a neutral order (e.g., alphabetical: Linux, Mac, Windows) to avoid implicit prioritization.
- Provide parity in documentation by mentioning accessibility features or limitations for all supported platforms, not just Windows and Mac.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/storage-explorer/vs-azure-tools-storage-manage-with-storage-explorer.md
...ttps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/storage-explorer/vs-azure-tools-storage-manage-with-storage-explorer.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation generally covers Windows, macOS, and Linux in parallel, especially in the prerequisites and installation sections. However, there is evidence of Windows bias: Windows is consistently presented first in tabbed sections, and the legacy Azure Storage Emulator (which is Windows-only) is mentioned before Azurite (cross-platform) in the local emulator section. There are no PowerShell-heavy examples or missing Linux examples, but the ordering and some tool references prioritize Windows.
Recommendations
- Rotate or randomize the order of OS tabs (Windows, macOS, Linux) or use alphabetical order to avoid always listing Windows first.
- In the local storage emulator section, mention Azurite (cross-platform) before the legacy Azure Storage Emulator (Windows-only), and clarify Azurite as the recommended emulator.
- Where possible, ensure that any tool or workflow mentioned for Windows has an equivalent or alternative for Linux/macOS, and present them with equal prominence.
- Explicitly state when a feature or tool is Windows-only to help set user expectations.
- Consider adding more Linux/macOS-specific troubleshooting or usage tips to further balance the documentation.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/queues/storage-quickstart-queues-nodejs.md
...les/storage/queues/storage-quickstart-queues-nodejs.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation demonstrates a mild Windows bias, particularly in the 'Create the project' section, where Windows shells (cmd, PowerShell) are mentioned before Bash, and Visual Studio Code (a Microsoft tool) is suggested as the editor without mentioning alternatives. However, most commands and instructions are cross-platform, and Linux is not excluded, but Windows environments are prioritized in the order of mention.
Recommendations
- When listing console options, use neutral or alphabetical order (e.g., 'Bash, cmd, or PowerShell') or simply say 'in a terminal' to avoid prioritizing Windows shells.
- When suggesting editors, mention alternatives to Visual Studio Code (e.g., 'Open the project in your preferred code editor, such as Visual Studio Code, Atom, or Sublime Text').
- Explicitly state that all commands are cross-platform and work on Windows, Linux, and macOS.
- Where environment variable instructions are given, clarify any OS-specific differences (e.g., how to set environment variables in Bash vs. PowerShell/cmd).
- Include example output or screenshots from both Windows and Linux terminals, if possible, to reinforce cross-platform parity.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/blob-cli.md
...zure-docs/blob/main/articles/storage/blobs/blob-cli.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation provides Bash-based Azure CLI examples, which are generally cross-platform, but consistently uses Windows-style file paths (e.g., C:\temp\) and references to Windows filesystem locations in variable assignments and instructions. There are no explicit Linux or macOS path examples, and the XML file example instructs users to create files in C:\temp, a Windows-specific directory. This may confuse or exclude Linux/macOS users, as no equivalent Linux paths (e.g., /tmp or ~/temp) are shown. No PowerShell-specific commands or Windows-only tools are used, but the path conventions and file location instructions display a subtle Windows-first bias.
Recommendations
- Provide both Windows and Linux/macOS path examples in all code snippets and instructions (e.g., use $HOME/temp or /tmp for Linux/macOS, and C:\temp for Windows).
- Add a note at the start of the article clarifying that file paths should be adapted to the user's OS, with examples for each.
- When referencing file creation or locations (such as the XML file example), include both Windows and Linux/macOS instructions.
- Consider using environment variables (like $HOME or %USERPROFILE%) in examples to make them more cross-platform.
- Explicitly state that the Bash examples work on both Windows (with WSL or Git Bash) and Linux/macOS, and provide guidance for PowerShell users if relevant.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/blob-storage-monitoring-scenarios.md
...les/storage/blobs/blob-storage-monitoring-scenarios.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation generally avoids strong platform bias, but in the section on decoding SAS token signatures, PowerShell is presented as the primary example, with the Linux/bash alternative mentioned only after. This ordering and the use of PowerShell as the default may suggest a slight Windows-first and PowerShell-heavy bias. Otherwise, the documentation is platform-neutral, focusing on Azure Portal, Kusto queries, and SQL, which are cross-platform.
Recommendations
- When providing code examples for tasks like decoding or hashing, present Linux/bash and Windows/PowerShell examples side by side, or explicitly state that both are supported.
- Avoid listing PowerShell examples first by default; alternate the order or provide both together.
- Where possible, use cross-platform tools (e.g., Azure CLI, Python scripts) in examples.
- Explicitly mention that tasks can be performed on both Windows and Linux, and provide equivalent command-line examples for both.
- Review other sections for subtle platform assumptions (e.g., references to Windows-only tools or UI patterns) and ensure parity.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/blob-upload-function-trigger-javascript.md
...orage/blobs/blob-upload-function-trigger-javascript.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a bias toward Windows environments by providing detailed instructions and screenshots for Visual Studio Code (with Windows-style keyboard shortcuts) and the Azure Portal, but does not include any explicit Linux- or macOS-specific instructions or terminal-based file upload examples. All tooling and workflows are described in a cross-platform way, but the lack of Linux/macOS-specific guidance or CLI-based alternatives for certain steps (such as uploading files to Blob Storage) may disadvantage Linux users.
Recommendations
- Add explicit Linux/macOS instructions or notes, especially for keyboard shortcuts and file paths in Visual Studio Code.
- Provide CLI-based alternatives for all major steps, including uploading files to Blob Storage (e.g., using 'az storage blob upload' or 'azcopy'), not just resource creation.
- Include screenshots or terminal examples from Linux environments where possible.
- Clarify that Visual Studio Code and its Azure extensions are cross-platform, and mention any OS-specific considerations.
- When listing multiple methods (e.g., VS Code, Portal, CLI), ensure CLI instructions are always present and not just for resource creation.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/data-lake-storage-abfs-driver.md
...rticles/storage/blobs/data-lake-storage-abfs-driver.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation refers to the 'Windows Azure Storage Blob driver' (WASB) as the prior capability, using 'Windows' in the driver name and description. This positions Windows terminology and tooling first, even though the driver is cross-platform. No explicit Linux or cross-platform command-line examples or tools are highlighted, and the configuration and usage instructions are generic but do not provide Linux-specific guidance or parity.
Recommendations
- Clarify that 'Windows Azure Storage Blob driver' is a legacy name and that the driver is cross-platform, not Windows-specific.
- Add explicit Linux and macOS usage notes or examples, especially for configuration file locations and command-line usage.
- Avoid using 'Windows' in section headings or descriptions unless strictly necessary; prefer 'Azure Storage Blob driver (WASB)'.
- Where tools like Ambari are mentioned, note their cross-platform nature or provide alternatives for Linux environments.
- Include a section or callout confirming that all features and instructions apply equally to Linux, macOS, and Windows environments.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/data-lake-storage-directory-file-acl-cli.md
...rage/blobs/data-lake-storage-directory-file-acl-cli.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a mild Windows bias. It references Windows PowerShell as the example of a 'command console application' before mentioning alternatives, and file path examples for upload and download operations use Windows-style paths (e.g., C:\myFolder\upload.txt) exclusively. There are no Linux or macOS shell or file path examples, which may confuse or exclude users on those platforms.
Recommendations
- When referencing command consoles, mention cross-platform options first or equally (e.g., 'open a terminal such as Windows PowerShell, Command Prompt, or a Bash shell on Linux/macOS').
- For file path examples, provide both Windows (C:\myFolder\file.txt) and Linux/macOS (/home/user/myFolder/file.txt) variants, or use a note to clarify path differences.
- Explicitly state that the Azure CLI is cross-platform and can be used on Windows, Linux, and macOS.
- Wherever possible, alternate or parallelize examples to show parity between Windows and Linux/macOS usage patterns.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/data-lake-storage-use-hdfs-data-lake-storage.md
.../blobs/data-lake-storage-use-hdfs-data-lake-storage.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation page is generally Linux-focused, as it discusses using the HDFS CLI on an HDInsight Hadoop cluster on Linux and provides standard HDFS commands. However, there is a notable instance of Windows bias: the SSH connection example is given in PowerShell syntax, and the phrase 'the sample PowerShell code would look as follows' is used, even though SSH and HDFS CLI usage is essentially the same on Linux and macOS. There are no Linux shell (bash) examples, and the PowerShell example is presented first and exclusively, which may confuse or alienate Linux users.
Recommendations
- Provide both PowerShell and bash (Linux/macOS) examples for SSH and HDFS CLI commands, or use a neutral shell syntax.
- Avoid referring to SSH command-line examples as 'PowerShell code' when the commands are cross-platform.
- If referencing Windows tools or shells, ensure Linux equivalents are given equal prominence and are presented first if the context is Linux-centric.
- Clarify that the HDFS CLI commands are the same across platforms, and specify any platform-specific differences if they exist.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/secure-file-transfer-protocol-performance.md
...age/blobs/secure-file-transfer-protocol-performance.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation demonstrates a mild Windows bias by mentioning WinSCP (a Windows SFTP client) first and providing configuration details specific to it, while not mentioning any Linux-native SFTP clients (such as lftp or command-line OpenSSH SFTP) in that section. In the network latency section, Windows and Linux OpenSSH examples are both provided, but the Windows example appears first. There are no PowerShell-specific commands, but the focus on WinSCP and ordering of examples may make Linux users feel secondary.
Recommendations
- Include examples and configuration details for popular Linux SFTP clients (e.g., lftp, command-line sftp) alongside or before Windows-specific tools like WinSCP.
- When listing client examples, alternate the order or present both Windows and Linux options together to avoid a 'Windows-first' impression.
- Provide equivalent instructions for adjusting logging and concurrency in Linux-native clients, not just WinSCP.
- Consider a table or section that summarizes SFTP client options and relevant settings for both Windows and Linux environments.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/secure-file-transfer-protocol-known-issues.md
...ge/blobs/secure-file-transfer-protocol-known-issues.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a mild Windows bias by providing a client settings example only for WinSCP, a popular Windows SFTP client, without mentioning or providing equivalent guidance for common Linux/macOS SFTP clients (such as OpenSSH's sftp command-line tool, FileZilla, or lftp). No Linux-specific tools, commands, or troubleshooting steps are referenced, and the only client configuration advice is tailored to a Windows environment.
Recommendations
- Include configuration and troubleshooting examples for widely used Linux/macOS SFTP clients, such as the OpenSSH sftp command-line tool.
- Mention cross-platform SFTP clients (e.g., FileZilla) and provide any relevant settings or caveats for those clients.
- When listing client settings or known issues, avoid focusing exclusively on Windows tools; provide parity by including Linux and macOS equivalents.
- If there are no special settings required for Linux clients, explicitly state this to reassure non-Windows users.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/snapshots-overview.md
...blob/main/articles/storage/blobs/snapshots-overview.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page does not provide any OS-specific command-line examples, but in the 'Next steps' section, it links only to a Windows-specific guide for backing up Azure unmanaged VM disks with incremental snapshots. There is no mention of Linux or cross-platform alternatives for this scenario, and the example scenario involving VHD files and VM disks implicitly references Windows-centric workflows. No Linux tools, patterns, or parity are discussed.
Recommendations
- Add links or references to equivalent Linux or cross-platform guides for managing and backing up Azure VM disks with snapshots.
- Include examples or scenarios relevant to Linux-based VMs and their disk formats (e.g., VHD for Linux, or mention how the process applies to Linux VMs).
- Ensure that 'Next steps' and scenario sections provide parity by including both Windows and Linux management workflows.
- If referencing tools like AzCopy, clarify their cross-platform support and provide usage examples for both Windows and Linux environments.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/snapshots-manage-dotnet.md
...main/articles/storage/blobs/snapshots-manage-dotnet.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Summary
The documentation exclusively provides .NET (C#) code examples and does not mention or provide any platform-specific instructions, but it implicitly assumes a Windows development environment by omitting any Linux or cross-platform setup, tooling, or command-line examples. There is no discussion of Linux-specific considerations or parity in developer experience.
Recommendations
- Explicitly state that the .NET SDK and examples are cross-platform and can be used on Linux, macOS, and Windows.
- Add instructions or notes for setting up the development environment on Linux (e.g., using .NET SDK on Ubuntu, installing required packages, using VS Code or JetBrains Rider).
- Provide sample commands for common Linux shells (bash/zsh) where relevant, such as environment variable setup or running the sample code.
- Mention any OS-specific caveats or differences in authentication, file paths, or dependencies.
- Include links to .NET installation guides for Linux and macOS, not just Windows.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/storage-blob-container-properties-metadata.md
...ge/blobs/storage-blob-container-properties-metadata.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Summary
The documentation page exclusively provides .NET (C#) code examples and setup instructions, which are typically associated with Windows development environments. There are no references to Linux-specific tools, shell commands, or cross-platform considerations. The environment setup and code samples implicitly assume a Windows or Visual Studio context, and there is no mention of how to perform equivalent tasks on Linux or using Linux-preferred tooling.
Recommendations
- Include explicit instructions and examples for setting up and running the .NET client library on Linux, such as using the .NET CLI and common Linux shells (e.g., bash).
- Mention cross-platform compatibility of the .NET SDK and provide guidance for both Windows and Linux users.
- Add code snippets or terminal commands that demonstrate how to perform the same operations in a Linux environment.
- Clarify any platform-specific prerequisites or differences in behavior between Windows and Linux.
- Reference Linux-friendly editors (e.g., VS Code) and package managers (e.g., apt, yum) where appropriate.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/storage-blob-download.md
...b/main/articles/storage/blobs/storage-blob-download.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation page assumes a Windows environment by referencing exceptions and file system behaviors specific to .NET on Windows (e.g., DirectoryNotFoundException, local file paths), and does not mention or provide examples for Linux or cross-platform file handling. There are no Linux-specific considerations or examples, and the language and patterns are implicitly Windows-centric.
Recommendations
- Explicitly mention that the .NET client library and code samples work on both Windows and Linux, and note any cross-platform differences in file path handling or permissions.
- Provide examples or notes for running the code on Linux, such as using Linux-style file paths (e.g., '/tmp/myfile.txt') in addition to Windows-style paths (e.g., 'C:\temp\myfile.txt').
- Clarify exception handling for file operations on Linux (e.g., DirectoryNotFoundException is also thrown on Linux, but directory creation and permissions may differ).
- Include a brief section or callout about cross-platform compatibility and any environment-specific prerequisites or behaviors.
- Avoid assuming a Windows file system structure in code comments and documentation text.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/storage-auth-abac-examples.md
...n/articles/storage/blobs/storage-auth-abac-examples.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Summary
The documentation provides detailed step-by-step examples for configuring Azure Blob Storage role assignment conditions using the Azure portal and Azure PowerShell. However, it lacks equivalent command-line examples for Linux users, such as Azure CLI (az) or bash scripts. All command-line automation and testing guidance is exclusively presented in PowerShell, which is primarily a Windows-centric tool, leading to a Windows bias.
Recommendations
- Add equivalent Azure CLI (az) command examples for all PowerShell scripts, covering both condition creation and testing.
- Where file paths or scripting are shown, provide bash-compatible examples alongside PowerShell.
- Explicitly mention cross-platform options (e.g., Azure CLI, REST API) in the prerequisites and example sections.
- For each 'Here's how to add this condition using Azure PowerShell' section, add a parallel 'Here's how to add this condition using Azure CLI' section.
- Include notes or links for Linux/macOS users on how to perform the same tasks without PowerShell.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/storage-blob-user-delegation-sas-create-dotnet.md
...lobs/storage-blob-user-delegation-sas-create-dotnet.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Summary
The documentation is focused exclusively on .NET usage, which is most commonly associated with Windows environments. There are no examples or mentions of Linux-specific workflows, tools, or shell environments (such as Bash), nor is there any guidance for cross-platform usage. All code samples are in C# and assume the use of the .NET client library, with no reference to command-line tools, REST API usage from non-Windows platforms, or alternative programming environments.
Recommendations
- Add examples or notes for using the Azure Storage REST API directly, which is platform-agnostic and can be used from Linux environments with tools like curl.
- Include cross-platform command-line examples (e.g., using Azure CLI or Bash scripts) for obtaining user delegation SAS tokens.
- Explicitly mention that the .NET client library is cross-platform and provide instructions or examples for running the code on Linux (e.g., using .NET Core on Ubuntu).
- Provide links or references to equivalent documentation for other languages or platforms (such as Python, Java, or Node.js) that are commonly used on Linux.
- Clarify in the introduction that while the guide uses .NET, the concepts apply to all platforms and provide pointers for Linux users.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/storage-blobs-list.md
...blob/main/articles/storage/blobs/storage-blobs-list.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Summary
The documentation provides .NET code samples and references output as 'console window', but does not specify or show examples for Linux environments or shells. There is an implicit assumption of a Windows environment (e.g., 'console window'), and no mention of Linux-specific considerations or parity in setup, execution, or output. There are no PowerShell-specific commands, but the lack of Linux/Unix shell references or examples constitutes a subtle Windows-first and missing-Linux-example bias.
Recommendations
- Clarify that the .NET examples are cross-platform and can be run on Linux, macOS, and Windows.
- Include explicit instructions or notes for running the code on Linux (e.g., using dotnet CLI in bash/zsh).
- Show sample output in a way that is neutral (e.g., 'terminal output' instead of 'console window'), or provide both Windows and Linux terminal examples if there are differences.
- Mention any OS-specific prerequisites or differences in environment setup, if applicable.
- If referencing file paths or delimiters, clarify cross-platform behavior (e.g., forward slash is standard on both platforms, but clarify if any .NET APIs behave differently on Windows vs. Linux).
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/storage-retry-policy.md
...ob/main/articles/storage/blobs/storage-retry-policy.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Summary
The documentation focuses exclusively on .NET and C# examples, which are most commonly associated with Windows development environments. There are no Linux-specific instructions, examples, or references to cross-platform usage, and no mention of how to implement retry policies using the Azure Storage client library in Linux environments or with other languages/tools more common on Linux.
Recommendations
- Include examples or notes on how to implement retry policies using the Azure Storage client library for .NET on Linux (e.g., using .NET Core/.NET 6+ on Linux).
- Add references or links to equivalent documentation for other platforms/languages (such as Python, Java, or Node.js), which are commonly used on Linux.
- Explicitly mention that the .NET Azure Storage client library is cross-platform and provide guidance for Linux users (e.g., installation steps, environment setup).
- Provide sample commands for running the code on Linux (e.g., using the dotnet CLI) alongside any Windows-specific instructions.
- Ensure parity in tooling and troubleshooting sections, mentioning both Windows and Linux development environments where relevant.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/storage-feature-support-in-storage-accounts.md
...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 commands as supported features, but only explicitly calls out PowerShell (a Windows-centric tool) in the feature tables. There is a dedicated row for 'Blob Storage PowerShell commands', but no equivalent row for Linux-native scripting tools (e.g., Bash, shell scripts) or SDKs. While 'Blobfuse' (a Linux tool) is included, the presence of PowerShell as a first-class citizen without an explicit Linux shell equivalent suggests a mild Windows bias.
Recommendations
- Add a row for 'Blob Storage Bash/shell scripts' or 'Blob Storage SDKs for Linux' to the feature tables to provide parity with the PowerShell row.
- Where PowerShell is mentioned, also mention Bash or other Linux-native scripting options, or clarify that Azure CLI is cross-platform.
- Consider providing links to Linux-specific quickstarts or usage guides alongside PowerShell and Azure CLI references.
- Ensure that examples and tooling references are balanced between Windows and Linux environments to avoid implicit prioritization of Windows tools.