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 1226-1250 of 1657 flagged pages
Storage
Azure data transfer options for small datasets with low to moderate network bandwidth
...ttps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/storage-solution-small-dataset-low-moderate-network.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation lists Azure PowerShell as a scripting/programmatic tool alongside AzCopy and Azure CLI, but it specifically highlights PowerShell (a Windows-centric tool) before Azure CLI (which is cross-platform and more Linux-friendly). There are no explicit Linux shell or scripting examples, and the mention of PowerShell may imply a Windows-first approach for users seeking automation, despite the cross-platform nature of AzCopy and Azure CLI.
Recommendations
- Provide explicit Linux shell (bash) examples for AzCopy and Azure CLI usage.
- Mention Azure CLI before PowerShell when listing scripting/programmatic tools, as CLI is more widely used on Linux.
- Clarify that PowerShell Core is available on Linux, or link to Linux installation instructions if PowerShell is referenced.
- Include references or links to Linux-specific documentation or tutorials for data transfer.
- Balance example coverage by showing both Windows (PowerShell, CMD) and Linux (bash, shell script) usage patterns.
Create Pull Request
Storage
Get started with the Azure Storage management library for .NET
...icles/storage/common/storage-srp-dotnet-get-started.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates subtle Windows bias by referencing Azure PowerShell as a primary tool for resource provider registration, and by not providing explicit Linux-specific examples or guidance. While the .NET SDK is cross-platform, the documentation does not mention Linux-specific setup, environment variable configuration, or shell usage, and omits Linux/Unix command-line examples (e.g., bash) in favor of generic or Windows-centric tools.
Recommendations
- Include explicit Linux/Unix shell examples (e.g., bash) for environment variable setup and credential configuration.
- Provide guidance for using the .NET SDK on Linux, including installation steps and troubleshooting common Linux-specific issues.
- When listing tools for resource provider registration, mention Azure CLI before Azure PowerShell, as CLI is cross-platform and more commonly used on Linux.
- Add notes or links to documentation about running .NET applications and Azure SDKs on Linux, including supported distributions and prerequisites.
- Ensure parity in examples and instructions for both Windows and Linux environments, especially for authentication and local development scenarios.
Storage
Optimize the performance of AzCopy v10 with Azure Storage
...articles/storage/common/storage-use-azcopy-optimize.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Linux and Windows examples for setting environment variables, but Windows (cmd.exe and PowerShell) is mentioned first in tips and examples. The guidance for quoting arguments prioritizes Windows-specific behavior, and PowerShell is used for Windows examples, while Linux uses bash. There are no missing Linux examples, but Windows tools and patterns are referenced before Linux equivalents in some cases.
Recommendations
- Present Linux and Windows examples side-by-side or in parallel tabs, ensuring equal prominence.
- When discussing quoting or shell-specific behavior, mention Linux and Windows equally, or start with Linux if usage statistics suggest it is more common.
- Avoid language that suggests Windows is the default or primary platform (e.g., 'except for Windows Command Shell'). Instead, use neutral phrasing such as 'On Linux/macOS, use single quotes; on Windows, use double quotes.'
- Include PowerShell and bash examples together, and consider adding macOS-specific notes if relevant.
- Review the order of platform-specific instructions to ensure neither is consistently prioritized over the other.
Storage
Download blobs from Azure Blob Storage by using AzCopy v10
...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') in all examples, and does not provide equivalent Linux/macOS examples (e.g., '/home/user/myDirectory'). While there are notes about quoting differences between shells, the examples themselves are exclusively Windows-centric, which may confuse or exclude Linux/macOS users.
Recommendations
- Provide paired examples for both Windows and Linux/macOS, showing appropriate local path formats (e.g., 'C:\myDirectory' and '/home/user/myDirectory').
- Alternate or parallelize examples so that Linux/macOS commands are shown alongside Windows commands.
- Add explicit notes or sections for Linux/macOS users, including common shell usage patterns and file path conventions.
- Ensure that documentation does not assume Windows as the default environment, and that instructions are equally clear for all supported platforms.
Storage
Copy or move data to Azure Storage by using AzCopy v10
...main/articles/storage/common/storage-use-azcopy-v10.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a mild Windows bias. In the main example for using AzCopy with a SAS token, only a Windows-style path (C:\local\path) is shown, with no Linux or macOS equivalent. Additionally, when describing how to run AzCopy, the use of '.\azcopy' (Windows syntax) is mentioned before any Linux-specific invocation, and the example command uses Windows path separators. While Linux installation is covered, usage examples and command syntax are Windows-centric.
Recommendations
- Provide parallel Linux/macOS examples alongside Windows examples, especially for command usage (e.g., show both 'C:\local\path' and '/home/user/local/path').
- When describing how to run AzCopy, include Linux/macOS shell syntax (e.g., './azcopy') equally or before Windows syntax.
- Ensure that all example commands use both Windows and Linux/macOS path formats, or use a generic placeholder that is platform-neutral.
- Explicitly mention differences in path separators and shell invocation between platforms to help users avoid confusion.
- Consider alternating the order of platform-specific instructions to avoid consistently prioritizing Windows.
Storage
Using the HDFS CLI with Azure Data Lake Storage
.../blobs/data-lake-storage-use-hdfs-data-lake-storage.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation page demonstrates Windows bias by presenting PowerShell code for SSH access as the only example, even though the context is a Linux HDInsight cluster. There is no equivalent Linux shell (bash) example, and the use of PowerShell is mentioned before any Linux alternatives, which may confuse or inconvenience Linux users.
Recommendations
- Provide Linux shell (bash) examples alongside or before PowerShell examples, especially for SSH commands.
- Clarify that PowerShell is optional and that standard Linux/Unix shells are fully supported and often preferred for HDInsight clusters.
- Explicitly mention cross-platform compatibility for all CLI commands and tools.
- Review other sections for similar patterns and ensure Linux parity in all command-line examples.
Storage
Encryption scopes for Blob storage
...in/articles/storage/blobs/encryption-scope-overview.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation page references PowerShell before CLI in the section about Azure Key Vault soft-delete, suggesting a Windows-first approach. There are no explicit Linux-only examples or tools, but the ordering and emphasis on PowerShell may indicate a subtle bias toward Windows users.
Recommendations
- Present CLI and PowerShell examples side-by-side or in parallel, rather than listing PowerShell first.
- Include explicit Bash or Linux shell examples where applicable, especially for common tasks.
- Ensure that references to platform-specific tools (PowerShell, CLI) are balanced and do not prioritize Windows tools.
- Add a note clarifying that all operations can be performed equally on Linux, macOS, and Windows using the Azure CLI.
Storage
Container-level WORM policies for immutable blob data
...orage/blobs/immutable-container-level-worm-policies.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation page demonstrates a Windows bias by referencing PowerShell commands first and providing explicit examples for Windows tools (PowerShell) before mentioning cross-platform alternatives (Azure CLI). No Linux-specific examples or shell commands are provided, and the documentation does not mention Linux tooling or patterns, focusing instead on Windows-centric approaches.
Recommendations
- Provide Linux shell (bash) examples alongside PowerShell commands, especially for control plane operations.
- Ensure Azure CLI examples are given equal prominence and detail as PowerShell examples, and consider listing CLI commands before or alongside PowerShell commands.
- Explicitly mention cross-platform compatibility for all command-line tools and clarify which commands work on Linux/macOS.
- Include notes or examples for scripting and automation in Linux environments, such as bash scripts or usage in cloud-native CI/CD pipelines.
- Review and update documentation to avoid Windows-first ordering and terminology, ensuring parity for Linux and macOS users.
Storage
Monitor Azure File Sync Cloud Tiering
...s/storage/file-sync/file-sync-monitor-cloud-tiering.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows Tools
Summary
The documentation assumes the use of Azure File Sync, which is only supported on Windows Server, and all monitoring instructions are given in the context of the Azure portal or Windows-based server endpoints. There are no examples or mentions of Linux tools, commands, or environments, and the documentation does not clarify the Windows-only nature of Azure File Sync, potentially leading to confusion for Linux users.
Recommendations
- Explicitly state early in the documentation that Azure File Sync and its monitoring features are only supported on Windows Server, to set expectations for Linux users.
- If any cross-platform monitoring is possible (e.g., via Azure Monitor REST APIs, CLI, or PowerShell Core on Linux), provide examples for Linux environments.
- Where possible, include Azure CLI or REST API examples for metric retrieval, which can be run on any platform, not just Windows.
- Add a section or note addressing Linux users, clarifying support limitations and suggesting alternative approaches for monitoring Azure Files from Linux clients if relevant.
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page exclusively describes Azure File Sync in the context of Windows Server, with no mention of Linux support, usage, or equivalent tooling. All examples, deployment scenarios, and performance considerations are Windows-centric, and there are no Linux examples or references to Linux-compatible agents or workflows.
Recommendations
- Clarify in the introduction whether Azure File Sync is supported only on Windows Server, or if Linux support is planned or available.
- If Linux support exists or is planned, add equivalent examples and performance guidance for Linux deployments.
- Explicitly mention the lack of Linux support if that is the case, to set expectations for cross-platform users.
- Provide links or references to alternative solutions for Linux environments, such as mounting Azure Files directly or using other synchronization tools.
Storage
Monitoring data reference for Azure Blob Storage
...ticles/storage/blobs/monitor-blob-storage-reference.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page shows mild Windows bias, most notably in the example 'userAgentHeader' field, which references a Windows-based browser environment ('Windows NT 10.0; Win64; x64; ... Edge/17.17134'). There are no explicit Linux or cross-platform command-line examples, nor are Linux tools or patterns mentioned. While the page is largely platform-neutral, the only concrete environment reference is Windows, and no Linux equivalents are provided.
Recommendations
- Add example log entries or user agent strings that reference Linux environments (e.g., 'Mozilla/5.0 (X11; Linux x86_64; ...)').
- Where environment-specific fields are shown, provide both Windows and Linux variants to illustrate cross-platform applicability.
- Include references to Linux monitoring tools or patterns if relevant, or clarify that the metrics and logs are accessible equally from Linux and Windows environments.
- Review reusable content includes for any hidden platform bias and update with cross-platform examples where possible.
Storage
Quickstart: Azure Blob storage library v12 - JS Browser
...s/storage/blobs/quickstart-blobs-javascript-browser.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation demonstrates a subtle Windows bias by listing Windows-specific consoles (cmd, PowerShell) before Bash when instructing users to create directories and run commands. Additionally, the prerequisites and instructions reference Visual Studio Code and Node.js, which are cross-platform, but do not provide explicit Linux-specific guidance or examples (such as using Linux package managers for Node.js installation, or alternative editors). There are no explicit Linux command-line examples or mentions of Linux-specific tools or patterns.
Recommendations
- When referencing console windows, list Bash (Linux/macOS) first or equally alongside cmd/PowerShell, and clarify that all commands work on Linux, macOS, and Windows.
- Provide explicit Linux/macOS instructions for installing Node.js (e.g., using apt, yum, brew) in the prerequisites section.
- Mention alternative editors (e.g., Vim, nano, Sublime Text) for users who may not use Visual Studio Code.
- Include a note or section confirming that all steps are cross-platform and highlighting any platform-specific differences if they exist.
- Where possible, provide example commands for both Windows and Linux/macOS environments, especially for project setup and running scripts.
Storage
Limitations & known issues with SFTP in Azure Blob Storage
...ge/blobs/secure-file-transfer-protocol-known-issues.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by providing a client settings example only for WinSCP, a popular Windows SFTP client, without mentioning or providing equivalent guidance for Linux/macOS SFTP clients (such as OpenSSH's sftp, FileZilla, or lftp). No Linux-specific tools, commands, or troubleshooting steps are referenced, and the only client configuration advice is for a Windows application.
Recommendations
- Add configuration and troubleshooting examples for common Linux/macOS SFTP clients, such as OpenSSH's sftp, FileZilla, or lftp.
- Include a section listing recommended settings or known issues for Linux/macOS SFTP clients, similar to the WinSCP example.
- When mentioning client settings, present Windows and Linux/macOS options side-by-side or in parallel, rather than focusing solely on Windows tools.
- Reference Linux command-line patterns (e.g., sftp, scp) in troubleshooting and usage examples.
- Ensure that any client-specific advice is balanced and covers both Windows and Linux/macOS environments.
Storage
Enable or disable SFTP support in Azure Blob Storage
.../blobs/secure-file-transfer-protocol-support-how-to.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides step-by-step instructions for enabling and disabling SFTP support in Azure Blob Storage using the Azure Portal, PowerShell, and Azure CLI. PowerShell examples are given equal prominence to Azure CLI, but PowerShell is a Windows-centric tool, and its section appears before the Azure CLI section. There are no explicit Linux shell or Bash examples, and no mention of Linux-specific tools or workflows, which may disadvantage Linux users.
Recommendations
- Provide Bash or shell script examples alongside PowerShell, especially for common administrative tasks.
- Consider listing Azure CLI examples before PowerShell, as Azure CLI is cross-platform and more commonly used on Linux.
- Explicitly mention that Azure CLI commands can be run on Linux, macOS, and Windows, and provide guidance for Linux users where appropriate.
- If PowerShell is included, clarify that PowerShell Core is available cross-platform, or provide equivalent Bash commands where possible.
- Add a note or section for Linux administrators, outlining any differences or tips for managing SFTP support from Linux environments.
Storage
Security recommendations for Blob storage
...ain/articles/storage/blobs/security-recommendations.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation page focuses exclusively on Azure portal and service features, with no command-line examples or tooling references. However, there is an implicit bias toward Windows environments: all security recommendations reference Azure-native tools and services (such as Microsoft Defender for Cloud, Azure Resource Manager, Azure Key Vault, and Azure Monitor) that are typically accessed via the Azure Portal or PowerShell, with no mention of Linux CLI tools, Bash, or cross-platform scripting. There are no examples or guidance for Linux users (e.g., using Azure CLI in Bash, automation via shell scripts, or integration with Linux-native security tools).
Recommendations
- Add cross-platform command-line examples for each recommendation, using Azure CLI (az) commands that can be run on Linux, macOS, and Windows.
- Where automation is discussed, provide sample scripts in Bash as well as PowerShell.
- Mention Linux-native tools and patterns for monitoring, such as integration with syslog, auditd, or other Linux logging frameworks.
- Clarify that all recommendations can be implemented from Linux environments, and provide links to relevant Linux documentation.
- Ensure parity in guidance for both Azure Portal (GUI) and CLI-based workflows, making it clear that Linux users are first-class citizens.
Storage
Tutorial - Simulate a failure in reading data from the primary region
...icles/storage/blobs/simulate-primary-region-failure.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation demonstrates some Windows bias by recommending Fiddler (a Windows-centric tool) as a primary method for simulating failures, without mentioning Linux alternatives. Additionally, in the static route section, Windows commands and tools (e.g., 'ipconfig', 'route add') are mentioned first or equally, but the Fiddler section is entirely Windows-focused.
Recommendations
- Provide Linux/macOS alternatives to Fiddler, such as mitmproxy or similar cross-platform tools, and include equivalent instructions.
- When listing commands or tools, alternate the order or explicitly show parity between Windows and Linux/macOS, rather than focusing on Windows-first or Windows-only tools.
- Clarify in the prerequisites or relevant sections which tools are cross-platform and which are not, and offer guidance for users on non-Windows systems.
- Consider adding screenshots or code snippets for Linux/macOS tools where Fiddler is used for Windows.
Storage
Reacting to Azure Blob storage events
.../articles/storage/blobs/storage-blob-event-overview.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation page lists quickstart articles for Azure portal, PowerShell, and Azure CLI, with PowerShell (a Windows-centric tool) given its own row and mentioned before Azure CLI. There are no explicit Linux shell or Bash examples, nor is there mention of Linux-specific tools or patterns. The CLI example is generic, but PowerShell is highlighted, which may suggest a Windows bias.
Recommendations
- Add explicit Bash or shell script examples for Linux users alongside PowerShell examples.
- Clarify that Azure CLI works cross-platform and provide Linux-specific usage notes where relevant.
- Consider listing Azure CLI before PowerShell in quickstart tables to avoid implicit prioritization of Windows tools.
- Include references to Linux-native automation tools or patterns where appropriate.
- Ensure that all code snippets and instructions are tested and presented for both Windows and Linux environments.
Storage
Blob Storage feature support in Azure storage accounts
...e/blobs/storage-feature-support-in-storage-accounts.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Summary
The documentation lists both Azure CLI and PowerShell command support for Blob Storage, but only explicitly mentions PowerShell (a Windows-centric tool) in the feature tables. There is no explicit mention of Linux shell or Bash examples, nor are Linux-specific tools (other than Blobfuse) highlighted. PowerShell commands are given parity with CLI commands, but the presence of PowerShell as a distinct row and the lack of Linux/Bash equivalents suggests a mild Windows bias.
Recommendations
- Add explicit references to Bash or Linux shell command examples where applicable, especially in feature tables.
- Include links to Linux-native tools (e.g., azcopy, Blobfuse, s3cmd) alongside PowerShell and CLI references.
- Ensure that examples and feature support documentation do not prioritize Windows tools (PowerShell) over cross-platform or Linux-native alternatives.
- Consider adding a row for 'Blob Storage Bash commands' or 'Blob Storage Linux shell commands' in the feature tables for parity.
- Review linked quickstart and reference articles to ensure Linux users are equally supported and not directed primarily to Windows-centric tooling.
Storage
Check the Last Sync Time property for a storage account
...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 examples for both PowerShell and Azure CLI, but PowerShell is presented first, which may suggest a Windows-centric approach. The PowerShell example is detailed and references the Az.Storage module, a Windows-focused tool, while the Azure CLI example is provided but not prioritized. There are no Linux-specific shell examples (e.g., Bash), nor is there mention of Linux tools or usage patterns.
Recommendations
- Alternate the order of examples so that Azure CLI (cross-platform) is presented before PowerShell, or present both equally.
- Explicitly mention that Azure CLI works on Linux, macOS, and Windows, and provide Bash-specific usage notes if relevant.
- Add examples using Bash scripting to demonstrate Linux usage patterns.
- Avoid language that implies PowerShell is the default or preferred method unless there is a technical reason.
- Consider including a note about installing and using Azure CLI on Linux systems.
Storage
Configure an expiration policy for shared access signatures (SAS)
.../main/articles/storage/common/sas-expiration-policy.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides configuration instructions for SAS expiration policies using the Azure portal, PowerShell, and Azure CLI. PowerShell examples are given in detail and are presented before Azure CLI examples, which can indicate a Windows-first and PowerShell-heavy bias. There are no explicit Linux shell (bash) examples, nor is there mention of Linux-specific tooling or patterns. The CLI examples are generic and could be used on Linux, but the lack of bash-specific context or parity in example ordering may disadvantage Linux users.
Recommendations
- Add explicit bash examples for Azure CLI commands, including shell variable usage and output parsing.
- Present Azure CLI examples before PowerShell examples, or at least in parallel, to avoid Windows-first ordering.
- Include notes clarifying that Azure CLI is cross-platform and can be used on Linux, macOS, and Windows.
- Reference Linux-specific tools or patterns where relevant (e.g., jq for JSON parsing, shell scripting for automation).
- Ensure screenshots and UI references are not Windows-centric (e.g., avoid showing only Windows browser or desktop environments).
Storage
Create a resource instance network rule for Azure Storage
.../common/storage-network-security-resource-instances.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides detailed PowerShell examples for managing Azure Storage network rules, with PowerShell presented before Azure CLI. PowerShell is primarily associated with Windows environments, which may disadvantage Linux users. While Azure CLI examples are included, there are no Bash or Linux shell-specific notes, and PowerShell is given prominence by being listed first.
Recommendations
- Alternate the order of PowerShell and Azure CLI sections, or present Azure CLI first to avoid Windows-first bias.
- Include explicit Bash/Linux shell examples or notes for Azure CLI usage in Linux environments.
- Add a brief section explaining cross-platform usage, clarifying that Azure CLI is natively supported on Linux and macOS, while PowerShell is more common on Windows.
- Reference installation and usage guides for both Azure CLI and PowerShell on multiple platforms.
- Ensure terminology and instructions do not assume a Windows environment (e.g., avoid references to Windows-only tools or paths).
Storage
Guidelines & limitations: Azure Storage firewall
...storage/common/storage-network-security-limitations.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page references Windows-centric tools such as PowerShell and the Azure portal as primary means for configuring firewall settings, mentioning them before cross-platform alternatives like Azure CLI. There are no explicit Linux-specific examples or tools mentioned, and the guidance does not provide parity for Linux users in terms of step-by-step instructions or tool recommendations.
Recommendations
- Include explicit examples using Azure CLI, which is cross-platform, for all configuration steps currently described with PowerShell or the Azure portal.
- Add references to Linux-native tools or workflows where applicable, such as scripting with Bash or using REST API calls from Linux environments.
- Ensure that instructions for changing properties (e.g., defaultAction) are demonstrated with both PowerShell and Azure CLI, and clarify that Azure CLI works on Linux, macOS, and Windows.
- Review the order of tool mentions to avoid listing Windows-specific options first; present cross-platform tools like Azure CLI before or alongside PowerShell.
- Consider adding a section or callout for Linux users, summarizing best practices and tool recommendations for managing Azure Storage firewall settings from Linux environments.
Storage
Set the default public network access rule: Azure Storage
.../common/storage-network-security-set-default-access.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation presents PowerShell instructions before Azure CLI, which may suggest a Windows-first bias. PowerShell is a Windows-centric tool, while Azure CLI is cross-platform and preferred by many Linux users. There are no explicit Linux shell examples, and no mention of Linux-specific patterns or tools. However, Azure CLI coverage does provide parity in functionality.
Recommendations
- Present Azure CLI instructions before PowerShell, or in parallel, to avoid Windows-first ordering.
- Explicitly mention that Azure CLI works on Linux, macOS, and Windows.
- Include Linux shell usage examples (e.g., bash) for Azure CLI commands.
- Add a note clarifying platform compatibility for each tool.
- Consider including links to Linux installation guides for Azure CLI.
Storage
Replace Azure Blob Storage properties & metadata with AzCopy
...common/storage-use-azcopy-blobs-properties-metadata.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation page exhibits mild Windows bias by referencing Windows Command Shell (cmd.exe) first when discussing quoting conventions, and by providing tips that prioritize Windows shell differences. There are no Linux-specific examples, nor are Linux tools or shell patterns discussed in detail. All examples use generic AzCopy syntax, but the only shell-specific advice is for Windows users.
Recommendations
- Provide explicit Linux and macOS shell examples alongside Windows examples, showing command syntax in bash/zsh.
- Include tips for Linux/macOS users, such as handling environment variables, escaping, or using AzCopy in scripts.
- Mention common Linux installation methods (e.g., apt, yum, Homebrew) for AzCopy in the 'Get started' section.
- Balance shell-specific notes by listing Linux/macOS conventions before or alongside Windows conventions.
- Add troubleshooting or configuration notes relevant to Linux/macOS environments.
Storage
Azure Storage encryption for data at rest
.../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 as an analogy for Azure Storage encryption and linking to the Windows-specific Cryptography API: Next Generation (CNG) documentation. These references prioritize Windows technologies and tools without mentioning Linux equivalents or providing cross-platform context. There are no command-line examples, but the analogies and references are Windows-centric.
Recommendations
- Provide analogies or references to Linux-native encryption tools (e.g., LUKS, dm-crypt) alongside BitLocker when describing Azure Storage encryption.
- Include links to cross-platform cryptographic standards or APIs (such as OpenSSL or Linux kernel cryptography documentation) in addition to Windows CNG.
- Ensure that conceptual explanations and external references are balanced and inclusive of both Windows and Linux environments.
- If mentioning platform-specific tools, clarify that Azure Storage encryption is platform-agnostic and does not require familiarity with Windows-specific technologies.