Storage
1359
Total Pages
1162
Linux-Friendly Pages
197
Pages with Bias
14.5%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
392 issues found
Showing 326-350 of 392 flagged pages
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Windows Heavy Examples
Summary
The documentation page exhibits mild Windows bias, primarily in its terminology, analogies, and value-added services. Windows is referenced first in several places (e.g., in the discussion of storage unit labeling and in analogies for snapshots), and Windows-specific tools and services (such as Azure File Sync for Windows file servers and VSS) are mentioned without equivalent Linux/macOS examples. The documentation does not provide Linux/macOS-specific instructions, examples, or value-added service integrations, and does not mention Linux tools or patterns for managing Azure Files. However, the core billing content is platform-neutral.
Recommendations
- Add Linux/macOS-specific examples or references, especially for mounting Azure Files, managing shares, and monitoring usage.
- Include analogies or explanations relevant to Linux/macOS users (e.g., compare snapshots to LVM snapshots or ZFS/Btrfs snapshots).
- Mention or link to Linux/macOS tools for interacting with Azure Files (e.g., mount.cifs, NFS client usage, Azure CLI on Linux).
- Discuss value-added services or third-party integrations available for Linux/macOS environments.
- Ensure that instructions for enabling features (e.g., soft delete, paid bursting) are available for CLI and not just PowerShell.
Create Pull Request
Storage
Assign an Azure role for access to queue data
...ticles/storage/queues/assign-azure-role-data-access.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation provides both PowerShell and Azure CLI examples for assigning Azure roles, but PowerShell (a Windows-centric tool) is presented before Azure CLI. There are no explicit Linux/macOS shell examples (e.g., Bash), nor any mention of platform-specific considerations for Linux or macOS users. The PowerShell example is detailed and uses Windows-style syntax, while the Azure CLI example is more generic. No Linux-specific tools or instructions are provided.
Recommendations
- Alternate the order of PowerShell and Azure CLI examples, or present Azure CLI first, as it is cross-platform.
- Explicitly mention that Azure CLI works on Linux/macOS and provide Bash shell examples or notes on usage in those environments.
- Add a note clarifying that PowerShell Core is available on Linux/macOS, or provide instructions for installing/running PowerShell on those platforms.
- Include troubleshooting or environment setup tips for Linux/macOS users where relevant.
Storage
Quickstart: Azure Queue Storage client library - .NET
...les/storage/queues/storage-quickstart-queues-dotnet.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation page is generally cross-platform, but there is a minor Windows bias in the 'Create the project' section, where Windows consoles (cmd, PowerShell) are mentioned before Bash. All commands shown are cross-platform (dotnet CLI), and there are no Windows-only tools or examples. No critical Linux/macOS omissions are present.
Recommendations
- List Bash (Linux/macOS) equally or first when mentioning console options.
- Explicitly state that all commands work on Linux, macOS, and Windows.
- Provide brief notes or links for Linux/macOS users regarding environment variable setup and editor choices, if relevant.
- Ensure screenshots and instructions (if any) do not assume Windows-only environments.
Storage
Quickstart: Azure Queue Storage client library for JavaScript
...les/storage/queues/storage-quickstart-queues-nodejs.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation mentions Windows-specific consoles ('cmd, PowerShell') before Bash when instructing users to create the project directory. It also recommends opening the project in Visual Studio Code using the 'code .' command, which is cross-platform but often associated with Windows workflows. No PowerShell-specific commands, Windows-only tools, or missing Linux/macOS examples are present. All commands and code samples are platform-agnostic and work on Linux/macOS as well as Windows.
Recommendations
- List Bash first or equally alongside Windows consoles when mentioning terminal options (e.g., 'in a console window such as Bash, cmd, or PowerShell').
- Explicitly state that all commands work on Linux/macOS and Windows.
- Consider mentioning alternative editors (e.g., Vim, nano, Sublime Text) for users who may not use Visual Studio Code.
- Add a note that the 'code .' command requires Visual Studio Code and may need to be installed separately on Linux/macOS.
Storage
Tutorial: Work with Azure Queue Storage queues in .NET
...ain/articles/storage/queues/storage-tutorial-queues.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Summary
The documentation page exhibits a mild Windows bias, primarily in its use of Windows-centric terminology and examples. Console instructions reference 'cmd' and 'PowerShell' before mentioning Azure CLI, and all example output uses Windows-style paths (e.g., C:\Tutorials). There are no explicit Linux/macOS examples, nor are Linux-specific shell environments (bash, zsh) mentioned. However, the actual commands (dotnet CLI) are cross-platform, and there are no steps that Linux/macOS users cannot complete.
Recommendations
- Explicitly mention Linux/macOS terminal environments (e.g., bash, zsh, Terminal.app) alongside Windows tools.
- Provide example output using Linux/macOS path formats (e.g., /home/user/Tutorials) in addition to Windows examples.
- Clarify that all dotnet CLI commands work on Linux/macOS and Windows.
- Avoid listing Windows tools (cmd, PowerShell) first; use neutral phrasing such as 'in a terminal window (e.g., cmd, PowerShell, bash, zsh)'.
- Add a note or section for Linux/macOS users, highlighting any minor differences (e.g., file paths, environment variables).
Storage
Introduction to Azure Queue Storage
...articles/storage/queues/storage-queues-introduction.md
Low Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page exhibits minor Windows bias in its 'Next steps' section, where quickstart links for .NET, Java, Python, and Node.js reference tabs or environment variable instructions specifically for Windows (e.g., 'environment-variable-windows'), without mention of Linux/macOS equivalents. There are no explicit Linux/macOS examples or instructions, and Windows terminology appears first or exclusively in tab names.
Recommendations
- Add environment variable instructions for Linux/macOS alongside Windows in quickstart guides.
- Ensure tab names and examples cover both Windows and Linux/macOS platforms equally.
- Explicitly mention cross-platform compatibility in introductory sections.
- Provide links or references to Linux/macOS setup guides where relevant.
Storage
Migrate your block data to Azure with Cirrus Data
...artners/data-management/cirrus-data-migration-guide.md
Low Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page exhibits mild Windows bias by linking to Windows-specific Azure VM creation guides and referencing Windows documentation first in 'Next steps.' While the migration example uses a Linux source host and Linux commands (e.g., iostat), there are no explicit Windows or PowerShell examples, nor are Windows tools or patterns described. However, Linux parity could be improved by including Linux-specific quick start links and examples for both platforms.
Recommendations
- Provide links to both Windows and Linux Azure VM quick start guides in the implementation section.
- Include explicit examples or notes for migrating from Windows hosts, such as relevant commands or disk management steps.
- Balance 'Next steps' links to include both Windows and Linux Azure VM documentation.
- Clarify that the migration process supports both Windows and Linux hosts, and provide platform-specific guidance where needed.
Storage
Get started with Storage Explorer
...ttps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/storage-explorer/vs-azure-tools-storage-manage-with-storage-explorer.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Summary
The documentation is generally cross-platform and provides installation and usage instructions for Windows, macOS, and multiple Linux distributions. However, there is a subtle Windows bias: Windows is listed first in prerequisites, and the legacy Azure Storage Emulator is mentioned as a supported emulator (Windows only) before Azurite, which is cross-platform. There are no explicit Linux/macOS command-line examples for tasks like connecting to storage accounts, and no mention of Linux-specific troubleshooting or parity for features like password manager integration beyond Ubuntu, RHEL, and SLES. No PowerShell examples are present, but the overall structure and tool mentions favor Windows.
Recommendations
- List operating systems in alphabetical order or rotate the order to avoid Windows-first bias.
- Emphasize Azurite as the recommended emulator for all platforms, and clearly mark Azure Storage Emulator as legacy/Windows-only.
- Provide Linux/macOS-specific command-line examples or troubleshooting steps where appropriate.
- Expand password manager integration instructions for other Linux distributions and macOS.
- Add parity checks for features and troubleshooting across all platforms.
Storage
Performance and scalability checklist for Table storage
...ticles/storage/tables/storage-performance-checklist.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation shows mild Windows bias, primarily through references to Windows-specific tools (WireShark, NetMon), and by mentioning PowerShell before Azure CLI when discussing client tools. The .NET configuration section is Windows-centric, focusing on .NET Framework and ServicePointManager, which are most relevant to Windows environments. There are no explicit Linux/macOS examples or tool recommendations, and troubleshooting guidance is oriented toward Windows users.
Recommendations
- Include Linux/macOS equivalents for network troubleshooting tools (e.g., tcpdump, iftop, nload) alongside WireShark and NetMon.
- When listing client libraries and tools, mention Azure CLI before or alongside PowerShell, and highlight cross-platform support.
- Add examples or notes for configuring connection limits and thread pools in popular Linux/macOS languages/environments (e.g., Python, Java, Node.js).
- Clarify that .NET Core is cross-platform and provide guidance for Linux/macOS users where relevant.
- Ensure that any code/configuration snippets are accompanied by platform-agnostic or Linux/macOS-specific alternatives where possible.
Storage
Apply an Azure Resource Manager lock to a storage account
.../main/articles/storage/common/lock-account-resource.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides step-by-step instructions for applying an Azure Resource Manager lock via the Azure portal, PowerShell, and Azure CLI. The PowerShell example is given before the Azure CLI example, and there is explicit mention of the Az PowerShell module, which is primarily a Windows tool. No Linux/macOS-specific shell examples (e.g., Bash) or guidance are provided, and the CLI example is not shown first.
Recommendations
- Present Azure CLI examples before PowerShell, as CLI is cross-platform and more widely used on Linux/macOS.
- Explicitly mention that Azure CLI works on Linux/macOS and provide installation links.
- Add Bash script examples for common scenarios.
- Clarify that PowerShell Core is available cross-platform, or link to instructions for using PowerShell on Linux/macOS if PowerShell examples are retained.
- Include notes about platform compatibility for each tool.
Storage
Choose an Azure solution for data transfer
...torage/common/storage-choose-data-transfer-solution.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation page shows mild Windows bias by listing PowerShell examples before Azure CLI examples in the 'Next steps' section and mentioning Azure PowerShell as a scriptable tool alongside AzCopy and Azure CLI. However, Linux tools and cross-platform options like Azure CLI and SDKs are also referenced, and no critical functionality is locked to Windows-only tools.
Recommendations
- List Azure CLI examples before PowerShell examples, or present them together to avoid implying preference.
- Explicitly mention Linux/macOS compatibility for tools like AzCopy and Azure CLI.
- Include links to Linux/macOS-specific quickstarts or documentation where available.
- Clarify that Azure PowerShell is available cross-platform, or highlight CLI as the most OS-agnostic option.
Storage
Transfer data to or from Azure Files by using AzCopy v10
...in/articles/storage/common/storage-use-azcopy-files.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Path Examples
Windows Shell Notes
Summary
The documentation provides both Windows (SMB) and Linux (NFS) examples for all major operations with AzCopy, using tabbed sections to separate them. However, Windows-style paths (e.g., C:\myDirectory) and Windows Command Shell instructions are consistently presented first in each example and tip, with Linux paths following. There are frequent notes about quoting conventions for Windows Command Shell, which are always mentioned before Linux/macOS shell conventions. No Linux-specific tools or patterns are missing, and parity is maintained for all commands, but the ordering and emphasis favor Windows.
Recommendations
- Alternate the order of examples so that Linux/NFS examples are shown first in some sections.
- Add explicit macOS examples or notes where relevant, especially for quoting and path conventions.
- Provide a summary table at the top showing platform support for each scenario.
- Reduce repetition of Windows-first quoting instructions; consider a single cross-platform note.
- Use more neutral language in tips and notes, e.g., 'If you are using Windows Command Shell (cmd.exe)...' after describing the default for Linux/macOS.
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation presents Windows/Powershell instructions and scripts before Linux equivalents in the 'Disconnect volumes from clients' section. PowerShell examples are consistently shown first in all deletion operations, with Azure CLI (cross-platform) examples following. While Linux instructions and CLI examples are present, the ordering and emphasis favor Windows and PowerShell, which may create friction for Linux/macOS users.
Recommendations
- Alternate the order of examples, sometimes showing Azure CLI or Linux instructions first.
- Explicitly mention that Azure CLI is cross-platform and suitable for Linux/macOS users.
- Ensure parity in detail and clarity between Windows/Powershell and Linux/CLI instructions.
- Consider adding macOS-specific notes if relevant.
- Use neutral language (e.g., 'On Windows, use PowerShell; on Linux/macOS, use CLI') to avoid implying Windows is the default.
Storage
Quickstart: Azure Queue Storage client library for Java
...icles/storage/queues/storage-quickstart-queues-java.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation mentions Windows consoles (cmd, PowerShell) before Bash when describing how to create the project, but provides both PowerShell and Bash examples side-by-side. No Windows-specific tools or patterns are used, and Linux/Mac users are given equivalent instructions and code. The only minor bias is listing Windows consoles first.
Recommendations
- List Bash (Linux/macOS) and PowerShell (Windows) examples in parallel, or alternate which is shown first.
- Explicitly mention that all commands work on Linux/macOS as well as Windows.
- Add a note clarifying that the instructions are cross-platform and tested on Linux/macOS.
Storage
Introduction to Azure Queue Storage
...articles/storage/queues/storage-queues-introduction.md
Low Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates minor Windows bias, primarily in the 'Next steps' section. The quickstart links for .NET, Java, Python, and Node.js all specify tabs such as 'environment-variable-windows' and 'powershell', with no explicit mention of Linux/macOS equivalents or bash examples. This may create friction for non-Windows users seeking platform-specific guidance.
Recommendations
- Add explicit tabs or instructions for Linux/macOS environments (e.g., 'environment-variable-linux', 'bash', 'zsh') in all quickstart guides.
- Ensure examples and environment setup steps are provided for both Windows and Linux/macOS users, ideally side-by-side.
- Avoid using Windows-specific tools (like PowerShell) as the default or only example; include bash or cross-platform CLI alternatives.
- Review linked quickstart pages to confirm Linux/macOS parity and update navigation to highlight cross-platform support.
Storage
Best practices for monitoring Azure Blob Storage
...les/storage/blobs/blob-storage-monitoring-scenarios.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation page provides a PowerShell example for decoding a SAS token signature, with the Linux equivalent shown afterwards. The PowerShell example is presented first, indicating a subtle Windows-first bias. However, Linux users are not blocked from completing any tasks, as Linux-compatible commands are included. No other sections show exclusive use of Windows tools or patterns.
Recommendations
- Present Linux/macOS and Windows examples side-by-side, or alternate which is shown first.
- Explicitly mention cross-platform compatibility for all command-line examples.
- Where possible, use platform-neutral tools (e.g., Azure CLI, Python scripts) in examples.
- Add a note clarifying that all tasks can be performed on Linux/macOS as well as Windows.
Storage
Access control lists in Azure Data Lake Storage
...cles/storage/blobs/data-lake-storage-access-control.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation page demonstrates mild Windows bias, primarily in the ordering and emphasis of tools. Windows-centric tools (Azure Storage Explorer, PowerShell) are listed before cross-platform or Linux-native options (Azure CLI, REST API), and PowerShell is given its own section. There are no explicit Linux/macOS command-line examples or references to Linux file permission tools (e.g., getfacl/setfacl), and the documentation does not provide parity examples for Linux shell environments. However, Azure CLI and REST API options are included, which are cross-platform.
Recommendations
- Add explicit Linux/macOS shell examples for managing ACLs (e.g., using Azure CLI from bash/zsh, or referencing Linux tools for POSIX ACLs where appropriate).
- Reorder the 'How to set ACLs' table to list cross-platform tools (Azure CLI, REST API) before Windows-specific tools (PowerShell, Storage Explorer).
- Include a note or section on managing ACLs from Linux environments, possibly referencing integration with Linux file systems or Hadoop/HDFS tools.
- Ensure parity in example commands and screenshots for Linux/macOS users, not just Windows/PowerShell.
- Clarify that Azure CLI is available on Linux/macOS and provide sample commands in bash syntax.
Storage
Use Azure CLI to manage ACLs in Azure Data Lake Storage
...in/articles/storage/blobs/data-lake-storage-acl-cli.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation page generally presents cross-platform Azure CLI usage, but in the 'Ensure that you have the correct version of Azure CLI installed' section, it lists Windows PowerShell as the example local console before mentioning alternatives. There are no explicit Linux/macOS examples, nor are Linux-specific tools or shell patterns referenced. However, the CLI commands themselves are platform-agnostic and no critical steps are Windows-only.
Recommendations
- Explicitly mention Linux/macOS terminal options alongside Windows PowerShell when instructing users to open a command console.
- Add a note or example showing Azure CLI usage in a Linux/macOS shell (e.g., Bash, Terminal.app).
- Ensure screenshots and output examples do not imply Windows-only environments.
- Where possible, clarify that all CLI commands work identically on Linux/macOS and Windows.
Storage
Best practices for using Azure Data Lake Storage
...cles/storage/blobs/data-lake-storage-best-practices.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation demonstrates mild Windows bias by listing Windows-centric tools (PowerShell, Azure portal) before cross-platform or Linux-native equivalents (Azure CLI, REST, DistCp) in tool tables and examples. PowerShell is repeatedly referenced for ingestion, management, and monitoring tasks, often before CLI or REST. There are no Linux-only examples or explicit mention of Linux/macOS-specific workflows, but most tools listed are cross-platform. No critical functionality is locked to Windows-only tools.
Recommendations
- Present Azure CLI examples and references before or alongside PowerShell, especially in tables and step-by-step instructions.
- Explicitly mention that Azure CLI, AzCopy, and REST are fully supported on Linux/macOS, and provide links to platform-specific installation guides.
- Add example workflows or code snippets for Linux/macOS environments (e.g., Bash scripts, CLI usage) where PowerShell is currently shown.
- Highlight cross-platform tools (AzCopy, DistCp, Storage Explorer) in introductory sections to reinforce Linux parity.
- Where PowerShell is referenced, clarify its availability on Linux/macOS or suggest CLI alternatives.
Storage
Use Azure CLI to manage data (Azure Data Lake Storage)
...rage/blobs/data-lake-storage-directory-file-acl-cli.md
Low Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a mild Windows bias. In the 'Ensure that you have the correct version of Azure CLI installed' section, Windows PowerShell is mentioned as the example console application for running Azure CLI locally, with no mention of Linux/macOS terminals. Additionally, file path examples for upload and download operations use Windows-style paths (e.g., 'C:\myFolder\upload.txt') exclusively, without providing Linux/macOS equivalents. No Linux-specific tools or patterns are referenced, and examples do not show Linux/macOS usage.
Recommendations
- Explicitly mention Linux/macOS terminal applications (e.g., bash, Terminal.app) alongside Windows PowerShell when instructing users to open a command console.
- Provide file path examples using both Windows and Linux/macOS formats (e.g., 'C:\myFolder\upload.txt' and '/home/user/upload.txt') for upload/download commands.
- Add a note clarifying that Azure CLI commands work identically on Linux/macOS, and adjust examples to show cross-platform compatibility.
- Consider including a table or toggle for platform-specific examples where file paths or shell conventions differ.
Storage
Encryption scopes for Blob storage
...in/articles/storage/blobs/encryption-scope-overview.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation page shows mild Windows bias in its references to Azure Key Vault recovery documentation. The PowerShell guide is listed before the CLI guide, and the examples use PowerShell terminology, which may be more familiar to Windows users. No Linux/macOS-specific tools or examples are provided, but the CLI link does offer some parity. The rest of the page is platform-neutral and does not rely on Windows-specific tools or patterns.
Recommendations
- List CLI and PowerShell documentation links in parallel or alternate their order to avoid Windows-first bias.
- Explicitly mention that Azure CLI is cross-platform and suitable for Linux/macOS users.
- Where PowerShell is referenced, also provide Bash/CLI equivalents or examples.
- Add a brief note clarifying that all described features are accessible from Linux/macOS using Azure CLI or REST API.
Storage
Known issues with NFS 3.0 in Azure Blob Storage
...age/blobs/network-file-system-protocol-known-issues.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation page is generally cross-platform, but there is minor Windows bias. The note about enabling static websites mentions PowerShell before Azure CLI, and the workaround for Windows NFS clients relies on WSL2 rather than native Windows support. No Linux examples are missing, and Linux tools are referenced appropriately for NFS operations.
Recommendations
- List Azure CLI before PowerShell when describing cross-platform configuration steps.
- Clarify that Azure CLI is available on both Windows and Linux, and provide example commands for both where relevant.
- Explicitly mention Linux/macOS support for NFS 3.0 clients, and provide example mount commands for those platforms.
- If possible, add a note about future plans for native Windows NFS client support.
Storage
Prevent object replication across Microsoft Entra tenants
...bs/object-replication-prevent-cross-tenant-policies.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides step-by-step instructions for preventing cross-tenant object replication in Azure Storage, offering examples for the Azure portal, PowerShell, and Azure CLI. In both the 'new account' and 'existing account' remediation sections, PowerShell examples are presented before Azure CLI, and the CLI examples use generic 'az' commands without explicit Linux/macOS context. There is a slight Windows bias in the ordering and emphasis on PowerShell, which is primarily a Windows tool, but Linux/macOS users can complete all tasks using Azure CLI or the portal.
Recommendations
- Alternate the order of PowerShell and Azure CLI examples, or present CLI examples first to better reflect cross-platform usage.
- Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and provide any OS-specific notes if needed.
- Consider including Bash shell script examples for common tasks to further support Linux/macOS users.
- Add a brief note clarifying that PowerShell is available cross-platform, but Azure CLI is often the preferred tool on Linux/macOS.
Storage
Quickstart: Azure Blob storage library v12 - JS Browser
...s/storage/blobs/quickstart-blobs-javascript-browser.md
Low Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation demonstrates a mild Windows bias in its developer environment setup instructions. Visual Studio Code is recommended as the editor, and the instructions for opening the project use the 'code .' command, which is available on all platforms but is most commonly associated with Windows. More notably, when instructing users to create a directory and run commands, the documentation refers to 'a console window (such as cmd, PowerShell, or Bash)', listing Windows shells first and not providing explicit Linux/macOS terminal examples or guidance. The rest of the documentation is platform-neutral, focusing on JavaScript and browser-based development.
Recommendations
- List Bash or Terminal (Linux/macOS) first or equally alongside cmd/PowerShell when referring to console windows.
- Explicitly mention that all commands work in Linux/macOS terminals and provide any necessary notes for those platforms.
- Include a brief note or example for installing Visual Studio Code and Node.js on Linux/macOS.
- Where relevant, provide alternative instructions for opening the project in editors on Linux/macOS (e.g., using 'code .' in a Linux terminal, or alternatives if not installed).
Storage
SSH File Transfer Protocol (SFTP) performance considerations in Azure Blob storage
...age/blobs/secure-file-transfer-protocol-performance.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation page demonstrates mild Windows bias by mentioning WinSCP (a Windows-centric SFTP client) first and providing a Windows OpenSSH example before the Linux equivalent. Windows tools and patterns are referenced before their Linux counterparts, though Linux examples are present.
Recommendations
- Present Linux and Windows examples side-by-side or alternate their order to avoid implicit prioritization.
- Include macOS-specific guidance or note parity with Linux commands where applicable.
- Mention cross-platform SFTP clients (e.g., FileZilla, Cyberduck) before or alongside WinSCP.
- Clarify that OpenSSH commands are applicable on macOS as well as Linux.
- Add explicit Linux/macOS configuration steps where relevant, not just Windows.