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 1626-1650 of 1657 flagged pages
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/encryption-scope-overview.md
...in/articles/storage/blobs/encryption-scope-overview.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation page is generally platform-neutral, but in the section on Azure Key Vault soft-delete, the PowerShell example is mentioned before the CLI example. This ordering subtly prioritizes Windows tooling, as PowerShell is more closely associated with Windows environments, while the Azure CLI is cross-platform and more commonly used on Linux and macOS.
Recommendations
- When listing platform-specific tools or examples, alternate the order in which they are presented (e.g., mention CLI before PowerShell in some places, especially in cross-platform documentation).
- Explicitly state that both PowerShell and CLI are supported, and provide parity in examples and references.
- Where possible, provide code snippets or links for both PowerShell and CLI together, or use the Azure CLI as the primary example since it is cross-platform.
- Consider adding a note clarifying that both Windows and Linux users are supported equally, and link to relevant documentation for both platforms.
Create Pull Request
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/snapshots-manage-dotnet.md
...main/articles/storage/blobs/snapshots-manage-dotnet.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation page exclusively provides .NET (C#) code samples and instructions without any reference to platform-specific tools or shell environments. However, it does not provide any command-line examples (such as PowerShell, Windows CMD, Bash, or Linux CLI), nor does it mention any platform-specific tools. The content is neutral in terms of Windows vs. Linux, but it lacks parity for users who might want to perform these operations using cross-platform command-line tools or scripts (e.g., Azure CLI, Bash).
Recommendations
- Add equivalent examples using Azure CLI commands for creating, managing, and deleting blob snapshots. Azure CLI is cross-platform and works on both Windows and Linux.
- If referencing command-line operations, ensure both PowerShell (Windows) and Bash (Linux/macOS) examples are provided, or use Azure CLI syntax which is consistent across platforms.
- Explicitly mention that the .NET code samples are platform-agnostic and can be run on Windows, Linux, or macOS, provided the .NET SDK is installed.
- Provide links or references to documentation for performing the same tasks using other languages or tools (e.g., Azure CLI, REST API, Python SDK) to improve accessibility for non-Windows and non-.NET users.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/storage-blob-delete.md
...lob/main/articles/storage/blobs/storage-blob-delete.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation is focused exclusively on .NET and C# code examples, with no mention of platform-specific tools or shell environments (such as Windows PowerShell or Linux Bash). However, it does not provide any Linux-specific examples or guidance, nor does it address cross-platform usage scenarios (e.g., running .NET code on Linux or Mac). The lack of Linux- or cross-platform-specific instructions or considerations may make the documentation less accessible to developers working outside of Windows environments.
Recommendations
- Explicitly mention that the .NET client library and code samples can be used on Linux and macOS as well as Windows.
- Provide setup instructions or notes for .NET development on Linux (e.g., using the .NET SDK on Ubuntu, installing dependencies, running code from the terminal).
- Include example commands for running the code on Linux/macOS terminals (e.g., using 'dotnet run' in Bash).
- If there are any platform-specific considerations (such as file paths, authentication methods, or environment variables), document these for Linux/macOS users.
- Consider linking to cross-platform .NET documentation or guides for Linux/macOS developers.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/elastic-san/elastic-san-encryption-overview.md
...storage/elastic-san/elastic-san-encryption-overview.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Summary
The documentation references the 'Cryptography API: Next Generation' (CNG), which is a Windows-specific cryptographic module, as the source for more information about Azure data encryption. No equivalent Linux or cross-platform cryptographic modules or standards are mentioned. There are no command-line examples, so there is no bias in example commands, but the reference to Windows cryptography tools is a subtle form of Windows bias.
Recommendations
- When referencing cryptographic modules or APIs, include cross-platform or Linux-relevant standards (e.g., OpenSSL, Linux kernel crypto modules) alongside Windows-specific ones.
- Provide links or references to general cryptographic standards (such as FIPS 140-2, NIST publications) that are not tied to a specific operating system.
- If mentioning Windows-specific tools or APIs, add a note or section about equivalent Linux or open-source cryptographic libraries and how they relate to Azure's encryption implementation.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/storage-use-azcopy-blobs-properties-metadata.md
...common/storage-use-azcopy-blobs-properties-metadata.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides AzCopy command-line examples that are cross-platform, but in every section where shell quoting is discussed, it refers to Windows Command Shell (cmd.exe) first and Linux/Unix shells second. The guidance is phrased as 'use single quotes except for Windows Command Shell (cmd.exe), use double quotes,' which subtly centers Windows as the primary or default environment. No PowerShell-specific or Windows-only tools are used, and Linux/Unix usage is acknowledged, but always as the alternative.
Recommendations
- Rephrase quoting guidance to be neutral or Linux-first, e.g., 'Use single quotes in Bash or other Unix shells. In Windows Command Shell (cmd.exe), use double quotes.'
- Add explicit mention of PowerShell if relevant, or clarify quoting rules for PowerShell, as it differs from both Bash and cmd.exe.
- Consider providing examples with both single and double quotes side by side, labeled for each shell, to make Linux/Unix users feel equally supported.
- Where possible, avoid phrasing that positions Windows as the default or primary environment.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/elastic-san/elastic-san-connect-aks.md
...rticles/storage/elastic-san/elastic-san-connect-aks.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation lists both Azure PowerShell and Azure CLI as options for obtaining volume information, but PowerShell is mentioned first in both the prerequisites and the example commands. No exclusive Windows tools or patterns are present, and all other instructions use cross-platform tools (kubectl, bash, yaml). There are no missing Linux examples, but the ordering gives slight preference to Windows/PowerShell.
Recommendations
- List Azure CLI before Azure PowerShell in prerequisites and example commands, as Azure CLI is cross-platform and more commonly used on Linux.
- Explicitly note that both Azure CLI and PowerShell are supported on Windows, Linux, and macOS to avoid implying PowerShell is Windows-only.
- Where possible, provide examples for both tools side-by-side or clarify that either can be used, with CLI first.
- Consider including a short note about installing and using Azure CLI on Linux, if relevant.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/storage-solution-periodic-data-transfer.md
...rage/common/storage-solution-periodic-data-transfer.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation does not display overt Windows bias in terms of mentioning Windows-specific tools, PowerShell, or Windows-first patterns. However, it lacks explicit examples or guidance for Linux users, such as Linux command-line usage, shell scripting, or references to Linux environments. The tools mentioned (AzCopy, REST APIs, Data Factory, Data Box) are cross-platform, but the absence of Linux-specific instructions or examples may leave Linux users underserved.
Recommendations
- Add explicit examples or references for using AzCopy and other tools on Linux (e.g., bash command-line usage, installation instructions for Linux).
- Include notes or sections clarifying cross-platform compatibility for each tool.
- Provide sample scripts or automation patterns for both Windows (PowerShell) and Linux (bash/shell).
- Mention any Linux-specific considerations or troubleshooting tips where relevant.
- Ensure parity in documentation structure by presenting Linux and Windows usage equally, or in parallel, where applicable.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/container-storage/volume-snapshot-restore.md
...s/storage/container-storage/volume-snapshot-restore.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation demonstrates a mild 'windows_first' bias by suggesting the use of the 'code' command to create YAML files (which is most commonly associated with Visual Studio Code on Windows) and by mentioning 'administrative privileges' for running commands locally, a concept more prominent in Windows environments. However, all command-line examples use cross-platform tools (kubectl, Azure CLI), and there are no PowerShell-specific or Windows-only commands. There are no Linux-specific instructions or examples, and Linux tools/editors are not mentioned.
Recommendations
- Explicitly mention that all CLI commands work on Linux, macOS, and Windows.
- When suggesting to create/edit files, recommend cross-platform editors (e.g., 'nano', 'vim', 'vi', or 'code') or use neutral language like 'use your preferred text editor'.
- Clarify that 'administrative privileges' may mean 'sudo' on Linux/macOS and 'Run as Administrator' on Windows.
- Add a note or section confirming that the instructions are valid for Linux, macOS, and Windows, and provide any OS-specific caveats if necessary.
- Where relevant, provide examples of common Linux workflows (e.g., using 'touch' and 'nano' to create/edit files).
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/storage-use-azcopy-optimize.md
...articles/storage/common/storage-use-azcopy-optimize.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation generally presents cross-platform information, but in the few places where OS-specific instructions are given (such as setting environment variables), Windows is listed first. There is a minor bias in the ordering of instructions, but Linux and macOS equivalents are always provided. The only other OS-specific note is a tip about quoting in shells, which does mention Windows separately but does not omit Linux guidance.
Recommendations
- Alternate the order of operating systems in tables and instructions, or list Linux/macOS first in some sections to avoid always privileging Windows.
- Where OS-specific instructions are given, ensure that Linux and macOS are not always listed after Windows.
- Consider adding explicit Linux/macOS command-line examples in addition to the syntax, especially in sections where only the Windows command shell is called out.
- Highlight any Linux-specific optimizations (such as concurrent scanning) more prominently, possibly with examples.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/queues/storage-quickstart-queues-dotnet.md
...les/storage/queues/storage-quickstart-queues-dotnet.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation page demonstrates a mild Windows bias by listing Windows-specific console environments (cmd, PowerShell) before Bash when instructing users to create a .NET project. However, all commands and instructions are cross-platform, and there are no PowerShell-specific scripts, Windows-only tools, or missing Linux examples. The documentation otherwise maintains good parity for Linux and macOS users.
Recommendations
- List Bash (or 'Bash, cmd, or PowerShell') first or equally when mentioning console environments to avoid implying Windows is primary.
- Explicitly state that all commands work on Windows, Linux, and macOS to reinforce cross-platform support.
- Where relevant, provide any OS-specific notes (e.g., environment variable setup differences) to ensure clarity for Linux/macOS users.
- Consider including a brief section or note on running the sample on Linux/macOS to further demonstrate parity.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/tables/authorize-access-azure-active-directory.md
...rage/tables/authorize-access-azure-active-directory.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation page does not provide any platform-specific examples, commands, or tooling references. However, it also does not include any examples or instructions for either Windows (e.g., PowerShell, Windows tools) or Linux (e.g., Bash, CLI). The absence of examples means there is no explicit Windows bias, but there is also a lack of Linux parity in practical guidance, which could be considered a missed opportunity for inclusivity.
Recommendations
- Add practical examples for both Windows (PowerShell) and Linux (Bash/CLI) environments for common tasks such as assigning roles or obtaining tokens.
- Explicitly mention cross-platform tools (such as Azure CLI) and provide usage examples for both operating systems.
- If referencing scripts or automation, ensure both PowerShell and Bash examples are included.
- Clarify that the instructions are platform-agnostic if no OS-specific steps are required, to reassure users on all platforms.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/queues/storage-quickstart-queues-python.md
...les/storage/queues/storage-quickstart-queues-python.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation page demonstrates a mild 'windows_first' bias in its instructions for creating the project directory. It lists 'cmd, PowerShell, or Bash' as example console windows, with Windows shells mentioned before Bash (the common Linux shell). However, all code examples and instructions are otherwise cross-platform and do not rely on Windows-specific tools or patterns. There are no PowerShell-specific commands, no exclusive use of Windows tools, and Linux users are not omitted from any step.
Recommendations
- When listing console windows or shells, alternate the order or explicitly state cross-platform compatibility, e.g., 'such as Bash, PowerShell, or cmd'.
- Where possible, provide explicit notes that all commands work on both Windows and Linux/macOS, or call out any OS-specific differences if they exist.
- Consider including a brief section or callout confirming that the quickstart is fully cross-platform, to reassure non-Windows users.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/storage-blob-delete.md
...lob/main/articles/storage/blobs/storage-blob-delete.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation is focused exclusively on .NET and C# code examples for managing Azure blobs, without any mention of platform-specific tools, shell environments, or OS-specific instructions. However, it lacks parity for Linux users by not providing examples using cross-platform command-line tools (such as Azure CLI or Bash scripts), which are commonly used on Linux and macOS. There is no explicit Windows bias (such as PowerShell examples or Windows-only tools), but the absence of Linux-friendly alternatives constitutes a subtle bias.
Recommendations
- Add equivalent examples using Azure CLI commands for deleting and restoring blobs, which work across Windows, Linux, and macOS.
- Include Bash script snippets for common blob management tasks, to support Linux and macOS users.
- Explicitly mention that the .NET SDK and code samples are cross-platform, and provide guidance for running them on Linux and macOS (e.g., using .NET Core).
- Consider adding a section or links to documentation for other popular languages and tools (such as Python, Java, or REST API with curl) to ensure broader platform coverage.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/concurrency-manage.md
...blob/main/articles/storage/blobs/concurrency-manage.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation provides only C# code examples and does not include any platform-specific command-line examples (such as PowerShell or Bash). However, it also does not provide any Linux- or cross-platform CLI examples (e.g., Azure CLI, Bash scripts, or REST API via curl), which may disadvantage Linux or non-Windows users who do not use .NET/C#. There is an implicit bias toward .NET/C# development, which is more common on Windows, and no parity for Linux-native workflows.
Recommendations
- Add Azure CLI examples for each concurrency scenario (optimistic and pessimistic) to demonstrate how to manage concurrency from the command line in a cross-platform way.
- Include REST API examples using curl to show how to set conditional headers and acquire/release leases, making the documentation accessible to Linux and macOS users.
- If possible, provide code snippets in additional languages commonly used on Linux (such as Python or JavaScript) to broaden accessibility.
- Explicitly mention that the concurrency concepts apply regardless of platform, and link to cross-platform tooling documentation.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/data-lake-storage-acl-cli.md
...in/articles/storage/blobs/data-lake-storage-acl-cli.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation exhibits a mild 'windows_first' bias by mentioning Windows PowerShell as the example of a local command console before any Linux or macOS alternatives. No Linux-specific shells or tools are referenced, and there are no explicit Linux/macOS command-line environment examples or notes, even though the Azure CLI is cross-platform. However, all command examples themselves are OS-agnostic Azure CLI commands.
Recommendations
- When referring to local command consoles, mention Linux (e.g., Bash) and macOS (e.g., Terminal) alongside Windows PowerShell, or use neutral phrasing such as 'open a command-line terminal (such as Windows PowerShell, macOS Terminal, or Linux Bash)'.
- Add a note clarifying that all Azure CLI commands work identically on Windows, Linux, and macOS.
- Where appropriate, include screenshots or terminal output from non-Windows environments to reinforce cross-platform parity.
- Ensure that any references to shell-specific behavior (such as quoting or environment variables) include Linux/macOS considerations if relevant.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/sas-service-create-dotnet.md
...in/articles/storage/blobs/sas-service-create-dotnet.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation provides only .NET (C#) code examples and does not reference or demonstrate any platform-specific tools, scripts, or command-line environments (such as PowerShell, Windows CMD, Bash, or Linux utilities). However, there is an implicit bias in that the documentation does not mention or provide parity for Linux or cross-platform command-line usage (e.g., Bash scripts, Azure CLI examples), focusing exclusively on .NET code without addressing how to perform these tasks outside of .NET or on non-Windows platforms.
Recommendations
- Add examples using Azure CLI and/or Azure PowerShell to demonstrate how to create a service SAS from the command line, which is relevant for both Windows and Linux users.
- Explicitly mention that the .NET SDK and code samples are cross-platform and can be used on Linux, macOS, and Windows, to avoid the impression of Windows-only applicability.
- Provide links or references to equivalent documentation for other languages or tools (such as Python, Java, Azure CLI) that are commonly used on Linux.
- Consider including a section or note on how to run the .NET code samples on Linux (e.g., using .NET Core/SDK on Ubuntu or other distributions).
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/encryption-scope-overview.md
...in/articles/storage/blobs/encryption-scope-overview.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation page is largely platform-neutral, but in the section on Key Vault soft-delete, the PowerShell example is mentioned before the CLI example, reflecting a subtle 'windows_first' ordering. No Linux-specific tools or examples are provided, but neither are Windows-specific tools beyond this ordering. There are no command-line examples or scripts at all, so there is no overt PowerShell or Windows tool bias, but the ordering of PowerShell before CLI may suggest a slight preference.
Recommendations
- When referencing platform-specific tools or guides (such as PowerShell and CLI), alternate the order in which they are presented, or explicitly mention that both Windows and Linux users are supported.
- Where possible, provide both PowerShell and CLI (az cli) examples side by side, and consider including Bash or Linux shell examples if relevant.
- Add a note clarifying that all features described are available via cross-platform tools (such as Azure CLI) to reassure Linux users.
- If including links to guides, ensure parity by providing links to both PowerShell and CLI documentation, and consider including REST API or SDK examples for maximum cross-platform inclusivity.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/storage-blob-container-create.md
...rticles/storage/blobs/storage-blob-container-create.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation focuses exclusively on .NET and C# code examples without any reference to platform-specific tools or commands. However, it does not provide any OS-specific setup or usage instructions, nor does it mention or show command-line examples (such as PowerShell, Windows CMD, Bash, or Linux shell). There is no explicit Windows bias, but there is a lack of parity in that no Linux (or cross-platform) command-line examples or considerations are provided.
Recommendations
- Add a section on how to create a blob container using cross-platform command-line tools such as Azure CLI (az), with both Windows (CMD/PowerShell) and Linux (Bash) syntax.
- If any environment setup is required (such as setting environment variables or installing the .NET SDK), provide instructions for both Windows and Linux/macOS.
- Explicitly mention that the .NET client library and code samples work on all supported platforms (Windows, Linux, macOS) if applicable.
- Include troubleshooting tips or notes for common issues encountered on Linux systems, if any.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/storage-blob-event-overview.md
.../articles/storage/blobs/storage-blob-event-overview.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation page lists quickstart articles for Azure portal, PowerShell, and Azure CLI in that order. PowerShell (a Windows-centric tool) is mentioned before Azure CLI, which is cross-platform and more commonly used on Linux. However, the page does provide an Azure CLI quickstart, and there are no exclusive Windows-only tools or examples. There are no explicit PowerShell-heavy sections, nor are Linux examples missing entirely.
Recommendations
- List Azure CLI before PowerShell in the quickstart table, as CLI is cross-platform and more accessible to Linux users.
- Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows to reassure non-Windows users.
- If possible, add Bash or shell script examples alongside PowerShell where relevant.
- Ensure that any referenced quickstart or tutorial articles also provide parity between PowerShell and CLI/Bash examples.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/storage-blob-upload.md
...lob/main/articles/storage/blobs/storage-blob-upload.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation is focused exclusively on .NET code examples for uploading blobs to Azure Storage, with all examples and setup instructions assuming a generic .NET development environment. There are no explicit references to Windows-specific tools, PowerShell, or Windows-first patterns. However, the documentation does not address or provide parity for Linux-specific considerations, such as file path conventions, environment setup, or command-line usage on Linux systems. This omission may implicitly bias the documentation toward Windows users, as Linux developers may encounter differences (e.g., file path separators, environment variable handling) that are not addressed.
Recommendations
- Add notes or examples that clarify cross-platform file path handling in .NET (e.g., using Path.Combine or Path.DirectorySeparatorChar).
- Include a section or callout on setting up the .NET development environment on Linux (e.g., using dotnet CLI on Ubuntu or other distributions).
- Mention any OS-specific considerations for uploading files, such as file permissions or case sensitivity on Linux file systems.
- If relevant, provide CLI commands for both Windows (cmd/PowerShell) and Linux (bash) when demonstrating project setup or execution.
- Explicitly state that the code samples are cross-platform and highlight any differences that Linux/macOS users should be aware of.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/storage-blobs-tune-upload-download.md
...es/storage/blobs/storage-blobs-tune-upload-download.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation focuses exclusively on .NET code and Azure Storage client library usage, with no mention of platform-specific tools, commands, or patterns. However, it does not provide any examples or considerations for Linux environments, such as differences in file system performance, network stack tuning, or cross-platform .NET deployment. All code and configuration guidance is generic, but the absence of Linux-specific notes or parity examples may disadvantage Linux users.
Recommendations
- Add a section discussing any platform-specific considerations for Linux, such as file system performance, ulimit settings, or network stack tuning that could impact upload/download performance.
- Provide guidance or links for running the .NET Azure Storage client library on Linux, including any prerequisites or common issues.
- If there are differences in default .NET connection pool settings or behaviors between Windows and Linux, document these explicitly.
- Include a Linux-based example (e.g., running the code in a Docker container or on Ubuntu) to demonstrate cross-platform compatibility.
- Mention any relevant Linux tools (such as lsof, netstat, or system resource monitors) that can help diagnose performance issues.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/classic-account-migration-process.md
...es/storage/common/classic-account-migration-process.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation references both PowerShell and Azure CLI for migration tasks, but consistently lists PowerShell (a Windows-centric tool) before Azure CLI (cross-platform). There are no explicit examples or commands shown, but the ordering and phrasing suggest a subtle preference for Windows tools. No Linux-specific tools or workflows are mentioned, and there is no explicit parity in example ordering or depth.
Recommendations
- When listing tools or migration options, alternate the order (e.g., 'Azure CLI or PowerShell') or explicitly state that both are supported equally.
- Provide example commands for both PowerShell and Azure CLI, ensuring that Linux users see clear, tested CLI examples.
- Mention that Azure CLI is cross-platform and works on Linux, macOS, and Windows, to reassure non-Windows users.
- If referencing documentation for migration steps, ensure that both PowerShell and CLI guides are equally prominent and linked.
- Consider including a short section or callout for Linux/macOS users, highlighting any platform-specific considerations or tips.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/storage-use-azcopy-blobs-properties-metadata.md
...common/storage-use-azcopy-blobs-properties-metadata.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides AzCopy command examples that are generally cross-platform, but the only shell-specific guidance given is for Windows Command Shell (cmd.exe), with a note that all other shells (implicitly Linux/macOS) should use single quotes. There are no explicit Linux or macOS command-line examples, nor are there references to Linux-specific shell behaviors, which may subtly prioritize Windows users.
Recommendations
- Include explicit Linux/macOS shell examples alongside Windows examples, showing both quoting styles in parallel.
- Add a table or section summarizing quoting and escaping differences for common shells (cmd.exe, PowerShell, Bash, Zsh, etc.).
- Reference Linux/macOS tools or shell environments where relevant, and mention any platform-specific considerations for AzCopy usage.
- Ensure that any troubleshooting or next steps sections include links or notes relevant to Linux/macOS users, not just Windows.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/storage-use-azcopy-blobs-copy.md
...ticles/storage/common/storage-use-azcopy-blobs-copy.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation is generally cross-platform, as AzCopy is a cross-platform CLI tool and all command examples use single quotes (Unix-style) by default. However, there is a recurring pattern where guidance for Windows users (specifically, the use of double quotes in cmd.exe) is always mentioned immediately after or alongside the main example, which is Unix/Linux/macOS oriented. While not egregiously biased, this does subtly prioritize Windows-specific instructions in every example's tip, rather than providing a balanced or parallel structure for both platforms.
Recommendations
- Consider providing both Linux/macOS and Windows (cmd.exe/PowerShell) command examples side by side, rather than embedding Windows-specific notes after each example.
- Explicitly mention that AzCopy is cross-platform at the start, and provide a brief table or section summarizing quoting/escaping differences across shells (Bash, PowerShell, cmd.exe) to avoid repetitive inline notes.
- Where possible, include PowerShell-specific guidance if Windows users are likely to use it, not just cmd.exe.
- Ensure parity in troubleshooting and environment variable instructions (e.g., how to set AZCOPY_CONCURRENCY_VALUE in Bash vs. Windows shells).
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/storage-use-azcopy-s3.md
.../main/articles/storage/common/storage-use-azcopy-s3.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation generally maintains cross-platform parity, providing both Windows and Linux/macOS environment variable examples. However, in the section on setting AWS credentials, Windows (PowerShell and Command Prompt) commands are presented first in the table, with Linux and macOS following. Additionally, there are notes about quoting conventions that specifically call out Windows (cmd.exe) differences, but these are informative and not exclusive. All AzCopy command examples themselves are platform-agnostic.
Recommendations
- Alternate the order of operating systems in tables or examples to avoid always listing Windows first. For example, sometimes list Linux/macOS before Windows.
- Explicitly state that all AzCopy commands work identically across platforms, and provide any necessary platform-specific notes in a balanced way.
- Where quoting or environment variable conventions differ, consider providing side-by-side examples or a short section for each OS, rather than embedding Windows-specific notes in general tips.
- Ensure that future additions do not default to Windows-first ordering or terminology, and review for parity in all new examples.