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 1551-1575 of 1657 flagged pages
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
Missing Linux Example
Summary
The documentation generally presents Windows information first and provides more detail for Windows prerequisites (e.g., .NET runtime requirements and installer behavior). The local storage emulator section lists the Windows-only Azure Storage Emulator before Azurite, which is cross-platform. There are no PowerShell-heavy examples or exclusive Windows command-line instructions, but some minor bias is present in the ordering and detail level. Linux installation instructions are present and reasonably detailed, but SLES support is noted as untested, and troubleshooting links sometimes point to Ubuntu pages even for other distros.
Recommendations
- Present OS sections in a neutral or rotating order (e.g., start with Linux or macOS sometimes).
- Provide equivalent detail for Linux/macOS prerequisites, including explicit dependency lists for .tar.gz installs.
- Clarify troubleshooting links for each Linux distro, not just Ubuntu.
- In the local storage emulator section, list Azurite (cross-platform) before the Windows-only Azure Storage Emulator and clarify emulator options for Linux/macOS.
- Add notes about .NET runtime requirements for Linux/macOS if applicable.
- Explicitly mention parity or differences in features between platforms where relevant.
Create Pull Request
Storage
Quickstart: Azure Queue Storage client library for Python
...les/storage/queues/storage-quickstart-queues-python.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation page generally maintains cross-platform parity, but in the 'Create the project' section, Windows shells (cmd, PowerShell) are mentioned before Bash, and there is a subtle preference for Windows-first terminology. No examples or instructions are Windows-only, and Linux/macOS users can follow all steps without friction.
Recommendations
- List Bash before cmd/PowerShell when mentioning consoles, or use 'such as Bash, cmd, or PowerShell' to avoid implicit prioritization.
- Explicitly state that all commands and instructions work on Linux/macOS as well as Windows.
- Add a note confirming cross-platform compatibility for all steps, especially for environment variable setup and running Python scripts.
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 provides a PowerShell example for decoding SAS token signatures and mentions using 'any tool or SDK' for hashing, but only gives a detailed PowerShell command before mentioning Linux alternatives. The Linux example is present but appears after the PowerShell example, indicating a slight Windows-first bias. No exclusive use of Windows tools or missing Linux examples are found, but the ordering and emphasis favor Windows users.
Recommendations
- Present Linux/macOS and Windows examples side-by-side or in parallel sections, rather than listing Windows/PowerShell first.
- Provide Bash or Python examples with equal detail and prominence as PowerShell.
- Explicitly mention cross-platform tools (e.g., openssl, sha256sum, Python) before platform-specific ones.
- Add a note clarifying that all steps can be performed on Linux/macOS and Windows, with equivalent commands.
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 mentions Windows PowerShell as the example local command console application before any Linux or macOS alternatives, and does not explicitly mention Linux/macOS terminals. All command examples are cross-platform Azure CLI, but the introductory instructions subtly prioritize Windows environments.
Recommendations
- Explicitly mention Linux/macOS terminal applications (e.g., Bash, Terminal.app, GNOME Terminal) alongside Windows PowerShell when referring to local CLI usage.
- Add a note clarifying that Azure CLI commands work identically on Windows, Linux, and macOS.
- Where screenshots or output are shown, consider including examples from non-Windows terminals if relevant.
- Avoid listing Windows tools or shells first unless there is a technical reason.
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
Summary
The documentation page demonstrates mild Windows bias by listing Azure PowerShell before Azure CLI in several tool tables and mentioning PowerShell as a primary method for tasks like ingesting and downloading data. However, Linux/macOS equivalents (Azure CLI, REST, SDKs, AzCopy, DistCp) are also included, and no critical functionality is Windows-only.
Recommendations
- Present Azure CLI examples and references before or alongside PowerShell to avoid Windows-first ordering.
- Explicitly mention cross-platform compatibility for tools like AzCopy, Azure CLI, and Storage Explorer.
- Add example commands for both PowerShell and Azure CLI where possible.
- Include notes or links for Linux/macOS installation and usage for key tools.
- Avoid implying PowerShell is the default or preferred method for tasks that can be done equally well with CLI or REST.
Storage
Known issues with Azure Data Lake Storage
...ticles/storage/blobs/data-lake-storage-known-issues.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation page demonstrates mild Windows bias by referencing PowerShell and Windows-specific tools (e.g., WASB driver) and listing PowerShell before Azure CLI in some sections. However, Linux/macOS alternatives (Azure CLI, ABFS driver) are mentioned, and most guidance is cross-platform. No critical tasks are Windows-only, but some examples and tool recommendations could be more balanced.
Recommendations
- Provide explicit Linux/macOS examples alongside PowerShell, especially for tasks like restoring soft-deleted blobs.
- Clarify cross-platform compatibility for tools like AzCopy and Azure Storage Explorer.
- List Azure CLI before PowerShell or present both equally when describing management tasks.
- Add notes or links for Linux/macOS users where Windows-specific drivers/tools (e.g., WASB) are mentioned.
- Ensure all SDK and CLI instructions are platform-neutral or include platform-specific notes.
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 exhibits mild Windows bias in the section about Azure Key Vault recovery, where PowerShell is mentioned before CLI, and the link text for PowerShell is more prominent. No Linux/macOS-specific tools or examples are provided, and the CLI is only referenced as an alternative. The rest of the page is platform-neutral and does not reference Windows-specific tools or workflows.
Recommendations
- Present CLI and PowerShell options together, or list CLI first to avoid implicit prioritization of Windows tools.
- Explicitly mention that both CLI and PowerShell are cross-platform, and provide parity in example coverage.
- Add Bash or Linux/macOS-specific instructions or notes where relevant, especially in sections involving command-line operations.
Storage
Version-level WORM policies for immutable blob data
...storage/blobs/immutable-version-level-worm-policies.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Windows First
Summary
The documentation page exhibits mild Windows bias, primarily in the 'Deletion' section, where PowerShell commands (Remove-AzRmStorageContainer, Remove-AzStorageContainer) are mentioned first and in detail, with explicit references to their behavior. While Azure CLI commands are also referenced, the PowerShell examples and terminology are presented before CLI equivalents, and no Linux/macOS shell examples (e.g., Bash, scripting) are provided. The documentation does not mention platform-specific differences or provide parity for Linux/macOS users in command-line examples.
Recommendations
- Provide Bash or shell script examples for Linux/macOS users alongside PowerShell commands.
- Clearly state that Azure CLI is cross-platform and highlight its usage for Linux/macOS users.
- List Azure CLI commands before PowerShell commands, or present both together in parallel.
- Add notes about platform compatibility for all command-line tools mentioned.
- Avoid assuming PowerShell as the default scripting environment.
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 demonstrates a mild Windows bias by referencing Windows PowerShell as the example local console and using Windows-style file paths (e.g., C:\myFolder\upload.txt) in upload/download commands. There are no explicit Linux/macOS shell references or examples using Unix-style paths, which may cause minor confusion or friction for non-Windows users.
Recommendations
- Explicitly mention Linux/macOS terminals (e.g., Bash, Terminal) alongside Windows PowerShell when describing how to open a command console.
- Provide parallel examples using Unix-style file paths (e.g., /home/user/upload.txt) for upload/download commands.
- Add a note clarifying that file path syntax should match the user's operating system.
- Consider alternating the order of examples or providing OS-specific tabs for commands involving local file paths.
Storage
Using the HDFS CLI with Azure Data Lake Storage
.../blobs/data-lake-storage-use-hdfs-data-lake-storage.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation page exhibits mild Windows bias by providing a sample PowerShell code block for SSH connection, even though the context is Linux HDInsight clusters. The SSH example is presented in PowerShell syntax, which is native to Windows, rather than Bash or a generic terminal command. However, all subsequent HDFS CLI commands are platform-agnostic and do not favor Windows tools or patterns.
Recommendations
- Replace the PowerShell SSH example with a Bash or generic terminal command, or provide both PowerShell and Bash examples side-by-side.
- Clarify that SSH commands can be run from any OS terminal, not just PowerShell.
- Add explicit instructions or examples for Linux/macOS users where relevant, especially in connection steps.
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 page demonstrates a slight Windows bias by listing Windows tools (cmd, PowerShell) before Bash when referencing console windows, and by recommending Visual Studio Code as the editor without mentioning Linux/macOS alternatives. All command-line instructions (mkdir, cd, npm, code .) are cross-platform, but there are no explicit Linux/macOS-specific instructions or clarifications. The Azure portal instructions are platform-agnostic, but the lack of explicit Linux parity in setup steps may create minor friction for non-Windows users.
Recommendations
- Explicitly mention Bash and terminal usage for Linux/macOS users alongside cmd/PowerShell.
- Clarify that Visual Studio Code is available on Linux/macOS, or suggest alternative editors (e.g., Vim, Atom, Sublime Text).
- Add notes or examples for installing Node.js and npm on Linux/macOS using package managers (e.g., apt, yum, brew).
- Include a brief section or callout confirming all CLI commands work on Linux/macOS, or provide platform-specific instructions where needed.
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 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 Linux ones, though Linux examples are present and parity is reasonable.
Recommendations
- Present Linux and Windows examples side-by-side or alternate which platform is shown first.
- Include explicit mentions of popular Linux/macOS SFTP clients (e.g., lftp, Nautilus, Cyberduck) alongside WinSCP and FileZilla.
- Clarify configuration steps for both platforms where applicable, not just for WinSCP (Windows).
- Add more Linux/macOS-specific tips or caveats if relevant.
Storage
Host keys for SFTP support for Azure Blob Storage
...orage/blobs/secure-file-transfer-protocol-host-keys.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation provides both cross-platform and Windows-specific guidance, but there is a mild Windows bias. Windows-specific tools (WinSCP, registry key storage) are mentioned explicitly and given their own example, while Linux/macOS equivalents (OpenSSH, ~/.ssh/known_hosts) are described in a more generic way. Windows registry storage is called out as a separate bullet, and Windows file paths are shown in warning messages before Linux equivalents. The order of presentation sometimes puts Windows-specific content before Linux/macOS, and Windows file paths are shown in error messages.
Recommendations
- Add explicit Linux/macOS client examples (e.g., FileZilla, Cyberduck) and their trusted host storage mechanisms.
- When showing file paths in error messages, show Linux/macOS paths first or side-by-side with Windows paths.
- Include a note or table summarizing how host key storage works on major platforms (Windows, Linux, macOS) and popular clients.
- Ensure that cross-platform instructions are presented before or alongside Windows-specific instructions.
- Provide more code or CLI examples for Linux/macOS (e.g., using ssh-keygen, ssh-add, or editing ~/.ssh/known_hosts).
Storage
Enable or disable SFTP support in Azure Blob Storage
.../blobs/secure-file-transfer-protocol-support-how-to.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides both PowerShell and Azure CLI examples for enabling/disabling SFTP support, but PowerShell (a Windows-centric tool) is presented before Azure CLI in each section. There are no Linux-specific tools or shell examples (e.g., Bash), and PowerShell is given equal prominence to Azure CLI, which is cross-platform. No explicit Windows-only tools are used, but the ordering and emphasis may subtly favor Windows users.
Recommendations
- Present Azure CLI examples before PowerShell, as Azure CLI is cross-platform and more commonly used on Linux/macOS.
- Explicitly mention that Azure CLI commands work on Linux/macOS and Windows.
- Consider adding Bash shell script examples or notes for Linux users where relevant.
- Clarify that PowerShell Core is available cross-platform, if relevant, or link to installation instructions for non-Windows platforms.
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation shows a mild Windows bias: PowerShell is featured as a primary automation example, and instructions for using the Azure CLI locally mention Windows PowerShell as the default console application. PowerShell examples are given before Azure CLI in both main and hierarchical namespace sections. There are no explicit Linux/macOS examples or references to Bash or other non-Windows shells, and the CLI instructions do not clarify cross-platform usage.
Recommendations
- Explicitly mention that Azure CLI commands work on Linux/macOS and can be run from Bash or other shells.
- Provide example commands using Bash or zsh, especially for CLI usage.
- Avoid referring to 'Windows PowerShell' as the default console; instead, use 'command-line terminal' or mention multiple OS options.
- Ensure parity in ordering: alternate the order of PowerShell and CLI examples, or present CLI first for cross-platform relevance.
- Add notes or links for installing and running Azure CLI on Linux/macOS.
Storage
SFTP support for Azure Blob Storage
...storage/blobs/secure-file-transfer-protocol-support.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation demonstrates a mild Windows bias. SFTP command examples are shown using PowerShell syntax, and the only explicit SFTP usage example references OpenSSH on Windows. There are no Linux/macOS-specific command examples or references to Linux tools, even though SFTP is widely used on those platforms. The SSH key management section links to a Windows-specific SSH guide, and Windows tools (PowerShell, OpenSSH for Windows) are mentioned before or instead of Linux equivalents.
Recommendations
- Add SFTP command examples using standard Linux/macOS shell syntax (e.g., bash) alongside PowerShell examples.
- Reference Linux/macOS SSH key management guides in addition to or instead of Windows-specific guides.
- Explicitly mention that SFTP works on Linux/macOS and provide examples using native tools (e.g., sftp, ssh-keygen).
- Ensure that client lists and instructions do not prioritize Windows tools or environments.
- Clarify that the instructions and examples are platform-agnostic unless a platform-specific step is required.
Storage
Reacting to Azure Blob storage events
.../articles/storage/blobs/storage-blob-event-overview.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation lists PowerShell (Windows-centric) as a primary tool for quickstart examples and mentions it before Azure CLI, which is cross-platform. While Azure CLI is also included, the ordering and explicit mention of PowerShell may subtly prioritize Windows users. No Linux/macOS-specific tools or examples are missing, but the presentation order and emphasis could create minor friction for non-Windows users.
Recommendations
- List Azure CLI before PowerShell in quickstart tables and sections, as CLI is cross-platform.
- Explicitly mention that Azure CLI works on Linux/macOS and provide links to installation guides for those platforms.
- Ensure parity in example depth and clarity between PowerShell and Azure CLI quickstarts.
- Consider adding a note that PowerShell Core is available cross-platform, if relevant, or clarify platform applicability.
Storage
Map a custom domain to an Azure Blob Storage endpoint
...n/articles/storage/blobs/storage-custom-domain-name.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation demonstrates a mild Windows bias by consistently listing PowerShell examples before Azure CLI examples in command sections. PowerShell is a Windows-centric tool, while Azure CLI is cross-platform. Additionally, some instructions refer to 'PowerShell command' even in the Azure CLI tab, which may confuse Linux/macOS users. However, Azure CLI examples are present throughout, and no critical steps are Windows-only.
Recommendations
- List Azure CLI examples before PowerShell examples to prioritize cross-platform usage.
- Use neutral language such as 'Run the following command' instead of 'Run the following PowerShell command' in Azure CLI sections.
- Explicitly mention that Azure CLI works on Linux/macOS and provide links to installation guides for non-Windows platforms.
- Consider adding bash script examples or references for Linux users where appropriate.
Storage
Quickstart: Azure Blob Storage library - .NET
...icles/storage/blobs/storage-quickstart-blobs-dotnet.md
Low Priority
View Details →
Detected Bias Types
Windows First
Visual Studio Heavy
Summary
The documentation provides both Visual Studio (Windows-centric) and .NET CLI instructions, but Visual Studio steps are consistently listed first and described in more detail, with screenshots. There is a slight bias toward Windows tools and workflows, though Linux/macOS users can follow the .NET CLI instructions. No explicit PowerShell-only or Windows-only commands are present, and Bash is mentioned as a valid shell. However, Visual Studio is emphasized as the primary IDE, and Linux/macOS equivalents (e.g., JetBrains Rider, VS Code) are not discussed.
Recommendations
- Alternate the order of Visual Studio and .NET CLI instructions, or present .NET CLI first to avoid Windows-first perception.
- Include explicit instructions and screenshots for VS Code or other cross-platform editors, especially for Linux/macOS users.
- Clarify that all .NET CLI commands work on Linux/macOS and provide any necessary notes for platform-specific differences.
- Mention and link to Linux/macOS installation guides for .NET SDK and Azure Developer CLI.
- Add troubleshooting tips for common Linux/macOS issues (e.g., file permissions, path separators) if relevant.
Storage
Quickstart: Azure Blob storage library - TypeScript
...ge/blobs/storage-quickstart-blobs-nodejs-typescript.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation exhibits mild Windows bias in several areas: Windows tools (cmd, PowerShell, Visual Studio Code) are mentioned first or exclusively in setup and authentication steps. PowerShell is given its own sign-in instructions, while Linux equivalents are less emphasized. The instructions for setting environment variables show Windows first, and Visual Studio Code is referenced as the default editor, which is more common on Windows. However, Linux commands and alternatives are present, and most code examples are platform-agnostic.
Recommendations
- Present Linux and macOS instructions before or alongside Windows instructions, not after.
- Include explicit Bash and terminal examples for authentication (e.g., az login) and environment variable setup.
- Mention cross-platform editors (e.g., VS Code, Vim, nano) or avoid assuming a specific editor.
- Add PowerShell and Bash instructions side-by-side for parity.
- Clarify that all steps can be performed on Linux/macOS, and link to platform-specific guides if available.
Storage
Quickstart: Azure Blob storage library - JavaScript
...icles/storage/blobs/storage-quickstart-blobs-nodejs.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page exhibits mild Windows bias. Windows tools (cmd, PowerShell) are mentioned before Linux equivalents in several places, and authentication instructions include PowerShell and Azure CLI, but do not mention Bash or Linux-specific sign-in flows. The 'Open the project in Visual Studio Code' step assumes the 'code' command is available, which is more common on Windows. The environment variable setup provides both Windows (setx) and Linux (export) instructions, but Windows is listed first. There are no explicit Linux-only examples or troubleshooting tips, and some steps (e.g., using Visual Studio Code) may be less familiar to Linux/macOS users. However, most commands are cross-platform and Linux users can complete the quickstart with minor adaptation.
Recommendations
- Present Linux/macOS examples before or alongside Windows examples, especially for environment variable setup and authentication.
- Include Bash-specific sign-in instructions (e.g., Azure CLI in Bash) and clarify that all commands work in Bash/Terminal on Linux/macOS.
- Mention alternative editors (e.g., nano, vim) for opening files, or clarify that 'code .' is optional.
- Add troubleshooting notes for common Linux/macOS issues (e.g., permissions, installing VS Code CLI tools).
- Explicitly state that all steps are cross-platform unless noted, and link to platform-specific guides where appropriate.
Storage
Quickstart: Deploy a static website on Azure Storage using Terraform
...e/blobs/storage-quickstart-static-website-terraform.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for verifying results, but PowerShell is given equal prominence and is presented immediately after CLI, without explicit Linux/macOS shell examples (e.g., Bash). There are no Linux-specific instructions or screenshots, and no mention of platform differences in command usage. The use of PowerShell may imply a Windows-centric approach, especially since Bash or other Linux-native shells are not referenced.
Recommendations
- Add explicit Bash/Linux shell examples alongside Azure CLI and PowerShell, especially for variable assignment and command usage.
- Clarify that Azure CLI commands can be run on Linux, macOS, and Windows, and provide platform-specific notes if needed.
- Include screenshots or instructions that demonstrate usage on Linux/macOS terminals.
- If PowerShell is included, note its cross-platform availability, but also show native shell alternatives for Linux/macOS users.
Storage
Performance checklist for Azure Blob Storage
...rticles/storage/blobs/storage-performance-checklist.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation page references tools like AzCopy and network monitoring utilities (WireShark, NetMon) without specifying platform parity or providing Linux/macOS alternatives. NetMon is a Windows-only tool, and AzCopy examples are referenced but not shown; there is no mention of Linux/macOS usage or equivalent commands. No explicit PowerShell bias is present, but the mention of NetMon and lack of Linux-specific guidance suggest a mild Windows bias.
Recommendations
- Explicitly mention that AzCopy is cross-platform and provide example usage for Linux/macOS (e.g., installation and command-line examples).
- Replace or supplement NetMon with Linux/macOS network monitoring tools such as tcpdump or iftop.
- Where tools are referenced, clarify platform compatibility and provide links or instructions for all major operating systems.
- Consider listing Linux/macOS tools alongside Windows tools, rather than only mentioning Windows-specific utilities.
Storage
Quickstart: Azure Blob Storage library - Java
...rticles/storage/blobs/storage-quickstart-blobs-java.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation page demonstrates mild Windows bias. Windows and PowerShell are frequently mentioned first or exclusively in several places, such as console output examples, environment variable setup, and authentication instructions. PowerShell and Windows command-line tools are often presented before their Linux equivalents, and Windows file paths appear in sample outputs. However, Linux/Bash alternatives are generally provided, and most instructions are cross-platform.
Recommendations
- Present Linux/Bash examples before or alongside Windows/PowerShell examples, especially in code tabs and environment variable setup.
- Use neutral file paths (e.g., ./blob-quickstart) in sample outputs, or provide both Windows and Linux paths.
- Ensure authentication instructions (e.g., Azure CLI, PowerShell) are equally detailed for Linux/macOS and Windows.
- Explicitly mention macOS where Linux is referenced, or provide macOS-specific notes if needed.
- Audit all sections for subtle Windows-first language or ordering and revise for parity.
Storage
Upgrading Azure Blob Storage to Azure Data Lake Storage
...les/storage/blobs/upgrade-to-data-lake-storage-gen2.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page shows mild Windows bias by referencing Windows-specific tools (e.g., WASB driver) and mentioning PowerShell commands before Linux equivalents, though it does also reference Azure CLI and SDKs. There are no explicit Linux/macOS examples or tool recommendations, and Windows terminology (e.g., 'Windows Azure Storage Blob driver') is used without Linux alternatives being equally highlighted.
Recommendations
- Explicitly mention Linux/macOS compatibility for all tools and commands.
- Provide Linux/macOS examples alongside PowerShell, especially for command-line operations.
- Reference cross-platform tools (e.g., Azure CLI, AzCopy) before or alongside Windows-specific tools.
- Include guidance for Linux users migrating from WASB to ABFS, and clarify that ABFS works across platforms.
- Avoid using 'Windows-first' terminology when describing drivers or endpoints; use platform-neutral language.