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 1426-1450 of 1657 flagged pages
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/storage-quickstart-static-website-terraform.md
...e/blobs/storage-quickstart-static-website-terraform.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell instructions for verifying results, but the PowerShell example is given equal prominence to the CLI example, and there is no explicit mention of Linux or macOS environments. The use of PowerShell as a primary example can be seen as a Windows-centric approach, especially since Linux users are more likely to use Bash or native CLI tools. There are no explicit Linux-specific instructions or examples, and no mention of platform differences in commands or environment setup.
Recommendations
- Explicitly mention that the Azure CLI example works on Linux, macOS, and Windows, while PowerShell is primarily for Windows (or PowerShell Core on other platforms).
- Provide Bash shell examples alongside PowerShell, especially for steps involving environment variables or command substitution.
- Clarify any platform-specific prerequisites or differences in command syntax.
- Consider listing the Azure CLI (Bash) example first, as it is cross-platform, and then provide PowerShell as an alternative.
- Add a note about how to open a browser from the command line on different operating systems, or clarify that users should manually open the URL in their preferred browser.
Create Pull Request
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/storage-quickstart-blobs-cli.md
...articles/storage/blobs/storage-quickstart-blobs-cli.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation is generally cross-platform and uses Azure CLI, which is available on Windows, Linux, and macOS. However, in the AzCopy section, the file path example ('C:\myDirectory\myFile.txt') is Windows-specific, and there is no equivalent Linux/macOS example provided. This prioritizes Windows usage patterns and omits Linux/macOS parity in that context.
Recommendations
- For all file path examples (especially in AzCopy), provide both Windows and Linux/macOS variants, e.g., 'C:\myDirectory\myFile.txt' and '/home/user/myDirectory/myFile.txt'.
- When introducing tools or commands that interact with the file system, explicitly mention that the examples apply to all platforms, and show platform-specific differences where relevant.
- Consider alternating the order of examples or providing side-by-side examples for Windows and Linux/macOS to avoid implicit prioritization.
- Audit other sections (such as file creation) to ensure that instructions are equally accessible to users on all platforms (e.g., mention 'touch' for Linux/macOS as well as 'vi').
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/storage-quickstart-blobs-java-quarkus.md
...storage/blobs/storage-quickstart-blobs-java-quarkus.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Summary
The documentation generally uses cross-platform tools (Azure CLI, Maven, Java), but there is a subtle Windows bias in the lack of explicit Linux-specific instructions or examples. The guide assumes a Unix-like shell environment (using bash syntax for commands), but does not clarify compatibility or provide PowerShell/Windows Command Prompt equivalents. However, it also does not provide explicit Linux guidance for environment variables, file paths, or troubleshooting, and references to Docker Desktop may imply a Windows/macOS focus. There are no PowerShell-specific examples, but the absence of Linux-specific troubleshooting or notes means Linux users may have to infer compatibility.
Recommendations
- Explicitly state that the bash commands are compatible with Linux, macOS, and Windows Subsystem for Linux (WSL), and provide PowerShell/Windows Command Prompt equivalents where appropriate.
- Add a section or notes on running the sample on native Linux, including any prerequisites or differences (e.g., file permissions, path separators).
- Clarify Docker installation instructions for Linux users, not just Docker Desktop (which is primarily for Windows/macOS).
- Include troubleshooting tips for common Linux-specific issues (e.g., permissions, environment variable export differences).
- Where file paths are mentioned, note the differences between Windows and Linux path conventions.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/storage-quickstart-blobs-nodejs-typescript.md
...ge/blobs/storage-quickstart-blobs-nodejs-typescript.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation demonstrates some Windows bias, particularly in the order and prominence of tool mentions. In setup instructions, Windows tools (cmd, PowerShell) are listed before Bash, and Visual Studio Code is used as the default editor without mentioning Linux alternatives. In environment variable setup, Windows instructions (setx) are presented before Linux (export). PowerShell is given its own authentication section, while Bash is not. However, Linux instructions are present and correct, and Bash is mentioned as a console option.
Recommendations
- List Bash (Linux/macOS) before or alongside Windows tools (cmd, PowerShell) when describing console options.
- When providing instructions for setting environment variables, present Linux/macOS (export) first or in parallel with Windows (setx), or use tabs to separate OS-specific instructions.
- Include explicit Bash authentication instructions (e.g., using Azure CLI in Bash) alongside PowerShell, not just as a note.
- Mention alternative editors (such as nano, vim, or code on Linux) when instructing users to open the project, or clarify that Visual Studio Code is cross-platform.
- Where possible, use neutral language (e.g., 'open a terminal') instead of Windows-specific terms ('console window', 'cmd').
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/storage-quickstart-blobs-nodejs.md
...icles/storage/blobs/storage-quickstart-blobs-nodejs.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation generally maintains cross-platform parity but exhibits mild Windows bias in a few areas. Windows shells (cmd, PowerShell) are mentioned before Bash in the initial project setup instructions, and Visual Studio Code is the only editor referenced for opening the project. In authentication instructions, PowerShell is given its own tab, while Linux shells are not explicitly highlighted elsewhere. Setting environment variables provides both Windows and Linux examples, but Windows is listed first.
Recommendations
- When listing console options, use neutral or alphabetical order (e.g., 'Bash, cmd, or PowerShell') instead of listing Windows shells first.
- Explicitly mention and provide parity for Linux/macOS tools and workflows throughout, including editor options (e.g., 'Open the project in your preferred editor, such as Visual Studio Code, Vim, or Sublime Text').
- For authentication instructions, provide tabs or explicit sections for both Linux/macOS and Windows shells (e.g., Bash, Zsh, cmd, PowerShell), not just PowerShell.
- When showing environment variable commands, alternate the order or clarify that both Windows and Linux/macOS are equally supported.
- Consider adding a short statement at the top affirming that all steps work on Windows, Linux, and macOS, and that examples are provided for each where differences exist.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/last-sync-time-get.md
...lob/main/articles/storage/common/last-sync-time-get.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides both PowerShell and Azure CLI examples for checking the Last Sync Time property, but PowerShell is presented first and in greater detail. PowerShell is a Windows-centric tool, and its prioritization may suggest a Windows bias. However, the Azure CLI example is present and is cross-platform, which helps mitigate the bias. There are no exclusive references to Windows-only tools or missing Linux examples, but the ordering and emphasis favor Windows users.
Recommendations
- Present Azure CLI examples before PowerShell, as Azure CLI is cross-platform and more inclusive for Linux and macOS users.
- Explicitly mention that both PowerShell and Azure CLI are available on Windows, Linux, and macOS (where applicable), to clarify cross-platform support.
- Consider providing Bash or shell script examples, or clarifying that the Azure CLI example works in Bash/Unix shells as well as Windows.
- Ensure parity in detail and explanation between PowerShell and Azure CLI sections.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/geo-redundant-design.md
...b/main/articles/storage/common/geo-redundant-design.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates bias by only providing a testing example using Fiddler, a Windows-centric tool, and does not mention or provide equivalent Linux-friendly alternatives. There are no command-line or scripting examples for Linux or cross-platform environments, and the only code snippets are in C# (which is cross-platform, but the testing tooling is not). No PowerShell or CMD examples are present, but the exclusive mention of Fiddler and lack of Linux alternatives constitutes a Windows bias.
Recommendations
- Include Linux-friendly alternatives to Fiddler for simulating HTTP errors, such as mitmproxy, tcpdump with iptables, or custom Python scripts using libraries like mitmproxy or scapy.
- Explicitly mention that Fiddler is a Windows tool and suggest equivalent tools for Linux and macOS users.
- Provide example scripts or command-line instructions for Linux environments to simulate retryable errors (e.g., using curl, iptables, or mitmproxy).
- Add a note or section on cross-platform testing strategies to ensure parity for developers on all major operating systems.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/lock-account-resource.md
.../main/articles/storage/common/lock-account-resource.md
Medium 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 using the Azure Portal, PowerShell, and Azure CLI. The PowerShell example is given before the Azure CLI example, which may suggest a Windows-first approach. The PowerShell example uses the Az PowerShell module, which is primarily associated with Windows environments, although it is cross-platform. There are no explicit Linux shell (bash) or scripting examples, and no mention of Linux-specific tools or workflows.
Recommendations
- Present Azure CLI examples before PowerShell examples, as Azure CLI is natively cross-platform and widely used on Linux.
- Explicitly mention that both Azure CLI and PowerShell are cross-platform, but highlight Azure CLI as the default for Linux users.
- Add bash shell scripting examples or usage notes for Linux users where appropriate.
- Where PowerShell is referenced, clarify that it is available on Linux and macOS as well as Windows, or provide a link to installation instructions for non-Windows platforms.
- Consider including a table or section that compares the commands across different platforms (Windows, Linux, macOS) to reinforce parity.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/security-restrict-copy-operations.md
...es/storage/common/security-restrict-copy-operations.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides configuration instructions for the Azure portal, PowerShell, and Azure CLI. PowerShell is presented as a primary scripting example before Azure CLI, which may indicate a Windows-first or PowerShell-heavy bias. There are no explicit Linux-only or Windows-only tools, but the ordering and emphasis on PowerShell may disadvantage Linux users, who are more likely to use Azure CLI or shell scripting.
Recommendations
- Present Azure CLI examples before PowerShell, as Azure CLI is cross-platform and more familiar to Linux users.
- Explicitly mention that both PowerShell and Azure CLI are available on Windows, macOS, and Linux, and provide installation links for all platforms.
- Where possible, provide Bash or shell script equivalents for common operations, especially for log querying or automation.
- Include a note clarifying that PowerShell Core is cross-platform, but that Azure CLI is often preferred in Linux environments.
- Ensure screenshots and instructions in portal sections do not assume a Windows environment (e.g., file paths, UI differences).
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/storage-account-sas-create-dotnet.md
...es/storage/common/storage-account-sas-create-dotnet.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Summary
The documentation exclusively provides .NET (C#) code examples and instructions, which are most commonly associated with Windows development environments. There are no examples or guidance for Linux users, such as using .NET on Linux, Bash, or cross-platform CLI tools. The focus on .NET without mention of Linux-compatible workflows or alternative languages/tools may make the content less accessible to Linux developers.
Recommendations
- Include explicit instructions or notes on how to run the .NET examples on Linux (e.g., using .NET Core/SDK on Ubuntu).
- Provide equivalent examples using Azure CLI or REST API calls, which are cross-platform and commonly used on Linux.
- Mention that the .NET client library is cross-platform and provide setup steps for Linux environments.
- Add links or references to documentation for other languages and platforms, such as Python or Java, which are popular in Linux environments.
- Ensure that any referenced tools or workflows are available and documented for both Windows and Linux users.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/storage-explorer-network.md
...in/articles/storage/common/storage-explorer-network.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation describes proxy configuration and network behavior in Azure Storage Explorer without explicit Windows-only commands or tools, but it implicitly prioritizes Windows patterns by referencing 'system proxy' and 'OS proxy settings' without clarifying platform differences or providing Linux/macOS-specific guidance. There are no examples or instructions tailored to Linux or macOS users, and no mention of how to configure system proxies or certificates on those platforms.
Recommendations
- Add explicit instructions or references for configuring system proxy settings on Linux and macOS, alongside Windows.
- Include example commands or GUI paths for setting environment variables and system proxies on Linux (e.g., using GNOME/KDE network settings or modifying /etc/environment).
- Clarify how Storage Explorer interacts with system proxy settings on different operating systems, including any limitations or differences.
- Provide troubleshooting tips or links specific to Linux/macOS for common proxy and certificate issues.
- Ensure parity in authentication method support explanations, noting any OS-specific behaviors.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/storage-account-keys-manage.md
...articles/storage/common/storage-account-keys-manage.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides examples for managing Azure Storage account access keys using the Azure portal, PowerShell, and Azure CLI. PowerShell examples are given equal prominence to Azure CLI, and in some cases, PowerShell is listed before Azure CLI. This ordering and the presence of detailed PowerShell scripts reflect a mild Windows bias, as PowerShell is primarily a Windows-centric tool (though it is now cross-platform). There are no explicit Linux shell (bash) or scripting examples outside of Azure CLI, and no mention of Linux-specific tools or workflows. The documentation does not provide any examples using native Linux utilities or shell scripting outside of Azure CLI, nor does it mention Linux as a platform in the narrative.
Recommendations
- Ensure that Azure CLI examples are always presented before or alongside PowerShell examples, as Azure CLI is cross-platform and more familiar to Linux users.
- Add explicit bash or shell script examples where appropriate, especially for common automation scenarios.
- Clarify in the introduction that PowerShell examples are also available on Linux and macOS, or provide a note about PowerShell Core's cross-platform support.
- Where possible, include references to Linux-native tools or workflows, or at least acknowledge their absence.
- Consider adding a 'Linux' or 'macOS' tab for scenarios where platform-specific steps or considerations exist.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/storage-explorer-sign-in.md
...in/articles/storage/common/storage-explorer-sign-in.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation demonstrates a mild Windows bias by listing Windows-specific sign-in mechanisms (authentication broker) before macOS and Linux equivalents, and by recommending the Windows-specific authentication broker as the default. Linux and macOS are grouped together and only offered the default web browser option, with less detail or emphasis.
Recommendations
- Present sign-in methods for all platforms in parallel, rather than listing Windows first.
- Provide equal detail and recommendations for Linux and macOS, including any platform-specific caveats or advantages.
- If Windows-specific tools (like the authentication broker) are mentioned, clarify the equivalent or alternative mechanisms for Linux and macOS.
- Consider adding Linux-specific troubleshooting tips or notes, if any exist, to ensure parity.
- Explicitly state when a feature is not available on Linux, and suggest alternatives or workarounds.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/storage-disaster-recovery-guidance.md
...s/storage/common/storage-disaster-recovery-guidance.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation references Windows-centric tools such as Azure PowerShell and AzCopy for data copy and backup operations, but does not provide equivalent Linux/Unix command-line examples or mention cross-platform alternatives. There are no explicit Linux or bash examples, and the documentation does not clarify that AzCopy is cross-platform or provide CLI/REST API examples that are OS-neutral.
Recommendations
- Explicitly mention that AzCopy is available for Windows, Linux, and macOS, and provide installation instructions or links for each platform.
- Include Azure CLI (az storage ...) examples alongside or instead of Azure PowerShell, as Azure CLI is cross-platform and more commonly used on Linux/macOS.
- When referencing PowerShell, also provide bash or shell script equivalents for common operations.
- Clarify that REST APIs and SDKs are available for all platforms, and provide sample commands or code snippets in a cross-platform language (e.g., Python, bash).
- Where tools are mentioned (e.g., AzCopy, PowerShell), provide links to their cross-platform documentation and usage guides.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/storage-require-secure-transfer.md
...cles/storage/common/storage-require-secure-transfer.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides detailed PowerShell instructions before Azure CLI examples, and the PowerShell section is more prominent and extensive. This ordering and emphasis may suggest a Windows-centric approach, potentially disadvantaging Linux or cross-platform users who are more likely to use Azure CLI or other SDKs.
Recommendations
- Present Azure CLI examples before PowerShell, as Azure CLI is cross-platform and widely used on Linux and macOS.
- Ensure that CLI and PowerShell sections are equally detailed and prominent.
- Explicitly mention that Azure CLI commands work on Windows, Linux, and macOS.
- Add Bash shell examples where appropriate, especially for scripting scenarios.
- Consider including a table summarizing all available methods (Portal, CLI, PowerShell, REST, SDKs) with platform compatibility notes.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/storage-service-encryption.md
.../articles/storage/common/storage-service-encryption.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page exhibits mild Windows bias by referencing BitLocker (a Windows-specific encryption technology) as a comparison for Azure Storage encryption and by linking to the Windows-specific Cryptography API: Next Generation (CNG) documentation for further information about cryptographic modules. There are no explicit Linux examples, tools, or references, and the only concrete tool comparisons are Windows-centric. However, the rest of the content is largely platform-neutral and focuses on Azure services and SDKs.
Recommendations
- When making analogies or comparisons, include Linux equivalents (e.g., compare Azure Storage encryption to both BitLocker and Linux dm-crypt/LUKS).
- When linking to cryptographic module documentation, provide references to cross-platform or Linux-relevant cryptographic APIs (such as OpenSSL, dm-crypt, or general FIPS 140-2 compliance documentation) alongside Windows CNG.
- Explicitly state that Azure Storage encryption is platform-agnostic and does not require any specific OS tools or patterns.
- Where possible, include examples or references that are relevant to Linux administrators, such as how to interact with Azure Key Vault or manage client-side encryption from Linux environments.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/storage-solution-large-dataset-low-network.md
...e/common/storage-solution-large-dataset-low-network.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by specifically recommending the use of Robocopy, a Windows-only file copy tool, for transferring data to Azure Data Box devices. There are no Linux-specific tools or examples mentioned, nor is there guidance for Linux or cross-platform environments. This may leave Linux users without clear instructions or tool recommendations.
Recommendations
- Include Linux-friendly data copy tools such as rsync, cp, or dd in the documentation alongside Robocopy.
- Provide example commands for both Windows (Robocopy, PowerShell) and Linux (rsync, cp) environments.
- Explicitly state that Data Box devices support SMB/NFS protocols and can be accessed from Linux systems, if applicable.
- Add a section or note addressing cross-platform usage and best practices for Linux and macOS users.
- Ensure parity in tool recommendations and examples to make the documentation inclusive for all major operating systems.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/elastic-san/elastic-san-planning.md
...n/articles/storage/elastic-san/elastic-san-planning.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page exhibits mild Windows bias. It references Windows-specific tools and APIs (such as BitLocker and Cryptography API: Next Generation) when discussing encryption, and draws analogies to Windows technologies before or instead of Linux equivalents. Additionally, in the networking section, Windows is mentioned after Linux, but the encryption section uses Windows as the primary comparison point.
Recommendations
- When describing encryption, provide Linux analogies or mention Linux-native disk encryption tools (e.g., LUKS/dm-crypt) alongside BitLocker.
- When referencing cryptographic APIs, include links or references to Linux/OpenSSL or other cross-platform cryptographic modules, not just Windows CNG.
- Ensure that all examples, analogies, and tool references are balanced between Windows and Linux, or are presented in a platform-neutral way.
- Consider including a brief note about how storage service encryption is analogous to both BitLocker (Windows) and LUKS (Linux), to help Linux users relate.
- If referencing platform-specific tools, always provide the equivalent for the other major platforms.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/storage-use-azcopy-files.md
...in/articles/storage/common/storage-use-azcopy-files.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation consistently uses Windows-style file paths (e.g., 'C:\myDirectory\myTextFile.txt') in all command examples and does not provide any Linux or macOS path examples. While there are repeated notes about quoting differences between shells, every single example uses Windows paths and backslashes, with no parity for Linux (e.g., '/home/user/myDirectory/myTextFile.txt'). This may confuse or alienate Linux/macOS users and gives the impression that Windows is the primary or only supported environment.
Recommendations
- For every example using a Windows path, provide a corresponding Linux/macOS example using forward slashes and typical Unix-style paths (e.g., '/home/user/myDirectory/myTextFile.txt').
- Where possible, alternate the order of examples so that Linux/macOS is shown first in some sections.
- Add a dedicated section or callout at the top clarifying cross-platform support and showing a side-by-side comparison of path formats and quoting conventions for Windows (cmd.exe), PowerShell, Linux, and macOS.
- Explicitly mention that AzCopy is fully supported on Linux and macOS, and link to installation instructions for those platforms.
- In tables or checklists, include notes or columns for both Windows and Linux/macOS usage patterns.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/storage-use-azcopy-blobs-synchronize.md
...storage/common/storage-use-azcopy-blobs-synchronize.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation consistently uses Windows-style paths (e.g., 'C:\myDirectory') in all examples and does not provide any Linux/macOS path examples (e.g., '/home/user/myDirectory'). While there are tips about quoting differences between shells, the actual command examples are all Windows-centric. No Linux or macOS-specific examples or patterns are shown.
Recommendations
- Provide parallel examples using Linux/macOS-style paths (e.g., '/home/user/myDirectory') alongside Windows examples.
- Explicitly show both Windows (cmd.exe) and Linux/macOS (bash/zsh) command syntax, including correct quoting and path separators.
- Consider a table or tabbed interface to let users select their OS and see relevant examples.
- Mention any OS-specific considerations (such as case sensitivity or file permission issues) where relevant.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/storage-use-azcopy-blobs-download.md
...es/storage/common/storage-use-azcopy-blobs-download.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation consistently uses Windows-style paths (e.g., 'C:\myDirectory\myTextFile.txt') in all examples and does not provide any Linux/macOS path examples. While there are notes about quoting differences between shells, all concrete examples use Windows paths, which may confuse or alienate Linux/macOS users. No Linux-specific tools or patterns are mentioned, and the documentation assumes a Windows file system structure throughout.
Recommendations
- For each example, provide both Windows and Linux/macOS versions, showing both 'C:\myDirectory\myTextFile.txt' and '/home/user/myDirectory/myTextFile.txt' (or similar).
- In syntax and example sections, alternate or parallelize examples for both platforms, clearly labeling them as 'Windows' and 'Linux/macOS'.
- Add a short section or note at the top clarifying path differences and providing a quick reference for both Windows and Linux/macOS users.
- Where quoting differences are discussed, provide explicit command examples for both cmd.exe, PowerShell, and bash/zsh.
- Review all references to local file paths and ensure Linux/macOS users are equally represented.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/storage-use-azcopy-blobs-upload.md
...cles/storage/common/storage-use-azcopy-blobs-upload.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation consistently uses Windows-style file paths (e.g., 'C:\myDirectory\myTextFile.txt') in all command examples and does not provide any Linux/macOS path examples (e.g., '/home/user/myDirectory/myTextFile.txt'). While there are tips about quoting differences between shells, all concrete examples are Windows-centric, which may confuse or alienate Linux/macOS users.
Recommendations
- For each example using a Windows path, provide an equivalent Linux/macOS example using forward slashes (e.g., '/home/user/myDirectory/myTextFile.txt').
- Alternate the order of examples or provide both Windows and Linux/macOS examples side by side to ensure parity.
- Explicitly mention that AzCopy is cross-platform and show at least one example per section for each major OS.
- Clarify wildcard and path separator usage for Linux/macOS shells where it differs from Windows.
- Consider a table or tabbed interface to switch between Windows and Linux/macOS examples for better usability.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/storage-network-security.md
...in/articles/storage/common/storage-network-security.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides comprehensive coverage for both Azure PowerShell and Azure CLI, with clear tabbed sections for each. However, there is a noticeable Windows bias: PowerShell examples are always presented before Azure CLI, and PowerShell is referenced as the primary scripting tool. There are no explicit Linux shell (bash) or cross-platform scripting examples outside of Azure CLI, and the use of PowerShell-centric language and commands may implicitly prioritize Windows users. No Windows-only tools are mentioned, but the ordering and prominence of PowerShell can disadvantage Linux-first users.
Recommendations
- Alternate the order of PowerShell and Azure CLI examples, or present Azure CLI first in some sections, as Azure CLI is cross-platform and more familiar to Linux users.
- Explicitly mention that both Azure CLI and PowerShell are available on Windows, macOS, and Linux, and provide installation links for all platforms.
- Where possible, add bash script examples (e.g., for looping or automation) to demonstrate Linux-native workflows.
- Clarify that Azure CLI commands can be run in any shell (bash, zsh, PowerShell, etc.), and provide sample shell invocation lines for Linux.
- Avoid language that implies PowerShell is the default or preferred automation tool; instead, present both options as equal.
- Consider including a short section or callout for Linux users, highlighting any differences or tips for using the Azure CLI or PowerShell on Linux.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/storage-use-azcopy-google-cloud.md
...cles/storage/common/storage-use-azcopy-google-cloud.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation demonstrates mild Windows bias by listing Windows-specific commands and tools before their Linux/macOS equivalents, and by providing detailed notes about Windows command shell quoting before mentioning other shells. However, Linux and macOS examples are present and correct, and the AzCopy commands themselves are cross-platform.
Recommendations
- Present Linux/macOS and Windows instructions/examples in parallel or in a neutral order (e.g., Linux/macOS first, or alphabetically).
- Where quoting or environment variable differences exist, provide explicit examples for all major shells (bash, zsh, PowerShell, cmd.exe) in a side-by-side or tabbed format.
- Avoid language that centers Windows as the default (e.g., 'except for Windows Command Shell (cmd.exe)'), and instead state differences neutrally (e.g., 'On Windows (cmd.exe), use double quotes; on Linux/macOS shells, use single quotes.').
- Consider including PowerShell-specific examples if Windows is to be supported, as many Windows users use PowerShell rather than cmd.exe.
- Ensure that download and installation instructions for AzCopy are equally detailed for all platforms.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/videos-azure-files-and-file-sync.md
...les/storage/common/videos-azure-files-and-file-sync.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page lists several Azure Files and File Sync video resources. Among the video titles and descriptions, there is a clear emphasis on Windows-centric scenarios (e.g., 'Mount an Azure file share in Windows', 'SMB workloads'), while equivalent Linux scenarios (such as mounting via Linux or using Linux tools) are not mentioned. Although there is a mention of NFS 4.1 (which is relevant for Linux), the overall focus and ordering prioritize Windows use cases, and there is a lack of explicit Linux examples or parity.
Recommendations
- Add video content or explicit references for mounting Azure file shares on Linux systems, including command-line examples (e.g., using mount.cifs or NFS on Linux).
- Ensure that for every Windows-specific scenario (such as mounting or configuring file shares), there is a corresponding Linux example or video.
- Balance the ordering of video topics so that Linux and Windows scenarios are presented with equal prominence.
- Include videos or documentation on using Azure Files with Linux authentication mechanisms and tools (e.g., Kerberos on Linux, Linux file server replacement scenarios).